Oh my, at least I'm consistent. Thanks for letting me know, fixed in 6.0.3. And you can also make fun of me for the regression I left in 6.0.0 (see changelog). I had to laugh when I ran into that.

Oh my, at least I'm consistent. Thanks for letting me know, fixed in 6.0.3. And you can also make fun of me for the regression I left in 6.0.0 (see changelog). I had to laugh when I ran into that.
Mistakes happen to the best of us. We're all human.... That's why a "semi-frozen" PPA comes in handy.
Has the fix been released yet? Launchpad seems to suggest so. But I did a sudo apt-get update && sudo apt-get dist-upgrade in the Ubuntu VM, and mintupdate still fails to launch...
Still waiting on launchpad to publish it. You can check the PPA's page on launchpad for the status, the gears need to turn into a green checkmark:
By design you cannot open a stand-alone Kernel Manager while Update Manager is running, it will always launch the integrated version. In a situation where Update Manager does not let you open the integrated Kernel Manager neither will the menu entry. This is also by design.
Right you are. Sleep well.
Glad you like it, but no, it's no fork of 19.3, just of a few tools (which were forked pre-19.2, although I copied some 19.3 components into it which I did not fork). I cannot take credit for Linux Mint running better on your computer with it - the PPA does tweak some system settings but nothing performance-related. So whatever makes it run better now was likely an unrelated updated.oldgranola wrote: ⤴Mon Dec 02, 2019 12:21 amSo If I've fully installed this PPA and updated, which I have and like, am I essentially running a fork of LM19.3? It beats the crap out of LM19.2 which wouldn't really run on three of my amd based computers. Thanks!
Ah, I see, that must be because my version does not need a password prompt but I suppose whatever tray icon you've got there to open it is opening it with pkexec because Mint's version needs that. Will fix, thanks for the report!t42 wrote: ⤴Mon Dec 02, 2019 6:18 amPls check this situation: in case a system message in a system tray appears about need to check videodrivers with button 'start driver manager', 1) pressing the button, 2) entering a password promt and 3) waiting for drivermanager which never arrive. So I can start it from Menu anyway.
It's probably nothing I can do about, just your system slowing down due to high number of connections and/or file system access, but if you want to look into it more try running anDrugwash wrote: ⤴Mon Dec 02, 2019 8:01 amJust to make sure it wasn't a one-time thing I triggered a refresh through tray menu and once again browser froze scrolling, panel refused to unhide (or just appeared partly).
Not a big deal considering checks are pretty rare but still thought should be reported.
apt update
or refresh Update Manager via the toolbar button instead of the tray menu (while running your P2P) and see if it's any different.Code: Select all
mintupdate (1:6.0.5~gm10) bionic; urgency=medium IMPORTANT: 1:6.0.0~gm10 cannot self-update due to an oversight. tray menu no longer gets disabled during refreshes and installations. * Refactor threading in the entire application, eliminate all instances of using the deprecated GDK locking mechanism and fix some threading issues along the way * CLI commands: * Add bash completion support * Add `show-kernels`, `show-history`, `show-log` commands * Packaging: Split into four binary packages so different components like `kernel-manager` or `mint-release-upgrade` can be installed separately. * Drop unused and deprecated mintupdate-tool binary * Update translations and manual pages * Other small fixes and optimizations ......................
Code: Select all
2019-12-02 12:27 + Performing initial refresh 2019-12-02 12:27 + Starting refresh (retrieving lists of updates from remote servers) 2019-12-02 12:27 + Found 1 software updates 2019-12-02 12:27 + Refresh finished 2019-12-02 12:28 + Recurring refresh will happen in 0 day(s), 19 hour(s) and 58 minute(s) 2019-12-02 12:29 + Install requested by user 2019-12-02 12:29 + Will install kernel-manager 2019-12-02 12:29 + Will install mintupdate-common 2019-12-02 12:29 + Will install mintupdate 2019-12-02 12:29 + Will install mint-release-upgrade 2019-12-02 12:29 + Launching Synaptic 2019-12-02 12:29 + Return code: 1 2019-12-02 12:29 + Install failed
/me points to the changelog you quotedgittiest personITW wrote: ⤴Mon Dec 02, 2019 8:27 amCode: Select all
mintupdate (1:6.0.5~gm10) bionic; urgency=medium IMPORTANT: 1:6.0.0~gm10 cannot self-update due to an oversight. To upgrade from that version please copy & paste this into a terminal window and run it: mintupdate exit && sudo apt-get install -y mintupdate Sorry about that!
Considering I was the one who broke it maybe we should form a self-help group.gittiest personITW wrote: ⤴Mon Dec 02, 2019 8:56 amMy only defences are that I got back very late last night and I'm an idiot.
Are they mitigating?
Incidentally, at the time there were only three items active: one waiting for peers and two downloading, each from a single peer. So even though the bandwidth was half used, the number of connections was very low (maybe half-connections was higher). May I point out again that this didn't happen before with old version of the tools, not even when there was a much higher number of active items and connections in the P2P application. Not to mention there used to be a second external drive before, used by the P2P application, and the USB modem used to be connected through an external hub which limited its max speed, whereas now it's connected directly to one of the notebook's ports. Thereotically everything should work better. That's precisely why it struck me as odd.
Tried both but at the moment there's only one download with ~5kB/s and there was no freeze/lag.
Speed wasn't maxed out during update check. Concurrent downloads could be the issue, if the P2P application somehow bottlenecks the connection even with a minimal number of active items and peers.
Or even unless you can keep reproducing this. There was no recent update to apt. Maybe you changed to the 5.3 kernel and are experiencing the same issues as I do with it.