30 Jan
2014
30 Jan
'14
5:38 p.m.
I've seen
this before, when logging in with the same account
between two systems that have different sound hardware.
Try terminating kmix, delete the two kmix* rc files, then start
kmix.
Good thought. I killed it, removed the
.trinity/share/config/kmixrc and
restarted. No change and no regeneration of kmixrc. I'll keep
poking at the
underlying sound system to see if there is something there causing
the issue. 
31 Jan
31 Jan
8:50 a.m.
New subject: [trinity-devel] kmix/kmixer cannot see arts running
On 01/30/2014 07:38 PM, Darrell Anderson wrote:
After deleting the two kmixrc* files, the default
should be to
autostart. If kmix is not autostarting, then try manually starting
from the command line.
Oh, it's autostarting every time - it just comes up with a big red X over it and
and it is dead as a doornail. Can't find any mixer, nothing..
--
David C. Rankin, J.D.,P.E.
1 Feb
1 Feb
12:22 p.m.
New subject: [trinity-devel] kmix/kmixer cannot see arts running
On 01/31/2014 10:50 AM, David C. Rankin wrote:
On 01/30/2014 07:38 PM, Darrell Anderson wrote:
Darrell,
I think my sound not working is a hal/nohal issue. I just opened a 3.5.13-sru
install with the in the exact same virtualbox environment and sound works
beautifully. The only difference is that install loads hal and R14 doesn't. Have
there been other sound problem with the nohal builds? I've attached my
perirpherals-hardware-sound setup for review. It is the exact same between
3.5.13-sru and R14.
--
David C. Rankin, J.D.,P.E.
After deleting the two kmixrc* files, the default
should be to
autostart. If kmix is not autostarting, then try manually starting
from the command line.
Oh, it's autostarting every time - it just comes up with a big red X over it and
and it is dead as a doornail. Can't find any mixer, nothing..
3949
days inactive
3950
days old
2 comments
2 participants
participants (2)
-
Darrell Anderson -
David C. Rankin