Please transition gtk-nodoka-engine to multiarch

Bug #1716229 reported by Sergio Callegari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gtk-nodoka-engine (Ubuntu)
New
Undecided
Unassigned

Bug Description

Amd64 and i386 versions of this package conflict, when they should not.

This is because they install libraries in the wrong location. For instance, gtk2-engines-nodoka installs in

/usr/lib/gtk-2.0/2.10.0/engines/

The 64bit version of the engine should use

/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/

The 32bit version of the engine should use

/usr/lib/i386-linux-gnu/gtk-2.0/2.10.0/engines/

As an example, see how the gtk-engines-oxygen, that is properly multiarch manages this.

See also bug 902128

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gtk2-engines-nodoka (not installed)
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Sep 10 15:39:29 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-12 (1367 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: gtk-nodoka-engine
UpgradeStatus: Upgraded to zesty on 2017-05-04 (129 days ago)

Revision history for this message
Sergio Callegari (callegar) wrote :
Revision history for this message
Sergio Callegari (callegar) wrote :

As a consequence of this issue, if you are on a 64 bit system and you need to use legacy gtk2 applications, you get lots of warnings and a bad integration of the application with your system look and feel.

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

Other bug subscribers

Remote bug watches

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