[kdenlive] [Bug 478626] Wrong thumbnail picture in project content list when copying title tracks
https://bugs.kde.org/show_bug.cgi?id=478626 --- Comment #1 from Thomas Murach --- Apologies, I hit "enter" to upload attachment, but then the report was submitted already :-/ STEPS TO REPRODUCE 1. Create a title track with just a little text in the bottom left corner, see attachment picture, track 1. Thumbnail picture seems correct. 2. Copy that title track, rename it, add text in the top left corner, see thumbnail picture, track 2. Thumbnail picture seems correct. 3. Copy track _1_ once more, rename it, do _not_ add text in the top left corner; see track 3. The thumbnail should resemble the thumbnail of track 1, not the thumbnail of track 2. OBSERVED RESULT Thumbnail of track 3 resembles thumbnail of track 2. EXPECTED RESULT Thumbnail should resemble thumbnail of track 1. SOFTWARE/OS VERSIONS Windows: macOS: Linux: OpenSuSE Leap 15.5, Kernel 5.14.21 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 478626] New: Wrong thumbnail picture in project content list when copying title tracks
https://bugs.kde.org/show_bug.cgi?id=478626 Bug ID: 478626 Summary: Wrong thumbnail picture in project content list when copying title tracks Classification: Applications Product: kdenlive Version: 22.12.3 Platform: openSUSE OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: asiasuppenes...@gmx.de Target Milestone: --- Created attachment 164237 --> https://bugs.kde.org/attachment.cgi?id=164237&action=edit Problem with preview of clip 3 SUMMARY In my workflow I copy title tracks often, rename the copies and change contents slightly. In the project content list (German: Projektinhalt) view the thumbnail picture of these copies is sometimes wrong, as described below. To me this issue is reproducible and has been there for a long time. Last but not least: Thanks so much for providing and maintaining this fantastic piece of software!!! It is truly amazing. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 475506] New: Screen locking failed because of too many open files, but rest of system works fine
https://bugs.kde.org/show_bug.cgi?id=475506 Bug ID: 475506 Summary: Screen locking failed because of too many open files, but rest of system works fine Classification: Plasma Product: kscreenlocker Version: 5.27.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: asiasuppenes...@gmx.de Target Milestone: --- SUMMARY *** Due to a problem with an unrelated software component (KMozillaHelper, see https://www.opensuse-forum.de/thread/66654-maximum-number-of-clients-reached-kmozillahelper/ (German, unfortunately)) I recently had many processes running and files open even right after booting my system. This did not cause any noticeable problems. I could start my IDE for software development, browse the web, etc. As far as I can tell the only issue I had is that I could not lock my screen, either via keyboard shortcut or by clicking the lock icon in the task bar. The error message in the logs was this: 2023-10-09T13:14:55.692681+02:00 laptop ksmserver[4361]: QProcessPrivate::createPipe: Cannot create pipe 0x7fbf90004b78 (Too many open files) 2023-10-09T13:14:55.699846+02:00 laptop ksmserver[4361]: kscreenlocker: Greeter Process not available Obviously this issue can be fixed by killing spurious kmozillahelper processes, but I do wonder why starting any other programm/process worked fine, and only the screen locker (a vital component!) could not be started. So please give this issue a thought before telling me to clean up my system ;-). PS executing /usr/lib/kscreenlocker_greet manually did work as expected! *** STEPS TO REPRODUCE 1. Open sufficiently many instances of KMozillaHelper 2. Try to lock the screen OBSERVED RESULT Screen did not lock EXPECTED RESULT Should have been locked SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION My "ulimit" settings: $ ulimit -a core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority(-e) 0 file size(blocks, -f) unlimited pending signals (-i) 127197 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files(-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size(kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 127197 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 464894] New: Non-optimal display of items in week view
https://bugs.kde.org/show_bug.cgi?id=464894 Bug ID: 464894 Summary: Non-optimal display of items in week view Classification: Applications Product: korganizer Version: 5.22.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: agendaview (weekview) Assignee: kdepim-b...@kde.org Reporter: asiasuppenes...@gmx.de Target Milestone: --- Created attachment 155698 --> https://bugs.kde.org/attachment.cgi?id=155698&action=edit The item highlighted by the hand-drawn red arrow is very small and could be displayed much wider SUMMARY When using korganizer's week view, sometimes calendar entries are displayed too small, i.e. smaller than they could be. I believe that maximising the use of the available space in a given column is a generally desirable goal. The attached picture should say it all - the item highlighted by the arrow could actually span three quarters of the column width, but instead only covers one quarter. STEPS TO REPRODUCE 1. Create a set of partially conflicting calendar entries, similar to those in the attached image 2. Observe how korganizer arranges the items OBSERVED RESULT Usually space is wasted and calendar entries are too small for their titles to be visible EXPECTED RESULT Maximise use of available space, yielding a higher fraction of titles to be readable / identifiable SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 461131] New: Korganizer sometimes crashes on startup
https://bugs.kde.org/show_bug.cgi?id=461131
Bug ID: 461131
Summary: Korganizer sometimes crashes on startup
Classification: Applications
Product: korganizer
Version: unspecified
Platform: OpenSUSE
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: asiasuppenes...@gmx.de
Target Milestone: ---
Application: korganizer (5.21.2 (22.08.2))
Qt Version: 5.15.6
Frameworks Version: 5.99.0
Operating System: Linux 6.0.3-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.26.1 [KCrashBackend]
-- Information about the crash:
When booting my desktop machine and starting KDE, sometimes I'm greeted with
DrKonqi telling me that Korganizer has crashed. Zero user interaction has
happened until this point. Simply restarting the app has worked fine in all
cases so far.
The crash can be reproduced sometimes.
-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
[KCrash Handler]
#4 KJob::setError (this=this@entry=0x0, errorCode=errorCode@entry=100) at
/usr/src/debug/kcoreaddons-5.99.0-1.1.x86_64/src/lib/jobs/kjob.cpp:254
#5 0x7f9316bc6734 in Akonadi::SessionPrivate::serverStateChanged
(this=, state=) at
/usr/src/debug/akonadi-22.08.2/src/core/session.cpp:298
#6 0x7f931531305d in QtPrivate::QSlotObjectBase::call (a=0x7ffeed012800,
r=0x557b96de6d60, this=0x557b96dffc70) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#7 doActivate (sender=0x557b96e074b0, signal_index=5,
argv=0x7ffeed012800) at kernel/qobject.cpp:3919
#8 0x7f931530c4df in QMetaObject::activate (sender=,
m=, local_signal_index=local_signal_index@entry=2,
argv=argv@entry=0x7ffeed012800) at kernel/qobject.cpp:3979
#9 0x7f9316bbdb31 in Akonadi::ServerManager::stateChanged (this=, _t1=, _t1@entry=Akonadi::ServerManager::Broken) at
/usr/src/debug/akonadi-22.08.2/build/src/core/KF5AkonadiCore_autogen/include/moc_servermanager.cpp:180
#10 0x7f9316bbdd9c in Akonadi::ServerManagerPrivate::setState
(state=Akonadi::ServerManager::Broken, this=0x7f9316ca7300
<_ZZN12_GLOBAL__N_115Q_QGS_sInstance13innerFunctionEvE6holder.lto_priv.0>) at
/usr/src/debug/akonadi-22.08.2/src/core/servermanager.cpp:73
#11 Akonadi::ServerManagerPrivate::timeout (this=0x7f9316ca7300
<_ZZN12_GLOBAL__N_115Q_QGS_sInstance13innerFunctionEvE6holder.lto_priv.0>) at
/usr/src/debug/akonadi-22.08.2/src/core/servermanager.cpp:93
#12
Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}::operator()()
const (__closure=) at
/usr/src/debug/akonadi-22.08.2/src/core/servermanager.cpp:52
#13 QtPrivate::FunctorCall, QtPrivate::List<>, void,
Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}>::call(Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}&,
void**) (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#14
QtPrivate::Functor::call,
void>(Akonadi::ServerManagerPrivate::ServerManagerPrivate()::{lambda()#1}&,
void*, void**) (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#15
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) (which=, this_=, r=, a=, ret=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#16 0x7f931531305d in QtPrivate::QSlotObjectBase::call (a=0x7ffeed012910,
r=0x557b96e074b0, this=0x557b96de0980) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#17 doActivate (sender=0x7f93080150e0, signal_index=3,
argv=0x7ffeed012910) at kernel/qobject.cpp:3919
#18 0x7f931530c4df in QMetaObject::activate (sender=,
m=m@entry=0x7f93155b39c0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffeed012910)
at kernel/qobject.cpp:3979
#19 0x7f9315316e9a in QTimer::timeout (this=, _t1=...) at
.moc/moc_qtimer.cpp:205
#20 0x7f93153077ed in QObject::event (this=0x7f93080150e0,
e=0x7ffeed012a60) at kernel/qobject.cpp:1369
#21 0x7f9315fa53fe in QApplicationPrivate::notify_helper (this=, receiver=0x7f93080150e0, e=0x7ffeed012a60) at
kernel/qapplication.cpp:3637
#22 0x7f93152dc178 in QCoreApplication::notifyInternal2
(receiver=0x7f93080150e0, event=0x7ffeed012a60) at
kernel/qcoreapplication.cpp:1064
#23 0x7f9315332c01 in QTimerInfoList::activateTimers (this=0x557b96cd08c0)
at kernel/qtimerinfo_unix.cpp:643
#24 0x7f9315333494 in timerSourceDispatch (source=) at
kernel/qeventdispatcher_glib.cpp:183
#25 0x7f9312d20a50 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#26 0x7f9312d20e08 in ?? () from /lib64/libglib-2.0.so.0
#27 0x7f9312d20e9c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#28 0x7f9315333806 in QEventDispatcherGlib::processEvents
(this=0x557b96cd05a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x7f93152dabeb in QEventLoop::exec (t
[kile] [Bug 455843] LivePreview disappears when closing background tab
https://bugs.kde.org/show_bug.cgi?id=455843 Thomas Murach changed: What|Removed |Added CC||asiasuppenes...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 455843] New: LivePreview disappears when closing background tab
https://bugs.kde.org/show_bug.cgi?id=455843 Bug ID: 455843 Summary: LivePreview disappears when closing background tab Product: kile Version: 2.9.93 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: asiasuppenes...@gmx.de Target Milestone: --- SUMMARY When editing the main tex file of a project, the live preview works very well. When keeping the tab of main tex file open / visible in the foreground and closing a background tab of e.g. a .bib file, the live preview disappears. To me this is (not super-annoying but) unexpected behaviour. I have to click into the main area of the editor again to a) restore the live preview and b) be able to continue writing. (Let me know if I should report the latter in a dedicated issue) STEPS TO REPRODUCE 1. Open two tabs: the main .tex file and a .bib file 2. Make sure the tab of the .tex file is visible/active, the .bib file is in the background 3. Click the little cross in the top-right corner of the background tab to close it OBSERVED RESULT The live preview of the main document, which is still visible, disappears. One cannot continue writing without clicking into the text editing area. EXPECTED RESULT Live preview remains visible, no need to click into the text editing area to continue writing. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuse 15.3 KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.76.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION Kile is great, thanks a lot for your efforts! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 341314] Plasma 5 somehow falls back to US keyboard after startup
https://bugs.kde.org/show_bug.cgi?id=341314 Thomas Murach changed: What|Removed |Added CC||asiasuppenes...@gmx.de --- Comment #5 from Thomas Murach --- Hi there, obviously I cannot comment on behalf of the original author, but I think I faced the same issue on my setup. Removing Ibus solved the problem for me. Thanks for the hint! On a side note, here's one workaround I used often. I mention it because at least I was surprised when I discovered it: After login, when the plasma workspace was already visible but all sorts of applications were still starting, I quickly changed to an arbitrary virtual console (Ctrl+Alt+F4 and the like) and back to the graphical session - et voila, my desired keyboard layout was loaded. It even worked when the gnome keyring dialogue was shown, which in my case got the keyboard and mouse focus exclusively. I always thought that the fact that the workaround did work was a sign of a race condition at startup. Don't know if this description is of any value for others... -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 432820] Missing German translation in reminder popup
https://bugs.kde.org/show_bug.cgi?id=432820 --- Comment #3 from Thomas Murach --- Thanks for your quick action! Manpower: fully understood. And one fine day I'll try to contribute more. Until then all I can say is keep up the good work! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 432820] New: Missing German translation in reminder popup
https://bugs.kde.org/show_bug.cgi?id=432820 Bug ID: 432820 Summary: Missing German translation in reminder popup Product: korganizer Version: 5.16.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-b...@kde.org Reporter: asiasuppenes...@gmx.de Target Milestone: --- Created attachment 135604 --> https://bugs.kde.org/attachment.cgi?id=135604&action=edit Screenshot showing the missing translation SUMMARY When the reminder popup hosts several entries, the "Dismiss All" button is not translated to German. It's a small issue, but since I see it almost every day I decided to eventually open this ticket. Not really knowing what I'm talking about, I think it's due to the translation in https://websvn.kde.org/trunk/l10n-kf5/de/messages/korganizer/korgac.po?revision=1583435&view=markup, line 53ff, being marked as fuzzy, which it actually is not. The German translation is a proper translation of the original phrase. Instead, the original English wording is slightly fuzzy, but acceptable in my opinion. STEPS TO REPRODUCE 1. Set your desktop environment language to German 2. Create several calendar entries set for the same date+time, all with reminders activated 3. Let the date+time arrive, so that a reminder popup window is shown 4. Observe the "Dismiss All" button at the bottom of the popup window Last but not least: Thanks for the great work, everyone! OBSERVED RESULT The button shows English text EXPECTED RESULT The button shows German text SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 325224] CalDav doesn't read server items
https://bugs.kde.org/show_bug.cgi?id=325224 Thomas Murach changed: What|Removed |Added CC||asiasuppenes...@gmx.de --- Comment #68 from Thomas Murach --- Same issue here (KOrganizer 5.5.1, OpenSuse 42.2, KDE Frameworks 5.34.0). It would be very nice to see this fixed. Thanks in advance! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 375897] New: Config module crashes when closing window
https://bugs.kde.org/show_bug.cgi?id=375897 Bug ID: 375897 Summary: Config module crashes when closing window Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: asiasuppenes...@gmx.de Target Milestone: --- Application: kcmshell5 (5.8.95) Qt Version: 5.8.0 Frameworks Version: 5.30.0 Operating System: Linux 4.4.36-8-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: After editing the network settings dialog invoked by clicking on the top-right "edit preferences" icon on the network manager widget, I clicked "Apply" and afterwards "Ok". After "OK" the application crashed. My gut feeling is that this happens in something like 50% of the cases, but not always. Maybe a race condition? The crash can be reproduced sometimes. -- Backtrace: Application: Modul für Systemeinstellungen (kcmshell5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2a8effd780 (LWP 11448))] Thread 3 (Thread 0x7f2a73274700 (LWP 11450)): #0 0x7f2a86b3837f in g_main_context_acquire () from /usr/lib64/libglib-2.0.so.0 #1 0x7f2a86b391d5 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f2a86b3942c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f2a8c1118ab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #4 0x7f2a8c0c16ab in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f2a8bf099aa in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #6 0x7f2a8da56d15 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7f2a8bf0e019 in ?? () from /usr/lib64/libQt5Core.so.5 #8 0x7f2a88eb3734 in start_thread () from /lib64/libpthread.so.0 #9 0x7f2a8e981d3d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f2a7c7ca700 (LWP 11449)): #0 0x7f2a8e97949d in poll () from /lib64/libc.so.6 #1 0x7f2a892d63e2 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7f2a892d7fcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7f2a7ed24c29 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f2a8bf0e019 in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x7f2a88eb3734 in start_thread () from /lib64/libpthread.so.0 #6 0x7f2a8e981d3d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2a8effd780 (LWP 11448)): [KCrash Handler] #6 0x02760ba0 in ?? () #7 0x7f2a8cdaf785 in QWidget::destroy(bool, bool) () from /usr/lib64/libQt5Widgets.so.5 #8 0x7f2a8cd76e34 in QApplication::~QApplication() () from /usr/lib64/libQt5Widgets.so.5 #9 0x7f2a8ec43595 in KCMShell::~KCMShell (this=0x7ffd40139ee0, __in_chrg=) at /usr/src/debug/kde-cli-tools-5.8.95/kcmshell/main.h:32 #10 kdemain (_argc=2, _argv=) at /usr/src/debug/kde-cli-tools-5.8.95/kcmshell/main.cpp:309 #11 0x7f2a8e8b86e5 in __libc_start_main () from /lib64/libc.so.6 #12 0x00400799 in _start () at ../sysdeps/x86_64/start.S:118 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 372575] New: Crash when starting KDevelop
https://bugs.kde.org/show_bug.cgi?id=372575 Bug ID: 372575 Summary: Crash when starting KDevelop Product: kdevelop Version: 5.0.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: asiasuppenes...@gmx.de Target Milestone: --- Application: kdevelop (5.0.1) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.1.34-33-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: KDevelop crashes very often when I start it; for example after starting it for the first time after booting my machine in the morning, it will always crash. When starting it again after a crash I'm asked whether I want to delete the cache. If I remember correctly, not clearing the cache will always lead to another crash at some point. Clearing the cache at least increases the chance of a successful startup, although also in this case it crashes often. >From my experience crashes occur at a stage where something on the order of 1-20% of the files in the project folder have been scanned, I've rarely seen crashes at much higher percentages, but maybe I'm just lacking statistics here. I'm happy to provide more info if needed. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f432699e7c0 (LWP 4969))] Thread 11 (Thread 0x7f42b4560700 (LWP 5290)): #0 0x7f431b172cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f431b1304b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7f431b130d80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f431b130f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f43240c3f4b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f432407389b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f4323eba02a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f43219df5d3 in () at /usr/lib64/libKDevPlatformLanguage.so.10 #8 0x7f4323ebe859 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f431d2a50a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f43237c702d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f42d9b49700 (LWP 5289)): #0 0x7f431d2a903f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f4323ebf4cb in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f43188973ff in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f431889adca in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f431889542b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f431889ae12 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f431889542b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f4318898a26 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f4323ebe859 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f431d2a50a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f43237c702d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f42da34a700 (LWP 5288)): [KCrash Handler] #6 0x7f43237170c7 in raise () at /lib64/libc.so.6 #7 0x7f4323718478 in abort () at /lib64/libc.so.6 #8 0x7f4323754784 in () at /lib64/libc.so.6 #9 0x7f432375a026 in malloc_printerr () at /lib64/libc.so.6 #10 0x7f432375ad53 in _int_free () at /lib64/libc.so.6 #11 0x7f42e876a615 in () at /usr/lib64/libkdevcmakecommon.so #12 0x7f42e876b247 in () at /usr/lib64/libkdevcmakecommon.so #13 0x7f42e876c047 in () at /usr/lib64/libkdevcmakecommon.so #14 0x7f42e876cf08 in CMakeListsParser::readCMakeFile(QString const&) () at /usr/lib64/libkdevcmakecommon.so #15 0x7f42e518679d in () at /usr/lib64/qt5/plugins/kdevplatform/25/kdevcmakemanager.so #16 0x7f431889a1aa in ThreadWeaver::IdDecorator::run(QSharedPointer, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #17 0x7f431889a567 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #18 0x7f43188993b0 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #19 0x7f4318898ad7 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7f4323ebe859 in () at /usr/lib64/libQt5Core.so.5 #21 0x7f431d2a50a4 in start_thread () at /lib64/libpthread.so.0 #22 0x7f4
