Ubuntu Mate 14.10 Beta 2 plymouthd error on bootup

Bug #1378284 reported by Christopher
174
This bug affects 27 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

untu Mate 14.10 Beta 2 plymouthd error on bootup. No further infomation.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: plymouth 0.9.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
Date: Tue Oct 7 05:29:32 2014
DefaultPlymouth: /lib/plymouth/themes/ubuntu-mate-logo/ubuntu-mate-logo.plymouth
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2014-09-26 (10 days ago)
InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - beta2 amd64 (20140925)
MachineType: TOSHIBA Satellite P50-A
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic.efi.signed root=UUID=2ae78306-0417-4c4c-b739-731a33003189 ro quiet splash vt.handoff=7
ProcCmdline: @sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic.efi.signed root=UUID=2ae78306-0417-4c4c-b739-731a33003189 ro quiet splash vt.handoff=7
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-mate-text/ubuntu-mate-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 04/23/2014
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.80
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: VG10ST
dmi.board.vendor: TOSHIBA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnTOSHIBA:bvr1.80:bd04/23/2014:svnTOSHIBA:pnSatelliteP50-A:pvrPSPMKU-04002Q:rvnTOSHIBA:rnVG10ST:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: Satellite P50-A
dmi.product.version: PSPMKU-04002Q
dmi.sys.vendor: TOSHIBA

Revision history for this message
Christopher (twowings) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ply_renderer_get_buffer_for_head (renderer=0x3ff0000000000000, head=0x0) at ply-renderer.c:328
 ply_pixel_display_draw_area (display=0x15faef0, x=347, y=316, width=21, height=21) at ply-pixel-display.c:144
 draw_area (data=0x15f7840, height=<optimized out>, width=<optimized out>, y=<optimized out>, x=<optimized out>) at ./script-lib-sprite.c:537
 script_lib_sprite_refresh (data=0x15f7840) at ./script-lib-sprite.c:837
 stop_script_animation (plugin=0x15f7250) at ./plugin.c:320

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
Changed in plymouth (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
tags: added: vivid
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
information type: Private → Public
tags: added: bugpattern-needed
Revision history for this message
Daniel (cdtenzi) wrote :

This fixes it:

sudo chown -R user:user /lib/plymouth

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 1378284] Re: Ubuntu Mate 14.10 Beta 2 plymouthd error on bootup

On Thu, Oct 29, 2015 at 04:01:05PM -0000, Daniel wrote:

> sudo chown -R user:user /lib/plymouth

That is absolutely not an appropriate fix for this bug.

Norbert (nrbrtx)
Changed in plymouth (Ubuntu):
status: Confirmed → Incomplete
tags: removed: utopic vivid
Steve Langasek (vorlon)
Changed in plymouth (Ubuntu):
status: Incomplete → 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.