[SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

luksow · 2011-02-08 14:53:52

Hi,

I'm encountering strange problem. When I log in (after booting up) as typical user, I have no shutdown button in System menu (Gnome) and I can't mount usb sticks from Places (I got "Not authorized"). Then, when I kill X and log as root, I have shutdown button and I can mount devices (which is probably not strange), but then, when I kill X and again log as typical user, this time I have shutdown button and can mount devices (and this is strange ). This issue started after huge full system update tonight, before then, it was all ok.

Any suggestions how to fix it?

Last edited by luksow (2011-02-09 00:14:52)

ewaller · 2011-02-08 15:45:57

How are you logging in? startx or a login manager?
If a login manager, which one?
What environment are you using (KDE, Gnome, Xfce4, *box, awesome)?
if startx, what is the command you use to invoke X ?

Edit: Sorry, I missed the Gnome bit. Does that imply you are using gdm? Are you sure dbus is running? Is hal?

Last edited by ewaller (2011-02-08 15:47:38)

adee · 2011-02-08 16:10:37

I'm not a big Gnome expert, but AFAIK gnome don't use hal for a long time.
What is the output of ck-list-sessions? I guess your problem is polkit authorization

luksow · 2011-02-08 16:34:12

How I start Gnome:
x:5:once:/bin/su luke -l -c "/bin/bash --login -c /usr/bin/startx >/dev/null 2>&1"

It all seems to work:
ls /var/run/daemons/ gives:
acpid bluetooth dbus laptop-mode networkmanager
alsa crond hal netfs syslog-ng

Output of ck-list-sessions:
Session1:
unix-user = '1000'
realname = 'xxx yyy'
seat = 'Seat2'
session-type = ''
active = FALSE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = ''
remote-host-name = ''
is-local = FALSE
on-since = '2011-02-08T16:29:47.806611Z'
login-session-id = '4294967295'

Note that it all worked fine before updating. And it works fine after relogging. That means:
If I turn on computer, it logs me into Gnome and there's no shutdown button nor mounting possible. Then I do:
kill `pidof X`
Types login and password of normal user.
startx
There's shutdown button and mounting is possible and everything works fne.

Last edited by luksow (2011-02-08 16:40:31)

ewaller · 2011-02-08 18:27:29

Wow.

I've never seen a run level defined like that before.

So, I see you just want the system to boot straight to gnome with a user name of luke -- do not pass go, do not ask for a password, even though one exists.
Interesting.

I have this nagging feeling you need to start the gnome session using ck-launch-session. Do you have a ~/.xinitrc ? Could it be starting Gnome using ck-launch-session. It would be invoked when you invoke startx from an interactive shell. I'm not sure it will be invoked with a bash -l -c -- Of course, I could be wrong.

Not that I am suggesting you should, but what is the reason for not setting up a login manager configured for auto login?

luksow · 2011-02-08 19:36:00

My .xinitrc:
exec ck-launch-session gnome-session

I have no idea why it's broken . Before updating everything was fine...

hokasch · 2011-02-08 20:16:42

ewaller wrote:

I've never seen a run level defined like that before.

It comes from the Wiki and worked until the recent consolekit update. I don't want to mess with gdm when there is no real need for a login manager (am the only user on my laptop).

ck-session wrote:

is-local = FALSE

is the problem; the wiki article linked above states the /etc/inittab method as broken for consolekit. We will have to try bash_profile & mingetty then I guess...

luksow, could you please rename the title to something descriptive (no user shutdown/hibernate/suspend button whatever) by editing first post? Surely more people with the same problem will browse/search the forum for a solution.

Last edited by hokasch (2011-02-08 20:19:32)

Stebalien · 2011-02-08 21:41:04

Adding

session         optional        pam_ck_connector.so

to your '/etc/pam.d/su' may fix it.
Note: This will allow all users that can run 'su' to shutdown, reboot, mount drives, etc...

luksow · 2011-02-08 22:54:52

hokasch wrote:

ewaller wrote:
I've never seen a run level defined like that before.
It comes from the Wiki and worked until the recent consolekit update. I don't want to mess with gdm when there is no real need for a login manager (am the only user on my laptop).
ck-session wrote:
is-local = FALSE
is the problem; the wiki article linked above states the /etc/inittab method as broken for consolekit. We will have to try bash_profile & mingetty then I guess...
luksow, could you please rename the title to something descriptive (no user shutdown/hibernate/suspend button whatever) by editing first post? Surely more people with the same problem will browse/search the forum for a solution.

Thanks for info! I will try this out.

Title changed.

// EDIT: Ok, https://wiki.archlinux.org/index.php/Au … al_console + https://wiki.archlinux.org/index.php/Start_X_at_Boot solved the problem. Thanks hokasch!

Last edited by luksow (2011-02-09 00:14:05)

PhotonX · 2011-02-11 09:13:56

luksow, could you please state the exact solution? I'm having the same problem here...

sagar_k · 2011-02-12 12:14:47

I had same problem. the problem was causing due to consolekit-0.4.3-2-x86_64.pkg.tar.xz package. i downgraded it to the consolekit-0.4.1-4-x86_64.pkg.tar.xz package and every thing seems to working fine again, no shutdown/reboot dialog box issues & no mounting dev issues.

Last edited by sagar_k (2011-02-12 12:15:43)

hokasch · 2011-02-12 13:47:08

1) downgrading is not a solution
2) if you start x by initab/runlevel, the solution is in this thread/the wiki page already

PhotonX · 2011-02-12 21:56:51

hokasch, could you be a bit more precise on the exact solution?

hokasch · 2011-02-12 22:10:08

Sure. I now use mingetty autologin and start x with bash_profile. Please kindly read the post directly over your first one in this thread before asking again...

Arch Linux Forum Etiquette wrote:

Life is a Two-way Street
A simple, yet profound and undeniable truth. Ensure your thread includes details and information that others will find useful. Share your findings with the community. Share your failures as well. Posting the equivalent of 'Nevermind, I fixed it.' in your thread or deleting your own posts for similar reasons is not only selfish and useless to the community, but a complete waste of resources and everyone's time. Also, demanding help or showing an obvious impatience toward getting it is unwanted here. Arch is provided by a community of volunteers. Arch users are strongly encouraged to do research, make an effort, report back in the thread, help others, get involved, and contribute to the community.
Please don't be a 'help vampire'.

PhotonX · 2011-02-13 14:44:45

Sorry, I've overread the keywords mingetty and bash_profile and didn't really know what to do with the wiki pages... However now it seems to work fine, thanks!

evilgnome · 2011-02-18 01:54:29

I know this is marked as solved, but I've been going crazy over this and still can't get it right, so here is my plea for guidance. I was happy with the inittab method of starting x till the consolekit problems started (thunar device mounting, shutdown permissions). So I read the updated wiki pages and related threads and made the adjustment to mingetty. X starts at boot as it should, but the original problems remain.

Thanks for any help.

Files and outputs, comment-stripped for brevity:

/etc/inittab:

id:3:initdefault:

rc::sysinit:/etc/rc.sysinit
rs:S1:once:/etc/rc.single
rm:2345:once:/etc/rc.multi
rh:06:once:/etc/rc.shutdown
su:S:once:/sbin/sulogin -p# -8 options fixes umlauts problem on login

c1:2345:respawn:/sbin/mingetty --autologin andykluger tty1 linux
c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux

ca::ctrlaltdel:/sbin/shutdown -t3 -r now

.zshrc:

<aliases and stuff>
if [[ -z $DISPLAY && $(tty) = /dev/tty1 ]]; then
  exec startx
fi

.xinitrc:

#!/bin/sh
export BROWSER="firefox-beta-bin %s &"
export DESKTOP_SESSION="ck-launch-session"
export EDITOR='nano'
export GDK_USE_XFT=1
export GREP_COLOR="1;33"
export http_proxy=http://127.0.0.1:8118/
export PYTHONSTARTUP=~/.pythonrc.py

if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
    eval `dbus-launch --sh-syntax --exit-with-session`
fi

exec ck-launch-session /home/andykluger/Code/session.sh

session.sh:

#!/bin/bash
compiz --indirect-rendering ccp &
start-pulseaudio-x11 &
nitrogen --restore &
conky &
conky -c ~/.conkyrc.dmesg &
avant-window-navigator &
guake &
xfce4-volumed &
~/Code/android-notifier.sh &
pytyle &
kupfer --no-splash

ck-list-sessions:

Session1:
        unix-user = '1000'
        realname = '(null)'
        seat = 'Seat2'
        session-type = ''
        active = FALSE
        x11-display = ':0'
        x11-display-device = '/dev/tty3'
        display-device = '/dev/tty1'
        remote-host-name = ''
        is-local = FALSE
        on-since = '2011-02-18T01:35:59.411477Z'
        login-session-id = '1'

Arch Linux

#1 2011-02-08 14:53:52

[SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#2 2011-02-08 15:45:57

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#3 2011-02-08 16:10:37

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#4 2011-02-08 16:34:12

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#5 2011-02-08 18:27:29

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#6 2011-02-08 19:36:00

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#7 2011-02-08 20:16:42

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#8 2011-02-08 21:41:04

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#9 2011-02-08 22:54:52

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#10 2011-02-11 09:13:56

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#11 2011-02-12 12:14:47

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#12 2011-02-12 13:47:08

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#13 2011-02-12 21:56:51

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#14 2011-02-12 22:10:08

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#15 2011-02-13 14:44:45

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

#16 2011-02-18 01:54:29

Re: [SOLVED] dbus/hal (?) problem - no shutdown button + no automounting

Board footer