Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation

[D.J.J. Ring, Jr.]

No, because the installer still might be selecting the wrong sound card,
it's usually the second choice, so even without sound I press enter to at
least choose something.

How can I chose the sound card, I'll chose them one by one and try.

David


On Tue, Jan 18, 2022, 03:21 Samuel Thibault  wrote:

> D.J.J. Ring, Jr., le lun. 17 janv. 2022 22:01:59 -0500, a ecrit:
> > Using firmware-10.11.0-amd64 installer, I gave this command:
> >
> > amixer -c 0 set IEC958,0 off
> >
> > I didn't get a response because my sound cards were renumbered.
>
> Ah, yes, sure.
>
> > So I changed the command to:
> > amixer -c 1 set IEC958,0 off
> >
> > This is the response I received.
> >
> > Simple mixer control 'IEC958',0
> >   Capabilities: pswitch pswitch-joined
> >   Playback channels: Mono
> >   Mono: Playback [off]
>
> And that didn't make espeakup start speaking?
>
> Samuel
>

Bug#1002976: Debian 11

[D.J.J. Ring, Jr.]

I just tried the mini iso again, the error about firmware was about the
installer language question, it then asked me if I had a disk with firmware
and if so to install it.

This looks normal to me.

I have since learned hot to download all the firmware and put it on my usb
stick in a folder named 'firmware", when I do this, the mini.iso is able to
see my wifi card and asks me the network ID number and password for my wifi
and it will connect.

Best regards,
David


On Mon, Jan 17, 2022 at 3:33 AM Samuel Thibault 
wrote:

> D.J.J. Ring, Jr., le dim. 16 janv. 2022 21:44:55 -0500, a ecrit:
> > The mini iso just gave me an error that firmware was missing for my wifi
> - I
> > found the instructions on how to load firmware and put it in a FAT
> partition on
> > USB stick in a directory named /firmware.  No more error.
>
> That was not the question. Please *exactly* answer the question I am
> asking:
>
> *When* was this error precisely? Before or after the installer language
> question?
>
> That's the information I need, if you don't provide it we'll be unused
> what works and what doesn't work, and won't be able to fix the bug.
>
> Samuel
>

Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation

[D.J.J. Ring, Jr.]

On Mon, Jan 17, 2022 at 4:55 AM Samuel Thibault 
wrote:

> Hello,
>
> Thanks for the information.
>
> D.J.J. Ring, Jr., le dim. 16 janv. 2022 22:12:29 -0500, a ecrit:
> > I already noticed something, in Buster, my digital card isn't listed
> > with the cat /proc/asound/cards command.
>
> Yes, that's because in the bullseye case you have used the mini.iso. As
> I wrote, please rather use the netinst bullseye iso image. The mini.iso
> image was only to check whether the presence of the i915 driver would
> help.
>
> > ## Output of amixer -c 0 scontents and amixer -c 1 scontents for the
> Bullseys
> > mini_amixer1contents
> >
> >
> > ## Output of amixer -c 0 scontents  amixer -c 1 scontents and amixer -c 1
> > 10.11.0_amixer1contents
>
> One thing I notice is this:
>
> Simple mixer control 'IEC958',0
>   Capabilities: pswitch pswitch-joined
>   Playback channels: Mono
>   Mono: Playback [off]
>
> It's off in the Buster case and on in the Bullseye case. I guess you are
> not using the IEC958 output.
>
> Could you try running this inside the bullseye installer:
>
> amixer -c 0 sset IEC958,0 off
>
> samuel
>

Hello Samuel,

I'm trying to be very careful to do whatever you tell me, but I will
probably make a mistake, but not on purpose, just because I misunderstood.

Here's what I did.

Using firmware-10.11.0-amd64 installer, I gave this command:

amixer -c 0 set IEC958,0 off

I didn't get a response because my sound cards were renumbered.

So I changed the command to:
amixer -c 1 set IEC958,0 off

This is the response I received.

Simple mixer control 'IEC958',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]

About the firmware error, it's right after language selection saying that
some of my hardware requires firmware and that I should insert a disk with
firmware on it.   That looks normal to me.

While my computer has a digital sound output, I don't use it, I use the
small speaker 3.5mm TRS (tip, ring, sleeve) plug like music players use to
go to an amplified speaker.

Regards,
David

Bug#1002976: Debian 11

[D.J.J. Ring, Jr.]

Samuel,

It was just an error that I needed firmware for my WiFi.  I put
firmware-iwlwifi_20210818-1_all.deb in a FAT formatted USB stick in
/firmware and everything was happy.

Thanks,
David

On Sun, Jan 16, 2022 at 7:13 PM Samuel Thibault 
wrote:

> D.J.J. Ring, Jr., le ven. 14 janv. 2022 08:55:16 -0500, a ecrit:
> > You gave me a mini.iso to try but when I booted from it, it gave me an
> error
> > that firmware for my WiFi was needed.
>
> Just to make sure, when was this error precisely? Before or after the
> installer language question?
>
> Samuel
>

Bug#1002976: Debian 11

[D.J.J. Ring, Jr.]

The mini iso just gave me an error that firmware was missing for my wifi -
I found the instructions on how to load firmware and put it in a FAT
partition on USB stick in a directory named /firmware.  No more error.

Thanks you.

David

On Sun, Jan 16, 2022 at 7:15 PM Samuel Thibault 
wrote:

> D.J.J. Ring, Jr., le ven. 14 janv. 2022 08:55:16 -0500, a ecrit:
> > You gave me a mini.iso to try but when I booted from it, it gave me an
> error
> > that firmware for my WiFi was needed.
>
> Just to make sure, when was this error precisely? Before or after the
> installer language question?
>
> Samuel
>
>

Bug#1002976: Debian 11

[D.J.J. Ring, Jr.]

Sorry, Samuel, you misunderstand me.

You gave me a mini.iso to try but when I booted from it, it gave me an
error that firmware for my WiFi was needed. I do not have access to
Ethernet, our housing has WiFi supplied to us only.

So I could not test your mini.iso.

Is there a way I can put the needed wifi firmware into the iso, or somehow
be able to try your iso?

Best wishes,

David

On Fri, Jan 14, 2022, 08:08 Samuel Thibault  wrote:

> D.J.J. Ring, Jr., le ven. 14 janv. 2022 08:00:27 -0500, a ecrit:
> > Is there a way to use your mini  iso somehow and load the wifi modules?
>
> Not directly, but that is unrelated. We don't need you to get the
> network working, the only thing which is at stake is getting sound
> working.
>
> Samuel
>

Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation

[D.J.J. Ring, Jr.]

It might have asked for the language, but I had no sound.  I know I didn't
get as far as networking, but I probably got as far as language and
keyboard, I've done installs so much recently I just didn't notice.

I'll try it again, I thought it was too soon to have logs. Usually when I
go to the other console, I just have busybox and I don't know how to mount
a CD stick with busy box.

I'll try it again.

David

On Sat, Jan 8, 2022 at 8:53 PM Samuel Thibault  wrote:

> D.J.J. Ring, Jr., le sam. 08 janv. 2022 20:38:43 -0500, a ecrit:
> > First, the mini.iso tried over and over to detect my soundcard,
>
> over and over, what do you mean? Was it failing to emit any sound at
> all?
>
> > then it went to ask if I had a USB stick with Debian on it,
>
> didn't it first ask for the language?
>
> Did you try to press alt-f2 to get to the second console?
>
> Samuel
>

Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation

[D.J.J. Ring, Jr.]

No, luck.

First, the mini.iso tried over and over to detect my soundcard, I currently
have 3, first one is usually digital, next is PCH analog, I use that, and I
had my USB camera plugged in.  It kept repeating in a loop for 5 minutes,
then I finally chose soundcard #1 then it went to ask if I had a USB stick
with Debian on it, so I just pressed enter, thinking it was talking about
the mini.iso.  It went around and around for a good 10 minutes before I had
decided it wasn't going to work.

So again, no luck with the mini.iso.

Best wishes,
David

On Sat, Jan 8, 2022 at 5:22 PM Samuel Thibault  wrote:

> D.J.J. Ring, Jr., le sam. 08 janv. 2022 16:34:09 -0500, a ecrit:
> > This is in bash, not busy box, right? I can't figure out busybox!
>
> busybox is mostly like bash.
>
> > At what time do I mount a USB stick,
>
> The main menu will be fine.
>
> > and where is the command to save installer logs to it?
>
> The syslog is already in /var/log/syslog
>
> Samuel
>

Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

[D.J.J. Ring, Jr.]

Is there anything else I can do to help solve this problem?

I just tried the last daily iso with firmware with no luck.

Also I've discussed the problem with GRUB inserting an entry in the EFI
boot automatically which overrides user setting in BIOS.  That means if I
last booted into Debian I will go directly to Debian without having the
ability to press F2 (or whatever key is needed to access BIOS settings)..
I mentioned that this caused a problem on a multi system boot, especially
for those of us who cannot see well, but  also for everyone because the
only way to change this is either to open up the computer or laptop and
reset the BIOS by pressing a rubber domed switch which I suppose grounds
the capacitor is there to  holds a voltage on the computer CMOS to keep
settings, pushing the little switch puts the voltage to zero and restore
the factory settings.

There is a problem and I'm trying to get someone to fix it.   It's probably
an unfortunate consequence of this "feature" - GRUB would work just right
without this feature, and I cannot think of any reason that this "feature"
exists. It appears to be a bug.  It's certainly understandable to those who
who must  now take extraordinary measures to reset their BIOS by resetting
the CMOS. For blind persons who have already obtained sighted help to et up
their BIOS the way they want it, to boot from USB HD - a USB stick, it's
totally unwanted and very inconvenient. I have no idea if GRUB is aware of
this bug.

I believe even if GRUB is intended to do this, it shouldn't, it seems to be
be an unfortunate consequence of their work.   Even if it can be
overridden, it is much too complicated for the average computer user.
(Some kind member of this list sent me instructions to override this new
behavior of GRUB, but they are extremely complicated. If anything this
"feature" should be enabled only as an option.  I've just subscribed to
GRUB bugs list to tell them of this, hopefully it can be fixed because it
overrides the user's BIOS settings.

Best wishes to all,
David


On Tue, Jan 4, 2022 at 2:54 PM D.J.J. Ring, Jr.  wrote:

> I have already done that, did it not go through? I did receive a message
> saying that the message I sent because it didn't mention a package would be
> disregarded.
> It would have been sent from n...@arrll.net - any way of checking
> further? Darn it,  I should have BCC it to you, Samuel.
>
> Thanks,
>
> David
>
> On Tue, Jan 4, 2022 at 3:53 AM Samuel Thibault 
> wrote:
>
>> Hello,
>>
>> As already mentioned, please do this:
>>
>> install with the Buster image, and use reportbug to send the
>> installation information, just like you did with Bullseye on Mon, 3 Jan
>> 2022 14:18:39 -0500.
>>
>> Really, do please do that.
>>
>> Samuel
>>
>

Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

[D.J.J. Ring, Jr.]

I have already done that, did it not go through? I did receive a message
saying that the message I sent because it didn't mention a package would be
disregarded.
It would have been sent from n...@arrll.net - any way of checking further?
Darn it,  I should have BCC it to you, Samuel.

Thanks,

David

On Tue, Jan 4, 2022 at 3:53 AM Samuel Thibault  wrote:

> Hello,
>
> As already mentioned, please do this:
>
> install with the Buster image, and use reportbug to send the
> installation information, just like you did with Bullseye on Mon, 3 Jan
> 2022 14:18:39 -0500.
>
> Really, do please do that.
>
> Samuel
>

Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

[D.J.J. Ring, Jr.]

On Tue, Jan 4, 2022, 01:09 Philip Hands  wrote:

> "D.J.J. Ring, Jr."  writes:
>
> > Yes, I said that, but I am under the impression that whatever went wrong
> > happened before partitions were mounted.
> >
> > I remembered using that advance menu configuration which I was unable to
> > find in Bullseye  - at least the same exact thing with the ability of
> > obtaining an IP address and downloading files.  I thought these files
> were
> > lost if the logs weren't sent to a web server or written during
> > installation to a mounted hard drive.
>
> I think you've been misinformed there, unless you are aborting the
> install early because you cannot drive it without the sound working.
>
> Assuming the install completes, the complete logs, including what happened
> early in the install, are copied from the installer's /var/log (which is
> in RAM) to the target system's /var/log/installer, where they can be
> found once one boots the resulting installed system.
>
> Of course if you are not able to complete the install, because the lack
> of working sound makes that impossible for you, then it will not get as far
> as writing the logs to the target system's disk for you.
>
> > No errors are ever seen or heard - except that there is no sound after
> the
> > installer probes for sound card (press enter if this is your sound card,
> > etc.).
> >
> > I'm going to install Bullseye once again because right now I have Buster
> -
> > but the sound is working in Buster and the screen readers orca and
> console
> > are both working. and sound from videos in the browser are all working.
> > Now if I can only get this in Bullseye.
>
> If you have working buster, you could also try upgrading that to
> bullseye to see if that ends up with a working setup.
>
> That ought to help narrow down whether the problem is really in the
> installer, or is related to other changes between the releases.
>
> BTW I find `etckeeper` very useful for seeing what changes on a system
> (it creates a git repository under /etc for you, and records changes
> that happen), so you could install that before upgrading. It also
> records the versions of packages that get changed in the git log as well
> as the changes to files under /etc when you upgrade packages.
>
> Cheers, Phil.
> --
> |)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
> |-|  http://www.hands.com/http://ftp.uk.debian.org/
> |(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY
>


Thanks, Phil.

I tried the daily Sid unstable and it also has no working sound screen
reader during but once finished it's there.

I'll believe you about the files because I cannot find an advanced menu
that installs the screen reader like Buster.had. Buster is much easier to
install.

I'm going to try another installer tomorrow.

David

Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

[D.J.J. Ring, Jr.]

Yes, I said that, but I am under the impression that whatever went wrong
happened before partitions were mounted.

I remembered using that advance menu configuration which I was unable to
find in Bullseye  - at least the same exact thing with the ability of
obtaining an IP address and downloading files.  I thought these files were
lost if the logs weren't sent to a web server or written during
installation to a mounted hard drive.

No errors are ever seen or heard - except that there is no sound after the
installer probes for sound card (press enter if this is your sound card,
etc.).

I'm going to install Bullseye once again because right now I have Buster -
but the sound is working in Buster and the screen readers orca and console
are both working. and sound from videos in the browser are all working.
Now if I can only get this in Bullseye.

Is there anything I can run while I have this installed?  I'm going to wait
for your response, it's past midnight on the Continent and 2000 hours here
on the east coast USA.  Also any suggestion of what to install thjat might
be more helpful?  Maybe the daily SID installer?

Best wishes,
David


On Mon, Jan 3, 2022 at 8:35 PM Samuel Thibault  wrote:

> D.J.J. Ring, Jr., le lun. 03 janv. 2022 20:26:54 -0500, a ecrit:
> > You mean take a video of the screen when I am trying to install Bullseye?
>
> Yes.
>
> > I don't get any error messages at all, it just doesn't speak to me.
>
> At some point you mentioned some errors:
>
> “the errors precede writing to disk.”
>
> Samuel
>

Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

[D.J.J. Ring, Jr.]

Samuel,

You mean take a video of the screen when I am trying to install Bullseye?

I don't get any error messages at all, it just doesn't speak to me.

Regards,

David

On Mon, Jan 3, 2022 at 7:03 PM Samuel Thibault  wrote:

> I'd like to emphasize this:
>
> john doe, le lun. 03 janv. 2022 09:39:41 +0100, a ecrit:
> > - As far as I understand it, everything is working fine on Buster but
> > not on Bullseye, tarring the logs from a Buster installation and from
> > Bullseye might give us some clues on where this is failing.
>
> Yes, please do this, that should be extremely informative.
>
> Any error message from the kernel will be visible in there.
>
> Possibly there are some error messages from alsa itself, which may not
> be there. Possibly you could use a smartphone to make a recording of the
> screen while you are booting the bullseye installer, so we can see which
> error messages you get there?
>
> Samuel
>

Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

[D.J.J. Ring, Jr.]

On Sun, Jan 2, 2022, 03:59 Holger Wansing  wrote:

> Hi,
>
> Am 2. Januar 2022 02:40:16 MEZ schrieb "David J. Ring, Jr."  >:
> >
> >lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U
> Audio Controller [8086:160c] (rev 09)
>
>
> As I already wrote:
> my best guess for this one would be
> https://www.debian.org/releases/stable/debian-installer/#errata
>
>
> Holger
>
>
> --
> Sent from /e/ OS on Fairphone3
>

Holger,

So is this fixed? Does the daily our weekly installer with firmware allow
speech to be heard during installation?

Thank you,
David

>

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

[D.J.J. Ring, Jr.]

I made a new partition for /home and I reinstalled Debian, this time I
could lot in to MATE and I could log into the CLI.

But the issue remains of after the Installation disk detects my sound card,
it seems to find my sound card, but immediately after finding it, no
further sound is heard.

This remains.

Thanks for the help.

David


On Sat, Jan 1, 2022 at 6:16 PM D.J.J. Ring, Jr.  wrote:

> I don't know why when using the installer, not hearring espeak in console
> isn't a installer issue.
>
> I believe I have already done what you are speaking of.
>
> I have /home/djringjr.
>
> At first I reused this, the installer permits NOT formatting a separate
> /home partition.  That's what I did.
>
> I had problems I could not log in as my regular named user using my old
> /home/djringjr files.
>
> Then I reran the installer - again no sound during accessible
> installation, This time I made up a brand new never before user name.
>
> The result was the very same, I could not log in with my user account,
> only root.
>
> What is your next suggestion?
>
> There is an installer issue, not having speech during an accessible
> installation is an installer issue .
>
> Making a brand new user account and not being able to log in might be
> something else.  Where do I go to get this part fixed?
>
> Thanks,
> David
>
> On Sat, Jan 1, 2022 at 5:22 PM Holger Wansing 
> wrote:
>
>> Hi,
>>
>> Am 1. Januar 2022 21:38:39 MEZ schrieb "D.J.J. Ring, Jr." > >:
>> >No on the first run after installation, I cannot log in using my user
>> >account.
>> >
>> >I tried installation again, still keeping /home partition data but using
>> a
>> >brand-new user account. This installation also failed in the exact same
>> >way.  I had voice at the lightdm login prompt but I could not log in. I
>> >could log in as previously by using root.
>> >
>> >So reusing by /home/djringjr folder won't let me log in, using a
>> brand-new
>> >user account with brand new files from /etc/skel won't let me run the
>> GUI.
>>
>> When performing a default installation it is known, that logging in as a
>> normal user.
>>
>> So, if you have over and over the same issue, using that unusual
>> installation
>> concept (re-using pre-existing home data), which is not officially
>> supported by
>> the installer, you should probably try a default install, without any
>> old-home-data
>> tricks - just for a test.
>>
>> If that works, you could then carefully merge your home data back into
>> the new
>> system.
>>
>>
>> In summary, this all is not an installer issue, by the way.
>>
>> Holger
>>
>>
>>
>>
>> --
>> Sent from /e/ OS on Fairphone3
>>
>

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

[D.J.J. Ring, Jr.]

I don't know why when using the installer, not hearring espeak in console
isn't a installer issue.

I believe I have already done what you are speaking of.

I have /home/djringjr.

At first I reused this, the installer permits NOT formatting a separate
/home partition.  That's what I did.

I had problems I could not log in as my regular named user using my old
/home/djringjr files.

Then I reran the installer - again no sound during accessible installation,
This time I made up a brand new never before user name.

The result was the very same, I could not log in with my user account, only
root.

What is your next suggestion?

There is an installer issue, not having speech during an accessible
installation is an installer issue .

Making a brand new user account and not being able to log in might be
something else.  Where do I go to get this part fixed?

Thanks,
David

On Sat, Jan 1, 2022 at 5:22 PM Holger Wansing  wrote:

> Hi,
>
> Am 1. Januar 2022 21:38:39 MEZ schrieb "D.J.J. Ring, Jr." :
> >No on the first run after installation, I cannot log in using my user
> >account.
> >
> >I tried installation again, still keeping /home partition data but using a
> >brand-new user account. This installation also failed in the exact same
> >way.  I had voice at the lightdm login prompt but I could not log in. I
> >could log in as previously by using root.
> >
> >So reusing by /home/djringjr folder won't let me log in, using a brand-new
> >user account with brand new files from /etc/skel won't let me run the GUI.
>
> When performing a default installation it is known, that logging in as a
> normal user.
>
> So, if you have over and over the same issue, using that unusual
> installation
> concept (re-using pre-existing home data), which is not officially
> supported by
> the installer, you should probably try a default install, without any
> old-home-data
> tricks - just for a test.
>
> If that works, you could then carefully merge your home data back into the
> new
> system.
>
>
> In summary, this all is not an installer issue, by the way.
>
> Holger
>
>
>
>
> --
> Sent from /e/ OS on Fairphone3
>

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

[D.J.J. Ring, Jr.]

To be clear,

On the first run after installation, I could not log in using my user
account.

I tried installation again, still keeping /home partition data but using a
brand-new user account. This installation also failed in the exact same
way. I had voice at the lightdm login prompt but I could not log in. I
could log in as previously by using root.

At that time, I didn't know a way to disable lightdm login and just log in
with the console. I suspect I'd get the same result as I do now, that I
could not log in with any user account, only the supervisor account, root.
At that time, I just suspected that my user account was just having
problems accessing Xorg, that's why I included the Xorg error logs, now I
see that the problem goes beyond this, that I cannot log in with any user
either using my old djringjr home folder which works if I reinstall latest
Debian 10, nor a previously non-existing username which created new file
folder populated by /etc/skel files.

I was able in all cases able to log into both the cli and the GUI with root.

I was able to log into root in the CLI then su to my original username in
all cases but starting GUI still failed.

Regards,

David



On Sat, Jan 1, 2022, 15:38 D.J.J. Ring, Jr.  wrote:

> No on the first run after installation, I cannot log in using my user
> account.
>
> I tried installation again, still keeping /home partition data but using a
> brand-new user account. This installation also failed in the exact same
> way.  I had voice at the lightdm login prompt but I could not log in. I
> could log in as previously by using root.
>
> So reusing by /home/djringjr folder won't let me log in, using a brand-new
> user account with brand new files from /etc/skel won't let me run the GUI.
>
> Since then I've discovered with my current installation not only can't I
> access the GUI but additionally I cannot access the CLI at least directly.
> I can login as root then su to my user name and access my user CLI but
> running startx still fails.
>
> I can install the last version of the previous Debian before Bullseye
> perfectly with my current /home folder.
>
> Best wishes,
>
> David
>
> Regards,
>
>
>
> On Sat, Jan 1, 2022, 14:39 Holger Wansing  wrote:
>
>> Hi,
>>
>> "D.J.J. Ring, Jr."  wrote (Sat, 1 Jan 2022 13:37:20
>> -0500):
>> > 1.  Cannot boot into MATE GUI means that I cannot boot into the MATE
>> > Graphical User Interface with the user account - which is what is
>> expected
>> > to happen after a normal successful installation.   I did some
>> > investigation  into this.
>> >
>> > This is what I did:  .  I disabled lightdm using systemctl disable
>> lightdm
>> > then more recently I used the root command "systemctl set-default
>> > multi-user.target" and now I see I cannot even log in as my regular
>> user.
>>
>> This is what I had expected, so in the first run it's not an issue with
>> the
>> MATE GUI.
>>
>> > I tried a new named user and did the same installation, I had the very
>> same
>> > problems with the new username.
>> >
>> > My /home/djringjr/ folder was used successfully with the last Debian
>> Buster
>> > release.
>>
>> Hmm, I wonder what that means exactly, as well as the following sentence:
>>
>> > [...]  When
>> > installing for my normal user account, I do not format /home/myuser
>> folder.
>>
>> Do you re-use an old/existing home folder of some user account somehow
>> for the
>> new user?
>> I don't know if that is supposed to work.
>> I only know the szenario, where a complete new home folder is created
>> automatically, when a new user is added to the system (with the "useradd"
>> command).
>>
>> > I have entered the root account and re-entered my useraccount
>> password.  I
>> > have done this several times.  Remember this also happened when I had an
>> > entirely new user account with a newly made /home/newuser folder.
>>
>> So you have tried, to log in as root on the console and type
>> "adduser yourusername" to create a completely new user?
>> And see if you can successfully login into that new account with
>> "su -l yourusername" ?
>>
>>
>> > I know the username password is correct because as root I enter "su
>> > myusername" and I am in user account, then from my user account,  I type
>> > "su myusername" and I receive a prompt for my password.  I have further
>> > checked by entering an incorrect password and received "authentication
>> > failure" response.
&g

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

[D.J.J. Ring, Jr.]

No on the first run after installation, I cannot log in using my user
account.

I tried installation again, still keeping /home partition data but using a
brand-new user account. This installation also failed in the exact same
way.  I had voice at the lightdm login prompt but I could not log in. I
could log in as previously by using root.

So reusing by /home/djringjr folder won't let me log in, using a brand-new
user account with brand new files from /etc/skel won't let me run the GUI.

Since then I've discovered with my current installation not only can't I
access the GUI but additionally I cannot access the CLI at least directly.
I can login as root then su to my user name and access my user CLI but
running startx still fails.

I can install the last version of the previous Debian before Bullseye
perfectly with my current /home folder.

Best wishes,

David

Regards,



On Sat, Jan 1, 2022, 14:39 Holger Wansing  wrote:

> Hi,
>
> "D.J.J. Ring, Jr."  wrote (Sat, 1 Jan 2022 13:37:20 -0500):
> > 1.  Cannot boot into MATE GUI means that I cannot boot into the MATE
> > Graphical User Interface with the user account - which is what is
> expected
> > to happen after a normal successful installation.   I did some
> > investigation  into this.
> >
> > This is what I did:  .  I disabled lightdm using systemctl disable
> lightdm
> > then more recently I used the root command "systemctl set-default
> > multi-user.target" and now I see I cannot even log in as my regular user.
>
> This is what I had expected, so in the first run it's not an issue with
> the
> MATE GUI.
>
> > I tried a new named user and did the same installation, I had the very
> same
> > problems with the new username.
> >
> > My /home/djringjr/ folder was used successfully with the last Debian
> Buster
> > release.
>
> Hmm, I wonder what that means exactly, as well as the following sentence:
>
> > [...]  When
> > installing for my normal user account, I do not format /home/myuser
> folder.
>
> Do you re-use an old/existing home folder of some user account somehow for
> the
> new user?
> I don't know if that is supposed to work.
> I only know the szenario, where a complete new home folder is created
> automatically, when a new user is added to the system (with the "useradd"
> command).
>
> > I have entered the root account and re-entered my useraccount password.
> I
> > have done this several times.  Remember this also happened when I had an
> > entirely new user account with a newly made /home/newuser folder.
>
> So you have tried, to log in as root on the console and type
> "adduser yourusername" to create a completely new user?
> And see if you can successfully login into that new account with
> "su -l yourusername" ?
>
>
> > I know the username password is correct because as root I enter "su
> > myusername" and I am in user account, then from my user account,  I type
> > "su myusername" and I receive a prompt for my password.  I have further
> > checked by entering an incorrect password and received "authentication
> > failure" response.
> >
> > root@debian:~# su djringjr
> > djringjr@debian:/root$ su djringjr
> > Password: [I enter the correct password\
> > djringjr@debian:/root$ exit
> > exit
> > djringjr@debian:/root$ su djringjr
> > Password: [I enter an incorrect password\
> > su: Authentication failure
> > djringjr@debian:/root$
> >
> > You asked me to state the problems again, here they are.
> >
> > 1. During installation I chose accessible text installation, the
> installer
> > appeared to detect my sound card, but after that I hear no sound from the
> > screen reader.
>
> That might be the issue described here:
> https://www.debian.org/releases/stable/debian-installer/#errata
>
> I do not  use a Braille device, so I cannot comment on
> > Braille.  I still have limited vision, so I was able to finish the
> > installation.
> > When I rebooted, I had screen reader, but there were additional problems.
> > I also tried the live DVD to install  and I had the exact problems.  I
> > believe I tried the 11.0 release with firmware four or five times,  and I
> > have tried the 11.2 firmware release at least four times, and the 11.2
> live
> > release twice, all gave me the exact same problems. The system was
> unusable
> > as regular user in every case except it WAS usable in the console if I
> > logged in as root, then logged in as username.
> >
> > 2. I cannot log in as my user account into console.  This also means had
> I
> > not dis

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

[D.J.J. Ring, Jr.]

Hello Holger Wansing,

Thanks for helping me with these problems.

Here are my answers to my best ability to answer them.

1.  Cannot boot into MATE GUI means that I cannot boot into the MATE
Graphical User Interface with the user account - which is what is expected
to happen after a normal successful installation.   I did some
investigation  into this.

This is what I did:  .  I disabled lightdm using systemctl disable lightdm
then more recently I used the root command "systemctl set-default
multi-user.target" and now I see I cannot even log in as my regular user.

I tried a new named user and did the same installation, I had the very same
problems with the new username.

My /home/djringjr/ folder was used successfully with the last Debian Buster
release.

If I reinstall the last Debian 10 firmware which I had been using prior to
Bullseys 11.0 release which also failed in the exact same way, everything
is excellent, my sound card is detected during accessible installation,
when I boot i go to the lightdm screen and I can  log in as my regular
user.  I also have sound as my regular user in GUI and also I have ORCA in
the GUI.

I have entered the root account and re-entered my useraccount password.  I
have done this several times.  Remember this also happened when I had an
entirely new user account with a newly made /home/newuser folder.  When
installing for my normal user account, I do not format /home/myuser folder.

I know the username password is correct because as root I enter "su
myusername" and I am in user account, then from my user account,  I type
"su myusername" and I receive a prompt for my password.  I have further
checked by entering an incorrect password and received "authentication
failure" response.

root@debian:~# su djringjr
djringjr@debian:/root$ su djringjr
Password: [I enter the correct password\
djringjr@debian:/root$ exit
exit
djringjr@debian:/root$ su djringjr
Password: [I enter an incorrect password\
su: Authentication failure
djringjr@debian:/root$

You asked me to state the problems again, here they are.

1. During installation I chose accessible text installation, the installer
appeared to detect my sound card, but after that I hear no sound from the
screen reader.  I do not  use a Braille device, so I cannot comment on
Braille.  I still have limited vision, so I was able to finish the
installation.
When I rebooted, I had screen reader, but there were additional problems.
I also tried the live DVD to install  and I had the exact problems.  I
believe I tried the 11.0 release with firmware four or five times,  and I
have tried the 11.2 firmware release at least four times, and the 11.2 live
release twice, all gave me the exact same problems. The system was unusable
as regular user in every case except it WAS usable in the console if I
logged in as root, then logged in as username.

2. I cannot log in as my user account into console.  This also means had I
not disabled graphical user log on with lightdm, I would not  be able to
log on to the MATE GUI as is the subject of my error report.

3.  I can  log into my root account in console, and before I disabled
lightdm  I was able  to log in with lightdm to the MATE GUI, however,
running orca -s says no speech available.  See the error file I produced by
running "orca -s 2> orcaerrors" then interrupting the terminal with
control-c.  I also get multiple AT-SPI errors which are in the attached
orcaerrors file.

.
Best regards,

David



On Sat, Jan 1, 2022 at 11:56 AM Holger Wansing  wrote:

> Hi,
>
> "D.J.J. Ring, Jr."  wrote (Sat, 1 Jan 2022 09:39:26 -0500):
> > Thanks,
> >
> > Here they are.
> >
> > Regards,
> > David
> >
> > On Sat, Jan 1, 2022 at 8:59 AM Holger Wansing 
> wrote:
> > > You should provide the installer log files (to be found in
> > > /var/log/installer).
> > > Sent them compressed to this bugreport.
>
> From your logs it seems your installation was a success, I cannot see any
> grave issues.
>
>
> So, we need to go back to the beginning:
> What are your problems, exaclty?
> What do you do, and what happens? Which error message exactly, and so on...
>
>
> The subject of this bug has "Cannot boot into MATE GUI".
> What does this mean? Could it be, that just the password is not correct?
> (Maybe you now have a different keyboard layout active than during
> installation, or similar?)
>
>
>
> Holger
>
>
> --
> Holger Wansing 
> PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
>


orcaerrors
Description: Binary data

Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can

[D.J.J. Ring, Jr.]

Also I just used
systemctl set-default multi-user.target to change to a console log in.

I cannot log in as user, only as root.
GUI can also only be started as root.
Have espeakup in console by as soon as log into Mate using root account, no
sound, Orca setup has no speech settings.

Regards,

David

On Sat, Jan 1, 2022 at 9:39 AM D.J.J. Ring, Jr.  wrote:

> Thanks,
>
> Here they are.
>
> Regards,
> David
>
> On Sat, Jan 1, 2022 at 8:59 AM Holger Wansing 
> wrote:
>
>> Hi,
>>
>> "David J. Ring, Jr."  wrote (Sat, 1 Jan 2022 00:11:22
>> -0500):
>> > Boot method: USB
>> > Image version: Image version: firmware-11.2.0-amd64-DVD-1.iso
>> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.2.0+nonfree/amd64/iso-dvd/firmware-11.2.0-amd64-DVD-1.iso
>> 2021-12-18
>> > Date: 
>> >
>> > Machine: Machine: Intense-PC2-BRW (IPC2) (System SKUNumber)
>> > Partitions: 
>> >
>> >
>> > Base System Installation Checklist:
>> > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>> >
>> > Initial boot:   [ ]
>> > Detect network card:[ ]
>> > Configure network:  [ ]
>> > Detect media:   [ ]
>> > Load installer modules: [ ]
>> > Clock/timezone setup:   [ ]
>> > User/password setup:[ ]
>> > Detect hard drives: [ ]
>> > Partition hard drives:  [ ]
>> > Install base system:[ ]
>> > Install tasks:  [ ]
>> > Install boot loader:[ ]
>> > Overall install:[ ]
>>
>> You did not provide useful information about the installation, so there is
>> no way to debug your situation.
>>
>> You should provide the installer log files (to be found in
>> /var/log/installer).
>> Sent them compressed to this bugreport.
>>
>> I ran a test installation of Debian 11 with MATE, and everything seems to
>> work
>> fine so far...
>>
>>
>> Holger
>>
>>
>>
>>
>> --
>> Holger Wansing 
>> PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
>>
>

Bug#1002921: Log Files

[D.J.J. Ring, Jr.]

Further to my bug report.

Installation detects my sound card but no screen reader present. System
inaccessible, only root can run MATE. User can only access CLI.

REGARDS,

David

-- Forwarded message -
From: David J. J. Ring, Jr. 
Date: Thu, Dec 30, 2021, 18:03
Subject: Log Files
To: David JJ Ring Jr 


Log  files
[  1838.994] 
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[  1838.994] Build Operating System: linux Debian
[  1838.994] Current Operating System: Linux debian 5.10.0-10-amd64 #1 SMP 
Debian 5.10.84-1 (2021-12-08) x86_64
[  1838.994] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-10-amd64 
root=UUID=2bb51d3e-ddb2-4a56-bf34-52e828bf8fe0 ro quiet
[  1838.994] Build Date: 16 December 2021  05:08:23PM
[  1838.994] xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support) 
[  1838.994] Current version of pixman: 0.40.0
[  1838.994]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  1838.994] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1838.994] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 30 17:09:15 
2021
[  1838.995] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1838.995] (==) No Layout section.  Using the first Screen section.
[  1838.995] (==) No screen section available. Using defaults.
[  1838.995] (**) |-->Screen "Default Screen Section" (0)
[  1838.995] (**) |   |-->Monitor ""
[  1838.995] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  1838.995] (==) Automatically adding devices
[  1838.995] (==) Automatically enabling devices
[  1838.995] (==) Automatically adding GPU devices
[  1838.995] (==) Max clients allowed: 256, resource mask: 0x1f
[  1838.995] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  1838.995]Entry deleted from font path.
[  1838.995] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[  1838.995] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1838.995] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[  1838.995] (II) Loader magic: 0x561e372abe40
[  1838.995] (II) Module ABI versions:
[  1838.995]X.Org ANSI C Emulation: 0.4
[  1838.995]X.Org Video Driver: 24.1
[  1838.995]X.Org XInput driver : 24.1
[  1838.995]X.Org Server Extension : 10.0
[  1838.996] (++) using VT number 7

[  1838.996] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[  1838.996] (II) xfree86: Adding drm device (/dev/dri/card0)
[  1839.009] (--) PCI:*(0@0:2:0) 8086:1616:8086:2010 rev 9, Mem @ 
0xc000/16777216, 0xa000/536870912, I/O @ 0x4000/64, BIOS @ 
0x/131072
[  1839.009] (II) LoadModule: "glx"
[  1839.009] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1839.010] (II) Module glx: vendor="X.Org Foundation"
[  1839.010]compiled for 1.20.11, module version = 1.0.0
[  1839.010]ABI class: X.Org Server Extension, version 10.0
[  1839.010] (==) Matched modesetting as autoconfigured driver 0
[  1839.010] (==) Matched fbdev as autoconfigured driver 1
[  1839.010] (==) Matched vesa as autoconfigured driver 2
[  1839.010] (==) Assigned the driver to the xf86ConfigLayout
[  1839.010] (II) LoadModule: "modesetting"
[  1839.010] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1839.010] (II) Module modesetting: vendor="X.Org Foundation"
[  1839.010]compiled for 1.20.11, module version = 1.20.11
[  1839.010]Module class: X.Org Video Driver
[  1839.010]ABI class: X.Org Video Driver, version 24.1
[  1839.010] (II) LoadModule: "fbdev"
[  1839.010] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[  1839.010] (II) Module fbdev: vendor="X.Org Foundation"
[  1839.010]compiled for 1.20.0, module version = 0.5.0
[  1839.010]Module class: X.Org Video Driver
[  1839.010]ABI class: X.Org Video Driver, version 24.0
[  1839.010] (II) LoadModule: "vesa"
[  1839.010] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[  1839.010] (II) Module vesa: vendor="X.Org Foundation"
[  1839.010]compiled for 1.20.9, module version = 2.5.0
[  1839.010]Module class: X.Org Video Driver
[  1839.010]ABI class: X.Org Video Driver, version 24.1
[  1839.010] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  1839.010] (II) FBDEV: driver for framebuffer: fbdev
[  1839.010] (II) VESA: driver for VESA chipsets: vesa
[  1839.023] (II) modeset(0): 

Bug#1002921: Xlog

[D.J.J. Ring, Jr.]

Further to my bug report

-- Forwarded message -
From: David J. J. Ring, Jr. 
Date: Thu, Dec 30, 2021, 18:13
Subject: Xlog
To: David JJ Ring Jr 
[  5570.481] 
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[  5570.486] Build Operating System: linux Debian
[  5570.488] Current Operating System: Linux debian 5.10.0-10-amd64 #1 SMP 
Debian 5.10.84-1 (2021-12-08) x86_64
[  5570.488] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-10-amd64 
root=UUID=2bb51d3e-ddb2-4a56-bf34-52e828bf8fe0 ro quiet
[  5570.492] Build Date: 16 December 2021  05:08:23PM
[  5570.493] xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support) 
[  5570.495] Current version of pixman: 0.40.0
[  5570.499]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  5570.499] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  5570.506] (==) Log file: "/home/djringjr/.local/share/xorg/Xorg.1.log", 
Time: Thu Dec 30 18:11:26 2021
[  5570.507] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  5570.508] (==) No Layout section.  Using the first Screen section.
[  5570.508] (==) No screen section available. Using defaults.
[  5570.508] (**) |-->Screen "Default Screen Section" (0)
[  5570.508] (**) |   |-->Monitor ""
[  5570.508] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  5570.508] (==) Automatically adding devices
[  5570.508] (==) Automatically enabling devices
[  5570.508] (==) Automatically adding GPU devices
[  5570.508] (==) Max clients allowed: 256, resource mask: 0x1f
[  5570.508] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  5570.508]Entry deleted from font path.
[  5570.508] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[  5570.508] (==) ModulePath set to "/usr/lib/xorg/modules"
[  5570.508] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[  5570.508] (II) Loader magic: 0x55ae00bf4e40
[  5570.508] (II) Module ABI versions:
[  5570.508]X.Org ANSI C Emulation: 0.4
[  5570.508]X.Org Video Driver: 24.1
[  5570.508]X.Org XInput driver : 24.1
[  5570.508]X.Org Server Extension : 10.0
[  5570.508] (++) using VT number 2

[  5570.510] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_311
[  5570.511] (II) xfree86: Adding drm device (/dev/dri/card0)
[  5570.511] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 13 paused 0
[  5570.513] (--) PCI:*(0@0:2:0) 8086:1616:8086:2010 rev 9, Mem @ 
0xc000/16777216, 0xa000/536870912, I/O @ 0x4000/64, BIOS @ 
0x/131072
[  5570.513] (II) LoadModule: "glx"
[  5570.513] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  5570.514] (II) Module glx: vendor="X.Org Foundation"
[  5570.514]compiled for 1.20.11, module version = 1.0.0
[  5570.514]ABI class: X.Org Server Extension, version 10.0
[  5570.514] (==) Matched modesetting as autoconfigured driver 0
[  5570.514] (==) Matched fbdev as autoconfigured driver 1
[  5570.514] (==) Matched vesa as autoconfigured driver 2
[  5570.514] (==) Assigned the driver to the xf86ConfigLayout
[  5570.514] (II) LoadModule: "modesetting"
[  5570.514] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  5570.514] (II) Module modesetting: vendor="X.Org Foundation"
[  5570.514]compiled for 1.20.11, module version = 1.20.11
[  5570.514]Module class: X.Org Video Driver
[  5570.514]ABI class: X.Org Video Driver, version 24.1
[  5570.514] (II) LoadModule: "fbdev"
[  5570.514] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[  5570.514] (II) Module fbdev: vendor="X.Org Foundation"
[  5570.514]compiled for 1.20.0, module version = 0.5.0
[  5570.514]Module class: X.Org Video Driver
[  5570.514]ABI class: X.Org Video Driver, version 24.0
[  5570.514] (II) LoadModule: "vesa"
[  5570.514] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[  5570.515] (II) Module vesa: vendor="X.Org Foundation"
[  5570.515]compiled for 1.20.9, module version = 2.5.0
[  5570.515]Module class: X.Org Video Driver
[  5570.515]ABI class: X.Org Video Driver, version 24.1
[  5570.515] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[  5570.515] (II) FBDEV: driver for framebuffer: fbdev
[  5570.515] (II) VESA: driver for VESA chipsets: vesa
[  5570.515] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not 
permitted)
[  5570.515] (II) modeset(0): using drv 

Bug#931483: konsole: Konsole will not launch from mate-panel or from KDE Application Launcher.

[D.J.J. Ring, Jr.]

Maximiliano, konsole is again working!

Close this!

David

On Fri, Aug 16, 2019, 10:37 Maximiliano Curia 
wrote:

> Control: severity -1 important
> Control: tag -1 moreinfo unreproducible
>
> ¡Hola David!
>
> El 2019-07-05 a las 21:19 -0400, David J. Ring escribió:
> > Package: konsole
> > Version: 4:18.04.0-1
> > Severity: grave
> > Justification: renders package unusable
>
> > Dear Maintainer,
>
> > konsole will not launch from mate-panel shortcut or from KDE Application
> menu.
>
> > konsole WILL launch from mate-terminal and will subsequently open both
> new windows and new tabs.
>
> > konsole is unusable because of the problem, but I do not know if the
> problem is konsole or the KDE launcher or mate-panel.
>
> I'm not able to reproduce the issue as reported, can you check running
> konsole
> from a different terminal and see what's kind of errors are you getting
> (it
> might also be useful to check your ~/.xsession-errors)?
>
> Happy hacking,
> --
> A computer scientist is someone who, when told to "Go to Hell,"
> sees the "go to," rather than the destination, as harmful.
> Saludos /\/\ /\ >< `/
>

Bug#594506: konsole crashed (signal 11)

[D.J.J. Ring, Jr.]

It must be.  Google is having problems, their email is all being archived
instead of being sent to inbox.

Sorry to bother you. No offense was meant.

Thank you for your help!

DR

On Thu, Jul 11, 2019, 19:03 Bernhard Übelacker 
wrote:

> Hello David,
> that was not the link I sent in my mail,
> I sent a plain link to bugs.debian.org.
> Maybe you are viewing my mail via google webmail client,
> and that is adding something unwanted?
>
> Kind regards,
> Bernhard
>
>

Bug#594506: konsole crashed (signal 11)

[D.J.J. Ring, Jr.]

Bernhard,

For some reason, I'm getting server error when I click on this link.

 subscribe

to
this bug.

Because it gives a hyperlink to
https://mail.google.com/a/arrl.net/mail/?view=cm=1=1=931844-subscr...@bugs.debian.org

Which is not supposed to  be!

An error results:

Server error

Sorry, you've reached a login page for a domain that isn't using G Suite.
Please check the web address and try again. Learn more



The REPLY hyperlink has the same problem.


Best regards


David



On Thu, Jul 11, 2019 at 5:53 AM Bernhard Übelacker 
wrote:

> Hello David,
> I could find an issue with konsole freezing
> and reported it in this bug:
> https://bugs.debian.org/931844
>
> Maybe you want to have a look if you find your issue there.
>
> Kind regards,
> Bernhard
>
>
>
>

Bug#594506: konsole crashed (signal 11)

[D.J.J. Ring, Jr.]

Thanks.

So many bugs, so little time!

Have fun!

DR

On Thu, Jul 11, 2019 at 5:53 AM Bernhard Übelacker 
wrote:

> Hello David,
> I could find an issue with konsole freezing
> and reported it in this bug:
> https://bugs.debian.org/931844
>
> Maybe you want to have a look if you find your issue there.
>
> Kind regards,
> Bernhard
>
>
>
>