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.
what is estimated build time for the build? build-cinnamon.sh
I never really paid attention, but the only thing that takes forever for me on my C2D @ 2GHz is mint-y-icons. Everything else I would estimate at about an hour on this old hardware.
I never really paid attention, but the only thing that takes forever for me on my C2D @ 2GHz is mint-y-icons. Everything else I would estimate at about an hour on this old hardware.
thats not too bad, I'd be using a laptop. if I do. CPU Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz
I'm still in it btw, and I even posted on when is slack going to get up with the times in "modern' desktops. I just seen this post today.
I'm still in it btw, and I even posted on when is slack going to get up with the times in "modern' desktops. I just seen this post today.
I have went and built my own Cinnamon DE, built up from Willy's csb. I don't install KDE or XFCE and build everything with a fork of slackrepo to build "CinBuilds" instead of SlackBuilds. I still closely follow Willy's csb, and it is usually installed on another laptop that I use.
I forked slackrepo to build "CinBuilds" so there would be less possibility of someone trying to build my "CinBuilds" that are not in the base repo that I use. It's kind of like my own little SBo, but a lot of the dependencies and make options are different.
The entire "CinSlack" repo is modeled after Linux Mint packages. It turns out almost exactly like LM, except for the few packages that require apt, and I have been working on those.
You can check it out here if you like but be warned, it takes 9 hours to build on my i3 @ 3.4GHz and -j8. Mostly due to qt5 which takes 6 hours by itself. And I am going to push a bunch of updates for GNOME packages that I use later tonight.
For those of us who prefer the "old" settings with the new Cinnamon 4 menu and panel, I have mapped out how to return them how they were in Cinnamon 3.x
Quote:
Cinnamon menu
-------------
Right click on the menu button and select "Configure".
Select the menu tab and in the first entry, "Minimum height of the favorites section (px)", set it to 300.
This should bring it back down to at least close to if not what it was before.
Cinnamon panel
--------------
# Height
The height can be fixed quickly by right clicking on the panel and selecting "Panel settings". In the "Customize" section set the "Panel height" from 26 to 30.
26 seems to be about where it used to be.
# Grouped icons
Again, right click on the panel and this time turn on "Panel edit mode" and then select "Add applets to the panel".
Select the "Grouped window list" and click the "-" at the bottom of the window.
Scroll down the applet list and highlight "Window List" then click the "+". You will need to reposition it to the left side of the panel.
You will also need to re add the "Panel launchers" that used to be on the left side of the panel. In the same applet list, find "Panel launchers" and click the "+". You will need to reposition this applet to the left as well.
For those of us who prefer the "old" settings with the new Cinnamon 4 menu and panel, I have mapped out how to return them how they were in Cinnamon 3.x
Skaendo, do you mind sending me the Slackware logo for the menu icon? I can change the default Cinnamon icon with that one.
It seems to be looking by default for either /etc/pki/tls/certs/ca-bundle.crt or /etc/ssl/certs/ca-certificates.crt, neither of which are present in Slackware, as far as I can tell. The other option is just to set --without-ca-certificates, but I'm not sure what effect that would have.
It seems to be looking by default for either /etc/pki/tls/certs/ca-bundle.crt or /etc/ssl/certs/ca-certificates.crt, neither of which are present in Slackware, as far as I can tell. The other option is just to set --without-ca-certificates, but I'm not sure what effect that would have.
/etc/ssl/certs/ca-certificates.crt exists on my -current system. It was installed a day or two ago.
/etc/ssl/certs/ca-certificates.crt exists on my -current system. It was installed a day or two ago.
Can you tell me what package it's from? I don't have it on either of my -current LXC containers, and I can't find it in any of the files in /var/log/packages either, or in the MANIFEST. I take it this must be created by a doinst.sh or something.
Edit: okay, I see that to generate this file, you need to run update-ca-certificates, and that is in doinst.sh for the ca-certificates package. I'm not sure why that doesn't happen in LXC, but anyway, it's obviously not an issue with the Cinnamon build script.
Last edited by montagdude; 11-26-2018 at 02:55 PM.
Cinnamon built just fine in VBox on a clean install of current. Actually, it is the first build for the VBox install. I've only kept it up-to-date for about a few weeks or so.
Time to play. I've always been a KDE user, occasionally going out of the box.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.