(*** This bug was imported into bugs.kde.org ***) Package: konqueror Version: KDE 2.1.1 Severity: normal Installed from: SuSE RPMs Compiler: download rpms OS: Linux OS/Compiler notes: Suse PPC 7.0 Kde 211/ with or without kdelibs2.1.2 is brain-dead. Konqueror does not recognise any protocolfile http etc. If I launch konqueror from the command line (under wmaker) I get DCOPServer up and running. kded: Does not exist! (/home/tony/.kde2/share/servicetypes/) kded: Does not exist! (/home/tony/.kde2/share/mimelnk/) kded: Does not exist! (/home/tony/.kde2/share/applnk/) kded: Does not exist! (/home/tony/.kde2/share/services/) kio (KLauncher): KLauncher: Got kdeinit_exec_wait('kbuildsycoca' ...) kio (KLauncher): kbuildsycoca (pid 1473) up and running. kio (KSycoca): WARNING: Found version 31 expecting version 32 or higher. Error can't open database! kio (KSycoca): WARNING: Found version 31 expecting version 32 or higher. kio (KSycoca): WARNING: Outdated database found kio (KTrader): KServiceTypeProfile::offers( Browser/View ) kio (KSycoca): WARNING: Found version 31 expecting version 32 or higher. kio (KSycoca): WARNING: Outdated database found kio (KMimeType): WARNING: KServiceType::offers : servicetype all/all not found kio (KMimeType): WARNING: KServiceType::offers : servicetype all/allfiles not found kio (KMimeType): WARNING: KServiceType::offers : servicetype Browser/View not found kio (KTrader): No profile using KServiceType::offers result: 0 offers libkonq: KNewMenu::KNewMenu 0x18607e0 libkonq: KBookmarkMenu::KBookmarkMenu 0x1877400 address : libkonq: KBookmarkManager::parse /home/tony/.kde2/share/apps/konqueror/bookmarks.xml konqueror: KonqMainWindow::enableAllActions false libkonq: ## loaded: 0 entries. kparts: MainWindow::createGUI for 0L konqueror: KonqMainWindow::openURL : url = 'file:/home/tony' serviceType='' view=(nil) kio (KSycoca): WARNING: Found version 31 expecting version 32 or higher. kio (KSycoca): WARNING: Outdated database found konqueror: main() -> no args konqueror: KonqViewManager::clear konqueror: KonqViewManager::setActivePart (nil) kparts: 0x185ebf8 emitting activePartChanged (nil) konqueror: slotPartActivated (nil) konqueror: New current view (nil) konqueror: No part activated - returning kparts: MainWindow::createGUI for 0L libkonq: KNewMenu::~KNewMenu 0x18607e0 tony@moore:~ > klauncher: KLauncher::process ---> terminateKDE kdeinit: Fatal IO error: client killed kdeinit: Fatal IO error: client killed (Submitted via bugs.kde.org)
On Wednesday 02 May 2001 01:48 augustmiles@yahoo.com wrote: > Package: konqueror > Version: KDE 2.1.1 > Severity: normal > Installed from: SuSE RPMs > Compiler: download rpms > OS: Linux > OS/Compiler notes: Suse PPC 7.0 > > Kde 211/ with or without kdelibs2.1.2 is brain-dead. Can you run kbuildsycoca? Does it update the file ~/.kde/tmp-$HOSTNAME/ksycoca? It does have write access to that file does it? Cheers Waldo -- bastian@kde.org | SuSE Labs KDE Developer | bastian@suse.com
well I don't even have a .kde directory! when I lauch kbuildsycoca I get Warning: kbuildsycoca is unable to register with DCOP Error can't open database I checked that I own everything by doing a "chown -R" on my home directory without any luck __________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
On Thursday 03 May 2001 00:32 august miles wrote: > well I don't even have a .kde directory! > > when I lauch kbuildsycoca I get > > > Warning: kbuildsycoca is unable to register with DCOP > Error can't open database > > > I checked that I own everything by doing a > "chown -R" on my home directory without any luck Can you run "strace kbuildsycoca" and send me the output in private mail? Cheers Waldo -- bastian@kde.org | SuSE Labs KDE Developer | bastian@suse.com
Thank you for your bug report. The bug that you reported appears to be a packaging bug due to a problem in the way in which your distribution/vendor has packaged KDE for distribution. The bug report will be closed since it is not a KDE problem. Please send the bug report to your distribution/vendor instead.
*** Bug 435111 has been marked as a duplicate of this bug. ***