Thunar frequently crashes

funkaddict · 2018-08-02 10:44:19

Hey there, first of all thank you for the great work with xfce and thunar.

Since yesterday I am experiencing massive crashes while running thunar on a manjaro xfce install. It just crashes at arbitrary operations. For example if I am opening a pdf in the file browser, both programs crash. When I try to copy a file from thunar to the desktop, it crashes. When I kill thunar, and open the file-browser again it just shows a black screen, it does not show anything. The only thing getting it to work again is a reboot. After rebooting, it works for some minutes and crashes again.
All other programs including firefox, thunderbird, virtualbox, etc. running without any issues, but when I try to save a document in libreoffice, it also crashes. I think I did not do any updates yesterday, so I am really wondering why these crashes occur.

Any ideas, where to start?

Last edited by funkaddict (2018-08-02 10:46:45)

ToZ · 2018-08-02 11:41:38

Hello and welcome.

You can use coredumpctl (see the section "Examining a core dump") to get more information about the crash. Perhaps post the complete info from that last thunar crash.

This will help display the info:

coredumpctl info $(coredumpctl list | grep thunar | tail -1 | awk '{print $5}') --no-pager

Jerry3904 · 2018-08-02 12:41:01

That command assumes systemd is the init, I guess.

ToZ · 2018-08-02 12:44:30

Jerry3904 wrote:

That command assumes systemd is the init, I guess.

Yes. I believe manjaro uses systemd.

funkaddict · 2018-08-03 12:31:59

Thank you. In the meanwhile I i found that the issue is not thunar related. I just installed Spacefm and it also just crashed when I tried to copy a file. Anyway here is the output of coredump:

$ coredumpctl info $(coredumpctl list | grep thunar | tail -1 | awk '{print $5}') --no-pager
Journal file /var/log/journal/68ad47f7afae4eaa8507db81d1201296/system@0005727218f3d3e6-c15bfbc15cd2610e.journal~ is truncated, ignoring file.
Journal file /var/log/journal/68ad47f7afae4eaa8507db81d1201296/system@0005727218f3d3e6-c15bfbc15cd2610e.journal~ is truncated, ignoring file.
PID: 831 (Thunar)
UID: 1000 (daniel)
GID: 1000 (daniel)
Signal: 11 (SEGV)
Timestamp: Fri 2018-06-29 15:23:09 CEST (1 months 4 days ago)
Command Line: Thunar --daemon
Executable: /usr/bin/thunar
Control Group: /user.slice/user-1000.slice/session-c2.scope
Unit: session-c2.scope
Slice: user-1000.slice
Session: c2
Owner UID: 1000 (xxxxxl)
Boot ID: 6ede137732c94cc3b0439c4f441d7b82
Machine ID: 68ad47f7afae4eaa8507db81d1201296
Hostname: LWET-RIGZ-105_2-Lin
Storage: /var/lib/systemd/coredump/core.Thunar.1000.6ede137732c94cc3b0439c4f441d7b82.831.1530278589000000.lz4 (inaccessible)
Message: Process 831 (Thunar) of user 1000 dumped core.

Stack trace of thread 831:
#0 0x000055a457272836 n/a (thunar)
#1 0x000055a45723ccb0 n/a (thunar)
#2 0x000055a45724aff0 n/a (thunar)
#3 0x00007fe1e6ea8204 n/a (libgio-2.0.so.0)
#4 0x00007fe1e6ea8d07 n/a (libgio-2.0.so.0)
#5 0x00007fe1ddb8f5c1 n/a (libgvfsdbus.so)
#6 0x00007fe1e6ea8204 n/a (libgio-2.0.so.0)
#7 0x00007fe1e6ea8d07 n/a (libgio-2.0.so.0)
#8 0x00007fe1e6ee973d n/a (libgio-2.0.so.0)
#9 0x00007fe1e6ea8204 n/a (libgio-2.0.so.0)
#10 0x00007fe1e6ea8d07 n/a (libgio-2.0.so.0)
#11 0x00007fe1e6eddc43 n/a (libgio-2.0.so.0)
#12 0x00007fe1e6ea8204 n/a (libgio-2.0.so.0)
#13 0x00007fe1e6ea8239 n/a (libgio-2.0.so.0)
#14 0x00007fe1e68fd1d6 g_main_context_dispatch (libglib-2.0.so.0)
#15 0x00007fe1e68fd5b1 n/a (libglib-2.0.so.0)
#16 0x00007fe1e68fd8e2 g_main_loop_run (libglib-2.0.so.0)
#17 0x00007fe1e87e8df3 gtk_main (libgtk-x11-2.0.so.0)
#18 0x000055a457235ec4 n/a (thunar)
#19 0x00007fe1e62fa06b __libc_start_main (libc.so.6)
#20 0x000055a4572360ba n/a (thunar)

Stack trace of thread 2002:
#0 0x00007fe1e635aed5 realloc (libc.so.6)
#1 0x00007fe1e6902b89 g_realloc (libglib-2.0.so.0)
#2 0x00007fe1e691f868 n/a (libglib-2.0.so.0)
#3 0x00007fe1e691fbf5 g_string_insert_len (libglib-2.0.so.0)
#4 0x00007fe1e68e86d8 n/a (libglib-2.0.so.0)
#5 0x00007fe1e68e9bb5 g_build_filename (libglib-2.0.so.0)
#6 0x00007fe1e6f007bb n/a (libgio-2.0.so.0)
#7 0x00007fe1e6f062c7 n/a (libgio-2.0.so.0)
#8 0x00007fe1e6f0734f g_file_monitor_source_handle_event (libgio-2.0.so.0)
#9 0x00007fe1e6f347df n/a (libgio-2.0.so.0)
#10 0x00007fe1e6f33b49 n/a (libgio-2.0.so.0)
#11 0x00007fe1e6f33d96 n/a (libgio-2.0.so.0)
#12 0x00007fe1e6f33094 n/a (libgio-2.0.so.0)
#13 0x00007fe1e68fd1d6 g_main_context_dispatch (libglib-2.0.so.0)
#14 0x00007fe1e68fd5b1 n/a (libglib-2.0.so.0)
#15 0x00007fe1e68fd63e g_main_context_iteration (libglib-2.0.so.0)
#16 0x00007fe1e68fd692 n/a (libglib-2.0.so.0)
#17 0x00007fe1e6925a2a n/a (libglib-2.0.so.0)
#18 0x00007fe1e669a075 start_thread (libpthread.so.0)
#19 0x00007fe1e63cf53f __clone (libc.so.6)

Stack trace of thread 2003:
#0 0x00007fe1e63c4ea9 __poll (libc.so.6)
#1 0x00007fe1e68fd523 n/a (libglib-2.0.so.0)
#2 0x00007fe1e68fd8e2 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007fe1e6eec348 n/a (libgio-2.0.so.0)
#4 0x00007fe1e6925a2a n/a (libglib-2.0.so.0)
#5 0x00007fe1e669a075 start_thread (libpthread.so.0)
#6 0x00007fe1e63cf53f __clone (libc.so.6)

Last edited by funkaddict (2018-08-03 12:32:53)

ToZ · 2018-08-03 13:26:34

Unfortunately, there is noting obvious there. However, since you can replicate the issue with another file manager, I guess the next best place is to look might be the health of your hard drive.

Btw, which version of Thunar are you running?

funkaddict · 2018-08-03 15:13:46

Thanks Toz,

I am running Thunar Version 1.8.1git-f5147445. One curious thing: I tried to copy from a network drive (cifs) to my local drive -> crash. Then I copied the exact same folder via command line -> No error at all. I am not sure, if this is a Kernel or some strange GUI behaviour or what ever.

Concerning Hardware issues, I got that hint already in the Manjaro Forums. But if cp in the command line does not produce an error, I asume that the problem is not hardware related.

But what I learn from all this, is that I really have to invest more time to really understand, what linux is, how it works. I think I will to have to start with Arch soon.

Last edited by funkaddict (2018-08-03 15:14:25)

ToZ · 2018-08-03 15:20:43

funkaddict wrote:

Then I copied the exact same folder via command line -> No error at all.

This is interesting. Is it only copying to and from cifs shares that causes a crash? If you copy the same file locally through thunar does it work?

funkaddict · 2018-08-03 15:33:34

No, it also crashes for local only copies. I have 3 drives, I am working on:

1. Local ssd
2. Local hdd
3. Remote hdd via cifs (I am working at a university which is completely relying on MS Software)

So if I copy files from 2, to 1 via any (gui-based) file browser it crashes. Same applies for:
3->1
1->3
2->3
3->2

And so on. So I think this is no cifs related issue. But, when I went back to use an older kernel (4.9 instead of 4.14) it seamed to be stable again. Unfortunately the cifs mount where not working anymore in the older kernel, which I couldn't comprehend for the moment.

Last edited by funkaddict (2018-08-03 15:33:58)

ToZ · 2018-08-03 17:28:09

Most of the file managers use gvfs/gio for their operations. What version of gvfs do you have installed?

pacman -Qi gvfs | grep Version

Also can you first quit the Thunar daemon and all processed:

thunar -q

...and then start thunar:

thunar

...and see if the problem replicates?

I am running Thunar Version 1.8.1git-f5147445.

Can you try downgrading the thunar package, logging out and back in again, and trying your test again?

funkaddict · 2018-08-03 19:31:58

I will try that tomorrow, when I am back in the office.

klevstul · 2018-08-29 18:48:37

i'm experiencing thunar crashes on manjaro as well. the bug has been reported at the manjaro forum.

is that a related issue to this one?

Last edited by klevstul (2018-08-29 19:01:30)

mint4all · 2018-08-29 22:39:41

Greetings!

Fwiw, OP #5 shows ...

Signal: 11 (SEGV)
Timestamp: Fri 2018-06-29 15:23:09 CEST (1 months 4 days ago)
Command Line: Thunar --daemon

which, ime, would indicate that the file manager tried to access out-of-scope memory. There are many reasons for this, and a common cause for this segment fault -- ime -- is bad/flaky memory (either physical or virtual), or an ill-configured BIOS setting.

Therefore, it would help to get some better info on how this system is configured by running the

inxi -Fxz

command and posting its output here for further analysis. Thanks.

ToZ · 2018-08-29 23:07:52

Might be best to create a bug report to bring it to the developer's attention.

klevstul · 2018-08-30 06:10:06

thanks for your replies. good idea creating a bug report. i will do that.

[klevstul@silentGamerMjr ~]$ inxi -Fxz
System:    Host: silentGamerMjr Kernel: 4.14.60-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.1.1 
           Desktop: Xfce 4.12.4 Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: MSI model: Z87-G45 GAMING (MS-7821) v: 1.0 serial: <filter> 
           UEFI: American Megatrends v: 1.9 date: 07/21/2014 
CPU:       Topology: Quad Core model: Intel Core i7-4770S bits: 64 type: MT MCP arch: Haswell rev: 3 
           L2 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 49623 
           Speed: 2028 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 2036 2: 2006 3: 2068 4: 2030 
           5: 2017 6: 2068 7: 2066 8: 2015 
Graphics:  Card-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 390.77 bus ID: 01:00.0 
           Display: x11 server: N/A driver: nvidia resolution: <xdpyinfo missing> 
           OpenGL: renderer: GeForce GTX 1060 6GB/PCIe/SSE2 v: 4.6.0 NVIDIA 390.77 direct render: Yes 
Audio:     Card-1: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 
           Card-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           Card-3: N/A type: USB driver: snd-usb-audio bus ID: 3:3 
           Card-4: Logitech G933 Wireless Headset Dongle type: USB driver: snd-usb-audio bus ID: 3:7 
           Sound Server: ALSA v: k4.14.60-1-MANJARO 
Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet driver: alx v: kernel port: d000 
           bus ID: 03:00 
           IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 5.68 TiB used: -9205357636648164124 
           ID-1: /dev/sda vendor: Intel model: SSDSC2BW240A4 size: 223.57 GiB 
           ID-2: /dev/sdb vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB 
           ID-3: /dev/sdc vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB 
           ID-4: /dev/sdd vendor: Western Digital model: WD2003FZEX-00SRLA0 size: 1.82 TiB 
RAID:      Device-1: md0 type: mdraid status: active Components: online: sdc~c1 sdb~c0 
           Info: raid: raid-10 blocks: 2930075136 report: 3/2 UU_ chunk size: 512K 
Partition: ID-1: / size: 184.81 GiB used: 43.27 GiB (23.4%) fs: ext4 dev: /dev/dm-0 
           ID-2: swap-1 size: 34.50 GiB used: 566.0 MiB (1.6%) fs: swap dev: /dev/dm-1 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nvidia temp: 48 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 27% 
Info:      Processes: 276 Uptime: 16d 22h 17m Memory: 31.36 GiB used: 15.84 GiB (50.5%) Init: systemd 
           Compilers: gcc: 8.2.0 clang: 6.0.1 Shell: bash v: 4.4.23 inxi: 3.0.20

klevstul · 2018-08-30 06:33:19

bug reported:
https://bugzilla.xfce.org/show_bug.cgi?id=14640

mint4all · 2018-08-30 16:35:35

I've looked over MSI's support page @ https://www.msi.com/Motherboard/support/Z87-G45-GAMING and didn't find anything unusual about your mobo, or your inxi info. Your nvidia card's temp seems a bit high compared to your mobo's temp, but with a working set of 15GB ram and an uptime of 16 days you've done a lot of crunching, imho, so really nothing sticks out ...

Since you've been able to copy via the command line with no problem, your system is working ok under the covers. That leaves the GUI, namely xfce, and its interactions with your nvidia card. That's where your system's "gaming" capabilities come into play. Which begs the question: how severely have you overclocked/tweaked your hardware, and have you installed intel's latest microcode for your 4 y.o. chipset+cpu+gpu combo?

I am saying this because Intel's early fixes for the Spectre & Heartbleed exploits didn't go all that well, and there were several iterations of those microcode updates pushed out before they got it right. I'm sorry i can't be of more help, but since i am not running Manjaro, i wouldn't know where to look for those updates (fortunately for me, Mint has its own update & driver manager).

Please let us know what you find out.

klevstul · 2018-08-30 22:05:46

thanks, mint4all, for providing me useful info.

answers to your questions:
- i have not done any overclocking
- i have not installed new microcode / flashed the hw
- there are no new updates

for more information do check this bug (i will keep updating that when asked for info):
- https://bugzilla.xfce.org/show_bug.cgi?id=14640

Last edited by klevstul (2018-08-31 21:47:15)

Xfce Forum

Sub domains

#1 2018-08-02 10:44:19

Thunar frequently crashes

#2 2018-08-02 11:41:38

Re: Thunar frequently crashes

#3 2018-08-02 12:41:01

Re: Thunar frequently crashes

#4 2018-08-02 12:44:30

Re: Thunar frequently crashes

#5 2018-08-03 12:31:59

Re: Thunar frequently crashes

#6 2018-08-03 13:26:34

Re: Thunar frequently crashes

#7 2018-08-03 15:13:46

Re: Thunar frequently crashes

#8 2018-08-03 15:20:43

Re: Thunar frequently crashes

#9 2018-08-03 15:33:34

Re: Thunar frequently crashes

#10 2018-08-03 17:28:09

Re: Thunar frequently crashes

#11 2018-08-03 19:31:58

Re: Thunar frequently crashes

#12 2018-08-29 18:48:37

Re: Thunar frequently crashes

#13 2018-08-29 22:39:41

Re: Thunar frequently crashes

#14 2018-08-29 23:07:52

Re: Thunar frequently crashes

#15 2018-08-30 06:10:06

Re: Thunar frequently crashes

#16 2018-08-30 06:33:19

Re: Thunar frequently crashes

#17 2018-08-30 16:35:35

Re: Thunar frequently crashes

#18 2018-08-30 22:05:46

Re: Thunar frequently crashes

Board footer