Bug#1029704: v2.2.7 from pypi works

Uninstalling python3-pymssql and installing https://files.pythonhosted.org/packages/60/53/66a17b63555d2f6bd8734defcd017f762c5b427e4b56958eae4ad897dd74/pymssql-2.2.7-cp39-cp39-manylinux_2_24_x86_64.whl instead fixes the problem.

Bug#1029704: Test result with docker images

Testing against docker images gives the same error. Tested: python:3.9.1-slim-bullseye python:3.10.9-slim-bullseye python:3.11.1-slim-bullseye

Bug#1029704: connect() fails with malloc(): unsorted double linked list corrupted

Package: python3-pymssql Version: 2.1.4+dfsg-3+b3 When re-connecting to an MSSQL server after a connection error, the program will stop with "malloc(): unsorted double linked list corrupted" This can be reproduced on Debian 11.6 (amd64) with latest dist-upgrade applied using the following pr

Bug#1012115: Sasl local login fails when selinux enforced

Package: sasl2-bin Version: 2.1.27+dfsg-2.1+deb11u1 I have a Cyrus Murder which was installed on Buster. SASL mechanism is set to PAM, with nsswitch configured "passwd: files systemd ldap". The system is SELinux enabled. After dist-upgrading to Bullseye, we had intermittent login problems, wh

Bug#970865: openssh 8.3 in buster-backports

Package: openssh-client Version: 1:7.9p1-10+deb10u2 I'd like to see openssh client+server with Version 8.3 in buster-backports, because I'd like to use the new FIDO2-U2F security key support which was introduced upstream in 8.2. Regards, Andreas

Bug#954935: winbind crashes when queried for user

Package: winbind Version: 2:4.9.5+dfsg-5+deb10u1 I have Samba running with LDAP backend. Machine was installed freshly with latest Buster, config copied and adapted from an old installation. When running wbinfo -g, groups are listed as expected. When running wbinfo -u, the winbind process crashes

Bug#689605: still xvd?

First off, I moved away from pygrub a long time ago since I had some problems (IIRC with multiple domU starts at the same time). I've been using pvgrub and now grub-xen, I'm not suffering from this problem any more. The pygrub block device is very short-lived, so you probably just missed its appea

Bug#689605: xen still using xvd?

Xen still uses xvd? device names.

Bug#890614: delete .ICEauthority

I was able to resolve the problem by deleting /var/lib/gdm3/.ICE* and restart gdm3.

Bug#890614: gdm3 not working with 4.9.0-6

Today, my machines (stretch) got the same problem gnome-session-binary[1201]: WARNING: IceLockAuthFile failed: File exists. Apparently the problem is invented by linux-image-4.9.0-6 which was automatically installed yesterday. Reverted to 4.9.0-5, problem is gone.

Bug#884622: Also corruption on shutdown/start

Control: severity -1 critical I just triggered a fs corruption by shutting down a VM and starting it on another host, to avoid migration. I don't have indication that the DRBD that provides the shared storage in this installation may have caused this, so I'm still suspecting a kernel problem with

Bug#884622: Migrating VM with kernel 3.16 between xen hosts results in fs corruption / data loss

Package: linux-image-3.16.0-4 Version: 3.16.43-2+deb8u5 Severity: critical In the past weeks, I'm experiencing data loss (screwed up file systems; ext4/xfs/zfs affected) when migrating Stretch DomU Xen virtual machines from one Xen host to another. This happens on solid long-time stable Xen hos

Bug#866511: kernel BUG at nvme/host/pci.c

After discussing the issue on linux-nvme, the bug was located in xen/biomerge.c. It can be fixed in 4.9.30 as well as 4.13RC1 using the patch from Roger Pau Monne below. --- drivers/xen/biomerge.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/xen/biomerge.c b/drive

Bug#868747: rpc.statd not running after upgrade

Package: nfs-common Version: 1.3.4-2.1 After dist-upgrading from Jessie to Stretch, I got "lockd: cannot monitor ". I found that rpc.statd was not running because it wasn't enabled for autostart. After enabling and starting rpc.statd, machine resumed normal operation.

Bug#866511: kernel BUG at nvme/host/pci.c

Bug reported upstream as https://bugzilla.kernel.org/show_bug.cgi?id=196315

Bug#866511: kernel BUG at nvme/host/pci.c

Am 05.07.17 um 19:31 schrieb Ben Hutchings: > Control: reassign -1 src:linux 4.9.30-2+deb9u2 > Control: tag -1 upstream patch moreinfo > > On Thu, 2017-06-29 at 19:30 +0200, Andreas Pflug wrote: >> Package: linux-image-4.9.0-3-amd64 >> >> Version: 4.9.30-2+deb9u2

Bug#866511: kernel BUG at nvme/host/pci.c

Package: linux-image-4.9.0-3-amd64 Version: 4.9.30-2+deb9u2 When starting an ancient Windows Server 2003 virtual machine on a fully updated stretch host, the host will crash repeatably about 10 seconds after start. Kernel logging was implemented over netconsole, so I could capture the kernel outp

Bug#813894: ClamAV installation is OUTDATED

Tried 0.99 from jessie-proposed-updates: works for me as expected. Regards Andreas

Bug#813894: ClamAV installation is OUTDATED

Package: clamav Version: 0.98.7+dfsg-0+deb8u1 Since Dec 1, freshclam will log: WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.98.7 Recommended version: 0.99 IMHO 0.99 should be backported or made available as security update.

Bug#810964: [Xen-devel] [BUG] EDAC infomation partially missing

Am 22.01.16 um 11:40 schrieb Jan Beulich: On 22.01.16 at 10:09, wrote: >> When booting with Xen 4.4.1: >> >> AMD64 EDAC driver v3.4.0 >> EDAC amd64: DRAM ECC enabled. >> EDAC amd64: NB MCE bank disabled, set MSR 0x017b[4] on node 0 to enable. > I wonder how valid his message is. We actual

Bug#810964: [Xen-devel] [BUG] EDAC infomation partially missing

Am 21.01.16 um 17:41 schrieb Jan Beulich: On 20.01.16 at 16:01, wrote: >> Initially reported to debian >> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810964), redirected here: >> >> With AMD Opteron 6xxx processors, half of the memory controllers are >> missing from /sys/devices/system/

Bug#810964: [BUG] EDAC infomation partially missing

Initially reported to debian (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810964), redirected here: With AMD Opteron 6xxx processors, half of the memory controllers are missing from /sys/devices/system/edac/mc Checked with single 6120 (dual memory controller) and twin 6344 (2x dual MC), other

Bug#810964: Same problem with Xen 4.6

Checked with xen-hypervisor-4.6-amd64 4.6.0-1 from sid: same result as with 4.4.1, only one of two memory controllers in /sys/devices/system/edac/mc

Bug#810964: only partial EDAC information with Xen

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u3 Debian 8.2 installed on a supermicro H8SGL Board, AMD 6128 with 4x4GB ECC RAM. When booting the plain kernel (stock Jessie 3.16 or backport 4.1 or 4.3), both memory controllers (mc0 and mc1) appear under /sys/devices/system/edac/mc with tw

Bug#797850: virsh cant specify disk device block-xxx script

Package: libvirt-clients Version: 1.2.9-9 Non-standard block devices may be used as disk for xen using /etc/xen/scripts/block-xxx scripts. In my case, I'm using a special lvm driver block-lvm With old xm configurations, it was possible to specify disk=["lvm:vg/lv,xvda1,w"] xl won't like this, b

Bug#796524: Fwd: [Bug 728] SMTP listener keeping log file open for days

Fixed upstream. Git Commit changed bug 728 WhatRemoved Added CC g...@exim.org *Comment # 16 on bug 728 from Git

Bug#796524: Exim4 has stale filehandle after logrotate

There was an old bug in the exim bugzilla that was closed-unresolved a while ago; I reopened it and added some information there. https://bugs.exim.org/show_bug.cgi?id=728

Bug#796524: Exim4 has stale filehandle after logrotate

Sorry for the glitch, searched for keyword logrotate... Actually, it IS documented that mainlog may stay open unused for a prolonged time (>2d). I don't think that's too sensible, keeping a possibly large file open when it's already zipped and deleted... Conclusion: Unexpected but documented exim4

Bug#796524: not specified

Actually, the file handling isn't specified in the spec.txt file. But since it "mostly works", without triggering a reload or other means of rotating logs, at least the debian package seems to assume the openLog-write-close cycle, and new log lines are correctly written to mainlog only, not mainlog

Bug#796524: Exim4 has stale filehandle after logrotate

Package: exim4-base Version: 4.84-8 After 2 executions of logrotate, lsof shows a mainlog.1 as deleted file. Apparently, exim4 keeps a logfile open although it will never write to it again. This appears as an exim4 bug to me, since exim4 is supposed to close all its logfiles after writing, but in

Bug#753295: libvirt 1.2.4: virsh dumpxml throws internal error

Package: libvirt-bin Version: 1.2.4-1 Running on a vanilla wheezy with default 3.2 kernel and xen4.1, dumping a running domain's config using "virsh dumpxml TheDomain" will throw the error "error: internal error: unexpected disk type 0" using libvirt-bin 1.2.4 from wheezy-backports. Reverting t

Bug#721443: drbd8-utils: drbd 8.4 tools needed for kernel 3.8+

Package: drbd8-utils Severity: important wheezy-backports linux-image-3.10 has drbd 8.4.3 included which won't work with wheezy's drbd8-utils 8.3. The tools compiled from sources work flawlessly. Please include them in wheezy-backports. -- System Information: Debian Release: 7.1 APT prefers s

Bug#715352: openvswitch bonding uses illegal port

Package: openvswitch-switch Version: 1.4.2+git20120612-2 Kernel 3.2.23-1~bpo60+2 An ovs installation configured for eth1+eth2 as bond0 with lacp active-backup sometimes switches from eth1 to eth0. eth0 isn't configured anywhere for ovs at all... Configuration is like this: # ovs-vsctl show Bridg

Bug#690517: corosync daemon vanishing

Package: corosync Version: 1.4.2-3 Severity: normal I'm running corosync with COROSYNC_DEFAULT_CONFIG_IFACE="openaisserviceenableexperimental:corosync_parser (as performed by aisexec) for clvm, with the these services: service { ver:0 name: openais_ckpt } quorum {

Bug#690099: python-configshell 1.1-3 is the problem

Actually, the problem seems to be python-configshell, which claims to be a library to create cli interfaces, but depends on python-epydoc which needs ghostscript, tex, graphviz et al. This results in >1GB of additional packages, quite a lot for a tiny cli tool. -- To UNSUBSCRIBE, email to deb

Bug#690099: targetcli depends on a zillion files

Package: targetcli Version: 2.0rc1-2 Severity: normal Installing targetcli from wheezy on a non-gui system will fetch a lot of gui-related libs, fonts, x11, tex, ... This is probably due to some unfortunate dependency of targetcli. -- System Information: Debian Release: 6.0.5 APT prefers stab

Bug#689605: multipath-tools: no default multipath.conf

Package: multipath-tools Version: 0.4.8+git0.761c66f-10 Severity: normal Since the multipath-tools package includes no standard multipath.conf, multipathd will grab any new block device. This can lead to surprising and hard debug effects. e.g. attaching a device in a XEN dom0 domain will render

Bug#686518: openvswitch-switch: No network configuration with openvswitch

Package: openvswitch-switch Version: 1.4.2+git20120612-2 Severity: normal Dear Maintainer, when replacing the kernel bridge module by openvswitch, the machines network configuration isn't executed because networking initialization is performed before the openvswitch daemons are running. I fixed

Bug#686517: initramfs-tools: module bridge loaded although blacklisted

Package: initramfs-tools Version: 0.99~bpo60+1 Severity: normal Dear Maintainer, in order to run openvswitch as bridge replacement, I tried to disable the kernel bridge module the usual way: I created a file /etc/modprobe.d/bridge.conf with the content "blacklist bridge" Then I ran update-initra

Bug#682979: sample logfile

This logfile was recorded while the vm-start was running. [20120727T14:43:34.919Z| info|vh10|1021 UNIX /var/lib/xcp/xapi|session.logout D:dd291648d150|xapi] Session.destroy trackid=e3179eeb95ba96c64ab771d0cb1557b6 [20120727T14:44:02.180Z|debug|vh10|25|Starting periodic scheduler D:641021a392d0|ba

Bug#682979: xcp-xapi: VM not starting, tasks not cancellable

Package: xcp-xapi Version: 1.3.2-9 Severity: grave Justification: renders package unusable I've following mostly the xcp-xapi/README.Debian instructions after installing it with apt-get -t wheezy network.conf is configured for bridge, xenbrN are functioning and shown with xe network-list A sing

Bug#671860: Disk freeze on 2.6.32 and 3.x kernels: blkback blocked for more than 120 seconds

I've been upgrading the machines to 3.2.0-0.bpo.2 (3.2.17), and rescheduled the checkarray to occur every weekend. So far, after two weekends, no more freeze occurrences. Previously, every 1-2 checkarray runs the machine used to stall. Seems the bug is fixed now. -- To UNSUBSCRIBE, email to d

Bug#671860: Disk freeze on 2.6.32 and 3.x kernels: blkback blocked for more than 120 seconds

Package: linux-image-3.2.0-0.bpo.1-amd64 Version: 3.2.1-2~bpo60+1 Severity: grave Actually, all kernels from 2.6.32 to (at least) 3.2.1 seem to be affected. I run two identical machines: Debian6 AMD64, raid1 software mirror for data disks, on /dev/mdx is lvm2 configured. The /dev/mapper devices a

Bug#637725: fixed

Apparently, the bug is fixed. The problem is gone in 3.2.1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#637725: Checked 3.0.4

checked with a vanilla 3.0.4 kernel (make oldconfig); Starting any domu fails with "hotplug script not working" for vif. The bridges the domu should connect to appear correctly created. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Troubl

Bug#637725: Acknowledgement (linux-image-3.0.0-1-amd64: Xen DomU restore fails with 3.0 kernel)

I tested with DomU kernels 2.6.32-5-34squeeze1 (debian stable) and a 2.6.21 x86 (endian 2.2). The Dom0 was tested with 2.6.32-5-35 and 3.0.0-1, i.e. the latest squeeze and wheezy kernels. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trou

Bug#637725: linux-image-3.0.0-1-amd64: Xen DomU restore fails with 3.0 kernel

Package: linux-image-3.0.0-1-amd64 Version: 3.0.0-1 Severity: normal On a Debian Stable host with recent backports, I added Xen 4.1 from recent Sid including all tools, and installed linux-image-3.0.0-1-amd64 and its dependencies. DomU save/restore and migration works both with Xen 4.0 and 4.1, b

Bug#630984: xen-utils-common: shutdown hangs with xenwatch and reboot being blocked

Package: xen-utils-common Version: 4.0.0-1 Severity: normal Tags: squeeze The host runs (at the time of testing) a single linux-x86 domu (128MB, 1VCPU). When issuing a reboot, everything looks as expected: - domu is saved - xend is stopped - drbd stopped - lvms unmounted - md0..4 stopped and th

Bug#613540: xen-utils-common: iptables rules missing for qemu tap interfaces

Package: xen-utils-common Version: 4.0.0-1 Severity: normal When a qemu hvm with vif=['type=ioemu,bridge=eth0'] is created, xen will successfully create the required vif and tap bridge interfaces, but will create the corresponding iptables filter rules for the vif interface only, not the tap in

Bug#611303: (no subject)

No wonder it's rarely used, if the button stays disabled... So maybe python-smbc should be made a requirement for gnome or the tasksel desktop package. With current defaults, SMB is perfectly supported in the desktop, except for printing. IIRC, in lenny the smb browsing was working out of the

Bug#611303: system-config-printer: SMB-Browser not working

Package: system-config-printer Version: 1.2.3-3 Severity: normal When adding an SMB printer, the SMB browser button is disabled unless python- smbc is installed. Currently, python-smbc is not required but merely proposed. IMHO this should be changed to "required". -- System Information: Debian

Bug#597462: splashy: Splash screen prevents gdm3 start

Package: splashy Severity: important This is probably the wrong package to blame, but I currently can't locate a better one. I've installed a Thinkpad freshly with Squeeze-AMD64 two weeks ago with GRUB2 and splashy, and dist-upgraded regularly. Hibernation worked fine, splashy's Tux went to sleep

Bug#523180: not ssl

Apparently the problem stems from strange behaviour of libnss-mdns. Seems it interacts although not configured in nsswitch.conf. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#523180: openssl: Some OpenVPNs conn not working with nm-applet after dist-upgrade

Package: openssl Version: 0.9.8g-15+lenny1 Severity: normal After an apt-get dist-upgrade of my Debian-5-amd64 system which updated the openssl libs, one specific OpenVPN connection won't connect any more using nm-applet 0.6.6 ("Could not connect to VPN server"), a second VPN conn still works ok

Bug#295880: Script to address both ttySx and CAPI modems

Package: capi4hylafax Version: 01.02.03_7 Severity: wishlist To support sending over analog modems and CAPI as well, I'd propose to configure SendFaxCmd as /usr/sbin/dofaxsend, with this script: #!/bin/sh case "$2" in tty*) /usr/sbin/faxsend $* *) /usr/bin/c2faxsend $* esac ex

Bug#295875: Empty TiffG4 fax sent

Package: capi4hylafax Version: 01.02.03-7 When tiffg4 compression is used, c2faxsend will send empty pages (only the header line is present). The very same converted file is transferred correctly using faxsend. tiff32d shows the same problem, tiff3 is ok, both gs-esp and gs-gpl tested. Versions u

Bug#293808: Capi4Hylafax resending despite success solved

I've been comparing faxsend's and c2faxsend's management of the queue file and found that the "returned" value needs to get updated, i.e. the fs.exitState needs to be written there (recoded to hylafax' needs). The attached patch against 01.02.03_7 sources corrects this. --- sendmain.cpp.org2005