[Touch-packages] [Bug 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbo
moving back to the driver https://github.com/intel/intel-vaapi-driver/issues/419 ** Bug watch added: github.com/intel/intel-vaapi-driver/issues #419 https://github.com/intel/intel-vaapi-driver/issues/419 ** Package changed: mesa (Ubuntu) => intel-vaapi-driver (Ubuntu) ** Also affects: libva (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in intel-vaapi-driver package in Ubuntu: New Status in libva package in Ubuntu: New Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1813131/+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 1783499] Re: systemd: Failed to send signal
After 36h of rebooting, the system is stuck. Attached is the debug log. ** Attachment added: "shutdown-logsysd237.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5232412/+files/shutdown-logsysd237.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1783499 Title: systemd: Failed to send signal Status in dbus package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit change signal for systemd-random-seed.service: Transport endpoint is not connected [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: Failed to send unit change signal for sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not connected [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by peer [3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected How to reproduce: 1. enable debug level journal LogLevel=debug in /etc/systemd/system.conf 2. reboot the system 3. journalctl | grep "Failed to send" sliu@vmlxhi-094:~$ lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 sliu@vmlxhi-094:~$ systemctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN sliu@vmlxhi-094:~$ dbus-daemon --version D-Bus Message Bus Daemon 1.10.6 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbo
probably needs a newer libva too -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in intel-vaapi-driver package in Ubuntu: New Status in libva package in Ubuntu: New Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1813131/+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 1813227] Re: lvm2-pvscan services fails to start on S390X DPM
Hi, I'm not sure what exactly will be needed, but the following would surely help. Do you have a way to fetch the following while at the error condition and attach it here?: - sudo multipath -ll - lsblk -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1813227 Title: lvm2-pvscan services fails to start on S390X DPM Status in lvm2 package in Ubuntu: New Bug description: The lvm2-pvscan service fails to start in the MAAS ephemeral environment. The service takes ~3 minutes to fail, blocking boot until failure. Curtin is expereincing a similar bug(LP:1813228) due to LVM. Release: 18.10(18.04 does not currently boot on S390X DPM) Kernel: 4.18.0-13-generic LVM: 2.02.176-4.1ubuntu3 root@node3:~# lvm pvscan --cache --activate ay 8:98 WARNING: Not using lvmetad because duplicate PVs were found. WARNING: Autoactivation reading from disk instead of lvmetad. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sde2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdba2 was already found on /dev/sdhd2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdfj2 was already found on /dev/sddi2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdg2 was already found on /dev/sddi2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdbc2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sdbf2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sddb2 was already found on /dev/sdhd2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sddr2 was already found on /dev/sdbq2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdbh2 was already found on /dev/sddi2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sddd2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sddg2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdfc2 was already found on /dev/sdhd2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdfs2 was already found on /dev/sdbq2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdp2 was already found on /dev/sdbq2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. Cannot activate LVs in VG zkvm4 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "zkvm4" now active zkvm4: autoactivation failed. Cannot activate LVs in VG zkvm1 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "zkvm1" now active zkvm1: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_473D86E3 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_473D86E3" now active Z_APPL_ROOT_lvm_473D86E3: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_BBD0E8D4 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_BBD0E8D4" now active Z_APPL_ROOT_lv
[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
@andre-jutisz From the log it looks like unattended-upgrades stops gracefully
during shutdown and there are not broken packages upon next invocation.
Do you have other logs that suggest otherwise?
--
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/1778219
Title:
unattended-upgrades hangs on shutdown, leaves system in a broken state
Status in init-system-helpers package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
Confirmed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in init-system-helpers source package in Xenial:
Confirmed
Status in snapd source package in Xenial:
Confirmed
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in init-system-helpers source package in Bionic:
Confirmed
Status in snapd source package in Bionic:
Confirmed
Status in unattended-upgrades source package in Bionic:
Fix Released
Status in unattended-upgrades source package in Cosmic:
Fix Released
Bug description:
[Impact]
* Unattended-upgrades hangs and gets killed when installing upgrades
that stat/stop services on shutdown, leaving the system in a broken
state
[Test Case]
* Install an updated bionic system:
$ lxc launch ubuntu:18.04 uu-shutdown-test
# apt update
...
* When testing the fixed version, install upgrade u-u at this point checking
that u-u.service is set up before and is wanted by shutdown.target:
# systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" [color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
* Configure u-u to run on shutdown and install -updates:
# echo 'Unattended-Upgrade::InstallOnShutdown "true";' >
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too
* Downgrade snapd:
# apt install snapd=2.32.5+18.04
* Dowload packages for u-u:
# unattended-upgrade --download-only
* Reboot using logind to let inhibitors hold up shutdown:
# dbus-send --system --print-reply --dest=org.freedesktop.login1
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false
* With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
`-{unattended-upgr}
* With fixed u-u observe snapd update taking place and system
rebooting after a few seconds with all updates installed
* Since this fix is partially reverting the fix for LP: #1654600
please test LP: #1654600 as well to avoid regressions.
[Regression Potential]
* As part of the fix manual changes were made to postinst to properly
transition from coupling u-u.service with multi-user.target to coupling it with
shutdown.target again which can make u-u started during normal boot when there
is a bug in the implementation.
on-testing the SRU.
* Due to relationship changes between u-u.service, other services and
targets u-u may fail to run on shutdown in case of an unexpected regression.
* There is a rarely occurring new crash caused by the (second) fix tracked in
LP: #1806487.
[Original Bug Text]
When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
package installation on various packages hangs until the systemd
ShutdownTimeout (30min) is expired and systemd kills all processes and
powers off/reboots the system.
This leaves packages in an unconfigured, broken state. At least
sometimes this cannot be fixed with a "dpkg --configure -a", but
instead requires the user to manually reinstall the package that
caused the hang.
This appears to be a deadlock, because the hanging commands are always
"systemctl stop ..." or "systemctl restart ...", etc.. If I understand
this correctly, those systemctl commands block because systemd tries
to shutdown the system and tries to satisfy all dependencies for the
shutdown targets before those systemctl commands could get executed,
whic
[Touch-packages] [Bug 1495339] Re: package slapd 2.4.31-1+nmu2ubuntu12.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
** Changed in: insserv (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to insserv in Ubuntu. https://bugs.launchpad.net/bugs/1495339 Title: package slapd 2.4.31-1+nmu2ubuntu12.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in insserv package in Ubuntu: New Status in insserv package in Debian: Fix Released Bug description: I belive that is the version of ubuntu because the hardware and some apps is very fresh, just this. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: slapd 2.4.31-1+nmu2ubuntu12.2 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Sun Sep 13 20:43:45 2015 DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu12.2:el subproceso instalado el script post-installation devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2015-05-15 (121 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: openldap Title: package slapd 2.4.31-1+nmu2ubuntu12.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/insserv/+bug/1495339/+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 1812955] Re: g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding
Fixed upstream: https://gitlab.gnome.org/GNOME/mutter/merge_requests/412 ** Changed in: gobject-introspection (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1812955 Title: g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding Status in gobject-introspection package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gobject-introspection/issues/260 --- g-ir-scanner is crashing with SIGSEGV instead of succeeding. So I can't build gnome-shell any more. Actually it looks like some kind of temporary sub-command "Shell-0.1" of g-ir-scanner that's crashing: /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include --no-libtool --namespace=Shell --nsversion=0.1 --warn-all --output src/Shell-0.1.gir --quiet -I/home/dan/git/gnome-shell/src -I/home/dan/git/gnome-shell/build/src -I./. -I../. -I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray --filelist=/home/dan/git/gnome-shell/build/src/src@@gnome-shell@sha/Shell_0.1_gir_filelist --include=Clutter-4 --include=ClutterX11-4 --include=Meta-4 --include=Gcr-3 --include=PolkitAgent-1.0 --include=NM-1.0 --include-uninstalled=subprojects/gvc/Gvc-1.0.gir --include-uninstalled=src/ShellMenu-0.1.gir --include-uninstalled=src/st/St-1.0.gir --cflags-begin -I./. -I../. -I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -include /usr/include/mozjs-60/js/RequiredDefines.h -I/usr/include/gobject-introspection-1.0 -I/usr/include/mozjs-60 -I/usr/include/gjs-1.0 -I/home/dan/tmp.gs/include/mutter-4/clutter -I/home/dan/tmp.gs/include/mutter-4/cogl -I/usr/include/json-glib-1.0 -I/usr/include/libwacom-1.0 -I/usr/include/startup-notification-1.0 -I/usr/include/polkit-1 -I/usr/include/gcr-3 -I/usr/include/gck-1 -I/usr/include/p11-kit-1 -I/usr/include/libnm -I/usr/include/libsecret-1 -I/usr/include/gstreamer-1.0 -D_REENTRANT -I/home/dan/tmp.gs/include/mutter-4 -I/home/dan/tmp.gs/include/gsettings-desktop-schemas -I/usr/include/gnome-desktop-3.0 -I/usr/include/gnome-settings-daemon-3.0 -I/usr/include/gudev-1.0 --cflags-end -L/home/dan/git/gnome-shell/build/src --add-include-path=/usr/share/gir-1.0 --add-include-path=/home/dan/tmp.gs/lib/x86_64-linux-gnu/mutter-4 --add-include-path=/home/dan/git/gnome-shell/build/subprojects/gvc --add-include-path=/home/dan/git/gnome-shell/build/src --add-include-path=/home/dan/git/gnome-shell/build/src/st -L/home/dan/git/gnome-shell/build/src -L/home/dan/git/gnome-shell/build/src/st -L/lib/x86_64-linux-gnu --library gnome-shell --extra-library=gio-2.0 --extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=xml2 --extra-library=gtk-3 --extra-library=gdk-3 --extra-library=pangocairo-1.0 --extra-library=pango-1.0 --extra-library=atk-1.0 --extra-library=cairo-gobject --extra-library=cairo --extra-library=gdk_pixbuf-2.0 --extra-library=atk-bridge-2.0 --extra-library=gjs -L/home/dan/tmp.gs//lib/x86_64-linux-gnu/mutter-4 --extra-library=mutter-clutter-4 --extra-library=m --extra-library=json-glib-1.0 --extra-library=pangoft2-1.0 --extra-library=fontconfig --extra-library=freetype --extra-library=wayland-egl --extra-library=wayland-client --extra-library=Xtst --extra-library=Xi --extra-library=udev --extra-library=input --extra-library=xkbcommon --extra-library=wacom --extra-library=mutter-cogl-4 --extra-library=gmodule-2.0 -pthread --extra-library=wayland-server --extra-library=EGL --extra-library=X11 --extra-library=Xext --extra-library=Xdamage --extra-library=Xfixes --extra-library=Xcomposite --extra-library=Xrandr --extra-library=GL --extra-library=GLESv2 --extra-library=mutter-cogl-pango-4 --extra-library=startup-notification-1 --extra-library=girepository-1.0 --extra-library=polkit-agent-1 --extra-library=polkit-gobject-1 --extra-library=gcr-base-3 --extra-library=gck-1 --extra-library=p11-kit --extra-library=systemd --extra-library=nm --extra-library=secret-1 --extra-library=gstreamer-1.0 --extra-library=gstbase-1.0 -L/home/dan/tmp.gs//lib/x86_64-linux-gnu --extra-library=mutter-4 --extra-library=gnome-desktop-3 --extra-library=canberra --extra-library=gudev-1.0 --extra-librar
[Touch-packages] [Bug 1813208] Re: Paired bluetooth mice irregularities after resume from suspend
Also, is bug 1812446 related to this? Please remember to answer bug 1812446 too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1813208 Title: Paired bluetooth mice irregularities after resume from suspend Status in bluez package in Ubuntu: Incomplete Bug description: System model: Dell XPS 9370 Killer Wireless 1435 Ubuntu Dell OEM - 18.04.1 LTS If a Bluetooth device is paired while system is in suspend, upon resuming the system's Bluetooth functionality will intermittently be lost whereas the expectation is the functionality would resume as before. Bluetooth functionality can be restored by restarting system, entering BIOS, and then exiting BIOS even if nothing is changed. Standard reboots without entering BIOS will not restore Bluetooth functionality. Note: Sometimes Wireless is missing as well, but that can be restored through normal reboots without going into BIOS. Tested on XPS 9370 with Ubuntu 18.04 Dell OEM clean install. Issue was observed to occur with both of the following devices: HP x4000b Bluetooth mouse Logitech G603 Bluetooth mouse Issue does not seem to occur if system is only allowed to suspend for a short time, issue only occurred if system was left in suspend overnight. Issue observed to occur both on battery and AC power, power source did not seem to affect the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1813208/+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 1813208] Re: Paired bluetooth mice irregularities after resume from suspend
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1813208 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => bluez (Ubuntu) ** Tags added: bionic ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1813208 Title: Paired bluetooth mice irregularities after resume from suspend Status in bluez package in Ubuntu: Incomplete Bug description: System model: Dell XPS 9370 Killer Wireless 1435 Ubuntu Dell OEM - 18.04.1 LTS If a Bluetooth device is paired while system is in suspend, upon resuming the system's Bluetooth functionality will intermittently be lost whereas the expectation is the functionality would resume as before. Bluetooth functionality can be restored by restarting system, entering BIOS, and then exiting BIOS even if nothing is changed. Standard reboots without entering BIOS will not restore Bluetooth functionality. Note: Sometimes Wireless is missing as well, but that can be restored through normal reboots without going into BIOS. Tested on XPS 9370 with Ubuntu 18.04 Dell OEM clean install. Issue was observed to occur with both of the following devices: HP x4000b Bluetooth mouse Logitech G603 Bluetooth mouse Issue does not seem to occur if system is only allowed to suspend for a short time, issue only occurred if system was left in suspend overnight. Issue observed to occur both on battery and AC power, power source did not seem to affect the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1813208/+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 1813208] [NEW] Paired bluetooth mice irregularities after resume from suspend
You have been subscribed to a public bug: System model: Dell XPS 9370 Killer Wireless 1435 Ubuntu Dell OEM - 18.04.1 LTS If a Bluetooth device is paired while system is in suspend, upon resuming the system's Bluetooth functionality will intermittently be lost whereas the expectation is the functionality would resume as before. Bluetooth functionality can be restored by restarting system, entering BIOS, and then exiting BIOS even if nothing is changed. Standard reboots without entering BIOS will not restore Bluetooth functionality. Note: Sometimes Wireless is missing as well, but that can be restored through normal reboots without going into BIOS. Tested on XPS 9370 with Ubuntu 18.04 Dell OEM clean install. Issue was observed to occur with both of the following devices: HP x4000b Bluetooth mouse Logitech G603 Bluetooth mouse Issue does not seem to occur if system is only allowed to suspend for a short time, issue only occurred if system was left in suspend overnight. Issue observed to occur both on battery and AC power, power source did not seem to affect the issue. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- Paired bluetooth mice irregularities after resume from suspend https://bugs.launchpad.net/bugs/1813208 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813160] Re: display problem
1. It appears you don't yet have the latest version of 'xserver-xorg- video-intel' that was released in 2016. If you have installed any PPAs then please remove them using 'ppa-purge' and then fully update the system: sudo apt update sudo apt full-upgrade 2. Please also explain in more detail when the problem happens. 3. Your hardware is much newer than the Ubuntu release you are trying to use so please also try live booting a newer version and tell us if that avoids the problem: http://releases.ubuntu.com/18.04/ ** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu) ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813160 Title: display problem Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: display is going black for fraction of second. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 24 18:47:01 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-127-generic, x86_64: installed oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-94-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-127-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-94-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0841] InstallationDate: Installed on 2018-08-26 (151 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Vostro 3478 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=a241a9ad-c097-481d-b704-f28b73bb8feb ro acpi_rev_override quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 08R7RH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd05/22/2018:svnDellInc.:pnVostro3478:pvr:rvnDellInc.:rn08R7RH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Vostro 3478 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Jan 24 16:25:51 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1805 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1813160/+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 1812446] Re: Bluetooth mouse stops responding after 24-48 hours of connectivity
Steven, Please click Hide on all the above comments. Only the original reporter (Juan) should run apport-collect here. Please then report your own bug by running: ubuntu-bug bluez -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1813234] Re: package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1813234 Title: package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: crashes on start up of gui ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 20 13:32:42 2019 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-25 (152 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools 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/initramfs-tools/+bug/1813234/+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 1813234] [NEW] package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: crashes on start up of gui ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 20 13:32:42 2019 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-25 (152 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1813234 Title: package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: crashes on start up of gui ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: udev:amd64: Install libudev1:amd64: Install libudev1:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Jan 20 13:32:42 2019 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-08-25 (152 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3.6 failed to install/upgrade: installed initramfs-tools 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/initramfs-tools/+bug/1813234/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-control-center/+git/gnome-control-center/+merge/362226 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK 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/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-control-center/+git/gnome-control-center/+merge/362225 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK 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/gnome-control-center/+bug/1745032/+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 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
Yeah apologies, I have to allocate another U18 host and build one. Will aim for tomorrow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Fix Released Status in debirf package in Ubuntu: Confirmed Status in busybox source package in Bionic: In Progress Status in debirf source package in Bionic: Confirmed Status in busybox source package in Cosmic: Fix Released Status in debirf source package in Cosmic: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+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 1806848] Re: not sure
** Changed in: debconf (Ubuntu) Status: Incomplete => Confirmed ** Changed in: debconf (Ubuntu) Status: Confirmed => In Progress ** Changed in: debconf (Ubuntu) Assignee: (unassigned) => lou (megamephistopheles) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1806848 Title: not sure Status in debconf package in Ubuntu: In Progress Bug description: it gave me a error but did not give detailed info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1806848/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362224 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK 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/gnome-control-center/+bug/1745032/+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 1782511] Re: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all
today pc builtin speaker works, I didn't change anythings here is the log today: http://www.alsa-project.org/db/?f=596407a5d73efbe9caa99db23ca2a5586664b45a -- 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/1782511 Title: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: none ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 2209 F...m pulseaudio /dev/snd/pcmC0D0p: ubuntu 2209 F...m pulseaudio /dev/snd/controlC0: ubuntu 2209 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 22:19:23 2018 InstallationDate: Installed on 2018-07-19 (0 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=en_CA.UTF-8 SHELL=/bin/bash 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/pcmC0D0c: ubuntu 2209 F...m pulseaudio /dev/snd/pcmC0D0p: ubuntu 2209 F...m pulseaudio /dev/snd/controlC0: gdm 961 F pulseaudio ubuntu 2209 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [UX370UAR, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX370UAR.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX370UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX370UAR.303:bd11/16/2017:svnASUSTeKCOMPUTERINC.:pnUX370UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX370UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: UX dmi.product.name: UX370UAR 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/1782511/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-shell (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK 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/gnome-control-center/+bug/1745032/+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 1813227] Re: lvm2-pvscan services fails to start on S390X DPM
** Description changed: The lvm2-pvscan service fails to start in the MAAS ephemeral environment. The service takes ~3 minutes to fail, blocking boot until - failure. + failure. Curtin is expereincing a similar bug(LP:1813228) due to LVM. Release: 18.10(18.04 does not currently boot on S390X DPM) Kernel: 4.18.0-13-generic LVM: 2.02.176-4.1ubuntu3 root@node3:~# lvm pvscan --cache --activate ay 8:98 - WARNING: Not using lvmetad because duplicate PVs were found. - WARNING: Autoactivation reading from disk instead of lvmetad. - WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2 was already found on /dev/sdfe2. - WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sde2 was already found on /dev/sdfh2. - WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdba2 was already found on /dev/sdhd2. - WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdfj2 was already found on /dev/sddi2. - WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdg2 was already found on /dev/sddi2. - WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdbc2 was already found on /dev/sdfe2. - WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sdbf2 was already found on /dev/sdfh2. - WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sddb2 was already found on /dev/sdhd2. - WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sddr2 was already found on /dev/sdbq2. - WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdbh2 was already found on /dev/sddi2. - WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sddd2 was already found on /dev/sdfe2. - WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sddg2 was already found on /dev/sdfh2. - WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdfc2 was already found on /dev/sdhd2. - WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdfs2 was already found on /dev/sdbq2. - WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdp2 was already found on /dev/sdbq2. - WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. - WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. - WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. - WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. - WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. - WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. - WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. - WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. - WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. - WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. - WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. - WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. - WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. - WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. - WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. - Cannot activate LVs in VG zkvm4 while PVs appear on duplicate devices. - 0 logical volume(s) in volume group "zkvm4" now active - zkvm4: autoactivation failed. - Cannot activate LVs in VG zkvm1 while PVs appear on duplicate devices. - 0 logical volume(s) in volume group "zkvm1" now active - zkvm1: autoactivation failed. - Cannot activate LVs in VG Z_APPL_ROOT_lvm_473D86E3 while PVs appear on duplicate devices. - 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_473D86E3" now active - Z_APPL_ROOT_lvm_473D86E3: autoactivation failed. - Cannot activate LVs in VG Z_APPL_ROOT_lvm_BBD0E8D4 while PVs appear on duplicate devices. - 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_BBD0E8D4" now active - Z_APPL_ROOT_lvm_BBD0E8D4: autoactivation failed. - Cannot activate LVs in VG Z_APPL_ROOT_lvm_382F5B8E while PVs appear on duplicate devices. - 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_382F5B8E" now active - Z_APPL_ROOT_lvm_382F5B8E: autoactivation failed. + WARNING: Not using lvmetad because duplicate PVs were found. + WARNING: Autoactivation reading from disk instead of lvmetad. + WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK 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/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-control-center (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: upower (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: upower (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: linux (Ubuntu Bionic) Assignee: Marco Trevisan (Treviño) (3v1n0) => Kai-Heng Feng (kaihengfeng) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: upower (Ubuntu) Importance: Undecided => Medium ** Changed in: upower (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: upower (Ubuntu) Status: Confirmed => In Progress ** Changed in: upower (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: In Progress Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: In Progress Status in linux source package in Bionic: In Progress Status in upower source package in Bionic: In Progress Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.f
[Touch-packages] [Bug 1813227] Re: lvm2-pvscan services fails to start on S390X DPM
** Attachment added: "jourctl output of lvm2" https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1813227/+attachment/5232337/+files/lvm.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1813227 Title: lvm2-pvscan services fails to start on S390X DPM Status in lvm2 package in Ubuntu: New Bug description: The lvm2-pvscan service fails to start in the MAAS ephemeral environment. The service takes ~3 minutes to fail, blocking boot until failure. Release: 18.10(18.04 does not currently boot on S390X DPM) Kernel: 4.18.0-13-generic LVM: 2.02.176-4.1ubuntu3 root@node3:~# lvm pvscan --cache --activate ay 8:98 WARNING: Not using lvmetad because duplicate PVs were found. WARNING: Autoactivation reading from disk instead of lvmetad. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sde2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdba2 was already found on /dev/sdhd2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdfj2 was already found on /dev/sddi2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdg2 was already found on /dev/sddi2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdbc2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sdbf2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sddb2 was already found on /dev/sdhd2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sddr2 was already found on /dev/sdbq2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdbh2 was already found on /dev/sddi2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sddd2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sddg2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdfc2 was already found on /dev/sdhd2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdfs2 was already found on /dev/sdbq2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdp2 was already found on /dev/sdbq2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. Cannot activate LVs in VG zkvm4 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "zkvm4" now active zkvm4: autoactivation failed. Cannot activate LVs in VG zkvm1 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "zkvm1" now active zkvm1: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_473D86E3 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_473D86E3" now active Z_APPL_ROOT_lvm_473D86E3: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_BBD0E8D4 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_BBD0E8D4" now active Z_APPL_ROOT_lvm_BBD0E8D4: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_382F5B8E while PVs appear on duplicate
[Touch-packages] [Bug 1813227] [NEW] lvm2-pvscan services fails to start on S390X DPM
Public bug reported: The lvm2-pvscan service fails to start in the MAAS ephemeral environment. The service takes ~3 minutes to fail, blocking boot until failure. Release: 18.10(18.04 does not currently boot on S390X DPM) Kernel: 4.18.0-13-generic LVM: 2.02.176-4.1ubuntu3 root@node3:~# lvm pvscan --cache --activate ay 8:98 WARNING: Not using lvmetad because duplicate PVs were found. WARNING: Autoactivation reading from disk instead of lvmetad. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdb2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sde2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdba2 was already found on /dev/sdhd2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdfj2 was already found on /dev/sddi2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdg2 was already found on /dev/sddi2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sdbc2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sdbf2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sddb2 was already found on /dev/sdhd2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sddr2 was already found on /dev/sdbq2. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S on /dev/sdbh2 was already found on /dev/sddi2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l on /dev/sddd2 was already found on /dev/sdfe2. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs on /dev/sddg2 was already found on /dev/sdfh2. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF on /dev/sdfc2 was already found on /dev/sdhd2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdfs2 was already found on /dev/sdbq2. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 on /dev/sdp2 was already found on /dev/sdbq2. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV tIvQUe-wsuE-RWlZ-Wmdo-uzws-qL5H-Y9zW5l prefers device /dev/sdfe2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV 3zsO6H-QCQq-eyJZ-8aLc-TGU1-q91J-LFWsKs prefers device /dev/sdfh2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV VEyfqe-Vln5-zMp5-wCeK-hkQN-u8Wp-LkPTMF prefers device /dev/sdhd2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV H7Ucbo-TJSw-tS4y-AwKT-xdql-NiMp-YvZC1S prefers device /dev/sddi2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. WARNING: PV 6ZwSAD-cFkP-Qjeg-WIDt-g3Hc-m8Tt-i3ex81 prefers device /dev/sdbq2 because device was seen first. Cannot activate LVs in VG zkvm4 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "zkvm4" now active zkvm4: autoactivation failed. Cannot activate LVs in VG zkvm1 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "zkvm1" now active zkvm1: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_473D86E3 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_473D86E3" now active Z_APPL_ROOT_lvm_473D86E3: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_BBD0E8D4 while PVs appear on duplicate devices. 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_BBD0E8D4" now active Z_APPL_ROOT_lvm_BBD0E8D4: autoactivation failed. Cannot activate LVs in VG Z_APPL_ROOT_lvm_382F5B8E while PVs appear on duplicate devices. 0 logical volume(s) in volume group "Z_APPL_ROOT_lvm_382F5B8E" now active Z_APPL_ROOT_lvm_382F5B8E: autoactivation failed. root@node3:~# echo $? 5 ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1813227/+attachment/5232336/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1813227
[Touch-packages] [Bug 1214882] Re: cannot move "save as" window
The issue described there was in the fileselector widget from gtk, not in the filemanager, it also seems resolved in newer versions with the new popover widget used for entering the name ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1214882 Title: cannot move "save as" window Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: file -> save as -> (from evince, libre office, firefox, etc) new folder -> here i must enter the name of the folder, I digit the first words, but I don't remember a keyword that I need for naming the folder, I move the "save as" windows to find the keyword in the file, but the new folder that I'm creating disappear. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Wed Aug 21 14:34:31 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+65+24'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.window-state' b'sidebar-width' b'339' InstallationDate: Installed on 2013-07-10 (41 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1214882/+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 1225201] Re: Nautilus memory leak when thumbnailing jpeg2000 images
The issue seems rather in the pixbuf loader/jpg library. Do you still see the problem in newer Ubuntu versions? If so could you add a file example to the bug? ** Package changed: nautilus (Ubuntu) => gdk-pixbuf (Ubuntu) ** Changed in: gdk-pixbuf (Ubuntu) Importance: Undecided => High ** Changed in: gdk-pixbuf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1225201 Title: Nautilus memory leak when thumbnailing jpeg2000 images Status in gdk-pixbuf package in Ubuntu: Incomplete Bug description: Nautilus starts with under 300 MB and after thumbnailing some jp2 files (JPEG 2000) memory ends up above 900 MB. Closing all nautilus windows does not release the memory. Memory is only freed when doing nautilus -q. The more files is thumbnails the more memory is uses. Steps to reproduce: Drop a few jp2 files in a folder (I tested with lossless jpeg2000 files about 3000 by 3000) Quit nautilus (nautilus -q) Start nautilus again and open the folder containing jp2 files. Watch memory go up as nautilus is thumbnailing each file. Close nautilus (ALT-F4 or clicking in the red cross), memory is never released. Quit nautilus (nautilus -q) and memory is freed. Valgrind is very helpful, apparently libpixbufloader-jasper.so is used to read jp2 files. ==3829== 325,112,688 bytes in 11 blocks are possibly lost in loss record 12,461 of 12,461 ==3829==at 0x4C2CD7B: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==3829==by 0x72AC150: gdk_pixbuf_new (in /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2800.0) ==3829==by 0x288C42CE: ??? (in /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jasper.so) ==3829==by 0x72B2CA9: gdk_pixbuf_loader_close (in /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2800.0) ==3829==by 0x5471919: ??? (in /usr/lib/libgnome-desktop-3.so.4.0.0) ==3829==by 0x5471E51: gnome_desktop_thumbnail_factory_generate_thumbnail (in /usr/lib/libgnome-desktop-3.so.4.0.0) ==3829==by 0x4D8B2A: ??? (in /usr/bin/nautilus) ==3829==by 0x8A70F8D: start_thread (pthread_create.c:311) ==3829==by 0x8D7FE1C: clone (clone.S:113) ==3829== ==3829== LEAK SUMMARY: ==3829==definitely lost: 12,603 bytes in 42 blocks ==3829==indirectly lost: 34,224 bytes in 1,064 blocks ==3829== possibly lost: 328,125,169 bytes in 16,209 blocks ==3829==still reachable: 226,694,419 bytes in 14,183 blocks ==3829== suppressed: 0 bytes in 0 blocks ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Fri Sep 13 18:15:06 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'979x653+131+63'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'194' InstallationDate: Installed on 2013-03-27 (170 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-25 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1225201/+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 1225201] [NEW] Nautilus memory leak when thumbnailing jpeg2000 images
You have been subscribed to a public bug: Nautilus starts with under 300 MB and after thumbnailing some jp2 files (JPEG 2000) memory ends up above 900 MB. Closing all nautilus windows does not release the memory. Memory is only freed when doing nautilus -q. The more files is thumbnails the more memory is uses. Steps to reproduce: Drop a few jp2 files in a folder (I tested with lossless jpeg2000 files about 3000 by 3000) Quit nautilus (nautilus -q) Start nautilus again and open the folder containing jp2 files. Watch memory go up as nautilus is thumbnailing each file. Close nautilus (ALT-F4 or clicking in the red cross), memory is never released. Quit nautilus (nautilus -q) and memory is freed. Valgrind is very helpful, apparently libpixbufloader-jasper.so is used to read jp2 files. ==3829== 325,112,688 bytes in 11 blocks are possibly lost in loss record 12,461 of 12,461 ==3829==at 0x4C2CD7B: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==3829==by 0x72AC150: gdk_pixbuf_new (in /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2800.0) ==3829==by 0x288C42CE: ??? (in /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-jasper.so) ==3829==by 0x72B2CA9: gdk_pixbuf_loader_close (in /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0.2800.0) ==3829==by 0x5471919: ??? (in /usr/lib/libgnome-desktop-3.so.4.0.0) ==3829==by 0x5471E51: gnome_desktop_thumbnail_factory_generate_thumbnail (in /usr/lib/libgnome-desktop-3.so.4.0.0) ==3829==by 0x4D8B2A: ??? (in /usr/bin/nautilus) ==3829==by 0x8A70F8D: start_thread (pthread_create.c:311) ==3829==by 0x8D7FE1C: clone (clone.S:113) ==3829== ==3829== LEAK SUMMARY: ==3829==definitely lost: 12,603 bytes in 42 blocks ==3829==indirectly lost: 34,224 bytes in 1,064 blocks ==3829== possibly lost: 328,125,169 bytes in 16,209 blocks ==3829==still reachable: 226,694,419 bytes in 14,183 blocks ==3829== suppressed: 0 bytes in 0 blocks ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Fri Sep 13 18:15:06 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'979x653+131+63'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'194' InstallationDate: Installed on 2013-03-27 (170 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-25 (140 days ago) ** Affects: gdk-pixbuf (Ubuntu) Importance: High Status: Incomplete ** Tags: amd64 apport-bug raring -- Nautilus memory leak when thumbnailing jpeg2000 images https://bugs.launchpad.net/bugs/1225201 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
Bryan - is there any chance we could get that image? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Fix Released Status in debirf package in Ubuntu: Confirmed Status in busybox source package in Bionic: In Progress Status in debirf source package in Bionic: Confirmed Status in busybox source package in Cosmic: Fix Released Status in debirf source package in Cosmic: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+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 1214882] [NEW] cannot move "save as" window
You have been subscribed to a public bug: file -> save as -> (from evince, libre office, firefox, etc) new folder -> here i must enter the name of the folder, I digit the first words, but I don't remember a keyword that I need for naming the folder, I move the "save as" windows to find the keyword in the file, but the new folder that I'm creating disappear. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Wed Aug 21 14:34:31 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+65+24'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.window-state' b'sidebar-width' b'339' InstallationDate: Installed on 2013-07-10 (41 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: Fix Released ** Tags: amd64 apport-bug raring -- cannot move "save as" window https://bugs.launchpad.net/bugs/1214882 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => In Progress ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in gnome-control-center source package in Bionic: New Status in gnome-shell source package in Bionic: New Status in linux source package in Bionic: New Status in upower source package in Bionic: New Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK 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/gnome-control-center/+bug/1745032/+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 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30
This bug was fixed in the package gsettings-desktop-schemas - 3.31.0.2-2ubuntu3 --- gsettings-desktop-schemas (3.31.0.2-2ubuntu3) disco; urgency=medium * Add Restore-peripherals-display-keys.patch: - Add 2 dummy keys for renamed gsettings keys to give us more time to fix their users (LP: #1812143) * Revert "Add Breaks: mutter << 3.31.4" -- Jeremy Bicha Thu, 24 Jan 2019 12:43:44 -0500 ** Changed in: gsettings-desktop-schemas (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1812143 Title: gsettings-desktop-schemas 3.31 breaks mutter 3.30 Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Status in ukwm package in Ubuntu: Confirmed Bug description: We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to gsettings-desktop-schemas. Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in gdm/gnome-shell being unable to start. Also, ukwm is a fork of mutter so the Kylin devs need to backport the relevant commits from mutter. The problematic gsettings commit was: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c I think the mutter commits can be found at https://gitlab.gnome.org/GNOME/mutter/merge_requests/133 We could easily add a dummy key with the old name but I'm thinking the way forward is just to package the newer mutter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+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 1813208] Re: Paired bluetooth mice irregularities after resume from suspend
** Package changed: bluez (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1813208 Title: Paired bluetooth mice irregularities after resume from suspend Status in Ubuntu: New Bug description: System model: Dell XPS 9370 Killer Wireless 1435 Ubuntu Dell OEM - 18.04.1 LTS If a Bluetooth device is paired while system is in suspend, upon resuming the system's Bluetooth functionality will intermittently be lost whereas the expectation is the functionality would resume as before. Bluetooth functionality can be restored by restarting system, entering BIOS, and then exiting BIOS even if nothing is changed. Standard reboots without entering BIOS will not restore Bluetooth functionality. Note: Sometimes Wireless is missing as well, but that can be restored through normal reboots without going into BIOS. Tested on XPS 9370 with Ubuntu 18.04 Dell OEM clean install. Issue was observed to occur with both of the following devices: HP x4000b Bluetooth mouse Logitech G603 Bluetooth mouse Issue does not seem to occur if system is only allowed to suspend for a short time, issue only occurred if system was left in suspend overnight. Issue observed to occur both on battery and AC power, power source did not seem to affect the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1813208/+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 1813208] [NEW] Paired bluetooth mice irregularities after resume from suspend
Public bug reported: System model: Dell XPS 9370 Killer Wireless 1435 Ubuntu Dell OEM - 18.04.1 LTS If a Bluetooth device is paired while system is in suspend, upon resuming the system's Bluetooth functionality will intermittently be lost whereas the expectation is the functionality would resume as before. Bluetooth functionality can be restored by restarting system, entering BIOS, and then exiting BIOS even if nothing is changed. Standard reboots without entering BIOS will not restore Bluetooth functionality. Note: Sometimes Wireless is missing as well, but that can be restored through normal reboots without going into BIOS. Tested on XPS 9370 with Ubuntu 18.04 Dell OEM clean install. Issue was observed to occur with both of the following devices: HP x4000b Bluetooth mouse Logitech G603 Bluetooth mouse Issue does not seem to occur if system is only allowed to suspend for a short time, issue only occurred if system was left in suspend overnight. Issue observed to occur both on battery and AC power, power source did not seem to affect the issue. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1813208 Title: Paired bluetooth mice irregularities after resume from suspend Status in Ubuntu: New Bug description: System model: Dell XPS 9370 Killer Wireless 1435 Ubuntu Dell OEM - 18.04.1 LTS If a Bluetooth device is paired while system is in suspend, upon resuming the system's Bluetooth functionality will intermittently be lost whereas the expectation is the functionality would resume as before. Bluetooth functionality can be restored by restarting system, entering BIOS, and then exiting BIOS even if nothing is changed. Standard reboots without entering BIOS will not restore Bluetooth functionality. Note: Sometimes Wireless is missing as well, but that can be restored through normal reboots without going into BIOS. Tested on XPS 9370 with Ubuntu 18.04 Dell OEM clean install. Issue was observed to occur with both of the following devices: HP x4000b Bluetooth mouse Logitech G603 Bluetooth mouse Issue does not seem to occur if system is only allowed to suspend for a short time, issue only occurred if system was left in suspend overnight. Issue observed to occur both on battery and AC power, power source did not seem to affect the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1813208/+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 1812446] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1812446/+attachment/5232312/+files/getfacl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1812446/+attachment/5232306/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1812446/+attachment/5232309/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] Re: Bluetooth mouse stops responding after 24-48 hours of connectivity
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-01-03 (20 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 004: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 Package: bluez 5.48-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=767c0b00-e72c-44a2-bac1-9527767a7bb4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. hciconfig: rfkill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Tags added: apport-collected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1812446/+attachment/5232310/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1812446/+attachment/5232307/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1812446/+attachment/5232313/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1812446/+attachment/5232304/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1812446/+attachment/5232311/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1812446/+attachment/5232308/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1812446] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1812446/+attachment/5232305/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812446 Title: Bluetooth mouse stops responding after 24-48 hours of connectivity Status in bluez package in Ubuntu: Incomplete Bug description: Tested on Dell XPS 9370, Ubuntu 18.04 Dell OEM ISO (for this model) -Bluetooth mouse (Tested with a HP x4000b BT Laser Mouse) stops responding after 1-2 days of being connected whereas the expectation is that the mouse would continue working normally -Bluetooth settings window will initially report Bluetooth is on when opened. -Switching away and back to the Bluetooth settings GUI will now show Bluetooth as disabled, and Settings GUI will lock up until system is restarted. o Settings window can be force closed and re-opened, but it will still be locked up on the Bluetooth tab -When moving the mouse or clicking any buttons in this state, the Bluetooth icon in the top right GNOME menu bar will briefly flash the Bluetooth icon but there is no actual mouse activity. -dmesg log shows an extremely large number of events “Bluetooth: hci0: last event is not cmd complete (0x0f)” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812446/+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 1183393] Re: devices bookmarks in the sidebar aren't at the bottom anymore
** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1183393 Title: devices bookmarks in the sidebar aren't at the bottom anymore Status in gtk+3.0 package in Ubuntu: New Bug description: the devices bookmarks in the sidebar are between the personal bookmarks and the places bookmarks but it should be at the bottom right before the networks bookmark. it's confusing and a drawback to Nautilus 3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1183393/+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 1183393] [NEW] devices bookmarks in the sidebar aren't at the bottom anymore
You have been subscribed to a public bug: the devices bookmarks in the sidebar are between the personal bookmarks and the places bookmarks but it should be at the bottom right before the networks bookmark. it's confusing and a drawback to Nautilus 3.4 ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: New -- devices bookmarks in the sidebar aren't at the bottom anymore https://bugs.launchpad.net/bugs/1183393 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello Łukasz, The problem persists. * installed sha256sum ubuntu-18.04.1-desktopmd64.iso (5748706937539418ee5707bd538c4f5eabae485d17aa49fb13ce2c9b70532433) * used update-manager to enable proposed-update * sudo apt-get update * sudo apt-get install initramfs-tools (initramfs-tools is now in version 0.130ubuntu3.7) * reboot * still showing WARNING:Failed to connect to lvmetad. Falling back to device scanning. Best regards Marc ** Tags added: verification-failed-bionic -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
I am still affected by this bug (Bionic server installation with the latest
updates - 24.01.2019)
Attached: unattended-upgrades.log
** Attachment added: "unattended-upgrades.log"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778219/+attachment/5232300/+files/unattended-upgrades.log
--
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/1778219
Title:
unattended-upgrades hangs on shutdown, leaves system in a broken state
Status in init-system-helpers package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
Confirmed
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in init-system-helpers source package in Xenial:
Confirmed
Status in snapd source package in Xenial:
Confirmed
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in init-system-helpers source package in Bionic:
Confirmed
Status in snapd source package in Bionic:
Confirmed
Status in unattended-upgrades source package in Bionic:
Fix Released
Status in unattended-upgrades source package in Cosmic:
Fix Released
Bug description:
[Impact]
* Unattended-upgrades hangs and gets killed when installing upgrades
that stat/stop services on shutdown, leaving the system in a broken
state
[Test Case]
* Install an updated bionic system:
$ lxc launch ubuntu:18.04 uu-shutdown-test
# apt update
...
* When testing the fixed version, install upgrade u-u at this point checking
that u-u.service is set up before and is wanted by shutdown.target:
# systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" [color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
* Configure u-u to run on shutdown and install -updates:
# echo 'Unattended-Upgrade::InstallOnShutdown "true";' >
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too
* Downgrade snapd:
# apt install snapd=2.32.5+18.04
* Dowload packages for u-u:
# unattended-upgrade --download-only
* Reboot using logind to let inhibitors hold up shutdown:
# dbus-send --system --print-reply --dest=org.freedesktop.login1
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false
* With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
`-{unattended-upgr}
* With fixed u-u observe snapd update taking place and system
rebooting after a few seconds with all updates installed
* Since this fix is partially reverting the fix for LP: #1654600
please test LP: #1654600 as well to avoid regressions.
[Regression Potential]
* As part of the fix manual changes were made to postinst to properly
transition from coupling u-u.service with multi-user.target to coupling it with
shutdown.target again which can make u-u started during normal boot when there
is a bug in the implementation.
on-testing the SRU.
* Due to relationship changes between u-u.service, other services and
targets u-u may fail to run on shutdown in case of an unexpected regression.
* There is a rarely occurring new crash caused by the (second) fix tracked in
LP: #1806487.
[Original Bug Text]
When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
package installation on various packages hangs until the systemd
ShutdownTimeout (30min) is expired and systemd kills all processes and
powers off/reboots the system.
This leaves packages in an unconfigured, broken state. At least
sometimes this cannot be fixed with a "dpkg --configure -a", but
instead requires the user to manually reinstall the package that
caused the hang.
This appears to be a deadlock, because the hanging commands are always
"systemctl stop ..." or "systemctl restart ...", etc.. If I understand
this correctly, those systemctl commands block because systemd tries
to shutdown the system and tries
[Touch-packages] [Bug 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30
** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1812143 Title: gsettings-desktop-schemas 3.31 breaks mutter 3.30 Status in gsettings-desktop-schemas package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in ukwm package in Ubuntu: Confirmed Bug description: We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to gsettings-desktop-schemas. Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in gdm/gnome-shell being unable to start. Also, ukwm is a fork of mutter so the Kylin devs need to backport the relevant commits from mutter. The problematic gsettings commit was: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c I think the mutter commits can be found at https://gitlab.gnome.org/GNOME/mutter/merge_requests/133 We could easily add a dummy key with the old name but I'm thinking the way forward is just to package the newer mutter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+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 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
No, I am not on Armbian. I have: x86_64 4.15.0-43-generic Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic systemd: Installed: 237-3ubuntu10.11 Candidate: 237-3ubuntu10.11 And errors started after november 2018 updates: ● systemd-tmpfiles-setup-dev.service loaded failed failed Create Static Device Nodes in /dev ● systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files and Directories I never downgraded my Ubuntu system, how I can do this? -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
Hello Cristian, or anyone else affected, Accepted apport into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.10-0ubuntu13.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apport (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: Fix Released Status in apport source package in Cosmic: Fix Committed Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+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 1798562] Re: After a side by side installation, resized filesystem is corrupted
This has been fixed in the e2fsprogs version in Disco. [ 8:40AM 10668 ] [ bdmurray@impulse:/tmp/e2fsprogs-1.44.5 ] $ grep -B1 1798562 doc/RelNotes/v1.44.5.txt Fix a bug where resize2fs was failing to update the extent tree checksums in an corner case. (Addresses Launchpad Bug: #1798562) ** Changed in: e2fsprogs (Ubuntu) Status: Confirmed => Fix Released -- 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/1798562 Title: After a side by side installation, resized filesystem is corrupted Status in e2fsprogs package in Ubuntu: Fix Released Bug description: Test Case 1: With e2fsprogs 1.44.4-2: Download this file system image: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+attachment/5203159/+files/vda1b.qcow2.bz Run the following commands: bunzip2 vda1b.qcow2.bz qemu-img convert vda1b.qcow2 vda1b.raw e2fsck -f vda1b.raw resize2fs vda1b.raw 6200M e2fsck -f vda1b.raw e2fsck 1.44.4 (18-Aug-2018) Pass 1: Checking inodes, blocks, and sizes Inode 45746 extent block passes checks, but checksum does not match extent (logical block 1272, physical block 466167, len 776) Fix? Test Case 2 (Use case of the installer): 1. Perform a first installation of Ubuntu 2. Reboot into the freshly installed system and verify everything works as expected 3. Do a second installation and select "Install alonogside". Keep the size proposed by the installer and proceed to the end of installation 4. Reboot 5. On boot, in the list of installed systems, select the first system installed on the machine 6. Verify that it boots, you can login and it works as expected Actual Result The FS is corrupted and depending on the corruption it goes to initramfs, boots but cannot login, ... Attached is the journal of the system installed on the corrupted partition. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 10:53:57 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- InstallationDate: Installed on 2018-10-18 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1798562/+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 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
Hello Alberto, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [Impact] initramfs-tools would always include all "framebuffer" drivers/firmware inside initramfs, which was making it ever more huge. In some systems with low memory, that would even prevent systems to boot. kdump, for example, had an impact. [Test case] Different systems on different arches were tested. When cryptsetup (or cryptsetup-initramfs) was installed, framebuffer drivers were included in the ramdisk. When not installed, the initramfs was smaller. Systems booted on both cases. Systems with encrypted disks were tested as well. [Regression Potential] Systems may not boot because of missing drivers. Users may have a different experience during boot because of missing "framebuffer" drivers. == initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello Marc, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-failed-bionic -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1750051] Re: cron doesn't support MAILFROM
** Changed in: cron (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1750051 Title: cron doesn't support MAILFROM Status in cron package in Ubuntu: Triaged Status in cron package in Debian: New Bug description: Ubuntu's cron version doesn't support setting MAILFROM to set the "From:" header of cron generated emails. This feature would be nice to have and bring parity with RHEL/CentOS which has it since RHEL 6: $ cat /etc/redhat-release CentOS release 6.6 (Final) $ man 5 crontab | grep -1 FROM doesn´t do aliasing, and UUCP usually doesn´t read its mail. If MAIL- FROM is defined (and non-empty), it will be used as the envelope sender address, otherwise, ‘‘root’’ will be used. $ apt-cache policy cron cron: Installed: 3.0pl1-128ubuntu2 Candidate: 3.0pl1-128ubuntu2 Version table: *** 3.0pl1-128ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 16 15:52:54 2018 InstallationDate: Installed on 2016-12-06 (436 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161206) SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1750051/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Changed in: initramfs-tools (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Confirmed => In Progress -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: In Progress Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1813090] Re: bash completions in /usr/share/bash-completion generate unbound variable errors
** Package changed: ubuntu => bash (Ubuntu) -- 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/1813090 Title: bash completions in /usr/share/bash-completion generate unbound variable errors Status in bash package in Ubuntu: New Bug description: After upgrading from Ubuntu 18.04 LTS to 18.04.1 LTS, I get errors whenever I attempt to tab-complete anything from an interactive bash prompt. Tab-completing nothing gives me: -bash: _xspecs[$cmd]: unbound variable Tab-completing an existing filename gives me: -bash: !ref: unbound variable I've partially narrowed down the cause to me putting `set -o nounset` in my `.bashrc` file, and something in `/usr/share/bash-completion` is triggering these unbound variable errors. (That is, the errors go away if I remove `set -o nounset` or if I make `/usr/share/bash- completion/bash_completion` exit immediately.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1813090/+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 1813090] [NEW] bash completions in /usr/share/bash-completion generate unbound variable errors
You have been subscribed to a public bug: After upgrading from Ubuntu 18.04 LTS to 18.04.1 LTS, I get errors whenever I attempt to tab-complete anything from an interactive bash prompt. Tab-completing nothing gives me: -bash: _xspecs[$cmd]: unbound variable Tab-completing an existing filename gives me: -bash: !ref: unbound variable I've partially narrowed down the cause to me putting `set -o nounset` in my `.bashrc` file, and something in `/usr/share/bash-completion` is triggering these unbound variable errors. (That is, the errors go away if I remove `set -o nounset` or if I make `/usr/share/bash- completion/bash_completion` exit immediately.) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- bash completions in /usr/share/bash-completion generate unbound variable errors https://bugs.launchpad.net/bugs/1813090 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715931] Re: Update to exiv2 version 0.26
** Tags removed: version-blocked -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.26 Status in exiv2 package in Ubuntu: Triaged Status in exiv2 package in Debian: Fix Released Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+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 1812353] Re: content injection in http method (CVE-2019-3462)
@Christoph: You can put HTTPS URLs into your "sources.list", many mirrors support it. The package "apt-transport-https" is not required, that is outdated information. APT supports HTTPS out of the box for a while now, it is just not the default. Packets will still be validated using the Debian release OpenPGP key, regardless of which method of transport you use. > an attacker could have used this long ago to basically do everything That is the case for any kind of security vulnerability. But the risk is much higher after the bug is published. > But is there a chance to e.g. get full audits of apt done by security experts? Bugs happen, audits don't find all bugs. APT has been around for a while and as a core infrastructure was reviewed by many people. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812353 Title: content injection in http method (CVE-2019-3462) Status in apt package in Ubuntu: Fix Released Status in apt source package in Precise: Fix Released Status in apt source package in Trusty: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: Fix Released Bug description: apt, starting with version 0.8.15, decodes target URLs of redirects, but does not check them for newlines, allowing MiTM attackers (or repository mirrors) to inject arbitrary headers into the result returned to the main process. If the URL embeds hashes of the supposed file, it can thus be used to disable any validation of the downloaded file, as the fake hashes will be prepended in front of the right hashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+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 1813160] [NEW] display problem
Public bug reported: display is going black for fraction of second. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 24 18:47:01 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-127-generic, x86_64: installed oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-94-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-127-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-94-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0841] InstallationDate: Installed on 2018-08-26 (151 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Vostro 3478 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=a241a9ad-c097-481d-b704-f28b73bb8feb ro acpi_rev_override quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 08R7RH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd05/22/2018:svnDellInc.:pnVostro3478:pvr:rvnDellInc.:rn08R7RH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Vostro 3478 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Jan 24 16:25:51 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1805 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1813160 Title: display problem Status in xorg package in Ubuntu: New Bug description: display is going black for fraction of second. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 24 18:47:01 2019 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-127-generic, x86_64: installed oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-94-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-127-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 1.2, 4.4.0-94-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0841] Installati
[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
** Tags added: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1754075] Re: apt-setup uses apt-key but probably should not anymore
I too used the workaround: d-i preseed/late_command string \ in-target wget -q -O /etc/apt/trusted.gpg.d/repo_key.asc http://our.repo/repo_key.asc ; \ We mirror the repositories we offer to our clients, so they can keep doing their stuff in case the intarwebz is inaccessible. None of those repo keys can be added the normal preseed way: d-i apt-setup/local0/key string http://our.repo/repo_key.asc I can add the repo this way, just not the key. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1782263] Re: NetworkManager authentication problems caused by polkit
This is likely a bug in network-manager, not policykit...adding network- manager to this. Also, I don't see any activity on the upstream bug that would suggest it's been addressed in any way. ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1782263 Title: NetworkManager authentication problems caused by polkit Status in network-manager package in Ubuntu: New Status in policykit package in Ubuntu: Confirmed Bug description: The following message, or variations upon it, appears dozens of times, one immediately after the other, in my system log. [1531853719.4893] error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: Authorization check failed: Failed to open file “/proc/10006/status”: No such file or directory The problem began when I did the following package update. apt-cache policy policykit-1 policykit-1: Installed: 0.105-20 Candidate: 0.105-20ubuntu0.18.04.1 Version table: 0.105-20ubuntu0.18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.105-20 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status When (via the TimeShift backup program) I restored my system to a state before the package was installed, the problem stopped. When I did have the problem, some networks would have trouble connecting. I asked about the issue on Mint's IRC channel, and no solution - save reinstalling - emerged; but by that point I had not traced the problem to policykit. Mint 19 x64 Cinnamon. I report this problem here because it seems to me - I might be wrong - an Ubuntu rather than Mint problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1782263/+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 1812955] Re: g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding
** Changed in: gobject-introspection (Ubuntu) Status: Invalid => Confirmed ** Description changed: + https://gitlab.gnome.org/GNOME/gobject-introspection/issues/260 + + --- + g-ir-scanner is crashing with SIGSEGV instead of succeeding. So I can't build gnome-shell any more. Actually it looks like some kind of temporary sub-command "Shell-0.1" of g-ir-scanner that's crashing: /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include --no-libtool --namespace=Shell --nsversion=0.1 --warn-all --output src/Shell-0.1.gir --quiet -I/home/dan/git/gnome-shell/src -I/home/dan/git/gnome-shell/build/src -I./. -I../. -I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray --filelist=/home/dan/git/gnome-shell/build/src/src@@gnome-shell@sha/Shell_0.1_gir_filelist --include=Clutter-4 --include=ClutterX11-4 --include=Meta-4 --include=Gcr-3 --include=PolkitAgent-1.0 --include=NM-1.0 --include-uninstalled=subprojects/gvc/Gvc-1.0.gir --include-uninstalled=src/ShellMenu-0.1.gir --include-uninstalled=src/st/St-1.0.gir --cflags-begin -I./. -I../. -I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -include /usr/include/mozjs-60/js/RequiredDefines.h -I/usr/include/gobject-introspection-1.0 -I/usr/include/mozjs-60 -I/usr/include/gjs-1.0 -I/home/dan/tmp.gs/include/mutter-4/clutter -I/home/dan/tmp.gs/include/mutter-4/cogl -I/usr/include/json-glib-1.0 -I/usr/include/libwacom-1.0 -I/usr/include/startup-notification-1.0 -I/usr/include/polkit-1 -I/usr/include/gcr-3 -I/usr/include/gck-1 -I/usr/include/p11-kit-1 -I/usr/include/libnm -I/usr/include/libsecret-1 -I/usr/include/gstreamer-1.0 -D_REENTRANT -I/home/dan/tmp.gs/include/mutter-4 -I/home/dan/tmp.gs/include/gsettings-desktop-schemas -I/usr/include/gnome-desktop-3.0 -I/usr/include/gnome-settings-daemon-3.0 -I/usr/include/gudev-1.0 --cflags-end -L/home/dan/git/gnome-shell/build/src --add-include-path=/usr/share/gir-1.0 --add-include-path=/home/dan/tmp.gs/lib/x86_64-linux-gnu/mutter-4 --add-include-path=/home/dan/git/gnome-shell/build/subprojects/gvc --add-include-path=/home/dan/git/gnome-shell/build/src --add-include-path=/home/dan/git/gnome-shell/build/src/st -L/home/dan/git/gnome-shell/build/src -L/home/dan/git/gnome-shell/build/src/st -L/lib/x86_64-linux-gnu --library gnome-shell --extra-library=gio-2.0 --extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=xml2 --extra-library=gtk-3 --extra-library=gdk-3 --extra-library=pangocairo-1.0 --extra-library=pango-1.0 --extra-library=atk-1.0 --extra-library=cairo-gobject --extra-library=cairo --extra-library=gdk_pixbuf-2.0 --extra-library=atk-bridge-2.0 --extra-library=gjs -L/home/dan/tmp.gs//lib/x86_64-linux-gnu/mutter-4 --extra-library=mutter-clutter-4 --extra-library=m --extra-library=json-glib-1.0 --extra-library=pangoft2-1.0 --extra-library=fontconfig --extra-library=freetype --extra-library=wayland-egl --extra-library=wayland-client --extra-library=Xtst --extra-library=Xi --extra-library=udev --extra-library=input --extra-library=xkbcommon --extra-library=wacom --extra-library=mutter-cogl-4 --extra-library=gmodule-2.0 -pthread --extra-library=wayland-server --extra-library=EGL --extra-library=X11 --extra-library=Xext --extra-library=Xdamage --extra-library=Xfixes --extra-library=Xcomposite --extra-library=Xrandr --extra-library=GL --extra-library=GLESv2 --extra-library=mutter-cogl-pango-4 --extra-library=startup-notification-1 --extra-library=girepository-1.0 --extra-library=polkit-agent-1 --extra-library=polkit-gobject-1 --extra-library=gcr-base-3 --extra-library=gck-1 --extra-library=p11-kit --extra-library=systemd --extra-library=nm --extra-library=secret-1 --extra-library=gstreamer-1.0 --extra-library=gstbase-1.0 -L/home/dan/tmp.gs//lib/x86_64-linux-gnu --extra-library=mutter-4 --extra-library=gnome-desktop-3 --extra-library=canberra --extra-library=gudev-1.0 --extra-library=pipewire-0.2 --extra-library=Xinerama --extra-library=ICE --extra-library=Xcursor --extra-library=xkbfile --extra-library=xkbcommon-x11 --extra-library=Xrender --extra-library=X11-xcb --extra-library=xcb --extra-library=xcb-randr --extra-library=xcb-res --extra-library=SM --extra-library=drm --extra-library=gbm Command '['/home/dan/git/gnome-shell/build/tmp-introspectu443gr_x/Shell-0.
[Touch-packages] [Bug 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
** Description changed: + [Impact] + initramfs-tools would always include all "framebuffer" drivers/firmware inside initramfs, which was making it ever more huge. In some systems with low memory, that would even prevent systems to boot. kdump, for example, had an impact. + + [Test case] + Different systems on different arches were tested. When cryptsetup (or cryptsetup-initramfs) was installed, framebuffer drivers were included in the ramdisk. When not installed, the initramfs was smaller. Systems booted on both cases. Systems with encrypted disks were tested as well. + + [Regression Potential] + Systems may not boot because of missing drivers. Users may have a different experience during boot because of missing "framebuffer" drivers. + + + == + initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: In Progress Bug description: [Impact] initramfs-tools would always include all "framebuffer" drivers/firmware inside initramfs, which was making it ever more huge. In some systems with low memory, that would even prevent systems to boot. kdump, for example, had an impact. [Test case] Different systems on different arches were tested. When cryptsetup (or cryptsetup-initramfs) was installed, framebuffer drivers were included in the ramdisk. When not installed, the initramfs was smaller. Systems booted on both cases. Systems with encrypted disks were tested as well. [Regression Potential] Systems may not boot because of missing drivers. Users may have a different experience during boot because of missing "framebuffer" drivers. == initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1561643/+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 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbo
it's a bug in the mesa build which is using meson now, it doesn't link with libwayland_drm, not sure why ** Package changed: intel-vaapi-driver (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in mesa package in Ubuntu: New Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1813131/+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 1813131] [NEW] i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined sym
You have been subscribed to a public bug: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] https://bugs.launchpad.net/bugs/1813131 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
Can we get this verified for cosmic as well? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Status in alsa-lib source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1812955] Re: g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding
Finally bisected. It seems like a regression in upstream mutter master this week: 1bbb5c8107ab77435f97c1b037a89a76121f6e3c is the first bad commit commit 1bbb5c8107ab77435f97c1b037a89a76121f6e3c Author: Jonas Ådahl Date: Sun Jan 20 17:41:53 2019 +0100 meta: Only declare types when generating gir files Some types were declared in the public headers so that g-ir-scanner could resolve the types. This caused warnings when using -Wredundant-decls, so only redeclare them for the gir scanner. :04 04 4ae3c1d894a568cf0903696034af467698403bc8 d32098d7d43859454dcc33c99f56e63e05a0fb03 M src So not an Ubuntu bug. ** Changed in: gobject-introspection (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1812955 Title: g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding Status in gobject-introspection package in Ubuntu: Invalid Bug description: g-ir-scanner is crashing with SIGSEGV instead of succeeding. So I can't build gnome-shell any more. Actually it looks like some kind of temporary sub-command "Shell-0.1" of g-ir-scanner that's crashing: /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include --no-libtool --namespace=Shell --nsversion=0.1 --warn-all --output src/Shell-0.1.gir --quiet -I/home/dan/git/gnome-shell/src -I/home/dan/git/gnome-shell/build/src -I./. -I../. -I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray --filelist=/home/dan/git/gnome-shell/build/src/src@@gnome-shell@sha/Shell_0.1_gir_filelist --include=Clutter-4 --include=ClutterX11-4 --include=Meta-4 --include=Gcr-3 --include=PolkitAgent-1.0 --include=NM-1.0 --include-uninstalled=subprojects/gvc/Gvc-1.0.gir --include-uninstalled=src/ShellMenu-0.1.gir --include-uninstalled=src/st/St-1.0.gir --cflags-begin -I./. -I../. -I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -include /usr/include/mozjs-60/js/RequiredDefines.h -I/usr/include/gobject-introspection-1.0 -I/usr/include/mozjs-60 -I/usr/include/gjs-1.0 -I/home/dan/tmp.gs/include/mutter-4/clutter -I/home/dan/tmp.gs/include/mutter-4/cogl -I/usr/include/json-glib-1.0 -I/usr/include/libwacom-1.0 -I/usr/include/startup-notification-1.0 -I/usr/include/polkit-1 -I/usr/include/gcr-3 -I/usr/include/gck-1 -I/usr/include/p11-kit-1 -I/usr/include/libnm -I/usr/include/libsecret-1 -I/usr/include/gstreamer-1.0 -D_REENTRANT -I/home/dan/tmp.gs/include/mutter-4 -I/home/dan/tmp.gs/include/gsettings-desktop-schemas -I/usr/include/gnome-desktop-3.0 -I/usr/include/gnome-settings-daemon-3.0 -I/usr/include/gudev-1.0 --cflags-end -L/home/dan/git/gnome-shell/build/src --add-include-path=/usr/share/gir-1.0 --add-include-path=/home/dan/tmp.gs/lib/x86_64-linux-gnu/mutter-4 --add-include-path=/home/dan/git/gnome-shell/build/subprojects/gvc --add-include-path=/home/dan/git/gnome-shell/build/src --add-include-path=/home/dan/git/gnome-shell/build/src/st -L/home/dan/git/gnome-shell/build/src -L/home/dan/git/gnome-shell/build/src/st -L/lib/x86_64-linux-gnu --library gnome-shell --extra-library=gio-2.0 --extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=xml2 --extra-library=gtk-3 --extra-library=gdk-3 --extra-library=pangocairo-1.0 --extra-library=pango-1.0 --extra-library=atk-1.0 --extra-library=cairo-gobject --extra-library=cairo --extra-library=gdk_pixbuf-2.0 --extra-library=atk-bridge-2.0 --extra-library=gjs -L/home/dan/tmp.gs//lib/x86_64-linux-gnu/mutter-4 --extra-library=mutter-clutter-4 --extra-library=m --extra-library=json-glib-1.0 --extra-library=pangoft2-1.0 --extra-library=fontconfig --extra-library=freetype --extra-library=wayland-egl --extra-library=wayland-client --extra-library=Xtst --extra-library=Xi --extra-library=udev --extra-library=input --extra-library=xkbcommon --extra-library=wacom --extra-library=mutter-cogl-4 --extra-library=gmodule-2.0 -pthread --extra-library=wayland-server --extra-library=EGL --extra-library=X11 --extra-library=Xext --extra-library=Xdamage --extra-library=Xfixes --extra-library=Xcomposite --extra-library=Xrandr --extra-library=GL --extra-library=GLESv2 --extra-library=mutter-cogl-pango-4 --e
[Touch-packages] [Bug 1812955] Re: g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding
And a fresh retrace today: Core was generated by `/home/dan/git/gnome-shell/build/tmp-introspectcxwjenqm/Shell-0.1 --introspect-d'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f0586db711f in type_check_is_value_type_U ( type=type@entry=1694390208) at ../../../../gobject/gtype.c:4156 4156../../../../gobject/gtype.c: No such file or directory. [Current thread is 1 (Thread 0x7f057dcc21c0 (LWP 18932))] (gdb) bt #0 0x7f0586db711f in type_check_is_value_type_U (type=type@entry=) at ../../../../gobject/gtype.c:4156 #1 0x7f0586db711f in g_type_check_is_value_type (type=type@entry=) at ../../../../gobject/gtype.c:4192 #2 0x7f0586da8b10 in g_signal_newv (signal_name=signal_name@entry=0x7f0586fd9bae "startup-sequence-changed", itype=itype@entry=0x559364fe55d0 [ShellWindowTracker], signal_flags=G_SIGNAL_RUN_LAST, class_closure=0x0, accumulator=0x0, accu_data=0x0, c_marshaller=0x0, return_type=0x4 [void], n_params=1, param_types=0x559364fdf3e0) at ../../../../gobject/gsignal.c:1672 #3 0x7f0586da9964 in g_signal_new_valist (signal_name=signal_name@entry=0x7f0586fd9bae "startup-sequence-changed", itype=itype@entry=0x559364fe55d0 [ShellWindowTracker], signal_flags=, class_closure=, accumulator=, accu_data=, c_marshaller=0x0, return_type=0x4 [void], n_params=1, args=0x7ffc1ddd2880) at ../../../../gobject/gsignal.c:1902 #4 0x7f0586da9a4e in g_signal_new (signal_name=0x7f0586fd9bae "startup-sequence-changed", itype=0x559364fe55d0 [ShellWindowTracker], signal_flags=, class_offset=, accumulator=, accu_data=, c_marshaller=0x0, return_type=0x4 [void], n_params=1) at ../../../../gobject/gsignal.c:1437 #5 0x7f0586fcb20e in shell_window_tracker_class_init (klass=0x559364fe5730) at ../src/shell-window-tracker.c:112 #6 0x7f0586fcafca in shell_window_tracker_class_intern_init (klass=0x559364fe5730) at ../src/shell-window-tracker.c:51 #7 0x7f0586db374b in type_class_init_Wm (pclass=0x50 [g_type: GObject], node=0x559364fe55d0) at ../../../../gobject/gtype.c:2232 #8 0x7f0586db374b in g_type_class_ref (type=) at ../../../../gobject/gtype.c:2947 #9 0x559364ad20e5 in dump_properties (type=0x559364fe55d0 [ShellWindowTracker], out=0x559364fcc510 [GLocalFileOutputStream]) at /home/dan/git/gnome-shell/build/tmp-introspectcxwjenqm/Shell-0.1.c:137 #10 0x559364ad1b83 in dump_object_type (out=0x559364fcc510 [GLocalFileOutputStream], symbol=, type=0x559364fe55d0 [ShellWindowTracker]) at /home/dan/git/gnome-shell/build/tmp-introspectcxwjenqm/Shell-0.1.c:260 #11 0x559364ad1b83 in dump_type (out=0x559364fcc510 [GLocalFileOutputStream], symbol=, type=0x559364fe55d0 [ShellWindowTracker]) at /home/dan/git/gnome-shell/build/tmp-introspectcxwjenqm/Shell-0.1.c:402 #12 0x559364ad1b83 in dump_irepository (error=0x7ffc1ddd2ae0, arg=) at /home/dan/git/gnome-shell/build/tmp-introspectcxwjenqm/Shell-0.1.c:547 #13 0x559364ad1b83 in main (argc=, argv=) at /home/dan/git/gnome-shell/build/tmp-introspectcxwjenqm/Shell-0.1.c:610 (gdb) ** Changed in: gobject-introspection (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1812955 Title: g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding Status in gobject-introspection package in Ubuntu: Confirmed Bug description: g-ir-scanner is crashing with SIGSEGV instead of succeeding. So I can't build gnome-shell any more. Actually it looks like some kind of temporary sub-command "Shell-0.1" of g-ir-scanner that's crashing: /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include --no-libtool --namespace=Shell --nsversion=0.1 --warn-all --output src/Shell-0.1.gir --quiet -I/home/dan/git/gnome-shell/src -I/home/dan/git/gnome-shell/build/src -I./. -I../. -I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray --filelist=/home/dan/git/gnome-shell/build/src/src@@gnome-shell@sha/Shell_0.1_gir_filelist --include=Clutter-4 --include=ClutterX11-4 --include=Meta-4 --include=Gcr-3 --include=PolkitAgent-1.0 --include=NM-1.0 --include-uninstalled=subprojects/gvc/Gvc-1.0.gir --include-uninstalled=src/ShellMenu-0.1.gir --include-uninstalled=src/st/St-1.0.gir --cflags-begin -I./. -I../. -I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr
[Touch-packages] [Bug 1812955] Re: g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding
The same crash is happening upstream: https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/194604 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1812955 Title: g-ir-scanner/Shell-0.1 is crashing with SIGSEGV instead of succeeding Status in gobject-introspection package in Ubuntu: Confirmed Bug description: g-ir-scanner is crashing with SIGSEGV instead of succeeding. So I can't build gnome-shell any more. Actually it looks like some kind of temporary sub-command "Shell-0.1" of g-ir-scanner that's crashing: /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include --no-libtool --namespace=Shell --nsversion=0.1 --warn-all --output src/Shell-0.1.gir --quiet -I/home/dan/git/gnome-shell/src -I/home/dan/git/gnome-shell/build/src -I./. -I../. -I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray --filelist=/home/dan/git/gnome-shell/build/src/src@@gnome-shell@sha/Shell_0.1_gir_filelist --include=Clutter-4 --include=ClutterX11-4 --include=Meta-4 --include=Gcr-3 --include=PolkitAgent-1.0 --include=NM-1.0 --include-uninstalled=subprojects/gvc/Gvc-1.0.gir --include-uninstalled=src/ShellMenu-0.1.gir --include-uninstalled=src/st/St-1.0.gir --cflags-begin -I./. -I../. -I./src/st/. -I../src/st/. -I./src/st/.. -I../src/st/.. -I./src/tray -I../src/tray -pthread -I/usr/include/gio-unix-2.0/ -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/libdrm -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -include /usr/include/mozjs-60/js/RequiredDefines.h -I/usr/include/gobject-introspection-1.0 -I/usr/include/mozjs-60 -I/usr/include/gjs-1.0 -I/home/dan/tmp.gs/include/mutter-4/clutter -I/home/dan/tmp.gs/include/mutter-4/cogl -I/usr/include/json-glib-1.0 -I/usr/include/libwacom-1.0 -I/usr/include/startup-notification-1.0 -I/usr/include/polkit-1 -I/usr/include/gcr-3 -I/usr/include/gck-1 -I/usr/include/p11-kit-1 -I/usr/include/libnm -I/usr/include/libsecret-1 -I/usr/include/gstreamer-1.0 -D_REENTRANT -I/home/dan/tmp.gs/include/mutter-4 -I/home/dan/tmp.gs/include/gsettings-desktop-schemas -I/usr/include/gnome-desktop-3.0 -I/usr/include/gnome-settings-daemon-3.0 -I/usr/include/gudev-1.0 --cflags-end -L/home/dan/git/gnome-shell/build/src --add-include-path=/usr/share/gir-1.0 --add-include-path=/home/dan/tmp.gs/lib/x86_64-linux-gnu/mutter-4 --add-include-path=/home/dan/git/gnome-shell/build/subprojects/gvc --add-include-path=/home/dan/git/gnome-shell/build/src --add-include-path=/home/dan/git/gnome-shell/build/src/st -L/home/dan/git/gnome-shell/build/src -L/home/dan/git/gnome-shell/build/src/st -L/lib/x86_64-linux-gnu --library gnome-shell --extra-library=gio-2.0 --extra-library=gobject-2.0 --extra-library=glib-2.0 --extra-library=xml2 --extra-library=gtk-3 --extra-library=gdk-3 --extra-library=pangocairo-1.0 --extra-library=pango-1.0 --extra-library=atk-1.0 --extra-library=cairo-gobject --extra-library=cairo --extra-library=gdk_pixbuf-2.0 --extra-library=atk-bridge-2.0 --extra-library=gjs -L/home/dan/tmp.gs//lib/x86_64-linux-gnu/mutter-4 --extra-library=mutter-clutter-4 --extra-library=m --extra-library=json-glib-1.0 --extra-library=pangoft2-1.0 --extra-library=fontconfig --extra-library=freetype --extra-library=wayland-egl --extra-library=wayland-client --extra-library=Xtst --extra-library=Xi --extra-library=udev --extra-library=input --extra-library=xkbcommon --extra-library=wacom --extra-library=mutter-cogl-4 --extra-library=gmodule-2.0 -pthread --extra-library=wayland-server --extra-library=EGL --extra-library=X11 --extra-library=Xext --extra-library=Xdamage --extra-library=Xfixes --extra-library=Xcomposite --extra-library=Xrandr --extra-library=GL --extra-library=GLESv2 --extra-library=mutter-cogl-pango-4 --extra-library=startup-notification-1 --extra-library=girepository-1.0 --extra-library=polkit-agent-1 --extra-library=polkit-gobject-1 --extra-library=gcr-base-3 --extra-library=gck-1 --extra-library=p11-kit --extra-library=systemd --extra-library=nm --extra-library=secret-1 --extra-library=gstreamer-1.0 --extra-library=gstbase-1.0 -L/home/dan/tmp.gs//lib/x86_64-linux-gnu --extra-library=mutter-4 --extra-library=gnome-desktop-3 --extra-library=canberra --extra-library=gudev-1.0 --extra-library=pipewire-0.2 --extra-library=Xinerama --extra-library=ICE --extra-library=Xcursor --extra-library=xkbfile --extra-library=xkb
[Touch-packages] [Bug 1801496] Re: Printing job in 16.04 is slower than in 14.04
Dear Till, Thank you very much for taking your time to help investigate this issue and providing us a method to continue the investigation even when you are so busy. We had tried to figure out the difference of convert into PostScript and no conversion to PostScript by the method you provide on the date 2019-01-18(#15). But negatively, we don’t know the correct way to make it work. We use the PPD attached (Ricoh-MP_C5503_PXL.ppd) to print a job. The output capture file(test_modify_Fail.prn) shows that the capture command did not convert normally. The output capture file(test_modify_Fail.prn) on which you can figure out that capture command file output by the PPD (Add "*FoomaticRIPCommandLinePDF:") missing a lot of commands than the capture command file(test_original_OK.prn) output by the original PPD (without modify). We suspected the definition of FoomaticRIP Command is duplicate by below two define(“*FoomaticRIPCommandLine:” and “*FoomaticRIPCommandLinePDF:”): --- *FoomaticRIPCommandLine: "(printf '\033%%-12345X@PJL\n@PJL JOB\n@PJL SET COPIES=&copies;\n'%G|perl -p -e "s/\x26copies\x3b/1/"); (gs -q -dBATCH -dPARANOIDSAFER -dNOPAUSE -dNOINTERPOLATE %B%A%C %D%E | perl -p -e "s/^\x1b\x25-12345X//" | perl -p -e "s/\xc1\x01\x00\xf8\x31\x44/\x44/g"); (printf '@PJL\n@PJL EOJ\n\033%%-12345X')" *End *FoomaticRIPCommandLinePDF: "(printf '\033%%-12345X@PJL\n@PJL JOB\n@PJL SET COPIES=&copies;\n'%G|perl -p -e "s/\x26copies\x3b/1/"); (gs -q -dBATCH -dPARANOIDSAFER -dNOPAUSE -dNOINTERPOLATE %B%A%C %D%E | perl -p -e "s/^\x1b\x25-12345X//" | perl -p -e "s/\xc1\x01\x00\xf8\x31\x44/\x44/g"); (printf '@PJL\n@PJL EOJ\n\033%%-12345X')" *End --- So, we delete the command “*FoomaticRIPCommandLine:” from PPD, Hopping the way can make it works correctly. But the output capture file shows that this method is the same result with two FoomaticRIP Command definition. Can you lead us the correct way to the investigation of no conversion to PostScript. And if you have further investigation result, it’s appreciated to share with us. Attach file introduction: -- Original PPD Capture file: test_original_OK.prn Modify PPD Capture file: test_modify_Fail.prn CUPS Log file: error_log_Bill_job1043_1072 -- Best Regards, ** Attachment added: "LogAndCapture.zip" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1801496/+attachment/5232011/+files/LogAndCapture.zip -- 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/1801496 Title: Printing job in 16.04 is slower than in 14.04 Status in cups package in Ubuntu: Incomplete Bug description: Ubuntu 16.04LTS OS Version： 16.04.5 CUPS Version： 2.1.3 Ghostscript Version： 9.25 （2018-09-13） Printing job in 16.04 is slower than in 14.04 We(RICOH printer driver developer) are report a problem from our printer users: I print file Ubuntu 14.04.5, CUPS 2.1.3,Ghostscript 9.25 is fast(12 Seconds). But, after I update to Ubuntu 16.04, CUPS 2.1.3, Ghostscript 9.25, I print the same file with the same driver is slow(326 Seconds). I figure out that all the print jobs is much slower on Ubuntu 16.04. I view the "CUPS Error Log", it shows that there are three points which maybe the reasons that makes the print job slowly. FIRST: By counting the time from "Starting renderer" to "renderer exited with status 0", we figure out that 16.04 spend more time than 14.04 on "renderer" process. So we assuming that："renderer" is one of the key process that makes the print job slowly. "Starting renderer with command: \"printf \'\\033%%-12345X@PJL JOB\\012\';printf \'@PJL SET DATAMODE=TWIN\\ @PJL EOJ\\012\\033%%-12345X\'\"" . renderer exited with status 0" SECOND: On 16.04, a print job outputs lots of logs as below: "[Job xxx] Removing document files." This step(“Removing document files”)does not exsit on 14.04. The phenomenon that print jobs slower in 16.04 is more obvious when printing many jobs in the same time. THIRD We tried drivers form other company(HP,Brother…), the printings also slow down in Ubuntu 16.04 than 14.04. Our question is: 1. Do you have any plan to improve the performance of printing on Ubuntu 16.04? 2. Do you have any workaround before this problems fixed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/
[Touch-packages] [Bug 1809827] Re: --add-file broken in bionic
Hello Brian and Sebastien, many thanks for your help! Testing of proposed package is done successfully on our side, --add-file switch is working again as expected. pkg version: tar:amd64 (1.29b-2ubuntu0.1) ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1809827 Title: --add-file broken in bionic Status in tar package in Ubuntu: Fix Released Status in tar source package in Bionic: Fix Committed Status in tar package in Fedora: Unknown Bug description: same error like this one: https://bugzilla.redhat.com/show_bug.cgi?id=1436030#c0 * Impact tar supplied in bionic has --add-file option broken. * Test case Steps to Reproduce: 1. echo >a.txt 2. echo >b.txt 3. tar cf a.tar a.txt 4. tar rf a.tar --add-file=b.txt Actual results: tar: unhandled positional option 0 * Regression potential The changes are around an option which isn't working so no much regression potential there, check that other options still work though Is likely fixed by this: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=3a283cfe9f8f1f127e8dc5597a5ea1d249985a54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1809827/+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 1784135] Re: libicu-dev and libicu-dev:i386 conflict with each other
** Changed in: icu (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1784135 Title: libicu-dev and libicu-dev:i386 conflict with each other Status in icu package in Ubuntu: Confirmed Status in icu package in Debian: Fix Released Bug description: Release is bionic (18.04.1) When trying to install libicu-dev and libicu-dev:i386 together in bionic, the conflict with each other. It is expected that these two libs can be installed together in one system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1784135/+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
@Thales Loiola Raveli Try to blacklist the nouveau; go to the software updates -> additional driver to look for nvidia driver. I am fortunate that I did not get the mx150 model. -- 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
The problem can been solved by updating to the newest 4.19.x kernel. I am a Ubuntu user with Asus UX433FA. After a few testing, I can confirm that newer kernel 4.19.17 currently available in kernel.org is the solution (I tried out 4.19.8 as well but I experienced something else so I decided to use 4.19.17, which, by default, accepts the changes suggested by Jian-Hong). However, I am using a dual boot system. There is a minor problem that bugs me: even if I turned off the fast boosting in BIOS, if I boot into Windows then restart and try to boot into Ubuntu, the sound will distort and disappear eventually. The solution would be completely shutdown Windows every time you want to switch between the OS. Hope this could be solved in the future. A good thing though, is after installing the new kernel, the original 4.15.x kernel that ships with Ubuntu 18.04 can also output sound properly !!! But, I have always got the feeling that the sound quality on Ubuntu is not as good as that of Windows. I might be over-sensitive tho. -- 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 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
This bug was fixed in the package apt - 1.8.0~beta1 --- apt (1.8.0~beta1) unstable; urgency=medium [ anatoly techtonik ] * README.md: Document that apt is also included * apt.cc: Add "apt info" alias for muscle memory [ Jean-Pierre Giraud ] * French manpages translation update (Closes: #915952) [ Frans Spiesschaert ] * Dutch manpages translation update (Closes: #916358) [ Julian Andres Klode ] * cache hash: Use sse4.2 CRC32c on x86-64 where available * configuration: Compare size first during lookup * debListParser: Avoid native arch lookup in ParseDepends * hash32: Tighten to multiversion to x86-64 ELF and use uint32_t * apt-mark: Introduce minimize-manual * doc/apt-verbatim.ent: Point ubuntu-codename to disco (LP: #1812696) * CI: Use debian:buster as test base image * doc/apt-verbatim.ent: Debian buster is stable * SECURITY UPDATE: content injection in http method (CVE-2019-3462) (LP: #1812353) * debian/control: Drop libcurl4-gnutls-dev build dependency [ Mo Zhou ] * zh_CN.po: Update Simplified Chinese programs translation. [ Khem Raj ] * Remove `register` keyword [ Vasya Novikov ] * bash completion: add keys [ David Kalnischkies ] * Communicate back which key(s) were used for signing -- Julian Andres Klode Wed, 23 Jan 2019 16:49:34 +0100 ** Changed in: apt (Ubuntu Disco) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-3462 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: In Progress Status in apt source package in Disco: Fix Released Bug description: [Impact] APT documentation/example/manpages isn't referencing the current release which could be misleading for certain users. --- APT src code: --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu &ubuntu-codename; main restricted deb-src http://us.archive.ubuntu.com/ubuntu &ubuntu-codename; main restricted deb http://security.ubuntu.com/ubuntu &ubuntu-codename;-security main restricted deb-src http://security.ubuntu.com/ubuntu &ubuntu-codename;-security main restricted deb http://us.archive.ubuntu.com/ubuntu &ubuntu-codename;-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu &ubuntu-codename;-updates main restricted --- The ubuntu-codename variable for Xenial and late in APT points to 'trusty or 'xenial' which generate the doc example & manpage with the wrong release instead of the actual ubuntu-codename. APT in Xenial point to 'trusty'. APT in Bionic and late to 'xenial' It also affect the man page: Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] With Xenial and late: * Look sources.list(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look apt_preferences(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html * Look /usr/share/doc/apt/examples/sources.list $ lsb_release -cs bionic $ cat /usr/share/doc/apt/examples/sources.list # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu xenial main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted deb http://security.ubuntu.com/ubuntu xenial-security main restricted deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted -- You'll notice they all point to the wrong release. While we understand it's not a "bug' and only a reference/example... I think it's for the best interest of all if the examples/manpage reference the current release. [Regression Potential] * None, it only affect documentation/examples and manpages. No behavior change in the APT
[Touch-packages] [Bug 1813128] Re: package cups-daemon 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1813128 Title: package cups-daemon 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: New Bug description: thank you ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-daemon 2.2.7-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: W [22/Jan/2019:21:50:28 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_MFC_9330CDW-Gray..\' already exists W [22/Jan/2019:21:50:28 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_MFC_9330CDW-DeviceN..\' already exists E [22/Jan/2019:22:21:32 +0100] (null): PPD creation failed: No IPP attributes. Date: Tue Jan 22 21:51:23 2019 ErrorMessage: installed cups-daemon package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-22 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Brother_MFC_9330CDW: ipp://BRW606DC72FFB65.local:631/ipp/print MachineType: LENOVO 20DNS03M00 Papersize: a4 PpdFiles: Brother_MFC_9330CDW: MFC-9330CDW ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=bb5e13a6-243d-4114-aa05-83df320472a7 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=bb5e13a6-243d-4114-aa05-83df320472a7 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: cups Title: package cups-daemon 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JFET54WW(1.31) dmi.board.asset.tag: Not Available dmi.board.name: 20DNS03M00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJFET54WW(1.31):bd06/07/2018:svnLENOVO:pn20DNS03M00:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DNS03M00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad S3 Yoga 14 dmi.product.name: 20DNS03M00 dmi.product.version: ThinkPad S3 Yoga 14 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1813128/+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 1813128] [NEW] package cups-daemon 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1
Public bug reported: thank you ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-daemon 2.2.7-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: W [22/Jan/2019:21:50:28 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_MFC_9330CDW-Gray..\' already exists W [22/Jan/2019:21:50:28 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_MFC_9330CDW-DeviceN..\' already exists E [22/Jan/2019:22:21:32 +0100] (null): PPD creation failed: No IPP attributes. Date: Tue Jan 22 21:51:23 2019 ErrorMessage: installed cups-daemon package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-22 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Brother_MFC_9330CDW: ipp://BRW606DC72FFB65.local:631/ipp/print MachineType: LENOVO 20DNS03M00 Papersize: a4 PpdFiles: Brother_MFC_9330CDW: MFC-9330CDW ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=bb5e13a6-243d-4114-aa05-83df320472a7 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=bb5e13a6-243d-4114-aa05-83df320472a7 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: cups Title: package cups-daemon 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JFET54WW(1.31) dmi.board.asset.tag: Not Available dmi.board.name: 20DNS03M00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJFET54WW(1.31):bd06/07/2018:svnLENOVO:pn20DNS03M00:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DNS03M00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad S3 Yoga 14 dmi.product.name: 20DNS03M00 dmi.product.version: ThinkPad S3 Yoga 14 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1813128 Title: package cups-daemon 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: New Bug description: thank you ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-daemon 2.2.7-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: W [22/Jan/2019:21:50:28 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_MFC_9330CDW-Gray..\' already exists W [22/Jan/2019:21:50:28 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Brother_MFC_9330CDW-DeviceN..\' already exists E [22/Jan/2019:22:21:32 +0100] (null): PPD creation failed: No IPP attributes. Date: Tue Jan 22 21:51:23 2019 ErrorMessage: installed cups-daemon package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-01-22 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Brother_MFC_9330CDW: ipp://BRW606DC72FFB65.local:631/ipp/print MachineType: LENOVO 20DNS03M00 Papersize: a4 PpdFiles: Brother_MFC_9330CDW: MFC-9330CDW ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=bb5e13a6-243d-4114-aa05-83df320472a7 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=bb5e13a6-243d-4114-aa05-83df320472a7 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: cups Title: package cups-daemon 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2018 dmi.bios.vendor: LENOVO dmi.bios.version: JFET54WW(1.31) dmi.board.asset.tag: Not Available dmi.board.name: 20DNS03M00 dmi.board.vendor: LE
[Touch-packages] [Bug 1719579] Re: [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save
Thanks for agreeing to my suggested approach to resolve all of this!
I have already taken out the deny rules since Cosmic and we had no bad
feedback that ceph (the original reason to add them) would trigger log
storms.
Therefore this bug is completely done.
Status already reflects this, I'll remove David as assignee to completely clean
up.
** Changed in: ubuntu-power-systems
Assignee: David Britton (davidpbritton) => (unassigned)
--
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/1719579
Title:
[Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in
/var/tmp folder using virsh save
Status in The Ubuntu-power-systems project:
Fix Released
Status in apparmor package in Ubuntu:
Invalid
Status in libvirt package in Ubuntu:
Fix Released
Bug description:
== Comment: #1 - SEETEENA THOUFEEK - 2017-01-17
00:09:16 ==
Bala, Please mail me the machine information.
== Comment: #3 - SEETEENA THOUFEEK - 2017-01-17
02:14:06 ==
2017-01-16 12:09:37.707+: 7024: info :
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on
'/var/tmp/bala'
2017-01-16 12:09:37.707+: 7024: info :
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on
'/var/tmp/bala' to '0:0'
2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750
: failed to restore save state label on /var/tmp/bala
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 :
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF:
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x3fff4ca62b00
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x3fff4ca535c0
2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with
ret=-1
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x3fff7c002c10
2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590
rerr=0x3fffa59be3c0
2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 :
Encode length as 172
2017-01-16 12:09:37.707+: 7024: debug :
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172
offset=0
2017-01-16 12:09:37.707+: 7024: info :
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE:
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1
serial=4
2017-01-16 12:09:37.707+: 7024: debug :
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670
tx=0x100133d2590
2017-01-16 12:09:37.707+: 7024: debug :
virNetServerClientCalculateHandleMode:192 : mode=3
2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 :
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 :
Interrupting
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x3fff7c002c10
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x100133caea0
2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF:
obj=0x100133d23c0
.
2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 :
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds":
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status":
"failed"}}
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147
: mon=0x3fff94004d90 obj=0x100133b5670
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 :
object=0x100133a8000
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 :
object=0x100133a8000 type=0 gen=0x100133d1160
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 :
object=0x100133d2a80 type=2 gen=0x100133d1160
2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 :
result={"status":"failed"}
2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 :
mon=0x3fff94004d90 event=MIGRATION
2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF:
obj=0x3fff94004d90
2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 :
vm=0x3fff4ca535c0
2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW:
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645
