[Touch-packages] [Bug 1950533] Re: Logging into Discord with DRM streaming in other Firefox tab breaks sound.
I cannot reproduce this error on an XPS 13. Suspect it may be hardware- specific. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1950533 Title: Logging into Discord with DRM streaming in other Firefox tab breaks sound. Status in firefox package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: What I expect to happen: seamless sound in multiple Firefox tabs What happens instead: While playing a certain youtube music stream with a clean browser history/cache: https://www.youtube.com/watch?v=5qap5aO4i9A I open another tab and log into Discord (in browser). As soon as I successfully log in, the sound from the youtube stream goes staticky and requires a pulseaudio -k (followed by a refresh of youtube) to remedy. $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy firefox firefox: Installed: 94.0+build3-0ubuntu0.20.04.1 Candidate: 94.0+build3-0ubuntu0.20.04.1 $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.12 Candidate: 1:13.99.1-1ubuntu3.12 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 94.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: username 36216 F pulseaudio /dev/snd/controlC2: username 36216 F pulseaudio /dev/snd/controlC0: username 36216 F pulseaudio BuildID: 20211028161635 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 20:15:31 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-11-11 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.1.1 dev enp3s0 proto dhcp metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.152 metric 100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=94.0/20211028161635 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.80 dmi.board.name: B550M/ac 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:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/22/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB550M/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1950533/+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 1949778] Re: unittest2 doesn't work on python3.10
** Changed in: unittest2 (Debian) Status: New => Fix Released -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in gitinspector package in Ubuntu: Fix Released Status in python-cloudkittyclient package in Ubuntu: Fix Released Status in python-cyborgclient package in Ubuntu: Fix Released Status in python-deprecation package in Ubuntu: Fix Released Status in python-freezerclient package in Ubuntu: Fix Released Status in python-futurist package in Ubuntu: Invalid Status in python-jenkins package in Ubuntu: Fix Released Status in python-launchpadlib package in Ubuntu: Invalid Status in python-pyghmi package in Ubuntu: Fix Released Status in python-pykmip package in Ubuntu: Fix Released Status in python-requests-mock package in Ubuntu: Fix Released Status in python-sphinx-feature-classification package in Ubuntu: Fix Released Status in python-sushy-cli package in Ubuntu: Fix Released Status in python-testtools package in Ubuntu: Invalid Status in python-tosca-parser package in Ubuntu: Fix Released Status in python-yaql package in Ubuntu: Fix Released Status in tempest package in Ubuntu: Fix Released Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: Fix Released Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitinspector/+bug/1949778/+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 1950533] Re: Logging into Discord with DRM streaming in other Firefox tab breaks sound.
Related: https://bugs.launchpad.net/ubuntu/+bug/1950539 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1950533 Title: Logging into Discord with DRM streaming in other Firefox tab breaks sound. Status in firefox package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: What I expect to happen: seamless sound in multiple Firefox tabs What happens instead: While playing a certain youtube music stream with a clean browser history/cache: https://www.youtube.com/watch?v=5qap5aO4i9A I open another tab and log into Discord (in browser). As soon as I successfully log in, the sound from the youtube stream goes staticky and requires a pulseaudio -k (followed by a refresh of youtube) to remedy. $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy firefox firefox: Installed: 94.0+build3-0ubuntu0.20.04.1 Candidate: 94.0+build3-0ubuntu0.20.04.1 $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.12 Candidate: 1:13.99.1-1ubuntu3.12 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 94.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: username 36216 F pulseaudio /dev/snd/controlC2: username 36216 F pulseaudio /dev/snd/controlC0: username 36216 F pulseaudio BuildID: 20211028161635 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 20:15:31 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-11-11 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.1.1 dev enp3s0 proto dhcp metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.152 metric 100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=94.0/20211028161635 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.80 dmi.board.name: B550M/ac 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:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/22/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB550M/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1950533/+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 1950441] Re: HDMI monitor no life: VGA monitor life after hibernation
*** This bug is a duplicate of bug 1950425 *** https://bugs.launchpad.net/bugs/1950425 ** This bug has been marked a duplicate of bug 1950425 desktop non responsive after going into hibernation -- 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/1950441 Title: HDMI monitor no life: VGA monitor life after hibernation Status in xorg package in Ubuntu: New Bug description: I walked away from my dual monitor machine one monitor is old VGA one monitor is HDMI I returned to use machine machine = hibernation I moved the mouse VGA monitor works after hibernation HDMI monitor does [NOT update|blank screen|no signal] after hibernation I am experiencing lots of monitor issues with impish! video https://youtu.be/sjqyQn9EWp8 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 11:11:07 2021 DistUpgraded: 2021-10-19 08:03:15,745 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (2270 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 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.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=1 mtime.conffile..etc.default.apport: 2021-11-09T14:33:49.606944 version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 xserver.bootTime: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1950441/+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 1950461] Re: gnome-remote-desktop is not installed by default
** Summary changed: - Installing vino does not expose the screen sharing slider in Gnome Control Center + gnome-remote-desktop is not installed by default ** Tags removed: vino ** Tags added: impish ** Package changed: gnome-control-center (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Low -- 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/1950461 Title: gnome-remote-desktop is not installed by default Status in gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Ubuntu 21.10 - minimal install on a fresh machine apt install vino Open the gnome settings dialog and go to the Sharing tab. I would expect to see the screen sharing slider but it is not there. Searching around I found a suggestion to use Ubunutu with Xorg but this makes no difference. This behaviour is also present in 21.04. I have put gnome-control-center as the package at fault as this is ultimately where I observe the issue but it may be that during the install of vino makes the gnome configuration change and this step is missed. I have enquired on askubuntu and reddit but have not received a response so decided to report this gnome-control-center 1:40.0-1ubuntu5 is installed vino 3.22.0-6ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950461/+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 1950487] Re: screen flickering
Thanks for the bug report. Please: 1. Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0" 2. Run: sudo update-grub 3. Reboot. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - screen flickering + [Lenovo Y50-70] [i915] Screen flickering ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1950487 Title: [Lenovo Y50-70] [i915] Screen flickering Status in linux package in Ubuntu: Incomplete Bug description: The problem is, when i start working on my pc the screen start flickering goes from black to normal, it's a matter of graphic card(nvidia) but i failed to solve it, any suggestion: *-display UNCLAIMED description: 3D controller product: GM107M [GeForce GTX 960M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: memory:d000-d0ff memory:a000-afff memory:b000-b1ff ioport:4000(size=128) memory:b200-b207 *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: driver=i915 latency=0 resources: irq:37 memory:d100-d13f memory:c000-cfff ioport:5000(size=64) memory:c-d ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 17:14:48 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2021-11-10 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=eb605582-0819-4c08-a72a-63c9558e8612 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 3.43 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.ec.firmware.release: 3.43 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:br3.43:efr3.43:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70:skuLENOVO_MT_20378_BU_idea_FM_LenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.sku: LENOVO_MT_20378_BU_idea_FM_Lenovo Y50-70 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950487/+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 1950533] Re: Logging into Discord with DRM streaming in other Firefox tab breaks sound.
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1950533 Title: Logging into Discord with DRM streaming in other Firefox tab breaks sound. Status in firefox package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: What I expect to happen: seamless sound in multiple Firefox tabs What happens instead: While playing a certain youtube music stream with a clean browser history/cache: https://www.youtube.com/watch?v=5qap5aO4i9A I open another tab and log into Discord (in browser). As soon as I successfully log in, the sound from the youtube stream goes staticky and requires a pulseaudio -k (followed by a refresh of youtube) to remedy. $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy firefox firefox: Installed: 94.0+build3-0ubuntu0.20.04.1 Candidate: 94.0+build3-0ubuntu0.20.04.1 $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.12 Candidate: 1:13.99.1-1ubuntu3.12 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 94.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: username 36216 F pulseaudio /dev/snd/controlC2: username 36216 F pulseaudio /dev/snd/controlC0: username 36216 F pulseaudio BuildID: 20211028161635 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 20:15:31 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-11-11 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.1.1 dev enp3s0 proto dhcp metric 100 169.254.0.0/16 dev enp3s0 scope link metric 1000 192.168.1.0/24 dev enp3s0 proto kernel scope link src 192.168.1.152 metric 100 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:363 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=94.0/20211028161635 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P1.80 dmi.board.name: B550M/ac 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:bvnAmericanMegatrendsInternational,LLC.:bvrP1.80:bd04/22/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB550M/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1950533/+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 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10
If the crash returns then please: 1. Wait 10 seconds. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1950393 Title: GDM session crashes on suspend on Ubuntu 21.10 Status in gdm3 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: Since I started using kernel 5.13.0-20 (and 5.13.0-21) on Ubuntu 21.10, my GDM session crashes when I try to put my laptop to standby. I've attached a relevant slice of the system journal that starts from the moment I pressed the power button, configured to trigger suspend, in my case. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 00:47:13 2021 DistUpgraded: 2021-10-16 23:05:19,206 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2020-03-17 (602 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to impish on 2021-10-16 (24 days ago) dmi.bios.date: 08/09/2017 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1950393/+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 1950095] Re: [github] 20.04: Apt fails to download URLs with non-encoded querystrings
I installed apt from TJ's PPA, hopefully there are no regressions but it fixed the URL problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1950095 Title: [github] 20.04: Apt fails to download URLs with non-encoded querystrings Status in apt package in Ubuntu: Fix Released Bug description: I've just helped a group of Ubuntu 20.04 users with Microsoft Surface devices. They rely upon a github repository releases pocket as the apt archive. Those users recently hit a bug "Ubuntu: Apt update fails with Error 401 Unauthorized" [1] The initial simple Github URL gets a Location: redirect to a complex URL with un-escaped query-string. The resulting complex URL causes apt to fail to fetch the resource. $ sudo apt upgrade -y Err:1 https://pkg.surfacelinux.com/debian release/main amd64 libwacom-surface amd64 1.12-2 401 Unauthorized [IP: 185.199.110.133 443] The URL can be manually corrected. One of the Surface users provided this example: bad: https://objects.githubusercontent.com/github-production-release- asset-2e65be/139604852/86019e52-7bfa-4bc6-8cc1-52147027aee6?X-Amz- Algorithm=AWS4-HMAC-SHA256&X-Amz- Credential=AKIAIWNJYAX4CSVEH53A/20211105/us- east-1/s3/aws4_request&X-Amz-Date=20211105T161053Z&X-Amz- Expires=300&X-Amz- Signature=2bc0c28946db539ada250b1030c37249dae909d73a68c90b5e7bfe7fecd5d347&X-Amz- SignedHeaders=host&actor_id=0&key_id=0&repo_id=139604852&response- content-disposition=attachment; filename=libwacom- surface_1.12-2_amd64.deb&response-content-type=application/octet- stream good: https://objects.githubusercontent.com/github-production-release- asset-2e65be/139604852/86019e52-7bfa-4bc6-8cc1-52147027aee6?X-Amz- Algorithm=AWS4-HMAC-SHA256&X-Amz- Credential=AKIAIWNJYAX4CSVEH53A%2F20211105%2Fus- east-1%2Fs3%2Faws4_request&X-Amz-Date=20211105T160935Z&X-Amz- Expires=300&X-Amz- Signature=44d9307e66dfb5b3672ee0082b8801ad2532ac4b6be61c3442fb265ffce72852&X-Amz- SignedHeaders=host&actor_id=0&key_id=0&repo_id=139604852&response- content-disposition=attachment%3B%20filename%3Dlibwacom- surface_1.12-2_amd64.deb&response-content-type=application%2Foctet- stream I found this also affects a github repository I recently added for Zotero on 20.04. The problem is fixed in later versions of apt upstream, in Debian and Ubuntu releases. I cherry-picked the 4 commits [3] and provided a package for Focal in my PPA [2] which multiple users have reported (in [1]) solves the issue. It would be really good to get those patches included in 20.04 as an SRU. As the code is in later versions of apt and is focused on the URL encoding only it has minimal potential for causing regressions. [1] https://github.com/linux-surface/linux-surface/issues/625 [2] https://launchpad.net/~tj/+archive/ubuntu/bugfixes [3] https://salsa.debian.org/apt- team/apt/-/commit/06ec0067057e0578f3bc515f6a97d6a9d70824f6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1950095/+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 1950410] Re: PS4 DualShock wireless controller connected/disconnected/unusable
** Summary changed: - 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable + PS4 DualShock wireless controller connected/disconnected/unusable ** Changed in: ubuntu-mate Status: Incomplete => New ** Changed in: blueman (Ubuntu) Status: Incomplete => New ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1950410 Title: PS4 DualShock wireless controller connected/disconnected/unusable Status in Ubuntu MATE: New Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: New Bug description: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44
[Touch-packages] [Bug 413278]
When building the stack guard, it has been traditionally important to have the value start (in memory) with a zero byte to protect the guard value (and the rest of the stack past it) from being read via strcpy, etc. This patch reduces the number of random bytes by one, leaving the leading zero byte. https://www.kildarehousebuilders.ie -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/413278 Title: stack protector guard value does not lead with a NULL byte Status in GLibC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Invalid Status in eglibc source package in Jaunty: Invalid Status in glibc source package in Jaunty: Fix Released Status in eglibc source package in Karmic: Fix Released Status in glibc source package in Karmic: Invalid Bug description: IMPACT: stack protections are weakened due to strcpy function being able to write the stack guard (since it does not start with a zero byte). ADDRESSED: correctly implement leading zero, as done in Karmic. DISCUSSION: regression potential is low, since the patch is isolated and well tested. TEST CASE: $ bzr branch lp:~ubuntu-bugcontrol/qa-regression-testing/master qa-regression-testing $ cd qa-regression-testing/scripts $ ./test-glibc-security.py -v Build helper tools ... (9.10) ok glibc heap protection ... ok sprintf not pre-truncated with -D_FORTIFY_SOURCE=2 ... ok glibc pointer obfuscation ... ok Password hashes ... (sha512) ok Stack guard exists ... ok Stack guard leads with zero byte ... FAIL Stack guard is randomized ... ok == FAIL: Stack guard leads with zero byte -- Traceback (most recent call last): File "./test-glibc-security.py", line 170, in test_81_stack_guard_leads_zero self.assertEqual(one.startswith('00 '), expected, one) AssertionError: 62 55 59 69 cd 20 39 80 -- Ran 8 tests in 0.145s FAILED (failures=1) expected outcome: 0 failures. ProblemType: Bug Architecture: amd64 Date: Thu Aug 13 13:59:02 2009 Dependencies: findutils 4.4.2-1 gcc-4.4-base 4.4.1-1ubuntu3 libc6 2.10.1-0ubuntu6 libgcc1 1:4.4.1-1ubuntu3 DistroRelease: Ubuntu 9.10 Package: libc6 2.10.1-0ubuntu6 ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SourcePackage: eglibc Uname: Linux 2.6.31-5-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/413278/+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 1261211]
To be clear: this fix hasn't been all sunshine and rainbows. It seems that there's a randomly probability at bootup that some of the pins don't connect right and I only get L,R,RR or some weird variation of this. Sometimes power cycling the system eventually corrects this to get at least 5 of the 5.1 channels. The bass redirect seems to pass things to LFE, but LFE as a discrete channel doesn't really seem happen very often for some reason. And even weird, mythtv (using the ALSA support), I have to select surround50 as the device or the channels get mismapped. Running hdajackretask seems to _completely_ screw things up, so that's a no go. Maybe a kernel/ALSA dev can chime in and maybe have a rough idea of what's happening? I assume the powercycling reloads the firmware on the DSP, and something during that initialization kind of haphazardly maps pins. I've never booted this system into windows to know if that would have any real side effects. -- 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/1261211 Title: No multichannel support on Creative CA0132 Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Multichannel sound is not working on my Creative CA0132 sound card. Stereo is working just fine but I cannot get 5.1 to work. when I run 'speaker-test -c 6' sound only comes out of the front 2 speakers and if I add '-Dsurround51' it returns "Channels count (6) not available for playbacks: Invalid argument". My alsa info http://www.alsa- project.org/db/?f=3a5ca77035da6be08769128daa43dcbc59badb93 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: somedude 1605 F lxpanel somedude 4927 F firefox /dev/snd/pcmC0D0p: somedude 4927 F...m firefox /dev/snd/timer: somedude 4927 f firefox Date: Sun Dec 15 15:58:33 2013 InstallationDate: Installed on 2013-12-15 (0 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: Z87 Professional 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:bd07/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Professional: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. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1261211/+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 1950473] Re: SSH keygen, Key enrollment failed: requested feature not supported
I got an answer from yubikey support. It seems that my keys have firmware that is to old. To use residential keys you need to have a YubiKey with credential management, this was added in Firmware 5.2.3 This bug report can be closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1950473 Title: SSH keygen, Key enrollment failed: requested feature not supported Status in openssh package in Ubuntu: New Bug description: Bug report: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 21.10 Release: 21.10 Codename: impish uname -r 5.13.0-21-generic Yubikey device: yubikey 5 NFC ssh -V OpenSSH_8.4p1 Ubuntu-6ubuntu2, OpenSSL 1.1.1l 24 Aug 2021 Dmesg output: 21.960057] usb 1-3: new full-speed USB device number 4 using xhci_hcd [ 22.296859] usb 1-3: New USB device found, idVendor=1050, idProduct=0407, bcdDevice= 5.12 [ 22.296869] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 22.296873] usb 1-3: Product: YubiKey OTP+FIDO+CCID [ 22.296876] usb 1-3: Manufacturer: Yubico [ 22.296879] usb 1-3: SerialNumber: 0009031500 [ 22.331164] input: Yubico YubiKey OTP+FIDO+CCID as /devices/pci:00/:00:01.3/:02:00.0/usb1/1-3/1-3:1.0/0003:1050:0407.0004/input/input19 [ 22.388838] hid-generic 0003:1050:0407.0004: input,hidraw3: USB HID v1.10 Keyboard [Yubico YubiKey OTP+FIDO+CCID] on usb-:02:00.0-3/input0 [ 22.396252] hid-generic 0003:1050:0407.0005: hiddev2,hidraw4: USB HID v1.10 Device [Yubico YubiKey OTP+FIDO+CCID] on usb-:02:00.0-3/input1 lsusb -v 2>/dev/null | grep -A2 Yubico | grep "bcdDevice" | awk '{print $2}' 5.12 ( Yubikey firmware ) Tried with the key pin: ssh-keygen -t ed25519-sk -O resident -vvv Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: debug3: start_helper: started pid=2678 debug3: ssh_msg_send: type 5 debug3: ssh_msg_recv entering debug1: start_helper: starting /usr/lib/openssh/ssh-sk-helper debug1: sshsk_enroll: provider "internal", device "(null)", application "ssh:", userid "(null)", flags 0x21, challenge len 0 with-pin debug1: sshsk_enroll: using random challenge debug1: sk_probe: 1 device(s) detected debug1: sk_probe: selecting sk by touch debug1: ssh_sk_enroll: using device /dev/hidraw4 debug1: ssh_sk_enroll: /dev/hidraw4 does not support credprot, refusing to create unprotected resident/verify-required key debug1: sshsk_enroll: provider "internal" returned failure -2 debug1: ssh-sk-helper: Enrollment failed: requested feature not supported debug1: ssh-sk-helper: reply len 8 debug3: ssh_msg_send: type 5 debug1: client_converse: helper returned error -59 debug3: reap_helper: pid=2678 Key enrollment failed: requested feature not supported Tried with touching the key: $ ssh-keygen -t ed25519-sk -O resident -vvv Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: debug3: start_helper: started pid=2681 debug3: ssh_msg_send: type 5 debug3: ssh_msg_recv entering debug1: start_helper: starting /usr/lib/openssh/ssh-sk-helper debug1: sshsk_enroll: provider "internal", device "(null)", application "ssh:", userid "(null)", flags 0x21, challenge len 0 with-pin debug1: sshsk_enroll: using random challenge debug1: sk_probe: 1 device(s) detected debug1: sk_probe: selecting sk by touch debug1: ssh_sk_enroll: using device /dev/hidraw4 debug1: ssh_sk_enroll: /dev/hidraw4 does not support credprot, refusing to create unprotected resident/verify-required key debug1: sshsk_enroll: provider "internal" returned failure -2 debug1: ssh-sk-helper: Enrollment failed: requested feature not supported debug1: ssh-sk-helper: reply len 8 debug3: ssh_msg_send: type 5 debug1: client_converse: helper returned error -59 debug3: reap_helper: pid=2681 Key enrollment failed: requested feature not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1950473/+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 1950521] Re: testresources does not support python 3.10
This also affects python-launchpadlib python-testtools python-gear Which are currently blocked on jammy-proposed due to failures related to this bug. ** Also affects: python-launchpadlib (Ubuntu) Importance: Undecided Status: New ** Also affects: python-testtools (Ubuntu) Importance: Undecided Status: New ** Also affects: python-gear (Ubuntu) Importance: Undecided Status: New -- 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/1950521 Title: testresources does not support python 3.10 Status in python-gear package in Ubuntu: New Status in python-launchpadlib package in Ubuntu: New Status in python-testtools package in Ubuntu: New Status in testresources package in Ubuntu: New Bug description: testresources does not support Python 3.10. The package cannot be loaded due to an incompatibility in the package's __init__.py file, as shown in [1], which is a fix proposed upstream. [1] https://github.com/testing-cabal/testresources/pull/14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-gear/+bug/1950521/+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 1950473] Re: SSH keygen, Key enrollment failed: requested feature not supported
Correction ** Package changed: gnupg (Ubuntu) => openssh (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1950473 Title: SSH keygen, Key enrollment failed: requested feature not supported Status in openssh package in Ubuntu: New Bug description: Bug report: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 21.10 Release: 21.10 Codename: impish uname -r 5.13.0-21-generic Yubikey device: yubikey 5 NFC ssh -V OpenSSH_8.4p1 Ubuntu-6ubuntu2, OpenSSL 1.1.1l 24 Aug 2021 Dmesg output: 21.960057] usb 1-3: new full-speed USB device number 4 using xhci_hcd [ 22.296859] usb 1-3: New USB device found, idVendor=1050, idProduct=0407, bcdDevice= 5.12 [ 22.296869] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 22.296873] usb 1-3: Product: YubiKey OTP+FIDO+CCID [ 22.296876] usb 1-3: Manufacturer: Yubico [ 22.296879] usb 1-3: SerialNumber: 0009031500 [ 22.331164] input: Yubico YubiKey OTP+FIDO+CCID as /devices/pci:00/:00:01.3/:02:00.0/usb1/1-3/1-3:1.0/0003:1050:0407.0004/input/input19 [ 22.388838] hid-generic 0003:1050:0407.0004: input,hidraw3: USB HID v1.10 Keyboard [Yubico YubiKey OTP+FIDO+CCID] on usb-:02:00.0-3/input0 [ 22.396252] hid-generic 0003:1050:0407.0005: hiddev2,hidraw4: USB HID v1.10 Device [Yubico YubiKey OTP+FIDO+CCID] on usb-:02:00.0-3/input1 lsusb -v 2>/dev/null | grep -A2 Yubico | grep "bcdDevice" | awk '{print $2}' 5.12 ( Yubikey firmware ) Tried with the key pin: ssh-keygen -t ed25519-sk -O resident -vvv Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: debug3: start_helper: started pid=2678 debug3: ssh_msg_send: type 5 debug3: ssh_msg_recv entering debug1: start_helper: starting /usr/lib/openssh/ssh-sk-helper debug1: sshsk_enroll: provider "internal", device "(null)", application "ssh:", userid "(null)", flags 0x21, challenge len 0 with-pin debug1: sshsk_enroll: using random challenge debug1: sk_probe: 1 device(s) detected debug1: sk_probe: selecting sk by touch debug1: ssh_sk_enroll: using device /dev/hidraw4 debug1: ssh_sk_enroll: /dev/hidraw4 does not support credprot, refusing to create unprotected resident/verify-required key debug1: sshsk_enroll: provider "internal" returned failure -2 debug1: ssh-sk-helper: Enrollment failed: requested feature not supported debug1: ssh-sk-helper: reply len 8 debug3: ssh_msg_send: type 5 debug1: client_converse: helper returned error -59 debug3: reap_helper: pid=2678 Key enrollment failed: requested feature not supported Tried with touching the key: $ ssh-keygen -t ed25519-sk -O resident -vvv Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: debug3: start_helper: started pid=2681 debug3: ssh_msg_send: type 5 debug3: ssh_msg_recv entering debug1: start_helper: starting /usr/lib/openssh/ssh-sk-helper debug1: sshsk_enroll: provider "internal", device "(null)", application "ssh:", userid "(null)", flags 0x21, challenge len 0 with-pin debug1: sshsk_enroll: using random challenge debug1: sk_probe: 1 device(s) detected debug1: sk_probe: selecting sk by touch debug1: ssh_sk_enroll: using device /dev/hidraw4 debug1: ssh_sk_enroll: /dev/hidraw4 does not support credprot, refusing to create unprotected resident/verify-required key debug1: sshsk_enroll: provider "internal" returned failure -2 debug1: ssh-sk-helper: Enrollment failed: requested feature not supported debug1: ssh-sk-helper: reply len 8 debug3: ssh_msg_send: type 5 debug1: client_converse: helper returned error -59 debug3: reap_helper: pid=2681 Key enrollment failed: requested feature not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1950473/+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 1950410] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1950410/+attachment/5539763/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1950410 Title: 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable Status in Ubuntu MATE: Incomplete Status in blueman package in Ubuntu: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44 [ 2522.948593] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input42 [ 2522.95151
[Touch-packages] [Bug 1950410] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1950410/+attachment/5539764/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1950410 Title: 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable Status in Ubuntu MATE: Incomplete Status in blueman package in Ubuntu: Incomplete Status in bluez package in Ubuntu: Incomplete Bug description: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44 [ 2522.948593] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input42 [ 2522.951519] sony 0005:0
[Touch-packages] [Bug 1950410] Re: 21.10-Bad wireless(bluetooth) gamepad integration. Connected/Disconnected/unusable
apport information ** Tags added: apport-collected ** Description changed: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44 [ 2522.948593] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input42 [ 2522.951519] sony 0005:054C:09CC.0007: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 ``` - When I plug the same controller via USB it's not only automatically - recognized but I can also use the track mouse on the controller just - fine. + When I plug the same controller via USB it's not only automatically recognized but I can also use the track mouse on the controller just fine. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd6
[Touch-packages] [Bug 1921518] Re: OpenSSL "double free" error
** Tags added: fr-1852 -- 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/1921518 Title: OpenSSL "double free" error Status in openssl package in Ubuntu: Incomplete Status in openssl source package in Focal: Incomplete Bug description: "double free" error is seen when using curl utility. Error is from libcrypto.so which is part of the OpenSSL package. This happens only when OpenSSL is configured to use a dynamic engine. OpenSSL version is 1.1.1f The issue is not encountered if http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead. OpenSSL can be configured to use a dynamic engine by editing the default openssl config file which is located at '/etc/ssl/openssl.cnf' on Ubuntu systems. On Bluefield systems, config diff to enable PKA dynamic engine, is as below: +openssl_conf = conf_section + # Extra OBJECT IDENTIFIER info: #oid_file = $ENV::HOME/.oid oid_section= new_oids +[ conf_section ] +engines = engine_section + +[ engine_section ] +bf = bf_section + +[ bf_section ] +engine_id=pka +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so +init=0 + engine_id above refers to dynamic engine name/identifier. dynamic_path points to the .so file for the dynamic engine. # curl -O https://tpo.pe/pathogen.vim double free or corruption (out) Aborted (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518/+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 1950520] [NEW] systemd-resolved delivers SOA information when it should not
Public bug reported: I have a setup where a host (say A) in the network runs knot-resolver as a caching nameserver. Among the other hosts, some of them run ubuntu 20.04 and use systemd- resolved. The dhcp setup make all these host use A as their nameserver. The issue with systemd- The issue is that if I do: host -t SOA foo.local the hosts running systemd-resolved answer foo.local has SOA record foo.local. nobody.invalid. 1 3600 1200 604800 10800 making up the SOA record from nowhere (sort of). In fact, if I do the same query pointing directly at A host -t SOA foo.local I correctly get no SOA record. The incorrect response of resolved breaks mDNS resolution. In fact, if nsswitch.conf is set at hosts: files mdns4_minimal [NOTFOUND=return] dns any call requiring name resolution first goes through the hosts files, then mdns is attempted. However, the nss mdnd implementation first checks if the DNS server responds to SOA queries for the top level local name and if this is the case, it gives up. As a consequence, trying to access hosts on the .local domain always fail. The reason why systemd-resolved makes up a SOA record for hosts such as foo.local is that knot resolver replies to queries about it without an answer, but including an authority section ;; AUTHORITY SECTION: foo.local. 10800 IN SOA foo.local. nobody.invalid. 1 3600 1200 604800 10800 ;; ADDITIONAL SECTION: explanation.invalid.10800 IN TXT "Blocking is mandated by standards, see references on https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml"; and systemd-resolved turns that AUTHORITY section into a SOA record. It is not totally clear to me if the fault is on knot-resolver, systemd-resolved or both, but I tend to think it is the second one. Unfortunately, trying to inquire upstream about systemd-resolved appears to be forbidden for anybody not running the last two releases of systemd. Furthermore, I understand that the nature of systemd makes it extra hard or impossible to test a more recent version of systemd- resolved than the one shipped in ubuntu focal. Interestingly, the issue seems to bite those running omnia turris router too (see https://forum.turris.cz/t/avahi-local-domain-warning-on- ubuntu/13437). Maybe they use knot-resolver as their caching nameserver. ** 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/1950520 Title: systemd-resolved delivers SOA information when it should not Status in systemd package in Ubuntu: New Bug description: I have a setup where a host (say A) in the network runs knot-resolver as a caching nameserver. Among the other hosts, some of them run ubuntu 20.04 and use systemd- resolved. The dhcp setup make all these host use A as their nameserver. The issue with systemd- The issue is that if I do: host -t SOA foo.local the hosts running systemd-resolved answer foo.local has SOA record foo.local. nobody.invalid. 1 3600 1200 604800 10800 making up the SOA record from nowhere (sort of). In fact, if I do the same query pointing directly at A host -t SOA foo.local I correctly get no SOA record. The incorrect response of resolved breaks mDNS resolution. In fact, if nsswitch.conf is set at hosts: files mdns4_minimal [NOTFOUND=return] dns any call requiring name resolution first goes through the hosts files, then mdns is attempted. However, the nss mdnd implementation first checks if the DNS server responds to SOA queries for the top level local name and if this is the case, it gives up. As a consequence, trying to access hosts on the .local domain always fail. The reason why systemd-resolved makes up a SOA record for hosts such as foo.local is that knot resolver replies to queries about it without an answer, but including an authority section ;; AUTHORITY SECTION: foo.local. 10800 IN SOA foo.local. nobody.invalid. 1 3600 1200 604800 10800 ;; ADDITIONAL SECTION: explanation.invalid.10800 IN TXT "Blocking is mandated by standards, see references on https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml"; and systemd-resolved turns that AUTHORITY section into a SOA record. It is not totally clear to me if the fault is on knot-resolver, systemd-resolved or both, but I tend to think it is the second one. Unfortunately, trying to inquire upstream about systemd-resolved appears to be forbidden for anybody not running the last two releases of systemd. Furthermore, I understand that the nature of systemd makes it extra hard or impossible to test a more recent version of systemd-resolved than the one shipped in ubuntu focal. Intere
[Touch-packages] [Bug 1949778] Re: unittest2 doesn't work on python3.10
** Changed in: gitinspector (Ubuntu) Status: New => Fix Released ** Changed in: python-cloudkittyclient (Ubuntu) Status: New => Fix Released ** Changed in: python-cyborgclient (Ubuntu) Status: New => Fix Released ** Changed in: python-freezerclient (Ubuntu) Status: New => Fix Released ** Changed in: python-jenkins (Ubuntu) Status: New => Fix Released ** Changed in: python-pyghmi (Ubuntu) Status: New => Fix Released ** Changed in: python-pykmip (Ubuntu) Status: New => Fix Released ** Changed in: python-requests-mock (Ubuntu) Status: New => Fix Released ** Changed in: python-sphinx-feature-classification (Ubuntu) Status: New => Fix Released ** Changed in: python-sushy-cli (Ubuntu) Status: New => Fix Released ** Changed in: tempest (Ubuntu) Status: New => Fix Released -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in gitinspector package in Ubuntu: Fix Released Status in python-cloudkittyclient package in Ubuntu: Fix Released Status in python-cyborgclient package in Ubuntu: Fix Released Status in python-deprecation package in Ubuntu: Fix Released Status in python-freezerclient package in Ubuntu: Fix Released Status in python-futurist package in Ubuntu: Invalid Status in python-jenkins package in Ubuntu: Fix Released Status in python-launchpadlib package in Ubuntu: Invalid Status in python-pyghmi package in Ubuntu: Fix Released Status in python-pykmip package in Ubuntu: Fix Released Status in python-requests-mock package in Ubuntu: Fix Released Status in python-sphinx-feature-classification package in Ubuntu: Fix Released Status in python-sushy-cli package in Ubuntu: Fix Released Status in python-testtools package in Ubuntu: Invalid Status in python-tosca-parser package in Ubuntu: Fix Released Status in python-yaql package in Ubuntu: Fix Released Status in tempest package in Ubuntu: Fix Released Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: New Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitinspector/+bug/1949778/+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 1950511] [NEW] FTBFS due to meson disallowing + for bools
Public bug reported: FTBFS with new meson: ../meson.build:46:3: ERROR: Object <[BooleanHolder] holds [bool]: False> of type bool does not support the `+` operator. ** Affects: systemd (Ubuntu) Importance: High Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: systemd (Ubuntu Jammy) Importance: High Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Jammy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Jammy) Importance: Medium => High ** Changed in: systemd (Ubuntu Jammy) Status: New => In Progress -- 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/1950511 Title: FTBFS due to meson disallowing + for bools Status in systemd package in Ubuntu: In Progress Status in systemd source package in Jammy: In Progress Bug description: FTBFS with new meson: ../meson.build:46:3: ERROR: Object <[BooleanHolder] holds [bool]: False> of type bool does not support the `+` operator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950511/+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 1920836] Re: Show Extended Security Maintenence status
This bug was fixed in the package software-properties - 0.99.9.8 --- software-properties (0.99.9.8) focal; urgency=medium [ Corey Bryant ] * cloudarchive: Enable support for the Yoga Ubuntu Cloud Archive on 20.04 (LP: #1948806). [ Chad Smith ] * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status - Handle absent /var/lib/ubuntu-advantage/status.json for non-root users (LP: #1939732) - print unexcepted errors and if _schema_version not equal to 0.1 software-properties (0.99.9.7) focal; urgency=medium * Show Ubuntu Pro banner on Livepatch page (LP: #1934439) software-properties (0.99.9.6) focal; urgency=medium * Show ESM support status (LP: #1920836) -- Corey Bryant Tue, 26 Oct 2021 08:27:56 -0400 ** Changed in: software-properties (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Hirsute: Fix Released Status in software-properties source package in Impish: Fix Released Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+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 1934439] Re: Add Ubuntu Pro banner to Livepatch page
This bug was fixed in the package software-properties - 0.99.9.8 --- software-properties (0.99.9.8) focal; urgency=medium [ Corey Bryant ] * cloudarchive: Enable support for the Yoga Ubuntu Cloud Archive on 20.04 (LP: #1948806). [ Chad Smith ] * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status - Handle absent /var/lib/ubuntu-advantage/status.json for non-root users (LP: #1939732) - print unexcepted errors and if _schema_version not equal to 0.1 software-properties (0.99.9.7) focal; urgency=medium * Show Ubuntu Pro banner on Livepatch page (LP: #1934439) software-properties (0.99.9.6) focal; urgency=medium * Show ESM support status (LP: #1920836) -- Corey Bryant Tue, 26 Oct 2021 08:27:56 -0400 ** Changed in: software-properties (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Bug description: [Impact] Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. [Test Case] 1. Open Software Properties. 2. Go to Livepatch tab. Expected result: A banner is shown directing the user to Ubuntu Pro. The banner can be dismissed, and doesn't return when restarting software-properties. [Regression Potential] Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1934439] Update Released
The verification of the Stable Release Update for software-properties 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Bug description: [Impact] Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. [Test Case] 1. Open Software Properties. 2. Go to Livepatch tab. Expected result: A banner is shown directing the user to Ubuntu Pro. The banner can be dismissed, and doesn't return when restarting software-properties. [Regression Potential] Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1948806] Update Released
The verification of the Stable Release Update for software-properties 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1948806 Title: [SRU] Enable support for Yoga Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: Please add support for: cloud-archive:yoga cloud-archive:yoga-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the yoga cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:yoga sudo add-apt-repository cloud-archive:yoga-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1948806/+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 1939732] Re: report availability of Ubuntu Advantage ESM services on unattached machines
This bug was fixed in the package software-properties - 0.99.9.8 --- software-properties (0.99.9.8) focal; urgency=medium [ Corey Bryant ] * cloudarchive: Enable support for the Yoga Ubuntu Cloud Archive on 20.04 (LP: #1948806). [ Chad Smith ] * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status - Handle absent /var/lib/ubuntu-advantage/status.json for non-root users (LP: #1939732) - print unexcepted errors and if _schema_version not equal to 0.1 software-properties (0.99.9.7) focal; urgency=medium * Show Ubuntu Pro banner on Livepatch page (LP: #1934439) software-properties (0.99.9.6) focal; urgency=medium * Show ESM support status (LP: #1920836) -- Corey Bryant Tue, 26 Oct 2021 08:27:56 -0400 ** Changed in: software-properties (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1939732 Title: report availability of Ubuntu Advantage ESM services on unattached machines Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Hirsute: Fix Released Status in software-properties source package in Impish: Fix Released Bug description: [Impact] * Error messages emitted to software-properties-gtk console "[Errno 2] No such file or directory: '/var/lib/ubuntu-advantage/status.json'" due to incorrect expectation that status.json file is written when non-root runs `ua status` * This logic results in multiple `ua status` calls which each result in a network-egress to https://contracts.canonical.com on unattached machines which could result in delays in rendering the GTK dialogs while awaiting a response. [Test Case] 1. Install latest version of software-properties-gtk from -proposed cat > setup_proposed.sh
[Touch-packages] [Bug 1948806] Re: [SRU] Enable support for Yoga Cloud Archive
This bug was fixed in the package software-properties - 0.99.9.8 --- software-properties (0.99.9.8) focal; urgency=medium [ Corey Bryant ] * cloudarchive: Enable support for the Yoga Ubuntu Cloud Archive on 20.04 (LP: #1948806). [ Chad Smith ] * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status - Handle absent /var/lib/ubuntu-advantage/status.json for non-root users (LP: #1939732) - print unexcepted errors and if _schema_version not equal to 0.1 software-properties (0.99.9.7) focal; urgency=medium * Show Ubuntu Pro banner on Livepatch page (LP: #1934439) software-properties (0.99.9.6) focal; urgency=medium * Show ESM support status (LP: #1920836) -- Corey Bryant Tue, 26 Oct 2021 08:27:56 -0400 ** Changed in: software-properties (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1948806 Title: [SRU] Enable support for Yoga Cloud Archive Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Focal: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: Please add support for: cloud-archive:yoga cloud-archive:yoga-proposed This will also need to be SRU'd back to focal. [Impact] End users have to manually enable the yoga cloud archive pockets. [Test case] sudo add-apt-repository cloud-archive:yoga sudo add-apt-repository cloud-archive:yoga-proposed [Regression potential] Limited - just a data item addition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1948806/+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 1949778] Re: unittest2 doesn't work on python3.10
** Changed in: python-testtools (Ubuntu) Status: New => Invalid ** Changed in: python-futurist (Ubuntu) Status: New => Invalid -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in gitinspector package in Ubuntu: New Status in python-cloudkittyclient package in Ubuntu: New Status in python-cyborgclient package in Ubuntu: New Status in python-deprecation package in Ubuntu: Fix Released Status in python-freezerclient package in Ubuntu: New Status in python-futurist package in Ubuntu: Invalid Status in python-jenkins package in Ubuntu: New Status in python-launchpadlib package in Ubuntu: Invalid Status in python-pyghmi package in Ubuntu: New Status in python-pykmip package in Ubuntu: New Status in python-requests-mock package in Ubuntu: New Status in python-sphinx-feature-classification package in Ubuntu: New Status in python-sushy-cli package in Ubuntu: New Status in python-testtools package in Ubuntu: Invalid Status in python-tosca-parser package in Ubuntu: Fix Released Status in python-yaql package in Ubuntu: Fix Released Status in tempest package in Ubuntu: New Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: New Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitinspector/+bug/1949778/+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 1949778] Re: unittest2 doesn't work on python3.10
** Changed in: python-deprecation (Ubuntu) Status: New => Fix Released ** Changed in: python-tosca-parser (Ubuntu) Status: New => Fix Released ** Changed in: python-launchpadlib (Ubuntu) Status: New => Invalid ** Changed in: python-yaql (Ubuntu) Status: New => Fix Released -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in gitinspector package in Ubuntu: New Status in python-cloudkittyclient package in Ubuntu: New Status in python-cyborgclient package in Ubuntu: New Status in python-deprecation package in Ubuntu: Fix Released Status in python-freezerclient package in Ubuntu: New Status in python-futurist package in Ubuntu: Invalid Status in python-jenkins package in Ubuntu: New Status in python-launchpadlib package in Ubuntu: Invalid Status in python-pyghmi package in Ubuntu: New Status in python-pykmip package in Ubuntu: New Status in python-requests-mock package in Ubuntu: New Status in python-sphinx-feature-classification package in Ubuntu: New Status in python-sushy-cli package in Ubuntu: New Status in python-testtools package in Ubuntu: Invalid Status in python-tosca-parser package in Ubuntu: Fix Released Status in python-yaql package in Ubuntu: Fix Released Status in tempest package in Ubuntu: New Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: New Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitinspector/+bug/1949778/+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 1950508] Re: unified cgroup incorrectly used in container on host with legacy/hybrid cgroup
** Changed in: systemd (Ubuntu Jammy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Impish) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Jammy) Status: New => In Progress ** Changed in: systemd (Ubuntu Impish) Status: New => In Progress -- 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/1950508 Title: unified cgroup incorrectly used in container on host with legacy/hybrid cgroup Status in systemd package in Ubuntu: In Progress Status in systemd source package in Impish: In Progress Status in systemd source package in Jammy: In Progress Bug description: [impact] after systemd was changed to default to cgroupv2, any container started on a host that still uses legacy or hybrid cgroup mounts will result in a container that attempts to use unified cgroup but can't due to all the controllers being used as v1 in the host kernel. [test case] TBD [regression potential] container, or vm or bare metal, that incorrectly uses cgroupv1, or incorrect use of cgroupv2. [scope] needed only for i and later f and earlier default to cgroupv1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950508/+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 1920836] Update Released
The verification of the Stable Release Update for software-properties 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Released Status in software-properties source package in Impish: Fix Released Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+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 1920836] Re: Show Extended Security Maintenence status
This bug was fixed in the package software-properties - 0.99.10.2 --- software-properties (0.99.10.2) hirsute; urgency=medium * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status - Handle absent /var/lib/ubuntu-advantage/status.json for non-root users (LP: #1939732) - print unexcepted errors and if _schema_version not equal to 0.1 software-properties (0.99.10.1) hirsute; urgency=medium * Show ESM support status (LP: #1920836) -- Chad Smith Fri, 29 Oct 2021 16:35:58 -0600 ** Changed in: software-properties (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Released Status in software-properties source package in Impish: Fix Released Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+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 1920836] Re: Show Extended Security Maintenence status
** Changed in: software-properties (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1920836 Title: Show Extended Security Maintenence status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Released Status in software-properties source package in Impish: Fix Released Bug description: [Impact] There is not currently a graphical method of determining if a system is subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) updates. This is resolved by adding some [new UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to the software properties application. [Test Case] 1. Install latest version of Ubuntu advantage: $ sudo add-apt-repository ppa:ua-client/stable $ sudo apt update $ sudo apt upgrade 2. Open Software Properties 3. Go to Updates tab. Expected result: Information is shown that indicates if this system is using Extended Security Maintenance updates, when updates will supported until, and a link to upgrade to ESM. Observed result: No ESM information currently shown. [Where problems could occur] - Software properties could hit a bug getting a response from the ua app. The current code carefully checks if and what is returned, falling back to a safe default behavior. - Launching software properties could trigger a bug in the ua app. - Software properties could show incorrect information, causing confusion for the user. The solution uses information from distro-info and the ua app which means software-properties contains no data about ESM, and instead relies on these apps that can be updated if things change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+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 1939732] Re: report availability of Ubuntu Advantage ESM services on unattached machines
This bug was fixed in the package software-properties - 0.99.10.2 --- software-properties (0.99.10.2) hirsute; urgency=medium * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status - Handle absent /var/lib/ubuntu-advantage/status.json for non-root users (LP: #1939732) - print unexcepted errors and if _schema_version not equal to 0.1 software-properties (0.99.10.1) hirsute; urgency=medium * Show ESM support status (LP: #1920836) -- Chad Smith Fri, 29 Oct 2021 16:35:58 -0600 ** Changed in: software-properties (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1939732 Title: report availability of Ubuntu Advantage ESM services on unattached machines Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Released Status in software-properties source package in Impish: Fix Released Bug description: [Impact] * Error messages emitted to software-properties-gtk console "[Errno 2] No such file or directory: '/var/lib/ubuntu-advantage/status.json'" due to incorrect expectation that status.json file is written when non-root runs `ua status` * This logic results in multiple `ua status` calls which each result in a network-egress to https://contracts.canonical.com on unattached machines which could result in delays in rendering the GTK dialogs while awaiting a response. [Test Case] 1. Install latest version of software-properties-gtk from -proposed cat > setup_proposed.sh
[Touch-packages] [Bug 1949778] Re: unittest2 doesn't work on python3.10
https://launchpad.net/ubuntu/+source/gitinspector/0.4.4+dfsg-10/+build/22296141 https://launchpad.net/ubuntu/+source/python-cloudkittyclient/4.3.0-2/+build/22303522 https://launchpad.net/ubuntu/+source/python-cyborgclient/1.5.0-2/+build/22303555 https://launchpad.net/ubuntu/+source/python-freezerclient/4.3.0-2/+build/22303691 https://launchpad.net/ubuntu/+source/python-jenkins/1.4.0-1/+build/22303764 https://launchpad.net/ubuntu/+source/python-pyghmi/1.5.29-2/+build/22303960 https://launchpad.net/ubuntu/+source/python-pykmip/0.10.0-4/+build/22341447 https://launchpad.net/ubuntu/+source/python-requests-mock/1.9.3-2/+build/22304041 https://launchpad.net/ubuntu/+source/python-sphinx-feature-classification/1.1.0-2/+build/22304079 https://launchpad.net/ubuntu/+source/python-sushy-cli/0.4.0-2/+build/22304092 https://launchpad.net/ubuntu/+source/tempest/1:29.0.0-2/+build/22310856 -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in gitinspector package in Ubuntu: New Status in python-cloudkittyclient package in Ubuntu: New Status in python-cyborgclient package in Ubuntu: New Status in python-deprecation package in Ubuntu: Fix Released Status in python-freezerclient package in Ubuntu: New Status in python-futurist package in Ubuntu: New Status in python-jenkins package in Ubuntu: New Status in python-launchpadlib package in Ubuntu: Invalid Status in python-pyghmi package in Ubuntu: New Status in python-pykmip package in Ubuntu: New Status in python-requests-mock package in Ubuntu: New Status in python-sphinx-feature-classification package in Ubuntu: New Status in python-sushy-cli package in Ubuntu: New Status in python-testtools package in Ubuntu: New Status in python-tosca-parser package in Ubuntu: Fix Released Status in python-yaql package in Ubuntu: New Status in tempest package in Ubuntu: New Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: New Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitinspector/+bug/1949778/+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 1939732] Update Released
The verification of the Stable Release Update for software-properties 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 software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1939732 Title: report availability of Ubuntu Advantage ESM services on unattached machines Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Released Status in software-properties source package in Impish: Fix Released Bug description: [Impact] * Error messages emitted to software-properties-gtk console "[Errno 2] No such file or directory: '/var/lib/ubuntu-advantage/status.json'" due to incorrect expectation that status.json file is written when non-root runs `ua status` * This logic results in multiple `ua status` calls which each result in a network-egress to https://contracts.canonical.com on unattached machines which could result in delays in rendering the GTK dialogs while awaiting a response. [Test Case] 1. Install latest version of software-properties-gtk from -proposed cat > setup_proposed.sh
[Touch-packages] [Bug 1939732] Re: report availability of Ubuntu Advantage ESM services on unattached machines
This bug was fixed in the package software-properties - 0.99.13.1 --- software-properties (0.99.13.1) impish; urgency=medium * utils: prefer /var/lib/ubuntu-advantage/status.json over ua status - Handle absent /var/lib/ubuntu-advantage/status.json for non-root users (LP: #1939732) - print unexcepted errors and if _schema_version not equal to 0.1 -- Chad Smith Mon, 01 Nov 2021 11:42:27 -0600 ** Changed in: software-properties (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1939732 Title: report availability of Ubuntu Advantage ESM services on unattached machines Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Released Status in software-properties source package in Impish: Fix Released Bug description: [Impact] * Error messages emitted to software-properties-gtk console "[Errno 2] No such file or directory: '/var/lib/ubuntu-advantage/status.json'" due to incorrect expectation that status.json file is written when non-root runs `ua status` * This logic results in multiple `ua status` calls which each result in a network-egress to https://contracts.canonical.com on unattached machines which could result in delays in rendering the GTK dialogs while awaiting a response. [Test Case] 1. Install latest version of software-properties-gtk from -proposed cat > setup_proposed.sh
[Touch-packages] [Bug 1950508] [NEW] unified cgroup incorrectly used in container on host with legacy/hybrid cgroup
Public bug reported: [impact] after systemd was changed to default to cgroupv2, any container started on a host that still uses legacy or hybrid cgroup mounts will result in a container that attempts to use unified cgroup but can't due to all the controllers being used as v1 in the host kernel. [test case] TBD [regression potential] container, or vm or bare metal, that incorrectly uses cgroupv1, or incorrect use of cgroupv2. [scope] needed only for i and later f and earlier default to cgroupv1 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Impish) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Impish) 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/1950508 Title: unified cgroup incorrectly used in container on host with legacy/hybrid cgroup Status in systemd package in Ubuntu: New Status in systemd source package in Impish: New Status in systemd source package in Jammy: New Bug description: [impact] after systemd was changed to default to cgroupv2, any container started on a host that still uses legacy or hybrid cgroup mounts will result in a container that attempts to use unified cgroup but can't due to all the controllers being used as v1 in the host kernel. [test case] TBD [regression potential] container, or vm or bare metal, that incorrectly uses cgroupv1, or incorrect use of cgroupv2. [scope] needed only for i and later f and earlier default to cgroupv1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950508/+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 1933117] Update Released
The verification of the Stable Release Update for ufw 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 ufw in Ubuntu. https://bugs.launchpad.net/bugs/1933117 Title: ufw delete can confuse protocol-specific rule with otherwise matching 'proto any' rule Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Bug description: [Impact] * The deletion of a rule without the 'proto' field that has a similar rule *with* the 'proto' field might delete the wrong rule (the latter). * This might cause services to be inaccessible or incorrectly allowed, depending on rule ordering (read original description below for examples.) [Test Steps] * Add rules: ufw allow from 1.1.1.1 port proto tcp ufw allow from 2.2.2.2 port proto tcp ufw allow from 1.1.1.1 port * Check iptables: iptables -L ufw-user-input -n ... ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT udp -- 1.1.1.1 0.0.0.0/0 udp spt: * Delete the third rule above ufw status numbered yes | ufw delete 3 * Check iptables again: iptables -L ufw-user-input -n Observed: (deleted tcp line from first rule, and udp line from third rule) ... ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: Expected: (deleted both tcp and udp lines from third rule) ... ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: [Regression Potential] * Potential regressions would be observed when deleting rules. * This fix has been suggested for SRU by jdstrand [1], and has already been available in 21.04 and the snap. [1] https://code.launchpad.net/~mfo/ufw/+git/ufw/+merge/410091/comments/1083005 [Original Description] UFW versions 0.35 (on Ubuntu 16.04 LTS) and 0.36 (on Ubuntu 20.04 LTS) If a rule is inserted without specifying the protocol, it will default to both udp and tcp. If a second rule is inserted earlier in the order that specifies the protocol but is otherwise identical, UFW will delete the wrong rule if the first rule is deleted. This is repeatable with the following script: ufw insert 1 allow from 1.1.1.1/26 to any port 22 ufw insert 2 allow from 1.2.3.4/26 to any port 22 ufw insert 1 allow from 1.2.3.4/26 to any port 22 proto tcp iptables -L -n | grep -A 6 "Chain ufw-user-input" yes | ufw delete 3 iptables -L -n | grep -A 4 "Chain ufw-user-input" The output is as follows: Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 ACCEPT tcp -- 1.1.1.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.1.1.0/26 0.0.0.0/0udp dpt:22 ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.2.3.0/26 0.0.0.0/0udp dpt:22 Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- 1.1.1.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.1.1.0/26 0.0.0.0/0udp dpt:22 ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 UFW deleted the first rule for 1.2.3.0 and then the last rule for 1.2.3.0, leaving the wrong rule remaining. Here is the ufw status: To Action From -- -- 22/tcp ALLOW 1.2.3.0/26 22 ALLOW 1.1.1.0/26 Mixing ALLOW and REJECT/DENY rules can further result in incorrect behavior due to this incorrect reordering. On port 22, this could render SSH remotely inaccessible. For example, if one had initially set up the following rule to port 22 (TCP and UDP)... ufw insert 1 allow from 1.2.3.4 to any port 22 ...and later wanted to further restrict it to only TCP, while explicitly rejecting any other port 22 connections... ufw insert 1 allow from 1.2.3.4 to any port 22 proto tcp ufw i
[Touch-packages] [Bug 1946804] Re: ufw breaks boot on network root filesystem
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.04.2 --- ufw (0.36-0ubuntu0.18.04.2) bionic; urgency=medium * d/p/0002-set-default-policy-after-load.patch: fix boot stall on iscsi/network root filesystem when starting ufw (LP: #1946804) * d/p/0003-unconditionally-reload-with-delete.patch: fix corner case of rule deletion with specific/any proto (LP: #1933117) -- Mauricio Faria de Oliveira Mon, 25 Oct 2021 14:30:24 -0300 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1946804 Title: ufw breaks boot on network root filesystem Status in ufw: Fix Committed Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Status in ufw source package in Impish: Fix Released Bug description: [Impact] A system with rootfs on iSCSI stops booting when ufw.service starts. The kernel logs iSCSI command/reset timeout until I/O fails and the root filesystem/journal break. The issue is that ufw_start() sets the default policy _first_, then adds rules _later_. So, a default INPUT policy of DROP (default setting in ufw) prevents further access to the root filesystem (blocks incoming iSCSI traffic) thus any rules that could help are not loaded (nor anything else.) [Fix] The fix is to set default policy after loading rules in ufw_start(). That seems to be OK as `ip[6]tables-restore -n/--noflush` is used, and per iptables source, that only sets the chain policy. This allows the system to boot due to the RELATED,ESTABLISHED rule, that is introduced by before.rules in INPUT/ufw-before-input chain. The comparison of `iptables -L` before/after shows no differences (verified on a local rootfs); `run_tests.sh` has 0 skipped/errors. [Test Steps] * Install Ubuntu on an iSCSI (or other network-based) root filesystem. (eg, Oracle Cloud's bare-metal 'BM.Standard1.36' shape.) * sudo ufw enable * Observed: system may stall immediately if no prior iptables rules. (eg, iptables -A INPUT -p tcp -s 169.254.0.2 --sport 3260 -j ACCEPT) * Expected: system continues working. * sudo reboot * Observed: system boot stalls once ufw.service starts (see below.) * Expected: system boot should move on. [Regression Potential] * Potential regressions would be observed on ufw start/reload, when iptables rules are configured. * The resulting iptables configuration has been compared before/after the change, with identical rules on both. [Other Info] * Fixed in Debian and Jammy. [ufw info] # ufw --version ufw 0.36 Copyright 2008-2015 Canonical Ltd. # lsb_release -cs focal [Boot Log] [ 232.168355] iBFT detected. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Setting up software interface enp45s0f0np0 ... [ 254.644505] Loading iSCSI transport class v2.0-870. [ 254.714938] iscsi: registered transport (tcp) [ 254.780129] scsi host12: iSCSI Initiator over TCP/IP ... [ 255.433491] sd 12:0:0:1: [sda] 251658240 512-byte logical blocks: (129 GB/120 GiB) ... [ 256.379550] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) ... [ 266.620860] systemd[1]: Starting Uncomplicated firewall... Starting Uncomplicated firewall... ... [ 298.491560] session1: iscsi_eh_cmd_timed_out scsi cmd 310a6696 timedout [ 298.580803] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.656262] session1: iscsi_eh_cmd_timed_out scsi cmd 94ad9246 timedout [ 298.745237] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.745270] session1: iscsi_eh_abort aborting sc 310a6696 [ 298.899644] session1: iscsi_eh_abort aborting [sc 310a6696 itt 0x13] [ 298.985788] session1: iscsi_exec_task_mgmt_fn tmf set timeout [ 302.075554] session1: iscsi_eh_cmd_timed_out scsi cmd 1a9458b5 timedout [ 302.164786] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 314.107541] session1: iscsi_tmf_timedout tmf timedout [ 314.169797] connection1:0: detected conn error (1021) [ 314.232266] session1: iscsi_eh_abort abort failed [sc 310a6696 itt 0x13] [ 314.323531] session1: iscsi_eh_abort aborting sc 94ad9246 [ 314.399640] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.495578] session1: iscsi_eh_abort aborting sc 1a9458b5 [ 314.571554] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.664050] session1: iscsi_eh_device_reset LU Reset [sc 310a6696 lun 1] [ 314.755773] session1: iscsi_eh_device_reset dev reset result = FAILED [ 314.834736] session1: iscsi_eh_target_rese
[Touch-packages] [Bug 1933117] Re: ufw delete can confuse protocol-specific rule with otherwise matching 'proto any' rule
This bug was fixed in the package ufw - 0.36-7.1ubuntu1 --- ufw (0.36-7.1ubuntu1) hirsute; urgency=medium * d/p/0015-set-default-policy-after-load.patch: fix boot stall on iscsi/network root filesystem when starting ufw (LP: #1946804) * d/p/0016-unconditionally-reload-with-delete.patch: fix corner case of rule deletion with specific/any proto (LP: #1933117) -- Mauricio Faria de Oliveira Mon, 25 Oct 2021 17:58:58 -0300 ** Changed in: ufw (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1933117 Title: ufw delete can confuse protocol-specific rule with otherwise matching 'proto any' rule Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Bug description: [Impact] * The deletion of a rule without the 'proto' field that has a similar rule *with* the 'proto' field might delete the wrong rule (the latter). * This might cause services to be inaccessible or incorrectly allowed, depending on rule ordering (read original description below for examples.) [Test Steps] * Add rules: ufw allow from 1.1.1.1 port proto tcp ufw allow from 2.2.2.2 port proto tcp ufw allow from 1.1.1.1 port * Check iptables: iptables -L ufw-user-input -n ... ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT udp -- 1.1.1.1 0.0.0.0/0 udp spt: * Delete the third rule above ufw status numbered yes | ufw delete 3 * Check iptables again: iptables -L ufw-user-input -n Observed: (deleted tcp line from first rule, and udp line from third rule) ... ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: Expected: (deleted both tcp and udp lines from third rule) ... ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: [Regression Potential] * Potential regressions would be observed when deleting rules. * This fix has been suggested for SRU by jdstrand [1], and has already been available in 21.04 and the snap. [1] https://code.launchpad.net/~mfo/ufw/+git/ufw/+merge/410091/comments/1083005 [Original Description] UFW versions 0.35 (on Ubuntu 16.04 LTS) and 0.36 (on Ubuntu 20.04 LTS) If a rule is inserted without specifying the protocol, it will default to both udp and tcp. If a second rule is inserted earlier in the order that specifies the protocol but is otherwise identical, UFW will delete the wrong rule if the first rule is deleted. This is repeatable with the following script: ufw insert 1 allow from 1.1.1.1/26 to any port 22 ufw insert 2 allow from 1.2.3.4/26 to any port 22 ufw insert 1 allow from 1.2.3.4/26 to any port 22 proto tcp iptables -L -n | grep -A 6 "Chain ufw-user-input" yes | ufw delete 3 iptables -L -n | grep -A 4 "Chain ufw-user-input" The output is as follows: Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 ACCEPT tcp -- 1.1.1.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.1.1.0/26 0.0.0.0/0udp dpt:22 ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.2.3.0/26 0.0.0.0/0udp dpt:22 Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- 1.1.1.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.1.1.0/26 0.0.0.0/0udp dpt:22 ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 UFW deleted the first rule for 1.2.3.0 and then the last rule for 1.2.3.0, leaving the wrong rule remaining. Here is the ufw status: To Action From -- -- 22/tcp ALLOW 1.2.3.0/26 22 ALLOW 1.1.1.0/26 Mixing ALLOW and REJECT/DENY rules can further result in incorrect behavior due to this incorrect reordering. On port 22, this could render SSH remotely inaccessible. For example, if one had initially set up the following rule to port 22 (TCP and UDP)... ufw insert 1 allow from 1.2.3.4 to any port 22 ...and later wanted to further restrict it to only TCP, while explicitly rejecting any other port 22 connect
[Touch-packages] [Bug 1933117] Re: ufw delete can confuse protocol-specific rule with otherwise matching 'proto any' rule
This bug was fixed in the package ufw - 0.36-6ubuntu1 --- ufw (0.36-6ubuntu1) focal; urgency=medium * d/p/0012-set-default-policy-after-load.patch: fix boot stall on iscsi/network root filesystem when starting ufw (LP: #1946804) * d/p/0013-unconditionally-reload-with-delete.patch: fix corner case of rule deletion with specific/any proto (LP: #1933117) -- Mauricio Faria de Oliveira Mon, 25 Oct 2021 14:30:14 -0300 ** Changed in: ufw (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: ufw (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 ufw in Ubuntu. https://bugs.launchpad.net/bugs/1933117 Title: ufw delete can confuse protocol-specific rule with otherwise matching 'proto any' rule Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Bug description: [Impact] * The deletion of a rule without the 'proto' field that has a similar rule *with* the 'proto' field might delete the wrong rule (the latter). * This might cause services to be inaccessible or incorrectly allowed, depending on rule ordering (read original description below for examples.) [Test Steps] * Add rules: ufw allow from 1.1.1.1 port proto tcp ufw allow from 2.2.2.2 port proto tcp ufw allow from 1.1.1.1 port * Check iptables: iptables -L ufw-user-input -n ... ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT udp -- 1.1.1.1 0.0.0.0/0 udp spt: * Delete the third rule above ufw status numbered yes | ufw delete 3 * Check iptables again: iptables -L ufw-user-input -n Observed: (deleted tcp line from first rule, and udp line from third rule) ... ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: Expected: (deleted both tcp and udp lines from third rule) ... ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: [Regression Potential] * Potential regressions would be observed when deleting rules. * This fix has been suggested for SRU by jdstrand [1], and has already been available in 21.04 and the snap. [1] https://code.launchpad.net/~mfo/ufw/+git/ufw/+merge/410091/comments/1083005 [Original Description] UFW versions 0.35 (on Ubuntu 16.04 LTS) and 0.36 (on Ubuntu 20.04 LTS) If a rule is inserted without specifying the protocol, it will default to both udp and tcp. If a second rule is inserted earlier in the order that specifies the protocol but is otherwise identical, UFW will delete the wrong rule if the first rule is deleted. This is repeatable with the following script: ufw insert 1 allow from 1.1.1.1/26 to any port 22 ufw insert 2 allow from 1.2.3.4/26 to any port 22 ufw insert 1 allow from 1.2.3.4/26 to any port 22 proto tcp iptables -L -n | grep -A 6 "Chain ufw-user-input" yes | ufw delete 3 iptables -L -n | grep -A 4 "Chain ufw-user-input" The output is as follows: Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 ACCEPT tcp -- 1.1.1.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.1.1.0/26 0.0.0.0/0udp dpt:22 ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.2.3.0/26 0.0.0.0/0udp dpt:22 Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- 1.1.1.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.1.1.0/26 0.0.0.0/0udp dpt:22 ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 UFW deleted the first rule for 1.2.3.0 and then the last rule for 1.2.3.0, leaving the wrong rule remaining. Here is the ufw status: To Action From -- -- 22/tcp ALLOW 1.2.3.0/26 22 ALLOW 1.1.1.0/26 Mixing ALLOW and REJECT/DENY rules can further result in incorrect behavior due to this incorrect reordering. On port 22, this could render SSH remotely inaccessible. For example, if one had initially set up the following rule to port 22 (TCP and UDP)... ufw insert 1 allow from 1.2.3.4 to any port 22 ...and later wanted to further restri
[Touch-packages] [Bug 1946804] Re: ufw breaks boot on network root filesystem
This bug was fixed in the package ufw - 0.36-7.1ubuntu1 --- ufw (0.36-7.1ubuntu1) hirsute; urgency=medium * d/p/0015-set-default-policy-after-load.patch: fix boot stall on iscsi/network root filesystem when starting ufw (LP: #1946804) * d/p/0016-unconditionally-reload-with-delete.patch: fix corner case of rule deletion with specific/any proto (LP: #1933117) -- Mauricio Faria de Oliveira Mon, 25 Oct 2021 17:58:58 -0300 ** Changed in: ufw (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: ufw (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1946804 Title: ufw breaks boot on network root filesystem Status in ufw: Fix Committed Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Status in ufw source package in Impish: Fix Released Bug description: [Impact] A system with rootfs on iSCSI stops booting when ufw.service starts. The kernel logs iSCSI command/reset timeout until I/O fails and the root filesystem/journal break. The issue is that ufw_start() sets the default policy _first_, then adds rules _later_. So, a default INPUT policy of DROP (default setting in ufw) prevents further access to the root filesystem (blocks incoming iSCSI traffic) thus any rules that could help are not loaded (nor anything else.) [Fix] The fix is to set default policy after loading rules in ufw_start(). That seems to be OK as `ip[6]tables-restore -n/--noflush` is used, and per iptables source, that only sets the chain policy. This allows the system to boot due to the RELATED,ESTABLISHED rule, that is introduced by before.rules in INPUT/ufw-before-input chain. The comparison of `iptables -L` before/after shows no differences (verified on a local rootfs); `run_tests.sh` has 0 skipped/errors. [Test Steps] * Install Ubuntu on an iSCSI (or other network-based) root filesystem. (eg, Oracle Cloud's bare-metal 'BM.Standard1.36' shape.) * sudo ufw enable * Observed: system may stall immediately if no prior iptables rules. (eg, iptables -A INPUT -p tcp -s 169.254.0.2 --sport 3260 -j ACCEPT) * Expected: system continues working. * sudo reboot * Observed: system boot stalls once ufw.service starts (see below.) * Expected: system boot should move on. [Regression Potential] * Potential regressions would be observed on ufw start/reload, when iptables rules are configured. * The resulting iptables configuration has been compared before/after the change, with identical rules on both. [Other Info] * Fixed in Debian and Jammy. [ufw info] # ufw --version ufw 0.36 Copyright 2008-2015 Canonical Ltd. # lsb_release -cs focal [Boot Log] [ 232.168355] iBFT detected. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Setting up software interface enp45s0f0np0 ... [ 254.644505] Loading iSCSI transport class v2.0-870. [ 254.714938] iscsi: registered transport (tcp) [ 254.780129] scsi host12: iSCSI Initiator over TCP/IP ... [ 255.433491] sd 12:0:0:1: [sda] 251658240 512-byte logical blocks: (129 GB/120 GiB) ... [ 256.379550] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) ... [ 266.620860] systemd[1]: Starting Uncomplicated firewall... Starting Uncomplicated firewall... ... [ 298.491560] session1: iscsi_eh_cmd_timed_out scsi cmd 310a6696 timedout [ 298.580803] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.656262] session1: iscsi_eh_cmd_timed_out scsi cmd 94ad9246 timedout [ 298.745237] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.745270] session1: iscsi_eh_abort aborting sc 310a6696 [ 298.899644] session1: iscsi_eh_abort aborting [sc 310a6696 itt 0x13] [ 298.985788] session1: iscsi_exec_task_mgmt_fn tmf set timeout [ 302.075554] session1: iscsi_eh_cmd_timed_out scsi cmd 1a9458b5 timedout [ 302.164786] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 314.107541] session1: iscsi_tmf_timedout tmf timedout [ 314.169797] connection1:0: detected conn error (1021) [ 314.232266] session1: iscsi_eh_abort abort failed [sc 310a6696 itt 0x13] [ 314.323531] session1: iscsi_eh_abort aborting sc 94ad9246 [ 314.399640] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.495578] session1: iscsi_eh_abort aborting sc 1a9458b5 [ 314.571554] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.664050] session1: iscsi_eh_device_reset LU Rese
[Touch-packages] [Bug 1946804] Re: ufw breaks boot on network root filesystem
This bug was fixed in the package ufw - 0.36-6ubuntu1 --- ufw (0.36-6ubuntu1) focal; urgency=medium * d/p/0012-set-default-policy-after-load.patch: fix boot stall on iscsi/network root filesystem when starting ufw (LP: #1946804) * d/p/0013-unconditionally-reload-with-delete.patch: fix corner case of rule deletion with specific/any proto (LP: #1933117) -- Mauricio Faria de Oliveira Mon, 25 Oct 2021 14:30:14 -0300 ** Changed in: ufw (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 ufw in Ubuntu. https://bugs.launchpad.net/bugs/1946804 Title: ufw breaks boot on network root filesystem Status in ufw: Fix Committed Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Status in ufw source package in Impish: Fix Released Bug description: [Impact] A system with rootfs on iSCSI stops booting when ufw.service starts. The kernel logs iSCSI command/reset timeout until I/O fails and the root filesystem/journal break. The issue is that ufw_start() sets the default policy _first_, then adds rules _later_. So, a default INPUT policy of DROP (default setting in ufw) prevents further access to the root filesystem (blocks incoming iSCSI traffic) thus any rules that could help are not loaded (nor anything else.) [Fix] The fix is to set default policy after loading rules in ufw_start(). That seems to be OK as `ip[6]tables-restore -n/--noflush` is used, and per iptables source, that only sets the chain policy. This allows the system to boot due to the RELATED,ESTABLISHED rule, that is introduced by before.rules in INPUT/ufw-before-input chain. The comparison of `iptables -L` before/after shows no differences (verified on a local rootfs); `run_tests.sh` has 0 skipped/errors. [Test Steps] * Install Ubuntu on an iSCSI (or other network-based) root filesystem. (eg, Oracle Cloud's bare-metal 'BM.Standard1.36' shape.) * sudo ufw enable * Observed: system may stall immediately if no prior iptables rules. (eg, iptables -A INPUT -p tcp -s 169.254.0.2 --sport 3260 -j ACCEPT) * Expected: system continues working. * sudo reboot * Observed: system boot stalls once ufw.service starts (see below.) * Expected: system boot should move on. [Regression Potential] * Potential regressions would be observed on ufw start/reload, when iptables rules are configured. * The resulting iptables configuration has been compared before/after the change, with identical rules on both. [Other Info] * Fixed in Debian and Jammy. [ufw info] # ufw --version ufw 0.36 Copyright 2008-2015 Canonical Ltd. # lsb_release -cs focal [Boot Log] [ 232.168355] iBFT detected. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Setting up software interface enp45s0f0np0 ... [ 254.644505] Loading iSCSI transport class v2.0-870. [ 254.714938] iscsi: registered transport (tcp) [ 254.780129] scsi host12: iSCSI Initiator over TCP/IP ... [ 255.433491] sd 12:0:0:1: [sda] 251658240 512-byte logical blocks: (129 GB/120 GiB) ... [ 256.379550] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) ... [ 266.620860] systemd[1]: Starting Uncomplicated firewall... Starting Uncomplicated firewall... ... [ 298.491560] session1: iscsi_eh_cmd_timed_out scsi cmd 310a6696 timedout [ 298.580803] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.656262] session1: iscsi_eh_cmd_timed_out scsi cmd 94ad9246 timedout [ 298.745237] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.745270] session1: iscsi_eh_abort aborting sc 310a6696 [ 298.899644] session1: iscsi_eh_abort aborting [sc 310a6696 itt 0x13] [ 298.985788] session1: iscsi_exec_task_mgmt_fn tmf set timeout [ 302.075554] session1: iscsi_eh_cmd_timed_out scsi cmd 1a9458b5 timedout [ 302.164786] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 314.107541] session1: iscsi_tmf_timedout tmf timedout [ 314.169797] connection1:0: detected conn error (1021) [ 314.232266] session1: iscsi_eh_abort abort failed [sc 310a6696 itt 0x13] [ 314.323531] session1: iscsi_eh_abort aborting sc 94ad9246 [ 314.399640] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.495578] session1: iscsi_eh_abort aborting sc 1a9458b5 [ 314.571554] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.664050] session1: iscsi_eh_device_reset LU Reset [sc 310a6696 lun 1] [ 314.755773] session1: iscsi_eh_device_reset dev rese
[Touch-packages] [Bug 1933117] Re: ufw delete can confuse protocol-specific rule with otherwise matching 'proto any' rule
This bug was fixed in the package ufw - 0.36-0ubuntu0.18.04.2 --- ufw (0.36-0ubuntu0.18.04.2) bionic; urgency=medium * d/p/0002-set-default-policy-after-load.patch: fix boot stall on iscsi/network root filesystem when starting ufw (LP: #1946804) * d/p/0003-unconditionally-reload-with-delete.patch: fix corner case of rule deletion with specific/any proto (LP: #1933117) -- Mauricio Faria de Oliveira Mon, 25 Oct 2021 14:30:24 -0300 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1933117 Title: ufw delete can confuse protocol-specific rule with otherwise matching 'proto any' rule Status in ufw: Fix Released Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Bug description: [Impact] * The deletion of a rule without the 'proto' field that has a similar rule *with* the 'proto' field might delete the wrong rule (the latter). * This might cause services to be inaccessible or incorrectly allowed, depending on rule ordering (read original description below for examples.) [Test Steps] * Add rules: ufw allow from 1.1.1.1 port proto tcp ufw allow from 2.2.2.2 port proto tcp ufw allow from 1.1.1.1 port * Check iptables: iptables -L ufw-user-input -n ... ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT udp -- 1.1.1.1 0.0.0.0/0 udp spt: * Delete the third rule above ufw status numbered yes | ufw delete 3 * Check iptables again: iptables -L ufw-user-input -n Observed: (deleted tcp line from first rule, and udp line from third rule) ... ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: Expected: (deleted both tcp and udp lines from third rule) ... ACCEPT tcp -- 1.1.1.1 0.0.0.0/0 tcp spt: ACCEPT tcp -- 2.2.2.2 0.0.0.0/0 tcp spt: [Regression Potential] * Potential regressions would be observed when deleting rules. * This fix has been suggested for SRU by jdstrand [1], and has already been available in 21.04 and the snap. [1] https://code.launchpad.net/~mfo/ufw/+git/ufw/+merge/410091/comments/1083005 [Original Description] UFW versions 0.35 (on Ubuntu 16.04 LTS) and 0.36 (on Ubuntu 20.04 LTS) If a rule is inserted without specifying the protocol, it will default to both udp and tcp. If a second rule is inserted earlier in the order that specifies the protocol but is otherwise identical, UFW will delete the wrong rule if the first rule is deleted. This is repeatable with the following script: ufw insert 1 allow from 1.1.1.1/26 to any port 22 ufw insert 2 allow from 1.2.3.4/26 to any port 22 ufw insert 1 allow from 1.2.3.4/26 to any port 22 proto tcp iptables -L -n | grep -A 6 "Chain ufw-user-input" yes | ufw delete 3 iptables -L -n | grep -A 4 "Chain ufw-user-input" The output is as follows: Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 ACCEPT tcp -- 1.1.1.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.1.1.0/26 0.0.0.0/0udp dpt:22 ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.2.3.0/26 0.0.0.0/0udp dpt:22 Chain ufw-user-input (1 references) target prot opt source destination ACCEPT tcp -- 1.1.1.0/26 0.0.0.0/0tcp dpt:22 ACCEPT udp -- 1.1.1.0/26 0.0.0.0/0udp dpt:22 ACCEPT tcp -- 1.2.3.0/26 0.0.0.0/0tcp dpt:22 UFW deleted the first rule for 1.2.3.0 and then the last rule for 1.2.3.0, leaving the wrong rule remaining. Here is the ufw status: To Action From -- -- 22/tcp ALLOW 1.2.3.0/26 22 ALLOW 1.1.1.0/26 Mixing ALLOW and REJECT/DENY rules can further result in incorrect behavior due to this incorrect reordering. On port 22, this could render SSH remotely inaccessible. For example, if one had initially set up the following rule to port 22 (TCP and UDP)... ufw insert 1 allow from 1.2.3.4 to any port 22 ...and later wanted to further restrict it to only TCP, while explicitly rejecting any other port 22 connections... ufw insert 1 allow from 1.2.3.4 to any port 22 proto tcp u
[Touch-packages] [Bug 1946804] Update Released
The verification of the Stable Release Update for ufw 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 ufw in Ubuntu. https://bugs.launchpad.net/bugs/1946804 Title: ufw breaks boot on network root filesystem Status in ufw: Fix Committed Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Status in ufw source package in Impish: Fix Released Bug description: [Impact] A system with rootfs on iSCSI stops booting when ufw.service starts. The kernel logs iSCSI command/reset timeout until I/O fails and the root filesystem/journal break. The issue is that ufw_start() sets the default policy _first_, then adds rules _later_. So, a default INPUT policy of DROP (default setting in ufw) prevents further access to the root filesystem (blocks incoming iSCSI traffic) thus any rules that could help are not loaded (nor anything else.) [Fix] The fix is to set default policy after loading rules in ufw_start(). That seems to be OK as `ip[6]tables-restore -n/--noflush` is used, and per iptables source, that only sets the chain policy. This allows the system to boot due to the RELATED,ESTABLISHED rule, that is introduced by before.rules in INPUT/ufw-before-input chain. The comparison of `iptables -L` before/after shows no differences (verified on a local rootfs); `run_tests.sh` has 0 skipped/errors. [Test Steps] * Install Ubuntu on an iSCSI (or other network-based) root filesystem. (eg, Oracle Cloud's bare-metal 'BM.Standard1.36' shape.) * sudo ufw enable * Observed: system may stall immediately if no prior iptables rules. (eg, iptables -A INPUT -p tcp -s 169.254.0.2 --sport 3260 -j ACCEPT) * Expected: system continues working. * sudo reboot * Observed: system boot stalls once ufw.service starts (see below.) * Expected: system boot should move on. [Regression Potential] * Potential regressions would be observed on ufw start/reload, when iptables rules are configured. * The resulting iptables configuration has been compared before/after the change, with identical rules on both. [Other Info] * Fixed in Debian and Jammy. [ufw info] # ufw --version ufw 0.36 Copyright 2008-2015 Canonical Ltd. # lsb_release -cs focal [Boot Log] [ 232.168355] iBFT detected. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Setting up software interface enp45s0f0np0 ... [ 254.644505] Loading iSCSI transport class v2.0-870. [ 254.714938] iscsi: registered transport (tcp) [ 254.780129] scsi host12: iSCSI Initiator over TCP/IP ... [ 255.433491] sd 12:0:0:1: [sda] 251658240 512-byte logical blocks: (129 GB/120 GiB) ... [ 256.379550] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) ... [ 266.620860] systemd[1]: Starting Uncomplicated firewall... Starting Uncomplicated firewall... ... [ 298.491560] session1: iscsi_eh_cmd_timed_out scsi cmd 310a6696 timedout [ 298.580803] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.656262] session1: iscsi_eh_cmd_timed_out scsi cmd 94ad9246 timedout [ 298.745237] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.745270] session1: iscsi_eh_abort aborting sc 310a6696 [ 298.899644] session1: iscsi_eh_abort aborting [sc 310a6696 itt 0x13] [ 298.985788] session1: iscsi_exec_task_mgmt_fn tmf set timeout [ 302.075554] session1: iscsi_eh_cmd_timed_out scsi cmd 1a9458b5 timedout [ 302.164786] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 314.107541] session1: iscsi_tmf_timedout tmf timedout [ 314.169797] connection1:0: detected conn error (1021) [ 314.232266] session1: iscsi_eh_abort abort failed [sc 310a6696 itt 0x13] [ 314.323531] session1: iscsi_eh_abort aborting sc 94ad9246 [ 314.399640] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.495578] session1: iscsi_eh_abort aborting sc 1a9458b5 [ 314.571554] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.664050] session1: iscsi_eh_device_reset LU Reset [sc 310a6696 lun 1] [ 314.755773] session1: iscsi_eh_device_reset dev reset result = FAILED [ 314.834736] session1: iscsi_eh_target_reset tg
[Touch-packages] [Bug 1946804] Re: ufw breaks boot on network root filesystem
This bug was fixed in the package ufw - 0.36.1-1ubuntu1 --- ufw (0.36.1-1ubuntu1) impish; urgency=medium * d/p/0004-set-default-policy-after-load.patch: fix boot stall on iscsi/network root filesystem when starting ufw (LP: #1946804) -- Mauricio Faria de Oliveira Mon, 25 Oct 2021 14:25:30 -0300 ** Changed in: ufw (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1946804 Title: ufw breaks boot on network root filesystem Status in ufw: Fix Committed Status in ufw package in Ubuntu: Fix Released Status in ufw source package in Bionic: Fix Released Status in ufw source package in Focal: Fix Released Status in ufw source package in Hirsute: Fix Released Status in ufw source package in Impish: Fix Released Bug description: [Impact] A system with rootfs on iSCSI stops booting when ufw.service starts. The kernel logs iSCSI command/reset timeout until I/O fails and the root filesystem/journal break. The issue is that ufw_start() sets the default policy _first_, then adds rules _later_. So, a default INPUT policy of DROP (default setting in ufw) prevents further access to the root filesystem (blocks incoming iSCSI traffic) thus any rules that could help are not loaded (nor anything else.) [Fix] The fix is to set default policy after loading rules in ufw_start(). That seems to be OK as `ip[6]tables-restore -n/--noflush` is used, and per iptables source, that only sets the chain policy. This allows the system to boot due to the RELATED,ESTABLISHED rule, that is introduced by before.rules in INPUT/ufw-before-input chain. The comparison of `iptables -L` before/after shows no differences (verified on a local rootfs); `run_tests.sh` has 0 skipped/errors. [Test Steps] * Install Ubuntu on an iSCSI (or other network-based) root filesystem. (eg, Oracle Cloud's bare-metal 'BM.Standard1.36' shape.) * sudo ufw enable * Observed: system may stall immediately if no prior iptables rules. (eg, iptables -A INPUT -p tcp -s 169.254.0.2 --sport 3260 -j ACCEPT) * Expected: system continues working. * sudo reboot * Observed: system boot stalls once ufw.service starts (see below.) * Expected: system boot should move on. [Regression Potential] * Potential regressions would be observed on ufw start/reload, when iptables rules are configured. * The resulting iptables configuration has been compared before/after the change, with identical rules on both. [Other Info] * Fixed in Debian and Jammy. [ufw info] # ufw --version ufw 0.36 Copyright 2008-2015 Canonical Ltd. # lsb_release -cs focal [Boot Log] [ 232.168355] iBFT detected. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Setting up software interface enp45s0f0np0 ... [ 254.644505] Loading iSCSI transport class v2.0-870. [ 254.714938] iscsi: registered transport (tcp) [ 254.780129] scsi host12: iSCSI Initiator over TCP/IP ... [ 255.433491] sd 12:0:0:1: [sda] 251658240 512-byte logical blocks: (129 GB/120 GiB) ... [ 256.379550] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) ... [ 266.620860] systemd[1]: Starting Uncomplicated firewall... Starting Uncomplicated firewall... ... [ 298.491560] session1: iscsi_eh_cmd_timed_out scsi cmd 310a6696 timedout [ 298.580803] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.656262] session1: iscsi_eh_cmd_timed_out scsi cmd 94ad9246 timedout [ 298.745237] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 298.745270] session1: iscsi_eh_abort aborting sc 310a6696 [ 298.899644] session1: iscsi_eh_abort aborting [sc 310a6696 itt 0x13] [ 298.985788] session1: iscsi_exec_task_mgmt_fn tmf set timeout [ 302.075554] session1: iscsi_eh_cmd_timed_out scsi cmd 1a9458b5 timedout [ 302.164786] session1: iscsi_eh_cmd_timed_out return shutdown or nh [ 314.107541] session1: iscsi_tmf_timedout tmf timedout [ 314.169797] connection1:0: detected conn error (1021) [ 314.232266] session1: iscsi_eh_abort abort failed [sc 310a6696 itt 0x13] [ 314.323531] session1: iscsi_eh_abort aborting sc 94ad9246 [ 314.399640] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.495578] session1: iscsi_eh_abort aborting sc 1a9458b5 [ 314.571554] session1: iscsi_eh_abort sc never reached iscsi layer or it completed. [ 314.664050] session1: iscsi_eh_device_reset LU Reset [sc 310a6696 lun 1] [ 314.755773] session1: iscsi_eh_device_reset dev reset result = FAILED [ 314.834736] session1: iscsi_eh_target_reset tgt Reset [sc 310a6696 tgt <...>] [ 314.954144] s
[Touch-packages] [Bug 1939732] Re: report availability of Ubuntu Advantage ESM services on unattached machines
Hello Chad, or anyone else affected, Accepted software-properties into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.18 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1939732 Title: report availability of Ubuntu Advantage ESM services on unattached machines Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Status in software-properties source package in Hirsute: Fix Committed Status in software-properties source package in Impish: Fix Committed Bug description: [Impact] * Error messages emitted to software-properties-gtk console "[Errno 2] No such file or directory: '/var/lib/ubuntu-advantage/status.json'" due to incorrect expectation that status.json file is written when non-root runs `ua status` * This logic results in multiple `ua status` calls which each result in a network-egress to https://contracts.canonical.com on unattached machines which could result in delays in rendering the GTK dialogs while awaiting a response. [Test Case] 1. Install latest version of software-properties-gtk from -proposed cat > setup_proposed.sh
[Touch-packages] [Bug 1934439] Re: Add Ubuntu Pro banner to Livepatch page
Hello Robert, or anyone else affected, Accepted software-properties into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/software-properties/0.96.24.32.18 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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. ** Tags removed: verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1934439 Title: Add Ubuntu Pro banner to Livepatch page Status in software-properties package in Ubuntu: New Status in software-properties source package in Xenial: New Status in software-properties source package in Bionic: Fix Committed Status in software-properties source package in Focal: Fix Committed Bug description: [Impact] Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for Desktop. Note that this is not shown in current releases, as this feature only applies to older versions. [Test Case] 1. Open Software Properties. 2. Go to Livepatch tab. Expected result: A banner is shown directing the user to Ubuntu Pro. The banner can be dismissed, and doesn't return when restarting software-properties. [Regression Potential] Some risk of introducing a new bug, however the change is quite small and doesn't have any complex interactions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1949778] Re: unittest2 doesn't work on python3.10
** Also affects: python-pykmip (Ubuntu) Importance: Undecided Status: New ** Also affects: python-requests-mock (Ubuntu) Importance: Undecided Status: New ** Also affects: python-sphinx-feature-classification (Ubuntu) Importance: Undecided Status: New ** Also affects: python-sushy-cli (Ubuntu) Importance: Undecided Status: New ** Also affects: python-cloudkittyclient (Ubuntu) Importance: Undecided Status: New ** Also affects: python-cyborgclient (Ubuntu) Importance: Undecided Status: New ** Also affects: python-freezerclient (Ubuntu) Importance: Undecided Status: New -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in gitinspector package in Ubuntu: New Status in python-cloudkittyclient package in Ubuntu: New Status in python-cyborgclient package in Ubuntu: New Status in python-deprecation package in Ubuntu: New Status in python-freezerclient package in Ubuntu: New Status in python-futurist package in Ubuntu: New Status in python-jenkins package in Ubuntu: New Status in python-launchpadlib package in Ubuntu: New Status in python-pyghmi package in Ubuntu: New Status in python-pykmip package in Ubuntu: New Status in python-requests-mock package in Ubuntu: New Status in python-sphinx-feature-classification package in Ubuntu: New Status in python-sushy-cli package in Ubuntu: New Status in python-testtools package in Ubuntu: New Status in python-tosca-parser package in Ubuntu: New Status in python-yaql package in Ubuntu: New Status in tempest package in Ubuntu: New Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: New Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitinspector/+bug/1949778/+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 1949778] Re: unittest2 doesn't work on python3.10
** Also affects: python-pyghmi (Ubuntu) Importance: Undecided Status: New -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in gitinspector package in Ubuntu: New Status in python-deprecation package in Ubuntu: New Status in python-futurist package in Ubuntu: New Status in python-jenkins package in Ubuntu: New Status in python-launchpadlib package in Ubuntu: New Status in python-pyghmi package in Ubuntu: New Status in python-testtools package in Ubuntu: New Status in python-tosca-parser package in Ubuntu: New Status in python-yaql package in Ubuntu: New Status in tempest package in Ubuntu: New Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: New Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitinspector/+bug/1949778/+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 1949778] Re: unittest2 doesn't work on python3.10
** Also affects: python-jenkins (Ubuntu) Importance: Undecided Status: New ** Also affects: tempest (Ubuntu) Importance: Undecided Status: New -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in gitinspector package in Ubuntu: New Status in python-deprecation package in Ubuntu: New Status in python-futurist package in Ubuntu: New Status in python-jenkins package in Ubuntu: New Status in python-launchpadlib package in Ubuntu: New Status in python-testtools package in Ubuntu: New Status in python-tosca-parser package in Ubuntu: New Status in python-yaql package in Ubuntu: New Status in tempest package in Ubuntu: New Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: New Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitinspector/+bug/1949778/+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 1949778] Re: unittest2 doesn't work on python3.10
** Also affects: gitinspector (Ubuntu) Importance: Undecided Status: New -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in gitinspector package in Ubuntu: New Status in python-deprecation package in Ubuntu: New Status in python-futurist package in Ubuntu: New Status in python-launchpadlib package in Ubuntu: New Status in python-testtools package in Ubuntu: New Status in python-tosca-parser package in Ubuntu: New Status in python-yaql package in Ubuntu: New Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: New Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitinspector/+bug/1949778/+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 1949778] Re: unittest2 doesn't work on python3.10
Tracking python-futurist as per https://launchpad.net/ubuntu/+source/python- futurist/2.4.0-2/+build/22303692 ** Also affects: python-futurist (Ubuntu) Importance: Undecided Status: New -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in python-deprecation package in Ubuntu: New Status in python-futurist package in Ubuntu: New Status in python-launchpadlib package in Ubuntu: New Status in python-testtools package in Ubuntu: New Status in python-tosca-parser package in Ubuntu: New Status in python-yaql package in Ubuntu: New Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: New Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-deprecation/+bug/1949778/+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 1950496] [NEW] networkd doesn't provide DNS to nspawn containers
Public bug reported: [impact] the host networkd doesn't include DNS info to nspawn containers [test case] create/start a nspawn container, e.g. with 'machinectl start', open a shell in the container, and check resolvectl to see if a nameserver was provided. [regression potential] failures in the host networkd, possibly affecting other host interfaces which are controlled by networkd, or (more likely) failure to provide dhcp to nspawn containers [scope] TBD ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Focal) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Focal) Status: New => In Progress -- 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/1950496 Title: networkd doesn't provide DNS to nspawn containers Status in systemd package in Ubuntu: New Status in systemd source package in Focal: In Progress Bug description: [impact] the host networkd doesn't include DNS info to nspawn containers [test case] create/start a nspawn container, e.g. with 'machinectl start', open a shell in the container, and check resolvectl to see if a nameserver was provided. [regression potential] failures in the host networkd, possibly affecting other host interfaces which are controlled by networkd, or (more likely) failure to provide dhcp to nspawn containers [scope] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950496/+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 1188475] Re: ldap group doesn't work
** Changed in: cyrus-sasl2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1188475 Title: ldap group doesn't work Status in Cyrus-sasl2: Fix Released Status in cyrus-sasl2 package in Ubuntu: Fix Released Bug description: Hello! I wrote almost the same mail to sasl mail list, but , I guess, it is good to fix in 12.04... This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04 Problem is that after user is authentificated with ldap bind , ldap connection for checking user in group ( lak_group_member function ) is made with this user's bind, not bind parameters from config file. User can not ( and have not in our case- I don't know why , but this is not real problem ) have access to ldap groups. And so, authentication is always fail. I added unbind and anonymous bind ( enough in our case): /var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig lak.c --- lak.c.orig2013-06-07 09:15:20.098788278 +0400 +++ lak.c2013-06-07 09:22:31.504774185 +0400 @@ -1342,6 +1342,10 @@ if (rc != LAK_OK) goto done; +lak_unbind (lak ); +rc = lak_bind(lak, ""); + + rc = ldap_search_st(lak->ld, group_search_base, lak->conf->group_scope, group_filter, (char **) group_attrs, 0, &(lak->conf->timeout), &res); switch (rc) { case LDAP_SUCCESS: but, it is obvoius that rebind should be done with credintials from config, but this is over my head :-( Could you, please, fix this bug correctly? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/1188475/+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 1950484] Re: Adding an admin user a Gnome Control Center should set the right groups
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1950484 Title: Adding an admin user a Gnome Control Center should set the right groups Status in accountsservice package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Currently when installing Ubuntu , the default admin belongs to several essential groups : adm cdrom sudo dip plugdev lpadmin lxd sambashare But when adding a user from GCC , the new admin user will only belong to : sudo This leads that the second admin cannot add printers and so on... This is observed on a clean 20.04.3 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1950484/+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 1949535] Re: X-forwarding no longer works
Closing the bug as Invalid as per the reporter's request. ** Changed in: openssh (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1949535 Title: X-forwarding no longer works Status in openssh package in Ubuntu: Invalid Bug description: I operate a Linux based Internet hosting service that includes Linux shell servers of various flavors. I control these from home using Ubuntu 21.10 presently. Until recently, X-forwarding has worked from all but ancient Redhat 6.2 servers. I recently upgraded my debian shell server to Bullet, and after the upgrade ssh -X debian.eskimo.com from my workstation nanook.eskimo.com ceased to function. It simply says "Cannot open DISPLAY". At the time, all the others continued to work. Today, when I went to do upgrades, now ssh -X is forwarding across the board to all flavors of Linux. I did an ssh -V, nothing obvious wrong in the connection. debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering public key: /home/nanook/.ssh/id_rsa RSA SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent debug1: Server accepts key: /home/nanook/.ssh/id_rsa RSA SHA256:a5bReJXl7L91eGOuCYugHsY2rn2a0WTDXEBTC93YdmA agent debug1: Authentication succeeded (publickey). Authenticated to igloo.eskimo.com ([204.122.16.128]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0 debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding debug1: Remote: /home/nanook/.ssh/authorized_keys:1: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: client_input_channel_req: channel 0 rtype e...@openssh.com reply 0 debug1: channel 0: free: client-session, nchannels 1 debug1: fd 2 clearing O_NONBLOCK Connection to igloo.eskimo.com closed. Transferred: sent 3748, received 3820 bytes, in 6.4 seconds Bytes per second: sent 589.4, received 600.8 I don't see anything obviously wrong here but still it does not work, I get: xclock Error: Can't open display: ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ssh (not installed) Uname: Linux 5.13.19 x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Tue Nov 2 17:31:14 2021 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1949535/+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 1950484] Re: Adding an admin user a Gnome Control Center should set the right groups
Interestingly, it appears that accountsservice has a build-time option to enable extra admin groups (extra_admin_groups), but the version in focal (0.6.55-0ubuntu12~20.04.4) has a debian patch that ignores it. That patch was recently reworked to not ignore the option: https://salsa.debian.org/freedesktop- team/accountsservice/-/commit/b1724af16828c08543cfae167daad46269051028. This would require version 0.6.55-2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1950484 Title: Adding an admin user a Gnome Control Center should set the right groups Status in accountsservice package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Currently when installing Ubuntu , the default admin belongs to several essential groups : adm cdrom sudo dip plugdev lpadmin lxd sambashare But when adding a user from GCC , the new admin user will only belong to : sudo This leads that the second admin cannot add printers and so on... This is observed on a clean 20.04.3 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1950484/+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 1950487] [NEW] screen flickering
Public bug reported: The problem is, when i start working on my pc the screen start flickering goes from black to normal, it's a matter of graphic card(nvidia) but i failed to solve it, any suggestion: *-display UNCLAIMED description: 3D controller product: GM107M [GeForce GTX 960M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: memory:d000-d0ff memory:a000-afff memory:b000-b1ff ioport:4000(size=128) memory:b200-b207 *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: driver=i915 latency=0 resources: irq:37 memory:d100-d13f memory:c000-cfff ioport:5000(size=64) memory:c-d ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 17:14:48 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3978] Subsystem: Lenovo GM107M [GeForce GTX 960M] [17aa:3978] InstallationDate: Installed on 2021-11-10 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=eb605582-0819-4c08-a72a-63c9558e8612 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 3.43 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.ec.firmware.release: 3.43 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:br3.43:efr3.43:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70:skuLENOVO_MT_20378_BU_idea_FM_LenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.sku: LENOVO_MT_20378_BU_idea_FM_Lenovo Y50-70 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption impish ubuntu wayland-session -- 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/1950487 Title: screen flickering Status in xorg package in Ubuntu: New Bug description: The problem is, when i start working on my pc the screen start flickering goes from black to normal, it's a matter of graphic card(nvidia) but i failed to solve it, any suggestion: *-display UNCLAIMED description: 3D controller product: GM107M [GeForce GTX 960M] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: latency=0 resources: memory:d000-d0ff memory:a000-afff memory:b000-b1ff ioport:4000(size=128) memory:b200-b207 *-display description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info
[Touch-packages] [Bug 1950484] Re: Adding an admin user a Gnome Control Center should set the right groups
** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1950484 Title: Adding an admin user a Gnome Control Center should set the right groups Status in accountsservice package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: Currently when installing Ubuntu , the default admin belongs to several essential groups : adm cdrom sudo dip plugdev lpadmin lxd sambashare But when adding a user from GCC , the new admin user will only belong to : sudo This leads that the second admin cannot add printers and so on... This is observed on a clean 20.04.3 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1950484/+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 1778073] Re: dnsmasq and resolvconf hangs on start
** Tags removed: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1778073 Title: dnsmasq and resolvconf hangs on start Status in dnsmasq package in Ubuntu: Incomplete Status in dnsmasq package in Debian: New Bug description: I installed today dnsmasq and I use resolvconf in background. Problem is, that systemd takes 1 minute or so after service start and than reports: root@proxy:~# service dnsmasq status dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled) Drop-In: /run/systemd/generator/dnsmasq.service.d 50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf Active: failed (Result: timeout) since Do 2018-06-21 15:58:13 CEST; 2min 10s ago Process: 3295 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf (code=killed, signal=TERM) Process: 3865 ExecStartPost=/etc/init.d/dnsmasq systemd-start-resolvconf (code=killed, signal=TERM) Process: 3837 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, status=0/SUCCESS) Process: 3825 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, status=0/SUCCESS) Main PID: 3862 (code=exited, status=0/SUCCESS) Jun 21 15:56:43 proxy dnsmasq[3862]: Benutze Namensserver 192.168.23.1#53 Jun 21 15:56:43 proxy dnsmasq[3865]: * Awakening mail retriever agent: Jun 21 15:56:43 proxy dnsmasq[3865]:...done. Jun 21 15:56:43 proxy postfix[3951]: Postfix is running with backwards-compatible default settings Jun 21 15:56:43 proxy postfix[3951]: See http://www.postfix.org/COMPATIBILITY_README.html for details Jun 21 15:56:43 proxy postfix[3951]: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload" Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Start-post operation timed out. Stopping. Jun 21 15:58:13 proxy systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server. Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Unit entered failed state. Jun 21 15:58:13 proxy systemd[1]: dnsmasq.service: Failed with result 'timeout'. when I look into the start script /etc/init.d/dnsmasq there is a func systemd-start-resolvconf which points to start-resolvconf. There is this part: for interface in $DNSMASQ_EXCEPT do [ $interface = lo ] && return done Before I had not defined DNSMASQ_EXCEPT in /etc/defaults/dnsmasq. Problem is, that this part MUST be faulty! When I commend it out, I can start dnsmasq! It looks like it loops forever there?! Also if I define DNSMASQ_EXCEPT to my listen interface, it works - but is is really needed? I found a other user which had the same problem: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871958 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1ubuntu0.16.04.4 [modified: etc/default/dnsmasq] ProcVersionSignature: Ubuntu 4.15.0-23.25~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Jun 21 16:12:14 2018 InstallationDate: Installed on 2017-02-27 (479 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) PackageArchitecture: all ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.dnsmasq: 2018-06-21T16:07:24.818774 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1778073/+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 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
Hello Jean-Baptiste, or anyone else affected, Accepted mesa into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.3~20.04.4 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: mesa (Ubuntu Focal) Status: Triaged => 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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Bug description: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. [What could go wrong] The patch resets two pointers to NULL in dri_unbind_context(), which is correct for that function and can't regress anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)
fixed in 21.2.5-1 which is in jammy-proposed ** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Status in mesa source package in Impish: New Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1946621/+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 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Changed in: mesa (Ubuntu Focal) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Triaged Bug description: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. [What could go wrong] The patch resets two pointers to NULL in dri_unbind_context(), which is correct for that function and can't regress anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. [What could go wrong] + + The patch resets two pointers to NULL in dri_unbind_context(), which is + correct for that function and can't regress anything else. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Incomplete Bug description: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. [What could go wrong] The patch resets two pointers to NULL in dri_unbind_context(), which is correct for that function and can't regress anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1950473] [NEW] SSH keygen, Key enrollment failed: requested feature not supported
Public bug reported: Bug report: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 21.10 Release:21.10 Codename: impish uname -r 5.13.0-21-generic Yubikey device: yubikey 5 NFC ssh -V OpenSSH_8.4p1 Ubuntu-6ubuntu2, OpenSSL 1.1.1l 24 Aug 2021 Dmesg output: 21.960057] usb 1-3: new full-speed USB device number 4 using xhci_hcd [ 22.296859] usb 1-3: New USB device found, idVendor=1050, idProduct=0407, bcdDevice= 5.12 [ 22.296869] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 22.296873] usb 1-3: Product: YubiKey OTP+FIDO+CCID [ 22.296876] usb 1-3: Manufacturer: Yubico [ 22.296879] usb 1-3: SerialNumber: 0009031500 [ 22.331164] input: Yubico YubiKey OTP+FIDO+CCID as /devices/pci:00/:00:01.3/:02:00.0/usb1/1-3/1-3:1.0/0003:1050:0407.0004/input/input19 [ 22.388838] hid-generic 0003:1050:0407.0004: input,hidraw3: USB HID v1.10 Keyboard [Yubico YubiKey OTP+FIDO+CCID] on usb-:02:00.0-3/input0 [ 22.396252] hid-generic 0003:1050:0407.0005: hiddev2,hidraw4: USB HID v1.10 Device [Yubico YubiKey OTP+FIDO+CCID] on usb-:02:00.0-3/input1 lsusb -v 2>/dev/null | grep -A2 Yubico | grep "bcdDevice" | awk '{print $2}' 5.12 ( Yubikey firmware ) Tried with the key pin: ssh-keygen -t ed25519-sk -O resident -vvv Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: debug3: start_helper: started pid=2678 debug3: ssh_msg_send: type 5 debug3: ssh_msg_recv entering debug1: start_helper: starting /usr/lib/openssh/ssh-sk-helper debug1: sshsk_enroll: provider "internal", device "(null)", application "ssh:", userid "(null)", flags 0x21, challenge len 0 with-pin debug1: sshsk_enroll: using random challenge debug1: sk_probe: 1 device(s) detected debug1: sk_probe: selecting sk by touch debug1: ssh_sk_enroll: using device /dev/hidraw4 debug1: ssh_sk_enroll: /dev/hidraw4 does not support credprot, refusing to create unprotected resident/verify-required key debug1: sshsk_enroll: provider "internal" returned failure -2 debug1: ssh-sk-helper: Enrollment failed: requested feature not supported debug1: ssh-sk-helper: reply len 8 debug3: ssh_msg_send: type 5 debug1: client_converse: helper returned error -59 debug3: reap_helper: pid=2678 Key enrollment failed: requested feature not supported Tried with touching the key: $ ssh-keygen -t ed25519-sk -O resident -vvv Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: debug3: start_helper: started pid=2681 debug3: ssh_msg_send: type 5 debug3: ssh_msg_recv entering debug1: start_helper: starting /usr/lib/openssh/ssh-sk-helper debug1: sshsk_enroll: provider "internal", device "(null)", application "ssh:", userid "(null)", flags 0x21, challenge len 0 with-pin debug1: sshsk_enroll: using random challenge debug1: sk_probe: 1 device(s) detected debug1: sk_probe: selecting sk by touch debug1: ssh_sk_enroll: using device /dev/hidraw4 debug1: ssh_sk_enroll: /dev/hidraw4 does not support credprot, refusing to create unprotected resident/verify-required key debug1: sshsk_enroll: provider "internal" returned failure -2 debug1: ssh-sk-helper: Enrollment failed: requested feature not supported debug1: ssh-sk-helper: reply len 8 debug3: ssh_msg_send: type 5 debug1: client_converse: helper returned error -59 debug3: reap_helper: pid=2681 Key enrollment failed: requested feature not supported ** Affects: gnupg (Ubuntu) Importance: Undecided Status: New ** Description changed: Bug report: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 21.10 Release: 21.10 Codename: impish uname -r 5.13.0-21-generic - ssh -V + Yubikey device: yubikey 5 NFC + + ssh -V OpenSSH_8.4p1 Ubuntu-6ubuntu2, OpenSSL 1.1.1l 24 Aug 2021 Dmesg output: 21.960057] usb 1-3: new full-speed USB device number 4 using xhci_hcd [ 22.296859] usb 1-3: New USB device found, idVendor=1050, idProduct=0407, bcdDevice= 5.12 [ 22.296869] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 22.296873] usb 1-3: Product: YubiKey OTP+FIDO+CCID [ 22.296876] usb 1-3: Manufacturer: Yubico [ 22.296879] usb 1-3: SerialNumber: 0009031500 [ 22.331164] input: Yubico YubiKey OTP+FIDO+CCID as /devices/pci:00/:00:01.3/:02:00.0/usb1/1-3/1-3:1.0/0003:1050:0407.0004/input/input19 [ 22.388838] hid-generic 0003:1050:0407.0004: input,hidraw3: USB HID v1.10 Keyboard [Yubico YubiKey OTP+FIDO+CCID] on usb-:02:00.0-3/input0 [ 22.396252] hid-generic 0003:1050:0407.0005: hiddev2,hidraw4: USB HID v1.10 Device [Yubico YubiKey OTP+FIDO+CCID] on usb-:02:00.0-3/input1 - lsusb -v 2>/dev/null | grep -A2 Yubico | grep "bcdDevice" | awk '{print $2}' 5.12 - Tried with they key pin: + Tried with the key pin:
[Touch-packages] [Bug 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
This bug was fixed in the package libsignon-glib - 2.1-3ubuntu0.21.04 --- libsignon-glib (2.1-3ubuntu0.21.04) hirsute; urgency=medium * add replaces relationship to gir1.2-signon-2.0 package. LP: #1916250 -- Rolf Leggewie Fri, 19 Feb 2021 16:52:20 +0100 ** Changed in: libsignon-glib (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: Fix Released Status in libsignon-glib source package in Impish: Fix Released Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1916250] Update Released
The verification of the Stable Release Update for libsignon-glib 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 libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: Fix Released Status in libsignon-glib source package in Impish: Fix Released Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
This bug was fixed in the package libsignon-glib - 2.1-3ubuntu0.21.10 --- libsignon-glib (2.1-3ubuntu0.21.10) impish; urgency=medium * add replaces relationship to gir1.2-signon-2.0 package. LP: #1916250 -- Rolf Leggewie Fri, 19 Feb 2021 16:52:20 +0100 ** Changed in: libsignon-glib (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: Fix Released Status in libsignon-glib source package in Impish: Fix Released Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
This bug was fixed in the package alsa-lib - 1.2.2-2.1ubuntu2.5 --- alsa-lib (1.2.2-2.1ubuntu2.5) focal; urgency=medium * d/p/0001-ucm-fix-regexec-REG_NOMATCH-state-handling-for-defin.patch - ucm: Fix a Regex parser bug, when there is no match, need to set err to 0, otherwise, the caller will get a wrong match instead of no match. (LP: #1949329) -- Hui Wang Mon, 01 Nov 2021 15:25:07 +0800 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-lib source package in Impish: Fix Released Status in alsa-lib source package in Jammy: Fix Released Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949329] Update Released
The verification of the Stable Release Update for alsa-lib 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 alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-lib source package in Impish: Fix Released Status in alsa-lib source package in Jammy: Fix Released Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
This bug was fixed in the package alsa-lib - 1.2.4-1.1ubuntu2.1 --- alsa-lib (1.2.4-1.1ubuntu2.1) hirsute; urgency=medium * d/p/0001-ucm-fix-regexec-REG_NOMATCH-state-handling-for-defin.patch - ucm: Fix a Regex parser bug, when there is no match, need to set err to 0, otherwise, the caller will get a wrong match instead of no match. (LP: #1949329) -- Hui Wang Mon, 01 Nov 2021 15:17:07 +0800 ** Changed in: alsa-lib (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** Changed in: alsa-lib (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-lib source package in Impish: Fix Released Status in alsa-lib source package in Jammy: Fix Released Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949329] Re: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string
This bug was fixed in the package alsa-lib - 1.2.4-1.1ubuntu3.1 --- alsa-lib (1.2.4-1.1ubuntu3.1) impish; urgency=medium * d/p/0001-ucm-fix-regexec-REG_NOMATCH-state-handling-for-defin.patch - ucm: Fix a Regex parser bug, when there is no match, need to set err to 0, otherwise, the caller will get a wrong match instead of no match. (LP: #1949329) -- Hui Wang Mon, 01 Nov 2021 15:05:47 +0800 ** Changed in: alsa-lib (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1949329 Title: [SRU] alsa-lib: ucm: Regex returns correct value without matching a string Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Status in alsa-lib source package in Impish: Fix Released Status in alsa-lib source package in Jammy: Fix Released Bug description: [Impact] In the Dell project, we tried to enable the audio on a machine, the machine has the soundwire audio design, it needs to load the ucm correctly, then users could see the audio devices from gnome. But on this machine, the ucm can't be loaded, through debugging, we found this machine has no headset, the Regex returns a wrong value when matching "Regex " hs:([a-z0-9]+(-sdca)?)". If let Regex returns a correct value, the ucm could be loaded successfully. [Fix] Backport a commit from upstream, this commit is merged to upstream from v1.2.5 [Test] After installed the patched libasound2, reboot, we could see the ucm is loaded succesfully on this machine, and open the gnome-sound-setting, we could see the internal mic and internal speaker, and all of them could work normally. [Where problems will occur] This change affect the Regex parser in the ucm, so if it could introduce regression, it will be on the ucm. It could make the audio not work (fail to load ucm and users can't see any audio devices from gnome) on the machines which need ucm. But this possibility is very low, since this commit is backported from upstream and we already tested this backporting on 2 lenovo machines and 2 Dell machines which all need ucm to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949329/+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 1949778] Re: unittest2 doesn't work on python3.10
This bug was fixed in the package unittest2 - 1.1.0-8 --- unittest2 (1.1.0-8) unstable; urgency=medium * Team upload. [ Ondřej Nový ] * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. [ Athos Ribeiro ] * d/p/python3.10-support.patch: Fix collections call for python 3.10 support (Closes: #998473) (LP: #1949778) [ Scott Talbert ] * Update debhelper-compat level to 13 -- Scott Talbert Tue, 09 Nov 2021 19:37:46 -0500 ** Changed in: unittest2 (Ubuntu) Status: New => Fix Released -- 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/1949778 Title: unittest2 doesn't work on python3.10 Status in python-deprecation package in Ubuntu: New Status in python-launchpadlib package in Ubuntu: New Status in python-testtools package in Ubuntu: New Status in python-tosca-parser package in Ubuntu: New Status in python-yaql package in Ubuntu: New Status in unittest2 package in Ubuntu: Fix Released Status in unittest2 package in Debian: New Bug description: Since Python 3.3, using or importing ABCs from 'collections' instead of 'collections.abc' has been deprecated, and it's finally removed in python 3.10. Because unittest2 relies on these collections in it's compatibility helpers, it fails to run on 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-deprecation/+bug/1949778/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
This is still valid for jammy. As mentioned by Kartik, in [1], a fix in /etc/logcheck/ignore.d.server/libsasl-modules should not fix the issue of getting the message spammed into the logs. I found this issue upstream [2] with a relevant comment [3] from 2019. I pinged upstream on this issue since it would be nice to assess whether we could remove the message or find a way to opt out there. [1] https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/827151/comments/17 [2] https://github.com/cyrusimap/cyrus-sasl/issues/386 [3] https://github.com/cyrusimap/cyrus-sasl/issues/386#issuecomment-504710968 ** Bug watch added: github.com/cyrusimap/cyrus-sasl/issues #386 https://github.com/cyrusimap/cyrus-sasl/issues/386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: New Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 package in Debian: New Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. + + [What could go wrong] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Incomplete Bug description: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. [What could go wrong] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
I don't see how your updated "Where problems could occur" addresses my comment 22 at all. -- 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/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: New Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested update has 2 parts: 1. Informative 1.1 Provide more information about modems whose drivers use WWAN subsystem in kernel 5.13 1.2 Modem manufacture's private utilities can use this information to do modem's FW upgrading manually 2. Changes are specific to Foxconn and Quectel modems 2.1 Modified code are only used by Foxconn and Quectel modems during their FW upgrading. (matched by vendor_id and product_id) In current Ubuntu's certification records for modem: * No other modem uses WWAN subsystem in kernel 5.13 * Modem's FW update is not supported via ModemManager ( < v1.18 ) There is no certificated modems can do the firmware upgrading flow for the regression test. This update should not affect existing modems. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
This SRU upload is missing SRU information. Please follow https://wiki.ubuntu.com/StableReleaseUpdates#Procedure. Thanks! ** Changed in: mesa (Ubuntu Focal) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Incomplete Bug description: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1950441] Re: HDMI monitor no life: VGA monitor life after hibernation
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1950441 Title: HDMI monitor no life: VGA monitor life after hibernation Status in xorg package in Ubuntu: New Bug description: I walked away from my dual monitor machine one monitor is old VGA one monitor is HDMI I returned to use machine machine = hibernation I moved the mouse VGA monitor works after hibernation HDMI monitor does [NOT update|blank screen|no signal] after hibernation I am experiencing lots of monitor issues with impish! video https://youtu.be/sjqyQn9EWp8 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 11:11:07 2021 DistUpgraded: 2021-10-19 08:03:15,745 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (2270 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 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.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=1 mtime.conffile..etc.default.apport: 2021-11-09T14:33:49.606944 version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 xserver.bootTime: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1950441/+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 1950441] [NEW] HDMI monitor no life: VGA monitor life after hibernation
You have been subscribed to a public bug: I walked away from my dual monitor machine one monitor is old VGA one monitor is HDMI I returned to use machine machine = hibernation I moved the mouse VGA monitor works after hibernation HDMI monitor does [NOT update|blank screen|no signal] after hibernation I am experiencing lots of monitor issues with impish! video https://youtu.be/sjqyQn9EWp8 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 11:11:07 2021 DistUpgraded: 2021-10-19 08:03:15,745 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (2270 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 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.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=1 mtime.conffile..etc.default.apport: 2021-11-09T14:33:49.606944 version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 xserver.bootTime: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu -- HDMI monitor no life: VGA monitor life after hibernation https://bugs.launchpad.net/bugs/1950441 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10
Interesting update Given the "Unit nvidia-resume.service is masked" complain by systemd- logind in my previous comment, I thought it could be related with the switching on and off the proprietary nvidia driver: after turning it on, I turned it off (switching to Nouveau) because of this other bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947614 So, I opened the "Software & Updates" tool and in "Additional Drivers" I turned nvidia-driver-470 on again and... voila', the session-crash-on-suspend bug disappeared. It looks like to me that the tool messed up some systemd units like nvidia-resume.service and it didn't return them to the previous state after I switched back to Nouveau. Note: the only thing I used to turn on and off the nvidia driver is that "Software & Updates" tool, no custom configurations/hacks at all. -- 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/1950393 Title: GDM session crashes on suspend on Ubuntu 21.10 Status in gdm3 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Since I started using kernel 5.13.0-20 (and 5.13.0-21) on Ubuntu 21.10, my GDM session crashes when I try to put my laptop to standby. I've attached a relevant slice of the system journal that starts from the moment I pressed the power button, configured to trigger suspend, in my case. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 00:47:13 2021 DistUpgraded: 2021-10-16 23:05:19,206 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2020-03-17 (602 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to impish on 2021-10-16 (24 days ago) dmi.bios.date: 08/09/2017 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1950393/+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 1785236] Re: "dm-tool add-nested-seat" doesn't work normally
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1785236 Title: "dm-tool add-nested-seat" doesn't work normally Status in lightdm package in Ubuntu: Confirmed Bug description: Hello, since I installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" hasn't worked normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1785236/+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 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10
If I grep for `systemd`, after the first meaningful message: Nov 10 00:20:06 lenovo systemd-logind[11553]: Power key pressed. The first error is: Nov 10 00:20:11 lenovo systemd-logind[11553]: Error during inhibitor- delayed operation (already returned success to client): Unit nvidia- resume.service is masked. And later: Nov 10 00:20:13 lenovo /usr/libexec/gdm-x-session[12386]: (EE) systemd- logind disappeared (stopped/restarted?) ** Also 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/1950393 Title: GDM session crashes on suspend on Ubuntu 21.10 Status in gdm3 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: Since I started using kernel 5.13.0-20 (and 5.13.0-21) on Ubuntu 21.10, my GDM session crashes when I try to put my laptop to standby. I've attached a relevant slice of the system journal that starts from the moment I pressed the power button, configured to trigger suspend, in my case. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 00:47:13 2021 DistUpgraded: 2021-10-16 23:05:19,206 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 530 [17aa:380a] Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b] InstallationDate: Installed on 2020-03-17 (602 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 80RU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to impish on 2021-10-16 (24 days ago) dmi.bios.date: 08/09/2017 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: E5CN61WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo ideapad 700-15ISK dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 700-15ISK dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80RU dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK dmi.product.version: Lenovo ideapad 700-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1950393/+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 1950201] Re: Gnugpg does not offer the option to store the private and public keys on two different keycards.
** Description changed: Gnugpg does not offer the option to store the private and public keys on two different keycards. I have followed the official yubikey guide as follows, ( found here : https://support.yubico.com/hc/en-us/articles/360013790259-Using-Your-YubiKey-with-OpenPGP ) - but it might apply to similar smart cards and USB tokens: + but it might apply to similar smart cards and USB tokens: To import the key on your YubiKey: Insert the YubiKey into the USB port if it is not already plugged in. Enter the GPG command: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key) Enter the command: keytocard When prompted if you really want to move your primary key, enter y (yes). When prompted where to store the key, select 1. This will move the signature subkey to the PGP signature slot of the YubiKey. Enter the command: key 1 Enter the command: keytocard When prompted where to store the key, select 2. This will move the encryption subkey to the YubiKey. Enter the command: key 1 Enter the command: key 2 Enter the command: keytocard When prompted where to store the key, select 3. This will move the authentication subkey to the YubiKey. Enter the command: quit When prompted to save your changes, enter y (yes). You have now saved your keyring to your YubiKey. The issue with that is that it permanently moves the secret keys to the yubikey or similar, and that causes issues later if one wants to create backup keys. If one saves the changes and tries to make a separate identical key card at a later date, one gets the "gpg: KEYTOCARD failed: Unusable secret key." error. I have read that if one presses control and c ( on Linux ) it after the last keytocard and option 3, the secret keys will not be deleted from the computer, only copied. One then can start forward again at this step: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key). Another possible but tedious workaround is to backup the secret keys and public keys, and import those back into gpg, then move they keys to a physical backup key. ( Note: Key 0 is the primary signature subkey. Key 1is the encryption subkey. key 2 is the authentication subkey .) Ideally, there should be a option in the gpg menu about this, that asks about permanently moving the keys. A nice addition would be: Do you want to make a separate identical key card? + + A additional problem is that even if you manage to create two yubikeys + with the same card then you still cant use them both on the same + computer as a replacement for eachother. + + GnuPG will remeber the card id when it moves te key and will only accept + the same card/yubikey again in the future. + + Workaround is to delete your gnupg home folder and import clean public + keys that have no info which yubikey has the private keys, in that case + gnupg can figure out that it can actually use the other yubikey. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1950201 Title: Gnugpg does not offer the option to store the private and public keys on two different keycards. Status in gnupg package in Ubuntu: New Bug description: Gnugpg does not offer the option to store the private and public keys on two different keycards. I have followed the official yubikey guide as follows, ( found here : https://support.yubico.com/hc/en-us/articles/360013790259-Using-Your-YubiKey-with-OpenPGP ) but it might apply to similar smart cards and USB tokens: To import the key on your YubiKey: Insert the YubiKey into the USB port if it is not already plugged in. Enter the GPG command: gpg --edit-key 1234ABC (where 1234ABC is the key ID of your key) Enter the command: keytocard When prompted if you really want to move your primary key, enter y (yes). When prompted where to store the key, select 1. This will move the signature subkey to the PGP signature slot of the YubiKey. Enter the command: key 1 Enter the command: keytocard When prompted where to store the key, select 2. This will move the encryption subkey to the YubiKey. Enter the command: key 1 Enter the command: key 2 Enter the command: keytocard When prompted where to store the key, select 3. This will move the authentication subkey to the YubiKey. Enter the command: quit When prompted to save your changes, enter y (yes). You have now saved your keyring to your YubiKey. The issue with that is that it permanently moves the secret keys to the yubikey or similar, and that causes issues later if one wants to create backup keys. If one saves the changes and tries to make a separate identical key card
[Touch-packages] [Bug 1945852] Re: [Dell Vostro 3500] sound strange noise - pulseaudio
The error can be partially resolved by installing oem kernel versions. The error was not present on the newest one available from the repository (for example, linux-image-5.14.0-1007-oem). The sound was good most of the time, but sometimes it faded out, then you had to connect the headphones to the jack socket for a while and disconnect it. However, there was no need to kill pulseaudio (it was possible to use a laptop on a daily basis). However, I replaced the laptop with a different model so as not to degenerate because the problem was 90% solved on the new kernel. This chipset 'Cirrus Logic' is probably to blame because I have a new dell vostro 5502 with the same intel i5 (11th gen) processor, but the chipset has 'Realtek ALC3204' and everything works on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1945852 Title: [Dell Vostro 3500] sound strange noise - pulseaudio Status in pulseaudio package in Ubuntu: Confirmed Bug description: The sound from the speakers and headphones is distorted when the system startup. Has some strange disturbance in sound. If I issue "pulseausio -k; pulseaudio --start" the sound is correct but when another startup problem is come back. Reinstalling pulseaudio and alsa does not help. Actually my pulseaudio version is 1:13.99.1-1ubuntu3.11. I try under ubuntu 20.04.3 LTS and 21.04 but it is the same bug. Installing another newer kernel doesn't help either. The card is HDA Intel PCH, Cirrus Logic CS8409 / CS42L42 chip (Dell Vostro 3500). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bartek 3166 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 2 09:02:58 2021 InstallationDate: Installed on 2021-10-02 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2021 dmi.bios.release: 1.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0GGCMJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd07/19/2021:br1.8:svnDellInc.:pnVostro3500:pvr:sku0A24:rvnDellInc.:rn0GGCMJ:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3500 dmi.product.sku: 0A24 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1945852/+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 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] + On Windows 11 with WSLg and Ubuntu 20.04 + 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Triaged Bug description: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] On Windows 11 with WSLg and Ubuntu 20.04 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1950174] Re: [SRU] focal: gallium: Reset {d, r}Priv in dri_unbind_context
** Description changed: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] + 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu + 2. Install and launch chrome, edge or vscode + 3. Resize the windows repeatedly + + Verification: + The app must not crash or hang. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1950174 Title: [SRU] focal: gallium: Reset {d,r}Priv in dri_unbind_context Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Triaged Bug description: [Description] This is a request to backport this fix from mesa 21.1 to focal-updates which is affecting users of WSL: https://gitlab.freedesktop.org/mesa/mesa/-/commit/7ff30a0499bd872d77b0f377414bbc03463b9f87 This cached stale pointer is causing various chromium applications (Edge, Chrome, Visual Studio Code, etc…) to hang on resize when vGPU is enabled in WSLg. We’re getting incredibly unlucky because a glx drawable is being freed and reallocated with exactly the same heap pointers during a resize, which is causing Mesa to think the new drawable is already fully initialized when binded to the context, but it is not true and only because the new drawable is matching the old stale pointer for the previously freed drawable… and as a result the context remain invalid and the app is unable to present. With the push of WDDMv3 drivers which expose vGPU in WSL, the number of users hitting this issue is increasing. [Test Case] 1. Verify that hardware acceleration is enable either with glxinfo -B or in edge with edge://gpu 2. Install and launch chrome, edge or vscode 3. Resize the windows repeatedly Verification: The app must not crash or hang. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1950174/+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 1950425] Re: desktop non responsive after going into hibernation
Thanks for the bug report. Please follow the same steps as https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1950316/comments/2 ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1950425 Title: desktop non responsive after going into hibernation Status in Ubuntu: Incomplete Bug description: situation: -machine was left running -went into hibernation mode (blank screen) -on return --keyboard not responsive --mouse not responsive -machine was still running -desktop not functional required hard restart to get machine functional again desktop non responsive after going into hibernation is undesired behavior! ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 09:10:08 2021 DistUpgraded: 2021-10-19 08:03:15,745 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (2270 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 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.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=1 mtime.conffile..etc.default.apport: 2021-11-09T14:33:49.606944 version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 xserver.bootTime: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1950425/+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 1950428] Re: Extra frozen / stuck mouse cursor after screen lock / sleep without fractional scaling
Sounds like you need a slightly newer kernel. https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873052/comments/15 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released ** No longer affects: mutter (Ubuntu) -- 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/1950428 Title: Extra frozen / stuck mouse cursor after screen lock / sleep without fractional scaling Status in linux package in Ubuntu: Fix Released Bug description: After a screenlock the appears a second, fixed or frozen, non-moveable mousecursor that vanishes after reboot. I have no fractional scaling active (as this seems to force the problem for others) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-67.75-lowlatency 5.4.94 Uname: Linux 5.4.0-67-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 08:48:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.20.906316-1188099, 5.4.0-67-lowlatency, x86_64: installed wireguard, 1.0.20201112, 5.4.0-67-lowlatency, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [148c:2378] InstallationDate: Installed on 2020-07-30 (467 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-67-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: H170I-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170I-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950428/+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 1950425] Re: desktop non responsive after going into hibernation
** Package changed: ubuntu => xorg (Ubuntu) -- 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/1950425 Title: desktop non responsive after going into hibernation Status in xorg package in Ubuntu: New Bug description: situation: -machine was left running -went into hibernation mode (blank screen) -on return --keyboard not responsive --mouse not responsive -machine was still running -desktop not functional required hard restart to get machine functional again desktop non responsive after going into hibernation is undesired behavior! ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 09:10:08 2021 DistUpgraded: 2021-10-19 08:03:15,745 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (2270 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 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.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=1 mtime.conffile..etc.default.apport: 2021-11-09T14:33:49.606944 version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 xserver.bootTime: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1950425/+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 1950428] Re: Extra frozen / stuck mouse cursor after screen lock / sleep without fractional scaling
I switched to wayland - I think this happens since than. -- 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/1950428 Title: Extra frozen / stuck mouse cursor after screen lock / sleep without fractional scaling Status in mutter package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After a screenlock the appears a second, fixed or frozen, non-moveable mousecursor that vanishes after reboot. I have no fractional scaling active (as this seems to force the problem for others) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-67.75-lowlatency 5.4.94 Uname: Linux 5.4.0-67-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 08:48:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.20.906316-1188099, 5.4.0-67-lowlatency, x86_64: installed wireguard, 1.0.20201112, 5.4.0-67-lowlatency, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [148c:2378] InstallationDate: Installed on 2020-07-30 (467 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-67-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: H170I-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170I-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1950428/+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 1950428] Re: Extra frozen / stuck mouse cursor after screen lock / sleep without fractional scaling
** Attachment added: "Motion-Gif of the frozen cursor and its moveable friend" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1950428/+attachment/5539473/+files/frozen-cursor.gif ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1950428 Title: Extra frozen / stuck mouse cursor after screen lock / sleep without fractional scaling Status in mutter package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After a screenlock the appears a second, fixed or frozen, non-moveable mousecursor that vanishes after reboot. I have no fractional scaling active (as this seems to force the problem for others) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-67.75-lowlatency 5.4.94 Uname: Linux 5.4.0-67-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 08:48:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.20.906316-1188099, 5.4.0-67-lowlatency, x86_64: installed wireguard, 1.0.20201112, 5.4.0-67-lowlatency, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [148c:2378] InstallationDate: Installed on 2020-07-30 (467 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-67-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: H170I-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170I-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1950428/+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 1950428] [NEW] Extra frozen / stuck mouse cursor after screen lock / sleep without fractional scaling
Public bug reported: After a screenlock the appears a second, fixed or frozen, non-moveable mousecursor that vanishes after reboot. I have no fractional scaling active (as this seems to force the problem for others) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-67.75-lowlatency 5.4.94 Uname: Linux 5.4.0-67-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 08:48:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.20.906316-1188099, 5.4.0-67-lowlatency, x86_64: installed wireguard, 1.0.20201112, 5.4.0-67-lowlatency, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [148c:2378] InstallationDate: Installed on 2020-07-30 (467 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-67-lowlatency root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: H170I-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH170I-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption focal ubuntu wayland-session -- 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/1950428 Title: Extra frozen / stuck mouse cursor after screen lock / sleep without fractional scaling Status in mutter package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: After a screenlock the appears a second, fixed or frozen, non-moveable mousecursor that vanishes after reboot. I have no fractional scaling active (as this seems to force the problem for others) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-67.75-lowlatency 5.4.94 Uname: Linux 5.4.0-67-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 08:48:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.20.906316-1188099, 5.4.0-67-lowlatency, x86_64: installed wireguard, 1.0.20201112, 5.4.0-67-lowlatency, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [148c:2378] InstallationDate: Installed on 2020-07-30 (467 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System
[Touch-packages] [Bug 1950425] [NEW] desktop non responsive after going into hibernation
You have been subscribed to a public bug: situation: -machine was left running -went into hibernation mode (blank screen) -on return --keyboard not responsive --mouse not responsive -machine was still running -desktop not functional required hard restart to get machine functional again desktop non responsive after going into hibernation is undesired behavior! ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 09:10:08 2021 DistUpgraded: 2021-10-19 08:03:15,745 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (2270 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 07/21/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 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.:bvr2501:bd07/21/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=1 mtime.conffile..etc.default.apport: 2021-11-09T14:33:49.606944 version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 xserver.bootTime: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu -- desktop non responsive after going into hibernation https://bugs.launchpad.net/bugs/1950425 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 1941752]
Same here. Ubuntu 21.10 Gwenview 21.08.1 Application: Gwenview (gwenview), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140017931865152) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140017931865152) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140017931865152, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7f587c8a7476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7f587c88d7b7 in __GI_abort () at abort.c:79 #9 0x7f587cb2aa31 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f587cb364ec in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f587cb36557 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x7f587cb367f9 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6 #13 0x7f587cb2d448 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #14 0x7f587c6627fd in ?? () from /lib/x86_64-linux-gnu/libexiv2.so.27 #15 0x7f587c60212d in Exiv2::Xmpdatum::write(std::ostream&, Exiv2::ExifData const*) const () from /lib/x86_64-linux-gnu/libexiv2.so.27 #16 0x7f587ebb86d6 in Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #17 0x7f587eb7dcd0 in Gwenview::Document::setExiv2Image(std::unique_ptr >) () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #18 0x7f587eb88cab in ?? () from /lib/x86_64-linux-gnu/libgwenviewlib.so.5 #19 0x7f587cf92a53 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f587cd78ec5 in QFutureWatcherBase::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f587dcc16b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f587cf5b16a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f587cf5e257 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f587cfb4ef7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f587a6428bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f587a695f08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f587a640003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7f587cfb4548 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f587cf59a9b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f587cf62024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x563a42669553 in ?? () #32 0x7f587c88efd0 in __libc_start_call_main (main=main@entry=0x563a42668fe0, argc=argc@entry=2, argv=argv@entry=0x7fffa40d4c98) at ../sysdeps/nptl/libc_start_call_main.h:58 #33 0x7f587c88f07d in __libc_start_main_impl (main=0x563a42668fe0, argc=2, argv=0x7fffa40d4c98, init=, fini=, rtld_fini=, stack_end=0x7fffa40d4c88) at ../csu/libc-start.c:409 #34 0x563a42669b75 in ?? () [Inferior 1 (process 28983) detached] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)