Possible bug in kwin or ??

gene heskett gheskett at wdtv.com
Mon Apr 25 16:47:28 BST 2011

On Monday, April 25, 2011 11:20:08 AM Ingo Malchow did opine:

> 2011/4/25 gene heskett <gheskett at wdtv.com>:
> > On Monday, April 25, 2011 06:33:28 AM Duncan did opine:
> >> gene heskett posted on Sun, 24 Apr 2011 08:10:46 -0400 as excerpted:
> >> > Please see this bug report:
> >> > �<https://bugs.freedesktop.org/show_bug.cgi?id=35452>
> >> > 
> >> > It turns out that the radeon driver is not the only victim, the
> >> > nvidia driver suffers also, and there may be others.
> >> > 
> >> > Symptoms with the nvidia blob are that black areas of the screen
> >> > are contaminated from playing a news story.
> >> > 
> >> > Black areas [...] such as the html status bar of kmail, or the
> >> > black patterns of the card faces in kpatience are also rendered
> >> > rather yucky.
> >> > 
> >> > We can fix it with:
> >> > 
> >> > Section Device
> >> > 
> >> > � � Option "NoFlip" �"True"
> >> > 
> >> > in the xorg.conf file.
> >> > 
> >> > There is a patch linked to in this bug-report, which also fixes it,
> >> > but its an unruly hack according to the X folks.
> >> > 
> >> > Can this be investigated please? �It seems to have become a problem
> >> > of a far greater frequency of occurrence somewhere around 4.6.2,
> >> > and has forced me to reboot to clean it up several times over the
> >> > recent week.
> >> 
> >> FWIW, the kwin devs aren't likely to see it here, and many devs
> >> prefer a filed bug even if they do read a list, as it's designed for
> >> tracking such things thru final release of the fixed code, while a
> >> list isn't.
> >> 
> >> Meanwhile, does turning off kwin compositing/effects get rid of the
> >> problem? �If not, it's very unlikely to be kwin related at all. �If
> >> that does workaround the problem, it's still unlikely to be a kwin
> >> bug, but may be kwin related in that kwin is sometimes the first
> >> widely used Linux software to make use of some OpenGL functionality.
> >> �Tho even then, kwin won't use the functionality unless the driver
> >> CLAIMS to support it.
> >> 
> >> I could write more on that topic but won't, here, as it's unclear
> >> whether suspending kwin's OpenGL functions (suspend
> >> compositing/effects) eliminates the effects of the bug, or not. �And
> >> if it doesn't, as sounds likely, there's little point in discussing
> >> it further as it's quite unlikely to be a kwin bug, at least one
> >> related to OpenGL.
> >> 
> >> Never-the-less, you could try a different window-manager, compiz for
> >> 3D perhaps, or a 2D-only manager, and see if the problem persists.
> >> �If it does, it's quite clearly not a kwin issue. �(After
> >> installation, the window manager docs and/or commandline help output
> >> should say how to run it to replace an existing window manager.
> >> �With kwin, for instance, kwin --help, run in konsole to see the
> >> output, says kwin --replace can be used to replace the existing
> >> window manager.)
> > 
> > This reply will detail why your bug tracker leaves a very bad taste in
> > my mouth. �If it offends someone to the extent that the bug handling
> > gets fixed, that's nice, but this is NOT the first time I have ranted
> > about kde's broken bug system. �So with that in mind, RANT MODE ON:
> > 
> > While that seems a reasonable request, AIR the passwd db for access to
> > this bug manager seems to be cleaned at 90 day or so intervals. �I
> > have signed up, but my passwd written on the wall doesn't work the
> > next time, and �when I try to rejoin, it refuses to process the
> > request claiming I am already a member. �However, requesting a passwd
> > reminder never results in the reception of such a message by me,
> > effectively locking me out of the process, so the bug never gets
> > filed. I have even sent msgs to admin at kde.org, but that seems to be a
> > black hole.
> Not sure where you got that address from, but it is actually
> sysadmin at kde.org , which is also stated at the bottom of bugs.kde.org.
> And like Duncan already stated nicely, yes, logins are handled via
> cookies, and if you did mark the "restrict this session to this IP"
> the chance is high you will loose your session even faster.
> Anyway, to make it short, KDE's bug system is indeed suboptimal and it
> is not the first time someone complains about it. But then be reminded
> it is an upstream project (http://www.bugzilla.org/). And it was
> already discussed more than once to replace or improve it. Like
> always, manpower needed.

Bugzilla itself has indeed been improved over the last decade.  Now, if a 
cursory search come up empty, it will actually give you a file new bug 
option.  I can remember when you had to wade through the whole database 
before it would let you post a new one.  That, when the database has 15 
years worth of bugs it takes a 400wpm reader a day to slog through, was 
simply not acceptable, and I was just one of many to raise all sorts of 
hate and discontent about that ill advised "feature".  I used up a goodly 
portion of my 5 minute monologue developed for use when I have hit my thumb 
with a hammer on more than one occasion at some poor hapless soul.  The 
current version is indeed a huge improvement.

> Stating it is intended to not have bugreports
> is wrong in any way.

When you have had the access battles with bz I have had, believe me that is 
the impression I come away with.

> About Devs, consider 50 mailinglists or more, where you should read
> something, with maybe 10 new mails a day (a rather positive
> estimation).

Yes, considering that among the 40 or so I am subscribed to, some of which 
have several hundred postings a day(like lkml), I would agree that is a 
charitable estimate.

> Would you really read all of them, and that in your spare
> time?

I am retired so that is moot, (and I don't read all, likely a quick scan of 
the subject & who its from & go on in about .7 seconds) what is not moot is 
the need to get out of this chair and go loosen up the stiff joints of old 
age and do something that might look like work to some, keeps me out of the 
bars etc.  ;-)  Currently plotting on how to get a few hundred bd/ft of 
wild cherry the wind took down almost a year ago, in the form of 6 or 7 
foot logs that I can get sawed up at a mill about a mile away.  The downed 
trees however, are about 150 feet up a moderately steep hill about a block 
away, in 60+ foot pieces that are thicker than my chain saws blade is long.

> Luckily KDE has a bunch of great folks out there trying to help
> with user questions while not involved in the dev process at all (like
> Duncan).

A good example to be sure.

> Now, telling you this might not be the best place for something like
> this is no offense at all, it is a helping hand trying to guide you to
> a place it might better fit. If you have a problem with this other
> place, it is indeed a problem and can also be asked (see above for
> correct address).
Which is not where I just took step one of creating a new 'me'.  I see 
there are 2 msgs in that folder, perhaps one of them will be step 2.

Thanks Ingo.

Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Marvelous!  The super-user's going to boot me!
What a finely tuned response to the situation!
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

More information about the kde mailing list