Bug#1040792: linux-image-6.1.0-10-amd64 - computer crashes after log-in

2023-07-10 Thread Jonathan Joseph Chiarella

Erratum:


Kernel linux-image-6.1.09-amd64 works fine.


Kernel linux-image-6.1.0-9-amd64 works fine.

--
Jonathan Joseph Chiarella

PGP Fingerprint: 8B54 67AE 714B 8A5B D479 F578 6AAB 963C 0402 061A



Bug#1040792: linux-image-6.1.0-10-amd64 - computer crashes after log-in

2023-07-10 Thread Jonathan Joseph Chiarella

Package: linux-image-6.1.0-10-amd64
Version: 6.1.37-1

When running Debian 12.0 (stable) on kernel linux-image-6.1.0-10-amd64 on an 
AMD64 computer (A9-9420 Radeon R5), the system crashes after logging in as a 
user. This only happens after logging in. The lightdm display manager 
disappears and begins to log in to the user. Then the screen flashes, goes 
black, and a hard reset ensues. This happens no matter how many times I try. 
Sometimes, there a is a black screen and white console text appears. It only 
appears briefly.

Kernel linux-image-6.1.09-amd64 works fine.

Error messages on the black screen that sometimes appear:

Hardware error Processor 2
mce: CPU 0: [something I couldn't get ] Check: 0
Bank 4: f20001120c0f
i2c_designwave AMD0010:00:controller timed out
TSC0
PROCESSOR 2:670f00
TIME 1688732464 SOCKET 0 APIC 0 microcode 6006705


I had to take photographs of the screen or videos with my cell phone camera. 
The error message text only appears for a moment.

--
Jonathan Joseph Chiarella

PGP Fingerprint: 8B54 67AE 714B 8A5B D479 F578 6AAB 963C 0402 061A



Bug#953334: RFP: projectm -- iterative music visualization library

2020-04-29 Thread Jonathan Joseph Chiarella
On Sat, 7 Mar 2020 19:45:27 -0500 Boyuan Yang  wrote:
> Package: wnpp
> Severity: normal
> X-Debbugs-CC: siret...@tauware.de m...@debian.org
> debian-multime...@lists.debian.org
> 
> Dear package projectm maintainers,
> 
> According to https://tracker.debian.org/pkg/projectm , this package
> was just removed
> from Sid due to dependency on Qt4. However, the upstream has already released
> new versions supporting Qt5.
> 
> Please consider reintroducing projectm using new upstream releases. Thanks!
> 
> -- 
> Regards,
> Boyuan Yang

It looks like no one was able to step up on ProjectM's end for packaging: 
<https://github.com/projectM-visualizer/projectm/issues/200>.

I can file bug reports and stalk bug reports, but I cannot package or code, 
otherwise I'd help. I imagine if there were just one release at this point, 
built on Qt5, it could last a long time. It's not a program you'd have to worry 
about security-wise. It doesn't open files, just reads audio streams, not 
directly hooked to internet, does not manage passwords, etc. It looks as if it 
may support Wayland, too, or at least indirectly.

-- 
Jonathan Joseph Chiarella
jonathan.chiare...@gmail.com
PGP Fingerprint: 8B54 67AE 714B 8A5B D479 F578 6AAB 963C 0402 061A



signature.asc
Description: OpenPGP digital signature


Bug#857792: icedove-bidiui needs to become thunderbird-bidiui

2017-03-14 Thread Jonathan Joseph Chiarella
Package: icedove-bidiui
Version: 0.9.7-1

Debian is returning to the upstream branding of Mozilla's Firefox and 
Thunderbird.

Most Thunderbird packages have been renamed from "icedove" to "thunderbird" 
(and from "iceowl" plugin to "lightning"), but one remaining package is 
icedove-bidiui, which needs to be renamed as "thunderbird-bidiui.



signature.asc
Description: OpenPGP digital signature


Bug#674936: pulseaudio: disable flat volumes

2016-04-21 Thread Jonathan Joseph Chiarella
Hello,

Another user chiming in. I would like to see Flat-volumes disabled by
default, system-wide in the /etc configuration file. This was the older
pulseaudio behavior and now we have downstream Ubuntu (and all of its
derivatives) as well as Arch and now even Fedora (whose parent, RedHat,
is home to PulseAudio founders and current key developers) have made the
switch.

I have written to the downstream TAILS distribution asking them to
switch for practical and because the surreptitious raising of the master
volume is especially worrisome for TAILS users who are especially likely
to use headphones.

I exchanged some emails on the mailing list a few months back.
Unfortunately, a tentative solution offered was to tweak each individual
app that comes with TAILS to make sure it doesn't raise the master
volume. Below are some excerpts.

(Thank you for making a rock solid Linux distribution!)

**

Flat-volumes are disadvantageous for the user experience.

1. Flat volumes effectively render the master volume pointless.
   (A) Moving the slider down only lowers the volume of streams that
were set at the same level that the master volume was.
   (B) If any stream moves above the master volume, the master volume
moves up, but this is just cosmetic, since the master volume does not
set any limits. The only effect is that moving streams altogether will
now be changed and all streams move in tandem in different ways
   (C) If any new streams open at 100%, the master volume is set at
100% while old streams remain low, destroying any proportionality you
would want to keep by just moving the master volume slider.
   (D) The master volume is not truly a master volume. Each individual
audio output stream is actually an independent stream that controls
the audio card directly and is irrelevant to whatever level the master
volume is set.

2. Flat volumes do not behave like physical mixers, which are the
source for the concept of and the source for the visual representation
of a "master volume".
   (A) In a real mixer, or with flat volumes disabled, the master
volume controls the audio card. Each stream remains always a
proportional equal to or less than the volume. So if some programme
outputs at 100%, it will be 100% of the master volume.
   (B) Moving the master volume will not ever affect the volumes of
audio streams relative to one another.
   (C) The addition of new inputs will not affect the max output level
set by the audio card. No unauthorized raising of master volume.

3. Accessibility and safety
   (A) If flat volumes are used, then any new stream (like System
sounds, one that comes and goes) could open at 100%, raising the
master volume, but more importantly it would output at max volume
allowed by sound card. Since Tails is used often discreetly, the usage
of headphones is to be expected. The shock of sudden jumps in volume
is dangerous.
   (B) Since those who care or know about this and those who have it
explained prefer non-flat volumes in the majority and since Tails is
strict about its persistence, the flat-volumes default will
inconvenience most users and they will not be able to configure it a
persistent way (not even per-user through ~/.pulse)

4. User expectations and general preferences
   (A) The argument of "That's how Windows does it and Windows is
widely used" is not an argument for a good user experience.
   (B) The previous argument is not true. Before Vista, Windows did
not have flat volumes. It also lacked the integration of
in-application volume sliders and stream volumes like many poorly
integrated ALSA or Pulseaudio audio players on *nix.
   (C) Even post-Vista, Windows flat volumes do not behave like Pulse
in flat volume mode. It is more like a hybird of the two. So it is
inappropriate to hold up Windows since it does not behave like
Pulseaudio does.
   (D) The volume slider on some pairs of headsets behaves exactly
like the true/traditional master volume concept.
   (E) Downstream of Debian is Ubuntu and its re-spins and
derivatives. These overwhelmingly form the majority of desktop Linux
installations and are the first experience most have with *nix on the
desktop.

There is a long discussion at reddit at


The very problem described in the reddit original post was experienced
often, I believe, by Chris Fisher of Jupiter Broadcasting (Linux
Action Show etc) this month. He blamed KDE for not preventing it. I do
not know what caused him to have his volume spikes, but I switched to
non-flat years ago for because of this problem and I know that Chris
Fisher's usual distro is Arch, which uses flat volumes. So I am
guessing he takes flat volumes for granted or is unaware/forgot that
non-flat volumes are a thing on desktops and is suffering from the
same problem.

Flat Volume PROS: default (but Tails changes defaults all the time) as
advocated by Poettering and is somewhat similar to Windows Vista and
post-Vista

Flat Volume CONS: Reasons mentioned above.

Using flat-volumes when users do not