[Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2010-11-30 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2010-03-31 Thread Brad Figg
** Tags added: karmic

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2010-03-29 Thread Sarraceno
Hi!

So, te tests were:
 Pre reboot I did changed settigns and also not changing settings.
 Then reboot
 Whe machine come up 10.04 chown no issue with sound, setting 
prevailed and I had real sound.


Thanks!
Good job!
Tomas
On 27-03-2010 23:37, Brad Figg wrote:
> Hi Sarraceno,
>
>
> Please, if you are still having issues, test with the latest development 
> release of Ubuntu.  ISO CD images are available from 
> http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command from a
> Terminal (Applications->Accessories->Terminal). It will automatically
> gather and attach updated debug information to this report.
>
> apport-collect -p alsa-base 467619
>
> Also, if you could test the latest upstream kernel available that would
> be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .
>
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag. This can be done by clicking on the yellow pencil
> icon next to the tag located at the bottom of the bug description and
> deleting the 'needs-upstream-testing' text.
>
> Please let us know your results.
>
>  [This is an automated message.  Apologies if it has reached you 
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: kj-triage needs-required-logs needs-test-current-image
> no-sound-system
>
> ** Changed in: alsa-driver (Ubuntu)
> Status: New =>  Incomplete
>
>

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2010-03-29 Thread Sarraceno
Hi!

First,
thanks!

Second, the answer is that the issue is different since December, I think.
So I do not use the "alsa force-reload", which is commented out since. 
I'm now able to get sound but erratically the sound is muted, full or 
some other level, which doesn't have nothing to do what I leaved last 
shutdown.

I have 10.04 installed and following hardly the updates using VMWare 
strategically configured using physicall partitions, so some times I 
boot live the installation.
I going to do some boots on my 10.04 and tell you.

Bye!
Tomas

On 27-03-2010 23:37, Brad Figg wrote:
> Hi Sarraceno,
>
>
> Please, if you are still having issues, test with the latest development 
> release of Ubuntu.  ISO CD images are available from 
> http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command from a
> Terminal (Applications->Accessories->Terminal). It will automatically
> gather and attach updated debug information to this report.
>
> apport-collect -p alsa-base 467619
>
> Also, if you could test the latest upstream kernel available that would
> be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .
>
> Once you've tested the upstream kernel, please remove the 'needs-
> upstream-testing' tag. This can be done by clicking on the yellow pencil
> icon next to the tag located at the bottom of the bug description and
> deleting the 'needs-upstream-testing' text.
>
> Please let us know your results.
>
>  [This is an automated message.  Apologies if it has reached you 
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: kj-triage needs-required-logs needs-test-current-image
> no-sound-system
>
> ** Changed in: alsa-driver (Ubuntu)
> Status: New =>  Incomplete
>
>

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2010-03-27 Thread Brad Figg
Hi Sarraceno,


Please, if you are still having issues, test with the latest development 
release of Ubuntu.  ISO CD images are available from 
http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a
Terminal (Applications->Accessories->Terminal). It will automatically
gather and attach updated debug information to this report.

apport-collect -p alsa-base 467619

Also, if you could test the latest upstream kernel available that would
be great. It will allow additional upstream developers to examine the
issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .

Once you've tested the upstream kernel, please remove the 'needs-
upstream-testing' tag. This can be done by clicking on the yellow pencil
icon next to the tag located at the bottom of the bug description and
deleting the 'needs-upstream-testing' text.

Please let us know your results.

[This is an automated message.  Apologies if it has reached you 
inappropriately; please just reply to this message indicating so.]


** Tags added: kj-triage needs-required-logs needs-test-current-image
no-sound-system

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2009-12-07 Thread WeatherGod
Moving this to alsa-driver, but I am not 100% convinced it is a driver
issue given the new odd symptom reported by Sarraceno

** Package changed: gst0.10-python (Ubuntu) => alsa-driver (Ubuntu)

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2009-11-07 Thread Sarraceno
After a couple of days installing everything fresh taking out any trick.
I do not know what is the relation, after adding a second user to the laptop, 
after reboot sound didn't work.

alsa force-reload
made to worked again.

Does anyone know about any module setting related to this sympthoms?


** Changed in: gst0.10-python (Ubuntu)
   Status: Invalid => New

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2009-11-01 Thread Sarraceno
No, still not ok.

After post this bug I did upgrade two of my computers from 9.04 into 9.10n 
(Ubunut Desktop, Ubuntu Studio) at home, only mediacenter is waiting, I need to 
be sure that one having sound after upgrade.
So, on the two I upgraded are fine, for for those I answered always to replace 
config files, for my work laptop I didn't begin afraid of next day I would have 
the machine available to go work...

So, it's possible that I need to refresh/reconfigure some package. Does
any one know what?

The packages for alsa that I have are:
>
jto...@ptjtomasub:~$ apt-show-versions -r '.*alsa.*'
alsa-base/karmic uptodate 1.0.20+dfsg-1ubuntu5
alsa-utils/karmic uptodate 1.0.20-2ubuntu6
bluez-alsa/karmic uptodate 4.51-0ubuntu2
gnome-alsamixer/karmic uptodate 0.9.7~cvs.20060916.ds.1-2
gstreamer0.10-alsa/karmic uptodate 0.10.25-2ubuntu1
libesd-alsa0/karmic uptodate 0.2.41-5
libsdl1.2debian-alsa not installed
libsox-fmt-alsa/karmic uptodate 14.3.0-1build1
linux-backports-modules-alsa-2.6.31-14-generic/karmic uptodate 2.6.31-14.16
linux-backports-modules-alsa-karmic-generic/karmic uptodate 2.6.31.14.27
jto...@ptjtomasub:~$ 
<

I have did dpkg-reconfigure for all these except the backports that were
no installed, result is none.

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2009-11-01 Thread Sarraceno
I think you are referring module linux-backports-modules-alsa-karmic-
generic, not installed, after reboot I'll come here to say if worked.

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2009-10-31 Thread WeatherGod
The linux-backports-modules-alsa package may need to be (re?)-installed.
Don't know for sure if this will fix things, but I don't think it will
hurt.

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2009-10-31 Thread Sarraceno
I forgot to say that: for my users I did check permissions for audio using the 
"Users and Groups" manager.
So I don't understant why "sudo alsa force-reload" gets the following output:
-->
jto...@ptjtomasub:~$ sudo alsa force-reload
[sudo] password for jtomas: 
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/jtomas/.gvfs
  Output information may be incomplete.
Terminating processes: 1358 3068lsof: WARNING: can't stat() 
fuse.gvfs-fuse-daemon file system /home/jtomas/.gvfs
  Output information may be incomplete.
 3268lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system 
/home/jtomas/.gvfs
  Output information may be incomplete.
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/jtomas/.gvfs
  Output information may be incomplete.
.
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/jtomas/.gvfs
  Output information may be incomplete.
Unloading ALSA sound driver modules: snd-hda-codec-si3054 snd-hda-codec-realtek 
snd-hda-intel snd-hda-codec snd-hwdep snd-pcm-oss snd-mixer-oss snd-pcm 
snd-seq-dummy snd-seq-oss snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq 
snd-timer snd-seq-device snd-page-alloc (failed: modules still loaded: 
snd-hda-codec-si3054 snd-hda-codec-realtek snd-hda-codec snd-hwdep snd-pcm 
snd-timer snd-page-alloc).
Loading ALSA sound driver modules: snd-hda-codec-si3054 snd-hda-codec-realtek 
snd-hda-intel snd-hda-codec snd-hwdep snd-pcm-oss snd-mixer-oss snd-pcm 
snd-seq-dummy snd-seq-oss snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq 
snd-timer snd-seq-device snd-page-alloc.
jto...@ptjtomasub:~$ 
<--

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 467619] Re: After upgrade, no sound. If I manually run "alsa force-reload" sound becomes available

2009-10-31 Thread Sarraceno

** Attachment added: "CheckboxData.txt"
   http://launchpadlibrarian.net/34818527/CheckboxData.txt

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/34818528/Dependencies.txt

** Attachment added: "XsessionErrors.txt"
   http://launchpadlibrarian.net/34818529/XsessionErrors.txt

-- 
After upgrade, no sound. If I manually run "alsa force-reload" sound becomes 
available
https://bugs.launchpad.net/bugs/467619
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs