[Touch-packages] [Bug 1833013] Re: Interactive prompt during non-interactive install
Robie: Nevermind, I was not setting up the env vars correctly. Sorry for the noise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833013 Title: Interactive prompt during non-interactive install Status in ansible package in Ubuntu: Incomplete Status in openssl package in Ubuntu: Invalid Bug description: `apt-get install -y -qq ansible` runs `whiptail --backtitle Package configuration --title Configuring libssl1.1:amd64 --output-fd 11 --defaultno --yesno -- There are services installed on your system which need to be restarted when certain libraries, such as libpam, libc, and libssl, are upgraded. Since these restarts may cause interruptions of service for the system, you will normally be prompted on each upgrade for the list of services you wish to restart. You can choose this option to avoid being prompted; instead, all necessary restarts will be done for you automatically so you can avoid being asked questions on each library upgrade. Restart services during package upgrades without asking? 16 77`, causing a non-interactive installation to be impossible. Also reported to the Ansible Local Vagrant provisioner because they will probably have to work around this in the short term: https://github.com/hashicorp/vagrant/issues/10914 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1833013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833013] Re: Interactive prompt during non-interactive install
Robie: We had one of our automated builds start failing due to this. We were using only -y and DEBIAN_FRONTEND=noninteractive (wrongly thinking that was enough). I've now changed to sudo apt-get -o Dpkg::Options::="--force-confdef" -o Dpkg::Options ::="--force-confold" -y install $(cat requirements-ubuntu.txt) and with DEBCONF_NONINTERACTIVE_SEEN=true, DEBIAN_FRONTEND=noninteractive and UCF_FORCE_CONFOLD=1 in the environment. But the prompt when configuring libssl1.1 still shows up, so the job hangs :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1833013 Title: Interactive prompt during non-interactive install Status in ansible package in Ubuntu: Incomplete Status in openssl package in Ubuntu: Invalid Bug description: `apt-get install -y -qq ansible` runs `whiptail --backtitle Package configuration --title Configuring libssl1.1:amd64 --output-fd 11 --defaultno --yesno -- There are services installed on your system which need to be restarted when certain libraries, such as libpam, libc, and libssl, are upgraded. Since these restarts may cause interruptions of service for the system, you will normally be prompted on each upgrade for the list of services you wish to restart. You can choose this option to avoid being prompted; instead, all necessary restarts will be done for you automatically so you can avoid being asked questions on each library upgrade. Restart services during package upgrades without asking? 16 77`, causing a non-interactive installation to be impossible. Also reported to the Ansible Local Vagrant provisioner because they will probably have to work around this in the short term: https://github.com/hashicorp/vagrant/issues/10914 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1833013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Thank you! Been waiting for this fix for 11 months, and boy does it taste sweet now that it's here :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Released Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps
Ah, thanks. Did not know about that page. Thanks for looking into it. (My primary interest is not actually this fix, but the mouse event compression SRU that got piggybacked into it: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource- src/+bug/1598173). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps Status in appmenu-qt5: In Progress Status in Canonical System Image: In Progress Status in sni-qt: New Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Committed Status in qtbase-opensource-src source package in Yakkety: Confirmed Bug description: Impact == This affects all Qt applications on Unity and other desktops which use global menu, either via appmenu-qt5 or via native implementation on Yakkety. Any shortcut is not working if the corresponding action is attached only to the menubar (i.e. and not also to the toolbar). It can be reproduced with almost any application by removing the toolbar (right- clicking on it and deselecting it). Test Case = * Open Qt Assistant; * Press Ctrl+T (this action is not on the toolbar). Expected: a new tab should be opened. Current result: nothing happens. In Yakkety the fix should work both with and without appmenu-qt5. Proposed Fix The proposed fix is a backport of the upstream fix at https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594. Actually just the qshortcut.cpp part would be sufficient, but the other parts make sure it plays fine together with https://cgit.kde.org /plasma-integration.git/commit/?id=aef74e97e2ed462a. Regression Potential The fix is in Zesty for 1½ months now (in upstream even longer), and so far nobody complained. People have verified that the fix works (see comment #63). To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps
Any idea when this will hit -updates, now that the verification is done? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps Status in appmenu-qt5: In Progress Status in Canonical System Image: In Progress Status in sni-qt: New Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Committed Status in qtbase-opensource-src source package in Yakkety: Confirmed Bug description: Impact == This affects all Qt applications on Unity and other desktops which use global menu, either via appmenu-qt5 or via native implementation on Yakkety. Any shortcut is not working if the corresponding action is attached only to the menubar (i.e. and not also to the toolbar). It can be reproduced with almost any application by removing the toolbar (right- clicking on it and deselecting it). Test Case = * Open Qt Assistant; * Press Ctrl+T (this action is not on the toolbar). Expected: a new tab should be opened. Current result: nothing happens. In Yakkety the fix should work both with and without appmenu-qt5. Proposed Fix The proposed fix is a backport of the upstream fix at https://code.qt.io/cgit/qt/qtbase.git/commit/?id=287f548d4c7cc594. Actually just the qshortcut.cpp part would be sufficient, but the other parts make sure it plays fine together with https://cgit.kde.org /plasma-integration.git/commit/?id=aef74e97e2ed462a. Regression Potential The fix is in Zesty for 1½ months now (in upstream even longer), and so far nobody complained. People have verified that the fix works (see comment #63). To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Aha, I forgot to check the other bug. No worries. Thanks a lot for all the work Dmitry, looking at that bug I see that it is much more complicated than this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Committed Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Do I need to do something more for this to be uploaded to xenial- updates? Should I try to get someone else to test? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Committed Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
@apw: I've tested the 5.5.1+dfsg-16ubuntu7.4 in xenial-proposed with the test case I attached in comment #4, as well as the Wrapping/Python/vtk/qt/QVTKRenderWindowInteractor.py script in the VTK source, and the problem is fixed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: Fix Committed Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Alright, yes lets hope. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: New Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
I made a couple of pings in #ubuntu-release without reply, but I guess people are just busy :) Another question though: I can see that there was already another qtbase-opensource-src upload in the queue (5.5.1+dfsg-16ubuntu7.3). Will an approver have to approve that first, or will that one be discarded and 5.5.1+dfsg-16ubuntu7.4 taken directly? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: New Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
I'm a little unsure what the process is now, should I tag this bug with something? Or just wait until someone comes around to approve the upload? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: New Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Excellent. Many thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: New Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
** Description changed: Mouse event compression stopped working in Qt 5, a regression from Qt 4: -https://bugreports.qt.io/browse/QTBUG-40889 + https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- - project.org/#/c/126136/ where it has been thoroughly tested by now. + project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally does. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. ** Description changed: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt - normally does. For example, VTK programs (ParaView, Tomviz, ...) do + normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu:
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
** Patch added: "debdiff for 5.5.1+dfsg-16ubuntu7.3 with backported fix from Qt 5.6" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+attachment/4841178/+files/fix-qtbug-40889.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: New Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Dmitry: I've updated the description with the SRU template. I also attached a test case and a debdiff. I've tested that the updated package fixes the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: New Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the widgets try to keep up with the onslaught of resize events due to the lack of mouse event compression. [Test Case] The attached test application can be used to check if event compression is functioning. It performs some artificial work on each mouse move and prints a message. Click and drag the mouse a little. After releasing the mouse, you'll notice that the printouts keeps coming for quite a while, as the program is catching up with the flood of events. With the attached patch (and with Qt 4), the problem is gone - the mouse event stream is compressed and the printouts are no longer lagging behind. [Regression Potential] There's a small risk that some applications have made workarounds for the faulty behavior, and that unwanted behavior is introduced if this bug is fixed. But chances are high that such workarounds will keep working, as the obvious workaround is to do timer based rendering instead of event based. The workarounds will then simply become unnecessary, but shouldn't cause problems. I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
** Description changed: - A fix for QTBUG-40889 was worked out and submitted at + Mouse event compression stopped working in Qt 5, a regression from Qt 4: - https://codereview.qt-project.org/#/c/115531/ +https://bugreports.qt.io/browse/QTBUG-40889 - but due to coming in a bit late, was moved to Qt 5.6 + The bug was fixed in Qt 5.6 https://codereview.qt- + project.org/#/c/126136/ where it has been thoroughly tested by now. - https://codereview.qt-project.org/#/c/126136/ + Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a + backport of the 5.6 patch (only one trivial hunk failed, which was + easily fixed). - The bug is about mouse motion event compression malfunctioning, and it - has grave consequences for some applications, where the flood of events - make rendering sluggish (e.g. anything based on VTK, but probably - others). + [Impact] - ParaView developer Ben Boeckel has tried the patch [2] against 5.5 and - confirmed it fixes rendering/interaction in VTK applications. + The bug affects any program that relies on the event compression Qt + normally does. For example, VTK programs (ParaView, Tomviz, ...) do + their rendering in response to mouse events during camera movements, and + with event compression at the Qt level suddenly gone, camera movements + become very slow, since the application is now flooded with mouse events + and the rendering lags behind. - It is not possible to work around the bug at the application level in a - satisfactory way, only by resorting to timer-based rendering. + The problem is not limited to these programs however; it can be observed + by simply putting two regular, slightly slow-to-render, widgets into a + QSplitter and moving the splitter handle. The result is a syrup-like + experience as the widgets try to keep up with the onslaught of resize + events due to the lack of mouse event compression. - I suggest an SRU to patch the Ubuntu Qt package with the patch that was - originally meant for the 5.x branch (first URL above). The patch was - later integrated in 5.6 where it has been well tested. + [Test Case] - [1] https://bugreports.qt.io/browse/QTBUG-40889 - [2] http://vtk.1045678.n5.nabble.com/Delayed-mouse-interaction-due-to-event-loop-bug-in-Qt5-tp5730474p5732870.html + The attached test application can be used to check if event compression + is functioning. It performs some artificial work on each mouse move and + prints a message. Click and drag the mouse a little. After releasing the + mouse, you'll notice that the printouts keeps coming for quite a while, + as the program is catching up with the flood of events. + + With the attached patch (and with Qt 4), the problem is gone - the mouse + event stream is compressed and the printouts are no longer lagging + behind. + + [Regression Potential] + + There's a small risk that some applications have made workarounds for + the faulty behavior, and that unwanted behavior is introduced if this + bug is fixed. But chances are high that such workarounds will keep + working, as the obvious workaround is to do timer based rendering + instead of event based. The workarounds will then simply become + unnecessary, but shouldn't cause problems. + + I'm asking for someone to nominate this bug for an SRU of 16.04 LTS. ** Attachment added: "Test case to demonstrate the bug" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+attachment/4841177/+files/qtbug40889.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: New Bug description: Mouse event compression stopped working in Qt 5, a regression from Qt 4: https://bugreports.qt.io/browse/QTBUG-40889 The bug was fixed in Qt 5.6 https://codereview.qt- project.org/#/c/126136/ where the fix has been thoroughly tested by now. Attached is a debdiff against 5.5.1+dfsg-16ubuntu7.2 which includes a backport of the 5.6 patch (only one trivial hunk failed, which was easily fixed). [Impact] The bug affects any program that relies on the event compression Qt normally performs. For example, VTK programs (ParaView, Tomviz, ...) do their rendering in response to mouse events during camera movements, and with event compression at the Qt level suddenly gone, camera movements become very slow, since the application is now flooded with mouse events and the rendering lags behind. The problem is not limited to these programs however; it can be observed by simply putting two regular, slightly slow-to-render, widgets into a QSplitter and moving the splitter handle. The result is a syrup-like experience as the
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Hi Dimitry! No problem. In fact, I've cherry picked the fix from Qt 5.6 and created an updated package. I'm building it at the moment to test. I'll fill out the SRU template as well, and attach a debdiff if it seems to work OK. Sorry for not sticking to the SRU procedure to begin with, I know I was a bit busy when I filed this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Xenial: New Bug description: A fix for QTBUG-40889 was worked out and submitted at https://codereview.qt-project.org/#/c/115531/ but due to coming in a bit late, was moved to Qt 5.6 https://codereview.qt-project.org/#/c/126136/ The bug is about mouse motion event compression malfunctioning, and it has grave consequences for some applications, where the flood of events make rendering sluggish (e.g. anything based on VTK, but probably others). ParaView developer Ben Boeckel has tried the patch [2] against 5.5 and confirmed it fixes rendering/interaction in VTK applications. It is not possible to work around the bug at the application level in a satisfactory way, only by resorting to timer-based rendering. I suggest an SRU to patch the Ubuntu Qt package with the patch that was originally meant for the 5.x branch (first URL above). The patch was later integrated in 5.6 where it has been well tested. [1] https://bugreports.qt.io/browse/QTBUG-40889 [2] http://vtk.1045678.n5.nabble.com/Delayed-mouse-interaction-due-to-event-loop-bug-in-Qt5-tp5730474p5732870.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] Re: Please consider SRU of "xcb: Compress mouse motion and touch update events"
Would be great if someone could at least respond to this 8+ month old bug. We're still suffering from this Qt bug, and have to put in lots of ugly workarounds to mitigate it. I'm not sure, should I subscribe someone else to this, and if so, who? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: New Bug description: A fix for QTBUG-40889 was worked out and submitted at https://codereview.qt-project.org/#/c/115531/ but due to coming in a bit late, was moved to Qt 5.6 https://codereview.qt-project.org/#/c/126136/ The bug is about mouse motion event compression malfunctioning, and it has grave consequences for some applications, where the flood of events make rendering sluggish (e.g. anything based on VTK, but probably others). ParaView developer Ben Boeckel has tried the patch [2] against 5.5 and confirmed it fixes rendering/interaction in VTK applications. It is not possible to work around the bug at the application level in a satisfactory way, only by resorting to timer-based rendering. I suggest an SRU to patch the Ubuntu Qt package with the patch that was originally meant for the 5.x branch (first URL above). The patch was later integrated in 5.6 where it has been well tested. [1] https://bugreports.qt.io/browse/QTBUG-40889 [2] http://vtk.1045678.n5.nabble.com/Delayed-mouse-interaction-due-to-event-loop-bug-in-Qt5-tp5730474p5732870.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.
Julian: Ah, indeed. If I make sure to use https against the SF, and make sure the file doesn't exist, it works reliably. Sorry for the confusion! So, LGTM from xenial. Thanks a lot for working this out! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1651923 Title: apt https method decodes redirect locations and sends them to the destination undecoded. Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Bug description: [Impact] Downloads via HTTPS fail if the URL contains a space (before yakkety only if there is no redirect from a previous space-free https URL). This breaks packages like ttf-mscorefonts-installer and various third party hosters. [Test case] Install/Upgrade apt-transport-https, that's where the fix is. Check that /usr/lib/apt/apt-helper download-file http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb test.deb can successfully download the file (or at least start downloading it) and does not fail early with a 505 HTTP version not supported error message. This problem does not occur with that file on xenial, as it first redirects to an https URI without a space which then redirects to an HTTPS uri with a space (http w/o space -> https w/o space -> https w/ space). In xenial, https->https redirects where handled internally by curl. Another test (applicable to xenial) is to install ttf-mscorefonts- installer. [Regression potential] The added code is: Uri.Path = QuoteString(Uri.Path, "+~ "); Some servers might not like + or ~ being quoted. We use the same quoting call for the http method too, though, so it seems highly unlikely to cause an issue. [Original bug report] Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety apt version 1.3.3 (also tried 1.4-beta2 .deb, same results) When trying to install a package hosted on s3 from the kxstudio repo, the download fails with an HTTP error: nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: wine1.6-amd64 The following NEW packages will be installed wine1.6-amd64 wineasio-amd64 0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade. Need to get 30.9 kB/32.6 kB of archives. After this operation, 184 kB of additional disk space will be used. Do you want to continue? [Y/n] y Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 amd64 0.9.0+git20110613-2kxstudio3 505 HTTP Version not supported E: Failed to fetch https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment; filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream 505 HTTP Version not supported E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Error allegedly not present in Ubuntu 14.04 and 16.04 More details in these forum posts: https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503 https://www.linuxmusicians.com/viewtopic.php?t=16056 https://www.drupal.org/node/2324991 (clues on root cause) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apt 1.3.3 ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6 Uname: Linux 4.8.0-30-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Dec 22 02:31:47 2016 InstallationDate: Installed on 2016-10-20 (62 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598173] [NEW] Please consider SRU of "xcb: Compress mouse motion and touch update events"
Public bug reported: A fix for QTBUG-40889 was worked out and submitted at https://codereview.qt-project.org/#/c/115531/ but due to coming in a bit late, was moved to Qt 5.6 https://codereview.qt-project.org/#/c/126136/ The bug is about mouse motion event compression malfunctioning, and it has grave consequences for some applications, where the flood of events make rendering sluggish (e.g. anything based on VTK, but probably others). ParaView developer Ben Boeckel has tried the patch [2] against 5.5 and confirmed it fixes rendering/interaction in VTK applications. It is not possible to work around the bug at the application level in a satisfactory way, only by resorting to timer-based rendering. I suggest an SRU to patch the Ubuntu Qt package with the patch that was originally meant for the 5.x branch (first URL above). The patch was later integrated in 5.6 where it has been well tested. [1] https://bugreports.qt.io/browse/QTBUG-40889 [2] http://vtk.1045678.n5.nabble.com/Delayed-mouse-interaction-due-to-event-loop-bug-in-Qt5-tp5730474p5732870.html ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Description changed: A fix for QTBUG-40889 was worked out and submitted at - https://codereview.qt-project.org/#/c/115531/ + https://codereview.qt-project.org/#/c/115531/ but due to coming in a bit late, was moved to Qt 5.6 - https://codereview.qt-project.org/#/c/126136/ + https://codereview.qt-project.org/#/c/126136/ The bug is about mouse motion event compression malfunctioning, and it has grave consequences for some applications, where the flood of events make rendering sluggish (e.g. anything based on VTK, but probably others). - ParaView developer Ben Boeckel has tried the patch [2] and confirm it - fixes rendering/interaction in VTK applications. + ParaView developer Ben Boeckel has tried the patch [2] against 5.5 and + confirmed it fixes rendering/interaction in VTK applications. It is not possible to work around the bug at the application level in a satisfactory way, only by resorting to timer-based rendering. I suggest an SRU to patch the Ubuntu Qt package with the patch that was originally meant for the 5.x branch (first URL above). The patch was later integrated in 5.6 where it has been well tested. [1] https://bugreports.qt.io/browse/QTBUG-40889 [2] http://vtk.1045678.n5.nabble.com/Delayed-mouse-interaction-due-to-event-loop-bug-in-Qt5-tp5730474p5732870.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1598173 Title: Please consider SRU of "xcb: Compress mouse motion and touch update events" Status in qtbase-opensource-src package in Ubuntu: New Bug description: A fix for QTBUG-40889 was worked out and submitted at https://codereview.qt-project.org/#/c/115531/ but due to coming in a bit late, was moved to Qt 5.6 https://codereview.qt-project.org/#/c/126136/ The bug is about mouse motion event compression malfunctioning, and it has grave consequences for some applications, where the flood of events make rendering sluggish (e.g. anything based on VTK, but probably others). ParaView developer Ben Boeckel has tried the patch [2] against 5.5 and confirmed it fixes rendering/interaction in VTK applications. It is not possible to work around the bug at the application level in a satisfactory way, only by resorting to timer-based rendering. I suggest an SRU to patch the Ubuntu Qt package with the patch that was originally meant for the 5.x branch (first URL above). The patch was later integrated in 5.6 where it has been well tested. [1] https://bugreports.qt.io/browse/QTBUG-40889 [2] http://vtk.1045678.n5.nabble.com/Delayed-mouse-interaction-due-to-event-loop-bug-in-Qt5-tp5730474p5732870.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 977804] Re: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device)
Just like Guillermo, I'm trying to run BricsCAD on my X220 laptop and get this error/crash. Anyone know if it has been reported upstream and if there's a fix in sight? To Guillermo: Did you ever find any workaround to getting BricsCAD to run? I tried setting LIBGL_DISABLE_DRI3 in the environment since I saw that tip here: https://bugs.freedesktop.org/show_bug.cgi?id=71759 , but it didn't work :( ** Bug watch added: freedesktop.org Bugzilla #71759 https://bugs.freedesktop.org/show_bug.cgi?id=71759 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/977804 Title: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device) Status in Unity: Confirmed Status in mesa package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Status in Debian: New Status in mesa package in Fedora: Unknown Bug description: Unity 5.8.0 (Ubuntu 12.04 Beta) crashes (or hanged up) on Fujitsu-Siemens S7020 (Intel 915GM Express Chipset) very often during attempt to use Dash or switch between applications when many winsows are opened with following error: intel_do_flush_locked failed: No space left on device ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Tue Apr 10 11:25:45 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120314) MachineType: FUJITSU SIEMENS LIFEBOOK S7020 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic-pae root=UUID=e6a4deb8-3e53-4afb-aed8-997537309262 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2005 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.07 dmi.board.name: FJNB19C dmi.board.vendor: FUJITSU dmi.board.version: CP234410-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: S7020 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.07:bd09/16/2005:svnFUJITSUSIEMENS:pnLIFEBOOKS7020:pvr:rvnFUJITSU:rnFJNB19C:rvrCP234410-02:cvnFUJITSUSIEMENS:ct10:cvrS7020: dmi.product.name: LIFEBOOK S7020 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.7.4-0ubuntu3 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/977804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
