1 |
On Thursday, August 25, 2011 08:14:55 AM Dale wrote: |
2 |
> Hi, |
3 |
> |
4 |
> I mentioned in a thread a week or so ago that I was going to install |
5 |
> Gentoo on another box for a friend. Anyway, I got everything done and |
6 |
> now I run into this problem. I found a thread on the forums but it |
7 |
> seems to have just fixed itself. That's not working here tho. This is |
8 |
> the xsessions error file for the user: |
9 |
> |
10 |
> startkde: Starting up... |
11 |
> Connecting to deprecated signal |
12 |
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) |
13 |
> kbuildsycoca4 running... |
14 |
> No outputs have backlight property |
15 |
> QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought |
16 |
> it was ':1.5' |
17 |
> Object::connect: No such signal QDBusAbstractInterface::DeviceAdded(QString) |
18 |
> Object::connect: No such signal |
19 |
> QDBusAbstractInterface::DeviceRemoved(QString) |
20 |
> Object::connect: No such signal |
21 |
> QDBusAbstractInterface::DeviceAdded(QDBusObjectPath) |
22 |
> Object::connect: No such signal |
23 |
> QDBusAbstractInterface::DeviceRemoved(QDBusObjectPath) |
24 |
> Object::connect: No such signal |
25 |
> QDBusAbstractInterface::DeviceChanged(QDBusObjectPath) |
26 |
> QStringList |
27 |
> Solid::Backends::UDisks::UDisksManager::allDevicesInternal() error: |
28 |
> "org.freedesktop.DBus.Error.Spawn.ExecFailed" |
29 |
> kded(4259)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: |
30 |
> OpenGL vendor string: VIA Technology |
31 |
> OpenGL renderer string: Mesa DRI UniChrome (KM400) |
32 |
> 20060710 x86/MMX+/3DNow!+/SSE |
33 |
> OpenGL version string: 1.2 Mesa 7.10.3 |
34 |
> Driver: Unknown |
35 |
> GPU class: Unknown |
36 |
> OpenGL version: 1.2 |
37 |
> Mesa version: 7.10.3 |
38 |
> X server version: 1.10.3 |
39 |
> Linux kernel version: 3.0.3 |
40 |
> Direct rendering: no |
41 |
> Requires strict binding: yes |
42 |
> GLSL shaders: no |
43 |
> Texture NPOT support: no |
44 |
> kactivitymanagerd(4302): Communication problem with "kactivitymanagerd" |
45 |
> , it probably crashed. |
46 |
> Error message was: "org.freedesktop.DBus.Error.Disconnected" : " |
47 |
> "Connection was disconnected before a reply was received" " |
48 |
> |
49 |
> kdeinit4: Fatal IO error: client killed |
50 |
> kdeinit4: sending SIGHUP to children. |
51 |
> kded(4259) PowerDevilUPowerBackend::brightness: |
52 |
> org.kde.powerdevil.backlighthelper.brightness failed |
53 |
> klauncher: Exiting on signal 1 |
54 |
> kglobalaccel: Fatal IO error: client killed |
55 |
> Qt-subapplication: Fatal IO error: client killed |
56 |
> kwin: Fatal IO error: client killed |
57 |
> kdeinit4: Fatal IO error: client killed |
58 |
> kdeinit4: sending SIGHUP to children. |
59 |
> QProcess: Destroyed while process is still running. |
60 |
> kdeinit4: sending SIGTERM to children. |
61 |
> kdeinit4: Exit. |
62 |
> virtual QStringList |
63 |
> Solid::Backends::UPower::UPowerManager::allDevices() error: |
64 |
> "org.freedesktop.DBus.Error.Spawn.ExecFailed" |
65 |
> kded4: Fatal IO error: client killed |
66 |
> kdeinit4: sending SIGTERM to children. |
67 |
> kdeinit4: Exit. |
68 |
> |
69 |
> This rig has a Athlon XP 2000 which is not to slow. My old 2500+ still |
70 |
> works OK. It also has 1.2Gbs of ram. The only downside is the built-in |
71 |
> video. It is a Via km400. I have tried both Mesa and Vesa for this |
72 |
> thing but same error. |
73 |
> |
74 |
> It does let me login in failsafe mode tho. So, I guess KDE itself is |
75 |
> working but something that is needed in regular mode is not working right. |
76 |
> |
77 |
> Any ideas on what could cause this? |
78 |
|
79 |
Are the usual suspects running? |
80 |
Like dbus and consolekit? |
81 |
|
82 |
which kde-package(s) did you emerge? |
83 |
|
84 |
> Oh, another odd thing I noticed. When I start kdm, I can't switch back |
85 |
> to a console. That is starting to piss me off. I can't login to KDE |
86 |
> and it won't let me go back to a console either. Is that related or a |
87 |
> separate issue? |
88 |
|
89 |
I have seen this myself. Some NVidia-drivers caused this. Could be that your |
90 |
graphics-card-driver is causing a similar issue. |
91 |
|
92 |
Can you try logging in with a text-console (eg. without /etc/init.d/xdm in |
93 |
your runlevel) and then start X with kde? |
94 |
|
95 |
Eg: |
96 |
|
97 |
Put the following into your ~/.xinitrc: |
98 |
** |
99 |
exec /usr/local/kde4/bin/startkde |
100 |
** |
101 |
( % echo "exec /usr/local/kde4/bin/startkde" > ~/.xinitrc |
102 |
) |
103 |
|
104 |
Then start X from the command-line with: |
105 |
# startx |
106 |
|
107 |
The above commands do NOT need root-access. |
108 |
|
109 |
If this works, the issue is with the login. If this doesn't work, the kde- |
110 |
session can't start. |
111 |
|
112 |
-- |
113 |
Joost |