[Touch-packages] [Bug 1710797] [NEW] package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
Public bug reported: i am noob in ubuntu. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Aug 15 11:48:05 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2017-07-11 (34 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1710797 Title: package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: i am noob in ubuntu. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Aug 15 11:48:05 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2017-07-11 (34 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-extra-4.10.0-27-generic 4.10.0-27.30~16.04.2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1710797/+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 1710795] Re: package python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] failed to install/upgrade: package python3-proble
** Tags removed: need-duplicate-check -- 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/1710795 Title: package python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] failed to install/upgrade: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') Status in apport package in Ubuntu: New Bug description: fatal error on installing glfw ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Aug 15 11:45:02 2017 Dependencies: DuplicateSignature: Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package python3-problem-report (--configure): package python3-problem-report is not ready for configuration ErrorMessage: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-08-04 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: apport Title: package python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] failed to install/upgrade: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1710795/+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 1710795] [NEW] package python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] failed to install/upgrade: package python3-prob
Public bug reported: fatal error on installing glfw ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Aug 15 11:45:02 2017 Dependencies: DuplicateSignature: Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package python3-problem-report (--configure): package python3-problem-report is not ready for configuration ErrorMessage: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-08-04 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: apport Title: package python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] failed to install/upgrade: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1710795 Title: package python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] failed to install/upgrade: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') Status in apport package in Ubuntu: New Bug description: fatal error on installing glfw ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Aug 15 11:45:02 2017 Dependencies: DuplicateSignature: Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package python3-problem-report (--configure): package python3-problem-report is not ready for configuration ErrorMessage: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-08-04 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: apport Title: package python3-problem-report 2.20.1-0ubuntu2 [modified: usr/share/doc/python3-problem-report/changelog.Debian.gz] failed to install/upgrade: package python3-problem-report is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1710795/+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 1702823] Re: Systemd fails to serialize tasks correctly on daemon-reload
Hi you mentioned to bulk-tackle those to save some time on upload verification. Any news on this one go forward - might just need a few status updates and then SRU work? -- 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/1702823 Title: Systemd fails to serialize tasks correctly on daemon-reload Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Zesty: New Status in systemd source package in Artful: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Hi, I was initially tracking down a libvirt bug [1], but happened to realize it is actually a general systemd issue. From there I got to file, discuss and test [2]. For now I file the bug to be ablte to do my tests correctly, but if it really fixes the issue I'd like to suggest to fix it in the release - so better file upfront and do even my test patches right. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867379 [2]: https://github.com/systemd/systemd/issues/6299. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1702823/+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 1265418] Re: Gtk3 bookmark can't be removed if it points to a file
** Changed in: gtk Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1265418 Title: Gtk3 bookmark can't be removed if it points to a file Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: In the file requestor of Gtk3 you can drag files and directories to the sidebar to create bookmarks. If the user drags a file here the bookmark can never be deleted because the option is disabled. To reproduce: 1. Open a Gtk3 application such as firefox, gedit etc. 2. Open the File Open requester. 3. Drag a file to the bookmarks. 4. Right click on the file bookmark. Expected result: Should be able to click on "Remove" to remove the bookmark. Actual result: The remove option is always disabled. Workaround: Edit ~/.config/gtk-3.0/bookmarks and delete the bookmark line. Also affects trusty. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk-3-0 3.8.6-0ubuntu3.1 Uname: Linux 3.11.0-031100-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Jan 2 02:49:04 2014 InstallationDate: Installed on 2013-08-27 (127 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827) MarkForUpload: True SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1265418/+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 1710487] Re: evince silently crashes with apparmor error on artful
This bug was fixed in the package apparmor - 2.11.0-2ubuntu16 --- apparmor (2.11.0-2ubuntu16) artful; urgency=medium * add wayland-cursor.patch (LP: #1710487) -- Jamie Strandboge Mon, 14 Aug 2017 19:36:26 + ** Changed in: apparmor (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1710487 Title: evince silently crashes with apparmor error on artful Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Bug description: On an up to date Ubuntu Artful system, evince is not runnable. $ evince (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted In the syslog. [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.119:120387): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-sWj8Hz" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.147:120388): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-nEkncR" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 13 17:41:34 2017 InstallationDate: Installed on 2017-08-02 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1710487/+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 1710601] Re: bluetoothctl fails to connect
Please check to see if the bluetoothd process has gone away (crashed?) after the problem occurs. You might also want to look in /var/crash/ Please also run this command to help us get more information about your system: apport-collect 1710601 ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1710601 Title: bluetoothctl fails to connect Status in bluez package in Ubuntu: Incomplete Bug description: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Tempor
[Touch-packages] [Bug 1710762] Re: RM: obsolete product
Removal chain is: qtorganizer5-eds address-book-service indicator-transfer-buteo indicator-transfer ** Changed in: qtorganizer5-eds (Ubuntu) Importance: Undecided => Critical ** Changed in: address-book-service (Ubuntu) Importance: Undecided => High ** Changed in: indicator-transfer-buteo (Ubuntu) Importance: Undecided => Medium ** Changed in: indicator-transfer (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1710762 Title: RM: obsolete product Status in address-book-service package in Ubuntu: New Status in indicator-transfer package in Ubuntu: New Status in indicator-transfer-buteo package in Ubuntu: New Status in qtorganizer5-eds package in Ubuntu: Triaged Bug description: qtorganizer5-eds was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:qtorganizer5-eds No reverse dependencies found $ reverse-depends -b src:qtorganizer5-eds No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1710762/+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 1710762] Re: RM: obsolete product
$ check-and-remove indicator-transfer Reverse-Depends === * indicator-transfer-buteo (for libindicator-transfer0) * indicator-transfer-buteo (for indicator-transfer) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x Reverse-Build-Depends = * indicator-transfer-buteo (for libindicator-transfer-dev) xnox@sochi:~/canonical/adt$ check-and-remove indicator-transfer-buteo Reverse-Depends === * address-book-updater (for indicator-transfer-buteo) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, i386, ppc64el, s390x No reverse dependencies found xnox@sochi:~/canonical/adt$ check-and-remove address-book-updater No reverse dependencies found Reverse-Build-Depends = * qtorganizer5-eds (for evolution-data-server-utouch-dev) xnox@sochi:~/canonical/adt$ check-and-remove qtorganizer5-eds No reverse dependencies found No reverse dependencies found https://bugs.launchpad.net/bugs/1710762 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1710762 Title: RM: obsolete product Status in address-book-service package in Ubuntu: New Status in indicator-transfer package in Ubuntu: New Status in indicator-transfer-buteo package in Ubuntu: New Status in qtorganizer5-eds package in Ubuntu: Triaged Bug description: qtorganizer5-eds was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:qtorganizer5-eds No reverse dependencies found $ reverse-depends -b src:qtorganizer5-eds No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1710762/+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 1710762] [NEW] RM: obsolete product
Public bug reported: qtorganizer5-eds was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:qtorganizer5-eds No reverse dependencies found $ reverse-depends -b src:qtorganizer5-eds No reverse dependencies found ** Affects: address-book-service (Ubuntu) Importance: High Status: New ** Affects: indicator-transfer (Ubuntu) Importance: Low Status: New ** Affects: indicator-transfer-buteo (Ubuntu) Importance: Medium Status: New ** Affects: qtorganizer5-eds (Ubuntu) Importance: Critical Status: Triaged ** Tags: u8rm ** Changed in: qtorganizer5-eds (Ubuntu) Status: New => Triaged ** Also affects: address-book-service (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-transfer-buteo (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-transfer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1710762 Title: RM: obsolete product Status in address-book-service package in Ubuntu: New Status in indicator-transfer package in Ubuntu: New Status in indicator-transfer-buteo package in Ubuntu: New Status in qtorganizer5-eds package in Ubuntu: Triaged Bug description: qtorganizer5-eds was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:qtorganizer5-eds No reverse dependencies found $ reverse-depends -b src:qtorganizer5-eds No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-service/+bug/1710762/+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 1710755] [NEW] No icon in Gnome Applications for ubuntu-bug
Public bug reported: There is no easy way to launch ubuntu-bug from Gnome Shell. Typing "bug" should display it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.6-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 19:10:49 2017 InstallationDate: Installed on 2017-08-07 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1710755 Title: No icon in Gnome Applications for ubuntu-bug Status in apport package in Ubuntu: New Bug description: There is no easy way to launch ubuntu-bug from Gnome Shell. Typing "bug" should display it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.6-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 19:10:49 2017 InstallationDate: Installed on 2017-08-07 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1710755/+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 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12
I need to check with ADT infrastructure team, that recent enough lxd is in use for armhf testing that bumps inotify watch limit, and that the limit is not too low. This has been coming up before. ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) -- 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/1710654 Title: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12 Status in systemd package in Ubuntu: New Bug description: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710654/+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 1710754] [NEW] [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
Public bug reported: When I start my computer I have no sound. If I unplug my line out and plug it in again sound works fine. In Windows 10 this unplug and replug is not required (the jack is fine). Running: $ amixer -c0 contents so I can compare the non working state with the working state, the following differences exist: Non Working: numid=43,iface=CARD,name='Line Out Front Jack' ; type=BOOLEAN,access=r---,values=1 : values=off numid=35,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on Working: numid=43,iface=CARD,name='Line Out Front Jack' ; type=BOOLEAN,access=r---,values=1 : values=on numid=35,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1154 F pulseaudio /dev/snd/controlC1: scott 1154 F pulseaudio CurrentDesktop: GNOME Date: Mon Aug 14 19:05:12 2017 InstallationDate: Installed on 2017-08-07 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1154 F pulseaudio /dev/snd/controlC1: scott 1154 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1807 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7P55D DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1710754 Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: When I start my computer I have no sound. If I unplug my line out and plug it in again sound works fine. In Windows 10 this unplug and replug is not required (the jack is fine). Running: $ amixer -c0 contents so I can compare the non working state with the working state, the following differences exist: Non Working: numid=43,iface=CARD,name='Line Out Front Jack' ; type=BOOLEAN,access=r---,values=1 : values=off numid=35,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on Working: numid=43,iface=CARD,name='Line Out Front Jack' ; type=BOOLEAN,access=r---,values=1 : values=on numid=35,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1154 F pulseaudio /dev/snd/controlC1: scott 1154 F pulseaudio CurrentDesktop: GNOME Date: Mon Aug 14 19:05:12 2017 InstallationDate: Installed on 2017-08-07 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1154 F pulseaudio /dev/snd/controlC1: scott 1154 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback t
[Touch-packages] [Bug 1710752] [NEW] Intel HDA Audio doesn't work
Public bug reported: I get no sound on most boots. In Sound settings the default Output device is HDMI / DisplayPort - Built-in Audio and there is no option to select anything else. If I unplug my line out and plug it in again it shows up in the list, automatically sets itself as default and sound works fine. In Windows 10 this unplug and replug is not required (the jack is fine). Running: $ amixer -c0 contents so I can compare the non working state with the working state, the following differences exist: Non Working: numid=43,iface=CARD,name='Line Out Front Jack' ; type=BOOLEAN,access=r---,values=1 : values=off numid=35,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on Working: numid=43,iface=CARD,name='Line Out Front Jack' ; type=BOOLEAN,access=r---,values=1 : values=on numid=35,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1710752 Title: Intel HDA Audio doesn't work Status in alsa-driver package in Ubuntu: New Bug description: I get no sound on most boots. In Sound settings the default Output device is HDMI / DisplayPort - Built-in Audio and there is no option to select anything else. If I unplug my line out and plug it in again it shows up in the list, automatically sets itself as default and sound works fine. In Windows 10 this unplug and replug is not required (the jack is fine). Running: $ amixer -c0 contents so I can compare the non working state with the working state, the following differences exist: Non Working: numid=43,iface=CARD,name='Line Out Front Jack' ; type=BOOLEAN,access=r---,values=1 : values=off numid=35,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=on Working: numid=43,iface=CARD,name='Line Out Front Jack' ; type=BOOLEAN,access=r---,values=1 : values=on numid=35,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw--,values=1 : values=off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1710752/+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 1125944] Re: (gedit:3366): IBUS-WARNING **: The owner of ~/.config/ibus/bus is not root!
I solved it. gksudo nautilus go to ~/.config/ibus/bus Set up the owner, group as my user. Propietary - (user) Access - Create and delete Group - (user) Access - Access to files others - Access to files After that. The message disappeared. The error is regards to opening graphical applications with sudo. To avoid this error in the future, just replace it with gksudo. Regards. Regards -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1125944 Title: (gedit:3366): IBUS-WARNING **: The owner of ~/.config/ibus/bus is not root! Status in ibus package in Ubuntu: Won't Fix Bug description: This is "Won't Fix" because it is the symptom of a user error. As indicated repeatedly in the comments below, you should not use "sudo gedit" (or if you do, you should be able to live with this error message). The proper way to run a GUI tool with elevated privileges is with sudo -i or gksudo. Original problem description follows. RR i386 logged as gnome-classic (fallback) Seen that error for the first time while using a terminal: oem@oem-desktop:~$ sudo gedit /etc/default/grub (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root! That one is own by "Me" (screenshot joined) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ibus 1.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Fri Feb 15 08:33:36 2013 MarkForUpload: True SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1125944/+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 1710750] [NEW] session hangs on logout
Public bug reported: Every session I've tried, in 17.10 (gnome, gnome classic, gnome wayland, budgie, cinnamon, cinnamon software rending) Hangs the system when I go to log out or shutdown. sometimes it completes sometimes I have to restart lightdm from a tty. but gnome locks the session bus then and a restart is required to fix it. system is ryzen 1600x rx580 on amdgpu. I can't even find to logs, the log file viewer only holds logs since boot no previous boots. ** 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/1710750 Title: session hangs on logout Status in systemd package in Ubuntu: New Bug description: Every session I've tried, in 17.10 (gnome, gnome classic, gnome wayland, budgie, cinnamon, cinnamon software rending) Hangs the system when I go to log out or shutdown. sometimes it completes sometimes I have to restart lightdm from a tty. but gnome locks the session bus then and a restart is required to fix it. system is ryzen 1600x rx580 on amdgpu. I can't even find to logs, the log file viewer only holds logs since boot no previous boots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710750/+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 1710487] Re: evince silently crashes with apparmor error on artful
This bug was fixed in the package evince - 3.24.1-0ubuntu2 --- evince (3.24.1-0ubuntu2) artful; urgency=medium * debian/apparmor-profile.abstraction: #include (LP: #1710487) -- Jamie Strandboge Mon, 14 Aug 2017 19:38:18 + ** Changed in: evince (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1710487 Title: evince silently crashes with apparmor error on artful Status in apparmor package in Ubuntu: Fix Committed Status in evince package in Ubuntu: Fix Released Bug description: On an up to date Ubuntu Artful system, evince is not runnable. $ evince (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted In the syslog. [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.119:120387): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-sWj8Hz" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.147:120388): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-nEkncR" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 13 17:41:34 2017 InstallationDate: Installed on 2017-08-02 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1710487/+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 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start
Another posibility is to check whether there is already a crash report file. You can attach it to this bug report. These files are in the /var/crash directory and their names contain path and name of the executable file which has crashed. In your case /usr/sbin/cupsd has crashed, so the name looks like: /var/crash/_usr_sbin_cupsd.1000.crash where the number is different with each crash (probably it is the process ID of the process which has crashed). List the files with date ls -l /var/crash/*cups* and create a bug report with the newest file apport-bug /var/crash/_usr_sbin_cupsd.1000.crash or simply try whether the system automatically finds a crash report which fits to this bug: apport-collect 1706052 -- 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/1706052 Title: cupsd crashes with SIGSEGV on ubuntu 17.04 on start Status in cups package in Ubuntu: New Bug description: Hey, I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it segfaults. Attaching strace ouput. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start
Unfortunately, your gdb backtrace is touching nowhere the code of CUPS, probably due to being a sub thread which was created somewhere in the libraries. You need to get this crash registered in the Ubuntu Error Tracker. To do so, you need to follow the instructions in the crash report pop-ups. So if some window is popping up on your machine telling you that some problem has occurred, do not click it away, please follow the instructions. -- 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/1706052 Title: cupsd crashes with SIGSEGV on ubuntu 17.04 on start Status in cups package in Ubuntu: New Bug description: Hey, I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it segfaults. Attaching strace ouput. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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 1681528] Re: Include information about python versions
** Changed in: apport (Ubuntu Artful) Milestone: ubuntu-17.07 => ubuntu-17.08 -- 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/1681528 Title: Include information about python versions Status in apport package in Ubuntu: New Status in apport source package in Artful: New Bug description: We are see lots of package installation failures that look like: package:apport:2.20.3-0ubuntu8 Preparing to unpack .../023-apport_2.20.3-0ubuntu8.2_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax One explanation for this is that pyclean is actually be run by python3 instead of python2.7. To confirm and invalidate reports like this apport should check to see what /usr/bin/python and /usr/bin/python3 are symlinks to or double check the versions of /usr/bin/python and /usr/bin/python3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1681528/+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 1710715] Re: tracker 1.99.2 transition
** Changed in: tracker (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1710715 Title: tracker 1.99.2 transition Status in tracker package in Ubuntu: In Progress Status in tracker package in Debian: New Bug description: Tracker bug for tracker! GNOME 3.26 includes tracker which bumps the libraries to tracker2. Also, tracker-miners is a new source package split from the old tracker source package. I have done test rebuilds for all packages that will need to be rebuilt for this transition in the GNOME3 Staging PPA. One nice benefit of the split source packages is that I believe we will be able to sync from Debian once Debian packages the new versions. Debian packaged 1.99.1 but the split happened in 1.99.2 and the Debian maintainers haven't had time yet to handle the 1.99.2 uploads. But Ubuntu needs this before Ubuntu Feature Freeze so I'm uploading to Ubuntu now. Debian ITP bug is attached. Setting block-proposed flags because I don't want src:tracker to migrate to artful this time without src:tracker-miners. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1710715/+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 1695601] Re: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1695601 Title: IPv6 temporary/privacy addresses lifetime are not renewed upon new ICMPv6 Router-Advertisement packet Status in network-manager package in Ubuntu: Confirmed Bug description: My ISP's router provides IPv6 connectivity and advertises valid lifetime of 900 secs and preferred lifetime of 300 secs. My Ubuntu 17.04 (and previous) installation has been showing weird behavior over IPv6, with connections dropping quite often but on a regular basis. After extensive debugging and verification that there was no issue on router side, and on WiFi physical connection, I have verified that this was not related to the lack of ICMPv6 RA packets. Running |watch -d -n1 ip -6 addr show dev wlan0| shows: - decreasing valid_lft and preferred_lft on both IPv6 addresses - upon ICMPv6 RA packet received, the global SLAAC address derived from MAC gets valid_lft and preferred_lft field updated - at the same time, the privacy extension address is still decreasing System uses NetworkManager to handle all of that. I could verify that my desktop system, running Debian Sid with NetworkManager v1.6 was not exposing the issue. Running NetworkManager in debug mode gives more informations: > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7897] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 900sec pref 300sec lifetime 289-289[300,900] dev 3 flags secondary src kernel > nm_ubuntu_zesty.log:NetworkManager[2418]: [1496447074.7901] platform-linux: event-notification: NEWADDR, seq 0: 2a01:::::::39c5/64 lft 622sec pref 22sec lifetime 289-289[22,622] dev 3 flags secondary src kernel The two timestamps of the NEWADDR event are very very close. The first one shows proper update of the lifetimes values ; while the second one shows invalid values being pushed. With those informations in mind, I dug a little bit in the NetworkManager source code, and I found that there was one change between v1.4.4 (current Zesty package) and v1.6 (Debian sid package) that was touching the code handling IPv6 addresses sync: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1dbd9d7948 ; the commit states that without this change, NM might overwrite IPv6 temporary addresses changes. I took my chance and rebuilt network-manager-1.4.4 package with that patch included: IPv6 temporary privacy extensions enabled addresses gets proper updates of their lifetime when ICMPv6 packets reaches my system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1695601/+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 1710715] Re: tracker 1.99.2 transition
** Tags added: needs-packaging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1710715 Title: tracker 1.99.2 transition Status in tracker package in Ubuntu: In Progress Status in tracker package in Debian: Unknown Bug description: Tracker bug for tracker! GNOME 3.26 includes tracker which bumps the libraries to tracker2. Also, tracker-miners is a new source package split from the old tracker source package. I have done test rebuilds for all packages that will need to be rebuilt for this transition in the GNOME3 Staging PPA. One nice benefit of the split source packages is that I believe we will be able to sync from Debian once Debian packages the new versions. Debian packaged 1.99.1 but the split happened in 1.99.2 and the Debian maintainers haven't had time yet to handle the 1.99.2 uploads. But Ubuntu needs this before Ubuntu Feature Freeze so I'm uploading to Ubuntu now. Debian ITP bug is attached. Setting block-proposed flags because I don't want src:tracker to migrate to artful this time without src:tracker-miners. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1710715/+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 1710720] [NEW] some libpcre3* packages have from support timeframe set for xenial LTS
Public bug reported: Some libpcre* packages from 16.04 have the wrong support timeframe set into the package info. Therefore they are falsely shown as unsupported on the "ubuntu-support-status" output: ~$ apt show libpcre3-dbg Package: libpcre3-dbg Version: 2:8.38-3.1 Priority: optional Section: libdevel Source: pcre3 Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Matthew Vernon Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 3.514 kB Depends: libpcre3 (= 2:8.38-3.1), libpcrecpp0v5 (= 2:8.38-3.1) Supported: 9m Download-Size: 692 kB APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Description: Perl 5 Compatible Regular Expression Library - debug symbols Dies ist eine Bibliothek von Funktionen zur Unterstützung von regulären Ausdrücken, deren Syntax und Semantik so ähnlich wie möglich zu denen der Sprache Perl 5 sind. . This package contains the debug symbols, This should be set to the 5years LTS timeframe (since its in main) and not to 9months. ** Affects: pcre3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcre3 in Ubuntu. https://bugs.launchpad.net/bugs/1710720 Title: some libpcre3* packages have from support timeframe set for xenial LTS Status in pcre3 package in Ubuntu: New Bug description: Some libpcre* packages from 16.04 have the wrong support timeframe set into the package info. Therefore they are falsely shown as unsupported on the "ubuntu-support-status" output: ~$ apt show libpcre3-dbg Package: libpcre3-dbg Version: 2:8.38-3.1 Priority: optional Section: libdevel Source: pcre3 Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Matthew Vernon Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 3.514 kB Depends: libpcre3 (= 2:8.38-3.1), libpcrecpp0v5 (= 2:8.38-3.1) Supported: 9m Download-Size: 692 kB APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Description: Perl 5 Compatible Regular Expression Library - debug symbols Dies ist eine Bibliothek von Funktionen zur Unterstützung von regulären Ausdrücken, deren Syntax und Semantik so ähnlich wie möglich zu denen der Sprache Perl 5 sind. . This package contains the debug symbols, This should be set to the 5years LTS timeframe (since its in main) and not to 9months. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1710720/+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 1710719] [NEW] python-dbg and other python packages in xenial got wrong timeframe set for support time
Public bug reported: The python* packages from 16.04 have the wrong support timeframe set into the package info. Therefore they are falsely shown as unsupported on the "ubuntu-support-status" output: ~$ apt show python-dbg Package: python-dbg Version: 2.7.11-1 Priority: extra Section: python Source: python-defaults Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Matthias Klose Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 25,6 kB Depends: python (= 2.7.11-1), libpython-dbg (= 2.7.11-1), python2.7-dbg (>= 2.7.11-1~) Homepage: http://www.python.org/ Supported: 9m Download-Size: 1.252 B APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Description: Debugversion des Python-Interpreters (Version 2.7) Dieser Python-Interpreter wurde mit --pydebug konfiguriert. Dynamisch ladbare Module sucht er zuerst in /usr/lib/python2.7/lib-dynload/debug. This should be set to the 5years LTS timeframe (since its in main) and not to 9months. ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1710719 Title: python-dbg and other python packages in xenial got wrong timeframe set for support time Status in python-defaults package in Ubuntu: New Bug description: The python* packages from 16.04 have the wrong support timeframe set into the package info. Therefore they are falsely shown as unsupported on the "ubuntu-support-status" output: ~$ apt show python-dbg Package: python-dbg Version: 2.7.11-1 Priority: extra Section: python Source: python-defaults Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Matthias Klose Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 25,6 kB Depends: python (= 2.7.11-1), libpython-dbg (= 2.7.11-1), python2.7-dbg (>= 2.7.11-1~) Homepage: http://www.python.org/ Supported: 9m Download-Size: 1.252 B APT-Sources: http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Description: Debugversion des Python-Interpreters (Version 2.7) Dieser Python-Interpreter wurde mit --pydebug konfiguriert. Dynamisch ladbare Module sucht er zuerst in /usr/lib/python2.7/lib-dynload/debug. This should be set to the 5years LTS timeframe (since its in main) and not to 9months. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1710719/+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 1710715] Re: tracker 1.99.2 transition
** Description changed: Tracker bug for tracker! GNOME 3.26 includes tracker which bumps the libraries to tracker2. Also, tracker-miners is a new source package split from the old tracker source package. I have done test rebuilds for all packages that will need to be rebuilt for this transition in the GNOME3 Staging PPA. One nice benefit of the split source packages is that I believe we will be able to sync from Debian once Debian packages the new versions. Debian packaged 1.99.1 but the split happened in 1.99.2 and the Debian maintainers haven't had time yet to handle the 1.99.2 uploads. But Ubuntu needs this before Ubuntu Feature Freeze so I'm uploading to Ubuntu now. Debian ITP bug is attached. + + Setting block-proposed flags because I don't want src:tracker to migrate + to artful this time without src:tracker-miners. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1710715 Title: tracker 1.99.2 transition Status in tracker package in Ubuntu: In Progress Status in tracker package in Debian: Unknown Bug description: Tracker bug for tracker! GNOME 3.26 includes tracker which bumps the libraries to tracker2. Also, tracker-miners is a new source package split from the old tracker source package. I have done test rebuilds for all packages that will need to be rebuilt for this transition in the GNOME3 Staging PPA. One nice benefit of the split source packages is that I believe we will be able to sync from Debian once Debian packages the new versions. Debian packaged 1.99.1 but the split happened in 1.99.2 and the Debian maintainers haven't had time yet to handle the 1.99.2 uploads. But Ubuntu needs this before Ubuntu Feature Freeze so I'm uploading to Ubuntu now. Debian ITP bug is attached. Setting block-proposed flags because I don't want src:tracker to migrate to artful this time without src:tracker-miners. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1710715/+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 1710715] [NEW] tracker 1.99.2 transition
Public bug reported: Tracker bug for tracker! GNOME 3.26 includes tracker which bumps the libraries to tracker2. Also, tracker-miners is a new source package split from the old tracker source package. I have done test rebuilds for all packages that will need to be rebuilt for this transition in the GNOME3 Staging PPA. One nice benefit of the split source packages is that I believe we will be able to sync from Debian once Debian packages the new versions. Debian packaged 1.99.1 but the split happened in 1.99.2 and the Debian maintainers haven't had time yet to handle the 1.99.2 uploads. But Ubuntu needs this before Ubuntu Feature Freeze so I'm uploading to Ubuntu now. Debian ITP bug is attached. ** Affects: tracker (Ubuntu) Importance: Wishlist Status: In Progress ** Affects: tracker (Debian) Importance: Unknown Status: Unknown ** Tags: artful upgrade-software-version ** Bug watch added: Debian Bug tracker #871738 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871738 ** Also affects: tracker (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871738 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1710715 Title: tracker 1.99.2 transition Status in tracker package in Ubuntu: In Progress Status in tracker package in Debian: Unknown Bug description: Tracker bug for tracker! GNOME 3.26 includes tracker which bumps the libraries to tracker2. Also, tracker-miners is a new source package split from the old tracker source package. I have done test rebuilds for all packages that will need to be rebuilt for this transition in the GNOME3 Staging PPA. One nice benefit of the split source packages is that I believe we will be able to sync from Debian once Debian packages the new versions. Debian packaged 1.99.1 but the split happened in 1.99.2 and the Debian maintainers haven't had time yet to handle the 1.99.2 uploads. But Ubuntu needs this before Ubuntu Feature Freeze so I'm uploading to Ubuntu now. Debian ITP bug is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1710715/+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 1710487] Re: evince silently crashes with apparmor error on artful
Uploaded apparmor and evince to artful. ** Changed in: apparmor (Ubuntu) Status: Triaged => Fix Committed ** Changed in: evince (Ubuntu) Status: Triaged => Fix Committed -- 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/1710487 Title: evince silently crashes with apparmor error on artful Status in apparmor package in Ubuntu: Fix Committed Status in evince package in Ubuntu: Fix Committed Bug description: On an up to date Ubuntu Artful system, evince is not runnable. $ evince (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted In the syslog. [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.119:120387): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-sWj8Hz" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.147:120388): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-nEkncR" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 13 17:41:34 2017 InstallationDate: Installed on 2017-08-02 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1710487/+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 1710487] Re: evince silently crashes with apparmor error on artful
FYI, there are two parts to this bug: 1. apparmor in Ubuntu doesn't have the upstream fix for wayland-cursor in the wayland abstraction 2. evince doesn't include the wayland abstraction anywhere ** Also affects: evince (Ubuntu) Importance: Undecided Status: New ** Changed in: evince (Ubuntu) Status: New => Triaged ** Changed in: evince (Ubuntu) Importance: Undecided => High ** Changed in: evince (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- 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/1710487 Title: evince silently crashes with apparmor error on artful Status in apparmor package in Ubuntu: Triaged Status in evince package in Ubuntu: Triaged Bug description: On an up to date Ubuntu Artful system, evince is not runnable. $ evince (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted In the syslog. [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.119:120387): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-sWj8Hz" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.147:120388): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-nEkncR" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 13 17:41:34 2017 InstallationDate: Installed on 2017-08-02 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1710487/+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 1710694] [NEW] package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status
Public bug reported: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket util- linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) ProblemType: Package DistroRelease: Ubuntu 17.04 Package: util-linux 2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sat Aug 12 13:41:53 2017 DpkgTerminalLog: dpkg: Fehler beim Bearbeiten des Paketes util-linux (--configure): Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) ErrorMessage: Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) InstallationDate: Installed on 2017-05-13 (93 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1710694 Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) Status in util-linux package in Ubuntu: New Bug description: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) ProblemType: Package DistroRelease: Ubuntu 17.04 Package: util-linux 2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sat Aug 12 13:41:53 2017 DpkgTerminalLog: dpkg: Fehler beim Bearbeiten des Paketes util-linux (--configure): Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) ErrorMessage: Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) InstallationDate: Installed on 2017-05-13 (93 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Paket util-linux ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1710694/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
Hello I have a problem, my latop is an Asus450U has HDA Intel PCH, Chip: Realtek ALC256. I had a problem with the microphone and line No. 8 gave the solution to this, but I've found that does not recognize the two internal speakers, only works the right speaker. And in the same way does not recognize the two headphones, only recognizes the left. I have played with Alsamixer but no configuration has helped, nor the pavucontrol. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12
There are quite a few messages like these that lead me to believe where running out of inotify watches. Failed to acquire watch file descriptor: Too many open files path-exists.path: Failed to enter waiting state: Too many open 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/1710654 Title: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12 Status in systemd package in Ubuntu: New Bug description: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710654/+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 1710684] [NEW] Debian merge 2.1.27~101-g0780600+dfsg-3
Public bug reported: Please merge Debian's cyrus-sasl into ubuntu. ** Affects: cyrus-sasl2 (Ubuntu) Importance: Low Assignee: Andreas Hasenack (ahasenack) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1710684 Title: Debian merge 2.1.27~101-g0780600+dfsg-3 Status in cyrus-sasl2 package in Ubuntu: In Progress Bug description: Please merge Debian's cyrus-sasl into ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1710684/+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 1710679] Re: tracker-extract crashed with signal 31 in __GI___openat()
*** This bug is a duplicate of bug 1700062 *** https://bugs.launchpad.net/bugs/1700062 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 #1700062, 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. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1710679/+attachment/4932218/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1710679/+attachment/4932220/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1710679/+attachment/4932224/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1710679/+attachment/4932225/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1710679/+attachment/4932226/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1710679/+attachment/4932227/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1710679/+attachment/4932228/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1700062 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1710679 Title: tracker-extract crashed with signal 31 in __GI___openat() Status in tracker package in Ubuntu: New Bug description: Tracker crashed in background after a couple of minutes of high CPU usage. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: tracker-extract 1.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Aug 14 14:05:45 2017 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2017-07-27 (18 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcCmdline: /usr/lib/tracker/tracker-extract Signal: 31 SourcePackage: tracker StacktraceTop: __GI___openat (fd=21, file=0x7f6fcc0ce431 "sys", oflag=2752512) at ../sysdeps/unix/sysv/linux/wordsize-64/../openat.c:58 () at /lib/x86_64-linux-gnu/libudev.so.1 () at /lib/x86_64-linux-gnu/libudev.so.1 () at /lib/x86_64-linux-gnu/libudev.so.1 () at /lib/x86_64-linux-gnu/libudev.so.1 Title: tracker-extract crashed with signal 31 in __GI___openat() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1710679/+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 1710666] [NEW] No resolution until manually adding a nameserver to resolv.conf
Public bug reported: I have no resolution until I manually add a `nameserver 8.8.8.8` to `/run/resolvconf/resolv.conf`. And if `resolvconf` is not installed, I don't know how to add a nameserver. So I keep that installed. I'm using Network Manager and it should take care of adding nameservers. I don't know where what is going wrong. I'm willing to send any necessary info from this system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Aug 14 18:58:10 2017 InstallationDate: Installed on 2010-10-12 (2498 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-13-generic root=/dev/mapper/root ro nomdmonddf nomdmonisw nomodeset SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-04-29 (107 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X10SRA dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1710666 Title: No resolution until manually adding a nameserver to resolv.conf Status in systemd package in Ubuntu: New Bug description: I have no resolution until I manually add a `nameserver 8.8.8.8` to `/run/resolvconf/resolv.conf`. And if `resolvconf` is not installed, I don't know how to add a nameserver. So I keep that installed. I'm using Network Manager and it should take care of adding nameservers. I don't know where what is going wrong. I'm willing to send any necessary info from this system. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 233-8ubuntu3 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Aug 14 18:58:10 2017 InstallationDate: Installed on 2010-10-12 (2498 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: Supermicro X10SRA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-13-generic root=/dev/mapper/root ro nomdmonddf nomdmonisw nomodeset SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-04-29 (107 days ago) dmi.bios.date: 06/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0a:bd06/23/2016:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: X10SRA dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710666/+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 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
Yeah, xenial is where most of the snapd users are for us, so that'd certainly be desired. We wouldn't need trusty though as snapd doesn't work inside trusty containers. -- 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/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in snapd: New Status in systemd package in Ubuntu: Fix Committed Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1709536/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
Since there are multiple packages that depend on dbus-user-session, there's really no need to mention a single package in the title. ** Summary changed: - gnome-keyring not unlocked on xenial when dbus-user-session is installed, which flatpak depends on + gnome-keyring not unlocked on xenial when dbus-user-session is installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in D-Bus: New Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: New Status in flatpak package in Ubuntu: Confirmed Status in gdm package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+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 1710487] Re: evince silently crashes with apparmor error on artful
** Changed in: apparmor (Ubuntu) Status: Confirmed => Triaged ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- 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/1710487 Title: evince silently crashes with apparmor error on artful Status in apparmor package in Ubuntu: Triaged Bug description: On an up to date Ubuntu Artful system, evince is not runnable. $ evince (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted In the syslog. [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.119:120387): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-sWj8Hz" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.147:120388): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-nEkncR" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 13 17:41:34 2017 InstallationDate: Installed on 2017-08-02 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1710487/+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 1710654] Re: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12
networkd-test.py FAIL non-zero exit status 1 root-unittests FAIL non-zero exit status 1 networkd-test: == FAIL: test_catchall_config (__main__.UnmanagedClientTest) Verify link states with a catch-all config, hot-plug. -- Traceback (most recent call last): File "/tmp/autopkgtest.0R9oTG/build.WC8/systemd-233/test/networkd-test.py", line 1009, in test_catchall_config m0unm='managed') File "/tmp/autopkgtest.0R9oTG/build.WC8/systemd-233/test/networkd-test.py", line 145, in assert_link_states (iface, expected, actual)) AssertionError: Link m1man expects state managed, found unmanaged root-unittests: == test-path === path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success path-exists.service: state = dead; result = success FAIL: test-path (code: 1) Test timeout when testing path-exists.path -- 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/1710654 Title: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12 Status in systemd package in Ubuntu: New Bug description: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710654/+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 1710654] [NEW] systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12
Public bug reported: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1710654 Title: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12 Status in systemd package in Ubuntu: New Bug description: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710654/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed, which flatpak depends on
** Summary changed: - gnome-keyring not unlocked on boot + gnome-keyring not unlocked on xenial when dbus-user-session is installed, which flatpak depends on -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed, which flatpak depends on Status in D-Bus: New Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: New Status in flatpak package in Ubuntu: Confirmed Status in gdm package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+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 1710634] [NEW] Incorrect directory for (lib)krb5 plugins
Public bug reported:
The libkrb5-3 package built from the krb5 source hints at a (lib)krb5
plugin directory like this:
debian/libkrb5-3.dirs.in:usr/lib/${DEB_HOST_MULTIARCH}/krb5/plugins/krb5
debian/libkrb5-3.lintian-overrides:libkrb5-3:
package-contains-empty-directory */plugins/krb5/
The correct (lib)krb5 plugins directory, however, is:
/usr/lib/${DEB_HOST_MULTIARCH}/krb5/plugins/libkrb5
This can be verified in the krb5 source:
$ grep plugins/libkrb5 -r src
src/lib/krb5/os/locate_kdc.c: LIBDIR
"/krb5/plugins/libkrb5",
src/lib/krb5/os/locate_kdc.c:static const char *objdirs[] = { LIBDIR
"/krb5/plugins/libkrb5", NULL };
As well as in the built library:
$ strings /usr/lib/x86_64-linux-gnu/libkrb5.so.3|grep plugins
/usr/lib/x86_64-linux-gnu/krb5/plugins/authdata
/usr/lib/x86_64-linux-gnu/krb5/plugins
plugins
/usr/lib/x86_64-linux-gnu/krb5/plugins/libkrb5
This also briefly introduced a bug in the ubuntu and debian sssd packages,
which assumed .../plugins/krb5 was the correct path:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1664566
In debian it was fixed in commit e6c4e91473e75f0ddc917a24f4d561fab9900939:
commit e6c4e91473e75f0ddc917a24f4d561fab9900939
Author: Timo Aaltonen
Date: Fri Feb 17 11:22:12 2017 +0200
rules, common.install: Fix sssd_krb5_locator_plugin install path. (LP:
#1664566)
There is no immediate impact to the libkrb5-3 package itself, since MIT
kerberos does not ship any libkrb5 plugin at the moment and it is an empty
directory. It should be fixed, though, to avoid inducing similar bugs in
the future.
** Affects: krb5 (Ubuntu)
Importance: Low
Status: New
** Affects: krb5 (Debian)
Importance: Unknown
Status: Unknown
** Tags: server-next
** Bug watch added: Debian Bug tracker #872140
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872140
** Also affects: krb5 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872140
Importance: Unknown
Status: Unknown
--
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/1710634
Title:
Incorrect directory for (lib)krb5 plugins
Status in krb5 package in Ubuntu:
New
Status in krb5 package in Debian:
Unknown
Bug description:
The libkrb5-3 package built from the krb5 source hints at a (lib)krb5
plugin directory like this:
debian/libkrb5-3.dirs.in:usr/lib/${DEB_HOST_MULTIARCH}/krb5/plugins/krb5
debian/libkrb5-3.lintian-overrides:libkrb5-3:
package-contains-empty-directory */plugins/krb5/
The correct (lib)krb5 plugins directory, however, is:
/usr/lib/${DEB_HOST_MULTIARCH}/krb5/plugins/libkrb5
This can be verified in the krb5 source:
$ grep plugins/libkrb5 -r src
src/lib/krb5/os/locate_kdc.c: LIBDIR
"/krb5/plugins/libkrb5",
src/lib/krb5/os/locate_kdc.c:static const char *objdirs[] = { LIBDIR
"/krb5/plugins/libkrb5", NULL };
As well as in the built library:
$ strings /usr/lib/x86_64-linux-gnu/libkrb5.so.3|grep plugins
/usr/lib/x86_64-linux-gnu/krb5/plugins/authdata
/usr/lib/x86_64-linux-gnu/krb5/plugins
plugins
/usr/lib/x86_64-linux-gnu/krb5/plugins/libkrb5
This also briefly introduced a bug in the ubuntu and debian sssd packages,
which assumed .../plugins/krb5 was the correct path:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1664566
In debian it was fixed in commit e6c4e91473e75f0ddc917a24f4d561fab9900939:
commit e6c4e91473e75f0ddc917a24f4d561fab9900939
Author: Timo Aaltonen
Date: Fri Feb 17 11:22:12 2017 +0200
rules, common.install: Fix sssd_krb5_locator_plugin install path. (LP:
#1664566)
There is no immediate impact to the libkrb5-3 package itself, since MIT
kerberos does not ship any libkrb5 plugin at the moment and it is an empty
directory. It should be fixed, though, to avoid inducing similar bugs in
the future.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1710634/+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 1710624] Re: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN'
*** This bug is a duplicate of bug 1708947 *** https://bugs.launchpad.net/bugs/1708947 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 #1708947, 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 ** Changed in: gdebi (Ubuntu) Importance: Undecided => Medium ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1710624/+attachment/4932109/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1710624/+attachment/4932110/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 1708947 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1710624 Title: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist- packages/PyKDE4/__init__.py: No module named 'DLFCN' Status in gdebi package in Ubuntu: New Bug description: Tried to install a .deb package from X Looks like it is related to the removal of the DLFCN module from python 3.6: In the new release Python 3.6, the DLFCN is removed, see https://docs.python.org/3.6/whatsnew/3.6.html ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gdebi-kde 0.9.5.7+nmu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: LXQt Date: Mon Aug 14 15:17:19 2017 ExecutablePath: /usr/share/gdebi/gdebi-kde InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-kde /media/username/SMSNG32G/master-pdf-editor-4.2.70_qt5.amd64.deb ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=qterminal PythonArgs: ['/usr/bin/gdebi-kde', '/media/username/SMSNG32G/master-pdf-editor-4.2.70_qt5.amd64.deb'] SourcePackage: gdebi Title: gdebi-kde crashed with ModuleNotFoundError in /usr/lib/python3/dist-packages/PyKDE4/__init__.py: No module named 'DLFCN' UpgradeStatus: Upgraded to artful on 2017-06-03 (72 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1710624/+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 1710613] [NEW] package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 23
Public bug reported: None ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-services (not installed) ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Mon Aug 14 14:03:19 2017 ErrorMessage: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 232-21ubuntu5 InstallationDate: Installed on 2017-08-11 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: systemd Title: package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 232-21ubuntu5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict zesty -- 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/1710613 Title: package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 232-21ubuntu5 Status in systemd package in Ubuntu: New Bug description: None ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-services (not installed) ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Mon Aug 14 14:03:19 2017 ErrorMessage: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 232-21ubuntu5 InstallationDate: Installed on 2017-08-11 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: systemd Title: package systemd-services (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/73-seat-late.rules', which is also in package systemd 232-21ubuntu5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710613/+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 1710607] [NEW] Release 1.27.1
Public bug reported: Hello, https://git.busybox.net/busybox/tree/?h=1_27_stable Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: busybox (not installed) Uname: Linux 4.13.0-041300rc4-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 09:02:28 2017 InstallationDate: Installed on 2017-07-05 (39 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: busybox UpgradeStatus: Upgraded to artful on 2017-07-05 (39 days ago) ** Affects: busybox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1710607 Title: Release 1.27.1 Status in busybox package in Ubuntu: New Bug description: Hello, https://git.busybox.net/busybox/tree/?h=1_27_stable Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: busybox (not installed) Uname: Linux 4.13.0-041300rc4-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 09:02:28 2017 InstallationDate: Installed on 2017-07-05 (39 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: busybox UpgradeStatus: Upgraded to artful on 2017-07-05 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1710607/+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 1710609] [NEW] New release 8.27
Public bug reported: Hello, http://git.savannah.gnu.org/cgit/coreutils.git/tag/?h=v8.27 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: coreutils 8.26-3ubuntu3 Uname: Linux 4.13.0-041300rc4-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 09:08:51 2017 InstallationDate: Installed on 2017-07-05 (39 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: coreutils UpgradeStatus: Upgraded to artful on 2017-07-05 (39 days ago) ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1710609 Title: New release 8.27 Status in coreutils package in Ubuntu: New Bug description: Hello, http://git.savannah.gnu.org/cgit/coreutils.git/tag/?h=v8.27 Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: coreutils 8.26-3ubuntu3 Uname: Linux 4.13.0-041300rc4-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 09:08:51 2017 InstallationDate: Installed on 2017-07-05 (39 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: coreutils UpgradeStatus: Upgraded to artful on 2017-07-05 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1710609/+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 1710604] [NEW] New release 7.55.1
Public bug reported: Hello, https://curl.haxx.se/changes.html "Fixed in 7.55.1 - August 14 2017: Bugfixes: build: fix 'make install' with configure, install docs/libcurl/* too make install: add 8 missing man pages to the installation curl: do bounds check using a double comparison dist: Add dictserver.py/negtelnetserver.py to release digest_sspi: Don't reuse context if the user/passwd has changed gitignore: ignore top-level .vs folder build: check out *.sln files with Windows line endings travis: verify "make install" dist: fix the cmake build by shipping cmake_uninstall.cmake.in too metalink: fix error: ‘*’ in boolean context, suggest ‘&&’ instead configure: use the threaded resolver backend by default if possible mkhelp.pl: allow executing this script directly maketgz: remove old *.dist files before making the tarball openssl: remove CONST_ASN1_BIT_STRING openssl: fix "error: this statement may fall through" proxy: fix memory leak in case of invalid proxy server name curl/system.h: support more architectures (OpenRISC, ARC) docs: fix typos curl/system.h: add Oracle Solaris Studio CURLINFO_TOTAL_TIME: could wrongly return 4200 seconds docs: --connect-to clarified cmake: allow user to override CMAKE_DEBUG_POSTFIX travis: test cmake build on tarball too redirect: make it handle absolute redirects to IDN names curl/system.h: fix for gcc on PowerPC curl --interface: fixed for IPV6 unique local addresses cmake: threads detection improvements" Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: curl 7.52.1-5ubuntu1 Uname: Linux 4.13.0-041300rc4-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 08:45:48 2017 InstallationDate: Installed on 2017-07-05 (39 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: curl UpgradeStatus: Upgraded to artful on 2017-07-05 (39 days ago) ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1710604 Title: New release 7.55.1 Status in curl package in Ubuntu: New Bug description: Hello, https://curl.haxx.se/changes.html "Fixed in 7.55.1 - August 14 2017: Bugfixes: build: fix 'make install' with configure, install docs/libcurl/* too make install: add 8 missing man pages to the installation curl: do bounds check using a double comparison dist: Add dictserver.py/negtelnetserver.py to release digest_sspi: Don't reuse context if the user/passwd has changed gitignore: ignore top-level .vs folder build: check out *.sln files with Windows line endings travis: verify "make install" dist: fix the cmake build by shipping cmake_uninstall.cmake.in too metalink: fix error: ‘*’ in boolean context, suggest ‘&&’ instead configure: use the threaded resolver backend by default if possible mkhelp.pl: allow executing this script directly maketgz: remove old *.dist files before making the tarball openssl: remove CONST_ASN1_BIT_STRING openssl: fix "error: this statement may fall through" proxy: fix memory leak in case of invalid proxy server name curl/system.h: support more architectures (OpenRISC, ARC) docs: fix typos curl/system.h: add Oracle Solaris Studio CURLINFO_TOTAL_TIME: could wrongly return 4200 seconds docs: --connect-to clarified cmake: allow user to override CMAKE_DEBUG_POSTFIX travis: test cmake build on tarball too redirect: make it handle absolute redirects to IDN names curl/system.h: fix for gcc on PowerPC curl --interface: fixed for IPV6 unique local addresses cmake: threads detection improvements" Regards, -- Cristian ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: curl 7.52.1-5ubuntu1 Uname: Linux 4.13.0-041300rc4-generic x86_64 ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 08:45:48 2017 InstallationDate: Installed on 2017-07-05 (39 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: curl UpgradeStatus: Upgraded to artful on 2017-07-05 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1710604/+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 1710601] Re: bluetoothctl fails to connect
** Description changed: - bluetooth stopped working after some update, probably to bluez5 - before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI - now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: - [bluetooth]# connect A8:7E:33:FC:6D:15 + bluetooth stopped working after some update, probably to bluez5 + before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI + now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: + [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. - I found errors in logs: + I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:session)
[Touch-packages] [Bug 1710601] [NEW] bluetoothctl fails to connect
Public bug reported: bluetooth stopped working after some update, probably to bluez5 before it was working flawlessly following https://wiki.archlinux.org/index.php/Bluetooth#Configuration_via_the_CLI now $ bluetoothctl shows no typed characters, $ sudo bluetoothctl works well until I try to connect the device: [bluetooth]# connect A8:7E:33:FC:6D:15 Attempting to connect to A8:7E:33:FC:6D:15 [CHG] Device A8:7E:33:FC:6D:15 Connected: yes Failed to connect: org.bluez.Error.NotAvailable [CHG] Device A8:7E:33:FC:6D:15 Connected: no [CHG] Device A8:7E:33:FC:6D:15 RSSI: -81 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -73 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -65 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -79 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -61 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -75 [CHG] Device A8:7E:33:FC:6D:15 RSSI: -63 I am using bluez 5.37-0ubuntu5 under Ubuntu 16.04.3 LTS, updated to the day. I found errors in logs: aug 13 17:34:25 george bluetoothd[752]: Starting SDP server aug 13 17:34:26 george ModemManager[738]: ModemManager (version 1.4.12) starting in system bus... aug 13 17:34:26 george kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 aug 13 17:34:26 george kernel: Bluetooth: BNEP filters: protocol multicast aug 13 17:34:26 george kernel: Bluetooth: BNEP socket layer initialized aug 13 17:34:26 george bluetoothd[752]: Bluetooth management interface 1.10 initialized aug 13 17:34:26 george dbus[702]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.fre aug 13 17:34:26 george bluetoothd[752]: Failed to obtain handles for "Service Changed" characteristic aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Error adding Link Loss service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Current Time Service could not be registered aug 13 17:34:26 george bluetoothd[752]: gatt-time-server: Input/output error (5) aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Not enough free handles to register service aug 13 17:34:26 george bluetoothd[752]: Sap driver initialization failed. aug 13 17:34:26 george bluetoothd[752]: sap-server: Operation not permitted (1) aug 13 17:35:00 george dbus[702]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.22" (uid=100 aug 13 17:35:14 george sudo[1199]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:35:14 george sudo[1199]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:35:23 george systemd[1]: Starting Stop ureadahead data collection... aug 13 17:35:23 george systemd[1]: Started Stop ureadahead data collection. aug 13 17:35:23 george systemd[1]: Stopped Read required files in advance. aug 13 17:43:26 george sudo[1199]: pam_unix(sudo:session): session closed for user root aug 13 17:47:44 george sshd[1389]: Accepted publickey for user from 192.168.69.200 port 57812 ssh2: RSA SHA256:MQ3JEM2k/Yw2jzz aug 13 17:47:44 george sshd[1389]: pam_unix(sshd:session): session opened for user user by (uid=0) aug 13 17:47:44 george systemd-logind[742]: New session 2 of user user. aug 13 17:47:44 george systemd[1]: Started Session 2 of user user. aug 13 17:47:52 george sudo[1431]: user : TTY=pts/1 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/bluetoothctl aug 13 17:47:52 george sudo[1431]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:49:30 george /usr/lib/snapd/snapd[685]: snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd[1]: Starting Cleanup of Temporary Directories... aug 13 17:49:30 george snapd[685]: 2017/08/13 17:49:30.803962 snapmgr.go:422: No snaps to auto-refresh found aug 13 17:49:30 george systemd-tmpfiles[1459]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. aug 13 17:49:31 george systemd[1]: Started Cleanup of Temporary Directories. aug 13 17:53:16 george sudo[1520]: user : TTY=pts/0 ; PWD=/var/log ; USER=root ; COMMAND=/usr/bin/vim -R dmesg aug 13 17:53:16 george sudo[1520]: pam_unix(sudo:session): session opened for user root by user(uid=0) aug 13 17:53:18 george sudo[1520]: pam_unix(sudo:session): session closed for user root these errors are common, as you can see in comments to this bug report: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349 user@george:~$ lsmod | grep bt\\\|blue btusb 40960 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel16384 1 btusb bluetooth 479232 24 bnep,btbcm,
[Touch-packages] [Bug 458071] Re: crashes in gcompris Assertion '!in_worker(m)' failed at pulse/thread-mainloop.c:161, function pa_threaded_mainloop_stop().
** Changed in: pulseaudio (openSUSE) Status: Confirmed => Fix Released ** Changed in: pulseaudio (openSUSE) Importance: Unknown => Medium -- 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/458071 Title: crashes in gcompris Assertion '!in_worker(m)' failed at pulse/thread- mainloop.c:161, function pa_threaded_mainloop_stop(). Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio package in Debian: Fix Released Status in pulseaudio package in openSUSE: Fix Released Bug description: Binary package hint: gcompris I'm reporting crashes in gcompris, at least two different boards are crashing: The click on a fish board and the move the mouse to display a hidden picture (others not tested) . Gcompris starts but crashes after a while. I've not been able to get apport to produce sensible output, but terminal output is pasted below. Pulseaudio seems to be implicated. Let me know if there is additional information I can produce. $ gcompris XF86VidMode: Compiled with XF86VidMode. If you have problems starting GCompris in fullscreen, try the -x option to disable XF86VidMode. ** (process:4584): WARNING **: Binary relocation disabled ** (process:4584): WARNING **: exec_prefix NONE package_data_dir = /usr/share/gcompris/boards package_locale_dir = /usr/share/locale package_plugin_dir = /usr/lib/gcompris package_python_plugin_dir= /usr/share/gcompris/python Infos: Config dir '/home/james/.config/gcompris' Users dir '/home/james/My GCompris' Database '/home/james/.config/gcompris/gcompris_sqlite.db' (gcompris:4584): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed (gcompris:4584): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed (gcompris:4584): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed Assertion '!in_worker(m)' failed at pulse/thread-mainloop.c:161, function pa_threaded_mainloop_stop(). Aborting. Aborted (core dumped) ProblemType: Bug Architecture: i386 Date: Thu Oct 22 11:13:18 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gcompris 8.4.12-1ubuntu2 [modified: usr/share/applications/gcompris.desktop] ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gcompris Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/458071/+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 458071]
Seems that gstreamer-0_10-plugins-good was updated to 0.10.27 in openSUSE 11.4, which should have fixed this issue. -- 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/458071 Title: crashes in gcompris Assertion '!in_worker(m)' failed at pulse/thread- mainloop.c:161, function pa_threaded_mainloop_stop(). Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio package in Debian: Fix Released Status in pulseaudio package in openSUSE: Fix Released Bug description: Binary package hint: gcompris I'm reporting crashes in gcompris, at least two different boards are crashing: The click on a fish board and the move the mouse to display a hidden picture (others not tested) . Gcompris starts but crashes after a while. I've not been able to get apport to produce sensible output, but terminal output is pasted below. Pulseaudio seems to be implicated. Let me know if there is additional information I can produce. $ gcompris XF86VidMode: Compiled with XF86VidMode. If you have problems starting GCompris in fullscreen, try the -x option to disable XF86VidMode. ** (process:4584): WARNING **: Binary relocation disabled ** (process:4584): WARNING **: exec_prefix NONE package_data_dir = /usr/share/gcompris/boards package_locale_dir = /usr/share/locale package_plugin_dir = /usr/lib/gcompris package_python_plugin_dir= /usr/share/gcompris/python Infos: Config dir '/home/james/.config/gcompris' Users dir '/home/james/My GCompris' Database '/home/james/.config/gcompris/gcompris_sqlite.db' (gcompris:4584): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed (gcompris:4584): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed (gcompris:4584): GStreamer-CRITICAL **: gst_object_unref: assertion `((GObject *) object)->ref_count > 0' failed Assertion '!in_worker(m)' failed at pulse/thread-mainloop.c:161, function pa_threaded_mainloop_stop(). Aborting. Aborted (core dumped) ProblemType: Bug Architecture: i386 Date: Thu Oct 22 11:13:18 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gcompris 8.4.12-1ubuntu2 [modified: usr/share/applications/gcompris.desktop] ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gcompris Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/458071/+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 1710487] Re: evince silently crashes with apparmor error on artful
the patch is now named wayland-cursor.patch in Debian -- 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/1710487 Title: evince silently crashes with apparmor error on artful Status in apparmor package in Ubuntu: Confirmed Bug description: On an up to date Ubuntu Artful system, evince is not runnable. $ evince (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted In the syslog. [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.119:120387): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-sWj8Hz" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.147:120388): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-nEkncR" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 13 17:41:34 2017 InstallationDate: Installed on 2017-08-02 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1710487/+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 1710487] Re: evince silently crashes with apparmor error on artful
It looks like debian has a patch in its apparmor package for that, which is mentioned in the changelog but not in the ubuntu package, could be a merge issue? https://launchpad.net/ubuntu/+source/apparmor/2.11.0-2ubuntu1 apparmor (2.10.95-5) unstable; urgency=medium * Merge from ubuntu-citrain up to revision 1600. Remaining Debian changes: - debian/apparmor.init: don't call handle_system_policy_package_updates. * r3566-wayland.patch: new patch, to support Wayland in at least Evince (Closes: #827335). Security team, is there any reason we don't have that patch in Ubuntu or is that a merge overlook? ** Package changed: evince (Ubuntu) => apparmor (Ubuntu) -- 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/1710487 Title: evince silently crashes with apparmor error on artful Status in apparmor package in Ubuntu: Confirmed Bug description: On an up to date Ubuntu Artful system, evince is not runnable. $ evince (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted In the syslog. [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.119:120387): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-sWj8Hz" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.147:120388): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-nEkncR" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 13 17:41:34 2017 InstallationDate: Installed on 2017-08-02 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1710487/+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 1258202] Re: recent group permissions change on /var/log cause logrotate errors
Sorry, it is all my own fault. I accidentally removed su root syslog from /etc/logrotate.conf using puppet. Feel free to delete my stupid posts. -- 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/1258202 Title: recent group permissions change on /var/log cause logrotate errors Status in logrotate package in Ubuntu: Fix Released Bug description: The fix for bug #1256695 is causing logrotate to error out with: /etc/cron.daily/logrotate: error: skipping "/var/log/dpkg.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/alternatives.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/pm-suspend.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/pm-powersave.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/ppp-connect-errors" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.info" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.warn" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.err" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/daemon.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/kern.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/auth.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/user.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/lpr.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/cron.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/debug" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/messages" because parent directory has insecure permissions (It's world writable
[Touch-packages] [Bug 1710487] [NEW] evince silently crashes with apparmor error on artful
You have been subscribed to a public bug: On an up to date Ubuntu Artful system, evince is not runnable. $ evince (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White (evince:1954): Gdk-WARNING **: Failed to load cursor theme DMZ-White ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted In the syslog. [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.119:120387): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-sWj8Hz" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 [Sun Aug 13 01:58:49 2017] audit: type=1400 audit(1502642630.147:120388): apparmor="DENIED" operation="mknod" profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-nEkncR" pid=1988 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 13 17:41:34 2017 InstallationDate: Installed on 2017-08-02 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (Ubuntu) Importance: High Status: Confirmed ** Tags: amd64 apparmor apport-bug artful wayland-session -- evince silently crashes with apparmor error on artful https://bugs.launchpad.net/bugs/1710487 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor 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 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
Is SRU of this fix to e.g. xenial's systemd desired? ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-17.08 ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Fix Committed -- 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/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in snapd: New Status in systemd package in Ubuntu: Fix Committed Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1709536/+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 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
commit 5b8e457f8d883fc6f55d33d46b3474926a495d29 Author: Dimitri John Ledkov Date: Tue Aug 1 18:51:20 2017 +0100 Ignore failures to set Nice priority on services in containers. Is in artful-proposed. Also please see - https://github.com/systemd/systemd/pull/6503 which needs further work to get merged upstream. -- 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/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in snapd: New Status in systemd package in Ubuntu: Fix Committed Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1709536/+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] Re: 229 backport for race between explicit mount and handling automount
There is no time commitment for this request. -- 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 1707898] Re: systemd translations are not synced with upstream
I will require assistance to solve this. ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop) -- 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/1707898 Title: systemd translations are not synced with upstream Status in Ubuntu Translations: New Status in systemd package in Ubuntu: New Bug description: Translations for systemd are outdated because they do not seem to be synced with the upstream ones. For example the Czech one: Launchpad: https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate - 0% translated Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% translated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1707898/+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] Re: 229 backport for race between explicit mount and handling automount
When you say "we" - who do you mean? Do you per chance have Ubuntu Advantage and/or any other support contracts? If that is the case, please note, you must use UA portal to escalate issues. Please note the bug report is incomplete w.r.t. infomration of the affected systems. Please use $ ubuntu-bug systemd To collect and file complete bug reports. Nonetheless I can check the mentioned pull requests, and assess if it is applicable for an SRU. -- 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 1258202] Re: recent group permissions change on /var/log cause logrotate errors
Is adding su root syslog to /etc/logrotate.conf a good solution? -- 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/1258202 Title: recent group permissions change on /var/log cause logrotate errors Status in logrotate package in Ubuntu: Fix Released Bug description: The fix for bug #1256695 is causing logrotate to error out with: /etc/cron.daily/logrotate: error: skipping "/var/log/dpkg.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/alternatives.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/pm-suspend.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/pm-powersave.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/ppp-connect-errors" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.info" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.warn" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.err" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/daemon.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/kern.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/auth.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/user.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/lpr.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/cron.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/debug" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/messages" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to
[Touch-packages] [Bug 1708635] Re: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random
** Changed in: util-linux (Ubuntu) Status: New => Fix Committed -- 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/1708635 Title: Valgrind reports " Uninitialised value was created by a stack allocation" in __uuid_generate_random Status in util-linux package in Ubuntu: Fix Committed Bug description: This has shown up in lp:mir CI on Artful amd64 (and no other architecture or series we're using) For example: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=artful/4870/consoleFull Marking the memory with VALGRIND_MAKE_MEM_DEFINED() suppresses the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1708635/+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 1710410] Re: Must run systemd-resolve --status before DNS resolving is operative
** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Artful) Status: New => Fix Committed ** Changed in: systemd (Ubuntu Zesty) Status: New => Triaged ** Changed in: systemd (Ubuntu Zesty) Importance: Undecided => High ** Changed in: systemd (Ubuntu Artful) Importance: Undecided => High ** Changed in: systemd (Ubuntu Artful) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu Zesty) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu Zesty) Milestone: None => zesty-updates -- 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/1710410 Title: Must run systemd-resolve --status before DNS resolving is operative Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Zesty: Triaged Status in systemd source package in Artful: Fix Committed Bug description: Context: fresh install of zesty via debootstrap --include=nano,dbus,iputils-ping,iproute2 zesty zesty1 http://fr.archive.ubuntu.com/ubuntu ran via asystemd-nspawn with a static IP 1. Upon first connexion, a ping fails: root@zesty1:~# ping google.com ping: google.com: Temporary failure in name resolution 2. The content of /etc/resolv.conf: root@zesty1:~# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. 3. When running systemd-resolve --status: root@zesty1:~# systemd-resolve --status Global DNS Servers: 8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa (...) 4. After running this command the resolution is miraculously restored: root@zesty1:~# ping google.com PING google.com (172.217.22.142) 56(84) bytes of data. 64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=1 ttl=53 time=2.62 ms 64 bytes from 172.217.22.142 (172.217.22.142): icmp_seq=2 ttl=53 time=1.93 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710410/+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 1258202] Re: recent group permissions change on /var/log cause logrotate errors
I am seeing this problem with several Ubuntu 16.04.3 LTS server installations. considering log /var/log/btmp error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. # ll -d /var/log/ drwxrwxr-x 17 root syslog 4096 Aug 13 21:31 /var/log// -- 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/1258202 Title: recent group permissions change on /var/log cause logrotate errors Status in logrotate package in Ubuntu: Fix Released Bug description: The fix for bug #1256695 is causing logrotate to error out with: /etc/cron.daily/logrotate: error: skipping "/var/log/dpkg.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/alternatives.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/pm-suspend.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/pm-powersave.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/ppp-connect-errors" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.info" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.warn" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.err" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/mail.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/daemon.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/kern.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/auth.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/user.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/lpr.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/cron.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/debug" because parent directory has insecure p
[Touch-packages] [Bug 1698795] Re: Humanity should provide symbolic versions of custom icons for GNOME Shell
This bug was fixed in the package gnome-shell - 3.24.3-0ubuntu2 --- gnome-shell (3.24.3-0ubuntu2) artful; urgency=medium * Ship ubuntu GNOME Shell mode which will be a slightely modified mode compared to upstream vanilla GNOME Shell one: reference a cutomized ubuntu.css, with some based rules changes from the upstream one, like default font, no symbolic icon in the appmenu for coherence with other set of icons not having symbolic ones. We use regexp rules based on the source shell css, so that it's always in sync with shell theming on any update. (LP: #1698795) * Dropped debian/patches/ubuntu_font.patch, not needed anymore as we will have our own theme. * debian/patches/ubuntu_gdm.patch: as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. * Bump Standard-Version to latest * Remove debian/gnome-shell.gsettings-override, as this is now in ubuntu-settings, and we will have per-session overrides there. -- Didier Roche Mon, 14 Aug 2017 09:03:41 +0200 ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- 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/1698795 Title: Humanity should provide symbolic versions of custom icons for GNOME Shell Status in Ubuntu theme: New Status in gnome-shell package in Ubuntu: Fix Released Status in humanity-icon-theme package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: The app icon in top panel next to application menu entry is the default adwaita icons and don't match the current theming. It's either: - the fact that we don't provide the correct icon size in our themes, and so, the icons are defaulted - a bug in G-S To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1698795/+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 1194188] Re: When using UOA, it's impossible to add any gmail-based account on Evolution
** Changed in: evolution-data-server Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1194188 Title: When using UOA, it's impossible to add any gmail-based account on Evolution Status in evolution-data-server: Expired Status in evolution-data-server package in Ubuntu: Triaged Bug description: I'm using Ubuntu Online Accounts in my system, but if I try to configure a new gmail-based account through the Evolution accounts wizard, at the end of the process, nothing happens: evolution doesn't show my new account, and UOA is not asking for the credentials (only the evolution configuration files mention it). The only way I've found to use a gmail account (both with gmail.com and a custom domain) in evolution is to configure it from UOA g-c-c panel. I think that Evolution should at least notify the user that it's impossible to add a such account, instead of just failing silently. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evolution-data-server-uoa 3.8.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Mon Jun 24 18:14:53 2013 InstallationDate: Installed on 2010-07-10 (1080 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True SourcePackage: evolution-data-server UpgradeStatus: Upgraded to saucy on 2012-10-10 (257 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1194188/+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 1706052] Re: cupsd crashes with SIGSEGV on ubuntu 17.04 on start
Hey, I updated the bug report, can you please update it and change it from incomplete? ** Changed in: cups (Ubuntu) Status: Incomplete => Opinion ** Changed in: cups (Ubuntu) Status: Opinion => Incomplete ** Changed in: cups (Ubuntu) Status: Incomplete => New -- 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/1706052 Title: cupsd crashes with SIGSEGV on ubuntu 17.04 on start Status in cups package in Ubuntu: New Bug description: Hey, I upgraded to Ubuntu 17.04, but CUPS crashes on boot, and when I run cupsd it segfaults. Attaching strace ouput. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1706052/+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 1355137] Re: gtk2 theme version improvements for high-dpi screens
The attached files were not submitted as a full patch that solves the problem how to switch between non-hidpi and hidpi systems, but just pointing to the spots where the problematic gtk2 widgets can be multiplied in size. If it is possible to have a switch in gtkrc, someone with gtk2 theming experience (design team?) would need to take a look. -- 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/1355137 Title: gtk2 theme version improvements for high-dpi screens Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: GTK2 applications are still widespread and the lack of resolution independence poses significant usability problems, for example for clicking radio buttons or checkboxes. By editing the gtkrc file one can at least mitigate a majority of issues. By doubling dimensions (like widths, heights, not border- widths), the following controls can be made usable: radio buttons, checkboxes, scrollbars, expand/collapse triangles in trees. While this is nothing like complete high-dpi support, still a significant partial improvement can be achieved. Users of high-dpi screens should not have to suffer under the current default, or have to patch the theme manually. It would be good to implement a way that when the scaling factor is >= 2.0, as many GTK 2 widgets as possible are rendered with larger dimensions, be it by theme engine or by switching the theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1355137/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Trusty) 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/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in systemd package in Ubuntu: Confirmed Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd source package in Trusty: Confirmed Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1252121/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
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/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in systemd package in Ubuntu: Confirmed Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd source package in Trusty: Confirmed Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1252121/+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 841366] Re: jockey-backend crashed with TypeError in pulse_items(): an integer is required
** Attachment removed: "64DC18CFB4B242EF.jpg" https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/841366/+attachment/4925616/+files/64DC18CFB4B242EF.jpg ** Attachment removed: "13E3BE819B3D041E.jpg" https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/841366/+attachment/4925670/+files/13E3BE819B3D041E.jpg ** Attachment removed: "E73D803B2D53D4F4.jpg" https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/841366/+attachment/4927678/+files/E73D803B2D53D4F4.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/841366 Title: jockey-backend crashed with TypeError in pulse_items(): an integer is required Status in python-apt package in Ubuntu: Fix Released Bug description: I get this error when I open software to install proprietary drivers for my nvidia video adapter. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: jockey-common 0.9.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) Date: Sun Sep 4 23:19:51 2011 ExecutablePath: /usr/share/jockey/jockey-backend InterpreterPath: /usr/bin/python2.7 MachineType: To be filled by O.E.M. To be filled by O.E.M. PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l /var/log/jockey.log ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=81c8ea82-fbcf-49f1-b7a5-fc8c37d6c4ee ro quiet splash vt.handoff=7 PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l', '/var/log/jockey.log'] SourcePackage: jockey Title: jockey-backend crashed with TypeError in pulse_items(): an integer is required Traceback: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/apt/progress/old.py", line 121, in pulse_items if self.currentCPS > 0: TypeError: an integer is required UpgradeStatus: Upgraded to oneiric on 2011-09-04 (0 days ago) UserGroups: dmi.bios.date: 06/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Crosshair V Formula dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd06/22/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnCrosshairVFormula:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/841366/+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
