Ubuntu
plymouth package

plymouth segfault with nvidia graphics

Bug #499541 reported by Per Ångström
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: plymouth

Upon inspection of dmesg, I ran across the following:

[ 13.403220] type=1505 audit(1261505409.431:9): operation="profile_replace" pid=960 name="/usr/lib/connman/scripts/dhclient-script"
[ 13.414081] type=1505 audit(1261505409.441:10): operation="profile_load" pid=962 name="/usr/bin/evince"
[ 13.432813] plymouthd[344]: segfault at 10 ip 00007f44649ec704 sp 00007ffff618d230 error 4 in libplybootsplash.so.2 (deleted [7f44649de000+14000]
[ 13.461301] iwlagn 0000:06:00.0: loaded firmware version 228.61.2.24
[ 13.712340] Registered led device: iwl-phy0::radio

ProblemType: Bug
Architecture: amd64
Date: Tue Dec 22 19:11:41 2009
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: plymouth 0.8.0~-5
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-9.13-generic
SourcePackage: plymouth
Tags: lucid
Uname: Linux 2.6.32-9-generic x86_64

Revision history for this message
Per Ångström (autark) wrote :
Revision history for this message
Per Ångström (autark) wrote :

Attaching dmesg output.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Could you supply "lspci -vvnn" output?

Changed in plymouth (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
summary: - [lucid] segmentation fault in plymouthd (libplybootsplash.so)
+ segmentation fault in plymouthd (libplybootsplash.so)
Revision history for this message
Per Ångström (autark) wrote : Re: segmentation fault in plymouthd (libplybootsplash.so)

Attaching "lspci -vvnn" output.

Changed in plymouth (Ubuntu):
status: Incomplete → New
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Thanks, I see you have an NVIDIA graphics card. This segfault is known, I think it's to do with the DRM renderer not cleaning up when it can't use the device.

summary: - segmentation fault in plymouthd (libplybootsplash.so)
+ plymouth segfault with nvidia graphics
Changed in plymouth (Ubuntu):
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package plymouth - 0.8.0~-6

---------------
plymouth (0.8.0~-6) lucid; urgency=low

  * Revert change in 0.8.0~-4 that scans the buffer out fo fbcon when
    deactivating i915; this was actually wrong, we don't want to use fbcon
    for the transition, we want to use our current framebuffer instead.
    Other bugs (with the VT code) are preventing that transition from working.
  * Fix a crash on "plymouth deactivate" when no renderer is active.
    LP: #499541.
  * Fix a crash on "plymouth deactivate" when --show-splash has never
    been called.
  * Fix failure to quit on "plymouth quit" after "plymouth deactivate".

  * Remove the code that disables plymouth when init= is on the command-line,
    we don't want that.

  * debian/initramfs-tools/scripts/init-top/plymouth:
    - Don't check the kernel command-line; we always want plymouth running
      whether or not "splash" is present, plymouth uses that to determine
      which of the graphics or text renderers to use.
    - Start with --attach-to-session so we redirect console messages.
  * debian/plymouth.plymouth-log.upstart:
    - Once the filesystem is mounted, flush the log out.
 -- Scott James Remnant <email address hidden> Wed, 23 Dec 2009 03:54:42 +0000

Changed in plymouth (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.