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.
My custom "lightweight" KDE 4.10.5 desktop for Slackware 14.0 is currently being finished and polished up. I have yet to sand down some rough edges and add a few missing bits. Right now I'm creating the default user profile for the KDE desktop, e. g. the desktop's default configuration when a user is created. I'm encountering a few problems with that.
Compared to the vanilla KDE configuration, the custom user profile here includes a few sensible defaults. Here's what I got so far to make KDE4 more Joe-Sixpack-friendly (see screenshot below to get a rough idea):
Increase kicker panel height.
Replace default quickstart buttons on the kicker panel by a handful of custom ones for Firefox, Thunderbird and Open Office.
Add these same applications to Favourites in the Kickoff menu.
Add a shutdown button to the lower right side of the kicker.
Deactivate semantic desktop and file indexation (for low-spec hardware).
Change mouse cursor theme and enable double-click.
Define Firefox and Thunderbird as default web browser and mail client.
Change desktop default to "Folder View" with ~/Desktop as default folder.
Choose a neutral wallpaper.
Creating a custom profile for a desktop environment like Xfce is dead simple. All you have to do is create a template user, configure the desktop, then copy all of /home/template/.config to /etc/skel (make a package eventually), and that's it. With KDE, things are more complicated, as it seems.
Application settings are stored in ~/.kde/share/config, in a series of files. Now of course I could grab all these files and copy them over to /etc/skel. Here's a summary of the problems that arise.
Some configuration defaults in plasma-desktop-appletsrc, for example, use hardcoded geometry, like this:
This is on a PC with a 19" screen, with 1280x1024 resolution. Now if I package this profile and move it to another computer with a different (smaller or bigger) resolution, the new user's default panel will be either too wide or too small. Hmmmmm.
Some configuration details seem to hardcode the user, like here for example:
I spent the best part of a sunny summer Sunday on this, and I'm just starting to get anything near a result. Which is quite unexpected actually, because the correct way to do things is to script the default profile. See attached screenshot.
Thanks to pprkut and AlienBob on #slackbuilds for the precious help.
Hi and thanks for your work on trimming down KDE! Have you considered making a repository for it that could be used with slackpkg plus?
His repository _is_ compatible with slackpkg+ . In fact, slackpkgplus.conf already has a commented-out example of the MLES/MLED repositories, it will be easy to add MLWS as well. See https://github.com/zuno/slackpkgplus....x86_64.sample .
I did a lot of experimenting yesterday evening and this morning. So far I have a quite usable default configuration. Here's my 00-defaultLayout.js:
Code:
loadTemplate("org.kde.plasma-desktop.defaultPanel")
for (var i = 0; i < screenCount; ++i) {
var desktop = new Activity
desktop.name = i18n("Workstation")
desktop.screen = i
desktop.wallpaperPlugin = 'image'
desktop.wallpaperMode = 'SingleImage'
var wallpaper = "Ethais"
desktop.currentConfigGroup = new Array("Wallpaper", "image")
desktop.writeConfig("wallpaper", wallpaper)
desktop.writeConfig("userswallpaper", wallpaper)
//Create more panels for other screens
if (i > 0){
var panel = new Panel
panel.screen = i
panel.location = 'bottom'
panel.height = panels()[i].height = screenGeometry(0).height > 1024 ? 35 : 27
var tasks = panel.addWidget("tasks")
tasks.writeConfig("showOnlyCurrentScreen", true);
}
}
And here's the corresponding layout.js:
Code:
var panel = new Panel
if (panelIds.length == 1) {
// we are the only panel, so set the location for the user
panel.location = 'bottom'
}
panel.height = screenGeometry(panel.screen).height > 1024 ? 70 : 54
panel.addWidget("launcher")
tasks = panel.addWidget("tasks")
panel.addWidget("systemtray")
panel.addWidget("digital-clock")
panel.addWidget("lockout")
tasks.currentConfigGroup = new Array("Launchers")
tasks.writeConfig("browser", "preferred://browser, , , ")
tasks.writeConfig("filemanager", "preferred://filemanager, , , ")
What I could manage so far:
Have a bigger panel (some of the users complain about small icons)
Don't show the activity button next to the Kickoff menu
Define a more "corporate" default wallpaper (Ethais is perfect)
Add a default shutdown button on the lower right side of the panel
I did this mainly by looking at other folks' mods on the web, and trying to figure out how I can adapt them for my own needs. I'm moving in very small steps, with a lot of trial and error.
Now here's some more things I'd like to do this way (e. g. by scripting), but I don't know how to go about it, in terms of mere syntax. I'll describe them in plain english:
Add some custom launchers to the Kickoff menu ("Favoris").
Deactivate all graphical effects (for low-spec hardware).
Deactivate the semantic desktop and file indexation (for the same reason).
Change mouse cursor to Whiteglass theme
Default to double click.
Default the desktop to "Folder View" for ~/Desktop.
Define Firefox as the default web browser.
Define Thunderbird as the default mail client.
Plasma widgets are locked by default.
Kiosk mode would be even better, e. g. most things become immutable.
If you have one or more suggestions for any of the points above, I'd be grateful. For now, "I've reached the end of my latin", as we say in my native Austria.
OK, I managed to go further in my default configuration. I edited a series of small files in /etc/skel/.kde/share/config to alter KDE's default configuration.
Everything works now as expected (again, after lots of trial & error). Which means I only have one last thing to configure, and I don't know how to figure that out:
How can I have widgets default to locked? Users can unlock them afterwards eventually, though I'd like to know how I can theoretically lock everything down for good.
I'd be really grateful to know that, as it would allow to wrap this up.
Maybe you can find an answer seeing what's changing when "block" or "unblock" the widgets in this file .kde/share/config/plasma-desktop-appletsrc (the key are the immutability options from 1 to 2):
Maybe you can find an answer seeing what's changing when "block" or "unblock" the widgets in this file .kde/share/config/plasma-desktop-appletsrc (the key are the immutability options from 1 to 2):
Nah, I just found it. It's actually just a one-liner, to be put in 00-defaultLayout.js.
The KDE mailing list is actually very helpful with this.
Mon Aug 19 19:15:33 CEST 2013
microlinux-wallpapers-1.0-noarch-1_microlinux.txz: Added.
kde-wallpapers-4.10.5-i486-2_microlinux.txz: Rebuilt.
kde-base-artwork-4.10.5-i486-2_microlinux.txz: Rebuilt.
Added a dirty hack to both packages which allows a consistent background
image for the login manager, the splash screen and the main desktop.
kde-workspace-4.10.5-i486-2_microlinux.txz: Rebuilt.
Added the system-wide part of a custom Joe-Sixpack-friendly user profile.
user-settings-kde-4.10.5-noarch-1_microlinux.txz: Added.
The userspace part of our custom user profile.
+--------------------------+
Did you ever consider recoll as a desktop search tool?
Not really, but thanks for the suggestion. I doubt my average user will use Mutt and/or Emacs. They already have a hard time figuring out Thunderbird.
The file search tools shipping with KDE already work quite well, at least in version 4.10.5. Only I decided to deactivate them in the default configuration - as I did with all the graphics effects - so folks can run the whole desktop even on low-spec hardware. Of course, everything can be (re)activated on more recent PCs. BTW, I tested everything on a battered 13 year old NEC Powermate (PIV 2.4 GHz, 512 MB RAM), and it runs correctly, using 175 MB RAM with the KDE desktop started. I'm also already running it on my main workhorse PC, and I love it. Feeling is similar to driving my old Mercedes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.