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,124
Original Poster
Rep:
Quote:
Originally Posted by notKlaatu
I just build it. Appears to work as expected. I've only spent 10 minutes in it, but so far so good. I'd understood it sat atop Fluxbox, so I'm surprised that it isn't picking up my flux theme, but maybe I'm just confused. Either way, it does work; it's fast but full of Qt goodness. I kinda like it....
Oh, for the record, this was built on top of a custom compile of Qt5, using Ryan McQuen's SlackBuild.
I just changed 0.9.1 to 1.0.0 in Ryan's SlackBuild and built (with sport, not that that makes a difference) using -j12. No problems.
Is anyone else testing this on a laptop and having the problem of power management not working at all? There is a battery icon on the panel, but it shows a red 'X' and is inactive. My key combinations for adjusting the screen brightness don't work either; I have to use xbacklight from the command line. I'm guessing it's a configuration/build issue, but I'm not sure how to check since it uses qmake and there's no config.log.
I'm not sure if I just missed it in the README the first time or if it was added since the SlackBuild was updated, but for power management, you need to have the acpi package installed. I still can't change the brightness with the keyboard, but the battery icon shows the current status now anyway.
Quote:
Originally Posted by Toutatis
I have tired it, but I find no way to change localization (only the default one). The same for windowmaker. Of course it could be possible to use the old "xmodmap"
There are localization options in the Preferences menu. Go to Preferences -> Configure Desktop -> User Settings -> Localization Options. I only have the "System Default" setting available though, but maybe if you have others installed, they would show up there.
There are localization options in the Preferences menu. Go to Preferences -> Configure Desktop -> User Settings -> Localization Options. I only have the "System Default" setting available though, but maybe if you have others installed, they would show up there.
This is my problem, I have only "System Default". But in KDE I have a long list instead
I've found that at least for the time being I've had to go back to 0.91 from the 1.0 slackbuild version (Slack 14.2 64). Lumina 0.91 has worked perfectly for me since it was issued, but 1.0 gives me mouse pointer and wm headaches. No window frames or window buttons on any windows, in terminal windows no text can be entered, and I get the hourglass pointer at all times in the desktop.
If, however, I run fluxbox directly from startx and then run lumina-desktop from a terminal window in fluxbox, then lumina-1.0 runs normally. Lumina will not start from fluxbox's startup file.
Reverting to 0.91, 0.91 runs normally. Same xinitrc in use for both versions, with "/usr/bin/lumina-desktop" used to start the environment in place of non-functional "exec Lumina-DE" in the "#start the window manager" stanza of the xinitrc
Peculiar. But I like lumina 0.91 a lot, so I'll try 1.0 again when I have more time to fool around with the xinitrc and diagnose my wm issues.
I've found that at least for the time being I've had to go back to 0.91 from the 1.0 slackbuild version (Slack 14.2 64). Lumina 0.91 has worked perfectly for me since it was issued, but 1.0 gives me mouse pointer and wm headaches. No window frames or window buttons on any windows, in terminal windows no text can be entered, and I get the hourglass pointer at all times in the desktop.
If, however, I run fluxbox directly from startx and then run lumina-desktop from a terminal window in fluxbox, then lumina-1.0 runs normally. Lumina will not start from fluxbox's startup file.
Reverting to 0.91, 0.91 runs normally. Same xinitrc in use for both versions, with "/usr/bin/lumina-desktop" used to start the environment in place of non-functional "exec Lumina-DE" in the "#start the window manager" stanza of the xinitrc
Peculiar. But I like lumina 0.91 a lot, so I'll try 1.0 again when I have more time to fool around with the xinitrc and diagnose my wm issues.
Did you see my post #11? Changing Lumina-DE to start-lumina-desktop did the trick for me.
Originally Posted by montagdude.
Did you see my post #11? Changing Lumina-DE to start-lumina-desktop did the trick for me.
Saw it. Doesn't work for me on my Lenovo laptop: X crashes back to a console, both in 0.91 and in 1.0. Which is why I've used "lumina-desktop" as the executable in the xinitrc. Works fine for 0.91, but there's wm and pointer mischief in 1.0.
This is my problem, I have only "System Default". But in KDE I have a long list instead
You are missing the 'locales' for Lumina. Download the source, create a dir named 'i18n' on your lumina shared path (mine is /usr/share/lumina-desktop/i18n/). Extract the file 'lumina-i18n-1.0.0-Release.tar.gz', go to the 'dist/' folder and you'll find a file named 'lumina-i18n.txz'. Extract the content (*.qm) to your '.../lumina-desktop/i18n/'.
Please note that this does not change your keyboard layout! If you need something to switch keyboard layout/languages on the fly, please install the "ibus" utility. That is a little tray application which is specifically designed for this type of use, and can be automatically started on login quite easily. I have also tested ibus on Lumina (FreeBSD) and it works very well as long as you install the desired language support packs you need (usually the separate packs are for non-english character support, such as traditional japanese/chinese characters).
I am use next method in Lumina 0.8.8 FreeBSD 10.3-BETA1. Create text file: for example "key" in user home directory and edit them: setxkbmap "us,ru" -option "grp:alt_shift_toggle,grp_led:scroll" then chmod +x ./key
After Lumina starts type in terminal: ./key after that you can change EN and RU by ALT_SHIFT.
Saw it. Doesn't work for me on my Lenovo laptop: X crashes back to a console, both in 0.91 and in 1.0. Which is why I've used "lumina-desktop" as the executable in the xinitrc. Works fine for 0.91, but there's wm and pointer mischief in 1.0.
I could be remembering wrong, but I think that happened to me the first time I tried it after making the change, but then subsequent times it worked. Anyway, I did send an email to the SBo mailing list and the maintainer of the lumina package about the fact that there is no Lumina-DE executable as referenced in the xinitrc script, with my proposed fix, so hopefully we will get a confirmed fix soon.
I managed to get brightness controls working with keys. Here is the relevant part of ~/.config/lumina-desktop/fluxbox-keys:
Code:
#Lumina Specific defaults
Print :Exec lumina-screenshot
Control Mod1 L :Exec xscreensaver-command -lock
Mod1 space :Exec lumina-search
F12 :Exec lumina-terminal -toggle
Mod1 F1 :Exec lumina-desktop --show-start
Control F1 :Workspace 1
Mod4 F1 :SendToWorkspace 1
Mod1 Prior :Exec lumina-open -volumeup
Mod1 Next :Exec lumina-open -volumedown
Mod1 Home :Exec lumina-open -brightnessup
Mod1 End :Exec lumina-open -brightnessdown
Control Mod1 Prior :Exec xbacklight -inc 10
Control Mod1 Next :Exec xbacklight -dec 10
The lumina-open -brightnessup and -brightnessdown didn't work for me, but xbacklight does. These could be added through the "Advanced Editor" in the Keyboard Shortcuts dialog, or editing the file directly (but I always log out and do that from the console). This is getting downright usable. It makes a nice lightweight alternative to KDE once you get it configured properly.
Slackware 14.1 x64 w/multilib. Was able to build the slackbuild.org 1.0 version when in root, but only on a clean install, not as an upgrade from the slackbuild 14.1 version (currently 0.8.6). I like the interface, but was surprised that when looking at htop total memory used is actually the same amount as KDE with the whistles and bells turned off. Additionally, it was missing any volume-icon control and when I added it to lumina it caused it to show-up twice in KDE restarts. So more playing around is needed. But it looks nice!
I like the interface, but was surprised that when looking at htop total memory used is actually the same amount as KDE with the whistles and bells turned off.
Just curious, but how much memory does it use? On my laptop (Slackware 64 14.2), it's 170 MB after boot, but it was already 66 MB before running startx. Of course, then I go fire up kmail which starts akonadi, at which point I don't think I'm really saving much compared to KDE.
Just a random note, but I installed plank, and it seemed like it was working well, but then I realized it was causing some weird issues with the WM. Specifically, it became nearly impossible or actually impossible to resize windows for certain applications (qupzilla and kmail as far as I found out). Other applications were fine, though. I'm guessing the same would happen on fluxbux. Like I said, just a random note, but maybe it will keep someone from pulling their hair out trying to find out what's causing it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Nicely done!
It makes a nice lightweight alternative to KDE once you get it configured properly.
