usplash crashed with SIGSEGV in __svgalib_get_perm()

StacktraceTop:port_in (port=972) at /build/buildd/usplash-0.5.16/svgalib/src/libvga.h:294
__svgalib_get_perm () at /build/buildd/usplash-0.5.16/svgalib/src/vga.c:1059
vga_setchipset (c=19) at /build/buildd/usplash-0.5.16/svgalib/src/vga.c:1569
usplash_svga_init () at usplash_svga.c:139
usplash_init () at libusplash.c:203

Happened to me while doing "sudo update-initramfs -u" with Hardy beta 1

This is probably fixed with the latest updates of usplash and the 2.6.24-14 kernel:

$ apt-cache policy usplash
usplash:
  Installed: 0.5.19
  Candidate: 0.5.19
  Version table:
 *** 0.5.19 0
        500 http://archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

This bug happened again for me with 0.5.19. I was watching a video and apport suddenly appeared for this usplash crash.

I got this today with 8.04 64 bits
lafa@black-shuttle:~$ dpkg -l|grep -i uspla
ii kubuntu-artwork-usplash 1:8.04-19 kubuntu artwork for usplash
ii libusplash0 0.5.19 userspace bootsplash library
ii usplash 0.5.19 Userspace bootsplash utility
ii usplash-theme-ubuntu 0.18 Usplash theme for Ubuntu

I don't know if it matters, but I got this from the logs that represents the shutdown sequence:
$ cat /var/log/syslog
[...]
Apr 14 09:49:55 ubuntu ntpd[6270]: synchronized to 192.43.244.18, stratum 1
Apr 14 09:50:13 ubuntu init: tty4 main process (4609) killed by TERM signal
Apr 14 09:50:13 ubuntu init: tty5 main process (4610) killed by TERM signal
Apr 14 09:50:13 ubuntu init: tty2 main process (4612) killed by TERM signal
Apr 14 09:50:13 ubuntu init: tty3 main process (4614) killed by TERM signal
Apr 14 09:50:13 ubuntu init: tty6 main process (4616) killed by TERM signal
Apr 14 09:50:13 ubuntu init: tty1 main process (6114) killed by TERM signal
Apr 14 09:50:13 ubuntu kernel: [87606.199800] printk: 212 messages suppressed.
Apr 14 09:50:13 ubuntu kernel: [87606.199804] usplash[18720] general protection rip:7f0f836b11bb rsp:7fff8bb35dc0 error:0
Apr 14 09:50:13 ubuntu kernel: [87606.657471] gdm[14593]: segfault at 1e31520 rip 7f9743da455a rsp 7fff4f62b880 error 4
Apr 14 09:50:13 ubuntu avahi-daemon[5058]: Got SIGTERM, quitting.
Apr 14 09:50:13 ubuntu avahi-daemon[5058]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Apr 14 09:50:17 ubuntu kernel: [87610.655748] ip6_tables: (C) 2000-2006 Netfilter Core Team
Apr 14 09:50:18 ubuntu exiting on signal 15
[...]

$ cat /var/log/messages
[...]
Apr 14 09:47:49 ubuntu -- MARK --
Apr 14 09:50:13 ubuntu kernel: [87606.199800] printk: 212 messages suppressed.
Apr 14 09:50:13 ubuntu kernel: [87606.199804] usplash[18720] general protection rip:7f0f836b11bb rsp:7fff8bb35dc0 error:0
Apr 14 09:50:13 ubuntu kernel: [87606.657471] gdm[14593]: segfault at 1e31520 rip 7f9743da455a rsp 7fff4f62b880 error 4
Apr 14 09:50:17 ubuntu kernel: [87610.655748] ip6_tables: (C) 2000-2006 Netfilter Core Team
Apr 14 09:50:18 ubuntu exiting on signal 15
[...]

$ cat /var/log/kern.log
[...]
Apr 14 09:50:13 ubuntu kernel: [87606.199800] printk: 212 messages suppressed.
Apr 14 09:50:13 ubuntu kernel: [87606.199804] usplash[18720] general protection rip:7f0f836b11bb rsp:7fff8bb35dc0 error:0
Apr 14 09:50:13 ubuntu kernel: [87606.657471] gdm[14593]: segfault at 1e31520 rip 7f9743da455a rsp 7fff4f62b880 error 4
Apr 14 09:50:17 ubuntu kernel: [87610.655748] ip6_tables: (C) 2000-2006 Netfilter Core Team
[...]

I still get crashes from usplash on hardy during shutdown:
/var/log/kern.log:
May 23 19:41:17 ubuntu kernel: [204694.340682] usplash[12718] general protection rip:7f6ad1c841bb rsp:7fffda106800 error:0
May 23 19:41:22 ubuntu kernel: [204699.015681] ip6_tables: (C) 2000-2006 Netfilter Core Team

/var/log/messages:
May 23 19:23:03 ubuntu -- MARK --
May 23 19:41:17 ubuntu kernel: [204694.340682] usplash[12718] general protection rip:7f6ad1c841bb rsp:7fffda106800 error:0
May 23 19:41:22 ubuntu kernel: [204699.015681] ip6_tables: (C) 2000-2006 Netfilter Core Team
May 23 19:41:23 ubuntu exiting on signal 15

I've also noticed that when it crashes during shutdown, there is no crash report on boot waiting in /var/crash/

should I mark this as a duplicate of bug 144900?
I'm not sure if it's the same thing

I still don't have the full usplash in ubuntu hardy heron 8.04.1

The usplash loads up, the bar goes back and forth, then all of the sudden it goes to
* Reading ... files ... for boot up (or something like that)

$ apt-cache policy usplash
usplash:
  Installed: 0.5.19
  Candidate: 0.5.19
  Version table:
 *** 0.5.19 0
        500 http://archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

/var/log/messages:Jul 9 23:24:20 ubuntu kernel: [178783.054256] usplash[7940] general protection rip:7f8e43ba81bb rsp:7fff4c02a720 error:0
/var/log/messages:Jul 13 01:31:01 ubuntu kernel: [ 2292.485929] usplash[28706] general protection rip:7f9645f571bb rsp:7fff4e3d9ad0 error:0
/var/log/kern.log:Jul 9 23:24:20 ubuntu kernel: [178783.054256] usplash[7940] general protection rip:7f8e43ba81bb rsp:7fff4c02a720 error:0
/var/log/kern.log:Jul 13 01:31:01 ubuntu kernel: [ 2292.485929] usplash[28706] general protection rip:7f9645f571bb rsp:7fff4e3d9ad0 error:0

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

I'll go for alpha 5 when it arrives

OK, during boot up is fine now, no breaks or crashes.
The problem now is that the usplash does not show up during shutdown. Instead of the ubuntu logo and the progress bar I see the shutdown messages. Only at the end I see ubuntu logo with an empty bar for a couple of seconds and then the machine powers off.

$ uname -a
Linux ubuntu 2.6.27-3-generic #1 SMP Wed Sep 10 16:18:52 UTC 2008 x86_64 GNU/Linux
$ apt-cache policy usplash
usplash:
  Installed: 0.5.23
  Candidate: 0.5.23
  Version table:
 *** 0.5.23 0
        500 http://archive.ubuntu.com intrepid/main Packages
        100 /var/lib/dpkg/status

whatever it was, it was fixed

(..in intrepid, I don't think it qualifies for a fix in hardy heron)

I'd like to be optimistic, but in linux-generic 2.6.27.7 the problem re-appeared.

I upgraded today to 2.6.27.7.8, we'll see how it goes :)

$ uname -a; apt-cache policy linux-generic
Linux ubuntu 2.6.27-7-generic #1 SMP Fri Oct 10 03:55:01 UTC 2008 x86_64 GNU/Linux
linux-generic:
  Installed: 2.6.27.7.8
  Candidate: 2.6.27.7.8
  Version table:
 *** 2.6.27.7.8 0
        500 http://archive.ubuntu.com intrepid/restricted Packages
        100 /var/lib/dpkg/status

This has not been fixed or is re-occuring in linux-generic package version 2.6.27.7.8

It happens on shutdown, my eye caught that something fails, I couldn't manage to read the whole message

syslog:
Oct 12 02:48:39 ubuntu acpid: client connected from 18444[0:0]
Oct 12 02:48:40 ubuntu acpid: client connected from 18444[0:0]
Oct 12 02:48:42 ubuntu gdmgreeter[18461]: Gtk-WARNING: Unable to locate theme engine in module_path: "ubuntulooks",
Oct 12 02:48:42 ubuntu bonobo-activation-server (forger-18463): could not associate with desktop session: Failed to connect to socket /tmp/dbus-Yf5OVEUbd7: Connection refused
Oct 12 02:48:48 ubuntu init: tty4 main process (4563) killed by TERM signal
Oct 12 02:48:48 ubuntu init: tty5 main process (4564) killed by TERM signal
Oct 12 02:48:48 ubuntu init: tty2 main process (4571) killed by TERM signal
Oct 12 02:48:48 ubuntu init: tty3 main process (4572) killed by TERM signal
Oct 12 02:48:48 ubuntu init: tty6 main process (4573) killed by TERM signal
Oct 12 02:48:48 ubuntu init: tty1 main process (5878) killed by TERM signal
Oct 12 02:48:48 ubuntu kernel: [22484.561100] usplash[18500] general protection ip:7f9940b16333 sp:7fff48f9b690 error:0 in libusplash.so.0[7f9940aff000+31000]
Oct 12 02:48:53 ubuntu kernel: [22489.419164] ip6_tables: (C) 2000-2006 Netfilter Core Team
Oct 12 02:48:56 ubuntu bluetoothd[5530]: bridge pan0 removed
Oct 12 02:48:56 ubuntu bluetoothd[5530]: Stopping SDP server
Oct 12 02:48:56 ubuntu bluetoothd[5530]: Exit
Oct 12 02:48:56 ubuntu avahi-daemon[4974]: Got SIGTERM, quitting.
Oct 12 02:48:56 ubuntu avahi-daemon[4974]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.2.
Oct 12 02:48:56 ubuntu exiting on signal 15

kern.log:
Oct 12 02:48:37 ubuntu kernel: [22473.061145] compiz.real[6185] trap stack segment ip:4101ae sp:7fffc4e87cb0 error:0
Oct 12 02:48:48 ubuntu kernel: [22484.561100] usplash[18500] general protection ip:7f9940b16333 sp:7fff48f9b690 error:0 in libusplash.so.0[7f9940aff000+31000]
Oct 12 02:48:53 ubuntu kernel: [22489.419164] ip6_tables: (C) 2000-2006 Netfilter Core Team

This happens on jaunty as well, as shown on duplicate bug 322713
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: usplash 0.5.27

"Me too", just reported by Apport. I think this happened on shutdown.

Ubuntu 8.10, AMD 64, fully up-to-date, kernel 2.6.27-11-generic
Non-Ubuntu software installed: VirtualBox 2.1.4

syslog:
Feb 18 22:48:35 michael-tp-ubuntu init: tty4 main process (4842) killed by TERM signal
Feb 18 22:48:35 michael-tp-ubuntu init: tty5 main process (4843) killed by TERM signal
Feb 18 22:48:35 michael-tp-ubuntu init: tty2 main process (4850) killed by TERM signal
Feb 18 22:48:35 michael-tp-ubuntu init: tty3 main process (4851) killed by TERM signal
Feb 18 22:48:35 michael-tp-ubuntu init: tty6 main process (4852) killed by TERM signal
Feb 18 22:48:35 michael-tp-ubuntu init: tty1 main process (6461) killed by TERM signal
Feb 18 22:48:35 michael-tp-ubuntu vpnc[9434]: select: Interrupted system call
Feb 18 22:48:35 michael-tp-ubuntu NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Feb 18 22:48:35 michael-tp-ubuntu NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Feb 18 22:48:35 michael-tp-ubuntu NetworkManager: <info> (tun0): writing resolv.conf to /sbin/resolvconf
Feb 18 22:48:35 michael-tp-ubuntu vpnc[9434]: terminated by signal: 15
Feb 18 22:48:37 michael-tp-ubuntu NetworkManager: <info> (wlan0): removing resolv.conf from /sbin/resolvconf
Feb 18 22:48:37 michael-tp-ubuntu avahi-daemon[5288]: Withdrawing address record for 192.168.178.30 on wlan0.
Feb 18 22:48:37 michael-tp-ubuntu avahi-daemon[5288]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.178.30.
Feb 18 22:48:37 michael-tp-ubuntu avahi-daemon[5288]: Interface wlan0.IPv4 no longer relevant for mDNS.
Feb 18 22:48:37 michael-tp-ubuntu avahi-daemon[5288]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.178.30.
Feb 18 22:48:37 michael-tp-ubuntu avahi-daemon[5288]: New relevant interface wlan0.IPv4 for mDNS.
Feb 18 22:48:37 michael-tp-ubuntu avahi-daemon[5288]: Registering new address record for 192.168.178.30 on wlan0.IPv4.
Feb 18 22:48:38 michael-tp-ubuntu kernel: [59357.155289] mtrr: no MTRR for e0000000,7f00000 found
Feb 18 22:48:38 michael-tp-ubuntu NetworkManager: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
Feb 18 22:48:38 michael-tp-ubuntu NetworkManager: <info> Policy set 'Auto fritz.box' (wlan0) as default for routing and DNS.
Feb 18 22:48:38 michael-tp-ubuntu NetworkManager: <info> (wlan0): writing resolv.conf to /sbin/resolvconf
Feb 18 22:48:38 michael-tp-ubuntu NetworkManager: <info> Policy set 'Auto fritz.box' (wlan0) as default for routing and DNS.
Feb 18 22:48:38 michael-tp-ubuntu kernel: [59357.373747] usplash[25622] general protection ip:7fa653f77333 sp:7fff5c3fbb10 error:0 in libusplash.so.0[7fa653f60000+31000]
Feb 18 22:48:38 michael-tp-ubuntu nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.
Feb 18 22:48:47 michael-tp-ubuntu avahi-daemon[5288]: Got SIGTERM, quitting.
Feb 18 22:48:47 michael-tp-ubuntu avahi-daemon[5288]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.178.30.
Feb 18 22:48:48 michael-tp-ubuntu exiting on signal 15

kern.log...

I've nominated it for Jaunty.
The developers won't probably fix this, usplash will be replaced by
plymouth in the near future (ubuntu 9.10?)

I've been wondering for ages why Ubuntu insisted on putting scarce manpower into a home-grown bootsplash. Now they are suddenly doing lots of the things I have always thought they should :)

This error and report was generated for me on BOOTING of Jaunty 9.04 64bit Beta
Zeddock

The same problem (Ubuntu 9.04 beta; usplash 0.5.31)

error continues

zeddock

If I manually update initrd (for exmpl. with: sudo update-initramfs -c -k all), no bug is present. But after update (which?) bug come again.

Re-started Jaunty 9.04 Development

2.6.28-11-generic #41-Ubuntu SMP Wed Apr 8 04:39:23 UTC 2009 x86_64 GNU/Linux

Have never seen this crash before...

same as kylea, received this for the first time today w/ jaunty 2.6.28-11

Apport just reported the same thing for me too

This is still an issue in current Jaunty.

I confirm it. Usually usplash doesn't run at on my Jaunty x64.

This still seems to be an issue in current Jaunty.

Linux Linux 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009 x86_64 GNU/Linux

I get this error on every start if I enable Apport.