On 04/06/2015 02:31 PM, John Andersen wrote:
In all seriousness, I have actually see this happen in the past, the notification gets stuck if you launch something else that grabs the device before dismissing the notification, or using one of the options it offers.
I've seen it with external USB hard drives more often than other devices.
I know just enough about this to get in trouble, and not much more, but this may be an area that needs watching by our systemd/polkit/udisk/udisk2/etc.. gurus. One of the areas where the sysVinit/systemd/consolekit/noconsolekit transition is particularly murky is user session tracking/user device control/management. I have not kept up with all the names of the new tools currently in use on the various distros that control this wizardry, but I've ventured off into the deep-end of freedesktop.org working with Trinity not too long ago. The extent of my understanding is that as systemd is implemented and consolekit goes away and the various pieces change [1], the framework to provide user control to mount/unmount various hardware devices, etc. will have to be reworked due to the new tools having to take over for function that consolekit provided in the past. [2] A side-effect of this is that many apps like wee-d-git, etc. may have to update the way they check the status of the devices they monitor for setting indication just as Basil indicates. Like I said above, I know just enough about this to get in trouble, so I cannot be sure this even applies to wee-d-git, but in general this type issue is something to keep an eye on and report about when things like this happen that can't otherwise be explained. P.S. Isn't 'wee-d-git' synonymous with "dime-bag?" footnotes: [1] 13.1 retained consolekit with systemd [2] similar to the migration away from HAL, etc. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org