PageEdit 1.2.0 would not run under Kubuntu 20.04 and Mint 20

[KevinH]

The fact that Qt gave it Priority P1 (release stopper) did not mean anything to Ubuntu?
The fact that it will hit any app that does live webpage editing? The fact that it can lead to lost source text? The fact it is one-line fix fix?

Wow, Ubuntu really needs to revamp its QA process!

[DiapDealer]

Silliness. But if it gets the upstream patch incorporated, it will have been worth it. Who knows how long (if ever) it might take this Ubuntu LTS release to update to Qt5.12.10. If there even WILL be a 5.12.10 to upgrade to!

[DiapDealer]

I just got the notification that the fix for the ubuntu 5.12.8 webengine package has been uploaded and is awaiting review. Baby steps forward!

The irony is that backporting Qt's upstream Priority 1 fix for live editing is only a medium priority issue for Ubuntu.

[Der_Andi]

It's hard if you have a problem and recognise that it seems, that you are the only one worldwide. I never believed that a solution will be found so fast. I'll try this evening and then report. Thank you very much for your very fast, good and friendly help!
Der_Andi

[DiapDealer]

The fix is not in Ubuntu's repositories just yet. But it IS being worked on. I'll post here whenever the package update is officially available through the normal apt-get channels.

The status was changed to "In Progress" by the guy who maintains Sigil for Ubuntu/Debian, so I have high hopes that it won't languish in the queues long.

[Der_Andi]

'til now nothing happens :-(
Der_Andi

[DiapDealer]

Yep. Still "In Progress" in Ubuntu's work queue. I will receive an email when/if that status changes (and will post an update here).

[DiapDealer]

Status updated to "Fix Commited".
Which will move it to the Ubuntu Focal -proposed updates repository (after it's built).

The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

I'm off to verify the -proposed version (if it's available yet--could be a few hours). The end is in sight!

[DiapDealer]

The proposed package update does indeed fix the issue on Ubuntu 20.04 LTS. I pulled the update from focal-proposed and verified (in the original bug report) that the fix works. If no one else reports any problems with it, it should hit the regular ubuntu updates repo in 7 days or so.

In the meantime, anyone who can't wait that long can always enable the focal-proposed repo in their software sources and get the updated package.

[eschwartz]

Originally Posted by DiapDealer

I've had to go through a little bit of dance with Ubuntu. The fact that Qt acknowledges the mistake and has patched it (and now merged the patch) doesn't seem to be enough reason for them to patch their own qt5.12.8 webengine packages. The maintainer asked for more details and possibly a test case. He said the acknowledged upstream mistake would be enough for him, but not for whatever review process Ubuntu has in place.

I've obliged with tons of detail and a small Qt test-case project that demonstrates the issue. Hopefully that will be enough!

Good grief...

[DiapDealer]

Originally Posted by eschwartz

Good grief...

Yeah, it's a bit of a pain (especially now that the proposed update has triggered a false regression test that will need to be resolved). But once done, several years of solid Qt (Ubuntu 20.10 will be Qt 5.14.2) and recent Sigil/PageEdit support will await users. I'll sacrifice a little time for a brief period of Sigil/PageEdit prosperity in the world of Ubuntu and its derivatives.

[eschwartz]

I'll tell you what -- I'll stick with Arch Linux. I've astoundingly rarely had problems with broken, unstable software like this, and none that weren't resolved quite fast.

[DiapDealer]

Originally Posted by eschwartz

I'll tell you what -- I'll stick with Arch Linux. I've astoundingly rarely had problems with broken, unstable software like this, and none that weren't resolved quite fast.

Oh, me too, for my own use.

This particular Ubuntu adventure seems to be about over, thank goodness. All tests passed. Now we wait 6 more days for someone to remember to push a button to move it to -updates. I almost feel like this bug-report should get a graduation party.

[JSWolf]

Originally Posted by DiapDealer

Oh, me too, for my own use.

This particular Ubuntu adventure seems to be about over, thank goodness. All tests passed. Now we wait 6 more days for someone to remember to push a button to move it to -updates. I almost feel like this bug-report should get a graduation party.

It's past the 6 days. Did the fixed version get moved to updates?

[DiapDealer]

I can't possibly imagine why you would even care, Jon. But I've already said that I would post here when the fix is available in the normal updates repo. And I will.