Bug 91706 - problem when configuring panel when running with "su -"
Summary: problem when configuring panel when running with "su -"
Status: ASSIGNED
Alias: None
Product: kiosk
Classification: Plasma
Component: kiosktool (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: geiseri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-19 20:43 UTC by Cp Hennessy
Modified: 2021-03-11 01:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cp Hennessy 2004-10-19 20:43:02 UTC
Version:           3.3.0 (using KDE KDE 3.3.0)
Installed from:    SuSE RPMs
OS:                Linux

If I run as root by using "su -" and then run "kiosktool" and then try to configure the panel, the old panel gets removed and a new panel is started as user root. However this causes all of the other windows on the screen to be scrolled upwards until they are unusable.
When I kill the kicker process started by root, another one is created and the same thing happens. Only when the second one is killed can I actually get back to the original kicker.
Comment 1 Waldo Bastian 2004-10-19 21:22:06 UTC
Any particular reason you run kiosktool as root?
Comment 2 Cp Hennessy 2004-10-20 11:21:52 UTC
No, except that I did not know that I could run as normal user. :(
I assumed that I had to be root.

I've tested as a normal user and have no problems.
However I imagine that this bug can be resolved with a warning/error that the user running kiosktool must be the same as the desktop user.
Comment 3 geiseri 2009-03-02 04:04:47 UTC
In KDE 4.x there is no more kicker.  That being said we will need to add better integration for the plasma panel in kiosktool.
Comment 4 Justin Zobel 2021-03-11 01:23:49 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.