Bug#1012859: Info received (Syslog)
OK, I went ahead and did a fresh install of Bookworm and the 10G NIC works. I went ahead and upgraded the Bullseye system to bookworm, and everything seems to work as well as ever, but I still don't have the 10G NIC working on that system. The driver for the card is bnx2x, but the card currently does not even show up on the system. On 7/13/2023 6:25 PM, Leslie Rhorer wrote: On 7/13/2023 5:18 PM, Jeremy Davis wrote: [Just a random passer-by that might have an idea?] On 14/7/23 07:14, Leslie Rhorer wrote: I filed report 1012859 to the Debian BTS over a year ago. Nothing has been done so far, and I have one cripped system and one dead system that needs to be upgraded to the most recent version, but I can't really proceed until the proper files get included into the Debian distro. Can someone please help? It looks to me like you are missing the firmware-realtek[1][2] (non-free) package?! No, I am not missing it. The package is broken in Bullseye. The firmware is there, but does not work. It worked just fine in Buster, but when I upgraded to Bullseye, the 10G NIC completely quit working. It's been over a year, so I don't recall everything I did, but I spent many, many hours trying to get the new firmware working, and many more hours trying to extract the firmware from the oldstable package, and then quite a few more hours trying to compile from source, but nothing worked. I could not even get the source code to compile. The bottom line is the firmware from the Buster non-free distro works perfectly well, but noone has come forth with a fix for Bullseye, and I have no reason to believe the firmware from Bookworm will work. The NIC is an Asus PEB-10G/57811-1S 10GbE SFP+ Network Adapter which employs a BCM 57811S controller. [1] https://packages.debian.org/bullseye/firmware-realtek [2] https://packages.debian.org/bookworm/firmware-realtek If you haven't already tried, I'd suggest that you try a clean bookworm install from ISO. FWIW bookworm now includes a separate "non-free-firmware" repo that is enabled by default. So the official installer should "just work". I can try, but I really would not be well advised to do so until I can get the dead system working again. If not, then I would suggest opening a new bug against the current installer. In the meantime, try manually installing the package (e.g. copy the deb via a USB stick). Hope that helps. Regards, Jeremy
Bug#1012859: Info received (Syslog)
On 7/13/2023 5:18 PM, Jeremy Davis wrote: [Just a random passer-by that might have an idea?] On 14/7/23 07:14, Leslie Rhorer wrote: I filed report 1012859 to the Debian BTS over a year ago. Nothing has been done so far, and I have one cripped system and one dead system that needs to be upgraded to the most recent version, but I can't really proceed until the proper files get included into the Debian distro. Can someone please help? It looks to me like you are missing the firmware-realtek[1][2] (non-free) package?! No, I am not missing it. The package is broken in Bullseye. The firmware is there, but does not work. It worked just fine in Buster, but when I upgraded to Bullseye, the 10G NIC completely quit working. It's been over a year, so I don't recall everything I did, but I spent many, many hours trying to get the new firmware working, and many more hours trying to extract the firmware from the oldstable package, and then quite a few more hours trying to compile from source, but nothing worked. I could not even get the source code to compile. The bottom line is the firmware from the Buster non-free distro works perfectly well, but noone has come forth with a fix for Bullseye, and I have no reason to believe the firmware from Bookworm will work. The NIC is an Asus PEB-10G/57811-1S 10GbE SFP+ Network Adapter which employs a BCM 57811S controller. [1] https://packages.debian.org/bullseye/firmware-realtek [2] https://packages.debian.org/bookworm/firmware-realtek If you haven't already tried, I'd suggest that you try a clean bookworm install from ISO. FWIW bookworm now includes a separate "non-free-firmware" repo that is enabled by default. So the official installer should "just work". I can try, but I really would not be well advised to do so until I can get the dead system working again. If not, then I would suggest opening a new bug against the current installer. In the meantime, try manually installing the package (e.g. copy the deb via a USB stick). Hope that helps. Regards, Jeremy
Bug#1012859: Info received (Syslog)
I filed report 1012859 to the Debian BTS over a year ago. Nothing has been done so far, and I have one cripped system and one dead system that needs to be upgraded to the most recent version, but I can't really proceed until the proper files get included into the Debian distro. Can someone please help? On 6/15/2022 3:12 PM, Debian Bug Tracking System wrote: Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian Install Team If you wish to submit further information on this problem, please send it to1012...@bugs.debian.org. Please do not send mail toow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
Bug#1012859: installation-reports: Ethernet firmware module failure - no LAN / internet access during or after install
Package: installation-reports Severity: grave Tags: d-i a11y Justification: renders package unusable X-Debbugs-Cc: lesrho...@siliconventures.net (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) Boot method: USB Image version: https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-dvd/firmware-11.3.0-amd64-DVD-1.iso Date: 5/28/2022 Machine: Asus AMD system with an 8 core FX-8350 CPU and Asus PEB-10G/57811-1S 10GbE SFP+ Network Adapter Partitions: N/A Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[0] Configure network: [E] Detect media: [0] Load installer modules: [E] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Install tasks: [O] Install boot loader:[O] Overall install:[E] Comments/Problems: Two of my servers are having bizarre problems after upgrading to Debian Bullseye. After attempting numerous fixes, I decided to wipe the systems and do a fresh install. I did a fresh install of the first from a netinst thumb drive, but the .iso does not contain the bnx2c drivers needed for the ASUS PEB-10G/57811-1S 10GbE SFP+ Network Adapters used by both systems. I tried adding what I thought to be the correct non-free drivers, but I still got errors about the bnx2x drivers and the interface shows no carrier. Since no carrier is detected on the interface, no LAN or internet access is possible. The system was effectively dead, although it boots up and of course I have local console access. After several different approaches, I changed from the netinst image to a full non-free image. It still would not properly load the bnx2x drivers. I tried downloading all six bnx2x e1, e1h, and e2 release 7.13.15.0 and 7.13.21.0 firmware files and adding them to the initram image. It no longer complains about missing files, but it doesn't activate the NIC, either. I tried compiling the driver from source, but I get a cc1 error saying the code model kernel does not support PIC mode. I have tried numerous modifications to the make file, but I have not been able to eliminate the error. The only thing I spot from dmesg that seems possibly related is: [1.420748] r8169 :0b:00.0: can't disable ASPM; OS doesn't have ASPM control [1.433467] r8169 :0b:00.0 eth0: RTL8168f/8111f, 50:46:5d:65:15:9c, XID 480, IRQ 39 [1.433469] r8169 :0b:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko] ... [1.458361] r8169 :0b:00.0 enp11s0: renamed from eth0 [1.465675] bnx2x: disagrees about version of symbol module_layout ... [ 12.976323] r8169 :0b:00.0: firmware: failed to load rtl_nic/rtl8168f-1.fw (-2) [ 12.976478] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 12.976632] r8169 :0b:00.0: Direct firmware load for rtl_nic/rtl8168f-1.fw failed with error -2 [ 12.976636] r8169 :0b:00.0: Unable to load firmware rtl_nic/rtl8168f-1.fw (-2) [ 12.977326] RTL8211E Gigabit Ethernet r8169-0-b00:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=r8169-0-b00:00, irq=IGNORE) [ 13.046445] r8169 :0b:00.0 enp11s0: Link is Down Please make sure that any installation logs that you think would be useful are attached to this report. Please compress large files using gzip. -- Package-specific info: == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20210731+deb11u3" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux Backup 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RD9x0/RX980 Host Bridge [1002:5a14] (rev 02) lspci -knn: Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD9x0/RX980 Host Bridge [1002:5a14] lspci -knn: 00:02.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GFX port 0) [1002:5a16] lspci -knn: DeviceName: Onboard IGD lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 0) [1002:5a18] lspci -knn: Kernel driver in use: pcieport lspci -knn: 00:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RD890/RD9x0/RX980 PCI to PCI bridge (PCI Express GPP Port 1) [1002:5a19] lspci
Bug#911144: apache2: Apache2 not working with CGI enabled
Package: apache2 Version: 2.4.25-3+deb9u5 Severity: important Dear Maintainer, This is a fresh Raspbian install with a brand new install of apache 2.4.25. Everything was working fine until I enabled CGI by entering `a2enmod cgi`. Now I cannot even run a raw html page, because apache is expectig it to be a script: [Mon Oct 15 09:02:02.196180 2018] [cgid:error] [pid 17010:tid 1995407360] (8)Exec format error: AH01241: exec of '/usr/lib/cgi-bin/Thermostat/index.html' failed [Mon Oct 15 09:02:02.198189 2018] [cgid:error] [pid 16450:tid 1945105456] [client 192.168.1.21:59329] End of script output before headers: index.html What is far worse, I can't get any script to run if it generates any html code. The system complains of a bad header, or in some cases invalid characters in the header. I have tried every header of which I can think: http://www.w3.org/TR/html4/loose.dtd;> http://www.w3.org/TR/html4/strict.dtd;> -- Package-specific info: -- System Information: Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.4 (stretch) Release: 9.4 Codename: stretch Architecture: armv7l Kernel: Linux 4.14.50-v7+ (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apache2 depends on: ii apache2-bin 2.4.25-3+deb9u5 ii apache2-data 2.4.25-3+deb9u5 ii apache2-utils 2.4.25-3+deb9u5 ii dpkg 1.18.24 ii init-system-helpers 1.48 ii lsb-base 9.20161125+rpi1 ii mime-support 3.60 ii perl 5.24.1-3+deb9u4 ii procps 2:3.3.12-3+deb9u1 Versions of packages apache2 recommends: ii ssl-cert 1.0.39 Versions of packages apache2 suggests: pn apache2-doc pn apache2-suexec-pristine | apache2-suexec-custom pn www-browser Versions of packages apache2-bin depends on: ii libapr1 1.5.2-5 ii libaprutil1 1.5.4-3 ii libaprutil1-dbd-sqlite3 1.5.4-3 ii libaprutil1-ldap 1.5.4-3 ii libc6 2.24-11+deb9u3 ii libldap-2.4-2 2.4.44+dfsg-5+deb9u1 ii liblua5.2-0 5.2.4-1.1 ii libnghttp2-14 1.18.1-1 ii libpcre3 2:8.39-3 ii libssl1.0.2 1.0.2l-2+deb9u3 ii libxml2 2.9.4+dfsg1-2.2+deb9u2 ii perl 5.24.1-3+deb9u4 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages apache2-bin suggests: pn apache2-doc pn apache2-suexec-pristine | apache2-suexec-custom pn www-browser Versions of packages apache2 is related to: ii apache2 2.4.25-3+deb9u5 ii apache2-bin 2.4.25-3+deb9u5 -- no debconf information
Bug#792808: coreutils: CRC file checks not consistent
On 7/18/2015 3:11 PM, Pádraig Brady wrote: On 18/07/15 19:38, Leslie Rhorer wrote: Package: coreutils Version: 8.23-4 Severity: grave Justification: renders package unusable Dear Maintainer, CRC checks on large files often return variable values. I have tried several different CRC check utilities, md5sum, md6sum, sha56sum, etc., and they all exhibit the same behavior. Multiple runs of the utility on a given file more often than not will return different values for many or all of the attempts. I have only noticed the effect on large files, but I cannot say with authority it only happens on large files. I noticed the effect when checking file integrity between identical files on two different systems. The backup server is running Squeeze, and checks on the files of that system are consistent, but when comparing the CRC between that system and the primary, which is running Jessie, the checks often failed. At first I of course thought this indicated file corruption on one server or the other, beut when I started investigating, I discovered sometimes the results were different on the two systems and sometimes the same. At that point I discovered it was only! th! e machine running Jessie that was producing inconsistent results. At first I thought I was having problems with the file system (and indeed I am, as it happens), but when I copied one of the large files over to a different file system, the problem perissts. One is an XFS file system (the one having the problems) and the other is an Ext4 file system. Note this impacts a great many very important procedures and utilities, including my backup and compare strategy using rsync, file systems checks, etc. RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 b2e15ca178832e9f12a4823c583eefb2028cec9f7c45f36ea9dfa2297c904d6d /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 eb3067b250d5d16e1d5d3f2b328001be91c4e5107a14e0010940acdab6584f2b /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 6eddb4174b49e9bac741070559ad159acaa39a404a1b75c395d716910e5c81ef /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 The inconsistent results are restricted to the Jessie system? I believe so, yes. I just booted up another Jessie system and copied over the file mentioned above, and it worked 3 times in a row. Although not proof positive, it suggests the issue is limited to this machine. I'd run memtest given results like that. I'm not able to reboot at the moment. I'll give it a look later, but memtester shows no errors. Of course that doesn't verify all the memory. Also I'd verify a separate checksum implementation. I don't think debian configures coreutils --with-openssl so this should be independent: openssl md5 largefile RAID-Server:/tmp/temp# openssl md5 Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 MD5(Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4)= fa54d754e0c51653d71d2419a26e18de RAID-Server:/tmp/temp# openssl md5 Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 MD5(Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4)= 6886fc9d69c5d1d3685ed158626ce563 thanks, Pádraig. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#792808: coreutils: CRC file checks not consistent
Package: coreutils Version: 8.23-4 Severity: grave Justification: renders package unusable Dear Maintainer, CRC checks on large files often return variable values. I have tried several different CRC check utilities, md5sum, md6sum, sha56sum, etc., and they all exhibit the same behavior. Multiple runs of the utility on a given file more often than not will return different values for many or all of the attempts. I have only noticed the effect on large files, but I cannot say with authority it only happens on large files. I noticed the effect when checking file integrity between identical files on two different systems. The backup server is running Squeeze, and checks on the files of that system are consistent, but when comparing the CRC between that system and the primary, which is running Jessie, the checks often failed. At first I of course thought this indicated file corruption on one server or the other, beut when I started investigating, I discovered sometimes the results were different on the two systems and sometimes the same. At that point I discovered it was only th! e machine running Jessie that was producing inconsistent results. At first I thought I was having problems with the file system (and indeed I am, as it happens), but when I copied one of the large files over to a different file system, the problem perissts. One is an XFS file system (the one having the problems) and the other is an Ext4 file system. Note this impacts a great many very important procedures and utilities, including my backup and compare strategy using rsync, file systems checks, etc. RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 b2e15ca178832e9f12a4823c583eefb2028cec9f7c45f36ea9dfa2297c904d6d /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 eb3067b250d5d16e1d5d3f2b328001be91c4e5107a14e0010940acdab6584f2b /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 RAID-Server:/# sha256sum /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 6eddb4174b49e9bac741070559ad159acaa39a404a1b75c395d716910e5c81ef /RAID/Recordings/Abyss, The (Recorded Thu Sep 11, 2014, MAXHD).mp4 -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') 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: sysvinit (via /sbin/init) Versions of packages coreutils depends on: ii libacl1 2.2.52-2 ii libattr1 1:2.4.47-2 ii libc62.19-18 ii libselinux1 2.3-2 coreutils recommends no packages. coreutils 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#792808: coreutils: CRC file checks not consistent
The inconsistent results are restricted to the Jessie system? I'd run memtest given results like that. Well, what do you know? One of the memory sticks had a bunch of errors on it. I don't think debian configures coreutils --with-openssl so this should be independent: openssl md5 largefile I guess nothing is independent when one has bad memory. Thank you so much for pinpointing the issue, and so quickly, too! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785016: (no subject)
I am having precisely the same issue. I need to scrape data from a web site for my HVAC controller, but the script cannot obtain the web pages from the site under Jessie. It works fine under Squeeze, but the Squeeze server is down right now, and will need to be upgraded. I don't know how it would perform under Wheezy. wget 1.15 under kernel 3.16-2-amd64 Example script line: wget --save-cookies cookies.txt --keep-session-cookies --no-check-certificate --post-data 'timeOffset=300UserName=x%40mygrande.netPassword=yRememberMe=false' https://mytotalconnectcomfort.com/portal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779732: linux-image-3.16-2-686-pae: Kernel forces rfkill to block wireless radio on boot
Can someone please look at this? It's been a month and a half since it was submitted. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779054: Wheezy Blueman not working
I was able to get Blueman working on my Raspberry Pi, but only by doing a dist upgrade to Jessie. I tried the backport version, but there were too many unmet dependencies with which to deal. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779732: Subject: linux-image-3.16-2-686-pae: Kernel forces rfkill to block wireless radio on boot
Package: src:linux Version: 3.16.3-2 Severity: normal Dear Maintainer, Ever since a recent upgrade, the kernel apparently instructs rfkill to block the wireless radio during boot. After google searching quite a bit, it seems this has been implemented to prevent laptops from broadcasting when on an airplane. Although this system uses a wireless NIC very commonly used in laptops, it is not a laptop. It is an Intel NUC. Many of the solutions on the web suggest simply pressing the wireless button on the laptop. There is no such button. Others suggest simply issuing an rfkill unblock command at the command line, but this is also not possible, because this is a headless unit with no wired Ethernet connections. It *MUST* come up with WiFi access at boot time. The best option would be to prevent the kernel from ever issuing the rfkill command at all. Barring that, I could write an init script (or modify an existing one) that re-enables the radio, but I am a little unsure of the exact details or where to insert such a script in the boot sequence. Typical of the behavior of this situation, the radio does come up for a few seconds during boot, but then shuts off. From syslog: Mar 3 20:42:50 DMXHost wpa_supplicant[377]: rfkill: WLAN soft blocked Mar 3 20:42:51 DMXHost NetworkManager[624]: info rfkill0: found WiFi radio killswitch (at /sys/devices/pci:00/:00:1c.1/:02:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi) -- Package-specific info: ** Version: Linux version 3.16-2-686-pae (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-11) ) #1 SMP Debian 3.16.3-2 (2014-09-20) ** Command line: auto BOOT_IMAGE=Linux ro root=UUID=487d9689-a65b-4fdf-b37e-6dad30518213 quiet ** Not tainted ** Kernel log: [2.445210] sound hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.445214] sound hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.445217] sound hdaudioC0D0:mono: mono_out=0x0 [2.445219] sound hdaudioC0D0:inputs: [2.445223] sound hdaudioC0D0: Mic=0x19 [2.459079] usbcore: registered new interface driver btusb [2.480368] iTCO_vendor_support: vendor-support=0 [2.480900] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 [2.480964] iTCO_wdt: Found a Bay Trail SoC TCO device (Version=3, TCOBASE=0x0460) [2.484738] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [2.502660] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUG disabled [2.502667] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled [2.502670] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled [2.502673] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N 2230 BGN, REV=0xC8 [2.503012] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [2.526944] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [2.542191] cfg80211: World regulatory domain updated: [2.542199] cfg80211: DFS Master region: unset [2.542202] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [2.542206] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [2.542209] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) [2.542212] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) [2.542215] cfg80211: (517 KHz - 525 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [2.542217] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) [2.542220] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) [2.551688] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/sound/card0/hdaudioC0D0/input9 [2.552823] input: HDA Intel PCH Mic as /devices/pci:00/:00:1b.0/sound/card0/input10 [2.553073] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1b.0/sound/card0/input11 [2.553313] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input12 [2.553552] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1b.0/sound/card0/input13 [2.568666] Adding 7772156k swap on /dev/sda3. Priority:-1 extents:1 across:7772156k SSFS [2.580903] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [2.656806] EXT4-fs (sda1): mounting ext2 file system using the ext4 subsystem [2.662728] EXT4-fs (sda1): mounted filesystem without journal. Opts: (null) [2.773295] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [2.781044] iwlwifi :02:00.0: Radio type=0x2-0x0-0x0 [2.879369] Switched to clocksource tsc [3.022910] i915 :00:02.0: No connectors reported connected with modes [3.022932] [drm] Cannot find any crtc or sizes - going 1024x768 [3.025348] fbcon: inteldrmfb (fb0) is primary device [3.026703] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [3.034461] iwlwifi :02:00.0:
Bug#779054: Another data point
I also tried pairing an Aluratek AIS11F Bluetooth Audio Receiver with precisely the same results as the TechnicalPro. This time, when presented with the pairing window, I selected a custom passkey and entered . The results are the same (connects for a few moments and then dies) under blueman-manager. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779054: More data
I tried a Calrad 40-BT2 A2DP receiver (reports as a BTR006L headset) with similar results, except that it does not even offer the option for an audio sink. I may be wrong, but it seems the drive is insisting the user enter a PIN on the receiver, but these devices do not have any means of entering a PIN. They have on and off buttons, and that is all. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779054: /usr/bin/blueman-manager: Connection fails to TechnicalPro loudspeaker from, BT-400
Package: blueman Version: 1.23-1 Severity: normal File: /usr/bin/blueman-manager Dear Maintainer, I am unable to pair to a TechnicalPro MB6000 loudspeaker system from an Asus BT-400 Bluetooth Adapter. The failure mode varies depending on the method employed to attempt the conenction, but no matter what, I get no sound from the speakers. In some cases, the system shows up as paired / connected for a few seconds and then the connection fails (unable to set up stream). In other cases, the conection seems to persist, but I get no audio. This is on a Raspberry Pi, but I have also tried it on an Intel NUC with the same results. -- System Information: Debian Release: 7.6 Architecture: armhf (armv6l) Kernel: Linux 3.12.29+ (PREEMPT) 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 blueman depends on: ii bluez4.99-2 ii dbus 1.6.8-1+deb7u3 ii gnome-icon-theme 3.4.0-2 ii libatk1.0-0 2.4.0-2 ii libbluetooth34.99-2 ii libc62.13-38+rpi2+deb7u1 ii libcairo21.12.2-3 ii libfontconfig1 2.9.0-7.1 ii libfreetype6 2.4.9-1.1 ii libgdk-pixbuf2.0-0 2.28.2-1rpi4rpi1 ii libglib2.0-0 2.40.0-3rpi3rpi1 ii libgtk2.0-0 2.24.10-2 ii libpango1.0-01.32.5-5rpi3 ii libpython2.7 2.7.3-6+deb7u2 ii librsvg2-common 2.36.1-2 ii libstartup-notification0 0.12-1 ii notification-daemon 0.7.6-1 ii obex-data-server 0.4.5-1 ii python 2.7.3-4+deb7u1 ii python-dbus 1.1.1-1 ii python-gi3.8.2-1+rpi1rpi2 ii python-gtk2 2.24.0-3 ii python-notify0.1.1-3 ii python2.72.7.3-6+deb7u2 ii xfce4-notifyd [notification-daemon] 0.2.2-2 Versions of packages blueman recommends: ii libpulse-mainloop-glib0 2.0-6.1 ii policykit-1 0.105-3 ii python-gconf 2.28.1+dfsg-1 blueman 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#765978: Bluetooth Manager does not come up on first invocation
Package: blueman Version: 1.99~alpha1-1 Severity: normal Dear Maintainer, Bluetooth manager does not come up fully the first time it is invoked. The little Bluetooth icon bounces up and down for 30 seconds or so, and then the cursor returns to normal. A second attempt to invoke produces an error saying it is already running. After `kill -9` of /usr/bin/python /usr/bin/blueman-applet and /usr/bin/python /usr/bin/blueman-manager, an additional attempt succeeds. from syslog: Oct 19 11:38:54 DMXHost bluetoothd[630]: /org/bluez/hci0/dev_00_15_83_43_88_88/fd1: fd(22) ready Oct 19 12:16:27 DMXHost bluetoothd[630]: /org/bluez/hci0/dev_00_15_83_43_88_88/fd2: fd(22) ready Oct 19 13:04:33 DMXHost bluetoothd[630]: Suspend: Connection timed out (110) Oct 19 13:04:35 DMXHost bluetoothd[630]: Abort: Connection timed out (110) Oct 19 13:04:57 DMXHost bluetoothd[630]: /org/bluez/hci0/dev_00_15_83_43_88_88/fd3: fd(22) ready Oct 19 13:43:31 DMXHost bluetoothd[630]: /org/bluez/hci0/dev_00_15_83_43_88_88/fd4: fd(22) ready Oct 19 13:53:32 DMXHost org.blueman.Applet[1403]: (blueman-applet:1968): Gdk-WARNING **: blueman-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Oct 19 13:53:32 DMXHost bluetoothd[630]: Terminating Oct 19 13:54:02 DMXHost kernel: [7.558355] Bluetooth: Core ver 2.19 Oct 19 13:54:02 DMXHost kernel: [7.558385] Bluetooth: HCI device and connection manager initialized Oct 19 13:54:02 DMXHost kernel: [7.558395] Bluetooth: HCI socket layer initialized Oct 19 13:54:02 DMXHost kernel: [7.558399] Bluetooth: L2CAP socket layer initialized Oct 19 13:54:02 DMXHost kernel: [7.558871] Bluetooth: SCO socket layer initialized Oct 19 13:54:02 DMXHost bluetoothd[982]: Bluetooth daemon 5.23 Oct 19 13:54:02 DMXHost bluetoothd[982]: Starting SDP server Oct 19 13:54:02 DMXHost kernel: [7.783225] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Oct 19 13:54:02 DMXHost kernel: [7.783231] Bluetooth: BNEP filters: protocol multicast Oct 19 13:54:02 DMXHost kernel: [7.783241] Bluetooth: BNEP socket layer initialized Oct 19 13:54:02 DMXHost bluetoothd[982]: Bluetooth management interface 1.6 initialized Oct 19 13:54:02 DMXHost bluetoothd[982]: Sap driver initialization failed. Oct 19 13:54:02 DMXHost bluetoothd[982]: sap-server: Operation not permitted (1) Oct 19 13:54:02 DMXHost bluetoothd[982]: hci0 Load Connection Parameters failed: Unknown Command (0x01) Oct 19 13:54:13 DMXHost pulseaudio[1128]: org.bluez.Manager.GetProperties() failed: org.freedesktop.DBus.Error.UnknownMethod: Method GetProperties with signature on interface org.bluez.Manager doesn't exist Oct 19 13:54:13 DMXHost bluetoothd[982]: Endpoint registered: sender=:1.20 path=/MediaEndpoint/A2DPSource Oct 19 13:54:13 DMXHost bluetoothd[982]: Endpoint registered: sender=:1.20 path=/MediaEndpoint/A2DPSink Oct 19 13:54:15 DMXHost dbus[618]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper) Oct 19 13:54:16 DMXHost blueman-mechanism: Starting blueman-mechanism Oct 19 13:54:16 DMXHost dbus[618]: [system] Successfully activated service 'org.blueman.Mechanism' Oct 19 13:54:16 DMXHost blueman-mechanism: loading Config Oct 19 13:54:16 DMXHost blueman-mechanism: loading Ppp Oct 19 13:54:16 DMXHost blueman-mechanism: loading RfKill Oct 19 13:54:16 DMXHost blueman-mechanism: loading Network Oct 19 13:54:16 DMXHost kernel: [ 21.089694] Bluetooth: RFCOMM TTY layer initialized Oct 19 13:54:16 DMXHost kernel: [ 21.089711] Bluetooth: RFCOMM socket layer initialized Oct 19 13:54:16 DMXHost kernel: [ 21.089719] Bluetooth: RFCOMM ver 1.11 Oct 19 13:54:46 DMXHost blueman-mechanism: Exiting Oct 19 13:54:46 DMXHost org.blueman.Mechanism[618]: Exception AttributeError: 'NoneType' object has no attribute 'stdout' in bound method Tee.__del__ of __main__.Tee object at 0xb6d4ca2c ignored Oct 19 13:54:46 DMXHost org.blueman.Mechanism[618]: Starting blueman-mechanism Oct 19 13:54:46 DMXHost org.blueman.Mechanism[618]: loading Config Oct 19 13:54:46 DMXHost org.blueman.Mechanism[618]: loading Ppp Oct 19 13:54:46 DMXHost org.blueman.Mechanism[618]: loading RfKill Oct 19 13:54:46 DMXHost org.blueman.Mechanism[618]: loading Network Oct 19 13:54:46 DMXHost org.blueman.Mechanism[618]: Exiting after killing the two processes: Oct 19 14:16:43 DMXHost dbus[618]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper) Oct 19 14:16:43 DMXHost blueman-mechanism: Starting blueman-mechanism Oct 19 14:16:43 DMXHost dbus[618]: [system] Successfully activated service 'org.blueman.Mechanism' Oct 19 14:16:43 DMXHost blueman-mechanism: loading Config Oct 19 14:16:43 DMXHost blueman-mechanism: loading Ppp Oct 19 14:16:43 DMXHost blueman-mechanism: loading RfKill Oct 19 14:16:43 DMXHost blueman-mechanism: loading Network -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500,
Bug#763582: Update: Apache2 now treating Python scripts the same way as CGI
Doing some research, I think I found the solution to the second issue. I installed libapache2-mod-python, and now Apache treats the same way as the other CGI scripts, but it still will not run any of them, reportedly due to permissions issues. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763582: Update: Apache2 now treating Python scripts the same way as CGI
On 10/1/2014 2:41 PM, Stefan Fritsch wrote:
severity 763582 normal
thanks
On Wednesday 01 October 2014 00:33:11, Leslie Rhorer wrote:
Doing some research, I think I found the solution to the second
issue. I installed libapache2-mod-python, and now Apache treats the
same way as the other CGI scripts, but it still will not run any of
them, reportedly due to permissions issues.
In general, you can't expect a 2.2 configuration to work on 2.4
unchanged. See [1].
In addition, the old authorization directives
don't work well together with the new ones (which is used by the rest
of the configuration). I would recommend that you convert your
configuration to the new syntax (using Require). And increase the
loglevel to find out where the problems are.
[1] http://httpd.apache.org/docs/2.4/upgrading.html
I had already read through that document and implemented several
different versions using Require, but while the exact nature of the
issues changed, nothing allowed scripts to work. I converted back to
tyhe defaul where there are any errors at all. When I try to load a
script in a subdirectory of /var/www/cgi, it merely prints the text of
the script on the screen. 'No errors. In fact, nothing at all in the
error.log file with the loglevel set to info.
So, I started from scratch, and lets take one step at a time. I
un-installed apache2 and then installed it back using apt-get. Then I
re-installed libapache2-mod-python. There is an html file in /var/www
called index.html. It seems to be working. All it is is a redirection
to /var/www/cgi-bin/Thermostat/index.cgi:
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN
http://www.w3.org/TR/html4/loose.dtd;
html
head
titleRedirecting example/title
meta http-equiv=Content-Type content=text/html; charset=iso-8859-1
META HTTP-EQUIV=refresh CONTENT=0; URL=/cgi-bin/Thermostat/index.cgi
/head
body
/body
/html
Here are the active parts of apache2.conf:
Mutex file:${APACHE_LOCK_DIR} default
PidFile ${APACHE_PID_FILE}
Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 5
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}
HostnameLookups Off
ErrorLog ${APACHE_LOG_DIR}/error.log
LogLevel debug
IncludeOptional mods-enabled/*.load
IncludeOptional mods-enabled/*.conf
Include ports.conf
Directory /
Options FollowSymLinks
AllowOverride None
Require all denied
/Directory
Directory /usr/share
AllowOverride None
Require all granted
/Directory
Directory /var/www/
Options Indexes FollowSymLinks
AllowOverride None
Require all granted
/Directory
AccessFileName .htaccess
FilesMatch ^\.ht
Require all denied
/FilesMatch
LogFormat %v:%p %h %l %u %t \%r\ %s %O \%{Referer}i\
\%{User-Agent}i\ vhost_combined
LogFormat %h %l %u %t \%r\ %s %O \%{Referer}i\ \%{User-Agent}i\
combined
LogFormat %h %l %u %t \%r\ %s %O common
LogFormat %{Referer}i - %U referer
LogFormat %{User-agent}i agent
IncludeOptional conf-enabled/*.conf
IncludeOptional sites-enabled/*.conf
sites-available/000-default.conf:
VirtualHost *:80
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
/VirtualHost
sites-available/default-ssl.conf:
IfModule mod_ssl.c
VirtualHost _default_:443
ServerAdmin webmaster@localhost
DocumentRoot /var/www/html
ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined
SSLEngine on
SSLCertificateFile
/etc/ssl/certs/ssl-cert-snakeoil.pem
SSLCertificateKeyFile
/etc/ssl/private/ssl-cert-snakeoil.key
FilesMatch \.(cgi|shtml|phtml|php)$
SSLOptions +StdEnvVars
/FilesMatch
Directory /usr/lib/cgi-bin
SSLOptions +StdEnvVars
/Directory
BrowserMatch MSIE [2-6] \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0
BrowserMatch MSIE [17-9] ssl-unclean-shutdown
/VirtualHost
/IfModule
conf-available/serve-cgi-bin.conf:
IfModule mod_alias.c
IfModule mod_cgi.c
Define ENABLE_USR_LIB_CGI_BIN
/IfModule
IfModule mod_cgid.c
Define ENABLE_USR_LIB_CGI_BIN
/IfModule
IfDefine ENABLE_USR_LIB_CGI_BIN
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
Directory /usr/lib/cgi-bin
AllowOverride None
Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
Require all granted
/Directory
/IfDefine
/IfModule
/usr/lib/cgi-bin:
lrwxrwxrwx 1 root root 17 Mar 7 2014 /usr/lib/cgi-bin - /var/www/cgi-bin
Bug#763193: kde-base: KDE Memory leak still present in jessie
On 9/30/2014 6:10 AM, Maximiliano Curia wrote: $ ps u $pid | tee /tmp/kded4_leak USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND maxy 5568 0.0 2.0 1615380 160056 ? Sl Sep24 0:12 kdeinit4: kded4 [kdeinit] And use the pid to get information about the maps: $ cat /proc/$pid/smaps | tee -a /tmp/kded4_leak And pmap, just because it's easier to read than the plain smaps; $ pmap -x $pid | tee -a /tmp/kded4_leak Since its all text, compressing the /tmp/kded4_leak file before sending it as an attachment would be useful (some mail clients like kmail allow you the compress the attachment directly from it). You can produce a compressed /tmp/kded4_leak.gz with: $ gzip -9 /tmp/kded4_leak Could you please attach the produced file to this bug? kded4_leak.gz Description: application/gzip
Bug#763582: apache2: Apache2 cannot run CGI scripts in jessie
Package: apache2
Version: 2.4.10-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, 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 template lines ***
-- Package-specific info:
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-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
Versions of packages apache2 depends on:
ii apache2-bin 2.4.10-2
ii apache2-data 2.4.10-2
ii lsb-base 4.1+Debian13
ii mime-support 3.56
ii perl 5.20.0-6
ii procps1:3.3.9-7
Versions of packages apache2 recommends:
ii ssl-cert 1.0.34
Versions of packages apache2 suggests:
ii apache2-doc 2.4.10-1
pn apache2-suexec-pristine | apache2-suexec-custom none
pn apache2-utilsnone
ii iceweasel [www-browser] 31.1.0esr-1
ii konqueror [www-browser] 4:4.14.1-1
ii w3m [www-browser]0.5.3-17
Versions of packages apache2-bin depends on:
ii libapr1 1.5.1-3
ii libaprutil1 1.5.3-3
ii libaprutil1-dbd-sqlite3 1.5.3-3
ii libaprutil1-ldap 1.5.3-3
ii libc62.19-11
ii libldap-2.4-22.4.39-1.1+b1
ii liblua5.1-0 5.1.5-7
ii libpcre3 1:8.35-3
ii libssl1.0.0 1.0.1i-2
ii libxml2 2.9.1+dfsg1-4
ii perl 5.20.0-6
ii zlib1g 1:1.2.8.dfsg-2
Versions of packages apache2-bin suggests:
ii apache2-doc 2.4.10-1
pn apache2-suexec-pristine | apache2-suexec-custom none
ii iceweasel [www-browser] 31.1.0esr-1
ii konqueror [www-browser] 4:4.14.1-1
ii w3m [www-browser]0.5.3-17
Versions of packages apache2 is related to:
ii apache2 2.4.10-2
ii apache2-bin 2.4.10-2
-- Configuration Files:
/etc/apache2/mods-available/alias.conf changed:
IfModule alias_module
Alias /icons/ /usr/share/apache2/icons/
Directory /usr/share/apache2/icons
Options FollowSymlinks
AllowOverride None
Order allow,deny
Allow from all
/Directory
Alias /DVD /RAID/DVD
Location /DVD
Options Indexes
Order allow,deny
Allow from all
/Location
Alias /RAID_Server /RAID/Recordings
Location /RAID_Server
Options Indexes
Order allow,deny
Allow from all
/Location
/IfModule
/etc/apache2/sites-available/000-default.conf changed:
VirtualHost *:80
ServerAdmin webmaster@localhost
DocumentRoot /var/www
Directory /
Options FollowSymLinks
AllowOverride None
/Directory
Directory /var/www/
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from all
/Directory
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
Directory /usr/lib/cgi-bin
AllowOverride None
Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
Order allow,deny
Allow from all
/Directory
Directory /var/www/vidmgr
Options +ExecCGI
AddHandler cgi-script .py
DirectoryIndex VidMgrWeb.py
Order allow,deny
Allow from all
/Directory
ErrorLog ${APACHE_LOG_DIR}/error.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
CustomLog ${APACHE_LOG_DIR}/access.log combined
/VirtualHost
VirtualHost *:8080
ServerAdmin webmaster@localhost
DocumentRoot /var/www/cgi-bin/TiVo
Directory /
Options FollowSymLinks
AllowOverride None
/Directory
Directory /var/www/cgi-bin/TiVo
Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from all
/Directory
ScriptAlias / /usr/lib/cgi-bin/
Directory /usr/lib/cgi-bin/TiVo
AllowOverride None
Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
Order allow,deny
Allow from all
/Directory
ErrorLog ${APACHE_LOG_DIR}/error.log
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel
Bug#763586: procmail: Procmail will not deliver to ~/mail/inbox
Package: procmail Version: 3.22-22 Severity: normal Dear Maintainer, *** Reporter, 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 template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-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 Versions of packages procmail depends on: ii libc6 2.19-11 Versions of packages procmail recommends: ii fetchmail 6.3.26-1 ii ssmtp [mail-transport-agent] 2.64-8 procmail suggests no packages. -- no debconf information I just rebuilt my server a few days ago, installing Debian jessie from scratch. Previously it ran wheezy. I am using fetchmail and procmail to deliver the inbound mail to the users, but despite setting up the configurations so the mail will be delivered to /home/user/mail/inbox, procmail insists on delivering to /var/mail/user. I have tried everything of which I can think, to no avail. For temporary purposes, I have a cron script running that detects any new mail and tosses it to the appropriate inbox, but this causes an additional delay of up to 2 minutes in mail delivery, and in any case represents something of a kludge. /etc/fetchmailrc (also in ~/.fetchmailrc): # Configuration created Sat Jan 9 00:35:57 2010 by fetchmailconf 1.54 $Revision: 5165 $ set no syslog set logfile /var/log/fetchmail.log set postmaster postmaster set nobouncemail set no spambounce set properties set daemon 60 poll mail.x.net via mail.x.net with proto POP3 user 'lrhorer' there with password '' is 'lrhorer' here options fetchall forcecr stripcr mda /usr/bin/procmail -f %F -d %T user 'ljrhorer' there with password '' is 'ljrhorer' here options fetchall forcecr stripcr ~/.procmailrc: # .procmailrc # routes incoming mail to appropriate mailboxes PATH=/usr/bin:/usr/local/bin MAILDIR=$HOME/Mail PMDIR=/var/log LOGFILE=$PMDIR/procmail.log LOGABSTRACT=no SHELL=/bin/sh ~/.forward: |IFS=' 'exec /usr/bin/procmail -f-||exit 75 #user -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763193: kde-base: KDE Memory leak still present in jessie
On 9/28/2014 3:31 PM, Maximiliano Curia wrote: Control: force-merge -1 725116 ¡Hola Leslie! El 2014-09-28 a las 10:29 -0500, Leslie Rhorer escribió: This bug was present in wheezy and persists in jessie. It was previously reported under Bug#725116. Ok, merging the two bugs. Usually, if a bug has not been fixed, we prefer to have followups, instead of opening new bugs. Um, OK. Since it is a completely new release of the OS, I thought it would be prudent to open a new report against the new release. It's also been almost exactly a year sine I opened the original report, and this is the first time I have had any response on it. The behavior manifests when using XDMCP, but is not strictly related to KDE alone, becasue it is not present in a fresh install of the operating system from a netinst CD. In order for us to work on a bug, we need to have clear reproduction instructions. I loaded the netinst CD, selected Advanced, had the utility reformat the partitions, and completed the install. I used SSH to get into the system, loaded vim, created an automated SSH login, modified kdmrc and Xaccess to allow logins via XDMCP, set the network interface for a static IP, and rebooted the system. After that, I logged in via XDMCP, and ran a short test to see if the unrestricted growth was still an issue. It did not seem to be. I then loaded the applications listed in the bug report, and went about the business of configuring the new system. At some point, I activated KDE again, and left it running for a time, at which point I noted the memory usage was growing again. Left overnight, the app consumed nearly 100% of the 8G of memory installed in this machine. When first launched, the memory usage is generally in the 500M - 800M range. If there is a leak, it could be that there is a memory area that is not being correctly freed (valgrind can help detecting this) or that certain type of alive object increases but never decreases (a memory profiler might help with this). Can you be a bit more specific? I installed valgrind, but I am going to need some specific binaries against which to run the utility. Only after installing several other packages has the behavior mmanifested itself. The memory utilization has grown from 512MB to 4.5G over a period of 2 days. When you upgrade a program that is currently running, the linux kernel needs to load the old version in memory and it will stay there until the program ends. It could be, that if you upgraded the whole of kde and didn't restart your session this is the reason. I didn't upgrade anything. As I said in my report, this is a virgin install of jessie. What's more, KDE wasn't even running when I added the elements listed in the bug report. The system has been rebooted at handful of times since installing the OS. What's more, the bug report against wheezy was posted almost exactly a year ago, and the system has most certainly been rebooted since then. It could be that there is a leak, but in order to work on that we need more information. Indubitably, but I need to know what you need me to investigate so I can tell you what you need to know. I'm not a duffer, but I'm surely not a guru, either. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763193: kde-base: KDE Memory leak still present in jessie
Package: kde-baseapps Version: 4:4.14.1-1 Severity: important File: kde-base Dear Maintainer, *** Reporter, 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 template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-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 Versions of packages kde-baseapps depends on: ii dolphin 4:4.14.1-1 ii kde-baseapps-bin 4:4.14.1-1 ii kdepasswd 4:4.14.1-1 ii kfind 4:4.14.1-1 ii konqueror 4:4.14.1-1 ii konsole 4:4.14.1-1 ii kwrite4:4.14.1-1 ii plasma-widget-folderview 4:4.14.1-1 Versions of packages kde-baseapps recommends: ii konqueror-nsplugins 4:4.14.1-1 kde-baseapps suggests no packages. -- no debconf information This bug was present in wheezy and persists in jessie. It was previously reported under Bug#725116. The behavior manifests when using XDMCP, but is not strictly related to KDE alone, becasue it is not present in a fresh install of the operating system from a netinst CD. Only after installing several other packages has the behavior mmanifested itself. The memory utilization has grown from 512MB to 4.5G over a period of 2 days. Here is the list of software installed after the OS installation: Commandline: apt-get install vim Commandline: apt-get install gadmin-rsync Commandline: apt-get install dovecot-imapd Commandline: apt-get install nut Commandline: apt-get install nut Commandline: apt-get install gnome-disk-utility Commandline: apt-get install nmon Commandline: apt-get install ssmtp Commandline: apt-get install fetchmail Commandline: apt-get install ffmpeg Commandline: apt-get install samba Commandline: apt-get install winbind Commandline: apt-get install isc-dhcp-server Commandline: apt-get install gnome-system-monitor Commandline: apt-get install --reinstall python-pil Commandline: apt-get install libjpeg62 libjpeg62-dev Commandline: apt-get install libjpeg-dev Commandline: apt-get install libtiff-dev Commandline: apt-get install libfreetype6-dev Commandline: apt-get install cmake -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747863: systemd service fails by default and causes package install failure
Package: nut Version: 2.7.2-1 Followup-For: Bug #747863 Dear Maintainer, *** Reporter, 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 template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-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 Versions of packages nut depends on: ih nut-client 2.7.2-1+b2 iu nut-server 2.7.2-1+b2 nut recommends no packages. nut suggests no packages. -- no debconf information I am experienceing the same issue. NUT fails configuration and so the package installation does not complete. I am unsure how to procede. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725116: 22 hours
After a mere 22 hours uptime, kded4 has grown to 2.6 GiB, and udisks-daemon has swelled to 371.2 MiB. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725116: kde-standard: Apparent memory leak in KDE4
Package: kde-standard Version: 5:77+deb7u1 Severity: important Dear Maintainer, When running KDE4 under a remote XDMCP session, over time a number of applications continually increase their memory useage far beyond reasonable limits. The worst seems to be kded4. After being up only 24 hours, its memory usage has grown to 408 MiB. Nothing special is being done (other than a resync of a RAID6 array under mdadm). I'm using Xming 6.9.0.31 to handle the XDMCP session. I do not know if the same issue occurs under a local session, because the system is headless. Shutting down the XDMCP session recovers much of the memory, although not all. -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.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 Versions of packages kde-standard depends on: ii akregator 4:4.4.11.1+l10n-3+b1 ii ark 4:4.8.4-2 ii dragonplayer 4:4.8.4-2 ii gwenview 4:4.8.4-2 ii juk 4:4.8.4-2 ii kaddressbook 4:4.4.11.1+l10n-3+b1 ii kate 4:4.8.4-1 ii kcalc 4:4.8.4-2 ii kde-plasma-desktop5:77+deb7u1 ii kdeplasma-addons 4:4.8.4-1 ii khelpcenter4 4:4.8.4-2 ii kmail 4:4.4.11.1+l10n-3+b1 ii kmix 4:4.8.4-2 ii knotes4:4.4.11.1+l10n-3+b1 ii kopete4:4.8.4-1+b1 ii korganizer4:4.4.11.1+l10n-3+b1 ii kscreensaver 4:4.8.4-5 ii ksnapshot 4:4.8.4-1 ii kwalletmanager4:4.8.4-3 ii okular4:4.8.4-3+b1 ii plasma-desktopthemes-artwork 4:4.8.4-5 ii polkit-kde-1 0.99.0-3 ii sweeper 4:4.8.4-1 Versions of packages kde-standard recommends: ii freespacenotifier4:4.8.4-6 ii konq-plugins 4:4.8.4-2 ii plasma-widget-networkmanagement 0.9.0.3-1 Versions of packages kde-standard suggests: pn kde-l10nnone ii kde-plasma-desktop 5:77+deb7u1 pn kde-plasma-netbook none pn skanlitenone -- 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#725116: Additional info
After less than 5 additional hours, kded4 is using 1000.5 MiB, and udisks-daemon has risen to 131.4 MiB -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628638: bash: window size not tracked in child shell
-Original Message- From: Jonathan Nieder [mailto:jrnie...@gmail.com] Sent: Monday, May 30, 2011 6:57 PM To: Leslie A Rhorer Cc: 628...@bugs.debian.org Subject: Re: bash: window size not tracked in child shell retitle 628638 bash.1: shopt -s checkwinsize has no effect in non- interactive shells severity 628638 minor tags 628638 + upstream quit Hi Leslie, Leslie A Rhorer wrote: The $COLUMNS variable seems to work properly in a terminal window (with shopt -s checkwinsize), but in a child script, the $COLUMNS variable is null no matter what I try, even if the windows is resized while running the script. I tried to reproduce this like so: cat $HOME/bin/echocolumns \EOF #!/bin/bash shopt -s checkwinsize read tmp echo $COLUMNS EOF chmod +x $HOME/bin/echocolumns echocolumns [resize the terminal, then hit enter] Indeed, it printed a blank line instead of a number of columns. But I can't really fault bash for this behavior when #!/bin/sh tput cols works reliably. OK, why? Why doesn't sending the process a SIGWINCH force it to update the $COLUMNS variable? Do you agree? If so, could you suggest a patch for the manpage? If not, what would be a better behavior? Thanks for reporting, Jonathan Well, I'm not quite sure what you mean by can't really fault bash..., but yes, if there is an acceptable work-around, I suppose merely updating the man page is sufficient. What about the $LINES variable? How can the script obtain it? Assuming there is a way, I would suggest something very close to your report above. Perhaps: The checkwinsize parameter has no effect in non-interactive shells. The $COLUMNS and $LINES parameters will remain null unless updated by the script itself. EXAMPLE: If one must obtain the width of the screen, one may set COLUMNS=$( tput cols ). To obtain the window height, set LINES= Followed by however that is done. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595483: kde: KDE4 Crashes system
I believe this bug report can be closed. I've upgraded two systems to the stable release, and both have been up for more than 24 hours without a failure. One system has been up nearly 3 days. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612079: ksensors: does not retain layout configuration
Package: ksensors Version: 0.7.3-18 Severity: normal Tags: l10n Previous versions of Ksensors properly maintained the user's layout settings when logging back in to KDE. For example, I have 18 tiles enabled in the Ksensors window, and I have them arranged in 3 rows of 6 tiles. After logging off KDE and logging back in, the window comes up with 4 rows of 5 tiles, with the bottom row empty and 3 of the tiles left un-displayed. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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/bash Versions of packages ksensors depends on: ii kdelibs4c2a4:3.5.10.dfsg.1-3 core libraries and binaries for al ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libgcc11:4.4.5-8 GCC support library ii libice62:1.0.6-1 X11 Inter-Client Exchange library ii libpng12-0 1.2.43-1 PNG library - runtime ii libqt3-mt 3:3.3.8b-6Qt GUI Library (Threaded runtime v ii libsensors41:3.1.2-2 library to read temperature/voltag ii libsm6 2:1.1.1-1 X11 Session Management library ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-3 X11 client-side library ii libxext6 2:1.1.1-3 X11 miscellaneous extension librar ii lm-sensors 1:3.1.2-2 utilities to read temperature/volt ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages ksensors recommends: ii hddtemp0.3-beta15-46 hard drive temperature monitoring ksensors 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#612088: kde-plasma-desktop: Desktop window settings not saved correctly
Package: kde-plasma-desktop Version: 5:66 Severity: normal Tags: l10n KDE4 does not correctly save the window information of some autostart utilities. KDE3 properly saved the window size, location, and startup properties of all autostart applications. I upgraded to KDE4, and now some apps do not appear as arranged by the user after the user logs out and back in. For example, running Ksensors, the window is sized to accomodate 3 rows of 6 tiles and places in the lower right-hand corner of the screen. After logging off and back on, the window comes up with 4 rows of 5 tiles with 3 tiles missing, and the window is positioned far away from the lower right-hand side of the screen. Another example is knutclient, which loads to the tray, but does not come up on the desktop. The user must resize/ move / restore the window settings every time he logs in. -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 kde-plasma-desktop depends on: ii hal 0.5.14-3 Hardware Abstraction Layer ii kdebase-apps 4:4.4.5-2 base applications from the officia ii kdebase-runtime 4:4.4.5-1 runtime components from the offici ii kdebase-workspace 4:4.4.5-7 KDE Plasma Workspace components ii plasma-desktop4:4.4.5-7 The KDE Plasma workspace for deskt Versions of packages kde-plasma-desktop recommends: ii kdm 4:4.4.5-7 KDE Display Manager for X11 pn xserver-xorg none (no description available) Versions of packages kde-plasma-desktop suggests: pn kde-l10n none (no description available) -- 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#612091: reportbug: fails to send email
Package: reportbug Version: 4.12.6 Severity: important When run as an ordinary user, reportbug fails to send an email to the Debian tracking system. It creates the email, but the send fails with the folowing output: Sending message via /usr/bin/mail... /usr/bin/mail: invalid option -- 'o' usage: mail [-dEIinv] [-a header] [-b bcc-addr] [-c cc-addr] [-s subject] to-addr ... [-- sendmail-options ...] mail [-dEIiNnv] -f [name] mail [-dEIiNnv] [-u user] Original write failed, wrote bug report to /var/tmp/reportbug-reportbug-20110205-19020-3W3kR1 The send mail package on this system is ssmtp, and it is working for other mail-enabled apps. -- Package-specific info: ** Environment settings: INTERFACE=text ** /home/lrhorer/.reportbugrc: reportbug_version 3.47 mode standard ui text email lrho...@satx.rr.com -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 reportbug depends on: ii apt 0.8.10.3 Advanced front-end for dpkg ii python 2.6.6-3+squeeze5 interactive high-level object-orie ii python-reportbug4.12.6 Python modules for interacting wit reportbug recommends no packages. Versions of packages reportbug suggests: pn debconf-utilsnone (no description available) pn debsums none (no description available) pn dlocate none (no description available) pn emacs22-bin-common | none (no description available) ii file 5.04-5 Determines file type using magic ii gnupg1.4.10-4GNU privacy guard - a free PGP rep ii python-gtk2 2.17.0-4Python bindings for the GTK+ widge pn python-gtkspell none (no description available) pn python-urwid none (no description available) ii python-vte 1:0.24.3-2 Python bindings for the VTE widget ii ssmtp [mail-transpor 2.64-4 extremely simple MTA to get mail o ii xdg-utils1.0.2+cvs20100307-2 desktop integration utilities from -- Configuration Files: /etc/reportbug.conf changed: submit query-bts cc config-files compress email lrho...@fletchergeek.com realname Leslie Rhorer mta /usr/bin/mail ui text verify mode standard -- 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#612092: reportbug: Does not run GUI as normal user
Package: reportbug Version: 4.12.6 Severity: minor When run as a normal user, reportbug issues an error and runs the text-only version of the program. It runs as a GUI if invoked as root. The error is: No protocol specified /usr/lib/pymodules/python2.6/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) **NOTE: This is under an XDMCP session of KDE4.** -- Package-specific info: ** Environment settings: INTERFACE=text ** /home/lrhorer/.reportbugrc: reportbug_version 3.47 mode standard ui text email lrho...@satx.rr.com -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 reportbug depends on: ii apt 0.8.10.3 Advanced front-end for dpkg ii python 2.6.6-3+squeeze5 interactive high-level object-orie ii python-reportbug4.12.6 Python modules for interacting wit reportbug recommends no packages. Versions of packages reportbug suggests: pn debconf-utilsnone (no description available) pn debsums none (no description available) pn dlocate none (no description available) pn emacs22-bin-common | none (no description available) ii file 5.04-5 Determines file type using magic ii gnupg1.4.10-4GNU privacy guard - a free PGP rep ii python-gtk2 2.17.0-4Python bindings for the GTK+ widge pn python-gtkspell none (no description available) pn python-urwid none (no description available) ii python-vte 1:0.24.3-2 Python bindings for the VTE widget ii ssmtp [mail-transpor 2.64-4 extremely simple MTA to get mail o ii xdg-utils1.0.2+cvs20100307-2 desktop integration utilities from -- Configuration Files: /etc/reportbug.conf 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#612094: reportbug: Fails when run as root
Package: reportbug Version: 4.12.6 Severity: normal When run as root, reportbug throws an exception and quits: Backup:/usr/share/man# reportbug /usr/lib/pymodules/python2.6/reportbug/ui/gtk2_ui.py:476: PangoWarning: shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='DejaVu Sans 10', text='' gtk.main () /usr/lib/pymodules/python2.6/reportbug/ui/gtk2_ui.py:476: PangoWarning: pango_layout_set_width: assertion `layout != NULL' failed gtk.main () /usr/lib/pymodules/python2.6/reportbug/ui/gtk2_ui.py:476: PangoWarning: pango_layout_get_extents: assertion `layout != NULL' failed gtk.main () /usr/lib/pymodules/python2.6/reportbug/ui/gtk2_ui.py:476: PangoWarning: pango_layout_get_line_count: assertion `layout != NULL' failed gtk.main () Floating point exception Backup:/usr/share/man# When run as a normal user, reportbug does not fail completely, but it does not run the GUI, either. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612092 -- Package-specific info: ** Environment settings: INTERFACE=text ** /home/lrhorer/.reportbugrc: reportbug_version 3.47 mode standard ui text email lrho...@satx.rr.com -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 reportbug depends on: ii apt 0.8.10.3 Advanced front-end for dpkg ii python 2.6.6-3+squeeze5 interactive high-level object-orie ii python-reportbug4.12.6 Python modules for interacting wit reportbug recommends no packages. Versions of packages reportbug suggests: pn debconf-utilsnone (no description available) pn debsums none (no description available) pn dlocate none (no description available) pn emacs22-bin-common | none (no description available) ii file 5.04-5 Determines file type using magic ii gnupg1.4.10-4GNU privacy guard - a free PGP rep ii python-gtk2 2.17.0-4Python bindings for the GTK+ widge pn python-gtkspell none (no description available) pn python-urwid none (no description available) ii python-vte 1:0.24.3-2 Python bindings for the VTE widget ii ssmtp [mail-transpor 2.64-4 extremely simple MTA to get mail o ii xdg-utils1.0.2+cvs20100307-2 desktop integration utilities from -- Configuration Files: /etc/reportbug.conf changed: submit query-bts cc config-files compress email lrho...@fletchergeek.com realname Leslie Rhorer mta /usr/bin/mail ui text verify mode standard -- 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#595483: kde: KDE4 Crashes system
-Original Message- From: George Kiagiadakis [mailto:kiagiadakis.geo...@gmail.com] Sent: Saturday, September 04, 2010 7:06 AM To: lrhorer; 595...@bugs.debian.org Cc: cont...@bugs.debian.org Subject: Re: Bug#595483: kde: KDE4 Crashes system severity 595483 normal thanks On Sat, Sep 4, 2010 at 2:46 PM, lrhorer lrho...@fletchergeek.com wrote: Package: kde Version: KDE4 Severity: critical Justification: breaks the whole system KDE4 invariably crashes the system. This system is running on an AMD Athlon 64 x 2 processer under Debian Squeeze and kernel 2.6.32-3-amd64. The same symptoms (only worse) are also observed on a Pentium IV system running 2.6.32-trunk-686. One can log in via kdm and bring up KDE4, but sooner or later - usually within an hour or two, the system will crash hard. One then cannot reach the system via telnet, XDMCP, or from the console. Often, it will not even reply to pings. The only option is to hit the power switch. If no KDE session is active, both machines are 100% stable, up continuously for months at a time without issues. If a KDE4 session is active, then after between 30 minutes and 24 hours, the system will crash. No activity is required on the KDE session for the failure to occur, but it seems that changing window foocus often triggers an event. This is most likely due to a faulty gpu driver. I guess you are using amd's proprietary fglrx driver? I have seen such issues in the past with this driver. KDE has no way to lock the system, if a system lock happens this is a problem deep in the kernel or some of its modules. Btw, both of these kernels that you are using are out-of-date. The latest squeeze kernel is 2.6.32-5-amd64. I advise you to upgrade to this kernel and uninstall any proprietary graphics drivers. A normal severity for a bug that causes the system to be completely unusable when the package is in use? That locks up the system like Fort Knox? That causes data loss if any files are still open? I'm hard pressed to think of a more severe problem. There are no proprietary gpu drivers, and please re-read the post. One of the systems is Intel. Both systems were upgraded from Debian Lenny with no problems whatsoever running KDE3. Neither has any problem running gnome. KDE4 was so unusable on the Pentium system I wiped the drive and installed fresh from the Squeeze installer. It didn't help. Both use the graphics processors embedded on the motherboard, with plain-vanilla Debian installations straight from the Debian install CD. The Pentium system is an old Dell Optiplex GX-1 system, which is about as Plain Jane Intel as it gets. The AMD is over a year old. All of the software on both machines - other than that I have written myself - is straight from the Debian repositories. I'll try upgrading the kernel on the AMD system. The Pentium is not local to me, and an upgrade failure would probably be unrecoverable. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-dist
Bug#595483: kde: KDE4 Crashes system
-Original Message- From: George Kiagiadakis [mailto:kiagiadakis.geo...@gmail.com] Sent: Saturday, September 04, 2010 7:48 AM To: Leslie Rhorer Cc: 595...@bugs.debian.org Subject: Re: Bug#595483: kde: KDE4 Crashes system On Sat, Sep 4, 2010 at 3:32 PM, Leslie Rhorer lrho...@fletchergeek.com wrote: A normal severity for a bug that causes the system to be completely unusable when the package is in use? That locks up the system like Fort Knox? That causes data loss if any files are still open? I'm hard pressed to think of a more severe problem. It is a serious problem, but it is not related to the 'kde' package where you reported it. The 'kde' package is a metapackage from lenny and does not even exist in squeeze. The most likely cause of the bug is the kernel, so this bug should eventually be reasigned there and have its severity raised, however I cannot do that until the problem has been fully identified. OK. There are no proprietary gpu drivers, and please re-read the post. One of the systems is Intel. Both systems were upgraded from Debian Lenny with no problems whatsoever running KDE3. Neither has any problem running gnome. KDE4 was so unusable on the Pentium system I wiped the drive and installed fresh from the Squeeze installer. It didn't help. Both use the graphics processors embedded on the motherboard, with plain-vanilla Debian installations straight from the Debian install CD. The Pentium system is an old Dell Optiplex GX-1 system, which is about as Plain Jane Intel as it gets. The AMD is over a year old. All of the software on both machines - other than that I have written myself - is straight from the Debian repositories. An intel system can have an amd graphics card, this is not uncommon. I As I said, neither has a graphics card, and I certainly have never seen an Intel motherboard with an AMD GPU. I would think the execs at Intel would rather have their nards shredded than use an AMD product on one of their motherboards. Come to think of it, however, would the GPU or its drivers even have any effect on XDMCP? I'm not an expert on X11, but I don't think X11 makes use of any local GPU resources - hardware or software - when the X-server is remote, does it? That, along with the fact the GPUs are as different as can be would seem to tend to eliminate the GPUs or their drivers as the source of the issue. That said, on a note related to the Intel GPU, I did have to disable the i915 modeset in /etc/modeprobe.d/i915-kms.conf on the Pentium system or else it would not boot without a monitor. As I recall, the video driver installed by Debian is xserver-xorg-video-intel. (Oh, BTW, I mis-spoke a bit: It's a GX-260, not a GX-1.) On what I don't think is a related note - but could be - KDM does not come up on the console of the AMD machine. The console never switches to the graphical interface. I'm not sure why, but since I never use the console, I really haven't worried about it. I don't recall exactly when this broke. I don't think it was during the upgrade to Squeeze / KDE4, but I could be mistaken. It definitely worked under Lenny, however. still believe the problem is in graphics drivers, though. Even if these are the free intel or radeon drivers. Radeon drivers are known to lock up if their non-free firmware is missing, perhaps you should make sure to install firmware-linux-nonfree and I'm not sure about the I don't follow. The embedded controller on the Asus MB is a Radeon HD 3200, though. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/debian-bugs-dist
Bug#589493: mdadm 3.1.2 fails to grow RAID 6 array - overflows when expanding number of drives in array
Package: mdadm Version: 3.1.2-2 Severity: important Mdadm fails when attempting to add a drive to the array. I believe this is a bug of which Neil Brown is aware and has fixed in code but not released. It is a critical bug for anyone running RAID 5 or RAID 6 who needs to grow their array, which is in turn a critical function. It may not affect those running RAID 0 - 4. Backup:/# mdadm -G -n 10 /dev/md0 mdadm: Need to backup 4503599627313152K of critical section.. mdadm: /dev/md0: Something wrong - reshape aborted -- Package-specific info: --- mdadm.conf DEVICE partitions CREATE owner=root group=disk mode=0660 auto=yes HOMEHOST system MAILADDR lrho...@satx.rr.com PROGRAM /usr/bin/mdadm_notify ARRAY /dev/md0 level=raid6 num-devices=9 metadata=01.2 name=Backup:0 UUID=431244d6:45d9635a:e88b3de5:92f30255 ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=4cde286c:0687556a:4d9996dd:dd23e701 ARRAY /dev/md2 level=raid1 num-devices=2 metadata=01.2 name=Backup:2 UUID=d45ff663:9e53774c:6fcf9968:21692025 ARRAY /dev/md3 level=raid1 num-devices=2 metadata=01.2 name=Backup:3 UUID=51d22c47:10f58974:0b27ef04:5609d357 --- /etc/default/mdadm INITRDSTART='all' AUTOSTART=true AUTOCHECK=true START_DAEMON=true DAEMON_OPTIONS=--syslog VERBOSE=false --- /proc/mdstat: Personalities : [raid1] [raid6] [raid5] [raid4] md0 : active raid6 sdj[9](S) sda[0] sdi[8] sdh[7] sdg[6] sdf[5] sde[4] sdd[3] sdc[2] sdb[1] 10255960064 blocks super 1.2 level 6, 1024k chunk, algorithm 2 [9/9] [U] bitmap: 0/11 pages [0KB], 65536KB chunk md3 : active (auto-read-only) raid1 hda3[0] hdb3[1] 204796548 blocks super 1.2 [2/2] [UU] bitmap: 0/196 pages [0KB], 512KB chunk md2 : active raid1 hda2[2] hdb2[1] 277442414 blocks super 1.2 [2/2] [UU] bitmap: 3/265 pages [12KB], 512KB chunk md1 : active raid1 hda1[0] hdb1[1] 6144704 blocks [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk unused devices: none --- /proc/partitions: major minor #blocks name 30 488386584 hda 316144831 hda1 32 277442550 hda2 33 204796620 hda3 3 64 488386584 hdb 3 656144831 hdb1 3 66 277442550 hdb2 3 67 204796620 hdb3 916144704 md1 92 277442414 md2 93 204796548 md3 80 1465138584 sda 8 16 1465138584 sdb 8 32 1465138584 sdc 8 48 1465138584 sdd 8 64 1465138584 sde 8 80 1465138584 sdf 8 96 1465138584 sdg 8 112 1465138584 sdh 8 128 1465138584 sdi 8 144 1465138584 sdj 90 10255960064 md0 --- LVM physical volumes: --- mount output /dev/md2 on / type ext3 (rw) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) fusectl on /sys/fs/fuse/connections type fusectl (rw) /dev/md0 on /Backup type xfs (rw) /dev/md1 on /boot type ext2 (rw) rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) nfsd on /proc/fs/nfsd type nfsd (rw) --- initrd.img-2.6.32-3-amd64: 16557 blocks f4fbd9099399ab08ba9b9f6c71d77595 ./scripts/local-top/mdadm c079eb5d2b7c064525d97687b3b0e0df ./etc/mdadm/mdadm.conf 077343bb4dacdb4395db3875260f6324 ./sbin/mdadm 74e3b00c27bf7dea2c03a2b6eb3adca4 ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/raid1.ko fecb50b8bb42cb2cfb293ecc6314d044 ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/dm-snapshot.ko 070687a0bb0bcee504d29a7f654d3807 ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/dm-mod.ko d5873a49abdcb752f72e0d47f43ca1a2 ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/raid10.ko 4858c93b0e36def5471e6a00b45ceb9a ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/raid6_pq.ko f3e8f7d66fbb3c9dae713de630d6086b ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/raid456.ko 1a37e82dfd17b08aea8cc3e03f18e302 ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/multipath.ko fcc6ce075dd0fb2b1b80a2766332b556 ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/linear.ko d101951bdcbf8fa33bbac389cee2f75b ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/md-mod.ko 9347393ef038eb856bbd49e4c11fbeed ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/dm-mirror.ko e9008780f29ea7015c40856e6ba22ebf ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/raid0.ko d6c5b858418c25500077c20f103a744a ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/dm-log.ko d557990148b4d72df5c5b4177b2108f2 ./lib/modules/2.6.32-3-amd64/kernel/drivers/md/dm-region-hash.ko --- initrd's /conf/conf.d/md: MD_HOMEHOST='Backup' MD_DEVPAIRS='/dev/md0:raid6 /dev/md1:raid1 /dev/md2:raid1 /dev/md3:raid1' MD_LEVELS='raid6 raid1 raid1 raid1' MD_DEVS=all MD_MODULES='raid1 raid456' --- /proc/modules: dm_mirror 10923 0 - Live 0xa0181000 dm_region_hash 6648 1 dm_mirror, Live
Bug#584188: grub-pc: GRUB will not upgrade to GRUB2 on RAID system
Package: grub-pc Version: 1.98-1 Severity: grave Justification: renders package unusable GRUB legacy cannot be upgraded to GRUB2 on a system with a RAID array for /boot. I upgraded one of my servers from Lenny to Squeeze, but the upgrade of GRUB fails because the package does not know how to upgrade when /boot is a RAID array. This is possibly peripherally related to bug report 575552. If GRUB2 were already installed, I could probably work around this, but as long as the installation fails, there is no way to hand-configure GRUB2, especially not while maintaining a chain-load from GRUB legacy until the operation fo GRUB2 is confirmed. Backup:/# dpkg --configure grub-pc Setting up grub-pc (1.98-1) ... Generating core.img /usr/sbin/grub-probe: error: no mapping exists for `md1'. Auto-detection of a filesystem module failed. Please specify the module with the option `--modules' explicitly. dpkg: error processing grub-pc (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: grub-pc -- Package-specific info: *** BEGIN /proc/mounts /dev/md2 / ext3 rw,relatime,errors=continue,data=ordered 0 0 /dev/md1 /boot ext2 rw,relatime,errors=continue 0 0 /dev/md0 /Backup xfs rw,relatime,attr2,nobarrier,sunit=2048,swidth=14336,noquota 0 0 *** END /proc/mounts *** BEGIN /boot/grub/device.map (hd0) /dev/hda (hd1) /dev/hdb (hd2) /dev/sda (hd3) /dev/sdb (hd4) /dev/sdc (hd5) /dev/sdd (hd6) /dev/sde (hd7) /dev/sdf (hd8) /dev/sdg (hd9) /dev/sdh (hd10) /dev/sdi *** END /boot/grub/device.map -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-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/bash Versions of packages grub-pc depends on: ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy ii grub-common 1.98-1 GRand Unified Bootloader, version ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii ucf 3.0025 Update Configuration File: preserv grub-pc recommends no packages. Versions of packages grub-pc suggests: ii desktop-base 5.0.5 common files for the Debian Deskto -- debconf information: grub2/kfreebsd_cmdline: * grub2/linux_cmdline: * grub-pc/chainload_from_menu.lst: true grub-pc/kopt_extracted: true grub-pc/install_devices: grub-pc/postrm_purge_boot_grub: false grub2/kfreebsd_cmdline_default: quiet grub2/linux_cmdline_default: quiet -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
