Thanks for the explanation. I see the point, but I still find that the rationale at best incomplete.
Assume that there is an offending application A (legacy, commercial, cad, simply old like eee-control, etc). - if one has not installed A, sticking to what is in the ubuntu official repos, it does not make any difference if A is blacklisted or not. Blacklisting it does not change the user experience, because a non installed application cannot result in unconsistent behavior of any sort - if one has installed A, having it whitelisted means that the user will get some minor unconsistent behavior. However, having installed something that is not official he should be obviously prepared to it. And in any case, from the very notification area he should immediately spot what is the offending application. Conversely, having everything blacklisted by default means one of the two: 1) if the user is lucky, A does not run at all. 2) if the user is not lucky, and this is the most likely case, A will run anyway, with the catch that it will not be able to provide any important notifications to the user. In my case, I simply could not realize that eee-control was running. I was seeing the machine extra-sluggish and thinking that natty was to blame. As a matter of fact, the issue was that eee-control-daemon was running and setting the machine to extreme powersaving. But of course I could not get any feedback on that. I wasn't even aware that eee-control was running. I had to use use ps to realize it (and a standard user should not be expected to be able to do that). Even worse, imagine a scenario were a legacy backup application tries to use a notification to activate/deactivate some "extra-dangerous-overwrite-mode" or a cloud service to say "syncronization to the cloud failed". What if there is around some perfect (but not ubuntu compliant) disk cleaning application that periodically wipes part of the home, with a behavior that is selectable via the notification area? Can one definitely exclude that there is something like that on the net and that a user will not run the risk of much more serious misbehaviors or data losses because of the blacklisting? So, rather than merely blacklisting, please at least assure that when a blacklisted application tries to notify something, a standard notification appears saying "App so and so using the old notification protocol. This is deprecated and turned off by default. Use gconf if you want to whitelist the app" or something like that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/773979 Title: legacy applications (using system tray) do not work in unity without a porting effort -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
