Bug#1058029: qemu-guest-agent: QEMU-GA WON'T START

2023-12-11 Thread JP Pozzi
Hello, The script /etc/init.d/qemu-guest-agent was modified by me to look at the problem, it is not the original one. I use also a "home made" script to get clear informations through a dedicated logfile : #!/bin/bash METHOD='virtio-serial'

Bug#1057799: systemd: fails to configure

2023-12-09 Thread JP Pozzi
Hello, It is a "test" machine, so I install and uninstall many softs, this can lead to that result if something gous wrong. I correct that ... and will look in other machines to circumvent such a problem. Regards JP P - Mail original - De: "Michael Biebl" À: &

Bug#1057799: systemd: fails to configure

2023-12-08 Thread JP Pozzi
Hello, Here the result : grep users /etc/group /etc/gshadow /etc/group:users:x:100: /etc/gshadow:users:*::suricata To circumvent the problem ; 1) I save /etc/gshadow, drop the "offending" line and restart systemd --configure with success 2) Restore the saved gshadow file. Regards

Bug#1057799: systemd: fails to configure

2023-12-08 Thread JP Pozzi
Hello, Sorry I didn't see the second part, here is it : 1) SYSTEMD_LOG_LEVEL=debug # systemd-sysusers /usr/lib/sysusers.d/basic.conf result : nothing 2) cat /usr/lib/sysusers.d/basic.conf # generated from /usr/share/base-passwd/{passwd,group}.master g adm 4 - g tty 5 - g disk 6 - g man

Bug#1057799: systemd: fails to configure

2023-12-08 Thread JP Pozzi
Hello, Here the result : grep users /etc/group /etc/gshadow /etc/group:users:x:100: /etc/gshadow:users:*::suricata To circumvent the problem ; 1) I save /etc/gshadow, drop the "offending" line and restart systemd --configure with success 2) Restore the saved gshadow file. Regards JP P

Bug#1057799: systemd: fails to configure

2023-12-08 Thread JP Pozzi
Hello, Sorry I didn't see the second part, here is it : 1) SYSTEMD_LOG_LEVEL=debug # systemd-sysusers /usr/lib/sysusers.d/basic.conf result : nothing 2) cat /usr/lib/sysusers.d/basic.conf # generated from /usr/share/base-passwd/{passwd,group}.master g adm4 - g tty5 - g

Bug#720484: virt-manager does not start Error: No D-BUS daemon running

2013-08-22 Thread JP Pozzi
Package: virt-manager Version: 0.9.5-1 Severity: grave Justification: renders package unusable Dear Maintainer, Can't launch virt-manager without crash : virt-manager --no-fork --debug 2013-08-22 13:26:41,949 (cli:71): virt-manager startup 2013-08-22 13:26:41,949 (virt-manager:306): Launched

Bug#711273: xen-hypervisor-4.2-amd64: Acn't re-create domains after migration from 4.1 to 4.2

2013-06-05 Thread JP Pozzi
Package: xen-hypervisor-4.2-amd64 Version: 4.2.1-2 Severity: critical Tags: upstream Justification: breaks the whole system Dear Maintainer, After migration from Xen 4.1 to 4.2 all VMs have disapeared and I am unable to re-create my VM from the configfiles. When I try xm new com-web i get a

Bug#684722: w3af: Does not start : pybloomfiltermmap is a required dependency

2012-08-13 Thread JP Pozzi
Package: w3af Version: 1.1svn5547-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, When I launch w3af I get the following messages : Additional information: pybloomfiltermmap is a required dependency in *nix systems,in order to install it please

Bug#559175: linux-image-2.6.26-2-xen-amd64: That kernel hang on starting when used as domain-0

2009-12-02 Thread JP Pozzi
Package: linux-image-2.6.26-2-xen-amd64 Version: 2.6.26-19 Severity: grave Justification: renders package unusable Hello, I am trying Xen on an AMD905e (quad core) system, when I start the sstem Xen loads well but when the linux kernel try to boot it hangs after a very short time giving

Bug#407716: samba: Samba fails at start lidldap_r.so.2 not found

2007-01-20 Thread JP Pozzi
shares, print a document from Windows machines. Regards JP Pozzi -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.18 Locale: LANG=en_US, LC_CTYPE