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.
The topic is not that Steam, but that 32-bit support, the 32-bit era, is over. Absolutely.
This is very important to understand.
I have a computer with Pentium 4 540J at 3,2GHz on socket 775, 8GB DDR2 800MHz on 4 slots, the on-board graphics from motherboard supports OpenGL 2.1 .
This box is 32bit only and it runs fine Slackware -current with Plasma5. The Plasma5 has all its grafics effects active and overall behavior of this particular box is quite decent.
Also I have two Asus EEPC netbooks which are 32bit only and runs fine Slackware -current with XFCE.
Long story short, 32bit only computers are still around and they do a fine job.
Last edited by LuckyCyborg; 02-10-2021 at 12:45 PM.
I have a computer with Pentium 4 540J at 3,2GHz on socket 775, 8GB DDR2 800MHz on 4 slots, the on-board graphics from motherboard supports OpenGL 2.1 .
This box is 32bit only and it runs fine Slackware -current with Plasma5. The Plasma5 has all its grafics effects active and overall behavior of this particular box is quite decent.
Also I have two Asus EEPC netbooks which are 32bit only and runs fine Slackware -current with XFCE.
Long story short, 32bit only computers are still around and they do a fine job.
Yeah, I'm definitely not suggesting stopping development of 32bit Slackware. It still certainly has its place and there's still a lot of 32bit hardware out there that can still use a modern distro.
yeah, i'm definitely not suggesting stopping development of 32bit slackware. It still certainly has its place and there's still a lot of 32bit hardware out there that can still use a modern distro.
Yes ! Is true !
But the 32-bit era, is over. Absolutely.
There is also an integral part of industrial equipment that will certainly use 32-bit applications.
Ditto for embedded or industry embedded.
Therefore, do not be afraid to be left without 32-bit support in Slackware or somewhere else!
I mean switching the mainstream from 32-bit to 64-bit is prefer, and this applies primarily to
the increased system requirements of applications (what make programmers and ask users).
Therefore, there will definitely be and 32-bit Slackware.
I have a whole rack of old faulty and working 32-bit PCs and several DVDs and СDROMs,
that no one needs even for free. Everyone switched to 64-bit and USB flash.
32-bit start does not mean full-fledged 32-bit work yet !
The 32-bit era is over.
Thank you for right understand !
May be this ? :
......................./---> 15.0 64-bit (kde5) mainstream
....................../
. ----> 14.2 (kde4) ---> 14.3 (kde5) old 32/64-bit mainstream
Last edited by Roman Dyaba; 02-13-2021 at 03:27 AM.
Reason: text editing
Thanks and kudos to Eric and Patrick for this. I really hope that 5.4.21 will make its way in -current (5.21.0 expected next Tuesday 16 February 2021).
If a user has used the "Install from FTP/HTTP server" option, then the $REMOTE_URL and $REMOTE_ROOT variables could be combined and offered to be added as the default mirror in /etc/slackpkg/mirrors.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,647
Rep:
I'm not sure if it's a problem on my box only, but geeqie has a problem. If I open an image with geeqie from command line it works like expected without an error. If I open it from thunar geeqie opens but neither does it show anything nor does it respond to mouse clicks. Recompiling 1.6 didn't help, compiling from git changed the behaviour to normal. There is no change to /usr/share/applications/geeqie.desktop, so I guess there is some other culprit.
Anyone with the same problem?
I'm not sure if it's a problem on my box only, but geeqie has a problem. If I open an image with geeqie from command line it works like expected without an error. If I open it from thunar geeqie opens but neither does it show anything nor does it respond to mouse clicks. Recompiling 1.6 didn't help, compiling from git changed the behaviour to normal. There is no change to /usr/share/applications/geeqie.desktop, so I guess there is some other culprit.
Anyone with the same problem?
I'm having the same problem here.
Same thing happens if I try open the image in geeqie using Dolphin file-manager.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.