[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 Nicolas Fella changed: What|Removed |Added Latest Commit||https://invent.kde.org/util ||ities/yakuake/commit/30ace2 ||43fb8f8f9a49df980a1e10e1887 ||27115cb Resolution|NOT A BUG |FIXED --- Comment #13 from Nicolas Fella --- Git commit 30ace243fb8f8f9a49df980a1e10e188727115cb by Nicolas Fella, on behalf of Maximilian Schiller. Committed on 10/07/2020 at 11:24. Pushed by nicolasfella into branch 'master'. Show a warning notification if Konsole is outdated Show a warning popup if yakuake detects that the konsolepart didn't return a TerminalInterfaceV2. Which most likely happens if konsole is outdated. M +5-0app/terminal.cpp https://invent.kde.org/utilities/yakuake/commit/30ace243fb8f8f9a49df980a1e10e188727115cb -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 Christoph Feck changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #12 from Christoph Feck --- Thanks for the update; changing status. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 --- Comment #11 from Paul Brown --- (In reply to Maximilian Schiller from comment #10) > (In reply to Paul Brown from comment #9) > > Very helpful indeed. Based on the crash log I'm suspecting that something is > wrong with your konsole installation. > It does find the konsole part/module correctly which is why you don't get > the error message but the interface seems to be an outdated version. So > either you are running some kind of partial upgrade on your system or you > have installed konsole in some other place from which its loading the module > with a higher priority than the default location. > > The system uses qt plugins to load this in so definitely check that don't > have a QT_PLUGIN_PATH environment variable defined and don't have some > installation of konsole under other default search locations (/usr/local, > .local, etc...). The file you need to look out for should be called > konsolepart.so (The correct one should be the one under /usr/lib/qt/plugins). > > I probably should add a more explanatory error message to yakuake if this > turns out to be the issue. Yes! You did it! I checked and I had installed Konsole-git from AUR (probably because I needed some feature for a video or screenshot) and forgot. The version I installed was interfering with Yakuake. Now everything works. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 --- Comment #10 from Maximilian Schiller --- (In reply to Paul Brown from comment #9) Very helpful indeed. Based on the crash log I'm suspecting that something is wrong with your konsole installation. It does find the konsole part/module correctly which is why you don't get the error message but the interface seems to be an outdated version. So either you are running some kind of partial upgrade on your system or you have installed konsole in some other place from which its loading the module with a higher priority than the default location. The system uses qt plugins to load this in so definitely check that don't have a QT_PLUGIN_PATH environment variable defined and don't have some installation of konsole under other default search locations (/usr/local, .local, etc...). The file you need to look out for should be called konsolepart.so (The correct one should be the one under /usr/lib/qt/plugins). I probably should add a more explanatory error message to yakuake if this turns out to be the issue. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 --- Comment #9 from Paul Brown --- I compiled the latest Git version from here: https://invent.kde.org/utilities/yakuake and used the -DCMAKE_BUILD_TYPE=Debug flag. Now Dr. Konqi says the following crash information is useful (Yay!): Application: Yakuake (yakuake), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8c01e51cc0 (LWP 84597))] Thread 11 (Thread 0x7f8bdeffd700 (LWP 84607)): #0 0x7f8c04de6158 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8c055cbce8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f8c055c9fd4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f8c055c5e0f in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f8c04ddf422 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f8c050f2bf3 in clone () from /usr/lib/libc.so.6 Thread 10 (Thread 0x7f8bdf7fe700 (LWP 84606)): #0 0x7f8c04de6158 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8c055cbce8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f8c055c9fd4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f8c055c5e0f in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f8c04ddf422 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f8c050f2bf3 in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f8bd700 (LWP 84605)): #0 0x7f8c04de6158 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8c055cbce8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f8c055c9fd4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f8c055c5e0f in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f8c04ddf422 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f8c050f2bf3 in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f8becef6700 (LWP 84604)): #0 0x7f8c04de6158 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8c055cbce8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f8c055c9fd4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7f8c055c5e0f in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f8c04ddf422 in start_thread () from /usr/lib/libpthread.so.0 #5 0x7f8c050f2bf3 in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f8bedc02700 (LWP 84603)): #0 0x7f8c04de5e32 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8bf9684dec in ?? () from /usr/lib/dri/iris_dri.so #2 0x7f8bf9684cf8 in ?? () from /usr/lib/dri/iris_dri.so #3 0x7f8c04ddf422 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f8c050f2bf3 in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f8bee403700 (LWP 84602)): #0 0x7f8c04de5e32 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8bf9684dec in ?? () from /usr/lib/dri/iris_dri.so #2 0x7f8bf9684cf8 in ?? () from /usr/lib/dri/iris_dri.so #3 0x7f8c04ddf422 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f8c050f2bf3 in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f8beec04700 (LWP 84601)): #0 0x7f8c04de5e32 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8bf9684dec in ?? () from /usr/lib/dri/iris_dri.so #2 0x7f8bf9684cf8 in ?? () from /usr/lib/dri/iris_dri.so #3 0x7f8c04ddf422 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f8c050f2bf3 in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f8bf8e67700 (LWP 84600)): #0 0x7f8c04de5e32 in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f8bf9684dec in ?? () from /usr/lib/dri/iris_dri.so #2 0x7f8bf9684cf8 in ?? () from /usr/lib/dri/iris_dri.so #3 0x7f8c04ddf422 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f8c050f2bf3 in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f8bfbe76700 (LWP 84599)): #0 0x7f8c050e3aec in read () from /usr/lib/libc.so.6 #1 0x7f8c03f92f2d in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f8c03fe2edb in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f8c03f94221 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f8c0580322c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f8c057a901c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f8c055c4c32 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f8c06808098 in ?? () from /usr/lib/libQt5DBus.so.5 #8 0x7f8c055c5e0f in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f8c04ddf422 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f8c050f2bf3 in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f8c0161e700 (LWP 84598)): #0 0x7f8c050e805f in poll () from /usr/lib/libc.so.6 #1
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 --- Comment #8 from Paul Brown --- (In reply to Maximilian Schiller from comment #7) > (In reply to Paul Brown from comment #6) > Thank you for being this detailed in your bug report. Ah! No problem. I realise how difficult it must be to try and solve a problem with little information. > Did you try removing you yakuakerc (Should be under ~/.config/)? If not > please try that (but keep a backup of it). I have runa find on .config/ and .local/ and I don't seem to have that file, so probably not that. > The snap version probably doesn't contain Konsole but that's unfortunately > something the snap packager did wrong. Yes, that is what I thought. > The next step would be to either manually build yakuake with debug symbols > or use a slightly modified version of the yakuake-git AUR package (since you > are running Manjaro). If you need help with that I and others who can help > are usually in the #yakuake:kde.org matrix channel. I have compiled stuff before, but not with debug symbols. I'll read up on how to do that and get back to you with how I get on. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 --- Comment #7 from Maximilian Schiller --- (In reply to Paul Brown from comment #6) Thank you for being this detailed in your bug report. Did you try removing you yakuakerc (Should be under ~/.config/)? If not please try that (but keep a backup of it). The snap version probably doesn't contain Konsole but that's unfortunately something the snap packager did wrong. The next step would be to either manually build yakuake with debug symbols or use a slightly modified version of the yakuake-git AUR package (since you are running Manjaro). If you need help with that I and others who can help are usually in the #yakuake:kde.org matrix channel. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 --- Comment #6 from Paul Brown --- (In reply to Maximilian Schiller from comment #5) > Does it happen after you changed something about you monitor setup? Thank you for your concern. I have always had two monitors. As I don't change this set up ever, and Yakuake has worked until it stopped working completely, I'm going to have to say "no". I apologise for not being able to pinpoint when it stopped working and what the exact circumstances were, as I didn't use Yakuake every day. It used to always work, on both monitors, and then, one day, it stopped working and never worked again. Yesterday I tried the snap version and it kind of worked in that it did not immediately crash. Instead, when pulled down, it showed the following message: > Yakuake was unable to load the Konsole component. > A Konsole installation is required to use Yakuake. I am guessing this has to do with the fact that snaps run in virtual containers (?). As I was unable to find a similar error online, and konsole does not seem to be in the snap store, I am again stumped as how to get Yakuake working for me. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 Maximilian Schiller changed: What|Removed |Added CC||manim...@outlook.de --- Comment #5 from Maximilian Schiller --- Does it happen after you changed something about you monitor setup? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 --- Comment #4 from Paul Brown --- (In reply to Christoph Feck from comment #3) > Please see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports Yeah, I already read that. > Arch[edit] > > Arch currently doesn't offer debug packages with symbols (Feature Request). > You therefore need to recompile all concerned packages with debugging > symbols. See their informative document Getting Traces. Using Manjaro, but same problem. As this is way beyond my skills, I guess I will not be using Yakuake any more :-( -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 Christoph Feck changed: What|Removed |Added CC||cf...@kde.org --- Comment #3 from Christoph Feck --- Please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 --- Comment #2 from Paul Brown --- How can I provide you with a more helpful backtrace? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 422187] Yakuake crashes on start up
https://bugs.kde.org/show_bug.cgi?id=422187 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- https://invent.kde.org/utilities/yakuake/-/merge_requests/20 is a possible fix, but it's hard to tell whether it is the same issue due to the lack of proper backtrace -- You are receiving this mail because: You are watching all bug changes.
