xfdesktop crashed with SIGSEGV in xfce_desktop_refresh()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Xfce4 Desktop |
Fix Released
|
High
|
|||
xfdesktop4 (Ubuntu) |
Fix Released
|
Medium
|
Jackson Doak |
Bug Description
The crash occurred just after the login and when entering the desktop.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xfdesktop4 4.11.3-1ubuntu1
Uname: Linux 3.14.0-
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CurrentDesktop: XFCE
Date: Thu Feb 20 10:37:51 2014
ExecutablePath: /usr/bin/xfdesktop
InstallationDate: Installed on 2013-03-22 (334 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130311.1)
ProcCmdline: xfdesktop --display :0.0 --sm-client-id 24680e5d5-
SegvAnalysis:
Segfault happened at: 0xb7703a98 <xfce_desktop_
PC (0xb7703a98) ok
source "(%eax,%ebp,1)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfdesktop4
StacktraceTop:
xfce_desktop_
?? ()
?? () from /lib/i386-
g_main_
?? () from /lib/i386-
Title: xfdesktop crashed with SIGSEGV in xfce_desktop_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Related branches
- Dmitry Shachnev: Approve
- Ubuntu branches: Pending requested
-
Diff: 1819 lines (+1750/-0)8 files modified.pc/applied-patches (+1/-0)
.pc/git-fix-segfault-on-session-start.patch/src/xfce-desktop.c (+1695/-0)
.pc/xubuntu_improve-nautilus-interactions.patch/src/xfce-desktop.c (+4/-0)
.pc/xubuntu_set-accountsservice-user-bg.patch/src/xfce-desktop.c (+4/-0)
debian/changelog (+18/-0)
debian/patches/git-fix-segfault-on-session-start.patch (+23/-0)
debian/patches/series (+1/-0)
src/xfce-desktop.c (+4/-0)
Changed in xfdesktop4 (Ubuntu): | |
importance: | Undecided → Medium |
tags: | removed: need-i386-retrace |
Changed in xfdesktop4 (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in xfdesktop: | |
importance: | Unknown → High |
status: | Unknown → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.