RSS/Atom feed Twitter
Site is read-only, email is disabled

strange behaviour when scrolling horizontal

This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2011-08-11 13:11:16 UTC (over 13 years ago)
postings
3

strange behaviour when scrolling horizontal

When scrolling left or right, many pixelgroups don't change, resulting in fractals and weird looking picture-parts. Scrolling up and down is working great.

I tried this on 2 computers, both with linux (up to date systems running: debian testing, ubuntu natty). Unfortunately both have an ati graphic card, so it might be a fglrx problem. Maybe someone knows a solution or can tell me if it's a problem for any linux users or just for those who have an ati card.

I already tried different settings in the xorg.conf, like activating horizonal sync and so on, but no effect.

Catalyst Control Center (amdcccle) has a setting like "Tear Free" - but this doesn't eliminate this error, it just seems to reduce it.

Thanks for any help - even if it's just help like finding out if it's a driver/card/gtk/gimp/... problem.!

2011-08-16 10:27:55 UTC (over 13 years ago)
postings
40

strange behaviour when scrolling horizontal

When scrolling left or right, many pixelgroups don't change, resulting in fractals and weird looking picture-parts. Scrolling up and down is working great.

I tried this on 2 computers, both with linux (up to date systems running: debian testing, ubuntu natty). Unfortunately both have an ati graphic card, so it might be a fglrx problem. Maybe someone knows a solution or can tell me if it's a problem for any linux users or just for those who have an ati card.

I already tried different settings in the xorg.conf, like activating horizonal sync and so on, but no effect.

Catalyst Control Center (amdcccle) has a setting like "Tear Free" - but this doesn't eliminate this error, it just seems to reduce it.

Thanks for any help - even if it's just help like finding out if it's a driver/card/gtk/gimp/... problem.!

Could you show what's in /var/log/Xorg.log (after scrolling horizontally). I've never used ATI cards because of the poor drivers. Gerard.

2011-08-16 11:11:30 UTC (over 13 years ago)
postings
3

strange behaviour when scrolling horizontal

Could you show what's in /var/log/Xorg.log (after scrolling horizontally). I've never used ATI cards because of the poor drivers. Gerard.

There seems to be no change in log..

Before horiz. scrolling: http://pastebin.com/fuGxKSes

After horiz. scrolling: http://pastebin.com/zakLAnXn

Thanks for reply!

2011-08-17 11:17:45 UTC (over 13 years ago)
postings
40

strange behaviour when scrolling horizontal

Could you show what's in /var/log/Xorg.log (after scrolling horizontally). I've never used ATI cards because of the poor drivers. Gerard.

There seems to be no change in log..

Before horiz. scrolling: http://pastebin.com/fuGxKSes

After horiz. scrolling: http://pastebin.com/zakLAnXn

Thanks for reply!

I noticed both DFP1 and CRT0 in the log. I assume you have a flat panel display,not a crt. Other than that I don't see anything wrong.

Another logfile that may contain info is /home//.xsession.errors. Gerard.

"Mikael St
2011-08-17 18:47:44 UTC (over 13 years ago)

strange behaviour when scrolling horizontal

On 2011-08-17 13:17, gerard82 wrote:

Another logfile that may contain info is /home//.xsession.errors.

I think that should be .xsession-errors

2011-08-18 09:23:53 UTC (over 13 years ago)
postings
3

strange behaviour when scrolling horizontal

On 2011-08-17 13:17, gerard82 wrote:

Another logfile that may contain info is /home//.xsession.errors.

I think that should be .xsession-errors

http://pastebin.com/20zMEL6Y - This is my .xsession-errors by running gimp and producing the error. Nothing useful in there I guess... I could also paste the .xsession-errors from before running gimp, but it's very very long...

I'm pretty sure that it's a driver problem, because there was once a combination of fglrx driver and gimp version that did not have this issue. Only problem is that I don't know if it is gimp or fglrx which produces this error... But I cannot see this problem in any other program, so I guess it might be a combination of both? (Or a GTK + fglrx error..)