** Description changed:

+ SRU REQUEST
+ as per https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
+ Originally written by https://launchpad.net/~mnaumann
+ 
+ [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://git.xfce.org/xfce/xfce4-session/commit/?id=ab391138cacc62ab184a338e237c4430356b41f9
+    It has been packaged (no other changes) by Ricardo Teixas, 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://git.xfce.org/xfce/xfce4-session/tag/?id=xfce4-session-4.10.1
+ Upstream version 4.10.1 has not been released, yet: 
http://archive.xfce.org/xfce/4.10/src/
+ 
+ 
+ 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
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  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/xfce4-session
  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_DIR=<set>
-  LANG=pl_PL.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=pl_PL.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7f07ac55f5af <g_slice_alloc+223>:    mov    
(%rbx),%rax
-  PC (0x7f07ac55f5af) ok
-  source "(%rbx)" (0xffffffff00000000) not located in a known VMA region 
(needed readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7f07ac55f5af <g_slice_alloc+223>:    mov    
(%rbx),%rax
+  PC (0x7f07ac55f5af) ok
+  source "(%rbx)" (0xffffffff00000000) not located in a known VMA region 
(needed readable region)!
+  destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: xfce4-session
  StacktraceTop:
-  g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_signal_connect_data () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  ?? () from /usr/lib/libwnck-1.so.22
-  ?? () from /usr/lib/libwnck-1.so.22
-  ?? () from /usr/lib/libwnck-1.so.22
+  g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_signal_connect_data () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  ?? () from /usr/lib/libwnck-1.so.22
+  ?? () from /usr/lib/libwnck-1.so.22
+  ?? () from /usr/lib/libwnck-1.so.22
  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

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

Title:
  xfce4-session crashed with SIGSEGV in g_slice_alloc()

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-session/+bug/1104435/+subscriptions

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

Reply via email to