[Desktop-packages] [Bug 1962135] [NEW] Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04
Public bug reported: On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962135 Title: Upgrade defalult gstreamer version 1.16 minor version on ubuntu-20.04 Status in gstreamer1.0 package in Ubuntu: New Bug description: On ubuntu-20.04 "apt-get" default installs gstreamer version 1.16.2, though gstreamer has subsequent minor version gst-1.16.3 with fixes incorporated. Hence, Ideally default gstreamer-1.16 minor version support with ubuntu-20.04 should be upgraded to use gstreamer version 1.16.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962135/+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 1962134] [NEW] Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on
Public bug reported: Following gstreamer critical warning observed on gstreamer version 1.16 on ubuntu-20.04 with nvidia specific gst-v4l2 decoder pipeline: "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" It seems fix for the issue is already incorporated on gstreamer version 1.18 with below: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/a1b41b2b2493069365a8274c6a544e6799a5a8df We need to backport above fix on top of gst-1.16 on ubuntu-20.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.16 on ubuntu-20.04 ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962134 Title: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04 Status in gstreamer1.0 package in Ubuntu: New Bug description: Following gstreamer critical warning observed on gstreamer version 1.16 on ubuntu-20.04 with nvidia specific gst-v4l2 decoder pipeline: "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" It seems fix for the issue is already incorporated on gstreamer version 1.18 with below: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/a1b41b2b2493069365a8274c6a544e6799a5a8df We need to backport above fix on top of gst-1.16 on ubuntu-20.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.16 on ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+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 1962133] [NEW] Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14
Public bug reported: Few specific h264 and h265 RTSP input streams sources when used with nvidia specific gst-v4l2 based gstreamer-1.0 (version gst-1.14 and ubuntu-18.04) decode pipeline intermittently yields very low fps (in the range of [~0/1 fps]). Issue seems caused by the gst_video_decoder_drain_out function erroneously getting called inside gst_video_decoder_chain_forward function. Required changes to fix the issue seems available with gst-1.16 and to resolve the issue need to backport the relevant OSS fixes from gst-1.16 to gst-1.14 on ubuntu-18.04. The mentioned issue was reported on with: https://bugzilla.gnome.org/show_bug.cgi?id=796771 Corresponding fix was incorporated with below: https://github.com/GStreamer/gst-plugins-base/commit/62cb08404b9bd055c45cc1d5b71141e927ad748a We need to backport above fix on top of gst-1.14.5 on ubuntu-18.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.14 on ubuntu-18.04 ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962133 Title: Intermittent very low fps(sometimes zero) with few specific h264 and h265 RTSP input streams sources when used with gst-v4l2 based gstreamer-1.0(version gst-1.14.5) decode pipeline Status in gstreamer1.0 package in Ubuntu: New Bug description: Few specific h264 and h265 RTSP input streams sources when used with nvidia specific gst-v4l2 based gstreamer-1.0 (version gst-1.14 and ubuntu-18.04) decode pipeline intermittently yields very low fps (in the range of [~0/1 fps]). Issue seems caused by the gst_video_decoder_drain_out function erroneously getting called inside gst_video_decoder_chain_forward function. Required changes to fix the issue seems available with gst-1.16 and to resolve the issue need to backport the relevant OSS fixes from gst-1.16 to gst-1.14 on ubuntu-18.04. The mentioned issue was reported on with: https://bugzilla.gnome.org/show_bug.cgi?id=796771 Corresponding fix was incorporated with below: https://github.com/GStreamer/gst-plugins-base/commit/62cb08404b9bd055c45cc1d5b71141e927ad748a We need to backport above fix on top of gst-1.14.5 on ubuntu-18.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.14 on ubuntu-18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962133/+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 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
See https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962127 for an ubuntu-bug of the gnome-shell crash file when this occurred for me yesterday. -- 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/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in gnome-shell package in Ubuntu: Incomplete Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+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 1962093] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563314/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2
[Desktop-packages] [Bug 1962093] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563320/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59
[Desktop-packages] [Bug 1962093] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563317/+files/ProcEnviron.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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59
[Desktop-packages] [Bug 1962093] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563315/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59
[Desktop-packages] [Bug 1962093] NetDevice.virbr0.txt
apport information ** Attachment added: "NetDevice.virbr0.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563313/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb
[Desktop-packages] [Bug 1962093] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563319/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59
[Desktop-packages] [Bug 1962093] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563318/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59
[Desktop-packages] [Bug 1962093] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563316/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2
[Desktop-packages] [Bug 1962093] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563308/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59
[Desktop-packages] [Bug 1962093] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563312/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24
[Desktop-packages] [Bug 1962093] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563307/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24
[Desktop-packages] [Bug 1962093] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563309/+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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59
[Desktop-packages] [Bug 1962093] NetDevice.enp5s0.txt
apport information ** Attachment added: "NetDevice.enp5s0.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563311/+files/NetDevice.enp5s0.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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb
[Desktop-packages] [Bug 1962093] NetDevice.enp4s1.txt
apport information ** Attachment added: "NetDevice.enp4s1.txt" https://bugs.launchpad.net/bugs/1962093/+attachment/5563310/+files/NetDevice.enp4s1.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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb
[Desktop-packages] [Bug 1962093] Re: network-manager can't connect to pppoe since version 1.35.90
apport information ** Tags added: apport-collected jammy ** Description changed: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8774] device (enp4s1): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8777] manager: NetworkManager state is now CONNECTED_LOCAL Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8779] device (enp4s1):
[Desktop-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported
python-b2sdk was removed from jammy in LP: #1961976 ** Changed in: python-b2sdk (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: Fix Released Status in pygobject package in Ubuntu: Fix Released Status in pytest-twisted package in Ubuntu: Fix Committed Status in python-b2sdk package in Ubuntu: Fix Released Status in python-hypothesis package in Ubuntu: Fix Released Status in python-taskflow package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: Fix Released Status in vorta package in Ubuntu: Fix Released Status in ipywidgets package in Debian: New Status in pygobject package in Debian: Fix Released Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: Confirmed Status in python-hypothesis package in Debian: Fix Released Status in supysonic package in Debian: Fix Released Status in vorta package in Debian: Fix Released Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+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 1962060] Re: problem in libreoffice draw
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1962060 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: libreoffice (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1962060 Title: problem in libreoffice draw Status in libreoffice package in Ubuntu: Incomplete Bug description: I am running libreoffice-draw 1:6.4.2-0ubuntu3 on an amd64 cpu under Ubuntu 20.04. The desktop mgr is gnome-flashback 3.36.1-1ubuntu1 I want to change the properties of text in a textbox, but cannot see the "tools" menu, and so cannot make sub- and super-scripts, bold, etc. Also, drawings created in my previous Draw (in Ubuntu 16.04) don't import correctly - especially text objects. For example, sub- and super-scripts don't import well - instead I see lots of solid black triangles with white exclamation points. I rummaged around the web looking for solutions but found mainly old bug reports and no useful resolutions, and the "DrawGuide 7.1" under "Text Formatting" only refers to toolbars that do not appear on my screen Why, oh why, have you made things so very complicated? I understand that it is in the nature of Developers to develop, but how about (like gnome-flashback) giving the option of a slightly less capable "retro-interface" so that users don't have to fight their way through myriad changes (and bugs) to use the new version (which I haven't figured out how to avoid). It would greatly assist our productivity. Happy to discuss this further. Best Regards, eter...@whoi.edu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1962060/+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 1962093] Re: network-manager can't connect to pppoe since version 1.35.90
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1962093 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1962093 Title: network-manager can't connect to pppoe since version 1.35.90 Status in network-manager package in Ubuntu: Incomplete Bug description: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP)
[Desktop-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
@Jason, could you help to check this issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Confirmed Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1962123] [NEW] When opening a video file Totem complains of missing codecs but video plays correctly
Public bug reported: When opening a video in Totem it will show an Unable to play this file warning and give you the option to Cancel or Find in Ubuntu Software. If you click on Find in Ubuntu Software the video will start playing correctly. The software store will but not find any codecs. I have tried this with a few videos and Totem behaves that same way, but all videos play correctly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 24 18:24:40 2022 InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1962123 Title: When opening a video file Totem complains of missing codecs but video plays correctly Status in totem package in Ubuntu: New Bug description: When opening a video in Totem it will show an Unable to play this file warning and give you the option to Cancel or Find in Ubuntu Software. If you click on Find in Ubuntu Software the video will start playing correctly. The software store will but not find any codecs. I have tried this with a few videos and Totem behaves that same way, but all videos play correctly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 24 18:24:40 2022 InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1962123/+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 1869086] Re: Firmware upgrade always notifies to reboot the device even on immediate failure
Marco - is this still occurring in recent versions of snap-store? Does it also occur in gnome-software? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869086 Title: Firmware upgrade always notifies to reboot the device even on immediate failure Status in snap-store-desktop: Triaged Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Focal: Triaged Bug description: If the firmware update request fails because of a network error or because the AC power is not plugged, or any other problem, gnome- software shows an error in an in-app notification, while sends a resident notification to gnome-shell that requests the user to restart the system, even if this is not really required. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1869086/+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 1936907] Re: [MIR] ADSys
I reviewed adsys 0.8 as checked into jammy. This shouldn't be considered a full audit but rather a quick gauge of maintainability. As usual with golang code, there's vastly more code in the package than we've authored, and it's not feasible to review the entirety. adsys allows network administrators to include Ubuntu systems in Windows Group Policy ecosystem. There's easy support for a lot of individual tunable elements, as well as generic support for running both machine and user scripts on login, logout, etc. - CVE History: none :) - Build-Depends? Build-Depends: debhelper-compat (= 13), dh-apport, dh-golang, golang-go (>= 2:1.16~), libsmbclient-dev, libdbus-1-dev, python3, python3-samba, samba-dsdb-modules, libpam0g-dev, samba, dbus, - pre/post inst/rm scripts? mostly added automatically by dh_ helpers; registers and unregisters pam module, enables systemd units, purges and unmasks systemd units, etc. - init scripts? none - systemd units? sets up socket activation, sets up timers, refreshes policies, runs machine scripts in machine units, runs user scripts in user units - dbus services? none - setuid binaries? none - binaries in PATH? adsysd, adsysctl - sudo fragments? /etc/sudoers.d/99-adsys-privilege-enforcement is under control of the application: "%admin ALL=(ALL) !ALL\n" "%sudo ALL=(ALL:ALL) !ALL\n" contentSudo += fmt.Sprintf("\"%s\" ALL=(ALL:ALL) ALL\n", e) these are very powerful; I'd appreciate a second set of eyes here :) - polkit files? yes, seems reasonable - udev rules? none - unit tests / autopkgtests? yes, many tests, run during the build - cron jobs? none, systemd timer units used instead - Build logs: the shell completion files are dumped during build, it's a bit noisy, but otherwise looks clean - Processes spawned? Yes -- pam module, copied from pam_exec.c Yes -- adsys spawned from the user manager will run scripts, seems okay - Memory management? Most is golang, safe enough pam module has some memory leaks; when reported to upstream pam_exec.c folks, they appear to be leaning towards leaking even more memory :) so probably fine. - File IO? Some issues, raised elsewhere. - Logging? pam module looked fine - Environment variable usage? NO_COLOR and KRB5CCNAME, seemed safe - Use of privileged functions? chown - Use of cryptography / random number sources etc? none - Use of temp files? none - Use of networking? grpc; to the extent I looked at it, it felt safe enough - Use of WebKit? none - Use of PolicyKit? yes, internal/authorizer/authorizer.go looks up process start time by searching *backwards* through /proc/pid/stat file for a ), then looking forward 19 fields. I didn't double-check the math but it sure sounds promising. - Any significant cppcheck results? memory leaks in pam_adsys.c, upstream for inspiration pam_exec didn't seem bothered - Any significant Coverity results? none - Any significant shellcheck results? none - Any significant bandit results? none adsys is carefully written, well-documented, and didrocks and jibel were very responsive to comments and feedback. Security team ACK for promoting adsys to main. I filed a few bugs along the way: https://github.com/grpc/grpc-go/issues/5137 https://github.com/olekukonko/tablewriter/issues/199 And some miscellaneous notes I took: Are there any conditions that can be added to adsys-boot.service to make it less likely to spam the journal every five seconds for ten hours when on an airplane? https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1961459 pam_adsys.c update_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() arggv leak in fork() failure pam_adsys.c update_machine_policy() -- status != 0 looks like it ought to work but I don't think that's how that API is supposed to be used pam_adsys.c pam_sm_open_session() -- gethostname() indentation is funny https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1961458 [redacted] ./internal/policies/scripts/scripts.go -- typo %qto ./conf.example/adsys.yaml ./doc/5.-The-adsys-daemon.md Both these use /tmp/adsysd/ .. paths in configuration files -- is this the recommended way to use adsys? It'd be nice if the configs were "real", production-ready, defaults, etc. ** Bug watch added: github.com/grpc/grpc-go/issues #5137 https://github.com/grpc/grpc-go/issues/5137 ** Bug watch added: github.com/olekukonko/tablewriter/issues #199 https://github.com/olekukonko/tablewriter/issues/199 ** Changed in: adsys (Ubuntu) Status: New => In Progress ** Changed in: adsys (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu.
[Desktop-packages] [Bug 1962100] [NEW] package yaru-theme-gnome-shell 20.04.11.1 failed to install/upgrade: installed yaru-theme-gnome-shell package post-installation script subprocess returned error
Public bug reported: isuue about the theme. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: yaru-theme-gnome-shell 20.04.11.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 24 08:22:55 2022 Dependencies: DuplicateSignature: package:yaru-theme-gnome-shell:20.04.11.1 Setting up yaru-theme-gnome-shell (20.04.11.1) ... update-alternatives: error: cannot stat file '/etc/alternatives/gdm3-theme.gresource': Invalid argument dpkg: error processing package yaru-theme-gnome-shell (--configure): installed yaru-theme-gnome-shell package post-installation script subprocess returned error exit status 2 ErrorMessage: installed yaru-theme-gnome-shell package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2022-02-22 (2 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: yaru-theme Title: package yaru-theme-gnome-shell 20.04.11.1 failed to install/upgrade: installed yaru-theme-gnome-shell package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1962100 Title: package yaru-theme-gnome-shell 20.04.11.1 failed to install/upgrade: installed yaru-theme-gnome-shell package post-installation script subprocess returned error exit status 2 Status in yaru-theme package in Ubuntu: New Bug description: isuue about the theme. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: yaru-theme-gnome-shell 20.04.11.1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 24 08:22:55 2022 Dependencies: DuplicateSignature: package:yaru-theme-gnome-shell:20.04.11.1 Setting up yaru-theme-gnome-shell (20.04.11.1) ... update-alternatives: error: cannot stat file '/etc/alternatives/gdm3-theme.gresource': Invalid argument dpkg: error processing package yaru-theme-gnome-shell (--configure): installed yaru-theme-gnome-shell package post-installation script subprocess returned error exit status 2 ErrorMessage: installed yaru-theme-gnome-shell package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2022-02-22 (2 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: yaru-theme Title: package yaru-theme-gnome-shell 20.04.11.1 failed to install/upgrade: installed yaru-theme-gnome-shell package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1962100/+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 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: modemmanager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: Confirmed Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1962029] Re: Change default click-action for ubuntu-dock to focus-minimize-or-previews
*** This bug is a duplicate of bug 1723835 *** https://bugs.launchpad.net/bugs/1723835 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1723835, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - change default click-action for ubuntu-dock + Change default click-action for ubuntu-dock to focus-minimize-or-previews ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Wishlist ** This bug has been marked a duplicate of bug 1723835 Dock - Clicking icon doesn't minimize -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1962029 Title: Change default click-action for ubuntu-dock to focus-minimize-or- previews Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: hi, issue overview: since last few releases of dash-to-dock extension, a new click-action named focus-minimize-or-previews has been introduced that does the same thing as focus-or-previews but also adds the ability to minimize. many ubuntu-desktop users have asked frequently in discourse.ubuntu.com threads for the default click action of ubuntu- dock to be minimize.It would be a better balance/compromise to change the default click action to focus-minimize-or-previews for ubuntu-22.04 with this change ubuntu-desktop users wouldn't have to look into online outdated-guides to manually change it to minimize click-action. proposal: - change ubuntu-dock click-actions's default from focus-or-previews to focus-minimize-or-previews. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1962029/+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 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Tags added: jammy -- 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/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in gnome-shell package in Ubuntu: Incomplete Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+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 1857392] Re: Window manager warning: Overwriting existing binding of keysym...
System hangs are not related to this bug. Please open a new bug for that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1857392 Title: Window manager warning: Overwriting existing binding of keysym... Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+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 1962049] Re: gnome-shell memory usage indefinitely increases and I can’t restart gnome-shell while in Wayland. Don’t know what to do to reduce it
Maybe try removing gsconnect first (bug 1812892). ** 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/1962049 Title: gnome-shell memory usage indefinitely increases and I can’t restart gnome-shell while in Wayland. Don’t know what to do to reduce it Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell memory usage indefinitely increases while using it. I can’t restart the shell (Alt+Fn+F2) while in Wayland and the only way to reduce this memory usage is to close the session. I don’t know what to do and many others too. Best regards and thanks to all developers from France. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 23 21:51:40 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00+beaver-osp1-sansa+X24.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962049/+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 1962049] Re: gnome-shell memory usage indefinitely increases and I can’t restart gnome-shell while in Wayland. Don’t know what to do to reduce it
Thanks for the bug report. First please uninstall all of these extensions, or at least disable them in the Extensions app and then log in again: 'user-th...@gnome-shell-extensions.gcampax.github.com', 'sto...@infinicode.de', 'bitcoin-mark...@ottoallmendinger.github.com', 'compiz-windows-eff...@hermes83.github.com', 'shellsh...@gfxmonk.net', 'keypadtil...@abakkk.framagit.org', 'BigSurStatusArea@korpsvart', 'BigSurMenu@korpsvart', 'bigSur-StatusArea@korpsvart', 'focus- effe...@paradoxxx.zero.gmail.com', 'b...@yozoon.dev.gmail.com', 'b...@zacbarton.com', 'shellt...@emasab.it', 'ubuntu- appindicat...@ubuntu.com', 'apps-menu@gnome-shell- extensions.gcampax.github.com', 'clipboard-indica...@tudmotu.com', 'compiz-alike-windows-eff...@hermes83.github.com', 'openweather- extens...@jenslody.de', 'tiling-assistant@leleat-on-github', 'floating- dock@nandoferreira_p...@hotmail.com', 'gestureImprovements@gestures', 'auto-move-wind...@gnome-shell-extensions.gcampax.github.com', 'gamem...@christian.kellner.me', 'gnome-ui-t...@itstime.tech', 'gsconn...@andyholmes.github.io', 'noannoya...@daase.net', 'system- moni...@paradoxxx.zero.gmail.com', 'blur-my-shell@aunetx' This is the first thing to try because all known gnome-shell memory leaks are leaks in extensions. ** Tags added: gnome-shell-leak -- 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/1962049 Title: gnome-shell memory usage indefinitely increases and I can’t restart gnome-shell while in Wayland. Don’t know what to do to reduce it Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell memory usage indefinitely increases while using it. I can’t restart the shell (Alt+Fn+F2) while in Wayland and the only way to reduce this memory usage is to close the session. I don’t know what to do and many others too. Best regards and thanks to all developers from France. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 23 21:51:40 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00+beaver-osp1-sansa+X24.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962049/+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 1962093] [NEW] network-manager can't connect to pppoe since version 1.35.90
Public bug reported: System:kubuntu 22.04 I create a Dsl connection with network-manager and it works ideal before I upgrading the network-manager from 1.35.8X to the higher. Now I can't connect to the Dsl, the network-manager reports errors. I found the messages in the syslogs as this: Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3773] ppp-manager: starting PPP connection Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.3788] ppp-manager: pppd started with pid 1897 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin rp-pppoe.so loaded. Feb 24 08:53:59 kUbuntu-Server kernel: [ 184.286354] r8169 :04:01.0 enp4s1: Link is Up - 1Gbps/Full - flow control rx/tx Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Plugin /usr/lib/pppd/2.4.9/nm-pppd-plugin.so loaded. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: initializing Feb 24 08:53:59 kUbuntu-Server pppd[1897]: pppd 2.4.9 started by root, uid 0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 3 / phase 'serial connection' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PPP session is 56656 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connected to cc:1a:fa:e8:2a:20 via interface enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 5 / phase 'establish' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Using interface ppp0 Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Connect: ppp0 <--> enp4s1 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.5519] manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/10) Feb 24 08:53:59 kUbuntu-Server systemd-udevd[1900]: Using default interface naming scheme 'v249'. Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 6 / phase 'authenticate' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: passwd-hook, requesting credentials... Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: got credentials from NetworkManager Feb 24 08:53:59 kUbuntu-Server pppd[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: Remote message: SUCCESS. Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 8 / phase 'network' Feb 24 08:53:59 kUbuntu-Server pppd[1897]: PAP authentication succeeded Feb 24 08:53:59 kUbuntu-Server pppd[1897]: peer from calling number CC:1A:FA:E8:2A:20 authorized Feb 24 08:53:59 kUbuntu-Server pppd[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: nm-ppp-plugin: status 9 / phase 'running' Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: local IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: remote IP address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8762] device (ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server pppd[1897]: primary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server pppd[1897]: secondary DNS address *.*.*.*(I marked the IP) Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8767] device (ppp0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8773] device (enp4s1): could not take control of link 10: the device already has ifindex 2 Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8774] device (enp4s1): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed') Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8777] manager: NetworkManager state is now CONNECTED_LOCAL Feb 24 08:53:59 kUbuntu-Server NetworkManager[703]: [1645664039.8779] device (enp4s1): Activation: failed for connection 'PPPonEnp4s1' ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug
[Desktop-packages] [Bug 1962060] Re: problem in libreoffice draw
** Project changed: pkg-website => libreoffice (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1962060 Title: problem in libreoffice draw Status in libreoffice package in Ubuntu: New Bug description: I am running libreoffice-draw 1:6.4.2-0ubuntu3 on an amd64 cpu under Ubuntu 20.04. The desktop mgr is gnome-flashback 3.36.1-1ubuntu1 I want to change the properties of text in a textbox, but cannot see the "tools" menu, and so cannot make sub- and super-scripts, bold, etc. Also, drawings created in my previous Draw (in Ubuntu 16.04) don't import correctly - especially text objects. For example, sub- and super-scripts don't import well - instead I see lots of solid black triangles with white exclamation points. I rummaged around the web looking for solutions but found mainly old bug reports and no useful resolutions, and the "DrawGuide 7.1" under "Text Formatting" only refers to toolbars that do not appear on my screen Why, oh why, have you made things so very complicated? I understand that it is in the nature of Developers to develop, but how about (like gnome-flashback) giving the option of a slightly less capable "retro-interface" so that users don't have to fight their way through myriad changes (and bugs) to use the new version (which I haven't figured out how to avoid). It would greatly assist our productivity. Happy to discuss this further. Best Regards, eter...@whoi.edu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1962060/+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 1962060] [NEW] problem in libreoffice draw
You have been subscribed to a public bug: I am running libreoffice-draw 1:6.4.2-0ubuntu3 on an amd64 cpu under Ubuntu 20.04. The desktop mgr is gnome-flashback 3.36.1-1ubuntu1 I want to change the properties of text in a textbox, but cannot see the "tools" menu, and so cannot make sub- and super-scripts, bold, etc. Also, drawings created in my previous Draw (in Ubuntu 16.04) don't import correctly - especially text objects. For example, sub- and super-scripts don't import well - instead I see lots of solid black triangles with white exclamation points. I rummaged around the web looking for solutions but found mainly old bug reports and no useful resolutions, and the "DrawGuide 7.1" under "Text Formatting" only refers to toolbars that do not appear on my screen Why, oh why, have you made things so very complicated? I understand that it is in the nature of Developers to develop, but how about (like gnome-flashback) giving the option of a slightly less capable "retro-interface" so that users don't have to fight their way through myriad changes (and bugs) to use the new version (which I haven't figured out how to avoid). It would greatly assist our productivity. Happy to discuss this further. Best Regards, eter...@whoi.edu ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- problem in libreoffice draw https://bugs.launchpad.net/bugs/1962060 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. -- 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 1962056] Re: ubuntu mate 20.04.4 on adjusting display positions to match setup; one display background now blocky-flashy
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1962056 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1962056 Title: ubuntu mate 20.04.4 on adjusting display positions to match setup; one display background now blocky-flashy Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Ubuntu-MATE QA-test install of 20.04.4 RC - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) NOTE: I bet this is a duplicate; but quickly sorry for QA-test records. Maybe filed on wrong package sorry (maybe why I'm not finding it). Issue looks identical to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1942561 (that was impish) Post-install checks I adjusted monitor to match my setup (one display above the other) On lower display, the background is now blocky-somewhat-flashy (on changes to screen (including just moving the mouse IF mouse is on the other screen! but not my-lower screen) or blinking of a cursor in a data entry field) The issue is only background, if TERMINAL or any window is maximized; the issue is gone (ie. blocky-flashy(changing graphics) is only occurring on background; windows are drawn correctly on issue. See attached picture. As I continued to use the system though (exploring it as I type this up on my primary box) the issue suddenly disappeared.. and it's now good. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Thu Feb 24 09:34:24 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=adf6196a-fec3-4c48-942c-a9b9b389de82 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:skuET090AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1962056/+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 1942561] Re: ubuntu-mate impish install; graphics on one display warped on display.position adjustment
Almost identical issue on 20.04.4 - https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1962056 related to kernel (module)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1942561 Title: ubuntu-mate impish install; graphics on one display warped on display.position adjustment Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Ubuntu MATE impish QA-test install to - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) NOTE: this or like issue is experienced with Ubuntu (GNOME) & Kubuntu (KDE) so it's not surprising. It does not occur on Xubuntu & Lubuntu though. Daniel (vanvugt) has suggested this box should only be used for 20.04; bugs in nouveau are difficult for Ubuntu to track down.. but this box is what I have for QA-installs. Related (possibly duplicates) - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930945 (Ubuntu GNOME desktop) - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919266 (Kubuntu KDE desktop) Install worked flawlessly except the adjust.screens.to.match.my.setup which I consider part of system shakedown.. ** Expected results I expect on adjust screens, I can read both screens ** Actual results My top.display remained readable; lower display had become a somewhat garbled mess (refer pics) Of NOTE: I can click the 'hide all windows & show desktop' and screen muck up was gone in an instant; hit it again & windows were returned & usable. MINOR ISSUE as relates to specific OLD nvidia graphics card(s?) ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-video-nouveau 1:1.0.17-1 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: MATE Date: Fri Sep 3 17:57:23 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] InstallationDate: Installed on 2021-09-03 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210903) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-14-generic root=UUID=27bd4e3d-7a58-434f-b833-a1d616e66b9e ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:skuET090AV:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.4-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1942561/+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 1962056] Re: ubuntu mate 20.04.4 on adjusting display positions to match setup; one display background now blocky-flashy
** Description changed: - Ubuntu-MATE QA-test install of 20.04.4 RC + Ubuntu-MATE QA-test install of 20.04.4 RC + - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) - (I'll add here shortly) + NOTE: I bet this is a duplicate; but quickly sorry for QA-test records. + Maybe filed on wrong package sorry (maybe why I'm not finding it) + + Post-install checks I adjusted monitor to match my setup (one display + above the other) + + On lower display, the background is now blocky-somewhat-flashy (on + changes to screen (including just moving the mouse IF mouse is on the + other screen! but not my-lower screen) or blinking of a cursor in a data + entry field) + + The issue is only background, if TERMINAL or any window is maximized; + the issue is gone (ie. blocky-flashy(changing graphics) is only + occurring on background; windows are drawn correctly on issue. + + See attached picture. + + As I continued to use the system though (exploring it as I type this up + on my primary box) the issue suddenly disappeared.. and it's now good. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Thu Feb 24 09:34:24 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] + NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=adf6196a-fec3-4c48-942c-a9b9b389de82 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:skuET090AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Description changed: - Ubuntu-MATE QA-test install of 20.04.4 RC + Ubuntu-MATE QA-test install of 20.04.4 RC - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) NOTE: I bet this is a duplicate; but quickly sorry for QA-test records. - Maybe filed on wrong package sorry (maybe why I'm not finding it) + Maybe filed on wrong package sorry (maybe why I'm not finding it). + + Issue looks identical to + https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- + nouveau/+bug/1942561 (that was impish) Post-install checks I adjusted monitor to match my setup (one display above the other) On lower display, the background is now blocky-somewhat-flashy (on changes to screen (including just moving the mouse IF mouse is on the other screen! but not my-lower screen) or blinking of a cursor in a data entry field) The issue is only background, if TERMINAL or any window is maximized; the issue is gone (ie. blocky-flashy(changing graphics) is only occurring on background; windows are drawn correctly on issue. See attached picture. As I continued to use the system though (exploring it as I type this up on my primary box) the issue suddenly disappeared.. and it's now good. - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux
[Desktop-packages] [Bug 1767542] Re: Turning off WiFi enables Airplane mode
I am unable to duplicate this issue on Ubuntu 22.04. Maybe this was fixed in gnome-control-center 40. ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released ** Changed in: gnome-control-center Importance: High => Undecided ** Changed in: gnome-control-center Status: Confirmed => New ** Changed in: gnome-control-center Remote watch: GNOME Bug Tracker #59 => None ** Changed in: gnome-control-center Status: New => Fix Released -- 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/1767542 Title: Turning off WiFi enables Airplane mode Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Turning off the WiFi from the top right control enables Airplane mode (see screenshots). Also after turning off airplane mode, the Wi-Fi is not turned back on, rather the Bluetooth is. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 17:46:34 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1767542/+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 1962056] [NEW] ubuntu mate 20.04.4 on adjusting display positions to match setup; one display background now blocky-flashy
Public bug reported: Ubuntu-MATE QA-test install of 20.04.4 RC (I'll add here shortly) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Thu Feb 24 09:34:24 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=adf6196a-fec3-4c48-942c-a9b9b389de82 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:skuET090AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "Screenshot at 2022-02-24 09-33-04.png" https://bugs.launchpad.net/bugs/1962056/+attachment/5563157/+files/Screenshot%20at%202022-02-24%2009-33-04.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1962056 Title: ubuntu mate 20.04.4 on adjusting display positions to match setup; one display background now blocky-flashy Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Ubuntu-MATE QA-test install of 20.04.4 RC (I'll add here shortly) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: MATE Date: Thu Feb 24 09:34:24 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492] InstallationDate: Installed on 2022-02-23 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=adf6196a-fec3-4c48-942c-a9b9b389de82 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2006 dmi.bios.release: 1.5 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E1 v01.05 dmi.board.name: 0A54h dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:br1.5:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:skuET090AV: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dc7700 Small Form Factor dmi.product.sku: ET090AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ub
[Desktop-packages] [Bug 1961898] Re: chromium-browser is refusing to start
i have disk space (1.1GB /home & 1.5 /) i logged out of GNOME desktop & into Lubuntu/LXQt and same error I also noted `telegram` wasn't running, in fact it appears to be an issue with all snaps guiverc@d960-ubu2:~$ chromium-browser internal error, please report: running "chromium" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/1729 finished with result failed guiverc@d960-ubu2:~$ telegram-desktop internal error, please report: running "telegram-desktop" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/1733 finished with result failed guiverc@d960-ubu2:~$ guiverc@d960-ubu2:~$ wethr internal error, please report: running "wethr" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/1737 finished with result failed ** Package changed: chromium-browser (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1961898 Title: chromium-browser is refusing to start Status in snapd package in Ubuntu: New Bug description: Ubuntu jammy box. I woke my box this morning & resumed it (from suspend; LXQt session) & everything was normal (many apps including chromium-browser visible on displays). I can't say when I last logged in (many days no doubt!), but I shutdown session to use box for QA-test & comment on bug report. After normal reboot & logging in though I tried opening `chromium` many times but nothing happened (from dock in GNOME). As most of what I do is in `firefox` I ignored it... It's been like that several hours with occasional tries & no exploration as to issue. On opening a terminal to try and open `chromium-browser` I get the following -- guiverc@d960-ubu2:~$ chromium-browser internal error, please report: running "chromium" failed: transient scope could not be started, job /org/freedesktop/systemd1/job/771 finished with result failed -- In `journalctl` I notice -- Feb 23 17:53:01 d960-ubu2 sudo[74762]: guiverc : TTY=pts/0 ; PWD=/home/guiverc ; USER=root ; COMMAND=/usr/bin/journalctl Feb 23 17:53:01 d960-ubu2 sudo[74762]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Couldn't move process 74970 to requested cgrou> Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Failed to add PIDs to scope's control group: P> Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Failed with result 'resources'. Feb 23 17:53:07 d960-ubu2 systemd[12489]: Failed to start snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope. Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Couldn't move process 74994 to requested c> Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Failed to add PIDs to scope's control grou> Feb 23 17:53:07 d960-ubu2 systemd[12489]: snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Failed with result 'resources'. Feb 23 17:53:07 d960-ubu2 systemd[12489]: Failed to start snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope. Feb 23 17:53:07 d960-ubu2 polkitd(authority=local)[48397]: Registered Authentication Agent for unix-process:74411:1109253 (system bus name :1.183 [pkttyage> Feb 23 17:53:11 d960-ubu2 polkit-agent-helper-1[75023]: pam_ecryptfs: pam_sm_authenticate: /home/guiverc is already mounted Feb 23 17:53:11 d960-ubu2 polkitd(authority=local)[48397]: Operator of unix-session:10 successfully authenticated as unix-user:guiverc to gain ONE-SHOT aut> Feb 23 17:53:11 d960-ubu2 pkexec[75020]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000) Feb 23 17:53:11 d960-ubu2 pkexec[75020]: guiverc: Executing command [USER=root] [TTY=/dev/pts/1] [CWD=/home/guiverc] [COMMAND=/usr/bin/dmesg] -- I see a snap-confine error in `dmesg` but I don't think its related (nothing else is even close) [ 9697.594155] audit: type=1400 audit(1645597770.987:130): apparmor="DENIED" operation="capable" profile="/snap/core/12725/usr/lib/snapd/snap-confine" pid=73276 comm="snap-confine" capability=4 capname="fsetid" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DRM.card0-DVI-I-1: enabled: enabled dpms: On status: connected edid-base64:
[Desktop-packages] [Bug 1962049] [NEW] gnome-shell memory usage indefinitely increases and I can’t restart gnome-shell while in Wayland. Don’t know what to do to reduce it
Public bug reported: The gnome-shell memory usage indefinitely increases while using it. I can’t restart the shell (Alt+Fn+F2) while in Wayland and the only way to reduce this memory usage is to close the session. I don’t know what to do and many others too. Best regards and thanks to all developers from France. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 23 21:51:40 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00+beaver-osp1-sansa+X24.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session -- 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/1962049 Title: gnome-shell memory usage indefinitely increases and I can’t restart gnome-shell while in Wayland. Don’t know what to do to reduce it Status in gnome-shell package in Ubuntu: New Bug description: The gnome-shell memory usage indefinitely increases while using it. I can’t restart the shell (Alt+Fn+F2) while in Wayland and the only way to reduce this memory usage is to close the session. I don’t know what to do and many others too. Best regards and thanks to all developers from France. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-30.33-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Feb 23 21:51:40 2022 DisplayManager: gdm3 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00+beaver-osp1-sansa+X24.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962049/+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 1962043] [NEW] libwacom9 : depends on : libwacom-common
Public bug reported: Broken denpendency on ARM64: (rpi4 @ ubuntu 22.04 test) libwacom9 : depend on: libwacom-common (= 2.1.0-2) but will be installed 1.12-1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwacom-common 1.12-1 ProcVersionSignature: Ubuntu 5.15.0-1002.2-raspi 5.15.12 Uname: Linux 5.15.0-1002-raspi aarch64 ApportVersion: 2.20.11-0ubuntu78 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Wed Feb 23 21:03:57 2022 Dependencies: DistUpgraded: 2022-02-11 12:31:30,541 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: wireguard/1.0.20210606: added GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:7D:95:B4 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: libwacom UpgradeStatus: Upgraded to jammy on 2022-02-11 (12 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: libwacom (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image has-workaround jammy raspi-image reproducible ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1962043 Title: libwacom9 : depends on : libwacom-common Status in libwacom package in Ubuntu: New Bug description: Broken denpendency on ARM64: (rpi4 @ ubuntu 22.04 test) libwacom9 : depend on: libwacom-common (= 2.1.0-2) but will be installed 1.12-1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libwacom-common 1.12-1 ProcVersionSignature: Ubuntu 5.15.0-1002.2-raspi 5.15.12 Uname: Linux 5.15.0-1002-raspi aarch64 ApportVersion: 2.20.11-0ubuntu78 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Wed Feb 23 21:03:57 2022 Dependencies: DistUpgraded: 2022-02-11 12:31:30,541 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: wireguard/1.0.20210606: added GraphicsCard: ImageMediaBuild: 20201022 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sk_SK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:7D:95:B4 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: libwacom UpgradeStatus: Upgraded to jammy on 2022-02-11 (12 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.109-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.14-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1962043/+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 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
Seems related to https://bugs.launchpad.net/bugs/1962036 -- 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/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in gnome-shell package in Ubuntu: Confirmed Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+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 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
Yes, it's wayland what it's using -- 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/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in gnome-shell package in Ubuntu: Confirmed Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+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 1962033] [NEW] [TUXEDO Aura 15 Gen1, Realtek ALC293, Speaker, Internal] No sound at all
Public bug reported: I got no audio, despite restart the service with suggested command lines ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-10027.29~20.04.1tux1-tuxedo 5.13.19 Uname: Linux 5.13.0-10027-tuxedo x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alaeddine 8183 F pulseaudio /dev/snd/controlC0: alaeddine 8183 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 23 19:10:53 2022 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alaeddine 8183 F pulseaudio /dev/snd/controlC0: alaeddine 8183 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [TUXEDO Aura 15 Gen1, Realtek ALC293, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2021 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08TTR3 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL5xRU dmi.board.vendor: NB01 dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TUXEDO dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08TTR3:bd03/18/2021:br7.8:svnTUXEDO:pnTUXEDOAura15Gen1:pvrNotApplicable:rvnNB01:rnNL5xRU:rvrNotApplicable:cvnTUXEDO:ct10:cvrN/A:skuAURA1501: dmi.product.family: Not Applicable dmi.product.name: TUXEDO Aura 15 Gen1 dmi.product.sku: AURA1501 dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1962033 Title: [TUXEDO Aura 15 Gen1, Realtek ALC293, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: I got no audio, despite restart the service with suggested command lines ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-10027.29~20.04.1tux1-tuxedo 5.13.19 Uname: Linux 5.13.0-10027-tuxedo x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alaeddine 8183 F pulseaudio /dev/snd/controlC0: alaeddine 8183 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 23 19:10:53 2022 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alaeddine 8183 F pulseaudio /dev/snd/controlC0: alaeddine 8183 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [TUXEDO Aura 15 Gen1, Realtek ALC293, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2021 dmi.bios.release: 7.8 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.08TTR3 dmi.board.asset.tag: Tag 12345 dmi.board.name: NL5xRU dmi.board.vendor: NB01 dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TUXEDO dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.08TTR3:bd03/18/2021:br7.8:svnTUXEDO:pnTUXEDOAura15Gen1:pvrNotApplicable:rvnNB01:rnNL5xRU:rvrNotApplicable:cvnTUXEDO:ct10:cvrN/A:skuAURA1501: dmi.product.family: Not Applicable dmi.product.name: TUXEDO Aura 15 Gen1 dmi.product.sku: AURA1501 dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1962033/+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 1961998] Re: alsamixer: volume controls are assigned to wrong channels
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1961998 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: alsa-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1961998 Title: alsamixer: volume controls are assigned to wrong channels Status in alsa-utils package in Ubuntu: Incomplete Bug description: I have tested the alsamixer with 2 different 8ch usb sound cards (UAC2 compatible) and the assignment of the volume controls to the respective channel is partly wrong on both cards. The volume control for rear changes the volume of the center and subwoofer/LFE and the volume control for "Center" and "Woofer" changes the volume of the rear speakers. According to the usb audio class 2 specification, chapter "4.1 Audio Channel Cluster Descriptor", the volume controls index must be (for a 8ch sound card): 1 = FL 2 = FR 3 = C 4 = LFE 5 = RL 6 = RR 7 = SL 8 = SR The current implementation as following assignment: 1 = FL 2 = FR 3 = RL 4 = RR 5 = C 6 = LFE 7 = SL 8 = SR Unfortunately, I can not judge whether this is a problem in the program or driver (audio usb). If you have any questions, feel free to contact me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1961998/+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 1962000] Re: alsamixer: Main volume is named as "Volume 1"
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1962000 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: alsa-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1962000 Title: alsamixer: Main volume is named as "Volume 1" Status in alsa-utils package in Ubuntu: Incomplete Bug description: It's only confusing labeling: The master or main volume of a 8ch usb sound card is labeled as "volume 1" in the alsamixer. It would be more intuitive if the control is named master or main volume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1962000/+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 1698173] Re: I can't change my desktop resolution in ubuntu 16.04
** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1698173 Title: I can't change my desktop resolution in ubuntu 16.04 Status in xorg package in Ubuntu: Invalid Bug description: Hello Sir, I am new in ubuntu. I can't change my desktop resolution as perfect. It's only showing two resolutin which are 800x600 and 1024x768 . But I need 1440x900 resolution for my desktop. What can I do? Please help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 CurrentDesktop: Unity Date: Thu Jun 15 22:59:03 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:434e] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=c3709d88-8d31-48ed-9b97-57a6f6c3d56a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: CNG4110H.86A.0012.2009.1223.1420 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41CN dmi.board.vendor: Intel Corporation dmi.board.version: AAE82429-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrCNG4110H.86A.0012.2009.1223.1420:bd12/23/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41CN:rvrAAE82429-102:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 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: Thu Jun 15 21:56:08 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output VGA-1 xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1698173/+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 1962029] Re: change default click-action for ubuntu-dock
I hope this is the right place for asking this change otherwise please point me to the right-place -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1962029 Title: change default click-action for ubuntu-dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: hi, issue overview: since last few releases of dash-to-dock extension, a new click-action named focus-minimize-or-previews has been introduced that does the same thing as focus-or-previews but also adds the ability to minimize. many ubuntu-desktop users have asked frequently in discourse.ubuntu.com threads for the default click action of ubuntu- dock to be minimize.It would be a better balance/compromise to change the default click action to focus-minimize-or-previews for ubuntu-22.04 with this change ubuntu-desktop users wouldn't have to look into online outdated-guides to manually change it to minimize click-action. proposal: - change ubuntu-dock click-actions's default from focus-or-previews to focus-minimize-or-previews. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1962029/+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 1962029] [NEW] change default click-action for ubuntu-dock
Public bug reported: hi, issue overview: since last few releases of dash-to-dock extension, a new click-action named focus-minimize-or-previews has been introduced that does the same thing as focus-or-previews but also adds the ability to minimize. many ubuntu-desktop users have asked frequently in discourse.ubuntu.com threads for the default click action of ubuntu-dock to be minimize.It would be a better balance/compromise to change the default click action to focus-minimize-or-previews for ubuntu-22.04 with this change ubuntu-desktop users wouldn't have to look into online outdated-guides to manually change it to minimize click-action. proposal: - change ubuntu-dock click-actions's default from focus-or-previews to focus-minimize-or-previews. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1962029 Title: change default click-action for ubuntu-dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: hi, issue overview: since last few releases of dash-to-dock extension, a new click-action named focus-minimize-or-previews has been introduced that does the same thing as focus-or-previews but also adds the ability to minimize. many ubuntu-desktop users have asked frequently in discourse.ubuntu.com threads for the default click action of ubuntu- dock to be minimize.It would be a better balance/compromise to change the default click action to focus-minimize-or-previews for ubuntu-22.04 with this change ubuntu-desktop users wouldn't have to look into online outdated-guides to manually change it to minimize click-action. proposal: - change ubuntu-dock click-actions's default from focus-or-previews to focus-minimize-or-previews. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1962029/+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 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
if gnome-shell crashes, you lose the session if it's using the wayland- based one ** Package changed: xwayland (Ubuntu) => gnome-shell (Ubuntu) -- 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/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in gnome-shell package in Ubuntu: Confirmed Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle
With no reply from reporter, closing as seems fixed in later releases according to comments 81, 83, 85 and 86. ** Changed in: xorg (Ubuntu) Status: Incomplete => Fix Released -- 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/1434351 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: Fix Released Bug description: After a suspend/resume cycle, the screen comes up normally, but every time I move my mouse over a piece of text, button, widget, etc, the text vanishes and it's replaced by a plain rectangle. This does not affect xterm, but it does affect any GTK apps, firefox, etc. xfce-panel vanishes, although it's still responding to mouse-clicks. Newly opened menus are grey rectangles. The lines underlining menu hotkeys do NOT disappear. In the attached screenshot, you can clearly see which buttons I have waved the mouse over, and which I have not. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 19:51:37 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+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 1563115] Re: System moves xorg.conf
With no reply from reporter, closing. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1563115 Title: System moves xorg.conf Status in xorg package in Ubuntu: Invalid Bug description: Every time i boot into Xubuntu 16.04 (daily) my xorg.conf got moved to xorg.conf.%DATE% by somebody. Tested on both 15.10 upgraded copy and 16.04 clean install $ ls /etc/X11 app-defaults default-display-manager rgb.txt xkb Xreset Xresources Xsession.dxsm cursors fontsxinitxorg.conf.03292016 Xreset.d XsessionXsession.options ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 29 02:40:51 2016 InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1563115/+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 1961610] Re: i386: seed inclusion for libfakechroot
fakechroot is now building on i386. https://launchpad.net/ubuntu/+source/fakechroot/2.20.1+ds-2/+build/23194235 ** Changed in: ubuntu-meta (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1961610 Title: i386: seed inclusion for libfakechroot Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: As per instructions on https://wiki.ubuntu.com/i386 fakechroot (arch: all) requires libfakechroot, but this is not built for i386: https://packages.ubuntu.com/jammy/libfakechroot init-system-helpers, which builds a package allow-listed for i386 builds, now build-depends on fakechroot for build-time unit tests, but given libfakechroot is not available for i386, the i386 build cannot start and thus migration from proposed is held back: https://launchpad.net/ubuntu/+source/init-system-helpers https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html init-system-helpers (1.61 to 1.62) Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: missing build on i386: init (from 1.61) Please enable the libfakechroot i386 build. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1961610/+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 1962021] [NEW] Make the deb package install the firefox snap
Public bug reported: Canonical and Mozilla are working together to make the firefox snap the only supported package in Ubuntu, thus deprecating the deb package in the archive. This bug tracks the transformation of the firefox package in the archive into a transitional package that installs the snap, much like was done for chromium-browser in Ubuntu 19.10. There are a number of known problems and regressions with the snap compared to the deb (see https://bugzilla.mozilla.org/show_bug.cgi?id=snap and https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap), those are actively being worked on and will be addressed in due time, please refrain from using this bug to point them out. Instead, file separate bugs in the upstream bug tracker (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify this is about the snap package. ** Affects: firefox (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: In Progress ** Tags: block-proposed snap ** Tags added: snap -- 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/1962021 Title: Make the deb package install the firefox snap Status in firefox package in Ubuntu: In Progress Bug description: Canonical and Mozilla are working together to make the firefox snap the only supported package in Ubuntu, thus deprecating the deb package in the archive. This bug tracks the transformation of the firefox package in the archive into a transitional package that installs the snap, much like was done for chromium-browser in Ubuntu 19.10. There are a number of known problems and regressions with the snap compared to the deb (see https://bugzilla.mozilla.org/show_bug.cgi?id=snap and https://bugs.launchpad.net/ubuntu/+source/firefox/+bugs?field.tag=snap), those are actively being worked on and will be addressed in due time, please refrain from using this bug to point them out. Instead, file separate bugs in the upstream bug tracker (https://bugzilla.mozilla.org/enter_bug.cgi), making sure to specify this is about the snap package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962021/+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 1439834] Re: After applying 2015 April patches "could not apply the stored configuration for monitors" Ubuntu 14.04LTS
With no reply from reporter, closing. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1439834 Title: After applying 2015 April patches "could not apply the stored configuration for monitors" Ubuntu 14.04LTS Status in xorg package in Ubuntu: Invalid Bug description: After applying routine security updates (April 2015), my system reports "could not apply the stored configuration for monitors" after logging in. The video mode is slightly wrong before login, and I end up at a colorful but empty screen after login. I cannot go any farther with the graphical login. I can CTRL-ALT-F1 to a console. Killing X repeats the procedure above. The graphics card is a GF108/GT 430 according to lspci. Ubuntu 14.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439834/+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 1698173] Re: I can't change my desktop resolution in ubuntu 16.04
With no reply from reporter, closing. -- 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/1698173 Title: I can't change my desktop resolution in ubuntu 16.04 Status in xorg package in Ubuntu: Incomplete Bug description: Hello Sir, I am new in ubuntu. I can't change my desktop resolution as perfect. It's only showing two resolutin which are 800x600 and 1024x768 . But I need 1440x900 resolution for my desktop. What can I do? Please help. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 CurrentDesktop: Unity Date: Thu Jun 15 22:59:03 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:434e] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic root=UUID=c3709d88-8d31-48ed-9b97-57a6f6c3d56a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: CNG4110H.86A.0012.2009.1223.1420 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41CN dmi.board.vendor: Intel Corporation dmi.board.version: AAE82429-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrCNG4110H.86A.0012.2009.1223.1420:bd12/23/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41CN:rvrAAE82429-102:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 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: Thu Jun 15 21:56:08 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output VGA-1 xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1698173/+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 1422899] Re: package x11-common 1:7.7+1ubuntu8 failed to install/upgrade: Unterprozess neues pre-installation-Skript gab den Fehlerwert 2 zurück
With no reply from reporter, closing. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1422899 Title: package x11-common 1:7.7+1ubuntu8 failed to install/upgrade: Unterprozess neues pre-installation-Skript gab den Fehlerwert 2 zurück Status in xorg package in Ubuntu: Invalid Bug description: Installtion of package failed: dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/xserver-xorg_1%3a7.7+1ubuntu8.1_amd64.deb (--unpack): Unterprozess neues pre-removal-Skript gab den Fehlerwert 2 zurück Can't locate Scalar/Util.pm in @INC (you may need to install the Scalar::Util module) (@INC contains: /etc/perl /usr/local/lib/perl/5.18.2 /usr/local/share/perl/5.18.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.18 /usr/share/perl/5.18 /usr/local/lib/site_perl .) at /usr/lib/perl/5.18/Hash/Util.pm line 9. BEGIN failed--compilation aborted at /usr/lib/perl/5.18/Hash/Util.pm line 9. Compilation failed in require at /usr/share/perl/5.18/fields.pm line 122. Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10. Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7. BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7. Compilation failed in require at /usr/share/debconf/frontend line 6. BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6. dpkg: Fehler beim Aufräumen: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück ProblemType: Package DistroRelease: Ubuntu 14.04 Package: x11-common 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.125 Mon Dec 1 19:58:28 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Feb 17 21:36:13 2015 DistUpgraded: 2015-01-29 22:00:47,961 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-45-generic, x86_64: installed nvidia-304-updates, 304.125, 3.13.0-45-generic, x86_64: installed DuplicateSignature: package:x11-common:1:7.7+1ubuntu8:Unterprozess neues pre-installation-Skript gab den Fehlerwert 2 zurück ErrorMessage: Unterprozess neues pre-installation-Skript gab den Fehlerwert 2 zurück ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C77 [GeForce 8200] [10de:0849] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation K10N78FullHD-hSLI R3.0 GeForce 8200 [1849:0849] InstallationDate: Installed on 2014-03-06 (348 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.2) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0471:0815 Philips (or NXP) eHome Infrared Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=85eae9fc-22b8-432c-81e8-2e1cdd01754c ro quiet splash SourcePackage: xorg Title: package x11-common 1:7.7+1ubuntu8 failed to install/upgrade: Unterprozess neues pre-installation-Skript gab den Fehlerwert 2 zurück UpgradeStatus: Upgraded to trusty on 2015-01-29 (18 days ago) dmi.bios.date: 11/24/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: K10N78FullHD-hSLI.. dmi.board.vendor: ASRock 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.:bvrP1.50:bd11/24/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnK10N78FullHD-hSLI..:rvr: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 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
[Desktop-packages] [Bug 1623290] Re: I cannot use my webcam
With no reply from reporter, closing. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1623290 Title: I cannot use my webcam Status in xorg package in Ubuntu: Invalid Bug description: I tried using each of the Nvidia and Xorg drivers in turn. The Xorg driver seems to work better on startup, but there is an error message right after that, so I use one of the Nvidia drivers instead. But I cannot use my webcam with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Sep 13 21:53:49 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-31-generic, x86_64: installed virtualbox, 5.0.24, 3.16.0-50-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G73 [GeForce 7300 GT] [10de:0393] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G73 [GeForce 7300 GT] [1043:820e] InstallationDate: Installed on 2015-07-18 (423 days ago) InstallationMedia: Lubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Dimension 9100 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=a9acfa03-6baa-4e39-a7ed-33919732994e ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0X8582 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd07/07/2006:svnDellInc.:pnDimension9100:pvr:rvnDellInc.:rn0X8582:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dimension 9100 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Sep 13 08:32:58 2016 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623290/+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 1694131] Re: problème cart graphique (Graphics card problem)
With no reply from reporter, closing. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1694131 Title: problème cart graphique (Graphics card problem) Status in xorg package in Ubuntu: Invalid Bug description: Problème avec carte graphique radéon HD 5000 cherche pilote. Merci Google translates as: Problem with Radeon HD 5000 graphics card looking for driver. Thank you ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 BootLog: /dev/sda1: clean, 231682/30269440 files, 3997297/121047808 blocks [[0m[0;31m* [0m] (1 of 7) A start job is running for Network Manager (21s / 1min 43s) CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 28 16:40:08 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon HD 5450 [1043:0386] InstallationDate: Installed on 2017-05-21 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=58213a0b-ae70-4cbf-92f9-7f61e83b1926 ro nomodeset splash quiet nopat vesafb.invalid=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0602 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-AM SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMSE:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun May 28 16:11:57 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLITEON Technology USB Keyboard KEYBOARD, id 8 inputLITEON Technology USB Keyboard KEYBOARD, id 9 inputLogitech Optical USB Mouse MOUSE, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1694131/+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 1732120] Re: i can't login correctly..
With no reply from reporter, closing. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1732120 Title: i can't login correctly.. Status in xorg package in Ubuntu: Invalid Bug description: initframes command line executed at startup. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Tue Nov 14 14:56:58 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c] InstallationDate: Installed on 2017-11-07 (6 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20351 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=ce1a215d-419c-4fbe-b91e-7c44679d5575 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN32WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN32WW:bd07/20/2015:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.name: 20351 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 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 Nov 14 11:14:44 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732120/+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 1912816] Re: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from
*** This bug is a duplicate of bug 1905519 *** https://bugs.launchpad.net/bugs/1905519 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1912816 Title: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Status in gnome-shell package in Ubuntu: Confirmed Bug description: Journalctl -f repeately shows every 1 to 2 seconds: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Before that it shows: Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: == Stack trace for context 0x558f639f9270 == Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: #0 7ffc767f5f00 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1f3aba6af420 @ 208) Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: == Stack trace for context 0x558f639f9270 == Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: #0 7ffc767f5f00 b /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:2051 (1f3aba6af420 @ 208) Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: Object St.Bin (0x558f64771240), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jan 22 11:18:30 BDXR-2ML gnome-shell[2931]: Object St.Bin (0x558f6751a480), has been already deallocated — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 Uname: Linux 5.10.4-051004-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 22 11:29:57 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2020-12-24 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-12-24 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1912816/+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 1857392] Re: Window manager warning: Overwriting existing binding of keysym...
I am also affected by this bug. Running 20.04.3 LTS on a SAGER laptop. System hangs. Sometimes I can recover by switching to another window, but most times I need to reboot. After reboot syslog is full of: gnome-shell[1979]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). ...messages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1857392 Title: Window manager warning: Overwriting existing binding of keysym... Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+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 1962019] [NEW] [850XBD, Realtek ALC256, Black Headphone Out, Right] Background noise or low volume
Public bug reported: Laptop's (Samsung Odyssey) speaker works fine, but headphone presents incredibly low volume and buzzing/crackling noise only when sound is being played ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ipontes3olavy 1497 F pulseaudio /dev/snd/pcmC0D0p: ipontes3olavy 1497 F...m pulseaudio /dev/snd/controlC1: ipontes3olavy 1497 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 23 12:37:47 2022 InstallationDate: Installed on 2022-02-22 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_Type: High background noise, or volume is too low Title: [850XBD, Realtek ALC256, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03AHZ.009.210719.JJ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP850XBD-XG2BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLA185A0K-C01-G001-S0001+10.0.18362 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03AHZ.009.210719.JJ:bd07/19/2021:br5.13:svnSAMSUNGELECTRONICSCO.,LTD.:pn850XBD:pvrP03AHZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP850XBD-XG2BR:rvrSGLA185A0K-C01-G001-S0001+10.0.18362:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAHZ: dmi.product.family: Odyssey Series dmi.product.name: 850XBD dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHZ dmi.product.version: P03AHZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1962019 Title: [850XBD, Realtek ALC256, Black Headphone Out, Right] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: Laptop's (Samsung Odyssey) speaker works fine, but headphone presents incredibly low volume and buzzing/crackling noise only when sound is being played ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ipontes3olavy 1497 F pulseaudio /dev/snd/pcmC0D0p: ipontes3olavy 1497 F...m pulseaudio /dev/snd/controlC1: ipontes3olavy 1497 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Feb 23 12:37:47 2022 InstallationDate: Installed on 2022-02-22 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_Type: High background noise, or volume is too low Title: [850XBD, Realtek ALC256, Black Headphone Out, Right] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P03AHZ.009.210719.JJ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP850XBD-XG2BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLA185A0K-C01-G001-S0001+10.0.18362 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP03AHZ.009.210719.JJ:bd07/19/2021:br5.13:svnSAMSUNGELECTRONICSCO.,LTD.:pn850XBD:pvrP03AHZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP850XBD-XG2BR:rvrSGLA185A0K-C01-G001-S0001+10.0.18362:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PAHZ: dmi.product.family: Odyssey Series dmi.product.name: 850XBD dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHZ dmi.product.version: P03AHZ
[Desktop-packages] [Bug 1961610] Re: i386: seed inclusion for libfakechroot
Bug against fakechroot: https://bugs.launchpad.net/ubuntu/+source/fakechroot/+bug/1875298 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1961610 Title: i386: seed inclusion for libfakechroot Status in ubuntu-meta package in Ubuntu: New Bug description: As per instructions on https://wiki.ubuntu.com/i386 fakechroot (arch: all) requires libfakechroot, but this is not built for i386: https://packages.ubuntu.com/jammy/libfakechroot init-system-helpers, which builds a package allow-listed for i386 builds, now build-depends on fakechroot for build-time unit tests, but given libfakechroot is not available for i386, the i386 build cannot start and thus migration from proposed is held back: https://launchpad.net/ubuntu/+source/init-system-helpers https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html init-system-helpers (1.61 to 1.62) Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: missing build on i386: init (from 1.61) Please enable the libfakechroot i386 build. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1961610/+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 1961610] Re: i386: seed inclusion for libfakechroot
Note that the only dependency is libjemalloc, whicih already has an i386 build, so there would be no other new i386 builds apart from libfakechroot itself. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1961610 Title: i386: seed inclusion for libfakechroot Status in ubuntu-meta package in Ubuntu: New Bug description: As per instructions on https://wiki.ubuntu.com/i386 fakechroot (arch: all) requires libfakechroot, but this is not built for i386: https://packages.ubuntu.com/jammy/libfakechroot init-system-helpers, which builds a package allow-listed for i386 builds, now build-depends on fakechroot for build-time unit tests, but given libfakechroot is not available for i386, the i386 build cannot start and thus migration from proposed is held back: https://launchpad.net/ubuntu/+source/init-system-helpers https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html init-system-helpers (1.61 to 1.62) Migration status for init-system-helpers (1.61 to 1.62): BLOCKED: Maybe temporary, maybe blocked but Britney is missing information (check below) Issues preventing migration: missing build on i386: init (from 1.61) Please enable the libfakechroot i386 build. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1961610/+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 1961955] Re: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
** Also affects: hwdata (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: hwdata (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: New Status in hwdata source package in Focal: New Status in hwdata source package in Jammy: New Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 583271] Re: The value of "Energy when full" is much higher than the value of "Energy (design)" so the percentage calculation is wrong
Ubuntu 21.10 ThinkPad X1 Carbon 7 Still exists. The Indicator is stuck at "Estimating...". The logs show this: Feb 23 15:17:46 upowerd[3233]: energy 42.66 bigger than full 0.00 Feb 23 15:18:56 upowerd[3233]: energy 43.54 bigger than full 0.00 Feb 23 15:18:56 upowerd[3233]: energy 43.54 bigger than full 0.00 Feb 23 15:20:56 upowerd[3233]: energy 43.70 bigger than full 0.00 Feb 23 15:23:17 upowerd[3233]: energy 44.47 bigger than full 0.00 Feb 23 15:23:18 upowerd[3233]: energy 44.47 bigger than full 0.00 My device shuts down unexpectedly mid work, although the indicator shows enough energy. The reverse has also happened, where my device ran for hours with only 5% battery left. I also observed that after plugging in a phone or tablet to charge, the power level drops from 100% to 50% instantly after a while and stays there while the devices charge and while "tracker-miner-fs" goes wild... . I had apcupsd installed on this machine, which I purged together with "power-profiles-daemon". After installing "tlp" (plus "acpi-call-dkms"), I still get the messages above. Seems related: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1530014 https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1590244 https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1903995 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/583271 Title: The value of "Energy when full" is much higher than the value of "Energy (design)" so the percentage calculation is wrong Status in upower package in Ubuntu: Confirmed Bug description: Binary package hint: indicator-applet Indicator Applet 0.3.7 Description: Ubuntu 10.04 LTS Release: 10.04 I have installed Ubuntu 10.04 on a Macbook 2,1 and sometimes the value of "Energy when full" gets way too high (currently 983.5 Wh). This leads to a wrong computation of the percentage value of the battery. Despite this the value of "Time to empty" is computed correctly (currently 2.1 h). The values of "Energy (design)" (currently 50.2 Wh) and "Energy" (currently 43.4 Wh) seem to be correct. If this happens only a restart can solve the problem and the value of "Energy when full" seems correct. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: indicator-applet 0.3.7-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Thu May 20 12:52:21 2010 ExecutablePath: /usr/lib/indicator-applet/indicator-applet InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANG=en_US.utf8 LANGUAGE=en LC_CTYPE=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/583271/+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 346912] Re: Tracker index corruption (was Tracker does not stop indexing)
have not seen this one jet in newer version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/346912 Title: Tracker index corruption (was Tracker does not stop indexing) Status in Tracker: Expired Status in tracker package in Ubuntu: Incomplete Status in tracker source package in Jaunty: Won't Fix Bug description: I recently realized that tracker does not always give me the search results I expected, meaning that it does not find documents containing certain words. A quick look through the indexer preferences, I doubled the "maximal amount of text to index" and "maximum number of unique words to index". After doing so, the tracker does not stop indexing. The information message when I hover over the tracker icons says: Tracker: Indexing Done: 883 of 22296 Estimated: 33 minutes ... Elapsed: 01 minute ... This message hasn't changed for about a day, and the indexing continues. One of my log files is continuously flooded with the following messages: nasko@serre:~/.local/share/tracker$ tail -n20 tracker-indexer.log 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'previous': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'troubl': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'preprocessor': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'ac_abs_top_builddir': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'detail': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'call': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'paramet': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'offshoot': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'with_gcc': with fatal error 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'honor': with fatal error I would like to have tracker index my files more fully, and yet have it do that in a normal manner. Is there a way to prevent this problem? To manage notifications about this bug go to: https://bugs.launchpad.net/tracker/+bug/346912/+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 1958019]
(In reply to Fer Korol from comment #568) > I can confirm (In reply to Darin Miller from comment #563) > > *Ubuntu version: > > > > 1) install kernel build tools: > > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev dkms > > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > > > 2) clone the kernel from github and checkout to v5.17 branch (Rather large, > > multiple GB's): > > > > * git clone https://github.com/torvalds/linux.git > > * cd linux > > * git checkout v5.17-rc4 > > > > 3) get the patch and install it: > > > > get the patch form this site and save to "linux" directory: (top right > > corner "series" button) and use the following "git am ..." line to apply > the > > patch: > > > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > > sbind...@opensource.cirrus.com/ > > > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > > > 4) load current kernel config and change configuration then run the > > following scripts/config commands: > > > > * make olddefconfig > > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > > * ./scripts/config --disable CONFIG_DEBUG_INFO > > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > > > 6) build the kernel > > > > * make -j 16 > > > > 7) install the kernel > > > > * sudo make module_install > > * sudo make install > > I confirm this guide works flawless on ubuntu 21.10 with this considerations: > * The steps 3) and above, i run as root user (sudo su or su) > * In the 7) step, as have been comented, the correct command is: > sudo make modules_install > > With this tweaks no more freezes at the boot. > > Regards! What pc model? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions
[Desktop-packages] [Bug 1958019]
(In reply to darnellkeithj from comment #569) > (In reply to Fer Korol from comment #568) > > I can confirm (In reply to Darin Miller from comment #563) > > > *Ubuntu version: > > > > > > 1) install kernel build tools: > > > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > > > > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev dkms > > > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > > > > > 2) clone the kernel from github and checkout to v5.17 branch (Rather > large, > > > multiple GB's): > > > > > > * git clone https://github.com/torvalds/linux.git > > > * cd linux > > > * git checkout v5.17-rc4 > > > > > > 3) get the patch and install it: > > > > > > get the patch form this site and save to "linux" directory: (top right > > > corner "series" button) and use the following "git am ..." line to apply > > the > > > patch: > > > > > > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > > > sbind...@opensource.cirrus.com/ > > > > > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > > > > > 4) load current kernel config and change configuration then run the > > > following scripts/config commands: > > > > > > * make olddefconfig > > > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > > > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > > > * ./scripts/config --disable CONFIG_DEBUG_INFO > > > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > > > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > > > > > 6) build the kernel > > > > > > * make -j 16 > > > > > > 7) install the kernel > > > > > > * sudo make module_install > > > * sudo make install > > > > I confirm this guide works flawless on ubuntu 21.10 with this > considerations: > > * The steps 3) and above, i run as root user (sudo su or su) > > * In the 7) step, as have been comented, the correct command is: > > sudo make modules_install > > > > With this tweaks no more freezes at the boot. > > > > Regards! > > What pc model? Lenovo Legion 7 5800h RTX-3070 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku:
[Desktop-packages] [Bug 1958019]
I can confirm (In reply to Darin Miller from comment #563) > *Ubuntu version: > > 1) install kernel build tools: > (https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel): > > * sudo apt install libncurses-dev gawk flex bison openssl libssl-dev dkms > libelf-dev libudev-dev libpci-dev libiberty-dev autoconf git > > 2) clone the kernel from github and checkout to v5.17 branch (Rather large, > multiple GB's): > > * git clone https://github.com/torvalds/linux.git > * cd linux > * git checkout v5.17-rc4 > > 3) get the patch and install it: > > get the patch form this site and save to "linux" directory: (top right > corner "series" button) and use the following "git am ..." line to apply the > patch: > https://patchwork.kernel.org/project/linux-acpi/patch/20220121172431.6876-4- > sbind...@opensource.cirrus.com/ > > * git am Support-Spi-in-i2c-multi-instantiate-driver.patch > > 4) load current kernel config and change configuration then run the > following scripts/config commands: > > * make olddefconfig > * ./scripts/config --enable CONFIG_SERIAL_MULTI_INSTANTIATE > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_I2C > * ./scripts/config --enable CONFIG_SND_HDA_SCODEC_CS35L41_SPI > * ./scripts/config --disable CONFIG_DEBUG_INFO > * ./scripts/config --set-str CONFIG_SYSTEM_TRUSTED_KEYS "" > * ./scripts/config --set-str CONFIG_SYSTEM_REVOCATION_KEYS "" > > 6) build the kernel > > * make -j 16 > > 7) install the kernel > > * sudo make module_install > * sudo make install I confirm this guide works flawless on ubuntu 21.10 with this considerations: * The steps 3) and above, i run as root user (sudo su or su) * In the 7) step, as have been comented, the correct command is: sudo make modules_install With this tweaks no more freezes at the boot. Regards! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More
[Desktop-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
** Project changed: canonical-identity-provider => modemmanager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1961859 Title: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. Status in modemmanager package in Ubuntu: New Bug description: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1961859] [NEW] When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.
You have been subscribed to a public bug: 1. We use sourcecode to install ModemManger1.16.6 2. Ubuntu can not enter UI. 3. We capture log and picture and add these on the attachment. ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI. https://bugs.launchpad.net/bugs/1961859 You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. -- 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 1956822] Re: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
No response to comment #2 so closing. ** Changed in: glib2.0 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1956822 Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in glib2.0 package in Ubuntu: Invalid Bug description: Update issue ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jan 8 15:55:28 2022 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-05-29 (223 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1956822/+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 1923542] Re: "Failed to restart network-manager.service: Unit network-manager.service not found." during package update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1923542 Title: "Failed to restart network-manager.service: Unit network- manager.service not found." during package update Status in network-manager package in Ubuntu: Confirmed Bug description: I updated network-manger on hirsute: network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) over (1.30.0-1ubuntu2) During the postinst run, I get: Setting up network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) ... Failed to restart network-manager.service: Unit network-manager.service not found. invoke-rc.d: initscript network-manager, action "force-reload" failed. The reason seems to be that there is no network-manager.service . it's called NetworkManager.service . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 13 06:15:31 2021 InstallationDate: Installed on 2020-12-08 (125 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: network-manager SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2020-12-09 (124 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 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/1923542/+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 1962000] [NEW] alsamixer: Main volume is named as "Volume 1"
Public bug reported: It's only confusing labeling: The master or main volume of a 8ch usb sound card is labeled as "volume 1" in the alsamixer. It would be more intuitive if the control is named master or main volume. ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1962000 Title: alsamixer: Main volume is named as "Volume 1" Status in alsa-utils package in Ubuntu: New Bug description: It's only confusing labeling: The master or main volume of a 8ch usb sound card is labeled as "volume 1" in the alsamixer. It would be more intuitive if the control is named master or main volume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1962000/+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 1958675] Re: The application (xdg-open)
Achraf, please can you give us a few more details and confirm the application that you are using. Also which release of Ubuntu? Looking at your screenshot I'm assuming that you are using the snap version of the Chromium browser. Is that correct? Where is the icon of Whatsapp? On a web page? On your desktop? ** Package changed: ubuntu => chromium-browser (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1958675 Title: The application (xdg-open) Status in chromium-browser package in Ubuntu: Incomplete Bug description: When I click an icon showing (Whatsapp), a new window shows to accept (xdg-open) application, but then the system indicates no file. How to resolve the problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1958675/+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 1958675] [NEW] The application (xdg-open)
You have been subscribed to a public bug: When I click an icon showing (Whatsapp), a new window shows to accept (xdg-open) application, but then the system indicates no file. How to resolve the problem? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- The application (xdg-open) https://bugs.launchpad.net/bugs/1958675 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- 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 1961997] [NEW] New upstream version in Debian libdeflate_1.10-1
Public bug reported: Debian has packaged a new upstream. Merge it into Ubuntu. ** Affects: libdeflate (Ubuntu) Importance: Undecided Status: New ** Tags: fr-2072 ** Tags added: fr-2072 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libdeflate in Ubuntu. https://bugs.launchpad.net/bugs/1961997 Title: New upstream version in Debian libdeflate_1.10-1 Status in libdeflate package in Ubuntu: New Bug description: Debian has packaged a new upstream. Merge it into Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1961997/+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 1961998] [NEW] alsamixer: volume controls are assigned to wrong channels
Public bug reported: I have tested the alsamixer with 2 different 8ch usb sound cards (UAC2 compatible) and the assignment of the volume controls to the respective channel is partly wrong on both cards. The volume control for rear changes the volume of the center and subwoofer/LFE and the volume control for "Center" and "Woofer" changes the volume of the rear speakers. According to the usb audio class 2 specification, chapter "4.1 Audio Channel Cluster Descriptor", the volume controls index must be (for a 8ch sound card): 1 = FL 2 = FR 3 = C 4 = LFE 5 = RL 6 = RR 7 = SL 8 = SR The current implementation as following assignment: 1 = FL 2 = FR 3 = RL 4 = RR 5 = C 6 = LFE 7 = SL 8 = SR Unfortunately, I can not judge whether this is a problem in the program or driver (audio usb). If you have any questions, feel free to contact me. ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1961998 Title: alsamixer: volume controls are assigned to wrong channels Status in alsa-utils package in Ubuntu: New Bug description: I have tested the alsamixer with 2 different 8ch usb sound cards (UAC2 compatible) and the assignment of the volume controls to the respective channel is partly wrong on both cards. The volume control for rear changes the volume of the center and subwoofer/LFE and the volume control for "Center" and "Woofer" changes the volume of the rear speakers. According to the usb audio class 2 specification, chapter "4.1 Audio Channel Cluster Descriptor", the volume controls index must be (for a 8ch sound card): 1 = FL 2 = FR 3 = C 4 = LFE 5 = RL 6 = RR 7 = SL 8 = SR The current implementation as following assignment: 1 = FL 2 = FR 3 = RL 4 = RR 5 = C 6 = LFE 7 = SL 8 = SR Unfortunately, I can not judge whether this is a problem in the program or driver (audio usb). If you have any questions, feel free to contact me. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1961998/+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 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
Updates work now but I continue to get the gnome-shell error when trying to report crashes with ubuntu-bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in xwayland package in Ubuntu: Confirmed Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1961910/+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 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
I also experienced a crash while performing a routine update and was thrown out of the desktop. I saw an error relating to canonical- livepatch which is installed but not enabled. I switched to vt4 and rebooted with the command "sudo reboot now". In my case everything appears to be working normally including the ability to report bugs. My /var/crash/ directory shows that files relating to gnome-shell, seahorse and cups-browsed were automatically uploaded at the time I experienced the crash. The times match entries found in /var/log/apt/history.log so the crash *was* related to the update process. I'm not sure if this helps anyone trace the source of the problem but I thought I should respond as this is the first instance I have seen of such a crash since I began using Ubuntu in 2010. Alexandru, I'm confirming the bug on the basis that *we* saw a similar crash while updating but not for the problems that you experienced afterwards. ** Changed in: xwayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in xwayland package in Ubuntu: Confirmed Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1961910/+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 1954649] Re: autopkgtest regressions with python3.10 as supported
pytest-twisted's autopkgtests pass with twisted 22.1.0 ** Changed in: pytest-twisted (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1954649 Title: autopkgtest regressions with python3.10 as supported Status in ipywidgets package in Ubuntu: Fix Released Status in pygobject package in Ubuntu: Fix Released Status in pytest-twisted package in Ubuntu: Fix Committed Status in python-b2sdk package in Ubuntu: New Status in python-hypothesis package in Ubuntu: Fix Released Status in python-taskflow package in Ubuntu: Fix Released Status in python3-defaults package in Ubuntu: New Status in skimage package in Ubuntu: Invalid Status in supysonic package in Ubuntu: Fix Released Status in vorta package in Ubuntu: Fix Released Status in ipywidgets package in Debian: New Status in pygobject package in Debian: Fix Released Status in pytest-twisted package in Debian: New Status in python-b2sdk package in Debian: Confirmed Status in python-hypothesis package in Debian: Fix Released Status in supysonic package in Debian: Fix Released Status in vorta package in Debian: Fix Released Bug description: This bug is for tracking the packages having autopkgtest regressions with python3.10 as a supported version, blocking migration of python3-defaults/3.9.7-4. All packages are in universe except pygobject and python-taskflow in main. All packages have RC bugs in Debian except python-taskflow which is based on a newer upstream version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+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 355499] Re: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data()
Please close this. On Mon, 21 Feb 2022 at 16:45, Rolf Leggewie <355...@bugs.launchpad.net> wrote: > @funkyhat, do you still experience this issue in focal or later or can > this be closed? > > ** Changed in: tracker (Ubuntu) >Status: Triaged => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/355499 > > Title: > tracker-indexer crashed with SIGSEGV in > tracker_module_metadata_utils_get_data() > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/355499/+subscriptions > > -- Vilius -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/355499 Title: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() Status in tracker package in Ubuntu: Incomplete Bug description: Binary package hint: tracker Description: Ubuntu jaunty (development branch) Release: 9.04 tracker: Installiert: 0.6.92-1ubuntu1 Kandidat: 0.6.92-1ubuntu1 Versions-Tabelle: *** 0.6.92-1ubuntu1 0 500 http://archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/lib/tracker/tracker-indexer Package: tracker 0.6.92-1ubuntu1 ProcCmdline: /usr/lib/tracker/tracker-indexer ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 Signal: 11 SourcePackage: tracker StacktraceTop: tracker_module_metadata_utils_get_data () ?? () tracker_module_file_get_metadata () ?? () ?? () Title: tracker-indexer crashed with SIGSEGV in tracker_module_metadata_utils_get_data() Uname: Linux 2.6.28-11-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin plugdev pulse-rt sambashare scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/355499/+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 1961955] [NEW] Request to pull-in new HBA & BOSS N1 PCI-ids from upstream
Public bug reported: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET Thanks. ** Affects: hwdata (Ubuntu) Importance: Undecided Status: New ** Description changed: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream + HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however + new form factors are being launched by Dell which are having new + subsystem-ids. - HBA350i are shipping cards supported from SLES15-SP1 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. + BOSS-N1 is planned support in Ubuntu 20.04 onwards. - BOSS-N1 is planned support in SLES15-SP3 onwards. - - Request is to pull these new pci-ids into SLES15-SP3 and SLES15-SP4. - + Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hwdata in Ubuntu. https://bugs.launchpad.net/bugs/1961955 Title: Request to pull-in new HBA & BOSS N1 PCI-ids from upstream Status in hwdata package in Ubuntu: New Bug description: Request to pull-in new HBA350i MM and HBA350i MM LP PCI-ids from upstream Also combining request to pull-in new BOSS-N1 PCI-id from upstream HBA350i are shipping cards supported from Ubuntu 20.04 onwards, however new form factors are being launched by Dell which are having new subsystem-ids. BOSS-N1 is planned support in Ubuntu 20.04 onwards. Request is to pull these new pci-ids into Ubuntu 20.04 and Ubuntu 22.04. PCI-id details: 1000: 00e6: 1028: 2170 HBA350i MM 1000: 00e6: 1028: 2197 HBA350i MM LP 1b4b: 2241: 1028: 2151 BOSS-N1 Modular ET Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hwdata/+bug/1961955/+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 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
I tried to update again, it asked me to restart, restarted and now looks like there are no newer updates. I still cannot send the report with ubuntu-bug. When I hit send I get a popup with an error stating that there's a problem with gnome-shell and could be caused by the fact that I have older versions of some packages (accountsservice, bind9-host, bind9-libs, dbus, gir1.2-accountservice-1.0, gir1.2-nm-1.0, libaccountservice0, libsasl2-modules-db, libwhoopsie-preferences0, libwhoopsie0, libxml2, networkmanager, whoopsie-preferences) But when I try to upgrade them with apt upgrade it says they are all fine -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in xwayland package in Ubuntu: New Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1961910/+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 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
Ubuntu 22 crash when updating, broken network manager and cannot report bug. The errors must be at the beginning because as soon as I logged in the first thing I did was updating ** Attachment added: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1961910/+attachment/5562973/+files/syslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in xwayland package in Ubuntu: New Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1961910/+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 1767542] Re: Turning off WiFi enables Airplane mode
This bug has quite a big impact but seems to be easy to fix. By this means 4 years is a looong time. 20.04 LTS, 21.04, 21.10 still have this issue - will 22.04 too? Seriously, when will this be fixed? -- 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/1767542 Title: Turning off WiFi enables Airplane mode Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Turning off the WiFi from the top right control enables Airplane mode (see screenshots). Also after turning off airplane mode, the Wi-Fi is not turned back on, rather the Bluetooth is. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 17:46:34 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1767542/+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 1902436] Re: Mouse slow in Xorg fractional scaling
** Summary changed: - Mouse slow in fractional scaling + Mouse slow in Xorg fractional scaling -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1902436 Title: Mouse slow in Xorg fractional scaling Status in mutter package in Ubuntu: Triaged Bug description: I have a Dell XPS 17 with a 3,840 x 2,400 screen and an external monitor with 3840 x 1600 resolution. When I use only one of them it works totally fine. I use the external monitor without scaling and my notebook display with fractional scaling of 150%. But when i want to use both at the same time, my mouse starts to be slow. So in this scenario i have the external monitor at 100% and the notebook screen at 150%. Everything works fine expect the mouse which is slow,on both screens. What I found is, when i set both my screens to 200% while fractional scaling is enabled. The issue is gone. Same with 100%. But as soon as I start using fractions, the mouse is slow again. I don't believe it is an power issue because my hardware is mostly in idle. Also, i tried different mouses over Bluetooth and USB but no change. I am currently using 20.10 but had the same issue with 20.04. But when i use Wayland, the problem is gone. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.80.02 Wed Sep 23 01:13:39 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 1 14:01:59 2020 DistUpgraded: 2020-10-30 12:11:16,382 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: evdi, 1.7.0, 5.8.0-26-generic, x86_64: installed nvidia, 450.80.02, 5.8.0-26-generic, x86_64: installed soundwire, 1.2.2: added DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:098f] NVIDIA Corporation TU106M [GeForce RTX 2060 Max-Q] [10de:1f12] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU106M [GeForce RTX 2060 Max-Q] [1028:098f] InstallationDate: Installed on 2020-09-19 (42 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 17 9700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=6d098ea0-9d87-46ec-beb0-cc19a3b20841 ro quiet splash resume=UUID=723b6007-ad35-4e89-be9e-341d54fe18f8 nouveau.modset=0 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) dmi.bios.date: 08/18/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0P1CHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd08/18/2020:br1.3:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0P1CHN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1902436/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1902921] Re: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar)
** Tags removed: xrandr-scaling -- 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/1902921 Title: Scaling one monitor (to 1.5x in my case) can cause Firefox to lose window features (titlebar, buttons, bookmark bar) Status in firefox package in Ubuntu: New Bug description: One monitor is a 4K monitor scaled to 1.5x, the other is a normal 1920x1080 monitor scaled to 1x. While Firefox is already open, after logging in with the lock screen, or modifying display settings, sometimes Firefox will lose the titlebar, address bar, buttons, and bookmark bar. The website being displayed will still show, however not all features are usable (right click menu, mouse icon doesn't change). Reproduction steps: - Change zoom level of one or more monitors to >1.0 but less than 2.0 (have not tested with non-fractional zooms) - Open Firefox and browse to any website - Lock screen or leave computer alone until the screen locks. - Login - Firefox may have lost the window chrome Workaround: - Open Display Settings - Change display settings or zoom level, then change back. Computer info: - Ubuntu 20.04.1 - Fractional Scaling enabled - NVidia GeForce GTX 1080/PCIe/SSE2 - Gnome 3.36.3 - X11 - Samsung LU32J590 4K (3840x2160) @ 1.5x - Dell E2416Hb 1920x1080 rotated portrait left, right of Samsung ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 09:31:17 2020 DistUpgraded: 2020-04-03 12:51:44,815 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP104 [GeForce GTX 1080] [3842:6188] InstallationDate: Installed on 2018-04-28 (920 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=dfb5d6fd-4a4e-471d-bb00-77a6729533d8 ro quiet splash pci=nommconf vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-03 (214 days ago) dmi.bios.date: 04/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.80 dmi.board.name: X99 Extreme4 dmi.board.vendor: ASRock 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.:bvrP3.80:bd04/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: 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.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1902921/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1961910] [NEW] Ubuntu 22 crash when updating, broken network manager and cannot report bug
Public bug reported: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug Status in xwayland package in Ubuntu: New Bug description: A new day, a new struggle with Ubuntu 22.04. So, I decided to get my daily updates and in the middle of the process the system just crashed, leaving me at the login page. When I got back, the wifi was no longer there and the network configuration was reporting an error about the network manager having problems. I shut down and restarted, the wifi came back. Went to the var/crash folder to report the bug with $:/var/crash$ ubuntu-bug _usr_bin_gnome-shell.1000.crash and it started complaining about older packages that need to be upgraded. I run `apt upgrade`, one of the packages is `dbus`, I tried `apt install dbus` and another even uglier crash that left me with a black screen from which I could only come back with a forced shutdown and restart. Now, how do I get out of this mess and report the bug? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1961910/+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