[systemsettings] [Bug 415364] Many touchpad settings are missing.
https://bugs.kde.org/show_bug.cgi?id=415364 Neil Rickert changed: What|Removed |Added CC||nwr10cst-os...@yahoo.com --- Comment #2 from Neil Rickert --- This still seems a bug to me. The setting that I am missing is "Disable touchpad when a mouse is plugged in". In all honesty, that setting is why I started using KDE. And that worked for me with openSUSE Leap 15.0 and Leap 15.1 (both using Plasma 5.12.8 and the Libinput drivers). But the setting is no longer available with openSUSE Leap 15.2 Beta (using Plasma 5.18.0). However, it still works if I copy ".config/touchpadrc" from an earlier system. I really hope that this setting isn't going away. And I hope we can get back a way of configuring it via system settings. Here's a strange thing. On one laptop, I see the old touchpad settings screen. That laptop was originally configured with openSUSE Leap 15.0, then upgraded. However, if I create a new user on that same computer, then I get the new touchpad settings screen with some settings no longer visible. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 380797] Cannot set MTU of wired connection
https://bugs.kde.org/show_bug.cgi?id=380797 --- Comment #7 from Neil Rickert --- >Could you please check whether this is not a duplicate of bug 378554? Yes, it appears to be the same bug. I set "allow auto-negotiation". Then "Apply" was no longer grayed out. I changed the MTU to 1471 and clicked "Apply" (and was prompted for root password). Checking the connection file in "/etc/NetworkManager/system-connection", the MTU information had changed to 1471. I was then prompted for the "kdewallet" key. I'm not sure what that is about, since this is a wired connection. I closed the connection editor. Then I restarted it. I could see that "allow auto-negotiation" was still checked. I changed the MTU back to 1472. And that caused "Apply" to no longer be grayed out. And I was able to save those changes. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 380797] Cannot set MTU of wired connection
https://bugs.kde.org/show_bug.cgi?id=380797 --- Comment #5 from Neil Rickert --- Tumbleweed upgrade plasma-nm to version 5.10.1 today. So I decided to retest. The problem is still there. But I paid closer attention to what is happening. When I start editing the Wired connect settings, I see "Okay", "Apply" and "Cancel" buttons near the bottom of the screen. But the "Apply" is grayed out, so cannot be used. When I change something (I tried changing the MTU from 1472 to 1471), the "Apply" remains greyed out. So the applet is not recognizing that there are changes that need to be saved. By contrast, if I edit a "WiFi" connection settings, then the change of MTU from 1472 to 1471 (and then back to 1472) makes the Apply button active (not grayed out). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 380797] Cannot set MTU of wired connection
https://bugs.kde.org/show_bug.cgi?id=380797 --- Comment #4 from Neil Rickert --- In openSUSE Tumbleweed, NetworkManager shows up as version 1.6.2. On KaOS, where I also see this problem, NetworkManager appears to be version 1.8.0. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 380797] Cannot set MTU of wired connection
https://bugs.kde.org/show_bug.cgi?id=380797 --- Comment #2 from Neil Rickert --- I am seeing the problem on openSUSE Tumbleweed (plasma-nm 5.10.0 -- actually called "plasma-nm5 there). I am also seeing the problem on KaOS, with plasma-nm 5.9.5.1 With the way that openSUSE handles NM, there should have been a polkit window that popped up when I tried to save the changes. But there was no such polkit popup. Similarly, with KaOS, there was no polkit popup. It's a while since I last used Fedora. But I seem to recall that it was more generous with allowing network config changes, so perhaps it would not have required a polkit query. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 380797] New: Cannot set MTU of wired connection
https://bugs.kde.org/show_bug.cgi?id=380797 Bug ID: 380797 Summary: Cannot set MTU of wired connection Product: plasma-nm Version: 5.10.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: nwr10cst-os...@yahoo.com Target Milestone: --- I attempted to set MTU for wired connection to 1472 (recommended for IPv6 via 6rd). Note: this is also reported as Bug 1042542 for opensuse (bugzilla.opensuse.org). In the client, I made the change, then clicked "Okay" (or "Apply"). I expected a connection definition file (probably "Wired connection 1") to be save in "/etc/NetworkManager/system-connections" with the changed setting. Instead, nothing happened. I rebooted, and the MTU was still 1500. I also have Gnome desktop installed. I tried using the Gnome NetworkManager client, and changing the MTU there worked as expected (while logged into Gnome). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 359842] Shared connection asks for root password on every reconnect.
https://bugs.kde.org/show_bug.cgi?id=359842 --- Comment #18 from Neil Rickert --- Thanks for reopening. I did not get any email for the recent comments. I think my ISP may be blocking KDE.org. So I have now changed the email address that I am using. (The same problem happened with the opensuse bugzilla). -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 359842] Shared connection asks for root password on every reconnect.
https://bugs.kde.org/show_bug.cgi?id=359842 Neil Rickert changed: What|Removed |Added CC||nrick...@ameritech.net --- Comment #14 from Neil Rickert --- In my opinion, this should be reopened. I won't reopen because of comment 8, but I disagree with that comment. Firstly, this is specifically a plasma 5 issue. If the network connect is setup in Gnome or XFCE or MATE or LXDE, then the problem does not arise. If "nm-applet" is used as network client and the connection is setup with that client, the problem does not arise. When I tried running nm-applet in Plasma 5, I could not access it, so nm-applet has to be run elsewhere. Since it works with nm-applet (which is used in XFCE), then it cannot be a polkit problem. Rather, the plasma client does things differently and, in my opinion, wrongly. I have a blog post about this at: https://nwrickert2.wordpress.com/2016/01/06/another-look-at-networkmanager-and-tumbleweed/ Responding to comment 4 >I think that "org.freedesktop.NetworkManager.settings.modify.system" = "auth" >is responsible for your problem. Yes, that's possible. But that's the wrong polkit rule. The user is just making a connection. The user is not changing a system connection. In my opinion, it should instead use "org.freedesktop.NetworkManager.network-control". As far as I know, it is a plasma issue to specify the appropriate rule. When the user first changed the connection to be a system connection, then "modify.system" was appropriate. But just connecting to an existing system connection does not modify the connection definition, so should be under the more general "network-control". -- You are receiving this mail because: You are watching all bug changes.
