SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,107
Original Poster
Rep:
"Xfce 4.14pre2 released!"
Quote:
As scheduled, the team has released the second pre-release for Xfce 4.14, which is due later this summer, yesterday evening. As this release was mostly focused on bugfixing there are not that many highlights, but as with Xfce 4.14pre1 I’ll try to point out a few – as before, not completely unbiased......
As i've probably said before, IMHO , the Whiskermenu plugin should be the default menu.
I don't particularly care about which menu is the default, since the first thing that I do when I start XFCE for the first time, is to run a script that sets up the panels to my liking. The Whisker menu, by the way, is no part of that setup, since I prefer the traditional one anyway. Guess I'm simply "old skool".
There's xfce4-panel-profiles, a new plugin that might be interesting. I'll probably package it for SBo. Re 4.14_pre3, it's in my tree (linked above) and seems pretty much ready to go from where I sit.
Would I be playing with fire if I attempted to mix your 4.14_pre3 build in with AlienBob's ktown Plasma5 on a -current multilib install? I noticed the message about breaking KDE4 related to the new upower package, which is still 0.9.23-x86_64-4 in mainline -current right now. Maybe best to just give it a whirl in a VM or a live Slack USB?
In the immortal words of Egon, "Don't cross the streams!"
Would I be playing with fire if I attempted to mix your 4.14_pre3 build in with AlienBob's ktown Plasma5 on a -current multilib install? I noticed the message about breaking KDE4 related to the new upower package, which is still 0.9.23-x86_64-4 in mainline -current right now. Maybe best to just give it a whirl in a VM or a live Slack USB?
In the immortal words of Egon, "Don't cross the streams!"
Well, I'm not sure how they would play together, but I *think* they'd be fine. I'm relatively (though not completely) sure that his Plasma stuff requires newer ConsoleKit2 and upower, as does Xfce, so you should already have those two from the Plasma stuff (i.e. maybe don't upgrade to my packages of those, but in theory, either mine or his should be fine). The only other new requirement introduced on my side is libwnck3, which almost surely doesn't overlap with Eric's Plasma stuff.
EDIT: after glancing through Eric's Plasma stuff, it looks like he's still using upower-0.9.23 in stock -current, so yeah, there's going to be a problem. I don't know which parts of Plasma/KDE actually link/use upower, but you could perhaps rebuild those parts yourself...
Last edited by rworkman; 08-01-2019 at 09:16 PM.
Reason: EDIT - upower note
It's sufficiently interesting that I went ahead and added xfce4-panel-profiles to my Xfce414 repo, but it probably won't be added to the -current tree: https://rlworkman.net/pkgs/current/ChangeLog.txt
As the title says, a Xfce thread for Slackware users.
Here we can discuss all things Xfce as they pertain to Slackware. Tips and tweaks, bugs, scripts and whatever floats your boat.
So Midori Browser... anyone have experience with it on Slackware?
I've used the SBo version and there are certain things not working right. For instance, some pages are said to be 'not reachable' even though I can open them on Firefox and Brave browser. So I was wondering if I was doing something wrong? I would love to have a lightweight browser without all the FF bloat and FF tracking nonsense. I used to love Epiphany when I used elementary OS. Midori seems like the next best thing available for Slackware users.
So Midori Browser... anyone have experience with it on Slackware?
I've used the SBo version and there are certain things not working right. For instance, some pages are said to be 'not reachable' even though I can open them on Firefox and Brave browser. So I was wondering if I was doing something wrong? I would love to have a lightweight browser without all the FF bloat and FF tracking nonsense. I used to love Epiphany when I used elementary OS. Midori seems like the next best thing available for Slackware users.
Damned, have I not already told you to just stick to Seamonkey in another thread of yours!
Seamonkey is good man, and does not contain al the crap that comes with newer firefoxes. Also the telemetry is off by default in Seamonkey. And you want it light? Well, disable javascript manually or with an addon, and it's light.
I don't have good results with midory. If you want really light, netsurf might be a better option. It's actively developed, and I think it used the fltk toolkit, which is pretty light.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.