SELinux problems after F10->F11 upgrade in x86_64 system
Hi all, there have been a lot (well over 100 during the 1st 12 hours) of dbusd-related SELinux denials after upgrading my x86_64 system from F10 to F11. In F10 and earlier SELinux problems were usually caused by various fail2ban operations but now these denials - probably due to updated fail2ban in F11 - are practically non-existent. In F10 (and earlier) it was possible to get rid of SELinux denials by compiling and installing a local module derived from either /var/log/messages or /var/log/audit/audit.log, as explained in SELinux FAQ. However, the local module method doesn't seem to be effective in the dbusd case - or I am doing something wrong. Compiling the local module doesn't report any errors but installing it results in: [r...@mybox ~]# semodule -i local.pp libsepol.print_missing_requirements: local's global requirements were not met: type/attribute unconfined_t libsemanage.semanage_link_sandbox: Link packages failed semodule: Failed! [r...@mybox ~]# After running 'touch /.autorelabel; reboot' I got rid of 'File label' denials but the 'dbusd' ones are still there. So what now? TIA, Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Where is the network activity applet
la, 2009-06-13 kello 12:26 -0500, Steven Stern kirjoitti: > I just did a clean install of F11. On F10, there was a little thing in > the system tray that advised me of the status of the network. It's not > there in F11. Please note that I am using "network", not > "NetworkManager" to manage the network. # yum install gnome-netstatus BR, Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Selinux, Fail2ban, iptables BUG
la, 2009-05-23 kello 12:14 -0400, Jim kirjoitti: > FC10/KDE > > Has anyone run across this problem run across this while running > fail2ban-0.8.3-18.fc10.noarch ?? > > there are two Redhat bug reports on this same problem and they seem to > think it's fixed, but it isn't. > Bug # > 499674 > 491444 Please look at bug # 475237. Though it originally didn't mention your particular problem, the latter was one of many fail2ban-related SELinux denials I encountered. In my case, the problem was solved by building a *local module* enabling the coexistence of fail2ban and SELinux. The procedure is explained in SELinux FAQ, but you may have to repeat the procedure several times. My local.te file is available (off-list) if you need it. Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Sound pops
su, 2009-03-29 kello 09:55 -0400, Kanwar Ranbir Sandhu kirjoitti: > Hi Everyone, > > I have fully updated F10 system running on an Asus P5Q-E motherboard. > Yesterday while listening to some mp3s, I heard snaps, pops, and > crackles (rice krispies are tasty!). At first I thought it was maybe a > poorly encoded mp3, but listening to many other mp3s didn't remove the > issue. > > Has anyone else experienced this recently? Unfortunately, yes, though not necessarily with mp3 files only. My F10 system also suffers from "snap, crackle and pop" syndrome with all audio reproduction. My MB is an ASUS K8N, and pulseaudio is working perfectly with my F9 system using the same hardware. > I remember reading here > quite a while ago about similar issues. I believe at that time it was a > problem with pulseaudio. Maybe the bug is back. :: shrugs :: I sincerely don't know where the blame really lies but there are several remedies already offered. One is removing alsa-plugins-pulseaudio, the other is editing /etc/pulse/default.pa (http://forums.fedoraforum.org/showthread.php?t=206868 ), and the third was published just yesterday on this list by Francois Patte under the title of "Re: sound on fedora 10[SOLVED(?)]". I haven't tried any of these yet but I'm somewhat perplexed by the fact that now that F10 has been available for 4 months, the problems with audio are still there. Isn't anybody writing bug reports any longer? I would have, but I've just had F10 installed a couple of weeks. > > Any input would be appreciated! > > Regards, > > Ranbir > BR, Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: NM fails to connect when booting ?? -[SOLVED]
ke, 2009-03-18 kello 08:22 +0100, Kevin Kofler kirjoitti: > William Case wrote: > > I agree completely. The problem seems to be in the NetworkManager > > Applet. First, there is no manual. Secondly, it seems to lack any > > ability to affect the function of NetworkManager -- at least at the > > simplest level. I can't use it to disconnect, if for some reason I > > might want to (eg. tweaking, playing around, etc.). Even when I use the > > edit function - "Edit Connections" - all the editable fields are greyed > > out. To me that is where an ordinary user would think to alter the > > ifcfg-eth* script. It seems to be just a front end gui for nm-tools > > which in turn is only a reporting program. > > "Edit Connections" is for primarily editing per-user settings. I think > there's also a plugin for systemwide settings which can be edited at the > same place, but Fedora is using a plugin to use the existing > system-config-network settings instead, so you have to fire up > system-config-network to change systemwide settings. > > Kevin Kofler > I wonder if "Edit connections" now works even for per-user settings? A few days ago I finally installed F10 from original (Nov -08) x86_64 DVD. That version seemed to allow me to edit NM connections at least somehow but I didn't do it before downloading some 340 M of updates. After that "Edit connections" was useless (greyed out) for ordinary user. Because I have a wired cable modem (at eth0) and a NATted Centos 5.2 box connected to Internet (via eth1) through the F10 box, I could not make NM behave the way I wanted. Maybe the original ifcfg-eth0 default of 'ONBOOT=no' is not a bug but it surely is a poor choice for someone like me with no wireless devices. After struggling a while with NM trying to configure it the way I wanted, I had to disable NM altogether and configure the trusty old network service like it is in my F9 system. To add insult to injury, it is now necessary to install gnome-netstatus applet separately because it has been removed from basic F10 installation's 'add-to-panel-gadgets'. To me it looks like "life is too short for NM". Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: pulseaudio deeply unreliable (Fedora 10)
su, 2009-03-08 kello 23:15 +0100, Nigel Henry kirjoitti:
> On Sunday 08 March 2009 18:38, Antti J. Huhtala wrote:
> > Hello Nigel,
> >
> > could/would you please stop advertising "remove pulseaudio" as the
> > panacea for all audio-related problems? Please? It is not as simple as
> > that.
I sent my comments to you off-list but now that it's all public I'd like
to add a couple of comments.
> I do not advocate the removal of pulseaudio to resolve all audio problems.
>
That's good. Learning how to properly use PulseAudio Volume Control in
Applications->Sound & Video solved whatever problems I still had in
directing audio streams where I wanted them.
> When I see audio related probelms, which may,or may not be related to
> pulseaudio, I suggest disabling pulseaudio to see if that resolves the audio
> problem, and that's as far as it goes. if disabling pulseaudio resolves a
> sound related problem, then all well and good.
>
> If the user now has his/her sounds working, that is all that I'm trying to
> help with. Personally I have no interest in pulseaudio, as on all my 3
> machines the sound works without pulseaudio entering the equation.
>
That's all right if you only use one audio application at a time.
However, sometimes one needs to use more. Here's a quotation from my
private mail to another list member:
"I'm attaching a small text file (of 'top') demonstrating successful use
of pulseaudio. I had Rhythmbox playing some of my favorite records. This
stream was directed to USB headphones. Simultaneously I had totem
(actually totem-xine with all the non-free codecs) playing a movie. This
stream was directed to loudspeakers through the Ensonic SB sound card.
Please note the relatively low average load, even if I have Firefox and
some other programs running.
Both audio signals were completely free of pops or crackles - and there
were no "holes" in the audio output of either. Those holes were plaguing
PA all the time when pulseaudio was new to Fedora :-("
> I will continue to try and help folks with sound related problems. I do not
> believe that pulseaudio is necessary for sounds to work, and sounds worked
> with Alsa long before pulseaudio existed (FC1).
>
I know that alsamixer already worked well around F7 era or so. Now I
need two sound cards working simultaneously with different streams to be
used in my SDR (Software-Defined Radio) experiments. I can't see how
alsamixer could handle that.
> No doubt this will start some flame or other, but is the way I answer sound
> related problems, whether on Fedora, Debian, or Kubuntu/Ubuntu lists. So so
> be it.
>
Well, it has generated a few rather even-tempered comments so far. I
doubt that this will develop into a flame war on this list.
To conclude, I understand that if someone - especially a newbie - has
trouble getting *any* sounds from his/her system, minimizing the number
of possible culprits (such as pulseaudio) can perhaps be justified. Now
that PulseAudio has reached a stable state, more often than not the
problem is probably elsewhere. Of course, my experience is based only on
the hardware I use. It might not be as plain sailing for other HW
combinations.
BR, Antti
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: pulseaudio does not start after kernel update
ma, 2008-07-28 kello 23:57 +0300, Antti J. Huhtala kirjoitti: > ma, 2008-07-28 kello 20:28 +0100, Andrea kirjoitti: > > > > Is there a bug report for that? > > > Andrea > > > Not by me, and haven't had the time to check if someone else has. > I briefly tried the previous kernel and PA seems to work OK in it. > I'll write a bug report tomorrow if no one else has by then. > > Antti > Replying to my own post: After trying what Alan Cox suggested in another thread (Re: getting sound back) on 28th July, my pulseaudio sound worked OK all day yesterday using the latest 2.6.25.11-97.fc9.x86_64 kernel. In addition, there are already a number of bug reports in bugzilla that cover the PA issue (eg. 456485, 455661, 455202, 452702, and 438284) for F9. Check these and add a comment if you think you can shed more light on the problem. I decided my experience had little or no added value. Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: pulseaudio does not start after kernel update
ma, 2008-07-28 kello 20:28 +0100, Andrea kirjoitti: > Antti J. Huhtala wrote: > > su, 2008-07-27 kello 23:34 +0100, Andrea kirjoitti: > >> Antti J. Huhtala wrote: > >> kernel-2.6.25.11-97.fc9.i686 > >> > > That's the one except that here it is 2.6.25.11-97.fc9.x86_64. > > > > > Is there a bug report for that? > Andrea > Not by me, and haven't had the time to check if someone else has. I briefly tried the previous kernel and PA seems to work OK in it. I'll write a bug report tomorrow if no one else has by then. Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: pulseaudio does not start after kernel update
su, 2008-07-27 kello 23:34 +0100, Andrea kirjoitti: > Antti J. Huhtala wrote: > > su, 2008-07-27 kello 11:29 +0100, Marcelo M. Garcia kirjoitti: > >> > > Yes, same and similar problems. I haven't tried Skype but when I > > redirected gtreamer stream to USB headphones instead of the usual > > loudspeakers of my Athlon64 desktop, Rhythmbox would play one track for > > a couple of minutes but then sound suddenly died in the middle of the > > track. I didn't do anything but listened. > > > > 'dmesg | grep pulseaudio' shows this: > > > > pulseaudio[2696]: segfault at 7f6acfca7330 ip 7f6acfca7330 sp > > 7fffdd2d5b58 error 14 in pulse-shm-1926128445[7f6ad04e6000+201000] > > > > It is high above my grasp of things to even try to guess what this > > means. It probably is a new quirk, appearing after latest kernel update. > > Same here. > pulseaudio server was not available, bur I run "pulseaudio -D" on command > line and soud is working now. > As in "Daemonize after startup, i.e. detach from the terminal." I see. I did not try that because sound via loudspeakers still worked using "ES1371 DAC1". Some KDE games direct sounds to USB headphones now. > my kernel is > > kernel-2.6.25.11-97.fc9.i686 > That's the one except that here it is 2.6.25.11-97.fc9.x86_64. Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: pulseaudio does not start after kernel update
su, 2008-07-27 kello 11:29 +0100, Marcelo M. Garcia kirjoitti: > Hi. > > I'm suspicious that PulseAudio is not starting properly after kernel > updates. For example, if I start Skype, I got the message: "problem with > audio playback". Or if I try "Applications->Sound & Video->PulseAudio > Volume Control", I got the message "connection refused". And finally: > [EMAIL PROTECTED] ~]# aplay > *** PULSEAUDIO: Unable to connect: Connection refused > *** Is your sound server running? > *** See: http://www.pulseaudio.org/wiki/Troubleshooting > aplay: main:564: audio open error: Connection refused > > > I'm running Fedora 9 in a Dell Latitude D510 (old low spec machine). > Does anyone else having similar problem? > Yes, same and similar problems. I haven't tried Skype but when I redirected gtreamer stream to USB headphones instead of the usual loudspeakers of my Athlon64 desktop, Rhythmbox would play one track for a couple of minutes but then sound suddenly died in the middle of the track. I didn't do anything but listened. 'dmesg | grep pulseaudio' shows this: pulseaudio[2696]: segfault at 7f6acfca7330 ip 7f6acfca7330 sp 7fffdd2d5b58 error 14 in pulse-shm-1926128445[7f6ad04e6000+201000] It is high above my grasp of things to even try to guess what this means. It probably is a new quirk, appearing after latest kernel update. Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Can't get CNN video sound ??
to, 2008-07-10 kello 18:27 +0100, Anne Wilson kirjoitti: > On Wednesday 09 July 2008 17:47, Bill Davidsen wrote: > > Anne Wilson wrote: > > > On Thursday 03 July 2008 20:39:58 Antti J. Huhtala wrote: > > >> to, 2008-07-03 kello 20:19 +0100, Anne Wilson kirjoitti: > > >>> On Thursday 03 July 2008 20:08:25 William Case wrote: > > >>>> I am somewhat of a media newbie. In F8 I was able to setup/get sound > > >>>> with videos. YouTube and CNN for example, remain silent for me in F9. > > >>> > > >>> Silly question, Bill. Have you looked at mixer settings? It seems > > >>> that there are many hidden channels on a lot of sound card, hidden, > > >>> that is, on the mixer applet, so it's possible that PCM or some such is > > >>> muted or set very low. > > >>> > > >>> Anne > > >> > > >> It's not quite that simple, I'm afraid. CNN and Youtube are silent here, > > >> too. A week or so ago I was listening to some favourites of mine on > > >> Youtube but today it is silent even if video still works all right. I'd > > >> suspect one of the recent updates. This may have something to do with > > >> another thread, "Re: problems with rhythmbox after updating to > > >> udev-124-1.fc9.1"- > > > > > > Hmm - I can't check my Fedora box tonight, but I'll look at it tomorrow. > > > > Mine worked. > > > I forgot to do this, but I've done it now. Sound works in both CNN videos > and > youtube videos. This is F9 + KDE4.0.5. > > Anne > Thank you, Anne. I got it working as well by briefly visiting KDE which is also installed in this box. CNN and Youtube sound started working there and when I returned to Gnome sound still worked. I reported about this on 4th July under "Re: Can't get CNN video sound ?? -[SOLVED]" Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: problems with rhythmbox after updating to udev-124-1.fc9.1
pe, 2008-07-04 kello 15:05 +0200, [EMAIL PROTECTED] kirjoitti: > Antti J. Huhtala wrote: > > pe, 2008-07-04 kello 09:09 +0200, [EMAIL PROTECTED] > > kirjoitti: > >> Antti J. Huhtala wrote: > >>> to, 2008-07-03 kello 21:56 +0300, Nicolae Ghimbovschi kirjoitti: > >>>> Amarok in my case works just fine. > >>>> > >>> Sorry, you're right. Amarok does work. My excuse is that I usually play > >>> CDs with rhythmbox and didn't know how to use Amarok properly. > >>> However, I have used Totem and KsCD for this purpose before and they > >>> won't play CDs now... > >> Additionally, found strange behaviour: Ejecting the CD by clicking the > >> CD symbol on the desktop (right button+eject) will eject the CD, but > >> immediately after it has been ejected, the cd will be loaded again, so I > >> have no chance to take it out. > >> > > So it does. Same thing if you click on 'Eject' in the pop-up window > > asking whether to start rhythmbox or sound juicer. This call for > > budzilla report but against which component? > > See: > > http://bugzilla.redhat.com/show_bug.cgi?id=451320 > > Joachim Backes > Right. The guys seem to argue whether it is a HAL or udev problem. Better not put my spoon in it. The interesting question is why Amarok is able to read a CD when all other CD players I've tried aren't? Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: problems with rhythmbox after updating to udev-124-1.fc9.1
pe, 2008-07-04 kello 09:09 +0200, [EMAIL PROTECTED] kirjoitti: > Antti J. Huhtala wrote: > > to, 2008-07-03 kello 21:56 +0300, Nicolae Ghimbovschi kirjoitti: > >> Amarok in my case works just fine. > >> > > Sorry, you're right. Amarok does work. My excuse is that I usually play > > CDs with rhythmbox and didn't know how to use Amarok properly. > > However, I have used Totem and KsCD for this purpose before and they > > won't play CDs now... > > Additionally, found strange behaviour: Ejecting the CD by clicking the > CD symbol on the desktop (right button+eject) will eject the CD, but > immediately after it has been ejected, the cd will be loaded again, so I > have no chance to take it out. > So it does. Same thing if you click on 'Eject' in the pop-up window asking whether to start rhythmbox or sound juicer. This call for budzilla report but against which component? > JB > Antti > > > >> On Thu, Jul 3, 2008 at 9:50 PM, Antti J. Huhtala <[EMAIL PROTECTED]> wrote: > >>> to, 2008-07-03 kello 18:40 +0200, [EMAIL PROTECTED] > >>> kirjoitti: > >>>> Somebody has seen this? > >>>> > >>>> Installing the most recent updates (july 3, 18:00 CEST), having problems > >>>> to play music CDs with rhythmbox: > >>> Yes, and it happens in 64-bit systems, too. This does not apply to > >>> rhythmbox alone; Amarok, Totem, and KsCD refuse to play CDs as well. > >>>> after inserting a music CD in the drive, the cd icon appears on the > >>>> gnome desktop, but nothing is played, and no CD index is shown (see > >>>> attachment). > >>>> > >>>> uname -r > >>>> 2.6.25.9-76.fc9.i686 > >>>> > >>> $ uname -r > >>> 2.6.25.9-76.fc9.x86_64 > >>> > >>>> rpm -q udev rhythmbox > >>>> > >>>> udev-124-1.fc9.1.i386 > >>>> rhythmbox-0.11.5-13.fc9.i386 > >>>> > >>> $ rpm -q udev rhythmbox > >>> udev-124-1.fc9.1.x86_64 > >>> rhythmbox-0.11.5-13.fc9.x86_64 > >>> > >>> Hopefully this problem will be fixed soon... > >>> > >>> Antti > >>> > > Thanks for correcting my error, Nicolae > > > > Antti > > > > > > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Can't get CNN video sound ?? -[SOLVED]
to, 2008-07-03 kello 17:59 -0400, William Case kirjoitti: > Thanks Craig; > > On Thu, 2008-07-03 at 14:32 -0700, Craig White wrote: > > On Thu, 2008-07-03 at 17:25 -0400, William Case wrote: > > > On Thu, 2008-07-03 at 16:55 -0400, William Case wrote: > [snip] > > > > you must not be checking too hard because > > http://mirrors.kernel.org/fedora/releases/9/Everything/x86_64/os/Packages/ > > > > shows both an i386 and an x86_64 version > > Never been there before. Always relied on yum or yumex; neither showed > the 32 bit libflashsupport. Went to the everything site, clicked on the > rpm. It downloaded and installed itself -- now I have sound. > > [snip] > -- > Regards Bill; Guess I have to update my posts on this subject, too: Just out of curiosity I logged out of my usual Gnome desktop and logged in KDE. There I started Firefox and - lo and behold - I had sound both on CNN and Youtube! Going back to Gnome, same thing again: sound on CNN and Youtube. I did not update or install anything between no-sound and sound experiences. Just changing from one desktop to another seems to have flipped whatever bit was in wrong state - and it stayed put when changing back to Gnome. Whatever the true explanation is, I had no sound on flash videos just a few hours earlier. I also did not adjust anything such as ALSA mixer settings or the like. It's a mystery to me... Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Can't get CNN video sound ??
to, 2008-07-03 kello 13:04 -0700, Craig White kirjoitti: > On Thu, 2008-07-03 at 22:39 +0300, Antti J. Huhtala wrote: > > to, 2008-07-03 kello 20:19 +0100, Anne Wilson kirjoitti: > > > On Thursday 03 July 2008 20:08:25 William Case wrote: > > > > I am somewhat of a media newbie. In F8 I was able to setup/get sound > > > > with videos. YouTube and CNN for example, remain silent for me in F9. > > > > > > Silly question, Bill. Have you looked at mixer settings? It seems that > > > there > > > are many hidden channels on a lot of sound card, hidden, that is, on the > > > mixer applet, so it's possible that PCM or some such is muted or set very > > > low. > > > > > > Anne > > > > > It's not quite that simple, I'm afraid. CNN and Youtube are silent here, > > too. A week or so ago I was listening to some favourites of mine on > > Youtube but today it is silent even if video still works all right. I'd > > suspect one of the recent updates. This may have something to do with > > another thread, "Re: problems with rhythmbox after updating to > > udev-124-1.fc9.1"- > > possible but doubtful. > > The issue of flash, pulseaudio and sound is typically solved by > installing libflashsupport > [EMAIL PROTECTED] ~]$ locate libflashsupport /usr/lib/libflashsupport.so /usr/lib64/libflashsupport.so Maybe I should add that I've used F9 since May and I've been listening to Youtube videos with it for longer than a month. Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Can't get CNN video sound ??
to, 2008-07-03 kello 20:19 +0100, Anne Wilson kirjoitti: > On Thursday 03 July 2008 20:08:25 William Case wrote: > > I am somewhat of a media newbie. In F8 I was able to setup/get sound > > with videos. YouTube and CNN for example, remain silent for me in F9. > > Silly question, Bill. Have you looked at mixer settings? It seems that > there > are many hidden channels on a lot of sound card, hidden, that is, on the > mixer applet, so it's possible that PCM or some such is muted or set very > low. > > Anne > It's not quite that simple, I'm afraid. CNN and Youtube are silent here, too. A week or so ago I was listening to some favourites of mine on Youtube but today it is silent even if video still works all right. I'd suspect one of the recent updates. This may have something to do with another thread, "Re: problems with rhythmbox after updating to udev-124-1.fc9.1"- Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: problems with rhythmbox after updating to udev-124-1.fc9.1
to, 2008-07-03 kello 21:56 +0300, Nicolae Ghimbovschi kirjoitti: > Amarok in my case works just fine. > Sorry, you're right. Amarok does work. My excuse is that I usually play CDs with rhythmbox and didn't know how to use Amarok properly. However, I have used Totem and KsCD for this purpose before and they won't play CDs now... > On Thu, Jul 3, 2008 at 9:50 PM, Antti J. Huhtala <[EMAIL PROTECTED]> wrote: > > to, 2008-07-03 kello 18:40 +0200, [EMAIL PROTECTED] > > kirjoitti: > >> Somebody has seen this? > >> > >> Installing the most recent updates (july 3, 18:00 CEST), having problems > >> to play music CDs with rhythmbox: > > Yes, and it happens in 64-bit systems, too. This does not apply to > > rhythmbox alone; Amarok, Totem, and KsCD refuse to play CDs as well. > >> > >> after inserting a music CD in the drive, the cd icon appears on the > >> gnome desktop, but nothing is played, and no CD index is shown (see > >> attachment). > >> > >> uname -r > >> 2.6.25.9-76.fc9.i686 > >> > > $ uname -r > > 2.6.25.9-76.fc9.x86_64 > > > >> rpm -q udev rhythmbox > >> > >> udev-124-1.fc9.1.i386 > >> rhythmbox-0.11.5-13.fc9.i386 > >> > > $ rpm -q udev rhythmbox > > udev-124-1.fc9.1.x86_64 > > rhythmbox-0.11.5-13.fc9.x86_64 > > > > Hopefully this problem will be fixed soon... > > > > Antti > > Thanks for correcting my error, Nicolae Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: problems with rhythmbox after updating to udev-124-1.fc9.1
to, 2008-07-03 kello 18:40 +0200, [EMAIL PROTECTED] kirjoitti: > Somebody has seen this? > > Installing the most recent updates (july 3, 18:00 CEST), having problems > to play music CDs with rhythmbox: Yes, and it happens in 64-bit systems, too. This does not apply to rhythmbox alone; Amarok, Totem, and KsCD refuse to play CDs as well. > > after inserting a music CD in the drive, the cd icon appears on the > gnome desktop, but nothing is played, and no CD index is shown (see > attachment). > > uname -r > 2.6.25.9-76.fc9.i686 > $ uname -r 2.6.25.9-76.fc9.x86_64 > rpm -q udev rhythmbox > > udev-124-1.fc9.1.i386 > rhythmbox-0.11.5-13.fc9.i386 > $ rpm -q udev rhythmbox udev-124-1.fc9.1.x86_64 rhythmbox-0.11.5-13.fc9.x86_64 Hopefully this problem will be fixed soon... Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: New kernels do not work.
su, 2008-05-25 kello 19:04 +0300, Antti J. Huhtala kirjoitti: > 9) Started "vi grub.conf" and replaced the UUIDs on two 'kernel' lines > with VolGroup00/LogVol00 (my Linux LVM). Sorry, I meant * /dev/VolGroup00/LogVol00 * > 10) Rebooted successfully to F9. > > HTH, Antti > Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: New kernels do not work.
su, 2008-05-25 kello 10:51 -0400, Steve kirjoitti: > ---- "Antti J. Huhtala" <[EMAIL PROTECTED]> wrote: > > la, 2008-05-24 kello 15:52 -0400, Steve kirjoitti: > > > "Antti J. Huhtala" <[EMAIL PROTECTED]> wrote: > > > > pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti: > > > > > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti: > > > > > > Please help. PC stuck in grub> prompt. > > > > > > > > > > > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files > > > > > updated at the same time - rewrote grub.conf so that (in my case) the > > > > > line which should have read: > > > > > > > > > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro > > > > > root=/dev/VolGroup00/LogVol00 > > > > > rhgb quiet > > > > > > > > > > actually read: > > > > > > > > > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro > > > > > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet > > > > > > > > > > Somehow my /dev/VolGroup... had been changed to UUID=... > > > > > > > > > > The same error had been applied to the previous kernel (2.6.25-14.fc9) > > > > > so that neither would boot. > > > > > > > > > Bugzilla # 448132. > > > > > > I have the same problem except that correcting my grub.conf file did not > > > help. I'm still stuck with just GRUB showing on the screen. Also I did > > > not get any sounds. > > > > > > Any futher suggestions? > > > > > Sorry, looking back at my cryptic hand-written notes I realize I forgot > > to mention that I ran 'grub-install' before editing grub.conf. On the > > basis of time-stamps of the files in /boot/grub, almost all files were > > rewritten but grub.conf was not. My notes don't record whether I tried > > rebooting after running grub-install but IIRC I probably did. I seem to > > recollect that I was still stuck at "GRUB". > > Therefore I edited grub.conf and tried again. This time reboot worked > > for me so I didn't delve into it further. > > Whether the real remedy was running grub-install or editing grub.conf > > *or both*, I don't know. The fact remains I'm typing this with 'fully' > > operational F9 system. > > > Steve > > Antti > > > ...and I should have added in my note that after I edited grub.conf, rebooted > and I was still stuck with just GRUB on the screen, that I re-installed grub > from the DVD while in rescue mode and then rebooted again. No luck - still > just GRUB. At this point I think my next move may be to do a complete > re-install. > OK, let's be precise here. I did *not* reinstall grub from the DVD but ran /sbin/grub-install script on my hard disk already. I used the DVD "Rescue" option only to get to the "sh-3.2#" prompt. Here's exactly what I did: 1) *Upgraded* my existing F8 using F9 DVD. After the _upgrade_ installation was over I rebooted and had a working F9 - of sorts. (My printer didnt work, I couldn't mount my NTFS partitions, totem-xine wouldn't show my movies, etc. - but that's another story.) 2) F9 PackageKit informed me that 199 packages needed updating and 15 packages needed installing, and I okayed that. Update was not successful however, because of long list of conflicts. I couldn't see all of them, so I 3) Tried 'yum update' which of course failed likewise, but now I could see that the conflicts were caused only by two packages left from F8: gnome-panel-2.20.3-1.fc8.i386 and gnome-applets-2.20.1-1.fc8.i386 (mine is an x86_64 box). I 'yum remove'd those two packages and after that successfully updated 199 packages and installed 15. 4) Because one of the 15 installed packages was kernel 2.6.26.3-18, I rebooted the box. That's when booting stopped at "GRUB". 5) Did some googling with another (Centos 5.1) box to find advice. Armed with this info I booted the non-working box with F9 DVD and chose "Rescue". 6) Went to /boot/grub/ and ran grub-install (from /sbin on my HD). 7) Tried booting the box but it again stopped at "GRUB". 8) Booted the box with F9 DVD and again went to /boot/grub directory. 9) Started "vi grub.conf" and replaced the UUIDs on two 'kernel' lines with VolGroup00/LogVol00 (my Linux LVM). 10) Rebooted successfully to F9. HTH, Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: New kernels do not work.
la, 2008-05-24 kello 15:52 -0400, Steve kirjoitti: > ---- "Antti J. Huhtala" <[EMAIL PROTECTED]> wrote: > > pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti: > > > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti: > > > > Please help. PC stuck in grub> prompt. > > > > > > > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files > > > updated at the same time - rewrote grub.conf so that (in my case) the > > > line which should have read: > > > > > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 > > > rhgb quiet > > > > > > actually read: > > > > > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro > > > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet > > > > > > Somehow my /dev/VolGroup... had been changed to UUID=... > > > > > > The same error had been applied to the previous kernel (2.6.25-14.fc9) > > > so that neither would boot. > > > > > Bugzilla # 448132. > > I have the same problem except that correcting my grub.conf file did not > help. I'm still stuck with just GRUB showing on the screen. Also I did not > get any sounds. > > Any futher suggestions? > Sorry, looking back at my cryptic hand-written notes I realize I forgot to mention that I ran 'grub-install' before editing grub.conf. On the basis of time-stamps of the files in /boot/grub, almost all files were rewritten but grub.conf was not. My notes don't record whether I tried rebooting after running grub-install but IIRC I probably did. I seem to recollect that I was still stuck at "GRUB". Therefore I edited grub.conf and tried again. This time reboot worked for me so I didn't delve into it further. Whether the real remedy was running grub-install or editing grub.conf *or both*, I don't know. The fact remains I'm typing this with 'fully' operational F9 system. Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: New kernels do not work.
la, 2008-05-24 kello 18:16 -0400, slamp slamp kirjoitti: > On Sat, May 24, 2008 at 3:52 PM, Steve <[EMAIL PROTECTED]> wrote: > > > > ---- "Antti J. Huhtala" <[EMAIL PROTECTED]> wrote: > >> pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti: > >> > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti: > >> > > Please help. PC stuck in grub> prompt. > >> > > > >> > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files > >> > updated at the same time - rewrote grub.conf so that (in my case) the > >> > line which should have read: > >> > > >> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 > >> > rhgb quiet > >> > > >> > actually read: > >> > > >> > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro > >> > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet > >> > > >> > Somehow my /dev/VolGroup... had been changed to UUID=... > >> > > >> > The same error had been applied to the previous kernel (2.6.25-14.fc9) > >> > so that neither would boot. > >> > > >> Bugzilla # 448132. > > > > I have the same problem except that correcting my grub.conf file did not > > help. I'm still stuck with just GRUB showing on the screen. Also I did not > > get any sounds. > > > > Any futher suggestions? > > > > Steve > > > > -- > > > > well my issue was either fedora or grub not being able work well with > "fakeraid". anything i tried nothing helped. i reinstalled grub to the > right fakeraid device and it did not help. so what i did was deleted > the "fakeraid" from intel bios and just did a software raid (mdadm). > this works better than dmraid and grub or fedora seems to properly use > the /dev/md* device. "fakeraid" sucks, too bad i did not catch this > when i bought my pc (powerspec e361). > Unfortunately I know next to nothing of RAIDed filesystems, but it would seem logical to assume that if you're stuck with "GRUB" it is because grub doesn't know where to go next. Another thread today deals with /etc/fstab containing UUIDs instead of filesystem partitions. It would be my guess that a working Fedora system knows how to handle UUIDs but I doubt that GRUB knows how to do it. If I'm wrong about this, I'll be happy to stand corrected. See my other reply today in this thread for something to try... Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: New kernels do not work.
pe, 2008-05-23 kello 05:47 +0300, Antti J. Huhtala kirjoitti: > to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti: > > Please help. PC stuck in grub> prompt. > > > The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files > updated at the same time - rewrote grub.conf so that (in my case) the > line which should have read: > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 > rhgb quiet > > actually read: > > kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro > root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet > > Somehow my /dev/VolGroup... had been changed to UUID=... > > The same error had been applied to the previous kernel (2.6.25-14.fc9) > so that neither would boot. > Bugzilla # 448132. > > > HTH > > Antti > Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: New kernels do not work.
to, 2008-05-22 kello 19:15 -0400, slamp slamp kirjoitti: > Please help. PC stuck in grub> prompt. > Does the system loudspeaker also ring like a firebell? I just recovered from the same situation - and your grub.conf confirms it is very likely the same problem I had. The latest kernel update 2.6.25.3-18.fc9 - or one of the 199 files updated at the same time - rewrote grub.conf so that (in my case) the line which should have read: kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet actually read: kernel /vmlinuz-2.6.25.3-18.fc9.x86_64 ro root=UUID=ab562fb5-0a9a-4458-9f30-61c8a23f774a rhgb quiet Somehow my /dev/VolGroup... had been changed to UUID=... The same error had been applied to the previous kernel (2.6.25-14.fc9) so that neither would boot. In short, boot the computer with F9 DVD, choose "Rescue previous installation", press OK to go to CLI, type "chroot /mnt/sysimage", and type "cd boot/grub". "ls" will list, among others, grub.conf. Then type "vi grub.conf" and edit the kernel lines to contain *your* /dev/filesystem instead of your UUID. Then ":write" to save your new grub.conf and ":quit" to exit vi. Once in CLI, type "exit" *twice* and remove the DVD while the system is closing down. It will reboot automatically. > > Part of my grub.conf > > title Fedora (2.6.25.3-18.fc9.i686.PAE) > root (hd0,0) > kernel /vmlinuz-2.6.25.3-18.fc9.i686.PAE ro root=/dev/VG/rootfs rhgb > quiet > initrd /initrd-2.6.25.3-18.fc9.i686.PAE.img > title Fedora (2.6.25.3-18.fc9.i686) > root (hd0,0) > kernel /vmlinuz-2.6.25.3-18.fc9.i686 ro > root=UUID=8741bb6e-dbe0-42c2-a91b-f5e685d70ada rhgb quiet > initrd /initrd-2.6.25.3-18.fc9.i686.img > title Fedora (2.6.25-14.fc9.i686) > root (hd0,0) > kernel /vmlinuz-2.6.25-14.fc9.i686 ro > root=UUID=8741bb6e-dbe0-42c2-a91b-f5e685d70ada rhgb quiet > initrd /initrd-2.6.25-14.fc9.i686.img > > HTH Antti -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
