Bug#501092: sawfish: new upstream version 1.3.4

2008-10-03 Thread Mike Hokenson
Package: sawfish Version: 1:1.3.3-1 Severity: wishlist http://sawfish.wikia.com/wiki/2008_08_29:_Sawfish_1.3.4_released http://sourceforge.net/project/shownotes.php?release_id=622825 Some bug fixes and enhancements. Thanks :) -- System Information: Debian Release: lenny/sid APT prefers uns

Bug#486543: [Pkg-audacious-maintainers] Bug#486543: audacious: Audacious segfaults on start

2008-06-26 Thread Mike Hokenson
On Thursday, June 19, 2008 at 05:50AM, William Pitcock wrote: Please install audacious-dbg and provide another traceroute. Thanks. Also, SIGILL is not a segfault. That may be another bug. I'm also having this problem, but only on at work (Athlon XP 3200+). (gdb) run Starting program: /usr/bin

Bug#375792: ogle-gui: enable gtk2

2006-06-27 Thread Mike Hokenson
Package: ogle-gui Version: 0.9.2-3 Severity: wishlist It'd be nice to see ogle-gui built with gtk2 by default (--enable-gtk2). There doesn't appear to be any ifdef's or special code, just include path and linking library adjustments. Seems to behave the same (no major problems) and looks alot

Bug#368679: mp3gain: incorrect path to README.method in manpage

2006-05-23 Thread Mike Hokenson
Package: mp3gain Version: 1.4.6-2 Severity: minor The path to README.method in the manpage is wrong: See also /usr/share/doc/README.method . Should be: See also /usr/share/doc/mp3gain/README.method . -- System Information: Debian Release: testing/unstable APT prefers unstable APT poli

Bug#344313: cryptsetup: unable to create map with libdevmapper1.02

2005-12-21 Thread Mike Hokenson
Package: cryptsetup Version: 20050111-4+b1 Severity: grave Justification: renders package unusable After last nights upgrade to cryptsetup 20050111-4+b1, I'm unable to map new or existing devices. Only by relinking to libdevmapper1.01 does it work. gozer:/tmp# dd if=/dev/zero of=test bs=1M coun

Bug#324017: Cron daemon dies when a cronjob is about to start

2005-08-20 Thread Mike Hokenson
On Sunday, August 21, 2005 at 03:20AM, Javier Fern?ndez-Sanguino Pe?a wrote: On Sat, Aug 20, 2005 at 07:51:17PM -0500, Mike Hokenson wrote: I'm not sure what your patch looks like, but just testing for a NULL u->scontext didn't work, I had to do this: Aggg.. you are right,

Bug#324017: Cron daemon dies when a cronjob is about to start

2005-08-20 Thread Mike Hokenson
On Sunday, August 21, 2005 at 03:01AM, Javier Fern?ndez-Sanguino Pe?a wrote: #ifdef WITH_SELINUX +u->scontext = NULL; + Hmm.. this might look like is needed too but I would like Russel to confirm it. I don't see a way around it. The only way it can work is if you have selinux suppor

Bug#324017: Cron daemon dies when a cronjob is about to start

2005-08-20 Thread Mike Hokenson
On Sunday, August 21, 2005 at 02:28AM, Javier Fern?ndez-Sanguino Pe?a wrote: On Sat, Aug 20, 2005 at 07:11:43PM -0500, Mike Hokenson wrote: Your assessment looks quite correct. Libselinux does this: void freecon(security_context_t con) { free(con); } So it might be the source of the

Bug#324017: Cron daemon dies when a cronjob is about to start

2005-08-20 Thread Mike Hokenson
On Sunday, August 21, 2005 at 01:57AM, Javier Fern?ndez-Sanguino Pe?a wrote: On Sat, Aug 20, 2005 at 07:28:25PM -0400, Rick Friedman wrote: Oh, and BTW, the only change in -88 that might affect cron's behaviour is either SElinux support or the enabling of pam_limits.so. You might want to review

Bug#324017: Cron daemon dies when a cronjob is about to start

2005-08-20 Thread Mike Hokenson
On Sunday, August 21, 2005 at 12:15AM, Javier Fern?ndez-Sanguino Pe?a wrote: I'm sorry but I can't reproduce this and you're the only one seeing this. I'm pretty sure that if 3.0pl1-88 introduce a bug of this kind I would be flooded with similar bug reports already since it is a base package. C