[Touch-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Thank you Mr. Eickmeyer for your fix in 23.04. > notice how the askubuntu question was closed? That's because it was offtopic/for an unsupported release AskUbuntu closes questions as off-topic *because* they want those questions to be *posted here* instead. It says "Bug reports and problems specific to development version of Ubuntu should be reported on Launchpad so that developers can see, track and fix these issues." Anyway, this bug doesn't affect me, and I might as well treat the Invalid as Fix Committed but not released. > won't be supported until August 2024 (upon release of 24.04.1) Interesting! You helped me learn something today after reading https://ubuntu.com/server/docs/upgrade-introduction . I never noticed this as I personally upgrade to either latest or dev, never LTS specifically. I will post a comment on AskUbuntu to relay this information -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Invalid Status in ubuntustudio-default-settings package in Ubuntu: Invalid Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a
[Touch-packages] [Bug 2051313] Re: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Marked as confirmed as the real reporter is the asker on AskUbuntu, and after my investigation, I confirm that this bug is reasonable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Confirmed Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a `Pre-Depends:` may be necessary instead as I read somewhere on Launchpad. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2051313/+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 2051313] [NEW] font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04
Public bug reported: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Not my computer. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Not my computer. 3) What you expected to happen The AskUbuntu user's upgrade from 22.04 to 24.04 to complete successfully. 4) What happened instead The upgrade failed and they posted to AskUbuntu. # Copy of their question body After an upgrade to ``` Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release: 24.04 Codename:noble ``` apt won't update bcs of unmet dependencies. ``` The following packages have unmet dependencies: libfontconfig1 : Depends: fontconfig-config (>= 2.14.2-6ubuntu1) libfontconfig1:i386 : Depends: fontconfig-config:i386 (>= 2.14.2-6ubuntu1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` I've tried: ``` apt --fix-broken install ``` ``` dpkg: error processing archive /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb (--unpack): trying to overwrite '/etc/fonts/conf.d/10-sub-pixel-rgb.conf', which is also in package ubuntustudio-default-settings 22.04.26.3 dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. dpkg-query: package 'fontconfig-config' is not installed Use dpkg --contents (= dpkg-deb --contents) to list archive files contents. Errors were encountered while processing: /var/cache/apt/archives/fontconfig-config_2.14.2-6ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ``` # Copy of workaround in my answer body The problem is that 24.04 moved `/etc/fonts/conf.d/10-sub-pixel- rgb.conf` out of `ubuntustudio-default-settings` ([before](https://packages.ubuntu.com/jammy/all/ubuntustudio-default- settings/filelist), [after](https://packages.ubuntu.com/noble/all/ubuntustudio-default- settings/filelist)) and into [`fontconfig- config`](https://packages.ubuntu.com/noble/all/fontconfig- config/filelist). The `ubuntustudio-default-settings` package needs to be updated first but the maintainers forgot to add an automatic `Conflicts:` line. You can retry installing the package in the correct order by running `sudo apt install --upgrade ubuntustudio-default-settings`. If that does not work, you need to forcibly reinstall things in the correct order: ```bash sudo -i apt update apt download ubuntustudio-default-settings apt download fontconfig-config # Temporarily force-uninstall only ubuntustudio-default-settings # so that we DON'T uninstall ubuntustudio-desktop dpkg --force-all -r ubuntustudio-default-settings dpkg --force-all -i ./fontconfig-config_* dpkg --force-all -i ./ubuntustudio-default-settings_* dpkg --configure -a apt --fix-broken install apt upgrade apt dist-upgrade ``` # Analysis Please apply an analogous fix. Where I mentioned `Conflicts:` on AskUbuntu, a `Pre-Depends:` may be necessary instead as I read somewhere on Launchpad. ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: ubuntustudio-default-settings (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed ** Changed in: ubuntustudio-default-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2051313 Title: font-config confilcts ubuntustudio-default-settings upgrading from 22.04 to 24.04 Status in fontconfig package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: Confirmed Bug description: This bug was migrated from https://askubuntu.com/q/1501240/1004020 . A nearly identical bug is https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2005124 . It fixed things for `kubuntu-settings-desktop` but not `ubuntustudio- default-settings`. Please add an analogous fix. A similar but potentially unrelated bug is https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-default- settings/+bug/2037471 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
[Touch-packages] [Bug 2018439] Re: Apparmor crashes GPU acceleration
Hi georgiag, thank you for your command suggestion. Yes, it does fix my issue. I had a bunch of tabs open for months and finally closed them. After updating Firefox and not restarting today, it seems that the postinst autoloaded the AppArmor profile despite apparmor.service being disabled, so I had to manually aa-teardown. I then tried to reproduce both with and without your line added. What was frustrating was that the broken behavior failed to appear in these cases: 1. When I added exactly 1 hash to try to comment out your line: s/include/#include/ . Turns out you need to add two hashes ( s/include/##include/ ) for the comment to work. vim confused me as it showed it as a green comment anyway 2. When I did mv local/usr.bin.firefox local/bak.usr.bin.firefox the profile did not load Anyway, when I fell back to adding and removing your entire line manually, I could consistently confirm that your solution works. I feel safer today now that I can reenable apparmor.service . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2018439 Title: Apparmor crashes GPU acceleration Status in apparmor package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Apparmor crashes GPU acceleration Firefox GPU acceleration started crashing after updating from Ubuntu 22.10 to 23.04. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 $ apt-cache policy firefox firefox: Installed: 113.0+build1-0ubuntu0.23.04.1~mt1 Candidate: 113.0+build1-0ubuntu0.23.04.1~mt1 Version table: 1:1snap1-0ubuntu3 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages *** 113.0+build1-0ubuntu0.23.04.1~mt1 999 500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 23.0.3~kisak1~k Candidate: 23.0.3~kisak1~k Version table: *** 23.0.3~kisak1~k 500 500 https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 23.0.2-1ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages $ apt-cache policy apparmor apparmor: Installed: 3.0.8-1ubuntu2 Candidate: 3.0.8-1ubuntu2 Version table: *** 3.0.8-1ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status # Expected behavior Firefox should not crash in WebGL aquarium and continue to work properly like on 22.10. It should successfully use my GPU to make scrolling smooths and save battery when watching videos. # Actual behavior 1. Startup takes a second or two longer than usual 2. Typing in the address bar is slow 3. Scrolling takes 400% CPU usage 4. Scrolling stutters 5. VAAPI on https://www.w3schools.com/html/html5_video.asp is no longer used as shown in intel_gpu_top 6. Fans start spinning and battery goes down fast 7. glxtest failures had to be manually deleted in about:config 8. Only a few fish in WebGL aquarium (https://webglsamples.org/aquarium/aquarium.html) load before Firefox force-closes with the message: "Mozilla Crash Reporter Firefox had a problem and crashed. Unfortunately, the crash reporter is unable to submit a crash report. Details: The application did not leave a crash dump file. Close" 9. The following lines are relevant in dmesg after clearing it: [22157.695580] kauditd_printk_skb: 6 callbacks suppressed [22157.695582] audit: type=1400 audit(1683153440.994:2583): apparmor="DENIED" operation="capable" class="cap" profile="firefox" pid=15898 comm="firefox" capability=21 capname="sys_admin" [22157.739641] audit: type=1400 audit(1683153441.038:2584): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739647] audit: type=1400 audit(1683153441.038:2585): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739719] audit: type=1400 audit(1683153441.038:2586): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739729] audit: type=1400 audit(1683153441.038:2587): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox"
[Touch-packages] [Bug 2044304] Re: Apparmor crashes GPU acceleration in Firefox 120
*** This bug is a duplicate of bug 2018439 ***
https://bugs.launchpad.net/bugs/2018439
There is a more official solution at
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2018439/comments/14
.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2044304
Title:
Apparmor crashes GPU acceleration in Firefox 120
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
$ apt-cache policy apparmor
apparmor:
Installed: 3.0.4-2ubuntu2.3
Candidate: 3.0.4-2ubuntu2.3
Version table:
*** 3.0.4-2ubuntu2.3 500 (phased 20%)
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.0.4-2ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ apt-cache policy firefox
firefox:
Installed: 120.0+build2-0ubuntu0.22.04.1~mt1
Candidate: 120.0+build2-0ubuntu0.22.04.1~mt1
Version table:
1:1snap1-0ubuntu2 -1
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
*** 120.0+build2-0ubuntu0.22.04.1~mt1 1001
1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
jammy/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy libglx-mesa0
libglx-mesa0:
Installed: 23.0.4-0ubuntu1~22.04.1
Candidate: 23.0.4-0ubuntu1~22.04.1
Version table:
*** 23.0.4-0ubuntu1~22.04.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/status
22.0.1-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Firefox Apparmor profile seems out of date and needs extra
permissions.
The issue started happening in Firefox version 120 after an upgrade
from 119.0.1.
I do see the lots of DENIED Apparmor errors before the freeze/crash:
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/sys/devices/pci:00/:00:01.0/:01:00.0/config" pid=11949
comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/sys/devices/pci:00/:00:01.0/:01:00.0/revision"
pid=11949 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/proc/34029/cgroup" pid=34029
comm=49736F6C617465642057656220436F requested_mask="r" denied_mask="r"
fsuid=1000 ouid=1000
MESA: error: Failed to query drm device.
libEGL warning: egl: failed to create dri2 screen
Adding the following the following permissions to
/etc/apparmor.d/local/usr.bin.firefox seems to mitigate the issue:
/sys/devices/pci*/**/{config,revision} r,
@{PROC}/[0-9]*/**/comm r,
@{PROC}/[0-9]*/**/oom_score_adj w,
Disabling the firefox profile also mitigates the issue. It seems the
profile needs an update to include permissions required by Firefox
120.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2044304/+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 2044304] Re: Apparmor crashes GPU acceleration in Firefox 120
*** This bug is a duplicate of bug 2018439 ***
https://bugs.launchpad.net/bugs/2018439
** This bug has been marked a duplicate of bug 2018439
Apparmor crashes GPU acceleration
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2044304
Title:
Apparmor crashes GPU acceleration in Firefox 120
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
$ lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
$ apt-cache policy apparmor
apparmor:
Installed: 3.0.4-2ubuntu2.3
Candidate: 3.0.4-2ubuntu2.3
Version table:
*** 3.0.4-2ubuntu2.3 500 (phased 20%)
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.0.4-2ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
$ apt-cache policy firefox
firefox:
Installed: 120.0+build2-0ubuntu0.22.04.1~mt1
Candidate: 120.0+build2-0ubuntu0.22.04.1~mt1
Version table:
1:1snap1-0ubuntu2 -1
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
*** 120.0+build2-0ubuntu0.22.04.1~mt1 1001
1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu
jammy/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy libglx-mesa0
libglx-mesa0:
Installed: 23.0.4-0ubuntu1~22.04.1
Candidate: 23.0.4-0ubuntu1~22.04.1
Version table:
*** 23.0.4-0ubuntu1~22.04.1 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
100 /var/lib/dpkg/status
22.0.1-1ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Firefox Apparmor profile seems out of date and needs extra
permissions.
The issue started happening in Firefox version 120 after an upgrade
from 119.0.1.
I do see the lots of DENIED Apparmor errors before the freeze/crash:
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/sys/devices/pci:00/:00:01.0/:01:00.0/config" pid=11949
comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/sys/devices/pci:00/:00:01.0/:01:00.0/revision"
pid=11949 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
name="/proc/34029/cgroup" pid=34029
comm=49736F6C617465642057656220436F requested_mask="r" denied_mask="r"
fsuid=1000 ouid=1000
MESA: error: Failed to query drm device.
libEGL warning: egl: failed to create dri2 screen
Adding the following the following permissions to
/etc/apparmor.d/local/usr.bin.firefox seems to mitigate the issue:
/sys/devices/pci*/**/{config,revision} r,
@{PROC}/[0-9]*/**/comm r,
@{PROC}/[0-9]*/**/oom_score_adj w,
Disabling the firefox profile also mitigates the issue. It seems the
profile needs an update to include permissions required by Firefox
120.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2044304/+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 2018439] Re: Apparmor crashes GPU acceleration
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2018439 Title: Apparmor crashes GPU acceleration Status in apparmor package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: Apparmor crashes GPU acceleration Firefox GPU acceleration started crashing after updating from Ubuntu 22.10 to 23.04. $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 $ apt-cache policy firefox firefox: Installed: 113.0+build1-0ubuntu0.23.04.1~mt1 Candidate: 113.0+build1-0ubuntu0.23.04.1~mt1 Version table: 1:1snap1-0ubuntu3 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages *** 113.0+build1-0ubuntu0.23.04.1~mt1 999 500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libglx-mesa0 libglx-mesa0: Installed: 23.0.3~kisak1~k Candidate: 23.0.3~kisak1~k Version table: *** 23.0.3~kisak1~k 500 500 https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status 23.0.2-1ubuntu1 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages $ apt-cache policy apparmor apparmor: Installed: 3.0.8-1ubuntu2 Candidate: 3.0.8-1ubuntu2 Version table: *** 3.0.8-1ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status # Expected behavior Firefox should not crash in WebGL aquarium and continue to work properly like on 22.10. It should successfully use my GPU to make scrolling smooths and save battery when watching videos. # Actual behavior 1. Startup takes a second or two longer than usual 2. Typing in the address bar is slow 3. Scrolling takes 400% CPU usage 4. Scrolling stutters 5. VAAPI on https://www.w3schools.com/html/html5_video.asp is no longer used as shown in intel_gpu_top 6. Fans start spinning and battery goes down fast 7. glxtest failures had to be manually deleted in about:config 8. Only a few fish in WebGL aquarium (https://webglsamples.org/aquarium/aquarium.html) load before Firefox force-closes with the message: "Mozilla Crash Reporter Firefox had a problem and crashed. Unfortunately, the crash reporter is unable to submit a crash report. Details: The application did not leave a crash dump file. Close" 9. The following lines are relevant in dmesg after clearing it: [22157.695580] kauditd_printk_skb: 6 callbacks suppressed [22157.695582] audit: type=1400 audit(1683153440.994:2583): apparmor="DENIED" operation="capable" class="cap" profile="firefox" pid=15898 comm="firefox" capability=21 capname="sys_admin" [22157.739641] audit: type=1400 audit(1683153441.038:2584): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739647] audit: type=1400 audit(1683153441.038:2585): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739719] audit: type=1400 audit(1683153441.038:2586): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.739729] audit: type=1400 audit(1683153441.038:2587): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.769407] audit: type=1400 audit(1683153441.070:2588): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/15898/oom_score_adj" pid=15898 comm="firefox" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 [22157.773042] audit: type=1400 audit(1683153441.074:2589): apparmor="DENIED" operation="file_mmap" class="file" profile="firefox//lsb_release" name="/usr/bin/dash" pid=15934 comm="lsb_release" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [22157.974718] audit: type=1400 audit(1683153441.274:2590): apparmor="DENIED" operation="open" class="file" profile="firefox" name="/proc/15898/cgroup" pid=15898 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [22157.996255] audit: type=1400 audit(1683153441.298:2591): apparmor="DENIED" operation="open" class="file" profile="firefox"
[Touch-packages] [Bug 1990691] Re: fdisk colors are not actually enabled by default
Knowing terminal escape codes, I now see those technically are colors. I had just expected something more ... colorful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1990691 Title: fdisk colors are not actually enabled by default Status in util-linux package in Ubuntu: Invalid Bug description: $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ apt-cache policy fdisk fdisk: Installed: 2.37.2-4ubuntu3 Candidate: 2.37.2-4ubuntu3 Version table: *** 2.37.2-4ubuntu3 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status # Expected behavior `fdisk -l`'s output should have colors other than white and black. Otherwise, `fdisk --help` should not say that colors are enabled by default. https://unix.stackexchange.com/a/385973/524752 says that /etc/terminal-colors.d/fdisk.scheme should exist, but it is missing from `dpkg-query -L fdisk | grep /etc/terminal-colors.d/fdisk.scheme`. # Actual behavior `fdisk -l` shows a list of partitions without color. $ fdisk --help | grep color -L, --color[=] colorize output (auto, always or never) colors are ___enabled___ by default (emphasis mine) $ dpkg-query -L fdisk | grep /etc/terminal-colors.d/fdisk.scheme $ # no output $ cat /etc/terminal-colors.d/fdisk.scheme cat: /etc/terminal-colors.d/fdisk.scheme: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1990691/+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 1995048] Re: reboot reboots system when --poweroff is passed
** Changed in: systemd (Ubuntu) Status: Triaged => Fix Committed -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: Fix Committed Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627387/+files/UdevDb.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627388/+files/acpidump.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] SystemdDelta.txt
apport information ** Attachment added: "SystemdDelta.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627386/+files/SystemdDelta.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627385/+files/ProcModules.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627378/+files/Dependencies.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627377/+files/CurrentDmesg.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627383/+files/ProcCpuinfoMinimal.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627380/+files/Lspci-vt.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627382/+files/ProcCpuinfo.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627384/+files/ProcInterrupts.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627379/+files/Lspci.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1995048/+attachment/5627381/+files/Lsusb-v.txt -- 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/1995048 Title: reboot reboots system when --poweroff is passed Status in systemd package in Ubuntu: New Bug description: The feature of passing "--poweroff" to the reboot command to "Power- off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995048/+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 1995048] [NEW] reboot reboots system when --poweroff is passed
Public bug reported: The feature of passing "--poweroff" to the reboot command to "Power-off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-09-19 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox Package: systemd 249.11-0ubuntu3.6 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Tags: jammy Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy ** Tags added: apport-collected jammy ** Description changed: The feature of passing "--poweroff" to the reboot command to "Power-off the machine, regardless of which one of the three commands is invoked." is broken. Either that or the man page is. This doesn't matter much to me anymore now that I found out that you can also pass "-f" to "poweroff" when debugging, but it confused me a lot at first. $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ apt-cache policy systemd-sysv systemd-sysv: Installed: 249.11-0ubuntu3.6 Candidate: 249.11-0ubuntu3.6 Version table: *** 249.11-0ubuntu3.6 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 249.11-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages # Expected behaviour The system to power off. # Actual behaviour The system reboots. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-09-19 (39 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + Lsusb: + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + MachineType: innotek GmbH VirtualBox + Package: systemd 249.11-0ubuntu3.6 + PackageArchitecture: amd64 + ProcEnviron: + TERM=linux + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=11e9994e-8b05-42e7-949a-2f635b160285 ro text debug + ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 + Tags: jammy + Uname: Linux 5.15.0-52-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/01/2006 + dmi.bios.vendor: innotek GmbH + dmi.bios.version: VirtualBox + dmi.board.name: VirtualBox + dmi.board.vendor: Oracle
[Touch-packages] [Bug 1991199] Re: sshd port migration is missing two config lines from jammy to kinetic
** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619910/+files/Lsusb-t.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619911/+files/Lsusb-v.txt ** Attachment removed: "Lspci-vt.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619908/+files/Lspci-vt.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619907/+files/Lspci.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619909/+files/Lsusb.txt ** Attachment removed: "acpidump.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619919/+files/acpidump.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619918/+files/UdevDb.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619915/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619916/+files/ProcModules.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619905/+files/CurrentDmesg.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199/+attachment/5619912/+files/ProcCpuinfo.txt -- 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/1991199 Title: sshd port migration is missing two config lines from jammy to kinetic Status in openssh package in Ubuntu: Triaged Status in systemd package in Ubuntu: Invalid Bug description: The automatic migration script from jammy to kinetic generates a invalid file for sshd that systemd refuses to read. Manual addition of two lines is required for a functional sshd with a custom port. This bug can be considered the opposite of https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They want to have sshd keep managing the socket while I want to try letting systemd do that. $ lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 $ apt-cache policy openssh-server openssh-server: Installed: 1:9.0p1-1ubuntu6 Candidate: 1:9.0p1-1ubuntu6 Version table: *** 1:9.0p1-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy systemd systemd: Installed: 251.4-1ubuntu6 Candidate: 251.4-1ubuntu6 Version table: *** 251.4-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status # Instructions - Configure /etc/ssh/sshd_config to port in 22.04 - Upgrade to 22.10 with sudo do-release-upgrade -d - Accept overwriting /etc/ssh/sshd_config with the new version - Attempt to ssh into the machine # Expected behavior systemd should listen on port and start sshd. $ cat /etc/systemd/system/ssh.socket.d/addresses.conf [Socket] ListenStream= ListenStream= $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (running) since Thu 2022-09-29 02:08:56 EDT; 9min ago Until: Thu 2022-09-29 02:08:56 EDT; 9min ago Triggers: ● ssh.service Listen: [::]: (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 923us CGroup: /system.slice/ssh.socket Sep 29 02:08:56 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. # Actual behavior Port refuses any connection. Systemd fails to parse the automatically generated file: $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (listening) since Thu 2022-09-29 01:51:57 EDT; 16min ago Until: Thu 2022-09-29 01:51:57 EDT; 16min ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 982us CGroup: /system.slice/ssh.socket Sep 29 01:51:57 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. Sep 29 01:56:23 daniel-desktop2 systemd[1]:
[Touch-packages] [Bug 1991199] acpidump.txt
** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1991199/+attachment/5619919/+files/acpidump.txt ** Information type changed from Private to Public -- 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/1991199 Title: sshd port migration is missing two config lines from jammy to kinetic Status in openssh package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: The automatic migration script from jammy to kinetic generates a invalid file for sshd that systemd refuses to read. Manual addition of two lines is required for a functional sshd with a custom port. This bug can be considered the opposite of https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They want to have sshd keep managing the socket while I want to try letting systemd do that. $ lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 $ apt-cache policy openssh-server openssh-server: Installed: 1:9.0p1-1ubuntu6 Candidate: 1:9.0p1-1ubuntu6 Version table: *** 1:9.0p1-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy systemd systemd: Installed: 251.4-1ubuntu6 Candidate: 251.4-1ubuntu6 Version table: *** 251.4-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status # Instructions - Configure /etc/ssh/sshd_config to port in 22.04 - Upgrade to 22.10 with sudo do-release-upgrade -d - Accept overwriting /etc/ssh/sshd_config with the new version - Attempt to ssh into the machine # Expected behavior systemd should listen on port and start sshd. $ cat /etc/systemd/system/ssh.socket.d/addresses.conf [Socket] ListenStream= ListenStream= $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (running) since Thu 2022-09-29 02:08:56 EDT; 9min ago Until: Thu 2022-09-29 02:08:56 EDT; 9min ago Triggers: ● ssh.service Listen: [::]: (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 923us CGroup: /system.slice/ssh.socket Sep 29 02:08:56 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. # Actual behavior Port refuses any connection. Systemd fails to parse the automatically generated file: $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (listening) since Thu 2022-09-29 01:51:57 EDT; 16min ago Until: Thu 2022-09-29 01:51:57 EDT; 16min ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 982us CGroup: /system.slice/ssh.socket Sep 29 01:51:57 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. Sep 29 01:56:23 daniel-desktop2 systemd[1]: /etc/systemd/system/ssh.socket.d/addresses.conf:1: Assignment outside of section. Ignoring. $ cat /etc/systemd/system/ssh.socket.d/override.conf ListenStream= # Analysis The migration script must be missing the `[Socket]` line and the next one. sshd works after I added those two lines manually. Either the migration script never worked or systemd changed the syntax in the meantime. --- ProblemType: Bug ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 MachineType: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6 Package: systemd 251.4-1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-06rc7-generic root=UUID=29b85a8a-08f8-42be-8629-fb6e88d149d6 ro text pcie_port_pm=off resume=UUID=21d61484-fe9b-4310-9390-d5f5d17510d8 Tags: kinetic Uname: Linux 6.0.0-06rc7-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/19/2017 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30BF_M32BF_A_F_K31BF_6 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:
[Touch-packages] [Bug 1991200] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1991200/+attachment/5619904/+files/ProcEnviron.txt ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1991200 Title: apport-cli apport-collect crash AttributeError: 'bytes' object has no attribute 'fileno' Status in apport package in Ubuntu: New Bug description: apport-collect crashed. # lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 # apt-cache policy apport apport: Installed: 2.23.0-0ubuntu2 Candidate: 2.23.0-0ubuntu2 Version table: *** 2.23.0-0ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main i386 Packages 100 /var/lib/dpkg/status # Instructions 1. Run apport-collect NUMBER as root 2. Get to the point it asks before sending 3. Choose to view the report 4. Watch the crash # Expected behavior Apport-collect should stay alive and not crash with a stacktrace. # Actual behavior # apport-collect 1991199 Please open this authorization page: (REDACTED) in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Press Enter after authorizing in your browser. Package openssh not installed and no hook available, ignoring *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** It seems you have modified the contents of "/etc/systemd/logind.conf". Would you like to add the contents of it to your bug report? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): n *** It seems you have modified the contents of "/etc/systemd/sleep.conf". Would you like to add the contents of it to your bug report? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): n ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (597.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): v Traceback (most recent call last): File "/usr/bin/apport-cli", line 442, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 858, in run_argv return self.run_update_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 758, in run_update_report response = self.ui_present_report_details(allowed_to_report) File "/usr/bin/apport-cli", line 258, in ui_present_report_details self.ui_update_view() File "/usr/bin/apport-cli", line 187, in ui_update_view subprocess.run( File "/usr/lib/python3.10/subprocess.py", line 501, in run with Popen(*popenargs, **kwargs) as process: File "/usr/lib/python3.10/subprocess.py", line 835, in __init__ errread, errwrite) = self._get_handles(stdin, stdout, stderr) File "/usr/lib/python3.10/subprocess.py", line 1606, in _get_handles p2cread = stdin.fileno() AttributeError: 'bytes' object has no attribute 'fileno' --- ProblemType: Bug ApportLog: ERROR: apport (pid 42855) Thu Sep 29 00:30:05 2022: executable was modified after program start, ignoring ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:0:148:22558:2022-09-29 02:33:04.712637295 -0400:2022-09-29 02:33:04.708637298 -0400:/var/crash/_usr_bin_apport-cli.0.crash DistroRelease: Ubuntu 22.10 Package: apport 2.23.0-0ubuntu2 PackageArchitecture: all Tags: kinetic third-party-packages Uname: Linux 6.0.0-06rc7-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) UserGroups: N/A _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1991200/+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 1991200] Re: apport-cli apport-collect crash AttributeError: 'bytes' object has no attribute 'fileno'
# apport-collect 1991200 *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.8 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): v Traceback (most recent call last): File "/usr/bin/apport-cli", line 442, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 858, in run_argv return self.run_update_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 758, in run_update_report response = self.ui_present_report_details(allowed_to_report) File "/usr/bin/apport-cli", line 258, in ui_present_report_details self.ui_update_view() File "/usr/bin/apport-cli", line 187, in ui_update_view subprocess.run( File "/usr/lib/python3.10/subprocess.py", line 501, in run with Popen(*popenargs, **kwargs) as process: File "/usr/lib/python3.10/subprocess.py", line 835, in __init__ errread, errwrite) = self._get_handles(stdin, stdout, stderr) File "/usr/lib/python3.10/subprocess.py", line 1606, in _get_handles p2cread = stdin.fileno() AttributeError: 'bytes' object has no attribute 'fileno' Guess I'll have to temporarily try setting this bug to private. ** Information type changed from Public to Private ** Tags added: apport-collected kinetic third-party-packages ** Description changed: apport-collect crashed. # lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 # apt-cache policy apport apport: Installed: 2.23.0-0ubuntu2 Candidate: 2.23.0-0ubuntu2 Version table: *** 2.23.0-0ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main i386 Packages 100 /var/lib/dpkg/status # Instructions 1. Run apport-collect NUMBER as root 2. Get to the point it asks before sending 3. Choose to view the report 4. Watch the crash # Expected behavior Apport-collect should stay alive and not crash with a stacktrace. # Actual behavior # apport-collect 1991199 Please open this authorization page: (REDACTED) in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Press Enter after authorizing in your browser. Package openssh not installed and no hook available, ignoring *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** It seems you have modified the contents of "/etc/systemd/logind.conf". Would you like to add the contents of it to your bug report? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): n *** It seems you have modified the contents of "/etc/systemd/sleep.conf". Would you like to add the contents of it to your bug report? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): n ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (597.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): v Traceback (most recent call last): File "/usr/bin/apport-cli", line 442, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 858, in run_argv return self.run_update_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 758, in run_update_report response = self.ui_present_report_details(allowed_to_report) File "/usr/bin/apport-cli", line 258, in ui_present_report_details self.ui_update_view() File "/usr/bin/apport-cli", line 187, in ui_update_view subprocess.run( File "/usr/lib/python3.10/subprocess.py", line 501, in run with Popen(*popenargs, **kwargs) as process: File "/usr/lib/python3.10/subprocess.py", line 835, in __init__ errread, errwrite) = self._get_handles(stdin, stdout, stderr) File "/usr/lib/python3.10/subprocess.py", line 1606, in _get_handles p2cread = stdin.fileno() AttributeError: 'bytes' object has no attribute 'fileno' + --- + ProblemType: Bug + ApportLog: ERROR:
[Touch-packages] [Bug 1991200] [NEW] apport-cli apport-collect crash AttributeError: 'bytes' object has no attribute 'fileno'
Public bug reported: apport-collect crashed. # lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 # apt-cache policy apport apport: Installed: 2.23.0-0ubuntu2 Candidate: 2.23.0-0ubuntu2 Version table: *** 2.23.0-0ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main i386 Packages 100 /var/lib/dpkg/status # Instructions 1. Run apport-collect NUMBER as root 2. Get to the point it asks before sending 3. Choose to view the report 4. Watch the crash # Expected behavior Apport-collect should stay alive and not crash with a stacktrace. # Actual behavior # apport-collect 1991199 Please open this authorization page: (REDACTED) in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Press Enter after authorizing in your browser. Package openssh not installed and no hook available, ignoring *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** It seems you have modified the contents of "/etc/systemd/logind.conf". Would you like to add the contents of it to your bug report? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): n *** It seems you have modified the contents of "/etc/systemd/sleep.conf". Would you like to add the contents of it to your bug report? What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): n ... *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (597.4 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): v Traceback (most recent call last): File "/usr/bin/apport-cli", line 442, in if not app.run_argv(): File "/usr/lib/python3/dist-packages/apport/ui.py", line 858, in run_argv return self.run_update_report() File "/usr/lib/python3/dist-packages/apport/ui.py", line 758, in run_update_report response = self.ui_present_report_details(allowed_to_report) File "/usr/bin/apport-cli", line 258, in ui_present_report_details self.ui_update_view() File "/usr/bin/apport-cli", line 187, in ui_update_view subprocess.run( File "/usr/lib/python3.10/subprocess.py", line 501, in run with Popen(*popenargs, **kwargs) as process: File "/usr/lib/python3.10/subprocess.py", line 835, in __init__ errread, errwrite) = self._get_handles(stdin, stdout, stderr) File "/usr/lib/python3.10/subprocess.py", line 1606, in _get_handles p2cread = stdin.fileno() AttributeError: 'bytes' object has no attribute 'fileno' --- ProblemType: Bug ApportLog: ERROR: apport (pid 42855) Thu Sep 29 00:30:05 2022: executable was modified after program start, ignoring ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashReports: 640:0:148:22558:2022-09-29 02:33:04.712637295 -0400:2022-09-29 02:33:04.708637298 -0400:/var/crash/_usr_bin_apport-cli.0.crash DistroRelease: Ubuntu 22.10 Package: apport 2.23.0-0ubuntu2 PackageArchitecture: all Tags: kinetic third-party-packages Uname: Linux 6.0.0-06rc7-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) UserGroups: N/A _MarkForUpload: True ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected kinetic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1991200 Title: apport-cli apport-collect crash AttributeError: 'bytes' object has no attribute 'fileno' Status in apport package in Ubuntu: New Bug description: apport-collect crashed. # lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 # apt-cache policy apport apport: Installed: 2.23.0-0ubuntu2 Candidate: 2.23.0-0ubuntu2 Version table: *** 2.23.0-0ubuntu2 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main i386 Packages 100 /var/lib/dpkg/status # Instructions 1. Run apport-collect NUMBER as root 2. Get to the point it asks before sending 3. Choose to view the report 4. Watch the crash # Expected behavior Apport-collect should stay alive and not crash with a stacktrace. # Actual behavior # apport-collect 1991199 Please open this authorization page: (REDACTED) in your browser.
[Touch-packages] [Bug 1990863] Re: conversion from sshd service to socket is too bumpy
> what happens in terms of the migration from ssh service to socket when the user opts to install the vendor version of sshd_config as a result of the merge conflict I upgraded today 2022-09-29 and installing the vendor version is not intended to break the port settings because there's a migration script. I commented out all Port= lines and both the first ssh connection and at least the second connection work. > listen.conf I don't know of this `listen.conf` you are talking about. > You could migrate the address and port settings from sshd_config There is supposed to be an automatic migration. Unfortunately it generates garbage and needs two lines to be manually added: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1991199 -- 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/1990863 Title: conversion from sshd service to socket is too bumpy Status in openssh package in Ubuntu: New Bug description: During upgrade from Jammy to Kinetic, I get asked what to do because my sshd_config has been modified. I say to do a 3-way merge. It says 3-way merge fails. I shrug, figure I'll just restore my customizations with Ansible after the upgrade like I always do, and tell it to use the vendor version of the file. This removes my custom Port settings, so they are not migrated over to the ssh.socket settings like https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation- ubuntu-22-10-and-later/30189 says they would be. I subsequently run my Ansible which restores the customizations and enables the ssh service, but now ssh.service and ssh.socket are enabled at the same time, sshd isn't listening on my specified ports, and everything is a mess. I've never used socket-based activation before and have no idea how to configure it so now I have to go reading man pages, Googling all over the place, and generally struggle to figure out what the heck is going wrong. I don't know what the right answer is here, but I really feel like some effort needs to be put into figuring out a smoother transition for people who are upgrading to Kinetic. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: openssh-server 1:9.0p1-1ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 11:41:58 2022 InstallationDate: Installed on 2019-08-16 (1136 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: openssh UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863/+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 1991199] [NEW] sshd port migration is missing two config lines from jammy to kinetic
Public bug reported: The automatic migration script from jammy to kinetic generates a invalid file for sshd that systemd refuses to read. Manual addition of two lines is required for a functional sshd with a custom port. This bug can be considered the opposite of https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They want to have sshd keep managing the socket while I want to try letting systemd do that. $ lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 $ apt-cache policy openssh-server openssh-server: Installed: 1:9.0p1-1ubuntu6 Candidate: 1:9.0p1-1ubuntu6 Version table: *** 1:9.0p1-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy systemd systemd: Installed: 251.4-1ubuntu6 Candidate: 251.4-1ubuntu6 Version table: *** 251.4-1ubuntu6 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status # Instructions - Configure /etc/ssh/sshd_config to port in 22.04 - Upgrade to 22.10 with sudo do-release-upgrade -d - Accept overwriting /etc/ssh/sshd_config with the new version - Attempt to ssh into the machine # Expected behavior systemd should listen on port and start sshd. $ cat /etc/systemd/system/ssh.socket.d/addresses.conf [Socket] ListenStream= ListenStream= $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (running) since Thu 2022-09-29 02:08:56 EDT; 9min ago Until: Thu 2022-09-29 02:08:56 EDT; 9min ago Triggers: ● ssh.service Listen: [::]: (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 923us CGroup: /system.slice/ssh.socket Sep 29 02:08:56 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. # Actual behavior Port refuses any connection. Systemd fails to parse the automatically generated file: $ systemctl status ssh.socket ● ssh.socket - OpenBSD Secure Shell server socket Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled) Drop-In: /etc/systemd/system/ssh.socket.d └─addresses.conf Active: active (listening) since Thu 2022-09-29 01:51:57 EDT; 16min ago Until: Thu 2022-09-29 01:51:57 EDT; 16min ago Triggers: ● ssh.service Listen: [::]:22 (Stream) Tasks: 0 (limit: 19047) Memory: 8.0K CPU: 982us CGroup: /system.slice/ssh.socket Sep 29 01:51:57 daniel-desktop2 systemd[1]: Listening on OpenBSD Secure Shell server socket. Sep 29 01:56:23 daniel-desktop2 systemd[1]: /etc/systemd/system/ssh.socket.d/addresses.conf:1: Assignment outside of section. Ignoring. $ cat /etc/systemd/system/ssh.socket.d/override.conf ListenStream= # Analysis The migration script must be missing the `[Socket]` line and the next one. sshd works after I added those two lines manually. Either the migration script never worked or systemd changed the syntax in the meantime. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: The automatic migration script from jammy to kinetic generates a invalid file for sshd that systemd refuses to read. Manual addition of two lines is required for a functional sshd with a custom port. + + This bug can be considered the opposite of + https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863 . They + want to have sshd keep managing the socket while I want to try letting + systemd do that. $ lsb_release -rd Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 $ apt-cache policy openssh-server openssh-server: - Installed: 1:9.0p1-1ubuntu6 - Candidate: 1:9.0p1-1ubuntu6 - Version table: - *** 1:9.0p1-1ubuntu6 500 - 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:9.0p1-1ubuntu6 + Candidate: 1:9.0p1-1ubuntu6 + Version table: + *** 1:9.0p1-1ubuntu6 500 + 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages + 100 /var/lib/dpkg/status $ apt-cache policy systemd systemd: - Installed: 251.4-1ubuntu6 - Candidate: 251.4-1ubuntu6 - Version table: - *** 251.4-1ubuntu6 500 - 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu kinetic/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 251.4-1ubuntu6 + Candidate: 251.4-1ubuntu6 + Version table: + *** 251.4-1ubuntu6 500 + 500
[Touch-packages] [Bug 1921482] [NEW] msgcat --color=test no longer works
Public bug reported: `msgcat --color=test` no longer prints anything. I rely on that package to determine what colors a terminal supports, as does anyone using https://askubuntu.com/a/1044802/1004020 . 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy gettext gettext: Installed: 0.21-3ubuntu2 Candidate: 0.21-3ubuntu2 Version table: *** 0.21-3ubuntu2 500 500 http://archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen It should work and the output should be the same as in 20.10: $ msgcat --color=test Colors (foreground/background): |black |blue |green |cyan |red|magenta|yellow |white |default black | Words | Words | Words | Words | Words | Words | Words | Words | Words blue | Words | Words | Words | Words | Words | Words | Words | Words | Words green | Words | Words | Words | Words | Words | Words | Words | Words | Words cyan | Words | Words | Words | Words | Words | Words | Words | Words | Words red| Words | Words | Words | Words | Words | Words | Words | Words | Words magenta| Words | Words | Words | Words | Words | Words | Words | Words | Words yellow | Words | Words | Words | Words | Words | Words | Words | Words | Words white | Words | Words | Words | Words | Words | Words | Words | Words | Words default| Words | Words | Words | Words | Words | Words | Words | Words | Words Colors (hue/saturation): red: yellow: green:
[Touch-packages] [Bug 1858090] Re: Surface Type Cover not detected by dpkg-reconfigure keyboard-configuration
** Patch added: "keyboard-configuration.config.patch" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+attachment/5317045/+files/keyboard-configuration.config.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] Re: Surface Type Cover not detected by dpkg-reconfigure keyboard-configuration
After making the keyboard detection search pattern for /proc/bus/input/devices more generic, dpkg-reconfigure keyboard- configuration works. The patch is attached. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] Re: Surface Type Cover not detected by dpkg-reconfigure keyboard-configuration
Analysis:
This is caused by keyboard-configuration trying and failing to detect a
keyboard.
It detects my USB keyboard using InterfaceClass 03, InterfaceSubClass 01, and
InterfaceProtocol 01 in /sys/bus/usb/devices/ .
It detects the built-in keyboard on my other computer using "AT Set" in
/proc/bus/input/devices .
However it does not detect the Surface Type Keyboard ('N: Name="Microsoft
Surface Type Cover Keyboard"') in /proc/bus/input/devices .
The problem is in the keyboard_present() function of line 36230 of
/var/lib/dpkg/info/keyboard-configuration.config .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1858090
Title:
Surface Type Cover not detected by dpkg-reconfigure keyboard-
configuration
Status in console-setup package in Ubuntu:
New
Bug description:
keyboard-configuration does not detect a Surface Type Cover as a
keyboard during dpkg-reconfigure. This causes it to skip the dialog
and prevents one from configuring the Type Cover.
$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10
$ apt-cache policy keyboard-configuration
keyboard-configuration:
Installed: 1.191ubuntu3
Candidate: 1.191ubuntu3
Version table:
*** 1.191ubuntu3 500
500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
What I expected to happen:
# dpkg-reconfigure keyboard-configuration
[I get prompted with an interactive dialog asking me to configure the
keyboard]
What happened instead:
# dpkg-reconfigure keyboard-configuration
Your console font configuration will be updated the next time your system
boots. If you want to update it now, run 'setupcon' from a virtual console.
update-initramfs: deferring update (trigger activated)
[...]
[The expected dialog doesn't show up, and it goes straight to
rebuilding the boot image]
Workaround:
Plug in a standalone USB Keyboard before running the command.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: KDE
DistroRelease: Ubuntu 19.10
Package: console-setup 1.191ubuntu3
PackageArchitecture: all
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Tags: eoan
Uname: Linux 5.3.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: dialout kvm plugdev sudo systemd-journal wireshark
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1858090/+attachment/5317043/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] ConsoleSetup.txt
apport information ** Attachment added: "ConsoleSetup.txt" https://bugs.launchpad.net/bugs/1858090/+attachment/5317040/+files/ConsoleSetup.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1858090/+attachment/5317044/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] Keyboard.txt
apport information ** Attachment added: "Keyboard.txt" https://bugs.launchpad.net/bugs/1858090/+attachment/5317042/+files/Keyboard.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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 1858090] [NEW] Surface Type Cover not detected by dpkg-reconfigure keyboard-configuration
Public bug reported: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected eoan ** Tags added: apport-collected eoan ** Description changed: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 19.10 + Package: console-setup 1.191ubuntu3 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + Tags: eoan + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: dialout kvm plugdev sudo systemd-journal wireshark + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion:
[Touch-packages] [Bug 1858090] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1858090/+attachment/5317041/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1858090 Title: Surface Type Cover not detected by dpkg-reconfigure keyboard- configuration Status in console-setup package in Ubuntu: New Bug description: keyboard-configuration does not detect a Surface Type Cover as a keyboard during dpkg-reconfigure. This causes it to skip the dialog and prevents one from configuring the Type Cover. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.191ubuntu3 Candidate: 1.191ubuntu3 Version table: *** 1.191ubuntu3 500 500 http://ubuntu.mirror.rafal.ca/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status What I expected to happen: # dpkg-reconfigure keyboard-configuration [I get prompted with an interactive dialog asking me to configure the keyboard] What happened instead: # dpkg-reconfigure keyboard-configuration Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) [...] [The expected dialog doesn't show up, and it goes straight to rebuilding the boot image] Workaround: Plug in a standalone USB Keyboard before running the command. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dialout kvm plugdev sudo systemd-journal wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1858090/+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
