Porteus-v1.1rc1-i486 ready for testing

New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
User avatar
brokenman
Site Admin
Site Admin
Posts: 5503
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v1.1rc1-i486 ready for testing

Post#31 by brokenman » 15 Nov 2011, 17:51

Blaze please remove the file in rootcopy/etc/rc.d/rc.local. I beleive the current ISO has been updated to remove this file left by me while testing switcheroo function in 32bit.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v1.1rc1-i486 ready for testing

Post#32 by Ahau » 18 Nov 2011, 02:22

There's something going on with console-kit-daemon, and I'm not sure yet exactly what the problem is. I don't get this error in V1.0 or in 64-bit. This is from /var/log/syslog:

Nov 17 18:16:06 (none) console-kit-daemon[2266]: WARNING: Failed to acquire org.freedesktop.ConsoleKit
Nov 17 18:16:06 (none) console-kit-daemon[2266]: WARNING: Could not acquire name; bailing out

This is a self-serving bug report; I don't recognize any issues that this is causing me in the standard distribution, but it may be contributing to some of my issues with xfce...and I thought it might be causing issues elsewhere, of which I'm not aware.

Thanks!
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
brokenman
Site Admin
Site Admin
Posts: 5503
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v1.1rc1-i486 ready for testing

Post#33 by brokenman » 18 Nov 2011, 13:51

I get this error once in syslog, but after boot i see the daemon is runing ok.

ps x|grep console
2526 ? Ssl 0:00 /usr/sbin/console-kit-daemon

To gather some more info:

Code: Select all

kill 2526
console-kit-daemon --debug
Then check the syslog again. It seems to load OK after a time ... but with the final message:

Code: Select all

Nov 18 11:47:00 (none) console-kit-daemon[4145]: DEBUG: NameOwnerChanged: service_name='org.freedesktop.ConsoleKit', old_service_name='' new_service_name=':1.16'
Perhaps the error is related to polkit or dbus. Will keep looking around.

Also this might be handy for your xfce quest:
http://forums.gentoo.org/viewtopic-p-6555114.html

EDIT:
It seems polikt requires some files from policykit.
After installing the following package the problem goes away:
http://repository.slacky.eu/slackware-1 ... cykit/0.9/
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v1.1rc1-i486 ready for testing

Post#34 by Ahau » 18 Nov 2011, 16:45

Hm...I added that package (converted the .tgz into a module and stuck it in /porteus/base), and it gave me more errors than I had before, lol!

Code: Select all

Nov 18 08:34:05 (none) console-kit-daemon[2300]: WARNING: Couldn't create log file /var/log/ConsoleKit/history (File exists) 
Nov 18 08:34:05 (none) console-kit-daemon[2300]: WARNING: polkit_authority_get: Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 
Nov 18 08:34:05 (none) console-kit-daemon[2299]: WARNING: polkit_authority_get: Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 
Nov 18 08:34:05 (none) console-kit-daemon[2300]: WARNING: Failed to acquire org.freedesktop.ConsoleKit 
Nov 18 08:34:05 (none) console-kit-daemon[2300]: WARNING: Could not acquire name; bailing out 
Did you perhaps have to add a user/group for polkit? I got an error during bootup that there was an unknown user, 'polkit' -- I resolved that problem for avahi by adding a user/group for avahi, but am not sure what to add for polkit. I'll keep looking around, too :)

Strange that this package exists for slackware 12.2 and 13.0, but I can't seem to track down a build for 13.37...
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
brokenman
Site Admin
Site Admin
Posts: 5503
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v1.1rc1-i486 ready for testing

Post#35 by brokenman » 19 Nov 2011, 00:30

OK .. when i tested i did not restart dbus (reboot) but simply restarted the consolekit daemon. I should have been more thorough.

Will retest shortly.

Posted after 10 minutes 37 seconds:
Since the daemon starts successfully at boot ... and trying to start the daemon again manually once it is already started gives the same error messages in syslog ... i would guess that console-kit-daemon is attempting to start twice during boot. Nothing to be too worried about.

Let me know if you find with certainty that it is causing problems.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
wread
Module Guard
Module Guard
Posts: 1080
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Porteus-v1.1rc1-i486 ready for testing

Post#36 by wread » 19 Nov 2011, 02:33

@brokenman
As I was testing kde4.7.1 with v1.0, I found out ConsoleKit was somehow buggy; the error showed up when kde4.7.1 started. I then tried to make ConsoleKit behave. To test if it was working ok, I issued the command (try it)
# ck-list-sessions

The official v1.0 version was buggy, but the rc1 version worked ok. I then found out 000-kernel was to blame, so I simply used the rc1 kernel (and corresponding vmlinuz in boot) to make my kde4.7.1 tests. With this combination I noticed that the ck-daemon was not started by rc.M; I still don't know how it gets started. By the kernel?

And now, in v1.1, I notice that the ck-daemon will be started by initrd, I guess (at least it shows at startup). Maybe we are starting it twice (once silently and once reported) and that is the apparent error? I will comment it out in rc.M and see if it starts up despite of that (and probably without error!). Let's see....

Cheers

EDIT: as expected! I commented out the line starting console kit in rc.M, and ConsoleKit will be started despite of this. By whom is a mistery... So we can take out those two lines in rc.M.
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
Ahau
King of Docs
King of Docs
Posts: 1331
Joined: 28 Dec 2010, 15:18
Distribution: LXDE & Xfce 32/64-bit
Location: USA

Re: Porteus-v1.1rc1-i486 ready for testing

Post#37 by Ahau » 19 Nov 2011, 07:30

@wread, I'm not getting the same results. If I comment out the consolekit section in rc.M and then check ck-list-sessions, I get a dbus error. Are you perhaps starting kde with 'startx' or by another means that uses xinitrc.kde?

root@porteus:~# cat /etc/X11/xinit/xinitrc.kde |grep -n ck
28:if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
29: ck-launch-session startkde
root@porteus:~#

if not started by rc.M, the xinitrc scripts will start consolekit, and you won't see it in the messages during boot up.
Please take a look at our online documentation, here. Suggestions are welcome!

User avatar
wread
Module Guard
Module Guard
Posts: 1080
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Porteus-v1.1rc1-i486 ready for testing

Post#38 by wread » 20 Nov 2011, 14:31

@Ahau
I am starting kde Always Fresh.

Your explanation seems to be consequent with the use of ck. ConsoleKit is needed at xorg upwards. Now I know who is starting it! :wall:

It is logic that it will be started by xinitrc by default. Maybe brokenman or fanthon could give us a light what the correct behavior of ck should be....

Regards!
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

User avatar
brokenman
Site Admin
Site Admin
Posts: 5503
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: Porteus-v1.1rc1-i486 ready for testing

Post#39 by brokenman » 20 Nov 2011, 21:23

As i understand it. ck is a tool that keeps track of users, sessions and seats on a system. A seat is a hardware group (mouse,keyboard for example) and a collection of sessions. There are various uses for ck so it could be required at login manager time, used to interact with hardware abstraction layer, session daemon or system daemon.

cat /usr/share/dbus-1/system-services/org.freedesktop.ConsoleKit.service

Code: Select all

[D-BUS Service]
Name=org.freedesktop.ConsoleKit
Exec=/usr/sbin/console-kit-daemon --no-daemon
User=root
SystemdService=console-kit-daemon.service
This file is a dbus service file and when an application (like gdm) tries to access consolekit it does so through dbus.

ck is called by /etc/X11/xinit/xinitrc (symlink to xinitrc.kde) so ck can know the session. (ck-launch-session)

consolekit is also started via rc.M (/etc/rc.d/rc.consolekit start)

So i believe the warnings in the syslog can be ignored.



Console kit is no longer being maintained either ... so we are alone.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
wread
Module Guard
Module Guard
Posts: 1080
Joined: 09 Jan 2011, 18:48
Distribution: Porteus v3.2.5-kde5-64 bits
Location: Santo Domingo
Contact:

Re: Porteus-v1.1rc1-i486 ready for testing

Post#40 by wread » 21 Nov 2011, 01:44

@brokenman

If that is the case, that we are going to use ck for text-sessions, ConsoleKit must be started at rc.M, ok.
Maybe we should move ck from 002-xorg to 001-core. So, if we strip 002-xorg, we will still have that service.

As far as I know, the commonly used login manager in text mode (also in poteus) doesn't make use of ck. That is why i followed the other way: strip the start script from rc.M and let xinitrc do the job.

I don't know what the others think....

Regards :)
Porteus is proud of the FASTEST KDE ever made.....(take akonadi, nepomuk and soprano out and you will have a decent OS).
The Porteus Community never sleeps!

Locked