I am running KDE, but, for some purposes, I find evince works better than
okular. I just did a fedup upgrade to F21 from F20 and everything seems to
be working well so far, but an evince window now has no border or (window
manager) titlebar. One particular annoyance with that, aside from making
that window look funny, is that it makes it hard to move the evince window
to another desktop without dragging it all the way--there's no button that
gives "Move To Desktop". I tried gnome-terminal, just to see if it was
all gnome applications, and it has a perfectly good titlebar and border.
How do I get the titlebar and border back? I would have thought this was
controlled by the destop/window manager, not the individual application,
but I can't find a setting where something special has been done for
That's the good news.
The bad news is:
$ sudo dnf erase NetworkManager-wifi
Package Arch Version Repository
NetworkManager-wifi x86_64 1:0.9.10.0-14.git20140704.fc21 @System 112 k
kde-plasma-nm x86_64 0.9.3.5-3.fc21 @System 3.4 M
kde-plasma-nm-openvpn x86_64 0.9.3.5-3.fc21 @System 418 k
kde-plasma-nm-pptp x86_64 0.9.3.5-3.fc21 @System 154 k
kde-plasma-nm-vpnc x86_64 0.9.3.5-3.fc21 @System 283 k
Remove 5 Packages
My desktop machine doesn't have any Wifi adapter. But I *do* use a
VPN all the time.
This looks like a bad dependency, no?
It's not all bad. I at least got to remove some cruft:
$ sudo dnf erase NetworkManager-adsl NetworkManager-bluetooth
Package Arch Version Repository
NetworkManager-adsl x86_64 1:0.9.10.0-14.git20140704.fc21 @System 27 k
NetworkManager-bluetooth x86_64 1:0.9.10.0-14.git20140704.fc21 @System 92 k
Remove 2 Packages
Garry T. Williams
I cannot help noticing: the Fedora Project is monumentally unfriendly to
KDE these days.
Look at their Product offerings: Cloud, Server, Workstation. And as far
as Fedora's officials are concerned, Workstation = GNOME. GNOME now and
GNOME forever. GNOME, all GNOME, and nothing but GNOME.
With the F21 release, they grudgingly let you upgrade with the
But what happens with F22? Will they Shanghai all us KDE users and force
us to switch to GNOME, or else get out of the Fedora community?
Where is the option to specify KDE as a Product?
I chose KDE for a reason: GNOME is just plain too confusing when it
comes to "switching a user." For that reason, and a whole host of
pleasant discoveries of how well KDE replicates another environment with
which I am familiar, I chose KDE beginning with F12. And I never looked
I just updated to Fedora-21 from Fedora-20/KDE,
and as far as I can see it is no longer possible
to turn off the touchpad on my ThinkPad T510
in System Settings/Hardware/Input Devices
as it used to be?
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin
I selected Fedora over Ubuntu because of KDE support and my CentOS server.
KDE was a major factor. My laptop looks like it came out of a science
fiction movie running KDE. I was hoping for even better integration in the
After update f20->f21, evince was broken. Attempting to operate dialogs (e.g,
printing), would just hang desktop gui.
After setting gtk+ appearance to something other than oxygen-gtk, problem is
-- Those who don't understand recursion are doomed to repeat it
Regularly, after having updated my F21 system with dnf,
I notice that apper suddenly indicates that there are a
few updates available. I rerun dnf and it says nothing
to do. Then, I sometimes even try yum and it also
indicates that no packages are available for update.
Why does apper constantly tell me there are updates
available, even after I just upgraded? What
repositories does it access that the others don't? For,
when I click the install button in the apper plasmoid,
something does appear to occur, although it is not
possible to tell, from the lack of output, whether an
upgrade is, in fact, enacted, but I would presume so.
What is happening?
On 12/03/2014 06:33 AM, Neal Becker wrote:
> fedup gave me the following warnings:
> kde-runtime-libs-4.14.3-2.fc20.x86_64 requires exiv2-libs-0.23-5.fc20.x86_64,
> OpenEXR-libs-1.7.1-6.fc20.x86_64, libgcrypt-1.5.3-2.fc20.x86_64,
> ilmbase-1.0.3-7.fc20.x86_64, libwebp-0.3.1-3.fc20.x86_64
kde-runtime upgrade path should be fixed now,
should get pushed to stable repos soon.
> armadillo-4.500.0-1.fc20.x86_64 requires atlas-3.8.4-13.fc20.x86_64
Outside our control, not a kde-related package.
> kde-workspace-4.11.14-2.fc20.x86_64 requires gpsd-libs-3.9-4.fc20.x86_64
> kwin-4.11.14-2.fc20.x86_64 requires libxcb-1.9.1-3.fc20.x86_64
> Continue with the upgrade at your own risk.
kde-workspace indeed has upgrade path problems, for now, looks like f20
update was pushed stable too soon. Remind me to whap dvratil with a wet
noodle as punishment. :)