[plasma-nm] [Bug 480287] Browser login for openconnect has fixed size
https://bugs.kde.org/show_bug.cgi?id=480287 --- Comment #5 from Paul de Vrieze --- I actually used blind entry to actually be able to log in. Today I logged in again, and somehow the window was larger so I could see most of the relevant parts of the web page (still not perfect, but...). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 480287] Browser login for openconnect has fixed size
https://bugs.kde.org/show_bug.cgi?id=480287 --- Comment #2 from Paul de Vrieze --- Created attachment 165199 --> https://bugs.kde.org/attachment.cgi?id=165199=edit Screenshot of the dialog This shows the issue. For some strange reason even forcing window geometry doesn't change the size. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 480287] Browser login for openconnect has fixed size
https://bugs.kde.org/show_bug.cgi?id=480287 --- Comment #1 from Paul de Vrieze --- I had a bit of a look at the code. The code sets the webengine widget to 640x480: (https://invent.kde.org/plasma/plasma-nm/-/blob/Plasma/6.0/vpn/openconnect/openconnectauth.cpp#L604) But the UI file restricts the full widget to 360x360 (https://invent.kde.org/plasma/plasma-nm/-/blob/Plasma/6.0/vpn/openconnect/openconnectauth.ui#L9). Note that (on wayland) the window class is seen as kded6 (with fixed maximum size) - attempting to force the maximum size with kwin doesn't work. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 480287] New: Browser login for openconnect has fixed size
https://bugs.kde.org/show_bug.cgi?id=480287 Bug ID: 480287 Summary: Browser login for openconnect has fixed size Classification: Plasma Product: plasma-nm Version: 5.92.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: paul.devri...@gmail.com Target Milestone: --- SUMMARY The webview for the openconnect browser authentication (for openconnect/anyconnect - with MS SAML auth) has a fixed size (can not be resized) as well as no scroll bars. Unfortunately the login page used by my provider has a reasonably large minimum size and therefore most of the login dialog is invisible. STEPS TO REPRODUCE 1. Try to connect to the VPN (using anyconnect) 2. Be prompted with the SAML login page OBSERVED RESULT The page does not scroll (some bits with selection do allow it) and can not be used reasonably. EXPECTED RESULT The page can be seen properly (ideally resized to display the page with "minimum" size), but at least allow scrolling and resizing of the login window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo / Plasma 5.92.0 (available in About System) KDE Plasma Version: 5.92.0 KDE Frameworks Version: 5.248 Qt Version: 6.6.1 ADDITIONAL INFORMATION - For some reason it does not appear possible to trigger the login for a second time. - Logging in with nm-applet (gnome applet) works correctly. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 --- Comment #4 from Paul de Vrieze --- In my case the cursor is visible on the intel screen, but not on the nvidia (external) screens. FYI kwin is using mesa/intel as primary acceleration. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479583] cursor disappear on laptop screen in prime system with external display connected after kwin commit b214251f81cbacacf3ef483081a7cef15343fa7f,
https://bugs.kde.org/show_bug.cgi?id=479583 Paul de Vrieze changed: What|Removed |Added CC||paul.devri...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479634] Invisible mouse cursor on internal laptop screen while visible on external
https://bugs.kde.org/show_bug.cgi?id=479634 Paul de Vrieze changed: What|Removed |Added CC||paul.devri...@gmail.com --- Comment #3 from Paul de Vrieze --- I have a similar issue. In my case the cursor is visible properly in 5.91.0. In 5.92.0 the cursor is only visible on the (primary) laptop screen that is driven by an Intel iGPU, but not on the external displays connected to the NVidia GPU. In my case I tried setting both WLR_NO_HARDWARE_CURSORS=1 and KWIN_FORCE_SW_CURSOR=1 in which the problem didn't go away (Reverting to 5.91.0 on an otherwise RC1 install "fixes" things, even with the environment variables still set. In dmesg I have the message: "[drm] [nvidia-drm] [GPU ID 0x0100] Framebuffer memory not appropriate for scanout". It also seems related to https://forums.developer.nvidia.com/t/hardware-cursor-is-not-working-on-wayland-drm-sessions/261853 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376801] kwin disables compositing with mesa 17
https://bugs.kde.org/show_bug.cgi?id=376801 --- Comment #18 from Paul de Vrieze <paul.devri...@gmail.com> --- @martin I am not sure about that configuration, but I believe that it was due to attempts to use wayland as well. I will try to have a look tomorrow, but it is one of those gentoo choice things. I hadn't realised that kwin was using es. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376801] kwin disables compositing with mesa 17
https://bugs.kde.org/show_bug.cgi?id=376801 --- Comment #16 from Paul de Vrieze <paul.devri...@gmail.com> --- Created attachment 106442 --> https://bugs.kde.org/attachment.cgi?id=106442=edit Debug info when running mesa 17 I've attached the support information. I made a before version as well, but the only differences are kwin version (5.10.2 instead of 5.10.3) and the mesa/opengl versions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 381318] New: Compositing disabled with mesa 17 and intel (i965) driver
https://bugs.kde.org/show_bug.cgi?id=381318 Bug ID: 381318 Summary: Compositing disabled with mesa 17 and intel (i965) driver Product: kwin Version: 5.10.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: paul.devri...@gmail.com Target Milestone: --- In line with the bug on freedesktop, it could be that the problem is in kwin rather than mesa (or perhaps kwin could easily work around it). https://bugs.freedesktop.org/show_bug.cgi?id=99604 Opengl still works with that driver, but kwin complains about "ShaderManager self test failed". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381197] New: Plasma shell stops updating the panel
https://bugs.kde.org/show_bug.cgi?id=381197 Bug ID: 381197 Summary: Plasma shell stops updating the panel Product: plasmashell Version: 5.10.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: paul.devri...@gmail.com Target Milestone: 1.0 For the last number of major releases plasma shell "randomly" stops updating the state of its plasmoids in the panel (the clock stops, load viewer (if enabled) stops, the task list doesn't update). The system is still responsive to user input, so clicking on an application in the task section of the panel does open (or bring forward) a window, but not the correct window. The alt-tab task switcher works correctly and lists all windows. Manually killing/restarting plasmashell fixes the problem temporarily, but it comes up again soon. The issue is much more likely to occur on high system load, even when system monitor is not included. It looks like some sort of race condition. -- You are receiving this mail because: You are watching all bug changes.
