[Bug 927636] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Miguel Fiandor Gutiérrez]

I also get this error since long time ago, however is not always, it's
just sometimes. When it happens i'm not able to login. After i input
username+pw and click login it gets blocked and I can do nothing but
rebooting the bad way.

In my error report generated by Ubuntu I have the following:
   "plymouth error destination "(%rdi)"... not located in a known VMA region (needed writable region)!"
   "writing unknown VMA"

<- i'm not sure if this helps. To me seems a problem of timing of
loading something during the boot and login. However some users solve it
by changing permissions, so maybe is related to the above message that I
have read it happens when a process tries to access to RAM addresses is
not allowed to. Some users said to give 775 others 777, if 775 works,
maybe the key is the group writable permission.

The dependencies of plymouth seems long:
sudo apt-get remove --simulate plymouth
The following packages will be REMOVED:
  cryptsetup gdm lightdm mountall plymouth plymouth-label plymouth-theme-ubuntu-gnome-logo plymouth-theme-ubuntu-gnome-text plymouth-theme-ubuntu-logo plymouth-theme-ubuntu-text ubuntu-desktop ubuntu-gnome-desktop unity unity-greeter unity-tweak-tool upstart
  upstart-bin

Are any of this packages ran under a user account without permission to
fire plymouth?, moreover, does that account belong to a group that
actually has write permission on plymouth?. Why timing on logging
matters? (I do sometimes login smoothly and sometimes not).

Sorry, but i can go further on this, and these are the questions that
come to my head that might, might not, give a hint to someone else.

Cheers

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/927636

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

Status in Plymouth:
  Confirmed
Status in plymouth package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 12.04 LTS (development branch)

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: plymouth 0.8.2-2ubuntu28
  ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
  Uname: Linux 3.2.0-14-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  Date: Mon Feb  6 07:03:15 2012
  DefaultPlymouth: /lib/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth
  ExecutablePath: /sbin/plymouthd
  MachineType: Foxconn AMD HDZS01
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic root=UUID=0bb93586-7343-45bd-802b-03adbb46f430 ro quiet splash vt.handoff=7
  ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
  ProcEnviron: PATH=(custom, no user)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-14-generic root=UUID=0bb93586-7343-45bd-802b-03adbb46f430 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7effe6b50ea0 <script_obj_deref_direct>:	cmpl   $0x1,(%rdi)
   PC (0x7effe6b50ea0) ok
   source "$0x1" ok
   destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: plymouth
  StacktraceTop:
   script_obj_deref_direct () from /lib/plymouth/script.so
   script_obj_as_custom () from /lib/plymouth/script.so
   script_execute_object () from /lib/plymouth/script.so
   script_lib_plymouth_on_update_status () from /lib/plymouth/script.so
   ?? ()
  TextPlymouth: /lib/plymouth/themes/xubuntu-text/xubuntu-text.plymouth
  Title: plymouthd crashed with SIGSEGV in script_obj_deref_direct()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A93F1022
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: AHD1S
  dmi.board.vendor: Foxconn
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA93F1022:bd04/19/2011:svnFoxconn:pnAMDHDZS01:pvrTobefilledbyO.E.M.:rvnFoxconn:rnAHD1S:rvr:
  dmi.product.name: AMD HDZS01
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Foxconn

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/927636/+subscriptions