[Touch-packages] [Bug 1583088] Re: Randomly corrupt font / text / characters in Unity8
using silo 2481, seems to work fine, i don't see the font corruption anymore -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt font / text / characters in Unity8 Status in Canonical System Image: In Progress Status in Mir: Won't Fix Status in gnome-desktop package in Ubuntu: Invalid Status in mir package in Ubuntu: Won't Fix Status in qtdeclarative-opensource-src package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Corrupted characters in text rendering. Only happens after starting non-GL application, like GTK application or mir_demo_client_fingerpaint. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1583088] Re: Randomly corrupt font / text / characters in Unity8
Awesome. I would like to see a permanent fix done in a more appropriate place though. I think somewhere in qtdeclarative-opensource-src there is the bad assumption about the current state of GL_UNPACK_ALIGNMENT. We need to find that code and add an explicit setting right before it uploads the corrupt/skewed texture. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt font / text / characters in Unity8 Status in Canonical System Image: In Progress Status in Mir: Won't Fix Status in gnome-desktop package in Ubuntu: Invalid Status in mir package in Ubuntu: Won't Fix Status in qtdeclarative-opensource-src package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Corrupted characters in text rendering. Only happens after starting non-GL application, like GTK application or mir_demo_client_fingerpaint. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1665944] Re: ListItem title/subtitle should be aligned to the right in RTL mode
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1665944 Title: ListItem title/subtitle should be aligned to the right in RTL mode Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: see the title To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1665944/+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 1630872] Re: Clear text (x) does not clear the first suggested but not committed word
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1630872 Title: Clear text (x) does not clear the first suggested but not committed word Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: When the "Word suggestions" option in the "Language & Text" settings then the (x) clear button does not clear the first not committed word from the text input. It seems that the suggested word is not yet in the text innut but only in the input method and the clear button does not clear the input method. After the first word is committed, the second suggestion is cleared if you clear the content. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630872/+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 1616865] Re: Windowed mode: hover events in the right edge area are not propagated to the application
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1616865 Title: Windowed mode: hover events in the right edge area are not propagated to the application Status in unity8 package in Ubuntu: Confirmed Bug description: === Environment === current build number: 174 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en last update: 2016-08-25 11:12:19 version version: 174 version ubuntu: 20160825 version device: 20160809.0 version custom: 20160805--42-20-vivid === Unity8 version === 8.14+15.04.20160819-0ubuntu1 === Description === It seems maximized applications do not receive hover events when the mouse is close to the right edge, in an area about 0.5GU wide === How to reproduce (one of the many ways) === 0) Make sure the M10 is in "Desktop mode" 1) Download the UITK gallery from the app store 2) Launch it 3) Maximize the app 4) Open a scrollable page, such as Colours 5) Move the mouse to the right edge to reveal the scrollbar === Expected result === The scrollbar receives hover events over its whole area === Actual result === The scrollbar does not receive mouse events in the rightmost area, i.e about 0.5GU from the right edge. As a consequence, it appears as not being hovered even when the mouse is inside the right half of the thumb === Cause === This is probably caused by the component handling the edge push eating hover events. ltinkl said that the EdgePush component has "hoverEnabled: true". That is probably why hover events are not getting propagated down to the app. Hover events in QtQuick are propagated to parents, not to siblings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1616865/+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 1666833] [NEW] GTK overlay scrollbars never appear at small window sizes
Public bug reported: GTK overlay scrollbars never appear at small window sizes, at least in Unity8. Test case: 1. In Unity8 launch "Files". 2. Navigate to a folder with lots of files/icons. 3. Resize the window as small as it will go. 4. Slowly move the mouse so the cursor enters from the right side of the window. Expected: Overlay scrollbars appear Observed: Overlay scrollbars never appear (unless the window is bigger) ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: overlay-scrollbar (Ubuntu) Importance: Undecided Status: New ** Tags: gtk-mir unity8-desktop ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags added: gtk-mir ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Tags added: unity8-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1666833 Title: GTK overlay scrollbars never appear at small window sizes Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: New Status in overlay-scrollbar package in Ubuntu: New Bug description: GTK overlay scrollbars never appear at small window sizes, at least in Unity8. Test case: 1. In Unity8 launch "Files". 2. Navigate to a folder with lots of files/icons. 3. Resize the window as small as it will go. 4. Slowly move the mouse so the cursor enters from the right side of the window. Expected: Overlay scrollbars appear Observed: Overlay scrollbars never appear (unless the window is bigger) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666833/+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 1656399] Re: Returning to existing session is unreliable and can leave on blank screen
Installing 1.21.5-0ubuntu1 has solved the problem coming out from lock screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1656399 Title: Returning to existing session is unreliable and can leave on blank screen Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.18 series: Fix Committed Status in Light Display Manager 1.20 series: Fix Committed Status in lightdm package in Ubuntu: In Progress Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Triaged Bug description: [Impact] Due to a logic bug LightDM returning to an existing session from a greeter can be unreliable. This case is common in systems which use the greeter as a lock screen. The bug was introduced in revision 1954 to fix bug 1296276. The race condition seems to have been made more likely to the change in revision 2437 to fix bug 1637758. [Test Case] 1. Log into a session 2. Switch to the greeter (e.g. dm-tool switch-to-greeter) 3. Log in again Expected result Returned to existing session Observed result Not always returned, can end up on blank screen. Since this is a race condition this may not occur on some systems. [Regression Potential] Low, the fix is to correct a logic bug that made LightDM think it hadn't stopped a session correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1656399/+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 1666836] Re: Unity8's blur effect slows the system down too much
** Tags added: unity8-desktop ** Description changed: Unity8's blur effect (such as in the app drawer) slows the system down - too much. + too much. I get 20 FPS with the blur, and 60 FPS+ without it. Here's my unity8.log output (with MIR_CLIENT_PERF_REPORT=log) on a 6-year old laptop, rendering egltriangle before and after the app drawer opens above it: [2017-02-22 17:25:09.160680] perf: : 60.03 FPS, render time 1.52ms, buffer lag 65.11ms (4 buffers) [2017-02-22 17:25:10.160958] perf: : 60.00 FPS, render time 1.56ms, buffer lag 65.11ms (4 buffers) [2017-02-22 17:25:11.176709] perf: : 60.09 FPS, render time 1.58ms, buffer lag 65.02ms (4 buffers) [2017-02-22 17:25:12.193072] perf: : 60.03 FPS, render time 1.23ms, buffer lag 65.39ms (4 buffers) [2017-02-22 17:25:13.209314] perf: : 60.03 FPS, render time 1.22ms, buffer lag 65.42ms (4 buffers) [2017-02-22 17:25:14.225774] perf: : 60.03 FPS, render time 1.40ms, buffer lag 65.23ms (4 buffers) [2017-02-22 17:25:15.241893] perf: : 60.03 FPS, render time 1.31ms, buffer lag 65.32ms (4 buffers) [2017-02-22 17:25:16.258348] perf: : 60.03 FPS, render time 1.23ms, buffer lag 65.41ms (4 buffers) [2017-02-22 17:25:17.275305] perf: : 60.03 FPS, render time 1.45ms, buffer lag 65.20ms (4 buffers) [2017-02-22:17:25:18.223] qml: pushing right edge without mouse actually being at right edge! [2017-02-22 17:25:18.292455] perf: : 59.98 FPS, render time 1.36ms, buffer lag 65.33ms (4 buffers) [2017-02-22:17:25:18.586] [PERFORMANCE]: Last frame took 44 ms to render. [2017-02-22:17:25:18.625] [PERFORMANCE]: Last frame took 37 ms to render. [2017-02-22:17:25:18.714] [PERFORMANCE]: Last frame took 42 ms to render. [2017-02-22:17:25:18.766] [PERFORMANCE]: Last frame took 43 ms to render. [2017-02-22:17:25:18.818] [PERFORMANCE]: Last frame took 50 ms to render. [2017-02-22:17:25:18.867] [PERFORMANCE]: Last frame took 44 ms to render. [2017-02-22:17:25:18.920] [PERFORMANCE]: Last frame took 51 ms to render. [2017-02-22:17:25:18.920] [PERFORMANCE]: Last 10 frames took over 17 ms to render (last frame: 51 ms) [2017-02-22:17:25:18.968] [PERFORMANCE]: Last frame took 45 ms to render. [2017-02-22:17:25:19.020] [PERFORMANCE]: Last frame took 34 ms to render. [2017-02-22:17:25:19.319] [PERFORMANCE]: Last frame took 33 ms to render. [2017-02-22 17:25:19.319652] perf: : 27.26 FPS, render time 31.01ms, buffer lag 108.55ms (4 buffers) [2017-02-22:17:25:19.418] [PERFORMANCE]: Last 10 frames took over 17 ms to render (last frame: 31 ms) [2017-02-22:17:25:19.919] [PERFORMANCE]: Last 10 frames took over 17 ms to render (last frame: 31 ms) [2017-02-22:17:25:20.071] [PERFORMANCE]: Last frame took 32 ms to render. [2017-02-22:17:25:20.167] [PERFORMANCE]: Last frame took 44 ms to render. [2017-02-22:17:25:20.215] [PERFORMANCE]: Last frame took 47 ms to render. [2017-02-22:17:25:20.215] [PERFORMANCE]: Too many warnings were given. Performance monitoring stops. [2017-02-22 17:25:20.361137] perf: : 20.17 FPS, render time 47.32ms, buffer lag 151.76ms (4 buffers) [2017-02-22 17:25:21.384374] perf: : 20.52 FPS, render time 43.28ms, buffer lag 149.30ms (4 buffers) [2017-02-22 17:25:22.402890] perf: : 20.62 FPS, render time 44.51ms, buffer lag 151.61ms (4 buffers) [2017-02-22 17:25:23.419072] perf: : 20.66 FPS, render time 43.71ms, buffer lag 147.78ms (4 buffers) [2017-02-22 17:25:24.433844] perf: : 20.71 FPS, render time 44.63ms, buffer lag 143.52ms (4 buffers) [2017-02-22 17:25:25.450279] perf: : 20.66 FPS, render time 44.08ms, buffer lag 154.40ms (4 buffers) [2017-02-22 17:25:26.468114] perf: : 20.64 FPS, render time 43.97ms, buffer lag 145.19ms (4 buffers) [2017-02-22 17:25:27.481509] perf: : 20.73 FPS, render time 44.42ms, buffer lag 153.57ms (4 buffers) [2017-02-22 17:25:28.500612] perf: : 20.60 FPS, render time 44.28ms, buffer lag 147.28ms (4 buffers) [2017-02-22 17:25:29.516410] perf: : 20.68 FPS, render time 44.19ms, buffer lag 151.85ms (4 buffers) [2017-02-22 17:25:30.534662] perf: : 20.62 FPS, render time 44.74ms, buffer lag 151.19ms (4 buffers) And while we still render the cursor manually this means the mouse cursor also now moves at only 20 FPS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666836 Title: Unity8's blur effect slows the system down too much Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: Unity8's blur effect (such as in the app drawer) slows the system down too much. I get 20 FPS with the blur, and 60 FPS+ without it. Here's my unity8.log output (with MIR_CLIENT_PERF_REPORT=log) on a 6-year old laptop, rendering egltriangle before and after the app drawer opens above it: [2017-02-22 17:25:09.160680] perf: : 60.03 FPS, render time 1.52ms, buffer lag 65.11ms (4
[Touch-packages] [Bug 1666836] Re: Unity8's blur effect slows the system down too much
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666836 Title: Unity8's blur effect slows the system down too much Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: Unity8's blur effect (such as in the app drawer) slows the system down too much. I get 20 FPS with the blur, and 60 FPS+ without it. Here's my unity8.log output (with MIR_CLIENT_PERF_REPORT=log) on a 6-year old laptop, rendering egltriangle before and after the app drawer opens above it: [2017-02-22 17:25:09.160680] perf: : 60.03 FPS, render time 1.52ms, buffer lag 65.11ms (4 buffers) [2017-02-22 17:25:10.160958] perf: : 60.00 FPS, render time 1.56ms, buffer lag 65.11ms (4 buffers) [2017-02-22 17:25:11.176709] perf: : 60.09 FPS, render time 1.58ms, buffer lag 65.02ms (4 buffers) [2017-02-22 17:25:12.193072] perf: : 60.03 FPS, render time 1.23ms, buffer lag 65.39ms (4 buffers) [2017-02-22 17:25:13.209314] perf: : 60.03 FPS, render time 1.22ms, buffer lag 65.42ms (4 buffers) [2017-02-22 17:25:14.225774] perf: : 60.03 FPS, render time 1.40ms, buffer lag 65.23ms (4 buffers) [2017-02-22 17:25:15.241893] perf: : 60.03 FPS, render time 1.31ms, buffer lag 65.32ms (4 buffers) [2017-02-22 17:25:16.258348] perf: : 60.03 FPS, render time 1.23ms, buffer lag 65.41ms (4 buffers) [2017-02-22 17:25:17.275305] perf: : 60.03 FPS, render time 1.45ms, buffer lag 65.20ms (4 buffers) [2017-02-22:17:25:18.223] qml: pushing right edge without mouse actually being at right edge! [2017-02-22 17:25:18.292455] perf: : 59.98 FPS, render time 1.36ms, buffer lag 65.33ms (4 buffers) [2017-02-22:17:25:18.586] [PERFORMANCE]: Last frame took 44 ms to render. [2017-02-22:17:25:18.625] [PERFORMANCE]: Last frame took 37 ms to render. [2017-02-22:17:25:18.714] [PERFORMANCE]: Last frame took 42 ms to render. [2017-02-22:17:25:18.766] [PERFORMANCE]: Last frame took 43 ms to render. [2017-02-22:17:25:18.818] [PERFORMANCE]: Last frame took 50 ms to render. [2017-02-22:17:25:18.867] [PERFORMANCE]: Last frame took 44 ms to render. [2017-02-22:17:25:18.920] [PERFORMANCE]: Last frame took 51 ms to render. [2017-02-22:17:25:18.920] [PERFORMANCE]: Last 10 frames took over 17 ms to render (last frame: 51 ms) [2017-02-22:17:25:18.968] [PERFORMANCE]: Last frame took 45 ms to render. [2017-02-22:17:25:19.020] [PERFORMANCE]: Last frame took 34 ms to render. [2017-02-22:17:25:19.319] [PERFORMANCE]: Last frame took 33 ms to render. [2017-02-22 17:25:19.319652] perf: : 27.26 FPS, render time 31.01ms, buffer lag 108.55ms (4 buffers) [2017-02-22:17:25:19.418] [PERFORMANCE]: Last 10 frames took over 17 ms to render (last frame: 31 ms) [2017-02-22:17:25:19.919] [PERFORMANCE]: Last 10 frames took over 17 ms to render (last frame: 31 ms) [2017-02-22:17:25:20.071] [PERFORMANCE]: Last frame took 32 ms to render. [2017-02-22:17:25:20.167] [PERFORMANCE]: Last frame took 44 ms to render. [2017-02-22:17:25:20.215] [PERFORMANCE]: Last frame took 47 ms to render. [2017-02-22:17:25:20.215] [PERFORMANCE]: Too many warnings were given. Performance monitoring stops. [2017-02-22 17:25:20.361137] perf: : 20.17 FPS, render time 47.32ms, buffer lag 151.76ms (4 buffers) [2017-02-22 17:25:21.384374] perf: : 20.52 FPS, render time 43.28ms, buffer lag 149.30ms (4 buffers) [2017-02-22 17:25:22.402890] perf: : 20.62 FPS, render time 44.51ms, buffer lag 151.61ms (4 buffers) [2017-02-22 17:25:23.419072] perf: : 20.66 FPS, render time 43.71ms, buffer lag 147.78ms (4 buffers) [2017-02-22 17:25:24.433844] perf: : 20.71 FPS, render time 44.63ms, buffer lag 143.52ms (4 buffers) [2017-02-22 17:25:25.450279] perf: : 20.66 FPS, render time 44.08ms, buffer lag 154.40ms (4 buffers) [2017-02-22 17:25:26.468114] perf: : 20.64 FPS, render time 43.97ms, buffer lag 145.19ms (4 buffers) [2017-02-22 17:25:27.481509] perf: : 20.73 FPS, render time 44.42ms, buffer lag 153.57ms (4 buffers) [2017-02-22 17:25:28.500612] perf: : 20.60 FPS, render time 44.28ms, buffer lag 147.28ms (4 buffers) [2017-02-22 17:25:29.516410] perf: : 20.68 FPS, render time 44.19ms, buffer lag 151.85ms (4 buffers) [2017-02-22 17:25:30.534662] perf: : 20.62 FPS, render time 44.74ms, buffer lag 151.19ms (4 buffers) And while we still render the cursor manually this means the mouse cursor also now moves at only 20 FPS. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666836/+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/Li
[Touch-packages] [Bug 1666836] [NEW] Unity8's blur effect slows the system down too much
Public bug reported: Unity8's blur effect (such as in the app drawer) slows the system down too much. I get 20 FPS with the blur, and 60 FPS+ without it. Here's my unity8.log output (with MIR_CLIENT_PERF_REPORT=log) on a 6-year old laptop, rendering egltriangle before and after the app drawer opens above it: [2017-02-22 17:25:09.160680] perf: : 60.03 FPS, render time 1.52ms, buffer lag 65.11ms (4 buffers) [2017-02-22 17:25:10.160958] perf: : 60.00 FPS, render time 1.56ms, buffer lag 65.11ms (4 buffers) [2017-02-22 17:25:11.176709] perf: : 60.09 FPS, render time 1.58ms, buffer lag 65.02ms (4 buffers) [2017-02-22 17:25:12.193072] perf: : 60.03 FPS, render time 1.23ms, buffer lag 65.39ms (4 buffers) [2017-02-22 17:25:13.209314] perf: : 60.03 FPS, render time 1.22ms, buffer lag 65.42ms (4 buffers) [2017-02-22 17:25:14.225774] perf: : 60.03 FPS, render time 1.40ms, buffer lag 65.23ms (4 buffers) [2017-02-22 17:25:15.241893] perf: : 60.03 FPS, render time 1.31ms, buffer lag 65.32ms (4 buffers) [2017-02-22 17:25:16.258348] perf: : 60.03 FPS, render time 1.23ms, buffer lag 65.41ms (4 buffers) [2017-02-22 17:25:17.275305] perf: : 60.03 FPS, render time 1.45ms, buffer lag 65.20ms (4 buffers) [2017-02-22:17:25:18.223] qml: pushing right edge without mouse actually being at right edge! [2017-02-22 17:25:18.292455] perf: : 59.98 FPS, render time 1.36ms, buffer lag 65.33ms (4 buffers) [2017-02-22:17:25:18.586] [PERFORMANCE]: Last frame took 44 ms to render. [2017-02-22:17:25:18.625] [PERFORMANCE]: Last frame took 37 ms to render. [2017-02-22:17:25:18.714] [PERFORMANCE]: Last frame took 42 ms to render. [2017-02-22:17:25:18.766] [PERFORMANCE]: Last frame took 43 ms to render. [2017-02-22:17:25:18.818] [PERFORMANCE]: Last frame took 50 ms to render. [2017-02-22:17:25:18.867] [PERFORMANCE]: Last frame took 44 ms to render. [2017-02-22:17:25:18.920] [PERFORMANCE]: Last frame took 51 ms to render. [2017-02-22:17:25:18.920] [PERFORMANCE]: Last 10 frames took over 17 ms to render (last frame: 51 ms) [2017-02-22:17:25:18.968] [PERFORMANCE]: Last frame took 45 ms to render. [2017-02-22:17:25:19.020] [PERFORMANCE]: Last frame took 34 ms to render. [2017-02-22:17:25:19.319] [PERFORMANCE]: Last frame took 33 ms to render. [2017-02-22 17:25:19.319652] perf: : 27.26 FPS, render time 31.01ms, buffer lag 108.55ms (4 buffers) [2017-02-22:17:25:19.418] [PERFORMANCE]: Last 10 frames took over 17 ms to render (last frame: 31 ms) [2017-02-22:17:25:19.919] [PERFORMANCE]: Last 10 frames took over 17 ms to render (last frame: 31 ms) [2017-02-22:17:25:20.071] [PERFORMANCE]: Last frame took 32 ms to render. [2017-02-22:17:25:20.167] [PERFORMANCE]: Last frame took 44 ms to render. [2017-02-22:17:25:20.215] [PERFORMANCE]: Last frame took 47 ms to render. [2017-02-22:17:25:20.215] [PERFORMANCE]: Too many warnings were given. Performance monitoring stops. [2017-02-22 17:25:20.361137] perf: : 20.17 FPS, render time 47.32ms, buffer lag 151.76ms (4 buffers) [2017-02-22 17:25:21.384374] perf: : 20.52 FPS, render time 43.28ms, buffer lag 149.30ms (4 buffers) [2017-02-22 17:25:22.402890] perf: : 20.62 FPS, render time 44.51ms, buffer lag 151.61ms (4 buffers) [2017-02-22 17:25:23.419072] perf: : 20.66 FPS, render time 43.71ms, buffer lag 147.78ms (4 buffers) [2017-02-22 17:25:24.433844] perf: : 20.71 FPS, render time 44.63ms, buffer lag 143.52ms (4 buffers) [2017-02-22 17:25:25.450279] perf: : 20.66 FPS, render time 44.08ms, buffer lag 154.40ms (4 buffers) [2017-02-22 17:25:26.468114] perf: : 20.64 FPS, render time 43.97ms, buffer lag 145.19ms (4 buffers) [2017-02-22 17:25:27.481509] perf: : 20.73 FPS, render time 44.42ms, buffer lag 153.57ms (4 buffers) [2017-02-22 17:25:28.500612] perf: : 20.60 FPS, render time 44.28ms, buffer lag 147.28ms (4 buffers) [2017-02-22 17:25:29.516410] perf: : 20.68 FPS, render time 44.19ms, buffer lag 151.85ms (4 buffers) [2017-02-22 17:25:30.534662] perf: : 20.62 FPS, render time 44.74ms, buffer lag 151.19ms (4 buffers) And while we still render the cursor manually this means the mouse cursor also now moves at only 20 FPS. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: blur performance unity8-desktop ** Summary changed: - Blur effect slows the system down too much + Unity8's blur effect slows the system down too much ** Description changed: Unity8's blur effect (such as in the app drawer) slows the system down too much. Here's my unity8.log output (with MIR_CLIENT_PERF_REPORT=log) on a 6-year old laptop, rendering egltriangle before and after the app drawer opens above it: [2017-02-22 17:25:09.160680] perf: : 60.03 FPS, render time 1.52ms, buffer lag 65.11ms (4 buffers) [2017-02-22 17:25:10.160958] perf: : 60.00 FPS, render time 1.56ms, buffer lag 65.11ms (4 buffers) [2017-02-22 17:25:11.176709] perf: : 60.09 FPS, render time 1.58
[Touch-packages] [Bug 1665727] Re: Window stuck in fullscreen mode
** Changed in: webbrowser-app (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1665727 Title: Window stuck in fullscreen mode Status in webbrowser-app package in Ubuntu: In Progress Bug description: Tested in unity8 deb session on xenial + overlay - Launcher set to always show in system-settings 1) open youtube.com 2) F11 to fullscreen browser 3) play a video 4) click fullscreen button to fullscreen video 5) press esc, F11 or click the fullscreen button in bottom right to exist fullscreen 6) Expected result: browser window still fullscreen, but esc or F11 should exist fullscreen Actual result: browser window stuck in fullscreen, no way to exit it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1665727/+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 1596698] Re: Strange font issue after awakening from suspend
Here I have the same issues, usually after suspend. Had it on the mate-Desktop too, so it might not be very gnome3-specific. There are some messages in the syslog, maybe that can help to further dig into a direction? ** Attachment added: "grep -i gnome /var/log/syslog > gnome_font_issue_syslog.txt" https://bugs.launchpad.net/ubuntu-gnome/+bug/1596698/+attachment/4824271/+files/gnome_font_issue_syslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1596698 Title: Strange font issue after awakening from suspend Status in GTK+: Unknown Status in Ubuntu GNOME: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When I awoke my computer from suspend last week on Thursday (23/06/2016) I found that all the text from all the title bars was missing, so I restarted gnome-shell as this normally fixes such problems, doing so seemed to make some text appear, but most not, as you can see from these images until I restarted my machine it was almost impossible to use: System_Monitor_No_Text.png Shutter_Main_Window_Font_Issue.png File_Chooser_Font_Issue.png Title_Bar_Partly_Missing.png Settings_Text_Issue.png ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgtk-3-0 3.20.6-1ubuntu1~ppa1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jun 27 21:23:02 2016 InstallationDate: Installed on 2016-05-15 (43 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1596698/+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 1666556] Re: [MIR] ubuntu-ui-extras
** Branch linked: lp:~ahayzen/ubuntu-ui-extras/fix-1666556-build-depends -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-extras in Ubuntu. https://bugs.launchpad.net/bugs/1666556 Title: [MIR] ubuntu-ui-extras Status in ubuntu-ui-extras package in Ubuntu: Incomplete Bug description: Please consider ubuntu-ui-extras for inclusion in main. ubuntu-terminal-app and webbrowser-app now depend on ubuntu-ui-extras to provide certain UI components which are shared, they are in main so it is required for the ubuntu-ui-extras to also be in main. [Availability] http://launchpad.net/ubuntu-ui-extras - qtdeclarative5-ubuntu-ui-extras0.2 is already in universe (http://packages.ubuntu.com/search?keywords=qtdeclarative5-ubuntu-ui-extras0.2+&searchon=names&suite=all§ion=all) [Rationale] ubuntu-ui-extras is a new dependency of a package that we already support. webbrowser-app and ubuntu-terminal-app want to use a common component which is in ubuntu-ui-extras. [Security] No CVE entries. No Secunia history. Written in QML and C++ Does not open any port. [Quality assurance] Package provides components for other Qt apps to use. The components have been used extensively on ubuntu touch platforms. Does not deal with exotic hardware which we cannot support. [Dependencies] qml-module-qtquick2 qml-module-ubuntu-components qml-module-qtquick-window2 Which are all in main. [Standards compliance] Meets the FHS, Debian Policy Standard packaging [Maintenance] ubuntu-ui-extras is already in universe and is maintained by the Ubuntu Phablet Team [Background information] Package has not been renamed recently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-extras/+bug/1666556/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Tags added: isv -- 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/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Fix Committed Status in libappindicator source package in Xenial: Fix Committed Status in qtbase-opensource-src source package in Xenial: New Status in snapd source package in Xenial: New Status in sni-qt source package in Xenial: Fix Committed Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)
** Changed in: lightdm (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/874924 Title: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir) Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Precise: Fix Released Bug description: During the upgrade to Oneiric I chose to use lightdm instead of gdm. After rebooting, nothing seemed to work properly. I could not configure wifi, shut down, reboot, mount USB drives, etc. All I got was an error message saying "Not authorized". Running ck-list-sessions gave no output at all. Changing back to gdm fixed the issue. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Sat Oct 15 11:56:15 2011 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en_GB:en PATH=(custom, user) LANG=nb_NO.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/874924/+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
Re: [Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
webbrowser-app and all other Qt apps trying to get an EGL handle, via Mir then. This means : should the policy be updated to have all Qt apps get this access level ? or should that stay as a per-app decision ? On Tue, Feb 21, 2017 at 8:44 PM, Seth Arnold <1590...@bugs.launchpad.net> wrote: > If webbrowser-app needs access to nvidia hardware (does it?) using the > file is probably easier than figuring out each > access one at a time. > > Thanks > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1590561 > > Title: > webbrowser-app crashes on startup on fresh zesty Unity8: No suitable > EGL configs found > > To manage notifications about this bug go to: > https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+ > subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590561 Title: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found Status in Canonical System Image: Confirmed Status in Oxide: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When trying to start webbrowser-app a unresponsive window appears and after a few moments it crashes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 8 22:56:35 2016 InstallationDate: Installed on 2016-04-28 (41 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+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 1666833] Re: GTK overlay scrollbars never appear at small window sizes
not only that but past a certain size it doesn't even rearanges the files, so a lot of files are not in the view, probably that's why the scroolbar don't appear because they are not in view, it's like the view is clipped see screenshot ** Attachment added: "screenshot20170222_122752210.png" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666833/+attachment/4824292/+files/screenshot20170222_122752210.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1666833 Title: GTK overlay scrollbars never appear at small window sizes Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: Confirmed Status in overlay-scrollbar package in Ubuntu: Confirmed Bug description: GTK overlay scrollbars never appear at small window sizes, at least in Unity8. Test case: 1. In Unity8 launch "Files". 2. Navigate to a folder with lots of files/icons. 3. Resize the window as small as it will go. 4. Slowly move the mouse so the cursor enters from the right side of the window. Expected: Overlay scrollbars appear Observed: Overlay scrollbars never appear (unless the window is bigger) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666833/+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 1666833] Re: GTK overlay scrollbars never appear at small window sizes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1666833 Title: GTK overlay scrollbars never appear at small window sizes Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: Confirmed Status in overlay-scrollbar package in Ubuntu: Confirmed Bug description: GTK overlay scrollbars never appear at small window sizes, at least in Unity8. Test case: 1. In Unity8 launch "Files". 2. Navigate to a folder with lots of files/icons. 3. Resize the window as small as it will go. 4. Slowly move the mouse so the cursor enters from the right side of the window. Expected: Overlay scrollbars appear Observed: Overlay scrollbars never appear (unless the window is bigger) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666833/+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 1666833] Re: GTK overlay scrollbars never appear at small window sizes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: overlay-scrollbar (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1666833 Title: GTK overlay scrollbars never appear at small window sizes Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: Confirmed Status in overlay-scrollbar package in Ubuntu: Confirmed Bug description: GTK overlay scrollbars never appear at small window sizes, at least in Unity8. Test case: 1. In Unity8 launch "Files". 2. Navigate to a folder with lots of files/icons. 3. Resize the window as small as it will go. 4. Slowly move the mouse so the cursor enters from the right side of the window. Expected: Overlay scrollbars appear Observed: Overlay scrollbars never appear (unless the window is bigger) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666833/+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 1666701] Re: unity8 freezes for a second while opening a client-side submenu in kate
Switching between tabs in kate also causes unity8 to freeze momentarily. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666701 Title: unity8 freezes for a second while opening a client-side submenu in kate Status in QtMir: New Status in unity8 package in Ubuntu: New Bug description: Steps: - Launch kate - Right-click on its main, text editor, area. A pop-up menu should show up. - Hover your mouse pointer over the "Bookmarks" menu item. A sub menu with "Set Bookmark" and "Clear All Bookmarks" options will show up. Expected outcome: The sub menu opens immediately and the mouse pointer is responsive throughout Actual outcome: unity8 freezes for a bit, with mouse pointer becoming unresponsive, before finally resuming and showing up the submenu. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1666701/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
Alt+Up and Alt+Down to switch between tabs in Kate also doesn't work currently. Could it have the same cause as this Ctrl+C issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1666515] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2017-02-22 05:54 EDT--- @XNOX: IBM will check again with the customer, which packages are required on which level of Ubuntu. Leave this bugzilla open. More information will follow, after receiving this information. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tbb in Ubuntu. https://bugs.launchpad.net/bugs/1666515 Title: Enable tbb package on Ubuntu 16.04 LTS Status in Ubuntu on IBM z Systems: New Status in tbb package in Ubuntu: Fix Released Status in tbb source package in Xenial: Incomplete Status in tbb source package in Yakkety: Fix Released Status in tbb source package in Zesty: Fix Released Bug description: tbb package is available since Yaketty 16.10.. As mentioned here https://launchpad.net/ubuntu/+source/tbb Potential customer case requires this package also compile on s390x for Xenial. = Changes (w.r.t. Intel TBB 4.4 Update 2): = - Modified parallel_sort to not require a default constructor for values ??? and to use iter_swap() for value swapping. - Added support for creating or initializing a task_arena instance that ??? is connected to the arena currently used by the thread. - graph/binpack example modified to use multifunction_node. - For performance analysis, use Intel(R) VTune(TM) Amplifier XE 2015 ??? and higher; older versions are no longer supported. - Improved support for compilation with disabled RTTI, by omitting its use ??? in auxiliary code, such as assertions. However some functionality, ??? particularly the flow graph, does not work if RTTI is disabled. - The tachyon example for Android* can be built using Android Studio 1.5 ??? and higher with experimental Gradle plugin 0.4.0. Preview Features: - Added class opencl_subbufer that allows using OpenCL* sub-buffer ??? objects with opencl_node. - Class global_control supports the value of 1 for ??? max_allowed_parallelism. Bugs fixed: - Fixed a race causing "TBB Warning: setaffinity syscall failed" message. - Fixed a compilation issue on OS X* with Intel(R) C++ Compiler 15.0. - Fixed a bug in queuing_rw_mutex::downgrade() that could temporarily ??? block new readers. - Fixed speculative_spin_rw_mutex to stop using the lazy subscription ??? technique due to its known flaws. - Fixed memory leaks in the tool support code. = Changes (w.r.t. Intel TBB 4.4 Update 3): = - Removed a few cases of excessive user data copying in the flow graph. - Improved robustness of concurrent_bounded_queue::abort() in case of ? ? simultaneous push and pop operations. Preview Features: - Added tbb::flow::async_msg, a special message type to support ? ? communications between the flow graph and external asynchronous ? ? activities. - async_node modified to support use with C++03 compilers. Bugs fixed: - Fixed a bug in dynamic memory allocation replacement for Windows* OS. - Fixed excessive memory consumption on Linux* OS caused by enabling ? ? zero-copy realloc. - Fixed performance regression on Intel(R) Xeon Phi(tm) coprocessor with ? ? auto_partitioner. = Changes (w.r.t. Intel TBB 4.4 Update 4): = - Modified graph/fgbzip2 example to remove unnecessary data queuing. Preview Features: - Added a Python* module which is able to replace Python's thread pool? ? ? class with the implementation based on Intel TBB task scheduler. Bugs fixed: - Fixed the implementation of 64-bit tbb::atomic for IA-32 architecture ? ? to work correctly with GCC 5.2 in C++11/14 mode. - Fixed a possible crash when tasks with affinity (e.g. specified via ? ? affinity_partitioner) are used simultaneously with task priority ? ? changes. You can download Intel TBB 4.4 update 5 from open source site. = After inclusion of these mentioned fixes, it runs on Yaketty..! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1666515/+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 1666859] [NEW] keyboard navigation in app menus not working the first time it is created
Public bug reported: Steps to reproduce: * Start Kate (or any other app with nested app menus) * open some menu using the keyboard (e.g. in Kate, Alt+T for Tools) * use the keyboard to navigate down to an entry that has a submenu * press "right" => the first time such a submenu is created, the keyboard focus doesn't move to the submenu but stays in the parent menu. It works fine on the second attempt. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666859 Title: keyboard navigation in app menus not working the first time it is created Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: * Start Kate (or any other app with nested app menus) * open some menu using the keyboard (e.g. in Kate, Alt+T for Tools) * use the keyboard to navigate down to an entry that has a submenu * press "right" => the first time such a submenu is created, the keyboard focus doesn't move to the submenu but stays in the parent menu. It works fine on the second attempt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1666859/+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 1656399] Re: Returning to existing session is unreliable and can leave on blank screen
This bug was fixed in the package lightdm - 1.21.5-0ubuntu1 --- lightdm (1.21.5-0ubuntu1) zesty; urgency=medium * New upstream release: - Fix logic that checked if a session was being stopped. This fixes a race condition that could cause logging into an existing session from a greeter to not return to that session. (LP: #1656399) -- Robert Ancell Wed, 22 Feb 2017 12:38:50 +1300 ** Changed in: lightdm (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1656399 Title: Returning to existing session is unreliable and can leave on blank screen Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.18 series: Fix Committed Status in Light Display Manager 1.20 series: Fix Committed Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Trusty: Triaged Status in lightdm source package in Xenial: Triaged Status in lightdm source package in Yakkety: Triaged Bug description: [Impact] Due to a logic bug LightDM returning to an existing session from a greeter can be unreliable. This case is common in systems which use the greeter as a lock screen. The bug was introduced in revision 1954 to fix bug 1296276. The race condition seems to have been made more likely to the change in revision 2437 to fix bug 1637758. [Test Case] 1. Log into a session 2. Switch to the greeter (e.g. dm-tool switch-to-greeter) 3. Log in again Expected result Returned to existing session Observed result Not always returned, can end up on blank screen. Since this is a race condition this may not occur on some systems. [Regression Potential] Low, the fix is to correct a logic bug that made LightDM think it hadn't stopped a session correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1656399/+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 1664610] Re: qtubuntu sends wrong text as part of QKeyEvent
Don't think so, Alt+Up/Alt+Down don't have text attached. Also http://paste.ubuntu.com/24045824/ seems to report the same presses in both unity7 and unity8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1664610 Title: qtubuntu sends wrong text as part of QKeyEvent Status in Mir: Fix Committed Status in mir package in Ubuntu: New Status in qtubuntu package in Ubuntu: In Progress Bug description: When using Unity7 or Plasma a key event created by Ctrl+C is QKeyEvent(KeyPress, Key_C, ControlModifier, text="\u0003") But Unity8+ qtubuntu send to the application QKeyEvent(KeyPress, Key_C, ControlModifier, text="c") This is most likely because QMirClientInput::dispatchKeyEvent is using xkb_keysym_to_utf8 to get the text of the event instead of using xkb_state_key_get_utf8 This breaks for example Konsole that expects the correct text to be sent. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1664610/+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 1608359] Re: Power "When the lid is closed" setting does nothing
This powerdevil bug explains a workaround for until Ubuntu updates systemd. https://bugs.kde.org/show_bug.cgi?id=366402 ** Bug watch added: KDE Bug Tracking System #366402 https://bugs.kde.org/show_bug.cgi?id=366402 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1608359 Title: Power "When the lid is closed" setting does nothing Status in systemd package in Ubuntu: New Bug description: Hi, Probably the opposite of LP: #1574120, after upgrading from Xenial to Yakkety (alpha 2), it seems my laptop automatically goes into suspend when the lid is closed even though I have "When the lid is closed" setting set to "Do nothing". I'm not sure what's changed, has the HandleLidSwitch default in logind changed? Also, any chance of fixing the "Power" setting so it correctly handles updating logind? I had to update /etc/systemd/logind.conf and add "HandleLidSwitch=ignore". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1608359/+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 1608359] Re: Power "When the lid is closed" setting does nothing
I think it is now just a matter of releasing the update and/or the config change: LidSwitchIgnoreInhibited=no -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1608359 Title: Power "When the lid is closed" setting does nothing Status in systemd package in Ubuntu: New Bug description: Hi, Probably the opposite of LP: #1574120, after upgrading from Xenial to Yakkety (alpha 2), it seems my laptop automatically goes into suspend when the lid is closed even though I have "When the lid is closed" setting set to "Do nothing". I'm not sure what's changed, has the HandleLidSwitch default in logind changed? Also, any chance of fixing the "Power" setting so it correctly handles updating logind? I had to update /etc/systemd/logind.conf and add "HandleLidSwitch=ignore". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1608359/+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 1666701] Re: unity8 freezes for a second while opening a client-side submenu in kate
Doing "sudo rm /usr/lib/x86_64-linux- gnu/qt5/plugins/platformthemes/libubuntuappmenu.so" and commenting out menu code in DecoratedWindow.qml fixes those freezes ** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Changed in: qtmir Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666701 Title: unity8 freezes for a second while opening a client-side submenu in kate Status in QtMir: Invalid Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Steps: - Launch kate - Right-click on its main, text editor, area. A pop-up menu should show up. - Hover your mouse pointer over the "Bookmarks" menu item. A sub menu with "Set Bookmark" and "Clear All Bookmarks" options will show up. Expected outcome: The sub menu opens immediately and the mouse pointer is responsive throughout Actual outcome: unity8 freezes for a bit, with mouse pointer becoming unresponsive, before finally resuming and showing up the submenu. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1666701/+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 1666863] [NEW] [unity8]kate - mouse scroll wheel doesn't work all the time
Public bug reported: ubuntu 17.04 unity8 open Kate, open the About windows (Help > About Kate), click on Authors tab, scroll up/down then click on Thanks To tab and scroll up/down with the mouse whell, it doesn't work. it's not specific to kate, i can reproduce this bug in many kde apps ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1666863 Title: [unity8]kate - mouse scroll wheel doesn't work all the time Status in Canonical System Image: New Status in qtubuntu package in Ubuntu: New Bug description: ubuntu 17.04 unity8 open Kate, open the About windows (Help > About Kate), click on Authors tab, scroll up/down then click on Thanks To tab and scroll up/down with the mouse whell, it doesn't work. it's not specific to kate, i can reproduce this bug in many kde apps To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666863/+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 1666863] Re: [unity8]kate - mouse scroll wheel doesn't work all the time
i think the focus is somehow still in the Authors tab or something like that, i see this with tiled even if i open a child window and click in a random box with scrollbars it still scrolls the previous focused in the main window o_O -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1666863 Title: [unity8]kate - mouse scroll wheel doesn't work all the time Status in Canonical System Image: New Status in qtubuntu package in Ubuntu: New Bug description: ubuntu 17.04 unity8 open Kate, open the About windows (Help > About Kate), click on Authors tab, scroll up/down then click on Thanks To tab and scroll up/down with the mouse whell, it doesn't work. it's not specific to kate, i can reproduce this bug in many kde apps To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666863/+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 1666701] Re: unity8 freezes for a second while opening a client-side submenu in kate
** Changed in: qtubuntu (Ubuntu) Assignee: (unassigned) => Daniel d'Andrada (dandrader) ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Daniel d'Andrada (dandrader) ** Changed in: qtubuntu (Ubuntu) Status: New => In Progress ** Changed in: unity8 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666701 Title: unity8 freezes for a second while opening a client-side submenu in kate Status in QtMir: Invalid Status in qtubuntu package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Steps: - Launch kate - Right-click on its main, text editor, area. A pop-up menu should show up. - Hover your mouse pointer over the "Bookmarks" menu item. A sub menu with "Set Bookmark" and "Clear All Bookmarks" options will show up. Expected outcome: The sub menu opens immediately and the mouse pointer is responsive throughout Actual outcome: unity8 freezes for a bit, with mouse pointer becoming unresponsive, before finally resuming and showing up the submenu. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1666701/+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 1666869] [NEW] QGuiApplication::layoutDirection() is always Qt::LeftToRight
Public bug reported: While working on fixing the iconprovider to load -rtl icons i saw that QGuiApplication::layoutDirection() is always Qt::LeftToRight and never changes even if the gallery layout changes to RTL, i think the layout changes are only applied to the elements rather that application. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1666869 Title: QGuiApplication::layoutDirection() is always Qt::LeftToRight Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: While working on fixing the iconprovider to load -rtl icons i saw that QGuiApplication::layoutDirection() is always Qt::LeftToRight and never changes even if the gallery layout changes to RTL, i think the layout changes are only applied to the elements rather that application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1666869/+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 1625595] Re: Libre Office Writer Icons unreadability on YY and ZZ with Intel Drivers
Tested and resolved on both 32-bit and 64-bit Kubuntu ZZ Beta 1 Images ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Fix Released ** Changed in: xorg (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1625595 Title: Libre Office Writer Icons unreadability on YY and ZZ with Intel Drivers Status in xorg package in Ubuntu: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Bug description: glxinfo | grep -i vendor server glx vendor string: SGI client glx vendor string: Mesa Project and SGI Vendor: Intel Open Source Technology Center (0x8086) OpenGL vendor string: Intel Open Source Technology Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625595/+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 1663048] Re: libmirclient in snaps gets out of sync with archive
This bug was fixed in the package unity8-desktop-session - 1.0.13+17.04.20170221-0ubuntu1 --- unity8-desktop-session (1.0.13+17.04.20170221-0ubuntu1) zesty; urgency=medium * Support connecting to mir-libs and unity8 when using unity8-snap- install. (LP: #1663048) -- Michael Terry Tue, 21 Feb 2017 16:33:17 + ** Changed in: unity8-desktop-session (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1663048 Title: libmirclient in snaps gets out of sync with archive Status in Canonical System Image: Confirmed Status in Ubuntu App Platform: In Progress Status in unity8 package in Ubuntu: In Progress Status in unity8-desktop-session package in Ubuntu: Fix Released Bug description: Because we directly include mir client libraries in the platform (due to a dependency of qtubuntu), when the mir interface is revised we get out of sync. The mir team publishes a mir-libs snap that tracks these changes and exposes a mir-libs content interface. We should investigate if that can be used transparently by apps connected to the platform. as of this report they are out of sync. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1666859] Re: keyboard navigation in app menus not working the first time it is created
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Albert Astals Cid (aacid) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666859 Title: keyboard navigation in app menus not working the first time it is created Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: * Start Kate (or any other app with nested app menus) * open some menu using the keyboard (e.g. in Kate, Alt+T for Tools) * use the keyboard to navigate down to an entry that has a submenu * press "right" => the first time such a submenu is created, the keyboard focus doesn't move to the submenu but stays in the parent menu. It works fine on the second attempt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1666859/+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 1666869] Re: Toolkit gallery doesn't change QGuiApplication::layoutDirection
** Summary changed: - QGuiApplication::layoutDirection() is always Qt::LeftToRight + Toolkit gallery doesn't change QGuiApplication::layoutDirection -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1666869 Title: Toolkit gallery doesn't change QGuiApplication::layoutDirection Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: While working on fixing the iconprovider to load -rtl icons i saw that QGuiApplication::layoutDirection() is always Qt::LeftToRight and never changes even if the gallery layout changes to RTL, i think the layout changes are only applied to the elements rather that application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1666869/+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 1666869] Re: Toolkit gallery doesn't change QGuiApplication::layoutDirection
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1666869 Title: Toolkit gallery doesn't change QGuiApplication::layoutDirection Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: While working on fixing the iconprovider to load -rtl icons i saw that QGuiApplication::layoutDirection() is always Qt::LeftToRight and never changes even if the gallery layout changes to RTL, i think the layout changes are only applied to the elements rather that application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1666869/+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 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found
For the ibus denial you need:
#include
For nvidia, you need:
#include
@{PROC}/driver/nvidia/params r,
/dev/nvidia* rw,
unix (send, receive) type=dgram peer=(addr="@nvidia[0-9a-f]*"),
(the apparmor abstraction needs to be updated for newer nvidia).
What happens if you add the above to the profile (and reload the profile
with 'sudo apparmor_parser -r /path/to/profile')?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1590561
Title:
webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
EGL configs found
Status in Canonical System Image:
Confirmed
Status in Oxide:
Confirmed
Status in webbrowser-app package in Ubuntu:
Confirmed
Bug description:
When trying to start webbrowser-app a unresponsive window appears and
after a few moments it crashes.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 8 22:56:35 2016
InstallationDate: Installed on 2016-04-28 (41 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: webbrowser-app
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590561/+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 1641017] Re: Mesa 12.0.6 - multiple important fixes, stable branch
Timo/Chris, I am still wondering why it been released only for Xenial?.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1641017 Title: Mesa 12.0.6 - multiple important fixes, stable branch Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Yakkety: Fix Committed Bug description: [Impact] Mesa 12.0.5 is now available as a point release in the stable branch. Mesa has MRE for these. The release contains multiple fixes amongst which: The nouveau vdpau driver performance has been restored. The wayland-egl module no longer crashes if the user calls eglDestroySurface and wl_egl_window_destroy in the "wrong" order. libEGL correctly advertises the EGL platforms available. Multiple fd leaks were addressed, which could prevent rmmod of devices such as the DisplayLink drivers. Radeonsi has gained noticeable performance by disabling ReZ. Interop between third party OpenCL implementations and mesa's libGL/libEGL is back online... and many more. Full changelog: https://lists.freedesktop.org/archives/mesa-dev/2016-November/135027.html I am particularly interested in the RadeonSI performance boost: https://lists.freedesktop.org/archives/mesa-dev/2016-October/131759.html In real-world tests the boost is about 20% (Yay!) : http://www.phoronix.com/scan.php?page=news_item&px=Mesa-Post-ReZ-Change-Benchmarks [Test case] Run the default desktop and maybe a game or two. This release has been tested on xenial by the certification team on a set of machines, covering: Intel Haswell Intel Broadwell Intel Skylake AMD Mobility Radeon HD 5430/5450/5470 and they all passed the tests. Once this is in -proposed, the community will be asked to test it on a wider range of devices. [Regression potential] yakkety: the release consists of cherry-picks from master, specifically selected as bugfixes. Regression potential should be low. xenial: it's a bigger bump for xenial, but since yakkety already ships with this series the risk should be low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1641017/+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 1639744] Re: lsblk does not use extended WWNs and may return the same ID for two different disks
Any news on this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1639744 Title: lsblk does not use extended WWNs and may return the same ID for two different disks Status in util-linux package in Ubuntu: New Bug description: lsblk from util-linux in xenial is affected by this bug: https://github.com/karelzak/util-linux/issues/321 This means that lsblk may return the same identifier for different devices, because it always uses the short WWN, while some devices are only identified uniquely by the full (extended) WWN. This has been fixed in upstream util-linux for a while, but the version in xenial is just a tick too old. Since the patch is less than 10 lines, maybe you would consider a backport? To my knowledge, this affects mainly "Enterprise" hardware - logical volumes on fully hardware-driven RAID controllers like HP, Dell, LSI/Avago, and logical volumes on external storage arrays addressed over iSCSI or FC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1639744/+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 1575141] Re: [Launcher] enable progressive autoscrolling for mouse interaction
** Branch linked: lp:~mzanetti/unity8/launcher-hover-scrolling -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1575141 Title: [Launcher] enable progressive autoscrolling for mouse interaction Status in unity8 package in Ubuntu: In Progress Bug description: As the title says. Progressive autoscrolling is implemented on Drag'n drop right now, but also needs to be enabled for regular mouse interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1575141/+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 1575141] Re: [Launcher] enable progressive autoscrolling for mouse interaction
** Changed in: unity8 (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1575141 Title: [Launcher] enable progressive autoscrolling for mouse interaction Status in unity8 package in Ubuntu: In Progress Bug description: As the title says. Progressive autoscrolling is implemented on Drag'n drop right now, but also needs to be enabled for regular mouse interactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1575141/+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 1666859] Re: keyboard navigation in app menus not working the first time it is created
** Branch linked: lp:~aacid/unity8/select_first_submenu_when_it_appears -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666859 Title: keyboard navigation in app menus not working the first time it is created Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: * Start Kate (or any other app with nested app menus) * open some menu using the keyboard (e.g. in Kate, Alt+T for Tools) * use the keyboard to navigate down to an entry that has a submenu * press "right" => the first time such a submenu is created, the keyboard focus doesn't move to the submenu but stays in the parent menu. It works fine on the second attempt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1666859/+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 1666701] Re: unity8 freezes for a second while opening a client-side submenu in kate
** Changed in: qtubuntu (Ubuntu) Assignee: Daniel d'Andrada (dandrader) => Albert Astals Cid (aacid) ** Changed in: unity8 (Ubuntu) Assignee: Daniel d'Andrada (dandrader) => Albert Astals Cid (aacid) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666701 Title: unity8 freezes for a second while opening a client-side submenu in kate Status in QtMir: Invalid Status in qtubuntu package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Steps: - Launch kate - Right-click on its main, text editor, area. A pop-up menu should show up. - Hover your mouse pointer over the "Bookmarks" menu item. A sub menu with "Set Bookmark" and "Clear All Bookmarks" options will show up. Expected outcome: The sub menu opens immediately and the mouse pointer is responsive throughout Actual outcome: unity8 freezes for a bit, with mouse pointer becoming unresponsive, before finally resuming and showing up the submenu. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1666701/+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 1460933] Re: VPN Connection lost after suspend / resume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1460933 Title: VPN Connection lost after suspend / resume Status in network-manager package in Ubuntu: Confirmed Bug description: When connected to a VPN and going into suspend, after resume the VPN connection is lost. Additionally, there is no indicator that tells users about not being connected to the VPN anymore. Manual reconnection, however, works without problems, but is a major annoyance. Under some circumstances this could be a life threatening security bug - e.g. if you are living in a failed Orwellian [state|world] that controls internet usage of it's inhabitants and randomly kills people that do not fit into certain criteria with drones, you should not use network manager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1460933/+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 1639896] Re: Backport support for AMD Polaris
13:17 sil2100, tjaalton: in bug 1639896, is there any thought to testing users who are on AMD but not using Polaris? 13:17 bug 1639896 in xserver-xorg-video-amdgpu (Ubuntu Xenial) "Backport support for AMD Polaris" [Undecided,Fix committed] https://launchpad.net/bugs/1639896 13:17 We don't want to regress those users accidentally, right? 13:17 For example, if the code that detected what card was in use was broken and was accidentally "always Polaris of course". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639896 Title: Backport support for AMD Polaris Status in mesa package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in mesa source package in Xenial: Fix Released Status in xserver-xorg-video-amdgpu source package in Xenial: Fix Released Bug description: [Impact] Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs. Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6 backported instead [Test case] Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration [Regression potential] This is a stable upstream release, and 16.10 ships the same versions so regression potential should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+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 1630906] Re: QML segfault on arm64 due to builder kernel change
(...and meanwhile the workarounded builder kernel not using the new setting is still required) ** Also affects: qtdeclarative-opensource-src (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: qtdeclarative-opensource-src (Ubuntu RTM) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Confirmed Status in online-accounts-api package in Ubuntu: New Status in qmenumodel package in Ubuntu: New Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in ubuntu-push-qml package in Ubuntu: New Status in unity8 package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Status in qtdeclarative-opensource-src package in Ubuntu RTM: Triaged Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+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 1639896] Re: Backport support for AMD Polaris
13:19 rbasak: all such tests use pci-id's. this adds new to support polaris 13:19 old radeons use -ati 13:20 this is for gcn1.0 and up iirc 13:20 I'm talking of "regression risk in case our understanding is wrong", not "what is our understanding". 13:21 "code that detected" is in the driver 13:21 you assume it's broken 13:22 I assume that broken-ness is unknown without some method to try to ensure that it's not. 13:22 it's in 16.10 13:22 guess we'd have heard by now 13:23 That's fair. 13:23 also on 16.04.2 13:23 Oh? 16.04.2 pulled from xenial-proposed for this package? 13:24 no, same version 13:24 x-x-v-amdgpu-hwe-16.04 13:24 xserver-xorg-video-amdgpu is 1.1.0-1 in xenial release, doesn't exist in xenial-updates and is 1.1.2-0ubuntu0.16.04.1 in xenial- proposed, now? 13:24 Oh, I see. 13:24 OK -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639896 Title: Backport support for AMD Polaris Status in mesa package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in mesa source package in Xenial: Fix Released Status in xserver-xorg-video-amdgpu source package in Xenial: Fix Released Bug description: [Impact] Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs. Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6 backported instead [Test case] Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration [Regression potential] This is a stable upstream release, and 16.10 ships the same versions so regression potential should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+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 1639896] Re: Backport support for AMD Polaris
This bug was fixed in the package xserver-xorg-video-amdgpu - 1.1.2-0ubuntu0.16.04.1 --- xserver-xorg-video-amdgpu (1.1.2-0ubuntu0.16.04.1) xenial; urgency=medium * Backport to xenial. - bugfix release - further support for Polaris (LP: #1639896) xserver-xorg-video-amdgpu (1.1.2-1) unstable; urgency=medium * New upstream release. - fix-configdir.diff: Dropped, fixed upstream [ Julien Cristau ] * Use https URL in debian/watch. xserver-xorg-video-amdgpu (1.1.1-1) unstable; urgency=medium * New upstream release. * fix-configdir.diff: Fix installing the config snippet. -- Timo Aaltonen Mon, 07 Nov 2016 20:40:47 +0200 ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639896 Title: Backport support for AMD Polaris Status in mesa package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in mesa source package in Xenial: Fix Released Status in xserver-xorg-video-amdgpu source package in Xenial: Fix Released Bug description: [Impact] Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs. Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6 backported instead [Test case] Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration [Regression potential] This is a stable upstream release, and 16.10 ships the same versions so regression potential should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+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 1639896] Update Released
The verification of the Stable Release Update for xserver-xorg-video- amdgpu has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639896 Title: Backport support for AMD Polaris Status in mesa package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in mesa source package in Xenial: Fix Released Status in xserver-xorg-video-amdgpu source package in Xenial: Fix Released Bug description: [Impact] Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs. Mesa needs a bunch of commits backported from 12.0.x. [update] 12.0.6 backported instead [Test case] Test desktop with a Polaris GPU, it should run with full 2D/3D-acceleration [Regression potential] This is a stable upstream release, and 16.10 ships the same versions so regression potential should be minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+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 1583088] Re: Randomly corrupt font / text / characters in Unity8
Here is what Qt is doing, on upload: https://code.woboq.org/qt5/qtdeclarative/src/quick/scenegraph/qsgdefaultdistancefieldglyphcache.cpp.html#158 It saves & restores the alignment, and assumes the default alignment of 4 for drawing. IMO Mir isn't playing along, as it changes the alignment but does not restore it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1583088 Title: Randomly corrupt font / text / characters in Unity8 Status in Canonical System Image: In Progress Status in Mir: Won't Fix Status in gnome-desktop package in Ubuntu: Invalid Status in mir package in Ubuntu: Won't Fix Status in qtdeclarative-opensource-src package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Bug description: Corrupted characters in text rendering. Only happens after starting non-GL application, like GTK application or mir_demo_client_fingerpaint. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1583088/+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 1666892] [NEW] [unity8] dolphin, closing one instance/window closes all
Public bug reported: ubuntu 17.04 unity8 launch dolphin, from the menu open a new window "File > New Window", now close the new window expected: first window to still be open. result all windows are closed, dolphin closed ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: qtubuntu (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: qtubuntu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666892 Title: [unity8] dolphin, closing one instance/window closes all Status in Canonical System Image: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: ubuntu 17.04 unity8 launch dolphin, from the menu open a new window "File > New Window", now close the new window expected: first window to still be open. result all windows are closed, dolphin closed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666892/+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 1666900] [NEW] avahi-autoipd fails because network interface name is too long
Public bug reported: Trying to use avahi-autoipd on a USB network interface, which gets created when I connect a USB gadget (g_ether) device (my raspberry pi zero). Avahi-autoipd fails to assign an IPv4LL address, and instead reports: # avahi-autoipd enp0s29u1u2 Found user 'avahi-autoipd' (UID 110) and group 'avahi-autoipd' (GID 120). Successfully called chroot(). Successfully dropped root privileges. Starting with address 169.254.7.125 Callout BIND, address 169.254.7.125 on interface enp0s29u1u2 client: RTNETLINK answers: Numerical result out of range Script execution failed with return value 2 Successfully claimed IP address 169.254.7.125 Although avahi-autoipd claims that the IP address gets configured, ifconfig shows that it didn't succeed. The root cause is that the label for the interface exceeds the maximum length of 15 characters. This happens in line 44 of /etc/avahi/avahi- autoipd.action: ip addr add "$3"/16 brd 169.254.255.255 label "$2:avahi" scope link dev "$2" With $2 the interface name, and $3 the IPv4LL address that it wants to claim. Interface names and label names can only be 15 characters in length, this is a kernel limitation. IF_NAMESIZE = 16, leaving 15 chars for the name, see /usr/include/net/if.h and IFNAMSIZ in the kernel includes. The rather long interface name, appended with ":avahi", exceeds this length. This results in the 'Numerical result out of range' error message. Workaround: I've edited the /etc/avahi/avahi-autopid.action script to only append ":a" for the label (lines 44 and 50) ,and in this case it works as designed. avahi-autoipd should perhaps check that the label does not exceed this limit of 15 characters. Note that the label must start with the full interface name, see ip- address(8). A more compact interface name would be helpful, as these long interface names tend to break other things as well. The kernel assigns 'usb0', but this gets changed right away. This occurs on both 16.04 and 16.10, haven't tried any other versions yet. ** Affects: avahi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1666900 Title: avahi-autoipd fails because network interface name is too long Status in avahi package in Ubuntu: New Bug description: Trying to use avahi-autoipd on a USB network interface, which gets created when I connect a USB gadget (g_ether) device (my raspberry pi zero). Avahi-autoipd fails to assign an IPv4LL address, and instead reports: # avahi-autoipd enp0s29u1u2 Found user 'avahi-autoipd' (UID 110) and group 'avahi-autoipd' (GID 120). Successfully called chroot(). Successfully dropped root privileges. Starting with address 169.254.7.125 Callout BIND, address 169.254.7.125 on interface enp0s29u1u2 client: RTNETLINK answers: Numerical result out of range Script execution failed with return value 2 Successfully claimed IP address 169.254.7.125 Although avahi-autoipd claims that the IP address gets configured, ifconfig shows that it didn't succeed. The root cause is that the label for the interface exceeds the maximum length of 15 characters. This happens in line 44 of /etc/avahi/avahi- autoipd.action: ip addr add "$3"/16 brd 169.254.255.255 label "$2:avahi" scope link dev "$2" With $2 the interface name, and $3 the IPv4LL address that it wants to claim. Interface names and label names can only be 15 characters in length, this is a kernel limitation. IF_NAMESIZE = 16, leaving 15 chars for the name, see /usr/include/net/if.h and IFNAMSIZ in the kernel includes. The rather long interface name, appended with ":avahi", exceeds this length. This results in the 'Numerical result out of range' error message. Workaround: I've edited the /etc/avahi/avahi-autopid.action script to only append ":a" for the label (lines 44 and 50) ,and in this case it works as designed. avahi-autoipd should perhaps check that the label does not exceed this limit of 15 characters. Note that the label must start with the full interface name, see ip- address(8). A more compact interface name would be helpful, as these long interface names tend to break other things as well. The kernel assigns 'usb0', but this gets changed right away. This occurs on both 16.04 and 16.10, haven't tried any other versions yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1666900/+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 1652486] Re: mesa gpu lockup
This has a couple of reverse dependency autopkgtest failures in Yakkety. I have requested retries as it isn't clear to me if they are intermittent or not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1652486 Title: mesa gpu lockup Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Released Status in mesa source package in Yakkety: Fix Committed Bug description: package: mesa version: 11.2.0-1ubuntu2.2 release: 16.04.1 / "Xenial" references: * https://bugs.freedesktop.org/show_bug.cgi?id=93649 * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3 symptoms: 1. kernel reports "GPU lockup" 2. kernel reports "GPU softreset" 3. immediately frozen display 4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 seconds." 5. computer hanging on system reboot requiring a forced power off Symptoms occur when playing Team Fortress 2. Attachments: 1. mesa source package patch 2. lspci output for video card (ie Radeon HD 7750) 3. kernel log To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1652486/+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 1666902] [NEW] Enable screencast utilities
Public bug reported: Peek is a utility to grab screencast to animated GIFs. They have an open bug to add Mir support: https://github.com/phw/peek/issues/39 Current mirscreencast util only works as root, due to Unity8 replacing the renderer with its own custom one (which does not support screenshotting yet). We need to get screencasting working for third party applications running as the user. Mediation of screencasting application is also needed - so user is aware screencast in progress. ** Affects: qtmir Importance: Undecided Status: New ** Affects: qtmir (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: unity8 (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Also affects: qtmir Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666902 Title: Enable screencast utilities Status in QtMir: New Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Peek is a utility to grab screencast to animated GIFs. They have an open bug to add Mir support: https://github.com/phw/peek/issues/39 Current mirscreencast util only works as root, due to Unity8 replacing the renderer with its own custom one (which does not support screenshotting yet). We need to get screencasting working for third party applications running as the user. Mediation of screencasting application is also needed - so user is aware screencast in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1666902/+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 1666902] Re: Enable screencast utilities
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666902 Title: Enable screencast utilities Status in QtMir: New Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Peek is a utility to grab screencast to animated GIFs. They have an open bug to add Mir support: https://github.com/phw/peek/issues/39 Current mirscreencast util only works as root, due to Unity8 replacing the renderer with its own custom one (which does not support screenshotting yet). We need to get screencasting working for third party applications running as the user. Mediation of screencasting application is also needed - so user is aware screencast in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1666902/+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 1666859] Re: keyboard navigation in app menus not working the first time it is created
** Changed in: unity8 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666859 Title: keyboard navigation in app menus not working the first time it is created Status in unity8 package in Ubuntu: In Progress Bug description: Steps to reproduce: * Start Kate (or any other app with nested app menus) * open some menu using the keyboard (e.g. in Kate, Alt+T for Tools) * use the keyboard to navigate down to an entry that has a submenu * press "right" => the first time such a submenu is created, the keyboard focus doesn't move to the submenu but stays in the parent menu. It works fine on the second attempt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1666859/+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 1666902] Re: Enable screencast utilities
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtmir (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666902 Title: Enable screencast utilities Status in QtMir: New Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Peek is a utility to grab screencast to animated GIFs. They have an open bug to add Mir support: https://github.com/phw/peek/issues/39 Current mirscreencast util only works as root, due to Unity8 replacing the renderer with its own custom one (which does not support screenshotting yet). We need to get screencasting working for third party applications running as the user. Mediation of screencasting application is also needed - so user is aware screencast in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1666902/+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 1666902] Re: Enable screencast utilities
One thing that has come up on the related Wayland discussion is the fact, that Peek uses the window positioning to obtain the recording coordinates. This is very different from e.g. the more traditional approach of Now on Wayland there is no such thing as global window coordinates, and I have read somewhere this is also the case on Mir. Is that correct? If so one way to solve this would be to allow the API to define the screenshot / screencast area relative to the window position. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666902 Title: Enable screencast utilities Status in QtMir: New Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Peek is a utility to grab screencast to animated GIFs. They have an open bug to add Mir support: https://github.com/phw/peek/issues/39 Current mirscreencast util only works as root, due to Unity8 replacing the renderer with its own custom one (which does not support screenshotting yet). We need to get screencasting working for third party applications running as the user. Mediation of screencasting application is also needed - so user is aware screencast in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1666902/+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 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface
I dig a bit around and found that this bug affects installation where
network interface is connected through USB. PCI-devices are not
affected.
Symptom: if computer suspends and resumes, 'ip link' command shows
increased interface number (1,2,3,4,...,11,etc).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
dnsmasq fails to send queries out after suspend disconnects the
interface
Status in dnsmasq package in Ubuntu:
Triaged
Bug description:
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface
Installed the patched version from #7, and it works great!
Killed the dnsmasq process and suspended/resumed twice to test it.
Dell XPS 15 9550 owner here. Just upgraded to 16.10. Never seen this bug
with 16.04, *or* with 16.04.2 (with HWE updates).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1639776
Title:
dnsmasq fails to send queries out after suspend disconnects the
interface
Status in dnsmasq package in Ubuntu:
Triaged
Bug description:
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1664947] Re: [unity8] alt drag a child window doesn't work
** Changed in: unity8 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1664947 Title: [unity8] alt drag a child window doesn't work Status in Canonical System Image: New Status in unity8 package in Ubuntu: In Progress Bug description: ubuntu 17.04 unity8 open a random app, tiled or kate or whatever, open a child window (help/about or whatever) and then try to move the window with alt left click, press alt left click inside the window and drag (move the mouse). it doesn't work. it does work with the main window To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1664947/+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 1650740] Re: dhclient depends on fstab 16.04LTS
A workaround could be to recreate /usr/lib/x86_64-linux- gnu/guestfs/supermin.d/init.tar.gz. So untar it, apply https://github.com/libguestfs/libguestfs/commit/fd60be95091a1923e108f72caf251f5549eeccd0 onto the untarred init file, compress it again and copy it back to /usr/lib/x86_64-linux-gnu/guestfs/supermin.d/init.tar.gz. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1650740 Title: dhclient depends on fstab 16.04LTS Status in isc-dhcp package in Ubuntu: Confirmed Bug description: As noted here: https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1632405 dhclient-script attempts to read fstab and if not available is unable to continue; while a workaround has been provided in the upstream for the dependent (and fairly critical) package, which will hopefully make it into the 16.04 repos soon, the bug does seem to be in dhclient- script, and presumably is easily fixable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1650740/+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 1342123] Re: evolution-calendar-factory always running with high memory usage
** Attachment added: "evolution-calendar-factory-subprocess.log" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1342123/+attachment/4824482/+files/evolution-calendar-factory-subprocess.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1342123 Title: evolution-calendar-factory always running with high memory usage Status in Canonical System Image: Confirmed Status in evolution-data-server package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: At boot the process is using over 100MB on my mako (build 129) I sync'd a fairly large set of calendar events from google previously Does this process need to be running all the time? Can we streamline it to not read so much of the data set, which it appears to be doing? With no calendar entries (i.e. removing .local/share/evolution/xxx/calendar.ics) the process still uses over 30MB (looking at RSS with ps aux --sort -rss ) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1342123/+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 1660367] Re: app drawer doesn't dismiss on selecting active (or inactive) app from launcher unity8 zesty
i fell for this again today, u-s-s is the right size to be "hidden" under the drawer ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1660367 Title: app drawer doesn't dismiss on selecting active (or inactive) app from launcher unity8 zesty Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: unsure if this is by design, but it doesn't "feel correct" on unity8(deb) zesty, installed the chrome-test snap launched chrome test along with terminal, hid chrome behind terminal moused over to reveal app drawer, selected chrome, which gained focus - but app drawer was still covering was able to repeat with unity-system-settings icon on launcher, u-s-s launched but drawer remained open. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1660367/+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 1660438] Re: display brightness & slider follows hw keys, but brightness does not follow slider unity8 zesty
** Tags added: unity8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1660438 Title: display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end Status in Canonical System Image: New Status in repowerd package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: using unity8 deb session, zesty to reproduce, reveal the "battery" indicator panel on a pc with brightness hw keys. play around intermittently with decreasing/increasing brightness with the hw keys. Then attempt to increase/decrease brightness with the slider. It becomes especially interesting when the slider & actual brightness are at their max/mins. fwiw, i was using an older dell studio laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1660438/+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 1666748] Re: Apparmor problem inside a lxd container
I'm also seeing those with my smb servers: apparmor="DENIED" operation="file_perm" namespace="root//lxd-smb_" profile="/usr/sbin/smbd" pid=15865 comm="smbd" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="---" On those I also have this: apparmor="DENIED" operation="file_inherit" namespace="root//lxd-smb_ " profile="/usr/sbin/smbd" name="/run/systemd/journal/stdout" pid=3755 comm="smbd" requested_mask="wr" denied_mask="wr" fsuid=165536 ouid=165536 I also have no clue about the above. John, is there any test kernel I could try before something more official hits -proposed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1666748 Title: Apparmor problem inside a lxd container Status in apparmor package in Ubuntu: New Bug description: I've been running /usr/sbin/sshd in a custom Apparmor profile [*] for a long time and it works well. When I loaded the same profile in a lxd container (named ganymede), it didn't work at all: apparmor="DENIED" operation="file_perm" namespace="root//lxd-ganymede_ " profile="/usr/sbin/sshd" pid=30870 comm="sshd" family="unix" sock_type="stream" protocol=0 requested_mask="send receive" denied_mask="send receive" addr=none peer_addr=none peer="---" Additional information about my environment: Both the host and the guest are up to date Xenials. root@jupiter:~# apt-cache policy linux-image-4.4.0-63-generic apparmor openssh-server linux-image-4.4.0-63-generic: Installed: 4.4.0-63.84 Candidate: 4.4.0-63.84 Version table: *** 4.4.0-63.84 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status apparmor: Installed: 2.10.95-0ubuntu2.5 Candidate: 2.10.95-0ubuntu2.5 Version table: *** 2.10.95-0ubuntu2.5 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.10.95-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages openssh-server: Installed: 1:7.2p2-4ubuntu2.1 Candidate: 1:7.2p2-4ubuntu2.1 Version table: *** 1:7.2p2-4ubuntu2.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:7.2p2-4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages *: https://github.com/simondeziel/aa-profiles/blob/4d7fbd9fcca4bd62d97e8d0ba2cdc35e8d48d096/16.04/usr.sbin.sshd ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2.5 ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44 Uname: Linux 4.4.0-63-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Feb 21 21:25:55 2017 InstallationDate: Installed on 2016-12-19 (64 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 (20161219) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-63-generic.efi.signed root=UUID=b23cf18f-e8d0-4a4f-9e8d-6aa47569e86b ro possible_cpus=2 nmi_watchdog=0 kaslr vsyscall=none transparent_hugepage=never PstreeP: Error: [Errno 2] No such file or directory: '/usr/bin/pstree' SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1666748/+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 1664947] Re: [unity8] alt drag a child window doesn't work
** Branch linked: lp:~dandrader/unity8/dragChildWithAltPress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1664947 Title: [unity8] alt drag a child window doesn't work Status in Canonical System Image: New Status in unity8 package in Ubuntu: In Progress Bug description: ubuntu 17.04 unity8 open a random app, tiled or kate or whatever, open a child window (help/about or whatever) and then try to move the window with alt left click, press alt left click inside the window and drag (move the mouse). it doesn't work. it does work with the main window To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1664947/+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 1660438] Re: display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end
ok, this bug has evolved to repro: reveal the indicator panel for battery/brightness either select drag element with mouse or choose up/down with hw brightness keys the slider position will not respond precisely, jump about & at the extremes (max/min) settings there will be flicker between what seems to be 2 different settings ** Summary changed: - display brightness & slider follows hw keys, but brightness does not follow slider unity8 zesty + display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: repowerd (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1660438 Title: display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end Status in Canonical System Image: New Status in repowerd package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: using unity8 deb session, zesty to reproduce, reveal the "battery" indicator panel on a pc with brightness hw keys. play around intermittently with decreasing/increasing brightness with the hw keys. Then attempt to increase/decrease brightness with the slider. It becomes especially interesting when the slider & actual brightness are at their max/mins. fwiw, i was using an older dell studio laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1660438/+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 1666481] Re: [unity8] kate, selecting a document tab freezes unity8 for a second, i see hight unity8 cpu usage 80% while changing tabs (documents)
*** This bug is a duplicate of bug 1666701 *** https://bugs.launchpad.net/bugs/1666701 ** This bug has been marked a duplicate of bug 1666701 unity8 freezes for a second while opening a client-side submenu in kate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666481 Title: [unity8] kate, selecting a document tab freezes unity8 for a second, i see hight unity8 cpu usage 80% while changing tabs (documents) Status in Canonical System Image: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8 deb session [unity8] kate, selecting a document tab freezes unity8 for a second, i see hight unity8 cpu usage 80% while changing tabs (documents) launch kate, create 7-8 new documents and then change from one to another by clicking the tabs, also see the unity8 cpu usage see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666481/+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 1666950] [NEW] icons in app scope unusually large, zesty u8 deb
Public bug reported: updated to the latest in zesty the icons shown in the apps scope in the dash look unusually large they appear normal in the app drawer ** Affects: canonical-devices-system-image Importance: Medium Status: New ** Affects: unity8 (Ubuntu) Importance: Medium Status: New ** Tags: unity8 ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: unity8 (Ubuntu) Importance: Undecided => Medium ** Tags added: unity8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666950 Title: icons in app scope unusually large, zesty u8 deb Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: updated to the latest in zesty the icons shown in the apps scope in the dash look unusually large they appear normal in the app drawer To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666950/+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 1665938] Re: Pagestack backAction should point to the right in RTL
** Branch linked: lp:~daker/ubuntu-ui-toolkit/fix.iconprovider-1665938 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1665938 Title: Pagestack backAction should point to the right in RTL Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The PageStack backAction should point to the right rather than the left when in RTL mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1665938/+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 1663048] Re: libmirclient in snaps gets out of sync with archive
Didier and I settled on a version of desktop-launch that tries to use mir-libs first, falling back to ubuntu-app-platform (while the libs are in there), and if not, then falling back to an internal copy of the libraries. That should help the transition and doesn't encode a requirement on mir- libs inside of desktop-launch. But should enable the use of them if the snap chooses. This has landed and now also sets LD_LIBRARY_PATH to point inside mir- libs for your snap, if mir-libs is connected. So go ahead and update your snaps. All you need to do is define the plug and create the $SNAP/mir-libs folder. Everything else should be done for you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1663048 Title: libmirclient in snaps gets out of sync with archive Status in Canonical System Image: Confirmed Status in Ubuntu App Platform: In Progress Status in unity8 package in Ubuntu: In Progress Status in unity8-desktop-session package in Ubuntu: Fix Released Bug description: Because we directly include mir client libraries in the platform (due to a dependency of qtubuntu), when the mir interface is revised we get out of sync. The mir team publishes a mir-libs snap that tracks these changes and exposes a mir-libs content interface. We should investigate if that can be used transparently by apps connected to the platform. as of this report they are out of sync. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663048/+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 1666950] Re: icons in app scope unusually large, zesty u8 deb
Yup, same in xenial fwiw -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666950 Title: icons in app scope unusually large, zesty u8 deb Status in Canonical System Image: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: updated to the latest in zesty the icons shown in the apps scope in the dash look unusually large they appear normal in the app drawer To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666950/+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 1666950] Re: icons in app scope unusually large, zesty u8 deb
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666950 Title: icons in app scope unusually large, zesty u8 deb Status in Canonical System Image: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: updated to the latest in zesty the icons shown in the apps scope in the dash look unusually large they appear normal in the app drawer To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666950/+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 1666892] Re: [unity8] dolphin, closing one instance/window closes all
In my machine dolphin doesn't quite work in a unity8 session. It complains about klauncher, so doesn't show any files in its main area. But, most importantly, "New Window" has no effect. Is there another application I can use to reproduce the bug? ** Changed in: unity8 (Ubuntu) Status: New => Incomplete ** Changed in: qtubuntu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666892 Title: [unity8] dolphin, closing one instance/window closes all Status in Canonical System Image: New Status in qtubuntu package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: ubuntu 17.04 unity8 launch dolphin, from the menu open a new window "File > New Window", now close the new window expected: first window to still be open. result all windows are closed, dolphin closed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666892/+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 1638695] Re: Python 2.7.12 performance regression
Hello, Following doko's advice, I ran a set of test with PGO & LTO optimization disabled. Here are the results : https://docs.google.com/spreadsheets/d/1tTlEOvMypwKwi99XHjvuQFE14_jpBBLy0-Mk6bjkvL0/edit#gid=1169944329 This may bring more light to the investigation as it appear that with LTO & PGO optimisation disabled on Trusty, the trusty version becomes slower than the Xenial stock version. Disabling optimisation on Xenial makes little difference though. So maybe the PGO & LTO optimisation on Trusty is more efficient than on Xenial and leads to better results,hence better performance. Just a thought -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1638695 Title: Python 2.7.12 performance regression Status in python2.7 package in Ubuntu: Confirmed Bug description: I work on the OpenStack-Ansible project and we've noticed that testing jobs on 16.04 take quite a bit longer to complete than on 14.04. They complete within an hour on 14.04 but they normally take 90 minutes or more on 16.04. We use the same version of Ansible with both versions of Ubuntu. After more digging, I tested python performance (using the 'performance' module) on 14.04 (2.7.6) and on 16.04 (2.7.12). There is a significant performance difference between each version of python. That is detailed in a spreadsheet[0]. I began using perf to dig into the differences when running the python performance module and when using Ansible playbooks. CPU migrations (as measured by perf) are doubled in Ubuntu 16.04 when running the same python workloads. I tried changing some of the kerne.sched sysctl configurables but they had very little effect on the results. I compiled python 2.7.12 from source on 14.04 and found the performance to be unchanged there. I'm not entirely sure where the problem might be now. We also have a bug open in OpenStack-Ansible[1] that provides additional detail. Thanks in advance for any help you can provide! [0] https://docs.google.com/spreadsheets/d/18MmptS_DAd1YP3OhHWQqLYVA9spC3xLt4PS3STI6tds/edit?usp=sharing [1] https://bugs.launchpad.net/openstack-ansible/+bug/1637494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1638695/+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 1666957] [NEW] Errors in the operating system
Public bug reported: Errors when running xdiagnose. Errors when playing audio and sound player. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 22 10:38:12 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0559] InstallationDate: Installed on 2016-12-28 (55 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) Lsusb: Bus 002 Device 003: ID 058f:b002 Alcor Micro Corp. Acer Integrated Webcam Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire 4743 ProcEnviron: LANGUAGE=es PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic root=UUID=98fc703b-d872-4083-9cb5-a7d8d0c4576b ro splash nopat quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2011 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.08 dmi.board.asset.tag: No Asset Tag dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.08:bd03/31/2011:svnAcer:pnAspire4743:pvrV1.08:rvnAcer:rn:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.name: Aspire 4743 dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Feb 22 03:40:17 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1666957 Title: Errors in the operating system Status in xorg package in Ubuntu: New Bug description: Errors when running xdiagnose. Errors when playing audio and sound player. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 22 10:38:12 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Core Processor Integrated Graphics Controller [1025:0559] InstallationDate: Installed on 2016-12-28 (55 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) Lsusb: Bus 002 Device 003: ID 058f:b002 Alcor Micro Corp. Acer Integrated Webcam Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Asp
[Touch-packages] [Bug 1666950] Re: icons in app scope unusually large, zesty u8 deb
We removed special casing for app scope now that it's not "the way" to show apps. ** Changed in: unity8 (Ubuntu) Status: Confirmed => Invalid ** Changed in: canonical-devices-system-image Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666950 Title: icons in app scope unusually large, zesty u8 deb Status in Canonical System Image: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: updated to the latest in zesty the icons shown in the apps scope in the dash look unusually large they appear normal in the app drawer To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666950/+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 1666980] [NEW] cannot install click, missing python files
Public bug reported: When I try to install click package, I get the following error: dpkg: click: dependency problems, but removing anyway as you requested: ubuntu-system-settings depends on click | ubuntu-snappy-cli; however: Package click is to be removed. Package ubuntu-snappy-cli is not installed. (Reading database ... 255714 files and directories currently installed.) Removing click (0.4.45.1+16.10.20160916-0ubuntu1) ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click ImportError: No module named 'click' dpkg: error processing package click (--remove): subprocess installed pre-removal script returned error exit status 1 Job for click-system-hooks.service failed because the control process exited with error code. See "systemctl status click-system-hooks.service" and "journalctl -xe" for details. click-system-hooks.service couldn't start. Errors were encountered while processing: click Script /usr/bin/click tries to import python module click, but it is missing. I suppose that this module should be included in *.deb package, but I cannot find it there. It seems that source code of required module is located here: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/vivid/click/vivid/files/head:/click/ as it contains submodule "commands" Ubuntu 16.10 click 0.4.45.1+16.10.20160916-0ubuntu1 ** Affects: click (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1666980 Title: cannot install click, missing python files Status in click package in Ubuntu: New Bug description: When I try to install click package, I get the following error: dpkg: click: dependency problems, but removing anyway as you requested: ubuntu-system-settings depends on click | ubuntu-snappy-cli; however: Package click is to be removed. Package ubuntu-snappy-cli is not installed. (Reading database ... 255714 files and directories currently installed.) Removing click (0.4.45.1+16.10.20160916-0ubuntu1) ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click ImportError: No module named 'click' dpkg: error processing package click (--remove): subprocess installed pre-removal script returned error exit status 1 Job for click-system-hooks.service failed because the control process exited with error code. See "systemctl status click-system-hooks.service" and "journalctl -xe" for details. click-system-hooks.service couldn't start. Errors were encountered while processing: click Script /usr/bin/click tries to import python module click, but it is missing. I suppose that this module should be included in *.deb package, but I cannot find it there. It seems that source code of required module is located here: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/vivid/click/vivid/files/head:/click/ as it contains submodule "commands" Ubuntu 16.10 click 0.4.45.1+16.10.20160916-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1666980/+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 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
I'm experiencing the same issue: Dell XPS 13 Developer Edition BIOS v1.3.2 Ubuntu 16.04 spike@blackhole:~$ uname -a Linux blackhole 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux spike@blackhole:~$ apt search alsa-base Sorting... Done Full Text Search... Done alsa-base/xenial,xenial,now 1.0.25+dfsg-0ubuntu5 all [installed] ALSA driver configuration files -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1665795] Re: apport-gtk crashes when removing app from unity launcher by dragging
*** This bug is a duplicate of bug 1552577 *** https://bugs.launchpad.net/bugs/1552577 ** This bug has been marked a duplicate of bug 1552577 apport-gtk crashed with SIGSEGV -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1665795 Title: apport-gtk crashes when removing app from unity launcher by dragging Status in apport package in Ubuntu: New Bug description: Removal using Unlock from Launcher option in menu failed first, so then I tried dragging to remove which resulted in the crash. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: apport-gtk 2.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-5.7+IntelAtom-linuxium 4.10.0-rc6 Uname: Linux 4.10.0-5-linuxium x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Feb 17 17:17:50 2017 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2017-02-17 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" Linuxium - Alpha (20170127) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f4d82635889:mov(%rbx),%rdi PC (0x7f4d82635889) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1665795/+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 1661209] Re: crashes when trying to upload avahi report from #1661205
It's worth noting that ProcEnviron and UserGroups are both empty. ** Changed in: apport (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1661209 Title: crashes when trying to upload avahi report from #1661205 Status in apport package in Ubuntu: New Bug description: In bug #1661205 avahi-dameon repeatedly crashes, and causes apport to go into an infinite loop. However I suspect this is a problem with apport, because when I manually unpack the .crash I get: # apport-unpack /var/crash/_usr_sbin_avahi-daemon.0.crash /home/redacted/foo Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['ProcEnviron', 'UserGroups'] has no binary content Please find attached /var/crash/_usr_sbin_avahi-daemon.0.crash ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apport 2.20.3-0ubuntu8.2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashReports: 640:0:122:14612:2017-02-02 10:48:08.638081761 +:2017-02-02 10:48:08.638081761 +:/var/crash/_usr_bin_apport-unpack.0.crash 640:0:122:1355374:2017-02-02 10:42:53.922800121 +:2017-02-02 10:48:08.582079751 +:/var/crash/_usr_sbin_avahi-daemon.0.crash CurrentDesktop: Unity Date: Thu Feb 2 10:51:34 2017 InstallationDate: Installed on 2016-10-31 (93 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1661209/+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 1666993] [NEW] Make all drop downs / Lists searchable
Public bug reported: Sometimes I encounter a list, like "Display Language" and immediate get annoyed, when the only way to get to my item (in this case country) by scrolling, especially if it is a long list. Every list should be searchable via an input field ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666993 Title: Make all drop downs / Lists searchable Status in unity8 package in Ubuntu: New Bug description: Sometimes I encounter a list, like "Display Language" and immediate get annoyed, when the only way to get to my item (in this case country) by scrolling, especially if it is a long list. Every list should be searchable via an input field To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1666993/+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 1641236] Re: Confined processes inside container cannot fully access host pty device passed in by lxc exec
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1641236 Title: Confined processes inside container cannot fully access host pty device passed in by lxc exec Status in apparmor package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Bug description: Now that AppArmor policy namespaces and profile stacking is in place, I noticed odd stdout buffering behavior when running confined processes via lxc exec. Much more data stdout data is buffered before getting flushed when the program is confined by an AppArmor profile inside of the container. I see that lxd is calling openpty(3) in the host environment, using the returned fd as stdout, and then executing the command inside of the container. This results in an AppArmor denial because the file descriptor returned by openpty(3) originates outside of the namespace used by the container. The denial is likely from glibc calling fstat(), from inside the container, on the file descriptor associated with stdout to make a decision on how much buffering to use. The fstat() is denied by AppArmor and glibc ends up handling the buffering differently than it would if the fstat() would have been successful. Steps to reproduce (using an up-to-date 16.04 amd64 VM): Create a 16.04 container $ lxc launch ubuntu-daily:16.04 x Run tcpdump in one terminal and generate traffic in another terminal (wget google.com) $ lxc exec x -- tcpdump -i eth0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 47 packets captured 48 packets received by filter 1 packet dropped by kernel Note that everything above was printed immediately because it was printed to stderr. , which is printed to stdout, was not printed until you pressed ctrl-c and the buffers were flushed thanks to the program terminating. Also, this AppArmor denial shows up in the logs: audit: type=1400 audit(1478902710.025:440): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-x_" profile="/usr/sbin/tcpdump" name="dev/pts/12" pid=15530 comm="tcpdump" requested_mask="r" denied_mask="r" fsuid=165536 ouid=165536 Now run tcpdump unconfined and take note that is printed immediately, before you terminate tcpdump. Also, there are no AppArmor denials. $ lxc exec x -- aa-exec -p unconfined -- tcpdump -i eth0 ... Now run tcpdump confined but in lxc exec's non-interactive mode and note that is printed immediately and no AppArmor denials are present. (Looking at the lxd code in lxd/container_exec.go, openpty(3) is only called in interactive mode) $ lxc exec x --mode=non-interactive -- tcpdump -i eth0 ... Applications that manually call fflush(stdout) are not affected by this as manually flushing stdout works fine. The problem seems to be caused by glibc not being able to fstat() the /dev/pts/12 fd from the host's namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1641236/+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 1666994] [NEW] Screen flicker on Dell XPS 13 9360 Developer Edition
Public bug reported: I get a periodic screen flicker across the top of the screen when using the mouse in that area. Otherwise, no other issues like blank screening, corruption, or the like. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 22 10:43:56 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:075b] InstallationDate: Installed on 2017-02-04 (17 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed root=UUID=ac2cc55d-dbc1-4ba0-90bb-8ab1d985e80f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Feb 22 09:14:10 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5194 vendor SHP xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1666994 Title: Screen flicker on Dell XPS 13 9360 Developer Edition Status in xorg package in Ubuntu: New Bug description: I get a periodic screen flicker across the top of the screen when using the mouse in that area. Otherwise, no other issues like blank screening, corruption, or the like. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Feb 22 10:43:56 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:075b] InstallationDate: Installed on 2017-02-04 (17 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. XPS 13 9360 ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.e
[Touch-packages] [Bug 1657567] Re: "Content-Range: */" on non-416 responses considered invalid
Queued for 1.2.20: https://github.com/Debian/apt/compare/1.2.19...julian- klode:1.2.y?expand=1 Queued for 1.3.5: https://github.com/Debian/apt/compare/1.3.4...julian- klode:1.3.y?expand=1 ** Also affects: apt (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: apt (Ubuntu Yakkety) Status: New => Triaged -- 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/1657567 Title: "Content-Range: */" on non-416 responses considered invalid Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Bug description: APT only allows Content-Range: */ to be specified on a 416 response. Sourceforge sometimes replies with that in a 302 redirect. We should probably just accept and silently ignore that content-range field for other values. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657567/+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 1657440] Re: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated
Queued for 1.2.20: https://github.com/Debian/apt/compare/1.2.19...julian- klode:1.2.y?expand=1 Queued for 1.3.5: https://github.com/Debian/apt/compare/1.3.4...julian- klode:1.3.y?expand=1 -- 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/1657440 Title: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Bug description: # apt --version apt 1.2.18 (amd64) xenial I got myself into a situation where a repository has a Release and a Release.gpg file, but apt is just ignoring the gpg one and won't download it via apt update for some reason: The repository in question is http://ubuntu- cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See how locally I have just the Release file: root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release* -rw-r--r-- 1 root root 100K Jan 15 18:03 archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease -rw-r--r-- 1 root root 242K Apr 21 2016 archive.ubuntu.com_ubuntu_dists_xenial_InRelease -rw-r--r-- 1 root root 100K Jan 18 11:42 archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease -rw-r--r-- 1 root root 100K Jan 18 11:42 security.ubuntu.com_ubuntu_dists_xenial-security_InRelease -rw-r--r-- 1 root root 7.7K Jan 18 11:45 ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a "Get:": root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton InRelease Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton Release Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton Release.gpg [543 B] Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease Fetched 205 kB in 0s (395 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 8 packages can be upgraded. Run 'apt list --upgradable' to see them. And I can't install packages: root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: python3-setuptools The following packages will be upgraded: dh-python dnsmasq-base python-pkg-resources python-setuptools python3-cryptography python3-pkg-resources python3-requests python3-urllib3 8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 1,193 kB of archives. After this operation, 808 kB of additional disk space will be used. Do you want to continue? [Y/n] WARNING: The following packages cannot be authenticated! dh-python dnsmasq-base python-setuptools python-pkg-resources python3-pkg-resources python3-setuptools python3-cryptography python3-requests python3-urllib3 Install these packages without verification? [y/N] n E: Some packages could not be authenticated root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# Somehow apt is thinking it has the Release.gpg file, but it doesn't? This server is behind a squid proxy. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1657440/+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 1645815] Re: apt install of local debs does not tab-complete
Queued for 1.2.20: https://github.com/Debian/apt/compare/1.2.19...julian- klode:1.2.y?expand=1 Queued for 1.3.5: https://github.com/Debian/apt/compare/1.3.4...julian- klode:1.3.y?expand=1 ** Also affects: apt (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: apt (Ubuntu Yakkety) Status: New => Triaged -- 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/1645815 Title: apt install of local debs does not tab-complete Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Bug description: this fails: $ touch xyzzy.deb $ apt install xyzzy because the completion support for install is using _filedir wrong. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.15 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 29 17:51:57 2016 InstallationDate: Installed on 2016-07-05 (147 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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/1645815/+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 1660438] Re: display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end
also, just noticed, if i rapidly hit hw key, i get the odd flicker between settings...if i go very slow, i don't get the flicker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1660438 Title: display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end Status in Canonical System Image: New Status in repowerd package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: using unity8 deb session, zesty to reproduce, reveal the "battery" indicator panel on a pc with brightness hw keys. play around intermittently with decreasing/increasing brightness with the hw keys. Then attempt to increase/decrease brightness with the slider. It becomes especially interesting when the slider & actual brightness are at their max/mins. fwiw, i was using an older dell studio laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1660438/+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 1660438] Re: display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end
added a log per request look for "kg marker" i made sure to go to the minimum and keep pressing minimum and got the flicker. The file also has all the other scenarios i saw earlier before the "kg marker" And i also noticed that it's constantly spewing handle_user_activity_changing_power_state handle_user_activity_extending_power_state back to back...like every second or so. definitely not optimal. ** Attachment added: "repowerd.log" https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1660438/+attachment/4824673/+files/repowerd.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1660438 Title: display brightness & slider follows hw keys or mousing, but jumps about & brightness flickers at low end Status in Canonical System Image: New Status in repowerd package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: using unity8 deb session, zesty to reproduce, reveal the "battery" indicator panel on a pc with brightness hw keys. play around intermittently with decreasing/increasing brightness with the hw keys. Then attempt to increase/decrease brightness with the slider. It becomes especially interesting when the slider & actual brightness are at their max/mins. fwiw, i was using an older dell studio laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1660438/+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 1666993] Re: Make all drop downs / Lists searchable
This sounds more like a UITK issue than unity8. Unity8 does, however, have a "Language" list in the wizard. The problem with searching through that is how do you type a language name unless you have already set up your input method to the language? It might work for latin alphabets, but it won't for no other. ** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: New => Incomplete ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666993 Title: Make all drop downs / Lists searchable Status in Ubuntu UX: New Status in ubuntu-ui-toolkit package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Sometimes I encounter a list, like "Display Language" and immediate get annoyed, when the only way to get to my item (in this case country) by scrolling, especially if it is a long list. Every list should be searchable via an input field To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1666993/+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 1667014] Re: If no pixel format is set for a window it hangs when requesting a buffer
** Summary changed: - If not pixel format is set for a window it hangs when requesting a buffer + If no pixel format is set for a window it hangs when requesting a buffer ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Kevin DuBois (kdub) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1667014 Title: If no pixel format is set for a window it hangs when requesting a buffer Status in Mir: New Status in mir package in Ubuntu: New Bug description: If no pixel format is set when creating a window the request for a buffer hangs. An example would be to comment out setting the pixel format in eglapp.c then running any egl client demo. http://paste.ubuntu.com/24047858/ To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1667014/+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 1666469] Re: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes
Just tried with calculator. It does set seem to be setting a minimum and a maximum width with the same value since I cannot resize it horizontally. And vertically, I can only enlarge it but not shrink beyond its original size. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666469 Title: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: unitu 17.04 unity8 deb session [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes open a random app, open a child window (help>about or whatever), resize the window as small as it's allowed. see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666469/+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 1666469] Re: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes
I guess the bug is really that those child dialogs shouldn't be resizable in the first place, like in Unity 7, right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666469 Title: [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: unitu 17.04 unity8 deb session [unity8] child windows don't have a minimum size, you can resize the windows to ludicrous sizes open a random app, open a child window (help>about or whatever), resize the window as small as it's allowed. see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1666469/+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 1582364] Re: Failure to reset devices.list on LXC privileged containers on Xenial
>From my current experience on Ubuntu 16.10 and LXC managed by Proxmox with Neo4j: + The service starts but does not create listening sockets after the initial run, when the /etc/neo4j/neo4j.conf configuration is changed to the following below: neo4j.conf >> ++ dbms.connectors.default_listen_address=0.0.0.0 root@neo4j-nmap:~# service neo4j status * neo4j.service - LSB: Neo4j Graph Database server Loaded: loaded (/etc/init.d/neo4j; generated; vendor preset: enabled) Active: active (exited) since Fri 2017-02-17 04:24:15 UTC; 5 days ago Docs: man:systemd-sysv-generator(8) Process: 486 ExecStart=/etc/init.d/neo4j start (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/neo4j.service Feb 17 04:24:15 neo4j-nmap systemd[1]: neo4j.service: Failed to reset devices.list: Operation n Feb 17 04:24:15 neo4j-nmap systemd[1]: Starting LSB: Neo4j Graph Database server... Feb 17 04:24:15 neo4j-nmap neo4j[486]: Starting Neo4j. Feb 17 04:24:15 neo4j-nmap neo4j[486]: WARNING: Max 1024 open files allowed, minimum of 4 r Feb 17 04:24:15 neo4j-nmap neo4j[486]: Started neo4j (pid 579). By default, it is available at Feb 17 04:24:15 neo4j-nmap neo4j[486]: There may be a short delay until the server is ready. Feb 17 04:24:15 neo4j-nmap neo4j[486]: See /var/log/neo4j/neo4j.log for current status. Feb 17 04:24:15 neo4j-nmap systemd[1]: Started LSB: Neo4j Graph Database server. Feb 17 04:38:44 neo4j-nmap systemd[1]: neo4j.service: Failed to reset devices.list: Operation n root@neo4j-nmap:~# netstat -ant|grep LISTEN tcp0 0 0.0.0.0:53550.0.0.0:* LISTEN tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp0 0 127.0.0.1:250.0.0.0:* LISTEN tcp6 0 0 :::5355 :::*LISTEN tcp6 0 0 :::22 :::*LISTEN tcp6 0 0 ::1:25 :::*LISTEN -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1582364 Title: Failure to reset devices.list on LXC privileged containers on Xenial Status in lxc package in Ubuntu: Invalid Bug description: I created a privilege container on Xenial using command "sudo lxc- create -n test-privilege -t ubuntu", and container hits failed to reset devices.list errors for every boot: root@psyduck-maas20:/var/lib/lxc# sudo lxc-start -n test-privilege -F systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) Detected virtualization lxc. Detected architecture x86-64. Welcome to Ubuntu 16.04 LTS! Set hostname to . Failed to install release agent, ignoring: No such file or directory [ OK ] Reached target Swap. [ OK ] Listening on Syslog Socket. Failed to reset devices.list on /system.slice: Operation not permitted [ OK ] Created slice System Slice. Failed to reset devices.list on /system.slice/system-getty.slice: Operation not permitted [ OK ] Created slice system-getty.slice. [ OK ] Reached target Encrypted Volumes. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on Journal Socket. Failed to reset devices.list on /system.slice/dev-hugepages.mount: Operation not permitted Mounting Huge Pages File System... Failed to reset devices.list on /system.slice/systemd-journald.service: Operation not permitted Starting Journal Service... Failed to reset devices.list on /system.slice/resolvconf.service: Operation not permitted Starting Nameserver information manager... Failed to reset devices.list on /system.slice/systemd-remount-fs.service: Operation not permitted Starting Remount Root and Kernel File Systems... [ OK ] Started Dispatch Password Requests to Console Directory Watch. Failed to reset devices.list on /system.slice/system-container\x2dgetty.slice: Operation not permitted [ OK ] Created slice system-container\x2dgetty.slice. [ OK ] Reached target Slices. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Reached target Sockets. Failed to reset devices.list on /system.slice/dev-lxc-tty4.mount: Operation not permitted Failed to reset devices.list on /system.slice/sys-kernel-debug.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-lxc-tty2.mount: Operation not permitted Failed to
[Touch-packages] [Bug 1582364] Re: Failure to reset devices.list on LXC privileged containers on Xenial
Update: the listening ports are created if you specify a specific address root@neo4j-nmap:~# netstat -ant|grep LISTEN tcp0 0 0.0.0.0:53550.0.0.0:* LISTEN tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp0 0 127.0.0.1:250.0.0.0:* LISTEN tcp6 0 0 10.0.1.211:7687 :::*LISTEN tcp6 0 0 :::5355 :::*LISTEN tcp6 0 0 10.0.1.211:7473 :::*LISTEN tcp6 0 0 10.0.1.211:7474 :::*LISTEN tcp6 0 0 :::22 :::*LISTEN tcp6 0 0 ::1:25 :::*LISTEN -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1582364 Title: Failure to reset devices.list on LXC privileged containers on Xenial Status in lxc package in Ubuntu: Invalid Bug description: I created a privilege container on Xenial using command "sudo lxc- create -n test-privilege -t ubuntu", and container hits failed to reset devices.list errors for every boot: root@psyduck-maas20:/var/lib/lxc# sudo lxc-start -n test-privilege -F systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) Detected virtualization lxc. Detected architecture x86-64. Welcome to Ubuntu 16.04 LTS! Set hostname to . Failed to install release agent, ignoring: No such file or directory [ OK ] Reached target Swap. [ OK ] Listening on Syslog Socket. Failed to reset devices.list on /system.slice: Operation not permitted [ OK ] Created slice System Slice. Failed to reset devices.list on /system.slice/system-getty.slice: Operation not permitted [ OK ] Created slice system-getty.slice. [ OK ] Reached target Encrypted Volumes. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on Journal Socket. Failed to reset devices.list on /system.slice/dev-hugepages.mount: Operation not permitted Mounting Huge Pages File System... Failed to reset devices.list on /system.slice/systemd-journald.service: Operation not permitted Starting Journal Service... Failed to reset devices.list on /system.slice/resolvconf.service: Operation not permitted Starting Nameserver information manager... Failed to reset devices.list on /system.slice/systemd-remount-fs.service: Operation not permitted Starting Remount Root and Kernel File Systems... [ OK ] Started Dispatch Password Requests to Console Directory Watch. Failed to reset devices.list on /system.slice/system-container\x2dgetty.slice: Operation not permitted [ OK ] Created slice system-container\x2dgetty.slice. [ OK ] Reached target Slices. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Reached target Sockets. Failed to reset devices.list on /system.slice/dev-lxc-tty4.mount: Operation not permitted Failed to reset devices.list on /system.slice/sys-kernel-debug.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-lxc-tty2.mount: Operation not permitted Failed to reset devices.list on /system.slice/-.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-lxc-tty1.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-mqueue.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-lxc-tty3.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-diskstats.mount: Operation not permitted Failed to reset devices.list on /system.slice/sys-fs-fuse-connections.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-meminfo.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-uptime.mount: Operation not permitted Failed to reset devices.list on /system.slice/sys-devices-virtual-net.mount: Operation not permitted Failed to reset devices.list on /system.slice/dev-lxc-console.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-sys-net.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-swaps.mount: Operation not permitted Failed to reset devices.list on /system.slice/proc-sysrq\x2dtrigger.mount: Operation not permitted Fa
[Touch-packages] [Bug 1667016] Re: tcpdump in lxd container: apparmor blocks writing to stdout/stderr
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1667016 Title: tcpdump in lxd container: apparmor blocks writing to stdout/stderr Status in apparmor package in Ubuntu: Confirmed Bug description: [ubuntu 16.04, lxd 2.0.8 or 2.0.9, tcpdump 4.7.4 or 4.9.0] If you ssh into an lxd container as a normal user, and inside that container run "sudo tcpdump", the tcpdump process is blocked from writing to stdout/stderr. This appears to be due to apparmor: disabling apparmor for tcpdump makes the problem go away. ln -s /etc/apparmor.d/usr.sbin.tcpdump /etc/apparmor.d/disable/ Note: this is a different bug from #1641236. In that bug, the user did "lxc exec bash" to get a shell in the container; the stdout fd was being passed from the outer host to the container. But in this case, the pty is being created entirely inside the container by sshd. Details copied from https://github.com/lxc/lxd/issues/2930 # Steps to reproduce 1. Create two Ubuntu 16.04 lxd containers, one privileged, one not. 2. ssh into each one, and then use `sudo -s` to get root. (Do not use `lxc exec` because of issue #1641236) 3. Inside one run `tcpdump -i eth0 -nn not tcp port 22`, and ping from the other. tcpdump in the privileged container works just fine. tcpdump in the unprivileged container does not show any output. But if I run strace on it I see errors attempting to access stdout and stderr: ~~~ ioctl(1, TCGETS, 0x7fff97c8d680)= -1 ENOTTY (Inappropriate ioctl for device) ... write(2, "tcpdump: verbose output suppress"..., 75) = -1 EACCES (Permission denied) write(2, "listening on eth0, link-type EN1"..., 74) = -1 EACCES (Permission denied) ~~~ This is very weird. Even more weird: the following command *does* capture packets: ~~~ tcpdump -i eth0 -nn -w foo.pcap ~~~ The file foo.pcap grows. This proves it's nothing to do with network capture perms. But the following command shows no output: ~~~ tcpdump -r foo.pcap -nn ~~~ And again it's because it can't write to stdout: ~~~ fstat(1, 0x7ffe2fb5eb10)= -1 EACCES (Permission denied) read(3, "", 4096) = 0 write(1, "14:34:30.618180 IP6 fe80::c609:6"..., 1740) = -1 EACCES (Permission denied) ~~~ I had originally thought this was to do with capabilities. But if I run `capsh --print` inside both containers, they both have `cap_net_raw` and `cap_net_admin`. In fact, the unprivileged container has two additional capabilities! (`cap_mac_override` and `cap_mac_admin`) So now I suspect that apparmor is at fault. dmesg dmesg output generated by the following steps: * start tcpdump * wait 5 seconds * send 1 ping from other side * wait 5 seconds * stop tcpdump ~~~ [429020.685987] audit: type=1400 audit(1487774339.708:3597): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.686000] audit: type=1400 audit(1487774339.708:3598): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.686013] audit: type=1400 audit(1487774339.708:3599): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.686022] audit: type=1400 audit(1487774339.708:3600): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.716725] device eth0 entered promiscuous mode [429020.741308] audit: type=1400 audit(1487774339.764:3601): apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="w" denied_mask="w" fsuid=10 ouid=0 [429020.741330] audit: type=1400 audit(1487774339.764:3602): apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="w" denied_mask="w" fsuid=10 ouid=0 [429021.716785] audit: type=1400 audit(1487774340.740:3603): apparmor="DENIED" operation="g
[Touch-packages] [Bug 1667016] [NEW] tcpdump in lxd container: apparmor blocks writing to stdout/stderr
Public bug reported: [ubuntu 16.04, lxd 2.0.8 or 2.0.9, tcpdump 4.7.4 or 4.9.0] If you ssh into an lxd container as a normal user, and inside that container run "sudo tcpdump", the tcpdump process is blocked from writing to stdout/stderr. This appears to be due to apparmor: disabling apparmor for tcpdump makes the problem go away. ln -s /etc/apparmor.d/usr.sbin.tcpdump /etc/apparmor.d/disable/ Note: this is a different bug from #1641236. In that bug, the user did "lxc exec bash" to get a shell in the container; the stdout fd was being passed from the outer host to the container. But in this case, the pty is being created entirely inside the container by sshd. Details copied from https://github.com/lxc/lxd/issues/2930 # Steps to reproduce 1. Create two Ubuntu 16.04 lxd containers, one privileged, one not. 2. ssh into each one, and then use `sudo -s` to get root. (Do not use `lxc exec` because of issue #1641236) 3. Inside one run `tcpdump -i eth0 -nn not tcp port 22`, and ping from the other. tcpdump in the privileged container works just fine. tcpdump in the unprivileged container does not show any output. But if I run strace on it I see errors attempting to access stdout and stderr: ~~~ ioctl(1, TCGETS, 0x7fff97c8d680)= -1 ENOTTY (Inappropriate ioctl for device) ... write(2, "tcpdump: verbose output suppress"..., 75) = -1 EACCES (Permission denied) write(2, "listening on eth0, link-type EN1"..., 74) = -1 EACCES (Permission denied) ~~~ This is very weird. Even more weird: the following command *does* capture packets: ~~~ tcpdump -i eth0 -nn -w foo.pcap ~~~ The file foo.pcap grows. This proves it's nothing to do with network capture perms. But the following command shows no output: ~~~ tcpdump -r foo.pcap -nn ~~~ And again it's because it can't write to stdout: ~~~ fstat(1, 0x7ffe2fb5eb10)= -1 EACCES (Permission denied) read(3, "", 4096) = 0 write(1, "14:34:30.618180 IP6 fe80::c609:6"..., 1740) = -1 EACCES (Permission denied) ~~~ I had originally thought this was to do with capabilities. But if I run `capsh --print` inside both containers, they both have `cap_net_raw` and `cap_net_admin`. In fact, the unprivileged container has two additional capabilities! (`cap_mac_override` and `cap_mac_admin`) So now I suspect that apparmor is at fault. dmesg dmesg output generated by the following steps: * start tcpdump * wait 5 seconds * send 1 ping from other side * wait 5 seconds * stop tcpdump ~~~ [429020.685987] audit: type=1400 audit(1487774339.708:3597): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.686000] audit: type=1400 audit(1487774339.708:3598): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.686013] audit: type=1400 audit(1487774339.708:3599): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.686022] audit: type=1400 audit(1487774339.708:3600): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.716725] device eth0 entered promiscuous mode [429020.741308] audit: type=1400 audit(1487774339.764:3601): apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="w" denied_mask="w" fsuid=10 ouid=0 [429020.741330] audit: type=1400 audit(1487774339.764:3602): apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="w" denied_mask="w" fsuid=10 ouid=0 [429021.716785] audit: type=1400 audit(1487774340.740:3603): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="r" denied_mask="r" fsuid=10 ouid=0 [429030.630448] audit: type=1400 audit(1487774349.652:3604): apparmor="DENIED" operation="file_perm" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="w" denied_mask="w" fsuid=10 ouid=0 [429030.630543]
