Comment # 49 on bug 1063638 from Oliver Kurz

(In reply to David Manca from comment #43)
> Who even thinks if not marking this as critical to fix. Have we
> dropped standards now?

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.

> It's a bug and it **has to get fixed IMMIDIATELY** it's a production-killing thing that will end your system. This *HAS TO GET FIXED*

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

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 :)

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*.

(In reply to Andre Guenther from comment #48)
> Actually there are at least two bugs here: 
> 1. The system gets unresponsive and you can't even cleanly shutdown it.
> 2. Hard reset / power loss will very likely kill your data (even if problem
> 1 didn't arise yet, but especially then).
> 
> As already has been mentioned - the second one is even worse.
> 
> Shouldn't it be considered to split them in two, making the second one
> critical?

Yes but only when we identified that the issues are actually different or at
least the way how to reproduce are different. I would really appreciate if you
could provide steps to reproduce this issue more easily.