On 10/18/2017 3:54 AM, Bernhard Schmidt wrote:
> Accessing /home leads to a blocked process. The reason is that (for
> numerous years, due to reasons I don't remember) I had
> x-systemd.automount in my fstab for /home
That makes sense. Now I wonder why is fsck trying to open /home? You
run it on
On 10/17/2017 2:42 AM, Bernhard Schmidt wrote:
> close(3)= 0
> open("/home", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXECstrace: Process 1677
> detached
>
So it hangs in a call to open() on /home? That looks like a kernel bug.
Is /home mounted at the time, or is i
On 11/3/2016 11:37 AM, Sandro Tosi wrote:
> Phillip, did you have a chance to look at making parted not crashing
> if there is only one unallocated sector between partitions? Mattia, do
> you still consider this bug RC? thanks!
I have not had time to work on it yet.
Do you have udisks2 installed? The only connection I can think of from
gparted to policykit is through udisks, as the gparted script tries to
run udisks-inhibit to stop auto mounting. I'm guessing that is where
this bug needs reassigned.
On 12/7/2015 7:33 AM, shirish शिरीष wrote:
> Package: gpar
4 matches
Mail list logo
