Re: [Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
if by non graphical shell you mean a shell you arrive at via a local login,
I would not expect the bug to be present. The bug, as I understand it,
happens when the login process (not the UI) skips some step.
I can't imagine you would encounter this in any "official" login, such as
to a virtual terminal, or via ssh. Because I think the bug happens in the
login process and not the session start process, I have to predict that
using wayland vs xorg sessions would make no difference. \
It is interesting that xrdp works. I don't know how xrdp works as far as
starting sessions goes. But it is actively maintained unlike x2go so it
seems likely to me that it has "modern" log in methods so it may be fine.
I use nomachine workstation server and the most recent version release
notes specifically mention changes to the login process with respect to PAM
handling.
The systemd experts who have looked at this bug, including correspondence
I've had with them outside of this bug report, indicate that the problem
with x2go and nomachine look like a missing PAM step in the login process.
I will upgrade my server soon to check it out
regards
TIm
On Tue, 7 Nov 2023 at 05:16, Richard Brooksby <1951...@bugs.launchpad.net>
wrote:
> Thank you for the clarifications, Tim. For what it's worth, my Ubuntu
> 22 non-graphical shell *does* have DBUS_SESSION_BUS_ADDRESS to the same
> value that appears in a Wayland session
> ("unix:path=/run/user/1000/bus"). So the bug you mention being exposed
> does not occur for me.
>
> It is also set correctly for an RDP (remote desktop) login to a headless
> Ubuntu 22 machine with xrdp installed to provide the session. The
> Firefox snap starts happily in that session.
>
> A local X session started with `startx` also produces a session in which
> the Firefox snap will run.
>
> The only session that breaks Firefox for me is starting Wayland using
> `XDG_SESSION_TYPE=wayland dbus-run-session gnome-session`. I have not
> found any other way to get a Wayland session from the command line.
>
> It's possible this is all evidence of this bug being fixed in Ubuntu 22,
> and all I have is a problem with starting Wayland correctly.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1951491
>
> Title:
> Can't run snaps: .slice/session-1.scope is not a snap cgroup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions
>
>
--
Tim Richardson
--
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/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
Status in X2Go:
New
Status in Xpra Terminal Server:
New
Status in snapd package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Incomplete
Status in x2goserver package in Ubuntu:
Confirmed
Status in snapd package in Debian:
New
Status in snapd package in Fedora:
New
Bug description:
I just upgraded from hirsute to impish using do-release-upgrade. On
the upgraded system, I can't run either firefox or chromium (both of
which worked fine under hirsute). Both fail with:
/user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
NNN is my uid
With firefox, I was able to fix the problem with:
snap remove --purge firefox
apt purge firefox
apt install firefox
Now firefox works. But I tried the same thing substituting chromium-
browser for firefox, and it didn't help: chromium fails with the same
error message.
I guess there must be something left over from the hirsute version of
snapd that isn't getting noticed or cleared by the impish version?
Someone suggested this might be related to bug 1850667, but that bug
is marked fixed as of a couple months ago, and I just did this upgrade
today. Also, it doesn't mention the error message I'm seeing.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: snapd 2.53+21.10ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Nov 18 18:12:45 2021
InstallationDate: Installed on 2020-04-29 (568 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: snapd
UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+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 2042902] [NEW] ucm2: soundwire: add rt713 SDCA device
Public bug reported: [ Impact ] Affects devices that use SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. [ Test Plan ] In progress ** Affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Package changed: pulseaudio (Ubuntu) => alsa-ucm-conf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in alsa-ucm-conf package in Ubuntu: New Bug description: [ Impact ] Affects devices that use SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. [ Test Plan ] In progress To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2042902/+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 2042892] Re: Desktop Dock couldn't be slided by mouse.
** Tags added: desktop dock -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2042892 Title: Desktop Dock couldn't be slided by mouse. Status in ubuntu-meta package in Ubuntu: New Bug description: Desktop Dock couldn't be slid by mouse. And the pagination of 'Show Apps'(the 'DOT') are real small, could it be designed as more styles? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop 1.524 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 11:51:32 2023 InstallationDate: Installed on 2023-10-26 (12 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to mantic on 2023-10-26 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2042892/+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 2042892] Re: Desktop Dock couldn't be slided by mouse.
** Attachment added: "Screenshot from 2023-11-07 12-53-16.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2042892/+attachment/5716694/+files/Screenshot%20from%202023-11-07%2012-53-16.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2042892 Title: Desktop Dock couldn't be slided by mouse. Status in ubuntu-meta package in Ubuntu: New Bug description: Desktop Dock couldn't be slid by mouse. And the pagination of 'Show Apps'(the 'DOT') are real small, could it be designed as more styles? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop 1.524 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 11:51:32 2023 InstallationDate: Installed on 2023-10-26 (12 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to mantic on 2023-10-26 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2042892/+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 2042892] Re: Desktop Dock couldn't be slided by mouse.
** Attachment added: "Screenshot from 2023-11-07 11-36-35.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2042892/+attachment/5716693/+files/Screenshot%20from%202023-11-07%2011-36-35.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2042892 Title: Desktop Dock couldn't be slided by mouse. Status in ubuntu-meta package in Ubuntu: New Bug description: Desktop Dock couldn't be slid by mouse. And the pagination of 'Show Apps'(the 'DOT') are real small, could it be designed as more styles? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop 1.524 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 11:51:32 2023 InstallationDate: Installed on 2023-10-26 (12 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to mantic on 2023-10-26 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2042892/+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 2042892] [NEW] Desktop Dock couldn't be slided by mouse.
Public bug reported: Desktop Dock couldn't be slid by mouse. And the pagination of 'Show Apps'(the 'DOT') are real small, could it be designed as more styles? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop 1.524 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 11:51:32 2023 InstallationDate: Installed on 2023-10-26 (12 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to mantic on 2023-10-26 (12 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2042892 Title: Desktop Dock couldn't be slided by mouse. Status in ubuntu-meta package in Ubuntu: New Bug description: Desktop Dock couldn't be slid by mouse. And the pagination of 'Show Apps'(the 'DOT') are real small, could it be designed as more styles? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop 1.524 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 11:51:32 2023 InstallationDate: Installed on 2023-10-26 (12 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to mantic on 2023-10-26 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2042892/+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 2042866] [NEW] Warning: Permissions for /etc/netplan/01-use-network-manager.yaml are too open. Netplan configuration should NOT be accessible by others.
Public bug reported: This warning is shown in the system journal (during boot): nov 06 17:15:23 fpgrpi generate[840]: Permissions for /etc/netplan/01-use-network-manager.yaml are too open. Netplan configuration should NOT be accessible by others. The file /etc/netplan/01-use-network-manager.yaml came from the package ubuntu-raspi-settings-desktop and its post install permissions are -rw-r --r-- (group and others readable). A simple workaround is to remove the file read permission for group and others, as suggested, using this command: sudo chmod 600 /etc/netplan/01-use-network-manager.yaml Additional info: OS: Ubuntu 23.10 aarch64 (Mantic) Host: Raspberry Pi 4 Model B Rev 1.4 Kernel: 6.5.0-1006-raspi # lsb_release -r No LSB modules are available. Release:23.10 # apt-cache policy ubuntu-raspi-settings-desktop ubuntu-raspi-settings-desktop: Instalados: 23.10.6 Candidato: 23.10.6 Tabla de versión: *** 23.10.6 500 500 http://ports.ubuntu.com/ubuntu-ports mantic/main arm64 Packages 100 /var/lib/dpkg/status ** Affects: ubuntu-raspi-settings (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu-settings (Ubuntu) => ubuntu-raspi-settings (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2042866 Title: Warning: Permissions for /etc/netplan/01-use-network-manager.yaml are too open. Netplan configuration should NOT be accessible by others. Status in ubuntu-raspi-settings package in Ubuntu: New Bug description: This warning is shown in the system journal (during boot): nov 06 17:15:23 fpgrpi generate[840]: Permissions for /etc/netplan/01-use-network-manager.yaml are too open. Netplan configuration should NOT be accessible by others. The file /etc/netplan/01-use-network-manager.yaml came from the package ubuntu-raspi-settings-desktop and its post install permissions are -rw-r--r-- (group and others readable). A simple workaround is to remove the file read permission for group and others, as suggested, using this command: sudo chmod 600 /etc/netplan/01-use-network-manager.yaml Additional info: OS: Ubuntu 23.10 aarch64 (Mantic) Host: Raspberry Pi 4 Model B Rev 1.4 Kernel: 6.5.0-1006-raspi # lsb_release -r No LSB modules are available. Release: 23.10 # apt-cache policy ubuntu-raspi-settings-desktop ubuntu-raspi-settings-desktop: Instalados: 23.10.6 Candidato: 23.10.6 Tabla de versión: *** 23.10.6 500 500 http://ports.ubuntu.com/ubuntu-ports mantic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2042866/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup
Thank you for the clarifications, Tim. For what it's worth, my Ubuntu
22 non-graphical shell *does* have DBUS_SESSION_BUS_ADDRESS to the same
value that appears in a Wayland session
("unix:path=/run/user/1000/bus"). So the bug you mention being exposed
does not occur for me.
It is also set correctly for an RDP (remote desktop) login to a headless
Ubuntu 22 machine with xrdp installed to provide the session. The
Firefox snap starts happily in that session.
A local X session started with `startx` also produces a session in which
the Firefox snap will run.
The only session that breaks Firefox for me is starting Wayland using
`XDG_SESSION_TYPE=wayland dbus-run-session gnome-session`. I have not
found any other way to get a Wayland session from the command line.
It's possible this is all evidence of this bug being fixed in Ubuntu 22,
and all I have is a problem with starting Wayland correctly.
--
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/1951491
Title:
Can't run snaps: .slice/session-1.scope is not a snap cgroup
Status in X2Go:
New
Status in Xpra Terminal Server:
New
Status in snapd package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Incomplete
Status in x2goserver package in Ubuntu:
Confirmed
Status in snapd package in Debian:
New
Status in snapd package in Fedora:
New
Bug description:
I just upgraded from hirsute to impish using do-release-upgrade. On
the upgraded system, I can't run either firefox or chromium (both of
which worked fine under hirsute). Both fail with:
/user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
NNN is my uid
With firefox, I was able to fix the problem with:
snap remove --purge firefox
apt purge firefox
apt install firefox
Now firefox works. But I tried the same thing substituting chromium-
browser for firefox, and it didn't help: chromium fails with the same
error message.
I guess there must be something left over from the hirsute version of
snapd that isn't getting noticed or cleared by the impish version?
Someone suggested this might be related to bug 1850667, but that bug
is marked fixed as of a couple months ago, and I just did this upgrade
today. Also, it doesn't mention the error message I'm seeing.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: snapd 2.53+21.10ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Nov 18 18:12:45 2021
InstallationDate: Installed on 2020-04-29 (568 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: snapd
UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+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 1986619] Re: Fail to install base-passwd
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1986619 Title: Fail to install base-passwd Status in base-passwd package in Ubuntu: Confirmed Bug description: /home/frank/Downloads# dpkg -i base-passwd_3.5.52build1_amd64.deb (Reading database ... 236425 files and directories currently installed.) Preparing to unpack base-passwd_3.5.52build1_amd64.deb ... Unpacking base-passwd (3.5.52build1) over (3.5.52build1) ... Setting up base-passwd (3.5.52build1) ... Changing home-directory of irc from /var/run/ircd to /run/ircd 1 changes have been made, rewriting files Writing passwd-file to /etc/passwd Failed to open passwd-file /etc/passwd.upwd-write for writing: Permission denied dpkg: error processing package base-passwd (--install): installed base-passwd package post-installation script subprocess returned error exit status 4 Errors were encountered while processing: base-passwd root@CNQDSX:/home/frank/Downloads# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1986619/+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 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs
This is the relevant dracut commit for spi_pxa2xx_platform:
https://github.com/dracutdevs/dracut/commit/df381b7e0cd95f78e40ac70f0f3c96a2fa8dd189
```
$ modprobe --show-depends spi_pxa2xx_platform
insmod /lib/modules/6.5.0-10-generic/kernel/drivers/dma/dw/dw_dmac_core.ko.zst
insmod /lib/modules/6.5.0-10-generic/kernel/drivers/dma/dw/dw_dmac.ko.zst
insmod
/lib/modules/6.5.0-10-generic/kernel/drivers/spi/spi-pxa2xx-platform.ko.zst
```
intel_lpss_pci or mfd (from mfd/intel_lpss_pci path) are not directly
mentioned in dracut. Neither does `dracut_instmods -o -s
"${_blockfuncs}" "=drivers"` install intel_lpss_pci.
dracut does not seem to install intel_lpss_pci:
```
$ schroot-wrapper -p dracut,linux-image-generic,systemd-sysv -c mantic -u root
[...]
(mantic)root@host:~# lsinitrd /boot/initrd.img-6.5.0-10-generic | grep
intel_lpss_pci
(mantic)root@host:~#
```
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2042710
Title:
Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1)
due to missing kernel modules in initramfs
Status in initramfs-tools package in Ubuntu:
Triaged
Status in initramfs-tools source package in Mantic:
New
Bug description:
I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root
partition, which I decrypt via passphrase during boot, at the "Please
unlock disk nvme0n1p4_crypt" prompt.
Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10
"Mantic", the built-in keyboard doesn't work for entering the
passphrase.
Quickest workaround: plug in a USB keyboard for entering the
passphrase.
Workaround: add the following modules to "/etc/initramfs-
tools/modules":
spi_pxa2xx_platform
intel_lpss_pci
... then "sudo update-initramfs -u".
I found that both kernel modules were required to get the keyboard
recognised in initramfs.
I did a bit of digging into what changed for 23.10. It could
potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do
not install ARM/RISCV specific modules on other architectures".
I had a look into how dracut handles it. Turns out that they
specifically include "spi_pxa2xx_platform" after reporting a similar
bug report in Fedora:
https://bugzilla.redhat.com/show_bug.cgi?id=2166209
I don't know how (if?) they handle the 2nd module, "intel_lpss_pci".
Anyway, I don't need an immediate fix since the workaround works for
me. Just posting this for further investigation, and for any other
MacBook Pro users in the same situation. Thanks for working on Ubuntu,
I think you're all amazing!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2041789] Re: amd 7840, ubuntu 22.04, display goes to wrong
*** This bug is a duplicate of bug 2042054 *** https://bugs.launchpad.net/bugs/2042054 ** This bug has been marked a duplicate of bug 2042054 22.04.3, zen 4 7840, screen turn white exception -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2041789 Title: amd 7840, ubuntu 22.04, display goes to wrong Status in xorg package in Ubuntu: New Bug description: release version: Ubuntu 22.04.3 LTS kernel: linux-oem-22.04d, others just the default of the official release, with update the screen display goes to white or black or full of stripe, but I can still move the pointer. I can restore the display by lock and unlock the screen. there is a photo attached. I have test the default kernel or linux-oem-22.04c linux-oem-22.04d, the problem dont go away. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-1004.4-oem 6.5.3 Uname: Linux 6.5.0-1004-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 13:16:07 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3818] InstallationDate: Installed on 2023-10-30 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: LENOVO 83AM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1004-oem root=UUID=ef93c72f-6025-43c4-820e-64cc8b1a9028 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2023 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: MKCN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76479 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: XiaoXinPro 14 APH8 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrMKCN27WW:bd09/08/2023:br1.27:efr1.27:svnLENOVO:pn83AM:pvrXiaoXinPro14APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76479WIN:cvnLENOVO:ct10:cvrXiaoXinPro14APH8:skuLENOVO_MT_83AM_BU_idea_FM_XiaoXinPro14APH8: dmi.product.family: XiaoXinPro 14 APH8 dmi.product.name: 83AM dmi.product.sku: LENOVO_MT_83AM_BU_idea_FM_XiaoXinPro 14 APH8 dmi.product.version: XiaoXinPro 14 APH8 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2041789/+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 2042367] Re: eglinfo device platform eglInitialize failed
I can't find an obvious explanation for this. Did you at some point use a PPA for your Mesa packages in the past? ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2042367 Title: eglinfo device platform eglInitialize failed Status in mesa package in Ubuntu: New Bug description: On an Intel NUC13RNGi9 system with 13900K processor with integrated Intel UHD 770 Graphics, the command "eglinfo" fails to initialize the Device platform: $ eglinfo ... Device platform: eglinfo: eglInitialize failed The other platforms (X11, Wayland, GBM) initialize. The reason I am reporting is I'm trying to fix an issue in my system where: EGLDisplay display = eglGetDisplay(EGL_DEFAULT_DISPLAY) is returning EGL_NO_DISPLAY on my system, and I think it's due to the Device platform failing to initialize. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 1 09:42:40 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:3033] InstallationDate: Installed on 2023-10-30 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Intel(R) Client Systems NUC13RNGi9 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2023 dmi.bios.release: 5.27 dmi.bios.vendor: Intel Corp. dmi.bios.version: SBRPL579.0056.2023.0204.0233 dmi.board.name: NUC13SBBi9 dmi.board.vendor: Intel Corporation dmi.board.version: M58736-304 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 44.0 dmi.modalias: dmi:bvnIntelCorp.:bvrSBRPL579.0056.2023.0204.0233:bd02/04/2023:br5.27:efr44.0:svnIntel(R)ClientSystems:pnNUC13RNGi9:pvrM89920-304:rvnIntelCorporation:rnNUC13SBBi9:rvrM58736-304:cvnIntelCorporation:ct35:cvr2.0:skuRNUC13RNGi9: dmi.product.family: RN dmi.product.name: NUC13RNGi9 dmi.product.sku: RNUC13RNGi9 dmi.product.version: M89920-304 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2042367/+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 2042549] Re: Xorg crash
Indeed it looks like Xwayland died due to problems in the nouveau kernel driver. Please consider using an official Nvidia driver instead, via the Additional Drivers app. ** Tags added: nouveau ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** Summary changed: - Xorg crash + [nouveau] Xwayland crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2042549 Title: [nouveau] Xwayland crash Status in linux-hwe-6.2 package in Ubuntu: New Bug description: Have a constant random crashes of Xwayland on almost idle PC. Never had any GUI crash issues with 20.04 on the exactly same hardware (same pc). As a result all applications are killed and work is not saved... [146226.831803] nouveau :01:00.0: gr: TRAP ch 2 [00ffe45000 Xwayland[3977]] [146226.831818] nouveau :01:00.0: gr: GPC0/TPC0/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831825] nouveau :01:00.0: gr: GPC0/TPC0/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b020020 [] [146226.831833] nouveau :01:00.0: gr: GPC0/TPC1/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831838] nouveau :01:00.0: gr: GPC0/TPC1/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b060020 [] [146226.831844] nouveau :01:00.0: gr: GPC0/TPC2/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b050020 [] [146226.831849] nouveau :01:00.0: gr: GPC0/TPC2/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b030020 [] [146226.831857] nouveau :01:00.0: gr: GPC1/TPC0/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b060020 [] [146226.831862] nouveau :01:00.0: gr: GPC1/TPC0/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b030020 [] [146226.831870] nouveau :01:00.0: gr: GPC1/TPC1/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831875] nouveau :01:00.0: gr: GPC1/TPC1/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831880] nouveau :01:00.0: gr: GPC1/TPC2/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b050020 [] [146226.831885] nouveau :01:00.0: gr: GPC1/TPC2/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b060020 [] [146226.831894] nouveau :01:00.0: gr: GPC2/TPC0/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831899] nouveau :01:00.0: gr: GPC2/TPC0/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b010020 [] [146226.831906] nouveau :01:00.0: gr: GPC2/TPC1/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b050020 [] [146226.831912] nouveau :01:00.0: gr: GPC2/TPC1/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831917] nouveau :01:00.0: gr: GPC2/TPC2/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b050020 [] [146226.831922] nouveau :01:00.0: gr: GPC2/TPC2/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b060020 [] [146226.831929] nouveau :01:00.0: gr: GPC2/TPC3/SM0 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b040020 [] [146226.831935] nouveau :01:00.0: gr: GPC2/TPC3/SM1 trap: global 0004 [MULTIPLE_WARP_ERRORS] warp b060020 [] [146226.831967] nouveau :01:00.0: fifo: fault 00 [VIRT_READ] at 0be02000 engine 40 [gr] client 01 [GPC0/T1_1] reason 00 [PDE] on channel 2 [00ffe45000 Xwayland[3977]] [146226.831971] nouveau :01:00.0: fifo:00:0002:[Xwayland[3977]] rc scheduled [146226.831972] nouveau :01:00.0: fifo:00: rc scheduled [146226.831981] nouveau :01:00.0: fifo:00:0002:0002:[Xwayland[3977]] errored - disabling channel [146226.831985] nouveau :01:00.0: Xwayland[3977]: channel 2 killed! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 2 12:22:56 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU116 [GeForce GTX 1650 SUPER] [1043:874b] InstallationDate: Installed on 2023-01-15 (290 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=81faac01-c5d9-4543-8547-d6a0cbee36fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log
[Touch-packages] [Bug 2042708] Re: Monitor preferences isn't fluid after 3rd monitor plugged in
** Package changed: xorg (Ubuntu) => ubuntu-mate-settings (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042708
Title:
Monitor preferences isn't fluid after 3rd monitor plugged in
Status in ubuntu-mate-settings package in Ubuntu:
New
Bug description:
I have just upgraded from dual monitors by adding one up now up to
three.
Detecting the monitor went ok. However recalibration messed up my
screen positions.
Another issue is that when attempting to recreate physical setup under
"monitor preferences" isn't very friendly. Read: you need to battle
with it.
By "battle with it" I mean that you cannot just choose any monitor and
flip it over per it's physical position. In my case I was able to
replicate my setup after having dragged the right-most monitor instead
of the center one. As moving the center one brought hell in the
interface.
By "hell in the interface" I mean that the flow of the monitors wasn't
easy. It is impossible to simply drag and drop the monitor wherever
but instead it will move down into some impossible position and REFUSE
to go back up, or worst, to it's original place.
Before plugging in the 3rd monitor I had a full workspace displayed in
the regular left/right format.
After plugging in my 3rd monitor that workspace had been separated and
broken. So instead of dragging the mouse from the left monitor to the
right one as regularly I had to access it from the left side.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Nov 3 23:47:50 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X /
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (203 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (21 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.cron.daily.apport: [deleted]
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/2042708/+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 2042710] Re: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14, 1) due to missing kernel modules in initramfs
Thank you for taking the time to report this bug and helping to make Ubuntu better. You did a great job of investigating it. Commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 and we should do the same as dracut did. ** Tags added: foundations-todo ** Changed in: initramfs-tools (Ubuntu) Status: New => Triaged ** Also affects: initramfs-tools (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Benjamin Drung (bdrung) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2042710 Title: Can't enter cryptsetup password on MacBook Pro 2017 (MacBookPro14,1) due to missing kernel modules in initramfs Status in initramfs-tools package in Ubuntu: Triaged Status in initramfs-tools source package in Mantic: New Bug description: I have a MacBook Pro 2017 (MacBookPro14,1) with an encrypted root partition, which I decrypt via passphrase during boot, at the "Please unlock disk nvme0n1p4_crypt" prompt. Using 23.04 "Lunar" this worked fine. However after upgrading to 23.10 "Mantic", the built-in keyboard doesn't work for entering the passphrase. Quickest workaround: plug in a USB keyboard for entering the passphrase. Workaround: add the following modules to "/etc/initramfs- tools/modules": spi_pxa2xx_platform intel_lpss_pci ... then "sudo update-initramfs -u". I found that both kernel modules were required to get the keyboard recognised in initramfs. I did a bit of digging into what changed for 23.10. It could potentially (?) be commit 2df78bbb143884b9601a32608e12e43d40ccb0b0 "Do not install ARM/RISCV specific modules on other architectures". I had a look into how dracut handles it. Turns out that they specifically include "spi_pxa2xx_platform" after reporting a similar bug report in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=2166209 I don't know how (if?) they handle the 2nd module, "intel_lpss_pci". Anyway, I don't need an immediate fix since the workaround works for me. Just posting this for further investigation, and for any other MacBook Pro users in the same situation. Thanks for working on Ubuntu, I think you're all amazing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2042710/+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 2042711] Re: Weird "system restart required" screen placement
** Package changed: xorg (Ubuntu) => mate-panel (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042711
Title:
Weird "system restart required" screen placement
Status in mate-panel package in Ubuntu:
New
Bug description:
After upgrading from 23.04 to 23.10 it now appears that what I assume
to be the front-end of apt displays a button at the top with what
looks like a WORLD HEALTH ORGANIZATION logo.
The only indicator that this is related to apt is only when hovering
the mouse cursor over any portion of this blue button will say that a
reboot is required.
I have this problem on 2 systems with the same exact upgrade history
path.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog:
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Sat Nov 4 00:15:10 2023
DistUpgraded: 2023-10-13 19:39:05,380 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X /
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
InstallationDate: Installed on 2023-04-14 (203 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/vgubuntu--mate-root ro ipv6.disable=1 pcie_aspm=off
ipv6.disable=1 pcie_aspm=off
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (21 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6063
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr6063:bd03/13/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/2042711/+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 2042729] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.
Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Summary changed:
- Xorg freeze
+ gnome-shell freeze
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042729
Title:
gnome-shell freeze
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Computer unresponsive after closing laptop screen and reopening. GDM
screen does not appear to login, just see contents of the X session
before i closed the lid. mouse moves and hardware buttons (mute, caps
lock etc) are responsive with LEDs. Have to hard reboot to login and
use computer
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 4 15:33:14 2023
DistUpgraded: 2023-11-02 15:19:38,871 DEBUG 'libkf5itemviews5' scheduled for
remove but not safe to remove, skipping
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if
00 [VGA controller])
Subsystem: Lenovo CoffeeLake-H GT2 [UHD Graphics 630] [17aa:229f]
NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
InstallationDate: Installed on 2023-05-24 (164 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=45e4e3f8-045a-4651-bd83-6087eca44175 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-02 (2 days ago)
dmi.bios.date: 09/19/2023
dmi.bios.release: 1.48
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET61W (1.48 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QV00BRUK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias:
dmi:bvnLENOVO:bvrN2OET61W(1.48):bd09/19/2023:br1.48:efr1.22:svnLENOVO:pn20QV00BRUK:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00BRUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
dmi.product.family: ThinkPad X1 Extreme 2nd
dmi.product.name: 20QV00BRUK
dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
dmi.product.version: ThinkPad X1 Extreme 2nd
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
[Touch-packages] [Bug 2042763] Re: Keyboard navigation in the Show Applications menu
Tracking in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6331
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
** Tags added: a11y
** Summary changed:
- Keyboard navigation in the Show Applications menu
+ Keyboard navigation doesn't work in app grid subfolders
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6331
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6331
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6331
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042763
Title:
Keyboard navigation doesn't work in app grid subfolders
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
Hello.
My bug, if it is one, is in Wayland, or more likely in new desktop icon
management thingy, which was introduced with one of the last Ubuntu versions.
Maybe around ubuntu 22.04. I'm not sure if the problem came when Wayland was
set as the window manager or if it came when the new "Desktop Icon Manager"
thing came along. I think the two weren't too far apart in time. I'm only
reporting my problem now because I always assumed it would be fixed in future
updates. But my problem never changed with all the updates.
Here is my problem:
I can't navigate in the "Show Applications" menu with the keyboard when I go
into a subfolder. This means that I can navigate in "Show Applications" with
the keyboard as long as I stay at the top level. But when I go to a folder that
contains several programs, such as the "Utilities" folder, the keyboard
navigation no longer works. The cursor will stuck no matter which arrow key I
press. Even the Tab key is of no use. I've already searched for this problem on
the Internet, but couldn't find it. Either I'm the only one who has this
problem, or most others simply prefer to use the mouse to navigate. I only use
the keyboard when possible. I am a heavy keyboard/hotkey user.
The problem has existed for me for a long time. It either came with the
switch to Wayland or with the switch to the new desktop icon management thingy.
It's just a small problem, but for a massive keyboard user, it's really
annoying. And definitely also for people who can't use a mouse.
Kind regards
Chris
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 5 11:22:55 2023
DistUpgraded: 2023-11-03 22:29:03,001 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500
XT/6500M] [1002:743f] (rev c1) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Navi 24 [Radeon RX 6400/6500 XT/6500M]
[1043:05db]
InstallationDate: Installed on 2021-09-16 (779 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=da9b8938-71c1-4591-9b97-e052ca3ea1b2 ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (2 days ago)
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F12
dmi.board.name: P35C-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35C-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35C-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
dmi.product.name: P35C-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
[Touch-packages] [Bug 2042772] Re: Display corrupted/freeze
** Tags added: amdgpu ** Summary changed: - Display corrupted/freeze + [amdgpu] Display corrupted/freeze ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2042772 Title: [amdgpu] Display corrupted/freeze Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: After latest updates login display is fine but after entering password display changes to black with random full width 1 pixel high white lines that move randomly vertically. Must power off to recover. Boot in recovery mode works OK. Send email if you need more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 5 07:09:04 2023 DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c9) (prog-if 00 [VGA controller]) Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769] Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [1028:0769] InstallationDate: Installed on 2018-08-11 (1912 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5565 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago) dmi.bios.date: 10/18/2016 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.5 dmi.board.name: 0021CT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.0.5 dmi.modalias: dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769: dmi.product.family: Inspiron dmi.product.name: Inspiron 5565 dmi.product.sku: 0769 dmi.product.version: 1.0.5 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042772/+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 2042823] Re: Login blank background (gray) after update
Do you have any disabled monitors plugged in? This sounds like bug 1760849 ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2042823 Title: Login blank background (gray) after update Status in gnome-shell package in Ubuntu: Incomplete Bug description: Today I booted up and the update manager came to inform me I had updates (system was recently updated). I chose to do them because I'm having issues with HDMI audio (and audio in general, only headset via USB works) and it is an NVIDIA GPU. However after reboot, the login screen is just blank with only the gray background. It is still the GUI but just no login box/logo/anything else. I chose xorg as the issue but I'm not certain of it. Not sure how to troubleshoot this as I'm unfamiliar with the inner workings of this. I have since attempted to reinstall the NVIDIA drivers using apt purge ~nnvidia and then reinstalling with ubuntu-drivers autoinstall, as well as reinstalling ubuntu-desktop and related components. I can still log in via terminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..05.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 6 11:14:02 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-88-generic, x86_64: installed virtualbox/6.1.38, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] [10de:2216] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GA102 [GeForce RTX 3080 Lite Hash Rate] [1043:882e] InstallationDate: Installed on 2021-11-03 (732 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=34735887-8417-4547-843c-9b9b6b7cfbd8 ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4201 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VIII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4201:bd04/26/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIHERO(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2042823/+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 2041496] Re: btmgmt --index broken in Mantic
** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: bluez (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2041496 Title: btmgmt --index broken in Mantic Status in bluez package in Ubuntu: In Progress Bug description: On Mantic: $ btmgmt --index 1 info Unable to open 1: No such file or directory (2) Index list with 1 item hci0: Primary controller addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration current settings: powered ssp br/edr le secure-conn name rpi-5b-rev1d0-f88b short name hci0: Configuration options supported options: public-address missing options: Note the error 'Unable to open...' above. The machine has only a single hci so index 1 is invalid. The correct result should be: $ btmgmt --index 1 info Reading hci1 info failed with status 0x11 (Invalid Index) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2041496/+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 2042587] Re: jammy's version breaks existing dhcp scripts with relay
..also, apologies for all the typos I managed to place there. Step 7 was meant to say "repeat steps 4 and 5" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: Incomplete Bug description: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 2042587] Re: jammy's version breaks existing dhcp scripts with relay
I'm so sorry this is so complex, but I couldn't figure out any simpler way to reproduce as they components involved do network configuration. Anyway, please find attached a docker compose file and related dnsmasq configurations (mapped automatically in that compose file) that helps in the reproduction by setting up two different dhcp servers based on dnsmasq (focal and jammy) and a machine that can be used to request a dhcp address. To reproduce the bug: 1) first install everything needed by running docker-compose up -d 2) wait until everything has been installed, check for example that the output of has something from all 3 containers and is not getting any more lines docker-compose logs --follow 3) stop jammy version of the server with docker-compose stop jammy-server 4) get inside client machine to run dhclient. Run it first without fake relay address, then with one (to trigger the DHCP relay behaviour in dnsmasq) docker-compose exec client bash dhclient -d -v (ctrl-c after a while) dhclient -d -v -g 192.168.0.10 (ctrl-c after a while) 5) observe server's log dnsmasq-script-sample-focal-server-1 | dnsmasq-dhcp: DHCPREQUEST(eth0) 192.168.0.3 02:42:c0:a8:00:04 dnsmasq-script-sample-focal-server-1 | dnsmasq-dhcp: DHCPACK(eth0) 192.168.0.3 02:42:c0:a8:00:04 5a49beb3cd53 dnsmasq-script-sample-focal-server-1 | hello from dhcp hook script, IP argument is 192.168.0.3 dnsmasq-script-sample-focal-server-1 | dnsmasq-dhcp: DHCPREQUEST(eth0) 192.168.0.3 02:42:c0:a8:00:04 dnsmasq-script-sample-focal-server-1 | dnsmasq-dhcp: DHCPACK(eth0) 192.168.0.3 02:42:c0:a8:00:04 5a49beb3cd53 dnsmasq-script-sample-focal-server-1 | hello from dhcp hook script, IP argument is 192.168.0.3 6) now stop focal version of server and start jammy: docker-compose stop focal-server docker-compose start jammy-server 7) repeat steps 5 and 6, this time the output has the wroing ip in the 2nd hook script invocation dnsmasq-script-sample-jammy-server-1 | dnsmasq-dhcp: DHCPREQUEST(eth0) 192.168.0.1 02:42:c0:a8:00:04 dnsmasq-script-sample-jammy-server-1 | dnsmasq-dhcp: DHCPACK(eth0) 192.168.0.1 02:42:c0:a8:00:04 5a49beb3cd53 dnsmasq-script-sample-jammy-server-1 | hello from dhcp hook script, IP argument is 192.168.0.1 dnsmasq-script-sample-jammy-server-1 | dnsmasq-dhcp: DHCPREQUEST(eth0) 192.168.0.1 02:42:c0:a8:00:04 dnsmasq-script-sample-jammy-server-1 | dnsmasq-dhcp: DHCPACK(eth0) 192.168.0.1 02:42:c0:a8:00:04 5a49beb3cd53 dnsmasq-script-sample-jammy-server-1 | hello from dhcp hook script, IP argument is 192.168.0.10 ** Attachment added: "archive containing docker-compose.yml and needed configuration files" https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5716459/+files/sample.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/2042587 Title: jammy's version breaks existing dhcp scripts with relay Status in dnsmasq package in Ubuntu: Incomplete Bug description: When upgrading from focal to jammy, existing dnsmasq dhcp-scripts stopped working in an environment where a DHCP relay is in use. Instead of the expected client IP address, the script gets the _relay_ IP address as an argument. From dnsmasq documentation for --dhcp- script: > The arguments to the process are "add", "old" or "del", the MAC address of the host (or DUID for IPv6) , the IP address, and the hostname, if known. I believe the change has been inadverently made in upstream commit 527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692 (https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f) as the commit message only speaks about inet_ntoa replacement and not the behavioral change it also introduces (previously the relay address was only set to the environment variable, now it effectively overrides the prevoiusly set client's IP address). dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 2041496] Re: btmgmt --index broken in Mantic
** Tags added: mantic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2041496 Title: btmgmt --index broken in Mantic Status in bluez package in Ubuntu: New Bug description: On Mantic: $ btmgmt --index 1 info Unable to open 1: No such file or directory (2) Index list with 1 item hci0: Primary controller addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration current settings: powered ssp br/edr le secure-conn name rpi-5b-rev1d0-f88b short name hci0: Configuration options supported options: public-address missing options: Note the error 'Unable to open...' above. The machine has only a single hci so index 1 is invalid. The correct result should be: $ btmgmt --index 1 info Reading hci1 info failed with status 0x11 (Invalid Index) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2041496/+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 2025339] Re: FDE image fails to run e2fsck
** Tags added: foundations-todo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025339 Title: FDE image fails to run e2fsck Status in e2fsprogs package in Ubuntu: Fix Released Status in e2fsprogs source package in Lunar: In Progress Status in e2fsprogs package in Debian: Fix Released Bug description: After installation of the FDE image, the system fails to boot due to e2fsck failing with: Jun 21 12:48:19 ubuntu systemd-fsck[268]: /dev/vda2 has unsupported feature(s): FEATURE_C12 this means that Jammy fsck fails against mantic created ext4 which is not great Seems this is orphan_file feature / orphan_present Also need to check if grub2 supports this as it is RO_INCOMPAT feature. [Fix] This SRU is disabling 2 features (orphan_file and metadata_csum_seed) from ext4 to generate filesystems compatible with older series. Fixes come from debian (fixing #1031622, #1030939). This is only disabling the feature by default. One can still generate a filesystem with this feature by explicitly listing them when invoking mkfs.ext4. [Impact] See LP: #2028564. Generating a filesystem on lunar with e2fsprogs will use the orphan_file feature. This will prevent a jammy (or older) based OS from modifying this filesystem (in particular resize it at first boot). [ Test Plan ] On lunar, generate a filesystem and check the orphan_file feature is enabled: $ dd if=/dev/zero of=test.img bs=100M count=1 $ mkfs.ext4 test.img $ # Then check the orphan_file feature is enabled $ dumpe2fs test.img | grep orphan Move this .img file to a jammy based machine, and try using resize2fs on it: $ resize2fs -d -f -M test.img resize2fs 1.46.5 (30-Dec-2021) resize2fs: Filesystem has unsupported feature(s) (test.img) [Where problems could occur] Some users on Lunar may currently rely on this feature to be enabled by default. This can still be enabled explicitly when calling mkfs.ext4 but the default behavior will be changed. The orphan_file feature aims at improving performances when dealing with deleted files or directories. So if we disable this by default, I think it should only impact performances of generated filesystems and probably not break anything else. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025339/+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 2042823] Re: Login blank background (gray) after update
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2042823 Title: Login blank background (gray) after update Status in xorg package in Ubuntu: New Bug description: Today I booted up and the update manager came to inform me I had updates (system was recently updated). I chose to do them because I'm having issues with HDMI audio (and audio in general, only headset via USB works) and it is an NVIDIA GPU. However after reboot, the login screen is just blank with only the gray background. It is still the GUI but just no login box/logo/anything else. I chose xorg as the issue but I'm not certain of it. Not sure how to troubleshoot this as I'm unfamiliar with the inner workings of this. I have since attempted to reinstall the NVIDIA drivers using apt purge ~nnvidia and then reinstalling with ubuntu-drivers autoinstall, as well as reinstalling ubuntu-desktop and related components. I can still log in via terminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..05.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 6 11:14:02 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-88-generic, x86_64: installed virtualbox/6.1.38, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] [10de:2216] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GA102 [GeForce RTX 3080 Lite Hash Rate] [1043:882e] InstallationDate: Installed on 2021-11-03 (732 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=34735887-8417-4547-843c-9b9b6b7cfbd8 ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4201 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VIII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4201:bd04/26/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIHERO(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2042823/+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 2042823] [NEW] Login blank background (gray) after update
You have been subscribed to a public bug: Today I booted up and the update manager came to inform me I had updates (system was recently updated). I chose to do them because I'm having issues with HDMI audio (and audio in general, only headset via USB works) and it is an NVIDIA GPU. However after reboot, the login screen is just blank with only the gray background. It is still the GUI but just no login box/logo/anything else. I chose xorg as the issue but I'm not certain of it. Not sure how to troubleshoot this as I'm unfamiliar with the inner workings of this. I have since attempted to reinstall the NVIDIA drivers using apt purge ~nnvidia and then reinstalling with ubuntu-drivers autoinstall, as well as reinstalling ubuntu-desktop and related components. I can still log in via terminal. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..05.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 6 11:14:02 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-88-generic, x86_64: installed virtualbox/6.1.38, 6.2.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] [10de:2216] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GA102 [GeForce RTX 3080 Lite Hash Rate] [1043:882e] InstallationDate: Installed on 2021-11-03 (732 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-36-generic root=UUID=34735887-8417-4547-843c-9b9b6b7cfbd8 ro quiet splash radeon.audio=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4201 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VIII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4201:bd04/26/2022:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIIHERO(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ubuntu -- Login blank background (gray) after update https://bugs.launchpad.net/bugs/2042823 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2042825] [NEW] package udev 245.4-4ubuntu3.22 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1
Public bug reported: After updating the system, I get this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.22 ProcVersionSignature: Ubuntu 5.4.0-166.183-generic 5.4.252 Uname: Linux 5.4.0-166-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules 70-snap.gnome-calculator.rules 70-snap.zoom-client.rules 70-snap.gnome-logs.rules 70-snap.firefox.rules 70-snap.slack.rules 70-snap.gnome-system-monitor.rules Date: Wed Nov 1 20:35:58 2023 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-09-13 (1514 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Latitude 5501 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-166-generic root=UUID=58414a1c-8bb9-4e71-a6db-e40231eeb7e0 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: systemd Title: package udev 245.4-4ubuntu3.22 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2023 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.26.0 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.26.0:bd07/05/2023:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5501 dmi.product.sku: 0919 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/2042825 Title: package udev 245.4-4ubuntu3.22 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: After updating the system, I get this error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.22 ProcVersionSignature: Ubuntu 5.4.0-166.183-generic 5.4.252 Uname: Linux 5.4.0-166-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules 70-snap.gnome-calculator.rules 70-snap.zoom-client.rules 70-snap.gnome-logs.rules 70-snap.firefox.rules 70-snap.slack.rules 70-snap.gnome-system-monitor.rules Date: Wed Nov 1 20:35:58 2023 ErrorMessage: installed udev package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-09-13 (1514 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Latitude 5501 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-166-generic root=UUID=58414a1c-8bb9-4e71-a6db-e40231eeb7e0 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: systemd Title: package udev 245.4-4ubuntu3.22 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2023 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.26.0 dmi.board.name: 0Y8H01 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.26.0:bd07/05/2023:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5501 dmi.product.sku: 0919 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2042825/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/455178 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2039104 Title: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Mantic: New Bug description: In response to LP: #2038964 and due to the timing we have forked ubuntu-raspi-settings into a separate source package. ubuntu-settings must therefore be updated to drop ubuntu-raspi- settings* from debian/control as otherwise binary builds of the package will be rejected by the archive (if the version number is <= 23.10.6) or will wrongly supersede the fixes that have just been uploaded to mantic (if the version number is > 23.10.6). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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
