Main menu:

Sponsoring

Please consider a small donation:

 

 

Or you can donate bitcoin:

 

Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank

Fame

FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.

Search

My Favourites

Slackware

Calendar

October 2014
M T W T F S S
« Sep    
 12345
6789101112
13141516171819
20212223242526
2728293031  

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

Meta

Getting closer: KDE 4.9 Release Candidate 1

Today, the KDE team officially announced the first release candidate for KDE Software Compilation 4.9. That is less than a day after the source tarballs were posted on the private area where packagers have access. The new KDE release manager is giving “us packagers” a hard time – it was probably done as a penalty for the fact that several of the “big distros” were releasing packages long before the KDE team officially announced them. This was seen by the KDE release team as abusing a privileged position. After all, the sources are released in advance so that packages can be ready when a new release is announced… but those packages should stay under wraps as long as the release team has not given a go-ahead. The discussions on the (private) kde-packager and releaseteam mailing lists were not always friendly.

But. of course compiling the KDE packages is trivial using the modular KDE.SlackBuild script, and I have the packages ready for you – compiled for Slackware-current. The upgrade from Slackware’s KDE 4.8.4 to the 4.9-rc1 release (the version number is 4.8.95) should be trivial. There are three updated dependencies (akonadi, soprano and shared-desktop-ontologies). The new akonadi is a requiremnt for RC1. The RC1 packages also fix the incompatibilities with Slackware-current’s new attica and python packages (the previous Beta2 packages needed some tweaking to work with the latest slackware-current).

Like with the previous betas, I did not bother with anything from “extragear”. Pat Volkerding updated many of those when he added KDE 4.8.4 to Slackware-current. Speaking of 4.8.4 – that is the version which will ship with Slackware 14 unless KDE releases an unplanned bugfix 4.8.5. DO NOT expect KDE 4.9 in the next Slackware. We have a winner with 4.8.4 and we do not want to risk introducing new bugs with a 4.9 zero release when we are basically cleaning up the loose ends in slackware-current.

Enough chatter, back to reality now. While you good folk are waiting for your KDE download, I will continue my fight with VLC dependencies in another Virtual Machine… those are currently giving me headaches, and VLC 2..0.2 has been tagged so I expect an official source tarball any moment.

Get my KDE packages in any of the following locations (the master repository at alien.slackbook.org is severely restricted in bandwidth so using a mirror is always advised):

The accompanying README file contains detailed installation/upgrade instructions.

As you may have noticed when inspecting the above URLs, I have re-arranged my “ktown” repository. People were confused about what version would work with Slackware -current and what would work for 13.37. Also, some people have asked for sources of older releases for which I no longer host the packages.

I moved all the sources out of the package trees, you will now find a “source” directory right at the top level of the repository. Below that will be the sources of all package sets which I currently have in my repository (KDE 4.6.5, 4.7.4, 4.8.4 and 4.8.95, including all the dependencies you may want for compiling it on Slackware 13.37). The packages will be available below a toplevel directory equal to the Slackware version they were compiled for (at the moment those are “13.37” and “current“). Below that you will find the actual KDE versions and further down, the 32-bit and 64-bit packages.

Have fun! Eric

Comments

Comment from escaflown
Posted: June 28, 2012 at 00:22

Thanks Eric! I can now get rid of the older attica :)

Comment from Schmatzler
Posted: June 28, 2012 at 00:41

Thank you! :)

Comment from escaflown
Posted: June 28, 2012 at 02:57

The NetworkManager widget doesn’t see any wired or wireless connection. Does anyone else have that issue?

Comment from silviu
Posted: June 28, 2012 at 08:43

Anybody else noticed that konsole profiles are gone from krunner? Damn I use those a lot as all my remote servers are defined as konsole profiles.

Comment from alienbob
Posted: June 28, 2012 at 11:07

@escaflown

I installed the RC1 onto my desktop but NM shows the wired network there. I can plug in a USB wireless stick when I get home tonight to see what wireless connections do, but my hunch is that the problem is local to your computer.

Eric

Comment from alienbob
Posted: June 28, 2012 at 11:08

Hi silviu

How would I test this? I never use konsole profiles and I have no idea what to look for in krunner.

Eric

Comment from p431i7o
Posted: June 28, 2012 at 11:54

well apparently the leak of memory has gone on 4.8.4, prior to this version after several days of keep KDE up, the system will consume a large amount of memory. As you say, I think we have a winner here :)

Thanks Eric, and I’ll be waiting the VLC packages.
have fun.

Comment from silviu
Posted: June 28, 2012 at 13:12

@escaflown
on my laptop it shows both wired and wireless connections just fine

@alienbob

thanks for the answer.
In konsole go to Settings->manager profiles Since you don’t use them you should only have the default there. Create a new one, name it set a command (this is executed on launching the profile and I use it to ssh some.server.com …. but echo “Hello World” should also work :) )
On the older kde’s (I don’t remember when krunner was introduced) I could then ALT+F2 and type the first letters of the profile name and it would show up. Also when going to ALT+F2, click on the settings icon I would see “konsole profiles” among the plugins Kde 4.8.4 still had it, now it’s gone. I tried locating a changelog for krunner but until now I came up empty.

Comment from David
Posted: June 28, 2012 at 13:21

Thank you very much Eric!

@escaflown
All is ok here with NetworkManager widget.

Comment from Eduardo
Posted: June 28, 2012 at 17:51

Thank you Eric! So far it’s working like a charm.

Comment from Mike Langdon (mlangdn)
Posted: June 29, 2012 at 00:17

Thanks again Eric! Just finished the upgrade and all is well. Also removed attica-0.3.0

Comment from Mike Langdon (mlangdn)
Posted: June 29, 2012 at 00:25

Spoke too soon. I can only launch konsole from a terminal emulator or urxvt. Well, also krunner. The icon in my tray no longer works and konsole is nowhere to be found in kmenu. I’ll just use kmenuedit and recreate it!

Comment from b
Posted: June 29, 2012 at 02:10

Trying to run konsole from krunner produces this error: Service ‘/usr/share/applications/kde4/konsole.desktop’ is malformatted.

Comment from silviu
Posted: June 29, 2012 at 06:12

I got the same issue with konsole on my desktop. Also checking krunner in kde 4.8.4 before updating showed a lot more plugins than in krunner 4.9. I didn’t make a list but I would say that more than half are gone.

Comment from fgcl2k
Posted: June 29, 2012 at 14:18

> We have a winner with 4.8.4
From your previous post I got the impression that 4.8.4 was a regression over 4.8.3 (which runs great on my 13.37) and I see that the gwenview bug is still open.

Comment from escaflown
Posted: June 29, 2012 at 22:45

Thanks all for your feedback. I still have the same issue. When I ran nm-tool from Konsole I got:
#############################
NetworkManager Tool

State: connected (global)

- Device: eth0 [Wired connection 1] ——————————————-
Type: Wired
Driver: r8169
State: connected
Default: yes
HW Address: xxxxxxxxxxxx

Capabilities:
Carrier Detect: yes
Speed: 100 Mb/s

Wired Properties
Carrier: on

IPv4 Settings:
Address: xxxxxxxxxxxxxxxxx
Prefix: xx(xxx.xxx.xxx.x)
Gateway: xxx.xxx.xx.x

DNS: xxx.xx.x.x
DNS: xxx.xx.x.x
DNS: x.x.x.x

- Device: wlan0 —————————————————————-
Type: 802.11 WiFi
Driver: rtl8192ce
State: disconnected
Default: no
HW Address: xxxxxxxxx

Capabilities:

Wireless Properties
WEP Encryption: yes
WPA Encryption: yes
WPA2 Encryption: yes

Wireless Access Points
xxxxx: Infra, xxxxxxxxxx, Freq 2427 MHz, Rate 54 Mb/s, Strength 75 WPA2
xxxxxxx: Infra, xxxxxxxxxx, Freq 2412 MHz, Rate 54 Mb/s, Strength 72
xxxxxxx: Infra, xxxxxxxxx, Freq 2412 MHz, Rate 54 Mb/s, Strength 74
xxxxxx: Infra, xxxxxxxxx, Freq 2412 MHz, Rate 54 Mb/s, Strength 74
xxxxx: Infra, xxxxxxxxx, Freq 2412 MHz, Rate 54 Mb/s, Strength 74
xxxxx: Infra, xxxxxxxxxxxx, Freq 2412 MHz, Rate 54 Mb/s, Strength 74
xxxxxxxxx: Ad-Hoc, xxxxxxxxxxx, Freq 2457 MHz, Rate 11 Mb/s, Strength 75 WEP
######################

which means I’m connected through eth0 but the networkmager widget keeps saying “No network interface”

Comment from alienbob
Posted: June 29, 2012 at 22:51

@fgcl2k,

I am running Slackware-current, with KDE 4.8.4 on this laptop, and the gwenview bug does not manifest itself. The bug report on bugs.de.org has not been closed, but that is not really my call, since new reports (from other distros) still keep get added.

As far as I am concerned, KDE 4.8.4 works very well.

Eric

Comment from alienbob
Posted: June 30, 2012 at 21:46

@b & silviu

I can start krunner and konsole just fine. All I get when I run krunner from a commandline are these two lines, which seem to come with almost every program:

$ krunner
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

But nothing else, and works OK.

Eric

Comment from alienbob
Posted: June 30, 2012 at 21:50

@escaflown,

I am running KDE 4.9-rc1 on this desktop with slackware64-current. I do not have wireless card, but NetworkManager manages my wired connection just fine.

I assume you failed an upgrade to -current and/or KDE 4.9-rc1 somewhere along the path.

You _are_ referring to the KDE networkmanagement widget, are you?

Eric

Comment from escaflown
Posted: July 1, 2012 at 05:51

@Eric: yes I’m referring to the KDE networkmanagement widget. I just noticed that I have NetworkManager-0.9.2.0 and networkmaagement-0.9.0. Could version number mismatch be an issue?

Comment from alienbob
Posted: July 1, 2012 at 12:07

Hi escaflown,

I have these same versions installed – they are the slackware-current official packages.

Eric

Comment from escaflown
Posted: July 1, 2012 at 16:09

@Eric: i will keep digging then.

Comment from silviu
Posted: July 2, 2012 at 08:10

@alienbob

Yes both run fine but after upgrading the konsole icon was gone from kmenu – I had to create a new shortcut
Krunner works fine, just that after the update more than half it’s plugins (start krunner, click on the settings icon [gears] ) There were a lot more there in all previous versions.

Comment from escaflown
Posted: July 2, 2012 at 23:25

@Eric: I finally fixed it but I did it the hard way :) I did a slackpkg clean-system with SBO and alien blacklisted then slackpkg reinstall a ap d e f installer k kde kdei l local n t tcl x xap y and finally slackpkg install-new without installing ksecrets.
It’s the hard way but it got it done :)

Comment from alienbob
Posted: July 3, 2012 at 01:03

@escaflown…

\ö/

It must have been some package which you forgot to install or upgrade. Glad you sorted it out.

Eric

Comment from escaflown
Posted: July 3, 2012 at 03:03

@Eric: by the way, any chance we get kde-telepathy slackbuilds from you?

Comment from alienbob
Posted: July 3, 2012 at 16:27

Hi escaflown

I looked at the requirements for telepathy when I started with the KDE 4.8.x SlackBuild and decided that it requires too many dependencies to make it into Slackware itself
I might try and find some time to build a set of telepathy related packages, but don’t hold your breath!

Eric

Comment from b
Posted: July 3, 2012 at 17:15

@alienbob When you start konsole through krunner, is it using the .desktop file or just running the executable /usr/bin/konsole? Both .desktop and executables in your path are valid sources for krunner. It still seems as though my konsole.desktop has a problem with 4.9 rc1.

Comment from David
Posted: July 3, 2012 at 19:50

Hi Eric,
if I try to use NetworkManager to connect to OpenVPN Server, I receive this error: “The VPN service ‘org.freedesktop.NetworkManager.openvpn’ was not installed.”
I was not able to find “network-manager-openvpn-kde” which seems to solve the problem.
Have you ever faced this issue?

Comment from escaflown
Posted: July 4, 2012 at 02:29

I noticed a little crash with the rc1. If you go in System Settings, then Workspace Appearance, the system settings always crash. It is a repeatable crash on all my boxes. This is the error collected from konsole:

QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
elom@Freemind3:~/Documents$ couldn’t create image from “/home/diau/overlay.png”
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: kwin : path “/usr/lib/kde4/kwin3_b2.so” for “kwin3_b2″
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: kwin : path “/usr/lib/kde4/kwin3_kde2.so” for “kwin3_kde2″
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: “******

The library /usr/lib/kde4/kwin3_kde2.so has no API version
Please use the KWIN_DECORATION or future versions of kwin will no longer load this decoration!
*******”
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: kwin : path “/usr/lib/kde4/kwin3_keramik.so” for “kwin3_keramik”
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: “******

The library /usr/lib/kde4/kwin3_keramik.so has no API version
Please use the KWIN_DECORATION or future versions of kwin will no longer load this decoration!
*******”
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: kwin : path “/usr/lib/kde4/kwin3_laptop.so” for “kwin3_laptop”
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: kwin : path “/usr/lib/kde4/kwin3_modernsys.so” for “kwin3_modernsys”
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: “******

The library /usr/lib/kde4/kwin3_modernsys.so has no API version
Please use the KWIN_DECORATION or future versions of kwin will no longer load this decoration!
*******”
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: kwin : path “/usr/lib/kde4/kwin3_oxygen.so” for “kwin3_oxygen”
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: kwin : path “/usr/lib/kde4/kwin3_plastik.so” for “kwin3_plastik”
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: kwin : path “/usr/lib/kde4/kwin3_qtcurve.so” for “kwin3_qtcurve”
systemsettings(3268)/kwin KDecorationPlugins::loadPlugin: “******

The library /usr/lib/kde4/kwin3_qtcurve.so has no API version
Please use the KWIN_DECORATION or future versions of kwin will no longer load this decoration!
*******”
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0×0
systemsettings: symbol lookup error: /usr/lib/kde4/kwin3_qtcurve.so: undefined symbol: _ZNK25KCommonDecorationUnstable16clientGroupItemsEv

Could anyone else confirm this?

Comment from David
Posted: July 4, 2012 at 08:57

@escaflown
No crash here, sorry ;-)

Comment from silviu
Posted: July 4, 2012 at 09:14

Anybody had any luck finding out where/why half the krunner plugins are gone? I couldn’t find anything online…

Comment from escaflown
Posted: July 4, 2012 at 13:36

@David: Thanks for the information!

Comment from Matt
Posted: July 10, 2012 at 06:45

The NetworkManager widget doesn’t see any wired or wireless connection. Does anyone else have that issue?
Matt.

Comment from alienbob
Posted: July 10, 2012 at 15:20

Matt, perhaps you are missing some new package (i.e. added to Slackware after the 13.37 release)?

Eric

Comment from Matt
Posted: July 11, 2012 at 07:43

Thanks Eric.

Comment from escaflown
Posted: July 11, 2012 at 13:32

rc2 on the way … :)

Comment from alienbob
Posted: July 11, 2012 at 13:44

Yes I know, KDE 4.9-RC2 is on the way, Libre Office 3.5.5 was just released, and I will not have time to create packages in the next two weeks… you are all on your own, people!

I just hope that Pat will not release new glibc or gcc packages in the next two weeks, or you’ll have to wait for multilib versions of those!

Eric

Comment from escaflown
Posted: July 12, 2012 at 00:34

Well, for KDE, your slackbuild scripts already point us in the right dicrection :)

Write a comment