[kwin] [Bug 483994] New: kwin: wrong window size after disabling external monitor
https://bugs.kde.org/show_bug.cgi?id=483994
Bug ID: 483994
Summary: kwin: wrong window size after disabling external
monitor
Classification: Plasma
Product: kwin
Version: 5.27.10
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: ho...@schirmeier.com
Target Milestone: ---
Created attachment 167466
--> https://bugs.kde.org/attachment.cgi?id=167466&action=edit
Firefox showing button at viewport bottom right (before disabling ext. monitor
/ after applying workaround)
SUMMARY
After enabling ("Extend to right") and again disabling an external monitor,
applications get the wrong impression what the current vertical viewport size
actually is, although the screen resolution seems right. For example, a
maximized Firefox window displaying a website with a button at the "bottom" of
the current viewport does not show the button in the right place anymore, but
at an even lower position behind the Plasma taskbar (see attached screenshots).
Similarly, a maximized Konsole terminal shows its bottom-most text line behind
the Plasma taskbar.
As a workaround, switching screen resolutions back and forth fixes the problem
temporarily, until again an external monitor is involved:
xrandr --screen 0 --size 1680x1050
sleep 1
xrandr --screen 0 --size 1920x1080
STEPS TO REPRODUCE
1. Attach external monitor via HDMI that has a higher resolution (here:
2560x2880) than the primary monitor (here: 1920x1080)
2. Enable external monitor, "Extend to right"
3. Start a Konsole terminal, maximize on primary monitor, repeatedly press
ENTER to reach the bottom terminal line
4. Disable external monitor, "Switch to laptop screen"
OBSERVED RESULT
Bottom terminal line (and cursor) isn't visible anymore but "behind" the Plasma
taskbar
EXPECTED RESULT
Bottom terminal line (and cursor) should be visible right above the Plasma
taskbar
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.27.10 (Debian testing: 4:5.27.10-3)
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.10
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 483994] kwin: wrong window size after disabling external monitor
https://bugs.kde.org/show_bug.cgi?id=483994 --- Comment #1 from Horst Schirmeier --- Created attachment 167468 --> https://bugs.kde.org/attachment.cgi?id=167468&action=edit Firefox showing button at viewport bottom right (after disabling ext. screen), actually rendering it behind taskbar -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483994] kwin: wrong window size after disabling external monitor
https://bugs.kde.org/show_bug.cgi?id=483994 --- Comment #2 from Horst Schirmeier --- Website for reproducers: https://www.w3schools.com/css/tryit.asp?filename=trycss_position_fixed (the Konsole variant is even easier to reproduce) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439332] Ghost windows and popups
https://bugs.kde.org/show_bug.cgi?id=439332 Horst Schirmeier changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||ho...@schirmeier.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 441977] After cloning, kscreen does not return to original resolution when using "Switch to laptop screen"
https://bugs.kde.org/show_bug.cgi?id=441977 --- Comment #2 from Horst Schirmeier --- Plasma Wayland exhibits a differently unexpected behavior: With "Unify outputs", both displays stay at their original (native) resolution. The laptop screen is still at 2560x1440, the external FHD monitor at 1920x1080 and mirroring a cutout of the laptop screen. When using "Switch to laptop screen" then, the internal screen stays at its native resolution; so in a way, the state afterwards is better with Wayland, but "Unify outputs" doesn't do what I expect. Guess that's a different bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 441977] After cloning, kscreen does not return to original resolution when using "Switch to laptop screen"
https://bugs.kde.org/show_bug.cgi?id=441977 --- Comment #3 from Horst Schirmeier --- Disregard that. My KDE/Plasma setup seems to be broken since Ubuntu's 5.22.4->5.22.5 recent update. I'll report on Wayland again when this is smoothed out. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 441977] After cloning, kscreen does not return to original resolution when using "Switch to laptop screen"
https://bugs.kde.org/show_bug.cgi?id=441977 --- Comment #4 from Horst Schirmeier --- (In reply to Horst Schirmeier from comment #2) > Plasma Wayland exhibits a differently unexpected behavior: With "Unify > outputs", both displays stay at their original (native) resolution. The > laptop screen is still at 2560x1440, the external FHD monitor at 1920x1080 > and mirroring a cutout of the laptop screen. > > When using "Switch to laptop screen" then, the internal screen stays at its > native resolution; so in a way, the state afterwards is better with Wayland, > but "Unify outputs" doesn't do what I expect. Guess that's a different bug. This differently broken behavior on Xwayland persists. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 441977] After cloning, kscreen does not return to original resolution when using "Switch to laptop screen"
https://bugs.kde.org/show_bug.cgi?id=441977 --- Comment #5 from Horst Schirmeier --- Also happens from a "clean" user account. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 442874] New: "Unify outputs" doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=442874 Bug ID: 442874 Summary: "Unify outputs" doesn't work on Wayland Product: KScreen Version: 5.22.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: libkscreen Assignee: kscreen-bugs-n...@kde.org Reporter: ho...@schirmeier.com Target Milestone: --- Created attachment 141855 --> https://bugs.kde.org/attachment.cgi?id=141855&action=edit Photo with both screens SUMMARY When attaching an external monitor with lower resolution (laptop internal: 2560x1440, external/HDMI: 1920x1080) and using "Unify outputs" on Wayland, outputs don't get unified but the external monitor's contents are shown in a kind-of window in the upper left corner of the internal monitor's screen. Note this works fine with Xorg; I can only reproduce this with Wayland. STEPS TO REPRODUCE 1. Run KDE in Wayland. Attach external monitor with FHD resolution. 2. Invoke kscreen, "Unify outputs". OBSERVED RESULT Internal monitor stays at original resolution, external monitor lights up. External monitor's display contents are shown in a subarea of the internal monitor. See attached screenshot(s). EXPECTED RESULT Both screens go to the same resolution and show the same content. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 441977] After cloning, kscreen does not return to original resolution when using "Switch to laptop screen"
https://bugs.kde.org/show_bug.cgi?id=441977 --- Comment #6 from Horst Schirmeier --- (In reply to Horst Schirmeier from comment #2) > When using "Switch to laptop screen" then, the internal screen stays at its > native resolution; so in a way, the state afterwards is better with Wayland, > but "Unify outputs" doesn't do what I expect. Guess that's a different bug. Reported as bug #442874. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 442874] "Unify outputs" doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=442874 --- Comment #3 from Horst Schirmeier --- Created attachment 141942 --> https://bugs.kde.org/attachment.cgi?id=141942&action=edit output of kscreen-doctor -o -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 442874] "Unify outputs" doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=442874 --- Comment #4 from Horst Schirmeier --- Created attachment 141943 --> https://bugs.kde.org/attachment.cgi?id=141943&action=edit screen shot of the kscreen dialog (page 1) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 442874] "Unify outputs" doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=442874 --- Comment #5 from Horst Schirmeier --- Created attachment 141944 --> https://bugs.kde.org/attachment.cgi?id=141944&action=edit screen shot of the kscreen dialog (page 2) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345670] ctrl-alt-t konsole example not starting on top
https://bugs.kde.org/show_bug.cgi?id=345670 --- Comment #8 from Horst Schirmeier --- I haven't seen this in a long time; not reproducible with Plasma 5.22.5. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 442874] "Unify outputs" doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=442874 --- Comment #7 from Horst Schirmeier --- (In reply to Méven Car from comment #6) > Two screens may not be able to render at the same resolution. > Here kscreen-doctor shows your laptop screens can only handle 2560*1440 > resolution. This is a regression in Ubuntu 21.10. It worked perfectly before. xrandr shows a very long list of possible resolutions of the laptop screen, including 1920x1200 and 1920x1080 (the native resolution of the external screen). > One could tweak the scale of the laptop screen so that its resolution > matches the smaller screen logical size. > In this case, you'd need a 1.3 on the biggest screen which is not a > valid scale factor. > > You'd need to scale down the external screen as well to find a matching > resolutions which is most likely not a satisfying solution. > > So your situation and the attachment > https://bugsfiles.kde.org/attachment.cgi?id=141944 shows the expected result > in this case. > > You will see that kwin still maximizes windows in the shared area between > screens. I disagree; this worked before, and should continue to work; and the hardware isn't the limiting factor here. > Just to make sure what is the output of `drm_info` ? I'll add an attachment. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 442874] "Unify outputs" doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=442874 --- Comment #8 from Horst Schirmeier --- Created attachment 142310 --> https://bugs.kde.org/attachment.cgi?id=142310&action=edit output of drm_info I concur that drm_info shows only one single possible resolution for the internal screen -- 2560x1440. However, cloning does work correctly when using X11. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 442874] "Unify outputs" doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=442874 --- Comment #9 from Horst Schirmeier --- Created attachment 142311 --> https://bugs.kde.org/attachment.cgi?id=142311&action=edit output of xrandr drm_info ran from an X11 session also claims the internal screen can only do 2560x1440. However, xrandr clearly shows the internal screen can run at many resolutions, including 1920x1008, and can 1:1 mirror an external FHD screen. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 441977] After cloning, kscreen does not return to original resolution when using "Switch to laptop screen"
https://bugs.kde.org/show_bug.cgi?id=441977 Horst Schirmeier changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 442874] "Unify outputs" doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=442874 --- Comment #11 from Horst Schirmeier --- mesa/drm bug report: https://gitlab.freedesktop.org/mesa/drm/-/issues/69 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 442874] "Unify outputs" doesn't work on Wayland
https://bugs.kde.org/show_bug.cgi?id=442874 Horst Schirmeier changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|UPSTREAM|--- --- Comment #12 from Horst Schirmeier --- The DRM people are directing me back here: > drm_info [...] just reports whatever the kernel advertises. IIRC xrandr adds > a bunch of "default" modes even if the monitor doesn't support them. > > Seems like what you're looking for is custom modes in KWin. Please fill a > feature request there. How should I proceed? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 246196] When filling in forms, make it possible to set the font size of the forms
https://bugs.kde.org/show_bug.cgi?id=246196 Horst Schirmeier changed: What|Removed |Added CC||ho...@schirmeier.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 441977] New: After cloning, kscreen does not return to original resolution when using "Switch to laptop screen"
https://bugs.kde.org/show_bug.cgi?id=441977 Bug ID: 441977 Summary: After cloning, kscreen does not return to original resolution when using "Switch to laptop screen" Product: KScreen Version: 5.22.4 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: ho...@schirmeier.com Target Milestone: --- SUMMARY When I clone my laptop screen (2560x1440) to an HDMI-connected TV (FHD), both displays go to FHD. When disabling clone mode by using kscreen's "Switch to laptop screen", the external display is disabled as expected, but the laptop display stays at FHD instead of going back to 2560x1440. This is a regression. STEPS TO REPRODUCE - attach external Full-HD monitor (e.g. via HDMI) - use kscreen to "Unify outputs" (Fn+F7 on my Lenovo T460p, or using the "Display Configuration" tray applet) - internal monitor is now down to 1920x1080, showing the same content as the external one - use kscreen to "Switch to laptop screen" OBSERVED RESULT (since Ubuntu 21.10, i.e. the kscreen 5.21.4 -> 5.22.4 transition): - external monitor goes black - internal monitor stays at 1920x1080 EXPECTED RESULT (seen up to and including Ubuntu 21.04, i.e. kscreen 5.21.4): - external monitor goes black - internal monitor returns to native resolution (2560x1440 in my case) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.10 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/1939377 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419745] New: WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows 10 client
https://bugs.kde.org/show_bug.cgi?id=419745
Bug ID: 419745
Summary: WiFi hotspot with WPA/WPA2 Personal security doesn't
work with Windows 10 client
Product: systemsettings
Version: 5.18.4
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_networkmanagement
Assignee: jgrul...@redhat.com
Reporter: ho...@schirmeier.com
CC: plasma-b...@kde.org
Target Milestone: ---
When I create a shared WiFi ("hotspot") in the "Connections - System Settings
Module" with enabled WPA/WPA2 security, I cannot get Windows 10 clients to
connect. Android 10 connects to this shared WiFi without problems. Using the
"Hotspot" button behind the system-tray network icon works with Windows 10
clients (but creates an open/unencrypted WiFi).
STEPS TO REPRODUCE
1. Go to System Settings -> Network / Connections
2. Add a new network ("+"), Connection Type: "Wi-Fi (shared)"
3. Pick an appropriate connection and SSID name (e.g. "xyz", "xyz").
4. "Security" tab: Security "WPA/WPA2 Personal", pick a password. Save.
5. "Connect" to this newly created network, enabling the Wi-Fi access point.
6. Try to connect to this AP with a Windows 10 client.
OBSERVED RESULT
1. When clicking on the "xyz" Wi-Fi, Windows 10 (EDU, Version 1909, Build
18363.418) asks for an eight-digit PIN instead of a password, unlike for other
WiFis. It is, however, also possible to click a link below and enter the
previously set AP password.
2. Windows 10's Wi-Fi dialog reports that it cannot connect to this network
("Keine Verbindung mit diesem Netzwerk möglich"). This is reproducible with
different Windows 10 machines.
3. A Sony Xperia XZ2 Compact with Android 10 connects to the "xyz" AP without
problems.
EXPECTED RESULT
Windows 10 should connect to the AP without problems, just like Android 10
does, or just as Windows 10 does to the unencrypted AP.
SOFTWARE/OS VERSIONS
Windows: Windows 10 Education, 1909, Build 18363.418
macOS:
Linux: Kubuntu 20.04
KDE Plasma Version: 5.18.4 (4:5.18.4.1-0ubuntu1)
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.5
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 419745] WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows 10 client
https://bugs.kde.org/show_bug.cgi?id=419745 --- Comment #2 from Horst Schirmeier --- (In reply to Jan Grulich from comment #1) > What is the mode set to in the "Wi-Fi" tab when configuring the connection? > Do you use Access Point or Adhoc? Access Point. > Can you change it to the other one, like to Access Point when using Adhoc and > vice versa and try if it makes a difference? After switching to Adhoc, the "WLAN Hotspot" connection doesn't come up at all; it remains in the "Configuring Interface" state and times out after a few seconds. I don't get to the stage where I can try connecting WiFi clients. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 419745] WiFi hotspot with WPA/WPA2 Personal security doesn't work with Windows 10 client
https://bugs.kde.org/show_bug.cgi?id=419745 --- Comment #3 from Horst Schirmeier --- Is systemsettings / kcm_networkmanagement the right component to file against? In the Ubuntu bug tracker I filed against network-manager (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1871710), and someone suggested to "report it upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager";; does that make sense? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #37 from Horst Schirmeier --- I haven't seen this issue for quite a while now, using Konsole 17.12.3-1ubuntu1. Seems to have been fixed in or before the release I'm currently using. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381645] New: plasmashell panel not drawn completely at screen bottom
https://bugs.kde.org/show_bug.cgi?id=381645 Bug ID: 381645 Summary: plasmashell panel not drawn completely at screen bottom Product: plasmashell Version: 5.10.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ho...@schirmeier.com Target Milestone: 1.0 Created attachment 106292 --> https://bugs.kde.org/attachment.cgi?id=106292&action=edit Screenshot As shown in the screenshot excerpt containing the bottom 76 pixels of my desktop, the panel is not drawn completely but shows 5 pixels of the background image instead at the very bottom. Playing around with the panel settings did not seem to be able to correct this issue. I'm using plasma-workspace 4:5.10.2-0ubuntu1~ubuntu17.04~ppa1 from http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu . -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 375133] konsole in fullscreen mixes up window stacking on other desktops
https://bugs.kde.org/show_bug.cgi?id=375133 Horst Schirmeier changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Horst Schirmeier --- Seems to be fixed in 16.12.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381645] plasmashell panel not drawn completely at screen bottom
https://bugs.kde.org/show_bug.cgi?id=381645 Horst Schirmeier changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Horst Schirmeier --- (In reply to Christoph Feck from comment #1) > Does it happen with all Plasma themes? You can change them with > systemsettings5 > Workspace Theme > Desktop Theme. No. > Additionally, try Alt+Shift+F12 to disable compositing. It is possible that > your video drivers expose this bug. Alt-Shift-F12 had no effect. But, interestingly, playing with the compositor settings (System settings -> Hardware -> Display and Monitor -> Compositor) revealed that KDE decided at some point in the past that OpenGL detection on my machine is prone to crash the system and disabled it. Once I clicked "re-enable OpenGL detection", the panel looked fine again. Thank you for the hint! For the records, I use Intel's i965-va-driver 1.8.0-0intel1 on an "HD Graphics 530" (Lenovo ThinkPad T460p, i7-6700HQ). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 371687] Unicode characters appear cut off and mess up text height for rest of line
https://bugs.kde.org/show_bug.cgi?id=371687 Horst Schirmeier changed: What|Removed |Added CC||ho...@schirmeier.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 371687] Unicode characters appear cut off and mess up text height for rest of line
https://bugs.kde.org/show_bug.cgi?id=371687 --- Comment #17 from Horst Schirmeier --- I built konsole from the current git master (v16.12.0-23-gb7e75cf) on Ubuntu 16.10 with most KDE packages from ppa:kubuntu-ppa/backports, and I still see vertical glyph cutoff/offsetting. However, I may see a different bug, because I can reproduce it with plain ASCII characters. The relevant part of my bugreport from the Ubuntu bug tracker (https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/1654875): Depending on the text-cursor position (e.g., in vim), glyphs in a complete text line in Konsole are cut off vertically. These characters need not be fancy Unicode ones, plain ASCII suffices. Konsole font is the default one here (Oxygen Mono, 9.0), but due to my Hi-DPI display (14" with 2560x1440px) I set "Force fonts DPI" to 192 in KDE's Settings->Appearance->Font->Fonts. Also reproducible with the "Hack" font instead of "Oxygen Mono", and/or disabling the fonts setting "Force fonts DPI". -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 371687] Unicode characters appear cut off and mess up text height for rest of line
https://bugs.kde.org/show_bug.cgi?id=371687 --- Comment #18 from Horst Schirmeier --- Created attachment 103355 --> https://bugs.kde.org/attachment.cgi?id=103355&action=edit Screenshot showing the effect in vim in line 54+55 How I created the screenshot: Create text file with sufficient number of lines; open with vim; move cursor down until I'm at the terminal's last line and beyond; move back up until cursor is about in the vertical middle of the terminal. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 Horst Schirmeier changed: What|Removed |Added CC||ho...@schirmeier.com --- Comment #5 from Horst Schirmeier --- I built konsole from the current git master (v16.12.0-23-gb7e75cf) on Ubuntu 16.10 with most KDE packages from ppa:kubuntu-ppa/backports, and I see vertical glyph cutoff/offsetting and partially also horizontal lines. Depending on the text-cursor position (e.g., in vim), glyphs in a complete text line in Konsole are cut off vertically. These characters need not be fancy Unicode ones, plain ASCII suffices. The effect vanishes when the terminal is redrawn, e.g., after switching Desktops back and forth. Displays -> Scale -> Scale Factor is 1.4 here (2560x1440px). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #6 from Horst Schirmeier --- Created attachment 103366 --> https://bugs.kde.org/attachment.cgi?id=103366&action=edit Screenshot showing the effect in vim in line 54+55 How I created the screenshot: Create text file with sufficient number of lines; open with vim; move cursor down until I'm at the terminal's last line and beyond; move back up until cursor is about in the vertical middle of the terminal. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 371687] Unicode characters appear cut off and mess up text height for rest of line
https://bugs.kde.org/show_bug.cgi?id=371687 --- Comment #21 from Horst Schirmeier --- Yes, HiDPI scaling is at 1.4 here. Thanks, I added comments to bug 373232. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling
https://bugs.kde.org/show_bug.cgi?id=373232 --- Comment #7 from Horst Schirmeier --- Note: I already saw this bug with konsole 4:16.04.3-0ubuntu1 on Ubuntu 16.10, which is why I tried konsole's git HEAD in the first place. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 345670] ctrl-alt-t konsole example not starting on top
https://bugs.kde.org/show_bug.cgi?id=345670 Horst Schirmeier changed: What|Removed |Added CC||ho...@schirmeier.com --- Comment #6 from Horst Schirmeier --- I'm seeing this on KDE 5.7.5 (Ubuntu 16.10 yakkety) and 5.8.5 (from the Kubuntu backports PPA). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 375133] New: konsole in fullscreen mixes up window stacking on other desktops
https://bugs.kde.org/show_bug.cgi?id=375133 Bug ID: 375133 Summary: konsole in fullscreen mixes up window stacking on other desktops Product: konsole Version: 16.04.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ho...@schirmeier.com Target Milestone: --- When I have a konsole in fullscreen (F11) mode on one desktop, the stacking order of windows on other desktops cannot be changed anymore. Expected: The stacking order of windows on other desktops should be changeable. For example, clicking the status bar of a background window should bring it to the front. Observed: Clicking the status bar of a background window focuses it, but does not bring it to the front. Once I quit fullscreen mode of the konsole (F11 again), this works properly again. I am not sure whether this is a konsole or a window-manager bug. However, I could not reproduce this issue with evince in full-screen mode. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498925] Request: More sophisticated touchpad auto-disable
https://bugs.kde.org/show_bug.cgi?id=498925 Horst Schirmeier changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |LATER --- Comment #3 from Horst Schirmeier --- (In reply to Nate Graham from comment #2) > When this happens, are you using X11, or Wayland? > > Does it also happen on Wayland? I don't use Wayland, and I have yet to test the behavior on Wayland. > If it doesn't happen on Wayland, there's a chance this should work as > expected without additional action needed in Plasma 6.3, which has a new > implementation of the "disable touchpad while mouse is connected" feature > and it might be smarter about figuring out what's actually a mouse and > what's not. > > If not, then I think it's reasonable to make the configuration more > fine-grained to work around devices that inappropriately report themselves > as mice, which wouldn't be something we can really fix on our side. OK – I guess it makes sense for me to wait for Plasma 6.3 to roll into my Debian Testing installation before I reopen this feature request. However, the previous whitelist (i.e., a list of devices that should not disable the touchpad) approach worked really well around the problem of devices inappropriately reporting themselves as mice – which sadly exist and definitely cannot be educated to report in differently. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 498925] New: Request: More sophisticated touchpad auto-disable
https://bugs.kde.org/show_bug.cgi?id=498925
Bug ID: 498925
Summary: Request: More sophisticated touchpad auto-disable
Classification: Applications
Product: systemsettings
Version: 6.2.5
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: kcm_touchpad
Assignee: plasma-b...@kde.org
Reporter: ho...@schirmeier.com
CC: duha.b...@gmail.com, natalie_clar...@yahoo.de
Target Milestone: ---
SUMMARY
I'm not sure this might even be a considered a bug, but since migrating from
KDE5 to KDE6, touchpad auto-disable is *always on* on my machine, and not
configurable in any way anymore:
- When I plug in a USB mouse, my Lenovo ThinkPad T15p touchpad ("SynPS/2
Synaptics TouchPad") gets disabled automatically (OK for me).
- A touch-screen input device the system sees when attaching our classroom
equipment via USB also disables the ThinkPad touchpad (not OK for me).
- When using "projecteur", a (Debian-packaged) piece of software that provides
a virtual mouse controlled by a "Logitech Spotlight" device, the ThinkPad
touchpad gets disabled (not OK for me).
Earlier, the xserver-xorg-input-synaptics configuration was much more
fine-grained and among other things allowed me to define a whitelist of devices
that did not disable the internal touchpad. Please consider adding such a
whitelist again, ideally one that can easily be filled with devices currently
connected to the machine.
The respective, now ignored entries from my .config/touchpadrc:
[autodisable]
DisableWhenMousePluggedIn=true
MouseBlacklist=Honghe KasaF75 CoolTouch® System,TPPS/2 Elan
TrackPoint,Projecteur_virtual_mouse,Projecteur_virtual_keyboard,SMART
Technologies SMART Board Mouse,SMART Technologies SMART Board,PixArt USB
Optical Mouse,Logitech USB Receiver Mouse,Logitech USB Receiver Consumer
Control,Projecteur_input_device,Presenter with Joystick Consumer
Control,Presenter with Joystick Mouse,TPPS/2 IBM TrackPoint,USB Trackpoint
pointing device,DualPoint Stick,ThinkPad USB Keyboard with TrackPoint
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 498925] Request: More sophisticated touchpad auto-disable
https://bugs.kde.org/show_bug.cgi?id=498925 --- Comment #1 from Horst Schirmeier --- PS: I just realized that I'm responsible for the auto-disable myself (see below), so this is certainly not a bug but merely a request to control this in a much more fine-grained manner. /etc/X11/xorg.conf.d/30-touchpad.conf : # https://gitlab.freedesktop.org/libinput/libinput/-/issues/924#note_2051323 Section "InputClass" Identifier "touchpad" Driver "libinput" MatchIsTouchpad "on" Option "SendEventsMode" "disabled-on-external-mouse" EndSection -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 415364] Implement feature to disable touchpad when mouse is plugged in when using Libinput driver
https://bugs.kde.org/show_bug.cgi?id=415364 Horst Schirmeier changed: What|Removed |Added CC||ho...@schirmeier.com --- Comment #34 from Horst Schirmeier --- It seems to me that all work in progress towards "disable touchpad when a mouse is plugged in" will still end us up in a worse position than we were in a year back. The Synaptics driver did not only offer this binary setting, but also allowed to define a white-list of mouse-like devices that do *not* disable the touchpad. Here, I e.g. added the "Logitech Spotlight" virtual laser pointer or the touch-screen input device I get when attaching our classroom equipment via USB. Is it still possible to somehow use the Synaptics driver? -- You are receiving this mail because: You are watching all bug changes.
