Based on the work of a fellow contributor, I've massaged and built a
soprano-backend-sesame2 package for testing purposes, and stuffed into
kde-redhat/unstable F-10 repo.
As I said, it's for testing purposes only, and includes binary .jars,
which aren't built from source... so it's not acceptable yet for
inclusion in fedora proper.
1. This has been a KDE problem for at least ten years:
When one wishes to effect a system configuration, a window pops up, asking
for the root password. Underneath will be a small box that one is instructed
to click to have the root password remembered. I almost always click it, but
despite my dedication, I cannot recall in any version of KDE, neither past
nor present, that the password was EVER remembered.
How is this supposed to work?
2. And, by the way, I have /etc/sudoers set up NOT to ask for the password,
so why does it?
Looks like we'll have
FUDCon Berlin 2009, Jun 26-28
Akademy 2009 (Gran Canaria, Spain), Jul 3-11
coming up near each other.
Myself, I'm holding out against all hope that I'll be able to stay over
to attend both somehow, but I'll venture it lucky enough to get to even one.
Anyone else have hopes or aspirations to come join the fun?
I just updated to Ktorrent 3.2, which seems to have a whole slew of
changes from the previous stable version (3.1.6), however on hitting F1
I get a pop-up saying "The file or folder help:/ktorrent/index.html does
not exist", on top of a Help Center window showing "There is no
documentation available for /ktorrent/index.html."
I had similar problems last year with several KDE apps. Turned out to be
that you had to have devel packages installed to create the manuals.
Ridiculous. Is this the same story again?
Also, the Help Center text as written makes no sense. Why would I want
documentation for the index.html file? It's trying to tell me it has no
documentation for Ktorrent, so why doesn't it just say so?
PS Does anyone else find it annoying that pop-up text is not selectable?
I had to manually copy the first quote above. Not good.
For the last week or two -- it's so easy to just close it so I don't
know how long -- the "Run command" box (the Alt-F2 thing) has been
coming up every time I log in on both my laptop and my netbook -- but
*not* my work desktop machine or either of my husband's computers. All
the computers are running Fedora 10 with KDE 4.2. I don't know (a) why
this would have started happening or (b) why it's only on some
Anyone else seeing this? Any clues why it might be happening?
Mary Ellen Foster -- http://homepages.inf.ed.ac.uk/mef/
Informatik 6: Robotics and Embedded Systems, Technische Universität München
and ICCS, School of Informatics, University of Edinburgh
Anyone interested in helping lead a kde-related fedora-classroom session
I'll try to help, at least, but I can't commit to anything yet.
Either way, I'd like to solicit ideas for topics(1)
(1) other than our usual and generic "any and all things fedora/kde"
session, like what we did last time.
I connect to several mail servers from several different machines because of
the nature of the way I work. I have one machine that is set to delete
messages from my mail servers after 10 days, and all other clients on my other
machines are configured to leave messages on the server. This has worked well
for me over years. But periodically, I get the occasional message from KMail
that it doesn't properly support UIDL and that therefore, leaving/deleting
messages from the server properly may not function. Right now, I have two
machines doing this - one is my principal machine, the one that's set to
delete after ten days, which is a desktop that's been in continuous use since
FC1 days - when I start getting those UIDL error messages, KMail becomes
tortuously slow, and seems to download many of the same messages over and
over; the other machine that's doing this right now is a brand new and fully
updated to regular but not testing software - it's an F10 machine running
inside virtual box.
I've been reading page after page from a google search on "KMail UIDL", but
there's no info so far on how to fix this...