Bug#991339: Unable to access battery features from tlp package
Package: release-notes Severity: normal Hello, Battery status and features cannot be accessed from Lenovo / Thinkpad notebook via tlp package in Bullseye. This is due required kernel module have not been merged to new linux kernel. Reference from tlp author: https://linrunner.de/tlp/faq/battery.html Cheers, Alan
Bug#991017: unbound: remote-control port 127.0.0.1:8953 was opened to listen unexpectedly
Package: unbound Version: 1.13.1-1 Severity: normal After upgrade from buster to bullseye with same config file, port 127.0.0.1:8953 was additionally listened for. >From man page, this is "remote-control" port and the default "control-enable" >is "no". When adding extra config section "remote-control" as below, the listening port 127.0.0.1:8953 was gone. remote-control: control-enable: no server: ... The default setting from man page and the observing behavior mismatch. Cheers, Alan
Bug#990025: libvirtd massively logs "Failed to open file '.../xxx.qcow2': No such file or directory"
Package: libvirt-daemon Version: 7.0.0-3 When boot up, libvirtd log hundreds lines of 'Failed to open file '.../xxx.qcow2': No such file or directory' messages repeatedly. The qcow2 files were defined in VM configs but these qcow2 files are no longer exist. Related bug report and patch is available: https://bugzilla.redhat.com/show_bug.cgi?id=1692100 Below is the log: # journalctl -- Journal begins at Fri 2021-06-18 10:10:15 HKT, ends at Fri 2021-06-18 11:59:21 HKT. -- Jun 18 10:10:15 HOSTNAME systemd-journald[48407]: Received SIGTERM from PID 1 (systemd). Jun 18 10:10:15 HOSTNAME systemd[1]: systemd-journald.service: Succeeded. Jun 18 10:10:15 HOSTNAME systemd[1]: Stopped Journal Service. Jun 18 10:10:15 HOSTNAME systemd[1]: Starting Journal Service... Jun 18 10:10:15 HOSTNAME systemd-journald[9354]: Journal started Jun 18 10:10:15 HOSTNAME systemd-journald[9354]: System Journal (/var/log/journal/###) is 96.0M, max 100.0M, 3.9M free. Jun 18 10:10:15 HOSTNAME systemd[1]: Started Journal Service. Jun 18 10:10:15 HOSTNAME systemd[1]: Starting Flush Journal to Persistent Storage... Jun 18 10:10:15 HOSTNAME systemd-journald[9354]: System Journal (/var/log/journal/###) is 96.0M, max 100.0M, 3.9M free. Jun 18 10:10:15 HOSTNAME systemd[1]: Finished Flush Journal to Persistent Storage. Jun 18 10:10:15 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM1.qcow2': No such file or directory Jun 18 10:10:15 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM2.qcow2': No such file or directory Jun 18 10:10:15 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM3.qcow2': No such file or directory Jun 18 10:10:15 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM4.qcow2': No such file or directory Jun 18 10:10:15 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM5.qcow2': No such file or directory Jun 18 10:10:15 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM6.qcow2': No such file or directory Jun 18 10:10:15 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM7.qcow2': No such file or directory Jun 18 10:10:15 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM8.qcow2': No such file or directory Jun 18 10:10:15 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM9.qcow2': No such file or directory Jun 18 10:10:16 HOSTNAME systemd[1]: Reloading. Jun 18 10:10:16 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM1.qcow2': No such file or directory Jun 18 10:10:16 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM2.qcow2': No such file or directory Jun 18 10:10:16 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM3.qcow2': No such file or directory Jun 18 10:10:16 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM4.qcow2': No such file or directory Jun 18 10:10:16 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM5.qcow2': No such file or directory Jun 18 10:10:16 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM6.qcow2': No such file or directory Jun 18 10:10:16 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM7.qcow2': No such file or directory Jun 18 10:10:16 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM8.qcow2': No such file or directory Jun 18 10:10:16 HOSTNAME libvirtd[1202]: Failed to open file '/opt/VM9.qcow2': No such file or directory Jun 18 10:10:16 HOSTNAME systemd[1]: Reloading. ... (hundreds of similar lines) ... Jun 18 10:11:34 HOSTNAME systemd[1]: Starting Self Monitoring and Reporting Technology (SMART) Daemon... Jun 18 10:11:34 HOSTNAME systemd-timesyncd[9282]: Timed out waiting for reply from 222.166.0.137:123 (1.debian.pool.ntp.org).
Bug#964362: chromium crash frequently, SEGV_MAPERR
Source: chromium Version: 83.0.4103.116-1~deb10u2 Followup-For: Bug #964362 Dear Maintainer, Frequent crash still occurred after upgrade from 83.0.4103.116-1~deb10u1 to ~deb10u2. Crash occurs after executing chromium for few minutes. Slow responsiveness found from 83..debu10u1 did not occur in this version. Command: /usr/bin/chromium --proxy-server="X.X.X.X:X" --proxy-bypass-list="X.X.*;X.X.*;*.X" --disk-cache-dir=/dev/null Error log: [9545:9545:0708/100337.163855:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [9506:9561:0708/100337.177992:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/js [9506:9562:0708/100337.178131:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/wasm [9506:9561:0708/100337.193285:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/js [9506:9562:0708/100337.193285:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/wasm [9506:9561:0708/100337.193321:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Code Cache/js [9506:9562:0708/100337.193331:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Code Cache/wasm [9506:9527:0708/100337.275442:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/js [9506:9529:0708/100337.275452:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/wasm [9506:9527:0708/100337.275485:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/js [9506:9529:0708/100337.275493:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/wasm [9506:9527:0708/100337.275494:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Code Cache/js [9506:9529:0708/100337.275507:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Code Cache/wasm [9550:9630:0708/100337.294177:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Cache [9550:9630:0708/100337.294308:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Cache [9550:9630:0708/100337.294328:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Cache [9550:9629:0708/100337.294541:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Cache [9550:9629:0708/100337.294580:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Cache [9550:9629:0708/100337.294589:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Cache [9550:9616:0708/100337.303063:ERROR:disk_cache.cc(184)] Unable to create cache [9506:9506:0708/100337.305955:ERROR:disk_cache.cc(184)] Unable to create cache [9506:9506:0708/100337.305995:ERROR:disk_cache.cc(184)] Unable to create cache [9506:9528:0708/100346.855696:ERROR:connection_factory_impl.cc(420)] Failed to connect to MCS endpoint with error -111 [9506:9528:0708/100915.111885:ERROR:socket_stream.cc(218)] Closing stream with result -2 [9506:9528:0708/100915.118034:ERROR:connection_factory_impl.cc(420)] Failed to connect to MCS endpoint with error -111 Received signal 11 SEGV_MAPERR 7f01c431fad7 #0 0x564a040cc469 (/usr/lib/chromium/chromium+0x51f9468) #1 0x564a0402a193 (/usr/lib/chromium/chromium+0x5157192) #2 0x564a040cbff1 (/usr/lib/chromium/chromium+0x51f8ff0) #3 0x7ff2ed488730 (/lib/x86_64-linux-gnu/libpthread-2.28.so+0x1272f) #4 0x7ff2e7394d48 (/lib/x86_64-linux-gnu/libc-2.28.so+0x7fd47) #5 0x7ff2e7397a58 (/lib/x86_64-linux-gnu/libc-2.28.so+0x82a57) #6 0x7ff2e739956a __libc_malloc #7 0x564a040e3bee operator new() #8 0x7ff2e760e3cd std::__cxx11::basic_string<>::reserve() #9 0x7ff2e7602845 std::__cxx11::basic_stringbuf<>::overflow() #10 0x7ff2e760c9cb std::basic_streambuf<>::xsputn() #11 0x7ff2e75fdb34 std::__ostream_insert<>() #12 0x564a040cc7b9 (/usr/lib/chromium/chromium+0x51f97b8) #13 0x564a040cc844 (/usr/lib/chromium/chromium+0x51f9843) #14 0x564a0403c9d2 (/usr/lib/chromium/chromium+0x51699d1) #15 0x564a0403eb1e (/usr/lib/chromium/chromium+0x516bb1d) #16 0x564a027a762a (/usr/lib/chromium/chromium+0x38d4629) #17 0x564a027a767e (/usr/lib/chromium/chromium+0x38d467d) #18 0x564a01e4d98f (/usr/lib/chromium/chromium+0x2f7a98e) #19 0x564a02761559 (/usr/lib/chromium/chromium+0x388e558) #20 0x564a0276179e (/usr/lib/chromium/chromium+0x388e79d) #21 0x564a027aae67 (/usr/lib/chromium/chromium+0x38d7e66) #22 0x564a027d6ac2 (/usr/lib/chromium/chromium+0x3903ac1) #23 0x564a027d6d7e (/usr/lib/chromium/chromium+0x3903d7d) #24 0x564a027
Bug#864918: icewm shows no taskbar
> > Package: icewm > > Version: 1.3.8+mod+20161220-1 > > Severity: important > > > > After login xorg, icewm shows no taskbar. Only a blank screen (gray > > background color) with cursor. Tried below config: > > And how do you now that it runs? Does a right-click display a menu? ps auxwf shows: root 1892 19.1 0.3 478820 75988 tty7 Rsl+ 14:48 3:50 \_ /usr/lib/xorg/Xorg -dpi 96 :0 vt7 -nolisten tcp -auth /var/lib/xdm/authdir/authfiles/A:0-Oa root 2130 0.0 0.0 88840 7052 ?Ss 14:48 0:01 \_ -:0 debian2712 0.0 0.0 8540 1600 ?Ss 14:58 0:00 \_ x-session-manager debian2744 0.0 0.0 13132 332 ?Ss 14:58 0:00 \_ /usr/bin/ssh-agent x-session-manager debian2745 0.2 0.0 89956 5684 ?SNs 14:58 0:01 \_ icewmbg debian7820 0.0 0.0 99124 8316 ?Rs 15:08 0:00 \_ icewm --notify > > nodm + icewm => no taskbar > > xdm + icewm (default config) => no taskbar > > xdm + icewm (custom config) => no taskbar > > lightdm + icewm (default config) => no taskbar > > lightdm + icewm (custom config) => no taskbar > > lightdm + xfce => everything ok > > You might have a general problem. Check: > > update-alternatives --display x-window-manager > update-alternatives --display x-session-manager Seems they have been default. Running update-alternatives as shown below, and restart xdm afterward is still the same: # update-alternatives --display x-window-manager x-window-manager - auto mode link best version is /usr/bin/icewm link currently points to /usr/bin/icewm link x-window-manager is /usr/bin/x-window-manager slave x-window-manager.1.gz is /usr/share/man/man1/x-window-manager.1.gz /usr/bin/icewm - priority 50 slave x-window-manager.1.gz: /usr/share/man/man1/icewm.1.gz # update-alternatives --display x-session-manager x-session-manager - auto mode link best version is /usr/bin/icewm-session link currently points to /usr/bin/icewm-session link x-session-manager is /usr/bin/x-session-manager /usr/bin/icewm-session - priority 10 > > The icewm custom config (/etc/X11/icewm and /home/username/.icewm) was used > > in Jessie without problem. No error messages found. > > Please go to a text console (Ctrl-F2) and make a detailed process list, > i.e. "pstree" or "ps aufwx" . Checking ~/.xsession-errors file might > also be interesting. .xsession-errors get hundred lines of: ... IceWM: using /home/debian/.icewm for private configuration files IceWM: using /home/debian/.icewm for private configuration files IceWM: using /home/debian/.icewm for private configuration files ... This issue also occur from another system upgraded from Jessie. I think this issue breaks most, even not all, users using icewm.
Bug#864918: icewm shows no taskbar
Package: icewm Version: 1.3.8+mod+20161220-1 Severity: important After login xorg, icewm shows no taskbar. Only a blank screen (gray background color) with cursor. Tried below config: nodm + icewm => no taskbar xdm + icewm (default config) => no taskbar xdm + icewm (custom config) => no taskbar lightdm + icewm (default config) => no taskbar lightdm + icewm (custom config) => no taskbar lightdm + xfce => everything ok The icewm custom config (/etc/X11/icewm and /home/username/.icewm) was used in Jessie without problem. No error messages found. System: Debian GNU/Linux 9.0rc5 (apt-get update + upgrade on 2017-06-16)
Bug#852760: Input methods have no effect under LXDE
Package: ibus
Version: jessie rc1
Dear Maintainer,
* What led up to the situation?
Select Cangjie3 / Quick3 input method but has no effect, keyboard keys
pressed are passing through directly to applications Leafpad / Firefox.
* What exactly did you do (or not do) that was effective (or ineffective)?
Source:
netinst iso-cd weekly built on 2017-01-23, downloaded from debian
website
System:
Debian Jessie running qemu-kvm 1:2.1+dfsg-12+deb8u6
KVM hardware:
1 x IDE CDROM (debian-testing netinst iso-cd)
1 x 8GB virtio disk (vda)
1 x virtio network adapter
QXL display
Key steps to get error:
1. Clean install the system, with task select "LXDE desktop", "SSH
Server", "System Tools" only
2. Install ibus as root: apt-get install ibus ibus-table-cangjie3
ibus-table-quick3 fonts-arphic-ukai fonts-arphic-uming
3. Reboot system
4. Login LXDE as normal user
5. Open LXDE desktop menu bar --> Preferences --> iBus Preferences
6. Activate Cangjie3 and Quick3 input method, Set "Shift-Space" as
hotkey, "Show Property Panel" to "Always"
7. Reboot system
8. Login LXDE as the same user
9. Open Leafpad, switch input method to Cangjie3 by hotkey "Shift-Space"
10. Type alphabet keys (e.g. "mmm")
* What was the outcome of this action?
"mmm" show on Leafpad
* What outcome did you expect instead?
"?" ("three" show on Leafpad)
-- System Information:
Debian Release: stretch/sid
Architecture: amd64
Bug#852653: Grub install failed on encrypted LVM disk
Dear Maintainer: Another test found that the detection of "Encryption configuration failure" exist while failed if the disk is configured as in case #2: #1. For below disk partition setup, "Encryption configuration failure ... You should go back and setup a /boot partition" show correctly. vda --> vda_crypto --> vg --> lv / #2. For below disk partition setup, no warning message and the system keep install until grub installation stage shows failed to isntall grub error: vda --> vda_crypto --> vg --> lvroot / lvhome / lvswap / Regards, Alan From: laalaa Sent: Thursday, January 26, 2017 12:38:19 PM To: 852...@bugs.debian.org Subject: Grub install failed on encrypted LVM disk Dear Maintainer: Problem solved. Mark "BOOT" flag in the encrypted disk. Then grub install completed successfully. Suggest to verify BOOT flag has been marked to allow proceeding to next installation stage. Regards, Alan
Bug#852660: Failed to cancel NTP detection in graphical install mode
Package: installation-reports Version: jessie rc1 Dear Maintainer, * What led up to the situation? Failed to cancel NTP detection during installation in 'Graphical Install' mode. * What exactly did you do (or not do) that was effective (or ineffective)? Source: netinst iso-cd weekly built on 2017-01-23, downloaded from debian website System: Debian Jessie running qemu-kvm 1:2.1+dfsg-12+deb8u6 KVM hardware: 1 x IDE CDROM (debian-testing netinst iso-cd) 1 x 8GB virtio disk (vda) 1 x virtio network adapter QXL display Key steps to get error: 1. Select "Graphical install" 2. Configure network adapter 3. During "Configure the clock" stage, click / press "Cancel" button shown on the screen * What was the outcome of this action? The status bar stopped refreshing, while not proceed to next stage immediately. Wait for some tenth seconds, proceed to next stage. * What outcome did you expect instead? Proceed to next stage in few seconds, same as "Text install mode". -- System Information: Debian Release: stretch/sid Architecture: amd64
Bug#852653: Grub install failed on encrypted LVM disk
Dear Maintainer: Problem solved. Mark "BOOT" flag in the encrypted disk. Then grub install completed successfully. Suggest to verify BOOT flag has been marked to allow proceeding to next installation stage. Regards, Alan
Bug#852653: Grub install failed on encrypted LVM disk
Package: installation-reports Version: jessie rc1 Severity: critical Justification: failed to install grub Dear Maintainer, * What led up to the situation? Failed installation of grub under KVM system with encrypted LVM disk. * What exactly did you do (or not do) that was effective (or ineffective)? Source: netinst iso-cd weekly built on 2017-01-23, downloaded from debian website System: Debian Jessie running qemu-kvm 1:2.1+dfsg-12+deb8u6 KVM hardware: 1 x IDE CDROM (debian-testing netinst iso-cd) 1 x 8GB virtio disk (vda) 1 x virtio network adapter QXL display Partition disks: Encrypte vda disk and setup with LVM: Encrypted volume (vda1_crypt) - 8.6GB #1 8.6GB K lvm LVM VG vg, LV lvhome - 4.1GB #1 4.1GB K ext4 /home LVM VG vg, LV lvroot - 4.1GB #1 4.1GB K ext4 / LVM VG vg, LV lvswap - 255.9MB #1 255.9MB K swap swap Virtual disk 1 (vda) - 8.6GB Virtio Block Device #1 primary 8.6GB K crypto GRUB installation: Install the GRUB boot loader to the master boot record --> Yes Device for boot loader installation: /dev/vda Force GRUB installation to the EFI removable media path? Yes * What was the outcome of this action? Error message: Unable to install GRUB in /dev/vda Executing 'grub-install /dev/vda' failed. This is a fatal error. * What outcome did you expect instead? Installation of grub completed. -- System Information: Debian Release: stretch/sid Architecture: amd64
Bug#798815: fluidsynth rejects server connection
Package: fluidsynth Version: 1.1.6-2 Problem: Start fluidsynth as server mode (-i -s), listening to default TCP port 9800, once connected will disconnect immediately. The bug was fixed upstream, hope it can be merged to official build, thanks: http://lists.nongnu.org/archive/html/fluid-dev/2015-01/msg00012.html Current result: $ fluidsynth -i -s & ... $ ps grep fluidsynth 828 pts/0 00:00:00 fluidsynth -i -s $ netstat -tln Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:9800 0.0.0.0:* LISTEN $telnet 127.0.0.1 9800 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. Connection closed by foreign host. $ Expected result: $telnet 127.0.0.1 9800 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. > (waiting for input such as 'help all')
Bug#747927: qemu-utils: qemu-nbd blocks
Package: linux-image Version: 3.16.0-4-amd64 Control: found 747927 linux/3.16.0-4
Bug#789651: tacacs+: Incomplete systemd integration
Package: tacacs+ Version: 4.0.4.27a-1 Severity: normal Description: tacacs+ is missing 'is-enabled' systemd integration: # systemctl is-active tacacs_plus.service active # systemctl enable tacacs_plus.service Synchronizing state for tacacs_plus.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d tacacs_plus defaults Executing /usr/sbin/update-rc.d tacacs_plus enable # systemctl is-enabled tacacs_plus.service Failed to get unit file state for tacacs_plus.service: No such file or directory Expected result: # systemctl is-enabled tacacs_plus.service enabled Workaround: Check if the link /etc/rc5.d/S02tacacs_plus exist or not, instead of using 'systemctl is-enabled' command.
Bug#784391: irqbalance: Logs flooded with "irq ### affinity_hint subset empty"
Package: irqbalance Version: 1.0.6-3 Severity: normal In Jessie amd64 dual CPU system, irqbalance flooded /var/log/daemon.log with below messages: May 6 09:23:24 servername /usr/sbin/irqbalance: irq 154 affinity_hint subset empty May 6 09:23:24 servername /usr/sbin/irqbalance: irq 155 affinity_hint subset empty May 6 09:23:24 servername /usr/sbin/irqbalance: irq 156 affinity_hint subset empty May 6 09:23:24 servername /usr/sbin/irqbalance: irq 157 affinity_hint subset empty May 6 09:23:24 servername /usr/sbin/irqbalance: irq 158 affinity_hint subset empty May 6 09:23:24 servername /usr/sbin/irqbalance: irq 159 affinity_hint subset empty May 6 09:23:24 servername /usr/sbin/irqbalance: irq 160 affinity_hint subset empty May 6 09:23:24 servername /usr/sbin/irqbalance: irq 161 affinity_hint subset empty May 6 09:23:24 servername /usr/sbin/irqbalance: irq 162 affinity_hint subset empty May 6 09:23:24 servername /usr/sbin/irqbalance: irq 163 affinity_hint subset empty May 6 09:23:34 servername /usr/sbin/irqbalance: irq 128 affinity_hint subset empty May 6 09:23:34 servername /usr/sbin/irqbalance: irq 129 affinity_hint subset empty May 6 09:23:34 servername /usr/sbin/irqbalance: irq 130 affinity_hint subset empty May 6 09:23:34 servername /usr/sbin/irqbalance: irq 131 affinity_hint subset empty May 6 09:23:34 servername /usr/sbin/irqbalance: irq 132 affinity_hint subset empty May 6 09:23:34 servername /usr/sbin/irqbalance: irq 133 affinity_hint subset empty May 6 09:23:34 servername /usr/sbin/irqbalance: irq 134 affinity_hint subset empty May 6 09:23:34 servername /usr/sbin/irqbalance: irq 135 affinity_hint subset empty May 6 09:23:34 servername /usr/sbin/irqbalance: irq 136 affinity_hint subset empty May 6 09:23:34 servername /usr/sbin/irqbalance: irq 137 affinity_hint subset empty The logged time interval is 10 seconds. The number of rows logged per interval is 24, which is the total number of physical CPU cores of the system (2 x 12 core). Same Bug in ubuntu: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1321425 Workaround to add "--hintpolicy=ignore" solved: # ps ax | grep irqbalance 18126 ? Ss 0:00 /usr/sbin/irqbalance --pid=/var/run/irqbalance.pid # vi /etc/default/irqbalance OPTIONS="--hintpolicy=ignore" # sudo systemcl restart irqbalance # ps ax | grep irqbalance 18126 ? Ss 0:00 /usr/sbin/irqbalance --pid=/var/run/irqbalance.pid --hintpolicy=ignore I would suggest detection of SMP system from the installation script and add this OPTIONS to /etc/irqbalance/default. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#709335: libvirt-bin: Memory leak whilst clients connected.
The bug is still exist in version 0.9.12.3-1+deb7u1 # uptime 10:14:03 up 39 days, 16 min, 2 users, load average: 0.24, 0.27, 0.25 # top top - 10:14:32 up 39 days, 17 min, 2 users, load average: 0.20, 0.26, 0.24 Tasks: 106 total, 1 running, 105 sleeping, 0 stopped, 0 zombie %Cpu(s): 1.1 us, 1.1 sy, 0.0 ni, 96.3 id, 1.5 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 8196188 total, 8012432 used, 183756 free, 336 buffers KiB Swap:0 total,0 used,0 free, 186404 cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 28184 libvirt- 20 0 4387m 4.0g 840 S 4.4 51.4 7207:43 kvm 2486 root 20 0 2946m 2.6g 3244 S 0.0 33.1 791:16.66 libvirtd 6403 libvirt- 20 0 894m 526m 1176 S 0.7 6.6 393:18.91 kvm 8GB RAM, 4GB allocated to windows-2012-64bit client, 512MB allocated to wheezy-32bit client. And libvirtd used 2.6GB after 39 days up. Almost to crash!
Bug#580226: wkhtmltopdf: Do not require a running X server
As xserver or xvfb is required to make wkhtmltopdf functioning, it is suggested to change the dependency from "suggest" to "required", or to show README.Debian mandatory in post-install stage.
