LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   All Things KDE5/Plasma for Slackware Users. (https://www.linuxquestions.org/questions/slackware-14/all-things-kde5-plasma-for-slackware-users-4175670109/)

sombragris 10-14-2021 11:15 PM

Bug reported upstream on removal of the cover switch effect (in fact, a bunch of effects were removed).

Should you wish to comment or show support (hopefully), here it is:

https://bugs.kde.org/show_bug.cgi?id=443757

Thanks in advance.

LuckyCyborg 10-15-2021 03:30 AM

Quote:

Originally Posted by USUARIONUEVO (Post 6292143)
Other plasma update , other nasty bug ...

I have enabled in the context menu the option "delete"

After upgrade to plasma 5.23 , i CANT , delete nothing in my desktop.

1 - I have configured as "desktop folder"
2 - In dolphin , preferences i enabled "delete" servicemenu
3 - make new file or something in desktop
4 - right click in file to options, delete

does nothing.

And ark bug , remains , thats very nice kde team , nice anniversary edition .. (ironic off)

https://bugs.kde.org/show_bug.cgi?id=440663

Full plage bugs every update ..... and not rare/strange actions from users , i think delete servicemenu is not a rare config , more users have enbaled ,im pretty sure.

Man, I really expected from you that you know that both Dolphin and Ark are 2 applications part of KDE Applications, so the upgrade of KDE Plasma (aka the desktop itself) changed absolute nothing.

LuckyCyborg 10-15-2021 03:42 AM

Quote:

Originally Posted by sombragris (Post 6292154)
Bug reported upstream on removal of the cover switch effect (in fact, a bunch of effects were removed).

Should you wish to comment or show support (hopefully), here it is:

https://bugs.kde.org/show_bug.cgi?id=443757

Thanks in advance.

From the notes of the pull request for removal of this effect, I understand that it does not work anymore and it needs to be rewritten or to be removed. Unfortunately for you, they chosen the second option.

Code:

effects: Remove Cover Switch effect

With the ongoing scene redesign, it needs to be rewritten. However,
given that it is not used widely based on support information from
various bug reports and our available man power is sparse, the most
reasonable thing is to drop the effect, unfortunately.

https://invent.kde.org/plasma/kwin/-...abfa74da40fe8f

nobodino 10-15-2021 07:14 AM

digikam is still crashing. I tested what was recommended by chrisretusn in post #1035, but no luck.

ctrlaltca 10-15-2021 07:26 AM

Quote:

Originally Posted by nobodino (Post 6292251)
digikam is still crashing. I tested what was recommended by chrisretusn in post #1035, but no luck.

Are you running it as root? If yes, can you try as a normal user?
Do you get the "digikam has crashed" dialog (drkonqui?) if you do, can you copypaste here the crash backtrace?

LuckyCyborg 10-15-2021 07:29 AM

Quote:

Originally Posted by nobodino (Post 6291317)
same problem here despite the fact that "ldd /usr/bin/digikam | grep vidstab" is ok.
--------------------------
root@xxxxxxx:~/scripts# digikam
QFSFileEngine:: open: No file name specified
digikam.facedb: Cannot found faces engine model "shapepredictor.dat"
digikam.facedb: Faces recognition feature cannot be used!
digikam.facedb: Cannot found faces engine DNN model "openface_nn4.small2.v1.t7"
digikam.facedb: Faces recognition feature cannot be used!
[15437:15437:1012/131448.019916:ERROR:zygote_host_impl_linux.cc(89)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = digikam path = /usr/bin pid = 15437
KCrash: Arguments: /usr/bin/digikam
KCrash: Attempting to start /usr/lib64/libexec/drkonqi
-------------------------

Quote:

Originally Posted by nobodino (Post 6292251)
digikam is still crashing. I tested what was recommended by chrisretusn in post #1035, but no luck.

Yep, this is yet another example how silly is for developers to make their applications to refuse to work as root, in the name of "security" .

In fact, is like hiding the dirt under the kitchen sink, and humble me believes that the proper way is to fix those eventual damn security issues instead to play "no root for you!"

So, your issue is in fact that the Chromium code refuses to work as root, because reasons.

Then, how it's used by QtWebEngine, any application which tries fancy things with it, will fail to run as root.

The solution is to add this snippet to your ~/.profile and to reboot or logout/login

Code:

# Disable the QtWebEngine's sandbox to make Konqueror and Falkon to work as root.
export QTWEBENGINE_DISABLE_SANDBOX=1

As bonus, will work also as root the Plasma5's web-browsers: Konqueror and Falkon

nobodino 10-15-2021 07:48 AM

I always run as root, I have no normal user for a long time now...
---------------------
[KCrash Handler]
#4 0x00007fdbeb9afa37 in QReadWriteLock::tryLockForWrite(int) () at /usr/lib64/libQt5Core.so.5
#5 0x00007fdbed9dea4d in () at /usr/lib64/libQt5Sql.so.5
#6 0x00007fdbee362bd3 in () at /usr/lib64/libdigikamcore.so.7.3.0
#7 0x00007fdbee362cdd in () at /usr/lib64/libdigikamcore.so.7.3.0
#8 0x00007fdbee36a8ee in () at /usr/lib64/libdigikamcore.so.7.3.0
#9 0x00007fdbeb9b361f in QThreadStorageData::finish(void**) () at /usr/lib64/libQt5Core.so.5
#10 0x00007fdbeb9adb1d in () at /usr/lib64/libQt5Core.so.5
#11 0x00007fdbeb9ae329 in () at /usr/lib64/libQt5Core.so.5
#12 0x00007fdbeb50ee45 in start_thread () at /lib64/libpthread.so.0
#13 0x00007fdbeb43244f in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fdbcdf44640 (LWP 30607) "QDBusConnection"):
#1 0x00007fdbdbd047cc in () at /usr/lib64/libglib-2.0.so.0
#2 0x00007fdbdbd048ef in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3 0x00007fdbebbe1fb6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4 0x00007fdbebb8d04b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5 0x00007fdbeb9ad31e in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x00007fdbecdd6447 in () at /usr/lib64/libQt5DBus.so.5
#7 0x00007fdbeb9ae321 in () at /usr/lib64/libQt5Core.so.5
#8 0x00007fdbeb50ee45 in start_thread () at /lib64/libpthread.so.0
#9 0x00007fdbeb43244f in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fdbd60a6640 (LWP 30606) "QXcbEventQueue"):
#1 0x00007fdbde5e6cb2 in () at /usr/lib64/libxcb.so.1
#2 0x00007fdbde5e8d3a in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3 0x00007fdbd618f190 in () at /usr/lib64/libQt5XcbQpa.so.5
#4 0x00007fdbeb9ae321 in () at /usr/lib64/libQt5Core.so.5
#5 0x00007fdbeb50ee45 in start_thread () at /lib64/libpthread.so.0
#6 0x00007fdbeb43244f in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fdbd6337180 (LWP 30599) "digikam"):
#1 0x00007fdbeb514d41 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#2 0x00007fdbeb9b3e9b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5
#3 0x00007fdbeb9ae059 in QThread::wait(QDeadlineTimer) () at /usr/lib64/libQt5Core.so.5
#4 0x00007fdbef0ed776 in Digikam::ScanController::~ScanController() () at /usr/lib64/libdigikamgui.so.7.3.0
#5 0x00007fdbef0ed859 in () at /usr/lib64/libdigikamgui.so.7.3.0
#6 0x00007fdbeb3654a7 in __run_exit_handlers () at /lib64/libc.so.6
#7 0x00007fdbeb36564a in () at /lib64/libc.so.6
#8 0x00007fdbe6e1df18 in () at /usr/lib64/libQt5WebEngineCore.so.5
#9 0x0000000000000012 in ()
#10 0x0000000000000000 in ()
[Inferior 1 (process 30599) detached]
-----------------------

LuckyCyborg 10-15-2021 07:50 AM

@nobodino

Did you setup that environment variable?

I tried the DigiKam and works fine on my system, both as root and unprivileged user.

nobodino 10-15-2021 07:57 AM

You're right LuckyCyborg with the change in the .profile, it works for the 3 apps. I had to reboot, otherwise it wasn't taken in account.
Thanks for your help.

LuckyCyborg 10-15-2021 08:09 AM

@nobodino

BTW, with that environment variable, will work also Mr. Hameleers' Chromium as root. ;)

marav 10-15-2021 11:15 AM

Quote:

Originally Posted by marav (Post 6292099)
I observed this behavior only without the title bar.

edit : but not on my VM ... :scratch:

Same with a fresh new install with the latest alienbob iso from yesterday with plasma 5.23

Nothing to report with XFCE ...

USUARIONUEVO 10-15-2021 11:31 AM

Quote:

Originally Posted by LuckyCyborg (Post 6292200)
Man, I really expected from you that you know that both Dolphin and Ark are 2 applications part of KDE Applications, so the upgrade of KDE Plasma (aka the desktop itself) changed absolute nothing.

I know ark is from applications , but the other issue comes now , after plasma 5.23 , im no start to bisect what package cause this issue , my first candidate is

plasma-desktop FROM PLASMA 5.23 ? :)

Im not happy with latest kde updates in general , remember konsole broken , overwrite files crasj dolphin , and other issues talk here in las months , but this is strange cause is after lasta 2 or 3 months , when start thinking on QT6 code.

Im not happy cause are very easy things to see ... i start thinking kde developers no use never kde ;=)

How is possible a regular user see bugs after 5 minutes of usage , and developers never see ? its strange for me , thats all.

USUARIONUEVO 10-15-2021 11:43 AM

See this one , sddm ,field problems ...PATCH , for workspace 5.23

https://invent.kde.org/plasma/plasma...d5a3e749.patch


Other very nice thing ...

https://invent.kde.org/plasma/plasma...e_requests/591


Its incredible...

marav 10-15-2021 11:51 AM

I can deal with problems in a 5.23.0 release
we have to be patient until around 5.23.3 where, generaly most of the important bugs are solved

I just reinstalled my latop with a fresh install to check that it was not my conf
lack of luck it was not that

the good point : I have a very clean slackware :)

LuckyCyborg 10-15-2021 11:55 AM

@USUARIONUEVO

It's a great thing that you try to find bugs on Plasma 5.23.x , but let's do not jump over horse... ;)

Please take note that in the next weeks, there will be 2 patch releases at one week interval, then another one after only 2 weeks.

IF you found something wrong, be kind to report that to KDE developers, to take a look.

I for one, for my daily usage, the Plasma 5.23 works perfectly. Heck, worked well even the Plasma 5.23 Beta.

However, I use the default settings of Plasma5, in general. I change only the Konsole colors and I make the window bar smaller while adding a small frame around window.


All times are GMT -5. The time now is 01:48 AM.