usplash crashed with SIGSEGV in __svgalib_get_perm()

[gnuckx]

Binary package hint: usplash

usplash crashed with SIGSEGV in __svgalib_get_perm()

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /sbin/usplash
NonfreeKernelModules: nvidia
Package: usplash 0.5.24
ProcAttrCurrent: unconfined
ProcCmdline: /sbin/usplash -c -x 1280 -y 1024
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: usplash
StacktraceTop:
 ?? () from /lib/libusplash.so.0
 __svgalib_get_perm () from /lib/libusplash.so.0
 vga_setchipset () from /lib/libusplash.so.0
 usplash_svga_init () from /lib/libusplash.so.0
 usplash_init () from /lib/libusplash.so.0
Title: usplash crashed with SIGSEGV in __svgalib_get_perm()
Uname: Linux 2.6.27-6-generic x86_64
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:?? () from /lib/libusplash.so.0
__svgalib_get_perm () from /lib/libusplash.so.0
vga_setchipset () from /lib/libusplash.so.0
usplash_svga_init () from /lib/libusplash.so.0
usplash_init () from /lib/libusplash.so.0

[Saivann Carignan (oxmosys)]

Confirming. I get the same bug each time that I install a new linux kernel and reboot. On first boot, usplash does not appear at all (I only see the console). If I stop ubuntu loading with sysrec + b, the computer reboots and now show a wide red corrupted screen instead of usplash, if I reset again with sysrec + b, usplash now starts to work correctly on next boot and apport ask to send crash informations.

[gnuckx (gnuckx)]

It happens at boot, without apparent provocation.

[Anakin Starkiller (sunrider)]

I have this problem each time I start a new gnome session....
Quite annoying...

[gnuckx (gnuckx)]

Happens at boot

[gnuckx (gnuckx)]

usplash crashed with SIGSEGV in __svgalib_get_perm()

It happened at boot. Just updated generic kernel.

[bartje (bart-deruyter)]

Hapens at boot too, using the real-time kernel. What is usplash actually?

[Michael (michaeljt)]

Apport just reported this. It was reported after boot had completed on Kubuntu 8.10, released version. No visible symptoms as yet (although I often notice that usplash does not display properly when shutting down again).

[Michael (michaeljt)]

By the way, is there any way of getting Apport to attach its crash information to an existing bug rather than to a new one?

[Sjors Gielen (sgielen)]

Got this on Ubuntu Jaunty 9.04, after having it installed for a while now. Linux kernel version 2.6.28-10.33, never had this before.

[quote]By the way, is there any way of getting Apport to attach its crash information to an existing bug rather than to a new one?[/quote]
I agree, there are still some features in apport (maybe just apport-qt) I'm missing, like that one and also saving the files and/or attach them to a different bugtracker etc. I should file these as a bug... :)

[Zemblan (graeme-zembla)]

Apport reported this after a kernel and other stuff were upgraded on Ubuntu 9.04, would like to attatch the crash info without opening a new bug report but don't know how. It caused no noticable problems except the notification, however the progress bar on the boot screen did not progress as it should, and booting was noticably slower after the update than before.

[Alex Ivasyuv (industral)]

Confirm this bug in Ubuntu jaunty 9.04 amd_64, 2.6.28-11-generic.
usplash: 0.5.31 (usplash_0.5.31_amd64.deb).

[Tristan Greaves (tristan-extricate)]

This has started happening to me since yesterday. apport flashes up the info once I have logged into Gnome.

jaunty 9.04
Linux petrucci 2.6.28-11-generic #37-Ubuntu SMP Mon Mar 23 16:40:00 UTC 2009 x86_64 GNU/Linux
usplash: 0.5.31 (usplash_0.5.31_amd64.deb).

[Alan (mrintegrity)]

I think a bug should be created for the crash report tool as the "reduced" report reccomended for slow connections was larger than the complete report by 10KiB

[fly3rman (fly3rman)]

ill confirm alans comment, same problem for me, 80kb full, 90kb reduced

[Rocko (rockorequin)]

I just got this too in the Jaunty beta, kernel 2.6.8-11.40.

@Michael: You can attach some info to an existing bug using apport-collect (eg apport-collect 280487 will add info to this bug). I'm not sure if it's clever enough to locate core dumps etc from a past crash, though. I used it in #348731 and it just attached info about the distro release, kernel, and architecture.