Announcement

Collapse
No announcement yet.

In Chroot: DBUS won't start

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    In Chroot: DBUS won't start

    I'm running Hardy as my main install, since KDE4 is still quite buggy on my unconventional setup (TwinView+64bit), but I'd like to migrate to Intrepid as much as possible. Plus, many things I'd like to use need to be run as 32-bit (for example XBMC). Thus, I've installed a 32-bit Intrepid chroot. So far so good. The problem is that no KDE4 programs, or XBMC for that matter, will run in the chroot. Example:

    Code:
    (8.10-32)keithzg@foundation:~$ konqueror
    konqueror(15656) KToolInvocation::klauncher: klauncher not running... launching kdeinit
    kdeinit4: preparing to launch /usr/lib/kde4/libexec/klauncher
    klauncher(15668) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    But however I try and launch dbus, it ends up looking like this:

    Code:
    (8.10-32)keithzg@foundation:~$ eval `dbus-launch --auto-syntax`
    Could not tell if SELinux is enabled: No such file or directory
    SELinux pre-initialization failed
    EOF in dbus-launch reading address from bus daemon
    If I just try /etc/init.d/dbus start nothing happens. Now, obviously this has something to do with the chroot. I have dbus set up like this in fstab:

    Code:
    /var/run/dbus/ /media/Zeitraum/etc/heavy/chroot/intrepid32/var/run/dbus/ none rbind 0 0
    I assume there's either more I need to do or something I've done wrong. Does anyone have any ideas? I'm itching to run KDE4, or at least the programs, on my main computer....I've got it installed on all my other systems but it isn't workable on my main one yet, so a chroot seems to be my only chance, I'm hoping it's possible.

    #2
    Re: In Chroot: DBUS won't start

    ...no ideas?

    Comment

    Working...
    X