xfdesktop crashed with SIGSEGV

Bug #1816245 reported by David Kastrup on 2019-02-16
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfdesktop4 (Ubuntu)
Undecided
Unassigned

Bug Description

Upon waking up computer from sleep.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: xfdesktop4 4.13.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-12.13-lowlatency 4.19.18
Uname: Linux 4.19.0-12-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CrashCounter: 1
CurrentDesktop: XFCE
Date: Sat Feb 16 15:34:36 2019
ExecutablePath: /usr/bin/xfdesktop
InstallationDate: Installed on 2011-10-14 (2682 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011)
ProcCmdline: xfdesktop --display :0.0 --sm-client-id 2f1767d95-cd68-4ef9-8cc1-b6f11f43976c
Signal: 11
SourcePackage: xfdesktop4
Stacktrace:
 #0 0x00007f0fcae59505 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #1 0x00007f0fcae39a1e in g_object_get () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #2 0x00007f0fbc007840 in ()
 #3 0x00007f0fcad4f780 in g_source_get_context () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #4 0x0000000000000000 in ()
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_get () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ()
 g_source_get_context () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ()
Title: xfdesktop crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout fax floppy lpadmin lxd plugdev pulse-access sambashare

David Kastrup (dak) wrote :
information type: Private → Public

StacktraceSource:
 #0 0x00007f0fcae59505 in ?? () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #1 0x00007f0fcae39a1e in g_object_get () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 #2 0x00007f0fbc007840 in ?? ()
 #3 0x00007f0fcad4f780 in g_source_get_context () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 #4 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_get () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 g_source_get_context () from /tmp/apport_sandbox_ter90rro/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace

Is this crash still reproducible? Does it affect version 4.13.3?

David Kastrup (dak) wrote :

Random crashes are _never_ reproducible. I report those as I encounter them but often are thwarted by the bug reporting system telling me that this bug has already been reported and I can add information to it but then redirects me to a bug page that refuses to let me view/access anything because it is marked as containing private information.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints