Comment # 96 on bug 1063638 from Oliver Kurz

(In reply to Harald Achitz from comment #95)
> this bug has a history back to 2016 and has been declared resolved
> I requested if there have been meaningful tests been done, you can look up
> the answer.
> https://bugzilla.opensuse.org/show_bug.cgi?id=1017461#c110
> 
> It seems either the responsible person do not understand the problem, or
> they want to hide something. I guess both is the case.
> But obviously they either don't care, or do not know how to reproduce this
> behavior do do meaningful development for this problem. I guess both is the
> case.

I struggle to understand how you can come to this conclusion. You should keep
in mind that I am also the reporter of the current bug and I did not give up on
this story. Certainly you might want to state that I do not understand the
problem but at least enough of it to keep the discussion running. Accussing me
of wanting to hide something is not very nice :(

I agree with you that this bug does not receive enough attention as *I* would
like it to see but also I trust the developers that can actually fix it are
aware of the issue as well as all others in their backlog and they decide based
on priorities and feasibility on what to work on first and what next. I see
your above statement as expressing your frustration but this will unfortunately
most likely not have any helpful impact.

It has been expressed that the issue is known and is ��� despite what the user
reports indicate ��� not easy to reproduce in a consistent manner that can be
used to help fix the issue (or issues) more easily. I am of course also running
openSUSE with the default btrfs + qgroups + snapshots enabled on my notebook
which I use for daily work and (unfortunately) I do not see the issue at all in
my environment!

If you want to help then try to provide either better tests or proposals for
fixes. I have not seen any contributions of that kind rejected.

@jeffm, dsterba: I guess you could help here. I would really appreciate if you
can give your current view on this and let the bug status reflect this, e.g.
"CONFIRMED" or "IN_PROGRESS"