Description of problem: Opening Thunar first time after login has some delay and abrt reports a crash, even though it opens (I see it's the daemon that crashes). Could be related to tumbler too as it gave some issues the first times I opened Thunar. I just upgraded from F17 to f18. I was using Xfce 4.10 in F17 but tumbler was upgraded. Will check how this will develop but I'm reporting because it's been happening all day when opening Thunar for the first time. Version-Release number of selected component: Thunar-1.4.0-3.fc18 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: poll kernel: 3.6.6-3.fc18.i686 truncated backtrace: :Thread no. 2 (6 frames) : #1 poll at ../sysdeps/unix/syscall-template.S:81 : #3 g_poll at gpoll.c:132 : #4 g_main_context_poll at gmain.c:3584 : #7 gdbus_shared_thread_func at gdbusprivate.c:277 : #8 g_thread_proxy at gthread.c:797 : #9 ?? at /usr/lib/nvidia/libGL.so.1
Created attachment 640932 [details] File: core_backtrace
Created attachment 640933 [details] File: environ
Created attachment 640934 [details] File: event_log
Created attachment 640935 [details] File: backtrace
Created attachment 640936 [details] File: limits
Created attachment 640937 [details] File: cgroup
Created attachment 640938 [details] File: executable
Created attachment 640939 [details] File: maps
Created attachment 640940 [details] File: dso_list
Created attachment 640941 [details] File: build_ids
Created attachment 640942 [details] File: var_log_messages
Created attachment 640943 [details] File: open_fds
Created attachment 640944 [details] File: proc_pid_status
I think this was a false alarm, Kevin. I use the nvidia driver and due to bug #873220 nouveau is not blacklisted. This mixture of drivers is what I presume was crashing thunar. I rebuilt initramfs omitting nouveau and now thunar didn't crash and opened quickly. Since thunar --daemon was invariably crashing the first time thunar was opened it will be easy to check if this is solved in a few logins. Then if it's the case I close the bug.
This is happening almost every time I open Thunar for the first time in a session. The following times it opens quickly and ABRT (Fedora bug reporting tool) doesn't report a crash. It started to happen after I upgraded from Fedora 17 to Fedora 18. I was already using Thunar 1.4.0 in F17 and I've cleared Thunar's config. folder. Maybe it's GVFS related? backtrace_rating: 4 Package: Thunar-1.4.0-3.fc18 OS Release: Fedora release 18 (Spherical Cow)
Should I open a bug report in Xfce bugzilla and point to this one here?
Here's an output of opening Thunar for the first time in the session (and thus making the daemon crash as usual) with gdb: (gdb) run Starting program: /usr/bin/Thunar [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". [New Thread 0xb36c3b40 (LWP 1020)] warning: cannot close "/usr/lib/gio/modules/libgiofam.so": Invalid operation warning: cannot close "/lib/libfam.so.0": Invalid operation [New Thread 0xad550b40 (LWP 1039)] [New Thread 0xacbffb40 (LWP 1040)] [New Thread 0xac3feb40 (LWP 1041)] [Thread 0xac3feb40 (LWP 1041) exited] warning: cannot close "/usr/lib/thunarx-2/thunar-apr.so": Invalid operation warning: cannot close "/usr/lib/thunarx-2/thunar-archive-plugin.so": Invalid operation warning: cannot close "/usr/lib/thunarx-2/thunar-sbr.so": Invalid operation warning: cannot close "/lib/libexif.so.12": Invalid operation warning: cannot close "/usr/lib/thunarx-2/thunar-wallpaper-plugin.so": Invalid operation [Thread 0xad550b40 (LWP 1039) exited] [Thread 0xacbffb40 (LWP 1040) exited] warning: cannot close "/usr/lib/thunarx-2/thunar-uca.so": Invalid operation [Thread 0xb36c3b40 (LWP 1020) exited] [Inferior 1 (process 1001) exited normally] This is without Thunar debuginfo installed.
Can you generate a stacktrace per https://fedoraproject.org/wiki/StackTraces and attach it?
I've installed Thunar debuginfo package now. I don't know if ABRT attaches the backtrace when a bug is a duplicate. Comment #15 was made with ABRT and it had generated its stuff but it didn't attach anything (first report I used the GNU debugger and the other I used the other two options, but anyway I didn't have the debuginfo package installed then). Anyway, yesterday I had an issue with the mixer plugin which wasn't detecting the default pulseaudio card (I uninstalled it, later will try to see if I can get it to work. alsamixer, pnmixer, everything detects the pulseaudio card, just xfce4-mixer has trouble with that...) and did a radical cleaning on all Xfce user configuration starting afresh. Of course 'Thunar --daemon' crashed as usual the first time Thunar was opened but later I enabled the 'save session' checkbox on logout (which was disabled all this time) because the (buggy) notes plugin needs to have a saved session otherwise the notes get all shuffled. Because of this now the session doesn't start 'Thunar --daemon' anymore (it was saved after it crashed) so the crash can't happen. The curious thing is that I can start the daemon manually and then open thunar and the daemon doesn't crash. If it did then it would be easy to get a backtrace but only 'Thunar --daemon' started from xfce4-session is the one that crashes (and it looks like it's hard-coded somewhere as it can't be disabled or changed in the settings editor). So we need to clear the saved session and make sure xfce4-session starts 'Thunar --daemon' to replicate this crash.
This has been solved for me with locally built exo 0.10/Thunar 1.6 Regarding the crash, the only way that *sometimes* Thunar --daemon from xfce4-session wouldn't crash the first time Thunar was opened was by launching Thunar/thunar from the command-line. I even set Thunar --daemon to auto-start in IceWM and the crash happened there too. Then I added a delay to the auto-start command (sleep 3.5 && Thunar --daemon) and it didn't crash any more. This might give some clue to knowledgeable folks. Now with exo 0.10/Thunar 1.6 I tried every way that before Thunar --daemon would invariably crash (menu 'File Manager', menu 'Thunar', keyboard shortcut, xfce4-appfinder) and it never crashed. It was built with all features enabled (besides regular Thunar 1.4 build-deps and xfce4-panel-devel I also installed startup-notification-devel and libgudev1-devel).
Closing this as it seems definitely fixed with exo 0.10/Thunar 1.6