Re: [Desktop-packages] [Bug 1902596] Re: VPN doesn't connect automatically
Hi, I shorted that log file. You probably don't need 100k lines. Godspeed, Jen On 11/16/20 9:42 AM, Jen Doty | The Silverwire Company wrote: > > I'm still learning, so I'm not entirely sure which lines you need > other than the obvious. I attached a txt file so you have as much as > possible. Thank goodness for CTRL-F :) > > Also, I tried to do ubuntu-bug but it didn't pull anything about the > network manager so I thought it wasn't correct. > > Godspeed, > Jen > > > > On 11/3/20 1:32 PM, Sebastien Bacher wrote: >> journalctl -b 0 ** Attachment added: "journalctl -b 0" https://bugs.launchpad.net/bugs/1902596/+attachment/5434827/+files/journalctl%20-b%200 -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] Re: VPN doesn't connect automatically
I'm still learning, so I'm not entirely sure which lines you need other than the obvious. I attached a txt file so you have as much as possible. Thank goodness for CTRL-F :) Also, I tried to do ubuntu-bug but it didn't pull anything about the network manager so I thought it wasn't correct. Godspeed, Jen On 11/3/20 1:32 PM, Sebastien Bacher wrote: > journalctl -b 0 ** Attachment added: "journalctl -b 0" https://bugs.launchpad.net/bugs/1902596/+attachment/5434819/+files/journalctl%20-b%200 -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434797/+files/nmcli-con.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434792/+files/NetworkManager.conf.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434798/+files/nmcli-dev.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434793/+files/PciNetwork.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434795/+files/RfKill.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434794/+files/ProcCpuinfoMinimal.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434796/+files/WifiSyslog.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] NetDevice.wlp1s0.txt
apport information ** Attachment added: "NetDevice.wlp1s0.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434791/+files/NetDevice.wlp1s0.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] NetDevice.virbr0-nic.txt
apport information ** Attachment added: "NetDevice.virbr0-nic.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434790/+files/NetDevice.virbr0-nic.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] Re: VPN doesn't connect automatically
apport information ** Tags added: apport-collected ** Description changed: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.1 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2020-10-25 (22 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IpRoute: + default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 + 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown + 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 + 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown + Package: network-manager 1.26.2-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 + Tags: groovy + Uname: Linux 5.8.0-29-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.26.2 connected started full enabled enabled enabled enabled enabled ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434784/+files/CRDA.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] NetDevice.virbr0.txt
apport information ** Attachment added: "NetDevice.virbr0.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434789/+files/NetDevice.virbr0.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434787/+files/IwConfig.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434788/+files/NetDevice.lo.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434786/+files/IpAddr.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1902596/+attachment/5434785/+files/Dependencies.txt -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: Incomplete Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-25 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.1.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.106 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Package: network-manager 1.26.2-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-25 (22 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.26.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1902596] [NEW] VPN doesn't connect automatically
Public bug reported: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description:Ubuntu 20.10 Release:20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: groovy ** Attachment added: "Screenshots" https://bugs.launchpad.net/bugs/1902596/+attachment/5430433/+files/Untitled.jpg -- 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/1902596 Title: VPN doesn't connect automatically Status in network-manager package in Ubuntu: New Bug description: I have set up my Network Connections manager to automatically connect to my VPN. My VPN is saved with its credentials. When I first log in (newly started, rebooted or woken from sleep/suspend), the VPN doesn't connect on its own. It sometimes doesn't connect at all, and sometimes it tells me that the VPN requires a password. I haven't noticed a pattern. Description: Ubuntu 20.10 Release: 20.10 network-manager: Installed: 1.26.2-1ubuntu1 Candidate: 1.26.2-1ubuntu1 Version table: *** 1.26.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1902596/+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 1865071] Re: Power indicator doesn't show when charging (eoan)
jen@jenius:~$ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC0 native-path: AC0 power supply: yes updated: Fri 24 Apr 2020 12:22:20 PM MST (1 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: ASUSTeK model: ASUS Battery power supply: yes updated: Fri 24 Apr 2020 12:22:20 PM MST (1 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable: yes state: discharging warning-level: none energy: 14.208 Wh energy-empty: 0 Wh energy-full: 33.409 Wh energy-full-design: 37.13 Wh energy-rate: 15.809 W voltage: 7.85 V time to empty: 53.9 minutes percentage: 42% capacity: 89.9785% technology: lithium-ion icon-name: 'battery-good-symbolic' History (charge): 1587756140 42.000 discharging 1587756076 43.000 discharging History (rate): 1587756140 15.809 discharging 1587756076 15.001 discharging Device: /org/freedesktop/UPower/devices/mouse_hidpp_battery_0 native-path: hidpp_battery_0 model: Wireless Mouse MX Master serial: 4060-e6-d2-a0-c0 power supply: no updated: Fri 24 Apr 2020 12:21:16 PM MST (65 seconds ago) has history: yes has statistics: yes mouse present: yes rechargeable: yes state: unknown warning-level: none battery-level: unknown percentage: 50% (should be ignored) icon-name: 'battery-missing-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Fri 24 Apr 2020 12:22:20 PM MST (1 seconds ago) has history: no has statistics: no battery present: yes state: discharging warning-level: none energy: 14.208 Wh energy-full: 33.409 Wh energy-rate: 15.809 W time to empty: 53.9 minutes percentage: 42% icon-name: 'battery-good-symbolic' Daemon: daemon-version: 0.99.11 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: PowerOff On 4/17/20 12:20 AM, Sebastien Bacher wrote: > Thank you for your bug report. Could you add a 'upower -d' log when > getting the issue? > > ** Changed in: gnome-shell (Ubuntu) > Importance: Undecided => Low > > ** Changed in: gnome-shell (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1865071 Title: Power indicator doesn't show when charging (eoan) Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Wed, Feb 26, 2020 at 7:00 PM Daniel van Vugt wrote: No problem. I suggest the least confusing way for us to discuss that new problem is to open a new bug by running: ubuntu-bug gnome-shell -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1845578 This is almost the same issue as my previous bug with disco, but I've noticed that if I'm plugged in before I boot, then the indicator knows it. But not if I plug in while the computer is awake or suspended/hibernating. If I plug in while it's suspended or hibernating, the indicator doesn't update. jen@jenius:~$ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.3-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 27 10:41:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-18 (39 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-02-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865
[Desktop-packages] [Bug 1865076] [NEW] Fingerprint swipe to login doesn't work
Public bug reported: After enrolling my right index fingerprint to ElanTech Fingerprint Sensor, I am unable to login via fingerprint swipe. I am able to see the (very faint) option to swipe my finger under the password entry field, but when I swipe, nothing happens. I've tried swiping both directions, just touching the sensor like I was able to in Windows (I used to dual boot) and holding my finger down for a few seconds. There's no indication of whether the sensor read anything and it just didn't process, or if it's just not getting any info. I'm including the apt-cache policy for control center and for the gnome shell, jic it's not a problem with the control center. jen@jenius:~$ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 jen@jenius:~$ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://ubuntu.securedservers.com eoan/main amd64 Packages 100 /var/lib/dpkg/status jen@jenius:~$ apt-cache policy gnome-shell gnome-shell: Installed: 3.34.3-1ubuntu1~19.10.1 Candidate: 3.34.3-1ubuntu1~19.10.1 Version table: *** 3.34.3-1ubuntu1~19.10.1 500 500 http://ubuntu.securedservers.com eoan-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://ubuntu.securedservers.com eoan-updates/main amd64 Packages 3.34.1-1ubuntu1 500 500 http://ubuntu.securedservers.com eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 27 11:46:54 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-01-18 (39 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2020-02-21 (6 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1865076 Title: Fingerprint swipe to login doesn't work Status in gnome-control-center package in Ubuntu: New Bug description: After enrolling my right index fingerprint to ElanTech Fingerprint Sensor, I am unable to login via fingerprint swipe. I am able to see the (very faint) option to swipe my finger under the password entry field, but when I swipe, nothing happens. I've tried swiping both directions, just touching the sensor like I was able to in Windows (I used to dual boot) and holding my finger down for a few seconds. There's no indication of whether the sensor read anything and it just didn't process, or if it's just not getting any info. I'm including the apt-cache policy for control center and for the gnome shell, jic it's not a problem with the control center. jen@jenius:~$ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 jen@jenius:~$ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://ubuntu.securedservers.com eoan/main amd64 Packages 100 /var/lib/dpkg/status jen@jenius:~$ apt-cache policy gnome-shell gnome-shell: Installed: 3.34.3-1ubuntu1~19.10.1 Candidate: 3.34.3-1ubuntu1~19.10.1 Version table: *** 3.34.3-1ubuntu1~19.10.1 500 500 http://ubuntu.securedservers.com eoan-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://ubuntu.securedservers.com eoan-updates/main amd64 Packages 3.34.1-1ubuntu1 500 500 http://ubuntu.securedservers.com eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 27 11:46:54 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-01-18 (39 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2020-02-21 (6 days ago) To manage notifica
[Desktop-packages] [Bug 1865071] [NEW] Power indicator doesn't show when charging (eoan)
Public bug reported: On Wed, Feb 26, 2020 at 7:00 PM Daniel van Vugt wrote: No problem. I suggest the least confusing way for us to discuss that new problem is to open a new bug by running: ubuntu-bug gnome-shell -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1845578 This is almost the same issue as my previous bug with disco, but I've noticed that if I'm plugged in before I boot, then the indicator knows it. But not if I plug in while the computer is awake or suspended/hibernating. If I plug in while it's suspended or hibernating, the indicator doesn't update. jen@jenius:~$ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.3-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 27 10:41:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-18 (39 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-02-21 (6 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan package-from-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1865071 Title: Power indicator doesn't show when charging (eoan) Status in gnome-shell package in Ubuntu: New Bug description: On Wed, Feb 26, 2020 at 7:00 PM Daniel van Vugt wrote: No problem. I suggest the least confusing way for us to discuss that new problem is to open a new bug by running: ubuntu-bug gnome-shell -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1845578 This is almost the same issue as my previous bug with disco, but I've noticed that if I'm plugged in before I boot, then the indicator knows it. But not if I plug in while the computer is awake or suspended/hibernating. If I plug in while it's suspended or hibernating, the indicator doesn't update. jen@jenius:~$ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.3-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 27 10:41:44 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-18 (39 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-02-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865071/+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 1845578] Re: Power indicator doesn't show when charging
Hello, I upgraded 3 days ago, and now the indicator does turn on, but not right away. It takes about half an hour for it to figure out that it's plugged in. Thanks :) -- Godspeed, Jen * Jennie R. Doty The Silverwire Company * *A Healthcare IT Support Agency * (402) 336-8871 Jen@Silverwire.ninja P.O. Box 245 Chambers, Ne 68725 On Fri, Jan 24, 2020 at 3:01 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Thank you for reporting this bug to Ubuntu. > Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020. > > See this document for currently supported Ubuntu releases: > https://wiki.ubuntu.com/Releases > > We appreciate that this bug may be old and you might not be interested > in discussing it any more. But if you are then please upgrade to the > latest Ubuntu version and re-test. If you then find the bug is still > present in the newer Ubuntu version, please add a comment here telling > us which new version it is in and change the bug status to Confirmed. > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Won't Fix > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1845578 > > Title: > Power indicator doesn't show when charging > > Status in gnome-shell package in Ubuntu: > Won't Fix > > Bug description: > This problem is intermittent, I have not found a pattern. > > Sometimes, when I plug my laptop into AC, the battery icon in the top > right of the screen doesn't show the charging (lightning) symbol. > Sometimes it stays this way until I restart, sometimes it shows the > lightning bolt when it increases a % point. > > Description: Ubuntu 19.04 > Release: 19.04 > > apt-cache policy pkgname > N: Unable to locate package pkgname > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845578/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1845578 Title: Power indicator doesn't show when charging Status in gnome-shell package in Ubuntu: Won't Fix Bug description: This problem is intermittent, I have not found a pattern. Sometimes, when I plug my laptop into AC, the battery icon in the top right of the screen doesn't show the charging (lightning) symbol. Sometimes it stays this way until I restart, sometimes it shows the lightning bolt when it increases a % point. Description: Ubuntu 19.04 Release: 19.04 apt-cache policy pkgname N: Unable to locate package pkgname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845578/+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 1842955] [NEW] When wifi is turned off, Settings says there's no adapter.
Public bug reported: Perhaps it should say that the wifi is turned off, instead of that there's no wifi adapter at all? Description:Ubuntu 19.04 Release:19.04 gnome-control-center: Installed: 1:3.32.2-0ubuntu1.1 Candidate: 1:3.32.2-0ubuntu1.1 Version table: *** 1:3.32.2-0ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.32.1-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 5 11:44:57 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-01 (34 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Settings window screenshot." https://bugs.launchpad.net/bugs/1842955/+attachment/5286988/+files/Screenshot%20from%202019-09-05%2011-29-52.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1842955 Title: When wifi is turned off, Settings says there's no adapter. Status in gnome-control-center package in Ubuntu: New Bug description: Perhaps it should say that the wifi is turned off, instead of that there's no wifi adapter at all? Description: Ubuntu 19.04 Release: 19.04 gnome-control-center: Installed: 1:3.32.2-0ubuntu1.1 Candidate: 1:3.32.2-0ubuntu1.1 Version table: *** 1:3.32.2-0ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.32.1-1ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 5 11:44:57 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-01 (34 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1842955/+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 1838912] [NEW] Bluetooth doesn't remember my Logitech MX Master mouse.
Public bug reported: I can pair my mouse, and sometimes Ubuntu will remember it, but more often it doesn't automatically connect when I turn the computer on or wake it up. I've noticed that it'll have the same BT address, so it should connect (?). When it DOES connect, it's when I've had the mouse turned off and don't turn it on until Ubuntu is completely awake and running. That doesn't always work, but if I have the mouse turned on before turning Ubuntu on, then it never connects. I have to re-pair them. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 18:40:38 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-01 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1838912 Title: Bluetooth doesn't remember my Logitech MX Master mouse. Status in gnome-control-center package in Ubuntu: New Bug description: I can pair my mouse, and sometimes Ubuntu will remember it, but more often it doesn't automatically connect when I turn the computer on or wake it up. I've noticed that it'll have the same BT address, so it should connect (?). When it DOES connect, it's when I've had the mouse turned off and don't turn it on until Ubuntu is completely awake and running. That doesn't always work, but if I have the mouse turned on before turning Ubuntu on, then it never connects. I have to re-pair them. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 18:40:38 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-08-01 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838912/+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 1552029] Re: Intermittently mouse corrupt on one screen
Version - 1.90Release date - 10/30/2015 Can't remember if there was no version 1.B at the time I did the update or I was dubious about using it because it looks like a Beta version or something. From: Christopher M. Penalver <christopher.m.penal...@gmail.com> To: allne...@yahoo.co.uk Sent: Friday, 20 May 2016, 12:58 Subject: [Bug 1552029] Re: Intermittently mouse corrupt on one screen Jen Hart, please provide the output of the following terminal command (not perform an apport-collect): sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1552029 Title: Intermittently mouse corrupt on one screen Status in xorg package in Ubuntu: Expired Bug description: Tried Gnome tweaks, tried changing monitors around, primary, (in case it was some how port related) etc. Can not reset the mouse cursor once it corrupts. Only solution I found was a reboot, which can be inconvenient. Might be related to Java applications somehow and their borders? P.S. I think my graphics card is R9 390 and has been picked up wrong by this bug report and by one game I know about (it thinks it is a HD 5600) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 2 01:20:06 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.201, 3.19.0-49-generic, x86_64: installed fglrx-updates-core, 15.201, 3.19.0-51-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015] InstallationDate: Installed on 2015-11-24 (98 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MSI MS-7885 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic.efi.signed root=UUID=46953798-0da7-48f9-8837-c446ced8f6f6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7885 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Mar 1 10:55:41 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3.1~trusty1 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552029
Re: [Desktop-packages] [Bug 1552029] Re: Intermittently mouse corrupt on one screen
Still get the bug.Still is random. Everything is the latest drivers and Bios. From: Launchpad Bug Tracker <1552...@bugs.launchpad.net> To: allne...@yahoo.co.uk Sent: Saturday, 14 May 2016, 5:17 Subject: [Bug 1552029] Re: Intermittently mouse corrupt on one screen [Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1552029 Title: Intermittently mouse corrupt on one screen Status in xorg package in Ubuntu: Expired Bug description: Tried Gnome tweaks, tried changing monitors around, primary, (in case it was some how port related) etc. Can not reset the mouse cursor once it corrupts. Only solution I found was a reboot, which can be inconvenient. Might be related to Java applications somehow and their borders? P.S. I think my graphics card is R9 390 and has been picked up wrong by this bug report and by one game I know about (it thinks it is a HD 5600) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 2 01:20:06 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.201, 3.19.0-49-generic, x86_64: installed fglrx-updates-core, 15.201, 3.19.0-51-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015] InstallationDate: Installed on 2015-11-24 (98 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MSI MS-7885 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic.efi.signed root=UUID=46953798-0da7-48f9-8837-c446ced8f6f6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7885 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Mar 1 10:55:41 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3.1~trusty1 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1552029/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1552029
Re: [Desktop-packages] [Bug 1552029] Re: Intermittently mouse corrupt on one screen
I was rather nervous about doing this. However, it is done. I shall endeavour to try and remember to report its success or failure in resolving the bug. Thank you for your response. On Wednesday, 2 March 2016, 2:05, Christopher M. Penalver <christopher.m.penal...@gmail.com> wrote: Jen Hart, thank you for reporting this and helping make Ubuntu better. As per https://us.msi.com/product/motherboard/support/X99A-SLI-PLUS.html #down-bios an update to your computer's buggy, insecure, and outdated BIOS is available (1.9). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. Also, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible: 1) Please provide the output of the following terminal command (not perform an apport-collect): sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 2) Please make a comment specifically advising on if there was an improvement or not. 3) Please mark this report Status New. If it's not reproducible, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-1.9 ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1552029 Title: Intermittently mouse corrupt on one screen Status in xorg package in Ubuntu: Incomplete Bug description: Tried Gnome tweaks, tried changing monitors around, primary, (in case it was some how port related) etc. Can not reset the mouse cursor once it corrupts. Only solution I found was a reboot, which can be inconvenient. Might be related to Java applications somehow and their borders? P.S. I think my graphics card is R9 390 and has been picked up wrong by this bug report and by one game I know about (it thinks it is a HD 5600) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 2 01:20:06 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.201, 3.19.0-49-generic, x86_64: installed fglrx-updates-core, 15.201, 3.19.0-51-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015] InstallationDate: Installed on 2015-11-24 (98 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MSI MS-7885 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic.efi.signed root=UUID=46953798-0da7-48f9-8837-c446ced8f6f6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7885 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-in
[Desktop-packages] [Bug 1552029] [NEW] Intermittently mouse corrupt on one screen
Public bug reported: Tried Gnome tweaks, tried changing monitors around, primary, (in case it was some how port related) etc. Can not reset the mouse cursor once it corrupts. Only solution I found was a reboot, which can be inconvenient. Might be related to Java applications somehow and their borders? P.S. I think my graphics card is R9 390 and has been picked up wrong by this bug report and by one game I know about (it thinks it is a HD 5600) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Mar 2 01:20:06 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates-core, 15.201, 3.19.0-49-generic, x86_64: installed fglrx-updates-core, 15.201, 3.19.0-51-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2015] InstallationDate: Installed on 2015-11-24 (98 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MSI MS-7885 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-51-generic.efi.signed root=UUID=46953798-0da7-48f9-8837-c446ced8f6f6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99A SLI PLUS(MS-7885) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/20/2015:svnMSI:pnMS-7885:pvr1.0:rvnMSI:rnX99ASLIPLUS(MS-7885):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7885 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Mar 1 10:55:41 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3.1~trusty1 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Description changed: Tried Gnome tweaks, tried changing monitors around, primary, (in case it was some how port related) etc. - Can not reset the mouse cursor once it corrupts. Only solution I found was a reboot, which can be inconvenient. + Can not reset the mouse cursor once it corrupts. Only solution I found was a reboot, which can be inconvenient. Might be related to Java applications somehow and their borders? + + P.S. I think my graphics card is R9 390 and has been picked up wrong by + this bug report and by one game I know about (it thinks it is a HD 5600) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13 Uname: Linux 3.19.0-51-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for
[Desktop-packages] [Bug 1272291] Re: 1002:68b8 [Asus M5A97 EVO] Corrupt mouse cursor when using multimonitors
Radeon R9 390 fglrx-update (proprietary) Corrupt on one screen sometimes. Reboot fixes for a time. Possible link is Java applications. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1272291 Title: 1002:68b8 [Asus M5A97 EVO] Corrupt mouse cursor when using multimonitors Status in xorg package in Ubuntu: Expired Bug description: I have 2 screens, sometimes one of the screens will have the cursor corrupt. Usually looks like the cursor is sliced vertically in about 3-5 slices and put back together in the wrong order. Moving the cursor between screens causes it to change from being fine on one screen to corrupt on the other. Affects not just the arrow, but others as well, such as move, resize and text select. Using the default cursor theme, never changed it. Rebooting fixes it. Sometimes, very rarely (maybe 2 times over the past several years) it will fix on it's own. But those self fixes have only happened if I move the cursor between screens quickly just after it happens, if it's left to be corrupt for a moment or more... it will stay that way until a reboot. Hard to say what causes it or when it happens. Maybe it's more likely to happen when moving a window between screens. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin DistUpgraded: 2013-10-05 23:33:35,358 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.101, 3.11.0-14-generic, x86_64: installed fglrx-updates, 13.101, 3.11.0-15-generic, x86_64: installed virtualbox, 4.2.16, 3.11.0-14-generic, x86_64: installed virtualbox, 4.2.16, 3.11.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:2543] InstallationDate: Installed on 2013-04-28 (271 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) JockeyStatus: ERROR:root:Could not find any typelib for AppIndicator3 kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use) MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True NonfreeKernelModules: fglrx Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=cbbe4688-ab8c-43ac-b0d0-8d0c97d9e9ca ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Tags: saucy ubuntu Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-06 (111 days ago) UserGroups: dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz N/A version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Jan 15 02:06:28 2014 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2~saucy1 xserver.video_driver: fglrx To manage notifications about this bug go to:
[Desktop-packages] [Bug 1359414] [NEW] I don't know
Public bug reported: ? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 20 23:25:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:817a] InstallationDate: Installed on 2002-01-01 (4614 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Olidata S.p.A. System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=f8ed6b3f-29c8-40b7-8ee0-dde0cfc75fc6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5L-VM GB dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0303:bd01/21/2008:svnOlidataS.p.A.:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5L-VMGB:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: Olidata S.p.A. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jan 1 01:00:44 2002 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9056 vendor INL xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1359414 Title: I don't know Status in “xorg” package in Ubuntu: New Bug description: ? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 20 23:25:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:817a] InstallationDate: Installed on 2002-01-01 (4614 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Olidata S.p.A. System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=f8ed6b3f-29c8-40b7-8ee0-dde0cfc75fc6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5L-VM GB dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3
[Desktop-packages] [Bug 1359413] [NEW] I don't know
Public bug reported: ? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 20 23:25:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:817a] InstallationDate: Installed on 2002-01-01 (4614 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Olidata S.p.A. System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=f8ed6b3f-29c8-40b7-8ee0-dde0cfc75fc6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5L-VM GB dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0303:bd01/21/2008:svnOlidataS.p.A.:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5L-VMGB:rvrRev2.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: Olidata S.p.A. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Jan 1 01:00:44 2002 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9056 vendor INL xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1359413 Title: I don't know Status in “xorg” package in Ubuntu: New Bug description: ? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 20 23:25:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:817a] InstallationDate: Installed on 2002-01-01 (4614 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) MachineType: Olidata S.p.A. System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=f8ed6b3f-29c8-40b7-8ee0-dde0cfc75fc6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/21/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0303 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5L-VM GB dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 2.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3
[Desktop-packages] [Bug 1162814] [NEW] package firefox 11.0+build1-0ubuntu0.10.04.2 failed to install/upgrade: trying to overwrite '/usr/lib/firefox/plugins', which is also in package mozilla-plugin-g
Public bug reported: i have no idea. i ran the update and got this my ex installed this i know nothing btw .. it is not charging my battery right either ... says it is charged but if i unplug it the battery is empty .. i replug it and it says it is empty and is charging ... very annoying because not my laptop is essentially a desk top ProblemType: Package DistroRelease: Ubuntu 10.04 Package: firefox 11.0+build1-0ubuntu0.10.04.2 ProcVersionSignature: Ubuntu 2.6.32-42.95-generic 2.6.32.59+drm33.24 Uname: Linux 2.6.32-42-generic i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vrsa 1366 F pulseaudio BuildID: 20120310193829 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xdc24 irq 22' Mixer name : 'Realtek ALC861' Components : 'HDA:10ec0861,11791205,00100300 HDA:11c13026,11790001,00100700' Controls : 11 Simple ctrls : 8 Channel: release Date: Mon Apr 1 07:33:54 2013 ErrorMessage: trying to overwrite '/usr/lib/firefox/plugins', which is also in package mozilla-plugin-gnash 0:0.8.7-0ubuntu1 EtcFirefoxSyspref: Cannot parse /etc/firefox/syspref.js - [Errno 2] No such file or directory: '/etc/firefox/syspref.js' ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IpRoute: 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.15 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.1.1 dev wlan0 proto static NoProfiles: True RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 11.0+build1-0ubuntu0.10.04.2 failed to install/upgrade: trying to overwrite '/usr/lib/firefox/plugins', which is also in package mozilla-plugin-gnash 0:0.8.7-0ubuntu1 WpaSupplicantLog: dmi.bios.date: 08/30/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 2.00 dmi.board.name: MPAD-MSAE Customer Reference Boards dmi.board.vendor: Intel Corporation dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr2.00:bd08/30/2006:svnTOSHIBA:pnSatelliteA105:pvrPSAA8U-14M02K:rvnIntelCorporation:rnMPAD-MSAECustomerReferenceBoards:rvrNotApplicable:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Satellite A105 dmi.product.version: PSAA8U-14M02K dmi.sys.vendor: TOSHIBA ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid release-channel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1162814 Title: package firefox 11.0+build1-0ubuntu0.10.04.2 failed to install/upgrade: trying to overwrite '/usr/lib/firefox/plugins', which is also in package mozilla-plugin-gnash 0:0.8.7-0ubuntu1 Status in “firefox” package in Ubuntu: New Bug description: i have no idea. i ran the update and got this my ex installed this i know nothing btw .. it is not charging my battery right either ... says it is charged but if i unplug it the battery is empty .. i replug it and it says it is empty and is charging ... very annoying because not my laptop is essentially a desk top ProblemType: Package DistroRelease: Ubuntu 10.04 Package: firefox 11.0+build1-0ubuntu0.10.04.2 ProcVersionSignature: Ubuntu 2.6.32-42.95-generic 2.6.32.59+drm33.24 Uname: Linux 2.6.32-42-generic i686 AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vrsa 1366 F pulseaudio BuildID: 20120310193829 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xdc24 irq 22' Mixer name : 'Realtek ALC861' Components : 'HDA:10ec0861,11791205,00100300 HDA:11c13026,11790001,00100700' Controls : 11 Simple ctrls : 8 Channel: release Date: Mon Apr 1 07:33:54 2013 ErrorMessage: trying to overwrite '/usr/lib/firefox/plugins', which is also in package mozilla-plugin-gnash 0:0.8.7-0ubuntu1 EtcFirefoxSyspref: Cannot parse /etc/firefox/syspref.js - [Errno 2] No such file or directory: '/etc/firefox/syspref.js' ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback IpRoute: 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.15 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.1.1 dev wlan0 proto static NoProfiles: True RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons:
