Re: [blfs-dev] KDM crashing, KDE runs!

2012-12-04 Thread Ragnar Thomsen
On Monday 03 December 2012 15:21:20 Baho Utot wrote:
 I have found out that KDM does indeed need its own usr/group.
 I now have kdm working as I can now login and boot the machine to run
 level 5 from inittab and it works.

I don't have a separate user/group for KDM, and it's working fine.

 I have a Console kit error dialog on login saying Warning: Cannot open
 ConsoleKit session: Unable to execute program
 /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

 This I have traced to dbus not started, but I have dbus starting run the
 init scripts at boot through the blfs-bootscripts.
 
 Also in the kdm log it has klauncher kdemain: No DBUS session-bus found.
 Check if you have started the DBUS server.
 
 I know that dbus is indeed started but how does one check to see if a
 dbus session exists?
 
 This is what I think this problem resolves to.
 If anyone has a link to all this dbus stuff I would like to get that so
 I can read up on dbus.

KDM starts a consolekit session automatically, if consolekit was installed 
when building kde-workspace. I think your error is related to d-bus. The d-bus 
sytem-wide bus should be started in your bootscripts and will be running as 
user messagebus. The d-bus session bus can be start in various ways and will 
be running as the logged in user. I use a method derived from this link for 
starting the session bus:
http://www.howtoforge.com/dbus_kde_integration
which I found works well and results in a single d-bus session process.

Basically, kdm launches this script when starting a session:
$KDE_PREFIX/share/config/kdm/Xstartup

And this script when stopping a session:
$KDE_PREFIX/share/config/kdm/Xreset

So these can be used to start/stop d-bus.

 Also I heard but have not been able to confirm that ConsoleKit is not
 required anymore as PolicyKit has all the ConsoleKit stuff.  Can anyone
 confirm this?

As Armin stated, if you do not use systemd, you need consolekit for kde.

-Ragnar-
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] KDM crashing, KDE runs!

2012-12-04 Thread Baho Utot
On 12/04/2012 09:53 AM, Ragnar Thomsen wrote:
 On Monday 03 December 2012 15:21:20 Baho Utot wrote:
 I have found out that KDM does indeed need its own usr/group.
 I now have kdm working as I can now login and boot the machine to run
 level 5 from inittab and it works.
 I don't have a separate user/group for KDM, and it's working fine.

This is what I have and it will work, if I remove this it will fail

 groupadd -g 135 kdm /dev/null
 useradd -u 135 -g kdm -d /var/lib/kdm -s /bin/false -r -M kdm 
/dev/null
 chown -R 135:135 var/lib/kdm /dev/null

 I have a Console kit error dialog on login saying Warning: Cannot open
 ConsoleKit session: Unable to execute program
 /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

 This I have traced to dbus not started, but I have dbus starting run the
 init scripts at boot through the blfs-bootscripts.

 Also in the kdm log it has klauncher kdemain: No DBUS session-bus found.
 Check if you have started the DBUS server.

 I know that dbus is indeed started but how does one check to see if a
 dbus session exists?

 This is what I think this problem resolves to.
 If anyone has a link to all this dbus stuff I would like to get that so
 I can read up on dbus.
 KDM starts a consolekit session automatically, if consolekit was installed
 when building kde-workspace. I think your error is related to d-bus. The d-bus
 sytem-wide bus should be started in your bootscripts and will be running as
 user messagebus. The d-bus session bus can be start in various ways and will
 be running as the logged in user. I use a method derived from this link for
 starting the session bus:
 http://www.howtoforge.com/dbus_kde_integration
 which I found works well and results in a single d-bus session process.

 Basically, kdm launches this script when starting a session:
 $KDE_PREFIX/share/config/kdm/Xstartup

 And this script when stopping a session:
 $KDE_PREFIX/share/config/kdm/Xreset

 So these can be used to start/stop d-bus.

Ok I will look at this to see what I have there.

Thanks
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] KDM crashing, KDE runs!

2012-12-03 Thread Baho Utot
On 12/03/2012 02:49 AM, Armin K. wrote:

[putolin]

 There is seperate applet for that. I wouldn't recommend downgrading
 networkmanager.

Are you talking about wicd?

 KDM crashes and this is my concern.  Currently I am starting KDE from a
 user login followed the book on setting up .xinitrc
 and then doing a startx, which works well.  Trying to start KDM from
 root login on tty1 it tries to start as the screen flashes like xorg is
 starting but then something goes south.  I don't have strace built just
 yet so I could not attempt that.

 Before I get down and dirty looking into KDM crashing does any one have
 any pointers or easy things to check?

 Thanks

 Do you have PAM installed?

No I don't do pam


-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] KDM crashing, KDE runs!

2012-12-03 Thread Armin K.
On 12/03/2012 02:31 PM, Baho Utot wrote:
 On 12/03/2012 02:49 AM, Armin K. wrote:

 [putolin]

 There is seperate applet for that. I wouldn't recommend downgrading
 networkmanager.

 Are you talking about wicd?


No, it is just another applet, but works with network manager 0.9.x

ftp://ftp.kde.org/pub/kde/unstable/networkmanagement/0.9.0.5/src/

I think that instructions on Further KDE Packages should do the trick.

 KDM crashes and this is my concern.  Currently I am starting KDE from a
 user login followed the book on setting up .xinitrc
 and then doing a startx, which works well.  Trying to start KDM from
 root login on tty1 it tries to start as the screen flashes like xorg is
 starting but then something goes south.  I don't have strace built just
 yet so I could not attempt that.

 Before I get down and dirty looking into KDM crashing does any one have
 any pointers or easy things to check?

 Thanks

 Do you have PAM installed?

 No I don't do pam



I have PAM installed and it needs 2 config files. I guess it isn't case 
for you.

I also have /var/log/kdm.log, but it does not contain anything useful.

I looked at Archlinux pkgbuild and install files and KDM seems to 
require seperate user, just like GDM.

This did the trick for me

groupadd -g 37 kdm
useradd  -u 37 -g kdm -d /var/lib/kdm -s /bin/false kdm

install -d -o kdm -g kdm /var/lib/kdm



I have this in my post install script (not any package manager, just 
plain cp -r and such).

If this doesn't solve problem for you, then you can hope that Ragnar 
will show up and try to help you because he wrote KDE instructions and 
maintains them in BLFS. I installed mine differently, ie everything into 
/usr, no env vars, no /etc/kde sysconf dir and such ...
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] KDM crashing, KDE runs!

2012-12-03 Thread Baho Utot
On 12/03/2012 10:42 AM, Armin K. wrote:
 On 12/03/2012 02:31 PM, Baho Utot wrote:


[putolin]

 Are you talking about wicd?

 No, it is just another applet, but works with network manager 0.9.x

 ftp://ftp.kde.org/pub/kde/unstable/networkmanagement/0.9.0.5/src/

 I think that instructions on Further KDE Packages should do the trick.

Ok I will have a look there


 I also have /var/log/kdm.log, but it does not contain anything useful. 
 I looked at Archlinux pkgbuild and install files and KDM seems to 
 require seperate user, just like GDM. This did the trick for me 
 groupadd -g 37 kdm useradd -u 37 -g kdm -d /var/lib/kdm -s /bin/false 
 kdm install -d -o kdm -g kdm /var/lib/kdm I have this in my post 
 install script (not any package manager, just plain cp -r and such). 
 If this doesn't solve problem for you, then you can hope that Ragnar 
 will show up and try to help you because he wrote KDE instructions and 
 maintains them in BLFS. I installed mine differently, ie everything 
 into /usr, no env vars, no /etc/kde sysconf dir and such ... 

I did also have kde installed to /usr.  I have used prefix=/usr for all 
packages.

I have found out that KDM does indeed need its own usr/group.
I now have kdm working as I can now login and boot the machine to run 
level 5 from inittab and it works.

I have a Console kit error dialog on login saying Warning: Cannot open 
ConsoleKit session: Unable to execute program 
/usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

This I have traced to dbus not started, but I have dbus starting run the 
init scripts at boot through the blfs-bootscripts.

Also in the kdm log it has klauncher kdemain: No DBUS session-bus found. 
Check if you have started the DBUS server.

I know that dbus is indeed started but how does one check to see if a 
dbus session exists?

This is what I think this problem resolves to.
If anyone has a link to all this dbus stuff I would like to get that so 
I can read up on dbus.

Also I heard but have not been able to confirm that ConsoleKit is not 
required anymore as PolicyKit has all the ConsoleKit stuff.  Can anyone 
confirm this?


-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] KDM crashing, KDE runs!

2012-12-03 Thread Armin K.
On 12/03/2012 09:21 PM, Baho Utot wrote:

 I did also have kde installed to /usr.  I have used prefix=/usr for all
 packages.

 I have found out that KDM does indeed need its own usr/group.
 I now have kdm working as I can now login and boot the machine to run
 level 5 from inittab and it works.

 I have a Console kit error dialog on login saying Warning: Cannot open
 ConsoleKit session: Unable to execute program
 /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success


Have you installed D-Bus via DESTDIR method?

If so, launch-helper needs to be root:messagebus owned and needs to have 
permissions 4754

chown root:messagebus /usr/lib/dbus-1.0/dbus-daemon-launch-helper
chmod 4754 /usr/lib/dbus-1.0/dbus-daemon-launch-helper

 This I have traced to dbus not started, but I have dbus starting run the
 init scripts at boot through the blfs-bootscripts.

 Also in the kdm log it has klauncher kdemain: No DBUS session-bus found.
 Check if you have started the DBUS server.

 I know that dbus is indeed started but how does one check to see if a
 dbus session exists?


This might be the problem with helper permissions as described above.

 This is what I think this problem resolves to.
 If anyone has a link to all this dbus stuff I would like to get that so
 I can read up on dbus.

 Also I heard but have not been able to confirm that ConsoleKit is not
 required anymore as PolicyKit has all the ConsoleKit stuff.  Can anyone
 confirm this?


That's true only if you are using systemd.

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] KDM crashing, KDE runs!

2012-12-03 Thread Baho Utot
On 12/03/2012 03:36 PM, Armin K. wrote:
 On 12/03/2012 09:21 PM, Baho Utot wrote:
 I did also have kde installed to /usr.  I have used prefix=/usr for all
 packages.

 I have found out that KDM does indeed need its own usr/group.
 I now have kdm working as I can now login and boot the machine to run
 level 5 from inittab and it works.

 I have a Console kit error dialog on login saying Warning: Cannot open
 ConsoleKit session: Unable to execute program
 /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success

 Have you installed D-Bus via DESTDIR method?

Yes, I will have a looked at the permissions and changed them as below 
and it now works.
The usb drive also now works.
I still have some permissions issues to fix, they are in the daemon.log, 
but what I have now works very well so I will put those on the back 
burner as I need to get the additional packages built for kde.


 If so, launch-helper needs to be root:messagebus owned and needs to have
 permissions 4754

 chown root:messagebus /usr/lib/dbus-1.0/dbus-daemon-launch-helper
 chmod 4754 /usr/lib/dbus-1.0/dbus-daemon-launch-helper

 This I have traced to dbus not started, but I have dbus starting run the
 init scripts at boot through the blfs-bootscripts.

 Also in the kdm log it has klauncher kdemain: No DBUS session-bus found.
 Check if you have started the DBUS server.

 I know that dbus is indeed started but how does one check to see if a
 dbus session exists?

 This might be the problem with helper permissions as described above.

 This is what I think this problem resolves to.
 If anyone has a link to all this dbus stuff I would like to get that so
 I can read up on dbus.

 Also I heard but have not been able to confirm that ConsoleKit is not
 required anymore as PolicyKit has all the ConsoleKit stuff.  Can anyone
 confirm this?

 That's true only if you are using systemd.

Ok

Thank you very much for helping me to resolve some of my issues


-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page


Re: [blfs-dev] KDM crashing, KDE runs!

2012-12-02 Thread Armin K.
On 12/03/2012 03:14 AM, Baho Utot wrote:
 I have just completed KDE 4.9.1 and it generally works well.
 I am using Beyond Linux® From Scratch - Version 2012-09-25, which I will
 update to the latest after I complete this desktop build.   The
 configuration went well and  have the sound working.  I have not built
 the KDE Additional Packages

 There is the following few problems to work out...

 DVD drive doesn't show up in /dev, this may be due to the kernel as I am
 using the default kernel as I used make defconfig to configure it when I
 build LFS 7.2.  I don't know if the kernel configuration is correct, I
 will make a custom kernel for this machine after I get the rest of KDE
 built.  So I will visit this later.

 USB drives also don't show up in the device notifier although usb drives
 do show up in /dev and I can mount them using root.  This I would like
 to get working but it is not real high on the list of things to get working.

 The NetworkManager in this version of the book causes the following
 problem when configuring/building Kde-workspace 4.9.1...

 -- Sorry, networkmanager-0.7 will not be built since your NetworkManager
 version (0.9.6.0) is not currently supported
 -- Will build networkmanager_fake-0.9

 Anyone know what version of NetworkManager works?
 I tried to dig through the cmake files but I have not found where the
 version of NetworkManager is tested for.  I did a grep on the source but
 it returned too much hay in which to find the needle.  So I did a Google
 and it returned

set(HAVE_NETWORKMANAGER FALSE)
 if(NETWORKMANAGER_FOUND)
 if(${NETWORKMANAGER_VERSION} VERSION_GREATER 0.6. AND
${NETWORKMANAGER_VERSION} VERSION_LESS 0.8.1001)
   message(STATUS Will build networkmanager-0.7)
   set(HAVE_NETWORKMANAGER TRUE)
   add_subdirectory(networkmanager-0.7)
 else()
   message(STATUS Sorry, networkmanager-0.7 will not be built since
 your NetworkManager version (${NETWORKMANAGER_VERSION}) is not currently
 supported)
   if (${NETWORKMANAGER_VERSION} VERSION_GREATER 0.8.999)
 message(STATUS Will build networkmanager_fake-0.9)
 set(HAVE_NETWORKMANAGER TRUE)
 add_subdirectory(networkmanager_fake-0.9)
   endif ()
 endif()
 endif (NETWORKMANAGER_FOUND)
 macro_log_feature(HAVE_NETWORKMANAGER NetworkManager A daemon for
 user controlled networking
 http://www.gnome.org/projects/NetworkManager; FALSE 0.7.0 Needed for
 building Network Management support in Solid. Max version supported is
 0.8.10
 So it looks like version  6.9 and  8.10 is needed not what is in the book.


There is seperate applet for that. I wouldn't recommend downgrading 
networkmanager.

 KDM crashes and this is my concern.  Currently I am starting KDE from a
 user login followed the book on setting up .xinitrc
 and then doing a startx, which works well.  Trying to start KDM from
 root login on tty1 it tries to start as the screen flashes like xorg is
 starting but then something goes south.  I don't have strace built just
 yet so I could not attempt that.

 Before I get down and dirty looking into KDM crashing does any one have
 any pointers or easy things to check?

 Thanks


Do you have PAM installed?
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page