ANNOUNCE: Xffm release
marcel.pol at home.nl
Wed Jun 8 16:41:36 CEST 2005
Edscott Wilson Garcia wrote:
> Xffm-184.108.40.206 is now released.
I have an issue with the plugins. They are called plugins, and according
to the lib.la files xffm uses dlopen for them. I'd think that if they
are plugins, they don't need a SONAME, and xffm could just dlopen the
Afaik a SONAME is only used for real libraries.
What happens is something different though. When xffm is run without the
lib.so files installed it gives this error:
** (xffm:23469): WARNING **: Cannot connect to session manager
** (xffm:23469): WARNING **: g_module_open(/usr/lib/libxffm_icons.so) ==
** (xffm:23469): WARNING **: Module cannot be opened! Check if correctly
** (xffm:23469): WARNING **: Show stopper: cannot get module info for
xffm: signal 11 received. Cleaning up before exiting
xffm: logfile = /home/marcel/.cache/xfce4/xffm/xffm_error.log
xffm: dumping core at= /home/marcel/.cache/xfce4/xffm
I'm no programmer, so I don't know if g_module_open is being used for
plugins or libraries, but it is trying to open a lib.so file, which is
or a plugin, or it is a development library. That confuses me a bit,
what is it? If it would be a real plugin, xffm shouldn't break on it not
being present. If it's a library, it should open the versioned lib.so.2.
So my question is, should I treat these files as plugins or libraries?
For reference, I listed the SONAME's below:
$ objdump -x libxffm_actions.so libxffm_basic.so \
libxffm_calls.so libxffm_cpy.so libxffm_primary.so \
libxffm_secondary.so libxffm_tubo.so |grep SO
More information about the Xfce4-dev