plymouthd crashed with SIGSEGV

Bug #1445594 reported by Patrizio Bruno
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

plymouth crashed at boot time

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: plymouth 0.9.0-0ubuntu9
ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
Uname: Linux 3.19.0-14-generic x86_64
ApportVersion: 2.17.1-0ubuntu2
Architecture: amd64
Date: Fri Apr 17 19:42:14 2015
DefaultPlymouth: /lib/plymouth/themes/ubuntu-gnome-logo/ubuntu-gnome-logo.plymouth
Disassembly: => 0x1cc0: Cannot access memory at address 0x1cc0
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-04-21 (361 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: ASUSTeK Computer Inc. U36SD
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-14-generic root=UUID=7bc6bb21-b7f4-4d90-9091-1cc91c0b8e6b ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session
ProcEnviron:
 LANG=it_IT.UTF-8
 PATH=(custom, no user)
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-14-generic root=UUID=7bc6bb21-b7f4-4d90-9091-1cc91c0b8e6b ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x1cc0: Cannot access memory at address 0x1cc0
 PC (0x00001cc0) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ()
 ply_pixel_display_draw_area () at /lib/x86_64-linux-gnu/libply-splash-core.so.4
 script_lib_sprite_refresh () at /lib/x86_64-linux-gnu/plymouth/script.so
 () at /lib/x86_64-linux-gnu/plymouth/script.so
 () at /lib/x86_64-linux-gnu/plymouth/script.so
TextPlymouth: /lib/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth
Title: plymouthd crashed with SIGSEGV
UpgradeStatus: Upgraded to vivid on 2015-04-12 (5 days ago)
UserGroups:

dmi.bios.date: 09/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: U36SD.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: U36SD
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrU36SD.206:bd09/26/2011:svnASUSTeKComputerInc.:pnU36SD:pvr1.0:rvnASUSTeKComputerInc.:rnU36SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: U36SD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Patrizio Bruno (desertconsulting) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1378284, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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