Jannis Pohlmann wrote: > Hi Benny, > > I just checked out libexo and thunar from /trunk and played around with > them a little bit. When opening some PDFs I noticed that, (almost) > whenever I opened a file, Thunar is closed. Notice the "almost", which > means that it doesn't happen all the time. > > My first guess is that it may depend on whether I set up the mime-type > to be opened with a custom program. But I'm unsure about this and I > can't proof this theory. > > See below for a backtrace of the crash. > > Program received signal SIGABRT, Aborted. > [Switching to Thread -1219017024 (LWP 8008)] > 0xffffe410 in __kernel_vsyscall () > (gdb) backtrace > #0 0xffffe410 in __kernel_vsyscall () > #1 0xb775c9b1 in raise () from /lib/tls/i686/cmov/libc.so.6 > #2 0xb775e2c9 in abort () from /lib/tls/i686/cmov/libc.so.6 > #3 0xb77906ea in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6 > #4 0xb7796f54 in malloc_trim () from /lib/tls/i686/cmov/libc.so.6 > #5 0xb77972ca in free () from /lib/tls/i686/cmov/libc.so.6 > #6 0xb78a0054 in g_free () from /usr/lib/libglib-2.0.so.0 > #7 0xb78b286b in g_strfreev () from /usr/lib/libglib-2.0.so.0 > #8 0xb7ed80e1 in thunar_vfs_exec_on_screen (screen=0x80c43d8, > working_directory=0x81429f8 "/home/jannis", argv=0x831dc28, envp=0xbfe19a5c, > flags=G_SPAWN_SEARCH_PATH, startup_notify=4, error=0xbfe18268) at > thunar-vfs-exec.c:462
Hm, dunno why it crashes here, but there was indeed a bug in that function. Can you try again? BTW: Is Thunar compiled with startup-notification support? Benedikt _______________________________________________ Thunar-dev mailing list [email protected] http://foo-projects.org/mailman/listinfo/thunar-dev
