Comment # 50 on bug 1063638 from David Manca

(In reply to Oliver Kurz from comment #49)

> Sorry, I don't understand your language here. So you are arguing that this
> issue is critical and not *just* major? As a reporter I set the severity to
> "Major" according to
> https://bugzilla.opensuse.org/page.cgi?id=importance_matrix.html and while I
> agree that this bug here is about the most important one to handle in the
> context of "openSUSE as a daily operating system" I would not regard it as
> critical because so far I have not seen data loss linked to it.

You what? There have been people here *complaining* that they had their systems
fucked and data lost. 

"Critical: Crash, data loss or corruption, severe memory leak, etc. " 

Crash definitely happens, it's severe enough! It is a critical bug that affects
everyone, just read the comments!


> Please stay calm and objective here :) The priority field is used by teams
> working on bugs to prioritize their internal backlog so please refrain from
> changing it without consideration of the according development team. Feel
> free to bring more people onto this bug and let them express their opinion
> by "voting". IMHO this is a good way to show how many people are affected
> and care about the issue without needing to add more comments which do not
> add objective information which help to actually fix the issues

People don't even know that this bugtracker exists, yet they experience it a
lot. I had to find the bugtracker on reddit, because I did not know how to find
it. People not seeing this thread =/= it doesn't affect them.


> I work as a QA engineer at SUSE and try to help with resolving this bug.
> Currently I have the challenge to find a clear reproducer. So it would help
> very much if we find one scenario which we can automate the failure
> reproduction. Providing this to the development teams could help to fix the
> issue faster. With the help of openQA we can already automate a lot which
> are very realistic scenarios but I would appreciate some help now :)

Install opensuse on a laptop, run YAST once or twice, use it and then see the
99% CPU drain and eventual crash of the system at least once a day.

> Rest assured that the issue *is being worked on* already but without a way
> to reproduce the issue as is observed on the side of the users it will
> likely take very long to fix the issue *as you see them*.

Thank god for that

It's a major bug that basically stopped me from deploying openSUSE machines.
Hopefully there will be progress, since it's like 1/2 of year from the report
of the bug and 0 progress