Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #208258

Re: next amd64 stretch problem

From Curt <curty@free.fr>
Newsgroups linux.debian.user
Subject Re: next amd64 stretch problem
Date 2019-05-06 09:40 +0200
Message-ID <xUGo9-3oP-1@gated-at.bofh.it> (permalink)
References <xUAiK-84X-5@gated-at.bofh.it>
Organization Unorganized

Show all headers | View raw


On 2019-05-06, Gene Heskett <gheskett@shentel.net> wrote:
> Greetings all;
>
> I have only one, very weak sound, from kmails new mail beep.  Down about 
> 20 db from what I'm used to hearing.

xset b 100?

Does that set the bell/beep volume at a hundred percent?

The man page says

 b
 ...
 If only one numerical parameter is given, the bell volume will be set to that
 value, as a percentage of its maximum.

A second numerical value would set the pitch in hertz (unrelated to car rentals).

A third would set the duration in milliseconds.

Whether this is the way to skin this cat I don't know, but something to try maybe.
I see in another of your emails that you've found speaker-test.

Here are my bell values from 'xset -q':

 bell percent:  50    bell pitch:  400    bell duration:  100

Good luck.

> Everything else is muted.  And I can't find the speaker-test utility in 
> the repo's to even begin to troubleshoot, so whats the next step?
>
> Thanks all;
>
> Cheers, Gene Heskett


-- 
The boys at first were very polite about my medals and asked me what I had done
to get them. I showed them the papers, which were written in very beautiful
language and full of fratellanza and abnegazione, but which really said, with
the adjectives removed, that I had been given the medals because I was 
an American. - "Another Country"

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

next amd64 stretch problem Gene Heskett <gheskett@shentel.net> - 2019-05-06 03:10 +0200
  Re: next amd64 stretch problem David Wright <deblis@lionunicorn.co.uk> - 2019-05-06 07:00 +0200
    Re: next amd64 stretch problem Gene Heskett <gheskett@shentel.net> - 2019-05-06 08:50 +0200
      Re: next amd64 stretch problem Jonas Smedegaard <jonas@jones.dk> - 2019-05-06 10:10 +0200
        Re: next amd64 stretch problem Gene Heskett <gheskett@shentel.net> - 2019-05-06 17:10 +0200
          Re: next amd64 stretch problem Gene Heskett <gheskett@shentel.net> - 2019-05-06 17:50 +0200
          Re: next amd64 stretch problem Jonas Smedegaard <jonas@jones.dk> - 2019-05-06 17:50 +0200
            Re: next amd64 stretch problem Gene Heskett <gheskett@shentel.net> - 2019-05-06 19:20 +0200
              Re: next amd64 stretch problem Jan Claeys <lists@janc.be> - 2019-05-09 20:40 +0200
                Re: next amd64 stretch problem Brian <ad44@cityscape.co.uk> - 2019-05-09 22:10 +0200
  Re: next amd64 stretch problem Curt <curty@free.fr> - 2019-05-06 09:40 +0200
    Re: next amd64 stretch problem Gene Heskett <gheskett@shentel.net> - 2019-05-06 17:20 +0200
  Re: next amd64 stretch problem Gene Heskett <gheskett@shentel.net> - 2019-05-06 20:10 +0200
    Re: next amd64 stretch problem ghe <ghe@slsware.net> - 2019-05-06 20:40 +0200
      Re: next amd64 stretch problem Gene Heskett <gheskett@shentel.net> - 2019-05-06 23:50 +0200

csiph-web