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 671760 - tries to load gtk2 variant of libvte
tries to load gtk2 variant of libvte
Status: RESOLVED FIXED
Product: vte
Classification: Core
Component: general
0.31.x
Other Linux
: Normal normal
: vte-0-32
Assigned To: VTE Maintainers
VTE Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-10 05:56 UTC by Michael Biebl
Modified: 2012-03-10 19:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Biebl 2012-03-10 05:56:15 UTC 
When starting glade, I get


access("/usr/lib/glade/modules/libvte.so", F_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/glade/modules/../../libvte.so", F_OK) = -1 ENOENT (No such file or directory)
access("/lib/libvte.so", F_OK)          = -1 ENOENT (No such file or directory)
access("/usr/lib/libvte.so", F_OK)      = -1 ENOENT (No such file or directory)
access("/usr/local/lib/libvte.so", F_OK) = -1 ENOENT (No such file or directory)
write(2, "\nGladeUI-CRITICAL **: Unable to "..., 72
GladeUI-CRITICAL **: Unable to load module 'vte' from any search paths
) = 72
write(2, "\nGladeUI-WARNING **: Failed to l"..., 59
GladeUI-WARNING **: Failed to load external library 'vte'


libvte.so is the gtk2 based variant of vte.
It think glade should try to load /usr/lib/libvte2_90.so(.9) , i.e. the gtk3 based one.
Comment 1 Christian Persch 2012-03-10 15:56:08 UTC 
This was a vte bug; fixed on 0-32.
Comment 2 Michael Biebl 2012-03-10 19:05:10 UTC 
(In reply to comment #1)
> This was a vte bug; fixed on 0-32.

How can this be a bug in vte? 
Are you implying that vte-0.32 re-uses the libvte.so soname again?
Comment 3 Michael Biebl 2012-03-10 19:11:40 UTC 
(In reply to comment #2)
> (In reply to comment #1)
> > This was a vte bug; fixed on 0-32.
> 
> How can this be a bug in vte? 
> Are you implying that vte-0.32 re-uses the libvte.so soname again?

nvm, seen b1040ae9a4f4326dd30adcb62647e0930bdd196c.

Thanks for the fix