! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
When trying to view a files/dirs properties, xffm crashes
Status:
CLOSED: FIXED
Severity:
critical

Comments

Description Nikolas.Arend 2004-07-06 11:07:18 CEST
xffm crashes when trying to show a files/dirs properties. This happens with
either the taskbar button or right-click->Properties. xffm does not receive
signal 9, though, but signal 6. I have todays (20040706) CVS version of all
relevant packages installed. Output is attached.
Comment 1 Nikolas.Arend 2004-07-06 11:07:20 CEST
Additional information:

Here's the output:

** Message: xffm: module libxfce4_mime_icons.so successfully loaded
** Message: xffm: loading toolbar buttons
** Message: xffm: module libxfce4_mime.so successfully loaded

** ERROR **: g_module_open(/usr/lib/xffm/libxffm_prop.so) == NULL

aborting...
xffm: signal 6 received. Cleaning up before exiting
Comment 2 edscott editbugs 2004-07-06 12:51:41 CEST
This is strange. The signal 6 is just because it cannot open a required
library. Nothing has been changed with this library, which creates the
properties window, for the last 3 or 4 months. Check for permissions on file
/usr/lib/xffm/libxffm_prop.so

Try doing a
./configure && make clean install
Comment 3 Nikolas.Arend 2004-07-06 13:16:10 CEST
ok, first thing is that the xffm library names are crippled (the .so is
missing). After freshly checking out the code from CVS and building it, still
the same.
But I'm installing into a non-standard directory in order to build rpm's. I
now realized that I'm reminded to do a libtool --finish lib_dir/, but that is
not the problem, I guess.
Since xffm looks for /usr/lib/xffm/libxffm_prop.so and the library name is not
ok, the load fails. So I think there's nothing wrong with libxffm_prop.so but
with the Makefiles/building stuff.

edited on: 07-06 13:18
Comment 4 Nikolas.Arend 2004-07-06 14:25:28 CEST
Sorry if you receive this note twice but I'm not sure if it was processed
corretly since I never got an email from the xfce bug tracker system.

Actual note:

ok, first thing is that the xffm library names are crippled (the .so is
missing). After freshly checking out the code from CVS and building it, still
the same.
But I'm installing into a non-standard directory in order to build rpm's. I
now realized that I'm reminded to do a libtool --finish lib_dir/, but that is
not the problem, I guess.
Since xffm looks for /usr/lib/xffm/libxffm_prop.so and the library name is not
ok, the load fails. So I think there's nothing wrong with libxffm_prop.so but
with the Makefiles/building stuff.
Comment 5 edscott editbugs 2004-07-07 03:16:44 CEST
From your description, the problem might be that your non-standard library
directory is not in the ld path. Check your ld.conf file.
If it's not that, then let's look at the file name:
library=g_strconcat("libxffm_prop.",G_MODULE_SUFFIX, NULL);
module = g_build_filename (LIBDIR, "xffm", library, NULL);
Check what LIBDIR is. It should be $prefix/lib

I'm currently using --prefix=/var/xfce for both xffm and xfce4-modules and
they work nicely on a xfce_4.0.5 gentoo box.
Comment 6 Nikolas.Arend 2004-07-07 08:40:37 CEST
First of all, I'm building xfce4 from CVS and preparing rpm packages on my
system for months and this kind of problem never occured with xffm before. I
remember now that I had the problem of screwed up library names with
libxfcegui4 once, but apparently it vanished in the next "release". Below is
a list of the installed libraries so you can see what I mean.
My install prefix is /usr for all the xfce4 stuff. From xffm's output I see
that it looks in /usr/lib/xffm, which is the right place, but the problem
doesn't seem to be the ld configuration. The line

module = g_build_filename (LIBDIR, "xffm", library, NULL);

builds the right filename (/usr/lib/xffm/libxffm_prop.so), only that file
doesn't exist (see below). After building xffm, I find the following in the
xffm/modules/.libs/ directory

libxffm_prop -> libxffm_prop.0.0.0
libxffm_prop.0 -> libxffm_prop.0.0.0
libxffm_prop.0.0.0
libxffm_prop.la -> ../libxffm_prop.la
libxffm_prop.lai
libxffm_prop_la-properties.o

That doesn't look right, does it?
So what could be the problem? I can hardly believe it's got something to do
with my system configuration, since it worked so far and works with all other
xfce4 modules, but I will look further into it.


/usr/lib/libxffm_actions
/usr/lib/libxffm_actions.1
/usr/lib/libxffm_actions.1.0.0
/usr/lib/libxffm_actions.la
/usr/lib/libxffm_book
/usr/lib/libxffm_book.1
/usr/lib/libxffm_book.1.0.0
/usr/lib/libxffm_book.la
/usr/lib/libxffm_calls
/usr/lib/libxffm_calls.1
/usr/lib/libxffm_calls.1.0.0
/usr/lib/libxffm_calls.la
/usr/lib/libxffm_cpy
/usr/lib/libxffm_cpy.1
/usr/lib/libxffm_cpy.1.0.0
/usr/lib/libxffm_cpy.la
/usr/lib/libxffm_fgr
/usr/lib/libxffm_fgr.1
/usr/lib/libxffm_fgr.1.0.0
/usr/lib/libxffm_fgr.la
/usr/lib/libxffm_fstab
/usr/lib/libxffm_fstab.1
/usr/lib/libxffm_fstab.1.0.0
/usr/lib/libxffm_fstab.la
/usr/lib/libxffm_goto
/usr/lib/libxffm_goto.1
/usr/lib/libxffm_goto.1.0.0
/usr/lib/libxffm_goto.la
/usr/lib/libxffm_rcp
/usr/lib/libxffm_rcp.1
/usr/lib/libxffm_rcp.1.0.0
/usr/lib/libxffm_rcp.la
/usr/lib/libxffm_trash
/usr/lib/libxffm_trash.1
/usr/lib/libxffm_trash.1.0.0
/usr/lib/libxffm_trash.la
/usr/lib/libxffm_tubo
/usr/lib/libxffm_tubo.1
/usr/lib/libxffm_tubo.1.0.0
/usr/lib/libxffm_tubo.la
/usr/lib/libxffmsmb
/usr/lib/libxffmsmb.1
/usr/lib/libxffmsmb.1.0.0
/usr/lib/libxffmsmb.la
/usr/lib/pkgconfig
/usr/lib/pkgconfig/xffm-1.0.pc
/usr/lib/xfce4
/usr/lib/xfce4/mcs-plugins
/usr/lib/xfce4/mcs-plugins/libxffmsettings
/usr/lib/xfce4/mcs-plugins/libxffmsettings.la
/usr/lib/xffm
/usr/lib/xffm/libxffm_prop
/usr/lib/xffm/libxffm_prop.0
/usr/lib/xffm/libxffm_prop.0.0.0
/usr/lib/xffm/libxffm_prop.la
Comment 7 edscott editbugs 2004-07-07 13:02:56 CEST
Perhaps my autostuff tools are broken and I generated broken build tools for
your system. If that is the case, if you run ./autogen.sh from within the xffm
directory should fix the problem.
Comment 8 Nikolas.Arend 2004-07-07 14:14:28 CEST
well definitely, that is what I should have done earlier ;-)

Thanks!
Comment 9 edscott editbugs 2004-07-15 02:58:28 CEST
build tools were just a bit broken

Bug #249

Reported by:
Nikolas.Arend
Reported on: 2004-07-06
Last modified on: 2009-07-14

People

Assignee:
edscott
CC List:
0 users

Version

Version:
unspecified

Attachments

Additional information