Bug 312152 - On doing press-and-hold F12 (yakuake open/retract shortcut) for 1-2 secs, yakuake doesn't open anymore.
Summary: On doing press-and-hold F12 (yakuake open/retract shortcut) for 1-2 secs, yak...
Status: RESOLVED WORKSFORME
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: 2.9.9
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-24 08:44 UTC by Viranch Mehta
Modified: 2020-04-08 04:33 UTC (History)
3 users (show)

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 Viranch Mehta 2012-12-24 08:44:48 UTC
When I press-and-hold the yakuake's open/retract keyboard shortcut for 1-2 secs (causing it to open/retract too fast and too frequently), it stops opening altogether.

Reproducible: Always

Steps to Reproduce:
1. Start yakuake.
2. Press-and-hold the open/retract keyboard shortcut for 1-2 secs.
3. Yakuake retracts, can no longer open it back.
Actual Results:  
Yakuake retracts, and can no longer be opened with the keyboard shortcut (or by any other way I know of).

Note: it doesn't seem to have crashed, the process is still running. Only seems to have hung up.

Expected Results:  
Yakuake should keep functioning normally.

Running ArchLinux with latest KDE packages- kdelibs 4.9.4-3, kdebase-runtime 4.9.4-1, kdebase-lib 4.9.4-2, kdebase-workspace 4.9.4-1
Comment 1 Anselmo L. S. Melo (anselmolsm) 2013-03-10 05:28:47 UTC
Hi, Viranch Mehta 

Could you please check if you still can reproduce this bug?

I could not trigger it here, also running Arch Linux with KDE packages kdelibs 4.10.1-2, kdebase-runtime 4.10.1-1, kdebase-lib 4.10.1-1, kdebase-workspace 4.10.1-1 and yakuake 2.9.9-1.

Thanks
Comment 2 Viranch Mehta 2013-03-15 15:07:54 UTC
Yes I can still reproduce this bug, although I noticed this happens only when "ask window manager to perform this action" is checked. I should have mentioned this earlier.

Also if it matters, I have 100% width and 90% height.

I'm using: kdelibs 4.10.1-2, kdebase-runtime 4.10.1-1, kdebase-lib 4.10.1-1, kdebase-workspace 4.10.1-1, yakuake 2.9.9-1
Comment 3 Raúl 2013-08-12 10:01:36 UTC
Hi:
I've also bumped into this. I normally work on Debian wheezy w/KDE 4.84 but I've also seen this on Debian sid with KDE 4.10.
On heavy CPU and disk load, yakuake stop answering to the unfold key shortcut. It's not easy to reproduce, but it happens to me from time to time. Here you are a gdb backtrace when yakuake is not responding to the unfold key.

(gdb) thread apply all bt

Thread 3 (Thread 0x7f611e61b700 (LWP 5169)):
#0  0x00007f612d907573 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007f612f16d704 in QProcessManager::run (this=0x7f612f4e6500) at io/qprocess_unix.cpp:245
#2  0x00007f612f094d0b in QThreadPrivate::start (arg=0x7f612f4e6500) at thread/qthread_unix.cpp:307
#3  0x00007f612c160b50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#4  0x00007f612d90da7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f611d515700 (LWP 16726)):
#0  0x00007f612d902e33 in *__GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=-1)
    at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f612a730624 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f612a730744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f612f1be276 in QEventDispatcherGlib::processEvents (this=0x2987e30, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f612f18e8af in QEventLoop::processEvents (this=this@entry=0x7f611d514e10, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f612f18eb38 in QEventLoop::exec (this=0x7f611d514e10, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f612f091d70 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f6130c441fe in KIO::NameLookUpThread::run (this=0x29893f0) at ../../kio/kio/hostinfo.cpp:226
#8  0x00007f612f094d0b in QThreadPrivate::start (arg=0x29893f0) at thread/qthread_unix.cpp:307
#9  0x00007f612c160b50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#10 0x00007f612d90da7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f6131556760 (LWP 5148)):
#0  0x00007f612d902e33 in *__GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=190)
    at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f612a730624 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f612a730744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f612f1be276 in QEventDispatcherGlib::processEvents (this=0x1e73b30, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f612e5da83e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...)
    at kernel/qguieventdispatcher_glib.cpp:204
#5  0x00007f612f18e8af in QEventLoop::processEvents (this=this@entry=0x7fff98729ae0, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f612f18eb38 in QEventLoop::exec (this=0x7fff98729ae0, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007f612f193cf8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#8  0x000000000041597a in _start ()

I can also add that I've tested to focus on each of those 3 threads. On either thread 3 and thread 2 I issue a gdb finish command, expecting for the select or poll ends. Neither of this happen, even when I press the unfold key. On thread 1 poll always ends, even when I don't press any key.

Please, let me know how if I could help to debug this issue further.

HTH,
Comment 4 Ryan McCoskrie 2020-03-08 01:30:24 UTC
Just tried this ~7 years later, doesn't happen on Plasma Neon.

Can anyone reproduce this bug in 2020?
Comment 5 Anselmo L. S. Melo (anselmolsm) 2020-03-09 16:18:08 UTC
(In reply to Ryan McCoskrie from comment #4)
> Just tried this ~7 years later, doesn't happen on Plasma Neon.
> 
> Can anyone reproduce this bug in 2020?

I can't reproduce this in 2020 (like I couldn't in 2013!) ;)
Comment 6 Bug Janitor Service 2020-03-24 04:33:11 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
mark the bug 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 7 Bug Janitor Service 2020-04-08 04:33:12 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!