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 debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 author directly, but got no repsonse. The Ubuntu MOTU people advised me to report the same bug here. The Ubuntu Bug report is here: https://bugs.launchpad.net/ubuntu/+source/gtkrsync/+bug/297183 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 'static' mode. Looking up the leases dynamically returns no entries when the dhcp-server searches for a specific HW Address. Looking at the slapd logs and by trying out manually, you can see that queries using search filters like ((objectClass=dhcpHost)(dhcpHWAddress=ethernet 00:11:22:33:44:55)) return no results. I tried manually using ldapsearch and confirm that any search for (dhcpHWAddress=ethernet 00:11:22:33:44:55) returns no results. AFAIK, neither spaces nor double colons should be a problem here. So I do not know if this is a slapd problem or one of dhcp3-server-ldap. -- System Information: Debian Release: 5.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages dhcp3-server-ldap depends on: ii debianutils 2.30 Miscellaneous utilities specific t ii dhcp3-common3.1.1-6 common files used by all the dhcp3 ii dhcp3-server3.1.1-6 DHCP server for automatic IP addre ii libc6 2.7-18 GNU C Library: Shared libraries ii libldap-2.4-2 2.4.11-1 OpenLDAP libraries ii libssl0.9.8 0.9.8g-15+lenny1 SSL shared libraries dhcp3-server-ldap recommends no packages. dhcp3-server-ldap suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 configuration, nor is it possible to run a . So I'm now running a single DHCP server at least until Monday, when the other machine will be upgraded. It would be nice if the postinst script of the package checked for a failover config and issued a warning regarding this incompatibility. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 as well. Windows Explorer makes use of this feature and behaves as the bug reporter expected. This is most likely an upstream bug and should be filed there. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 fix the problem. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages fai-server depends on: ii debootstrap 1.0.26+squeeze1 Bootstrap a basic Debian system ii fai-client 3.4.7 Fully Automatic Installation clien Versions of packages fai-server recommends: ii dhcp3-server4.1.1-P1-15+squeeze1 ISC DHCP server (transitional pack ii fai-setup-storage 3.4.7automatically prepare storage devi ii isc-dhcp-server [dh 4.1.1-P1-15+squeeze1 ISC DHCP server for automatic IP a ii libproc-daemon-perl 0.03-2 Run Perl program as a daemon proce ii nfs-kernel-server 1:1.2.2-4support for NFS kernel server ii openbsd-inetd [inet 0.20080125-6 The OpenBSD Internet Superserver ii openssh-client 1:5.5p1-6secure shell (SSH) client, for sec ii openssh-server 1:5.5p1-6secure shell (SSH) server, for sec ii syslinux-common 2:4.02+dfsg-7collection of boot loaders (common ii tftpd-hpa 5.0-18 HPA's tftp server Versions of packages fai-server suggests: ii apt-move 4.2.27-1+b8 Maintain Debian packages in a pack ii aptitude 0.6.3-3.2 terminal-based package manager (te ii debmirror1:2.4.5 Debian partial mirror script, with ii genisoimage 9:1.1.11-1 Creates ISO-9660 CD-ROM filesystem ii grub 0.97-64 GRand Unified Bootloader (dummy pa pn perl-tk none (no description available) -- Configuration Files: /etc/fai/NFSROOT changed [not included] /etc/fai/apt/sources.list changed [not included] /etc/fai/make-fai-nfsroot.conf changed [not included] /etc/fai/menu.lst changed [not included] -- no debconf information --- fai-cd.orig 2011-04-01 09:33:29.0 +0200 +++ fai-cd 2011-04-01 09:34:15.0 +0200 @@ -275,10 +275,10 @@ elif [ $grub_version -eq 2 ]; then # detect device of mounted usb stick, grub2 -device=$(grub-probe -tdrive $usbdir | perl -ane 'm#(/dev/\w+),# print $1\n') +device=$(grub-probe -tdrive $usbdir | perl -ane 'm#(\w+),# print ($1)\n') echo Installing grub2 to $device. # this call seems to remove file and copies them again onto the stick -grub-install --no-floppy --root-directory=$usbdir $device +grub-install --no-floppy --root-directory=$usbdir $device fi } # - - - - - - - - - - - - - - - - - - - - - - - - - -
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: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages fai-server depends on: ii debootstrap 1.0.26+squeeze1 Bootstrap a basic Debian system ii fai-client 3.4.7 Fully Automatic Installation clien Versions of packages fai-server recommends: ii dhcp3-server4.1.1-P1-15+squeeze1 ISC DHCP server (transitional pack ii fai-setup-storage 3.4.7automatically prepare storage devi ii isc-dhcp-server [dh 4.1.1-P1-15+squeeze1 ISC DHCP server for automatic IP a ii libproc-daemon-perl 0.03-2 Run Perl program as a daemon proce ii nfs-kernel-server 1:1.2.2-4support for NFS kernel server ii openbsd-inetd [inet 0.20080125-6 The OpenBSD Internet Superserver ii openssh-client 1:5.5p1-6secure shell (SSH) client, for sec ii openssh-server 1:5.5p1-6secure shell (SSH) server, for sec ii syslinux-common 2:4.02+dfsg-7collection of boot loaders (common ii tftpd-hpa 5.0-18 HPA's tftp server Versions of packages fai-server suggests: ii apt-move 4.2.27-1+b8 Maintain Debian packages in a pack ii aptitude 0.6.3-3.2 terminal-based package manager (te ii debmirror1:2.4.5 Debian partial mirror script, with ii genisoimage 9:1.1.11-1 Creates ISO-9660 CD-ROM filesystem ii grub 0.97-64 GRand Unified Bootloader (dummy pa pn perl-tk none (no description available) -- Configuration Files: /etc/fai/NFSROOT changed [not included] /etc/fai/apt/sources.list changed [not included] /etc/fai/make-fai-nfsroot.conf changed [not included] /etc/fai/menu.lst changed [not included] -- no debconf information --- fai-cd.orig 2011-02-04 16:01:03.0 +0100 +++ fai-cd 2011-04-04 11:10:04.0 +0200 @@ -181,7 +182,7 @@ cat $tmp/boot/grub/grub.cfg EOF menuentry Memory test (memtest86+) { -linux16 /boot/memtest86+ +linux16 /boot/memtest86+.bin } EOF fi
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 the .orig.tar.gz of the debian package. The newer version included several added attributes (PWDCHANGEDTIME, PWDHISTORY, PWDFAILURETIME, PWDGRACEUSETIME) which are needed e.g. by GoSA. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 blank disk), but a second run (i.e. without 'initial' and with the previous partitions and data on disk) gave: ... Creating directory /etc/lvm/backup Creating volume group backup /etc/lvm/backup/vg1 (seqno 5). Use of uninitialized value $lvn in hash element at /usr/share/perl5/LVM.pm line 300. Exiting subroutine via next at /usr/share/perl5/Linux/LVM.pm line 301. Exiting subroutine via next at /usr/share/perl5/Linux/LVM.pm line 301. Exiting subroutine via next at /usr/share/perl5/Linux/LVM.pm line 301. Label not found for next LVINF at /usr/share/perl5/Linux/LVM.pm line 301 Error in task partition. Code: 710 Traceback: task_error task_partition task task_install task task_action task main ... The disk_config used is: disk_config disk1 disklabel:msdos bootable:1 align-at:1 fstabkey:uuid primary /boot 300 ext4rw logical - 1024- - - disk_config lvm vg vg1 disk1.5 vg1-root / 8192-12000 ext4 rw,errors=remount-ro vg1-swap swap 1024-2048 swap rw vg1-tmp /tmp 500-1024ext4 rw,nosuid vg1-varlog /var/log 500-1024 ext4 rw -- System Information: Debian Release: 6.0.9 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages fai-setup-storage depends on: ii liblinux-lvm-perl 0.17-1Perl module to access LVM status i ii libparse-recdescent-pe 1.965001+dfsg-1 Perl module to create and use recu ii parted 2.3-5 The GNU Parted disk partition resi ii perl 5.10.1-17squeeze6 Larry Wall's Practical Extraction Versions of packages fai-setup-storage recommends: ii lvm22.02.66-5The Linux Logical Volume Manager di mdadm 3.1.4-1+8efb9d1+squeeze1 tool to administer Linux MD arrays Versions of packages fai-setup-storage suggests: ii cryptsetup 2:1.1.3-4squeeze2 configures encrypted block devices ii dmsetup2:1.02.48-5 The Linux Kernel Device Mapper use pn dosfstools none(no description available) pn jfsutils none(no description available) pn ntfsprogs none(no description available) pn reiserfsprogs none(no description available) pn xfsprogs none(no description available) -- no debconf information Starting setup-storage 1.5 Using config file: /var/lib/fai/config/disk_config/PRECISE_HOMI Creating directory /run/lock/lvm Finding all volume groups Finding volume group vg1 Creating directory /etc/lvm/archive Archiving volume group vg1 metadata (seqno 6). Creating directory /etc/lvm/backup Creating volume group backup /etc/lvm/backup/vg1 (seqno 6). Use of uninitialized value $lvn in hash element at /usr/share/perl5/Linux/LVM.pm line 300. Exiting subroutine via next at /usr/share/perl5/Linux/LVM.pm line 301. Exiting subroutine via next at /usr/share/perl5/Linux/LVM.pm line 301. Exiting subroutine via next at /usr/share/perl5/Linux/LVM.pm line 301. Label not found for next LVINF at /usr/share/perl5/Linux/LVM.pm line 301. --- Logical volume --- LV Path/dev/vg1/root LV Nameroot VG Namevg1 LV UUIDR1oQ70-3Sjx-Qloe-tpwW-g9fU-gNAT-FwShuM LV Write Accessread/write LV Creation host, time precise-ll, 2014-03-05 15:05:29 +0100 LV Status NOT available LV Size9.31 GiB Current LE 2383 Segments 1 Allocation inherit Read ahead sectors auto --- Logical volume --- LV Path/dev/vg1/swap LV Nameswap VG Namevg1 LV UUIDnVYzYu-myeZ-K3XJ-DE9W-x4Fb-ijxZ-whIxSM LV Write Accessread/write LV Creation host, time precise-ll, 2014-03-05 15:05:33 +0100 LV Status NOT available LV Size1.36 GiB Current LE 347 Segments 1 Allocation inherit Read ahead sectors auto --- Logical volume --- LV Path/dev/vg1/tmp LV Nametmp VG Namevg1 LV UUIDkwNEq0-QOWf-P0rf-3XkE-nPYs-dtkW-73WNJA LV Write Accessread/write LV Creation host, time precise-ll, 2014-03-05 15:05:34 +0100 LV Status NOT available LV Size688.00 MiB
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 prepared with these ISOs. Just to be sure, I will do again with 1.3.6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 'real' nscd. For compatibility reasons, the unscd binary is also named /usr/sbin/nscd, but the init script is /etc/init.d/unscd. So the postinst script fails. Not a big deal, but I thought I'd let you know. -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages libnss-ldap depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38+deb7u8 ii libcomerr2 1.42.5-1.1+deb7u1 ii libgssapi-krb5-2 1.10.1+dfsg-5+deb7u3 ii libkrb5-3 1.10.1+dfsg-5+deb7u3 ii libldap-2.4-2 2.4.31-2 ii libsasl2-2 2.1.25.dfsg1-6+deb7u1 ii multiarch-support 2.13-38+deb7u8 Versions of packages libnss-ldap recommends: ii libpam-ldap 184-8.6 ii unscd [nscd] 0.48-2 libnss-ldap suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages monitoring-plugins-basic depends on: ii iputils-ping 3:20121221-5+b2 ii libc6 2.19-18 ii libssl1.0.01.0.1k-3 ii monitoring-plugins-common 2.1.1-1 ii procps 2:3.3.9-9 ii ucf3.0030 Versions of packages monitoring-plugins-basic recommends: ii libcap2-bin 1:2.24-8 Versions of packages monitoring-plugins-basic suggests: pn icinga | icinga | nagios3 none -- no debconf information -- Command definition: object Service dhcp { import generic-service host_name = localhost check_command = dhcp vars.dhcp_serverip = 172.16.9.3 vars.dhcp_requestedip = 172.16.9.254 vars.dhcp_mac = aa:bb:cc:dd:ee:ff vars.dhcp_interface = eth1 vars.sla = 24x7 } -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 to 255.255.255.255 port 67 DHCPDISCOVER XID: 901953561 (0x35C2B819) DHCDISCOVER ciaddr: 0.0.0.0 DHCDISCOVER yiaddr: 0.0.0.0 DHCDISCOVER siaddr: 0.0.0.0 DHCDISCOVER giaddr: 0.0.0.0 send_dhcp_packet result: 548 recv_result_1: 315 recv_result_2: 315 receive_dhcp_packet() result: 315 receive_dhcp_packet() source: 172.16.9.3 Result=OK DHCPOFFER from IP address 172.16.9.3 via 172.16.9.3 DHCPOFFER XID: 901953561 (0x35C2B819) DHCPOFFER chaddr: AABBCCDDEEFF DHCPOFFER ciaddr: 0.0.0.0 DHCPOFFER yiaddr: 172.16.9.254 DHCPOFFER siaddr: 172.16.9.3 DHCPOFFER giaddr: 0.0.0.0 Option: 53 (0x01) Option: 54 (0x04) Option: 51 (0x04) Option: 1 (0x04) Option: 6 (0x04) Option: 12 (0x0F) Option: 28 (0x04) Option: 42 (0x04) Option: 44 (0x04) Option: 15 (0x0A) Lease Time: 3600 seconds Renewal Time: 0 seconds Rebinding Time: 0 seconds Added offer from server @ 172.16.9.3 of IP address 172.16.9.254 No (more) data received (nfound: 0) Result=ERROR Total responses seen on the wire: 1 Valid responses for this machine: 1 DHCP Server Match: Offerer=172.16.9.3 Requested=172.16.9.3 OK: Received 1 DHCPOFFER(s), 1 of 1 requested servers responded, requested address (172.16.9.254) was offered, max lease time = 3600 sec. --- So it works, though the Result=ERROR thing looks strange. The bug report I linked above claims that this patch fixes it: --- --- plugins-root/check_dhcp.c.orig2014-07-06 17:55:03 UTC +++ plugins-root/check_dhcp.c @@ -323,7 +323,8 @@ int get_hardware_address(int sock,char * #elif defined(__bsd__) /* King 2004see ACKNOWLEDGEMENTS */ -int mib[6], len; +int mib[6]; +size_t len; char*buf; unsigned char *ptr; struct if_msghdr*ifm; @@ -1182,7 +1183,7 @@ int call_getopt(int argc, char **argv){ } } -return i; +return i+1; } --- I will give it a try tomorrow, no time left for today ;-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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' '--exclude=.git' '--exclude=.arch' '--exclude=.hg' '--exclude=_darcs' '--exclude=.bzr' monitoring-plugins-2.1.1~/plugins-root/check_dhcp.c monitoring-plugins-2.1.1/plugins-root/check_dhcp.c --- monitoring-plugins-2.1.1~/plugins-root/check_dhcp.c2014-12-02 04:36:29.0 + +++ monitoring-plugins-2.1.1/plugins-root/check_dhcp.c2015-05-06 12:19:24.772947737 + @@ -323,7 +323,8 @@ #elif defined(__bsd__) /* King 2004see ACKNOWLEDGEMENTS */ -int mib[6], len; +int mib[6]; +size_tlen; char*buf; unsigned char *ptr; struct if_msghdr*ifm; @@ -1182,7 +1183,7 @@ } } -return i; +return i+1; } --- SNIP --- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198318 Note that I can confirm this is not reproducible when running check_dhcp from the command line. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
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 /usr/share/applications/openjdk-7-java.desktop, which is not included in the package anymore. There are files in /usr/share/application- registry (obsolete, AFAIK) and /usr/share/mime-info, but these alone obviously don't work. Google turns up several results on that matter, many of them ending up with either re-creating openjdk-7-java.desktop or manually associating .jar files with "java -jar...", but IMHO this should work out of the box. -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openjdk-7-jre depends on: ii libasound21.0.28-1 ii libatk-wrapper-java-jni 0.30.5-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-18+deb8u4 ii libcairo2 1.14.0-2.1+deb8u1 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-3+deb8u1 ii libgdk-pixbuf2.0-02.31.1-2+deb8u5 ii libgif4 4.1.6-11+deb8u1 ii libgl1-mesa-glx [libgl1] 11.1.3-1~bpo8+1 ii libglib2.0-0 2.48.0-1~bpo8+1 ii libgtk2.0-0 2.24.25-3+deb8u1 ii libjpeg62-turbo 1:1.3.1-12 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpng12-01.2.50-2+deb8u2 ii libx11-6 2:1.6.2-3 ii libxcomposite11:0.4.4-1 ii libxext6 2:1.3.3-1 ii libxi62:1.7.4-1+b2 ii libxinerama1 2:1.1.3-1+b1 ii libxrandr22:1.4.2-1+b1 ii libxrender1 1:0.9.8-1+b1 ii libxtst6 2:1.2.2-1+b1 ii openjdk-7-jre-headless7u101-2.6.6-2~deb8u1 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages openjdk-7-jre recommends: ii fonts-dejavu-extra 2.34-1 ii libgconf2-4 3.2.6-3 ii libgnome2-0 2.32.1-5 ii libgnomevfs2-0 1:2.24.4-6+b1 Versions of packages openjdk-7-jre suggests: pn icedtea-7-plugin -- no debconf information
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 exactly the problems that are describe above. I am using kernel 4.6 from jessie-backports. I too have a One4All remote, namely URC-6440. I would be glad to help solve this problem, as it is a real show-stopper.
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 or save the file, and when clicking "open", the attachment opens with the associated application Real behaviour: Icedove asks whether to open or save the file, and when clicking "open", nothing happens Until now, I can only reproduce that with PDF files, but not with plain text, OpenDocument, JPEG - these behave as expected. Opening PDF attachments from *received* messages (or messages in the "Sent" folder) works as expected. Occurs with several different accounts. Since I regularly double-check attached files before sending, I am pretty sure this worked in earlier versions. Might be an upstream bug since it occurs in thunderbird for Ubuntu as well. I tried running icedove from the console but got no helpful output. Tried in safe mode, does not change anything. -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages icedove depends on: ii debianutils 4.4+b1 ii fontconfig2.11.0-6.3 ii libasound21.0.28-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-18+deb8u4 ii libcairo2 1.14.0-2.1+deb8u1 ii libdbus-1-3 1.8.20-0+deb8u1 ii libdbus-glib-1-2 0.102-1 ii libevent-2.0-52.0.21-stable-2 ii libffi6 3.1-2+b2 ii libfontconfig12.11.0-6.3 ii libfreetype6 2.5.2-3+deb8u1 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-02.31.1-2+deb8u5 ii libglib2.0-0 2.48.0-1~bpo8+1 ii libgtk2.0-0 2.24.25-3+deb8u1 ii libhunspell-1.3-0 1.3.3-3 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpixman-1-0 0.32.6-3 ii libstartup-notification0 0.12-4 ii libstdc++64.9.2-10 ii libx11-6 2:1.6.2-3 ii libxcomposite11:0.4.4-1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes31:5.0.1-2+b2 ii libxrender1 1:0.9.8-1+b1 ii libxt61:1.1.4-1+b1 ii psmisc22.21-2 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages icedove recommends: pn iceowl-extension ii myspell-de-de [myspell-dictionary] 20131206-5 Versions of packages icedove suggests: pn fonts-lyx ii libgssapi-krb5-2 1.12.1+dfsg-19+deb8u2 -- no debconf information
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 wouldn't ask... I took a look at these settings and actually found two associations for PDF files. One is labeled "application/pdf: .pdf", the other "application/force-download: .pdf". Both were initially set to "Always ask". I found out that "application/pdf" is applied to all *received* mails with PDF attachments, whereas "application/force-download" is used when *writing* a message. If I change "application/force-download" from the default to e.g. "evince", then it works as expected. This is not unusual since "application/force-download" is not meant to be opened with any application. The question is, why is icedove/thunderbird using the MIME type application/force-download in this case?
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 file system. This is often the case if you try to save a mail containing "Re:" in the subject. Steps to reproduce: - Open any mail containing 'Re:' in the subject - Press Ctrl+S - Choose any VFAT formatted file system (e.g. USB drive) as destination - Do not change the proposed file name - Click save Expected result: - File is saved or icedove complains about invalid file name Actual result: - File is not saved, no message from icedove -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages icedove depends on: ii debianutils 4.4+b1 ii fontconfig2.11.0-6.3+deb8u1 ii libasound21.0.28-1 ii libatk1.0-0 2.14.0-1 ii libc6 2.19-18+deb8u7 ii libcairo2 1.14.0-2.1+deb8u2 ii libdbus-1-3 1.8.22-0+deb8u1 ii libdbus-glib-1-2 0.102-1 ii libevent-2.0-52.0.21-stable-2 ii libffi6 3.1-2+b2 ii libfontconfig12.11.0-6.3+deb8u1 ii libfreetype6 2.5.2-3+deb8u1 ii libgcc1 1:4.9.2-10 ii libgdk-pixbuf2.0-02.31.1-2+deb8u5 ii libglib2.0-0 2.48.0-1~bpo8+1 ii libgtk2.0-0 2.24.25-3+deb8u1 ii libhunspell-1.3-0 1.3.3-3 ii libpango-1.0-01.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-0 1.36.8-3 ii libpixman-1-0 0.32.6-3 ii libstartup-notification0 0.12-4 ii libstdc++64.9.2-10 ii libx11-6 2:1.6.2-3 ii libxcomposite11:0.4.4-1 ii libxdamage1 1:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes31:5.0.1-2+b2 ii libxrender1 1:0.9.8-1+b1 ii libxt61:1.1.4-1+b1 ii psmisc22.21-2 ii zlib1g1:1.2.8.dfsg-2+b1 Versions of packages icedove recommends: pn iceowl-extension ii myspell-de-de [myspell-dictionary] 20131206-5 Versions of packages icedove suggests: pn fonts-lyx ii libgssapi-krb5-2 1.12.1+dfsg-19+deb8u2
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 eatmydata to speed up the build process. This can either be fixed by giving a value for LD_PRELOAD in config/environment.chroot or by changing chroot.sh to pass LD_PRELOAD along. I suggest doing the latter since this is a quite common request. Patch is attached. --- chroot.sh.orig2017-02-09 08:24:52.995385684 +0100 +++ chroot.sh2017-02-09 08:25:48.623280273 +0100 @@ -26,7 +26,7 @@ fi done -${_LINUX32} chroot "${CHROOT}" /usr/bin/env -i HOME="/root" PATH="/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin" TERM="${TERM}" DEBIAN_FRONTEND="${LB_DEBCONF_FRONTEND}" DEBIAN_PRIORITY="${LB_DEBCONF_PRIORITY}" DEBCONF_NONINTERACTIVE_SEEN="true" DEBCONF_NOWARNINGS="true" ${ENV} ${COMMANDS} +${_LINUX32} chroot "${CHROOT}" /usr/bin/env -i LD_PRELOAD=${LD_PRELOAD} HOME="/root" PATH="/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin" TERM="${TERM}" DEBIAN_FRONTEND="${LB_DEBCONF_FRONTEND}" DEBIAN_PRIORITY="${LB_DEBCONF_PRIORITY}" DEBCONF_NONINTERACTIVE_SEEN="true" DEBCONF_NOWARNINGS="true" ${ENV} ${COMMANDS} return "${?}" } --- System information. --- Architecture: amd64 Kernel: Linux 4.8.0-0.bpo.2-amd64 Debian Release: 8.7 500 stable-updates ftp.de.debian.org 500 stable security.debian.org 500 stable ftp.gruen.hm.mlpd.de 500 stable ftp.de.debian.org 500 jessie-local ftp.gruen.hm.mlpd.de 200 jessie-backports mozilla.debian.net 200 jessie-backports ftp.de.debian.org --- Package information. --- Depends (Version) | Installed ==-+-=== debootstrap | 1.0.86~bpo8+1 Recommends (Version) | Installed ===-+-=== apt-utils | 1.0.9.8.4 cpio | 2.11+dfsg-4.1+deb8u1 live-boot-doc | 1:20160511~bpo8+1 live-config-doc | 4.0.4-1 live-manual-html | 1:4.0.1-1 OR live-manual | wget | 1.16-1+deb8u1 Suggests (Version) | Installed =-+-=== debian-keyring | 2015.04.10 gpgv | 1.4.18-7+deb8u3
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 used to check the checksums in live-boot (when booted with the 'verify-checksums' parameter) uses a busybox implementation of shaXsum which obviously cannot deal with comments and always complains about 7 failures. Removing the comment from the checksum file solves the problem. --- System information. --- Architecture: amd64 Kernel: Linux 4.9.0-0.bpo.1-amd64 --- Package information. --- Depends (Version) | Installed ==-+-=== debootstrap | 1.0.86~bpo8+1 Recommends (Version) | Installed ===-+-=== apt-utils | 1.0.9.8.4 cpio | 2.11+dfsg-4.1+deb8u1 live-boot-doc | 1:20160511~bpo8+1 live-config-doc | 4.0.4-1 live-manual-html | 1:4.0.1-1 OR live-manual | wget | 1.16-1+deb8u1 Suggests (Version) | Installed =-+-=== debian-keyring | 2015.04.10 gpgv | 1.4.18-7+deb8u3 --- a/scripts/build/binary_checksums 2017-03-01 14:35:49.270545671 +0100 +++ b/scripts/build/binary_checksums 2017-03-01 14:36:36.271418980 +0100 @@ -71,16 +71,6 @@ \! -path './*sum.txt' \ -print0 | sort -z | xargs -0 ${CHECKSUM}sum > ../${CHECKSUMS} -cat > ${CHECKSUMS} << EOF -## This file contains the list of ${CHECKSUM} checksums of all files on this -## medium. -## -## You can verify them automatically with the 'verify-checksums' boot parameter, -## or, manually with: '${CHECKSUM}sum -c ${CHECKSUMS}'. -## -## -EOF - cat ../${CHECKSUMS} >> ${CHECKSUMS} rm -f ../${CHECKSUMS}
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 the commandline gives: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/gi/module.py", line 320, in __getattr__ return getattr(self._introspection_module, name) File "/usr/lib/python2.7/dist-packages/gi/module.py", line 139, in __getattr__ self.__name__, name)) AttributeError: 'gi.repository.Nemo' object has no attribute 'NameAndDescProvider' (nemo:16310): Nemo-Python-WARNING **: nemo_python_init_python failed My own extensions - which used to work until at least two weeks ago - also stopped working. I suspect that this is not really the fault of nemo-python, since it hasn't been updated over the last months, but something in the gi-repository introspection mechanism. I'm filing the bug here since I know no better place. -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nemo-python depends on: ii gir1.2-nemo-3.0 2.2.4-2 ii libatk1.0-0 2.14.0-1 ii libc62.19-18+deb8u6 ii libcairo-gobject21.14.0-2.1+deb8u1 ii libcairo21.14.0-2.1+deb8u1 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u5 ii libglib2.0-0 2.48.0-1~bpo8+1 ii libgtk-3-0 3.14.5-1+deb8u1 ii libnemo-extension1 3.0.3-1~bpo8+1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpython2.7 2.7.9-2+deb8u1 nemo-python recommends no packages. nemo-python suggests no packages. -- no debconf information
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 systems like I am (www.discreete-linux.org), we need a way that will boot the live system on as many computers and platforms as possible without user interaction, including those users which regulary use only windows, and including platforms like Intel-based Tablets/Detachables which often do not allow to turn off Secureboot. Our live system requires a special kernel to work, it cannot work with any generic kernel/initrd signed by Debian. UEFI/SecureBoot specs do not require to keep the chain of signatures through to the kernel/initrd, it is optional. There should at least be a choice by providing two packages, one which allows booting unsigned kernels and one which doesn't. Or we can find a way for projects to get their kernels and/or own grub signed by Debian. signature.asc Description: OpenPGP digital signature
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 has libstdc++ 4.92. The package does, however, build and install cleanly from source when built under jessie. It then depends on libstdc++ > 4.9 instead. So i guess 02.18 could be included in jessie-backports easily.
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 Costamagnawrote: > 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 > >? If it's quick, I will wait for it, otherwise, I will recompile the > >virtualbox package with the new version. > > > never, because of backports policy. > Could you explain this a little? Also, I see you had created a version 5.1.8-dfsg-7 a while ago which also should fix that problem, at least it says so in the changelog. Could this be backported? Thanks, Andreas
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 > > Ronny > Hello, I appreciate your work, but I think your approach is too complex. This issue can be solved by supplying '--debootstrap-options "--include=apt-transport-https"' to lb config on the command line or in auto/config. If you want that to be the default, I am sure this can be set somewhere in the source, but I wouldn't include that in an "official" release. Including apt-transport-https in the bootstrap stage ensures that it does not fail because of https-repositories. Debootstrap uses only the main repository, which is non-https by default. This eliminates the need to patch the sources.list files. Bye, Andreas signature.asc Description: OpenPGP digital signature
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 have attached a patch that fixes the problem. Bug is tracked upstream at https://www.virtualbox.org/ticket/16899 --- System information. --- Architecture: Kernel: Linux 4.9.0-3-amd64 Debian Release: 9.0 900 stable ftp.de.debian.org 100 stretch-backports ftp.de.debian.org --- Package information. --- Depends (Version) | Installed ===-+- adduser | 3.115 iproute2 | 4.9.0-1 procps | 2:3.3.12-3 virtualbox-dkms (>= 5.1.24-dfsg-1) | 5.1.24-dfsg-1 OR virtualbox-source (>= 5.1.24-dfsg-1) | OR virtualbox-modules | init-system-helpers (>= 1.18~) | 1.48 python3 (<< 3.6) | 3.5.3-1 python3 (>= 3.5~) | 3.5.3-1 python3.5 | 3.5.3-1 python3:any (>= 3.3.2-2~) | libc6 (>= 2.15) | 2.24-11+deb9u1 libcurl3-gnutls (>= 7.16.2) | 7.52.1-5 libdevmapper1.02.1 (>= 2:1.02.97) | 2:1.02.137-2 libgcc1 (>= 1:3.0) | 1:6.3.0-18 libgsoap10 | 2.8.35-4 libpng16-16 (>= 1.6.2-1) | 1.6.28-1 libpython3.5 (>= 3.5.0~b1) | 3.5.3-1 libsdl1.2debian (>= 1.2.11) | 1.2.15+dfsg1-4 libssl1.1 (>= 1.1.0) | 1.1.0f-3 libstdc++6 (>= 5.2) | 6.3.0-18 libvncserver1 (>= 0.9.10) | 0.9.11+dfsg-1 libvpx4 (>= 1.6.0) | 1.6.1-3 libx11-6 | 2:1.6.4-3 libxcursor1 (>> 1.1.2) | 1:1.1.14-1+b4 libxext6 | 2:1.3.3-1+b2 libxml2 (>= 2.7.4) | 2.9.4+dfsg1-2.2 libxmu6 | 2:1.1.2-2 libxt6 | 1:1.1.5-1 zlib1g (>= 1:1.1.4) | 1:1.2.8.dfsg-5 Recommends (Version) | Installed =-+-== virtualbox-qt (= 5.1.24-dfsg-1) | 5.1.24-dfsg-1 libgl1-mesa-glx | 13.0.6-1+b2 OR libgl1 | libqt5core5a (>= 5.7.0) | 5.7.1+dfsg-3+b1 libqt5opengl5 (>= 5.0.2) | 5.7.1+dfsg-3+b1 libqt5widgets5 (>= 5.0.2) | 5.7.1+dfsg-3+b1 Suggests (Version) | Installed =-+-=== vde2 | virtualbox-guest-additions-iso | Index: bindings/xpcom/python/xpcom/vboxxpcom.py === --- bindings/xpcom/python/xpcom/vboxxpcom.py 2016-09-12 17:32:29.0 +0200 +++ /usr/lib/virtualbox/sdk/bindings/xpcom/python/xpcom/vboxxpcom.py 2017-07-13 12:11:50.309907961 +0200 @@ -39,7 +39,7 @@ if sys.hexversion >= 0x030200f0 and sys.abiflags: _asNew = [] for sCandidate in _asVBoxPythons: -if isdigit(sCandidate[-1:]): +if sCandidate[-1:].isdigit(): _asNew.append(sCandidate + sys.abiflags) else: _asNew.append(sCandidate) signature.asc Description: OpenPGP digital signature
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 gives "Error in file "/usr/share/applications/evince.desktop": "" is an invalid MIME type ("" does not contain a subtype)" --- System information. --- Architecture: Kernel: Linux 4.9.0-3-amd64 Debian Release: 9.1 900 stable ftp.de.debian.org 100 stretch-backports ftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+- evince-common (<< 3.23) | 3.22.1-3+deb9u1 evince-common (>= 3.22) | 3.22.1-3+deb9u1 gsettings-desktop-schemas | 3.22.0-1 libevdocument3-4 (= 3.22.1-3+deb9u1) | 3.22.1-3+deb9u1 libevview3-3 (= 3.22.1-3+deb9u1) | 3.22.1-3+deb9u1 shared-mime-info | 1.8-1 dconf-gsettings-backend | 0.26.0-2+b1 OR gsettings-backend | libatk1.0-0 (>= 1.12.4) | 2.22.0-1 libc6 (>= 2.4) | 2.24-11+deb9u1 libcairo-gobject2 (>= 1.10.0) | 1.14.8-1 libcairo2 (>= 1.14.0) | 1.14.8-1 libgdk-pixbuf2.0-0 (>= 2.22.0) | 2.36.5-2 libglib2.0-0 (>= 2.41.2) | 2.50.3-2 libgnome-desktop-3-12 (>= 3.17.92) | 3.22.2-1 libgtk-3-0 (>= 3.19.12) | 3.22.11-1 libnautilus-extension1a (>= 3.21.92-3~) | 3.22.3-1 libpango-1.0-0 (>= 1.20.0) | 1.40.5-1 libsecret-1-0 (>= 0.7) | 0.18.5-3.1 Recommends (Version) | Installed ===-+-=== default-dbus-session-bus | OR dbus-session-bus | Suggests (Version) | Installed ==-+-=== gvfs | 1.30.4-1 nautilus-sendto | 3.8.4-2+b1 poppler-data | 0.4.7-8 unrar | signature.asc Description: OpenPGP digital signature
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: Kernel: Linux 4.9.0-3-amd64 Debian Release: 9.1 900 stable ftp.de.debian.org 100 stretch-backports ftp.de.debian.org --- Package information. --- Depends (Version) | Installed ===-+- libc6 (>= 2.14) | 2.24-11+deb9u1 libcrack2 (>= 2.8.12) | 2.9.2-5 libpwquality-common | 1.3.0-1 Package's Recommends field is empty. Package's Suggests field is empty. signature.asc Description: OpenPGP digital signature
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 /etc/network/interfaces, but in the status menu of gnome shell it reads "Wired, not connected" even though it is connected and working. Clicking on "Connect" apparently does nothing. In the network settings, the wired interface does *not* show up (which is the expected behaviour). I am pretty sure this was not the case in jessie. --- System information. --- Architecture: Kernel: Linux 4.9.0-3-amd64 Debian Release: 9.0 900 stable ftp.de.debian.org 100 stretch-backports ftp.de.debian.org --- Package information. --- Depends (Version) | Installed =-+-= libatk1.0-0 (>= 1.12.4) | 2.22.0-1 libc6 (>= 2.4) | 2.24-11+deb9u1 libcairo2 (>= 1.2.4) | 1.14.8-1 libgdk-pixbuf2.0-0 (>= 2.22.0) | 2.36.5-2 libglib2.0-0 (>= 2.41.1) | 2.50.3-2 libgtk-3-0 (>= 3.4) | 3.22.11-1 libjansson4 (>= 2.0.1) | 2.9-1 libmm-glib0 (>= 0.7.991) | 1.6.4-1 libnm0 (>= 1.5.90) | 1.6.2-3 libnma0 (= 1.4.4-1) | 1.4.4-1 libnotify4 (>= 0.7.0) | 0.7.7-2 libpango-1.0-0 (>= 1.14.0) | 1.40.5-1 libpangocairo-1.0-0 (>= 1.14.0) | 1.40.5-1 libsecret-1-0 (>= 0.7) | 0.18.5-3.1 dconf-gsettings-backend | 0.26.0-2+b1 OR gsettings-backend | network-manager (>= 1.6) | 1.6.2-3 policykit-1-gnome | 0.105-6 OR polkit-1-auth-agent | default-dbus-session-bus | OR dbus-session-bus | Recommends (Version) | Installed =-+-=== notification-daemon | 3.20.0-1+b1 gnome-keyring | 3.20.0-3 mobile-broadband-provider-info | 20161204-1 iso-codes | 3.75-1 Suggests (Version) | Installed -+-=== network-manager-openconnect-gnome | network-manager-openvpn-gnome | network-manager-vpnc-gnome | network-manager-pptp-gnome | signature.asc Description: OpenPGP digital signature
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 shell, English and the configured layout, with English being the default. The fact that we have two layouts seems to be due to some change in gnome-shell and/or gdm - a fresh install of Debian stretch shows the same behaviour, except that the configured keyboard is selected as the default. I don't know what would be the "right" way to fix this. We could hard-wire the dconf setting org/gnome/desktop/input-sources, but that does not look right. I found a maybe related report in Mageia Linux here: https://bugs.mageia.org/show_bug.cgi?id=14476 It suggests that a) Gnome Shell/GDM now ignores several env vars like GDM_LANG, which is set in Debian b) accounts-daemon needs to be restarted after setting up the system-wide locale and keyboard layout I will try to dig further into this, but maybe someone else has an idea. Andreas signature.asc Description: OpenPGP digital signature
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 cases. The problem is that dhclient is supposed to set the hostname if it is told to request the hostname in dhclient.conf, but doesn't. The output of 'hostname' is 'localhost.localdomain' instead. --- System information. --- Architecture: Kernel: Linux 4.9.0-3-amd64 Debian Release: 9.0 900 stable ftp.de.debian.org 100 stretch-backports ftp.de.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== libc6 (>= 2.15) | 2.24-11+deb9u1 libdns-export162 | 1:9.10.3.dfsg.P4-12.3 libisc-export160 | 1:9.10.3.dfsg.P4-12.3 debianutils (>= 2.8.2) | 4.8.1.1 iproute2 | 4.9.0-1 Recommends (Version) | Installed ==-+-=== isc-dhcp-common | 4.3.5-3 Suggests (Version) | Installed ===-+-=== resolvconf | avahi-autoipd | isc-dhcp-client-ddns |
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 very annoying and confusing. I guess this is an upstream bug, please forward. Thanks! signature.asc Description: OpenPGP digital signature
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 work fine with jessie, but fails since I upgraded to stretch. When I run apt-get update on the air-gapped machine, it always complains about a missing InRelease file in the main stretch archive. Indeed there is no InRelease on the official mirrors, only Release and Release.gpg. The Debian FTP masters told me that this was "on purpose", whatever that might be. I thought that apt was supposed to try Release.gpg instead if InRelease is missing, but it doesn't. Turning on "Debug::Acquire::FTP=true" on the internet connected machine using the official mirrors shows that it works there; but the air-gapped machine doesn't even try to download Release.gpg but immediately fails. I don't know if that has anything to do with the local mirror at all, or if something got screwed during the update, however I have no idea where to look. Thanks, Andreas
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 EFI firmware, not necessarily that of the installed OS. A 32bit EFI can boot a 64bit OS just fine, and vice versa. There are in fact numerous intel based tablets and convertibles out there which for whatever reason use a 32bit EFI firmware even though their Atom CPU is 64bit capable and runs Debian amd64 just fine. I have one here at hand. So either need to determine EFI architecture at install time and then pull in the correct package (hard way), or correct the dependencies and depend on *both* grub-efi-amd64 and grub-efi-ia32, regardless of installation architecture (easy way). I did the latter for tests on our machines and found no problems so far with both of them co-existing. signature.asc Description: OpenPGP digital signature
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! -- Output from apt-get update: <- '-%20Welcome%20to%20Pure-FTPd%20[privsep]%20[TLS]%20--%0d%0aYou%20are%20user%20number%201%20of%2050%20allowed.%0d%0aLocal%20time%20is%20now%2014:02.%20Server%20port:%2021.%0d%0aIPv6%20connections%20are%20also%20welcome%20on%20this%20server.%0d%0aYou%20will%20be%20disconnected%20after%2015%20minutes%20of%20inactivity.%0d%0a' -> 'USER%20anonymous%0d%0a' <- 'Anonymous%20user%20logged%20in%0d%0a' -> 'TYPE%20I%0d%0a' <- 'TYPE%20is%20now%208-bit%20binary%0d%0a' -> 'SIZE%20/debian/debian/dists/stretch/InRelease%0d%0a' <- 'Can't%20check%20for%20file%20existence%0d%0a' -> 'MDTM%20/debian/debian/dists/stretch/InRelease%0d%0a' <- 'Can't%20check%20for%20file%20existence%0d%0a' -> 'PASV%0d%0a' Get:1 ftp://localhost/debian/debian stretch InRelease <- 'Entering%20Passive%20Mode%20(127,0,0,1,99,74)%0d%0a' -> 'RETR%20/debian/debian/dists/stretch/InRelease%0d%0a' <- 'Can't%20open%20/debian/debian/dists/stretch/InRelease:%20No%20such%20file%20or%20directory%0d%0a' Err:1 ftp://localhost/debian/debian stretch InRelease Unable to fetch file, server said 'Can't open /debian/debian/dists/stretch/InRelease: No such file or directory ' [IP: 127.0.0.1 21] -> 'SIZE%20/debian/debian-security/dists/stretch/updates/InRelease%0d%0a' <- '62912%0d%0a' -> 'MDTM%20/debian/debian-security/dists/stretch/updates/InRelease%0d%0a' <- '20170626002101%0d%0a' Hit:2 ftp://localhost/debian/debian-security stretch/updates InRelease -> 'SIZE%20/debian/debian/dists/stretch-backports/InRelease%0d%0a' <- '78544%0d%0a' -> 'MDTM%20/debian/debian/dists/stretch-backports/InRelease%0d%0a' <- '20170626082744%0d%0a' Hit:3 ftp://localhost/debian/debian stretch-backports InRelease -> 'SIZE%20/virtualbox/dists/stretch/InRelease%0d%0a' <- '7776%0d%0a' -> 'MDTM%20/virtualbox/dists/stretch/InRelease%0d%0a' <- '20170429054359%0d%0a' Hit:4 ftp://localhost/virtualbox stretch InRelease Reading package lists... W: Failed to fetch ftp://localhost/debian/debian/dists/stretch/InRelease Unable to fetch file, server said 'Can't open /debian/debian/dists/stretch/InRelease: No such file or directory ' [IP: 127.0.0.1 21] W: Some index files failed to download. They have been ignored, or old ones used instead. -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "1"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-4\.9\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^linux-image-4\.9\.0-0\.bpo\.3-amd64$"; APT::NeverAutoRemove:: "^linux-image-4\.9\.0-3-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-0\.bpo\.3-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.9\.0-3-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-0\.bpo\.3-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.9\.0-3-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-0\.bpo\.3-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-4\.9\.0-3-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-0\.bpo\.3-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-4\.9\.0-3-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-0\.bpo\.3-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-4\.9\.0-3-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-0\.bpo\.3-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-4\.9\.0-3-amd64$"; APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-0\.bpo\.3-amd64$"; APT::NeverAutoRemove:: "^.*-modules-4\.9\.0-3-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-0\.bpo\.3-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-4\.9\.0-3-amd64$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-0\.bpo\.3-amd64$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.9\.0-3-amd64$"; APT::NeverAutoRemove:: "^linux-tools-4\.9\.0-0\.bpo\.2-amd64$";
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 /usr/share/gosa/plugins/admin/groups/mail/class_groupMail.inc line 1167 The problem seems to go away when replacing 'continue' with 'return' in this case, but since I am not very familiar with PHP, I don't know whether this is correct or if there are further compatibility problems in GoSA. -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gosa depends on: ii apache2 [httpd] 2.4.25-3+deb9u3 ii exim4 4.89-2+deb9u1 ii exim4-daemon-heavy [mail-transport-a 4.89-2+deb9u1 ii fonts-liberation 1:1.07.4-2 ii gettext 0.19.8.1-2 ii imagemagick 8:6.9.7.4+dfsg-11+deb9u1 ii imagemagick-6.q16 [imagemagick] 8:6.9.7.4+dfsg-11+deb9u1 ii libcrypt-smbhash-perl 0.12-4 ii libjs-scriptaculous 1.9.0-2 ii php 1:7.0+49 ii php-curl 1:7.0+49 ii php-gd 1:7.0+49 ii php-imap 1:7.0+49 ii php-ldap 1:7.0+49 ii php-mbstring 1:7.0+49 ii php-mcrypt 1:7.0+49 ii php-recode 1:7.0+49 ii php-xml 1:7.0+49 ii php7.0 [php] 7.0.19-1 ii php7.0-cli 7.0.19-1 ii php7.0-curl [php-curl] 7.0.19-1 ii php7.0-gd [php-gd] 7.0.19-1 ii php7.0-imap [php-imap] 7.0.19-1 ii php7.0-ldap [php-ldap] 7.0.19-1 ii php7.0-mbstring [php-mbstring] 7.0.19-1 ii php7.0-mcrypt [php-mcrypt] 7.0.19-1 ii php7.0-mysql [php-mysqli] 7.0.19-1 ii php7.0-recode [php-recode] 7.0.19-1 ii php7.0-xml [php-xml] 7.0.19-1 ii smarty-gettext 1.5.0-2 ii smarty3 3.1.31+20161214.1.c7d42e4+selfpack1-2 gosa recommends no packages. Versions of packages gosa suggests: pn cyrus21-imapd ii gosa-schema 2.7.4+reloaded2-13 pn gosa-si-server pn php-apc pn php-fpdf pn php-suhosin pn postfix-ldap ii slapd 2.4.44+dfsg-5+deb9u1 -- Configuration Files: /etc/gosa/shells changed [not included] -- no debconf information signature.asc Description: OpenPGP digital signature
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 and LFENCE. > > Anyway, uploading a partial, unofficial set of updates to unstable to > close the bug. Several processors are still missing. I expect an > official release from Intel soon, hopefully with updates for everything. > > Everyone should look for firmware updates, the usual good vendors > already have them out, or will have them out by the end of the next > week. Sorry for the question, this is not exactly the right place but I know of no better one: Do microcode updates delivered by this package have the same effect as BIOS/Firmware updates? Or do they complement each other? At our organization, we unfortunately have a large number of different machines from different vendors, and updating the BIOS on all of them will be a very time consuming task. So I'd like to ask whether we can expect the same protection from updated microcode and kernel packages. Thanks, Andreas
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 something that was already done in Ubuntu. IIRC, Ubuntu 12.04 was the first distro to support EFI booting (without Secure Boot, that was introduced in 14.04 via shim), and they did it that way. One reason was that Syslinux EFI wasn't ready at that time. The other one was that Ubuntu traditionally put a lot of effort into user experience, and they were using gfxboot as menu system with legacy syslinux. Unfortunately, gfxboot hadn't been ported to EFI the last time I asked about two years ago. A quick google search didn't turn up anything new, so I guess that is still the case. Someone on the syslinux mailing list told me that the gfxboot code was actually from someone not directly involved with syslinux and more or less abandoned, so someone would have to dive into it and port it to EFI. That means if you want to use syslinux EFI, you will have to stick with its traditional menu system. On the other hand, grub themes allowed for similar "shiny" menus so they chose this. Bye, Andreas
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 file. It is as such unusable. Is jessie-updates obsolete? Then it should be removed completely. Thanks!
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 ways to deal with this. The best would obviously be a redesign of the application; but there are other solutions. The most popular ones either include the environment variable XDG_RUNTIME_DIR within the sudo env (it is cleaned out by default) or use a temporary access rule using xhost. Both have its drawbacks. I don't know if there is a general acceptable solution for this, or if there is a central bug tracking page for this issue in Debian 10. If so, I'd be happy to know. I know that synaptic has been dropped completely because of this, but it would be sad to drop all affected packages which don't get fixed upstream. -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lshw-gtk depends on: ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-02.58.3-1 ii libgtk2.0-0 2.24.32-3 ii libstdc++6 8.3.0-6 Versions of packages lshw-gtk recommends: ii menu 2.1.47+b1 ii pciutils 1:3.5.2-1 ii usbutils 1:010-3 lshw-gtk suggests no packages. -- no debconf information
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 system-config-printer to select a personal default printer, by right-clicking it an selecting "Set as default". This worked without having to unlock settings or being member of the lpadmin group. This was essentially the same as running "lpoptions -d" on the command line. With Debian 9, this is not possible anymore. The relevant menu item is grayed out and only becomes available after unlock, which needs membership of the lpadmin group. "lpoptions -d" still works, and system-config-printer even reflects these changes with an emblem on the default printer. --- System information. --- Architecture: Kernel: Linux 4.19.0-0.bpo.4-amd64 Debian Release: 9.8 900 stable-updates deb.debian.org 900 stable deb.debian.org 500 stretch fai-project.org 500 icinga-stretch packages.icinga.com 100 stretch-backports deb.debian.org --- Package information. --- Depends (Version) | Installed ==-+-== gir1.2-gdkpixbuf-2.0 | 2.36.5-2+deb9u2 gir1.2-glib-2.0 | 1.50.0-1+b1 gir1.2-gtk-3.0 | 3.22.11-1 gir1.2-notify-0.7 | 0.7.7-2 gir1.2-packagekitglib-1.0 | 1.1.5-2+deb9u1 gir1.2-pango-1.0 | 1.40.5-1 python3-cups (>= 1.9.60) | 1.9.73-1 python3-cupshelpers (= 1.5.7-3) | 1.5.7-3 python3-dbus | 1.2.4-1+b1 python3-gi | 3.22.0-2 system-config-printer-common (= 1.5.7-3) | 1.5.7-3 python3:any (>= 3.3.2-2~) | Recommends (Version) | Installed =-+-=== cups-pk-helper | 0.2.6-1+b1 python3-smbc | 1.0.15.6-1 system-config-printer-udev | 1.5.7-3+b1 Suggests (Version) | Installed -+-== gnome-software (>= 3.16.5-2) | 3.22.5-1
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 default printer as a normal user. The relevant checkbox is grayed out and only becomes available after unlock, which needs membership of the lpadmin group. This is usually not wanted in an organizational network. "lpoptions -d" on the command line works as expected, and the control center even reflects these changes with a checkmark on the default printer. Why is it not possible to change it? --- System information. --- Architecture: Kernel: Linux 4.19.0-0.bpo.4-amd64 Debian Release: 9.8 900 stable-updates deb.debian.org 900 stable deb.debian.org 500 stretch fai-project.org 500 icinga-stretch packages.icinga.com 100 stretch-backports deb.debian.org --- Package information. --- Depends (Version) | Installed -+-=== libaccountsservice0 (>= 0.6.40) | 0.6.43-1 libatk1.0-0 (>= 1.12.4) | 2.22.0-1 libc6 (>= 2.4) | 2.24-11+deb9u4 libcairo-gobject2 (>= 1.10.0) | 1.14.8-1 libcairo2 (>= 1.10.0) | 1.14.8-1 libcanberra-gtk3-0 (>= 0.25) | 0.30-3 libcanberra0 (>= 0.2) | 0.30-3 libcheese-gtk25 (>= 3.18.0) | 3.22.1-1+b1 libcheese8 (>= 3.18.0) | 3.22.1-1+b1 libclutter-1.0-0 (>= 1.23.4) | 1.26.0+dfsg-3 libclutter-gtk-1.0-0 (>= 0.91.8) | 1.8.2-2 libcolord-gtk1 (>= 0.1.24) | 0.1.26-1.1 libcolord2 (>= 0.1.31) | 1.3.3-2 libcups2 (>= 1.6.0) | 2.2.1-8+deb9u3 libfontconfig1 (>= 2.11) | 2.11.0-6.7+b1 libgdk-pixbuf2.0-0 (>= 2.25.2) | 2.36.5-2+deb9u2 libglib2.0-0 (>= 2.44.0) | 2.50.3-2 libgnome-bluetooth13 (>= 3.18.2) | 3.20.1-1 libgnome-desktop-3-12 (>= 3.21.4) | 3.22.2-1 libgoa-1.0-0b (>= 3.16.2) | 3.22.5-1 libgoa-backend-1.0-1 (>= 3.10.0) | 3.22.5-1 libgrilo-0.3-0 (>= 0.3.0) | 0.3.2-2 libgtk-3-0 (>= 3.22.0) | 3.22.11-1 libgtop-2.0-10 (>= 2.22.3) | 2.34.2-1 libgudev-1.0-0 (>= 146) | 230-3 libibus-1.0-5 (>= 1.5.2) | 1.5.14-3+deb9u1 libkrb5-3 (>= 1.8+dfsg) | 1.15-1+deb9u1 libmm-glib0 (>= 0.7.991) | 1.6.4-1 libnm0 (>= 1.1.90) | 1.6.2-3+deb9u2 libnma0 (>= 1.1.90) | 1.4.4-1+deb9u1 libpango-1.0-0 (>= 1.18.0) | 1.40.5-1 libpangocairo-1.0-0 (>= 1.18.0) | 1.40.5-1 libpolkit-gobject-1-0 (>= 0.99) | 0.105-18+deb9u1 libpulse-mainloop-glib0 (>= 0.99.1) | 10.0-1+deb9u1 libpulse0 (>= 0.99.1) | 10.0-1+deb9u1 libpwquality1 (>= 1.1.0) | 1.3.0-1+b1 libsmbclient (>= 2:4.0.3+dfsg1) | 2:4.5.16+dfsg-1+deb9u1 libsoup2.4-1 (>= 2.33.92) | 2.56.0-2+deb9u2 libupower-glib3 (>= 0.99.0) | 0.99.4-4+b1 libwacom2 (>= 0.7) | 0.22-1+b1 libx11-6 | 2:1.6.4-3+deb9u1 libxi6 (>= 2:1.2.99.4) | 2:1.7.9-1 libxml2 (>= 2.7.4) | 2.9.4+dfsg1-2.2+deb9u2 accountsservice | 0.6.43-1 apg | 2.2.3.dfsg.1-4+b1 colord (>= 0.1.30) | 1.3.3-2 desktop-file-utils | 0.23-1 gnome-control-center-data (<< 1:3.23) | 1:3.22.2-3 gnome-control-center-data (>= 1:3.22.2-3) | 1:3.22.2-3 gnome-desktop3-data | 3.22.2-1 gnome-settings-daemon (>= 3.19.1) | 3.22.2-2+deb9u2 gsettings-desktop-schemas (>= 3.21.4) | 3.22.0-1 Recommends (Version) | Installed ===-+-=== cups-pk-helper | 0.2.6-1+b1 gnome-online-accounts | 3.22.5-1 gnome-user-guide | 3.22.0-1 gnome-user-share | 3.18.3-1+b1 gkbd-capplet | 3.22.0.1-1+b1 iso-codes | 3.75-1 libcanberra-pulse | 0.30-3 mousetweaks | 3.12.0-1+b1 policykit-1 | 0.105-18+deb9u1 rygel | 0.32.1-3 OR rygel-tracker | 0.32.1-3 system-config-printer-common (>= 1.4) | 1.5.7-3 network-manager-gnome (>= 0.9.8) | 1.4.4-1+deb9u1 libnss-myhostname | 232-25+deb9u11 cracklib-runtime | 2.9.2-5 pulseaudio-module-bluetooth | 10.0-1+deb9u1 realmd | 0.16.3-1 Suggests (Version) | Installed ==-+-=== gstreamer1.0-pulseaudio | 1.10.4-1 libcanberra-gtk-module | 0.30-3 libcanberra-gtk3-module | 0.30-3 x11-xserver-utils | 7.7+7+b1
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 format as exFAT. Manually creating the symlink helped fix the problem. -- System Information: Debian Release: 11.0 APT prefers stable APT policy: (900, 'stable'), (500, 'stable-security') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages exfatprogs depends on: ii libc6 2.31-13 exfatprogs recommends no packages. exfatprogs suggests no packages. -- no debconf information
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 (separate:22416): LibGimp-CRITICAL **: 14:10:05.069: gimp_tile_unref: assertion 'tile->ref_count > 0' failed (separate:22416): LibGimp-CRITICAL **: 14:10:05.069: gimp_tile_unref: assertion 'tile->ref_count > 0' failed /usr/lib/gimp/2.0/plug-ins/separate: fatal error: Speicherzugriffsfehler gimp: GEGL-WARNUNG: (../gegl/buffer/gegl-tile-handler-cache.c:1076):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (_queue)) eEeek! 5 GeglBuffers leaked Steps to reproduce: * Run GIMP, open any image * Click Image>Separate>Separate * Confirm dialog with OK * Plugin crashes The problem has already been identified and dicussed here: https://gitlab.gnome.org/GNOME/gimp/-/issues/2305 In short, the problem seems to be that the plugin "assumes that gimp_tile_width () and gimp_tile_height () return 64, but evidently tiles changed size in gimp-2.10 and so third-party plug-ins have to be adjusted" There is a proposed patch which I don't know (yet) if it works: In this case the problem is in separate-core.c, line 545 should have been: sc->cmyktemp = g_new (guchar, gimp_tile_width () * gimp_tile_height () * 4); but probably there is the same problem at line 429: sc->cmyktemp = g_new (guchar, 64 * 64 * 4); The plugin itself seems to have been abandoned long ago, so there is no chance to get it fixed upstream. But if above patch works, it should be possible to include it in the debian package. I will give it a try and report back when I have found out something. -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (900, 'stable-updates'), (900, 'stable'), (500, 'stable-security') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-18-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp-plugin-registry depends on: ii gimp2.10.22-4 ii libc6 2.31-13+deb11u5 ii libgcc-s1 10.2.1-6 ii libgdk-pixbuf2.0-0 2.40.2-2 ii libgimp2.0 2.10.22-4 ii libglib2.0-02.66.8-1 ii libgtk2.0-0 2.24.33-2 ii libjpeg62-turbo 1:2.0.6-4 ii liblcms2-2 2.12~rc1-2 ii liblqr-1-0 0.4.2-2.1 ii libpango-1.0-0 1.46.2-3 ii libstdc++6 10.2.1-6 ii libtiff-tools 4.2.0-1+deb11u1 ii libtiff54.2.0-1+deb11u1 ii python3 3.9.2-3 ii xdg-utils 1.1.3-4.1 Versions of packages gimp-plugin-registry recommends: ii gimp-gmic 2.9.4-4 Versions of packages gimp-plugin-registry suggests: pn icc-profiles -- no debconf information
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); -sc->cmyktemp = g_new (guchar, 64 * 64 * 4); +sc->cmyktemp = g_new (guchar, gimp_tile_width () * gimp_tile_height () * 4); gimp_progress_init (_("Separating...")); ntiles = drawable->ntile_rows * drawable->ntile_cols; @@ -549,7 +549,7 @@ n_drawables++; } -sc->cmyktemp = g_new (guchar, 64 * 64 * 4); +sc->cmyktemp = g_new (guchar, gimp_tile_width () * gimp_tile_height () * 4); gimp_progress_init (_("Separating...")); ntiles = drawable->ntile_cols * drawable->ntile_rows;
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 "application/octet-stream" and doesn't know how to open it when double-clicking it. When copying the files over to a local drive, the MIME type is recognized correctly. Other files types, e.g. PDF or ODT, work as expected. Problem also occurs in Debian bookworm, but does not occur in latest Linux Mint with Nemo 5.8.4. Problem does *not* occur with nautilus, so I guess it is not a GNOME thing. -- System Information: Debian Release: 11.8 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-26-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nemo depends on: ii cinnamon-desktop-data 4.8.1-2 ii desktop-file-utils 0.26-1 ii gsettings-desktop-schemas 3.38.0-2 ii gvfs 1.46.2-1 ii libatk1.0-02.36.0-2 ii libc6 2.31-13+deb11u7 ii libcairo-gobject2 1.16.0-5 ii libcairo2 1.16.0-5 ii libcinnamon-desktop4 4.8.1-2 ii libexempi8 2.5.2-1 ii libexif12 0.6.22-3 ii libgail-3-03.24.24-4+deb11u3 ii libgdk-pixbuf-2.0-02.42.2+dfsg-1+deb11u1 ii libglib2.0-0 2.66.8-1 ii libglib2.0-data2.66.8-1 ii libgtk-3-0 3.24.24-4+deb11u3 ii libnemo-extension1 4.8.6-2 ii libnotify4 0.7.9-3 ii libpango-1.0-0 1.46.2-3 ii libpangocairo-1.0-01.46.2-3 ii libselinux13.1-3 ii libx11-6 2:1.7.2-1+deb11u2 ii libxapp1 2.0.7-1 ii libxml22.9.10+dfsg-6.7+deb11u4 ii nemo-data 4.8.6-2 ii shared-mime-info 2.0-1 Versions of packages nemo recommends: ii cinnamon-l10n4.8.3-1 ii gvfs-backends1.46.2-1 ii gvfs-fuse1.46.2-1 ii librsvg2-common 2.50.3+dfsg-1+deb11u1 ii nemo-fileroller 4.8.0-1 Versions of packages nemo suggests: ii eog 3.38.2-1 ii evince [pdf-viewer] 3.38.2-1 ii okular [pdf-viewer] 4:20.12.3-2 ii totem3.38.0-2 ii vlc [mp3-decoder]3.0.20-0+deb11u1 ii xdg-user-dirs0.17-2 -- no debconf information