Good morning,
The KDE SC 4.13 is available in experimental-snapshots. The version of all the packages right now is 4.13.0 except for kdelibs (which was already updated to 4.13.1) and kde-workspace (which is still 4.11.x because there won't be any kde-workspace 4.12.x or 4.13.x, as you probably already know).
KDE SC 4.13.1 was already released so the packages will be updated and moved to unstable soon if that's possible.
Warning: in this KDE SC release nepomuk was replaced by baloo. Unfortunately right now you can't deactivate it pressing a button like you did with nepomuk, this issue will be taken care of, however if that's a big problem for you feel free to hold your dist-upgrade until it's fixed.
Cheers.
Update went well, no problems discovered.
Thanx for your good work santa! ;)
Please also notice, that KDE 4.13.1 enters sid:
$ apt-cache policy kdelibs5-data
kdelibs5-data:
Installiert: 4:4.13.1-1
Installationskandidat: 4:4.13.1-1
Versionstabelle:
*** 4:4.13.1-1 0
500 http://debian/ sid/main amd64 Packages
100 /var/lib/dpkg/status
4:4.12.4-90r0 0
500 http://packages.siduction.org/kdenext/ unstable/main amd64 Packages
500 http://ftp.spline.de/pub/siduction/extra/ unstable/main amd64 Packages
4:4.12.4-1 0
500 http://debian/ testing/main amd64 Packages
4:4.12.2-90r0 0
500 http://packages.siduction.org/kdenext/ kdepim-ng/main amd64 Packages
4:4.8.4-4 0
500 http://debian/ stable/main amd64 Packages
The move to the sid packages went without any errors.
Zitat von: hefee in 2014/05/18, 16:57:07
Please also notice, that KDE 4.13.1 enters sid:
Only a few bits were uploaded so far. Given the way the person in charge of kde manages the uploads, I strongly recommend to not dist-upgrade until 4.13.1 is in kdenext/unstable.
KDE SC 4.13.1 moved to unstable. If you are using the experimental new kdepim packages in kdepim-ng you should wait a bit more for dist-upgrading because the kdepim 4.13 isn't packaged yet.
With regarding to the "I can't disable baloo" issue there is an alternate kcm for baloo, this kcm allows you to disable the file indexing (unlike the default one). To install this kcm you can just do a simple "apt-get install baloo-kcmadv".
Nice work :) all good here
confirmed, nothing gets removed, all fine ;)
Sharing the same nice (usual) experience here too ;D
thanks
Ercolinux
Users that are fully upgraded to kde 4.13 are using baloo instead of nepomuk, that sucked donkey dicks for a long time. So now, the rewrite baloo does the same job of indexing in the background. You can use the search in deolphin, but I would ask you to use a new tool that is not in official kde yet, but that santa packaged for us. It is called milou and is a search widget and more.
apt install plasma-widget-milou After that, activate the widget and log out and back in to kde. Now your widget should be ready to work. you can customize the order in which results are presented.
For a nice read on milou and the plans for it, look at:
http://vhanda.in/blog/2014/03/introducing-milou/
and for a deeper look:
http://aseigo.blogspot.de/2014/03/krunner-sprinter-and-milou-sorting-it.html
Please report, how it works for you. It crashes plasma for santa but works fine for musca and me, which might be related to gfx and drivers.
greetz
devil
Thanks Santa, Devil and anyone else involved.
Seems to be working fine here.
Zitat von: devil in 2014/05/22, 22:27:18
Users that are fully upgraded to kde 4.13 are using baloo instead of nepomuk,......
greetz
devil
Hi devil,
is there a possibilty to check my box whether it is fully to 4.13?
Zitat von: mylo in 2014/05/23, 23:51:10
Zitat von: devil in 2014/05/22, 22:27:18
Users that are fully upgraded to kde 4.13 are using baloo instead of nepomuk,......
greetz
devil
Hi devil,
is there a possibilty to check my box whether it is fully to 4.13?
If you have kdenext in your sources.list you should be (except for kdepim which is 4.4).
Zitat von: mylo in 2014/05/23, 23:51:10
is there a possibilty to check my box whether it is fully to 4.13?
bei mir sieht es nach DU so aus:
4.12 gibt es demnach nicht mehr, dafür aber 4.11 ?!
cas@lifo: $ dpkg -l|grep kde|grep -v 4.13
ii gfxboot-themes-siduction-december-kde 2013.12.30 all tool to test and create graphical boot logos (siduction December)
ii gfxboot-themes-siduction-december-kde-core 2013.12.30 all graphical boot logos for siduction December kde
ii kde-config-gtk-style 3:2.2.1-1 i386 KDE configuration module for GTK+ 2.x and GTK+ 3.x styles selection
ii kde-config-touchpad 0.8.1-2 all touchpad configuration tool (synaptiks)
ii kde-plasma-desktop 5:84+mod2 i386 KDE Plasma Desktop and minimal set of applications
ii kde-style-oxygen 4:4.11.9-90r0 i386 Oxygen widget style
ii kde-window-manager 4:4.11.9-90r0 i386 K window manager (KWin)
ii kde-workspace 4:4.11.9-90r0 all KDE Plasma Workspace components
ii kde-workspace-bin 4:4.11.9-90r0 i386 core binaries for the KDE Plasma Workspace
ii kde-workspace-data 4:4.11.9-90r0 all shared data files for the KDE Plasma Workspace
ii kde-workspace-kgreet-plugins 4:4.11.9-90r0 i386 KDE greet libraries for authentication
ii kdebase-workspace-bin 4:4.11.9-90r0 all transitional package for kde-workspace-bin
ii kdesudo 3.4.2.4-2 i386 sudo frontend for KDE
ii libkdecorations4abi2 4:4.11.9-90r0 i386 library used by decorations for the KDE window manager
ii libkworkspace4abi2 4:4.11.9-90r0 i386 library for the kdebase workspace
ii oxygencursors 0.0.2012-06-kde4.8-2.1 all Oxygen mouse cursor theme
ii polkit-kde-1 0.99.1-1 i386 KDE dialogs for PolicyKit
ii siduction-art-kde-december 2014.01.26.1 all KDE theme for the siduction 2013.2.1 release
ii siduction-settings-kde-december 2014.02.10 all provide default KDE settings for siduction
Zitat von: cas in 2014/05/24, 00:28:40
Zitat von: mylo in 2014/05/23, 23:51:10
is there a possibilty to check my box whether it is fully to 4.13?
bei mir sieht es nach DU so aus:
4.12 gibt es demnach nicht mehr, dafür aber 4.11 ?!
cas@lifo: $ dpkg -l|grep kde|grep -v 4.13
ii gfxboot-themes-siduction-december-kde 2013.12.30 all tool to test and create graphical boot logos (siduction December)
ii gfxboot-themes-siduction-december-kde-core 2013.12.30 all graphical boot logos for siduction December kde
ii kde-config-gtk-style 3:2.2.1-1 i386 KDE configuration module for GTK+ 2.x and GTK+ 3.x styles selection
ii kde-config-touchpad 0.8.1-2 all touchpad configuration tool (synaptiks)
ii kde-plasma-desktop 5:84+mod2 i386 KDE Plasma Desktop and minimal set of applications
ii kde-style-oxygen 4:4.11.9-90r0 i386 Oxygen widget style
ii kde-window-manager 4:4.11.9-90r0 i386 K window manager (KWin)
ii kde-workspace 4:4.11.9-90r0 all KDE Plasma Workspace components
ii kde-workspace-bin 4:4.11.9-90r0 i386 core binaries for the KDE Plasma Workspace
ii kde-workspace-data 4:4.11.9-90r0 all shared data files for the KDE Plasma Workspace
ii kde-workspace-kgreet-plugins 4:4.11.9-90r0 i386 KDE greet libraries for authentication
ii kdebase-workspace-bin 4:4.11.9-90r0 all transitional package for kde-workspace-bin
ii kdesudo 3.4.2.4-2 i386 sudo frontend for KDE
ii libkdecorations4abi2 4:4.11.9-90r0 i386 library used by decorations for the KDE window manager
ii libkworkspace4abi2 4:4.11.9-90r0 i386 library for the kdebase workspace
ii oxygencursors 0.0.2012-06-kde4.8-2.1 all Oxygen mouse cursor theme
ii polkit-kde-1 0.99.1-1 i386 KDE dialogs for PolicyKit
ii siduction-art-kde-december 2014.01.26.1 all KDE theme for the siduction 2013.2.1 release
ii siduction-settings-kde-december 2014.02.10 all provide default KDE settings for siduction
... and except for kde-workspace, which is 4.11.x (there are no 4.12.x or 4.13.x releases of kde-workspace).
... on my computer plasma desktop always crashes upon restart after installing the milou widget.
Fully upgraded siduction, nouveau driver.
Greetings
Tom
Zitat von: samoht in 2014/05/24, 14:25:39
... on my computer plasma desktop always crashes upon restart after installing the milou widget.
Fully upgraded siduction, nouveau driver.
Greetings
Tom
Exact same behaviour here. Unfortunately I don't have time to debug the thing.
It is not the nouveau driver per se, works fine for someone on IRC with that driver.
greetz
devil
Das Plasma-Widget Milou funktioniert hier auf 3 Rechnern problemlos (2x Intel/ 1x Nvidia mit dem proprietäre Treiber). So etwas gab es früher unter Gnome 2 auch. Ich finde es gut.