Re: slint release install findings

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

 



Jude DaShiell here again, if memory serves this didn't happen in rc3 it was a while ago I used that so I probably ought to check that to be sure.

On Wed, 3 Jan 2018, Linux for blind general discussion wrote:

Date: Wed, 3 Jan 2018 12:49:08
From: Linux for blind general discussion <blinux-list@xxxxxxxxxx>
To: Linux for blind general discussion <blinux-list@xxxxxxxxxx>
Subject: Re: slint release install findings

Hello Jude,

Did this issue occur since RC3 or since the final release?

I ask because I see this in the ChangeLog, cf. http://slackware.uk/slint/x86_64/slint-14.2.1/ChangeLog.txt
cut here
Monday 27 November 2017
Note: this batch of updates is the last applied in slint64-14.2.1RC3. espeak-1.48.04-x86_64-4slint.txz: Rebuilt.
 Use portaudio as backend to allow using orca in parallel without
 having to start pulseaudio system wide.
portaudio-v19-x86_64-2slint: Re-added and rebuilt.
 Dependency of espeak.
cut here

other than that the espeak version didn't change.

If that was also the case in RC3, I could rebuild an espeak
package with pulseaudio as backend that you could test.

I would also be curious to know if this issue occurs for
other users.

Greetings,

Didier

Le 03/01/2018 ? 17:56, Linux for blind general discussion a ?crit?:
This is Jude here.? I haven't tried most yet and will do that next. This problem happens with or without usb speakers attached, so the usb speakers are not at fault here.? Had speakup for console got a version change that hadn't happened in the release candidates?? If that did happen, a possible regression in speakup could be the culprit.

On Wed, 3 Jan 2018, Linux for blind general discussion wrote:

Date: Wed, 3 Jan 2018 04:23:10
From: Linux for blind general discussion <blinux-list@xxxxxxxxxx>
To: blinux-list@xxxxxxxxxx
Subject: Re: slint release install findings

Hello,

Could you please indicate your first name when posting? I am not
comfortable speaking to anonymous and this list don't preserve senders'
address.

You can increase swap, but I doubt that changes something as the system
should need less RAM in console mode that in graphical mode, at least if
you? use startx to start mate.

I will try to investigate on the sound issue, however I don't have USB
speakers to try.

Does the same issue occur if you use another page like most instead of
less?

About the installation logs, they go in /dev/tty4, that you can hear
during installation typing Alt+F4

However, this is not very useful as you can't scroll.

This is set in /etc/syslog.conf in the installer, so could be changed
there.

When the system is running the logs go partly in /var/log/syslog, partly
in /var/log/messages, both are text files readable by root.

You can also type as root dmesg|less or dmesg|most to check the messages
from starting the system.

Thanks for your reports so far.

Greetings,

Didier

Le 03/01/2018 ? 08:09, Linux for blind general discussion a ?crit?:
I just had an idea and it will take another slint install to test it. Could swap partition size be under-stated for screen readers?? I have a root partition of 1996GB and a linux-swap partition of 4GB and available memory on the machine ram is 1GB.? I'll try taking the swap partition size up and see if this problem goes away.

On Wed, 3 Jan 2018, Linux for blind general discussion wrote:

Date: Wed, 3 Jan 2018 02:03:31
From: Linux for blind general discussion <blinux-list@xxxxxxxxxx>
To: Linux for blind general discussion <blinux-list@xxxxxxxxxx>
Subject: Re: slint release install findings

When I ran the slint release earlier it was on only one set of speakers.
Adding the usb speaker set to the system had no effect on speech output quality.

On Wed, 3 Jan 2018, Linux for blind general discussion wrote:

?Date: Wed, 3 Jan 2018 01:34:10
?From: Linux for blind general discussion <blinux-list@xxxxxxxxxx>
?To: blinux-list@xxxxxxxxxx
?Subject: slint release install findings

?speech in console mode with mate as default graphical user interface
?dstarts sounding choked shortly after login.? Speech in graphical mode
?once startx gets run has no such problems.? To reproduce just run less on
?a document that's a few screens long and listen to the speech.? flushing
?speakup has very temporary improvement of speech before speech goes back
?to sounding choked.
?One thing that may be useful for slint in future is to have ability to
?preserve installation logs which also detect hard? I have two sets of
?speakers on this computer and will try disconnecting usb speakers and see
?if that helps speakup work better.


?--

?_______________________________________________
?Blinux-list mailing list
?Blinux-list@xxxxxxxxxx
?https://www.redhat.com/mailman/listinfo/blinux-list






_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list


_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list

--

_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list



[Index of Archives]     [Linux Speakup]     [Fedora]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]