Problems after upgrading to Gnome 2.24

Szelek · 2008-10-23 08:30:38

So, after huge update last night, i have a little mess in my system.
First of all cpu frequency scalling doesn't work. When laptop is on AC or on battery cpufreq always is set to ondemand.
Secondly my gnome/openbox session doesn't work. When I login the appereance is horrible, it looks like crap and metacity is still enabled, only when I open Appearance menu the system looks like standard gnome session. I've tried reinstalling openbox, with no results.
I hope that someone know what to do.

wonder · 2008-10-23 08:34:26

the new feature in gnome si consolekit and policykit. there are users that demand that to be added in arch.
go to system->preferences->authorization and there you will see Change Cpu Frequency scaling. Play with that. i add my user clicking on Grant
personaly i don't like that "new feature".

for the second problem, i don't know because i only use gnome

Last edited by wonder (2008-10-23 08:36:57)

tuxce · 2008-10-23 14:45:53

Szelek wrote:

Secondly my gnome/openbox session doesn't work. When I login the appereance is horrible, it looks like crap and metacity is still enabled, only when I open Appearance menu the system looks like standard gnome session. I've tried reinstalling openbox, with no results.
I hope that someone know what to do.

gnome changes the way he start different window manager, to enable openbox with gnome session (gnome in gdm, not gnome/openbox), you have to create openbox.desktop in /usr/share/applications:

[Desktop Entry]
Type=Application
Encoding=UTF-8
Name=OpenBox
Exec=openbox
NoDisplay=true
# name of loadable control center module
X-GNOME-WMSettingsModule=openbox
# name we put on the WM spec check window
X-GNOME-WMName=OpenBox

and set /desktop/gnome/session/required_components/windowmanager to "openbox" in gconf:

gconftool-2 -s -t string /desktop/gnome/session/required_components/windowmanager openbox

Szelek · 2008-10-23 16:41:08

Thanks tuxce, openbox window manager is working now, but i still can't get cpufreq scalling to work. I permitted myself to change cpufreq but nothing happanes when AC is (un)pluged in.

hoschi · 2008-11-03 21:01:34

Hello,
I am trying to add a "user" in policykit under "cpu frequency" and "suspend", but it is impossible because the grant button is alway greyed out. So I tryed to start as "root" gnome-control-center, but than I was not able to open policykit.

I don't use GDM or things like that, I just start X11 and Gnome with "startx".
Any idea?

zhuqin · 2008-11-03 22:52:59

Since 2.24, gnome-power-manager removed cpu scaling options, you'll have to put cpufreq into your rc.conf, and set ondemand as default.
Please check the wiki.

hoschi · 2008-11-04 20:12:35

Thats bad.
But I still need policytkit-permission for "suspend"!?

Why does the gnome-programmers invent a new wheel, instead of using simple POSIX-Compatible solutions = Groups?!
I hate them. Sometimes I think the gnome people want to force shell-users not the use GUI-Apps...

azleifel · 2008-11-04 21:39:48

Been there, including the whinging ;-) What do you have in /etc/PolicyKit/PolicyKit.conf? What I did to fix my PolicyKit-related problems is here. There's also a man page for PolicyKit.conf and it's worth a read.

hoschi · 2008-11-04 22:14:43

Here it is:

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->

<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">

<!-- See the manual page PolicyKit.conf(5) for file format -->

<config version="0.1">
</config>

cat /etc/group | grep -i policy
policykit:x:1003:

cat /etc/passwd | grep -i policy
policykit:x:102:1003:PolicyKit:/:/sbin/nologin
gdm:x:120:1002:PolicyKit:/var/lib/gdm:/sbin/nologin

Do you really think we have to change their something in /etc/PolicyKit/PolicyKit.conf ?

azleifel · 2008-11-05 21:01:10

hoschi wrote:

Do you really think we have to change their something in /etc/PolicyKit/PolicyKit.conf ?

All I know is that I was having all sorts of little problems, including not being able to do anything useful with Authorisations, until I did. In fact, I reckon that PolicyKit is supposed to be configured and when I looked I found that Ubuntu, FreeBSD et al all package PolicyKit with a basic configuration that is very similar to what I have now, i.e.

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->

<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">

<!-- See the manual page PolicyKit.conf(5) for file format -->

<config version="0.1">
    <match user="root">
        <return result="yes"/>
    </match>
    <define_admin_auth group="wheel"/>
</config>

The only real difference between them is the name of the admin_auth group, e.g. it's wheel on FreeBSD and admin on Ubuntu. (Wanders off, muttering to himself angrily about having to learn how to administer something that's intended to facilitate the deployment of 1,000s of identical desktops in an enterprise environment...)

Last edited by azleifel (2008-11-05 22:03:01)

hoschi · 2008-11-06 19:48:59

Thanks for your patient help, but I can't still not "grant" any authorization with PolicyKit.
If I open a terminal as root, start gnome-control-center and hit "authorizations" I receive only this message 100 times in the shell:

** (gnome-control-center:2663): WARNING **: error accessing /apps/main-menu/upgrade_package_command [Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)]

azleifel · 2008-11-06 21:34:57

What we all are really missing is decent user-focussed documentation for PolicyKit - all I can find is the Library Reference Manual. Anyway, it shouldn't be necessary to start polkit-gnome-authorization (= "Authorisations") as root because it will ask for admin authorisation, e.g. the root password, as necessary. So did you configure PolicyKit yet? If so, how? I use sudo here with a disabled root account à la Ubuntu and I can start polkit-gnome-authorization from the console either as a user or as sudo root without problems other than "harmless"

(polkit-gnome-authorization:8233): Gtk-CRITICAL **: gtk_tree_view_set_cursor_on_cell: assertion `tree_view->priv->tree != NULL' failed

errors when I click on an action in the tree.

Last edited by azleifel (2008-11-06 21:35:27)

hoschi · 2008-11-06 22:26:08

I just added the this lines:

<config version="0.1">
    <match user="root">
        <return result="yes"/>
    </match>
    <define_admin_auth group="wheel"/>
</config>

I receive this:

bash-3.2# polkit-gnome-authorization 

** (polkit-gnome-authorization:3406): WARNING **: Couldn't connect to session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** (polkit-gnome-authorization:3406): DEBUG: Already running
bash-3.2#

hoschi · 2008-11-06 22:46:16

Okay, okay...
If I start a login-shell as root (su -) I can open polkit-gnome-authorization, but can't use the greyed out "grant" button.
Maybe I should add this

<config version="0.1">
    <match user="root">
        <return result="yes"/>
    </match>
    <define_admin_auth group="wheel"/>
</config>

again, I removed it two minutes before *d'oh*

Tomorrow is a new day, will try it soon.

azleifel · 2008-11-07 19:46:11

It won't work unless you either restart dbus or reboot (to be honest, just restarting dbus screws things up here - maybe hal needs to be restarted too, so probably best to reboot) after editing PolicyKit.conf.

amranu · 2008-11-08 02:25:44

Anyone else unable to change their clock from 24 hour time?

hoschi · 2008-11-09 12:47:28

YES! YES! YES! It runs again in the Gnome and on the terminals!

Add this lines to your /etc/PolicyKit/PolicyKit.conf

<config version="0.1">
    <match user="root">
        <return result="yes"/>
    </match>
    <define_admin_auth group="wheel"/>
</config>

Restart the howl system or dbus&hal (last one not tested, but maybe gnome respects here the Unix-Way)!
Open a login shell as root (su -) and open gnome-polkit-authorization

Here you can open your access as user to: Suspend, Hibernate, CPU-Scaling, Clock...
Thanks for the help! If I have the time I will post it in the Wiki.

PS: HELLO GNOME USE THE FUCKING UNIX/POSIX-GROUPS!

azleifel · 2008-11-09 13:10:44

I knew that it would work

Buffalo Soldier · 2009-02-18 16:06:05

Thanks azleifel, thanks hoschi.

I followed your instruction and edited /etc/PolicyKit/PolicyKit.conf and now I can access my gnome system admin tools

orph · 2009-03-03 02:57:35

Thanks too!

It worked well for me.

proxima_centauri · 2009-04-22 23:24:14

Hmm I recently reinstalled Arch using a new partition scheme, can't seem to grant users privileges through Authorizations in the menu. I can click on grant, and then select my user, but when I click on Grant to accept the user I selected, it clicks in and does nothing. I added the lines mentioned in this thread to /etc/PolicyKit/PolicyKit.conf and rebooted, with no avail.

<config version="0.1">
    <match user="root">
        <return result="yes"/>
    </match>
    <define_admin_auth group="wheel"/>
</config>

Any ideas?

Arch Linux

#1 2008-10-23 08:30:38

Problems after upgrading to Gnome 2.24

#2 2008-10-23 08:34:26

Re: Problems after upgrading to Gnome 2.24

#3 2008-10-23 14:45:53

Re: Problems after upgrading to Gnome 2.24

#4 2008-10-23 16:41:08

Re: Problems after upgrading to Gnome 2.24

#5 2008-11-03 21:01:34

Re: Problems after upgrading to Gnome 2.24

#6 2008-11-03 22:52:59

Re: Problems after upgrading to Gnome 2.24

#7 2008-11-04 20:12:35

Re: Problems after upgrading to Gnome 2.24

#8 2008-11-04 21:39:48

Re: Problems after upgrading to Gnome 2.24

#9 2008-11-04 22:14:43

Re: Problems after upgrading to Gnome 2.24

#10 2008-11-05 21:01:10

Re: Problems after upgrading to Gnome 2.24

#11 2008-11-06 19:48:59

Re: Problems after upgrading to Gnome 2.24

#12 2008-11-06 21:34:57

Re: Problems after upgrading to Gnome 2.24

#13 2008-11-06 22:26:08

Re: Problems after upgrading to Gnome 2.24

#14 2008-11-06 22:46:16

Re: Problems after upgrading to Gnome 2.24

#15 2008-11-07 19:46:11

Re: Problems after upgrading to Gnome 2.24

#16 2008-11-08 02:25:44

Re: Problems after upgrading to Gnome 2.24

#17 2008-11-09 12:47:28

Re: Problems after upgrading to Gnome 2.24

#18 2008-11-09 13:10:44

Re: Problems after upgrading to Gnome 2.24

#19 2009-02-18 16:06:05

Re: Problems after upgrading to Gnome 2.24

#20 2009-03-03 02:57:35

Re: Problems after upgrading to Gnome 2.24

#21 2009-04-22 23:24:14

Re: Problems after upgrading to Gnome 2.24

Board footer