[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debian 11 unofficial firmware first installation


Pawel L.wrote:
> The Speakup volume is extremely low during the installation process.

Did you take a look at the documentation for accessibility support in
the installer?


It notably says

“The default volume should be medium. To make it louder, press
CapsLock+2. To make it quieter, press CapsLock+1.”

There is *NO* way to be able to configure the audio level at a level
that matches all situations. The card itself, the speaker plugged on it,
the driver, all of these have an impact on what "good audio level" would
be. That is why there are these shortcuts to raise/lower it if never

> In the graphical environment, after login, I have no speech and my
> Braille display shows only 'Window without name" message.

So things actually seem to be just working, and it's simply that you do
not know yet how to use the graphical desktop.  The application menu can
be opened with the alt-f1 shortcut.

D.J.J. Ring wrote:
> 1.) You cannot log into MATE as a regular user.

You definitely can. At least all my tests let me just work fine with
MATE with the screen reader.

> 2.) The sound card detection and selection dialog is broken because there is no
> sound to hear to verify which sound card works.

In my tests there definitely is. Possibly with your precise sound boards
there are some drivers issues, but that's *not* a general problem.

We need more information from your system to be able to work out why
things don't work out for your.

> But you cannot log into MATE, you can type your username and password, press
> enter, but something crashes

That doesn't happen in my tests. Again, we'd need more information,
notably logs, from your system to determine what is crashing. That
should however rather be reported to MATE maintainers since that's MATE
that is crashing.

> Something similar happened with the release of Buster several years ago, but
> the next released version fixed it.

Bugs get fixed early when they are reported early. When they are
reported late, they are fixed late.

> Wait for the next version, hopefully the next version will fix this problem.

If bug reports do not contain useful information to be able to fix the
bug, the bug cannot get auto-fixed magically.

D.J.J. Ring, Jr., le mer. 18 août 2021 11:32:39 -0400, a ecrit:
> Too bad they didn't see my message about RC3 failures that I sent.

I do have in my mbox some messages from you dated august 14.
But that was the very day of the release!! CD images were already
getting uploaded and everything. You cannot expect bugs to be fixed with
such a short notice.

D.J.J. Ring, Jr. wrote:
> They should have stopped the release because few things are worse than
> a release that doesn't work at all.

It does completely work in my tests.

> Now Debian Bullseye won't even run out of the box.

It definitely does in my tests.

> so this is progress in the "making it worse" direction.

If people keep just ranting and not test and not provide information on
bugs, then yes thing will go bad. If people just happen to test the
alpha releases and report bug with information (all you need to know to
report is written on the wiki), then things will go smooth.

> but it needs modifications that Debian seems unwilling to do.

This is mere trial of intent. Don't you realize that it's just the
best way to demotivate the very people that happen to work on such
things? Please change your behavior, otherwise it's auto-realizing FUD.


Reply to: