Bug#983462: Please update for Node's February security release (CVE-2021-22883, CVE-2021-22884, CVE-2021-23840)

Package: nodejs Version: 12.20.2~dfsg-2 Version 12.21.0 is available which fixes the mentioned CVEs, see https://nodejs.org/en/blog/vulnerability/february-2021-security-releases/

Bug#957957: wmweather+: ftbfs with GCC-10

Should be fixed in version 2.18 that I just uploaded upstream. I also went ahead and removed the auto-dating of the manpage upstream, as I recall that has been a problem for some of my other programs that are packaged in Debian.

Bug#833440: wmweather+: please make the build reproducible

On Thu, Mar 23, 2017 at 08:43:57PM +, Chris Lamb wrote: > > Would you consider applying this patch and uploading? > > Friendly ping on this :) Unless I'm mistaken, I included it upstream in 2.16. There are a few other fixes in 2.16 and 2.17 too.

Bug#740275: fuser acts as if -M is specified if any of -acikmsuvw are

Package: psmisc Version: 22.21-1 Severity: important Tags: patch Expected output: $ src/fuser /tmp/.foo.swp /tmp/.foo.swp:6073 $ src/fuser -v /tmp/.foo.swp USERPID ACCESS COMMAND /tmp/.foo.swp: me 6073 F vi Actual output: $ fuser /t

Bug#739629: slock: Should use PAM for authentication

On Thu, Feb 20, 2014 at 11:12:26PM +0530, Vasudev Kamath wrote: > > > The attached patch adds PAM support to slock in Debian following the > > model of dmenu's xft support or tabbed's meta support. It seems the way > > to apply this would be to quilt pop -a, then apply the patch, then quilt > > pu

Bug#739629: slock: Should use PAM for authentication

Package: suckless-tools Version: 40-1 Tags: patch slock uses the password in /etc/shadow for authentication, which causes problems for setups that use some other mechanism for login (NIS passwords, fingerprint readers, etc) and have no password set in /etc/shadow. It also means that slock can't do

Bug#720433: [php-maint] Bug#720433: libapache2-mod-php5: Segmentation fault in 5.5.2+dfsg-1

On Thu, Aug 22, 2013 at 12:37:55AM +0200, Ondřej Surý wrote: > Pleaye report that to upstream. Quoth http://www.debian.org/Bugs/Reporting: > Don't file bugs upstream > > If you file a bug in Debian, don't send a copy to the upstream > software maintainers yourself, as it is possible that the bug e

Bug#621718: cheese needs to depend on gstreamer0.10-gconf

Package: cheese Version: 2.30.1-2 As of version 0.10.28-3, the gconf plugins have been moved from gstreamer0.10-plugins-good to a separate package, so packages that do not need gconf won't pull it in by using gstreamer. Without installing that package, cheese gives an error message that the gconfa

Bug#593390: wmweather+: Crashes with libcurl 7.21.1

Package: wmweather+ Version: 2.11-4 Tags: fixed-upstream I upgraded to libcurl 7.21.1-1 today, and found that wmweather+ stopped working. It turns out that changes in 7.21.1-1 can cause libcurl to send multiple CURLMSG_DONE messages if the easy_handle is not removed from the multi_handle immediate

Bug#588732: Incorrect udev rules file

Package: trousers Version: 0.3.5-1 Severity: severe Marking "severe" because there is no way this is suitable for release. The udev rules file installed in /lib/udev/rules.d/45-trousers.rules contains the following text: debian/local/45-trousers.rules This is obviously not a valid rules file.

Bug#582980: update completely broke wicd, dhcpcd invocation wrong, nothing works

tags 582980 patch thanks The problem seems to be that the /sbin/dhcpcd script requires all options before the interface. This patch fixes it for me. --- a/wicd/wnettools.py +++ b/wicd/wnettools.py @@ -292,7 +292,7 @@ 'id' : misc.PUMP, }, "dhcpcd" :

Bug#579968: Emulated mice should support a horizontal scroll wheel

tags 579968 + upstream forwarded 579968 qemu-de...@nongnu.org thanks On Mon, May 03, 2010 at 09:14:53PM +0400, Michael Tokarev wrote: > > Please add proper Signed-Off-By line to each of the > patches, and resend the whole lot to qemu-de...@nongnu.org. I have subscribed to that list, thanks for t

Bug#579968: Emulated mice should support a horizontal scroll wheel

Package: qemu-kvm Version: 0.12.3+dfsg-4 Severity: wishlist Tags: patch Where possible, the emulated mice should support a horizontal wheel. The attached patch series does the following: 01: Add parameters for the horizontal wheel delta to the relevant functions and typedefs. The hwheel delta

Bug#578846: USB keyboard emulation key mapping error

Package: qemu-kvm Version: 0.12.3+dfsg-4 The USB keyboard emulation's translation table in hw/usb-hid.c doesn't match the codes actually sent for the Logo (a.k.a. "Windows") or Menu keys. This results in the guest OS not being able to receive these keys at all when the USB keyboard emulation is be

Bug#574697: please test proposed fix

On Sun, Mar 21, 2010 at 04:06:38PM +0100, Michael Biebl wrote: > > Could you all, who experienced this crashes with 1.2.22 in dbus-daemon, try > the > packages from [1] and report back if they fix your problems. I verify 1.2.22-2~test1 does not crash for me, and I also note that 12_syslog_msg_fi

Bug#471565: dbus-daemon segfaults

I am also seeing this bug, with the log message dbus-daemon[2709]: segfault at 100 ip 7f0aca0 8c411 sp 7fffbeec66a0 error 4 in libc-2.10.2.so[7f0aca047000+14a000] On my system, it is 100% reproducable: 1. (Re-)Start the system dbus-daemon 2. (Re-)Start the bluez bluetoothd (/etc/init.

Bug#571438: Does not set up root device on boot

It would help if I didn't forget the transcript... Script started on Thu 25 Feb 2010 08:57:25 AM EST # udevadm info --query=env --path=/devices/virtual/block/dm-0 UDEV_LOG=3 DEVPATH=/devices/virtual/block/dm-0 MAJOR=252 MINOR=0 DEVNAME=dm-0 DEVTYPE=disk SUBSYSTEM=block # udevadm trigger --verbose -

Bug#571438: Does not set up root device on boot

Package: dmsetup Version: 2.02.54-1 The udev rules provided by this package set a number of environment variables on dm devices, which in turn are used by other applications like devicekit-disks. On my system, where / is on an LVM logical volume, these variables do not get set for that device; see

Bug#570581: Trailing garbage in buttons with fribidi 0.19.2-1

Package: libnewt0.52 Version: 0.52.10-5+b1 Illustrative command: whiptail --yesno foo 15 77 This may be a bug in fribidi, it all depends on how fribidi_log2vis is supposed to work. I'm filing it here because it seems to me libnewt0.52 is more likely to be in the wrong. The signature for that fun

Bug#568191: bash-completion: scp floods with network errors, not filenames

To turn it off, edit /etc/bash_completion and comment out or remove the bit about avahi (lines 1302-1315 in the version of the file distributed with 1:1.1-3). And then source /etc/bash_completion to activate the changes in your current session, or just log out and log back in. -- To UNSUBSCRIBE

Bug#569993: closed by m...@linux.it (Marco d'Itri) (Re: Bug#569993: Should document that "udevadm trigger" is probably a bad idea)

On Mon, Feb 15, 2010 at 07:51:01PM +0100, Marco d'Itri wrote: > Why you do not send a patch upstream with better documentation if you > feel strongly about this? I can live with the current one. Isn't forwarding bugs upstream "A big part of your job as Debian maintainer"?[1] But whatever. I guess

Bug#569993: closed by m...@linux.it (Marco d'Itri) (Re: Bug#569993: Should document that "udevadm trigger" is probably a bad idea)

On Mon, Feb 15, 2010 at 01:35:53PM -0500, Brad Jorsch wrote: > On Mon, Feb 15, 2010 at 06:24:06PM +, Debian Bug Tracking System wrote: > > > > On Feb 15, Brad Jorsch wrote: > > > > > When udev rules are updated, a user might want to trigger udev to >

Bug#569993: closed by m...@linux.it (Marco d'Itri) (Re: Bug#569993: Should document that "udevadm trigger" is probably a bad idea)

On Mon, Feb 15, 2010 at 06:24:06PM +, Debian Bug Tracking System wrote: > > On Feb 15, Brad Jorsch wrote: > > > When udev rules are updated, a user might want to trigger udev to > > process those rules. "udevadm trigger" seems to be the tool for the job,

Bug#569993: Should document that "udevadm trigger" is probably a bad idea

Package: udev Version: 150-2 Severity: wishlist When udev rules are updated, a user might want to trigger udev to process those rules. "udevadm trigger" seems to be the tool for the job, but apparently the default --action=add can cause bad things to happen and --action=change is a better idea for

Bug#568169: Acknowledgement (devicekit-disks forgets dm devices on udevadm trigger)

close 568169 thanks Never mind, I just found out that "udevadm trigger" is a bad idea, and the correct "udevadm trigger --action=change" works fine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.o

Bug#532823: wmweather+: Linked with OpenSSL, seems to be a GPL violation

For some reason, possibly my ISP being dainbramaged and periodically blocking forwarding from sourceforge.net because their mailing lists get spammed, I never saw the original bug report. On Thu, Oct 22, 2009 at 02:40:18PM +0200, Patrick Schoenfeld wrote: > Eventually with some knowledge > how to

Bug#503934:

I noticed the same problem a while back when installing 6-10-2; I immediately downgraded to 6-07-4 and put the packages on hold. I haven't had time to try to track down the issue further yet. This may have to do with the bug reported at .

Bug#484789: This looks suspicious

In the soap reply for bug 356853, this snippet looks suspicious: 2007-14 2007-14 And it turns out if I hack /usr/lib/ruby/1.8/http-access2.rb to s/xsd:gYearMonth/xsd:string/g on the response before passing it back up, the package installs. Apparently the BTS's soap

Bug#469514: Is dhcp3-server-ldap really "important"?

Package: dhcp3-server-ldap Version: 3.1.0-4 Severity: minor According to http://www.debian.org/doc/debian-policy/ch-archive.html#s-priorities Important programs, including those which one would expect to find on any Unix-like system. If the expectation is that an experienced Unix person who

Bug#468163: bash-completion: no completion specification

I've seen the same thing just now. The attached patch seems to fix it. --- /etc/bash_completion2008-02-27 10:53:55.0 -0500 +++ /etc/bash_completion2008-02-27 10:53:57.0 -0500 @@ -85,7 +85,7 @@ complete -f -X '!*.@(dvi|DVI)?(.@(gz|Z|bz2))' xdvi complete -f -X '!*.@(

Bug#459214: plans to remove w3c-libwww from the archive

On Fri, Jan 04, 2008 at 05:56:53PM +0100, Martin Stigge wrote: > > It looks reasonable to get rid of libwww. I'll coordinate with upstream > of wmweather+ regarding this issue. > > It could happen that I have to do the port myself (upstream didn't do > anything for years now, but there were also

Bug#445735: image creation fails with a non-modular kernel

merge 445735 433708 tags 445735 patch thanks On Mon, Oct 08, 2007 at 09:00:09AM +0200, maximilian attems wrote: > > bah this is a duplicate bug report. > boring and yes modular kernel are recommended! bah, that was a useless reply. Other people recommend a non-modular kernel, especially if no m

Bug#445735: image creation fails with a non-modular kernel

Package: initramfs-tools Version: 0.91b I compiled a kernel using kernel-package, with CONFIG_MODULES not set since this machine is not going to need to load any modules. When trying to install the generated .deb, I get the following error: Setting up linux-image-2.6.22.9 (3:2.6.22.9.anomie1) ..

Bug#72917: closed by Martin Michlmayr <[EMAIL PROTECTED]> (obsoleted by libwraster3)

Wow that's an old bug. I ended up abandoning the program I was going to use libwraster in and completely forgot about it. Bad news though, it looks like the bug still exists in libwraster3 0.92.0-6.1. The patch still even half-way works (mostly the rejections are in raster.c, it looks like someone

Bug#375286: spamc BSMTP mode is broken in 3.1.3

Package: spamc Version: 3.1.3-1 Severity: important Tags: upstream BSMTP mode is currently broken in spamc, which will cause mail loss for common mail filtering configurations including those posted in several spamc+exim HOWTOs. It does not cause data loss for all users, thus 'important' and not '

Bug#364962: proguard: does not accept command line options properly

Package: proguard Version: 3.4-1 Proguard should be able to accept its options on the command line, but this does not work very well: $ proguard -injars in.jar -outjars out.jar -libraryjars midpapi.jar \ > -overloadaggressively -defaultpackage '' -allowaccessmodification \ > -keep 'public clas