Patchmanager 3.0

Rating: 
4.933335
Your rating: None Average: 4.9 (30 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.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.62-1.136.1.jolla_.i486.rpm357.76 KB10/11/2019 - 21:19
File patchmanager-3.0.62-1.136.1.jolla_.armv7hl.rpm346.03 KB10/11/2019 - 21:19
File patchmanager-3.0.63-1.137.1.jolla_.armv7hl.rpm345.99 KB11/11/2019 - 16:38
File patchmanager-3.0.63-1.137.1.jolla_.i486.rpm357.62 KB11/11/2019 - 16:38
Changelog: 

3.0.63
Fixed check for updates scheduler

3.0.62
Removed freeze when opening patch info

3.0.61
Watching jolla-settings process for qml errors and automatically disable all patches
Fetched translations

Comments

danfin's picture

I found the problem that the google login page which appears after accepting google credentials did not show up. It remained black I could not log in. After disabling all patches and disabling patchmanager auto load i could login as that page was visible again.

coderus's picture

You should check which patch causes problem and report it to patch maintainer

deloptes's picture

Xperia X 3.2.0.12 Failed to start Patchmanager check for updates service.

    Nov 11 10:28:16 Sailfish systemd[1]: Starting Patchmanager check for updates service...
    Nov 11 10:28:16 Sailfish systemd[4524]: checkForUpdates-org.SfietKonstantin.patchmanager.service: Failed at step     EXEC spawning /bin/dbus-send: No such file or directory
    Nov 11 10:28:16 Sailfish systemd[1]: checkForUpdates-org.SfietKonstantin.patchmanager.service: Main process exited, code=exited, status=203/EXEC
    Nov 11 10:28:16 Sailfish systemd[1]: Failed to start Patchmanager check for updates service.
    Nov 11 10:28:16 Sailfish systemd[1]: checkForUpdates-org.SfietKonstantin.patchmanager.service: Unit entered failed state.
    Nov 11 10:28:16 Sailfish systemd[1]: checkForUpdates-org.SfietKonstantin.patchmanager.service: Failed with result 'exit-code'.
    Nov 11 10:28:16 Sailfish systemd[1]: Started Cleanup of Temporary Directories.
    Nov 11 10:28:18 Sailfish PackageKit[4499]: daemon quit

 

It seems dbus-send is now under /usr/bin/dbus-send

coderus's picture

check 3.0.63

deloptes's picture

Seems to be working fine - thank you and God bless you!

coderus's picture

Thanks

Historyscholar's picture

Chinese translation updated:)

csg1976's picture

When trying to access certain patches (e.g. Extended volume control) through PM, it will crash and take the settings app unresolvably with it. Only a reboot will help (XA2, 3.2.0.12, latest PM).

coderus's picture

good bug, please check with new build

csg1976's picture

Solved! Thanks a ton!

eson's picture

Please, also update translations. It's been more then a year.  ;)

 

carmenfdezb's picture

Hi @coderus! Since I updated SailfishOS v3.2.0, I have to load engine manually every time I reboot my phone. Is that a bug?

coderus's picture

this is a feature. go to settings and enable auto applying.

carmenfdezb's picture

Sorry, I didn't notice. Thank you for your answer!

sebix's picture

Does not seem to work with Sailfish OS 3.2.0 - The page in settings shows "Could not load page"

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

Pages