[plasmashell] [Bug 378037] auto-hide panel appears when focus changes to another window
https://bugs.kde.org/show_bug.cgi?id=378037 --- Comment #7 from Stamatis Kavvadias --- > Having that out of the way, the same bug is _still_ a problem in Kubuntu > 22.04 (KDE Plasma version 5.18.8). Sorry to be back about this, but to be very clear, I really doubt the commit above ([1]), from 2017, has not reached KDE Plasma version 5.18.8. If that is truly the case, that commit _did not_ correct the bug. And, please, don't close this bug as fixed, without filling "Version fixed in". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378037] auto-hide panel appears when focus changes to another window
https://bugs.kde.org/show_bug.cgi?id=378037 --- Comment #6 from Stamatis Kavvadias --- Please, don't be rude. Replying to me after 1 year and 7 months and when Kubuntu 20.04 has been largely surpassed/replaced by 22.04 is already impertinence. The bug you suggest (468356) has the description "when you move the mouse focus away from the panel, it stays visible", which is not the case with my bug. My bug does what is described here: "when focus moves from one window to another the auto-hide panel pops up and stays, covering the bottom of other windows, until a mouse-over on the panel". Having that out of the way, the same bug is _still_ a problem in Kubuntu 22.04 (KDE Plasma version 5.18.8). Please, stop evading this bug and deal with it! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382692] Auto-Hide is broken for plasmashell 5.18.5, 5.22.4,
https://bugs.kde.org/show_bug.cgi?id=382692 --- Comment #15 from Stamatis Kavvadias --- The option that allows panel autohiding in Window Behavior settings is 'Hide utility windows for inactive applications'. I have also mentioned this in bug #378037. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382692] Auto-Hide is broken for plasmashell 5.18.5, 5.22.4,
https://bugs.kde.org/show_bug.cgi?id=382692 Stamatis Kavvadias changed: What|Removed |Added Platform|Archlinux Packages |Kubuntu Packages Version|5.22.4 |5.18.8 CC||stamatis.kavvad...@gmail.co ||m --- Comment #14 from Stamatis Kavvadias --- I have this problem since I was on kubuntu 18.04. My current setup is: kubuntu 20.04 KDE Plasma 5.18.8 KDE Framework 5.68.0 Qt Version: 5.12.8 Single monitor, but the graphics card is connected in 2 monitor inputs (HDMI and DP) and the OS assumes 2 monitors. The problem persist, regardless if I replicate the output of one "monitor" to the other or not. I have 2 panels (bottom and right side). The right side panel is set to autohide; and I use click to focus windows activation policy. The panel hides only after I hover the mouse over it. Whenever I change focus to some window, the panel appears (pops left) and I have to hover over it again, for it to hide. Of course, there is a task manager on the right panel, but I do not want the panel to appear, just to show me that it changed the selected app in the task manager! I have found a way to prevent the problem, but that is not what I want. If I set, in Window Behavior settings, the option "Special windows: Hide helper windows for inactive applications" then the problem stops and the panel does not pop up every time I change the window focus. Btw, I am not sure that the option's title refers to "helper windows" in english, or "auxiliary windows" or something else... What I want is for my e-mail and torrent clients, or any other app that may activate a message window, the window to appear and not wait till I bring up the main application window. But that should not mean that I cannot have a panel that autohides! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378037] auto-hide panel appears when focus changes to another window
https://bugs.kde.org/show_bug.cgi?id=378037 --- Comment #4 from Stamatis Kavvadias --- Reading a thread in KDE forum (https://forum.kde.org/viewtopic.php?t=132342), I just found a way to prevent this problem, in my case: Set 'Hide utility windows for inactive applications' in settings:/workspace/windowmanagement/ -> tab 'Advanced'. [I am using 'Click to focus' for 'Window activation policy'.] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378037] auto-hide panel appears when focus changes to another window
https://bugs.kde.org/show_bug.cgi?id=378037 Stamatis Kavvadias changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- CC||stamatis.kavvad...@gmail.co ||m Status|RESOLVED|REOPENED --- Comment #3 from Stamatis Kavvadias --- The problem still exists in Kubuntu 20.04 (Plasma 5.18.5), as well as in Kubuntu 18.04. It is very annoying. Would you consider fixing this, eventually? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399836] kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 --- Comment #13 from Stamatis Kavvadias --- Listen, I am sorry if I was not clear enough (but you also did not check my previous efforts to provide a backtrace). The case is that, since I provided the initial backtrace (w/o debug symbols), I have accepted an update which changed the situation: I no longer have a version of kwin (or kwin_x11) that crashes from the bug. Instead, my current kwin version just exits normally when the bug happens. This update happened exactly before I tried to attach gdb to kwin, so when I did the result was that gdb *could not* provide a backtrace. I have provided the output of gdb in this case, which explains clearly why. So, tell me something new to do or just delete this bug report, if it cannot be handled, under the circumstances. Thank you for your efforts, anyway. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399836] kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 --- Comment #11 from Stamatis Kavvadias --- Please read the whole (short) history of these comments. I cannot do what you ask any more. The crash does not trigger the KDE Crash Dialog to appear, after there has been an update of kwin and plasma packages. The crash still persists but, according to my efforts to provide a gdb backtrace, kwin exits normally and there can be no backtrace! Unless you can guide me on how to monitor with gdb any signals kwin may be receiving before it exits, I cannot provide the backtrace asked. In my opinion, you should try to debug this differently, as the last update has hidden a bug that once led to a crash, so that it now exits normally. How can this bug ever be reported and corrected now, if you require a backtrace? Nevertheless, if you cannot reproduce the bug, I understand you do not have a place to start. But, this would leave me no option, but to go back to Kubuntu 16.04, which did not have this problem. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399836] kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 Stamatis Kavvadias changed: What|Removed |Added CC||stamatis.kavvad...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399836] kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 Stamatis Kavvadias changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|WORKSFORME |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399836] kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 --- Comment #7 from Stamatis Kavvadias --- Just to make it clear, kwin_x11 exits without a logout and windows are still visible, but non-responsive. This seems wrong to me, or kwin_x11 process received a signal, which I cannot monitor, unless you guide me on how to instruct gdb to catch such an event... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399836] kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 --- Comment #6 from Stamatis Kavvadias --- I found that kwin_x11 symbols are included in the kwin package. I followed the instructions in the page you mention, using gdb from a remote ssh terminal (from my laptop to the desktop). I tried twice to get the backtrace via gdb. The first time there was a kwin process running and no kwin_x11 and the next time the other way round. There has been an update of kwin and plasma packages in-between, but both times gdb cannot provide a backtrace. The first time I was not sure what happened; I provide the output of the second try, bellow. As you will see, it appears kwin_x11 exits normally(!!!) and I cannot get a backtrace. Here is the output of the command used, i.e. gdb --pid `pidof kwin_x11` 2>&1 | tee kwin_x11.gdb --- GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". Attaching to process 2460 [New LWP 2462] [New LWP 2480] [New LWP 2542] [New LWP 2637] [New LWP 2652] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f13b1348cf6 in __GI_ppoll (fds=0x5574122160c8, nfds=5, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 39 ../sysdeps/unix/sysv/linux/ppoll.c: No such file or directory. (gdb) c Continuing. [New Thread 0x7f1379ff7700 (LWP 4603)] [Thread 0x7f1379185700 (LWP 2637) exited] [Thread 0x7f1395788700 (LWP 2480) exited] [Thread 0x7f1379ff7700 (LWP 4603) exited] [Thread 0x7f1370f69700 (LWP 2652) exited] [Thread 0x7f138f5e0700 (LWP 2542) exited] [Thread 0x7f13b19e9cc0 (LWP 2460) exited] [Inferior 1 (process 2460) exited with code 01] (gdb) bt No stack. (gdb) detach The program is not being run. (gdb) run Starting program: /usr/bin/kwin_x11 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". /usr/bin/kwin_x11: FATAL ERROR while trying to open display [Inferior 1 (process 10196) exited with code 01] (gdb) quit -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399836] kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 --- Comment #4 from Stamatis Kavvadias --- I cannot send an updated backtrace because KDE Crash Dialog does not appear again. Your link for howto get symbols for the backtrace is wrong. I had to read a useless page (since I am not classifying this bug, just reporting it) to get to https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports, which instructs on how to get debug symbols. I found out I need to install kdelibs5-dbg. I do not know if I need to install symbols for kwin and which packages to install (kwin does not have any -dbg package available). Still I cannot produce and send a backtrace, if KDE Crash Dialog does not appear . kwin still crashes, after a few desktop changes. It is likely that the cube desktop switch effect and the multiple windows in multiple activities I have running, do not interoperate correctly, but I cannot tell you anything more. What should I do with this bug? Going back to Kubuntu 16.04 is my best alternative. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399836] kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 --- Comment #1 from Stamatis Kavvadias --- I had another crash, just hours after the original report. This time an application (claws-mail) from another activity and a different virtual desktop number, showed up in the task manager. When I clicked on it, kwin crashed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 399836] New: kwin crash on changing virtual desktop
https://bugs.kde.org/show_bug.cgi?id=399836 Bug ID: 399836 Summary: kwin crash on changing virtual desktop Product: kwin Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: stamatis.kavvad...@gmail.com Target Milestone: --- Application: kwin_x11 (5.12.6) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: Windows lose titlebar; I cannot change the focus with the mouse or with ALT-tab; the focused application is not responsive to the keyboard or the mouse; mouse is the only think moving; some lost titlebar usually allows mouse access to the desktop background and I can right-click and select Execute command... to run kwin --replace, which restores normal functionality. If I remember correctly, I can also go to a terminal, with CTRL-ALT-F1/F2 etc during the crash. Windows from all activities appear in a single activity, but retain their virtual desktop, on restore from the crash --I cannot say if this is also the case during the crash. - What I was doing when the application crashed: The crash happens repeatedly, when changing virtual desktop, using the keyboard shortcut (CTRL-ALT-left/right/up/down arrow). Usually, after I have been viewing idly a window for some time; more frequently when I was viewing idly for more than a minut, but it also happens after only 5-10 seconds sometimes. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff0a4aa7cc0 (LWP 9737))] Thread 3 (Thread 0x7fefb9f12700 (LWP 9749)): #0 0x7ff09d4739f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7ff0a0a0afb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7ff09d4739f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7ff0a0a0af68, cond=0x7ff0a0a0af90) at pthread_cond_wait.c:502 #2 0x7ff09d4739f3 in __pthread_cond_wait (cond=0x7ff0a0a0af90, mutex=0x7ff0a0a0af68) at pthread_cond_wait.c:655 #3 0x7ff0a07145f4 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7ff0a0714639 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7ff09d46d6db in start_thread (arg=0x7fefb9f12700) at pthread_create.c:463 #6 0x7ff0a441388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ff088847700 (LWP 9739)): #0 0x7ffc4dd1ab62 in clock_gettime () #1 0x7ff0a4422ea6 in __GI___clock_gettime (clock_id=1, tp=0x7ff088846b80) at ../sysdeps/unix/clock_gettime.c:115 #2 0x7ff0a180c221 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7ff0a180aa59 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff0a180b035 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff0a1809fe4 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff0a17b19ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff0a15d022a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff09ae32d45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7ff0a15d516d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff09d46d6db in start_thread (arg=0x7ff088847700) at pthread_create.c:463 #11 0x7ff0a441388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff0a4aa7cc0 (LWP 9737)): [KCrash Handler] #6 0x7ff0a3f9322d in KWin::Xcb::Extensions::init() () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #7 0x7ff0a3f93ad7 in KWin::Xcb::Extensions::self() () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #8 0x7ff0a3f03a8a in KWin::Application::updateX11Time(xcb_generic_event_t*) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #9 0x7ff0a3f03b32 in () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #10 0x7ff0a17b058f in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7ff08c005820 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #12 0x7ff08c0064ac in QXcbConnection::processXcbEvents() () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #13 0x7ff0a17e3122 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7ff0a253182c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7ff0a25390f4 in QApplication::notify(QObject*, QEvent*) () at
