Part one, libfm-qt was pushed through to proposed, had symbols errors, then got fixed. A new version has landed.

so, I now understando more the process we need as dependency from ubuntu update-notifier-common, that will handle the cache update, restart needed "flag" (is file/diretcory) and it has the /usr/lib/update-notifier/apt-check to check for updates, so we only need to decide where/how (pop-up/panel/notification) we will show it. Since discover doesn't works well and since in muon we cannot start directly to update, we might have to build an "update manager" which can do the upgrade and maybe force a check update.

So, I found that the best way to check silently if there are updates is to use this script:
/usr/lib/update-notifier/apt-check (/usr/lib/update-notifier/apt_check.py)
which is not installed by default but is part of update-notifier.
Good things is that already handles exception and is the one used by kingston-update-notifier
We shoudl define what to do when we they are updates available.

I think that it would be easier and less resource hungry to run a script that updates cache and check for updates, and if there are updates open discover with one of this modes:
plasma-discover --compact update
plasma-discover --compact sources
I would prefer muon over discover, but in muon you will have to manually check for updates again

This could be another option https://github.com/mhogomchungu/qt-update-notifier

Already pushed in https://bazaar.launchpad.net/~hmollercl/software-properties/software-properties/files

I reported this bug a while ago on launchpad.

I'm confused on what is needed, there are 2 pieces of software:

• update-notifier https://launchpad.net/ubuntu/+source/update-notifier
• update-manager https://launchpad.net/ubuntu/+source/update-manager

which is the one we need?

port is complete but I need testers. For testing please download it from here: https://github.com/hmollercl/swprop

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

The package is in the disco repo, so I suppose, this task can be closed?

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

ACK on cherry-picking; do you need me to do this or does someone else want the practice? :)

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

Do you think this should be SRUed? If so, could you please do le paperwork?

I thought it was part of software-properties, but is not, is update-manager https://launchpad.net/ubuntu/+source/update-manager/1:18.10.10

@wxl , yes as agreed earlier we'll have to use one of the alternatives.

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

Is it possible to move the super key shortcuts to open box as suggested? I know you suggested we consolidate all the key shortcuts in one place but it looks like that isn't going to happen without changing the standard shortcuts.

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.

maybe I could help, since I'm doing the port on the additional driver tab in https://phab.lubuntu.me/T144 this feature should be in software-properties-gtk so it could be ported to software-properties-qt

FYI: T167 is not related to this patch. You do *not* need to include T167 if you only pull environment stripping in. If you intend to pull in the C locale enforcement that prompted the security patch in T167 (from upstream's pull number 46 which introduced it) then you need T167. Otherwise, T167 is "Not An Issue" upon investigations.

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!

I have created T167
I was not sure which visibility I should set.

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

This security patch should be added too?

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.