Fedora 19 released

Posted Jul 3, 2013 10:43 UTC (Wed) by hadrons123 (guest, #72126)
In reply to: Fedora 19 released by AdamW
Parent article: Fedora 19 released

>Not to throw Dan under any buses, I love the guy, but please note he and upstream have been trying to fix this issue for something like three months now.
I know. I like Dan too. I have reported my observations on that bug too.
>It is clearly not an easy fix.
I understand.
>What do you want us to do? Delay the entire Fedora 19 release indefinitely (since we clearly have no reliable timeframe for a fix) due to a superficial bug in a single fairly new desktop spin?
I don't expect to delay the entire F19 release. But when you have released the OS already, how about an updated image of MATE-LiveCD alone when the bug is fixed, since the bug is reasonably troublesome when it involves the file manager and bringing the system down for the sake of the users?

An updated image which is not tested as much as the release is better than the "broken caja which brings the system down". Can't the QA guys make this as an exception for the users since its too big to be neglected?

Fedora 19 released

Posted Jul 3, 2013 15:38 UTC (Wed) by AdamW (subscriber, #48457) [Link] (2 responses)

Um. The bunch of windows doesn't 'bring the system down': you can just close them all and the system will work fine. If you're seeing the system not working, it seems likely you're actually seeing *two* bugs. All other reporters so far indicate that the bunch-o-windows problem is entirely superficial.

Fedora 19 released

Posted Jul 3, 2013 16:44 UTC (Wed) by hadrons123 (guest, #72126) [Link] (1 responses)

I am not seeing 2 bugs. The bunch of caja windows actually fills the screen with mate-panel using 99% of the CPU and I have to kill the X server in Terminal. Its not really bunch where you can just close all the open windows. Its about hundreds of caja-windows. AdamW, Thanks for the reply though!

Fedora 19 released

Posted Jul 3, 2013 18:44 UTC (Wed) by AdamW (subscriber, #48457) [Link]

Huh, that's definitely worse than the cases we saw in testing. I've hit the bug myself, several times, and for me it's just ten windows or so and it's fairly easy to just close 'em all and start working. The issue does seem to be a timing bug, so maybe it's not only a case of 'happens or not', but there's a spectrum of how badly it happens, and your system is affected worse than most :( Sorry about that.

We don't really do official respins, but once there's a confirmed fix for the bug, Dan and I may throw up a strictly unofficial respin somewhere.