Yeah, well, beauty is in the eye of the beholder. You’re welcome to propose something different for 19.10!
Yeah, I have a lot of hope for the future, especially given that its biggest problem (“slow”) I think will be solved entirely by having a progress indicator.
We were originally considering Falkon but had lots of problems with it and decided we need to make a change. I still think we need to revisit this, but one of the considerations was that we should supply the thing nearly everyone would want: a fully functional standard browser. Lightweight is not our only consideration.
Same argument could be made about LibreOffice. However, with both pieces of software, I found the alternatives (especially those based in Qt) to be rather unsatisfactory alternatives in terms of function.
This is a known bug and it looks like some code already exists.
There’s also the --profile option. Just make multiple profiles for each email address and you can start multiple instances of Trojitá, but each with their own profile.
Where are you seeing this? Screenshot might help.
It’s a input manager, which is useful, but not to everyone. We don’t enable it by default, just as we don’t enable Compton (compositing) by default. As for why there’s a menu entry— well, you want to have some way to turn it on if you do want it, no?
That was my perception too. I can’t give specifics now. But, PCmanfam stood out to me as containing the most useless whitespace/padding around things within it.
On a fresh install of Lubuntu 19.04 with recent upgrades in openbox session there is no wallpaper but instead last rendered windows stuck their images on the background. Here is a screenshot:
Yeah this is a known bug though not one with a clear solution. It doesn’t happen to everyone and doesn’t happen in virtual machines. It seems that having compositing (compton) will cause the screen to refresh.
As mentioned there, it is not the intention of Lubuntu to have the OpenBox session, but it’s something that necessarily comes with the OpenBox package, so we can’t remove it without affecting non-Lubuntu OpenBox users.
I like OpenBox, I wish I could use it form Lubuntu. And naked OpenBox fits Lubuntu objective of being lightweight distro too. Please, consider supporting OpenBox sessions in Lubuntu intentionally. Thank you for such a great distro.
Lubuntu 19.04: Please make nm-tray more visible, it is barely visble in the panel, it works fine but looks like being deactivated in comparison to the green circle of the charging reader, qlipper or volume control.
I cannot show you because pastebin will not accept a screenshot, only text.
Openbox, in contrast, shows a clearly visible WiFi applet (icon, symbol) in the panel.
When I log into Lubuntu 19.04 I have the choice “Lubuntu” and “LXQt Desktop”. What is the difference berween them except for the nicer icons in the panel and for the main maps with “LXQt Desktop”?
The LXQt Desktop session is basically LXQt with default values, so none of the specific Lubuntu settings. Similarly, the Openbox session is Openbox with default values.
Multiuser Login Shells: 1st User gets /bin/bash, every 2nd or more User gets /bin/sh
This is awkward in the QTerminal:
P.S.
Let others join the conversation
since wxl kind of “forced” me to reinstall 19.04 to help development - I was happy with 18.04 - I just report errors, or what I see as errors with my humble mind, to help. So, I gladly invite anybody over
The default shell needs to be specified when you add a new user else it will resort to /bin/sh
This is easy to change after the fact however. In the menu select preferences → LXQt settings → Users and Groups. You should see a dialog similar to this picture :
I migrated over from Ubuntu Xenial (w/Unity) to Lubuntu 19.04 a couple of weeks ago. Having an Ubuntu flavor that is based on LXQt is a breath of fresh air. Overall it’s been great so far. There were a few minor issues that are worth mentioning though:
The installer did not seem to play well with pre-existing partitions, and would simply quit about a tenth of the way through the install process. I worked around this by cloning my Xenial install to another drive and then re-partitioning through Calamares. Could have just been an issue with my previous layout and not a universal thing.
Qlipper failed to start sometimes after logging out and back in again. I worked around this by replacing the autostart entry for Qlipper with a short script that waits five seconds before calling it.
The gnome keyring often fails to unlock after logging out and logging back in again. I think this is an issue with sddm. I planned on migrating to passwordstore anyway (which I did using the pass import tools), but I’m sure some people prefer gnome keyring daemon, so it could be worth looking at.
GTK applications don’t pick up on font antialiasing and hinting settings for some reason. I worked around this by installing xsettingsd and adapting my preferences to the config file for that program. GTK applications now look great.
I don’t think the Spice VD Agent and Geoclue Demo applications should be set to autostart by default (nor do I think that the lubuntu-desktop metapackage should have spice-vdagent as a dependency). Regarding Spice in particular, there are many people who have no use for remote access to virtual machines, and it just seems like a niche feature that does not need to be running or installed by default.
Synaptics still has much better support for touchpad configurations than libinput (OOTB at-least). So I had to switch back to that for handling my trackpad. Works as well as it always has. This brings up a final issue, which is that a lot of the settings for both the touchpad and standard mouse do not seem to stick. This is workable for me as I have some things configured for synaptics and xinput anyway, but I assume this might cause trouble for other users.
Otherwise it’s been smooth sailing, and LXQt feels really mature at this point. I plan on sticking with Lubuntu, and hope that the upgrade process is smooth between releases. I read that Wayland support is supposed to be fully implemented by the next LTS release, and I pray that things go smoothly (and also that users who still prefer X can continue using it without issue at that point).
Kudos for the wonderful implementation of LXQt!
P.S. I forgot to mention that compton is still a great lightweight compositor, but that the comptonconf tool could reveal a few more settings to the user. While one can obviously change the config for compton manually, revealing the vsync settings would be particularly useful for those who switch between Nvidia and Intel integrated graphics, as using one of the opengl options for compton’s vsync resolves tearing issues on most Nvidia GPUs. The default configuration is solid when simply using Intel integrated graphics though, which was a nice surprise.
Could be specific to calamares but I doubt it. Do you have any errors or anything?
That’s a new one! If you remove your delay, are there any errors shown in the logs? Also you say sometimes. Do you mean it does this inconsistently?
The word here “often” (not “always”) concerns me because it says it’s inconsistent. Given this is the same behavior you’re expierincing with Qlipper, I’m wondering if there isn’t some other issue going on. Did it do this out of the box?
This is strange as my impression is that upstream has worked hard to ensure consistency of theming, but perhaps that doesn’t extend to fonts.
Could you share that config?
Say what?! I have no clue why these are there. @tsimonq2???
I’ve heard this before, but as synaptics is essentially deprecated in lieu of libinput (the author of both pieces of software are the same), it’s pointless to keep carrying the torch.
By what methodology?
You might consider reporting an upstream issue, especially given you have intimate experience with the issue.
