login sequence aborts and restarts occasionally
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Hello! I just updated to Lucid, and I've been noticing a bug.
I have my computer set-up to login automatically. This seems to work: the login process works correctly, I can start some applications. The problem is that _sometimes_ (I'm 95% sure it doesn't happen every time) the process stops somewhere and I'm returned to GDM. I can then proceed to login manually, and the second time it seems to work.
I've only noticed this happening when I was in a hurry, and I was starting a few programs as soon as the panel became available. However, since I was always in a hurry when this happened, I can't remember exactly everything I did. I'm not sure if timing is involved, or if this a manifestation of bug #522692 or bug #516412.
Today I started the computer, and it started an automatic log-in. I started a couple of apps: a script that mounts some SSHFS shares, Amarok, and Firefox, and I _think_ I started a terminal, but I don't remember if I had time to type anything in it. Then I was dumped to GDM's login screen. I logged in, I ran "geany ~/.xsession-
I noticed the following in .xsession-
************
(gnome-
gnome-settings-
** Message: Got disconnected from the session message bus; retrying to reconnect every 10 seconds
gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
** Message: <info> disconnected by the session bus.
nautilus: Fatal IO error 104 (Connection reset by peer) on X server :0.0.
nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
polkit-
gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gtk-window-
libnotify-Message: GetServerInform
libnotify-Message: Error getting spec version
(Pidgin:1616): libnotify-CRITICAL **: notify_
gdu-notificatio
padevchooser: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
firefox-bin: Fatal IO error 0 (Success) on X server :0.0.
The application 'Pidgin' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
Session management error: Could not open network socket
Session management error: Could not open network socket
DCOPClient:
Session management error: Could not open network socket
kbuildsycoca running...
DCOP Cleaning up dead connections.
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
QLayout: Adding KToolBar/
QObject::connect: Incompatible sender/receiver arguments
StarManager:
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
************
The line starting with “(gnome-
Backtrace:
0: /usr/bin/X (xorg_backtrace
1: /usr/bin/X (0x400000+0x652dd) [0x4652dd]
2: /lib/libpthread
3: /usr/bin/X (GrabMatchesSec
4: /usr/bin/X (0x400000+0x3c92b) [0x43c92b]
5: /usr/bin/X (0x400000+0x3cfe3) [0x43cfe3]
6: /usr/bin/X (0x400000+0xdecbf) [0x4decbf]
7: /usr/bin/X (XkbHandleActio
8: /usr/bin/X (AccessXFilterP
9: /usr/bin/X (mieqProcessDev
10: /usr/bin/X (mieqProcessInp
11: /usr/bin/X (ProcessInputEv
12: /usr/bin/X (0x400000+0x308b3) [0x4308b3]
13: /usr/bin/X (0x400000+0x2613a) [0x42613a]
14: /lib/libc.so.6 (__libc_
15: /usr/bin/X (0x400000+0x25ce9) [0x425ce9]
Caught signal 3 (Quit). Server aborting
ProblemType: Bug
Architecture: amd64
CurrentDmesg: [ 31.874483] ppdev: user-space parallel port driver
Date: Fri Mar 5 13:16:38 2010
DistroRelease: Ubuntu 10.04
DkmsStatus:
nvidia-current, 195.36.03, 2.6.32-15-generic, x86_64: installed
nvidia-current, 195.36.03, 2.6.32-14-generic, x86_64: installed
EcryptfsInUse: Yes
MachineType: System manufacturer P5Q-PRO
NonfreeKernelMo
Package: xorg 1:7.5+1ubuntu11
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: nvidia-
Uname: Linux 2.6.32-15-generic x86_64
dmi.bios.date: 11/04/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1501
dmi.board.
dmi.board.name: P5Q-PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P5Q-PRO
dmi.product.
dmi.sys.vendor: System manufacturer
system:
distro: Ubuntu
codename: lucidarchitecture: x86_64kernel: 2.6.32-15-generic
description: | updated |
Are you still having this problem after the plymouth update on march 12th?
Is your plymouth version 0.8.0~-14?