Pulseaudio volume control crashes sound
by Paul Cartwright
I was trying to make a call on skype, and they couldn't hear me ( I
guess I need to plug in a microphone;-)
but in the process I ran the PA volume control, or tried to. It started,
brought up a window saying something like " trying to talk to sound
server, or connecting to sound server... I forget exactly", then the PA
volume control window disappeared, and I had no sound. Besides logging
out & back in, what can I do to bring back the sound?? how do you
restart pulseaudio??
Fedora 20 amd_64..
what are my options to get rid of Pulseaudio?? install alsa??
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
10 years
BZ 1010572 || systemd useless socket
by Soham Chakraborty
Howdy folks,
Typically this is a discussion material in the bugzilla itself but I am
wondering that if any of you has hit this bug on F20, then is there any way
around or some hack fix? Or rather even, any way to bring the system back
to usable state at all?
https://bugzilla.redhat.com/show_bug.cgi?id=1010572
I don't see any progress on the bugzilla. And in case anyone has found
anything...
Thanks,
10 years
Re: grub2
by Patrick Dupre
> Subject: Re: grub2
>
> Hi,
> My experience with kernel installs in a grub 2 environment is that
> I have to always manually run grub2-mkconfig and grub2-install as the
> kernel install wants to run Gruby to update the grub configuration and
> on my system, from Fedora 17 onwards, Gruby always fails with
> authorisation issues even though all O/S updates are run under sudo with
> full admin access. So my question would be, are you grub issues as a
> result of the kernel install running Gruby rather than grub2-mkconfig?
>
> regards,
> Steve
>
Obviously,
During an update of the kernel, there is no run of:
grub2-mkconfig -o /boot/grub2/grub.cfg
When I run it by my self, I get a different file!
Why?
Thank for your help.
> >
> >> ----- Original Message -----
> >> From: Chris Murphy
> >> Sent: 05/05/14 07:35 AM
> >> To: Community support for Fedora users
> >> Subject: Re: grub2
> >>
> >> On May 4, 2014, at 4:33 PM, Patrick Dupre <pdupre(a)gmx.com> wrote:
> >>
> >>> Hello,
> >>>
> >>> After the installation of a new kernel (typically during an update).
> >>> There is a change of the file /boot/grub2/grub.cfg.
> >>>
> >>> However, the new menuentry created is not correct.
> >>> The new one includes
> >>> linux /vmlinuz-3.14.2-200.fc20.x86_64 root=/dev/mapper/VolGrpSys_DK1-root
> >>> which wrong.
> >>> I can change it manually.
> >>>
> >>> I cannot guess where the information is found!
> >>> the
> >>> set root='lvm/VolGrpSys_DK1-root'
> >>>
> >>> is correct
> >> The first one looks correct, the second one doesn't. Can you either post the entire grub.cfg, or you can also edit an older entry and check what root= it uses. For any rootfs on LVM, I expect root=/dev/mapper/VG-LV. When updating the kernel, it calls grubby, which should just create a new entry based on a previous entry only updating the name of the kernel and initramfs accordingly. I haven't seen it change the root entry.
> >>
> >> The other thing you can do is create a new grub.cfg from scratch by using
> >>
> >> grub2-mkconfig -o /boot/grub2/grub.cfg
> >>
> >> This is the same command the installer used when Fedora was installed.
> >>
> > Thank you for the information.
> > When I run grub2-mkconfig -o /boot/grub2/grub.cfg.test
> > the generated file is correct.
> > I am not able to reproduce manually what happens during the 2 last kernal updates.
> > I will check again after the next update.
> >
> > ===========================================================================
> > Patrick DUPRÉ | | email: pdupre(a)gmx.com
> > Laboratoire de Physico-Chimie de l'Atmosphère | |
> > Université du Littoral-Côte d'Opale | |
> > Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
> > 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
> > ===========================================================================
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years
screen goes black in fedora 20 live cd
by Fatemeh Mehdizadeh
Hi all,
I want to use live cd of fedora 20 but when it boots up suddenly it's
screen goes
black.
I search about this and do the following steps:
1. In /etc/default/grub, I remove "nomodeset"
2. grub2-mkconfig -o /boot/grub2/grub.cfg
3.reboot
Now my system is very bright and nice but just for some minutes! After some
minutes the screen goes black. when I add nomodeset I don't see black
screen but in live cd I see it. Also with nomodeset it can't recognize my
graphic card(radeon).
Thanks.
10 years
Has anyone else's sound broken today?
by Someone
This happened to me some weeks ago, and it just happened again: I
rebooted, and sound simply doesn't play. I'm running the LXDE spin, and
I'm wondering if anyone else has run into this issue.
10 years
Tips on burning to Bluray (BD-R) media under Fedora 20
by Steven P. Ulrick
Hello, Everyone
I just installed a new Asus Bluray drive/burner and everything seems
to work fine so far except for one thing: I can't burn to Bluray
(BD-R) media using K3B. K3B detects my media correctly, even tells me
in the burn dialog that I have an "Empty BD-R medium" in the drive.
I am trying to burn 21.4 GiB to a disc that K3B automatically detects
as having a capacity of 23.3 GiB. So, things look good so far...
Then I do the following:
1. "Open the burn dialog for the current project"
2. Click the "Burn" button.
3. This soon results in this interesting message:
Found medium: Empty BD-R medium
Please insert an empty medium of size 21.4 GiB or larger into drive
ASUS BC-12B1ST b (/dev/sr0)
Load Eject Cancel
As you probably assume, clicking "Load" just redraws the above quoted
error message...
Right now I am using mkisofs to make an image of the same 21.4 GiB of
data that I want to test this new drive with. We'll see what
happens...
Oh yeah, this new drive rips CD's perfectly, as well as burning to
single layer DVD media. I don't have any dual layer around to play
with.
Thank you for your help,
Steven P. Ulrick
10 years
CPUFREQ on a Thinkpad Yoga i7 in a new Fedora 20 install
by Alan E. Davis
I had a good experience, almost perfect, with Fedora some months ago,
staring with the Beta of F20. Since then I've tried several Linux distros,
each of them as usual, with some issue to separate itself from the rest. I
have a new Lenovo Yoga ultrabook and want to ruin LInux on. I have been
through 3 or 4. So I thought, "Let's try Fedora again."
The install went well on this UEFI system, installing the other linux
distros on other partitions, as well as the Windows Boot Loader, on the
Grub menu. I am happy, Fedora is awesome.
With the exception of a couple of wrinkles.
First, I cannot seem to install Jupiter or any other useful cpufrequency
tool. And with Fedora, I only see two governor options: performance, and
powersave. This is extremely frustrating. This laptop is running an Intel
i7 Mobile processor that touts a high CPU freq, but this is only in a
"turbo" mode. Other distros have picked up at least four, on this same
machine. What are the limitations I am facing here? Kernel, modules, or
the inavailability of certain packages, like Jupiter, which I am starting
to like quite a lot?
As a more general remark, Fedora 20 seems to have left a number of other
packages behind as well.
I ran into a brick wall as far as documentation on this issue, the issue
about cpu frequency.
I have now resorted to Desktop Manager roulette to try to find one that
supports this. The E17, for example, cpufreq tool, which works fine
elsewhere, does not function.
Thank you,
Alan Davis
10 years
Re: grub2
by Patrick Dupre
> Subject: Re: grub2
>
> Hi,
> My experience with kernel installs in a grub 2 environment is that
> I have to always manually run grub2-mkconfig and grub2-install as the
> kernel install wants to run Gruby to update the grub configuration and
> on my system, from Fedora 17 onwards, Gruby always fails with
> authorisation issues even though all O/S updates are run under sudo with
> full admin access. So my question would be, are you grub issues as a
> result of the kernel install running Gruby rather than grub2-mkconfig?
Hello,
The issue appears after I cloned a the boot and / partitions.
>
> regards,
> Steve
>
> On 05/05/2014 08:39 PM, Patrick Dupre wrote:
> >
> >> ----- Original Message -----
> >> From: Chris Murphy
> >> Sent: 05/05/14 07:35 AM
> >> To: Community support for Fedora users
> >> Subject: Re: grub2
> >>
> >> On May 4, 2014, at 4:33 PM, Patrick Dupre <pdupre(a)gmx.com> wrote:
> >>
> >>> Hello,
> >>>
> >>> After the installation of a new kernel (typically during an update).
> >>> There is a change of the file /boot/grub2/grub.cfg.
> >>>
> >>> However, the new menuentry created is not correct.
> >>> The new one includes
> >>> linux /vmlinuz-3.14.2-200.fc20.x86_64 root=/dev/mapper/VolGrpSys_DK1-root
> >>> which wrong.
> >>> I can change it manually.
> >>>
> >>> I cannot guess where the information is found!
> >>> the
> >>> set root='lvm/VolGrpSys_DK1-root'
> >>>
> >>> is correct
> >> The first one looks correct, the second one doesn't. Can you either post the entire grub.cfg, or you can also edit an older entry and check what root= it uses. For any rootfs on LVM, I expect root=/dev/mapper/VG-LV. When updating the kernel, it calls grubby, which should just create a new entry based on a previous entry only updating the name of the kernel and initramfs accordingly. I haven't seen it change the root entry.
> >>
> >> The other thing you can do is create a new grub.cfg from scratch by using
> >>
> >> grub2-mkconfig -o /boot/grub2/grub.cfg
> >>
> >> This is the same command the installer used when Fedora was installed.
> >>
> > Thank you for the information.
> > When I run grub2-mkconfig -o /boot/grub2/grub.cfg.test
> > the generated file is correct.
> > I am not able to reproduce manually what happens during the 2 last kernal updates.
> > I will check again after the next update.
> >
> > ===========================================================================
> > Patrick DUPRÉ | | email: pdupre(a)gmx.com
> > Laboratoire de Physico-Chimie de l'Atmosphère | |
> > Université du Littoral-Côte d'Opale | |
> > Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
> > 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
> > ===========================================================================
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years
amd video card on dell latitude
by François Patte
Bonjour,
Does anyone experienced the use of catalyst driver on Dell latitude
E6540 with video card AMD RADEON HD 8790M under fedora?
Thank you for attention.
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte
10 years