Re: [kde] konqueror crash



I can't provide a technical answer, but I have occasionally had increased
crashes when I upgrade from one version of kde to the next without updating
~/.kde. The solution has been to rename the original folder and allow kde to
make a new config folder at startup. You can then copy mail and book mark
files to the new folder.
Paul
On Wednesday 23 May 2007 1:15:49 am pol wrote:
Hi all,

After a couple years working perfectly, kde session restoring begun to
fail a few weeks ago, on my debian/testing laptop.
At the user session opening, every konqueror instance, saved in the
previous session, crashes. Here included the backtrace, from the crash
window panel. lHowever, any new konqueror instaces start flawlessly.
Any idea?

thank you for your help
--
Pol


---- enc.
(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1232545568 (LWP 10458)]
[KCrash handler]
#5 0x00000000 in ?? ()
#6 0xb5b6d940 in KonqKfmIconView::doOpenURL ()
from /usr/lib/kde3/konq_iconview.so
#7 0xb65d6a0c in KonqDirPart::openURL () from /usr/lib/libkonq.so.4
#8 0xb66a9960 in KonqView::openURL () from
/usr/lib/libkdeinit_konqueror.so #9 0xb66b537c in KonqMainWindow::openView
()
from /usr/lib/libkdeinit_konqueror.so
#10 0xb66c0879 in KonqViewManager::loadItem ()
from /usr/lib/libkdeinit_konqueror.so
#11 0xb66c0ec0 in KonqViewManager::loadItem ()
from /usr/lib/libkdeinit_konqueror.so
#12 0xb66c0491 in KonqViewManager::loadItem ()
from /usr/lib/libkdeinit_konqueror.so
#13 0xb66c2f67 in KonqViewManager::loadViewProfile ()
from /usr/lib/libkdeinit_konqueror.so
#14 0xb66c3dcb in KonqMainWindow::readProperties ()
from /usr/lib/libkdeinit_konqueror.so
#15 0xb6d54ca2 in KMainWindow::readPropertiesInternal ()
from /usr/lib/libkdeui.so.4
#16 0xb6d54e22 in KMainWindow::restore () from /usr/lib/libkdeui.so.4
#17 0xb66caf41 in kdemain () from /usr/lib/libkdeinit_konqueror.so
#18 0xb7f38524 in kdeinitmain () from /usr/lib/kde3/konqueror.so
#19 0x0804e457 in ?? ()
#20 0x00000003 in ?? ()
#21 0x0807bda8 in ?? ()
#22 0x00000001 in ?? ()
#23 0x00000000 in ?? ()
----


___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.


___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.



Relevant Pages

  • Re: [kde-linux] Upgrading Linux breaks KDE 3.5
    ... I use KDE 4.2.2 on my work system, ... my distro does support KDE-4.2.x. ... can't uses something that crashes the whole X session. ...
    (KDE)
  • Re: New Member
    ... I'm a new member here and I'd like to ask about my Fedora Core's 4 Problem. ... I run GNOME (mostly, unless the mood for KDE strikes my fancy, temporarily.) ... I'm using development but the packages should be the same, ... The no debugging symbols found indicate that you need the package-debug rpm for the failing program. ...
    (Fedora)
  • KDE 4.1 debug
    ... I am currently working on trying to capture some crash logs from a kde ... with loads of "no debugging symbols found". ... Debug Build of the Python Interpreter (versi ... Quiet often I get no crash log at all, other times I get a mix of no ...
    (Ubuntu)
  • kernel upgrade broke kde
    ... I discovered that KDE was broken. ... Here is a traceback from one of the crashes: ... (no debugging symbols found) ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
    (Debian-User)
  • Re: "hwcap 0 nosegneg" doesnt work with paravirt_ops xen as of 2.6.23.9
    ... It shouldn't ever lead to segfaults. ... (no debugging symbols found) ... This was before running an ldconfig. ... you shouldn't be seeing crashes either way. ...
    (Linux-Kernel)