[Touch-packages] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
I'm running mesa 22.2.5-0ubuntu0.1~22.04.3 since it was released without any issues any more. Previously, I had between one and a dozend kwin crashes a day, so for me it's definitely fixed in this version. @autra: Do you really see the "kwin_x11: The X11 connection broke: I/O error (code 1)" kwin quits (technically, it's not even a crash as I understand), or maybe something differently which causes kwin to suddenly disappear? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
On my machine the crashes also seem to be solved. I was using Intel driver until the weekend (since I use this laptop) and then switched to the nVidia binary drivers because I wanted to use CUDA for some experiments. kwin seems to run properly with both so far. @Konstantin Petrov: You write about a "hang", even referring to "GPU hangs" in the logs, which sometimes happen with Intel cards but on my system then actually cause a "hang" / "freeze", not a crash with kwin disappearing. This issue here is about kwin suddenly just quitting / disappearing, not about kwin freezing. Are we talking about the same symptoms? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Released Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
I can confirm the fix for jammy - I'm now running the fixed version since it hit jammy-proposed on Friday. I wanted to wait a few days to be sure, but so far it looks very promising - no kwin crash / termination since then! :) ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) Status in KDE Base Workspace: Fix Released Status in Mesa: Fix Released Status in kwin package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in kwin source package in Jammy: Invalid Status in mesa source package in Jammy: Fix Committed Status in kwin package in Debian: New Bug description: [Impact] kwin might crash after running some time Two commits have been reverted upstream since 22.2.x branch was closed, needs those backported to fix this. [Test case] Run kwin for a day or so, which is usually enough time to hit this. Crash happens mostly on a notification popups, so system must be actively receiving notifications to test the crash. Without that crash may not happen even in a week of runtime. [Where things could go wrong] This just reverts two commits, and they have been upstream for a few months now, so these causing a regression is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2017898] [NEW] MESA 22.2 Regression Causes Kwin Crashes (Fix Available)
Public bug reported: MESA 22.2 contains a malfunction which causes kwin to exit regularly / frequently, leaving the system without window management. This is a regression compared to MESA 22.1 and fixed again in MESA 22.3. See following MESA bug: * https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674 * just for reference, corresponding KDE Bugtracker entry: https://bugs.kde.org/show_bug.cgi?id=461316 Maybe the fix could be backported? It currently is something between inconvenient (for very technically savy users) and rendering the system unusable (for less technically savy users - suddenly, Window Management will be gone and switching windows, accessing panels, and controlling most applications even if they are in foreground at the time of a crash become impossible). ProblemType: Bug DistroRelease: KDE neon 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Thu Apr 27 14:26:47 2023 DistUpgraded: 2020-10-11 12:05:38,766 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.19.0-40-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-40-generic root=/dev/mapper/ubuntu--vg--970-root ro resume=/dev/ubuntu-vg-970/swap fsck.mode=force rd.driver.blacklist=nouveau pcie_aspm=off RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2020-10-11 (928 days ago) dmi.bios.date: 11/10/2022 dmi.bios.release: 1.31 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.31.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.31.0:bd11/10/2022:br1.31:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115-0xneon+22.04+jammy+release+build8 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017898 Title: MESA 22.2 Regression Causes Kwin Crashes (Fix Available) Status in mesa package in Ubuntu: New Bug description: MESA 22.2 contains a malfunction which causes kwin to exit regularly / frequently, leaving the system without window management. This is a regression compared to MESA 22.1 and fixed again in MESA 22.3. See following MESA bug: * https://gitlab.freedesktop.org/mesa/mesa/-/issues/7674 * just for reference, corresponding KDE Bugtracker entry: https://bugs.kde.org/show_bug.cgi?id=461316 Maybe the fix could be backported? It currently is something between inconvenient (for very technically savy users) and rendering the system unusable (for less technically savy users - suddenly, Window Management will be gone and switching windows, accessing panels, and controlling most applications even if they are in foreground at the time of a crash become impossible). ProblemType: Bug DistroRelease: KDE neon 22.04 Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Thu Apr 27 14:26:47 2023 DistUpgraded: 2020-10-11
[Touch-packages] [Bug 1699772] [NEW] linux-image-4.4.0-81-generic Regression: Oracle Java plugin crashes
Public bug reported: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from > /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, > unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from > /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from > /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package > and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Package changed: mesa (Ubuntu) => linux (Ubuntu) ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2017-1000364 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.4.0-81-generic Regression: Oracle Java plugin crashes Status in linux package in Ubuntu: Confirmed Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from
[Touch-packages] [Bug 1453912] Re: systemd does not unlock dm-crypt password
I just noticed that I can enter the password and unlock the disk if I boot with splash / plymouth enabled. I normally do not use the "splash" boot option to boot up in text mode, and the cryptsetup unit file or something does not seem to be able to cope with that and does not query for the password. Adding "splash" to the boot options made a password prompt appear during systemd boot, but of course also enabled a graphical boot up process... -- 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/1453912 Title: systemd does not unlock dm-crypt password Status in systemd package in Ubuntu: New Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached "screenshot" (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service -> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not unlock dm-crypt password
Unfortunately, this bug is still current - I submitted all requested information, there has been no activity in response, but the problem still persists. ** Changed in: systemd (Ubuntu) Status: Expired => New -- 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/1453912 Title: systemd does not unlock dm-crypt password Status in systemd package in Ubuntu: New Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached "screenshot" (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service -> /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not unlock dm-crypt password
BTW, is there anything else needed from my side or anything else I should or can do to provide any required information? I'm still having this issue and I fear my system might be rendered unusable if the next Kubuntu update possibly removes upstart support completely and with it the fallback boot option that's currently saving me... -- 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/1453912 Title: systemd does not unlock dm-crypt password Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not unlock dm-crypt password
HTH ** Attachment added: The requested generator.tar file. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4422419/+files/generator.tar.bz2 -- 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/1453912 Title: systemd does not unlock dm-crypt password Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not allow to boot with /home on dm-crypt
I fetched the debug log using the debug console, however it's contents do not look suspicious to me... systemd seems to try to start the cryptsetup service, the only question probably is where the password prompt does end up... ** Attachment added: systemd jounal fetched using debug console. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4416839/+files/journal.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/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not allow to boot with /home on dm-crypt
When I boot using systemd, nothing is logged at all - maybe booting stalls even before rsyslogd is started? If I boot using upstart, the syslog is as follows - note the massive delay before activation of org.freedesktop.UDisks2 which causes the boot process to take quite long - Kubuntu 14.10 had a *much* faster boot process without such a delay. ** Attachment added: syslog while booting using upstart - there are no log entries if I try to boot using systemd https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4412154/+files/upstart_syslog.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/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] Re: systemd does not allow to boot with /home on dm-crypt
none is the key file: crypttab(5): The third field, key file, describes the file to use as a key for decrypting the data of the source device. Note that the entire key file will be used as the passphrase; the passphrase must not be followed by a newline character. However I'll try booting with the different init systems and attach the syslog results soon, hopefully this evening. -- 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/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+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 1453912] [NEW] systemd does not allow to boot with /home on dm-crypt
Public bug reported: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: 20150511_001.jpg https://bugs.launchpad.net/bugs/1453912/+attachment/4395710/+files/20150511_001.jpg -- 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/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: New Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during
