Don't close until we've tested it and confirm. @hmollercl could you take care of that?

Heeeeey so in dev versions of Neon they're using Calamares. We should check to see if it works there and if so steal their config!!!

See T112 for what we need to deal with translations and such.

Great work!

Very small request: you'll want to be targetting disco and not UNRELEASED. You can make that change to your repo and arc diff again and it should fix it here.

This appears to be done at least in that the SRU is all fixed.

One other thing: having a general task to discuss a bunch of wishlist tasks is bound to be a rather long, lengthy, and confusing conversation because of too many subjects being dealt with at one time. Just like it's a bad idea to send in a bug report for a bunch of different bugs, it's bad to have a task for a bunch of different tasks. That said, I'm going to close this. If you have a specific item, make a new task for that.

To be fair, those rules are covered by the Ubuntu Code of Conduct, which governs all of our actions within Lubuntu. It also gets to the point that as Lubuntu we are Ubuntu and as such we will not be doing anything which deviates from the base of Ubuntu.¹ That said, we will not be even considering the idea of a rolling distro until you can convince Ubuntu of it. I should add it's been brought up more than once and shot down vehemently, so I think your likelihood of success there is extremely small.

I think it's a great opportunity for someone new to figure it out, especially considering how low priority it is.

I don't think many people would want to create a desktop entry for a terminal program. Some will, sure. Not many.

@Steedalion we could do that, but then we wouldn't be able to use the Super key to open the menu. That, to me, seems like something we really want.

Upstream bug has been closed as won't fix, basically on the notion that Openbox isn't a requirement of LXQt. That said, we workaround this one.

Looks like the last remaining thing was solved in rSEEDc8729c3a3541.

@tsimonq2 that seems to have been in cosmic-updates since the 5th. Did you already create the SRU?

This is in cosmic-updates, so calling it done.

Done.

I have finally bothered to confirm the fix in Cosmic. @tsimonq2 can you get the SRU finished and the fix moved out of proposed?

Well, this sucks. Previous to Discover, Kubuntu was using update-notifier-kde with Muon, but that hasn't been updated in a long, long time. Now they don't use any of the update-notifier codebase and all the notifications are hidden within the stupid plasmoid widget.

Public visibility is fine and yes, it should be that simple so have at it!

@apt-ghetto um, yes. please make a separate subtask of T117 with an "Unbreak Now!" priority.

18.10 release notes are now updated (rBLOG4691b5d032a9).

Also here's ones not involving the Super key we should just move out of Openbox based on the notion of using the Openbox configuration only for Openbox thing:

Well we don't really have an official Facebook. We have had it, but none of us really want to maintain it, so we don't consider it an official resource. I don't even have a Facebook account. That said, perhaps we could push it through the mailing list/other forms of social media. The socialite amongst us is @tsimonq2 so I'll leave that in his hands.

@Steedalion unfortunately there are options that lxqt-globalkeys provides that Openbox simply cannot accomplish. Plus, it theoretically can be used as the place to look for most shortcuts. Application specific shortcuts (such as window manager ones) would be in those applications. Not to mention the fact that it's easy to graphically edit shortcuts in lxqt-globalkeys but it is simply not possible in Openbox. Openbox requires manually editing an XML file, knowing all of its particular quirks (such as the name of the actions and the ways to depict certain keys) and manually forcing Openbox to reconfigure. That's a lot to ask if what we're trying to produce is something usable and intuitive. I'd like to use it less and less because of that. And then there's the fact that should someone (myself included) choose to use a different window manager, non-window manager shortcuts are not removed.

Absolutely weird finding: it seems that Control + F10 and Control + F11 want to run xbacklight for some reason but they're not even defined and xbacklight isn't installed. Interestingly no such problems with the ones that control the brightness. Why????

@Steedalion oh, I'm sorry, I'm wrong. We can set lxqt-runner to anything. I like Super + R and have my machines set up this way.

BTW here's what we have in lxqt-globalkeys:

@Steedalion see T141: Native nm-tray connection editor

1. We wanted to use the Windows/Super key for the menu because it mimics Windows and just makes sense. We could do something different, but there was a general feeling that this just made sense. That said, do you have a non-Windows/Super key suggestion for the runner? I think Alt + R would be nice, personally.
   1. The idea is good but the suggested hotkeys won't work if we keep the Windows/Super key for the menu as I'm suggesting above since this requires Openbox commands. If you make a suggestion that does not use the Windows/Super key, I'll be happy to implement it.

Pro tip: most are HTTP redirects. And they don't do HTTPS. I use http://http.rip to get the captive portals up reliably.

There's no consistency among captive portals, so automatic sign ins won't really be a thing. Even the methodology used (HTTP redirect, DNS, etc.) varies.

A cop out? Even KWin doesn't really handle tiling. There's a script out there to make it work but reading some discussion on it, it's not foolproof. The Lubuntu "solution" wasn't really ideal, either (and was not an Openbox one, but one we developed) and is probably best described a window arrangement hack that vaguely resembled tiling. We should support the things we know we can support and that work well. That's not one of them.

Before, I think we were willing to sacrifice too much to keep the very idea of lightweight going on (whether or not it actually was lightweight) and I think we focused far too much on saving disk space, especially on the initial image which I think is an absolute waste of time. It's more important to make sure that we can edit network connections or deal with touchpad settings graphically than it is to make sure we take up the smallest amount of space. This is analogous to the business that, in an attempt to maximize profits, alienates customers through excess fees. That certainly doesn't sound good and it wasn't good for most of our users.

lxqt-sudo (and symlinks lxsu, lxsudo) is a graphical QT frontend for plain sudo(8) or

su(1) (for requesting optional password in GUI fashion).
When invoked it simply spawns child  sudo  or  su  process  with  requested  command  (and
optional arguments).

The whole lightweight thing is a precarious thing.

@teward has server access. Didn't give him a WP account because he probably doesn't need one. @tsimonq2 I'll let you do what you want with that development page but maybe it should provide links to how to contribute and connect?

@SBanya

Well, hey, Discover does the trick and even takes care of depends which GDebi was sometimes not cool about. Nevermind.

Solution for the 404 problem: make a generic "in development page." Then we can just use nginx to redirect to that page until release time.

Actually, I'm wrong about the past. We didn't use functional names. No one knows what a Gnumeric is!

It's hit the primetime. Smarmyness still applies.

Actually, looking above, it seems like we've got nearly everything covered. Window tiling? Get a tiling window manager!

It seems that in combinations, lxqt-globalkeys makes no distinction between right and left Super keys and instead refers to them all as Meta.

We could delete these

Further inspiration:

Until this is documented in the release notes for 18.10 and the requirements not made so strict (or perhaps not be there at all) for 19.04, this is not resolved.