[Touch-packages] [Bug 1843201] Re: Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome
Thanks for looking into this, and the pointer. I guess, another option would be to not request shortcut inhibition, unless I'm misunderstanding its value? Unless there's a worry that some other application will be able to steal your password this way — it doesn't seem obviously warranted to me. For example, `ssh-askpass-fullscreen` does not generate this prompt. It isn't clear to me that the fullscreen-ness of this implementation materially changes the risk profile, so either shortcut inhibition isn't useful, or I should file a bug against `ssh-askpass-fullscreen` to either request this privilege or document the gap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1843201 Title: Unity in Wayland prompts for keyboard focus on each run of ssh- askpass-gnome Status in gnome-desktop package in Ubuntu: New Status in openssh package in Ubuntu: Incomplete Status in wayland package in Ubuntu: New Bug description: When using a Wayland-based Unity session on Ubuntu 19.04: 1. Have ssh-askpass-gnome as your askpass program. 2. ssh-add -c 3. `ssh` to a host Each time, before the ssh-askpass prompt is shown, Unity shows this dialog: +-+ | | | ssh-askpass wants to inhibit shortcuts | | | | You can restore Shortcuts by pressing | | Super+Escape. | | | |_| | Deny | Allow | +-+ This is mildly distracting, and it means that you need to hit , answer, , instead of just answer . ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ssh-askpass-gnome 1:7.9p1-10 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 15:04:25 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1 InstallationDate: Installed on 2019-08-27 (12 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1843201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483751] Re: Issues traversing a sftp server when files or folders contain the character "]"
Can confirm: sftp> cd Foo\ \[bar\] sftp> ls hello.txt sftp> get hello.txt File "/home/lfaraone/Foo [bar]/hello.txt" not found. sftp> ** Changed in: openssh (Ubuntu) Importance: Undecided => Low ** Changed in: openssh (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1483751 Title: Issues traversing a sftp server when files or folders contain the character "]" Status in openssh package in Ubuntu: Triaged Bug description: I am unsure if the bug is with openssh sftp client or within openssh- sftp-server When traversing an sftp server, I encounter issues for files and, in particular, directories containing the character "]". Tab completion does not escape the character in sftp shell, however, in bash it will escape the character for tab completion. If I "cd" into a directory that contains the character I cannot get any files with in that directory and I have to rename the directory outside of the sftp shell to remove the character in order to be able to correctly get files. Ex: sftp> cd Movie\ \[1080p]/ sftp> ls Movie.1080p.mp4 sftp> get Movie.1080p.mp4 File "/home/hitsuji/movies/Movie [1080p]/Movie.1080p.mp4" not found. sftp> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 11 14:36:00 2015 InstallationDate: Installed on 2015-05-01 (101 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1483751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843201] [NEW] Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome
Public bug reported: When using a Wayland-based Unity session on Ubuntu 19.04: 1. Have ssh-askpass-gnome as your askpass program. 2. ssh-add -c 3. `ssh` to a host Each time, before the ssh-askpass prompt is shown, Unity shows this dialog: +-+ | | | ssh-askpass wants to inhibit shortcuts | | | | You can restore Shortcuts by pressing | | Super+Escape. | | | |_| | Deny | Allow | +-+ This is mildly distracting, and it means that you need to hit , answer, , instead of just answer . ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ssh-askpass-gnome 1:7.9p1-10 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 15:04:25 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1 InstallationDate: Installed on 2019-08-27 (12 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1843201 Title: Unity in Wayland prompts for keyboard focus on each run of ssh- askpass-gnome Status in openssh package in Ubuntu: New Bug description: When using a Wayland-based Unity session on Ubuntu 19.04: 1. Have ssh-askpass-gnome as your askpass program. 2. ssh-add -c 3. `ssh` to a host Each time, before the ssh-askpass prompt is shown, Unity shows this dialog: +-+ | | | ssh-askpass wants to inhibit shortcuts | | | | You can restore Shortcuts by pressing | | Super+Escape. | | | |_| | Deny | Allow | +-+ This is mildly distracting, and it means that you need to hit , answer, , instead of just answer . ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ssh-askpass-gnome 1:7.9p1-10 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 15:04:25 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1 InstallationDate: Installed on 2019-08-27 (12 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: openssh UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1843201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733002] Re: Google Online Account Two Factor with hardware key fails immediately
** Changed in: gnome-online-accounts (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1733002 Title: Google Online Account Two Factor with hardware key fails immediately Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: The hardware key authentication two factor fails immediately with a web based retry dialogue when connecting a Google account to the online accounts in settings using a hardware key second factor. Steps to reproduce: 1. Set Google Account to default to a hardware security key like a Yubikey or other FIDO standard key after having two factor authentication enabled on your Google Account. 2. Open Online accounts 3. Add a Google Account 4. Enter google email address 5. Enter google password 6. (this is the login flow of two factor, if default is the hardware key the error should appear). Work around: Choose use another method to authenticate: enter the authentication code and you will proceed. Expectations were: The ability to use the hardware key to authenticate as the second factor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 16:01:11 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751657] Re: man journalctl gives info about -g option not present in command
** Changed in: systemd (Ubuntu) Importance: Undecided => Low -- 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/1751657 Title: man journalctl gives info about -g option not present in command Status in systemd package in Ubuntu: Confirmed Bug description: man journalctl documents a --grep option, however: $ journalctl -g a journalctl: invalid option -- 'g' $ journalctl --grep a Compiled without pattern matching support ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Feb 25 21:53:29 2018 InstallationDate: Installed on 2017-06-21 (248 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 0c45:6713 Microdia Bus 001 Device 004: ID 10d7:1102 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet splash acpi_rev_override=5 pci=noaer vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-02-17 (8 days ago) dmi.bios.date: 12/15/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
** Description changed: - I've found an issue on some of our Xenial office machines, causing - NetworkManager to drop its IP address lease in some cases when it - shouldn't. I'm not sure if the actual bug is in NetworkManager or - perhaps dbus or dhclient, but I'll do my best to help to figure out - where it is. + SRU REQUEST: + + Debdiff (nm-dhcp-helper.debdiff) attached. + + Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug + was fixed upstream in 1.4. + + [Impact] + + * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP + lease renewal due to a DBus race condition. + + * Upstream NetworkManager 1.4 fixes the race condition by changing + nm-dhcp-helper's DBus notification from signal "Event" to method + "Notify". + + * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's + NM 1.2.x. + + [Test Case] + + * Not reliably reproducible. Out of hundreds of machines, only a + dozen or so fail to notify NetworkManager of a DHCP lease + renewal about 30-50% of the time. (i.e. It's always the same + handful of machines that fail.) + + * All such machines with the patched packages have been fine for weeks, + over many dozens of lease renewals. + + [Regression Potential] + + * The patch changes both nm-dhcp-helper and NetworkManager itself. As + soon as the new packages are unpacked, the new nm-dhcp-helper will be + used on DHCP lease renewals, with the new Notify mechanism. Since the + running, old NetworkManager is still expecting Event notifications, the + patched nm-dhcp-helper has fallback capability to Event. + + * Once NetworkManager is restarted and is running the patched version, + it will have the new Notify support. + + [Other Info] + + * Upstream bug w/ patch: + https://bugzilla.gnome.org/show_bug.cgi?id=784636 + + * RHEL bug with links to the 1.4 commits from which the patch was + derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 + + * NOTE: The final comment on the upstream GNOME bug claims that the + fix is incomplete. However, it is possible that the running + NetworkManager was not restarted (see Regression Potential notes above), + which is why nm-dhcp-helper is falling back to Event. The remainder of + the log messages in that final comment are from a custom wrapper the + submitter was running around nm-dhcp-helper. I have deployed the exact + same patch (without said wrapper) to real-world systems and tested + extensively, and see nothing but successful DHCP lease renewal + notifications using D-Bus Notify, not D-Bus Event. + + + + I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.
[Touch-packages] [Bug 1686803] Re: sudo returns exit code 0 if child is killed with SIGTERM
This may have security implications in edge cases. E.g. if an application is checking the status code of `sudo` and using `0` as "good to go", this may allow for access to a resource to be permitted when it should not be. ** Summary changed: - Backport changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" + sudo returns exit code 0 if child is killed with SIGTERM ** Tags added: regression-release ** Changed in: sudo (Ubuntu) Importance: Undecided => Medium ** Changed in: sudo (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: sudo returns exit code 0 if child is killed with SIGTERM Status in sudo: Unknown Status in sudo package in Ubuntu: Triaged Bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686803] Re: Backport changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the"
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686803 Title: Backport changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" Status in sudo: Unknown Status in sudo package in Ubuntu: New Bug description: Please backport upstream sudo changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the" to xenial, yakkety, and zesty versions of sudo. This will fix a regression documented by this upstream bug report: https://bugzilla.sudo.ws/show_bug.cgi?id=784 sudo 1.8.15 changeset 10229:153f016db8f1 "When the command sudo is running is killed by a signal, sudo will" introduced a regression where the exit status is always 0 when a command is killed by a signal other than SIGINT. https://www.sudo.ws/repos/sudo/rev/153f016db8f1 This will be fixed in sudo 1.8.20 with changeset 10917:50b988d0c97f "The fix for Bug #722 contained a typo/thinko that resulted in the". https://www.sudo.ws/repos/sudo/rev/50b988d0c97f trusty sudo is based off sudo 1.8.9 and is not affected. xenial sudo based off sudo 1.8.16, yaketty sudo based off sudo 1.8.16, and zesty sudo based off 1.8.19 need the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1686803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Changed in: initramfs-tools Assignee: gintassi (gintassi) => (unassigned) ** Changed in: initramfs-tools (Ubuntu) Assignee: gintassi (gintassi) => Luke Faraone (lfaraone) -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. See instructions here https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Luke Faraone (lfaraone) ** Changed in: initramfs-tools Assignee: sauro peña (sauropm) => (unassigned) -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. See instructions here https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
b-vantola, please don't change the assignee unless you're actively working to fix the bug. ** Changed in: initramfs-tools (Ubuntu) Assignee: Boguslav Vantola (b-vantola) => Luke Faraone (lfaraone) -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. See instructions here https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
Fair enough. I've unmarked it as a duplicate. Technically, yes, this bug is about the error message, although the "WORKAROUND" in the description is a bit of a misnomer, since it focuses on resolving the issue that resulted in the error. Updating the copy should be easy enough; I can tackle that for Yakkety. ** Changed in: initramfs-tools (Ubuntu) Status: Triaged => In Progress ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Luke Faraone (lfaraone) -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed
** This bug is no longer a duplicate of bug 798414 update-initramfs should produce a more helpful error when there isn't enough free space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1054927 Title: Autoupdater fills /boot and crashes because old kernel images are never removed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Install Ubuntu with the default LVM encryption recipe 2) Set Ubuntu to automatically install security updates on the background 3) Use ubuntu for 5 months Actual results: The system automatically installs security updates for the kernel under /boot. It's never removes previous kernel images. After about five months, the /boot partition created by the install recipe (i.e. sized according to the judgment of Ubuntu developers—not me) fills up and the unattended updater crashes during the next kernel update. Expected results: Expected the unattended updater to leave the nearest kernel and the previous one on /boot and to automatically remove older kernel images. Expected the system installer to set up /boot such that it never runs out of space when the system updater operates automatically. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sun Sep 23 12:53:52 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1054927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1054927] Re: Autoupdater fills /boot and crashes because old kernel images are never removed
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error when there isn't enough free space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1054927 Title: Autoupdater fills /boot and crashes because old kernel images are never removed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Install Ubuntu with the default LVM encryption recipe 2) Set Ubuntu to automatically install security updates on the background 3) Use ubuntu for 5 months Actual results: The system automatically installs security updates for the kernel under /boot. It's never removes previous kernel images. After about five months, the /boot partition created by the install recipe (i.e. sized according to the judgment of Ubuntu developers—not me) fills up and the unattended updater crashes during the next kernel update. Expected results: Expected the unattended updater to leave the nearest kernel and the previous one on /boot and to automatically remove older kernel images. Expected the system installer to set up /boot such that it never runs out of space when the system updater operates automatically. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.14.9 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sun Sep 23 12:53:52 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1054927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323593] Re: Unattended upgrades crash
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** This bug is no longer a duplicate of bug 1054927 Autoupdater fills /boot and crashes because old kernel images are never removed ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error when there isn't enough free space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1323593 Title: Unattended upgrades crash Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Based this bug report upon https://bugs.launchpad.net/ubuntu/+source /unattended-upgrades/+bug/1052360/comments/17 Installed latest updates on Xubuntu Trusty, immediately during the update process the system detected an error, after reboot an error report again emerged, hence reporting this bug as suggested above. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 27 12:40:58 2014 InstallationDate: Installed on 2014-05-17 (10 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1323593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** This bug is no longer a duplicate of bug 1054927 Autoupdater fills /boot and crashes because old kernel images are never removed ** This bug has been marked a duplicate of bug 798414 update-initramfs should produce a more helpful error when there isn't enough free space -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades package in Ubuntu: Fix Committed Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Changed in: initramfs-tools Assignee: Timothy Ricks (timothy-ricks) => (unassigned) -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: Triaged Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516517] Re: package linux-image-extra-4.2.0-18-generic 4.2.0-18.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
*** This bug is a duplicate of bug 798414 *** https://bugs.launchpad.net/bugs/798414 ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1516517 Title: package linux-image-extra-4.2.0-18-generic 4.2.0-18.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Occurred on system update. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: linux-image-extra-4.2.0-18-generic 4.2.0-18.22 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lfaraone 3488 F pulseaudio Date: Mon Nov 16 07:07:02 2015 DuplicateSignature: package:linux-image-extra-4.2.0-18-generic:4.2.0-18.22:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=c8caa2b5-9a00-4eca-af20-3ea9fdb4dac9 InstallationDate: Installed on 2015-05-19 (180 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b217 Chicony Electronics Co., Ltd Lenovo Integrated Camera (0.3MP) Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4286CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: initramfs-tools Title: package linux-image-extra-4.2.0-18-generic 4.2.0-18.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-29 (18 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1516517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572004] Re: pcscd consumes 100% CPU
*** This bug is a duplicate of bug 1551897 *** https://bugs.launchpad.net/bugs/1551897 ** This bug has been marked a duplicate of bug 1551897 Excessive CPU utilization -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1572004 Title: pcscd consumes 100% CPU Status in pcsc-lite package in Ubuntu: New Status in pcsc-lite package in Debian: Fix Released Bug description: After upgrading to 16.04, pcscd process is stuck at using 100% CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1572004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507190] Re: Disconnect Smartcard reader from USB causes pscd to crash
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1507190 Title: Disconnect Smartcard reader from USB causes pscd to crash Status in pcsc-lite package in Ubuntu: New Bug description: PCSC works corectly with Reiner SCT cardreader and Moneyplex. Regular crashes however when application is shutdown or cardreader unplugged, ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: pcscd 1.8.14-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 AssertionMessage: *** Error in `/usr/sbin/pcscd': free(): corrupted unsorted chunks: 0x014d59a0 *** Date: Thu Oct 15 14:46:33 2015 ExecutablePath: /usr/sbin/pcscd InstallationDate: Installed on 2012-08-21 (1152 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcCmdline: /usr/sbin/pcscd --foreground --auto-exit ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: pcsc-lite StacktraceTop: select () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x402f60, argc=3, argv=0x7ffc375ce0b8, init=, fini=, rtld_fini=, stack_end=0x7ffc375ce0a8) at libc-start.c:289 _start () Title: pcscd assert failure: *** Error in `/usr/sbin/pcscd': free(): corrupted unsorted chunks: 0x014d59a0 *** UpgradeStatus: Upgraded to wily on 2015-10-03 (14 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1507190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554570] Re: package libpcsclite1 1.8.14-1ubuntu1 [modified: usr/share/doc/libpcsclite1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc
** Changed in: pcsc-lite (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1554570 Title: package libpcsclite1 1.8.14-1ubuntu1 [modified: usr/share/doc/libpcsclite1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from other instances of package libpcsclite1:i386 Status in pcsc-lite package in Ubuntu: Incomplete Bug description: I was trying to install a smart card reader to a digital certificate. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libpcsclite1 1.8.14-1ubuntu1 [modified: usr/share/doc/libpcsclite1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 AptOrdering: libpcsclite1: Install libpcsclite1: Configure libpcsclite1: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Mar 8 12:13:18 2016 Dependencies: gcc-5-base 5.2.1-22ubuntu2 libc6 2.21-0ubuntu4.1 libgcc1 1:5.2.1-22ubuntu2 DpkgTerminalLog: Preparing to unpack .../libpcsclite1_1.8.14-1ubuntu1_i386.deb ... Unpacking libpcsclite1:i386 (1.8.14-1ubuntu1) over (1.8.5-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libpcsclite1_1.8.14-1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from other instances of package libpcsclite1:i386 DuplicateSignature: package:libpcsclite1:1.8.14-1ubuntu1 [modified: usr/share/doc/libpcsclite1/changelog.Debian.gz]:trying to overwrite shared '/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from other instances of package libpcsclite1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from other instances of package libpcsclite1:i386 InstallationDate: Installed on 2016-03-08 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: pcsc-lite Title: package libpcsclite1 1.8.14-1ubuntu1 [modified: usr/share/doc/libpcsclite1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libpcsclite1/changelog.Debian.gz', which is different from other instances of package libpcsclite1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1554570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1532455] Re: NetworkManager crashed with SIGSEGV
*** This bug is a duplicate of bug 1496741 *** https://bugs.launchpad.net/bugs/1496741 ** Attachment removed: "nmcli-con.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532455/+attachment/4546946/+files/nmcli-con.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532455/+attachment/4546945/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1532455 Title: NetworkManager crashed with SIGSEGV Status in network-manager package in Ubuntu: New Bug description: NetworkManager crashes whenever I have wifi enabled. My card is a Intel Centrino Advanced-N 6205 ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.2 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sat Jan 9 15:38:10 2016 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1449088802 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-19 (235 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SegvAnalysis: Segfault happened at: 0x497b07: mov(%rax),%rsi PC (0x00497b07) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: NetworkManager crashed with SIGSEGV UpgradeStatus: Upgraded to wily on 2015-10-29 (72 days ago) UserGroups: pkcs11 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1496741] Re: NetworkManager crashed with SIGSEGV
I just started experiencing this today, with no change in my hardware or software :/ Blowing away /etc/NetworkManager/ didn't fix anything, sadly. ** Attachment removed: "nmcli-con.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1496741/+attachment/4466659/+files/nmcli-con.txt ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1496741 Title: NetworkManager crashed with SIGSEGV Status in network-manager package in Ubuntu: Confirmed Bug description: It shows NetworkManager crashed when Ubuntu 15.10 started. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: i386 Date: Thu Sep 17 01:22:05 2015 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2011-12-01 (1385 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.13 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en PATH=(custom, no user) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SegvAnalysis: Segfault happened at: 0x80d83fc: mov(%eax),%eax PC (0x080d83fc) ok source "(%eax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: NetworkManager crashed with SIGSEGV UpgradeStatus: Upgraded to wily on 2015-08-12 (36 days ago) UserGroups: nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH wlan0wifi connected /org/freedesktop/NetworkManager/Devices/2 vodafoneE509 af9db9ab-35e5-40d8-ac17-06a719f176f5 /org/freedesktop/NetworkManager/ActiveConnection/0 ttyACM0 gsm disconnected /org/freedesktop/NetworkManager/Devices/3 ------ eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 ------ lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 ------ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1496741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1526646] [NEW] package systemd 219-7ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Possibly the same as Bug 1446219, but reporting anyhoo. This occurred when I did `telinit 1` and then `sudo apt-get install byobu` on a freshly-installed-that-day Ubuntu GNOME 15.04 system. Non-Ubuntu packages on this host: * google-chrome-stable * vagrant (from upstream) ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-39.44-generic 3.19.8-ckt9 Uname: Linux 3.19.0-39-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 Date: Wed Dec 16 07:33:03 2015 DuplicateSignature: package:systemd:219-7ubuntu6:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-12-16 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-39-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: systemd Title: package systemd 219-7ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET80WW (2.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET80WW(2.30):bd10/20/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- 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/1526646 Title: package systemd 219-7ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Possibly the same as Bug 1446219, but reporting anyhoo. This occurred when I did `telinit 1` and then `sudo apt-get install byobu` on a freshly-installed-that-day Ubuntu GNOME 15.04 system. Non-Ubuntu packages on this host: * google-chrome-stable * vagrant (from upstream) ProblemType: Package DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-39.44-generic 3.19.8-ckt9 Uname: Linux 3.19.0-39-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 Date: Wed Dec 16 07:33:03 2015 DuplicateSignature: package:systemd:219-7ubuntu6:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-12-16 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-39-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1.1 apt 1.0.9.7ubuntu4.2 SourcePackage: systemd Title: package systemd 219-7ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET80WW (2.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET80WW(2.30):bd10/20/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98417PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20AQCTO1WW dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1526646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** No longer affects: ubuntu ** Changed in: initramfs-tools (Ubuntu) Assignee: omesalim (omesalim) => (unassigned) -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1485089] Re: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100
*** This bug is a duplicate of bug 1485396 *** https://bugs.launchpad.net/bugs/1485396 ** This bug has been marked a duplicate of bug 1485396 impossible to upgrade package from vivid to wily because of maintainer script reference to upstart job without matching init script -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1485089 Title: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100 Status in isc-dhcp package in Ubuntu: New Bug description: install failure during do-release-upgrade from vivid to wily seems to be not a coincidence that maas-dhcp 1.7.6 failed immediately after. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: isc-dhcp-server 4.3.1-5ubuntu2.1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 Date: Fri Aug 14 12:10:01 2015 DhServerLeases: DuplicateSignature: package:isc-dhcp-server:4.3.1-5ubuntu2.1:subprocess new pre-removal script returned error exit status 100 ErrorMessage: subprocess new pre-removal script returned error exit status 100 InstallationDate: Installed on 2014-04-15 (485 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=2855a735-f240-4e8a-a2ef-2361fafe8731 ro SourcePackage: isc-dhcp Title: package isc-dhcp-server 4.3.1-5ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100 UpgradeStatus: Upgraded to wily on 2015-08-14 (0 days ago) upstart.isc-dhcp-server.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1485089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 370795] Re: update-manager is downloading all packages although its configured for security updates only
Thank you for reporting this bug to Ubuntu. Jaunty has reached EOL. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again. Do feel free to report any other bugs you may find. ** Changed in: software-properties (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/370795 Title: update-manager is downloading all packages although its configured for security updates only Status in software-properties package in Ubuntu: Incomplete Bug description: Binary package hint: update-manager It seems that update-manager is currently downloading packages in the background when not configured to do so. I have been feeling this is true for some time, and likely ever since I upgraded to Jaunty but I have no confirmation of this behaviour until now. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Package: update-manager 1:0.111.9 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: update-manager Uname: Linux 2.6.28-11-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/370795/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439313] Re: apt-key del keyid is case sensitive
Fixed in 1.0.9.9ubuntu1 ** Changed in: apt (Ubuntu) Status: Triaged => Fix Released ** Changed in: apt (Ubuntu) Milestone: vivid-updates => None -- 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/1439313 Title: apt-key del keyid is case sensitive Status in apt package in Ubuntu: Fix Released Status in apt package in Debian: Fix Released Bug description: Note: Confirmed on Ubuntu utopic with apt 1.0.9.2ubuntu2 Confirmed on Debian jessie apt 1.0.9.7 Behavior NOT seen on Ubuntu precise with apt 0.8.16~exp12ubuntu10.22 Behavior NOT seen on Debian wheezy apt 0.9.7.9+deb7u7 apt-key export is not case-sensitive to the hex keyid specified. Inconsistently, apt-key del is case-sensitive and won't match unless the hex keyid is uppercase. This is highly exacerbated by bug #1256565 which results in "OK" being printed and success being returned when apt-key del doesn't match anything. The user is reasonably left to conclude that the key has been deleted from the trusted keyring when it has not. Example: # apt-key export 7fac5991 -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1 mQGiBEXwb0YRBADQva2NLpYXxgjNkbuP0LnPoEXruGmvi3XMIxjEUFuGNCP4Rj/a kv2E5VixBP1vcQFDRJ+p1puh8NU0XERlhpyZrVMzzS/RdWdyXf7E5S8oqNXsoD1z fvmI+i9b2EhHAA19Kgw7ifV8vMa4tkwslEmcTiwiw8lyUl28Wh4Et8SxzwCggDcA feGqtn3PP5YAdD0km4S4XeMEAJjlrqPoPv2Gf//tfznY2UyS9PUqFCPLHgFLe80u QhI2U5jt6jUKN4fHauvR6z3seSAsh1YyzyZCKxJFEKXCCqnrFSoh4WSJsbFNc4PN b0V0SqiTCkWADZyLT5wll8sWuQ5ylTf3z1ENoHf+G3um3/wk/+xmEHvj9HCTBEXP 78X0A/0Tqlhc2RBnEf+AqxWvM8sk8LzJI/XGjwBvKfXe+l3rnSR2kEAvGzj5Sg0X 4XmfTg4Jl8BNjWyvm2Wmjfet41LPmYJKsux3g0b8yzQxeOA4pQKKAU3Z4+rgzGmf HdwCG5MNT2A5XxD/eDd+L4fRx0HbFkIQoAi1J3YWQSiTk15fw7RMR29vZ2xlLCBJ bmMuIExpbnV4IFBhY2thZ2UgU2lnbmluZyBLZXkgPGxpbnV4LXBhY2thZ2VzLWtl eW1hc3RlckBnb29nbGUuY29tPohjBBMRAgAjAhsDBgsJCAcDAgQVAggDBBYCAwEC HgECF4AFAkYVdn8CGQEACgkQoECDD3+sWZHKSgCfdq3HtNYJLv+XZleb6HN4zOcF AJEAniSFbuv8V5FSHxeRimHx25671az+uQINBEXwb0sQCACuA8HT2nr+FM5y/kzI A51ZcC46KFtIDgjQJ31Q3OrkYP8LbxOpKMRIzvOZrsjOlFmDVqitiVc7qj3lYp6U rgNVaFv6Qu4bo2/ctjNHDDBdv6nufmusJUWq/9TwieepM/cwnXd+HMxu1XBKRVk9 XyAZ9SvfcW4EtxVgysI+XlptKFa5JCqFM3qJllVohMmr7lMwO8+sxTWTXqxsptJo pZeKz+UBEEqPyw7CUIVYGC9ENEtIMFvAvPqnhj1GS96REMpry+5s9WKuLEaclWpd K3krttbDlY1NaeQUCRvBYZ8iAG9YSLHUHMTuI2oea07Rh4dtIAqPwAX8xn36JAYG 2vgLAAMFB/wKqaycjWAZwIe98Yt0qHsdkpmIbarD9fGiA6kfkK/UxjL/k7tmS4Vm CljrrDZkPSQ/19mpdRcGXtb0NI9+nyM5trweTvtPw+HPkDiJlTaiCcx+izg79Fj9 KcofuNb3lPdXZb9tzf5oDnmm/B+4vkeTuEZJ//IFty8cmvCpzvY+DAz1Vo9rA+Zn cpWY1n6z6oSS9AsyT/IFlWWBZZ17SpMHu+h4Bxy62+AbPHKGSujEGQhWq8ZRoJAT G0KSObnmZ7FwFWu1e9XFoUCt0bSjiJWTIyaObMrWu/LvJ3e9I87HseSJStfw6fki 5og9qFEkMrIrBCp3QGuQWBq/rTdMuwNFiEkEGBECAAkFAkXwb0sCGwwACgkQoECD D3+sWZF/WACfeNAu1/1hwZtUo1bR+MWiCjpvHtwAnA1R3IHqFLQ2X3xJ40XPuAyY /FJG =Quqp -END PGP PUBLIC KEY BLOCK- # apt-key del 7fac5991 OK # echo $? 0 # apt-key export 7fac5991 -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1 mQGiBEXwb0YRBADQva2NLpYXxgjNkbuP0LnPoEXruGmvi3XMIxjEUFuGNCP4Rj/a kv2E5VixBP1vcQFDRJ+p1puh8NU0XERlhpyZrVMzzS/RdWdyXf7E5S8oqNXsoD1z fvmI+i9b2EhHAA19Kgw7ifV8vMa4tkwslEmcTiwiw8lyUl28Wh4Et8SxzwCggDcA feGqtn3PP5YAdD0km4S4XeMEAJjlrqPoPv2Gf//tfznY2UyS9PUqFCPLHgFLe80u QhI2U5jt6jUKN4fHauvR6z3seSAsh1YyzyZCKxJFEKXCCqnrFSoh4WSJsbFNc4PN b0V0SqiTCkWADZyLT5wll8sWuQ5ylTf3z1ENoHf+G3um3/wk/+xmEHvj9HCTBEXP 78X0A/0Tqlhc2RBnEf+AqxWvM8sk8LzJI/XGjwBvKfXe+l3rnSR2kEAvGzj5Sg0X 4XmfTg4Jl8BNjWyvm2Wmjfet41LPmYJKsux3g0b8yzQxeOA4pQKKAU3Z4+rgzGmf HdwCG5MNT2A5XxD/eDd+L4fRx0HbFkIQoAi1J3YWQSiTk15fw7RMR29vZ2xlLCBJ bmMuIExpbnV4IFBhY2thZ2UgU2lnbmluZyBLZXkgPGxpbnV4LXBhY2thZ2VzLWtl eW1hc3RlckBnb29nbGUuY29tPohjBBMRAgAjAhsDBgsJCAcDAgQVAggDBBYCAwEC HgECF4AFAkYVdn8CGQEACgkQoECDD3+sWZHKSgCfdq3HtNYJLv+XZleb6HN4zOcF AJEAniSFbuv8V5FSHxeRimHx25671az+uQINBEXwb0sQCACuA8HT2nr+FM5y/kzI A51ZcC46KFtIDgjQJ31Q3OrkYP8LbxOpKMRIzvOZrsjOlFmDVqitiVc7qj3lYp6U rgNVaFv6Qu4bo2/ctjNHDDBdv6nufmusJUWq/9TwieepM/cwnXd+HMxu1XBKRVk9 XyAZ9SvfcW4EtxVgysI+XlptKFa5JCqFM3qJllVohMmr7lMwO8+sxTWTXqxsptJo pZeKz+UBEEqPyw7CUIVYGC9ENEtIMFvAvPqnhj1GS96REMpry+5s9WKuLEaclWpd K3krttbDlY1NaeQUCRvBYZ8iAG9YSLHUHMTuI2oea07Rh4dtIAqPwAX8xn36JAYG 2vgLAAMFB/wKqaycjWAZwIe98Yt0qHsdkpmIbarD9fGiA6kfkK/UxjL/k7tmS4Vm CljrrDZkPSQ/19mpdRcGXtb0NI9+nyM5trweTvtPw+HPkDiJlTaiCcx+izg79Fj9 KcofuNb3lPdXZb9tzf5oDnmm/B+4vkeTuEZJ//IFty8cmvCpzvY+DAz1Vo9rA+Zn cpWY1n6z6oSS9AsyT/IFlWWBZZ17SpMHu+h4Bxy62+AbPHKGSujEGQhWq8ZRoJAT G0KSObnmZ7FwFWu1e9XFoUCt0bSjiJWTIyaObMrWu/LvJ3e9I87HseSJStfw6fki 5og9qFEkMrIrBCp3QGuQWBq/rTdMuwNFiEkEGBECAAkFAkXwb0sCGwwACgkQoECD D3+sWZF/WACfeNAu1/1hwZtUo1bR+MWiCjpvHtwAnA1R3IHqFLQ2X3xJ40XPuAyY /FJG =Quqp -END PGP PUBLIC KEY BLOCK- # apt-key del 7FAC5991 OK # echo $? 0 # apt-key export 7fac5991 gpg: WARNING: nothing exported To manage notifications about this bug g
[Touch-packages] [Bug 561479] Re: Windows executable on unwritable removable media cannot execute with Wine due to lack of executable bit
Now this is fixed in mime-support, do we still need to make a change to udisks? If so, what is it? ** Changed in: udisks (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/561479 Title: Windows executable on unwritable removable media cannot execute with Wine due to lack of executable bit Status in One Hundred Papercuts: Triaged Status in udisks: New Status in mime-support package in Ubuntu: Fix Released Status in udisks package in Ubuntu: Incomplete Status in mime-support source package in Lucid: Won't Fix Status in udisks source package in Lucid: Won't Fix Status in mime-support source package in Maverick: Invalid Status in udisks source package in Maverick: Invalid Status in Baltix: New Bug description: I would like to install Far Cry from the DVD on Ubuntu Lucid but I wasn't able to do so because the installation executable was lacking the executable bit. I verified in fstab and there was the exec option on the cdrom line. Furthermore I was able to install Counter Strike from the CDROM (is there a difference between how DVD and CDROM are managed?). I had to umount the DVD and mount it again in an other folder, /usr/cd (/mnt/cd didn't work) to get the install executable work. == Regression details == Discovered in version: lucid Last known good version: karmic, which had no cautious-launcher == Workaround == Install Wine from the Wine Team PPA, which disables the use of cautious-launcher To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/561479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 302209] Re: software-properties only adds central Ubuntu repository for security updates (doesn't respect choice of local mirror)
** Changed in: software-properties (Ubuntu) Importance: Low => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/302209 Title: software-properties only adds central Ubuntu repository for security updates (doesn't respect choice of local mirror) Status in software-properties package in Ubuntu: Triaged Bug description: Binary package hint: synaptic When we remove than add again the security repository the result in source.list is always http://security and nor the URI of the server ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/sbin/synaptic Package: synaptic 0.62.1ubuntu10 ProcAttrCurrent: unconfined ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: synaptic Uname: Linux 2.6.27-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/302209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448725] Re: whoopsie prints "online" multiple times a second
** Description changed: from `sudo service whoopsie status`: ● whoopsie.service - crash report submission daemon -Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) -Active: active (running) since Sun 2015-04-26 10:42:33 PDT; 2min 51s ago - Main PID: 4112 (whoopsie) -CGroup: /system.slice/whoopsie.service -└─4112 /usr/bin/whoopsie -f + Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) + Active: active (running) since Sun 2015-04-26 10:42:33 PDT; 2min 51s ago + Main PID: 4112 (whoopsie) + CGroup: /system.slice/whoopsie.service + └─4112 /usr/bin/whoopsie -f Apr 26 10:45:04 cobalt whoopsie[4112]: [10:45:04] online Apr 26 10:45:05 cobalt whoopsie[4112]: [10:45:05] online Apr 26 10:45:12 cobalt whoopsie[4112]: [10:45:12] online Apr 26 10:45:13 cobalt whoopsie[4112]: [10:45:13] online Apr 26 10:45:19 cobalt whoopsie[4112]: [10:45:19] online Apr 26 10:45:20 cobalt whoopsie[4112]: [10:45:20] online Apr 26 10:45:22 cobalt whoopsie[4112]: [10:45:22] online Apr 26 10:45:23 cobalt whoopsie[4112]: [10:45:23] online Apr 26 10:45:24 cobalt whoopsie[4112]: [10:45:24] online Apr 26 10:45:24 cobalt whoopsie[4112]: [10:45:24] online + This behaviour is also experienced when running whoopsie from the + command line: - possibly a regression from 1217407 ? + root@cobalt:~# export CRASH_DB_URL=https://daisy.ubuntu.com; exec whoopsie -f + [10:49:17] Using lock path: /var/lock/whoopsie/lock + [10:49:17] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/3 + [10:49:17] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/3 + [10:49:17] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/3 + [10:49:17] online + [10:49:22] online + [10:49:23] online + [10:49:28] online + [10:49:28] online + [10:49:29] online + [10:49:30] online + [10:49:37] online + [10:49:38] online + [10:49:40] online + [10:49:41] online + [10:49:43] online + [10:49:44] online + [10:49:46] online + [10:49:46] online + [10:49:47] online + + Possibly a regression from bug #1217407 ? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: whoopsie 0.2.44 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 .var.log.upstart.whoopsie.log: Error: [Errno 13] Permission denied: '/var/log/upstart/whoopsie.log' ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 Date: Sun Apr 26 10:44:31 2015 InstallationDate: Installed on 2015-03-19 (38 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: Upgraded to vivid on 2015-04-18 (7 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1448725 Title: whoopsie prints "online" multiple times a second Status in whoopsie package in Ubuntu: New Bug description: from `sudo service whoopsie status`: ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2015-04-26 10:42:33 PDT; 2min 51s ago Main PID: 4112 (whoopsie) CGroup: /system.slice/whoopsie.service └─4112 /usr/bin/whoopsie -f Apr 26 10:45:04 cobalt whoopsie[4112]: [10:45:04] online Apr 26 10:45:05 cobalt whoopsie[4112]: [10:45:05] online Apr 26 10:45:12 cobalt whoopsie[4112]: [10:45:12] online Apr 26 10:45:13 cobalt whoopsie[4112]: [10:45:13] online Apr 26 10:45:19 cobalt whoopsie[4112]: [10:45:19] online Apr 26 10:45:20 cobalt whoopsie[4112]: [10:45:20] online Apr 26 10:45:22 cobalt whoopsie[4112]: [10:45:22] online Apr 26 10:45:23 cobalt whoopsie[4112]: [10:45:23] online Apr 26 10:45:24 cobalt whoopsie[4112]: [10:45:24] online Apr 26 10:45:24 cobalt whoopsie[4112]: [10:45:24] online This behaviour is also experienced when running whoopsie from the command line: root@cobalt:~# export CRASH_DB_URL=https://daisy.ubuntu.com; exec whoopsie -f [10:49:17] Using lock path: /var/lock/whoopsie/lock [10:49:17] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/3 [10:49:17] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/3 [10:49:17] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/3 [10:49:17] online [10:49:22] online [10:49:23] online [10:49:28] online [10:49:28] online [10:49:29] online [10:49:30] online [10:49:37] online [10:49:38] online [10:49:40] online [10:49:41] online [10:49:43] online [10:49:44] online [10:49:46] online [10:49:46] online [10:49:47] online Possibly a regression from bug #1217407 ? ProblemType: Bug DistroRelease: Ubuntu 15
[Touch-packages] [Bug 1448725] [NEW] whoopsie prints "online" multiple times a second
Public bug reported: from `sudo service whoopsie status`: ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2015-04-26 10:42:33 PDT; 2min 51s ago Main PID: 4112 (whoopsie) CGroup: /system.slice/whoopsie.service └─4112 /usr/bin/whoopsie -f Apr 26 10:45:04 cobalt whoopsie[4112]: [10:45:04] online Apr 26 10:45:05 cobalt whoopsie[4112]: [10:45:05] online Apr 26 10:45:12 cobalt whoopsie[4112]: [10:45:12] online Apr 26 10:45:13 cobalt whoopsie[4112]: [10:45:13] online Apr 26 10:45:19 cobalt whoopsie[4112]: [10:45:19] online Apr 26 10:45:20 cobalt whoopsie[4112]: [10:45:20] online Apr 26 10:45:22 cobalt whoopsie[4112]: [10:45:22] online Apr 26 10:45:23 cobalt whoopsie[4112]: [10:45:23] online Apr 26 10:45:24 cobalt whoopsie[4112]: [10:45:24] online Apr 26 10:45:24 cobalt whoopsie[4112]: [10:45:24] online This behaviour is also experienced when running whoopsie from the command line: root@cobalt:~# export CRASH_DB_URL=https://daisy.ubuntu.com; exec whoopsie -f [10:49:17] Using lock path: /var/lock/whoopsie/lock [10:49:17] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/3 [10:49:17] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/3 [10:49:17] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/3 [10:49:17] online [10:49:22] online [10:49:23] online [10:49:28] online [10:49:28] online [10:49:29] online [10:49:30] online [10:49:37] online [10:49:38] online [10:49:40] online [10:49:41] online [10:49:43] online [10:49:44] online [10:49:46] online [10:49:46] online [10:49:47] online Possibly a regression from bug #1217407 ? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: whoopsie 0.2.44 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 .var.log.upstart.whoopsie.log: Error: [Errno 13] Permission denied: '/var/log/upstart/whoopsie.log' ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 Date: Sun Apr 26 10:44:31 2015 InstallationDate: Installed on 2015-03-19 (38 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: Upgraded to vivid on 2015-04-18 (7 days ago) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug autoreport-false third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1448725 Title: whoopsie prints "online" multiple times a second Status in whoopsie package in Ubuntu: New Bug description: from `sudo service whoopsie status`: ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2015-04-26 10:42:33 PDT; 2min 51s ago Main PID: 4112 (whoopsie) CGroup: /system.slice/whoopsie.service └─4112 /usr/bin/whoopsie -f Apr 26 10:45:04 cobalt whoopsie[4112]: [10:45:04] online Apr 26 10:45:05 cobalt whoopsie[4112]: [10:45:05] online Apr 26 10:45:12 cobalt whoopsie[4112]: [10:45:12] online Apr 26 10:45:13 cobalt whoopsie[4112]: [10:45:13] online Apr 26 10:45:19 cobalt whoopsie[4112]: [10:45:19] online Apr 26 10:45:20 cobalt whoopsie[4112]: [10:45:20] online Apr 26 10:45:22 cobalt whoopsie[4112]: [10:45:22] online Apr 26 10:45:23 cobalt whoopsie[4112]: [10:45:23] online Apr 26 10:45:24 cobalt whoopsie[4112]: [10:45:24] online Apr 26 10:45:24 cobalt whoopsie[4112]: [10:45:24] online This behaviour is also experienced when running whoopsie from the command line: root@cobalt:~# export CRASH_DB_URL=https://daisy.ubuntu.com; exec whoopsie -f [10:49:17] Using lock path: /var/lock/whoopsie/lock [10:49:17] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/3 [10:49:17] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/3 [10:49:17] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/3 [10:49:17] online [10:49:22] online [10:49:23] online [10:49:28] online [10:49:28] online [10:49:29] online [10:49:30] online [10:49:37] online [10:49:38] online [10:49:40] online [10:49:41] online [10:49:43] online [10:49:44] online [10:49:46] online [10:49:46] online [10:49:47] online Possibly a regression from bug #1217407 ? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: whoopsie 0.2.44 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 .var.log.upstart.whoopsie.log: Error: [Errno 13] Permission denied: '/var/log/upstart/whoopsie.log' ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 D
[Touch-packages] [Bug 1415983] [NEW] package mime-support 3.58ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
Public bug reported: - ProblemType: Package DistroRelease: Ubuntu 15.04 Package: mime-support 3.58ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 Date: Thu Jan 29 11:19:17 2015 DuplicateSignature: package:mime-support:3.58ubuntu1:subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2014-08-16 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: mime-support Title: package mime-support 3.58ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to vivid on 2015-01-21 (8 days ago) ** Affects: mime-support (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1415983 Title: package mime-support 3.58ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in mime-support package in Ubuntu: New Bug description: - ProblemType: Package DistroRelease: Ubuntu 15.04 Package: mime-support 3.58ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 Date: Thu Jan 29 11:19:17 2015 DuplicateSignature: package:mime-support:3.58ubuntu1:subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2014-08-16 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: mime-support Title: package mime-support 3.58ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: Upgraded to vivid on 2015-01-21 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1415983/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1249515] Re: regression with session-cleanup-script triggering without actual logins
On 17 August 2014 03:46, Borim <1249...@bugs.launchpad.net> wrote: > My problem was caused by a broken lightdm.conf > After fixing the configuration file the session-cleanup-script works as > intended. Thats why I mark this bug as Fix Released. This issue is still affecting other users, and isn't obviously caused by an issue in the lightdm.conf. Would you care to elaborate here? status confirmed ** Changed in: lightdm (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1249515 Title: regression with session-cleanup-script triggering without actual logins Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Description: In Ubuntu 13.10, session-cleanup scripts trigger before a session has started. Simply clicking between users at the login menu triggers the session cleanup script. In my particular configuration this triggers a logout script that runs rsync with the --delete flag. Clicking between users runs the risk of deleting good files rather than doing backups as in prior releases so I can't update all my computers until fixed. The example below replicates and visually shows the effect. While running, the user cannot login until it has completed and depending on what the logout script does it can cause problems. Configuration to Replicate: /etc/lightdm/lightdm.conf session-setup-script = /usr/bin/gnome-terminal --command "/bin/sleep 10" session-cleanup-script = /usr/bin/gnome-terminal --command "/bin/sleep 10" Version Information: `lsb_release -rd` Description: Ubuntu 13.10 Release: 13.10 `apt-cache policy lightdm` lightdm: Installed: 1.8.4-0ubuntu1 Candidate: 1.8.4-0ubuntu1 Version table: *** 1.8.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages 100 /var/lib/dpkg/status 1.8.2-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages Log information (while clicking between users at login screen): `cat /var/log/lightdm/lightdm.log` [+825.63s] DEBUG: Session pid=8564: Greeter start authentication for nixadm [+825.63s] DEBUG: Session pid=12697: Sending SIGTERM [+825.63s] DEBUG: Seat: Setting XDG_SEAT=seat0 [+825.63s] DEBUG: Session: Setting XDG_VTNR=7 [+825.63s] DEBUG: Session pid=29773: Started with service 'lightdm', username 'nixadm' [+825.63s] DEBUG: Session pid=12697: Terminated with signal 15 [+825.63s] DEBUG: Session: Failed during authentication [+825.63s] DEBUG: Seat: Session stopped [+825.64s] DEBUG: Launching process 29780: /usr/bin/gnome-terminal --command "/bin/sleep 10" [+835.82s] DEBUG: Process 29780 exited with return value 0 [+835.82s] DEBUG: Seat: Exit status of /usr/bin/gnome-terminal --command "/bin/sleep 10": 0 [+835.82s] DEBUG: Session pid=29773: Got 1 message(s) from PAM [+835.82s] DEBUG: Session pid=8564: Prompt greeter with 1 message(s) [+836.30s] DEBUG: Session pid=8564: Greeter start authentication for jason [+836.30s] DEBUG: Session pid=29773: Sending SIGTERM [+836.30s] DEBUG: Seat: Setting XDG_SEAT=seat0 [+836.30s] DEBUG: Session: Setting XDG_VTNR=7 [+836.31s] DEBUG: Session pid=29790: Started with service 'lightdm', username 'jason' [+836.31s] DEBUG: Session pid=29773: Terminated with signal 15 [+836.31s] DEBUG: Session: Failed during authentication [+836.31s] DEBUG: Seat: Session stopped [+836.32s] DEBUG: Launching process 29797: /usr/bin/gnome-terminal --command "/bin/sleep 10" [+846.47s] DEBUG: Process 29797 exited with return value 0 [+846.47s] DEBUG: Seat: Exit status of /usr/bin/gnome-terminal --command "/bin/sleep 10": 0 [+846.47s] DEBUG: Session pid=29790: Got 1 message(s) from PAM [+846.47s] DEBUG: Session pid=8564: Prompt greeter with 1 message(s) [+846.92s] DEBUG: Session pid=8564: Greeter start authentication for nixadm [+846.92s] DEBUG: Session pid=29790: Sending SIGTERM [+846.92s] DEBUG: Seat: Setting XDG_SEAT=seat0 [+846.92s] DEBUG: Session: Setting XDG_VTNR=7 [+846.92s] DEBUG: Session pid=30421: Started with service 'lightdm', username 'nixadm' [+846.93s] DEBUG: Session pid=29790: Terminated with signal 15 [+846.93s] DEBUG: Session: Failed during authentication [+846.93s] DEBUG: Seat: Session stopped [+846.94s] DEBUG: Launching process 30428: /usr/bin/gnome-terminal --command "/bin/sleep 10" [+857.08s] DEBUG: Process 30428 exited with return value 0 [+857.08s] DEBUG: Seat: Exit status of /usr/bin/gnome-terminal --command "/bin/sleep 10": 0 [+857.08s] DEBUG: Session pid=30421: Got 1 message(s) from PAM [+857.08s] DEBUG: Session pid=8564: Prompt greeter with 1 message(s) [+857.60s] DEBUG: Session pid=
