Bug#614773: Mssing upgrade path from dhcp3-server-ldap to isc-dhcp-server-ldap

Package: isc-dhcp-server-ldap Version: 4.1.1-P1-15 When upgrading from lenny to squeeze with dhcp3-server-ldap installed, it is not automatically replaced by isc-dhcp-server-ldap because there is no pseudo-package for the upgrade. -- To UNSUBSCRIBE, email to

Bug#537255: gtkrsync incomaptible with rsync 3.0

Package: gtkrsync Version: 1.0.2 gtkrsync does not work correctly with rsync 3.0, i.e. no progress bar is shown. The rsync run itself works, of course, but without the bar gtkrsync is pretty useless. I filed this bug against the ubuntu package some time ago and also tried to contact the upstream

Bug#535964: dhcp3-server-ldap: Looking up dhcpHWAddress fails

Package: dhcp3-server-ldap Version: 3.1.1-6 Severity: normal We are using dhcp3-server-ldap with static leases, i.e. there are host records in LDAP with the 'dhcpHWAddress' attribute like 'dhcpHWAddress: ethernet 00:11:22:33:44:55'. This works as long as dhcp3-server-ldap is configured in

Bug#535964:

Please close this bug - for whatever reason, stopping slapd, running slapindex and starting slapd again helped. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#521434: Postinst script should check for failover config

Package: dhcp3-server Version: 3.1.1-6 Severity: wishlist I upgraded one of two machines in a dhcp failover configuration from etch to lenny today, only to find out that apparently dhcp failover config has changed between ISC dhcpd 3.0 and 3.1. It is not possible to run a mixed 3.0/3.1 failover

Bug#568389: It *is* possible

File change notification is part of the CIFS spec, as can be seen here: http://www.snia.org/tech_activities/CIFS/CIFS-TR-1p00_FINAL.pdf or here: http://msdn.microsoft.com/en-us/library/aa365233%28VS.85%29.aspx All Windows server starting from at least Windows 2000 support it, Samba supports it

Bug#620334: fai-cd: grub-install to USB device fails

Package: fai-server Version: 3.4.7 Severity: normal Tags: upstream patch fai-cd tries to install grub2 to a USB device when told to do so, but fails. This is because the line which find out the device to use obviously got mixed up in the transition from GRUB to GRUB2. I am attaching a patch to

Bug#620798: fai-server: fai-cd provides wrong memtest boot option for grub2

Package: fai-server Version: 3.4.7 Severity: normal Tags: upstream patch The provide_memtest_boot_option in fai-cd inserts a wrong boot option for memtest86 when using grub2. It tries to load /boot/memtest86+ instead of /boot/memtest86+.bin Patch attached -- System Information: Debian Release:

Bug#680049: Old version of ppolicy.schema included

Package: slapd Version: 2.4.23-7.2 Severity: normal The file /etc/ldap/schema/ppolicy.schema included with the package is version 1.2.2.4 2007/01/02, while the version included with the official tarball of openldap-2.4.23 is 1.7.2.5 2010/04/13. Curiously, there is no ppolicy.schema at all in

Bug#639770: apt-move: fails to open fifo-file and hangs

I can reproduce this bug with apt-move 4.2.27-2, here in line 1232. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#740929: fai-setup-storage: setup-storage fails with already existing LVM on target, device

Package: fai-setup-storage Version: 4.1 Severity: normal yesterday I finally started migrating from FAI 3.4.8 and a squeeze nfsroot to FAI 4.1 with a wheezy nfsroot (Server itself is still squeeze for several reasons). I could successfully perform an initial install of a test client (using a

Bug#740504:

Correct me if I got this wrong, but the bug in question is supposed to have existed in upstream until 1.3.4? I built several ISOs of our Ubuntu Privacy Remix live project using upstream xorriso 1.3.0 and 1.3.1 So far I have not seen any UEFI test machine which failed booting from USB drive

Bug#783159: libnss-ldap: postinst script not compatible with unscd

Package: libnss-ldap Version: 264-2.5 Severity: normal Dear Maintainer, I found a bug in the postinst script of libnss-ldap. It looks for an executable named /usr/sbin/nscd and, if found, tries to restart it by invoking 'invoke-rc.d nscd restart'. This is broken when unscd is used instead of the

Bug#784319: [Pkg-nagios-devel] Bug#784319: Segfault when running check_dhcp

Of course, here it is. Everything worked under wheezy with icinga2 and the plugins from wheezy-backports, which I believe were the same version as in jessie. If you need any further information, just let me know. -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (500,

Bug#784319: [Pkg-nagios-devel] Bug#784319: Bug#784319: Segfault when running check_dhcp

I switched from root to 'nagios' with 'su -s /bin/bash nagios', then ran '/usr/lib/nagios/plugins/check_dhcp -v -s 172.16.9.3 -r 172.16.9.254 -i eth1 -m aa:bb:cc:dd:ee:ff' This is the result: --- Requested server address: 172.16.9.3 Hardware address: aa:bb:cc:dd:ee:ff DHCP socket: 3 DHCPDISCOVER

Bug#784319: [Pkg-nagios-devel] Bug#784319: Bug#784319: Segfault when running check_dhcp

FWIW, it worked. Here is the dpatch I created: --- SNIP --- #! /bin/sh /usr/share/dpatch/dpatch-run ## 10_check_dhcp.dpatch by aheinl...@gmx.com ## ## All lines beginning with `## DP:' are a description of the patch. ## DP: No description. @DPATCH@ diff -urNad '--exclude=CVS' '--exclude=.svn'

Bug#784319: Segfault when running check_dhcp

Package: monitoring-plugins-basic Version: 2.1.1-1 Since upgrading to jessie, I get this in my syslog: kernel: check_dhcp[20879]: segfault at 21 ip 2b508d08f21e sp 7ffc9eee20b0 error 4 in libc-2.19.so[2b508cfc1000+19f000] The problem seems to be already tracked and fixed here:

Bug#827817: openjdk-7-jre: .jar files cannot be opened with double-click

Package: openjdk-7-jre Version: 7u101-2.6.6-2~deb8u1 Severity: normal Dear Maintainer, I used to be able to run Java .jar files by double clicking them, which is not possible with debian 8. "OpenJDK runtime" is also not available when choosing "Open With..." There was once a file

Bug#827817: Additional info

I see that there is/was a fix for Ubuntu (LP #1448548) to install the missing .desktop file when "cautious-launcher" is available. This obviously isn't the case for debian.

Bug#790969: Same here...

I came acrosss this bug since it describes exactly my problem - except that I can rule out any hardware fault. My setup is working fine under Ubuntu 12.04 with Kernel 3.13 and LIRC 0.9.0. I installed Debian 8.5 on the same machine on another partition, using the same lircd.conf and getting

Bug#829672: icedove: Cannot open some attachments from the compose window

Package: icedove Version: 1:45.1.0-1~deb8u1 Severity: normal Dear Maintainer, I found this behaviour in icedove: 1. Click "Write" to compose a new message 2. Attach a PDF file 3. Double-Click the attached file (i.e. to verify it's the right one) Expected behaviour: Icedove asks whether to open

Bug#829672: icedove: Cannot open some attachments from the compose window

Am 05.07.2016 um 16:47 schrieb Carsten Schoenert: my setups work as you expected. Please check the settings for Icedove Settings in Menu -> Edit -> Preferences -> Attachments; Incomming -> Content Type 'PDF File' There you have probably 'Save File' selected. I have not, if I had icedove

Bug#790969: [Pkg-lirc-maint] Bug#790969: Same here...

I did as described and could reproduce the bug. Both the debug messages and irrecord claiming it cannot find any toggle mask. What now? Greets, Andreas

Bug#854391: icedove: silently fails to save with invalid characters in file name

Package: icedove Version: 1:45.6.0-1~deb8u1 Severity: normal Dear Maintainer, I noticed that icedove fails silently if one tries to save an e-mail (not attachment!) using Ctrl+S, in cases where the resulting file name contains characters like a colon which are not supported on the destination

Bug#844749: Use overlayfs instead

The kernels from jessie-backports definitely do not contain aufs anymore. IIRC, aufs-dkms did not build against the backport kernels. Aufs was dropped in favour of overlayfs, which should be supported in the current unstable release of live-build.

Bug#854660: [live-build] pass LD_PRELOAD to the chroot stage (to enable e.g. libeatmydata)

Package: live-build Version: 1:20161216 Severity: normal Tags: patch --- Please enter the report below this line. --- The script functions/chroot.sh in live-build cleans the environment before entering the chroot and so also removes LD_PRELOAD from the environment. This prevents the use of

Bug#856482: [live-build] Comments in checksum fails make the check fail

Package: live-build Version: 1:20170213 Severity: normal Tags: patch --- Please enter the report below this line. --- live-build generates a checksum file with seven lines of comments at the start, which explain what this file is for. While this works with "normal" shaXsum utilities, the script

Bug#856482: (no subject)

Probably related to #796474

Bug#842253: nemo-python: Nemo python init failed

Package: nemo-python Version: 3.0.0-2~bpo8+1 Severity: important Dear Maintainer, I have installed nemo-python and copied over one of the example extensions from /usr/share/doc/nemo-python/examples to /usr/share/nemo-python/extensions. Whatever you choose, it does not work. Starting nemo from

Bug#820129: This is not a bug, but a feature

I do not think this should be done, it would make it difficult if not impossible to boot custom kernels. For your own use, you could always build your own signed kernel and add the signing key to the UEFI firmware, or turn off SecureBoot altogether. However, for authors of Debian-based live

Bug#781846: 02.18 works as well

I came across this bug and can confirm that it does not occur with 02.16-1 from wheezy. It does also not occur with 02.18-1, taken from stretch. The package from stretch cannot be installed under jessie right away because of dependency problems, it depends on libstdc++ > 5.2, while jessie

Bug#856537: virtualbox-dkms: virtualbox 5.1.8 module does not build on kernel 4.9.0-0.bpo.1-amd64

On Tue, 7 Mar 2017 11:24:11 + (UTC) Gianfranco Costamagna wrote: > Hi, > > >This bug is closed since a few days, but virtualbox still does not build > > >with the kernel 4.9! > > > >Do you have any idea when the new version will be available in backports > >?

Bug#871780: live-build: support for apt-transport-https

Am 11.08.2017 um 15:06 schrieb Ronny Standtke: > Package: live-build > Version: 1:20170807 > Severity: normal > Tags: patch > > Debian Live currently doesn't support https archives (needed for e.g. the > upstream archives of itch.io or jitsi). > > The attached patch fixes this issue. > > Cheers >

Bug#868853: [virtualbox] Python 3 module does not work

Package: virtualbox Version: 5.1.24-dfsg-1 Severity: normal Tags: patch --- Please enter the report below this line. --- The python module 'vboxapi' does not work with python 3, due to a small error in vboxxpcom.py. The error occurs e.g. when trying to create a new VirtualBoxManager object. I

Bug#869548: [evince] Typo in evince.desktop gives error during update-desktop-database

Package: evince Version: 3.22.1-3+deb9u1 Severity: minor --- Please enter the report below this line. --- The file /usr/share/applications/evince.desktop contains two repeated semicolon at the end: "...application/x-ext-cb7;;application/oxps..." When running 'update-desktop-database', this

Bug#866021: [libpwquality1] New upstream release

Package: libpwquality1 Version: 1.3.0-1+b1 --- Please enter the report below this line. --- The new upstream that dkg pointed to has released a new version 1.4.0 on May 26th. Please update the debian/watch file as well to not miss out such changes. --- System information. --- Architecture:

Bug#867139: [network-manager-gnome] Network Manager does not hide manually configured wired interfaces

Package: network-manager-gnome Version: 1.4.4-1 Severity: normal --- Please enter the report below this line. --- Network manager is supposed to hide any interfaces which were manually configured, but in the version included in stretch, it doesn't. I have an interface eth0 configured in

Bug#866361: live-config: Keyboard configuration in gnome-shell not working

Package: live-config Version: 5.20170316 Severity: normal Tags: l10n Related to but not identical to #854004. Keyboard configuration is still not working in gnome shell 3.22 as expected. The fix for #854004 works on the console and has the effect that we now have two keyboard layouts in gnome

Bug#866218: [isc-dhcp-client] dhclient fails to set hostname

Package: isc-dhcp-client Version: 4.3.5-3 Severity: normal --- Please enter the report below this line. --- This is a follow-up to bug #792854, which is archived and obviously cannot be re-opened. The problem still occurs in stretch, so obviously the fix in #604883 did not work for all

Bug#754431: Still present

I just wanted to join in and add that this bug is still present in stretch (and Ubuntu 17.04, as reported here: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1299747). Keys are generated after a long time, but it is not visible to the user that something is actually happening. This is

Bug#866002: apt-get update fails with missing InRelease file on local mirror

Package: apt For testing and development purposes, I have created an air-gapped machine and use a local mirror on hard disk (created with debmirror) for installation and updates. The mirror is a full mirror of the stretch, stretch-updates and stretch-security archives. That method used to

Bug#865052: Do not choose efi architecture based on installation arch

Package: grub-efi Version: 2.02~beta3-5 Severity: important The meta-package grub-efi depends on either grub-efi-amd64 if installation architecture is amd64, or grub-efi-ia32 if installed on i386. There is no sane reason to do so. GRUB EFI architecture needs to match the architecture of the

Bug#866002: apt-get update fails with missing InRelease file on local mirror

Hello, FWIW, I installed lighttpd on the offline machine, switched to http method and it worked. So it seems there is indeed something wrong with the ftp method. I am attaching the requested information anyway, just in case someone wants to take a look into it. Many thanks again! --

Bug#871780: live-build: support for apt-transport-https

Seems I forgot something. What we are using for our project is --debootstrap-options "--include=apt-transport-https,ca-certificates,openssl" That should work. Andreas signature.asc Description: OpenPGP digital signature

Bug#879105: gosa: Compatibility problems with PHP7

Package: gosa Version: 2.7.4+reloaded2-13 Severity: normal Dear Maintainer, there seem to be compatibility problems with PHP7. After upgrading to Debian 9 yesterday, GoSA web frontend failed with: PHP Fatal error: 'continue' not in the 'loop' or 'switch' context in

Bug#886367: partial fix uploaded

On Thu, 4 Jan 2018 23:18:49 -0200 Henrique de Moraes Holschuh wrote: > Intel has released several updates already, but not all of them AFAIK. > > These microcode updates are of little impact until the kernel changes to > activate the new MSRs are deployed. But they do mess with conditional > jumps

Bug#922251: live-build: support syslinux-efi as (additional) bootloader

Am 14.02.2019 um 17:35 schrieb Thomas Schmitt: > Maybe Steve McIntyre can contribute an anecdote how he came to the > decision in debian-cd to use GRUB2 for EFI and thus to create the need > for two independent boot menu configurations. I am only taking a guess here, but maybe he just took over

Bug#927108: [ftp.debian.org] Release file for jessie-updates is incomplete

Package: ftp.debian.org Severity: normal --- Please enter the report below this line. --- The release for for jessie-updates (debian/dists/jessie-updates/Release), created/modified on 04/15/2019 04:22, only contains entries and checksum for the various Content files, but none for any Packages

Bug#929789: lshw-gtk: Doesn't run under wayland

Package: lshw-gtk Version: 02.18.85-0.1 Severity: important lshw-gtk doesn't run under wayland in the way it is currently implemented. This is because root cannot access the graphical interface under wayland. This is a design choice which affects quite a few applications. There are several

Bug#927848: [system-config-printer] Cannot set default printer as normal user

Package: system-config-printer Version: 1.5.7-3 Severity: normal --- Please enter the report below this line. --- We have a setup where all printers are shared by a central CUPS server. Clients use cups-browsed and DNS-SD to auto-discover them. Until Debian 8, it was possible for users to use

Bug#927849: [gnome-control-center] Cannot set default printer

Package: gnome-control-center Version: 1:3.22.2-3 Severity: normal --- Please enter the report below this line. --- We have a setup where all printers are shared by a central CUPS server. Clients use cups-browsed and DNS-SD to auto-discover them. With this setup, it is not possible to select a

Bug#994529: exfatprogs: Missing symlink from mkexfatfs -> mkfs.exfat

Package: exfatprogs Version: 1.1.0-1 Severity: normal X-Debbugs-Cc: aheinl...@gmx.com The package is missing a symlink which allows to call mkfs.exfat as mkexfatfs. At least the GNOME Disk Utility relies on this symlink, which is present in exfat-utils - it calls mkexfatfs -n when trying to

Bug#1023452: gimp-plugin-registry: Separate+ plugin crashes

Package: gimp-plugin-registry Version: 9.20200927 Severity: normal Tags: upstream X-Debbugs-Cc: aheinl...@gmx.com The separate+ plugin dies with a segfault when trying to run it. (separate:22416): LibGimp-CRITICAL **: 14:10:05.069: gimp_tile_unref: assertion 'tile->ref_count > 0' failed

Bug#1023452: gimp-plugin-registry: Separate+ plugin crashes

It looks like the attached patch seems to work.--- a/separate+/src/separate-core.c +++ b/separate+/src/separate-core.c @@ -431,7 +431,7 @@ for (counter = 0; counter < n_drawables; ++counter) gimp_pixel_rgn_init ([counter], drawables[counter], 0, 0, width, height, TRUE, FALSE); -

Bug#1057033: nemo: Several MIME types not recognized on GVFS mounted volumes

Package: nemo Version: 4.8.6-2 Severity: normal X-Debbugs-Cc: aheinl...@gmx.com Nemo fails to recognize several MIME types, namely *.pgp (application/pgp-encrypted) and *.doc (application/msword) when the files reside on a network drive mounted with GVFS (SMB share on NAS). Instead it shows