Le dimanche 26 novembre 2006 à 12:31 +0000, geokok a écrit : > 1. The system was flawed since it was in a relatively "virgin" state, > meaning that I encountered the problem in a relatively fresh > installation the very first time i tried to add programs to the start up > list.
Your user is not authorized to change the permission of that folder that way and package do not change any user configuration, which means you runned an application with sudo which did that > 2. Others have encountered the problem as mentioned in the forums. It is > highly unlikely that we all screwed up the system in the same way!!! Why? How unlikely is it that some people runned the same program with sudo? > 3. I hardly knew at the time of the bug report how to change permissions > in the system as a user. U see, CLI was something unknown to me at the > time so I dont see how I could " break" it in that way......all I had > done before discovering the bug was installing some apps through > synaptic, such as Banshee and others, very mainstream apps.... One of that applications is broken then. Which one did you run with sudo? Banshee is an application non installed by default by example. It's likely that your problem comes from one application which is not from the default set because otherwise we would probably have a bunch of duplicate bugs about that -- No programs can be added in the startup list. https://launchpad.net/bugs/71200 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs