yum update issue
by Rafnews
Hi,
i've just installed Fedora 21 x64 in a virtualbox (as usual) for test.
while running a "yum update" command i get "cannot retrieve metalink for
repository: fedora/21/x86_64. Please verify its path and try again"
it is a fresh install, so i guess the path is missing in yum.conf file.
--
Best Regards
Alain R.
The information contained in this e-mail message is privileged and
confidential and is for the exclusive use of the addressee. The person
who receives this message and who is not the addressee, one of his
employees or an agent entitled to hand it over to the addressee, is
informed that he may not use, disclose or reproduce the contents
thereof. Please do not disclose the contents to anyone, but notify the
sender by return email and delete this email (and any attachments) from
your system. Thank you.
9 years, 3 months
rpmfusion akmod-nvidia and kmodtools
by Tom Horsley
Installed f21 workstation (64 bit) from live image.
Got the f21 rpmfusion repos installed by guessing the
URL from the f20 URLs which are the latest listed on
the rpmfusion web page :-).
Then tried to yum install akmod-nvidia and it kept
puking on installing the kmodtools package because
it didn't have the gpg keys for f20 rpmfusion (and
apparently kmodtools is still an f20 package).
Worked around it by "yum --nogpg install kmodtools"
then everything else seemed to work.
9 years, 3 months
Announcing Fedora 21!
by Matthew Miller
Fedora 21 Release Announcement
==============================
<http://fedoramagazine.org/announcing-fedora-21/>
The Fedora Project is pleased to announce the release of Fedora 21,
ready to run on your desktops, servers, and in the cloud. Fedora 21 is
a game-changer for the Fedora Project, and we think you're going to be
very pleased with the results.
Fedora.next and Fedora 21 Flavors
=================================
As part of the Fedora.next initiative, Fedora 21 comes in three
flavors: Cloud, Server, and Workstation -- whether you're using
Linux on your laptop, using Linux on your servers, or spinning up
containers or images in the cloud, we have what you need to be
successful.
Fedora 21 Base
--------------
Each of the flavors builds on the "base" set of packages for
Fedora. For instance, each flavor uses the same packages for the
kernel, RPM, Yum, systemd, Anaconda, and so forth.
The Base Working Group develops the standard platform for all
Fedora deliverables, which includes the installer, compose tools,
and basic platform for the other flavors. The Base set of packages
*is not* intended for use on its own, but is kept as a small,
stable platform for other initiatives to build on.
Highlights in the Fedora 21 Release
===================================
Fedora 21 Cloud
---------------
The Fedora Cloud Working Group and Special Interest Group (SIG) has
been busy leading up to Fedora 21. Cloud is now a top-level
deliverable for Fedora 21, and includes images for use in private
cloud environments like OpenStack, as well as AMIs for use on
Amazon, and a new "Atomic" image streamlined for running Docker
containers.
* Modular Kernel Packaging for Cloud
Space is precious, and there's little reason to include drivers
for hardware that doesn't exist in the cloud. As part of the work
for this release, the cloud SIG and kernel team split the kernel
into two packages. One package contains the minimum modules for
running in a virtualized environment, the other contains the
larger set of modules for a more general installation. With other
size reduction work, the F21 cloud image is about 25% smaller
than F20, making for faster deployment and more room to whatever
*you* need.
* Fedora Atomic Host
In early April, Red Hat announced Project Atomic, an effort to
provide the tools and patterns for a streamlined operating system
to run containers. The Fedora 21 release is the first to offer an
"Atomic" host for Fedora, which includes a minimal set of
packages and an image composed with rpm-ostree.
While using the same RPMs as other Fedora offerings, the Atomic
host lets you roll back updates (if necessary) as one atomic unit
-- making update management much easier.
Our Atomic image includes Kubernetes and Cockpit for container
management, and will receive updates through the Fedora 21
release cycle as rpm-ostree updates.
Fedora 21 Server
----------------
The Fedora Server flavor is a common base platform that is meant to
run featured application stacks, which are produced, tested, and
distributed by the Server Working Group. Want to use Fedora as a
Web server, file server, database server, or platform for an
Infrastructure-as-a-Service? Fedora 21 Server is for you.
* Fedora Server Management Features
The Fedora Server flavor introduces new Server management
features aimed at making it easier to install discrete
infrastructure services. The Fedora Server introduces three new
technologies to handle this task, rolekit, Cockpit, and OpenLMI.
Rolekit is a Role deployment and management toolkit that provides
a consistent interface to administrators to install and configure
all the packages needed to implement a specific server role.
Rolekit is at an early stage of development in Fedora 21.
Cockpit is a user interface for configuring and monitoring your
server or servers. It is accessible remotely via a web browser.
OpenLMI is a remote management system built atop DMTF-CIM. Use
OpenLMI for scripting management functions across many machines
and for querying for capabilities and monitoring for system
events.
* Domain Controller Server Role
As part of the server role offerings available for Fedora 21, the
Server flavor ships with a role deployment mechanism. One of the
roles offered in 21 is the Domain Controller Service.
The Domain Controller Service packages freeIPA's integrated
identity and authentication solution for Linux/UNIX networked
environments.
A FreeIPA server provides centralized authentication,
authorization, and account information by storing data about
user, groups, hosts, and other objects necessary to manage the
security aspects of a network of computers.
Fedora 21 Workstation
---------------------
The Fedora Workstation is a new take on desktop development from
the Fedora community. Our goal is to pick the best components, and
integrate and polish them. This work results in a more polished and
targeted system than you've previously seen from the Fedora
desktop. We want our desktop operating system to solve your
problems, not be your problem.
* Easy access to all your software
The cornerstone of the Fedora Workstation is the Software
installer, which lets you find all kinds of applications quickly
and easily. The improvements to the Software installer in Fedora
21 provide a responsive and fast user experience. In addition,
Fedora packagers have worked with developers around the world to
greatly improve the number of featured applications.
* Improvements to the Terminal application
We want developers to have a great experience, so a strong
Terminal application is absolutely important. We've integrated a
set of additional features in the Terminal, such as:
- Support for transparent backgrounds
- Automatic title updates to help you identify different terminals
- A simple toggle for disabling shortcuts in the Terminal
- Search for Terminals by name in the GNOME desktop overview
* Experimental Wayland support
Wayland is a new and exciting display server technology that will
power Linux desktops of the future. With Fedora Workstation 21
you can visit the future now, and see how well your applications
work with Wayland. You can also experiment with making your
applications take advantage of Wayland's new capabilities. Much
of the core Wayland development comes from Fedora Workstation
contributors, so this is your chance to try out Wayland straight
from the source.
* DevAssistant
We recognize developers need an easy and straightforward way to
set up many different programming environments. In Fedora
Workstation, we offer the DevAssistant developer helper, which
takes care of this setup for a large number of language runtimes
and IDEs.
To provide the most flexible development environment possible,
DevAssistant integrates with Fedora Software collections, to
provide multiple versions of different languages to suit your
needs. Software Collections allow you to install additional
language support alongside the system software, without any
conflicts. For example, you could use Software Collections to
enable a separate version of Perl or Ruby without conflicting
with the system version.
* Ease of installation
We want the installation of the Fedora Workstation to be as
straightforward and simple as possible. In Fedora Workstation we've
distilled this process down to selecting the layout of your physical
media, and then pressing "Install." (In fact, you can even let the
installer choose the disk layout for you.) And because the future of
installations is not optical disks, we ship with an easy to use tool to
help you create bootable USB sticks -- just download a new Live image,
right-click, and write to USB.
* Web service integration
We recognize you have work to do, and you want to use the tools
that let you get it done. That's why we're working to make all
your applications in Fedora Workstation look and feel the same.
With the ability to run HTML5 web services in a chromeless
window, we aim to make your apps feel like a natural extension to
your desktop. More integration upgrades are coming in future
Fedora Workstation releases.
* Support for high resolution displays (HiDPI)
Technology never stands still, and as a software developer you
are used to using the best technology available. So we've spent a
lot of time and effort on supporting the new generation of HiDPI
displays found on new hardware like many new ultrabook models, or
the Apple Retina display. That's probably why Fedora has been
called the best of HiDPI.
* Exciting roadmap
This Fedora Workstation release is not the end. It's the
beginning of a new era for Fedora on the desktop. We have a
roadmap lined up to bring a range of exciting new technologies to
the Linux desktop:
- Containers
- Smarter virtual machines
- Better development tools
- Improved toolkit integration
- More web integration
- ...and much more
So if you want to be part of the future of the Linux desktop, get
on board now!
Downloads, upgrades, documentation, and common bugs
===================================================
You can start by downloading Fedora 21:
<https://getfedora.org/>
If you are upgrading from a previous release of Fedora, refer to:
<https://fedoraproject.org/wiki/Upgrading>
* Fedora now includes the FedUp utility to enable an easy upgrade to
Fedora 21 from previous releases. See the FedUp page on the
Fedora wiki for more information:
<https://fedoraproject.org/wiki/FedUp>
Documentation
-------------
Read the full release notes for Fedora 21, guides for several languages,
and learn about known bugs and how to report new ones:
<https://docs.fedoraproject.org/>
Fedora 21 common bugs are documented at:
<https://fedoraproject.org/wiki/Common_F21_bugs>
This page includes information on several known non-blocker bugs in
Fedora 20, please be sure to read it before installing!
Spins
-----
In addition to the new Fedora flavors, Fedora users also have the
alternative of Fedora Spins that highlight user favorites like KDE
Plasma Workspaces, Xfce, LXDE, and Sugar on a Stick (SoaS). If
you're interested in trying out one of the spins, head over to the
page for Fedora Spins and grab the spins you're interested in!
<https://spins.fedoraproject.org/>
Contributing
------------
We hope that you're excited to have Fedora 21 in your hands and are
looking forward to using it and exploring its new features and many
improvements over Fedora 20. But that's not all! Fedora never
stands still, we're always working towards a new and better release
and sharing our work with the world. Want to be part of the fun?
It's easy to get involved!
There are many ways to contribute to Fedora, even if it's just bug
reporting. You can also help translate software and content, test and
give feedback on software updates, write and edit documentation, design
and do artwork, help with all sorts of promotional activities, and
package free software for use by millions of Fedora users worldwide. To
get started, visit <https://join.fedoraproject.org> today!
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
9 years, 3 months
Re: f21 runs dnf check on every shell startup
by Neal Becker
Thanks for the hint!
bash -x
...
++++ complete -D -F _completion_loader
++++ [[ -d /etc/bash_completion.d ]]
++++ [[ -r /etc/bash_completion.d ]]
++++ [[ -x /etc/bash_completion.d ]]
+++++ LC_ALL=C
+++++ command ls /etc/bash_completion.d
+++++ ls /etc/bash_completion.d
++++ for i in '$(LC_ALL=C command ls "$BASH_COMPLETION_COMPAT_DIR")'
++++ i=/etc/bash_completion.d/dnf-completion.bash
++++ [[ dnf-completion.bash !=
@(@(#*#|*@(~|.@(bak|orig|rej|swp|dpkg*|rpm@(orig|new|save))))|Makefile*|(a)())
]]
++++ [[ -f /etc/bash_completion.d/dnf-completion.bash ]]
++++ [[ -r /etc/bash_completion.d/dnf-completion.bash ]]
++++ . /etc/bash_completion.d/dnf-completion.bash
+++++++ dnf help
+++++++ sed -e 's/\( \)\+.*$//g' -e '/^$/d' -e '/^[A-Z ]/d' -e /:/d
Repository google-chrome is listed more than once in the configuration
And there is the message!
I have seen sometimes long hangs trying to ssh into the machine. After
printing 'last login...' and before getting this message and a bash
prompt. I'm just guessing this is what is causing sometimes long delay.
On Tue, Dec 9, 2014 at 10:11 AM, Igor Gnatenko <i.gnatenko.brain(a)gmail.com>
wrote:
> If we're talking about bash startup, so there nothing what takes long time.
>
> bash should load functions from dnf-completion.bash and should not
> execute something.
>
> I think would be good to get logs from command `bash -x`
>
> On Tue, Dec 9, 2014 at 6:06 PM, Jan Zelený <jzeleny(a)redhat.com> wrote:
> > On 9. 12. 2014 at 18:52:29, Igor Gnatenko wrote:
> >> On Tue, Dec 9, 2014 at 5:34 PM, Neal Becker <ndbecker2(a)gmail.com>
> wrote:
> >> > I'm sorry, I'm confused.
> >> > The problem is that it seems with every shell startup, some dnf
> command is
> >> > run (perhaps check-update?). I did not run the command. I don't
> want it
> >> > to run - sometimes it slows shell startup.
> >>
> >> You mean GNOME shell startup? or what startup?
> >
> > IIUIC that would be bash startup. Is is possible that the bash completion
> > script does some preloading at that time?
> >
> > Jan
>
>
>
> --
> -Igor Gnatenko
>
--
*Those who don't understand recursion are doomed to repeat it*
9 years, 3 months
Re: f21 runs dnf check on every shell startup
by Jan Zelený
On 9. 12. 2014 at 18:52:29, Igor Gnatenko wrote:
> On Tue, Dec 9, 2014 at 5:34 PM, Neal Becker <ndbecker2(a)gmail.com> wrote:
> > I'm sorry, I'm confused.
> > The problem is that it seems with every shell startup, some dnf command is
> > run (perhaps check-update?). I did not run the command. I don't want it
> > to run - sometimes it slows shell startup.
>
> You mean GNOME shell startup? or what startup?
IIUIC that would be bash startup. Is is possible that the bash completion
script does some preloading at that time?
Jan
9 years, 3 months
Re: f21 runs dnf check on every shell startup
by Neal Becker
I'm sorry, I'm confused.
The problem is that it seems with every shell startup, some dnf command is
run (perhaps check-update?). I did not run the command. I don't want it
to run - sometimes it slows shell startup.
What command did you want me to run to diagnose this?
On Tue, Dec 9, 2014 at 9:31 AM, Igor Gnatenko <
ignatenkobrain(a)fedoraproject.org> wrote:
> dnf with debuglevel=10... Paste dnf.log
>
> -Igor Gnatenko
> On Dec 9, 2014 5:23 PM, "Neal Becker" <ndbecker2(a)gmail.com> wrote:
>
>> which log should I be looking at? What log entries would be relevant?
>>
>> On Tue, Dec 9, 2014 at 9:14 AM, Igor Gnatenko <
>> ignatenkobrain(a)fedoraproject.org> wrote:
>>
>>> On Dec 9, 2014 3:47 PM, "Jan Zelený" <jzeleny(a)redhat.com> wrote:
>>> >
>>> > On 9. 12. 2014 at 07:06:52, Neal Becker wrote:
>>> > > After fedup f20->f21, on every shell startup I see:
>>> > >
>>> > > Repository google-chrome is listed more than once in the
>>> configuration
>>> > >
>>> > > I don't want this check run on each shell start. For one thing, I
>>> believe
>>> > > it is causing sometimes long delays. How do I turn it off?
>>> >
>>> > Sounds like it's caused by dnf bash completion script. Adding Igor
>>> into the
>>> > loop, as he is the author of that script.
>>> I'll check. Can you provide debug log?
>>> >
>>> > Jan
>>> --
>>> -Igor Gnatenko
>>>
>>>
>>
>>
>> --
>> *Those who don't understand recursion are doomed to repeat it*
>>
>
--
*Those who don't understand recursion are doomed to repeat it*
9 years, 3 months
Re: f21 runs dnf check on every shell startup
by Neal Becker
which log should I be looking at? What log entries would be relevant?
On Tue, Dec 9, 2014 at 9:14 AM, Igor Gnatenko <
ignatenkobrain(a)fedoraproject.org> wrote:
> On Dec 9, 2014 3:47 PM, "Jan Zelený" <jzeleny(a)redhat.com> wrote:
> >
> > On 9. 12. 2014 at 07:06:52, Neal Becker wrote:
> > > After fedup f20->f21, on every shell startup I see:
> > >
> > > Repository google-chrome is listed more than once in the configuration
> > >
> > > I don't want this check run on each shell start. For one thing, I
> believe
> > > it is causing sometimes long delays. How do I turn it off?
> >
> > Sounds like it's caused by dnf bash completion script. Adding Igor into
> the
> > loop, as he is the author of that script.
> I'll check. Can you provide debug log?
> >
> > Jan
> --
> -Igor Gnatenko
>
>
--
*Those who don't understand recursion are doomed to repeat it*
9 years, 3 months
f21 runs dnf check on every shell startup
by Neal Becker
After fedup f20->f21, on every shell startup I see:
Repository google-chrome is listed more than once in the configuration
I don't want this check run on each shell start. For one thing, I believe it is
causing sometimes long delays. How do I turn it off?
--
-- Those who don't understand recursion are doomed to repeat it
9 years, 3 months
No video in News or Youtube ?
by Mickey
F20
Firefox-firefox-34.0-1
Flash-plugin-11.2.202.424
In Addons/plugins Flasplayer is Always Activated.
No videos in News or Youtube.
What ain't installed.
9 years, 3 months
Broken IR remote setup on Fedora 20
by Justin Moore
Hi,
I recently did a clean install of F20 on a new system, and now I'm trying
to get a remote control working. The remote is a Harmony 670 emulating a
Hauppage 350, talking to a Phillips (but Microsoft-branded) receiver. This
remote works beautifully on my old F14 system (and has since 2007 going all
the way back to Fedora Core 6) but I've been utterly unable to get it to
work on F20. I've tried a combination of approaches outlined on a host of
sites, including MythTV, LIRC, ArchLinux, and FedoraProject.
The mceusb kernel module loads just fine.
=== start relevant lsmod
ir_lirc_codec 13021 0
lirc_dev 19504 1 ir_lirc_codec
mceusb 28026 0
rc_core 27490 13
ir_sharp_decoder,lirc_dev,ir_lirc_codec,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,mceusb,ir_mce_kbd_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_sanyo_decoder,rc_rc6_mce
=== end relevant lsmod
When I plug it in, I see this in dmesg:
=== start dmesg
[1363994.259561] usb 3-7: USB disconnect, device number 9
[1364061.976061] usb 3-7: new full-speed USB device number 10 using xhci_hcd
[1364062.141766] usb 3-7: New USB device found, idVendor=0471,
idProduct=0815
[1364062.141768] usb 3-7: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[1364062.141769] usb 3-7: Product: eHome Infrared Transceiver
[1364062.141770] usb 3-7: Manufacturer: Philips
[1364062.141771] usb 3-7: SerialNumber: PH00QtmD
[1364062.143239] Registered IR keymap rc-rc6-mce
[1364062.143310] input: Media Center Ed. eHome Infrared Remote Transceiver
(0471:0815) as
/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/rc/rc0/input30
[1364062.143422] rc0: Media Center Ed. eHome Infrared Remote Transceiver
(0471:0815) as /devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/rc/rc0
[1364062.143568] input: MCE IR Keyboard/Mouse (mceusb) as
/devices/virtual/input/input31
[1364062.143960] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered
at minor = 0
[1364062.276018] mceusb 3-7:1.0: Registered Philips eHome Infrared
Transceiver with mce emulator interface version 1
[1364062.276021] mceusb 3-7:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors
(0x0 active)
=== end dmesg
I see these entries in /proc/bus/input/devices:
=== start devices
I: Bus=0003 Vendor=0471 Product=0815 Version=0000
N: Name="Media Center Ed. eHome Infrared Remote Transceiver (0471:0815)"
P: Phys=usb-0000:00:14.0-7
S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb3/3-7/3-7:1.0/rc/rc0/input34
U: Uniq=
H: Handlers=kbd event5
B: PROP=0
B: EV=100013
B: KEY=fff 0 200108fc32e 237605100000000 0 700158000 419200004001
8e968000000000 10000000
B: MSC=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="MCE IR Keyboard/Mouse (mceusb)"
P: Phys=/input0
S: Sysfs=/devices/virtual/input/input35
U: Uniq=
H: Handlers=sysrq kbd mouse2 event16
B: PROP=0
B: EV=100017
B: KEY=30000 7 ff87207ac14057ff febeffdfffefffff fffffffffffffffe
B: REL=3
B: MSC=10
=== end devices
Running 'ir-keytable' gives me this:
=== start ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event5) with:
Driver mceusb, table rc-rc6-mce
Supported protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
Enabled protocols: NEC RC-5 RC-6 JVC SONY SANYO LIRC other
Name: Media Center Ed. eHome Infrared
bus: 3, vendor/product: 0471:0815, version: 0x0000
Repeat delay = 500 ms, repeat period = 125 ms
=== end ir-keytable
Yet running 'ir-keytable -t' and hitting buttons on the remote gives me
nothing. I see the light on the receiver light up, but nothing shows up.
When I unplug the IR receiver from the new computer and plug it back into
the old one, and press some buttons, I see the old computer receive and
process them just fine, so it's clearly not a remote/receiver/battery issue.
I've been messing around with this on and off for about 15 hours now with
no success. I'd be happy to provide more info on what I've tried, but can
anyone give me tips on what I might be overlooking and/or missing. I'm sure
it's something stupid but I'm about to pull my hair out over this (and
don't get me started about a host of other stuff in F20).
I'll be happy to let you know what other documentation I've read/approaches
I've tried, but this email is long enough as-is.
Thanks,
-jdm
9 years, 3 months