Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

2018-03-19 Thread Jeff Ketchum
Second issue, I have trouble getting my system to boot reliably after the changes. It is using systemd:amd64 On Sun, Mar 18, 2018 at 5:28 PM, Michael Biebl wrote: > Am 15.03.2018 um 23:31 schrieb Jeff Ketchum: > > I upgraded systemd, and after a failure to boot, realized

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

2018-03-15 Thread Jeff Ketchum
t interface state: ready -> disabled Mar 15 17:00:38 jket-deb NetworkManager[794]: [1521154838.8324] device (wlp4s0): supplicant interface state: disabled -> inactive Mar 15 17:00:38 jket-deb wpa_supplicant[793]: wlp4s0: Reject scan trigger since one is already pending On Thu, Mar 15,

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

2018-03-15 Thread Jeff Ketchum
Package: systemd Version: 238-2 Severity: normal -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.15.0-1-amd64 (SMP w/8 CPU cores) Locale:

Bug#893041: libvirt update fails, dependencies

2018-03-15 Thread Jeff Ketchum
I am seeing the same issue from my upgrade. I don't think the entry for Server in the Socket section is the cause. ar 15 15:32:56 jket-deb systemd[1]: Reloading. Mar 15 15:32:56 jket-deb systemd[1]: /lib/systemd/system/virtlockd-admin.socket:7: Unknown lvalue 'Server' in section 'Socket' Mar 15 15

Bug#881219: test latest upstream

2017-11-22 Thread Jeff Ketchum
Hey Dann, It doesn't appear to have made a differnce, it still is failing. Thanks jeff On Wed, Nov 22, 2017 at 2:18 PM, dann frazier wrote: > hey Jeff, > Would you mind checking to see if this is fixed in latest upstream? > I've posted a build here: > > https://people.debian.org/~dannf/bug

Bug#881293: [Pkg-libvirt-maintainers] Bug#881293: libvirt-daemon: libvirtd sefgfault when disconnect and reconnect iso

2017-11-13 Thread Jeff Ketchum
python2.7/dist-packages/libvirt.py", line 2739, in updateDeviceFlags if ret == -1: raise libvirtError ('virDomainUpdateDeviceFlags() failed', dom=self) libvirtError: End of file while reading data: Input/output error On Fri, Nov 10, 2017 at 11:37 AM, Guido Günther wrote: > Hi, &g

Bug#881293: [Pkg-libvirt-maintainers] Bug#881293: libvirt-daemon: libvirtd sefgfault when disconnect and reconnect iso

2017-11-10 Thread Jeff Ketchum
wrote: > Hi, > On Thu, Nov 09, 2017 at 11:47:01AM -0700, Jeff Ketchum wrote: > > Package: libvirt-daemon > > Version: 3.9.0-1 > > Severity: important > > > > > > [ 271.168779] libvirtd[1177]: segfault at 10 ip 7f2cae6d9208 sp > 7f2cb80049a0 e

Bug#881293: libvirt-daemon: libvirtd sefgfault when disconnect and reconnect iso

2017-11-09 Thread Jeff Ketchum
Package: libvirt-daemon Version: 3.9.0-1 Severity: important [ 271.168779] libvirtd[1177]: segfault at 10 ip 7f2cae6d9208 sp 7f2cb80049a0 error 4 in libvirt_driver_qemu.so[7f2cae64d000+173000] -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500,

Bug#881219: ovmf: efi install of windows server 2012 r2 blue screen

2017-11-08 Thread Jeff Ketchum
installation process, then it gives a BSOD after formatting the disk and trying to copy files. Jeff On Wed, Nov 8, 2017 at 3:44 PM, dann frazier wrote: > On Wed, Nov 08, 2017 at 02:53:23PM -0700, Jeff Ketchum wrote: > > Package: ovmf > > Version: 0~20171027.76fd5a66-1 > >

Bug#881219: ovmf: efi install of windows server 2012 r2 blue screen

2017-11-08 Thread Jeff Ketchum
Package: ovmf Version: 0~20171027.76fd5a66-1 Severity: important Issue is not present in previous version of package: 0~20161202.7bbe0b3e-1 Booting windows 2012 r2 and installing causes BSOD and reboot issues with qemu/kvm virt-manager. -- System Information: Debian Release: buster/sid APT pr