After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 582282 - ia32 - lookup gio modules in $(host) directory
ia32 - lookup gio modules in $(host) directory
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gio
unspecified
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2009-05-12 08:05 UTC by Alexander Sack
Modified: 2018-05-24 11:51 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
prefer gio modules shipped in $(host) dir (1.60 KB, patch)
2009-05-12 08:08 UTC, Alexander Sack 		none Details | Review

Description Alexander Sack 2009-05-12 08:05:59 UTC 
Please describe the problem:
to improve the ia32 on amd64 case, similar to bug 582280, gio should look for plugins in the modules/$(host) directory.

Error messages:
/usr/lib/gio/modules/libgioremote-volume-monitor.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgioremote-volume-monitor.so
/usr/lib/gio/modules/libgiogconf.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgiogconf.so
/usr/lib/gio/modules/libgvfsdbus.so: wrong ELF class: ELFCLASS64
Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so

Ubuntu Bug: https://bugs.edge.launchpad.net/bugs/369498

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Alexander Sack 2009-05-12 08:08:40 UTC 
Created attachment 134470 [details] [review]
prefer gio modules shipped in $(host) dir
Comment 2 GNOME Infrastructure Team 2018-05-24 11:51:28 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/218.