Bug 255705 - kate crashes when it starts
Summary: kate crashes when it starts
Status: RESOLVED DUPLICATE of bug 265540
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
Depends on:
Reported: 2010-10-30 23:46 UTC by Joost Ringoot
Modified: 2011-08-11 08:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

New crash information added by DrKonqi (2.39 KB, text/plain)
2010-10-30 23:49 UTC, Joost Ringoot

Note You need to log in before you can comment on or make changes to this bug.
Description Joost Ringoot 2010-10-30 23:46:01 UTC
Application: kate (3.5.1)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-23-generic i686
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed: trying to start kate. I thought it was going to detect this as a duplicate bug. Thanks for any assistance

The crash can be reproduced every time.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
[Current thread is 1 (Thread 0xb781b930 (LWP 6083))]

Thread 2 (Thread 0xb7597b70 (LWP 6084)):
#0  0x002af7d4 in __pthread_mutex_unlock_usercnt (mutex=0x9d28004, decr=<value optimized out>) at pthread_mutex_unlock.c:52
#1  0x00c63fb6 in pthread_mutex_unlock (mutex=0x9d28004) at forward.c:184
#2  0x00a2c428 in ?? () from /lib/libglib-2.0.so.0
#3  0x00a2cba7 in g_main_loop_run () from /lib/libglib-2.0.so.0
#4  0x023d96b4 in ?? () from /usr/lib/libgio-2.0.so.0
#5  0x00a5348f in ?? () from /lib/libglib-2.0.so.0
#6  0x002abcc9 in start_thread (arg=0xb7597b70) at pthread_create.c:304
#7  0x00c566ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb781b930 (LWP 6083)):
[KCrash Handler]
#7  QString::operator= (this=0x15, other=...) at tools/qstring.cpp:1324
#8  0x028b07f9 in KateHighlighting::KateHighlighting (this=0x9ed47e8, def=0x0) at ../../kate/syntax/katehighlight.cpp:86
#9  0x028991ea in KateHlManager::KateHlManager (this=0x9e7a8a8) at ../../kate/syntax/katesyntaxmanager.cpp:89
#10 0x02981776 in KateGlobal::KateGlobal (this=0x9e78c10) at ../../kate/utils/kateglobal.cpp:135
#11 0x02981bf4 in KateGlobal::self () at ../../kate/utils/kateglobal.cpp:441
#12 0x02e7ff97 in KateFactory::editor (this=0x9e72348) at ../../kate/utils/katefactory.cpp:53
#13 0x0534b06d in KTextEditor::editor (libname=0x9e717c0 "katepart") at ../../../interfaces/ktexteditor/ktexteditor.cpp:179
#14 0x05353de0 in KTextEditor::EditorChooser::editor (postfix=..., fallBackToKatePart=true) at ../../../interfaces/ktexteditor/editorchooser.cpp:135
#15 0x008da261 in KateDocManager::KateDocManager (this=0x9e38988, parent=0xbfa8f8fc) at ../../../kate/app/katedocmanager.cpp:64
#16 0x008cf857 in KateApp::KateApp (this=0xbfa8f8fc, args=0x9cebf30) at ../../../kate/app/kateapp.cpp:60
#17 0x003143af in kdemain (argc=1, argv=0xbfa8ffa4) at ../../../kate/app/katemain.cpp:373
#18 0x0804859b in main (argc=1, argv=0xbfa8ffa4) at kate_dummy.cpp:3

Reported using DrKonqi
Comment 1 Joost Ringoot 2010-10-30 23:49:01 UTC
Created attachment 53004 [details]
New crash information added by DrKonqi

kate (3.5.1) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashed: Starting kate, I am pretty sure it has to do with qt4 and the "bad" uninstall of beid

-- Backtrace (Reduced):
#7  QString::operator= (this=0x15, other=...) at tools/qstring.cpp:1324
#8  0x02c1f7f9 in KateHighlighting::KateHighlighting (this=0x9719380, def=0x0) at ../../kate/syntax/katehighlight.cpp:86
#9  0x02c081ea in KateHlManager::KateHlManager (this=0x96bef40) at ../../kate/syntax/katesyntaxmanager.cpp:89
#10 0x02cf0776 in KateGlobal::KateGlobal (this=0x96bb5c8) at ../../kate/utils/kateglobal.cpp:135
#11 0x02cf0bf4 in KateGlobal::self () at ../../kate/utils/kateglobal.cpp:441
Comment 2 Joost Ringoot 2010-10-31 00:03:45 UTC
after reinstall of QT4 and kate, it appears fixed
Comment 3 Dominik Haumann 2011-08-11 08:29:11 UTC

*** This bug has been marked as a duplicate of bug 265540 ***