[Touch-packages] [Bug 1723105] Re: Upgrade to 1.28-1ubuntu2.2 fails because postrm script is a directory containing kernel modules
** Attachment added: "The other file in the /var/lib/dpkg/info/libidn11:amd64.postrm directory" https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1723105/+attachment/4968613/+files/llc2.ko -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1723105 Title: Upgrade to 1.28-1ubuntu2.2 fails because postrm script is a directory containing kernel modules Status in libidn package in Ubuntu: New Bug description: When trying to upgrade my Ubuntu 14.04.5 LTS server using the command sudo apt-get dist-upgrade, the upgrade consistently failed while trying to upgrade libidn11 to version 1.28-1ubuntu2.2 with the following error message: unable to install (supposed) new info file `/var/lib/dpkg/tmp.ci/postrm': Is a directory I determined that instead of being a script, /var/lib/dpkg/info/libidn11:amd64.postrm was in fact a directory! It contained two kernel modules, llc.ko and llc2.lo. I will attach the two files. To get the package to install and the upgrade operation to proceed, I renamed /var/lib/dpkg/info/libidn11:amd64.postrm to /var/lib/dpkg/info/libidn11:amd64.postrm.bak, after which a renewed dist-upgrade proceeded without any warnings or errors. After the installation /var/lib/dpkg/info/libidn11:amd64.postrm once again existed, and is now a script, as expected. What gives? Is this a bug in either this or the previous version of libidn? Is it now correctly installed? Was I hacked (I get a bit nervous when executable files spontaneously appear in random places)? I scanned the two files with virustotal.com, and it found nothing, but I don't think that means much. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libidn11 1.28-1ubuntu2.2 ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39 Uname: Linux 3.13.0-129-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 Date: Thu Oct 12 14:41:57 2017 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.13 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.13 SourcePackage: libidn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1723105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723105] Re: Upgrade to 1.28-1ubuntu2.2 fails because postrm script is a directory containing kernel modules
** Attachment added: "One of the files in the /var/lib/dpkg/info/libidn11:amd64.postrm directory" https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1723105/+attachment/4968612/+files/llc.ko -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1723105 Title: Upgrade to 1.28-1ubuntu2.2 fails because postrm script is a directory containing kernel modules Status in libidn package in Ubuntu: New Bug description: When trying to upgrade my Ubuntu 14.04.5 LTS server using the command sudo apt-get dist-upgrade, the upgrade consistently failed while trying to upgrade libidn11 to version 1.28-1ubuntu2.2 with the following error message: unable to install (supposed) new info file `/var/lib/dpkg/tmp.ci/postrm': Is a directory I determined that instead of being a script, /var/lib/dpkg/info/libidn11:amd64.postrm was in fact a directory! It contained two kernel modules, llc.ko and llc2.lo. I will attach the two files. To get the package to install and the upgrade operation to proceed, I renamed /var/lib/dpkg/info/libidn11:amd64.postrm to /var/lib/dpkg/info/libidn11:amd64.postrm.bak, after which a renewed dist-upgrade proceeded without any warnings or errors. After the installation /var/lib/dpkg/info/libidn11:amd64.postrm once again existed, and is now a script, as expected. What gives? Is this a bug in either this or the previous version of libidn? Is it now correctly installed? Was I hacked (I get a bit nervous when executable files spontaneously appear in random places)? I scanned the two files with virustotal.com, and it found nothing, but I don't think that means much. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libidn11 1.28-1ubuntu2.2 ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39 Uname: Linux 3.13.0-129-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 Date: Thu Oct 12 14:41:57 2017 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.13 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.13 SourcePackage: libidn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1723105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723105] [NEW] Upgrade to 1.28-1ubuntu2.2 fails because postrm script is a directory containing kernel modules
Public bug reported: When trying to upgrade my Ubuntu 14.04.5 LTS server using the command sudo apt-get dist-upgrade, the upgrade consistently failed while trying to upgrade libidn11 to version 1.28-1ubuntu2.2 with the following error message: unable to install (supposed) new info file `/var/lib/dpkg/tmp.ci/postrm': Is a directory I determined that instead of being a script, /var/lib/dpkg/info/libidn11:amd64.postrm was in fact a directory! It contained two kernel modules, llc.ko and llc2.lo. I will attach the two files. To get the package to install and the upgrade operation to proceed, I renamed /var/lib/dpkg/info/libidn11:amd64.postrm to /var/lib/dpkg/info/libidn11:amd64.postrm.bak, after which a renewed dist-upgrade proceeded without any warnings or errors. After the installation /var/lib/dpkg/info/libidn11:amd64.postrm once again existed, and is now a script, as expected. What gives? Is this a bug in either this or the previous version of libidn? Is it now correctly installed? Was I hacked (I get a bit nervous when executable files spontaneously appear in random places)? I scanned the two files with virustotal.com, and it found nothing, but I don't think that means much. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libidn11 1.28-1ubuntu2.2 ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39 Uname: Linux 3.13.0-129-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 Date: Thu Oct 12 14:41:57 2017 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.13 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.13 SourcePackage: libidn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libidn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1723105 Title: Upgrade to 1.28-1ubuntu2.2 fails because postrm script is a directory containing kernel modules Status in libidn package in Ubuntu: New Bug description: When trying to upgrade my Ubuntu 14.04.5 LTS server using the command sudo apt-get dist-upgrade, the upgrade consistently failed while trying to upgrade libidn11 to version 1.28-1ubuntu2.2 with the following error message: unable to install (supposed) new info file `/var/lib/dpkg/tmp.ci/postrm': Is a directory I determined that instead of being a script, /var/lib/dpkg/info/libidn11:amd64.postrm was in fact a directory! It contained two kernel modules, llc.ko and llc2.lo. I will attach the two files. To get the package to install and the upgrade operation to proceed, I renamed /var/lib/dpkg/info/libidn11:amd64.postrm to /var/lib/dpkg/info/libidn11:amd64.postrm.bak, after which a renewed dist-upgrade proceeded without any warnings or errors. After the installation /var/lib/dpkg/info/libidn11:amd64.postrm once again existed, and is now a script, as expected. What gives? Is this a bug in either this or the previous version of libidn? Is it now correctly installed? Was I hacked (I get a bit nervous when executable files spontaneously appear in random places)? I scanned the two files with virustotal.com, and it found nothing, but I don't think that means much. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libidn11 1.28-1ubuntu2.2 ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39 Uname: Linux 3.13.0-129-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: amd64 Date: Thu Oct 12 14:41:57 2017 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.13 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.13 SourcePackage: libidn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1723105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked
This is still happening on 14.04. I too have multiple monitors, with the middle one being the main monitor. There have been other programs which can't cope with that, perhaps it has something to do with this problem as well? It would be quite nice to have it confirmed for trusty. It only shows as nominated above. I don't know what that means, but it definitely isn't fixed on 14.04... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1003950 Title: launcher does not show minimized update manager while clicked Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Fix Released Status in unity package in Ubuntu: Fix Released Status in update-manager package in Ubuntu: Confirmed Status in unity source package in Precise: Fix Released Status in update-manager source package in Precise: Confirmed Status in unity source package in Quantal: Fix Released Status in update-manager source package in Quantal: Confirmed Bug description: Update manager is showing up in the dock but I can click on the icon all day and nothing happens. Similarly if I do Super-S or Super-W it doesn't show up anywhere. Even if I alt-tab to the application nothing shows up. This happens only when update manager runs on its own. If I kill it and then launch it myself it comes to the foreground just fine. I'm not 100% sure whether this is a unity, compiz, or update-manager bug but so far my bet is on unity. =Original Report= Bug #877444 is showing again in latest updates, please re-open it. This is the exact same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1003950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
