[Touch-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
Having the exact same issue with ubuntu 20.04. Has anyone found a work around for this rather annoying issue? -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+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 1782709] Re: Updating systemd kills network on bionic
I have: apt-get install ifupdown systemctl stop systemd-networkd.socket systemd-networkd networkd-dispatcher systemd-network-wait-online systemctl disable systemd-networkd.socket systemd-networkd networkd-dispatcher systemd-network-wait-online systemctl mask systemd-networkd.socket systemd-networkd networkd-dispatcher systemd-network-wait-online best. -- 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/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+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 1916485] Re: test -x fails inside shell scripts in containers
Seems to still be an issue with docker on groovy/focal/[...]. Any plans to backport the new seccomp to those? -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in glibc source package in Xenial: Invalid Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in glibc source package in Bionic: Invalid Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: New Status in systemd source package in Bionic: New Status in docker.io source package in Focal: New Status in glibc source package in Focal: Invalid Status in libseccomp source package in Focal: New Status in runc source package in Focal: New Status in systemd source package in Focal: New Status in docker.io source package in Groovy: New Status in glibc source package in Groovy: Invalid Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: New Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Status in systemd source package in Hirsute: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute images. From comparison this seems to be caused by a
[Touch-packages] [Bug 1918044] Re: Weather forecast and info is not available any more
** No longer affects: gnome-weather -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: Weather forecast and info is not available any more Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Confirmed Status in libgweather package in Ubuntu: Confirmed Status in gnome-weather package in Fedora: New Bug description: The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://developer.yr.no/doc/guides/getting-started-from-forecast-xml/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1919093] [NEW] Desktop does not load after login - purple screen with mouse
Public bug reported: When logging in, the screen goes purple and blank, but I can still move the mouse. Keyboard shortcuts such as Alt+F2 or Ctrl+Alt+T have no effect. I can use Ctrl+Alt+F[1345...] to switch to a shell or go back to the login screen, but Ctrl+Alt+F2 puts me back in the blank state. When turning off the computer from the login screen, I get a warning that my user is logged in. The most similar previous bug report I've been able to find is https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137. However, my problem occurs regardless of whether I fail the first login attempt or not, or whether I enter my password or scan my fingerprint. I have replicated the problem booting with two kernel versions: Linux 5.8.0-44 and Linux 5.8.0-43 I have been using the computer since November 2020, and this problem occurred for the first time when I rebooted it this weekend (Sat 2021-03-13). I have previously had trouble getting getting external monitors to work, but even that has worked fine for the past few months. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Mar 14 21:19:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22c0] NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22c0] MachineType: LENOVO 20TH000VMX ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=linux PATH=(custom, no user) LANG=nb_NO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=9da324cb-cdc4-42f8-abdd-b764e455a1f7 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET27W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TH000VMX 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.7 dmi.modalias: dmi:bvnLENOVO:bvrN2VET27W(1.12):bd12/21/2020:br1.12:efr1.7:svnLENOVO:pn20TH000VMX:pvrThinkPadP1Gen3:rvnLENOVO:rn20TH000VMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20TH000VMX dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu ** Description changed: When logging in, the screen goes purple and blank, but I can still move the mouse. Keyboard shortcuts such as Alt+F2 or Ctrl+Alt+T have no effect. I can use Ctrl+Alt+F[1345...] to switch to a shell or go back to the login screen, but Ctrl+Alt+F2 puts me back in the blank state. When turning off the computer from the login screen, I get a warning that my user is logged in. The most similar previous bug report I've been able to find is https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137. However, my problem occurs regardless of whether I fail the first login attempt or not, or whether I enter my password or scan my fingerprint. + + I have replicated the problem booting with two kernel versions: Linux + 5.8.0-44 and Linux 5.8.0-43 I have been using the computer since November 2020, and this problem occurred for the first time when I rebooted it this weekend (Sat 2021-03-13). I have previously had trouble getting getting external monitors to work, but even that has worked fine for the past few months. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun
[Touch-packages] [Bug 1919078] [NEW] Ubuntu SSO login - not working (Throws "Error connecting to server"
You have been subscribed to a public bug: Hi, I'm looking for possible ways to add an Ubuntu SSO account with my Ubuntu system for the past few weeks. But I'm getting the error as "Error connecting to Ubuntu SSO server. Something went wrong. Please try again later". I tried to login via the web, it works fine. I'm on the latest build. Check my system version at https://ibb.co/7bc1JgP Screenshot (of error): https://ibb.co/v1JvKZ6 Kindly help me with this error. ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment login -- Ubuntu SSO login - not working (Throws "Error connecting to server" https://bugs.launchpad.net/bugs/1919078 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts 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 1919078] Re: Ubuntu SSO login - not working (Throws "Error connecting to server"
** Package changed: ubuntu => gnome-online-accounts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1919078 Title: Ubuntu SSO login - not working (Throws "Error connecting to server" Status in gnome-online-accounts package in Ubuntu: New Bug description: Hi, I'm looking for possible ways to add an Ubuntu SSO account with my Ubuntu system for the past few weeks. But I'm getting the error as "Error connecting to Ubuntu SSO server. Something went wrong. Please try again later". I tried to login via the web, it works fine. I'm on the latest build. Check my system version at https://ibb.co/7bc1JgP Screenshot (of error): https://ibb.co/v1JvKZ6 Kindly help me with this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1919078/+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 1891810] Re: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers
Updating libseccomp to 2.5.1 breaks the systemd unit tests on ppc64el since the behaviour around filtering of the multiplexed socket() system call changes - as such a fix for systemd in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 is also required. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1891810 Title: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: New Status in libseccomp source package in Bionic: New Status in libseccomp source package in Focal: New Status in libseccomp source package in Groovy: New Status in libseccomp source package in Hirsute: Fix Released Bug description: The version of libseccomp2 in bionic does not know about the openat2 syscall. In my particular usecase, I was trying to run podman/buildah in an nspawn container, using fuse-overlayfs. This leads to peculiar failure modes as described in this issue: https://github.com/containers/fuse-overlayfs/issues/220 This could well cause other problems, previously issues like that have affected snapd, etc. Backporting the master branch of libseccomp fixed this for me, but for an SRU a cherrypick of https://github.com/seccomp/libseccomp/commit/b3206ad5645dceda89538ea8acc984078ab697ab might be sufficient... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libseccomp2 2.4.3-1ubuntu3.18.04.3 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 Date: Sun Aug 16 17:35:09 2020 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1.2 libgcc1 1:8.4.0-1ubuntu1~18.04 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: libseccomp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1916485] Re: test -x fails inside shell scripts in containers
@oded-geek - yes, the libseccomp SRU to backport 2.5.1 to these releases is being handled in https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810 -- 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/1916485 Title: test -x fails inside shell scripts in containers Status in docker.io package in Ubuntu: New Status in glibc package in Ubuntu: Opinion Status in libseccomp package in Ubuntu: Fix Committed Status in runc package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in glibc source package in Xenial: Invalid Status in libseccomp source package in Xenial: New Status in runc source package in Xenial: New Status in systemd source package in Xenial: New Status in docker.io source package in Bionic: New Status in glibc source package in Bionic: Invalid Status in libseccomp source package in Bionic: New Status in runc source package in Bionic: New Status in systemd source package in Bionic: New Status in docker.io source package in Focal: New Status in glibc source package in Focal: Invalid Status in libseccomp source package in Focal: New Status in runc source package in Focal: New Status in systemd source package in Focal: New Status in docker.io source package in Groovy: New Status in glibc source package in Groovy: Invalid Status in libseccomp source package in Groovy: New Status in runc source package in Groovy: New Status in systemd source package in Groovy: Fix Released Status in docker.io source package in Hirsute: New Status in glibc source package in Hirsute: Opinion Status in libseccomp source package in Hirsute: Fix Committed Status in runc source package in Hirsute: New Status in systemd source package in Hirsute: Fix Released Bug description: (SRU template for systemd) [impact] bash (and some other shells) builtin test command -x operation fails [test case] on any affected host system, start nspawn container, e.g.: $ sudo apt install systemd-container $ wget https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz $ mkdir h $ cd h $ tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz $ sudo systemd-nspawn Then from a bash shell, verify if test -x works: root@h:~# ls -l /usr/bin/gpg -rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg root@h:~# test -x /usr/bin/gpg || echo "fail" fail [regression potential] any regression would likely occur during a syscall, most likely faccessat2(), or during other syscalls. [scope] this is needed for b/f this is fixed upstream by commit bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so this is fixed in h this was pulled into Debian at version 246.2 in commit e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g in x, the entire systemd seccomp code is completely different and the patch doesn't apply, nor does it appear to be needed, as the problem doesn't reproduce in a h container under x. [other info] this needs fixing in libseccomp as well [original description] glibc regression causes test -x to fail inside scripts inside docker/podman, dash and bash are broken, mksh and zsh are fine: root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail" Fail root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail" root@0df2ce5d7a46:/# root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail" root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail" Fail The -f flag works, as does /usr/bin/test: # bash -c "test -f /usr/bin/gpg || echo Fail" # bash -c "/usr/bin/test -x /usr/bin/gpg || echo Fail" # [Original bug report] root@84b750e443f8:/# lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 root@84b750e443f8:/# dpkg -l gnupg apt Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--== ii apt2.1.20 amd64commandline package manager ii gnupg 2.2.20-1ubuntu2 all GNU privacy guard - a free PGP replacement Hi, for 3 days our CI pipelines to recreate Docker images fails for the Hirsute ima
[Touch-packages] [Bug 1891810] Re: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers
** Patch added: "libseccomp_2.5.1-1ubuntu1~18.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+attachment/5476577/+files/libseccomp_2.5.1-1ubuntu1~18.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1891810 Title: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: New Status in libseccomp source package in Bionic: New Status in libseccomp source package in Focal: New Status in libseccomp source package in Groovy: New Status in libseccomp source package in Hirsute: Fix Released Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1891810] Re: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers
** Patch added: "libseccomp_2.5.1-1ubuntu1~20.10.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+attachment/5476579/+files/libseccomp_2.5.1-1ubuntu1~20.10.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1891810 Title: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: New Status in libseccomp source package in Bionic: New Status in libseccomp source package in Focal: New Status in libseccomp source package in Groovy: New Status in libseccomp source package in Hirsute: Fix Released Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1891810] Re: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers
** Description changed: - The version of libseccomp2 in bionic does not know about the openat2 - syscall. + [Impact] - In my particular usecase, I was trying to run podman/buildah in an - nspawn container, using fuse-overlayfs. This leads to peculiar failure - modes as described in this issue: + The version of libseccomp2 in X/B/F/G does not know about the openat2 + syscall. As such applications that use libseccomp cannot specify a + system-call filter against this system-call and so it cannot be + mediated. - https://github.com/containers/fuse-overlayfs/issues/220 - This could well cause other problems, previously issues like that have - affected snapd, etc. + [Test Plan] - Backporting the master branch of libseccomp fixed this for me, but for - an SRU a cherrypick of - https://github.com/seccomp/libseccomp/commit/b3206ad5645dceda89538ea8acc984078ab697ab - might be sufficient... + This can be tested by simply running scmp_sys_resolver from the seccomp + binary package and specifying this system-call: - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: libseccomp2 2.4.3-1ubuntu3.18.04.3 - ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 - Uname: Linux 5.4.0-42-generic x86_64 - ApportVersion: 2.20.9-0ubuntu7.16 - Architecture: amd64 - Date: Sun Aug 16 17:35:09 2020 - Dependencies: - gcc-8-base 8.4.0-1ubuntu1~18.04 - libc6 2.27-3ubuntu1.2 - libgcc1 1:8.4.0-1ubuntu1~18.04 - ProcEnviron: - TERM=screen.xterm-256color - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash - SourcePackage: libseccomp - UpgradeStatus: No upgrade log present (probably fresh install) + Existing behaviour: + + $ scmp_sys_resolver openat2 + -1 + + Expected behaviour: + + $ scmp_sys_resolver openat2 + 437 + + (Note this value will be different on other architectures) + + + [Where problems could occur] + + In version 2.5.1 of libseccomp which adds this new system-call, changes + were also made in the way the socket system-call is handled by + libseccomp on PPC platforms - this resulted in a change in the expected + behaviour and so this has already been noticed and a fix is required for + the systemd unit tests as a result + https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 + + There was also a similar change for s390x but so far no regressions have + been observed as a result as systemd already expected that behaviour + from libseccomp, it was only PPC that was missing. + + In the event that a regression is observed however, we can easily either + patch the affected package to cope with the new behaviour of this + updated libseccomp since in each case the change in behaviour only + affects a few system calls on particular architectures, or we can revert + this update. + + + [Other Info] + + * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ ** Description changed: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. - [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) - [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. + [Other Info] - [Other Info] - - * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security-proposed/+archive/u
[Touch-packages] [Bug 1891810] Re: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers
** Patch added: "libseccomp_2.5.1-1ubuntu1~20.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+attachment/5476578/+files/libseccomp_2.5.1-1ubuntu1~20.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1891810 Title: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: New Status in libseccomp source package in Bionic: New Status in libseccomp source package in Focal: New Status in libseccomp source package in Groovy: New Status in libseccomp source package in Hirsute: Fix Released Bug description: [Impact] The version of libseccomp2 in X/B/F/G does not know about the openat2 syscall. As such applications that use libseccomp cannot specify a system-call filter against this system-call and so it cannot be mediated. [Test Plan] This can be tested by simply running scmp_sys_resolver from the seccomp binary package and specifying this system-call: Existing behaviour: $ scmp_sys_resolver openat2 -1 Expected behaviour: $ scmp_sys_resolver openat2 437 (Note this value will be different on other architectures) [Where problems could occur] In version 2.5.1 of libseccomp which adds this new system-call, changes were also made in the way the socket system-call is handled by libseccomp on PPC platforms - this resulted in a change in the expected behaviour and so this has already been noticed and a fix is required for the systemd unit tests as a result https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1918696 There was also a similar change for s390x but so far no regressions have been observed as a result as systemd already expected that behaviour from libseccomp, it was only PPC that was missing. In the event that a regression is observed however, we can easily either patch the affected package to cope with the new behaviour of this updated libseccomp since in each case the change in behaviour only affects a few system calls on particular architectures, or we can revert this update. [Other Info] * As usual thorough testing of this update has been performed both manually via the QA Regression Testing scripts, and via the autopkgtest infrastructure against packages in the Ubuntu Security Proposed PPA https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/ with results seen https://people.canonical.com/~platform/security-britney/current/ I have attached debdiffs of the prepared updates which are also sitting in the Ubuntu Security Proposed PPA. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+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 1906267] Re: IntelHD audio not detected after upgrading to Ubuntu 20.10
Yes please. Or just let us know. -- 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/1906267 Title: IntelHD audio not detected after upgrading to Ubuntu 20.10 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to Kubuntu 20.10, from 20.04 occasionally when I turn my computer on the sound card doesn't work. If I load Pulse Audio Volume Control and disable and then re-enable the audio controller (Family 17h (Models 00h-0fh) HD Audio Controller it will work again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Nov 30 15:19:50 2020 InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-29-generic N/A linux-backports-modules-5.8.0-29-generic N/A linux-firmware1.190.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: groovy Uname: Linux 5.8.0-29-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-11-20 (10 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/09/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.90 dmi.board.name: B450M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.90:bd12/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=UUID=e53f97b3-d450-45b0-be09-5c7f0e17b18d InstallationDate: Installed on 2020-03-21 (254 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=d29e468f-8ce0-494e-9de4-c9cb9211b09e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0
[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in OEM Priority Project: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1918880] Re: pulseaudio threaded-ml suspend issue
No there's no need to change the config file. I'm guessing now that the issue is the daemon stuck in a system call. That usually means it's a kernel bug, or a bug in the kernel sound driver. So if you are comfortable doing so, please try some different kernel versions: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.6 (Ubuntu) Status: New => Incomplete -- 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/1918880 Title: pulseaudio threaded-ml suspend issue Status in linux-oem-5.6 package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: My laptop failed to suspend overnight and was unresponsive when I opened it back up. This is on Ubuntu 20.04.2 LTS with kernel 5.6.0-1048-oem and pulseaudio:amd64/focal-updates 1:13.99.1-1ubuntu3.10 uptodate. In syslog, I found a stream of suspend attempts with pulseaudio-related issues repeating in a 40s cycle, so reporting this as a PA issue. Mar 12 00:08:31 churn systemd[1]: Reached target Sleep. Mar 12 00:08:31 churn upowerd[1698]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running Mar 12 00:08:31 churn systemd[1]: Starting Suspend... Mar 12 00:08:31 churn ModemManager[1427]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running Mar 12 00:08:31 churn kernel: [883904.845262] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM Mar 12 00:08:31 churn ModemManager[1427]: Couldn't check support for device '/sys/devices/pci:00/:00:14.3': Device support check task already available for device '/sys/devices/pci:00/:00:14.3' Mar 12 00:08:31 churn systemd-sleep[516395]: Suspending system... Mar 12 00:08:31 churn kernel: [883904.853576] PM: suspend entry (s2idle) Mar 12 00:08:51 churn kernel: [883904.856917] Filesystems sync: 0.003 seconds Mar 12 00:08:51 churn kernel: [883904.857284] Freezing user space processes ... Mar 12 00:08:51 churn kernel: [883904.991749] iwlwifi :00:14.3: FW already configured (0) - re-configuring Mar 12 00:08:51 churn kernel: [883924.868069] Freezing of tasks failed after 20.010 seconds (1 tasks refusing to freeze, wq_busy=0): Mar 12 00:08:51 churn kernel: [883924.868160] threaded-ml D0 3306 2128 0x80004326 Mar 12 00:08:51 churn kernel: [883924.868166] Call Trace: Mar 12 00:08:51 churn kernel: [883924.868183] __schedule+0x2d8/0x760 Mar 12 00:08:51 churn kernel: [883924.868188] schedule+0x55/0xc0 Mar 12 00:08:51 churn kernel: [883924.868195] do_exit.cold+0x9f/0xb5 Mar 12 00:08:51 churn kernel: [883924.868200] rewind_stack_do_exit+0x17/0x20 Mar 12 00:08:51 churn kernel: [883924.868205] RIP: 0033:0x7fc8a96ebcb9 Mar 12 00:08:51 churn kernel: [883924.868216] Code: Bad RIP value. Mar 12 00:08:51 churn kernel: [883924.868219] RSP: 002b:7fc899504850 EFLAGS: 0293 ORIG_RAX: 0007 Mar 12 00:08:51 churn kernel: [883924.868223] RAX: fdfc RBX: 208bbe357f60 RCX: 7fc8a96ebcb9 Mar 12 00:08:51 churn kernel: [883924.868225] RDX: 7530 RSI: 0003 RDI: 208bbe357f60 Mar 12 00:08:51 churn kernel: [883924.868227] RBP: 0003 R08: R09: 1587756a Mar 12 00:08:51 churn kernel: [883924.868229] R10: 0f90 R11: 0293 R12: 7530 Mar 12 00:08:51 churn kernel: [883924.868231] R13: 7530 R14: 208bbe3285d0 R15: 7fff6f13d440 Mar 12 00:08:51 churn kernel: [883924.868427] OOM killer enabled. Mar 12 00:08:51 churn rtkit-daemon[1608]: The canary thread is apparently starving. Taking action. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1026] device (p2p-dev-wlp0s20f3): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed') Mar 12 00:08:51 churn rtkit-daemon[1608]: Demoting known real-time threads. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1036] manager: NetworkManager state is now DISCONNECTED Mar 12 00:08:51 churn rtkit-daemon[1608]: Demoted 0 threads. Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1039] manager: sleep: sleep requested (sleeping: no enabled: yes) Mar 12 00:08:51 churn NetworkManager[1297]: [1615504131.1039] device (wlp0s20f3): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') Mar 12 00:08:51 churn pulseaudio[2134]: q overrun, queuing locally Mar 12 00:08:51 churn kernel: [883924.868429] Restarting tasks ... done. Mar 12 00:08:51 churn pulseaudio[2134]: message repe
[Touch-packages] [Bug 1918954] Re: [Fujitsu MS-7293] [1106:3288] No sound at all
** Summary changed: - [MS-7293, Realtek ALC883, Orange Line Out, Rear] No sound at all + [Fujitsu MS-7293] [1106:3288] No sound at all ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1918954 Title: [Fujitsu MS-7293] [1106:3288] No sound at all Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: We have no sounds on speakers nor signals during the starting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.11 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic i686 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmljkl 1444 F pulseaudio /dev/snd/controlC1: hmljkl 1444 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Mar 12 17:19:26 2021 InstallationDate: Installed on 2021-03-11 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:VT82xx successful Symptom_Card: VT8237A/VT8251 HDA Controller - HDA VIA VT82xx Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmljkl 1444 F pulseaudio /dev/snd/controlC1: hmljkl 1444 F pulseaudio Symptom_Jack: Orange Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7293, Realtek ALC883, Orange Line Out, Rear] No sound at all UpgradeStatus: Upgraded to bionic on 2021-03-12 (0 days ago) dmi.bios.date: 10/27/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7293 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 1.00 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/27/2006:svnFUJITSUSIEMENS:pnMS-7293:pvr1.00:rvnFUJITSUSIEMENS:rnMS-7293:rvr1.00:cvn:ct3:cvr: dmi.product.name: MS-7293 dmi.product.version: 1.00 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918954/+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 1919093] Re: Desktop does not load after login - purple screen with mouse
** Tags added: regression-update -- 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/1919093 Title: Desktop does not load after login - purple screen with mouse Status in xorg package in Ubuntu: New Bug description: When logging in, the screen goes purple and blank, but I can still move the mouse. Keyboard shortcuts such as Alt+F2 or Ctrl+Alt+T have no effect. I can use Ctrl+Alt+F[1345...] to switch to a shell or go back to the login screen, but Ctrl+Alt+F2 puts me back in the blank state. When turning off the computer from the login screen, I get a warning that my user is logged in. The most similar previous bug report I've been able to find is https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137. However, my problem occurs regardless of whether I fail the first login attempt or not, or whether I enter my password or scan my fingerprint. I have replicated the problem booting with two kernel versions: Linux 5.8.0-44 and Linux 5.8.0-43 I have been using the computer since November 2020, and this problem occurred for the first time when I rebooted it this weekend (Sat 2021-03-13). I have previously had trouble getting getting external monitors to work, but even that has worked fine for the past few months. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Mar 14 21:19:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22c0] NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22c0] MachineType: LENOVO 20TH000VMX ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=linux PATH=(custom, no user) LANG=nb_NO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=9da324cb-cdc4-42f8-abdd-b764e455a1f7 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET27W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TH000VMX 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.7 dmi.modalias: dmi:bvnLENOVO:bvrN2VET27W(1.12):bd12/21/2020:br1.12:efr1.7:svnLENOVO:pn20TH000VMX:pvrThinkPadP1Gen3:rvnLENOVO:rn20TH000VMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20TH000VMX dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1919093/+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 1918855] Re: Xorg xserver got signal 6 to abort
** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in OEM Priority Project: New Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1919093] Re: Desktop does not load after login - purple screen with mouse
Thanks for the bug report. It appears the computer is in recovery/low graphics mode according to these kernel parameters "recovery nomodeset" and the Xorg log concurs in using "FBDEV". If you did that just to report this bug then that's OK, please just run this command to collect some logs of when the bug was occurring: journalctl -b-1 > journal1.txt journalctl -b-2 > journal2.txt journalctl -b-3 > journal3.txt and attach the resulting text files here. If you are not in recovery mode intentionally then please reboot, tap Esc before Ubuntu starts, and be sure to select the regular non-recovery kernel. Separately, please install the Nvidia driver, either by the 'Additional Drivers' app or by running: sudo apt install nvidia-driver-460 ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (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/1919093 Title: Desktop does not load after login - purple screen with mouse Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: When logging in, the screen goes purple and blank, but I can still move the mouse. Keyboard shortcuts such as Alt+F2 or Ctrl+Alt+T have no effect. I can use Ctrl+Alt+F[1345...] to switch to a shell or go back to the login screen, but Ctrl+Alt+F2 puts me back in the blank state. When turning off the computer from the login screen, I get a warning that my user is logged in. The most similar previous bug report I've been able to find is https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137. However, my problem occurs regardless of whether I fail the first login attempt or not, or whether I enter my password or scan my fingerprint. I have replicated the problem booting with two kernel versions: Linux 5.8.0-44 and Linux 5.8.0-43 I have been using the computer since November 2020, and this problem occurred for the first time when I rebooted it this weekend (Sat 2021-03-13). I have previously had trouble getting getting external monitors to work, but even that has worked fine for the past few months. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Mar 14 21:19:17 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22c0] NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22c0] MachineType: LENOVO 20TH000VMX ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en TERM=linux PATH=(custom, no user) LANG=nb_NO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=9da324cb-cdc4-42f8-abdd-b764e455a1f7 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.12 dmi.bios.vendor: LENOVO dmi.bios.version: N2VET27W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TH000VMX 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.7 dmi.modalias: dmi:bvnLENOVO:bvrN2VET27W(1.12):bd12/21/2020:br1.12:efr1.7:svnLENOVO:pn20TH000VMX:pvrThinkPadP1Gen3:rvnLENOVO:rn20TH000VMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 3 dmi.product.name: 20TH000VMX dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3 dmi.product.version: ThinkPad P1 Gen 3 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-no
[Touch-packages] [Bug 1918954] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1918954 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1918954 Title: [Fujitsu MS-7293] [1106:3288] No sound at all Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: We have no sounds on speakers nor signals during the starting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.11 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic i686 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmljkl 1444 F pulseaudio /dev/snd/controlC1: hmljkl 1444 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Mar 12 17:19:26 2021 InstallationDate: Installed on 2021-03-11 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:VT82xx successful Symptom_Card: VT8237A/VT8251 HDA Controller - HDA VIA VT82xx Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmljkl 1444 F pulseaudio /dev/snd/controlC1: hmljkl 1444 F pulseaudio Symptom_Jack: Orange Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [MS-7293, Realtek ALC883, Orange Line Out, Rear] No sound at all UpgradeStatus: Upgraded to bionic on 2021-03-12 (0 days ago) dmi.bios.date: 10/27/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7293 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 1.00 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/27/2006:svnFUJITSUSIEMENS:pnMS-7293:pvr1.00:rvnFUJITSUSIEMENS:rnMS-7293:rvr1.00:cvn:ct3:cvr: dmi.product.name: MS-7293 dmi.product.version: 1.00 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918954/+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