plymouthd crashed with SIGSEGV in ply_list_insert_node()

Bug #1162089 reported by Dimitri John Ledkov
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I was playing around with plymouth-x11, like one should on a friday evening =)

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Thu Mar 28 20:11:44 2013
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2012-01-12 (442 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-15-generic root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro quiet splash vt.handoff=7
ProcCmdline: @lymouthd --tty=/dev/pts/12
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-15-generic root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f83905794e3 <ply_list_insert_data+51>: mov 0x10(%rbx),%rdx
 PC (0x7f83905794e3) ok
 source "0x10(%rbx)" (0x441f0f66e70f) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ply_list_insert_data () from /lib/x86_64-linux-gnu/libply.so.2
 ply_trigger_pull () from /lib/x86_64-linux-gnu/libply.so.2
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libply-splash-core.so.2
 ?? () from /lib/x86_64-linux-gnu/plymouth/renderers/x11.so
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_list_insert_data()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: utah
dmi.bios.date: 10/24/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F16
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77X-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF16:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :
information type: Private → Public
Changed in plymouth (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ply_list_insert_node (new_node=0x27b06f0, node_before=0x441f0f66e6ff, list=0x7f838e36dca0 <g_idle_dispatch>) at ply-list.c:140
 ply_list_insert_data (list=0x7f838e36dca0 <g_idle_dispatch>, data=0x27a9fb0, node_before=0x441f0f66e6ff) at ply-list.c:162
 ply_trigger_pull (trigger=0x27bbe80, data=0x25eda80) at ply-trigger.c:167
 on_enter (state=0x7fff80520b80, line=0x26a63d0 "asf") at main.c:1484
 process_keyboard_input (character_size=1, keyboard_input=0x27aefe0 "\n", keyboard=0x26a6360) at ply-keyboard.c:238

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
summary: - plymouthd crashed with SIGSEGV in ply_list_insert_data()
+ plymouthd crashed with SIGSEGV in ply_list_insert_node()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
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.