[Touch-packages] [Bug 264144] Re: NetworkManager VPN configuration export does not work
I confirm this issue in 16.04 x64 -- 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/264144 Title: NetworkManager VPN configuration export does not work Status in NetworkManager: Invalid Status in NetworkManager-OpenVPN: Fix Released Status in network-manager package in Ubuntu: Invalid Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager-pptp package in Ubuntu: Triaged Bug description: Intrepid, network-manager: 0.7~~svn20080818t061112+eni0-0ubuntu1 Subject says it. To reproduce: 1. Configure VPN connection 2. Try to Export it to a file As a result I got cryptic error message dialog: === Cannot export VPN connection The VPN connection 'vpn_test' could not be exported to vpn_test (pptp).conf. Error: unknown error. === Expected behavior: Configuration saved to a file. = WORKAROUND The configuration is saved in a file in /etc/NetworkManager/system-connections/ that has the same name as the connection. This file can be examined with a text editor and/or copied around to other machines. source: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/264144/comments/27 WORKAROUND = To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/264144/+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 1671361] [NEW] The time slider in Clementine is not functional.
Public bug reported: Log out does not work either. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Mar 9 01:33:09 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-38-generic, x86_64: installed bbswitch, 0.8, 4.8.0-39-generic, x86_64: installed bbswitch, 0.8, 4.8.0-41-generic, x86_64: installed nvidia-340, 340.102, 4.8.0-39-generic, x86_64: installed nvidia-340, 340.102, 4.8.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215 [GeForce GT 240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215 [GeForce GT 240] [1043:8326] InstallationDate: Installed on 2017-02-21 (15 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: MSI MS-7793 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=3b007a63-0336-4bb3-a9a5-a197b7458240 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FM2-A85XA-G43 (MS-7793) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.6:bd02/12/2015:svnMSI:pnMS-7793:pvr2.0:rvnMSI:rnFM2-A85XA-G43(MS-7793):rvr2.0:cvnToBeFilledByO.E.M.:ct3:cvr2.0: dmi.product.name: MS-7793 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Thu Mar 9 01:10:32 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHESEN PS2 to USB Converter KEYBOARD, id 8 inputCHESEN PS2 to USB Converter KEYBOARD, id 9 inputLive! Cam Chat HD VF0790 KEYBOARD, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1671361 Title: The time slider in Clementine is not functional. Status in xorg package in Ubuntu: New Bug description: Log out does not work either. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 BootLog: CompizPlugins: No value set
[Touch-packages] [Bug 1618988] Re: unity8 goes to black screen 'n freeze after logout attempt
*** This bug is a duplicate of bug 1535297 *** https://bugs.launchpad.net/bugs/1535297 ** This bug has been marked a duplicate of bug 1535297 Unity8 reliably crashes on logout due to heap corruption (libprotobuf.so.9 called from libprotobuf-lite.so.9), causing delays while it dumps core and reports errors. -- 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/1618988 Title: unity8 goes to black screen 'n freeze after logout attempt Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Expired Bug description: as in subject header ... when logging out of unity8 it will go to blackspace and freeze. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160826-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13 Uname: Linux 4.4.0-25-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 31 13:09:15 2016 InstallationDate: Installed on 2016-08-31 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160616) SourcePackage: unity8 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/1618988/+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 1509622] Re: Xorg crash
Thomas Mayer (thomas303), it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal: ubuntu-bug xorg Also, please feel free to subscribe me to it. For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs. ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- 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/1509622 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: This is the full apport data from the crash reported as bug #1507461. It occurred whilst watching a full-screen Flash video in Google Chrome. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 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 CurrentDesktop: Unity Date: Sat Oct 24 18:04:11 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21fa] MachineType: LENOVO CTO ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/peleg0-lv01 ro splash quiet nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET33WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Oct 24 17:58:31 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622/+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 1502057] Re: Logout from Unity8 on wily desktop takes a very long time (~30sec of black screen)
*** This bug is a duplicate of bug 1535297 *** https://bugs.launchpad.net/bugs/1535297 ** This bug has been marked a duplicate of bug 1535297 Unity8 reliably crashes on logout due to heap corruption (libprotobuf.so.9 called from libprotobuf-lite.so.9), causing delays while it dumps core and reports errors. -- 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/1502057 Title: Logout from Unity8 on wily desktop takes a very long time (~30sec of black screen) Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: Logout from Unity8 on wily desktop takes a very long time (~30sec of black screen) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502057/+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] Re: Screen flicker on Dell XPS 13 9360 Developer Edition
spike speigel, thank you for reporting this and helping make Ubuntu better. To see if this is already resolved in Ubuntu, could you please test the enablement stack via https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the results? ** This bug is no longer a duplicate of bug 1586539 Major screen flickering in Chromium and Google Chrome ** Tags added: latest-bios-1.3.2 ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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: Incomplete 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.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1666994/+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 1667352] Re: SDL apps either "Failed to connect to the mir server: std::bad_alloc" or crash in protobuf via mir_connect_sync
** Summary changed: - SDL apps "Failed to connect to the mir server: std::bad_alloc" or crash in google::protobuf::MessageLite::InternalSerializeWithCachedSizesToArray from mir_connect_sync + SDL apps either "Failed to connect to the mir server: std::bad_alloc" or crash in protobuf via mir_connect_sync ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Triaged ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Stephen M. Webb (bregma) ** Changed in: canonical-devices-system-image Milestone: None => u8c-1 ** Summary changed: - SDL apps either "Failed to connect to the mir server: std::bad_alloc" or crash in protobuf via mir_connect_sync + SDL apps either "Failed to connect to the mir server: ..." or crash in protobuf via mir_connect_sync ** Summary changed: - SDL apps either "Failed to connect to the mir server: ..." or crash in protobuf via mir_connect_sync + SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync ** Changed in: canonical-devices-system-image Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1667352 Title: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync Status in Canonical System Image: In Progress Status in Mir: In Progress Status in Mir 0.26 series: Triaged Status in libsdl2 package in Ubuntu: Confirmed Status in neverball package in Ubuntu: Invalid Status in protobuf package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8, trying to run neverball game Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting ubuntu-app-launch-application-legacy-neverball-1487864803635991.service... Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL (Failed to connect to the mir server: std::bad_alloc) Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main process exited, code=exited, status=1/FAI Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start ubuntu-app-launch-application-legacy-neverball-1487864803635991.service. Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit entered failed state. Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle
** Changed in: xorg (Ubuntu) Status: Incomplete => New -- 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/1434351 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: New Bug description: After a suspend/resume cycle, the screen comes up normally, but every time I move my mouse over a piece of text, button, widget, etc, the text vanishes and it's replaced by a plain rectangle. This does not affect xterm, but it does affect any GTK apps, firefox, etc. xfce-panel vanishes, although it's still responding to mouse-clicks. Newly opened menus are grey rectangles. The lines underlining menu hotkeys do NOT disappear. In the attached screenshot, you can clearly see which buttons I have waved the mouse over, and which I have not. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 19:51:37 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+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 1669444] Re: [regression] OSK input shaping no longer works correctly
** Branch linked: lp:mir/0.26 -- 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/1669444 Title: [regression] OSK input shaping no longer works correctly Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in ubuntu-keyboard package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Run the keyboard under Unity8 (silo 2481 can be helpful in making this more usable at present) 2) Click in an input field 3) Move the mouse over the keyboard 4) Attempt to click on the app again Expected result: The mouse click should be passed through to the app Actual result: The click is swallowed by the keyboard surface instead. However, it is still possible to click on the app if this is done prior to the mouse entering the visible keyboard area. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669444/+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 1669444] Re: [regression] OSK input shaping no longer works correctly
** Changed in: mir/0.26 Status: Triaged => Fix Committed -- 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/1669444 Title: [regression] OSK input shaping no longer works correctly Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in ubuntu-keyboard package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Run the keyboard under Unity8 (silo 2481 can be helpful in making this more usable at present) 2) Click in an input field 3) Move the mouse over the keyboard 4) Attempt to click on the app again Expected result: The mouse click should be passed through to the app Actual result: The click is swallowed by the keyboard surface instead. However, it is still possible to click on the app if this is done prior to the mouse entering the visible keyboard area. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669444/+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 1669444] Re: [regression] OSK input shaping no longer works correctly
Fix committed to lp:mir/0.26 at revision 4034, scheduled for release in Mir 0.26.2 -- 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/1669444 Title: [regression] OSK input shaping no longer works correctly Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in ubuntu-keyboard package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Run the keyboard under Unity8 (silo 2481 can be helpful in making this more usable at present) 2) Click in an input field 3) Move the mouse over the keyboard 4) Attempt to click on the app again Expected result: The mouse click should be passed through to the app Actual result: The click is swallowed by the keyboard surface instead. However, it is still possible to click on the app if this is done prior to the mouse entering the visible keyboard area. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669444/+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 1670876] Re: Setting MirWindowSpec parameters always causes window's input_region to be reset
*** This bug is a duplicate of bug 1669444 *** https://bugs.launchpad.net/bugs/1669444 ** Branch linked: lp:mir/0.26 -- 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/1670876 Title: Setting MirWindowSpec parameters always causes window's input_region to be reset Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Triaged Status in MirAL: Invalid Status in mir package in Ubuntu: Triaged Bug description: I've made a quick demo to reproduce this: https://code.launchpad.net/~gerboland/+git/basic_mir_client/+ref /cursor-mask-demo 1. launch any mir demo server 2. launch the above demo 3. press 'c' to set the cursor of the window, cursor should become a cross over the window. 4. press 'm' to set the input region as a subset of the window. You can observe the input region by moving the cursor over the window, cursor will be a cross inside the specified region. You can click too, will cause client to print "click" 5. press 'c' again. Expected result no change Actual result Input region of surface appears to be reset - cursor is a cross over the entire window. I've noticed this behaviour only after this update to QtUbuntu: https://code.launchpad.net/~albaguirre/qtubuntu/more-new-mir-apis/+merge/316646 so suspect a bug with the new api only. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670876/+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 1664397] Re: Mouse trails and distorted cursor on 2nd monitor
Edward Gibbs, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664397/comments/4 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid -- 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/1664397 Title: Mouse trails and distorted cursor on 2nd monitor Status in xorg package in Ubuntu: Invalid Bug description: Lenovo Thinkpad P50, Xeon, Nvidia M2000m 4GB, 16 GB RAM 2nd monitor (ASUS) connected via either DP or HDMI, when using Hybrid Graphics the cursor on the second display is distorted and leaves mouse trails that persist for several seconds. Switching to Nvidia graphics cures but Nvidia has other problems (built in display is dim and brightness cannot be adjusted). Interestingly, just opening Display settings also cures the problem for as long as the Display Setting dialog is open. Under Windows (10 Pro) Hybrid Graphics does not exhibit this problem. Ubuntu release is 16.04.2 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.9.0-040900-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: /dev/nvme0n1p2: clean, 297436/7282688 files, 2849132/29101568 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Feb 13 18:15:25 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-62-generic, x86_64: installed bbswitch, 0.8, 4.9.0-040900-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GM107GLM [Quadro M2000M] [10de:13b0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM107GLM [Quadro M2000M] [17aa:2230] InstallationDate: Installed on 2017-01-07 (37 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20EN001SUS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-040900-generic root=UUID=81b27291-6609-488b-8477-b2eb41ab17f2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET64W (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EN001SUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET64W(1.37):bd12/08/2016:svnLENOVO:pn20EN001SUS:pvrThinkPadP50:rvnLENOVO:rn20EN001SUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20EN001SUS dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO 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: Mon Feb 13 18:15:02 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664397/+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 1667352] Re: SDL apps "Failed to connect to the mir server: std::bad_alloc" or crash in google::protobuf::MessageLite::InternalSerializeWithCachedSizesToArray from mir_connect_sy
** Summary changed: - Failure to initialize SDL (Failed to connect to the mir server: std::bad_alloc) + SDL apps "Failed to connect to the mir server: std::bad_alloc" or crash in google::protobuf::MessageLite::InternalSerializeWithCachedSizesToArray from mir_connect_sync ** Also affects: protobuf (Ubuntu) Importance: Undecided Status: New ** Changed in: protobuf (Ubuntu) Importance: Undecided => High ** Changed in: protobuf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1667352 Title: SDL apps "Failed to connect to the mir server: std::bad_alloc" or crash in google::protobuf::MessageLite::InternalSerializeWithCachedSizesToArray from mir_connect_sync Status in Mir: In Progress Status in Mir 0.26 series: Triaged Status in libsdl2 package in Ubuntu: Confirmed Status in neverball package in Ubuntu: Invalid Status in protobuf package in Ubuntu: Confirmed Bug description: ubuntu 17.04 unity8, trying to run neverball game Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting ubuntu-app-launch-application-legacy-neverball-1487864803635991.service... Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL (Failed to connect to the mir server: std::bad_alloc) Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main process exited, code=exited, status=1/FAI Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start ubuntu-app-launch-application-legacy-neverball-1487864803635991.service. Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit entered failed state. Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1667352/+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 1670876] Re: Setting MirWindowSpec parameters always causes window's input_region to be reset
*** This bug is a duplicate of bug 1669444 *** https://bugs.launchpad.net/bugs/1669444 OK, there's no need to have two bug reports open for the one bug. Marking this as a duplicate. It's always best if the bug describes user-facing symptoms. ** This bug has been marked a duplicate of bug 1669444 [regression] OSK input shaping no longer works correctly -- 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/1670876 Title: Setting MirWindowSpec parameters always causes window's input_region to be reset Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Triaged Status in MirAL: Invalid Status in mir package in Ubuntu: Triaged Bug description: I've made a quick demo to reproduce this: https://code.launchpad.net/~gerboland/+git/basic_mir_client/+ref /cursor-mask-demo 1. launch any mir demo server 2. launch the above demo 3. press 'c' to set the cursor of the window, cursor should become a cross over the window. 4. press 'm' to set the input region as a subset of the window. You can observe the input region by moving the cursor over the window, cursor will be a cross inside the specified region. You can click too, will cause client to print "click" 5. press 'c' again. Expected result no change Actual result Input region of surface appears to be reset - cursor is a cross over the entire window. I've noticed this behaviour only after this update to QtUbuntu: https://code.launchpad.net/~albaguirre/qtubuntu/more-new-mir-apis/+merge/316646 so suspect a bug with the new api only. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670876/+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 1670844] Re: libmirclient cannot be reloaded through dlopen
*** This bug is a duplicate of bug 1667352 *** https://bugs.launchpad.net/bugs/1667352 We've been creating multiple bug reports for single bugs too often recently. Let's get it down to one each... ** This bug has been marked a duplicate of bug 1667352 SDL apps "Failed to connect to the mir server: std::bad_alloc" or crash in google::protobuf::MessageLite::InternalSerializeWithCachedSizesToArray from mir_connect_sync -- 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/1670844 Title: libmirclient cannot be reloaded through dlopen Status in Mir: In Progress Status in Mir 0.26 series: Triaged Status in mir package in Ubuntu: Triaged Bug description: Code example: http://paste.ubuntu.com/24133139/ Fails on the 2nd load due to an issue of libprotobuf-lite not being unloaded. Meaning the static variables aren't being re-inited. Protobuf uses a static variable for an empty string optimization which ends up becoming a dangling pointer: back trace: http://paste.ubuntu.com/24133152/ valgrind: http://paste.ubuntu.com/24133156/ The workaround/fix that we saw was to re-set that static variable which will let the empty string be init'd correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1670844/+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 1670876] Re: Setting MirWindowSpec parameters always causes window's input_region to be reset
*** This bug is a duplicate of bug 1669444 *** https://bugs.launchpad.net/bugs/1669444 ** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Triaged ** Changed in: mir (Ubuntu) Importance: Undecided => High -- 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/1670876 Title: Setting MirWindowSpec parameters always causes window's input_region to be reset Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Triaged Status in MirAL: Invalid Status in mir package in Ubuntu: Triaged Bug description: I've made a quick demo to reproduce this: https://code.launchpad.net/~gerboland/+git/basic_mir_client/+ref /cursor-mask-demo 1. launch any mir demo server 2. launch the above demo 3. press 'c' to set the cursor of the window, cursor should become a cross over the window. 4. press 'm' to set the input region as a subset of the window. You can observe the input region by moving the cursor over the window, cursor will be a cross inside the specified region. You can click too, will cause client to print "click" 5. press 'c' again. Expected result no change Actual result Input region of surface appears to be reset - cursor is a cross over the entire window. I've noticed this behaviour only after this update to QtUbuntu: https://code.launchpad.net/~albaguirre/qtubuntu/more-new-mir-apis/+merge/316646 so suspect a bug with the new api only. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670876/+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 1669444] Re: [regression] OSK input shaping no longer works correctly
** Changed in: canonical-devices-system-image Status: Triaged => Fix Committed -- 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/1669444 Title: [regression] OSK input shaping no longer works correctly Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Triaged Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in ubuntu-keyboard package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Run the keyboard under Unity8 (silo 2481 can be helpful in making this more usable at present) 2) Click in an input field 3) Move the mouse over the keyboard 4) Attempt to click on the app again Expected result: The mouse click should be passed through to the app Actual result: The click is swallowed by the keyboard surface instead. However, it is still possible to click on the app if this is done prior to the mouse entering the visible keyboard area. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669444/+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 1669444] Re: [regression] OSK input shaping no longer works correctly
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 1.0.0 ** Changed in: mir Status: In Progress => Fix Committed -- 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/1669444 Title: [regression] OSK input shaping no longer works correctly Status in Canonical System Image: Triaged Status in Mir: Fix Committed Status in Mir 0.26 series: Triaged Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in ubuntu-keyboard package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Run the keyboard under Unity8 (silo 2481 can be helpful in making this more usable at present) 2) Click in an input field 3) Move the mouse over the keyboard 4) Attempt to click on the app again Expected result: The mouse click should be passed through to the app Actual result: The click is swallowed by the keyboard surface instead. However, it is still possible to click on the app if this is done prior to the mouse entering the visible keyboard area. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669444/+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 1669444] Re: [regression] OSK input shaping no longer works correctly
** Also affects: mir/0.26 Importance: Undecided Status: New ** Changed in: mir/0.26 Status: New => Triaged ** Changed in: mir/0.26 Importance: Undecided => High ** Changed in: mir/0.26 Assignee: (unassigned) => Kevin DuBois (kdub) ** Changed in: mir/0.26 Milestone: None => 0.26.2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1669444 Title: [regression] OSK input shaping no longer works correctly Status in Canonical System Image: Triaged Status in Mir: In Progress Status in Mir 0.26 series: Triaged Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Invalid Status in ubuntu-keyboard package in Ubuntu: Invalid Bug description: Steps to reproduce: 1) Run the keyboard under Unity8 (silo 2481 can be helpful in making this more usable at present) 2) Click in an input field 3) Move the mouse over the keyboard 4) Attempt to click on the app again Expected result: The mouse click should be passed through to the app Actual result: The click is swallowed by the keyboard surface instead. However, it is still possible to click on the app if this is done prior to the mouse entering the visible keyboard area. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669444/+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 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting
FFab, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following: 1) The one to test is at the very top line at the top of the page (not the daily folder). 2) The release names are irrelevant. 3) The folder time stamps aren't indicative of when the kernel actually was released upstream. 4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . If testing on your main install would be inconvenient, one may: 1) Install Ubuntu to a different partition and then test this there. 2) Backup, or clone the primary install. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Also, you don't need to apport-collect further unless specifically requested to do so. It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed. Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available. Thank you for your help. -- 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/1639517 Title: [HP Pavilion Notebook - 17-g164ng] black screen when booting Status in xorg package in Ubuntu: Incomplete Bug description: When booting the screen is black – backlight on – off - on. When HDD is inactive - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or Strg + Alt + Del - remote access e.g. using ssh is possible Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10. My notebook is a HP Pavilion 17-g164ng with an AMD A10-8780P APU and 2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz. It seems very similar to that described in #1597079. The bug report was generated from a remote PC. My HP notebook was started without any workaround parameters. This apport doesn't display the second graphic subsystem Topaz R7 as an apport generated with nomodeset xforcevesa. WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver. WORKAROUND: When booting in UEFI mode, use kernel parameters: nomodeset or: nomodeset xforcevesa Resolution without xforcevesa: 800x600 Resolution with xforcevesa: 1600x900 – the optimal resolution ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 5 23:40:19 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:80b6] InstallationDate: Installed on 2016-11-03 (2 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Pavilion Notebook ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.41 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80B6 dmi.board.vendor: HP dmi.board.version: 81.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias:
[Touch-packages] [Bug 1317505] Re: EmbeddedBitmap for ttf-ms-corefonts
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1317505 Title: EmbeddedBitmap for ttf-ms-corefonts Status in fontconfig package in Ubuntu: Confirmed Bug description: When opening a mail in gmail that was send by someone with outlook , the font (Verdana) looks really ugly and broken. This is because for small font sizes the embedded bitmap is used. The default behaviour should be to not use the embeddedBitmap for Verdana (and other ttf-ms- corefonts), since that makes them very ugly. Workaround: Add following lines to ~/.config/fontconfig/fonts.conf false ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: fontconfig 2.11.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 8 14:11:32 2014 InstallationDate: Installed on 2014-04-17 (20 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1317505/+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 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
** Changed in: juju
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1665160
Title:
MachineSuite.TestMachineWorkers timed out waiting for workers zesty
because dbus is in interactive mode
Status in juju:
Triaged
Status in juju 2.1 series:
Won't Fix
Status in dbus package in Ubuntu:
New
Bug description:
As seen at
http://reports.vapour.ws/releases/issue/5768c750749a563f2d7daa6e
A unit test is exclusively failing on our new zesty machine. the
previous issues is not related to the zesty falures
machine-0: has workers [agent api-address-updater api-caller
api-config-watcher disk-manager log-forwarder log-sender logging-config-updater
machine-action-runner machiner migration-fortress migration-inactive-flag
migration-minion proxy-config-updater reboot-executor ssh-authkeys-updater
state-config-watcher storage-provisioner termination-signal-handler
unconverted-api-workers upgrade-check-flag upgrade-check-gate
upgrade-steps-flag upgrade-steps-gate upgrader]
machine-0: waiting for [unit-agent-deployer]
machine-0: unexpected []
machine-0: report:
{}
machine_test.go:1272:
WaitMatch(c, matcher.Check, coretesting.LongWait,
s.BackingState.StartSync)
engine_test.go:234:
c.Fatalf("timed out waiting for workers")
... Error: timed out waiting for workers
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1665160/+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 1581342] Re: Bluetooth menu closes immediately after opening
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-bluetooth (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1581342 Title: Bluetooth menu closes immediately after opening Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04 LTS Release: 16.04 indicator-bluetooth: 0.0.6+16.04.20160214-0ubuntu1 fcitx: 1:4.2.9.1-1ubuntu1 Steps to reproduce: 1. click on the top-right bluetooth icon 2. the panel opens, but closes immediately I do not observe similar behavior with other indicator menus. If I click on other icons, like network/wifi icon, then move cursor on bluetooth icon, bluetooth menu remains opened when cursor hovers it. I suspect this might have something to do with fcitx, I have fcitx- rime installed, if Rime (a input method) is enabled, during the brief time bluetooth menu is opened, rime is disabled. Any suggestion on how to debug further? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1581342/+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 1581342] Re: Bluetooth menu closes immediately after opening
I see this issue on a clean 16.0.4.2 install, I don't have any kind of special input methods installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1581342 Title: Bluetooth menu closes immediately after opening Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04 LTS Release: 16.04 indicator-bluetooth: 0.0.6+16.04.20160214-0ubuntu1 fcitx: 1:4.2.9.1-1ubuntu1 Steps to reproduce: 1. click on the top-right bluetooth icon 2. the panel opens, but closes immediately I do not observe similar behavior with other indicator menus. If I click on other icons, like network/wifi icon, then move cursor on bluetooth icon, bluetooth menu remains opened when cursor hovers it. I suspect this might have something to do with fcitx, I have fcitx- rime installed, if Rime (a input method) is enabled, during the brief time bluetooth menu is opened, rime is disabled. Any suggestion on how to debug further? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1581342/+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 1671325] [NEW] package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1
Public bug reported: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: click 0.4.43+16.04.20160203-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Mar 8 01:51:37 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2015-10-29 (496 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: Upgraded to xenial on 2017-03-08 (0 days ago) ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- 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/1671325 Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 Status in click package in Ubuntu: New Bug description: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: click 0.4.43+16.04.20160203-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Mar 8 01:51:37 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 InstallationDate: Installed on 2015-10-29 (496 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1 UpgradeStatus: Upgraded to xenial on 2017-03-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1671325/+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 1556205] Re: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails
** Changed in: mir Status: Fix Committed => Fix Released -- 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/1556205 Title: mir_demo_server --test-client [mir_demo_client_scroll|mir_demo_client_flicker] fails Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: $ bin/mir_demo_server --test-timeout 3 --test-client bin/mir_demo_client_flicker || echo FAILED ... Connected Surface created [2016-03-11 17:19:54.463733] server_example_test_client.cpp: Client terminated by signal 15 [2016-03-11 17:19:54.463779] mirserver: Stopping FAILED $ bin/mir_demo_server --test-timeout 3 --test-client bin/mir_demo_client_scroll || echo FAILED ... Connected Mir chose pixel format 3 Surface created [2016-03-11 17:21:51.921994] server_example_test_client.cpp: Client terminated by signal 15 [2016-03-11 17:21:51.922045] mirserver: Stopping FAILED I suspect these clients ignore SIGTERM To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1556205/+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 1639745] Re: Mir GL clients never appear at all on VirtualBox
*** This bug is a duplicate of bug 1669807 *** https://bugs.launchpad.net/bugs/1669807 Thanks, but creating a second bug has made a mess. Please be sure to use the original bug report in future. ** Changed in: mir Status: In Progress => Won't Fix ** Changed in: mir Milestone: 1.0.0 => None ** This bug has been marked a duplicate of bug 1669807 Allow Mir/Unity8 to run inside Virtualbox -- 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/1639745 Title: Mir GL clients never appear at all on VirtualBox Status in Mir: Won't Fix Status in mesa package in Ubuntu: Confirmed Bug description: Mir GL clients never appear at all on VirtualBox. After digging for a while, it appears the issue is that vboxvideo does not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly Mir is the opposite now: Mir only supports PRIME but not flink names. Internally some exceptions are being thrown in Mir at present, but we seem to catch and silence them all. So you never see any error messages at all. Just Mir GL clients never appear on screen in VirtualBox. For the record, Wayland supports falling back to flink names in the absence of PRIME. We should too. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1639745/+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 1642272] Re: Incorrect UI scale on high-resolution desktop
** Summary changed: - Incorrect UI scale on high-resolution desktop (everything is gigantic) + Incorrect UI scale on high-resolution desktop -- 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/1642272 Title: Incorrect UI scale on high-resolution desktop Status in Canonical System Image: Triaged Status in Mir: Invalid Status in unity8 package in Ubuntu: Triaged Bug description: On a hidpi display, the unity8 desktop session in 16.10 has an oversized and inconsistent UI scale. The unity8 session is absolutely not usable for testing (because there is not even enough screen space to display the logout menu item). The shell+cursor is rendered with a UI scale of at least 2× the correct scale (e.g. 4× the scale of a low-dpi display). Due to this the indicator menus collapse immediately after clicking because they are larger than the screen height. The content of the scopes window is rendered with 4× the correct scale, giving space for only one icon. In unity 16.04, the correct scale could be achieved by setting "export GRID_UNIT_PX=16" in .bashrc, however this has no effect anymore when I remove or change it. The issue is also in the guest session. Ubuntu version: 16.10 (fresh install) unity8 version: 8.14+16.10.20160 amd64 physical resolution: 3200×1800 resolution used by unity8: 3200×1800 (at first sight I thought it selected a low resolution, but in fact fonts are very sharp). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642272/+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 1661557] Re: Touch tutorial is inescapable on desktop (without a touchscreen)
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) ** Tags added: unity8-desktop ** Changed in: canonical-devices-system-image Milestone: None => u8c-1 ** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: unity8 (Ubuntu) Importance: Undecided => Medium -- 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/1661557 Title: Touch tutorial is inescapable on desktop (without a touchscreen) Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: The touch tutorial is inescapable on desktop (without a touchscreen). I somehow accidentally started Unity8 in touch mode and could use it with a mouse. However after a short while (bug 1607176) the tutorial starts, and there I'm stuck. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661557/+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 1671318] [NEW] System freeze random while using Chrome or Firerfox
Public bug reported: System freeze random while using Chrome or Firerfox ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39 Uname: Linux 3.13.0-110-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Mar 8 20:38:42 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV670 [Radeon HD 3690/3850] [1002:9505] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2245] InstallationDate: Installed on 2014-12-31 (798 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-110-generic root=UUID=91bec545-52b8-46b3-bcc7-ef88511e4a1b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41RQ dmi.board.vendor: Intel Corporation dmi.board.version: AAE54511-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr: version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Mar 8 20:10:08 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- 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/1671318 Title: System freeze random while using Chrome or Firerfox Status in xorg package in Ubuntu: New Bug description: System freeze random while using Chrome or Firerfox ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-110.157-generic 3.13.11-ckt39 Uname: Linux 3.13.0-110-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Mar 8 20:38:42 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV670 [Radeon HD 3690/3850] [1002:9505] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2245] InstallationDate: Installed on 2014-12-31 (798 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-110-generic root=UUID=91bec545-52b8-46b3-bcc7-ef88511e4a1b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41RQ dmi.board.vendor: Intel Corporation dmi.board.version: AAE54511-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr: version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs:
[Touch-packages] [Bug 1670652] Re: No way to contain pointer in VM window
I can't see an option for it in virt-manager so can't fully confirm
(because I have no time to create a VM to verify for you).
Either you're unaware of Qemu's keyboard shortcut to contain the pointer
("Ctrl-Alt Toggle mouse and keyboard grab." [1]), or your VM is
defaulting to -usbdevice tablet when you want -usbdevice mouse, or you
need both.
Put another way, this is probably either user error or lack of
configuration in virt-manager. So at most it's a virt-manager bug.
[1] https://qemu.weilnetz.de/doc/qemu-doc.html#pcsys_005fkeys
** Changed in: mir
Status: Incomplete => Invalid
** Changed in: mir (Ubuntu)
Status: Incomplete => Invalid
** Changed in: virt-manager (Ubuntu)
Status: New => Incomplete
** Changed in: unity8 (Ubuntu)
Status: Incomplete => 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/1670652
Title:
No way to contain pointer in VM window
Status in Canonical System Image:
Incomplete
Status in Mir:
Invalid
Status in mir package in Ubuntu:
Invalid
Status in qemu package in Ubuntu:
Incomplete
Status in unity8 package in Ubuntu:
Invalid
Status in virt-manager package in Ubuntu:
Incomplete
Bug description:
In a Qemu VM, the unity8 side gestures (for the launcher and app
switcher) cannot be activated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670652/+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 1670652] Re: No way to contain pointer in VM window
Doesn't 'qemu -usbdevice mouse' constrain the pointer correctly already? I assume we're talking about the behaviour of 'qemu -usbdevice tablet' here... ** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Status: New => Incomplete ** Also affects: virt-manager (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/1670652 Title: No way to contain pointer in VM window Status in Canonical System Image: Incomplete Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in qemu package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Invalid Status in virt-manager package in Ubuntu: Incomplete Bug description: In a Qemu VM, the unity8 side gestures (for the launcher and app switcher) cannot be activated. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670652/+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 1670670] Re: Unity8 pointer does not stay in sync with Qemu VM tablet input
Invalid for Mir because the enhancement Gerry mentioned is covered in bug 1600220 instead. If Unity8 used the absolute pointer coordinates that USC gives it then we wouldn't have a problem here. If Unity8 doesn't want to use those all the time then we will need to work out a compromise that makes events from Qemu's mouse/tablet hybrid more obviously absolute (like touches are) so that clients (which U8 is one) know that relative motion from that device is useless. In Qemu you can move the cursor off the right edge of the window, move it around the Qemu window and make it appear on some other edge. It would be messy at least to try and communicate that using relative motion data. If we really want to do that then sure this is a Mir bug, but I don't think we want to do that. Useful links: https://bugs.launchpad.net/mir/+bugs?field.tag=wacom https://bugs.launchpad.net/mir/+bugs?field.tag=cursor -- 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/1670670 Title: Unity8 pointer does not stay in sync with Qemu VM tablet input Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Each time you login, or come back from the lock screen, you need to "recalibrate" the pointer by carefully moving the pointer into each corner. Contrast this with unity7, where the absolute position of the virtual tablet pointer is tracked, and sync is never lost. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670670/+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 1671039] Re: app drawer - show full application name on roll over the icon
*** This bug is a duplicate of bug 1667570 *** https://bugs.launchpad.net/bugs/1667570 Duplicate of bug 1667570 I think. ** This bug has been marked a duplicate of bug 1667570 App drawer icon titles are difficult to read (truncated too much and have no tooltips) -- 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/1671039 Title: app drawer - show full application name on roll over the icon Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: When the name of an application is too long it is ellipsised and in several cases there is no way to know which application is which from the shorten name and the icons are not always obvious. For example in French there are several viewer applications like: - Visionneuse de documents (pdf viewer) - Visionneuse de polices de caractères (character map viewer) - Visionneuse d'images (image viewer) - ... There are all ellipsised to 'Visionne..." ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity8 8.15+17.04.20170221-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Wed Mar 8 11:44:22 2017 InstallationDate: Installed on 2014-07-23 (958 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: unity8 UpgradeStatus: Upgraded to zesty on 2016-11-15 (112 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671039/+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 1670670] Re: Unity8 pointer does not stay in sync with Qemu VM tablet input
** Tags added: cursor ** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Status: New => Invalid ** Changed in: mir (Ubuntu) Status: Confirmed => Invalid -- 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/1670670 Title: Unity8 pointer does not stay in sync with Qemu VM tablet input Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Each time you login, or come back from the lock screen, you need to "recalibrate" the pointer by carefully moving the pointer into each corner. Contrast this with unity7, where the absolute position of the virtual tablet pointer is tracked, and sync is never lost. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670670/+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 1668093] Re: ssh-keygen -H corrupts already hashed entries
This was fixed upstream in this commit https://anongit.mindrot.org/openssh.git/commit/?id=12d3767ba4c84c32150cbe6ff6494498780f12c9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1668093 Title: ssh-keygen -H corrupts already hashed entries Status in openssh package in Ubuntu: Triaged Status in openssh package in Debian: New Bug description: xenial @ 1:7.2p2-4ubuntu2.1 on amd64 has this bug. trusty @ 1:6.6p1-2ubuntu2.8 on amd64 does not have this bug. I have not tested any other ssh versions. The following should reproduce the issue: #ssh-keyscan > ~/.ssh/known_hosts # ssh root@X Permission denied (publickey). # ssh-keygen -H /root/.ssh/known_hosts updated. Original contents retained as /root/.ssh/known_hosts.old WARNING: /root/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames # ssh root@XX Permission denied (publickey). # ssh-keygen -H /root/.ssh/known_hosts updated. Original contents retained as /root/.ssh/known_hosts.old WARNING: /root/.ssh/known_hosts.old contains unhashed entries Delete this file to ensure privacy of hostnames # ssh root@X The authenticity of host 'XX' can't be established. RSA key fingerprint is XX. Are you sure you want to continue connecting (yes/no)? # diff known_hosts.old known_hosts 1c1 < |1|BoAbRpUE3F5AzyprJcbjdepeDh8=|x/1AcaLxh45FlShmVQnlgx2qjxY= X --- > |1|nTPsoLxCugQyZi3pqOa2pc/cX64=|bUH5qwZlZPp8msMGHdLtslf3Huk= X To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1668093/+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 1525477] Re: X server crash when pasting selection using middle button in Chromium
Andrei Borzenkov, one may install chromium in the live environment if one has the universe repository enabled via https://help.ubuntu.com/community/Repositories. -- 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/1525477 Title: X server crash when pasting selection using middle button in Chromium Status in xorg package in Ubuntu: Incomplete Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 xorg 1:7.7+1ubuntu8.1 Select any text; use middle button to paste selection in Chromium (I observed it pasting in URL bar or in any form text input field, including previous attempt to report this bug :) ). Session crashes. It does not happen, when either pasting into different application (like terminal) or wen use Copy - Paste instead of middle button. I noticed it about a week ago, so it must be some recent change; I use selection paste often enough to notice something like this before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-19.23~14.04.1-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 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 CurrentDesktop: Unity Date: Sat Dec 12 11:09:22 2015 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062b] InstallationDate: Installed on 2015-07-02 (162 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 12 11:08:11 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525477/+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 1194185] Re: After adding an Ubuntu Online Accounts based account evolution is not updated
** Changed in: evolution-data-server Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1194185 Title: After adding an Ubuntu Online Accounts based account evolution is not updated Status in evolution-data-server: Expired Status in evolution-data-server package in Ubuntu: New Bug description: I've configured a gmail based account using the Ubuntu Online Accounts data-server and I wasn't able to see the mail account in evolution until I've killed an evolution-* process (it should be evolution-source-registry). Afterwards, my mail account was accessible on evolution. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evolution-data-server-uoa 3.8.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic x86_64 ApportVersion: 2.10.2-0ubuntu2 Architecture: amd64 Date: Mon Jun 24 18:05:20 2013 InstallationDate: Installed on 2010-07-10 (1080 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True SourcePackage: evolution-data-server UpgradeStatus: Upgraded to saucy on 2012-10-10 (257 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1194185/+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 1636205] Re: NumberFormatter has incorrect currency symbols for certain locales
# cat test.php format(5000) . PHP_EOL; ?> 17.04 (7.0.15-1ubuntu3): # php test.php 5 000,00 Ft 16.10 (7.0.15-0ubuntu0.16.10.4): # php test.php 5 000,00 Ft 16.04 (7.0.15-0ubuntu0.16.04.4): # php test.php 5 000,00 HUF So I took a look at 16.04 uses libicu55 while 16.10+ use libicu57. I'm guessing there is an upstream bugfix needed for src:icu. ** Also affects: icu (Ubuntu) Importance: Undecided Status: New ** Also affects: icu (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: php7.0 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: icu (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: php7.0 (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: icu (Ubuntu) Status: New => Fix Released ** Changed in: icu (Ubuntu Yakkety) Status: New => Fix Released ** Changed in: icu (Ubuntu Xenial) Status: New => Triaged ** Changed in: php7.0 (Ubuntu Xenial) Status: New => Triaged ** Changed in: php7.0 (Ubuntu) Status: Triaged => Fix Released ** Changed in: php7.0 (Ubuntu Yakkety) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1636205 Title: NumberFormatter has incorrect currency symbols for certain locales Status in icu package in Ubuntu: Fix Released Status in php7.0 package in Ubuntu: Fix Released Status in icu source package in Xenial: Triaged Status in php7.0 source package in Xenial: Triaged Status in icu source package in Yakkety: Fix Released Status in php7.0 source package in Yakkety: Fix Released Bug description: Intl seems to be missing certain currency symbols in certain locales on ubuntu 16.04. I noticed while doing some unit tests. Under hu_HU locale, the expected result was 5 000 Ft The actual result turned out to be 5 000 HUF. It seems to be specific to this build, as this passes without problems on the CI server, and also worked fine on other distributions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1636205/+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 1631288] Re: XV video screen always on top
dabrain, regarding the new issue of screen corruption, please file a new report. -- 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/1631288 Title: XV video screen always on top Status in xorg package in Ubuntu: Fix Released Bug description: When playing a video with vlc, gstreamer(xvimagesink), the video stays on top of every X window. In VLC this bug can be bypassed disabling overlay video. In Gstreamer using ximagsink is ok too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Oct 7 09:45:31 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Skylake Integrated Graphics [1179:001d] Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d] InstallationDate: Installed on 2016-10-03 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: TOSHIBA TECRA Z50-C PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.70 dmi.board.asset.tag: 00 dmi.board.name: TECRA Z50-C dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z50-C dmi.product.version: PT577E-01100GCE dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.68-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Oct 6 17:44:07 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1237 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
Hello!
I have changed Before to After and it is working
Here is what the unit looks like now:
[Unit]
Description=Unattended Upgrades Shutdown
DefaultDependencies=no
After=shutdown.target reboot.target halt.target network.target local-fs.target
Documentation=man:unattended-upgrade(8)
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStop=/usr/share/unattended-upgrades/unattended-upgrade-shutdown
TimeoutStopSec=900
[Install]
WantedBy=shutdown.target
So the proper fix would be changing the Service to ExecStop= and Unit to After=
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Yakkety:
Fix Committed
Status in unattended-upgrades package in Debian:
New
Bug description:
[SRU justification]
This fix is needed to make sure that the system does not hang on shutdown
when /var is a speparate file system
[Impact]
System can hang up to 10 minutes if not fixed.
[Fix]
Change the systemd unit's ExecStart to an ExecStop so the unit is correctly
sequenced.
[Test Case]
In a VM with /var separated from the / file system, shutdown the VM. It will
hang for 10 minutes
[Regression]
None to be expected. A ExecStop unit will be sequenced before the Before=
units which is earlier than previously.
[Original description of the problem]
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all
filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in
progress
and the service will wait until it finishes (and therefore automatically wait
at
shutdown).
However, if /var is a separate filesystem, it will get unmounted even though
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5
seconds, and
tries to check the lockfile again. After 10 minutes (the default timeout), it
will finally
exit and the system will continue shutdown.
The problem is the error handling in
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:
while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True
The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an
error.
File descriptors are just C file descriptors, so they are always positive
integers.
The code should check the result to be negative, not positive. I have
attached a patch
to reverse the logic.
Additional information:
1)
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2)
unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
*** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
100 /var/lib/dpkg/status
0.90 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
3)
Fast reboot
4)
Very slow reboot (after a 10 minutes timeout)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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 1646739] Re: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
For those that do see this issue, is it reproducible from update- manager? That is, once it happens, if you cancle/quit update-manager, and then try to use it to update again, does it again hang (e.g., on php7.0-xml as in this bug report). If so, we might be able to get some more debugging by modifying the postinst locally. @f-abeni: do you have any local modifications to your php-xml .ini file snippet? Also, if you do re-encounter the hang, does /var/log/apt/history.log contain the "Use of uninitialized value" errors already (before you hit cancel or kill update-manager)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1646739 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in debconf package in Ubuntu: Confirmed Status in php7.0 package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: During a software upgrade, process was stuck on php7.0-xml configuration for 20 minutes, after that I killed the process. I am not sure what additional info are required, will be happy to provide any. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Fri Dec 2 09:52:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-03-11 (265 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: php7.0 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 1671278] [NEW] Xorg freeze
Public bug reported: Freezes the screen and locks the computer, needing to reboot. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Mar 8 20:40:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-11-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.10.0-9-generic, x86_64: installed virtualbox, 5.1.14, 4.10.0-11-generic, x86_64: installed GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G98M [GeForce 9300M GS] [1028:02bb] InstallationDate: Installed on 2014-01-10 (1153 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Dell Inc. Vostro 1320 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-11-generic root=UUID=5189c31e-9b68-4026-a657-b0d301136218 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0R235J dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnDellInc.:bvrA04:bd09/10/2009:svnDellInc.:pnVostro1320:pvrNull:rvnDellInc.:rn0R235J:rvr:cvnDellInc.:ct8:cvrN/A: dmi.product.name: Vostro 1320 dmi.product.version: Null dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 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.8.0-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.13-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze ubuntu zesty -- 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/1671278 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Freezes the screen and locks the computer, needing to reboot. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Mar 8 20:40:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-11-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.10.0-9-generic, x86_64: installed virtualbox, 5.1.14, 4.10.0-11-generic, x86_64: installed GpuHangFrequency: Continuously GpuHangReproducibility: I don't know GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G98M [GeForce 9300M GS] [1028:02bb] InstallationDate: Installed on 2014-01-10 (1153 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Dell Inc. Vostro 1320 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-11-generic root=UUID=5189c31e-9b68-4026-a657-b0d301136218 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0R235J dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: N/A dmi.modalias:
[Touch-packages] [Bug 1666441] Re: Topbar interferes with VMware workstation in fullscreen mode
Vaclav Cermak, thank you for reporting this and helping make Ubuntu better. For you personally, could you please advise to the following: 1) What version(s) of VMware Player have you tested? 2) What version(s) of Ubuntu has this been reproducible with as a guest? 3) On the host, if you use Nouveau instead of the Nvidia drivers, does this change anything? ** Tags added: latest-bios-0079 ** Description changed: - When I run VMware workstation (player in my case) in fullscreen mode, - top bar is hidden, but it still takes mouse events and I cannot click to - undelying VMware window. This happens randomly. + When I run VMware Player in fullscreen mode, the top bar is hidden, but + it still takes mouse events and I cannot click to underlying VMware + window. This happens randomly. Seems like it is the same like in this expired bug: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314780. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 - GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 + GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .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 CurrentDesktop: Unity Date: Tue Feb 21 09:12:08 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - NVIDIA Corporation GM200 [GeForce GTX TITAN X] [10de:17c2] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: NVIDIA Corporation GM200 [GeForce GTX TITAN X] [10de:1132] + NVIDIA Corporation GM200 [GeForce GTX TITAN X] [10de:17c2] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: NVIDIA Corporation GM200 [GeForce GTX TITAN X] [10de:1132] InstallationDate: Installed on 2016-06-14 (251 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=615648ea-b585-4a04-9853-0a98eaa41577 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BAP6710H.86A.0079.2012.0622.1722 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DP67DE dmi.board.vendor: Intel Corporation dmi.board.version: AAG10217-204 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBAP6710H.86A.0079.2012.0622.1722:bd06/22/2012:svn:pn:pvr:rvnIntelCorporation:rnDP67DE:rvrAAG10217-204:cvn:ct3:cvr: 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Mon Feb 20 09:32:11 2017 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputPower Button KEYBOARD, id 7 - inputLogitech Performance MX MOUSE, id 8 - inputLogitech M510MOUSE, id 9 - inputLogitech K340KEYBOARD, id 10 + inputPower Button KEYBOARD, id 6 + inputPower Button KEYBOARD, id 7 + inputLogitech Performance MX MOUSE, id 8 + inputLogitech M510MOUSE, id 9 + inputLogitech K340KEYBOARD, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - + xserver.version: 2:1.18.4-0ubuntu0.2 ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in:
[Touch-packages] [Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
Any idea if an upstream fix will be applied on Xenial ? It's a very annoying issue :/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot Status in ifupdown package in Ubuntu: Confirmed Bug description: Expectation: After reboot, route for default gateway specified on bonded interface is installed according to "gateway x.x.x.x" (where x.x.x.x is a valid IPv4 address) specified in /etc/network/interfaces or files sourced per /etc/network/interfaces Actual Result: After reboot, route is not installed. Interface does work otherwise (I can ping the gateway on that subnet, for instance). 'ifdown -a' followed by 'ifup -a' (run with proper permission... so sudo) brings the gateway back until next reboot. Package: I'm not familiar enough to be certain what is causing this, but I was seeing this in beta2 of 16.04 as well. *username snipped*@*hostname snipped*:~$ lsb_release -rd Description:Ubuntu 16.04 LTS Release:16.04 *username snipped*@*hostname snipped*:~$ apt-cache policy ifenslave ifenslave: Installed: 2.7ubuntu1 Candidate: 2.7ubuntu1 Version table: *** 2.7ubuntu1 100 100 /var/lib/dpkg/status *username snipped*@*hostname snipped*:~$ apt-cache policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 100 100 /var/lib/dpkg/status /etc/network/interfaces -- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto enp2s0f1 iface enp2s0f1 inet manual bond-master bond0 auto enp2s0f0 iface enp2s0f0 inet manual bond-master bond0 auto bond0 iface bond0 inet static address 10.96.96.2 netmask 255.255.255.0 network 10.96.96.0 broadcast 10.96.96.255 # dns-* options are implemented by the resolvconf package, if installed dns-search *snip* bond-mode balance-alb bond-slaves none bond-miimon 100 auto bond0.3000 iface bond0.3000 inet static address 172.21.33.29 netmask 255.255.255.0 network 172.21.33.0 broadcast 172.21.33.255 gateway 172.21.33.1 dns-search *snip* vlan-raw-device bond0 dns-nameservers 172.31.10.84 8.8.8.8 4.2.2.2 - interfaces.d is empty: *username snipped*@*hostname snipped*:~$ ls -lisah /etc/network/interfaces.d total 8.0K 10748247 4.0K drwxr-xr-x 2 root root 4.0K Jan 24 14:08 . 10748237 4.0K drwxr-xr-x 7 root root 4.0K Apr 21 17:32 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573272/+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 1646739] Re: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
For those who filed bugs I just duped here, there seems to be an underlying issue with update-manager invoking aptdaemon which in turn seems to think it needs to call a maintscript (although it doesn't necessarily) which then errors out. Using cli tools instead, this does not occur. This is not specific to php7.0 at all, but is something seen across many packages always involving update-manager. I have seen at least a few historic bugs (supposedly fixed) and am still doing archaeology to see if something maybe was dropped: LP: #804250, LP: #779970, LP: #845367. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1646739 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in debconf package in Ubuntu: Confirmed Status in php7.0 package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: During a software upgrade, process was stuck on php7.0-xml configuration for 20 minutes, after that I killed the process. I am not sure what additional info are required, will be happy to provide any. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Fri Dec 2 09:52:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-03-11 (265 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: php7.0 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 1646739] Re: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: debconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1646739 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in debconf package in Ubuntu: Confirmed Status in php7.0 package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: During a software upgrade, process was stuck on php7.0-xml configuration for 20 minutes, after that I killed the process. I am not sure what additional info are required, will be happy to provide any. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Fri Dec 2 09:52:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-03-11 (265 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: php7.0 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 1646739] Re: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Also affects: debconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1646739 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in debconf package in Ubuntu: Confirmed Status in php7.0 package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: During a software upgrade, process was stuck on php7.0-xml configuration for 20 minutes, after that I killed the process. I am not sure what additional info are required, will be happy to provide any. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Fri Dec 2 09:52:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-03-11 (265 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: php7.0 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 1615482] Re: apt-daily timer runs at random hours of the day
Marking this 'high' and a regression. This had been deliberately engineered in Ubuntu to run once per day outside of normal work hours, with a random offset <1h to spread out the mirror load. The current behavior is not consistent with that design, and can be disruptive to the regular use of the system. (I experienced this today with my desktop going into a tailspin because my browser and apt were fighting for memory.) ** Changed in: apt (Ubuntu) Importance: Medium => High -- 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/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Triaged Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+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 1615482] Re: apt-daily timer runs at random hours of the day
Marking this 'high' and a regression. This had been deliberately engineered in Ubuntu to run once per day outside of normal work hours, with a random offset <1h to spread out the mirror load. The current behavior is not consistent with that design, and can be disruptive to the regular use of the system. (I experienced this today with my desktop going into a tailspin because my browser and apt were fighting for memory.) -- 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/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Triaged Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+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 1670745] Re: ssh-keyscan : bad host signature when using port option
Thank you for your action Joshua. The most weird thing is that it is known to work on debian (as reported here : https://github.com/ansible/ansible-modules-extras/issues/2651) ! For future reference, your bug report URL to openssh is : https://bugzilla.mindrot.org/show_bug.cgi?id=2692 ** Bug watch added: github.com/ansible/ansible-modules-extras/issues #2651 https://github.com/ansible/ansible-modules-extras/issues/2651 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1670745 Title: ssh-keyscan : bad host signature when using port option Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: New Bug description: When I use the port option with ssh-keygen, the result is not compatible with ssh known_host file format. UBUNTU VERSION : lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 BAD : :~/.ssh$ cat /etc/issue Ubuntu 16.04.1 LTS \n \l :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...] debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400 # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3 debug1: Enabling compatibility mode for protocol 2.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha...@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= ==> we see the port number because it is not hashed ! GOOD : rm ~/.ssh/known_hosts :~/$ ssh -p [...port...] [...snip...] The authenticity of host '[[...snip...]]:[...port...] ([[...snip...]]:[...port...])' can't be established. ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list of known hosts. [...snip...]@[...snip...]'s password: :~/$ !cat cat ~/.ssh/known_hosts |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= ==> we cannot see the port number as it is well hashed ! REMARKS : == Same problem has already reported here (on macOS): https://github.com/ansible/ansible-modules-extras/issues/2651 It seems that ssh-keyscan version and open-ssh version differs : dpkg -l | grep openssh :: ii openssh-client 1:7.2p2-4ubuntu2.1 [...] ssh-keyscan -v [...] :: debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400 It is very annoying because I am trying to manage hand installed VMs with Ansible. For that I want to automate SSH host keys storing in known_hosts database. And because of this bug I can't. (ansible KIKIN project in development). Thank you, BR, Gautier HUSSON. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1670745/+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 1637239] Re: Please merge ncurses 6.0+20161126-1 (main) from Debian unstable (main)
The debdiff looks good, but have reviewed the upstream delta and agreed with Tiago that this should wait until after the zesty release. Unsubscribing sponsors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1637239 Title: Please merge ncurses 6.0+20161126-1 (main) from Debian unstable (main) Status in ncurses package in Ubuntu: Confirmed Bug description: Ubuntu version: 6.0+20160625-1ubuntu1 Debian verison: 6.0+20161126-1 Details: https://merges.ubuntu.com/n/ncurses/REPORT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1637239/+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 1671263] [NEW] No volume and brightness
Public bug reported: I was using the Unity Tweak tool and teh system crashed. After that the sound doesn't works and the brightness can't be changed. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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 CurrentDesktop: Unity Date: Wed Mar 8 13:39:50 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2017-03-07 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 20211 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=25482d3f-3b71-4e4b-b099-270f07f3d3cb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN31WW(V1.10) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad P400 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN31WW(V1.10):bd11/16/2012:svnLENOVO:pn20211:pvrLenovoIdeaPadP400Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadP400Touch: dmi.product.name: 20211 dmi.product.version: Lenovo IdeaPad P400 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 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 Mar 8 13:33:45 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: amd64 apport-bug compiz-0.9 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/1671263 Title: No volume and brightness Status in xorg package in Ubuntu: New Bug description: I was using the Unity Tweak tool and teh system crashed. After that the sound doesn't works and the brightness can't be changed. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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 CurrentDesktop: Unity Date: Wed Mar 8 13:39:50 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2017-03-07 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: LENOVO 20211 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=25482d3f-3b71-4e4b-b099-270f07f3d3cb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN31WW(V1.10) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag
[Touch-packages] [Bug 1554806] Re: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now
A simpler workaround that was OK for me: rm /etc/localtime dpkg-reconfigure -f noninteractive tzdata After /etc/localtime is removed, it is regenerated properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1554806 Title: Change of behavior: "dpkg-reconfigure -f noninteractive" unconditionally overwrites /etc/timezone now Status in tzdata package in Ubuntu: Confirmed Bug description: In previous versions it was possible to set the system's timezone by editing /etc/timezone before running "dpkg-reconfigure -f noninteractive tzdata". This behavior changed, /etc/timezone gets overwritten unconditionally during "dpkg-reconfigure -f noninteractive tzdata": --- root@xenial:/# echo "Europe/Berlin" > /etc/timezone root@xenial:/# cat /etc/timezone Europe/Berlin root@xenial:/# dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Etc/UTC' Local time is now: Tue Mar 8 23:09:39 UTC 2016. Universal Time is now: Tue Mar 8 23:09:39 UTC 2016. root@xenial:/# cat /etc/timezone Etc/UTC --- As a workaround to programmatically set the timezone one now needs to point "/etc/localtime" to the new timezone: --- root@xenial:/# ln -fs /usr/share/zoneinfo/Europe/Berlin /etc/localtime root@xenial:/# ll /etc/localtime lrwxrwxrwx 1 root root 33 Mar 9 00:48 /etc/localtime -> /usr/share/zoneinfo/Europe/Berlin root@xenial:/# cat /etc/timezone Etc/UTC root@xenial:/# dpkg-reconfigure -f noninteractive tzdata Current default time zone: 'Europe/Berlin' Local time is now: Wed Mar 9 00:49:05 CET 2016. Universal Time is now: Tue Mar 8 23:49:05 UTC 2016. root@xenial:/# cat /etc/timezone Europe/Berlin --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1554806/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
Hello,
Yes, I am fully aware that my /var/run->/run replacement in that script
is a hack.
To be clear I am not testing in Zesty but Ubuntu 16.04.2 LTS Xenial.
The setup is following:
/dev/sda1 on / type xfs (rw,relatime,attr2,inode64,noquota)
/dev/sdc on /var type xfs (rw,relatime,attr2,inode64,noquota)
Every single machine we (my and my colleague) tested with the updated
unit still hangs.
As var as I can tell they never reboot.
I have posted a question regarding this issue to systemd mailing list,
and one of the responses was the following:
"""
> [Unit]
> Description=Unattended Upgrades Shutdown
> DefaultDependencies=no
> Before=shutdown.target reboot.target halt.target network.target
> local-fs.target
Well, you order if before local-fs.target, which means it is stopped
after local-fs.target. You get exactly what you ask for. If this is
wrong, fix unit definition, but we do not really know what is
appropriate for this service.
> Documentation=man:unattended-upgrade(8)
>
> [Service]
> Type=oneshot
> RemainAfterExit=yes
> ExecStop=/usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug
> TimeoutStopSec=900
>
> [Install]
> WantedBy=shutdown.target
>
> It appears no one who is involved in this fix understands systemd (which is
> very worrying!).
>
> How does one would fix this unit so it is ran before the file systems get
> unmounted?
>
Order it
After=local-fs.target
"""
"Obviously" according to systemd mailing list if I want to things to run Before
I need to use After!
So I believe the confusion is with what exactly Before and After mean in
systemd units.
Today I will be testing various combinations with After/Before to see if
I can make sense of it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Yakkety:
Fix Committed
Status in unattended-upgrades package in Debian:
New
Bug description:
[SRU justification]
This fix is needed to make sure that the system does not hang on shutdown
when /var is a speparate file system
[Impact]
System can hang up to 10 minutes if not fixed.
[Fix]
Change the systemd unit's ExecStart to an ExecStop so the unit is correctly
sequenced.
[Test Case]
In a VM with /var separated from the / file system, shutdown the VM. It will
hang for 10 minutes
[Regression]
None to be expected. A ExecStop unit will be sequenced before the Before=
units which is earlier than previously.
[Original description of the problem]
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all
filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in
progress
and the service will wait until it finishes (and therefore automatically wait
at
shutdown).
However, if /var is a separate filesystem, it will get unmounted even though
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5
seconds, and
tries to check the lockfile again. After 10 minutes (the default timeout), it
will finally
exit and the system will continue shutdown.
The problem is the error handling in
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:
while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True
The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an
error.
File descriptors are just C file descriptors, so they are always positive
integers.
The code should check the result to be negative, not positive. I have
attached a patch
to reverse the logic.
Additional information:
1)
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2)
unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
*** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
100 /var/lib/dpkg/status
0.90 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu
[Touch-packages] [Bug 1668700] Re: Blank default scope in unity8-deb
** No longer affects: unity-scope-mediascanner (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1668700 Title: Blank default scope in unity8-deb Status in Canonical System Image: New Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: Environment: unity8-deb on a fresh zesty installation in kvm Steps: 1º Install zesty on kvm image 2º Enter unity8-deb 3º Check the default scope Expected result: some scopes should be marked by default as favorite, unity-scope-mediascanner2 wasn't installed along with zesty so some scopes are missing Current result: default scope is blank and only 3rd party scopes are available Add info: Bug #1668701 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668700/+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 1671155] Re: Autopilot tests that involve special keys fail
** Changed in: autopilot
Status: Fix Committed => 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/1671155
Title:
Autopilot tests that involve special keys fail
Status in Autopilot:
In Progress
Status in webbrowser-app package in Ubuntu:
New
Bug description:
I upgraded my laptop running xenial+overlay to yakkety then zesty
yesterday, and since then all webbrowser-app autopilot tests that
involve pressing special keys or key combinations (like 'Escape', 'F6'
or 'Ctrl+plus') are consistently failing:
Traceback (most recent call last):
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/tests/test_fullscreen.py",
line 70, in test_user_exit_ESC
self.main_window.press_key('Escape')
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/emulators/browser.py",
line 192, in press_key
self.keyboard.press_and_release(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 181,
in press_and_release
self.press(keys, delay)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 138,
in press
self._device.press(key_button)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 56,
in press
ecode = self._get_ecode_for_key(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 66,
in _get_ecode_for_key
raise ValueError('Unknown key name: %s.' % key)
ValueError: Unknown key name: Escape.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1671155/+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 1671155] Re: Autopilot tests that involve special keys fail
https://code.launchpad.net/~sbaldassin/autopilot/fix_1671155/+merge/319367
** Changed in: autopilot
Status: New => Confirmed
** Changed in: autopilot
Status: Confirmed => Fix Committed
--
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/1671155
Title:
Autopilot tests that involve special keys fail
Status in Autopilot:
Fix Committed
Status in webbrowser-app package in Ubuntu:
New
Bug description:
I upgraded my laptop running xenial+overlay to yakkety then zesty
yesterday, and since then all webbrowser-app autopilot tests that
involve pressing special keys or key combinations (like 'Escape', 'F6'
or 'Ctrl+plus') are consistently failing:
Traceback (most recent call last):
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/tests/test_fullscreen.py",
line 70, in test_user_exit_ESC
self.main_window.press_key('Escape')
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/emulators/browser.py",
line 192, in press_key
self.keyboard.press_and_release(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 181,
in press_and_release
self.press(keys, delay)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 138,
in press
self._device.press(key_button)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 56,
in press
ecode = self._get_ecode_for_key(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 66,
in _get_ecode_for_key
raise ValueError('Unknown key name: %s.' % key)
ValueError: Unknown key name: Escape.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1671155/+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 1671216] [NEW] ColdplugWifi test failures in ADT
Public bug reported: We're seeing intermittent kernel ADT test failues against network- manager due to the ColdplugWifi test timing out. This is happening across multiple releases. Here's an example from xenial: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/i386/n/network- manager/20170215_193017_bf4ec@/log.gz and another from zesty: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/i386/n/network- manager/20170307_182040_787e9@/log.gz In experimenting on zesty I've found that I can pretty easily recreate the failures by running the ColdplugWifi test in a loop, usually within 10 iterations. I've also found that if I increase the timeout in the test for reaching the activated state from 20 to 30 seconds I cannot reproduce the error. So it seems that perhaps the timeout on the test is too short and should be increased. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1671216 Title: ColdplugWifi test failures in ADT Status in network-manager package in Ubuntu: New Bug description: We're seeing intermittent kernel ADT test failues against network- manager due to the ColdplugWifi test timing out. This is happening across multiple releases. Here's an example from xenial: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/i386/n/network- manager/20170215_193017_bf4ec@/log.gz and another from zesty: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/i386/n/network- manager/20170307_182040_787e9@/log.gz In experimenting on zesty I've found that I can pretty easily recreate the failures by running the ColdplugWifi test in a loop, usually within 10 iterations. I've also found that if I increase the timeout in the test for reaching the activated state from 20 to 30 seconds I cannot reproduce the error. So it seems that perhaps the timeout on the test is too short and should be increased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671216/+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 1671214] [NEW] Several xmir instances crash unity8
*** This bug is a duplicate of bug 1670710 *** https://bugs.launchpad.net/bugs/1670710 Public bug reported: I'm testing the deb-based unity8. And launching several xmir-using apps will in short order take unity8 down. The problem is about to get worse once the UAL that defaults to xmir launches lands. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: unity8-desktop ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags added: unity8-desktop ** This bug has been marked a duplicate of bug 1670710 unity8 crashed with SIGSEGV in qtmir::DBusFocusInfo::findQmlSurface() -- 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/1671214 Title: Several xmir instances crash unity8 Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: I'm testing the deb-based unity8. And launching several xmir-using apps will in short order take unity8 down. The problem is about to get worse once the UAL that defaults to xmir launches lands. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671214/+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 1671209] [NEW] Error
Public bug reported: Error language in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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 Mar 8 20:19:35 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-41-generic, x86_64: installed nvidia-367, 367.57, 4.8.0-41-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:5001] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [GeForce GT 630M] [17aa:5001] InstallationDate: Installed on 2017-03-08 (0 days ago) InstallationMedia: Ubuntu-Kylin 16.10 "Yakkety Yak" - Release amd64 (20161012.3) MachineType: LENOVO 32593TG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=635cf8fd-f7ab-4a83-b9aa-2221195e9279 ro locale=zh_CN quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H0ET30WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 32593TG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH0ET30WW(1.12):bd05/08/2012:svnLENOVO:pn32593TG:pvrThinkPadEdgeE530:rvnLENOVO:rn32593TG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 32593TG dmi.product.version: ThinkPad Edge E530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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 Mar 8 20:00:42 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1671209 Title: Error Status in xorg package in Ubuntu: New Bug description: Error language in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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 Mar 8 20:19:35 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-41-generic, x86_64: installed nvidia-367, 367.57, 4.8.0-41-generic, x86_64: installed GraphicsCard: Intel
[Touch-packages] [Bug 1670796] Re: totem fails to launch under deb-based unity8
With latest UAL (in zesty-proposed), totem opens (using xmir now). Its
menus don't work though... So I'll just convert this bug.
** Summary changed:
- totem fails to launch under deb-based unity8
+ totem's menus don't open under deb-based unity8
** Description changed:
- This is very similar to bug 1670721, but looks to be a different root
- cause.
-
- When launching totem, it complains about not being able to initialize a
- clutter backend. Other clutter apps may have the same problem.
+ When launching totem under xmir, it's menus don't react to mouse clicks.
Needs investigation.
** Description changed:
- When launching totem under xmir, it's menus don't react to mouse clicks.
+ When launching totem ("Videos" in app drawer) under xmir, it's menus
+ don't react to mouse clicks.
Needs investigation.
--
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/1670796
Title:
totem's menus don't open under deb-based unity8
Status in Canonical System Image:
New
Status in unity8 package in Ubuntu:
New
Bug description:
When launching totem ("Videos" in app drawer) under xmir, it's menus
don't react to mouse clicks.
Needs investigation.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670796/+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 1653687] Re: No sound after some time
** Package changed: alsa-driver (Ubuntu) => alsa-lib (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1653687 Title: No sound after some time Status in alsa-lib package in Ubuntu: New Bug description: Since a few weeks the sound is suddenly stopping on my laptop after some time. This can happen when I play music with Spotify, talk with Skype or play with Steam. The only way to get the sound back is to restart the computer. I tried to follow the sound troubleshooting procedure (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) but it didn't solved my issue. Attached are the information generated by the also-info script and the pulseaudio log taken while the issue occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1653687/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
I just upgraded 16.04 to 16.10 and had to search and find the solution on my fucking smartphone instead of the PC because somebody decided to change the way the network manager *manages* the network interfaces. Good job, you've just wasted tens of people's hours for nothing. I hope somebody's really proud of themselves. I swear to god, as soon as Android manages to take a big chunk out of the Linux desktop market share, Ubuntu goes right out of the SSD on my machine. I've just about had enough of this crap. -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update
*** This bug is a duplicate of bug 1615871 *** https://bugs.launchpad.net/bugs/1615871 I am experiencing the same problem with chrome version 56.0.2924.87 (64-bit) and ubuntu 16.04 after the update to 16.04.2 chrome becames very slow in scrolling and loading pages when multiple chrome windows are opened in different workspaces. I am also not sure that this is a duplicated bug, or just a different one - uname -a: Linux nbbag7 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux glxinfo: name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 515 (Skylake GT2) (0x191e) Version: 12.0.6 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.3 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 515 (Skylake GT2) OpenGL core profile version string: 4.3 (Core Profile) Mesa 12.0.6 OpenGL core profile shading language version string: 4.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 3.0 Mesa 12.0.6 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.1 Mesa 12.0.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10 -- 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/1628866 Title: After upgrading to 16.10, Chrome has become unusable because of extremely slow update Status in X.Org X server: Unknown Status in xorg package in Ubuntu: Confirmed Bug description: Both Chrome and Firefox actually were extremely slow regarding visual update (1 second after clicking a tab, lagging when entering text). Examining this old report: https://bugs.launchpad.net/ubuntu- gnome/+bug/1386721, I tried disbling bootloader graphics and VESA framebuffer, which suddenly made firefox behave as it used to, but chrome shows no improvement. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 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 CurrentDesktop: Unity:Unity7 Date: Thu Sep 29 12:19:56 2016 DistUpgraded: 2016-09-28 22:48:16,082 DEBUG icon theme changed, re-reading DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2227] InstallationDate: Installed on 2016-04-28 (153 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20BTS26N00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=96f314f8-7e1b-4d70-b372-84febb180710 ro vesafb.invalid=1 quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-09-28 (0 days ago) dmi.bios.date: 03/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET28W (1.06 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTS26N00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BTS26N00:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS26N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BTS26N00 dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 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
[Touch-packages] [Bug 1653687] Re: No sound after some time
** Attachment added: "alsa-info.txt.20170803" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1653687/+attachment/4833941/+files/alsa-info.txt.20170803 -- 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/1653687 Title: No sound after some time Status in alsa-driver package in Ubuntu: New Bug description: Since a few weeks the sound is suddenly stopping on my laptop after some time. This can happen when I play music with Spotify, talk with Skype or play with Steam. The only way to get the sound back is to restart the computer. I tried to follow the sound troubleshooting procedure (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) but it didn't solved my issue. Attached are the information generated by the also-info script and the pulseaudio log taken while the issue occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1653687/+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 1653687] Re: No sound after some time
Updated to 17.04, issue is still there. I think it comes from alsa driver instead of pulseaudio. ** Package changed: pulseaudio (Ubuntu) => alsa-driver (Ubuntu) -- 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/1653687 Title: No sound after some time Status in alsa-driver package in Ubuntu: New Bug description: Since a few weeks the sound is suddenly stopping on my laptop after some time. This can happen when I play music with Spotify, talk with Skype or play with Steam. The only way to get the sound back is to restart the computer. I tried to follow the sound troubleshooting procedure (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) but it didn't solved my issue. Attached are the information generated by the also-info script and the pulseaudio log taken while the issue occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1653687/+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 1653687] Re: No sound after some time
** Attachment added: "New logs after 17.04 update" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1653687/+attachment/4833942/+files/pulseverbose_20170803.log -- 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/1653687 Title: No sound after some time Status in alsa-driver package in Ubuntu: New Bug description: Since a few weeks the sound is suddenly stopping on my laptop after some time. This can happen when I play music with Spotify, talk with Skype or play with Steam. The only way to get the sound back is to restart the computer. I tried to follow the sound troubleshooting procedure (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) but it didn't solved my issue. Attached are the information generated by the also-info script and the pulseaudio log taken while the issue occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1653687/+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 1671193] Re: No sound after some time
*** This bug is a duplicate of bug 1653687 *** https://bugs.launchpad.net/bugs/1653687 Duplicate of https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1653687, can be closed ** This bug has been marked a duplicate of bug 1653687 No sound after some time -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1671193 Title: No sound after some time Status in pulseaudio package in Ubuntu: Invalid Bug description: Since a few months the sound is suddenly stopping on my laptop after some time. This can happen when I play music with Spotify, talk with Skype or play with Steam. The only way to get the sound back is to restart the computer or at least suspend it. I tried to follow the sound troubleshooting procedure (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) but it didn't solved my issue. Attached are the information generated by the also-info script and the pulseaudio log taken while the issue occurred. SIGINT signals the moment where the sound cuts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1671193/+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 1671193] [NEW] No sound after some time
*** This bug is a duplicate of bug 1653687 *** https://bugs.launchpad.net/bugs/1653687 Public bug reported: Since a few months the sound is suddenly stopping on my laptop after some time. This can happen when I play music with Spotify, talk with Skype or play with Steam. The only way to get the sound back is to restart the computer or at least suspend it. I tried to follow the sound troubleshooting procedure (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) but it didn't solved my issue. Attached are the information generated by the also-info script and the pulseaudio log taken while the issue occurred. SIGINT signals the moment where the sound cuts. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid ** Changed in: pulseaudio (Ubuntu) Status: Invalid => New ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1671193 Title: No sound after some time Status in pulseaudio package in Ubuntu: Invalid Bug description: Since a few months the sound is suddenly stopping on my laptop after some time. This can happen when I play music with Spotify, talk with Skype or play with Steam. The only way to get the sound back is to restart the computer or at least suspend it. I tried to follow the sound troubleshooting procedure (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) but it didn't solved my issue. Attached are the information generated by the also-info script and the pulseaudio log taken while the issue occurred. SIGINT signals the moment where the sound cuts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1671193/+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 1671159] Re: wget crashed with SIGSEGV
gdb output : Program received signal SIGSEGV, Segmentation fault. __memset_sse2 () at ../sysdeps/x86_64/multiarch/../memset.S:93 93 ../sysdeps/x86_64/multiarch/../memset.S: File not found ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1671159 Title: wget crashed with SIGSEGV Status in wget package in Ubuntu: New Bug description: wget crashed when I try to download one iso. a tried 2 different computer the status is the same. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: wget 1.17.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CrashCounter: 1 Date: Wed Mar 8 17:05:38 2017 ExecutablePath: /usr/bin/wget InstallationDate: Installed on 2015-08-17 (569 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: wget http://mirror.infotronik.hu/mirrors/linuxmint/iso/stable/18.1/linuxmint-18.1-mate-64bit.iso ProcEnviron: TERM=xterm-256color SHELL=/bin/bash PATH=(custom, no user) LANG=hu_HU.UTF-8 XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f80d3dde720 <__memset_sse2+144>:movdqa %xmm0,(%rcx) PC (0x7f80d3dde720) ok source "%xmm0" ok destination "(%rcx)" (0x561bd7d3) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: wget StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: wget crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2016-05-03 (308 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1671159/+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 1671155] Re: Autopilot tests that involve special keys fail
Replacing 'Ctrl+plus' with 'Ctrl+equal' does the trick, although it’s
not semantically equivalent.
--
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/1671155
Title:
Autopilot tests that involve special keys fail
Status in Autopilot:
New
Status in webbrowser-app package in Ubuntu:
New
Bug description:
I upgraded my laptop running xenial+overlay to yakkety then zesty
yesterday, and since then all webbrowser-app autopilot tests that
involve pressing special keys or key combinations (like 'Escape', 'F6'
or 'Ctrl+plus') are consistently failing:
Traceback (most recent call last):
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/tests/test_fullscreen.py",
line 70, in test_user_exit_ESC
self.main_window.press_key('Escape')
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/emulators/browser.py",
line 192, in press_key
self.keyboard.press_and_release(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 181,
in press_and_release
self.press(keys, delay)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 138,
in press
self._device.press(key_button)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 56,
in press
ecode = self._get_ecode_for_key(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 66,
in _get_ecode_for_key
raise ValueError('Unknown key name: %s.' % key)
ValueError: Unknown key name: Escape.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1671155/+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 1670745] Re: ssh-keyscan : bad host signature when using port option
Thanks for the bug report! Steps to reproduce: $ lxc launch ubuntu-daily:xenial xenial # edit /etc/ssh/sshd_config and change port to # service ssh restart # ip a to note container IP # exit $ ssh-keyscan -H -p The port will be in the output and not hashed as described in the report. The linked Github issue did state there is a workaround by getting the values unhashed and then hashing them in a second step. Not saying this is ideal, but it is a workaround: $ ssh-keyscan -p $ ssh-keygen -H -f .ssh/authorized_keys && rm .ssh/authorized_keys.old Because the man page for ssh-keyscan clearly states that -H will include the hostnames and addres and makes no mention of port in the hash, I have filed a bug with openssh to get clarity on the expected behavior and if this should be fixed. ** Bug watch added: OpenSSH Portable Bugzilla #2692 https://bugzilla.mindrot.org/show_bug.cgi?id=2692 ** Also affects: openssh via https://bugzilla.mindrot.org/show_bug.cgi?id=2692 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1670745 Title: ssh-keyscan : bad host signature when using port option Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: New Bug description: When I use the port option with ssh-keygen, the result is not compatible with ssh known_host file format. UBUNTU VERSION : lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 BAD : :~/.ssh$ cat /etc/issue Ubuntu 16.04.1 LTS \n \l :~/.ssh$ ssh-keyscan -v -p [...port...] -t ecdsa -H [...snip...] debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400 # [...snip...]:[...port...] SSH-2.0-OpenSSH_6.7p1 Debian-5+deb8u3 debug1: Enabling compatibility mode for protocol 2.0 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha...@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY [|1|BEEwVcggbNPf7fUydgU4O+BDoLg=|9SmWBUxFZkpR70Hqq8uqxLAzXFU=]:[...port...] ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= ==> we see the port number because it is not hashed ! GOOD : rm ~/.ssh/known_hosts :~/$ ssh -p [...port...] [...snip...] The authenticity of host '[[...snip...]]:[...port...] ([[...snip...]]:[...port...])' can't be established. ECDSA key fingerprint is SHA256:b/Jx+y3fNWFqOqTzFRI3XGrz33DBtAFFLmQaYQYFRnM. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '[[...snip...]]:[...port...],[[...snip...]]:[...port...]' (ECDSA) to the list of known hosts. [...snip...]@[...snip...]'s password: :~/$ !cat cat ~/.ssh/known_hosts |1|qdg91H9/DMHLO7yGOivI17+WFQI=|B+a6SrzF1GBd3XFvmAvQRnJxLWs= ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= |1|8I/vbrBV04VaUF12JXRwxvAL9So=|ToMf+kRwbSeNertVdUVuG3iLdH8= ecdsa-sha2-nistp256 E2VjZHNhLXNoYTItbmlzdHAyNTYIbmlzdHAyNTYAAABBBLEde+dZfL0TW6Z9jh+gOkW5fG/qeP9JAejKQXdmg9D7CH4NwMrWDEjXBDDo6iirIPAB6M0uUnK2mDw7uUWXYt8= ==> we cannot see the port number as it is well hashed ! REMARKS : == Same problem has already reported here (on macOS): https://github.com/ansible/ansible-modules-extras/issues/2651 It seems that ssh-keyscan version and open-ssh version differs : dpkg -l | grep openssh :: ii openssh-client 1:7.2p2-4ubuntu2.1 [...] ssh-keyscan -v [...] :: debug1: match: OpenSSH_6.7p1 Debian-5+deb8u3 pat OpenSSH* compat 0x0400 It is very annoying because I am trying to manage hand installed VMs with Ansible. For that I want to automate SSH host keys storing in known_hosts database. And because of this bug I can't. (ansible KIKIN project in development). Thank you, BR, Gautier HUSSON. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1670745/+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 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target
Details about different release vs. network backend requirements ** Attachment added: "lp1649931-release-network-matrix.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1649931/+attachment/4833940/+files/lp1649931-release-network-matrix.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1649931 Title: systemd-networkd needs to ensure DNS is up before network- online.target Status in resolvconf package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in resolvconf source package in Xenial: Fix Released Status in systemd source package in Xenial: Incomplete Status in resolvconf source package in Yakkety: Fix Committed Status in resolvconf package in Debian: Fix Committed Bug description: Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached. This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug. [SRU] Fix: switch resolvconf.service to run Before=network-pre.target and add Wants=network-pre.target. Add a Before=network-online.target to systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf with DNS config prior to reaching network-online.target. Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial. Test Case: lxc launch ubuntu-daily:xenial x1 lxc exec x1 /bin/bash # make sure you're on systemd-229-4ubuntu17 apt update && apt install -y systemd # enable networkd and netplan apt install -y nplan cat < /etc/netplan/nplan.yaml network: version: 2 ethernets: all-en: match: name: "en*" dhcp4: true all-eth: match: name: "eth*" dhcp4: true EOF sed -i.orig -e 's/^source/# source/' /etc/network/interfaces netplan generate # make sure cloud-init.service uses networkd sed -i.orig -e '/After=networking.service/a After=systemd-networkd-wait-online.service' /lib/systemd/system/cloud-init.service reboot # check that the order of execution with: journalctl -o short-precise --unit resolvconf.service --unit network-online.target --unit systemd-networkd-wait-online.service --unit systemd-networkd-resolvconf-update.service # the order should be: 1. resolvconf: systemd[1]: Started Nameserver information manager. 2. systemd-networkd-wait-online.service: systemd[1]: Starting Wait for Network to be Configured... 3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update resolvconf for networkd DNS. 4. network-online.target: systemd[1]: Reached target Network is Online. === BAD OUTPUT === On a failing system, Reached target Network is Online occurs before (1, 2, or 3) above, like this output: Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager. Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be Configured... Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd DNS... Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be Configured. Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online. Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd DNS. === GOOD OUTPUT === On a passing system, Reached target Network is Online occurs after 1, 2, and 3. Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager. Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be Configured... Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be Configured. Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd DNS... Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd DNS. Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931/+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 1649931] Re: systemd-networkd needs to ensure DNS is up before network-online.target
@racb I verified systemd 229-4ubuntu17 with both ifupdown and networkd configuration. The specific packages and features is somewhat complicated due to the different scenarios and change in networking behavior in yakkety+ I've attached a chart with details. Also viewable here: http://paste.ubuntu.com/24140363/ The tl;dr is for Xenial, we won't need another SRU as systemd-resolved is not enabled to manage DNS, rather resolvconf still controls /etc/resolv.conf In Yakkety+, systemd-resolved ends up owning /etc/resolv.conf and employs resolvconf to register itself therein. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1649931 Title: systemd-networkd needs to ensure DNS is up before network- online.target Status in resolvconf package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in resolvconf source package in Xenial: Fix Released Status in systemd source package in Xenial: Incomplete Status in resolvconf source package in Yakkety: Fix Committed Status in resolvconf package in Debian: Fix Committed Bug description: Currently resolvconf and systemd-networkd don't ensure DNS has been configured before allowing network-online.target to be reached. This was discussed in https://launchpad.net/bugs/1636912 however it was not a regression since there aren't any users of networkd + DNS early in boot at this time, it was requested that we move this DNS issue to a separate bug. [SRU] Fix: switch resolvconf.service to run Before=network-pre.target and add Wants=network-pre.target. Add a Before=network-online.target to systemd-networkd-resolvconf-update.service to ensure we update /etc/resolv.conf with DNS config prior to reaching network-online.target. Regression potential: Low. networkd is not widely being used outside of netplan/snappy in xenial. Test Case: lxc launch ubuntu-daily:xenial x1 lxc exec x1 /bin/bash # make sure you're on systemd-229-4ubuntu17 apt update && apt install -y systemd # enable networkd and netplan apt install -y nplan cat < /etc/netplan/nplan.yaml network: version: 2 ethernets: all-en: match: name: "en*" dhcp4: true all-eth: match: name: "eth*" dhcp4: true EOF sed -i.orig -e 's/^source/# source/' /etc/network/interfaces netplan generate # make sure cloud-init.service uses networkd sed -i.orig -e '/After=networking.service/a After=systemd-networkd-wait-online.service' /lib/systemd/system/cloud-init.service reboot # check that the order of execution with: journalctl -o short-precise --unit resolvconf.service --unit network-online.target --unit systemd-networkd-wait-online.service --unit systemd-networkd-resolvconf-update.service # the order should be: 1. resolvconf: systemd[1]: Started Nameserver information manager. 2. systemd-networkd-wait-online.service: systemd[1]: Starting Wait for Network to be Configured... 3. systemd-networkd-resolvconf-update.service: systemd[1]: Started Update resolvconf for networkd DNS. 4. network-online.target: systemd[1]: Reached target Network is Online. === BAD OUTPUT === On a failing system, Reached target Network is Online occurs before (1, 2, or 3) above, like this output: Dec 15 19:18:15.233443 x4 systemd[1]: Started Nameserver information manager. Dec 15 19:18:15.797857 x4 systemd[1]: Starting Wait for Network to be Configured... Dec 15 19:18:15.799573 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:18:15.804949 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:18:15.805079 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:18:29.100305 x4 systemd[1]: Starting Update resolvconf for networkd DNS... Dec 15 19:18:29.101870 x4 systemd[1]: Started Wait for Network to be Configured. Dec 15 19:18:29.102144 x4 systemd[1]: Reached target Network is Online. Dec 15 19:18:29.212842 x4 systemd[1]: Started Update resolvconf for networkd DNS. === GOOD OUTPUT === On a passing system, Reached target Network is Online occurs after 1, 2, and 3. Dec 15 19:28:42.548545 x4 systemd[1]: Started Nameserver information manager. Dec 15 19:28:43.144389 x4 systemd[1]: Starting Wait for Network to be Configured... Dec 15 19:28:43.146155 x4 systemd-networkd-wait-online[145]: ignoring: lo Dec 15 19:28:56.081487 x4 systemd[1]: Started Wait for Network to be Configured. Dec 15 19:28:56.100353 x4 systemd[1]: Starting Update resolvconf for networkd DNS... Dec 15 19:28:56.124005 x4 systemd[1]: Started Update resolvconf for networkd DNS. Dec 15 19:28:56.124555 x4 systemd[1]: Reached target Network is Online. To manage notifications about this bug go to:
[Touch-packages] [Bug 1671155] Re: Autopilot tests that involve special keys fail
And I haven’t yet found a working replacement for the 'Ctrl+plus' key
combination ('Ctrl+minus' seems to be working fine).
--
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/1671155
Title:
Autopilot tests that involve special keys fail
Status in Autopilot:
New
Status in webbrowser-app package in Ubuntu:
New
Bug description:
I upgraded my laptop running xenial+overlay to yakkety then zesty
yesterday, and since then all webbrowser-app autopilot tests that
involve pressing special keys or key combinations (like 'Escape', 'F6'
or 'Ctrl+plus') are consistently failing:
Traceback (most recent call last):
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/tests/test_fullscreen.py",
line 70, in test_user_exit_ESC
self.main_window.press_key('Escape')
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/emulators/browser.py",
line 192, in press_key
self.keyboard.press_and_release(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 181,
in press_and_release
self.press(keys, delay)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 138,
in press
self._device.press(key_button)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 56,
in press
ecode = self._get_ecode_for_key(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 66,
in _get_ecode_for_key
raise ValueError('Unknown key name: %s.' % key)
ValueError: Unknown key name: Escape.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1671155/+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 1671155] Re: Autopilot tests that involve special keys fail
I’m observing that references to 'Ctrl+Page_Down' don’t work any longer,
changing them to 'Ctrl+PageDown' fix the issue (had to remove the
underscore from 'Page_Down', and same for 'Page_Up').
** Summary changed:
- Autopilot tests that involve special keys fail on zesty
+ Autopilot tests that involve special keys fail
--
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/1671155
Title:
Autopilot tests that involve special keys fail
Status in Autopilot:
New
Status in webbrowser-app package in Ubuntu:
New
Bug description:
I upgraded my laptop running xenial+overlay to yakkety then zesty
yesterday, and since then all webbrowser-app autopilot tests that
involve pressing special keys or key combinations (like 'Escape', 'F6'
or 'Ctrl+plus') are consistently failing:
Traceback (most recent call last):
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/tests/test_fullscreen.py",
line 70, in test_user_exit_ESC
self.main_window.press_key('Escape')
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/emulators/browser.py",
line 192, in press_key
self.keyboard.press_and_release(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 181,
in press_and_release
self.press(keys, delay)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 138,
in press
self._device.press(key_button)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 56,
in press
ecode = self._get_ecode_for_key(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 66,
in _get_ecode_for_key
raise ValueError('Unknown key name: %s.' % key)
ValueError: Unknown key name: Escape.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1671155/+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 1671155] Re: Autopilot tests that involve special keys fail on zesty
** Changed in: autopilot
Assignee: (unassigned) => Santiago Baldassin (sbaldassin)
** Changed in: autopilot
Importance: Undecided => High
--
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/1671155
Title:
Autopilot tests that involve special keys fail on zesty
Status in Autopilot:
New
Status in webbrowser-app package in Ubuntu:
New
Bug description:
I upgraded my laptop running xenial+overlay to yakkety then zesty
yesterday, and since then all webbrowser-app autopilot tests that
involve pressing special keys or key combinations (like 'Escape', 'F6'
or 'Ctrl+plus') are consistently failing:
Traceback (most recent call last):
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/tests/test_fullscreen.py",
line 70, in test_user_exit_ESC
self.main_window.press_key('Escape')
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/emulators/browser.py",
line 192, in press_key
self.keyboard.press_and_release(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 181,
in press_and_release
self.press(keys, delay)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 138,
in press
self._device.press(key_button)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 56,
in press
ecode = self._get_ecode_for_key(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 66,
in _get_ecode_for_key
raise ValueError('Unknown key name: %s.' % key)
ValueError: Unknown key name: Escape.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1671155/+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 1670670] Re: Unity8 pointer does not stay in sync with Qemu VM tablet input
** Changed in: mir (Ubuntu) Status: Invalid => Confirmed -- 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/1670670 Title: Unity8 pointer does not stay in sync with Qemu VM tablet input Status in Canonical System Image: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Each time you login, or come back from the lock screen, you need to "recalibrate" the pointer by carefully moving the pointer into each corner. Contrast this with unity7, where the absolute position of the virtual tablet pointer is tracked, and sync is never lost. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670670/+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 1663062] Re: [regression] Software clients of nested servers with size >=480x480 are all black in Mir 0.25.0 and later (or stretched and distorted under Unity8)
@vanvugt - if that happens, it's just bug cruft from my wholesale marking. feel free to mark "fix released" if appropriate -- 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/1663062 Title: [regression] Software clients of nested servers with size >=480x480 are all black in Mir 0.25.0 and later (or stretched and distorted under Unity8) Status in Canonical System Image: Fix Released Status in Mir: Fix Committed Status in Mir 0.25 series: Won't Fix Status in Mir 0.26 series: Fix Released Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Fix Released Bug description: GPU apps seem to work. CPU apps all get black screen. To repro : Under unity7 using mir-on-x: 1- In a terminal, run : mir_demo_server -f /tmp/mysock 2- In another terminal, run : mir_demo_server --host-socket /tmp/mysock 3- In another terminal, run : mir_demo_client_progressbar Under Unity8 : In another terminal, run : mir_demo_client_progressbar Observe that, the window is black. Whereas, egl clients run fine. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1663062/+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 1671042] Re: Support application indicators for Unity8
** Tags added: unity8-desktop ** Also affects: canonical-devices-system-image 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/1671042 Title: Support application indicators for Unity8 Status in Canonical System Image: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Incomplete Bug description: It seems there's no plan to support application indicators for Unity8 I have an application called rsibreak https://userbase.kde.org/RSIBreak It tells you to stop typing/using the mouse for 20 seconds after every 10 minutes of use. Basically the application has no window, just a statistics dialog and a configure dialog. The "view" of the application is the application indicator that contains a graphic display that shows how much time is left for the next break. If we don't support application indicators the user will not see anything after he launches the application. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671042/+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 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings
@Yutani - would you mind reporting on the two diffs to upstream to Debian and
mention the bug number here?
- After=syslog.target which might be reasonable to pick
- PIDFile=/var/run/keepalived.pid (which is not bad and we thought would
If you are unwilling or unable let me know, but it would be a great help
if you could do so.
For SRU later this might get interesting. Usually an SUR requires the fix to be
in the latest Release - but it is "fixed" in Zesty, yet not with the code that
we might SRU back then (PIDFile).
If possible I'm waiting for the systemd info to show up here to get the bigger
picture.
--
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/1644530
Title:
keepalived fails to restart cleanly due to the wrong systemd settings
Status in keepalived package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
New
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
New
Bug description:
Because "PIDFile=" directive is missing in the systemd unit file,
keepalived sometimes fails to kill all old processes. The old
processes remain with old settings and cause unexpected behaviors. The
detail of this bug is described in this ticket in upstream:
https://github.com/acassen/keepalived/issues/443.
The official systemd unit file is available since version 1.2.24 by
this commit:
https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15
This includes "PIDFile" directive correctly:
PIDFile=/var/run/keepalived.pid
We should go the same way.
I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic.
Package: keepalived
Version: 1.2.19-1
===
How to reproduce:
I used the two instances of Ubuntu 16.04.2 on DigitalOcean:
Configurations
--
MASTER server's /etc/keepalived/keepalived.conf:
vrrp_script chk_nothing {
script "/bin/true"
interval 2
}
vrrp_instance G1 {
interface eth1
state BACKUP
priority 100
virtual_router_id 123
unicast_src_ip
unicast_peer {
}
track_script {
chk_nothing
}
}
BACKUP server's /etc/keepalived/keepalived.conf:
vrrp_script chk_nothing {
script "/bin/true"
interval 2
}
vrrp_instance G1 {
interface eth1
state MASTER
priority 200
virtual_router_id 123
unicast_src_ip
unicast_peer {
}
track_script {
chk_nothing
}
}
Loop based probing for the Error to exist:
--
After the setup above start keepalived on both servers:
$ sudo systemctl start keepalived.service
Then run the following loop
$ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo
systemctl restart keepalived; sudo systemctl status keepalived | egrep
'Main.*exited'; done; done
Expected: no error, only time reports
Error case: Showing Main PID exited, details below
Step by Step Procedures
---
1) Start keepalived on both servers
$ sudo systemctl start keepalived.service
2) Restart keepalived on either one
$ sudo systemctl restart keepalived.service
3) Check status and PID
$ systemctl status -n0 keepalived.service
Result
--
0) Before restart
Main PID is 3402 and the subprocesses' PIDs are 3403-3406. So far so
good.
root@ubuntu-2gb-sgp1-01:~# systemctl status -n0 keepalived
● keepalived.service - Keepalive Daemon (LVS and VRRP)
Loaded: loaded (/lib/systemd/system/keepalived.service; enabled; vendor
preset: enabled)
Active: active (running) since Sat 2017-03-04 01:37:12 UTC; 14min ago
Process: 3402 ExecStart=/usr/sbin/keepalived $DAEMON_ARGS (code=exited,
status=0/SUCCESS)
Main PID: 3403 (keepalived)
Tasks: 3
Memory: 1.7M
CPU: 1.900s
CGroup: /system.slice/keepalived.service
├─3403 /usr/sbin/keepalived
├─3405 /usr/sbin/keepalived
└─3406 /usr/sbin/keepalived
1) First restart
Now Main PID is 3403, which was one of the previous subprocesses and
is actually exited. Something is wrong. Yet, the previous processes
are all exited; we are not likely to see no weird behaviors here.
root@ubuntu-2gb-sgp1-01:~# systemctl restart keepalived
root@ubuntu-2gb-sgp1-01:~# systemctl status -n0 keepalived
● keepalived.service - Keepalive Daemon (LVS and VRRP)
Loaded: loaded (/lib/systemd/system/keepalived.service; enabled; vendor
preset: enabled)
Active: active (running) since Sat 2017-03-04 01:51:45 UTC; 1s ago
Process: 4782 ExecStart=/usr/sbin/keepalived $DAEMON_ARGS (code=exited,
status=0/SUCCESS)
Main
[Touch-packages] [Bug 1671069] Re: touch menus should show more to the right when launcher is visible
** Tags added: unity8-desktop -- 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/1671069 Title: touch menus should show more to the right when launcher is visible Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: To not have this problem http://i.imgur.com/pYXv05G.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671069/+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 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work
definitely - just tested, it's fixed. ** Changed in: canonical-devices-system-image Status: Incomplete => Fix Released ** No longer affects: xorg-server (Ubuntu RTM) ** No longer affects: libertine (Ubuntu) -- 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/1591356 Title: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work Status in Canonical System Image: Fix Released Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-lts-xenial package in Ubuntu: Invalid Status in gtk+3.0 source package in Trusty: New Status in libertine source package in Trusty: New Status in xorg-server source package in Trusty: Invalid Status in xorg-server-lts-xenial source package in Trusty: Fix Committed Status in gtk+3.0 source package in Xenial: New Status in libertine source package in Xenial: New Status in xorg-server source package in Xenial: Fix Released Status in xorg-server-lts-xenial source package in Xenial: Invalid Bug description: [Impact] Auto key repeating does not work in Libertine X apps which is very frustrating to users. [Test Case] 1. Install xterm in libertine 2. Start xterm from the "Xapps" scope 3. Wait for xterm to appear 4. Press and hold a key See how it only appears once and not multiple times as it should. [Regression Potential] Non observed. Original Description: How to reproduce: * Install xterm in libertine * Start xterm from the "Xapps" scope * Wait for xterm to appear * Press and hold a key * See how it only appears once and not multiple times as it should To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+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 1670327] Re: [unity8] application switcher - feature missing, add Q to close selected/highlighted app
** Changed in: unity8 (Ubuntu) Status: Triaged => 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/1670327 Title: [unity8] application switcher - feature missing, add Q to close selected/highlighted app Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: In Progress Bug description: Ubuntu 17.04 Unity8 [unity8] application switcher - feature missing, add Q to close selected/highlighted app in unity7 when in app switcher (ALT TAB), you can just press Q to close the current/selected/highlighter app. open some apps, ALT TAB, select whatever app and then press Q. the app closes To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670327/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
@louis-bouchard
I'd love to help you, but I'm in rush on my current job.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Yakkety:
Fix Committed
Status in unattended-upgrades package in Debian:
New
Bug description:
[SRU justification]
This fix is needed to make sure that the system does not hang on shutdown
when /var is a speparate file system
[Impact]
System can hang up to 10 minutes if not fixed.
[Fix]
Change the systemd unit's ExecStart to an ExecStop so the unit is correctly
sequenced.
[Test Case]
In a VM with /var separated from the / file system, shutdown the VM. It will
hang for 10 minutes
[Regression]
None to be expected. A ExecStop unit will be sequenced before the Before=
units which is earlier than previously.
[Original description of the problem]
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all
filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in
progress
and the service will wait until it finishes (and therefore automatically wait
at
shutdown).
However, if /var is a separate filesystem, it will get unmounted even though
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5
seconds, and
tries to check the lockfile again. After 10 minutes (the default timeout), it
will finally
exit and the system will continue shutdown.
The problem is the error handling in
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:
while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True
The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an
error.
File descriptors are just C file descriptors, so they are always positive
integers.
The code should check the result to be negative, not positive. I have
attached a patch
to reverse the logic.
Additional information:
1)
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2)
unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
*** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
100 /var/lib/dpkg/status
0.90 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
3)
Fast reboot
4)
Very slow reboot (after a 10 minutes timeout)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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 1644530] Re: keepalived fails to restart cleanly due to the wrong systemd settings
I can confirm that the adding of a PIDFile as suggested makes it survive the
looped test.
We should try to understand the changes behind it working in zesty.
But sooner or later adding the PIDFile might be the less invasive option
to make it working in an SRU.
--
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/1644530
Title:
keepalived fails to restart cleanly due to the wrong systemd settings
Status in keepalived package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
New
Status in keepalived source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
New
Bug description:
Because "PIDFile=" directive is missing in the systemd unit file,
keepalived sometimes fails to kill all old processes. The old
processes remain with old settings and cause unexpected behaviors. The
detail of this bug is described in this ticket in upstream:
https://github.com/acassen/keepalived/issues/443.
The official systemd unit file is available since version 1.2.24 by
this commit:
https://github.com/acassen/keepalived/commit/635ab69afb44cd8573663e62f292c6bb84b44f15
This includes "PIDFile" directive correctly:
PIDFile=/var/run/keepalived.pid
We should go the same way.
I am using Ubuntu 16.04.1, kernel 4.4.0-45-generic.
Package: keepalived
Version: 1.2.19-1
===
How to reproduce:
I used the two instances of Ubuntu 16.04.2 on DigitalOcean:
Configurations
--
MASTER server's /etc/keepalived/keepalived.conf:
vrrp_script chk_nothing {
script "/bin/true"
interval 2
}
vrrp_instance G1 {
interface eth1
state BACKUP
priority 100
virtual_router_id 123
unicast_src_ip
unicast_peer {
}
track_script {
chk_nothing
}
}
BACKUP server's /etc/keepalived/keepalived.conf:
vrrp_script chk_nothing {
script "/bin/true"
interval 2
}
vrrp_instance G1 {
interface eth1
state MASTER
priority 200
virtual_router_id 123
unicast_src_ip
unicast_peer {
}
track_script {
chk_nothing
}
}
Loop based probing for the Error to exist:
--
After the setup above start keepalived on both servers:
$ sudo systemctl start keepalived.service
Then run the following loop
$ for j in $(seq 1 20); do sleep 11s; time for i in $(seq 1 5); do sudo
systemctl restart keepalived; sudo systemctl status keepalived | egrep
'Main.*exited'; done; done
Expected: no error, only time reports
Error case: Showing Main PID exited, details below
Step by Step Procedures
---
1) Start keepalived on both servers
$ sudo systemctl start keepalived.service
2) Restart keepalived on either one
$ sudo systemctl restart keepalived.service
3) Check status and PID
$ systemctl status -n0 keepalived.service
Result
--
0) Before restart
Main PID is 3402 and the subprocesses' PIDs are 3403-3406. So far so
good.
root@ubuntu-2gb-sgp1-01:~# systemctl status -n0 keepalived
● keepalived.service - Keepalive Daemon (LVS and VRRP)
Loaded: loaded (/lib/systemd/system/keepalived.service; enabled; vendor
preset: enabled)
Active: active (running) since Sat 2017-03-04 01:37:12 UTC; 14min ago
Process: 3402 ExecStart=/usr/sbin/keepalived $DAEMON_ARGS (code=exited,
status=0/SUCCESS)
Main PID: 3403 (keepalived)
Tasks: 3
Memory: 1.7M
CPU: 1.900s
CGroup: /system.slice/keepalived.service
├─3403 /usr/sbin/keepalived
├─3405 /usr/sbin/keepalived
└─3406 /usr/sbin/keepalived
1) First restart
Now Main PID is 3403, which was one of the previous subprocesses and
is actually exited. Something is wrong. Yet, the previous processes
are all exited; we are not likely to see no weird behaviors here.
root@ubuntu-2gb-sgp1-01:~# systemctl restart keepalived
root@ubuntu-2gb-sgp1-01:~# systemctl status -n0 keepalived
● keepalived.service - Keepalive Daemon (LVS and VRRP)
Loaded: loaded (/lib/systemd/system/keepalived.service; enabled; vendor
preset: enabled)
Active: active (running) since Sat 2017-03-04 01:51:45 UTC; 1s ago
Process: 4782 ExecStart=/usr/sbin/keepalived $DAEMON_ARGS (code=exited,
status=0/SUCCESS)
Main PID: 3403 (code=exited, status=0/SUCCESS)
Tasks: 3
Memory: 1.7M
CPU: 11ms
CGroup: /system.slice/keepalived.service
├─4783 /usr/sbin/keepalived
├─4784 /usr/sbin/keepalived
└─4785 /usr/sbin/keepalived
2) Second restart
Now Main PID is 4783 and subprocesses' PIDs are
[Touch-packages] [Bug 1670652] Re: No way to contain pointer in VM window
** Changed in: canonical-devices-system-image Status: Invalid => Incomplete ** Changed in: mir (Ubuntu) Status: Invalid => Incomplete ** Changed in: unity8 (Ubuntu) Status: Invalid => Incomplete ** Changed in: qemu (Ubuntu) Status: Invalid => 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/1670652 Title: No way to contain pointer in VM window Status in Canonical System Image: Incomplete Status in mir package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: In a Qemu VM, the unity8 side gestures (for the launcher and app switcher) cannot be activated. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670652/+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 1671155] Re: Autopilot tests that involve special keys fail on zesty
And changing references to function keys such as 'F11' to 'f11' fixes
that case too.
References to Ctrl+ combinations are still failing.
--
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/1671155
Title:
Autopilot tests that involve special keys fail on zesty
Status in Autopilot:
New
Status in webbrowser-app package in Ubuntu:
New
Bug description:
I upgraded my laptop running xenial+overlay to yakkety then zesty
yesterday, and since then all webbrowser-app autopilot tests that
involve pressing special keys or key combinations (like 'Escape', 'F6'
or 'Ctrl+plus') are consistently failing:
Traceback (most recent call last):
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/tests/test_fullscreen.py",
line 70, in test_user_exit_ESC
self.main_window.press_key('Escape')
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/emulators/browser.py",
line 192, in press_key
self.keyboard.press_and_release(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 181,
in press_and_release
self.press(keys, delay)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 138,
in press
self._device.press(key_button)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 56,
in press
ecode = self._get_ecode_for_key(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 66,
in _get_ecode_for_key
raise ValueError('Unknown key name: %s.' % key)
ValueError: Unknown key name: Escape.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1671155/+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 1580916] Re: LIstitem dividers not shown for new items.
*** This bug is a duplicate of bug 1665559 *** https://bugs.launchpad.net/bugs/1665559 ** This bug has been marked a duplicate of bug 1665559 UbuntuListView dividers don't get updated on model changes -- 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/1580916 Title: LIstitem dividers not shown for new items. Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Newly added listitems don't show a divider. Expected Behavior: All list view items include a divide between items. no divider on the bottom of the last item. Experienced Behavior: No dividers are shown for newly added items. The dividers are shown if the page is reopened with an existing model, but any subsequently added items do not have a divider. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1580916/+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 1665286] Re: [unity8] A ghost (shadow only) window opens with some app windows/menus
** Changed in: canonical-devices-system-image Status: Incomplete => In Progress -- 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/1665286 Title: [unity8] A ghost (shadow only) window opens with some app windows/menus Status in Canonical System Image: In Progress Status in Mir: Incomplete Status in MirAL: Incomplete Status in mir package in Ubuntu: Incomplete Status in miral package in Ubuntu: Incomplete Status in qtubuntu package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: ubuntu 17.04 unity8 install tiled, apt install tiled launch tiled, you'll see a transparent window opened beneath the main window called "Object Types Editor" see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1665286/+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 1670670] Re: Unity8 pointer does not stay in sync with Qemu VM tablet input
> AFAIK the only thing stopping us from using Mir's native input coordinates > was the inability to implement barriers/edge resistance in places. We had other use-cases where unity8 having control over mouse position was useful. One example coming to mind is phone docked to an external display, we wanted to limit the cursor to the external display only. And we had a few other pie-in-the-sky design ideas which would be much easier if unity8 had cursor control. I still don't see why Mir can't just let Unity8 (a nested) position the cursor (like it could, if it were a host server)! And absolute vs relative. If we're doing it wrong, we can fix it. -- 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/1670670 Title: Unity8 pointer does not stay in sync with Qemu VM tablet input Status in Canonical System Image: Confirmed Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Each time you login, or come back from the lock screen, you need to "recalibrate" the pointer by carefully moving the pointer into each corner. Contrast this with unity7, where the absolute position of the virtual tablet pointer is tracked, and sync is never lost. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670670/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
@kay-diam:
I get what you mean. I also use KVM to debug the issue.
I'm going to switch to verification-failed to this one does not get
released and push the investigation further as there is another issue
that side-tracked me :
If Unattended-Upgrade::InstallOnShutdown is set to "true", it will still
fail as the network will no longer be available when it gets to access
the archive so this must also be fixed.
...Louis
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Yakkety:
Fix Committed
Status in unattended-upgrades package in Debian:
New
Bug description:
[SRU justification]
This fix is needed to make sure that the system does not hang on shutdown
when /var is a speparate file system
[Impact]
System can hang up to 10 minutes if not fixed.
[Fix]
Change the systemd unit's ExecStart to an ExecStop so the unit is correctly
sequenced.
[Test Case]
In a VM with /var separated from the / file system, shutdown the VM. It will
hang for 10 minutes
[Regression]
None to be expected. A ExecStop unit will be sequenced before the Before=
units which is earlier than previously.
[Original description of the problem]
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all
filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in
progress
and the service will wait until it finishes (and therefore automatically wait
at
shutdown).
However, if /var is a separate filesystem, it will get unmounted even though
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5
seconds, and
tries to check the lockfile again. After 10 minutes (the default timeout), it
will finally
exit and the system will continue shutdown.
The problem is the error handling in
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:
while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True
The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an
error.
File descriptors are just C file descriptors, so they are always positive
integers.
The code should check the result to be negative, not positive. I have
attached a patch
to reverse the logic.
Additional information:
1)
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2)
unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
*** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
100 /var/lib/dpkg/status
0.90 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
3)
Fast reboot
4)
Very slow reboot (after a 10 minutes timeout)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
BTW, KVM allows you to use serial console you can use it for debugging.
But you have explicitly specify the order of defined "console" kernel
parameters, i.e.:
this will specify VGA console as default output:
console=ttyS0 console=tty1
this will specify serial console as default output:
console=tty1 console=ttyS0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Yakkety:
Fix Committed
Status in unattended-upgrades package in Debian:
New
Bug description:
[SRU justification]
This fix is needed to make sure that the system does not hang on shutdown
when /var is a speparate file system
[Impact]
System can hang up to 10 minutes if not fixed.
[Fix]
Change the systemd unit's ExecStart to an ExecStop so the unit is correctly
sequenced.
[Test Case]
In a VM with /var separated from the / file system, shutdown the VM. It will
hang for 10 minutes
[Regression]
None to be expected. A ExecStop unit will be sequenced before the Before=
units which is earlier than previously.
[Original description of the problem]
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all
filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in
progress
and the service will wait until it finishes (and therefore automatically wait
at
shutdown).
However, if /var is a separate filesystem, it will get unmounted even though
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5
seconds, and
tries to check the lockfile again. After 10 minutes (the default timeout), it
will finally
exit and the system will continue shutdown.
The problem is the error handling in
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:
while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True
The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an
error.
File descriptors are just C file descriptors, so they are always positive
integers.
The code should check the result to be negative, not positive. I have
attached a patch
to reverse the logic.
Additional information:
1)
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2)
unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
*** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
100 /var/lib/dpkg/status
0.90 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
3)
Fast reboot
4)
Very slow reboot (after a 10 minutes timeout)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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 1665286] Re: [unity8] A ghost (shadow only) window opens with some app windows/menus
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Daniel d'Andrada (dandrader) ** Changed in: qtubuntu (Ubuntu) Assignee: (unassigned) => Daniel d'Andrada (dandrader) ** Changed in: qtubuntu (Ubuntu) Status: Confirmed => In Progress ** 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 mir in Ubuntu. https://bugs.launchpad.net/bugs/1665286 Title: [unity8] A ghost (shadow only) window opens with some app windows/menus Status in Canonical System Image: Incomplete Status in Mir: Incomplete Status in MirAL: Incomplete Status in mir package in Ubuntu: Incomplete Status in miral package in Ubuntu: Incomplete Status in qtubuntu package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: ubuntu 17.04 unity8 install tiled, apt install tiled launch tiled, you'll see a transparent window opened beneath the main window called "Object Types Editor" see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1665286/+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 1669880] Re: [unity8] Launcher navigation stops working if you open the app drawer
** Changed in: unity8 (Ubuntu) Status: Triaged => 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/1669880 Title: [unity8] Launcher navigation stops working if you open the app drawer Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: In Progress Bug description: ubuntu 17.04 Unity 8 first, DO NOT OPEN THE APP DRAWER. press ALT F1, now you should see the a blue outline on the ubuntu logo, now press TAB or the Arrow key UP and DOWN to navigate. now open the app drawer with the mouse or SUPER A then close the app drower. now try to navigate again. ALT F1 and then up/down or tab. it doesn't work anymore. workaround: right click on the launcher to probably give focus again or something To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669880/+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 1669880] Re: [unity8] Launcher navigation stops working if you open the app drawer
** Branch linked: lp:~mzanetti/unity8/fix-launcher-focus -- 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/1669880 Title: [unity8] Launcher navigation stops working if you open the app drawer Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: In Progress Bug description: ubuntu 17.04 Unity 8 first, DO NOT OPEN THE APP DRAWER. press ALT F1, now you should see the a blue outline on the ubuntu logo, now press TAB or the Arrow key UP and DOWN to navigate. now open the app drawer with the mouse or SUPER A then close the app drower. now try to navigate again. ALT F1 and then up/down or tab. it doesn't work anymore. workaround: right click on the launcher to probably give focus again or something To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1669880/+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 1671155] Re: Autopilot tests that involve special keys fail on zesty
This also occurs for me on xenial+overlay, but i have found changing the
key from "Escape" to "Esc" fixes the problem.
--
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/1671155
Title:
Autopilot tests that involve special keys fail on zesty
Status in Autopilot:
New
Status in webbrowser-app package in Ubuntu:
New
Bug description:
I upgraded my laptop running xenial+overlay to yakkety then zesty
yesterday, and since then all webbrowser-app autopilot tests that
involve pressing special keys or key combinations (like 'Escape', 'F6'
or 'Ctrl+plus') are consistently failing:
Traceback (most recent call last):
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/tests/test_fullscreen.py",
line 70, in test_user_exit_ESC
self.main_window.press_key('Escape')
File
"/build/webbrowser-app/staging/tests/autopilot/webbrowser_app/emulators/browser.py",
line 192, in press_key
self.keyboard.press_and_release(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 181,
in press_and_release
self.press(keys, delay)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 138,
in press
self._device.press(key_button)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 56,
in press
ecode = self._get_ecode_for_key(key)
File "/usr/lib/python3/dist-packages/autopilot/input/_uinput.py", line 66,
in _get_ecode_for_key
raise ValueError('Unknown key name: %s.' % key)
ValueError: Unknown key name: Escape.
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1671155/+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 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
@louis-bouchard
"Started Unattended Upgrades Shutdown." means that the unit was started.
Since the patch assumes that we don't use "ExecStart" this means
nothing.
Upgrade procedure should be executed on "ExecStop". But it is not
happening. I tried to set debug info inside the "ExecStop" instead of
executing "unattended-upgrade-shutdown", but it doesn't work. I can
provide you with the detailed step-by-step instructions on how to 100%
reproduce the issue, but it will require KVM host, and running my
scripts which will deploy VM with LVM.
Basic steps:
* follow https://github.com/kayrus/deploy-vm docs
* git clone https://github.com/kayrus/deploy-vm
* cd deploy-vm
* ./deploy_vms_cluster.sh -o ubuntu -c xenial
* follow https://github.com/kayrus/rescue-initramfs docs
* and reinstall VM from initramfs using "deploy_os_lvm.sh" script
Then your Xenial VM will stuck at reboot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1654600
Title:
unattended-upgrade-shutdown hangs when /var is a separate filesystem
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
Fix Committed
Status in unattended-upgrades source package in Yakkety:
Fix Committed
Status in unattended-upgrades package in Debian:
New
Bug description:
[SRU justification]
This fix is needed to make sure that the system does not hang on shutdown
when /var is a speparate file system
[Impact]
System can hang up to 10 minutes if not fixed.
[Fix]
Change the systemd unit's ExecStart to an ExecStop so the unit is correctly
sequenced.
[Test Case]
In a VM with /var separated from the / file system, shutdown the VM. It will
hang for 10 minutes
[Regression]
None to be expected. A ExecStop unit will be sequenced before the Before=
units which is earlier than previously.
[Original description of the problem]
The systemd unit file unattended-upgrades.service is used to stop a running
unattended-upgrade
process during shutdown. This unit file is running together with all
filesystem
unmount services.
The unattended-upgrades service checks if the lockfile for unattended-upgrade
(in /var/run) exists, and if it does, there is an unattended-upgrade in
progress
and the service will wait until it finishes (and therefore automatically wait
at
shutdown).
However, if /var is a separate filesystem, it will get unmounted even though
/var/run
is a tmpfs that's still mounted on top of the /var/run directory in the /var
filesystem.
The unattended-upgrade script will fail to find lockfile, sleeps for 5
seconds, and
tries to check the lockfile again. After 10 minutes (the default timeout), it
will finally
exit and the system will continue shutdown.
The problem is the error handling in
/usr/share/unattended-upgrades/unattended-upgrade-shutdown
where it tries to lock itself:
while True:
res = apt_pkg.get_lock(options.lock_file)
logging.debug("get_lock returned %i" % res)
# exit here if there is no lock
if res > 0:
logging.debug("lock not taken")
break
lock_was_taken = True
The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an
error.
File descriptors are just C file descriptors, so they are always positive
integers.
The code should check the result to be negative, not positive. I have
attached a patch
to reverse the logic.
Additional information:
1)
Description: Ubuntu 16.04.1 LTS
Release: 16.04
2)
unattended-upgrades:
Installed: 0.90ubuntu0.3
Candidate: 0.90ubuntu0.3
Version table:
*** 0.90ubuntu0.3 500
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386
Packages
100 /var/lib/dpkg/status
0.90 500
500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages
3)
Fast reboot
4)
Very slow reboot (after a 10 minutes timeout)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+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
