My thoughts on Slackware, life and everything

KDE 5_15.05 packages are available for slackware-current

qt-kde-620x350I am trying to keep up with a monthly release of KDE 5 (Plasma5) packages for Slackware-current. So far, so good, and every month I have been able to make a significant difference. Today the KDE developers released an update to Plasma 5 while earlier this month you could have noticed updates for Frameworks and Applications. Time for some new packages for Slackware land!

Therefore, you can now download my May release of KDE 5_15.05. Components are Frameworks 5.10.0, Plasma 5.3.1 and Applications 15.04.1 which includes the latest updates of the KDE 4 Long Term Support (LTS) packages kdelibs, kdepimlibs, kdepim, kdepim-runtime and kde-workplace.

What’s new in KDE 5_15.05?

The highlights of 5_15.05 (May release) are:

  • KDE Frameworks have been updated to 5.10.0 (maintenance release, no new frameworks)
  • KDE Plasma has been updated to 5.3.1 (also a maintenance release)
  • KDE Applications have been updated to 15.04.1 (yet another maintenance release)
  • KDE Extragear is still empty (this started with my KDE 5_15.04 release): you must grab the extragear packages (calligra, k3b, kdev-python, kdevelop, kdevelop-php, kdevelop-php-docs, kdevplatform, kio-mtp, kwebkitpart, oxygen-gtk2, oxygen-gtk3, partitionmanager, skanlite) from regular slackware-current itself.
  • No new or udated “deps” packages this time, but one has been removed. I got rid of the “qt-gstreamer0” package because I believe there is nothing that uses it. Also, the package content was conflicting with the “qt-gstreamer” package. So after you have removed qt-gstreamer0 be sure to reinstall qt-gstreamer.
  • I have added several policy files to the “powerdevil” package which bring back the Shutdown/Reboot and Suspend/Hibernate options in Plasma 5. Thanks to luis (suspend/hibernate) and manciuleas (restart/shutdown) who came up with the solution in a discussion following an older post.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

As always, the accompanying README file contains full installation & upgrade instructions. Note that the packages are available in several subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “kde4”, “kde4-extragear” (currently empty), “frameworks” “plasma”, “plasma-extra” and “applications”.

Upgrading to this KDE 5 is not difficult this time, especially if you already are running KDE 5_15.04. You will have to remove old KDE packages manually. If you do not have KDE installed at all, you will have to install some of Slackware’s own KDE 4 packages manually.

Note:

If you are using slackpkg+, have already moved to KDE 5_15.01 or newer and are adventurous, you can try upgrading using the following set of commands. This should work but feel free to send me improved instructions if needed (assuming in this example that you tagged my KDE 5 repository “ktown_testing”):
# slackpkg update
# slackpkg install ktown_testing (to get the newly added packages from my repo)
# slackpkg install-new (to get the new official Slackware packages that were part of my deps previously)
# slackpkg upgrade ktown_testing (upgrade all existing packages to their latest versions)
# slackpkg upgrade-all (upgrade the remaining dependencies that were part of my repo previously)
# removepkg sddm-theme-breeze (gone after KDE 5_15.01)
# removepkg libmm-qt5 (gone after KDE 5_15.03)
# removepkg qt-gstreamer0 (gone after KDE 5_15.04)
# slackpkg reinstall qt-gstreamer (ensure that none of the overlapping files of qt-gstreamer0 are left)

And doublecheck that you have not inadvertently blacklisted my packages in “/etc/slackpkg/blacklist“! Check for the existence of a line in that blacklist file that looks like “[0-9]+alien” and remove it if you find it!

My observations after upgrading

Again, some peculiarities I ran across when starting the freshly upgraded desktop that I want to share with you (there are some more observations in my previous KDE post):

  • At first the desktop would not even start and all kinds of Frameworks related programs were crashing. Re-installing all packages solved that. Something got corrupted the first time? No way to find out.
  •  I switched from wmsystemtray to trayer-srg as the solution for supporting old-style Xembed tray icons like Dropbox with the commandline “trayer –edge bottom –widthtype request –align right –distance 30 &” which places it lower right, directly above the Plasma taskbar. However – and I don’t recall what I did – on all subsequent logins, trayer would start before the rest of the desktop. As a result of that, trayer would cover the full task bar area. The task bar, including the KDE menu, were made inaccessible and invisible. At first I thought “yet another crash of plasmashell” and restarting plasmashell would indeed fix the issue. It was only later that I found out that they were all running, but trayer was in the way of the task bar. So I created a “trayer.desktop” file in ~/.config/autostart where Plasma5 looks for applications it has to start automatically when you login – and it will start these applications after the full desktop environment has loaded. That fixed it. By the way, the file has to end with “.desktop” or else it will be ignored. Inside it should look something like this:
[Desktop Entry]
Type=Application
Exec=trayer --edge bottom --widthtype request --align right --distance 30
Terminal=false
Hidden=false
NoDisplay=false
Name=Trayer

Where to get the new packages for Plasma 5

Download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ subdirectories). If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

29 Comments

  1. Michelino

    Many thanks, as usual!

  2. Eduardo

    Thank you Eric!

    However, I cannot use the software. I experienced the behavior you described on the first start, but with the difference that the crashes wouldn’t go away, even after reinstalling everything.

    The culprit seems to be, once more, Kactivities. Here is the backtrace for krunner, but it is similar in every crash. I’ll appreciate any help in solving it.

    Thanks!

    *** BACKTRACE ***

    Application: krunner (krunner), signal: Segmentation fault
    Using host libthread_db library “/lib64/libthread_db.so.1”.
    [Current thread is 1 (Thread 0x7ff16b9247c0 (LWP 1752))]

    Thread 8 (Thread 0x7ff156338700 (LWP 1764)):
    #0 0x00007ff165aba2fd in poll () at /lib64/libc.so.6
    #1 0x00007ff164944002 in () at /usr/lib64/libxcb.so.1
    #2 0x00007ff164945a9f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
    #3 0x00007ff1593a32d9 in () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
    #4 0x00007ff16664f61f in () at /usr/lib64/libQt5Core.so.5
    #5 0x00007ff1640c0754 in () at /usr/lib64/libGL.so.1
    #6 0x00007ff1623c6654 in start_thread () at /lib64/libpthread.so.0
    #7 0x00007ff165ac57dd in clone () at /lib64/libc.so.6

    Thread 7 (Thread 0x7ff14ac69700 (LWP 1771)):
    #0 0x00007ff165aba2fd in poll () at /lib64/libc.so.6
    #1 0x00007ff1614561a4 in () at /usr/lib64/libglib-2.0.so.0
    #2 0x00007ff1614562ac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
    #3 0x00007ff16687fd77 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5
    #4 0x00007ff166829182 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5
    #5 0x00007ff16664a84c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
    #6 0x00007ff16a0e01c5 in () at /usr/lib64/libQt5Qml.so.5
    #7 0x00007ff16664f61f in () at /usr/lib64/libQt5Core.so.5
    #8 0x00007ff1640c0754 in () at /usr/lib64/libGL.so.1
    #9 0x00007ff1623c6654 in start_thread () at /lib64/libpthread.so.0
    #10 0x00007ff165ac57dd in clone () at /lib64/libc.so.6

    Thread 6 (Thread 0x7ff1425c2700 (LWP 1862)):
    #0 0x00007ff1623cbd8f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
    #1 0x00007ff16665063b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5
    #2 0x00007ff16a7c32e2 in () at /usr/lib64/libQt5Quick.so.5
    #3 0x00007ff16a7c3700 in () at /usr/lib64/libQt5Quick.so.5
    #4 0x00007ff16664f61f in () at /usr/lib64/libQt5Core.so.5
    #5 0x00007ff1640c0754 in () at /usr/lib64/libGL.so.1
    #6 0x00007ff1623c6654 in start_thread () at /lib64/libpthread.so.0
    #7 0x00007ff165ac57dd in clone () at /lib64/libc.so.6

    Thread 5 (Thread 0x7ff137c04700 (LWP 1882)):
    #0 0x00007ff1623cbd8f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
    #1 0x00007ff16665063b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5
    #2 0x00007ff143dec177 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
    #3 0x00007ff143defed8 in () at /usr/lib64/libKF5ThreadWeaver.so.5
    #4 0x00007ff143deb31f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
    #5 0x00007ff143dedf83 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5
    #6 0x00007ff16664f61f in () at /usr/lib64/libQt5Core.so.5
    #7 0x00007ff1640c0754 in () at /usr/lib64/libGL.so.1
    #8 0x00007ff1623c6654 in start_thread () at /lib64/libpthread.so.0
    #9 0x00007ff165ac57dd in clone () at /lib64/libc.so.6

    Thread 4 (Thread 0x7ff137403700 (LWP 1883)):
    #0 0x00007ff1623cbd8f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
    #1 0x00007ff16665063b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5
    #2 0x00007ff143dec177 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
    #3 0x00007ff143defed8 in () at /usr/lib64/libKF5ThreadWeaver.so.5
    #4 0x00007ff143deb31f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
    #5 0x00007ff143dedf83 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5
    #6 0x00007ff16664f61f in () at /usr/lib64/libQt5Core.so.5
    #7 0x00007ff1640c0754 in () at /usr/lib64/libGL.so.1
    #8 0x00007ff1623c6654 in start_thread () at /lib64/libpthread.so.0
    #9 0x00007ff165ac57dd in clone () at /lib64/libc.so.6

    Thread 3 (Thread 0x7ff136c02700 (LWP 1884)):
    #0 0x00007ff1623cbd8f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
    #1 0x00007ff16665063b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5
    #2 0x00007ff143dec177 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
    #3 0x00007ff143defed8 in () at /usr/lib64/libKF5ThreadWeaver.so.5
    #4 0x00007ff143deb31f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
    #5 0x00007ff143deff22 in () at /usr/lib64/libKF5ThreadWeaver.so.5
    #6 0x00007ff143deb31f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
    #7 0x00007ff143dedf83 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5
    #8 0x00007ff16664f61f in () at /usr/lib64/libQt5Core.so.5
    #9 0x00007ff1640c0754 in () at /usr/lib64/libGL.so.1
    #10 0x00007ff1623c6654 in start_thread () at /lib64/libpthread.so.0
    #11 0x00007ff165ac57dd in clone () at /lib64/libc.so.6

    Thread 2 (Thread 0x7ff136401700 (LWP 1885)):
    #0 0x00007ff1623cbd8f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
    #1 0x00007ff16665063b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5
    #2 0x00007ff143dec177 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
    #3 0x00007ff143defed8 in () at /usr/lib64/libKF5ThreadWeaver.so.5
    #4 0x00007ff143deb31f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
    #5 0x00007ff143deff22 in () at /usr/lib64/libKF5ThreadWeaver.so.5
    #6 0x00007ff143deb31f in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5
    #7 0x00007ff143dedf83 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5
    #8 0x00007ff16664f61f in () at /usr/lib64/libQt5Core.so.5
    #9 0x00007ff1640c0754 in () at /usr/lib64/libGL.so.1
    #10 0x00007ff1623c6654 in start_thread () at /lib64/libpthread.so.0
    #11 0x00007ff165ac57dd in clone () at /lib64/libc.so.6

    Thread 1 (Thread 0x7ff16b9247c0 (LWP 1752)):
    [KCrash Handler]
    #5 0x00007ff13b3bded7 in () at /usr/lib64/libKF5Activities.so.5
    #6 0x00007ff16685a892 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
    #7 0x00007ff166646f02 in QFutureWatcherBase::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
    #8 0x00007ff1677b2cdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
    #9 0x00007ff1677b7e10 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
    #10 0x00007ff16682b583 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
    #11 0x00007ff16682d50b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
    #12 0x00007ff16687f983 in () at /usr/lib64/libQt5Core.so.5
    #13 0x00007ff161455fc4 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
    #14 0x00007ff161456208 in () at /usr/lib64/libglib-2.0.so.0
    #15 0x00007ff1614562ac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
    #16 0x00007ff16687fd77 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5
    #17 0x00007ff166829182 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5
    #18 0x00007ff1668307ad in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
    #19 0x00000000004079cf in main ()

  3. alienbob

    Eduardo, try re-installing kactivities-framework. The kactivities and kactivities-framework packages are coïnstallable but the kactivities-framework package needs to be installed last so that its KF5 version of kactivitymanagerd overwrites the KDE4 variant of the kactivities package.
    I need to find a good solution for resolving this conflict.

  4. Eduardo

    Eric: it worked! Now I’m using Plasma as usual. Thank you!

  5. Mike

    Why not just add a line to the README.
    Thanks for excellent job.

  6. Alan Aversa

    After doing this upgrade, why does Okular, for example, say it’s KDE 4.14.8, yet okular-15.04.1-x86_64-1alien is in /var/log/packages/ ?

  7. Alan Aversa

    (I went the slackpkg+ route.)

  8. alienbob

    Hi Alan

    Okular is part of Applications 15.04.1 but it’s still a KDE4 based application, it has not yet been ported to KF5. And all KDE4 applications will report the version of kdelibs as the KDE version – currently that is indeed 4.14.8.

  9. alienbob

    Mike, yes that is an option indeed.

  10. Alan Aversa

    alienbob, thanks. The update worked flawlessly, then.

  11. gmgf

    Thanks, Eric, these news packages, work fine here.

  12. Willy Arana

    HI, i re-install but still this error when run plasmashell

    plasmashell
    QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-willy’
    kf5.kservice.sycoca: Trying to open ksycoca from “/home/willy/.cache/ksycoca5”
    populateAddPanelsMenu 1
    kf5.kiconthemes: “Theme tree: (Brisa)”
    Application::crashHandler() called with signal 11; recent crashes: 1
    /usr/bin/plasmashell –crashes 1 &
    KCrash: crashing… crashRecursionCounter = 2
    KCrash: Application Name = plasmashell path = /usr/bin pid = 23856
    KCrash: Arguments: /usr/bin/plasmashell
    KCrash: Attempting to start /usr/lib64/drkonqi from kdeinit
    sock_file=/tmp/runtime-willy/kdeinit5__0
    QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-willy’
    kf5.kservice.sycoca: Trying to open ksycoca from “/home/willy/.cache/ksycoca5”
    populateAddPanelsMenu 1
    kf5.kiconthemes: “Theme tree: (Brisa)”
    Application::crashHandler() called with signal 11; recent crashes: 2
    /usr/bin/plasmashell –crashes 2 &
    KCrash: crashing… crashRecursionCounter = 2
    KCrash: Application Name = plasmashell path = /usr/bin pid = 23866
    KCrash: Arguments: /usr/bin/plasmashell –crashes 1
    KCrash: Attempting to start /usr/lib64/drkonqi from kdeinit
    sock_file=/tmp/runtime-willy/kdeinit5__0
    QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-willy’
    kf5.kservice.sycoca: Trying to open ksycoca from “/home/willy/.cache/ksycoca5”
    populateAddPanelsMenu 1
    kf5.kiconthemes: “Theme tree: (Brisa)”
    Application::crashHandler() called with signal 11; recent crashes: 3
    /usr/bin/plasmashell –crashes 3 &
    Too many crashes in short order or respawning disabled, not restarting automatically.
    KCrash: crashing… crashRecursionCounter = 2
    KCrash: Application Name = plasmashell path = /usr/bin pid = 23877
    KCrash: Arguments: /usr/bin/plasmashell –crashes 2
    KCrash: Attempting to start /usr/lib64/drkonqi from kdeinit
    sock_file=/tmp/runtime-willy/kdeinit5__0

    [1]+ Detenido plasmashel

  13. MiRacLe

    Willy, try \”hard\” reboot or \”soft\” – telinit 3 && telinit 4

  14. Willy Arana

    @MiRacLe i try that, i think maybe i have a corrupt install when i download the packages, but i don’t know XD

  15. Alex

    Hi Eric,

    thanks for the upgrade!
    However, the README mentions some packages in deps, that are not there, such as akonadi-qt5. If the documentation is correct, then this package (plus a few others) are missing in deps. In that case: Where can I find them?

    Thanks!

    Alex

  16. alienbob

    Alex I will check that README. There are no missing “deps” packages so the README must be updated.

  17. Willy Arana

    Hi erick (again) i have a error similar to @Eduardo, i try our solution (reinstall kactivies-framework) but doesn’t work, my backtrace is:

    Application: Plasma (plasmashell), signal: Segmentation fault
    Using host libthread_db library “/lib64/libthread_db.so.1”.
    [Current thread is 1 (Thread 0x7fb4984387c0 (LWP 876))]

    Thread 7 (Thread 0x7fb484adf700 (LWP 878)):
    #0 0x00007fb4905342fd in poll () at /lib64/libc.so.6
    #1 0x00007fb496828002 in () at /usr/lib64/libxcb.so.1
    #2 0x00007fb496829a9f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
    #3 0x00007fb48793d2d9 in () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
    #4 0x00007fb4910c961f in () at /usr/lib64/libQt5Core.so.5
    #5 0x00007fb48f0ab654 in start_thread () at /lib64/libpthread.so.0
    #6 0x00007fb49053f7dd in clone () at /lib64/libc.so.6

    Thread 6 (Thread 0x7fb47b5f7700 (LWP 885)):
    #0 0x00007fb4905342fd in poll () at /lib64/libc.so.6
    #1 0x00007fb48b8251a4 in () at /usr/lib64/libglib-2.0.so.0
    #2 0x00007fb48b8254ca in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
    #3 0x00007fb47e8eec66 in () at /usr/lib64/libgio-2.0.so.0
    #4 0x00007fb48b849f75 in () at /usr/lib64/libglib-2.0.so.0
    #5 0x00007fb48f0ab654 in start_thread () at /lib64/libpthread.so.0
    #6 0x00007fb49053f7dd in clone () at /lib64/libc.so.6

    Thread 5 (Thread 0x7fb47adf6700 (LWP 888)):
    #0 0x00007fb4905342fd in poll () at /lib64/libc.so.6
    #1 0x00007fb48b8251a4 in () at /usr/lib64/libglib-2.0.so.0
    #2 0x00007fb48b8252ac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
    #3 0x00007fb48b8252e9 in () at /usr/lib64/libglib-2.0.so.0
    #4 0x00007fb48b849f75 in () at /usr/lib64/libglib-2.0.so.0
    #5 0x00007fb48f0ab654 in start_thread () at /lib64/libpthread.so.0
    #6 0x00007fb49053f7dd in clone () at /lib64/libc.so.6

    Thread 4 (Thread 0x7fb479ce4700 (LWP 891)):
    #0 0x00007fb4905342fd in poll () at /lib64/libc.so.6
    #1 0x00007fb48b8251a4 in () at /usr/lib64/libglib-2.0.so.0
    #2 0x00007fb48b8252ac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
    #3 0x00007fb4912f9d77 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5
    #4 0x00007fb4912a3182 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5
    #5 0x00007fb4910c484c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
    #6 0x00007fb4952f31c5 in () at /usr/lib64/libQt5Qml.so.5
    #7 0x00007fb4910c961f in () at /usr/lib64/libQt5Core.so.5
    #8 0x00007fb48f0ab654 in start_thread () at /lib64/libpthread.so.0
    #9 0x00007fb49053f7dd in clone () at /lib64/libc.so.6

    Thread 3 (Thread 0x7fb462ac1700 (LWP 892)):
    #0 0x00007fb4905342fd in poll () at /lib64/libc.so.6
    #1 0x00007fb48b8251a4 in () at /usr/lib64/libglib-2.0.so.0
    #2 0x00007fb48b8252ac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
    #3 0x00007fb4912f9d77 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5
    #4 0x00007fb4912a3182 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5
    #5 0x00007fb4910c484c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
    #6 0x00007fb4952f31c5 in () at /usr/lib64/libQt5Qml.so.5
    #7 0x00007fb4910c961f in () at /usr/lib64/libQt5Core.so.5
    #8 0x00007fb48f0ab654 in start_thread () at /lib64/libpthread.so.0
    #9 0x00007fb49053f7dd in clone () at /lib64/libc.so.6

    Thread 2 (Thread 0x7fb4614a9700 (LWP 893)):
    #0 0x00007fb490536033 in select () at /lib64/libc.so.6
    #1 0x00007fb49123c441 in () at /usr/lib64/libQt5Core.so.5
    #2 0x00007fb4910c961f in () at /usr/lib64/libQt5Core.so.5
    #3 0x00007fb48f0ab654 in start_thread () at /lib64/libpthread.so.0
    #4 0x00007fb49053f7dd in clone () at /lib64/libc.so.6

    Thread 1 (Thread 0x7fb4984387c0 (LWP 876)):
    [KCrash Handler]
    #5 0x00007fb4975f5ed7 in () at /usr/lib64/libKF5Activities.so.5
    #6 0x00007fb4912d4892 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
    #7 0x00007fb4910c0f02 in QFutureWatcherBase::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
    #8 0x00007fb492873cdc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
    #9 0x00007fb492878e10 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
    #10 0x00007fb4912a5583 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
    #11 0x00007fb4912a750b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
    #12 0x00007fb4912f9983 in () at /usr/lib64/libQt5Core.so.5
    #13 0x00007fb48b824fc4 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
    #14 0x00007fb48b825208 in () at /usr/lib64/libglib-2.0.so.0
    #15 0x00007fb48b8252ac in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
    #16 0x00007fb4912f9d77 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5
    #17 0x00007fb4912a3182 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5
    #18 0x00007fb4912aa7ad in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
    #19 0x0000000000430d80 in main ()

  18. alienbob

    Willy Arana, it is not kactivities which is crashing. The crash is in plasmashell (part of the plasma-workspace package).
    I have no solution for you except try re-installing plasma-workspace.

  19. Willy Arana

    I try re-install plasma-workspace, but still with the error, that’s so weird but thank’s for all you work

  20. Willy Arana

    well i take this image https://s-media-cache-ak0.pinimg.com/236x/36/6f/17/366f175d20b9fae77f0a1b6e87b9ca67.jpg and that’s happen to me, i don’t know why but work now, thanks Erick , you are awesome!

  21. rvdboom

    I can confirm that the crash at start is caused by kactivities being installled after kactivities-framework.
    But since kactivities is in the kde4 subdir while kactivities-framework is in the frameworks subdir, you’ll get this every time when you upgrade using “upgradepkg */*.txz” : kde4 comes after frameworks.
    Would probably be better in the README to advise running upgradepkg in each subdir, in the proper order (i.e. kde4 before frameworks). Or number the subdirs in the proper order.

  22. alienbob

    Hi rvdboom

    I plan on releasing an update soon and that includes a modified kactivities packages with the kactivitymanagerd removed. That version of the daemon is not compatible with the kactivities-framework libraries, but the other way works: the kactivitymanagerd from the kactivities-framework will work just fine with the KDE4 based kactivities.

  23. rvdboom

    Perfect solution indeed!
    Been fiddling a bit with KDE5, it’s usable but now you cannot bind an activity to a virtual desktop anymore. I’m OK with using activities but moving around activities and windows between them is more awkward than before, when you could just use desktop in grids to move a window from a desktop to another. Hopefully someone will step up and develop something similar to move around activities. Otherwise, plasma takes a lot of CPU, will wait until putting it on my laptop…
    Firefox doesn’t seem to pick up GTK-QT, it looks like old motif. 🙂
    But as far as your package go, everything works fine. Very good job! Thanks a lot!

  24. rvdboom

    For the record, the high CPU usage I had with plasmashell is caused by monitoring widgets with graphs, as described in this bug report : https://bugs.kde.org/show_bug.cgi?id=345696. Removing the widgets made plasmashell CPU come back to a few percents.

  25. Michelino

    Hallo Eric,
    I think it could be a good idea to add in the README the advice that in order to have a working “Shutdown/Reboot” and “Suspend/Hibernate” in Plasma 5 you have to add your user to the “power” group.
    Just my 2 cents

  26. alienbob

    Hi Michelino.

    That is not specific to my KDE packages, it is a generic Slackware requirement. It has no place in the README.

  27. Michelino

    You are surely right, but I used to be able to shutdown/reboot using your “Plasma 5 preview” not being part of “power” group (I have just added mi account to that group upgrading to your KDE 5_15.05).

  28. alienbob

    Hi Michelino – that was a permissions error then. If you are not in the “power” group then your account should not be able to shutdown or reboot the computer.

    Of course, if you were using my KDE 5 preview in Runlevel 3 (console boot) then your account would have been added to the “power” group dynamically for the duration of your login session. See /etc/login.defs – if you are logging on at the console then you are entitled to manage the hardware to the fullest extent.

    The “power” group membership limitation is most important to avoid that someone logs into your computer remotely, starts an X session and then clicks “shutdown”.

  29. Michelino

    Eric, you hit the mark!
    🙂
    Thanks for explanation

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

© 2024 Alien Pastures

Theme by Anders NorenUp ↑