[Bug 460449] New: xkvbd cannot be shut down by normal user
https://bugzilla.novell.com/show_bug.cgi?id=460449 Summary: xkvbd cannot be shut down by normal user Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: bryeny@mi-tech.com QAContact: qa@suse.de Found By: Community User With the tablet pattern installed on fresh 11.1 Tablet PC, xkvbd is started at login time. But user does not have the option to shut it down. It must only be shut down by root. This should be allowed for user to exit it as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=460449 User bryeny@mi-tech.com added comment https://bugzilla.novell.com/show_bug.cgi?id=460449#c1 Bryen Yunashko <bryeny@mi-tech.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|xkvbd cannot be shut down by normal user |xvkbd cannot be shut down by normal user --- Comment #1 from Bryen Yunashko <bryeny@mi-tech.com> 2008-12-18 16:09:57 MST --- oops, I meant xvkbd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=460449 User bryeny@mi-tech.com added comment https://bugzilla.novell.com/show_bug.cgi?id=460449#c2 --- Comment #2 from Bryen Yunashko <bryeny@mi-tech.com> 2008-12-18 21:53:00 MST --- Additional annoying behavior. - When going into screensaver or powersave mode, the keyboard comes back! Ack. I thought I killed you! What do I have to do? burn a cross into my screen? :-) - When it comes back, the titlebar over the keyboard is gone, unlike when it first started at bootup time. Thus, no access to the minimize button. For a user who is annoyed by this behavior but doesn't know enough how to kill it each time and resorts to minizing, this is truly going to extremely annoying. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=460449 User rodrigo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=460449#c3 Rodrigo Moya <rodrigo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rodrigo@novell.com AssignedTo|bnc-team-gnome@forge.provo.novell.com |rodrigo@novell.com Status|NEW |ASSIGNED Priority|P5 - None |P3 - Medium --- Comment #3 from Rodrigo Moya <rodrigo@novell.com> 2008-12-24 03:11:22 MST --- the screensaver unlock dialog spawns it again to allow auth via it also, so this is normal. What is not is xvkbd not being killed after successful auth -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=460449 User mcfrost@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=460449#c4 Uwe Winter <mcfrost@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mcfrost@web.de --- Comment #4 from Uwe Winter <mcfrost@web.de> 2009-01-06 19:03:34 MST --- Rodrigo. Do you know how the xvkbd program is spawned? Which config or binary is responsible for spawning xvkbd? Since this one really bugs me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=460449 User bryeny@mi-tech.com added comment https://bugzilla.novell.com/show_bug.cgi?id=460449#c5 --- Comment #5 from Bryen Yunashko <bryeny@mi-tech.com> 2009-01-06 21:28:00 MST --- Uwe. Seems to me that this gets re-spawned if screensaver has lock enabled. I switched it to blank screensaver/no lock, and the problem goes away. Of course, there's still the problem of it staying in place after initial login. (/me wonders if the problem would go away if I set it to auto-login, which I don't wish to set up.) I could just as easily remove xvkbd as I know others have done, but I'm leaving it in place at personal burden :-) so I can test with rodrigo when a patch comes out. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=460449 User rodrigo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=460449#c6 Rodrigo Moya <rodrigo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |bryeny@mi-tech.com --- Comment #6 from Rodrigo Moya <rodrigo@novell.com> 2009-01-08 04:16:22 MST --- Yes, gnome-screensaver spawns it for the lock dialog, and then kills it (using kill (xvkbd_pid, 9) in all exit code paths AFAICS, so not sure why it is staying. Maybe it was the previous instance run at the login screen? Or is it really been spawned by g-s? can you please confirm that -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com