netbook-launcher crashed with SIGSEGV in glGetString()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
netbook-launcher (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: netbook-launcher
Booting up from CD with a bad disk on a WinXP PC. No idea when and how it crashed, then Ubuntu restarted OK, since I am doing this note on that machine.
ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 16 11:58:46 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
GConfNonDefault:
/apps/
/apps/
LiveMediaBuild: Ubuntu-
MachineType: ECS L7VMM3
Package: netbook-launcher 2.1.12-0ubuntu3
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: netbook-launcher
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu7
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0x58a326 <glGetString+6>: jmp *0x44c(%eax)
PC (0x0058a326) ok
source "*0x44c(%eax)" ok
Reason could not be automatically determined.
Signal: 11
SourcePackage: netbook-launcher
StacktraceTop:
glGetString () from /usr/lib/libGL.so.1
?? () from /usr/lib/
cogl_features_
?? () from /usr/lib/
cogl_texture_
Tags: ubuntu-unr ubuntu-unr
Title: netbook-launcher crashed with SIGSEGV in glGetString()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/
XorgLogOld: Error: [Errno 2] No such file or directory: '/var/log/
dmi.bios.date: 04/02/01
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 07.00T
dmi.board.name: L7VMM3
dmi.board.vendor: ECS
dmi.board.version: 3.1
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: L7VMM3
dmi.product.
dmi.sys.vendor: ECS
fglrx: Not loaded
system:
distro: Ubuntu
architecture: i686kernel: 2.6.31-14-generic
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #467474, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.