Ubuntu
gtk+2.0 package

Wrong path name 2.10.0, should be 2.4.0 for back-compatibility

Bug #54956 reported by Wen-Yen Chuang
2
Affects Status Importance Assigned to Milestone
gtk+2.0 (Ubuntu)
Invalid
Undecided
Ubuntu Desktop Bugs

Bug Description

This is bug of edgy, source package gtk+2.0, version 2.10.1-0ubuntu1.

Many modules of gtk+2.0 were installed in /usr/lib/gtk-2.0/2.4.0/.

However, edgy gtk+2.0 renamed it to 2.10.0, thus many modules will be disabled.

Involved packages I know includes: scim-bridge, uim-gtk2.0, gcin, and scim-gtk2-immodule.

Those GTK immodules needs to be renewed in /etc/gtk-2.0/gtk.immodules. The new libgtk2.0-0 searches only path 2.10.0, modules in path 2.4.0 will not be found.

It is reasonable to change it from 2.4.0 to 2.10.0. But it is better making a soft link, thus can keep compatibility, and backport GTK immodules will very smooth.

If edgy supports only 2.10.0, then many packages needs upgrade, and backport to dapper may encounter more trouble.

I think a soft link 2.4.0 points to 2.10.0 is good.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. That's not a GTK bug, those packages just need to rebuild, I rebuild most of main packages when I uploaded GTK, I'll rebuild those too later

Changed in gtk+2.0:
assignee: nobody → desktop-bugs
status: Unconfirmed → Rejected
Revision history for this message
Sebastien Bacher (seb128) wrote :

I've just uploaded a bunch of updates for that, most of issues should be fixed once they have built

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.