FAQ Search Today's Posts Mark Forums Read

» Linux Archive
Home
New Posts
Search
FAQ


Go Back   Linux Archive > Debian > Debian KDE

 
 
LinkBack Thread Tools
 
Old 02-10-2008, 08:42 PM
David Baron
 
Default Experiences with KDE4 on Sid

I did get everything installed. Some are on experimental, some off Sid. I
finally installed udev for the hal stuff needed by the kde4. All fine.

>From kdm, I cannot get a kde4 session running. Crash after crash. Depending
upon the profile paths, the kde3 desktop may come up. Knotify4 will crash
repeatedly (but I can move that out of the way if I so choose).

I CAN get kde4 running from a "failsafe" session by "sudo startkde" in the
xterm window. Without the root privileges, same crashes as from kdm. (The
root runs are problematic because of setting root ownership of .kde4 stuff,
and this is simply dangerous and not desirable.)

Clued from some kubuntu complaints: Is dbus (used instead of dcop) OK? It IS
running. However, I have dbus-launcher instances stuck in memory, one for the
user and one for root. These should have gone away immediately since dbus was
started on bootup.

HAL: Its udev rule cites a socket file. There is no such file. The URI is not
to any /dev entry.

I have filed the bugs but KDE-for-Debian is not really addressing these as of
yet. Some folks have apparently succeeded in running it (and I do not mean
live CDs or virtual machines). Any ideas?


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 02-11-2008, 11:33 AM
Kevin Krammer
 
Default Experiences with KDE4 on Sid

On Sunday 10 February 2008, David Baron wrote:

> Clued from some kubuntu complaints: Is dbus (used instead of dcop) OK? It
> IS running. However, I have dbus-launcher instances stuck in memory, one
> for the user and one for root. These should have gone away immediately
> since dbus was started on bootup.

No idea about the other issues, but this one sounds OK.
If you are running KDE sessions, you should have a dbus-launch process for
each of them, since each session has a D-Bus session bus.

The one started at bootup is called the system bus, basically a D-Bus server
for applications of different users/priviledges which want to interact, e.g.
a user GUI accessing a system service.

Cheers,
Kevin
--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
 

Thread Tools




All times are GMT. The time now is 06:07 AM.

VBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org