Bug#800527: devscripts: bts fails to retrieve bug reports as a mailbox
Package: devscripts Version: 2.15.8~bpo8+1 Severity: normal Dear Maintainer, retrieving a bug report as a mailbox fails with the following error message: bts show --mbox 787157 /home/uwe/.cache/devscripts/bts/787157.mbox is not a mailbox. The file indeed is not a mailbox and contains almost no data (file attached below). I've also tried to call bts with the --noconf and --force-refresh options, but the result is still the same. Retrieving the bug report in a browser with bts show 787157 works as expected. Regards Uwe -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- DEBUILD_LINTIAN_OPTS='-i -I --show-overrides' RMADISON_ARCHITECTURE=source,all,amd64,i386 -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (850, 'stable'), (840, 'stable-updates'), (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages devscripts depends on: ii dpkg-dev 1.17.25 ii libc62.19-18+deb8u1 ii perl 5.20.2-3+deb8u1 ii python3 3.4.2-2 pn python3:any Versions of packages devscripts recommends: ii at 3.1.16-1 ii curl7.38.0-4+deb8u2 ii dctrl-tools 2.23 ii debian-keyring 2015.04.10 ii dput0.9.6.4 ii equivs 2.0.9 ii fakeroot1.20.2-1 ii file1:5.22+15-2 ii gnupg 1.4.18-7 ii libdistro-info-perl 0.14 ii libencode-locale-perl 1.03-1 ii libjson-perl2.61-1 ii liblwp-protocol-https-perl 6.06-2 ii libsoap-lite-perl 1.11-1 ii liburi-perl 1.64-1 ii libwww-perl 6.08-1 ii lintian 2.5.30+deb8u4 ii man-db 2.7.0.2-5 ii patch 2.7.5-1 ii patchutils 0.3.3-1 ii python3-debian 0.1.27 ii python3-magic 1:5.22+15-2 ii sensible-utils 0.0.9 ii strace 4.9-2 ii unzip 6.0-16 ii wdiff 1.2.2-1 ii wget1.16-1 ii xz-utils5.1.1alpha+20120614-2+b3 Versions of packages devscripts suggests: ii bsd-mailx [mailx]8.1.2-0.20141216cvs-2 ii build-essential 11.7 pn cvs-buildpackage pn debbindiff pn devscripts-el ii gnuplot 4.6.6-2 ii gpgv 1.4.18-7 pn libauthen-sasl-perl pn libfile-desktopentry-perl ii libnet-smtp-ssl-perl 1.01-3 pn libterm-size-perl ii libtimedate-perl 2.3000-2 ii libyaml-syck-perl1.27-2+b2 ii mutt 1.5.23-3 ii openssh-client [ssh-client] 1:6.7p1-5 pn svn-buildpackage ii w3m 0.5.3-19 -- debconf-show failed 787157.mbox Description: Binary data
Bug#798909: linux-image-4.1.0-0.bpo.2-686-pae: Brightness control on a HP Compaq nx8220 does not work anymore since kernel 3.16
Package: src:linux Version: 4.1.6-1~bpo8+1 Severity: normal Dear Maintainer, since kernel version 3.16.7-ckt11-1+deb8u3 from jessie the keys for brightness control on my HP Compaq nx8220 laptop do not work anymore. The problem also exists with kernel version 4.1.6-1~bpo8+1 from jessie-backports. When I boot an older kernel (linux-image-3.14-2-686-pae, version 3.14.15-2) the brightness keys do work (without any other changes to the system). Regards Uwe -- Package-specific info: ** Version: Linux version 4.1.0-0.bpo.2-686-pae (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.1.6-1~bpo8+1 (2015-09-09) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.1.0-0.bpo.2-686-pae root=UUID=32077a82-12e5-4f22-a606-1dd16fcd68c1 ro quiet ** Not tainted ** Kernel log: [ 12.005545] [TTM] Initializing pool allocator [ 12.005554] [TTM] Initializing DMA pool allocator [ 12.005594] [drm] radeon: 64M of VRAM memory ready [ 12.005597] [drm] radeon: 512M of GTT memory ready. [ 12.005618] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 12.006564] [drm] radeon: power management initialized [ 12.006584] [drm] radeon: 1 quad pipes, 1 Z pipes initialized. [ 12.007467] [drm] PCIE GART of 512M enabled (table at 0xC004). [ 12.007490] radeon :01:00.0: WB enabled [ 12.007496] radeon :01:00.0: fence driver on ring 0 use gpu addr 0xa000 and cpu addr 0xf2fe5000 [ 12.007499] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 12.007500] [drm] Driver supports precise vblank timestamp query. [ 12.007503] radeon :01:00.0: radeon: MSI limited to 32-bit [ 12.007541] radeon :01:00.0: radeon: using MSI. [ 12.007566] [drm] radeon: irq initialized. [ 12.007576] [drm] Loading R300 Microcode [ 12.184489] radeon :01:00.0: firmware: direct-loading firmware radeon/R300_cp.bin [ 12.184887] [drm] radeon: ring at 0xA0001000 [ 12.184918] [drm] ring test succeeded in 0 usecs [ 12.185279] [drm] ib test succeeded in 0 usecs [ 12.186619] [drm] Panel ID String: LPL [ 12.186626] [drm] Panel Size 1680x1050 [ 12.186900] [drm] Radeon Display Connectors [ 12.186905] [drm] Connector 0: [ 12.186909] [drm] VGA-1 [ 12.186916] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [ 12.186919] [drm] Encoders: [ 12.186923] [drm] CRT1: INTERNAL_DAC1 [ 12.186927] [drm] Connector 1: [ 12.186931] [drm] DVI-D-1 [ 12.186935] [drm] HPD1 [ 12.186940] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 [ 12.186944] [drm] Encoders: [ 12.186948] [drm] DFP1: INTERNAL_TMDS1 [ 12.186951] [drm] Connector 2: [ 12.186955] [drm] LVDS-1 [ 12.186961] [drm] DDC: 0x68 0x68 0x68 0x68 0x68 0x68 0x68 0x68 [ 12.186964] [drm] Encoders: [ 12.186968] [drm] LCD1: INTERNAL_LVDS [ 12.186971] [drm] Connector 3: [ 12.186975] [drm] SVIDEO-1 [ 12.186978] [drm] Encoders: [ 12.186982] [drm] TV1: INTERNAL_DAC2 [ 12.252511] Bluetooth: Core ver 2.20 [ 12.252573] NET: Registered protocol family 31 [ 12.252575] Bluetooth: HCI device and connection manager initialized [ 12.252724] Bluetooth: HCI socket layer initialized [ 12.252729] Bluetooth: L2CAP socket layer initialized [ 12.252737] Bluetooth: SCO socket layer initialized [ 12.269777] [drm] fb mappable at 0xC00C [ 12.269782] [drm] vram apper at 0xC000 [ 12.269784] [drm] size 7057408 [ 12.269785] [drm] fb depth is 24 [ 12.269787] [drm]pitch is 6720 [ 12.269981] fbcon: radeondrmfb (fb0) is primary device [ 12.313714] Console: switching to colour frame buffer device 210x65 [ 12.322717] radeon :01:00.0: fb0: radeondrmfb frame buffer device [ 12.322720] radeon :01:00.0: registered panic notifier [ 12.322835] [drm] Initialized radeon 2.42.0 20080528 for :01:00.0 on minor 0 [ 12.499707] usbcore: registered new interface driver btusb [ 12.568146] cfg80211: World regulatory domain updated: [ 12.568153] cfg80211: DFS Master region: unset [ 12.568156] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 12.568161] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 12.568165] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [ 12.568169] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) [ 12.568174] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 12.568179] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 12.568183] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) [ 12.568186] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [ 12.568190] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [ 12.676468] Adding 979960k swap on /dev/sda2.
Bug#763406: geeqie: Float window uses image window dimensions
Hi, I also run into this bug after upgrading to jessie. I've restored the old config file from version 1.1 and have set it to read only. Geeqie complains on exit that it cannot save the config file (why wants it to save it anyway when I don't have changed the configuration?), but at least I don't have to rearrange the windows after every program start. Unfortunately this way I cannot change any settings in geeqie. So at least for me this bug also is important. ;) On Sep 30, Klaus Ethgen wrote: Should be not that big problem to fix but I will not promise any. :-) Any hope to get that fixed in jessie? Regards Uwe
Bug#725768: tkcvs: tk depends
On Apr 29, Matt Taggart wrote: I'd also be happy to use something not based on '90's technology, but I have yet to find anything that works as well. If people have suggestions I would love to hear them. There are not many. With the same functionality there's only kdiff3 and maybe meld. But they are much more heavyweight. One of the advantages of tkdiff is that it's rather lightweight and has not a lot of dependencies. Unfortunately the bundling in the tkcvs package introduces unnecessary dependencies and reduces this advantage. There where plans to split this package (see the last mail in bug #664084), but this was more than 3 years ago and nothing has happened since then. If someone starts to work on this package please consider to split it up into separate packages (tkdiff, tkcvs and tkdirdiff) and maybe drop either the tkdirdiff part or the dirdiff package (see bugs #664084 and #699146). Regards Uwe
Bug#795098: cxref complains about a locally modified config file on a fresh installation
Package: cxref Version: 1.6e-1 Severity: serious Justification: Policy 10.7.3 Dear Maintainer, on a fresh installation cxref complains about a locally modified config file: A new version (/tmp/cxref-cpp.defines) of configuration file /etc/cxref/cxref-cpp.defines is available, but the version installed currently has been locally modified. Even worse this config file is marked as locally modified after the package installation and apt probably will complain on every future package upgrade although I have chosen install the package maintainer's version in the installation dialog. It looks like the cxref package contains an (older) version of this config file and is overwriting it in the postinst script. I'm not sure about the severity of this bug. According to https://release.debian.org/jessie/rc_policy.txt and Debian Policy 10.7.3 it should be serious. Please adjust the severity when I interpret that wrong. Regards Uwe diff of the old and new version of the config file: # diff /etc/cxref/cxref-cpp.defines /tmp/cxref-cpp.defines 102c102 #define __GNUC_PATCHLEVEL__ 1 --- #define __GNUC_PATCHLEVEL__ 2 104a105,106 #define __has_include_next(STR) __has_include_next__(STR) #define __has_include(STR) __has_include__(STR) 238c240 #define __VERSION__ 4.9.1 --- #define __VERSION__ 4.9.2 -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (850, 'stable'), (840, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cxref depends on: ii debconf [debconf-2.0] 1.5.56 ii gcc4:4.9.2-2 ii libc6 2.19-18 ii ucf3.0030 cxref recommends no packages. Versions of packages cxref suggests: ii chromium [www-browser] 44.0.2403.89-1~deb8u1 pn cxref-docnone ii iceweasel [www-browser] 31.8.0esr-1~deb8u1 ii surf [www-browser] 0.6-1 ii texlive-binaries 2014.20140926.35254-6 -- Configuration Files: /etc/cxref/cxref-cpp.defines changed: // cxref-cpp runtime configuration file // -I/usr/lib/gcc/x86_64-linux-gnu/4.9/include // -I/usr/local/include // -I/usr/lib/gcc/x86_64-linux-gnu/4.9/include-fixed // -I/usr/include/x86_64-linux-gnu // -I/usr/include -- debconf information: cxref/cxref-cpp-autoconf: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707824: less: crashes with multiple group regex
Package: less Version: 458-3 Followup-For: Bug #707824 Hi, for me the bug only affects the i386 version of less, but not the amd64 version. The same test crashes on an i386 system, but not on an amd64 system (with the same package versions). test: dpkg -s dash | less -p '^(Package|Description(-en)?):' == i386 == crash: *** Error in `less': double free or corruption (fasttop): 0xb7ba6808 *** Aborted package versions: $ dpkg -l less debianutils libc6 libtinfo5 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii debianutils4.4+b1 i386 Miscellaneous utilities specific ii less 458-3i386 pager program similar to more ii libc6:i386 2.19-18 i386 GNU C Library: Shared libraries ii libtinfo5:i386 5.9+20140913 i386 shared low-level terminfo library == amd64 == no crash $ dpkg -l less debianutils libc6 libtinfo5 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii debianutils4.4+b1 amd64Miscellaneous utilities specific ii less 458-3amd64pager program similar to more ii libc6:amd642.19-18 amd64GNU C Library: Shared libraries ii libtinfo5:amd6 5.9+20140913 amd64shared low-level terminfo library Here's the backtrace for a crash on an i386 system, but it probably doesn't help much as it only contains the malloc error handling: *** Error in `/usr/bin/less': double free or corruption (fasttop): 0x565917d0 *** Program received signal SIGABRT, Aborted. 0xf7fdad70 in __kernel_vsyscall () (gdb) bt #0 0xf7fdad70 in __kernel_vsyscall () #1 0xf7e0a307 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xf7e0b9c3 in __GI_abort () at abort.c:89 #3 0xf7e486f8 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0xf7f3e65c *** Error in `%s': %s: 0x%s ***\n) at ../sysdeps/posix/libc_fatal.c:175 #4 0xf7e4e76a in malloc_printerr (action=optimized out, str=0xf7f3e820 double free or corruption (fasttop), ptr=0x565917d0) at malloc.c:4996 #5 0xf7e4f3bd in _int_free (av=0xf7f82420 main_arena, p=optimized out, have_lock=0) at malloc.c:3840 #6 0x5656a4c0 in ?? () #7 0x5656c355 in ?? () #8 0x5656ca7c in ?? () #9 0x56563198 in ?? () #10 0x56562904 in ?? () #11 0x56563d48 in ?? () #12 0x5656d2a8 in ?? () #13 0x5655d4b7 in ?? () #14 0x5655edda in ?? () #15 0x565574a0 in main () Regards Uwe -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (850, 'stable'), (840, 'stable-updates'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages less depends on: ii debianutils 4.4+b1 ii libc62.19-18 ii libtinfo55.9+20140913-1+b1 less recommends no packages. less suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777683: Network hang and data corruption with e1000e driver
Control: retitle -1 linux-image-3.16: Network hang and data corruption with e1000e driver Control: found -1 3.16.7-ckt11-1+deb8u2 After upgrading the original system to jessie the problem still appears when I boot kernel 3.16 from jessie, but not when I boot kernel 3.2 from wheezy. The network hangs sporadically and files which were transferred while the bug occurred contain large blocks of corrupted data (several kB). The logs from jessie are attached below. On Jun 30, Mike Crowe wrote: At that point as a stab in the dark I ran: ethtool -K eth-office tso off and the network has been reliable and no such messages have appeared since (about 24 hours.) Thanks for sharing, Mike! I'll try that. Regards Uwe 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DM Gigabit Network Connection [8086:104a] (rev 02) Subsystem: Hewlett-Packard Company Device [103c:2800] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 41 Region 0: Memory at f050 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at f0525000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 2000 [size=32] Capabilities: [c8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0300c Data: 4152 Kernel driver in use: e1000e Aug 04 06:10:30 c1 kernel: e1000e :00:19.0 lan: Detected Hardware Unit Hang: TDH 31 TDT 5b next_to_use 5b next_to_clean31 buffer_info[next_to_clean]: time_stamp 17cb9f3 next_to_watch36 jiffies 17cbcc1 next_to_watch.status 0 MAC Status 802a3 PHY Status 792d PHY 1000BASE-T Status 3800 PHY Extended Status3000 PCI Status 10 Aug 04 06:10:32 c1 kernel: e1000e :00:19.0 lan: Detected Hardware Unit Hang: TDH 31 TDT 5b next_to_use 5b next_to_clean31 buffer_info[next_to_clean]: time_stamp 17cb9f3 next_to_watch36 jiffies 17cbeb5 next_to_watch.status 0 MAC Status 802a3 PHY Status 792d PHY 1000BASE-T Status 3800 PHY Extended Status3000 PCI Status 10 Aug 04 06:10:33 c1 kernel: [ cut here ] Aug 04 06:10:33 c1 kernel: WARNING: CPU: 0 PID: 0 at /build/linux-M5bqDz/linux-3.16.7-ckt11/net/sched/sch_generic.c:264 dev_watchdog+0x1e8/0x200() Aug 04 06:10:33 c1 kernel: NETDEV WATCHDOG: lan (e1000e): transmit queue 0 timed out Aug 04 06:10:33 c1 kernel: Modules linked in: tcp_diag inet_diag authenc xfrm4_mode_transport xfrm6_mode_tunnel xfrm4_mode_tunnel binfmt_misc xt_recent xt_TCPMSS xt_multiport xt_policy xt_nat xt_conntrack xt_tcpudp ipt_REJECT xt_LOG iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conn Aug 04 06:10:33 c1 kernel: hmac crypto_null af_key xfrm_algo ses enclosure usb_storage iTCO_wdt iTCO_vendor_support kvm_intel kvm hp_wmi ppdev sparse_keymap rfkill snd_hda_codec_realtek snd_hda_codec_generic sata_sil tg3 psmouse libphy evdev snd_hda_intel snd_hda_controller snd_hda_codec sg snd_hwdep serio_raw snd_pc Aug 04 06:10:33 c1 kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16.0-4-686-pae #1 Debian 3.16.7-ckt11-1+deb8u2 Aug 04 06:10:33 c1 kernel: Hardware name: Hewlett-Packard HP Compaq dc7700p Convertible Minitower/0A58h, BIOS 786E1 v01.15 08/05/2008 Aug 04 06:10:33 c1 kernel: c15adc04 f4809ef4 c14773af f4809f04 c1056c74 c15adbc8 f4809f20 Aug 04 06:10:33 c1 kernel: c15adc04 0108 c13bd268 c13bd268 0009 f34a8000 fe834532 ff25 Aug 04 06:10:33 c1 kernel:
Bug#777683: Network hangs sporadically after upgrade to jessie
Control: found -1 3.16.7-ckt11-1 The problem still appears with the updated jessie kernel. It does not appear when I boot the system with the old wheezy kernel. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777683: Network hangs sporadically after upgrade to jessie
Control: found -1 3.16.7-ckt9-3~deb8u1 The same bug seems to affect another system (HP Compaq dc7800 SFF) after upgrading it to jessie (with kernel 3.16). The machine has been working without problems for nearly 2 years under wheezy with kernel 3.2. Regards Uwe Hardware: HP Compaq dc7800 SFF Debian Release: 8.0 amd64 Kernel: Linux cx 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) x86_64 GNU/Linux Network device: 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) Subsystem: Hewlett-Packard Company Device 2818 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 43 Region 0: Memory at f018 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at f01a5000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 4100 [size=32] Capabilities: [c8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0300c Data: 4143 Capabilities: [e0] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: e1000e Kernel log: May 04 17:04:39 cx kernel: e1000e :00:19.0 eth0: Detected Hardware Unit Hang: TDH ef TDT b next_to_use b next_to_cleaned buffer_info[next_to_clean]: time_stamp 1937c next_to_watchef jiffies 1953a next_to_watch.status 0 MAC Status 80283 PHY Status 792d PHY 1000BASE-T Status 3800 PHY Extended Status3000 PCI Status 10 May 04 17:04:41 cx kernel: e1000e :00:19.0 eth0: Detected Hardware Unit Hang: TDH ef TDT b next_to_use b next_to_cleaned buffer_info[next_to_clean]: time_stamp 1937c next_to_watchef jiffies 1972e next_to_watch.status 0 MAC Status 80283 PHY Status 792d PHY 1000BASE-T Status 3800 PHY Extended Status3000 PCI Status 10 May 04 17:04:43 cx kernel: e1000e :00:19.0 eth0: Detected Hardware Unit Hang: TDH ef TDT b next_to_use b next_to_cleaned buffer_info[next_to_clean]: time_stamp 1937c next_to_watchef jiffies 19922 next_to_watch.status 0 MAC Status 80283 PHY Status 792d PHY 1000BASE-T Status 3800 PHY Extended Status3000 PCI Status 10 May 04 17:04:45 cx kernel: e1000e :00:19.0 eth0: Detected Hardware Unit Hang: TDH ef TDT b next_to_use b next_to_cleaned buffer_info[next_to_clean]: time_stamp 1937c next_to_watchef jiffies 19b16 next_to_watch.status 0 MAC Status 80283 PHY Status 792d PHY 1000BASE-T Status 3800 PHY Extended Status3000 PCI Status 10 May 04 17:04:46
Bug#779063: exim4-daemon-light: file size tripled with no apparent reason
Package: exim4-daemon-light Version: 4.84-8 Severity: normal Dear Maintainer, the installed size of package exim4-daemon-light on amd64 has increased from 1287 to 3268 between versions 4.84-7 and 4.84-8 without any apparent reason in the changelog: Package: exim4-daemon-light Architecture: amd64 Version: 4.84-7 Installed-Size: 1287 Version: 4.84-8 Installed-Size: 3268 The file size of the exim4 binary has more than tripled between the two package versions: -rwsr-xr-x root/root 1031104 2015-02-07 16:40 ./usr/sbin/exim4 -rwsr-xr-x root/root 3124160 2015-02-17 18:45 ./usr/sbin/exim4 Compared with exim4-daemon-heavy this version is not that light anymore. ;) Package: exim4-daemon-heavy Version: 4.84-8 Installed-Size: 1349 Regards Uwe -- Package-specific info: Exim version 4.84 #3 built 17-Feb-2015 17:45:49 Copyright (c) University of Cambridge, 1995 - 2014 (c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2014 Berkeley DB: Berkeley DB 5.3.28: (September 9, 2013) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DKIM PRDR OCSP Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages exim4-daemon-light depends on: ii debconf [debconf-2.0] 1.5.55 ii exim4-base 4.84-8 ii libc6 2.19-13 ii libdb5.3 5.3.28-7~deb8u1 ii libgnutls-deb0-28 3.3.8-5 ii libpcre3 2:8.35-3.3 exim4-daemon-light recommends no packages. exim4-daemon-light suggests no packages. -- debconf information: exim4-daemon-light/drec: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#777683: linux-image-3.16.0-0.bpo.4-686-pae: high package loss and data corruption with e1000e driver
Package: src:linux Version: 3.16.7-ckt2-1~bpo70+1 Severity: important Dear Maintainer, after switching to kernel 3.16 from backports network packets over the on-board ethernet controller (Intel Corporation 82566DM Gigabit Network Connection, driver e1000e) are only transferred in bursts, transfer rates are below 1 MB/s, packet loss is at 70 to 80%, transferred files are corrupted and I get a lot of kernel errors (see below). Switching back to kernel linux-image-3.2.0-4-686-pae fixes the problem. Regards Uwe -- Package-specific info: ** Kernel log: boot messages should be attached Feb 11 05:05:02 c1 kernel: [4667586.001612] e1000e :00:19.0 lan: Detected Hardware Unit Hang: Feb 11 05:05:02 c1 kernel: [4667586.001612] TDH ab Feb 11 05:05:02 c1 kernel: [4667586.001612] TDT 11 Feb 11 05:05:02 c1 kernel: [4667586.001612] next_to_use 11 Feb 11 05:05:02 c1 kernel: [4667586.001612] next_to_cleanab Feb 11 05:05:02 c1 kernel: [4667586.001612] buffer_info[next_to_clean]: Feb 11 05:05:02 c1 kernel: [4667586.001612] time_stamp 458c46a8 Feb 11 05:05:02 c1 kernel: [4667586.001612] next_to_watchb0 Feb 11 05:05:02 c1 kernel: [4667586.001612] jiffies 458c487d Feb 11 05:05:02 c1 kernel: [4667586.001612] next_to_watch.status 0 Feb 11 05:05:02 c1 kernel: [4667586.001612] MAC Status 802a3 Feb 11 05:05:02 c1 kernel: [4667586.001612] PHY Status 792d Feb 11 05:05:02 c1 kernel: [4667586.001612] PHY 1000BASE-T Status 3800 Feb 11 05:05:02 c1 kernel: [4667586.001612] PHY Extended Status3000 Feb 11 05:05:02 c1 kernel: [4667586.001612] PCI Status 10 Feb 11 05:05:04 c1 kernel: [4667588.001373] e1000e :00:19.0 lan: Detected Hardware Unit Hang: Feb 11 05:05:04 c1 kernel: [4667588.001373] TDH ab Feb 11 05:05:04 c1 kernel: [4667588.001373] TDT 11 Feb 11 05:05:04 c1 kernel: [4667588.001373] next_to_use 11 Feb 11 05:05:04 c1 kernel: [4667588.001373] next_to_cleanab Feb 11 05:05:04 c1 kernel: [4667588.001373] buffer_info[next_to_clean]: Feb 11 05:05:04 c1 kernel: [4667588.001373] time_stamp 458c46a8 Feb 11 05:05:04 c1 kernel: [4667588.001373] next_to_watchb0 Feb 11 05:05:04 c1 kernel: [4667588.001373] jiffies 458c4a71 Feb 11 05:05:04 c1 kernel: [4667588.001373] next_to_watch.status 0 Feb 11 05:05:04 c1 kernel: [4667588.001373] MAC Status 802a3 Feb 11 05:05:04 c1 kernel: [4667588.001373] PHY Status 792d Feb 11 05:05:04 c1 kernel: [4667588.001373] PHY 1000BASE-T Status 3800 Feb 11 05:05:04 c1 kernel: [4667588.001373] PHY Extended Status3000 Feb 11 05:05:04 c1 kernel: [4667588.001373] PCI Status 10 Feb 11 05:05:06 c1 kernel: [4667590.000645] e1000e :00:19.0 lan: Detected Hardware Unit Hang: Feb 11 05:05:06 c1 kernel: [4667590.000645] TDH ab Feb 11 05:05:06 c1 kernel: [4667590.000645] TDT 11 Feb 11 05:05:06 c1 kernel: [4667590.000645] next_to_use 11 Feb 11 05:05:06 c1 kernel: [4667590.000645] next_to_cleanab Feb 11 05:05:06 c1 kernel: [4667590.000645] buffer_info[next_to_clean]: Feb 11 05:05:06 c1 kernel: [4667590.000645] time_stamp 458c46a8 Feb 11 05:05:06 c1 kernel: [4667590.000645] next_to_watchb0 Feb 11 05:05:06 c1 kernel: [4667590.000645] jiffies 458c4c65 Feb 11 05:05:06 c1 kernel: [4667590.000645] next_to_watch.status 0 Feb 11 05:05:06 c1 kernel: [4667590.000645] MAC Status 802a3 Feb 11 05:05:06 c1 kernel: [4667590.000645] PHY Status 792d Feb 11 05:05:06 c1 kernel: [4667590.000645] PHY 1000BASE-T Status 3800 Feb 11 05:05:06 c1 kernel: [4667590.000645] PHY Extended Status3000 Feb 11 05:05:06 c1 kernel: [4667590.000645] PCI Status 10 Feb 11 05:05:08 c1 kernel: [4667592.000580] e1000e :00:19.0 lan: Detected Hardware Unit Hang: Feb 11 05:05:08 c1 kernel: [4667592.000580] TDH ab Feb 11 05:05:08 c1 kernel: [4667592.000580] TDT 11 Feb 11 05:05:08 c1 kernel: [4667592.000580] next_to_use 11 Feb 11 05:05:08 c1 kernel: [4667592.000580] next_to_cleanab Feb 11 05:05:08 c1 kernel: [4667592.000580] buffer_info[next_to_clean]: Feb 11 05:05:08 c1 kernel: [4667592.000580] time_stamp 458c46a8 Feb 11 05:05:08 c1 kernel: [4667592.000580] next_to_watchb0 Feb 11 05:05:08 c1 kernel: [4667592.000580] jiffies 458c4e59 Feb 11 05:05:08 c1 kernel: [4667592.000580] next_to_watch.status 0 Feb 11 05:05:08 c1 kernel: [4667592.000580] MAC Status 802a3 Feb 11 05:05:08 c1 kernel: [4667592.000580] PHY Status 792d Feb 11 05:05:08 c1 kernel: [4667592.000580] PHY 1000BASE-T Status 3800 Feb 11 05:05:08 c1 kernel: [4667592.000580] PHY Extended Status3000 Feb 11 05:05:08 c1 kernel: [4667592.000580] PCI Status 10
Bug#775236: gitweb breaks apache2 configuration - Invalid command 'AddHandler'
Package: gitweb Version: 1:2.1.4-2 Severity: normal Dear Maintainer, the upgrade of gitweb from version 1:2.1.3-1 to 1:2.1.4-2 broke the apache2 configuration on my system: apache2_invoke: Enable configuration gitweb apache2_reload: Your configuration is broken. Not reloading Apache 2 apache2_reload: AH00526: Syntax error on line 15 of /etc/apache2/conf-enabled/gitweb.conf: apache2_reload: Invalid command 'AddHandler', perhaps misspelled or defined by a module not included in the server configuration It looks like gitweb requires mod_mime to be enabled on the web server. At least my apache server starts again after enabling mod_mime. I had installed gitweb a while ago but hadn't set up the repositories yet. So I don't know if gitweb was working before. But at least it did not break the apache configuration. I don't know what severity is appropriate for this kind of bug. If you notice the error message on upgrade it's easy to fix by enabling mod_mime, but if the error slips unnoticed it'll break your web server on the next restart. So adjust the severity as you like. Regards Uwe -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gitweb depends on: ii apache2 [httpd] 2.4.10-9 ii dpkg1.17.23 ii git 1:2.1.4-2 ii lynx-cur2.8.9dev1-2+b1 ii mini-httpd [httpd] 1.19-9.3 ii perl5.20.1-4 Versions of packages gitweb recommends: ii libhttp-date-perl 6.02-1 Versions of packages gitweb suggests: ii apache2 [httpd-cgi] 2.4.10-9 pn git-doc none ii libcgi-fast-perl1:2.04-1 ii mini-httpd [httpd-cgi] 1.19-9.3 -- 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#772826: watchdog fails to upgrade
On Dec 16, Michael Meskes wrote:
What happens if you stop watchdog, does the process go away? Or if you happen
to reboot, does that change things? I'm wondering if the old process stays in
the way and thus may need to be killed manually. I have it that before, that
processes do not disappear despite being stopped via systemctl.
No, the process is stopped properly. systemctl start and stop
work as expected, only systemctl restart fails.
Stop / start:
# systemctl status watchdog
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
Active: active (running) since Thu 2014-12-11 14:44:09 CET; 4 days ago
Main PID: 30954 (watchdog)
CGroup: /system.slice/watchdog.service
└─30954 /usr/sbin/watchdog
Dec 11 14:44:09 grappa watchdog[30954]: starting daemon (5.14):
Dec 11 14:44:09 grappa watchdog[30954]: int=1s realtime=yes sync=no soft=no
mla=0 mem=0
Dec 11 14:44:09 grappa watchdog[30954]: ping: no machine to check
Dec 11 14:44:09 grappa watchdog[30954]: file: no file to check
Dec 11 14:44:09 grappa watchdog[30954]: pidfile: no server process to check
Dec 11 14:44:09 grappa watchdog[30954]: interface: no interface to check
Dec 11 14:44:09 grappa watchdog[30954]: temperature: no sensors to check
Dec 11 14:44:09 grappa watchdog[30954]: test=none(0) repair=none(0)
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
Dec 11 14:44:09 grappa watchdog[30954]: cannot set timeout 60 (errno = 22 =
'Invalid argument')
Dec 11 14:44:09 grappa watchdog[30954]: hardware watchdog identity: INTCAMT
# ps ax|grep watchdog
10 ?S 0:01 [watchdog/0]
11 ?S 0:02 [watchdog/1]
28719 pts/4S+ 0:00 grep watchdog
30954 ?SLs0:17 /usr/sbin/watchdog
# systemctl stop watchdog
# systemctl status watchdog
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
Active: inactive (dead) since Tue 2014-12-16 13:32:38 CET; 7s ago
Process: 28726 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false
(code=exited, status=1/FAILURE)
Main PID: 30954 (code=exited, status=0/SUCCESS)
Dec 11 14:44:09 grappa watchdog[30954]: file: no file to check
Dec 11 14:44:09 grappa watchdog[30954]: pidfile: no server process to check
Dec 11 14:44:09 grappa watchdog[30954]: interface: no interface to check
Dec 11 14:44:09 grappa watchdog[30954]: temperature: no sensors to check
Dec 11 14:44:09 grappa watchdog[30954]: test=none(0) repair=none(0)
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
Dec 11 14:44:09 grappa watchdog[30954]: cannot set timeout 60 (errno = 22 =
'Invalid argument')
Dec 11 14:44:09 grappa watchdog[30954]: hardware watchdog identity: INTCAMT
Dec 16 13:32:33 grappa watchdog[30954]: stopping daemon (5.14)
Dec 16 13:32:38 grappa systemd[1]: watchdog.service: control process exited,
code=exited status=1
Dec 16 13:32:38 grappa systemd[1]: Unit watchdog.service entered failed state.
# ps ax|grep watchdog
10 ?S 0:01 [watchdog/0]
11 ?S 0:02 [watchdog/1]
28746 pts/4S+ 0:00 grep watchdog
# systemctl start watchdog
# systemctl status watchdog
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
Active: active (running) since Tue 2014-12-16 13:32:59 CET; 20s ago
Process: 28726 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false
(code=exited, status=1/FAILURE)
Process: 28756 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
Process: 28753 ExecStartPre=/bin/sh -c [ -z ${watchdog_module} ] || [
${watchdog_module} = none ] || /sbin/modprobe $watchdog_module
(code=exited, status=0/SUCCESS)
Main PID: 28758 (watchdog)
CGroup: /system.slice/watchdog.service
└─28758 /usr/sbin/watchdog
Dec 16 13:32:59 grappa watchdog[28758]: starting daemon (5.14):
Dec 16 13:32:59 grappa watchdog[28758]: int=1s realtime=yes sync=no soft=no
mla=0 mem=0
Dec 16 13:32:59 grappa watchdog[28758]: ping: no machine to check
Dec 16 13:32:59 grappa watchdog[28758]: file: no file to check
Dec 16 13:32:59 grappa watchdog[28758]: pidfile: no server process to check
Dec 16 13:32:59 grappa watchdog[28758]: interface: no interface to check
Dec 16 13:32:59 grappa watchdog[28758]: temperature: no sensors to check
Dec 16 13:32:59 grappa watchdog[28758]: test=none(0) repair=none(0)
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
Dec 16 13:32:59 grappa watchdog[28758]: cannot set timeout 60 (errno = 22 =
'Invalid argument')
Dec 16 13:32:59 grappa watchdog[28758]: hardware watchdog identity: INTCAMT
# ps ax|grep watchdog
10 ?S 0:01 [watchdog/0]
11 ?S 0:02 [watchdog/1]
28758 ?SLs0:00 /usr/sbin/watchdog
28762 pts/4
Bug#772826: watchdog fails to upgrade
Hi Michael, here are my results from purging and reinstalling watchdog. There are some messages during the installation: /run/udev or .udevdb or .udev presence implies active udev. Aborting MAKEDEV invocation. update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Not sure if that means anything, but to me it sounds like an obsolete mechanism is used somewhere. I don't know what the intended behavior for /etc/default/watchdog is now. The changelog states: Changed rules file to make sure default file doesn't come back. But the package installation still references /etc/default/watchdog: Configuring watchdog Please specify whether stopping watchdog should start wd_keepalive to keep on triggering the watchdog device. This can be changed later by editing /etc/default/watchdog. Start wd_keepalive after stopping watchdog? And the file is recreated on package installation. At least the package database is cleaned up as expected by purging and reinstalling watchdog. I also have found out what causes systemctl restart watchdog to fail. When I disable run_wd_keepalive in /etc/default/watchdog anything works as expected (at least as far as I can see). But when I enable run_wd_keepalive the restart fails as reported before. Is restarting watchdog with wd_keepalive as a temporary replacement not supported? Regards Uwe PS: Sorry for not testing the reboot now, it's my desktop system and I have too many windows open at the moment. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772826: watchdog fails to upgrade
Package: watchdog
Version: 5.14-3
Severity: important
Dear Maintainer,
the watchdog package fails to upgrade (from version 5.14-2):
Setting up watchdog (5.14-3) ...
/run/udev or .udevdb or .udev presence implies active udev. Aborting MAKEDEV
invocation.
Job for watchdog.service canceled.
invoke-rc.d: initscript watchdog, action restart failed.
dpkg: error processing package watchdog (--configure):
subprocess installed post-installation script returned error exit status 1
Trying to recover at the end of the aptitude run fails too:
Errors were encountered while processing:
watchdog
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package. Trying to recover:
Setting up watchdog (5.14-3) ...
/run/udev or .udevdb or .udev presence implies active udev. Aborting MAKEDEV
invocation.
Also when I try to restart watchdog manually I end up with no
watchdog process running:
# systemctl status watchdog.service
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
Active: active (running) since Thu 2014-12-11 14:27:42 CET; 22s ago
Process: 29018 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false
(code=exited, status=1/FAILURE)
Process: 29042 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
Process: 29040 ExecStartPre=/bin/sh -c [ -z ${watchdog_module} ] || [
${watchdog_module} = none ] || /sbin/modprobe $watchdog_module
(code=exited, status=0/SUCCESS)
Main PID: 29044 (watchdog)
CGroup: /system.slice/watchdog.service
└─29044 /usr/sbin/watchdog
# systemctl restart watchdog.service
Job for watchdog.service canceled.
# systemctl status -l watchdog.service
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
Active: inactive (dead) since Thu 2014-12-11 14:30:15 CET; 33s ago
Process: 29639 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false
(code=exited, status=1/FAILURE)
Process: 29042 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
Process: 29040 ExecStartPre=/bin/sh -c [ -z ${watchdog_module} ] || [
${watchdog_module} = none ] || /sbin/modprobe $watchdog_module
(code=exited, status=0/SUCCESS)
Main PID: 29044 (code=exited, status=0/SUCCESS)
Dec 11 14:30:10 grappa watchdog[29044]: stopping daemon (5.14)
Dec 11 14:30:15 grappa systemd[1]: watchdog.service: control process exited,
code=exited status=1
Dec 11 14:30:15 grappa systemd[1]: Unit watchdog.service entered failed state.
Using only the start command works, but ends up with status
1/FAILURE for the service:
# systemctl start watchdog.service
# systemctl status -l watchdog.service
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service; enabled)
Active: active (running) since Thu 2014-12-11 14:31:35 CET; 15s ago
Process: 29639 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false
(code=exited, status=1/FAILURE)
Process: 29675 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec
/usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS)
Process: 29673 ExecStartPre=/bin/sh -c [ -z ${watchdog_module} ] || [
${watchdog_module} = none ] || /sbin/modprobe $watchdog_module
(code=exited, status=0/SUCCESS)
Main PID: 29678 (watchdog)
CGroup: /system.slice/watchdog.service
└─29678 /usr/sbin/watchdog
Dec 11 14:31:35 grappa watchdog[29678]: starting daemon (5.14):
Dec 11 14:31:35 grappa watchdog[29678]: int=1s realtime=yes sync=no soft=no
mla=0 mem=0
Dec 11 14:31:35 grappa watchdog[29678]: ping: no machine to check
Dec 11 14:31:35 grappa watchdog[29678]: file: no file to check
Dec 11 14:31:35 grappa watchdog[29678]: pidfile: no server process to check
Dec 11 14:31:35 grappa watchdog[29678]: interface: no interface to check
Dec 11 14:31:35 grappa watchdog[29678]: temperature: no sensors to check
Dec 11 14:31:35 grappa watchdog[29678]: test=none(0) repair=none(0)
alive=/dev/watchdog heartbeat=none to=root no_act=no force=no
Dec 11 14:31:35 grappa watchdog[29678]: cannot set timeout 60 (errno = 22 =
'Invalid argument')
Dec 11 14:31:35 grappa watchdog[29678]: hardware watchdog identity: INTCAMT
I'm not sure what the correct severity for this bug should be
(I would consider it RC, so serious?). Please adjust the
severity as needed.
Regards
Uwe
PS: The old config file /etc/default/watchdog seems not to be
properly removed from the package, dpkg -s still lists it (as
obsolete). See also the Configuration Files section below.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU
Bug#766028: wine32 segfault
I also get the SIGUSR1 signal sometimes with wine version 1.6.2-10. This seems to be a timing issue and not a difference between the wine versions 1.6.2-10 and 1.6.2-11. Please ignore the remarks about the signal behavior in my last mail. Sorry for the confusion! Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766028: wine32 segfault
Hi
This bug is not fixed in wine32 version 1.6.2-17 for me too. Only
wine is affected by the bug, but not wine-development.
On Dec 07, Michael Gilbert wrote:
The original report indicates that the nvidia proprietary driver was
used. Is this true for everyone running into the problem?
I also use the nvidia binary driver.
If so, can you try nouveau instead?
The nouveau driver does not support my hardware configuration
(2 GPUs with 3 screens), at least the last time I tried it.
People which need Direct3D or OpenGL support in wine usually
play games with it and need the better performance of the nvidia
binary driver. So switching to the nouveau driver is often not
an option.
To narrow down the problem I have tested several wine32 versions.
The bug has been introduced between version 1.6.2-10 and version
1.6.2-11. It is sufficient to downgrade the wine32 package and no
other of the wine packages.
When I understand the package version numbers in Debian correctly
the wine32 package versions 1.6.2-10 and 1.6.2-11 are produced
from the same upstream sources. So the bug has been introduced in
the Debian part of the wine32 package between version 1.6.2-10
and version 1.6.2-11. That should considerably narrow things
down.
It's also suspect that wine does not segfault when I run it
inside of gdb. Maybe something in the build process of the
wine32 package has changed between these two versions and causes
the problem.
When I run wine32 in gdb the process gets a signal SIGUSR1 in
wine32 version 1.6.2-11 which I don't see in version 1.6.2-10:
Program received signal SIGUSR1, User defined signal 1.
The gdb logs for both versions are attached below.
I don't know why this signal has been introduced and what it's
used for, but it may cause the segfault when it's not caught
properly.
I hope this helps a bit to narrow down this bug.
Regards
Uwe
wine32 version 1.6.2-11:
$ gdb wine32
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
[..]
Reading symbols from wine32...(no debugging symbols found)...done.
(gdb) run dxdiag
Starting program: /usr/bin/wine32 dxdiag
[Thread debugging using libthread_db enabled]
Using host libthread_db library
/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1.
[New Thread 0xf7c27b40 (LWP 10161)]
[Thread 0xf7c27b40 (LWP 10161) exited]
process 10157 is executing new program:
/usr/lib/i386-linux-gnu/wine/bin/wine-preloader
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x0030
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:win:EnumDisplayDevicesW ((null),0,0x32d6e4,0x), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32d504,0x), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid
{aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category
{33d9a760-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category
{33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
[New LWP 10192]
Program received signal SIGUSR1, User defined signal 1.
[Switching to LWP 10192]
0xf7ffd430 in ?? ()
(gdb) cont
Continuing.
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category
{cc7bfb41-f175-11d1-a392-00e0291f3959} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category
{cc7bfb46-f175-11d1-a392-00e0291f3959} not found
fixme:dxdiag:wWinMain Information dialog is not implemented
[LWP 10192 exited]
[Inferior 1 (process 10157) exited normally]
(gdb) quit
wine32 version 1.6.2-10:
$ gdb wine32
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
[..]
Reading symbols from wine32...(no debugging symbols found)...done.
(gdb) run dxdiag
Starting program: /usr/bin/wine32 dxdiag
[Thread debugging using libthread_db enabled]
Using host libthread_db library
/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1.
[New Thread 0xf7c27b40 (LWP 8686)]
[Thread 0xf7c27b40 (LWP 8686) exited]
process 8682 is executing new program:
/usr/lib/i386-linux-gnu/wine/bin/wine-preloader
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x0030
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:win:EnumDisplayDevicesW ((null),0,0x32d6e4,0x), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x32d504,0x), stub!
fixme:ddraw:ddraw7_Initialize Ignoring guid
{aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category
{33d9a760-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category
{33d9a761-90c8-11d0-bd43-00a0c911ce86} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category
{cc7bfb41-f175-11d1-a392-00e0291f3959} not found
fixme:devenum:DEVENUM_ICreateDevEnum_CreateClassEnumerator Category
{cc7bfb46-f175-11d1-a392-00e0291f3959} not found
fixme:dxdiag:wWinMain Information dialog is not implemented
[Inferior 1 (process 8682) exited normally]
(gdb) quit
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Bug#771141: wpasupplicant: Upgrade to wpasupplicant 2 breaks WLAN
Package: wpasupplicant
Version: 2.3-1
Severity: important
Dear Maintainer,
after upgrading wpasupplicant from version 1.1-1 to version 2.3-1
wpasupplicant fails to establish a WLAN connection:
# wpa_supplicant -dd -ieth1 -c/tmp/wpa_supplicant.conf
wpa_supplicant v2.3
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'eth1' conf '/tmp/wpa_supplicant.conf' driver 'default'
ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/tmp/wpa_supplicant.conf' - '/tmp/wpa_supplicant.conf'
Reading configuration file '/tmp/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
Line: 3 - start of a new network block
ssid - hexdump_ascii(len=4):
74 65 73 74 test
PSK - hexdump(len=32): [REMOVED]
Priority group 0
id=0 ssid='test'
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
rfkill: initial event: idx=1 type=2 op=0 soft=0 hard=0
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Driver does not support authentication/association or connect commands
nl80211: Remove monitor interface: refcount=0
netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6
(IF_OPER_UP)
nl80211: Set mode ifindex 3 iftype 2 (STATION)
eth1: Failed to initialize driver interface
Failed to add interface eth1
eth1: Cancelling scan request
eth1: Cancelling authentication timeout
# cat /tmp/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
network={
ssid=test
#psk=12345678
psk=fe727aa8b64ac9b3f54c72432da14faed933ea511ecab15bbc6c52e7522f709a
}
The system is a HP Compaq nx8220. WLAN device:
02:04.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2]
Network Connection (rev 05)
Loaded kernel modules: ipw2200, libipw, cfg80211, lib80211
Almost all WLANs require WPA and a notebook without working WLAN
is rather useless, hence severity important.
I don't know what other information could be useful so please
tell me if you need anything else.
Regards
Uwe
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages wpasupplicant depends on:
ii adduser 3.113+nmu3
ii libc6 2.19-13
ii libdbus-1-3 1.8.10-1
ii libnl-3-200 3.2.24-2
ii libnl-genl-3-200 3.2.24-2
ii libpcsclite1 1.8.13-1
ii libreadline6 6.3-8+b1
ii libssl1.0.0 1.0.1j-1
ii lsb-base 4.1+Debian13+nmu1
wpasupplicant recommends no packages.
Versions of packages wpasupplicant suggests:
pn libengine-pkcs11-openssl none
ii wpagui2.3-1
-- 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#768168: watchdog does not start at boot
On Nov 11, Michael Biebl wrote: Please boot with systemd.log_level=debug on the kernel command line, the attach the output of journalctl -alb I guess these are the relevant lines: Found ordering cycle on graphical.target/start Found dependency on multi-user.target/start Found dependency on watchdog.service/start Found dependency on graphical.target/start Breaking ordering cycle by deleting job watchdog.service/start The part of the journal after hardware initialization is attached. Regards Uwe Nov 12 14:02:21 grappa kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) Nov 12 14:02:21 grappa systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpuset of type cgroup with options cpuset. Nov 12 14:02:21 grappa systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpu,cpuacct of type cgroup with options cpu,cpuacct. Nov 12 14:02:21 grappa systemd[1]: Mounting cgroup to /sys/fs/cgroup/devices of type cgroup with options devices. Nov 12 14:02:21 grappa systemd[1]: Mounting cgroup to /sys/fs/cgroup/freezer of type cgroup with options freezer. Nov 12 14:02:21 grappa systemd[1]: Mounting cgroup to /sys/fs/cgroup/net_cls,net_prio of type cgroup with options net_cls,net_prio. Nov 12 14:02:21 grappa systemd[1]: Mounting cgroup to /sys/fs/cgroup/blkio of type cgroup with options blkio. Nov 12 14:02:21 grappa systemd[1]: Mounting cgroup to /sys/fs/cgroup/perf_event of type cgroup with options perf_event. Nov 12 14:02:21 grappa systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR) Nov 12 14:02:21 grappa systemd[1]: Detected architecture 'x86-64'. Nov 12 14:02:21 grappa systemd[1]: Your kernel apparently lacks built-in autofs4 support. Might be a good idea to compile it in. We'll now try to work around this by loading the module... Nov 12 14:02:21 grappa kernel: Switched to clocksource tsc Nov 12 14:02:21 grappa systemd[1]: Inserted module 'autofs4' Nov 12 14:02:21 grappa systemd[1]: Set hostname to grappa. Nov 12 14:02:21 grappa systemd[1]: /usr appears to be on its own filesytem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information. Nov 12 14:02:21 grappa systemd[1]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd. Nov 12 14:02:21 grappa systemd[1]: Installed release agent. Nov 12 14:02:21 grappa systemd[1]: Set up TFD_TIMER_CANCEL_ON_SET timerfd. Nov 12 14:02:21 grappa systemd[145]: Spawned /lib/systemd/system-generators/systemd-sysv-generator as 146. Nov 12 14:02:21 grappa systemd[145]: Spawned /lib/systemd/system-generators/systemd-cryptsetup-generator as 147. Nov 12 14:02:21 grappa systemd[145]: Spawned /lib/systemd/system-generators/systemd-insserv-generator as 148. Nov 12 14:02:21 grappa systemd[145]: Spawned /lib/systemd/system-generators/systemd-getty-generator as 149. Nov 12 14:02:21 grappa systemd[145]: Spawned /lib/systemd/system-generators/systemd-rc-local-generator as 150. Nov 12 14:02:21 grappa systemd[145]: Spawned /lib/systemd/system-generators/systemd-fstab-generator as 151. Nov 12 14:02:21 grappa systemd[145]: Spawned /lib/systemd/system-generators/systemd-gpt-auto-generator as 152. Nov 12 14:02:21 grappa systemd[145]: Spawned /lib/systemd/system-generators/systemd-system-update-generator as 153. Nov 12 14:02:21 grappa systemd[145]: Spawned /lib/systemd/system-generators/systemd-debug-generator as 154. Nov 12 14:02:21 grappa kernel: random: nonblocking pool is initialized Nov 12 14:02:21 grappa systemd[145]: /lib/systemd/system-generators/systemd-sysv-generator succeeded. Nov 12 14:02:21 grappa systemd[145]: /lib/systemd/system-generators/systemd-cryptsetup-generator succeeded. Nov 12 14:02:21 grappa systemd[145]: /lib/systemd/system-generators/systemd-insserv-generator succeeded. Nov 12 14:02:21 grappa systemd[145]: /lib/systemd/system-generators/systemd-getty-generator succeeded. Nov 12 14:02:21 grappa systemd[145]: /lib/systemd/system-generators/systemd-rc-local-generator succeeded. Nov 12 14:02:21 grappa systemd[145]: /lib/systemd/system-generators/systemd-fstab-generator succeeded. Nov 12 14:02:21 grappa systemd[145]: /lib/systemd/system-generators/systemd-gpt-auto-generator succeeded. Nov 12 14:02:21 grappa systemd[145]: /lib/systemd/system-generators/systemd-system-update-generator succeeded. Nov 12 14:02:21 grappa systemd[145]: /lib/systemd/system-generators/systemd-debug-generator succeeded. Nov 12 14:02:21 grappa systemd[1]: /lib/systemd/system-generators succeeded. Nov 12 14:02:21 grappa systemd[1]: Looking for unit files in (higher priority first): Nov 12 14:02:21 grappa systemd[1]: /etc/systemd/system Nov 12 14:02:21 grappa systemd[1]: /run/systemd/system Nov 12 14:02:21 grappa systemd[1]: /run/systemd/generator
Bug#768168: watchdog does not start at boot
On Nov 10, Michael Meskes wrote: Could you run 'ls /lib/systemd/system/graphical.target.wants/' please? # ls /lib/systemd/system/graphical.target.wants/ systemd-update-utmp-runlevel.service # cat /lib/systemd/system/graphical.target.wants/systemd-update-utmp-runlevel.service # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. [Unit] Description=Update UTMP about System Runlevel Changes Documentation=man:systemd-update-utmp.service(8) man:utmp(5) DefaultDependencies=no RequiresMountsFor=/var/log/wtmp Conflicts=shutdown.target Requisite=systemd-update-utmp.service After=systemd-update-utmp.service After=runlevel1.target runlevel2.target runlevel3.target runlevel4.target runlevel5.target Before=shutdown.target [Service] Type=oneshot ExecStart=/lib/systemd/systemd-update-utmp runlevel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768168: watchdog does not start at boot
On Nov 10, Michael Meskes wrote: Could you tell me which other services you have included in graphical.target? On my system the current setup works flawlessly. Could very well be that I made a mistake when setting the After: fields. It's the standard file from the systemd installation, no manual changes. /lib/systemd/system/graphical.target: # This file is part of systemd. # # systemd is free software; you can redistribute it and/or # modify it # under the terms of the GNU Lesser General Public License as # published by # the Free Software Foundation; either version 2.1 of the # License, or # (at your option) any later version. [Unit] Description=Graphical Interface Documentation=man:systemd.special(7) Requires=multi-user.target After=multi-user.target Conflicts=rescue.target Wants=display-manager.service AllowIsolate=yes There's no graphical display manager installed on the system though, in case that matters. The according line from the log is: systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768452: linux-image-3.16-3-amd64: system locks up every one or two days since upgrade to kernel 3.16
Package: src:linux Version: 3.16.5-1 Severity: important Dear Maintainer, since I have upgraded my system to kernel 3.16 it freezes every one or two days. Neither keyboard nor network access work. Even sysrq keys do not work anymore. I have to power off the machine. The freeze always seems to happen during the nightly backup session (rsnapshot connecting via ssh from a backup server), at least these are the last log messages I get: Nov 07 05:43:52 grappa sshd[2860]: Accepted publickey for root from 172.18.1.1 port 34726 ssh2: RSA xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx Nov 07 05:43:52 grappa sshd[2860]: pam_unix(sshd:session): session opened for user root by (uid=0) Nov 07 05:43:52 grappa systemd-logind[891]: New session 1966 of user root. Nov 07 05:43:52 grappa systemd[2870]: pam_unix(systemd-user:session): session opened for user root by (uid=0) Nov 07 05:43:52 grappa systemd[2870]: Starting Paths. Nov 07 05:43:52 grappa systemd[2870]: Reached target Paths. Nov 07 05:43:52 grappa systemd[2870]: Starting Timers. Nov 07 05:43:52 grappa systemd[2870]: Reached target Timers. Nov 07 05:43:52 grappa systemd[2870]: Starting Sockets. Nov 07 05:43:52 grappa systemd[2870]: Reached target Sockets. Nov 07 05:43:52 grappa systemd[2870]: Starting Basic System. Nov 07 05:43:52 grappa systemd[2870]: Reached target Basic System. Nov 07 05:43:52 grappa systemd[2870]: Starting Default. Nov 07 05:43:52 grappa systemd[2870]: Reached target Default. Nov 07 05:43:52 grappa systemd[2870]: Startup finished in 7ms. Regards Uwe -- Package-specific info: ** Version: Linux version 3.16-3-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-12) ) #1 SMP Debian 3.16.5-1 (2014-10-10) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16-3-amd64 root=UUID=---- ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 10.964342] usb 7-4: New USB device found, idVendor=0424, idProduct=2514 [ 10.964347] usb 7-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 10.964638] hub 7-4:1.0: USB hub found [ 10.964708] hub 7-4:1.0: 4 ports detected [ 10.980199] input: HP WMI hotkeys as /devices/virtual/input/input11 [ 11.094389] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [ 11.094421] iTCO_wdt: Found a ICH9 TCO device (Version=2, TCOBASE=0xf860) [ 11.094476] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 11.336041] usb 8-6: new high-speed USB device number 3 using ehci-pci [ 11.371056] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4 [ 11.377183] sdb: unknown partition table [ 11.404821] Adding 1959892k swap on /dev/sda10. Priority:-1 extents:1 across:1959892k FS [ 11.485695] usb 8-6: New USB device found, idVendor=0bda, idProduct=0111 [ 11.485700] usb 8-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 11.485703] usb 8-6: Product: USB2.0-CRW [ 11.485706] usb 8-6: Manufacturer: Generic [ 11.485708] usb 8-6: SerialNumber: 2002153705700 [ 11.545068] media: Linux media interface: v0.10 [ 11.564525] Linux video capture interface: v2.00 [ 11.574275] usb-storage 8-6:1.0: USB Mass Storage device detected [ 11.574335] scsi4 : usb-storage 8-6:1.0 [ 11.574399] usbcore: registered new interface driver usb-storage [ 11.584017] sdb: unknown partition table [ 11.670878] EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 11.699174] usbcore: registered new interface driver snd-usb-audio [ 11.874584] uvcvideo: Found UVC 1.00 device Webcam C170 (046d:082b) [ 11.880101] input: Webcam C170 as /devices/pci:00/:00:1a.7/usb7/7-1/7-1:1.0/input/input12 [ 11.880179] usbcore: registered new interface driver uvcvideo [ 11.880180] USB Video Class driver (1.1.1) [ 11.928050] usb 4-1: new full-speed USB device number 2 using uhci_hcd [ 12.090059] usb 4-1: New USB device found, idVendor=0430, idProduct=100e [ 12.090064] usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 12.093101] hub 4-1:1.0: USB hub found [ 12.095048] hub 4-1:1.0: 4 ports detected [ 12.300244] usb 7-4.2: new low-speed USB device number 4 using ehci-pci [ 12.396348] usb 7-4.2: New USB device found, idVendor=046d, idProduct=c016 [ 12.396354] usb 7-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 12.396357] usb 7-4.2: Product: Optical USB Mouse [ 12.396359] usb 7-4.2: Manufacturer: Logitech [ 12.477052] usb 4-1.4: new full-speed USB device number 3 using uhci_hcd [ 12.565277] hidraw: raw HID events driver (C) Jiri Kosina [ 12.568555] usbcore: registered new interface driver usbhid [ 12.568557] usbhid: USB HID core driver [ 12.578586] scsi 4:0:0:0: Direct-Access Generic- Compact Flash1.00 PQ: 0 ANSI: 0 CCS [ 12.579671] input: Logitech Optical USB Mouse as
Bug#511812: Is this still a problem?
I do not have an ISDN connection anymore. If nobody else cares about this bug you may close it. Thanks Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768168: watchdog does not start at boot
Package: watchdog Version: 5.14-1 Severity: important Dear Maintainer, since the last upgrade watchdog does not get started at boot time: Nov 05 16:42:52 grappa systemd[1]: Found ordering cycle on graphical.target/start Nov 05 16:42:52 grappa systemd[1]: Breaking ordering cycle by deleting job watchdog.service/start Nov 05 16:42:52 grappa systemd[1]: Job watchdog.service/start deleted to break ordering cycle starting with graphical.target/start Starting the service manually works. The only modification in the config files I have done manually is to enable the watchdog-device. Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages watchdog depends on: ii debconf [debconf-2.0] 1.5.53 ii init-system-helpers1.21 ii libc6 2.19-12 ii lsb-base 4.1+Debian13+nmu1 ii makedev2.3.1-93 ii udev 215-5+b1 watchdog recommends no packages. watchdog suggests no packages. -- Configuration Files: /etc/default/watchdog changed: run_wd_keepalive=1 run_watchdog=1 watchdog_module=none watchdog_options= /etc/watchdog.conf changed: watchdog-device = /dev/watchdog realtime= yes priority= 1 -- debconf information: * watchdog/run: true * watchdog/module: none * watchdog/restart: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754401: gource starts on the wrong X11 screen
Control: retitle -1 SDL2 programs start on the wrong X11 screen Control: reassign -1 libsdl2-2.0-0 2.0.2+dfsg1-4 Control: severity -1 important Control: affects -1 + gource Thanks Andrew! I reassign the bug to libsdl2-2.0-0. Severity is increased to important as it's more general and affects all SDL2 programs and prevents them from beeing started on any of the screens but the first one, which makes having multiple screens quite pointless. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759483: AnotherDNS: Undefined subroutine Net::DNS::PACKETSZ
Package: smokeping Version: 2.6.9-1 Severity: normal Dear Maintainer, the probe AnotherDNS fails with the error message: smokeping[21463]: Undefined subroutine Net::DNS::PACKETSZ called at /usr/share/perl5/Smokeping/probes/AnotherDNS.pm line 98. This is probably caused by an upgrade of package libnet-dns-perl to version 0.79-1. Net::DNS::PACKETSZ doesn't exist anymore in that package version. PACKETSZ is defined as a constant now. Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages smokeping depends on: ii adduser 3.113+nmu3 ii debianutils 4.4 ii fping 3.10-2 ii libcgi-fast-perl5.20.0-4 ii libconfig-grammar-perl 1.10-2 ii libdigest-hmac-perl 1.03+dfsg-1 ii libjs-cropper 1.2.2-1 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii librrds-perl1.4.8-1.1+b1 ii libsnmp-session-perl1.13-1.1 ii liburi-perl 1.64-1 ii libwww-perl 6.08-1 ii lsb-base4.1+Debian13 ii perl5.20.0-4 ii ucf 3.0030 Versions of packages smokeping recommends: ii apache2 2.4.10-1+b1 ii apache2-bin [httpd-cgi] 2.4.10-1+b1 ii dnsutils 1:9.9.5.dfsg-4 ii echoping 6.0.2-8 ii libsocket6-perl 0.25-1+b1 ii mini-httpd [httpd-cgi] 1.19-9.3 Versions of packages smokeping suggests: ii curl7.37.1-1 pn libauthen-radius-perl none ii libio-socket-ssl-perl 1.997-2 ii libnet-dns-perl 0.79-1 ii libnet-ldap-perl1:0.6400+dfsg-1 ii libnet-telnet-perl 3.04-1 ii openssh-client 1:6.6p1-7 ii postfix [mail-transport-agent] 2.11.1-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759487: smokeping: reporting a bug tries to include private data into the bug report
Package: smokeping Version: 2.6.9-1 Severity: normal Dear Maintainer, when filing a bug report against smokeping the reportbug tool tries to include private data into the (public) bug report: /etc/smokeping/smokeping_secrets [Errno 13] Permission denied: u'/etc/smokeping/smokeping_secrets' It fails because of missing permissions, but it shouldn't event try to do so. I don't know if this problem is specific to smokeping or if it belongs to reportbug. Please reassign the bug if necessary. Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages smokeping depends on: ii adduser 3.113+nmu3 ii debianutils 4.4 ii fping 3.10-2 ii libcgi-fast-perl5.20.0-4 ii libconfig-grammar-perl 1.10-2 ii libdigest-hmac-perl 1.03+dfsg-1 ii libjs-cropper 1.2.2-1 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii librrds-perl1.4.8-1.1+b1 ii libsnmp-session-perl1.13-1.1 ii liburi-perl 1.64-1 ii libwww-perl 6.08-1 ii lsb-base4.1+Debian13 ii perl5.20.0-4 ii ucf 3.0030 Versions of packages smokeping recommends: ii apache2 2.4.10-1+b1 ii apache2-bin [httpd-cgi] 2.4.10-1+b1 ii dnsutils 1:9.9.5.dfsg-4 ii echoping 6.0.2-8 ii libsocket6-perl 0.25-1+b1 ii mini-httpd [httpd-cgi] 1.19-9.3 Versions of packages smokeping suggests: ii curl7.37.1-1 pn libauthen-radius-perl none ii libio-socket-ssl-perl 1.997-2 ii libnet-dns-perl 0.79-1 ii libnet-ldap-perl1:0.6400+dfsg-1 ii libnet-telnet-perl 3.04-1 ii openssh-client 1:6.6p1-7 ii postfix [mail-transport-agent] 2.11.1-1 -- Configuration Files: /etc/smokeping/config.d/Alerts changed [not included] /etc/smokeping/config.d/Database changed [not included] /etc/smokeping/config.d/General changed [not included] /etc/smokeping/config.d/Presentation changed [not included] /etc/smokeping/config.d/Probes changed [not included] /etc/smokeping/config.d/Targets changed [not included] /etc/smokeping/smokeping_secrets [Errno 13] Permission denied: u'/etc/smokeping/smokeping_secrets' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758215: clusterssh: console is always put into top-left corner when using option console_position
Package: clusterssh Version: 4.03.02-1 Severity: normal Dear Maintainer, clusterssh positions the console window always in the top-left corner (+0+0) when I use the option console_position, regardless what coordinates I use. Example: ~/.clusterssh/config reduced to one line console_position = +100+100 The debug log is attached below. I use a multi-head X server configuration (displays :0.0 and :0.1), in case that matters. The behavior is the same on both screens. Regards Uwe $ cssh --debug 4 teq vir Loading in config file: /home/uwe/.clusterssh/config Loading in config file: /home/uwe/.clusterssh/config console_position=+100+100 VERSION: 4.03_02 Fetching font size Done with font size Loading keymaps and keycodes Unknown keycode 269025042 Unknown keycode 269025042 Unknown keycode 269025041 Unknown keycode 269025041 Unknown keycode 269025043 Unknown keycode 269025043 Unknown keycode 269025066 Unknown keycode 269025066 Unknown keycode 269025098 Unknown keycode 269025098 Unknown keycode 268828528 Unknown keycode 268828528 Unknown keycode 268828529 Unknown keycode 268828529 Unknown keycode 269025111 Unknown keycode 269025111 Unknown keycode 269025131 Unknown keycode 269025131 Unknown keycode 269025133 Unknown keycode 269025133 Unknown keycode 269025112 Unknown keycode 269025112 Unknown keycode 269025125 Unknown keycode 269025125 Unknown keycode 269025053 Unknown keycode 269025053 Unknown keycode 269025071 Unknown keycode 269025071 Unknown keycode 269025067 Unknown keycode 269025067 Unknown keycode 269025117 Unknown keycode 269025117 Unknown keycode 269025147 Unknown keycode 269025147 Unknown keycode 269025162 Unknown keycode 269025162 Unknown keycode 269025089 Unknown keycode 269025089 Unknown keycode 269025090 Unknown keycode 269025090 Unknown keycode 269025070 Unknown keycode 269025070 Unknown keycode 269025114 Unknown keycode 269025114 Unknown keycode 269025069 Unknown keycode 269025069 Unknown keycode 269025140 Unknown keycode 269025140 Unknown keycode 269025151 Unknown keycode 269025151 Unknown keycode 269025049 Unknown keycode 269025049 Unknown keycode 269025072 Unknown keycode 269025072 Unknown keycode 269025075 Unknown keycode 269025075 Unknown keycode 269025062 Unknown keycode 269025062 Unknown keycode 269025063 Unknown keycode 269025063 Unknown keycode 269025068 Unknown keycode 269025068 Unknown keycode 269025068 Unknown keycode 269025068 Unknown keycode 269025068 Unknown keycode 269025068 Unknown keycode 269025047 Unknown keycode 269025047 Unknown keycode 269025044 Unknown keycode 269025073 Unknown keycode 269025044 Unknown keycode 269025073 Unknown keycode 269025046 Unknown keycode 269025046 Unknown keycode 269025045 Unknown keycode 269025068 Unknown keycode 269025045 Unknown keycode 269025068 Unknown keycode 269025052 Unknown keycode 269025052 Unknown keycode 269025086 Unknown keycode 269025086 Unknown keycode 269025134 Unknown keycode 269025134 Unknown keycode 269025153 Unknown keycode 269025153 Unknown keycode 269025048 Unknown keycode 269025048 Unknown keycode 269025139 Unknown keycode 269025139 Unknown keycode 269025110 Unknown keycode 269025110 Unknown keycode 269025144 Unknown keycode 269025144 Unknown keycode 269025145 Unknown keycode 269025145 Unknown keycode 269025128 Unknown keycode 269025128 Unknown keycode 269025153 Unknown keycode 269025153 Unknown keycode 269025093 Unknown keycode 269025093 Unknown keycode 269025094 Unknown keycode 269025094 Unknown keycode 269025095 Unknown keycode 269025095 Unknown keycode 269025096 Unknown keycode 269025096 Unknown keycode 269025097 Unknown keycode 269025097 Unknown keycode 269025202 Unknown keycode 269025202 Unknown keycode 269025193 Unknown keycode 269025193 Unknown keycode 269025200 Unknown keycode 269025200 Unknown keycode 269025201 Unknown keycode 269025201 Unknown keycode 269025044 Unknown keycode 269025044 Unknown keycode 269025073 Unknown keycode 269025073 Unknown keycode 269025091 Unknown keycode 269025091 Unknown keycode 269025092 Unknown keycode 269025092 Unknown keycode 269025099 Unknown keycode 269025099 Unknown keycode 269025191 Unknown keycode 269025191 Unknown keycode 269025110 Unknown keycode 269025110 Unknown keycode 269025044 Unknown keycode 269025044 Unknown keycode 269025175 Unknown keycode 269025175 Unknown keycode 269025167 Unknown keycode 269025167 Unknown keycode 269025049 Unknown keycode 269025049 Unknown keycode 269025166 Unknown keycode 269025166 Unknown keycode 269025051 Unknown keycode 269025051 Unknown keycode 269025119 Unknown keycode 269025119 Unknown keycode 269025084 Unknown keycode 269025084 Unknown keycode 269025118 Unknown keycode 269025118 Unknown keycode 269025078 Unknown keycode 269025078 Unknown keycode 269025027 Unknown keycode 269025027 Unknown keycode 269025026 Unknown keycode 269025026 Unknown keycode 269025074 Unknown keycode 269025074 Unknown keycode 269025113 Unknown keycode 269025113 Unknown keycode 269025028 Unknown keycode 269025028 Unknown keycode 269025030 Unknown keycode 269025030
Bug#754401: gource starts on the wrong X11 screen
Package: gource Version: 0.42-1+b1 Severity: normal Dear Maintainer, I have 3 screens on my X server (:0.0, :0.1 and :0.2). Regardless on what screen I start gource it always opens its window on the first screen (:0.0). But it should open its window on the same screen where it has been started, e.g. when I start gource on screen :0.2 it should open its window on screen :0.2. Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gource depends on: ii fonts-freefont-ttf 20120503-4 ii libboost-filesystem1.55.0 1.55.0+dfsg-2 ii libboost-system1.55.0 1.55.0+dfsg-2 ii libc6 2.19-4 ii libfreetype6 2.5.2-1 ii libgcc11:4.9.0-7 ii libgl1-mesa-glx [libgl1] 10.2.2-1 ii libglew1.101.10.0-3 ii libglu1-mesa [libglu1] 9.0.0-2 ii libpcre3 1:8.31-5 ii libpng12-0 1.2.50-1 ii libsdl2-2.0-0 2.0.2+dfsg1-4 ii libsdl2-image-2.0-02.0.0+dfsg-3+b2 ii libstdc++6 4.9.0-7 ii libtinyxml2.6.22.6.2-2 gource recommends no packages. gource 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#751398: linux-image-3.14-1-686-pae: kernel switches off cooling on HP Compaq nx8220
Package: src:linux Version: 3.14.4-1 Severity: important Dear Maintainer, kernel 3.14 switches off cooling on my laptop. The fans do not start even when the temperature reported by acpi raises above 100 °C (I've stopped there to not damage the hardware). There is no fan controlling software like lm-sensors/fancontrol installed. Booting with kernel 3.2 fixes the problem, fans work normal and start to work at about 50 to 60 °C. Regards Uwe -- Package-specific info: ** Version: Linux version 3.14-1-686-pae (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-21) ) #1 SMP Debian 3.14.4-1 (2014-05-13) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.14-1-686-pae root=UUID=32077a82-12e5-4f22-a606-1dd16fcd68c1 ro quiet ** Not tainted ** Kernel log: [6.881925] radeon :01:00.0: radeon: using MSI. [6.881957] [drm] radeon: irq initialized. [6.881974] [drm] Loading R300 Microcode [6.918172] radeon :01:00.0: firmware: direct-loading firmware radeon/R300_cp.bin [6.918525] [drm] radeon: ring at 0xA0001000 [6.918553] [drm] ring test succeeded in 0 usecs [6.918849] [drm] ib test succeeded in 0 usecs [6.920600] [drm] Panel ID String: LPL [6.920606] [drm] Panel Size 1680x1050 [6.941407] [drm] radeon legacy LVDS backlight initialized [6.941413] [drm] Radeon Display Connectors [6.941418] [drm] Connector 0: [6.941422] [drm] VGA-1 [6.941429] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [6.941432] [drm] Encoders: [6.941437] [drm] CRT1: INTERNAL_DAC1 [6.941441] [drm] Connector 1: [6.941445] [drm] DVI-D-1 [6.941448] [drm] HPD1 [6.941454] [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 [6.941457] [drm] Encoders: [6.941461] [drm] DFP1: INTERNAL_TMDS1 [6.941465] [drm] Connector 2: [6.941469] [drm] LVDS-1 [6.941475] [drm] DDC: 0x68 0x68 0x68 0x68 0x68 0x68 0x68 0x68 [6.941478] [drm] Encoders: [6.941482] [drm] LCD1: INTERNAL_LVDS [6.941486] [drm] Connector 3: [6.941490] [drm] SVIDEO-1 [6.941493] [drm] Encoders: [6.941496] [drm] TV1: INTERNAL_DAC2 [7.012097] [drm] fb mappable at 0xC00C [7.012100] [drm] vram apper at 0xC000 [7.012102] [drm] size 7057408 [7.012103] [drm] fb depth is 24 [7.012105] [drm]pitch is 6720 [7.012291] fbcon: radeondrmfb (fb0) is primary device [7.035649] input: HP WMI hotkeys as /devices/virtual/input/input14 [7.061201] Console: switching to colour frame buffer device 210x65 [7.085861] radeon :01:00.0: fb0: radeondrmfb frame buffer device [7.085864] radeon :01:00.0: registered panic notifier [7.087335] [drm] Initialized radeon 2.37.0 20080528 for :01:00.0 on minor 0 [7.320066] intel8x0_measure_ac97_clock: measured 55416 usecs (2670 samples) [7.320076] intel8x0: clocking to 48000 [7.404869] psmouse serio4: synaptics: Touchpad model: 1, fw: 6.2, id: 0x25a0b1, caps: 0xa04793/0x30/0x0, board id: 71, fw id: 35334 [7.404886] psmouse serio4: synaptics: serio: Synaptics pass-through port at isa0060/serio4/input0 [7.444144] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input12 [8.259747] cfg80211: World regulatory domain updated: [8.259757] cfg80211: DFS Master region: unset [8.259762] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [8.259769] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm) [8.259774] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm) [8.259780] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm) [8.259785] cfg80211: (517 KHz - 525 KHz @ 8 KHz), (N/A, 2000 mBm) [8.259790] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm) [8.259795] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm) [9.381183] Adding 979960k swap on /dev/sda2. Priority:-1 extents:1 across:979960k [9.420517] EXT4-fs (sda3): re-mounted. Opts: (null) [9.889756] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro [ 10.409729] usbcore: registered new interface driver usbserial [ 10.410242] usbcore: registered new interface driver usbserial_generic [ 10.410733] usbserial: USB Serial support registered for generic [ 10.412375] usbcore: registered new interface driver visor [ 10.412865] usbserial: USB Serial support registered for Handspring Visor / Palm OS [ 10.413353] usbserial: USB Serial support registered for Sony Clie 5.0 [ 10.413393] usbserial: USB Serial support registered for Sony Clie 3.5 [ 10.473684] fuse init (API version 7.22) [ 11.244164] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: errors=remount-ro [ 13.431338] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.396350] tg3 :10:00.0 eth0: Link is up at 1000 Mbps, full duplex [ 16.396362]
Bug#724827: wifi works again with kernel 3.14
Hi, the wifi does not get disabled anymore with kernel 3.14 on my HP Compaq nx8220 (which did get disabled with kernel versions at least from 3.10 to 3.13). But maybe the issue has not really been fixed and things are only going wrong at a different place now. wifi works with kernel 3.14, but cooling gets disabled (see bug #751398). Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746735: exfat-fuse: df -i shows wrong inode numbers on a mounted exfat file system
Package: exfat-fuse Version: 1.0.1-1 Severity: normal Dear Maintainer, when I try to display the number of free inodes on a mounted exfat file system df -i shows wrong numbers: # df -i /mnt Filesystem Inodes IUsedIFree IUse% Mounted on /dev/sdg1 211785 -13681772 13893557 - /mnt While I was transferring files to the exfat file system the numbers were changing as follows: Filesystem Inodes IUsedIFree IUse% Mounted on /dev/sdg12533 -15565039 15567572 - /mnt /dev/sdg1 93422 -14747035 14840457 - /mnt /dev/sdg1 125491 -14458414 14583905 - /mnt /dev/sdg1 211785 -13681772 13893557 - /mnt /dev/sdg1 365837 -12295302 12661139 - /mnt The number displayed under IFree seems to show the number of free clusters (and inodes?). But the number which is displayed under Inodes seems to be the number of used inodes. And the number under IUsed obviously is the difference between Inodes and IFree, calculated with wrong input values. Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages exfat-fuse depends on: ii fuse 2.9.3-9 ii libc6 2.18-4 ii libfuse2 2.9.3-9 Versions of packages exfat-fuse recommends: ii exfat-utils 1.0.1-1 exfat-fuse 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#746397: snmpd: Missing log_end_msg in /etc/init.d/snmpd
Package: snmpd Version: 5.7.2.1~dfsg-5 Severity: normal Tags: patch Dear Maintainer, the start and stop messages from /etc/init.d/snmpd are garbled. The final ok and the line feed is missing. The attached patch adds the missing calls of log_end_msg so that the start script works as expected, at least when the auto-start of the snmpd service is enabled. It also fixes some minor issues in the start and stop messages like duplicate colons and unnecessary spaces. I don't know how Debian start scripts should behave when a service is disabled, so I tried to not change the behavior when the auto-start of snmpd is disabled. As I am not very familiar with Debian start script conventions better double check the changes before using them. Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages snmpd depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.52 ii libc6 2.18-4 ii libsnmp-base 5.7.2.1~dfsg-3 ii libsnmp30 5.7.2.1~dfsg-5 ii lsb-base 4.1+Debian12 snmpd recommends no packages. Versions of packages snmpd suggests: pn snmptrapd none -- debconf information: * snmpd/upgradefrom521: snmpd/upgradefrom36: diff --git a/init.d/snmpd b/init.d/snmpd index 3e6dc03..610cfbc 100755 --- a/init.d/snmpd +++ b/init.d/snmpd @@ -34,9 +34,11 @@ SNMPDOPTS=-Lsd -Lf /dev/null -p $SNMP_PID # Cd to / before starting any daemons. cd / +status=0 + case $1 in start) -log_daemon_msg Starting SNMP services: +log_daemon_msg Starting SNMP services # remove old symlink with previous version if [ -L /var/run/agentx ]; then rm -f /var/run/agentx @@ -45,36 +47,43 @@ case $1 in mkdir -p /var/run/agentx fi if [ $SNMPDRUN = yes -a -f /etc/snmp/snmpd.conf ]; then + log_progress_msg snmpd start-stop-daemon --quiet --start --oknodo --exec /usr/sbin/snmpd \ - -- $SNMPDOPTS - log_progress_msg snmpd + -- $SNMPDOPTS || status=$? fi +log_end_msg $status ;; stop) -log_daemon_msg Stopping SNMP services: -start-stop-daemon --quiet --stop --oknodo --retry 3 --exec /usr/sbin/snmpd [ ! -f $SNMP_PID ] || rm $SNMP_PID -log_progress_msg snmpd +log_daemon_msg Stopping SNMP services snmpd +start-stop-daemon --quiet --stop --oknodo --retry 3 --exec /usr/sbin/snmpd \ + || status=$? +[ $status -eq 0 -a -f $SNMP_PID ] rm $SNMP_PID +log_end_msg $status ;; restart) -log_daemon_msg Restarting SNMP services: -start-stop-daemon --quiet --stop --oknodo --retry 3 --exec /usr/sbin/snmpd [ ! -f $SNMP_PID ] || rm $SNMP_PID +log_daemon_msg Restarting SNMP services +start-stop-daemon --quiet --stop --oknodo --retry 3 --exec /usr/sbin/snmpd \ + || status=$? +[ $status -eq 0 -a -f $SNMP_PID ] rm $SNMP_PID if [ $SNMPDRUN = yes -a -f /etc/snmp/snmpd.conf ]; then - start-stop-daemon --quiet --start --exec /usr/sbin/snmpd -- $SNMPDOPTS - log_progress_msg snmpd + log_progress_msg snmpd + start-stop-daemon --quiet --start --exec /usr/sbin/snmpd -- $SNMPDOPTS \ + || status=$? fi +log_end_msg $status ;; reload|force-reload) -log_daemon_msg Reloading SNMP services: +log_daemon_msg Reloading SNMP services if [ $SNMPDRUN = yes -a -f /etc/snmp/snmpd.conf ]; then + log_progress_msg snmpd start-stop-daemon --quiet --stop --signal 1 \ - --pidfile $SNMP_PID --exec /usr/sbin/snmpd - log_progress_msg snmpd + --pidfile $SNMP_PID --exec /usr/sbin/snmpd || status=$? fi +log_end_msg $status ;; status) -status=0 if [ $SNMPDRUN = yes -a -f /etc/snmp/snmpd.conf ]; then - status_of_proc /usr/sbin/snmpd snmpd || status=$? + status_of_proc /usr/sbin/snmpd snmpd || status=$? fi exit $status ;;
Bug#746399: snmpd: Typo in config file - line 53: Error: Name or service not known
Package: snmpd Version: 5.7.2.1~dfsg-5 Severity: minor Dear Maintainer, on startup snmpd complains about an error in the config file: /etc/snmp/snmpd.conf: line 53: Error: Name or service not known The reason is a typo (defalut instead of default): rocommunity6 public defalut -V systemonly ^^ There are also two warnings on startup: /etc/snmp/snmpd.conf: line 145: Warning: Unknown token: defaultMonitors. /etc/snmp/snmpd.conf: line 147: Warning: Unknown token: linkUpDownNotifications. Not sure if they have any relevance. Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages snmpd depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.52 ii libc6 2.18-4 ii libsnmp-base 5.7.2.1~dfsg-3 ii libsnmp30 5.7.2.1~dfsg-5 ii lsb-base 4.1+Debian12 snmpd recommends no packages. Versions of packages snmpd suggests: pn snmptrapd none -- Configuration Files: /etc/snmp/snmpd.conf [Errno 13] Permission denied: u'/etc/snmp/snmpd.conf' /etc/snmp/snmptrapd.conf [Errno 13] Permission denied: u'/etc/snmp/snmptrapd.conf' -- debconf information: snmpd/upgradefrom36: * snmpd/upgradefrom521: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743972: openssh-client: ssh reprocesses configuration files even when CanonicalizeHostname is not set
Package: openssh-client Version: 1:6.6p1-2 Severity: normal Dear Maintainer, I have an ssh configuration which allows me to easily access local hosts (which are reachable directly) and remote hosts (which are only reachable through a HTTP proxy). The configuration file (simplified) looks like this: Host a Hostname 172.18.1.1 Host b Hostname 172.18.1.2 [..] Host *.* ProxyCommand nc -X connect -x gateway:8080 %h %p The upgrade of openssh-client from version 1:6.5p1-6 to 1:6.6p1-2 breaks this configuration. ssh now reprocesses the config file with the substituted host name even when I explicitly set CanonicalizeHostname to no. Thus the Host *.* pattern matches always and ssh tries to reach all hosts through the proxy. CanonicalizeHostname is the only option I have found which should trigger the reprocessing of the config file. And there seems to be no other option to explicitly disable this behavior. Uwe ssh log with config file: Host * CanonicalizeHostname no Host a Hostname 172.18.1.1 Host *.* ProxyCommand nc -X connect -x gateway:8080 %h %p $ ssh -v a OpenSSH_6.6, OpenSSL 1.0.1g 7 Apr 2014 debug1: Reading configuration data /home/uwe/.ssh/config debug1: /home/uwe/.ssh/config line 1: Applying options for * debug1: /home/uwe/.ssh/config line 3: Applying options for a debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Hostname has changed; re-reading configuration debug1: Reading configuration data /home/uwe/.ssh/config debug1: /home/uwe/.ssh/config line 1: Applying options for * debug1: /home/uwe/.ssh/config line 5: Applying options for *.* debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Executing proxy command: exec nc -X connect -x gateway:8080 172.18.1.1 22 [..] nc: Proxy error: HTTP/1.0 504 Gateway Time-out ssh_exchange_identification: Connection closed by remote host -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssh-client depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.6 ii libc6 2.18-4 ii libedit2 3.1-20140213-1 ii libgssapi-krb5-2 1.12.1+dfsg-1 ii libselinux1 2.2.2-1 ii libssl1.0.0 1.0.1g-1 ii passwd1:4.1.5.1-1.1 ii zlib1g1:1.2.8.dfsg-1 Versions of packages openssh-client recommends: ii xauth 1:1.0.7-1 Versions of packages openssh-client suggests: pn keychain none pn libpam-sshnone pn monkeysphere none ii ssh-askpass 1:1.2.4.1-9 -- 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#740900: apt-cacher: aptitude changelog package fails when using apt-cacher]
On Mar 31, Mark Hindley wrote: OK, could you try this patch please (on top of the others). Although I cannot reproduce this behavious (I think I have an upstream transparent proxy that is filtering all the redirects), I think I understand what was wrong and hope this addresses it. Although the patch looks big, it is mostly a refactoring of the logic. I think it should reliably read all the headers before going on to the body. Looks like this patch fixes the bug. I could not reproduce it anymore, with none of the combinations of apt-get/aptitude on stable/testing. No more HTTP headers in the changelog output. Nice work, thank you! Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740900: apt-cacher: aptitude changelog package fails when using apt-cacher]
Hi Mark, sorry for the delay. On Mar 08, Mark Hindley wrote: On Fri, Mar 07, 2014 at 05:17:30PM +0100, Uwe Storbeck wrote: So we have 2 different problems, apt-get/aptitude on stable and apt-get on testing/unstable throw the HTTP headers into the changelog output when using apt-cacher and aptitude on testing/unstable fails to get the changelog because it uses a different URL than apt-get to fetch it? Could you test these 2 patches and see if they help? I've applied both patches and the patch from your 2nd mail to apt-cacher 1.7.6 from stable. Both apt-get and aptitude work as expected now, when I switch off the use of an external proxy. It looks like the primary issue of this bug is fixed by your patches, aptitude changelog does not fail anymore. But when I use squid as an external proxy (use_proxy = 1) apt-get from stable (version 0.9.7.9+deb7) and testing (version 0.9.15.5+b1) and aptitude from stable (version 0.6.8.2-1), but not aptitude from testing (version 0.6.10-1), still throw HTTP headers into the changelog output when apt-cacher has to retrieve the changelog file from the debian server (see attached apt-cacher log). The output in apt-get or aptitude looks like this: HTTP/1.0 200 Connection established Connection: Keep-Alive Date: Thu, 27 Mar 2014 19:56:32 GMT Via: 1.1 c1:3142 (apt-cacher/1.7.6) Accept-Ranges: bytes Content-Length: 12381 Keep-Alive: timeout=15, max=100 X-AptCacher-URL: http://packages.debian.org/changelogs/pool/main/e/ed/ed_1.10-2/changelog ed (1.10-2) unstable; urgency=medium * enable DEB_BUILD_MAINT_OPTIONS = hardening=+all -- Martin Zobel-Helas zo...@debian.org Tue, 25 Feb 2014 21:58:25 +0100 ed (1.10-1) unstable; urgency=medium [..] When apt-cacher can deliver the changelog from its cache the output is always displayed as expected, without the HTTP headers. I hope the log helps to also fix the problem with the displayed HTTP headers. Thanks Uwe Thu Mar 27 20:56:31 2014|debug [1897]: Connection from 172.18.1.2 Thu Mar 27 20:56:31 2014|debug [6133]: New Daemon connection Thu Mar 27 20:56:31 2014|debug [6133]: Test client 172.18.1.2/32 against localhost: 127.0.0.1/8 Thu Mar 27 20:56:31 2014|debug [6133]: Test client 172.18.1.2/32 against localhost: 0:0:0:0:0:0:0:1/128 Thu Mar 27 20:56:31 2014|debug [6133]: Test client 172.18.1.2/32 against allowed: 172.18.1.0/24 Thu Mar 27 20:56:31 2014|debug [6133]: Client 172.18.1.2/32 passed access control rules Thu Mar 27 20:56:31 2014|debug [6133]: Processing a new request line Thu Mar 27 20:56:31 2014|debug [6133]: got: 'GET http://packages.debian.org/changelogs/pool/main/e/ed/ed_1.10-2/changelog HTTP/1.1' Thu Mar 27 20:56:31 2014|debug [6133]: Processing a new request line Thu Mar 27 20:56:31 2014|debug [6133]: got: 'Host: packages.debian.org' Thu Mar 27 20:56:31 2014|debug [6133]: Processing a new request line Thu Mar 27 20:56:31 2014|debug [6133]: got: 'Accept: text/*' Thu Mar 27 20:56:31 2014|debug [6133]: Processing a new request line Thu Mar 27 20:56:31 2014|debug [6133]: got: 'User-Agent: Debian APT-HTTP/1.3 (0.9.15.5)' Thu Mar 27 20:56:31 2014|debug [6133]: Processing a new request line Thu Mar 27 20:56:31 2014|debug [6133]: got: '' Thu Mar 27 20:56:31 2014|debug [6133]: Checking host packages.debian.org in absolute URI Thu Mar 27 20:56:31 2014|debug [6133]: Different ports in absolute URI: 3142 = 80 Thu Mar 27 20:56:31 2014|debug [6133]: Host in Absolute URI is not this server Thu Mar 27 20:56:31 2014|debug [6133]: Resolved request is http://packages.debian.org/changelogs/pool/main/e/ed/ed_1.10-2/changelog Thu Mar 27 20:56:31 2014|debug [6133]: Reverse path_map match: packages\.debian\.org - debian-changelogs Thu Mar 27 20:56:31 2014|debug [6133]: Changelog file: ed_1.10-2_changelog Thu Mar 27 20:56:31 2014|debug [6133]: Locked header /var/cache/apt-cacher/headers/ed_1.10-2_changelog Thu Mar 27 20:56:31 2014|debug [6133]: Freshness checks Thu Mar 27 20:56:31 2014|debug [6133]: Revalidating ed_1.10-2_changelog. Age: 41 Thu Mar 27 20:56:31 2014|debug [6133]: Libcurl candidate: http://packages.debian.org/changelogs/pool/main/e/ed/ed_1.10-2/changelog Thu Mar 27 20:56:31 2014|debug [6133]: Global lock: Connect libcurl Thu Mar 27 20:56:31 2014|debug [6133]: Connection to running libcurl process found on /var/cache/apt-cacher/libcurl.socket Thu Mar 27 20:56:31 2014|debug [6133]: Release global lock Thu Mar 27 20:56:31 2014|debug [4384]: libcurl: new connection Thu Mar 27 20:56:31 2014|debug [4384]: Libcurl: thawed request HEAD http://packages.debian.org/changelogs/pool/main/e/ed/ed_1.10-2/changelog with headers Pragma: Thu Mar 27 20:56:31 2014|debug [4384]: Init new libcurl object Thu Mar 27 20:56:31 2014|debug [4384]: Add curl handle #13: for http://packages.debian.org/changelogs/pool/main/e/ed/ed_1.10-2/changelog Thu Mar 27 20:56:31 2014|debug [4384]: libcurl: setting up for HEAD request Thu Mar 27 20:56:31 2014|debug [4384]: CURLINFO_TEXT: Re-using existing
Bug#740971: completion fails on file names with special characters
On Mar 20, Chet Ramey wrote:
I've updated the patch, and attached it. This seems to fix all of the
reported problems from Debian's version of bash-completion.
It looks like this patch is included in Debian bash version
4.3-4. Most of my examples for bash completion which started to
fail with bash 4.3 are working again now. But one example still
fails, though I don't know if this is a problem of bash or
bash-completion:
$ mkdir /tmp/test cd /tmp/test touch aa 'a('
$ ls aTABTAB
a( aa
So far it's ok. But:
$ ls a(TAB
results in a wrong completion:
$ ls a(a
Uwe
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740971: completion fails on file names with special characters
On Mar 27, Chet Ramey wrote: Since that line, as you entered it above, is a syntax error, it's not clear what bash should do with it (probably nothing). What do you expect to happen? The same as if you would try to complete any non-existing file name, nothing? The completion should not append an a to the typed in a(. Instead the cursor should stay in the same position (after the parenthesis) and bash should beep. When you try to complete ls ab with TAB in the same example with the two files aa and a( in a directory bash-completion handles it correctly. It only fails because of the parenthesis (and maybe also with other special characters). Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740971: completion fails on file names with special characters
retitle 740971 bash: completion fails on file names that contain spaces or other special characters thanks On Mar 08, Filipus Klutiero wrote: To clarify, it's not that completion is completely broken, it just fails when several files share a start which contains at least one space. Completion already fails on a single file name which contains a space. Try: $ mkdir /tmp/test cd /tmp/test touch 'a a' $ ls TABTAB Nothing happens .. Completion also fails for file names which contain other special characters which bash would escape with a backslash on completion. Try the above example with file names like a( or a,. You can use single quotes to work around this bug: $ ls 'TABTAB In the example above this works as expected. Strangely it does not work when you use double quotes instead. Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740971: completion fails on file names with special characters
A few corrections to my last mail:
bash completion before the first letter of the file name fails at
all, even for normal file names:
$ mkdir /tmp/test cd /tmp/test touch a
$ ls TABTAB
Also not all characters where the completion after the first
letter fails are characters which bash would escape with a
backslash during the completion as the comma actually does not
get escaped by bash.
Not sure what qualifies special characters in this context.
Characters where completion does not work for me (when file
names share the same beginning, as you have mentioned before)
are:
!$'()*,:;=?[\]^`{|}
Interesting is also this example:
$ mkdir /tmp/test cd /tmp/test touch aa 'a('
$ ls aTABTAB
a( aa
So far it's ok. But:
$ ls a(TAB
results in a wrong completion:
$ ls a(a
Uwe
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740900: apt-cacher: aptitude changelog package fails when using apt-cacher]
On Mar 07, Mark Hindley wrote: I think you said you had a stable system, this looks like the version from testing. The server where apt-cacher (and squid) runs is on stable, the client where I did run aptitude/apt-get is on testing. I thought using the most recent software versions where easily possible would be best, but I can also use the stable versions of aptitude/apt-get on the server when you prefer that. Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740900: apt-cacher: aptitude changelog package fails when using apt-cacher]
On Mar 07, Mark Hindley wrote: I can update the regexp to try to cover these cases, but I need to read more first to see if apt-cacher or aptitude is out of line. A short test with aptitude on stable (version 0.6.8.2-1) shows that this version behaves like apt-get, it throws the HTTP headers into the output, but does not fail to fetch the changelog. So we have 2 different problems, apt-get/aptitude on stable and apt-get on testing/unstable throw the HTTP headers into the changelog output when using apt-cacher and aptitude on testing/unstable fails to get the changelog because it uses a different URL than apt-get to fetch it? Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740900: apt-cacher: aptitude changelog package fails when using apt-cacher]
[I resend the mail to the bug tracker. I was in a hurry and
failed to reply properly in my previous mail. Sorry!]
Hi Mark
This works for me with both 1.7.6 and 1.7.8 using both aptitude
changelog package and apt-get changelog package so I can't
immediately reproduce it here.
I have the impression that this may be triggered by different
server behavior. Sometimes the requests are answered directly,
sometimes they are redirected (and end up with header lines in
the output of apt-get changelog). Unfortunately I have no time
to dig deeper into this at the moment, maybe at the weekend.
Could you post the rest of your config? In particular what is the
setting of installer_files_regexp? The default contains a portion which
matches changelog. You can get the config by running by pointing any
browser to http://server-hostname:port
Yes, I've seen it (now) in installer_files_regexp. But it does
not match in the case when the changelog file is delivered as
packagename_changelog and not as packagename/changelog.
My configuration is attached below (original and with my change).
Also 2 examples of apt-cache changelog which to me look like
different server behavior.
Uwe
Apt-cacher version 1.7.6: Daemon mode
Usage:
Edit /etc/apt/apt.conf to include the configuration
Acquire::http::proxy=http://c1:3142
Alternatively, edit /etc/apt/sources.list so all your HTTP sources are
prepended with the address of your apt-cacher machine and the port, like this:
deb http://example.debian.org/debian unstable main contrib non-free
becomes
deb http://c1:3142/example.debian.org/debian unstable main contrib non-free
Configuration: /etc/apt-cacher/apt-cacher.conf
Directive Value
admin_emailroot@localhost
allowed_hosts 172.18.1.0/24
allowed_ssl_locations
allowed_ssl_ports 443
cache_dir /var/cache/apt-cacher
clean_cache1
concurrent_import_limit2
curl_idle_timeout 120
curl_throttle 10
daemon_addr172.18.1.1
daemon_port3142
data_timeout 120
debug 0
denied_hosts
distinct_namespaces0
expire_hours 0
fork 1
generate_reports 1
group www-data
http_proxy http-proxy:8080
http_proxy_auth
libcurl_socket /var/cache/apt-cacher/libcurl.socket
limit 0
limit_global 0
log_dir/var/log/apt-cacher
ftp.debian.org mirror.switch.ch/ftp/mirror
ftp.ch.debian.org ftp.debian.org;
security.debian.org mirror.switch.ch/ftp/mirror/
debian-security ftp.ch.debian.org
path_map security.debian.org; backports.debian.org
mirror.switch.ch/ftp/mirror ftp.ch.debian.org
backports.debian.org; volatile.debian.org
mirror.switch.ch/ftp/mirror ftp.ch.debian.org
volatile.debian.org
pidfile/var/run/apt-cacher.pid
request_empty_lines5
request_timeout30
retry 3
return_buffer_size 1048576
reverse_path_map 1
dapper, edgy, feisty, gutsy, hardy, intrepid,
ubuntu_release_names jaunty, karmic, lucid, maverick, natty, oneiric,
precise, quantal
use_proxy 1
use_proxy_auth 0
user www-data
checksum_files_regexp (?^:^(?:Packages(?:\.gz|\.bz2)?|Sources(?:\.gz|
\.bz2)?|(?:In)?Release|Index(?:\.bz2)?)$)
(?^:^(?:Index(?:\.bz2)?|Packages(?:\.gz|\.bz2)?|
Release(?:\.gpg)?|InRelease|Sources(?:\.gz|\.bz2)?|
index_files_regexp Contents-(?:[a-z]+-)?[a-zA-Z0-9]+\.gz|(?:srclist|
pkglist)\.[a-z-]+\.bz2|release(?:\.gz|\.bz2)?|
Translation-[a-z]{2,3}(?:_[A-Z]{2})?(?:\.gz|\.bz2|
\.xz)?)$)
(?^:^(?:vmlinuz|linux|initrd\.gz|changelog|
NEWS.Debian|(?:dapper|edgy|feisty|gutsy|hardy|
installer_files_regexp intrepid|jaunty|karmic|lucid|maverick|natty|oneiric|
precise|quantal)\.tar\.gz(?:\.gpg)?|(?:Devel|EOL)?
ReleaseAnnouncement(?:\.html)?|meta-release(?:-lts)?
(?:-(?:development|proposed))?)$)
(?^:(?:^[-+.a-z0-9]+_(?:\d:)?[-+.~a-zA-Z0-9]+(?:_
package_files_regexp [-a-z0-9]+\.(?:u|d)?deb|\.dsc|\.tar(?:\.gz|\.bz2|
\.xz)|\.diff\.gz)|\.rpm|index\.db-.+\.gz|\.jigdo|
Bug#740900: apt-cacher: aptitude changelog package fails when using apt-cacher
Package: apt-cacher Version: 1.7.6 Severity: normal Dear Maintainer, when I try to display the changelog of a package with aptitude changelog package and I have not the most recent version of that package installed on my system aptitude needs to download the changelog file from the debian server. This download fails when I use apt-cacher: $ aptitude changelog ed Err Changelog of ed E: Changelog download failed: 403 Sorry, not allowed to fetch that type of file: ed_1.10-2_changelog Extending the parameter package_files_regexp in apt-cacher.conf for the changelog files fixes the problem for me so far, but I'm not sure if that's the complete solution for all cases. Old (default and commented out) setting: package_files_regexp = (?:^[-+.a-z0-9]+_(?:\d:)?[-+.~a-zA-Z0-9]+(?:_[-a-z0-9]+\.(?:u|d)?deb|\.dsc|\.tar(?:\.gz|\.bz2|\.xz)|\.diff\.gz)|\.rpm|index\.db-.+\.gz|\.jigdo|\.template)$ Changed to: package_files_regexp = (?:^[-+.a-z0-9]+_(?:\d:)?[-+.~a-zA-Z0-9]+(?:_[-a-z0-9]+\.(?:u|d)?deb|\.dsc|\.tar(?:\.gz|\.bz2|\.xz)|\.diff\.gz|_changelog)|\.rpm|index\.db-.+\.gz|\.jigdo|\.template)$ I have not tested the current version of apt-cacher from sid as my server runs on stable. But I haven't found an entry in the changelog file of apt-cacher 1.7.8 which indicates that this bug is already fixed. Uwe -- System Information: Debian Release: 7.4 APT prefers stable APT policy: (850, 'stable'), (840, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-cacher depends on: ii debconf [debconf-2.0] 1.5.49 ii dpkg 1.16.12 ii ed 1.6-2 ii libfilesys-df-perl 0.92-4+b1 ii libfreezethaw-perl 0.5001-1 ii libio-interface-perl 1.06-1+b1 ii libnetaddr-ip-perl 4.062+dfsg-1 ii libsys-syscall-perl0.23-1 ii libwww-curl-perl 4.15-1+b2 ii libwww-perl6.04-1 ii lsb-base 4.1+Debian8+deb7u1 ii perl 5.14.2-21+deb7u1 ii ucf3.0025+nmu3 ii update-inetd 4.43 Versions of packages apt-cacher recommends: ii libberkeleydb-perl 0.51-1 Versions of packages apt-cacher suggests: ii libio-socket-inet6-perl 2.69-2 -- Configuration Files: /etc/apt-cacher/apache.conf changed: Alias /apt-cacher /usr/share/apt-cacher/apt-cacher-cgi.pl DirectoryMatch /usr/share/apt-cacher/ Options ExecCGI AddHandler cgi-script .pl AllowOverride None order allow,deny Allow from XXX /DirectoryMatch /etc/apt-cacher/apt-cacher.conf changed: group = www-data user = www-data daemon_addr = 172.18.1.1 allowed_hosts = 172.18.1.0/24 http_proxy = http-proxy:8080 use_proxy = 1 package_files_regexp = (?:^[-+.a-z0-9]+_(?:\d:)?[-+.~a-zA-Z0-9]+(?:_[-a-z0-9]+\.(?:u|d)?deb|\.dsc|\.tar(?:\.gz|\.bz2|\.xz)|\.diff\.gz|_changelog)|\.rpm|index\.db-.+\.gz|\.jigdo|\.template)$ path_map = \ ftp.debian.org mirror.switch.ch/ftp/mirror ftp.ch.debian.org ftp.debian.org; \ security.debian.org mirror.switch.ch/ftp/mirror/debian-security ftp.ch.debian.org security.debian.org; \ backports.debian.org mirror.switch.ch/ftp/mirror ftp.ch.debian.org backports.debian.org; \ volatile.debian.org mirror.switch.ch/ftp/mirror ftp.ch.debian.org volatile.debian.org /etc/default/apt-cacher changed: AUTOSTART=1 -- debconf information: * apt-cacher/mode: daemon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#740900: apt-cacher: aptitude changelog package fails when using apt-cacher
You can also use aptitude changelog on any package which is not installed on your system to test the bug. That's probably easier and works also when all installed packages are upgraded to the latest version. Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727708: init system coupling etc.
On Feb 12, Russ Allbery wrote: Packages should normally support the default Linux init system. [..] Package maintainers are strongly encouraged to merge any contributions for support of init systems other than the Linux default, and to add that support themselves if they're willing and capable of doing so. Assumed a package has (only) start scripts for sysvinit. This satisfies Packages should normally support the default Linux init system (using sysvinit compatibility mode). Someone provides patches to add native support for upstart and systemd, maybe to use advanced features like socket activation. Following the above proposal the package maintainer is encouraged to apply the patch for upstart (as an init system other than the Linux default), but not the patch for systemd. Wouldn't it be better to change that to something like for support of any init system? Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#370747: closed by Solveig deb...@solveig.org (Re: Command-line options should override Xresources - closing)
Hi Solveig Sorry if the answer under what conditions the bug arises wasn't clear enough. For a detailed description how to reproduce it see below. The bug is still unfixed. It also has been confirmed by Thomas Dickey. Therefore I'm going to reopen the bug and remove the unreproducible tag. To reproduce the bug: - Set xterm.vt100.saveLines to e.g. 100 in your X resource file (~/.Xresources or whatever): xterm.vt100.saveLines:100 - Merge the resource file: xrdb -merge ~/.Xresources - Start an xterm (without options), it should have 100 saved lines. - Start another xtem with option -sl 200. This xterm should have 200 saved lines, as command line options should override resource settings. But it still only has 100 saved lines, the command line option has no effect. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#733633: arpwatch uses 100% CPU and does not log any addresses
Package: arpwatch
Version: 2.1a15-1.2
Severity: important
Dear Maintainer,
after the start arpwatch uses 100% CPU and does not log any
addresses to /var/lib/arpwatch/arp.dat:
-rw-r- 1 arpwatch root 0 2013-12-30 14:53 /var/lib/arpwatch/arp.dat
A trace of arpwatch is attached (strace /usr/sbin/arpwatch -d).
This behavior is reproducible on every start, only the number
of calls to poll at the end of the trace differs (from one to
several).
Regards
Uwe
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages arpwatch depends on:
ii adduser 3.113+nmu3
ii libc6 2.17-97
ii libpcap0.8 1.5.2-1
arpwatch recommends no packages.
arpwatch suggests no packages.
-- debconf-show failed
execve(/usr/sbin/arpwatch, [/usr/sbin/arpwatch, -d], [/* 18 vars */]) = 0
brk(0) = 0x9336000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xf76f9000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY|O_CLOEXEC) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=199715, ...}) = 0
mmap2(NULL, 199715, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf76c8000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/i386-linux-gnu/i686/cmov/libresolv.so.2, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 '\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=79720, ...}) = 0
mmap2(NULL, 92232, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xf76b1000
mmap2(0xf76c4000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x12) = 0xf76c4000
mmap2(0xf76c6000, 6216, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xf76c6000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/i386-linux-gnu/libpcap.so.0.8, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=243892, ...}) = 0
mmap2(NULL, 244608, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xf7675000
mmap2(0xf76af000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3a) = 0xf76af000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/lib/i386-linux-gnu/i686/cmov/libc.so.6, O_RDONLY|O_CLOEXEC) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 \232\1\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1763108, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xf7674000
mmap2(NULL, 1768220, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xf74c4000
mmap2(0xf766e000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1aa) = 0xf766e000
mmap2(0xf7671000, 11036, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xf7671000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xf74c3000
set_thread_area({entry_number:-1 - 12, base_addr:0xf74c36c0, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0,
useable:1}) = 0
mprotect(0xf766e000, 8192, PROT_READ) = 0
mprotect(0xf76af000, 4096, PROT_READ) = 0
mprotect(0xf76c4000, 4096, PROT_READ) = 0
mprotect(0x804f000, 4096, PROT_READ)= 0
mprotect(0xf771b000, 4096, PROT_READ) = 0
munmap(0xf76c8000, 199715) = 0
socket(PF_NETLINK, SOCK_RAW, 0) = 3
bind(3, {sa_family=AF_NETLINK, pid=0, groups=}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=10704, groups=}, [12]) = 0
time(NULL) = 1388413817
sendto(3, \24\0\0\0\22\0\1\3y\203\301R\0\0\0\0\0\0\0\0, 20, 0,
{sa_family=AF_NETLINK, pid=0, groups=}, 12) = 20
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\f\4\0\0\20\0\2\0y\203\301R\320)\0\0\0\0\4\3\1\0\0\0I\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 2080
brk(0) = 0x9336000
brk(0x9357000) = 0x9357000
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\24\0\0\0\3\0\2\0y\203\301R\320)\0\0\0\0\0\0\1\0\0\0I\0\1\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
sendto(3, \24\0\0\0\26\0\1\3z\203\301R\0\0\0\0\0\0\0\0, 20, 0,
{sa_family=AF_NETLINK, pid=0,
Bug#719754: phpmyadmin breaks apache2 configuration
Package: phpmyadmin Version: 4:4.0.5-1 Severity: important Dear Maintainer, the phpmyadmin configuration for apache2 makes apache2 fail to start: [warn] The apache2 configtest failed. ... (warning). Output of config test was: AH00526: Syntax error on line 10 of /etc/apache2/conf-enabled/phpmyadmin.conf: Invalid command 'AddType', perhaps misspelled or defined by a module not included in the server configuration Action 'configtest' failed. Looks like AddType is included in the wrong conditional statement. Shouldn't that be a check for mod_mime? At least enabling mime fixes this error, but ... ... leads to the next error: [warn] The apache2 configtest failed. ... (warning). Output of config test was: AH00526: Syntax error on line 30 of /etc/apache2/conf-enabled/phpmyadmin.conf: Unknown Authz provider: valid-user Action 'configtest' failed. phpmyadmin also still uses the old Order Deny,Allow authorization scheme. Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages phpmyadmin depends on: ii dbconfig-common 1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.50 ii libapache2-mod-php5 5.5.1+dfsg-1 ii libjs-codemirror 2.23-1 ii libjs-jquery 1.7.2+dfsg-3 ii libjs-jquery-cookie 8-2 ii libjs-jquery-event-drag 8-2 ii libjs-jquery-mousewheel 8-2 ii libjs-jquery-tablesorter 8-2 ii libjs-jquery-ui 1.10.1+dfsg-1 ii libjs-underscore 1.1.6-1+deb7u1 ii perl 5.14.2-21 ii php-gettext 1.0.11-1 ii php5 5.5.1+dfsg-1 ii php5-json 1.3.1+dfsg-1 ii php5-mcrypt 5.5.1+dfsg-1 ii php5-mysql5.5.1+dfsg-1 ii ttf-dejavu-core 2.33+svn2514-3 ii ucf 3.0027+nmu1 Versions of packages phpmyadmin recommends: ii apache2 2.4.6-2 ii apache2-bin [httpd] 2.4.6-2 ii mysql-client 5.5.31+dfsg-1 ii mysql-client-5.5 [mysql-client] 5.5.31+dfsg-1 ii php5-gd 5.5.1+dfsg-1 -- debconf information: phpmyadmin/remove-error: abort phpmyadmin/setup-username: admin * phpmyadmin/db/app-user: phpmyadmin phpmyadmin/remote/host: * phpmyadmin/dbconfig-install: true phpmyadmin/remote/port: * phpmyadmin/dbconfig-upgrade: true phpmyadmin/missing-db-package-error: abort phpmyadmin/upgrade-error: abort phpmyadmin/dbconfig-reinstall: false * phpmyadmin/db/dbname: phpmyadmin phpmyadmin/database-type: mysql phpmyadmin/dbconfig-remove: * phpmyadmin/mysql/method: unix socket phpmyadmin/purge: false phpmyadmin/install-error: abort * phpmyadmin/reconfigure-webserver: apache2 phpmyadmin/restart-webserver: false * phpmyadmin/mysql/admin-user: root phpmyadmin/internal/reconfiguring: false phpmyadmin/remote/newhost: phpmyadmin/internal/skip-preseed: false phpmyadmin/upgrade-backup: true phpmyadmin/passwords-do-not-match: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719756: phpmyadmin: removal of package phpmyadmin fails
Package: phpmyadmin
Version: 4:4.0.5-1
Severity: normal
Dear Maintainer,
the removal of the phpmyadm package fails (log see below). Maybe that's
caused by apache2 not running (which was broken by phpmyadmin's
configuration). But the removal of the package should not fail
even when apache is not running.
Regards
Uwe
# aptitude purge phpmyadmin
The following packages will be REMOVED:
dbconfig-common{pu} [1.8.47+nmu1] -1,208 kB
libjs-codemirror{pu} [2.23-1] -976 kB
libjs-jquery-cookie{pu} [8-2] -45.1 kB
libjs-jquery-event-drag{pu} [8-2] -91.1 kB
libjs-jquery-metadata{pu} [8-2] -46.1 kB
libjs-jquery-mousewheel{pu} [8-2] -52.2 kB
libjs-jquery-tablesorter{pu} [8-2] -455 kB
libjs-jquery-ui{pu} [1.10.1+dfsg-1] -1,875 kB
php-gettext{pu} [1.0.11-1] -106 kB
php5-gd{pu} [5.5.1+dfsg-1] -150 kB
php5-mcrypt{pu} [5.5.1+dfsg-1] -91.1 kB
phpmyadmin{p} [4:4.0.5-1] -22.3 MB
0 packages upgraded, 0 newly installed, 12 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 27.4 MB will be freed.
Do you want to continue? [Y/n/?]
(Reading database ... 545509 files and directories currently installed.)
Removing phpmyadmin ...
dbconfig-common: dumping mysql database phpmyadmin to
/var/tmp/phpmyadmin.phpmyadmin.2013-08-15-00.23.mysql.WXPuCV.
dbconfig-common: dropping mysql database phpmyadmin.
dropping database phpmyadmin: success.
verifying database phpmyadmin was dropped: success.
dbconfig-common: revoking privileges for user phpmyadmin on phpmyadmin.
revoking access to database phpmyadmin from phpmyadmin@localhost: success.
Conf phpmyadmin disabled.
apache2_invoke postrm: Disable configuration phpmyadmin
[FAIL] Reloading web server: apache2 failed!
[warn] Apache2 is not running ... (warning).
invoke-rc.d: initscript apache2, action reload failed.
[FAIL] Reloading web server: apache2 failed!
[warn] Apache2 is not running ... (warning).
invoke-rc.d: initscript apache2, action reload failed.
Purging configuration files for phpmyadmin ...
apache2_invoke postrm: Purging state for phpmyadmin
dpkg: error processing phpmyadmin (--purge):
subprocess installed post-removal script returned error exit status 1
Removing dbconfig-common ...
Purging configuration files for dbconfig-common ...
dpkg: warning: while removing dbconfig-common, directory
'/var/cache/dbconfig-common/backups' not empty so not removed
Removing libjs-codemirror ...
Removing libjs-jquery-cookie ...
Removing libjs-jquery-event-drag ...
Removing libjs-jquery-tablesorter ...
Removing libjs-jquery-metadata ...
Removing libjs-jquery-mousewheel ...
Removing libjs-jquery-ui ...
Removing php-gettext ...
Removing php5-gd ...
php5_invoke prerm: Disable module gd for apache2 SAPI
php5_invoke prerm: Disable module gd for cli SAPI
Purging configuration files for php5-gd ...
php5_invoke gd postrm: No action required for apache2 SAPI
php5_invoke gd postrm: No action required for cli SAPI
Removing php5-mcrypt ...
php5_invoke prerm: Disable module mcrypt for apache2 SAPI
php5_invoke prerm: Disable module mcrypt for cli SAPI
Purging configuration files for php5-mcrypt ...
php5_invoke mcrypt postrm: No action required for apache2 SAPI
php5_invoke mcrypt postrm: No action required for cli SAPI
Processing triggers for man-db ...
Processing triggers for doc-base ...
Processing 2 removed doc-base files...
Registering documents with dwww...
Registering documents with dhelp...
Registering documents with scrollkeeper...
Processing triggers for hicolor-icon-theme ...
Processing triggers for libapache2-mod-php5 ...
Errors were encountered while processing:
phpmyadmin
[master 0b86d61] committing changes in /etc after apt run
19 files changed, 1 insertion(+), 385 deletions(-)
delete mode 12 apache2/conf-available/phpmyadmin.conf
delete mode 12 apache2/conf-enabled/phpmyadmin.conf
delete mode 100644 dbconfig-common/config
delete mode 100644 dbconfig-common/phpmyadmin.conf
delete mode 12 php5/apache2/conf.d/20-gd.ini
delete mode 12 php5/apache2/conf.d/20-mcrypt.ini
delete mode 12 php5/cli/conf.d/20-gd.ini
delete mode 12 php5/cli/conf.d/20-mcrypt.ini
delete mode 100644 php5/mods-available/gd.ini
delete mode 100644 php5/mods-available/mcrypt.ini
delete mode 100644 phpmyadmin/apache.conf
delete mode 100644 phpmyadmin/config-db.php
delete mode 100644 phpmyadmin/config.footer.inc.php
delete mode 100644 phpmyadmin/config.header.inc.php
delete mode 100644 phpmyadmin/config.inc.php
delete mode 100644 phpmyadmin/lighttpd.conf
delete mode 100644 phpmyadmin/phpmyadmin.desktop
delete mode 100644 phpmyadmin/phpmyadmin.service
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Bug#718597: dwww fails to recognize some documentation files
Package: dwww Version: 1.12.0 Severity: normal Dear Maintainer, dwww does not recognize some documentation files and reports errors under http://localhost/dwww/menu/errors.html: /var/lib/doc-base/documents/cvs-doc-paper Can't read /usr/share/doc/cvs/cvs-paper.pdf*: No such file or directory /var/lib/doc-base/documents/cvs-doc-paper No known formats! $ ls -l /usr/share/doc/cvs/cvs-paper.pdf* -rw-r--r-- 1 root root 87703 Oct 2 2005 /usr/share/doc/cvs/cvs-paper.pdf $ file /usr/share/doc/cvs/cvs-paper.pdf /usr/share/doc/cvs/cvs-paper.pdf: PDF document, version 1.2 The file /usr/share/doc/cvs/cvs-paper.pdf exists and although the asterisk at the end of the file pattern is not necessary it's a valid shell pattern. Same here; /var/lib/doc-base/documents/cvs-doc-client Can't read /usr/share/doc/cvs/cvsclient.pdf*: No such file or directory $ ls -l /usr/share/doc/cvs/cvsclient.pdf* -rw-r--r-- 1 root root 235407 Jul 19 00:09 /usr/share/doc/cvs/cvsclient.pdf Next error: /var/lib/doc-base/documents/cxref Can't read /usr/share/doc/cxref/FAQ.gz /usr/share/doc/cxref/README.gz: No such file or directory I don't know why dwww tries to process these two files as one. Both files exist: $ ls -l /usr/share/doc/cxref/FAQ.gz /usr/share/doc/cxref/README.gz -rw-r--r-- 1 root root 6502 Dec 27 2010 /usr/share/doc/cxref/FAQ.gz -rw-r--r-- 1 root root 5281 Oct 3 2012 /usr/share/doc/cxref/README.gz Next error: /var/lib/doc-base/documents/libxml-parser-perl Can't read : No such file or directory /var/lib/doc-base/documents/libxml-parser-perl No known formats! In the control file the file names are not listed on the same line as the Files: label. According to /usr/share/doc/doc-base/doc-base.txt.gz this is allowed for field values in general, but it's not clear if it's also allowed for the Files entry. Be free to reassign the bug. The doc-base control files are attached below. The corresponding package versions are: ii cvs 2:1.12.13+real-11 ii cxref 1.6d-6 ii libxml-parser-perl 2.41-1+b1 Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dwww depends on: ii apache2 2.4.6-2 ii apache2-bin [httpd-cgi] 2.4.6-2 ii debconf [debconf-2.0]1.5.50 ii debianutils 4.3.4 ii doc-base 0.10.5 ii file 1:5.14-2 ii libc62.17-7 ii libfile-ncopy-perl 0.36-1 ii libmime-types-perl 1.35-1 ii man-db 2.6.5-2 ii mime-support 3.54 ii perl 5.14.2-21 ii ucf 3.0027+nmu1 Versions of packages dwww recommends: ii apache2 2.4.6-2 ii apache2-bin [httpd] 2.4.6-2 ii apt 0.9.8.2 ii dlocate 1.02+nmu3 ii info2www 1.2.2.9-24 ii swish++ 6.1.5-2.2 Versions of packages dwww suggests: pn doc-debian none ii dpkg-www2.54+nmu1 -- debconf information: * dwww/cgiuser: www-data * dwww/cgidir: /usr/lib/cgi-bin * dwww/docrootdir: /var/www * dwww/serverport: 80 * dwww/servername: grappa.ibr.ch dwww/index_docs: true dwww/nosuchdir: dwww/nosuchuser: dwww/badport: Document: cvs-doc-paper Section: Programming Title: CVS II: Parallelizing Software Development Author: Brian Berliner berli...@prisma.com Abstract: This paper is the cvs USENIX article, Winter 1990. The program described in this paper fills a need in the UNIX community for a freely available tool to manage software revision and release control in a multi-developer, multi-directory, multi-group environment. This tool also addresses the increasing need for tracking third-party vendor source distributions while trying to maintain local modifications to earlier releases. Format: PDF Files: /usr/share/doc/cvs/cvs-paper.pdf* Document: cvs-doc-client Section: Programming Title: CVS client/server protocol description Abstract: This document describes the client/server protocol used by CVS. Format: HTML Index: /usr/share/doc/cvs/cvsclient.html Files: /usr/share/doc/cvs/cvsclient.html* Format: Info Index: /usr/share/info/cvsclient.info.gz Files: /usr/share/info/cvsclient.info* Format: PDF Files: /usr/share/doc/cvs/cvsclient.pdf* Format: Text Files: /usr/share/doc/cvs/cvsclient.txt* Document: cxref Section: Programming Title: Cxref Manual Author: Andrew M. Bishop Abstract: Generates LaTeX and HTML documentation for C programs. Format: HTML Index: /usr/share/doc/cxref/README.html Files: /usr/share/doc/cxref/*.html Format: text Files: /usr/share/doc/cxref/FAQ.gz /usr/share/doc/cxref/README.gz
Bug#718538: rxvt scrollbar is gone
Package: rxvt Version: 1:2.7.10-2 Severity: important Dear Maintainer, with the last update of rxvt the scrollbar is gone. According to rxvt -h it is compiled without scrollbar support now: $ rxvt -h Rxvt v2.7.10 - released: 26 MARCH 2003 Options: utmp,XIM,scrollbars=NONE,XGetDefaults Without scrollbar the use of rxvt is quite limited. Please re-add scrollbar support. Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rxvt depends on: ii libc6 2.17-7 ii libx11-6 2:1.6.0-1 ii libxpm4 1:3.5.10-1 rxvt recommends no packages. rxvt 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#717092: patch: Ignoring potentially dangerous file name
Package: patch Version: 2.7.1-3 Severity: normal Dear Maintainer, patch 2.7 refuses to patch files with absolute path names (without option -d/). This is an essential change in program behaviour and possibly breaks sysadm scripts. This change should be documented in the man page and announced as package news. Regards Uwe Example: $ patch -p0 /tmp/p Ignoring potentially dangerous file name /tmp/a.old Ignoring potentially dangerous file name /tmp/a can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |--- /tmp/a.old 2013-07-16 18:30:53.726805297 +0200 |+++ /tmp/a 2013-07-16 18:31:03.850761947 +0200 -- File to patch: /tmp/a patching file /tmp/a $ -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages patch depends on: ii libc6 2.17-7 patch recommends no packages. Versions of packages patch suggests: pn diffutils-doc none ii ed 1.6-2 -- no debconf information 1 2 3 4 5 --- /tmp/a.old 2013-07-16 18:30:53.726805297 +0200 +++ /tmp/a 2013-07-16 18:31:03.850761947 +0200 @@ -1,5 +1,4 @@ 1 2 -3 4 5
Bug#716992: [Aptitude-devel] Bug#716992: aptitude does not purge deleted packages when it asks for user confirmation
Hi Daniel APT::Get::Purge should not have any effect in aptitude. Its name indicates it is only used by apt-get. Oh, I always thought aptitude inherits apt settings ... Presently there is no option to do what you ask, which is beyond the scope of Purge-Unused. Responding to those prompts where “remove this package to resolve a conflict” is not the same as removing an unused package. This is something to be looked at during the next development cycle. It would be nice to have a more general purge option which would change the behavior of aptitude to always purge config files when a package gets deleted, no matter why it is deleted. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716992: aptitude does not purge deleted packages when it asks for user confirmation
Package: aptitude
Version: 0.6.8.2-1
Severity: normal
Dear Maintainer,
I have set APT::Get::Purge and Aptitude::Purge-Unused to true.
Aptitude normally honors these settings when it (auto-)deletes
packages.
But when aptitude runs into a situation where it has to ask the user
for confirmation (e.g. when it has to delete other packages because
of conflicts or dependencies) it ignores these settings and only
deletes the packages without purging the config files.
Example:
# aptitude install cups-bsd
The following NEW packages will be installed:
cups-bsd{b} [1.6.2-10] +71.7 kB
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 29.2 kB of archives. After unpacking 71.7 kB will be used.
The following packages have unmet dependencies:
cups-bsd : Conflicts: lpr but 1:2008.05.17+nmu1 is installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) lpr
Accept this solution? [Y/n/q/?] y
The following NEW packages will be installed:
cups-bsd [1.6.2-10] +71.7 kB
The following packages will be REMOVED:
lpr{a} [1:2008.05.17+nmu1] -418 kB
^^^
0 packages upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 29.2 kB of archives. After unpacking 346 kB will be freed.
Do you want to continue? [Y/n/?] _lpr
The following NEW packages will be installed:
cups-bsd [1.6.2-10] +71.7 kB
The following packages will be REMOVED:
lpr{ap} [1:2008.05.17+nmu1] -418 kB
0 packages upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
Need to get 29.2 kB of archives. After unpacking 346 kB will be freed.
Do you want to continue? [Y/n/?]
Aptitude should automatically set lpr to purge and not force me
to do it manually.
Regards
Uwe
-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude
aptitude version information:
aptitude 0.6.8.2 compiled at Nov 5 2012 06:20:41
Compiler: g++ 4.7.2
Compiled against:
apt version 4.12.0
NCurses version 5.9
libsigc++ version: 2.2.10
Ept support enabled.
Gtk+ support disabled.
Qt support disabled.
Current library versions:
NCurses version: ncurses 5.9.20130608
cwidget version: 0.5.16
Apt version: 4.12.0
aptitude linkage:
linux-gate.so.1 (0xf773d000)
libapt-pkg.so.4.12 = /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12
(0xf71b1000)
libncursesw.so.5 = /lib/i386-linux-gnu/libncursesw.so.5 (0xf717e000)
libtinfo.so.5 = /lib/i386-linux-gnu/libtinfo.so.5 (0xf715c000)
libsigc-2.0.so.0 = /usr/lib/i386-linux-gnu/libsigc-2.0.so.0
(0xf7157000)
libcwidget.so.3 = /usr/lib/libcwidget.so.3 (0xf7057000)
libept.so.1.aptpkg4.12 = /usr/lib/libept.so.1.aptpkg4.12 (0xf6fc4000)
libxapian.so.22 = /usr/lib/sse2/libxapian.so.22 (0xf6dde000)
libz.so.1 = /lib/i386-linux-gnu/libz.so.1 (0xf6dc4000)
libsqlite3.so.0 = /usr/lib/i386-linux-gnu/libsqlite3.so.0 (0xf6d0e000)
libboost_iostreams.so.1.49.0 = /usr/lib/libboost_iostreams.so.1.49.0
(0xf6cf8000)
libpthread.so.0 = /lib/i386-linux-gnu/i686/cmov/libpthread.so.0
(0xf6cdd000)
libstdc++.so.6 = /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf6bef000)
libm.so.6 = /lib/i386-linux-gnu/i686/cmov/libm.so.6 (0xf6bab000)
libgcc_s.so.1 = /lib/i386-linux-gnu/libgcc_s.so.1 (0xf6b8f000)
libc.so.6 = /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xf69df000)
libutil.so.1 = /lib/i386-linux-gnu/i686/cmov/libutil.so.1 (0xf69db000)
libdl.so.2 = /lib/i386-linux-gnu/i686/cmov/libdl.so.2 (0xf69d6000)
libbz2.so.1.0 = /lib/i386-linux-gnu/libbz2.so.1.0 (0xf69c4000)
libuuid.so.1 = /lib/i386-linux-gnu/libuuid.so.1 (0xf69be000)
librt.so.1 = /lib/i386-linux-gnu/i686/cmov/librt.so.1 (0xf69b5000)
/lib/ld-linux.so.2 (0xf773e000)
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages aptitude depends on:
ii aptitude-common 0.6.8.2-1
ii libapt-pkg4.120.9.8.2
ii libboost-iostreams1.49.0 1.49.0-4
ii libc6 2.17-7
ii libcwidget3 0.5.16-3.4
ii libept1.4.12 1.0.9
ii libgcc1 1:4.8.1-2
ii libncursesw5 5.9+20130608-1
ii libsigc++-2.0-0c2a2.2.10-0.2
ii libsqlite3-0 3.7.17-1
ii libstdc++64.8.1-2
ii libtinfo5 5.9+20130608-1
ii libxapian22 1.2.15-2
ii zlib1g1:1.2.8.dfsg-1
Versions of packages aptitude recommends:
ii apt-xapian-index0.45
ii aptitude-doc-en [aptitude-doc] 0.6.8.2-1
ii libparse-debianchangelog-perl 1.2.0-1
ii sensible-utils 0.0.9
Versions
Bug#714321: update of fontconfig makes munin spam an email every 5 minutes
Hi, this bug makes munin spam an email every 5 minutes, very annoying. Would it be possible to suppress this warning at least and not to send it on every use of the fontconfig interface? Also there's another font which is affected: fonts-droid Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-fonts.conf, line 103: Having multiple values in test isn't supported and may not work as expected Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-fonts.conf, line 138: Having multiple values in test isn't supported and may not work as expected Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710460: geeqie fails to keep the view position in picture when switching between pictures
Package: geeqie Version: 1:1.1-7 Severity: important Dear Maintainer, I often use geeqie to check or compare the quality of photos. I zoom in into the photo to have a 1:1 or even a 2:1 view, move to a part of the picture with a lot of details and then switch between different photos of the same object (with the mouse wheel) to compare the quality of the photos. geeqie 1.0 (on wheezy) maintains the view position within the picture so that you always see the same part of the pictures when you switch back and forth between them. geeqie 1.1 randomly either keeps the position in the picture or jumps to a completely different part of the picture when you switch between two pictures. Losing the view position in a zoomed in picture while scrolling through pictures makes geeqie quite unusable for checking photos, hence severity important. To reproduce the bug: Load 2 large photos of the same motif into geeqie, zoom in to 2:1 level, move to an easily recognizable spot of the photo and switch a few times back and forth between the pictures. When geeqie fails to keep the view position while switching between the pictures the whole picture gets blank for a short time. This blanking does not happen when geeqie successfully keeps the position during switching. Regards Uwe -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages geeqie depends on: ii geeqie-common 1:1.1-7 ii libc6 2.17-3 ii libexiv2-12 0.23-1 ii libgcc1 1:4.8.0-7 ii libgdk-pixbuf2.0-0 2.28.1-1 ii libglib2.0-02.36.1-2build1 ii libgtk2.0-0 2.24.18-1 ii libjpeg88d-1 ii liblcms11.19.dfsg-1.2 ii liblircclient0 0.9.0~pre1-1 ii libpango1.0-0 1.30.0-1 ii libstdc++6 4.8.0-7 ii libtiff43.9.6-11 Versions of packages geeqie recommends: ii exiftran 2.07-10 ii exiv20.23-1 ii imagemagick 8:6.7.7.10-5 ii librsvg2-common 2.36.1-1 ii ufraw-batch 0.18-2 ii zenity 3.4.0-2 Versions of packages geeqie suggests: pn geeqie-dbg none ii gimp 2.8.4-1 ii libjpeg-progs 8d-1 ii ufraw 0.18-2 ii xpaint 2.9.1.4-3+b2 -- 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#705852: python-fife unnecessary forces you to install a second python version
Package: python-fife Version: 0.3.3+r3-3 Severity: normal Dear Maintainer, python-fife depends on libpython2.6 and libpython2.7. So no matter what python 2 version you have installed on your system it forces you to also install the other version. It should depend on libpython2.6 or libpython2.7. Regards Uwe -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-fife depends on: ii libboost-filesystem1.49.0 1.49.0-3.2 ii libboost-regex1.49.0 1.49.0-3.2 ii libboost-system1.49.0 1.49.0-3.2 ii libc6 2.13-38 ii libgcc11:4.7.2-5 ii libgl1-mesa-glx [libgl1] 8.0.5-4 ii libglee0d1 5.4.0-1 ii libguichan-0.8.1-1 0.8.2-10+b1 ii libguichan-opengl-0.8.1-1 0.8.2-10+b1 ii libguichan-sdl-0.8.1-1 0.8.2-10+b1 ii libogg01.3.0-4 ii libopenal1 1:1.14-4 ii libpng12-0 1.2.49-1 ii libpython2.6 2.6.8-1.1 ii libpython2.7 2.7.3-6 ii libsdl-image1.21.2.12-2 ii libsdl-ttf2.0-02.0.11-2 ii libsdl1.2debian1.2.15-5 ii libstdc++6 4.7.2-5 ii libtinyxml2.6.22.6.2-1 ii libvorbis0a1.3.2-1.3 ii libvorbisfile3 1.3.2-1.3 ii libxcursor11:1.1.13-1 ii python 2.7.3-4 python-fife recommends no packages. python-fife 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#705007: E763: Word characters differ between spell files
Package: vim-runtime Version: 2:7.3.547-7 Severity: normal Dear Maintainer, please update the included English spell files. They are not compatible with spell files which vim automatically downloads from ftp.vim.org: :set spelllang en,de :set spell Cannot find spell file for de in utf-8 Do you want me to try downloading it? Downloading de.utf-8.spl... /tmp/vjEMsg7/0.spl [noeol] 5996L, 2388148C In which directory do you want to write the file: 1. /home/uwe/.vim/spell ~/.vim/spell/de.utf-8.spl [New] 5996L, 2388149C written Do you want me to try getting the .sug file? This will improve making suggestions for spelling mistakes, but it uses quite a bit of memory. Downloading de.utf-8.sug... ~/.vim/spell/de.utf-8.sug [New] 19573L, 7989987C written 1 buffer wiped out Error detected while processing /home/uwe/.vim/spell/de.utf-8.spl: E763: Word characters differ between spell files After that download the error message reappears every time I activate spell checking. When I manually download the current English spell files from http://ftp.vim.org/pub/vim/runtime/spell/ and copy them to /home/uwe/.vim/spell spell checking works as expected without any error messages. Regards Uwe -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash vim-runtime depends on no packages. Versions of packages vim-runtime recommends: ii vim 2:7.3.547-7 ii vim-gnome [vim] 2:7.3.547-7 ii vim-gtk [vim]2:7.3.547-7 vim-runtime 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#704806: postfix: unused parameter: program_directory=/usr/lib/postfix
Package: postfix Version: 2.9.6-2 Severity: minor Dear Maintainer, postfix complains about an unused parameter in /etc/postfix/main.cf. The postfix configuration is not edited manually. dpkg-reconfigure does not fix the problem (see below). Regards Uwe # dpkg-reconfigure postfix [] Stopping Postfix Mail Transport Agent: postfix/usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix .. ok postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix setting synchronous mail queue updates: false setting myorigin setting destinations: [deleted] setting relayhost: setting mynetworks: [deleted] setting mailbox_command setting mailbox_size_limit: 0 setting recipient_delimiter: + setting inet_interfaces: all postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix setting inet_protocols: ipv4 Postfix is now set up with the changes above. If you need to make changes, edit /etc/postfix/main.cf (and others) as needed. To view Postfix configuration values, see postconf(1). After modifying main.cf, be sure to run '/etc/init.d/postfix reload'. Running newaliases postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix [ ok ] Stopping Postfix Mail Transport Agent: postfix. [] Starting Postfix Mail Transport Agent: postfixpostconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix /usr/sbin/postconf: warning: /etc/postfix/main.cf: unused parameter: program_directory=/usr/lib/postfix .. ok -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (750, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages postfix depends on: ii adduser3.113+nmu3 ii cpio 2.11+dfsg-0.1 ii debconf [debconf-2.0] 1.5.49 ii dpkg 1.16.10 ii libc6 2.13-38 ii libdb5.1 5.1.29-5 ii libsasl2-2 2.1.25.dfsg1-6 ii libsqlite3-0 3.7.13-1 ii libssl1.0.01.0.1e-2 ii lsb-base 4.1+Debian8 ii netbase5.0 ii ssl-cert 1.0.32 Versions of packages postfix recommends: ii python 2.7.3-4 Versions of packages postfix suggests: ii bsd-mailx [mail-reader] 8.1.2-0.2006cvs-1 pn dovecot-common none ii libsasl2-modules 2.1.25.dfsg1-6 ii mutt [mail-reader] 1.5.21-6.2 pn postfix-cdb none pn postfix-doc none pn postfix-ldap none pn postfix-mysql
Bug#704806: postfix: unused parameter: program_directory=/usr/lib/postfix
Manually removing the parameter from the config file fixes the problem. So this parameter probably should be deleted from the config file during the postfix upgrade. I don't know which postfix version dropped the support for this parameter. I saw the warning messages the first time after the upgrade today. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703194: kismet does not work in setuid mode
Package: kismet Version: 2011.03.R2-2 Severity: important Dear Maintainer, kismet fails to initialize the WLAN interface when installed in setuid mode and started by a non-root user: ERROR: IPC child Source 'eth1' requires root permissions to open, but we're not running as root. Something is wrong. The user running kismet is in the kismet group: $ id uid=1000(uwe) gid=1000(uwe) groups=1000(uwe), .. ,138(kismet) When started as user root kismet works. None of the kismet binaries is installed setuid root: $ ls -l /usr/bin/kismet* -rwxr-xr-x 1 root root 259 Feb 27 02:01 /usr/bin/kismet -rwxr-xr-x 1 root kismet 632864 Feb 27 02:01 /usr/bin/kismet_capture -rwxr-xr-x 1 root root 1408668 Feb 27 02:01 /usr/bin/kismet_client -rwxr-xr-x 1 root root740524 Feb 27 02:01 /usr/bin/kismet_drone -rwxr-xr-x 1 root root 1426268 Feb 27 02:01 /usr/bin/kismet_server Instead capabilities are used: $ getcap /usr/bin/kismet* /usr/bin/kismet_capture = cap_net_admin,cap_net_raw+eip When I manually set the suid bit on /usr/bin/kismet_capture kismet works for non-root users too. Maybe a required capability is missing? Also, I'm not a capability expert, but shouldn't the permissions on /usr/bin/kismet_capture set to 0750 so that only members of the group kismet are able to execute the program and not anybody else? Regards Uwe -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (500, 'testing-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kismet depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii dpkg 1.16.9 ii libc6 2.13-38 ii libcap21:2.22-1.2 ii libcap2-bin1:2.22-1.2 ii libgcc11:4.7.2-5 ii libncurses55.9-10 ii libnl-3-2003.2.7-4 ii libnl-genl-3-200 3.2.7-4 ii libpcap0.8 1.3.0-1 ii libpcre3 1:8.30-5 ii libstdc++6 4.7.2-5 ii libtinfo5 5.9-10 kismet recommends no packages. Versions of packages kismet suggests: ii festival1:2.1~release-5.1 ii gpsd3.6-4 ii kismet-plugins 2011.03.R2-2 -- Configuration Files: /etc/kismet/kismet.conf changed [not included] The only difference in the config file is the ncsource entry: ncsource=eth1:type=ipw2200 -- debconf information: * kismet/install-setuid: true * kismet/install-users: uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701684: virt-viewer no longer contains virt-viewer
severity 701684 grave thanks Justification: renders package unusable Raising severity to grave as virt-viewer is the basic functionality of this package. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684725: virt-viewer cannot connect to remote VMs
Hi, the patch [1] attached to bug #696435 by Attila Kinali fixes this bug for me (applied to virt-viewer version 0.5.3-1). Regards Uwe [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=fix-remote-ssh-access;att=1;bug=696435 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698977: missing bash completion for dpkg-deb options -R|--raw-extract and --vextract
Package: bash-completion
Version: 1:2.0-1
Severity: normal
Tags: patch
Dear Maintainer,
the bash completion for dpkg-deb with options -R, --raw-extract or
--vextract does not work. The handling for these options is missing
in /usr/share/bash-completion/completions/dpkg.
The attached patch works for me, but it's not extensively tested.
I had to split the function for dpkg and dpkg-deb as the usage of
parameter -R of dpkg and dpkg-deb is not compatible.
Regards
Uwe
PS: Is there a guideline in which order program options should be
listed to ease maintenance? As they are not in alphabetical
order I have used the order from 'dpkg-deb --help' as the 2nd
best guess.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bash-completion depends on:
ii bash 4.2+dfsg-0.1
ii dpkg 1.16.9
bash-completion recommends no packages.
bash-completion suggests no packages.
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/share/bash-completion/completions/dpkg (from
bash-completion package)
--- usr/share/bash-completion/completions/dpkg.orig 2012-06-17 21:09:06.0 +0200
+++ usr/share/bash-completion/completions/dpkg 2013-01-25 23:40:35.710070458 +0100
@@ -32,7 +32,7 @@
}
}
-# Debian dpkg(8) completion
+# Debian dpkg(1) completion
#
_dpkg()
{
@@ -54,7 +54,7 @@
case $prev in
-c|-i|-A|-I|-f|-e|-x|-X|-W|--install|--unpack|--record-avail| \
--contents|--info|--fsys-tarfile|--field|--control|--extract| \
---show)
+--vextract|--show)
_filedir '?(u)deb'
return 0
;;
@@ -85,7 +85,45 @@
COMPREPLY=( $( compgen -W '$( _parse_help $1 )' -- $cur ) )
[[ $COMPREPLY == *= ]] compopt -o nospace
}
-complete -F _dpkg dpkg dpkg-deb dpkg-query
+complete -F _dpkg dpkg dpkg-query
+
+# Debian dpkg-deb(1) completion
+#
+_dpkg_deb()
+{
+local cur prev words cword split
+_init_completion -s || return
+
+_expand || return 0
+
+local i=$cword
+
+# find the last option flag
+if [[ $cur != -* ]]; then
+while [[ $prev != -* $i -ne 1 ]]; do
+i=$((i-1))
+prev=${words[i-1]}
+done
+fi
+
+case $prev in
+-c|-I|-W|-f|-e|-x|-X|-R|--contents|--info|--show|--field|--control| \
+--extract|--vextract|--raw-extract|--fsys-tarfile)
+_filedir '?(u)deb'
+return 0
+;;
+-b|--build)
+_filedir -d
+return 0
+;;
+esac
+
+$split return
+
+COMPREPLY=( $( compgen -W '$( _parse_help $1 )' -- $cur ) )
+[[ $COMPREPLY == *= ]] compopt -o nospace
+}
+complete -F _dpkg_deb dpkg-deb
# Debian GNU dpkg-reconfigure(8) completion
#
Bug#688550: Workaround for bug #688550
Hi, when you only use dpkg and apt or aptitude and never use dselect is it safe to just clear the file /var/lib/dpkg/available with the command dpkg --clear-avail as a workaround for this bug? Or is this file used for anything else than dselect? Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698745: dpkg breaks other packages during installation of a package
Package: dpkg Version: 1.16.9 Severity: grave Justification: causes non-serious data loss Dear Maintainer, before and after the upgrade from squeeze to wheezy I checked my system with debsums. After the upgrade I found several modified files. I tried to fix the changed files by reinstalling the associated packages. But when I reinstall one package to fix the changed files of that package unrelated files from a different package get modified which weren't modified before. The behaviour is not always consistent. Sometimes files of a different package get removed, sometimes they get changed (it looks like they get overwritten by files from the package I install). Sometimes even the reinstallation of the second package which had been broken by the installation of the first package breaks the first package again, creating an error loop. I have seen this behaviour with the same files and packages on more than one system and the systems were running without problems on squeeze before so that I think I can exclude hardware issues. The bug happens with more than one package and I don't see anything which is overwriting files from a different package in these packages. That's why I file this bug against dpkg. But I'm not an expert for debian packages, so be free to reassign the bug to any other package. I also do not know what the appropriate severity for this bug should be. But when the package system corrupts installed files on the system I think that's a release critical bug, hence severity grave. As my description is probably hard to understand I have attached a logfile where I have tried to track the installation problems down to a minimum of commands. There's also a second logfile attached from another upgrade where I have tried to fix the problems by reinstalling the packages with aptitude first. I don't know if this bug is related to bug #687611 as I also had a modified file debian-archive-removed-keys.gpg on all the systems which I have upgraded to wheezy so far. This file has been fixed on all systems by reinstalling the package debian-archive-keyring without any side effects on other packages though. Regards Uwe grappa:~# debsums --changed /usr/share/doc/e2fsprogs/copyright /usr/share/doc/libtiff-tools/README /usr/share/doc/libtiff-tools/TODO /usr/share/doc/libtiff-tools/changelog.Debian.gz /usr/share/doc/libtiff-tools/changelog.gz /var/lib/xine/xine.desktop grappa:~# apt-cache policy e2fsprogs e2fsprogs: Installed: 1.42.5-1 Candidate: 1.42.5-1 Version table: *** 1.42.5-1 0 750 http://ftp.debian.org/debian/ wheezy/main i386 Packages 650 http://ftp.debian.org/debian/ sid/main i386 Packages 100 /var/lib/dpkg/status grappa:~# dpkg -l e2fsprogs Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii e2fsprogs 1.42.5-1 i386 ext2/ext3/ext4 file system utilit grappa:~# md5sum /usr/share/doc/e2fsprogs/copyright 726570c997e520841dbf8f7611b173ae /usr/share/doc/e2fsprogs/copyright grappa:~# grep copyright /var/lib/dpkg/info/e2fsprogs.md5sums 51a47eee51e75de66777fc781af2f063 usr/share/doc/e2fsprogs/copyright grappa:~# dpkg-deb -R /var/cache/apt/archives/e2fsprogs_1.42.5-1_i386.deb /tmp/e2fsprogs grappa:~# grep copyright /tmp/e2fsprogs/DEBIAN/md5sums 51a47eee51e75de66777fc781af2f063 usr/share/doc/e2fsprogs/copyright grappa:~# ll /usr/share/doc/e2fsprogs/copyright /tmp/e2fsprogs/usr/share/doc/e2fsprogs/copyright -rw-r--r-- 1 root root 3586 2012-07-06 15:37 /tmp/e2fsprogs/usr/share/doc/e2fsprogs/copyright -rw-r--r-- 1 root root 995 2012-07-06 15:37 /usr/share/doc/e2fsprogs/copyright grappa:~# dpkg -r --force-remove-essential e2fsprogs dpkg: warning: overriding problem because --force enabled: This is an essential package - it should not be removed. (Reading database ... 568582 files and directories currently installed.) Removing e2fsprogs ... Processing triggers for man-db ... grappa:~# dpkg -i /var/cache/apt/archives/e2fsprogs_1.42.5-1_i386.deb Selecting previously unselected package e2fsprogs. (Reading database ... 568522 files and directories currently installed.) Unpacking e2fsprogs (from .../e2fsprogs_1.42.5-1_i386.deb) ... Setting up e2fsprogs (1.42.5-1) ... Processing triggers for man-db ... grappa:~# debsums --changed /usr/share/doc/e2fsck-static/copyright /usr/share/doc/libtiff-tools/README /usr/share/doc/libtiff-tools/TODO /usr/share/doc/libtiff-tools/changelog.Debian.gz /usr/share/doc/libtiff-tools/changelog.gz /var/lib/xine/xine.desktop grappa:~# apt-cache policy e2fsck-static e2fsck-static: Installed: 1.42.5-1 Candidate: 1.42.5-1 Version table: *** 1.42.5-1 0 750
Bug#698302: munin_stats: wrong values for munin graph
Hi Steve, these are the files: /var/lib/munin/munin-update.stats UD|workstation;c8|5.18 UD|workstation;c2|7.77 UD|server;nd|10.17 UD|workstation;c10|10.43 UD|server;porto|14.43 UD|server;c1|14.62 UT|26.00 /var/lib/munin/munin-graph.stats GS|0.06 GT|total|0.06 Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698302: munin_stats: wrong values for munin graph
Package: munin-plugins-core Version: 2.0.6-3 Severity: normal Dear Maintainer, after upgrading from squeeze to wheezy the munin_stats plugin provides wrong values for the munin graph time (only a fraction of a second) while I can see the munin-graph process running for about half a minute when I watch processes with e.g. top. A graph which shows munin processing times before and after the upgrade to wheezy is attached. Regards Uwe -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages munin-plugins-core depends on: ii munin-common 2.0.6-3 ii perl 5.14.2-16 Versions of packages munin-plugins-core recommends: ii libnet-snmp-perl 6.0.1-2 Versions of packages munin-plugins-core suggests: pn libnet-netmask-perl none ii libnet-telnet-perl3.03-3 ii python2.7.3~rc2-1 ii ruby 4.9 ii ruby1.8 [ruby-interpreter]1.8.7.358-6 ii ruby1.9.1 [ruby-interpreter] 1.9.3.194-5 -- no debconf information attachment: munin_stats-day.png
Bug#688751: viking crashes when used to geotag images
Package: viking Version: 1.3-1 Severity: normal Dear Maintainer, viking crashes when I try to use it to geotag images. To reproduce the bug: - load a GPS track into viking - open the geotag window on that track - add an image - press OK It even crashes when I only try to create a waypoint for the image and not try to update the EXIF data (option Write EXIF disabled). A backtrace is attached below. Regards, Uwe Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xe7ff8b70 (LWP 8042)] 0x080697e9 in ?? () (gdb) bt #0 0x080697e9 in ?? () #1 0x080a95ae in ?? () #2 0x0809219e in ?? () #3 0xf7594768 in g_thread_pool_thread_proxy (data=0x82d7628) at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gthreadpool.c:309 #4 0xf7593d93 in g_thread_proxy (data=0x86f2150) at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gthread.c:801 #5 0xf73efc39 in start_thread (arg=0xe7ff8b70) at pthread_create.c:304 #6 0xf735c23e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages viking depends on: ii libatk1.0-0 2.4.0-2 ii libc6 2.13-35 ii libcairo2 1.12.2-2 ii libcurl3-gnutls 7.26.0-1 ii libexif12 0.6.20-3 ii libexpat1 2.1.0-1 ii libfontconfig1 2.9.0-7 ii libfreetype62.4.9-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgps203.6-4 ii libgtk2.0-0 2.24.10-2 ii libpango1.0-0 1.30.0-1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages viking recommends: ii gpsbabel 1.4.3-1 Versions of packages viking suggests: ii gpsd 3.6-4 -- 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#685817: viking crashes a lot when used to display maps
Hi Rob, thank you for the hint to disable the status bar. It seems to improve the stability a lot, although it does not prevent viking completely from crashing. But that's maybe because I have to switch on the status bar from time to time to check coordinates. Regards, Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688775: nvidia-graphics-drivers: upgrade of nvidia graphics driver wants to install unnecessary packages
Source: nvidia-graphics-drivers
Version: 304.48-1
Severity: normal
Dear Maintainer,
the upgrade of the nvidia graphics drivers on wheezy (from version
302.17-3 to 304.48-1) tries to install more than 50 MB of new,
unnecessary packages:
# aptitude dist-upgrade
The following NEW packages will be installed:
dkms{a} [2.2.0.3-1.1] +347 kB
linux-headers-3.2.0-3-686-pae{a} [3.2.23-1] +9,137 kB
linux-headers-3.2.0-3-common{a} [3.2.23-1] +17.9 MB
linux-headers-686-pae{a} [3.2+45] +28.7 kB
linux-kbuild-3.2{a} [3.2.17-1] +660 kB
nvidia-kernel-dkms{a} [304.48-1] +27.4 MB
The following packages will be upgraded:
libgl1-nvidia-alternatives [302.17-3 - 304.48-1] +6,144 B
libgl1-nvidia-glx [302.17-3 - 304.48-1] +313 kB
libglx-nvidia-alternatives [302.17-3 - 304.48-1] +6,144 B
libnvidia-ml1 [302.17-3 - 304.48-1] +135 kB
libxnvctrl0 [302.17-2 - 304.48-1] +1,024 B
nvidia-alternative [302.17-3 - 304.48-1] +7,168 B
nvidia-glx [302.17-3 - 304.48-1] +26.6 kB
nvidia-settings [302.17-2 - 304.48-1] +1,024 B
nvidia-smi [302.17-3 - 304.48-1] +27.6 kB
nvidia-vdpau-driver [302.17-3 - 304.48-1] +67.6 kB
xserver-xorg-video-nvidia [302.17-3 - 304.48-1] -195 kB
11 packages upgraded, 6 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/22.3 MB of archives. After unpacking 55.8 MB will be used.
Same with apt-get:
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
dkms (2.2.0.3-1.1)
linux-headers-3.2.0-3-686-pae (3.2.23-1)
linux-headers-3.2.0-3-common (3.2.23-1)
linux-headers-686-pae (3.2+45)
linux-kbuild-3.2 (3.2.17-1)
nvidia-kernel-dkms (304.48-1)
The following packages have been kept back:
hpodder (1.1.5.0+nmu2 = 1.1.5.0+nmu3)
The following packages will be upgraded:
libgl1-nvidia-alternatives (302.17-3 = 304.48-1)
libgl1-nvidia-glx (302.17-3 = 304.48-1)
libglx-nvidia-alternatives (302.17-3 = 304.48-1)
libnvidia-ml1 (302.17-3 = 304.48-1)
libxnvctrl0 (302.17-2 = 304.48-1)
nvidia-alternative (302.17-3 = 304.48-1)
nvidia-glx (302.17-3 = 304.48-1)
nvidia-settings (302.17-2 = 304.48-1)
nvidia-smi (302.17-3 = 304.48-1)
nvidia-vdpau-driver (302.17-3 = 304.48-1)
xserver-xorg-video-nvidia (302.17-3 = 304.48-1)
11 upgraded, 6 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/22.3 MB of archives.
After this operation, 55.8 MB of additional disk space will be used.
I guess the problem is that the new nvidia-kernel-amd64 package
has not been migrated to wheezy yet:
# apt-cache policy nvidia-kernel-amd64
nvidia-kernel-amd64:
Installed: 302.17+2
Candidate: 302.17+2
Version table:
304.48+1 0
650 http://ftp.debian.org/debian/ sid/non-free i386 Packages
*** 302.17+2 0
750 http://ftp.debian.org/debian/ wheezy/non-free i386 Packages
100 /var/lib/dpkg/status
Please make sure that the nvidia graphics driver packages always get
migrated together, not separately.
Regards,
Uwe
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (750, 'testing'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688137: libwebkitgtk-1.0-0: midori crashes when using bing maps
Package: libwebkitgtk-1.0-0 Version: 1.8.1-2 Severity: normal Dear Maintainer, when using the Bird's eye view in bing maps midori crashes. It seems to be a webkit bug as the surf browser also crashes on bing maps. I cannot verify the bug with the GtkLauncher because it seems to ignore the http_proxy variable and I'm behind a non-routing firewall. To reproduce the bug in midori: - open bing maps http://www.bing.com/maps/ - activate Bird's eye view - scroll to a place which is covered by the bird's eye view (e.g. Germany/Berlin) - zoom in A crash log is attached below. Regards, Uwe Crash log: Program received signal SIGSEGV, Segmentation fault. JSC::JSCell::toNumber (this=0x0, exec=0xe40c8420) at ../Source/JavaScriptCore/runtime/JSCell.cpp:143 143 ../Source/JavaScriptCore/runtime/JSCell.cpp: No such file or directory. (gdb) bt #0 JSC::JSCell::toNumber (this=0x0, exec=0xe40c8420) at ../Source/JavaScriptCore/runtime/JSCell.cpp:143 #1 0xf5d6d072 in toNumberSlowCase (exec=0xe40c8420, this=0xd0b0) at ../Source/JavaScriptCore/runtime/JSValue.cpp:61 #2 JSC::JSValue::toNumberSlowCase (this=0xd0b0, exec=0xe40c8420) at ../Source/JavaScriptCore/runtime/JSValue.cpp:57 #3 0xf5c7f757 in toNumber (exec=0xe40c8420, this=0xd0b0) at ../Source/JavaScriptCore/runtime/JSCell.h:298 #4 JSC::cti_op_mul (args=optimized out) at ../Source/JavaScriptCore/jit/JITStubs.cpp:2129 #5 0xe0029ec7 in ?? () #6 0xf5c37a2c in execute (globalData=0xe100a1cc, callFrame=0xe40c8040, registerFile=0xf110c33c, this=optimized out) at ../Source/JavaScriptCore/jit/JITCode.h:115 #7 JSC::Interpreter::executeCall (this=0xf110c330, callFrame=0xe3b9f4b4, function=0xe0fcb700, callType=JSC::CallTypeJS, callData=..., thisValue=..., args=...) at ../Source/JavaScriptCore/interpreter/Interpreter.cpp:1211 #8 0xf5d17172 in JSC::call (exec=0xe3b9f4b4, functionObject=..., callType=JSC::CallTypeJS, callData=..., thisValue=..., args=...) at ../Source/JavaScriptCore/runtime/CallData.cpp:39 #9 0xf613631d in call (thisValue=..., functionObject=..., args=..., callData=..., callType=JSC::CallTypeJS, exec=0xe3b9f4b4) ---Type return to continue, or q return to quit--- at ../Source/WebCore/bindings/js/JSMainThreadExecState.h:56 #10 instrumentedCall (args=..., thisValue=..., callData=..., callType=JSC::CallTypeJS, functionObject=..., exec=0xe3b9f4b4, page=0xf10bdee0) at ../Source/WebCore/bindings/js/JSMainThreadExecState.h:75 #11 WebCore::JSCallbackData::invokeCallback (this=0xe03c65e0, args=..., raisedException=0xd36f) at ../Source/WebCore/bindings/js/JSCallbackData.cpp:74 #12 0xf6b7c1d2 in WebCore::JSRequestAnimationFrameCallback::handleEvent (this= 0xe3667e80, time=1348073699743) at ../Source/WebCore/bindings/js/JSRequestAnimationFrameCallbackCustom.cpp:49 #13 0xf6b7c6cb in WebCore::ScriptedAnimationController::serviceScriptedAnimations (this=0xe038a9b0, time=1348073699743) at ../Source/WebCore/dom/ScriptedAnimationController.cpp:145 #14 0xf6b7c9c1 in WebCore::ScriptedAnimationController::animationTimerFired ( this=0xe038a9b0) at ../Source/WebCore/dom/ScriptedAnimationController.cpp:204 #15 0xf6b7cbd5 in WebCore::TimerWebCore::ScriptedAnimationController::fired ( this=0xe038a9cc) at ../Source/WebCore/platform/Timer.h:100 #16 0xf6774642 in WebCore::ThreadTimers::sharedTimerFiredInternal ( this=0xf10fb450) at ../Source/WebCore/platform/ThreadTimers.cpp:115 #17 0xf67746b5 in WebCore::ThreadTimers::sharedTimerFired () ---Type return to continue, or q return to quit--- at ../Source/WebCore/platform/ThreadTimers.cpp:93 #18 0xf70ca02b in WebCore::timeout_cb () at ../Source/WebCore/platform/gtk/SharedTimerGtk.cpp:49 #19 0xf7ea730f in g_timeout_dispatch (source=source@entry=0x572ff678, callback=0xf70ca010 WebCore::timeout_cb(gpointer), user_data=0x0) at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmain.c:3882 #20 0xf7ea6633 in g_main_dispatch (context=0x566488a8) at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmain.c:2539 #21 g_main_context_dispatch (context=context@entry=0x566488a8) at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmain.c:3075 #22 0xf7ea69d0 in g_main_context_iterate (context=0x566488a8, block=block@entry=1, dispatch=dispatch@entry=1, self=error reading variable: Unhandled dwarf expression opcode 0xfa) at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmain.c:3146 #23 0xf7ea6e2b in g_main_loop_run (loop=loop@entry=0x56628038) at /build/buildd-glib2.0_2.32.3-1-i386-987P8N/glib2.0-2.32.3/./glib/gmain.c:3340 #24 0xf7af5ad0 in IA__gtk_main () at /build/buildd-gtk+2.0_2.24.10-2-i386-Tg7Q_2/gtk+2.0-2.24.10/gtk/gtkmain.c---Type return to continue, or q return to quit--- :1256 #25 0x56573bd3 in main () -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy:
Bug#685817: viking crashes a lot when used to display maps
Hi Bernd Unfortunately they are not that useful as you did not have the according -dbg packages installed. That would be at least libglib2.0-0-dbg and libgtk2.0-0-dbg. Here's a crash log and backtrace with the two debug libraries installed. Regards, Uwe $ gdb /usr/bin/viking GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/viking...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/viking [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. ** (viking:14072): WARNING **: Unexpected gpsbabel format string: serial r-r--- wb [New Thread 0xec18ab70 (LWP 14083)] [New Thread 0xeb7ffb70 (LWP 14626)] [New Thread 0xeaffeb70 (LWP 14755)] DEBUG: queue count=90 size=17703720 [New Thread 0xea7fdb70 (LWP 14966)] [New Thread 0xe9ffcb70 (LWP 15213)] DEBUG: queue count=184 size=36194272 [New Thread 0xe97fbb70 (LWP 15220)] [New Thread 0xe8ffab70 (LWP 15226)] DEBUG: queue count=283 size=55668364 [New Thread 0xe87f9b70 (LWP 15228)] [New Thread 0xe7ff8b70 (LWP 15235)] DEBUG: queue count=370 size=72781960 [New Thread 0xe77f7b70 (LWP 15237)] DEBUG: queue count=455 size=89502140 DEBUG: queue count=538 size=105828904 DEBUG: queue count=613 size=120582004 DEBUG: queue count=701 size=137892308 DEBUG: queue count=769 size=151268452 DEBUG: queue count=845 size=166218260 DEBUG: queue count=821 size=161497268 DEBUG: queue count=855 size=168185340 ** (viking:14072): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/0.png ** (viking:14072): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/0 ** (viking:14072): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/1.png ** (viking:14072): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/1 ** (viking:14072): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/2.png ** (viking:14072): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/2 ** (viking:14072): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/3.png ** (viking:14072): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/3 DEBUG: queue count=633 size=124516164 ** (viking:14072): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/4/0.png ** (viking:14072): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/4/0 DEBUG: queue count=721 size=141826468 *** glibc detected *** /usr/bin/viking: double free or corruption (fasttop): 0xe6af0a50 *** === Backtrace: = /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x6e3b1)[0xf72fa3b1] /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x6fc18)[0xf72fbc18] /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x73911)[0xf72ff911] /lib/i386-linux-gnu/i686/cmov/libc.so.6(realloc+0xdd)[0xf72ffd9d] /lib/i386-linux-gnu/libglib-2.0.so.0(+0x4f093)[0xf7575093] === Memory map: 08048000-08134000 r-xp 08:05 262161 /usr/bin/viking 08134000-08148000 rw-p 000ec000 08:05 262161 /usr/bin/viking 08148000-12893000 rw-p 00:00 0 [heap] e620-e62f1000 rw-p 00:00 0 e62f1000-e630 ---p 00:00 0 e640-e64f9000 rw-p 00:00 0 e64f9000-e650 ---p 00:00 0 e650-e65f1000 rw-p 00:00 0 e65f1000-e660 ---p 00:00 0 e660-e66da000 rw-p 00:00 0 e66da000-e670 ---p 00:00 0 e670-e67f9000 rw-p 00:00 0 e67f9000-e680 ---p 00:00 0 e680-e68f1000 rw-p 00:00 0 e68f1000-e690 ---p 00:00 0 e690-e69f1000 rw-p 00:00 0 e69f1000-e6a0 ---p 00:00 0 e6a0-e6af1000 rw-p 00:00 0 e6af1000-e6b0 ---p 00:00 0 e6b0-e6bf1000 rw-p 00:00 0 e6bf1000-e6c0 ---p 00:00 0 e6c0-e6cff000 rw-p 00:00 0 e6cff000-e6d0 ---p 00:00 0 e6d0-e6df1000 rw-p 00:00 0 e6df1000-e6e0 ---p 00:00 0 e6e0-e6e4a000 rw-p 00:00 0 e6e4a000-e6f0 ---p 00:00 0 e6ff7000-e6ff8000 ---p 00:00 0 e6ff8000-e77f8000 rw-p 00:00 0 e77f8000-e77f9000 ---p 00:00 0 e77f9000-e7ff9000 rw-p 00:00 0 e7ff9000-e7ffa000 ---p 00:00 0 e7ffa000-e87fa000 rw-p 00:00 0 e87fa000-e87fb000 ---p 00:00 0
Bug#685817: viking crashes a lot when used to display maps
Package: viking Version: 1.3-1 Severity: important Dear Maintainer, since I have upgraded from squeeze to wheezy viking crashes a lot when used to display maps. To reproduce the crash I can start viking, add a new map layer (e.g. Mapnik), activate autodownload maps, then repeatedly scroll the map, zoom in, zoom out and sooner or later viking crashes. I had 5 crashes in less than an hour using viking which makes it quite unusable, hence severity important. Three examples of such crashes with viking running in gdb are attached below (empty lines in output removed). Regards, Uwe $ gdb /usr/bin/viking GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/viking...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/viking [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [New Thread 0xec18ab70 (LWP 17688)] [Thread 0xec18ab70 (LWP 17688) exited] [New Thread 0xec18ab70 (LWP 17689)] [New Thread 0xeb7ffb70 (LWP 17690)] DEBUG: queue count=100 size=19670800 [New Thread 0xeaffeb70 (LWP 17691)] [New Thread 0xea7fdb70 (LWP 17692)] DEBUG: queue count=200 size=39341600 [New Thread 0xe9ffcb70 (LWP 17693)] [New Thread 0xe97fbb70 (LWP 17694)] DEBUG: queue count=300 size=59012400 [New Thread 0xe8ffab70 (LWP 17695)] [New Thread 0xe87f9b70 (LWP 17696)] DEBUG: queue count=400 size=78683200 [New Thread 0xe7ff8b70 (LWP 17697)] [New Thread 0xe77f7b70 (LWP 17698)] DEBUG: queue count=500 size=98354000 [Thread 0xe97fbb70 (LWP 17694) exited] [Thread 0xe7ff8b70 (LWP 17697) exited] [Thread 0xeaffeb70 (LWP 17691) exited] [Thread 0xe9ffcb70 (LWP 17693) exited] [Thread 0xe8ffab70 (LWP 17695) exited] [Thread 0xec18ab70 (LWP 17689) exited] [Thread 0xeb7ffb70 (LWP 17690) exited] [Thread 0xea7fdb70 (LWP 17692) exited] DEBUG: queue count=600 size=118024800 [New Thread 0xea7fdb70 (LWP 17702)] [New Thread 0xeb7ffb70 (LWP 17705)] [New Thread 0xec18ab70 (LWP 17706)] [New Thread 0xe8ffab70 (LWP 17707)] [New Thread 0xeaffeb70 (LWP 17709)] [New Thread 0xe9ffcb70 (LWP 17710)] [New Thread 0xe97fbb70 (LWP 17712)] [New Thread 0xe7ff8b70 (LWP 17713)] ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/0.png ** (viking:17677): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/0 DEBUG: queue count=688 size=135335104 DEBUG: queue count=779 size=153235532 ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/1.png ** (viking:17677): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/1 ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/2.png ** (viking:17677): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/2 DEBUG: queue count=822 size=161693976 DEBUG: queue count=919 size=180774652 ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/3.png ** (viking:17677): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/3 DEBUG: queue count=996 size=195921168 ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/4/0.png ** (viking:17677): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/4/0 DEBUG: queue count=1077 size=211854516 ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/4/1.png ** (viking:17677): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/4/1 ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/0.png ** (viking:17677): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/0 ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/1.png ** (viking:17677): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/1 ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/2.png ** (viking:17677): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/2 ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/-1/3.png ** (viking:17677): WARNING **: Download error: /home/uwe/.viking-maps/t13s15z0/-1/3 ** (viking:17677): WARNING **: curl_download_uri: http response: 404 for uri http://tile.openstreetmap.org/2/4/0.png ** (viking:17677): WARNING **: Download
Bug#685085: viking warns about not having unbuffer in path
Package: viking Version: 1.3-1 Severity: minor Dear Maintainer, viking warns about not having unbuffer in path when the package expect-dev is not installed: ** (viking:22671): WARNING **: unbuffer not found in PATH Also the viking homepage recommends unbuffer (http://sourceforge.net/apps/mediawiki/viking/index.php?title=Source_code). I don't know why unbuffer is in a development and not in a utility package, but shouldn't viking nevertheless suggest or maybe recommend this package? Regards, Uwe -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages viking depends on: ii libatk1.0-0 2.4.0-2 ii libc6 2.13-33 ii libcairo2 1.12.2-2 ii libcurl3-gnutls 7.26.0-1 ii libexif12 0.6.20-3 ii libexpat1 2.1.0-1 ii libfontconfig1 2.9.0-7 ii libfreetype62.4.9-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgps203.6-4 ii libgtk2.0-0 2.24.10-2 ii libpango1.0-0 1.30.0-1 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages viking recommends: ii gpsbabel 1.4.3-1 Versions of packages viking suggests: ii gpsd 3.6-4 -- 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#684725: virt-viewer cannot connect to remote VMs
Package: virt-viewer Version: 0.5.3-1 Severity: important Dear Maintainer, after upgrade from squeeze to wheezy virt-viewer cannot connect to remote VMs anymore: $ virt-viewer -v -c qemu+ssh://vir/system centos Opening connection to libvirt with URI qemu+ssh://vir/system Guest centos is running, determining display Guest centos has a vnc display Opening indirect TCP connection to display at vir:5901 Setting up SSH tunnel via vir Guest centos display has disconnected, shutting down$ Installing the virt-viewer locally on the VM host and starting it there works: $ virt-viewer -v -c qemu:///system centos Opening connection to libvirt with URI qemu:///system Guest centos is running, determining display Guest centos has a vnc display Opening direct TCP connection to display at localhost:5901:-1 (virt-viewer:24900): Gtk-WARNING **: Could not find the icon 'preferences-desktop-keyboard-shortcuts'. The 'hicolor' theme was not found either, perhaps you need to install it. You can get a copy from: http://icon-theme.freedesktop.org/releases Remote access by forwarding the VNC port manually with ssh and using a VNC viewer also works: $ ssh -R 5901:localhost:5901 vir $ xvncviewer localhost:1 VNC Viewer Free Edition 4.1.1 for X - built Mar 10 2010 21:40:13 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Mon Aug 13 15:04:51 2012 CConn: connected to host localhost port 5901 CConnection: Server supports RFB protocol version 3.8 CConnection: Using RFB protocol version 3.8 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding Regards, Uwe -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (1750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages virt-viewer depends on: ii libc6 2.13-33 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgtk-3-0 3.4.2-2 ii libgtk-vnc-2.0-00.5.0-3 ii libvirt00.9.12-3 ii libxml2 2.8.0+dfsg1-5 virt-viewer recommends no packages. Versions of packages virt-viewer suggests: ii netcat-openbsd [netcat] 1.105-7 ii netcat-traditional [netcat] 1.10-40 -- 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#684775: qemu-kvm: cannot boot a wheezy guest with SMP and less than 927 MB of RAM
Package: qemu-kvm Version: 1.1.0+dfsg-3 Severity: normal Dear Maintainer, after upgrading the host system from squeeze to wheezy a guest system with wheezy does not boot anymore. Before the upgrade the same guest system was running without problems with the following options (with squeeze as host system): $ kvm -smp 2 -m 512 -drive file=/local/kvm/wheezy.img,index=0,media=disk When I disable the smp option the guest system also boots with wheezy as host system. It even boots successfully with very low RAM settings: $ kvm -m 48 -curses -drive file=/local/kvm/wheezy.img,index=0,media=disk # free total used free sharedbuffers cached Mem: 43388 38856 4532 0 2588 20328 -/+ buffers/cache: 15940 27448 Swap: 489944132 489812 When I enable the smp option with wheezy as host system I have to give the same wheezy guest system at least 927 MB of RAM to be able to boot: $ kvm -smp 2 -m 927 -curses -drive file=/local/kvm/wheezy.img,index=0,media=disk # free total used free sharedbuffers cached Mem:935632 47060 888572 0 2932 24264 -/+ buffers/cache: 19864 915768 Swap: 489944 0 489944 If I supply less than 927 MB of RAM the guest boot fails with the following error messages: $ kvm -smp 2 -m 926 -curses -drive file=/local/kvm/wheezy.img,index=0,media=disk Loading, please wait...20120603_194846-gandalf) modprobe: module unix not found in modules.dep [ 28.008023] BUG: soft lockup - CPU#0 stuck for 23s! [busybox:155] [ 28.008402] Process busybox (pid: 155, ti=f72ca000 task=f710d6a0 task.ti=f72c a000)(http://ipxe.org) 00:03.0 C900 PCI2.10 PnP PMM+39DC9CA0+39D89CA0 C900 [ 28.008733] Stack: [ 28.008899] Call Trace: [ 28.009172] Code: 0f 30 31 c0 57 89 c6 53 6a 00 55 68 43 d1 35 c1 e8 ad 6f 29 00 89 f0 83 c4 14 5b 5e 5f 5d c3 90 56 89 c6 53 89 d3 8b 00 8b 56 04 f0 0f c7 0e 75 fa 5b 5e c3 9c 58 c3 50 9d c3 fa c3 fb c3 fb f4 If I reduce the memory further the error messages slightly change: $ kvm -smp 2 -m 925 -curses -drive file=/local/kvm/wheezy.img,index=0,media=disk Loading, please wait...20120603_194846-gandalf) [ 28.008015] BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:119] [ 28.008373] Process modprobe (pid: 119, ti=f728c000 task=f7262900 task.ti=f72 8c000) [ 28.008709] Stack:) 00:03.0 C900 PCI2.10 PnP PMM+39CC9CA0+39C89CA0 C900 [ 28.008875] Call Trace: [ 28.009119] Code: 0f 30 31 c0 57 89 c6 53 6a 00 55 68 43 d1 35 c1 e8 ad 6f 29 00 89 f0 83 c4 14 5b 5e 5f 5d c3 90 56 89 c6 53 89 d3 8b 00 8b 56 04 f0 0f c7 0e 75 fa 5b 5e c3 9c 58 c3 50 9d c3 fa c3 fb c3 fb f4 [ 28.024012] BUG: soft lockup - CPU#1 stuck for 23s! [modprobe:62] [ 28.024324] Process modprobe (pid: 62, ti=f70e2000 task=f70bf240 task.ti=f70e 2000) [ 28.024653] Stack: [ 28.024819] Call Trace: [ 28.025016] Code: f0 ff 08 79 05 e8 44 6d 10 00 c3 f0 81 28 00 00 10 00 74 05 e8 19 6d 10 00 c3 ba 00 01 00 00 f0 66 0f c1 10 0f b6 ce 38 ca 74 06 f3 90 8a 10 eb f6 c3 53 66 8b 10 89 c1 31 c0 38 d6 75 16 8d 9a $ kvm -smp 2 -m 924 -curses -drive file=/local/kvm/wheezy.img,index=0,media=disk Loading, please wait...20120603_194846-gandalf) [ 28.008012] BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:120] [ 28.008373] Process modprobe (pid: 120, ti=f7264000 task=f63e4560 task.ti=f72 64000) [ 28.008733] Stack:) 00:03.0 C900 PCI2.10 PnP PMM+39BC9CA0+39B89CA0 C900 [ 28.008900] Call Trace: [ 28.009141] Code: 0f 30 31 c0 57 89 c6 53 6a 00 55 68 43 d1 35 c1 e8 ad 6f 29 00 89 f0 83 c4 14 5b 5e 5f 5d c3 90 56 89 c6 53 89 d3 8b 00 8b 56 04 f0 0f c7 0e 75 fa 5b 5e c3 9c 58 c3 50 9d c3 fa c3 fb c3 fb f4 [ 28.028012] BUG: soft lockup - CPU#1 stuck for 23s! [modprobe:67] [ 28.028343] Process modprobe (pid: 67, ti=f70ec000 task=f70be620 task.ti=f70e c000) [ 28.028672] Stack: [ 28.028839] Call Trace: [ 28.029040] Code: 05 e8 44 6d 10 00 c3 f0 81 28 00 00 10 00 74 05 e8 19 6d 10 00 c3 ba 00 01 00 00 f0 66 0f c1 10 0f b6 ce 38 ca 74 06 f3 90 8a 10 eb f6 c3 53 66 8b 10 89 c1 31 c0 38 d6 75 16 8d 9a 00 01 00 00 $ kvm -smp 2 -m 923 -curses -drive file=/local/kvm/wheezy.img,index=0,media=disk Loading, please wait...20120603_194846-gandalf) [ 28.008014] BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:113] [ 28.008368] Process modprobe (pid: 113, ti=f725a000 task=f72110c0 task.ti=f72 5a000) [ 28.008706] Stack:) 00:03.0 C900 PCI2.10 PnP PMM+39AC9CA0+39A89CA0 C900 [ 28.008871] Call Trace: [ 28.009112] Code: 0f 30 31 c0 57 89 c6 53 6a 00 55 68 43 d1 35 c1 e8 ad 6f 29 00 89 f0 83 c4 14 5b 5e 5f 5d c3 90 56 89 c6 53 89 d3 8b 00 8b 56 04 f0 0f c7 0e 75 fa 5b 5e c3 9c 58 c3 50 9d c3 fa c3 fb c3 fb f4 [ 28.028012] BUG: soft lockup - CPU#1 stuck for 23s! [udevd:118] [ 28.028316] Process udevd (pid: 118, ti=f7284000 task=f72148c0 task.ti=f72840 00) [ 28.028637] Stack: [ 28.028802] Call Trace: [
Bug#684150: python-wxgtk2.8 breaks upgrade from squeeze to wheezy
Package: python-wxgtk2.8 Version: 2.8.12.1-11 Severity: critical Justification: breaks the whole system Hello, the upgrade from squeeze to wheezy aborts with the following error message: E: Could not perform immediate configuration on 'python-wxgtk2.8'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2) After this error the package system is in a broken state, apt cannot continue the upgrade: # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... failed. The following packages have unmet dependencies: bup : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed gimp : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed idle : Depends: python (= 2.6.6-3+squeeze7) but 2.7.3~rc2-1 is installed jack : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed mayavi2 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed mercurial : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed miro : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed multiarch-support : Depends: libc6 (= 2.13-5) but 2.11.3-3 is installed pida : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python : Depends: python-minimal (= 2.7.3~rc2-1) but 2.6.6-3+squeeze7 is installed python-apt : Breaks: python (= 2.7) but 2.7.3~rc2-1 is installed python-bluez : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-cairo : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-crypto : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-dbus : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-dev : Depends: python (= 2.6.6-3+squeeze7) but 2.7.3~rc2-1 is installed python-egenix-mxdatetime : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-egenix-mxtools : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-eggtrayicon : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-fuse : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gammu : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gconf : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gda : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gdl : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gksu2 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-glade2 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gmenu : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gnome2 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gnomekeyring : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gobject : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gpod : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gps : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gst0.10 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gtk2 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gtkglext1 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gtkmozembed : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gtksourceview2 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-gtkspell : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-httplib2 : Breaks: python (= 2.7) but 2.7.3~rc2-1 is installed python-imaging : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-imaging-tk : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-jppy : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-libtorrent : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-libxml2 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-mapnik : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-markupsafe : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-mmkeys : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-mysqldb : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-newt : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-notify : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-numpy : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-openal : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-osmgpsmap : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-psyco : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-pycurl : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-pygame : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-pyorbit : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-pysqlite2 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-pyx : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-qscintilla2 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-qt3 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-qt4 : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed python-qtext : Depends: python ( 2.7) but 2.7.3~rc2-1 is installed
Bug#684079: binutils: missing md5sums control file in the dpkg database
Package: binutils Version: 2.22-6.1 Severity: normal Dear Maintainer, the upgrade from squeeze to wheezy results in an incorrectly installed binutils package (2.20.1-16 = 2.22-6.1). # dpkg --audit The following packages are missing the md5sums control file in the database, they need to be reinstalled: binutils GNU assembler, linker and binary utilities Reinstalling the package fixes the problem. Regards, Uwe -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (750, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages binutils depends on: ii libc6 2.13-33 ii libgcc1 1:4.7.1-2 ii libstdc++6 4.7.1-2 ii zlib1g 1:1.2.7.dfsg-13 binutils recommends no packages. Versions of packages binutils suggests: pn binutils-doc none -- 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#682137: reportbug fails to use a http proxy
Hello, same problem here, reportbug fails to access the BTS through a proxy. When the proxy is configured in ~/.reportbugrc reportbug also fails to access the package database: $ grep proxy ~/.reportbugrc # Your proxy server address http_proxy http://http-proxy.ibr.ch:8080/; $ reportbug Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. binutils [..] Using 'Uwe Storbeck u...@ibr.ch' as your from address. Getting status for binutils... Checking for newer versions at madison... Querying Debian BTS for reports on binutils (source)... Unable to connect to Debian BTS; continue [y|N|?]? When I set the proxy from the shell environment reportbug at least can access the package database, but still fails to access the bug tracker: $ http_proxy=http://http-proxy.ibr.ch:8080/ reportbug Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. binutils [..] Using 'Uwe Storbeck u...@ibr.ch' as your from address. Getting status for binutils... Checking for newer versions at madison... Your version (2.22-6.1) of binutils appears to be out of date. The following newer release(s) are available in the Debian archive: experimental: 2.22.90.20120731-1 unstable: 2.22-7.1 Do you still want to file a report [y|N|q|?]? y Querying Debian BTS for reports on binutils (source)... Unable to connect to Debian BTS; continue [y|N|?]? Regards, Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672855: vainfo: Package in wrong section
Package: vainfo Version: 1.0.1-3 Severity: minor The section is set to libs, but the package provides a binary and no libraries. Package: vainfo Status: install ok installed Priority: optional Section: libs [..] Regards Uwe -- System Information: Debian Release: 6.0.5 APT prefers stable APT policy: (850, 'stable'), (840, 'stable-updates'), (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vainfo depends on: ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libva-x11-1 1.0.1-3Video Acceleration (VA) API for Li ii libva11.0.1-3Video Acceleration (VA) API for Li ii libx11-6 2:1.3.3-4 X11 client-side library vainfo recommends no packages. vainfo 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#511812: Is this still a problem?
Hello Rolf, I'm using a different ISDN card driver now, which is not compatible with isdnlog. So I cannot recheck it for newer versions of isdnlog at the moment (if there are any). But the bug still was valid after the upgrade to the current stable release (squeeze). Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613124: [Logcheck-devel] Bug#613124: rule update for changed snmp log messages
On Sep 02, Hannes von Haugwitz wrote: Does logcheck really report those log lines? Actually logcheck removes all trailing whitespaces before applying the rules. Sorry, I did not know that logcheck strips trailing spaces now. I only checked the pattern with egrep against syslog. It matched on one of my servers but not on another. But with logcheck it works on all servers. So ignore my last message. ;) Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613124: rule update for changed snmp log messages
For me these log messages contain a space at the end of the line
(snmpd version 5.4.3~dfsg-2). So this rule may need an additional
? or * at the end to work for all cases:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ snmpd\[[0-9]+\]: Connection from UDP:
\[[.0-9]{7,15}\]:[0-9]{4,5}-\[[.0-9]{7,15}\] ?$
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631970: package vainfo in wrong section?
Package: vainfo Version: 1.0.1-3 Severity: minor Hi, shouldn't this package be in a different section, not libs? It only contains a binary plus documentation and no libraries. At least deborphan gets confused about it and reports it wrongly. Regards Uwe -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (850, 'stable'), (840, 'stable-updates'), (750, 'testing'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vainfo depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libva-x11-1 1.0.1-3Video Acceleration (VA) API for Li ii libva11.0.1-3Video Acceleration (VA) API for Li ii libx11-6 2:1.3.3-4 X11 client-side library vainfo recommends no packages. vainfo 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#620620: x11vnc: mouse and keyboard events are always sent to the first screen of a multiscreen display
Package: x11vnc Version: 0.9.10-1.1 Severity: important When you connect to a multiscreen display with x11vnc and you don't connect to the first screen of the remote display (e.g. to :0.1) your mouse and keyboard events still get sent to the first screen (:0.0) and not to the screen you are connected to. This makes x11vnc useless for multiscreen displays, hence severity important. Version 0.9.3.dfsg.1-1 on lenny was working as expected. Regards Uwe -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (850, 'stable'), (750, 'testing'), (650, 'unstable'), (500, 'stable-updates'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages x11vnc depends on: ii libavahi-client3 0.6.27-2+squeeze1 Avahi client library ii libavahi-common3 0.6.27-2+squeeze1 Avahi common library ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libjpeg62 6b1-1 The Independent JPEG Group's JPEG ii libssl0.9.80.9.8o-4squeeze1 SSL shared libraries ii libvncserver0 0.9.7-2+b1API to write one's own vnc server ii libx11-6 2:1.3.3-4 X11 client-side library ii libxdamage11:1.1.3-1 X11 damaged region extension libra ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar ii libxfixes3 1:4.0.5-1 X11 miscellaneous 'fixes' extensio ii libxinerama1 2:1.1-3 X11 Xinerama extension library ii libxrandr2 2:1.3.0-3 X11 RandR extension library ii libxtst6 2:1.1.0-3 X11 Testing -- Record extension li ii openssl0.9.8o-4squeeze1 Secure Socket Layer (SSL) binary a ii tk 8.4.16-2 The Tk toolkit for Tcl and X11 (de ii x11vnc-data0.9.10-1.1data files for x11vnc ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime x11vnc recommends no packages. x11vnc 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#620620: x11vnc: mouse and keyboard events are always sent to the first screen of a multiscreen display
Package: x11vnc Version: 0.9.12-1 This bug is also present in x11vnc version 0.9.12-1. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559194: Unused automatically installed packages don't get removed on upgrade
On Mar 30, David Kalnischkies wrote: Common pratice is it to place a package in 'oldlibs' section as it will be grabbed by deborphan then. You can switch the priority, too, and the description should be changed. If this will be a policy obeyed by all packages the problem would be solved. deborphan would list the obsolete package and give you the hint to check it. That's not perfect, but still would give you all information to keep your system clean. So file the bug against the package which does not conform to this policy? Or is this common practice voluntarily? If its priority extra, being in oldlibs and the description says something about a transitional package, it is way easier to hit 'yes'… Agreed. A clear policy for unique tagging or at least a unique description of obsolete packages instead of the current dummy, obsolete, transitional, can be removed safely mess would be helpful too. Best at last: Now that support has landed in squeeze APT and dpkg for 'disappearing packages', try this to avoid the transition package mess alltogether. I did not know about that so far, thanks for the hint. On a first view it sounds somewhat dangerous for the consistency of package databases to me. I guess I would have preferred a clear policy and tagging for transitional packages instead. But that's going off-topic here ... Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559194: Unused automatically installed packages don't get removed on upgrade
On Mar 30, David Kalnischkies wrote:
As far as i know its just voluntary, but after all, IANAD{D,M},
so take everything i say with a bit of salt.
I agree with you that it's probably not the best idea to fix this
problem by changing the behaviour of package managers. But I also
think this bug can not be solved by a voluntary common practice
which may be not so common. ;)
As far as I understand it the support for disappearing packages
does not make transitional packages completely obsolete.
So is there any pseudo-package to reassign this bug to to help
establishing such a policy for transitional packages?
Maybe someone who's more familiar with debian internals or bts
can help?
Regards
Uwe
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559194: Unused automatically installed packages don't get removed on upgrade
On Mar 26, David Kalnischkies wrote: policy says about priority required: Packages which are necessary for the proper functioning of the system (usually, this means that dpkg functionality depends on these packages). We are talking about obsolete packages. These packages are not required anymore by the system. Actually they are not even used anymore and are garbage only. I wouldn't consider this a bug in APT and co as its way easier to break your system than it is useful in helping cleaning up… apt knows when a package is obsolete and not used anymore. So it could remove those packages with no harm to the system. Debian has a good reputation for long term stability and upgradability. That's why there should be a standard mechanism to get rid of old, obsolete packages which are not used anymore, even when they have been required for the system at some point. I do not say that apt and co have to handle this case. It also could be handled by another mechanism (e.g. by transitional packages which reduce the priority when a packages is not required by the system anymore). But it should be handled at all. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559194: Unused automatically installed packages don't get removed on upgrade
reassign 559194 aptitude,apt thanks Same problem occurs when you upgrade a stable system (like from lenny to squeeze). Some packages don't get removed although they are marked as automatically installed and no other package depends on them. I also guess those packages don't get removed by any package tool because they are set to priority required. It affects apt, aptitude and other package tools like deborphan. If you don't want to remove packages with priority required directly because of stability reasons than maybe resolve the problem by policy: To remove a required package always add a transitional package with reduced priority so that package tools can remove the package with standard mechanisms. Regards Uwe Package libcap1 as an example: # aptitude search libcap1 i A libcap1 - support for getting/setting POSIX.1e capab == the package is installed and marked as automatically installed # aptitude why libcap1 Unable to find a reason to install libcap1. == no other package depends on it, recommends or suggests it # aptitude search '~o'|grep libcap1 i A libcap1 - support for getting/setting POSIX.1e capab # apt-cache policy libcap1 libcap1: Installed: 1:1.10-14 Candidate: 1:1.10-14 Version table: *** 1:1.10-14 0 100 /var/lib/dpkg/status == the package is obsolete and not in the debian repository anymore # aptitude upgrade No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Do you want to continue? [Y/n/?] == but it still doesn't get removed # apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. == apt also ignores it # deborphan --guess-all == even deborphan does not recognise it # dpkg -s libcap1 Package: libcap1 Status: install ok installed Priority: required Section: libs [..] == package priority is required, probably the reason for the special handling -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612977: Warning: ignored obsolete keyword (null)
Hi Harald Hmmm I understand but this shouldn't have broken your config as the keyword is still implemented by the parser (and removed keywords should be detected and alerted by the init script). I don't think it has broken my config. The best guess I can do from what I remember is that I had swapped left and right peer in my old config (copied same config file for both sides of the connection) which the old openswan version obviously has tolerated and the new one - correctly - doesn't anymore. But the bug report wasn't about breaking my config but about not to tell me what keyword in my config is obsolete. If you have a running configuration such a message doesn't matter much. But when your configuration is broken such a message adds confusion as you don't know if it's the reason for the break or not. Sorry for beeing misleading there. For this report should we consider this a wishlist entry or close it completely (as it seems the original problem did not have anything to do with the null entry)? I still consider it a bug when a program complains about obsolete keywords and then tell you null instead of the name of the keyword. It either should not try to tell you the name at all or - of course more user friendly - tell the correct name. But you are right, severity of the bug rather should have been minor. I'll change it. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612977: Warning: ignored obsolete keyword (null)
Hello Harald, thanks for your offer. Meanwhile my VPN is running again. Not sure what the exact propblem was. I partially rewrote my config from scratch, forced the use of the netkey protocol stack and had to disable compression. The warnings about the obsolete keyword probably were caused by the keyword 'forwardcontrol'. I don't know why compression does not work anymore, but I guess I will look into that when my peer also is upgraded to squeeze. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614834: kdiff3 does not remember the setting for Show White Space
Package: kdiff3 Version: 0.9.95-6 Severity: important Since the upgrade from lenny to squeeze kdiff3 does not remember the setting for Show White Space anymore. I also haven't found any option under Diff settings to configure this option in the program settings. So you have to enable the option after every start of the program manually. If you forget to enable it you may overlook (whitespace) changes in a file unintentionally. Hence severity important. Even if you enable Show White Space you cannot navigate between the whitespace differences with the arrow up and arrow down buttons. If you compare two files with white space differences only both buttons stay greyed out even with white space differences enabled. Regards Uwe -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (850, 'stable'), (650, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kdiff3 depends on: ii kdebase-runtime 4:4.4.5-1 runtime components from the offici ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libkdecore5 4:4.4.5-2 the KDE Platform Core Library ii libkdeui5 4:4.4.5-2 the KDE Platform User Interface Li ii libkio5 4:4.4.5-2 the Network-enabled File Managemen ii libkonq5 4:4.4.5-2 core libraries for Konqueror ii libkparts44:4.4.5-2 the Framework for the KDE Platform ii libqt4-dbus 4:4.6.3-4 Qt 4 D-Bus module ii libqt4-network4:4.6.3-4 Qt 4 network module ii libqt4-qt3support 4:4.6.3-4 Qt 3 compatibility library for Qt ii libqt4-svg4:4.6.3-4 Qt 4 SVG module ii libqt4-xml4:4.6.3-4 Qt 4 XML module ii libqtcore44:4.6.3-4 Qt 4 core module ii libqtgui4 4:4.6.3-4 Qt 4 GUI module ii libstdc++64.4.5-8The GNU Standard C++ Library v3 Versions of packages kdiff3 recommends: ii kdiff3-doc0.9.95-6 documentation for kdiff3 kdiff3 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#614584: fdisk: cannot handle sector numbers of 2^31 and above
Package: util-linux
Version: 2.17.2-9
Severity: normal
fdisk recommends to switch display units to sectors. But it
cannot handle sector numbers of 2^31 and above. Even worse it
silently fails to set such sector numbers (see example below).
So you cannot align partitions exactly for harddisks with more
than 1 TB capacity.
Regards
Uwe
Example:
# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF
disklabel
Building a new DOS disklabel with disk identifier 0x5653f3d0.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.
Warning: invalid flag 0x of partition table 4 will be corrected by w(rite)
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): c
DOS Compatibility flag is not set
Command (m for help): u
Changing display/entry units to sectors
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First sector (2048-3907029167, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-3907029167, default 3907029167):
30
Command (m for help): p
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5653f3d0
Device Boot Start End Blocks Id System
/dev/sdb12048 2147483647 1073740800 83 Linux
Command (m for help): q
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (850, 'stable'), (650, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages util-linux depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii dpkg1.15.8.10Debian package management system
ii initscripts 2.88dsf-13.1 scripts for initializing and shutt
ii install-info4.13a.dfsg.1-6 Manage installed documentation in
ii libblkid1 2.17.2-9 block device id library
ii libc6 2.11.2-10Embedded GNU C Library: Shared lib
ii libncurses5 5.7+20100313-5 shared libraries for terminal hand
ii libselinux1 2.0.96-1 SELinux runtime shared libraries
ii libslang2 2.2.2-4 The S-Lang programming library - r
ii libuuid12.17.2-9 Universally Unique ID library
ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii tzdata 2010o-1 time zone and daylight-saving time
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
util-linux recommends no packages.
Versions of packages util-linux suggests:
ii console-tools1:0.2.3dbs-69.1 Linux console and font utilities
ii dosfstools 3.0.9-1 utilities for making and checking
pn util-linux-locales none (no description available)
-- debconf information:
util-linux/noauto-with-nonzero-passnum:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612977: Warning: ignored obsolete keyword (null)
Package: openswan Version: 1:2.6.28+dfsg-5 Severity: normal The upgrade to squeeze broke my vpn connection. So far I do not know why, maybe because of obsolete parameters in my config. But getting a lot of warnings about obsolete keywords without giving the name of the obsolete keyword and printing (null) instead is not very helpful: Feb 12 01:46:24 c10 ipsec_starter[9681]: Warning: ignored obsolete keyword (null) Feb 12 01:46:24 c10 ipsec_starter[9682]: Warning: ignored obsolete keyword (null) Feb 12 01:46:25 c10 ipsec_setup: Warning: ignored obsolete keyword (null) Feb 12 01:46:25 c10 ipsec_starter[9756]: Warning: ignored obsolete keyword (null) Feb 12 01:46:25 c10 ipsec__plutorun: Warning: ignored obsolete keyword (null) Feb 12 01:46:25 c10 ipsec_starter[9767]: Warning: ignored obsolete keyword (null) Feb 12 01:46:25 c10 ipsec__plutorun: Warning: ignored obsolete keyword (null) Feb 12 01:46:25 c10 ipsec_starter[9768]: Warning: ignored obsolete keyword (null) Feb 12 01:46:25 c10 ipsec__plutorun: Warning: ignored obsolete keyword (null) Feb 12 01:46:25 c10 ipsec_starter[9769]: Warning: ignored obsolete keyword (null) Regards Uwe -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (850, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openswan depends on: ii bind9-host [host]1:9.7.2.dfsg.P3-1.1 Version of 'host' bundled with BIN ii bsdmainutils 8.0.13 collection of more utilities from ii debconf [debconf-2.0 1.5.36.1Debian configuration management sy ii iproute 20100519-3 networking and traffic control too ii ipsec-tools 1:0.7.3-12 IPsec tools for Linux ii libc62.11.2-10 Embedded GNU C Library: Shared lib ii libcurl3 7.21.0-1Multi-protocol file transfer libra ii libgmp3c22:4.3.2+dfsg-1 Multiprecision arithmetic library ii libldap-2.4-22.4.23-7OpenLDAP libraries ii libpam0g 1.1.1-6.1 Pluggable Authentication Modules l ii openssl 0.9.8o-4Secure Socket Layer (SSL) binary a openswan recommends no packages. Versions of packages openswan suggests: pn curl none (no description available) ii openswan-doc 1:2.6.28+dfsg-5 Internet Key Exchange daemon - doc pn openswan-modules-source none (no description available) -- Configuration Files: /etc/ipsec.conf [Errno 13] Permission denied: u'/etc/ipsec.conf' /etc/ipsec.secrets [Errno 13] Permission denied: u'/etc/ipsec.secrets' /etc/logcheck/ignore.d.paranoid/openswan [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.paranoid/openswan' /etc/logcheck/ignore.d.server/openswan [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.server/openswan' /etc/logcheck/ignore.d.workstation/openswan [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.workstation/openswan' /etc/logcheck/violations.ignore.d/openswan [Errno 13] Permission denied: u'/etc/logcheck/violations.ignore.d/openswan' -- debconf information: openswan/existing_x509_key_filename: openswan/no-oe_include_file: openswan/x509_state_name: openswan/x509_email_address: openswan/x509_country_code: AT openswan/x509_self_signed: true * openswan/rsa_key_length: 2048 * openswan/restart: true * openswan/start_level: earliest * openswan/install_x509_certificate: false * openswan/enable-oe: false openswan/x509_organizational_unit: openswan/x509_locality_name: openswan/how_to_get_x509_certificate: create openswan/existing_x509_rootca_filename: * openswan/runlevel_changes: openswan/existing_x509_certificate: false openswan/existing_x509_certificate_filename: openswan/x509_common_name: * openswan/create_rsa_key: true * openswan/rsa_key_type: plain openswan/x509_organization_name: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#604197: PC speaker does not work after upgrade to squeeze
Package: linux-image-2.6.32-5-686-bigmem Version: 2.6.32+29 Same problem here, after boot the PC speaker does not work (since the upgrade to squeeze). Standard HP Compaq PC with ICH9 chipset. So no exotic hardware, if that matters. The module pcspkr is loaded after boot, but no beep or speaker sound at all. When I manually remove the module and reload it with modprobe the speaker works normal. Regards Uwe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610978: python-minimal: upgrade from lenny to squeeze fails
Package: python-minimal Version: 2.6.6-3+squeeze5 Severity: important The upgrade from lenny to squeeze aborted with an error. It looks like a python package is changing the link /usr/bin/python to python2.6 before /usr/bin/python2.6 is installed. /usr/bin/python is part of python-minimal, so I file the bug against this package. Be free to reassign the bug if it's not the right one. Regards Uwe Log from apt-get dist-upgrade: Preparing to replace python2.5 2.5.2-15+lenny1 (using .../python2.5_2.5.5-11_i386.deb) ... Unpacking replacement python2.5 ... Preparing to replace python2.5-minimal 2.5.2-15+lenny1 (using .../python2.5-minimal_2.5.5-11_i386.deb) ... Unpacking replacement python2.5-minimal ... Preparing to replace python-semanage 2.0.25-3 (using .../python-semanage_2.0.45-1_i386.deb) ... Unpacking replacement python-semanage ... Preparing to replace python-apt 0.7.7.1+nmu1 (using .../python-apt_0.7.100.1_i386.deb) ... Unpacking replacement python-apt ... Preparing to replace mercurial 1.3.1-1~bpo50+2 (using .../mercurial_1.6.4-1_i386.deb) ... Unpacking replacement mercurial ... Preparing to replace python-selinux 2.0.65-5 (using .../python-selinux_2.0.96-1_i386.deb) ... Unpacking replacement python-selinux ... Preparing to replace python 2.5.2-3 (using .../python_2.6.6-3+squeeze5_all.deb) ... Unpacking replacement python ... Preparing to replace python-minimal 2.5.2-3 (using .../python-minimal_2.6.6-3+squeeze5_all.deb) ... Unpacking replacement python-minimal ... Preparing to replace libsepol1 2.0.30-2 (using .../libsepol1_2.0.41-1_i386.deb) ... Unpacking replacement libsepol1 ... Processing triggers for man-db ... Processing triggers for python-support ... /var/lib/dpkg/info/python-support.postinst: /usr/sbin/update-python-modules: /usr/bin/python: bad interpreter: No such file or directory dpkg: error processing python-support (--unpack): subprocess installed post-installation script returned error exit status 126 Errors were encountered while processing: python-support perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). E: Sub-process /usr/bin/dpkg returned an error code (1) # ls -l /usr/bin/python lrwxrwxrwx 1 root root 9 Jan 24 00:51 /usr/bin/python - python2.6 c10:/# ls -l /usr/bin/python2.6 ls: cannot access /usr/bin/python2.6: No such file or directory -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (750, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-minimal depends on: ii dpkg 1.15.8.8 Debian package management system ii python2.6-minimal 2.6.6-8+b1 A minimal subset of the Python lan Versions of packages python-minimal recommends: ii python 2.6.6-3+squeeze5 interactive high-level object-orie python-minimal 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
