Dbus problem at KDE4 start

rvdboom · 01-12-2008, 02:36 PM

Hi!
I just compiled KDE4 from source (without much issues, they're really doing a great packaging work) with a self-compiled QT4 using the slackbuild provided in slackbuilds.org. I'm running Slackware-current (up to date).
As I don't really know what I'm doing, I basically added the /etc/profile.d and /etc/X11 scripts provided by Slack for KDE3.
When I start X, I see the begining of the splash screen with a jumping hard disk, and then a "Could not start D-Bus". dbus is running as daemon, though, and works apparently well with KDE3.
I found this mail on the kde forum :

http://lists-archives.org/kde-devel/...and-kde-4.html

But it didn't really help me. I notice that on my systems, dbus is running with his UID as user (81) though "messagebus" is present in /etc/group and /etc/passwd. the "messagebus" user is not added to the "messagebus" group in the /etc/group file, though, but adding it doesn't seem to change anything and I don't know if it should anyway.
Does anyone perchance has a solution or an idea?
Best regards,

rvdboom · 01-13-2008, 04:11 AM

OK, that was really stupid :
it's just that the QT4 bin dir was not in the PATH, so qdbus was not found. Just copy the /etc/profile.d/qt.sh file to a /etc/profile.d/qt4.sh and edit it to replace the /usr/lib/qt dirs by /usr/lib/qt4, and it works.
I think the QT4 slackbuild provided by slackbuilds.org should be updated to add this qt4.sh (and the equivalent qt4.csh file) within the built qt4 package.

duryodhan · 01-14-2008, 03:21 AM

I am more interested on how you got kde4 working. Other than source packages mentioned at kde4 site , what else do you need to download on a stock slack12 install ?

rvdboom · 01-14-2008, 03:57 AM

Well, I may have missed some stuff but globaly, I first compiled :

* QT4 of course (see Slackbuilds.org)

* boost : http://www.boost.org/

* Strigi : http://strigi.sourceforge.net/
Strigi normally uses Clucene (http://clucene.sourceforge.net/index.php/Main_Page) but it did not compile for me though I did not try very hard. It's probably useless without it, but right now, I'm essentially interested in getting KDE4 start the quickest way, even if some features are not available.

* Soprano: http://soprano.sourceforge.net/

* Blitz : http://sourceforge.net/projects/qimageblitz

That's all I was asked as mandatory libs. Some others did miss but they provided functionnality I did not need.
To compile the Cmake-based projects, I basically replaced in my Slackbuilds the "configure --prefix='/usr' --sysconfdir='/etc/kde'" by "cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX:PATH=/usr -DSYSCONF_INSTALL_DIR:PATH=/etc/kde".

Now I'm fighting with the ati open source driver to try to get composite to work. :-)

duryodhan · 01-14-2008, 09:06 AM

aah boost ... I never quite got those libs working on my comp .. but lets try all this again ...

rworkman · 01-14-2008, 09:38 AM

Ah yes, you discovered the qdbus issue. Glad you found the solution already

Note that KDEDIR needs to be KDEDIRS for kde4.

As for the dbus process showing "81" instead of "messagebus" - that's okay; names longer than 8 characters are shown with the uid instead.

rvdboom · 01-14-2008, 10:01 AM

Thanks for the explanation for "81", it has bugged me since saturday. :-)
Didn't know about KDEDIRS. I haven't change anything and it seems to work, but that may be because I removed KDE3 before installing my KDE4.
Now I've run into an ATI driver issue on my laptop : it absolutely wants the VGA-0 output to be the primary display and the LVDS to be the secondary... :-( Openned a bug to Xorg, I'll see how it comes out.
Looks I'm not close to enjoy a composited desktop yet. :-D

H_TeXMeX_H · 01-14-2008, 12:46 PM

Quote:

Originally Posted by duryodhan

aah boost ... I never quite got those libs working on my comp .. but lets try all this again ...

They indeed are difficult to compile properly in which case try the slackbuild:
http://slackbuilds.org/repository/12...lopment/boost/

or Alien Bob's package:
http://www.slackware.com/~alien/slackbuilds/boost/

whichever you prefer.

MarcusMoeller · 01-14-2008, 02:19 PM

I am still having problems with kdebase-workspace | dbus | plasma on slackware 12:

Quote:

kwin(25863): Couldn't start knotify from knotify4.desktop: "KDEInit kann "/opt/kde4/bin/knotify4" nicht starten."

X Error: BadMatch (invalid parameter attributes) 8
Extension: 155 (RENDER)
Minor opcode: 4 (RenderCreatePicture)
Resource id: 0x64
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
kdeinit4: preparing to launch /opt/kde4/bin/plasma
X Error: BadMatch (invalid parameter attributes) 8
Extension: 155 (RENDER)
Minor opcode: 4 (RenderCreatePicture)
Resource id: 0x64
kdeinit4: preparing to launch
ALSA lib setup.c:555

add_elem) Cannot obtain info for CTL elem (MIXER,'IEC958 Playback Default',0,0,0): Datei oder Verzeichnis
nicht gefunden
QCoreApplication:

ostEvent: Unexpected null receiver
plasma(25868): Communication problem with "plasma" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

QDBusConnection received a message of type 3 that it shouldn't have
kdeinit4: preparing to launch /opt/kde4/bin/kaccess
<stdin>:232:2: error: invalid preprocessing directive #nspluginviewer
<stdin>:233:2: error: invalid preprocessing directive #acroread
<stdin>:262:2: error: invalid preprocessing directive #GV
kdeinit4: preparing to launch /opt/kde4/bin/kmixctrl
kdeinit4: preparing to launch /opt/kde4/bin/ktip
KDE Daemon (kded) already running.
kdeinit4: preparing to launch /opt/kde4/bin/klipper
kdeinit4: preparing to launch /opt/kde4/bin/korgac

and wonder if it's a dbus problem, only or a problem with plasma itselfs.

Best Regards
Marcus

rvdboom · 01-15-2008, 12:55 AM

I would say a plasma issue. Try to remove the ~/.kde/share/config/plasmarc file (or something like that), it may be corrupted and plasma is not too solid yet.

rvdboom · 01-15-2008, 12:58 AM

Quote:

Originally Posted by duryodhan

aah boost ... I never quite got those libs working on my comp .. but lets try all this again ...

The last version 1.34.1 compiled without fuss on my Slack current.

MarcusMoeller · 01-15-2008, 07:27 AM

I am still having the same problems, even after deleting the complete .kde dirs:

Quote:

kdeinit4: preparing to launch
plasma(3601): Communication problem with "plasma" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

QDBusConnection received a message of type 3 that it shouldn't have
kdeinit4: preparing to launch /opt/kde4/bin/kaccess
kdeinit4: preparing to launch /opt/kde4/bin/nspluginscan
<stdin>:232:2: error: invalid preprocessing directive #nspluginviewer
<stdin>:233:2: error: invalid preprocessing directive #acroread
<stdin>:262:2: error: invalid preprocessing directive #GV
kdeinit4: preparing to launch /opt/kde4/bin/kmixctrl
kdeinit4: preparing to launch /opt/kde4/bin/ktip
KDE Daemon (kded) already running.
kdeinit4: preparing to launch /opt/kde4/bin/klipper
nspluginscan(3624) tryCheck: Plugin doesn't implement NP_GetValue
QDir::exists: Empty or null file name
kdeinit4: preparing to launch /opt/kde4/bin/korgac
QCoreApplication:

ostEvent: Unexpected null receiver
kded(3622): Communication problem with "kded" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

korgac(3630)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "The name org.kde.kded was not provided by an
y .service files"

Seems that dbus does not respond correctly. But qdbus replies correctly.

Best Regards
Marcus

rvdboom · 01-16-2008, 03:31 AM

Don't know. I notice that I have the same message as you have for plasma at startup, and still get a desktop, so I don't think the problem comes from there.
What problems do you have exactly? KDE doesn't start at all?

MarcusMoeller · 01-17-2008, 01:14 PM

Hmm.

I have now recompiled the whole thing and still getting similar errors:

Quote:

kdeinit4: preparing to launch /opt/kde4/bin/knotify4
kdeinit4: preparing to launch /opt/kde4/bin/krunner
kwin(5289): Couldn't start knotify from knotify4.desktop: "KDEInit could not launch '/opt/kde4/bin/knotify4'."

ALSA lib setup.c:555

add_elem) Cannot obtain info for CTL elem (MIXER,'IEC958 Playback Default',0,0,0): No such file or directory
X Error: BadMatch (invalid parameter attributes) 8
Extension: 155 (RENDER)
Minor opcode: 4 (RenderCreatePicture)
Resource id: 0x64
QCoreApplication:

ostEvent: Unexpected null receiver
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
kdeinit4: preparing to launch /opt/kde4/bin/plasma
X Error: BadMatch (invalid parameter attributes) 8
Extension: 155 (RENDER)
Minor opcode: 4 (RenderCreatePicture)
Resource id: 0x64
kdeinit4: preparing to launch
plasma(5305): Communication problem with "plasma" , it probably crashed.
Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

The problem is that KDE starts very slowly. e.g. it takes about 30 seconds for ktip to launch. Also plasma does not seem to work correctly after startup.

It's just silly strange.

Best Regards
Marcus

Alien_Hominid · 01-17-2008, 02:07 PM

You need composite extension enabled to get speed increase.