Friday, May 3, 2024
 Popular · Latest · Hot · Upcoming
2
rated 0 times [  2] [ 0]  / answers: 1 / hits: 15728  / 1 Year ago, fri, november 18, 2022, 7:32:19

My Ubuntu 12.04 box has been working fine. A recent update may have messed something up.



I normally run remote windows on it, and I noticed that my windows were failing to start up. I then tried logging into it directly from the GUI console, and I'm seeing that after I press enter on the (valid) password, the page just redisplays. It's not a password error, as that would give me an inline error. I see some messages appear and disappear quickly between the login screen going away and then redisplaying, but they go away too quickly to read.



I was able to run the non-gui login, and I did an update and upgrade, and then rebooted, but it's doing the same thing.



I have a Samba connection from my Windows box, and that's still working.



If it matters, here's my uname output (somewhat elided):



Linux ... 3.2.0-26-generic #41-Ubuntu SMP Thu Jun 14 17:49:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux



What can I do to troubleshoot this?



Note that when I select "Guest Session", it lets me log in and displays the window manager. This seems significant to me. Does this mean that something specific to my login is causing it to fail?



Note: If it matters, here's the output from /var/log/dmesg. The line about gdm seems interesting:



[    9.815883] Bluetooth: RFCOMM TTY layer initialized
[ 9.815887] Bluetooth: RFCOMM socket layer initialized
[ 9.815888] Bluetooth: RFCOMM ver 1.11
[ 9.879088] [PCSPP,TRISTATE]
[ 9.879092] parport0: irq 7 detected
[ 9.883935] type=1400 audit(1341871177.871:10): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=845 comm="apparmor_parser"
[ 9.884365] type=1400 audit(1341871177.871:11): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/ntpd" pid=851 comm="apparmor_parser"
[ 9.950397] e1000e 0000:00:19.0: irq 42 for MSI/MSI-X
[ 9.961160] init: gdm main process (907) killed by TERM signal
[ 9.966358] lp0: using parport0 (polling).


Some other useful information might be in what appears in /var/log/auth.log when I try to log in:



Jul 11 08:28:32 -hostname- lightdm: pam_unix(lightdm:session): session closed for user lightdm
Jul 11 08:28:32 -hostname- lightdm: pam_unix(lightdm:session): session opened for user -username- by (uid=0)
Jul 11 08:28:32 -hostname- lightdm: pam_ck_connector(lightdm:session): nox11 mode, ignoring PAM_TTY :0
Jul 11 08:28:32 -hostname- lightdm: pam_unix(lightdm:session): session closed for user -username-
Jul 11 08:28:32 -hostname- lightdm: pam_unix(lightdm:session): session opened for user lightdm by (uid=0)
Jul 11 08:28:32 -hostname- lightdm: pam_ck_connector(lightdm:session): nox11 mode, ignoring PAM_TTY :0
Jul 11 08:28:33 -hostname- lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "-username-"
Jul 11 08:28:33 -hostname- dbus[769]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.60" (uid=104 pid=14858 comm="/usr/lib/indicator-datetime/indicator-datetime-ser") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.16" (uid=0 pid=1329 comm="/usr/sbin/console-kit-daemon --no-daemon ")

More From » 12.04

 Answers
4

Ok, I figured it out. It was simply an error in my .bashrc. I finally saw my .xsession-errors file. It wasn't a recent change my .bashrc, but I recently changed my .profile to source it. I believe the problem is that I'm sourcing it from Bourne shell, so some Bash-specific stuff fails.


[#36973] Saturday, November 19, 2022, 1 Year  [reply] [flag answer]
Only authorized users can answer the question. Please sign in first, or register a free account.
reangi

Total Points: 213
Total Questions: 102
Total Answers: 114

Location: Namibia
Member since Wed, Jan 19, 2022
2 Years ago
reangi questions
;