kde December 2013

kde@lists.fedoraproject.org

25 participants
27 discussions

Discontinued in 4.12?
by Peter G. 21 Dec '13

21 Dec '13

I have noticed that... kde-style-oxygen-4.11.4-1.fc20.x86_64 kde-workspace-4.11.4-1.fc20.x86_64 kde-workspace-libs-4.11.4-1.fc20.x86_64 ksysguard-4.11.4-1.fc20.x86_64 ksysguard-libs-4.11.4-1.fc20.x86_64 ksysguardd-4.11.4-1.fc20.x86_64 kwin-gles-4.11.4-1.fc20.x86_64 kwin-gles-libs-4.11.4-1.fc20.x86_64 libkworkspace-4.11.4-1.fc20.x86_64 oxygen-cursor-themes-4.11.4-1.fc20.noarch plasma-scriptengine-python-4.11.4-1.fc20.x86_64 ...never got updated to 4.11.95, 4.11.97 or 4.12. Have they been discontinued?

3 3

fear and loathing on the KDE5 trail (was: Discontinued in 4.12?)
by T.C. Hollingsworth 21 Dec '13

21 Dec '13

On Sat, Dec 21, 2013 at 11:10 AM, Orcan Ogetbil <oget.fedora(a)gmail.com> wrote: > Uh oh. I sense a potential disturbance in the force. I hope the 4to5 > transition experience in Fedora won't be as adventurous as the 3to4 > was. Nope. There will be lots of changes under the hood, but not so much in the way of user-visible changes. The big ticket item is splitting out the big old monolithic kdelibs into 57 separate libraries that each do one thing and one thing well. That effort recently hit a major milestone of actually separating out into different git repositories. [1] There is some work to be done for developers, but much less work is required than the Qt/KDE3->4 transition. I've been watching the commits for porting Kate to KDE5 fly by my e-mail and it's amazing how quickly they got Kate & KWrite up and running on KDE5. [2] The only thing you may notice is some of those under the hood changes will result in greater visual consistency. Right now everything's a grab bag of various theming and GUI implementation. In KDE5 the plan is to render everything in the workspace the same way using the same theming framework, so those jarring differences between different components of the desktop will become a thing of the past. [3] Also, disk and memory use will slightly improve for us KDE users, but vastly improve for those folks using other environments, since instead of a big old kdelibs they'll just need the libraries the app they want uses. So soon your GNOME-using friends will have no excuse not to try out awesome KDE app foo. ;-) Finally, you didn't say it, but before anyone else does—a lot of people seem to be worried that KDE is suddenly going to go all touch-friendly and forget the desktop. This is not the case. As one of the KDE core developers so elegantly puts: "...we do not believe in the 'one interface that runs on both your desktop and your tablet'. We believe in code reuse, in component-reuse (and, where beneficial, drop-in-replacement), compatibility and interoperability; but we also believe that a tablet interface and a desktop interface are not, and should not, be the same thing. The use cases and form factors are just too different. "We have no plans of bastardizing Plasma Desktop into a watered-down attempt at a tablet interface that also sort-of-makes-sense on a laptop. We feel this only produces interfaces that perform OK but not great on either kind of device. We want interfaces that work great on each sort of device." [4] So instead, KDE 5 will provide the ability to switch between various Plasma shells instantly, even automatically when triggered by the appearance of certain devices. You will be able to have a tablet with an awesome Plasma Active touch-based interface, then plug a keyboard and mouse into it and instantly get the full-featured Plasma desktop you know and love. (And you'll still be able to turn that off and get the desktop in tablet mode or Active in laptop mode if that's your thing. KDE's legendary configurability isn't going anywhere either.) There's really nothing to worry about. :-) -T.C. [1] http://lists.kde.org/?l=kde-core-devel&m=138738562930062&w=2 [2] http://kate-editor.org/2013/12/08/kate-on-kde-frameworks-5/ [3] http://aseigo.blogspot.com/2011/05/qt5-kde5.html [4] http://aseigo.blogspot.com/2011/09/more-on-active-strategy.html

1 0

Re: RHEL6 with KDE 4.11 - Network management on KDE
by Rex Dieter 20 Dec '13

20 Dec '13

On 12/19/2013 11:01 AM, Syam Krishnan wrote: > > Hi > > I managed to customize RHEL 6.5 (32-bit) DVD with KDE 4.11 RPMs > (thanks to Rex Dieter et al). > > After installation, for the first login, I selected KDE. But then > there's no way I can configure my network interface. Use NetworkManager-gnome, aka nm-applet -- Rex

4 3

RHEL6 with KDE 4.11 - Network management on KDE
by Syam Krishnan 19 Dec '13

19 Dec '13

1 0

crashing new installation
by Felix Miata 19 Dec '13

19 Dec '13

CPU: 1.13GHz Piii gfx: G400 AGP RAM: .5G 22 installed operating systems across 2 PATA HDs Not simple crashing, but crash triggering reboot!!! I did a minimal HTTP F20 install, upgraded to F21, then added enough of Xorg and KDE to get it to start with startx. The first few starts I forgot to block kscreen and nepomuk from starting. Each start when painting looked complete, I tried to configure the digital clock by adding seconds and applying, whereupon I was returned to the login prompt. Only since setting 'Option "Composite" "Disable"' in xorg.conf*, kscreen autoload off in kdedrc, start nepomuk false Used Soprano Backend null and autostart false for nepomukstrigiservice in nepomukserverrc, and index hidden folders and index newly mounted false in nepomukstrigirc, has crashing been avoided in F21. IIRC, none other of the installed distros have been crashing at all, though they've all had bling disabled for quite some time. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/

1 0

Stopping kscreen service starting
by Roderick Johnstone 18 Dec '13

18 Dec '13

Hi I need to stop the kscreen kded module running for all my users becuase it interacts badly with x2go. I've achieved this by making a file /etc/kde/kdedrc with contents: [Module-kscreen] autoload=false This seems to work fine for the first login of x2go. (I'm using a new testing account). I confirmed that the kscreen service in system settings -> Startup and Shutdown -> Service manager shows kscreen2 not running. However, the Use checkbox is ticked for the kscreen2 service, and on the next login the kscreen2 service is running and messing up my x2go session. ~/.kde/share/config/kdedrc now contains: [$Version] update_info=kded.upd:kde3.0 [Module-kscreen] autoload=true [Module-randrmonitor] autoload=false Can anyone explain please why the kscreen2 service is being switched back on and how I can prevent this from happening? Thanks. Roderick Johnstone

3 9

apper error messages
by Ed Greshko 16 Dec '13

16 Dec '13

Running F19/KDE. Recently, at times, when the apper icon appears on the taskbar to indicate updates are available I'll click on "Install Updates". The process runs and then the following appears in the Notifications.... The task was canceled successfully and no packages were changed. Clicking on "Show Details" give slightly more information.... the script was killed as the action was canceled Checking the yum.log shows all packages were updated and "yum update" indicates nothing to update. Any suggestion as to how to debug or collect more info on what happened to generate the messages?

2 1

Removing Sleep option from Leave tab of kickoff
by Roderick Johnstone 16 Dec '13

16 Dec '13

Hi Can anyone tell me how I prevent the "Sleep" option appearing on the Leave tab of kickoff please. I need to set this system-wide for any user. Thanks Roderick Johnstone

2 1

Re: Criterion revision proposal: KDE default applications
by Bill Nottingham 15 Dec '13

15 Dec '13

"Jóhann B. Guðmundsson" (johannbg(a)gmail.com) said: > The DVD is releng/fesco responsibility, they dictate and decide > what's on it and what not and how it's delivered not the > sub-community's. Really? The KDE SIG has full access to change what gets installed when you install from the DVD. If you're saying it's releng and FESCo's responsibility to fix that, then as a releng and FESCo member, I'll fix it... commit f349ff05510a1f60cb43470cb544d55136c837c3 (HEAD, f20) Author: Bill Nottingham <notting(a)redhat.com> Date: Fri Dec 13 12:22:39 2013 -0500 Drop KDE from the DVD, to avoid blocker bugs due to installed package set. diff --git a/fedora-install-fedora.ks b/fedora-install-fedora.ks index f1a767f..fd9f4e9 100644 --- a/fedora-install-fedora.ks +++ b/fedora-install-fedora.ks @@ -73,13 +73,6 @@ dracut-* @libreoffice @gnome-games -## KDE -@kde-desktop -@kde-apps -@kde-education -@kde-media -@kde-office - ## XFCE @xfce-desktop @xfce-apps @@ -111,7 +104,6 @@ dracut-* @rpm-development-tools @fedora-packager @gnome-software-development -@kde-software-development @x-software-development @virtualization @web-server @@ -139,8 +131,6 @@ autocorr-* eclipse-nls-* hunspell-* hyphen-* -calligra-l10n-* -kde-l10n-* libreoffice-langpack-* man-pages-* mythes-* commit 833fdfaf7ec6a9588b1d51a11b9a2a9d956ab873 (HEAD, master) Author: Bill Nottingham <notting(a)redhat.com> Date: Fri Dec 13 12:25:13 2013 -0500 Drop KDE environment as an installation choice. Live media is the SIG-supported install method. diff --git a/comps-f21.xml.in b/comps-f21.xml.in index 66ff5c5..f462e58 100644 --- a/comps-f21.xml.in +++ b/comps-f21.xml.in @@ -6200,34 +6200,6 @@ </optionlist> </environment> <environment> - <id>kde-desktop-environment</id> - <_name>KDE Plasma Workspaces</_name> - <_description>The KDE Plasma Workspaces, a highly-configurable graphical user interface which includes a panel, desktop, system icons and desktop widgets, and many powerful KDE applications.</_description> - <display_order>10</display_order> - <grouplist> - <groupid>base-x</groupid> - <groupid>standard</groupid> - <groupid>core</groupid> - <groupid>admin-tools</groupid> - <groupid>dial-up</groupid> - <groupid>fonts</groupid> - <groupid>input-methods</groupid> - <groupid>multimedia</groupid> - <groupid>hardware-support</groupid> - <groupid>printing</groupid> - <groupid>guest-desktop-agents</groupid> - <groupid>kde-desktop</groupid> - </grouplist> - <optionlist> - <groupid>kde-apps</groupid> - <groupid>kde-education</groupid> - <groupid>kde-media</groupid> - <groupid>kde-office</groupid> - <groupid>kde-telepathy</groupid> - <groupid>3d-printing</groupid> - </optionlist> - </environment> - <environment> <id>xfce-desktop-environment</id> <_name>Xfce Desktop</_name> <_description>A lightweight desktop environment that works well on low end machines.</_description> Ready to push whenever. Now, I'm ASSuming they don't actually want that. But, to be clear: the installation choices of the assorted desktops on the DVD/netinstall are the provence of those SIGs. If they don't want to maintain them, we can absolutely remove them, just as we'd do for any Spin that was not maintained or tested. Bill

4 4

Re: Criterion revision proposal: KDE default applications
by Adam Williamson 14 Dec '13

14 Dec '13

On Sat, 2013-12-14 at 00:44 +0000, "Jóhann B. Guðmundsson" wrote: > On fös 13.des 2013 20:42, Adam Williamson wrote: > > So avoiding the grandstanding, I'd say FESCo probably is the arbiter of > > 'what major groups do we put on the DVD?', but it's not FESCo's job to > > micro-manage specifically what packages are in each group. > > No but it's their responsibility since it's *them* that manage the DVD ( > the dvd is not sub-communites product ) to deliver the *same* out of the > box experience that the live does to match the expectations of the user > as the sub-community has shown him through the deliverable they make. So, let's rewind a bit and look at things. The main reason we have a divergence is due to space on the live images. Perhaps the simple thing to do going forward is bump KDE and GNOME to 2GB max sizes, so they both have space to include everything they actually want in a default install in their live images, and then have both those groups clean up comps and spin-kickstarts so that DVD installs and live images contain the same package set from comps, then maintain the package set in comps in future and only make package changes in the kickstarts which for some reason absolutely have to be changed on a live image (of which there shouldn't be many)? That should make things cleaner and simpler all around. We could ditch the multiple kickstarts that each desktop currently has; both KDE and desktop have two kickstarts, ostensibly one that's CD sized and one that's larger-than-CD-sized, but this has not really been what they are for years. In fact, when Desktop finally gave up doing CD-sized lives, instead of dropping fedora-livecd-desktop.ks , they just added a few packages back to it and used *it* to build the 1GB live image. So now we have fedora-livecd-desktop.ks which, despite its name, is not CD sized, and fedora-live-desktop.ks , which was meant to be the 'ideal' desktop live from which livecd-desktop.ks would just cut the necessary packages to fit in a CD sized image, yet isn't actually used for anything... anyhow, desktop and KDE teams: what do you think of this idea? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

kde December 2013