Fwd: [Bug 295970] Magnet torrents don't save to the proper directory
by John Aldrich
Just in case anyone else is wondering... it's supposedly fixed in
KTorrent-4.2.0. As soon as that version is released from testing, I'll
upgrade.
---------- Forwarded Message ----------
Subject: [Bug 295970] Magnet torrents don't save to the proper directory
Date: Thu March 15 2012, 6:37:36 PM
From: nucleo <nucleo(a)fedoraproject.org>
To: jmaldrich(a)yahoo.com
https://bugs.kde.org/show_bug.cgi?id=295970
--- Comment #2 from nucleo <nucleo(a)fedoraproject.org> ---
ktorrent-4.2.0 along with kde-4.8.1 submitted to Fedora 16 updates.
Please, test this update.
--
You are receiving this mail because:
You reported the bug.
-----------------------------------------
10 years, 6 months
f16 kde48 repo no more, use kde-testing instead
by Rex Dieter
since we've got kde-4.8.x in f16's updates-testing for a little while now, I
took the liberty to:
* clear out the dedicated kde48 repo (it's empty now)
* put it all in f16/kde-testing repo instead
and, if all goes well, we should get kde-4.8.x pushed to f16 stable updates
before the end of the week.
-- rex
10 years, 6 months
Re: KMail issues
by Rex Dieter
On 03/12/2012 01:28 AM, Eli Wapniarski wrote:
> On Sunday 11 March 2012 12:24:17 Rex Dieter wrote:
>> On 03/11/2012 11:42 AM, John Aldrich wrote:
>>> I've reported this problem, but the developers don't seem to care about it
>>> -- I regularly receive HTML messages and if I click on the link to render
>>> the HTML and/or load external pictures, it will often cause KMail (Kmail
>>> 2) to crash.
>>
>> For giggles, if you happen to have flash-plugin installed, to uninstall
>> it (temporarily) if that helps?
>>
>> If so, you're experiencing a flash-plugin bug (fixed in 11.2beta and newer)
>>
>
> Tried it Rex... External sources still crashing kmail :(
OK, which bug is tracking this for you?
the flash one was generally qtwebkit-related and/or
https://bugs.kde.org/show_bug.cgi?id=286307
-- rex
10 years, 6 months
Re: yumbackend.py running every few minutes...?
by Rares Aioanei
On 03/13/2012 06:40 AM, Gene Smith wrote:
> Since today's f16 update, yumBackend.py seem to being running 100% cpu
> every few minutes. I think this also happened a few months ago but got
> OK but now it seems to be back.
>
> OK, here's where it's described:
> https://bugzilla.redhat.com/show_bug.cgi?id=752564
>
> I had set my kde apper check for update interval to "weekly" and that
> "fixed" it. But now it doesn't care and just does the check every 5
> minutes regardless.
>
> -gene
>
It's PackageKit, most likely. Try running gpk-prefs.
Best,
--
Rares Aioanei
10 years, 6 months
Ktorrent + magnet links
by John Aldrich
Any idea when/if the bug that exists in KTorrent with respect to NOT saving
downloads in the correct directory will be fixed? Apparently it's a known bug,
but no one seems to be worried about squishing it. It's saving in
~\apps\kio_magnet\ instead of the directory specified in the configs.
10 years, 6 months
F16: kde-plasma-daisy broken
by Reindl Harald
kde-plasma-daisy-0.0.4.25-2.fc15.x86_64
* no updated package for F16 available
* applet does not work "component plasma_applet_daisy" not found
can we have a update for this?
___________________________
kde-baseapps-4.8.1-1.fc16.x86_64
kde-baseapps-libs-4.8.1-1.fc16.x86_64
kde-filesystem-4-38.fc15.x86_64
kdegraphics-thumbnailers-4.8.1-1.fc16.x86_64
kde-i18n-3.5.10-15.fc15.noarch
kde-i18n-German-3.5.10-15.fc15.noarch
kde-l10n-4.8.1-2.fc16.noarch
kde-l10n-German-4.8.1-2.fc16.noarch
kdelibs3-3.5.10-31.fc16.x86_64
kdelibs-4.8.1-1.fc16.x86_64
kdelibs-common-4.8.1-1.fc16.x86_64
kdemultimedia-common-4.8.1-1.fc16.noarch
kdemultimedia-kio_audiocd-4.8.1-1.fc16.x86_64
kdemultimedia-kmix-4.8.1-1.fc16.x86_64
kdemultimedia-libs-4.8.1-1.fc16.x86_64
kdenetwork-common-4.8.1-1.fc16.1.noarch
kdenetwork-kdnssd-4.8.1-1.fc16.1.x86_64
kdenetwork-kget-4.8.1-1.fc16.1.x86_64
kdenetwork-kget-libs-4.8.1-1.fc16.1.x86_64
kdenetwork-kopete-4.8.1-1.fc16.1.x86_64
kdenetwork-kopete-libs-4.8.1-1.fc16.1.x86_64
kdenetwork-krfb-4.8.1-1.fc16.1.x86_64
kdenetwork-krfb-libs-4.8.1-1.fc16.1.x86_64
kdepimlibs-4.8.1-1.fc16.x86_64
kdepimlibs-akonadi-4.8.1-1.fc16.x86_64
kdeplasma-addons-4.8.1-2.fc16.x86_64
kdeplasma-addons-libs-4.8.1-2.fc16.x86_64
kde-plasma-daisy-0.0.4.25-2.fc15.x86_64
kde-plasma-ihatethecashew-0.4-3.fc15.x86_64
kde-printer-applet-4.8.1-1.fc16.noarch
kde-runtime-4.8.1-2.fc16.x86_64
kde-runtime-flags-4.8.1-2.fc16.noarch
kde-runtime-libs-4.8.1-2.fc16.x86_64
kdesdk-common-4.8.1-1.fc16.noarch
kdesdk-kcachegrind-4.8.1-1.fc16.x86_64
kdesdk-kioslave-4.8.1-1.fc16.x86_64
kdesdk-kmtrace-4.8.1-1.fc16.x86_64
kdesdk-kmtrace-libs-4.8.1-1.fc16.x86_64
kdesdk-kompare-4.8.1-1.fc16.x86_64
kdesdk-kompare-libs-4.8.1-1.fc16.x86_64
kdesdk-kpartloader-4.8.1-1.fc16.x86_64
kdesdk-okteta-4.8.1-1.fc16.x86_64
kdesdk-okteta-libs-4.8.1-1.fc16.x86_64
kdesdk-scripts-4.8.1-1.fc16.noarch
kde-settings-4.7-14.fc16.noarch
kde-settings-kdm-4.7-14.fc16.noarch
kde-settings-ksplash-4.7-14.fc16.noarch
kde-settings-plasma-4.7-14.fc16.noarch
kde-settings-pulseaudio-4.7-14.fc16.noarch
kdesvn-1.5.5-3.fc15.x86_64
kdeutils-common-4.8.1-1.fc16.noarch
kdewebdev-3.5.10-11.fc16.x86_64
kdewebdev-libs-3.5.10-11.fc16.x86_64
kde-workspace-4.8.1-2.fc16.x86_64
kde-workspace-libs-4.8.1-2.fc16.x86_64
lockdev-1.0.3-10.fc16.x86_64
lovelock-backgrounds-kde-14.91.1-1.fc16.noarch
lovelock-kde-theme-14.91.0-2.fc16.noarch
polkit-kde-0.99.0-3.fc16.x86_64
pykde4-4.8.1-1.fc16.x86_64
qalculate-kde-0.9.7-3.fc15.x86_64
qtcurve-kde4-1.8.11-1.fc16.x86_64
subversion-kde-1.6.17-5.fc16.x86_64
verne-backgrounds-kde-15.92.1-1.fc16.noarch
verne-kde-theme-15.91.0-1.fc16.noarch
10 years, 6 months
KMail even worse
by Timothy Murphy
Is anyone except me still using KMail?
The recent enormous yum-update (600MB in my case) of Fedora-16/KDE
seems to have left KMail in an even more unstable state.
It crashes perhaps half the times I use it,
and what is worse, it has developed a habit of not crashing,
but simply disappearing.
I see nothing reported in /var/log/messages after these episodes.
I tried sending the error (backtrace) as suggested after one crash,
but as far as I could see KDE bugzilla was out of action at the time.
Am I alone in thinking that Fedora, and in particular KDE,
is becoming too complicated?
There seem to me to be too many interacting applications
which depend on each other for survival.
The idea of a single program that does one thing (and does it well)
seems to have gone out of fashion.
I see that in Italy they have a Minister of (or for) Simplification.
I wish there were something like that in KDE.
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College Dublin
10 years, 6 months
Custom workspace arrangement?
by Marko Vojinovic
Hi everyone! :-)
I have configured eight virtual desktops (or workspaces, or whatever they are
called) on my stock up-to-date F16 KDE. They are automatically arranged in 2x4
fashion, two rows with four columns in the pager. I want a 1x8 geometry, so
that there is no desktop "above" or "below" the current one. I can configure
the pager to display the desktops in this fashion, but the rest of KDE somehow
still "knows" that desktop 5 is "below" desktop 1. This is visible when
switching desktops via the keyboard, or using some 3D desktop effects, or
otherwise.
So, how do I configure KDE to arrange my desktops into a 1x8 geometry?
The point is that I want to use right/left screen edge to move to the
next/previous desktop, but I do *not* want anything to happen when I hit the
top/bottom screen edge. However, I cannot configure screen edge action
separately for each edge, and OTOH I cannot arrange eight desktops so that
there is no desktop above/below the current one.
I'd appreciate any pointers on how to disentangle this mess. ;-)
Best, :-)
Marko
10 years, 6 months
KDE 4.8.1 update: kwin crashing
by Patrick O'Callaghan
Last night I noticed a lot of 4.8.* rpms in updates-testing, so I
decided to have go:
sudo yum --enablerepo=updates-testing update "KDE Software Compilation"
Now I find that Kwin crashes on login, leaving me without a window
manager, and hence unable even to focus on a console window. Kwin is
from kde-workspace-4.8.1-2.fc16.x86_64. The problem occurs even when I
rename .kde and try again.
Writing this from FVWM (which is very functional and fast BTW :-)
poc
10 years, 6 months
