[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-04-14 Thread Dan Streetman
This actually appears to be bug(s) in the 'finalrd', not systemd; probably bug 1920107 is a dup of this one ** Package changed: systemd (Ubuntu) => finalrd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in U

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-04-14 Thread Dan Streetman
** Changed in: systemd (Ubuntu) Status: Incomplete => 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/1905166 Title: systemd-shutdown cannot detach DM Status in

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-04-06 Thread Dan Streetman
> [ timestamp] sd-umoun[2337]: Failed to unmount /oldroot: Device or resource > busy > [ timestamp] sd-umoun[2337]: Failed to unmount /oldroot/sys: Device or > resource busy um, your mount output doesn't show any mounts at those dirs...you sure you're getting those messages at shutdown? ;-) --

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-03-27 Thread Jo Liss
> for those affected, does this happen every boot/shutdown? Yes, I'm getting the following messages on Hirsute at the end of every shut down (or reboot): [ OK ] Reached target Reboot. [ timestamp] XFS: attr2 mount option is deprecated. [ timestamp] sd-umoun[2337]: Failed to unmount /oldroo

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-02-18 Thread Dan Streetman
for those affected, does this happen every boot/shutdown? is this a 'standard' installation, using the standard iso? what do you have mounted? what's the output of 'mount' and the output of 'lsblk'? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages,

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-02-03 Thread j
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5459534/+files/kern.log -- 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.n

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-02-03 Thread j
** Attachment added: "short.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5459536/+files/short.log -- 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

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-02-03 Thread j
** Attachment added: "long.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5459535/+files/long.log -- 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.n

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-02-03 Thread j
** Attachment added: "2.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5459533/+files/2.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/bug

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-02-03 Thread j
The message: systemd-shutdown[1]: Could not detach DM /dev/dm-0: Device or resource busy systemd-shutdown[1]: Failed to finalize DM devices, ignoring is not in the logs, idk why, here are some more logs, the image shows the message and the time before. I attached also a longer log file and kern lo

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-01-13 Thread smartman
Same issue here. 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux I had issue with glxgears and some other apps that failed to start. When restarting then the computer(Lenovo P73) hanged. I think the same hanging behaviour has happened before. No

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-01-12 Thread Dan Streetman
> Have the same problem, here is the log: that log doesn't show the reported problematic log messages -- 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/1905166 Title: system

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2021-01-07 Thread j
Have the same problem, here is the log: ** Attachment added: "Log of systemd" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1905166/+attachment/5450309/+files/lp1905166.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subsc

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2020-12-11 Thread Dan Streetman
please reboot with this kernel boot parameter added: systemd.log_level=debug Then let the system boot up, and then perform a shutdown, to reproduce the problem. Then start the system back up (you can remove the kernel boot parameter) and capture the previous boot's journal, which should include t

[Touch-packages] [Bug 1905166] Re: systemd-shutdown cannot detach DM

2020-11-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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.n