[Touch-packages] [Bug 1627248] Re: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 1600506 *** https://bugs.launchpad.net/bugs/1600506 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1600506, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1627248/+attachment/4747589/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1627248/+attachment/4747591/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1627248/+attachment/4747594/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1627248/+attachment/4747595/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1627248/+attachment/4747596/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1627248/+attachment/4747597/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1627248/+attachment/4747598/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1600506 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1627248 Title: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in mediascanner2 package in Ubuntu: New Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: mediascanner2.0 0.112+16.10.20160909-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-15-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 07:24:02 2016 ExecutablePath: /usr/bin/mediascanner-service-2.0 InstallationDate: Installed on 2015-04-30 (512 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/bin/mediascanner-service-2.0 Signal: 6 SourcePackage: mediascanner2 StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ScannerDaemon::setupBus() () SystemImageInfo: current build number: 0 device name: channel: daily last update: 2015-07-02 09:27:08 Title: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to yakkety on 2016-09-14 (9 days ago) UserGroups: adm audio cdrom dip libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1627248/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
Kyle, I agree (thank you!), but could you possible to say definitely -- what was a mistake: 1. thees actions: # cd ~/.local/share/libertine # rm ContainersConfig.json # cp /custom/click/.click/users/@all/com.ubuntu.puritine/libertine-config/libertine/ContainersConfig.json . or 2. some records in (I didn't remember if I edited it) /home/phablet/.local/share/libertine/ContainersConfig.json ?? And to be bug or not. If some utility, reading config files, does not check them and HANGS MAIN USER INTERFACE in place of ignoring mistakes or using default configuration -- is it not bug? -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: Invalid Status in Today Scope: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1619720] Re: Unity8 sometimes crashes after Bluetooth reconnect
Gents, I've exactly this problem when the second device got paired. Where do i find the logfile you need ? Mako last rc-proposed -- 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/1619720 Title: Unity8 sometimes crashes after Bluetooth reconnect Status in Canonical System Image: Confirmed Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: Test case. - In System Settings, pair a Bluetooth keyboard and mouse. - Wait some minutes so keyboard and mouse suspend. - Reboot the device. - Start typing on the password prompt and move the mouse. Expected result. - User can log in. Actual result. - Unity8 crashes. It's not an accurate test case but has happened at least three times in similar scenarios which involve waking up the keyboard (or mouse?). current build number: 180 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en With silo 37. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1619720/+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 1580219] Re: screen switches off
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1580219 Title: screen switches off Status in xorg package in Ubuntu: Expired Bug description: Hi, My computer is an ASUS X751L with a Dell monitor connected through VGA. I've just upgraded to 16.04 "Xenial" and rebooted. Now this external monitor often goes black when I mouse my mouse to the native LVDS screen. I've still not been able to find the exact conditions, but it seems to occur when I don't move the mouse for a long time, then move it to the other screen. The screen goes black and comes back quickly, as if I would have run "xset dpms force off". Also, from time to time, the upper part of my LVDS screen just "scrambles" (you know, like when the old cathodic TVs were trembling...) for a few seconds when I click on some keys on the keyboard (e.g. the CTL-ALT-ARROWS, which are associated to "Desktop"/Tag switching in my AwesomeWM config) For more info: # Executing a few commands found on another page (https://askubuntu.com/questions/28033/how-to-check-the-information-of-current-installed-video-drivers) to provide more info: $ lspci | grep VGA ; lsmod | grep "kms\|drm" ; find /dev -group video ; \ cat /proc/cmdline ; find /etc/modprobe.d/; cat /etc/modprobe.d/*kms* ; \ ls /etc/X11/xorg.conf ; glxinfo | grep -i "vendor\|rendering" ; \ grep LoadModule /var/log/Xorg.0.log 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) drm_kms_helper139264 1 i915 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops16384 1 drm_kms_helper drm 360448 5 i915,drm_kms_helper /dev/video0 find: ‘/dev/vboxusb’: Permission denied /dev/fb0 /dev/dri/card0 /dev/dri/renderD128 /dev/dri/controlD64 BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=a3c0bf21-3b98-45f2-8f95-2abd53cef1e7 ro quiet splash vt.handoff=7 /etc/modprobe.d/ /etc/modprobe.d/blacklist-rare-network.conf /etc/modprobe.d/blacklist-firewire.conf /etc/modprobe.d/mlx4.conf /etc/modprobe.d/fbdev-blacklist.conf /etc/modprobe.d/iwlwifi.conf /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/blacklist-ath_pci.conf /etc/modprobe.d/vmwgfx-fbdev.conf /etc/modprobe.d/intel-microcode-blacklist.conf /etc/modprobe.d/blacklist.conf /etc/modprobe.d/blacklist-framebuffer.conf /etc/modprobe.d/blacklist-oss.conf /etc/modprobe.d/dkms.conf /etc/modprobe.d/blacklist-watchdog.conf /etc/modprobe.d/blacklist-modem.conf /etc/modprobe.d/qemu-system-x86.conf # modprobe information used for DKMS modules # # This is a stub file, should be edited when needed, # used by default by DKMS. /bin/ls: cannot access '/etc/X11/xorg.conf': No such file or directory direct rendering: Yes server glx vendor string: SGI client glx vendor string: Mesa Project and SGI Vendor: Intel Open Source Technology Center (0x8086) OpenGL vendor string: Intel Open Source Technology Center [33.140] (II) LoadModule: "glx" [34.658] (II) LoadModule: "intel" [34.831] (II) LoadModule: "modesetting" [34.883] (II) LoadModule: "fbdev" [34.916] (II) LoadModule: "vesa" [34.989] (II) LoadModule: "fbdevhw" [35.092] (II) LoadModule: "dri2" [35.092] (II) LoadModule: "present" [39.380] (II) LoadModule: "evdev" [39.740] (II) LoadModule: "synaptics" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1580219/+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 1606071] Re: [HP ProBook 455 G3] Unable to boot
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1606071 Title: [HP ProBook 455 G3] Unable to boot Status in xorg package in Ubuntu: Expired Bug description: When using Ubuntu 16.04 I get a black screen immediately when booting up. I tried using kernel parameter amdgpu.runpm=0 Ubuntu boots up into the live Ubuntu with the correct resolution but after 5 minutes or so, I got the black screen again. This doesn't happen with 15.10 where the fglrx drivers are still available. My hardware: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:80ef] WORKAROUND: The following kernel parameter allows me to boot into low graphics mode: nomodeset ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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: Sun Jul 24 17:45:49 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201, 4.2.0-42-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:80ef] InstallationDate: Installed on 2016-07-23 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: HP HP ProBook 455 G3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed root=UUID=3995b7d0-4563-4eb7-b27b-220f98ff0526 ro nomodeset quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2016 dmi.bios.vendor: HP dmi.bios.version: N79 Ver. 01.11 dmi.board.name: 80EF dmi.board.vendor: HP dmi.board.version: KBC Version 92.49 dmi.chassis.asset.tag: 5CD6216FPW dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN79Ver.01.11:bd04/11/2016:svnHP:pnHPProBook455G3:pvr:rvnHP:rn80EF:rvrKBCVersion92.49:cvnHP:ct10:cvr: dmi.product.name: HP ProBook 455 G3 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.fglrx-installer: fglrx-installer N/A 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.1 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: Sun Jul 24 21:30:05 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1606071/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
WRT regression potential: 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. It is in widespread use; and the set of functionality used by ipconfig in the initramfs is very small, so unlikely to run into any problems as a result of behavior differences between ipconfig and dhclient. However, the risk is non-zero, and I consider it acceptable to change the dhcpv4 client from ipconfig to dhclient in SRU solely because we should also plan to solve 1) in the longer term, which is only possible by removing klibc-utils completely from the initramfs. Were this not the case, the preferred safer path would be to continue using ipconfig for ipv4 and use dhclient only for ipv6. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: New Status in open-iscsi package in Ubuntu: Fix Committed Status in initramfs-tools source package in Xenial: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in klibc source package in Xenial: New Status in open-iscsi source package in Xenial: Fix Committed Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1607531] Re: Music ignores local album artwork.
In my experience, most music programs and applications recognize "album title.supported_extension" as album artwork, usually in addition to the same or similar filename structures you list above... That was why I thought there was a bug. I agree that there is no bug here, though I still think there is a design flaw. I'll close this "bug" and raise a request for "album title.supported_extension" to be added to the "wishlist" for Music... Thanks for clearing that up though, Michi. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1607531 Title: Music ignores local album artwork. Status in Ubuntu Music App: Invalid Status in thumbnailer package in Ubuntu: Invalid Bug description: When using "Music", local album artwork is ignored, seemingly in favor of online album artwork, which is frequently incorrect. This appears to be a different issue to https://bugs.launchpad.net/thumbnailer/+bug/1372000 , because https://bugs.launchpad.net/thumbnailer/+bug/1372000 is apparently "fixed" and I still experience this issue. -- Reproduce: - Copy music to your Ubuntu mobile device, ensuring that each folder contains appropriately-named album artwork (in my case, exactly the same name as the album and the folder in which the music is contained). - Launch/open Music, browse your library and playback music. Result: - Most tracks are shown with no or incorrect album artwork. Expectation: - That Music would utilize or otherwise prioritize local album artwork. -- Music: 2.4.1003 bq Aquaris E5 HD Ubuntu Edition: * OS build number: OTA-12 * Ubuntu Image part: 20160708 * Ubuntu build description: Ubuntu 15.04 - armhf (20160708-091336) * Device Image part: 20160606-540a47f * Device build description: VEGETA01A-S23A_BQ_L100EN_2014_160708 * Customization Image part: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1607531/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Hello LaMont, or anyone else affected, Accepted initramfs-tools into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.122ubuntu8.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: initramfs-tools (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: open-iscsi (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: New Status in open-iscsi package in Ubuntu: Fix Committed Status in initramfs-tools source package in Xenial: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in klibc source package in Xenial: New Status in open-iscsi source package in Xenial: Fix Committed Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Please test proposed package
Hello LaMont, or anyone else affected, Accepted open-iscsi into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/open- iscsi/2.0.873+git0.3b4b4500-14ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: New Status in open-iscsi package in Ubuntu: Fix Committed Status in initramfs-tools source package in Xenial: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in klibc source package in Xenial: New Status in open-iscsi source package in Xenial: Fix Committed Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Description changed: - initramfs' configure_networking function uses ipconfig to configure the - network. - - ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi- - bin/bugreport.cgi?bug=627164 - - Anyone wanting to netboot in an ipv6-only environment is affected. + initramfs' configure_networking function uses ipconfig to configure the network. + ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: - * bug 1621615: network not configured when ipv6 netbooted into cloud-init + * bug 1229458: grub2 needed changes + * bug 1621615: network not configured when ipv6 netbooted into cloud-init + + [Impact] + + It is not possible to netboot Ubuntu with a network-based root + filesystem in an ipv6-only environment. Anyone wanting to netboot in an + ipv6-only environment is affected. + + These uploads address this by replacing the one-off klibc dhcp client + (IPv4-only) with the defacto standard isc-dhcp-client, and thereby + provide both ipv6 and ipv4 DHCP configuration. + + [Test Case] + + See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only + netbooting world. Pass the boot process an ipv6 address to talk to, and + see it fail to configure the network. + + [Regression Potential] + + 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. + 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: New Status in open-iscsi package in Ubuntu: Fix Committed Status in initramfs-tools source package in Xenial: New Status in isc-dhcp source package in Xenial: Fix Committed Status in klibc source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Hello LaMont, or anyone else affected, Accepted isc-dhcp into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/isc- dhcp/4.3.3-5ubuntu12.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: isc-dhcp (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: New Status in open-iscsi package in Ubuntu: Fix Committed Status in initramfs-tools source package in Xenial: New Status in isc-dhcp source package in Xenial: Fix Committed Status in klibc source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1626808] Re: Unable to log in from bq Aquaris tablet
thanks i will try this mark On 24 Sep 2016 6:01 AM, "Rodney Dawes" <1626...@bugs.launchpad.net> wrote: > Can you attach before/after screenshots? You should be able to take a > screenshot by pressing both Vol Up+Vol Dn at the same time. You should > be able to attach them to the bug via the browser on the M10 or transfer > them via USB to a PC for attaching to the bug. > > If you attach with USB and with developer mode enabled, you can use the > "phablet-shell" tool on Ubuntu to shell in to the tablet, and watch > /home/phablet/.cache/upstart/dbus.log while trying to log in. There may > be some indication of what's going on printed to this file while > attempting to log in. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1626808 > > Title: > Unable to log in from bq Aquaris tablet > > Status in Canonical SSO provider: > New > Status in ubuntuone-credentials package in Ubuntu: > New > > Bug description: > Hi > > I have five Aquaris tablets I am installing some new products I have > built onto. > > On one tablet, when I try to log in to the Ubuntu One so I can get the > terminal app, I enter my email and password (correct) to log in, but I > am not logged in and the terminal app does not download. > > Without the terminal app installed I cannot run any diagnostics or get > any information about what is going wrong. > > This setup, where terminal is not on the Tablet OS by default, totally > SUCKS. > > I need support urgently. > > I cannot provide log files to you or anything else. Presumably the > Ubuntu Web web site logs will say that I am trying to log in from a > Tablet device. I wish I had some logs myself... > > Mark Anson > > To manage notifications about this bug go to: > https://bugs.launchpad.net/canonical-identity-provider/+ > bug/1626808/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1626808 Title: Unable to log in from bq Aquaris tablet Status in Canonical SSO provider: New Status in ubuntuone-credentials package in Ubuntu: New Bug description: Hi I have five Aquaris tablets I am installing some new products I have built onto. On one tablet, when I try to log in to the Ubuntu One so I can get the terminal app, I enter my email and password (correct) to log in, but I am not logged in and the terminal app does not download. Without the terminal app installed I cannot run any diagnostics or get any information about what is going wrong. This setup, where terminal is not on the Tablet OS by default, totally SUCKS. I need support urgently. I cannot provide log files to you or anything else. Presumably the Ubuntu Web web site logs will say that I am trying to log in from a Tablet device. I wish I had some logs myself... Mark Anson To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/1626808/+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 1626394] Re: 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test)
This bug was fixed in the package linux - 4.8.0-16.17 --- linux (4.8.0-16.17) yakkety; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1626768 * Support ARM GIC ITS in ACPI mode (LP: #1626631) - [Config] CONFIG_ACPI_IORT=y - SAUCE: ACPI: I/O Remapping Table (IORT) initial support - SAUCE: ACPI: Add new IORT functions to support MSI domain handling - SAUCE: irqchip/gicv3-its: Cleanup for ITS domain initialization - SAUCE: irqchip/gicv3-its: Refactor ITS DT init code to prepare for ACPI - SAUCE: irqchip/gicv3-its: Probe ITS in the ACPI way - SAUCE: irqchip/gicv3-its: Factor out PCI-MSI part that might be reused for ACPI - SAUCE: irqchip/gicv3-its: Use MADT ITS subtable to do PCI/MSI domain initialization - SAUCE: PCI/MSI: Setup MSI domain on a per-device basis using IORT ACPI table * 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test) (LP: #1626394) - [Config] CONFIG_ATA=y * Yakkety: Enable drivers with respect to Xenial (LP: #1626543) - [Config] CONFIG_VMD=m - [Config] CONFIG_MAC80211_RC_MINSTREL_VHT=y for all arches - [Config] CONFIG_OF=y for all arches - [Config] CONFIG_BLK_DEV_NVME_SCSI=y - [Config] Xenial device settings sync with amd64 - [Config] Xenial device settings sync with i386 - [Config] CONFIG_MTD_UBI_GLUEBI=m - [Config] Xenial device settings sync with armhf - [Config] Xenial device settings sync with arm64 * yakkety 4.8, missing config CONFIG_USERFAULTFD=y (LP: #1626149) - [Config] CONFIG_USERFAULTFD=y * 4.8 regression: SLAB is being used instead of SLUB (LP: #1626564) - [Config] CONFIG_SLUB=y * image won't boot after upgrading to yakkety's 4.8 kernel because efi (LP: #1626158) - add nls_cp437 to the generic.inclusion-list -- Tim GardnerThu, 22 Sep 2016 06:51:45 -0600 ** Changed in: linux (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- 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/1626394 Title: 4.8 dropped CONFIG_ATA=y (breaks systemd's TEST-08-ISSUE-2730 upstream test) Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Won't Fix Status in linux source package in Yakkety: Fix Released Status in systemd source package in Yakkety: Won't Fix Bug description: Since the kernel upgrade from 4.4 to 4.8 in yakkety, systemd's TEST-08-ISSUE-2730 upstream test now consistently fails with: + timeout --foreground 180 /usr/bin/qemu-system-x86_64 -smp 1 -net none -m 512M -nographic -kernel /boot/vmlinuz-4.8.0-14-generic -drive format=raw,cache=unsafe,file=/var/tmp/systemd-test.4jlHRw/rootdisk.img -append 'root=/dev/sda1 raid=noautodetect loglevel=2 init=/lib/systemd/systemd ro console=ttyS0 selinux=0 systemd.unified_cgroup_hierarchy=no ' warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5] [1.491760] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.492153] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-14-generic #15-Ubuntu [1.492153] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [1.492153] 0086 35700369 a8b59c24 97201dd45000 [1.492153] 97201e9afea0 a8987431 0010 97201e9afeb0 [1.492153] 97201e9afe48 35700369 97201e9afe58 97201e9afeb8 [1.492153] Call Trace: [1.492153] [] ? dump_stack+0x5c/0x78 [1.492153] [] ? panic+0xe4/0x226 [1.492153] [] ? mount_block_root+0x284/0x2c0 [1.492153] [] ? set_debug_rodata+0xc/0xc [1.492153] [] ? prepare_namespace+0x12b/0x180 [1.492153] [] ? kernel_init_freeable+0x1dd/0x1ed [1.492153] [] ? kernel_init+0xa/0x100 [1.492153] [] ? ret_from_fork+0x1f/0x40 [1.492153] [] ? rest_init+0x80/0x80 [1.492153] Kernel Offset: 0x2780 from 0x8100 (relocation range: 0x8000-0xbfff) [1.492153] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) qemu-system-x86_64: terminating on signal 15 from pid 8784 This only happens on amd64, i386 and ppc64el are fine. http://autopkgtest.ubuntu.com/packages/systemd/yakkety/amd64 I'll investigate more details, filing this for getting a reference for the britney hint. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626394/+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 1398025] Re: Error messages like "error: /dev/sdb: No medium found" on booting
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1398025 Title: Error messages like "error: /dev/sdb: No medium found" on booting Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 15.04 dev with udev 217-1ubuntu1 and for a few days I'm seeing on every boot errors like "error: /dev/sdb: No medium found". Here is the content of /var/log/boot.log: Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... error: /dev/sdb: No medium found error: /dev/sdc: No medium found error: /dev/sdd: No medium found error: /dev/sde: No medium found error: /dev/sdb: No medium found error: /dev/sdc: No medium found error: /dev/sdd: No medium found error: /dev/sde: No medium found done. Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. * Setting up X socket directories... [210G [204G[ OK ] * cryptswap1 (running)... [210G * Starting early crypto disks... [210G [204G[ OK ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1398025/+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 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags
I can confirm that with this fix I have been successfully able to enlist, commission and deploy ubuntu to multiple servers in a cabinet via a DHCP relay agent to MaaS in another cabinet. THis is great! THanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: Fix Committed Status in klibc source package in Xenial: Fix Committed Status in klibc source package in Yakkety: Fix Released Bug description: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags field causes some DHCP relay agents to drop the packets, causing PXE to fail. [Test Case] Get a DHCP relay agent that drops PXE packets with an invalid bootp.flags bit set, and try to PXE boot; it fails. [Regression] None, the previous patch introduced this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+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 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags
Note, I was using a provided hotfix build of xenial in my tests. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: Fix Committed Status in klibc source package in Xenial: Fix Committed Status in klibc source package in Yakkety: Fix Released Bug description: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags field causes some DHCP relay agents to drop the packets, causing PXE to fail. [Test Case] Get a DHCP relay agent that drops PXE packets with an invalid bootp.flags bit set, and try to PXE boot; it fails. [Regression] None, the previous patch introduced this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+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 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags
The fix has been tested and is working. Several machine's have been booted and commissioned successfully ** Tags removed: verification-needed ** Tags added: verification-done-xenial verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: Fix Committed Status in klibc source package in Xenial: Fix Committed Status in klibc source package in Yakkety: Fix Released Bug description: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags field causes some DHCP relay agents to drop the packets, causing PXE to fail. [Test Case] Get a DHCP relay agent that drops PXE packets with an invalid bootp.flags bit set, and try to PXE boot; it fails. [Regression] None, the previous patch introduced this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+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 1602628] Re: can't drag/move window if it's semi-maximized by Ctrl+Super+Left/Right
works great now :D thanks x1000! https://launchpad.net/ubuntu/yakkety/+source/unity8/+changelog -- 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/1602628 Title: can't drag/move window if it's semi-maximized by Ctrl+Super+Left/Right Status in Canonical System Image: In Progress Status in Ubuntu UX: New Status in unity8 package in Ubuntu: In Progress Bug description: ubuntu 16.10 can't drag/move window if it's semi-maximized open random app, semi-miaximize left or rigt (CTRL SUPER + Left or Right), try to move the window by draggin' it from the title bar. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1602628/+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 1609107] Re: Ota13
can not reproduce anymore -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1609107 Title: Ota13 Status in bluez package in Ubuntu: New Bug description: Without ota13 bluetooth doesn't work anymore in my m10 tablet anymore. Keyboard and mouse donut connct and bluetooth switches itself off all the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1609107/+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 1627195] [NEW] exchange
Public bug reported: I would like to sync my company contacts that ar on a MS exchange server ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1627195 Title: exchange Status in address-book-app package in Ubuntu: New Bug description: I would like to sync my company contacts that ar on a MS exchange server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1627195/+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 1627192] [NEW] owncloud login
Public bug reported: I can't login to my owncloud on my raspberry pi. the button to login doesn't apear. (does in firefox) Owncloud 9.1 ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- 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/1627192 Title: owncloud login Status in webbrowser-app package in Ubuntu: New Bug description: I can't login to my owncloud on my raspberry pi. the button to login doesn't apear. (does in firefox) Owncloud 9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627192/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
Vladimir, The ContainersConfig.json found in "/custom/click/.click/users/@all/com.ubuntu.puritine/libertine- config/libertine" is the copy that "ships" with the click and should not affect any functionality after a fresh install of the image. I'm surprised to see that article suggesting a "copy/paste" situation as that's not necessary - libertine-container-manager will take care of that for you. Since Puritine did not update, your original ContainersConfig.json should have still been in-tact. There were dependency issues preventing the scope from showing any results for the last couple of weeks, but those were resolved with the OTA-13 release. If everything is working and your puritine apps are showing up in the scope, you should just be able to use the libertine-container-manager to start creating containers and installing apps again. If you want to delete your old container, you'll probably need to do a raw `rm -rf $HOME/.cache/libertine-container/my-container/`. I do not recommend using `rm` to manage libertine containers in normal scenarios, but this is a special situation. As for all the apps that don't quite work, I'm sorry to hear that. You can often find some of the libertine developers and enthusiasts on #ubuntu-libertine on freenode irc, but it's a pretty small group so you might not be able to find help at all hours of the day. You could also ask questions on AskUbuntu to broaden the audience. -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: Invalid Status in Today Scope: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1607185] Re: It's difficult to close the launcher without tapping on something you didn't want to
Why is this marked as "Incomplete"? What else is to be provided? -- 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/1607185 Title: It's difficult to close the launcher without tapping on something you didn't want to Status in Canonical System Image: Incomplete Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Incomplete Bug description: It's difficult to close the launcher without tapping on something you didn't want to. Test case: 1. Open an app. 2. Open the launcher swiping from the left. 3. Close the launcher without triggering any touches in the app. Expected: Tapping outside the launcher will close it without touches reaching the app. Observed: Tapping outside the launcher closes it but unwanted touches reach the app. You can close the launcher by swiping it back off the side, but it's too small to do that very easily without also accidentally touching the top-most app. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607185/+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 1627187] [NEW] touchpad is not recognized. no two finger scrolling or zoom
Public bug reported: touchpad is not recognized. no two finger scrolling or zoom ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.6.0-040600-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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: Fri Sep 23 13:40:10 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] InstallationDate: Installed on 2016-06-27 (88 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 005: ID 0457:10cc Silicon Integrated Systems Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.0-040600-generic root=UUID=8d4bed35-4644-4bea-9928-057c910ef932 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.206:bd02/03/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N501VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 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: Fri Sep 23 12:32:57 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16971 vendor SDC xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1627187 Title: touchpad is not recognized. no two finger scrolling or zoom Status in xorg package in Ubuntu: New Bug description: touchpad is not recognized. no two finger scrolling or zoom ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.6.0-040600-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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: Fri Sep 23 13:40:10 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] InstallationDate: Installed on 2016-06-27 (88 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 005: ID 0457:10cc Silicon Integrated Systems
[Touch-packages] [Bug 1626180] Re: Desktop Apps scope hangs unity8-dash
Larry, thanks for your insight here. Vladimir, it seems that either there was something wrong with your CC.json file or with your container. So on that basis I'll mark this bug invalid. I is probably not a good idea to manually modify CC.json files. If I understand correctly, all container modifications can be done with the libertine-container-manager command and that automatically keeps the CC.json file up to date. If the problem comes back you might need to delete the container and start fresh. ** Changed in: canonical-devices-system-image Status: New => Invalid ** Changed in: unity8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: Invalid Status in Today Scope: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
And what about to restore link to "/custom/click/.click/users/@all/com.ubuntu.puritine/libertine- config/libertine"? Can problem repeat? Or to use your new ContainersConfig.json (or my copy of it)? -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: Invalid Status in Today Scope: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
Larry, it works. Kyle, Larry -- thanks for help! How to fully and correctly delete my previous my-container? About behavior installed apps in my-container -- I can say: Okular only tries to start, MC hangs (when starts via scope), mir-demo doesn't work, others have problem with DPI except Geany. I have some questions about DPI setting in Libertine and some other problems with Ubuntu One. How can I discuss them (of course, I've checked out many pages askubuntu.com) P.S. I used this fix from article: http://notyetthere.org/installing-more-puritine-apps-on-the-m10/ Why did it work before OTA-13 ?? -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: Invalid Status in Today Scope: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1599771] Re: Webview appears to think it's in focus when typing in the addressbar
** Changed in: oxide Milestone: None => branch-1.19 ** Changed in: oxide Status: Fix Committed => Fix Released -- 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/1599771 Title: Webview appears to think it's in focus when typing in the addressbar Status in Oxide: Fix Released Status in webbrowser-app package in Ubuntu: Invalid Bug description: See the screenshot - when keyboard focus is on the addressbar, the webview thinks it is still in focus (indicated by the presence of the caret in the search field). Not sure if this is Oxide or webbrowser-app To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1599771/+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 1585723] Re: UbuntuShape on intel i915 (Atom) uses fallback CPU rendering
Any news now?(sorry for my insistence but it is important) -- 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/1585723 Title: UbuntuShape on intel i915 (Atom) uses fallback CPU rendering Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: I'm digging into unity8 performance problems on older generation Intel GPUs - specifically i915 Atom GPUs. I've tested a simple QML file with a single empty UbuntuShape in it: import QtQuick 2.4 import Ubuntu.Components 1.3 Rectangle { width: 400 height: 300 color: "blue" UbuntuShape {} } Running it with INTEL_DEBUG=perf env var set, I get this output: i915_program_error: Exceeded max ALU instructions (76 out of 64) ENTER FALLBACK 1: Program Mapping a busy BO, causing a stall on the GPU. which implies that MESA was unable to compile one of the UbuntuShape shaders as it created more ALU instructions than the GPU could deal with. MESA falls back to CPU rendering as a result. The GPU stall message I guess is related to that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1585723/+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 1622002] Re: dhcp_release6 can be called when it is not present
Reviewed: https://review.openstack.org/366291 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=d4f92ede9ed52cd0b9059d993e3cf1f42d5ff57e Submitter: Jenkins Branch:master commit d4f92ede9ed52cd0b9059d993e3cf1f42d5ff57e Author: Brian HaleyDate: Tue Sep 6 14:44:41 2016 -0400 Fix dhcp_release6 error when not supported If the system does not have a version of dnsmasq that supports dhcp_release6, warn about but otherwise handle it gracefully, and also don't even try to execute it the next time. Closes-Bug: #1622002 Related-Bug: #1624079 Change-Id: I6bb9547f9d9a9fcfb2357521f3f5bd1dc1dd5136 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1622002 Title: dhcp_release6 can be called when it is not present Status in neutron: Fix Released Status in dnsmasq package in Ubuntu: New Bug description: If someone enables dhcpv6-stateful addressing on a subnet, but they are running an old version of dnsmasq (<2.76), then the dhcp agent could try and run dhcp_release6 even though it isn't present. An example: http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron- multinode-full-ubuntu- xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272 Checking it's present first would fix this problem. Since the change to call dhcp_release6 was just added in https://review.openstack.org/#/c/301747/ we should fix this before Newton ships and people complain. There is also an effort to get Cirros to support DHCPv6 so that we can test this in the gate, https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so we can add a functional test. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1622002/+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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Guys, the patch from Joakim did work for me! It turns out all I needed after installing pulseaudio suite from Joakim's PPA is: pactl load-module module-bluetooth-discover I'm pretty sure I have tried it before I applied the PPA and it didn't work. Since there was no mention of it in this conversation until recently, I totally forgot to check it. Thanks everyone! I will try to figure out now if it's possible to connect 2 Jaybird devices simultaneously. It works like a charm on Mac. -- 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/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
Vladimir, I wonder if something is going on with one of the apps you installed in your custom container? I've attached a copy of your ContainersConfig.json with only puritine apps, which I believe will work and give you the default applications back. I'll poke through a few of the applications and see if I can figure out if any of them in particular caused this issue. In lieu of my investigation, you could recreate your custom container and start installing apps. If any of them in particular cause this issue to appear again, please let us know. ** Attachment added: "ContainersConfig.json without my-container" https://bugs.launchpad.net/today-scope/+bug/1626180/+attachment/4747411/+files/ContainersConfig.json -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address
** Changed in: ifupdown Status: New => Fix Released -- 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/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot assign requested address Status in ifupdown: Fix Released Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Precise: Invalid Status in ifupdown source package in Trusty: Invalid Status in ifupdown source package in Xenial: In Progress Bug description: (Original bug description follows SRU info) [Description] When using dhcpv6 configured via ifupdown, the interface's dhcp client fails to start at boot with the error: Can't bind to dhcp address: Cannot assign requested address This is because ifupdown doesn't wait, after bringing the interface up, for it to complete its link-local Duplicate Address Detection (DAD), and the dhcp client can't bind to the link-local address because it's still in "tentative" state (until DAD completes). This is fixed upstream in debian ifupdown in version 0.8.11 by adding '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the script was only waiting for the link-local address to appear, now it waits until the link-local address appears and is not in 'tentative' state. [Test Case] Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0 inet6 dhcp) and reboot. It will fail to get a dhcp address during boot. [Regression] None -- original bug description -- After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 address via DHCPv6. The root cause is that dhclient is exiting with the following message: - Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. - The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04 version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10 version) allows me to obtain an address. NetworkManager is the one launching dhclient. The two invocations (one for IPv4 and one for IPv6) are: dhclient_start(): running: /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient6-eth0.pid -lf /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b- 563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient6-eth0.conf eth0 I do not see anything suspicious with the way both dhclients are invoked. Given that a downgrade allows me to obtain an IPv6 address I think this might be a bug in the ISC DHCP client rather than in NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1447715/+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 1492767] Re: gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3
Maybe it's not related... but I prefer to register here. I use Trusty for some months (3,4...) and the last one or two dist- upgrades just got me out of my Unity Desktop. GUI login did not complete (always back to login), default wallpaper not shown, topbar not shown (icons, etc). Only console saved me (Ctrl-Alt-F1). I noticed the same info about Gdkpixbuf loader module in the bug description. Also gdk-pixbuf-query-loaders was not installed. But I just did not worry about these messages. On next boot the problem aroused. I analysed apt log file and isolated last two dist-upgrades (below). I decided to downgrade the first ones and I regained login to desktop. Now you see the words GDK and PIXBUF: gir1.2-gdkpixbuf-2.0:amd64 (2.30.7-0ubuntu1.2, 2.30.7-0ubuntu1.6) libgdk-pixbuf2.0-common:amd64 (2.30.7-0ubuntu1.2, 2.30.7-0ubuntu1.6) libgdk-pixbuf2.0-0:amd64 (2.30.7-0ubuntu1.2, 2.30.7-0ubuntu1.6) libgdk-pixbuf2.0-0:i386 (2.30.7-0ubuntu1.2, 2.30.7-0ubuntu1.6) openssl:amd64 (1.0.1f-1ubuntu2.19, 1.0.1f-1ubuntu2.20) libssl1.0.0:amd64 (1.0.1f-1ubuntu2.19, 1.0.1f-1ubuntu2.20) linux-image-4.4.0-38-generic:amd64 (4.4.0-38.57~14.04.1, automatic) linux-headers-4.4.0-38:amd64 (4.4.0-38.57~14.04.1, automatic) linux-image-extra-4.4.0-38-generic:amd64 (4.4.0-38.57~14.04.1, automatic) linux-headers-4.4.0-38-generic:amd64 (4.4.0-38.57~14.04.1, automatic) linux-generic-lts-xenial:amd64 (4.4.0.36.26, 4.4.0.38.28) libservlet3.0-java:amd64 (7.0.52-1ubuntu0.6, 7.0.52-1ubuntu0.7) linux-headers-generic-lts-xenial:amd64 (4.4.0.36.26, 4.4.0.38.28) linux-image-generic-lts-xenial:amd64 (4.4.0.36.26, 4.4.0.38.28) linux-libc-dev:amd64 (3.13.0-95.142, 3.13.0-96.143) firefox-locale-en:amd64 (48.0+build2-0ubuntu0.14.04.1, 49.0+build4-0ubuntu0.14.04.1) python3.4:amd64 (3.4.3-1ubuntu1~14.04.3, 3.4.3-1ubuntu1~14.04.4) dkms:amd64 (2.2.0.3-1.1ubuntu5.14.04.7, 2.2.0.3-1.1ubuntu5.14.04.8) thunderbird-locale-en-us:amd64 (45.2.0+build1-0ubuntu0.14.04.3, 45.3.0+build1-0ubuntu0.14.04.4) firefox:amd64 (48.0+build2-0ubuntu0.14.04.1, 49.0+build4-0ubuntu0.14.04.1) python3.4-minimal:amd64 (3.4.3-1ubuntu1~14.04.3, 3.4.3-1ubuntu1~14.04.4) libpython3.4-stdlib:amd64 (3.4.3-1ubuntu1~14.04.3, 3.4.3-1ubuntu1~14.04.4) libgweather-3-6:amd64 (3.10.2-0ubuntu2, 3.10.2-0ubuntu3) libpython3.4:amd64 (3.4.3-1ubuntu1~14.04.3, 3.4.3-1ubuntu1~14.04.4) libpython3.4-minimal:amd64 (3.4.3-1ubuntu1~14.04.3, 3.4.3-1ubuntu1~14.04.4) libgweather-common:amd64 (3.10.2-0ubuntu2, 3.10.2-0ubuntu3) My Desktop is still buggy at startup (some app crash and I cannot figure out). But at least I can work. Cheers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1492767 Title: gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3 Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: Hello, I did a fresh install with a Trusty 14.04.3 (x86_64) yesterday (custom Bento Openbox), and today, I updated the system (with the console, because other issues came first which led me to do a filesystem check). Then I started Synaptic, and oops! no GUI, only the borders of the window would show. Several other programs were affected and would not start (Geany, text editor), or show their content. After tests and research it appeared only GTK3 programs were affected. If using a theme with GTK2, or move the GTK configuration out of the way, the programs would work. The upgrade contained the following packages: gir1.2-gdkpixbuf-2.0_2.30.7 libgdk-pixbuf2.0-0_2.30.7 libgdk-pixbuf2.0-common_2.30.7 I fixed the issue by booting to the Live USB I had used to install, and repackage the programs with dpkg-repack, then reinstalled them using "sudo dpkg -i *.deb". (copied from the live usb to the home in the install, rebooted and reinstalled there). Problem solved for this install, where I have for now blocked the update for these three packages. At post-install, after I had updated, I had the same message as the people who reported that bug: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294 (gtk-update-icon-cache-3.0:29671): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. and when trying to do so, the console returned a message stating gdk- pixbuf-query-loaders was not installed. (no such package in the repos either). More information can be found at http://irclogs.ubuntu.com/2015/09/06/%23ubuntu-bugs.html where I discussed about this bug and my findings. Now I will try to produce this bug again in the Live USB (which has no persistence).
[Touch-packages] [Bug 1626808] Re: Unable to log in from bq Aquaris tablet
Can you attach before/after screenshots? You should be able to take a screenshot by pressing both Vol Up+Vol Dn at the same time. You should be able to attach them to the bug via the browser on the M10 or transfer them via USB to a PC for attaching to the bug. If you attach with USB and with developer mode enabled, you can use the "phablet-shell" tool on Ubuntu to shell in to the tablet, and watch /home/phablet/.cache/upstart/dbus.log while trying to log in. There may be some indication of what's going on printed to this file while attempting to log in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1626808 Title: Unable to log in from bq Aquaris tablet Status in Canonical SSO provider: New Status in ubuntuone-credentials package in Ubuntu: New Bug description: Hi I have five Aquaris tablets I am installing some new products I have built onto. On one tablet, when I try to log in to the Ubuntu One so I can get the terminal app, I enter my email and password (correct) to log in, but I am not logged in and the terminal app does not download. Without the terminal app installed I cannot run any diagnostics or get any information about what is going wrong. This setup, where terminal is not on the Tablet OS by default, totally SUCKS. I need support urgently. I cannot provide log files to you or anything else. Presumably the Ubuntu Web web site logs will say that I am trying to log in from a Tablet device. I wish I had some logs myself... Mark Anson To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/1626808/+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 1516696] Re: SMS notifications are received only when the phone is unlocked
Not sure if that be of any use as I don't have any logs but I'll add it anyway :) Yesterday I had a phone on my desk, I wasn't doing anything with it. At some point I got notification about new SMS. I've checked immediately and noticed that in the notification "bubble" it said "8 minutes ago". Later the same day I had similar situation but this time the "bubble" said "13 minutes ago" when the SMS notification arrived. For a change today I had the problem exactly as described in the bug report: when I pressed the power button, the notification showed up. bq e4.5 OTA-13 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1516696 Title: SMS notifications are received only when the phone is unlocked Status in Canonical System Image: Confirmed Status in powerd: New Status in Unity System Compositor: New Status in indicator-messages package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: WHAT HAPPENED: The phone stays quiet while locked but once the power button is pressed (unlocked), SMS notification are received with vibration, notification bubble and sound alert. The message received shows that it was actually received 10 minutes ago. This happened multiple times already but I think I ignored them and this seems to have started after OTA-7 was released. EXPECTED: The phone should have the vibration, notification bubble/indicator and sound alert even if the phone is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516696/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
phablet@ubuntu-phablet:~/.local/share/libertine$ mv ContainersConfig.json ContainersConfig.current oh, it works!! top - 02:38:03 up 2:14, 2 users, load average: 11,63, 11,65, 11,14 Tasks: 271 total, 5 running, 264 sleeping, 2 stopped, 0 zombie %Cpu(s): 10,9 us, 9,9 sy, 0,0 ni, 78,7 id, 0,3 wa, 0,0 hi, 0,2 si, 0,0 st KiB Mem: 2009416 total, 1047892 used, 961524 free, 1248 buffers KiB Swap: 524284 total,0 used, 524284 free. 118240 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2225 phablet 20 0 776796 221816 97464 S 13,2 11,0 0:42.46 unity8 1909 phablet9 -11 287268 12936 9104 S 7,0 0,6 0:02.38 pulseaudio 5721 root 0 -20 0 0 0 S 4,0 0,0 0:01.88 kworker/u9+ 2556 phablet 20 0 183860 5076 3744 S 2,6 0,3 0:01.96 indicator-+ 1611 phablet 20 07168 2460 1192 S 2,3 0,1 0:22.26 upstart 2194 phablet 20 0 260124 21364 16484 S 2,3 1,1 0:00.61 media-hub-+ 758 root 20 0 35328 3232 2488 S 1,7 0,2 0:02.00 accounts-d+ 1350 root 20 0 269836 15920 10712 S 1,7 0,8 0:05.90 unity-syst+ 720 message+ 20 06408 2680836 S 1,3 0,1 0:21.76 dbus-daemon 7115 root 20 0 0 0 0 S 1,3 0,0 0:02.01 kworker/u8+ 1754 phablet 20 05448 2080768 S 1,0 0,1 0:04.67 dbus-daemon 1923 phablet 20 05436596344 S 1,0 0,0 0:04.16 upstart-db+ but, still empty scope, but with some message, see attachment ** Attachment added: "Scope partially works" https://bugs.launchpad.net/today-scope/+bug/1626180/+attachment/4747393/+files/screenshot20160924_023803889.png -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
phablet@ubuntu-phablet:~$ ls -la $HOME/.local/share/libertine/ total 24 drwxrwxr-x 2 phablet phablet 4096 авг. 9 16:13 . drwxrwxr-x 58 phablet phablet 4096 сент. 23 20:39 .. lrwxrwxrwx 1 phablet phablet 100 янв. 1 2015 ContainersConfig.bak -> /custom/click/.click/users/@all/com.ubuntu.puritine/libertine-config/libertine/ContainersConfig.json -rw-rw-rw- 1 phablet phablet 4079 авг. 9 16:09 ContainersConfig.jso_ -rw-rw-r-- 1 phablet phablet 5241 сент. 21 22:14 ContainersConfig.json And I will try to rename now... wait -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1516696] Re: SMS notifications are received only when the phone is unlocked
rild holds a wakelock for only 200ms so its quite possible the phone suspends while we are waiting on that timer. Also, QTimer must not use hardware wakeup events or things would work. We need to figure out where to put a wakelock request, repowerd provides an interface for this. It wold also be good to remove that timer and find a better way to handle when messaging app is open. See comment #25 which is a similar issue with clock alarms in indicator- datetime, although it has logic to keep the device awake which is clearly not working. ** Tags added: wakeup -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1516696 Title: SMS notifications are received only when the phone is unlocked Status in Canonical System Image: Confirmed Status in powerd: New Status in Unity System Compositor: New Status in indicator-messages package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: WHAT HAPPENED: The phone stays quiet while locked but once the power button is pressed (unlocked), SMS notification are received with vibration, notification bubble and sound alert. The message received shows that it was actually received 10 minutes ago. This happened multiple times already but I think I ignored them and this seems to have started after OTA-7 was released. EXPECTED: The phone should have the vibration, notification bubble/indicator and sound alert even if the phone is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516696/+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 1588526] Re: Alarm doesn't ring when screen locked
** Tags added: wakeup -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1554504] Re: Calendar reminder does not wake phone when airplane mode is enabled
@charles can you comment, do we set an alarm to wakeup or rely on a timer? ** Changed in: canonical-devices-system-image Milestone: backlog => 14 ** Tags added: wakeup -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1554504 Title: Calendar reminder does not wake phone when airplane mode is enabled Status in Canonical System Image: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: If airplane mode is enabled, the phone seems to go into a deep sleep where it doesn't wake up for a calendar reminder. The reminder does not sound until the power button is pressed to wake the phone, in some cases this has been more than an hour after the reminder was scheduled for. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554504/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
Vladimir, thanks. It looks like your filesystem matches your ContainersConfig.json, but my theory is still that something odd must be going on with that file. * What are the file permissions on ContainersConfig.json (`ls -la $HOME/.local/share/libertine/ContainersConfig.json`? * If you temporarily rename ContainersConfig.json, does the scope load? There would be no results, but should at least be a message saying as much. -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1626773] Re: CVE-2016-2182.patch has broken BN_bn2dec
** Changed in: openssl (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1626773 Title: CVE-2016-2182.patch has broken BN_bn2dec Status in openssl package in Ubuntu: Fix Released Bug description: My software which links to libcrypto stopped working on both Ubuntu 12.04 / 14.04 / 16.04 last week. The problem is that BN_bn2dec returns NULL all the time (without setting an error message) even for valid input values. I think is a bug in CVE-2016-2182.patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1626773/+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 1626817] Re: package ifupdown 0.8.10ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1626817 Title: package ifupdown 0.8.10ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in ifupdown package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Thu Sep 22 22:53:02 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2016-09-18 (4 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: ifupdown Title: package ifupdown 0.8.10ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1626817/+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 1588526] Re: Alarm doesn't ring when screen locked
Theory is that the phone suspends before the alarm sound can be played. In that case pushing the power button or waking on the 5 min poll timer will then sound the alarm. However we do request that repowerd keeps the system awake when we issue the alarm or notification. We wait for the system dbus to be available, perhaps that is sometimes taking too long, or the request is not serviced properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
Larry, here they are: phablet@ubuntu-phablet:~$ ls $HOME/.cache/libertine-container/ my-container puritine ** Attachment added: "/home/phablet/.local/share/libertine/ContainersConfig.json" https://bugs.launchpad.net/today-scope/+bug/1626180/+attachment/4747366/+files/ContainersConfig.json -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1626773] Re: CVE-2016-2182.patch has broken BN_bn2dec
Yes, the problem seems to be fixed. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1626773 Title: CVE-2016-2182.patch has broken BN_bn2dec Status in openssl package in Ubuntu: Incomplete Bug description: My software which links to libcrypto stopped working on both Ubuntu 12.04 / 14.04 / 16.04 last week. The problem is that BN_bn2dec returns NULL all the time (without setting an error message) even for valid input values. I think is a bug in CVE-2016-2182.patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1626773/+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 1447756] Re: [SRU] segfault in log.c code causes phone reboot loops
Yep, this is definitely affecting Trusty as well. Is there any chance the fix will be backported? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1447756 Title: [SRU] segfault in log.c code causes phone reboot loops Status in Canonical System Image: Fix Released Status in upstart : Fix Committed Status in upstart package in Ubuntu: Fix Released Status in upstart source package in Utopic: Won't Fix Status in upstart source package in Vivid: Won't Fix Status in upstart source package in Wily: Fix Released Status in upstart package in Ubuntu RTM: Fix Released Bug description: = Summary = The version of Upstart in vivid is affected by a coule of bugs relating to the flushing data from early-boot jobs to disk which can both result in a crash: == Problem 1 == An internal list is mishandled meaning a crash could occur randomly. == Problem 2 == Jobs which spawn processes in the background then themselves exit can cause a crash due. = Explanation of how Upstart flushes early job output = If an Upstart job starts *and ends* early in the boot sequence (before the log partition is mounted and writable) and produces output to its stdout/stderr, Upstart will cache the output for later flushing by adding the 'Log' object associated with the 'Job' to a list. When the log partition is mounted writable, the /etc/init/flush-early-job-log.conf job is run which calls "initctl notify-disk-writeable". This is a signal to Upstart to flush its cache of early-boot job output which takes the form of iterating the 'log_unflushed_files' list and flushing all the 'Log' entries to disk. = Code Specifics = There are 2 issues (note that the numbers used below match those used in the Summary). == Problem 1 detail == Due to a bug in the way the 'log_unflushed_files' list is handled (the 'Log' cannot be added to the list directly, so is added via an intermediary ('NihListElem') node), a crash can result when iterating the list since the 'Log' is freed, but NOT the intermediary node. The implication is that it is possible for the intermediary node to be attempt to dereference already-freed data, resulting in a crash. == Problem 2 detail == If a job spawns a process in the background, then itself exits, that jobs 'Log' entry will be added to the 'log_unflushed_files' list. But, if the background process produces output and then exits before Upstart attempts to flush the original jobs data to disk, the 'NihIo' corresponding to the log will be serviced automatically and the data flushed to disk. The problem comes when Upstart receives the notification to flush the 'log_unflushed_files' list, since that list now contains an entry which has already been freed (since all its data has already been flushed). The result is an assertion failure. = Fix = == Problem 1 fix == Correct the 'log_unflushed_files' list handling by freeing the 'NihListElem' (which will automatically free the 'Log' object), not by simply freeing the 'Log' object itself. * Branch: lp:~jamesodhunt/ubuntu/vivid/upstart/bug-1447756/ * New Upstart test added to avoid regression?: Yes. == Problem 2 fix == Correct the assumption that the only entries in the 'log_unflushed_files' list will always have data to flush by checking if there is in fact any data to flush; if not, remove the entry from the 'log_unflushed_files' list since it has already been handled automatically by the 'NihIo'. * Branch: lp:~jamesodhunt/upstart/bug-1447756-the-actual-fix * New Upstart test added to avoid regression?: Yes. = Workarounds = If a system is affected by this bug, it will be manifested by a crash early in the boot sequence. To overcome the issue, either: a) Boot by adding "--no-log" to the kernel command-line. b) Disable the flush-early-job-log job (assuming the machine is bootable) by running the following: $ echo manual | sudo tee -a /etc/init/flush-early-job-log.override = Impact = The issue has been present in Upstart since logging was introduced but no known instances of crashes relating to these problems have been reported prior to this bug being reported (which relates the the issue being seen on a very small subset of specific Ubuntu Touch phone hardware where Upstart is used as the system init daemon). Note that vivid still uses Upstart for managing the graphical session, but now uses systemd by default for the system init daemon. Since the session (Upstart) init does not even require a flush-early-job-log, the exposure to both the bug and the updated fix codepath is extremely limited. = Test Case = This bug is extremely hard to surface so the approach is simply to check that the internal list can be iterated correctly by: 1) Booting the system with upstart
[Touch-packages] [Bug 1626180] Re: Desktop Apps scope hangs unity8-dash
Hi Vladimir! My guess is that there is a mismatch between ContainersConfig.json and what's actually available to you. The ContainersConfig.json file acts as our local database, so replacing it is highly likely to cause issues. I'd like a little bit more information before we proceed: * Can you attach your ContainersConfig.json file? * Can you show us the result of `ls $HOME/.cache/libertine-container/`? -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1615204] Re: select-by-word/double-click drag-select only works sporadically on Toshiba Chromebook 1
some potentially-promising files from the restore diff (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1615204/+attachment/4747314/+files/restore.log): .d..t.. usr/share/X11/xorg.conf.d/ >f..t.. usr/share/X11/xorg.conf.d/10-evdev.conf >f..t.. usr/share/X11/xorg.conf.d/10-quirks.conf >f..t.. usr/share/X11/xorg.conf.d/11-evdev-quirks.conf >f..t.. usr/share/X11/xorg.conf.d/11-evdev-trackpoint.conf >f..t.. usr/share/X11/xorg.conf.d/50-synaptics.conf >f..t.. usr/share/X11/xorg.conf.d/50-vmmouse.conf >f.st.. usr/share/X11/xorg.conf.d/50-wacom.conf >f..t.. usr/share/X11/xorg.conf.d/51-synaptics-quirks.conf cd+ usr/share/bug/xserver-xorg-input-mouse/ cL+ usr/share/bug/xserver-xorg-input-mouse/script -> ../xserver-xorg-core/script cd+ usr/share/bug/xserver-xorg-input-synaptics/ cL+ usr/share/bug/xserver-xorg-input-synaptics/script -> ../xserver-xorg-core/script cd+ usr/share/bug/xserver-xorg-input-vmmouse/ cL+ usr/share/bug/xserver-xorg-input-vmmouse/script -> ../xserver-xorg-core/script the files in /usr/lib/xorg/modules/ (restored previously and not in the diff) -- 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/1615204 Title: select-by-word/double-click drag-select only works sporadically on Toshiba Chromebook 1 Status in Linux: Unknown Status in xorg package in Ubuntu: Incomplete Bug description: (also on Linux kernel bug tracker at https://bugzilla.kernel.org/show_bug.cgi?id=153871) Detailed bug description: In Ubuntu 16.04.1 [1] on the Toshiba Chromebook 1, if you try to select text by word, by double-clicking/triple-touchpad-tapping and then dragging the mouse, this only works occasionally. However, selecting text by line with a triple-click/4-tap drag works fine. This bug does not appear when Ubuntu 16.04.1 is run in a VM in VirtualBox. [1] and now Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 4.4.0-34-generic (the same as for 16.04) Steps to reproduce: 1) On a 1st-generation Toshiba Chromebook (and possibly other machines, too), run Ubuntu 16.04.1 from a boot disk (http://releases.ubuntu.com/16.04/ubuntu-16.04.1-desktop-i386.iso). 2) Open a terminal window and type several words. 3) Double-click/triple-touchpad-tap and then drag the mouse to attempt to select multiple words. 4) Compare this to the same boot disk run in VirtualBox, where it works properly. 5) Compare this to Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 4.4.0-34-generic, where it doesn't work. 6) Compare this to the hardware-specific update but with Linux kernel 4.4.0-34-generic removed (downgraded to 3.16.0-77-generic), where it also doesn't work (and is therefore not a kernel problem, but rather relates to other files in the hardware-specific update). Expected results: Multiple words are selected. Actual result: Only the first word is selected. Reproducibility: Double-click drag-select will work occasionally, but most of the time it doesn't. Workaround: In applications other than Terminal, can use Ctrl+Shift+Right-Arrow to select by word (significantly slower for large text blocks). No known workaround for Terminal. Impact: Recommend not upgrading to 16.04 if you have a computer where double-click drag-select doesn't work in it. Description of the environment: Operation system: Ubuntu 16.04.1 Versions of components: Linux kernel 4.4.0-34-generic (also on Ubuntu 14.04.5) Reference architecture: 1st-generation Toshiba Chromebook (model name "Toshiba Leon") Network model: N/A Related projects installed: none (boot disk) Additional information: N/A --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: administrator 1882 F pulseaudio /dev/snd/controlC1: administrator 1882 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-04-05 (506 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) MachineType: Toshiba Leon Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=127e42a1-2015-0521--28e347c5f54d ro tpm_tis.force=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.127.22 Tags: trusty Uname: Linux 4.4.0-34-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/26/2014
[Touch-packages] [Bug 1615204] Re: select-by-word/double-click drag-select only works sporadically on Toshiba Chromebook 1
Not a Linux kernel bug, but rather a bug in other files in the hardware- specific update, probably the xorg ones. ** Description changed: (also on Linux kernel bug tracker at https://bugzilla.kernel.org/show_bug.cgi?id=153871) Detailed bug description: In Ubuntu 16.04.1 [1] on the Toshiba Chromebook 1, if you try to select text by word, by double-clicking/triple-touchpad-tapping and then dragging the mouse, this only works occasionally. However, selecting text by line with a triple-click/4-tap drag works fine. This bug does not appear when Ubuntu 16.04.1 is run in a VM in VirtualBox. [1] and now Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 4.4.0-34-generic (the same as for 16.04) Steps to reproduce: 1) On a 1st-generation Toshiba Chromebook (and possibly other machines, too), run Ubuntu 16.04.1 from a boot disk (http://releases.ubuntu.com/16.04/ubuntu-16.04.1-desktop-i386.iso). 2) Open a terminal window and type several words. 3) Double-click/triple-touchpad-tap and then drag the mouse to attempt to select multiple words. 4) Compare this to the same boot disk run in VirtualBox, where it works properly. - 5) Also compare this to Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 4.4.0-34-generic, where it doesn't work. + 5) Compare this to Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 4.4.0-34-generic, where it doesn't work. + 6) Compare this to the hardware-specific update but with Linux kernel 4.4.0-34-generic removed (downgraded to 3.16.0-77-generic), where it also doesn't work (and is therefore not a kernel problem, but rather relates to other files in the hardware-specific update). Expected results: Multiple words are selected. Actual result: Only the first word is selected. Reproducibility: Double-click drag-select will work occasionally, but most of the time it doesn't. Workaround: In applications other than Terminal, can use Ctrl+Shift+Right-Arrow to select by word (significantly slower for large text blocks). No known workaround for Terminal. Impact: Recommend not upgrading to 16.04 if you have a computer where double-click drag-select doesn't work in it. Description of the environment: Operation system: Ubuntu 16.04.1 Versions of components: Linux kernel 4.4.0-34-generic (also on Ubuntu 14.04.5) Reference architecture: 1st-generation Toshiba Chromebook (model name "Toshiba Leon") Network model: N/A Related projects installed: none (boot disk) Additional information: N/A - --- + --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: administrator 1882 F pulseaudio - /dev/snd/controlC1: administrator 1882 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: administrator 1882 F pulseaudio + /dev/snd/controlC1: administrator 1882 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-04-05 (506 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) MachineType: Toshiba Leon Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=127e42a1-2015-0521--28e347c5f54d ro tpm_tis.force=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15 RelatedPackageVersions: - linux-restricted-modules-4.4.0-34-generic N/A - linux-backports-modules-4.4.0-34-generic N/A - linux-firmware1.127.22 + linux-restricted-modules-4.4.0-34-generic N/A + linux-backports-modules-4.4.0-34-generic N/A + linux-firmware1.127.22 Tags: trusty Uname: Linux 4.4.0-34-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/26/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Toshiba dmi.modalias: dmi:bvncoreboot:bvr:bd08/26/2014:svnToshiba:pnLeon:pvr1.0:cvnToshiba:ct3:cvr: dmi.product.name: Leon dmi.product.version: 1.0 dmi.sys.vendor: Toshiba ** Package changed: linux (Ubuntu) => xorg (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/1615204 Title: select-by-word/double-click drag-select only works sporadically on Toshiba Chromebook 1 Status in Linux: Unknown Status in xorg package in Ubuntu: Incomplete Bug description: (also on Linux kernel bug tracker at https://bugzilla.kernel.org/show_bug.cgi?id=153871) Detailed bug description: In Ubuntu 16.04.1 [1] on the Toshiba Chromebook 1, if you try to select text by word, by double-clicking/triple-touchpad-tapping and
[Touch-packages] [Bug 1615204] Re: select-by-word/double-click drag-select only works sporadically on Toshiba Chromebook 1
** Attachment added: "rsync log for restoring to previous system, showing changed files" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1615204/+attachment/4747314/+files/restore.log -- 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/1615204 Title: select-by-word/double-click drag-select only works sporadically on Toshiba Chromebook 1 Status in Linux: Unknown Status in xorg package in Ubuntu: Incomplete Bug description: (also on Linux kernel bug tracker at https://bugzilla.kernel.org/show_bug.cgi?id=153871) Detailed bug description: In Ubuntu 16.04.1 [1] on the Toshiba Chromebook 1, if you try to select text by word, by double-clicking/triple-touchpad-tapping and then dragging the mouse, this only works occasionally. However, selecting text by line with a triple-click/4-tap drag works fine. This bug does not appear when Ubuntu 16.04.1 is run in a VM in VirtualBox. [1] and now Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 4.4.0-34-generic (the same as for 16.04) Steps to reproduce: 1) On a 1st-generation Toshiba Chromebook (and possibly other machines, too), run Ubuntu 16.04.1 from a boot disk (http://releases.ubuntu.com/16.04/ubuntu-16.04.1-desktop-i386.iso). 2) Open a terminal window and type several words. 3) Double-click/triple-touchpad-tap and then drag the mouse to attempt to select multiple words. 4) Compare this to the same boot disk run in VirtualBox, where it works properly. 5) Compare this to Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 4.4.0-34-generic, where it doesn't work. 6) Compare this to the hardware-specific update but with Linux kernel 4.4.0-34-generic removed (downgraded to 3.16.0-77-generic), where it also doesn't work (and is therefore not a kernel problem, but rather relates to other files in the hardware-specific update). Expected results: Multiple words are selected. Actual result: Only the first word is selected. Reproducibility: Double-click drag-select will work occasionally, but most of the time it doesn't. Workaround: In applications other than Terminal, can use Ctrl+Shift+Right-Arrow to select by word (significantly slower for large text blocks). No known workaround for Terminal. Impact: Recommend not upgrading to 16.04 if you have a computer where double-click drag-select doesn't work in it. Description of the environment: Operation system: Ubuntu 16.04.1 Versions of components: Linux kernel 4.4.0-34-generic (also on Ubuntu 14.04.5) Reference architecture: 1st-generation Toshiba Chromebook (model name "Toshiba Leon") Network model: N/A Related projects installed: none (boot disk) Additional information: N/A --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: administrator 1882 F pulseaudio /dev/snd/controlC1: administrator 1882 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-04-05 (506 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) MachineType: Toshiba Leon Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=127e42a1-2015-0521--28e347c5f54d ro tpm_tis.force=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.127.22 Tags: trusty Uname: Linux 4.4.0-34-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/26/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Toshiba dmi.modalias: dmi:bvncoreboot:bvr:bd08/26/2014:svnToshiba:pnLeon:pvr1.0:cvnToshiba:ct3:cvr: dmi.product.name: Leon dmi.product.version: 1.0 dmi.sys.vendor: Toshiba To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1615204/+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 1627144] [NEW] Received texts merging
Public bug reported: Sometimes, long multi-part texts have their ends truncated and replaced with the end of random texts received months earlier. I can't reproduce it, however if I ask the sender to re-send the long text, it is displayed correctly. The texts are displayed incorrectly in both the Messages app and scope. OTA-12 saw the issue almost eradicated, but OTA-13 has seen it return. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1627144 Title: Received texts merging Status in messaging-app package in Ubuntu: New Bug description: Sometimes, long multi-part texts have their ends truncated and replaced with the end of random texts received months earlier. I can't reproduce it, however if I ask the sender to re-send the long text, it is displayed correctly. The texts are displayed incorrectly in both the Messages app and scope. OTA-12 saw the issue almost eradicated, but OTA-13 has seen it return. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1627144/+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 1626773] Re: CVE-2016-2182.patch has broken BN_bn2dec
Can you see if the regression fix we published today fixes your issue? http://www.ubuntu.com/usn/usn-3087-2/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1626773 Title: CVE-2016-2182.patch has broken BN_bn2dec Status in openssl package in Ubuntu: Incomplete Bug description: My software which links to libcrypto stopped working on both Ubuntu 12.04 / 14.04 / 16.04 last week. The problem is that BN_bn2dec returns NULL all the time (without setting an error message) even for valid input values. I think is a bug in CVE-2016-2182.patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1626773/+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 1615204] [NEW] select-by-word/double-click drag-select only works sporadically on Toshiba Chromebook 1
You have been subscribed to a public bug: (also on Linux kernel bug tracker at https://bugzilla.kernel.org/show_bug.cgi?id=153871) Detailed bug description: In Ubuntu 16.04.1 [1] on the Toshiba Chromebook 1, if you try to select text by word, by double-clicking/triple-touchpad-tapping and then dragging the mouse, this only works occasionally. However, selecting text by line with a triple-click/4-tap drag works fine. This bug does not appear when Ubuntu 16.04.1 is run in a VM in VirtualBox. [1] and now Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 4.4.0-34-generic (the same as for 16.04) Steps to reproduce: 1) On a 1st-generation Toshiba Chromebook (and possibly other machines, too), run Ubuntu 16.04.1 from a boot disk (http://releases.ubuntu.com/16.04/ubuntu-16.04.1-desktop-i386.iso). 2) Open a terminal window and type several words. 3) Double-click/triple-touchpad-tap and then drag the mouse to attempt to select multiple words. 4) Compare this to the same boot disk run in VirtualBox, where it works properly. 5) Compare this to Ubuntu 14.04.5 with the hardware-specific update to Linux kernel 4.4.0-34-generic, where it doesn't work. 6) Compare this to the hardware-specific update but with Linux kernel 4.4.0-34-generic removed (downgraded to 3.16.0-77-generic), where it also doesn't work (and is therefore not a kernel problem, but rather relates to other files in the hardware-specific update). Expected results: Multiple words are selected. Actual result: Only the first word is selected. Reproducibility: Double-click drag-select will work occasionally, but most of the time it doesn't. Workaround: In applications other than Terminal, can use Ctrl+Shift+Right-Arrow to select by word (significantly slower for large text blocks). No known workaround for Terminal. Impact: Recommend not upgrading to 16.04 if you have a computer where double-click drag-select doesn't work in it. Description of the environment: Operation system: Ubuntu 16.04.1 Versions of components: Linux kernel 4.4.0-34-generic (also on Ubuntu 14.04.5) Reference architecture: 1st-generation Toshiba Chromebook (model name "Toshiba Leon") Network model: N/A Related projects installed: none (boot disk) Additional information: N/A --- ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: administrator 1882 F pulseaudio /dev/snd/controlC1: administrator 1882 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2015-04-05 (506 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1) MachineType: Toshiba Leon Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=127e42a1-2015-0521--28e347c5f54d ro tpm_tis.force=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-34.53~14.04.1-generic 4.4.15 RelatedPackageVersions: linux-restricted-modules-4.4.0-34-generic N/A linux-backports-modules-4.4.0-34-generic N/A linux-firmware1.127.22 Tags: trusty Uname: Linux 4.4.0-34-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/26/2014 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Toshiba dmi.modalias: dmi:bvncoreboot:bvr:bd08/26/2014:svnToshiba:pnLeon:pvr1.0:cvnToshiba:ct3:cvr: dmi.product.name: Leon dmi.product.version: 1.0 dmi.sys.vendor: Toshiba ** Affects: linux Importance: Unknown Status: Unknown ** Affects: xorg (Ubuntu) Importance: Medium Status: Incomplete ** Tags: apport-collected kernel-da-key trusty -- select-by-word/double-click drag-select only works sporadically on Toshiba Chromebook 1 https://bugs.launchpad.net/bugs/1615204 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1617963] Re: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured bec
Ayy! My bad. You are right. However, I have encountered this: The option is blanked out. [image: Inline images 1] (for comparison:) [image: Inline images 1] Any thoughts? Yours sincerely, Brandon Camilleri +356 7991 9116 brandon.camilleri...@gmail.com On 23 September 2016 at 15:56, Robie Basak <1617...@bugs.launchpad.net> wrote: > Thank you for helping out! However see > http://askubuntu.com/q/785414/7808: "There is very little benefit to > users in using -proposed during the development cycle and such use is > strongly discouraged." > > Packages in yakkety-proposed that are not in yakkety are *known to be > broken* - otherwise they would migrate to the release pocket within a > few hours. We appreciate you helping out in testing, but I suggest that > you test by using yakkety only - using the proposed pocket provides no > real benefit to developers. > > ** Changed in: heimdal (Ubuntu) >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1617963 > > Title: > package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to > install/upgrade: package libasn1-8-heimdal:amd64 > 1.7~git20160703+dfsg-1 cannot be configured because > libasn1-8-heimdal:i386 is at a different version (1.7~git20150920 > +dfsg-4ubuntu1) > > Status in heimdal package in Ubuntu: > Invalid > > Bug description: > "The following packages have been kept back:" > > 12 packages > > so I ran: > > sudo apt install <12 packages> > > ProblemType: Package > DistroRelease: Ubuntu 16.10 > Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 > ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 > Uname: Linux 4.4.0-9136-generic x86_64 > ApportVersion: 2.20.3-0ubuntu7 > Architecture: amd64 > Date: Mon Aug 29 11:52:32 2016 > Dependencies: >gcc-6-base 6.2.0-1ubuntu12 >libc6 2.24-0ubuntu1 >libcomerr2 1.43.1-1 >libgcc1 1:6.2.0-1ubuntu12 >libroken18-heimdal 1.7~git20160703+dfsg-1 > ErrorMessage: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 > cannot be configured because libasn1-8-heimdal:i386 is at a different > version (1.7~git20150920+dfsg-4ubuntu1) > InstallationDate: Installed on 2016-08-05 (23 days ago) > InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release > amd64 (20160720) > RelatedPackageVersions: >dpkg 1.18.10ubuntu1 >apt 1.3~rc2ubuntu3 > SourcePackage: heimdal > Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to > install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 > cannot be configured because libasn1-8-heimdal:i386 is at a different > version (1.7~git20150920+dfsg-4ubuntu1) > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/ > 1617963/+subscriptions > ** Attachment added: "image.png" https://bugs.launchpad.net/bugs/1617963/+attachment/4747311/+files/image.png ** Attachment added: "image.png" https://bugs.launchpad.net/bugs/1617963/+attachment/4747312/+files/image.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1617963 Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured because libasn1-8-heimdal:i386 is at a different version (1.7~git20150920 +dfsg-4ubuntu1) Status in heimdal package in Ubuntu: Invalid Bug description: "The following packages have been kept back:" 12 packages so I ran: sudo apt install <12 packages> ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Mon Aug 29 11:52:32 2016 Dependencies: gcc-6-base 6.2.0-1ubuntu12 libc6 2.24-0ubuntu1 libcomerr2 1.43.1-1 libgcc1 1:6.2.0-1ubuntu12 libroken18-heimdal 1.7~git20160703+dfsg-1 ErrorMessage: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured because libasn1-8-heimdal:i386 is at a different version (1.7~git20150920+dfsg-4ubuntu1) InstallationDate: Installed on 2016-08-05 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: heimdal Title: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 failed to install/upgrade: package libasn1-8-heimdal:amd64 1.7~git20160703+dfsg-1 cannot be configured because libasn1-8-heimdal:i386 is at a different version (1.7~git20150920+dfsg-4ubuntu1) UpgradeStatus: No upgrade log
[Touch-packages] [Bug 1627137] Re: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal()
*** This bug is a duplicate of bug 1608560 *** https://bugs.launchpad.net/bugs/1608560 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1608560, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1627137/+attachment/4747302/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1627137/+attachment/4747304/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1627137/+attachment/4747306/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1627137/+attachment/4747307/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1627137/+attachment/4747308/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1627137/+attachment/4747309/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1627137/+attachment/4747310/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1608560 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1627137 Title: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal() Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Bug description: Crash occurred when adding a Ubuntu One account. Selected the Ubuntu One from the listView, then the UI freezed. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: ubuntu-system-settings-online-accounts 0.7+16.10.20160718-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7 Uname: Linux 4.8.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Fri Sep 23 18:44:10 2016 ExecutablePath: /usr/bin/online-accounts-ui InstallationDate: Installed on 2016-02-15 (220 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) ProcCmdline: /usr/bin/online-accounts-ui --socket /run/user/1000/online-accounts-ui/ui-1-ubuntuone --profile unconfined ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=pt:pt_BR:en LANG=pt_PT.UTF-8 Signal: 6 SourcePackage: ubuntu-system-settings-online-accounts StacktraceTop: QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 Title: online-accounts-ui crashed with SIGABRT in QMessageLogger::fatal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1627137/+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 1626737] Re: [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel oops
** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1626737 Title: [4.8.0-14/ppc64el regression] rmmod scsi_debug keeps causing kernel oops Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Bug description: Since upgrading to 4.8.0-14, the "storage" autopkgtest of systemd is broken. This uses scsi_debug to get a test hard drive, which is reset between the test through unloading/reloading the module. This has worked fine so far (and still works on amd64/i386), but now regularly triggers a kernel oops: [ 161.120362] Unable to handle kernel paging request for data at address 0x [ 161.120468] Faulting instruction address: 0xc0538ecc [ 161.120517] Oops: Kernel access of bad area, sig: 11 [#1] [ 161.120555] SMP NR_CPUS=2048 NUMA pSeries [ 161.120595] Modules linked in: dm_crypt dm_mod xts algif_skcipher af_alg sd_mod sg xt_TCPMSS xt_tcpudp iptable_mangle ghash_generic gf128mul vmx_crypto virtio_balloon ip_tables x_tables autofs4 ext4 crc16 jbd2 fscrypto mbcache crc32c_generic btrfs xor raid6_pq ohci_pci ehci_pci ohci_hcd virtio_blk virtio_net ehci_hcd usbcore crc32c_vpmsum usb_common virtio_pci virtio_ring virtio [last unloaded: scsi_debug] [ 161.121016] CPU: 0 PID: 5473 Comm: rmmod Not tainted 4.8.0-15-generic #16-Ubuntu [ 161.121067] task: c0005ae51980 task.stack: c0005ef58000 [ 161.121110] NIP: c0538ecc LR: c0538ee0 CTR: c00f7250 [ 161.121162] REGS: c0005ef5b9f0 TRAP: 0300 Not tainted (4.8.0-15-generic) [ 161.121213] MSR: 80010280b033CR: 28002444 XER: 2000 [ 161.121390] CFAR: c009a8e0 DAR: DSISR: 4000 SOFTE: 1 GPR00: c0538e98 c0005ef5bc70 c0f67b00 GPR04: d1302018 0002 c10d7b00 GPR08: c0fa7b00 0063 0073 0004 GPR12: 28002844 cfb8 GPR16: 0100331f11f0 384b3890 384b3848 GPR20: 384b3830 384b3870 384b38a8 384b3888 GPR24: 3fffd23d6e70 c0ebdec8 fffe d1302018 GPR28: c0ebdeb8 [ 161.122099] NIP [c0538ecc] ddebug_remove_module+0x8c/0x160 [ 161.122143] LR [c0538ee0] ddebug_remove_module+0xa0/0x160 [ 161.122186] Call Trace: [ 161.122205] [c0005ef5bc70] [c0538e98] ddebug_remove_module+0x58/0x160 (unreliable) [ 161.122280] [c0005ef5bd10] [c018961c] free_module+0x21c/0x3c0 [ 161.122333] [c0005ef5bd60] [c0189a38] SyS_delete_module+0x278/0x2f0 [ 161.122394] [c0005ef5be30] [c00095e0] system_call+0x38/0x108 [ 161.122445] Instruction dump: [ 161.122472] 3d42fff5 e92a63b8 7fa9e000 7d3d4b78 ebe9 419e00bc 7d3e4b78 3b40fffe [ 161.122561] 4818 7fbfe000 7ffdfb78 7ffefb78 419e0060 e87e0010 7f64db78 [ 161.122651] ---[ end trace 5f19b96c7077a0e0 ]--- This isn't reproducible by merely loading and unloading the module, it apparently needs to get some actual exercise. I'll find a simpler reproducer than running the systemd test tomorrow morning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626737/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
report (via SSH): click list | grep libertine libertine-scope.ubuntu 1.3.2.2 sudo click unregister --user phablet libertine-scope.ubuntu (process:4396): Json-CRITICAL **: json_object_get_string_member: assertion 'node != NULL' failed Unable to find application for 'libertine-scope.ubuntu_libertine-scope_1.3.2.2': Manifest for application 'libertine-scope' does not have a 'desktop' hook phablet@ubuntu-phablet:~$ click list | grep libertine phablet@ubuntu-phablet:~$ Then I'm going to Ubuntu App Store (on device) and install Desktop Apps Scope 1.3.2.2 and then I launch this scope. Empty! phablet@ubuntu-phablet:~$ click list | grep libertine libertine-scope.ubuntu 1.3.2.2 and the same thing: top - 00:54:11 up 30 min, 2 users, load average: 11,23, 10,83, 7,57 Tasks: 262 total, 6 running, 256 sleeping, 0 stopped, 0 zombie %Cpu(s): 9,8 us, 4,4 sy, 0,0 ni, 85,6 id, 0,2 wa, 0,0 hi, 0,0 si, 0,0 st KiB Mem: 2009416 total, 1094052 used, 915364 free,18364 buffers KiB Swap: 524284 total,0 used, 524284 free. 176856 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2694 phablet 20 0 672028 166964 77496 R 99,5 8,3 2:00.89 unity8-dash 5582 phablet 20 06260 1156752 R 11,7 0,1 0:00.04 top 1 root 20 03928 2456 1080 S 0,0 0,1 0:03.81 init 2 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kthreadd 3 root 20 0 0 0 0 S 0,0 0,0 0:00.06 ksoftirqd/0 :( ** Attachment added: "screenshot20160924_005509827.png" https://bugs.launchpad.net/today-scope/+bug/1626180/+attachment/4747295/+files/screenshot20160924_005509827.png -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1466758] Re: /usr/bin/unity8-dash:url-dispatcher-bad-url
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1466758 Title: /usr/bin/unity8-dash:url-dispatcher-bad-url Status in unity8 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.10+15.10.20150612-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/44e14f0d852df94e252d39bcb88f9005df3b5b7d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1466758/+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 1622002] Fix proposed to neutron (stable/newton)
Fix proposed to branch: stable/newton Review: https://review.openstack.org/375645 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1622002 Title: dhcp_release6 can be called when it is not present Status in neutron: In Progress Status in dnsmasq package in Ubuntu: New Bug description: If someone enables dhcpv6-stateful addressing on a subnet, but they are running an old version of dnsmasq (<2.76), then the dhcp agent could try and run dhcp_release6 even though it isn't present. An example: http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron- multinode-full-ubuntu- xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272 Checking it's present first would fix this problem. Since the change to call dhcp_release6 was just added in https://review.openstack.org/#/c/301747/ we should fix this before Newton ships and people complain. There is also an effort to get Cirros to support DHCPv6 so that we can test this in the gate, https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so we can add a functional test. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1622002/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
Vladimir: let's try uninstalling your desktop apps scope as follows: phablet@ubuntu-phablet:~$ click list | grep libertine libertine-scope.ubuntu 1.3.2.1 phablet@ubuntu-phablet:~$ sudo click unregister --user phablet libertine-scope.ubuntu [sudo] password for phablet: (process:20113): Json-CRITICAL **: json_object_get_string_member: assertion 'node != NULL' failed Unable to find application for 'libertine-scope.ubuntu_libertine-scope_1.3.2.1': Manifest for application 'libertine-scope' does not have a 'desktop' hook phablet@ubuntu-phablet:~$ click list | grep libertine then, install the scope from the store. see if we've fixed it. -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
yes, it does: phablet@ubuntu-phablet:~$ libertine-container-manager list-apps --json | grep name error processing /home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-xsltfilter.desktop: 'Desktop Entry' "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/firefox.desktop", "name": "Firefox Web Browser", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/gedit.desktop", "name": "gedit", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/gimp.desktop", "name": "GIMP Image Editor", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-base.desktop", "name": "LibreOffice Base", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-calc.desktop", "name": "LibreOffice Calc", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-draw.desktop", "name": "LibreOffice Draw", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-impress.desktop", "name": "LibreOffice Impress", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-math.desktop", "name": "LibreOffice Math", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-startcenter.desktop", "name": "LibreOffice", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-writer.desktop", "name": "LibreOffice Writer", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/mb-panel-manager.desktop", "name": "Panel Manager", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/notification-daemon.desktop", "name": "Notification Daemon", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/openjdk-7-java.desktop", "name": "OpenJDK Java 7 Runtime", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/openjdk-7-policytool.desktop", "name": "OpenJDK Java 7 Policy Tool", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/python2.7.desktop", "name": "Python (v2.7)", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/python3.4.desktop", "name": "Python (v3.4)", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/xchat-gnome.desktop", "name": "XChat-GNOME", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/yelp.desktop", "name": "Help", "name": "Desktop Applications" -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1627122] [NEW] laptop inbuilt speaker does not work it shows dummy output
Public bug reported: a hcl leaptop no sound at all is heard neither does inbuilt sound system nor earphones work ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Sep 23 22:45:51 2016 InstallationDate: Installed on 2016-02-11 (225 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.00.04 dmi.board.name: TN120R dmi.board.vendor: HCL Infosystems Limited dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.00.04:bd03/26/2008:svnHCLInfosystemsLimited:pnTN120R:pvrNotApplicable:rvnHCLInfosystemsLimited:rnTN120R:rvrNotApplicable:cvnNoEnclosure:ct9:cvrN/A: dmi.product.name: TN120R dmi.product.version: Not Applicable dmi.sys.vendor: HCL Infosystems Limited ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1627122 Title: laptop inbuilt speaker does not work it shows dummy output Status in alsa-driver package in Ubuntu: New Bug description: a hcl leaptop no sound at all is heard neither does inbuilt sound system nor earphones work ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Sep 23 22:45:51 2016 InstallationDate: Installed on 2016-02-11 (225 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.00.04 dmi.board.name: TN120R dmi.board.vendor: HCL Infosystems Limited dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.00.04:bd03/26/2008:svnHCLInfosystemsLimited:pnTN120R:pvrNotApplicable:rvnHCLInfosystemsLimited:rnTN120R:rvrNotApplicable:cvnNoEnclosure:ct9:cvrN/A: dmi.product.name: TN120R dmi.product.version: Not Applicable dmi.sys.vendor: HCL Infosystems Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1627122/+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 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
Did the update to OTA13 on a Meizu MX4 and trying to connect to an Audi bluetooth system: - First, the phone sayd it was connected to the bluetooth system but the car didn't agree. - After removing the known devices on both the car and the phone (and restarting the phone) the phone doesn't detect the car bluetooth system. So for me, big step backwards. (Hoping on one step backwards on OTA13 and two steps forwards on OTA14...) If new debug info/logs are useful, please let me know... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1622002] Re: dhcp_release6 can be called when it is not present
** Changed in: neutron Milestone: ocata-1 => newton-rc2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1622002 Title: dhcp_release6 can be called when it is not present Status in neutron: In Progress Status in dnsmasq package in Ubuntu: New Bug description: If someone enables dhcpv6-stateful addressing on a subnet, but they are running an old version of dnsmasq (<2.76), then the dhcp agent could try and run dhcp_release6 even though it isn't present. An example: http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron- multinode-full-ubuntu- xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272 Checking it's present first would fix this problem. Since the change to call dhcp_release6 was just added in https://review.openstack.org/#/c/301747/ we should fix this before Newton ships and people complain. There is also an effort to get Cirros to support DHCPv6 so that we can test this in the gate, https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so we can add a functional test. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1622002/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
does this command list any libertine apps: libertine-container-manager list-apps --json | grep name phablet@ubuntu-phablet:~$ libertine-container-manager list-apps --json | grep name error processing /home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-xsltfilter.desktop: 'Desktop Entry' "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/notification-daemon.desktop", "name": "Notification Daemon", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-base.desktop", "name": "LibreOffice Base", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/mb-panel-manager.desktop", "name": "Panel Manager", "desktop_file_name": "/home/phablet/.cache/libertine-container/puritine/rootfs/usr/share/applications/libreoffice-calc.desktop", "name": "LibreOffice Calc", ... -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1627078] Re: ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property
@Andrea - Sure, no problem! ;) @Tim - Yes, checking for e.g. 'verticalVelocity' property of the Flickable could accomplish it. QQC2 are not provided with the Ubuntu UI Toolkit and they are available only with Qt 5.7, so I would prefer a solution which can be easily integrated in a Ubuntu convergent app. I'll have a try checking for the velocity of the flick action, since it may be desiderable to show such overlay for any 'fast-scroll' event. However, I wanted to provide an example why such property could be useful also for UITK ScrollBars. Calling it 'pressed' for consistence sounds good to me. Thank you guys for the fast reply, have a great weekend! -- 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/1627078 Title: ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I'm trying to implement a "page indicator" to be shown when the user scrolls a Flickable using a UITK ScrollBar. The idea is to mimic a feature available in Adobe Reader for Android. i.e. http://imgur.com/a/OzjYG In order to do this, I have to access the "draggingThumb" property of the style instance of a UITK ScrollBar, which is meant to be private. Item { [...] visible: scrollView.verticalScrollbar.__styleInstance.draggingThumb } What it could be useful is to expose this property directly in the ScrollBar. Using the Flickable properties for this purpose would be a bit complicated, since it wouldn't be desiderable to see such overlay during an "ordinary" touch/flick event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1627078/+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 1626435] Re: Keyboard layout not applied on the shell
** Branch linked: lp:~andreas-pokorny/mir/fix-1626435 -- 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/1626435 Title: Keyboard layout not applied on the shell Status in Canonical System Image: Triaged Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Split out from bug #1611859: Steps: * connect a BT or a physical keyboard * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot * go through the wizard Expected: * I can use the selected layout in the wizard * and in snap decisions Current: * you can only use us layout in the shell ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.14+16.04.20160914-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-landing-078] ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 22 10:07:47 2016 InstallationDate: Installed on 2016-05-06 (138 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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/1626435/+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 1626435] Re: Keyboard layout not applied on the shell
** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Andreas Pokorny (andreas-pokorny) -- 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/1626435 Title: Keyboard layout not applied on the shell Status in Canonical System Image: Triaged Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Split out from bug #1611859: Steps: * connect a BT or a physical keyboard * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot * go through the wizard Expected: * I can use the selected layout in the wizard * and in snap decisions Current: * you can only use us layout in the shell ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.14+16.04.20160914-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-landing-078] ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 22 10:07:47 2016 InstallationDate: Installed on 2016-05-06 (138 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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/1626435/+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 1588526] Re: Alarm doesn't ring when screen locked
This affects me on BQ Aqarius M10 since OTA13. I have previously successfully used the alarm pre - OTA13. This happened the morning before last. Last night I changed the alarm sound to a different sound and while I woke before the alarm was due to go off when it did go off it had the default alarm sound (I was reading a book at the time so the screen was active). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1627105] Re: Opening a certain number of windows closes already open windows
Note this doesn't seem to be a memory pressure as the qmlscene process is around 40MB. -- 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/1627105 Title: Opening a certain number of windows closes already open windows Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I'm not sure this is specifically the ubuntu-ui-toolkit, but if I use a Label vs Text seems to affect the number of windows I can open so thought I'd check here first. What happened: 1) Branch the demo-app [0] 2) Launch the app 3) Notice a window appears with a number 4) Click anywhere in the window to launch another window with an incremented number 5) Keep clicking on the first window, generating a large number of windows 6) Notice at a certain number as the window is spawning all the other windows close. For me this happens at different times depending on the environment/app, if I change the Label inside the Window to Text it happens later, or if I switch from the LXD/LXC based SDK to running $ qmlscene directly on the host this also increases the number of windows I can generate. --|-Label-|-Text-| LXD---|---61--|--81--| Host--|--125--|--143-| What I expected to happen: For me to be able to keep generating a number of windows without other windows being closed. Note: When I found this issue in a more complex app, the lowest limit was 14 not 61 windows, so the complexity of the app may affect this. 0 - https://code.launchpad.net/~ahayzen/+junk/multi-window-issue Environment: Unity7, 16.04, with stable overlay PPA. $ apt-cache policy qtdeclarative5-ubuntu-ui-toolkit-plugin ubuntu-sdk-ide qtdeclarative5-ubuntu-ui-toolkit-plugin: Installed: 1.3.2085+16.04.20160916 Candidate: 1.3.2085+16.04.20160916 Version table: *** 1.3.2085+16.04.20160916 100 100 /var/lib/dpkg/status 1.3.2085+16.04.20160915 500 500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages 1.3.1918+16.04.20160404-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ubuntu-sdk-ide: Installed: 4.1.0~161+201609151241~ubuntu16.04.1 Candidate: 4.1.0~161+201609151241~ubuntu16.04.1 Version table: *** 4.1.0~161+201609151241~ubuntu16.04.1 500 500 http://ppa.launchpad.net/ubuntu-sdk-team/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1627105/+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 1627112] [NEW] [Wizard] Spanish (Spain) cannot be selected
Public bug reported: Test case. - Fresh install. - In Language, scroll and tap on "Spanish (Spain)". Expected result - Spanish (Spain) language is selected. Actual result. - Spanish (Spain) language cannot be selected. Sometimes during the installation wizard, when I touch on "Spanish (Spain)" I can't select this language. The other Spanish options can be selected, though. This has happened to me using frieza and turbo. It doesn't happen always. Cannot see any warning on unity8.log. current build number: 186 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: qa-silo ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Description changed: Test case. - Fresh install. - In Language, scroll and tap on "Spanish (Spain)". Expected result - Spanish (Spain) language is selected. Actual result. - Spanish (Spain) language cannot be selected. Sometimes during the installation wizard, when I touch on "Spanish (Spain)" I can't select this language. The other Spanish options can be - selected, though. This has happened to me using frieza and arale. It + selected, though. This has happened to me using frieza and turbo. It doesn't happen always. Cannot see any warning on unity8.log. + + current build number: 186 + device name: turbo + channel: ubuntu-touch/rc-proposed/meizu-pd.en -- 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/1627112 Title: [Wizard] Spanish (Spain) cannot be selected Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: Test case. - Fresh install. - In Language, scroll and tap on "Spanish (Spain)". Expected result - Spanish (Spain) language is selected. Actual result. - Spanish (Spain) language cannot be selected. Sometimes during the installation wizard, when I touch on "Spanish (Spain)" I can't select this language. The other Spanish options can be selected, though. This has happened to me using frieza and turbo. It doesn't happen always. Cannot see any warning on unity8.log. current build number: 186 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627112/+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 1622002] Re: dhcp_release6 can be called when it is not present
Actually, the impact here is actually making allocation reloading completely broken for dhcpv6-stateful networks, something that was not completely clear to me until I read the code. I actually now prefer we get it in rc2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1622002 Title: dhcp_release6 can be called when it is not present Status in neutron: In Progress Status in dnsmasq package in Ubuntu: New Bug description: If someone enables dhcpv6-stateful addressing on a subnet, but they are running an old version of dnsmasq (<2.76), then the dhcp agent could try and run dhcp_release6 even though it isn't present. An example: http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron- multinode-full-ubuntu- xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272 Checking it's present first would fix this problem. Since the change to call dhcp_release6 was just added in https://review.openstack.org/#/c/301747/ we should fix this before Newton ships and people complain. There is also an effort to get Cirros to support DHCPv6 so that we can test this in the gate, https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so we can add a functional test. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1622002/+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 1626180] Re: Desktop Apps scope hangs unity8-dash
Kyle, I've just installed click-package libertine- scope.ubuntu_1.3.2.1_armhf.click: phablet@ubuntu-phablet:~$ pkcon install-local --allow-untrusted libertine-scope.ubuntu_1.3.2.1_armhf.click Установка файлов[=] Завершено[=] Установка файлов[=] Начало [=] Завершено[=] Установленный libertine-scope.ubuntu-1.3.2.1.armhf (installed:click,removable=1,app_name=libertine-scope) summary goes here phablet@ubuntu-phablet:~$ Then I tried to run "Desktop App Scope" -- no changes: top - 23:34:56 up 2 min, 2 users, load average: 11,23, 4,94, 1,87 Tasks: 265 total, 6 running, 257 sleeping, 2 stopped, 0 zombie %Cpu(s): 50,5 us, 0,8 sy, 0,0 ni, 48,7 id, 0,0 wa, 0,0 hi, 0,0 si, 0,0 st KiB Mem: 2009416 total, 1317888 used, 691528 free,49300 buffers KiB Swap: 524284 total,0 used, 524284 free. 369340 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2692 phablet 20 0 596608 130704 74088 R 99,5 6,5 1:46.25 unity8-dash 83 root 20 0 0 0 0 S 1,7 0,0 0:00.43 kworker/u8+ 4233 phablet 20 06264 1268812 R 0,7 0,1 0:00.06 top 89 root -92 0 0 0 0 S 0,3 0,0 0:00.20 hdmi_timer+ 1027 root 20 0 25268 3008 2076 S 0,3 0,1 0:00.24 Binder_2 2221 phablet 20 0 705928 211004 93824 S 0,3 10,5 0:12.61 unity8 1 root 20 03900 2340 1080 S 0,0 0,1 0:03.17 init 2 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kthreadd 3 root 20 0 0 0 0 S 0,0 0,0 0:00.02 ksoftirqd/0 4 root 20 0 0 0 0 S 0,0 0,0 0:00.00 kworker/0:0 5 root 0 -20 0 0 0 S 0,0 0,0 0:00.00 kworker/0:+ 6 root 20 0 0 0 0 S 0,0 0,0 0:00.77 kworker/u8+ 7 root -99 0 0 0 0 S 0,0 0,0 0:00.01 migration/0 8 root 20 0 0 0 0 S 0,0 0,0 0:00.06 rcu_preempt 9 root 20 0 0 0 0 S 0,0 0,0 0:00.00 rcu_bh 10 root 20 0 0 0 0 S 0,0 0,0 0:00.00 rcu_sched 11 root -99 0 0 0 0 S 0,0 0,0 0:00.01 migration/1 And "Desktop App Scope" is still empty (see attached picture). But before this bug there are applications of puritine and of my-container. Maybe problem is with this fix, I did before to make my-container: # cd ~/.local/share/libertine # rm ContainersConfig.json # cp /custom/click/.click/users/@all/com.ubuntu.puritine/libertine-config/libertine/ContainersConfig.json . or when I changed Resolution for X application: in ~/.local/share/libertine-container/user-data/my-container/.Xdefaults Xft.dpi: 224 ??? ** Attachment added: "screenshot20160923_233429296.png" https://bugs.launchpad.net/today-scope/+bug/1626180/+attachment/4747200/+files/screenshot20160923_233429296.png -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1626987] Re: openssl update may have broken puppet cert sign
See #1626883 ** Changed in: openssl (Ubuntu) Status: Confirmed => Fix Released ** Changed in: puppet (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1626987 Title: openssl update may have broken puppet cert sign Status in openssl package in Ubuntu: Fix Released Status in puppet package in Ubuntu: Invalid Bug description: After tonight's openssl update on our puppet CA server, we can no longer sign puppet certificates: root@sistemes:~# puppet cert sign vm-host-14.ac.upc.es Notice: Signed certificate request for vm-host-14.ac.upc.es Error: root@sistemes:~# puppet ca sign vm-host-14.ac.upc.es Notice: Signed certificate request for vm-host-14.ac.upc.es Error: Error: Try 'puppet help ca sign' for usage AFAICT, no other changes on the puppet CA have been performed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssl 1.0.1f-1ubuntu2.20 ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39 Uname: Linux 3.13.0-96-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Sep 23 13:41:12 2016 InstallationDate: Installed on 2010-05-25 (2313 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openssl UpgradeStatus: Upgraded to trusty on 2015-02-05 (596 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1626987/+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 1627105] [NEW] Opening a certain number of windows closes already open windows
Public bug reported: I'm not sure this is specifically the ubuntu-ui-toolkit, but if I use a Label vs Text seems to affect the number of windows I can open so thought I'd check here first. What happened: 1) Branch the demo-app [0] 2) Launch the app 3) Notice a window appears with a number 4) Click anywhere in the window to launch another window with an incremented number 5) Keep clicking on the first window, generating a large number of windows 6) Notice at a certain number as the window is spawning all the other windows close. For me this happens at different times depending on the environment/app, if I change the Label inside the Window to Text it happens later, or if I switch from the LXD/LXC based SDK to running $ qmlscene directly on the host this also increases the number of windows I can generate. --|-Label-|-Text-| LXD---|---61--|--81--| Host--|--125--|--143-| What I expected to happen: For me to be able to keep generating a number of windows without other windows being closed. Note: When I found this issue in a more complex app, the lowest limit was 14 not 61 windows, so the complexity of the app may affect this. 0 - https://code.launchpad.net/~ahayzen/+junk/multi-window-issue Environment: Unity7, 16.04, with stable overlay PPA. $ apt-cache policy qtdeclarative5-ubuntu-ui-toolkit-plugin ubuntu-sdk-ide qtdeclarative5-ubuntu-ui-toolkit-plugin: Installed: 1.3.2085+16.04.20160916 Candidate: 1.3.2085+16.04.20160916 Version table: *** 1.3.2085+16.04.20160916 100 100 /var/lib/dpkg/status 1.3.2085+16.04.20160915 500 500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages 1.3.1918+16.04.20160404-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ubuntu-sdk-ide: Installed: 4.1.0~161+201609151241~ubuntu16.04.1 Candidate: 4.1.0~161+201609151241~ubuntu16.04.1 Version table: *** 4.1.0~161+201609151241~ubuntu16.04.1 500 500 http://ppa.launchpad.net/ubuntu-sdk-team/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09 ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1627105 Title: Opening a certain number of windows closes already open windows Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I'm not sure this is specifically the ubuntu-ui-toolkit, but if I use a Label vs Text seems to affect the number of windows I can open so thought I'd check here first. What happened: 1) Branch the demo-app [0] 2) Launch the app 3) Notice a window appears with a number 4) Click anywhere in the window to launch another window with an incremented number 5) Keep clicking on the first window, generating a large number of windows 6) Notice at a certain number as the window is spawning all the other windows close. For me this happens at different times depending on the environment/app, if I change the Label inside the Window to Text it happens later, or if I switch from the LXD/LXC based SDK to running $ qmlscene directly on the host this also increases the number of windows I can generate. --|-Label-|-Text-| LXD---|---61--|--81--| Host--|--125--|--143-| What I expected to happen: For me to be able to keep generating a number of windows without other windows being closed. Note: When I found this issue in a more complex app, the lowest limit was 14 not 61 windows, so the complexity of the app may affect this. 0 - https://code.launchpad.net/~ahayzen/+junk/multi-window-issue Environment: Unity7, 16.04, with stable overlay PPA. $ apt-cache policy qtdeclarative5-ubuntu-ui-toolkit-plugin ubuntu-sdk-ide qtdeclarative5-ubuntu-ui-toolkit-plugin: Installed: 1.3.2085+16.04.20160916 Candidate: 1.3.2085+16.04.20160916 Version table: *** 1.3.2085+16.04.20160916 100 100 /var/lib/dpkg/status 1.3.2085+16.04.20160915 500 500 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu xenial/main amd64 Packages 1.3.1918+16.04.20160404-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages ubuntu-sdk-ide: Installed: 4.1.0~161+201609151241~ubuntu16.04.1 Candidate: 4.1.0~161+201609151241~ubuntu16.04.1 Version table: *** 4.1.0~161+201609151241~ubuntu16.04.1 500 500 http://ppa.launchpad.net/ubuntu-sdk-team/ppa/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release:
[Touch-packages] [Bug 1572653] Re: keyboard does not show up on xenial
Hi Kris, Your issue appears to be unrelated to this bug report (which relates specifically to running the keyboard on an X11 desktop system); whereas you're attempting to run an XMir application on the phone outside of libertine, which isn't something we've tested much previously. Firstly could you make sure you have maliit-inputcontext-gtk3 and maliit- inputcontext-gtk2 installed, these provide GTK support for the OSK and wouldn't be installed by default on the phone (except inside libertine containers). If the problem still persists with those installed could you file a separate bug report for this and we'll try to look into it further Thanks :) -- 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/1572653 Title: keyboard does not show up on xenial Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Expected behaviour: Install ubuntu-keyboard, run maliit-server, click on place to enter text -> keyboard shows up. What happens: Running maliit-server after installing ubuntu-keyboard-english in terminal shows following error: WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is not enabled Clicking on fields for entering text, does not cause the keyboard to show up. What I tried so far: export QT_IM_MODULE=Maliit export GTK_IM_MODULE=Maliit and gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled "[llibubuntu-keyboard-plugin.so,en_gb]" gconftool-2 -s --type list --list-type string /maliit/onscreen/active "[libubuntu-keyboard-plugin.so,en_gb]" according to https://github.com/maliit/framework and https://github.com/maliit/plugins but it still won't show up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 18:03:03 2016 InstallationDate: Installed on 2016-04-03 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.maliit.org.server.conf: [modified] mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1572653/+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 1626883] Re: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault
** Changed in: openssl (Ubuntu Yakkety) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1626883 Title: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault Status in openssl package in Ubuntu: Invalid Status in openssl source package in Precise: Fix Released Status in openssl source package in Trusty: Fix Released Status in openssl source package in Xenial: Fix Released Status in openssl source package in Yakkety: Invalid Bug description: Last night unattended-upgrades upgraded the openssl packages (libssl1.0.0, libssl-dev, openssl) from version 1.0.2g-1ubuntu4.1 to version 1.0.2g-1ubuntu4.4 on a CI build server. Then everything that used PHP to connect to a HTTPS site started crashing when verifying the server cert. Like this: ``` jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$ DATABASE_DATABASE=wordpressmastere2e catchsegv wp plugin install --force --activate wp-cfm Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; WP_Import has a deprecated constructor in /var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop /vagrant/wordpress/wp-content/plugins/wordpress-importer/wordpress-importer.php on line 38 Notice: Undefined offset: 4 in phar:///usr/local/bin/wp/php/WP_CLI/DocParser.php on line 124 Segmentation fault (core dumped) *** Segmentation fault Register dump: RAX: RBX: 0001 RCX: RDX: 000c RSI: 55665071af59 RDI: RBP: 556650a49e4e R8 : 556652364720 R9 : R10: R11: 7fdb3c081730 R12: 55665071af59 R13: 000c R14: R15: 7fdb39418cf0 RSP: 7ffc4bad7a08 RIP: 7fdb3bf77d16 EFLAGS: 00010293 CS: 0033 FS: GS: Trap: 000e Error: 0004 OldMask: CR2: FPUCW: 027f FPUSW: TAG: RIP: RDP: ST(0) ST(1) ST(2) ST(3) ST(4) ST(5) ST(6) ST(7) mxcsr: 1fa0 XMM0: XMM1: XMM2: XMM3: XMM4: XMM5: XMM6: XMM7: XMM8: XMM9: XMM10: XMM11: XMM12: XMM13: XMM14: XMM15: Backtrace: /lib/x86_64-linux-gnu/libc.so.6(strlen+0x26)[0x7fdb3bf77d16] php(add_assoc_string_ex+0x32)[0x556650677b12] php(zif_openssl_x509_parse+0x17c)[0x5566505312ec] php(dtrace_execute_internal+0x2a)[0x556650664b3a] php(+0x2e37e0)[0x5566506f97e0] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(zend_call_function+0x749)[0x55665039] php(zif_call_user_func+0xb5)[0x5566505b39d5] php(dtrace_execute_internal+0x2a)[0x556650664b3a] php(+0x2e37e0)[0x5566506f97e0] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(zend_call_function+0x749)[0x55665039] php(zif_call_user_func+0xb5)[0x5566505b39d5]
[Touch-packages] [Bug 1627078] Re: ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property
Would there be any other ways to show the overlay? For example by flicking the Flickable really fast? Then maybe it is better to use a property of the flickable. Also, to keep the APIs consistent, maybe there should be property 'pressed' which is similar to MouseArea.pressed. Also, we can have a look at the API for QtQuickControls 2 Scrollbar, which has a 'pressed' and 'active' property: http://doc.qt.io/qt-5/qml-qtquick- controls2-scrollbar.html -- 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/1627078 Title: ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I'm trying to implement a "page indicator" to be shown when the user scrolls a Flickable using a UITK ScrollBar. The idea is to mimic a feature available in Adobe Reader for Android. i.e. http://imgur.com/a/OzjYG In order to do this, I have to access the "draggingThumb" property of the style instance of a UITK ScrollBar, which is meant to be private. Item { [...] visible: scrollView.verticalScrollbar.__styleInstance.draggingThumb } What it could be useful is to expose this property directly in the ScrollBar. Using the Flickable properties for this purpose would be a bit complicated, since it wouldn't be desiderable to see such overlay during an "ordinary" touch/flick event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1627078/+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 1627078] Re: ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property
^ Using the API of QQC2 Scrollbar you can accomplish what you want. In onPositionChanged, you can check if 'pressed' is true and then enable the overlay. You can hide the overlay again when pressed becomes false. -- 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/1627078 Title: ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I'm trying to implement a "page indicator" to be shown when the user scrolls a Flickable using a UITK ScrollBar. The idea is to mimic a feature available in Adobe Reader for Android. i.e. http://imgur.com/a/OzjYG In order to do this, I have to access the "draggingThumb" property of the style instance of a UITK ScrollBar, which is meant to be private. Item { [...] visible: scrollView.verticalScrollbar.__styleInstance.draggingThumb } What it could be useful is to expose this property directly in the ScrollBar. Using the Flickable properties for this purpose would be a bit complicated, since it wouldn't be desiderable to see such overlay during an "ordinary" touch/flick event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1627078/+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 1626826] Re: KVM guest cannot use br0 created by brctl on Ubuntu16.04
Hi, I was checking by starting with a common setup I ususlly use adapting towards your case step by step. uvt-simplestreams-libvirt sync --source http://cloud-images.ubuntu.com/daily release=xenial arch=s390x label=daily uvt-simplestreams-libvirt query uvt-kvm create --memory 2048 --cpu 4 --password=ubuntu --template template-s390x.xml kvmguest-xenial release=xenial arch=s390x label=daily cat template-s390x.xml hvm virsh dumpxml kvmguest-xenial [...] [...] Ok, so far things are fine - I have a bridge brctl show virbr0 bridge name bridge id STP enabled interfaces virbr0 8000.5254006ec370 yes virbr0-nic vnet0 The guest is connecte to that. The bridge is the default libvirt way of handling default network (nat). The guest gets a dhcp (from host) address on that net 192.168.122.241 in my case. This gets to the Host just nice and works to get to the outside as well via the host. Changing the guest to a static IP in guest e/n/i auto eth0 iface eth0 inet static address 192.168.122.241/24 gateway 192.168.122.1 Still working fine. Changing that to a guest linked to a bride looks like Unfortunately my net setup here is very demaning with vlan only. Could one send me 10 extra OSAs so we can autotagging by the switch :-) ? It is just very complex to get bridge, onto only one Host interface that has vlan required to be set up correctly. So before doing all that I'd like to ask a few questions: But to go on I think it is time to ask you how exactly you 1. defined the bridge and host networking in your case (exact commands to set up your bridge + brctl show on the bridge + host ifconfig -a and route) 2. connected the bridge to your guest (see my xml example above, how does yours look like?) 3. is it a hard requirement that there is only one Host network device? ** Changed in: bridge-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1626826 Title: KVM guest cannot use br0 created by brctl on Ubuntu16.04 Status in Ubuntu on IBM z Systems: New Status in bridge-utils package in Ubuntu: Incomplete Bug description: == Comment: #0 - QI YE - 2016-09-22 06:01:59 == ---Problem Description--- Ubuntu16.04. Created a bridge br0 on enc100 via brctl. enc100 is the only external accessible nic. Defined a ubuntu guest to use br0 and assigned an IP to the guest in the same subnet as br0. After started the guest, couldn't access external servers or internet from the guest. ---uname output--- Linux ntc170 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:47:15 UTC 2016 s390x s 390x s390x GNU/Linux Machine Type = 2827 (z Systems EC12) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. define br0 on enc100 via brctl command (IP on br0 is 192.168.1.170 for example) 2. update /etc/network/interfaces 3. create a guest on KVM and use br0 for it's nic 4. Start guest via virsh command and assign an IP, e.g. 192.168.1.171. After installation, cannot access external systems via KVM host. == Comment: #2 - QI YE - 2016-09-22 09:53:58 == attached sosreport file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1626826/+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 1627078] Re: ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property
Hi Stefano, thank you for this report. I'll bring this up with the SDK team and see if we can "afford" providing (which means guaranteeing future compatibility for) that property ;) Can you please ping me again on Monday about this? -- 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/1627078 Title: ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I'm trying to implement a "page indicator" to be shown when the user scrolls a Flickable using a UITK ScrollBar. The idea is to mimic a feature available in Adobe Reader for Android. i.e. http://imgur.com/a/OzjYG In order to do this, I have to access the "draggingThumb" property of the style instance of a UITK ScrollBar, which is meant to be private. Item { [...] visible: scrollView.verticalScrollbar.__styleInstance.draggingThumb } What it could be useful is to expose this property directly in the ScrollBar. Using the Flickable properties for this purpose would be a bit complicated, since it wouldn't be desiderable to see such overlay during an "ordinary" touch/flick event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1627078/+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 995074] Re: Can't print from Evince/"Document Viewer" HP 4215
*** This bug is a duplicate of bug 1023717 *** https://bugs.launchpad.net/bugs/1023717 ** Also affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/995074 Title: Can't print from Evince/"Document Viewer" HP 4215 Status in cups package in Ubuntu: Confirmed Status in evince package in Ubuntu: New Bug description: Just upgraded to 12.04 from 10.04 a few days ago. Am able to print test pages, web forms, and Libre Office documents but when I try to print a .pdf opened with Evince, the document goes into the print queue and stays there with a status of "stopped." The only thing that I can do at that point is to cancel the document, the only other options available are "reprint" which puts it right back in the same state, and "retrieve" which saves the file to disk. I can't say with 100% certainty that I was able to print .pdfs from 10.04 but I can't imagine that I was using that distro for several years without having the occasion to do so at least once. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evince 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sat May 5 09:10:53 2012 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to precise on 2012-04-28 (6 days ago) XsessionErrors: gnome-session[2710]: WARNING: Could not launch application 'gdu-notification-daemon.desktop': Unable to start application: Failed to execute child process "/usr/lib/gnome-disk-utility/gdu-notification-daemon" (No such file or directory) (gnome-settings-daemon:2782): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed (gnome-settings-daemon:2782): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed (gnome-settings-daemon:2782): power-plugin-WARNING **: failed to show notification: GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded: Exceeded maximum number of notifications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/995074/+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 1602737] Re: PCI RoCE Interface could not be renamed from default name with link file
** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- 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/1602737 Title: PCI RoCE Interface could not be renamed from default name with link file Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in linux source package in Xenial: Fix Released Status in systemd source package in Xenial: New Status in linux source package in Yakkety: Fix Released Status in systemd source package in Yakkety: New Bug description: == Comment: #0 - Helmut Grauer- 2016-07-13 09:05:27 == Try to rename PCI Roce Interface with .link file root@s35lp02:/etc/systemd/network# cat 10-net.link [Match] Path=pci-:00:00.0* MACAddress=82:01:14:07:85:70 [Link] Name=hug0 root@s35lp02:/etc/systemd/network# do a reboot and journalctl show old interface name for RoCE PCI Interface Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: frag:0 - size:1522 prefix:0 stride:1536 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing port Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: frag:0 - size:1522 prefix:0 stride:1536 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing port Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from eth0 Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from eth1 Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed from eth3 Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from eth2 Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system using the ext4 subsystem Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with ordered data mode. Opts: (null) udevadm test show the following output oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0 calling: test version 229 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 229 file size: 6841701 bytes header size 80 bytes strings1755245 bytes nodes 5086376 bytes Load module index timestamp of '/etc/systemd/network' changed Skipping overridden file: /usr/lib/systemd/network/99-default.link. Skipping overridden file: /usr/lib/systemd/network/10-net.link. Skipping overridden file: /lib/systemd/network/99-default.link. Skipping overridden file: /lib/systemd/network/10-net.link. Parsed configuration file /etc/systemd/network/99-default.link Parsed configuration file /lib/systemd/network/90-mac-for-usb.link Parsed configuration file /etc/systemd/network/11-net.link Parsed configuration file /etc/systemd/network/10-net.link Created link configuration context. timestamp of '/etc/udev/rules.d' changed Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules Reading rules file: /lib/udev/rules.d/40-z90crypt.rules Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules Reading rules file: /lib/udev/rules.d/50-firmware.rules Reading rules file: /lib/udev/rules.d/50-udev-default.rules Reading rules file: /lib/udev/rules.d/55-dm.rules Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules Reading rules file: /lib/udev/rules.d/56-lvm.rules Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules Reading rules file: /lib/udev/rules.d/59-dasd.rules Reading rules file: /lib/udev/rules.d/60-block.rules Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules Reading rules file: /lib/udev/rules.d/60-crda.rules Reading rules file: /lib/udev/rules.d/60-drm.rules Reading rules file: /lib/udev/rules.d/60-evdev.rules Reading
[Touch-packages] [Bug 1627078] [NEW] ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property
Public bug reported: I'm trying to implement a "page indicator" to be shown when the user scrolls a Flickable using a UITK ScrollBar. The idea is to mimic a feature available in Adobe Reader for Android. i.e. http://imgur.com/a/OzjYG In order to do this, I have to access the "draggingThumb" property of the style instance of a UITK ScrollBar, which is meant to be private. Item { [...] visible: scrollView.verticalScrollbar.__styleInstance.draggingThumb } What it could be useful is to expose this property directly in the ScrollBar. Using the Flickable properties for this purpose would be a bit complicated, since it wouldn't be desiderable to see such overlay during an "ordinary" touch/flick event. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1627078 Title: ScrollBars and ScrollView - add 'isDragged' or 'isScrolling' property Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I'm trying to implement a "page indicator" to be shown when the user scrolls a Flickable using a UITK ScrollBar. The idea is to mimic a feature available in Adobe Reader for Android. i.e. http://imgur.com/a/OzjYG In order to do this, I have to access the "draggingThumb" property of the style instance of a UITK ScrollBar, which is meant to be private. Item { [...] visible: scrollView.verticalScrollbar.__styleInstance.draggingThumb } What it could be useful is to expose this property directly in the ScrollBar. Using the Flickable properties for this purpose would be a bit complicated, since it wouldn't be desiderable to see such overlay during an "ordinary" touch/flick event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1627078/+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 1578698] Re: Crash on waking from suspend after upgrading to 16.04
The same thing is happening on my laptop too with 16.04.1 : 470 G0/1948, BIOS 68IRF Ver. F.27 02/12/2014 After resume, the GPU seems to hang and needs a reset: [10210.040529] [drm] stuck on render ring [10210.041074] [drm] GPU HANG: ecode 7:0:0x85ffbff8, in chromium-browse [19248], reason: Ring hung, action: reset [10210.041076] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [10210.041076] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [10210.041077] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [10210.041078] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [10210.041078] [drm] GPU crash dump saved to /sys/class/drm/card0/error [10210.041087] [ cut here ] [10210.041140] WARNING: CPU: 1 PID: 23298 at /build/linux-R0TiM8/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11309 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]() [10210.041142] WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips)) [10210.041143] Modules linked in: [10210.041144] ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_tcpudp ip6t_REJECT nf_reject_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 xt_conntrack ip6table_mangle ip6table_filter ip6_tables iptable_mangle pci_stub iptable_nat nf_conntrack_ipv4 vboxpci(OE) nf_defrag_ipv4 vboxnetadp(OE) nf_nat_ipv4 vboxnetflt(OE) nf_nat nf_conntrack iptable_filter vboxdrv(OE) ip_tables x_tables ctr ccm rfcomm bnep binfmt_misc arc4 snd_hda_codec_hdmi hp_wmi sparse_keymap snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core uvcvideo snd_hwdep videobuf2_vmalloc snd_pcm videobuf2_memops videobuf2_v4l2 videobuf2_core intel_rapl btusb v4l2_common btrtl x86_pkg_temp_thermal btbcm snd_seq_midi intel_powerclamp btintel iwlmvm coretemp bluetooth snd_seq_midi_event videodev media mac80211 snd_rawmidi kvm_intel [10210.041192] iwlwifi kvm snd_seq cfg80211 irqbypass snd_seq_device snd_timer joydev input_leds snd hp_accel lpc_ich serio_raw soundcore mei_me lis3lv02d input_polldev mei shpchp 8250_fintek hp_wireless mac_hid parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq jitterentropy_rng drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul i915 aesni_intel aes_x86_64 i2c_algo_bit lrw psmouse drm_kms_helper gf128mul glue_helper syscopyarea ablk_helper sysfillrect cryptd sysimgblt fb_sys_fops ahci drm r8169 libahci mii wmi video fjes The details of the video card: 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) DeviceName: 96 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 31 Memory at c000 (64-bit, non-prefetchable) [size=4M] Memory at b000 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at [disabled] Capabilities: Kernel driver in use: i915 Kernel modules: i915 -- 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/1578698 Title: Crash on waking from suspend after upgrading to 16.04 Status in xorg package in Ubuntu: Expired Bug description: Since upgrading to Ubuntu 16.04 and compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 I have started to see frequent, apparently random crashes when resuming from suspend. I don't have any definitive proof that it is compiz vs e.g. the Unity plugin, as I don't even get one of the usual crash dialogues when this happens. I just see the screen freeze up, aside from the cursor, and then after 10-15 seconds it seems to reload compiz and I am able to actually enter my password to login. I'm sorry this report isn't of more help, I will continue investigating to see if I can narrow it down at all. Edit: I'm using the Intel graphics driver, and spotted the following in dmesg: [drm] stuck on render ring [drm] GPU HANG: ecode 7:0:0x85d8, in compiz [16077], reason: Ring hung, action: reset drm/i915: Resetting chip after gpu hang [drm] stuck on render ring [drm] GPU HANG: ecode 7:0:0x85d8, in compiz [16077], reason: Ring hung, action: reset [ cut here ] WARNING: CPU: 6 PID: 804 at /build/linux-Ay7j_C/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:11287 intel_mmio_flip_work_func+0x38e/0x3d0 [i915]() WARN_ON(__i915_wait_request(mmio_flip->req, mmio_flip->crtc->reset_counter, false, NULL, _flip->i915->rps.mmioflips)) Modules linked in: vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) hidp cmac drbg ansi_cprng ctr ccm pci_stub rfcomm bnep zram lz4_compress arc4
[Touch-packages] [Bug 1626180] Re: Today Scope not clickable after OTA-13
Nice work Vladimir! Based on this, I will have removed Today scope from this bug and made other top-level bug modifications. Please, try installing the "Desktop Apps" scope as describe here: https://bugs.launchpad.net/libertine-scope/+bug/1617545/comments/9 Please let me know the result here. Cheers ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Summary changed: - Today Scope not clickable after OTA-13 + Desktop Apps scope hangs unity-dash ** Description changed: - Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became - not clickable. I can't turn (swipe to) to programs and to other scopes. - And Today Scope isn't resizeable now -- this scope does not fit screen - in album mode. But traditional Ubuntu left panel is working and - reachable, and I can run Terminal, Contacts, Browser, etc. + Desktop Apps scope hangs unity8-dash + + == Previous description + Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. ** Tags removed: ota-13 scope today ** Changed in: today-scope Status: New => Invalid ** Summary changed: - Desktop Apps scope hangs unity-dash + Desktop Apps scope hangs unity8-dash -- 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/1626180 Title: Desktop Apps scope hangs unity8-dash Status in Canonical System Image: New Status in Today Scope: Invalid Status in unity8 package in Ubuntu: New Bug description: Desktop Apps scope hangs unity8-dash == Previous description Just after installing OTA-13 (BQ Aquaris M10 FHD) "Today Scope" became not clickable. I can't turn (swipe to) to programs and to other scopes. And Today Scope isn't resizeable now -- this scope does not fit screen in album mode. But traditional Ubuntu left panel is working and reachable, and I can run Terminal, Contacts, Browser, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626180/+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 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address
And yakkety has ifupdown 0.8.13 which contains the fix already. ** Tags added: sts-sru -- 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/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot assign requested address Status in ifupdown: New Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Precise: Invalid Status in ifupdown source package in Trusty: Invalid Status in ifupdown source package in Xenial: In Progress Bug description: (Original bug description follows SRU info) [Description] When using dhcpv6 configured via ifupdown, the interface's dhcp client fails to start at boot with the error: Can't bind to dhcp address: Cannot assign requested address This is because ifupdown doesn't wait, after bringing the interface up, for it to complete its link-local Duplicate Address Detection (DAD), and the dhcp client can't bind to the link-local address because it's still in "tentative" state (until DAD completes). This is fixed upstream in debian ifupdown in version 0.8.11 by adding '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the script was only waiting for the link-local address to appear, now it waits until the link-local address appears and is not in 'tentative' state. [Test Case] Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0 inet6 dhcp) and reboot. It will fail to get a dhcp address during boot. [Regression] None -- original bug description -- After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 address via DHCPv6. The root cause is that dhclient is exiting with the following message: - Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. - The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04 version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10 version) allows me to obtain an address. NetworkManager is the one launching dhclient. The two invocations (one for IPv4 and one for IPv6) are: dhclient_start(): running: /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient6-eth0.pid -lf /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b- 563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient6-eth0.conf eth0 I do not see anything suspicious with the way both dhclients are invoked. Given that a downgrade allows me to obtain an IPv6 address I think this might be a bug in the ISC DHCP client rather than in NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1447715/+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 1447715] Re: dhclient -6: Can't bind to dhcp address: Cannot assign requested address
I tested on precise and trusty, and this problem doesn't appear there, so only xenial requires the ifupdown SRU. ** Changed in: ifupdown (Ubuntu Trusty) Status: In Progress => Invalid -- 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/1447715 Title: dhclient -6: Can't bind to dhcp address: Cannot assign requested address Status in ifupdown: New Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Precise: Invalid Status in ifupdown source package in Trusty: Invalid Status in ifupdown source package in Xenial: In Progress Bug description: (Original bug description follows SRU info) [Description] When using dhcpv6 configured via ifupdown, the interface's dhcp client fails to start at boot with the error: Can't bind to dhcp address: Cannot assign requested address This is because ifupdown doesn't wait, after bringing the interface up, for it to complete its link-local Duplicate Address Detection (DAD), and the dhcp client can't bind to the link-local address because it's still in "tentative" state (until DAD completes). This is fixed upstream in debian ifupdown in version 0.8.11 by adding '-tentative' to the /lib/ifupdown/wait-for-ll6.sh script; before the script was only waiting for the link-local address to appear, now it waits until the link-local address appears and is not in 'tentative' state. [Test Case] Configure an interface, using ifupdown, with dhcpv6 (e.g. iface eth0 inet6 dhcp) and reboot. It will fail to get a dhcp address during boot. [Regression] None -- original bug description -- After upgrading to Ubuntu 15.04 my computer is unable to obtain an IPv6 address via DHCPv6. The root cause is that dhclient is exiting with the following message: - Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. - The problem seems to exist in isc-dhcp-client 4.3.1-5ubuntu2 (15.04 version) because downgrading to isc-dhcp-client 4.2.4-7ubuntu14 (14.10 version) allows me to obtain an address. NetworkManager is the one launching dhclient. The two invocations (one for IPv4 and one for IPv6) are: dhclient_start(): running: /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient-eth0.pid -lf /var/lib/NetworkManager /dhclient-c0a3dfde-5c0b-4cef-9c3b-563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient-eth0.conf eth0 dhclient_start(): running: /sbin/dhclient -d -q -6 -N -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d /network-manager.dhclient6-eth0.pid -lf /var/lib/NetworkManager/dhclient6-c0a3dfde-5c0b-4cef-9c3b- 563cfb1fb9d2-eth0.lease -cf /var/lib/NetworkManager/dhclient6-eth0.conf eth0 I do not see anything suspicious with the way both dhclients are invoked. Given that a downgrade allows me to obtain an IPv6 address I think this might be a bug in the ISC DHCP client rather than in NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/ifupdown/+bug/1447715/+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 1602737] Re: PCI RoCE Interface could not be renamed from default name with link file
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Released -- 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/1602737 Title: PCI RoCE Interface could not be renamed from default name with link file Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: New Status in linux source package in Xenial: Fix Released Status in systemd source package in Xenial: New Status in linux source package in Yakkety: Fix Released Status in systemd source package in Yakkety: New Bug description: == Comment: #0 - Helmut Grauer- 2016-07-13 09:05:27 == Try to rename PCI Roce Interface with .link file root@s35lp02:/etc/systemd/network# cat 10-net.link [Match] Path=pci-:00:00.0* MACAddress=82:01:14:07:85:70 [Link] Name=hug0 root@s35lp02:/etc/systemd/network# do a reboot and journalctl show old interface name for RoCE PCI Interface Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:1 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 32 TX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Using 4 RX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: frag:0 - size:1522 prefix:0 stride:1536 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 1: Initializing port Jul 13 14:39:40 s35lp02 kernel: mlx4_en 0001:00:00.0: Activating port:2 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 32 TX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Using 4 RX rings Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: frag:0 - size:1522 prefix:0 stride:1536 Jul 13 14:39:40 s35lp02 kernel: mlx4_en: 0001:00:00.0: Port 2: Initializing port Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0: renamed from eth0 Jul 13 14:39:40 s35lp02 kernel: mlx4_core :00:00.0 enp0s0d1: renamed from eth1 Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0d1: renamed from eth3 Jul 13 14:39:40 s35lp02 kernel: mlx4_core 0001:00:00.0 enP1p0s0: renamed from eth2 Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounting ext3 file system using the ext4 subsystem Jul 13 14:39:40 s35lp02 kernel: EXT4-fs (dasda1): mounted filesystem with ordered data mode. Opts: (null) udevadm test show the following output oot@s35lp02:/etc/systemd/network# udevadm test /class/net/enp0s0 calling: test version 229 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 229 file size: 6841701 bytes header size 80 bytes strings1755245 bytes nodes 5086376 bytes Load module index timestamp of '/etc/systemd/network' changed Skipping overridden file: /usr/lib/systemd/network/99-default.link. Skipping overridden file: /usr/lib/systemd/network/10-net.link. Skipping overridden file: /lib/systemd/network/99-default.link. Skipping overridden file: /lib/systemd/network/10-net.link. Parsed configuration file /etc/systemd/network/99-default.link Parsed configuration file /lib/systemd/network/90-mac-for-usb.link Parsed configuration file /etc/systemd/network/11-net.link Parsed configuration file /etc/systemd/network/10-net.link Created link configuration context. timestamp of '/etc/udev/rules.d' changed Reading rules file: /lib/udev/rules.d/40-vm-hotadd.rules Reading rules file: /lib/udev/rules.d/40-z90crypt.rules Reading rules file: /etc/udev/rules.d/41-cio-ignore.rules Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af06.rules Reading rules file: /etc/udev/rules.d/41-dasd-eckd-0.0.af07.rules Reading rules file: /etc/udev/rules.d/41-generic-ccw-0.0.0009.rules Reading rules file: /etc/udev/rules.d/41-qeth-0.0.b100.rules Reading rules file: /etc/udev/rules.d/41-qeth-0.0.f500.rules Reading rules file: /lib/udev/rules.d/50-firmware.rules Reading rules file: /lib/udev/rules.d/50-udev-default.rules Reading rules file: /lib/udev/rules.d/55-dm.rules Reading rules file: /lib/udev/rules.d/55-scsi-sg3_id.rules Reading rules file: /lib/udev/rules.d/56-dm-mpath-lvm.rules Reading rules file: /lib/udev/rules.d/56-lvm.rules Reading rules file: /lib/udev/rules.d/58-scsi-sg3_symlink.rules Reading rules file: /lib/udev/rules.d/59-dasd.rules Reading rules file: /lib/udev/rules.d/60-block.rules Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules Reading rules file: /lib/udev/rules.d/60-crda.rules Reading rules file: /lib/udev/rules.d/60-drm.rules Reading rules file: /lib/udev/rules.d/60-evdev.rules Reading rules
[Touch-packages] [Bug 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI
What fails is most likely the call to self.drag_bottom_edge_upwards(0.75) in open_tabs_view(). -- 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/1627056 Title: 48 webbrowser_app autopilot test failures on krillin in CI Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+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 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI
46 of the failures share this common stack trace: File "/usr/lib/python3/dist-packages/webbrowser_app/tests/__init__.py", line 138, in open_tabs_view tabs_view = self.main_window.get_tabs_view() File "/usr/lib/python3/dist-packages/webbrowser_app/emulators/browser.py", line 129, in get_tabs_view return self.wait_select_single(TabsList, visible=True) File "/usr/lib/python3/dist-packages/autopilot/introspection/dbus.py", line 369, in wait_select_single raise StateNotFoundError(type_name, **kwargs) autopilot.exceptions.StateNotFoundError: Object not found with name '' and properties {'visible': True}. -- 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/1627056 Title: 48 webbrowser_app autopilot test failures on krillin in CI Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+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 1626883] Re: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault
This bug was fixed in the package openssl - 1.0.2g-1ubuntu4.5 --- openssl (1.0.2g-1ubuntu4.5) xenial-security; urgency=medium * SECURITY REGRESSION: incomplete fix for CVE-2016-2182 (LP: #1626883) - debian/patches/CVE-2016-2182-2.patch: fix off-by-one in overflow check in crypto/bn/bn_print.c. -- Marc DeslauriersFri, 23 Sep 2016 08:00:13 -0400 ** Changed in: openssl (Ubuntu Xenial) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1626883 Title: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Precise: Fix Released Status in openssl source package in Trusty: Fix Released Status in openssl source package in Xenial: Fix Released Status in openssl source package in Yakkety: Confirmed Bug description: Last night unattended-upgrades upgraded the openssl packages (libssl1.0.0, libssl-dev, openssl) from version 1.0.2g-1ubuntu4.1 to version 1.0.2g-1ubuntu4.4 on a CI build server. Then everything that used PHP to connect to a HTTPS site started crashing when verifying the server cert. Like this: ``` jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$ DATABASE_DATABASE=wordpressmastere2e catchsegv wp plugin install --force --activate wp-cfm Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; WP_Import has a deprecated constructor in /var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop /vagrant/wordpress/wp-content/plugins/wordpress-importer/wordpress-importer.php on line 38 Notice: Undefined offset: 4 in phar:///usr/local/bin/wp/php/WP_CLI/DocParser.php on line 124 Segmentation fault (core dumped) *** Segmentation fault Register dump: RAX: RBX: 0001 RCX: RDX: 000c RSI: 55665071af59 RDI: RBP: 556650a49e4e R8 : 556652364720 R9 : R10: R11: 7fdb3c081730 R12: 55665071af59 R13: 000c R14: R15: 7fdb39418cf0 RSP: 7ffc4bad7a08 RIP: 7fdb3bf77d16 EFLAGS: 00010293 CS: 0033 FS: GS: Trap: 000e Error: 0004 OldMask: CR2: FPUCW: 027f FPUSW: TAG: RIP: RDP: ST(0) ST(1) ST(2) ST(3) ST(4) ST(5) ST(6) ST(7) mxcsr: 1fa0 XMM0: XMM1: XMM2: XMM3: XMM4: XMM5: XMM6: XMM7: XMM8: XMM9: XMM10: XMM11: XMM12: XMM13: XMM14: XMM15: Backtrace: /lib/x86_64-linux-gnu/libc.so.6(strlen+0x26)[0x7fdb3bf77d16] php(add_assoc_string_ex+0x32)[0x556650677b12] php(zif_openssl_x509_parse+0x17c)[0x5566505312ec] php(dtrace_execute_internal+0x2a)[0x556650664b3a] php(+0x2e37e0)[0x5566506f97e0] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b]
[Touch-packages] [Bug 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI
** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- 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/1627056 Title: 48 webbrowser_app autopilot test failures on krillin in CI Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+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 1627056] Re: 48 webbrowser_app autopilot test failures on krillin in CI
On the webbrowser-app side, 8 branches landed on the 25th of August (https://bazaar.launchpad.net/~phablet-team/webbrowser- app/trunk/revision/1527). None of these branches immediately stand out as potential culprits. On the system-apps jenkins instance side (https://code.launchpad.net /~system-apps-team/system-apps-jenkins/+git/system-apps- jenkins/+ref/master), nothing happened in this time frame. -- 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/1627056 Title: 48 webbrowser_app autopilot test failures on krillin in CI Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+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 1514860] Re: OptionSelector does not work with keyboard
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1514860 Title: OptionSelector does not work with keyboard Status in Canonical System Image: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: OptionSelector does not fully work with only keyboard. There is no way to select a option on OptionSelector using only the keyboard. Pressing the arrows does not navigate on the options. And it does not have any visual feedback that it contains focus. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514860/+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 1627056] [NEW] 48 webbrowser_app autopilot test failures on krillin in CI
Public bug reported: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "autopkgtest-log-308.txt" https://bugs.launchpad.net/bugs/1627056/+attachment/4747112/+files/autopkgtest-log-308.txt -- 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/1627056 Title: 48 webbrowser_app autopilot test failures on krillin in CI Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The autopilot tests for webbrowser_app have been failing in CI (system-apps jenkins instance) for about a month. Before that they reliably passed. They are being run on a krillin device that is being flashed anew for every single run. The device hasn’t changed. The last known successful run was on August 10: https://jenkins.canonical.com/system-apps/job/test-0-autopkgtest/243/. The next run on a webbrowser-app branch didn’t happen until August 27, and it failed: https://jenkins.canonical.com/system- apps/job/test-0-autopkgtest/308/. Something happened in between those two dates that broke the tests. It might be something in the infrastructure rather than in webbrowser-app itself, given that the tests all pass when run on my krillin at home. I am attaching the full log for the first failing run on August 27. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1627056/+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 1626883] Re: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault
This bug was fixed in the package openssl - 1.0.1f-1ubuntu2.21 --- openssl (1.0.1f-1ubuntu2.21) trusty-security; urgency=medium * SECURITY REGRESSION: incomplete fix for CVE-2016-2182 (LP: #1626883) - debian/patches/CVE-2016-2182-2.patch: fix off-by-one in overflow check in crypto/bn/bn_print.c. -- Marc DeslauriersFri, 23 Sep 2016 07:57:00 -0400 ** Changed in: openssl (Ubuntu Trusty) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1626883 Title: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault Status in openssl package in Ubuntu: Confirmed Status in openssl source package in Precise: Fix Released Status in openssl source package in Trusty: Fix Released Status in openssl source package in Xenial: Confirmed Status in openssl source package in Yakkety: Confirmed Bug description: Last night unattended-upgrades upgraded the openssl packages (libssl1.0.0, libssl-dev, openssl) from version 1.0.2g-1ubuntu4.1 to version 1.0.2g-1ubuntu4.4 on a CI build server. Then everything that used PHP to connect to a HTTPS site started crashing when verifying the server cert. Like this: ``` jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$ DATABASE_DATABASE=wordpressmastere2e catchsegv wp plugin install --force --activate wp-cfm Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; WP_Import has a deprecated constructor in /var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop /vagrant/wordpress/wp-content/plugins/wordpress-importer/wordpress-importer.php on line 38 Notice: Undefined offset: 4 in phar:///usr/local/bin/wp/php/WP_CLI/DocParser.php on line 124 Segmentation fault (core dumped) *** Segmentation fault Register dump: RAX: RBX: 0001 RCX: RDX: 000c RSI: 55665071af59 RDI: RBP: 556650a49e4e R8 : 556652364720 R9 : R10: R11: 7fdb3c081730 R12: 55665071af59 R13: 000c R14: R15: 7fdb39418cf0 RSP: 7ffc4bad7a08 RIP: 7fdb3bf77d16 EFLAGS: 00010293 CS: 0033 FS: GS: Trap: 000e Error: 0004 OldMask: CR2: FPUCW: 027f FPUSW: TAG: RIP: RDP: ST(0) ST(1) ST(2) ST(3) ST(4) ST(5) ST(6) ST(7) mxcsr: 1fa0 XMM0: XMM1: XMM2: XMM3: XMM4: XMM5: XMM6: XMM7: XMM8: XMM9: XMM10: XMM11: XMM12: XMM13: XMM14: XMM15: Backtrace: /lib/x86_64-linux-gnu/libc.so.6(strlen+0x26)[0x7fdb3bf77d16] php(add_assoc_string_ex+0x32)[0x556650677b12] php(zif_openssl_x509_parse+0x17c)[0x5566505312ec] php(dtrace_execute_internal+0x2a)[0x556650664b3a] php(+0x2e37e0)[0x5566506f97e0] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b]
[Touch-packages] [Bug 1627053] [NEW] Need visual indication that video recording isn't capturing sound
Public bug reported: When recording a video and the camera-app doesn't have permission to access the microphone, no audio will be recorded. This is expected of course, but it would be useful to have a visual indication that this is happening, perhaps somewhere on the camera HUD. Without this visual indication the users has no way of knowing that the video won't have any sound, until they try to play back the video, and then it's too late. I have a few important videos without sound for this reason :/. Also, taking a step back, a more fundamental solution would be to follow Matthew's suggestion from bug 1554142: the camera-app shouldn't ask for a special microphone permission, "the ability to record video includes the ability to use the microphone". ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1627053 Title: Need visual indication that video recording isn't capturing sound Status in camera-app package in Ubuntu: New Bug description: When recording a video and the camera-app doesn't have permission to access the microphone, no audio will be recorded. This is expected of course, but it would be useful to have a visual indication that this is happening, perhaps somewhere on the camera HUD. Without this visual indication the users has no way of knowing that the video won't have any sound, until they try to play back the video, and then it's too late. I have a few important videos without sound for this reason :/. Also, taking a step back, a more fundamental solution would be to follow Matthew's suggestion from bug 1554142: the camera-app shouldn't ask for a special microphone permission, "the ability to record video includes the ability to use the microphone". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1627053/+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