Patchmanager 3.0

Rating: 
4.92
Your rating: None Average: 4.9 (25 votes)

Patchmanager 3 public beta

Make sure to unapply patches before upgrade from Patchmanager 2. Installation will fail if any patch is applied.

If you have installed prepatch, please remove it before patchmanager3 installation.

Changes between version 2 and version 3:

  • Not changing original files. Patches applied to fakeroot located at /tmp/patchmanager
  • OS update friendly. Patchmanager3 automatically detects when user start downloading an update and unapplying all patches
  • Patches can be reordered to be applied in correct order. Just drag to left and drop at required position
  • Collect information about possible conflicting patches. Visit patch info page.
  • Automatic check for updates for online catalog patches. Notificaiton will popup if new version of patch will be released
  • Patchmanager settngs are located inside Settings application as entry

Patchmanager daemon acts like proxy, filtering open calls and decide if application should open original file or fake one.

Useful environment variables:
NO_PM_PRELOAD=1 disables preload plugin from filtering calls
PM_PRELOAD_DEBUG=1 enables additional stderr output for preload plugin

Keep in mind this is beta version and should contain a lot of bugs. However it was tested for a while.

Please report all bugs to: https://talk.maemo.org/showthread.php?t=92935

You can collect patchmanager logs by running:
devel-su journalctl -al _COMM=jolla-settings + _EXE=/usr/sbin/patchmanager + _EXE=/usr/bin/patchmanager-dialog > patchmanager.log

Sources available here: https://github.com/sailfishos-patches/patchmanager/tree/patchmanager3

Translate project: https://www.transifex.com/coderus/patchmanager3

 

Big thanks jakibaki for Prepatch. This was very good idea to create such way for applying patches. You can review my plugin here: https://github.com/sailfishos-patches/patchmanager/blob/patchmanager3/sr...

See this TMO thread for more information.

Screenshots: 

Keywords:

Application versions: 
AttachmentSizeDate
File patchmanager-2.1.0-10.23.1.jolla_.armv7hl.rpm30.8 KB23/12/2016 - 16:42
File patchmanager-2.1.0-10.24.1.jolla_.i486.rpm193.97 KB23/12/2016 - 16:42
File patchmanager-2.1.1-10.25.1.jolla_.i486.rpm194.22 KB23/12/2016 - 19:48
File patchmanager-2.1.1-10.25.1.jolla_.armv7hl.rpm188.1 KB23/12/2016 - 19:48
File patchmanager-2.1.2-10.26.1.jolla_.i486.rpm194.07 KB23/12/2016 - 21:23
File patchmanager-2.1.2-10.26.1.jolla_.armv7hl.rpm188.1 KB23/12/2016 - 21:23
File patchmanager-2.1.3-10.27.1.jolla_.armv7hl.rpm192.65 KB09/01/2017 - 14:30
File patchmanager-2.1.3-10.27.1.jolla_.i486.rpm198.39 KB09/01/2017 - 14:30
File patchmanager-2.1.4-10.28.1.jolla_.armv7hl.rpm192.78 KB09/01/2017 - 14:55
File patchmanager-2.1.4-10.28.1.jolla_.i486.rpm198.59 KB09/01/2017 - 14:55
File patchmanager-2.1.5-10.29.1.jolla_.armv7hl.rpm192.65 KB09/01/2017 - 15:05
File patchmanager-2.1.5-10.29.1.jolla_.i486.rpm198.3 KB09/01/2017 - 15:05
File patchmanager-2.1.6-10.30.1.jolla_.armv7hl.rpm191.51 KB10/01/2017 - 10:16
File patchmanager-2.1.6-10.30.1.jolla_.i486.rpm197.41 KB10/01/2017 - 10:16
File patchmanager-2.2.1-10.32.1.jolla_.i486.rpm211.54 KB26/01/2017 - 17:19
File patchmanager-2.2.1-10.32.1.jolla_.armv7hl.rpm205.87 KB26/01/2017 - 17:19
File patchmanager-2.2.2-10.33.1.jolla_.i486.rpm211.86 KB27/01/2017 - 13:53
File patchmanager-2.2.2-10.33.1.jolla_.armv7hl.rpm206.08 KB27/01/2017 - 13:53
File patchmanager-2.3.0-10.38.1.jolla_.armv7hl.rpm237.59 KB01/02/2017 - 12:21
File patchmanager-2.3.0-10.38.1.jolla_.i486.rpm246.63 KB01/02/2017 - 12:21
File patchmanager-2.3.1-10.39.1.jolla_.armv7hl.rpm237.55 KB10/02/2017 - 13:17
File patchmanager-2.3.1-10.39.1.jolla_.i486.rpm246.9 KB10/02/2017 - 13:17
File patchmanager-2.3.2-10.40.1.jolla_.armv7hl.rpm234.42 KB24/07/2017 - 16:10
File patchmanager-2.3.2-10.40.1.jolla_.i486.rpm240.62 KB24/07/2017 - 16:10
File patchmanager-2.3.3-10.41.1.jolla_.i486.rpm240.99 KB28/07/2017 - 16:26
File patchmanager-2.3.3-10.41.1.jolla_.armv7hl.rpm234.42 KB28/07/2017 - 16:26
File patchmanager-3.0.58-1.126.1.jolla_.armv7hl.rpm334.41 KB22/07/2019 - 17:21
File patchmanager-3.0.58-1.126.1.jolla_.i486.rpm353.98 KB22/07/2019 - 17:21
File patchmanager-3.0.59-1.129.2.armv7hl.rpm338 KB13/08/2019 - 11:37
File patchmanager-3.0.59-1.129.2.i486.rpm349.61 KB13/08/2019 - 11:37
Changelog: 

Uploaded pm3 to main repo. Please start searching bugs in new version.

Comments

paolomi's picture

Hi, please update disable-glass-avatar for sailfish 3.1. Thanks a lot!

hsjpekka's picture

Is there a way to skip the os version check? 'Return old button style' v.0.0.1, for example, is compatible with 2.x - 3.0.3.10. So, I believe, it is compatible with 3.1.0.11 also. But, I can't install it due to the version check.

coderus's picture

It's called God mode :)

hsjpekka's picture

Thanks!

Sometimes checking the settings would give a hint.

jakecn's picture

Can you support more languages?

levone1's picture

Any help... I was using with 6 or 7 patches on Xperia X Compact, and everything fine, until one reboot, when I got 'no patches available' message in patchmanager. All patches were still installed, but not showing up in patchmanager. I tried uninstalling and reinstalling patches and patchmanager, and still the same. Systemctl showed service failed to start due to fatal signal. Journalctl put out this:
[root@Sailfish nemo]# systemctl status -l dbus-org.
SfietKonstantin.patchmanager.service
● dbus-org.SfietKonstantin.patchmanager.service - P
atchmanager service
Loaded: loaded (/lib/systemd/system/dbus-org.Sfi
etKonstantin.patchmanager.service; disabled; vendor
preset: enabled)
Active: failed (Result: start-limit) since Sun 2
018-08-05 02:46:35 EDT; 11min ago
Process: 14939 ExecStart=/usr/sbin/patchmanager -
-daemon (code=killed, signal=SEGV)
Main PID: 14939 (code=killed, signal=SEGV)

Aug 05 02:46:30 Sailfish systemd[1]: Failed to star
t Patchmanager service.
Aug 05 02:46:30 Sailfish systemd[1]: dbus-org.Sfiet
Konstantin.patchmanager.service: Unit entered faile
d state.
Aug 05 02:46:30 Sailfish systemd[1]: dbus-org.Sfiet
Konstantin.patchmanager.service: Failed with result
'signal'.
Aug 05 02:46:35 Sailfish systemd[1]: dbus-org.Sfiet
Konstantin.patchmanager.service: Service hold-off t
ime over, scheduling restart.
Aug 05 02:46:35 Sailfish systemd[1]: dbus-org.Sfiet
Konstantin.patchmanager.service: Start request repe
ated too quickly.
Aug 05 02:46:35 Sailfish systemd[1]: dbus-org.Sfiet
Konstantin.patchmanager.service: Unit entered faile
d state.
Aug 05 02:46:35 Sailfish systemd[1]: dbus-org.Sfiet
Konstantin.patchmanager.service: Failed with result
'start-limit'.

Thanks

coderus's picture
journalctl -al -n 1000 /usr/sbin/patchmanager
levone1's picture

Interesting thing now is that, even though all patches are applied, and everything working, still, whenever I open a terminal, the first thing that happens is it outputs 'ERROR: ld.so: object '/usr/lib/libpreloadpatchmanag
er.so' from /etc/ld.so.preload cannot be preloaded
(cannot open shared object file): ignored.' about a hundred times, and also one time here and there after certain commands.

levone1's picture

Thanks - output was about 3 million lines, so I started looking into options to filter, (from... To..., etc.), and send to file, etc., then I thought it might be easier to just look into wiping/repairing files, etc., so I eventually got functionality back. Working again now... I'll see if it happens again. Would be nice to know what caused it.

vpp612's picture

Hi, where can I find the "patch" that is required by ausmt (which is required by patchmanager)? Cannot make patches work for me otherwise.

coderus's picture

patch is in jolla repository

vpp612's picture

Thanks! Should have tried as the first thing! :)

Markkyboy's picture

Apologies: comment removed; bad info :(

vpp612's picture

No problem, patches work now! :)

vpp612's picture

I am not too experienced in tweaking Jolla, so I cannot say how to find "patch" on that page. Is it embedded into one of the ausmt packages? I still cannot find "patch"? Ausmt-1.3.0 is the one I am having now. At least trying to install that produced an error  "patch is needed by ausmt-...".

coderus's picture

use Storeman to install from Openrepos. And always refresh repositories before doing anything.

objectifnul's picture

https://coderus.openrepos.net/pm2 => 502 bad gateway

EDIT1 - fixed now. Some patches still displayed in red (means not compatible with current OS release I guess). 'catalogue web' in Patchmanager 2.0 unresponsive. Just wait?

EDIT2 - 'Catalogue Web' now working, some patches still appear in red.

EDIT3 - 502 error again :-(

Bocephus's picture

An update is obviously badly needed at this point. Has the project been abandoned?

jakibaki's picture

Do you have any problem with it?

The restart services function not working is a bit annoying but other then that I haven't expericened any other problems with it.

gedeon's picture

That function also doesn't work on Jolla C 2.1.2.3 .

gedeon's picture

Hi, the "restart preloaded services" function is not working in "Sailfis X" v2.1.3.5 .

Alfdererste's picture

Hi. If I install Patchmanager 2.0 on Xperia X(2.1.1.26) all Sailfish-default icons are missing. But Patchmanager itself is working fine.
If someone else runs into this, you can get it back by reinstall the theme icons..
"pkcon install sailfish-content-graphics-default-z1.75-base"

Jessica_0rchid's picture

Очень ждем обновления, Вашего замечательного приложения для версии SFOS 2.1.2.3

eriklundin's picture

The newest compatibility version available when uploading or editing a patch is 2.1.1.24, but the latest version of SFOS is 2.1.1.26 so the patch manager doesn't let me install a patch that I know will work.

eriklundin's picture

Saw that it's fixed now. Thanks!

explit's picture

Can you update also the 2.1.1.24 build for i486 please?

coderus's picture

what are you talking about?

Skillmon's picture

I can't activate Return Old Pulley Menu patch with SFOS 2.1.1.23 installed though the web catalogue lists it as compatible.

Markkyboy's picture

'Restart preloaded services' doesn't restart homescreen on Jamsanjoki, is this version of PM not ready yet for Jamsanjoki?

coderus's picture

hm, how is this possible... thanks, i'll check this tomorrow

Pages