I ran yum update earlier and now I have no sound. I haven't found anything that restores it in alsamixer or p/a vol. control. Alsamixer [F5 for All] only displays two controls, normally there are others that require unmuting?
I have Thunderbird mail set up for voice announcements for various e-mail sources and have come to rely on sound for that so it's a bit of a panic.
This is: Linux box6 2.6.38.8-35.fc15.i686 #1 SMP Wed Jul 6 14:46:26 UTC 2011 i686 i686 i386 GNU/Linux
Any suggestions?
Bob
--
Without intending a flamewar (after all, we have to move forward, wherever that means), the linked article[1] is not interesting or unique in its blatant criticism of the Windows 8 interface, but it is interesting that the author sees the Windows 8 interface as a chance for Linux to get the upper hand on the desktop:
http://www.pcmag.com/article2/0,2817,2386343,00.asp?obref=obinsite
Is he right and we're moving badly in the wrong direction (as in, an interface with a more traditional GUI feel would be a big winner?) or is competing with a similar look-and-feel as the default while providing lots of traditional-feeling alternatives a winning attitude?
I haven't found any debate written anywhere public about a deliberate decision to try to "out-Windows8 Windows8" as far as interface is concerned, but it seems this is what Gnome 3 is aimed at.
Now that F15 has had a few weeks of heavy use, and people have either adapted to the new interface or adopted a permanently frustrated attitude toward it, I'm curious the general feeling. (Sorry, my English is giving out -- I think this last sentence may be weird.)
-Iwao
I have no opinion on those types of articles. Even if I did, it would only be my opinion...
But, I would like to point out that you've managed to hijack a thread. Not something that is nice around these parts. :-)
Now that F15 has had a few weeks of heavy use, and people have either adapted to the new interface or adopted a permanently frustrated attitude toward it, I'm curious the general feeling. (Sorry, my English is giving out -- I think this last sentence may be weird.)
A long long time ago (before even Linux) the fact that it was dumb to lock the Windowing system and UI together was part of the design of X. It still is. So Fedora isn't really moving in any direction. Gnome 3 may be trying to go a particular way but Fedora supports multiple desktops and people can write more of them.
I certainly played with Gnome 3 a bit, and there are some good ideas but in general I found it dire. Gnome 3.2 will be the real test, have they fixed all the really dumb bits of the design that users hate or not.
Alan
On 07/13/2011 07:39 AM, 夜神 岩男 wrote:
Is he right and we're moving badly in the wrong direction (as in, an interface with a more traditional GUI feel would be a big winner?) or is competing with a similar look-and-feel as the default while providing lots of traditional-feeling alternatives a winning attitude?
Thank you for the link. I've just passed it on to Jerry Pournelle, as I think he (and maybe his readers) will find it interesting.
I think what we have in the Gnome Shell is what happens when the devs on a big project find themselves controlled by people who believe that if it's new it must be better. This, naturally, isn't always true any more than the opposite attitude of if it's new it must be bad. Of course, with Linux, those of us who don't like the direction Gnome is going in are able to move to a different DE; in Windows, you won't have that choice, so we may find ourselves becoming more mainstream if Microsoft doesn't correct its current cranio-rectal insertion.
--- On Wed, 7/13/11, Bob Goodwin bobgoodwin@wildblue.net wrote:
From: Bob Goodwin bobgoodwin@wildblue.net Subject: No sound after update today - To: "Fedora list" users@lists.fedoraproject.org Date: Wednesday, July 13, 2011, 7:03 AM I ran yum update earlier and now I have no sound. I haven't found anything that restores it in alsamixer or p/a vol. control. Alsamixer [F5 for All] only displays two controls, normally there are others that require unmuting?
I have Thunderbird mail set up for voice announcements for various e-mail sources and have come to rely on sound for that so it's a bit of a panic.
This is: Linux box6 2.6.38.8-35.fc15.i686 #1 SMP Wed Jul 6 14:46:26 UTC 2011 i686 i686 i386 GNU/Linux
Any suggestions?
Bob
--
--
Try directly with alsa:
$ alsamixer -c 0
If not proceed to check if pulseaudio is running?
Regards,
Antonio
Bob Goodwin writes:
I ran yum update earlier and now I have no sound. I haven't found anything that restores it in alsamixer or p/a vol. control. Alsamixer [F5 for All] only displays two controls, normally there are others that require unmuting? I have Thunderbird mail set up for voice announcements for various e-mail sources and have come to rely on sound for that so it's a bit of a panic. This is: Linux box6 2.6.38.8-35.fc15.i686 #1 SMP Wed Jul 6 14:46:26 UTC 2011 i686 i686 i386 GNU/Linux Any suggestions?
Boot with the previous kernel, and see if that fixes it.
On 13/07/11 10:44, Sam Varshavchik wrote:
Bob Goodwin writes:
I ran yum update earlier and now I have no sound. I haven't found anything that restores it in alsamixer or p/a vol. control. Alsamixer [F5 for All] only displays two controls, normally there are others that require unmuting? I have Thunderbird mail set up for voice announcements for various e-mail sources and have come to rely on sound for that so it's a bit of a panic. This is: Linux box6 2.6.38.8-35.fc15.i686 #1 SMP Wed Jul 6 14:46:26 UTC 2011 i686 i686 i386 GNU/Linux Any suggestions?Boot with the previous kernel, and see if that fixes it.
Thanks Sam, that fixed it, or at least got around the problem. I can't recall having a problem due to a new kernel, usually everything continues to work. But I should have tried first ...
Hopefully whatever the problem will be corrected.
Bob
On 07/13/2011 11:00 AM, Bob Goodwin wrote:
Boot with the previous kernel, and see if that fixes it.
Thanks Sam, that fixed it, or at least got around the problem. I can't recall having a problem due to a new kernel, usually everything continues to work. But I should have tried first ... Hopefully whatever the problem will be corrected. Bob
Was it rebooting that fixed it - or rebooting with an older kernel? Can you try rebooting with newer kernel?
gene
On 13/07/11 11:28, Genes MailLists wrote:
Was it rebooting that fixed it - or rebooting with an older kernel? Can you try rebooting with newer kernel?
gene
A good question and that only adds to the confusion. To begin with, rebooting is a painful process and takes about a minute and a half to get to the point where I can log in and startx.
I shut down then tried booting with the new kernel. No sound.
Then booted with the previous kernel. No Sound.
Shut down and booted again with previous kernel. Sound restored.
I always reboot after a yum update to flush out any problems like that at my convenience rather than wait. That's what happened this morning when I found there was no sound. It took a while to realize I wasn't hearing the incoming message signals.
I'll try the new kernel again later, perhaps rebooting it a second time made a difference? I prefer to think not but will try just for laughs.
Bob
On 07/13/2011 12:51 PM, Bob Goodwin wrote:
On 13/07/11 11:28, Genes MailLists wrote:
Was it rebooting that fixed it - or rebooting with an older kernel? Can you try rebooting with newer kernel?
gene
A good question and that only adds to the confusion. To begin with, rebooting is a painful process and takes about a minute and a half to get to the point where I can log in and startx.
mmm ... Was that boot time comparable on F14 or faster?
that kinda sounds like possibly something is not starting right - is there anything in /var/log/messages?
On 13/07/11 13:38, Genes MailLists wrote:
On 07/13/2011 12:51 PM, Bob Goodwin wrote:
A good question and that only adds to the confusion. To begin with, rebooting is a painful process and takes about a minute and a half to get to the point where I can log in and startx.mmm ... Was that boot time comparable on F14 or faster?
that kinda sounds like possibly something is not starting right - is there anything in /var/log/messages?
F14 worked well, booted quickly.
A clean install of F15 booted quickly. I made several attempts to remove NetworkManager and this is the result. Normally only a once per day event so I drink coffee and don't much care at 03:00. I never saw anything in the log that I recognized as helpful.
On 13/07/11 12:51, Bob Goodwin wrote:
On 13/07/11 11:28, Genes MailLists wrote:
Was it rebooting that fixed it - or rebooting with an older kernel? Can you try rebooting with newer kernel?
gene
A good question and that only adds to the confusion. To begin with, rebooting is a painful process and takes about a minute and a half to get to the point where I can log in and startx. I shut down then tried booting with the new kernel. No sound. Then booted with the previous kernel. No Sound. Shut down and booted again with previous kernel. Sound restored. I always reboot after a yum update to flush out any problems like that at my convenience rather than wait. That's what happened this morning when I found there was no sound. It took a while to realize I wasn't hearing the incoming message signals. I'll try the new kernel again later, perhaps rebooting it a second time made a difference? I prefer to think not but will try just for laughs. Bob
To further add to the mysteries of Fedora 15, sound works normally this morning after booting to the latest kernel, 2.6.38.8-35.fc15.i686. Will it continue to work over subsequent reboots? That remains to be seen.
The only other thing I found necessary was to "fix" LibreOffice Calc configuration in order to get it to run. That seems to be required after LibreOffice updates.
Thanks for the help.
Bob
On 14/07/11 08:24, Patrick O'Callaghan wrote:
On Thu, 2011-07-14 at 04:05 -0400, Bob Goodwin wrote:
The only other thing I found necessary was to "fix" LibreOffice Calc configuration in order to get it to run.
Could you be more explicit? That sounds like either a bug or a configuration error. I know I've never seen it.
poc
Yes, Ed Greshko provided the answer a couple of weeks ago.
I have a spread sheet to track my ISP usage and although Calc comes up normally when I open a file the display would freeze and I could do nothing. I would try to close but again nothing until an error message comes up telling me the application is not responding and offers to kill it.
The solution is to comment out the line SAL_ENABLE_FILE_LOCKING=1 in /usr/lib/libreoffice/program/soffice as below:
#***********************************************
# # STAR_PROFILE_LOCKING_DISABLED=1 # export STAR_PROFILE_LOCKING_DISABLED #
# file locking now enabled by default # SAL_ENABLE_FILE_LOCKING=1 export SAL_ENABLE_FILE_LOCKING
That's all I know, it fixes the problem and I have had to do it several times now after F-15 updates.
Bob .
-
Alan Cox -
Antonio Olivares -
Bob Goodwin -
Ed Greshko -
Genes MailLists -
Joe Zeff -
Patrick O'Callaghan -
Sam Varshavchik -
夜神 岩男