Ubuntu
xfdesktop4 package

xfdesktop crashed with SIGSEGV in xfce_desktop_refresh()

Bug #1284225 reported by Donald W Bauer on 2014-02-24

This bug report is a duplicate of: Bug #1282509: xfdesktop crashed with SIGSEGV in xfce_desktop_refresh(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xfdesktop4 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Have no idea whether this reported before, 80 chars is not enuf info when I know nothing

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xfdesktop4 4.11.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Feb 24 12:27:33 2014
ExecutablePath: /usr/bin/xfdesktop
InstallationDate: Installed on 2013-12-16 (70 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131215)
ProcCmdline: xfdesktop --display :0.0 --sm-client-id 24194df6d-0243-41bf-8e19-07a21ee42a2a
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fbd7443e659 <xfce_desktop_refresh+153>: mov (%rax,%r12,1),%rdi
PC (0x7fbd7443e659) ok
source "(%rax,%r12,1)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfdesktop4
StacktraceTop:
xfce_desktop_refresh ()
?? ()
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: xfdesktop crashed with SIGSEGV in xfce_desktop_refresh()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Donald W Bauer (dwbauer-p) wrote on 2014-02-24:

Dependencies.txt Edit (6.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2014-02-24: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1283728, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.