Building the KDE4 for Slackware 15.0 in the KTown style - a build based on the PBSLACKS patches

LuckyCyborg · 02-23-2023, 03:55 AM

Quote:

Originally Posted by BrunoLafleur

Sorry I have forgotten to put the last version which I have compiled and put on my machine.
The one you have is broken and is not workable.

I have just upload the good one.

Yes, the new tarball compiles clean and the package is generated successfully.

HOWEVER, the plasma-nm build now fails with libnm-qt-1.0.1

Code:

...
Generating moc_handler.cpp
Generating moc_networkmodel.cpp
Generating moc_networkmodelitem.cpp
[ 11%] Built target plasmanetworkmanagement-internal_automoc
Consolidate compiler generated dependencies of target plasmanetworkmanagement-internal
[ 11%] Building CXX object libs/CMakeFiles/plasmanetworkmanagement-internal.dir/plasmanetworkmanagement-internal_automoc.cpp.o
[ 11%] Linking CXX shared library ../lib/libplasmanetworkmanagement-internal.so
[ 13%] Built target plasmanetworkmanagement-internal
Consolidate compiler generated dependencies of target kde-nm-connection-editor
[ 13%] Building CXX object editor/CMakeFiles/kde-nm-connection-editor.dir/kde-nm-connection-editor_automoc.cpp.o
[ 13%] Building CXX object editor/CMakeFiles/kde-nm-connection-editor.dir/connectioneditor.cpp.o
/tmp/kde_build/extragear/plasma-nm-0.9.3.6/editor/connectioneditor.cpp: In member function ‘void ConnectionEditor::importVpn()’:
/tmp/kde_build/extragear/plasma-nm-0.9.3.6/editor/connectioneditor.cpp:517:95: error: ‘QString’ is an inaccessible base of ‘QDBusObjectPath’
  517 |                 const QString conId = NetworkManager::addConnection(connectionSettings.toMap());
      |                                                                                               ^
In file included from /usr/lib64/qt/include/QtDBus/qdbusreply.h:52,
                 from /usr/lib64/qt/include/QtDBus/qdbusconnectioninterface.h:48,
                 from /usr/lib64/qt/include/QtDBus/QtDBus:8,
                 from /usr/include/ModemManagerQt/generic-types.h:28,
                 from /usr/include/NetworkManagerQt/settings/setting.h:27,
                 from /usr/include/NetworkManagerQt/settings/connectionsettings.h:27,
                 from /usr/include/NetworkManagerQt/connection.h:28,
                 from /usr/include/NetworkManagerQt/Connection:1,
                 from /tmp/kde_build/extragear/plasma-nm-0.9.3.6/libs/handler.h:26,
                 from /tmp/kde_build/extragear/plasma-nm-0.9.3.6/editor/connectioneditor.h:25,
                 from /tmp/kde_build/extragear/plasma-nm-0.9.3.6/editor/connectioneditor.cpp:22:
/usr/lib64/qt/include/QtDBus/qdbuspendingreply.h:184:12: note:   after user-defined conversion: ‘QDBusPendingReply<T1, T2, T3, T4, T5, T6, T7, T8>::operator typename QDBusPendingReply<T1, T2, T3, T4, T5, T6, T7, T8>::Select<0>::Type() const [with T1 = QDBusObjectPath; T2 = void; T3 = void; T4 = void; T5 = void; T6 = void; T7 = void; T8 = void; typename QDBusPendingReply<T1, T2, T3, T4, T5, T6, T7, T8>::Select<0>::Type = QDBusObjectPath]’
  184 |     inline operator typename Select<0>::Type() const
      |            ^~~~~~~~
make[2]: *** [editor/CMakeFiles/kde-nm-connection-editor.dir/build.make:108: editor/CMakeFiles/kde-nm-connection-editor.dir/connectioneditor.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:1406: editor/CMakeFiles/kde-nm-connection-editor.dir/all] Error 2
make: *** [Makefile:146: all] Error 2
extragear:plasma-nm failed to build.

marav · 02-23-2023, 04:00 AM

Quote:

Originally Posted by LuckyCyborg

There is the download link for latest KDE4 build of mine, uploaded in two tarballs - one for sources (1.59 GB) and one for packages (1.06 GB).

https://easyupload.io/m/9fghwj

The SHA256SUMS are bellow:

Code:

7bd0780da2bcbda0d5ecb02684d4eeae96cbbbe59db21c3262148b6448e64dcc  kde4town-packages-20230220.tar
f7cc6dfdd6bce825e6a35c48ccf2cce4842b4a79fefa383e992a29f9bf66b259  kde4town-source-20230220.tar

Updated here:
https://matoda.pw/publik/KDE4_town/v2/

Note: of course, let me know if anyone has access problems.

LuckyCyborg · 02-23-2023, 04:02 AM

Quote:

Originally Posted by marav

Updated here:
https://matoda.pw/publik/KDE4_town/v2/

Many thanks, Monsieur Marav!

LuckyCyborg · 02-23-2023, 04:09 AM

Quote:

Originally Posted by ZhaoLin1457

In fact, I think we ended up talking about 3 problems, because it seems that I found a solution for the KDM autologin problems. It's about PAM.

post-install/kde-workspace/config/kde.pamd

Code:

#%PAM-1.0

auth       substack     system-auth

# Uncomment this line to restrict login to users with a UID greater
# than 999 (in other words, don't allow login for root):
#auth       required     pam_succeed_if.so        uid >= 1000 quiet

-auth      optional     pam_gnome_keyring.so
auth       include      postlogin

account    include      system-auth

password   substack     system-auth
-password  optional     pam_gnome_keyring.so     use_authtok

session    optional     pam_keyinit.so           force revoke
session    substack     system-auth
session    required     pam_loginuid.so
-session   optional     pam_elogind.so
-session   optional     pam_gnome_keyring.so     auto_start
session    include      postlogin

post-install/kde-workspace/config/kde-np.pamd

Code:

#%PAM-1.0

auth       requisite    pam_nologin.so
auth       required     pam_env.so
auth       required     pam_shells.so

# Uncomment this line to restrict autologin to users with a UID greater
# than 999 (in other words, don't allow autologin for root):
#auth       required     pam_succeed_if.so uid >= 1000 quiet

auth       required     pam_permit.so

account    include      system-auth

password   include      system-auth

session    substack     system-auth
session    required     pam_loginuid.so
-session   optional     pam_elogind.so
-session   optional     pam_gnome_keyring.so     auto_start
session    include      postlogin

With these PAM files there is no difference between how the KDE4 desktop works with normal login and autologin in KDM.

Please note that I have no idea if KDE4 distributes a PAM module for KWallet.

Yes, this does the job. Many thanks!

LuckyCyborg · 02-23-2023, 04:10 AM

However, even with successful upgrade to libnm-qt-1.0.1 (but with not rebuilt plasma-nm) the NetworkManager widget and configuration works the same - the interface is updated only on startup.

ZhaoLin1457 · 02-23-2023, 08:34 AM

Quote:

Originally Posted by LuckyCyborg

However, even with successful upgrade to libnm-qt-1.0.1 (but with not rebuilt plasma-nm) the NetworkManager widget and configuration works the same - the interface is updated only on startup.

Additional patches are probably needed for plasma-nm to work with the new libnm-qt.

Let's be patient for @BrunoLafleur to do his magic, and in the meantime let's study the other 2 problems. Which I think could have the same cause, a problem with QML logic. So, actually being only one problem.

What's strange is that the base is that KDE4 that went great in Slackware. I haven't encountered any problems with notifications or adding Plasma widgets in the past. So what exactly is wrong? Is a dependency missing? Is one of the dependencies having problems?

BrunoLafleur · 02-23-2023, 09:56 AM

https://github.com/BrunoLafleur/pbsl...lasma-nm.patch

with :
https://github.com/BrunoLafleur/pbsl...1.0.1.patch.gz

It should compile and it works on my old Slackware. But it is probably not enough for libnm-qt and the new NetworkManager 1.32

I have to dig more.

BrunoLafleur · 02-23-2023, 10:04 AM

Quote:

Originally Posted by ZhaoLin1457

Additional patches are probably needed for plasma-nm to work with the new libnm-qt.

Let's be patient for @BrunoLafleur to do his magic, and in the meantime let's study the other 2 problems. Which I think could have the same cause, a problem with QML logic. So, actually being only one problem.

What's strange is that the base is that KDE4 that went great in Slackware. I haven't encountered any problems with notifications or adding Plasma widgets in the past. So what exactly is wrong? Is a dependency missing? Is one of the dependencies having problems?

I have no clue. It has appeared somewhere between 2019 and 2021. I have kept 3 versions of the older current from there.

But I don't see anything apart that qml for qt4 (the same as in 2019-2020) don't seem to work well as for those two commands :
qmlplugindump-qt4 -nonrelocatable org.kde.plasma.components 1.0
qmlplugindump-qt5 -nonrelocatable org.kde.plasma.components 2.0

I have seen this problem even before I began to recompile all kde4 when it was in the Slackware current.

As LuckyCyborg says I have rendered qt4 and qt5 as independant so we can compile with qt5 here. And he has tested with only qt4 so qt5 seems not be guilty.

qml seems to communicate via dbus so maybe there is some changes in that area I didn't see. Or with Xorg for mouse support (message pointed in this thread for MouseArea event not recognized).

LuckyCyborg · 02-23-2023, 10:28 AM

Quote:

Originally Posted by BrunoLafleur

https://github.com/BrunoLafleur/pbsl...lasma-nm.patch

with :
https://github.com/BrunoLafleur/pbsl...1.0.1.patch.gz

It should compile and it works on my old Slackware. But it is probably not enough for libnm-qt and the new NetworkManager 1.32

I have to dig more.

Yes, with this patch the plasma-nm package is compiled successfully.

BUT, like you already suspected, nothing changed in the behavior of NetworkManager's widget and config tool.

LuckyCyborg · 02-23-2023, 10:35 AM

Quote:

Originally Posted by BrunoLafleur

I have no clue. It has appeared somewhere between 2019 and 2021. I have kept 3 versions of the older current from there.

But I don't see anything apart that qml for qt4 (the same as in 2019-2020) don't seem to work well as for those two commands :
qmlplugindump-qt4 -nonrelocatable org.kde.plasma.components 1.0
qmlplugindump-qt5 -nonrelocatable org.kde.plasma.components 2.0

I have seen this problem even before I began to recompile all kde4 when it was in the Slackware current.

As LuckyCyborg says I have rendered qt4 and qt5 as independant so we can compile with qt5 here. And he has tested with only qt4 so qt5 seems not be guilty.

qml seems to communicate via dbus so maybe there is some changes in that area I didn't see. Or with Xorg for mouse support (message pointed in this thread for MouseArea event not recognized).

Well, I remember that my friend (who made the patches) said that at least in the Widgets Explorer (the widgets bar) case it looks like it's a QML issue and more particularly it has issues with loading a thing named MenuItem. BUT, he does not did any further investigations.

Again, trying the widgets bar, I got in the ~/.xsession-errors

Code:

kwin(6497) KWin::Client::configureRequest: KWin::Client(0x1fd5890) true false false
kwin(6497) KWin::Client::configureRequest: PERMITTED 'ID: 31457836 ;WMCLASS: "plasma-desktop" : "plasma-desktop" ;Caption: "plasma-desktop" ' true
kwin(6497) KWin::Client::configureRequest: KWin::Client(0x1fd5890) true false false
kwin(6497) KWin::Client::configureRequest: PERMITTED 'ID: 31457836 ;WMCLASS: "plasma-desktop" : "plasma-desktop" ;Caption: "plasma-desktop" ' true
kwin(6497) KWin::Client::configureRequest: KWin::Client(0x1fd5890) true false false
kwin(6497) KWin::Client::configureRequest: PERMITTED 'ID: 31457836 ;WMCLASS: "plasma-desktop" : "plasma-desktop" ;Caption: "plasma-desktop" ' true
plasma-desktop(6514)/libplasma Plasma::DeclarativeWidgetPrivate::errorPrint: "file:///usr/share/apps/plasma/packages/org.kde.desktop.widgetexplorer/contents/ui/main.qml
Error loading QML file.
51: Cannot assign to non-existent property "onClicked"
".
QDeclarativeComponent: Component is not ready
plasma-desktop(6514)/libplasma Plasma::DeclarativeWidgetPrivate::errorPrint: "file:///usr/share/apps/plasma/packages/org.kde.desktop.widgetexplorer/contents/ui/main.qml
Error loading QML file.
51: Cannot assign to non-existent property "onClicked"
".
kwin(6497) KWin::Client::configureRequest: KWin::Client(0x1fd5890) true false false
kwin(6497) KWin::Client::configureRequest: PERMITTED 'ID: 31457836 ;WMCLASS: "plasma-desktop" : "plasma-desktop" ;Caption: "plasma-desktop" ' true
kwin(6497) KWin::Client::configureRequest: KWin::Client(0x1fd5890) true false false
kwin(6497) KWin::Client::configureRequest: PERMITTED 'ID: 31457836 ;WMCLASS: "plasma-desktop" : "plasma-desktop" ;Caption: "plasma-desktop" ' true
kwin(6497) KWin::Client::configureRequest: KWin::Client(0x1fd5890) true false false
kwin(6497) KWin::Client::configureRequest: PERMITTED 'ID: 31457836 ;WMCLASS: "plasma-desktop" : "plasma-desktop" ;Caption: "plasma-desktop" ' true

Looks like the failure actually happens there:

Code:

    Repeater {
        parent: categoriesDialog
        model: widgetExplorer.filterModel
        delegate: PlasmaComponents.MenuItem {
            text: display
            separator: model["separator"] ? model["separator"] : false
            onClicked: {
                list.contentX = 0
                list.contentY = 0
                var item = widgetExplorer.filterModel.get(index)

                widgetExplorer.widgetsModel.filterType = item.filterType
                widgetExplorer.widgetsModel.filterQuery = item.filterData
                main.categoryButton.text = item.display
            }
            Component.onCompleted: {
                parent = categoriesDialog
            }
        }
    }

where

Code:

import org.kde.plasma.components 0.1 as PlasmaComponents

So, looks like something is wrong with org.kde.plasma.components

BrunoLafleur · 02-23-2023, 11:11 AM

Maybe my kde-workspace-opengl.patch.gz is buggy for the menuitem. I should look after it.

ZhaoLin1457 · 02-23-2023, 11:16 AM

Quote:

Originally Posted by BrunoLafleur

Maybe my kde-workspace-opengl.patch.gz is buggy for the menuitem. I should look after it.

But wasn't this patch for a KInfoCenter module?

BrunoLafleur · 02-23-2023, 02:40 PM

Quote:

Originally Posted by ZhaoLin1457

But wasn't this patch for a KInfoCenter module?

Yes it seems to work. I don't know what could have changed because qt4 and kde-workspace didn't change since a long time.

And the main.qcm file which give an error in .xsession-error is in kde-workspace and qcm is the one inside qt4.

And the problem exist since before I recompile and redo the qt4.Slackbuild script.

But qcm is connected to dbus, so there maybe a difference here. There is something like dbusmenu I didn't explore. A lot of things have changed in this area.

I was thinking of an interaction with qt5 also because I have a lot of qt5 stuff. But this doesn't seem to be the problem.

LuckyCyborg · 02-26-2023, 12:49 AM

@BrunoLafleur

So, today I do some debugging on my KDE4 build trying to see/uderstand WHY the notifications aren't shown.

Meanwhile, on ~/.xsession-errors I have noticed something which may be interesting for the NetworkManager integration:

Code:

NetworkManagerQt "kded" ( 5666 ) NetworkManager::Device::Ptr NetworkManager::NetworkManagerPrivate::createNetworkInterface(const QString&) : libNetworkManagerQt: Can't create object of type  14 11 for "/org/freedesktop/NetworkManager/Devices/1" 
Object::connect: No such signal OrgFreedesktopDBusObjectManagerInterface::InterfacesAdded(QDBusObjectPath,NMVariantMapMap) in /tmp/kde_build/extragear/libmm-qt-1.0.1/manager.cpp:61
NetworkManagerQt "kded" ( 5666 ) void NetworkManager::NetworkManagerPrivate::propertiesChanged(const QVariantMap&) :    "/org/freedesktop/NetworkManager/ActiveConnection/1"

LuckyCyborg · 02-26-2023, 06:24 AM

So, I can confirm that the notifications lack is generated by a QML issue...

On ~/.xsession-errors I found:

Code:

file:///usr/share/apps/plasma/plasmoids/org.kde.notifications/contents/ui/Notifications.qml:226:19: Type NotificationDelegate unavailable
plasmapackage:/ui/NotificationDelegate/NotificationDelegate.qml:189:25: Cannot assign to non-existent property "onClicked"

where

Code:

                PlasmaComponents.ContextMenu {
                    id: contextMenu
                    visualParent: contextMouseArea
                    PlasmaComponents.MenuItem {
                        text: i18n("Copy")
                        onClicked: bodyText.copy()
                    }
                    PlasmaComponents.MenuItem {
                        text: i18n("Select All")
                        onClicked: bodyText.selectAll()
                    }
                }

Again, it's all about the MenuItem failure(s), just like in the case of Widgets Explorer...

Anyway, I do NOT believe that there's a DBUS related issue, because effectively the Desktop Notifications service does not arrive to be registered to DBUS - I looked with qdbusviewer(-qt4) and there's not registered org.freedesktop.Notifications .

AND, I have have successfully built and packaged the Colibri Notifications on EXTRAGEAR, which works like a charm.

https://github.com/KDE/colibri

So, I can confirm the ZhaoLin1457's suspicion that the issues with the Widgets Explorer and Desktop Notifications are in fact manifestations of a single QML issue.

The moral of this story is that right now we have just 2 issues: one with the (MenuItem from) QML and the second one with the NetworkManager integration.