@tsimonq2 Why not just use the Xsetup and Xstop scripts to setup and tear down the guest user as outlined in the issue referenced in the upstream issue?

Another idea is that lshw maintains a GTK GUI that perhaps could be ported. It's pretty much all C++, too.

Doesn't our packaging module already do this? Perhaps this needs further explanation.

A quick update: 2.43.1 has been released upstream and there's a pre-build of 2.43 in proposed. It seems our fix is tagged in both so you could probably enable proposed to see if the fix is there. Oddly, I couldn't find it in the Ubuntu changelog, which is bizarre since it comes from the repo, but whatever. At the very least, coming soon.

good job!

@tsimonq2 it doesn't seem like this is resolved when https://manual.lubuntu.me/lts doesn't seem to go anywhere or rather it seems to go to https://manual.lubuntu.me/stable/lts which is obviously not valid. Perhaps this one is @teward's fault????

@apt-ghetto I am confident that despite your issue surrounding zsh, something is wrong with the way Lubuntu handles Snaps until a Snap is installed and a log out and back in is completed.

One thing that's true is that once you have the core snap installed, you can't uninstall it.

The core snap DOES resolve the problem if installed first. However, you need to logout and back in again after it's installed.

Yeah, I think working on Debian would be the next step.

Could someone fire up a VM and try installing the core snap first and then some other one and make sure it works?

@kc2bez do you mean this core snap?

In T139#2843, @gsilvapt wrote:

Considering all mentioned distros come from debian, I'd say this might be related with LXQt. Take Ubuntu as an example - it just works out of the box.

@gsilvapt Good job! So now the next question is whether or not this is actually a problem with LXQt or a problem with Lubuntu (or rather LXQt but specifically in combination to the rest of our system). To test this, it would be best to check and see what happens in Debian, since it's going to be the closest to what we have. Using Debian testing or stable would be the best bet with the LXQt desktop environment installed. Probably best to check them both.

In T139#2837, @apt-ghetto wrote:

In my installation, it does not show up.

I installed chromium as a snap 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.

Good work, @guiverc. I left some comments on this very welcome recent change, but I also emphasized that fixing those last commits pre-399 are our big priority. If we can get those fixed up, we can get them on the ISO tracker. It will be a huge improvement over what we have now. This is just additional icing on the cake (and you might even want to put it in a separate merge proposal). Thanks again!!!

LGTM

I think you mean #marketing_communications_team

@The_LoudSpeaker based on @hmollercl's comments, we should probably do three things:

Don't forget you'll need to update rMETA.

Hey @The_LoudSpeaker I happened to be looking at this file to see what our default command for launching runner was and I almost had a heart attack thinking we didn't have one. The commentary above refreshed my memory, but it seems to me that we didn't follow up on this. I was hoping to see an upstream bug report (though this one might be appropriate for Launchpad— @hmollercl may want to confirm as the reporter) for this but I didn't find any. We should also think of a reasonable workaround assuming we won't see an upstream fix anytime soon.

In case I didn't make myself clear, Lyn, I do not envision this as another thing to lump on your plate. I mean, hey, if you want to add to your TODO list, knock yourself out, but you already do so much.

Judging by recent conversations on the ubuntu-devel list, it's quite possible this will get implemented without us.

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?

No rush. Whenever works for you.

Spell default right. Also don't reference Phab objects, which won't make sense to most folks reading changelogs. Oh, and change the version string.

Have a good night and talk to you soon. Thanks again!

For what it's worth, I'm no C++ programmer myself, although I can follow the logic enough to at least try to figure out what's happening. I imagine if you've had any experience with any programming language, you probably know enough to do that.

I *might* be awake 15-17 UTC. 20 would probably be better. Of course, like I said, others are there.

It's just one of those things that having synchronous communication would be really helpful with. If you join #lubuntu-devel on Freenode, not only will I be there, but so will our whole team of developers, so we can all help together.

It most certainly stands. Do you IRC or Telegram or what?

I think it would be really great to have an indication that a development release is a development release. I'd like us to have a stock "in construction" wallpaper (this would be a great use for Lenny). For that matter, Plymouth could use the same methodology. For the text-based, we could include the actual codename and/or version. That's my 2¢.

Also an FYI I found out recently: KWin swallowed up the screensaver and includes it.

We need to file an ITP (Intent To Package) in Debian. @tsimonq2 should be able to help with this.

Thanks for the catch, @apt-ghetto. Still waiting on the README fix, @hmollercl.

Aw jeez one last thing: update the README so that the bit about dch -r "" is removed.

superceded by D57

Fix the update line as discussed on IRC to dch -r \"\" and include a bit in the changelog about that and it's good.

Ok, well, you've got until about spring of next year so you've got some time!

Thank you for bringing this up and helping us resolve it.

User error? Never heard of it 😆