If you're going to create a swap *file* then I'd strongly recommend it be the *first* thing done after the root file-system has been created - before any other files have been written to the file-system.

Isn't this as easy as adding an entry to etc/fstab ? Does this need to be done by calamares? We could create a post install script that do that.

It seems there's an upstream issue specifically about swapfiles.

This is fixed in Eoan:

This sounds like something that dm-verity would be ideal for. It is for read-only devices and uses a kernel layer to ensure the block device reads match the hashes.

Hi @hmollercl, I'll take a look at it.

palinek added a commit to solve the issue and it worked, the commit is:
https://github.com/palinek/nm-tray/commit/ecbe243339cc4a89dbaf3c37362cd0d963e0a22d
since it is over 0.4.2 and we are in 0.4.1 and in sid there is already 0.4.2-1 https://packages.debian.org/sid/nm-tray how should we proceed?

I found this python3 library if someone wants to do this in python:
https://packages.debian.org/sid/python3-networkmanager
https://pypi.org/project/python-networkmanager/
https://github.com/seveas/python-networkmanager
look at the examples
https://github.com/seveas/python-networkmanager/tree/master/examples

submitted issue upstream https://github.com/palinek/nm-tray/issues/39

Here is the link to git.

BTW here's some stuff from the previous version of this bug:

Hey! I have a first draft of the theme ready. Where should I upload it? So that you guys can also test it?

In T30#1180, @wxl wrote:

Looks like MATE no longer installs the theme by default because it's problematic with some hardware it seems. Curious.

Whoops! My bad I thought you had claimed this task @wxl Sorry for the message on telegram. I had recieved the email notif and I was in a hurry so didn't read properly. My bad. Really sorry. I will complete the task asap. Really sorry again!

Looks like MATE no longer installs the theme by default because it's problematic with some hardware it seems. Curious.

If you do decide to do graphics drivers here's the PPA Canonical works on. https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa

I think looks-wise the login screen needs a bit of an update(provided screen of 19.04 login screen). Simple changes like centering the user login and making the bar on top a darker color and 2px thinner would make the login screen a bit more complete appearance wise.

Does that mean integrating Raspberry Pi kernel fixes to the Lubuntu Pi images? https://github.com/raspberrypi/linux

Debian has the fix here:

Yes, that's what I'm referring to with the first question— how exactly one updates it. As I said above, I'm confirming one just clones, runs the update script, and commits?

Are you referring to rLUBUNTUMETAPACKAGING lubuntu-meta Packaging?

Ok, what about lubuntu-meta?

Let me talk to the SRU team and see what their thoughts are on SRUing such a patch.

I think the problem with that is that we have designed the whole system around a particular look. There's always been a set of colors (or at least a family of color tones) that we have used. We've had optional wallpapers before, but the default has always been something we designed. The nice thing about that is we can limit the amount of colors in it, which makes it blend better with the rest of the system. With photographs, this is much more difficult.

I like nature pictures, isn't there some type of license that would let us use some? Creative Commons kind.

In T21#608, @wxl wrote:

The app-defaults file will usually be  named  /usr/lib/X11/app-defaults/XScreenSaver,

Yep

Alright, I'm writing this all down in one place so I don't forget and others can rubber ducky me. Basically, we need to set Calamares up to configure some custom settings, iff the OEM GRUB entry is set. This isn't horribly complicated at all.

:P

This task remains here so that it does get added there.

Exactly. Move everything over, it doesn't belong here. :P

Spite closes things, dummy.

Put it in rNEWREL New Release Tooling :P

The sloppy way we dealt with release notes and the website indicates how important things like this are.

It better be done. Cuz it's out.

I prefer to pass on this, not much time and I don't have problematic machines anymore to test. However, apparently there is a better solution for broadcom than it was before when I had the issue packaged in bcmwl-kernel-source.
Could we seed it?
https://packages.ubuntu.com/disco/bcmwl-kernel-source
apparently this(was?) is the ubuntu solution
https://askubuntu.com/questions/626642/how-to-install-broadcom-wireless-drivers-offline/626653#626653

@hmollercl you're probably right, but I've seen cases where live works but the install doesn't. In any case, I want to know what Ubuntu proper does so we can emulate that. You have any interest in digging into that quagmire?

Why in https://phab.lubuntu.me/w/lubuntu-dev/new-code/ this appear to be C++? It could be done in Python to.

Single Sign On

What's SSO?

I understand the issue with wireless drivers (Broadcom comes into mind) but graphic cards?
I mean if there are graphic chards drivers necessarily needed (ie nouveau doesn't work) calamares wouldn't start, am I wrong?
Besides Broadcom, any other drivers you are aware of?

regarding galternatives...
https://forum.lxqt.org/t/lxqt-config-on-debian-recommends-galternatives/698/2

Looks like the golang stuff is gone. The others would be nice to remove, but we took care of the big stuff.

I would suggest we just add this to rNEWREL New Release Tooling, sort of like how the Ubuntu release checklist is.