[Spectacle] [Bug 476370] Rectangular region corrupts screen content: view seems to be duplicated and shifted
https://bugs.kde.org/show_bug.cgi?id=476370 Raman Gupta changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Raman Gupta --- (In reply to Nate Graham from comment #2) > It looks like your attachment is a text file containing the filename of the > video, not the video itself. Can you attach the video? No the video is too large to attach it. I followed the recommendation from Bugzilla to add the text of the external URL hosting the video as an attachment. Here it is directly: https://rocketraman.com/screencap-2023-10-31_09.53.39.mp4 > I suspect this is already fixed for the upcoming Spectacle 24.02, though. Hope so. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476370] Rectangular region corrupts screen content: view seems to be duplicated and shifted
https://bugs.kde.org/show_bug.cgi?id=476370 --- Comment #1 from Raman Gupta --- Created attachment 162763 --> https://bugs.kde.org/attachment.cgi?id=162763=edit Video of screen corruption -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476370] New: Rectangular region corrupts screen content: view seems to be duplicated and shifted
https://bugs.kde.org/show_bug.cgi?id=476370 Bug ID: 476370 Summary: Rectangular region corrupts screen content: view seems to be duplicated and shifted Classification: Applications Product: Spectacle Version: 23.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: rocketra...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY When choosing a screenshot of a rectangular region, the view is corrupted. Some part of the content on the middle monitor is shown overlaid and shifted right. I have 3 monitors, the issue appears to be with the content on the middle monitor, but some of the "shifted" content overlays the left part of the right monitor. See attached video. This seems related to https://bugs.kde.org/show_bug.cgi?id=385885 but that seems to be marked as fixed, and also that issue is related to mixed-DPI screens. In my case, I do use HiDPI, but with global scaling rather than mixed. This is a new problem after recent updates. This was always fine before. STEPS TO REPRODUCE 1. Open KSpectacle and choose rectangular region SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.8-200.fc38.x86_64 (64-bit) Graphics Platform: X11 Processors: 24 × 12th Gen Intel® Core™ i9-12900KS Memory: 125.0 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.
https://bugs.kde.org/show_bug.cgi?id=383555 --- Comment #34 from Raman Gupta --- (In reply to Davide Cavestro from comment #33) > (In reply to Raman Gupta from comment #32) > > (In reply to Davide Cavestro from comment #31) > > > Switching yakuake to full screen, it works on all monitors even if > > > stacked vertically > > > > Using full screen does not fix it for me. Still only shows on 2/3 monitors. > > The full screen workaround works just on X for me., while if I switch to > wayland the issue persists with no workarounds so far. I think from an earlier message you have 2 monitors right? If so, I guess that would be the difference between your setup and mine. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.
https://bugs.kde.org/show_bug.cgi?id=383555 --- Comment #32 from Raman Gupta --- (In reply to Davide Cavestro from comment #31) > Switching yakuake to full screen, it works on all monitors even if stacked > vertically Using full screen does not fix it for me. Still only shows on 2/3 monitors. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 429408] kde-open5 changes case of argument
https://bugs.kde.org/show_bug.cgi?id=429408 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 15329] Save and remember positions of all windows
https://bugs.kde.org/show_bug.cgi?id=15329 --- Comment #81 from Raman Gupta --- In https://bugs.kde.org/show_bug.cgi?id=470318#c1 Nate explained that X11 apps are allowed to save and restore their own window positions. So I'm guessing that this bug has been open for almost 23 years because this ceased to be an issue on X11, as every app implemented this on their own. However, Nate also explains in https://bugs.kde.org/show_bug.cgi?id=470318#c1 that on Wayland, apps are no longer allowed to restore their own window positions. This can be seen easily with Firefox. MOZ_DISABLE_WAYLAND=1 firefox Firefox running via XWayland is able to remember its own window position (though there is some visual jank as the windows position in the default spot, and then move to the remembered position). But when running firefox natively on Wayland, window positions are not remembered. Nate's comment in late 2020 was about purported progress in Wayland, but this is still not working in 2023. Now that Wayland will not allow apps to remember their own positions, I hope that renewed focus will be applied to this nearly 23 year old issue. For me, this is a showstopper issue for Wayland adoption, as I have many carefully positioned windows with browsers and IDEs and its a major pain to continually reposition Windows across every restart. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470318] Wayland: window positioning lost on application restart
https://bugs.kde.org/show_bug.cgi?id=470318 --- Comment #2 from Raman Gupta --- (In reply to Nate Graham from comment #1) > Per the X11 spec, windows are allowed to place themselves on the screen--but > they aren't required to. If a window doesn't, then KWin places it according > to its > placement policy, which is user-controllable. This includes XWayland apps run > in a Wayland session. I've experimented with `MOZ_DISABLE_WAYLAND=1 firefox` and indeed the window positioning appears to be saved and restored when Firefox is run via XWayland. Thanks for the detailed explanation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470318] New: Wayland: window positioning lost on application restart
https://bugs.kde.org/show_bug.cgi?id=470318 Bug ID: 470318 Summary: Wayland: window positioning lost on application restart Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: rocketra...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY In Wayland, when an application starts, it always starts in the middle of the center monitor, regardless of where it was positioned when it was shut down. This is most annoying for applications for which users routinely have multiple positions opened, carefully positioned. This includes browsers like Firefox and Chrome, and IDEs and editors like Kate and IntelliJ IDEA. This is not an issue in X11. Applications always start up with the same monitor positioning, and window size/positioning STEPS TO REPRODUCE 1. In a Wayland session, start Firefox (configure Firefox to re-open previous Windows and tabs on restart) 2. Move a window to the left (or open multiple windows, and move them around the scrreen and resize them) 3. Shut down Firefox 4. Restart Firefox Same goes for Chrome or IntelliJ IDEA or Dolphin or anything else. OBSERVED RESULT The Firefox window, or windows, are all positioned at the center of the primary screen. EXPECTED RESULT The Firefox windows should all open up at their previous positions, and on the same screens they were on when Firefox was shut down. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.9-300.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 2 × 12th Gen Intel® Core™ i9-12900KS Memory: 3.8 GiB of RAM Graphics Processor: llvmpipe Manufacturer: QEMU Product Name: Standard PC (Q35 + ICH9, 2009) System Version: pc-q35-7.2 ADDITIONAL INFORMATION I've tested this on my own box with AMD graphics hardware, as well as on a QEMU virtual machine using llvmpipe, and its the same behavior. Virtual machine info given above. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Triple-monitor setup with all monitors being the same model (with different serial numbers) gets scrambled on login
https://bugs.kde.org/show_bug.cgi?id=461822 --- Comment #18 from Raman Gupta --- Ok, so someone on Redditt found the root cause here by pointing me to https://bugs.kde.org/show_bug.cgi?id=463527 -- my kscreen2 background service was not running. I recalled I had disabled it some time ago because it was causing issues with my monitors suspending or unsuspending or something, and disabling it helped. Re-enabling the kscreen2 service fixes this problem, as well as https://bugs.kde.org/show_bug.cgi?id=469115. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469115] 3-screen arrangement with one screen having multiple inputs connected to different computers gets messed up when switching the input between computers
https://bugs.kde.org/show_bug.cgi?id=469115 --- Comment #10 from Raman Gupta --- Ok, so someone on Redditt found the root cause here by pointing me to https://bugs.kde.org/show_bug.cgi?id=463527 -- my kscreen2 background service was not running. I recalled I had disabled it some time ago because it was causing issues with my monitors suspending or unsuspending or something, and disabling it helped. Re-enabling the kscreen2 service fixes this problem, as well as https://bugs.kde.org/show_bug.cgi?id=461822. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Triple-monitor setup with all monitors being the same model (with different serial numbers) gets scrambled on login
https://bugs.kde.org/show_bug.cgi?id=461822 --- Comment #17 from Raman Gupta --- Another problem which I suspect is related... I've been trying to switch over to Wayland and have this issue on Wayland as well. Plus on Wayland I have another problem, which is that the per-monitor scaling gets reset to 100% on every login. The scaling setting is not persisted at all. On X11, the global scaling is not affected -- it saves and restores correctly. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469115] 3-screen arrangement with one screen having multiple inputs connected to different computers gets messed up when switching the input between computers
https://bugs.kde.org/show_bug.cgi?id=469115 Raman Gupta changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #8 from Raman Gupta --- FYI I'm back on X11, let me know if you want this output for wayland also -- doing a diff of the ouptuts below I'm not seeing any actual differences. Before: xrandr --verbose== Screen 0: minimum 320 x 200, current 11520 x 2160, maximum 16384 x 16384 DisplayPort-0 connected 3840x2160+0+0 (0x59) normal (normal left inverted right x axis y axis) 597mm x 336mm Identifier: 0x54 Timestamp: 18534 Subpixel: unknown Gamma: 1.0:1.0:1.0 Brightness: 1.0 Clones: CRTC: 1 CRTCs: 1 0 2 3 4 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: _KDE_SCREEN_INDEX: 2 EDID: 000010ac98a14c4d4a30 1f200104b53c22783b5095a8544ea526 0f5054a54b00714f8180a9c0a940d1c0 e100010101014dd000a0f0703e803020 35005550211a00ff0036574b 4b4d34330a202020202000fc0044 454c4c20533237323151530a00fd 00283c89893c010a2020202020200189 02032af1546101020304050607101112 1415161f20215d5e5f23090707830100 00681a0101283c00565e00a0a0a0 2950302035005550211a 000b GAMMA_LUT_SIZE: 4096 range: (0, -1) DEGAMMA_LUT_SIZE: 4096 range: (0, -1) GAMMA_LUT: 0 range: (0, 65535) CTM: 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 DEGAMMA_LUT: 0 range: (0, 65535) TearFree: auto supported: off, on, auto subconnector: Native supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native HDCP Content Type: HDCP Type0 supported: HDCP Type0, HDCP Type1 Content Protection: Undesired supported: Undesired, Desired, Enabled vrr_capable: 1 range: (0, 1) max bpc: 8 range: (8, 16) underscan vborder: 0 range: (0, 128) underscan hborder: 0 range: (0, 128) underscan: off supported: off, on, auto scaling mode: None supported: None, Full, Center, Full aspect link-status: Good supported: Good, Bad CONNECTOR_ID: 86 supported: 86 non-desktop: 0 range: (0, 1) 3840x2160 (0x59) 533.250MHz +HSync -VSync *current +preferred h: width 3840 start 3888 end 3920 total 4000 skew0 clock 133.31KHz v: height 2160 start 2163 end 2168 total clock 60.00Hz 3840x2160 (0x5a) 594.000MHz +HSync +VSync h: width 3840 start 4016 end 4104 total 4400 skew0 clock 135.00KHz v: height 2160 start 2168 end 2178 total 2250 clock 60.00Hz 3840x2160 (0x5b) 593.407MHz +HSync +VSync h: width 3840 start 4016 end 4104 total 4400 skew0 clock 134.87KHz v: height 2160 start 2168 end 2178 total 2250 clock 59.94Hz 3840x2160 (0x5c) 297.000MHz +HSync +VSync h: width 3840 start 4016 end 4104 total 4400 skew0 clock 67.50KHz v: height 2160 start 2168 end 2178 total 2250 clock 30.00Hz 3840x2160 (0x5d) 297.000MHz +HSync +VSync h: width 3840 start 4896 end 4984 total 5280 skew0 clock 56.25KHz v: height 2160 start 2168 end 2178 total 2250 clock 25.00Hz 3840x2160 (0x5e) 297.000MHz +HSync +VSync h: width 3840 start 5116 end 5204 total 5500 skew0 clock 54.00KHz v: height 2160 start 2168 end 2178 total 2250 clock 24.00Hz 3840x2160 (0x5f) 296.703MHz +HSync +VSync h: width 3840 start 4016 end 4104 total 4400 skew0 clock 67.43KHz v: height 2160 start 2168 end 2178 total 2250 clock 29.97Hz 3840x2160 (0x60) 296.703MHz +HSync +VSync h: width 3840 start 5116 end 5204 total 5500 skew0 clock 53.95KHz v: height 2160 start 2168 end 2178 total 2250 clock 23.98Hz 2560x1440 (0x61) 241.500MHz +HSync -VSync h: width 2560 start 2608 end 2640 total 2720 skew0 clock 88.79KHz v: height 1440 start 1443 end 1448 total 1481
[plasmashell] [Bug 469115] Notification positioning becomes "lost" if the primary monitor switches off temporarily
https://bugs.kde.org/show_bug.cgi?id=469115 --- Comment #6 from Raman Gupta --- Also, any settings (such as Scale configuration) are lost for the monitor that switches inputs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469115] Notification positioning becomes "lost" if the primary monitor switches off temporarily
https://bugs.kde.org/show_bug.cgi?id=469115 --- Comment #5 from Raman Gupta --- In Wayland, starting output of `kscreen-doctor -a`: Output: 1 DP-1 enabled connected priority 2 DisplayPort Modes: 0:3840x2160@60*! 1:3840x2160@60 2:3840x2160@60 3:3840x2160@30 4:3840x2160@30 5:3840x2160@25 6:3840x2160@24 7:3840x2160@24 8:2560x1440@60 9:2048x1280@60 10:1920x1200@60 11:1920x1080@60 12:1920x1080@60 13:1920x1080@60 14:1920x1080@50 15:1920x1080@25 16:1920x1080@24 17:1920x1080@24 18:1600x1200@60 19:1680x1050@60 20:1600x900@60 21:1280x1024@75 22:1280x1024@60 23:1440x900@60 24:1280x800@60 25:1152x864@75 26:1280x720@60 27:1280x720@60 28:1024x768@75 29:1024x768@60 30:800x600@75 31:800x600@60 32:720x576@50 33:720x576@50 34:720x480@60 35:720x480@60 36:720x480@60 37:720x480@60 38:640x480@75 39:640x480@60 40:640x480@60 41:640x480@60 42:720x400@70 43:1600x1200@60 44:1280x1024@60 45:1024x768@60 46:2560x1600@60 47:1920x1200@60 48:1280x800@60 49:3840x2160@60 50:3200x1800@60 51:2880x1620@60 52:2560x1440@60 53:1920x1080@60 54:1600x900@60 55:1368x768@60 56:1280x720@60 Geometry: 0,0 3491x1964 Scale: 1.1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 2 HDMI-A-1 enabled connected priority 3 HDMI Modes: 0:3840x2160@60*! 1:3840x2160@60 2:3840x2160@60 3:3840x2160@30 4:3840x2160@30 5:3840x2160@25 6:3840x2160@24 7:3840x2160@24 8:2560x1440@60 9:2048x1280@60 10:1920x1200@60 11:1920x1080@60 12:1920x1080@60 13:1920x1080@60 14:1920x1080@50 15:1920x1080@25 16:1920x1080@24 17:1920x1080@24 18:1600x1200@60 19:1680x1050@60 20:1600x900@60 21:1280x1024@75 22:1280x1024@60 23:1440x900@60 24:1280x800@60 25:1152x864@75 26:1280x720@60 27:1280x720@60 28:1024x768@75 29:1024x768@60 30:800x600@75 31:800x600@60 32:720x576@50 33:720x576@50 34:720x480@60 35:720x480@60 36:720x480@60 37:720x480@60 38:640x480@75 39:640x480@60 40:640x480@60 41:640x480@60 42:720x400@70 43:1600x1200@60 44:1280x1024@60 45:1024x768@60 46:2560x1600@60 47:1920x1200@60 48:1280x800@60 49:3840x2160@60 50:3200x1800@60 51:2880x1620@60 52:2560x1440@60 53:1920x1080@60 54:1600x900@60 55:1368x768@60 56:1280x720@60 Geometry: 6982,0 3491x1964 Scale: 1.1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 3 DP-2 enabled connected priority 1 DisplayPort Modes: 0:3840x2160@60*! 1:3840x2160@60 2:3840x2160@60 3:3840x2160@30 4:3840x2160@30 5:3840x2160@25 6:3840x2160@24 7:3840x2160@24 8:2560x1440@60 9:2048x1280@60 10:1920x1200@60 11:1920x1080@60 12:1920x1080@60 13:1920x1080@60 14:1920x1080@50 15:1920x1080@25 16:1920x1080@24 17:1920x1080@24 18:1600x1200@60 19:1680x1050@60 20:1600x900@60 21:1280x1024@75 22:1280x1024@60 23:1440x900@60 24:1280x800@60 25:1152x864@75 26:1280x720@60 27:1280x720@60 28:1024x768@75 29:1024x768@60 30:800x600@75 31:800x600@60 32:720x576@50 33:720x576@50 34:720x480@60 35:720x480@60 36:720x480@60 37:720x480@60 38:640x480@75 39:640x480@60 40:640x480@60 41:640x480@60 42:720x400@70 43:1600x1200@60 44:1280x1024@60 45:1024x768@60 46:2560x1600@60 47:1920x1200@60 48:1280x800@60 49:3840x2160@60 50:3200x1800@60 51:2880x1620@60 52:2560x1440@60 53:1920x1080@60 54:1600x900@60 55:1368x768@60 56:1280x720@60 Geometry: 3491,0 3491x1964 Scale: 1.1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown And output after switching the monitor input on the primary monitor: Output: 1 DP-1 enabled connected priority 1 DisplayPort Modes: 0:3840x2160@60*! 1:3840x2160@60 2:3840x2160@60 3:3840x2160@30 4:3840x2160@30 5:3840x2160@25 6:3840x2160@24 7:3840x2160@24 8:2560x1440@60 9:2048x1280@60 10:1920x1200@60 11:1920x1080@60 12:1920x1080@60 13:1920x1080@60 14:1920x1080@50 15:1920x1080@25 16:1920x1080@24 17:1920x1080@24 18:1600x1200@60 19:1680x1050@60 20:1600x900@60 21:1280x1024@75 22:1280x1024@60 23:1440x900@60 24:1280x800@60 25:1152x864@75 26:1280x720@60 27:1280x720@60 28:1024x768@75 29:1024x768@60 30:800x600@75 31:800x600@60 32:720x576@50 33:720x576@50 34:720x480@60 35:720x480@60 36:720x480@60 37:720x480@60 38:640x480@75 39:640x480@60 40:640x480@60 41:640x480@60 42:720x400@70 43:1600x1200@60 44:1280x1024@60 45:1024x768@60 46:2560x1600@60 47:1920x1200@60 48:1280x800@60 49:3840x2160@60 50:3200x1800@60 51:2880x1620@60 52:2560x1440@60 53:1920x1080@60 54:1600x900@60 55:1368x768@60 56:1280x720@60 Geometry: 0,0 3491x1964 Scale: 1.1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 2 HDMI-A-1 enabled connected priority 3 HDMI Modes: 0:3840x2160@60*! 1:3840x2160@60 2:3840x2160@60 3:3840x2160@30 4:3840x2160@30 5:3840x2160@25 6:3840x2160@24 7:3840x2160@24 8:2560x1440@60 9:2048x1280@60 10:1920x1200@60 11:1920x1080@60 12:1920x1080@60 13:1920x1080@60 14:1920x1080@50 15:1920x1080@25 16:1920x1080@24 17:1920x1080@24 18:1600x1200@60 19:1680x1050@60 20:1600x900@60 21:1280x1024@75 22:1280x1024@60 23:1440x900@60 24:1280x800@60 25:1152x864@75 26:1280x720@60 27:1280x720@60 28:1024x768@75 29:1024x768@60 30:800x600@75 31:800x600@60 32:720x576@50 33:720x576@50 34:720x480@60 35:720x480@60 36:720x480@60 37:720x480@60 38:640x480@75 39:640x480@60 40:640x480@60 41:640x480@60 42:720x400@70 43
[plasmashell] [Bug 469115] Notification positioning becomes "lost" if the primary monitor switches off temporarily
https://bugs.kde.org/show_bug.cgi?id=469115 Raman Gupta changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Raman Gupta --- (In reply to Nate Graham from comment #3) > Thanks. I was looking for one-pixel overlaps, which are known to trigger > this, but it looks like there are none. > > Does this happen on Wayland too, or just X11? It does not, but the behavior on Wayland is even worse. What happens on Wayland is that the Display Configuration window shows the notification "A new output has been added. Settings have been reloaded." and then completely re-arranges the displays. It switches the position of the middle and right monitors for some reason, and switches the primary to the first monitor, which completely messes up my window layouts. I'm guessing by re-arranging the displays and resetting the display configuration Wayland avoids this notification issue (remember the manual workaround on X11 is to change the monitor priorities and then change them back), but the overall behavior of the system is far more annoying than on X11. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469115] Notification positioning becomes "lost" if the primary monitor switches off temporarily
https://bugs.kde.org/show_bug.cgi?id=469115 Raman Gupta changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|FIXED |--- --- Comment #2 from Raman Gupta --- (In reply to Nate Graham from comment #1) > When things are in this strange state, can you run `kscreen-doctor -o` in a > terminal window and paste the output here? Output of `kscreen-doctor -o` in the strange state does not change -- it is exactly the same as the output in the normal correct state, which is: Output: 84 DisplayPort-0 enabled connected priority 2 DisplayPort Modes: 89:3840x2160@60*! 90:3840x2160@60 91:3840x2160@60 92:3840x2160@30 93:3840x2160@25 94:3840x2160@24 95:3840x2160@30 96:3840x2160@24 97:2560x1440@60 98:2048x1280@60 99:1920x1200@60 100:1920x1080@60 101:1920x1080@60 102:1920x1080@50 103:1920x1080@60 104:1920x1080@25 105:1920x1080@24 106:1920x1080@24 107:1600x1200@60 108:1680x1050@60 109:1600x900@60 110:1280x1024@75 111:1280x1024@60 112:1440x900@60 113:1280x800@60 114:1152x864@75 115:1280x720@60 116:1280x720@60 117:1024x768@75 118:1024x768@60 119:800x600@75 120:800x600@60 121:720x576@50 122:720x480@60 123:720x480@60 124:640x480@75 125:640x480@60 126:640x480@60 127:720x400@70 Geometry: 0,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 85 DisplayPort-1 enabled connected priority 1 DisplayPort Modes: 89:3840x2160@60*! 90:3840x2160@60 91:3840x2160@60 92:3840x2160@30 93:3840x2160@25 94:3840x2160@24 95:3840x2160@30 96:3840x2160@24 97:2560x1440@60 98:2048x1280@60 99:1920x1200@60 100:1920x1080@60 101:1920x1080@60 102:1920x1080@50 103:1920x1080@60 104:1920x1080@25 105:1920x1080@24 106:1920x1080@24 107:1600x1200@60 108:1680x1050@60 109:1600x900@60 110:1280x1024@75 111:1280x1024@60 112:1440x900@60 113:1280x800@60 114:1152x864@75 115:1280x720@60 116:1280x720@60 117:1024x768@75 118:1024x768@60 119:800x600@75 120:800x600@60 121:720x576@50 122:720x480@60 123:720x480@60 124:640x480@75 125:640x480@60 126:640x480@60 127:720x400@70 Geometry: 3840,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 86 DisplayPort-2 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 87 HDMI-A-0 enabled connected priority 3 HDMI Modes: 90:3840x2160@60*! 91:3840x2160@60 92:3840x2160@30 93:3840x2160@25 94:3840x2160@24 95:3840x2160@30 96:3840x2160@24 97:2560x1440@60 100:1920x1080@60 101:1920x1080@60 102:1920x1080@50 103:1920x1080@60 104:1920x1080@25105:1920x1080@24 106:1920x1080@24 107:1600x1200@60 109:1600x900@60 110:1280x1024@75 111:1280x1024@60 114:1152x864@75 115:1280x720@60 116:1280x720@60 117:1024x768@75 118:1024x768@60 119:800x600@75 120:800x600@60 121:720x576@50 122:720x480@60 123:720x480@60 124:640x480@75 125:640x480@60 126:640x480@60 127:720x400@70 128:2048x1280@60 129:1920x1200@60 130:1680x1050@60 131:1440x900@60 132:1280x800@60 Geometry: 7680,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361623] Notifications is shown in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=361623 --- Comment #14 from Raman Gupta --- (In reply to Nate Graham from comment #13) > That sounds like something different. Would be best to get a new bug report > for it, especially if it's consistently reproducible. It is consistently reproducible. Here is the new issue: https://bugs.kde.org/show_bug.cgi?id=469115. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469115] New: Notification positioning becomes "lost" if the primary monitor switches off temporarily
https://bugs.kde.org/show_bug.cgi?id=469115 Bug ID: 469115 Summary: Notification positioning becomes "lost" if the primary monitor switches off temporarily Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: rocketra...@gmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY I have a multi-monitor display with 3 monitors. My primary monitor has two HDMI inputs from two different computers -- if I switch the monitor to the other input, and then switch it back to the original input, notifications and hover views no longer show up in the correct positions. Examples: * Hover over a task bar window, the window preview shows up on the secondary monitor (to the left of the primary), bottom right. * Hover over the audio plasmashell widget in the task bar, the volume/input summary shows on the secondary monitor (to the left of the primary), bottom right. * Click on the audio plasmashell widget in the task bar, the audio volume dialog box shows up on the primary monitor, bottom left. * Notifications show up just below the middle of the primary screen. This weird state can be manually reset by changing the primary in display priorities in the Display Settings to another monitor, applying those changes, and then back to the way things were. STEPS TO REPRODUCE 1. Switch monitor to secondary input, and then back. It may work by turning off the monitor as well -- honestly, I haven't tried because I am scared Plasma will mess up my desktop layout :-) 2. Hover over anything in the task bar. OBSERVED RESULT Hover views and other things are placed in the wrong position / sometimes on the wrong monitor. EXPECTED RESULT Correct placement. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.105.0 Qt Version: 5.15.9 Kernel Version: 6.2.12-300.fc38.x86_64 (64-bit) Graphics Platform: X11 Graphics Processor: AMD Radeon RX 6600 XT ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361623] Notifications is shown in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=361623 --- Comment #12 from Raman Gupta --- Nate, in my case I found that notifications would be misplaced after my primary monitor turned off for a moment (for example, when switching inputs). The notifications went back to normal after switching the primary to secondary, and then from secondary back to primary. Is this a different issue or the same one that is now resolved? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Triple-monitor setup with all monitors being the same model (with different serial numbers) gets scrambled on login
https://bugs.kde.org/show_bug.cgi?id=461822 Raman Gupta changed: What|Removed |Added Version|5.27.3 |5.27.4 --- Comment #16 from Raman Gupta --- Still an issue on 5.27.4. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 446349] Android phone does not stop ringing after using 'Ring my phone' feature
https://bugs.kde.org/show_bug.cgi?id=446349 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Triple-monitor setup with all monitors being the same model (with different serial numbers) gets scrambled on login
https://bugs.kde.org/show_bug.cgi?id=461822 Raman Gupta changed: What|Removed |Added Version|5.27.0 |5.27.3 --- Comment #15 from Raman Gupta --- Still an issue on 5.27.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361623] Notifications is shown in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=361623 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com --- Comment #10 from Raman Gupta --- I have this highly annoying issue also. Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-200.fc37.x86_64 (64-bit) Graphics Platform: X11 Triple-monitor setup, High DPI. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.
https://bugs.kde.org/show_bug.cgi?id=383555 --- Comment #29 from Raman Gupta --- One other detail: when opening on the left monitor, yakuake opens according to my settings: horizontally centered. But when opening on the middle monitor, yakuake opens horizontally left-aligned to screen edge, and when opening on the right monitor, yakuake opens on the middle monitor but horizontally right-aligned to screen edge. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 383555] Yakuake doesn't show on Screen2 when I'm working on two monitors.
https://bugs.kde.org/show_bug.cgi?id=383555 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com --- Comment #28 from Raman Gupta --- I have the same problem with 3 hidpi screens on Plasma 5.27.0. Yakuake is configured to open at the mouse location, but I can only open it on the left or middle screens. Attempting to open it on the right screen opens it on the middle screen instead. Deleting `~/.config/yakuakerc ` and restarting yakuake did not fix the problem for me. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Triple-monitor setup with all monitors being the same model (with different serial numbers) gets scrambled on login
https://bugs.kde.org/show_bug.cgi?id=461822 --- Comment #14 from Raman Gupta --- Here is the new `kscreen-doctor -o` output with my new hardware: Output: 84 DisplayPort-0 enabled connected priority 2 DisplayPort Modes: 89:3840x2160@60*! 90:3840x2160@60 91:3840x2160@60 92:3840x2160@30 93:3840x2160@25 94:3840x2160@24 95:3840x2160@30 96:3840x2160@24 97:2560x1440@60 98:2048x1280@60 99:1920x1200@60 100:1920x1080@60 101:1920x1080@60 102:1920x1080@50 103:1920x1080@60 104:1920x1080@25 105:1920x1080@24 106:1920x1080@24 107:1600x1200@60 108:1680x1050@60 109:1600x900@60 110:1280x1024@75 111:1280x1024@60 112:1440x900@60 113:1280x800@60 114:1152x864@75 115:1280x720@60 116:1280x720@60 117:1024x768@75 118:1024x768@60 119:800x600@75 120:800x600@60 121:720x576@50 122:720x480@60 123:720x480@60 124:640x480@75 125:640x480@60 126:640x480@60 127:720x400@70 Geometry: 0,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 85 DisplayPort-1 enabled connected priority 1 DisplayPort Modes: 89:3840x2160@60*! 90:3840x2160@60 91:3840x2160@60 92:3840x2160@30 93:3840x2160@25 94:3840x2160@24 95:3840x2160@30 96:3840x2160@24 97:2560x1440@60 98:2048x1280@60 99:1920x1200@60 100:1920x1080@60 101:1920x1080@60 102:1920x1080@50 103:1920x1080@60 104:1920x1080@25 105:1920x1080@24 106:1920x1080@24 107:1600x1200@60 108:1680x1050@60 109:1600x900@60 110:1280x1024@75 111:1280x1024@60 112:1440x900@60 113:1280x800@60 114:1152x864@75 115:1280x720@60 116:1280x720@60 117:1024x768@75 118:1024x768@60 119:800x600@75 120:800x600@60 121:720x576@50 122:720x480@60 123:720x480@60 124:640x480@75 125:640x480@60 126:640x480@60 127:720x400@70 Geometry: 3840,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 86 DisplayPort-2 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 87 HDMI-A-0 enabled connected priority 3 HDMI Modes: 90:3840x2160@60*! 91:3840x2160@60 92:3840x2160@30 93:3840x2160@25 94:3840x2160@24 95:3840x2160@30 96:3840x2160@24 97:2560x1440@60 100:1920x1080@60 101:1920x1080@60 102:1920x1080@50 103:1920x1080@60 104:1920x1080@25 105:1920x1080@24 106:1920x1080@24 107:1600x1200@60 109:1600x900@60 110:1280x1024@75 111:1280x1024@60 114:1152x864@75 115:1280x720@60 116:1280x720@60 117:1024x768@75 118:1024x768@60 119:800x600@75 120:800x600@60 121:720x576@50 122:720x480@60 123:720x480@60 124:640x480@75 125:640x480@60 126:640x480@60 127:720x400@70 128:1920x1200@60 129:1680x1050@60 130:1440x900@60 131:1280x800@60 Geometry: 7680,0 3840x2160 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Each of two monitors are mis-identified as the other one on login
https://bugs.kde.org/show_bug.cgi?id=461822 Raman Gupta changed: What|Removed |Added Version|5.26.5 |5.27.0 --- Comment #13 from Raman Gupta --- So I had high hopes for Plasma 5.27 solving this, but it looks like this is *still* an issue in 5.27. Some of my hardware is different from my prior reports, but the problem remains the same. I now have 3 different monitors -- my monitors are all the same model (Dell S2721QS), but Display Configuration shows a different serial # for all of them, so there is no particular reason why Plasma/KScreen shouldn't be able to differentiate them. I choose the screen priorities (middle monitor as highest priority). The display shifts as expected. I then logout, restart sddm, log in again and -- the left monitor has become highest priority again. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 462307] No folder or file icons are shown
https://bugs.kde.org/show_bug.cgi?id=462307 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Each of two monitors are mis-identified as the other one on login
https://bugs.kde.org/show_bug.cgi?id=461822 Raman Gupta changed: What|Removed |Added Version|5.26.2 |5.26.5 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Each of two monitors are mis-identified as the other one on login
https://bugs.kde.org/show_bug.cgi?id=461822 Raman Gupta changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #12 from Raman Gupta --- (In reply to Nate Graham from comment #11) > Thanks. Out of curiosity, does it work better when you start in a Wayland > session and reboot into another wayland session? Same problem in Wayland, except (somewhat amusingly), it keeps choosing the center monitor -- the one I want -- as the Primary display rather than the left monitor like in X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461927] In WindowHeap-based effects, moving focus to windows on another screen takes too many keypresses and can be unpredictable
https://bugs.kde.org/show_bug.cgi?id=461927 --- Comment #4 from Raman Gupta --- (In reply to Nate Graham from comment #3) > Better now? Yep. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461927] In WindowHeap-based effects, window filtering should filter windows on all screens, not just the current screen
https://bugs.kde.org/show_bug.cgi?id=461927 --- Comment #2 from Raman Gupta --- (In reply to Nate Graham from comment #1) > Right now filtering is per-screen. So you have to move focus over to the > other screen if you want to filter the windows on that screen. I'm not sure this is the best characterization. The *filtering* works on all screens i.e. only the windows that match what I have typed show on all screens. The problem is really the subsequent keyboard selection of the post-filtered windows across screens with arrow keys, and then selecting a particular window with the enter key. You can see some of the issues even without filtering. For example, use present windows and then attempt to move the window selection with the arrow keys across screens. Sometimes it takes three presses of the arrow key to "jump across" the screen gap, and sometimes it takes only one. The problems only get worse when filtering is used and some screens have no matching windows shown at all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455974] Present windows with multiple monitors only shows windows on active display
https://bugs.kde.org/show_bug.cgi?id=455974 Raman Gupta changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=461927 --- Comment #23 from Raman Gupta --- Created https://bugs.kde.org/show_bug.cgi?id=461927 for anyone interested in the keyboard type and select issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461927] Present windows: cannot select windows on non-active monitors with typing and keyboard
https://bugs.kde.org/show_bug.cgi?id=461927 Raman Gupta changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=455974 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461927] New: Present windows: cannot select windows on non-active monitors with typing and keyboard
https://bugs.kde.org/show_bug.cgi?id=461927 Bug ID: 461927 Summary: Present windows: cannot select windows on non-active monitors with typing and keyboard Classification: Plasma Product: kwin Version: 5.26.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: rocketra...@gmail.com Target Milestone: --- SUMMARY This is a follow-up to https://bugs.kde.org/show_bug.cgi?id=455974. While present windows now shows the correct windows, typing to find a window on a non-active monitor focuses it, but it is not selected and therefore cannot be selected with the Enter key. STEPS TO REPRODUCE 1. Have windows open on multiple monitors 2. Type to narrow down the selection to a single window on a secondary monitor 3. The window is not "selected" and so enter does not focus it Sometimes a selection can be made by pressing the arrow keys, seemingly randomly, but the behavior does not seem to be deterministic. If typing narrows focus to multiple windows, the arrow keys can be used to select a window on the non-active screen, but sometimes it seems an extra keypress is required to "transition" screens. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.8-300.fc37.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Each of two monitors are mis-identified as the other one when display connector IDs change on boot
https://bugs.kde.org/show_bug.cgi?id=461822 Raman Gupta changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED Version|5.25.5 |5.26.2 --- Comment #10 from Raman Gupta --- I confirm this issue still exists on 5.26.2. Exactly the same behavior as before. Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 6.0.8-300.fc37.x86_64 (64-bit) Graphics Platform: X11 `kscreen-doctor -o` has same output as before. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Each of two monitors are mis-identified as the other one when display connector IDs change on boot
https://bugs.kde.org/show_bug.cgi?id=461822 --- Comment #9 from Raman Gupta --- (In reply to Nate Graham from comment #7) > Thanks. There's probably a bug in the detection algorithm that's causing it > to incorrectly take into account the connector name when it doesn't need to, > which triggers the issue due to an AMD-specific kernel bug that results in > the connector IDs changing on boot (which I can't find a link to right now, > sorry). > A colleague found the AMD kernel bug for me: > https://bugzilla.kernel.org/show_bug.cgi?id=206387. I don't think this kernel bug is affecting me -- my Xorg logs show that the output names are consistent from boot to boot: [root@edison ~]# grep DisplayPort- /var/log/Xorg.0.log [27.175] (II) AMDGPU(0): Output DisplayPort-0 has no monitor section [27.177] (II) AMDGPU(0): Output DisplayPort-1 has no monitor section [27.177] (II) AMDGPU(0): Output DisplayPort-2 has no monitor section [27.218] (II) AMDGPU(0): EDID for output DisplayPort-0 [27.218] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [27.220] (II) AMDGPU(0): EDID for output DisplayPort-1 [27.221] (II) AMDGPU(0): Printing probed modes for output DisplayPort-1 [27.221] (II) AMDGPU(0): EDID for output DisplayPort-2 [27.222] (II) AMDGPU(0): Output DisplayPort-0 connected [27.222] (II) AMDGPU(0): Output DisplayPort-1 connected [27.222] (II) AMDGPU(0): Output DisplayPort-2 disconnected [27.222] (II) AMDGPU(0): Output DisplayPort-0 using initial mode 2560x1440 +0+0 [27.222] (II) AMDGPU(0): Output DisplayPort-1 using initial mode 2560x1440 +2560+0 [root@edison ~]# grep DisplayPort- /var/log/Xorg.0.log.old [26.438] (II) AMDGPU(0): Output DisplayPort-0 has no monitor section [26.440] (II) AMDGPU(0): Output DisplayPort-1 has no monitor section [26.440] (II) AMDGPU(0): Output DisplayPort-2 has no monitor section [26.487] (II) AMDGPU(0): EDID for output DisplayPort-0 [26.487] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0 [26.489] (II) AMDGPU(0): EDID for output DisplayPort-1 [26.490] (II) AMDGPU(0): Printing probed modes for output DisplayPort-1 [26.490] (II) AMDGPU(0): EDID for output DisplayPort-2 [26.491] (II) AMDGPU(0): Output DisplayPort-0 connected [26.491] (II) AMDGPU(0): Output DisplayPort-1 connected [26.491] (II) AMDGPU(0): Output DisplayPort-2 disconnected [26.491] (II) AMDGPU(0): Output DisplayPort-0 using initial mode 2560x1440 +0+0 [26.491] (II) AMDGPU(0): Output DisplayPort-1 using initial mode 2560x1440 +2560+0 > I think we changed the detection algorithm in Plasma 5.26. Any chance you > could test with 5.26 to see if it's still happening? I'm planning to update to Fedora 37 shortly which I believe has 5.26. I'll report back here once I have tried it. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Primary display setting does not persist
https://bugs.kde.org/show_bug.cgi?id=461822 --- Comment #6 from Raman Gupta --- Created attachment 153812 --> https://bugs.kde.org/attachment.cgi?id=153812=edit Display Configuration view Attached a view of the Display Configuration kcm, with the monitor models and serial numbers detected showing, and a visual representation of which monitor I am choosing as primary and which KDE keeps selecting as primary on reboot. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Primary display setting does not persist
https://bugs.kde.org/show_bug.cgi?id=461822 Raman Gupta changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Primary display setting does not persist
https://bugs.kde.org/show_bug.cgi?id=461822 --- Comment #5 from Raman Gupta --- (In reply to Nate Graham from comment #4) > Ok, so the problem is that the display connector ID that KScreen thinks each > screen is connected to is reversing on login. On one boot, your intended > primary monitor has the ID "DisplayPort-0" and on the next boot, it's got > the ID "DisplayPort-0" Because this data is used to disambiguate screens > that have otherwise identical information (e.g. identical serial numbers), > KScreen is getting confused about which physical monitor is the primary one. > > I'm assuming that you're not manually plugging your screens into different > ports every time you restart the machine. :) Correct :-) > Do you have an AMD graphics card, by any chance? Yes, AMD Radeon RX 6600 XT (ASUS). > Also are both monitors the same model? Or are they different? DisplayPort-0 and DisplayPort-1, which are the two monitors KScreen is confused about, are actually different models. DisplayPort-0 is a Dell U2717D and DisplayPort-1 is a Dell U2711. HDMI-A-0 is also a U2717D but KScreen is not confusing the two U2717D monitors. FYI also: `kscreen-doctor` doesn't show it, but the "Display Configuration" kcm "Identify" function shows the U2717Ds with unique serial numbers. The U2711 DOES NOT show a unique serial number, but I only have one of those monitors anyway. Therefore, as far as I can tell, there is no reason KScreen should be confused about this setup. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] Primary display setting does not persist
https://bugs.kde.org/show_bug.cgi?id=461822 Raman Gupta changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Raman Gupta --- (In reply to Nate Graham from comment #2) > Can you paste the output of `kscreen-doctor -o` when it's working properly, Output: 84 DisplayPort-0 enabled connected DisplayPort Modes: 89:2560x1440@60*! 90:1920x1200@60 91:2048x1080@60 92:2048x1080@24 93:1920x1080@60 94:1920x1080@50 95:1920x1080@60 96:1600x1200@60 97:1680x1050@60 98:1280x1024@75 99:1280x1024@60 100:1440x900@60 101:1280x800@60 102:1152x864@75 103:1280x720@60 104:1280x720@50 105:1280x720@60 106:1024x768@75 107:1024x768@60 108:800x600@75 109:800x600@60 110:720x576@50 111:720x480@60 112:720x480@60 113:640x480@75 114:640x480@60 115:640x480@60 116:720x400@70 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 85 DisplayPort-1 enabled connected primary DisplayPort Modes: 89:2560x1440@60*! 93:1920x1080@60 94:1920x1080@50 95:1920x1080@60 96:1600x1200@60 98:1280x1024@75 99:1280x1024@60 100:1440x900@60 102:1152x864@75 103:1280x720@60 104:1280x720@50 105:1280x720@60 106:1024x768@75 107:1024x768@60 108:800x600@75 109:800x600@60 110:720x576@50 111:720x480@60 112:720x480@60 113:640x480@75 114:640x480@60 115:640x480@60 116:720x400@70 117:1920x1200@60 118:1920x1080@60 119:1920x1080@24 120:1920x1080@24 121:1680x1050@60 122:1280x800@60 Geometry: 2560,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown primary Output: 86 DisplayPort-2 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 87 HDMI-A-0 enabled connected HDMI Modes: 89:2560x1440@60*! 90:1920x1200@60 91:2048x1080@60 92:2048x1080@24 93:1920x1080@60 94:1920x1080@50 95:1920x1080@60 96:1600x1200@60 97:1680x1050@60 98:1280x1024@75 99:1280x1024@60 100:1440x900@60 101:1280x800@60 102:1152x864@75 103:1280x720@60 104:1280x720@50 105:1280x720@60 106:1024x768@75 107:1024x768@60 108:800x600@75 109:800x600@60 110:720x576@50 111:720x480@60 112:720x480@60 113:640x480@75 114:640x480@60 115:640x480@60 116:720x400@70 Geometry: 5120,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown (BTW, I have no idea what Output 86 is) > and then again after rebooting when the Primary Display setting has gotten > reset? Thanks a lot! Output: 84 DisplayPort-0 enabled connected primary DisplayPort Modes: 89:2560x1440@60*! 90:1920x1200@60 91:2048x1080@60 92:2048x1080@24 93:1920x1080@60 94:1920x1080@50 95:1920x1080@60 96:1600x1200@60 97:1680x1050@60 98:1280x1024@75 99:1280x1024@60 100:1440x900@60 101:1280x800@60 102:1152x864@75 103:1280x720@60 104:1280x720@50 105:1280x720@60 106:1024x768@75 107:1024x768@60 108:800x600@75 109:800x600@60 110:720x576@50 111:720x480@60 112:720x480@60 113:640x480@75 114:640x480@60 115:640x480@60 116:720x400@70 Geometry: 0,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown primary Output: 85 DisplayPort-1 enabled connected DisplayPort Modes: 89:2560x1440@60*! 93:1920x1080@60 94:1920x1080@50 95:1920x1080@60 96:1600x1200@60 98:1280x1024@75 99:1280x1024@60 100:1440x900@60 102:1152x864@75 103:1280x720@60 104:1280x720@50 105:1280x720@60 106:1024x768@75 107:1024x768@60 108:800x600@75 109:800x600@60 110:720x576@50 111:720x480@60 112:720x480@60 113:640x480@75 114:640x480@60 115:640x480@60 116:720x400@70 117:1920x1200@60 118:1920x1080@60 119:1920x1080@24 120:1920x1080@24 121:1680x1050@60 122:1280x800@60 Geometry: 2560,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 86 DisplayPort-2 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown Output: 87 HDMI-A-0 enabled connected HDMI Modes: 89:2560x1440@60*! 90:1920x1200@60 91:2048x1080@60 92:2048x1080@24 93:1920x1080@60 94:1920x1080@50 95:1920x1080@60 96:1600x1200@60 97:1680x1050@60 98:1280x1024@75 99:1280x1024@60 100:1440x900@60 101:1280x800@60 102:1152x864@75 103:1280x720@60 104:1280x720@50 105:1280x720@60 106:1024x768@75 107:1024x768@60 108:800x600@75 109:800x600@60 110:720x576@50 111:720x480@60 112:720x480@60 113:640x480@75 114:640x480@60 115:640x480@60 116:720x400@70 Geometry: 5120,0 2560x1440 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 407519] Primary display setting does not persist
https://bugs.kde.org/show_bug.cgi?id=407519 --- Comment #5 from Raman Gupta --- (In reply to Nate Graham from comment #3) > Raman, can you also open a new bug report with your issue? Done so here: https://bugs.kde.org/show_bug.cgi?id=461822. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 461822] New: Primary display setting does not persist
https://bugs.kde.org/show_bug.cgi?id=461822 Bug ID: 461822 Summary: Primary display setting does not persist Classification: Plasma Product: KScreen Version: 5.25.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: rocketra...@gmail.com Target Milestone: --- SUMMARY In a multimonitor setup, the "Primary display" setting does not persist across logins. STEPS TO REPRODUCE 1. Connect two monitors to a computer, turn it on, and log into KDE. 2. In System Settings, select a different primary display and press "Apply". 3. Reboot and log into KDE. OBSERVED RESULT 4. Panels appear on the wrong monitors. Inspecting System Settings shows that this is because the primary display setting is back to the way it was originally. EXPECTED RESULT 4. Primary display setting should have persisted. Panels should have appeared on the correct monitors. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Platform: X11 On Fedora 36 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455974] Present windows with multiple monitors only shows windows on active display
https://bugs.kde.org/show_bug.cgi?id=455974 --- Comment #21 from Raman Gupta --- (In reply to Kirby from comment #19) > This is still an issue where a search a for an application via Present > Windows finds the window after filtering on the other monitor but is unable > to select it using Enter. @Kirby, did you end up creating a new issue for this? If so, can you link it here? Using the keyboard to select a window is an important use case for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403563] Memory leak in plasma desktop (plasmashell)
https://bugs.kde.org/show_bug.cgi?id=403563 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com --- Comment #16 from Raman Gupta --- This is the issue that comes up when Googling "plasmashell memory leak", so I'll post here. There are usually multiple root causes of these types of problems, but without better ways to debug / investigate these issues than "try it with this configuration" it is really hard for users to determine whether we are talking about the same issue or not. On my Fedora 36 system with 128 GB of real memory, systemd-oomd has killed plasmashell twice in two days for using almost 133 GB of memory (real memory + considerable swap). There is no conceivable situation in which plasmashell should be using that much memory. Oct 23 03:04:40 edison systemd-oomd[1888]: Killed /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service due to memory used (132956889088) / total (134229807104) and swap used (27105050624) / total (30064758784) being more than 90.00% Oct 23 03:04:40 edison systemd[2255]: plasma-plasmashell.service: systemd-oomd killed 199 process(es) in this unit. and then almost exactly 24 hours later: Oct 24 03:05:46 edison systemd-oomd[1888]: Killed /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service due to memory used (132685852672) / total (134229807104) and swap used (27061297152) / total (30064758784) being more than 90.00% Oct 24 03:05:46 edison systemd[2255]: plasma-plasmashell.service: systemd-oomd killed 156 process(es) in this unit. I do find it suspicious that both instances happened at almost exactly the same time overnight -- the cron log does not show any process triggering at or around that time. If there is a way to effectively debug this sort of thing, that would be helpful. I don't use slideshow wallpaper. Output of qdbus supportInformation: https://invent.kde.org/-/snippets/2387 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450068] Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else
https://bugs.kde.org/show_bug.cgi?id=450068 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #45 from Raman Gupta --- On 5.25.4 with u2f PAM (Yubikey), not even the `unlock-sessions` workaround worked. Doing unlock sessions just resulted in a black screen with a block cursor moving and a random character in green on the screen. No amount of locking and unlocking via loginctl got it out of this state. I even unplugged the Yubikey to no avail. Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.6-200.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 24 × 12th Gen Intel® Core™ i9-12900KS Memory: 125.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #44 from Raman Gupta --- Same problem here, using u2f PAM with a Yubikey to login. Have 3 monitors, using X11. Like other users, `/usr/lib/kscreenlocker_greet --testing` has the same behavior. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors
https://bugs.kde.org/show_bug.cgi?id=456210 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455974] Present windows with multiple monitors only shows windows on active display
https://bugs.kde.org/show_bug.cgi?id=455974 Raman Gupta changed: What|Removed |Added Version|5.25.2 |5.25.4 --- Comment #13 from Raman Gupta --- Man, this bug is annoying. Totally breaks my workflow. How does breaking fundamental stuff like this get through testing? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455974] Present windows with multiple monitors only shows windows on active display
https://bugs.kde.org/show_bug.cgi?id=455974 --- Comment #10 from Raman Gupta --- The other related behavior that has changed is that when doing "Toggle Present Windows (Window class)", it used to show all the windows, but only if they were on the same desktop. i.e.: old (and IMO correct behavior): same screen, same desktop: yes different screen, same desktop: yes same screen, different desktop: no different screen, different desktop: no current behavior: same screen, same desktop: yes different screen, same desktop: no same screen, different desktop: yes different screen, different desktop: no IOW, the logic used to show the window as long as it was on the same desktop regardless of screen, and now it shows the window as long as it is on the same screen regardless of desktop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455974] Present windows with multiple monitors only shows windows on active display
https://bugs.kde.org/show_bug.cgi?id=455974 --- Comment #9 from Raman Gupta --- Same problem here on: Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.3 Kernel Version: 5.18.11-200.fc36.x86_64 (64-bit) Graphics Platform: X11 This is a regression as this has previously been working fine for years. Have tried Chrome and IntelliJ IDEA and both applications only present their windows on the active screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455974] Present windows with multiple monitors only shows windows on active display
https://bugs.kde.org/show_bug.cgi?id=455974 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 407519] Primary display setting does not persist
https://bugs.kde.org/show_bug.cgi?id=407519 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com --- Comment #2 from Raman Gupta --- Same thing here. Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.3 Kernel Version: 5.18.11-200.fc36.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455066] Windows don't remember what screen they were on if that screen is disconnected and reconnected
https://bugs.kde.org/show_bug.cgi?id=455066 --- Comment #6 from Raman Gupta --- Please make sure this handles the use case I mentioned in https://bugs.kde.org/show_bug.cgi?id=456681 in which multiple screens are turned off and on in a very short period of time, which might cause multiple screen disconnects before everything is restored back to normal. An example of what would cause this: a power blip. IMO, a delay of a few seconds in which KDE doesn't move windows at all is preferable to moving them instantaneously when a screen disappears, and then again when another screen disappears, and then trying to restore all that back to the original configuration when both screens reappear. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 456681] New: Kscreen is too eager with changing display configuration and moving windows around
https://bugs.kde.org/show_bug.cgi?id=456681 Bug ID: 456681 Summary: Kscreen is too eager with changing display configuration and moving windows around Product: KScreen Version: 5.25.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: rocketra...@gmail.com Target Milestone: --- SUMMARY There are two situations in which I find KScreen is way too eager to change display configuration, which then causes windows to shift in strange ways. Scenario 1) one of several monitors is turned off by accident. It is immediately turned back on, but kscreen has already messed up my screen layouts by trying to re-arrange all my windows onto the two monitors that are still on. This actually happens to me very often because of the where the power button on one of my monitors is. Scenario 2) a power blip causes multiple monitors to turn off simultaneously (assume the monitors are not on the UPS, the main computer is, not an ideal scenario but not uncommon with an underpowered UPS and multiple monitors). In both cases, kscreen very quickly tries to re-arrange windows on the screen, even in the second case where all 3 monitors go off simultaneously, kscreen re-arranges windows in the millisecond timing differences between the monitors turning off. Furthermore, the re-arrangement doesn't even make sense -- I end up with some windows that are halfway across two monitors and other strange things like that. Both scenarios could be handled by making monitor reconfiguration an optional user-driven item -- for example, if kscreen detects a change in screens, it could pop up a dialog box on any screen which is still working with the message: "A screen change configuration was detected, do you want to reconfigure the display?" with an optional count-down to automatically reconfigure within 30 seconds or something like that. Alternately, kscreen could remember the previous window configuration, and if the display configuration returns to the previous setting within a certain time-frame (say 30s), then kscreen could automatically return windows to their previous positions. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 36 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 453280] kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 --- Comment #13 from Raman Gupta --- (In reply to Raman Gupta from comment #11) > On Fedora, kded appears to run via systemd user unit, so the "right" way to > do it appears to be : > > systemd --user restart plasma-kded Oops, that should be: systemctl --user restart plasma-kded -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 453280] kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 --- Comment #11 from Raman Gupta --- (In reply to kdebugs from comment #8) > (In reply to Mikiya Okuno from comment #7) > > The problem is really irritating. I have to restart my machine every time > > when the session is running out. Since the maximum number of X11 sessions > > available is 256, the session runs out by 42 monitor power cycles at > > maximum. Other applications also open X11 sessions, so it runs out even > > earlier. > > Irritating indeed, but you can avoid having to restart the whole computer > with just restarting kded5 > Personally I kill the process and start kded5 with kstart5, but I'm not sure > if this is the "correct" method or not > but it seemingly works without any negative effects On Fedora, kded appears to run via systemd user unit, so the "right" way to do it appears to be : systemd --user restart plasma-kded -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 453280] kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 --- Comment #5 from Raman Gupta --- I believe the issue is more related to monitors going into a power-saving mode rather than the screen locking -- 5 connections were leaked this morning when my monitors were woken up, but before the lock screen activated. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 453280] kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 --- Comment #4 from Raman Gupta --- Just FYI -- my leak *might* also be related to the lock screen and/or monitors sleeping, but the behavior on my machine seems to be different than with Phil Hord -- using the same script as in comment #2, with the computer locked overnight, 5 connections were leaked, but only when the monitors woke up / computer was unlocked at 08:44:13 -- none were leaked while the monitors were sleeping / lock screen was active: Computer went to sleep at approximately 6:30 pm, woke up at 8:44 am: 124 Mon May 9 05:13:53 PM EDT 2022 129 Tue May 10 08:44:13 AM EDT 2022 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 453280] New: kded5 leaks X-Window connections: Maximum number of clients reached
https://bugs.kde.org/show_bug.cgi?id=453280 Bug ID: 453280 Summary: kded5 leaks X-Window connections: Maximum number of clients reached Product: frameworks-kded Version: 5.91.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: rocketra...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY I started receiving the error "Maximum number of clients reached" when trying to open new X-based programs. Upon investigation, I saw that `kded5` was using 146 connections -- the next highest program was using 8 [1]. Restarting kded5 solved the problem. [1] I used the script found here to identify this: https://unix.stackexchange.com/a/700637/11249 STEPS TO REPRODUCE 1. Leave desktop running for a few days/weeks, until X reports "Maximum number of clients reached" when trying to start a new window. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.20-200.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 32 × AMD Ryzen Threadripper 1950X 16-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 590 Series ADDITIONAL INFORMATION It appears I'm not the only one experiencing this probem. See also: https://unix.stackexchange.com/questions/700366/kded-taking-up-x-client-connections -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396359] crash in QQuickItemPrivate::addToDirtyList
https://bugs.kde.org/show_bug.cgi?id=396359 --- Comment #30 from Raman Gupta --- The crash (at least the one reported in dup issue https://bugs.kde.org/show_bug.cgi?id=446993) no longer happens for me on: Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.12-200.fc35.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444742] Plasma crash right after login
https://bugs.kde.org/show_bug.cgi?id=444742 --- Comment #13 from Raman Gupta --- The crash (at least the one reported in dup issue https://bugs.kde.org/show_bug.cgi?id=446993) no longer happens for me on: Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.12-200.fc35.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440825] open at mouse location not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=440825 --- Comment #11 from Raman Gupta --- (In reply to George Diamantopoulos from comment #10) > i.e. in my case, hovering over an xwayland window is not enough. Do you have "Focus follows mouse" enabled? My Window activation policy is "Focus follows mouse (mouse precedence)" and also "Active screen follows mouse". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444742] Plasma crash right after login
https://bugs.kde.org/show_bug.cgi?id=444742 --- Comment #11 from Raman Gupta --- (In reply to burneddi from comment #10) > It still crashes for me even though it runs as a systemd service. Not every > time, but maybe 70% of the time when my monitors wake up. I can confirm this as well. I still do get crashes on monitor wake-up, even when running as a systemd service. You would think crashers with backtraces would be easy to fix... -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357288] Setting "Screen Energy Saving" in "Energy Saving" config has no effect
https://bugs.kde.org/show_bug.cgi?id=357288 Raman Gupta changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #16 from Raman Gupta --- As the OP I don't have this issue on recent KDE versions, so I'll go ahead and close. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440825] open at mouse location not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=440825 --- Comment #8 from Raman Gupta --- Same thing here. Interestingly, it does work when the mouse hovers over a window rendered via XWayland. However, windows rendered by Wayland (or mouse over the desktop) do not affect the Yakuake window placement. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440825] open at mouse location not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=440825 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444742] Plasma crash right after login
https://bugs.kde.org/show_bug.cgi?id=444742 --- Comment #9 from Raman Gupta --- (In reply to burneddi from comment #7) > at least on Fedora the easiest way to restart Plasmashell is with "systemctl > --user restart plasma-plasmashell" On Fedora, is this a new approach to running Plasmashell? Interestingly, if I run plasmashell this way, as opposed to just restarting it the way I always used to (`kstart plasmashell &> /dev/null`) it no longer crashes on monitor wakeup. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444742] Plasma crash right after login
https://bugs.kde.org/show_bug.cgi?id=444742 --- Comment #8 from Raman Gupta --- I have a multi-monitor setup also. 3 monitors, all the same resolution. 2/3 are a different model than the other (though same brand, Dell). In my case the monitors do wake up at different times as well, though in my case that seems to more be a function of the video card than the monitor model, and there is not a significant difference between them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444742] Plasma crash right after login
https://bugs.kde.org/show_bug.cgi?id=444742 --- Comment #5 from Raman Gupta --- One piece of important information, at least in my case, is that the crash happens when my monitors wake up, not at the actual login. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446993] Crash on wakeup
https://bugs.kde.org/show_bug.cgi?id=446993 Raman Gupta changed: What|Removed |Added Status|NEEDSINFO |REOPENED Ever confirmed|0 |1 Resolution|BACKTRACE |--- --- Comment #3 from Raman Gupta --- Information provided as requested. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446993] Crash on wakeup
https://bugs.kde.org/show_bug.cgi?id=446993 --- Comment #2 from Raman Gupta --- Created attachment 144584 --> https://bugs.kde.org/attachment.cgi?id=144584=edit Result of `thread apply all backtrace` after SEGFAULT I have attached the result of `thread apply all backtrace` after the segfault, captured via gdb. This is the output of gdb before the backtrace attached: ``` Thread 96 "QSGRenderThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f4ce37fe640 (LWP 871408)] 0x7f4e1342813b in QQuickWindow::maybeUpdate (this=0x55f606338f60) at items/qquickwindow.cpp:3930 Downloading -0.00 MB source file /usr/src/debug/qt5-qtdeclarative-5.15.2-8.fc35.x86_64/src/quick/items/qquickwindow.cpp 3930if (d->renderControl) (gdb) Continuing. [Detaching after fork from child process 871546] [Detaching after fork from child process 871548] Thread 1 "plasmashell" received signal SIGSTOP, Stopped (signal). [Switching to Thread 0x7f4e0d17fe00 (LWP 868071)] __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55f60d096690) at futex-internal.c:57 Downloading -0.00 MB source file /usr/src/debug/glibc-2.34-12.fc35.x86_64/nptl/futex-internal.c 57 return INTERNAL_SYSCALL_CANCEL (futex_time64, futex_word, op, expected, ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446993] New: Crash on wakeup
https://bugs.kde.org/show_bug.cgi?id=446993 Bug ID: 446993 Summary: Crash on wakeup Product: plasmashell Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: rocketra...@gmail.com Target Milestone: 1.0 SUMMARY I have a desktop on A/C power with an APC UPS. The power energy settings are default -- 10 min monitor sleep on A/C. When I leave my computer the screen locks and the displays go to sleep. When I wake up my screens by moving my mouse, plasmashell crashes. Note that it crashes at wake time, NOT at unlock time. STEPS TO REPRODUCE 1. Lock screen and wait for displays to sleep 2. Wake up screen OBSERVED RESULT Plasmashell crashes. I tried to follow the directions to get a stack trace but it didn't work for me. EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.6-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 348868] Applications using KWallet keep prompting unexisting wallet
https://bugs.kde.org/show_bug.cgi?id=348868 --- Comment #4 from Raman Gupta --- I am not the OP but I no longer have this issue. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 421910] plasma-pa breaks if Pulseaudio server is restarted
https://bugs.kde.org/show_bug.cgi?id=421910 --- Comment #1 from Raman Gupta --- Workaround: kquitapp5 plasmashell && sleep 5 && kstart plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 421910] New: plasma-pa breaks if Pulseaudio server is restarted
https://bugs.kde.org/show_bug.cgi?id=421910 Bug ID: 421910 Summary: plasma-pa breaks if Pulseaudio server is restarted Product: plasma-pa Version: 5.17.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: rocketra...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- When the pulseaudio server crashes or is restarted, the plasma-pa plasmoid breaks until plasma is restarted. STEPS TO REPRODUCE 1. Restart the pulseaudio server OBSERVED RESULT The pulse-pa plasmoid now shows a speaker icon with a red cross symbol. When opening the plasmoid details, no streams or devices are shown. EXPECTED RESULT The plasmoid should reconnect to the new server and resume operation normally. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 411441] Dolphin makes kdeinit crash when closed
https://bugs.kde.org/show_bug.cgi?id=411441 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 403843] Libinput touchpad KCM needs a scroll speed setting
https://bugs.kde.org/show_bug.cgi?id=403843 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403842] Libinput mouse KCM lost the scroll speed setting that was present in the evdev version
https://bugs.kde.org/show_bug.cgi?id=403842 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)
https://bugs.kde.org/show_bug.cgi?id=373907 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 385882] Yakuake Wayland: when launching Yakuake the second time it appears in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=385882 Raman Gupta changed: What|Removed |Added CC||rocketra...@gmail.com --- Comment #8 from Raman Gupta --- Similar issues here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 346558] Folder View resets to Desktop after Reboot
https://bugs.kde.org/show_bug.cgi?id=346558 --- Comment #12 from Raman Gupta --- This hasn't happened to me in a long time. I wasn't the OP but I'd feel confident in saying this is fixed. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357288] Setting "Screen Energy Saving" in "Energy Saving" config has no effect
https://bugs.kde.org/show_bug.cgi?id=357288 Raman Gupta <rocketra...@gmail.com> changed: What|Removed |Added Version|5.8.4 |5.9.4 --- Comment #10 from Raman Gupta <rocketra...@gmail.com> --- Now on Plasma 5.9.4, I can see in the battery manager applet that Power Management is suppressed by a tab in google-chrome-stable. The tab doesn't exist, and Chrome isn't even running (confirmed with ps as root), but hey, at least now there is some information that explains why the energy saving isn't working. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361497] High memory usage of plasma shell when vmvare workstation is running
https://bugs.kde.org/show_bug.cgi?id=361497 --- Comment #4 from Raman Gupta <rocketra...@gmail.com> --- Following on my last comment, I believe I can confirm the issue with vmware and plasmashell, at least on my machine, is related to the vmware-tray process. I started vmware and immediately killed the vmware-tray process on my Fedora host. Since that time, no more CPU issues with plasmashell. I'd like to hear from the OP whether or not that is the case for him also. Now I suspect that vmware is doing something naughty related to the tray... but, I don't believe any program should be able to "break" plasmashell using any tray APIs, no matter what they are. Allowing this is essentially allowing a denial of service attack on plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361497] High memory usage of plasma shell when vmvare workstation is running
https://bugs.kde.org/show_bug.cgi?id=361497 --- Comment #3 from Raman Gupta <rocketra...@gmail.com> --- I have the same behavior on Fedora 24 with KDE Plasma 5.8.6, Frameworks 5.31.0, QT 5.6.2, and VMWare 12.5. There are other reports of this as well: https://forum.manjaro.org/t/plasmashell-kde-high-load-over-my-cpu/8645/5 One commenter at https://superuser.com/questions/1118866/high-load-over-my-cpu-and-high-temperature-when-running-plasmashell had an interesting theory, but I have not yet tested it: > FWIW, we ran into this at work and it turns out it's the vmware tray icon. If > you kill the vmware-tray process after you start up the VMs, then everything > is fine. There is an option to say that you don't ever want the icon, but > that doesn't appear to be honored and VMWare fires it up anyways. CPU usage increases to about 60% on plasmashell, with a significant percentage on the Xorg process and on the VMware process, even with an idle VM. Shutting down VMWare has no affect, but restarting plasma after shutting down VMWare fixes the issue. The display becomes sluggish until plasmashell is restarted. -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 375011] New: Crash when opening a Word docx file
https://bugs.kde.org/show_bug.cgi?id=375011 Bug ID: 375011 Summary: Crash when opening a Word docx file Product: calligrawords Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: rocketra...@gmail.com Target Milestone: --- Application: calligrawords (2.9.11) KDE Platform Version: 4.14.26 Qt Version: 4.8.7 Operating System: Linux 4.8.15-200.fc24.x86_64 x86_64 Distribution: "Fedora release 24 (Twenty Four)" -- Information about the crash: - What I was doing when the application crashed: I opened a Word docx file. Unfortunately I cannot attach it here as it has private information. -- Backtrace: Application: Calligra Words (calligrawords), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7f698266192c in QTextLine::y() const () at /lib64/libQtGui.so.4 #7 0x7f697ffd8e02 in KoTextDocumentLayout::positionAnchorTextRanges(int, int, QTextDocument const*) () at /lib64/libkotextlayout.so.14 #8 0x7f697ffc1683 in KoTextLayoutArea::layoutBlock(FrameIterator*) () at /lib64/libkotextlayout.so.14 #9 0x7f697ffc40cb in KoTextLayoutArea::layout(FrameIterator*) () at /lib64/libkotextlayout.so.14 #10 0x7f697ffd6ded in KoTextLayoutRootArea::layoutRoot(FrameIterator*) () at /lib64/libkotextlayout.so.14 #11 0x7f697ffda15d in KoTextDocumentLayout::doLayout() () at /lib64/libkotextlayout.so.14 #12 0x7f697ffda7e8 in KoTextDocumentLayout::layout() () at /lib64/libkotextlayout.so.14 #13 0x7f69814e0db1 in QObject::event(QEvent*) () at /lib64/libQtCore.so.4 #14 0x7f69823f2edc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #15 0x7f69823f9ddc in QApplication::notify(QObject*, QEvent*) () at /lib64/libQtGui.so.4 #16 0x7f698662cdf5 in KoApplication::notify(QObject*, QEvent*) () at /lib64/libkomain.so.14 #17 0x7f69814c6eed in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQtCore.so.4 #18 0x7f69814ca556 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQtCore.so.4 #19 0x7f69814f72ee in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQtCore.so.4 #20 0x7f697b4786ba in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #21 0x7f697b478a70 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #22 0x7f697b478b1c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #23 0x7f69814f745e in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtCore.so.4 #24 0x7f698249b5b6 in QGuiEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQtGui.so.4 #25 0x7f69814ca89f in QCoreApplication::processEvents(QFlags) () at /lib64/libQtCore.so.4 #26 0x7f69844f5d4f in KoProgressUpdater::update() () at /lib64/libkowidgetutils.so.14 #27 0x7f69814db090 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #28 0x7f69814db090 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /lib64/libQtCore.so.4 #29 0x7f69844f7251 in KoUpdater::sigProgress(int) () at /lib64/libkowidgetutils.so.14 #30 0x7f69844f72e7 in KoUpdater::setProgress(int) () at /lib64/libkowidgetutils.so.14 #31 0x7f6986638cbb in KoDocument::openFile() () at /lib64/libkomain.so.14 #32 0x7f6986641cf9 in KoDocument::openUrlInternal(KUrl const&) () at /lib64/libkomain.so.14 #33 0x7f6986642128 in KoDocument::openUrl(KUrl const&) () at /lib64/libkomain.so.14 #34 0x7f698664c39c in KoMainWindow::openDocumentInternal(KUrl const&, KoPart*, KoDocument*) () at /lib64/libkomain.so.14 #35 0x7f698664c941 in KoMainWindow::openDocument(KoPart*, KUrl const&) () at /lib64/libkomain.so.14 #36 0x7f6986629935 in KoApplication::start() () at /lib64/libkomain.so.14 #37 0x7f69868e2440 in kdemain () at /lib64/libkdeinit4_calligrawords.so #38 0x7f69804c9731 in __libc_start_main () at /lib64/libc.so.6 #39 0x55a24a8fe9b9 in _start () The reporter indicates this bug may be a duplicate of or related to bug 372670. Possible duplicates by query: bug 372670. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356706] The system activity manager insists on opening partially off-screen
https://bugs.kde.org/show_bug.cgi?id=356706 --- Comment #6 from Raman Gupta <rocketra...@gmail.com> --- Created attachment 102736 --> https://bugs.kde.org/attachment.cgi?id=102736=edit Output of xprop Output of xprop attached. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356706] The system activity manager insists on opening partially off-screen
https://bugs.kde.org/show_bug.cgi?id=356706 --- Comment #5 from Raman Gupta <rocketra...@gmail.com> --- Created attachment 102735 --> https://bugs.kde.org/attachment.cgi?id=102735=edit Screenshot Screenshot of window just after it opens via ksnapshot. Note its location on the left monitor, which is smaller than the center and right monitors. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356706] The system activity manager insists on opening partially off-screen
https://bugs.kde.org/show_bug.cgi?id=356706 Raman Gupta <rocketra...@gmail.com> changed: What|Removed |Added Version|5.7.5 |5.8.4 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357288] Setting "Screen Energy Saving" in "Energy Saving" config has no effect
https://bugs.kde.org/show_bug.cgi?id=357288 Raman Gupta <rocketra...@gmail.com> changed: What|Removed |Added Version|5.7.3 |5.8.4 --- Comment #9 from Raman Gupta <rocketra...@gmail.com> --- Still the same issue on Plasma 5.8.4, QT 5.6.2 (Fedora 24). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356706] The system activity manager insists on opening partially off-screen
https://bugs.kde.org/show_bug.cgi?id=356706 --- Comment #3 from Raman Gupta <rocketra...@gmail.com> --- Still happening on Plasma 5.8.4, QT 5.6.2. (In reply to Valeriy Malov from comment #1) > I have a dual screen setup, systemmonitor always opens up on a secondary > screen, seems to be related bug? I think it is the same issue. If the screen opened on my main center monitor, it would be the correct size and position within that monitor. However, it opens on the wrong monitor. It seems as if KDE is using the correct monitor to calculate the window's size and x,y position (relative to that monitor), but then actually placing the window on the wrong monitor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356706] The system activity manager insists on opening partially off-screen
https://bugs.kde.org/show_bug.cgi?id=356706 Raman Gupta <rocketra...@gmail.com> changed: What|Removed |Added Version|5.7.3 |5.7.5 --- Comment #2 from Raman Gupta <rocketra...@gmail.com> --- Still happens in 5.7.5, QT 5.6.1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process
https://bugs.kde.org/show_bug.cgi?id=371889 --- Comment #17 from Raman Gupta <rocketra...@gmail.com> --- Here is another report that seems related to the virtualization mentioned in comment #4, this time with VMWare: https://bugs.kde.org/show_bug.cgi?id=361497 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361497] High memory usage of plasma shell when vmvare workstation is running
https://bugs.kde.org/show_bug.cgi?id=361497 Raman Gupta <rocketra...@gmail.com> changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371889] High CPU and memory usage in plasmashell process
https://bugs.kde.org/show_bug.cgi?id=371889 Raman Gupta <rocketra...@gmail.com> changed: What|Removed |Added CC||rocketra...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357288] Setting "Screen Energy Saving" in "Energy Saving" config has no effect
https://bugs.kde.org/show_bug.cgi?id=357288 Raman Gupta <rocketra...@gmail.com> changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|UPSTREAM|--- --- Comment #7 from Raman Gupta <rocketra...@gmail.com> --- Well, this problem is back again, for no apparent reason. Simply applied some updates (kernel 4.7.3) and rebooted, and now monitor power-save / sleep again does not work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359426] Plasmashell process uses a huge amount of memory making the computer overloaded and KDE unresponsive
https://bugs.kde.org/show_bug.cgi?id=359426 --- Comment #8 from Raman Gupta <rocketra...@gmail.com> --- Interesting: I haven't had this issue recently, even though Plasmashell and QT are both still the same version as before (5.7.3 and 5.6.1 respectively), and as far as I know I haven't changed any settings at all. Though I have updated a few other components, none of which seem remotely relevant, except *maybe* the following: * kernel (now at 4.7.3) * ibus (now at 1.5.11) * chromium-libs-media (now at 52.0.2743.116-10) -- You are receiving this mail because: You are watching all bug changes.
