xfce4-session crashed with SIGSEGV in g_slice_alloc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Xfce4 Session |
Fix Released
|
Medium
|
|||
xfce4-session (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned | ||
Saucy |
Fix Released
|
High
|
Unassigned |
Bug Description
SRU REQUEST
as per https:/
Originally written by https:/
[Impact]
End user impact:
XFCE session closes (due to segfault) without specific (or any) user action, unsaved work is lost, user needs to login again. Critical UX impact to XFCE users on at least Raring (there are reports that Quantal is affected, too).
Justification for backporting the fix to the stable release:
A tiny upstream patch is available:
http://
It has been packaged (no other changes) by Ricardo F. Teixeira, tested by several users who commented on the XFCE and Ubuntu bug trackers, and has been reviewed and approved by 7 of the Ubuntu community.
According to tests by users
[Test Case]
How to reproduce:
An exact trigger action is not known, reports state that the session will often fail faster if user starts and quits applications such as Firefox or Thunderbird, or adds / removes applets to/from or interacts with panel. On affected system with user interaction, the session process should fail after a maximum of 1 hour of use, though most likely it will take more like less than 10 minutes.
[Regression Potential]
My (limited) understanding is that the patch is minimally invasive. As discussed above, the patch is well tested and there are no reports, after (sometimes) weeks of use, that it would introduce new issues. Based on my (limited) understanding, there is no or neglegible regression potential involved.
[Other Info]
Upstream version 4.10.1 includes the patch, tagged on May 5: http://
Upstream version 4.10.1 has not been released, yet: http://
Please feel free to edit and take over theis SRU request if you feel more qualified to handle it (I don't feel very qualified myself). Please also note that I am unable to upload a patch to *-proposed.
----
Original bug report:
During normal operation, suddenly, without any particular reason, the session was restarted. The problem was repeated several times, even several times. Only now I was able to report a bug, because after each restart of the session, error reporting program was closed.
Podczas normalnej pracy, nagle, bez żadnej konkretnej przyczyny, sesja została zrestartowana. Problem powtarzał się wielokrotnie, nawet kilka razy. Dopiero teraz udalo mi się zgłosić błąd, gdyż po każdym restarcie sesji, program raportowania błędów był zamykany.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xfce4-session 4.10.0-2ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Thu Jan 24 21:34:23 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2013-01-13 (11 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130113)
MarkForUpload: True
ProcCmdline: xfce4-session
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f07ac55f5af <g_slice_
PC (0x7f07ac55f5af) ok
source "(%rbx)" (0xffffffff0000
destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: xfce4-session
StacktraceTop:
g_slice_alloc () from /lib/x86_
g_signal_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: xfce4-session crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Related branches
- Martin Pitt: Approve
- Dimitri John Ledkov: Approve
- Robert Sander (community): Approve
- Coya DeBrojara (community): Approve
- Kaio Donadelli (community): Approve
- Piotr Maliński (community): Approve
- Thomas Karcher (community): Approve (user experience)
- Moritz Naumann (community): Approve
-
Diff: 48 lines (+28/-0)3 files modifieddebian/changelog (+6/-0)
debian/patches/series (+1/-0)
debian/patches/xfsm-startup-random-crash.patch (+21/-0)
Changed in xfce4-session (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
description: | updated |
description: | updated |
tags: | added: errors-watch |
Changed in xfce4-session (Ubuntu Raring): | |
status: | Fix Committed → Fix Released |
Changed in xfce4-session (Ubuntu Raring): | |
status: | Fix Released → Fix Committed |
tags: |
added: verification-done removed: verification-needed |
Changed in xfce4-session: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
see:
https:/ /bugzilla. redhat. com/show_ bug.cgi? id=891113 /bugzilla. redhat. com/show_ bug.cgi? id=865539
https:/
there's backtraces there, also:
Additional info: chain_pop_ head xfce4-session
backtrace_rating: 4
cmdline: xfce4-session
crash_function: magazine_
executable: /usr/bin/
kernel: 3.7.1-1.fc19.x86_64
remote_result: NOTFOUND
uid: 1000
Truncated backtrace: chain_pop_ head at gslice.c:532 memory_ magazine1_ alloc at gslice.c:835 from_arg_ signature at dbus-gsignature .c:200 proxy_emit_ remote_ signal at dbus-gproxy.c:1777 proxy_manager_ filter at dbus-gproxy.c:1355
Thread no. 1 (9 frames)
#0 magazine_
#1 thread_
#2 g_slice_alloc at gslice.c:994
#3 g_array_sized_new at garray.c:198
#4 g_array_new at garray.c:170
#5 _dbus_gtypes_
#6 dbus_g_
#7 dbus_g_
#15 gtk_main at gtkmain.c:1257
The crashes seem somewhat random unfortunately. ;(