[Touch-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
Same issue with evince 43.0-1 and apparmor 3.0.7-1ubuntu2 on cinnamon 5.4.12-1 from Ubuntu 22.10 (Kinetic Kudu) The apparmor workaround provided by Karsten has to be updated : Inside '/etc/apparmor.d/usr.bin.evince', add following line after the line containing 'thunar' : /usr/lib/x86_64-linux-gnu/libproxy/0.4.18/pxgsettings Cx -> sanitized_helper, # Print Dialog This updated workaround works for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
** Tags added: kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
With evince 42.3-0ubuntu2 and apparmor 3.0.4-2ubuntu2.1 on cinnamon 5.2.7-4 from Ubuntu 22.04 (Jammy Jellyfish) : - The 'at-spi/bus' issue is fixed. - The print issue is NOT fixed yet, but Karsten's workaround inside apparmor still works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
Thanks to Sebastien Bacher for his selective fix proposal (delete the 'deny dbus send' section in '/etc/apparmor.d/abstractions/exo-open'). $ sudo apparmor_parser -r /etc/apparmor.d/abstractions/exo-open fails with error message 'AppArmor parser error for /etc/apparmor.d/abstractions/exo-open in profile /etc/apparmor.d/abstractions/dri-common at line 8: syntax error, unexpected TOK_MODE, expecting TOK_OPEN' But following command succeeds : $ sudo systemctl restart apparmor Then evince remembers last page, window size and side pane. -- 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/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in apparmor package in Ubuntu: New Status in evince package in Ubuntu: In Progress Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
Thanks Alberto : Re-enabling the snapd.apparmor service has fixed my issue. Therefore, I have migrated my issue to a contribution to https://bugs.launchpad.net/snapd/+bug/1806135 -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
** Tags removed: jammy -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
$ systemctl status snapd.apparmor ○ snapd.apparmor.service - Load AppArmor profiles managed internally by snapd Loaded: loaded (/lib/systemd/system/snapd.apparmor.service; disabled; vendor preset: enabled) Active: inactive (dead) I do NOT remember having manually disabled this service. -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
Inside the attached journal for the 'apparmor.service' unit, I do NOT understand at all which "DENIED" messages are normal and which are abnormal. For independent reasons, I would like to keep my machine running for several days (or weeks). But after I reboot, and before running the apparmor_parser command, I will attach the output of following commands : $ SNAPD_DEBUG=1 firefox $ journalctl -b ** Attachment added: "journalctl-apparmor.service-sirius-2022-05-23.log" https://bugs.launchpad.net/apparmor/+bug/1871148/+attachment/5592394/+files/journalctl-apparmor.service-sirius-2022-05-23.log -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
Yes, on the slower machine (where I am seeing this issue), I will NOT be able to start firefox until I have run that apparmor_parser command. Not even if I try starting firefox well after the login. $ ls -l /etc/apparmor.d/disable total 0 lrwxrwxrwx. 1 root root 31 août 27 2019 usr.bin.firefox -> /etc/apparmor.d/usr.bin.firefox lrwxrwxrwx. 1 root root 33 août 27 2019 usr.sbin.rsyslogd -> /etc/apparmor.d/usr.sbin.rsyslogd $ ls -l /etc/apparmor.d/usr.bin.firefox -rw-r--r-- 1 root root 9186 déc. 1 10:22 /etc/apparmor.d/usr.bin.firefox I do NOT know at all if '/etc/apparmor.d/disable/usr.bin.firefox' is useful or harmful. ** Attachment added: "systemctl-status-apparmor-sirius-2022-05-17.log" https://bugs.launchpad.net/apparmor/+bug/1871148/+attachment/5592390/+files/systemctl-status-apparmor-sirius-2022-05-17.log -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
** Attachment added: "systemd-analyze-plot-sirius-2022-05-18.svg" https://bugs.launchpad.net/apparmor/+bug/1871148/+attachment/5590993/+files/systemd-analyze-plot-sirius-2022-05-18.svg -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
The issue that I am seeing is exactly the one explained in the bug description. More precisely, on my slower machine, each time I start firefox (which is now a snap) from a terminal, following error message is displayed : cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1 Workaround : After each reboot : $ sudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/* I did NOT find 'snap.firefox.service', but I attach the output of following command : $ systemctl list-dependencies --after snap-firefox-1351.mount ** Attachment added: "systemctl_list-dependencies_--after_snap-firefox-1351.mount.log" https://bugs.launchpad.net/apparmor/+bug/1871148/+attachment/5590992/+files/systemctl_list-dependencies_--after_snap-firefox-1351.mount.log -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
With snapd 2.55.3+22.04ubuntu1 and apparmor 3.0.4-2ubuntu2 from Ubuntu 22.04 (Jammy Jellyfish) : - On a machine with a powerful i7-7700 HQ processor, the issue did NOT appear yet. - On a machine with the slower AMD FX-8370E processor, the issue occurs systematically after each reboot. $ sudo systemd-analyze critical-chain apparmor.service snapd.service apparmor.service +396ms └─local-fs.target @3.660s snapd.service +529ms └─basic.target @4.509s └─sockets.target @4.509s └─snapd.socket @4.505s +3ms └─sysinit.target @4.307s └─systemd-timesyncd.service @3.813s +494ms └─systemd-tmpfiles-setup.service @3.726s +77ms └─local-fs.target @3.660s Workaround : After each reboot : $ sudo apparmor_parser -r /var/lib/snapd/apparmor/profiles/* -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded
** Tags added: jammy -- 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/1871148 Title: services start before apparmor profiles are loaded Status in AppArmor: Invalid Status in snapd: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Invalid Status in apparmor source package in Focal: Fix Released Status in snapd source package in Focal: Fix Released Status in zsys source package in Focal: Invalid Bug description: Per discussion with Zyga in #snapd on Freenode, I have hit a race condition where services are being started by the system before apparmor has been started. I have a complete log of my system showing the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/. Restarting apparmor using `sudo systemctl restart apparmor` is enough to bring installed snaps back to full functionality. Previously, when running any snap I would receive the following in the terminal: --- cannot change profile for the next exec call: No such file or directory snap-update-ns failed with code 1: File exists --- Updated to add for Jamie: $ snap version snap2.44.2+20.04 snapd 2.44.2+20.04 series 16 ubuntu 20.04 kernel 5.4.0-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
Same issue with evince 42.1-3 and apparmor 3.0.4-2ubuntu2 on cinnamon 5.2.7-4 from Ubuntu 22.04 (Jammy Jellyfish) The apparmor workaround fixes it for me. Thanks Karsten. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Confirmed Status in libproxy package in Ubuntu: Confirmed Status in evince package in Debian: New Bug description: audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
Inside Ubuntu 20.10 (Groovy Gorilla), I just tested with systemd versions 246.6-1ubuntu1 and 246.6-1ubuntu1.1 : The issue has disappeared; umask is correct under gnome-terminal. So, I remove the 'groovy' tag. ** Tags removed: groovy -- 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/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: Invalid Status in GNOME Terminal: Confirmed Status in Nautilus: Invalid Status in systemd: Unknown Status in dbus package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Bionic: Invalid Status in gnome-terminal source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Bug description: [impact] pam_umask, from /etc/passwd, is not honored in systemd --user instances [test case] on a desktop system, edit /etc/passwd to change the test user entry (e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th field). For example change: ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash to: ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash You may need to reboot for your X session to pick up the change. Then, from the graphical desktop, open a terminal and run: $ gnome-terminal -e sh in the opened terminal, run: $ umask the number shown should be 0007, as set in the passwd file [regression potential] any regression would likely result in an incorrect umask for the user whose passwd entry is modified. [scope] this is needed only for b this is fixed in systemd upstream by commit 5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in v246, so this is fixed in g and later. This commit was also picked up by Debian and included in the v245 release for focal, so this is fixed in focal already. [original description] In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685754] Re: 'systemd --user' unduly forces umask=0022
REGRESSION: With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy Gorilla), the issue had reappeared ** Tags added: groovy -- 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/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: Invalid Status in GNOME Terminal: Confirmed Status in Nautilus: Invalid Status in systemd: Unknown Status in dbus package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Bionic: Invalid Status in gnome-terminal source package in Bionic: Invalid Status in systemd source package in Bionic: Confirmed Bug description: In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
With systemd version 245.2-1ubuntu2 from Ubuntu 20.04 Beta (Focal Fossa), the issue is still the same. ** Tags added: eoan focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: New Status in GNOME Terminal: Confirmed Status in Nautilus: Confirmed Status in dbus package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Bug description: In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Sven, here are the workaround steps (as root) : 1) Create the folder '/etc/systemd/user/gnome-terminal-server.service.d' (with usual mode 755). 2) In this newly created folder, create the 'umask.conf' file with following content : [Service] UMask= -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: New Status in GNOME Terminal: Confirmed Status in Nautilus: Confirmed Status in dbus package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Bug description: In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
In order that gnome-terminal starts with the correct umask : Lot of thanks to Olivier JOLY for comment #27 : His workaround is effective. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: New Status in GNOME Terminal: Confirmed Status in Nautilus: Confirmed Status in dbus package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Bug description: In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
Currently, the upstream issue has NOT been migrated to GNOME GitLab yet, but is still being tracked at https://bugzilla.gnome.org/show_bug.cgi?id=780622 ** Bug watch added: bugzilla.gnome.org/ #780622 https://bugzilla.gnome.org/show_bug.cgi?id=780622 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: New Status in GNOME Terminal: Confirmed Status in Nautilus: Confirmed Status in dbus package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Bug description: In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1571195] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
*** This bug is a duplicate of bug 1550124 *** https://bugs.launchpad.net/bugs/1550124 ** This bug has been marked a duplicate of bug 1550124 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1571195 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo- progs 1.3.0-0ubuntu2 Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg8-empty package in Ubuntu: Confirmed Bug description: apt-cache policy libjpeg-progs libjpeg-progs: Installed: 8c-2ubuntu8 Candidate: 1:9b-1 Version table: 1:9b-1 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages *** 8c-2ubuntu8 100 100 /var/lib/dpkg/status Description: Ubuntu 16.04 LTS Release: 16.04 Codename: xenial ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 16 15:36:52 2016 ErrorMessage: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2014-10-21 (542 days ago) InstallationMedia: RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-04-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1571195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528195] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que também está no pacote libjpeg-turbo-progs
*** This bug is a duplicate of bug 1550124 *** https://bugs.launchpad.net/bugs/1550124 ** This bug is no longer a duplicate of bug 1571195 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ** This bug has been marked a duplicate of bug 1550124 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1528195 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: Confirmed Bug description: Não sei... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 Date: Mon Dec 21 09:57:10 2015 ErrorMessage: a tentar sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2015-10-30 (51 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151027) RelatedPackageVersions: dpkg 1.18.3ubuntu1 apt 1.1.5 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/share/man/man1/djpeg.1.gz', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1528195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1571351] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0-0
*** This bug is a duplicate of bug 1550124 *** https://bugs.launchpad.net/bugs/1550124 ** This bug is no longer a duplicate of bug 1571195 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ** This bug has been marked a duplicate of bug 1550124 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1571351 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: New Bug description: desconozco el error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 17 12:13:18 2016 ErrorMessage: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2015-06-25 (296 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-04-15 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1571351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1557361] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-turbo-progs 1.3.0-0ubuntu2
*** This bug is a duplicate of bug 1550124 *** https://bugs.launchpad.net/bugs/1550124 ** This bug is no longer a duplicate of bug 1571195 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ** This bug has been marked a duplicate of bug 1550124 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1557361 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg- turbo-progs 1.3.0-0ubuntu2 ist Status in libjpeg8-empty package in Ubuntu: Confirmed Bug description: This is on a developer version of xenial. $ sudo apt-cache policy libjpeg-progs libjpeg-progs: Installiert: 8c-2ubuntu8 Installationskandidat: 1:9b-1 Versionstabelle: 1:9b-1 500 500 http://ftp.uni-stuttgart.de/ubuntu xenial/universe amd64 Packages *** 8c-2ubuntu8 100 100 /var/lib/dpkg/status What was expected? an upgrade or dist-upgrade should run to completion without errors What happened instead? $ sudo apt-get upgrade (...) Error: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Mar 14 22:58:05 2016 ErrorMessage: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-turbo-progs 1.3.0-0ubuntu2 ist InstallationDate: Installed on 2015-01-26 (413 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.6 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: Versuch, »/usr/bin/rdjpgcom« zu überschreiben, welches auch in Paket libjpeg-turbo-progs 1.3.0-0ubuntu2 ist UpgradeStatus: Upgraded to xenial on 2016-03-05 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1557361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516242] Re: dpkg: error al procesar el archivo /var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack): intentando sobreescribir `/usr/share/man/man1/djpeg.1
*** This bug is a duplicate of bug 1550124 *** https://bugs.launchpad.net/bugs/1550124 ** This bug is no longer a duplicate of bug 1571195 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ** This bug has been marked a duplicate of bug 1550124 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1516242 Title: dpkg: error al procesar el archivo /var/cache/apt/archives/libjpeg- progs_1%3a9a-2ubuntu1_amd64.deb (--unpack): intentando sobreescribir `/usr/share/man/man1/djpeg.1.gz', que está también en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: New Bug description: the mfollowing line appears when trying to upgrade dpkg: error al procesar el archivo /var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack): intentando sobreescribir `/usr/share/man/man1/djpeg.1.gz', que está también en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.2.0-19.23-lowlatency 4.2.6 Uname: Linux 4.2.0-19-lowlatency x86_64 ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Sat Nov 14 14:25:34 2015 InstallationDate: Installed on 2012-02-27 (1355 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: libjpeg8-empty UpgradeStatus: Upgraded to xenial on 2015-11-08 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1516242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573586] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
*** This bug is a duplicate of bug 1550124 *** https://bugs.launchpad.net/bugs/1550124 ** This bug is no longer a duplicate of bug 1571195 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ** This bug has been marked a duplicate of bug 1550124 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1573586 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo- progs 1.3.0-0ubuntu2 Status in One Hundred Papercuts: Confirmed Status in libjpeg8-empty package in Ubuntu: Confirmed Bug description: The GUI upgrade crashed because of LP: #1573558. I resumed with apt-get install -f apt-get dist-upgrade and got this error in the middle of the dist-upgrade. It's probably a duplicate of LP: #1571195. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 22 15:36:57 2016 ErrorMessage: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2012-07-25 (1366 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1573586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577261] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentando sobrescrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2
*** This bug is a duplicate of bug 1550124 *** https://bugs.launchpad.net/bugs/1550124 ** This bug is no longer a duplicate of bug 1571195 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ** This bug has been marked a duplicate of bug 1550124 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1577261 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentando sobrescrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg- turbo-progs 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: New Bug description: Este erro aparece sempre que atualizo o sistema, mesmo quando removo o pacote do cache do apt ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Sun May 1 22:00:49 2016 ErrorMessage: tentando sobrescrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2014-11-03 (545 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentando sobrescrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1577261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576937] Re: trying to overwrite '/usr/bin/rdjpgcom'
*** This bug is a duplicate of bug 1550124 *** https://bugs.launchpad.net/bugs/1550124 ** This bug is no longer a duplicate of bug 1571195 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ** This bug has been marked a duplicate of bug 1550124 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1576937 Title: trying to overwrite '/usr/bin/rdjpgcom' Status in libjpeg-turbo package in Ubuntu: New Status in libjpeg9 package in Ubuntu: New Bug description: Seen while upgrading from trusty to xenial: Unpacking libjpeg-progs (1:9b-1) over (8c-2ubuntu8) ... dpkg: error processing archive /mnt/ubuntu/pool/universe/libj/libjpeg9/libjpeg-progs_9b-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 Errors were encountered while processing: /mnt/ubuntu/pool/universe/libj/libjpeg9/libjpeg-progs_9b-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo-progs 1.3.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 30 00:43:24 2016 InstallationDate: Installed on 2012-10-18 (1290 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: libjpeg-turbo UpgradeStatus: Upgraded to xenial on 2016-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1576937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1649210] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentata sovrascrittura di "/usr/bin/rdjpgcom" presente anche nel pacchetto libjpeg-turbo-progs 1.3.0-0ub
*** This bug is a duplicate of bug 1550124 *** https://bugs.launchpad.net/bugs/1550124 ** This bug is no longer a duplicate of bug 1571195 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ** This bug has been marked a duplicate of bug 1550124 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1649210 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentata sovrascrittura di "/usr/bin/rdjpgcom" presente anche nel pacchetto libjpeg-turbo-progs 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: New Bug description: Ubuntu 16.04.1 LTS libjpeg-progs 8c-2ubuntu8 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 8 08:47:23 2016 ErrorMessage: tentata sovrascrittura di "/usr/bin/rdjpgcom" presente anche nel pacchetto libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2015-02-14 (666 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: tentata sovrascrittura di "/usr/bin/rdjpgcom" presente anche nel pacchetto libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-07-12 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1649210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638348] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu
*** This bug is a duplicate of bug 1550124 *** https://bugs.launchpad.net/bugs/1550124 ** This bug is no longer a duplicate of bug 1571195 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 ** This bug has been marked a duplicate of bug 1550124 package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.4.2-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1638348 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg- turbo-progs 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: New Bug description: No details available ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 Date: Tue Nov 1 15:05:03 2016 ErrorMessage: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: a tentar sobre-escrever '/usr/bin/rdjpgcom', que também está no pacote libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-09-21 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1638348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction
With 'systemd' version 237-3ubuntu7 from Ubuntu 18.04 Bionic Beta2 : - The 'pm-utils' package is NOT installed by default, and 'systemd' does NOT systematically suspend my computer 2mn after the last opened user session has been closed. - After manual installation of the 'pm-utils' package, 'systemd' DID suspend my computer 2mn after the last opened user session has been closed. I have to perform further tests to check if the good behavior of 'systemd' systematically comes from the presence of the 'pm-utils' package. ** Tags added: artful bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1504254 Title: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I want my computer to suspend when there is NO opened user session. So, I have activated following lines inside '/etc/systemd/logind.conf' : IdleAction=suspend IdleActionSec=15min - Systematically , under Ubuntu Vivid (15.04), this works correctly : During user interaction, the computer does NOT automatically suspend, but stays continuously alive. Once all users have closed their session, the computer automatically suspends after 15 min. - But systematically , under Ubuntu Wily (15.10 beta2), the computer automatically suspends after 15 min EVEN during user interaction. Hitting the keyboard makes the computer resume without data loss, but this is still annoying. In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must systematically be inhibited during user interaction. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z_admin1665 F pulseaudio /dev/snd/controlC1: z_admin1665 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 8 19:26:59 2015 HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140 InstallationDate: Installed on 2015-09-27 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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/systemd/+bug/1504254/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669517] Re: apt-key del must absolutely detect all errors, and then provide NON-zero return code and error message
In package 'apt' 1.6~beta1 from Kubuntu Bionic Beaver Beta1 (18.04) : - The 'apt-key' command is still present, - 'apt-key del' still does NOT detect that the keyid given in parameter is invalid : It still erroneously displays 'OK' and provides a return code equal to zero. ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1669517 Title: apt-key del must absolutely detect all errors, and then provide NON- zero return code and error message Status in apt package in Ubuntu: Triaged Bug description: Currently, 'apt-key del' does NOT detect that the keyid given in parameter is invalid : It displays 'OK' and provides a return code equal to zero (see log below). I consider that letting erroneously believe that a GPG key has been successfully removed is a security issue. In fact 'apt-key del' must absolutely detect all errors, and then provide NON-zero return code and error message. # wget -q -O - https://oss.oracle.com/el4/RPM-GPG-KEY-oracle | apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg add - OK # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list /etc/apt/trusted.gpg.d/oracle.gpg - pub 1024D/B38A8516 2006-09-05 [expired: 2013-09-06] uid Oracle OSS group (Open Source Software group) # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg del 1024D/B38A8516 OK # echo $? 0 # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list /etc/apt/trusted.gpg.d/oracle.gpg - pub 1024D/B38A8516 2006-09-05 [expired: 2013-09-06] uid Oracle OSS group (Open Source Software group) # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg del B38A8516 OK # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list # ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.19 ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49 Uname: Linux 4.4.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Mar 2 17:34:07 2017 InstallationDate: Installed on 2014-11-03 (849 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-05-09 (297 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1669517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
I have reported this issue at https://bugzilla.kernel.org/show_bug.cgi?id=199127 ** Bug watch added: Linux Kernel Bug Tracker #199127 https://bugzilla.kernel.org/show_bug.cgi?id=199127 ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed -- 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/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: Confirmed Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
With bluez version 5.48-0ubuntu3 from Kubuntu 18.04 Beta1 (Bionic), the issue is still there : The command 'bluetoothctl' displays 'Waiting to connect to bluetoothd...', then hangs. ** Tags added: bionic -- 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/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: Fix Released Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
With bluez version 5.46-0ubuntu3 from Ubuntu 17.10 (Artful), the issue is still there : The command 'bluetoothctl' systematically hangs. ** Tags added: artful ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed -- 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/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: Confirmed Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729736] [NEW] 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile
Public bug reported: Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10 (Artful)' : - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically fails (1 CPU stuck). - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel- ppa/mainline seems to succeed. See attached kern.log After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted : $ lspci -nn -v -s 1:0.0 01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 1050 Ti Mobile] [1462:11c8] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at de00 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [disabled] [size=128] Expansion ROM at df00 [disabled] [size=512K] Capabilities: Kernel modules: nvidiafb, nouveau ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 artful kernel-fixed-upstream kernel-fixed-upstream-4.14 ** Attachment added: "kern.log with linux 4.13.0-16 showing nouveau failing" https://bugs.launchpad.net/bugs/1729736/+attachment/5002694/+files/kern-4.13.0-16-nouveau.log ** Package changed: ubuntu-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1729736 Title: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile Status in linux package in Ubuntu: New Bug description: Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10 (Artful)' : - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically fails (1 CPU stuck). - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel- ppa/mainline seems to succeed. See attached kern.log After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted : $ lspci -nn -v -s 1:0.0 01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 1050 Ti Mobile] [1462:11c8] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at de00 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [disabled] [size=128] Expansion ROM at df00 [disabled] [size=512K] Capabilities: Kernel modules: nvidiafb, nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
My particular use case is to detect, inside a shell script, if there is any bluetooth hardware at all. Since 'bluetoothctl' systematically hangs when there is NO bluetooth hardware, I can NOT use the 'bluetoothctl' command to achieve this use case. But I have found a good alternate method : if rfkill list | grep -q -i Bluetooth; then ...; fi So, the issue is NOT blocking for me. But I suggest that 'man bluetoothctl' should indicate that 'bluetoothctl' waits (possibly indefinitely) for answers from the 'bluetoothd' daemon, and therefore is NOT adequate for scripting. -- 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/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: New Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
With bluez version 5.43-0ubuntu1 from Ubuntu 17.04 (Zesty), the issue is still there : The command 'bluetoothctl' displays 'Waiting to connect to bluetoothd...', then hangs. ** Tags added: zesty ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: New Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction
I apologize, but my comment #9 was wrong : After more precise testing of 'systemd' version 232-21ubuntu2 from Ubuntu 17.04 Zesty with 'IdleAction=suspend' and 'IdleActionSec=2min' : 'systemd' does NOT unduly suspend my computer when there is an opened user session (OK). But 'systemd' does NOT systematically suspend my computer 2mn after the last opened user session has been closed. As a workaround, I am using the attached 'login-screen-suspend.sh' script. Since '/etc/rc.local' seems to be deprecated, I am starting my script as a 'systemd' service whose '/etc/systemd/system/login-screen-suspend.service' file has following content : [Unit] Description=login screen suspend daemon After=systemd-user-sessions.service [Service] Environment="LOGFILE=/var/log/login-screen-suspend.log" ExecStart=/bin/sh -c "/usr/local/sbin/login-screen-suspend.sh >> $LOGFILE 2>&1" [Install] WantedBy=multi-user.target ** Attachment removed: "/usr/local/bin/login-screen-suspend.sh" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1504254/+attachment/4749166/+files/login-screen-suspend.sh ** Attachment added: "/usr/local/sbin/login-screen-suspend.sh" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1504254/+attachment/4865743/+files/login-screen-suspend.sh -- 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/1504254 Title: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I want my computer to suspend when there is NO opened user session. So, I have activated following lines inside '/etc/systemd/logind.conf' : IdleAction=suspend IdleActionSec=15min - Systematically , under Ubuntu Vivid (15.04), this works correctly : During user interaction, the computer does NOT automatically suspend, but stays continuously alive. Once all users have closed their session, the computer automatically suspends after 15 min. - But systematically , under Ubuntu Wily (15.10 beta2), the computer automatically suspends after 15 min EVEN during user interaction. Hitting the keyboard makes the computer resume without data loss, but this is still annoying. In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must systematically be inhibited during user interaction. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z_admin1665 F pulseaudio /dev/snd/controlC1: z_admin1665 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 8 19:26:59 2015 HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140 InstallationDate: Installed on 2015-09-27 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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/systemd/+bug/1504254/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction
In systemd version 232-21ubuntu2 from Ubuntu 17.04 Zesty, this bug seems to be corrected : With 'IdleAction=suspend' and 'IdleActionSec=2min', systemd now does suspend my computer, but only when there is NO opened user session. -- 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/1504254 Title: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I want my computer to suspend when there is NO opened user session. So, I have activated following lines inside '/etc/systemd/logind.conf' : IdleAction=suspend IdleActionSec=15min - Systematically , under Ubuntu Vivid (15.04), this works correctly : During user interaction, the computer does NOT automatically suspend, but stays continuously alive. Once all users have closed their session, the computer automatically suspends after 15 min. - But systematically , under Ubuntu Wily (15.10 beta2), the computer automatically suspends after 15 min EVEN during user interaction. Hitting the keyboard makes the computer resume without data loss, but this is still annoying. In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must systematically be inhibited during user interaction. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z_admin1665 F pulseaudio /dev/snd/controlC1: z_admin1665 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 8 19:26:59 2015 HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140 InstallationDate: Installed on 2015-09-27 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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/systemd/+bug/1504254/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669517] [NEW] apt-key del must absolutely detect all errors, and then provide NON-zero return code and error message
Public bug reported: Currently, 'apt-key del' does NOT detect that the keyid given in parameter is invalid : It displays 'OK' and provides a return code equal to zero (see log below). I consider that letting erroneously believe that a GPG key has been successfully removed is a security issue. In fact 'apt-key del' must absolutely detect all errors, and then provide NON-zero return code and error message. # wget -q -O - https://oss.oracle.com/el4/RPM-GPG-KEY-oracle | apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg add - OK # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list /etc/apt/trusted.gpg.d/oracle.gpg - pub 1024D/B38A8516 2006-09-05 [expired: 2013-09-06] uid Oracle OSS group (Open Source Software group) # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg del 1024D/B38A8516 OK # echo $? 0 # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list /etc/apt/trusted.gpg.d/oracle.gpg - pub 1024D/B38A8516 2006-09-05 [expired: 2013-09-06] uid Oracle OSS group (Open Source Software group) # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg del B38A8516 OK # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list # ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.19 ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49 Uname: Linux 4.4.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Mar 2 17:34:07 2017 InstallationDate: Installed on 2014-11-03 (849 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-05-09 (297 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1669517 Title: apt-key del must absolutely detect all errors, and then provide NON- zero return code and error message Status in apt package in Ubuntu: New Bug description: Currently, 'apt-key del' does NOT detect that the keyid given in parameter is invalid : It displays 'OK' and provides a return code equal to zero (see log below). I consider that letting erroneously believe that a GPG key has been successfully removed is a security issue. In fact 'apt-key del' must absolutely detect all errors, and then provide NON-zero return code and error message. # wget -q -O - https://oss.oracle.com/el4/RPM-GPG-KEY-oracle | apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg add - OK # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list /etc/apt/trusted.gpg.d/oracle.gpg - pub 1024D/B38A8516 2006-09-05 [expired: 2013-09-06] uid Oracle OSS group (Open Source Software group) # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg del 1024D/B38A8516 OK # echo $? 0 # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list /etc/apt/trusted.gpg.d/oracle.gpg - pub 1024D/B38A8516 2006-09-05 [expired: 2013-09-06] uid Oracle OSS group (Open Source Software group) # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg del B38A8516 OK # apt-key --keyring /etc/apt/trusted.gpg.d/oracle.gpg list # ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.19 ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49 Uname: Linux 4.4.0-65-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Mar 2 17:34:07 2017 InstallationDate: Installed on 2014-11-03 (849 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-05-09 (297 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1669517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580308] Re: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
I am NOT using 'btrfs'. I am using 'PARTLABEL' in '/etc/fstab'. -- 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/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab Status in initramfs-tools package in Ubuntu: New Bug description: Systematically, - With a /etc/fstab using UUID or LABEL, update-initramfs works correctly - With a /etc/fstab using PARTLABEL, update-initramfs displays following error messages : cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=Ubuntu-Gnome cryptsetup: WARNING: could not determine root device from /etc/fstab cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu The cryptsetup part of update-initramfs must correctly take into account PARTLABEL inside /etc/fstab Thank you in advance ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue May 10 21:14:24 2016 InstallationDate: Installed on 2014-11-03 (553 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago) mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
With bluez version 5.41-0ubuntu3 : The command 'bluetoothctl' displays 'Waiting to connect to bluetoothd...', then hangs. -- 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/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: New Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction
IdleAction=suspend still DOES NOT WORK AT ALL in systemd version 231-9git1 from Ubuntu 16.10 Yakkety Beta. -- 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/1504254 Title: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction Status in systemd package in Ubuntu: New Bug description: I want my computer to suspend when there is NO opened user session. So, I have activated following lines inside '/etc/systemd/logind.conf' : IdleAction=suspend IdleActionSec=15min - Systematically , under Ubuntu Vivid (15.04), this works correctly : During user interaction, the computer does NOT automatically suspend, but stays continuously alive. Once all users have closed their session, the computer automatically suspends after 15 min. - But systematically , under Ubuntu Wily (15.10 beta2), the computer automatically suspends after 15 min EVEN during user interaction. Hitting the keyboard makes the computer resume without data loss, but this is still annoying. In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must systematically be inhibited during user interaction. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z_admin1665 F pulseaudio /dev/snd/controlC1: z_admin1665 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 8 19:26:59 2015 HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140 InstallationDate: Installed on 2015-09-27 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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/systemd/+bug/1504254/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction
The attached 'login-screen-suspend.sh' script contains a workaround daemon permitting to automatically suspend the computer after NO user has been active during the time specified in '/etc/systemd/logind.conf'. It is possible to install this script in '/usr/local/bin/login-screen- suspend.sh', and launch this daemon by adding following lines at the beginning of '/etc/rc.local' : LOGIN_SCREEN_SUSPEND='/usr/local/bin/login-screen-suspend.sh' if [ -f "$LOGIN_SCREEN_SUSPEND" ] && \ [ -x "$LOGIN_SCREEN_SUSPEND" ]; then $LOGIN_SCREEN_SUSPEND >> /var/log/login-screen-suspend.log 2>&1 & fi This workaround is probably NOT bulletproof, but it works correctly for me. In the hope that it may be useful. ** Attachment added: "/usr/local/bin/login-screen-suspend.sh" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1504254/+attachment/4749166/+files/login-screen-suspend.sh -- 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/1504254 Title: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction Status in systemd package in Ubuntu: New Bug description: I want my computer to suspend when there is NO opened user session. So, I have activated following lines inside '/etc/systemd/logind.conf' : IdleAction=suspend IdleActionSec=15min - Systematically , under Ubuntu Vivid (15.04), this works correctly : During user interaction, the computer does NOT automatically suspend, but stays continuously alive. Once all users have closed their session, the computer automatically suspends after 15 min. - But systematically , under Ubuntu Wily (15.10 beta2), the computer automatically suspends after 15 min EVEN during user interaction. Hitting the keyboard makes the computer resume without data loss, but this is still annoying. In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must systematically be inhibited during user interaction. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z_admin1665 F pulseaudio /dev/snd/controlC1: z_admin1665 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 8 19:26:59 2015 HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140 InstallationDate: Installed on 2015-09-27 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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/systemd/+bug/1504254/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction
IdleAction=suspend DOES NOT WORK AT ALL in systemd version 231-6git1 from Ubuntu 16.10 Yakkety Beta. -- 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/1504254 Title: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction Status in systemd package in Ubuntu: New Bug description: I want my computer to suspend when there is NO opened user session. So, I have activated following lines inside '/etc/systemd/logind.conf' : IdleAction=suspend IdleActionSec=15min - Systematically , under Ubuntu Vivid (15.04), this works correctly : During user interaction, the computer does NOT automatically suspend, but stays continuously alive. Once all users have closed their session, the computer automatically suspends after 15 min. - But systematically , under Ubuntu Wily (15.10 beta2), the computer automatically suspends after 15 min EVEN during user interaction. Hitting the keyboard makes the computer resume without data loss, but this is still annoying. In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must systematically be inhibited during user interaction. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z_admin1665 F pulseaudio /dev/snd/controlC1: z_admin1665 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 8 19:26:59 2015 HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140 InstallationDate: Installed on 2015-09-27 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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/systemd/+bug/1504254/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
The problem is still the same with bluez version 5.37-0ubuntu5 -- 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/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: New Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580308] [NEW] update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab
Public bug reported: Systematically, - With a /etc/fstab using UUID or LABEL, update-initramfs works correctly - With a /etc/fstab using PARTLABEL, update-initramfs displays following error messages : cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=Ubuntu-Gnome cryptsetup: WARNING: could not determine root device from /etc/fstab cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu The cryptsetup part of update-initramfs must correctly take into account PARTLABEL inside /etc/fstab Thank you in advance ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue May 10 21:14:24 2016 InstallationDate: Installed on 2014-11-03 (553 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago) mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01 ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1580308 Title: update-initramfs cryptsetup must correctly take into account PARTLABEL inside /etc/fstab Status in initramfs-tools package in Ubuntu: New Bug description: Systematically, - With a /etc/fstab using UUID or LABEL, update-initramfs works correctly - With a /etc/fstab using PARTLABEL, update-initramfs displays following error messages : cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=Ubuntu-Gnome cryptsetup: WARNING: could not determine root device from /etc/fstab cryptsetup: WARNING: failed to detect canonical device of PARTLABEL=USR-Ubuntu The cryptsetup part of update-initramfs must correctly take into account PARTLABEL inside /etc/fstab Thank you in advance ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue May 10 21:14:24 2016 InstallationDate: Installed on 2014-11-03 (553 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago) mtime.conffile..etc.initramfs-tools.initramfs.conf: 2016-02-21T22:22:01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction
This bug is still present in systemd version 229-4ubuntu4 from 'Ubuntu 16.04 Xenial' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1504254 Title: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction Status in systemd package in Ubuntu: New Bug description: I want my computer to suspend when there is NO opened user session. So, I have activated following lines inside '/etc/systemd/logind.conf' : IdleAction=suspend IdleActionSec=15min - Systematically , under Ubuntu Vivid (15.04), this works correctly : During user interaction, the computer does NOT automatically suspend, but stays continuously alive. Once all users have closed their session, the computer automatically suspends after 15 min. - But systematically , under Ubuntu Wily (15.10 beta2), the computer automatically suspends after 15 min EVEN during user interaction. Hitting the keyboard makes the computer resume without data loss, but this is still annoying. In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must systematically be inhibited during user interaction. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z_admin1665 F pulseaudio /dev/snd/controlC1: z_admin1665 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 8 19:26:59 2015 HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140 InstallationDate: Installed on 2015-09-27 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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/systemd/+bug/1504254/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] [NEW] bluetoothctl systematically hangs when there is no bluetooth hardware
Public bug reported: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: New Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1
[Touch-packages] [Bug 1428874] Re: libblkid: HFS+ label NOT found when the HFS+ filesystem is nearly full
This bug is corrected in libblkid1 version 2.26.2-6ubuntu3 from Ubuntu 15.10 Wily It may in fact have been corrected in earlier versions. ** Changed in: util-linux (Ubuntu) Status: New => Fix Released -- 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/1428874 Title: libblkid: HFS+ label NOT found when the HFS+ filesystem is nearly full Status in util-linux package in Ubuntu: Fix Released Bug description: Under Ubuntu, for HFS+ filesystems : The 'blkid' command finds in general BOTH the 'Partition label' and the 'Filesystem label'. For example : $ sudo blkid -s LABEL -s TYPE -s PARTLABEL /dev/sda11 /dev/sda11: LABEL="Etienne" TYPE="hfsplus" PARTLABEL="Etienne" But when the HFS+ filesystem is nearly full : The 'blkid' command correctly finds the partition label, but NOT the HFS+ filesystem label. For example : $ sudo blkid -s LABEL -s TYPE -s PARTLABEL /dev/sda14 /dev/sda14: TYPE="hfsplus" PARTLABEL="Camille" I am absolutely certain that '/dev/sda14' has a filesystem label, because 'fsck.hfsplus' finds it, and 'diskutil' of 'Mac OS 10.5' also finds it : $ sudo fsck.hfsplus /dev/sda14 ** /dev/sda14 ** Checking HFS Plus volume. ** Checking Extents Overflow file. ** Checking Catalog file. ** Checking multi-linked files. ** Checking Catalog hierarchy. ** Checking Extended Attributes file. ** Checking volume bitmap. ** Checking volume information. ** The volume Camille appears to be OK. $ sudo diskutil info /dev/disk0s14 Device Identifier:disk0s14 Device Node: /dev/disk0s14 Part Of Whole:disk0 Device / Media Name: Camille Volume Name: Camille Mount Point: /Users/camille File System: HFS+ Owners: Enabled Partition Type: Apple_HFS Bootable: Not bootable, can be made bootable safely Media Type: Generic Protocol: SATA SMART Status: Verified Volume UUID: 91C9F9E9-94F6-30F3-A0EE-6BE6373CFD4E Total Size: 21.9 Gi (23487053824 B) (45873152 512-byte blocks) Free Space: 74.7 Mi (78323712 B) (152976 512-byte blocks) Read Only:No Ejectable:No Whole:No Internal: Yes ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libblkid1 2.25.1-3ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Mar 5 22:56:33 2015 InstallationDate: Installed on 2014-11-03 (121 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1428874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction
This bug is still present in systemd version 229-2ubuntu1 from 'Ubuntu 16.04 Xenial Beta1'. ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1504254 Title: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction Status in systemd package in Ubuntu: New Bug description: I want my computer to suspend when there is NO opened user session. So, I have activated following lines inside '/etc/systemd/logind.conf' : IdleAction=suspend IdleActionSec=15min - Systematically , under Ubuntu Vivid (15.04), this works correctly : During user interaction, the computer does NOT automatically suspend, but stays continuously alive. Once all users have closed their session, the computer automatically suspends after 15 min. - But systematically , under Ubuntu Wily (15.10 beta2), the computer automatically suspends after 15 min EVEN during user interaction. Hitting the keyboard makes the computer resume without data loss, but this is still annoying. In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must systematically be inhibited during user interaction. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z_admin1665 F pulseaudio /dev/snd/controlC1: z_admin1665 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 8 19:26:59 2015 HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140 InstallationDate: Installed on 2015-09-27 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0: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/systemd/+bug/1504254/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1428874] [NEW] libblkid: HFS+ label NOT found when the HFS+ filesystem is nearly full
Public bug reported: Under Ubuntu, for HFS+ filesystems : The 'blkid' command finds in general BOTH the 'Partition label' and the 'Filesystem label'. For example : $ sudo blkid -s LABEL -s TYPE -s PARTLABEL /dev/sda11 /dev/sda11: LABEL="Etienne" TYPE="hfsplus" PARTLABEL="Etienne" But when the HFS+ filesystem is nearly full : The 'blkid' command correctly finds the partition label, but NOT the HFS+ filesystem label. For example : $ sudo blkid -s LABEL -s TYPE -s PARTLABEL /dev/sda14 /dev/sda14: TYPE="hfsplus" PARTLABEL="Camille" I am absolutely certain that '/dev/sda14' has a filesystem label, because 'fsck.hfsplus' finds it, and 'diskutil' of 'Mac OS 10.5' also finds it : $ sudo fsck.hfsplus /dev/sda14 ** /dev/sda14 ** Checking HFS Plus volume. ** Checking Extents Overflow file. ** Checking Catalog file. ** Checking multi-linked files. ** Checking Catalog hierarchy. ** Checking Extended Attributes file. ** Checking volume bitmap. ** Checking volume information. ** The volume Camille appears to be OK. $ sudo diskutil info /dev/disk0s14 Device Identifier:disk0s14 Device Node: /dev/disk0s14 Part Of Whole:disk0 Device / Media Name: Camille Volume Name: Camille Mount Point: /Users/camille File System: HFS+ Owners: Enabled Partition Type: Apple_HFS Bootable: Not bootable, can be made bootable safely Media Type: Generic Protocol: SATA SMART Status: Verified Volume UUID: 91C9F9E9-94F6-30F3-A0EE-6BE6373CFD4E Total Size: 21.9 Gi (23487053824 B) (45873152 512-byte blocks) Free Space: 74.7 Mi (78323712 B) (152976 512-byte blocks) Read Only:No Ejectable:No Whole:No Internal: Yes ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libblkid1 2.25.1-3ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Mar 5 22:56:33 2015 InstallationDate: Installed on 2014-11-03 (121 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1428874 Title: libblkid: HFS+ label NOT found when the HFS+ filesystem is nearly full Status in util-linux package in Ubuntu: New Bug description: Under Ubuntu, for HFS+ filesystems : The 'blkid' command finds in general BOTH the 'Partition label' and the 'Filesystem label'. For example : $ sudo blkid -s LABEL -s TYPE -s PARTLABEL /dev/sda11 /dev/sda11: LABEL="Etienne" TYPE="hfsplus" PARTLABEL="Etienne" But when the HFS+ filesystem is nearly full : The 'blkid' command correctly finds the partition label, but NOT the HFS+ filesystem label. For example : $ sudo blkid -s LABEL -s TYPE -s PARTLABEL /dev/sda14 /dev/sda14: TYPE="hfsplus" PARTLABEL="Camille" I am absolutely certain that '/dev/sda14' has a filesystem label, because 'fsck.hfsplus' finds it, and 'diskutil' of 'Mac OS 10.5' also finds it : $ sudo fsck.hfsplus /dev/sda14 ** /dev/sda14 ** Checking HFS Plus volume. ** Checking Extents Overflow file. ** Checking Catalog file. ** Checking multi-linked files. ** Checking Catalog hierarchy. ** Checking Extended Attributes file. ** Checking volume bitmap. ** Checking volume information. ** The volume Camille appears to be OK. $ sudo diskutil info /dev/disk0s14 Device Identifier:disk0s14 Device Node: /dev/disk0s14 Part Of Whole:disk0 Device / Media Name: Camille Volume Name: Camille Mount Point: /Users/camille File System: HFS+ Owners: Enabled Partition Type: Apple_HFS Bootable: Not bootable, can be made bootable safely Media Type: Generic Protocol: SATA SMART Status: Verified Volume UUID: 91C9F9E9-94F6-30F3-A0EE-6BE6373CFD4E Total Size: 21.9 Gi (23487053824 B) (45873152 512-byte blocks) Free Space: 74.7 Mi (78323712 B) (152976 512-byte blocks) Read Only:No Ejectable:No Whole:No Internal: Yes ProblemType
[Touch-packages] [Bug 1175780] Re: libblkid: HFS+ label found by 'quantal' is NOT found by 'raring'
Version '2.25.1-3ubuntu4' of 'util-linux' correctly finds the HFS+ label on a 48G HFS+ partition : $ df -h . Filesystem Size Used Avail Use% Mounted on /dev/sda11 48G 39G 9,5G 81% /home/etienne $ sudo blkid -s LABEL -s TYPE /dev/sda11 /dev/sda11: LABEL="Etienne" TYPE="hfsplus" So, this bug is probably fixed. -- 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/1175780 Title: libblkid: HFS+ label found by 'quantal' is NOT found by 'raring' Status in util-linux package in Ubuntu: New Bug description: Several partitions of my first hard disk are formatted with Mac OS 10.5 as HFS+. 'quantal' did correctly read the HFS+ label of all these partitions. 'raring' correctly reads the HFS+ label of all these partitions, EXCEPT one, which is my largest partition formatted with non-journaled HFS+. So, this bug is probably related to Ubuntu bug #789928. Mac OS 10.5 clearly states that the 10th partition (labeled 'Etienne') contains a non-journaled HFS+ filesystem whose label is also 'Etienne' : # diskutil info /dev/disk0s10 Device Identifier:disk0s10 Device Node: /dev/disk0s10 Part Of Whole:disk0 Device / Media Name: Etienne Volume Name: Etienne Mount Point: /Users/etienne File System: HFS+ Owners: Enabled Partition Type: Apple_HFS Bootable: Not bootable, can be made bootable safely Media Type: Generic Protocol: SATA SMART Status: Verified Volume UUID: F4B66803-AE66-3576-99D7-F6234E3434A2 Total Size: 44.6 Gi (47865397248 B) (93487104 512-byte blocks) Free Space: 14.4 Gi (15454658560 B) (30184880 512-byte blocks) Read Only:No Ejectable:No Whole:No Internal: Yes # fsck_hfs -n -d /dev/disk0s10 ** /dev/rdisk0s10 (NO WRITE) Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K. ** Verifying volume when it is mounted with write access. ** Checking Non-journaled HFS Plus volume. ** Checking Extents Overflow file. ** Checking Catalog file. ** Checking multi-linked files. CheckHardLinks: found 3 pre-Leopard file inodes. ** Checking Catalog hierarchy. ** Checking Extended Attributes file. ** Checking volume bitmap. ** Checking volume information. ** The volume Etienne appears to be OK. Ubuntu 'raring' finds all HFS+ labels, EXCEPT the label of this 10th partition (you can see that the UUID really is the same) : # blkid -t TYPE=hfsplus /dev/sda2: UUID="83b917f1-60e6-3028-8cf3-5f42cb769e85" LABEL="Macintosh HD" TYPE="hfsplus" /dev/sda10: UUID="f4b66803-ae66-3576-99d7-f6234e3434a2" TYPE="hfsplus" /dev/sda11: UUID="f2503c35-115f-3da9-a9b2-5168b8189246" LABEL="Marguerite" TYPE="hfsplus" ... ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: util-linux 2.20.1-5.1ubuntu8 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 2 22:17:33 2013 InstallationDate: Installed on 2013-02-14 (77 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: util-linux UpgradeStatus: Upgraded to raring on 2013-04-26 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1175780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1175780] Re: libblkid: HFS+ label found by 'quantal' is NOT found by 'raring'
** Tags added: saucy trusty utopic -- 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/1175780 Title: libblkid: HFS+ label found by 'quantal' is NOT found by 'raring' Status in “util-linux” package in Ubuntu: New Bug description: Several partitions of my first hard disk are formatted with Mac OS 10.5 as HFS+. 'quantal' did correctly read the HFS+ label of all these partitions. 'raring' correctly reads the HFS+ label of all these partitions, EXCEPT one, which is my largest partition formatted with non-journaled HFS+. So, this bug is probably related to Ubuntu bug #789928. Mac OS 10.5 clearly states that the 10th partition (labeled 'Etienne') contains a non-journaled HFS+ filesystem whose label is also 'Etienne' : # diskutil info /dev/disk0s10 Device Identifier:disk0s10 Device Node: /dev/disk0s10 Part Of Whole:disk0 Device / Media Name: Etienne Volume Name: Etienne Mount Point: /Users/etienne File System: HFS+ Owners: Enabled Partition Type: Apple_HFS Bootable: Not bootable, can be made bootable safely Media Type: Generic Protocol: SATA SMART Status: Verified Volume UUID: F4B66803-AE66-3576-99D7-F6234E3434A2 Total Size: 44.6 Gi (47865397248 B) (93487104 512-byte blocks) Free Space: 14.4 Gi (15454658560 B) (30184880 512-byte blocks) Read Only:No Ejectable:No Whole:No Internal: Yes # fsck_hfs -n -d /dev/disk0s10 ** /dev/rdisk0s10 (NO WRITE) Using cacheBlockSize=32K cacheTotalBlock=1024 cacheSize=32768K. ** Verifying volume when it is mounted with write access. ** Checking Non-journaled HFS Plus volume. ** Checking Extents Overflow file. ** Checking Catalog file. ** Checking multi-linked files. CheckHardLinks: found 3 pre-Leopard file inodes. ** Checking Catalog hierarchy. ** Checking Extended Attributes file. ** Checking volume bitmap. ** Checking volume information. ** The volume Etienne appears to be OK. Ubuntu 'raring' finds all HFS+ labels, EXCEPT the label of this 10th partition (you can see that the UUID really is the same) : # blkid -t TYPE=hfsplus /dev/sda2: UUID="83b917f1-60e6-3028-8cf3-5f42cb769e85" LABEL="Macintosh HD" TYPE="hfsplus" /dev/sda10: UUID="f4b66803-ae66-3576-99d7-f6234e3434a2" TYPE="hfsplus" /dev/sda11: UUID="f2503c35-115f-3da9-a9b2-5168b8189246" LABEL="Marguerite" TYPE="hfsplus" ... ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: util-linux 2.20.1-5.1ubuntu8 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 2 22:17:33 2013 InstallationDate: Installed on 2013-02-14 (77 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: util-linux UpgradeStatus: Upgraded to raring on 2013-04-26 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1175780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp