[Touch-packages] [Bug 1972159] Re: systemd-oomd frequently kills firefox and visual studio code
This is also occuring on Ubuntu Server on VPS. I have 7x Ubuntu 22.04 VPSses with 1 GB physical RAM and a 3GB swap file. The programs I'm running get killed which stops production even though the swap file is far from full. -- 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/1972159 Title: systemd-oomd frequently kills firefox and visual studio code Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Kinetic: Confirmed Status in systemd package in Fedora: Unknown Bug description: Since I installed Ubuntu 22.04, firefox and visual studio code are frequently killed by systemd-oomd (every 2hours). I have 8 GB memory and never experienced this before the upgrade to Ubuntu 22.04. I thus assume that the claim that there is not enough memory is abusive. Did 64GB of memory become the minimum requirement to run Ubuntu ? The second problem is that it gives a very bad user experience which is critical for new Ubuntu users. There should be a warning prior killing apps to give the opportunity to save the app data. There should at least be an apologize and an explanation after killing the app. The current behavior gives the impression that Ubuntu 22.04 is unreliable and unsafe to use which is a problem for an LTS release that many people might want to use for critical production context. There might be a configuration problem with systemd-oomd or simply a bogus behavior. I would recommend to disable it or remove it completely until this problem is resolved. This is what I will do for myself because I have work to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1972159/+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 1773859] Re: upgrades to 18.04 fail
Can confirm that these steps BEFORE REBOOTING lead to a working 18.04 system after the 16.04 upgrade fails. Maybe these steps could be added to the upgrade script In psudocode: if [ error due to systemd1.service ] then; sudo mv /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.bak sudo apt-get install -f sudo apt dist-upgrade sudo apt autoremove exit fi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial, ie. lxc launch ubuntu-daily:xenial test-shim-upgrade lxc exec test-shim-upgrade apt update apt install systemd-shim wget https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb apt install ./systemd-shim_10-3_amd64.deb sed 's/xenial/bionic/' -i /etc/apt/sources.list apt update apt install systemd this currently passes, however, systemd-shim remains installed. It should be removed instead. Apt install systemd should have lines like this: The following packages will be REMOVED: systemd-shim ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' ... [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 281580] Re: [Intrepid] New Bluetooth Wizard fails to pair with devices: reintroduce hidd
Isn't bluetoothctl the current alternative to hidd? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/281580 Title: [Intrepid] New Bluetooth Wizard fails to pair with devices: reintroduce hidd Status in Mactel Support: Invalid Status in bluez package in Ubuntu: Fix Released Bug description: Binary package hint: bluez With the latest updates to Intrepid testing, the new bluetooth device setup wizard (which is an excellent improvement over the previous setup methods) fails to pair with my Apple Keyboard (pre-aluminum, broadcom based). No debug information or error messages are given other than "failed to pair". Further making this an issue is the fact that the recent bluetooth updates also removed the hidd binary from Ubuntu (again). This method seems to be the only thing that works for Apple Bluetooth Keyboards recently: http://idebian.wordpress.com/2008/07/06/manage-hid-bluetooth-devices-in-linux/ Notice that it requires hci to be reset, but cannot use hid2hci to do this. The keyboard was working fine previous to the update using the method in the above link. Removing reliable and useful software from the repos that can be useful for workarounds when new software is introduced is not a good idea. The hidd binary has been removed several times from Ubuntu and each time it has been requested that it is put back. Please make this binary available in the repos via other means so that it can be used as a fallback in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/281580/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
I saved one 14.04.5 machine for this purpose. Will I be able to enabled -proposed for 14.04.5 even though it's now out of support? -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Fix Released Status in systemd source package in Trusty: New Status in landscape-client source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Committed Status in landscape-client source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10
This issue is also happening in Ubuntu 16.04LTS with backports enabled. So I think there is something foobar with systemd-resolved and not resolvconf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after update from 17.04 to 17.10 Status in Cubic: Won't Fix Status in resolvconf package in Ubuntu: Confirmed Bug description: After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS lookup on my wireless network connection did not work any more. As it seems, the file /etc/resolv.conf was static and contained wrong data assigned by the NetworkManager. When I changed the file content manually to nameserver 127.0.0.53 DNS lookup worked fine. After reboot, however, I had to repeat this operation since NetworkManager seems to have replaced the file content. Finally, I found a solution. Running sudo dpkg-reconfigure resolvconf the file /etc/resolv.conf was replaced by the link /etc/resolv.conf -> ../run/resolvconf/resolv.conf Now, the wireless network seems to work properly. Hence, there must be some kind of bug during the update process from Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured properly. Best regards, Artur ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: resolvconf 1.79ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 23:17:38 2017 InstallationDate: Installed on 2013-10-18 (1463 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cubic/+bug/1725840/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
So physically at the machine it was only possible to log into the command prompt. There is no graphical interface available. To top it off Network manager was stopped! Not very good for network-manager to be stopped right after an upgrade. sudo service network-manager restart started the network, where I could resume fixing the computer over ssh. sudo apt install -f is my first course of action. -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
Ok so this is still FUBAR but then on a higher level. The upgrade failed miserably see the attached file. I was able to ssh into the machine after the upgrade. ran dpkg --reconfigure -a as suggested see below then I tried to reboot. which was a big mistake. when I try to reconnect to the remote machine ssh: connect to host remotemachine port 22: No route to host This is terrible. ssh should be like the first thing started always. even grub should have some kind of ssh feature so if the grub menu shows one could fix that remotely. Now I have a unusable machine and have to go physically to the location to try and reinstall everything by hand. == sudo shutdown --reboot 1 Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to start reboot.target: Failed to setup environment correctly See system logs and 'systemctl status reboot.target' for details. = It found too many errors to continue Errors found when configuring: libvlc5 libnss-winbind:amd64 ppp network-manager-pptp cups cups-daemon cups-core-drivers libpam-winbind:amd64 smbclient udev gnome-bluetooth libwayland-egl1-mesa:amd64 samba vlc-plugin-notify samba-common-bin bluez indicator-bluetooth network-manager-pptp-gnome hplip pulseaudio mountall unity-control-center printer-driver-hpcups libcogl20:amd64 initramfs-tools-core printer-driver-postscript-hp lvm2 libtotem0:amd64 libwebkit2gtk-4.0-37:amd64 libcheese-gtk25:amd64 libcanberra-pulse:amd64 libsolid4 initramfs-tools udisks2 upower xserver-xorg-input-vmmouse gnome-control-center libgtk-3-0:amd64 xserver-xorg-core gstreamer1.0-plugins-bad:amd64 winbind xserver-xorg-video-radeon libpeas-1.0-0:amd64 plymouth xserver-xorg libgstreamer-plugins-bad1.0-0:amd64 bamfdaemon xfce4-power-manager gnome-system-monitor network-manager kdelibs5-plugins Stopped configuring too many errors === ** Attachment added: "The upgrade file from Trust to Xenial from Landscape" https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+attachment/5206437/+files/Upgrade_Trusty-Xenial.result.txt -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
One quick little rant. Landscape is supposed to be Enterprise Grade software. I should be able to upgrade the releases of an entire farm of machines. This has been broken since the first time I tried this feature with Landscape. -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
I'm going to upgrade a system from 14.04.5 to 16.04.x tomorrow at 10:00AM CEST so I'll let you know the results. -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: In Progress Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
I have still have two machines that need upgrading from 14.04 -> 16.04 -> 18.04. I want to replace them and test the upgrade in the lab. The upgrade from 16.04->18.04 also fails. I'll report it in a new ticket. -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in landscape-client source package in Bionic: New Status in systemd source package in Bionic: Confirmed Status in landscape-client source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: https://github.com/systemd/systemd/pull/10061 [Impact] * When logind is not available, shutdown command fails to schedule a shutdown, and despite its intentions to immediately shutdown, does not do so. [Test Case] sudo systemctl mask systemd-logind.service sudo systemctl stop systemd-logind.service shutdown +1 The expectation is that system goes to shutdown. It is buggy if the system remains up - i.e. command returns to shell with exit code 1. [Regression Potential] * It is a corner case to run against systemd-shim logind / or logind not otherwise available. The function still performs a clean-shutdown, and should not cause loss of work. [Other Info] * Original bug report, running against systemd-shim/systemd-service post trusty->xenial upgrade, pre-reboot. Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1787853] [NEW] SystemD's default TimeoutStart and TimeoutStop are too long for Desktop
Public bug reported: On Ubuntu 18.04LTS starting and stopping the computer is extremely slow. SystemD defaults to a start time timeout of 90seconds and a stop time timeout of 90seconds in the file /etc/systemd/system.conf This is great for huge databased raid systems in some cloud datacenter but is very inappropriate for desktop computing where there is a human waiting for the process. Ubuntu Desktops need to have the /etc/systemd/system.conf Set to timeout in less than <10 seconds (the magic computer irritation moment for humans) out of the box, default for example: DefaultTimeoutStartSec=9s DefaultTimeoutStopSec=9s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 23:12:49 2018 InstallationDate: Installed on 2015-11-15 (1008 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/vg0-root ro noprompt persistent quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago) dmi.bios.date: 08/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X99 Extreme11 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme11:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.systemd.system.conf: 2018-08-19T23:11:55.785333 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1787853 Title: SystemD's default TimeoutStart and TimeoutStop are too long for Desktop Status in systemd package in Ubuntu: New Bug description: On Ubuntu 18.04LTS starting and stopping the computer is extremely slow. SystemD defaults to a start time timeout of 90seconds and a stop time timeout of 90seconds in the file /etc/systemd/system.conf This is great for huge databased raid systems in some cloud datacenter but is very inappropriate for desktop computing where there is a human waiting for the process. Ubuntu Desktops need to have the /etc/systemd/system.conf Set to timeout in less than <10 seconds (the magic computer irritation moment for humans) out of the box, default for example: DefaultTimeoutStartSec=9s DefaultTimeoutStopSec=9s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 19 23:12:49 2018 InstallationDate: Installed on 2015-11-15 (1008 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=/dev/mapper/vg0-root ro noprompt persistent quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago) dmi.bios.date: 08/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: X99 Extreme11 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd08/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX99Extreme11:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.systemd.system.conf: 2018-08-19T23:11:55.785333 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1787853/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1787294] Re: ".ico" icon files are shown as random noise
Upstream moved the bug to gtk-pixbuf as they knew of some problems with ico's in gdk-pixbuf https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/86 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise Status in gtk+3.0 package in Ubuntu: New Bug description: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1787294/+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 1787294] Re: ".ico" icon files are shown as random noise
Here is the Upstream Bug report https://gitlab.gnome.org/GNOME/gtk/issues/1279 side note: When will Launchpad be updated with rich images and header templates like the gitlab bug tracker? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise Status in gtk+3.0 package in Ubuntu: New Bug description: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1787294/+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 1192051] Re: plymouthd spinning at 100% CPU after I log in
Didn't help after all. Plymouth is still using 100% CPU on reboot. Now trying all the suggestions in https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1536771 Disabled plymouth in Grub and dpkg-reconfigured it. -- 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/1192051 Title: plymouthd spinning at 100% CPU after I log in Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: plymouthd spinning at 100% CPU. Probably triggered by use of this PPA: https://launchpad.net/~mir-team/+archive/system-compositor-testing although that does not change Plymouth. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: plymouth 0.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Tue Jun 18 15:06:38 2013 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd InstallationDate: Installed on 2013-06-11 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611) MachineType: LENOVO 4286CTO MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) 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:bvr8DET68WW(1.38):bd04/11/2013: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/lightdm/+bug/1192051/+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 1192051] Re: plymouthd spinning at 100% CPU after I log in
I found the conflict with the eGalax Touch Daemon driver. I moved the driver startup from /etc/init.d/eGtouch.sh to userspace as I don't need the touchscreen at login. The strange thing is I have 17 machines with this configuration and only one is exhibiting this behaviour with plymouthd -- 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/1192051 Title: plymouthd spinning at 100% CPU after I log in Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: plymouthd spinning at 100% CPU. Probably triggered by use of this PPA: https://launchpad.net/~mir-team/+archive/system-compositor-testing although that does not change Plymouth. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: plymouth 0.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Tue Jun 18 15:06:38 2013 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd InstallationDate: Installed on 2013-06-11 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611) MachineType: LENOVO 4286CTO MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) 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:bvr8DET68WW(1.38):bd04/11/2013: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/lightdm/+bug/1192051/+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 1192051] Re: plymouthd spinning at 100% CPU after I log in
I've attached an apport report of the runaway process ** Attachment added: "apport.plymouth.b8ut5mm8.apport" https://bugs.launchpad.net/lightdm/+bug/1192051/+attachment/5103196/+files/apport.plymouth.b8ut5mm8.apport -- 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/1192051 Title: plymouthd spinning at 100% CPU after I log in Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: plymouthd spinning at 100% CPU. Probably triggered by use of this PPA: https://launchpad.net/~mir-team/+archive/system-compositor-testing although that does not change Plymouth. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: plymouth 0.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Tue Jun 18 15:06:38 2013 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd InstallationDate: Installed on 2013-06-11 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611) MachineType: LENOVO 4286CTO MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) 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:bvr8DET68WW(1.38):bd04/11/2013: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/lightdm/+bug/1192051/+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 1192051] Re: plymouthd spinning at 100% CPU after I log in
There is a regression of this bug in 16.04.4LTS Linux computer 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 388 root 20 0 201472 100776 8516 R 95,7 2,9 19:57.46 plymouthd ii liblightdm-gobject-1-0:amd64 1.18.3-0ubuntu1.1 amd64LightDM GObject client library ii lightdm 1.18.3-0ubuntu1.1 amd64Display Manager -- 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/1192051 Title: plymouthd spinning at 100% CPU after I log in Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: plymouthd spinning at 100% CPU. Probably triggered by use of this PPA: https://launchpad.net/~mir-team/+archive/system-compositor-testing although that does not change Plymouth. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: plymouth 0.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Tue Jun 18 15:06:38 2013 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth ExecutablePath: /sbin/plymouthd InstallationDate: Installed on 2013-06-11 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130611) MachineType: LENOVO 4286CTO MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb 1 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-6-generic root=UUID=25c27832-0efa-4fc4-8a14-41af68d008dc ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) 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:bvr8DET68WW(1.38):bd04/11/2013: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/lightdm/+bug/1192051/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
Could we please use $ systemctl reboot $ systemctl -f reboot $ systemctl -ff reboot instead of poweroff. My machines are spread all around the country I live in. I don't want to have to drive hundreds of kilometers to go around to turn on all my machines by hand after the upgrade. Thanks! -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Incomplete Bug description: Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1551022] Re: mouse pointer leaves trail
Regression in 16.04.2 this bug has come back. Using Intel i915 driver on a Intel J3160 processor. Connection is dual monitor VGA + HDMI What do you need qua logging or actions to solve this issue? ** Attachment added: "Mouse Pointer Trails" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551022/+attachment/4845654/+files/MousePointerTrails.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1551022 Title: mouse pointer leaves trail Status in xorg package in Ubuntu: Expired Bug description: In my desktop system Kubuntu 15.10 I have the integrated graphic card (Intel HD3000) and a discrete graphic card (Nvidia GTX 550). Some days ago I attached a monitor on the iGPU and enabled it, giving me a triple head system (two monitors on the Nvidia and one on the Intel). From that moment, the mouse pointer started to leave a trail when it pass over something that is animating. I'm using nouveau for the nvidia card. I tried to upgrade to Kubuntu 16.04, but it gives me the same glitch. --- ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: 2016-02-24 01:06:09,804 DEBUG enabling apt cron job DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:844d] NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GF116 [GeForce GTX 550 Ti] [19da:5194] InstallationDate: Installed on 2015-11-19 (106 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: System manufacturer System Product Name Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic root=UUID=679d8ad1-4664-4abd-a80a-3ac9339425bb ro quiet splash nomdmonddf nomdmonisw irqnodebug vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Tags: xenial ubuntu single-occurrence reproducible has-workaround Uname: Linux 4.4.0-10-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 07/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3707 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-V dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3707:bd07/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-V:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1551022/+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 1392064] Re: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf
Solved by using the proprietary non-free driver from eGalax http://www.eeti.com.tw/drivers_Linux.html OpenSource and multiple displays where one is a touchscreen still don't get along very well yet. -- 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/1392064 Title: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf Status in lightdm package in Ubuntu: Expired Bug description: Setup: Ubuntu 14.04.1LTS IIyama 19" Pro-Lite Touchscreen Dell 17" regular monitor Due to another bug in the detection of input devices I had to write a script to tell Ubuntu which screen to use the touch from the touchscreen. so I put the following two entries into a basic bash script based on xinput list and xrandr -q #!/bin/bash xinput map-to-output 12 DVI-I-1 xrandr --output DVI-I-1 --primary = I added this script to /usr/share/lightdm/lightdm.conf.d/50-dualscreen-touch.conf and the contents look like this. [SeatDefaults] greeter-setup-script=/usr/local/bin/iiyama-touchscreen.sh session-setup-script=/usr/local/bin/iiyama-touchscreen.sh When I start a user session the touchscreen is calibrated and works normally with the touch happening on the touchscreen. As soon as I logoff into LightDM the touch calibration is off moving the pointer a logarithmic distance from the left of the touchscreen. As soon as I log in again, no problems, touch works great, log back out into the lightDM greeter and boom touch is all crazy. Can lightdm please detect that a touchscreen can only accept touch input and output to the touchscreen device?? Or at least have lightdm actually run the script when given? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 12 22:11:38 2014 InstallationDate: Installed on 2014-11-03 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmConfig: [SeatDefaults] autologin-user=boerske SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1392064/+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 1570065] Re: Package cgroup-lite: 1.11~ubuntu14.04.1 being held, unable to install
user@host:~$ apt-cache policy cgroup-lite cgroup-lite: Geïnstalleerd: 1.9 Kandidaat: 1.9 Versietabel: 1.11~ubuntu14.04.1 0 100 http://nl.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 Packages *** 1.9 0 500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1570065 Title: Package cgroup-lite: 1.11~ubuntu14.04.1 being held, unable to install Status in cgroup-lite package in Ubuntu: Confirmed Bug description: Trusty with 3.13 The latest cgroup-lite package was added to the backports repo and on installation I get the following error message: hostname:~$ apt-cache policy cgroup-lite cgroup-lite: Installed: (none) Candidate: 1.11~ubuntu14.04.1 Version table: 1.11~ubuntu14.04.1 0 amd64 Packages hostname:~$ sudo apt-get install cgroup-lite Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: checkbox-ng-service : Depends: checkbox-ng (= 0.3-2) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Not sure what is causing this, the 1.9 package works just fine - it's reproducible on many of systems, so it seems like a package bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1570065/+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 1570065] Re: Package cgroup-lite: 1.11~ubuntu14.04.1 being held, unable to install
I get the same error when upgrading using Landscape: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. The following packages have unmet dependencies: checkbox-ng-service: Depends: checkbox-ng (= 0.3-2) but 0.3-2 is to be installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1570065 Title: Package cgroup-lite: 1.11~ubuntu14.04.1 being held, unable to install Status in cgroup-lite package in Ubuntu: Confirmed Bug description: Trusty with 3.13 The latest cgroup-lite package was added to the backports repo and on installation I get the following error message: hostname:~$ apt-cache policy cgroup-lite cgroup-lite: Installed: (none) Candidate: 1.11~ubuntu14.04.1 Version table: 1.11~ubuntu14.04.1 0 amd64 Packages hostname:~$ sudo apt-get install cgroup-lite Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: checkbox-ng-service : Depends: checkbox-ng (= 0.3-2) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Not sure what is causing this, the 1.9 package works just fine - it's reproducible on many of systems, so it seems like a package bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1570065/+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 1398025] Re: Error messages like error: /dev/sdb: No medium found on booting
I'm getting the same message, it delays boot by 40 seconds. When the machine does finally boot into Ubuntu the device /dev/sdc is available and working normally. systemd-udevd[292]: error: /dev/sdc: No medium found Model: ATA FUJITSU MHZ2500B (scsi) Disk /dev/sdc: 500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: -- 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/1398025 Title: Error messages like error: /dev/sdb: No medium found on booting Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 15.04 dev with udev 217-1ubuntu1 and for a few days I'm seeing on every boot errors like error: /dev/sdb: No medium found. Here is the content of /var/log/boot.log: Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... error: /dev/sdb: No medium found error: /dev/sdc: No medium found error: /dev/sdd: No medium found error: /dev/sde: No medium found error: /dev/sdb: No medium found error: /dev/sdc: No medium found error: /dev/sdd: No medium found error: /dev/sde: No medium found done. Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. * Setting up X socket directories... [210G [204G[ OK ] * cryptswap1 (running)... [210G * Starting early crypto disks... [210G [204G[ OK ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1398025/+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 1392064] Re: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf
Here is a video of the bug, LightDM ignores the settings and moves the pointer to the right https://drive.google.com/file/d/0B4c5GbInagPqZEZvUlQxZ01qX0U/view?usp=sharing Here is a video of a working user session after logging in from LightDM, proving that the script works. https://drive.google.com/file/d/0B4c5GbInagPqNW5BU1BsWGV2cDA/view?usp=sharing -- 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/1392064 Title: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf Status in “lightdm” package in Ubuntu: New Bug description: Setup: Ubuntu 14.04.1LTS IIyama 19 Pro-Lite Touchscreen Dell 17 regular monitor Due to another bug in the detection of input devices I had to write a script to tell Ubuntu which screen to use the touch from the touchscreen. so I put the following two entries into a basic bash script based on xinput list and xrandr -q #!/bin/bash xinput map-to-output 12 DVI-I-1 xrandr --output DVI-I-1 --primary = I added this script to /usr/share/lightdm/lightdm.conf.d/50-dualscreen-touch.conf and the contents look like this. [SeatDefaults] greeter-setup-script=/usr/local/bin/iiyama-touchscreen.sh session-setup-script=/usr/local/bin/iiyama-touchscreen.sh When I start a user session the touchscreen is calibrated and works normally with the touch happening on the touchscreen. As soon as I logoff into LightDM the touch calibration is off moving the pointer a logarithmic distance from the left of the touchscreen. As soon as I log in again, no problems, touch works great, log back out into the lightDM greeter and boom touch is all crazy. Can lightdm please detect that a touchscreen can only accept touch input and output to the touchscreen device?? Or at least have lightdm actually run the script when given? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 12 22:11:38 2014 InstallationDate: Installed on 2014-11-03 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) LightdmConfig: [SeatDefaults] autologin-user=boerske SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1392064/+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 1383964] [NEW] package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: subproces nieuw pre-instal
Public bug reported: see attachment for the full log I ran this command in a terminal: sudo apt-get install vim-gui-common vim-common vim-scripts vim-youcompleteme apparently it didn't want to overwrite the documentation dpkg-divert: error: hernoemen omvat overschrijven van '/usr/share/vim/vim74/doc/help.txt.vim-tiny' met verschillend bestand '/usr/share/vim/vim74/doc/help.txt', niet toegelaten ProblemType: Package DistroRelease: Ubuntu 14.04 Package: vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Oct 22 04:07:41 2014 DuplicateSignature: package:vim-runtime:(not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags]:subproces nieuw pre-installation script gaf een foutwaarde 2 terug ErrorMessage: subproces nieuw pre-installation script gaf een foutwaarde 2 terug InstallationDate: Installed on 2014-06-13 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: vim Title: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: subproces nieuw pre-installation script gaf een foutwaarde 2 terug UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty ** Attachment added: full logging https://bugs.launchpad.net/bugs/1383964/+attachment/4241482/+files/vim_install_bug.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1383964 Title: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: subproces nieuw pre-installation script gaf een foutwaarde 2 terug Status in “vim” package in Ubuntu: New Bug description: see attachment for the full log I ran this command in a terminal: sudo apt-get install vim-gui-common vim-common vim-scripts vim-youcompleteme apparently it didn't want to overwrite the documentation dpkg-divert: error: hernoemen omvat overschrijven van '/usr/share/vim/vim74/doc/help.txt.vim-tiny' met verschillend bestand '/usr/share/vim/vim74/doc/help.txt', niet toegelaten ProblemType: Package DistroRelease: Ubuntu 14.04 Package: vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Oct 22 04:07:41 2014 DuplicateSignature: package:vim-runtime:(not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags]:subproces nieuw pre-installation script gaf een foutwaarde 2 terug ErrorMessage: subproces nieuw pre-installation script gaf een foutwaarde 2 terug InstallationDate: Installed on 2014-06-13 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: vim Title: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: subproces nieuw pre-installation script gaf een foutwaarde 2 terug UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1383964/+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 1383964] Re: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: subproces nieuw pre-installa
Now my package management is broken sudo apt-get install -f Adding 'diversion of /usr/share/vim/vim74/doc/help.txt to /usr/share/vim/vim74/doc/help.txt.vim-tiny by vim-runtime' dpkg-divert: error: hernoemen omvat overschrijven van '/usr/share/vim/vim74/doc/help.txt.vim-tiny' met verschillend bestand '/usr/share/vim/vim74/doc/help.txt', niet toegelaten dpkg: error processing archive /var/cache/apt/archives/vim-runtime_2%3a7.4.052-1ubuntu3_all.deb (--unpack): subproces nieuw pre-installation script gaf een foutwaarde 2 terug No diversion 'diversion of /usr/share/vim/vim74/doc/help.txt by vim-runtime', none removed. No diversion 'diversion of /usr/share/vim/vim74/doc/tags by vim-runtime', none removed. E: Sub-process /usr/bin/dpkg returned an error code (1) so I can't easily fix the problem either. :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1383964 Title: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: subproces nieuw pre-installation script gaf een foutwaarde 2 terug Status in “vim” package in Ubuntu: New Bug description: see attachment for the full log I ran this command in a terminal: sudo apt-get install vim-gui-common vim-common vim-scripts vim-youcompleteme apparently it didn't want to overwrite the documentation dpkg-divert: error: hernoemen omvat overschrijven van '/usr/share/vim/vim74/doc/help.txt.vim-tiny' met verschillend bestand '/usr/share/vim/vim74/doc/help.txt', niet toegelaten ProblemType: Package DistroRelease: Ubuntu 14.04 Package: vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Oct 22 04:07:41 2014 DuplicateSignature: package:vim-runtime:(not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags]:subproces nieuw pre-installation script gaf een foutwaarde 2 terug ErrorMessage: subproces nieuw pre-installation script gaf een foutwaarde 2 terug InstallationDate: Installed on 2014-06-13 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: vim Title: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: subproces nieuw pre-installation script gaf een foutwaarde 2 terug UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1383964/+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 1383964] Re: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: subproces nieuw pre-installa
fixed it. had a few old repositories from an older release in my apt/sources.list One day Ubuntu will be able to detect and automatically repair bad entries in the sources.list.d files. Unfortunatly that's not yet today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1383964 Title: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: subproces nieuw pre-installation script gaf een foutwaarde 2 terug Status in “vim” package in Ubuntu: New Bug description: see attachment for the full log I ran this command in a terminal: sudo apt-get install vim-gui-common vim-common vim-scripts vim-youcompleteme apparently it didn't want to overwrite the documentation dpkg-divert: error: hernoemen omvat overschrijven van '/usr/share/vim/vim74/doc/help.txt.vim-tiny' met verschillend bestand '/usr/share/vim/vim74/doc/help.txt', niet toegelaten ProblemType: Package DistroRelease: Ubuntu 14.04 Package: vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Oct 22 04:07:41 2014 DuplicateSignature: package:vim-runtime:(not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags]:subproces nieuw pre-installation script gaf een foutwaarde 2 terug ErrorMessage: subproces nieuw pre-installation script gaf een foutwaarde 2 terug InstallationDate: Installed on 2014-06-13 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: vim Title: package vim-runtime (not installed) [modified: usr/share/vim/vim74/doc/help.txt usr/share/vim/vim74/doc/tags] failed to install/upgrade: subproces nieuw pre-installation script gaf een foutwaarde 2 terug UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1383964/+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
