[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
This bug was fixed in the package openldap - 2.4.45+dfsg-1ubuntu1 --- openldap (2.4.45+dfsg-1ubuntu1) artful; urgency=low * Merge from Debian unstable. Remaining changes: - Enable AppArmor support: - d/apparmor-profile: add AppArmor profile - d/rules: use dh_apparmor - d/control: Build-Depends on dh-apparmor - d/slapd.README.Debian: add note about AppArmor - Enable GSSAPI support: - d/patches/gssapi.diff, thanks to Jerry Carter (Likewise): - Add --with-gssapi support - Make guess_service_principal() more robust when determining principal - d/configure.options: Configure with --with-gssapi - d/control: Added heimdal-dev as a build depend - d/rules: - Explicitly add -I/usr/include/heimdal to CFLAGS. - Explicitly add -I/usr/lib//heimdal to LDFLAGS. - Enable ufw support: - d/control: suggest ufw. - d/rules: install ufw profile. - d/slapd.ufw.profile: add ufw profile. - Enable nss overlay: - d/{patches/nssov-build,rules}: Apply, build and package the nss overlay. - d/{rules,slapd.py}: Add apport hook. - d/slapd.init.ldif: don't set olcRootDN since it's not defined in either the default DIT nor via an Authn mapping. - d/slapd.scripts-common: - add slapcat_opts to local variables. - Fix backup directory naming for multiple reconfiguration. - d/{slapd.default,slapd.README.Debian}: use the new configuration style. - d/rules: Enable -DLDAP_CONNECTIONLESS to build CLDAP (UDP) support in the openldap library, as required by Likewise-Open - Show distribution in version: - d/control: added lsb-release - d/patches/fix-ldap-distribution.patch: show distribution in version - d/libldap-2.4-2.symbols: Add symbols not present in Debian. - CLDAP (UDP) was added in 2.4.17-1ubuntu2 - GSSAPI support was enabled in 2.4.18-0ubuntu2 openldap (2.4.45+dfsg-1) unstable; urgency=medium * New upstream release. - fixed a use-after-free in GnuTLS options handling (ITS#8385) (Closes: #820244) (LP: #1557248) - fixed unsafe concurrent SASL calls causing memory corruption (ITS#8648) (Closes: #860947) (LP: #1688575) - fixed syncrepl infinite looping with multi-master delta-syncrepl (ITS#8432) (Closes: #868753) * Rebase patches to apply cleanly: - do-not-second-guess-sonames - no-AM_INIT_AUTOMAKE * Drop patches applied upstream: - ITS-8554-kFreeBSD-is-like-BSD.patch - ITS-8644-wait-for-slapd-to-start-in-test064.patch - ITS-8655-paged-results-double-free.patch * Upgrade to debhelper compat level 10. - Depend on debhelper 10. - Stop enabling parallel and autoreconf explicitly. They are now enabled by default. - Drop dh-autoreconf from build-depends since debhelper requires it. * Add -Wno-format-extra-args to CFLAGS to reduce the noise in the build logs, as this warning is emitted on each use of the Debug() macro. * Drop libldap-2.4-4-dbg and slapd-dbg binary packages in favour of automatic dbgsym packages. * Update Standards-Version to 4.0.0; no changes required. * Drop Priority and Section from binary package stanzas when they only duplicate information from the source stanza. * Update Priority of slapd-smbk5pwd and libldap2-dev to optional to match the archive. * Remove retired developer, Roland Bauerschmidt, from Uploaders. (Closes: #856422) * Remove Timo Aaltonen from Uploaders, with his agreement. * debian/patches/ITS8650-retry-gnutls_handshake-after-GNUTLS_E_AGAIN.patch: If gnutls_handshake() returns EAGAIN, call it again. Fixes TLS handshake failures when the ServerHello message exceeds 16K. (ITS#8650) (Closes: #861838) * Drop time from Build-Depends. The upstream testsuite no longer calls it. -- Gianfranco Costamagna Fri, 28 Jul 2017 14:49:07 +0200 ** Changed in: openldap (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 openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Committed Status in openldap package in Ubuntu: Fix Released Bug description: I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr
[Touch-packages] [Bug 1661766] Re: aa-genprof crashes on start due to python 3.6 bug
This bug was fixed in the package apparmor - 2.11.0-2ubuntu15 --- apparmor (2.11.0-2ubuntu15) artful; urgency=medium * Correctly remove system upstart job. -- Dimitri John Ledkov Mon, 07 Aug 2017 17:03:19 -0400 ** Changed in: apparmor (Ubuntu) Status: New => Fix Released -- 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/1661766 Title: aa-genprof crashes on start due to python 3.6 bug Status in AppArmor: Fix Committed Status in apparmor package in Ubuntu: Fix Released Bug description: aa-genprof crashes with the following error message on start: http://pastebin.com/SWvk4GAj It seem to be realated to the following bug with python 3.6: https://github.com/kennethreitz/tablib/issues/254 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1661766/+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 1632575] Re: systemd starts two copies of ntp at boot time
[Expired for ntp (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ntp (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1632575 Title: systemd starts two copies of ntp at boot time Status in ntp package in Ubuntu: Expired Bug description: My system monitoring check noticed a stale /var/run/ntpd.pid pidfile on a xenial machine that rebooted at 2 AM after unattended upgrades. ntpd itself was running, but with a different pid. Digging through journalctl I can see Oct 12 02:00:11 xenial64 ntp[681]: * Starting NTP server ntpd Oct 12 02:00:11 xenial64 systemd[1]: Started Getty on tty1. Oct 12 02:00:11 xenial64 systemd[1]: Reached target Login Prompts. Oct 12 02:00:11 xenial64 systemd[1]: Stopped LSB: Start NTP daemon. Oct 12 02:00:11 xenial64 systemd[1]: Stopped LSB: Start NTP daemon. Oct 12 02:00:11 xenial64 run-parts[760]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example Oct 12 02:00:11 xenial64 systemd[1]: Starting LSB: Start NTP daemon... Oct 12 02:00:11 xenial64 ntpd[719]: ntpd 4.2.8p4@1.3265-o Wed Oct 5 12:34:45 UTC 2016 (1): Starting Oct 12 02:00:11 xenial64 ntpd[719]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 109:114 Oct 12 02:00:11 xenial64 ntp[770]: * Starting NTP server ntpd Oct 12 02:00:11 xenial64 ntpd[778]: ntpd 4.2.8p4@1.3265-o Wed Oct 5 12:34:45 UTC 2016 (1): Starting Oct 12 02:00:11 xenial64 ntpd[778]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 109:114 Oct 12 02:00:11 xenial64 ntp[770]:...done. Oct 12 02:00:11 xenial64 systemd[1]: Started LSB: Start NTP daemon. Oct 12 02:00:11 xenial64 systemd[1]: Started Advanced key-value store. Oct 12 02:00:11 xenial64 ntpd[773]: proto: precision = 0.077 usec (-24) Oct 12 02:00:11 xenial64 ntpd[780]: proto: precision = 0.076 usec (-24) Oct 12 02:00:11 xenial64 ntpd[780]: unable to bind to wildcard address :: - another process may be running - EXITING Oct 12 02:00:11 xenial64 ntpd[773]: Listen and drop on 0 v6wildcard [::]:123 Oct 12 02:00:11 xenial64 ntpd[773]: Listen and drop on 1 v4wildcard 0.0.0.0:123 As you can see, for some reason systemd starts ntpd twice, so there's a race to take over the socket, and a race to take over the pidfile. ntpd[773] gets the socket, ntpd[780] gets the pidfile. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.3 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 12 06:18:29 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1632575/+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 1704295] Re: Gnome Software titlebar is too thin during startup under Ambiance
** Changed in: gnome-software (Ubuntu) Importance: Medium => Low ** Changed in: ubuntu-themes (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1704295 Title: Gnome Software titlebar is too thin during startup under Ambiance Status in gnome-software package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Gnome Software titlebar is too thin during startup under Ambiance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1704295/+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 1709766] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676380 *** https://bugs.launchpad.net/bugs/1676380 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1676380, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1676380 Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures -- 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/1709766 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: Unable to install virtualbox at Ubantu 16.04 , I have Intel nuk box . sudo apt-get install virtualbox-5.1 Getting error: Conflicts: virtualbox-5.1 but 5.1.26-117224~Ubuntu~xenial is to be installed E: Unmet dependencies. Try. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CupsErrorLog: Date: Wed Aug 9 22:10:22 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-06-11 (59 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Papersize: letter ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0057.2016.1012.1134 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0057.2016.1012.1134:bd10/12/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1709766/+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 1709766] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676380 *** https://bugs.launchpad.net/bugs/1676380 Public bug reported: Unable to install virtualbox at Ubantu 16.04 , I have Intel nuk box . sudo apt-get install virtualbox-5.1 Getting error: Conflicts: virtualbox-5.1 but 5.1.26-117224~Ubuntu~xenial is to be installed E: Unmet dependencies. Try. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CupsErrorLog: Date: Wed Aug 9 22:10:22 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-06-11 (59 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Papersize: letter ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0057.2016.1012.1134 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0057.2016.1012.1134:bd10/12/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1709766 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: Unable to install virtualbox at Ubantu 16.04 , I have Intel nuk box . sudo apt-get install virtualbox-5.1 Getting error: Conflicts: virtualbox-5.1 but 5.1.26-117224~Ubuntu~xenial is to be installed E: Unmet dependencies. Try. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CupsErrorLog: Date: Wed Aug 9 22:10:22 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-06-11 (59 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Papersize: letter ProcCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-30-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0057.2016.1012.1134 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0057.2016.1012.1134:bd10/12/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1709766/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
This bug was fixed in the package logrotate - 3.8.7-2ubuntu4 --- logrotate (3.8.7-2ubuntu4) artful; urgency=medium * logrotate does not ever recover from a corrupted statefile (LP: #1709670) - d/p/do-not-treat-failure-of-readState-as-fatal.patch (Backported from commit b9d82003002c98370e4131a7e43c76afcd23306a) -- Eric Desrochers Wed, 09 Aug 2017 11:39:36 -0700 ** Changed in: logrotate (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Trusty: In Progress Status in logrotate source package in Xenial: In Progress Status in logrotate source package in Zesty: In Progress Status in logrotate source package in Artful: Fix Released Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. Impact scenarios : - System could eventually run out of disk space on a separate partition if mounted in "/var" or specifically "/var/log" or even worst if "/var/log" is on the same partition as "/" it could create even more damage if by any chance the partition is running out of free space. - System keep updating the same files over and over, creating large size logfiles. - ... [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. * Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. * Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1709163] Re: default output changes from intel builtin to hdmi when display is turned off. yes off not on
If the problem was localized to 17.10 then I would have said try undoing a recent change we introduced to /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif But that's probably not relevant if you had the same bug in previous Ubuntu versions. There is however this module that's been enabled for a long time and isn't documented so I'm not yet familiar with its behaviour. Perhaps commenting this one out would help: ### Should be after module-*-restore but before module-*-detect load-module module-switch-on-port-available -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1709163 Title: default output changes from intel builtin to hdmi when display is turned off. yes off not on Status in pulseaudio package in Ubuntu: New Bug description: So if I have sound output selected to be the intel sound on the mainboard and turn off one of my two displays the audio out is changed to HDMI. YES OFF it's not a typo. The Display I turn off is connected to displayport and do not even have HDMI. The audio is switched over to the still active display. If I then turn the display back it's still hdmi. If I then turn off the display that has HDMI out connected. the audio is still connected to that display. since its actually off I hear no sound but pulseaudio still connect to it. I have to manually open the GUI tool and change back to the correct output when the display is turned off or when the display is blanked. or suspend/resume. I attache the output of "pacmd list-cards && pacmd list-sinks" ok -> ps_w1.txt fail -> ps_f1.txt --- ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kenjo 3721 F pulseaudio /dev/snd/controlC1: kenjo 3721 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2015-10-18 (659 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) Package: pulseaudio 1:10.0-2ubuntu1 PackageArchitecture: amd64 Tags: artful Uname: Linux 4.12.1-041201-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.I0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M7 (MS-7976) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7976 dmi.product.version: 1.0 dmi.sys.vendor: MSI modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709163/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
** Description changed: [Impact] - logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. - System will eventually run out of disk space on /var/log for instance. + logrotate never recovers if the statefile is corrupted unless you remove + it or fix the corruption by hand. + + Impact scenarios : + - System could eventually run out of disk space on a separate partition if mounted in "/var" or specifically "/var/log" or even worst if "/var/log" is on the same partition as "/" it could create even more damage if by any chance the partition is running out of free space. + + - System keep updating the same files over and over, creating large size logfiles. + - ... [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. * Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 ** Description changed: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. Impact scenarios : - - System could eventually run out of disk space on a separate partition if mounted in "/var" or specifically "/var/log" or even worst if "/var/log" is on the same partition as "/" it could create even more damage if by any chance the partition is running out of free space. - - System keep updating the same files over and over, creating large size logfiles. + - System could eventually run out of disk space on a separate partition + if mounted in "/var" or specifically "/var/log" or even worst if + "/var/log" is on the same partition as "/" it could create even more + damage if by any chance the partition is running out of free space. + + - System keep updating the same files over and over, creating large size + logfiles. + - ... [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. * Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 ** Description changed: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. Impact scenarios : - System could eventually run out of disk space on a separate partition if mounted in "/var" or specifically "/var/log" or even worst if "/var/log" is on the same partition as "/" it could create even more damage if by any chance the partition is running out of free space. - System keep updating the same files over and over, creating large size logfiles. - ... [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and
[Touch-packages] [Bug 1709736] [NEW] package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Public bug reported: installing Lazarus ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 9 20:03:52 2017 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2017-07-14 (26 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: glib2.0 Title: package libglib2.0-dev 2.48.2-0ubuntu1 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) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1709736 Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in glib2.0 package in Ubuntu: New Bug description: installing Lazarus ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 9 20:03:52 2017 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2017-07-14 (26 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: glib2.0 Title: package libglib2.0-dev 2.48.2-0ubuntu1 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/glib2.0/+bug/1709736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
On Tue, Aug 08, 2017 at 08:53:48AM -, ethan.hsieh wrote: > @Balint > > I tried three times, and 0.95-16.04.0rbalint1 didn't work well. > > Please refer to attached file for detailed log. > > 1) Reboot system when unattended upgrades starts to download packages. > //unattended-upgrades.log > 2017-08-08 15:34:07,782 INFO Starting unattended upgrades script > 2017-08-08 15:34:07,782 INFO Allowed origins are: ['o=Ubuntu,a=xenial', > 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] > //unattended-upgrades-shutdown.log > 2017-08-08 15:36:06,358 INFO - All upgrades installed > > The log shows "All upgrades installed", but there is no package > installed. > > 2) Reboot system after unattended upgrades downloads packages for 5mins > //unattended-upgrades.log > 2017-08-08 15:55:27,907 INFO Starting unattended upgrades script > 2017-08-08 15:55:27,907 INFO Allowed origins are: ['o=Ubuntu,a=xenial', > 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] > > System reboots immediately. There is no unattended-upgrades-shutdown > log. > > 3) Reboot system when unattended upgrades starts to download packages. > //unattended-upgrades.log > 2017-08-08 16:09:03,548 INFO Starting unattended upgrades script > 2017-08-08 16:09:03,549 INFO Allowed origins are: ['o=Ubuntu,a=xenial', > 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] > //unattended-upgrades-shutdown.log > 2017-08-08 16:10:50,573 INFO - All upgrades installed > > The log shows "All upgrades installed", but there is no package > installed. Keep in mind there is also the log file /var/log/unattended-upgrades/unattended-upgrades-dpkg.log which contains detailed information about the packages being installed. -- Brian Murray -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+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 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Ethan Yes, the "All upgrades installed" message is still misleading. Note however that there are two modes of u-u you can operate in on shutdown and they are picked by setting Unattended- Upgrade::InstallOnShutdown. When it is set to True u-u runs to completion (unless it times out after 15 minutes). In the other case (set to false) shutdown gracefully terminates u-u with the current fixes possibly (and probably) not installing every update. In that case the message is clearly misleading. I'm updating the message, but I believe that this is how u-u is expected to operate. -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+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 1708563] Re: apport silently sends crash reports to errors.ubuntu.com
That would be great. For years now I have been assuming it was broken, since there is no acknowledgement of any form. Consequently I have been pressing 'cancel' instead of submitting the report. Why not wait until the report has been sent before closing the dialog, for example, and giving an error if it isn't sent? Additionally, sometimes I would have liked to described what I was doing at the time of the crash -- sometimes there's some context that seems like it would be useful. It would be great to have that option offered. -- 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/1708563 Title: apport silently sends crash reports to errors.ubuntu.com Status in apport package in Ubuntu: Triaged Bug description: For quite some time now, I have experienced apport popup windows reporting certain crashes. When I click to submit a report, the popup window disappears and nothing further happens. In the past, when closing the popup window, I used to see a new Launchpad bug report where I could enter further details about what was happening, or check that the bug had already been reported by others. However that feature seems to have been disabled or become broken some time ago. If apport is going to silently ignore my request to report my bug, or is reporting it somehow without feedback me, then either of these is poor design, since there has been no feedback to me as the user about what is happening. Can I suggest that apport be changed to inform the user of whether or not the crash report will be uploaded, and whether or not the user will be redirected to give extra details? Then, if the firefox window fails to popup, I can report a separate bug about that if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1708563/+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 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
** Changed in: openssh (Debian) Assignee: (unassigned) => Andrew T. Aldridge (dubleeh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: New Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+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 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
** Also affects: openssh (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: New Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+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 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
** Also affects: openssh Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+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 1709055] Re: Drop support for Android (Ubuntu Touch patches)
** Changed in: pulseaudio (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1709055 Title: Drop support for Android (Ubuntu Touch patches) Status in pulseaudio package in Ubuntu: Fix Committed Bug description: Drop support for Android (Ubuntu Touch patches) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709055/+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 1709621] Re: Facebook login appears broken
This bug was fixed in the package gnome-online-accounts - 3.25.90-0ubuntu1 --- gnome-online-accounts (3.25.90-0ubuntu1) artful; urgency=medium * New upstream release - Fix Facebook login (LP: #1709621) * debian/control.in: - Bump minimum libglib2.0-dev to 2.52 * debian/rules: Explicitly enable Todoist and Telepathy * Add new symbols and drop 2 apparently unused symbols that are part of the "private" API - goa_oauth2_provider_get_authentication_cookie - goa_oauth_provider_get_authentication_cookie -- Jeremy Bicha Wed, 09 Aug 2017 10:02:07 -0400 ** Changed in: gnome-online-accounts (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1709621 Title: Facebook login appears broken Status in gnome-online-accounts: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Xenial: Triaged Status in gnome-online-accounts source package in Zesty: Triaged Bug description: Impact -- On latest 17.10 I tried to login to facebook via online accounts. I managed to login successfully, but now when I click the facebook icon in online accounts it pops up a box then goes away. In addition I don't see how I can post to facebook from other applications like shotwell. Seems it didn't fully create. Test Case - Regression Potential GNOME has a standing microrelease exception for Stable Release Updates. https://wiki.ubuntu.com/StableReleaseUpdates#GNOME ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 9 14:02:34 2017 InstallationDate: Installed on 2017-08-02 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1709621/+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 1707645] Re: system with high numbered uids has huge sparse /var/log/lastlog
** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1707645 Title: system with high numbered uids has huge sparse /var/log/lastlog Status in util-linux package in Ubuntu: New Bug description: I was investigating the use of a single high UID user (ie, 20) and discovered that /var/log/lastlog grew to an enormously large sparse file: $ ls -lh /var/log/lastlog -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog The file is actually quite small though: $ ls -lh --size /var/log/lastlog 56K -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog On a standalone system, this is possibly not a problem since it is highly unlikely that a system will have 2 billion users, but this is confirmed to wreak havoc on rsync backups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1707645/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
** Changed in: logrotate (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: Fix Committed Status in logrotate source package in Trusty: In Progress Status in logrotate source package in Xenial: In Progress Status in logrotate source package in Zesty: In Progress Status in logrotate source package in Artful: Fix Committed Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. * Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1709714] [NEW] srart-up backgrounds are fixed.
Public bug reported: Cannot be changed ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Aug 10 06:39:51 2017 DistUpgraded: 2017-06-06 10:44:16,052 DEBUG icon theme changed, re-reading DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] InstallationDate: Installed on 2017-06-05 (65 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic root=UUID=7c6836e2-8dff-4656-b696-a03a3fa554b3 ro quiet drm.debug=0xe splash plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-06-06 (64 days ago) dmi.bios.date: 08/04/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0R092H dmi.board.vendor: Dell Inc. dmi.chassis.type: 16 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/04/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0R092H:rvr:cvnDellInc.:ct16:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Thu Aug 10 06:36:27 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu zesty -- 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/1709714 Title: srart-up backgrounds are fixed. Status in xorg package in Ubuntu: New Bug description: Cannot be changed ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Aug 10 06:39:51 2017 DistUpgraded: 2017-06-06 10:44:16,052 DEBUG icon theme changed, re-reading DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell OptiPlex 755 [1028:0211] Subsystem: Dell OptiPlex 755 [1028:0211] InstallationDate: Installed on 2017-06-05 (65 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) MachineType: Dell Inc. OptiPlex 755 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic root=UUID=7c6836e2-8dff-4656-b696-a03a3fa554b3 ro quiet drm.debug=0xe splash plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-06-06 (64 days ago) dmi.bios.date: 08/04/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0R092H dmi.board.vendor: Dell Inc. dmi.chassis.type: 16 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/04/2008:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0R092H:rvr:cvnDellInc.:ct16:cvr: dmi.product.name: OptiPlex 755 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa
[Touch-packages] [Bug 1707645] Re: system with high numbered uids has huge sparse /var/log/lastlog
** Changed in: util-linux (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1707645 Title: system with high numbered uids has huge sparse /var/log/lastlog Status in util-linux package in Ubuntu: New Bug description: I was investigating the use of a single high UID user (ie, 20) and discovered that /var/log/lastlog grew to an enormously large sparse file: $ ls -lh /var/log/lastlog -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog The file is actually quite small though: $ ls -lh --size /var/log/lastlog 56K -rw-rw-r-- 1 root utmp 544G Jul 27 12:35 /var/log/lastlog On a standalone system, this is possibly not a problem since it is highly unlikely that a system will have 2 billion users, but this is confirmed to wreak havoc on rsync backups. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1707645/+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 1708905] Re: FQDN used as a hostname causes ping and other lookups to append the FQDN to unknown / unresolvable hosts when using wildcard DNS
** Package changed: ubuntu => systemd (Ubuntu) -- 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/1708905 Title: FQDN used as a hostname causes ping and other lookups to append the FQDN to unknown / unresolvable hosts when using wildcard DNS Status in systemd package in Ubuntu: New Bug description: If you configure your top level fully qualified domain name (FQDN) to use a wildcard DNS record in its zone file in bind9, any sub-servers (subdomains) or hostnames using part of the FQDN will have unexpected behavior when attempting to resolve DNS. -- Steps to reproduce: -- - Using the main server where the top level FQDN is configured: - 1. Create a wildcard A record in the main name server's zone file for your domain. Let's use example.com for this report. sudo nano /etc/bind/example.com Add this line to the end of the file: * IN A1.1.1.1 2. Save changes to the file and quit the editor. 3. Reload / restart bind9 to apply these changes. sudo service bind9 restart - On a subdomain server (just another server) that will use part of the FQDN: - 1. Change your server's hostname by editing /etc/hostname sudo nano /etc/hostname 2. Use a FQDN such as server1.example.com 2. Save changes to the file and quit the editor. 4. Add a hosts file entry for server1.example.com in /etc/hosts sudo nano /etc/hosts Add this line to the end of the file: 127.0.1.1 server1.example.com 5. Save changes to the file and quit the editor. 6. Reboot the server to apply the hostname and hosts changes. sudo shutdown -r now 7. In a terminal, ping any unresolvable or unknown host. ping adsfadsfadsfdsafadsfadsfadsfadsfadsfadsf.com The ping command appends .example.com to the host. adsfadsfadsfdsafadsfadsfadsfadsfadsfadsf.com.example.com will thus resolve to *.example.com. This is INCORRECT because I did NOT ping "adsfadsfadsfdsafadsfadsfadsfadsfadsfadsf.com.example.com" I pinged "adsfadsfadsfdsafadsfadsfadsfadsfadsfadsf.com". Wildcard DNS entries are being appended to a host lookup in certain utilities such as ping. This should NOT be happening. If you remove the wildcard entry from the main FQDN server and reload bind, pinging from the sub-server will now correctly return the error I was expecting of "ping: unknown host adsfadsfadsfdsafadsfadsfadsfadsfadsfadsf.com" More info: https://ubuntuforums.org/showthread.php?t=2368024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1708905/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
Tested the patch package (pre-SRU) on trusty and it works as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: In Progress Status in logrotate source package in Trusty: In Progress Status in logrotate source package in Xenial: In Progress Status in logrotate source package in Zesty: In Progress Status in logrotate source package in Artful: In Progress Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. * Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1709712] [NEW] Xorg freeze
Public bug reported: Computer freezes without apparent cause. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Wed Aug 9 17:35:26 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80d1] InstallationDate: Installed on 2017-03-18 (144 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: HP HP Pavilion x360 Convertible ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed root=UUID=8352e01f-2580-4315-98ff-f584b17874d1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80D1 dmi.board.vendor: HP dmi.board.version: 84.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd06/13/2017:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D1:rvr84.33:cvnHP:ct31:cvrChassisVersion: dmi.product.name: HP Pavilion x360 Convertible dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-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.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 9 17:34:56 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze 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/1709712 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Computer freezes without apparent cause. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Wed Aug 9 17:35:26 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80d1] InstallationDate: Installed on 2017-03-18 (144 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: HP HP Pavilion x360 Convertible ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed root=UUID=8352e01f-2580-4315-98ff-f584b17874d1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze
[Touch-packages] [Bug 1708905] [NEW] FQDN used as a hostname causes ping and other lookups to append the FQDN to unknown / unresolvable hosts when using wildcard DNS
You have been subscribed to a public bug: If you configure your top level fully qualified domain name (FQDN) to use a wildcard DNS record in its zone file in bind9, any sub-servers (subdomains) or hostnames using part of the FQDN will have unexpected behavior when attempting to resolve DNS. -- Steps to reproduce: -- - Using the main server where the top level FQDN is configured: - 1. Create a wildcard A record in the main name server's zone file for your domain. Let's use example.com for this report. sudo nano /etc/bind/example.com Add this line to the end of the file: * IN A1.1.1.1 2. Save changes to the file and quit the editor. 3. Reload / restart bind9 to apply these changes. sudo service bind9 restart - On a subdomain server (just another server) that will use part of the FQDN: - 1. Change your server's hostname by editing /etc/hostname sudo nano /etc/hostname 2. Use a FQDN such as server1.example.com 2. Save changes to the file and quit the editor. 4. Add a hosts file entry for server1.example.com in /etc/hosts sudo nano /etc/hosts Add this line to the end of the file: 127.0.1.1 server1.example.com 5. Save changes to the file and quit the editor. 6. Reboot the server to apply the hostname and hosts changes. sudo shutdown -r now 7. In a terminal, ping any unresolvable or unknown host. ping adsfadsfadsfdsafadsfadsfadsfadsfadsfadsf.com The ping command appends .example.com to the host. adsfadsfadsfdsafadsfadsfadsfadsfadsfadsf.com.example.com will thus resolve to *.example.com. This is INCORRECT because I did NOT ping "adsfadsfadsfdsafadsfadsfadsfadsfadsfadsf.com.example.com" I pinged "adsfadsfadsfdsafadsfadsfadsfadsfadsfadsf.com". Wildcard DNS entries are being appended to a host lookup in certain utilities such as ping. This should NOT be happening. If you remove the wildcard entry from the main FQDN server and reload bind, pinging from the sub-server will now correctly return the error I was expecting of "ping: unknown host adsfadsfadsfdsafadsfadsfadsfadsfadsfadsf.com" More info: https://ubuntuforums.org/showthread.php?t=2368024 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- FQDN used as a hostname causes ping and other lookups to append the FQDN to unknown / unresolvable hosts when using wildcard DNS https://bugs.launchpad.net/bugs/1708905 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1709670] Re: logrotate never recovers if the statefile is corrupted
** Changed in: logrotate (Ubuntu Zesty) Status: Confirmed => In Progress ** Changed in: logrotate (Ubuntu Trusty) Status: Confirmed => In Progress ** Changed in: logrotate (Ubuntu Xenial) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: In Progress Status in logrotate source package in Trusty: In Progress Status in logrotate source package in Xenial: In Progress Status in logrotate source package in Zesty: In Progress Status in logrotate source package in Artful: In Progress Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. * Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1709708] [NEW] Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio detects output but produces no sound on NUC6CAYH
Public bug reported: Upon bootup, the HDMI output connected to a Samsung TV shows up as an output. If this output is selected and a sound test run (either using the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no sound is heard. Pavumeter does however show sound coming through. I found that sound can be fixed by allowing the display to sleep, waking it up, and then restarting pulseaudio (pulseaudio -k). After that sound output through HDMI to the TV will work until rebooted. The fix can be succesfully scripted as follows: xset dpms force off sleep 1 pulseaudio -k The machine is an Intel NUC6CAYH, connected to a not particularly new Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu 16.04. In earlier attempts at fixing the issue I set pulseaudio to never let the sound device sleep (commented out load-module module-suspend-on-idle in /etc/pulse/default.pa), and also set the default sampling rate to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not sure if these settings contributed to the fix, but they are not sufficient on their own. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 9 21:48:39 2017 InstallationDate: Installed on 2017-08-06 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-402 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr: modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382 mtime.conffile..etc.pulse.default.pa: 2017-08-06T22:51:49.639085 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Description changed: Upon bootup, the HDMI output connected to a Samsung TV shows up as an output. If this output is selected and a sound test run (either using - the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav, no + the GUI or using aplay /user/share/sounds/alsa/Front_Center.wav) no sound is heard. Pavumeter does however show sound coming through. I found that sound can be fixed by allowing the display to sleep, waking it up, and then restarting pulseaudio (pulseaudio -k). After that sound output through HDMI to the TV will work until rebooted. The fix can be succesfully scripted as follows: xset dpms force off sleep 1 pulseaudio -k The machine is an Intel NUC6CAYH, connected to a not particularly new Samsung 42" TV using an HDMI cable, running a fresh install of Ubuntu 16.04. In earlier attempts at fixing the issue I set pulseaudio to never let the sound device sleep (commented out load-module module-suspend-on-idle in /etc/pulse/default.pa), and also set the default sampling rate to 48000 (default-sample-rate = 48000 in /etc/pulse/daemon.conf). Not sure if these settings contributed to the fix, but they are not sufficient on their own. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Aug 9 21:48:39 2017 InstallationDate: Installed on 2017-08-06 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Title: [, Intel Broxton HDMI, Digital Out, HDMI] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0029.2016.1124.1625 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-402 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0029.2016.1124.1625:bd11/24/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-402:cvn:ct3:cvr: modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-08-06T22:55:35.510382 mtime.conffile
[Touch-packages] [Bug 1709670] Re: logrotate never recovers if the statefile is corrupted
** Patch removed: "lp1709670-logrotate-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+attachment/4929665/+files/lp1709670-logrotate-zesty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: In Progress Status in logrotate source package in Trusty: Confirmed Status in logrotate source package in Xenial: Confirmed Status in logrotate source package in Zesty: Confirmed Status in logrotate source package in Artful: In Progress Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. * Additionally, I will run the /path_to_source/test/test script as a dogfooding that does ~72 tests. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
** Description changed: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] - * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. - - * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. + * Risk of potential regression is low, and IMHO couldn't be worst than + the actual situation where logrotate simply doesn't recover from a + corrupt statefile. + + * The current patch does recover (after verification) and has been + through some upstream CI validation, community feedbacks, et al. + + * Additionally, I will run the /path_to_source/test/test script as a + dogfooding that does a bunch of tests. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 ** Description changed: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. - * Additionally, I will run the /path_to_source/test/test script as a - dogfooding that does a bunch of tests. + * Additionally, I will run the /path_to_source/test/test script as a + dogfooding that does ~72 tests. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 ** Tags removed: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: In Progress Status in logrotate source package in Trusty: Confirmed Status in logrotate source package in Xenial: Confirmed Status in logrotate source package in Zesty: Confirmed Status in logrotate source package in Artful: In Progress Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et
[Touch-packages] [Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting
Revisting this on an artful image, and nothing besides the driver replug (what netplan apply does) appears to work to process .link files. Something changed I suspect in systemd w.r.t the builtin-test setup_net_link path which would process .link files. -- 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/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting Status in systemd package in Ubuntu: New Status in systemd source package in Artful: New Bug description: 1. root@ubuntu:~# lsb_release -rd Description:Ubuntu Zesty Zapus (development branch) Release:17.04 2. root@ubuntu:~# apt-cache policy udev udev: Installed: 232-18ubuntu1 Candidate: 232-18ubuntu1 Version table: *** 232-18ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status 3. udevadm trigger --verbose --subsystem-match=net --action=add will run and read .link files from /run/systemd/network/10-netplan-interface1.link and apply MTU settings 4. during system boot running (3) does not set the MTU; running (3) after boot has completed MTU is set correctly. Here'a log during boot where cloud-init generates a netplan config, invokes `netplan generate` which writes the networkd config out and then udevadm trigger (3). Upon logging in interface1 has an MTU of 1500. Re-running udevadm trigger now runs the rules/link files and updates the MTU. Note that, if you run udevadm test /sys/class/net/interface1; this also will apply the MTU (test probably shouldn't change the interface, I'll file a bug for that as well). # journalctl -o short-precise --no-pager -b | grep WARK Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['netplan', '--debug', 'generate']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['stat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['cat', '/run/systemd/network/10-netplan-interface1.link']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['systemctl', 'start', '--no-block', 'systemd-udev-trigger.service']: Mar 02 19:17:19.839797 ubuntu cloud-init[647]: WARK: ['udevadm', 'trigger', '--verbose', '--subsystem-match=net', '--action=add']: root@ubuntu:~# cat /run/systemd/network/10-netplan-interface1.link [Match] MACAddress=52:54:00:12:34:02 [Link] Name=interface1 WakeOnLan=off MTUBytes=1492 root@ubuntu:~# ifconfig interface1 interface1: flags=4163 mtu 1500 inet 10.0.2.100 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::5054:ff:fe12:3402 prefixlen 64 scopeid 0x20 inet6 fec0::5054:ff:fe12:3402 prefixlen 64 scopeid 0x40 ether 52:54:00:12:34:02 txqueuelen 1000 (Ethernet) RX packets 16 bytes 5053 (5.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 35 bytes 3287 (3.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@ubuntu:~# udevadm trigger --verbose --subsystem-match=net --action=add /sys/devices/pci:00/:00:04.0/virtio1/net/interface1 /sys/devices/pci:00/:00:05.0/virtio2/net/interface2 ys/devices/pci:00/:00:06.0/virtio3/net/interface0 /sys/devices/virtual/net/lo root@ubuntu:~# ifconfig interface1 interface1: flags=4163 mtu 1492 inet 10.0.2.100 netmask 255.255.255.0 broadcast 10.0.2.255 inet6 fe80::5054:ff:fe12:3402 prefixlen 64 scopeid 0x20 inet6 fec0::5054:ff:fe12:3402 prefixlen 64 scopeid 0x40 ether 52:54:00:12:34:02 txqueuelen 1000 (Ethernet) RX packets 16 bytes 5053 (5.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 37 bytes 3504 (3.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: udev 232-18ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Thu Mar 2 19:22:14 2017 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcEnviron: TERM=vt220 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-8-generic root=UUID=8bbb84fe-91e8-4a9a-bd91-f6af4793727e ro console=ttyS0 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.1-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1:bd04/01/2014:svnQEM
[Touch-packages] [Bug 1492174] Re: Notebook does not shutdown when battery is critically low
This bug is still active in Ubuntu Gnome 17.04. Changing the value of attribute critical-battery-action from "suspend" to "shutdown" within org/gnome/settings-daemon/plugins/power inside dconf editor does not help: the laptop still goes to sleep instead of shutting down. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1492174 Title: Notebook does not shutdown when battery is critically low Status in d-conf package in Ubuntu: Confirmed Bug description: After discharging the battery completely, my notebook suspends instead of shutting down. To prevent the battery from getting damaged, it is important that the machine shuts down. This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10. In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'. In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'. In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again. So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely! This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action. It leads to unwanted behavior of machines when users change power settings by executing: "gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1492174/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
Sponsored to artful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: In Progress Status in logrotate source package in Trusty: Confirmed Status in logrotate source package in Xenial: Confirmed Status in logrotate source package in Zesty: Confirmed Status in logrotate source package in Artful: In Progress Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
@iiro, That is interesting ... To recap using KVM you can't reproduce the situation (just like me) that you are experience using virtualbox ... so we are on the same page about not being able to reproduce using LXC nor KVM, but you can reproduce it if using virtualbox. I'll give it a try this week and see if I can reproduce it using virtualbox. Thanks a bunch iiro. Please keep me posted if you find anything else relevant. Regards, Eric -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Triaged Status in cups source package in Yakkety: Fix Released Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
** Description changed: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] - * Risk of potential regression is low, and couldn' be worst than the actual situation where logrotate doesn't recover from a corrupt statefile. - The current patch does recover (after verification) + * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. + + * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: In Progress Status in logrotate source package in Trusty: Confirmed Status in logrotate source package in Xenial: Confirmed Status in logrotate source package in Zesty: Confirmed Status in logrotate source package in Artful: In Progress Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
Debdiff for stable release : Zesty/17.04 ** Patch added: "lp1709670-logrotate-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+attachment/4929665/+files/lp1709670-logrotate-zesty.debdiff ** Changed in: logrotate (Ubuntu Zesty) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: logrotate (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: logrotate (Ubuntu Trusty) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: In Progress Status in logrotate source package in Trusty: Confirmed Status in logrotate source package in Xenial: Confirmed Status in logrotate source package in Zesty: Confirmed Status in logrotate source package in Artful: In Progress Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and IMHO couldn't be worst than the actual situation where logrotate simply doesn't recover from a corrupt statefile. * The current patch does recover (after verification) and has been through some upstream CI validation, community feedbacks, et al. [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
Debdiff for devel release Artful. ** Patch added: "lp1709670-logrotate-artful.debdiff" https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+attachment/4929643/+files/lp1709670-logrotate-artful.debdiff ** Tags added: patch ** Changed in: logrotate (Ubuntu Trusty) Status: New => Confirmed ** Changed in: logrotate (Ubuntu Zesty) Status: New => Confirmed ** Changed in: logrotate (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: In Progress Status in logrotate source package in Trusty: Confirmed Status in logrotate source package in Xenial: Confirmed Status in logrotate source package in Zesty: Confirmed Status in logrotate source package in Artful: In Progress Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and couldn' be worst than the actual situation where logrotate doesn't recover from a corrupt statefile. The current patch does recover (after verification) [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1709688] Re: package systemd 229-4ubuntu17 failed to install/upgrade: subprocess installed pre-removal script 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709688 Title: package systemd 229-4ubuntu17 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Teamviewer failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Aug 9 14:04:07 2017 DpkgTerminalLog: Removing systemd (229-4ubuntu17) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 DuplicateSignature: package:systemd:229-4ubuntu17 Removing systemd (229-4ubuntu17) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-29 (101 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Inspiron 3646 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=2a8d6b85-2950-47ff-bac6-29533c928095 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu17 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0KXN37 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/17/2015:svnDellInc.:pnInspiron3646:pvr:rvnDellInc.:rn0KXN37:rvrA00:cvnDellInc.:ct3:cvrA09: dmi.product.name: Inspiron 3646 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709688/+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 1671951] Re: networkd should allow configuring IPV6 MTU
Unsubscribing sponsors based upon IRC discussion with rharper: 10:57 < nacc> rharper: is LP: #1671951 actually ready to sponsor? 10:57 < ubottu> Launchpad bug 1671951 in systemd (Ubuntu) "networkd should allow configuring IPV6 MTU" [Medium,New] https://launchpad.net/bugs/1671951 11:07 < rharper> nacc: it was, but not sure of the status now; the debdiff likely needs refreshed against systemd in artful; I'm not sure of xnox or anyone else attempted to re-work the issue upstream; 11:08 < nacc> rharper: ok, can i unsub sponsors for now? 11:08 < rharper> sure -- 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd package in Ubuntu: New Bug description: 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+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 1709688] [NEW] package systemd 229-4ubuntu17 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: Teamviewer failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Aug 9 14:04:07 2017 DpkgTerminalLog: Removing systemd (229-4ubuntu17) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 DuplicateSignature: package:systemd:229-4ubuntu17 Removing systemd (229-4ubuntu17) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-29 (101 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Inspiron 3646 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=2a8d6b85-2950-47ff-bac6-29533c928095 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu17 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0KXN37 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/17/2015:svnDellInc.:pnInspiron3646:pvr:rvnDellInc.:rn0KXN37:rvrA00:cvnDellInc.:ct3:cvrA09: dmi.product.name: Inspiron 3646 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709688 Title: package systemd 229-4ubuntu17 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Teamviewer failed to install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Aug 9 14:04:07 2017 DpkgTerminalLog: Removing systemd (229-4ubuntu17) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 DuplicateSignature: package:systemd:229-4ubuntu17 Removing systemd (229-4ubuntu17) ... systemd is the active init system, please switch to another before removing systemd. dpkg: error processing package systemd (--purge): subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-29 (101 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Inspiron 3646 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=2a8d6b85-2950-47ff-bac6-29533c928095 ro quiet splash vt.handoff=7 init=/lib/systemd/systemd RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu17 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Here's the relevant journalctl log on VirtualBox. It complains something about colord. "Laitetta tai osoitetta ei ole" means "No such device or address". elo 09 20:32:09 il-VirtualBox colord[1431]: (colord:1431): Cd-WARNING **: failed to get session [pid 3130]: Laitetta tai osoitetta ei ole elo 09 20:32:18 il-VirtualBox systemd[1]: Stopped CUPS Scheduler. elo 09 20:32:18 il-VirtualBox systemd[1]: Reloading. elo 09 20:32:18 il-VirtualBox systemd[1]: Stopping Make remote CUPS printers available locally... elo 09 20:32:18 il-VirtualBox systemd[1]: Started ACPI event daemon. elo 09 20:32:18 il-VirtualBox systemd[1]: Stopped Make remote CUPS printers available locally. elo 09 20:32:18 il-VirtualBox systemd[1]: Stopping CUPS Scheduler... elo 09 20:32:18 il-VirtualBox systemd[1]: Started CUPS Scheduler. elo 09 20:32:18 il-VirtualBox colord[1431]: (colord:1431): Cd-WARNING **: failed to get session [pid 6581]: Laitetta tai osoitetta ei ole elo 09 20:32:18 il-VirtualBox systemd[1]: Stopped CUPS Scheduler. elo 09 20:32:19 il-VirtualBox systemd[1]: Reloading. elo 09 20:32:19 il-VirtualBox systemd[1]: Stopping CUPS Scheduler... elo 09 20:32:19 il-VirtualBox systemd[1]: Started ACPI event daemon. elo 09 20:32:19 il-VirtualBox systemd[1]: Started CUPS Scheduler. elo 09 20:32:19 il-VirtualBox colord[1431]: (colord:1431): Cd-WARNING **: failed to get session [pid 6682]: Laitetta tai osoitetta ei ole elo 09 20:32:20 il-VirtualBox systemd[1]: Reloading. elo 09 20:32:20 il-VirtualBox systemd[1]: Started ACPI event daemon. elo 09 20:32:20 il-VirtualBox systemd[1]: Reloading. elo 09 20:32:20 il-VirtualBox systemd[1]: Started CUPS Scheduler. elo 09 20:32:20 il-VirtualBox systemd[1]: Started ACPI event daemon. elo 09 20:32:20 il-VirtualBox systemd[1]: Reloading. elo 09 20:32:20 il-VirtualBox systemd[1]: Started ACPI event daemon. elo 09 20:32:20 il-VirtualBox systemd[1]: Started CUPS Scheduler. elo 09 20:32:20 il-VirtualBox systemd[1]: Started CUPS Scheduler. -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Triaged Status in cups source package in Yakkety: Fix Released Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@
[Touch-packages] [Bug 1709670] Re: logrotate never recovers if the statefile is corrupted
** Bug watch added: Debian Bug tracker #871592 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 ** Also affects: logrotate (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 Importance: Unknown Status: Unknown ** Description changed: - - Install logrotate + [Impact] + + logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. + System will eventually run out of disk space on /var/log for instance. + + [Test Case] + + - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - - Re-run "/etc/cron.daily/logrotate" and you will get something like this "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate + - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate - logrotate never recovers if the statefile is corrupted unless you remove - it or fix the corruption by hand. + [Regression Potential] - System will eventually run out of disk space and crash. + * Risk of potential regression is low, and couldn' be worst than the actual situation where logrotate doesn't recover from a corrupt statefile. +The current patch does recover (after verification) + + [Other Info] + + * Upstream commit: + https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a + + * Upstream bug: + https://github.com/logrotate/logrotate/issues/45 + + * Debian bug: + https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 ** Description changed: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate + Unless you remove the statefile and start again or fix the corruption by + hand. + [Regression Potential] - * Risk of potential regression is low, and couldn' be worst than the actual situation where logrotate doesn't recover from a corrupt statefile. -The current patch does recover (after verification) + * Risk of potential regression is low, and couldn' be worst than the actual situation where logrotate doesn't recover from a corrupt statefile. + The current patch does recover (after verification) [Other Info] - + * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871592 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: In Progress Status in logrotate source package in Trusty: New Status in logrotate source package in Xenial: New Status in logrotate source package in Zesty: New Status in logrotate source package in Artful: In Progress Status in logrotate package in Debian: Unknown Bug description: [Impact] logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space on /var/log for instance. [Test Case] - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and one will get the following error : "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate Unless you remove the statefile and start again or fix the corruption by hand. [Regression Potential] * Risk of potential regression is low, and couldn' be worst than the actual situation where logrotate doesn't recover from a corrupt statefile. The current patch does recover (after verification) [Other Info] * Upstream commit: https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a * Upstream bug: https://github.com/logrotate/logrotate/issues/45 * Debian bug: https://bugs.de
[Touch-packages] [Bug 1709676] [NEW] package libcdparanoia0:i386 3.10.2+debian-11 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a
Public bug reported: error always appearing when updating system. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libcdparanoia0:i386 3.10.2+debian-11 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: gstreamer1.0-plugins-base:i386: Remove libcdparanoia0:i386: Remove NULL: ConfigurePending Architecture: amd64 Date: Sun Aug 6 18:02:59 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 multiarch-support 2.24-9ubuntu2.2 DpkgTerminalLog: A remover gstreamer1.0-plugins-base:i386 (1.10.4-1ubuntu1) ... dpkg: erro ao processar o pacote libcdparanoia0:i386 (--remove): O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. ErrorMessage: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: cdparanoia Title: package libcdparanoia0:i386 3.10.2+debian-11 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cdparanoia (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cdparanoia in Ubuntu. https://bugs.launchpad.net/bugs/1709676 Title: package libcdparanoia0:i386 3.10.2+debian-11 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. Status in cdparanoia package in Ubuntu: New Bug description: error always appearing when updating system. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libcdparanoia0:i386 3.10.2+debian-11 ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: gstreamer1.0-plugins-base:i386: Remove libcdparanoia0:i386: Remove NULL: ConfigurePending Architecture: amd64 Date: Sun Aug 6 18:02:59 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 multiarch-support 2.24-9ubuntu2.2 DpkgTerminalLog: A remover gstreamer1.0-plugins-base:i386 (1.10.4-1ubuntu1) ... dpkg: erro ao processar o pacote libcdparanoia0:i386 (--remove): O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. ErrorMessage: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: cdparanoia Title: package libcdparanoia0:i386 3.10.2+debian-11 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdparanoia/+bug/1709676/+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 1709670] Re: logrotate never recovers if the statefile is corrupted
Using the above reproducer ^ I confirm that logrotate never recover if the statefile is corrupted unless you remove it or fix the corruption by hand. The upstream fix introduce in 3.12.0-18 [1] is fixing the issue[2] (tested using Artful so far) Since all supported|devel releases are lower than 3.12 [3], then all releases are affected. [1] - https://github.com/logrotate/logrotate/commit/b9d82003002c98370e4131a7e43c76afcd23306a # git describe --contains b9d8200 3.12.0~18 [2] - https://github.com/logrotate/logrotate/issues/45 [3] - rmadison logrotate | 3.8.7-1ubuntu1 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el logrotate | 3.8.7-1ubuntu1 | vivid | source, amd64, arm64, armhf, i386, powerpc, ppc64el logrotate | 3.8.7-1ubuntu1.1 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el logrotate | 3.8.7-2ubuntu2 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x logrotate | 3.8.7-2ubuntu2.16.04.1 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x logrotate | 3.8.7-2ubuntu3 | zesty | source, amd64, arm64, armhf, i386, ppc64el, s390x logrotate | 3.8.7-2ubuntu3 | artful | source, amd64, arm64, armhf, i386, ppc64el, s390x Regards, Eric ** Tags added: sts sts-sru-needed ** Also affects: logrotate (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: logrotate (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: logrotate (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: logrotate (Ubuntu Zesty) Importance: Undecided Status: New ** Bug watch added: github.com/logrotate/logrotate/issues #45 https://github.com/logrotate/logrotate/issues/45 ** Changed in: logrotate (Ubuntu Artful) Status: New => In Progress ** Changed in: logrotate (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: logrotate (Ubuntu Artful) Assignee: (unassigned) => Eric Desrochers (slashd) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: In Progress Status in logrotate source package in Trusty: New Status in logrotate source package in Xenial: New Status in logrotate source package in Zesty: New Status in logrotate source package in Artful: In Progress Bug description: - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and you will get something like this "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space and crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1709628] Re: New release wayland 1.14.0
Ubuntu's wayland package is synced from Debian. Therefore, you can file a Debian bug if you want to see this updated sooner. Is there any change in particular you were expecting in the new version? ** Changed in: wayland (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1709628 Title: New release wayland 1.14.0 Status in wayland package in Ubuntu: New Bug description: Hello, New Release: https://lists.freedesktop.org/archives/wayland-devel/2017-August/034748.html Regards, -- Cristian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1709628/+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 1709667] Re: Regression - Loss of hiDPI configuration settings
The workaround here is to manually execute ```gsettings set org.gnome.desktop.interface scaling-factor 2``` and then restart the system to be into a scaled (2x) mode. -- 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/1709667 Title: Regression - Loss of hiDPI configuration settings Status in xorg package in Ubuntu: New Bug description: When upgrading from ubuntu 17.04 to 17.10 (obviously new window manager) ... there is no longer the ability to configure the HiDPI scaling within the window manager. This may be an intentional regression or simply something that got passed by. But I find this configuration option to be very useful when working on a Lenovo P70 w/ 17" 4k monitor (which neds 2x DPI scaling) and also when switching back to my multiple-monitor configuration (which doesn't need any scaling). This is a piece of functionality I use on a regular basis that is now lost. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Aug 9 09:24:28 2017 DistUpgraded: 2017-08-07 09:44:27,630 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.11.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2016-11-30 (251 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform 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.11.0-10-generic root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-08-07 (1 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Aug 7 08:59:11 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output Virtual2Virtual3Virtual4Virtual5Virtual6 Virtual7Virtual8 xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: vmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1709667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
On Wed, Aug 09, 2017 at 04:28:43PM -, Iiro Laiho wrote: > Cannot reproduce. Maybe this has something to do with VirtualBox. Sounds like a race. -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Triaged Status in cups source package in Yakkety: Fix Released Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1709670] [NEW] logrotate never recovers if the statefile is corrupted
Public bug reported: - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and you will get something like this "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space and crash. ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1709670 Title: logrotate never recovers if the statefile is corrupted Status in logrotate package in Ubuntu: New Bug description: - Install logrotate - Run "/etc/cron.daily/logrotate" ## The first logrotate run will generate the statefile "var/lib/logrotate/status" - Modify "/var/lib/logrotate/status" by removing the first line in order to corrupt the file - Re-run "/etc/cron.daily/logrotate" and you will get something like this "error: bad top line in state file /var/lib/logrotate/status" every time you run logrotate logrotate never recovers if the statefile is corrupted unless you remove it or fix the corruption by hand. System will eventually run out of disk space and crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1709670/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
After talking with slashd, I did my own experiment in the same way I did with virtualbox, but this time I used virt-manager and KVM instead. Cannot reproduce. Maybe this has something to do with VirtualBox. -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Triaged Status in cups source package in Yakkety: Fix Released Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1709628] Re: New release wayland 1.14.0
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1709628 Title: New release wayland 1.14.0 Status in wayland package in Ubuntu: New Bug description: Hello, New Release: https://lists.freedesktop.org/archives/wayland-devel/2017-August/034748.html Regards, -- Cristian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1709628/+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 1709667] [NEW] Regression - Loss of hiDPI configuration settings
Public bug reported: When upgrading from ubuntu 17.04 to 17.10 (obviously new window manager) ... there is no longer the ability to configure the HiDPI scaling within the window manager. This may be an intentional regression or simply something that got passed by. But I find this configuration option to be very useful when working on a Lenovo P70 w/ 17" 4k monitor (which neds 2x DPI scaling) and also when switching back to my multiple-monitor configuration (which doesn't need any scaling). This is a piece of functionality I use on a regular basis that is now lost. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Aug 9 09:24:28 2017 DistUpgraded: 2017-08-07 09:44:27,630 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.26, 4.11.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2016-11-30 (251 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform 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.11.0-10-generic root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-08-07 (1 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Aug 7 08:59:11 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputVirtual2 Virtual3Virtual4Virtual5Virtual6Virtual7 Virtual8 xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: vmware ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: hidpi high-resolution scaling -- 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/1709667 Title: Regression - Loss of hiDPI configuration settings Status in xorg package in Ubuntu: New Bug description: When upgrading from ubuntu 17.04 to 17.10 (obviously new window manager) ... there is no longer the ability to configure the HiDPI scaling within the window manager. This may be an intentional regression or simply something that got passed by. But I find this configuration option to be very useful when working on a Lenovo P70 w/ 17" 4k monitor (which neds 2x DPI scaling) and also when switching back to my multiple-monitor configuration (which doesn't need any scaling). This is a piece of functionality I use on a regular basis that is now lost. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins
[Touch-packages] [Bug 1709649] Re: 229 backport for race between explicit mount and handling automount
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1709649 Title: 229 backport for race between explicit mount and handling automount Status in systemd package in Ubuntu: Confirmed Bug description: Hi, We have a blocking issue in systemd for the following release ``` NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial ``` This release runs systemd229, we are affected by the following auto- mouting race condition ``` https://github.com/systemd/systemd/pull/5916 ``` Is back porting the fix to the release 229 an option? Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709649/+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 1709649] [NEW] 229 backport for race between explicit mount and handling automount
Public bug reported: Hi, We have a blocking issue in systemd for the following release ``` NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial ``` This release runs systemd229, we are affected by the following auto- mouting race condition ``` https://github.com/systemd/systemd/pull/5916 ``` Is back porting the fix to the release 229 an option? Regards. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709649 Title: 229 backport for race between explicit mount and handling automount Status in systemd package in Ubuntu: New Bug description: Hi, We have a blocking issue in systemd for the following release ``` NAME="Ubuntu" VERSION="16.04.3 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.3 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial ``` This release runs systemd229, we are affected by the following auto- mouting race condition ``` https://github.com/systemd/systemd/pull/5916 ``` Is back porting the fix to the release 229 an option? Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1709649/+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 1709645] [NEW] package linux-image-4.10.0-30-generic 4.10.0-30.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
Public bug reported: https://bugs.launchpad.net/bugs/1708785 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-30-generic 4.10.0-30.34 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riofest1238 F pulseaudio Date: Wed Aug 9 11:30:58 2017 Df: Dmesg: ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=6d4e0f10-12e3-4a73-86fd-25ad6f7af483 InstallationDate: Installed on 2017-08-08 (1 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 004: ID 064e:a118 Suyin Corp. Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LG Electronics A410-G.BE31P1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=95968d68-ac8e-4230-b8d6-6d81bfff617d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-4.10.0-30-generic 4.10.0-30.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2011 dmi.bios.vendor: INSYDE dmi.bios.version: QL7L3F71 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrQL7L3F71:bd01/06/2011:svnLGElectronics:pnA410-G.BE31P1:pvrTBD:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: A410-G.BE31P1 dmi.product.version: TBD dmi.sys.vendor: LG Electronics ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- 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/1709645 Title: package linux-image-4.10.0-30-generic 4.10.0-30.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in initramfs-tools package in Ubuntu: New Bug description: https://bugs.launchpad.net/bugs/1708785 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-30-generic 4.10.0-30.34 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: riofest1238 F pulseaudio Date: Wed Aug 9 11:30:58 2017 Df: Dmesg: ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=6d4e0f10-12e3-4a73-86fd-25ad6f7af483 InstallationDate: Installed on 2017-08-08 (1 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 004: ID 064e:a118 Suyin Corp. Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LG Electronics A410-G.BE31P1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=95968d68-ac8e-4230-b8d6-6d81bfff617d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-4.10.0-30-generic 4.10.0-30.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2011 dmi.bios.vendor: INSYDE dmi.bios.version: QL7L3F71 dmi.board.asset.tag: Base Board Asset T
[Touch-packages] [Bug 1709621] Re: Facebook login appears broken
** Description changed: - On latest 17.10 I tried to login to facebook via online accounts. I - managed to login successfully, but now when I click the facebook icon in - online accounts it pops up a box then goes away. In addition I don't see - how I can post to facebook from other applications like shotwell. Seems - it didn't fully create. Perhaps related to gnome bug 785726 + Impact + -- + On latest 17.10 I tried to login to facebook via online accounts. I managed to login successfully, but now when I click the facebook icon in online accounts it pops up a box then goes away. In addition I don't see how I can post to facebook from other applications like shotwell. Seems it didn't fully create. + + Test Case + - + + Regression Potential + + GNOME has a standing microrelease exception for Stable Release Updates. + + https://wiki.ubuntu.com/StableReleaseUpdates#GNOME + ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 9 14:02:34 2017 InstallationDate: Installed on 2017-08-02 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-online-accounts 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 gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1709621 Title: Facebook login appears broken Status in gnome-online-accounts: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Committed Status in gnome-online-accounts source package in Xenial: Triaged Status in gnome-online-accounts source package in Zesty: Triaged Bug description: Impact -- On latest 17.10 I tried to login to facebook via online accounts. I managed to login successfully, but now when I click the facebook icon in online accounts it pops up a box then goes away. In addition I don't see how I can post to facebook from other applications like shotwell. Seems it didn't fully create. Test Case - Regression Potential GNOME has a standing microrelease exception for Stable Release Updates. https://wiki.ubuntu.com/StableReleaseUpdates#GNOME ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 9 14:02:34 2017 InstallationDate: Installed on 2017-08-02 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1709621/+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 1709621] Re: Facebook login appears broken
** Also affects: gnome-online-accounts (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gnome-online-accounts (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: gnome-online-accounts (Ubuntu Zesty) Importance: Undecided => High ** Changed in: gnome-online-accounts (Ubuntu Zesty) Status: New => Triaged ** Changed in: gnome-online-accounts (Ubuntu Xenial) Importance: Undecided => High ** Changed in: gnome-online-accounts (Ubuntu Xenial) Status: New => Triaged ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => High ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Fix Committed ** Tags added: xenial zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1709621 Title: Facebook login appears broken Status in gnome-online-accounts: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Committed Status in gnome-online-accounts source package in Xenial: Triaged Status in gnome-online-accounts source package in Zesty: Triaged Bug description: Impact -- On latest 17.10 I tried to login to facebook via online accounts. I managed to login successfully, but now when I click the facebook icon in online accounts it pops up a box then goes away. In addition I don't see how I can post to facebook from other applications like shotwell. Seems it didn't fully create. Test Case - Regression Potential GNOME has a standing microrelease exception for Stable Release Updates. https://wiki.ubuntu.com/StableReleaseUpdates#GNOME ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 9 14:02:34 2017 InstallationDate: Installed on 2017-08-02 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1709621/+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 1709621] Re: Facebook login appears broken
** Changed in: gnome-online-accounts Status: Unknown => Fix Released ** Changed in: gnome-online-accounts Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1709621 Title: Facebook login appears broken Status in gnome-online-accounts: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Committed Status in gnome-online-accounts source package in Xenial: Triaged Status in gnome-online-accounts source package in Zesty: Triaged Bug description: Impact -- On latest 17.10 I tried to login to facebook via online accounts. I managed to login successfully, but now when I click the facebook icon in online accounts it pops up a box then goes away. In addition I don't see how I can post to facebook from other applications like shotwell. Seems it didn't fully create. Test Case - Regression Potential GNOME has a standing microrelease exception for Stable Release Updates. https://wiki.ubuntu.com/StableReleaseUpdates#GNOME ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 9 14:02:34 2017 InstallationDate: Installed on 2017-08-02 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1709621/+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 1709628] [NEW] New release wayland 1.14.0
Public bug reported: Hello, New Release: https://lists.freedesktop.org/archives/wayland-devel/2017-August/034748.html Regards, -- Cristian ** Affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1709628 Title: New release wayland 1.14.0 Status in wayland package in Ubuntu: New Bug description: Hello, New Release: https://lists.freedesktop.org/archives/wayland-devel/2017-August/034748.html Regards, -- Cristian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1709628/+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 1709621] Re: Facebook login appears broken
** Bug watch added: GNOME Bug Tracker #785726 https://bugzilla.gnome.org/show_bug.cgi?id=785726 ** Also affects: gnome-online-accounts via https://bugzilla.gnome.org/show_bug.cgi?id=785726 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1709621 Title: Facebook login appears broken Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: New Bug description: On latest 17.10 I tried to login to facebook via online accounts. I managed to login successfully, but now when I click the facebook icon in online accounts it pops up a box then goes away. In addition I don't see how I can post to facebook from other applications like shotwell. Seems it didn't fully create. Perhaps related to gnome bug 785726 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 9 14:02:34 2017 InstallationDate: Installed on 2017-08-02 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1709621/+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 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)
Hi Andreas, here are my syncprov and syncrepl configurations: dn: olcOverlay={0}syncprov,olcDatabase={1}mdb,cn=config objectClass: olcOverlayConfig objectClass: olcSyncProvConfig olcOverlay: {0}syncprov olcSpCheckpoint: 5 5 dn: olcOverlay={0}syncprov,olcDatabase={2}mdb,cn=config objectClass: olcOverlayConfig objectClass: olcSyncProvConfig olcOverlay: {0}syncprov olcSpCheckpoint: 5 5 olcSyncrepl: rid=201 provider=ldap://master.example.com bindmethod=sasl timeout=0 network-timeout=0 saslmech=GSSAPI realm=EXAMPLE.COM keepalive=0 :0:0 starttls=yes tls_cert="/etc/ssl/certs/slave.pem" tls_key= "/etc/ssl/private/slave.key" tls_cacert="/etc/ssl/certs/ca-cer tificates.crt" tls_reqcert=demand tls_cipher_suite=NORMAL:-VERS-SSL3.0:-VER S-TLS-ALL:+VERS-TLS1.2:-CIPHER-ALL:-SHA1:-MD5:-RSA:+AES-256-CBC:+CAMELLIA-2 56-CBC:+AES-128-CBC:+RSA filter="(objectclass=*)" searchbase="dc=example,dc=com" s cope=sub schemachecking=off type=refreshAndPersist retry="5 10 15 +" olcSyncrepl: rid=202 provider=ldap://master.example.com bindmethod=sasl timeout=0 network-timeout=0 saslmech=GSSAPI realm=EXAMPLE.COM keepalive=0 :0:0 starttls=yes tls_cert="/etc/ssl/certs/slave.pem" tls_key= "/etc/ssl/private/slave.key" tls_cacert="/etc/ssl/certs/ca-cer tificates.crt" tls_reqcert=demand tls_cipher_suite=NORMAL:-VERS-SSL3.0:-VER S-TLS-ALL:+VERS-TLS1.2:-CIPHER-ALL:-SHA1:-MD5:-RSA:+AES-256-CBC:+CAMELLIA-2 56-CBC:+AES-128-CBC:+RSA filter="(objectclass=*)" searchbase="ou=db2" scope=sub schemachecking=off type=refreshAndPersist retry="5 10 15 +" krb5-kdc 1.13.2+dfsg-5ubuntu2 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1688575 Title: Segmentation fault on a slave slapd (sync replication with kerberos authentication) Status in openldap: Fix Committed Status in openldap package in Ubuntu: In Progress Bug description: I have a slapd problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault or 100% CPU. Maybe an useful info, I'm replicating two databases. When I deactivate syncrepl for one of them (doesn't matter which one) the problem is not occuring. Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 GDB debug: Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u openldap -g openldap -f /etc/ldap/slapd.conf -d 256 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 590c82ab @(#) $OpenLDAP: slapd (Ubuntu) (May 11 2016 16:12:05) $ buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd 590c82ab slapd starting [New Thread 0x7f2e96b7b700 (LWP 42139)] [New Thread 0x7f2e9637a700 (LWP 42140)] [New Thread 0x7f2e95b79700 (LWP 42141)] [New Thread 0x7f2e95378700 (LWP 42142)] [New Thread 0x7f2e94b77700 (LWP 42143)] 590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s failed (-6) 590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left) Thread 4 "slapd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f2e95b79700 (LWP 42141)] 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (gdb) thr apply all bt Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e94b77700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f2e95378700 (LWP 42142)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2ea59463f3 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 #2 0x7f2ea487c6ba in start_thread (arg=0x7f2e95378700) at pthread_create.c:333 #3 0x7f2ea45b282d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f2e95b79700 (LWP 42141)): #0 0x7f2ea53035b5 in sasl_client_add_plugin () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #1 0x7f2ea530f250 in ?? () from /usr/lib/x86_64-linux-gnu/libsasl2.so.2 #2 0x7f2ea5303d69 in sasl_client_in
[Touch-packages] [Bug 1544627] Re: systemd-udevd crashed with SIGABRT in __open_nocancel()
Every time I dd ISO to a USB disk systemd-udevd crashes ... Still happens on 16.04.3 with 4.10 kernel. -- 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/1544627 Title: systemd-udevd crashed with SIGABRT in __open_nocancel() Status in systemd package in Ubuntu: Confirmed Bug description: The computer was one... I was not even using it... ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: udev 228-5ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Thu Feb 11 14:59:05 2016 ExecutablePath: /lib/systemd/systemd-udevd InstallationDate: Installed on 2016-02-03 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: HP HP ZBook Studio G3 ProcCmdline: /lib/systemd/systemd-udevd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic root=UUID=a9634764-1439-45e7-a0ca-8c2d030238e6 ro quiet splash Signal: 6 SourcePackage: systemd StacktraceTop: __open_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () ?? () ?? () Title: systemd-udevd crashed with SIGABRT in __open_nocancel() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/25/2015 dmi.bios.vendor: HP dmi.bios.version: N82 Ver. 01.03 dmi.board.name: 80D4 dmi.board.vendor: HP dmi.board.version: KBC Version 11.38 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN82Ver.01.03:bd12/25/2015:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.38:cvnHP:ct10:cvr: dmi.product.name: HP ZBook Studio G3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1544627/+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 1703649] Re: Traceroute needs net_admin capability for unknown reason
How could I get comment from Systemd maintainers..? -- 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/1703649 Title: Traceroute needs net_admin capability for unknown reason Status in systemd package in Ubuntu: New Status in traceroute package in Ubuntu: New Bug description: With help of AppArmor on 17.04 and 17.10 I've discovered that traceroute needs net_admin capabilities. My plan is to update [0] AppArmor profile to fix various DENIED messages in syslog/audit for traceroute, though I am not sure about allowing, or denying, net_admin capability. Looks like traceroute tries to set SO_RCVBUFFORCE and SO_SNDBUFFORCE: setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted) setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0 setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted) setsockopt(4, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0 setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted) setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0 setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted) setsockopt(4, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0 setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted) setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0 setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted) setsockopt(4, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0 setsockopt(4, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted) setsockopt(4, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0 setsockopt(4, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted) What is interesting, that traceroute developer does not recall changing these values [1]. On Debian Sid and OpenSuse Tumbleweed this issue does not reproduce either. Could it be some Ubuntu-specific patch in the works? It seems that traceroute works OK without net_admin... Thanks! [0] https://code.launchpad.net/~talkless/apparmor/fix_traceroute_tcp/+merge/326260 [1] https://sourceforge.net/p/traceroute/mailman/message/35927818/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1703649/+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 1709621] [NEW] Facebook login appears broken
Public bug reported: On latest 17.10 I tried to login to facebook via online accounts. I managed to login successfully, but now when I click the facebook icon in online accounts it pops up a box then goes away. In addition I don't see how I can post to facebook from other applications like shotwell. Seems it didn't fully create. Perhaps related to gnome bug 785726 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 9 14:02:34 2017 InstallationDate: Installed on 2017-08-02 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1709621 Title: Facebook login appears broken Status in gnome-online-accounts package in Ubuntu: New Bug description: On latest 17.10 I tried to login to facebook via online accounts. I managed to login successfully, but now when I click the facebook icon in online accounts it pops up a box then goes away. In addition I don't see how I can post to facebook from other applications like shotwell. Seems it didn't fully create. Perhaps related to gnome bug 785726 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-online-accounts 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 9 14:02:34 2017 InstallationDate: Installed on 2017-08-02 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1709621/+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 559331] Re: Permanent "Printer-out-of-paper" message.
This bug still affects me (after 7 years?) - I can clear it using the workround of deleting the incorrect status from printers.conf but this isn't really a solution. System is Linux gryphon 4.4.0-87-generic #110-Ubuntu SMP Tue Jul 18 12:54:58 UTC 2017 i686 i686 i686 GNU/Linux Printer is a Canon MP495 operating over a wireless network. -- 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/559331 Title: Permanent "Printer-out-of-paper" message. Status in cups package in Ubuntu: Confirmed Bug description: Binary package hint: cups This probably has to do with CUPS. Version: 1.4.1- 4ubuntu2.4 (latest on Karmic). I was printing a document when the printer was out of paper and got a message that "The printer is out of paper". I went to reload it and clicked resume on the printer and printing carried on normally. From this point on, the message "The printer is out of paper" is permanently stuck on the printer. - Every time i print, i get the message "The printer is out of paper", but the printing occurs without errors. - The configuration tool (system-config-printer 1.1.12) shows the printer with the red error sign. When viewing the properties of said printer, in the "Ink/Toner Levels" section, i have the "Status Message": "Printer HP-Officejet-Pro-k550 is out of paper". If i click refresh then i get a "CUPS server error": "There was an error during the CUPS operation: 'client-error-document-format-not-supported'." (Not sure this is relevant). Removing and reinstalling the printer fixes this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/559331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1696735] Re: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt
I gave up on this one. I installed 17.04 on a new PC. Working great. John Johnson On 08/09/2017 12:17 AM, Launchpad Bug Tracker wrote: > [Expired for krb5 (Ubuntu) because there has been no activity for 60 > days.] > > ** Changed in: krb5 (Ubuntu) > Status: Incomplete => Expired > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1696735 Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in krb5 package in Ubuntu: Expired Bug description: unknown ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 8 08:22:46 2017 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-02-12 (481 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: krb5 Title: package libgssapi-krb5-2:i386 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2016-05-22 (381 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1696735/+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 1709603] Re: apt {upgrade, install} require an update call first
Some IRC discussion on this: https://irclogs.ubuntu.com/2017/08/09 /%23ubuntu-devel.html#t11:32 -- 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/1709603 Title: apt {upgrade,install} require an update call first Status in apt package in Ubuntu: Confirmed Bug description: I think that this should be tracked in its own separate bug tracking my specific UX objection to the current status quo. See https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/5, subsequent discussion and https://twitter.com/chr1sa/status/894048628284604416 We think that the updating of indexes should be an implementation detail of "apt upgrade" and "apt install", rather than something exposed to the user. If updating is judged be required (for example the index is more than X old), then it should be done automatically before the requested operation commences. Here's one proposed implementation: 1) Fix bug 1429285 ("apt-get update --if-necessary"). 2) Add an option to have "apt install" and "apt upgrade" (also "apt full-upgrade", etc?) automatically and internally call the implementation of "apt-get update --if-necessary" first. 3) Enable the option by default on Ubuntu. This would change the behaviour of "apt", which AIUI is intended to be the user focused CLI. It wouldn't change the behaviour of "apt-get", which AIUI needs to retain behavioural backwards compatibility for existing scripts. Then we could promote "apt install" and "apt upgrade" as much simpler commands to operate. Note that Julian disagreed with this proposed behaviour change in https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/7. I think that the very user-focused Ubuntu perspective should be to focus on the common use case for "apt". Hence my (compromise) suggestion that we implement this as an option upstream, and then leave it to distros to choose the default behaviour for their users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1709603/+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 1709488] Re: impossível fazer upgrade
** Information type changed from Private Security to Public -- 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/1709488 Title: impossível fazer upgrade Status in xorg package in Ubuntu: New Bug description: a atualização é sempre a mesma. Sempre se repete, mas não se efetiva ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 BootLog: Starting WPA supplicant... [[0;32m OK [0m] Started WPA supplicant. [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Aug 8 18:35:41 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651] InstallationDate: Installed on 2017-08-08 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Dell Inc. Inspiron 3542 ProcEnviron: LANGUAGE=pt_BR: TERM=xterm-256color PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic root=UUID=689bf1e6-7c78-4ddc-bfd6-07b7238d444c ro locale=pt_BR quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0P8H6J dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Aug 8 18:27:39 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1110 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1709488/+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 1709619] [NEW] When I upgrade from 14.04.5 to 16.04.3 failed with below error message GLib-CRITICAL **: g_hash_table_destroy: assertion 'hash_table != NULL' failed
Public bug reported: When I upgrade from 14.04.5 to 16.04.3 failed with below error message GLib-CRITICAL **: g_hash_table_destroy: assertion 'hash_table != NULL' failed Inspiron-3558:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty @Inspiron-3558:~$ sudo update-manager -d (update-manager:3160): GLib-CRITICAL **: g_hash_table_destroy: assertion 'hash_table != NULL' failed upgrade glib ** Affects: hud (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1709619 Title: When I upgrade from 14.04.5 to 16.04.3 failed with below error message GLib-CRITICAL **: g_hash_table_destroy: assertion 'hash_table != NULL' failed Status in hud package in Ubuntu: New Bug description: When I upgrade from 14.04.5 to 16.04.3 failed with below error message GLib-CRITICAL **: g_hash_table_destroy: assertion 'hash_table != NULL' failed Inspiron-3558:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty @Inspiron-3558:~$ sudo update-manager -d (update-manager:3160): GLib-CRITICAL **: g_hash_table_destroy: assertion 'hash_table != NULL' failed upgrade glib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1709619/+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 1709163] Re: default output changes from intel builtin to hdmi when display is turned off. yes off not on
The problem existed even before I upgraded to 17.10. but now I can not go back to that version. I think it started to happen when upgrading the kernel version. I thought that it would eventually be fixed but apparently I'm about the only one seeing this. What I do not understand is why it changes as the selected output is present all the time, and especially when I turn off a screen that has no audio associated with it. The monitor has no speakers. the only think I can think of is that the display subsystem is doing some reinit when I turn off the monitor and might remove the HDMI audio associated with the other monitor that still is on and then reinserting it. But why do pulse audio then switch over to that ?? is this some auto thing like if I put in headphones. the old GUI(unity) I could directly select sound config from the top icons. but now I have to first go to setting then sound so its even more work than before to get sound back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1709163 Title: default output changes from intel builtin to hdmi when display is turned off. yes off not on Status in pulseaudio package in Ubuntu: New Bug description: So if I have sound output selected to be the intel sound on the mainboard and turn off one of my two displays the audio out is changed to HDMI. YES OFF it's not a typo. The Display I turn off is connected to displayport and do not even have HDMI. The audio is switched over to the still active display. If I then turn the display back it's still hdmi. If I then turn off the display that has HDMI out connected. the audio is still connected to that display. since its actually off I hear no sound but pulseaudio still connect to it. I have to manually open the GUI tool and change back to the correct output when the display is turned off or when the display is blanked. or suspend/resume. I attache the output of "pacmd list-cards && pacmd list-sinks" ok -> ps_w1.txt fail -> ps_f1.txt --- ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kenjo 3721 F pulseaudio /dev/snd/controlC1: kenjo 3721 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2015-10-18 (659 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) Package: pulseaudio 1:10.0-2ubuntu1 PackageArchitecture: amd64 Tags: artful Uname: Linux 4.12.1-041201-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-06-10 (59 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.I0 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M7 (MS-7976) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.I0:bd04/25/2017:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7976 dmi.product.version: 1.0 dmi.sys.vendor: MSI modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2016-04-23T00:00:29.066742 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1709163/+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 1709603] Re: apt {upgrade, install} require an update call first
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- 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/1709603 Title: apt {upgrade,install} require an update call first Status in apt package in Ubuntu: Confirmed Bug description: I think that this should be tracked in its own separate bug tracking my specific UX objection to the current status quo. See https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/5, subsequent discussion and https://twitter.com/chr1sa/status/894048628284604416 We think that the updating of indexes should be an implementation detail of "apt upgrade" and "apt install", rather than something exposed to the user. If updating is judged be required (for example the index is more than X old), then it should be done automatically before the requested operation commences. Here's one proposed implementation: 1) Fix bug 1429285 ("apt-get update --if-necessary"). 2) Add an option to have "apt install" and "apt upgrade" (also "apt full-upgrade", etc?) automatically and internally call the implementation of "apt-get update --if-necessary" first. 3) Enable the option by default on Ubuntu. This would change the behaviour of "apt", which AIUI is intended to be the user focused CLI. It wouldn't change the behaviour of "apt-get", which AIUI needs to retain behavioural backwards compatibility for existing scripts. Then we could promote "apt install" and "apt upgrade" as much simpler commands to operate. Note that Julian disagreed with this proposed behaviour change in https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/7. I think that the very user-focused Ubuntu perspective should be to focus on the common use case for "apt". Hence my (compromise) suggestion that we implement this as an option upstream, and then leave it to distros to choose the default behaviour for their users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1709603/+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 1429285] Re: feature request: apt-get update --if-necessary
I have filed bug 1709603 to track my request of having "apt update" called automatically, as really it's independent of Scott's request for --is-necessary here. -- 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/1429285 Title: feature request: apt-get update --if-necessary Status in apt package in Ubuntu: Confirmed Bug description: In many cases (juju, lxc containers .. ) we find ourselves in the position of not knowing if the apt-cache has been udpated recently. So, you either risk not doing it, or do it and it takes some time and generates load. so long story short, you always run 'apt-get update' which is quite often unnecessary. Would it be possible to add (or is there now) something like '--if-necessary' or '--if-necessary=5m'. I could imagine that that would look at /var/lib/apt/lists and check timestamps on files for each url that /etc/apt/sources.list[.d/*] would hit. If nothing was needed and reasonably recent, then it would not do the update. There exist other solutions to this like: https://coderwall.com/p/0xtstw/doing-an-apt-get-update-in-ansible-only-if-a-condition-is-met https://blog.kumina.nl/2010/11/puppet-tipstricks-running-apt-get-update-only-when-needed/ It'd be nice if we had a sane way to say: update if you need to, otherwise don't waste time and resources ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apt 1.0.9.3ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 6 17:06:22 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-01-02 (63 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150101) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/+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 1709603] [NEW] apt {upgrade, install} require an update call first
Public bug reported: I think that this should be tracked in its own separate bug tracking my specific UX objection to the current status quo. See https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/5, subsequent discussion and https://twitter.com/chr1sa/status/894048628284604416 We think that the updating of indexes should be an implementation detail of "apt upgrade" and "apt install", rather than something exposed to the user. If updating is judged be required (for example the index is more than X old), then it should be done automatically before the requested operation commences. Here's one proposed implementation: 1) Fix bug 1429285 ("apt-get update --if-necessary"). 2) Add an option to have "apt install" and "apt upgrade" (also "apt full-upgrade", etc?) automatically and internally call the implementation of "apt-get update --if-necessary" first. 3) Enable the option by default on Ubuntu. This would change the behaviour of "apt", which AIUI is intended to be the user focused CLI. It wouldn't change the behaviour of "apt-get", which AIUI needs to retain behavioural backwards compatibility for existing scripts. Then we could promote "apt install" and "apt upgrade" as much simpler commands to operate. Note that Julian disagreed with this proposed behaviour change in https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/7. I think that the very user-focused Ubuntu perspective should be to focus on the common use case for "apt". Hence my (compromise) suggestion that we implement this as an option upstream, and then leave it to distros to choose the default behaviour for their users. ** Affects: apt (Ubuntu) Importance: Wishlist Status: New -- 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/1709603 Title: apt {upgrade,install} require an update call first Status in apt package in Ubuntu: New Bug description: I think that this should be tracked in its own separate bug tracking my specific UX objection to the current status quo. See https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/5, subsequent discussion and https://twitter.com/chr1sa/status/894048628284604416 We think that the updating of indexes should be an implementation detail of "apt upgrade" and "apt install", rather than something exposed to the user. If updating is judged be required (for example the index is more than X old), then it should be done automatically before the requested operation commences. Here's one proposed implementation: 1) Fix bug 1429285 ("apt-get update --if-necessary"). 2) Add an option to have "apt install" and "apt upgrade" (also "apt full-upgrade", etc?) automatically and internally call the implementation of "apt-get update --if-necessary" first. 3) Enable the option by default on Ubuntu. This would change the behaviour of "apt", which AIUI is intended to be the user focused CLI. It wouldn't change the behaviour of "apt-get", which AIUI needs to retain behavioural backwards compatibility for existing scripts. Then we could promote "apt install" and "apt upgrade" as much simpler commands to operate. Note that Julian disagreed with this proposed behaviour change in https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/7. I think that the very user-focused Ubuntu perspective should be to focus on the common use case for "apt". Hence my (compromise) suggestion that we implement this as an option upstream, and then leave it to distros to choose the default behaviour for their users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1709603/+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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
This bug was fixed in the package mpv - 0.26.0-3ubuntu1 --- mpv (0.26.0-3ubuntu1) artful; urgency=medium * Prefer Wayland over X11, so if both are present (e.g. Xwayland) then VA-API gets a display type that works (LP: #1698287) * Enable hardware acceleration by default (LP: #1708102) -- Daniel van Vugt Wed, 09 Aug 2017 16:38:55 +0800 ** Changed in: mpv (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 gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: New Status in Mutter: Confirmed Status in Totem: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in libva package in Ubuntu: Triaged Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+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 1579911] Re: Totem unable to play VirtualBox webm files
Yes, I am also unable to play videos. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1579911 Title: Totem unable to play VirtualBox webm files Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Totem is unable to play VirtualBox .webm Video Capture files. I have gstreamer-plugins-good, bad and ugly installed. VLC plays these files just fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.0-1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 9 13:46:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-05-09 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1579911/+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 1672960] Re: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size()
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 1.0.0 ** Changed in: mir Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1672960 Title: unity-system-compositor crashed with SIGSEGV in invoke() from mir::frontend::detail::ProtobufMessageProcessor::dispatch:on_new_message() from on_read_size() Status in Canonical System Image: Confirmed Status in Mir: Fix Committed Status in Unity System Compositor: Invalid Status in mir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.8.0+17.04.20161206-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/322176398baf670e4e9e5bb140a0aed0bbf0a00e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672960/+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 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
Actually, the snapshotting/screencasting thread could also trigger it. If that's still a thing...? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mir: Triaged Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk
** Changed in: hundredpapercuts Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1630516 Title: Logrotate doesn't clean old system logs, allowing them to fill the disk Status in One Hundred Papercuts: Fix Released Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Trusty: Fix Released Status in logrotate source package in Xenial: Fix Released Status in logrotate source package in Yakkety: Fix Released Status in logrotate source package in Zesty: Fix Released Status in logrotate package in Debian: Fix Released Bug description: [Impact] Logrotate fails to rotate a log and then will continue to fail to rotate it until manual intervention takes place. If messaging has not been configured on the system there will be no warning issued to the user. The log will grow day by day until a user intervenes or the drive that the log is stored on is full. Very large log files can make it more difficult to find useful data. Full drives make the rest of the system fail to operate. Backporting a fix would prevent drives filling up on stable releases. [Test Case] Go to your logs area (/var/logs) and create a file with a name ending .2, as would be created part way through the logrotate process. So if you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz, /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your subsequent log rotate runs will fail. [Regression Potential] - I'd hope the potential is low as it only triggers under certain conditions that are special (target filename in the way). - So far in those conditions it failed to rotate - Yet If despite my hope there still manifests an issue I'd expect it could be renaming files it should not, so people would end up "missing" their logs - the good thing is that this is a rename, so they should find it at different names. - Another thing I consider possible is that some unexpected conditions cause e.g. a crash in the changed code, in that case the logs are not rotated, but since there is no unlink the logs will still exist. - Therefore I consider the Potential low enough to consider the fix. [Other Info] n/a --- Good afternoon. I have started seeing something very similar to Debian Dug 734688 "Logs are not rotated for a month" but in the latest Ubuntu LTS (16.04). I seem to have $ logrotate --version logrotate 3.8.7 bundled in it. A few weeks ago I started getting root emails such as this: > Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/munin/munin-node.log.1: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 When I inspected the area of concern I was able to see that there was an existing .1 file. manager@warden:/var/log/munin$ ll total 580 drwxr-xr-x 2 munin adm 4096 Sep 27 06:31 ./ drwxr-xr-x 13 root syslog 4096 Oct 5 06:26 ../ -rw-r--r-- 1 root root 3440 Sep 26 13:39 munin-node-configure.log -rw-r--r-- 1 root root 490251 Oct 5 10:25 munin-node.log -rw-r--r-- 1 root root56598 Sep 21 02:01 munin-node.log.1 -rw-r--r-- 1 root root24576 Aug 31 02:01 munin-node.log.2 -rw-r--r-- 1 root root 1906 Sep 19 06:25 munin-node.log.8.gz The contents of the munin-node.log file seem to run from the 19th September until today. Unlike other parts of this bug the .1 and .2 files do not seem to be already compressed. I deleted all but the munin-node.log file to see if it would resolve the problem and was going to leave it at that. Then I noticed that I have had another Ubuntu machine which has been sending similar emails for the past week: > Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/syslog.1.gz: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 Different file, different machine but a very similar error message. Checking on the syslog file I can see that it better fits with other reports on this bug as my duplicated .1 files has a corresponding .1.gz file. manager@trac:/var/log$ ll syslog* -rw-r- 1 syslog adm 918492 Oct 5 10:30 syslog -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1 -rw-r- 1 syslog adm 20638 Oct 2 02:01 syslog.1.gz -rw-r- 1 syslog adm 41989 Sep 30 02:00 syslog.2.gz -rw-r- 1 syslog adm 18654 Sep 28 02:01 syslog.3.gz -rw-r- 1 syslog adm 31720 Sep 26 06:40 syslog.4.gz -rw-r- 1 syslog adm 33151 Sep 25 02:01 syslog.5.gz -rw-r- 1 syslog adm 17290 Sep 23 02:01 syslog.6.gz -rw-r- 1 syslog adm 39275 Sep 21 06
[Touch-packages] [Bug 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
I don't think the problem description is clear that both the Mir and Unity8 compositors are affected. (It can be read as applying to the stack including Unity8.) Thanks for clarifying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mir: Triaged Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
Update: * totem is fixed by the gst-plugins-bad fix released today. * mpv is fixed by the patch proposed in bug 1708102. * chromium needs to either be ported to native Wayland, or for libva to be enhanced with DRI3 support. There are no workarounds for Chromium other than to avoid Wayland and use Xorg sessions. * gst-play-1.0 needs an enhancement to mutter linked above, but the workaround mentioned above is also simple. ** Changed in: mutter (Ubuntu) Importance: Medium => Low ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** No longer affects: totem (Ubuntu) ** No longer affects: intel-vaapi-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: New Status in Mutter: Confirmed Status in Totem: Confirmed Status in chromium-browser package in Ubuntu: Confirmed Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in libva package in Ubuntu: Triaged Status in mpv package in Ubuntu: In Progress Status in mutter package in Ubuntu: Triaged Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+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 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
Well, yes. The problem description before that covers the fact that Mir's multi-threaded compositor manifests the problem (assuming you have multiple monitors). And comment #20 states that avoiding multiple threads (a single headed or cloned config) avoids the instability. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mir: Triaged Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
Doug, and all: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1708102/comments/3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: New Status in Mutter: Confirmed Status in Totem: Confirmed Status in chromium-browser package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in intel-vaapi-driver package in Ubuntu: Invalid Status in libva package in Ubuntu: Triaged Status in mpv package in Ubuntu: In Progress Status in mutter package in Ubuntu: Triaged Status in totem package in Ubuntu: Invalid Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+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 1553328] Re: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings
Daniel, you are saying comment #20 states that Mir's thread-per-monitor rendering manifests the problem? (I don't have any nouveau based kit to test on.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir/Unity8/USC crashes/freezes on nouveau (nv50) in pushbuf_kref() especially with multiple monitors, webbrowser-app or system settings Status in Canonical System Image: Triaged Status in Mir: Triaged Status in Nouveau Xorg driver: Unknown Status in Unity System Compositor: Triaged Status in libdrm package in Ubuntu: Triaged Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: New Status in Mutter: Confirmed Status in Totem: Confirmed Status in chromium-browser package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in intel-vaapi-driver package in Ubuntu: Invalid Status in libva package in Ubuntu: Triaged Status in mpv package in Ubuntu: In Progress Status in mutter package in Ubuntu: Triaged Status in totem package in Ubuntu: Invalid Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+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 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: New Status in Mutter: Confirmed Status in Totem: Confirmed Status in chromium-browser package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in intel-vaapi-driver package in Ubuntu: Invalid Status in libva package in Ubuntu: Triaged Status in mpv package in Ubuntu: In Progress Status in mutter package in Ubuntu: Triaged Status in totem package in Ubuntu: Invalid Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+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 1709500] Re: Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance.
Yes, I would argue many things are non-obvious and difficult to discover in Gnome. But Unity had some similar problems... Good news though - We can fix this bug by changing the colour to Ubuntu- style, avoid the garish blue/red colours, and choose something else. Everyone could be satisfied with a well-chosen colour. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1709500 Title: Headerbar buttons that are highlighted/coloured in Adwaita are not coloured at all in Ambiance. Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Using Ambiance on artful, the "action buttons" used in GtkHeaderBar are using a color similar to bar background which makes them not stand out. One example is the file-roller extract dialog, when using Adwaita the "extract" button is blue which make it an obvious click target, that's not the case under our themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1709500/+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