Bug#997073: apt-cacher-ng: current version stopped working for client (initial error: confusing proxy mode or prohibited port)

2023-01-05 Thread Bob Weber
On 1/5/23 18:29, Pierre-Elliott Bécue wrote: Hi Eduard, Pierre-Elliott Bécue wrote on 27/10/2021 at 20:52:10+0100: [[PGP Signed Part:Signature made by expired key 29BFA0D079290ACA Pierre-Elliott Bécue]] Same issue here: Err :1http://HTTPS///deb.debian.org/debian unstable InRelease 403

Bug#1010026: qemu-system-x86: fails to start VM with "host" cpu missing features

2022-05-27 Thread Bob Weber
I have this same problem when I upgraded a testing system on May 24. I also installed: linux-image-5.17.0-2-amd64 from unstable This is the error from a (all) VM: vm: error: failed to set MSR 0xc104 to 0x1 kvm: ../../target/i386/kvm/kvm.c:2996: kvm_buf_set_msrs: Assertion `ret ==

Bug#939768: gimp: After the last upgrade, GIMP crashes when creating a new image or opening an existing one.

2019-09-12 Thread Bob Weber
I tried upgrading gegl, libgegl-0.4-0, and libgegl-common to : gegl (0.4.14-1+b2) libspiro1 (1:20190731-1+b1)<== brought in by upgrading gegl libgegl-0.4-0 (0.4.12-2 => 0.4.14-1+b2) libgegl-common (0.4.12-2 => 0.4.14-1) I run testing but also have unstable pined to a lower priorty than tes

Bug#907262: [plasma-workspace] Cannot load tray icons and Vault

2018-08-26 Thread Bob Weber
I also found this problem with plasma-workspace 5.13.4-1. After upgrading I had no system tray and right clicking the Launcher Button or anything on the Panel (to get a configuration options) does not work. I backed out of the upgrade and installed small groups of programs/libs until the fault

Bug#907262: [plasma-workspace] Cannot load tray icons and Vault

2018-08-26 Thread Bob Weber
I also found this problem with plasma-workspace 5.13.4-1. After upgrading I had no system tray and right clicking the Launcher Button or anything on the Panel (to get a configuration options) does not work. I backed out of the upgrade and installed small groups of programs/libs until the fault

Bug#748703: Any Progress

2014-06-05 Thread Bob Weber
Any thoughts on what has caused this? There must have been major changes to libvirtd from 1.2.1-1 to 1.2.4-3 for this bug to appear. Its apparent that libvirtd forgets the full path when it tries to access the backing file. The image file was created with the following qemu-img command: qemu-im

Bug#748703: Pool file XML

2014-05-20 Thread Bob Weber
The pool storage file: was produced by Virtual Machine Manager 0.9.5. Debian-7.4 47fc31a1-eb1f-9c9f-ebbd-75b770b2098b 0 0 0 /home/img/MyMachines/Debian-7.4 0755 -1 -1 - However when I look at the pool with virsh pool-edit

Bug#748703: libvirt-bin: libvirtd version 1.2.4-3 cannot probe backing volume format

2014-05-19 Thread Bob Weber
Package: libvirt-bin Version: 1.2.4-3 Severity: grave Justification: renders package unusable After upgrading to 1.2.4-3 libvirtd reports: kern.log.1:May 17 19:20:06 bob libvirtd[11315]: internal error: cannot probe backing volume format: Debian-7.4-base.img This happens for every VM that I ha

Bug#698243: gnucash: Fails to open data file from version 1:2.4.10-5

2013-01-16 Thread Bob Weber
consider this bug closed. Thank you for your help. I apologize for the noise. *...Bob* On 01/15/2013 04:48 PM, Sébastien Villemot wrote: Control: tags -1 + moreinfo Le mardi 15 janvier 2013 à 16:20 -0500, Bob Weber a écrit : Package: gnucash Version: 1:2.4.10-6 Severity: critical Tags

Bug#698243: gnucash: Fails to open data file from version 1:2.4.10-5

2013-01-15 Thread Bob Weber
Package: gnucash Version: 1:2.4.10-6 Severity: critical Tags: upstream Justification: causes serious data loss Upon openeing gnucash there is an error "parsing" input file. This happened after a upgrade to 1:2.4.10-6. I have downgraded to version 1:2.4.10-5 to get work done. The data below

Bug#662983: When called by wajig/apt apt-listbugs crash and precludes the package upgrade

2012-03-15 Thread Bob Weber
I also see this same error. However, I login as root and then execute wajig in interactive mode. I use the update command followed by distupgrade. I'm not sure if there are any "su -c" commands run since I am already root. If there are any bugs to be reported by apt-listbugs I get the follow

Bug#661043: pulseaudio: After upgrade to alsa-utils pulseaudio now fails to connect, to, bluetooth device.

2012-02-25 Thread Bob Weber
I reverted to an image I made several days before this problem appeared. I upgraded everything but alsa-utils and the problem was not there. I then upgraded alsa-utils and still no problem. So something must have gone wrong with the original upgrade process to keep pulseaudio from seeing the

Bug#661043: pulseaudio: After upgrade to alsa-utils pulseaudio now fails to connect to, bluetooth device.

2012-02-23 Thread Bob Weber
Package: pulseaudio Version: 1.0-4 Severity: important I upgraded alsa-utils from 1.0.24.2-5 to 1.0.25-1 and libasound from 1.0.24.1-4 to 1.0.25-2 and pulseaudio now fails to see a blutooth device that has been connected to by the blutooth tray app. Also the pulseaudio volume control stopped s