LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-14-2008, 04:20 PM   #1
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Rep: Reputation: 227Reputation: 227Reputation: 227
KDE4.1 on current - problems running


So I have downloaded the /testing directory from current to my slackware/current mirror and followed the instructions in /testing/packages/kde4/README on my current install.

When trying to run KDE4.1 with startx I get the splash screen of 4.1 up with the new icons coming into focus as KDE initialises.

I then see a very brief view of the new desktop (too quick to comment on) and then KDE crashes.

For debugging I ran "startx > kde4mess.txt 2>kdeerr.txt" to capture all the messages that went scrolling by.

Here is kde4mess.txt:
Code:
GOT SIGHUP
and here is the end of the kdeerr.txt:

Code:
<unknown program name>(2843)/ kdemain: Xlib XKB extension major= 1  minor= 0
kdeinit4: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/ed/.gtkrc::/home/ed/.kde/share/config/gtkrc' from klauncher.
kdeinit4: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/ed/.gtkrc-2.0::/home/ed/.kde/share/config/gtkrc-2.0' from klauncher.
kcminit(2818)/kcontrol KCMInit::runModule: Initializing  "kcm_input" :  "kcminit_mouse"
ksmserver(2820) KSMServer::kcmPhase1Done: Kcminit phase 1 done
kdeinit4: Got EXEC_NEW '/usr/bin/kmixctrl' from launcher.
kdeinit4: preparing to launch /usr/bin/kmixctrl
klauncher(2810)/kio (KLauncher) KLauncher::processRequestReturn: "/usr/bin/kmixctrl" (pid 2847) up and running.
ksmserver(2820) KSMServer::autoStart1Done: Autostart 1 done
kded(2812)/kded4 Kded::loadSecondPhase: Loading second phase autoload
kdeinit4: Got EXEC_NEW '/usr/bin/hp-systray' from launcher.
kdeinit4: preparing to launch /usr/bin/hp-systray
kded(2812)/kded4 Kded::loadModule: Successfully loaded module "remotedirnotify"
klauncher(2810)/kio (KLauncher) KLauncher::processRequestReturn: "/usr/bin/hp-systray" (pid 2848) up and running.
kdeinit4: Got EXEC_NEW '/usr/bin/guidance-power-manager' from launcher.
kdeinit4: preparing to launch /usr/bin/guidance-power-manager
klauncher(2810)/kio (KLauncher) KLauncher::processRequestReturn: "/usr/bin/guidance-power-manager" (pid 2849) up and running.
kdeinit4: Got EXEC_NEW '/usr/bin/printer-applet' from launcher.
kdeinit4: preparing to launch /usr/bin/printer-applet
kded(2812)/kdecore (KLibLoader) kde4Factory: The library "/usr/lib/kde4/solid_fakenet.so" does not offer a qt_plugin_instance function.
kded(2812)/kdecore (KLibLoader) kde3Factory: The library "/usr/lib/kde4/solid_fakenet.so" does not offer an "init_solid_fakenet" function.
kded(2812) Solid::Control::ManagerBasePrivate::loadBackend: Error loading ' "Fake Net" ', KService said:  "QLibrary::resolve_sys: Symbol "init_solid_fakenet" undefined in /usr/lib/kde4/solid_fakenet.so (/usr/lib/kde4/solid_fakenet.so: undefined symbol: init_solid_fakenet)"

Backtrace:
0: X(xf86SigHandler+0x7e) [0x80d8b5e]
1: [0xffffe420]
2: /usr/lib/xorg/modules//libxaa.so [0xb7a9bac8]
3: /usr/lib/xorg/modules//libxaa.so [0xb7add897]
4: X [0x8164f9e]
5: X(ValidateGC+0x25) [0x80945d5]
6: /usr/lib/xorg/modules//libxaa.so [0xb7ade09c]
7: /usr/lib/xorg/modules//libxaa.so [0xb7ade4cf]
8: X [0x816618f]
9: X(compPaintWindowBackground+0x6d) [0x80fb6cd]
10: X(miWindowExposures+0xf2) [0x81172e2]
11: X [0x80dcdd5]
12: X(miHandleValidateExposures+0x78) [0x812d118]
13: X(MapWindow+0x3aa) [0x807267a]
14: X(ProcMapWindow+0x66) [0x8086096]
15: X [0x814628e]
16: X(Dispatch+0x2bf) [0x808688f]
17: X(main+0x48b) [0x806ddab]
18: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7cf0390]
19: X(FontFileCompleteXLFD+0x20d) [0x806d121]

Fatal server error:
Caught signal 11.  Server aborting

kded(2812)/networkstatus NetworkStatusModule::registerNetwork: "SolidNetwork" , with status  0  is owned by  ":1.2"
kded(2812)/kded4 Kded::loadModule: Successfully loaded module "networkstatus"
klauncher(2810)/kio (KLauncher) KLauncher::processRequestReturn: "/usr/bin/printer-applet" (pid 2850) up and running.
kdeinit4: Got EXEC_NEW '/usr/bin/klipper' from launcher.
kdeinit4: preparing to launch /usr/bin/klipper
klauncher(2810)/kio (KLauncher) KLauncher::processRequestReturn: "/usr/bin/klipper" (pid 2851) up and running.
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
QObject: Do not delete object, 'unnamed', during its event handler!
QDBusConnectionPrivate::connectSignal: received error from D-Bus server while connecting signal to org::kde::KCMInit::phase2Done(): org.freedesktop.DBus.Error.Disconnected (Connection is closed)
ksmserver(2820) KToolInvocation::klauncher: klauncher not running... launching kdeinit
[/usr/bin/nepomukservicestub] QObject: Do not delete object, 'unnamed', during its event handler!
[/usr/bin/nepomukservicestub] QObject: Do not delete object, 'unnamed', during its event handler!
<unknown program name>(2840)/: Communication problem with  "kaccess" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.Disconnected" : " "Connection was disconnected before a reply was received" " 

kdeinit4: PID 2840 terminated.
kdeinit4: Fatal IO error: client killed
kcminit_startup: Fatal IO error: client killed
kdeinit4: sending SIGHUP to children.
kdeinit4: sending SIGTERM to children.
kdeinit4: Exit.
klauncher: Exiting on signal 15
klauncher: Exiting on signal 1
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 25 requests (8 known processed) with 0 events remaining.
xinit:  connection to X server lost.
Hangup
kded4: Fatal IO error: client killed
QProcess: Destroyed while process is still running.
Could not connect to D-Bus server: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /tmp/dbus-2YlXzqPSTy: Connection refused
startkde: Shutting down...
kdeinit4_wrapper: Warning: connect(/home/ed/.kde/socket-bgeddy/kdeinit4__0) failed: : No such file or directory
Error: Can not contact kdeinit4!
startkde: Running shutdown scripts...
xprop:  unable to open display ':0'
usage:  xprop [-options ...] [[format [dformat]] atom] ...

where options include:
    -grammar                       print out full grammar for command line
    -display host:dpy              the X server to contact
    -id id                         resource id of window to examine
    -name name                     name of window to examine
    -font name                     name of font to examine
    -remove propname               remove a property
    -set propname value            set a property to a given value
    -root                          examine the root window
    -len n                         display at most n bytes of any property
    -notype                        do not display the type field
    -fs filename                   where to look for formats for properties
    -frame                         don't ignore window manager frames
    -f propname format [dformat]   formats to use for property of given name
    -spy                           examine window properties forever

xprop:  unable to open display ':0'
usage:  xprop [-options ...] [[format [dformat]] atom] ...

where options include:
    -grammar                       print out full grammar for command line
    -display host:dpy              the X server to contact
    -id id                         resource id of window to examine
    -name name                     name of window to examine
    -font name                     name of font to examine
    -remove propname               remove a property
    -set propname value            set a property to a given value
    -root                          examine the root window
    -len n                         display at most n bytes of any property
    -notype                        do not display the type field
    -fs filename                   where to look for formats for properties
    -frame                         don't ignore window manager frames
    -f propname format [dformat]   formats to use for property of given name
    -spy                           examine window properties forever

startkde: Done.
ksmserver(2820): Couldn't start knotify from knotify4.desktop:  "KLauncher could not be reached via D-Bus. Error when calling start_service_by_desktop_path:
empty
" 

QDBusConnectionPrivate::connectSignal: received error from D-Bus server while connecting signal to KNotificationManager::notificationClosed(int): org.freedesktop.DBus.Error.Disconnected (Connection is closed)
QDBusConnectionPrivate::connectSignal: received error from D-Bus server while connecting signal to KNotificationManager::notificationActivated(int,int): org.freedesktop.DBus.Error.Disconnected (Connection is closed)
ksmserver(2820)/kdeui (KNotification) KNotification::close: 0
ksmserver(2820)/kdeui (KNotification) KNotification::~KNotification: -2
Apologies for the length of the error file - the entire file is 911KB !! Hopefully the bit I've shown is useful to someone knowledgable with KDE4.

Anyone any ideas what going on ? I know running current I should be tracking down problems myself but I am by no means a KDE expert - especially not with KDE 4.1.
 
Old 08-14-2008, 04:52 PM   #2
darkhatter
Member
 
Registered: Dec 2005
Distribution: Slackware 12.1/Current
Posts: 159

Rep: Reputation: 30
Doing a quick scan I noticed a few DBUS errors, do you have that installed?
 
Old 08-14-2008, 05:24 PM   #3
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
Well this is an up to date current system.

I have /etc/rc.d/rc.messagebus set with perms 0755 so it runs on boot.

Also "ps aux | grep dbus" gives "/usr/bin/dbus-daemon --system" as a process.

The only changes I've made to the system are the instructions in the README.
 
Old 08-14-2008, 05:39 PM   #4
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,617

Rep: Reputation: 136Reputation: 136
Does your qt package match your new KDE version ?
I mean KDE wants a compatible qt package installed for working well,
sorry if you already checked that
 
Old 08-14-2008, 08:51 PM   #5
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
Does your qt package match your new KDE version ?
I'm not sure how to check that. Presumably KDE 4.1 needs QT4.

But apologies if I'm repeating myself or stating the obvious.

I have kept my install of "current" up to date and merely followed the instructions in current/testing/kde4/README which apply to kde4.1.

I take it the aforementioned instructions are relevant to an updated current system - I simply followed these.

Again - apologies for asking for help on a current system. Yes this is a proving ground for what is possibly the next version of Slackware - in fact I have been running current on a test box for some years.

My way of keeping my curent test system up to date has always been by mirroring the current tree to a separate partition and upgrading/new installing/deleting by referring to ChangeLog.txt. The mirroring being accomplished with Alien Bob's mirror scripts involving rsync.

I suppose it is possible my version of current is missing out on an upgrade to a package that has been rolled out through the current tree but I doubt it.

Thanks to all who have replied...I can't wait to see how KDE4 shapes up !
 
Old 08-15-2008, 07:20 AM   #6
keefaz
Senior Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 4,617

Rep: Reputation: 136Reputation: 136
Here is the mentioned README file
(it is always best to give a reference/address when you talk about a specific file)
A light resume:
- You'll need to uninstall *all* qt and kde apps
- if you have not already had previous kde4packages from here installed, you'll need to remove (and backup) /etc/kde (rm -rf /etc/kde) and backup your $HOME/.kde/ directory
- From the /testing/packages/kde4/ directory, use this command:upgradepkg --install-new deps/*.tgz extragear/*.tgz kde/*.tgz kde3-compat/*.tgz
- Then, if you need any of the language packs in kde-l10n, install those. You'llalso want to log out and back in before starting kde4 to set the proper QTDIR.

So as I can see, the compatible QT package is in the deps directory...
I assume you did all those steps... Sorry can't help much here
 
Old 08-15-2008, 09:21 AM   #7
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
Here is the mentioned README file
(it is always best to give a reference/address when you talk about a specific file)
Yes - thanks for the reference . I assumed responders would have caried out the upgrade and so knew the contents of the README. Not a very wise assumption now I think about it..

Quote:
So as I can see, the compatible QT package is in the deps directory...
I assume you did all those steps... Sorry can't help much her
Yes - thats what I did. Thanks for your time anyway.
 
Old 08-17-2008, 07:13 PM   #8
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 212
Blog Entries: 15

Rep: Reputation: 17
I am having what _look like_ the same problems (e.g. I am seeing the same thing as the OP) but my equivalent to his kdeerr.txt is an even longer/larger file. I am not even sure where to begin troubleshooting it. I was careful to follow the README.
 
Old 08-17-2008, 11:17 PM   #9
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
Quote:
I am having what _look like_ the same problems (e.g. I am seeing the same thing as the OP) but my equivalent to his kdeerr.txt is an even longer/larger file.
Well I have only posted the last bit of my error file as the whole thing was over 900KB long.
Quote:
I am not even sure where to begin troubleshooting it. I was careful to follow the README.
Same here. I followed the README to the letter and even re did the process several times.

I too have no idea what to do next as I feel I'm just stumbling round in the dark trying to fix this ! Oh well..

Thanks for replying and although I'm sorry to hear your having the same problems at least it not just me !
 
Old 08-18-2008, 07:39 AM   #10
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 212
Blog Entries: 15

Rep: Reputation: 17
I have it seems managed to slightly alter (well, worsen) the behavior I am seeing on trying to start KDE 4.1.

I got slightly paranoid I had missed some update or other in -current, so I compared the PACKAGES.TXT file I got from slackware-current to what I had installed. There were a couple of differences: I had apparently missed an update to aaa_elflibs (I had 12.1.0, the tree has 12.1.1) and a couple of other things I didn't feel were relevant but downloaded and installed anyway.

Now, instead of crashing, I see the distorted desktop view and everything freezes. Hangs. Can't even CTRL-ALT-BACKSPACE down from it.

I will have to see if I can try to troubleshoot it - if I can get a trace of the errors.

Strangely, I am able to run KDE apps (I tried KStars, a favorite) via fluxbox ...

Part of me wonders whether this laptop (Dell PIII 1000mHz) is even up to the task of running this DE. If I can get the apps I like via different window managers, maybe I shouldn't bother ...
 
Old 08-18-2008, 08:13 AM   #11
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,334

Rep: Reputation: Disabled
That aaa_elflibs-12.1.1 is part of Slackware 12.1 even. With a configuration like yours which is not 12.1 nor -current, anything may happen.
I suggest re-installing from scratch, or using slackpkg to track down the missing / outdated packages.
Also, try (re-)moving ~/.kde and see if a fresh start of KDE4.1 works better afterwards.

Eric
 
Old 08-18-2008, 08:36 AM   #12
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 212
Blog Entries: 15

Rep: Reputation: 17
Quote:
Originally Posted by Alien Bob View Post
That aaa_elflibs-12.1.1 is part of Slackware 12.1 even. With a configuration like yours which is not 12.1 nor -current, anything may happen.
I suggest re-installing from scratch, or using slackpkg to track down the missing / outdated packages.
Also, try (re-)moving ~/.kde and see if a fresh start of KDE4.1 works better afterwards.

Eric
Thanks, Eric. I will give slackpkg a try. I did remove $HOME/.kde/ before trying this. I'll follow up ...
 
Old 08-18-2008, 09:52 PM   #13
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 212
Blog Entries: 15

Rep: Reputation: 17
slackpkg worked great ... although it really wanted to upgrade me to a huge kernel ...

My system is all 'clean' now. I have retreated from KDE 4.1 for the time being. I will see what happens when they make their way out of testing, I guess.
 
Old 08-19-2008, 04:07 PM   #14
bgeddy
Senior Member
 
Registered: Sep 2006
Location: Liverpool - England
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810

Original Poster
Rep: Reputation: 227Reputation: 227Reputation: 227
I've not used slackpkg before as i prefer to do things manually with pkgtools and rsync.

Anyway I tried slackpkg install-new and slackpkg upgrade-all before running the steps in the README again.

Still the same behavior unfortunately.
 
Old 03-29-2009, 01:57 PM   #15
chexmix
Member
 
Registered: Apr 2002
Location: Arlington, MA
Distribution: Slackware, Debian, OpenBSD
Posts: 212
Blog Entries: 15

Rep: Reputation: 17
bgeddy, did you ever wind up with a usable KDE4.x?

I ask mainly because I b0rked up my -current installation on the laptop I was using in re: this thread, and installed a completely new -current. I got the same behavior I described in my second post above: nice splash screen, then horizontally truncated / striated / blurry view of the desktop, then total freeze-up.

So I can only presume my version of qt is the right one, since everything is -current, and ...

It's frustrating. I have a new netbook and am sorely tempted to upgrade it to -current, but I'd like to understand what is going on here first.

G
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
KDM-KDE4 Configuration problems Yoda3114 Linux - Software 2 07-30-2008 02:48 PM
No Panels Running kde4 Under Ubuntu Tim_Olaguna Ubuntu 2 07-26-2008 05:22 PM
LXer: Running KDE4 (Final) on Mandriva 2008 LXer Syndicated Linux News 0 01-27-2008 03:11 PM
Dependency problems with KDE:KDE4 roastedmnm Suse/Novell 2 01-23-2008 08:04 PM
LXer: Running KDE4 (preview) on Mandriva 2008 LXer Syndicated Linux News 0 10-14-2007 07:11 PM


All times are GMT -5. The time now is 06:42 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration