After installing 3.1, Konqueror has stopped working. Clicking on the icon results in a busy icon for maybe 30 seconds and then nothing. Running konqueror from a shell, results in nothing, except a message "Alarm clock" and then the prompt returns. I assume that is a time out. Any suggestions? Bill Hogsett
On Thursday 20 February 2003 06:00 am, Bill Hogsett wrote:
After installing 3.1, Konqueror has stopped working.
Clicking on the icon results in a busy icon for maybe 30 seconds and then nothing.
Running konqueror from a shell, results in nothing, except a message "Alarm clock" and then the prompt returns. I assume that is a time out.
Any suggestions?
Bill Hogsett
------------------------------- Bill, This is one I haven't seen yet when updating to 3.1. The first thing I might suggest you doing is removing the mcop folders/files in /tmp and any folders that relate to the user there as well, such as kde-bill. That has eliminated many of the Konq problems for most. All will be recreated as needed, so don't worry about removing them. Patrick --- KMail v1.5 --- SuSE Linux Pro v8.1 --- Registered Linux User #225206 On any other day, that might seem strange...
try a SuSEconfig from a root shell. It should work. bye At 15.00 20/02/2003, PL O'Smith wrote:
On Thursday 20 February 2003 06:00 am, Bill Hogsett wrote:
After installing 3.1, Konqueror has stopped working.
Clicking on the icon results in a busy icon for maybe 30 seconds and then nothing.
Running konqueror from a shell, results in nothing, except a message "Alarm clock" and then the prompt returns. I assume that is a time out.
Any suggestions?
Bill Hogsett
------------------------------- Bill, This is one I haven't seen yet when updating to 3.1. The first thing I might suggest you doing is removing the mcop folders/files in /tmp and any folders that relate to the user there as well, such as kde-bill. That has eliminated many of the Konq problems for most. All will be recreated as needed, so don't worry about removing them.
Patrick
--- KMail v1.5 --- SuSE Linux Pro v8.1 --- Registered Linux User #225206 On any other day, that might seem strange...
-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e
Hi Bill, I experienced the exact same problem after having installed the SuSE 8.1 packages via YaST. The problem turns out to be that the old package containing the 3.0.x version of konqueror is still installed. Apparently the packaging has changed between the two versions and some of the 3.0.x packages have no direct 3.1 equivalents. Thus they are not updated. The solution for me was to; - use yast to find and uninstall all remainng KDE 3.0.x packages. As I remember you'll find one or two of them still lying around, specifically - kdebase3-devel-doc - kdebase3-konqueror - kdeutils3-printing - kde3addons-internet Use teh search facility in YaST to find them (search term: kde). - re-install (update) the new packages replacing these; I'm now sure which ones exactly, but I seem to have gotten away with re-installing just - kdebase3 (this is where konqueror now lives) Hope this helps; Kind regards Jacob On Thursday 20 February 2003 12:00, Bill Hogsett wrote:
After installing 3.1, Konqueror has stopped working.
Clicking on the icon results in a busy icon for maybe 30 seconds and then nothing.
Running konqueror from a shell, results in nothing, except a message "Alarm clock" and then the prompt returns. I assume that is a time out.
Any suggestions?
Bill Hogsett
-- Jacob Lauemøller HiQ WISE - Klampenborgvej 221, 3. - 2800 Kgs. Lyngby - Denmark Phone: +45 2613 3806
participants (4)
-
Bill Hogsett -
Jacob Lauemøller (HiQ WISE) -
Luca Botti -
PL O'Smith