Bah. Just when I had packaged the "p1" release and wanted to test it :-)

By the way, I intend to create a new version of Plasma5 Live ISO which will have both Lumina and LXQT included so you can play with them. Why not, they are all Qt5 based.

8 members found this post helpful.

Woo Hoo !

Thanks Alien Bob !

Can't wait TYVM!!!

http://www.slackware.com/~alien/slackbuilds/lumina/


Many thanks!

I've been using pytyle with lumina, and it just randomly stopped working reliably. All I can think of that might have changed anything are the few updates to multilib that I installed today, but I really don't think that's it. The issue is that the command to tile the current screen doesn't work anymore if there is just one window, and Alt+z (to cycle the tiling method) doesn't work correctly either, no matter how many windows are open. I tried it in fluxbox too, since that's lumina's WM, and the behavior is the same. It works fine with other WMs/DEs, though. I've tried reinstalling it and clearing all the config files for pytyle and fluxbox, but to no avail. I also tried changing the hot keys, but no luck. Rather frustrating, because I was really growing to like both lumina and pytyle...

1 members found this post helpful.

Well, I didn't figure out why pytyle stopped working, but I did find a native fluxbox way to do the basic tiling functions I need. Add this to ~/.config/lumina-desktop/fluxbox-keys:

These will let you manually tile a window to different halves of the screen with Super + {Left, Right, Up, Down}. The only thing this is missing is a way to "un-tile" back to the original dimensions and size, but that's not such a big deal to me. Interestingly, I also tried to use fluxbox's ArrangeWindows commands, but it creates nonsense in Lumina because apparently Lumina's desktop background and panels are considered by fluxbox to be windows, so they get tiled too.

1 members found this post helpful.

Hi,

Is anybody perservering with Lumina? I installed it last night and gave it a whirl.

There were a few things missing for me
Can I autostart nm-applet (manually worked ok)
the system-tray did not appear, even though it was reported as added to the panel
There was no configurable shortcut key to open the menu.

I guess I might get told to read the docs, but does anybody have an "improvements" they cant live without on it. I am a long time XFCE user, but thought I would give this new DE a try.

Thanks

1 members found this post helpful.

1) Did you try making a .desktop file in ~/.config/autostart for nm-applet? You can use the startup applications wizard in Lumina's desktop settings, but you might have to edit the Exec= line yourself afterwards. As I recall, the dialog might try to use lumina-run (can't remember if that's the exact name) to run programs when you create autostart entries with this wizard. Just change that line to Exec=nm-applet or Exec=/usr/bin/nm-applet.

2) For the system tray, it only shows applications that are using it.

3) In ~/.config/lumina-desktop/fluxbox-keys, there should be a command called lumina-desktop --show-start. I believe that's the one you are looking for. Just change the keyboard shortcut to the one you want.

1 members found this post helpful.

Thanks for the tips, I don't know why I missed the start up config, was pretty late when I installed!

Mm applet start and work well once the exec line was used, ok so next is the gtk apps which look appalling!!

1 members found this post helpful.

You probably just have an ugly default theme. There's a tool available from SBo called lxappearance that you could use to change it (but you might need to install more themes first). Another option is kde-gtk-config, also from SBo, but I think you need to log into KDE to use it.

1 members found this post helpful.

Lumina worked well on FreeBSD & PCBSD, however, whenever I built it for Slack it would spike CPU to 100%. This happened on Slackware 14.1-64 and Salix 14.1-64. Wasn't able to figure out why as all the depends were built in order etc... It is a nice layer ontop of good ol fluxbox. Although, flux is perfect just the way it is.

1 members found this post helpful.

I had the same problem with an earlier version of Lumina, but the most recent release works fine.

This is good news. Will have to check it out again.

1 members found this post helpful.

Sorry for resurrecting a thread that hasn't had traffic for over a month, but I did exactly that and, after restarting the Lumina DE the drop-down lists for localization settings are populated with long lists of countries and languages to choose from, quite like I know it from KDE. Also, when I select on the entries, the value is accepted with no error message, and after logging out and in to Lumina, the values are remembered by the config tool.

However, whatever I choose, the settings seem to have no effect. They are stored, but then ignored. Although the translation for "Deutsch" (German) is said to be 99% complete, all I get is US English, which is the system default.

If it is not a bug of Lumina, I have learned the hard way that 90%+ of all problems with *nix are related to inappropriate user rights or file modes and file ownership settings. So, my question is: is -rw-r--r-- correct for the .qm files? Or do they need to be executable, in order to make the localization options take effect?

Thanks!

gargamel