Gentoo Archives: gentoo-user

From: Paul Hartman <paul.hartman+gentoo@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Gentoo is the best linux distro
Date: Wed, 12 Sep 2012 22:42:48
Message-Id: CAEH5T2PbJpK6T+G2dMEkK-7Jj26hHun6ZdnJz5uWNCFF=1Sdow@mail.gmail.com
In Reply to: Re: [gentoo-user] Gentoo is the best linux distro by Michael Mol
1 On Wed, Sep 12, 2012 at 5:08 PM, Michael Mol <mikemol@×××××.com> wrote:
2 > On Wed, Sep 12, 2012 at 5:59 PM, Paul Hartman
3 > <paul.hartman+gentoo@×××××.com> wrote:
4 >>
5 >> On Wed, Sep 12, 2012 at 4:06 PM, Michael Mol <mikemol@×××××.com> wrote:
6 >> > On Wed, Sep 12, 2012 at 4:57 PM, Alan McKinnon <alan.mckinnon@×××××.com>
7 >> > wrote:
8 >> >>
9 >> >> On Wed, 12 Sep 2012 11:15:25 -0400
10 >> >> Michael Mol <mikemol@×××××.com> wrote:
11 >> >>
12 >> >> > On Wed, Sep 12, 2012 at 10:55 AM, Alan McKinnon
13 >> >> > <alan.mckinnon@×××××.com>wrote:
14 >> >> >
15 >> >> > > On Wed, 12 Sep 2012 16:00:34 +0200
16 >> >> > > Alex Schuster <wonko@×××××××××.org> wrote:
17 >> >> > >
18 >> >> > > > Michael Mol writes:
19 >> >> > > >
20 >> >> > > > > On Wed, Sep 12, 2012 at 9:33 AM, Neil Bothwick
21 >> >> > > > > <neil@××××××××××.uk <mailto:neil@××××××××××.uk>> wrote:
22 >> >> > > >
23 >> >> > > > > Instead we get, try USE="-*" :P
24 >> >> > > > >
25 >> >> > > > > "Try MAKEOPTS='-j1'"
26 >> >> > > >
27 >> >> > > > Which in fact often helps... especially for me, I am using
28 >> >> > > > MAKEOPTS="-j --load=4", and I often experience build problems
29 >> >> > > > that
30 >> >> > > > are not reproducible with a fixed number of jobs, regardless how
31 >> >> > > > large.
32 >> >> > >
33 >> >> > > Yes indeed, and that one is good advice.
34 >> >> > >
35 >> >> > > Not every Makefile out there is safe for -j > 1, so running it as
36 >> >> > > one job is valid debugging. It's the correct thing to do with weird
37 >> >> > > build failures as it tests if a specific condition is true or not.
38 >> >> > >
39 >> >> > >
40 >> >> > Yeah, except I've already gone that route, or otherwise ruled it out,
41 >> >> > before I ask. That's why it's grating. (Even more grating when I have
42 >> >> > to spend the time building a package again, just to convince someone
43 >> >> > that, no, it's not MAKEOPTS that's the problem.)
44 >> >> >
45 >> >> > It's like "Have you tried turning it off and back on again".
46 >> >>
47 >> >> I learned that one the hard way :-)
48 >> >>
49 >> >> Now when I submit support posts, I try emulate what bgo asks:
50 >> >>
51 >> >> 1. nature of problem
52 >> >> 2. what have I tried already
53 >> >> 3. steps to reproduce
54 >> >> 4. result gotten
55 >> >> 5. expected result
56 >> >> 6. relevant config files and settings
57 >> >>
58 >> >> Tends to weed out a lot of the silly auto-bot style answers
59 >> >>
60 >> >
61 >> > I'm going through one on launchpad right now where I indicated that I
62 >> > couldn't get beeps out of xterm, but I could get sound from
63 >> > sound-emitting
64 >> > websites. (Trying to get x11 bell to function via PulseAudio via work
65 >> > laptop)
66 >> >
67 >> > First response? "Needs information: Can you get sound from other sound
68 >> > apps?"
69 >> >
70 >> > #pulseaudio simply ignored me. And googling turns up that Lennart hates
71 >> > the
72 >> > X server as being a funnel for sound events. I was physically twitching
73 >> > by
74 >> > the time I gave up...
75 >>
76 >> It is not a feature I use, but... I think you need the x11-bell module
77 >> loaded in your PA config, and point it to a valid sound file
78 >> containing your preferred beep noise. Maybe then also run "xset b on"
79 >> in X... maybe some "xset b something" to set volume of the beep as
80 >> well, and hope your desktop environment doesn't override your hard
81 >> work with its own sound preferences. :)
82 >
83 >
84 > xset is set properly, x11-bell module is loaded...but it's entirely unclear
85 > how to get it pointed at a valid sample file. Even PulseAudio's "Perfect
86 > Setup" page glosses over it.
87
88 /etc/pulse/default.pa on gentoo contains this line (commented out):
89 load-sample-lazy x11-bell /usr/share/sounds/gtk-events/activate.wav
90
91 I'm assuming that creates a sample called x11-bell, then I think later
92 on when you load the module, you would reference it like:
93 load-module module-x11-bell sample=x11-bell
94
95 then hopefully your xset commands might actually produce something
96 audible. Cross your fingers, etc. :)