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

2018-08-10 Thread Bug Watch Updater 
Launchpad has imported 6 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=104791.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-01-25T16:18:01+00:00 Cristian Aravena Romero wrote:

Hello,

Open bug in Launchpad.net
https://bugs.launchpad.net/bugs/1745406

"I do not know why this happened"


BackTrace:
#0  script_obj_deref_direct (obj=0x0) at ./script-object.c:133
No locals.
#1  0x7faef226f6ff in script_obj_as_custom (obj=, 
user_func=user_func@entry=0x7faef226ef70 , 
user_data=user_data@entry=0x7ffc11c15b10) at ./script-object.c:242
reply = 
#2  0x7faef226ecac in script_execute_object_with_parlist 
(parameter_data=0x55ba4b4f7600, this=0x0, obj=, 
state=0x55ba4b3dd390) at ./script-execute.c:287
execute_data = {state = 0x55ba4b3dd390, this = 0x0, parameter_data = 
0x55ba4b4f7600}
execute_data = 
#3  script_execute_object (state=0x55ba4b3dd390, function=, 
this=this@entry=0x0, first_arg=first_arg@entry=0x0) at ./script-execute.c:649
reply = 
args = {{gp_offset = 32, fp_offset = 21946, overflow_arg_area = 
0x7ffc11c15bb0, reg_save_area = 0x7ffc11c15b50}}
arg = 
parameter_data = 0x55ba4b4f7600
#4  0x7faef2272be3 in script_lib_plymouth_on_display_normal 
(state=, data=) at ./script-lib-plymouth.c:289
ret = 
#5  0x7faef226ba42 in display_normal (plugin=0x55ba4b3dd2a0) at 
./plugin.c:473
No locals.
#6  0x7faef4459101 in create_text_displays_for_terminal 
(terminal=0x55ba4b3d1c10, manager=0x55ba4b3d1a70) at ply-device-manager.c:658
display = 0x55ba4b4f3780
display = 
_old_errno = 
_old_errno = 
#7  create_devices_for_terminal_and_renderer_type (manager=0x55ba4b3d1a70, 
device_path=, terminal=0x55ba4b3d1c10, renderer_type=) at ply-device-manager.c:735
renderer = 
keyboard = 0x55ba4b446de0
__func__ = "create_devices_for_terminal_and_renderer_type"
#8  0x7faef4670e32 in ply_event_loop_handle_timeouts (loop=0x55ba4b3ca3a0) 
at ply-event-loop.c:1192
next_node = 
watch = 0x55ba4b3d1990
node = 0x55ba4b3e75d0
now = 10.590881546
node = 
now = 
next_node = 
watch = 
#9  ply_event_loop_process_pending_events (loop=loop@entry=0x55ba4b3ca3a0) at 
ply-event-loop.c:1251
timeout = 
number_of_received_events = 0
i = 
events = {{events = 4294967295, data = {ptr = 0x, fd = 
-1, u32 = 4294967295, u64 = 18446744073709551615}} }
__PRETTY_FUNCTION__ = "ply_event_loop_process_pending_events"
#10 0x7faef4671480 in ply_event_loop_run (loop=0x55ba4b3ca3a0) at 
ply-event-loop.c:1310
No locals.
#11 0x55ba49be1514 in main (argc=4, argv=0x7ffc11c16f58) at main.c:2390
state = {loop = 0x55ba4b3ca3a0, boot_server = 0x55ba4b3cce70, 
boot_splash = 0x55ba4b3d6b10, session = 0x55ba4b3ce1a0, boot_buffer = 
0x55ba4b3cd170, progress = 0x55ba4b3d17a0, keystroke_triggers = 0x55ba4b3cbdc0, 
entry_triggers = 0x55ba4b3cbde0, entry_buffer = 0x55ba4b3cbe00, messages = 
0x55ba4b3cce50, command_parser = 0x55ba4b3ca260, mode = PLY_MODE_BOOT, 
local_console_terminal = 0x55ba4b3d1c10, device_manager = 0x55ba4b3d1a70, 
deactivate_trigger = 0x0, quit_trigger = 0x0, start_time = 5.43730001, 
splash_delay = nan(0x8), device_timeout = 5, kernel_command_line = 
"BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7\n", '\000' , kernel_command_line_is_set 
= 1, no_boot_log = 0, showing_details = 0, system_initialized = 1, 
is_redirected = 0, is_attached = 0, should_be_attached = 1, 
should_retain_splash = 0, is_inactive = 1, is_shown = 1, should_force_details = 
0, override_splash_path = 0x0, system_default_splash_path = 0x0, 
distribution_default_splash_path = 0x0, default_tty = 0x55ba49bebcff 
"/dev/tty1", number_of_errors = 0, pending_messages = 0x55ba4b3cce30}
exit_code = 
should_help = false
no_boot_log = false
no_daemon = false
debug = false
attach_to_session = true
daemon_handle = 
mode_string = 0x55ba4b3cac30 "p\254
__func__ = "main"


Regards,
--
Cristian

Reply at:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1745406/comments/6


On 2018-01-25T16:55:19+00:00 T-freedesktop wrote:

Are you running a custom theme? If so could you supply the .script
component of it?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1745406/comments/7


On

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

2018-05-01 Thread Francis Ginther 
** Tags added: id-5ae73e3eeb6dee8e1438bb11

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-19 Thread Marcos Nascimento 
When this problem occurs, the mouse on the logon screen does not appear.
I haven't tested the PPA yet. Log file:


** Attachment added: "plymouth-debug.log"
   
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1745406/+attachment/5122441/+files/plymouth-debug.log

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-19 Thread Launchpad Bug Tracker 
This bug was fixed in the package plymouth - 0.9.3-1ubuntu7

---
plymouth (0.9.3-1ubuntu7) bionic; urgency=medium

  * debian/patches/misc-changes.patch: Drop call to stop_animation as it would
unreference a bunch of variables and may cause a crash writing a NULL VMA.
(LP: #1745406)

 -- Brian Murray   Thu, 12 Apr 2018 17:07:36 -0700

** Changed in: plymouth (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-16 Thread Brian Murray 
The crash in the Error Tracker for this can be found here:

https://errors.ubuntu.com/problem/ca24c0c94ac60ac9ca8da3a4ff28dd1fda0b7100

** Changed in: plymouth (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: plymouth (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-16 Thread Andrea Azzarone 
After installing plymouth from the above ppa I don't get the crash
anymore.

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-14 Thread Jeroen Donkervoort 
Same here, added the ppa, been rebooting and shutting down and no mention
anymore of this error.

2018-04-14 3:47 GMT+02:00 Adam Carter <1745...@bugs.launchpad.net>:

> No longer experienced
>
> On Fri., 13 Apr. 2018, 3:51 am Brian Murray,  wrote:
>
> > Does this happen to anybody on a regular basis? Would you be able to
> > test a package from a PPA and confirm that the crash is no longer
> > happening?
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1762146).
> > https://bugs.launchpad.net/bugs/1745406
> >
> > Title:
> >   plymouthd crashed with SIGSEGV in script_obj_deref_direct()
> >
> > Status in Plymouth:
> >   In Progress
> > Status in plymouth package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   Hello,
> >
> >   I do not know why this happened
> >
> >   Regards,
> >   --
> >   Cristian
> >
> >   ProblemType: Crash
> >   DistroRelease: Ubuntu 18.04
> >   Package: plymouth 0.9.3-1ubuntu1
> >   Uname: Linux 4.15.0-041500rc9-generic x86_64
> >   ApportVersion: 2.20.8-0ubuntu6
> >   Architecture: amd64
> >   Date: Thu Jan 25 09:05:56 2018
> >   DefaultPlymouth:
> > /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
> >   ExecutablePath: /sbin/plymouthd
> >   ExecutableTimestamp: 1516196236
> >   InstallationDate: Installed on 2017-10-13 (103 days ago)
> >   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> > (20170926)
> >   MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
> >   ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic
> > root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@
> quiet
> > splash vt.handoff=7
> >   ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid
> > --attach-to-session
> >   ProcCwd: /
> >   ProcEnviron:
> >LANG=es_CL.UTF-8
> >LANGUAGE=es_CL:es
> >PATH=(custom, no user)
> >   ProcFB: 0 inteldrmfb
> >   ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic
> > root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@
> quiet
> > splash vt.handoff=7
> >   SegvAnalysis:
> >Segfault happened at: 0x7faef226f480 :
> > cmpl   $0x1,(%rdi)
> >PC (0x7faef226f480) ok
> >source "$0x1" ok
> >destination "(%rdi)" (0x) not located in a known VMA region
> > (needed writable region)!
> >   SegvReason: writing NULL VMA
> >   Signal: 11
> >   SourcePackage: plymouth
> >   StacktraceTop:
> >script_obj_deref_direct () at
> > /usr/lib/x86_64-linux-gnu/plymouth/script.so
> >script_obj_as_custom () at /usr/lib/x86_64-linux-gnu/
> plymouth/script.so
> >script_execute_object () at /usr/lib/x86_64-linux-gnu/
> plymouth/script.so
> >script_lib_plymouth_on_display_normal () at
> > /usr/lib/x86_64-linux-gnu/plymouth/script.so
> >() at /usr/lib/x86_64-linux-gnu/plymouth/script.so
> >   TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-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/15/2013
> >   dmi.bios.vendor: Phoenix Technologies Ltd.
> >   dmi.bios.version: P14AAJ
> >   dmi.board.asset.tag: Base Board Asset Tag
> >   dmi.board.name: SAMSUNG_NP1234567890
> >   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
> >   dmi.board.version: FAB1
> >   dmi.chassis.asset.tag: No Asset Tag
> >   dmi.chassis.type: 9
> >   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
> >   dmi.chassis.version: 0.1
> >   dmi.modalias:
> > dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:
> svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:
> rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:
> cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
> >   dmi.product.family: ChiefRiver System
> >   dmi.product.name: 530U3C/530U4C
> >   dmi.product.version: 0.1
> >   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/plymouth/+bug/1745406/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1761948).
> https://bugs.launchpad.net/bugs/1745406
>
> Title:
>   plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>
> Status in Plymouth:
>   In Progress
> Status in plymouth package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Hello,
>
>   I do not know why this happened
>
>   Regards,
>   --
>   Cristian
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: plymouth 0.9.3-1ubuntu1
>   Uname: Linux 4.15.0-041500rc9-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu6
>   Architecture: amd64
>   Date: Thu Jan 25 09:05:56 2018
>   DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.
> plymouth
>   ExecutablePath: /sbin/plymouthd
>   ExecutableTimestamp: 1516196236
>   InstallationDate: Installed on 2017-10-13 (103 days ago)
>

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

2018-04-13 Thread Adam Carter 
No longer experienced

On Fri., 13 Apr. 2018, 3:51 am Brian Murray,  wrote:

> Does this happen to anybody on a regular basis? Would you be able to
> test a package from a PPA and confirm that the crash is no longer
> happening?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1762146).
> https://bugs.launchpad.net/bugs/1745406
>
> Title:
>   plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>
> Status in Plymouth:
>   In Progress
> Status in plymouth package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Hello,
>
>   I do not know why this happened
>
>   Regards,
>   --
>   Cristian
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: plymouth 0.9.3-1ubuntu1
>   Uname: Linux 4.15.0-041500rc9-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu6
>   Architecture: amd64
>   Date: Thu Jan 25 09:05:56 2018
>   DefaultPlymouth:
> /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
>   ExecutablePath: /sbin/plymouthd
>   ExecutableTimestamp: 1516196236
>   InstallationDate: Installed on 2017-10-13 (103 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170926)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
>   ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic
> root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet
> splash vt.handoff=7
>   ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid
> --attach-to-session
>   ProcCwd: /
>   ProcEnviron:
>LANG=es_CL.UTF-8
>LANGUAGE=es_CL:es
>PATH=(custom, no user)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic
> root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet
> splash vt.handoff=7
>   SegvAnalysis:
>Segfault happened at: 0x7faef226f480 :
> cmpl   $0x1,(%rdi)
>PC (0x7faef226f480) ok
>source "$0x1" ok
>destination "(%rdi)" (0x) not located in a known VMA region
> (needed writable region)!
>   SegvReason: writing NULL VMA
>   Signal: 11
>   SourcePackage: plymouth
>   StacktraceTop:
>script_obj_deref_direct () at
> /usr/lib/x86_64-linux-gnu/plymouth/script.so
>script_obj_as_custom () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
>script_execute_object () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
>script_lib_plymouth_on_display_normal () at
> /usr/lib/x86_64-linux-gnu/plymouth/script.so
>() at /usr/lib/x86_64-linux-gnu/plymouth/script.so
>   TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-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/15/2013
>   dmi.bios.vendor: Phoenix Technologies Ltd.
>   dmi.bios.version: P14AAJ
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: SAMSUNG_NP1234567890
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: FAB1
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.chassis.version: 0.1
>   dmi.modalias:
> dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
>   dmi.product.family: ChiefRiver System
>   dmi.product.name: 530U3C/530U4C
>   dmi.product.version: 0.1
>   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/plymouth/+bug/1745406/+subscriptions
>

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-13 Thread Dominique Meeùs 
(From Bug 1762022)
I did add the ppa to my sources list and installed the new version.
I did not have a crash at startup since (but I am not sure to have had one 
every time).

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-12 Thread Brian Murray 
I've uploaded a version of plymouth for bionic to test with to my PPA.

https://launchpad.net/~brian-murray/+archive/ubuntu/ppa

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-12 Thread Adam Carter 
Yeah every login after boot

On Fri., 13 Apr. 2018, 5:01 am Jeroen Donkervoort, <
1745...@bugs.launchpad.net> wrote:

> Hi,
>
> It happens almost every day, so testing won't be a problem.
>
> Regards,
>
> Jeroen
>
>
> Op do 12 apr. 2018 19:51 schreef Brian Murray :
>
> > Does this happen to anybody on a regular basis? Would you be able to
> > test a package from a PPA and confirm that the crash is no longer
> > happening?
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1761948).
> > https://bugs.launchpad.net/bugs/1745406
> >
> > Title:
> >   plymouthd crashed with SIGSEGV in script_obj_deref_direct()
> >
> > Status in Plymouth:
> >   In Progress
> > Status in plymouth package in Ubuntu:
> >   Confirmed
> >
> > Bug description:
> >   Hello,
> >
> >   I do not know why this happened
> >
> >   Regards,
> >   --
> >   Cristian
> >
> >   ProblemType: Crash
> >   DistroRelease: Ubuntu 18.04
> >   Package: plymouth 0.9.3-1ubuntu1
> >   Uname: Linux 4.15.0-041500rc9-generic x86_64
> >   ApportVersion: 2.20.8-0ubuntu6
> >   Architecture: amd64
> >   Date: Thu Jan 25 09:05:56 2018
> >   DefaultPlymouth:
> > /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
> >   ExecutablePath: /sbin/plymouthd
> >   ExecutableTimestamp: 1516196236
> >   InstallationDate: Installed on 2017-10-13 (103 days ago)
> >   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> > (20170926)
> >   MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
> >   ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic
> > root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@
> quiet
> > splash vt.handoff=7
> >   ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid
> > --attach-to-session
> >   ProcCwd: /
> >   ProcEnviron:
> >LANG=es_CL.UTF-8
> >LANGUAGE=es_CL:es
> >PATH=(custom, no user)
> >   ProcFB: 0 inteldrmfb
> >   ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic
> > root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@
> quiet
> > splash vt.handoff=7
> >   SegvAnalysis:
> >Segfault happened at: 0x7faef226f480 :
> > cmpl   $0x1,(%rdi)
> >PC (0x7faef226f480) ok
> >source "$0x1" ok
> >destination "(%rdi)" (0x) not located in a known VMA region
> > (needed writable region)!
> >   SegvReason: writing NULL VMA
> >   Signal: 11
> >   SourcePackage: plymouth
> >   StacktraceTop:
> >script_obj_deref_direct () at
> > /usr/lib/x86_64-linux-gnu/plymouth/script.so
> >script_obj_as_custom () at
> /usr/lib/x86_64-linux-gnu/plymouth/script.so
> >script_execute_object () at
> /usr/lib/x86_64-linux-gnu/plymouth/script.so
> >script_lib_plymouth_on_display_normal () at
> > /usr/lib/x86_64-linux-gnu/plymouth/script.so
> >() at /usr/lib/x86_64-linux-gnu/plymouth/script.so
> >   TextPlymouth:
> /usr/share/plymouth/themes/ubuntu-text/ubuntu-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/15/2013
> >   dmi.bios.vendor: Phoenix Technologies Ltd.
> >   dmi.bios.version: P14AAJ
> >   dmi.board.asset.tag: Base Board Asset Tag
> >   dmi.board.name: SAMSUNG_NP1234567890
> >   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
> >   dmi.board.version: FAB1
> >   dmi.chassis.asset.tag: No Asset Tag
> >   dmi.chassis.type: 9
> >   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
> >   dmi.chassis.version: 0.1
> >   dmi.modalias:
> >
> dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
> >   dmi.product.family: ChiefRiver System
> >   dmi.product.name: 530U3C/530U4C
> >   dmi.product.version: 0.1
> >   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/plymouth/+bug/1745406/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1762146).
> https://bugs.launchpad.net/bugs/1745406
>
> Title:
>   plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>
> Status in Plymouth:
>   In Progress
> Status in plymouth package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Hello,
>
>   I do not know why this happened
>
>   Regards,
>   --
>   Cristian
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: plymouth 0.9.3-1ubuntu1
>   Uname: Linux 4.15.0-041500rc9-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu6
>   Architecture: amd64
>   Date: Thu Jan 25 09:05:56 2018
>   DefaultPlymouth:
> /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
>   ExecutablePath: /sbin/plymouthd
>   ExecutableTimestamp: 1516196236
>   InstallationDate: Installed on 2017-10-13 (103 days ago)
>

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

2018-04-12 Thread Jeroen Donkervoort 
Hi,

It happens almost every day, so testing won't be a problem.

Regards,

Jeroen


Op do 12 apr. 2018 19:51 schreef Brian Murray :

> Does this happen to anybody on a regular basis? Would you be able to
> test a package from a PPA and confirm that the crash is no longer
> happening?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1761948).
> https://bugs.launchpad.net/bugs/1745406
>
> Title:
>   plymouthd crashed with SIGSEGV in script_obj_deref_direct()
>
> Status in Plymouth:
>   In Progress
> Status in plymouth package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Hello,
>
>   I do not know why this happened
>
>   Regards,
>   --
>   Cristian
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: plymouth 0.9.3-1ubuntu1
>   Uname: Linux 4.15.0-041500rc9-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu6
>   Architecture: amd64
>   Date: Thu Jan 25 09:05:56 2018
>   DefaultPlymouth:
> /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
>   ExecutablePath: /sbin/plymouthd
>   ExecutableTimestamp: 1516196236
>   InstallationDate: Installed on 2017-10-13 (103 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170926)
>   MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
>   ProcCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic
> root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet
> splash vt.handoff=7
>   ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid
> --attach-to-session
>   ProcCwd: /
>   ProcEnviron:
>LANG=es_CL.UTF-8
>LANGUAGE=es_CL:es
>PATH=(custom, no user)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-041500rc9-generic
> root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet
> splash vt.handoff=7
>   SegvAnalysis:
>Segfault happened at: 0x7faef226f480 :
> cmpl   $0x1,(%rdi)
>PC (0x7faef226f480) ok
>source "$0x1" ok
>destination "(%rdi)" (0x) not located in a known VMA region
> (needed writable region)!
>   SegvReason: writing NULL VMA
>   Signal: 11
>   SourcePackage: plymouth
>   StacktraceTop:
>script_obj_deref_direct () at
> /usr/lib/x86_64-linux-gnu/plymouth/script.so
>script_obj_as_custom () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
>script_execute_object () at /usr/lib/x86_64-linux-gnu/plymouth/script.so
>script_lib_plymouth_on_display_normal () at
> /usr/lib/x86_64-linux-gnu/plymouth/script.so
>() at /usr/lib/x86_64-linux-gnu/plymouth/script.so
>   TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-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/15/2013
>   dmi.bios.vendor: Phoenix Technologies Ltd.
>   dmi.bios.version: P14AAJ
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: SAMSUNG_NP1234567890
>   dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.board.version: FAB1
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
>   dmi.chassis.version: 0.1
>   dmi.modalias:
> dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
>   dmi.product.family: ChiefRiver System
>   dmi.product.name: 530U3C/530U4C
>   dmi.product.version: 0.1
>   dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/plymouth/+bug/1745406/+subscriptions
>

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-12 Thread Andrea Azzarone 
I get this every login. I can test the ppa if it helps.

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-12 Thread Brian Murray 
Does this happen to anybody on a regular basis? Would you be able to
test a package from a PPA and confirm that the crash is no longer
happening?

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-03 Thread David 
On my system at least it seems to be causing a system wide error,
leaving the mouse as the only working device on the system, usually
about a minute or two after logged into gnome, using gdm.

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-03 Thread Tomasz 
Now It's crashed

** Attachment added: "plymouth-debug.log"
   
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1745406/+attachment/5100354/+files/plymouth-debug.log

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-03 Thread Tomasz 
Plymouth is crashing randomly on my machine.

I've tried to reboot three times but it doesn't want to crash :(


Here is my log - without crash but it contains few errors - maybe it will be 
helpful.

** Attachment added: "plymouth-debug.log"
   
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1745406/+attachment/5100346/+files/plymouth-debug.log

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-04-03 Thread Brian Murray 
It might be helpful to get some plymouth debug log files, you can have
plymouth run in debug mode by adding 'plymouth.debug' to
/etc/default/grub and then running sudo update-grub.  Here's what the
correct line in /etc/default/grub might look like.

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash plymouth.debug"

After rebooting and running plymouth in debug mode you'll have a log
file at '/var/log/plymouth-debug.log'. It'd be great if someone
experiencing the crash could attach that file to this bug.

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-02-24 Thread Apport retracing service 
** Tags added: bugpattern-needed

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-01-27 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: plymouth (Ubuntu)
   Status: New => Confirmed

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-01-25 Thread Bug Watch Updater 
** Changed in: plymouth
   Status: Unknown => In Progress

** Changed in: plymouth
   Importance: Unknown => Medium

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

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

2018-01-25 Thread Cristian Aravena Romero 
** Information type changed from Private to Public

** Bug watch added: freedesktop.org Bugzilla #104791
   https://bugs.freedesktop.org/show_bug.cgi?id=104791

** Also affects: plymouth via
   https://bugs.freedesktop.org/show_bug.cgi?id=104791
   Importance: Unknown
   Status: Unknown

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs