For years, I have been using the kdeforge.repo file,
but since a while, I have been having
difficulties/impossibility to get anything.
I spent the last hour trying to muddle through the
various repo files and I am unable to determine which
is the one to use: kde.repo, kdeforge.repo, kde-
Also, and this is where the problem seems to lie, some
of these repo files refer to the mirrorlist at:
while other of these repo files refer to the location
of the mirrorlist at:
No matter which combination I seem to try, dnf hangs
for ages and then returns and error:
Failed to synchronize cache for repo 'kde-unstable'
Cannot download, all mirrors were already tried
without success, disabling.
So, how do I get this working? Which is the correct
repo file and which is the correct location of the
I am currently on kf5 5.21, plasma 5.5 and qt 5.6 from the testing
repos. I just noticed that the i18n from dolphin seems to be broken as
the "general" menu from it is in english, while the rest is German. I
just noticed that the packages are marked by dnf when trying to perform
an update. I am not sure why these packages seems to fail upgrading, so
any ideas? Not sure if I am stuck on some weird package combination or
might be a general issue with the language packs.
[root@phobos ~]# LC_ALL=C dnf update --enablerepo=kde-unstable
Failed to synchronize cache for repo 'kde-unstable', disabling.
] --- B/s | 0 B --:-- ETA
Last metadata expiration check: 0:02:48 ago on Sat Apr 16 20:36:20 2016.
Skipping packages with broken dependencies:
updates 9.2 k
updates 34 M
updates 613 k
Skip 3 Packages
Nothing to do.
[root@phobos ~]# LC_ALL=C dnf repoquery --requires kde-l10n
Last metadata expiration check: 1:47:54 ago on Sat Apr 16 18:52:18 2016.
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
[root@phobos ~]# dnf info kde-filesystem
Letzte Prüfung auf abgelaufene Metadaten: vor 1:48:06 am Sat Apr 16
Name : kde-filesystem
Arch : x86_64
Epoch : 0
Version : 4
Release : 52.fc23
Größe : 3.9 k
Paketquelle : @System
Aus Paketqu : @commandline
Zusammenfas : KDE filesystem layout
Lizenz : Public Domain
Beschreibun : This package provides some directories that are
required/used by KDE.
Oops, forgot to add distribution...
On Sun, Apr 17, 2016 at 8:08 AM, Gerald B. Cox <gbcox(a)bzb.us> wrote:
> On Sun, Apr 17, 2016 at 1:13 AM, Colin J Thomson <
> colin.thomson(a)g6avk.co.uk> wrote:
>> I don't see that bug, I guess because that bug appears on Chromium 51
>> which is
>> the unstable branch.
>> Test it with Chromium 50 (stable)
> Yes, see my previous message about
> where I talk about Chrome stable and unstable branches.
> It's a bit of alphabet (pun intended) soup, but there is no concept of
> stable, beta or unstable in Chromium... that
> only applies to Chrome.
> Chrome 51 is getting ready to move to the beta branch, most likely next
> week - so hopefully this can be
> resolved before it hits stable (which will be around the first week of
> The problem of course is that many people do not run Chrome unstable, and
> of those that do, the subset that use
> libunity is less than that - so not many people have encountered this
> yet. Anyone who encounters this, please
> star the bug.
> I started running unstable due to the previous bug regarding status area
> icons in plasma that made it into stable. You
> can really complain if you don't help test.
Just checking to see if I missed something...
Installed libunity and plasma 5.6
According to http://blog.broulik.de/2016/01/on-being-more-convenient/
I should see some type of notification in the task manager when downloading
a file... I don't see anything at all different.
Has anyone else tested this?
Chrome under KDE session with plasma-desktop >=5.5.95 and libunity
installed is missing the minimize/maximize/close buttons. This also
applies to Chromium...
You may encounter this... if so, please star the bug so it gets some
Thanks for putting libunity out on copr for F23 testing... but unless I am
mistaken, to really test out the functionality I also need plasma-workspace
5.6 - and looks like that is only available for F24+.
Do you have a timeframe when plama-workspace 5.6 will be out in the testing
repo for F23? Not trying to rush you... I'm sure you have other things
with a higher priority.... just asking.
For those of you who don't know what this is all about:
I had already mentioned (twice) that my konsole eat to much memory
(16Gb? not a limit!). And finally I found out that the reason is in
konsole AND mplayer. Somehow the output produced by mplayer caused
kosole eat more and more memory. May be that is a long-long-very-long
strings produced during playing, with typing info, then ^W it, and again
and again. But that still ALL remains in buffer.
Here two cases.
1. How could I flush the buffer? Close tab is not a case as it not
trigger flushing. I don't know why but it doesn't. And I don't whant to
close FULL konsole (what have to for now). I tried to scroll them with
new strings above the buffer's limit but that didn't help.
2. How could I make new konsole thread? Every new konsole window is a
window of existing process. I what a brand new one. Is it possible somehow?
Dmitrij S. Kryzhevich