[Thunar-dev] Crash in Thunar Rev 17355

[Benedikt Meurer]

Biju Chacko wrote:
> Hi,
> 
> I experience a crash when I attempt a rename using the file properties 
> dialog. This is consistent.
> 
> The backtrace:
> 
> (gdb) run
> Starting program: /opt/xfce4/bin/thunar
> Reading symbols from shared object read from target memory...done.
> Loaded system supplied DSO at 0xc86000
> [Thread debugging using libthread_db enabled]
> [New Thread -1208379712 (LWP 963)]
> [New Thread -1211221072 (LWP 966)]
> [Thread -1211221072 (LWP 966) exited]
> 
> Thunar-CRITICAL **: thunar_local_file_monitor: assertion 
> `thunar_vfs_uri_equal (local_file->info->uri, handle_uri)' failed
> aborting...
> 
> Program received signal SIGABRT, Aborted.
> [Switching to Thread -1208379712 (LWP 963)]
> 0x00c86402 in __kernel_vsyscall ()
> (gdb) bt
> #0  0x00c86402 in __kernel_vsyscall ()
> #1  0x006571f8 in raise () from /lib/libc.so.6
> #2  0x00658948 in abort () from /lib/libc.so.6
> #3  0x001b02d1 in g_logv () from /usr/lib/libglib-2.0.so.0
> #4  0x001b0305 in g_log () from /usr/lib/libglib-2.0.so.0
> #5  0x001b0441 in g_return_if_fail_warning () from /usr/lib/libglib-2.0.so.0
> #6  0x0806bbb4 in thunar_local_file_monitor (monitor=0x9ef0ce8,
>      handle=0x9efd894, event=THUNAR_VFS_MONITOR_EVENT_DELETED,
>      handle_uri=0x9ef4c70, event_uri=0x9ef4c70, user_data=0x9f0bec0)
>      at thunar-local-file.c:628
> #7  0x00dc12d5 in thunar_vfs_monitor_fam_event (monitor=0x9ef0ce8,
>      fe=0xbf9c41ac) at thunar-vfs-monitor.c:235
> #8  0x00dc13cf in thunar_vfs_monitor_fam_watch (channel=0x9ef2178,
>      condition=G_IO_IN, user_data=0x9ef0ce8) at thunar-vfs-monitor.c:275
> #9  0x001cd3ac in g_vasprintf () from /usr/lib/libglib-2.0.so.0
> #10 0x001a73ee in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
> #11 0x001aa3f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
> #12 0x001aa6e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
> #13 0x046341b5 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
> #14 0x0805408a in main (argc=1, argv=0xbf9c53f4) at main.c:101
> 
> Hope this helps -- doesn't look quite right to me. I suspect I have the 
> bt of the wrong thread.

No, it's the correct thread. Fixed now.

> -- b

Benedikt