Bug#1040896: raspi-firmware: Unable to uninstall raspi-firmware on amd64 systems

2023-07-11 Thread William Chung
Package: raspi-firmware
Version: 1.20220830+ds-1
Severity: important
X-Debbugs-Cc: wiiliamchung...@gmail.com

Dear Maintainer,

Users are not able to uninstall raspi-firmware on amd64 systems, as the
initramfs hook will exit with the following error:

>   raspi-firmware: missing /boot/firmware, did you forget to mount it?
>   run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with
>   return code 1
>   run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
>   dpkg: error processing package linux-image-6.1.0-10-amd64 (--configure):
>installed linux-image-6.1.0-10-amd64 package post-installation script
>subprocess returned error exit status 1
>   dpkg: dependency problems prevent configuration of linux-image-amd64:
>linux-image-amd64 depends on linux-image-6.1.0-10-amd64 (= 6.1.37-1);
>however:
> Package linux-image-6.1.0-10-amd64 is not configured yet.
>
>   dpkg: error processing package linux-image-amd64 (--configure):
>dependency problems - leaving unconfigured
>   Errors were encountered while processing:
>linux-image-6.1.0-10-amd64
>linux-image-amd64
>   E: Sub-process /usr/bin/dpkg returned an error code (1)

To purge raspi-firmware, users will need to prevent
/etc/kernel/postinst.d/z50-raspi-firmware from triggering.

A current workaround is to add `exit 0` at the first line of
/etc/kernel/postinst.d/z50-raspi-firmware

I don't know where raspi-firmware was pulled in from, but the package  was
found in both systems where I installed debian bookworm (12) using the amd64
KDE live image. I assume that raspi-firmware is included by default.

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages raspi-firmware depends on:
ii  dosfstools  4.2-1
ii  dpkg1.21.22

raspi-firmware recommends no packages.

Versions of packages raspi-firmware suggests:
ii  bluez-firmware 1.2-9
ii  firmware-brcm80211 20230210-5
ii  firmware-misc-nonfree  20230210-5



Bug#951303: blender: Measure tool fails to snap with control key pressed

2020-02-13 Thread William Chung
Package: blender
Version: 2.81.a+dfsg-5
Severity: normal

Dear Maintainer,

   * What led up to the situation?

Nothing. Just launch blender and start working.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Open blender. Press tab at the default scene with the cube. Then press Shift +
Spacebar, then M. Click and drag to start measuring while pressing the control
key. (Any control key will do).

   * What was the outcome of this action?

The measure line did not snap to edges nor verticies.

   * What outcome did you expect instead?

Measure tool to snap to verticies or edges as mentioned in the blender forums
here: https://devtalk.blender.org/t/measurement-tool-snapping/6342



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (600, 'experimental'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-3-amd64 (SMP w/24 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages blender depends on:
ii  blender-data  2.81.a+dfsg-5
ii  fonts-dejavu  2.37-1
ii  libavcodec58  7:4.2.2-1
ii  libavdevice58 7:4.2.2-1
ii  libavformat58 7:4.2.2-1
ii  libavutil56   7:4.2.2-1
ii  libboost-locale1.67.0 1.67.0-17
ii  libc6 2.29-10
ii  libfftw3-double3  3.3.8-2
ii  libfreetype6  2.10.1-2
ii  libgcc-s1 [libgcc1]   10-20200204-1
ii  libgcc1   1:10-20200204-1
ii  libgl11.3.0-7
ii  libglew2.12.1.0-4+b1
ii  libgomp1  10-20200204-1
ii  libilmbase24  2.3.0-6
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2+b1
ii  libjemalloc2  5.2.1-1
ii  libjpeg62-turbo   1:1.5.2-2+b1
ii  libopenal11:1.19.1-1+b1
ii  libopencolorio1v5 1.1.1~dfsg0-5+b1
ii  libopenexr24  2.3.0-6
ii  libopenimageio2.1 2.1.10.1~dfsg0-5+b1
ii  libopenjp2-7  2.3.1-1
ii  libopenvdb5.2 5.2.0-7+b1
ii  libosdcpu3.4.03.4.0-6
ii  libosdgpu3.4.03.4.0-6
ii  libpcre3  2:8.39-12+b1
ii  libpng16-16   1.6.37-2
ii  libpython3.7  3.7.6-1+b1
ii  libsndfile1   1.0.28-6
ii  libspnav0 0.2.3-1+b2
ii  libstdc++610-20200204-1
ii  libswscale5   7:4.2.2-1
ii  libtbb2   2020.1-2
ii  libtiff5  4.1.0+git191117-2
ii  libx11-6  2:1.6.8-1
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  libxml2   2.9.4+dfsg1-8
ii  libxrender1   1:0.9.10-1
ii  libxxf86vm1   1:1.1.4-1+b2
ii  zlib1g1:1.2.11.dfsg-1.2

blender recommends no packages.

blender suggests no packages.

-- no debconf information



Bug#932102: FATAL_ERROR: Can't receive value from the server at pulseaudio volume over 100

2019-07-14 Thread William Chung
Package: moc
Version: 1:2.6.0~svn-r2994-3
Severity: normal

Dear Maintainer,

Turning up the volume over 100 in pulseaudio settings kills mocp. This happens
in both the build in buster and testing.

Turning the volume over 100% makes mocp throw the error on the title

`FATAL_ERROR: Can't receive value from the server!`



-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages moc depends on:
ii  libasound21.1.8-1
ii  libc6 2.28-10
ii  libcurl3-gnutls   7.64.0-4
ii  libdb5.3  5.3.28+dfsg1-0.6
ii  libfaad2  2.8.8-3
ii  libflac8  1.3.2-3
ii  libgcc1   1:8.3.0-7
ii  libid3tag00.15.1b-14
ii  libjack-jackd2-0 [libjack-0.125]  1.9.12~dfsg-2
ii  libltdl7  2.4.6-10
ii  libmad0   0.15.1b-10
ii  libmagic1 1:5.35-4
ii  libmodplug1   1:0.8.9.0-2
ii  libmpcdec62:0.1~r495-1+b2
ii  libncursesw6  6.1+20181013-2
ii  libogg0   1.3.2-1+b1
ii  libopusfile0  0.9+20170913-1
ii  libpopt0  1.16-12
ii  librcc0   0.2.12-0.1
ii  libresid-builder0c2a  2.1.1-15
ii  libsamplerate00.1.9-2
ii  libsidplay2   2.1.1-15
ii  libsidutils0  2.1.1-15
ii  libsndfile1   1.0.28-6
ii  libspeex1 1.2~rc1.2-1+b2
ii  libstdc++68.3.0-7
ii  libtagc0  1.11.1+dfsg.1-0.3
ii  libtinfo6 6.1+20181013-2
ii  libvorbis0a   1.3.6-2
ii  libvorbisfile31.3.6-2
ii  libwavpack1   5.1.0-6
ii  zlib1g1:1.2.11.dfsg-1

moc recommends no packages.

Versions of packages moc suggests:
ii  moc-ffmpeg-plugin  1:2.6.0~svn-r2994-3

-- no debconf information