Steps to reproduce: 1. put a .desktop file on the desktop 2. open a terminal and rename this file Result: xfdesktop crashes with a delightful segfault
I forgot to mention it only happens sometimes.
Unable to reproduce. I'm gonna need a backtrace of the crash.
It seems to be a bit more complicated than that, and closely linked to bug 1701. Example: I open the property dialog for one .desktop file. I select the Launcher tab and change something. For any change I make, I see a new icon appearing on the desktop (some of them are not selectable). Then, if I sweep a window over them, I'm sure I get a crash with this message: (xfdesktop:11291): GLib-GObject-WARNING **: gsignal.c:1739: instance `0x82a3200' has no handler with id `596' sometimes, the crash also happens if I move the pointer over an icon or if I click. I suppose the crash isn't linked to renaming the files but more generally to any changes that occur on a .desktop file. I'll post an strace of the crash shortly. And my gtk+ version is 2.8.16
Created attachment 513 strace
here's my strace. In this case, it crashed in the following situation: - I had changed something in my .desktop file resulting in 3 or 4 copies of the same icon - I dragged one of the icons and it went mad
Sorry, not sure what that output is - an strace is just human-readable text. Regardless, I need a backtrace from gdb, not an strace. I'm not able to reproduce your issue. right-click -> properties -> launcher -> change something. And nothing happens. From the debug output, I see that the volume manager gets a "changed" event, and then it finds the file in its list of files on the desktop, and does nothing. Benny, any thoughts here?
Created attachment 515 gdb output here's the (bare) gdb output. I launched it with the following command: gdb --tty=~/debug.txt --exec=/usr/bin/xfdesktop -ex run -ex backtrace -ex kill -ex quit > gdb.txt
Created attachment 516 debug output and here's the debug output
I've seen the problem of multiple icons for the same file as well some time ago, but I haven't seen that for a while, so I thought it was fixed. I'm unable to reproduce that currently. I'm unable to tell anything from the debug output as I'm not very familar with what xfdesktop does.
*** This bug has been marked as a duplicate of 1701 ***