antiX / MX LinuxThis forum is for the discussion of antiX and MX 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.
I don't think this was a distro version problem because the previous release that I was using used slim, not slimski. And I didn't upgrade it in situ because the advice was not to. I installed the new version from scratch. But something must have got out of step in the repos because a newly reinstalled package shouldn't include a theme that doesn't exist any more.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by hazel
That's why I put it in this forum. I know Anticapitalista visits here regularly and he's helped me out before.
This is what happens with very tightly integrated systems and it increases my appreciation of Slackware's looser coupling. In Slack, I don't even bother with a display manager; I just use startx and it works perfectly well.
Yes, anti is a good example of an approachable dev.. Also, agree with appreciating Slackware's looser coupling. Although, antiX is the only distro where I could possibly tolerate Debian.
And now once more it doesn't work!! There was a mammoth update last week and I think slimski was included. Now it fails at startup again. This time, editing the login manager didn't work. It's already set to Default.
So I looked at a couple of actual theme files in /usr/share/slimski/themes/Default (en_GB and en_US), and I noticed something very odd. The files are empty except for a comment line. What's going on?
I did not know you had a slimski screwup again. I don't even have a default folder and my fully updated current antiX
64 bit full iso install my chromebook. Here is my readout below
Code:
harry@antix1:~
$ cd /usr/share/slimski/themes/Default
bash: cd: /usr/share/slimski/themes/Default: No such file or directory
harry@antix1:~
$ cd /usr/share/slimski/themes
harry@antix1:/usr/share/slimski/themes
$ ls
antiX ax BlueLinesLight default PrettyPink SunnyDay
antiXIce BlueLines DarkCity flat Space
harry@antix1:/usr/share/slimski/themes
$
It cured itself! More updates and now the damn thing works again without doctoring it. But that machine is really at the end of its life. It's too low-spec even for the sort of thing I use computers for, and the VIA Chrome graphics aren't compatible with any modern kernel, so I can't update it to 23. Instead, I installed 23 on bigboy, on the new SSD alongside Slackware, and now I use that. I'm thinking of eventually using littleboy as an rsync server for bigboy.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.