[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 --- Comment #58 from Steve Ramage --- > Lol, just have a "Nuke X11" button on a shortcut :)). But speaking of which, > it would be worth confirming for the others that would want a dirty fix in > the meantime, does killing kwin_x11 restart the applications smoothly from > where they were left off? Yes sorry, to be clear when I do that, it takes about 5 seconds but my session continues without any negative side effects, the side effects are minimum. All my applications seem unaffected, no crashes or anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478556] Sometimes the stacking order is out of sync with Xorg
https://bugs.kde.org/show_bug.cgi?id=478556 Steve Ramage changed: What|Removed |Added CC||k...@sjrx.net --- Comment #56 from Steve Ramage --- Just wanted to say this is affecting me as well, how I fix it , is by killing kwin_x11 that seems to recover everything. Although maybe that is horrible. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 458605] New: 100% CPU usage and infinite loop while opening HTML file.
https://bugs.kde.org/show_bug.cgi?id=458605 Bug ID: 458605 Summary: 100% CPU usage and infinite loop while opening HTML file. Product: ark Version: 22.08.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: ubu...@sjrx.net CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. echo "Hello" > file.html 2. tar -czf file.tar.gz ./file.html 3. ark file.tar.gz 4. Double click the file. OBSERVED RESULT 100% cpu usage and hanging. EXPECTED RESULT A preview of some kind SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION * Note I was having this issue on 22.04.3 and noticed newer versions on the bug report, so I upgraded just ark to 22.08.0 . So if the versions don't match up that might be why. Using GDB I noticed every time I interrupted the program it seemed to be stuck in: 0x7728769f in QWidget::graphicsEffect() const () from /usr/lib/libQt5Widgets.so.5 Here is one back trace. #0 0x7728769f in QWidget::graphicsEffect() const () at /usr/lib/libQt5Widgets.so.5 #1 0x77288186 in QWidgetPrivate::invalidateGraphicsEffectsRecursively() () at /usr/lib/libQt5Widgets.so.5 #2 0x7728821b in QWidgetPrivate::setDirtyOpaqueRegion() () at /usr/lib/libQt5Widgets.so.5 #3 0x7728b4f1 in QWidgetPrivate::updateIsOpaque() () at /usr/lib/libQt5Widgets.so.5 #4 0x77285c08 in QWidget::create(unsigned long long, bool, bool) () at /usr/lib/libQt5Widgets.so.5 #5 0x7728847f in QWidgetPrivate::createWinId() () at /usr/lib/libQt5Widgets.so.5 #6 0x77296859 in QWidgetPrivate::setParent_sys(QWidget*, QFlags) () at /usr/lib/libQt5Widgets.so.5 #7 0x77298ca2 in QWidget::setParent(QWidget*, QFlags) () at /usr/lib/libQt5Widgets.so.5 #8 0x7727b5bc in QLayout::addChildWidget(QWidget*) () at /usr/lib/libQt5Widgets.so.5 #9 0x7727d044 in QBoxLayout::insertWidget(int, QWidget*, int, QFlags) () at /usr/lib/libQt5Widgets.so.5 #10 0x7fffc95db0c1 in ArkViewer::viewInInternalViewer(QExplicitlySharedDataPointer, QString const&, QString const&, QMimeType const&) (mimeType=, entryPath=..., fileName=..., viewer=..., this=0x55ffb620) at /usr/src/debug/ark-22.08.0/part/arkviewer.cpp:184 #11 ArkViewer::openInternalViewer(QExplicitlySharedDataPointer, QString const&, QString const&, QMimeType const&) (viewer=..., fileName=..., entryPath=..., mimeType=) at /usr/src/debug/ark-22.08.0/part/arkviewer.cpp:93 #12 0x7fffc95d0d87 in ArkViewer::view(QString const&, QString const&) (entryPath=..., fileName=...) at /usr/src/debug/ark-22.08.0/part/arkviewer.cpp:148 #13 Ark::Part::slotPreviewExtractedEntry(KJob*) (this=0x55adde10, job=) at /usr/src/debug/ark-22.08.0/part/part.cpp:1070 #14 0x7680f440 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x77261b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x767ebad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x767ec5e3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #18 0x76832548 in () at /usr/lib/libQt5Core.so.5 #19 0x74d8ac6b in g_main_dispatch (context=0x7fffec005010) at ../glib/glib/gmain.c:3417 #20 g_main_context_dispatch (context=0x7fffec005010) at ../glib/glib/gmain.c:4135 #21 0x74de1001 in g_main_context_iterate.constprop.0 (context=context@entry=0x7fffec005010, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/glib/gmain.c:4211 #22 0x74d88392 in g_main_context_iteration (context=0x7fffec005010, may_block=1) at ../glib/glib/gmain.c:4276 #23 0x7683632c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #24 0x767e427c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x767eeda9 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #26 0x55561550 in main(int, char**) (argc=, argv=) at /usr/src/debug/ark-22.08.0/app/main.cpp:341 I can open the attachment in Ark in an external browser. I did see bug 454181 but the symptoms were different. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401187] Maximized windows covered by plasma after monitor wake up
https://bugs.kde.org/show_bug.cgi?id=401187 --- Comment #5 from Steve Ramage --- (In reply to Nate Graham from comment #4) > A lot has changed since this bug was filed. Is it still reproducible for you > in Plasma 5.25? We made a lot of multimonitor improvements in that version. I think it's safe to close this bug. I haven't noticed this recently. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401187] Maximized windows covered by plasma after monitor wake up
https://bugs.kde.org/show_bug.cgi?id=401187 --- Comment #3 from Steve Ramage --- Also FYI, this is affecting 5.14.3, but that option is not available in the version list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401187] Maximized windows covered by plasma after monitor wake up
https://bugs.kde.org/show_bug.cgi?id=401187 --- Comment #2 from Steve Ramage --- Also a work around I have done is to simply map a keyboard short cut to the following shell script and run it: xrandr --output DP-3-2 --primary xrandr --output DP-3-1 --primary Besides the momentary flicker, it fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401187] Maximized windows covered by plasma after monitor wake up
https://bugs.kde.org/show_bug.cgi?id=401187 --- Comment #1 from Steve Ramage --- This might be related to 372586, I'm not sure. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401187] New: Maximized windows covered by plasma after monitor wake up
https://bugs.kde.org/show_bug.cgi?id=401187 Bug ID: 401187 Summary: Maximized windows covered by plasma after monitor wake up Product: plasmashell Version: 5.14.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ubu...@sjrx.net Target Milestone: 1.0 Created attachment 116397 --> https://bugs.kde.org/attachment.cgi?id=116397=edit Screenshot of issue. SUMMARY STEPS TO REPRODUCE 1. Setup triple monitor installation (maybe an issue with dual or single displays), two external and main laptop display 2. Maximize a window on the primary screen (the bottom of the window should stay above the plasma bar). 3. Turn off external display 1 and 2 3-a) Laptop display turns off automagically (not sure if this matters). 4. Wait 5 seconds. 5. Turn external displays back on 5-a) Laptop display turns on automagically. 6. Look at maximized window on primary display. OBSERVED RESULT Bottom of maximized window is below the plasma bar. EXPECTED RESULT Bottom of maximized window should be above the plasma bar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.2 ADDITIONAL INFORMATION Output of xrandr -q in this state: xrandr -q Screen 0: minimum 320 x 200, current 5120 x 2520, maximum 8192 x 8192 eDP-1 connected 1920x1080+1540+1440 (normal left inverted right x axis y axis) 309mm x 173mm 1920x1080 60.03 + 60.01* 59.9759.9659.9348.03 1680x1050 59.9559.88 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1280x800 59.9959.9759.8159.91 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 700x525 59.98 800x450 59.9559.82 640x512 60.02 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 640x400 59.8859.98 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) HDMI-3 disconnected (normal left inverted right x axis y axis) DP-3-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 708mm x 398mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0024.0029.9723.98 1680x1050 59.88 1600x900 60.00 1280x1024 75.0260.02 1440x900 59.90 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DP-3-2 connected 2560x1440+2560+0 (normal left inverted right x axis y axis) 708mm x 398mm 2560x1440 59.95*+ 1920x1080 60.0059.94 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1440x900 59.89 1280x800 59.81 1152x864 75.00 1280x720 60.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DP-3-3 disconnected (normal left inverted right x axis y axis). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 397279] CTRL+P shortcut being swallowed before application / Changed settings not the same on restart
https://bugs.kde.org/show_bug.cgi?id=397279 --- Comment #2 from Steve Ramage --- Oh I have an update and/or workaround. I'm not sure why but the run command for me had a short cut of CTRL+R. It doesn't work, but I have two keyboard layouts, Dvorak and US. When a physically US keyboard (i.e., QWERTY) is set to Dvorak the QWERTY becomes "<>PY. I'm not sure but this run command short cut seems to be conflict. It doesn't work when set to CTRL+R but ALT+F2 does cause it to show up. Removing the assignment causes CTRL+P to work. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 397279] CTRL+P shortcut being swallowed before application / Changed settings not the same on restart
https://bugs.kde.org/show_bug.cgi?id=397279 --- Comment #1 from Steve Ramage --- Created attachment 114378 --> https://bugs.kde.org/attachment.cgi?id=114378=edit kglobalshortcutsrc file -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 397279] New: CTRL+P shortcut being swallowed before application / Changed settings not the same on restart
https://bugs.kde.org/show_bug.cgi?id=397279 Bug ID: 397279 Summary: CTRL+P shortcut being swallowed before application / Changed settings not the same on restart Product: frameworks-kglobalaccel Version: 5.48.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: ubu...@sjrx.net Target Milestone: --- Overview: Applications (both Plasma) such as Kate and (non Plasma) such as IntelliJ don't seem to receive the Ctrl+P shortcut when pressed. Steps to Reproduce: 1) Open either application, hit Ctrl+P Actual Results: Nothing Expected Results: Print Dialog should show up in Kate, View Parameter Info should show up in IntelliJ. Build Date & Platform: Arch Linux x86_64, running kglobalaccel 5.48.0-1. Additional Information: * Evidence pointing to kglobalaccel and that it isn't a setup issue. 1) It took a while to figure out what was happening, following the advice of (https://unix.stackexchange.com/questions/261371/how-do-i-find-out-what-program-owns-a-hotkey) and (https://bbs.archlinux.org/viewtopic.php?id=179957), lead me to use XF86LogGrabInfo to see what was grabbing the shortcut and it was kglobalaccel5. 2) If I killed kglobalaccel5 process, then the short cuts in both Kate and IntelliJ started to work. * Weird behaivour with Global Shortcuts 1) There is no shortcut for Ctrl+P anywhere in settings that I can see, however I did notice the following behaviour. 2) If I assign something to have a shortcut of Ctrl+P anywhere, that short cut works fine (e.g., take screenshot). 3) If I then unassign that short cut, then the short cut stops doing it's action, however it starts working in IntelliJ and kate. 4. If I then restart kglobalaccel I'm back to square one, nothing happens when hitting Ctrl+P, and nothing is mapped to it. -- You are receiving this mail because: You are watching all bug changes.
