Package: spamassassin
Version: 3.3.0-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since the recent spamassassin upgrade, I'm starting to get log entries
like this:
> Feb 9 10:41:04 tinkerbell mimedefang-multiplexor[2743]: Slave 2
> stderr: plugin: failed to parse plugin (from
Package: ninja
Version: 0.1.3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On first installation of ninja, it flat-out refuses to create its log
file:
> Starting ninja: log: reading configuration file: /etc/ninja/ninja.conf
> log: ninja version 0.1.3 initializing
> log: magic
Package: grub-pc
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As of the last grub-pc update, this problem seems to have been
resolved (at least as far as I'm concerned: the original submitter may
differ).
Thanks for your work on this.
.Ron
- -- Package-specific info:
**
Package: grub-pc
Version: 1.97~beta3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ah, thanks for clearing that up. Again, sorry for the confusion.
The problem, then, seems to be that grub is going into rescue mode
when it first comes up. On my machines, at least, it looks f
Package: grub-pc
Version: 1.97~beta3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looks like I should file bug reports soon after doing the research,
not several weeks later. The root device is apparently chosen
(incorrectly, IMHO) by a line in /etc/grub.d/00_header:
> prepa
Package: grub-pc
Version: 1.97~beta3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems that, on my system at least (don't know about the original
submitter), grub is going directly into rescue mode. I do not know why
it should do such a thing, although one possibility is t
Package: grub-pc
Version: 1.97~beta3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have three boxes running testing. They all exhibit the same problem,
and have been doing so for a couple of months now.
They're all set up in much the same way:
- - root partition is a primar
Package: shorewall6
Version: 4.2.9-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There's a typo in the example two-interface config file in
/usr/share/doc/shorewall6/examples/two-interfaces/shorewall6.conf
which, when copied to /etc/shorewall6, renders the ipv6 firewall
unuseab
Package: manpages-dev
Version: 3.05-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The basename (3) man page says that there are two different versions
of basename(): the POSIX one and the GNU version. This is
correct. However, it goes on to say that you get the GNU version with
Package: powertweak
Version: 0.99.5-18+b1
Followup-For: Bug #417589
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems I made a minor error in the bounds checking code. I've
attached a patch to apply against the patched dmi.c. Sorry I didn't
find it before you released the update.
This is, o
Mark Brown wrote:
On Sun, Jan 20, 2008 at 02:45:08PM -0500, Ron Murray wrote:
I think the following code should fix it (at least, it protects
against out-of-array-bounds problems):
Thanks.
Could you please resend this patch as a unified diff (ie: 'diff -u orig
new')? patch cannot
Package: powertweak
Version: 0.99.5-18+b1
Followup-For: Bug #417589
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Found powertweak to segfault on my i386 box, caused by bad bounds
checking in src/backends/DMI/dmi.c/dmi_port_type(). My system entered
here with a code of 0xa1 for its floppy: dmi_po
Package: libcdk5
Version: 5.0.20060507-1
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The calendar widget segfaults when you call activateCDKCalendar().
Found the problem to be caused by a classic buffer overflow: in line
462 of calendar.c, the temp[] buffer is init
Package: brasero
Version: 0.6.1-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This appears to be the same problem as bug #441451, which is now
closed. When I try to write a data disc (haven't tried any others), I
get an error message saying that the CD is not writable (sic).
Package: krb5-clients
Version: 1.6.dfsg.1-7
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When running ftp (linked via /etc/alternatives/ftp to
/usr/bin/krb5-ftp):
> $ ftp elsewhere
> ../../../../src/appl/gssftp/ftp/cmds.c: at line 175
> Connected to elsewhere.rjmx.net.
> 220 Pro
Package: hobbit
Version: 4.2.0.dfsg-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package bb (see http://packages.debian.org/lenny/bb) also has a
/usr/share/man/man1/bb.1.gz file. This causes a conflict when you try
to install one of these packages if the other is already insta
Package: libpam-tmpdir
Version: 0.07-1
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I installed libpam-tmpdir on three of my machines. It worked fine on
two of them, but on the third I was unable to log in until I disabled
it. I found that pam-tmpdir-helper was crash
Package: gtk-theme-switch
Followup-For: Bug #229384
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patch for both switch and switch2 attached to fix hash table pointer
problems.
- -- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable
Package: gtk-theme-switch
Followup-For: Bug #229384
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After looking at the switch(1) code further, it seems that my comments
about the 'dirname' variable were not quite correct. The usage of that
variable does work as originally written, although using
Package: gtk-theme-switch
Followup-For: Bug #229384
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not sure whether all of this applies to bug #229384, but some of
it does, so here goes.
switch (i.e. switch for gtk 1.x) wouldn't change themes for me at
all. (Actually, it's more complex than t
Package: installation-reports
Version: 2.17
Severity: normal
-- Package-specific info:
Boot method: CD
Image version: etch beta 3
(http://cdimage.debian.org/cdimage/etch_di_beta3/i386/iso-cd/debian-testing-i386-netinst.iso)
Date: September 17, 2006, some time in the morning
Machine: Compaq Pr
Package: php5
Version: 5.1.4-0.1
Severity: serious
Justification: no longer builds from source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
While trying to build php5_5.1.4-0.1 locally (to track down a segfault
bug, similar to #347642), discovered that the php5 package is currently
unbuildable i
> Perhaps a warning that long filenames don't work well with samba would
^
> be appropriate.
Sorry, that should be "printer names". I probably shouldn't file these
things at 1:30 am.
--
Ron Murray ([EMAIL PROTECTED])
http://ww
Package: cupsys
Version: 1.2.1-2
Severity: wishlist
After upgrading to the latest cupsys package in testing, the CUPS
printer no longer appeared as a samba share (not visible from a
Windows machine nor a Linux box running smbclient).
After spending several hours trying to track the problem down,
Package: gdb
Version: 6.4-1
Severity: important
I'm trying to help track down a problem with sshfs, which is a
threaded program. Here's what happens:
> (gdb) set args -s -d -osshfs_debug bb: ./mnt
> (gdb) r
> Starting program: /home/ron/Debian/sshfs/sshfs-fuse-1.6/sshfs -s -d
> -osshfs_debug bb
Package: sshfs
Version: 1.6-1
Severity: normal
When I try to run sshfs on my Sun Enterprise 250 (2 x 400 MHz
Ultrasparc II processors), I get a bus error:
> [EMAIL PROTECTED]:~/tmp$ mkdir mnt
>
> [EMAIL PROTECTED]:~/tmp$ ll
> total 64
> drwxr-xr-x 3 ron ron 126 May 17 11:42 ./
> drwxr-xr-x 1
Package: util-linux
Version: 2.12r-6
Severity: normal
Since the recent util-linux upgrade, all five of my Debian machines
(running etch) boot up with their clocks five hours slow (i.e. the
difference between my timezone and UTC). All have "UTC=no" in
/etc/default/rcS, but the system clock is not
Package: xserver-xorg
Version: 6.9.0.dfsg.1-4
Severity: normal
X worked fine until I rebooted after running today's etch upgrade,
and now it won't start. The Xorg.0.log gives details, but basically
we get an "INVALID MEM ALLOCATION" warning, and later a message to the
effect that xf86RegisterReso
Package: acidbase
Version: 1.2.1-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When I try to delete alerts from the "5 most frequent alerts" page (by
selecting the checkbox next to the alerts, selecting "delete alerts"
from the dropdown box under "ACTION", and then hitting
Package: acidlab
Version: 0.9.6b20-10.1
Severity: important
If I select one or more alerts from the "5 Most Frequent Alerts"
screen, select "Delete alert(s)" from the "Action" dropdown box, and
then hit the "Selected" button, the alerts are not deleted. Instead, I
get an error message that says
>
Kurt Roeckx wrote:
> On Sat, Nov 12, 2005 at 08:57:17PM +0100, Kurt Roeckx wrote:
>
>>Hi,
>>
>>Can you try the patch available at:
>>http://cvs.openssl.org/chngview?cn=14621
>
>
> Hi Ron,
>
> Can you please give more details about the hardware you're using?
> Upstream seems to think this might
Package: xinetd
Version: 1:2.3.13-3
Severity: wishlist
Tags: patch
Debian turns off entries in inetd.conf by putting "##" at the
beginning of the line. It would be nice if xconv.pl processed those
lines as well, adding a "disable = yes" line to the xinetd.conf entry.
The attached patch does exact
Package: libssl0.9.8
Version: 0.9.8a-2
Severity: normal
After the libssl upgrade to 0.9.8a-2 yesterday, the ssh client
segfaults. Confusingly, it doesn't do it all the time, just most of
the time. Usually, I can get it to work by repeating the command until
it works.
Here's a gdb session, with ba
Package: hplip-base
Version: 0.9.3-3
Severity: normal
When starting hplip:
> ~# /etc/init.d/hplip start
> Starting HP Linux Printing and Imaging System: hpiod, hpssd
my syslog shows:
> Sep 12 19:11:58 rjmx hpiod: 0.9.3 accepting connections at 1031...
> Sep 12 19:12:12 rjmx python: hpssd [ERRO
I don't have access to an alpha box any longer, so I can't test lshw on
one. The current version seems to work ok on powerpc, however. I thhink
we can close this bug.
.....Ron
--
Ron Murray ([EMAIL PROTECTED])
http://www.rjmx.net/~ron
GPG Public Key Fingerprint: F2C1 FC47 5EF7
This bug was fixed several months ago by a new upstream version, I
believe. It should probably be closed.
.Ron
--
Ron Murray ([EMAIL PROTECTED])
http://www.rjmx.net/~ron
GPG Public Key Fingerprint: F2C1 FC47 5EF7 0317 133C D66B 8ADA A3C4
D86C 74DE
--
To UNSUBSCRIBE, email to [EMAIL
Package: xcdroast
Version: 0.98+0alpha15-2rjmx1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With the new xcdroast package compiled with gtk 2, drag and drop (at
least in the Create CD/Write Tracks screen) doesn't work. The only way
I can add tracks to the list is to use the "ad
Christian Perrier wrote:
> tags 199079 unreproducible moreinfo
> retitle 199079 [TO CLOSE] passwd: groupadd/groupdel abort on signal 13
> thanks
>
> Despite my efforts (including installation of nagios and mysql stuff
> which I don't need), I haven't been able to reproduce this bug, which
> is ver
Package: bluez-firmware
Version: 1.0-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When plugging my BT3030 Bluetooth dongle into a USB slot:
> Apr 3 17:33:27 khufu kernel: usb 1-1: new full speed USB device using
> uhci_hcd and address 2
> Apr 3 17:33:28 khufu usb.agent[78
on in the acidlab package?
.Ron
--
Ron Murray ([EMAIL PROTECTED])
http://www.rjmx.net/~ron
GPG Public Key Fingerprint: F2C1 FC47 5EF7 0317 133C D66B 8ADA A3C4
D86C 74DE
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: acidlab
Version: 0.9.6b20-10
Followup-For: Bug #247730
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
acidlab version now in sarge still has this problem, which exists in
three files:
acid_graph_main.php
acid_stat_time.php
acid_state_citems.inc
It looks like there's been a new upstream
101 - 141 of 141 matches
Mail list logo
