Bug#776572: fail2ban: $named missing as dependency in init script
Package: fail2ban Version: 0.8.6-3wheezy3 Severity: important Dear Maintainer, the init script for fail2ban is missing $named as dependency. So it's getting started before named is running, and the initial processing of log files fails on all lines with a hostname. So you should change # Required-Start:$local_fs $remote_fs $named # Required-Stop: $local_fs $remote_fs $named For completeness you should als add ufw to Sholud-Start and Should-Stop. -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (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 fail2ban depends on: ii lsb-base4.1+Debian8+deb7u1 ii python 2.7.3-4+deb7u1 ii python-central 0.6.17 Versions of packages fail2ban recommends: ii iptables 1.4.14-3.1 ii python-gamin 0.1.10-4.1 ii whois 5.1.1~deb7u1 Versions of packages fail2ban suggests: ii heirloom-mailx [mailx] 12.5-2+deb7u1 -- Configuration Files: /etc/fail2ban/jail.conf changed [not included] /etc/init.d/fail2ban changed [not included] -- 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#668325: colord-sane consumes 40-82% cpu at all times
I also hit this bug. If version 0.1.21-2 fixes this, why is it not available in package archive? Where can I download this package? Jessie version is newer and does not met the dependencies in wheezy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Am Samstag, den 31.05.2014, 11:33 +0200 schrieb Jochen Fahrner: some more info on this. I installed kernel 3.12 and 3.14 from wheezy backports, and both don't have this shutdown problem. Maybe it has something to do with acpi. If I boot kernel 3.2 with acpi=off, system is halted on shutdown and I can manually power off. I have to correct: newer kernels also have this problem, but not on _every_ shutdown. After some googling, I found many hints that laptop-mode-tools can be the cause of this reboots. I don't have laptop-mode-tools installed, but since my Lenovo Ideacentre is not a laptop, I removed some other laptop related packages: acpi-support acpi-support-base pcmciautils powertop task-laptop That seems to solve the problem. Shutdown was working fine now for several times with kernel 3.2. Ubuntu kernels also don't have this problem, but I cannot use Ubuntu kernels because the kernel header package dependencies are not compatible with Debian, and I need them because of virtualbox kernel modules. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Hi, some more info on this. I installed kernel 3.12 and 3.14 from wheezy backports, and both don't have this shutdown problem. Maybe it has something to do with acpi. If I boot kernel 3.2 with acpi=off, system is halted on shutdown and I can manually power off. Jochen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Hi, I just switched from Ubuntu to Debian 7.5 (Gnome 3) and have the same issue. Kernel is 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u1 x86_64 GNU/Linux. I was working with Ubuntu for several years and never had such a problem with any kernel. I was using Ubuntu 12.04 with LTS enablement stack, so I got many different version of the kernel, starting at 3.2 and ending with 3.11. After upgrade to Ubuntu 14.04 I used kernel 3.13.0 and also had no problem. So, maybe this is not an issue with the kernel, but with something else in Debians shutdown procedure? Maybe the setting of RTC in shutdown procedure? (I think Ubuntu does not set it on shutdown) Jochen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747905: pcscd: Error message about missing group 'pcscd'
Hi, there is one more rule containing group pcscd: /lib/udev/rules.d/92-libccid.rules Jochen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
One more observation that may help: When I boot from grub directly into single user mode, and then do shutdown -h now, it is correctly powering off. When I boot into multi user mode, then switch to single user mode via init 1, then do shutdown -h now, it is rebooting. Jochen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726880: gftp-gtk: Connection closed when starting a second download
Package: gftp-gtk Version: 2.0.19-4 Severity: normal Dear Maintainer, when starting a second download while a download is active, the connection to server is closed, instead of appending the file to the download list. This only happens at the second download. After manual reconnect I can add more downloads without this issue. -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gftp-gtk depends on: ii gftp-common 2.0.19-4 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-38 ii libcairo2 1.12.2-3 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-5 ii libgtk2.0-0 2.24.10-2 ii libpango1.0-0 1.30.0-1 gftp-gtk recommends no packages. gftp-gtk 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#709591: gajim: Gajim does not reconnect after resume from suspend
Package: gajim Version: 0.15.1-4 Severity: normal Dear Maintainer, version 0.15 added UPower support and disconnects properly when a mobile device goes to suspend. But on resume it does not reconnect as it should. I had a look at the source code and found that it relies on network-manager events to reestablish connections when network goes up. This does not work. Maybe it's better to register a resume event like gajim-suspend-watcher script does. For more information look at this bug report: https://trac.gajim.org/ticket/1962#comment:22 -- System Information: Debian Release: 7.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gajim depends on: ii dnsutils 1:9.8.4.dfsg.P1-6+nmu2 ii python 2.7.3-4 ii python-gtk2 2.24.0-3+b1 Versions of packages gajim recommends: ii dbus 1.6.8-1 ii python-crypto2.6-4 ii python-dbus 1.1.1-1 ii python-openssl 0.13-2 ii python-pyasn10.1.3-1 ii xfce4-notifyd [notification-daemon] 0.2.2-2 Versions of packages gajim suggests: ii aspell-en 7.1-0-1 ii avahi-daemon0.6.31-2 pn dvipng none ii gnome-keyring 3.4.1-5 ii gstreamer0.10-plugins-ugly 0.10.19-2+b2 pn libgtkspell0none pn nautilus-sendto none ii network-manager 0.9.4.0-10 pn python-avahinone pn python-farstreamnone ii python-gconf2.28.1+dfsg-1 ii python-gnome2 2.28.1+dfsg-1 pn python-gnomekeyring none pn python-gupnp-igdnone pn python-kerberos none ii python-pycurl 7.19.0-5 pn texlive-latex-base 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#705796: installation-reports: Installing Debian Wheezy Xfce installs 2 notification daemons: xfce4-notifyd and notification-daemon
Package: installation-reports Severity: normal Dear Maintainer, I installed Debian Wheezy RC1 from Xfce CD 1 and found that 2 notification daemons were installed: notification-daemon and xfce4-notifyd. This way you get an error at login, saying a notification daemon is already running. Solution is to uninstall notification-daemon and keep xfce4-notifyd. -- Package-specific info: Boot method: Image version: Date: Date and time of the install Machine: Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7.0 (wheezy) - installer build 20120930+b1 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux Ideacentre 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor Family DRAM Controller [8086:0100] (rev 09) lspci -knn: Subsystem: Lenovo Device [17aa:3623] lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) lspci -knn: Subsystem: Lenovo Device [17aa:3623] lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 05) lspci -knn: Subsystem: Lenovo Device [17aa:3623] lspci -knn: Kernel driver in use: e1000e lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) lspci -knn: Subsystem: Lenovo Device [17aa:3623] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05) lspci -knn: Subsystem: Lenovo Device [17aa:3623] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.2 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 [8086:1c14] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b5) lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05) lspci -knn: Subsystem: Lenovo Device [17aa:3623] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation H61 Express Chipset Family LPC Controller [8086:1c5c] (rev 05) lspci -knn: Subsystem: Lenovo Device [17aa:3623] lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller [8086:1c02] (rev 05) lspci -knn: Subsystem: Lenovo Device [17aa:3623] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller [8086:1c22] (rev 05) lspci -knn: Subsystem: Lenovo Device [17aa:3623] lspci -knn: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 7400A Series] [1002:6772] lspci -knn: Subsystem: Lenovo Device [17aa:3623] lspci -knn: 02:00.0
Bug#702566: thunar: View is not refreshed after deletion of a remote file
Package: thunar Version: 1.2.3-4+b1 Severity: normal Dear Maintainer, subject says it all. This bug is listed in Xfce Bugzilla #8101. https://bugzilla.xfce.org/show_bug.cgi?id=8101 https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/999824 This bug seems solved in Thunar 1.5.0, but Debian Wheezy contains an old version of Thunar. Please upgrade to a newer version. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages thunar depends on: ii desktop-file-utils 0.20-0.1 ii exo-utils 0.6.2-5 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-38 ii libcairo2 1.12.2-3 ii libdbus-1-3 1.6.8-1 ii libdbus-glib-1-20.100.1-1 ii libexo-1-0 0.6.2-5 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-5 ii libgtk2.0-0 2.24.10-2 ii libgudev-1.0-0 175-7.1 ii libice6 2:1.0.8-2 ii libnotify4 0.7.5-1 ii libpango1.0-0 1.30.0-1 ii libsm6 2:1.2.1-2 ii libthunarx-2-0 1.2.3-4+b1 ii libxfce4ui-1-0 4.8.1-1 ii libxfce4util4 4.8.2-1 ii shared-mime-info1.0-1+b1 ii thunar-data 1.2.3-4 Versions of packages thunar recommends: ii dbus-x111.6.8-1 ii gvfs1.12.3-4 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1 ii thunar-volman 0.6.1-1 ii tumbler 0.1.25-1+b1 ii xdg-user-dirs 0.14-1 ii xfce4-panel 4.8.6-4 Versions of packages thunar suggests: ii thunar-archive-plugin 0.3.0-4 ii thunar-media-tags-plugin 0.2.0-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#702362: linux-image-3.2.0-4-amd64: Wireless Lan driver brcmsmac not connecting to channels 12, 13 14
Package: src:linux Version: 3.2.35-2 Severity: normal Dear Maintainer, the driver brcmsmac cannot connect to wifi channels 12-14. After installing the patch from this blog: http://133nux.blogspot.de/2011/12/missing-channel-13-this-time-broadcom.html I can connect on channel 12 13, but still not on channel 14. The regulatory domain is correctly set to JP. jochen@Aspire:~$ sudo iw reg get country JP: (2402 - 2472 @ 40), (N/A, 20) (2457 - 2482 @ 20), (N/A, 20) (2474 - 2494 @ 20), (N/A, 20), NO-OFDM (4910 - 4930 @ 10), (N/A, 23) (4910 - 4990 @ 40), (N/A, 23) (4930 - 4950 @ 10), (N/A, 23) (5030 - 5045 @ 10), (N/A, 23) (5030 - 5090 @ 40), (N/A, 23) (5050 - 5060 @ 10), (N/A, 23) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 23), DFS jochen@Aspire:~$ sudo iwlist freq lono frequency information. wlan0 14 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 12 : 2.467 GHz Channel 13 : 2.472 GHz Channel 14 : 2.484 GHz Current Frequency:2.412 GHz (Channel 1) I have the same symptoms as mentioned in the blog -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 root=UUID=6cba8902-d28b-490e-a7c2-c1cbd8c9e57a ro quiet ** Not tainted ** Kernel log: [ 12.920935] FS-Cache: Netfs 'nfs' registered for caching [ 12.947077] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 14.862635] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input12 [ 17.770133] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 17.770143] Bluetooth: BNEP filters: protocol multicast [ 17.770665] Bluetooth: RFCOMM TTY layer initialized [ 17.770674] Bluetooth: RFCOMM socket layer initialized [ 17.770679] Bluetooth: RFCOMM ver 1.11 [ 17.879943] lp: driver loaded but no devices found [ 18.078969] ppdev: user-space parallel port driver [ 22.914517] atl1c :02:00.0: irq 43 for MSI/MSI-X [ 22.914652] atl1c :02:00.0: atl1c: eth0 NIC Link is Up100 Mbps Full Duplex [ 22.973549] ieee80211 phy0: brcms_ops_config: change monitor mode: false (implement) [ 22.973556] ieee80211 phy0: brcms_ops_config: change power-save mode: false (implement) [ 22.974058] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 22.974526] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 26.019048] wlan0: authenticate with 10:bf:48:e6:28:42 (try 1) [ 26.216079] wlan0: authenticate with 10:bf:48:e6:28:42 (try 2) [ 26.416187] wlan0: authenticate with 10:bf:48:e6:28:42 (try 3) [ 26.616072] wlan0: authentication with 10:bf:48:e6:28:42 timed out [ 27.555633] wlan0: authenticate with 10:bf:48:e6:28:42 (try 1) [ 27.752170] wlan0: authenticate with 10:bf:48:e6:28:42 (try 2) [ 27.952154] wlan0: authenticate with 10:bf:48:e6:28:42 (try 3) [ 28.152050] wlan0: authentication with 10:bf:48:e6:28:42 timed out [ 29.095183] wlan0: authenticate with 10:bf:48:e6:28:42 (try 1) [ 29.292139] wlan0: authenticate with 10:bf:48:e6:28:42 (try 2) [ 29.492139] wlan0: authenticate with 10:bf:48:e6:28:42 (try 3) [ 29.692170] wlan0: authentication with 10:bf:48:e6:28:42 timed out [ 30.628803] wlan0: authenticate with 10:bf:48:e6:28:42 (try 1) [ 30.828138] wlan0: authenticate with 10:bf:48:e6:28:42 (try 2) [ 31.028183] wlan0: authenticate with 10:bf:48:e6:28:42 (try 3) [ 31.228146] wlan0: authentication with 10:bf:48:e6:28:42 timed out [ 32.166659] wlan0: authenticate with 10:bf:48:e6:28:42 (try 1) [ 32.364518] wlan0: authenticate with 10:bf:48:e6:28:42 (try 2) [ 32.564151] wlan0: authenticate with 10:bf:48:e6:28:42 (try 3) [ 32.764155] wlan0: authentication with 10:bf:48:e6:28:42 timed out [ 33.698677] wlan0: authenticate with 10:bf:48:e6:28:42 (try 1) [ 33.896064] wlan0: authenticate with 10:bf:48:e6:28:42 (try 2) [ 34.064103] eth0: no IPv6 routers present [ 34.097543] wlan0: authenticate with 10:bf:48:e6:28:42 (try 3) [ 34.296137] wlan0: authentication with 10:bf:48:e6:28:42 timed out [ 35.225965] wlan0: authenticate with 10:bf:48:e6:28:42 (try 1) [ 35.424135] wlan0: authenticate with 10:bf:48:e6:28:42 (try 2) [ 35.624136] wlan0: authenticate with 10:bf:48:e6:28:42 (try 3) [ 35.824218] wlan0: authentication with 10:bf:48:e6:28:42 timed out [ 36.757779] wlan0: authenticate with 10:bf:48:e6:28:42 (try 1) [ 36.956056] wlan0: authenticate with
Bug#702364: broadcom-sta-dkms: Driver does not connect to channels 12,13 14
Package: broadcom-sta-dkms Version: 5.100.82.112-8 Severity: normal Dear Maintainer, this driver does not connect to wifi channels 12, 13 14. Regulatory domain is set correctly: jochen@Aspire:~$ sudo iw reg get country JP: (2402 - 2472 @ 40), (N/A, 20) (2457 - 2482 @ 20), (N/A, 20) (2474 - 2494 @ 20), (N/A, 20), NO-OFDM (4910 - 4930 @ 10), (N/A, 23) (4910 - 4990 @ 40), (N/A, 23) (4930 - 4950 @ 10), (N/A, 23) (5030 - 5045 @ 10), (N/A, 23) (5030 - 5090 @ 40), (N/A, 23) (5050 - 5060 @ 10), (N/A, 23) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 23), DFS jochen@Aspire:~$ sudo iwlist freq lono frequency information. wlan0 32 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 12 : 2.467 GHz Channel 13 : 2.472 GHz Channel 14 : 2.484 GHz Channel 36 : 5.18 GHz Channel 38 : 5.19 GHz Channel 40 : 5.2 GHz Channel 42 : 5.21 GHz Channel 44 : 5.22 GHz Channel 46 : 5.23 GHz Channel 48 : 5.24 GHz Channel 52 : 5.26 GHz Channel 56 : 5.28 GHz Channel 60 : 5.3 GHz Channel 64 : 5.32 GHz Channel 100 : 5.5 GHz Channel 104 : 5.52 GHz Channel 108 : 5.54 GHz Channel 112 : 5.56 GHz Channel 116 : 5.58 GHz Channel 120 : 5.6 GHz Channel 124 : 5.62 GHz Current Frequency:2.412 GHz (Channel 1) -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages broadcom-sta-dkms depends on: ii dkms 2.2.0.3-1.2 Versions of packages broadcom-sta-dkms recommends: ii wireless-tools 30~pre9-8 broadcom-sta-dkms 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#698410: pyro: Pyro nameserver binds to 127.0.0.1
Package: pyro Version: 1:3.14-1.1 Severity: important Dear Maintainer, a standard Debian installation has an entry with 127.0.0.1 for hostname in /etc/hosts. When pyro nameserver daemon starts, it resolves hostname, gets 127.0.0.1 and binds to the loopback interface. The troubleshooting section of pyro documentation says: Probable cause: incorrect DNS config, or the server's host name resolves to 127.0.0.1, for instance because the hosts file contains an invalid entry. only localhost is allowed resolve to 127.0.0.1 ! http://irmen.home.xs4all.nl/pyro3/troubleshooting.html#connection_problems_involving_localhost.2BAC8-127.0.0.1 But this is wrong. It is not a misconfiguration when hostname resolves to 127.0.0.1 on local machine. This is standard Debian behaviour! Instead the pyro nameserver should bind to ALL interfaces that have a broadcast address. You can determine them with netifaces module. Also socket has the ability to bind to all interfaces with an empty host string. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pyro depends on: ii python 2.7.3~rc2-1 ii python-support 1.0.15 pyro recommends no packages. Versions of packages pyro suggests: pn pyro-doc none pn pyro-gui 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#697493: xarchiver add-to fails on folders with space in name
Package: xarchiver Version: 1:0.5.2+20090319+dfsg-4.1 Severity: normal Tags: upstream Dear Maintainer, Steps to reproduce this bug: mkdir test with space echo file1 test with space/file1 echo file2 test with space/file2 xarchiver -d test with space Choose an archive name and select archive type 7z or zip. This results in an error Cannot find 1 file This action is what Thunar does through thunar-archive-plug when creating an archive and makes thunar-archive-plugin unusable on folders with spaces in their name. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xarchiver depends on: ii libatk1.0-0 2.4.0-2 ii libc6 2.13-37 ii libcairo2 1.12.2-2 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-3 ii libgtk2.0-0 2.24.10-2 ii libpango1.0-0 1.30.0-1 Versions of packages xarchiver recommends: ii arj 3.10.22-10 ii bzip2 1.0.6-4 ii p7zip-full 9.20.1~dfsg.1-4 ii rpm 4.10.0-5 ii unzip 6.0-8 ii xdg-utils 1.1.0~rc1+git20111210-6 ii zip 3.0-6 Versions of packages xarchiver suggests: pn lha none pn rar 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#691788: installation-reports: libartsc0 is missing, but needed for avidemux in debian multimedia.
Package: installation-reports Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: Boot method: CD Image version: XFCE CD1 Beta3 Date: Date and time of the install Machine: MacBook 5,1 Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Clock/timezone setup: [ ] User/password setup:[ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=7.0 (wheezy) - installer build 20120930+b1 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux Macbook 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: NVIDIA Corporation MCP79 Host Bridge [10de:0a82] (rev b1) lspci -knn: 00:00.1 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0a88] (rev b1) lspci -knn: 00:03.0 ISA bridge [0601]: NVIDIA Corporation MCP79 LPC Bridge [10de:0aae] (rev b2) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: 00:03.1 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0aa4] (rev b1) lspci -knn: 00:03.2 SMBus [0c05]: NVIDIA Corporation MCP79 SMBus [10de:0aa2] (rev b1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: 00:03.3 RAM memory [0500]: NVIDIA Corporation MCP79 Memory Controller [10de:0a89] (rev b1) lspci -knn: 00:03.4 RAM memory [0500]: NVIDIA Corporation Device [10de:0a98] (rev b1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: 00:03.5 Co-processor [0b40]: NVIDIA Corporation MCP79 Co-processor [10de:0aa3] (rev b1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: 00:04.0 USB controller [0c03]: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa5] (rev b1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:04.1 USB controller [0c03]: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa6] (rev b1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:06.0 USB controller [0c03]: NVIDIA Corporation MCP79 OHCI USB 1.1 Controller [10de:0aa7] (rev b1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: 00:06.1 USB controller [0c03]: NVIDIA Corporation MCP79 EHCI USB 2.0 Controller [10de:0aa9] (rev b1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:08.0 Audio device [0403]: NVIDIA Corporation MCP79 High Definition Audio [10de:0ac0] (rev b1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: 00:09.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Bridge [10de:0aab] (rev b1) lspci -knn: 00:0a.0 Ethernet controller [0200]: NVIDIA Corporation MCP79 Ethernet [10de:0ab0] (rev b1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: Kernel driver in use: forcedeth lspci -knn: 00:0b.0 IDE interface [0101]: NVIDIA Corporation MCP79 SATA Controller [10de:0ab5] (rev b1) lspci -knn: Subsystem: NVIDIA Corporation Device [10de:cb79] lspci -knn: Kernel driver in use: ahci lspci -knn: 00:10.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0aa0] (rev b1) lspci -knn: 00:15.0 PCI bridge [0604]: NVIDIA Corporation MCP79 PCI Express Bridge [10de:0ac6] (rev b1) lspci -knn: Kernel driver in use: pcieport lspci -knn: 02:00.0 VGA compatible controller [0300]: NVIDIA Corporation C79 [GeForce
