to initiate a reboot, must enter root password

Hello all,

on my Acer Aspire one laptop, running openSUSE 12.2 and KDE 4.8.5, when
I try and initiate a reboot from KDE, after KDE exits and it is on the
green screen (the display manager?), a dialog box pops up saying that
root authorization is required to initiate a reboot. It does the same
thing for a shutdown.

If I do a logout from KDE and then at kdm I try and select shutdown or
power off, I get the same dialog box requesting authorization. However,
if I do it that way, the keyboardis suddenly disabled and I am not able
to type anything into the box.

I looked in yast to see if I could find the system configuration setting
to allow the user to initiate a shutdown, but I couldn’t figure out
where to look. Any ideas?

George

In kde > System Settings > Login Screen > Shutdown

On the left side for Local it should = Everybody
Halt = /sbin/shutdown -h -P now

Is that what you see?

I have the same as the op, Caf. In ‘Configure Desktop’ > login Screen>shutdown it shows as you describe…

On 01/16/2013 01:06 PM, caf4926 wrote:
> In kde > System Settings > Login Screen > Shutdown
>
> On the left side for Local it should = Everybody
> Halt = /sbin/shutdown -h -P now
>
> Is that what you see?
>
>
Yes, for local it says Everybody, and the halt is as you wrote there. It
also says that remote shutdown is only root, but I don’thave ssh enabled
on this laptop.

If you create a new user and try from there
Does it work?

On 01/16/2013 06:36 PM, caf4926 wrote:
> If you create a new user and try from there
> Does it work?
>
>
Sorry for the wait on long response. I was out of the office on business
a few days and couldn’t get back to my daughter’s computer.

We tried creating a new user, and it still requires the superuser
password to shutdown (but only from the kdm screen - it shuts down fine
if shutting down from directly within KDE Plasma Workspace).

Here is a pic of what I am seeing when we try to shutdown or reboot from
the kdm screen:

http://picpaste.com/2584_0_IMG_7680-2cG1vENv.JPG

Can we see result of

uname -a
zypper lr -d

Ok, here is the results of those:


xxxxxx@linux-nkgv:~> uname -a
Linux linux-nkgv.site 3.4.11-2.16-desktop #1 SMP PREEMPT Wed Sep 26 17:05:00 UTC 2012 (259fc87) x86_64 x86_64 x86_64 GNU/Linux

and the repositories:


xxxxxx@linux-nkgv:~> zypper lr -d
#  | Alias                     | Name                               | Enabled | Refresh | Priority | Type     | URI                                                               | Service
---+---------------------------+------------------------------------+---------+---------+----------+----------+-------------------------------------------------------------------+--------
 1 | Downloads                 | Downloads                          | Yes     | Yes     |   99     | plaindir | dir:///home/abby/Downloads                                        |        
 2 | google-chrome             | google-chrome                      | Yes     | Yes     |   99     | rpm-md   | http://dl.google.com/linux/chrome/rpm/stable/x86_64               |        
 3 | graphics                  | graphics                           | Yes     | Yes     |   99     | rpm-md   | http://download.opensuse.org/repositories/graphics/openSUSE_11.4/ |        
 4 | libdvdcss                 | libdvdcss                          | Yes     | Yes     |   99     | rpm-md   | http://opensuse-guide.org/repo/12.2/                              |        
 5 | packman                   | packman                            | Yes     | Yes     |   99     | rpm-md   | http://packman.inode.at/suse/openSUSE_12.2/                       |        
 6 | repo-debug                | openSUSE-12.2-Debug                | No      | Yes     |   99     | NONE     | http://download.opensuse.org/debug/distribution/12.2/repo/oss/    |        
 7 | repo-debug-update         | openSUSE-12.2-Update-Debug         | No      | Yes     |   99     | NONE     | http://download.opensuse.org/debug/update/12.2/                   |        
 8 | repo-debug-update-non-oss | openSUSE-12.2-Update-Debug-Non-Oss | No      | Yes     |   99     | NONE     | http://download.opensuse.org/debug/update/12.2-non-oss/           |        
 9 | repo-non-oss              | openSUSE-12.2-Non-Oss              | Yes     | Yes     |   99     | yast2    | http://download.opensuse.org/distribution/12.2/repo/non-oss/      |        
10 | repo-oss                  | openSUSE-12.2-Oss                  | Yes     | Yes     |   99     | yast2    | http://download.opensuse.org/distribution/12.2/repo/oss/          |        
11 | repo-source               | openSUSE-12.2-Source               | No      | Yes     |   99     | NONE     | http://download.opensuse.org/source/distribution/12.2/repo/oss/   |        
12 | repo-update               | openSUSE-12.2-Update               | Yes     | Yes     |   99     | rpm-md   | http://download.opensuse.org/update/12.2/                         |        
13 | repo-update-non-oss       | openSUSE-12.2-Update-Non-Oss       | Yes     | Yes     |   99     | rpm-md   | http://download.opensuse.org/update/12.2-non-oss/                 |        
abby@linux-nkgv:~> 


That looks perfect.

So. Just to be clear.
You can shutdown from the desktop but not from the login screen?

I’m not sure this is related. But how many users are there? And are you the original user that created the system? And have you ever logged in as root?

We tried creating a new user, and it still requires the superuser
password to shutdown (but only from the kdm screen - it shuts down fine
if shutting down from directly within KDE Plasma Workspace).]

Post the output of

grep -i DISPLAYMANAGER_SHUTDOWN /etc/sysconfig/displaymanager

You may need to check the settings in

YaST >> System >> /etc/sysconfig Editor

Navigate to System >> Security >> Permissions >> PERMISSION SECURITY and check the settings there.

On 01/21/2013 07:36 AM, caf4926 wrote:
> That looks perfect.

hmmmm…is there supposed to be an enabled “libdvdcss” from
http://opensuse-guide.org/repo/12.2/


dd
openSUSE®, the “German Engineered Automobile” of operating systems!

It’s fine, either way.


> grep -i DISPLAYMANAGER_SHUTDOWN /etc/sysconfig/displaymanager
DISPLAYMANAGER_SHUTDOWN=""
# that root can never login if DISPLAYMANAGER_SHUTDOWN is "auto" and
>

I also noticed that the DISPLAYMANAGER_SHUTDOWN parameter is not listed in yast /etc/sysconfig/ editor

I have changed that parameter to “auto” (my desktop had it set to auto and did not have this problem). I will reboot and see if this fixes the problem.

thanks!
G.O.

On 01/22/2013 11:16 AM, golson765 wrote:
>
>
> I also noticed that the DISPLAYMANAGER_SHUTDOWN parameter is not listed
> in yast /etc/sysconfig/ editor
>
> I have changed that parameter to “auto” (my desktop had it set to auto
> and did not have this problem). I will reboot and see if this fixes the
> problem.
>
> thanks!
> G.O.
>
>
That worked - I can now shutdown as a regular user. Thanks!

However, I now have a new problem - I cannot get past the kdm screen. Whenever I try and log in to any desktop, immediately after entering the login data, the screen, keyboard, and mouse freeze there at the green kdm screen and will not let me in to any desktop. I tried changing the parameter above back to blank, and it still did the same thing. I also tried changing it to “all” and it did the same thing.

So I booted into runlevel 3 (or the equivalent when in systemd) and logged in as root to change the display manager to kdm3. Then as root I typed in “systemctl reboot”, and the terminal locked up, just the same way that the kdm screen locked up.

And now even with kdm3 as the display manager, the system locks up when I try and get into the desktop.

I guess I better start a new thread on this one.


G.O.
Box #1: 12.2 | KDE 4.9.2 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.1 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.2 | KDE 4.9.2 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

Can you start up in failsafe mode?

Do a Console Login
Then switch to su -
Start yast with: yast

Create a new user
quit yast
reboot

try login with new user
or if you still have a test user from earlier, just try that…