[Desktop-packages] [Bug 2008489] [NEW] Unable to switch NVIDIA driver -- cryptic "OK" window pops up
Public bug reported: See askubuntu.com question: https://askubuntu.com/questions/1415167/what-does-the-software-updater- popup-that-says-ok-with-a-circled-x-mean-when tail -f /var/log/syslog Feb 24 08:56:26 ML PackageKit: new install-packages transaction /9536_dadedeab scheduled from uid 1000 Feb 24 08:56:26 ML PackageKit: install-packages transaction /9536_dadedeab from uid 1000 finished with failed after 205ms Feb 24 08:56:26 ML software-proper[115228]: Failed to set text 'Error while applying changes#012#012pk-client-error-quark: The following packages have unmet dependencies:#012 linux-modules-nvidia-525-generic: Depends: linux-modules-nvidia-525-5.15.0-60-generic (= 5.15.0-60.66) but it is not going to be installed#012Depends: nvidia-kernel-common-525 (<= 525.78.01-1) but it is not installable#012 Depends: nvidia-kernel-common-525 (>= 525.78.01) but it is not installable#012 (268)' from markup due to error parsing markup: Error on line 5 char 74: “=” is not a valid character following a “<” character; it may not begin an element name $ lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22.4 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 08:52:03 2023 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-02-05 (1114 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2008489 Title: Unable to switch NVIDIA driver -- cryptic "OK" window pops up Status in software-properties package in Ubuntu: New Bug description: See askubuntu.com question: https://askubuntu.com/questions/1415167/what-does-the-software- updater-popup-that-says-ok-with-a-circled-x-mean-when tail -f /var/log/syslog Feb 24 08:56:26 ML PackageKit: new install-packages transaction /9536_dadedeab scheduled from uid 1000 Feb 24 08:56:26 ML PackageKit: install-packages transaction /9536_dadedeab from uid 1000 finished with failed after 205ms Feb 24 08:56:26 ML software-proper[115228]: Failed to set text 'Error while applying changes#012#012pk-client-error-quark: The following packages have unmet dependencies:#012 linux-modules-nvidia-525-generic: Depends: linux-modules-nvidia-525-5.15.0-60-generic (= 5.15.0-60.66) but it is not going to be installed#012Depends: nvidia-kernel-common-525 (<= 525.78.01-1) but it is not installable#012 Depends: nvidia-kernel-common-525 (>= 525.78.01) but it is not installable#012 (268)' from markup due to error parsing markup: Error on line 5 char 74: “=” is not a valid character following a “<” character; it may not begin an element name $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.22.4 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 08:52:03 2023 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-02-05 (1114 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bu
Re: [Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
First of all, you just cost me a few hours trying to get my network connection back after the instructions for reinstall of network-manager upon failed WICD, themselves, failed. Second, if the default network manager system that comes with distributions has a bug, it's not "whining" to rather insist that it be fixed or replaced with something that works. On Sat, Nov 5, 2016 at 3:50 AM, Peter S <1589...@bugs.launchpad.net> wrote: > If people keep whining about bugs in network-manager, without even > trying WICD (or the like) for a couple of weeks, this thread is > meaningless! > > I'm still not sure that the problems I experience are completely > unrelated to network-manager. I seem to have a more stable connection > with WICD, so far. But I have to try it for another few weeks before I > can say anything for sure. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1589401 > > Title: > cannot view wifi networks after re-enabling wifi > > Status in NetworkManager: > Confirmed > Status in network-manager package in Ubuntu: > Incomplete > > Bug description: > after re enabling wifi, up-down arrows just like wired network. cannot > see any wifi ssid. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
After I gave up and shifted to a wired connection, I noticed that I'd get disconnected periodically but then it would reconnect successfully. It seems some drivers manage to reconnect and other drivers don't. So there may be _two_ bugs: 1) A bug that results in occasional loss of connection. 2) A bug in one or more drivers that disables automatic reconnection. On Wed, Mar 1, 2017 at 9:42 AM, Jeremy LaCroix <1589...@bugs.launchpad.net> wrote: > Network Manager is the culprit, not anyone's routers. This is evident by > the fact that earlier versions of Ubuntu didn't experience this issue, > this issue happens regardless of which router we're connecting to, it > happens regardless of which location we are at, and the underlying issue > is that Network Manager cannot see ANY access points, not just the one > we normally connect to. There is literally no scenario in which it is > someone's router that is causing this. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1589401 > > Title: > cannot view wifi networks after re-enabling wifi > > Status in NetworkManager: > Unknown > Status in network-manager package in Ubuntu: > Incomplete > > Bug description: > after re enabling wifi, up-down arrows just like wired network. cannot > see any wifi ssid. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
Confirmed here and none of these "work-arounds" worked for me: # systemctl restart network-manager.service # nmcli g # killall nm-applet # start nm-applet start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused I'm running: ~# dpkg -l | grep network-manager ii network-manager 1.2.0-0ubuntu0.16.04.3 amd64 network management framework (daemon and userspace tools) With a Belkin dongle model f7d1101v1 # lshw -class network Shows no "product: ..." attribute but does show: *-network ... configuration: broadcast=yes driver=r8712u multicast=yes wireless=unassociated -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
iwlist didn't work on my system. Nothing did. I finally gave up and bought another interface. On Thu, Jan 19, 2017 at 2:02 PM, Jeremy LaCroix <1589...@bugs.launchpad.net> wrote: > Again, you shouldn't need to restart network manager or the applet. You > can simply rescan your wireless networks manually. > > sudo iwlist scan > > The applet should be doing this as soon as the machine wakes up, but > it's clearly not. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1589401 > > Title: > cannot view wifi networks after re-enabling wifi > > Status in NetworkManager: > Confirmed > Status in network-manager package in Ubuntu: > Incomplete > > Bug description: > after re enabling wifi, up-down arrows just like wired network. cannot > see any wifi ssid. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1690470] [NEW] Quadro 420 limited to 1280x1024 for each of the 4 displays
Public bug reported: Nvidia's specifications for the Quadro 420 state: "Drive up to four 30’ displays at 2560x1600 resolutions" After a couple of days trying variations, I discovered the only way I could get 4 displays working properly was to set them all to 1280x1024. If any of the 4 were set to a higher resolution via the System Settings -> Displays -> Resolution, it would do various buggy things. Here's my configuration: # apt list --installed|egrep -i "nvidia|nouveau" WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libdrm-nouveau2/zesty,now 2.4.76-1 amd64 [installed] nvidia-340/zesty,zesty,now 340.102-0ubuntu3 amd64 [installed] nvidia-opencl-icd-340/zesty,zesty,now 340.102-0ubuntu3 amd64 [installed,automatic] nvidia-prime/zesty,now 0.8.4 amd64 [installed,automatic] nvidia-settings/zesty,now 381.22-0ubuntu0~gpu17.04.1 amd64 [installed] # lspci -k | grep -iEA3 '3D|VGA' 03:00.0 VGA compatible controller: NVIDIA Corporation G98 [Quadro NVS 420] (rev a1) Subsystem: NVIDIA Corporation G98 [Quadro NVS 420] Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau, nvidia_340 04:00.0 3D controller: NVIDIA Corporation G98 [Quadro NVS 420] (rev a1) Subsystem: NVIDIA Corporation G98 [Quadro NVS 420] Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau, nvidia_340 # uname -a Linux jabowery-H61M-S2-B3 4.10.0-21-lowlatency #23-Ubuntu SMP PREEMPT Fri Apr 28 18:21:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux ** Affects: nvidia-graphics-drivers-340-updates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340-updates in Ubuntu. https://bugs.launchpad.net/bugs/1690470 Title: Quadro 420 limited to 1280x1024 for each of the 4 displays Status in nvidia-graphics-drivers-340-updates package in Ubuntu: New Bug description: Nvidia's specifications for the Quadro 420 state: "Drive up to four 30’ displays at 2560x1600 resolutions" After a couple of days trying variations, I discovered the only way I could get 4 displays working properly was to set them all to 1280x1024. If any of the 4 were set to a higher resolution via the System Settings -> Displays -> Resolution, it would do various buggy things. Here's my configuration: # apt list --installed|egrep -i "nvidia|nouveau" WARNING: apt does not have a stable CLI interface. Use with caution in scripts. libdrm-nouveau2/zesty,now 2.4.76-1 amd64 [installed] nvidia-340/zesty,zesty,now 340.102-0ubuntu3 amd64 [installed] nvidia-opencl-icd-340/zesty,zesty,now 340.102-0ubuntu3 amd64 [installed,automatic] nvidia-prime/zesty,now 0.8.4 amd64 [installed,automatic] nvidia-settings/zesty,now 381.22-0ubuntu0~gpu17.04.1 amd64 [installed] # lspci -k | grep -iEA3 '3D|VGA' 03:00.0 VGA compatible controller: NVIDIA Corporation G98 [Quadro NVS 420] (rev a1) Subsystem: NVIDIA Corporation G98 [Quadro NVS 420] Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau, nvidia_340 04:00.0 3D controller: NVIDIA Corporation G98 [Quadro NVS 420] (rev a1) Subsystem: NVIDIA Corporation G98 [Quadro NVS 420] Kernel driver in use: nouveau Kernel modules: nvidiafb, nouveau, nvidia_340 # uname -a Linux jabowery-H61M-S2-B3 4.10.0-21-lowlatency #23-Ubuntu SMP PREEMPT Fri Apr 28 18:21:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340-updates/+bug/1690470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
