xfce segfault & complete system failure after Thunar crash

[markling]

The climax of this error is a Linux blackscreen of death, instant reset, termination of all processes and loss of data.

It has happened on more than one occassion.

The general sequence is: Thunar crashes, user complies with system request to file error report, user restarts Thunar, system blackscreens and resets.

The background to this fault has therefore already been filed as a system-prompted error report against (presumably) Thunar, about an hour ago (around 14:55 BST).

Thunar was accessing an encrypted USB drive. It had numerous tabs open to the same drive.

A notable recent occurance around here: Dolphin had been installed and had taken over (without user permission, I might add) from Thunar in those instances from e.g. Firefox and Ubuntu Search when you opt to "open containing folder". It should also be noted that Thunar was anyway malfunctioning at this task before Dolphin came along. I try and avoid executing the task at all now because I don't want Dolphin popping up. But it does happen on occassion. One of those occassions was today.

Here's a series of events recorded in the log:

29/07/2013 14:53:54 Arjuna kernel [19347.155747] do_general_protection: 18 callbacks suppressed
29/07/2013 14:53:54 Arjuna kernel [19347.155756] traps: Thunar[2188] general protection ip:7fa4263a0040 sp:7fff2c6aabb0 error:0 in libc-2.17.so[7fa426353000+1be000]
29/07/2013 14:54:41 Arjuna kernel [19395.063675] xfce4-session[2181]: segfault at ffffffff00000000 ip 00007fbb551d3f7f sp 00007fff21160470 error 5 in libglib-2.0.so.0.3600.0[7fbb55170000+f9000]
29/07/2013 14:54:55 Arjuna NetworkManager[1230] <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.38': no such name
29/07/2013 14:54:55 Arjuna NetworkManager[1230] <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.38': no such name
29/07/2013 14:54:55 Arjuna NetworkManager[1230] <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.38': no such name
29/07/2013 14:54:55 Arjuna NetworkManager[1230] <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.38': no such name
29/07/2013 14:54:55 Arjuna NetworkManager[1230] <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.38': no such name
29/07/2013 14:54:55 Arjuna NetworkManager[1230] <warn> error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: (3) GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get UID of name ':1.38': no such name
29/07/2013 14:54:58 Arjuna acpid client 1251[0:0] has disconnected
29/07/2013 14:54:58 Arjuna acpid client connected from 8604[0:0]
29/07/2013 14:54:58 Arjuna acpid 1 client rule loaded
29/07/2013 14:55:02 Arjuna CRON[8622] (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
29/07/2013 14:55:15 Arjuna rtkit-daemon[2240] Successfully made thread 8884 of process 8884 (n/a) owned by '1000' high priority at nice level -11.
29/07/2013 14:55:15 Arjuna rtkit-daemon[2240] Supervising 1 threads of 1 processes of 1 users.
29/07/2013 14:55:18 Arjuna rtkit-daemon[2240] Successfully made thread 8913 of process 8884 (n/a) owned by '1000' RT at priority 5.
29/07/2013 14:55:18 Arjuna rtkit-daemon[2240] Supervising 2 threads of 1 processes of 1 users.
29/07/2013 14:55:18 Arjuna rtkit-daemon[2240] Successfully made thread 8914 of process 8884 (n/a) owned by '1000' RT at priority 5.
29/07/2013 14:55:18 Arjuna rtkit-daemon[2240] Supervising 3 threads of 1 processes of 1 users.
29/07/2013 14:55:19 Arjuna rtkit-daemon[2240] Successfully made thread 8918 of process 8918 (n/a) owned by '1000' high priority at nice level -11.
29/07/2013 14:55:19 Arjuna rtkit-daemon[2240] Supervising 4 threads of 2 processes of 1 users.
29/07/2013 14:55:19 Arjuna pulseaudio[8918] [pulseaudio] pid.c: Daemon already running.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: thunar 1.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
Uname: Linux 3.8.0-26-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Mon Jul 29 15:37:48 2013
InstallationDate: Installed on 2012-11-28 (242 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MarkForUpload: True
SourcePackage: thunar
UpgradeStatus: Upgraded to raring on 2013-05-14 (75 days ago)

[markling (markling)]

This just happened again.

The crash happened while traversing up the directory tree of an encrypted USB drive using the "UP ARROW" in the Thunar control panel.

The system reset and loss of data occurs without further user involvement. I.e. if the crash happens, just wait a few seconds and the reset will come. (I happened previously to have restarted Thunar in that time and incorrectly associated this action with the system reset.)

[markling (markling)]

I am unable to repeat the error by simply navigating to a place in Thunar, either locally or on an encrypted USB, and rapidly traversing up the tree using the "UP ARROW" in Thunar's control panel.

[Joshua Bell (eages)]

I've experienced the same issue with my RAID1 mounts on Ubuntu Server 13.04. Two instances of Thunar are started, I view separate directories of the RAID partition in each window. On several occasions, Thunar crashes without user notification, then the DM session restarts without warning, potentially losing data. I've not associated the Thunar crash with any particular action, it seems to spontaneously fail when I happen to be viewing the RAID partition.

dmesg dump:
[ 4464.572006] show_signal_msg: 36 callbacks suppressed
[ 4464.572011] Thunar[2167]: segfault at 20 ip 00007fb21cecad42 sp 00007ffff1a1ac48 error 4 in thunar[7fb21ce8f000+b2000]
[ 4475.324529] xfce4-session[2160]: segfault at ffffffff00000000 ip 00007f1abe3f0f7f sp 00007fffef327aa0 error 5 in libglib-2.0.so.0.3600.0[7f1abe38d000+f9000]

I've never seen the problem with the same xfce4 setup before but the RAID and associated drives are new so I can't rule out a hardware/kernel driver issue.

[Launchpad Janitor (janitor)]

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

[markling (markling)]

I've had minor repeats of this problem, without the linux black screen of death.

Just happened twice within an hour. Filed crash reports. Both occassions was rapidly pressing the up arrow on the Thunar navigation panel.

Can't see cause. First time was about three directories deep on an external, encrypted disk. Rapdily up - the crash happened on a rapid 'double-click'-like stab at the up arrow. I.e. the clicking was happening just very slightly faster than Thunar was able to respond. It crashed out.

Second time, was 7 directories deep on same disk. Upped very quickly toward root of drive and it crashed a few directories up the tree.

I have tried unsuccessfully to simply repeat these same errors.

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

Does this crash still occur in 13.10 or 14.04?

[markling (markling)]

Excuse me, Thaddäus. Didn't see your question here.

Thunar has been regularly crashing out in a similar fashion in 14.04 but not with fatal consequences. I have been required only to restart Thunar to continue work.

[Sean Davis (bluesabre)]

This issue hasn't been reported since 14.04. Marking as resolved. Please reopen if you are still able to reproduce on 20.04, 21.10, or 22.04. Thanks!