Red Hat Bugzilla – Bug 511097
xpad replicates on desktop at startup even though turned off
Last modified: 2009-10-22 02:16:40 EDT
Created attachment 351490 [details]
Shows that xpad is not selected in startup setting
Description of problem: When logging into gnome on F11 x86_64, even though xpad is turned off in the startup menu, it still starts and generates 25 instances on the desktop.
Version-Release number of selected component (if applicable):
How reproducible: Every time I log in.
Steps to Reproduce:
1. Initially, xpad was turned on by default, only a single instance generated.
2. Turned off xpad in startup menu.
3. Xpad still started at login, now with many instances (25)
Xpad is started with many instances.
Xpad doesn't start.
Additional info: See attached png of setting and proliferation.
Created attachment 351491 [details]
Shows proliferation of xpad instances on desktop
I cant reproduce the bug on F11 x86. Its working as expected.
Even if i disable the automatic startup.
I have reported the bug to upstream. I will try to get the bug fixed.
Thank you for the report!
Thank you for the action. This is mostly an annoyance. I'll keep trying things to see if I can find a way to fix it.
The fact that you can't reproduce it makes it seem like it is something about my system causing it. And it is difficult to give good instructions because I didn't really pay attention to it until it started putting lots of them on the desktop. At first it was just one.
In System->Preferences->startup applications, I had selected
terminal in each window on start
When I removed that selection and instead selected
automatically remember running applications when logging out
the problem disappeared.
So a workaround.
(In reply to comment #4)
> When I removed that selection and instead selected
> automatically remember running applications when logging out
> the problem disappeared.
> So a workaround.
I think this is not only a workaround but also the cause of the problems. Have you turned on automatic session saving on logout or did you save the session before?
I've tried it with session saving, can't reproduce it.
Perhaps it was a mix of session saving and maloperation of the user that causes to this error.
I will try to reproduce it again, after you give me more info. Do you remember, what do you have done?
Seems to me, this is not a bug!
Actually, I have moved to Fedora 12/Rawhide for over a month now. This problem is not present with F12 as far as I can tell. And after I implemented the workaround described above, I didn't have the problem anymore on F11. So it seems like this bugzilla can be closed as notabug.
Thanks for your efforts.