Bug 122894 - Crashed when it is opened with a sign 11
Summary: Crashed when it is opened with a sign 11
Status: RESOLVED UNMAINTAINED
Alias: None
Product: knode
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-01 11:20 UTC by Esteban García
Modified: 2018-09-04 18:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Esteban García 2006-03-01 11:20:31 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc version 4.0.3 20060212 
OS:                Linux

When I try to open knode it simply crahs with a sigsev 11 and show me a bug screen with this log information:

(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)
(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)
(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)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1240348448 (LWP 14553)]
(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)
(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)
[KCrash handler]
#3  0xb71392af in QMenuData::findItem () from /usr/lib/libqt-mt.so.3
#4  0xb7139a77 in QMenuData::setItemChecked () from /usr/lib/libqt-mt.so.3
#5  0xb7e69d69 in KNCollectionView::updatePopup ()
   from /usr/lib/libknodecommon.so
#6  0xb7f1335e in KNCollectionView::readConfig ()
   from /usr/lib/libknodecommon.so
#7  0xb7f13732 in KNCollectionView::KNCollectionView ()
   from /usr/lib/libknodecommon.so
#8  0xb7f144aa in KNMainWidget::KNMainWidget ()
   from /usr/lib/libknodecommon.so
#9  0x0804ee5e in ?? ()
#10 0x0810a370 in ?? ()
#11 0x0805e830 in ?? ()
#12 0x00000001 in ?? ()
#13 0x0805e770 in ?? ()
#14 0x00000000 in ?? ()
Comment 1 Michael Leupold 2009-03-28 10:56:28 UTC
Unfortunately this backtrace doesn't contain any useful information. If you're still able to reproduce this bug (which I somehow doubt regarding this report is already some years old), please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports on how to get more information.
Comment 2 Nicolas L. 2010-08-19 10:35:11 UTC
do you still reproduce this bug ? if yes can you provide the needed backtrace ?


thank you a lot
Comment 3 Esteban García 2010-08-19 12:47:42 UTC
Sorry , but Im afraid I cannot  reproduce it now due to changes in my 
machine.

         Thanks,
            Esteban.

El 19/08/2010 10:35, Nicolas Lécureuil  escribió:
> https://bugs.kde.org/show_bug.cgi?id=122894
>
>
> Nicolas Lécureuil<nlecureuil@mandriva.com>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |nlecureuil@mandriva.com
>
>
>
>
> --- Comment #2 from Nicolas Lécureuil<nlecureuil mandriva com>   2010-08-19 10:35:11 ---
> do you still reproduce this bug ? if yes can you provide the needed backtrace ?
>
>
> thank you a lot
>
>
Comment 4 Andrew Crouthamel 2018-09-04 18:38:18 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.