xfce4-session crashed with SIGSEGV in g_slice_alloc()

[Coya DeBrojara]

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 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://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
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
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
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

[nirik (kevin-scrye)]

see:

https://bugzilla.redhat.com/show_bug.cgi?id=891113
https://bugzilla.redhat.com/show_bug.cgi?id=865539

there's backtraces there, also:

Additional info:
backtrace_rating: 4
cmdline: xfce4-session
crash_function: magazine_chain_pop_head
executable: /usr/bin/xfce4-session
kernel: 3.7.1-1.fc19.x86_64
remote_result: NOTFOUND
uid: 1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 magazine_chain_pop_head at gslice.c:532
 #1 thread_memory_magazine1_alloc at gslice.c:835
 #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_from_arg_signature at dbus-gsignature.c:200
 #6 dbus_g_proxy_emit_remote_signal at dbus-gproxy.c:1777
 #7 dbus_g_proxy_manager_filter at dbus-gproxy.c:1355
 #15 gtk_main at gtkmain.c:1257

The crashes seem somewhat random unfortunately. ;(

[nirik (kevin-scrye)]

Sadly this seems to be increasing in frequency. ;(

[ 62.155631] xfce4-session[1383]: segfault at ffffffff00000000 ip 00007fc6b041d1af sp 00007fff82a7d2d0 error 4 in libglib-2.0.so.0.3503.0[7fc6b03ba000+121000]
[ 142.221402] xfce4-session[2975]: segfault at ffffffff00000000 ip 00007fbb1a79a1af sp 00007fff9e20d060 error 4 in libglib-2.0.so.0.3503.0[7fbb1a737000+121000]
[ 364.454128] xfce4-session[4539]: segfault at ffffffff00000000 ip 00007f5533dee1af sp 00007fff56abfaa0 error 4 in libglib-2.0.so.0.3503.0[7f5533d8b000+121000]
[ 449.070814] xfce4-session[6348]: segfault at ffffffff00000000 ip 00007ff0be2321af sp 00007ffffc97c840 error 4 in libglib-2.0.so.0.3503.0[7ff0be1cf000+121000]
[14129.127767] xfce4-session[8108]: segfault at ffffffff00000000 ip 00007fc8b3bf11af sp 00007fff9e045610 error 4 in libglib-2.0.so.0.3503.0[7fc8b3b8e000+121000]
[36287.178871] xfce4-session[24893]: segfault at ffffffff00000000 ip 00007f5f41da91af sp 00007fffef96daf0 error 4 in libglib-2.0.so.0.3503.0[7f5f41d46000+121000]
[36530.389847] xfce4-session[20474]: segfault at ffffffff00000000 ip 00007f85d64321af sp 00007fffb58b4e60 error 4 in libglib-2.0.so.0.3503.0[7f85d63cf000+121000]
[36619.040731] xfce4-session[22293]: segfault at ffffffff00000000 ip 00007f942e4aa1af sp 00007fffe0b49a00 error 4 in libglib-2.0.so.0.3503.0[7f942e447000+121000]
[36679.058052] xfce4-session[23879]: segfault at ffffffff00000000 ip 00007eff2a46d82c sp 00007fff7e911230 error 4 in libglib-2.0.so.0.3503.0[7eff2a40b000+121000]
[37364.920335] xfce4-session[25400]: segfault at ffffffff00000000 ip 00007fb0266531af sp 00007fff323d39b0 error 4 in libglib-2.0.so.0.3503.0[7fb0265f0000+121000]

it's glib2-2.35.3

Happy to try any debugging or gathering more info.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[schollsky (schollsky)]

Same situation here. Last crash came up after adding a new starter icon for gedit in the program bar below and using it.

[Coya DeBrojara (coyadebrojara)]

The problem of abrupt closure (restart) the session was repeated. This time, while watching a movie on youtube. At the same time, with "xfce4-session", failure has been the "pidgin".

Problem z nagłym zamknięciem (restartem) sesji, powtórzył się. Tym razem podczas oglądania filmu na youtube. Jednocześnie z "xfce4-session", awarii uległ program "pidgin".

[steph wied (nebu1207)]

So and what can I do now about it? Please help, it's so annoying...

[Coya DeBrojara (coyadebrojara)]

I tried to run the "synaptic". At the same time talking on Skype. It's frustrating ...

Próbowałam uruchomić program "synaptic". Jednocześnie rozmawiałam przez Skype. To frustrujące...

[sdv (sean-devega)]

same here, it's done this 5 times. so annoying. I restarted and everything; still doing it on and off.

[Arnd Bergmann (arnd-arndb)]

I've tried replacing the ubuntu version of xfce4-session with a fresh git checkout (2bfcd87736), and I still see the same symptom.

[KALImar Franklin (kalimar999)]

As soon as Xubuntu/xfce came on..it crashed..Irritating

[nirik (kevin-scrye)]

Also, there's reports that 'G_SLICE=always-malloc G_DEBUG=gc-friendly' causes the crashes to go away.

So, possibly this is related to g_slice allocation?

Another possibly related backtrace/crash:

 #0 magazine_chain_pop_head at gslice.c:532
 #1 thread_memory_magazine1_alloc at gslice.c:835
 #2 g_slice_alloc at gslice.c:994
 #3 g_tree_node_new at gtree.c:139
 #4 g_tree_insert_internal at gtree.c:443
 #5 g_tree_replace at gtree.c:421
 #6 xfsm_properties_set_string at xfsm-properties.c:505
 #7 xfsm_properties_set_from_smprop at xfsm-properties.c:656
 #8 xfsm_client_merge_properties at xfsm-client.c:346
 #9 sm_set_properties at sm-layer.c:374

https://bugzilla.redhat.com/show_bug.cgi?id=927379

[Kostya Vasilyev (kmansoft)]

Possibly related to this:

https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1162855

First Thunar crashed, immediately afterwards I was logged out of XFCE.

[Greg Adams (adamsgn)]

It crashed immediately after opening both Transmission and Thunderbird but I was able to reopen them after logging back in with no issues thus far.

[Landry-o (landry-o)]

Not 100% sure if this is related or not, but since upgrading to glib 2.36 i'm seeing xfce4-session crashes upon logout, and also pointing at g_slice_alloc() :

(gdb) bt
#0 0x00000a6e0753386f in g_slice_alloc () from /usr/local/lib/libglib-2.0.so.3600.0
#1 0x00000a6e0c0c83ca in simple_add_entry () from /usr/local/lib/libxfce4util.so.3.0
#2 0x00000a6e0c0c900e in _xfce_rc_simple_parse () from /usr/local/lib/libxfce4util.so.3.0
#3 0x00000a6e0c0c7738 in xfce_rc_simple_open () from /usr/local/lib/libxfce4util.so.3.0
#4 0x00000a6bfa11702a in xfsm_manager_store_session () from /usr/local/bin/xfce4-session
#5 0x00000a6bfa118f67 in xfsm_manager_complete_saveyourself () from /usr/local/bin/xfce4-session

[Landry-o (landry-o)]

And it also seems G_SLICE=always-malloc G_DEBUG=gc-friendly mitigates this crash, session is properly saved in .cache/sessions.

[Vedran Rodic (vrodic)]

I confirm this bug, my machine is i5-3320M

[pqwoerituytrueiwoq (pqwoerituytrueiwoq)]

@vrodic
the i5-3320M is a mobile class processor (and a pretty nice one at that) not a laptop model number

[Ncopa (ncopa)]

Seems like this also happens on Alpine Linux, x86_64.

I got a backtrace with debugging symbols:
#0 magazine_chain_pop_head (magazine_chunks=magazine_chunks@entry=0xb1106203ae0) at gslice.c:532
#1 0x00006f3d2348e46f in thread_memory_magazine1_alloc (ix=<optimized out>, tmem=<optimized out>) at gslice.c:835
#2 g_slice_alloc (mem_size=mem_size@entry=48) at gslice.c:994
#3 0x00006f3d23768b7d in handler_new (after=0) at gsignal.c:575
#4 0x00006f3d2376beea in g_signal_connect_closure_by_id (instance=instance@entry=0xb11062504f0, signal_id=signal_id@entry=20, detail=detail@entry=0, closure=0xb110627f2e0, after=after@entry=0) at gsignal.c:2293
#5 0x00006f3d23be76ba in export_signals (object=0xb11062504f0, info_list=0xb110624e820) at dbus-gobject.c:2445
#6 dbus_g_connection_register_g_object (connection=0xb110622edf8, at_path=0xb110624a090 "/org/xfce/SessionClients/2df371776_0473_4ccf_9935_10cbdf179961", object=0xb11062504f0) at dbus-gobject.c:2824
#7 0x00000b11055bbc40 in xfsm_client_dbus_init (client=0xb11062504f0) at xfsm-client.c:446
#8 xfsm_client_set_initial_properties (client=client@entry=0xb11062504f0, properties=0xb110623fa40) at xfsm-client.c:254
#9 0x00000b11055c2dda in xfsm_manager_register_client (manager=0xb1106238000, client=client@entry=0xb11062504f0, previous_id=previous_id@entry=0x0) at xfsm-manager.c:914
#10 0x00000b11055ba798 in sm_register_client (sms_conn=<optimized out>, client_data=0xb11062504f0, previous_id=0x0) at sm-layer.c:213
#11 0x00006f3d26048895 in _SmsProcessMessage () from /usr/lib/libSM.so.6
#12 0x00006f3d25e3aa2c in IceProcessMessages () from /usr/lib/libICE.so.6
#13 0x00000b11055b963b in ice_process_messages (channel=<optimized out>, condition=<optimized out>, user_data=0xb1106275a80) at ice-layer.c:111
#14 0x00006f3d23475de8 in g_main_dispatch (context=0xb110622b990) at gmain.c:3054
#15 g_main_context_dispatch (context=context@entry=0xb110622b990) at gmain.c:3630
#16 0x00006f3d234760d3 in g_main_context_iterate (context=0xb110622b990, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3701
#17 0x00006f3d234765f4 in g_main_loop_run (loop=0xb110623c0a0) at gmain.c:3895
#18 0x00006f3d24d853b2 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#19 0x00000b11055b8eae in main (argc=1, argv=0x77b6789954d8) at main.c:308

Also, 'info locals' returns:

chunk = 0xffffffff00000000

[Ncopa (ncopa)]

Slightly different backtrace when running with G_SLICE=debug-blocks:

#0 magazine_chain_pop_head (magazine_chunks=magazine_chunks@entry=0x1debcaf5220) at gslice.c:532
#1 0x00006dfbe96a646f in thread_memory_magazine1_alloc (ix=<optimized out>, tmem=<optimized out>) at gslice.c:835
#2 g_slice_alloc (mem_size=mem_size@entry=40) at gslice.c:994
#3 0x00006dfbe96b37a2 in g_tree_node_new (key=key@entry=0x1debcb79b10, value=value@entry=0x1debcb79b70) at gtree.c:139
#4 0x00006dfbe96b3cf6 in g_tree_insert_internal (tree=0x1debcb06b20, key=0x1debcb79b10, value=0x1debcb79b70, replace=1) at gtree.c:488
#5 0x00006dfbe96b4357 in g_tree_replace (tree=<optimized out>, key=<optimized out>, value=<optimized out>) at gtree.c:421
#6 0x000001deb8c79e00 in xfsm_properties_set_string (properties=<optimized out>, property_name=<optimized out>, property_value=<optimized out>) at xfsm-properties.c:505
#7 0x000001deb8c7a517 in xfsm_properties_set_from_smprop (properties=properties@entry=0x1debcb06b50, sm_prop=sm_prop@entry=0x1debcb79880) at xfsm-properties.c:656
#8 0x000001deb8c71076 in xfsm_client_merge_properties (client=client@entry=0x1debcb4ecf0, props=props@entry=0x1debcb45ef0, num_props=num_props@entry=7) at xfsm-client.c:346
#9 0x000001deb8c6efde in sm_set_properties (sms_conn=<optimized out>, client_data=0x1debcb4ecf0, num_props=7, props=0x1debcb45ef0) at sm-layer.c:374
#10 0x00006dfbec261033 in _SmsProcessMessage () from /usr/lib/libSM.so.6
#11 0x00006dfbec052a2c in IceProcessMessages () from /usr/lib/libICE.so.6
#12 0x000001deb8c6e63b in ice_process_messages (channel=<optimized out>, condition=<optimized out>, user_data=0x1debcb292c0) at ice-layer.c:111
#13 0x00006dfbe968dde8 in g_main_dispatch (context=0x1debcb27850) at gmain.c:3054
#14 g_main_context_dispatch (context=context@entry=0x1debcb27850) at gmain.c:3630
#15 0x00006dfbe968e0d3 in g_main_context_iterate (context=0x1debcb27850, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3701
#16 0x00006dfbe968e5f4 in g_main_loop_run (loop=0x1debcb380d0) at gmain.c:3895
#17 0x00006dfbeaf9d3b2 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#18 0x000001deb8c6deae in main (argc=1, argv=0x70fa795642c8) at main.c:308

[Ncopa (ncopa)]

I managed to make it crash with G_SLICE=always-malloc. Here is the backtrace:

#0 0x000068d1014418bc in raise () from /lib/libc.so.0.9.32
#1 0x000068d10143d3b7 in abort () from /lib/libc.so.0.9.32
#2 0x000068d10143cc0a in ?? () from /lib/libc.so.0.9.32
#3 0x000068d10143beb4 in malloc () from /lib/libc.so.0.9.32
#4 0x000068d104491d7d in IceAcceptConnection () from /usr/lib/libICE.so.6
#5 0x00000d5e766bb6ac in ice_connection_accept (channel=<optimized out>, condition=<optimized out>, watch_data=0xd5e793bdc30) at ice-layer.c:178
#6 0x000068d101ad7de8 in g_main_dispatch (context=0xd5e793b0760) at gmain.c:3054
#7 g_main_context_dispatch (context=context@entry=0xd5e793b0760) at gmain.c:3630
#8 0x000068d101ad80d3 in g_main_context_iterate (context=0xd5e793b0760, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3701
#9 0x000068d101ad85f4 in g_main_loop_run (loop=0xd5e793c7a20) at gmain.c:3895
#10 0x000068d1033e73b2 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x00000d5e766bafae in main (argc=1, argv=0x731fe27ab898) at main.c:308
No symbol table info available.

[Ncopa (ncopa)]

I don't know if it is related but I also noticed this warning:

(xfce4-session.dbg:16977): GLib-WARNING **: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly.

It puzzles me because I have verified that SIGCHLD is not ignored and I patched out the waitpid() in the kde compat. I also grepped the libs that they don't do any waitpid().

[Stephen Wright (stephen-wright)]

Unable to open any file, or program without it crashing. Firefox seems to not be an issue, but everything else caused an instant crash and log out. Any ideas when this bug is likely to be resolved?

[Stephen Wright (stephen-wright)]

I switched my log-in session from Xubuntu to just running xforce and have not experienced a crash yet.

[Landry-o (landry-o)]

Another crash rooted in g_slice_alloc, this time during a regular session when launching a new app.

#0 0x00001e1fdc05186f in g_slice_alloc () from /usr/local/lib/libglib-2.0.so.3600.0
#1 0x00001e1fdc05fdfe in g_tree_node_new () from /usr/local/lib/libglib-2.0.so.3600.0
#2 0x00001e1fdc05ff0d in g_tree_insert_internal () from /usr/local/lib/libglib-2.0.so.3600.0
#3 0x00001e1dc901a3bf in xfsm_properties_set_from_smprop () from /usr/local/bin/xfce4-session
#4 0x00001e1dc90118f3 in xfsm_client_merge_properties () from /usr/local/bin/xfce4-session
#5 0x00001e1dc9010107 in sm_init () from /usr/local/bin/xfce4-session
#6 0x00001e1fcdf8c6c9 in _SmsProcessMessage () from /usr/X11R6/lib/libSM.so.8.0
#7 0x00001e1fdcd03fff in IceProcessMessages () from /usr/X11R6/lib/libICE.so.9.0
#8 0x00001e1dc900f131 in ice_cleanup () from /usr/local/bin/xfce4-session
#9 0x00001e1fdc03595a in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.3600.0
#10 0x00001e1fdc037708 in g_main_context_iterate () from /usr/local/lib/libglib-2.0.so.3600.0
#11 0x00001e1fdc03882b in g_main_loop_run () from /usr/local/lib/libglib-2.0.so.3600.0
#12 0x00001e1fdb4fb833 in gtk_main () from /usr/local/lib/libgtk-x11-2.0.so.2400.0

[Calin Cerghedean (ccerghe1)]

This has been reported several times against the Ubuntu 13.04 (Raring) distribution:
https://bugs.launchpad.net/bugs/1104435

I don't think that you can release the 4.10 build until this crash is fixed.

[Kip Warner (kip)]

I'm in agreement. It seems to be a show stopper.

[Ncopa (ncopa)]

(In reply to comment #10)
> This has been reported several times against the Ubuntu 13.04 (Raring)
> distribution:
> https://bugs.launchpad.net/bugs/1104435
>
> I don't think that you can release the 4.10 build until this crash is fixed.

I am not convinced the bug is in xfce4-session. It could also be a bug in glib.

[Kip Warner (kip)]

It could be in glibc, but I have a feeling it's somewhere in client code. It is possible it's in glibc, but improbable without further evidence. The reason I say this is because there would probably be a lot more people reporting the same or similar issues with glibc, perhaps regardless of their desktop environment.

[Landry-o (landry-o)]

(In reply to comment #13)
> It could be in glibc, but I have a feeling it's somewhere in client code. It
> is possible it's in glibc, but improbable without further evidence. The
> reason I say this is because there would probably be a lot more people
> reporting the same or similar issues with glibc, perhaps regardless of their
> desktop environment.

i think you meant _glib_ here. glibc is something else :)

> I don't think that you can release the 4.10 build until this crash is fixed.

4.10 was released a year ago. If the issue is really in xfce4-session and a fix is a found, there will be a bugfix release of it.

The problem was definitely caused by various os/distributions upgrading their glib version to 2.36, and the crashes are a consequence of this.

[Kip Warner (kip)]

(In reply to comment #14)
> i think you meant _glib_ here. glibc is something else :)
>
> > I don't think that you can release the 4.10 build until this crash is fixed.
>
> 4.10 was released a year ago. If the issue is really in xfce4-session and a
> fix is a found, there will be a bugfix release of it.
>
> The problem was definitely caused by various os/distributions upgrading
> their glib version to 2.36, and the crashes are a consequence of this.

Hey Landry. Yes, I meant glib, not glibc. However, my point is still relevant because glib is just as ubiquitous which suggests to me that there might expect to be a lot more activity around the bug if that were the case as opposed to specific to just one desktop environment. Although, it could be that the bug is in glib, but the client's usage of the library is unique enough that only we are the ones seeing this behaviour. Who knows. We need more info.

[Landry-o (landry-o)]

Got another crash with a different traceback this time. xfce4-session was starting the apps of the session, with the debug log :

[1366139916] -> Set string (UserID, landry)
[1366139917] Client Id = 110af6c82f000136596667800000064170000, received SET PROPERTIES [Num props = 1]
[1366139917] Name: RestartCommand
[1366139917] Type: LISTofARRAY8
[1366139917] Value:
[1366139917] /usr/local/lib/firefox-21.0/firefox,
[1366139917] --sm-config-prefix,
[1366139917] /firefox-PfYLAg/,
[1366139917] --sm-client-id,
[1366139917] 110af6c82f000136596667800000064170000,
[1366139917] --screen,
[1366139917] 0
[1366139917]
[1366139917]
[1366139917] -> Set strv (RestartCommand)
[1366139918] ICE connection fd = 18, received NEW CLIENT

[1366139918] ICE connection fd = 18, received REGISTER CLIENT [Previous Id = 110af6c82f000136353664600000290120000]

#0 0x00000bb07648786f in g_slice_alloc () from /usr/local/lib/libglib-2.0.so.3600.0
(gdb) bt
#0 0x00000bb07648786f in g_slice_alloc () from /usr/local/lib/libglib-2.0.so.3600.0
#1 0x00000bb06c93c3ca in simple_add_entry () from /usr/local/lib/libxfce4util.so.3.0
#2 0x00000bb06c93d00e in _xfce_rc_simple_parse () from /usr/local/lib/libxfce4util.so.3.0
#3 0x00000bb06c93bedc in _xfce_rc_config_new () from /usr/local/lib/libxfce4util.so.3.0
#4 0x00000bae61d1cfaf in xfsm_splash_screen_new () from /usr/local/bin/xfce4-session
#5 0x00000bae61d1d588 in xfsm_splash_screen_new () from /usr/local/bin/xfce4-session
#6 0x00000bae61d1da12 in xfsm_startup_session_continue () from /usr/local/bin/xfce4-session
#7 0x00000bae61d1767e in xfsm_manager_register_client () from /usr/local/bin/xfce4-session
#8 0x00000bae61d10963 in sm_init () from /usr/local/bin/xfce4-session
#9 0x00000bb06374e05e in _SmsProcessMessage () from /usr/X11R6/lib/libSM.so.8.0
#10 0x00000bb06dbeafff in IceProcessMessages () from /usr/X11R6/lib/libICE.so.9.0
#11 0x00000bae61d0f131 in ice_cleanup () from /usr/local/bin/xfce4-session
#12 0x00000bb07646b95a in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.3600.0
#13 0x00000bb07646d708 in g_main_context_iterate () from /usr/local/lib/libglib-2.0.so.3600.0
#14 0x00000bb07646e82b in g_main_loop_run () from /usr/local/lib/libglib-2.0.so.3600.0
#15 0x00000bb0718f3833 in gtk_main () from /usr/local/lib/libgtk-x11-2.0.so.2400.0
#16 0x00000bae61d0f7b6 in main () from /usr/local/bin/xfce4-session

of course, linked again to XfceRc->GSlice

[Kip Warner (kip)]

The only way I can see g_slice_alloc possibly segfaulting is if its only parameter block_size was either 0 or the client requested more memory than was available. Otherwise the problem could well be in glib since if the call failed, one might expect it to have returned NULL, but then the crash would have happened in the caller when it dereferenced it and not within the g_slice_alloc function itself. I also don't think it is a threading issue because glib is allegedly thread safe.

[schollsky (schollsky)]

Hi all,

problem is most likely caused by lightdm. I constantly experience crashes when starting xfce/Xubuntu using lightdm selector.

There are no crashes after stopping lightdm on console and starting Xfce manually by "startxfce4"! (may also be used as workaround).

Kind regards,

Stefan

[appzer0 (appzer0)]

I can confirm the errors seen here, since I upgraded glib to 2.36.1. I've never encountered those problems with 2.34.x or earlier versions.

Crahes tend to occur when raising a window or launching e.g. Thunar or another glib/gtk app, even when restoring a (precompiled binary) Firefox window. xfce4-session segfaults then X crashes (the latter may be another problem at my side).

---
GLib-WARNING **: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). Most likely the process is ignoring SIGCHLD, or some other thread is invoking waitpid() with a nonpositive first argument; either behavior can break applications that use g_child_watch_add()/g_spawn_sync() either directly or indirectly.

Plus other 'g_slice_set_config' errors, with "sys_page_size == 0 failed".
---

[Robert (metzgerr-9)]

I can confirm this bug with the new glib2. Other Arch Linux are having similar problems:

https://bugs.archlinux.org/task/34892
https://bbs.archlinux.org/viewtopic.php?pid=1264082

I'm seeing the following entry in "dmesg":

xfce4-session[451]: segfault at ffffffff00000000 ip 00007f9802f24537 sp 00007fffb8eeba50 error 5 in libglib-2.0.so.0.3600.1[7f9802ec1000+fc000]

[Ncopa (ncopa)]

(In reply to comment #18)
> I can confirm the errors seen here, since I upgraded glib to 2.36.1. I've
> never encountered those problems with 2.34.x or earlier versions.

...

> ---
> GLib-WARNING **: GChildWatchSource: Exit status of a child process was
> requested but ECHILD was received by waitpid(). Most likely the process is
> ignoring SIGCHLD, or some other thread is invoking waitpid() with a
> nonpositive first argument; either behavior can break applications that use
> g_child_watch_add()/g_spawn_sync() either directly or indirectly.

I have a feeling that whatever causes this warning causes a memory corruption or a double free. I could not find any reason to *why* this warning shows up so I think something fishy here is going on.

I have the following suggestions to move forward on this:

1) fix the above ECHILD warning and see if problem still happens.

2) git bisect glib and find the exact glib commit that introduces this error.

A wild guess would be:
https://git.gnome.org/browse/glib/commit/glib/?id=ce0022933c255313e010b27f977f4ae02aad1e7e
(which seems to be partially reverted recently)

[Ncopa (ncopa)]

It would be nice is someone could test if this patch (to glib) solves this issue:

https://git.gnome.org/browse/glib/commit/glib/gspawn.c?id=eb860fd898a6a2bd86c11d245294cd0e8cd4304b

[appzer0 (appzer0)]

Hi,

Applied the patch and recompiles glib 2.36.1, but same problems occur in Xfce (maybe a little less frequent) : GChildWatchSource errors all the same and "random" crashes/segfaults when launching Thunar or other gtk windows/apps.

Thanks!

[8-nick (8-nick)]

Pushed 2 fixes to master for this. Please give it a shot.

[Vladimír Čunát (vcunat)]

I updated glib to 2.36.1 + I disabled SANE_MALLOC_PROTOS (see https://bugzilla.gnome.org/show_bug.cgi?id=698716), and the crashes seem to have disappeared for me (one day of using now).

I also have a coredump of one of the previous crashes. If you're interested, I could post the binaries with symbols inside and the core somewhere so you can inspect yourselves. I looked at the disassembly just before the crash: it's somewhere inside g_slice_alloc (it's -O2 so the calls above probably got inlined) and there is a series of pointer dereferences (some a bit ofsetted) with 0-tests, so essentially walking some 0-ended linked list, until it gets into a place where there's 0xffffffff00000000 and at dereferencing this it SIGSEGVs.

[appzer0 (appzer0)]

Hi,

I could not reproduce this bug with xfce4-session patched with the 2 fixes (async spawn + double-free bug), no lmatter how hard I try. No more gchildwatchsource errors. glib is still patched with #21. Seems fixed.

Should I try once again with an unpatched stable 2.36.1 glib?

Thanks again

[Vladimír Čunát (vcunat)]

I forgot to add that the non-crashing version described above still produces one GChildWatchSource warning at the start (unpatched released xfce4-session-4.10).

[Landry-o (landry-o)]

Given that lots of coredumps are showing 0xffffffff00000000 errors, would be nice to know if the crashes happen only on x86_64/amd64 or if they've also been experienced on 32-bits archs.

[Calin Cerghedean (ccerghe1)]

(In reply to comment #27)
> Given that lots of coredumps are showing 0xffffffff00000000 errors, would be
> nice to know if the crashes happen only on x86_64/amd64 or if they've also
> been experienced on 32-bits archs.

It looks like the bug reported against Ubuntu is limited to x86_64/amd64.
I checked the bug that is linked to this one (1104435) and all of its duplicates.

[Ncopa (ncopa)]

(In reply to comment #23)
> Pushed 2 fixes to master for this. Please give it a shot.

This one alone fixes it:
http://git.xfce.org/xfce/xfce4-session/commit/?id=ab391138cacc62ab184a338e237c4430356b41f9

The other might have impact on startup time if you have many apps. I don't know how much difference in time it is vfork vs fork, if any at all. I suppose it should be tested. vfork *migh* be noticeable faster (even if g_spawn_async is cleaner).

[Calin Cerghedean (ccerghe1)]

Please let me know when it's available in a PPA, and I will install it and test it.

[8-nick (8-nick)]

I doubt its any slower certainly not with the *normal* amount of applications started with this (say < 20), and using the spawn function from glib makes it more future proof.

[Jochen Kemnade (jochenkemnade)]

Stefan, I tried your "workaround", but it crashed, too. However, apparently the bug has been fixed upstream:
https://bugzilla.xfce.org/show_bug.cgi?id=9709#c29
http://git.xfce.org/xfce/xfce4-session/commit/?id=ab391138cacc62ab184a338e237c4430356b41f9

[Shirish Agarwal (shirishag75)]

I hope there is a new release of xfce4-session soon which has the patch shared here as I'm also suffering the same issue.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706425

Looking forward to a new release.

[8-nick (8-nick)]

If some more people can test the patches and can confirm the issue is fixed (the segfaults, probably not the new warnings) i can make a new release.

[Jochen Kemnade (jochenkemnade)]

I built and installed a version that contains this fix yesterday. I started and quit Xubuntu sessions (from lightdm btw) three times since then and got no crashes so far where the stock version would have crashed at least three times (upon every logout).

[Jan Rękorajski (baggins-pld-linux)]

(In reply to comment #33)
> If some more people can test the patches and can confirm the issue is fixed
> (the segfaults, probably not the new warnings) i can make a new release.

No crashes for me after applying the patches to xfce4-session and glib.

[appzer0 (appzer0)]

No crashes anymore here after applying the patches to xfce4-sessions AND glib 2.36.1 but I still have logout problems/freezes, though maybe not directly linked to this bug.

[nirik (kevin-scrye)]

I've had no further crashes here since applying the 2 patches.

I also pushed them out to Fedora rawhide / 19alpha folks... so far no reports either way from them however. ;(

[Moritz Naumann (mnaumann)]

Please help testing Ricardo F. Teixeira's patched builds from this PPA:
https://launchpad.net/~ricardo.teixas/+archive/xfce4-session
...and provide feedback here:
https://code.launchpad.net/~ricardo.teixas/ubuntu/raring/xfce4-session/fix-for-1104435/+merge/161735
Please be sure to test thoroughly.

The process to get the updated package would be:
sudo apt-add-repository ppa:ricardo.teixas/xfce4-session
sudo apt-get update
sudo apt-get install xfce4-session=4.10.0-2ubuntu2~raring1 ppa-purge

To remove this PPA:
sudo ppa-purge ppa:ricardo.teixas/xfce4-session

To downgrade to the xfce4-session version currently in the Ubuntu Universe repository:
sudo apt-get update
sudo apt-get install xfce4-session=4.10.0-2ubuntu1

[Jean-Philippe Guérard (fevrier)]

The updated rpm has solved the issue for me. No more segfault since I installed it.

Before that, my system was barely usable.

[Jean-Philippe Guérard (fevrier)]

Hum... I meant, the updated deb file ^^

[Coya DeBrojara (coyadebrojara)]

Works fine, and no more errors occur.
Thanks for the tip Moritz.
I was wandering the problem in a different way. I replaced lightdm, on "mdm" - such as in linux mint, and the problem also disappeared.

[Bjorn Madsen (esprit-tordu)]

This affects me too. Switching to a different display manager until upstream fixes it for my xubuntu release 13.04.

[Calin Cerghedean (ccerghe1)]

No longer crashes for me, since I applied the patch for xfce4-session from the PPA.

[Thomas Karcher (thkarcher)]

Moritz' fix #19 worked for me - great, thanks!

[Jeromeg (jeromeg)]

*** Bug 10068 has been marked as a duplicate of this bug. ***

[thejpster (ubuntu-thejpster)]

I'm seeing this in 12.04 LTS running XFCE4 and XMonad. I can't apply the PPA as it only seems to support 13.04.

$ dmesg | grep xfce4-session
[ 6007.436056] xfce4-session[3340]: segfault at ffffffff00000000 ip 00007ffb724b4b5a sp 00007fff04e2bb20 error 5 in libglib-2.0.so.0.3504.0[7ffb72452000+f9000]
[607137.017906] xfce4-session[11826]: segfault at ffffffff00000000 ip 00007f8e29911b5a sp 00007fff572436a0 error 5 in libglib-2.0.so.0.3504.0[7f8e298af000+f9000]

[thejpster (ubuntu-thejpster)]

Oh, I've got some updated libgvfs-mtp stuff installed which may have updated my libglib. I'll try backing it all out and reverting to stock.

$ sudo dpkg -l libglib*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=====================================================-=====================================================-==========================================================================================================================
ii libglib-perl 2:1.241-1 interface to the GLib and GObject libraries
ii libglib2.0-0 2.35.4-0ubuntu5~webupd8~precise1 GLib library of C routines
ii libglib2.0-bin 2.35.4-0ubuntu5~webupd8~precise1 Programs for the GLib library
ii libglib2.0-cil 2.12.10-2ubuntu4 CLI binding for the GLib utility library 2.12
un libglib2.0-cil-dev <none> (no description available)
ii libglib2.0-data 2.35.4-0ubuntu5~webupd8~precise1 Common files for GLib library
ii libglib2.0-dev 2.35.4-0ubuntu5~webupd8~precise1 Development files for the GLib library
un libglib2.0-doc <none> (no description available)
ii libglibmm-2.4-1c2a 2.32.0-0ubuntu1 C++ wrapper for the GLib toolkit (shared libraries)

[Pilou-o (pilou-o)]

This error occurs since I upgraded glib to 2.36 (debian package 2.36.1-2) with xfce4-session 4.8 (debian package: 4.8.3-3).

No crashes for me after applying the patch (http://git.xfce.org/xfce/xfce4-session/commit/?id=ab391138cacc62ab184a338e237c4430356b41f9) to xfce4-session.

[Kaio Donadelli (xhikofff)]

Just installed xfce4-session from the suggested PPA at #19 and it seems to have solved it for me too.

[Kip Warner (kip)]

I concur with Kaio. The patched xfce4-session package from the PPA in #19 solved it for me too.

[junomedia (junomedia)]

The patched xfce4-session package from the PPA in https://bugs.launchpad.net/ubuntu/+source/xfce4-session/+bug/1104435/comments/19 solved it for me.

[Vanessa Dannenberg (vanessadannenberg)]

Both of my 13.04 setups were affected by this (one rarely, the other quite severely). The PPA in comment #19 applied cleanly and fixed both.

[Tim Michals (tcmichals)]

Also, mine crashes all the time also.. tried disable screen savers etc..
The crash report is titled Xorg crash with SIGABRT is this the same issue. I sent the report in.

[gdi2k (gdi2k)]

Everything was fine until this afternoon, then this started happening, no idea what triggered it.

I could reproduce consistantly by launching deadbeef (the excellent music player).

Solution in comment 19 fixed it for me. Thanks!

[Launchpad Janitor (janitor)]

This bug was fixed in the package xfce4-session - 4.10.0-2ubuntu2

---------------
xfce4-session (4.10.0-2ubuntu2) saucy; urgency=low

  * debian/patches/xfsm-startup-random-crash.patch: added. Fix random crashes. lp: #1104435
 -- <email address hidden> (Ricardo F. Teixeira) Wed, 01 May 2013 00:33:42 +0100

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Staszek (s-aleksinski)]

I can reproduce it by launching any aplication in full screen and after that I launch terminal. When I launch terminal first, then some fullscreen application, and then terminal again, it doesn't happen.

That's probably only one of the ways to reproduce it.

[memilanuk (memilanuk)]

Fresh install of Xubuntu 13.04 as of a week or so ago. Don't know if its related to the recent updates pushed out in the last few days, but now XFCE is crashing within a few minutes of login.

[Adam Groszer (agroszer)]

my xubuntu 13.04 is not crashing anymore since #19

[Martin Pitt (pitti)]

Raring SRU uploaded to -proposed queue.

[Brian Murray (brian-murray)]

If in fact all the bugs that are marked as duplicates of this are really duplicates then we can use the following buckets at errors.ubuntu.com to see if the -proposed version of xfce4-session is affected by the bug.

 $ ./related-errors.py 1104435
https://errors.ubuntu.com/bucket?id=/usr/bin/xfce4-session:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:handler_new:g_signal_connect_data
https://errors.ubuntu.com/bucket?id=/usr/bin/xfce4-session:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_array_sized_new:invoke_object_method
https://errors.ubuntu.com/bucket?id=/usr/bin/xfce4-session:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_tree_node_new:g_tree_insert_internal
https://errors.ubuntu.com/bucket?id=/usr/bin/xfce4-session:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:pango_font_description_new:pango_font_description_from_string
https://errors.ubuntu.com/bucket?id=/usr/bin/xfce4-session:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_slice_alloc0:g_type_create_instance
https://errors.ubuntu.com/bucket?id=/usr/bin/xfce4-session:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_tree_new_full:xfsm_properties_new

Of those buckets the first one has the most incidences.

[Brian Murray (brian-murray)]

Hello Coya, or anyone else affected,

Accepted xfce4-session into raring-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/xfce4-session/4.10.0-2ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Brian Murray (brian-murray)]

As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of xfce4-session from raring-proposed was performed and bug 1186705 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed" tag from this bug report and tag 1186705 "bot-stop-nagging". Thanks!

[Dmitry Malykhanov (dmalykhanov)]

xfce4-session_4.10.0-2ubuntu1.1 appears to do the trick. Before installing the bugfix I was unable to perform ANY session-related operation (save, clear, even log out). How all of them working. Still testing the long run...

[Coya DeBrojara (coyadebrojara)]

I have xubuntu installed on three computers. Two laptops and a desktop computer. Previously, before you apply the update I had huge problems with the stability of the session. Now, after the update is applied, the problems do not occur, the system runs stably and smoothly.
Brian, the problem described here: Bug#1186705 also appears on all of my computers, but the gray screen appears for half a second, and then loading properly xubuntu desktop. So do not do you consider that this is really a problem that prevents the proper operation of the system.
In summary, I believe that the patch must be attached to the stable version of xubuntu.

(Xubuntu mam zainstalowane na trzech komputerach. Dwóch laptopach i jednym komputerze stacjonarnym. Poprzednio, przed zastosowaniem aktualizacji mialam ogromne problemy ze stabilnością sesji. Obecnie, po zastosowaniu aktualizacji, problemy się nie pojawiają, system działa stabilnie i bezproblemowo.
Brian, problem opisany tutaj: Bug#1186705 występuje również na wszystkich moich komputerach, jednak szary ekran pojawia się na pół sekundy, po czym ładuje się poprawnie pulpit xubuntu. Więc nie uwarzam że jest to naprawdę problem uniemożliwiający poprawną pracę z systemem.
Reasumując: uważam że patch należy załączyć do stabilnej wersji xubuntu.)

[Ricardo F. Teixeira (ricardo.teixas)]

Coya did you have the same problem before applying the patch? I'm asking, because I'm not experiencing the problems described by the bug #1186705.

[Coya DeBrojara (coyadebrojara)]

Yes, described gray screen also performed before installing the patch. I do not consider this a problem, because the gray screen appears for half a second and does not affect in any way the operation of the system. I'm not getting any error message.

Is it possible that this effect is related to the use of my proprietary driver from nVidia, and that is not affiliated with xfce?

(Tak, opisany szary ekran występował również przed instalacją patcha. Nie uznaję tego za problem, ponieważ szary ekran pojawia się na pół sekundy i nie wpływa w jakikolwiek sposób na działanie systemu. Nie wyświetla się żadna informacja o błędzie.
Czy możliwe jest, że taki efekt jest związany z używaniem przeze mnie sterowników własnościowych od nvidia i że nie jest powiązany z xfce ?)

[pqwoerituytrueiwoq (pqwoerituytrueiwoq)]

If you are refering to the wallpaper going gray for a moment during login, i get that on both my systems 1 amd (Phenom II 965) +nvidia (gtx 550 ti) desktop and 1 intel sandy bridge laptop

[Forest (foresto)]

Bug 1186705 is probably a duplicate of bug 996791, and unrelated to this proposed patch.

I installed xfce4-session 4.10.0-2ubuntu1.1 from raring-proposed and have rebooted a couple of times since. I haven't had a problem so far. Xubuntu, amd64, nvidia-310 proprietary driver.

[Ricardo F. Teixeira (ricardo.teixas)]

Based on my research only those who are using proprietary drivers are suffering from this problem. Nevertheless, I found some complaints from people who had their /home encrypted and had the problem from bug #1186705. Based on my results I will remove the "verification-failed" tag.

[Kip Warner (kip)]

Ricardo, I've observed this issue on hardware running without any proprietary drivers. In that case, they were using a System76 machine with an integrated Intel GPU.

[Anzan Hoshin (anzanhoshinroshi)]

Ricardo, as Kip wrote. this is a System 76 Sable Complete upgraded from 12.10 to 13.04 and it has the bug.

[Coya DeBrojara (coyadebrojara)]

Ricardo, Kip, when I installed the driver Nouevau (1:1.0.7-0ubuntu1) on a laptop, a gray screen does not appear. If I run Xubuntu in "nomodeset" the gray screen also does not appear.

(On these computers, I've installed xubuntu, drivers nvidia-310-updates (310.44-0ubuntu2)
i7-720QM, NV GF GTX260M
i7-2670QM, NV GF GTX570M
AMD Phenom II X4 805, NV GF 9600GT)

[Kip Warner (kip)]

I think the really key thing to ascertain at this point is whether anyone, proprietary drivers or not, are still experiencing this issue since using the PPA supplied in comment #19.

[Coya DeBrojara (coyadebrojara)]

As I wrote earlier (#46), the problem with the gray screen appeared before installing the patches described in comment #19

(Jak napisałam wcześniej (#46) problem z szary ekranem występował przed instalacją łatki opisanej w komentarzu #19. )

[pqwoerituytrueiwoq (pqwoerituytrueiwoq)]

@Ricardo F. Teixeira (ricardo.teixas)
Using the version prior to the fix, i have yet to encounter this issue on my nvidia system, the only system i encountered this on was my 100% open source laptop, was able to reproduce it using full screen app and using alt+tab to switch windows, a month or so later it starred happening left and right on me then i added the ppa with the patched copy of xfc4-session it has not happened since, i have not tried patched copy on my nvidia/amd system

[Dmitry Malykhanov (dmalykhanov)]

Worked through the day without a crash, the same today. Have not seen any artifacts during login or any other side effects. Thus, xfce4-session_4.10.0-2ubuntu1.1 works for me.

HW: Intel i5 480M

[Dennis Benzinger (dennis-benzinger)]

Since version 4.10.0-2ubuntu1.1 this problem has gone away. And I have never experienced <https://bugs.launchpad.net/bugs/1186705>.

[Calin Cerghedean (ccerghe1)]

I tried pointing to raring-proposed, but since I already installed it from the PPA, it isn't showing up as an available upgrade.
Currently, I have this version installed: 4.10.0-2ubuntu2~raring1
I wonder whether you should bump up the version and republish to -proposed, so that everyone who previously installed from the PPA gets the official update.
Also, I have seen no crashes since I installed the fix.

[Ricardo F. Teixeira (ricardo.teixas)]

Calin can you try the following command?
$ sudo apt-get update && sudo apt-get install xfce4-session=4.10.0-2ubuntu1.1

I think you can force apt to install a specific version... Give it a shot and let me know if you were successful.

[Calin Cerghedean (ccerghe1)]

Yes, the install of the specific version worked for me; you do get a warning from apt-get that you are downgrading a package, but we all know that is not the case here.
Thanks for the suggestion.

[Vliegendehuiskat (vliegendehuiskat)]

Had this problem on both a system with fglrx and a system with non-proprietary drivers.

The packages in the PPA fixed this bug on both of them.

[Bjorn Madsen (esprit-tordu)]

I switched to lxde to avoid this problem and receive a similar problem there but there the window manager crash is blamed on Xorg. I have a hunch this problem might be caused by having dual monitors, is there anybody receiving this error with only one monitor?

[pqwoerituytrueiwoq (pqwoerituytrueiwoq)]

@Bjorn Madsen (esprit-tordu)
i was using a single display (intel GPU)

[Forest (foresto)]

Update: After a couple of weeks using xfce4-session_4.10.0-2ubuntu1.1 with no more crashes, I think it's safe to say this fixed the problem for me.

[Forest (foresto)]

(I'm on Raring, where the package hasn't yet made it out of -proposed.)

[Florian Fuchs (fuchsfl)]

After using xfce4-session 4.10.0-2ubuntu1.1 a few weeks, I didn't have any crashes. I have no other packages installed from proposed. I don't notice any sideeffects, using Asus N76V Laptop. I'm using plain raring.

[Dennis Benzinger (dennis-benzinger)]

@Bjorn Madsen (esprit-tordu)
I had the problem with a single display. But with the new version everthing is ok.

[Bjorn Madsen (esprit-tordu)]

Update: I have found a way to cause this bug 100% repeatable. Open a terminal window and type firefox -new-instance and immediate segfault. The resulting errors:

xfce4-session[11891]: segfault at ffffffff00000000 ip 00007fb430233f7f sp 00007fffb89662f0 error 5 in libglib-2.0.so.0.3600.0[7fb4301d0000+f9000]

xfce4-session[9120]: segfault at ffffffff00000000 ip 00007fb98e8c3f7f sp 00007fffa3dd2c50 error 5 in libglib-2.0.so.0.3600.0[7fb98e860000+f9000]

[Match (xhosa)]

It seems likely that this bug is related to the following xfce bug report: http://comments.gmane.org/gmane.comp.desktop.xfce.bugs/3072

I have installed 4.10.1 from ppa (https://launchpad.net/~xubuntu-dev/+archive/xfce-4.10) and the problem seems to be resolved.

Can this update be 'fast-tracked' to try to resolve this issue?

[Aaron Patterson (apatters)]

The PPA in #19 appears to have fixed this issue for me. I was experiencing this problem and for two days since installing the fix it hasn't recurred.

[JMB (jmb-tux)]

The PPA in #19 has worked for me, too.
I am on Xubuntu 13.04 amd64 3.8.0-25-generic (now: -26-) with a pure
Intel Sandy Bridge system - no proprietary driver, but quite complete
installation (but with XFCE as only window manager).
I crete many xterms by a script which crashed the XFCE session deliberately.
After installing the fix/PPA my system is stable.
Will this fix enter the standard raring repository soon ?
Many thanks for the fix/PPA !

[George Poulson (george-poulson)]

I found this page while researching a problem that has been affecting me for a couple of weeks. I'm running xubuntu-13.04 x64 (upgraded from 12.10) on an Asus X52 notebook.

As other users have reported my session was being repeatedly logged out at seemingly random intervals with no identifiable trigger.

As suggested in earlier posts I configured the 'raring-proposed' repository and upgraded 'xfce4-session' from '4.10.0-2ubuntu-1' to '4.10.0-2ubuntu-1.1' and my system now appears to be stable.

Thanks!

[Jack Grigg (pythonian4000)]

This error occurred for one of the user accounts on my laptop when I first opened Pidgin in it, and then tried to go to "Sessions and Startup" to remove it. Since then, xfce4-session would crash opening "Sessions and Startup" or when logging out.

I am running Xubuntu 13.04, xfce4-session = 4.10.0-2ubuntu1, libglib2.0-0 = 2.36.0-1ubuntu2

I downloaded the xfce4-session-4.10.0 src tarball, applied the patch (http://git.xfce.org/xfce/xfce4-session/commit/?id=ab391138cacc62ab184a338e237c4430356b41f9), compiled and installed locally, and then symlinked the patched binaries into /usr/bin over the installed ones (moving the installed ones out of the way first). I'm not getting any more crashes now.

[rantsh (rantsh)]

I was affected too, problem dissapeared after using "proposed" fix (as per response #41)

[Si Dedman (si-dedman)]

Tried #19, got this:

Setting up ppa-purge (0.2.8+bzr57) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Processing triggers for menu ...
sh: 0: getcwd() failed: No such file or directory

Don't know what directory is being referred to. Don't know if this will prevent things running smoothly. Any ideas guys?
Cheers
Si

[Si Dedman (si-dedman)]

Still broken.

[Dennis Benzinger (dennis-benzinger)]

@Si Dedman (dez93-2000):
Can you try the package from #41 instead? That's the version I used for my test in comment #57.

[Patrik B. (inoki-deactivatedaccount)]

Using the patch from the PPA in comment #19 and no crashes so far.

[Patrik B. (inoki-deactivatedaccount)]

Ok, had to report a crash using Chromium again. You can find it here: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1209197

[Elkan (roelen)]

After the patch my system kept crashing random.
I even noticed that when i want to close my session or shutdown the system the session crashed.

After removing the session the crash hasn come back any more.

To remove the session:

$ rm .cache/sessions/xf*

Good luck!

[Marius (felijohn)]

No more crashes after installing 4.10.0-2ubuntu1.1. I did not notice any other bugs introduced. It works great for me.

[Launchpad Janitor (janitor)]

This bug was fixed in the package xfce4-session - 4.10.0-2ubuntu1.1

---------------
xfce4-session (4.10.0-2ubuntu1.1) raring; urgency=low

  * debian/patches/xfsm-startup-random-crash.patch: added. Fix random crashes.
    LP: #1104435
 -- <email address hidden> (Ricardo F. Teixeira) Wed, 01 May 2013 00:33:42 +0100

[Brian Murray (brian-murray)]

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

[Merrattic (merrattic)]

I have this problem on 12.04.3 64bit. How to apply the patch ?

[pqwoerituytrueiwoq (pqwoerituytrueiwoq)]

are you using the xfce 4.10 and 4.12 PPAs? if so I think you can install the current deb file
http://mirror.pnl.gov/ubuntu//pool/universe/x/xfce4-session/xfce4-session_4.10.0-2ubuntu1_amd64.deb

BTW if you upgrade to 12.10 you can skip strait to 14.04 when it comes out via the update manager
xubuntu 12.04 just seemed to be lacking the finishing touches imo
12.10 is supported till April 2014
13.04 is supported till January 2014
13.10 is supported till July 2014

[Eric Koegel (eric-koegel)]

Was fixed in master and backported to 4.10 in
http://git.xfce.org/xfce/xfce4-session/commit/?h=xfce-4.10&id=3ed422cb352b65
bc7c4ff6d68b1ed89bd278464f and released in 4.10.1, marking closed.