Bug 175146 - Mime type association crash when i add one via properties
Summary: Mime type association crash when i add one via properties
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_filetypes (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
: 176083 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-11-14 18:58 UTC by laurent Protois
Modified: 2009-02-20 15:09 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description laurent Protois 2008-11-14 18:58:13 UTC
Version:           konqueror 4.1.2 (kde 4.1.2) (using KDE 4.1.2)
Compiler:          gcc version 4.3.2 (GCC) 
OS:                Linux
Installed from:    Mandriva RPMs

Application : Type KEditFile (keditfiletype), signal SIGABRT
(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 0x7f3281563700 (LWP 5541)]
[New Thread 0x41ce0950 (LWP 5542)]
(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)
[KCrash handler]
#5  0x00007f327e7d2975 in raise () from /lib64/libc.so.6
#6  0x00007f327e7d41a3 in abort () from /lib64/libc.so.6
#7  0x00007f32805befb5 in qt_message_output () from /usr/lib64/libQtCore.so.4
#8  0x00007f32805bf0fd in qFatal () from /usr/lib64/libQtCore.so.4
#9  0x000000000041203c in _start ()
Comment 1 Zayed Al-Saidi 2008-11-17 08:31:11 UTC
I think this not related to konqueror. It belongs to filetypes module in the system settings.

Here is the backtrace:

Application: كونكيورر (konqueror), signal SIGSEGV
(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 0xb60cc6c0 (LWP 10670)]
[KCrash handler]
#6  0xb74163d7 in QString::operator== (this=0x8a84adc, other=@0xbfaae784)
    at ../../include/QtCore/../../src/corelib/tools/qstring.h:106
#7  0xb3a80ba1 in ?? () from /usr/lib/kde4/lib/kde4/kcm_filetypes.so
#8  0xb3a80c6e in ?? () from /usr/lib/kde4/lib/kde4/kcm_filetypes.so
#9  0xb74d5f79 in QMetaObject::activate (sender=0x8844870, 
    from_signal_index=29, to_signal_index=30, argv=0xbfaae8cc)
    at kernel/qobject.cpp:3016
#10 0xb74d63b0 in QMetaObject::activate (sender=0x8844870, m=0xb718ce24, 
    from_local_signal_index=2, to_local_signal_index=3, argv=0xbfaae8cc)
    at kernel/qobject.cpp:3106
#11 0xb6f891c1 in QAbstractButton::clicked (this=0x8844870, _t1=false)
    at .moc/release-shared/moc_qabstractbutton.cpp:185
#12 0xb6ce7919 in QAbstractButtonPrivate::emitClicked (this=0x8847fb8)
    at widgets/qabstractbutton.cpp:544
#13 0xb6ce8de0 in QAbstractButtonPrivate::click (this=0x8847fb8)
    at widgets/qabstractbutton.cpp:537
#14 0xb6ce903b in QAbstractButton::mouseReleaseEvent (this=0x8844870, 
    e=0xbfaaeeac) at widgets/qabstractbutton.cpp:1116
#15 0xb69fad44 in QWidget::event (this=0x8844870, event=0xbfaaeeac)
    at kernel/qwidget.cpp:7021
#16 0xb6ce7b3f in QAbstractButton::event (this=0x8844870, e=0xbfaaeeac)
    at widgets/qabstractbutton.cpp:1078
#17 0xb6d8cf22 in QPushButton::event (this=0x8844870, e=0xbfaaeeac)
    at widgets/qpushbutton.cpp:658
#18 0xb69a2f9c in QApplicationPrivate::notify_helper (this=0x805c870, 
    receiver=0x8844870, e=0xbfaaeeac) at kernel/qapplication.cpp:3800
#19 0xb69a8125 in QApplication::notify (this=0xbfaaf84c, receiver=0x8844870, 
    e=0xbfaaeeac) at kernel/qapplication.cpp:3527
#20 0xb793f483 in KApplication::notify (this=0xbfaaf84c, receiver=0x8844870, 
    event=0xbfaaeeac)
    at /build/buildd/kde4libs-4.1.2/kdeui/kernel/kapplication.cpp:311
#21 0xb74c10b9 in QCoreApplication::notifyInternal (this=0xbfaaf84c, 
    receiver=0x8844870, event=0xbfaaeeac) at kernel/qcoreapplication.cpp:591
#22 0xb69a5661 in QApplicationPrivate::sendMouseEvent (receiver=0x8844870, 
    event=0xbfaaeeac, alienWidget=0x8844870, nativeWidget=0x85028f8, 
    buttonDown=0xb7198a10, lastMouseReceiver=@0xb7198a14)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#23 0xb6a0f52d in QETWidget::translateMouseEvent (this=0x85028f8, 
    event=0xbfaaf3c8) at kernel/qapplication_x11.cpp:4048
#24 0xb6a0dee1 in QApplication::x11ProcessEvent (this=0xbfaaf84c, 
    event=0xbfaaf3c8) at kernel/qapplication_x11.cpp:3166
#25 0xb6a36c2a in x11EventSourceDispatch (s=0x805fb88, callback=0, 
    user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#26 0xb6423cc6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb6427083 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0xb642763e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb74ec9f8 in QEventDispatcherGlib::processEvents (this=0x805c928, 
    flags=@0xbfaaf568) at kernel/qeventdispatcher_glib.cpp:325
#30 0xb6a36a25 in QGuiEventDispatcherGlib::processEvents (this=0x805c928, 
    flags=@0xbfaaf598) at kernel/qguieventdispatcher_glib.cpp:204
#31 0xb74c033d in QEventLoop::processEvents (this=0xbfaaf610, 
    flags=@0xbfaaf5d4) at kernel/qeventloop.cpp:149
#32 0xb74c04cd in QEventLoop::exec (this=0xbfaaf610, flags=@0xbfaaf618)
    at kernel/qeventloop.cpp:200
#33 0xb74c274d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:849
#34 0xb69a2897 in QApplication::exec () at kernel/qapplication.cpp:3330
#35 0xb7f7fabd in kdemain () from /usr/lib/kde4/lib/libkdeinit4_konqueror.so
#36 0x08048582 in _start ()
#0  0xb7f99410 in __kernel_vsyscall ()
Comment 2 FiNeX 2008-11-19 20:25:59 UTC
Changed severity to "crash". I hope to have selected only the right bugs (>100) :-)
Comment 3 Dario Andres 2008-12-04 22:19:59 UTC
*** Bug 176083 has been marked as a duplicate of this bug. ***
Comment 4 David Faure 2009-02-20 01:44:41 UTC
Does this still happen in KDE 4.2?
Comment 5 Luca Zorzi 2009-02-20 14:41:14 UTC
My bug was marked as a duplicate of this one, and mine now is resolved with KDE 4.3
Comment 6 David Faure 2009-02-20 14:58:27 UTC
KDE 4.3 doesn't exist yet, so I guess you mean either 4.2 or trunk, but ok :)
Comment 7 Luca Zorzi 2009-02-20 15:09:57 UTC
Yes, sorry, i meant 4.2. :)