Bug#494734: adesklets broken because of --enable-debug switch
Package: adesklets
Version: 0.6.1-3
Severity: important
Recently updated adesklets 0.6.1-3 binary builds are broken out of the
box for most normal uses, because they were compiled with special purpose
--enable-debug configure switch. From adesklets_0.6.1-3.diff.gz
(debian/rules):
+./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
+ --prefix=/usr --mandir=\$${prefix}/share/man \
+ --infodir=\$${prefix}/share/info \
+ --without-perl-support --enable-debug \
+ CFLAGS="$(CFLAGS)" || (cat config.log; exit 1)
With this switch on, adesklets generates a lot of debugging lines
interfering with normal operation, unless the ADESKLETS_LOG environment
variable is also set to collect the debug info separately (as warned by
configure).
The consequence is that most users upgrading to version 0.6.1-r3 will see
something like this when invoking the launcher:
$ adesklets
Frontend signature not detected: try to execve it.
(last line is already debug line). Then nothing further will occur,
because the forked desklets will bail out due of the intermixed debug
messages.
Optimal solution is to remove the switch from the build process
altogether; a workaround with the current builds is to set ADESKLETS_LOG
in the environment; something in the line of:
export ADESKLETS_LOG=/tmp/alog
Beware that adesklets used this way will be slower, and that the
/tmp/alog.pid* files might become quite large over time.
--
Sylvain Fourmanoit <syfou@users.sourceforge.net>
P.-S. On a loosely related topic, my thanks to Debian QA team for fixing
bug #489535; I have integrated the changes upstream:
http://repo.or.cz/w/adesklets.git?a=commit;h=7ce08866713cffaee2fb6d21cc95c3af0c0062bc
Reply to: