Re: Anybody else seeing this GTK2 bug?

2006-07-31 Thread Cancel

I've fixed this bug by applying patch provided by someone in project's
bugzilla.You can build pathced library package using these files:

http://regolit.com/libcairo2/libcairo_1.2.0-3cancel.dsc
http://regolit.com/libcairo2/libcairo_1.2.0-3cancel.diff.gz
-- 
View this message in context: 
http://www.nabble.com/Anybody-else-seeing-this-GTK2-bug--tf1984833.html#a5578556
Sent from the Debian User forum at Nabble.com.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Anybody else seeing this GTK2 bug?

2006-07-24 Thread Florian Kulzer
On Sun, Jul 23, 2006 at 14:40:04 -0700, Steve Lamb wrote:
> Florian Kulzer wrote:
> > setting to take effect, though (if I remember correctly). I never had to
> > use the gnome-control-center after that, and the text rendering in all
> > my GTK2 applications is fine.
> 
> Not working here and KDE's been set up like that for a while now.  :(
> I've found that it is my anti-aliased fonts that are disappearing.

What else could be different on your box, fontconfig settings maybe?

$ awk '/^Name: fontconfig/,/^$/' /var/cache/debconf/config.dat
Name: fontconfig/enable_autohinter
Template: fontconfig/enable_autohinter
Owners: fontconfig

Name: fontconfig/enable_bitmaps
Template: fontconfig/enable_bitmaps
Value: false
Owners: fontconfig, fontconfig-config
Flags: seen

Name: fontconfig/hinting_type
Template: fontconfig/hinting_type
Value: Native
Owners: fontconfig, fontconfig-config
Flags: seen

Name: fontconfig/rendering_type
Template: fontconfig/rendering_type
Value: Subpixel rendering (LCD screens)
Owners: fontconfig
Flags: seen

Name: fontconfig/subpixel_rendering
Template: fontconfig/subpixel_rendering
Value: Automatic
Owners: fontconfig, fontconfig-config
Flags: seen

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Anybody else seeing this GTK2 bug?

2006-07-24 Thread Florian Kulzer
On Sun, Jul 23, 2006 at 22:46:37 +0200, Torquil Macdonald Sørensen wrote:
> On Sunday 23 July 2006 22:08, Florian Kulzer wrote:
> > How do you log on or start X? I use the graphical log-in screen of kdm.
> > I don't use ~/.Xresources at all (nor ~/.xinitrc or ~/.xsession) and my
> > Xft options get set to exactly what I would expect from the contents of
> > my ~/.fonts.conf:
> >
> > $ xrdb -query | grep Xft
> > Xft.antialias:  1
> > Xft.hinting:1
> > Xft.hintstyle:  hintfull
> >
> > Do you have any references to Xft in files in /etc/X11/Xresources or
> > /etc/X11/Xsession.d?
> 
> Finally! I found the culprit: it was ~/.qt/qtrc. I included the 
> lines 'enableXft=true' and 'useXft=true', and now I get 'Xft.antialias: 1' in 
> my Xresources automatically. And everything works beautifully.
> 
> It was this debian-kde post that told me what was wrong:
> http://www.mail-archive.com/debian-kde%40lists.debian.org/msg25650.html
> 
> I really appreciate all your kind help, Florian. Thanks!

No problem, it's fun to poke at these things. Besides, I learned
something, too. I didn't know about the ~/.qt/qtrc settings; they are
indeed both "true" for my user. 

-- 
Regards,
  Florian



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Steve Lamb
Florian Kulzer wrote:
> setting to take effect, though (if I remember correctly). I never had to
> use the gnome-control-center after that, and the text rendering in all
> my GTK2 applications is fine.

Not working here and KDE's been set up like that for a while now.  :(
I've found that it is my anti-aliased fonts that are disappearing.

-- 
 Steve C. Lamb | But who decides what they dream?
   PGP Key: 8B6E99C5   |   And dream I do...
---+-



signature.asc
Description: OpenPGP digital signature


Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Torquil Macdonald Sørensen
On Sunday 23 July 2006 22:08, Florian Kulzer wrote:
> How do you log on or start X? I use the graphical log-in screen of kdm.
> I don't use ~/.Xresources at all (nor ~/.xinitrc or ~/.xsession) and my
> Xft options get set to exactly what I would expect from the contents of
> my ~/.fonts.conf:
>
> $ xrdb -query | grep Xft
> Xft.antialias:  1
> Xft.hinting:1
> Xft.hintstyle:  hintfull
>
> Do you have any references to Xft in files in /etc/X11/Xresources or
> /etc/X11/Xsession.d?

Finally! I found the culprit: it was ~/.qt/qtrc. I included the 
lines 'enableXft=true' and 'useXft=true', and now I get 'Xft.antialias: 1' in 
my Xresources automatically. And everything works beautifully.

It was this debian-kde post that told me what was wrong:
http://www.mail-archive.com/debian-kde%40lists.debian.org/msg25650.html

I really appreciate all your kind help, Florian. Thanks!

Best regards,
Torquil M. Sørensen



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Torquil Macdonald Sørensen
On Sunday 23 July 2006 22:08, Florian Kulzer wrote:
> On Sun, Jul 23, 2006 at 21:21:26 +0200, Torquil Macdonald Sørensen wrote:
> > I checked the X resources with 'xrdb -query', and found the following Xft
> > related settings:
> >
> > Xft.antialias:  0
> > Xft.hinting:1
> > Xft.hintstyle:  hintmedium
> > Xft.rgba:   rgb
> >
> > I don't know why Xft.antialias was set to 0, since from .fonts.conf I
> > would think that it should be 1:
> >
> > The relevant part of .fonts.conf:
> >  
> >   
> >true
> >   
> >  
> >
> > But setting 'Xft.antialias: 1' in .Xresources and
> > running 'xrdb -merge .Xresources' has the same effect as
> > running 'gnome-settings-daemon': it fixes the problem. But the strange
> > thing is that this .Xresrouces setting is not persistent across logging
> > out and then in, as all the other .Xresources settings I use are. So
> > something must be altering the Xft.antialias setting from 1 to 0 when I
> > log into KDE.
>
> How do you log on or start X? I use the graphical log-in screen of kdm.
> I don't use ~/.Xresources at all (nor ~/.xinitrc or ~/.xsession) and my
> Xft options get set to exactly what I would expect from the contents of
> my ~/.fonts.conf:
>
> $ xrdb -query | grep Xft
> Xft.antialias:  1
> Xft.hinting:1
> Xft.hintstyle:  hintfull
>
> Do you have any references to Xft in files in /etc/X11/Xresources or
> /etc/X11/Xsession.d?

I use an .xsession file with 'startkde' at the end, but I get the same 
behaviour with no .xsession or .xinitrc, and just choosing "KDE" from the 
Session Type menu in kdm.
It is interesting that using Session Type: Twm gives no lines for Xft in the 
xrdb -query output, but GTK applications work correctly with antialiasing in 
that case. I have no references to xft inside /etc/X11. And my .Xresources 
doesn't contain any other lines that should conflict with the Xft lines that 
appear automatically.

Best regards,
Torquil M. Sørensen



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Florian Kulzer
On Sun, Jul 23, 2006 at 21:21:26 +0200, Torquil Macdonald Sørensen wrote:
> I checked the X resources with 'xrdb -query', and found the following Xft 
> related settings:
> 
> Xft.antialias:  0
> Xft.hinting:1
> Xft.hintstyle:  hintmedium
> Xft.rgba:   rgb
> 
> I don't know why Xft.antialias was set to 0, since from .fonts.conf I would 
> think that it should be 1:
> 
> The relevant part of .fonts.conf:
>  
>   
>true
>   
>  
> 
> But setting 'Xft.antialias: 1' in .Xresources and 
> running 'xrdb -merge .Xresources' has the same effect as 
> running 'gnome-settings-daemon': it fixes the problem. But the strange thing 
> is that this .Xresrouces setting is not persistent across logging out and 
> then in, as all the other .Xresources settings I use are. So something must 
> be altering the Xft.antialias setting from 1 to 0 when I log into KDE.

How do you log on or start X? I use the graphical log-in screen of kdm.
I don't use ~/.Xresources at all (nor ~/.xinitrc or ~/.xsession) and my
Xft options get set to exactly what I would expect from the contents of
my ~/.fonts.conf:

$ xrdb -query | grep Xft
Xft.antialias:  1
Xft.hinting:1
Xft.hintstyle:  hintfull

Do you have any references to Xft in files in /etc/X11/Xresources or
/etc/X11/Xsession.d?

-- 
Regards,
  Florian



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Torquil Macdonald Sørensen
> I also had this problem of the gnome-control-center screwing with the
> font sizes; that is one of the reasons why I never open it anymore.
>
> So, what is the difference between your setup and mine? Maybe it is a
> setting in ~/.gtkrc-2.0. Here is what I have (I had gtk2-engines-gtk-qt
> installed at one point):
>
> # This file was written by KDE
> # You can edit it in the KDE control center, under "GTK Styles and Fonts"
>
> include "/usr/share/themes/Qt/gtk-2.0/gtkrc"
>
> style "user-font"
> {
> font_name="Bitstream Vera Sans 11"
> }
> widget_class "*" style "user-font"
>
> gtk-theme-name="Qt"
> gtk-font-name="Bitstream Vera Sans 11"
> # ~/.gtkrc-2.0 ends above this line
>
> Maybe it is something in the general X setup. Do you run a font server?
> I use xfs and have it listed as the first FontPath in my xorg.conf.

I checked the X resources with 'xrdb -query', and found the following Xft 
related settings:

Xft.antialias:  0
Xft.hinting:1
Xft.hintstyle:  hintmedium
Xft.rgba:   rgb

I don't know why Xft.antialias was set to 0, since from .fonts.conf I would 
think that it should be 1:

The relevant part of .fonts.conf:
 
  
   true
  
 

But setting 'Xft.antialias: 1' in .Xresources and 
running 'xrdb -merge .Xresources' has the same effect as 
running 'gnome-settings-daemon': it fixes the problem. But the strange thing 
is that this .Xresrouces setting is not persistent across logging out and 
then in, as all the other .Xresources settings I use are. So something must 
be altering the Xft.antialias setting from 1 to 0 when I log into KDE.

Best regards
Torquil Sørensen



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Torquil Macdonald Sørensen
> I also had this problem of the gnome-control-center screwing with the
> font sizes; that is one of the reasons why I never open it anymore. So,
> what is the difference between your setup and mine? Maybe it is a
> setting in ~/.gtkrc-2.0. Here is what I have (I had gtk2-engines-gtk-qt
> installed at one point):
> # This file was written by KDE
> # You can edit it in the KDE control center, under "GTK Styles and
> Fonts"
> include "/usr/share/themes/Qt/gtk-2.0/gtkrc"
> style "user-font"
> {
> font_name="Bitstream Vera Sans 11"
> }
> widget_class "*" style "user-font"
> gtk-theme-name="Qt"
> gtk-font-name="Bitstream Vera Sans 11"
> # ~/.gtkrc-2.0 ends above this line
> Maybe it is something in the general X setup. Do you run a font server?
> I use xfs and have it listed as the first FontPath in my xorg.conf.

I did not have a .gtkrc-2.0. I tried with yours, after installing 
gtk2-engines-gtk-qt, but it didn't fix the bug. It did look different,  
though. Yes, I run xfs, and I originally had only unix:/7100 listed in the
font section of xorg.conf. I also added the standard font directory paths,
but it did not have any effect.

Deleting everything gnome-related in ~ did not change anything either 
(.gnome2, .gnome2_private, .gconf, .gconfd)

Best regards
Torquil Sørensen



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Florian Kulzer
On Sun, Jul 23, 2006 at 18:36:49 +0200, Torquil Macdonald Sørensen wrote:
> > With KDE it is of course possible to fine-tune the font settings in a nice
> > menu which uses the proper technical terms.  Just go to "Control Center >
> > Appearance & Themes > Fonts" and select "Use anti-aliasing for fonts". You
> > can use the "Configure..." button to set the hinting style, etc. Your
> > ~/.fonts.conf will be rewritten accordingly as soon as you press "Apply" or
> > "OK". You have to log out and log in again for the setting to take effect,
> > though (if I remember correctly). I never had to use the
> > gnome-control-center after that, and the text rendering in all my GTK2
> > applications is fine.
> 
> Yes, you are right. The KDE control center does indeed modify .fonts.conf. So 
> I have activated the anti-aliasing from there instead. But the GTK bug is 
> around until I start gnome-control-center (or gnome-settings-daemon). I can 
> see that after logging in to KDE, my GTK apps are not anti-aliased until I 
> run one of those commands, even though .fonts.conf says that they should be. 
> This is independent of $GDK_USE_XFT=0/1. But after I run 
> gnome-settings-daemon or gnome-control-center, fonts in GTK apps become 
> anti-aliased and smaller, and the bug disappears. In addition KDE fonts also 
> become smaller. All this while not changing .fonts.conf at all...

I also had this problem of the gnome-control-center screwing with the
font sizes; that is one of the reasons why I never open it anymore.

So, what is the difference between your setup and mine? Maybe it is a
setting in ~/.gtkrc-2.0. Here is what I have (I had gtk2-engines-gtk-qt
installed at one point):

# This file was written by KDE
# You can edit it in the KDE control center, under "GTK Styles and Fonts"

include "/usr/share/themes/Qt/gtk-2.0/gtkrc"

style "user-font"
{
font_name="Bitstream Vera Sans 11"
}
widget_class "*" style "user-font"

gtk-theme-name="Qt"
gtk-font-name="Bitstream Vera Sans 11"
# ~/.gtkrc-2.0 ends above this line

Maybe it is something in the general X setup. Do you run a font server?
I use xfs and have it listed as the first FontPath in my xorg.conf.

-- 
Regards,
  Florian



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Torquil Macdonald Sørensen
> With KDE it is of course possible to fine-tune the font settings in a nice
> menu which uses the proper technical terms.  Just go to "Control Center >
> Appearance & Themes > Fonts" and select "Use anti-aliasing for fonts". You
> can use the "Configure..." button to set the hinting style, etc. Your
> ~/.fonts.conf will be rewritten accordingly as soon as you press "Apply" or
> "OK". You have to log out and log in again for the setting to take effect,
> though (if I remember correctly). I never had to use the
> gnome-control-center after that, and the text rendering in all my GTK2
> applications is fine.

Yes, you are right. The KDE control center does indeed modify .fonts.conf. So 
I have activated the anti-aliasing from there instead. But the GTK bug is 
around until I start gnome-control-center (or gnome-settings-daemon). I can 
see that after logging in to KDE, my GTK apps are not anti-aliased until I 
run one of those commands, even though .fonts.conf says that they should be. 
This is independent of $GDK_USE_XFT=0/1. But after I run 
gnome-settings-daemon or gnome-control-center, fonts in GTK apps become 
anti-aliased and smaller, and the bug disappears. In addition KDE fonts also 
become smaller. All this while not changing .fonts.conf at all...

Best regards,
Torquil M. Sørensen




Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Florian Kulzer
On Sun, Jul 23, 2006 at 17:43:16 +0200, Torquil Macdonald Sørensen wrote:
> On Sunday 23 July 2006 16:17, Florian Kulzer wrote:
> > I suspect that the Gnome font configuration dialog uses ~/.fonts.conf as
> > well to set up the font rendering according to the user's preferences,
> > but I don't know for sure since I don't use Gnome. You can make some
> > changes via the dialog and check this file, then you will see which
> > Gnome option corresponds to which font setting. (The fact that the Gnome
> > developers refuse to use standard technical terms like "anti-aliasing"
> > is one of the main reasons why I don't use Gnome, by the way.)
> 
> I am using KDE, and I just found out that every time I log in, I have to 
> start 
> the gnome-control-center and turn on the anti-aliasing (Even if it says that 
> it is already on. I change it to a different setting, and then back again). 
> If I don't do that, I still have the original bug in my GTK applications. But 
> the .fonts.conf file is unchanged through that process.

With KDE it is of course possible to fine-tune the font settings in a
nice menu which uses the proper technical terms.  Just go to "Control
Center > Appearance & Themes > Fonts" and select "Use anti-aliasing for
fonts". You can use the "Configure..." button to set the hinting style,
etc. Your ~/.fonts.conf will be rewritten accordingly as soon as you
press "Apply" or "OK". You have to log out and log in again for the
setting to take effect, though (if I remember correctly). I never had to
use the gnome-control-center after that, and the text rendering in all
my GTK2 applications is fine.

-- 
Regards,
  Florian



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Torquil Macdonald Sørensen
On Sunday 23 July 2006 16:17, Florian Kulzer wrote:
> I suspect that the Gnome font configuration dialog uses ~/.fonts.conf as
> well to set up the font rendering according to the user's preferences,
> but I don't know for sure since I don't use Gnome. You can make some
> changes via the dialog and check this file, then you will see which
> Gnome option corresponds to which font setting. (The fact that the Gnome
> developers refuse to use standard technical terms like "anti-aliasing"
> is one of the main reasons why I don't use Gnome, by the way.)

I am using KDE, and I just found out that every time I log in, I have to start 
the gnome-control-center and turn on the anti-aliasing (Even if it says that 
it is already on. I change it to a different setting, and then back again). 
If I don't do that, I still have the original bug in my GTK applications. But 
the .fonts.conf file is unchanged through that process.

Best regards
Torquil M. Sørensen



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Torquil Macdonald Sørensen
To be absolutely sure that you have the environment variable set correctly, 
you could run 'export GDK_USE_XFT=1' in an xterm, and then run 
boa-constructor afterwards from the same xterm.

Best regards,
Torquil Sørensen

On Sunday 23 July 2006 16:10, you wrote:
> I do as your sugesstion. but my font still disappear for some part.
> This symtom appear for boa-constructor which use wxpython.
>
> Maybe It is not like you issue.
>
> Best regards,
> Kan
>
>
> เมื่อ อา. 2006-07-23 เวลา 15:39 +0200, Torquil Macdonald Sørensen
>
> เขียนว่า:
> > > Where to set anti-aliasing? I don't see this configuration on gnome
> > > font preference. See attach for detail
> >
> > I didn't find it either, so instead I set put 'export GDK_USE_XFT=1' in
> > ~/.xsession and ~/.bashrc. It will then apply to applications started
> > both from X menus, and from xterm windows. But there is probably a better
> > way to do it.
> >
> > Looking at the Gnome Font preferences, it looks to me that it is the
> > "Best contrast" setting that is equavalent to anti-aliasing. But it is
> > not clear to me if that will apply to all GTK apps or just Gnome apps.
> >
> > Best regards,
> > Torquil Sørensen



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Florian Kulzer
On Sun, Jul 23, 2006 at 15:39:54 +0200, Torquil Macdonald Sørensen wrote:
> > Where to set anti-aliasing? I don't see this configuration on gnome font
> > preference. See attach for detail
> 
> I didn't find it either, so instead I set put 'export GDK_USE_XFT=1' in 
> ~/.xsession and ~/.bashrc. It will then apply to applications started both 
> from X menus, and from xterm windows. But there is probably a better way to 
> do it.
> 
> Looking at the Gnome Font preferences, it looks to me that it is the "Best 
> contrast" setting that is equavalent to anti-aliasing. But it is not clear to 
> me if that will apply to all GTK apps or just Gnome apps.

You can set it in your ~/.fonts.conf, then it should be the same for all
(freetype using) X applications. I have an LCD display and like to use
anti-aliasing with hintstyle "full", but without RGB subpixel hinting.
The corresponding ~/.fonts.conf looks like this:




 
  
   true
  
 
 
  
   hintfull
  
 
 
  
   none
  
 
 
  
   true
  
 


If you do not like how your fonts look with full hinting then you can
use anti-aliasing only:




 
  
   false
  
 
 
  
   true
  
 


I suspect that the Gnome font configuration dialog uses ~/.fonts.conf as
well to set up the font rendering according to the user's preferences,
but I don't know for sure since I don't use Gnome. You can make some
changes via the dialog and check this file, then you will see which
Gnome option corresponds to which font setting. (The fact that the Gnome
developers refuse to use standard technical terms like "anti-aliasing"
is one of the main reasons why I don't use Gnome, by the way.)

-- 
Regards,
  Florian



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Surachai Locharoen




I do as your sugesstion. but my font still disappear for some part.
This symtom appear for boa-constructor which use wxpython.

Maybe It is not like you issue.

Best regards,
Kan


เมื่อ อา. 2006-07-23 เวลา 15:39 +0200, Torquil Macdonald Sørensen เขียนว่า:


> Where to set anti-aliasing? I don't see this configuration on gnome font
> preference. See attach for detail

I didn't find it either, so instead I set put 'export GDK_USE_XFT=1' in 
~/.xsession and ~/.bashrc. It will then apply to applications started both 
from X menus, and from xterm windows. But there is probably a better way to 
do it.

Looking at the Gnome Font preferences, it looks to me that it is the "Best 
contrast" setting that is equavalent to anti-aliasing. But it is not clear to 
me if that will apply to all GTK apps or just Gnome apps.

Best regards,
Torquil Sørensen







Screenshot-Find-Replace.png
Description: PNG image


Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Torquil Macdonald Sørensen
> Where to set anti-aliasing? I don't see this configuration on gnome font
> preference. See attach for detail

I didn't find it either, so instead I set put 'export GDK_USE_XFT=1' in 
~/.xsession and ~/.bashrc. It will then apply to applications started both 
from X menus, and from xterm windows. But there is probably a better way to 
do it.

Looking at the Gnome Font preferences, it looks to me that it is the "Best 
contrast" setting that is equavalent to anti-aliasing. But it is not clear to 
me if that will apply to all GTK apps or just Gnome apps.

Best regards,
Torquil Sørensen



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Surachai Locharoen




On Sun, 2006-07-23 at 15:12 +0200, Torquil Macdonald Sørensen wrote:


On Sunday 23 July 2006 13:53, Florian Kulzer wrote:
> On Sun, Jul 23, 2006 at 09:52:10 +0200, Torquil Macdonald Sørensen wrote:
> > > > Hello
> > > >
> > > > Is anybody else seeing this bug?:
> > > >
> > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377850
> > > >
> > > > It makes it quite problematic for me to use any GTK applications,
> > > > so I would really appreciate any hints as to what might be
> > > > causing it. I am wondering whether if it really is a GTK bug, or
> > > > maybe it is X.org?
> > >
> > > My system is debian kernel 2.6.17, gtk2, gnome2.14. I have the same
> > > problem.
> > > especialy in boa-constructor package which use wxPython.
> >
> > I have this bug in gqview, bittornado-gui (which uses python-wxgtk2.6),
> > avidemux & dcgui, which are all the GTK2 applications I use.
> >
> > Maybe it is related to X.org. My video card is ATI Mobility Radeon 9600
> > M10, and I am using the "radeon" driver.
>
> If you are using non-anti-aliased fonts, then it might be a known
> libcairo2 bug:
>
> http://lists.debian.org/debian-user/2006/07/msg00992.html
> http://lists.debian.org/debian-user/2006/07/msg01023.html
>
> The easiest workaround seems to be to switch to anti-aliased GUI fonts.
> Downgrading libcairo2 is also possible, but it might be annoying since
> many other packages depend on the newest version.

Thanks Florian, your suggestion was correct! I switched on anti-aliasing, and 
everything is back to normal.

Best regards,
TMS




Where to set anti-aliasing? I don't see this configuration on gnome font preference. See attach for detail




Screenshot-Font Preferences.png
Description: PNG image


Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Torquil Macdonald Sørensen
On Sunday 23 July 2006 13:53, Florian Kulzer wrote:
> On Sun, Jul 23, 2006 at 09:52:10 +0200, Torquil Macdonald Sørensen wrote:
> > > > Hello
> > > >
> > > > Is anybody else seeing this bug?:
> > > >
> > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377850
> > > >
> > > > It makes it quite problematic for me to use any GTK applications,
> > > > so I would really appreciate any hints as to what might be
> > > > causing it. I am wondering whether if it really is a GTK bug, or
> > > > maybe it is X.org?
> > >
> > > My system is debian kernel 2.6.17, gtk2, gnome2.14. I have the same
> > > problem.
> > > especialy in boa-constructor package which use wxPython.
> >
> > I have this bug in gqview, bittornado-gui (which uses python-wxgtk2.6),
> > avidemux & dcgui, which are all the GTK2 applications I use.
> >
> > Maybe it is related to X.org. My video card is ATI Mobility Radeon 9600
> > M10, and I am using the "radeon" driver.
>
> If you are using non-anti-aliased fonts, then it might be a known
> libcairo2 bug:
>
> http://lists.debian.org/debian-user/2006/07/msg00992.html
> http://lists.debian.org/debian-user/2006/07/msg01023.html
>
> The easiest workaround seems to be to switch to anti-aliased GUI fonts.
> Downgrading libcairo2 is also possible, but it might be annoying since
> many other packages depend on the newest version.

Thanks Florian, your suggestion was correct! I switched on anti-aliasing, and 
everything is back to normal.

Best regards,
TMS



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Florian Kulzer
On Sun, Jul 23, 2006 at 09:52:10 +0200, Torquil Macdonald Sørensen wrote:
> > > Hello
> > > 
> > > Is anybody else seeing this bug?:
> > > 
> > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377850
> > > 
> > > It makes it quite problematic for me to use any GTK applications,
> > > so I would really appreciate any hints as to what might be
> > > causing it. I am wondering whether if it really is a GTK bug, or
> > > maybe it is X.org?
> 
> > My system is debian kernel 2.6.17, gtk2, gnome2.14. I have the same
> > problem.
> > especialy in boa-constructor package which use wxPython.
> 
> I have this bug in gqview, bittornado-gui (which uses python-wxgtk2.6), 
> avidemux & dcgui, which are all the GTK2 applications I use.
> 
> Maybe it is related to X.org. My video card is ATI Mobility Radeon 9600 M10, 
> and I am using the "radeon" driver.

If you are using non-anti-aliased fonts, then it might be a known
libcairo2 bug:

http://lists.debian.org/debian-user/2006/07/msg00992.html
http://lists.debian.org/debian-user/2006/07/msg01023.html

The easiest workaround seems to be to switch to anti-aliased GUI fonts.
Downgrading libcairo2 is also possible, but it might be annoying since
many other packages depend on the newest version.

-- 
Regards,
  Florian



Re: Anybody else seeing this GTK2 bug?

2006-07-23 Thread Torquil Macdonald Sørensen
> > Hello
> > 
> > Is anybody else seeing this bug?:
> > 
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377850
> > 
> > It makes it quite problematic for me to use any GTK applications,
> > so I would really appreciate any hints as to what might be
> > causing it. I am wondering whether if it really is a GTK bug, or
> > maybe it is X.org?

> My system is debian kernel 2.6.17, gtk2, gnome2.14. I have the same
> problem.
> especialy in boa-constructor package which use wxPython.

I have this bug in gqview, bittornado-gui (which uses python-wxgtk2.6), 
avidemux & dcgui, which are all the GTK2 applications I use.

Maybe it is related to X.org. My video card is ATI Mobility Radeon 9600 M10, 
and I am using the "radeon" driver.

Best regards,
TMS


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: Anybody else seeing this GTK2 bug?

2006-07-22 Thread Surachai Locharoen




My system is debian kernel 2.6.17, gtk2, gnome2.14. I have the same problem.
especialy in boa-constructor package which use wxPython.


เมื่อ ส. 2006-07-22 เวลา 14:06 -0500, Ron Johnson เขียนว่า:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Torquil Macdonald S?rensen wrote:
> Hello
> 
> Is anybody else seeing this bug?:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377850
> 
> It makes it quite problematic for me to use any GTK applications,
> so I would really appreciate any hints as to what might be
> causing it. I am wondering whether if it really is a GTK bug, or
> maybe it is X.org?

Running Sid, X7, Gtk & GNOME, no.

- --
Ron Johnson, Jr.
Jefferson LA  USA

Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEwnc6S9HxQb37XmcRAj90AJ9Ww1trqqiPRNk6WQhzDQ8Ie4OltQCglhEO
TqVaVkEScLwzmdcIOoxfSmY=
=jhHR
-END PGP SIGNATURE-








Re: Anybody else seeing this GTK2 bug?

2006-07-22 Thread Ron Johnson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Torquil Macdonald S?rensen wrote:
> Hello
> 
> Is anybody else seeing this bug?:
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377850
> 
> It makes it quite problematic for me to use any GTK applications,
> so I would really appreciate any hints as to what might be
> causing it. I am wondering whether if it really is a GTK bug, or
> maybe it is X.org?

Running Sid, X7, Gtk & GNOME, no.

- --
Ron Johnson, Jr.
Jefferson LA  USA

Is "common sense" really valid?
For example, it is "common sense" to white-power racists that
whites are superior to blacks, and that those with brown skins
are mud people.
However, that "common sense" is obviously wrong.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEwnc6S9HxQb37XmcRAj90AJ9Ww1trqqiPRNk6WQhzDQ8Ie4OltQCglhEO
TqVaVkEScLwzmdcIOoxfSmY=
=jhHR
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]