Hello, I am having a curious bug with my hardware-monitor package, which i don't know how to solve. Upstream does not experience it, so it is debian-specific, or something such.
The problem is that hardware-monitor dies when trying to add/edit devices to be monitored. It dies with the following error (on the command line) : $ /usr/lib/gnome-panel/hardware-monitor flex scanner jammed And well, altough i think this is flex related, it don't seem that flex is part of the hardware-monitor dependencies : Depends: bonobo-activation (>= 1:2.2.4), libart-2.0-2 (>= 2.3.8), libatk1.0-0 (>= 1.2.4), libbonobo-activation4 (>= 1:2.2.4), libbonobo2-0 (>= 2.2.3), libbonobomm1.3-8 (>= 1.3.7-2), libbonoboui2-0 (>= 2.2.4), libbonobouimm1.3-7, libc6 (>= 2.3.2-1), libgcc1 (>= 1:3.3.1-1), libgconf2-4 (>= 2.2.1), libgconfmm2.0-1c102, libglade2-0 (>= 2.0.0), libglademm2.0-1c102, libglib2.0-0 (>= 2.2.3), libgnome2-0 (>= 2.1.90), libgnomecanvas2-0 (>= 2.1.90), libgnomecanvasmm2.0-1c102, libgnomemm1.3-10, libgnomeui-0 (>= 2.1.90), libgnomeuimm1.3-18, libgnomevfs2-0 (>= 2.2.5), libgnomevfs2-common (>= 2.2.5), libgtk2.0-0 (>= 2.2.1), libgtkmm2.0-1c102, libgtop2, liblinc1 (>= 1:1.0.0), liborbit2 (>= 1:2.6.0), liborbit2cpp7, libpanel-applet2-0 (>= 2.0.0), libpango1.0-0 (>= 1.2.1), libsensors-1debian1, libsigc++-1.2-5c102, libstdc++5 (>= 1:3.3.1-1), libxml2 (>= 2.5.9), xlibs (>> 4.1.0), zlib1g (>= 1:1.1.4) Also, running hardware-monitor through gdb doesn't yield anything more than the above message, and no backtrace to be had whatsoever. What is worst, this problem did not appear in 0.7-1, which i compiled some time earlier, but which failed due to a dependency to an older libbonobomm or something such. Please, if anyone has an idea about this one, i would be real happy. If this cannot be solved, i fear hardware-monitor would have to be removed from sarge (i somehow doubt that the sarge 0.5.1-1 still runs, not sure though, as there where some strange libsensor stuff going on). Friendly, Sven Luther
