Thank you all for testing, but it is a problem, that is not really related to LXQt or Lubuntu. Meanwhile I have found out, why it does not show up in my installations of Lubuntu 19.10 and Lubuntu 20.04, on different hardware.

In T139#2836, @wxl wrote:

I installed chromium as a snap in 19.10 and 20.04 and it did not initially show up in the menu, but did after I logged out and back in again. This is probably a problem with snaps.

In my installation, it does not show up.

However, I'm confused about the mention of the "panel" here?

I did not find a better name. In which package is the application menu?

On Lubuntu 20.04

@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.