Same experience here. The new method of building (and using) the poppler-qt4 package indeed fixes the PDF support in Okular.

Many thanks, @BrunoLafleur!

I can't speak on name of @BrunoLafleur, but I for one I believe that the priority for now is to completely fix the NetworkManager integration.

In the end, the programmers are a scarce resource in Slackware, and in this little project we have exactly one active programmer: @BrunoLafleur and sometimes is also the help of that friend of mine. Then, let's "use" this scarce resource for the most highly priority developments.

I believe that after everything works as expected, we have all time to wonder how to improve the things. After all, the KDE4 is frozen in time, and certainly it will not change in the next months.

2 members found this post helpful.

Of course there are the same problems with the Okular's support for PDF files, because nothing changed yet. In the end, @BrunoLafleur found a solution for this issue just yesterday, and no build of mine including a fix for this issue was published yet. So, I ask you for a bit of patience, you Great Wizard!

HOWEVER, I would like to note again: the purpose of this kde4town of mine is (for now) to make a KDE4 for Slackware 15.0 , which is a stable release, then is simpler to follow. Because my skills aren't on pair with Mr. Hameleers or Darth Vader. They both are also skilled C/C++ programmers capable to patch the things, while I am NOT.

On this thread you can see talked about many patches, BUT no one was made by myself. The infrastructure was made and patched by @BrunoLafleur and some other patches for Slackware 15.0 are made by a friend of mine.

In principle I am not against to having a kde4town for slackware-current, but to exists such thing, first should be a PBSLACKS supporting it. OR, other people with programming skills to join this humble project. Because as I said already and you know, the KDE4 is frozen in time, but the -current always changes. And there will be needed patches, patches, patches.

So, if you use kde4town on -current, I am afraid that for now I can't support this kind of usage. You are in your own. I for one, I doubt that KDE4 clean compiles and work on -current.

In other hand, that GAMIN package exists on Slackware 15.0 as it was removed from -current after the -stable was made, and one of big rules of this project is to NOT replace any system package.

That's WHY I wonder if it's appropriate to ship a GAMIN package, which is not useful for Slackware 15.0, but only for slackware-current, which is no supported (yet?) anyway.

3 members found this post helpful.

You are too modest.
How is our friend Darth?
I don't expect any support for running it on -current. I'm just relating the results of my fiddling, with the hope it somehow helps, just a little bit, with your, BrunoLafleur's, Monsieur Marav's and ZhaoLin1457's hard work.

Happy Easter!

2 members found this post helpful.

FWIW.
Just went to change the desktop wallpaper and found I'm locked into one
directory. There is no way to move to another directory in the search of
a different image.

2 members found this post helpful.

Just FYI.

Another minor problem.
If you have your virtual desktops setup with different images..... actually, the image doesn't matter. So, say you have four virtual workspaces set up on your main desktop and you also have
a second "activity" (second desktop) (windows button/tab button) set up with four virtual workspaces.
When you change your workspace in the second activity, it will change your workspace in your first activity (main desktop), and vice-versa. So, if on your main desktop you are using virtual workspace 1, and you switch to activity two (second desktop) and change to virtual workspace 4, when you go back to your main desktop you find the workspace has been changed to 4. It might have taken me longer to notice this if I hadn't been using different images.

Also, when I open a program via WINE and try to minimize it to the panel, it "bounces" back up. I have to close it to get it off the desktop.

Again, just FYI.

2 members found this post helpful.

Many thanks for the bugs reported, Great Wizard!

However, would be very useful if those bugs would be double checked against that Slackware -current of yours with last KDE4, and also they to be confirmed on kde4town installed in Slackware 15.0.

The idea is to not introduce new bugs like was that now famous QML problem, then would be very important to know if those bugs are "new" or they are already present on KDE4, because I am afraid that "fixing" all the bugs already present on KDE4 is a long shoot - and maybe they would be solved by @BrunoLafleur in a long term, if he ever has this purpose.

And I apologize to everyone for my eventual delayed responses, but unfortunately I got some very busy times at job.

1 members found this post helpful.

I can tell you, without a doubt, that the "original" kde4 did not have those bugs, that is, to say, in kde4 the WINE program could be minimized to the panel and changing workspaces in one activity did not change workspaces in another activity.

2 members found this post helpful.

When I start to think all this work might be more trouble than it is worth, I remember how much I loathe kde5.
I've tried -current and the latest version of Xfce, but it locks up or spontaneously reboots on a regular basis, as in every few hours. Sometimes within an hour or two of starting the system. Kde5 takes almost 3 days before it does something similar.
OTOH, Kde4 doesn't lock up. I've let the system run 24 hours a day for longer than a week
without any problems.
My biggest problem is self-inflicted. I'll get that December 2000 version of -current installed and running well, but can't resist fiddling with this or that to the point I finally "break" something and have to start over from scratch.
I should find another hobby or go back to work to keep myself busy..

2 members found this post helpful.

Kde4 on -current crashed (froze), so I rebooted and changed to Xfce-4.18, where the same problem exists (as quoted above).
Perhaps, it is a WINE bug?
Think I'll re-install the December 2000, -current and see what happens.
This will take a while.

2 members found this post helpful.

Does the same thing in a fresh installation of -current and using kde5.
I'll see if I can find a older version of WINE and try it again.

2 members found this post helpful.

The problem was the same with wine-8.4 and 8.5, so I dug around and found a old
copy of wine-5.18-x86_64. After removing wine-8.5 and installing wine-5.18, the
program can be minimized to the panel. I only use one program that needs wine
and it is working great with 5.18, so I'll leave it that way.

2 members found this post helpful.

Great Wizard, I will look for those issues said by you when I will return home, probably in the next Weekend - now I am in a job trip. I have with me my old pal Dell Inspiron N5030, but it's a bit spartan as storage space, even if in the evenings I have some spare time.

Heck, I was reluctant since long time to replace its DVD unit with a hard drive adapter and to put a second hard drive, but I started to contemplate more and more this idea. This second hard drive could permit me to do some experiments, even when I am on trips.

2 members found this post helpful.

I have corrected some bugs in libnm-qt but it remains one with my tests. I expect to find it later.

https://github.com/BrunoLafleur/pbsl...t-1.0.4.tar.xz

in place of the previous one.

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

with :
https://github.com/BrunoLafleur/pbsl...atch/plasma-nm

For poppler I will see for patching with security bugs only.

3 members found this post helpful.

Many thanks!

I was wondering, are you, guys, going to do all this hard work again when 15.1 is released?
And so on ...