F12: 30 second freeze when accessing certain panel items ?

Linuxguy123 linuxguy123 at gmail.com
Thu Dec 17 01:56:12 UTC 2009


On Thu, 2009-12-17 at 02:02 +0100, Kevin Kofler wrote:
> Log files are essential to debug driver issues, it's normal that bugs
> only 
> get looked at if you provide them.

I assume you are implying that I haven't provided information on some of
the bugs that I have reported.

Well... lets look at this one.
https://bugzilla.redhat.com/show_bug.cgi?id=528188

Its a nouveau bug.  Nothing to do with a proprietary nVidia driver. NO
excuses there.

I first reported it pre rawhide, on October 9th.   I provided xorg files
bootlog and dmesg.  

I tested again on October 22nd.  This time it was in rawhide.  Again I
provided xorg, bootlog and dmesg files. 

Yet the developers did NOTHING about this report, except once again ask
for it to be retested.

On December 14th I again tested it and provided xorg and dmesg files.

The only way I was able to install F12 at all was to peer through a
snowy screen and figure out what the buttons probably meant. 

Result: priority LOW, no action. 

Luckily the PROPRIETARY driver works.

> As for that GUI, that's what the Display section of System Settings is
> for. 

And does it work ? Nope.

For some reason KDE and Fedora developers figure they have license to
ship incomplete and not working software.  Its their right.  Screw the
users. 




More information about the kde mailing list