Comment 161 for bug 441835

Revision history for this message
Björn Kautler (vampire0) wrote :

John, if you refer to "After upstream discussion this should be fixed in dk-disks after all.", then this was just a misunderstanding. What Martin meant to say was "After upstream discussion this should get fixed in dk-disks after all.", just defining the component in which this will get fixed somewhen in the future. It shouldn't mean that the bug is fixed already. Of course it will need a software update, so as I siad, please be patient until one arrives. Noone said it will be fixed without a software update, I just told you a workaround for the meantime.

> Guys jumping in and going all negative on people does not help.

Correct, that is why I didn't do it. I jumped in and gave Martin access to my box to find the cause of the problem what he did. THAT helped. Your dozens of comments without any additional info that mostly contain whining on the other hand do NOT help in any way. It just annoys anyone who is subscribed to this bug as for every comment you write, a mail is sent out. And writing comments in 2 minutes steps without any helpful information, even after it was clearly stated that the cause of the problem is clear now IS spam. I didn't attack ALL people, I just asked you to not spam this bug with unhelpful comments. Instead I actually attacked the problem in actively helping to find the root cause by giving Martin access to my box what YOU didn't want to provide. That is ok, but please don't complain that I attack people instead of the problem.

For me, this discussion with you is over now. I will not reply to any comment regarding this anymore, so please don't write any, it doesn't help and is totally unrelated to this bug.