@kc2bez Are we affected by this?

In D60#1369, @wxl wrote:

Isn't removing the cfg file necessarily going to render this non-functional? I was thinking just removing the prerm/postinst is all that really needed to be done, no?

Could you please answer these questions?

What is the use case for the "new login" button? I mean, if a user locks the screen, the user normally wants to unlock the existing session again.

In T126#2582, @EinarMostad wrote:

D'oh! I have completely misunderstood the move to phabricator.

Yes and no. Phabricator is in some cases the best place to file bugs and reports, for example this task or T127. In other cases, Launchpad or Github are better, e.g. for T125.

I am sorry for wasting your time!

You don't waste our time! At the end, maybe it is the same developer or packager, that is working with your bug report, independently if it is written on Phab or Launchpad.

(Maybe the wiki shold mention that Phabricator is only used to track development so others can avoid the same misunderstanding.)

Maybe you are right.

First of all, thank you, that you have started writing bug reports.

Is this task resolved or is there still something to do?

@tsimonq2 I try to upload it in the next two hours.

Upstream bug report

Postponing to 20.04 because there is no new upstream release available.

The file src/boot/grub/themes/lubuntu-grub-theme/icons/lubuntu.png has dimensions of 512x512 px.

I have still duplicates on a new installed system from the latest eoan iso:

03:     Print
03:     XF86HomePage
03:     XF86MonBrightnessDown
02:     Control%2BAlt%2BB
03:     XF86Mail
03:     Control%2BAlt%2BL
03:     XF86MonBrightnessUp
03:     Meta%2BE
03:     Shift%2BControl%2BF6
03:     Shift%2BControl%2BF7
04:     Control%2BAlt%2BDelete
03:     Control%2BAlt%2BT
03:     XF86MyComputer
03:     XF86Calculator

What is the file size?

My duplicates:

05:     XF86MonBrightnessUp
02:     Control%2BAlt%2BB
05:     XF86Calculator
05:     XF86Mail
04:     Shift%2BControl%2BF6
05:     Shift%2BControl%2BF7
05:     Control%2BAlt%2BL
05:     XF86HomePage
03:     Print
05:     XF86MonBrightnessDown

After every reboot/boot, I have another entry for some shortcuts in ~/.config/lxqt/globalkeyshortcuts.conf, e.g. Print.

Fix changelog entry

Shouldn't we inform the users and explain, how to fix it? Every installation from a 18.10/19.04 ISO is still vulnerable and will remain vulnerable for the next weeks, months, years.

My testing steps:

• Fixes in automirror module

After sbuild -d eoan-amd:

See my inline comment

The default, and therefore expected, behaviour is, that the Grub menu is only shown with several installed operating systems. It would make some users angry, if they would see the Grub menu and wait 3, 5, 10 seconds until it boots. Why should there be a Grub menu, if you only have one operating system?

If there is no "platform expectation" from Ubuntu, I am in favour of always including UMASK=0077.

Opened upstream issue.

After testing a bit, I think that pkexec does not work well with Calamares.

I have no problem to make recommendations like 1 or even 2 GiB of RAM. And we can or should write these recommendations and the minimum requirements into the manual/blog/download page/forum, so that it will be hard not to find them.

In T72#1808, @hmollercl wrote:

So, less than 1Gb RAM shouldn't be an option.

I disagree. The point of minimum requirements is, that we prevent users from installing, if the machine does not fulfil the minimum requirements (e.g. on hardware with 256 MiB). The minimum requirements should be based on technical facts and not impose unnecessary limits.

The reason, why the stable lxqt-archiver build is failing is always the same:

+ uscan --download-current-version
uscan warn: In debian/watch no matching hrefs for version 0.0.96 in watch line
  https://github.com/lxqt/lxqt-archiver/releases .*/lxqt-archiver-([\d\.]+).tar.xz
Build step 'Execute shell' marked build as failure

On https://github.com/lxqt/lxqt-archiver/releases there is no lxqt-archiver-0.0.96.tar.xz to download.

Without any log files or stack traces, it is quite challenging to find out the reason. (Maybe you have to clean the logfile from access tokens and other sensitive data prior to publish them)

@Tj Thank you. I have changed the issue now.

Created upstream bug to include UMASK in initramfs.conf and not in a separate configuration.

@guiverc On our Download page, we have also magnet links. I hope it is not blocked by your government.