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

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 406 other subscribers

My Favourites

Slackware

Calendar

November 2018
M T W T F S S
« Oct    
 1234
567891011
12131415161718
19202122232425
2627282930  

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current

RSS SBo

Meta

KDE Plasma5 for Slackware – october ’18 batch

Today the Plasma developer team released Plasma 5.14.1 which was what I was waiting for. I was a bit hesitant to add a major new release (5.14.0) to my monthly refresh for Slackware and opted for this point release.

And now “KDE-5_18.10” has been uploaded to the ‘ktown‘ repository. Again I was able to offer a full set of updates.

What’s new

The October release of KDE Plasma5 for Slackware contains the KDE Frameworks 5.51.0, Plasma 5.14.1 and Applications 18.08.2. All this on top of Qt 5.11.2 which was updated inbetween the two monthly ‘ktown’ releases.
There were two updates in the ‘extras’ section for Applications: new versions for ‘krita’ and ‘okteta”. The ‘deps’ section saw some changes as well: ‘PyQt5’ was updated to work properly with Qt 5.11.2, a newer version of ‘sip’ had to be added for that same reason – it replaces the somewhat older Slackware package. And a new package ‘python-enum34’ package had to be added, it is a dependency for the Python2 support in PyQt5.

The incremental releases of Frameworks and Applications are focusing on bugfixing and stability improvements, but Plasma 5.14 is a bigger change compared with the 5.13 that was part of my last month’s ‘ktown’ release. Let’s repeat the highlights from the releasenotes:

  • There’s a new Display Configuration widget for screen management which is useful for presentations.
  • The Audio Volume widget now has a built in speaker test feature moved from Phonon settings.
  • The Network widget now works for SSH VPN tunnels again.
  • Switching primary monitor when plugging in or unplugging monitors is now smoother.
  • The lock screen now handles user-switching for better usability and security.
  • You can now import existing encrypted files from a Plasma Vault.
  • The Task Manager implements better compatibility with LibreOffice.
  • The System Monitor now has a ‘Tools’ menu full of launchers to handy utilities.
  • The Kickoff application menu now switches tabs instantly on hover.
  • Widget and panels get consistent icons and other user interface improvements.
  • Plasma now warns on logout when other users are logged in.
  • The Breeze widget theme has improved shadows.
  • The Global menu now supports GTK applications. This was a ‘tech preview’ in 5.13, but it now works out of the box in 5.14.

More features were added – to Plasma Discover and to the Wayland stack, both of which I skip in my ‘ktown’ releases.

Go get it

Download the KDE-5_18.10 from the usual location at https://slackware.nl/alien-kde/current/latest/ . Check out the README file in the root of the repository for detailed installation or upgrade instructions.

I will generate a new Plasma Live ISO soon. You will find it in https://slackware.nl/slackware-live/latest/

Have fun! Eric

Comments

Comment from lamerix
Posted: October 17, 2018 at 07:34

Hello Eric,
Are those packages build against the new icu4c (that got pushed to current today) ?

Comment from Gérard Monpoontet
Posted: October 17, 2018 at 09:19

Current ChangeLog:

(Those of you using Plasma 5 or various third party packages should know by
now what it means when icu4c gets a bump in -current. You may want to wait
a few days for those things to appear again rebuilt against this)

Comment from alienbob
Posted: October 17, 2018 at 09:23

No, the packages have not been built against the new icu4c. Pat’s updates surprised me too. Just wait a bit with upgrading to the latest -current if you are running KDE Plasma5, like the Slackware-current ChangeLog.txt cautions you.
I will check what packages need to be recompiled and get to do that after I return home from work.

Comment from Gérard Monpontet
Posted: October 17, 2018 at 09:56

Just for info, Eric:
on current QScintilla is on ‘2.10.7’ version, kdeconnect-1.3.2 is available, OpenAL-1.19.1, also.

Comment from Gérard Monpontet
Posted: October 17, 2018 at 10:29

Also in Current, gpgme is on (1.12.0) version 😉
( ChangeLog,)fri Oct 12 19:24:43 UTC 2018 )

Comment from Eduardo
Posted: October 17, 2018 at 13:45

Hi Eric, thank you!
I note about the warnings on updating current.
By the way, it seems like your ktown packages still put some *.la libraries, if you have time perhaps you might like to look into that.
Otherwise, the latest update is running smoothly here. Thanks again!

Comment from Marcus_777
Posted: October 17, 2018 at 14:27

Uff, it looks like a big part of recompilation. Unicode is everywhere. For example(libicui): kdeinit5, kdostartupconfig5, kapplymousetheme, ksplashqml, etc…

Pingback from Links 17/10/2018: Elementary OS 5.0 “Juno” Released, MongoDB’s Server Side Public Licence | Techrights
Posted: October 17, 2018 at 18:30

[…] KDE Plasma5 for Slackware – october ’18 batch […]

Comment from alienbob
Posted: October 17, 2018 at 20:00

Marcus, what you see are indirect dynamic dependencies. Which means, the binaries you mention link against Qt5 libraries, and Qt5 has a direct dependency in icu4c libraries.
Which means, after recompiling qt5 (which will take ages unfortunately) most of those perceived library issues will be resolved automatically.
Bottomline: do not use “ldd” to find direct dependencies.
Instead, use “readelf -d” and look for the lines that have “NEEDED” in them. Those are the direct dependencies.

Comment from Marcus_777
Posted: October 17, 2018 at 21:50

Sorry, my fault. I do not tested it. I only typed objects from error log on one PC. Autoupdate script was faster than me. 🙂
Thanks for “readelf -d” I did not know that. Usually use ” objdump -p /path/to/program | grep NEEDED”

Comment from alienbob
Posted: October 17, 2018 at 21:55

Auto-updating a Slackware-current installation? Not a good idea…

Comment from Marcus_777
Posted: October 17, 2018 at 22:43

I know, only for testing purpose(and laziness) on one pc. At least it is fun to repair a malfunctioning system. 🙂 Man will learn a lot.

Comment from chrisretusn
Posted: October 18, 2018 at 08:56

Thanks! Installed, working well as expected. Yeah that icu4c update caught me by surprise too.

Comment from Omar
Posted: October 18, 2018 at 09:44

Hello Eric, first than all thank you very much! I really was enjoying KDE plasma even in my office – I know I shouldn’t -, but I got a lot of troubles with the update of the icu4c to 63.1 kde only lies the 61.1 and not even the ln -s link trick works. At the end I had to remove every clue of KDE on my slack. Do you think that it could be a solution any time soon? or maybe compiling – and waiting for hours – may solve the problem ? Thank you again !!

Comment from alienbob
Posted: October 18, 2018 at 12:53

Omar, and anyone else reading this:
VERY important to realize if you use slackware-current, is that you should NEVER automatically upgrade to the latest batch of packages.
ALWAYS FIRST read the ChangeLog.txt file and search for possible breakage of 3rd party packages.

If you see a warning in the ChangeLog.txt that goes “Shared library .so-version bump.” this means that any program depending on this library will be broken after the upgrade.
And if the above message is shown for packages like boost, icu4c, harfbuzz, or poppler, you know that a LOT of programs will be broken.

In such a case, it is advised to wait with upgrading, and start with reading news articles for clues as to the potential impact.

In this case we are talking about now, the icu4c update unfortunately requires compiling a lot of packages in ‘ktown’. The biggest is ‘qt5’ and that takes a long time to finish. And currently I have issues in the chain, I am stuck at QScintilla because of an apparent new issue with PyQt5.

If you already did the upgrade, there;s no other way except wait for my updates. In the meantime, you can use XFCE if you need a Desktop Environment. I will release new 64bit packages first, to avoid delays, and then I will recompile the 32bit packages where needed.

Comment from Omar
Posted: October 18, 2018 at 15:00

Thank you Eric, now I learned the lesson, hehe. Slackware always techs you – sometimes in a bad way but it does -. I am using XFCE and now and so on I will read the ChangeLog.txt file. I was trying to downgrade but it could come with other issues, I think it is better to wait – also for the LibreOffice, it was broken too-. Again, thank you very much and I am glad to help if you need it. 🙂

Comment from Deny Dias
Posted: October 18, 2018 at 18:40

I ignored the ChangeLog.txt. It hurts! 😛

I’ll patiently wait for the recompiled stuff, Eric. Thanks for your heads up.

Comment from Regnad Kcin
Posted: October 18, 2018 at 21:07

Working and Looking good. Noto-CJK fonts no longer causing problems with SCIM. There is now an option to set window translucency! Operation smooth overall.

Comment from alienbob
Posted: October 18, 2018 at 22:45

I am facing issues with recompiling qt5, qt5-webkit and QScintilla so I cannot proceed with the remaining Plasma recompile candidates for now.
I need to figure out why the qt5/qt5-webkit packages are incomplete. In the meantime I have uploaded a “icu4c-compat” package to my regular repository. It contains the icu4c shared libraries of all the previous couple of years’ packages and it hopefully resolves the present issues until I get the recompile working properly.
See http://www.slackware.com/~alien/slackbuilds/icu4c-compat/

Comment from Ricardo J. Barberis
Posted: October 18, 2018 at 22:59

Eric, after I upgraded I’m having problems with some PyQt5 programs too, mainly git-cola (which I maintain on SBo).

I tracked the error to sip/python2 in case it might be useful with your problems (git-cola uses qtpy, which is a wrapper around PyQt4, PyQt5 and PySide).

I haven’t yet attempted to recompile sip, will check and report back.

These are the errors I’m getting:

$ git-cola
Traceback (most recent call last):
File “/usr/bin/git-cola”, line 53, in
from cola.main import main
File “/usr/share/git-cola/lib/cola/main.py”, line 6, in
from . import app
File “/usr/share/git-cola/lib/cola/app.py”, line 15, in
from qtpy import QtCore
File “/usr/share/git-cola/lib/qtpy/__init__.py”, line 175, in
raise PythonQtError(‘No Qt bindings could be found’)
qtpy.PythonQtError: No Qt bindings could be found

$ slf /usr/lib64/python2.7/site-packages/sip.so
sip-4.19.13-x86_64-1alien: usr/lib64/python2.7/site-packages/sip.so

$ python
Python 2.7.15 (default, Jun 17 2018, 22:57:51)
[GCC 7.3.0] on linux2
Type “help”, “copyright”, “credits” or “license” for more information.
>>> import sip
Traceback (most recent call last):
File “”, line 1, in
ImportError: /usr/lib64/python2.7/site-packages/sip.so: undefined symbol: _Py_FalseStruct
>>> quit()

$ python3
Python 3.6.6 (default, Jul 31 2018, 15:43:11)
[GCC 8.2.0] on linux
Type “help”, “copyright”, “credits” or “license” for more information.
>>> import sip
>>> quit()

Comment from Ricardo J. Barberis
Posted: October 18, 2018 at 23:00

BTW, whatever happened to the “Subscribe to posts” button?

Comment from Ricardo J. Barberis
Posted: October 18, 2018 at 23:37

I downloaded the files from https://slackware.nl/alien-kde/source/latest/deps/sip/ and put a ‘make clean’ before ‘python configure.py’ in the Slackbuild, and that seems to have done the trick for the python module.

Your package seems to have installed the python3 module in the python2 path:

sip-4.19.8-x86_64-2.txz ## from Slackware64-current
$ ls -l /usr/lib64/python*/site-packages/sip.so
-rwxr-xr-x 1 root root 140440 abr 13 2018 /usr/lib64/python2.7/site-packages/sip.so
-rwxr-xr-x 1 root root 140376 abr 13 2018 /usr/lib64/python3.6/site-packages/sip.so

sip-4.19.13-x86_64-1alien.txz ## from your repo
$ ls -l /usr/lib64/python*/site-packages/sip.so
-rwxr-xr-x 1 root root 140312 oct 11 17:50 /usr/lib64/python2.7/site-packages/sip.so
-rwxr-xr-x 1 root root 140312 oct 11 17:50 /usr/lib64/python3.6/site-packages/sip.so
$ cmp /usr/lib64/python*/site-packages/sip.so ; echo $?
0

$ ll /usr/bin/sip{,3}
-rwxr-xr-x 1 root root 398608 oct 11 17:50 /usr/bin/sip
-rwxr-xr-x 1 root root 398608 oct 11 17:50 /usr/bin/sip3
$ cmp /usr/bin/sip{,3} ; echo $?
0

## Newly compiled package with ‘make clean’ added
$ ls -l /tmp/package-sip/usr/lib64/python*/site-packages/sip.so
-rwxr-xr-x 1 root root 148632 oct 18 18:12 /tmp/package-sip/usr/lib64/python2.7/site-packages/sip.so
-rwxr-xr-x 1 root root 140376 oct 18 18:12 /tmp/package-sip/usr/lib64/python3.6/site-packages/sip.so
$ cmp /tmp/package-sip/usr/lib64/python*/site-packages/sip.so
/tmp/package-sip/usr/lib64/python2.7/site-packages/sip.so /tmp/package-sip/usr/lib64/python3.6/site-packages/sip.so differ: char 25, line 1

$ ls -l /tmp/package-sip/usr/bin/sip{,3}
-rwxr-xr-x 1 root root 398648 oct 18 18:12 /tmp/package-sip/usr/bin/sip
-rwxr-xr-x 1 root root 398648 oct 18 18:12 /tmp/package-sip/usr/bin/sip3
$ cmp /tmp/package-sip/usr/bin/sip{,3} ; echo $?
0

Comment from bam
Posted: October 18, 2018 at 23:47

Plasma Discover is very welcomed. Any plans to include it, Eric?

Comment from Ricardo J. Barberis
Posted: October 18, 2018 at 23:47

PyQt5 seems partially affected too:

$ ll /usr/lib64/python*/site-packages/dbus/mainloop/pyqt5.so
-rwxr-xr-x 1 root root 23264 oct 11 20:22 /usr/lib64/python2.7/site-packages/dbus/mainloop/pyqt5.so
-rwxr-xr-x 1 root root 23264 oct 11 20:22 /usr/lib64/python3.6/site-packages/dbus/mainloop/pyqt5.so
$ cmp /usr/lib64/python*/site-packages/dbus/mainloop/pyqt5.so ; echo $?
0

Comment from alienbob
Posted: October 18, 2018 at 23:52

Ricardo, the place to subscribe to the blog and receive emails about new posts is at the top right of the page.

Comment from alienbob
Posted: October 18, 2018 at 23:53

bam, I do not see any value for plasma-discover in a Slackware distribution.

Comment from alienbob
Posted: October 19, 2018 at 00:06

Ricardo, what I will do is reverse the build order (python2 / python3) in the sip package and rename the python2 version of sip to sip2 instead of renaming the python3 based sip to sip3. That should get rid of these issues. The likely cause is that I did a similar reversing of building the python2 and python3 based code and it should be done the same in both.
Why did I do this reversal? Because the KItemModels Framework now requires the python3 based code in PyQt5 and so python3 had to become the default python in sip/PyQt5.
At least, that is my theory.

Comment from Ricardo J. Barberis
Posted: October 19, 2018 at 01:55

Re. subscribe button: my bad, I meant the “subscribe to new comments” button, I think it’s wordpress feature.

Re. PyQt5: I recompiled it with a make clean and git-cola keeps using PyQt4.
In python2’s shell I get:

>>> from PyQt5 import QtCore
import PyQt5 # directory /usr/lib64/python2.7/site-packages/PyQt5
# /usr/lib64/python2.7/site-packages/PyQt5/__init__.pyc matches /usr/lib64/python2.7/site-packages/PyQt5/__init__.py
import PyQt5 # precompiled from /usr/lib64/python2.7/site-packages/PyQt5/__init__.pyc
dlopen(“/usr/lib64/python2.7/site-packages/PyQt5/QtCore.so”, 2);
Traceback (most recent call last):
File “”, line 1, in
ImportError: No module named sip
>>>
>>> from PyQt5 import QtCore
>>> quit()

Weird that it fails the first time (which is why git-cola falls back to PyQt4) but works the second :/

I’ll try recompiling in the order you suggest.

Thank you.

Comment from Deny Dias
Posted: October 19, 2018 at 06:07

Eric, thank you so much for the icu4c-compat. It worked like a charm. SDDM and Plasma are back on duty.

Comment from Gérard Monpontet
Posted: October 19, 2018 at 08:44

pyqt5 need the module PyQt5.sip now (for hplip compiled with pyqt5 qt5 ), this module isn’t compiled by default, with your Slackbuild, i have modified your sip.Slackbuild like this:

if [ -n “${PYTHON3LIB}” ]; then
python3 configure.py –sip-module PyQt5.sip –no-tools \
-b “/usr/bin” \
-d “$PYTHON3LIB” \
CFLAGS=”$SLKCFLAGS” \
CXXFLAGS=”$SLKCFLAGS” || exit 1
make $NUMJOBS || make || exit 1
make install DESTDIR=$PKG || exit 1

fi

if [ -n “${PYTHON3LIB}” ]; then
python3 configure.py \
-b “/usr/bin” \
-d “$PYTHON3LIB” \
CFLAGS=”$SLKCFLAGS” \
CXXFLAGS=”$SLKCFLAGS” || exit 1
make $NUMJOBS || make || exit 1
make install DESTDIR=$PKG || exit 1

mv $PKG/usr/bin/sip $PKG/usr/bin/sip3
fi
these changes, are for added sip module ‘PyQt5.sip’,
and now hplip compiled with pyqt5, work.

Comment from LoneStar
Posted: October 19, 2018 at 09:36

Hello Eric,
the icu4c-compat package is a simple and smart idea!!
It’s something that maybe Patrick could consider for all the sensitive packages (boost, icu4c).
Even if -current always requires some self-awareness from the user.

Comment from Alex
Posted: October 19, 2018 at 23:06

Thanks, Eric, for the super-quick reaction. After installing your icu4c-compat package everything is smoother than ever. Great solution and “ludicrous” speed on your side! 🙂

Comment from alienbob
Posted: October 20, 2018 at 00:01

Well, the icu4c-compat was a stop-gap measure but a good one that I will keep.
I used the suggestions made by Ricardo and Gérard to improve on the sip and PyQt5 packages and I found out why qt5-webkit was missing stuff: the version 5.9.1 is no longer compatible with Qt 5.11.x. I had to upgrade it to the Webkit port which is being developed and maintained here: https://github.com/annulen/webkit … I succeeded in recompiling gpgme, qt5, qt5-webkit, sip, PyQt5 and currently fighting with QScintilla which now refuses to compile with all-new errors.

Comment from acidtripper
Posted: October 20, 2018 at 01:40

Great, glad to hear that qt is almost done, right now using current and latest kde. Great an quick solution with icu4c-compat. I see kde deployment on current on near future :D. at least nearer than some time ago. last version was mature, but this is better. thanks again for taking your time, your work is really appreciated by slack community.
Gonzalo.

Comment from rvdboom
Posted: October 20, 2018 at 13:03

Thanks for the icu4c-compat package, Eric. Much appreciated here.

Comment from Regnad Kcin
Posted: October 22, 2018 at 05:50

upgraded -current with icu4c-compat waiting to be installed. plasma did fail after upgrade, all working fine after installing icu4c-compat. plasma ok, libreoffice including impress ok, scim ok, inkscape ok, skype ok, OpenBoard ok, vlc ok . sensitive sometimes persnickety apps all running smoothly.

Comment from KG Hammarlund
Posted: October 22, 2018 at 09:18

A million thanks, Eric, for the ingenious solution building the icu4c-compat package.
Since I’ve chosen MATE as my DE, the dreaded .so bumps usually have limited consequences. This time just a few programs dependent on Qt5 and Qt5-webkit were affected: MuseScore, qBittorrent, vlc. But icu4c-compat solved it all.
Looking forward to the fresh Qt5 packages in the pipeline.

Comment from alienbob
Posted: October 22, 2018 at 13:58

Hi all.

Updates will eventually come, but I am currently ill and at home, so things are a bit slower.
For Plasma the fix takes the shape of recompiled qt5 and PyQt5, updated qt5-webkit, sip, QScintilla and gpgme with a new ‘hyphen’ package added.
These package updates will also fix qbittorrent and vlc.
The calibre and libreoffice packages need a full recompile.
For 64bit, I have done all of the above except for libreoffice. The 32bit effort needs to commence yet, but you still have icu4c-compat.

Comment from Deny Dias
Posted: October 22, 2018 at 17:34

Eric, take your time with those packages and a well deserved rest so you can get better asap! I care more about your health than anything else.

Comment from Antonio
Posted: October 22, 2018 at 21:10

Problem:

dolphin: error while loading shared libraries: liblmdb.so.0.0.0: cannot open shared object file: No such file or directory

Solved:

cd /usr/lib64
ln -s liblmdb.so liblmdb.so.0.0.0

Comment from alienbob
Posted: October 22, 2018 at 21:19

Antonio, no idea what happened on your computer but /usr/lib64/liblmdb.so.0.0.0 should be a regular file and it is part of the lmdb-0.9.22-x86_64-2.txz package.
And liblmdb.so should be a symlink.

Did you install lmdb from another location instead of using the Slackware package that was added to Slackware on Sep 14?

Comment from Antonio
Posted: October 23, 2018 at 01:23

Alien, all the wonder out there? Here in Brazil we are looking forward to the presidential elections! Hehehe.

My installation looks like this:

[ Status] [ Repository] [ Package]
installed myktown lmdb-0.9.21-x86_64-2alien
uninstalled(masked) slackware64 lmdb-0.9.22-x86_64-2

Should I install the “official package” parallel to yours?

I use a local ktown mirror, a local Slackware64 mirror and slackpkg+ to manage the packages.

Hugs

Comment from Ricardo J. Barberis
Posted: October 23, 2018 at 05:18

Antonio, I’d recommend to install Slackware’s version, that’s what I have on my system:

$ slackpkg search lmdb

Looking for lmdb in package list. Please wait… DONE

The list below shows all packages with name matching “lmdb”.

[ Status ] [ Repository ] [ Package ]
installed slackware64 lmdb-0.9.22-x86_64-2

Cheers!

Comment from Ricardo J. Barberis
Posted: October 23, 2018 at 05:20

Eric, I upgraded your Qt5 and related packages a few hours ago, so far so good!

Thank you!

Comment from Helios
Posted: October 23, 2018 at 08:47

Then you very much !

There are still icu4c problems in many deps/telepathy and kde/telepathy packages.

I found also “libclang.so.6 not found” in /usr/lib64/libKDevClangPrivate.so.30 (in kdevelop)

Comment from alienbob
Posted: October 23, 2018 at 08:50

Helios I do not use Telepathy myself, so I have not paid attention to it. I may fix those packages later, but 32bit fixes have to come first. Considering the issues I have at the moment, recompiling anything Qt5 related, it may take a week before I get the time for further fixes.

Comment from Helios
Posted: October 23, 2018 at 08:56

alienbob I don’t use Telepathy too, but I check everything in /usr/bin and /usr/lib64 to see which extra packages I need to recompile after updating icu4c. Fortunately there is ony one (tesseract)

Comment from alienbob
Posted: October 23, 2018 at 09:04

Antonio, I assume that “myktown” is a local repository with Plasma5 packages? It is not an up-to-date repository then, because lmdb was part of the older releases but not part of the current set any longer since lmdb got added to Slackware.

Comment from Pete Christy
Posted: October 23, 2018 at 11:09

Hi Eric,
Firstly, thanks for all your hard work, and hope you manage to shake the bug off soon!

I’ve just updated -current, LibreOffice and KDE5 with your latest offerings and run into a problem: kdenlive won’t run

~$ kdenlive
kdenlive: error while loading shared libraries: libhyphen.so.0: cannot open shared object file: No such file or directory

~$ locate libhyphen
/usr/lib64/libreoffice/program/libhyphenlo.so

Is this something I’ve done wrong, or is something missing from the updates? It was working fine before.

Cheers,


Pete

Comment from Pete Christy
Posted: October 23, 2018 at 12:24

Update: Have built Hyphen-2.8.8 from slackbuilds, and everything seems to be fine now. I suspect you’ve built on a machine with this installed – not sure if its essential or not, but if it is, perhaps this needs adding to dependencies?

Cheers,


Pete

Comment from Antonio
Posted: October 23, 2018 at 13:07

Fantastico Alien, everything beauty?
I fixed the script that creates my local mirrors and now everything is working fine.
Many thanks for your patience and great work!
PEACE!

Comment from alienbob
Posted: October 23, 2018 at 13:58

Pete, hyphen is a new dependency for the new qt5-webkit sources I am using.
A ‘hyphen’ package was already added both to ktown and my regular repository together with the upload of new qt5 and qt5-webkit packages. I assume you forgot to read the README and/or the ChangeLog.txt of my rpeository (always see if there’s new packages to install).

Comment from Pete Christy
Posted: October 23, 2018 at 15:01

Whoops! Mea culpa! Thanks, Eric!

I’m due an opticians appointment in a week’s time! 😉


Pete

Comment from chrisretusn
Posted: October 23, 2018 at 17:15

Just updated my local repository to the latest ktown and upgraded ktown on my systems. Finally able to upgrade Slackware. All is working well. Thanks a million.

Comment from aocab
Posted: October 23, 2018 at 21:55

Just updated and I noticed an issue opening my vault from the task bar. When I attempt to open it I do not get the prompt for the password. I do not get any visual feedback and the vault entry disappears from the list. I can however open the vault fine from the command line. Thanks

Comment from alienbob
Posted: October 23, 2018 at 22:16

aocab I can confirm that.
I thought I tested the vault after the updates… guess not.
What I also observe is that I see a message popup stating that my wireless connection is established (but it’s active all the time) and in the system tray I see three crash boxes appear and then disappear again before I get the chance to click on them.

Comment from acidtripper
Posted: October 24, 2018 at 04:17

I can see although an other problem with libre office 6.1.2 #2 packages. file menu dissapreaded, can somebody check if having same issue? thanks !

Comment from alienbob
Posted: October 24, 2018 at 12:38

acidtripper, works fine here on Plasma5 Desktop.
Check /etc/profile.d/libreoffice.sh and un-comment this line:

export SAL_USE_VCLPLUGIN=gtk3

And leave all other lines commented-out.
Login again or start a new login shell, and run Libre Office again. Are the menus back?

Comment from acidtripper
Posted: October 24, 2018 at 16:04

Im at work, let me check it when arrive home.
Other thing i saw yesterday is that when you open dolphin for example, file menu appears but on desktop background. what i did is to remove icu4c-compat reinstall -current one, and upgrade to latest kde 5.14.1 packages (the ones you uploaded with new qt neq qt-webkit, etc.

Comment from alienbob
Posted: October 24, 2018 at 16:22

acidtripper, Dolphin looks fine here. Perhaps you are experiencing a graphics bug in combination with Plasma 5.14?
What happens if you create a new user account and login with that account, then check?

By the way, icu4c-compat does not take the place of Slackware’s icu4c package, it is meant to be co-installed.

Comment from acidtripper
Posted: October 24, 2018 at 18:11

But as soon as i installed the new qt versions and kde stuff it shouldn’t be necessary anymore to conserve icu4c-compat i’m right?. On the other hand maybe i faced some misconfiguration related to my user. i’ll check it in some hours and let you know about this two things: libreoffice and dolphin file’s menu.
Thanks!

Comment from alienbob
Posted: October 24, 2018 at 21:02

acidtripper perhaps I just misunderstood your statement “remove icu4c-compat reinstall -current one”.

Comment from acidtripper
Posted: October 24, 2018 at 23:19

i remove icu4c-compat and installed again slackware’s icu4c from current, after upgrading to latest kde with new qt stuff.

Comment from acidtripper
Posted: October 24, 2018 at 23:54

Well here im testing. adding a new user solved libreoffice file menu issue. about dolphin file menu isn-t present but menu isnt in the wallpaper. although i upgraded qscintilla and sip, dated from today *24th.

Comment from alienbob
Posted: October 25, 2018 at 10:58

acidtripper then perhaps it is time that you to open a bug report on bugs.kde.org with as much detail as you can give, including screenshots.
I do not experience the issues you are describing.

Comment from alienbob
Posted: October 25, 2018 at 12:50

FYI,

According to a quick scan of packages using ‘ldd’, the following packages still have icu4c linking issues and probably have to be recompiled.
From the deps/telepathy section, in this order:
libaccounts-glib
libaccounts-qt5
signon-ui
telepathy-gabble
telepathy-logger
telepathy-logger-qt5
telepathy-mission-control
telepathy-accounts-signon

And in kde/telepathy (in this order):
kaccounts-integration
kaccounts-providers
ktp-common-internals
ktp-accounts-kcm
ktp-contact-list
ktp-contact-runner
ktp-text-ui
ktp-kded-module
ktp-auth-handler
ktp-filetransfer-handler
ktp-send-file
ktp-call-ui

I’ll see what I can do. A new KDE Applications release is still two weeks away.
Perhaps with the compilation of the dependencies, most of the damage is repaired already. And if you have icu4c-compat installed, you won’t have an issue anyway…

Comment from acidtripper
Posted: October 25, 2018 at 16:28

Well, everything working as a charm here, although telepathy issues, personally i dont use it . So i don’t get hurt this time. Is there any idea of merging kde5 on current eric? or it’s far away?
Thanks for your dedicated work and answers. Im using it an testing in my main devices.

Comment from Regnad Kcin
Posted: October 28, 2018 at 01:56

Plasma 5 working great with all apps and fast and smooth. Wacom tablets support good now, with calibration flawlessly operating. No longer any need to tweak with xsetwacom to get it right. Overall this is a system that anyone can use. Great work.

Comment from Michael Langdon
Posted: October 30, 2018 at 14:28

Eric,
Today I did Alt+F2 for krunner and nothing happened after three tries. I tried in Konsole, and krunner was looking for gnome icons or crystalsvg icons. I installed crystalsvg icons and had KDE use that. Alt+F2 immediately pulled up krunner. I like the crystalsvg icons, but hadn’t had this problem in the past. I only use krunner with kdesu anyway. Sometimes I’m a bit lazy.

Comment from alienbob
Posted: October 30, 2018 at 17:21

Michael, that means you changed something on your computer. Krunner should not require Gnome icons or crystalsvg.

Comment from Michael Langdon
Posted: October 31, 2018 at 12:37

It was not what I changed, but what I didn’t change. I was suffering some goofiness from the background flashing black to white with more than one app open. It did not matter the apps. Then I remembered that when I removed KDE and replaced all with your KDE5, I never removed the nvidia driver. It did not cross my mind. I just now removed the driver, and it complained about the driver installation had been changed, so I new that having removed KDE, something went awry. Re-installing nvidia solved all probems with the flashing screen and krunner. I took out crystalsvg and krunner was just fine. I then put crystalsvg back, because I did like it.

Write a comment