[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 u
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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.5
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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 0
[Touch-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 Ubuntu Touch seeded 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 0
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded 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 if
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded 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 ifinde
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded 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 Fe
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded 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 ifinde
[Touch-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 Ubuntu Touch seeded 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 Fe
[Touch-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 Ubuntu Touch seeded 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 ifinde
[Touch-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 Ubuntu Touch seeded 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:
[Touch-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): Activ
[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
*** This bug is a duplicate of bug 1961910 *** https://bugs.launchpad.net/bugs/1961910 ** This bug has been marked a duplicate of bug 1961910 Ubuntu 22 crash when updating, broken network manager and cannot report bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Confirmed Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to python3-defaults 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
I hit this too - just reported https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1962127 from the associated gnome-shell crash. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Confirmed Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: Confirmed Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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 marke
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961805] Re: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main)
This bug was fixed in the package procps - 2:3.3.17-6ubuntu1 --- procps (2:3.3.17-6ubuntu1) jammy; urgency=low * Merge from Debian unstable (LP: #1961805). Remaining changes: - debian/sysctl.d (Ubuntu-specific): + 10-console-messages.conf: stop low-level kernel messages on console. + 10-kernel-hardening.conf: add the kptr_restrict setting + 10-ipv6-privacy.conf: add a file to sysctl.d to apply the defaults for IPv6 privacy extensions for interfaces. (LP: #176125, #841353) + 10-magic-sysrq.conf: Disable most magic sysrq by default, allowing critical sync, remount, reboot functions. (LP: #194676, LP: #1025467) + 10-network-security.conf: enable rp_filter. + 10-ptrace.conf: describe new PTRACE setting. + 10-zeropage.conf: safe mmap_min_addr value for graceful fall-back. for armhf, and arm64. + 10-qemu.conf.s390x for qemu. - debian/rules: Fix cross build - ignore_eaccess.patch: If we get eaccess when opening a sysctl file for writing, don't error out. Otherwise package upgrades can fail, especially in containers. - Adjust logic due to rc no longer being propagated (LP: #1903351) - ignore_erofs.patch: Same as ignore_eaccess but for the case where part of /proc is read/only. - Adjust logic due to rc no longer being propagated (LP: #1903351) - debian/procps.maintscript: handle migration of link-protect.conf from /etc to /usr. Dropped changes: - debian/README.sysctl: Debian has added this information. - debian/procps.install: debian/protect-links.conf has been re-named to debian/99-protect-links.conf, so it can be safely installed again (see LP: #1938585 for background). -- Nick Rosbrook Fri, 18 Feb 2022 16:49:15 -0500 ** Changed in: procps (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1961805 Title: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main) Status in procps package in Ubuntu: Fix Released Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. Dropped changes: - debian/README.sysctl: Debian has added this information. - debian/procps.install: debian/protect-links.conf has been re-named to debian/99-protect-links.conf, so it can be safely installed again (see LP: #1938585 for background). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960863] Re: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances
Performing verification for openssl on Focal. An affected user performed the verification, due to c7g instance types being in "Preview" state on Amazon AWS, and not generally accessible. The user started a c7g instance, and checked they had openssl 1.1.1f-1ubuntu2.10 from -updates. They attempted to use the poly1035 MAC downloading the file from the testcase: $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output gradle-7.2.bin % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0Segmentation fault (core dumped) They can reproduce the issue. They then enabled -proposed from ports.ubuntu.com mirror, and installed openssl 1.1.1f-1ubuntu2.11. They again tried downloading the file: $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output gradle-7.2.bin % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 (note the file doesn't actually download due to curl not automatically following 301 redirects): $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output gradle-7.2.bin --verbose ... * SSL connection using TLSv1.2 / ECDHE-ECDSA-CHACHA20-POLY1305 ... < HTTP/1.1 301 Moved Permanently < Location: https://downloads.gradle-dn.com/distributions/gradle-7.2-bin.zip ... curl does not segfault, and exits successfully. The package in -proposed fixes the issue. Happy to mark as verified. ** Tags removed: sts-sponsor verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960863 Title: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Bug description: [Impact] Support for hardware pointer authentication for armv8 systems was merged in openssl 1.1.1f, but it contains a bug in the implementation for poly1305 message authenticated code routines, which causes the calling program to fail pointer authentication, which causes the program to crash with a segmentation fault. You can easily test it by accessing any website that uses poly1305. There is no workaround except use a different MAC. [Testcase] This bug applies to armv8 systems which support pointer authentication. Start an armv8 instance, such as a c7g graviton 3 instance on AWS, and make sure the paca flag is present in lscpu: $ grep paca /proc/cpuinfo Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng Next, attempt to connect to any website that uses poly1305 MAC. $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output gradle-7.2.bin % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Segmentation fault (core dumped) There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf327917-test Install it, and poly1305 operations will no longer segfault. [Where problems could occur] The patch changes the order of operations for loading the SP and checking the AUTIASP against it, from checking the AUTIASP against nothing then loading the correct SP to check with, to the correct loading the SP and then checking the AUTIASP against the SP. This only changes one code path for armv8 systems, and other architectures are not affected. This is also only limited to poly1305 MAC. If a regression were to occur, it would only affect users of poly1035 MAC on armv8 with pacs support. [Other info] The fix landed upstream in openssl 1.1.1i with the following commit: commit 5795acffd8706e1cb584284ee5bb3a30986d0e75 Author: Ard Biesheuvel Date: Tue Oct 27 18:02:40 2020 +0100 Subject: crypto/poly1305/asm: fix armv8 pointer authentication Link: https://github.com/openssl/openssl/commit/5795acffd8706e1cb584284ee5bb3a30986d0e75 This commit is already present in Impish onward. Only Focal needs the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscr
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 notific
[Touch-packages] [Bug 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
This bug was fixed in the package packagekit - 1.2.5-2ubuntu1 --- packagekit (1.2.5-2ubuntu1) jammy; urgency=low * Merge from Debian unstable (LP: #1961837). Remaining changes: - debian/control: Added recommends for packagekit-installer packagekit (1.2.5-2) unstable; urgency=medium * Add fix-single-candidate-pkgid-emission.patch - Unblock updates by emitting package-IDs again even if there is just one candidate available. -- Julian Andres Klode Wed, 23 Feb 2022 11:10:46 +0100 ** Changed in: packagekit (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in PackageKit: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Jammy: Fix Released Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1961837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962061] [NEW] ZFS Key load error: Failed to open key material file: No such file or directory
Public bug reported: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory Status in systemd package in Ubuntu: New Bug description: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960863] Autopkgtest regression report (openssl/1.1.1f-1ubuntu2.11)
All autopkgtests for the newly accepted openssl (1.1.1f-1ubuntu2.11) for focal have finished running. The following regressions have been reported in tests triggered by the package: python3.8/3.8.10-0ubuntu1~20.04.2 (armhf, amd64) linux-hwe-5.11/5.11.0-60.60 (amd64) linux-azure-5.11/5.11.0-1029.32~20.04.2 (amd64) mysql-8.0/8.0.28-0ubuntu0.20.04.3 (i386) linux-gcp-5.13/5.13.0-1015.18~20.04.1 (amd64) linux-oem-5.13/5.13.0-1029.36 (amd64) kopanocore/8.7.0-7ubuntu1 (amd64) python3.9/3.9.5-3ubuntu0~20.04.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#openssl [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960863 Title: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Bug description: [Impact] Support for hardware pointer authentication for armv8 systems was merged in openssl 1.1.1f, but it contains a bug in the implementation for poly1305 message authenticated code routines, which causes the calling program to fail pointer authentication, which causes the program to crash with a segmentation fault. You can easily test it by accessing any website that uses poly1305. There is no workaround except use a different MAC. [Testcase] This bug applies to armv8 systems which support pointer authentication. Start an armv8 instance, such as a c7g graviton 3 instance on AWS, and make sure the paca flag is present in lscpu: $ grep paca /proc/cpuinfo Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng Next, attempt to connect to any website that uses poly1305 MAC. $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output gradle-7.2.bin % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Segmentation fault (core dumped) There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf327917-test Install it, and poly1305 operations will no longer segfault. [Where problems could occur] The patch changes the order of operations for loading the SP and checking the AUTIASP against it, from checking the AUTIASP against nothing then loading the correct SP to check with, to the correct loading the SP and then checking the AUTIASP against the SP. This only changes one code path for armv8 systems, and other architectures are not affected. This is also only limited to poly1305 MAC. If a regression were to occur, it would only affect users of poly1035 MAC on armv8 with pacs support. [Other info] The fix landed upstream in openssl 1.1.1i with the following commit: commit 5795acffd8706e1cb584284ee5bb3a30986d0e75 Author: Ard Biesheuvel Date: Tue Oct 27 18:02:40 2020 +0100 Subject: crypto/poly1305/asm: fix armv8 pointer authentication Link: https://github.com/openssl/openssl/commit/5795acffd8706e1cb584284ee5bb3a30986d0e75 This commit is already present in Impish onward. Only Focal needs the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
This reminds me a lot of https://bugs.launchpad.net/bugs/1871538 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: New Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set
** Changed in: apparmor (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1962035 Title: apparmor blocks VM installation when automatic UEFI firmware is set Status in apparmor package in Ubuntu: New Status in apparmor package in Debian: New Bug description: # lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Package: apparmor Version: 3.0.3-0ubuntu1 Package: virtinst Version: 1:3.2.0-3 When trying to re-install an existing VM with uefi boot set up using the recently introduced `--reinstall` option apparmor makes the installation fail with the following error: Could not open '/var/lib/libvirt/qemu/nvram/test_VARS.fd': Permission denied Steps to reproduce: Create a VM: root@ubuntu:~# virt-install --connect qemu:///system --quiet --os-variant fedora28 --memory 1024 --name test --wait -1 --disk size=1,format=qcow2 --print-xml 1 > /tmp/test1.xml Edit the VM configuration to enable automatic UEFI boot by changing the like follows: - + Define the VM: root@ubuntu:~# virsh define /tmp/test1.xml Start VM installation: root@ubuntu:~# virt-install --connect qemu:///system --reinstall test --wait -1 --noautoconsole --cdrom /var/lib/libvirt/novell.iso --autostart WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: 2022-02-23T18:56:54.738510Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/test_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/var/lib/libvirt/qemu/nvram/test_VARS.fd': Permission denied Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start test otherwise, please restart your installation. Expected behavior: VM installation will start without apparmor error. Actual behavior: The above denial happens: Feb 23 18:56:54 ubuntu audit[4420]: AVC apparmor="DENIED" operation="open" profile="libvirt- bdd92fa6-6030-4980-951c-2a52ec7e406c" name="/var/lib/libvirt/qemu/nvram/test_VARS.fd" pid=4420 comm="qemu- system-x86" requested_mask="r" denied_m> and stop the installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1962035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535840] Re: systemd ignoring /etc/modules due to blacklist
This issue makes it annoying to load watchdog drivers, as systemd now supports hardware watchdogs they'd have to be added to rc.local or a custom service. The pre-systemd behaviour only applied the blacklist with udev, not when processing /etc/modules(-load.d) so that they could be prevented from loading automatically unless explicitly listed by the user. So this is more of a regression due to behaviour change than opinion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in systemd package in Ubuntu: Opinion Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961837] Re: PackageKit 1.2.5 unable to perform upgrades
** Changed in: packagekit Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1961837 Title: PackageKit 1.2.5 unable to perform upgrades Status in PackageKit: Fix Released Status in packagekit package in Ubuntu: Fix Committed Status in packagekit source package in Jammy: Fix Committed Bug description: After being notified of upgrades available in Plasma Discover, I attempted to do an upgrade of all available packages. Unfortunately, it would not but also wouldn't show an error. I attempted to run 'pkcon update' which showed no available upgrades, whereas 'apt update' showed several packages available for upgrade. Expected behavior: 'pkcon update' would have performed the upgrade. Actual behavior: 'pkcon update' did nothing, saying no packages were available to upgrade. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: packagekit 1.2.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-lowlatency 5.15.12 Uname: Linux 5.15.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Feb 22 11:33:52 2022 InstallationDate: Installed on 2021-03-20 (338 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) SourcePackage: packagekit UpgradeStatus: Upgraded to jammy on 2021-11-07 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/packagekit/+bug/1961837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set
** Bug watch added: Debian Bug tracker #1006324 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006324 ** Also affects: apparmor (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006324 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1962035 Title: apparmor blocks VM installation when automatic UEFI firmware is set Status in apparmor package in Ubuntu: New Status in apparmor package in Debian: Unknown Bug description: # lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Package: apparmor Version: 3.0.3-0ubuntu1 Package: virtinst Version: 1:3.2.0-3 When trying to re-install an existing VM with uefi boot set up using the recently introduced `--reinstall` option apparmor makes the installation fail with the following error: Could not open '/var/lib/libvirt/qemu/nvram/test_VARS.fd': Permission denied Steps to reproduce: Create a VM: root@ubuntu:~# virt-install --connect qemu:///system --quiet --os-variant fedora28 --memory 1024 --name test --wait -1 --disk size=1,format=qcow2 --print-xml 1 > /tmp/test1.xml Edit the VM configuration to enable automatic UEFI boot by changing the like follows: - + Define the VM: root@ubuntu:~# virsh define /tmp/test1.xml Start VM installation: root@ubuntu:~# virt-install --connect qemu:///system --reinstall test --wait -1 --noautoconsole --cdrom /var/lib/libvirt/novell.iso --autostart WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: 2022-02-23T18:56:54.738510Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/test_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/var/lib/libvirt/qemu/nvram/test_VARS.fd': Permission denied Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start test otherwise, please restart your installation. Expected behavior: VM installation will start without apparmor error. Actual behavior: The above denial happens: Feb 23 18:56:54 ubuntu audit[4420]: AVC apparmor="DENIED" operation="open" profile="libvirt- bdd92fa6-6030-4980-951c-2a52ec7e406c" name="/var/lib/libvirt/qemu/nvram/test_VARS.fd" pid=4420 comm="qemu- system-x86" requested_mask="r" denied_m> and stop the installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1962035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962038] [NEW] wrong sysrq value in /usr/lib/sysctl.d/50-default.conf
Public bug reported: I've just learned that systemd is setting kernel.sysrq to 16 in /usr/lib/sysctl.d/50-default.conf. This is inconsistent with /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176 by default. systemd should drop its setting to defer to the file that we have been carrying in procps for a very long time. ** Affects: systemd (Ubuntu) Importance: High Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962038 Title: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf Status in systemd package in Ubuntu: New Bug description: I've just learned that systemd is setting kernel.sysrq to 16 in /usr/lib/sysctl.d/50-default.conf. This is inconsistent with /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176 by default. systemd should drop its setting to defer to the file that we have been carrying in procps for a very long time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962038] Re: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf
we may want to audit /usr/lib/sysctl.d vs /etc/sysctl.d to verify if there are any other settings that are being shadowed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1962038 Title: wrong sysrq value in /usr/lib/sysctl.d/50-default.conf Status in systemd package in Ubuntu: New Bug description: I've just learned that systemd is setting kernel.sysrq to 16 in /usr/lib/sysctl.d/50-default.conf. This is inconsistent with /etc/sysctl.d/10-magic-sysrq.conf which intentionally sets it to 176 by default. systemd should drop its setting to defer to the file that we have been carrying in procps for a very long time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
Seems related to https://bugs.launchpad.net/bugs/1961910 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: New Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
I did not find interesting journalctl, maybe someone else is luckier. ** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+attachment/5563112/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: New Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
The attached /var/log/apt/term.log does not show anything suspicious ** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+attachment/5563111/+files/apt-term.log ** Description changed: + Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. + Had to hard reset. + Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. + ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: New Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962036] Re: dbus was stopped during today's jammy update, breaking desktop
dpkg.log from that run ** Attachment added: "dpkg.log" https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+attachment/5563110/+files/dpkg.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: New Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962036] [NEW] dbus was stopped during today's jammy update, breaking desktop
Public bug reported: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1962036 Title: dbus was stopped during today's jammy update, breaking desktop Status in dbus package in Ubuntu: New Bug description: Impact: logind stopped, so desktop stopped, ssh stopped, got no getty. Had to hard reset. Today's jammy upgrade stopped dbus at 19:46:27 Feb 23 19:46:27 jak-t480s systemd[1]: Stopping D-Bus System Message Bus... This should not happen. I don't know which package caused this, but presumably dbus should not be stoppable in the first place. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dbus 1.12.20-2ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Feb 23 20:03:41 2022 InstallationDate: Installed on 2018-03-14 (1442 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1962036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962035] [NEW] apparmor blocks VM installation when automatic UEFI firmware is set
Public bug reported: # lsb_release -rd Description:Ubuntu 21.10 Release:21.10 Package: apparmor Version: 3.0.3-0ubuntu1 Package: virtinst Version: 1:3.2.0-3 When trying to re-install an existing VM with uefi boot set up using the recently introduced `--reinstall` option apparmor makes the installation fail with the following error: Could not open '/var/lib/libvirt/qemu/nvram/test_VARS.fd': Permission denied Steps to reproduce: Create a VM: root@ubuntu:~# virt-install --connect qemu:///system --quiet --os-variant fedora28 --memory 1024 --name test --wait -1 --disk size=1,format=qcow2 --print-xml 1 > /tmp/test1.xml Edit the VM configuration to enable automatic UEFI boot by changing the like follows: - + Define the VM: root@ubuntu:~# virsh define /tmp/test1.xml Start VM installation: root@ubuntu:~# virt-install --connect qemu:///system --reinstall test --wait -1 --noautoconsole --cdrom /var/lib/libvirt/novell.iso --autostart WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: 2022-02-23T18:56:54.738510Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/test_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/var/lib/libvirt/qemu/nvram/test_VARS.fd': Permission denied Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start test otherwise, please restart your installation. Expected behavior: VM installation will start without apparmor error. Actual behavior: The above denial happens: Feb 23 18:56:54 ubuntu audit[4420]: AVC apparmor="DENIED" operation="open" profile="libvirt-bdd92fa6-6030-4980-951c-2a52ec7e406c" name="/var/lib/libvirt/qemu/nvram/test_VARS.fd" pid=4420 comm="qemu- system-x86" requested_mask="r" denied_m> and stop the installation. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1962035 Title: apparmor blocks VM installation when automatic UEFI firmware is set Status in apparmor package in Ubuntu: New Bug description: # lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 Package: apparmor Version: 3.0.3-0ubuntu1 Package: virtinst Version: 1:3.2.0-3 When trying to re-install an existing VM with uefi boot set up using the recently introduced `--reinstall` option apparmor makes the installation fail with the following error: Could not open '/var/lib/libvirt/qemu/nvram/test_VARS.fd': Permission denied Steps to reproduce: Create a VM: root@ubuntu:~# virt-install --connect qemu:///system --quiet --os-variant fedora28 --memory 1024 --name test --wait -1 --disk size=1,format=qcow2 --print-xml 1 > /tmp/test1.xml Edit the VM configuration to enable automatic UEFI boot by changing the like follows: - + Define the VM: root@ubuntu:~# virsh define /tmp/test1.xml Start VM installation: root@ubuntu:~# virt-install --connect qemu:///system --reinstall test --wait -1 --noautoconsole --cdrom /var/lib/libvirt/novell.iso --autostart WARNING No operating system detected, VM performance may suffer. Specify an OS with --os-variant for optimal results. Starting install... ERRORinternal error: process exited while connecting to monitor: 2022-02-23T18:56:54.738510Z qemu-system-x86_64: -blockdev {"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/test_VARS.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}: Could not open '/var/lib/libvirt/qemu/nvram/test_VARS.fd': Permission denied Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start test otherwise, please restart your installation. Expected behavior: VM installation will start without apparmor error. Actual behavior: The above denial happens: Feb 23 18:56:54 ubuntu audit[4420]: AVC apparmor="DENIED" operation="open" profile="libvirt- bdd92fa6-6030-4980-951c-2a52ec7e406c" name="/var/lib/libvirt/qemu/nvram/test_VARS.fd" pid=4420 comm="qemu- system-x86" requested_mask="r" denied_m> and stop the installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1962035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424768] Re: Consider switching to path based activation
** Changed in: whoopsie (Ubuntu Bionic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1424768 Title: Consider switching to path based activation Status in whoopsie package in Ubuntu: Fix Released Status in whoopsie source package in Bionic: Won't Fix Bug description: 1) Ubuntu 15.04 2) 0.2.46 3) Whoopsie to only run when it is needed. 4) Instead it runs constantly, using network activity, l See bug (there are more..): https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/991481 also try: sudo fnotifystat -p whoopsie Instead whoopsie should use path based activation to only run when /var/crash has changed. http://www.freedesktop.org/software/systemd/man/systemd.path.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1424768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961805] Re: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main)
** Tags added: fr-2073 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1961805 Title: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main) Status in procps package in Ubuntu: Confirmed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. Dropped changes: - debian/README.sysctl: Debian has added this information. - debian/procps.install: debian/protect-links.conf has been re-named to debian/99-protect-links.conf, so it can be safely installed again (see LP: #1938585 for background). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959126] Re: Consider update to 3.68.2
** Tags removed: server-todo ** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1959126 Title: Consider update to 3.68.2 Status in nss package in Ubuntu: In Progress Bug description: Debian is shipping nss 3.73.1, but that is not an ESR release. Ubuntu is on 3.68, which is ESR, but two releases behind: upstream has 3.68.2. Here are upstream's release notes: 3.68.1: https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/jFIuiWbCphk Changes: - Bug 1735028 - check for missing signedData field. - Bug 1737470 - Ensure DER encoded signatures are within size limits. 3.68.2: https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/uGRwqw6Ove8 Change: - Bug 966856 - Add SHA-2 support to mozilla::pkix's OCSP implementation Our 3.68 package has a patch for CVE-2021-43527. It's unclear if any of the above changes is that CVE. The most promising one was bug 1737470, but the bug is private. The request here is to investigate if our patched 3.68 has one or more of the fixes in the above point releases, and if it would be worth it to go to 3.68.2. I think we should not go to 3.7x. Ubuntu has been on 3.68 since impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1959126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961800] Re: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
This issue is probably linked to a misuse of libexpat1 in the pyexpat python library. Also happening on debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Invalid Status in python-xmltodict package in Ubuntu: Confirmed Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962018] [NEW] pypy3compile errors during postinst confuses user
Public bug reported: Could you add some clarifying output in the postinst around pypy3compile failures to give context to an end user? The errors as they stand don't indicate that this is pyp3 specific and can be concerning (they also give the impression that QA isn't catching basic python bugs which isn't the case). pypy3 support was added to dh-python3 towards the end of 2018 as "WIP" such that postinst will call `pypy3compile $PACKAGE || true` to ignore errors if pypy3 is installed. I was talking with a user that saw this fail when installing an update for python3-software-properties and the error message was cause for concern and confusion, for that package it looked like this: Setting up python3-software-properties (0.99.19) ... Failed to byte-compile /usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py: File "/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 436 def __init__(self, sourceslist=None, /, files=None): ^ SyntaxError: invalid syntax (expected ')') That's all fine, the author has introduced the positional-only parameter (PEP570) new to python 3.8 and that's supported in cpython shipped by default in the distro, but it isn't supported by pypy3. I think it's reasonable for the maintainer of a package to decide that they want to use new features and that they might not have testing with pypy3 installed as a requirement. The fact that the failure is pypy3compile and not python3compile isn't communicated for the failure nor that it's optional. The user might think that the package is broken for the default interpreter. Would you consider adding a message before each compilation step to call out which interpreter is byte-compiling the module as well as pypy3 being optional/best-effort and may fail? Preferably you might also indicate the impact (i.e. the package is usable with the system python3 interpreter but pypy3) to set expectations with the end user. Thank you Piotr! ** Affects: dh-python (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/1962018 Title: pypy3compile errors during postinst confuses user Status in dh-python package in Ubuntu: New Bug description: Could you add some clarifying output in the postinst around pypy3compile failures to give context to an end user? The errors as they stand don't indicate that this is pyp3 specific and can be concerning (they also give the impression that QA isn't catching basic python bugs which isn't the case). pypy3 support was added to dh-python3 towards the end of 2018 as "WIP" such that postinst will call `pypy3compile $PACKAGE || true` to ignore errors if pypy3 is installed. I was talking with a user that saw this fail when installing an update for python3-software-properties and the error message was cause for concern and confusion, for that package it looked like this: Setting up python3-software-properties (0.99.19) ... Failed to byte-compile /usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py: File "/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py", line 436 def __init__(self, sourceslist=None, /, files=None): ^ SyntaxError: invalid syntax (expected ')') That's all fine, the author has introduced the positional-only parameter (PEP570) new to python 3.8 and that's supported in cpython shipped by default in the distro, but it isn't supported by pypy3. I think it's reasonable for the maintainer of a package to decide that they want to use new features and that they might not have testing with pypy3 installed as a requirement. The fact that the failure is pypy3compile and not python3compile isn't communicated for the failure nor that it's optional. The user might think that the package is broken for the default interpreter. Would you consider adding a message before each compilation step to call out which interpreter is byte-compiling the module as well as pypy3 being optional/best-effort and may fail? Preferably you might also indicate the impact (i.e. the package is usable with the system python3 interpreter but pypy3) to set expectations with the end user. Thank you Piotr! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1962018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961805] Re: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main)
Oh yes, of course. I will remember next time. Thank you for reviewing and sponsoring this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1961805 Title: Please merge procps 2:3.3.17-6 (main) from Debian unstable (main) Status in procps package in Ubuntu: Confirmed Bug description: This requires a merge because there are changes in the Ubuntu version not present in the Debian version. Dropped changes: - debian/README.sysctl: Debian has added this information. - debian/procps.install: debian/protect-links.conf has been re-named to debian/99-protect-links.conf, so it can be safely installed again (see LP: #1938585 for background). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1961805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/+subs
[Touch-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 Ubuntu Touch seeded 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_M
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages Mo
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 c
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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961983] Re: New Debian upstream: netcat-openbsd 1.218-4
** Changed in: netcat-openbsd (Ubuntu) Assignee: (unassigned) => Graham Inggs (ginggs) ** Changed in: netcat-openbsd (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1961983 Title: New Debian upstream: netcat-openbsd 1.218-4 Status in netcat-openbsd package in Ubuntu: In Progress Bug description: Debian has updated the package. We should merge the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1961983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
This bug was fixed in the package rsync - 3.1.2-2.1ubuntu1.3 --- rsync (3.1.2-2.1ubuntu1.3) bionic; urgency=medium * d/p/avoid-deadlock-huge-amounts-verbose-messages.patch: Allow the receiver to increase their iobuf.msg xbuf if it fills up. This ensures that the receiver will never block trying to output a message, and thus it will always drain the data from the sender and keep the whole thing from clogging up. Thanks to Wayne Davison . (LP: #1528921) -- Miriam España Acebal Tue, 08 Feb 2022 13:26:20 +0100 ** Changed in: rsync (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1528921 Title: rsync hangs on select(5, [], [4], [], {60, 0} Status in rsync: Unknown Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Bionic: Fix Released Status in rsync source package in Focal: Fix Committed Bug description: [Impact] What the user suffering from this bug experiences is that the big amount of informative messages related to the copy process with the three spawned processes(sender, receiver and generator) exhaust the I/O buffer and the sync gets stuck, either because there are too many files to synchronise and/or because too many detail messages (levels of verbose mode) have been requested in the output. The fix, that comes from upstream and is applied there since version 3.2.0., increments the size of the receiver's I/O buffer. [Test Plan] This test plan is for Focal, but it's the same for Bionic. 0.Preparing the test environment: #Preparing the container lxc launch images:ubuntu/focal rsync-iobuffer-focal lxc shell rsync-iobuffer-focal apt update -y apt upgrade -y #Installing necessary tools apt install rsync #Get test cases from comments #16 and #19 on this LP bug: As test case #16 covers both aspects (a lot of files and upper verbosity) and test #19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19 scenario (but, please, feel to reach me it if you consider it necessary and I'll provide the steps and bad/good scenarios). cd /tmp/ #16 Paste the contents of https://pastebin.com/raw/ctzJJGwt: #!/bin/bash mkdir source_dir pushd source_dir dd if=/dev/zero of=source bs=600K count=1 for i in `seq 1 11500`; do cp -v source file_$i; done rm source for i in `seq 1 10`; do dd if=/dev/zero of=file_large_$i bs=200M count=1 done popd echo "Created 11500 files with size 600K and 10 files with size 200M, try the following command:" echo "rsync -avvvz --delete source_dir target_dir" in a new file script_comment16.sh chmod +x script_comment16.sh ./script_comment16.sh 1. Bad cases (without and with using strace): # Scenario from comment 16 $ rsync -avvvz --delete source_dir target_dir sending incremental file list [sender] make_file(source_dir,*,0) send_file_list done [sender] pushing local filters for /root/source_dir/ [sender] make_file(source_dir/file_3048,*,2) [sender] make_file(source_dir/file_11358,*,2) [sender] make_file(source_dir/file_5914,*,2) [sender] make_file(source_dir/file_5880,*,2) [sender] make_file(source_dir/file_9318,*,2) [sender] make_file(source_dir/file_5539,*,2) [...] sending file_sum false_alarms=0 hash_hits=0 matches=0 sender finished source_dir/file_10807 send_files(903, source_dir/file_10808) send_files mapped source_dir/file_10808 of size 614400 calling match_sums source_dir/file_10808 source_dir/file_10808 It hangs here, where using strace we can see: $ strace rsync -avvvz --delete source_dir target_dir source_dir/file_11280 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) = 262144 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) = 262144 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) = 90112 select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left {tv_sec=59, tv_usec=96}) read(5, "\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 1900) = 1900 select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout) select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout) select(5, [], [4], [], {tv_sec=60, tv_usec=0} 1. Good cases: # Scenario from comment 16 $ rsync -avvvz --delete source_dir target_dir sending incremental file list [sender] make_file(source_dir,*,0) send_file_list done [sender] pushing local filters for /tmp/source_dir/ [sender] make_file(source_dir/file_3052,*,2) [sender] make_file(source_dir/file_1766,*,2) [sender] make_file(source_dir/file_10466,*,2) [sender] make_file(source_dir/file_9375,*,2) [sender] make_file(source_dir/file_7260,*,2) [s
[Touch-packages] [Bug 1528921] Update Released
The verification of the Stable Release Update for rsync has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1528921 Title: rsync hangs on select(5, [], [4], [], {60, 0} Status in rsync: Unknown Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Bionic: Fix Released Status in rsync source package in Focal: Fix Committed Bug description: [Impact] What the user suffering from this bug experiences is that the big amount of informative messages related to the copy process with the three spawned processes(sender, receiver and generator) exhaust the I/O buffer and the sync gets stuck, either because there are too many files to synchronise and/or because too many detail messages (levels of verbose mode) have been requested in the output. The fix, that comes from upstream and is applied there since version 3.2.0., increments the size of the receiver's I/O buffer. [Test Plan] This test plan is for Focal, but it's the same for Bionic. 0.Preparing the test environment: #Preparing the container lxc launch images:ubuntu/focal rsync-iobuffer-focal lxc shell rsync-iobuffer-focal apt update -y apt upgrade -y #Installing necessary tools apt install rsync #Get test cases from comments #16 and #19 on this LP bug: As test case #16 covers both aspects (a lot of files and upper verbosity) and test #19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19 scenario (but, please, feel to reach me it if you consider it necessary and I'll provide the steps and bad/good scenarios). cd /tmp/ #16 Paste the contents of https://pastebin.com/raw/ctzJJGwt: #!/bin/bash mkdir source_dir pushd source_dir dd if=/dev/zero of=source bs=600K count=1 for i in `seq 1 11500`; do cp -v source file_$i; done rm source for i in `seq 1 10`; do dd if=/dev/zero of=file_large_$i bs=200M count=1 done popd echo "Created 11500 files with size 600K and 10 files with size 200M, try the following command:" echo "rsync -avvvz --delete source_dir target_dir" in a new file script_comment16.sh chmod +x script_comment16.sh ./script_comment16.sh 1. Bad cases (without and with using strace): # Scenario from comment 16 $ rsync -avvvz --delete source_dir target_dir sending incremental file list [sender] make_file(source_dir,*,0) send_file_list done [sender] pushing local filters for /root/source_dir/ [sender] make_file(source_dir/file_3048,*,2) [sender] make_file(source_dir/file_11358,*,2) [sender] make_file(source_dir/file_5914,*,2) [sender] make_file(source_dir/file_5880,*,2) [sender] make_file(source_dir/file_9318,*,2) [sender] make_file(source_dir/file_5539,*,2) [...] sending file_sum false_alarms=0 hash_hits=0 matches=0 sender finished source_dir/file_10807 send_files(903, source_dir/file_10808) send_files mapped source_dir/file_10808 of size 614400 calling match_sums source_dir/file_10808 source_dir/file_10808 It hangs here, where using strace we can see: $ strace rsync -avvvz --delete source_dir target_dir source_dir/file_11280 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) = 262144 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) = 262144 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) = 90112 select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left {tv_sec=59, tv_usec=96}) read(5, "\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 1900) = 1900 select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout) select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout) select(5, [], [4], [], {tv_sec=60, tv_usec=0} 1. Good cases: # Scenario from comment 16 $ rsync -avvvz --delete source_dir target_dir sending incremental file list [sender] make_file(source_dir,*,0) send_file_list done [sender] pushing local filters for /tmp/source_dir/ [sender] make_file(source_dir/file_3052,*,2) [sender] make_file(source_dir/file_1766,*,2) [sender] make_file(source_dir/file_10466,*,2) [sender] make_file(source_dir/file_9375,*,2) [sender] make_file(source_dir/file_7260,*,2) [sender] make_file(source_dir/file_5554,*,2) [sender] make_file(source_dir/file_5523,*,2) [sender] make_file(source_dir/file_1685,*,2) [sender] make_file(source_dir/file_
[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
Focal is in freeze for the point release, but I don't see there being any practical issue with releasing to Bionic now. It seems unlikely that a user would be surprised by a regression on this issue upgrading from Bionic to Focal in the next week. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1528921 Title: rsync hangs on select(5, [], [4], [], {60, 0} Status in rsync: Unknown Status in rsync package in Ubuntu: Fix Released Status in rsync source package in Bionic: Fix Released Status in rsync source package in Focal: Fix Committed Bug description: [Impact] What the user suffering from this bug experiences is that the big amount of informative messages related to the copy process with the three spawned processes(sender, receiver and generator) exhaust the I/O buffer and the sync gets stuck, either because there are too many files to synchronise and/or because too many detail messages (levels of verbose mode) have been requested in the output. The fix, that comes from upstream and is applied there since version 3.2.0., increments the size of the receiver's I/O buffer. [Test Plan] This test plan is for Focal, but it's the same for Bionic. 0.Preparing the test environment: #Preparing the container lxc launch images:ubuntu/focal rsync-iobuffer-focal lxc shell rsync-iobuffer-focal apt update -y apt upgrade -y #Installing necessary tools apt install rsync #Get test cases from comments #16 and #19 on this LP bug: As test case #16 covers both aspects (a lot of files and upper verbosity) and test #19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19 scenario (but, please, feel to reach me it if you consider it necessary and I'll provide the steps and bad/good scenarios). cd /tmp/ #16 Paste the contents of https://pastebin.com/raw/ctzJJGwt: #!/bin/bash mkdir source_dir pushd source_dir dd if=/dev/zero of=source bs=600K count=1 for i in `seq 1 11500`; do cp -v source file_$i; done rm source for i in `seq 1 10`; do dd if=/dev/zero of=file_large_$i bs=200M count=1 done popd echo "Created 11500 files with size 600K and 10 files with size 200M, try the following command:" echo "rsync -avvvz --delete source_dir target_dir" in a new file script_comment16.sh chmod +x script_comment16.sh ./script_comment16.sh 1. Bad cases (without and with using strace): # Scenario from comment 16 $ rsync -avvvz --delete source_dir target_dir sending incremental file list [sender] make_file(source_dir,*,0) send_file_list done [sender] pushing local filters for /root/source_dir/ [sender] make_file(source_dir/file_3048,*,2) [sender] make_file(source_dir/file_11358,*,2) [sender] make_file(source_dir/file_5914,*,2) [sender] make_file(source_dir/file_5880,*,2) [sender] make_file(source_dir/file_9318,*,2) [sender] make_file(source_dir/file_5539,*,2) [...] sending file_sum false_alarms=0 hash_hits=0 matches=0 sender finished source_dir/file_10807 send_files(903, source_dir/file_10808) send_files mapped source_dir/file_10808 of size 614400 calling match_sums source_dir/file_10808 source_dir/file_10808 It hangs here, where using strace we can see: $ strace rsync -avvvz --delete source_dir target_dir source_dir/file_11280 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) = 262144 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) = 262144 read(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) = 90112 select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left {tv_sec=59, tv_usec=96}) read(5, "\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 1900) = 1900 select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout) select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout) select(5, [], [4], [], {tv_sec=60, tv_usec=0} 1. Good cases: # Scenario from comment 16 $ rsync -avvvz --delete source_dir target_dir sending incremental file list [sender] make_file(source_dir,*,0) send_file_list done [sender] pushing local filters for /tmp/source_dir/ [sender] make_file(source_dir/file_3052,*,2) [sender] make_file(source_dir/file_1766,*,2) [sender] make_file(source_dir/file_10466,*,2) [sender] make_file(source_dir/file_9375,*,2) [sender] make_file(source_dir/file_7260,*,2) [sender] make_file(source_dir/file_5554,*,2) [sender] make_file(source_dir/file_5523,*,2) [sender] make_file(source_dir/file_1685,*,2) [sender] make_file(source_dir/file_7217,*,2) [sender] make_file(source_dir/file_10411,*,2) [...] generate_files finished sent 9,555,678 bytes received 3,599,560 bytes 124,694.20 bytes/sec total size is 9,162,752,000 speedup is 696.51
[Touch-packages] [Bug 1960297] Re: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main)
We agreed to submit this patch to Debian before sponsoring. I just found out that a pull request by the original author of the patch in Ubuntu already exists: https://salsa.debian.org/openstack- team/python/python-testtools/-/merge_requests/5 Thanks, Olivier -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/1960297 Title: Please merge python-testtools 2.5.0-3 (main) from Debian unstable (main) Status in python-testtools package in Ubuntu: Confirmed Bug description: python-testtools Mon Dec 27 21:14:53 2021 base: 2.5.0-2 python-testtools_2.5.0-2.dsc python-testtools_2.5.0.orig.tar.xz python-testtools_2.5.0-2.debian.tar.xz ubuntu: 2.5.0-2ubuntu1 python-testtools_2.5.0-2ubuntu1.dsc python-testtools_2.5.0.orig.tar.xz python-testtools_2.5.0-2ubuntu1.debian.tar.xz base -> ubuntu python-testtools_2.5.0-2ubuntu1.patch debian: 2.5.0-3 python-testtools_2.5.0-3.dsc python-testtools_2.5.0.orig.tar.xz python-testtools_2.5.0-3.debian.tar.xz base -> debian python-testtools_2.5.0-3.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/1960297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961983] Re: New Debian upstream: netcat-openbsd 1.218-4
** Patch added: "netcat-openbsd_1.218-3ubuntu1..1.218-4ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1961983/+attachment/5563026/+files/netcat-openbsd_1.218-3ubuntu1..1.218-4ubuntu1.debdiff ** Changed in: netcat-openbsd (Ubuntu) Status: New => Confirmed ** Tags added: fr-2071 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1961983 Title: New Debian upstream: netcat-openbsd 1.218-4 Status in netcat-openbsd package in Ubuntu: Confirmed Bug description: Debian has updated the package. We should merge the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1961983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961983] Re: New Debian upstream: netcat-openbsd 1.218-4
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1961983 Title: New Debian upstream: netcat-openbsd 1.218-4 Status in netcat-openbsd package in Ubuntu: Confirmed Bug description: Debian has updated the package. We should merge the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1961983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961981] Re: Current delta applied twice, not needed
ACK, other changes look good. Synced. Thanks! ** Changed in: audit (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1961981 Title: Current delta applied twice, not needed Status in audit package in Ubuntu: Fix Released Bug description: audit has this ubuntu delta: * Merge with Debian unstable. Remaining changes: - debian/rules: Disable auditd network listener, with --disable-listener, to reduce the risk of a remote attack on auditd, which runs as root Turns out this was adopted in debian since 1:2.8.5-1: * debian/rules: On Ubuntu and derivatives, disable auditd network listener with --disable-listener Debian's change is: # Merge the last remaining Ubuntu specific change in Debian: # Disable auditd network listener to reduce the risk of a remote attack on # auditd, which runs as root ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes), yes) CONFIGURE_FLAGS += --disable-listener endif and ours is to add --disable-listener explicitly. d/rules ends up being: dh_auto_configure -- \ --sbindir=/sbin \ --libdir=/lib/${DEB_HOST_MULTIARCH} \ --enable-shared=audit \ --enable-gssapi-krb5 \ --disable-listener \ --with-apparmor \ --with-libwrap \ --with-libcap-ng \ $(CONFIGURE_FLAGS) \ --with-arm --with-aarch64 ${EXTRA_ARCH_TABLE} CONFIGURE_FLAGS gets --disable-listener on ubuntu, and we add it again. The delta can be dropped. Then it's just a matter of checking the other debian changes and, if deemed appropriate, sync the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1961981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961983] [NEW] New Debian upstream: netcat-openbsd 1.218-4
Public bug reported: Debian has updated the package. We should merge the changes. ** Affects: netcat-openbsd (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: fr-2071 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1961983 Title: New Debian upstream: netcat-openbsd 1.218-4 Status in netcat-openbsd package in Ubuntu: Confirmed Bug description: Debian has updated the package. We should merge the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1961983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961981] [NEW] Current delta applied twice, not needed
Public bug reported: audit has this ubuntu delta: * Merge with Debian unstable. Remaining changes: - debian/rules: Disable auditd network listener, with --disable-listener, to reduce the risk of a remote attack on auditd, which runs as root Turns out this was adopted in debian since 1:2.8.5-1: * debian/rules: On Ubuntu and derivatives, disable auditd network listener with --disable-listener Debian's change is: # Merge the last remaining Ubuntu specific change in Debian: # Disable auditd network listener to reduce the risk of a remote attack on # auditd, which runs as root ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes), yes) CONFIGURE_FLAGS += --disable-listener endif and ours is to add --disable-listener explicitly. d/rules ends up being: dh_auto_configure -- \ --sbindir=/sbin \ --libdir=/lib/${DEB_HOST_MULTIARCH} \ --enable-shared=audit \ --enable-gssapi-krb5 \ --disable-listener \ --with-apparmor \ --with-libwrap \ --with-libcap-ng \ $(CONFIGURE_FLAGS) \ --with-arm --with-aarch64 ${EXTRA_ARCH_TABLE} CONFIGURE_FLAGS gets --disable-listener on ubuntu, and we add it again. The delta can be dropped. Then it's just a matter of checking the other debian changes and, if deemed appropriate, sync the package. ** Affects: audit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1961981 Title: Current delta applied twice, not needed Status in audit package in Ubuntu: New Bug description: audit has this ubuntu delta: * Merge with Debian unstable. Remaining changes: - debian/rules: Disable auditd network listener, with --disable-listener, to reduce the risk of a remote attack on auditd, which runs as root Turns out this was adopted in debian since 1:2.8.5-1: * debian/rules: On Ubuntu and derivatives, disable auditd network listener with --disable-listener Debian's change is: # Merge the last remaining Ubuntu specific change in Debian: # Disable auditd network listener to reduce the risk of a remote attack on # auditd, which runs as root ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes), yes) CONFIGURE_FLAGS += --disable-listener endif and ours is to add --disable-listener explicitly. d/rules ends up being: dh_auto_configure -- \ --sbindir=/sbin \ --libdir=/lib/${DEB_HOST_MULTIARCH} \ --enable-shared=audit \ --enable-gssapi-krb5 \ --disable-listener \ --with-apparmor \ --with-libwrap \ --with-libcap-ng \ $(CONFIGURE_FLAGS) \ --with-arm --with-aarch64 ${EXTRA_ARCH_TABLE} CONFIGURE_FLAGS gets --disable-listener on ubuntu, and we add it again. The delta can be dropped. Then it's just a matter of checking the other debian changes and, if deemed appropriate, sync the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1961981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628910] Re: netcat silently fails without error message when not using -v
** Changed in: netcat-openbsd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1628910 Title: netcat silently fails without error message when not using -v Status in netcat-openbsd package in Ubuntu: Won't Fix Bug description: $ nc localhost 1234 $ nc -v localhost 1234 nc: connect to localhost port 1234 (tcp) failed: Connection refused even without the -v option I expect nc to report any errors to stderr instead of just exiting. i sometimes use nc together with tar as a simple file transfer tool and its pretty handy to know what is going on. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: netcat-openbsd 1.105-7ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 CurrentDesktop: Unity Date: Thu Sep 29 12:37:32 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libbsd0 0.8.2-1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netcat-openbsd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1628910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628910] Re: netcat silently fails without error message when not using -v
Debian adopts the package source from OpenBSD. Please, address the OpenBSD maintainer to have your suggestion considered. Cf. https://github.com/openbsd/, https://www.openbsd.org/report.html. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1628910 Title: netcat silently fails without error message when not using -v Status in netcat-openbsd package in Ubuntu: Won't Fix Bug description: $ nc localhost 1234 $ nc -v localhost 1234 nc: connect to localhost port 1234 (tcp) failed: Connection refused even without the -v option I expect nc to report any errors to stderr instead of just exiting. i sometimes use nc together with tar as a simple file transfer tool and its pretty handy to know what is going on. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: netcat-openbsd 1.105-7ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 CurrentDesktop: Unity Date: Thu Sep 29 12:37:32 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libbsd0 0.8.2-1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netcat-openbsd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1628910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961800] Re: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
Confirm the problem on focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Invalid Status in python-xmltodict package in Ubuntu: Confirmed Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1872983] Re: in netcat-openbsd manpage, port argument description is not good
This package is copied from Debian. Please, open send a bug report there. Cf. https://www.debian.org/Bugs/Reporting. ** Changed in: netcat-openbsd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1872983 Title: in netcat-openbsd manpage, port argument description is not good Status in netcat-openbsd package in Ubuntu: Confirmed Bug description: in netcat-openbsd manpage, port argument description is not good. it is this: "port can be a specified as a numeric port number, or as a service name. Ports may be specified in a range of the form nn-mm. In general, a destination port must be specified, unless the -U option is given." why this is not good: really, the port argument also is used as source port: while using "nc -l 1234". this "nc -l 1234" is an example from the manpage in "CLIENT/SERVER MODEL" section, which is immediately after the port argument description. and this command works correctly. (while connecting from other computer with nc IPaddressHere 1234, it works, and in that case i think it is destination port, and thus source port for the command on first laptop. it must be source port on first comp, because a process must listen on a specific source port, they do not usually listen on all ports, as i know from my experience... unless it is something like tcpdump, and such programs run with root permission, while netcat runs with non-root permission... and it is because processes should not access to listening ports of other processes... ) the text "In general, a destination port must be specified, unless the -U option is given." is not good, because it says "must" and says "in general", and it is hard to disambiguate this. it can be understood as "in general" refers to the all cases except the "unless the -U option is given". in that way of understanding, it means that if the -U option is not given, it must be source port only. but really it is not so. so, "in general" does not refer to the all cases except the "unless the -U option is given". it just means, that destination port is more usually used in this place. but this way of understanding is also hard to accept, because the usage, the intention of the extra word "must" becomes not understood. it is extra, because it can be said shorter: "a destination port is specified", or it can be said with less of the fierce: "a destination port should be specified". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1872983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628910] Re: netcat silently fails without error message when not using -v
** Changed in: netcat-openbsd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1628910 Title: netcat silently fails without error message when not using -v Status in netcat-openbsd package in Ubuntu: Confirmed Bug description: $ nc localhost 1234 $ nc -v localhost 1234 nc: connect to localhost port 1234 (tcp) failed: Connection refused even without the -v option I expect nc to report any errors to stderr instead of just exiting. i sometimes use nc together with tar as a simple file transfer tool and its pretty handy to know what is going on. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: netcat-openbsd 1.105-7ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CasperVersion: 1.376 CurrentDesktop: Unity Date: Thu Sep 29 12:37:32 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libbsd0 0.8.2-1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 LiveMediaBuild: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netcat-openbsd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1628910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1961800] Re: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal)
This can be reproduced without xmltodict, using only the stdlib: >>> from xml.parsers import expat >>> parser = expat.ParserCreate(namespace_separator=':') >>> parser.Parse('', True) Traceback (most recent call last): File "", line 1, in xml.parsers.expat.ExpatError: out of memory: line 1, column 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to expat in Ubuntu. https://bugs.launchpad.net/bugs/1961800 Title: Seeing out of memory errors after libexpat1 upgrade to 2.2.5-3ubuntu0.4 (bionic) or 2.2.9-1ubuntu0.2 (focal) Status in expat package in Ubuntu: Invalid Status in python-xmltodict package in Ubuntu: Confirmed Bug description: I started seeing errors parsing XML files today (Feb 22, 2022) after my system was updated to 2.2.5-3ubuntu0.4. This is on a bionic server. The parsing is being done by python3's xmltodict module, which uses python3 expat as the actual parser. This is the error it raises: xml.parsers.expat.ExpatError: out of memory: line 1, column 0 So far this is happening on multiple xml files, although they all come from the same source (these are jenkins config.xml files). I'm working on coming up with a minimal test case which I'll provide once I have it cleaned up of any private data. [System info] $ lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 $ apt-cache policy libexpat1 libexpat1: Installed: 2.2.5-3ubuntu0.4 Candidate: 2.2.5-3ubuntu0.4 Version table: *** 2.2.5-3ubuntu0.4 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.2.5-3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1961800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1900197] Re: netcat fails with an error with -v
In netcat-openbsd 1.218-3ubuntu1 used by Ubuntu Jammy the message is only a warning and only written if providing the -v argument. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1900197 Title: netcat fails with an error with -v Status in netcat-openbsd package in Ubuntu: Confirmed Bug description: In a fresh install of Ubuntu Server 20.04.1, netcat -vlp 8000 fails with the following error message: netcat: getnameinfo: Temporary failure in name resolution Name resolution, both forwards and backwards, works as expected elsewhere (e.g., ping or nslookup). There's an upstream Debian patch that changes getnameinfo() errors into warnings that should suffice. I'm not sure whether the underlying getnameinfo() error is inherited as well, but neither Debian Buster or Sid have such an error, nor does Ubuntu Server 18.04.5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1900197/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960863] Re: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances
This was a perfectly researched and written up bug and patch and made SRU review easy. Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960863 Title: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Bug description: [Impact] Support for hardware pointer authentication for armv8 systems was merged in openssl 1.1.1f, but it contains a bug in the implementation for poly1305 message authenticated code routines, which causes the calling program to fail pointer authentication, which causes the program to crash with a segmentation fault. You can easily test it by accessing any website that uses poly1305. There is no workaround except use a different MAC. [Testcase] This bug applies to armv8 systems which support pointer authentication. Start an armv8 instance, such as a c7g graviton 3 instance on AWS, and make sure the paca flag is present in lscpu: $ grep paca /proc/cpuinfo Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng Next, attempt to connect to any website that uses poly1305 MAC. $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output gradle-7.2.bin % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Segmentation fault (core dumped) There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf327917-test Install it, and poly1305 operations will no longer segfault. [Where problems could occur] The patch changes the order of operations for loading the SP and checking the AUTIASP against it, from checking the AUTIASP against nothing then loading the correct SP to check with, to the correct loading the SP and then checking the AUTIASP against the SP. This only changes one code path for armv8 systems, and other architectures are not affected. This is also only limited to poly1305 MAC. If a regression were to occur, it would only affect users of poly1035 MAC on armv8 with pacs support. [Other info] The fix landed upstream in openssl 1.1.1i with the following commit: commit 5795acffd8706e1cb584284ee5bb3a30986d0e75 Author: Ard Biesheuvel Date: Tue Oct 27 18:02:40 2020 +0100 Subject: crypto/poly1305/asm: fix armv8 pointer authentication Link: https://github.com/openssl/openssl/commit/5795acffd8706e1cb584284ee5bb3a30986d0e75 This commit is already present in Impish onward. Only Focal needs the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960863] Re: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances
Hello Matthew, or anyone else affected, Accepted openssl into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssl/1.1.1f-1ubuntu2.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: openssl (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1960863 Title: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Focal: Fix Committed Bug description: [Impact] Support for hardware pointer authentication for armv8 systems was merged in openssl 1.1.1f, but it contains a bug in the implementation for poly1305 message authenticated code routines, which causes the calling program to fail pointer authentication, which causes the program to crash with a segmentation fault. You can easily test it by accessing any website that uses poly1305. There is no workaround except use a different MAC. [Testcase] This bug applies to armv8 systems which support pointer authentication. Start an armv8 instance, such as a c7g graviton 3 instance on AWS, and make sure the paca flag is present in lscpu: $ grep paca /proc/cpuinfo Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng Next, attempt to connect to any website that uses poly1305 MAC. $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output gradle-7.2.bin % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Segmentation fault (core dumped) There is a test package available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf327917-test Install it, and poly1305 operations will no longer segfault. [Where problems could occur] The patch changes the order of operations for loading the SP and checking the AUTIASP against it, from checking the AUTIASP against nothing then loading the correct SP to check with, to the correct loading the SP and then checking the AUTIASP against the SP. This only changes one code path for armv8 systems, and other architectures are not affected. This is also only limited to poly1305 MAC. If a regression were to occur, it would only affect users of poly1035 MAC on armv8 with pacs support. [Other info] The fix landed upstream in openssl 1.1.1i with the following commit: commit 5795acffd8706e1cb584284ee5bb3a30986d0e75 Author: Ard Biesheuvel Date: Tue Oct 27 18:02:40 2020 +0100 Subject: crypto/poly1305/asm: fix armv8 pointer authentication Link: https://github.com/openssl/openssl/commit/5795acffd8706e1cb584284ee5bb3a30986d0e75 This commit is already present in Impish onward. Only Focal needs the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
> However, Focal (which uses klibc 2.0.7) uses dhclient for networking initialization instead of ipconfig... If no users in Focal could be affected by the bug then I'm fine with accepting the fix to Bionic only. But could you please expand on the above statement? Under what conditions does Focal use dhclient instead of ipconfig? Presumably through initramfs-tools and ip=/ip6=? Are there any other situations where users could reasonably be using klibc/ipconfig on Focal? Is it possible for them to be doing this but not using initramfs-tools? It would help me understand if you could present a complete user story to explain the user impact. Right now the bug description doesn't explain the full scenario under which they would be impacted by this bug. > [Where problems could occur] I don't think you've really answered this question. What different scenarios, from a user perspective (ie. user stories), can reasonably be predicted that will hit this ipconfig DHCP-related timeout case? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases Status in klibc package in Ubuntu: New Status in klibc source package in Bionic: In Progress Bug description: [Impact] In some cases, ipconfig can take a longer time than the user-specified timeouts, causing unexpected delays. [Test Plan] Any situation where ipconfig encounters an error sending the DHCP packet, it will automatically set a delay of 10 seconds, which could be longer than the user-specified timeout. It can be reproduced by creating a dummy interface and attempting to run ipconfig on it with a timeout value of less than 10: # ip link add eth1 type dummy # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date Thu Nov 18 04:46:13 EST 2021 IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP IP-Config: no response after 2 secs - giving up Thu Nov 18 04:46:23 EST 2021 ^ Notice above, ipconfig thinks that it waited 2 seconds, but the timestamps show an actual delay of 10 seconds. [Where problems could occur] Please see reproduction steps above. We are seeing this in production too (see comment #2). [Other Info] A patch to fix the issue is being proposed here. It is a safe fix - it only checks before going into sleep that the timeout never exceeds the user-requested value. [Original Description] In some cases, ipconfig can take longer than the user-specified timeouts, causing unexpected delays. in main.c, in function loop(), the process can go into process_timeout_event() (or process_receive_event() ) and if it encounters an error situation, will set an attempt to "try again later" at time equal now + 10 seconds by setting s->expire = now + 10; This can happen at any time during the main event loop, which can end up extending the user-specified timeout if "now + 10" is greater than "start_time + user-specified-timeout". I believe a patch like the following is needed to avoid this problem: --- a/usr/kinit/ipconfig/main.c +++ b/usr/kinit/ipconfig/main.c @@ -437,6 +437,13 @@ static int loop(void) if (timeout > s->expire - now.tv_sec) timeout = s->expire - now.tv_sec; + + /* Compensate for already-lost time */ + gettimeofday(&now, NULL); + if (now.tv_sec + timeout > start + loop_timeout) { + timeout = loop_timeout - (now.tv_sec - start); + printf("Lowered timeout to match user request = (%d s) \n", timeout); + } } I believe the current behaviour is buggy. This is confirmed when the following line is executed: if (loop_timeout >= 0 && now.tv_sec - start >= loop_timeout) { printf("IP-Config: no response after %d " "secs - giving up\n", loop_timeout); rc = -1; goto bail; } 'loop_timeout' is the user-specified time-out. With a value of 2, in case of error, this line prints: IP-Config: no response after 2 secs - giving up So it thinks that it waited 2 seconds - however, in reality it had actually waited for 10 seconds. The suggested code-change ensures that the timeout that is actually used never exceeds the user-specified timeout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1947099/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-pa
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to python3-defaults 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1960404] Re: merge python-debian 0.1.43 from Debian sid
This bug was fixed in the package python-debian - 0.1.43ubuntu1 --- python-debian (0.1.43ubuntu1) jammy; urgency=low * Merge from Debian unstable (LP: #1960404). Remaining changes: * Add support for zstd compression format (LP: #1923845) -> the patch has been rewritten to account for upstream work on this particular area and their move to dynamically generated test packages python-debian (0.1.43) unstable; urgency=medium [ Jelmer Vernooij ] * Support the Files-Included field in debian/copyright. [ Stuart Prescott ] * Always run both mypy and pylint on CI. * Fix URL for API documentation in README.rst (Closes: #995442). * RTS parser: minor documentation fixes. * Declare minimum Python version of 3.5 for most modules except the RTS parser. Add CI testing with Python 3.5 (Closes: #997857). [ Niels Thykier ] * RTS parser: Handle leading tabs for setting values (Closes: #996785). * RTS parser: Preserve original field case (Closes: #996784). * RTS parser: Expose str type for keys in paragraphs (Closes: #996783). python-debian (0.1.42) unstable; urgency=medium "The Hitchhiker's Guide to the Galaxy" release. [ Jelmer Vernooij ] * Use logging for warnings about data that's being read, rather than the warnings module. [ Stuart Prescott ] * Fix type checks for mypy 0.910 * Refactor CI code to be less repetitive. * Fix autopkgtest invocation of py.test. * Silence lintian complaint about touching the dpkg database in the examples. * Update Standards-Version to 4.6.0 (no changes required). * Add RTS parser to setup.py so that it is installed. * Add copyright attribution for RTS parser. [ Niels Thykier ] * RTS parser: Accept tabs as continuation line marker. Closes: #994854 * Interpretation: Preserve tab as continuation line if used * CI: Always build docs; only publish it for master * RTS parser: Make value interpretation tokenization consistent * RTS parser: Add interpretation for Uploaders field python-debian (0.1.41) experimental; urgency=medium [ Stuart Prescott ] * Drop some old python version checks (Closes: #986550) * Skip tests that use apt_pkg if unavailable * Run tests in absense of recommended packages * Drop use of six. * Drop old version constraints in autopkgtest tests * Generate .deb packages for tests on-demand * Add contextmanager to DebFile * Fix sphinx _static config [ Niels Thykier ] * Added format/comment preserving deb822 parser as debian._deb822_repro. * CI: Add coverage reports * Use py.test for running tests [ Jelmer Vernooij ] * Add Build-Depends-Arch, Build-Conflicts-Arch to list of relationship fields. Closes: #985492 python-debian (0.1.40) experimental; urgency=medium [ Jelmer Vernooij ] * In debian.changelog.get_maintainer, cope with unknown UIDs. Closes: #980385 [ Niels Thykier ] * Add some doctest SKIP markers to the code (MR!45). * Fix examples in code (MR!41, MR!43). [ Frédéric Pierret ] * Numerous enhancements to the deb822.BuildInfo class (MR!40). [ Stuart Prescott ] * Update annotations for mypy 0.8.00. * Include portability patch for pwd module on Windows from MR!38, with thanks to Ryan Pavlik for the report and Carmen Bianca Bakker for the implementation. * Drop the deb822.BuildInfo.get_debian_suite function. * Stop testing with Python 2.7. [ Debian Janitor ] * Remove constraints unnecessary since stretch: + Build-Depends: Drop versioned constraint on binutils. -- Simon Chopin Wed, 09 Feb 2022 12:27:26 +0100 ** Changed in: python-debian (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-debian in Ubuntu. https://bugs.launchpad.net/bugs/1960404 Title: merge python-debian 0.1.43 from Debian sid Status in python-debian package in Ubuntu: Fix Released Bug description: Please merge the latest Debian version of this package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1960404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp