You are not logged in.

Announcement

Due to heavy spamming of forums registration is going in stages. If you wish to register as a new user with ArchBang Forums, first register and then send an e-mail to: archbangforums at gmail dot com. It should contain the problem you want to discuss or some other AB related content. You will be promoted from registering member with no posting rights to new member with posting rights after that. If your mail is ignored you haven't fulfilled the requirements.

#1 2012-05-10 09:30:49

sano
Member
Registered: 2012-02-13
Posts: 19

Slim update and consolekit issues , permission errors for network too

After the slim was updated yesterday, it now has consolekit built in. Because AB'S .xinitrc includes 'ck-launch-session', you might end up with two running ck-sessions, leading to permission problems when mounting external devices and when trying to restart or shutdown from oblogout.

You have to change the line in ~/.xinitrc from

exec ck-launch-session dbus-launch openbox-session

to this:

exec dbus-launch openbox-session

I guess most people here figured it out already, but this might save you some time if you haven't yet.

Source: https://bbs.archlinux.org/viewtopic.php?id=141220

Note: that this can also lead to  a permission error regarding networking:

not authorized to control networking

see: http://bbs.archbang.org/viewtopic.php?pid=14351#p14351
and http://bbs.archbang.org/viewtopic.php?pid=14358#p14358

Offline

#2 2012-05-10 11:00:31

scjet
ArchBanger
From: Windsor, Canada
Registered: 2010-12-01
Posts: 749

Re: Slim update and consolekit issues , permission errors for network too

thanks for that informative-potential lookout.


The "BSD" things in life are "Free", and "Open", and so is ArchBang!
Go Leafs Go !!!

Offline

#3 2012-05-10 15:34:14

pablokal
Administrator
From: Nijmegen, Holland
Registered: 2010-10-12
Posts: 2,624
Website

Re: Slim update and consolekit issues , permission errors for network too

Note, Mr Green!!


Getting your questions answered here at ArchBang Forums
Please! Always give hardware info, if there is a chance that 's relevant: #lspci -vnn
Quote: What I have learnt from Linux is to minimize dependencies and functionalities for greater independence.
On Arch(bang) and Openbox: http://stillstup.blogspot.com/

Offline

#4 2012-05-10 16:36:33

Conker1r
AB Artist
From: GlobeVille
Registered: 2010-10-07
Posts: 144

Re: Slim update and consolekit issues , permission errors for network too

good thing I saw this Now I don't have to post another thread. Thanks.


It's only chaos to those not interested.

"Power aint nothing if you don't use it."
"I call it a sin Not to rule the world, if you've been blessed, with the strength!"

Offline

#5 2012-05-10 22:52:33

Mr Green
Iso Developer
Registered: 2010-11-07
Posts: 3,749

Re: Slim update and consolekit issues , permission errors for network too

Noted! smile

Easy way to check ck problem is to run

ck-list-sessions

You may get the following

[mrgreen@macmillan ~]$ ck-list-sessions 
Session1:
	unix-user = '1000'
	realname = '(null)'
	seat = 'Seat1'
	session-type = 'x11'
	active = TRUE
	x11-display = ':0.0'
	x11-display-device = '/dev/tty7'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2012-05-11T04:45:25.485318Z'
	login-session-id = '1'
Session2:
	unix-user = '1000'
	realname = '(null)'
	seat = 'Seat1'
	session-type = ''
	active = FALSE
	x11-display = ':0.0'
	x11-display-device = '/dev/tty7'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2012-05-11T04:45:25.711012Z'
	login-session-id = '1'
[mrgreen@macmillan ~]$ 

Then you need to edit .xinitrc and remove ck-launch-session to look like

exec dbus-launch openbox-session

Offline

Board footer

Powered by FluxBB