Following up on my last entry, it seems that the problem must exist in the way thunar is started when the thunar-settings script spawns thunar as a daemon. The problem always occurs when thunar is launched that way, and never occurs when run directly as a daemon, nor when run as a foreground process. Something to do with dbus-send or the way it invokes thunar?

--
Scott Barker       sc...@mostlylinux.ca
Linux Consultant   http://www.mostlylinux.ca/scott



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to