kde December 2015

kde@lists.fedoraproject.org

38 participants
45 discussions

KDE on Fedora - Continuous Integration proposal
by Helio Chissini de Castro 23 Dec '15

23 Dec '15

Hello all Everyone knows that recently KDE SIG became more and more present and active. The goal is towards make KDE a good citzen on Fedora world. On latest meeting, i put under scrutiny to have a continuous integration process to keep up to date on recent releases. The initial idea is keep a continuous build on fix branch commits, not a daily yet, but this will be evaluated if this initial process proves a winning choice. So, Rex Dieter asked me to present the possible solutions, and open the discussion here until a final decision is be made. I will not discuss the resources needed now, because this will be defined depending on the solution we decide. Please be constructive. So here we are of the options: 1 - Using rawhide directly - This will make us have less work on the official releases since is already submitted on main Fedora database. We will need a secondary machine to run a setup script on jenkins ( or similar ). What counts against this procedure is that packages will be available only to rawhide users, limiting our test field ground. We will rely on a semi-complex process on look on kde git tree, built the tarballs, generate the packages and send to compilation on koji 2 - Using Copr kdesig directly - This will make us have less work similar as previous option, same external machine to jenkins ( or similar ). On the pro side of this solution, we can have all arches and fedora releases, including epel 7, been tested and have packages available for many users. What counts against is that we will need more extra work to the moment that we decide that the package x.y.z is good to consumption on the release servers ( koji ) 3 - Use KDE infrastructure and build our packages there. Before someone raise the argument that KDE project doesn't look some place to do this, recently we have the Noon project, that is building basically a Debia/Ubuntu distro inside the project fully accepted. So, there's no ground reasons to us request same thing if needed. Under KDE infrastructure, we could use their jenkins CI and at same time we would be glued on the KDE servers easing the git version pooling. The downside on this is that the generated artifacts will not be in a repository, so we still need a secondary machine to get the repository and at same time decide where to go the results. I personally think this is last resort, because will be too much work and could end up in not be successful 4 - The Hybrid solution - We get Copr or Rawhide solutions and add KDE Jenkins CI as the control machine. Using the command line capabilities of both koji and copr, we can easily setup a big compile job on some of this ones, controlled by the machine on KDE infra. This is my particular choice using copr, even not been the most simple, since we connect the both interested tech parts, KDE and Fedora, been KDE ready on the jb setup, git control on KDE repo, and Copr have all necessary Fedora parts to build the results. What counts against it is the initially complicated setup on integrate both techies, but i think is manageable. So, let's open for discussions. Regards, and Froeh Weihnachten :-)

1 0

Creating a LiveKDE USB stick
by Timothy Murphy 23 Dec '15

23 Dec '15

I see that RedHat recommend in <http://www.redhatguides.com/create-a-centos-7-bootable-usb-drive/> that one should create a CentOS LiveKDE USB stick under Windows using the Linus Live USB Creator app. I've been using Fedora LiveUSB Creator on a Fedora laptop. I'm wondering if there is any CentOS app for this? I know I can do it directly with dd, but I'd like to add some persistent storage, if that is possible. Incidentally, all the information I have seen on CentOS USB sticks assume one is running GNOME. Is there any specific KDE documentation on this? -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

4 5

KTorrent shutdown plugin missing
by Syam Krishnan 22 Dec '15

22 Dec '15

Hello, Did something happen with KTorrent recently? I was out of town for a week and got back today and updated my Fedora 23 (x86-64) machine. Now KTorrent doesn't have the 'shutdown' plugin - the one which is used to automatically shutdown the computer when one or more torrents finish downloading. Searching the web, I get only a discussion on arch linux forums: https://lists.archlinux.org/pipermail/arch-dev-public/2015-December/027595.… which basically says that kdebase-workspace package from KDE4 is being dropped and kTorrent has to be rebuilt without linking against it which results in loss of the shutdown plugin. Did something similar happen on Fedora too? Installed packages: ktorrent.x86_64 4.3.1-19.fc23 ktorrent-libs.x86_64 4.3.1-19.fc23 libktorrent.x86_64 1.3.1-15.fc23 PS: I hope this is not related: http://osdir.com/ml/kde-commits/2015-12/msg04246.html Thanks, Syam

2 5

Re: KTorrent shutdown plugin missing
by Rex Dieter 21 Dec '15

21 Dec '15

I assure you, it is there, for example, http://koji.fedoraproject.org/koji/rpminfo?rpmID=7134513 See /usr/lib/kde4/ktshutdownplugin.so being listed now -- Rex ________________________________________ From: Syam Krishnan <syamcr(a)gmail.com> Sent: Monday, December 21, 2015 1:39 PM To: kde(a)lists.fedoraproject.org Subject: Re: KTorrent shutdown plugin missing On 12/21/2015 09:28 PM, Rex Dieter wrote: > OK, mind testing this build? > > http://koji.fedoraproject.org/koji/buildinfo?buildID=706727 I downloaded both RPMs, installed and ran KTorrent. But the plugin is still not to be found. Syam _______________________________________________ kde mailing list kde(a)lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/kde@lists.fedoraproject.org

2 2

konsole memory usage
by Dmitrij S. Kryzhevich 21 Dec '15

21 Dec '15

Hi, could anybody suggest how to investigate this: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3674 krege 20 0 5262016 4,393g 75960 S 7,6 14,0 39:23.07 konsole Very annoying to restart it. Dmitrij

2 3

Re: kdelibs-4.14.15-1.fc23.x86_64: kopete closes agaian
by Rex Dieter 19 Dec '15

19 Dec '15

Arg, I went through all the trouble of putting the upstream commit fixing this into git, but then forgot to actually *apply* the patch. Fixing now, kdelibw-4.14.15-2 should be better, sorry. -- Rex ________________________________________ From: Reindl Harald <h.reindl(a)thelounge.net> Sent: Saturday, December 19, 2015 11:29 AM To: Mailing-List fedora-kde Subject: kdelibs-4.14.15-1.fc23.x86_64: kopete closes agaian well, with the latest build we are exactly in the same situation as before Sat Dec 05 2015 "revert upstream commit causing kopete crashes for now (kde#355275)" only difference is *sometimes* you can close a message window when you don#t have written anything, but most of the time kopete goes away _______________________________________ * Fri Dec 18 2015 Rex Dieter <rdieter(a)fedoraproject.org> - 6:4.14.15-1 - 4.14.15 (kde apps 15.12.0) - include a few post-4.14.15 commits (kparts, python related) * Wed Dec 09 2015 Rex Dieter <rdieter(a)fedoraproject.org> 6:4.14.14-4 - make VFolderMenu::loadDoc KDebug instead of KWarning * Sat Dec 05 2015 Rex Dieter <rdieter(a)fedoraproject.org> 6:4.14.14-3 - revert upstream commit causing kopete crashes for now (kde#355275) Dec 19 15:20:22 Updated: kde-runtime-libs-15.12.0-1.fc23.x86_64 Dec 19 15:20:25 Updated: kde-runtime-15.12.0-1.fc23.x86_64 Dec 19 15:20:25 Updated: kde-runtime-flags-15.12.0-1.fc23.noarch Dec 19 18:08:44 Updated: 6:kde-apps-rpm-macros-4.14.15-1.fc23.noarch Dec 19 18:08:44 Updated: 6:kdelibs-common-4.14.15-1.fc23.x86_64 Dec 19 18:08:45 Updated: 6:kdelibs-ktexteditor-4.14.15-1.fc23.x86_64 Dec 19 18:08:45 Updated: 6:kdelibs-webkit-4.14.15-1.fc23.x86_64 Dec 19 18:08:48 Updated: 6:kdelibs-4.14.15-1.fc23.x86_64

2 1

menu-editor is broken in 5.5
by Reindl Harald 19 Dec '15

19 Dec '15

am i the only one where the menu-editor no longer works? it appears sometimes like changes as remove the description are saved because you see the same state when open it again but after logout/login anything as before when i manually edit the .desktop-file in the userhome after logout/login it get applied - one reason more why i am terrible angry that "lancelot" is not ported to KDE5 - it was it's own process you can kill and just start with ALT+F2 -> "lancelot" to make sure it realizes changes however, the menu-editor now is a terrible broken blackbox

2 1

kdelibs-4.14.15-1.fc23.x86_64: kopete closes agaian
by Reindl Harald 19 Dec '15

19 Dec '15

well, with the latest build we are exactly in the same situation as before Sat Dec 05 2015 "revert upstream commit causing kopete crashes for now (kde#355275)" only difference is *sometimes* you can close a message window when you don#t have written anything, but most of the time kopete goes away _______________________________________ * Fri Dec 18 2015 Rex Dieter <rdieter(a)fedoraproject.org> - 6:4.14.15-1 - 4.14.15 (kde apps 15.12.0) - include a few post-4.14.15 commits (kparts, python related) * Wed Dec 09 2015 Rex Dieter <rdieter(a)fedoraproject.org> 6:4.14.14-4 - make VFolderMenu::loadDoc KDebug instead of KWarning * Sat Dec 05 2015 Rex Dieter <rdieter(a)fedoraproject.org> 6:4.14.14-3 - revert upstream commit causing kopete crashes for now (kde#355275) Dec 19 15:20:22 Updated: kde-runtime-libs-15.12.0-1.fc23.x86_64 Dec 19 15:20:25 Updated: kde-runtime-15.12.0-1.fc23.x86_64 Dec 19 15:20:25 Updated: kde-runtime-flags-15.12.0-1.fc23.noarch Dec 19 18:08:44 Updated: 6:kde-apps-rpm-macros-4.14.15-1.fc23.noarch Dec 19 18:08:44 Updated: 6:kdelibs-common-4.14.15-1.fc23.x86_64 Dec 19 18:08:45 Updated: 6:kdelibs-ktexteditor-4.14.15-1.fc23.x86_64 Dec 19 18:08:45 Updated: 6:kdelibs-webkit-4.14.15-1.fc23.x86_64 Dec 19 18:08:48 Updated: 6:kdelibs-4.14.15-1.fc23.x86_64

1 0

KMail address-completion
by Timothy Murphy 18 Dec '15

18 Dec '15

Where does KMail get its address-completions from? Is it possible to edit or remove these? Many of the completions offered to me are bizarre inventions, while e-mail addresses I have used hundreds of times are ignored. -- Timothy Murphy gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin

3 5

Breeze Dark icon theme has been broken in kf5-5.17 update
by Sudhir Khanger 17 Dec '15

17 Dec '15

Hi, Another update more bugs. I use Breeze Dark desktop theme and Breeze icon theme. I use Breeze dark because I can't see anything in the breeze desktop theme. I need that contrast and black background for things to be visible. * Battery icon border is missing if you use breeze dark desktop theme. Changing icon theme between light and dark variant doesn't do anything. Using Breeze Dark icon theme break other things. * ownCloud icon is also hardly visible. Screenshots:- http://imgur.com/a/hlA63 I have tried logging out and I have already cleared cache. $ sudo dnf history info 99 | grep breeze Upgraded breeze-icon-theme-5.16.0-2.fc23.noarch @updates $ sudo dnf downgrade breeze-icon-theme Last metadata expiration check performed 0:00:00 ago on Fri Dec 18 00:10:10 2015. Error: package breeze-cursor-theme-5.5.0-1.fc23.noarch conflicts with breeze- icon-theme < 5.4.3-4 provided by breeze-icon-theme-5.4.2-1.fc23.noarch (try to add '--allowerasing' to command line to replace conflicting packages) -- Regards, Sudhir Khanger, sudhirkhanger.com.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde December 2015