Hi, using recently released xfce4-sensors-plugin, I can't add it to the panel, it's removed instantly (it even made my panel crash, twice). I may think it's because it tries to open /proc/acpi/info wich I don't have (running 2.6.24-rc4 with ACPI_PROCFS=no has it's now deprecated). In any case, it shouldn't die like this (and should _not_ kill the panel since it's an external plugin :/) When panel crash, this is the output from console: ** Message: Sensor plugin: screen changed: 0 ** Message: No valid plug window. (xfce4-panel:17371): Gtk-CRITICAL **: gtk_socket_get_id: assertion `GTK_WIDGET_ANCHORED (socket)' failed ** (xfce4-panel:17371): CRITICAL **: An item was unexpectedly removed: "Sensor plugin". (xfce4-panel:17371): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.14.4/gobject/gtype.c:2524: invalid class pointer `0xb78bb0' [1] 17371 segmentation fault xfce4-panel Feel free to ask more information. Cheers, -- Yves-Alexis
well, I do have /proc/acpi/info on my x86_32 system, running debian 2.6.22-2-k7. but changing the above file to an unexisting one does not lead to any crashes. do you have /proc/acpi at all? Can't try it currently, cause I broke something else to play with before being able to check this possibility. so, can you please try ./configure --enable-debug, and send the output to me? feel free to continue by private conversation with me.
I have a /proc/acpi but my kernel is configured with ACPI_PROCFS=no so it may be the problem. I'll try the debug build.
What version of lm_sensors are you running. If you are using 3.0.0 it will cause exactly the behavior you describe. The api/major is changed in 3.0.0 and it is not supported by the sensor-plugin. Charles
lm-sensors is installed and version 3, but xfce4-sensors-plugin is built with libsensors 2 and linked against libsensors 2. If it requires lm-sensors 2 too, it won't be available on Debian as lm-sensors is version 3 in debian.
Then it's definitely not going to work. If it's built against 2 (libsensors.so.3) it will not run with 3 (libsensors.so.4) Charles
libsensors.so.3 (libsensors 2) is installed too. But lm-sensors is the version 3.
Same problem lm_sensors-3.0.0 needs libsensors.so.4 to run and the sensors-plugin can not handle that. You can ether downgrade back to 2 or forget about using the plugin for the time being. Charles
OK guys, you shouldn't have been able to compile the plugin with libsensors4 at all. So, I think you installed libsensors3-dev while having libsensors4, and some runtime stuff uses libsensors 4 wrongly. - I am not able to build the plugin with only libsensors4-dev and libsensors4. Never mind, I am currently investigating in that and hope to come up with real and complete libsensors4 support. What I don't understand: libsensors4 was not automatically installed on my unstable system, so you cannot say that the plugin doesn't go into Debian unstable as long as Debian doesn't fully switch to libsensors4. Then, if you run ./configure --help, you will note 00disable-lmsensors. So the plugin _can_ go with/without libsensors4. "Never shoot too fast.": Discover potential bug, think, read the README, think, read it again, then talk if still necessary.
Well I built against libsensor3-dev, not libsensor4-dev. The thing is, it requires lmsensors and lmsensors is built against libsensor4-dev, so at install time it requires libsensor3 *and* libsensor4. But if building without lmsensor is possible, I'll do that, thanks!
OK, and meanwhile I'll be working on a nice way to offer both interfaces and also on making sure that only the right ones are subject to the rather harsh tone ;)
try subversion.
wooooh, it works \o/ (just tried with r3775 built against libsensors.so.4 and using lmsensors 3.0.0. Thanks!
Close it?
Oups, forgot to close this one.