** Changed in: kdebase
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
https://bugs.launchpad.net/bugs/187918
Title:
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check
** Changed in: kdebase
Status: New = Invalid
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in
Cannot reproduce using a fresh installation of Ubuntu 8.10 + KDE nightly
from project neon.
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a member of Ubuntu
Closing unused PAM upstream bug watch.
** Changed in: pam
Status: New = Invalid
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a member of Ubuntu
Bugs,
That is _completely_ unrelated.
** Changed in: kdebase (Ubuntu)
Status: Incomplete = Fix Released
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a member
** Bug watch added: KDE Bug Tracking System #171533
http://bugs.kde.org/show_bug.cgi?id=171533
** Also affects: kdebase via
http://bugs.kde.org/show_bug.cgi?id=171533
Importance: Unknown
Status: Unknown
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
** Changed in: kdebase
Status: Unknown = New
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I think it's still an issue in Intrepid with kde4 at least, in fact I don't
when did this happened, but after an update/upgrade, I wasn't able to login
from kdm, I looked at .xsession-errors and there was only one error:
open: permission denied
I started a console login (by Ctrl-Alt-F2), no
Still an issue in Intrepid?
** Changed in: kdebase (Ubuntu)
Importance: Undecided = Medium
Status: Confirmed = Incomplete
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug
** Changed in: kdebase (Ubuntu)
Sourcepackagename: meta-kde4 = kdebase
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a member of Kubuntu
Team, which is
I don't use ldap but I have a very similar problem ...
When I choose a KDE4 session, the splash appears , the HD icon for 45s, then
the Settings icon for 4 or 5 minutes and eventually I get the the kdm blue
background with the cursor but that's all...
This behavior appeared just the day before
...
[EMAIL PROTECTED]:~$ sudo touch $HOME/foobar
[sudo] password for philippe:
[EMAIL PROTECTED]:~$ ls ~/foobar
/home/philippe/foobar
[EMAIL PROTECTED]:~$
...
Home is local,...
Before I started having this problem I received some messages boxes about D-Bus
errors just after login in kde4, as the
In that case, I'd suggest you check elsewhere. You might check
permissions of your user-specific configuration stuff, like .kde and
.kde4 and .kde4.1 if there is one, and .ICEauthority, .Xauthority,
.DCOPserver*, etc.
I don't think it's the same bug that you're describing.
--
[Hardy] KDE4 logon
Philippe,
Does KDE 4.0 work for you? This bug was originally about KDE 4.0, but it
seems to have been fixed.
Using:
dbus 1.1.20-1ubuntu2
dbus-x11 1.1.20-1ubuntu2
hal 0.5.11~rc2-ubuntu8.1
kubuntu-kde4-desktop 0.14
libdbus-1-3 1.1.20-1ubuntu2
linux-headers-generic 2.6.24.19.21
kde4-core 3.3
All the files your mentionned are mine, and I already tried the .kde4 delete
Thanx anyway
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a member of Ubuntu
For my surprise, today 24-jun, after the latest upgrade (which includes a ldap
update) my Kubuntu 4.0 IS working OK with Ldap authentication.
Thanks for the developers
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
Anyone knows the status of this bug? Should we stop using KDE4?
Regards
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a
My xorg.conf file:
Section InputDevice
Identifier Generic Keyboard
Driver kbd
Option XkbRules xorg
Option XkbModel abnt2
Option XkbLayout br
EndSection
Section InputDevice
Identifier
** Changed in: meta-kde4 (Ubuntu)
Status: Incomplete = Confirmed
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Oh, and using Hardy Heron (kubuntu-8.04-kde4.04-x86). It happens on every
machine I install on. Here are the video cards for two of them:
VGA compatible controller: nVidia Corporation NV18GL [Quadro NVS 280 SD] (rev
a2)
VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300
Okay, I've installed GDM and tried starting KDE that way. It fails as
well, same error message. GDM also gives me the option of viewing
.xsession-errors, and when I choose that option, THAT fails as well--
says it's unable to open the file (which is 644). For your viewing
pleasure, I've included a
I took a look the process table from a computer that runs Kde 3 and
authenticate with ldap int the right manner (running ps -aux from console) and
see that d-bus-daemon has the UID 104:
104 3960 0.0 0.2 6088 1148 ?Ss 09:14 0:00
/usr/bin/dbus-daemon --system
but in the
I've done a bit more troubleshooting, and narrowed the problem down
some. I think it has to do with the order system services are started
relative to PAM, or some permissions setting within PAM. Here's why:
In startkde, there is a section that begins with:
# D-Bus autolaunch is broken
if test -z
My experience is the same as Edsoncv; I also authenticate using LDAP. I
tried removing .kde*, .qt*, and .ICEauthority, but none of these things
helped. Pretty frustrating.
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
Exactly like Chris Warren described, with me this problem only happens when
I authenticate using LDAP (I installed Ldap client using this tutorial:
http://ubuntuforums.org/showthread.php?t=597056highlight=ldap ). I think it is
not a authentication problem since I can logon normally using
This happens to me when I switch to LDAP authentication. If I switch
back to default setup, I am able to get into kde again.
Hardy 8.04 i386
KDE 4.0.3
Geforce MX4400 (tried both nv and nvidia-glx drivers)
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
The same started today :(
I'm running Hardy 8.04 i386 / KDE 4.0.3.
I can run KDE3 (or IceWM) + KDE4 applications but not a full-session KDE4.
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug
Hi, the .ICEauthorithy file already belongs to me
Any other idea ?
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I remember a similar situation that effected both KDE3 and KDE4.
Somehow, the .ICEauthority file's permissions were changed so that root
owned it. I wonder if this would fix any of the problems?
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
Oh wow, total brainfart. To fix the .ICEauthority problem, you had to
change the permissions back to you owning the file. I wonder if this
solution would work around this problem?
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
experiencing the same with:
- kubuntu gutsy 7.10 32 bit
- kde 4.0.3
- nvidia 7900 gs driver nvidia 169.12
I had not this problem with the same system and kde 4.0.2
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
Hello, I'm currently having this pb
- Ubuntu Hardy 8.04 amd64 updated
- using current version of kde 4 on hardy (how can i know the version ?)
- video card : nvidia quadro 4500, compiz enabled
On an other computer configured nearly in the same way except it's a 32
bit CPU, everything goes fine,
Are you still experiencing this issue? If so can you provide some
further information such as:
1) Version of Ubuntu/Kubuntu you are using
2) Using version 4.0.1 of KDE 4
3) Your video card and driver information
I know there are quite a few people using KDE 4 in a similar environment
as you by
** Tags added: kde4
--
[Hardy] KDE4 logon failure: 'startkde: Could not start D-Bus. Check your
installation.'
https://bugs.launchpad.net/bugs/187918
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Interestingly enough, when I run:
/usr/lib/kde4/bin/startkde from the CLI with sudo, I don't get the
error. The splash displays but does nothing further, whereas if I run
startkde from CLI w/o root privileges, I get the above-mentioned error.
Could it be a permissions problem?
--
[Hardy] KDE4
35 matches
Mail list logo
