Thunar 1.6.4 crashes when copying files

ungutknut · 2015-01-29 21:07:29

Hi,

since a few days/weeks (I guess since the update from 1.6.3 to 1.6.4) thunar crashes when I try to copy files (single or multiple, doesn't matter) from one folder to another. No matter how I do it (drag&drop, ctrl-c/v, copy/paste with context menu) or where I do it (from one HDD to another or just copy on one partition) thunar shuts down at roughly 50% of all copy/paste actions without any graphical error message.

I checked if it's some usersetting that might could be wrong so I deleted the Thunar config files in ./config and tried to copy/paste with a newly created user. Result in both tries negative: still crash.

I also think I can exclude some hardware failure as copying in the commandline still works fine.

Some system information:
Xubuntu 14.04 64bit
Kernel 3.16.2
xfce 4.12 ppa from xubuntu-dev
Harddisks have plenty of space

This is the error message displayed when I run thunar from the terminal:

Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkMenuBar::internal-padding' of type `gint' from rc file value "-1" of type `glong'
Speicherzugriffsfehler (Speicherabzug geschrieben)

The Gtk-message appears right after starting thunar, that Speicherzugriffsfehler just happens when thunar is crashing. BTW: it translates as something like: memory access error (memory-tear-off written)
Sorry if that's not entirely correct ^^.

Is somebody aware of this issue? Some tips for me? Is it possible to downgrade to 1.6.3 without dismissing all the other xfce-4.12 packages?

Please help.
Thanks.

edit: for me this issue is not existent anymore. As someone else already wrote, here's the workaround:

"To work around the issue, it should suffice to go to Preferences and check/uncheck "Show file size in binary format"."
(source: https://bugzilla.xfce.org/show_bug.cgi?id=11450#c111)

Last edited by ungutknut (2015-03-30 10:23:01)

ToZ · 2015-01-30 03:57:40

If at all possible, can you do an strace on thunar? To do this, start thunar in a terminal window with:

strace thunar -o ~/thunar.strace

...and make it crash. The ~/thunar.strace file will probably be large, so if you can host is somewhere like pastebin.com that would probably be best. You can do this from within Xubuntu via:

pastebinit ~/thunar.strace

...and post back the link that is generated. (You may need to install the pastebinit program if its not already installed).

ungutknut · 2015-01-30 08:59:21

That strace doesn't seem to work:

When I use it as you suggested it says option "-o" is unknown.
When I use it without -o it says it can't find the file thunar.strace.
When I create the file thunar.strace before, it will open that empty file after showing some output... but thunar won't open.

Here's the output:
http://pastebin.com/index/bDnSs4EZ

...but I guess that won't help as thunar is neither starting nor crashing. Do you have any other suggestions?

ToZ · 2015-01-30 11:43:49

Sorry, I got that backwards:

strace -o ~/thunar.strace thunar

(note to self: always test the command first before posting it)

ungutknut · 2015-01-31 19:13:05

Ok that works now:

http://paste.ubuntu.com/9981318/

ToZ · 2015-01-31 20:49:01

That one doesn't seem to contain information about the crash. Perhaps another copy of, or the Thunar daemon is running (in which case you'll need to connect to the running process with strace).

Here is information on how to use gdb to try to debug the crash. Perhaps it might yield some information.

ungutknut · 2015-02-01 18:30:53

dbg doesn't seem to detect anything, just saying it exited normally:
http://pastebin.com/index/aRnke81M

@thunar daemon: I can't find any thunar related processes with "top -p $(pgrep -d',' thu)", so I guess it's not running.

I also tried another strace like before but the message I received is the same. What's different this time: strace seems to have crashed and caused a bug-warning with that xfce-gui-crash-report-thingy. It says:

strace crashed with SIGSEGV in__GI_raise()

...and some other stuff which doesn't look so important to me (and is not possible to copy/paste because it's not selectable).

I just clicked on "send report"... don't know will happen with the informations though.

GWR · 2015-02-06 14:22:47

Hi,

I have this problem too. Think it started somewhen at the end of last year.

There is no clear way to reproduce it ... just take a file and move it from directory A to directory B ... repeat this until it crashes... sometimes it crashes right on begin, sometimes it needs 10 tries (I varied between 3 directories, moving to/from an attached smb-share increased chances - but this might be subjective).

So how to trace it down:

thunar -q
$ gdb thunar
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
...
(gdb) run
Starting program: /usr/bin/thunar 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffedf13700 (LWP 14974)]
[New Thread 0x7fffed712700 (LWP 14975)]
[New Thread 0x7fffe4f46700 (LWP 14984)]
[New Thread 0x7fffd20fb700 (LWP 14989)]
[New Thread 0x7fffd18fa700 (LWP 14990)]
...
[New Thread 0x7fffd18fa700 (LWP 15039)]
[Thread 0x7fffc37fe700 (LWP 15017) exited]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff5445d80 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
(gdb) backtrace
#0  0x00007ffff5445d80 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#1  0x00007ffff54449cd in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2  0x00007ffff5444a39 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3  0x00007ffff5443ea7 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#4  0x00007ffff5444675 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#5  0x00007ffff542d539 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#6  0x00007ffff542df86 in dbus_connection_get_dispatch_status () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#7  0x00007ffff5671cc3 in ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
#8  0x00007ffff4b9e68d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007ffff4b9ef03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007ffff4b9f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007ffff6a28447 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#12 0x0000555555577809 in ?? ()
#13 0x00007ffff4593ec5 in __libc_start_main (main=0x5555555772e0, argc=1, argv=0x7fffffffe478, init=<optimized out>, 
    fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe468) at libc-start.c:287
#14 0x0000555555577882 in ?? ()
(gdb)

EDIT, adding last lines of strace (full file was 16mb and contained private data - filenames, directories ... so I wont post it on pastebin)

poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
futex(0x7f457d647280, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f457d647280, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f4538015784, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f4538015780, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f45380138f0, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 1 ([{fd=4, revents=POLLIN}])
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{"$\t\1\0&\0\2\0\265\0\0\0", 12}, {NULL, 0}, {"", 0}], 3) = 12
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\1\1!\303\0\0\0\0\265\0\0\0\304U\214\0\224\0\17\2\224\0\17\2\20\0\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, 0x7fff9402f4b0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, 0x7fff9402f4b0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{"&\t\2\0\304U\214\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\1\1\"\303\0\0\0\0\265\0\0\0\4\0\240\3\224\0\17\2\224\0\17\2\20\0\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, 0x7fff9402f4b0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, 0x7fff9402f4b0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{"&\t\2\0\4\0\240\3", 8}, {NULL, 0}, {"", 0}], 3) = 8
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\1\1#\303\0\0\0\0\265\0\0\0\0\0\0\0\224\0\17\2\224\0\367\1\20\0\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, 0x7fff9402f4b0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, 0x7fff9402f4b0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{"%\t\1\0", 4}, {NULL, 0}, {"", 0}], 3) = 4
recvmsg(3, 0x7fff9402f510, 0)           = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{"&\t\2\0t\23\240\3", 8}, {NULL, 0}, {"", 0}], 3) = 8
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\1\1%\303\0\0\0\0\265\0\0\0\0\0\0\0\224\0\17\2\370\0s\2\20\0\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, 0x7fff9402f4b0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, 0x7fff9402f4b0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{"&\t\2\0\4\0\240\3", 8}, {NULL, 0}, {"", 0}], 3) = 8
poll([{fd=3, events=POLLIN}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\1\1&\303\0\0\0\0\265\0\0\0\0\0\0\0\224\0\17\2\224\0\367\1\20\0\0\0\0\0\0\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, 0x7fff9402f4b0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, 0x7fff9402f4b0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 1 ([{fd=4, revents=POLLIN}])
read(4, "\2\0\0\0\0\0\0\0", 16)         = 8
futex(0x7f453800ad74, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f453800ad70, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f4538004ce0, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
read(4, 0x7fff9402fa80, 16)             = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 0 (Timeout)
poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=6, events=POLLIN}, {fd=30, events=POLLIN}, {fd=5, events=POLLIN}], 5, 0) = 1 ([{fd=3, revents=POLLIN}])
poll([{fd=3, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=3, revents=POLLIN|POLLOUT}])
recvmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{"\6\0&\303\n6\345/\265\0\0\0\4\0\240\3\0\0\0\0\225\0\20\2\225\0\370\1\20\0\1\0", 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
writev(3, [{"\2\t\4\0\4\0\240\3\0@\0\0\0\0\0\0\2\6\4\0\4\0\240\3\0@\0\0\0\0\0\0", 32}, {NULL, 0}, {"", 0}], 3) = 32
recvmsg(3, 0x7fff9402f8e0, 0)           = -1 EAGAIN (Resource temporarily unavailable)
close(5 <unfinished ...>
+++ killed by SIGSEGV (core dumped) +++

EDIT2: I think the following portion of strace is what defined file descriptor #5 (lines 1.244-1.248 of 165.000)

connect(5, {sa_family=AF_LOCAL, sun_path=@"/tmp/dbus-vpvAWZGKFu"}, 23) = 0
fcntl(5, F_GETFL)                       = 0x2 (flags O_RDWR)
fcntl(5, F_SETFL, O_RDWR|O_NONBLOCK)    = 0
geteuid()                               = 1000
getsockname(5, {sa_family=AF_LOCAL, NULL}, [2]) = 0

So this seems more and more to be related to libdbus.

Sorry for posting the content here instead of a bug report, but this removes the hassle to file a complete bug report - which I just do not have the time for now.

Hope that helps somehow,

bye
Ron

Last edited by GWR (2015-02-06 14:41:38)

ToZ · 2015-02-06 15:19:05

Looks like this bug.

GWR · 2015-02-06 15:41:30

Sometimes it is hard to find existing bug reports because you search with the wrong keywords.

"Nautilus" got an update the last weeks too (here on linux mint xfce) ... they had a copy-past-file->bug too. Was glad when seeing the update, until I recognized it was for Nautilus ... and I was using Thunar tongue

So ... sorry for writing to this topic instead of adding useful information to the bug report (if this is the same thing, which I think is).

bye
Ron

ToZ · 2015-02-06 17:35:47

GWR wrote:

So ... sorry for writing to this topic instead of adding useful information to the bug report (if this is the same thing, which I think is).

No worries. Your stack traces contained the information to help locate the most likely culprit of the bug. It will be helpful information to the community at large. And you are correct, it is difficult to find the correct bug reports.

gregg128 · 2015-02-23 16:30:46

Any news about this bug? 1.6.4 is unusable now, I needed to downgrade to 1.6.3 sad

ToZ wrote:

GWR wrote:
So ... sorry for writing to this topic instead of adding useful information to the bug report (if this is the same thing, which I think is).
No worries. Your stack traces contained the information to help locate the most likely culprit of the bug. It will be helpful information to the community at large. And you are correct, it is difficult to find the correct bug reports.

ungutknut · 2015-02-23 18:18:27

gregg128 wrote:

Any news about this bug? 1.6.4 is unusable now, I needed to downgrade to 1.6.3

I really thought this bug was eliminated in 1.6.5 when it came out a few days ago.

But after some time using it I found out it "just" got better: with 1.6.4 the crashing-probability when copy/pasting was about 50% on my system; now with 1.6.5 it seems to have decreased to about 20% (and I can only reproduce it with ctrl+c/v - drag&drop now works all the time... coincidence?). That's still not usable but I'm sure the devs are working hard on it as rumors tell that the xfce-team plans to finish 4.12 within february.

ToZ · 2015-02-23 18:22:22

I think that any news would come from that bug report. Reading the report, it looks there are some issues reproducing the bug. Perhaps you can offer to assist?

GWR · 2015-02-26 08:44:00

I did not see any changes regarding this issue with the latest version on Linux Mint. Only visible change (for me) was the removal of running "marked as executable" scripts right from Thunar (for whatever reason someone thought this is a good idea to "just remove" that ...).

bye
Ron

ToZ · 2015-02-26 11:39:54

GWR wrote:

I did not see any changes regarding this issue with the latest version on Linux Mint. Only visible change (for me) was the removal of running "marked as executable" scripts right from Thunar (for whatever reason someone thought this is a good idea to "just remove" that ...).

bye
Ron

The bug has not yet been resolved. There are some issues with the developers being able to reproduce it. Therefore any potential fix will not yet be available.

The problem seems to be that it is difficult to replicate. For instance, I can't seem to replicate the issue on my system. Thats not to say that the issue is not a valid one, just that its difficult to replicate.

If anyone who is experiencing this bug could also offer to work with the developer in that bug report, they may be able to locate the issue quicker.

GWR · 2015-02-26 16:27:57

The problem is for us "helpers" the same: we cannot replicate it everytime - else we would of course provide a guide to reach the bugged spot. I also receive "game crashes" reports without further info. Ends often with me trying hours to replicate things.

My last post wasnt meant offending, I just wanted to state, that I assume the "bug" not to be ironed out already (because it was not mentioned in the changelogs).

Regarding "reproduceability": I think it has to do with some lib changes - but I assume that these libs are the same for all - when running the same distribution (Linux Mint 17 64Bit xfce edition here). Maybe devs are running another distro with another "libdbus"-revision.

BTW my libdbus is:

lrwxrwxrwx 1 root root      18 Nov 25 21:38 libdbus-1.so.3 -> libdbus-1.so.3.7.6
-rw-r--r-- 1 root root  281552 Nov 25 21:38 libdbus-1.so.3.7.6

bye
Ron

Last edited by GWR (2015-02-26 16:30:55)

ToZ · 2015-02-26 18:49:49

I'm sorry if I gave the impression that I was offended - I was not. I was just recapping the current state of the bug.

It is quote possible, as you say, that it is some intermediary component that is causing the bug. On this system, Arch Linux, I've got:

$ pacman -Qi libdbus
Name           : libdbus
Version        : 1.8.16-2

On my Xubuntu 14.10 system, I have:

$ apt-cache policy libdbus-1-3
libdbus-1-3:
  Installed: 1.8.8-1ubuntu2.1

Unfortunately, I cannot replicate this bug on either of these two systems.

alcornoqui · 2015-02-26 19:20:16

Hello. I'd like to help debug this. I'm currently running two Xubuntu systems, one has the bug and the other doesn't seem to.

The bug-free system is a netbook using Xubuntu 14.04.1 (32 bits/i686) with Intel graphics, no propietary drivers, and the 4.12 Xfce repo.

The buggy one, a laptop, has the 64 bits (x86-64) version of Xubuntu, nVIDIA graphics (with driver version 331.113), and also Thunar 1.65 (same repo as the netbook).

I'll read the whole threads and report back...

GWR · 2015-02-28 13:08:54

@ offending
No problem, did not really expect someone to be offended, but the last weeks I often had to excuse for myself sometimes writing a bit rude or "interpretable" (not my mother tongue).

hmm apt-cache.

$ apt-cache policy libdbus-1-3
libdbus-1-3:
  Installiert:           1.6.18-0ubuntu4.3
  Installationskandidat: 1.6.18-0ubuntu4.3
  Versionstabelle:
 *** 1.6.18-0ubuntu4.3 0
        500 http://ftp-stud.hs-esslingen.de/ubuntu/ trusty-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
        100 /var/lib/dpkg/status
     1.6.18-0ubuntu4 0
        500 http://ftp-stud.hs-esslingen.de/ubuntu/ trusty/main amd64 Packages

As you see I am running with locale "deDE" (which shouldnt affect the whole thing). Seems I have "1.6.18" installed. Always thought the "***.so"-names show which kind of version is installed.

Also I do not run "Xubuntu" but "Linux Mint" (64bit). Think my Xubuntu boxes do not have that bug either, at least I did not recognize that bug when "cleaning up" the computers of my parents (btw: 32bit variant installed there).

bye
Ron

linux-man · 2015-03-03 19:23:05

Another thunar crash message (Xubuntu 14.04 64 upgraded today to 4.12 with ppa:xubuntu-dev/xubuntu-staging and ppa:xubuntu-dev/xfce-4.12):

process 6691: arguments to dbus_message_get_reply_serial() were incorrect, assertion "message != NULL" failed in file ../../dbus/dbus-message.c line 1090.
This is normally a bug in some application using the D-Bus library.

Most of the time, thunar crashes while copying with a simple segmentation fault message.

Last edited by linux-man (2015-03-03 19:24:41)

MountainDewManiac · 2015-03-03 21:55:51

linux-man wrote:

Another thunar crash message

I hope that you (and everyone else) are filing bug reports here:

https://bugzilla.xfce.org/

Or adding information, if there is already one filed that fits. See:

https://bugzilla.xfce.org/buglist.cgi?quicksearch=thunar

Regards,
MDM

ToZ · 2015-03-05 11:37:28

Unfortunately, I don't think we are going to solve the dev/user issue here on this thread, and this thread is wandering from its initial purpose. Lets return back to focusing on the issue at hand - thunar crashing.

Reading through the bug report, I'm seeing that a large number of people experiencing the bug are using the 4.12 PPA.

GWR · 2015-03-05 14:30:24

I do not use any ppa but the one provided by Linux Mint 17 "Qiana".
EDIT: ok, I am using the "ppa:xubuntu-dev/xfce-4.12" too (somehow my repos wont get listed via gui atm but saw it when comparing version strings with local install and vm).

I assume many devs are using other distros. I only have VMs with older distros running and they do not have these issues (12.04 based ones to keep lib-issues away from my precompiled binaries).

Will setup a new VM with Mint 17 64bit now ...

@dev/user-issue:
Feel free to extract them into a new thread to keep this thread a bit more non-derailed big_smile

Last edited by GWR (2015-03-05 15:42:29)

ToZ · 2015-03-05 14:37:25

GWR wrote:

@dev/user-issue:
Feel free to extract them into a new thread to keep this thread a bit more non-derailed

Done: https://forum.xfce.org/viewtopic.php?id=9456.

Xfce Forum

Sub domains

#1 2015-01-29 21:07:29

Thunar 1.6.4 crashes when copying files

#2 2015-01-30 03:57:40

Re: Thunar 1.6.4 crashes when copying files

#3 2015-01-30 08:59:21

Re: Thunar 1.6.4 crashes when copying files

#4 2015-01-30 11:43:49

Re: Thunar 1.6.4 crashes when copying files

#5 2015-01-31 19:13:05

Re: Thunar 1.6.4 crashes when copying files

#6 2015-01-31 20:49:01

Re: Thunar 1.6.4 crashes when copying files

#7 2015-02-01 18:30:53

Re: Thunar 1.6.4 crashes when copying files

#8 2015-02-06 14:22:47

Re: Thunar 1.6.4 crashes when copying files

#9 2015-02-06 15:19:05

Re: Thunar 1.6.4 crashes when copying files

#10 2015-02-06 15:41:30

Re: Thunar 1.6.4 crashes when copying files

#11 2015-02-06 17:35:47

Re: Thunar 1.6.4 crashes when copying files

#12 2015-02-23 16:30:46

Re: Thunar 1.6.4 crashes when copying files

#13 2015-02-23 18:18:27

Re: Thunar 1.6.4 crashes when copying files

#14 2015-02-23 18:22:22

Re: Thunar 1.6.4 crashes when copying files

#15 2015-02-26 08:44:00

Re: Thunar 1.6.4 crashes when copying files

#16 2015-02-26 11:39:54

Re: Thunar 1.6.4 crashes when copying files

#17 2015-02-26 16:27:57

Re: Thunar 1.6.4 crashes when copying files

#18 2015-02-26 18:49:49

Re: Thunar 1.6.4 crashes when copying files

#19 2015-02-26 19:20:16

Re: Thunar 1.6.4 crashes when copying files

#20 2015-02-28 13:08:54

Re: Thunar 1.6.4 crashes when copying files

#21 2015-03-03 19:23:05

Re: Thunar 1.6.4 crashes when copying files

#22 2015-03-03 21:55:51

Re: Thunar 1.6.4 crashes when copying files

#23 2015-03-05 11:37:28

Re: Thunar 1.6.4 crashes when copying files

#24 2015-03-05 14:30:24

Re: Thunar 1.6.4 crashes when copying files

#25 2015-03-05 14:37:25

Re: Thunar 1.6.4 crashes when copying files

Board footer