KDE Plasma 5 Hits Testing!

RadicalDreamer · 11-17-2020, 10:53 PM

"gwenview: error while loading shared libraries: libraw.so.20: cannot open shared object file: No such file or directory"

Code:

bash-5.0# ldd gwenview | grep libraw
        libraw.so.20 => not found

Code:

bash-5.0# locate libraw
/usr/lib/libraw.so.16
/usr/lib/libraw.so.16.0.0
/usr/lib/libraw_r.so.16
/usr/lib/libraw_r.so.16.0.0
/usr/lib64/libraw.so.16
/usr/lib64/libraw.so.16.0.0
/usr/lib64/libraw1394.so
/usr/lib64/libraw1394.so.11
/usr/lib64/libraw1394.so.11.1.0
/usr/lib64/libraw_r.so.16
/usr/lib64/libraw_r.so.16.0.0

Where is libraw.so.20?

drgibbon · 11-17-2020, 10:57 PM

Quote:

Originally Posted by RadicalDreamer

Where is libraw.so.20?

Code:

slackpkg file-search libraw.so.20

btw, an updated version of LibRaw was a dependency in ktown, so after removing it and installing vtown, `slackpkg install-new` would not pick up LibRaw again from the main Slackware tree (I guess that's why it's missing on your system). To get slackpkg to pick up that kind of missing stuff you can do `slackpkg install slackware64` (obviously with kde etc blacklisted). Actually I still think an 'install-missing' option wouldn't be too bad of an idea for slackpkg, as intuitively I thought that install-new worked like that (as in, "new to this system", rather being strictly based on changelog newness).

RadicalDreamer · 11-18-2020, 12:33 AM

Quote:

Originally Posted by drgibbon

Code:

slackpkg file-search libraw.so.20

btw, an updated version of LibRaw was a dependency in ktown, so after removing it and installing vtown, `slackpkg install-new` would not pick up LibRaw again from the main Slackware tree (I guess that's why it's missing on your system). To get slackpkg to pick up that kind of missing stuff you can do `slackpkg install slackware64` (obviously with kde etc blacklisted). Actually I still think an 'install-missing' option wouldn't be too bad of an idea for slackpkg, as intuitively I thought that install-new worked like that (as in, "new to this system", rather being strictly based on changelog newness).

Thanks, I would have never figured that out! I see what happened, slackpkg is case-sensitive.

Code:

bash-5.0# slackpkg search LibRaw

Looking for LibRaw in package list. Please wait... DONE

The list below shows all packages with name matching "LibRaw".

[ Status           ] [ Repository               ] [ Package                                  ]
  uninstalled              slackware64                  LibRaw-0.20.2-x86_64-1

Code:

bash-5.0# slackpkg search libraw

Looking for libraw in package list. Please wait... DONE

The list below shows all packages with name matching "libraw".

[ Status           ] [ Repository               ] [ Package                                  ]
   installed               slackware64                  libraw1394-2.1.2-x86_64-2

Alien Bob · 11-18-2020, 01:01 AM

Quote:

Originally Posted by drgibbon

Code:

slackpkg file-search libraw.so.20

btw, an updated version of LibRaw was a dependency in ktown, so after removing it and installing vtown, `slackpkg install-new` would not pick up LibRaw again from the main Slackware tree (I guess that's why it's missing on your system). To get slackpkg to pick up that kind of missing stuff you can do `slackpkg install slackware64` (obviously with kde etc blacklisted). Actually I still think an 'install-missing' option wouldn't be too bad of an idea for slackpkg, as intuitively I thought that install-new worked like that (as in, "new to this system", rather being strictly based on changelog newness).

That's why there is a bit fat red-colored line of text in my blog about "ktown becomes vtown":

Code:

...
slackpkg install LibRaw autoconf-archive exiv2 poppler

The last line will re-install the few packages that were in my ‘ktown’ but also part of Slackware core.
They were upgraded by Pat in Slackware core instead of in ‘vtown’ and thus the “slackpkg remove ktown” removed those permanently.

drgibbon · 11-18-2020, 09:56 AM

Quote:

Originally Posted by RadicalDreamer

Thanks, I would have never figured that out! I see what happened, slackpkg is case-sensitive.

Hmm yeah, easy to miss that then. Personally I'd prefer smart-case by default (like silver-searcher/ag), where case sensitivity is only enabled if there are upper case letters in the search.

Quote:

Originally Posted by Alien Bob

That's why there is a bit fat red-colored line of text in my blog about "ktown becomes vtown":

Code:

...
slackpkg install LibRaw autoconf-archive exiv2 poppler

The last line will re-install the few packages that were in my ‘ktown’ but also part of Slackware core.
They were upgraded by Pat in Slackware core instead of in ‘vtown’ and thus the “slackpkg remove ktown” removed those permanently.

lovemeslk · 11-20-2020, 05:48 PM

Quote:

Originally Posted by drgibbon

Code:

slackpkg file-search libraw.so.20

btw, an updated version of LibRaw was a dependency in ktown, so after removing it and installing vtown, `slackpkg install-new` would not pick up LibRaw again from the main Slackware tree (I guess that's why it's missing on your system). To get slackpkg to pick up that kind of missing stuff you can do `slackpkg install slackware64` (obviously with kde etc blacklisted). Actually I still think an 'install-missing' option wouldn't be too bad of an idea for slackpkg, as intuitively I thought that install-new worked like that (as in, "new to this system", rather being strictly based on changelog newness).

One system did not have an issue one system one system did but unable to reproduce. Happen when gimp was updated.

garpu · 11-21-2020, 08:34 PM

OK, just noticed it again. kwin_x11 was taking 100% of my cpu. Killing X and dropping to console (I'm always in runlevel 3) didn't kill the process. (I had to kill -9 it.) I've no clue what actually causes it, though, or how to reproduce.

3rensho · 11-22-2020, 12:51 AM

Quote:

Originally Posted by garpu

OK, just noticed it again. kwin_x11 was taking 100% of my cpu. Killing X and dropping to console (I'm always in runlevel 3) didn't kill the process. (I had to kill -9 it.) I've no clue what actually causes it, though, or how to reproduce.

I've noticed this myself sometimes. 100% of one core was being used by kwin_x11. Logging out of plasma and a startx cured it for the rest of the day. Does not happen to me regularly so have no idea what can trigger it.

montagdude · 11-22-2020, 06:44 AM

I just upgraded from ktown to vtown yesterday. No issues whatsoever so far. It's nice to be able to remove a repo from my slackpkgplus config.

_peter · 11-22-2020, 08:13 AM

for a week, restarting with up to date slackware64 current no multi-lib and new user $HOME/, so far i no longer see the kwin_x11 using 100% of cpu when running kde plasma.

Pixxt · 11-22-2020, 08:39 AM

Quote:

Originally Posted by 3rensho

I've noticed this myself sometimes. 100% of one core was being used by kwin_x11. Logging out of plasma and a startx cured it for the rest of the day. Does not happen to me regularly so have no idea what can trigger it.

Just kill -9 the 100% hogging kwin_x11 process while inside of Plasma itself, nothing visible crashes if you do so. I.e no windows will disappear and reappear or window borders disappear, no apps seem to crash. And you can continue on with out logging out and logging back in and all that time wasting jazz.

3rensho · 11-22-2020, 08:51 AM

Quote:

Originally Posted by Pixxt

Just kill -9 the 100% hogging kwin_x11 process while inside of Plasma itself, nothing visible crashes if you do so. I.e no windows will disappear and reappear or window borders disappear, no apps seem to crash. And you can continue on with out logging out and logging back in and all that time wasting jazz.

Thanks for that. Had considered doing that but then thought it might kill everything and I'd have to restart anyway.

JimBrewster · 11-23-2020, 03:36 PM

Maybe a dumb question, but is there a good reason not to just run

Code:

slackpkg upgrade vtown

if I'm starting from an upgraded -current system with no ktown? When I run that command I get a full list of packages to upgrade, and I assume they will replace whatever is in the current kde installation? TIA...

Quote:

Originally Posted by RadicalDreamer

This is what I did. I first ran

Code:

slackpkg install-new

. Then

Code:

slackpkg upgrade-all

. Then

Code:

slackpkg clean-system

. I did a kernel upgrade. Rebooted. Then I ran (at runlevel 3)

Code:

slackpkg remove ktown

. Then I ran

Code:

slackpkg remove kde

. Then

Code:

slackpkg remove kdei

. Then I did

Code:

slackpg install vtown

. I noticed it missed a few packages so I did

Code:

slackpkg upgrade vtown

and that got everything related to vtown.

RadicalDreamer · 11-23-2020, 06:57 PM

JimBrewster, run

Code:

slackpkg search testing

and see if you've got all of vtown.

bassmadrigal · 11-23-2020, 07:46 PM

Quote:

Originally Posted by JimBrewster

Maybe a dumb question, but is there a good reason not to just run

Code:

slackpkg upgrade vtown

if I'm starting from an upgraded -current system with no ktown? When I run that command I get a full list of packages to upgrade, and I assume they will replace whatever is in the current kde installation? TIA...

If you just run slackpkg upgrade vtown, I believe it will only present upgrades from vtown of packages you currently have installed. You'd also want to run slackpkg install vtown to get any new packages and slackpkg remove kde{,i} to get rid of the kde4 packages.