[plasma-nm] [Bug 412795] Wireguard set up fails with erros -settings lost
https://bugs.kde.org/show_bug.cgi?id=412795 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479020] Attempting to import a wireguard configuration with an invalid name leads to a misleading error message
https://bugs.kde.org/show_bug.cgi?id=479020 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 --- Comment #2 from Matt Keith --- Also - the reproduction steps key and ip info are all false. But it will let you save the info. I of course found https://bugs.kde.org/show_bug.cgi?id=412795 which is for the same issue after creating this one. I feel mine is more useful so I will not mark it as duplicate myself -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 Matt Keith changed: What|Removed |Added Platform|Fedora RPMs |Neon Version|5.27.10 |5.91.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 --- Comment #1 from Matt Keith --- I was able to reproduce this on kde plasma 6 beta 2 KDE Plasma Version: 5.91.90 KDE Freameworks Version: 5.248.0 QT Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Using the live demo installer. The issue is the same - the name is invalid - and the problem is the same - you lose everything trying to save. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479179] New: KDE Network Manager creates unusable name for wireguard and fails to save
https://bugs.kde.org/show_bug.cgi?id=479179 Bug ID: 479179 Summary: KDE Network Manager creates unusable name for wireguard and fails to save Classification: Plasma Product: plasma-nm Version: 5.27.10 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: ro...@appus.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open Network Connections 2. Click Add New Connection 3. Pick Wireguard 4. Click Create Note default Connection Name ‘New wireguard connection’ Populate the following fields Wireguard Interface Private key: WD3tC88Km+Kuh8aXgzT8aDF4tj4ULD1pRbqZYkiiyVA= Click Peers Public key: udgr1rvvd/hk6kX2f8LCewlFB/OknvXYPeOH4IKiSXk= Allowed Ips: 192.168.3.1/32,192.168.3.2/32,0.0.0.0/0 Endpoint address: 70.1.123.123 Endpoint port: 51820 This password is not required Persistent keepalive: 25 Press Ok IPv4 Method: Manual DNS Servers: 192.168.3.1 Click +Add for Address Address: 192.168.3.2 Netmask: 255.255.255.255 Gateway: 192.168.3.1 Check IPv4 is required for this connection Click Save OBSERVED RESULT The window closes and an error notification pops up briefly with an error EXPECTED RESULT Either detect the error in the name and flag it, preventing you from saving OR The VPN connection should save. I'm not sure why the default name is not allowed or what can be done to allow it. I think the name should work with spaces if at all possible. If not - set a sensible default that replaces spaces with hyphens SOFTWARE/OS VERSIONS Operating System: Fedora Linux 39 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-200.fc39.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-1280P Memory: 62.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A8 ADDITIONAL INFORMATION The error is a bad experience because 1) it's too quick to make a note of. and 2) you lose your work of entering all of your details as it fails to save at all. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470432] When entering password after a screen lock the enter key is used as part of the password
https://bugs.kde.org/show_bug.cgi?id=470432 --- Comment #4 from Matt Keith --- (In reply to Nate Graham from comment #3) > So the first time you try to enter your password, it's rejected, and the > second time, it works? Correct > > Can you elaborate on why you think the enter key is involved here, or is > that a hypothesis at this point? It is a hypothesis -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 470432] When entering password after a screen lock the enter key is used as part of the password
https://bugs.kde.org/show_bug.cgi?id=470432 --- Comment #2 from Matt Keith --- (In reply to Nate Graham from comment #1) > Are you saying that at step 4, when you wake up the monitor with the enter > key, it inappropriately attempts to unlock the screen using an empty > password? It does not attempt to unlock the screen, but when I enter the password in correctly I get a password incorrect error back, as though the enter key was considered part of the password. On the second attempt i am allowed to enter the password and log in. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470432] New: When entering password after a screen lock the enter key is used as part of the password
https://bugs.kde.org/show_bug.cgi?id=470432 Bug ID: 470432 Summary: When entering password after a screen lock the enter key is used as part of the password Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ro...@appus.org Target Milestone: --- SUMMARY *** After a screen lock I press the enter key to wake up my monitors. I then type in my password and am rejected as invalid password. It looks like the enter key is being taken as part of the password input *** STEPS TO REPRODUCE 1. Start your desktop 2. Log into sddm 3. wait for screen saver to lock the computer 4. press enter to wake monitor 5. enter password to log in OBSERVED RESULT Your password is rejected as invalid EXPECTED RESULT The enter key should either "enter" the empty password or be disregarded as input on the first character input Your password should be accepted if it matches and you unlock the screensaver SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.15-300.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-1280P Memory: 62.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467771] Wayland screen corruption, dual output, dual GPU, different screen resolution
https://bugs.kde.org/show_bug.cgi?id=467771 --- Comment #5 from Matt Keith --- (In reply to Stefan Hoffmeister from comment #3) > https://www.reddit.com/r/Fedora/comments/12j8j1n/ > have_you_guys_seen_this_screen_glitch_in_kde_what/ > ?utm_source=share_medium=web2x=3 looks interesting and possibly > related - the symptoms are very similar. > > Note that the Reddit thread talks about an AMD RX5700 eGPU, attached to a > laptop. Hi, I am the reddit poster here. about info below: Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.9-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-1280P Memory: 62.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A8 I am happy to provide any debug info that would be useful. This happens just about every time I use my computer so I can reproduce it easily -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467771] Wayland screen corruption, dual output, dual GPU, different screen resolution
https://bugs.kde.org/show_bug.cgi?id=467771 Matt Keith changed: What|Removed |Added CC||ro...@appus.org --- Comment #4 from Matt Keith --- Created attachment 158056 --> https://bugs.kde.org/attachment.cgi?id=158056=edit picture of corruption attachment showing my occurrence. the top left seems to work reliably and is about the size of my laptops display -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 466276] New: Cursor is not where it should be while using UI Scailing
https://bugs.kde.org/show_bug.cgi?id=466276 Bug ID: 466276 Summary: Cursor is not where it should be while using UI Scailing Classification: Applications Product: krfb Version: 22.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: ro...@appus.org Target Milestone: --- SUMMARY Krfb displays the cursor in the wrong place but the remote desktop's cursor is somewhere else when using UI Scaling. Once I reduced the UI Scaling to 100% it worked as expected STEPS TO REPRODUCE 1. Use a single monitor on KDE/Wayland 2. Given a base resolution of 2256x1504. Scale to 200% 3. connect with krfb OBSERVED RESULT Your mouse cursor is in the wrong location EXPECTED RESULT Mouse cursor should reflect it's actual location SOFTWARE/OS VERSIONS Windows client using RealVNC and TigerVNC Linux/KDE Plasma: KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I am using wayland as the compositor -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 --- Comment #4 from Matt Keith --- (In reply to Zamundaaa from comment #2) > Bug 452219 is more about NVidia GPUs specifically, but yeah it's most likely > the same underlying issue. > Please attach the output of drm_info > (https://gitlab.freedesktop.org/emersion/drm_info), whether or not KWin > falls back to CPU copy should be visible in there. The file is attached. I reinstalled fedora 37 onto a new partition so that I could ensure the egpu script i ran was not a factor. I'll keep it this way for troubleshooting purposes for a while -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 --- Comment #3 from Matt Keith --- Created attachment 156551 --> https://bugs.kde.org/attachment.cgi?id=156551=edit drm_info output from freshly installed fedora 37 with all updates This drm_info was collected from a freshly installed fedora 37 kde spin with the updates as of today, which includes kde 5.27 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #24 from Matt Keith --- Also to add, I am running fedora 37 kde spin with the 5.27 release of kde plasma under wayland -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 --- Comment #23 from Matt Keith --- (In reply to Nick from comment #21) > I'm not sure if this is exactly the right issue, but I seem to be > experiencing something like this ever since upgrading from Fedora KDE 36 to > Fedora KDE 37. > I have an Asus XG27AQ at 144hz using DisplayPort, and an Asus VS239 at 60hz > using HDMI. Both are plugged in to a 6700XT. > > The last version of KDE on Fedora KDE 36 was 5.25.5, and my monitors would > stay asleep as expected. > After upgrading to Fedora KDE 37 which brought KDE 5.26.3, as long as both > monitors are powered on, they immediately wake up after entering sleep. > If I turn off the HDMI monitor, the DisplayPort monitor stays asleep. If I > turn off the DisplayPort monitor, the HDMI monitor wakes up after entering > sleep. > This persisted with 5.26.4, and at the moment with 5.26.5. > > On Wayland in all instances. Disabling kscreen2 doesn't help. > At the end of Fedora KDE 36, I had kernel 6.0.7. Fedora KDE 37 brought that > to 6.0.8. I'm now on 6.1.6. I am experiencing this issue as well I have a framework laptop with the display open. a radeon rx5700 connected by a razer chroma egpu enclosure. A monitor connected to the video card by the display port. The computer locks when idle but both the laptop and the monitor stay on all night. =/ Are there any logs I could attach that might be relevant and useful? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 422455] Monitor power saving won't work when using DisplayPort cable
https://bugs.kde.org/show_bug.cgi?id=422455 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 348529] When screen is locked, turn off screen with a shorter timeout
https://bugs.kde.org/show_bug.cgi?id=348529 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 Matt Keith changed: What|Removed |Added Version|unspecified |5.26.5 Platform|Other |Fedora RPMs -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 --- Comment #1 from Matt Keith --- probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=452219 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel
https://bugs.kde.org/show_bug.cgi?id=452219 Matt Keith changed: What|Removed |Added CC||ro...@appus.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465809] New: external display running through an egpu is very laggy
https://bugs.kde.org/show_bug.cgi?id=465809 Bug ID: 465809 Summary: external display running through an egpu is very laggy Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: ro...@appus.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install Fedora 37 KDE spin 2. plug in an egpu RX 5700 3. plug in monitor into egpu 4. reboot OBSERVED RESULT both laptop and external display work. laptop display is buttery smooth. external display is choppy. EXPECTED RESULT Both laptop and the external display work. laptop display is buttery smooth. external display is buttery smooth SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Fedora 37 KDE spin Plasma: 5.26.5 (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I am running wayland with a display plugged into an egpu Radeon RX5700. I created a post with my laptop manufacturer with some additional details: https://community.frame.work/t/linux-poor-performance-of-egpu-driven-external-monitor-in-fedora-37-kde-spin/27290 After running the following script to designate my egpu as primary per this project: https://github.com/ewagner12/all-ways-egpu/wiki I now observe the external display is smooth and the integrated display is now choppy. My suggestion would be to either run the display on the gpu for which it is designated and give options to switch this or provide an option within KDE to select which GPU to use and note that the other will perform poorly Perhaps the choppiness is also an issue with wayland or kwin that could in itself be resolved? Being able to choose which gpu to use is still needed for tasks like running games though -- You are receiving this mail because: You are watching all bug changes.
