[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-16 Thread Launchpad Bug Tracker
This bug was fixed in the package qtwebengine-opensource-src - 5.12.8 +dfsg-0ubuntu1.1 --- qtwebengine-opensource-src (5.12.8+dfsg-0ubuntu1.1) focal; urgency=medium * Backport upstream patch to fix live editing (LP: #1884550). -- Dmitry Shachnev Tue, 23 Jun 2020 21:10:05 +0300

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-10 Thread Doug Massay
Well shoot. If someone had told me about Ubuntu's 3-day weekend policy, I would have mentioned it yesterday when the seven day minimum was up. ;) Sorry. I'm being impatient--I know this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-10 Thread Dmitry Shachnev
You can look at . All is green, just be patient. There is no promoting on Fridays or on weekends, so I guess it will be promoted in the beginning of next week. -- You received this bug notification because you are a member of Ubuntu

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-10 Thread Doug Massay
I'm not pushing, I just want to make sure there's nothing else holding this back from being moved to -updates that I can help with. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884550

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-02 Thread Dmitry Shachnev
Yes but manually, not automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884550 Title: Live Editing broken in 5.12.8/9 upstream To manage notifications about this bug go to:

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-02 Thread Doug Massay
Good news. Thanks! So if no other problems arise, this will automatically move to -updates (after the 7 day minimum), correct? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884550 Title: Live

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-02 Thread Dmitry Shachnev
I have retried that test, and it passed now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884550 Title: Live Editing broken in 5.12.8/9 upstream To manage notifications about this bug go to:

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-02 Thread Doug Massay
Looks like a flaky test, rather than a real regression to me: > : failure: timed out waiting for testbed to reboot > autopkgtest [08:11:33]: ERROR: testbed failure: cannot send to testbed: > [Errno 32] Broken pipe -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-02 Thread Dmitry Shachnev
Unfortunately we can't move to 5.12.9 — that will require a rebuild of all packages that use private Qt ABI, which is not possible for stable release updates. If there are any specific fixes from 5.12.9 that you want to have in 20.04, please open separate bugs for them. -- You received this bug

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-01 Thread Doug Massay
I updated libqt5webengine5 and its dependencies to version 5.12.8+dfsg- 0ubuntu1.1 from focal-proposed and verified (with the originally provided test case) that the bug is indeed fixed. I also tested with the open-source project I maintain to verify that the upstream Live Editing breakage was

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-01 Thread Doug Massay
> Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. > If this package fixes the bug for you, please add a comment to this

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-01 Thread Robie Basak
Hello Doug, or anyone else affected, Accepted qtwebengine-opensource-src into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /qtwebengine-opensource-src/5.12.8+dfsg-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-07-01 Thread Robie Basak
> I assumed that Qt's own acknowledgement of the issue, and subsequent official patch to correct it, would be sufficient to demonstrate the necessity of incorporating said fix into a package that's part of an Ubuntu LTS release. We won't accept a patch in a stable release without verifying that

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-06-24 Thread Mattia Rizzolo
** Changed in: qtwebengine-opensource-src (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884550 Title: Live Editing broken in 5.12.8/9 upstream To

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-06-23 Thread Doug Massay
Fingers crossed. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884550 Title: Live Editing broken in 5.12.8/9 upstream To manage notifications about this bug go to:

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-06-23 Thread Dmitry Shachnev
Thanks! I have uploaded the fix, it is now waiting for review in the queue: https://launchpad.net/ubuntu/focal/+queue?queue_state=1 ** Description changed: Ubuntu 20.04 LTS + + [Impact] QtWebEngine bad chrome 77->69 cherry-pick bug broke live editing in Qt 5.12.8 and Qt 5.12.9. The

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-06-23 Thread Doug Massay
** Description changed: - Ununtu 20.04 LTS + Ubuntu 20.04 LTS QtWebEngine bad chrome 77->69 cherry-pick bug broke live editing in Qt 5.12.8 and Qt 5.12.9. The bad merge breaks styled markup traverse by accidentally inverting condition. Results in loss of content under certain

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-06-23 Thread Doug Massay
Understood. I'll get something together as soon as I can. Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884550 Title: Live Editing broken in 5.12.8/9 upstream To manage

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-06-23 Thread Dmitry Shachnev
> I assumed that Qt's own acknowledgement of the issue, and subsequent official patch to correct it, would be sufficient to demonstrate the necessity of incorporating said fix into a package that's part of an Ubuntu LTS release. It would be sufficient for me, but not for the SRU team who will

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-06-23 Thread Doug Massay
I assumed that Qt's own acknowledgement of the issue, and subsequent official patch to correct it, would be sufficient to demonstrate the necessity of incorporating said fix into a package that's part of an Ubuntu LTS release. I'll see what I can do about putting together a small test case (for

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-06-23 Thread Dmitry Shachnev
Can you please add some test case to the bug description? Like what app or website you are using, what exactly you are doing, etc? This is needed per our stable release update procedure: . Also, I have verified that the bad code is not

[Bug 1884550] Re: Live Editing broken in 5.12.8/9 upstream

2020-06-22 Thread Dmitry Shachnev
Thanks for the heads up! I will fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884550 Title: Live Editing broken in 5.12.8/9 upstream To manage notifications about this bug go to: