3 Mar
2012
3 Mar
'12
4:09 p.m.
Hello,
does someone tried to install Trinity on Ubuntu Precise?
Today I upgraded my system from Oneiric to Precise due to new hardware that did not work
properly on Oneiric.
Everything works fine in Precise, except the sound. While I still have sound in gdm or in
unity DE I don't hear anything in Trinity.
Since the sound works already in gdm I think it should also work in Trinity if Trinity
would not touch it at startup. Unfortunately Trinity does. Shortly after the start the
sound gets somehow deactivated or invisible muted (in alsamixer everything looks fine,
volume is up not muted). However, I don't hear anything and I don't get any error
messages). What can I do?
Regards,
Stefan
3 Mar
3 Mar
4:45 p.m.
New subject: [trinity-users] First experience with Ubuntu Precise
On Saturday 03 March 2012 11:09:23 am Stefan Endrullis wrote:
Hello,
does someone tried to install Trinity on Ubuntu Precise?
Today I upgraded my system from Oneiric to Precise due to new hardware that did not work
properly on Oneiric.
Everything works fine in Precise, except the sound. While I still have sound in gdm or
in unity DE I don't hear anything in Trinity.
Since the sound works already in gdm I think it should also work in Trinity if Trinity
would not touch it at startup. Unfortunately Trinity does. Shortly after the start the
sound gets somehow deactivated or invisible muted (in alsamixer everything looks fine,
volume is up not muted). However, I don't hear anything and I don't get any error
messages). What can I do?
The first thing I'd recommend is to launch Kmix and see if it agrees with alsamixer.
If it does, go into Control Cente -> Sound & Multimedia -> Sound System. Try to
disable it (untick "Enable the sound system", hit apply) and see if it works. If
not, then re-enable the Sound System and click the Hardware tab. Check the setting for
"Select the audio device". This is normally set to "Autodetect", but
it may be worth while to specify one specificly. Since you're using ALSA, that would
be the first one to try, followed by the others if you have any listed.
The "last resort" thing I'd recommend is to use either apt-get or Synaptic
to purge/completely remove ALSA, then reinstall it.
--
Kris Gamrat
4 Mar
4 Mar
8:21 a.m.
New subject: [trinity-users] First experience with Ubuntu Precise
Am 03.03.2012 17:45, schrieb Kristopher John Gamrat:
On Saturday 03 March 2012 11:09:23 am Stefan Endrullis
wrote:
Thanks for your help. Unfortunately, it did not help. I also tried to remove or disable
everything that could conflict with the sound system. I removed pulseaudio and arts via
aptitude, removed all autostart applications from /opt/trinity/share/autostart and
~/.trinity/Autostart, except kdesktop and panel, and deleted
.trinity/share/config/ksmserverrc to start with a new and clean session. However, the
problem stays the same. When KDE session manager (ksmserver) starts up my sound gets
deactivated.
As workaround I'm currently starting openbox instead of TDE. In openbox I can run
kdesktop, kicker, khotkeys without issues. Sound works. Only the start of ksmserver
breaks the sound system, so I skip this one.
Regards,
Stefan
Hello,
does someone tried to install Trinity on Ubuntu Precise?
Today I upgraded my system from Oneiric to Precise due to new hardware that did not work
properly on Oneiric.
Everything works fine in Precise, except the sound. While I still have sound in gdm or
in unity DE I don't hear anything in Trinity.
Since the sound works already in gdm I think it should also work in Trinity if Trinity
would not touch it at startup. Unfortunately Trinity does. Shortly after the start the
sound gets somehow deactivated or invisible muted (in alsamixer everything looks fine,
volume is up not muted). However, I don't hear anything and I don't get any error
messages). What can I do?
The first thing I'd recommend is to launch Kmix and see if it agrees with alsamixer.
If it does, go into Control Cente -> Sound& Multimedia -> Sound System. Try
to disable it (untick "Enable the sound system", hit apply) and see if it works.
If not, then re-enable the Sound System and click the Hardware tab. Check the setting for
"Select the audio device". This is normally set to "Autodetect", but
it may be worth while to specify one specificly. Since you're using ALSA, that would
be the first one to try, followed by the others if you have any listed.
The "last resort" thing I'd recommend is to use either apt-get or Synaptic
to purge/completely remove ALSA, then reinstall it. 
10:32 a.m.
New subject: [trinity-users] First experience with Ubuntu Precise
Hi,
As a workaround, you can try to use OSSV4 instead of alsa. With TDE,
only OSSV4 tools (ossxmix is the mixer interface you can use in any
environment) have the control on OSSV4.
Link to configuration :
http://www.opensound.com/wiki/index.php/Configuring_Applications_for_OSSv4
And the sound is better than it is with ALSA.
I presume OSSV4 should be in repositories of precise directly as they
are in Mint. I recommend to install the DKMS packages if there are some,
that way you can configure your sound much further and better.
If you need some more explanation look at the OSS wiki page,
http://www.opensound.com/wiki/index.php/Main_Page
or ask at the OSS Linux forum if you are locked :
http://www.opensound.com/forum/viewforum.php?f=3&sid=2409e5285da9341bc7…
Of course, if I can first answer, just ask me, I'm not using precise,
but I guess that it's quite near from Mint 12 and oneiric ;)
See yu
Pierre
Le dimanche 04 mars 2012 à 09:21 +0100, Stefan Endrullis a écrit :
Am 03.03.2012 17:45, schrieb Kristopher John Gamrat:
On Saturday 03 March 2012 11:09:23 am Stefan
Endrullis wrote:
Thanks for your help. Unfortunately, it did not help. I also tried to remove or disable
everything that could conflict with the sound system. I removed pulseaudio and arts via
aptitude, removed all autostart applications from /opt/trinity/share/autostart and
~/.trinity/Autostart, except kdesktop and panel, and deleted
.trinity/share/config/ksmserverrc to start with a new and clean session. However, the
problem stays the same. When KDE session manager (ksmserver) starts up my sound gets
deactivated.
As workaround I'm currently starting openbox instead of TDE. In openbox I can run
kdesktop, kicker, khotkeys without issues. Sound works. Only the start of ksmserver
breaks the sound system, so I skip this one.
Regards,
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hello,
does someone tried to install Trinity on Ubuntu Precise?
Today I upgraded my system from Oneiric to Precise due to new hardware that did not work
properly on Oneiric.
Everything works fine in Precise, except the sound. While I still have sound in gdm or
in unity DE I don't hear anything in Trinity.
Since the sound works already in gdm I think it should also work in Trinity if Trinity
would not touch it at startup. Unfortunately Trinity does. Shortly after the start the
sound gets somehow deactivated or invisible muted (in alsamixer everything looks fine,
volume is up not muted). However, I don't hear anything and I don't get any error
messages). What can I do?
The first thing I'd recommend is to launch Kmix and see if it agrees with alsamixer.
If it does, go into Control Cente -> Sound& Multimedia -> Sound System. Try
to disable it (untick "Enable the sound system", hit apply) and see if it works.
If not, then re-enable the Sound System and click the Hardware tab. Check the setting for
"Select the audio device". This is normally set to "Autodetect", but
it may be worth while to specify one specificly. Since you're using ALSA, that would
be the first one to try, followed by the others if you have any listed.
The "last resort" thing I'd recommend is to use either apt-get or Synaptic
to purge/completely remove ALSA, then reinstall it.
6 Mar
6 Mar
7:28 p.m.
New subject: [trinity-users] First experience with Ubuntu Precise
Hi,
I finally solved my sound problem, but I'm not sure which action did the trick. I can
only tell you that I removed arts and pulseaudio and deactivated the sound in kcontrol.
However, now it works.
Cheers,
Stefan
Am 04.03.2012 11:32, schrieb pierre.lag6633(a)free.fr:
Hi,
As a workaround, you can try to use OSSV4 instead of alsa. With TDE,
only OSSV4 tools (ossxmix is the mixer interface you can use in any
environment) have the control on OSSV4.
Link to configuration :
http://www.opensound.com/wiki/index.php/Configuring_Applications_for_OSSv4
And the sound is better than it is with ALSA.
I presume OSSV4 should be in repositories of precise directly as they
are in Mint. I recommend to install the DKMS packages if there are some,
that way you can configure your sound much further and better.
If you need some more explanation look at the OSS wiki page,
http://www.opensound.com/wiki/index.php/Main_Page
or ask at the OSS Linux forum if you are locked :
http://www.opensound.com/forum/viewforum.php?f=3&sid=2409e5285da9341bc7…
Of course, if I can first answer, just ask me, I'm not using precise,
but I guess that it's quite near from Mint 12 and oneiric ;)
See yu
Pierre
Le dimanche 04 mars 2012 à 09:21 +0100, Stefan Endrullis a écrit :
Am 03.03.2012 17:45, schrieb Kristopher John
Gamrat:
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Saturday 03 March 2012 11:09:23 am Stefan
Endrullis wrote:
Thanks for your help. Unfortunately, it did not help. I also tried to remove or disable
everything that could conflict with the sound system. I removed pulseaudio and arts via
aptitude, removed all autostart applications from /opt/trinity/share/autostart and
~/.trinity/Autostart, except kdesktop and panel, and deleted
.trinity/share/config/ksmserverrc to start with a new and clean session. However, the
problem stays the same. When KDE session manager (ksmserver) starts up my sound gets
deactivated.
As workaround I'm currently starting openbox instead of TDE. In openbox I can run
kdesktop, kicker, khotkeys without issues. Sound works. Only the start of ksmserver
breaks the sound system, so I skip this one.
Regards,
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hello,
does someone tried to install Trinity on Ubuntu Precise?
Today I upgraded my system from Oneiric to Precise due to new hardware that did not work
properly on Oneiric.
Everything works fine in Precise, except the sound. While I still have sound in gdm or
in unity DE I don't hear anything in Trinity.
Since the sound works already in gdm I think it should also work in Trinity if Trinity
would not touch it at startup. Unfortunately Trinity does. Shortly after the start the
sound gets somehow deactivated or invisible muted (in alsamixer everything looks fine,
volume is up not muted). However, I don't hear anything and I don't get any error
messages). What can I do?
The first thing I'd recommend is to launch Kmix and see if it agrees with alsamixer.
If it does, go into Control Cente -> Sound& Multimedia -> Sound System. Try
to disable it (untick "Enable the sound system", hit apply) and see if it works.
If not, then re-enable the Sound System and click the Hardware tab. Check the setting for
"Select the audio device". This is normally set to "Autodetect", but
it may be worth while to specify one specificly. Since you're using ALSA, that would
be the first one to try, followed by the others if you have any listed.
The "last resort" thing I'd recommend is to use either apt-get or Synaptic
to purge/completely remove ALSA, then reinstall it.
4440
days inactive
4443
days old
4 comments
3 participants
participants (3)
-
Kristopher John Gamrat -
pierre.lag6633＠free.fr -
Stefan Endrullis