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

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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from

2018-04-16 Thread Jeroen Donkervoort 
Same here, after I read this message, I changed my login settings to Ubuntu
on Wayland and never got this error again

2018-04-14 8:38 GMT+02:00 Per-Inge :

> I always get this bug when I start with an Xorg session. I started with
> a Wayland session and didn't get the bug.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1752815).
> https://bugs.launchpad.net/bugs/1748450
>
> Title:
>   gnome-shell crashed with SIGTRAP in _g_log_abort() from
>   g_log_default_handler() from default_log_handler(message="Connection
>   to xwayland lost") from g_logv() from g_log() from 
>
> Status in gnome-shell package in Ubuntu:
>   Triaged
> Status in gnome-shell source package in Bionic:
>   Triaged
>
> Bug description:
>   *** This is a duplicate of bug 1505409, but is being kept separate so
>   as to automatically collect duplicate reports since the stacktrace
>   signature has changed recently. Any resolution and discussion should
>   occur in bug 1505409. ***
>
>   See also:
>   https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988
> f78ecd0f95
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.26.2-0ubuntu2
>   ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
>   Uname: Linux 4.13.0-33-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu8
>   Architecture: amd64
>   CurrentDesktop: GNOME-Greeter:GNOME
>   Date: Thu Feb  8 23:50:23 2018
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   GsettingsChanges:
>
>   InstallationDate: Installed on 2016-03-21 (690 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64
> (20160307)
>   ProcCmdline: /usr/bin/gnome-shell
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/false
>   Signal: 5
>   SourcePackage: gnome-shell
>   StacktraceTop:
>() at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
>_XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>_XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
>() at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>   Title: gnome-shell crashed with signal 5
>   UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
>   UserGroups:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+
> bug/1748450/+subscriptions
>

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions

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

[Bug 1752066] [NEW] Grub won't install during first install

2018-02-27 Thread Jeroen Donkervoort 
Public bug reported:

Trying to install onto a ACER X3990 as dual boot. W10 is installed.
Ignored the UEFI warning. Installation stopped when GRUB was to be
installed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 27 12:47:34 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
ProcEnviron:
 LANGUAGE=nl_NL.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.1 ubuntu

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

Title:
  Grub won't install during first install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1752066/+subscriptions

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