[Touch-packages] [Bug 2061977] Re: t64 migration: libgtk-3-0t64 has unmet dependencies, blocks >200 packages
root@kyle:~# dpkg -l | egrep "^h" hi atril 1.26.2-1 amd64MATE document viewer hi evince 45.0-1 amd64Document (PostScript, PDF) viewer hi gimp 2.10.36-2 amd64GNU Image Manipulation Program hi libpoppler-cpp0v5:amd6424.02.0-1ubuntu2 amd64PDF rendering library (CPP shared library) hi libpoppler-glib8:amd64 24.02.0-1ubuntu2 amd64PDF rendering library (GLib-based shared library) hi libpoppler134:amd6424.02.0-1ubuntu2 amd64PDF rendering library hi poppler-utils 24.02.0-1ubuntu2 amd64PDF utilities (based on Poppler) hi tumbler:amd64 4.18.1-1 amd64D-Bus thumbnailing service hi tumbler-common 4.18.1-1 all D-Bus thumbnailing service (common files) hi xubuntu-desktop2.262 amd64Xubuntu desktop system root@kyle:~# -- 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/2061977 Title: t64 migration: libgtk-3-0t64 has unmet dependencies, blocks >200 packages Status in gtk+3.0 package in Ubuntu: Invalid Bug description: lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 This unresolved dependency seems to be the main t64 migration blocker for the last weeks. I've manually thinned out the dependencies that "apt upgrade" can't solve but the libgtk-3-0t64/libreoffice-core unresolvable dependencies remain as main blocker. This has not changes for at least 2 weeks now. root@kyle:/# apt install vim-tiny Reading package lists... Done Building dependency tree... Done 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: libgtk-3-0t64 : Depends: libcups2 (>= 2.3~b6) Recommends: libgtk-3-bin libreoffice-core : Depends: libcups2t64 (>= 1.7.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. root@kyle:/# There are no held packages. root@kyle:/# apt update; apt upgrade Hit:1 http://dl.google.com/linux/earth/deb stable InRelease Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease Hit:3 http://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease Hit:4 https://download.tinkerforge.com/apt/ubuntu noble InRelease Hit:5 https://repo.steampowered.com/steam stable InRelease Hit:6 https://updates.signal.org/desktop/apt xenial InRelease Hit:7 https://updates.signal.org/desktop/apt artful InRelease Hit:8 https://mkvtoolnix.download/ubuntu mantic InRelease Hit:9 http://ppa.launchpad.net/yubico/stable/ubuntu kinetic InRelease Hit:10 http://security.ubuntu.com/ubuntu noble-security InRelease Hit:11 https://ppa.launchpadcontent.net/ubuntuhandbook1/handbrake/ubuntu mantic InRelease Hit:12 https://dl.google.com/linux/chrome/deb stable InRelease Hit:13 https://packages.microsoft.com/repos/ms-teams stable InRelease Hit:14 https://ppa.launchpadcontent.net/yubico/stable/ubuntu noble InRelease Hit:15 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/jammy pgadmin4 InRelease Hit:16 http://apt.postgresql.org/pub/repos/apt mantic-pgdg InRelease Hit:17
[Touch-packages] [Bug 2061977] Re: t64 migration: libgtk-3-0t64 has unmet dependencies, blocks >200 packages
never underestimate the might of of trusty old dselect to help untangle even the most complex dependencies where all other tools fail... -- 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/2061977 Title: t64 migration: libgtk-3-0t64 has unmet dependencies, blocks >200 packages Status in gtk+3.0 package in Ubuntu: Invalid Bug description: lsb_release -rd No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 This unresolved dependency seems to be the main t64 migration blocker for the last weeks. I've manually thinned out the dependencies that "apt upgrade" can't solve but the libgtk-3-0t64/libreoffice-core unresolvable dependencies remain as main blocker. This has not changes for at least 2 weeks now. root@kyle:/# apt install vim-tiny Reading package lists... Done Building dependency tree... Done 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: libgtk-3-0t64 : Depends: libcups2 (>= 2.3~b6) Recommends: libgtk-3-bin libreoffice-core : Depends: libcups2t64 (>= 1.7.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. root@kyle:/# There are no held packages. root@kyle:/# apt update; apt upgrade Hit:1 http://dl.google.com/linux/earth/deb stable InRelease Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease Hit:3 http://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease Hit:4 https://download.tinkerforge.com/apt/ubuntu noble InRelease Hit:5 https://repo.steampowered.com/steam stable InRelease Hit:6 https://updates.signal.org/desktop/apt xenial InRelease Hit:7 https://updates.signal.org/desktop/apt artful InRelease Hit:8 https://mkvtoolnix.download/ubuntu mantic InRelease Hit:9 http://ppa.launchpad.net/yubico/stable/ubuntu kinetic InRelease Hit:10 http://security.ubuntu.com/ubuntu noble-security InRelease Hit:11 https://ppa.launchpadcontent.net/ubuntuhandbook1/handbrake/ubuntu mantic InRelease Hit:12 https://dl.google.com/linux/chrome/deb stable InRelease Hit:13 https://packages.microsoft.com/repos/ms-teams stable InRelease Hit:14 https://ppa.launchpadcontent.net/yubico/stable/ubuntu noble InRelease Hit:15 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/jammy pgadmin4 InRelease Hit:16 http://apt.postgresql.org/pub/repos/apt mantic-pgdg InRelease Hit:17 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/mantic pgadmin4 InRelease Hit:18 http://ppa.launchpad.net/yubico/stable/ubuntu mantic InRelease Hit:19 http://apt.postgresql.org/pub/repos/apt noble-pgdg InRelease Hit:20 http://ppa.launchpad.net/yubico/stable/ubuntu noble InRelease Hit:21 http://archive.ubuntu.com/ubuntu mantic InRelease Hit:22 http://archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:23 http://archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:24 http://archive.ubuntu.com/ubuntu noble InRelease Hit:25 http://archive.ubuntu.com/ubuntu noble-updates InRelease Hit:26 http://archive.ubuntu.com/ubuntu noble-backports InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 210 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: alsa-utils atril coreutils evince gimp gir1.2-gst-plugins-base-1.0 gir1.2-javascriptcoregtk-4.1 gir1.2-webkit2-4.1 gstreamer1.0-gl gstreamer1.0-gtk3
[Touch-packages] [Bug 2061977] [NEW] t64 migration: libgtk-3-0t64 has unmet dependencies, blocks >200 packages
Public bug reported: lsb_release -rd No LSB modules are available. Description:Ubuntu Noble Numbat (development branch) Release:24.04 This unresolved dependency seems to be the main t64 migration blocker for the last weeks. I've manually thinned out the dependencies that "apt upgrade" can't solve but the libgtk-3-0t64/libreoffice-core unresolvable dependencies remain as main blocker. This has not changes for at least 2 weeks now. root@kyle:/# apt install vim-tiny Reading package lists... Done Building dependency tree... Done 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: libgtk-3-0t64 : Depends: libcups2 (>= 2.3~b6) Recommends: libgtk-3-bin libreoffice-core : Depends: libcups2t64 (>= 1.7.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. root@kyle:/# There are no held packages. root@kyle:/# apt update; apt upgrade Hit:1 http://dl.google.com/linux/earth/deb stable InRelease Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease Hit:3 http://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease Hit:4 https://download.tinkerforge.com/apt/ubuntu noble InRelease Hit:5 https://repo.steampowered.com/steam stable InRelease Hit:6 https://updates.signal.org/desktop/apt xenial InRelease Hit:7 https://updates.signal.org/desktop/apt artful InRelease Hit:8 https://mkvtoolnix.download/ubuntu mantic InRelease Hit:9 http://ppa.launchpad.net/yubico/stable/ubuntu kinetic InRelease Hit:10 http://security.ubuntu.com/ubuntu noble-security InRelease Hit:11 https://ppa.launchpadcontent.net/ubuntuhandbook1/handbrake/ubuntu mantic InRelease Hit:12 https://dl.google.com/linux/chrome/deb stable InRelease Hit:13 https://packages.microsoft.com/repos/ms-teams stable InRelease Hit:14 https://ppa.launchpadcontent.net/yubico/stable/ubuntu noble InRelease Hit:15 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/jammy pgadmin4 InRelease Hit:16 http://apt.postgresql.org/pub/repos/apt mantic-pgdg InRelease Hit:17 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/mantic pgadmin4 InRelease Hit:18 http://ppa.launchpad.net/yubico/stable/ubuntu mantic InRelease Hit:19 http://apt.postgresql.org/pub/repos/apt noble-pgdg InRelease Hit:20 http://ppa.launchpad.net/yubico/stable/ubuntu noble InRelease Hit:21 http://archive.ubuntu.com/ubuntu mantic InRelease Hit:22 http://archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:23 http://archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:24 http://archive.ubuntu.com/ubuntu noble InRelease Hit:25 http://archive.ubuntu.com/ubuntu noble-updates InRelease Hit:26 http://archive.ubuntu.com/ubuntu noble-backports InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 210 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: alsa-utils atril coreutils evince gimp gir1.2-gst-plugins-base-1.0 gir1.2-javascriptcoregtk-4.1 gir1.2-webkit2-4.1 gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio gstreamer1.0-vaapi gstreamer1.0-x hexchat hexchat-common hexchat-plugins hexchat-python3 hplip hplip-data hplip-gui imagemagick-6.q16 libatk-wrapper-java-jni libblockdev-nvme3 libfcgi-perl libfido2-1 libfluidsynth3 libglusterfs0 libgssapi-krb5-2 libgssapi-krb5-2:i386 libgstreamer-gl1.0-0 libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libhpmud0 libimage-magick-q16-perl
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
I also had to purge apport in order to get this under control. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly.
[Touch-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
With BIOS A25 and eoan it is still not fixed. -- 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/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in xorg package in Ubuntu: Incomplete Bug description: With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the display shuts off, it will not wake up anymore, and the screen stays dark. A cycle of the following will leave the display dark: xset dpms force off; sleep 30; xset dpms force on WORKAROUND: A restart of the Xserver will bring back the display. WORKAROUND: Don't allow DPMS to switch off the display: xset dpms 0 0 0 xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/+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 1667512] Re: update-initramfs hangs on upgrade, dpkg unusable, unbootable system
This problem also still exists with much newer kernels, for me with
4.15.0-12 on Ubuntu 18.04 (alpha)
diff -uN /var/lib/dpkg/info/initramfs-tools.postinst~
/var/lib/dpkg/info/initramfs-tools.postinst
--- /var/lib/dpkg/info/initramfs-tools.postinst~2018-02-20
22:34:46.0 +0100
+++ /var/lib/dpkg/info/initramfs-tools.postinst 2018-03-22 13:08:09.989213260
+0100
@@ -38,10 +38,10 @@
# Regenerate initramfs whenever we go to dpkg state `installed'
if [ "x$1" != xtriggered ]; then
# this activates the trigger, if triggers are working
- update-initramfs -u
+ update-initramfs -u -v
else
# force it to actually happen
- DPKG_MAINTSCRIPT_PACKAGE='' update-initramfs -u
+ DPKG_MAINTSCRIPT_PACKAGE='' update-initramfs -u -v
fi
# Automatically added by dh_installdeb/11.1.4ubuntu1
-
diff -uN /usr/sbin/update-initramfs~ /usr/sbin/update-initramfs
--- /usr/sbin/update-initramfs~ 2018-01-05 13:15:45.0 +0100
+++ /usr/sbin/update-initramfs 2018-03-22 13:11:34.440124524 +0100
@@ -158,7 +158,9 @@
mv -f "${initramfs}.new" "${initramfs}"
set_sha1
# Guard against an unclean shutdown
- sync
+ # The sync never returns and seems to deadlock for some reason
+ # so comment it out for the time beeing
+ #sync
else
mkinitramfs_return="$?"
remove_initramfs_bak
---
Also take sync out of commission in order to allow for a clean shutdown
(important: re-enable after the reboot!). Also give the system enough time to
sync all its buffers on its own before restarting.
cd /bin
mv sync sync.real
cp ls sync
This helped me before and now I have the deadlocked sync issue again.
root@charion:~# ps auxwww | grep sync
systemd+ 1949 0.0 0.0 146076 3364 ?Ssl 11:56 0:00
/lib/systemd/systemd-timesyncd
root 19420 0.0 0.0 7796 780 pts/7D+ 12:03 0:00 sync
root 22919 0.0 0.0 14756 1120 pts/2S+ 13:20 0:00 grep
--color=auto sync
So I'll try to restart and try to run the
update-initramfs -u -v manually with these changes and then try to finish the
apt-get upgrade
--
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/1667512
Title:
update-initramfs hangs on upgrade, dpkg unusable, unbootable system
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
At least four users, including myself, are having an issue with
update-initramfs hanging while updating ubuntu 16.04. The bug has been
documented while attempting an update to multiple kernel versions (
4.4.0-24, 4.4.0-62, 4.4.0-63). The bug causes any apt-get update or
install to fail, and may also lead to an unbootable system.
User #1 (me):
$ uname -a
Linux 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
$ sudo apt-get upgrade
Fetched 1,571 MB in 2min 9s (12.2 MB/s)
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 344634 files and directories currently installed.)
Preparing to unpack .../base-files_9.4ubuntu4.4_amd64.deb ...
Unpacking base-files (9.4ubuntu4.4) over (9.4ubuntu4.3) ...
Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for cracklib-runtime (2.9.2-1build2) ...
Processing triggers for install-info (6.1.0.dfsg.1-5) ...
Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
update-initramfs: Generating /boot/initrd.img-4.4.0-63-generic
Uh oh! Let's try to troubleshoot.
$ sudo killall dpkg
$ sudo dpkg --configure -a
Setting up initramfs-tools (0.122ubuntu8.8) ...
update-initramfs: deferring update (trigger activated)
Setting up base-files (9.4ubuntu4.4) ...
Installing new version of config file /etc/issue ...
Installing new version of config file /etc/issue.net ...
Installing new version of config file /etc/lsb-release ...
Setting up linux-image-4.4.0-63-generic (4.4.0-63.84) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
initrd.img(/boot/initrd.img-4.4.0-63-generic
) points to /boot/initrd.img-4.4.0-63-generic
(/boot/initrd.img-4.4.0-63-generic) -- doing nothing at
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
vmlinuz(/boot/vmlinuz-4.4.0-63-generic
) points to /boot/vmlinuz-4.4.0-63-generic
(/boot/vmlinuz-4.4.0-63-generic) -- doing nothing at
/var/lib/dpkg/info/linux-image-4.4.0-63-generic.postinst line 491.
Examining
[Touch-packages] [Bug 1450009] Re: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock
I am also still seeing this on my Dell M4800 (with Ubuntu 18.04 alpha) I have 2 monitors attached and the same issues as Gareth. -- 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/1450009 Title: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock Status in systemd package in Ubuntu: Fix Released Bug description: Using systemd as init system on a HP zbook15 notebook having 2 external monitors connected using a docking station and starting with lid closed the system goes to sleep after successfully booting and starting lightdm greeter. Sometimes there's enough time to enter username and password but system goes to sleep every time after a few seconds. The system can be woken up and used after this happens but it will not let me shutdown later. The problem is just present in docked situation starting with closed lid using systemd a init system. If notebook is used in non-docked situation with open lid and systemd the problem does not occur. Workaround: A switch back to upstart as init system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 14:46:09 2015 InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+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 1441253] Re: hanging suspend job prevents shutdown
This still exists in Ubuntu 18.04(alpha) I have the additional fun effect that my Dell M4800 laptop (lid closed, with 2 external monitors attached via docking station) suspends immediately after logging into the display manager (doesnt matter if it is gdm3 or lightdm) on boot. Only after waking up the laptop again I can start working. If the laptop sits idle for a little while, it will also suspend and them might or might now wake up again properly (the behaviour of gdm3 is worse here then lightdm). The laptop is configured NOT to suspend ine the Gnome Power settings. ** Attachment added: "Screenshot from 2018-03-18 20-29-38.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+attachment/5083420/+files/Screenshot%20from%202018-03-18%2020-29-38.png -- 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/1441253 Title: hanging suspend job prevents shutdown Status in systemd package in Ubuntu: Won't Fix Bug description: poweroff (systemd poweroff) and reboot no longer work running sudo sytemd poweroff generates this: Failed to start poweroff.target: Transaction is destructive. journal log also shows: Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive. Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Output of systemctl list-jobs JOB UNITTYPE STATE 6009 suspend.target start waiting 6010 systemd-suspend.service start running 6014 anacron-resume.service start waiting ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Tue Apr 7 18:32:27 2015 MachineType: Hewlett-Packard HP EliteBook 8560w ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@ SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+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 1441253] Re: hanging suspend job prevents shutdown
This still exists in Ubuntu 18.04(alpha) I have the additional fun effect that my Dell M4800 laptop (lid closed, with 2 external monitors attached via docking station) suspends immediately after logging into the display manager (doesnt matter if it is gdm3 or lightdm) on boot. Only after waking up the laptop again I can start working. If the laptop sits idle for a little while, it will also suspend and them might or might now wake up again properly (the behaviour of gdm3 is worse here then lightdm). The laptop is configured NOT to suspend ine the Gnome Power settings. ** Attachment added: "Screenshot from 2018-03-18 20-29-38.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+attachment/5083419/+files/Screenshot%20from%202018-03-18%2020-29-38.png -- 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/1441253 Title: hanging suspend job prevents shutdown Status in systemd package in Ubuntu: Won't Fix Bug description: poweroff (systemd poweroff) and reboot no longer work running sudo sytemd poweroff generates this: Failed to start poweroff.target: Transaction is destructive. journal log also shows: Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive. Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Output of systemctl list-jobs JOB UNITTYPE STATE 6009 suspend.target start waiting 6010 systemd-suspend.service start running 6014 anacron-resume.service start waiting ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Tue Apr 7 18:32:27 2015 MachineType: Hewlett-Packard HP EliteBook 8560w ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@ SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago) dmi.bios.date: 08/04/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.50 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+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 1756593] Re: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 143
Start of the log (above is only the tail end where it gets stuck during the cpio: root@charion:/boot# update-initramfs -u -k 4.15.0-12-generic -b /boot -t -v Keeping /boot/initrd.img-4.15.0-12-generic.dpkg-bak update-initramfs: Generating /boot/initrd.img-4.15.0-12-generic Copying module directory kernel/drivers/usb/host (excluding hwa-hc.ko sl811_cs.ko sl811-hcd.ko u132-hcd.ko whci-hcd.ko) Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/isp116x-hcd.ko Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/ssb/ssb.ko Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/ssb-hcd.ko Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/xhci-plat-hcd.ko Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/r8a66597-hcd.ko Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/oxu210hp-hcd.ko Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/max3421-hcd.ko Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/bcma/bcma.ko Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/bcma-hcd.ko Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/isp1362-hcd.ko Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/host/fotg210-hcd.ko Copying module directory kernel/drivers/usb/c67x00 Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/c67x00/c67x00.ko Copying module directory kernel/drivers/usb/chipidea Adding module /lib/modules/4.15.0-12-generic/kernel/drivers/usb/gadget/udc/udc-core.ko [...] -- 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/1756593 Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 143 Status in initramfs-tools package in Ubuntu: New Bug description: Adding library-link /lib/x86_64-linux-gnu/libcap-ng.so.0 Adding library /lib/x86_64-linux-gnu/libcap-ng.so.0.0.0 Adding binary /sbin/dumpe2fs Calling hook dmsetup Calling hook klibc-utils /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable dns: libnss_files: /lib/i386-linux-gnu/libnss_files.so.2 Adding library-link /lib/i386-linux-gnu/libnss_files.so.2 Adding library /lib/i386-linux-gnu/libnss_files-2.27.so dns: libnss_dns: /lib/i386-linux-gnu/libnss_dns.so.2 Adding library-link /lib/i386-linux-gnu/libnss_dns.so.2 Adding library /lib/i386-linux-gnu/libnss_dns-2.27.so dns: libresolv: /lib/i386-linux-gnu/libresolv.so.2 Adding library-link /lib/i386-linux-gnu/libresolv.so.2 Adding library /lib/i386-linux-gnu/libresolv-2.27.so Building cpio /boot/initrd.img-4.15.0-12-generic.new initramfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 17 21:17:40 2018 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 143 InstallationDate: Installed on 2018-02-28 (17 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 143 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1756593/+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 1756593] [NEW] package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 14
Public bug reported: Adding library-link /lib/x86_64-linux-gnu/libcap-ng.so.0 Adding library /lib/x86_64-linux-gnu/libcap-ng.so.0.0.0 Adding binary /sbin/dumpe2fs Calling hook dmsetup Calling hook klibc-utils /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable dns: libnss_files: /lib/i386-linux-gnu/libnss_files.so.2 Adding library-link /lib/i386-linux-gnu/libnss_files.so.2 Adding library /lib/i386-linux-gnu/libnss_files-2.27.so dns: libnss_dns: /lib/i386-linux-gnu/libnss_dns.so.2 Adding library-link /lib/i386-linux-gnu/libnss_dns.so.2 Adding library /lib/i386-linux-gnu/libnss_dns-2.27.so dns: libresolv: /lib/i386-linux-gnu/libresolv.so.2 Adding library-link /lib/i386-linux-gnu/libresolv.so.2 Adding library /lib/i386-linux-gnu/libresolv-2.27.so Building cpio /boot/initrd.img-4.15.0-12-generic.new initramfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 17 21:17:40 2018 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 143 InstallationDate: Installed on 2018-02-28 (17 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 143 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1756593 Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 143 Status in initramfs-tools package in Ubuntu: New Bug description: Adding library-link /lib/x86_64-linux-gnu/libcap-ng.so.0 Adding library /lib/x86_64-linux-gnu/libcap-ng.so.0.0.0 Adding binary /sbin/dumpe2fs Calling hook dmsetup Calling hook klibc-utils /usr/share/initramfs-tools/scripts/panic/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-bottom/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-bottom/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-block/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-top/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/local-premount/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-premount/ORDER ignored: not executable /usr/share/initramfs-tools/scripts/init-top/ORDER ignored: not executable dns: libnss_files: /lib/i386-linux-gnu/libnss_files.so.2 Adding library-link /lib/i386-linux-gnu/libnss_files.so.2 Adding library /lib/i386-linux-gnu/libnss_files-2.27.so dns: libnss_dns: /lib/i386-linux-gnu/libnss_dns.so.2 Adding library-link /lib/i386-linux-gnu/libnss_dns.so.2 Adding library /lib/i386-linux-gnu/libnss_dns-2.27.so dns: libresolv: /lib/i386-linux-gnu/libresolv.so.2 Adding library-link /lib/i386-linux-gnu/libresolv.so.2 Adding library /lib/i386-linux-gnu/libresolv-2.27.so Building cpio /boot/initrd.img-4.15.0-12-generic.new initramfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 17 21:17:40 2018 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 143 InstallationDate: Installed on 2018-02-28 (17 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
[Touch-packages] [Bug 1756437] [NEW] systemd starts suspend service on startup and gets stuck...
Public bug reported: root@charion:~# systemctl status ● charion State: starting Jobs: 2 queued Failed: 1 units Since: Fri 2018-03-16 20:37:37 CET; 39min ago CGroup: / ├─user.slice │ ├─user-122.slice │ │ ├─user@122.service │ │ │ ├─pulseaudio.service │ │ │ │ └─2981 /usr/bin/pulseaudio --daemonize=no │ │ │ ├─at-spi-dbus-bus.service [...] root@charion:~# systemctl list-jobs JOB UNITTYPE STATE 2076 systemd-suspend.service start running 2075 suspend.target start waiting 2 jobs listed. root@charion:~# On the console is visible: "A start job is running for Suspend" and the time it is already running. This is while I am logged into a gdm3/Gnome session. I've already deleted all snap packages which provided additional shutdown/suspend targets. I had those under suspicion initially. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 21:22:41 2018 InstallationDate: Installed on 2018-02-28 (16 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) MachineType: Dell Inc. Precision M4800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=UUID=d0075e29-dbce-40fe-8c81-b56b505b40b9 ro video=vesa:off vga=normal SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0PMFT3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/14/2017:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0PMFT3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. ** 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/1756437 Title: systemd starts suspend service on startup and gets stuck... Status in systemd package in Ubuntu: New Bug description: root@charion:~# systemctl status ● charion State: starting Jobs: 2 queued Failed: 1 units Since: Fri 2018-03-16 20:37:37 CET; 39min ago CGroup: / ├─user.slice │ ├─user-122.slice │ │ ├─user@122.service │ │ │ ├─pulseaudio.service │ │ │ │ └─2981 /usr/bin/pulseaudio --daemonize=no │ │ │ ├─at-spi-dbus-bus.service [...] root@charion:~# systemctl list-jobs JOB UNITTYPE STATE 2076 systemd-suspend.service start running 2075 suspend.target start waiting 2 jobs listed. root@charion:~# On the console is visible: "A start job is running for Suspend" and the time it is already running. This is while I am logged into a gdm3/Gnome session. I've already deleted all snap packages which provided additional shutdown/suspend targets. I had those under suspicion initially. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 21:22:41 2018 InstallationDate: Installed on 2018-02-28 (16 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) MachineType: Dell Inc. Precision M4800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=UUID=d0075e29-dbce-40fe-8c81-b56b505b40b9 ro video=vesa:off vga=normal SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0PMFT3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/14/2017:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0PMFT3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1756437/+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 1712639] Re: nfs-kernel-server doesn't wait on (luks) encrypted fs on startup
The problem still exists. -- 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/1712639 Title: nfs-kernel-server doesn't wait on (luks) encrypted fs on startup Status in systemd package in Ubuntu: New Bug description: nfs-kernel-server fails on startup when the exported FS is on an encrypted partition that requires a password entry. Currently nfs-kernel-server must be restarted in order to export the FS. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nfs-kernel-server 1:1.3.4-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Aug 23 20:31:02 2017 InstallationDate: Installed on 2014-05-30 (1181 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: nfs-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712639/+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 1432265] [NEW] after the upstart replacement with systemd, the system fails to boot with 2 LUKS encrypted devices.
Public bug reported: after the recent upstart - systemd migration my system is left unable to complete it's boot process. It asks for the first passphrase, but not for the second. When booting with upstart (via the advanced boot options), the system behaves correctly and asks for both passphrases. /etc/crypttab sda2_crypt UUID=32a5c8b9--4b06-9224-0dc595e320b7 none luks,discard sdb1_crypt UUID=8b568ed8-842b-462c-9ecd-789d80fb913f none luks,discard /etc/fstab # file system mount point type options dump pass /dev/mapper/sda2_crypt /ext4 discard,noatime,nodiratime,commit=300,errors=remount-ro 0 1 /dev/sda1 /boot ext3 discard,relatime,nodiratime,commit=300,defaults 0 2 /dev/mapper/sdb1_crypt /opt btrfs nofail,autodefrag,discard,enospc_debug 0 1 # tmpfs /tmp tmpfs relatime,nosuid 0 0 #/dev/mapper/swap none swapsw,discard 0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Mar 15 00:10:02 2015 InstallationDate: Installed on 2014-05-30 (288 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Dell Inc. Precision M4800 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=UUID=c72e0d8e-4822-45c8-b95f-6e13971940d3 ro nomodeset allow-discards root_trim=yes nomdmonddf nomdmonisw crashkernel=384M-:128M nogpumanager init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/graphical.target → /lib/systemd/system/graphical.target.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PMFT3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0PMFT3:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1432265 Title: after the upstart replacement with systemd, the system fails to boot with 2 LUKS encrypted devices. Status in systemd package in Ubuntu: New Bug description: after the recent upstart - systemd migration my system is left unable to complete it's boot process. It asks for the first passphrase, but not for the second. When booting with upstart (via the advanced boot options), the system behaves correctly and asks for both passphrases. /etc/crypttab sda2_crypt UUID=32a5c8b9--4b06-9224-0dc595e320b7 none luks,discard sdb1_crypt UUID=8b568ed8-842b-462c-9ecd-789d80fb913f none luks,discard /etc/fstab # file system mount point type options dump pass /dev/mapper/sda2_crypt /ext4 discard,noatime,nodiratime,commit=300,errors=remount-ro 0 1 /dev/sda1 /boot ext3 discard,relatime,nodiratime,commit=300,defaults 0 2 /dev/mapper/sdb1_crypt /opt btrfs nofail,autodefrag,discard,enospc_debug 0 1 # tmpfs/tmp tmpfs relatime,nosuid 0 0 #/dev/mapper/swap none swapsw,discard 0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Mar 15 00:10:02 2015 InstallationDate: Installed on 2014-05-30 (288 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Dell Inc. Precision M4800 ProcKernelCmdLine:
[Touch-packages] [Bug 1403419] [NEW] update-initramfs / mkinitramfs fails to add ANY kernel modules
Public bug reported: The error occured which the update last Saturday or Sunday. (Re-)Building an initrd results in unusable initrds Checking the directory shows that there is not a single module included in the archive. The initrd itself is much smaller as a first visual indication. Booting a kernel with such an initrd strands the machine in the initrd busybox with almost no available devices (due to the missing kernel modules) No kernel modules: neuffer@charion:/tmp/mkinitramfs_kDABiK/lib/modules/3.16.0-28-generic$ ls -la total 208 drwxr-xr-x 2 root root260 Dez 17 10:04 . drwxr-xr-x 3 root root 60 Dez 17 10:04 .. -rw-r--r-- 1 root root 45 Dez 17 10:04 modules.alias -rw-r--r-- 1 root root 12 Dez 17 10:04 modules.alias.bin -rw-r--r-- 1 root root 6299 Dez 12 19:38 modules.builtin -rw-r--r-- 1 root root 8273 Dez 17 10:04 modules.builtin.bin -rw-r--r-- 1 root root 0 Dez 17 10:04 modules.dep -rw-r--r-- 1 root root 12 Dez 17 10:04 modules.dep.bin -rw-r--r-- 1 root root 52 Dez 17 10:04 modules.devname -rw-r--r-- 1 root root 162124 Dez 12 19:38 modules.order -rw-r--r-- 1 root root 55 Dez 17 10:04 modules.softdep -rw-r--r-- 1 root root 49 Dez 17 10:04 modules.symbols -rw-r--r-- 1 root root 12 Dez 17 10:04 modules.symbols.bin neuffer@charion:/tmp/mkinitramfs_kDABiK/lib/modules/3.16.0-28-generic$ euffer@charion:/tmp/mkinitramfs_kDABiK/lib/modules/3.16.0-28-generic$ ls -la /boot total 120356 drwxr-xr-x 4 root root 4096 Dez 17 10:06 . drwxr-xr-x 24 root root 4096 Dez 16 20:07 .. -rw-r--r-- 1 root root 1206876 Sep 28 09:41 abi-3.16.0-17-generic-working -rw-r--r-- 1 root root 1207195 Dez 1 20:59 abi-3.16.0-26-generic -rw-r--r-- 1 root root 1207195 Dez 12 19:38 abi-3.16.0-28-generic -rw-r--r-- 1 root root 31075053 Dez 16 10:21 ba.initrd.img-3.16.0-17-generic-working -rw-r--r-- 1 root root 171664 Sep 28 09:41 config-3.16.0-17-generic-working -rw-r--r-- 1 root root 171760 Dez 1 20:59 config-3.16.0-26-generic -rw-r--r-- 1 root root 171760 Dez 12 19:38 config-3.16.0-28-generic drwxr-xr-x 5 root root 4096 Dez 16 20:08 grub -rw-r--r-- 1 root root 31075053 Sep 28 09:41 initrd.img-3.16.0-17-generic-working -rw-r--r-- 1 root root 15158157 Dez 16 20:08 initrd.img-3.16.0-26-generic -rw-r--r-- 1 root root 11293654 Dez 17 09:33 initrd.img-3.16.0-28-generic drwx-- 2 root root16384 Mai 30 2014 lost+found -rw-r--r-- 1 root root 176500 Mär 12 2014 memtest86+.bin -rw-r--r-- 1 root root 178176 Mär 12 2014 memtest86+.elf -rw-r--r-- 1 root root 178680 Mär 12 2014 memtest86+_multiboot.bin -rw--- 1 root root 3498250 Sep 28 09:41 System.map-3.16.0-17-generic-working -rw--- 1 root root 3500830 Dez 1 20:59 System.map-3.16.0-26-generic -rw--- 1 root root 3500841 Dez 12 19:38 System.map-3.16.0-28-generic -rw--- 1 root root 6399936 Sep 28 09:41 vmlinuz-3.16.0-17-generic-working -rw--- 1 root root 6407488 Dez 1 20:59 vmlinuz-3.16.0-26-generic -rw--- 1 root root 6406800 Dez 12 19:38 vmlinuz-3.16.0-28-generic neuffer@charion:/tmp/mkinitramfs_kDABiK/lib/modules/3.16.0-28-generic$ And yes, I've added a set -xv to mkinitramfs ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: initramfs-tools 0.103ubuntu8 [modified: usr/sbin/mkinitramfs] ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 NonfreeKernelModules: btrfs xor raid6_pq hid_generic usbhid hid dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse e1000e ahci libahci ptp sdhci_pci pps_core sdhci_acpi video sdhci ApportVersion: 2.15-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Dec 17 10:20:06 2014 InstallationDate: Installed on 2014-05-30 (201 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Description changed: - The error occured which the update last Saturday or Sunday. (Re-)Building an initrd results in unusable initrds Checking the directory shows that there is not a single module included in the archive. The initrd itself is much smaller as a first visual indication. - Booting a kernel with such an initrd strands the machine in the initrd busybox + Booting a kernel with such an initrd strands the machine in the initrd busybox with almost no available devices (due to the missing kernel modules) No kernel modules: neuffer@charion:/tmp/mkinitramfs_kDABiK/lib/modules/3.16.0-28-generic$ ls -la total 208 drwxr-xr-x 2 root root260 Dez 17 10:04 . drwxr-xr-x 3 root root 60 Dez 17 10:04 .. -rw-r--r-- 1 root root 45 Dez 17 10:04 modules.alias -rw-r--r-- 1 root root 12 Dez 17
Re: [Touch-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
On 01.12.2014 11:57, Christopher M. Penalver wrote: Michael Neuffer, could you please boot into the kernel that comes with Ubuntu by default (i.e. not 3.11.x) What do you mean with that comes with Ubuntu by default ? I currently use 3.16.0-26-generic and execute the following in a terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1268151 Please ensure you have xdiagnose installed, That is currently not possible: --- root@charion:~# apt-get install xdiagnose 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: xdiagnose : Depends: python3-pygtk but it is not installable Recommends: intel-gpu-tools but it is not going to be installed E: Unable to correct problems, you have held broken packages. Once the dependcy can be fullfilled I can install it. -- 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/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in xorg package in Ubuntu: Incomplete Bug description: With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the display shuts off, it will not wake up anymore, and the screen stays dark. A cycle of the following will leave the display dark: xset dpms force off; sleep 30; xset dpms force on WORKAROUND: A restart of the Xserver will bring back the display. WORKAROUND: Don't allow DPMS to switch off the display: xset dpms 0 0 0 xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/+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 1332947] Re: HDPI: unity randomly turns on large text in universal access
I get this behaviour with my Dell M4800 (3200x1800) with utopic and current vivid However I mostly get the effect when I connect one or two additional displays and configure them with arandr. I never had it directly after a reboot. Restarting the XServer always fixes the problem for me. - Until it is triggered again. -- 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/1332947 Title: HDPI: unity randomly turns on large text in universal access Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: In Progress Bug description: I have a macbook pro with retina display. In Ubuntu 14.04 64bit, every couple of reboots, the 'large text' option in Universal Access gets switched on upon login. It happens in roughly 1 out of 5 reboots for 1 or more users on the computer. It appears to happen to people with small HighDPI screens. In my case, it's 13 inch at 2560x1600. Another example is 13 inch at 1080p - http://askubuntu.com/questions/453785/large-text-button-in-universal-access-turns-itself-on-after-reboot-ubuntu-14-0 unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages unity-control-center: Installed: 14.04.3+14.04.20140410-0ubuntu1 Candidate: 14.04.3+14.04.20140410-0ubuntu1 Version table: *** 14.04.3+14.04.20140410-0ubuntu1 0 500 http://sk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status intel iris pro graphics (lspci -vvv): 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device 011a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 66 Region 0: Memory at b000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at a000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 1000 [size=64] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1332947/+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 1394639] [NEW] lightdm fails to start with 3 connected displays but works 2 displays
Public bug reported: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off --output DP-0 --off When lightdm is started with all three displays connected, it will terminate and force the Xserver to go down as well, triggering a cycle of Xserver/lightdm restarts. Disconnecting the 3rd display will bring up lightdm immediately without a glitch. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 20 14:09:40 2014 InstallationDate: Installed on 2014-05-30 (174 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) LightdmGreeterLog: (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lightdm-gtk-greeter:7540): WARNING **: Failed to load user image: Failed to open file '/home/neuffer/.face': No such file or directory SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1394639 Title: lightdm fails to start with 3 connected displays but works 2 displays Status in “lightdm” package in Ubuntu: New Bug description: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off --output DP-0 --off When lightdm is started with all three displays connected, it will terminate and force the Xserver to go down as well, triggering a cycle of Xserver/lightdm restarts. Disconnecting the 3rd display will bring up lightdm immediately without a glitch. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 20 14:09:40 2014 InstallationDate: Installed on 2014-05-30 (174 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) LightdmGreeterLog: (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lightdm-gtk-greeter:7540): WARNING **: Failed to load user image: Failed to open file '/home/neuffer/.face': No such file or directory 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/1394639/+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 1394639] Re: lightdm fails to start with 3 connected displays but works 2 displays
** Attachment added: X Server log with 3 displays connected https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1394639/+attachment/4264462/+files/Xorg.0.log.borked -- 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/1394639 Title: lightdm fails to start with 3 connected displays but works 2 displays Status in “lightdm” package in Ubuntu: New Bug description: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off --output DP-0 --off When lightdm is started with all three displays connected, it will terminate and force the Xserver to go down as well, triggering a cycle of Xserver/lightdm restarts. Disconnecting the 3rd display will bring up lightdm immediately without a glitch. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 20 14:09:40 2014 InstallationDate: Installed on 2014-05-30 (174 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) LightdmGreeterLog: (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lightdm-gtk-greeter:7540): WARNING **: Failed to load user image: Failed to open file '/home/neuffer/.face': No such file or directory 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/1394639/+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 1394639] Re: lightdm fails to start with 3 connected displays but works 2 displays
lightdm log with 3 displays attached [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.13.0, UID=0 PID=4640 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-xubuntu.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Registered seat module xlocal [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Monitoring logind for seats [+0.00s] DEBUG: New seat added from logind: seat0 [+0.00s] DEBUG: Loading properties from config section SeatDefaults [+0.00s] DEBUG: Seat seat0: Starting [+0.00s] DEBUG: Seat seat0: Creating greeter session [+0.00s] DEBUG: Seat seat0: Creating display server of type x [+0.00s] DEBUG: Using VT 7 [+0.00s] DEBUG: Seat seat0: Starting local X display on VT 7 [+0.00s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log [+0.00s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0 [+0.00s] DEBUG: DisplayServer x-0: Launching X Server [+0.00s] DEBUG: Launching process 4650: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+0.00s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0 [+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.00s] DEBUG: Loading users from org.freedesktop.Accounts [+0.00s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+2.09s] DEBUG: Got signal 10 from process 4650 [+2.09s] DEBUG: DisplayServer x-0: Got signal from X server :0 [+2.09s] DEBUG: DisplayServer x-0: Connecting to XServer :0 [+2.09s] DEBUG: Seat seat0: Display server ready, starting session authentication [+2.09s] DEBUG: Session pid=4694: Started with service 'lightdm-greeter', username 'lightdm' [+2.10s] DEBUG: Session pid=4694: Authentication complete with return value 0: Success [+2.10s] DEBUG: Seat seat0: Session authenticated, running command [+2.10s] DEBUG: Session pid=4694: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/lightdm-gtk-greeter [+2.10s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+2.10s] DEBUG: Session pid=4694: Logging to /var/log/lightdm/x-0-greeter.log [+2.11s] DEBUG: Activating VT 7 [+2.11s] DEBUG: Activating login1 session c3 [+2.14s] DEBUG: Session pid=4694: Greeter connected version=1.13.0 resettable=false [+2.40s] DEBUG: Session pid=4694: Greeter closed communication channel [+2.40s] DEBUG: Session pid=4694: Exited with return value 0 [+2.40s] DEBUG: Seat seat0: Session stopped [+2.40s] DEBUG: Seat seat0: Stopping; failed to start a greeter [+2.40s] DEBUG: Seat seat0: Stopping [+2.40s] DEBUG: Seat seat0: Stopping display server [+2.40s] DEBUG: Sending signal 15 to process 4650 [+3.61s] DEBUG: Process 4650 exited with return value 0 [+3.61s] DEBUG: DisplayServer x-0: X server stopped [+3.61s] DEBUG: Releasing VT 7 [+3.61s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0 [+3.61s] DEBUG: Seat seat0: Display server stopped [+3.61s] DEBUG: Seat seat0: Stopped [+3.61s] DEBUG: Required seat has stopped [+3.61s] DEBUG: Stopping display manager [+3.61s] DEBUG: Display manager stopped [+3.61s] DEBUG: Stopping daemon [+3.61s] DEBUG: Exiting with return value 1 -- 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/1394639 Title: lightdm fails to start with 3 connected displays but works 2 displays Status in “lightdm” package in Ubuntu: New Bug description: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off
Re: [Touch-packages] [Bug 1394639] Re: lightdm fails to start with 3 connected displays but works 2 displays
On 20.11.2014 20:55, Andrew P. wrote: Since you are using gtk-greeter - can you test version from this PPA? https://code.launchpad.net/~kalgasnik/+archive/ubuntu/lightdm-gtk-greeter-background-transition Yes, the new version works fine! No more fiddling with monitor cables. Please do not wait to long before uploading it. :-) Thanks! Cheers Mike -- 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/1394639 Title: lightdm fails to start with 3 connected displays but works 2 displays Status in “lightdm” package in Ubuntu: New Bug description: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off --output DP-0 --off When lightdm is started with all three displays connected, it will terminate and force the Xserver to go down as well, triggering a cycle of Xserver/lightdm restarts. Disconnecting the 3rd display will bring up lightdm immediately without a glitch. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 20 14:09:40 2014 InstallationDate: Installed on 2014-05-30 (174 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) LightdmGreeterLog: (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lightdm-gtk-greeter:7540): WARNING **: Failed to load user image: Failed to open file '/home/neuffer/.face': No such file or directory 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/1394639/+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 1387642] [NEW] lightdm fails to open Pipe - too many open files (with link to patch)
Public bug reported: Please check https://bugs.launchpad.net/lightdm/+bug/1190344 for details and hopefully the fix. The bug report mentioned above is against Fedora and the fix might not have made it into Debian/Ubuntu as it seems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 30 13:47:37 2014 InstallationDate: Installed on 2014-05-30 (153 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1387642 Title: lightdm fails to open Pipe - too many open files (with link to patch) Status in “lightdm” package in Ubuntu: New Bug description: Please check https://bugs.launchpad.net/lightdm/+bug/1190344 for details and hopefully the fix. The bug report mentioned above is against Fedora and the fix might not have made it into Debian/Ubuntu as it seems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 30 13:47:37 2014 InstallationDate: Installed on 2014-05-30 (153 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) 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/1387642/+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
