LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
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 11-19-2004, 02:23 AM   #1
N|k0N
Member
 
Registered: Aug 2004
Location: New York
Posts: 63

Rep: Reputation: 15
konqueror problems


earlier on last night i used swaret to update the packages that i needed since i never updated anything since i installed slack 3 months ago. The problem i am having now is after installing the packages that i need, whenever i try to open konqueror to view my files it tells me it is not supported and when i try to go into konqueror's settings to look around to see if anything is unchecked or maybe i could fix it myself, when i click on certain icons i get this:

Quote:
The diagnostics is:
Library files for "libkcm_konqhtml.la" not found in paths
Possible reasons:
An error occurred during your last KDE upgrade leaving an orphaned control module
You have old third party modules lying around.
Check these points carefully and try to remove the module mentioned in the error message. If this fails, consider contacting your distributor or packager.
Now I am guessing this library had to exist sometime before unless i couldnt be able to use konqueror at all, now how can i find out how to re-link this library so i can end this problem or is the problem deeper than i might think?Now i tried to look in my control center and it is telling me other library files similar to the one i posted above(all ending in .la) are missing too. Did I do something wrong when i updated or left something out?

Last edited by N|k0N; 11-19-2004 at 02:28 AM.
 
Old 11-19-2004, 06:23 PM   #2
tw001_tw
Member
 
Registered: Mar 2003
Location: St. Louis, MO
Distribution: kubuntu-current
Posts: 551
Blog Entries: 4

Rep: Reputation: 31
Just a thought:

Did you remove the running of "ldconfig" at startup? (it is ran automatically
when I do a full install).

Or just try running ldconfig at the CLI.

May or may not work, but it might be worth a try.
Start simple then move on.
 
Old 11-19-2004, 07:54 PM   #3
N|k0N
Member
 
Registered: Aug 2004
Location: New York
Posts: 63

Original Poster
Rep: Reputation: 15
My computer hasnt been restarted in over 28 days, so i dont think that is the problem. Also, how can i run ldconfig at CLI? What exactly does that mean?
 
Old 11-19-2004, 10:16 PM   #4
tw001_tw
Member
 
Registered: Mar 2003
Location: St. Louis, MO
Distribution: kubuntu-current
Posts: 551
Blog Entries: 4

Rep: Reputation: 31
ldconfig updates your shared libraries.
(since you updated, thats what put it in my mind)

at the prompt - not sure off hand, but I think you have to be root or SU,

just type:

ldconfig

and then it churns for a bit and its done. Simple and should only take a minute or 2.

worth a try anyway.
 
Old 11-20-2004, 07:12 AM   #5
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 768

Rep: Reputation: 64
tw001_tw has a good point, I hope that will fix it.

If not, see if you can make any sense from my ramblings:

'An error occurred during your last KDE upgrade leaving an orphaned control module'

I had a similar situation with the KDE font installer a while back.

Your 'missing' library file comes from the kdebase package, but you have the newer version, it is the module that is calling for this file that is out of date.

later versions of kde seem to favour the form kcm_konqhtml.la over libkcm_konqhtml.la,
that is they changed their naming system slightly.

What version of kde did you upgrade to? It looks like kde 3.2 is the latest in slackware 10,
the first thing I would do is check that all the kde and qt packages in your mirror's
/slackware/slackware-10.0/patches/packages/ dir ties up with what you have locally in /var/log/packages/

if that all looks ok, try reinstalling the kde packages
swaret --reinstall kde
should do it. Just to be on the safe side, dont do it with kde running. Reboot to runlevel 3 and do it from
the command line. (Modify /etc/inittab to change runlevel, use 'pico /etc/inittab' as root to change it back)


(Only if you upgraded to current: then you must make sure that the imlib package is also installed, this is new since kde 3.3)

tobyl
(ps. insert 'at you own risk' disclaimer here...)
 
Old 11-20-2004, 11:07 PM   #6
N|k0N
Member
 
Registered: Aug 2004
Location: New York
Posts: 63

Original Poster
Rep: Reputation: 15
Now I have a new problem, i cannot get my kde to start up at all, i went with the idea of checking the libraries and then using swaret to reinstall kde. X -config/startkde or startx doesnt work anymore, i just get a blank screen now.What i realized was that during the upgrade some of the kde packages download failed, so maybe that is why certain libraries cannot be found. But what really confuses me is when i try to use swaret to upgrade again to see if i can re-dowload these packages, swaret installed some of the other packages that failed during downloading before also but not the kde one's, am i missing something? I guess for now i will just use fluxbox or another of the desktops until i figure this problem out, any help would be appreciated..

Last edited by N|k0N; 11-21-2004 at 02:19 AM.
 
Old 11-21-2004, 12:40 PM   #7
tw001_tw
Member
 
Registered: Mar 2003
Location: St. Louis, MO
Distribution: kubuntu-current
Posts: 551
Blog Entries: 4

Rep: Reputation: 31
So due to some files not being downloaded, thus not installed, you have a
partially upgrade kde?

If so, did you try:

swaret --upgrade kde

and have "DEPENDENCY=1" in your swaret.conf ?

Also, what versions of kde are we dealing with here.
Did you just update kde 3.2 from '10.0' or go to 3.3 in 'current'?
 
Old 11-21-2004, 01:56 PM   #8
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 768

Rep: Reputation: 64
N|k0N
Also, bear in mind that swaret will use packages already downloaded to /var/swaret before re-downloading new packages. I think you may need to delete from there and start again. (hope you have dsl!) It may be worth trying a different mirror if you are getting a corrupted package(s).
tobyl
 
Old 11-21-2004, 07:01 PM   #9
DaWallace
Member
 
Registered: Feb 2004
Location: Southern Maine, United States
Distribution: Slackware Ubuntu Debian FreeBSD
Posts: 418

Rep: Reputation: 31
swaret --purge... if you want to be safe... if you don't have the bandwidth go into /var/swaret and manually delete the ones that failed
 
Old 11-22-2004, 05:41 PM   #10
N|k0N
Member
 
Registered: Aug 2004
Location: New York
Posts: 63

Original Poster
Rep: Reputation: 15
Since it was my first time installing the update it should be from kde 3.2 on 10.0. I dont think it is 3.3 to current. I purged the files and im going to start over again i could be wrong though. Im going to try the update, i have cable(9mbps down/1.5mbps up) so i should be fine with the online speeds.Hopefully this works, dont want to ever use windows as far as i am concerned again.

Last edited by N|k0N; 11-23-2004 at 02:17 AM.
 
Old 11-23-2004, 07:23 PM   #11
N|k0N
Member
 
Registered: Aug 2004
Location: New York
Posts: 63

Original Poster
Rep: Reputation: 15
I purged all the files in /var/swaret/ to make it easier for me but whenever i use swaret --upgrade or update, it tells me all the files are already updated. So i improvised and used swaret --dep and then swaret --dep kde it said all the files are there for the kde even though i saw that some files failed in the log file. So i am confused here, a lil lost. Did i miss something? Anyone have any ideas, becausen when i try to run startx my screen just stays blank, when i try to use strartkde i get this message
Quote:
xsetroot: unable to open display ' ' xset: unable to open display'''' xset: unable to open display'''' xset: unable to open display'''' setroot: unable to open display ' ' startkde: starting up... ksplash: cannot connect to the X server kdeinit: Aborting $DISPLAY is not set. Warning: connect() failed : No such file or directory
ksmserver: canot connect to X server
startkde: Shutting down...
Warning: connect() failed : No such file or directory
Error: Can't connect kdeinit!
startkde: Running shutdown scripts...
startkde: Done
Hopefully this helps someone to help me solve this frustrating problem. Using lynx isnt so bad, but it gets kinda dull after a while..
 
Old 11-23-2004, 07:59 PM   #12
tw001_tw
Member
 
Registered: Mar 2003
Location: St. Louis, MO
Distribution: kubuntu-current
Posts: 551
Blog Entries: 4

Rep: Reputation: 31
N|k0N,

Since you have two issues here, could you post 2 files?
(or maybe 1 issue)

/etc/swaret.conf & /etc/X11/xorg.conf

I'm sure that will help a bit.

Also, have you tried running xorgconfig?

-tw
 
Old 11-23-2004, 08:36 PM   #13
N|k0N
Member
 
Registered: Aug 2004
Location: New York
Posts: 63

Original Poster
Rep: Reputation: 15
i just ran xorgconfig and hopefully that might work. I will post both of those directories when i use my laptop with lynx(if i can fiure out how to do it...
 
Old 11-24-2004, 04:38 PM   #14
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 768

Rep: Reputation: 64
N|k0N,
what I had in mind was swaret --reinstall kde.
I don't think swaret --upgrade or update would work on its own, as you did this already. I think your X problems may disappear once you have a good kde setup.
so swaret purge - update - reinstall kde, in that order (hopefully)

tobyl
 
Old 11-27-2004, 11:46 AM   #15
N|k0N
Member
 
Registered: Aug 2004
Location: New York
Posts: 63

Original Poster
Rep: Reputation: 15
I tried using swaret in the exact order that you mentioned to use it and when i use startx or startkde i still cannot get anything to show up on my screen. I am lost and confused right about now, when i ran swaret and purged everything, then updated and then reinstalled kde this time all the files installed and didnt fail like last time, but i am still stuck, Dont know what to do......
 
  


Reply



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
Konqueror problems mem0ryleak2005 Mandriva 2 10-12-2005 06:11 PM
locking up problems with Konqueror 3.30 Kilahchris Linux - Software 6 06-17-2005 12:38 AM
Konqueror problems shaneblyth Linux - Software 3 04-18-2004 12:49 PM
Problems with Konqueror JoeDuncan Linux - Software 3 09-10-2003 11:47 AM
problems with Konqueror DarkGhost Linux - General 9 06-04-2002 01:20 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:37 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration