Bug#346459: ifupdown: post-down is not the last thing executed

Package: ifupdown Version: 0.6.7 Severity: normal pre-up commands are the first things executed, before the *-up.d/* scripts. But post-down commands are *not* the last things executed. The *-down.d/* scripts are executed after the post-down commands. This is counterintuitive, and makes it

Bug#324891: openssh-client. strange lines in known_host

Occasionally a host key changes (like when the machine is reinstalled), and users need to be able to remove the corresonding line from known_hosts. Now that the hostnames are hashed, that's difficult. OpenSSH supposedly comes with utilities remove-knownhost and ssh-showkey for dealing with this.

Bug#324891: openssh-client. strange lines in known_host

Colin Watson [EMAIL PROTECTED] wrote: In fact it's easier than it was before hashing was implemented. See the ssh-keygen(1) man page. Thanks! Sorry for the false alarm. AMC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#304718: [EMAIL PROTECTED]: Bug#304718: mutt: exim4 deletes bcc field, so maybe it's time to set write_bcc?]

Julian Gilbey [EMAIL PROTECTED] wrote: It seems that in older versions of mutt, any Bcc header would be passed to the sendmail program, whereas in 1.5.9-2 (and presumably later versions), the write_bcc option is only made use of when saving a message to a mailbox (in mutt_write_rfc822_headers

Bug#385334: ntpd_initres, permission denied error, same here with config file

Norbert Preining [EMAIL PROTECTED] wrote: I have the same here on my Debian/sid box. Restart fixes this problem. I just now saw the same thing with ntp 1:4.2.2.p4+dfsg-1. I have the unmodified /etc/ntp.conf, just like Norbert. /etc/init.d/ntp restart fixed it (for the moment). AMC -- To

Bug#488844: iceweasel: Does not print

iceweasel 2.0 was able to print just fine, but iceweasel 3.0 only offers me the option of printing to a file (which I can then print using lp). Here is the printer entry from /etc/printcap: lp|angrist (HP Color LaserJet 3800dn):\ :lp=:\ :rm=angrist:\ :sd=/var/spool/lpd/angrist:\ :mx#0:\

Bug#494611: iceweasel: 3.0 crashes when tab containing embedded mplayer is closed

Package: iceweasel Version: 3.0.1-1 Severity: normal When a tab or window containing an embedded video being handled by mozilla-mplayer (mplayerplug-in) is closed, firefox crashes. I'm using mozilla-mplayer 1:3.55-0.0 and mplayer 1:1.0.rc2svn20080531-0.1 from debian-multimedia.org. I tried

Bug#436267: stuck at 2.6.21

I'm just a regular Debian user who long ago built my own kernels (for a forgotten reason) and ran into headaches getting out of sync with the official config, so for the past several years I've been using the pre-built Debian kernel images, and generally been happier. But now I have a DV video

Bug#170795: opensp: strange error when parsing an HTML file with onsgmls using stdin

Frederic Schutz [EMAIL PROTECTED] wrote: 1) If I do onsgmls -s test.html, no output, as expected; 2) If I do cat test.html | onsgmls -s, the same; 3) but if I do onsgmls -s test.html, I get: onsgmls:OSFD0:73:16:E: end tag for UL omitted, but its declaration does not permit this

Bug#295649: tk8.4: spinbox widget gets stuck in infinite repeat

Package: tk8.4 Version: 8.4.9-1 Severity: normal The bug is in /usr/lib/tk8.4/spinbox.tcl. It's possible for a spinbox button to get effectively stuck down so that its action gets invoked repeatedly until the application is killed. The B1-Leave event is used to start a repeating chain of

Bug#303827: mawk: printf %x clamps numbers to range of signed int rather than unsigned int

Package: mawk Version: 1.3.3-11 Severity: normal [Sorry if this is a duplicate. I'm not sure whether my first attempt got through.] The printf %x conversion is supposed to treat its argument as an unsigned int (see printf(3)). But look at what mawk does: $ mawk 'END { printf(%x %x\n, 2e9,

Bug#306094: exim4: local part restrictions became inconsistent with comments, changelog is silent

Package: exim4 Version: 4.50-4 Severity: minor Very recently (between 4.50-4 and 4.50-6) the local_parts restrictions in /etc/exim4/conf.d/acl/30_exim4-config_check_rcpt changed, but the comments discussing the restrictions did not change, so the actual restrictions and the explanation are now

Bug#307445: mutt: scrolling functions no longer reveal empty space

Package: mutt Version: 1.5.9-1 Severity: wishlist Until recently the functions current-middle, current-top, and next-line were all capable of revealing empty space below the last message in the index. I have long been in the habit, whenever I finish reading all the new messages, of doing

Bug#307445: mutt: scrolling functions no longer reveal empty space

Marco d'Itri [EMAIL PROTECTED] wrote: Does set menu_move_off (which is in the default /etc/Muttrc) fixes this? Yes! Thanks. In case you're wondering why I didn't inherit menu_move_off from /etc/Muttrc, I think it's because when I started using mutt years ago, /etc/Muttrc included some

Bug#290672: tcl8.4: man page lsearch(3tcl) is unviewable, emacs comment confuses man

Package: tcl8.4 Version: 8.4.9-1 Severity: minor The first line of the lsearch(3tcl) man page (unlike all other 3tcl man pages) begins with a comment intended for emacs: '\ -*- nroff -*- Unfortunately man thinks this is directed at itself, indicating preprocessors to run, and it fails to

Bug#290672: tcl8.4: man page lsearch(3tcl) is unviewable, emacs comment confuses man

Chris Waters [EMAIL PROTECTED] wrote: Hmm, when I try it, I get messages about ignoring unknown preprocessor sent to stderr, but the man page itself displays just fine. That would still, I suppose, qualify as a minor bug, but I'm curious why it works on my system but not yours... On closer

Bug#442946: *.debian.pool.ntp.org do not exist on 4 of 5 pool.ntp.org name servers

Package: ntp Version: 1:4.2.4p3+dfsg-1 Severity: grave Justification: renders package unusable Of the five name servers for pool.ntp.org, four of them claim there is no such host as 1.debian.pool.ntp.org, etc. To investigate this: dig -t ns pool.ntp.org # Shows the name servers to be

Bug#393454: my .gv stopped working

Package: gv Version: 1:3.6.2-3 Followup-For: Bug #393454 I'm not sure when my ~/.gv stopped working, but it's not working now. For example, no matter how I set GV.reverseScrolling (True or False), I get the same scrolling behavior. This used to work. -- System Information: Debian Release: 4.0

Bug#426464: libgphoto2-2: cannot get movie thumbnails on Canon SD700

Package: libgphoto2-2 Version: 2.3.1-3 Severity: normal With version 2.2.1-16 (the stable version) I can get thumbnails for both still images and movies from my Canon PowerShot SD700 IS. With version 2.3.1-3 (the testing version), I can still get the thumbnails for the still images, but for the

Bug#253790: Wondershaper HTB vs CBQ

Vince Mulhollon [EMAIL PROTECTED] wrote: 2) I need to research HTB vs CBQ more... I recently read up on HTB and found that the HTB version of wondershaper 1.1 wasn't really set up right. It was trying to use HTB as a drop-in replacement for CBQ, but there are some fundamental differences. I

Bug#356329: kernel: device names are non-deterministic

Package: kernel Severity: important Whenever I boot my machine, the device names are assigned non-deterministically. There is only one disk (SATA), which is sometimes called /dev/sda and is sometimes called /dev/sdc. There is a built-in USB card-reader that also uses sd* names, but there are

Bug#524796: madwifi-tools: /etc/modprobe.d/madwifi needs to end with .conf

Package: madwifi-tools Version: 1:0.9.4+r3685.20080531+dfsg-1 Severity: normal The configuration file /etc/modprobe.d/madwifi needs to be renamed to end with .conf. module-init-tools is issuing warnings at boot time that a future release will ignore files that don't end with .conf. -- System

Bug#611964: netcat-openbsd: -q -1 does not behave as the man page says

Package: netcat-openbsd Version: 1.89-4 Severity: normal The man page says a negative value for -q means infinity. But the code makes no distinction between negative and zero. The bug was introduced in 1.89-4, and is related to bug #502188. In version 1.89-3, -q behaved as documented

Bug#566639: dash: wait $pid exits before $pid has terminated

Package: dash Version: 0.5.5.1-3 Severity: normal I've discovered a situation in which wait $pid exits before process $pid has terminated. Maybe EINTR is not being handled when calling wait()? Here's a script to reproduce it: #!/bin/sh # # This script illustrates an anomaly when trapping

Bug#566641: bash: wait $pid exits before $pid has terminated

Package: bash Version: 4.1-1 Severity: normal I've discovered a situation in which wait $pid exits before process $pid has terminated. Here's a script to reproduce it: #!/bin/sh # # This script illustrates an anomaly when trapping SIGTSTP and waiting # for a child to exit. When the suspend key

Bug#504955: acpi-support: suspendorhibernate method 'dbus-pm' exits without doing anything

Package: acpi-support Version: 0.109-6 Severity: normal The logic for method 'dbus-pm' in /usr/share/acpi-support/suspendorhibernate looks a little screwy. It runs the command /usr/bin/dbus-send \ --session \ --dest=org.freedesktop.PowerManagement \ --type=method_call \ --print-reply \

Bug#513871: uswsusp: s2both does not resume after battery runs out

Package: uswsusp Version: 0.7-1.2 Severity: normal s2both (invoked via pm-suspend-hybrid) saves a disk image and then puts my ThinkPad T41p to sleep. I can then wake the laptop and it correctly resumes from RAM. Or from the sleep state I can power it off (by holding down the power button), then

Bug#571779: dvi2ps: FATAL-- cannot open fontdesc file bikan-mor2

Package: dvi2ps Version: 4.1j-2 Severity: grave Justification: renders package unusable Whenever I run 'dvi2ps foo' I get the following error message (and nothing else): dvi2ps: FATAL-- cannot open fontdesc file bikan-mor2 This used to work. It happens even for a trivial foo.tex:

Bug#577845: dvi2ps: SIGSEGV every time

Package: dvi2ps Version: 4.1j-3 Severity: important Whenever I run dvi2ps, it immediately crashes, producing this output: ---quote--- @(#)dvi2ps (j-version) 4.1j Prescanning Segmentation fault ---unquote--- and a log message like: kernel: [8971046.561510] dvi2ps[12166]: segfault at 21 ip

Bug#571779: closed by OHURA Makoto oh...@debian.org (Bug#571779: fixed in dvi2ps 4.1j-3)

Source: dvi2ps Source-Version: 4.1j-3 We believe that the bug you reported is fixed in the latest version of dvi2ps, I installed that version, and now instead of getting an error message (dvi2ps: FATAL-- cannot open fontdesc file bikan-mor2) I get a SIGSEGV: kernel: [8930844.284122]

Bug#574658: dpkg: [CONFFILE] purging conffile replaced by symlink removes target, not symlink

I just noticed this behavior too, and I find it astonishing and worrisome. I sometimes manually replace a conf file with a symlink to a file in my own private config directory (example: /etc/foo - /mydir/foo). I always assumed that dpkg remove --purge would remove the conf file /etc/foo and not

Bug#599778: tgif depends on gettext?

Package: tgif Version: 1:4.1.45-3 Severity: normal Does tgif really need to depend on gettext, or would gettext-base be sufficient? gettext pulls in git. AMC -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (600,

Bug#526818: netcat-openbsd: please push -q flag upstream

Package: netcat-openbsd Version: 1.89-3 Severity: wishlist This request applies equally to netcat-openbsd and netcat-traditional. I find the -q flag to be very useful. It's been a Debian-specific extension for years. Please encourage the upstream maintainers to incorporate it. Thanks, AMC --

Bug#509235: iceweasel crashes when libcurl3-gnutls is not installed

Mike Hommey m...@glandium.org wrote: That's not iceweasel requiring curl-gnutls, but something else you installed. I have just experienced the same problem and same workaround. I suspect that the Flash plugin is the culprit. I grep'ed for curl-gnutls in all my extensions and plugins, and

Bug#509018: Upstream bug

Mehdi Tibouchi mehdi.tibou...@normalesup.org wrote: This seems to be the same bug as [#FP-1008] and [#FP-1017] on Adobe's bug tracker: http://bugs.adobe.com/jira/browse/FP-1008 http://bugs.adobe.com/jira/browse/FP-1017 Maybe, or maybe it's the same as Debian bug 509235. People who are

Bug#508107: sox: trim effect on WAV input loses 44 bytes at the end

Package: sox Version: 14.0.1-2+b1 Severity: normal sox foo.wav bar.wav trim start correctly trims the start, but erroneously trims 44 bytes from the end as well. It's probably no coincidence that the WAV header is 44 bytes. -- System Information: Debian Release: lenny/sid APT prefers testing

Bug#545757: gphoto2: in shell mode ls and tab-completion use different sorting

Package: gphoto2 Version: 2.4.5-2 Severity: normal In shell mode, tab-completion lists files in the usual column-major order: 1 4 7 2 5 8 3 6 9 but ls lists files in row-major order (unlike the unix ls command): 1 2 3 4 5 6 7 8 9 ghoto2's ls should be consistent with its tab-completion and

Bug#635679: useradd and groupadd fail if /etc/passwd and /etc/group are symlinks

Nicolas François nicolas.franc...@centraliens.net wrote: How did shadow behave before this change? I think that it could read successfully the files, but then it probably destroyed the links every time a change was committed. I don't remember. I would expect the same behavior from PAM

Bug#644038: olvwm corrupts DISPLAY when running menu commands if DISPLAY has screen number

Package: olvwm Version: 4.4.3.2p1.4-28 Severity: important Tags: patch Dear Maintainer, In bug 635154 I reported the exact opposite bug: olvwm corrupts DISPLAY when running menu commands if DISPLAY *lacks* screen number. Someone else reported the same problem in bug 617236 and provided a

Bug#635154: olvwm corrupts DISPLAY when running menu commands if DISPLAY lacks screen number

Package: olvwm Version: 4.4.3.2p1.4-25 Severity: important If DISPLAY lacks a screen number (for example, :0 rather than :0.0) then olvwm corrupts it when running a command from the popup menu, preventing the command from connecting to the X server. For example, with DISPLAY=:0 olvwm will invoke

Bug#635679: useradd and groupadd fail if /etc/passwd and /etc/group are symlinks

Package: passwd Version: 1:4.1.4.2+svn3283-3 Severity: normal Until revision 3095 in the upstream svn, useradd and groupadd worked just fine if /etc/passwd and /etc/group were symlinks. That revision added the O_NOFOLLOW flag to open() in lib/commonio.c, and now those tools fail to open

Bug#675748: dselect no longer shows package descriptions, /var/lib/dpkg/available no longer contains them

Package: dselect Version: 1.16.3 Severity: normal Dear Maintainer, dselect no longer shows package descriptions for the vast majority of packages, except for a one-line description. Presumably this is because the descriptions are absent from /var/lib/dpkg/available. A Description-md5 field

Bug#676167: SEGV when libsox-fmt-oss is the only installed audio driver

Package: sox Version: 14.4.0-3 Severity: normal Dear Maintainer, Rather than always pass '-t oss' to sox, or set AUDIODRIVER=oss, I thought I'd just uninstall libsox-fmt-alsa and leave libsox-fmt-oss as the only installed audio driver. But this causes sox to SEGV: $ play foo.wav Segmentation

Bug#675748: dselect no longer shows package descriptions, /var/lib/dpkg/available no longer contains them

[Sorry for the duplication, I forgot to reply-all.] Guillem Jover guil...@debian.org wrote: I'm guessing you are not using the apt method? Perhaps the ftp one? I am using the apt method. I don't remember ever configuring the access method in dselect, but I just now checked it, and it's apt.

Bug#676167: Acknowledgement (SEGV when libsox-fmt-oss is the only installed audio driver)

This may be another clue: I reinstalled libsox-fmt-alsa, and with AUDIODRIVER unset, 'play foo.wav' issues a warning (before proceding to play successfully): play WARN alsa: can't encode 0-bit Unknown or not applicable but 'play foo.wav -t alsa' issues no warning. I'm guessing the absence of

Bug#657570: mutt: sender patterns (~e and %e) don't work in IMAP folder

Package: mutt Version: 1.5.20-9 Severity: normal In a newly-opened IMAP folder, the patterns that look at the Sender: header field (~e and %e) don't match any messages. If I read a message that should have matched, then the patterns will match that message (but no others). It looks like the

Bug#657570: mutt: sender patterns (~e and %e) don't work in IMAP folder

C. Meissa carsten.mei...@gmx.de wrote: Does set imap_headers=Sender fix your problem? Yes! Thanks! Maybe Sender: should be added to the default set of headers requested via IMAP. AMC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#694257: fdk-aac: who knows more?

Fabian Greffrath fab...@greffrath.com: Is fdk-aac finally the first *free* high-quality AAC encoder or is it just the next *non-free* one after FAAC? From what I've read, FAAC is not a high-quality AAC encoder. As far as I know, fdk-aac is the only high-quality open-source AAC encoder. I

Bug#732955: exiv2: creates new file in wrong place when old file is a relative symlink

Package: exiv2 Version: 0.23-1 Severity: normal Dear Maintainer, exiv2 version 0.18.2 fixed a bug related to symlinks, but the fix introduced two more bugs. exiv2 is designed to give the illusion of modifying a file in place, but actually it creates the new file, removes the old file, and

Bug#761459: libreadline6: terminfo delays not honored, visible bell nearly invisible

Package: libreadline6 Version: 6.3-8 Severity: normal Tags: upstream Dear Maintainer, When readline tries to flash my terminal (xterm), the flash is either completely invisible or flashes only a fraction of the window (a horizontal stripe) almost too fast to see. My .inputrc has set bell-style

Bug#675748: dselect no longer shows package descriptions, /var/lib/dpkg/available no longer contains them

In two years this bug seems to have gotten no attention from the apt maintainer. Maybe it would help to change the bug description to apt-cache dumpavail omits full description, unlike apt-cache show. Thanks, AMC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a

Bug#769719: nviboot fails to send recovery mail

Package: nvi Version: 1.81.6-11+b1 Severity: important Tags: patch Dear Maintainer, /etc/init.d/nviboot attempts to send mail about recovery from crashed editor sessions, but the attempt fails due to a misplaced quote. This line: (su - nobody -s /bin/sh -c $SENDMAIL

Bug#688814: pdfunite: error-prone command line arguments

[Sorry for the duplicate, the first went to submit@ instead of 688814@.] Eric Cooper wrote: > It is very easy to overwrite a desired input file when doing, i.e., > $ pdfunite page*.pdf > instead of > $ pdfunite page*.pdf new-file.pdf > > Using something like "-o

Bug#852532: olvwm: source code not 64-bit clean, SIGSEGV everywhere

Package: olvwm Version: 4.4.3.2p1.4-28.2 Severity: grave Justification: renders package unusable Dear Maintainer, The latest version (4.4.3.2p1.4-28.2) immediately crashes with SIGSEGV on my x86_64 system. I tried building it from source with debug symbols, and discovered that it is not 64-bit

Bug#852532: Acknowledgement (olvwm: source code not 64-bit clean, SIGSEGV everywhere)

I retract "SIGSEGV everywhere". If I compile client.c with -O0, then the third SIGSEGV is avoided, and I don't see any others. Summary: olvwm runs on my system only if I make all three of these changes, each of which avoids a SIGSEGV: In cursors.c, remove (int) from this line:

Bug#983504: firefox-esr: depends on wrong libnss3 version, TLS hangs with 2:3.58-1

Package: firefox-esr Version: 78.7.0esr-1 Severity: important Dear Maintainer, firefox-esr (both the latest version 78.8.0esr-1 and the latest testing version 78.7.0esr-1) depends on libnss3 (>= 2:3.53.1~), but that is not sufficient. https fails completely with libnss3 2:3.58-1. It works with

Bug#983502: firefox-esr: depends on wrong libnss3 version, TLS hangs with 2:3.58-1

Package: firefox-esr Version: 78.7.0esr-1 Severity: important Dear Maintainer, firefox-esr (both the latest version 78.8.0esr-1 and the latest testing version 78.7.0esr-1) depends on libnss3 (>= 2:3.53.1~), but that is not sufficient. https fails completely with libnss3 2:3.58-1. It works with