Summary: | Konqueror startup crash in filemanager mode | ||
---|---|---|---|
Product: | [Applications] konqueror | Reporter: | Andreas Korinek <andreas.korinek> |
Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | jakehawkes2001 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Another eample and a work around. |
Description
Andreas Korinek
2003-01-30 17:35:25 UTC
Created attachment 902 [details]
Another eample and a work around.
I get the same problem with konqueror 3.1 compiled from scratch on a Slackware
8.1 system.
The problem seems to be with kfmclient opening the filemanager profile. The
particular line that causes problems is
View2_ServiceName=konq_iconview
A work around for my case is:
Start konqueror from the command line.
Load the File Management profile.
Change the View to Info or something like it.
Save the profile as File Management.
Konqueror should now start from the Home icon OK.
If it doesn't make sure that you don't have any directory properties saved in a
.directory file.
When starting Konq from command line OK, but get lots of output on the console:\ sh-2.05a$ konqueror & [2] 12798 sh-2.05a$ mcop warning: user defined signal handler found for SIG_PIPE, overriding mcop warning: user defined signal handler found for SIG_PIPE, overriding ASSERT: "info.isValid()" in konq_infolistviewitem.cc (123) ASSERT: "info.isValid()" in konq_infolistviewitem.cc (123) mcop warning: user defined signal handler found for SIG_PIPE, overriding kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *parent, const char *name, KInstance *instance ) konqueror: WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) \x08 Major opcode: * kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *parent, const char *name, KInstance *instance ) QObject::connect: No such slot KSB_MediaWidget::showMenu() QObject::connect: (sender name: 'Menu') QObject::connect: (receiver name: 'KSB_MediaWidget_skel') following directions for work around above (re-saving file management profile) does not prevent konq from crashing if started in web browse mode and switch to file management mode. This is my stacktrace: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 11668)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x449aafc9 in wait4 () from /lib/libc.so.6 #0 0x449aafc9 in wait4 () from /lib/libc.so.6 #1 0x44a26138 in __DTOR_END__ () from /lib/libc.so.6 #2 0x44864392 in waitpid () from /lib/libpthread.so.0 #3 0x4401cace in KCrash::defaultCrashHandler () from /usr/kde/3.1/lib/libkdecore.so.4 #4 0x448620c4 in pthread_sighandler () from /lib/libpthread.so.0 #5 <signal handler called> #6 0x00006b66 in ?? () #7 0x456ceb25 in _init () from /usr/lib/libvorbisenc.so.0 #8 0x43a63ce7 in call_init () from /lib/ld-linux.so.2 #9 0x43a63e3e in _dl_init () from /lib/ld-linux.so.2 #10 0x44a046c1 in dl_open_worker () from /lib/libc.so.6 #11 0x43a63af0 in _dl_catch_error () from /lib/ld-linux.so.2 #12 0x44a047bf in _dl_open () from /lib/libc.so.6 #13 0x440e32e7 in dlopen_doit () from /lib/libdl.so.2 #14 0x43a63af0 in _dl_catch_error () from /lib/ld-linux.so.2 #15 0x440e3730 in _dlerror_run () from /lib/libdl.so.2 #16 0x440e3326 in dlopen@@GLIBC_2.1 () from /lib/libdl.so.2 #17 0x44089154 in sys_dl_open () from /usr/kde/3.1/lib/libkdecore.so.4 #18 0x44086826 in tryall_dlopen () from /usr/kde/3.1/lib/libkdecore.so.4 #19 0x44086c5d in find_module () from /usr/kde/3.1/lib/libkdecore.so.4 #20 0x44087995 in lt_dlopen () from /usr/kde/3.1/lib/libkdecore.so.4 #21 0x44030017 in KLibLoader::library () from /usr/kde/3.1/lib/libkdecore.so.4 #22 0x44031631 in KLibLoader::factory () from /usr/kde/3.1/lib/libkdecore.so.4 #23 0x44c3cc11 in KonqIconViewWidget::startImagePreview () from /usr/kde/3.1/lib/libkonq.so.4 #24 0x453f4c9e in KMimeTypeResolver<KFileIVI, KonqKfmIconView>::slotProcessMimeIcons () from /usr/kde/3.1/lib/kde3/konq_iconview.so #25 0x43bfbcee in KMimeTypeResolverHelper::qt_invoke () from /usr/kde/3.1/lib/libkio.so.4 #26 0x44342364 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 #27 0x4434229f in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3 #28 0x445c9670 in QTimer::timeout () from /usr/qt/3/lib/libqt-mt.so.3 #29 0x4435d872 in QTimer::event () from /usr/qt/3/lib/libqt-mt.so.3 #30 0x442edb73 in QApplication::internalNotify () from /usr/qt/3/lib/libqt-mt.so.3 #31 0x442ed977 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3 #32 0x43fa65ff in KApplication::notify () from /usr/kde/3.1/lib/libkdecore.so.4 #33 0x442d0095 in QEventLoop::activateTimers () from /usr/qt/3/lib/libqt-mt.so.3 #34 0x442b1cf4 in QEventLoop::processEvents () from /usr/qt/3/lib/libqt-mt.so.3 #35 0x442ffb33 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3 #36 0x442ffa82 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3 #37 0x442edcf5 in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3 #38 0x44caabfe in main () from /usr/kde/3.1/lib/konqueror.so #39 0x0804d467 in strcpy () #40 0x0804e2d8 in strcpy () #41 0x0804e7f5 in strcpy () #42 0x0804f62f in strcpy () #43 0x4492066d in __libc_start_main () from /lib/libc.so.6 Jake: That bt indicates that you have an incorrect/broken version of libvorbisenc. Please read this, and see whether it helps: http://bugs.kde.org/show_bug.cgi?id=53511#c5 |