F-18 installation from KDE Live USB stick
by Timothy Murphy
I've installed the Fedora-18 KDE Live CD on a USB stick,
and am able to boot my laptop from this.
But I find the "Install to Hard Disk" facility
greatly disimproved compared to F-17.
My main gripe is that there appears to be no way
to preserve the current disk partitioning.
The "Custom Install" option seems to have disappeared.
I have a spare partition on my Fedora-17/Windows disk,
and I want to install F-18 on that.
Is this no longer possible?
If not, why not?
I absolutely do not want to use the "Automatic Partioning"
which seems to be all I am offered.
Sorry, Mr Fedora, I have absolutely no idea
what you are going to do to my hard disk,
and I am not in the habit of "buying a pig in a poke".
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College Dublin
11 years, 3 months
Firewalld applet in KDE
by Patrick O'Callaghan
F18 has a new firewall daemon (firewalld) which is intended eventually
to replace the existing system-config-firewall system. From what I can
see, it appears to be accessible via an applet under Gnome. There is
also a command-line tool (firewall-cmd) and a GUI (fireall-config,
though the latter has to be installed manually).
I'm wondering if there are plans for a Plasma applet for this.
poc
11 years, 3 months
Hang your system with firewall-config
by Ed Greshko
This is a fully updated F18 system. I've reproduced this in both a Vbox VM as well as actual system.
You can hang your KDE session by doing the following....
1. Start firewall-config as a normal user.
2. Enter the password as prompted.
3. Do *nothing* with firewall-config for about 4 minutes (I don't know the polkit timeout).
4. Toggle the "Current View" from Runtime to Persistent.
5. Your session is hung.
The cursor moves but you can't enter the password and you can't raise any windows or access the menus.
You can ssh into the system and kill the firewall-config process to regain your system.
--
Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. -- Rick Cook, The Wizardry Compiled
11 years, 3 months
"The key you just pressed is not supported by Qt"
by Mary Ellen Foster
Hello all,
In all previous versions of KDE, I would always use
ctrl-alt-shift-{right,left} as a shortcut for "window to {next,previous}
desktop". However, I'm now unable to use that shortcut (it seems to be
processed as "ctrl-shift-{right,left}", and if I go to the system settings
to try to fix it I can't even set the shortcut.
As soon as I press ctrl-alt-shift (or even alt-shift), I get a popup that
says "The key you just pressed is not supported by Qt". I know this
definitely used to work -- and, indeed, you can see in the system-settings
UI that the old shortcut is still set. It's just not actually working any
more.
I currently have kde-4.9.5 and qt-4.8.4 (Fedora 18, 64-bit). I may try
updating to kde-unstable just to see whether that makes a difference ...
Any ideas on what's going on?
Thanks,
MEF
--
Mary Ellen Foster -- http://www.macs.hw.ac.uk/~mef3/
Interaction Lab -- http://www.macs.hw.ac.uk/InteractionLab
School of Mathematical and Computer Sciences, Heriot-Watt University
Heriot-Watt University is a Scottish charity registered under charity
number SC000278
11 years, 3 months
F17/F18 kde login screen misspelling
by punjabimunda@mail.org
Hello,
I am Ahsan, a silent Linux enthusiat from Finland. I have been using kde f17 and briefly used f18. I want to draw the developers attention to a small login screen issue. If a user has a password in caps and s/he presses caps lock while entering the password, the red color warning text appears that caps lock is emabled. The spelling of enabled is incorrect and 'ed' is missing. Kindly notice and correct it.
br,
Ahsan
11 years, 3 months
trouble with f17->f18 update
by Neal Becker
If you use --enablerepo=kde-unstable,kde-testing
on f17, expect trouble when updating to f18.
I used fedup, which didn't complain, but left with a system where kde wouldn't
start.
You might want to use yum distro-sync before running fedup.
I don't have kde-unstable,kde-testing enabled by default in /etc/yum.repos.d.
Perhaps if you do, fedup will use it and then you won't see this problem.
11 years, 3 months
qt-x11 problem
by Neal Becker
Any ideas about this?
yum check
Loaded plugins: langpacks, presto, refresh-packagekit
1:qt-x11-4.8.4-6.fc17.i686 has missing requires of libtiff.so.3
1:qt-x11-4.8.4-6.fc17.x86_64 has missing requires of libtiff.so.3()(64bit)
yum --enablerepo=kde-testing,kde-unstable info qt-x11
Loaded plugins: langpacks, presto, refresh-packagekit
Installed Packages
Name : qt-x11
Arch : i686
Epoch : 1
Version : 4.8.4
Release : 6.fc17
Size : 33 M
Repo : installed
>From repo : updates
Summary : Qt GUI-related libraries
URL : http://qt.nokia.com/
License : (LGPLv2 with exceptions or GPLv3 with exceptions) and ASL 2.0 and
: BSD and FTL and MIT
Description : Qt libraries used for drawing widgets and OpenGL items.
Name : qt-x11
Arch : x86_64
Epoch : 1
Version : 4.8.4
Release : 6.fc17
Size : 33 M
Repo : installed
>From repo : updates
Summary : Qt GUI-related libraries
URL : http://qt.nokia.com/
License : (LGPLv2 with exceptions or GPLv3 with exceptions) and ASL 2.0 and
: BSD and FTL and MIT
Description : Qt libraries used for drawing widgets and OpenGL items.
11 years, 3 months