[Touch-packages] [Bug 1965608] [NEW] Crash in gbm_dri_bo_import on ASPEED + AMDGPU system
Public bug reported: I have a server machine with an ASPEED BMC (kernel driver `ast`) and a Radeon Pro WX 4100 (driver `amdgpu`). If I try to log into a KDE Wayland session or a Gnome Wayland session, it crashes back to the login screen, with the same innermost level in the traceback. What I'd like to be able to do: if a monitor is connected to the AMD GPU, then show the login screen on that, and maybe duplicate it on the BMC. If no external monitor is connected, show it only on the BMC. Ideally, it should switch on the fly, but at the very least, it shouldn't crash. Note that in Xorg sessions, it doesn't crash, but xrandr only shows outputs from the AMD GPU. If I do xrandr --listproviders, I see that the `ast` has no capabilities. Provider 0: id: 0x58 cap: 0x9, Source Output, Sink Offload crtcs: 5 outputs: 4 associated providers: 0 name:AMD Radeon (TM) Pro WX 4100 @ pci::0e:00.0 Provider 1: id: 0x99 cap: 0x0 crtcs: 1 outputs: 1 associated providers: 0 name:modesetting It really would be nice to support using it as a dumb output like DisplayLink, even if it has to allow tearing or drop many frames. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libgbm1 21.2.6-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Mar 19 00:09:57 2022 DistUpgraded: 2022-03-15 02:09:53,367 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 41) (prog-if 00 [VGA controller]) Subsystem: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:67e3] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] [1002:0b0d] InstallationDate: Installed on 2016-10-27 (1969 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=c4c2bc1a-635a-4890-9b75-207bd66db859 ro usbcore.autosuspend=0 earlycon console=ttyS1,115200n8 console=tty0 intel_iommu=on amd_iommu=on plymouth.ignore-serial-consoles pstore.backend=efi drm.debug=0x104 video=efifb:off thunderbolt.dyndbg pcie_ports=native pci=assign-busses,hpbussize=0x33,realloc,hpmmiosize=256M,hpmmioprefsize=1G RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: Upgraded to impish on 2022-03-15 (3 days ago) dmi.bios.date: 08/19/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: L1.43 dmi.board.name: X570D4U-2L2T dmi.board.vendor: ASRockRack dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrL1.43:bd08/19/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRockRack:rnX570D4U-2L2T:rvr:cvnToBeFilledByO.E.M.:ct2:cvrToBeFilledByO.E.M.:skuToBeFilledByO.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. version.compiz: compiz 1:0.9.14.1+21.10.20210501-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu ** Summary changed: - Crash in gbm_dri_bo_import on ASPEED + AMDGPU system (KDE Wayland and Gnome Wayland) + Crash in gbm_dri_bo_import on ASPEED + AMDGPU system -- 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/1965608 Title: Crash in gbm_dri_bo_import on ASPEED + AMDGPU system Status in mesa package
[Touch-packages] [Bug 1960425] Re: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Error message appeared a few minutes after exiting Suspend mode. -- 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/1960425 Title: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Not sure - submitting crash record ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 9 11:10:21 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-11-30 (70 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) 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-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1960425/+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 1768104] Re: systemd sometimes misdetects Xen VMs (fixed up-stream)
Hi Steve,
This build seems to work OK for me as well. Thanks!
% dpkg-query -Wf '${Package}: ${Version}\n' | rg systemd
libnss-systemd: 237-3ubuntu10.2
libpam-systemd: 237-3ubuntu10.2
libsystemd0: 237-3ubuntu10.2
python3-systemd: 234-1build1
systemd: 237-3ubuntu10.2
systemd-sysv: 237-3ubuntu10
% SYSTEMD_LOG_LEVEL=debug systemd-detect-virt
Failed to read $container of PID 1, ignoring: Permission denied
Found container virtualization none.
Virtualization Xen found in DMI (/sys/class/dmi/id/sys_vendor)
Virtualization XEN, found /sys/hypervisor/properties/features with value
2705, XENFEAT_dom0 (indicating the 'hardware domain') is not set.
Found VM virtualization xen
xen
% systemctl is-active xe-daemon
active
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1768104
Title:
systemd sometimes misdetects Xen VMs (fixed up-stream)
Status in systemd package in Ubuntu:
Fix Committed
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* XEN virtualization missidentified as hyperv
* This may cause units limited to a virtualisation not to be started; or
redundant units for the other type of virtualisation to be started instead.
* Previously xen & hyper-v were detected correctly separately, even when xen
emulates/suggests that it is hyper-v.
[Test Case]
* Execute systemd-detect-virt and check that it detects Xen & Hyperv
[Regression Potential]
* Things that "fake" xen might not work as the detection code
branches are changed, but it would affect previous releases and future
releases of systemd-detect-virt. So far such things are not known to
exist, and if such things appear in the future support for them would
need to land upstream first.
[Other Info]
* Original bug report
Cherrypick
https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a
It appears that Xen-based VMs sometimes report themselves as Microsoft
Hyper-V via CPUID — apparently this is for compatibility with Windows
guests. systemd 237 (as found in Bionic) gives preference to this
CPUID information when detecting Xen, and thus it erroneously assumes
that the guest is running under Hyper-V. This causes Xen-related
services (and anything else that relies on systemd's VM-detection
functionality) to fail.
I *believe* this is a regression from systemd 229 as used in Xenial —
we have at least a few Xen-based VMs that report as Hyper-V via CPUID
and don't have this issue on that version — but i haven't confirmed
that for certain.
Anyway, i've submitted a ticket with more details to the up-stream
project, and that has now been resolved through a fairly simple change
which applies cleanly to the Bionic systemd sources:
https://github.com/systemd/systemd/issues/8844
Would it be possible to pull this down? As mentioned, Xen-based Ubuntu
VMs can seriously misbehave without it.
Thanks!
See also:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573
---
% lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
% apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10
Candidate: 237-3ubuntu10
Version table:
*** 237-3ubuntu10 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1768104/+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 1768104] Re: systemd sometimes misdetects Xen VMs (fixed up-stream)
Hi Łukasz and Dimitri,
Thanks for responding so quickly. I've tested this on my Bionic VM and
it seems to be working:
% lsb_release -sd
Ubuntu 18.04 LTS
% uname -r
4.15.0-20-generic
% dpkg-query -Wf '${Package}: ${Version}\n' | rg systemd
libnss-systemd: 237-3ubuntu10.1
libpam-systemd: 237-3ubuntu10.1
libsystemd0: 237-3ubuntu10.1
python3-systemd: 234-1build1
systemd: 237-3ubuntu10.1
systemd-sysv: 237-3ubuntu10
% SYSTEMD_LOG_LEVEL=debug systemd-detect-virt
Failed to read $container of PID 1, ignoring: Permission denied
Found container virtualization none.
Virtualization Xen found in DMI (/sys/class/dmi/id/sys_vendor)
Virtualization XEN, found /sys/hypervisor/properties/features with value
2705, XENFEAT_dom0 (indicating the 'hardware domain') is not set.
Found VM virtualization xen
xen
I also did a few spot checks of journalctl, systemctl, , and all that
looks OK too.
Thanks!
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
** Tags removed: verification-done
** Tags added: verification-needed
--
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/1768104
Title:
systemd sometimes misdetects Xen VMs (fixed up-stream)
Status in systemd package in Ubuntu:
Fix Committed
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* XEN virtualization missidentified as hyperv
* This may cause units limited to a virtualisation not to be started; or
redundant units for the other type of virtualisation to be started instead.
* Previously xen & hyper-v were detected correctly separately, even when xen
emulates/suggests that it is hyper-v.
[Test Case]
* Execute systemd-detect-virt and check that it detects Xen & Hyperv
[Regression Potential]
* Things that "fake" xen might not work as the detection code
branches are changed, but it would affect previous releases and future
releases of systemd-detect-virt. So far such things are not known to
exist, and if such things appear in the future support for them would
need to land upstream first.
[Other Info]
* Original bug report
Cherrypick
https://github.com/systemd/systemd/commit/f2fe2865cd19cd4318b82d01b9b62d22b1697b3a
It appears that Xen-based VMs sometimes report themselves as Microsoft
Hyper-V via CPUID — apparently this is for compatibility with Windows
guests. systemd 237 (as found in Bionic) gives preference to this
CPUID information when detecting Xen, and thus it erroneously assumes
that the guest is running under Hyper-V. This causes Xen-related
services (and anything else that relies on systemd's VM-detection
functionality) to fail.
I *believe* this is a regression from systemd 229 as used in Xenial —
we have at least a few Xen-based VMs that report as Hyper-V via CPUID
and don't have this issue on that version — but i haven't confirmed
that for certain.
Anyway, i've submitted a ticket with more details to the up-stream
project, and that has now been resolved through a fairly simple change
which applies cleanly to the Bionic systemd sources:
https://github.com/systemd/systemd/issues/8844
Would it be possible to pull this down? As mentioned, Xen-based Ubuntu
VMs can seriously misbehave without it.
Thanks!
See also:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573
---
% lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
% apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10
Candidate: 237-3ubuntu10
Version table:
*** 237-3ubuntu10 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1768104/+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 1768104] [NEW] systemd sometimes misdetects Xen VMs (fixed up-stream)
Public bug reported: It appears that Xen-based VMs sometimes report themselves as Microsoft Hyper-V via CPUID — apparently this is for compatibility with Windows guests. systemd 237 (as found in Bionic) gives preference to this CPUID information when detecting Xen, and thus it erroneously assumes that the guest is running under Hyper-V. This causes Xen-related services (and anything else that relies on systemd's VM-detection functionality) to fail. I *believe* this is a regression from systemd 229 as used in Xenial — we have at least a few Xen-based VMs that report as Hyper-V via CPUID and don't have this issue on that version — but i haven't confirmed that for certain. Anyway, i've submitted a ticket with more details to the up-stream project, and that has now been resolved through a fairly simple change which applies cleanly to the Bionic systemd sources: https://github.com/systemd/systemd/issues/8844 Would it be possible to pull this down? As mentioned, Xen-based Ubuntu VMs can seriously misbehave without it. Thanks! See also: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573 --- % lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 % apt-cache policy systemd systemd: Installed: 237-3ubuntu10 Candidate: 237-3ubuntu10 Version table: *** 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1768104 Title: systemd sometimes misdetects Xen VMs (fixed up-stream) Status in systemd package in Ubuntu: New Bug description: It appears that Xen-based VMs sometimes report themselves as Microsoft Hyper-V via CPUID — apparently this is for compatibility with Windows guests. systemd 237 (as found in Bionic) gives preference to this CPUID information when detecting Xen, and thus it erroneously assumes that the guest is running under Hyper-V. This causes Xen-related services (and anything else that relies on systemd's VM-detection functionality) to fail. I *believe* this is a regression from systemd 229 as used in Xenial — we have at least a few Xen-based VMs that report as Hyper-V via CPUID and don't have this issue on that version — but i haven't confirmed that for certain. Anyway, i've submitted a ticket with more details to the up-stream project, and that has now been resolved through a fairly simple change which applies cleanly to the Bionic systemd sources: https://github.com/systemd/systemd/issues/8844 Would it be possible to pull this down? As mentioned, Xen-based Ubuntu VMs can seriously misbehave without it. Thanks! See also: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573 --- % lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 % apt-cache policy systemd systemd: Installed: 237-3ubuntu10 Candidate: 237-3ubuntu10 Version table: *** 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1768104/+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 1689227] [NEW] systemd power functions do not send broadcast (wall) message
Public bug reported: Running on Xenial, i've found that none of the methods of interacting with systemd's power functions send the wall message as they're supposed to. I have tried all of the following and none of them produce the message: reboot shutdown -r shutdown -r +1 shutdown -r +1 'testing' shutdown -r 1 shutdown -r now shutdown -r now 'testing' systemctl reboot systemctl reboot --message 'testing' There are no errors displayed on the screen after running the command. If i check the journal after the system comes back up i can find no errors there either. A message DOES appear in the journal, if i use `systemctl reboot --message`: May 07 23:11:18 mysrv sudo[1244]: dana : TTY=pts/0 ; PWD=/home/dana ; USER=root ; COMMAND=/bin/systemctl reboot --message testing May 07 23:11:18 mysrv sudo[1244]: pam_unix(sudo:session): session opened for user root by dana(uid=0) May 07 23:11:18 mysrv systemd-logind[634]: System is rebooting (testing). I noticed that if i ran these commands without `sudo`, it'd complain about PolicyKit, so i installed that, thinking maybe it'd help. It did not. As another experiment, i added a call to `wall` to `systemd- reboot.service` via drop-in as below. It works, but i don't consider it an acceptable solution, because it's a hard-coded message and it doesn't show the name of the user that triggered the reboot. [Service] ExecStartPre=-/usr/bin/wall testing It's also worth pointing out that i'm running these commands over SSH; i don't have access to the physical machine right now. OS version: Ubuntu 16.04.2 (Xenial) server Relevant packages (i hope): dbus1.10.6-1ubuntu3.3 libdbus-1-3:amd64 1.10.6-1ubuntu3.3 libdbus-glib-1-2:amd64 0.106-1 libqt5dbus5:amd64 5.5.1+dfsg-16ubuntu7.2 libsystemd0:amd64 229-4ubuntu17 python3-systemd 231-2build1 systemd 229-4ubuntu17 systemd-sysv229-4ubuntu17 PS: There are some related tickets in the system already, but none of them seemed to describe the exact behaviour i was seeing (they were missing wall messages only in certain circumstances — mine are ALWAYS missing). I'm linking them here for completeness, feel free to close this obv if you consider it a duplicate of one of them: Bug # 1448070 Bug # 1512235 There is also this Debian bug, which might be the same, though i have confirmed that this affects not just the SysV-style commands but even `systemctl` itself: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810608 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1689227 Title: systemd power functions do not send broadcast (wall) message Status in systemd package in Ubuntu: New Bug description: Running on Xenial, i've found that none of the methods of interacting with systemd's power functions send the wall message as they're supposed to. I have tried all of the following and none of them produce the message: reboot shutdown -r shutdown -r +1 shutdown -r +1 'testing' shutdown -r 1 shutdown -r now shutdown -r now 'testing' systemctl reboot systemctl reboot --message 'testing' There are no errors displayed on the screen after running the command. If i check the journal after the system comes back up i can find no errors there either. A message DOES appear in the journal, if i use `systemctl reboot --message`: May 07 23:11:18 mysrv sudo[1244]: dana : TTY=pts/0 ; PWD=/home/dana ; USER=root ; COMMAND=/bin/systemctl reboot --message testing May 07 23:11:18 mysrv sudo[1244]: pam_unix(sudo:session): session opened for user root by dana(uid=0) May 07 23:11:18 mysrv systemd-logind[634]: System is rebooting (testing). I noticed that if i ran these commands without `sudo`, it'd complain about PolicyKit, so i installed that, thinking maybe it'd help. It did not. As another experiment, i added a call to `wall` to `systemd- reboot.service` via drop-in as below. It works, but i don't consider it an acceptable solution, because it's a hard-coded message and it doesn't show the name of the user that triggered the reboot. [Service] ExecStartPre=-/usr/bin/wall testing It's also worth pointing out that i'm running these commands over SSH; i don't have access to the physical machine right now. OS version: Ubuntu 16.04.2 (Xenial) server Relevant packages (i hope): dbus1.10.6-1ubuntu3.3 libdbus-1-3:amd64 1.10.6-1ubuntu3.3 libdbus-glib-1-2:amd64 0.106-1 libqt5dbus5:amd64 5.5.1+dfsg-16ubuntu7.2 libsystemd0:amd64 229-4ubuntu17 python3-systemd 231-2build1 systemd 229-4ubuntu17 systemd-sysv229-4ubuntu17 PS: There are some related tickets in the system already, but none of them seemed to describe the exact
[Touch-packages] [Bug 1686878] [NEW] Race condition in pam_motd
Public bug reported:
This is kind of esoteric, but it seems there is a race condition in
pam_motd: If two SSH sessions are started at almost the same time, the
MOTD will appear truncated in the earlier session.
I have replicated this on both Xenial and (after accounting for bug #
1368864) Trusty. Here's an illustration of what happens with the default
MOTD stuff that comes with Trusty server:
# Single SSH session: MOTD looks fine
workstation:~ % ssh server
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-112-generic x86_64)
System information as of Thu Apr 27 21:26:21 CDT 2017
System load: 0.03 Processes: 114
Usage of /: 45.5% of 13.40GB Users logged in: 0
Memory usage: 8% IP address for eth0: 1.2.3.4
Swap usage: 0% IP address for eth1: 5.6.7.8
71 packages can be updated.
0 updates are security updates.
New release '16.04.2 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
*** System restart required ***
Last login: Thu Apr 27 21:25:19 2017 from workstation
server:~ %
# Multiple SSH sessions: MOTD is truncated
workstation:~ % ( sleep 0.25; ssh server /bin/true ) > /dev/null 2>&1 & ssh
server
[1] 93182
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-112-generic x86_64)
System information as of Thu Apr 27 21:26:45 CDT 2017
Last login: Thu Apr 27 21:26:21 2017 from workstation
[1] + done ( sleep 0.25; ssh server /bin/true; ) > /dev/null 2>&1
server:~ %
You might have to play with the `sleep` time to get it to happen.
Obviously this is a contrived scenario. The actual reason i keep running
into the problem is that i use OpenSSH's LocalCommand directive to rsync
(via SSH) my dotfiles to the servers i manage. As soon as i connect to
the server, but before the remote shell starts, OpenSSH fires the rsync
command, which begins a new SSH session, which triggers the race
condition. I suppose the same thing would happen 'in the wild' if two
different users connected at exactly the same time, but that's unlikely
too. It happens with the LocalCommand thing probably over half of the
time though.
An attempt is made in pam_motd.c to make the file-update process atomic,
by dumping the contents to /run/motd.dynamic.new before renaming it to
/run/motd.dynamic -- but obviously that doesn't help here. I was able to
fix the problem by simply appending the current PID to the temp-file
name, like so:
if (do_update && (stat("/etc/update-motd.d", ) == 0)
&& S_ISDIR(st.st_mode))
{
mode_t old_mask = umask(0022);
char tmp[64];
char cmd[256];
sprintf(tmp, "/run/motd.dynamic.new.%d", getpid());
sprintf(cmd, "/usr/bin/env -i
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin run-
parts --lsbsysinit /etc/update-motd.d > %s", tmp);
if (!system(cmd))
rename(tmp, "/run/motd.dynamic");
umask(old_mask);
}
This is probably broken somehow because i'm horrible at C -- plus i
couldn't get the update-motd patch in the libpam-modules package source
to apply cleanly -- otherwise i'd supply my own patch. But i think you
see what i mean.
cheers
** Affects: pam (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1686878
Title:
Race condition in pam_motd
Status in pam package in Ubuntu:
New
Bug description:
This is kind of esoteric, but it seems there is a race condition in
pam_motd: If two SSH sessions are started at almost the same time, the
MOTD will appear truncated in the earlier session.
I have replicated this on both Xenial and (after accounting for bug #
1368864) Trusty. Here's an illustration of what happens with the
default MOTD stuff that comes with Trusty server:
# Single SSH session: MOTD looks fine
workstation:~ % ssh server
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-112-generic x86_64)
System information as of Thu Apr 27 21:26:21 CDT 2017
System load: 0.03 Processes: 114
Usage of /: 45.5% of 13.40GB Users logged in: 0
Memory usage: 8% IP address for eth0: 1.2.3.4
Swap usage: 0% IP address for eth1: 5.6.7.8
71 packages can be updated.
0 updates are security updates.
New release '16.04.2 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
*** System restart required ***
Last login: Thu Apr 27 21:25:19 2017 from workstation
server:~ %
# Multiple SSH sessions: MOTD is truncated
workstation:~ % ( sleep 0.25; ssh server /bin/true ) > /dev/null 2>&1 & ssh
server
[1] 93182
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-112-generic x86_64)
System information as of Thu Apr 27 21:26:45 CDT 2017
Last login: Thu Apr 27 21:26:21 2017 from workstation
[1] + done ( sleep 0.25; ssh server /bin/true; ) > /dev/null 2>&1
server:~
[Touch-packages] [Bug 1498129] Re: Asus Xonar U7 S/PDIF output not recognized by pulseaudio
I managed to add the U7 Echelon to the config file: "Xonar U7 Echelon Ed_" 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1498129 Title: Asus Xonar U7 S/PDIF output not recognized by pulseaudio Status in alsa-driver package in Ubuntu: New Bug description: The external USB audio card Asus Xonar U7 is capable of both analog and digital output. ALSA name for the digital (S/PDIF) output is hw:1,1, and it is listed in aplay -l output, and aplay can output to it: aplay -D plughw:1,1 sample.wav. So, direct alsa sound works fine. However, pulseadio does not recognize the digital output of Xonar U7, it offers only analog output. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-63.103-lowlatency 3.13.11-ckt25 Uname: Linux 3.13.0-63-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aoand 3756 F pulseaudio /dev/snd/controlC0: aoand 3756 F pulseaudio CurrentDesktop: Unity Date: Mon Sep 21 21:29:54 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2011-02-20 (1674 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to trusty on 2014-05-19 (490 days ago) dmi.bios.date: 11/29/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7WET71WW (3.21 ) dmi.board.name: 7448CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7WET71WW(3.21):bd11/29/2012:svnLENOVO:pn7448CTO:pvrThinkPadX200Tablet:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7448CTO dmi.product.version: ThinkPad X200 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1498129/+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 1488056] Re: Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
I have an Ubuntu 15.10 that's up to date, and I'm still seeing the "rejected" message. The seemingly most relevant file is /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf, from the network-manager config file. None of the rules in that file seem to handle all the "(unset)" fields. ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" Status in bind9 package in Ubuntu: Expired Status in network-manager package in Ubuntu: New Bug description: Seeing lots of those log entries. Here an example Aug 24 20:14:36 M1 NetworkManager[748]: [1440404076.494991] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Aug 24 20:14:36 M1 dbus[792]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.84" (uid=0 pid=3300 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=748 comm="/usr/sbin/NetworkManager --no-daemon ") Attached info might help locating the issue. Thanks for any clues. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dnsmasq 2.72-3ubuntu0.1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Mon Aug 24 23:08:37 2015 InstallationDate: Installed on 2014-10-31 (297 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1488056/+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 916356] Dana and Paula House Celebration - Boyle Heights
Dana and Paula open house party this sunday View this email in your browser (http://us4.campaign- archive2.com/?u=dad1b7a19a0262b96767efef0=f2066d4de8=2fd5b154b9) We're having an open house party at our Boyle Heights Craftsman Revival house. Sunday 11 - 3. 2230 Inez st. L.A. 90023 We're just celebrating for fun and are proud to have you here. It took a lot of work and love to make this space beautiful. We hope you can come. Dana and Paula ** (http://danaross.us4.list-manage1.com/track/click?u=dad1b7a19a0262b96767efef0=554432df9e=2fd5b154b9) ** (http://danaross.us4.list-manage.com/track/click?u=dad1b7a19a0262b96767efef0=3610314c6d=2fd5b154b9) ** (http://danaross.us4.list-manage2.com/track/click?u=dad1b7a19a0262b96767efef0=8397101e9e=2fd5b154b9) Want to change how you receive these emails? You can ** update your preferences (http://danaross.us4.list-manage.com/profile?u=dad1b7a19a0262b96767efef0=4520cc1d96=2fd5b154b9) or ** unsubscribe from this list (http://danaross.us4.list-manage1.com/unsubscribe?u=dad1b7a19a0262b96767efef0=4520cc1d96=2fd5b154b9=f2066d4de8) This email was sent to 916...@bugs.launchpad.net (mailto:916...@bugs.launchpad.net) why did I get this? (http://danaross.us4.list-manage.com/about?u=dad1b7a19a0262b96767efef0=4520cc1d96=2fd5b154b9=f2066d4de8) unsubscribe from this list (http://danaross.us4.list-manage1.com/unsubscribe?u=dad1b7a19a0262b96767efef0=4520cc1d96=2fd5b154b9=f2066d4de8) update subscription preferences (http://danaross.us4.list-manage.com/profile?u=dad1b7a19a0262b96767efef0=4520cc1d96=2fd5b154b9) cultureandmusic . 13510 Erwin Street . Los Angeles, CA 91401 . USA Email Marketing Powered by MailChimp http://www.mailchimp.com/monkey-rewards/?utm_source=freemium_newsletter_medium=email_campaign=monkey_rewards=dad1b7a19a0262b96767efef0=1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/916356 Title: unity-applications-daemon crashed with SIGSEGV in dee_sequence_model_free_row() Status in libunity: Fix Released Status in Unity: Fix Released Status in Unity Distro Priority: Fix Released Status in unity-lens-applications: Fix Released Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-lens-applications package in Ubuntu: Fix Released Status in libunity source package in Precise: Fix Released Status in unity source package in Precise: Fix Released Status in unity-lens-applications source package in Precise: Fix Released Bug description: When I start up ubuntu 12.04, I got this bug report ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-lens-applications 5.0.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.90-0ubuntu2 Architecture: amd64 Date: Sat Jan 14 10:50:58 2012 ExecutablePath: /usr/lib/unity-lens-applications/unity-applications-daemon InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111212) ProcCmdline: /usr/lib/unity-lens-applications/unity-applications-daemon ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_SG:en LANG=en_SG.UTF-8 SegvAnalysis: Segfault happened at: 0x7fe201352e38:mov0x0(%rbp,%r14,8),%rdi PC (0x7fe201352e38) ok source "0x0(%rbp,%r14,8)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-lens-applications StacktraceTop: ?? () from /usr/lib/libdee-1.0.so.4 ?? () from /usr/lib/libdee-1.0.so.4 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-applications-daemon crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to precise on 2012-01-13 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/916356/+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
