[karmic] netbook-launcher segfault 4 on libc

No crash files exist for this. A watchdog process seems to intercept the segfault and restart netbook-launcher.

Architecture: i386
CheckboxSubmission: cbd66e76023689ba0d9f5f41745564b1
CheckboxSystem: b1865df84255b8716d3bcc269ff410d1
DistroRelease: Ubuntu 9.10
GConfNonDefault:
 /apps/netbook-launcher/disable_single_instance=false
 /apps/netbook-launcher/force_low_graphics=false
MachineType: TOSHIBA TOSHIBA NB205
Package: netbook-launcher 2.1.10-0ubuntu1
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=bdccab3e-7939-48a4-84bd-dde2782cfe7b ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu6
 libdrm2 2.4.13-1ubuntu1
 xserver-xorg-video-intel 2:2.8.1-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu2
Tags: ubuntu-unr ubuntu-unr
Uname: Linux 2.6.31-11-generic i686
UserGroups:

XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf'
Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Can't open display
dmi.bios.date: 04/07/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.20
dmi.board.name: KAVAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnTOSHIBA:bvrV1.20:bd04/07/2009:svnTOSHIBA:pnTOSHIBANB205:pvrPLL20U-00P01D:rvnTOSHIBA:rnKAVAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.name: TOSHIBA NB205
dmi.product.version: PLL20U-00P01D
dmi.sys.vendor: TOSHIBA
fglrx: Not loaded
glxinfo: Error: command ['glxinfo'] failed with exit code 255: Error: unable to open display
setxkbmap: Error: command ['setxkbmap', '-print'] failed with exit code 255: Cannot open display "default display"
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-11-generic
xdpyinfo: Error: command ['xdpyinfo'] failed with exit code 1: xdpyinfo: unable to open display "".
xkbcomp:
 Error: command ['xkbcomp', ':0', '-w0', '-'] failed with exit code 1: Error: Cannot open display ":0"
                   Exiting

Thanks for the report Joey. The xsession-errors makes it look like quite a bit more may be failing than just netbook-launcher, can you confirm that? Is netbook-launcher the only thing that seems to crash, or is it the entire desktop? Can you even alt-f2 and run things?

I can get to a console via control-f1 assuming I do that at or before GDM login. Once logged in I can get over to it as long as I was already logged in to it. If I just logged in via gdm straight away I am not able to control-f1 out.

Yes, I can get to alt-f2 inside! And I do see the netbook desktop for a second or two before it crashes and restarts.

During the partial upgrade from alpha to beta this week, there was a point in time where it did work until apt-get downloaded libc6 and installed it.

I was able to use the desktop switcher and when I did apport generated a new bug report: bug 441537 and for some reason it marked it private. I think this might be a dup of bug 360999.

Discussed on IRC with Joey and there were some possible hardware issues that may have been a factor here. He said he would reproduce when he gets a chance, so I'm going to mark incomplete for now so that nobody reads too much into this in the meantime.

I was able to fix and then recreate this! The original problem was a somehow corrupted (binary looking) .gtk-bookmarks (hat tip to Paul for that). I deleted it and it works great. If I cat a binary file into .gtk-bookmarks it crashes the launcher. Looking for someone to confirm this.

Reducing severity since 1. This shouldn't normally happen on a normal system, ans 2. Is probably the least of your problems if something is corrupting your fs :)