FS#50258 - [systemd] freezes during unmount whilst shuting down
Attached to Project:
Arch Linux
Opened by Mattias Andrée (maandree) - Thursday, 04 August 2016, 12:47 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 29 October 2016, 15:15 GMT
Opened by Mattias Andrée (maandree) - Thursday, 04 August 2016, 12:47 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 29 October 2016, 15:15 GMT
|
Details
systemd “eats the filesystem”. This has been an issue since
Arch Linux started using systemd and is still a problem in
systemd 230-7.
During shutdown or reboot, it freezes when dettaching LUKS-encrypted swap, and no filesystem is ever unmounted, and the must be shutdown or rebooted by pressing the physical shutdown or reboot buttons. |
This task depends upon
but I seldom restart my computer, so it can take quite some time.
Regardless, upstream will be interested in your findings when you get around to it. This isn't a packaging problem.
Stop this bullshit (we often see) about bug reports being egoistic or plain harassment. When you file a bug report, you are helping out, and more would probably be filed is this attitude did not exist, and that would be good.
As for your second paragraph. Upsteam usually tell me to report it do the distro when I think it is an upstream issue. In this case, I don't know, I have not investigated it. So I'm just doing what they would tell me to do anyway.
All falconindy said was that he is not sure what this bug report is supposed to accomplish then. He basically cannot do anything at all and there is no way to even start to work on this issue. Your reaction is extremely hostile and, frankly speaking, ridiculous. Falconindy did nothing even approaching what you accuse him of.
Frankly I think that closing a bug report because I haven't had time to debug a problem is being a bit hostile and akin to closing a bug report because I didn't provide a patch for the problem, which is ridiculous. It shouldn't be expected of me more than describing the symptoms. If I am however asked to try potential solutions, or descibed whys to acquire more that than could help you, I argubly should, but I am not responsible for doing so immediately. I do it when it fits me, not when it fits you. You have other problems too, so you are not in a hurry with any specific one (unless it is a critical bug, which I did not report this as).