*** This bug is a duplicate of bug 299093 ***
https://bugs.launchpad.net/bugs/299093
> @Bowmore can that native mode be the cause of bug #295519 ?
Thanks BUGabundo, I'll try to contribute to that bug as it seems to be
the same problem as I experienced before my workaround by forcing alsa
modu
*** This bug is a duplicate of bug 299093 ***
https://bugs.launchpad.net/bugs/299093
@Bowmore can that native mode be the cause of bug #295519 ?
--
[Jaunty] Sound muted on boot
https://bugs.launchpad.net/bugs/296738
You received this bug notification because you are a member of Ubuntu
Bugs
*** This bug is a duplicate of bug 299093 ***
https://bugs.launchpad.net/bugs/299093
On Wed, 2008-11-26 at 09:15 +, BUGabundo wrote:
> *** This bug is a duplicate of bug 299093 ***
> https://bugs.launchpad.net/bugs/299093
>
> On Tuesday 25 November 2008 22:08:20 Mackenzie Morgan wrote
*** This bug is a duplicate of bug 299093 ***
https://bugs.launchpad.net/bugs/299093
sorry about that.
hadnt read the entire bug mail...
Its now fixed.
--
[Jaunty] Sound muted on boot
https://bugs.launchpad.net/bugs/296738
You received this bug notification because you are a member of Ubunt
*** This bug is a duplicate of bug 299093 ***
https://bugs.launchpad.net/bugs/299093
On Tuesday 25 November 2008 22:08:20 Mackenzie Morgan wrote:
> It seems like alsactl store and restore are functional, in that case.
So why aint it getting restored on boot, Mac?
--
BUGabundo :o)
(``-_-´´
*** This bug is a duplicate of bug 299093 ***
https://bugs.launchpad.net/bugs/299093
Thanks Noel, but the bug's been figured out now. alsactl works
fine...it just happens to have ended up in the wrong place so that the
init script couldn't find it. That's why it's been marked a duplicate.
An
*** This bug is a duplicate of bug 299093 ***
https://bugs.launchpad.net/bugs/299093
Mackenzie,
> is this *only* after reboots, or does this occur when you
> log out and log back in as well?
For me, only after a reboot. Logging out and back in has its own
problems (X won't restart properly,
*** This bug is a duplicate of bug 299093 ***
https://bugs.launchpad.net/bugs/299093
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** This bug has been marked a duplicate of bug 299093
[jaunty] initscript fails to (re)store mixer settings due to check for
nonexistent /
Thank you Bugabundo. It *seems* like alsactl store and restore are
functional, in that case.
--
[Jaunty] Sound muted on boot
https://bugs.launchpad.net/bugs/296738
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
On Tue, 2008-11-25 at 16:00 +, BUGabundo wrote:
> Olá LinkinXp e a todos.
>
> On Tuesday 25 November 2008 15:05:27 LinkinXp wrote:
> > I have the same problem, and when I try to lower or increase the volume
> > level using the buttons in my laptop it doesn't work i have to do it
> > using the
My file /var/lib/alsa/asound.state didn't exist so I copied the one for
Intrepid (same machine) and modified it manually then restored settings
using "PULSE_INTERNAL=0 alsactl restore" and it works! But the settings
do not survive a reboot. Furthermore, any changes made in the Volume
Control Panel
Olá LinkinXp e a todos.
On Tuesday 25 November 2008 15:05:27 LinkinXp wrote:
> I have the same problem, and when I try to lower or increase the volume
> level using the buttons in my laptop it doesn't work i have to do it
> using the Volume Control Applet
LinkinXp thats another bug... not this on
Mackenzie Morgan schrieb:
> Do you have a ~/.pulse anyway? If you remove it with PA uninstalled,
> then log out and back in, is it recreated?
>=20
Oh yes, indeed. It contains one symbolic link to one empty directory in
/tmp:
$ ls -ld ~/.pulse/*
lrwxrwxrwx 1 k k 23 2008-11-25 15:48
/home/k/.pulse
I have the same problem, and when I try to lower or increase the volume
level using the buttons in my laptop it doesn't work i have to do it
using the Volume Control Applet
--
[Jaunty] Sound muted on boot
https://bugs.launchpad.net/bugs/296738
You received this bug notification because you are a
On Tuesday 25 November 2008 12:17:21 Mackenzie Morgan wrote:
> Been working on this with Bugabundo, and for the sake of archiving tests
Thank you for all the hard work.
> Can someone please:
> 1. change mixer values to something that lets them hear sound
Done.
> 2. run "sudo -i" followed by "PU
Current suspect: alsactl store and/or restore
Been working on this with Bugabundo, and for the sake of archiving
tests, I'm posting what we've checked:
* On boot, before logging into GDM, all but Master are 0% and mute.
* After booting, try changing settings and running "PULSE_INTERNAL=0 alsactl
I'm having this problem too. My master and PCM channels are fine, but
the rest (front etc) are muted each boot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: pulseaudio (Ubuntu)
Importance: Undecid
The pulseaudio executable fails which is also logged in my user.log. Another
way to find out is e.g. to use the command
pulseaudio --dump-modules
to list the PA's modules. This gives the following initial output:
I: caps.c: Limited capabilities successfully to CAP_SYS_NICE.
I: caps.c: Dropping
On Mon, 2008-11-24 at 19:01 +, Kjell Braden wrote:
> Note that this issue does not seem to be pulseaudio related to me. I've
> removed most parts of it (except: gstreamer0.10-pulseaudio, libpulse-
> browse0, libpulse-mainloop-glib0 and libpulse0) and I experience the
> same issue: no sound afte
Note that this issue does not seem to be pulseaudio related to me. I've
removed most parts of it (except: gstreamer0.10-pulseaudio, libpulse-
browse0, libpulse-mainloop-glib0 and libpulse0) and I experience the
same issue: no sound after booting, unmuting the "Front" control
temporarily fixes the i
No driver has been manually configured for sound (or for Hardy 8.0.4.1).
Sound works fine in Hardy with no errors. Logging off and on again is
not a problem as sound settings are saved between sessions. There is no
switch for audio as the sound is integral to the monitor and the cable
is fine. Soun
The problem seems at least partly to be a PulseAudio problem maybe a
consecutive problem though.
The problem as mentioned earlier here is that some sound channels are
muted and most handles reset after a reboot but not at a re-login. After
adjusting the main sound handle then Totem sound works but
loging off and logging on did not affected my sound volume! all controls
were left as they were before ending the session
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
[Jaunty] Sound muted on boot
https://bugs.launchpad.net/bugs/296738
You received this bug notification becau
$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xf3ff8000 irq 21
** Attachment added: "alsa-info.txt"
http://launchpadlibrarian.net/19903358/alsa-info.txt
--
[Jaunty] Sound muted on boot
https://bugs.launchpad.net/bugs/296738
You rece
Could you please include the information requested from the "Reporting
Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems ?
And is this *only* after reboots, or does this occur when you log out
and log back in as well? If it occurs from starting a new X session, I
think it's mo
25 matches
Mail list logo