[Ubuntu-x-swat] [Bug 532603] Re: login sequence aborts and restarts occasionally

2010-03-16 Thread Bogdan Butnaru
*** This bug is a duplicate of bug 532047 ***
https://bugs.launchpad.net/bugs/532047

Hmm. I’ll have to do some more testing. After sending the bug report I
noticed that indeed the Return key caused the problem, so I’ve just
uninstalled Plymouth a few days ago.

This is what’s in my apt’s cache folder:

bogd...@mabelode:/var/cache/apt/archives$ ls |grep plymouth
libplymouth2_0.8.0~-14_amd64.deb
plymouth_0.8.0~-14_amd64.deb
plymouth-x11_0.8.0~-14_amd64.deb

Which I guess means yes to your second question. It’s also the latest
version shown right now as available by aptitude.

(A bit tangential: does Plymouth do anything on nvidia? On Karmic I had
a very nice setup, the boot process switched to a Vesa console very
early and I had a 1920x1200 working console. Since Lucid nothing I tried
worked; my console is an ugly VGA, and for some reason my sound turns
off when I switch from X to it. Is it still possible to get things
working as in Karmic on nvidia hardware?)

-- 
login sequence aborts and restarts occasionally
https://bugs.launchpad.net/bugs/532603
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu (via bug 532047).

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 532603] Re: login sequence aborts and restarts occasionally

2010-03-15 Thread Robert Hooker
** Description changed:

  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-errors*, then
  opened FF and this bug report.
  
  I noticed the following in .xsession-errors.old (which I assume
  corresponds to the crashed session):
  
  
  (gnome-terminal:1803): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion 
`entry != NULL  entry-lock_count  0' failed
  gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) 
on X server :0.0.
  ** 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-authentication-agent-1: Fatal IO error 11 (Resource temporarily 
unavailable) on X server :0.0.
  gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X 
server :0.0.
  gtk-window-decorator: Fatal IO error 11 (Resource temporarily unavailable) on 
X server :0.0.
  libnotify-Message: GetServerInformation call failed: Connection was 
disconnected before a reply was received
  libnotify-Message: Error getting spec version
  
  (Pidgin:1616): libnotify-CRITICAL **: notify_get_server_caps: assertion 
`proxy != NULL' failed
  gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) 
on X server :0.0.
  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::attachInternal. Attach failed Could not open network socket
  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/mainToolBar (child of QVBox/unnamed) to layout for 
PlaylistWindow/PlaylistWindow
  QObject::connect: Incompatible sender/receiver arguments
-   StarManager::ratingsColorsChanged() -- 
ContextBrowser::ratingOrScoreOrLabelsChanged(const QString)
+  StarManager::ratingsColorsChanged() -- 
ContextBrowser::ratingOrScoreOrLabelsChanged(const QString)
  Amarok: [Loader] Starting amarokapp..
  Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use 
amarokapp.
  
  
  The line starting with “(gnome-terminal:1803)” is always there, even in
  “normal” sessions (some other bug somewhere), everything else I assume
  belongs to the crash. It's strange that Amarok _does_ work in this
  session, although I don't think I started it again. The lines from it
  appeared after I started Geany (in the .xs-e.old file); perhaps start-up
  delay caused it to connect to the new session. No idea if it's relevant
  to this bug, I just mentioned it in case it's helpful.
  
+ 
+ Backtrace:
+ 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a25d8]
+ 1: /usr/bin/X (0x40+0x652dd) [0x4652dd]
+ 2: /lib/libpthread.so.0 (0x7f18dc377000+0xf920) [0x7f18dc386920]
+ 3: /usr/bin/X (GrabMatchesSecond+0xf) [0x44814f]
+ 4: /usr/bin/X (0x40+0x3c92b) [0x43c92b]
+ 5: /usr/bin/X (0x40+0x3cfe3) [0x43cfe3]
+ 6: /usr/bin/X (0x40+0xdecbf) [0x4decbf]
+ 7: /usr/bin/X (XkbHandleActions+0x1c4) [0x507504]
+ 8: /usr/bin/X (AccessXFilterPressEvent+0x23b) [0x5007cb]
+ 9: /usr/bin/X (mieqProcessDeviceEvent+0x1c1) [0x4a1a11]
+ 10: /usr/bin/X (mieqProcessInputEvents+0xda) [0x4a1b2a]
+ 11: /usr/bin/X (ProcessInputEvents+0x9) [0x46fa29]
+ 12: /usr/bin/X (0x40+0x308b3) [0x4308b3]
+ 13: /usr/bin/X 

[Ubuntu-x-swat] [Bug 532603] Re: login sequence aborts and restarts occasionally

2010-03-15 Thread Robert Hooker
Are you still having this problem after the plymouth update on march
12th?

Is your plymouth version 0.8.0~-14?

** Package changed: nvidia-graphics-drivers (Ubuntu) = plymouth
(Ubuntu)

-- 
login sequence aborts and restarts occasionally
https://bugs.launchpad.net/bugs/532603
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 532603] Re: login sequence aborts and restarts occasionally

2010-03-05 Thread Bogdan Butnaru

** Attachment added: BootDmesg.txt
   http://launchpadlibrarian.net/40243804/BootDmesg.txt

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/40243805/Dependencies.txt

** Attachment added: GdmLog.txt
   http://launchpadlibrarian.net/40243806/GdmLog.txt

** Attachment added: GdmLog1.txt
   http://launchpadlibrarian.net/40243807/GdmLog1.txt

** Attachment added: GdmLog2.txt
   http://launchpadlibrarian.net/40243808/GdmLog2.txt

** Attachment added: Lspci.txt
   http://launchpadlibrarian.net/40243809/Lspci.txt

** Attachment added: Lsusb.txt
   http://launchpadlibrarian.net/40243810/Lsusb.txt

** Attachment added: PciDisplay.txt
   http://launchpadlibrarian.net/40243811/PciDisplay.txt

** Attachment added: ProcCpuinfo.txt
   http://launchpadlibrarian.net/40243812/ProcCpuinfo.txt

** Attachment added: ProcInterrupts.txt
   http://launchpadlibrarian.net/40243813/ProcInterrupts.txt

** Attachment added: ProcModules.txt
   http://launchpadlibrarian.net/40243815/ProcModules.txt

** Attachment added: RelatedPackageVersions.txt
   http://launchpadlibrarian.net/40243816/RelatedPackageVersions.txt

** Attachment added: UdevDb.txt
   http://launchpadlibrarian.net/40243817/UdevDb.txt

** Attachment added: UdevLog.txt
   http://launchpadlibrarian.net/40243818/UdevLog.txt

** Attachment added: XorgConf.txt
   http://launchpadlibrarian.net/40243819/XorgConf.txt

** Attachment added: XorgLog.txt
   http://launchpadlibrarian.net/40243820/XorgLog.txt

** Attachment added: XorgLogOld.txt
   http://launchpadlibrarian.net/40243822/XorgLogOld.txt

** Attachment added: Xrandr.txt
   http://launchpadlibrarian.net/40243823/Xrandr.txt

** Attachment added: glxinfo.txt
   http://launchpadlibrarian.net/40243825/glxinfo.txt

** Attachment added: monitors.xml.txt
   http://launchpadlibrarian.net/40243827/monitors.xml.txt

** Attachment added: setxkbmap.txt
   http://launchpadlibrarian.net/40243828/setxkbmap.txt

** Attachment added: xdpyinfo.txt
   http://launchpadlibrarian.net/40243830/xdpyinfo.txt

** Attachment added: xkbcomp.txt
   http://launchpadlibrarian.net/40243832/xkbcomp.txt

-- 
login sequence aborts and restarts occasionally
https://bugs.launchpad.net/bugs/532603
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp