Bug#1030129: ca-certificates-java - Fails to install: Error loading java.security file

I haven't been able to reproduce this on a Debian 12 container. For those that are still seeing this problem, is it always reproducible? If there is a race, is there a way to force this (e.g. via apt settings or manual package install ordering with dpkg etc.)? Thanks, Tim.

Bug#912171: pcsxr: Cannot configure/use 2nd joypad

Package: pcsxr Version: 1.9.94-5 Followup-For: Bug #912171 X-Debbugs-Cc: t...@buttersideup.com I should add that in my tests (bookworm and bullseye on 3 different x86_64 machines), this bug makes pcsxr segfault when entering the configuration UI, or launching a game immediately if any joystick /

Bug#912171: pcsxr: Cannot configure/use 2nd joypad

Package: pcsxr Version: 1.9.94-5 Followup-For: Bug #912171 X-Debbugs-Cc: t...@buttersideup.com This bug is still present. I independently found it, and can confirm that the previous fix should work. An alternative fix is to call SDL_JoystickNameForIndex() The patch below lacks a guarding ifdef

Bug#1036033: upgrade-reports: bullseye -> bookworm kernel package upgrade fails when ddcci-dkms package installed

This took a while to track down - sorry for the delay. The machine which was being upgraded had a non-functional shim in place instead of rpm. This had been done to satisfy a hardware-vendor provided firmware upgrade, which would not work unless an rpm executable was found on the system

Bug#1036033: upgrade-reports: bullseye -> bookworm kernel package upgrade fails when ddcci-dkms package installed

Hi Stephen, Sorry for the delay - busy with family, work and other matters... I've restored a backup to a VM, and re-run the upgrade there, taking care to follow exactly the upgrade instructions at: https://www.debian.org/releases/testing/amd64/release-notes.en.pdf ...this lead to a

Bug#1036041: upgrade-reports: Dell XPS 9550 fails to boot after bullseye to bookworm upgrade - grub/bios interaction bug?

Package: upgrade-reports Severity: normal X-Debbugs-Cc: t...@seoss.co.uk My previous release is: bullseye I am upgrading to: bookworm Upgrade date: 2022-05-06 Method: apt dist-upgrade Contents of /etc/apt/sources.list: deb http://deb.debian.org/debian/ bookworm main non-free non-free-firmware

Bug#1036033: upgrade-reports: bullseye -> bookworm kernel package upgrade fails when ddcci-dkms package installed

Package: upgrade-reports Severity: normal X-Debbugs-Cc: t...@seoss.co.uk (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) My previous release is: bullseye I am upgrading to: bookworm Upgrade date:

Bug#1036032: upgrade-reports: mariadb upgrade fails when KDE akonadi installed

Package: upgrade-reports Severity: normal X-Debbugs-Cc: t...@seoss.co.uk (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) My previous release is: Bullseye I am upgrading to: Bookworm Archive date:

Bug#1022276: linux-image-6.0.0-1-amd64: Debian kernels since 5.19 drop Solarflare SFC9000 (SFN5xxx SFN6xxx) support.

Package: src:linux Version: 6.0.2-1+b1 Severity: normal Tags: patch X-Debbugs-Cc: t...@seoss.co.uk Firstly, thanks for the work on the Debian kernel packaging! Upstream kernel v5.19 incorporated a patch which split out Solarflare SFC9000 (NIC model SFN5000 and SFN6000 series) driver support from

Bug#990863: libserialport0: libserialport tries to use termiox on bullseye, and fails to open serial ports

Package: libserialport0 Version: 0.1.1-3+b1 Severity: important Tags: upstream patch X-Debbugs-Cc: t...@seoss.co.uk Serial port open seems to fail on bullseye. Strace output follows: 1512868 openat(AT_FDCWD, "/dev/ttyACM0", O_RDWR|O_NOCTTY|O_NONBLOCK) = 9 1512868 ioctl(9, TCGETS, {B9600 opost

Bug#990715: prometheus-smokeping-prober: Package is non-functional by default, and steps necessary to make it functional are not documented and non-obvious

Package: prometheus-smokeping-prober Version: 0.4.1-2+b4 Severity: important X-Debbugs-Cc: t...@seoss.co.uk Thanks for packaging this in Debian! Unfortunately it does appear to have an important problem which I think most users will hit, and is actually quite difficult to debug. Installing this

Bug#990222: crmsh: Bundled vim addons cannot be enabled.

Package: crmsh Version: 4.2.1-2 Severity: normal Tags: patch X-Debbugs-Cc: t...@seoss.co.uk The vim syntax highlighting addon seems to be broken: root@crmshtest:~# vim-addons status # Name User Status System Status haproxy removed installed pcmk

Bug#989831: konsole: Bitmap fonts rendered incorrectly if display scaling is enabled

Package: konsole Version: 4:20.12.3-1 Followup-For: Bug #989831 X-Debbugs-Cc: t...@seoss.co.uk On 16/06/2021 05:07, Norbert Preining wrote: > On Mon, 14 Jun 2021, Tim Small wrote: >> instead each character is rendered with large amounts >> of surrounding space. >> >>

Bug#989834: konsole: Only possible to select the smallest available size for OpenType Bitmap fonts

Package: konsole Version: 4:20.12.3-1 Severity: normal Tags: a11y X-Debbugs-Cc: t...@seoss.co.uk When selecting a bitmap font via Konsole -> Settings -> Configure Konsole -> Profiles -> Edit -> Appearance -> Font -> Choose, only the smallest font size is displayed for OpenType bitmap fonts. e.g.

Bug#989831: konsole: Bitmap fonts rendered incorrectly if display scaling is enabled

Package: konsole Version: 4:20.12.3-1 Severity: normal Tags: a11y X-Debbugs-Cc: t...@seoss.co.uk When a bitmap font is selected, and display scaling is also enabled (KDE -> System Settings -> Display Configuration -> Global scale != 100%), then the fonts are rendered at their unscaled size (this

Bug#989209: haproxy: Default /etc/haproxy/haproxy.cfg config file includes SSL config for 2.0.3 instead of 2.2.9

Package: haproxy Version: 2.2.9-1 Severity: normal After installing the version 2.2.9-1 Debian package, the default /etc/haproxy/haproxy.cfg contains an SSL configuration excerpt in the global section which has been generated with:

Bug#988915: automysqlbackup: Many spelling, grammar and other typos in comments and docs.

Package: automysqlbackup Version: 2.6+debian.4-3 Severity: minor Tags: patch I've attached a patch which corrects many spelling, grammar and other typos in comments and docs. I didn't correct errors in the changelog section. This patch applies on top of the compression enhancement and bugfix

Bug#988914: automysqlbackup: COMP=bzip2 and COMPDIRECT=yes results in a gzip-compressed file with a .bz2 suffix

Package: automysqlbackup Version: 2.6+debian.4-3 Severity: normal Tags: patch Combining the COMP=bzip2 and COMPDIRECT=yes arguments results in gzip compressed database dumps being created, but with ".bz2" file suffixes. I've created a patch which fixes this, and also adds support for pigz, zstd,

Bug#987061: phpmyadmin: Error "Illegal mix of collations" when clicking on Priviliges tab after default installation

Package: phpmyadmin Version: 4:5.0.4+dfsg2-2 Followup-For: Bug #987061 This has been fixed upstream, see: https://github.com/phpmyadmin/phpmyadmin/pull/16442 Patch looks straightforward, so would be great to get this into bullseye if poss.

Bug#965965: openjdk-11-jdk-headless: JRE fails at startup on ARM Cortex A8

Package: openjdk-11-jdk-headless Version: 11.0.7+10-3~deb10u1 Severity: normal Tags: upstream Dear Maintainer, jre fails on Cortex-A8 (Sitara AM335x): # # A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=0xb40c7b60, pid=13376, tid=13385 # # JRE version:

Bug#948375: Debian Ceph maintenance release / support policy

Hello, What would the procedure be for getting Debian to adopt a similar policy with Ceph as it does with Chromium, Firefox, Thunderbird? As a user of Ceph on Debian, it's disappointing that I should basically ignore the Ceph packages in Debian because they cannot provide the same

Bug#934055: motion: systemd unit file

Package: motion Version: 4.2.2-1 Severity: wishlist Tags: patch Hi, Thanks for packaging 4.2.2! I noticed that this package doesn't have a systemd unit file. I saw that there was a basic one upstream, but it lacked some features. I've submitted this upstream bug, but as you may know upstream

Bug#928710: drkonqi: segfault after using reload button to get backtrace for dolphin

Package: drkonqi Version: 5.14.5-1 Severity: normal dolphin crashed, and I didn't have sufficient debug sym installed. I installed them, and then hit the "reload" button to re-do the backtrace, at which point drkonqi crashed. Backtrace below: Application: drkonqi (drkonqi), signal:

Bug#907039: avahi-daemon: Host name conflict on startup (race condition?).

Package: avahi-daemon Version: 0.7-4 Severity: normal Dear Maintainer, On boot-up I sometimes see avahi-daemon reporting a hostname conflict. The system uses network-manager and has a single Ethernet interface which is configured as a bridge (to allow virtualisation on this workstation). Logs

Bug#810735: fatresize: fails to open /dev/mmcblk0p1

Package: fatresize Version: 1.0.2-9 Followup-For: Bug #810735 This patch works for me, please could we get it into buster? Regards, Tim. -- System Information: Debian Release: 9.4 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64)

Bug#890501: prometheus startup fails due to racey PID file implementation in prometheus

Package: prometheus Version: 2.1.0+ds-1+b1 Severity: important Tags: upstream Due to https://github.com/prometheus/prometheus/issues/2689 Prometheus may fail to start (most commonly after a reboot), since the lock file checking implementation it uses is naive (just "is there a pid running with

Bug#864720: glibc: Upgrade to stretch warns about 2.6.32 kernel on i386/amd64 - inconsistent with upstream release notes

Source: glibc Version: 2.24-11 Severity: normal The upstream release notes state: "The minimum Linux kernel version that this version of the GNU C Library can be used with is 3.2, except on i[4567]86 and x86_64, where Linux kernel version 2.6.32 or later suffices (on architectures that already

Bug#864339: network-manager: README.Debian contains references to older version, various other minor issues.

Package: network-manager Version: 1.6.2-3 Severity: normal Tags: patch The README.Debian file contains outdated references to the 0.9 version, and documentation. Also updated to expand reference to the command line tools, since nmtui has been expanded. Fix other minor grammar bits too. --

Bug#862007: prometheus-alertmanager: Fails to start on machines without a MAC address

Source: prometheus-alertmanager Version: 0.5.1+ds-7+b2 Severity: normal Due to upstream bug https://github.com/prometheus/alertmanager/issues/582 It's not possible to start alertmanager on machines with no MAC address. e.g. machines with non-broadcast network interfaces such as those with

Bug#861097: tayga: DNS64 availability in Debian not mentioned

Package: tayga Version: 0.9.2-6+b1 Severity: normal A documentation bug, but since DNS64 is necessesary for most deployments of tayga, it might be useful to mention somewhere what software exists in Debian which can be used to provide DNS64? AFAIK, this is only bind9 currently? Maybe this could

Bug#856856: Upstream bug report https://github.com/cobbler/cobbler/issues/1717

Upstream bug report https://github.com/cobbler/cobbler/issues/1717

Bug#856856: cobbler-web: Doesn't run out of the box with Django 1.10

Package: cobbler-web Version: 2.6.6+dfsg1-13 Severity: important The cobbler-web package appears to assume an earlier django version and breaks on version 1.10 which is currently in Stretch. 500 Server error. I've made the following changes in an effort to workaround, but given up as didn't

Bug#855145: prometheus: Console templates don't work out of the box

Package: prometheus Version: 1.5.0+ds-1 Severity: normal The sample consoles are missing when the debian package is installed, giving users a system with reduced functionality and usability. Nothing in the UI gives any indication that they are missing, or that they must be manually restored (or

Bug#845253: icedove: Contrast ratio reduced in message list and folder panes.

Package: icedove Version: 1:45.5.0-1 Followup-For: Bug #845253 Workaround for /chrome/userChrome.css: /* Make folder pane and message pane text dark grey or black */ treechildren { color: #1f1c1b; /* color: black; */ }

Bug#845253: icedove: Contrast ratio reduced in message list and folder panes.

Package: icedove Version: 1:45.5.0-1 Severity: normal The text in the folder view and email list view has changed from dark grey (RGB #1f1c1b) to a lighter grey (RGB #31363b) (checked on a different machine running 45.4.0) with the latest version of Icedove. This represents a change in contrast

Bug#636871: provide a command-line switch to prefer IPv6 or IPv4

Package: apt Followup-For: Bug #636871 There are already system-wide mechanisms to change the default stack which is used (/etc/gai.conf), and apt has: -o Acquire::ForceIPv4 and -o Acquire::ForceIPv6 (see "man apt.conf" and #611891). What might be better (and would be a useful addition)

Bug#844707: plasma-workspace: plasmadesktop - excessive cpu usage, slow desktop operation

Package: plasma-workspace Version: 4:5.8.2-1 Severity: important plasmashell consumes excessive CPU, increases over time. Possibly I'm hitting a couple of bugs here, but I'm not sure... plasmashell starts by stat()ing about 4 files per second, and consuming 50% of one CPU core. CPU then

Bug#841415: mopidy: default local config includes data_dir entry

Package: mopidy Version: 2.0.1-1 Severity: normal The package ships with a default config which includes: [local] data_dir = /var/lib/mopidy/local and also creates a corresponding directory. However the data_dir config entry is marked "Deprecated" in

Bug#840735: haproxy: Default SSL cipher list quotes external source, but is out of date

Source: haproxy Version: 1.6.9-2 Severity: normal The default haproxy.cfg include tls cipher and protocol restrictions. They cite an external source: https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/ This has now been updated, so the shipping cfg file should probably be updated

Bug#839893: btrfs-progs: mkfs.btrfs fails to show UUID after filesystem creation

Package: btrfs-progs Version: 4.7.3-1 Severity: normal The filesystem UUID insn't shown following creation of a new filesystem: root@lxdtest2:~# mkfs.btrfs /dev/vdb1 btrfs-progs v4.7.3 See http://btrfs.wiki.kernel.org for more information. Label: (null) UUID: Node

Bug#837880: vim: Unable to globally disable mouse

Package: vim Version: 2:8.0.0003-1+b1 Followup-For: Bug #837880 mouse=a is now unconditionally set in /usr/share/vim/vim80/defaults.vim As this is sourced after /etc/vim/vimrc this takes precedent. Would be good if this could be fixed (i.e. to honour /etc/vim/vimrc), but I'm not really sure

Bug#834724: curl: (35) gnutls_handshake() failed: Public key signature verification has failed.

Package: curl Followup-For: Bug #834724 I fixed this on a sid install by removing libgnutls-deb0-28 which was being kept around by an old librtmp1 package version, left over from Jessie debian-multimedia. Possibly libcurl should conflict with this package? -- System Information: Debian Release:

Bug#834724: curl: (35) gnutls_handshake() failed: Public key signature verification has failed.

Package: curl Version: 7.50.1-1 Followup-For: Bug #834724 I'm seeing all https accesses failing with curl. Connecting to the same sites with gnutls-cli works OK. tim@ermintrude:~$ curl-config --ca /etc/ssl/certs/ca-certificates.crt tim@ermintrude:~$ curl -V curl 7.50.1 (x86_64-pc-linux-gnu)

Bug#741047: [x11vnc] Treats all Xerrors as fatal, occassionally dies during Xerror on initial connection

Package: x11vnc Version: 0.9.13-1.2+b4 Followup-For: Bug #741047 In my setup (2x 4k monitors, Intel Skylake integrated graphics), x11vnc lasts about 30 seconds on average before exiting with errors like: caught XIO error: deleted 240 tile_row polling images Tim. -- System Information: Debian

Bug#829083: linux-image-4.6.0-1-amd64: [drm:haswell_crtc_disable [i915]] *ERROR* failed to update payload -22, then WARN_ON(!wm_changed) when turning off external monitor

Package: src:linux Version: 4.6.2-2 Severity: normal The errors and warnings below occur when an external displayport monitor is turned off (connected to Intel Skylake integrated graphics). -- Package-specific info: ** Version: Linux version 4.6.0-1-amd64 (debian-ker...@lists.debian.org) (gcc

Bug#829075: plasma-workspace: plasmashell crashes - debug symbols not available in unstable apparently?

Package: plasma-workspace Version: 4:5.6.5.1-1 Severity: normal KDE bug tracker reports debug symbols unavailable for plasmashell, even though the debug symbol package with a matching version number is installed. ii plasma-workspace 4:5.6.5.1-1 amd64Plasma Workspace for KF5 ii

Bug#801247: pinentry-gnome3: No PIN dialog

Package: pinentry-gnome3 Followup-For: Bug #801247 In my case, it looks like: gpg-agent is started, and inherits the DBUS_SESSION_BUS_ADDRESS env varible. The gpg-agent persists across login sessions, so that when it starts the gnome3 pinentry the dbus session doesn't correspond with the

Bug#827224: targetcli: On upgrade "Value of wwn attribute is not set for"

On 14/06/16 16:08, Ritesh Raj Sarraf wrote: > Control: tag -1 moreinfo > > Hello Tim, > > We never had a version released for Debian Jessie. There were just too many > issues back then. For Stretch, I hope we have the current ones in the > repository. > > Assuming you have interest in LIO, I'd

Bug#787241: xserver-xorg-video-intel: VT never returns from powersave on Haswell

Package: xserver-xorg-video-intel Followup-For: Bug #787241 Could you try: . Switch to VT . Log in as same use as X session on VT . run 'sleep 6 ; DISPLAY=:0 xrandr' on VT . switch to X VT before 6 seconds have elapsed, then switch back after 6 seconds have elapsed . Check output to see what

Bug#827224: targetcli: On upgrade "Value of wwn attribute is not set for"

Package: targetcli Version: 1:3.0~pre4.1~ga55d018-2 Severity: important Following upgrade from Jessie to Stretch with a pre-existing, working live config (created under Jessie): list(config.apply()) File "/usr/lib/python2.7/dist-packages/rtslib/config.py", line 717, in apply

Bug#802586: gnupg2: Fails to sign using smartcard after upgrade

Package: gnupg-agent Version: 2.1.11-7 Followup-For: Bug #802586 Identical behaviour with recent upgrade from Jessie to testing using an OpenPGP compatible card with 4096 bit keys, including ssh-auth working fine... -- System Information: Debian Release: stretch/sid APT prefers testing APT

Bug#813468: boinc-client: Some https connections fail due to Debian Jessie openssl and ca-certificate interactions

The latest Debian point release should have fixed this with an update to OpenSSL: openssl (1.0.1t-1+deb8u1) jessie; urgency=medium [...] - Use alternate trust chains part of 1.0.1n (Closes: #774882). [...] -- Kurt Roeckx Fri, 06 May 2016 15:56:09 +0200 -- South East

Bug#822795: liblockfile-bin: dotlogfile -r -1 doesn't work - gives up immediately

Package: liblockfile-bin Version: 1.09-6 Severity: normal Tags: patch dotlockfile -r -1 doesn't work on x86_64 (haven't tried other archs) - instead of retrying indefinitely, it never retries (behaves like "-r 0"). This seems to be due to an integer overflow, since: int

Bug#779628: bcache: task bcache_writebac blocked for more than 240 seconds, system load high when module used

On 05/02/16 23:14, Ben Hutchings wrote: >> https://lkml.org/lkml/2015/12/30/331 >> >> It would be good to get this set into Stretch, and possibly a Jessie >> point release too (IIRC, it will apply cleanly to the Jessie kernel). > That whole patch series was included in 4.3.3-6, but I have yet

Bug#779628: bcache: task bcache_writebac blocked for more than 240 seconds, system load high when module used

Package: src:linux Version: 3.16.7-ckt20-1+deb8u3 Followup-For: Bug #779628 I think this patch fixes this issue: https://github.com/torvalds/linux/commit/627ccd20b4ad3ba836472468208e2ac4dfadbf03 It's included in this set which got merged in the 4.5 window. See this thread:

Bug#812488: libsms-send-perl: After upgrade: Can't send SMS: 500 Can't connect to api.twilio.com:443 (certificate verify failed)

Package: ca-certificates Followup-For: Bug #812488 #813468 is similar but impacting a different application. I did come across a patch which backports the fix included in newer versions of the upstream OpenSSL 1.0.1 branch, to the 1.0.1k derived package in Jessie. I haven't reviewed or tested

Bug#813468: boinc-client: Some https connections fail due to Debian Jessie openssl and ca-certificate interactions

Package: openssl Version: 1.0.1k-3+deb8u2 Followup-For: Bug #813468 > On Tue, Feb 02, 2016 at 19:14:24 +0100, Kurt Roeckx wrote: > > On Tue, Feb 02, 2016 at 03:04:41PM +0100, Christian Beer wrote: > > Since it works in openssl 1.0.2 you can either upgrade the package in > > Jessie to 1.0.2 (which

Bug#813468: boinc-client: Some https connections fail due to Debian Jessie openssl and ca-certificate interactions

Package: boinc-client Version: 7.4.23+dfsg-1 Severity: normal Connections by boinc to upload work data to https://cleanenergy.worldcommunitygrid.org/ are failing. This is due to a problem with the Jessie OpenSSL infrastructure. The server TLS/SSL certificate is signed like this: 1. cleanenergy

Bug#746712: Please update the loginuid patch to match upstream's current version

FWIW, I think it would be good to get this into a Jessie point release, as it currently makes running Jessie in lxc containers awkward (e.g. breaks cron etc.).

Bug#784823: Regression - mdadm in jessie will not boot degraded raid1 array

Package: mdadm Followup-For: Bug #784823 See also: http://serverfault.com/questions/688207/how-to-auto-start-degraded-software-raid1-under-debian-8-0-0-on-boot with workaround... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#754291: chromium: Recent Chromium builds readily exhaust Debian default 1024 open file soft ulimit

Package: chromium Version: 43.0.2357.65-1~deb8u1 Followup-For: Bug #754291 Nothing on the upstream bug for a year - is it worth just implementing the suggested workaround(s) in the meantime? -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (500, 'stable')

Bug#704467: ddclient: Add ipv6 support for dyndns (patch)

Package: ddclient Version: 3.8.2-2 Followup-For: Bug #704467 Would be good to get something like this merged, too late for Jessie I know. Also if might not be such a great idea as I assign my ppp ipv6 address to a different interface (so perhaps it could fall back to using any Scope:Global

Bug#780609: arduino: Leonardo fails to reset on Jessie (works on Wheezy)

Package: arduino Version: 2:1.0.5+dfsg2-4 Severity: normal I have a few Arudino Leonardos of varying vintages. One fails to reset on Jessie during the programming phase (but will reset successfully on Wheezy using Arduino 1.0.1). Pressing the reset button on the board manually makes programming

Bug#666499: Wrong frequency after suspend to ram

Package: cpufrequtils Version: 008-1 Followup-For: Bug #666499 I'm also seeing this on a Dell Studio XPS 8100 The first CPU gets the correct frequency settings on resume, but the others don't. On boot - set via /etc/default/cpufrequtils: ENABLE=true GOVERNOR=ondemand MAX_SPEED=2133000

Bug#769109: x2vnc accidentally trigger window hiding when pointer leaves the VNC screen on Windows 7

Package: x2vnc Version: 1.7.2-5 Severity: normal When the pointer leaves the VNC screen and returns to the controlling machine, x2vnc sets the point location to the extreme lower-right corner of the VNC screen, instead of the last pointer location before the pointer left the VNC screen. When the

Bug#768504: cdparanoia: Very poor read performance when running on two optical drives simultaneously

Package: cdparanoia Version: 3.10.2+debian-11 Severity: normal In a system with 2 SATA optical drives (have tried on two Jessie systems so-far), if two copies of cdparanoia are run simultaneously, and -d /dev/sr0 is specified on one copy, and -d /dev/sr1 on the other, then read performance drops

Bug#764582: cpufrequtils: -r flag for related CPUs broke on transition from 3.2 to 3.14 kernel

Apologies, change in behaviour wasn't 3.14 to 3.16, it was between 3.2 and 3.14. strace output of cpufreq-set from 3.16 (3.14 shows same behaviour): 8820 open(/sys/devices/system/cpu/cpu0/cpufreq/related_cpus, O_RDONLY) = 3 8820 read(3, 0\n, 4095) = 2 on 3.2: 2257

Bug#765075: qemu: non-upstream patch to copy ACPI SLIC oem_id into the RSDT table is undocumented.

Package: qemu Version: 2.1+dfsg-5 Severity: normal Tags: patch Debian is currently carrying a non-upstream patch to copy the ACPI SLIC oem_id into the RSDT table. Whilst useful, this altered behavious is currently undocumented. -- System Information: Debian Release: jessie/sid APT prefers

Bug#765080: libvirt-bin: USB Host Device passthrough broken on new minimal Jessie install

Package: libvirt-bin Version: 1.2.8-3 Severity: normal On a newly installed Jessie amd64 box, USB Host Device passthrough for qemu guests is broken due to qemu-system being unable to access the necessary /dev/bus/usb device files, e.g. 2014-10-09T20:46:52.077038Z qemu-system-x86_64: Warning:

Bug#765080: libvirt-bin: Fixed in 1.2.9-2 (via policykit ?).

Package: libvirt-bin Followup-For: Bug #765080 Tried the workaround detailed in #764811, but that didn't work. Have manually upgraded the Jessie system to the packages from sid (1.2.9-2), and now working OK - the device files now get their ownership correctly set: crw-rw-r-- 1 libvirt-qemu

Bug#765075: qemu: non-upstream patch to copy ACPI SLIC oem_id into the RSDT table is undocumented.

Package: qemu Version: 2.1+dfsg-5 Followup-For: Bug #765075 On 13/10/14 16:28, Michael Tokarev wrote: So, what do you suggest to do? I attached a simple patch to the original bug report when I filed it, which added a note to the docs (ends up in --help output and man page too I think).

Bug#764582: cpufrequtils: -r flag for related CPUs broke on transition from 3.14 to 3.16 kernel

Package: cpufrequtils Version: 008-1 Severity: normal Hi, On 3.14 with Jessie this worked: cpufreq-set -g ondemand --max 2.1GHz -r since upgrading to 3.16 (it's possible that another upgrade installed at the same time impacted this), these CPUs are no longer related. i.e. this call only

Bug#764339: targetcli: install with --no-install-recommends fails on implicit python-prettytable dependancy

Package: targetcli Version: 3.0+git0.7e32595e-2 Severity: important Installing target with --no-install-recommends results in: targetcli Traceback (most recent call last): File /usr/bin/targetcli, line 23, in module from targetcli import UIRoot File

Bug#764340: targetcli: On new install exit or configure etc. fail due to missing /var/target/policy

Package: targetcli Version: 3.0+git0.7e32595e-2 Severity: important On a new install, on Jessie: root@ermintrude:/home/tim/Downloads# targetcli targetcli GIT_VERSION (rtslib GIT_VERSION) Copyright (c) 2011-2014 by Datera, Inc. All rights reserved. /backstores/iblock/win7 exit Traceback (most

Bug#764354: targetcli: Fails to save even an empty configuration

Package: targetcli Version: 3.0+git0.7e32595e-2 Severity: normal On fresh install with no configuration at all: root@ermintrude:/home/tim# targetcli targetcli GIT_VERSION (rtslib GIT_VERSION) Copyright (c) 2011-2014 by Datera, Inc. All rights reserved. / saveconfig WARNING: Saving ermintrude

Bug#764355: targetcli: Fails to load or save any config on Jessie

Package: targetcli Version: 3.0+git0.7e32595e-2 Severity: grave Justification: renders package unusable Having tried on two systems (one fresh install netboot system), and I really can't get this package to do anything at all: . Give useless error message if kernel modules aren't loaded: This

Bug#764339: targetcli: install with --no-install-recommends fails on implicit python-prettytable dependancy

Package: targetcli Version: 3.0+git0.7e32595e-2 Followup-For: Bug #764339 python-pyparsing is also a missing dependancy. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux

Bug#764358: targetcli: Starting the target service loads QLogic Fibre Channel HBA Driver

Package: targetcli Version: 3.0+git0.7e32595e-2 Severity: normal Starting the target service causes the QLogic Fibre Channel HBA Driver (qla2xxx) to be unconditionally loaded on machines which lack this hardware. Same for the rest of the fibrechannel kernel modules e.g. libfc. -- System

Bug#754291: chromium: Recent Chromium builds readily exhaust Debian default 1024 open file soft ulimit

Package: chromium Version: 35.0.1916.153-2 Severity: normal Tags: upstream patch upstream bug: https://code.google.com/p/chromium/issues/detail?id=137875 It's reasonably easy for the chromium parent process to hit the maximum open files limit which defaults to 1024 open files per process on

Bug#745611: libkscreensaver5: Can't unlock screen with locker set to 'Desktop Widgets', and multiple monitors configured

Package: libkscreensaver5 Version: 4:4.11.8-1 Severity: important The Unlock popup fails to display when screen locker is set to 'Desktop Widgets', and multiple monitors configured - leaving desktop irrevocably locked. With the second display disabled, the unlock widget appears. With the second

Bug#745560: wide-dhcpv6-client: service wide-dhcpv6-client restart doesn't wait for old process to stop.

Package: wide-dhcpv6-client Version: 20080615-11.1 Severity: normal Tags: patch ipv6 The init script 'stop' function doesn't wait for the old process to exit, but just sends SIGTERM and walks away... This means that 'restart' fails if the old process doesn't exit quickly enough. The attached

Bug#721877: automysqlbackup: Causes warnings and hence cron job mails once a month since Wheezy

Package: automysqlbackup Version: 2.6+debian.3-1 Followup-For: Bug #721877 We have the same problem with automysqlbackup on wheezy. If the previous patch is not deemed to be satisfactory, then a mechanism for inserting additional arbitary arguments to mysqldump would be handy - e.g. by adding an

Bug#721877: mysqldump config file setting correction

Sorry - that should be: events= true added to a: [mysqldump] section in /etc/mysql/debian.cnf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#736511: installation-reports: Impossible to set domain name via preseeding or dhcp with netinstall

Package: installation-reports Severity: normal -- Package-specific info: Boot method: network Image version: http://ftp.nl.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/netboot/netboot.tar.gz 13661649 Dec 12 2013 06:18 netboot.tar.gz Date: Date and time of the install

Bug#636134: is this fixed upstream or not?

Hi, Unfortunately I don't currently have access to a system with large numbers of drives to test against, and personal circumstances mean that I'm unlikely to have time to work on this further during the next 6 months or so, although hopefully I'll be able to get on to it at some point. I'll

Bug#702876: linux-image-2.6.32-5-openvz-amd64: OpenVZ 'vzctl start VEID --wait' hangs.

Package: linux-image-2.6.32-5-openvz-amd64 Version: 2.6.32-48squeeze1 Severity: normal Tags: When using the squeeze openvz kernel, the --wait feature of 'vzctl' seems to wait forever. Broken with: + Squeeze hardware node + Squeeze guests + vzctl 3.0.24 and also 3.0.30 + kernel

Bug#701913: cluster-agents: /usr/lib/ocf/resource.d/heartbeat/SendArp starts send_arp once, doesn't monitor.

Package: cluster-agents Version: 1:1.0.3-3.1 Severity: normal The behaviour of /usr/lib/ocf/resource.d/heartbeat/SendArp is such that when the $ARP_BACKGROUND option is given, the return code of the send_arp binary is never checked on start. The monitor option unconditionally returns

Bug#701914: cluster-agents: send_arp leaks socket fds, dies when all FDs consumed.

Package: cluster-agents Version: 1:1.0.3-3.1 Severity: normal send_arp consumes all available FDs (one per packet sent), and then exits. e.g. stracing: /usr/lib/heartbeat/send_arp -i 20 -r 512 -p /var/run/heartbeat/rsctmp/send_arp-192.168.42.189-eth1 eth1 192.168.42.189 auto 192.168.42.189

Bug#701913: /usr/lib/ocf/resource.d/heartbeat/SendArp starts send_arp once, doesn't monitor.

Package: cluster-agents Severity: normal Tags: patch Ommited to actually include the attachment. #!/bin/sh # # Copyright (c) 2013, Tim Small t...@seoss.co.uk # Cleanup monitor action, add initial burst behaviour. # # Copyright (c) 2006, Huang Zhen zhen.hu...@gmail.com # Converting original

Bug#701914: send_arp leaks socket fds, dies when all FDs consumed.

Package: cluster-agents Severity: normal Tags: patch Attached patch is an easy fix for this. Possibly the other proposed fix would be better tho? -- System Information: Debian Release: 6.0.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux

Bug#655385: [squeeze openvz] Cannot allocate memory when doing cat, /proc/self/mountinfo inside a vm

Hmm, I just re-read http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#deprecated and it says Debian GNU/Linux 6.0 will be the last release to include Linux kernel virtualization featuresets outside of mainline. This means that the OpenVZ and Linux-Vserver featuresets

Bug#584881: Lockups under heavy disk IO; md (RAID) resync/check implicated

FWIW, I was only able to reproduce the problem which I was seeing on lenny+openvz (running the same workload on lenny+chroot, or squeeze+openvz didn't trigger it). The fix you attached does sound like a plausible fix for the issue I was seeing (having spent a day or two peering at the code and

Bug#636463: vzctl: /etc/vz/dists/scripts/postcreate.sh randomises run-times in /etc/crontab, but not cron.d

cc'ing openvz users mailing list, as this has been discussed there recently. On 04/08/11 06:36, Ola Lundqvist wrote: This is certainly an interesting problem. The patch is a good start but as we can foresee problems already now we need to find out a solution to that before it is applied.

Bug#636463: vzctl: /etc/vz/dists/scripts/postcreate.sh randomises run-times in /etc/crontab, but not cron.d

Package: vzctl Version: 3.0.24-12 Severity: normal Tags: patch I sent this a few months ago, but it seems to have been eaten by a faulty MTA setup :-(. With multiple Debian VEs installed on a host, load spikes occur corresponding with cron job execution. On investigation, it appeared that

Bug#636474: ifupdown-extra: network-test chokes when VLANs are configured

Package: ifupdown-extra Version: 0.14 Severity: normal INFO: The eth0.5@eth0 interface is up Device eth0.5@eth0 does not exist. WARN: The eth0.5@eth0 interface does not have an IP address assigned eth0.5@eth0: error fetching interface information: Device not found eth0.5@eth0: error fetching

Bug#636134: munin-node: Various flaws in hddtemp_smartctl - timeouts, dev name persistance etc.

Package: munin-node Version: 1.4.5-3 Severity: normal Tags: patch hddtemp_smartctl has numerous bugs and annoymances e.g.: . Fails to collect anything on systems with large numbers of drives due to timeouts. . Fails to collect anything on systems with one or more faulty or slow drives due to

Bug#503268: Another occurrence on lenny

A little info to add. Again, similar messages, and the program which is getting the error isn't giving anything away as to it's identity: date10 July 2011 06:25 subject Cron root@xeon1 test -x /usr/sbin/anacron || ( cd / run-parts --report /etc/cron.daily ) /dev/dm-1: stat failed: No such

Bug#604469: Update check

On 20/06/11 06:19, Ola Lundqvist wrote: I would like you to check if the issue you reported in 604469 is solved in the squeeze release. Well, I can't say for certain, but I couldn't reproduce the issue using the squeeze kernel. Tim. -- South East Open Source Solutions Limited Registered

Bug#619496: arno-iptables-firewall: interface wildcard expansion in traffic-shaper plugin fails when sh isn't bash

Package: arno-iptables-firewall Version: 1.9.2.k-4 Severity: normal Network interface wildcard expansion (e.g. ppp+ etc.) in traffic-shaper plugin fails when /bin/sh is /bin/dash. Things work again if /bin/bash is substituted. Also ref:

Bug#609368: duplicity: Test for time moving forward fails because it seems to use an unchanging time from a file

Package: duplicity Version: 0.6.08b-1+b1 Severity: important I believe I had a connectivity problem which interrupted a transfer, and since then duplicity has failed on every run saying: time not moving forward at appropriate pace - system clock issues? - which was the result of a failed

  1   2   3   >