[Touch-packages] [Bug 2023322]
(In reply to Michael Catanzaro from comment #62) > Hi Craig and Thomas (and Emil if you're still around): if you're still > encountering problems with NVIDIA graphics, please report new a bug and > leave a comment here linking to the new bug. My problem was on legacy nvidia driver, and newer versions wouldn't even start. But I now know a workaround (GSK_RENDERER=cairo) and don't expect there will be a fix for my old driver anyway. https://gitlab.gnome.org/GNOME/gtk/-/issues/5858 -- 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/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL syst
[Touch-packages] [Bug 2025176] Re: External hard disk fails to automount in /etc/fstab with message FEATURE_C12
I've solved this issue by upgrading e2fsprogs: wget http://ftp.de.debian.org/debian/pool/main/e/e2fsprogs/e2fsprogs_1.47.0-2_arm64.deb wget http://ftp.de.debian.org/debian/pool/main/e/e2fsprogs/libext2fs2_1.47.0-2_arm64.deb ** Package changed: util-linux (Ubuntu) => e2fsprogs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/2025176 Title: External hard disk fails to automount in /etc/fstab with message FEATURE_C12 Status in e2fsprogs package in Ubuntu: New Bug description: I am having a problem with auto mounting an external 14TB 3.5" hard disk on Ubuntu 22.04 (arm64) (arm board). The drive is formatted using ext4 however this was done on a amd64 based Ubuntu 23.04 install (laptop). I tried to automount on the 22.04 install by using /etc/fstab, however the system would then fail to boot, entering emergency mode. Terminal output: [FAILED]: Failed to start File System Check on /dev/disk/by-uuuid/xx-xx-xx-xx-xx See 'systemctl status "systemd-fsck@dev-disk-by\\xx\\xx\\xx\\xx\\xx' [DEPEND] Dependency failed for /mnt/share/external_14tb_drive The particular error is: /dev/xxx has unsupported feature(s): FEATURE_C12 /etc/fstab UUID=xx-xx-xx-xx-xx /mnt/share/external_14tb_drive ext4 defaults,noatime,nofail 0 2 arm board description:Ubuntu 22.04.2 LTS Release: 22.04 apt-cache policy e2fsprogs e2fsprogs: Installed: 1.46.5-2ubuntu1.1 Candidate: 1.46.5-2ubuntu1.1 Version table: *** 1.46.5-2ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages 100 /var/lib/dpkg/status 1.46.5-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages apt-cache policy util-linux util-linux: Installed: 2.37.2-4ubuntu3 Candidate: 2.37.2-4ubuntu3 Version table: *** 2.37.2-4ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status Laptop description: Ubuntu 23.04 Release: 23.04 apt-cache policy e2fsprogs e2fsprogs: Installed: 1.47.0-1ubuntu1 Candidate: 1.47.0-1ubuntu1 Version table: *** 1.47.0-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status util-linux: Installed: 2.38.1-4ubuntu1 Candidate: 2.38.1-4ubuntu1 Version table: *** 2.38.1-4ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The only option I have is to manually mount it after boot which is not convenient as it a server board. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: util-linux 2.37.2-4ubuntu3 Uname: Linux 5.10.110-rockchip-rk3588 aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue Jun 27 19:38:40 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025176/+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 2025176] Re: External hard disk fails to automount in /etc/fstab with message FEATURE_C12
** Description changed: I am having a problem with auto mounting an external 14TB 3.5" hard disk on Ubuntu 22.04 (arm64) (arm board). The drive is formatted using ext4 however this was done on a amd64 based Ubuntu 23.04 install (laptop). I tried to automount on the 22.04 install by using /etc/fstab, however the system would then fail to boot, entering emergency mode. Terminal output: [FAILED]: Failed to start File System Check on /dev/disk/by-uuuid/xx-xx-xx-xx-xx See 'systemctl status "systemd-fsck@dev-disk-by\\xx\\xx\\xx\\xx\\xx' [DEPEND] Dependency failed for /mnt/share/external_14tb_drive The particular error is: /dev/xxx has unsupported feature(s): FEATURE_C12 /etc/fstab UUID=xx-xx-xx-xx-xx /mnt/share/external_14tb_drive ext4 defaults,noatime,nofail 0 2 arm board description:Ubuntu 22.04.2 LTS Release: 22.04 + apt-cache policy e2fsprogs + e2fsprogs: + Installed: 1.46.5-2ubuntu1.1 + Candidate: 1.46.5-2ubuntu1.1 + Version table: + *** 1.46.5-2ubuntu1.1 500 + 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages + 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages + 100 /var/lib/dpkg/status + 1.46.5-2ubuntu1 500 + 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages + apt-cache policy util-linux util-linux: Installed: 2.37.2-4ubuntu3 Candidate: 2.37.2-4ubuntu3 Version table: *** 2.37.2-4ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status Laptop description: Ubuntu 23.04 Release: 23.04 + + apt-cache policy e2fsprogs + e2fsprogs: + Installed: 1.47.0-1ubuntu1 + Candidate: 1.47.0-1ubuntu1 + Version table: + *** 1.47.0-1ubuntu1 500 + 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages + 100 /var/lib/dpkg/status util-linux: Installed: 2.38.1-4ubuntu1 Candidate: 2.38.1-4ubuntu1 Version table: *** 2.38.1-4ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The only option I have is to manually mount it after boot which is not convenient as it a server board. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: util-linux 2.37.2-4ubuntu3 Uname: Linux 5.10.110-rockchip-rk3588 aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue Jun 27 19:38:40 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2025176 Title: External hard disk fails to automount in /etc/fstab with message FEATURE_C12 Status in util-linux package in Ubuntu: New Bug description: I am having a problem with auto mounting an external 14TB 3.5" hard disk on Ubuntu 22.04 (arm64) (arm board). The drive is formatted using ext4 however this was done on a amd64 based Ubuntu 23.04 install (laptop). I tried to automount on the 22.04 install by using /etc/fstab, however the system would then fail to boot, entering emergency mode. Terminal output: [FAILED]: Failed to start File System Check on /dev/disk/by-uuuid/xx-xx-xx-xx-xx See 'systemctl status "systemd-fsck@dev-disk-by\\xx\\xx\\xx\\xx\\xx' [DEPEND] Dependency failed for /mnt/share/external_14tb_drive The particular error is: /dev/xxx has unsupported feature(s): FEATURE_C12 /etc/fstab UUID=xx-xx-xx-xx-xx /mnt/share/external_14tb_drive ext4 defaults,noatime,nofail 0 2 arm board description:Ubuntu 22.04.2 LTS Release: 22.04 apt-cache policy e2fsprogs e2fsprogs: Installed: 1.46.5-2ubuntu1.1 Candidate: 1.46.5-2ubuntu1.1 Version table: *** 1.46.5-2ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages 100 /var/lib/dpkg/status 1.46.5-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages apt-cache policy util-linux util-linux: Installed: 2.37.2-4ubuntu3 Candidate: 2.37.2-4ubuntu3 Version table: *** 2.37.2-4ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status Laptop description: Ubuntu 23.04 Release: 23.04 apt-cache policy e2fsprogs e2fsprogs: Installed: 1.47.0-1ubuntu1 Candidate: 1.47.0-1ubuntu1 Version table: *** 1.47.0-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
[Touch-packages] [Bug 2025176] [NEW] External hard disk fails to automount in /etc/fstab with message FEATURE_C12
Public bug reported: I am having a problem with auto mounting an external 14TB 3.5" hard disk on Ubuntu 22.04 (arm64) (arm board). The drive is formatted using ext4 however this was done on a amd64 based Ubuntu 23.04 install (laptop). I tried to automount on the 22.04 install by using /etc/fstab, however the system would then fail to boot, entering emergency mode. Terminal output: [FAILED]: Failed to start File System Check on /dev/disk/by-uuuid/xx-xx-xx-xx-xx See 'systemctl status "systemd-fsck@dev-disk-by\\xx\\xx\\xx\\xx\\xx' [DEPEND] Dependency failed for /mnt/share/external_14tb_drive The particular error is: /dev/xxx has unsupported feature(s): FEATURE_C12 /etc/fstab UUID=xx-xx-xx-xx-xx /mnt/share/external_14tb_drive ext4 defaults,noatime,nofail 0 2 arm board description: Ubuntu 22.04.2 LTS Release:22.04 apt-cache policy util-linux util-linux: Installed: 2.37.2-4ubuntu3 Candidate: 2.37.2-4ubuntu3 Version table: *** 2.37.2-4ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status Laptop description: Ubuntu 23.04 Release:23.04 util-linux: Installed: 2.38.1-4ubuntu1 Candidate: 2.38.1-4ubuntu1 Version table: *** 2.38.1-4ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The only option I have is to manually mount it after boot which is not convenient as it a server board. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: util-linux 2.37.2-4ubuntu3 Uname: Linux 5.10.110-rockchip-rk3588 aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue Jun 27 19:38:40 2023 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 jammy uec-images ** Description changed: I am having a problem with auto mounting an external 14TB 3.5" hard disk - on Ubuntu 22.04 (arm64). The drive is formatted using ext4 however this - was done on a amd64 based Ubuntu 23.04 install. + on Ubuntu 22.04 (arm64) (arm board). The drive is formatted using ext4 + however this was done on a amd64 based Ubuntu 23.04 install (laptop). I tried to automount on the 22.04 install by using /etc/fstab, however the system would then fail to boot, entering emergency mode. Terminal output: [FAILED]: Failed to start File System Check ono /dev/disk/by-uuuid/xx-xx-xx-xx-xx See 'systemctl status "systemd-fsck@dev-disk-by\\xx\\xx\\xx\\xx\\xx' [DEPEND] Dependency failed for /mnt/share/external_14tb_drive The particular error is: /dev/xxx has unsupported feature(s): FEATURE_C12 /etc/fstab UUID=xx-xx-xx-xx-xx /mnt/share/external_14tb_drive ext4 defaults,noatime,nofail 0 2 - Laptop description: Ubuntu 23.04 - Release: 23.04 - - util-linux: - Installed: 2.38.1-4ubuntu1 - Candidate: 2.38.1-4ubuntu1 - Version table: - *** 2.38.1-4ubuntu1 500 - 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages - 100 /var/lib/dpkg/status - - arm board description:Ubuntu 22.04.2 LTS Release: 22.04 apt-cache policy util-linux util-linux: - Installed: 2.37.2-4ubuntu3 - Candidate: 2.37.2-4ubuntu3 - Version table: - *** 2.37.2-4ubuntu3 500 - 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages - 100 /var/lib/dpkg/status + Installed: 2.37.2-4ubuntu3 + Candidate: 2.37.2-4ubuntu3 + Version table: + *** 2.37.2-4ubuntu3 500 + 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages + 100 /var/lib/dpkg/status + + Laptop description: Ubuntu 23.04 + Release: 23.04 + + util-linux: + Installed: 2.38.1-4ubuntu1 + Candidate: 2.38.1-4ubuntu1 + Version table: + *** 2.38.1-4ubuntu1 500 + 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages + 100 /var/lib/dpkg/status The only option I have is to manually mount it after boot which is not convenient as it a server board. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: util-linux 2.37.2-4ubuntu3 Uname: Linux 5.10.110-rockchip-rk3588 aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue Jun 27 19:38:40 2023 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I am having a problem with auto mounting an external 14TB 3.5" hard disk on Ubuntu 22.04 (arm64) (arm board). The drive
[Touch-packages] [Bug 2000880] Re: systemd-networkd: ActivationPolicy ignored in VLANs
Thanks so much! I really appreciate the help here. I can confirm that 249.11-0ubuntu3.8 fixes this bug. A VLAN with ActivationPolicy=manual now no longer comes up at boot, as expected, but can be brought up manually with networkctl. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done-jammy -- 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/2000880 Title: systemd-networkd: ActivationPolicy ignored in VLANs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] The ActivationPolicy property in .network files is ignored for VLANs. [Test Plan] * On a Jammy machine with an interface named ens3, create the following configs: $ cat > /etc/systemd/network/10-vlan18.netdev << EOF [NetDev] Name=vlan18 Kind=vlan [VLAN] Id=18 EOF $ cat > /etc/systemd/network/20-vlan18.network << EOF [Match] Name=vlan18 [Network] Address=10.10.1.1/24 [Link] ActivationPolicy=manual EOF $ cat > /etc/systemd/network/30-ens3.network << EOF [Match] Name=ens3 [Network] DHCP=ipv4 VLAN=vlan18 EOF * Reboot the machine * On an affected machine, the vlan18@ens3 interface will have a configured IP at boot, despite the ActivationPolicy=manual setting in /etc/systemd/network/20-vlan18.network. On a patched machine, the interface should not have a configured IP. [Where problems could occur] The patch adds a condition where a netdev is not yet ready to be created. Specifically, it makes sure stacked netdevs are not created before their underlying link is activated. If we saw any problems, it would be related to netdev creation. [Original Description] This has been fixed upstream, see Upstream bug: https://github.com/systemd/systemd/issues/22593 Any chance of a backport of the fix to 22.04? Fix: https://github.com/systemd/systemd-stable/pull/211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000880/+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 2000880] [NEW] systemd-networkd: ActivationPolicy ignored in VLANs
Public bug reported: This has been fixed upstream, see Upstream bug: https://github.com/systemd/systemd/issues/22593 Any chance of a backport of the fix to 22.04? Fix: https://github.com/systemd/systemd-stable/pull/211 ** 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/2000880 Title: systemd-networkd: ActivationPolicy ignored in VLANs Status in systemd package in Ubuntu: New Bug description: This has been fixed upstream, see Upstream bug: https://github.com/systemd/systemd/issues/22593 Any chance of a backport of the fix to 22.04? Fix: https://github.com/systemd/systemd-stable/pull/211 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000880/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Ah, didn't realize Debian had a different limit. Thanks @juliank. @anourzad, I'm not sure I would want to start adding custom steps to the kernel update path. I'm much more inclined to add an /etc option for a supported automatic mechanism, like compression or module selection. @adrien-n, great notes in #125, I'm sure this will help others. -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Triaged Status in grub2-unsigned package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff #endif ``` If everything works as expected, then i386 should working good. If not lucky, based on “UEFI writers’ guide”[2], the i386 will get > 4GB memory region and never be able to access. [Other Info] * Upstream grub2 bug #61058 https://savannah.gnu.org/bugs/index.php?61058 * Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320 * Test grubx64.efi: https://people.c
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Confirmed that reducing the size of the initrd.img slightly allowed my machine to boot. I just enabled `COMPRESSLEVEL=19` with `COMPRESS=zstd` (default on debian) in initramfs.conf. That reduced my initrd.img size from 72MB to 62MB, which allowed my machine to boot. Ultimately, I set `MODULES=dep` (instead of `MODULES=most`) and reverted the compression to defaults. This reduced my initrd.img to 22MB, which includes Intel microcode (specific binary), nvme, crypto, and lvm support, among other things. --- For the record: My machine is running Debian bookworm with the Nvidia proprietary drivers with 32GB. I first noticed the issue when, coincidentally, upgrading from kernel 5.19 to 6.0. ``` Loading Linux 6.0.0-4amd64 ... Loading initial ramdisk ... error: out of memory. Press any key to continue... ``` -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Triaged Status in grub2-unsigned package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available memory. * When users grown the initramfs, then probably will get initramfs not found which really annoyed and impact the user experience (system not able to boot). [Test Plan] * detailed instructions how to reproduce the bug: 1. Any method to grow the initramfs, such as install nvidia-driver. 2. If developers would like to reproduce, then could dd if=/dev/random of=... bs=1M count=500, something like: ``` $ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file #!/bin/sh PREREQ="" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac . /usr/share/initramfs-tools/hook-functions dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500 ``` And then update-initramfs * After applying my patches, the issue is gone. * I did also test my test grubx64.efi in: 1. X86_64 qemu with 1.1. 60M initramfs + 5.15.0-37-generic kernel 1.2. 565M initramfs + 5.17.0-1011-oem kernel 2. Amd64 HP mobile workstation with 2.1. 65M initramfs + 5.15.0-39-generic kernel 2.2. 771M initramfs + 5.17.0-1011-oem kernel All working well. [Where problems could occur] * The changes almost in i386/efi, thus the impact will be in the i386 / x86_64 EFI system. The other change is to modify the “grub-core/kern/efi/mm.c” but I use the original addressing for “arm/arm64/ia64/riscv32/riscv64”. Thus it should not impact them. * There is a “#if defined(__x86_64__)” which intent to limit the > 32bits code in i386 system and also ``` #if defined (__code_model_large__) -#define GRUB_EFI_MAX_USABLE_ADDRESS 0x +#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__ +#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff #else #define GRUB_EFI_MAX_USABLE_ADDRESS 0x7f
[Touch-packages] [Bug 1991661] Re: systemd mounts /run without noexec
Hi, I asked the original question, and tbh, I'm only just following along (I haven't really spent much time looking at initramfs/systemd). I'm just wondering, is this something that's likely to be changed for the AWS servers? Or should I use the suggestions from Andrew Lowther[1] on how I could modify the "/usr/share/initramfs-tools/init" and run update-initramfs... or disable "/etc/default/grub.d/40-force-partuuid.cfg", and run update- grub? If so, I'm not sure what the risks are (e.g. I'd rather have a server that can boot; and I assume "initramfs-tools" could get an update in the future that replaces the modified "init" script, so the noexec would be lost again?). Previously[2] this kind of thing was seen as a "High" severity problem by Tenable (I'm not sure why). In my case, I'd simply like to make sure the "www-data" user (used by Apache/PHP) can only write to folders that are on noexec partitions (the idea being "defence in depth", not perfect, just if anyone using the website was somehow able to write arbitrary files to disk, then they cannot be executed normally, while accepting that shell and other scripts can still be executed). [1] https://askubuntu.com/a/1432445/924107 [2] https://www.tenable.com/plugins/nessus/73180 -- 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/1991661 Title: systemd mounts /run without noexec Status in initramfs-tools package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: initramfs-tools in Bionic+, when mounting the filesystem, mounts /run with noexec Cloud images run without initramfs and rely on systemd for the mounts. systemd, however, mounts /run without noexec. Snip from mount-setup.c (either in src/core/mount-setup.c < 248 or src/shared/mount-setup.c in >= 248 ) ``` #if ENABLE_SMACK { "tmpfs", "/run", "tmpfs", "mode=755,smackfsroot=*" TMPFS_LIMITS_RUN, MS_NOSUID|MS_NODEV|MS_STRICTATIME, mac_smack_use, MNT_FATAL }, #endif { "tmpfs", "/run", "tmpfs", "mode=755" TMPFS_LIMITS_RUN, MS_NOSUID|MS_NODEV|MS_STRICTATIME, NULL, MNT_FATAL|MNT_IN_CONTAINER }, ``` Originally raised in an askubuntu forum: https://askubuntu.com/questions/1432383/mounting-run-as-noexec/1433208 CPC hasn't received word from any partners yet, but it does constitute a possible regression from how the system was mounted in Bionic and Focal before moving to optimized boots in 2020/2021. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1991661/+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 1951279] Re: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds
I have the same issue. It's preventing me from doing some fairly important things, without an obvious workaround at the moment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1951279 Title: OpenSSL 1.1.1f raise a segmentation faults on Arm64 builds Status in openssl package in Ubuntu: Incomplete Bug description: Description --- It seems that current Ubuntu 20.04 (Focal) distribution for Arm64/Aarch64 raise a segmentation fault when certain validates some certificates. This issue affects only to Arm64/Aarch64 all the tools statically or dynamically linked with this version of the library are affected (Libcurl4, Curl, Wget, OpenJDK, Curl-PHP, etc). Environment and platform Linux 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24 14:29:20 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux Steps to reproduce -- 1. Run: curl -v https://graph.facebook.com/v12.0/act_111/ or wget https://graph.facebook.com/v12.0/act_111/ Result received --- Segmentation fault (core dumped) Notes - This bug was found by the Curl users: See: https://github.com/curl/curl/issues/8024 I believe that this bug is related to https://ubuntu.com/security/CVE-2020-1967 that maybe used as a vector point for code injection. Actually there isn't any replacement for OpenSSL 1.1.1f for Focal (Arm64), so it makes difficult to use Ubuntu 20.04 in a production environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1951279/+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 1902430] [NEW] package ca-certificates 20201027ubuntu0.20.10.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exi
Public bug reported: I just reinstalled Ubuntu 20.10 on RPi 4 (4GB) ProblemType: Package DistroRelease: Ubuntu 20.10 Package: ca-certificates 20201027ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 AptOrdering: ca-certificates:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: skip Date: Sun Nov 1 07:18:27 2020 DuplicateSignature: package:ca-certificates:20201027ubuntu0.20.10.1 Setting up ca-certificates (20201027ubuntu0.20.10.1) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package ca-certificates (--configure): installed ca-certificates package post-installation script subprocess returned error exit status 1 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20201022 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: ca-certificates Title: package ca-certificates 20201027ubuntu0.20.10.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1902430 Title: package ca-certificates 20201027ubuntu0.20.10.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: I just reinstalled Ubuntu 20.10 on RPi 4 (4GB) ProblemType: Package DistroRelease: Ubuntu 20.10 Package: ca-certificates 20201027ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 AptOrdering: ca-certificates:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: skip Date: Sun Nov 1 07:18:27 2020 DuplicateSignature: package:ca-certificates:20201027ubuntu0.20.10.1 Setting up ca-certificates (20201027ubuntu0.20.10.1) ... debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable dpkg: error processing package ca-certificates (--configure): installed ca-certificates package post-installation script subprocess returned error exit status 1 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20201022 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: ca-certificates Title: package ca-certificates 20201027ubuntu0.20.10.1 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1902430/+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 1896110] Re: Favorites side bar empty when login in with USB pluged in
Update - If I lock the screen and then unlock it - the Side bar comes back and works as normal. Screenshot attached ** Attachment added: "Screen shot of problem" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1896110/+attachment/5411879/+files/Broken.png -- 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/1896110 Title: Favorites side bar empty when login in with USB pluged in Status in xorg package in Ubuntu: New Bug description: If I connect a USB key to the computer then login the Favorites side bar is empty and the Application launcher does not work. The mouse and keyboard still work Removing the USB key does not resolve the issue Removing the USB key and then logging out and back in again resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 07:32:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-45-generic, x86_64: installed nvidia, 440.100, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop) [17aa:3140] NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 730] [1462:3380] InstallationDate: Installed on 2020-05-28 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 10TXCTO1WW ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=8f7f8957-ea10-4c4f-aa8c-0b2db299cab5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: M22KT42A dmi.board.name: 3140 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258133898759 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM22KT42A:bd12/23/2019:svnLENOVO:pn10TXCTO1WW:pvrV530S-07ICB:rvnLENOVO:rn3140:rvrSDK0J40700WIN3258133898759:cvnLENOVO:ct3:cvrNone: dmi.product.family: V530S-07ICB dmi.product.name: 10TXCTO1WW dmi.product.sku: LENOVO_MT_10TX_BU_Lenovo_FM_V530S-07ICB dmi.product.version: V530S-07ICB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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/1896110/+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 1896110] [NEW] Favorites side bar empty when login in with USB pluged in
Public bug reported: If I connect a USB key to the computer then login the Favorites side bar is empty and the Application launcher does not work. The mouse and keyboard still work Removing the USB key does not resolve the issue Removing the USB key and then logging out and back in again resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 07:32:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-45-generic, x86_64: installed nvidia, 440.100, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop) [17aa:3140] NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 730] [1462:3380] InstallationDate: Installed on 2020-05-28 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 10TXCTO1WW ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=8f7f8957-ea10-4c4f-aa8c-0b2db299cab5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: M22KT42A dmi.board.name: 3140 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN 3258133898759 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM22KT42A:bd12/23/2019:svnLENOVO:pn10TXCTO1WW:pvrV530S-07ICB:rvnLENOVO:rn3140:rvrSDK0J40700WIN3258133898759:cvnLENOVO:ct3:cvrNone: dmi.product.family: V530S-07ICB dmi.product.name: 10TXCTO1WW dmi.product.sku: LENOVO_MT_10TX_BU_Lenovo_FM_V530S-07ICB dmi.product.version: V530S-07ICB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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 focal ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Favorites side bar empty when login in with USB pluged in Status in xorg package in Ubuntu: New Bug description: If I connect a USB key to the computer then login the Favorites side bar is empty and the Application launcher does not work. The mouse and keyboard still work Removing the USB key does not resolve the issue Removing the USB key and then logging out and back in again resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 18 07:32:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-45-generic, x86_64: installed nvidia, 440.100, 5.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Subsystem: Lenovo UHD Graphics 630 (Desktop) [17aa:3140] NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 730] [1462:3380] InstallationDate: Installed on 2020-05-28 (111 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 10TXCTO1WW ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic root=UUID=8f7f8957-ea10-4c4f-aa8c-0b2db299cab5 ro quiet splash vt.handoff=7 So
[Touch-packages] [Bug 1892712] Re: Printing garbage to Brother HL-L2375DW printer
Bug #1832646 sounds similar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1892712 Title: Printing garbage to Brother HL-L2375DW printer Status in cups package in Ubuntu: New Bug description: Starting a few weeks ago, sometimes trying to print ends up printing pages and pages of garbage/junk/mojibake. It's not all the time. Printer drivers are somewhat mysterious, because if I delete them, they automatically reappear. Often a program will list two printer drivers for the one printer, and one of them prints okay while the other prints garbage, and it's not at all obvious which is which. This affects two Ubuntu PCs, one a desktop running Ubuntu 20.04.1, the other a laptop running Lubuntu 20.04.1. The printer is on the network. I guess the computers find it via Zeroconf. The problem seems to be Ubuntu, rather than the printer, because printing from a Windows PC works fine. And, for months, printing from Ubuntu also worked fine. I also noticed earlier, several months back, that double-sided printing was misbehaving, always flipping on the short edge rather than the long edge, no matter which was selected. Short edge is the setting I usually don't want -- the other side is effectively upside down. I have also noticed that selecting 2 or more copies doesn't print multiple copies, but just one copy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1892712/+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 1892712] [NEW] Printing garbage to Brother HL-L2375DW printer
Public bug reported: Starting a few weeks ago, sometimes trying to print ends up printing pages and pages of garbage/junk/mojibake. It's not all the time. Printer drivers are somewhat mysterious, because if I delete them, they automatically reappear. Often a program will list two printer drivers for the one printer, and one of them prints okay while the other prints garbage, and it's not at all obvious which is which. This affects two Ubuntu PCs, one a desktop running Ubuntu 20.04.1, the other a laptop running Lubuntu 20.04.1. The printer is on the network. I guess the computers find it via Zeroconf. The problem seems to be Ubuntu, rather than the printer, because printing from a Windows PC works fine. And, for months, printing from Ubuntu also worked fine. I also noticed earlier, several months back, that double-sided printing was misbehaving, always flipping on the short edge rather than the long edge, no matter which was selected. Short edge is the setting I usually don't want -- the other side is effectively upside down. I have also noticed that selecting 2 or more copies doesn't print multiple copies, but just one copy. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: printer -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1892712 Title: Printing garbage to Brother HL-L2375DW printer Status in cups package in Ubuntu: New Bug description: Starting a few weeks ago, sometimes trying to print ends up printing pages and pages of garbage/junk/mojibake. It's not all the time. Printer drivers are somewhat mysterious, because if I delete them, they automatically reappear. Often a program will list two printer drivers for the one printer, and one of them prints okay while the other prints garbage, and it's not at all obvious which is which. This affects two Ubuntu PCs, one a desktop running Ubuntu 20.04.1, the other a laptop running Lubuntu 20.04.1. The printer is on the network. I guess the computers find it via Zeroconf. The problem seems to be Ubuntu, rather than the printer, because printing from a Windows PC works fine. And, for months, printing from Ubuntu also worked fine. I also noticed earlier, several months back, that double-sided printing was misbehaving, always flipping on the short edge rather than the long edge, no matter which was selected. Short edge is the setting I usually don't want -- the other side is effectively upside down. I have also noticed that selecting 2 or more copies doesn't print multiple copies, but just one copy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1892712/+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 1404172] Re: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Seeing this in 20.04.1 with lightdm 1.30.0. see output attached. ** Attachment added: "output from journalctl using unit=lightdm" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1404172/+attachment/5400542/+files/lightdm.bug-1404172 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1404172 Title: lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Status in One Hundred Papercuts: Confirmed Status in Light Display Manager: Confirmed Status in systemd: New Status in lightdm package in Ubuntu: Confirmed Bug description: auth.log complaints: Dec 19 07:24:42 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 19 07:24:42 u32 lightdm: PAM adding faulty module: pam_kwallet.so Dec 19 07:24:42 u32 lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Dec 19 07:24:42 u32 systemd-logind[656]: New session c1 of user lightdm. Dec 19 07:24:42 u32 systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0) Dec 19 07:24:46 u32 lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 19 07:24:46 u32 lightdm: PAM adding faulty module: pam_kwallet.so Dec 19 07:24:46 u32 lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "oem" Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm-greeter:session): session closed for user lightdm Dec 19 07:24:53 u32 lightdm: pam_unix(lightdm:session): session opened for user oem by (uid=0) As per lp:1309535 #18 comment such 'warnings' should be silenced (as they scared unawared users about the both needs of pam's gnome/kde) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-7.8-generic 3.18.0 Uname: Linux 3.18.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Fri Dec 19 10:47:07 2014 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1404172/+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 1878955] [NEW] resolved dhclient-enter-hook complains about an empty file
Public bug reported: When starting/using `dhclient`, it will often return an error such as: cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty This is due to the use of `cmp` in "/etc/dhcp/dhclient-enter- hooks.d/resolved" Because the $oldstate file can be empty, or different, it should use `cmp --quiet` This happens when "/run/systemd/resolved.conf.d/isc- dhcp-v*-$interface.conf" files do not exist, or when the content changes. This is very loosely related to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183 ** 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/1878955 Title: resolved dhclient-enter-hook complains about an empty file Status in systemd package in Ubuntu: New Bug description: When starting/using `dhclient`, it will often return an error such as: cmp: EOF on /tmp/tmp.yCyV6zBzhB which is empty This is due to the use of `cmp` in "/etc/dhcp/dhclient-enter- hooks.d/resolved" Because the $oldstate file can be empty, or different, it should use `cmp --quiet` This happens when "/run/systemd/resolved.conf.d/isc- dhcp-v*-$interface.conf" files do not exist, or when the content changes. This is very loosely related to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1878955/+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 1853879] Re: Dell E310dw: Default driver doesn't work, driverless fails on sides=two-sided-long-edge
I'm having this problem -- printing duplex on short edge instead of long edg -- with a Brother HL-L2375DW. I'm running Ubuntu 19.10. It was working in Ubuntu 19.04. But, I thought it had also been printing correctly previously in 19.10, until it stopped working more recently. But I'm not 100% sure when it stopped working, since I don't print duplex very often. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1853879 Title: Dell E310dw: Default driver doesn't work, driverless fails on sides =two-sided-long-edge Status in cups package in Ubuntu: Confirmed Bug description: Dell E310dw printer which worked well on 19.04 has problems in 19.10: First, I went through the CUPS web interface to add the printer. The interface gave me a choice of two entries with the same name plus one with "driverless" added. I chose the first entry (not driverless) and completed adding the printer. On the Printers page, the Dell was now listed. When I tried "Print Test Page", I got many pages each containing a single line of symbols. I deleted the printer in the web interface, intending to start again and choose the second option. But after I did Delete Printer, CUPS took me back to the Printers page which now listed: Dell_Printer_E310dw@DELL316BAA.local Dell Printer E310dw, driverless, cups-filters 1.25.11 So I clicked on that printer and tried Print Test Page, which worked. So then I tried a duplex print (which is really what I need this morning): lp -o sides=two-sided-long-edge -o collate=true -d Dell_Printer_E310dw@DELL316BAA.local filename.pdf It printed the PDF 2-sided, but with the sides flipped around the short edge, as if it was a landscape print. I tried the same command with sides=two-sided-short-edge and it flipped the same way. So sides is handling duplex but ignoring which edge is supposed to be used, and defaulting to landscape which I'd guess is less commonly what people want. This is all using what's built into Ubuntu. I haven't yet downloaded any extra drivers from Dell's site since Ubuntu claims to have a driver for the printer, and I'm pretty sure it was working in 19.04 (I may still have a working 19.04 to check that, if it would help). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Mon Nov 25 09:58:21 2019 InstallationDate: Installed on 2019-10-10 (45 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lpstat: device for Brother_HL-3170CDW_series: dnssd://Brother%20HL-3170CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4251dee device for Dell_Printer_E310dw@DELL316BAA.local: implicitclass://Dell_Printer_E310dw%40DELL316BAA.local/ MachineType: LENOVO 20QDCTO1WW Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd', '/etc/cups/ppd/Brother_HL-3170CDW_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/dell_printer_e31...@dell316baa.local.ppd: Permission denied grep: /etc/cups/ppd/Brother_HL-3170CDW_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=a5868be6-8495-47af-a190-9af5fdc9b419 ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET30W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET30W(1.13):bd07/04/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853879/+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 1504079] Re: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()
Looks like this bug should be reported on Gitlab rather than Gnome Bugzilla. There are several tracker subprojects on Gitlab. I'm guessing this bug should be reported on one of: https://gitlab.gnome.org/GNOME/tracker-miners or, https://gitlab.gnome.org/GNOME/tracker -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1504079 Title: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps() Status in tracker package in Ubuntu: Confirmed Bug description: i need ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: tracker-extract 1.4.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic i686 ApportVersion: 2.19-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Oct 8 16:04:40 2015 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2015-09-13 (25 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) ProcCmdline: /usr/lib/tracker/tracker-extract ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xad14eb08 :mov (%eax),%eax PC (0xad14eb08) ok source "(%eax)" (0x007c) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: gst_video_info_to_caps () from /usr/lib/i386-linux-gnu/libgstvideo-1.0.so.0 ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstlibav.so ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56 ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56 avcodec_decode_video2 () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56 Title: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1504079/+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 991360] Re: isc-dhcp-client does not send hostnames in DHCPv6 by default
The opening line is somewhat misleading, even if in some sense it may be technically correct. > DHCPv6 does not have a host-name option to send the client hostname to register with the DHCP server. See option 39 OPTION_CLIENT_FQDN, and RFC 4704 "The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/991360 Title: isc-dhcp-client does not send hostnames in DHCPv6 by default Status in isc-dhcp package in Ubuntu: Fix Released Bug description: DHCPv6 does not have a host-name option to send the client hostname to register with the DHCP server. There are several potential options here: 1) Use the same "magic" to insert the hostname via fqdn.fqdn (i.e. "send fqdn.fqdn "";" This should work with DHCPv4 as well. 2) Backport the gethostname() functionality from DHCP 4.2. 3) Upgrade to isc-dhcp-client 4.2. Perhaps some of these are more appropriate to consider for the Q cycle. Personally, I think option 1 (implementing "" magic) for fqdn.fqdn would be the least intrusive. As issues go, this is admittedly minor. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: isc-dhcp-client 4.1.ESV-R4-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CheckboxSubmission: 014d169fc2d78562c156088c6ab6adc0 CheckboxSystem: c69722ecac764861be52925fa50b4dcc Date: Sun Apr 29 13:19:49 2012 DhclientLeases: ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: isc-dhcp UpgradeStatus: Upgraded to precise on 2012-04-15 (14 days ago) mtime.conffile..etc.dhcp.dhclient.conf: 2011-09-26T21:03:34.986111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/991360/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Kernel version 4.19.10 has the fix. To install run: ukuu --install v4.19.10 And reboot. -- 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/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I can confirm the following fixed the no-sound issue on my UX533 per buchovagabond's post above: sudo ukuu --install v4.19.10 Cheers, Craig -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Don't forget to 'sudo apt update' after making those changes. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Just uncomment the deb-src lines in /etc/apt/sources.list. For example, replace: # deb-src http://au.archive.ubuntu.com/ubuntu/ cosmic main restricted With: deb-src http://au.archive.ubuntu.com/ubuntu/ cosmic main restricted -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
For those following https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel, I had to do some extra things to get kernel compilation working. The workaround steps are described here: https://askubuntu.com/questions/1085411/unable-to-follow-kernel- buildyourownkernel/1099988. Substitute the kernel version relevant to you wherever you see "4.18.0"... -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
The above worked for (k)ubuntu 18.10. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Re above comment, the UX533 also has the ALC294. I should have made this clear in that comment. Thanks, Craig -- 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/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Hi Pawel, You may be right, but I think the common thread in all the laptops exhibiting this problem is the ALC294. Does the power save trick mentioned in my comment work for you at all? Cheers, Craig -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1742852 -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1742852] Re: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update
Seems related to https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1784485, as I'm seeing the same symptoms, with the same temporary improvement enabling the power save as described above. Asus UX533 Kubuntu 18.10 (4.18.0-11-generic) fresh install (dual boot with Windows 10). -- 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/1742852 Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a windows update I lost all the sound on my ubuntu machine. It's the second time that this happends. My sound is unmuted and at a loud level and nothing is comming out of my speakers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-26-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer CurrentDesktop: Unity Date: Thu Jan 11 22:21:23 2018 InstallationDate: Installed on 2017-11-29 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: gbergeron 2408 F...m pulseaudio /dev/snd/controlC0: gbergeron 2408 F pulseaudio gbergeron 3656 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Interestingly, if I put the sound device into power save mode and wait a few seconds before playing a sound, I can actually hear it perffectly clearly, but after repeating the playing of the sound a few times, it distorts then disappears: sudo -i echo 10 >/sys/module/snd_hda_intel/parameters/power_save sleep 10 aplay /usr/share/sounds/alsa/Front_Center.wav -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Same on Asus Zenbook UX533 with Realtek ALC294. No sound on Kubuntu 18.10 (4.18.0-11-generic) - speakers or headphones. Dual boot with Windows 10. Windows 10 sounds work fine. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1729357] Re: unprivileged user can drop supplementary groups
It's really not a problem, I'm happy to leave it as it is. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1729357 Title: unprivileged user can drop supplementary groups Status in shadow package in Ubuntu: Confirmed Bug description: Distribution: Ubuntu 16.04.3 LTS Kernel: 4.4.0-97-generic uidmap package version: 1:4.2-3.1ubuntu5.3 The newgidmap setuid executable allows any user to write a single mapping line to the gid_map of a process whose identity is the same as the calling process, as long as that mapping line maps the process's own GID outside of the user namespace to GID 0 inside the user namespace. Newgidmap will write the mapping regardless of the content of /proc/$process_being_mapped/setgroups, which will initially contain the string "allow". After this mapping is performed, and also after the process' uid_map is written with newuidmap, the process in the user namespace will be able to use the setgroups system call to drop supplementary groups. This is possible even if there is no entry for the user in /etc/subgid, because no subordinate GIDs are actually being used. This allows any user to circumvent the use of supplementary groups as blacklists, e.g. for some file owned by root:blacklist with permission bits 0604 (octal). Normally any process whose identity included the group "blacklist" in its supplementary groups would not be able to read that file. By performing this exploit using newgidmap, they can drop all supplementary groups and read that file. If newgidmap was not available, unprivileged users would not be able to write a process's gid_map until writing "deny" to /proc/$pid/setgroups. A fix for this might be for newgidmap to check the content of /proc/$process_being_mapped/setgroups is "deny", but we have not tried to patch this ourselves. An example using 2 login shells for a user named "someone" on Ubuntu Xenial, with the uidmap package installed: Shell 1 someone@ubuntu-xenial:~$ id uid=1001(someone) gid=1001(someone) groups=1001(someone),1002(restricted) someone@ubuntu-xenial:~$ ls -al /tmp/should_restrict -rwr-- 1 root restricted 8 Nov 1 12:23 /tmp/should_restrict someone@ubuntu-xenial:~$ cat /tmp/should_restrict cat: /tmp/should_restrict: Permission denied someone@ubuntu-xenial:~$ unshare -U --setgroups allow # /proc/self/setgroups already contains 'allow', but let's be explicit nobody@ubuntu-xenial:~$ echo $$ 1878 Shell 2 someone@ubuntu-xenial:~$ cat /etc/subuid lxd:10:65536 root:10:65536 ubuntu:165536:65536 someone@ubuntu-xenial:~$ cat /etc/subgid lxd:10:65536 root:10:65536 ubuntu:165536:65536 # There are no entries in /etc/sub{u,g}id for someone, but this doesn't matter that much as subordinate IDs are not being requested. someone@ubuntu-xenial:~$ newuidmap 1878 0 1001 1 someone@ubuntu-xenial:~$ newgidmap 1878 0 1001 1 Back to shell 1 nobody@ubuntu-xenial:~$ id uid=0(root) gid=0(root) groups=0(root),65534(nogroup) # The presence of the "nogroup" supplementary group indicates that some unmapped GIDs are present as supplementary GIDs. The kernel knows that this process still has "restricted" in its supplementary groups, so it can't read the restricted file yet. nobody@ubuntu-xenial:~$ cat /tmp/should_restrict cat: /tmp/should_restrict: Permission denied # The process has gained CAP_SETGID in its user namespace by becoming UID 0. /proc/$pid/setgroups contains "allow", so it can call setgroups(2). By su-ing to root (itself, in the user namespace), it can drop the supplementary groups. It can't read /root/.bashrc as that file is owned by UID 0 in the initial user namespace, which creates some distracting error output but doesn't matter in this case. nobody@ubuntu-xenial:~$ su root su: Authentication failure (Ignored) bash: /root/.bashrc: Permission denied # Supplementary groups have been dropped root@ubuntu-xenial:~# id uid=0(root) gid=0(root) groups=0(root) # It can read the restricted file root@ubuntu-xenial:~# cat /tmp/should_restrict content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1729357/+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 1729357] Re: unprivileged user can drop supplementary groups
Thanks for the credit! I did highlight that the bug was in newgidmap in my initial report, by the way. Aleksa, thanks for asking for a CVE? How did you go about this? This is new territory to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1729357 Title: unprivileged user can drop supplementary groups Status in shadow package in Ubuntu: Confirmed Bug description: Distribution: Ubuntu 16.04.3 LTS Kernel: 4.4.0-97-generic uidmap package version: 1:4.2-3.1ubuntu5.3 The newgidmap setuid executable allows any user to write a single mapping line to the gid_map of a process whose identity is the same as the calling process, as long as that mapping line maps the process's own GID outside of the user namespace to GID 0 inside the user namespace. Newgidmap will write the mapping regardless of the content of /proc/$process_being_mapped/setgroups, which will initially contain the string "allow". After this mapping is performed, and also after the process' uid_map is written with newuidmap, the process in the user namespace will be able to use the setgroups system call to drop supplementary groups. This is possible even if there is no entry for the user in /etc/subgid, because no subordinate GIDs are actually being used. This allows any user to circumvent the use of supplementary groups as blacklists, e.g. for some file owned by root:blacklist with permission bits 0604 (octal). Normally any process whose identity included the group "blacklist" in its supplementary groups would not be able to read that file. By performing this exploit using newgidmap, they can drop all supplementary groups and read that file. If newgidmap was not available, unprivileged users would not be able to write a process's gid_map until writing "deny" to /proc/$pid/setgroups. A fix for this might be for newgidmap to check the content of /proc/$process_being_mapped/setgroups is "deny", but we have not tried to patch this ourselves. An example using 2 login shells for a user named "someone" on Ubuntu Xenial, with the uidmap package installed: Shell 1 someone@ubuntu-xenial:~$ id uid=1001(someone) gid=1001(someone) groups=1001(someone),1002(restricted) someone@ubuntu-xenial:~$ ls -al /tmp/should_restrict -rwr-- 1 root restricted 8 Nov 1 12:23 /tmp/should_restrict someone@ubuntu-xenial:~$ cat /tmp/should_restrict cat: /tmp/should_restrict: Permission denied someone@ubuntu-xenial:~$ unshare -U --setgroups allow # /proc/self/setgroups already contains 'allow', but let's be explicit nobody@ubuntu-xenial:~$ echo $$ 1878 Shell 2 someone@ubuntu-xenial:~$ cat /etc/subuid lxd:10:65536 root:10:65536 ubuntu:165536:65536 someone@ubuntu-xenial:~$ cat /etc/subgid lxd:10:65536 root:10:65536 ubuntu:165536:65536 # There are no entries in /etc/sub{u,g}id for someone, but this doesn't matter that much as subordinate IDs are not being requested. someone@ubuntu-xenial:~$ newuidmap 1878 0 1001 1 someone@ubuntu-xenial:~$ newgidmap 1878 0 1001 1 Back to shell 1 nobody@ubuntu-xenial:~$ id uid=0(root) gid=0(root) groups=0(root),65534(nogroup) # The presence of the "nogroup" supplementary group indicates that some unmapped GIDs are present as supplementary GIDs. The kernel knows that this process still has "restricted" in its supplementary groups, so it can't read the restricted file yet. nobody@ubuntu-xenial:~$ cat /tmp/should_restrict cat: /tmp/should_restrict: Permission denied # The process has gained CAP_SETGID in its user namespace by becoming UID 0. /proc/$pid/setgroups contains "allow", so it can call setgroups(2). By su-ing to root (itself, in the user namespace), it can drop the supplementary groups. It can't read /root/.bashrc as that file is owned by UID 0 in the initial user namespace, which creates some distracting error output but doesn't matter in this case. nobody@ubuntu-xenial:~$ su root su: Authentication failure (Ignored) bash: /root/.bashrc: Permission denied # Supplementary groups have been dropped root@ubuntu-xenial:~# id uid=0(root) gid=0(root) groups=0(root) # It can read the restricted file root@ubuntu-xenial:~# cat /tmp/should_restrict content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1729357/+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 1724233] Re: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
looking through the original documentation above could this be due to the accountable2you program? I guess what i could do is turn off all my extensions and attempt to find which one is bringing up the error? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1724233 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() Status in python2.7 package in Ubuntu: Incomplete Bug description: Booted into stock Ubuntu 17.10 release candidate from October 15, 2017 and this error message simply came up. apt-cache policy python python: Installed: 2.7.14-2ubuntu1 Candidate: 2.7.14-2ubuntu1 Version table: *** 2.7.14-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: python2.7-minimal 2.7.14-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 06:15:41 2017 ExecutablePath: /usr/bin/python2.7 InstallationDate: Installed on 2017-10-17 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) ProcCmdline: python accountable2you.pyc --username ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f84d920daa9 : movzwl 0xa(%rdi),%r15d PC (0x7f84d920daa9) ok source "0xa(%rdi)" (0x64007d) not located in a known VMA region (needed readable region)! destination "%r15d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: python2.7 StacktraceTop: ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1724233/+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
Re: [Touch-packages] [Bug 1724233] Re: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
It is on the GNOME software/extension center so I assume that is a yes On Nov 27, 2017 11:50 PM, "Matthias Klose" wrote: > is this a packaged extension? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1724233 > > Title: > python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() > > Status in python2.7 package in Ubuntu: > Incomplete > > Bug description: > Booted into stock Ubuntu 17.10 release candidate from October 15, 2017 > and this error message simply came up. > > apt-cache policy python > python: > Installed: 2.7.14-2ubuntu1 > Candidate: 2.7.14-2ubuntu1 > Version table: >*** 2.7.14-2ubuntu1 500 > 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 > Packages > 100 /var/lib/dpkg/status > > ProblemType: Crash > DistroRelease: Ubuntu 17.10 > Package: python2.7-minimal 2.7.14-2ubuntu2 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Uname: Linux 4.13.0-16-generic x86_64 > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Tue Oct 17 06:15:41 2017 > ExecutablePath: /usr/bin/python2.7 > InstallationDate: Installed on 2017-10-17 (0 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) > ProcCmdline: python accountable2you.pyc --username > ProcEnviron: >LANGUAGE=en_CA:en >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_CA.UTF-8 >SHELL=/bin/bash > Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, > 3.6.3-0ubuntu2 > PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, > 2.7.14-2ubuntu1 > SegvAnalysis: >Segfault happened at: 0x7f84d920daa9 : > movzwl 0xa(%rdi),%r15d >PC (0x7f84d920daa9) ok >source "0xa(%rdi)" (0x64007d) not located in a known VMA region > (needed readable region)! >destination "%r15d" ok >Stack memory exhausted (SP below stack segment) > SegvReason: reading unknown VMA > Signal: 11 > SourcePackage: python2.7 > StacktraceTop: >ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6 >ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 >IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6 >ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 >ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 > Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/ > 1724233/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1724233 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() Status in python2.7 package in Ubuntu: Incomplete Bug description: Booted into stock Ubuntu 17.10 release candidate from October 15, 2017 and this error message simply came up. apt-cache policy python python: Installed: 2.7.14-2ubuntu1 Candidate: 2.7.14-2ubuntu1 Version table: *** 2.7.14-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: python2.7-minimal 2.7.14-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 06:15:41 2017 ExecutablePath: /usr/bin/python2.7 InstallationDate: Installed on 2017-10-17 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) ProcCmdline: python accountable2you.pyc --username ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f84d920daa9 : movzwl 0xa(%rdi),%r15d PC (0x7f84d920daa9) ok source "0xa(%rdi)" (0x64007d) not located in a known VMA region (needed readable region)! destination "%r15d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: python2.7 StacktraceTop: ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.
[Touch-packages] [Bug 1724233] Re: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
it possible that this happened after installing the Sensors extension in Gnome, the extension does not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1724233 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() Status in python2.7 package in Ubuntu: Incomplete Bug description: Booted into stock Ubuntu 17.10 release candidate from October 15, 2017 and this error message simply came up. apt-cache policy python python: Installed: 2.7.14-2ubuntu1 Candidate: 2.7.14-2ubuntu1 Version table: *** 2.7.14-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: python2.7-minimal 2.7.14-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 06:15:41 2017 ExecutablePath: /usr/bin/python2.7 InstallationDate: Installed on 2017-10-17 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) ProcCmdline: python accountable2you.pyc --username ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f84d920daa9 : movzwl 0xa(%rdi),%r15d PC (0x7f84d920daa9) ok source "0xa(%rdi)" (0x64007d) not located in a known VMA region (needed readable region)! destination "%r15d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: python2.7 StacktraceTop: ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1724233/+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 1729357] Re: unprivileged user can drop supplementary groups
Thanks for replying Eric, but I'm having trouble reproducing what you've posted. I can't write the gid map until I've written deny to /prod/$pid/setgroups, not the other way around. There might be some nuance I've missed. Also, newgidmap will allow a user to map their own GID to 0 in the user namespace, even when there is no entry for that user in /etc/subgid. What if newgidmap wrote "deny" to /proc/$pid/setgroups unless the user is whitelisted in some config file, probably separate from /etc/subgid, as Stéphane suggested? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1729357 Title: unprivileged user can drop supplementary groups Status in shadow package in Ubuntu: Confirmed Bug description: Distribution: Ubuntu 16.04.3 LTS Kernel: 4.4.0-97-generic uidmap package version: 1:4.2-3.1ubuntu5.3 The newgidmap setuid executable allows any user to write a single mapping line to the gid_map of a process whose identity is the same as the calling process, as long as that mapping line maps the process's own GID outside of the user namespace to GID 0 inside the user namespace. Newgidmap will write the mapping regardless of the content of /proc/$process_being_mapped/setgroups, which will initially contain the string "allow". After this mapping is performed, and also after the process' uid_map is written with newuidmap, the process in the user namespace will be able to use the setgroups system call to drop supplementary groups. This is possible even if there is no entry for the user in /etc/subgid, because no subordinate GIDs are actually being used. This allows any user to circumvent the use of supplementary groups as blacklists, e.g. for some file owned by root:blacklist with permission bits 0604 (octal). Normally any process whose identity included the group "blacklist" in its supplementary groups would not be able to read that file. By performing this exploit using newgidmap, they can drop all supplementary groups and read that file. If newgidmap was not available, unprivileged users would not be able to write a process's gid_map until writing "deny" to /proc/$pid/setgroups. A fix for this might be for newgidmap to check the content of /proc/$process_being_mapped/setgroups is "deny", but we have not tried to patch this ourselves. An example using 2 login shells for a user named "someone" on Ubuntu Xenial, with the uidmap package installed: Shell 1 someone@ubuntu-xenial:~$ id uid=1001(someone) gid=1001(someone) groups=1001(someone),1002(restricted) someone@ubuntu-xenial:~$ ls -al /tmp/should_restrict -rwr-- 1 root restricted 8 Nov 1 12:23 /tmp/should_restrict someone@ubuntu-xenial:~$ cat /tmp/should_restrict cat: /tmp/should_restrict: Permission denied someone@ubuntu-xenial:~$ unshare -U --setgroups allow # /proc/self/setgroups already contains 'allow', but let's be explicit nobody@ubuntu-xenial:~$ echo $$ 1878 Shell 2 someone@ubuntu-xenial:~$ cat /etc/subuid lxd:10:65536 root:10:65536 ubuntu:165536:65536 someone@ubuntu-xenial:~$ cat /etc/subgid lxd:10:65536 root:10:65536 ubuntu:165536:65536 # There are no entries in /etc/sub{u,g}id for someone, but this doesn't matter that much as subordinate IDs are not being requested. someone@ubuntu-xenial:~$ newuidmap 1878 0 1001 1 someone@ubuntu-xenial:~$ newgidmap 1878 0 1001 1 Back to shell 1 nobody@ubuntu-xenial:~$ id uid=0(root) gid=0(root) groups=0(root),65534(nogroup) # The presence of the "nogroup" supplementary group indicates that some unmapped GIDs are present as supplementary GIDs. The kernel knows that this process still has "restricted" in its supplementary groups, so it can't read the restricted file yet. nobody@ubuntu-xenial:~$ cat /tmp/should_restrict cat: /tmp/should_restrict: Permission denied # The process has gained CAP_SETGID in its user namespace by becoming UID 0. /proc/$pid/setgroups contains "allow", so it can call setgroups(2). By su-ing to root (itself, in the user namespace), it can drop the supplementary groups. It can't read /root/.bashrc as that file is owned by UID 0 in the initial user namespace, which creates some distracting error output but doesn't matter in this case. nobody@ubuntu-xenial:~$ su root su: Authentication failure (Ignored) bash: /root/.bashrc: Permission denied # Supplementary groups have been dropped root@ubuntu-xenial:~# id uid=0(root) gid=0(root) groups=0(root) # It can read the restricted file root@ubuntu-xenial:~# cat /tmp/should_restrict content To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1729357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https
[Touch-packages] [Bug 1731094] [NEW] Trouble Switching between GPUs on a Carrizo laptop with an integrated and discrete graphics card.
Public bug reported: Yesterday I decided to learn how to switch between my low power usage GPU and my discrete GPU in my laptop using Prime. I started by running this command: xrandr --listproviders. I got the following result: Providers: number : 2 Provider 0: id: 0x75 cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 3 associated providers: 1 name:AMD Radeon R6 Graphics @ pci::00:01.0 Provider 1: id: 0x3f cap: 0x4, Source Offload crtcs: 0 outputs: 0 associated providers: 1 name:AMD Radeon (TM) R7 M360 @ pci::03:00.0 I then ran this command to switch to my discrete GPU: xrandr --setprovideroffloadsink 1 0. This resulted in the following result to my GPU with this command: DRI_PRIME=1 glxinfo | grep "OpenGL renderer" OpenGL renderer string: AMD Radeon (TM) R7 M360 (AMD ICELAND / DRM 3.18.0 / 4.13.8-041308-generic, LLVM 5.0.0) Now however when i attempt to switch back to using my low powered Radeon R6 with this command I get: xrandr --setprovideroffloadsink 0 1 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 34 (RRSetProviderOffloadSink) Value in failed request: 0x75 Serial number of failed request: 16 Current serial number in output stream: 17 I should mention I am logging into the Gnome session using Xorg on Ubuntu 17.10. I would love to be able to switch back to my R6 so any help is much appreciated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.13.8-041308-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME Date: Wed Nov 8 19:53:41 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.13.8-041308-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Carrizo [1025:095e] InstallationDate: Installed on 2017-10-20 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.8-041308-generic root=UUID=17c9ce89-7e9f-4910-965e-cbd862c45839 ro modprobe.blacklist=radeon radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Nami_CZ dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd09/15/2015:svnAcer:pn:pvrV1.10:rvnAcer:rnNami_CZ:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: CZ dmi.product.version: V1.10 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu xrandr -- 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/1731094 Title: Trouble Switching between GPUs on a Carrizo laptop with an integrated and discrete graphics card. Status in xorg package in Ubuntu: New Bug description: Yesterday I decided to learn how to switch between my low power usage GPU and my discrete GPU in my laptop using Prime. I started by running this command: xrandr --listproviders. I got the following result: Providers: number : 2 Provider 0: id: 0x75 cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 3 associated providers: 1 name:AMD Radeon R6 Graphics @ pci::00:01.0 Provider 1: id: 0x3f cap: 0x4, Source Offload crtcs: 0 outputs: 0 associated providers: 1 name:AMD Radeon (TM) R7 M360 @ pci::03:00.0 I then ran this command to switch to my discrete GPU: xrandr --setprovideroffloadsink 1 0. This resulted in the following result to my GPU with this command: DRI_PRIME=1 glxinfo | grep "OpenGL renderer" OpenGL renderer string: AMD Radeon (TM) R7 M360 (AMD ICELAND / DRM 3.18.0 / 4.13.8-041308-generic, LLVM 5.0.0) Now however when i attempt t
[Touch-packages] [Bug 1724233] Re: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
i wiped my system and loaded production ubuntu 17.10 and the same error still exists there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1724233 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() Status in python2.7 package in Ubuntu: New Bug description: Booted into stock Ubuntu 17.10 release candidate from October 15, 2017 and this error message simply came up. apt-cache policy python python: Installed: 2.7.14-2ubuntu1 Candidate: 2.7.14-2ubuntu1 Version table: *** 2.7.14-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: python2.7-minimal 2.7.14-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 06:15:41 2017 ExecutablePath: /usr/bin/python2.7 InstallationDate: Installed on 2017-10-17 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) ProcCmdline: python accountable2you.pyc --username ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f84d920daa9 : movzwl 0xa(%rdi),%r15d PC (0x7f84d920daa9) ok source "0xa(%rdi)" (0x64007d) not located in a known VMA region (needed readable region)! destination "%r15d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: python2.7 StacktraceTop: ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1724233/+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 1584575] Re: /lib/systemd/system/lightdm.service file has no [Install] clause
I too needed to re-enable graphical login after having disabled it. I can confirm adding: [Install] Alias=display-manager.service to my /lib/systemd/system/lightdm.service file. Allowed me to re-enable lightdm to start on boot (by running "sudo systemctl enable lightdm"), previous to this I would end up booting to a black screen with a flashing cursor in the top left. Ctrl+Alt+F1 (for VT1) etc... would lead me to the login prompts, Ctrl+Alt+F7 leads me back to the screen with the flashing cursor (VT7). So for me Ubuntu was expecting a graphical interface to be running and had me on VT7 at boot. Logging in from one of the other terminals showed lightdm to be stopped ("systemctl status lightdm"). Prior to the fix above I would have to manually start lightdm by logging in and running "sudo systemctl start lightdm" I hope the above helps anyone googling the issue as it took me a couple of hours to track down why it wasn't starting when I thought it was re- enabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1584575 Title: /lib/systemd/system/lightdm.service file has no [Install] clause Status in lightdm package in Ubuntu: Confirmed Bug description: This concerns lightdm 1.18.1-0ubuntu1 in Xenial. The /lib/systemd/system/lightdm.service file lacks an [Install] clause. Meaning, that if you do # systemctl disable display-manager to prevent LightDM from starting, running # systemctl enable lightdm does not restore the /etc/systemd/system/display-manager.service symlink, and thus does not re-enable LightDM to run at the next boot as intended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1584575/+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 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
I have the same issue: Dell XPS 15 9560 Ubuntu 17.04 4.10.0-20-generic -- 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/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+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 717518] Re: show-all-if-ambiguous and show-all-if-unmodified in ~/.input breaks characters a and u
I see old bug, but I'm seeing this with `show-all-if-unmodified` on ubuntu 14.04.5 (libreadline6=6.3-4ubuntu2). `show-all-if-ambiguous` works fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/717518 Title: show-all-if-ambiguous and show-all-if-unmodified in ~/.input breaks characters a and u Status in bash package in Ubuntu: New Bug description: Binary package hint: bash If I set 'show-all-if-ambiguous' to either 'on' or 'off' in my ~/.inputrc , I can't type 'a' on the bash command line anymore. And if try to paste a string with 'a':s in it, the string appear without the 'a':s. Other characters are not affected (not even 'A'). In a similar manner, setting 'show-all-if-unmodified' to either 'on' or 'off', makes it impossible to type 'u'. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: bash 4.1-2ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic x86_64 Architecture: amd64 Date: Sat Feb 12 03:41:11 2011 InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101008.1) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/717518/+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 1650825] [NEW] package linux-image-extra-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
Public bug reported: clean new load on vmware 10, error message on first reboot. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: craig 1034 F lxpanel Date: Sat Dec 17 16:30:27 2016 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=8ea0593d-b792-40e2-9b36-afd9595d82c5 InstallationDate: Installed on 2016-12-17 (0 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: ens33 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-53-generic root=/dev/mapper/lubuntu--vg-root ro quiet splash RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 RfKill: SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- 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/1650825 Title: package linux-image-extra-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in initramfs-tools package in Ubuntu: New Bug description: clean new load on vmware 10, error message on first reboot. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: craig 1034 F lxpanel Date: Sat Dec 17 16:30:27 2016 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=8ea0593d-b792-40e2-9b36-afd9595d82c5 InstallationDate: Installed on 2016-12-17 (0 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: ens33 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-53-generic root=/dev/mapper/lubuntu--vg-root ro quiet splash RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 RfKill: SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNo
[Touch-packages] [Bug 1594814] Re: NetworkManager looking for signal strength in 'wlan0' instead of the apropriate 'wlxc46e1f1abe34"
It seems like a fix was released for NetworkManager a few months ago, when can we expect it to be released into the Ubuntu repositories? -- 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/1594814 Title: NetworkManager looking for signal strength in 'wlan0' instead of the apropriate 'wlxc46e1f1abe34" Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Confirmed Bug description: I get this error in my log a lot: "Jun 21 15:04:00 basspistol NetworkManager[834]: [1466514240.9769] (wlan0): error getting signal strength: No such device" My wireless device (TP-Link 150Mbps Wireless N Nano USB Adapter) is getting a very funky name: "wlxc46e1f1abe34". It's not too much of a problem since the connection is established and working, but it renders the wifi-strength icon as if it was receiving maximum signal strength. Restarting the network-manager with: "sudo systemctl restart network- manager.service" solves the problem. Not sure if it is related, but i am also affected by this bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1589401 Even after upgrading to: network-manager-gnome:amd64 (1.2.0-0ubuntu0.16.04.1, 1.2.0-0ubuntu0.16.04.3) on 2016-06-19 Let me know if there is any complementary information i can provide. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-24.43-lowlatency 4.4.10 Uname: Linux 4.4.0-24-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 21 15:04:46 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-21 (60 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 10.42.0.1 dev wlxc46e1f1abe34 proto static metric 600 10.42.0.0/24 dev wlxc46e1f1abe34 proto kernel scope link src 10.42.0.22 metric 600 169.254.0.0/16 dev wlxc46e1f1abe34 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlxc46e1f1abe34 wifi connected /org/freedesktop/NetworkManager/Devices/0 sakrecoer 1 7bfae379-b282-4335-8bfe-f1f55229ad51 /org/freedesktop/NetworkManager/ActiveConnection/0 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1594814/+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
Re: [Touch-packages] [Bug 1639477] Re: package url-dispatcher 0.1+16.04.20151110-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Worked, thanks! Sent from my phone Craig Wells On Nov 12, 2016 2:45 PM, "Stoyan Penchev" wrote: > Resolved by running: > sudo pip3 uninstall click > sudo apt-get upgrade > > And optionally but recommended "sudo apt autoremove" for cleanup after > upgrade > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1639477 > > Title: > package url-dispatcher 0.1+16.04.20151110-0ubuntu2 failed to > install/upgrade: subprocess new pre-removal script returned error exit > status 1 > > Status in url-dispatcher package in Ubuntu: > Confirmed > > Bug description: > During upgrade to 16.10 > > ProblemType: Package > DistroRelease: Ubuntu 16.10 > Package: url-dispatcher 0.1+16.04.20151110-0ubuntu2 > ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 > Uname: Linux 4.4.0-46-generic x86_64 > NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.3-0ubuntu8 > Architecture: amd64 > Date: Sat Nov 5 10:02:10 2016 > ErrorMessage: subprocess new pre-removal script returned error exit > status 1 > InstallationDate: Installed on 2016-05-04 (184 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > RelatedPackageVersions: >dpkg 1.18.10ubuntu1 >apt 1.3.1 > SourcePackage: url-dispatcher > Title: package url-dispatcher 0.1+16.04.20151110-0ubuntu2 failed to > install/upgrade: subprocess new pre-removal script returned error exit > status 1 > UpgradeStatus: Upgraded to yakkety on 2016-11-05 (0 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/ > +bug/1639477/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1639477 Title: package url-dispatcher 0.1+16.04.20151110-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in url-dispatcher package in Ubuntu: Confirmed Bug description: During upgrade to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: url-dispatcher 0.1+16.04.20151110-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sat Nov 5 10:02:10 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-04 (184 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: url-dispatcher Title: package url-dispatcher 0.1+16.04.20151110-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-11-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1639477/+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 1639489] [NEW] package click-apparmor 0.3.13.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: Happened after upgrade from 16.04 to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click-apparmor 0.3.13.1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sat Nov 5 10:44:18 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-04 (184 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click-apparmor Title: package click-apparmor 0.3.13.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-11-05 (0 days ago) ** Affects: click-apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1639489 Title: package click-apparmor 0.3.13.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in click-apparmor package in Ubuntu: New Bug description: Happened after upgrade from 16.04 to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click-apparmor 0.3.13.1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sat Nov 5 10:44:18 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-04 (184 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click-apparmor Title: package click-apparmor 0.3.13.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-11-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1639489/+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 1639477] [NEW] package url-dispatcher 0.1+16.04.20151110-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: During upgrade to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: url-dispatcher 0.1+16.04.20151110-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sat Nov 5 10:02:10 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-04 (184 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: url-dispatcher Title: package url-dispatcher 0.1+16.04.20151110-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-11-05 (0 days ago) ** Affects: url-dispatcher (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1639477 Title: package url-dispatcher 0.1+16.04.20151110-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in url-dispatcher package in Ubuntu: New Bug description: During upgrade to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: url-dispatcher 0.1+16.04.20151110-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sat Nov 5 10:02:10 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-04 (184 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: url-dispatcher Title: package url-dispatcher 0.1+16.04.20151110-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-11-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1639477/+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 1619307] Re: Switching to USB sound device stops USB mouse clicks from registering Edit
I have a JABRA Evolve 40 - MS Skype Edition attached to my Ubuntu 16.04.01 LTS and had experienced the same issues as kringalf. kringalf's solution solved this for me as well. Distribution: Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial Kernel: 4.4.0-36-generic usb-devices: T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0b0e ProdID=0305 Rev=02.02 S: Manufacturer=GN Netcom A/S S: Product=Jabra EVOLVE LINK MS S: SerialNumber=898EF4E007 C: #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio I: If#= 1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio I: If#= 2 Alt= 0 #EPs= 0 Cls=01(audio) Sub=02 Prot=00 Driver=snd-usb-audio I: If#= 3 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid -- 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/1619307 Title: Switching to USB sound device stops USB mouse clicks from registering Edit Status in xorg package in Ubuntu: Triaged Bug description: I have a JABRA Evolve 80 headset with the 3.5mm plugged into the JABRA Evolve 80 Link UC. Once I plug the JABRA Evolve Link UC USB into my computer, the mouse pointer is somehow "captured" by the last active window. I can switch windows via alt-tab but left clicks in the new window still won't work, they will only work in the "old" window. WORKAROUND: Add 50-jabra.conf file in /usr/share/X11/xorg.conf.d with the following: Section "InputClass" Identifier "Jabra" MatchProduct "GN Netcom A/S Jabra EVOLVE LINK MS" Option "ButtonMapping" "0 0 0 0 0 0 0 0 0 0 0 0" EndSection and restart xorg-server. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Sep 1 14:47:55 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0535] MachineType: Dell Inc. Latitude E6530 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed root=/dev/mapper/system-root_crypt ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0JC5MT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd08/19/2015:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn0JC5MT:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Sep 1 11:27:32 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 812 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619307/+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 1336663] Re: lightdm uses wrong ccache name on pam_krb5 credentials refresh
FWIW, this issue is also present using gdm3 in Ubuntu 16.04. With pam_krb5's debug option set, I see the following during initial login (with successful credential cache construction): gdm-password]: pam_krb5(gdm-password:auth): pam_sm_authenticate: entry gdm-password]: pam_krb5(gdm-password:auth): (user cgallek) attempting authentication as cgal...@.com gdm-password]: pam_krb5(gdm-password:auth): user cgallek authenticated as cgal...@.com gdm-password]: pam_krb5(gdm-password:auth): (user cgallek) temporarily storing credentials in /tmp/krb5cc_pam_LB8CeL gdm-password]: pam_krb5(gdm-password:auth): pam_sm_authenticate: exit (success) gdm-password]: pam_krb5(gdm-password:setcred): pam_sm_setcred: entry (establish) gdm-password]: pam_krb5(gdm-password:setcred): (user cgallek) initializing ticket cache FILE:/tmp/krb5cc_1000_3BiTY0 gdm-password]: pam_krb5(gdm-password:setcred): pam_sm_setcred: exit (success) When unlocking the screen, I see the following successful credential refresh, but to the wrong cache filename (/tmp/krb5cc_0): gdm-password]: pam_krb5(gdm-password:auth): pam_sm_authenticate: entry gdm-password]: pam_krb5(gdm-password:auth): (user cgallek) attempting authentication as cgal...@angrydoughnuts.com gdm-password]: pam_krb5(gdm-password:auth): user cgallek authenticated as cgal...@.com gdm-password]: pam_krb5(gdm-password:auth): (user cgallek) temporarily storing credentials in /tmp/krb5cc_pam_Dkg5Ip gdm-password]: pam_krb5(gdm-password:auth): pam_sm_authenticate: exit (success) gdm-password]: pam_krb5(gdm-password:setcred): pam_sm_setcred: entry (reinit) gdm-password]: pam_krb5(gdm-password:setcred): (user cgallek) refreshing ticket cache /tmp/krb5cc_0 gdm-password]: pam_krb5(gdm-password:setcred): pam_sm_setcred: exit (success) The _0 cache that is created has the correct new credential in it, but is obviously not known by any other process as it does not match the earlier version of $KRB5CCNAME. I imagine this is the same issue described above where the $KRB5CCNAME environment variable is not available in the gdm context which unlocks the screen. It's worth noting that in the GDM case, there appears to be a per- session helper process (gdm-session-worker) used to communicate with the GDM service. This process _does not_ have the $KRB5CCNAME variable set in its environment. Would storing the value in this processes environment fix the problem? ~: ps -ef | grep gdm-session-worker root 11364 11203 0 Jun25 ?00:00:00 gdm-session-worker [pam/gdm-password] ~: cat /proc/11364/environ LANG=en_US.UTF-8PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binGDM_SESSION_DBUS_ADDRESS=unix:abstract=/tmp/dbus-oTnmcExV ** Also affects: gdm Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1336663 Title: lightdm uses wrong ccache name on pam_krb5 credentials refresh Status in gdm: New Status in Light Display Manager: Triaged Status in libpam-krb5 package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: As already noted by Brian Knoll in https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1296276/comments/24 lightdm 1.10.1-0ubuntu1 uses an inappropriate credentials cache, /tmp/krb5cc_0, when refreshing Kerberos credentials on screen unlock. I couldn't find the new bug Robert Ancell called for in https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1296276/comments/27 so I'm opening one now. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1336663/+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 1590547] Re: LXC package for trusty no longer has configuration files
Thank you, that did the trick. Not sure how it got into that state though. Some guidance on what I did wrong would helpful. :) Thanks again! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1590547 Title: LXC package for trusty no longer has configuration files Status in lxc package in Ubuntu: New Bug description: Did an upgrade this morning to the latest LXC package (via the updates channel). LXC Package 2.0.1-0ubuntu1~ubuntu14.04.1 no longer has the configuration files under /usr/share/lxc/config. This causes lxc-ls to complain about missing template files. lxc-ls: parse.c: lxc_file_for_each_line: 57 Failed to parse config: lxc.include = /usr/share/lxc/config/ubuntu.common.conf Do I need to change the container's configuration to point to a new location? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1590547/+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 1590547] Re: LXC package for trusty no longer has configuration files
root@lister:~# apt-get remove lxc-templates Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: lxc-templates 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 391 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 310044 files and directories currently installed.) Removing lxc-templates (1.0.8-0ubuntu0.3) ... root@lister:~# apt-get install lxc-templates Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: qemu-user-static The following NEW packages will be installed: lxc-templates 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 63.0 kB of archives. After this operation, 391 kB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main lxc-templates amd64 1.0.8-0ubuntu0.3 [63.0 kB] Fetched 63.0 kB in 0s (327 kB/s) Selecting previously unselected package lxc-templates. (Reading database ... 310024 files and directories currently installed.) Preparing to unpack .../lxc-templates_1.0.8-0ubuntu0.3_amd64.deb ... Unpacking lxc-templates (1.0.8-0ubuntu0.3) ... Setting up lxc-templates (1.0.8-0ubuntu0.3) ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1590547 Title: LXC package for trusty no longer has configuration files Status in lxc package in Ubuntu: New Bug description: Did an upgrade this morning to the latest LXC package (via the updates channel). LXC Package 2.0.1-0ubuntu1~ubuntu14.04.1 no longer has the configuration files under /usr/share/lxc/config. This causes lxc-ls to complain about missing template files. lxc-ls: parse.c: lxc_file_for_each_line: 57 Failed to parse config: lxc.include = /usr/share/lxc/config/ubuntu.common.conf Do I need to change the container's configuration to point to a new location? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1590547/+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 1590547] Re: LXC package for trusty no longer has configuration files
root@lister:~# apt-cache madison lxc-templates lxc-templates | 2.0.1-0ubuntu1~ubuntu14.04.1 | http://us.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 Packages lxc-templates | 1.0.8-0ubuntu0.3 | http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages lxc-templates | 1.0.7-0ubuntu0.7 | http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages lxc-templates | 1.0.3-0ubuntu3 | http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages lxc | 1.0.3-0ubuntu3 | http://us.archive.ubuntu.com/ubuntu/ trusty/main Sources lxc | 1.0.8-0ubuntu0.3 | http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main Sources lxc | 2.0.1-0ubuntu1~ubuntu14.04.1 | http://us.archive.ubuntu.com/ubuntu/ trusty-backports/main Sources lxc | 1.0.7-0ubuntu0.7 | http://security.ubuntu.com/ubuntu/ trusty-security/main Sources root@lister:~# apt-get install lxc-templates Reading package lists... Done Building dependency tree Reading state information... Done lxc-templates is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@lister:~# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1590547 Title: LXC package for trusty no longer has configuration files Status in lxc package in Ubuntu: New Bug description: Did an upgrade this morning to the latest LXC package (via the updates channel). LXC Package 2.0.1-0ubuntu1~ubuntu14.04.1 no longer has the configuration files under /usr/share/lxc/config. This causes lxc-ls to complain about missing template files. lxc-ls: parse.c: lxc_file_for_each_line: 57 Failed to parse config: lxc.include = /usr/share/lxc/config/ubuntu.common.conf Do I need to change the container's configuration to point to a new location? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1590547/+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 1590547] Re: LXC package for trusty no longer has configuration files
craig@lister:~$ dpkg -l | grep lxc ii libclxclient3:amd64 3.9.0-1 amd64X Window System C++ access library ii liblxc1 2.0.1-0ubuntu1~ubuntu14.04.1amd64Linux Containers userspace tools (library) ii lxc 2.0.1-0ubuntu1~ubuntu14.04.1all Transitional package for lxc1 ii lxc-common 2.0.1-0ubuntu1~ubuntu14.04.1amd64Linux Containers userspace tools (common tools) ii lxc-templates 1.0.8-0ubuntu0.3 amd64Linux Containers userspace tools (templates) ii lxc1 2.0.1-0ubuntu1~ubuntu14.04.1amd64Linux Containers userspace tools ii lxcfs 2.0.1-0ubuntu1~ubuntu14.04.1amd64FUSE based filesystem for LXC ii python3-lxc 2.0.1-0ubuntu1~ubuntu14.04.1amd64Linux Containers userspace tools (Python 3.x bindings) So it's an old package, but I'm not offered the latest package when I try apt-get update && apt-get dist-upgrade. What's the best way to fix this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1590547 Title: LXC package for trusty no longer has configuration files Status in lxc package in Ubuntu: New Bug description: Did an upgrade this morning to the latest LXC package (via the updates channel). LXC Package 2.0.1-0ubuntu1~ubuntu14.04.1 no longer has the configuration files under /usr/share/lxc/config. This causes lxc-ls to complain about missing template files. lxc-ls: parse.c: lxc_file_for_each_line: 57 Failed to parse config: lxc.include = /usr/share/lxc/config/ubuntu.common.conf Do I need to change the container's configuration to point to a new location? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1590547/+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 1590547] Re: LXC package for trusty no longer has configuration files
I do, but the templates don't seem to have the .conf files: craig@lister:~$ dpkg -L lxc-templates /. /usr /usr/share /usr/share/lxc /usr/share/lxc/lxc-patch.py /usr/share/lxc/templates /usr/share/lxc/templates/lxc-gentoo /usr/share/lxc/templates/lxc-centos /usr/share/lxc/templates/lxc-oracle /usr/share/lxc/templates/lxc-alpine /usr/share/lxc/templates/lxc-fedora /usr/share/lxc/templates/lxc-sshd /usr/share/lxc/templates/lxc-altlinux /usr/share/lxc/templates/lxc-opensuse /usr/share/lxc/templates/lxc-download /usr/share/lxc/templates/lxc-busybox /usr/share/lxc/templates/lxc-ubuntu /usr/share/lxc/templates/lxc-ubuntu-cloud /usr/share/lxc/templates/lxc-openmandriva /usr/share/lxc/templates/lxc-cirros /usr/share/lxc/templates/lxc-plamo /usr/share/lxc/templates/lxc-archlinux /usr/share/lxc/templates/lxc-debian /usr/share/doc /usr/share/doc/lxc-templates /usr/share/doc/lxc-templates/copyright /usr/share/doc/lxc-templates/changelog.Debian.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1590547 Title: LXC package for trusty no longer has configuration files Status in lxc package in Ubuntu: New Bug description: Did an upgrade this morning to the latest LXC package (via the updates channel). LXC Package 2.0.1-0ubuntu1~ubuntu14.04.1 no longer has the configuration files under /usr/share/lxc/config. This causes lxc-ls to complain about missing template files. lxc-ls: parse.c: lxc_file_for_each_line: 57 Failed to parse config: lxc.include = /usr/share/lxc/config/ubuntu.common.conf Do I need to change the container's configuration to point to a new location? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1590547/+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 1590547] Re: LXC package for trusty no longer has configuration files
Copied over the config from lxc-2.0.1/config/templates to /usr/share/lxc/config and it appears to be working. So the files seem to be missing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1590547 Title: LXC package for trusty no longer has configuration files Status in lxc package in Ubuntu: New Bug description: Did an upgrade this morning to the latest LXC package (via the updates channel). LXC Package 2.0.1-0ubuntu1~ubuntu14.04.1 no longer has the configuration files under /usr/share/lxc/config. This causes lxc-ls to complain about missing template files. lxc-ls: parse.c: lxc_file_for_each_line: 57 Failed to parse config: lxc.include = /usr/share/lxc/config/ubuntu.common.conf Do I need to change the container's configuration to point to a new location? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1590547/+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 1590547] [NEW] LXC package for trusty no longer has configuration files
Public bug reported: Did an upgrade this morning to the latest LXC package (via the updates channel). LXC Package 2.0.1-0ubuntu1~ubuntu14.04.1 no longer has the configuration files under /usr/share/lxc/config. This causes lxc-ls to complain about missing template files. lxc-ls: parse.c: lxc_file_for_each_line: 57 Failed to parse config: lxc.include = /usr/share/lxc/config/ubuntu.common.conf Do I need to change the container's configuration to point to a new location? ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1590547 Title: LXC package for trusty no longer has configuration files Status in lxc package in Ubuntu: New Bug description: Did an upgrade this morning to the latest LXC package (via the updates channel). LXC Package 2.0.1-0ubuntu1~ubuntu14.04.1 no longer has the configuration files under /usr/share/lxc/config. This causes lxc-ls to complain about missing template files. lxc-ls: parse.c: lxc_file_for_each_line: 57 Failed to parse config: lxc.include = /usr/share/lxc/config/ubuntu.common.conf Do I need to change the container's configuration to point to a new location? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1590547/+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 1573370] [NEW] package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 -- report it anyway
*** This bug is a duplicate of bug 1570310 *** https://bugs.launchpad.net/bugs/1570310 Public bug reported: Problem surfaces during "do-release-upgrade" from 15.10 to 16.04. Upgrade process halts and I had to manually "sudo apt-get -f install" followed by several "sudo apt-get update" and "upgrade" and "dist- upgrades" to end up completing the upgrade. This error remains. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 21 20:36:40 2016 DpkgTerminalLog: Preparing to unpack .../systemd_229-4ubuntu4_amd64.deb ... De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2015-07-19 (277 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Acer Aspire VN7-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=a9472da9-2f8d-484c-8d7e-cc2fb2b2feae ro splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) dmi.bios.date: 08/06/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-591G dmi.board.vendor: Acer dmi.board.version: V1.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.15 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.15:bd08/06/2015:svnAcer:pnAspireVN7-591G:pvrV1.15:rvnAcer:rnAspireVN7-591G:rvrV1.15:cvnAcer:ct10:cvrV1.15: dmi.product.name: Aspire VN7-591G dmi.product.version: V1.15 dmi.sys.vendor: Acer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1573370 Title: package systemd 229-4ubuntu4 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 -- report it anyway Status in systemd package in Ubuntu: New Bug description: Problem surfaces during "do-release-upgrade" from 15.10 to 16.04. Upgrade process halts and I had to manually "sudo apt-get -f install" followed by several "sudo apt-get update" and "upgrade" and "dist- upgrades" to end up completing the upgrade. This error remains. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 21 20:36:40 2016 DpkgTerminalLog: Preparing to unpack .../systemd_229-4ubuntu4_amd64.deb ... De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu4_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2015-07-19 (277 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Acer Aspire VN7-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=a9472da9-2f8d-484c-8d7e-cc2fb2b2feae ro splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: syst
[Touch-packages] [Bug 1561041] [NEW] open-iscsi not controlled by upstart
Public bug reported: occasionally we will have the iscsid process die on a node. this is not controlled by the iscsi-network interfaces upstart module. we would like an upstart module included. ** 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/1561041 Title: open-iscsi not controlled by upstart Status in systemd package in Ubuntu: New Bug description: occasionally we will have the iscsid process die on a node. this is not controlled by the iscsi-network interfaces upstart module. we would like an upstart module included. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1561041/+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 1452849] Re: initctl cannot find Upstart
*** This bug is a duplicate of bug 1447099 *** https://bugs.launchpad.net/bugs/1447099 Clean install of 15.10 - dist-upgrade, reboot, same error. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1452849 Title: initctl cannot find Upstart Status in upstart : New Status in upstart package in Ubuntu: Triaged Bug description: Please see Apport's automatically generated files (attached) ProblemType: RecoverableProblem DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 7 19:03:35 2015 DuplicateSignature: /sbin/upstart:indicator-session-unknown-user-error ExecutablePath: /sbin/upstart InstallationDate: Installed on 2011-12-08 (1246 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcCmdline: /sbin/upstart --user SourcePackage: upstart UpgradeStatus: Upgraded to vivid on 2015-04-24 (13 days ago) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist UserGroups: adm admin avahi avahi-autoipd cdrom dialout dip fax floppy fuse lp lpadmin mythtv plugdev sambashare tape users video whoopsie www-data icon_file: (null) is_current_user: false is_logged_in: false real_name: (null) uid: 0 upstart.upstart-event-bridge.log: upstart-event-bridge: Could not connect to system Upstart: Failed to connect to socket /com/ubuntu/upstart/local/bridge: Connection refused user_name: (null) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1452849/+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 1501913] [NEW] Apparmor Abstraction Prevents Firefox From Opening Torrents in Deluge-Gtk
Public bug reported: The apparmor abstractions in ubuntu-bittorrent-clients do not allow applications like firefox to open torrent files using 'deluge-gtk', although it works fine for 'deluge'. Simple fix is to change one line in ubuntu-bittorrent-clients. Change this line in ubuntu-bittorrent-clients: /usr/bin/deluge Cxr -> sanitized_helper, to this: /usr/bin/deluge{,-gtk} Cxr -> sanitized_helper, ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1501913 Title: Apparmor Abstraction Prevents Firefox From Opening Torrents in Deluge-Gtk Status in apparmor package in Ubuntu: New Bug description: The apparmor abstractions in ubuntu-bittorrent-clients do not allow applications like firefox to open torrent files using 'deluge-gtk', although it works fine for 'deluge'. Simple fix is to change one line in ubuntu-bittorrent-clients. Change this line in ubuntu-bittorrent-clients: /usr/bin/deluge Cxr -> sanitized_helper, to this: /usr/bin/deluge{,-gtk} Cxr -> sanitized_helper, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1501913/+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 1470299] [NEW] package unattended-upgrades 0.82.8ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: This occurred as the system was booting up. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: unattended-upgrades 0.82.8ubuntu0.3 ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.5 AptOrdering: unattended-upgrades: Install unattended-upgrades: Configure Architecture: amd64 Date: Mon Jun 29 20:47:30 2015 DuplicateSignature: package:unattended-upgrades:0.82.8ubuntu0.3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-03-21 (831 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) PackageArchitecture: all SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.82.8ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2015-05-07 (54 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-05-07T13:31:12.701689 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1470299 Title: package unattended-upgrades 0.82.8ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: This occurred as the system was booting up. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: unattended-upgrades 0.82.8ubuntu0.3 ProcVersionSignature: Ubuntu 3.16.0-41.57-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8.5 AptOrdering: unattended-upgrades: Install unattended-upgrades: Configure Architecture: amd64 Date: Mon Jun 29 20:47:30 2015 DuplicateSignature: package:unattended-upgrades:0.82.8ubuntu0.3:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-03-21 (831 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423) PackageArchitecture: all SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.82.8ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2015-05-07 (54 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-05-07T13:31:12.701689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1470299/+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 1466103] Re: dnsmasq runs unconfined due to starting before apparmor on boot
My currently running dnsmasq (which is confined the way it should be) was started by NetworkManager: $> ps axjf PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND 1 1873 1873 1873 ? -1 Ssl 0 0:00 NetworkManager 1873 2047 2047 1873 ? -1 S65534 0:00 \_ /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1466103 Title: dnsmasq runs unconfined due to starting before apparmor on boot Status in dnsmasq package in Ubuntu: Triaged Bug description: Description and behavior are identical to Bug #573315. However, the solution to that bug was to make a change to /etc/apparmor.d/usr.sbin.libvirtd. There is no longer an apparmor profile /etc/apparmor.d/usr.sbin.libvirtd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466103/+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 1466103] Re: dnsmasq runs unconfined due to starting before apparmor on boot
The dnsmasq apparmor profile comes from package apparmor-profiles. My installed version is apparmor-profiles 2.8.95~2430-0ubuntu5.1. It recently updated (June 16). I have only rebooted my machine three times since, and saw the "unconfined" only once. I will continue to watch to see if it occurs again. $> lsb_release -r Release:14.04 $> ls -l /sbin/init -rwxr-xr-x 1 root root 265848 Jul 18 2014 /sbin/init aa-status is uploaded as attachment ** Attachment added: "Output from aa-status" https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466103/+attachment/4416907/+files/aa-status.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1466103 Title: dnsmasq runs unconfined due to starting before apparmor on boot Status in dnsmasq package in Ubuntu: Incomplete Bug description: Description and behavior are identical to Bug #573315. However, the solution to that bug was to make a change to /etc/apparmor.d/usr.sbin.libvirtd. There is no longer an apparmor profile /etc/apparmor.d/usr.sbin.libvirtd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466103/+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 1466103] Re: dnsmasq runs unconfined due to starting before apparmor on boot
Additional info: Only happens intermittently. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1466103 Title: dnsmasq runs unconfined due to starting before apparmor on boot Status in dnsmasq package in Ubuntu: New Bug description: Description and behavior are identical to Bug #573315. However, the solution to that bug was to make a change to /etc/apparmor.d/usr.sbin.libvirtd. There is no longer an apparmor profile /etc/apparmor.d/usr.sbin.libvirtd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466103/+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 1466103] [NEW] dnsmasq runs unconfined due to starting before apparmor on boot
Public bug reported: Description and behavior are identical to Bug #573315. However, the solution to that bug was to make a change to /etc/apparmor.d/usr.sbin.libvirtd. There is no longer an apparmor profile /etc/apparmor.d/usr.sbin.libvirtd. ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor ** Package changed: libvirt (Ubuntu) => dnsmasq (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1466103 Title: dnsmasq runs unconfined due to starting before apparmor on boot Status in dnsmasq package in Ubuntu: New Bug description: Description and behavior are identical to Bug #573315. However, the solution to that bug was to make a change to /etc/apparmor.d/usr.sbin.libvirtd. There is no longer an apparmor profile /etc/apparmor.d/usr.sbin.libvirtd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466103/+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 1364452] Re: People's own phone number isn't where they expect to find it
Number not even showing correctly in "About" for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1364452 Title: People's own phone number isn't where they expect to find it Status in Address Book App: New Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: Triaged Bug description: Twenty people were given an Ubuntu phone and asked to find their own phone number. (10 were iPhone users, 8 Android, 1 Windows Phone, and 1 feature phone user.) The first place they looked: - 9 in the Contacts app - 5 in System Settings "Phone" screen - 3 in System Settings "About" screen - 2 in the Dialer app contacts screen - 1 in System Settings "Cellular" screen. So, our current placement of the phone number in the "About" screen (bug 1221908) is suboptimal. Instead it should be in the Contacts app, and possibly in the "Phone" screen. Where the phone is dual SIM, both phone numbers should be shown. This first needs design work. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1364452/+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 1428811] Re: Trusty hwe kernel (utopic) gpio shutdown trigger for ProLiant m400 cartridges
I tested that proposed udev does not regress the 3.13 kernel and that it fixes the issue when running the hwe kernel. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1428811 Title: Trusty hwe kernel (utopic) gpio shutdown trigger for ProLiant m400 cartridges Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Fix Committed Bug description: This is an additional change following after the m800 bug (LP: #1347776) and m400 bug (LP: #1354306), udev/systemd needs a rule to cover triggering a graceful shutdown on the HP Proliant m400 Cartridge when running the utopic hwe kernel in trusty. [Impact] Currently, graceful shutdown via the iLO works when running the base trusty kernel, but if the hwe kernel is installed, it does not. [Test Case] Initiate a graceful shutdown via the iLO. [Regression Potential] The new rule is pretty tightly bound to the m400 system - so the risk of this rule matching and impacting behavior on a different platform is minimal. This will presumably cause new code to run and read /proc/device-tree/model on other platforms - but this is already done for the m800 system in both utopic and trusty as well as the 3.13.0 kernel m400 rule. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1428811/+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
Re: [Touch-packages] [Bug 1080107] auto log-in doesn't function after logout
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1080107 Title: auto log-in doesn't function after logout Status in Light Display Manager: Incomplete Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Enabling auto log-in for a user causes a ubuntu unity session to be started when the operating system is booted. The session has a "Log Out..." item on the pull-down menu item in the upper right corner. When this command is used, the session is logged out, but there is no subsequent auto log-in. Consequently, remote access by VNC (vinagre/vino) ceases. This problem has been around for several releases, but is definately present for the one below: lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1080107/+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 1432414] [NEW] printing service not available after recent upgrade
Public bug reported: Prior to a recent update, the wireless printer worked fine, now the system settings printing configuration says that "Printing service not available. Start the service on this computer or connect to another server." The "Start Service" button is greyed out leaving just the "Connect" button. When clicked it brings up a dialog asking where the cups server is located, default is localhost, and an unchecked checkbox for "Require encryption." Click the "Continue" button and get an error message: "There was an error during the CUPS operation: 'failed to connect to server'." Looking at the cups error log, this message is printed: E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.key" is a bad symlink - No such file or directory It seems the ssl-cert package's snakeoil certs were removed by something, reinstalling that package restored the ssl files the above links point to. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: cups 1.7.5-3ubuntu3.1 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.key" is a bad symlink - No such file or directory CurrentDesktop: Unity Date: Sun Mar 15 14:46:34 2015 Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: System76, Inc. Wild Dog Performance PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-7520.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-7520.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=968bc182-d0be-4b2c-9558-2a6d5af9b400 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2306 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: wilp11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2306:bd10/09/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp11:rvnASUSTeKCOMPUTERINC.:rnH97-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp11: dmi.product.name: Wild Dog Performance dmi.product.version: wilp11 dmi.sys.vendor: System76, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1432414 Title: printing service not available after recent upgrade Status in cups package in Ubuntu: New Bug description: Prior to a recent update, the wireless printer worked fine, now the system settings printing configuration says that "Printing service not available. Start the service on this computer or connect to another server." The "Start Service" button is greyed out leaving just the "Connect" button. When clicked it brings up a dialog asking where the cups server is located, default is localhost, and an unchecked checkbox for "Require encryption." Click the "Continue" button and get an error message: "There was an error during the CUPS operation: 'failed to connect to server'." Looking at the cups error log, this message is printed: E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.key" is a bad symlink - No such file or directory It seems the ssl-cert package's snakeoil certs were removed by something, reinstalling that package restored the ssl files the above links point to. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: cups 1.7.5-3ubuntu3.1 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.key" is a bad symlink - No such file or directory CurrentDesktop: Unity Date: Sun Mar 15 14:46:34 2015 Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: System76, Inc. Wild Dog Performance PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-7520.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-7520.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/v
[Touch-packages] [Bug 1428811] Re: Trusty hwe kernel (utopic) gpio shutdown trigger for ProLiant m400 cartridges
Is there anything I can do to help that process along? -- 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/1428811 Title: Trusty hwe kernel (utopic) gpio shutdown trigger for ProLiant m400 cartridges Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Trusty: In Progress Bug description: This is an additional change following after the m800 bug (LP: #1347776) and m400 bug (LP: #1354306), udev/systemd needs a rule to cover triggering a graceful shutdown on the HP Proliant m400 Cartridge when running the utopic hwe kernel in trusty. [Impact] Currently, graceful shutdown via the iLO works when running the base trusty kernel, but if the hwe kernel is installed, it does not. [Test Case] Initiate a graceful shutdown via the iLO. [Regression Potential] The new rule is pretty tightly bound to the m400 system - so the risk of this rule matching and impacting behavior on a different platform is minimal. This will presumably cause new code to run and read /proc/device-tree/model on other platforms - but this is already done for the m800 system in both utopic and trusty as well as the 3.13.0 kernel m400 rule. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1428811/+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 1428811] Re: Trusty hwe kernel (utopic) gpio shutdown trigger for ProLiant m400 cartridges
** Patch added: "trusty-proposed patch for systemd" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1428811/+attachment/4335565/+files/trusty-proposed.patch ** Tags added: hs-arm64 ** Description changed: This is an additional change following after the m800 bug (LP: #1347776) and m400 bug (LP: #1354306), udev/systemd needs a rule to cover triggering a graceful shutdown on the HP Proliant m400 Cartridge when running the utopic hwe kernel in trusty. [Impact] - Currently, graceful shutdown via the iLO works when running the base trusty kernel, but if the hwe kernel is installed, it stops. + Currently, graceful shutdown via the iLO works when running the base trusty kernel, but if the hwe kernel is installed, it does not. [Test Case] Initiate a graceful shutdown via the iLO. [Regression Potential] The new rule is pretty tightly bound to the m400 system - so the risk of this rule matching and impacting behavior on a different platform is minimal. This will presumably cause new code to run and read /proc/device-tree/model on other platforms - but this is already done for the m800 system in both utopic and trusty as well as the 3.13.0 kernel m400 rule. -- 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/1428811 Title: Trusty hwe kernel (utopic) gpio shutdown trigger for ProLiant m400 cartridges Status in systemd package in Ubuntu: New Bug description: This is an additional change following after the m800 bug (LP: #1347776) and m400 bug (LP: #1354306), udev/systemd needs a rule to cover triggering a graceful shutdown on the HP Proliant m400 Cartridge when running the utopic hwe kernel in trusty. [Impact] Currently, graceful shutdown via the iLO works when running the base trusty kernel, but if the hwe kernel is installed, it does not. [Test Case] Initiate a graceful shutdown via the iLO. [Regression Potential] The new rule is pretty tightly bound to the m400 system - so the risk of this rule matching and impacting behavior on a different platform is minimal. This will presumably cause new code to run and read /proc/device-tree/model on other platforms - but this is already done for the m800 system in both utopic and trusty as well as the 3.13.0 kernel m400 rule. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1428811/+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 1428811] [NEW] Trusty hwe kernel (utopic) gpio shutdown trigger for ProLiant m400 cartridges
Public bug reported: This is an additional change following after the m800 bug (LP: #1347776) and m400 bug (LP: #1354306), udev/systemd needs a rule to cover triggering a graceful shutdown on the HP Proliant m400 Cartridge when running the utopic hwe kernel in trusty. [Impact] Currently, graceful shutdown via the iLO works when running the base trusty kernel, but if the hwe kernel is installed, it stops. [Test Case] Initiate a graceful shutdown via the iLO. [Regression Potential] The new rule is pretty tightly bound to the m400 system - so the risk of this rule matching and impacting behavior on a different platform is minimal. This will presumably cause new code to run and read /proc/device-tree/model on other platforms - but this is already done for the m800 system in both utopic and trusty as well as the 3.13.0 kernel m400 rule. ** 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/1428811 Title: Trusty hwe kernel (utopic) gpio shutdown trigger for ProLiant m400 cartridges Status in systemd package in Ubuntu: New Bug description: This is an additional change following after the m800 bug (LP: #1347776) and m400 bug (LP: #1354306), udev/systemd needs a rule to cover triggering a graceful shutdown on the HP Proliant m400 Cartridge when running the utopic hwe kernel in trusty. [Impact] Currently, graceful shutdown via the iLO works when running the base trusty kernel, but if the hwe kernel is installed, it stops. [Test Case] Initiate a graceful shutdown via the iLO. [Regression Potential] The new rule is pretty tightly bound to the m400 system - so the risk of this rule matching and impacting behavior on a different platform is minimal. This will presumably cause new code to run and read /proc/device-tree/model on other platforms - but this is already done for the m800 system in both utopic and trusty as well as the 3.13.0 kernel m400 rule. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1428811/+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 1300367] Re: rsync 3.1.0 and 3.0.9 incompatibility
I tried the patch and I can confirm it worked once. However it didn't fail every time before so it probably needs a bit more testing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1300367 Title: rsync 3.1.0 and 3.0.9 incompatibility Status in rsync: In Progress Status in “rsync” package in Ubuntu: Triaged Bug description: When running rsync on a directory of a few hundred files from rsync 3.0.9-4 on Ubuntu 13.04 Raring to rsync 3.1.0-2 on Ubuntu 14.04 Trusty rsync errors with: rsync error: error in rsync protocol data stream (code 12) at io.c(441) [sender=3.0.9] Here is the full command I'm trying to run: rsync --delay-updates -FF --compress --timeout=10 --archive --rsh 'ssh -o StrictHostKeyChecking=no' --out-format='<>%i %n%L' templates/dotfiles/ wirehive@172.2.0.1.128:/home/wirehive/ If I repeatedly run this after maybe 4 times it will succeed. The same sounding bug is reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1014769 and here: https://bugzilla.samba.org/show_bug.cgi?id=10332 To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1300367/+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 1367305] [NEW] package procps 1:3.2.8-11ubuntu6.3 failed to install/upgrade: ErrorMessage: package procps is already installed and configured.
Public bug reported: This error occurred after an upgrade to Lubuntu 14. lx panel was not starting on system startup, I fixed that using these instructions: http://askubuntu.com/questions/451858/blank-desktop-after-upgrading- lubuntu-to-the-next-version But there are still other errors I am working through. Everything seemed to be working fine before the upgrade. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: procps ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 AptdaemonVersion: 1.1.1-1ubuntu5 Architecture: amd64 Date: Thu Sep 4 22:42:22 2014 DuplicateSignature: package:procps:1:3.2.8-11ubuntu6.3:ErrorMessage: package procps is already installed and configured ErrorMessage: ErrorMessage: package procps is already installed and configured InstallationDate: Installed on 2014-01-10 (242 days ago) InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release amd64 (20120423) SourcePackage: procps Title: package procps 1:3.2.8-11ubuntu6.3 failed to install/upgrade: ErrorMessage: package procps is already installed and configured UpgradeStatus: Upgraded to trusty on 2014-09-05 (4 days ago) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1367305 Title: package procps 1:3.2.8-11ubuntu6.3 failed to install/upgrade: ErrorMessage: package procps is already installed and configured. Status in “procps” package in Ubuntu: New Bug description: This error occurred after an upgrade to Lubuntu 14. lx panel was not starting on system startup, I fixed that using these instructions: http://askubuntu.com/questions/451858/blank-desktop-after-upgrading- lubuntu-to-the-next-version But there are still other errors I am working through. Everything seemed to be working fine before the upgrade. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: procps ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 AptdaemonVersion: 1.1.1-1ubuntu5 Architecture: amd64 Date: Thu Sep 4 22:42:22 2014 DuplicateSignature: package:procps:1:3.2.8-11ubuntu6.3:ErrorMessage: package procps is already installed and configured ErrorMessage: ErrorMessage: package procps is already installed and configured InstallationDate: Installed on 2014-01-10 (242 days ago) InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release amd64 (20120423) SourcePackage: procps Title: package procps 1:3.2.8-11ubuntu6.3 failed to install/upgrade: ErrorMessage: package procps is already installed and configured UpgradeStatus: Upgraded to trusty on 2014-09-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1367305/+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