Bug 214002 - Kate -> Preferences caused Kate to crash with signal 6 (SIGABRT) error"
Summary: Kate -> Preferences caused Kate to crash with signal 6 (SIGABRT) error"
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Fink Packages Other
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-11-10 16:39 UTC by Steve Mauget
Modified: 2018-10-21 04:57 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Mauget 2009-11-10 16:39:56 UTC
Version:           4.2.4-1 (using KDE 4.2.4)
Compiler:          gcc-4.0  
OS:                OS X
Installed from:    Mac OS X (Fink) Packages

After fink install kate4-mac completed successfully, I started kate.app by dbl clicking on the executable in /sw/opt/kde4/mac/bin. After the app seemed to open OK I went to Kate -> Preferences and the app crashed with the following error message: "kate crashed and caused the signal 6 (SIGABRT)"

Backtrace details are as follows, but this is not the complete backtrace , which apparently stalled:

Attaching to process 85990.
Reading symbols for shared libraries . done
Reading symbols for shared libraries ................................................................................................................................................... done
0x93a4a851 in __wait4 ()
[Current thread is 1 (process 85990 thread 0x20b)]

Thread 2 (process 85990 thread 0x2703):
#0  0x93a06e03 in __error ()
#1  0x93a06d8f in cthread_set_errno_self ()
#2  0x93a06ac3 in cerror ()
#3  0x93a37155 in _pthread_start ()
#4  0x93a37012 in thread_start ()

Thread 1 (process 85990 thread 0x20b):
#0  0x93a4a851 in __wait4 ()
#1  0x93a4a847 in waitpid$UNIX2003 ()
#2  0x022a6854 in KCrash::startDirectly ()
#3  0x022a76e4 in KCrash::defaultCrashHandler ()
#4  <signal handler called>
#5  0x93a73e42 in __kill ()
#6  0x93a73e34 in kill$UNIX2003 ()
#7  0x93ae623a in raise ()
#8  0x93af2679 in abort ()
#9  0x003d26d5 in qt_message_output ()
#10 0x003d340c in qFatal ()
#11 0x003d3500 in qt_assert ()
#12 0x01478364 in KMimeTypeTrader::query ()
#13 0x00709949 in KTextEditor::EditorChooser::EditorChooser ()
#14 0x000e615d in KateConfigDialog::KateConfigDialog ()
#15 0x000f71fe in KateMainWindow::slotConfigure ()
#16 0x000fcb57 in KateMainWindow::qt_metacall ()
#17 0x004da148 in QMetaObject::activate ()
#18 0x00a3dc8c in QAction::triggered ()
#19 0x00a3e71c in QAction::activate ()
#20 0x00a1d439 in qt_mac_activate_action ()
#21 0x00a1da53 in qt_mac_menu_event ()
#22 0x963ab11d in DispatchEventToHandlers ()
#23 0x963aa55b in SendEventToEventTargetInternal ()
#24 0x963c6eac in SendEventToEventTarget ()
#25 0x963fb1c7 in SendHICommandEvent ()
#26 0x96421939 in SendMenuCommandWithContextAndModifiers ()
#27 0x964218f4 in SendMenuItemSelectedEvent ()
#28 0x9642180a in FinishMenuSelection ()
#29 0x963fe474 in MenuSelectCore ()
#30 0x9648d030 in MenuSelect ()
#31 0x009dfffd in QApplicationPrivate::globalEventProcessor ()
#32 0x963ab11d in DispatchEventToHandlers ()
#33 0x963aa55b in SendEventToEventTargetInternal ()
#34 0x963c6eac in SendEventToEventTarget ()
#35 0x963d95e3 in ToolboxEventDispatcherHandler ()
#36 0x963ab4d6 in DispatchEventToHandlers ()
#37 0x963aa55b in SendEventToEventTargetInternal ()
#38 0x963c6eac in SendEventToEventTarget ()
#39 0x009ef384 in QEventDispatcherMac::processEvents ()
#40 0x004c4131 in QEventLoop::processEvents ()
#41 0x004c446a in QEventLoop::exec ()
#42 0x004c6316 in QCoreApplication::exec ()
#43 0x0001e7ac in kdemain ()
#44 0x00008fa6 in start ()


Also, attempting to open a file results an error message:
"Could not find mime type application/octet-stream
Comment 1 Steve Mauget 2009-11-10 16:41:36 UTC
I should say the fink install process appeared to be successful.
Comment 2 Christoph Cullmann 2010-02-16 12:59:58 UTC
If at all, this looks like some generic kdelibs problem, therefor assign to kdelibs, but guess without backtrace with debugging symbols, can't be looked at.
Comment 3 Andrew Crouthamel 2018-09-20 21:58:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 04:57:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!