[Edgy] fonts are not displayed in GTK1 applications

I will attach some screenshot. The bug did not appear in Dapper.

I will attach some screenshots. The bug did not appear in Dapper.

This also applies for Audacity.

+ XMULE

all the failing applications show

>Gtk-WARNING **: Failed to load module "libgail.so": libgail.so: cannot open >shared object file: No such file or directory

>Gtk-WARNING **: Failed to load module "libatk-bridge.so": libatk-bridge.so: >cannot open shared object file: No such file or directory

changing the package the bug applies to to gtk 1.2

this works fine on a fresh edgy installation. so the problem may be caused by some configuration changes which I did.

Remove ~/.gtkrc-1.2-gnome2 , and make sure xfonts-{100dpi,75dpi,scalable} are installed.

Since this bug is rejected, I posted new experiences here (a duplicate of this):
https://launchpad.net/distros/ubuntu/+source/gtk+1.2/+bug/65708

r

I am getting a bit frustrated (and angry) with this bug, since I upgraded from dapper to edgy I have this bug, I read all the solutions and all the related bugs. I have the xfonts installed (all of the necessary), I don't have .gtkrc-1.2-gnome2, and my Fontpaths are ok. Why this bug is rejected if there is no solution for some users?

I rejected the bug as I reported it and as I solved it deleting some configuration files, which I excepted not to be existent on normal installations ( I used some gtk1 configuration tools, among these a gtk1 font changing tool).

You could have reopened the bug, but I do it for you now.

Thank very much. Today I keep on fighting with this bug, and I solved it for me by this way:

The origin of this bug, in my case, was the Fontpaths, I added the routes that Risto H. Kurppa proposed (/user/share/fonts/X11/...) but in order to make it work well I must delete the old ones even If they pointed to a existent folder (/user/share/X11/fonts/...).

My fontpaths working correctly now:

Section "Files"
 # path to defoma fonts
 FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
 # Añadido por mi
 FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
 FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
 FontPath "/usr/share/fonts/X11/100dpi"
 FontPath "/usr/share/fonts/X11/75dpi"
 FontPath "/usr/share/fonts/X11/misc"
 FontPath "/usr/share/fonts/X11/Type1"

EndSection

Thanks to Martin Jürgens and Risto H. Kurppa for his patience and posts on this bug. Sorry I don't know that I could change the status of the bug, in fact, I don't know how to do it now, I didn't find the option :(

> I don't know that I could change the status of the bug, in fact, I don't know how to do it now,

Just click on "gtk+1.2 (Ubuntu)" at the top of this page (in the center).

Then you have a drop-down menu "Status", where you can select the status of the bug.

Huh? Why was this rejected again? Still seems to be a bug for me, although removing configuration files sometimes works.

I don't rejected it, I am agree with you and still I think it is a bug.

Finally fixed this on my end after reading through a few bugs.
Everyone seems to be suggesting that you remove the file .gtkrc-1.2-gnome2 and that you paste some info into .gtkrc.mine.

The funny part is that looking in .gtkrc-1.2-gnome2 you will probably see an incude line for .gtkrc.mine. So how the heck will deleting .gtkrc-1.2-gnome2 get anything that you paste into .gtkrc.mine to work?

Here's what I did.
In .gtkrc-1.2-gnome2 paste the following:
style "user-font"
{
fontset="-bitstream-bitstream vera sans-medium-r-normal-*-12-*-*-*-*-*-iso8859-15"
}
widget_class "*" style "user-font"

Delete .gtkrc.mine

Everything should work perfectly.

I was only having trouble with audacity--and it is having no problems now.

On Sun, 2007-02-04 at 19:12 +0000, Chris Rose wrote:
> ** Changed in: gtk+1.2 (Ubuntu)
> Status: Confirmed => Rejected

Just because users are able to resolve this issue manually does not make
it a non-bug. Aside from the fact that many users wouldn't be competent
enough to manage to find the solution (here in the bug tracker or
where-be-it), this bug is just "ugly".

reopening, please do not close this bug!!

I don't see a bug here. If this can be fixed by undoing some changes to a config file then we need to find out what package or software (if any) is modifying the config file to a broken state in the first place. If modifying paths in xorg.conf fixes it, then this bug needs to be refiled against the relevant xorg package.

If someone can provide a set of steps for reproducing it that would be great, I can't reproduce the bug here.

Martin Jürgens wrote:
> I solved it deleting some configuration files, which I excepted not to
> be existent on normal installations ( I used some gtk1 configuration
> tools, among these a gtk1 font changing tool).

Can you provide some more details about which tools and what changes you made?

Maybe I'm missing something, but I don't see a GTK bug here.

I don't really know if this is the same that happened to me, but, i have an almos fresh install of the lates ubuntu edgy, and i installed support for truetype fonts and added a few custom ones in /home/user/.fonts/, and set one of those in system-->preferences-->fonts, then i found that some apps (synaptic package manager) wouldn't recognize the font, so i read this bug and i thought, maybe adding some symlinks to the /usr/share/fonts/ directory and it's subdirectories can solve it. And it DID!!!.

Note for newbiers than me: if you want to make a symlink just
1.- open nautilus (file explorer)
2.- make a link to the folder where you have your fonts
3.- copy it <cntrl>+C
4.- delete the link
4.- close nautilus
5.- open terminal
6.- type: "sudo nautilus" (without quotes)
7.- type your password
8.- go to /usr/share/fonts/ and paste it
9.- paste it into /usr/shar/fonts/ 1st level subdirectories (don't know if this is necessary)
10.- close nautilus
11.- check if it worked

Hope this helps, cheers

Or maybe it not the same problem/bug, let me know!

Not sure how many are still looking for solution. Doing 'sudo dpkg-reconfigure xserver-corg' solved my problem. Looks like some font paths were borked in xorg.conf.

I just installed Ubuntu Feisty on a fresh hard disk Partition , only to find gtk 1 apps not working.I think this bug should be generalised (just just edgy) , Ironically XMMS worked fine on the Live CD and also on Edgy.

None of the above workarounds work for Feisty . Anybody experiencing problems in Ubuntu Feisty ??

I am facing the same problem in Audacity on a fresh Feisty install.

The same bug was bugging me for the past few months in my Ubuntu Feisty .Gtk 1.2 applications started rendering text when i changed the default language to English (United States of America).I think the bug is not associated with libgtk itself but has to do with missing fonts , in my case English (India).

The same bug was bugging me for the past few months in my Ubuntu Feisty .Gtk 1.2 applications started rendering text when i changed the default language to English (United States of America).I think the bug is not associated with libgtk itself but has to do with missing fonts , in my case English (India).Maybe that's wy it was working fine in the lIve CD.

Try Changing the Default language to Something else Nikhil K.

akshay, it worked when i logged in next time. so maybe i had to restart the xserver or somethin

thanks

:-)

niyam

I don't think this bug is related to ligbtk.I think it has to do more with the language and localisation part of Ubuntu , about which I'm not familiar.Anybody care to find out which package that is ?

Got fixed for me on upgrade to gutsy from feisty

On 7/12/07, Akshay Srinivasan <email address hidden> wrote:
> I don't think this bug is related to ligbtk.I think it has to do more
> with the language and localisation part of Ubuntu , about which I'm not
> familiar.Anybody care to find out which package that is ?
>
> --
> [Edgy] fonts are not displayed in GTK1 applications
> https://bugs.launchpad.net/bugs/62300
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Amit Shah
http://www.amitshah.net/

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

This bug is no longer an issue for me.

Thanks for the update. Closing the report, if anyone should still encounter the issue, please reopen. Thanks.