LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-26-2023, 11:49 AM   #61
ZhaoLin1457
Senior Member
 
Registered: Jan 2018
Posts: 1,022

Rep: Reputation: 1208Reputation: 1208Reputation: 1208Reputation: 1208Reputation: 1208Reputation: 1208Reputation: 1208Reputation: 1208Reputation: 1208

Quote:
Originally Posted by LuckyCyborg View Post
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.
In fact, the problem with the NetworkManager integration is more of an update to a new version of NetworkManager, so the only real problem is the one with QML.

BTW, I found a solution to create the Step package without an Eigen2 one. Considering that Eigen2 is only necessary for Step, and that Eigen2 is actually a set of C++ headers, it is possible to use it locally.

cmake/step
Code:
mkdir build
cd build
  cmake \
    $KDE_OPT_ARGS \
    -DCMAKE_PREFIX_PATH="$PKG/eigen2" \
    -DKDE_PLATFORM_FEATURE_DISABLE_DEPRECATED=TRUE \
    -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_C_FLAGS_RELEASE:STRING="$SLKCFLAGS" \
    -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS  -std=c++11 -fpermissive" \
    -DCMAKE_CXX_FLAGS_RELEASE:STRING="$SLKCFLAGS -std=c++11 -fpermissive" \
    -DCMAKE_BUILD_TYPE=Release \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -DMAN_INSTALL_DIR=/usr/man \
    -DSYSCONF_INSTALL_DIR=/etc/kde \
    -DLIB_SUFFIX=${LIBDIRSUFFIX} \
    ..
pre-install/step.pre-install
Code:
# First, build and install Eigen2:
cd $CWD/pre-install/step/eigen2
  echo "Building Eigen2..."
  ARCH=$ARCH sh ./eigen2.build $PKG
cd -

pre-install/step/eigen2/eigen2.build

Code:
#!/bin/sh

# Copyright 2007, 2008  Robby Workman, Northport, Alabama, USA
# Copyright 2008, 2009, 2015  Patrick J. Volkerding, Sebeka, MN, USA
# All rights reserved.

# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


PKGNAM=eigen2
VERSION=2.0.17
SRCVER="eigen-b23437e61a07"

# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) export ARCH=i586 ;;
    arm*) export ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) export ARCH=$( uname -m ) ;;
  esac
fi

CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
PKG=$1

if [ "$ARCH" = "i586" ]; then
  SLKCFLAGS="-O2 -march=i586 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "s390" ]; then
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
fi

rm -rf $PKG/$PKGNAM
mkdir -p $TMP $PKG/$PKGNAM
cd $TMP || exit 1
rm -rf eigen-eigen-*
tar xvf $CWD/$PKGNAM-$VERSION.tar.?z* || exit 1
cd eigen-$SRCVER || exit 1
chown -R root:root .
find . \
 \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
 -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
 -exec chmod 644 {} \;

mkdir -p build
cd build
  cmake \
    -DCMAKE_BUILD_TYPE=Release \
    -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_INSTALL_PREFIX=/$PKGNAM \
    ..
   make || exit 1
   make install DESTDIR=$PKG || exit 1
cd -
post-install/step.post-install
Code:
# Remove the installed Eigen2
rm -rf $PKG/eigen2
The source tarball should be pre-install/step/eigen2/eigen2-2.0.17.tar.xz
 
2 members found this post helpful.
Old 02-26-2023, 12:13 PM   #62
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,500

Original Poster
Rep: Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309
Quote:
Originally Posted by ZhaoLin1457 View Post
In fact, the problem with the NetworkManager integration is more of an update to a new version of NetworkManager, so the only real problem is the one with QML.
Yeah, you can say that.

And regarding the updates for NetworkManager integration, our only hope is BrunoLafleur, considering the amount of changes made.

So, the moral of this story is that what is of tinkering is this QML issue.

Quote:
Originally Posted by ZhaoLin1457 View Post
BTW, I found a solution to create the Step package without an Eigen2 one. Considering that Eigen2 is only necessary for Step, and that Eigen2 is actually a set of C++ headers, it is possible to use it locally.

cmake/step
Code:
mkdir build
cd build
  cmake \
    $KDE_OPT_ARGS \
    -DCMAKE_PREFIX_PATH="$PKG/eigen2" \
    -DKDE_PLATFORM_FEATURE_DISABLE_DEPRECATED=TRUE \
    -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_C_FLAGS_RELEASE:STRING="$SLKCFLAGS" \
    -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS  -std=c++11 -fpermissive" \
    -DCMAKE_CXX_FLAGS_RELEASE:STRING="$SLKCFLAGS -std=c++11 -fpermissive" \
    -DCMAKE_BUILD_TYPE=Release \
    -DCMAKE_INSTALL_PREFIX=/usr \
    -DMAN_INSTALL_DIR=/usr/man \
    -DSYSCONF_INSTALL_DIR=/etc/kde \
    -DLIB_SUFFIX=${LIBDIRSUFFIX} \
    ..
pre-install/step.pre-install
Code:
# First, build and install Eigen2:
cd $CWD/pre-install/step/eigen2
  echo "Building Eigen2..."
  ARCH=$ARCH sh ./eigen2.build $PKG
cd -

pre-install/step/eigen2/eigen2.build

Code:
#!/bin/sh

# Copyright 2007, 2008  Robby Workman, Northport, Alabama, USA
# Copyright 2008, 2009, 2015  Patrick J. Volkerding, Sebeka, MN, USA
# All rights reserved.

# Redistribution and use of this script, with or without modification, is
# permitted provided that the following conditions are met:
#
# 1. Redistributions of this script must retain the above copyright
#    notice, this list of conditions and the following disclaimer.
#
# THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
# EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
# OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
# OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
# ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


PKGNAM=eigen2
VERSION=2.0.17
SRCVER="eigen-b23437e61a07"

# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
  case "$( uname -m )" in
    i?86) export ARCH=i586 ;;
    arm*) export ARCH=arm ;;
    # Unless $ARCH is already set, use uname -m for all other archs:
       *) export ARCH=$( uname -m ) ;;
  esac
fi

CWD=$(pwd)
TMP=${TMP:-/tmp/SBo}
PKG=$1

if [ "$ARCH" = "i586" ]; then
  SLKCFLAGS="-O2 -march=i586 -mtune=i686"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "s390" ]; then
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
  SLKCFLAGS="-O2 -fPIC"
  LIBDIRSUFFIX="64"
else
  SLKCFLAGS="-O2"
  LIBDIRSUFFIX=""
fi

rm -rf $PKG/$PKGNAM
mkdir -p $TMP $PKG/$PKGNAM
cd $TMP || exit 1
rm -rf eigen-eigen-*
tar xvf $CWD/$PKGNAM-$VERSION.tar.?z* || exit 1
cd eigen-$SRCVER || exit 1
chown -R root:root .
find . \
 \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \
 -exec chmod 755 {} \; -o \
 \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \
 -exec chmod 644 {} \;

mkdir -p build
cd build
  cmake \
    -DCMAKE_BUILD_TYPE=Release \
    -DCMAKE_C_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_CXX_FLAGS:STRING="$SLKCFLAGS" \
    -DCMAKE_INSTALL_PREFIX=/$PKGNAM \
    ..
   make || exit 1
   make install DESTDIR=$PKG || exit 1
cd -
post-install/step.post-install
Code:
# Remove the installed Eigen2
rm -rf $PKG/eigen2
The source tarball should be pre-install/step/eigen2/eigen2-2.0.17.tar.xz
Many thanks!

I will test this and eventually adopt it. I have no strong feelings for that Eigen2 package.

Last edited by LuckyCyborg; 02-27-2023 at 02:08 AM.
 
2 members found this post helpful.
Old 02-26-2023, 12:46 PM   #63
BrunoLafleur
Member
 
Registered: Apr 2020
Location: France
Distribution: Slackware
Posts: 401

Rep: Reputation: 366Reputation: 366Reputation: 366Reputation: 366
Quote:
Yeah, you can say that.

And regarding the updates for NetworkManager integration, our only hope is BrunoLafleur, considering the amount of changes made.

So, the moral of this story is that what is of tinkering is this QML issue.
For NetworkManager I have now a Slackware 15.0 install so that I can test and see the differences. It is the deprecated issue with NetworkManager I speak about above. I can see the differences in the .xsession-errors.

For QML maybe I will find the reason and correct it. When I will have more time. I have seen the .xsession-errors message some time ago but that don't really help me. So I try to see what has changed. I have some other ideas like bad config with qt4 in one of the deps/other/kde4 packages (some are old and cmake has also changed).
 
3 members found this post helpful.
Old 02-26-2023, 12:47 PM   #64
BrunoLafleur
Member
 
Registered: Apr 2020
Location: France
Distribution: Slackware
Posts: 401

Rep: Reputation: 366Reputation: 366Reputation: 366Reputation: 366
In the mean time your patches and ideas are really good and help me to keep my favorite desktop alive.
 
4 members found this post helpful.
Old 02-26-2023, 03:21 PM   #65
BrunoLafleur
Member
 
Registered: Apr 2020
Location: France
Distribution: Slackware
Posts: 401

Rep: Reputation: 366Reputation: 366Reputation: 366Reputation: 366
Just a grab from my KDE4 desktop.

Click image for larger version

Name:	FondBlSlackKDE4b.png
Views:	71
Size:	193.4 KB
ID:	40530
 
2 members found this post helpful.
Old 03-07-2023, 11:04 AM   #66
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,500

Original Poster
Rep: Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309
Quote:
Originally Posted by BrunoLafleur View Post
For NetworkManager I have now a Slackware 15.0 install so that I can test and see the differences. It is the deprecated issue with NetworkManager I speak about above. I can see the differences in the .xsession-errors.
Speaking of this NetworkManager integration, I have tested carefully your new libnm-qt-1.0.2 and I can say that it's a huge leap forward.

So, it almost works.

However, the Network configurator and the widget interface still have mishits - I hope that you will fix them soon.

BTW, even I know well that the Notifications are broken because of the QML issue, I have noticed that when a connection is made some kind of (ugly) notifications are show in top middle of the screen.

My question is: what the heck is that? It's a fallback notifications system of KDE4 or it's just some kind of visual debugging enabled by you?

Quote:
Originally Posted by BrunoLafleur View Post
For QML maybe I will find the reason and correct it. When I will have more time. I have seen the .xsession-errors message some time ago but that don't really help me. So I try to see what has changed. I have some other ideas like bad config with qt4 in one of the deps/other/kde4 packages (some are old and cmake has also changed).
Since you posted this, I have fully rebuilt my KDE4 build for several times, looking for build issues.

Unfortunately, this QML issue is still present as usual. Still looking.

Last edited by LuckyCyborg; 03-07-2023 at 01:12 PM.
 
2 members found this post helpful.
Old 03-10-2023, 10:31 AM   #67
BrunoLafleur
Member
 
Registered: Apr 2020
Location: France
Distribution: Slackware
Posts: 401

Rep: Reputation: 366Reputation: 366Reputation: 366Reputation: 366
Quote:
Originally Posted by LuckyCyborg View Post
Speaking of this NetworkManager integration, I have tested carefully your new libnm-qt-1.0.2 and I can say that it's a huge leap forward.

So, it almost works.

However, the Network configurator and the widget interface still have mishits - I hope that you will fix them soon.
I work on it. I have a better one but it have other problems. I have to do more tests.

Quote:
Originally Posted by LuckyCyborg View Post
BTW, even I know well that the Notifications are broken because of the QML issue, I have noticed that when a connection is made some kind of (ugly) notifications are show in top middle of the screen.

My question is: what the heck is that? It's a fallback notifications system of KDE4 or it's just some kind of visual debugging enabled by you?
It is not debugging from my part. I have them also. It comes from libnm-qt and maybe other parts of KDE4 and are dbus related. There is still some problems with libnm-qt. I work on it but not very quickly. I am not retired and work on some large projects.

Quote:
Originally Posted by LuckyCyborg View Post
Since you posted this, I have fully rebuilt my KDE4 build for several times, looking for build issues.

Unfortunately, this QML issue is still present as usual. Still looking.
I don't have time to look after that problem. I have to look after the glib lib which may have changed . KDE4 use glib-dbus which is somewhat deprecated. There is now the coupling glib with gio for dbus. May be there is some mismatch here.
 
3 members found this post helpful.
Old 03-10-2023, 11:12 AM   #68
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,500

Original Poster
Rep: Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309
Quote:
Originally Posted by BrunoLafleur View Post
I work on it. I have a better one but it have other problems. I have to do more tests.
I can wait to test this new NetworkManager integration! Honestly, I started to believe that's the only big showstopper in the daily usage of KDE4 on Slackware 15.0 and probably the 15.1 too.

Quote:
Originally Posted by BrunoLafleur View Post
It is not debugging from my part. I have them also. It comes from libnm-qt and maybe other parts of KDE4 and are dbus related. There is still some problems with libnm-qt. I work on it but not very quickly. I am not retired and work on some large projects.
Thanks for details! So, I should understand that's a fallback system for KDE4 notifications?

IF then, when my friend have time, I intends to ask him to "beautify" those fallback notifications a bit. Anyway they are much better than nothing.

Anyway, I have discovered an alternative - it's named Colibri Notifications and it works fine on this KDE4 build of mine.

Quote:
Originally Posted by BrunoLafleur View Post
I don't have time to look after that problem. I have to look after the glib lib which may have changed . KDE4 use glib-dbus which is somewhat deprecated. There is now the coupling glib with gio for dbus. May be there is some mismatch here.
Thanks for your efforts! They are greatly appreciated by me and certainly by others.

However, I would like to raise this point to you: if you want people to use your PBSLACKS, it should run in a stable release of Slackware. How many people you believe that they have those snapshots of -current used by you. Probably, few.

And for making PBSLACKS to work perfectly in the Slackware 15.0, obviously this issue is better to be fixed.

Last edited by LuckyCyborg; 03-10-2023 at 12:45 PM.
 
2 members found this post helpful.
Old 03-13-2023, 04:42 PM   #69
BrunoLafleur
Member
 
Registered: Apr 2020
Location: France
Distribution: Slackware
Posts: 401

Rep: Reputation: 366Reputation: 366Reputation: 366Reputation: 366
Quote:
Originally Posted by LuckyCyborg View Post
I can wait to test this new NetworkManager integration! Honestly, I started to believe that's the only big showstopper in the daily usage of KDE4 on Slackware 15.0 and probably the 15.1 too.



Thanks for details! So, I should understand that's a fallback system for KDE4 notifications?

IF then, when my friend have time, I intends to ask him to "beautify" those fallback notifications a bit. Anyway they are much better than nothing.

Anyway, I have discovered an alternative - it's named Colibri Notifications and it works fine on this KDE4 build of mine.



Thanks for your efforts! They are greatly appreciated by me and certainly by others.

However, I would like to raise this point to you: if you want people to use your PBSLACKS, it should run in a stable release of Slackware. How many people you believe that they have those snapshots of -current used by you. Probably, few.

And for making PBSLACKS to work perfectly in the Slackware 15.0, obviously this issue is better to be fixed.
Yes I am on it. I have almost recompiled all my packages I have with pbslacks in my new Slackware-15.0 test machine. I work also on libnm-qt and plasma-nm and some other little problems when I have some time.
 
3 members found this post helpful.
Old 03-23-2023, 04:31 PM   #70
BrunoLafleur
Member
 
Registered: Apr 2020
Location: France
Distribution: Slackware
Posts: 401

Rep: Reputation: 366Reputation: 366Reputation: 366Reputation: 366
I have done some improvements for the widgetexplorer :

https://github.com/BrunoLafleur/pbsl.../kde-workspace
https://github.com/BrunoLafleur/pbsl...orkspace.patch

Finally I just corrected the qml file and it worked. I don't know the real cause for the non supported deleted stuff.

There is also a patch in kde-workspace for opengl which fit better with Mesa.

There is also a new 1.0.3 version for libnm-qt and a new patch for plasma-nm

With a screen copy here in attachment.
Attached Thumbnails
Click image for larger version

Name:	FondBlSlackKDE4d.png
Views:	30
Size:	175.3 KB
ID:	40674  
 
3 members found this post helpful.
Old 03-23-2023, 04:39 PM   #71
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,500

Original Poster
Rep: Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309
Quote:
Originally Posted by BrunoLafleur View Post
I have done some improvements for the widgetexplorer :

https://github.com/BrunoLafleur/pbsl.../kde-workspace
https://github.com/BrunoLafleur/pbsl...orkspace.patch

Finally I just corrected the qml file and it worked. I don't know the real cause for the non supported deleted stuff.

There is also a patch in kde-workspace for opengl which fit better with Mesa.

There is also a new 1.0.3 version for libnm-qt and a new patch for plasma-nm

With a screen copy here in attachment.
WOW! Sincere congratulations!

And for notifications you managed to do something?

Unfortunately, now I am in a job trip, BUT in weekend this is what I will do first.

BTW, I hope that you did not removed the OpenGL 1.4 support from KWin with kde-workspace-opengl2.patch.gz ?

LATER:

Yep, exactly this you did it. Oh, well...

Not a big issue, let's hope it's an improvement - in the end, it's a patch which can be not applied at will.

However, this OpenGL 1.4 support on KWin was exactly one of the important features, considering the purpose of this experiment of mine: a KDE4 which works well on Intel graphics with support for OpenGL 1.4 only.

So, in future please be kind to clearly specify (or at least to announce me) which patches affects this OpenGL 1.4 support on KWin, because it's important for my purpose.

Last edited by LuckyCyborg; 03-23-2023 at 06:47 PM.
 
1 members found this post helpful.
Old 03-24-2023, 07:36 AM   #72
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,500

Original Poster
Rep: Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309
I have received a patch for notifications from that friend of mine who made the previous patches.
Code:
diff -urN kde-workspace-4.11.22.orig/plasma/generic/applets/notifications/contents/ui/NotificationDelegate/NotificationDelegate.qml kde-workspace-4.11.22/plasma/generic/applets/notifications/contents/ui/NotificationDelegate/NotificationDelegate.qml
--- kde-workspace-4.11.22.orig/plasma/generic/applets/notifications/contents/ui/NotificationDelegate/NotificationDelegate.qml	2015-08-12 10:03:15.000000000 +0300
+++ kde-workspace-4.11.22/plasma/generic/applets/notifications/contents/ui/NotificationDelegate/NotificationDelegate.qml	2023-03-24 02:09:41.004161195 +0200
@@ -184,14 +184,6 @@
                 PlasmaComponents.ContextMenu {
                     id: contextMenu
                     visualParent: contextMouseArea
-                    PlasmaComponents.MenuItem {
-                        text: i18n("Copy")
-                        onClicked: bodyText.copy()
-                    }
-                    PlasmaComponents.MenuItem {
-                        text: i18n("Select All")
-                        onClicked: bodyText.selectAll()
-                    }
                 }
                 MouseArea {
                     id: contextMouseArea
From his explanations, this patch restores completely the notifications support on KDE4, excluding the ability to select and copy to clipboard the body text from a notification popup - which I for one I believe that's a rather minor feature, anyway...

In other hand, seems like that that QML MenuItem hits again!

Last edited by LuckyCyborg; 03-24-2023 at 07:39 AM.
 
1 members found this post helpful.
Old 03-24-2023, 08:34 AM   #73
BrunoLafleur
Member
 
Registered: Apr 2020
Location: France
Distribution: Slackware
Posts: 401

Rep: Reputation: 366Reputation: 366Reputation: 366Reputation: 366
Maybe I have found a better way for widgetexplorer and notifications but I have to test. I will test this evening.
The idea is to find the real cause of the differences and not to suppress what is causing trouble in some qml files.

For opengl, yes I have separated it in a patch. On my somewhat old machines it is ok but you can work without this opengl patch which is separated from the others. Maybe I won't enable it by default in pbslacks.
 
3 members found this post helpful.
Old 03-26-2023, 08:10 PM   #74
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,500

Original Poster
Rep: Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309Reputation: 3309
So, there is the third upload of kde4town of mine, in the form of separate tarballs for complete sources and x86_64 packages.

https://easyupload.io/m/je9oel

The SHA256 checksums of tarballs are:
Code:
ac1b3bcf287ac0617c9047aa37932b6ad828919beab8915626be973cd8950d8c  kde4town-packages-20230327.tar
e7c21dcac50f39a75bc61876286d6374a4f0ee0e2ae78b0f5538f091c921887e  kde4town-source-20230327.tar
As news, was adopted many patches made meanwhile by @BrunoLafleur, the eigen2 local build proposed by @ZhaoLin1457 for building the step package and also the notifications patch made by my friend.

This packages set is a full rebuild, required also by the patch for fixing the GCC detection on Qt4 build (made by @BrunoLafleur) and are built successfully all packages traditionally shipped by the KDE4 build on Slackware.

Additionally, was added in the sources only, the alternative colibri notifications (now rather superseded by the native notifications) and smooth-tasks which I love as alternative tasks panel. They are part of a "custom" build module and should be build (and installed) with ca command like
Code:
./kde.SlackBuild custom:smooth-tasks
However, the famous QML MenuItem issue was still not fixed, yet various workaround patches was applied by @BrunoLafleur and me - the most benign one (as functionality loss) seems being the one for notifications.

Certainly, finding and fixing that QML issue is the best way, but meanwhile KDE4 interface is workable.

And while considerable improved, the NetworkManager integration still have some issues as interface logic. But, overall it works and you can manage the network connections - yet is not ready yet.

Also to be noted that on this build I applied @BrunoLafleour's kde-workspace-opengl2.patch to kde-workspace, because seems to improve well the OpenGL2 support, yet this patch removes also the OpenGL 1.4 support from KWin. So, if the intention is to use kde4town on a OpenGL 1.4 only machine, probably the best is to rebuild kde-workspace without this patch.

@BrunoLafleur

Man, please be kind to use a whatever WiFi USB dongle to test the NetworkManager integration. As you certainly known, you can delegate its usage to a VM, so you can test at your heart content how the NM integration behave.

Last edited by LuckyCyborg; 03-27-2023 at 03:32 AM.
 
2 members found this post helpful.
Old 03-26-2023, 08:33 PM   #75
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,362

Rep: Reputation: 4075Reputation: 4075Reputation: 4075Reputation: 4075Reputation: 4075Reputation: 4075Reputation: 4075Reputation: 4075Reputation: 4075Reputation: 4075Reputation: 4075
And, as usual, the French mirror:

https://matoda.pw/publik/KDE4_town/v3/
 
3 members found this post helpful.
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
KDE4 pbslacks BrunoLafleur Slackware 29 02-26-2021 07:57 AM
e.g., BSD style (Slackware) vs. SystemV style startup scripts haertig Slackware 5 01-03-2009 10:52 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:29 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration