On 6/17/20 11:40 PM, Joe Zeff wrote:
On 06/11/2020 10:15 PM, Tim via users wrote:
Try recording yourself to a file (e.g. use Audacity). Does it sound
clear? If not, check your mike gain isn't wound up excessively high,
wiggle leads and connectors, see if you can find a fault with your mic
that
On 2020-06-18 15:07, Samuel Sieb wrote:
> On 6/17/20 11:40 PM, Joe Zeff wrote:
>> On 06/11/2020 10:15 PM, Tim via users wrote:
>>> Try recording yourself to a file (e.g. use Audacity). Does it sound
>>> clear? If not, check your mike gain isn't wound up excessively high,
>>> wiggle leads and conn
On 06/18/2020 01:37 AM, Ed Greshko wrote:
I found that would happen if one has the input level set too high in
pavcontrol. What is shown in audacity doesn't
appear to reflect the settings in audacity.
I have pavcontrol set to 40%~45% and it sounds fine. Well, except for the fact
that the lap
On 2020-06-18 15:46, Joe Zeff wrote:
> On 06/18/2020 01:37 AM, Ed Greshko wrote:
>> I found that would happen if one has the input level set too high in
>> pavcontrol. What is shown in audacity doesn't
>> appear to reflect the settings in audacity.
>>
>> I have pavcontrol set to 40%~45% and it so
On 06/18/2020 02:24 AM, Ed Greshko wrote:
So, you see no green bars to the right of the mic icon?
Note, that if you make changes to the "recording device" you will need to "start
monitoring" again as changes
cause the monitor to turn off.
Got it in one. It's now 2:35 AM, I finally finished c
On 2020-06-18 16:34, Joe Zeff wrote:
> On 06/18/2020 02:24 AM, Ed Greshko wrote:
>> So, you see no green bars to the right of the mic icon?
>>
>> Note, that if you make changes to the "recording device" you will need to
>> "start monitoring" again as changes
>> cause the monitor to turn off.
>
> G
On Thu, Jun 18, 2020 at 3:37 AM Ed Greshko wrote:
>
> On 2020-06-18 15:07, Samuel Sieb wrote:
> > On 6/17/20 11:40 PM, Joe Zeff wrote:
> >> On 06/11/2020 10:15 PM, Tim via users wrote:
> >>> Try recording yourself to a file (e.g. use Audacity). Does it sound
> >>> clear? If not, check your mike
On Thu, 2020-06-18 at 00:40 -0600, Joe Zeff wrote:
> I've installed Audacity on my laptop and tried to make a recording.
> I've got the internal mike set at the default setting, and when I
> test it in the Settings of Zoom, it looks like it's working, but I
> can't get any response from Audacity
I was trying to run through the tutorial here:
https://allan-blanchard.fr/publis/frama-c-wp-tutorial-en.pdf
The first example on page 15 & 16 fails with:
[wp] Running WP plugin...
[wp] User Error: Prover 'alt-ergo' not found in why3.conf
I couldn't get any further. What I tried was:
-
On Thu, Jun 18, 2020 at 01:46:20AM -0600, Joe Zeff wrote:
> On 06/18/2020 01:37 AM, Ed Greshko wrote:
> >I found that would happen if one has the input level set too high in
> >pavcontrol. What is shown in audacity doesn't
> >appear to reflect the settings in audacity.
> >
> >I have pavcontrol se
On 2020-06-18 19:31, Richard W.M. Jones wrote:
> I was trying to run through the tutorial here:
>
> https://allan-blanchard.fr/publis/frama-c-wp-tutorial-en.pdf
>
> The first example on page 15 & 16 fails with:
>
> [wp] Running WP plugin...
> [wp] User Error: Prover 'alt-ergo' not found in wh
Hi, I'm running F32 on a hi-dpi screen, with kde+wayland.
I find I get good results by going to font settings, and choosing Force
dpi, and selecting 120 rather than the default 96. This produces a warning
that the recommended approach is to instead use scaling. If I try scaling
the results look
On Thu, Jun 18, 2020 at 12:31:44PM +0100, Richard W.M. Jones wrote:
> - Run /usr/lib64/why3/commands/why3config by hand (why isn't it in
>/usr/bin?), which creates $HOME/.why3.conf
So the reason it's not in /usr/bin is because you have to run it like
this:
$ why3 config --detect
Found prover
I constantly get this nonsense in my logwatch mail:
> **Unmatched Entries**
> crond: pam_systemd(crond:session): Failed to create session: File exists:
> 1 Time(s)
That apparently corresponds to this entry in /var/log/secure:
Jun 16 08:42:01 tomh crond[25783]: pam_systemd(crond:session): Fa
On Thu, 2020-06-18 at 08:57 -0400, Tom Horsley wrote:
> The fetchmail job runs every minute. Does this happen when the
> previous fetchmail cron job hasn't finished yet?
As a simple test, try longer than 1 minute between fetchmail runs.
--
uname -rsvp
Linux 3.10.0-1127.10.1.el7.x86_64 #1 SMP
On Thu, Jun 18, 2020 at 5:31 AM Richard W.M. Jones wrote:
> I was trying to run through the tutorial here:
>
> https://allan-blanchard.fr/publis/frama-c-wp-tutorial-en.pdf
>
> The first example on page 15 & 16 fails with:
>
> [wp] Running WP plugin...
> [wp] User Error: Prover 'alt-ergo' not
On 06/18/2020 02:46 AM, Ed Greshko wrote:
Well, there should be drop down box with a mic icon next to, probably ALSA. It
seems it would then
be set to mono. Try changing to Stereo.
It's set to Stereo. Changing it to Mono before starting to monitor
doesn't help.
___
On Thu, Jun 18, 2020 at 9:01 AM Jerry James wrote:
> I see this in the log:
>
> [wp] User Error: Prover 'alt-ergo' not found in why3.conf
>
> which is a lie. Prover alt-ergo is most definitely listed in
> why3.conf. I'll debug this. Stand by.
Run "why3 config --full-config", then start frama-c
On 06/18/2020 01:07 AM, Samuel Sieb wrote:
The interface is a little confusing and the toolbars can be moved
around, so I'll assume the default layout that I have is the same as yours.
Mine is different, but not so much that I can't work with your instructions.
To the right of the play contr
On 2020-06-19 05:07, Joe Zeff wrote:
> On 06/18/2020 02:46 AM, Ed Greshko wrote:
>> Well, there should be drop down box with a mic icon next to, probably ALSA.
>> It seems it would then
>> be set to mono. Try changing to Stereo.
>
> It's set to Stereo. Changing it to Mono before starting to mon
On 6/18/20 2:14 PM, Joe Zeff wrote:
On 06/18/2020 01:07 AM, Samuel Sieb wrote:
The interface is a little confusing and the toolbars can be moved
around, so I'll assume the default layout that I have is the same as
yours.
Mine is different, but not so much that I can't work with your
instru
On 06/18/2020 03:37 PM, Ed Greshko wrote:
Well, if your laptop has only a single microphone you will get only one green
bar no matter the setting.
So, if you see a fluctuating green bar can you now record/play-back?
I didn't then, but things have changed, as you'll see in a reply to a
later
On 06/18/2020 03:39 PM, Samuel Sieb wrote:
I see that mine also doesn't change from ALSA, but if I click on it, I
get a list of options: default, sysdefault, pulse, and "HDA Intel...".
Yes. At first I couldn't bring up that list, but it eventually came up
and I set it to sysdefault, which is
On Thu, 2020-06-18 at 15:50 -0600, Joe Zeff wrote:
> That brought up the green bars, and Recording actually worked.
> Consider this thread Solved and Closed!
But you didn't tell us how good/bad it sounded. Enquiring minds want
to know.
--
uname -rsvp
Linux 3.10.0-1127.10.1.el7.x86_64 #1 SMP
On 2020-06-19 11:43, Tim via users wrote:
> On Thu, 2020-06-18 at 15:50 -0600, Joe Zeff wrote:
>> That brought up the green bars, and Recording actually worked.
>> Consider this thread Solved and Closed!
> But you didn't tell us how good/bad it sounded. Enquiring minds want
> to know.
I'm in the
On 06/18/2020 09:43 PM, Tim via users wrote:
On Thu, 2020-06-18 at 15:50 -0600, Joe Zeff wrote:
That brought up the green bars, and Recording actually worked.
Consider this thread Solved and Closed!
But you didn't tell us how good/bad it sounded. Enquiring minds want
to know.
It sounded
On 06/18/2020 10:05 PM, Ed Greshko wrote:
I'm in the camp of "If the OP is happy, good enough".
If you consider "not my equipment" happy, them I am.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@li
I have never seen this before.I just updated, but have not rebooted
( I am in Rawhide )
[david@localhost ~]$ sudo flatpak update
[sudo] password for david:
Looking for updates…
Login required remote fedora (realm https://registry.fedoraproject.org/
)
User:
On 18/6/20 10:35 pm, Neal Becker wrote:
Hi, I'm running F32 on a hi-dpi screen, with kde+wayland.
I find I get good results by going to font settings, and choosing
Force dpi, and selecting 120 rather than the default 96. This
produces a warning that the recommended approach is to instead use
29 matches
Mail list logo
