On mar, 2009-04-28 at 08:44 -0600, Scott Barker wrote: > On 04/28/09 08:27, Yves-Alexis Perez wrote: > > When running as a foreground process, you didn't quit between the first > > connect and the second one, did you? > > In both cases (daemon and foreground), I left the thunar window open as > I unmounted, removed, reconnected and tried to remount the device.
Ok > > > It looks to me like a hal problem (device correctly appears in the > > kernel logs, but not in hal). > > Sorry - I should have noted that in the case of running thunar as a > daemon, it wouldn't even mount the device the first time I reconnected > it, so the log I sent in that case does not show repeated insertion and > removal. It seems that once a device has been inserted, mounted, and > unmounted, thunar as a daemon can no longer mount it anymore, while > thunar as a foreground process can. Doing lshal -m while thunar is > running as a daemon, and inserting and removing the device repeatedly, > hal is noticing it every time, while thunar continues to not mount the > device. So both hal logs are identical. Just, when running “as a daemon”, it'll refuse to mount the second time. Is that correct? > I just tried something different - I launched thunar as a daemon from a > terminal window, and then everything worked fine. So, the difference > seems to be launching thunar as a daemon via the window manager. I've > been launching it by going to the menu and choosing Settings -> File > Manager, which launches /usr/bin/Thunar --daemon if it is not already > running. Can you try running Thunar vs. thunar and Thunar --daemon vs. thunar --daemon. Double check there is no other instance running, wether with T or t. > > Of course, I've also been launching thunar from the window manager menu > as well (directly in the top-level menu as File Manager), so I'm not > sure what is different about how thunar is invoked between those two menus. The latter only runs Thunar (so if it's not already running as a daemon, it'll run a new instance and die when the window is closed). Cheers, -- Yves-Alexis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org