KDE/Gtk and Perhaps X Errors
in [Slackware]
|
Prev: Pidgin 2.6.5
Next: Compiling 2.6.32.9 on Slackware 13
From: Peter Chant on 26 Feb 2010 02:50 Any thoughts? Just playing with desk top effects in kde, slack 13.0, and the desktop crashed. Now I find I cannot log in using kde nor can I use kde / qt apps from xcfe etc. Tried renaming .kde4 and .config to see if it was something in there to no avail. Note however that root can still run kde4. Trying to run kmail from within xcfe: bash-3.1$ kmail QGtkStyle cannot be used together with the GTK_Qt engine. <unknown program name>(4926)/: Communication problem with "kmail" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " ====== Trying to startup kde from the command line: xauth: creating new authority file /home/pete/.serverauth.4703 X.Org X Server 1.6.3 Release Date: 2009-7-31 X Protocol Version 11, Revision 0 Build Operating System: Slackware 13.0 Slackware Linux Project Current Operating System: Linux phoenix 2.6.31.6 #1 SMP Sat Nov 21 19:27:48 GMT 2009 x86_64 Build Date: 03 August 2009 07:39:15PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 26 07:41:00 2010 (==) Using config file: "/etc/X11/xorg.conf" (EE) Failed to load module "freetype" (module does not exist, 0) (EE) Failed to load module "type1" (module does not exist, 0) (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:1) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:1) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:5:1) found /home/pete/.xinitrc: line 28: fusion-icon: command not found xset: bad font path element (#23), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax startkde: Starting up... kdeinit4: preparing to launch /usr/lib64/kde4/libexec/klauncher kdeinit4: preparing to launch /usr/bin/kded4 QGtkStyle cannot be used together with the GTK_Qt engine. kded(4774): Communication problem with "kded" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by m essage bus)" " kdeinit4: preparing to launch /usr/bin/kcminit_startup QGtkStyle cannot be used together with the GTK_Qt engine. kdeinit4: preparing to launch /usr/bin/ksmserver QGtkStyle cannot be used together with the GTK_Qt engine. startkde: Shutting down... klauncher: Exiting on signal 1 startkde: Running shutdown scripts... startkde: Done. waiting for X server to shut down bash-3.1$
From: jr4412 on 26 Feb 2010 10:48 On 26 Feb, 07:50, Peter Chant <pet...(a)MOpetezilla.coV.Euk> wrote: > Any thoughts? Just playing with desk top effects in kde, slack 13.0, and > the desktop crashed. Now I find I cannot log in using kde nor can I use > kde / qt apps from xcfe etc. > > Tried renaming .kde4 and .config to see if it was something in there to > no avail. Note however that root can still run kde4. > > Trying to run kmail from within xcfe: > > bash-3.1$ kmail > QGtkStyle cannot be used together with the GTK_Qt engine. > <unknown program name>(4926)/: Communication problem with "kmail" , it > probably crashed. > Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did > not receive a reply (timeout by message bus)" " > > ====== > > Trying to startup kde from the command line: > > xauth: creating new authority file /home/pete/.serverauth.4703 > > X.Org X Server 1.6.3 > Release Date: 2009-7-31 > X Protocol Version 11, Revision 0 > Build Operating System: Slackware 13.0 Slackware Linux Project > Current Operating System: Linux phoenix 2.6.31.6 #1 SMP Sat Nov 21 > 19:27:48 GMT 2009 x86_64 > Build Date: 03 August 2009 07:39:15PM > > Before reporting problems, checkhttp://wiki.x.org > to make sure that you have the latest version. > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 26 07:41:00 2010 > (==) Using config file: "/etc/X11/xorg.conf" > (EE) Failed to load module "freetype" (module does not exist, 0) > (EE) Failed to load module "type1" (module does not exist, 0) > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:1) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:1) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) > found > (WW) fglrx: No matching Device section for instance (BusID PCI:0@1:5:1) > found > /home/pete/.xinitrc: line 28: fusion-icon: command not found > xset: bad font path element (#23), possible causes are: > Directory does not exist or has wrong permissions > Directory missing fonts.dir > Incorrect font server address or syntax > startkde: Starting up... > kdeinit4: preparing to launch /usr/lib64/kde4/libexec/klauncher > kdeinit4: preparing to launch /usr/bin/kded4 > QGtkStyle cannot be used together with the GTK_Qt engine. > kded(4774): Communication problem with "kded" , it probably crashed. > Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did > not receive a reply (timeout by m > essage bus)" " > > kdeinit4: preparing to launch /usr/bin/kcminit_startup > QGtkStyle cannot be used together with the GTK_Qt engine. > kdeinit4: preparing to launch /usr/bin/ksmserver > QGtkStyle cannot be used together with the GTK_Qt engine. > startkde: Shutting down... > klauncher: Exiting on signal 1 > startkde: Running shutdown scripts... > startkde: Done. > > waiting for X server to shut down > > bash-3.1$ have you checked for stale lock files? (in '/tmp/kde-<user>/' or similar, from memory)
From: Peter Chant on 27 Feb 2010 09:13 Peter Chant wrote: > Tried renaming .kde4 and .config to see if it was something in there to > no avail. Note however that root can still run kde4. Sorted. Something in .kde was the issue. Moved it and copied important config files across. Pete -- http://www.petezilla.co.uk
From: Peter Chant on 27 Feb 2010 19:34 jr4412 wrote: > have you checked for stale lock files? (in '/tmp/kde-<user>/' or > similar, from memory) No, but my sledgehammer approach seems to have fixed things. I think that playing with desktop effects was the issue. Pete -- http://www.petezilla.co.uk
|
Pages: 1 Prev: Pidgin 2.6.5 Next: Compiling 2.6.32.9 on Slackware 13 |