Bug 387924 - Crash on reverse search
Summary: Crash on reverse search
Status: RESOLVED NOT A BUG
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: 3.0.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-15 09:09 UTC by Heiko Tietze
Modified: 2018-01-03 14:26 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Tietze 2017-12-15 09:09:14 UTC
Reverse search in bash (shift+ctrl+R) crashes yakuake but works in qterminal, for instance. I'm on LXQt with Arch distribution.
Comment 1 Eike Hein 2018-01-01 14:35:13 UTC
Backtrace?

What happens in Konsole?
Comment 2 Heiko Tietze 2018-01-02 08:55:05 UTC
QTerminal works as expected, Yakuake crashes without any feedback. journalctl says "yakuake[547]: shell did not close, sending SIGHUP".Not sure how to get meaningful information out of gdb

gdb yakuake
...
Reading symbols from yakuake...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/yakuake 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe31f0700 (LWP 3404)]
qt5ct: using qt5ct plugin
[New Thread 0x7fffe0a0d700 (LWP 3405)]
Error loading text-to-speech plug-in "speechd"
shell did not close, sending SIGHUP
Comment 3 Eike Hein 2018-01-02 15:22:09 UTC
QTerminal is not Konsole and irrelevant to both Konsole and Yakuake. Could you test with Konsole? Yakuake embeds Konsole (i.e. this bug, if it is one, is 99% likely in Konsole code, that's why I ask).

gdb: You haven't installed debug symbols for Yakuake according to the output you posted. Could you install them and try again?
Comment 4 Heiko Tietze 2018-01-02 17:05:21 UTC
No problem with Konsole, forward and backward works well. Don't know how to "install" debug symbols without setting up everything new. I'm on Arch Linux.
Wonder why I should be the only one with this issue as it is 100% reproducible. Can't you try yourself?
Comment 5 Eike Hein 2018-01-03 12:21:20 UTC
I tried of course - but no, it's not crashing here (and there are no other reports except for yours). So I rely on your information to find out what's going on.

On Arch Linux (which I recommend against using for this reason) I believe you will need to rebuild Yakuake (and likely other packages) with debug symbols to be able to provide a decent crash bug report to developers.
Comment 6 Eike Hein 2018-01-03 12:23:34 UTC
Oh, I just realized what's actually going on and we're on the wrong track here :-). It's not actually crashing!

Ctrl+Shift+R is the default shortcut for "Close Active Terminal". You can change it in the menu -> Configure Shortcuts.
Comment 7 Heiko Tietze 2018-01-03 13:53:04 UTC
(In reply to Eike Hein from comment #6)
> Oh, I just realized what's actually going on and we're on the wrong track
> here :-). It's not actually crashing!
> 
> Ctrl+Shift+R is the default shortcut for "Close Active Terminal". You can
> change it in the menu -> Configure Shortcuts.

Lol, in fact that was the reason. But you should definitely change this to ctrl+W as shift+ctrl+R is the usual shortcut for going forward through the bash history (maybe not well known).
Comment 8 Eike Hein 2018-01-03 14:26:40 UTC
I think it used to be Ctrl+Shift+R in Konsole as well, but Konsole changed it to Ctrl+Shift+X - for consistency I should probably change Yakuake to that ...