[Touch-packages] [Bug 1620934] Re: [regression] Starting in Mesa 12.0.2, Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")
that wasn't the commit to revert, and Chris fixed the mir egl patch. I'll upload it in a bit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1620934 Title: [regression] Starting in Mesa 12.0.2, Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001") Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in QtMir: Confirmed Status in qtubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: nothing works, all apps, dash are just black windows - Ubuntu 16.10 + proposed (x86, and using Nvidia 8600GT with nouveau drivers) and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 3001" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572352] Re: Should remove TMPTIME from /etc/rcS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sysvinit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1572352 Title: Should remove TMPTIME from /etc/rcS Status in sysvinit package in Ubuntu: Confirmed Bug description: Now that systemd is cleaning /tmp (via /usr/lib/tmpfiles.d/tmp.conf), we should remove TMPTIME from the default /etc/rcS distribution. Leaving it in is just confusing as setting it to anything other than the default will still have no effect (since the files will now be cleaned by systemd rather than initscripts). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initscripts 2.88dsf-59.3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue Apr 19 20:19:06 2016 InstallationDate: Installed on 2012-10-07 (1290 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: sysvinit UpgradeStatus: Upgraded to xenial on 2016-04-09 (10 days ago) mtime.conffile..etc.default.rcS: 2015-05-26T01:09:17.227420 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1572352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
The problem is still the same with bluez version 5.37-0ubuntu5 -- 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/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: New Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
** Tags added: xenial ** Changed in: less (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: In Progress Bug description: When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://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 1616413] Re: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all
Ok, looking more closely, a card is found, but its only finding a line- out connectino. What physical connections do you have? Secondly, cyould you try and get a log from PulseAudio, as outlined here: https://wiki.ubuntu.com/PulseAudio/Log. Thanks. -- 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/1616413 Title: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: I am not getting any sound at all from my Dell Optiplex 7040 (running Ubuntu 16.04). The volume control icon is showing up next to the clock, and I am able to change the volume levels: but this has no effect. There is absolutely NO sound at all. In Settings -> Output, no devices are listed. Strangely enough, aplay -l results in: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3234 Analog [ALC3234 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 which indicates that the sound card is getting detected. I tried sudo alsa force-reload following which I rebooted. That doesn't fix the problem. I opened alsamixer: it is detecting the sound card perfectly and nothing is muted. Still, there is no audio. I then tried the following: sudo apt-get remove --purge alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio sudo alsa force-reload And still there is no audio. I'd be really grateful if you could look into this. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: suvam 4522 F pulseaudio suvam 5594 F alsamixer CurrentDesktop: Unity Date: Wed Aug 24 15:59:21 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-02-12 (193 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: suvam 4522 F pulseaudio suvam 5594 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-08-11 (13 days ago) dmi.bios.date: 12/04/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0HD5W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd12/04/2015:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7040 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1616413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
** Tags removed: verification-needed -- 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/1327412 Title: Delay during PXE Boot, IP-Config gives up Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: Fix Released Status in klibc source package in Wily: Won't Fix Status in klibc source package in Xenial: Fix Released Status in klibc package in Debian: New Bug description: [Impact] PXE booting users with live images or other minimal setups using klibc-utils. [Test case] Attempt to PXE boot using Ubuntu live images; see below for details. [Regression potential] This forces the yiaddr (client requested/current IP) to be set to 0 when sending DHCP messages; currently the messages are DHCPREQUEST and DHCPDISCOVER, which should typically only happen when there is no IP set on the device and it is otherwise unable to receive unicast (on account of not being configured). Should there be a need to send other messages which would require setting the yiaddr value to the current configured IP address, a naive change would break. The yiaddr variable would need to be adjusted to pull value from a new location, or initialized directly by the callers to dhcp_send() where the business logic would reside. --- Attempting to PXE boot both the 12.04.3 and 14.04 Live images. PXE boot works normally (PXE Menu, select desired image, image begins loading), then the boot process hangs while IP-Config attempts to get an IP address: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 2 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 3 secs - giving up These lines appear very quickly (5 seconds has NOT elapsed), after about a minute, we get this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 4 secs - giving up Some time later, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 6 secs - giving up Until finally, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 9 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.25.11.31 IP-Config: eth0 complete (dhcp from 172.25.10.20): (snip) While watching the DHCP server logs, Ubuntu is either not sending a DHCP Discover at times, or is not replying back with a DHCPRequest during these sessions, presumably ignoring an response from the DHCP server. From the initial booting of the system via PXE, to when Ubuntu finally shows the desktop, almost 12 minutes will have elapsed. I am seeing this same behavior on both 12.04.3 and 14.04. After finding a number of similar erros via Google and no real resolution, I have opened this bug. The system experiencing this issue has multiple ethernet interfaces (actual HW, not a VM), some Google found solutions suggest hard coding DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't acceptable as a system attempting to PXE boot may be using an alternate port for the network. I have found what looks to be a very similar bug filed for Debian, #584583, which also contains a patch for this issue (under Debian). I have no problems in PXE booting to various Windows, RedHat, Centos, or Fedora OSs. Ubuntu is the only Live OS that I'm attempting to boot at present. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Jun 6 20:22:09 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packa
[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/popoverRootItemArgument -- 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/1586013 Title: UITK Date picker broken on xenial Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6 (right). More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml [...] FAIL! : components::DatePicker13API::test_1_changeMinimumBeforeDate() Uncaught exception: Cannot call method hasOwnProperty of null Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622893] Re: NetworkManager takes very long to start, or times out, blocked on RNG
** Tags added: bootspeed regression-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1622893 Title: NetworkManager takes very long to start, or times out, blocked on RNG Status in Auto Package Testing: Fix Released Status in gnutls28 package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Bug description: Since a few days ago, NetworkManager.service takes awfully long to start, or even times out on failure and then gets restarted. This happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes due to the NM timeout. In the journal there is no actual logging from /usr/sbin/NetworkManager yet, just the start timeout. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu8 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 CurrentDesktop: i3 Date: Tue Sep 13 10:05:05 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback source-directory interfaces.d NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1622893/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Tags added: regression-update -- 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: New 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 1556785] Re: Blinking cursor is higher than the text (especially on the lock screen password entry)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1556785 Title: Blinking cursor is higher than the text (especially on the lock screen password entry) Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Unity8's blinking cursor is higher than the text. You can see this on desktop, both on the Unity8 login screen (password entry), and in System Settings "Search". In both cases the blue cursor appears to be the right size, but is several pixels higher than the text. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1556785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556785] Re: Blinking cursor is higher than the text (especially on the lock screen password entry)
It seems to me like this is merely the space left for accents - even if the text is "AEOU" the cursor (and selection) will be high enough to accomodate for "ÁÉÓÚ". If you use other characters, say "私は猫がすきです", the spacing will differ. -- 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/1556785 Title: Blinking cursor is higher than the text (especially on the lock screen password entry) Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Unity8's blinking cursor is higher than the text. You can see this on desktop, both on the Unity8 login screen (password entry), and in System Settings "Search". In both cases the blue cursor appears to be the right size, but is several pixels higher than the text. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1556785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556785] Re: Blinking cursor is higher than the text (especially on the lock screen password entry)
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => Incomplete -- 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/1556785 Title: Blinking cursor is higher than the text (especially on the lock screen password entry) Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Unity8's blinking cursor is higher than the text. You can see this on desktop, both on the Unity8 login screen (password entry), and in System Settings "Search". In both cases the blue cursor appears to be the right size, but is several pixels higher than the text. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1556785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623173] Re: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work
you already filed this ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1623173 Title: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work Status in xorg package in Ubuntu: Invalid Bug description: On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7, 4.6.7, 4.7.3 nor 4.8-rc6. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.8.0-040800rc6-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.44 Wed Aug 17 22:24:07 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 13 21:49:46 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-01 (104 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 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500] Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.300 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.300:bd05/09/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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Tue Sep 13 21:14:29 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) [drm] Failed to open DRM device for (null): -22 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SDC xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623172] Re: [Asus ZenBook UX501VW] Function keys to change keyboard brightness don't work
kernel bug ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1623172 Title: [Asus ZenBook UX501VW] Function keys to change keyboard brightness don't work Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7, 4.6.7, 4.7.3 nor 4.8-rc6. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.8.0-040800rc6-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.44 Wed Aug 17 22:24:07 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 13 21:44:06 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-01 (104 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 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500] Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.300 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.300:bd05/09/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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A 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: Tue Sep 13 21:14:29 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) [drm] Failed to open DRM device for (null): -22 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SDC xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1623172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582629] Re: mutt does not properly restore console colors on exit
Short summary of the ncurses bug: - when you call start_color() and then endwin() twice without calling use_default_colors() in the middle, endwin() resets the color to grey on black (and then clears to end of line, which leaves an ugly black bar in my gnome-terminal which uses a white background). Translated into muttrc: - when you shell out to external programs before configuring 'default' as a color name, you get this bug This leads to a workaround I've just tested: - edit /etc/Muttrc and insert color normal default default just above the last line, which is source /usr/lib/mutt/source-muttrc.d| -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1582629 Title: mutt does not properly restore console colors on exit Status in mutt package in Ubuntu: Confirmed Status in ncurses package in Ubuntu: New Status in mutt package in Debian: Fix Released Bug description: With release of Ubuntu 16.04 Debian Bug 803405 also hits Ubuntu. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803405 After quitting mutt (with q or x) mutt doesn't restore colors of the console properly, colors are mangled, at least when colors used in mutt are different from console colors. Tested in xfce4-terminal and gnome-terminal, maybe also other terminal or text console is affected. In addition to the information in the debian report this problem only occurs when a .muttrc (even when empty) exists for the user. Without a .muttrc file the behaviour of mutt on leaving is ok. I could confirm this on amd64 and armv7l, so it seems platform independent. Even if the bug is already known in Debian I repost this in Ubuntu just to have documented it also hits Ubuntu and to maybe have some fix for current mutt version (or to get an update to next version in this LTS release). xxx@xxx:~$ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 xxx@xxx:~$ apt-cache policy mutt mutt: Installiert: 1.5.24-1build1 Installationskandidat: 1.5.24-1build1 Versionstabelle: *** 1.5.24-1build1 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status xxx@xxx:~$ mutt -v Mutt 1.5.24 (2015-08-30) Copyright (C) 1996-2009 Michael R. Elkins und andere. Mutt übernimmt KEINERLEI GEWÄHRLEISTUNG. Starten Sie »mutt -vv«, um weitere Details darüber zu erfahren. Mutt ist freie Software. Sie können es unter bestimmten Bedingungen weitergeben; starten Sie »mutt -vv« für weitere Details. System: Linux 4.4.0-22-generic (x86_64) ncurses: ncurses 6.0.20160213 (compiled with 6.0) libidn: 1.32 (compiled with 1.32) hcache backend: tokyocabinet 1.4.48 Compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 5.3.1-9ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-5 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 5.3.1 20160216 (Ubuntu 5.3.1-9ubuntu1) Configure options: '--prefix=/usr' '--sysconfdir=/etc' '-- mandir=/usr/share/man' '--with-docdir=/usr/share/doc' '--with- mailpath=/var/mail' '--disable-dependency-tracking' '--enable- compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with- mixmaster' '--with-sasl' '--without-gdbm' '--without-bdb' '--without- qdbm' '--build' 'x86_64-linux-gnu' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format- security -Wall' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include
[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/pickerConditionalBindingTarget -- 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/1586013 Title: UITK Date picker broken on xenial Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6 (right). More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml [...] FAIL! : components::DatePicker13API::test_1_changeMinimumBeforeDate() Uncaught exception: Cannot call method hasOwnProperty of null Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624253] [NEW] UITK segfault in qmlplugindump on Qt 5.7
Public bug reported: --- make[4]: Leaving directory '/«BUILDDIR»/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4build1/src/Ubuntu/Components/Themes' Segmentation fault (core dumped) Makefile.ComponentModule:368: recipe for target '/«BUILDDIR»/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4build1/qml/Ubuntu/Components/plugins.qmltypes' failed make[4]: *** [/«BUILDDIR»/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4build1/qml/Ubuntu/Components/plugins.qmltypes] Error 139 --- (https://launchpadlibrarian.net/284597820/buildlog_ubuntu-yakkety-amd64 .ubuntu-ui-toolkit_1.3.2085+16.10.20160831.4build1_BUILDING.txt.gz) More information about Qt 5.7 at https://wiki.ubuntu.com/Touch/QtTesting ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.7 -- 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/1624253 Title: UITK segfault in qmlplugindump on Qt 5.7 Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: --- make[4]: Leaving directory '/«BUILDDIR»/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4build1/src/Ubuntu/Components/Themes' Segmentation fault (core dumped) Makefile.ComponentModule:368: recipe for target '/«BUILDDIR»/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4build1/qml/Ubuntu/Components/plugins.qmltypes' failed make[4]: *** [/«BUILDDIR»/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4build1/qml/Ubuntu/Components/plugins.qmltypes] Error 139 --- (https://launchpadlibrarian.net/284597820/buildlog_ubuntu-yakkety- amd64.ubuntu-ui- toolkit_1.3.2085+16.10.20160831.4build1_BUILDING.txt.gz) More information about Qt 5.7 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556785] Re: Blinking cursor is higher than the text (especially on the lock screen password entry)
No the cursor placement used to be obviously wrong. But I think this got fixed in the past month or so. Just waiting for some other Unity8 bugs to get fixed right now before I can retest. ** Changed in: canonical-devices-system-image Status: New => Incomplete -- 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/1556785 Title: Blinking cursor is higher than the text (especially on the lock screen password entry) Status in Canonical System Image: Incomplete Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Unity8's blinking cursor is higher than the text. You can see this on desktop, both on the Unity8 login screen (password entry), and in System Settings "Search". In both cases the blue cursor appears to be the right size, but is several pixels higher than the text. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1556785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624251] [NEW] gsettings-qt fails a test on Qt 5.7
Public bug reported: -- FAIL! : GSettings::test_reset() property count Actual (): 0 Expected (): 1 Loc: [/«BUILDDIR»/gsettings-qt-0.1+16.04.20160329/tests/tst_GSettings.qml(102)] (process:7207): GLib-GIO-WARNING **: g_settings_set_value: value for key 'test-enum' in schema 'com.canonical.gsettings.Test' is outside of valid range -- (https://launchpadlibrarian.net/284597323/buildlog_ubuntu-yakkety-amd64 .gsettings-qt_0.1+16.04.20160329-0ubuntu2~5_BUILDING.txt.gz) More information about Qt 5.7 at https://wiki.ubuntu.com/Touch/QtTesting ** Affects: gsettings-qt (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-qt in Ubuntu. https://bugs.launchpad.net/bugs/1624251 Title: gsettings-qt fails a test on Qt 5.7 Status in gsettings-qt package in Ubuntu: New Bug description: -- FAIL! : GSettings::test_reset() property count Actual (): 0 Expected (): 1 Loc: [/«BUILDDIR»/gsettings-qt-0.1+16.04.20160329/tests/tst_GSettings.qml(102)] (process:7207): GLib-GIO-WARNING **: g_settings_set_value: value for key 'test-enum' in schema 'com.canonical.gsettings.Test' is outside of valid range -- (https://launchpadlibrarian.net/284597323/buildlog_ubuntu-yakkety- amd64.gsettings-qt_0.1+16.04.20160329-0ubuntu2~5_BUILDING.txt.gz) More information about Qt 5.7 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1624251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586013] Re: UITK Date picker broken on xenial
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed => In Progress -- 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/1586013 Title: UITK Date picker broken on xenial Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Seems somewhat broken on both Qt 5.5 (left) and even more so on Qt 5.6 (right). More information on Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_datepicker.bug1567840.SEGFAULT.13.qml [...] FAIL! : components::DatePicker13API::test_1_changeMinimumBeforeDate() Uncaught exception: Cannot call method hasOwnProperty of null Loc:[./_build/qml/Ubuntu/Test/UbuntuTestCase13.qml(86)] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616107] Re: Kernel oops + system freeze on network-bridge shutdown
4.4 final shows the same oops. -- 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/1616107 Title: Kernel oops + system freeze on network-bridge shutdown Status in bridge-utils package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver. This error does not appear in Ubuntu 14.04 however. The error is reproducible whenever issuing the commands "shutdown", "service networking stop" or "brctl delbr br0". Manually creating the bridge and subsequently bringing it down results in the same error. /var/log/kern.log: [...] Aug 23 15:09:46 base1 kernel: [ 617.996677] device ens1f0 left promiscuous mode Aug 23 15:09:46 base1 kernel: [ 617.996699] br0: port 1(ens1f0) entered disabled state Aug 23 15:09:46 base1 kernel: [ 617.996730] BUG: unable to handle kernel NULL pointer dereference at 00d2 Aug 23 15:09:46 base1 kernel: [ 618.008306] IP: [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.020549] PGD 10374c0067 PUD 1033927067 PMD 0 Aug 23 15:09:46 base1 kernel: [ 618.032773] Oops: 0002 [#1] SMP Aug 23 15:09:46 base1 kernel: [ 618.044434] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio libcrc32c wmi fjes Aug 23 15:09:46 base1 kernel: [ 618.058563] CPU: 3 PID: 4049 Comm: brctl Not tainted 4.4.0-34-generic #53-Ubuntu Aug 23 15:09:46 base1 kernel: [ 618.058564] Hardware name: HP ProLiant DL120 Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016 Aug 23 15:09:46 base1 kernel: [ 618.058574] task: 881030676040 ti: 8810341e4000 task.ti: 8810341e4000 Aug 23 15:09:46 base1 kernel: [ 618.058576] RIP: 0010:[] [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058754] RSP: 0018:8810341e7d68 EFLAGS: 00010206 Aug 23 15:09:46 base1 kernel: [ 618.058769] RAX: RBX: RCX: Aug 23 15:09:46 base1 kernel: [ 618.058774] RDX: 881038470848 RSI: RDI: Aug 23 15:09:46 base1 kernel: [ 618.058775] RBP: 8810341e7d78 R08: R09: 8170d949 Aug 23 15:09:46 base1 kernel: [ 618.058776] R10: ead61340 R11: 8810329d2c00 R12: 00c0 Aug 23 15:09:46 base1 kernel: [ 618.058777] R13: 881030044000 R14: 881038470840 R15: Aug 23 15:09:46 base1 kernel: [ 618.058782] FS: 7f9aebc94700() GS:88107fcc() knlGS: Aug 23 15:09:46 base1 kernel: [ 618.058789] CS: 0010 DS: ES: CR0: 80050033 Aug 23 15:09:46 base1 kernel: [ 618.058790] CR2: 00d2 CR3: 00102fe83000 CR4: 001406e0 Aug 23 15:09:46 base1 kernel: [ 618.058802] Stack: Aug 23 15:09:46 base1 kernel: [ 618.058806] 8810356a4c00 8810341e7d98 c0489258 Aug 23 15:09:46 base1 kernel: [ 618.058822] 8810356a4c00 881038470840 8810341e7dc0 c0479bd8 Aug 23 15:09:46 base1 kernel: [ 618.058825] 881038470838 881038470848 88103847 8810341e7df8 Aug 23 15:09:46 base1 kernel: [ 618.058827] Call Trace: Aug 23 15:09:46 base1 kernel: [ 618.058863] [] nbp_vlan_flush+0x28/0x65 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058870] [] del_nbp+0x98/0x130 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058889] [] br_dev_delete+0x42/0xb0 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058895] [] br_del_bridge+0x4a/0x70 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058911] [] br_ioctl_deviceless_stub+0x153/0x230 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058984] [] ? security_file_alloc+0x33/0x50 Aug 23 15:09:46 base1 kernel: [ 618.059095] [] sock_ioctl+0x215/0x290 Aug 23 15:09:46 base1 kernel: [ 618.059121] [] do_vfs_ioctl+0x29f/0x490 Aug 23 15:09:46 base1 kernel: [ 618.059223] [] ? __do_page_fault+0x1b4/0x400 Aug 23 15:09:46 base1 kernel: [ 618.059264] [] ? fd_install+0x25/0x30 Aug 23 15:09:46 base1 kernel: [ 618.059266] [] SyS_ioctl+0x79/0x90 Aug 23 15:09:46 base1 kern
[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle
noticed this issue second time for last two days. 4.4.0-36-generic on i5-3340M (Intel® HD Graphics 4000). I didn't notice such issue previously (using xubuntu near two years) affected: terminal, system menu, eclipse not affected: chrome -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1434351 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: Expired Bug description: After a suspend/resume cycle, the screen comes up normally, but every time I move my mouse over a piece of text, button, widget, etc, the text vanishes and it's replaced by a plain rectangle. This does not affect xterm, but it does affect any GTK apps, firefox, etc. xfce-panel vanishes, although it's still responding to mouse-clicks. Newly opened menus are grey rectangles. The lines underlining menu hotkeys do NOT disappear. In the attached screenshot, you can clearly see which buttons I have waved the mouse over, and which I have not. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 19:51:37 2015 InstallationDate: Installed on 2015-03-05 (14 days ago) InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads
Since an update a couple of days ago, I have the same symptoms. I log in normally, the desktop appears (with icons) but nothing else. With right mouse click I can open a terminal, but windows have no borders and no menus. I removed my ~/.config/dconf and .config/compiz-1 and checked my .XAuthority permissions, but the problem subsists. My .xsession-errors only contain this: openConnection: connect: No such file or directory cannot connect to brltty at :0 I'm running Ubuntu 16.04.1 LTS HTH Fernando -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads Status in at-spi2-core package in Ubuntu: Triaged Bug description: Here is what I encounter 1. Boot computer, boot proceeds normally 2. Reach standard Ubuntu login screen, nothing seems to be amiss 3. Enter user name and password 4. Login disappears, just see the pink "Ubuntu 14.04" background The desktop never loads, not even after ~30 minutes. The launcher never appears, and the Desktop background never changes to the user- configured background. Other features: * Cursor works fine, it can be moved around the screen * No error messages pop up * ALT+F1 etc. can be used to switch to different TTYs; all files on the system appear to be intact * Print screen button works (I will upload a screen shot when I get a chance to copy it onto a USB drive) * Hitting power button pops up a window prompting the user to decide whether to shut down * CTRL+ALT+DELETE prompts the user to log out * Desktop does not load on any user accounts, including the guest account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619281] Re: Text.color can't be compared reliably
QColor stores RGB colour with 16 bits per channel, so "0.5" would
convert to 32768 (i.e. round(0.5 * 65535)), or 0x8000.
If you convert down to 8 bits per channel, you'll have 0x80. If you
convert that value back up to 16 bits per channel, you'll have 0x8080.
And finally, converting that to floating point gives you 0.50196.
So you'll probably need to adjust the tests to accept an error on the
order of 1/(2*255) in these values.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1619281
Title:
Text.color can't be compared reliably
Status in qtdeclarative-opensource-src package in Ubuntu:
Confirmed
Bug description:
Given the below QML:
import QtQuick 2.4
Text {
id: text
text: 'foobar'
color: foobar
property color foobar: Qt.rgba(0, 0, 0, 0.5)
property color foobar2: foobar
Component.onCompleted: {
console.log("text:", text.color, foobar, Qt.colorEqual(text.color,
foobar), text.color.a);
console.log("property:", foobar2, foobar, Qt.colorEqual(foobar2,
foobar), foobar2.a);
/*
qml: text: #8000 #8000 false 0.5019607843137255
qml: property: #8000 #8000 true 0.576295109483
*/
}
}
Seems that Text.color stores the colour with a different precision,
resulting in Qt.colorEqual() returning false.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libqt5quick5 5.6.1-4ubuntu3~xenialoverlay1~1 [origin:
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 1 14:40:27 2016
InstallationDate: Installed on 2016-05-06 (117 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1619281/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619281] Re: Text.color can't be compared reliably
Yeah, we did that, however I'm not sure I agree that we should need to.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1619281
Title:
Text.color can't be compared reliably
Status in qtdeclarative-opensource-src package in Ubuntu:
Confirmed
Bug description:
Given the below QML:
import QtQuick 2.4
Text {
id: text
text: 'foobar'
color: foobar
property color foobar: Qt.rgba(0, 0, 0, 0.5)
property color foobar2: foobar
Component.onCompleted: {
console.log("text:", text.color, foobar, Qt.colorEqual(text.color,
foobar), text.color.a);
console.log("property:", foobar2, foobar, Qt.colorEqual(foobar2,
foobar), foobar2.a);
/*
qml: text: #8000 #8000 false 0.5019607843137255
qml: property: #8000 #8000 true 0.576295109483
*/
}
}
Seems that Text.color stores the colour with a different precision,
resulting in Qt.colorEqual() returning false.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libqt5quick5 5.6.1-4ubuntu3~xenialoverlay1~1 [origin:
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 1 14:40:27 2016
InstallationDate: Installed on 2016-05-06 (117 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: qtdeclarative-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1619281/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555751] Re: Some apps require a restart after switching to/from Wifi/Cellular to reconnect to the network
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1555751 Title: Some apps require a restart after switching to/from Wifi/Cellular to reconnect to the network Status in Canonical System Image: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Some apps require a restart after switching to/from Wifi/Cellular to reconnect to the network What happened: 1) Ensure wifi is connected 2) Start Dekko 3) Refresh the inbox (notice the bouncing/loading bar stops eventually) 4) Disable wifi so you are on cellular 5) Refresh the inbox (notice the bouncing/loading bar stays continuously) Note - if after step 5 you restart the app it is fine - this only occurs on certain apps, specifically Dekko and Telegram are the ones that i've noticed so far. (Both of which i assume try to have a long running open network connection?) What I expected to happen: At step 5) for the connection to automatically change to using Cellular and not require an app restart $ system-image-cli -i current build number: 258 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-03-10 15:48:08 version version: 258 version ubuntu: 20160310 version device: 20160304.2 version custom: 20160201-5-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1555751/+subscriptions -- Mailing list: https://launchpad.net/~touch-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: New => Triaged -- 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: New Status in systemd package in Ubuntu: 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 file: /lib/udev/rules.d/60-gnupg.rules Reading rules file: /lib/udev/rules.d/60-persistent-alsa.rules Reading rules file: /lib/udev/rules.d/60-persistent-input.rules Reading rules file: /lib/udev/rules.d/60-persistent-storage-dm.rules Reading rules file
[Touch-packages] [Bug 1623901] Re: DUT does not locate. GPS is not working.
It seems this is suspected to be a duplicate of something long-standing ** Information type changed from Embargoed to Proprietary ** Project changed: barajas => avila ** Changed in: avila Milestone: 13 => None ** Information type changed from Proprietary to Public ** Project changed: avila => canonical-devices-system-image ** Also affects: krillin Importance: Undecided Status: New ** Also affects: vegetahd Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Milestone: None => 13 ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Also affects: location-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1623901 Title: DUT does not locate. GPS is not working. Status in Canonical System Image: Confirmed Status in krillin: New Status in vegetahd: New Status in location-service package in Ubuntu: New Bug description: Environment Product: VEGETA HD // KRILLIN FW version: UBUNTU 15.04 (r46) // UBUNTU (r66) HW version: MP Material: Description Steps to Reproduce: 1 - Activate Location detection 2 - Location Settings: Select “Using GPS, anonymised Wi-Fi and mobile network info. By selecting this option you accept the Nokia HERE terms and conditions. Actual Result: DUT does not locate. Neither Nearby nor HERE maps works because of this. Expected Result: DUT should locate as expected. Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623901/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Adding Linux as it seems (at least) to be related to the kernel and might need a bisect followed by a SRU for Xenial. Also once 4.6 is ready this should be verified and closed on Yakkety. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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: New Status in systemd package in Ubuntu: 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 file: /lib/udev/rules.d/60-gnupg.rules Reading rules fi
[Touch-packages] [Bug 1532358] Re: flaky autopkgtests cause migration issues
Let's continue to use this bug. It was technically incorrect for it to have been marked Fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1532358 Title: flaky autopkgtests cause migration issues Status in Canonical System Image: Fix Released Status in unity-scope-click package in Ubuntu: In Progress Status in unity-scopes-shell package in Ubuntu: In Progress Bug description: A few times recently when unity8 got into xenial-proposed for migration, unity-scope-click's autopkgtest failed on the first run, having passed on the next: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unity-scope-click/20160105_174239@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/u/unity-scope-click/20160108_185317@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-030/xenial/armhf/u/unity-scope-click/20160111_213558@/log.gz This delays migration until someone notices the failure and asks for a re-run, which usually passes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-scope-click 0.1.1+16.04.20151216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 9 00:29:21 2016 SourcePackage: unity-scope-click UpgradeStatus: Upgraded to xenial on 2015-10-28 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532358/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Comment bridged from LTC Bugzilla
--- Comment From barbara.mun...@de.ibm.com 2016-09-15 08:54 EDT--- -- 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: New Status in systemd package in Ubuntu: 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 file: /lib/udev/rules.d/60-gnupg.rules Reading rules file: /lib/udev/rules.d/60-persistent-alsa.rules Reading rules file: /lib/udev/rules.d/60-persistent-input.rules Reading rules file: /lib/udev/rules.d/60-persistent-storage-dm.rules Readi
[Touch-packages] [Bug 1424566] Re: sensible-editor is unexitable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sensible-utils (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sensible-utils in Ubuntu. https://bugs.launchpad.net/bugs/1424566 Title: sensible-editor is unexitable Status in sensible-utils package in Ubuntu: Confirmed Bug description: On fresh Ubuntu 14.04 (trusty) I start 'crontab -e' and a message is shown suggesting to Select an editor, but it is not possible to escape from that dialog without selecting an editor. ctrl+c is not working, q is not working. had to login from other ssh session and kill that with kill -9. It is rather unreasonable for any app to not process ctrl+c and not allow any way to exit it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1424566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624285] [NEW] /etc/init.d/dbus checks for dbus-daemon in wrong location
Public bug reported: dbus 1.6.18-0ubuntu4.3 for Ubuntu 14.04 installs a /etc/init.d/dbus script that checks for /usr/bin/dbus-daemon instead of /bin/dbus-daemon . Evidently this is not a critical failure as something still starts a system dbus on my system: 5 102 2423 1 1 0 41004 3304 - Ss ? 3:07 dbus-daemon --system --fork Who, I haven't figured out yet. The usual suspect systemd seems to be innocent here, because AFAICT it's supposed to start the daemon with a different set of options: ExecStart=//bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation This makes it a little bit tricky to figure out how to relaunch the system dbus daemon... ** Affects: dbus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1624285 Title: /etc/init.d/dbus checks for dbus-daemon in wrong location Status in dbus package in Ubuntu: New Bug description: dbus 1.6.18-0ubuntu4.3 for Ubuntu 14.04 installs a /etc/init.d/dbus script that checks for /usr/bin/dbus-daemon instead of /bin/dbus- daemon . Evidently this is not a critical failure as something still starts a system dbus on my system: 5 102 2423 1 1 0 41004 3304 - Ss ? 3:07 dbus-daemon --system --fork Who, I haven't figured out yet. The usual suspect systemd seems to be innocent here, because AFAICT it's supposed to start the daemon with a different set of options: ExecStart=//bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation This makes it a little bit tricky to figure out how to relaunch the system dbus daemon... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1624285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start
I got this after accidentally starting the bluetooth service while playing
audio via a2dp.
The hackaround from #4 worked for me.
--
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/1490349
Title:
15:10 and 16.04: bluetoothd reports "Not enough handles to register
service" at start
Status in bluez package in Ubuntu:
Confirmed
Bug description:
On 15:10 after the bluetooth service has been stopped and restarted it
is not possible to scan or connect to devices:
$ sudo systemctl start bluetooth
$ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print
$0}'
23:31:53 systemd[1]: Starting Bluetooth service...
23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33
23:31:53 systemd[1]: Started Bluetooth service.
23:31:53 bluetoothd[16647]: Starting SDP server
23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized
23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed"
characteristic
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Error adding Link Loss service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Current Time Service could not be registered
23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5)
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Not enough free handles to register service
23:31:53 bluetoothd[16647]: Sap driver initialization failed.
23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1)
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSource
23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440
path=/MediaEndpoint/A2DPSink
And
$ bluetoothctl
[NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
[NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
[NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624028] Re: lxc create using debian template fails on ppc64el
As following command works $ sudo lxc-create -n debian01 -t ubuntu Checking cache download in /var/cache/lxc/yakkety/rootfs-ppc64el ... Installing packages in template: apt-transport-https,ssh,vim,language-pack-en Downloading ubuntu yakkety minimal ... I: Retrieving InRelease I: Checking Release signature I: Valid Release signature (key id 790BC7277767219C42C86F933B4FE6ACC0B21F32) I: Retrieving Packages I: Validating Packages I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1624028 Title: lxc create using debian template fails on ppc64el Status in lxc package in Ubuntu: New Bug description: If I try to create a lxc container using the debian template, I get the following error on ppc64el arch: ➜ ~ sudo lxc-create -n debian01 -t debian debootstrap is /usr/sbin/debootstrap Checking cache download in /var/cache/lxc/debian/rootfs-jessie-ppc64le ... gpg: WARNING: unsafe ownership on configuration file `/home/ubuntu/.gnupg/gpg.conf' gpg: key 2B90D010: "Debian Archive Automatic Signing Key (8/jessie) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 Downloading debian minimal ... I: Retrieving InRelease I: Failed to retrieve InRelease I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010) E: Invalid Release file, no entry for main/binary-ppc64le/Packages Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for debian01 failed lxc-create: tools/lxc_create.c: main: 318 Error creating container debian01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1624028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624286] [NEW] External monitor reports no signal from HDMI port (Ubuntu 16.04)
Public bug reported: I think the phenomenon has already been reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574005 I have used "ubuntu-bug xorg" to report this bug. I hope this was the right choice and does provide you with the necessary information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri Sep 16 11:18:50 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-36-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5050] InstallationDate: Installed on 2016-08-31 (15 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20FW003PMZ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET63W (2.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW003PMZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET63W(2.03):bd03/15/2016:svnLENOVO:pn20FW003PMZ:pvrThinkPadT460p:rvnLENOVO:rn20FW003PMZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FW003PMZ dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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 16 09:45:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 38562 vendor MEI xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1624286 Title: External monitor reports no signal from HDMI port (Ubuntu 16.04) Status in xorg package in Ubuntu: New Bug description: I think the phenomenon has already been reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574005 I have used "ubuntu-bug xorg" to report this bug. I hope this was the right choice and does provide you with the necessary information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri Sep 16 11:18:50 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-36-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5050] InstallationDate: Installed on 2016-08-31 (15 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20FW003PMZ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgra
[Touch-packages] [Bug 1624028] Re: lxc create using debian template fails on ppc64el
I understand the debian image is not working properly (or doesn't exist). Using sudo lxc-create -n debian01 -t download we get the list of valid distro/release/arch available, and specifying: Distribution: debian Release: sid Architecture: ppc64el works on debian and on ubuntu !. Downloading the image index Downloading the rootfs Downloading the metadata The image cache is now ready Unpacking the rootfs --- You just created a Debian container (release=sid, arch=ppc64el, variant=default) To enable sshd, run: apt-get install openssh-server For security reason, container images ship without user accounts and without a root password. Use lxc-attach or chroot directly into the rootfs to set a root password or create user accounts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1624028 Title: lxc create using debian template fails on ppc64el Status in lxc package in Ubuntu: New Bug description: If I try to create a lxc container using the debian template, I get the following error on ppc64el arch: ➜ ~ sudo lxc-create -n debian01 -t debian debootstrap is /usr/sbin/debootstrap Checking cache download in /var/cache/lxc/debian/rootfs-jessie-ppc64le ... gpg: WARNING: unsafe ownership on configuration file `/home/ubuntu/.gnupg/gpg.conf' gpg: key 2B90D010: "Debian Archive Automatic Signing Key (8/jessie) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 Downloading debian minimal ... I: Retrieving InRelease I: Failed to retrieve InRelease I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010) E: Invalid Release file, no entry for main/binary-ppc64le/Packages Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for debian01 failed lxc-create: tools/lxc_create.c: main: 318 Error creating container debian01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1624028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622577] Re: tst_pagestack_deprecated_toolbar unit test warnings with qt56
I can take this bug later, but I un-assign myself for now so I won't prevent anyone else from working on it while I work on another Qt 5.6 bug. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: Tim Peeters (tpeeters) => (unassigned) -- 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/1622577 Title: tst_pagestack_deprecated_toolbar unit test warnings with qt56 Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: ubuntu@xenial1:~/dev/ubuntu-ui-toolkit/staging/tests/unit/components$ qmltestrunner -import ../../../qml/ -input tst_pagestack_deprecated_toolbar.qml qml: Page.tools is a deprecated property. Please use Page.head instead. qml: Page.tools is a deprecated property. Please use Page.head instead. qml: WARNING! Do not put Page/Tabs/PageStack inside another Page because that causes confusion which is the active page that sets the title and actions. qml: WARNING! Do not put Page/Tabs/PageStack inside another Page because that causes confusion which is the active page that sets the title and actions. * Start testing of qmltestrunner * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) PASS : qmltestrunner::PageStackAPI::initTestCase() PASS : qmltestrunner::PageStackAPI::test_active_bug1260116() QDEBUG : qmltestrunner::PageStackAPI::test_active_bug1260116() qml: Page.tools is a deprecated property. Please use Page.head instead. PASS : qmltestrunner::PageStackAPI::test_currentPage() PASS : qmltestrunner::PageStackAPI::test_depth() PASS : qmltestrunner::PageStackAPI::test_pop_to_tabs_bug1316736() PASS : qmltestrunner::PageStackAPI::test_tabs_inside_stack_bug1187850() PASS : qmltestrunner::PageStackAPI::test_title_bug1143345_bug1317902() PASS : qmltestrunner::PageStackAPI::test_tools_bug1126197() QDEBUG : qmltestrunner::PageStackAPI::test_tools_bug1126197() qml: Page.tools is a deprecated property. Please use Page.head instead. PASS : qmltestrunner::PageStackAPI::cleanupTestCase() QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null QWARN : qmltestrunner::UnknownTestFunc() file:///home/ubuntu/dev/ubuntu-ui-toolkit/staging/qml/Ubuntu/Components/Themes/Ambiance/1.2/TabBarStyle.qml:144: TypeError: Cannot read property 'count' of null Totals: 9 passed, 0 failed, 0 skipped, 0 blacklisted * Finished testing of qmltestrunner * To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1622577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623901] Re: DUT does not locate. GPS is not working.
This has been tested on a krillin. I get a location on initial boot after 2.5 minutes On subsequent reboot I get a location within 10 seconds of starting an app I also get a location in the today and nearby scopes. Accuracy is within 10 metres -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1623901 Title: DUT does not locate. GPS is not working. Status in Canonical System Image: Confirmed Status in krillin: New Status in vegetahd: New Status in location-service package in Ubuntu: New Bug description: Environment Product: VEGETA HD // KRILLIN FW version: UBUNTU 15.04 (r46) // UBUNTU (r66) HW version: MP Material: Description Steps to Reproduce: 1 - Activate Location detection 2 - Location Settings: Select “Using GPS, anonymised Wi-Fi and mobile network info. By selecting this option you accept the Nokia HERE terms and conditions. Actual Result: DUT does not locate. Neither Nearby nor HERE maps works because of this. Expected Result: DUT should locate as expected. Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624028] Re: lxc create using debian template fails on ppc64el
So my understanding is that '-t debian' parameter doesn't use the proper information like the DIST (it does mention jessie) $ sudo lxc-create -n debian03 -t debian debootstrap is /usr/sbin/debootstrap Checking cache download in /var/cache/lxc/debian/rootfs-jessie-ppc64le ... gpg: key 2B90D010: "Debian Archive Automatic Signing Key (8/jessie) " not changed ... even though manually, it works also on jessie $ sudo lxc-create -n debian03 -t download Setting up the GPG keyring Downloading the image index Distribution: debian Release: jessie Architecture: ppc64el Downloading the image index Downloading the rootfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1624028 Title: lxc create using debian template fails on ppc64el Status in lxc package in Ubuntu: New Bug description: If I try to create a lxc container using the debian template, I get the following error on ppc64el arch: ➜ ~ sudo lxc-create -n debian01 -t debian debootstrap is /usr/sbin/debootstrap Checking cache download in /var/cache/lxc/debian/rootfs-jessie-ppc64le ... gpg: WARNING: unsafe ownership on configuration file `/home/ubuntu/.gnupg/gpg.conf' gpg: key 2B90D010: "Debian Archive Automatic Signing Key (8/jessie) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 Downloading debian minimal ... I: Retrieving InRelease I: Failed to retrieve InRelease I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010) E: Invalid Release file, no entry for main/binary-ppc64le/Packages Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for debian01 failed lxc-create: tools/lxc_create.c: main: 318 Error creating container debian01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1624028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575313] Re: [Ubuntu Touch] Today Scope doesn't display current location status
I'd like to view in Today scope the place where I am. And may put manually coordinates or so of my place in order to see the weather correctly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1575313 Title: [Ubuntu Touch] Today Scope doesn't display current location status Status in Canonical System Image: Confirmed Status in Today Scope: Triaged Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: Today scope doesn't display a users current location. It is confusing for the weather, sunrise and sunset information as it is not clear what location that is for. It came to my attention as I'm on corporate VPN and Today-Scope is proving information based on IP address, which for me, is thousands of kilometers away. My Aquaris M10 tablet is also inside so is not picking up GPS signal. When I enable GPS only, Today-Scope still defaults back to IP address location data. Appears that there is no way to manually set location and when I set location in The Weather Channel app it defaults back to IP location when I switch back to Today-Scope. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1575313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624299] [NEW] SFTP protocol source cannot be found
Public bug reported:
Trying to play a video over SFTP fails, with Totem giving a pop-up:
"""
Required plugin could not be found
Videos requires to install plugins to support the following multimedia feature:
SFTP protocol source
"""
There does not seem to be any package that fits this description in the
apt repos. Trying from the command line with a local terminal I get the
following:
"""
/run/user/1000/gvfs/sftp:host=nas.local/Videos $ totem GOPR0210.MP4
** Message: Missing plugin: gstreamer|1.0|totem|SFTP protocol
source|urisource-sftp (SFTP protocol source)
/usr/lib/python3/dist-packages/sessioninstaller/core.py:47: PyGIWarning: Gst
was imported without specifying a version first. Use gi.require_version('Gst',
'1.0') before import to ensure that the right version gets loaded.
from gi.repository import Gst
/usr/lib/python3/dist-packages/sessioninstaller/core.py:48: PyGIWarning: Gtk
was imported without specifying a version first. Use gi.require_version('Gtk',
'3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
Falling back to package information
CRITICAL:Could not find any packages to operate on
"""
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.2-1~ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 16 19:28:29 2016
InstallationDate: Installed on 2016-06-07 (100 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gstreamer1.0 (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 gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1624299
Title:
SFTP protocol source cannot be found
Status in gstreamer1.0 package in Ubuntu:
New
Bug description:
Trying to play a video over SFTP fails, with Totem giving a pop-up:
"""
Required plugin could not be found
Videos requires to install plugins to support the following multimedia
feature: SFTP protocol source
"""
There does not seem to be any package that fits this description in
the apt repos. Trying from the command line with a local terminal I
get the following:
"""
/run/user/1000/gvfs/sftp:host=nas.local/Videos $ totem GOPR0210.MP4
** Message: Missing plugin: gstreamer|1.0|totem|SFTP protocol
source|urisource-sftp (SFTP protocol source)
/usr/lib/python3/dist-packages/sessioninstaller/core.py:47: PyGIWarning: Gst
was imported without specifying a version first. Use gi.require_version('Gst',
'1.0') before import to ensure that the right version gets loaded.
from gi.repository import Gst
/usr/lib/python3/dist-packages/sessioninstaller/core.py:48: PyGIWarning: Gtk
was imported without specifying a version first. Use gi.require_version('Gtk',
'3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
Falling back to package information
CRITICAL:Could not find any packages to operate on
"""
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.2-1~ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 16 19:28:29 2016
InstallationDate: Installed on 2016-06-07 (100 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1624299/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624286] Re: External monitor reports no signal from HDMI port (Ubuntu 16.04)
hdmi output is owned by the nvidia gpu, so you need to switch to it from nvidia-settings ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1624286 Title: External monitor reports no signal from HDMI port (Ubuntu 16.04) Status in xorg package in Ubuntu: Invalid Bug description: I think the phenomenon has already been reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574005 I have used "ubuntu-bug xorg" to report this bug. I hope this was the right choice and does provide you with the necessary information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Fri Sep 16 11:18:50 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-36-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-36-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5050] InstallationDate: Installed on 2016-08-31 (15 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20FW003PMZ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-36-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET63W (2.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW003PMZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET63W(2.03):bd03/15/2016:svnLENOVO:pn20FW003PMZ:pvrThinkPadT460p:rvnLENOVO:rn20FW003PMZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FW003PMZ dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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 16 09:45:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 38562 vendor MEI xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1624286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624028] Re: lxc create using debian template fails on ppc64el
$ diff -urN /usr/share/lxc/templates/lxc-debian /tmp/debian.template --- /usr/share/lxc/templates/lxc-debian 2016-09-16 12:02:34.047133580 +0200 +++ /tmp/debian.template2016-09-16 12:02:26.122949227 +0200 @@ -550,6 +550,8 @@ arch="amd64" elif [ "$arch" = "armv7l" ]; then arch="armhf" +elif [ "$arch" = "ppc64le" ]; then +arch="ppc64el" fi hostarch=$arch mainonly=1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1624028 Title: lxc create using debian template fails on ppc64el Status in lxc package in Ubuntu: New Bug description: If I try to create a lxc container using the debian template, I get the following error on ppc64el arch: ➜ ~ sudo lxc-create -n debian01 -t debian debootstrap is /usr/sbin/debootstrap Checking cache download in /var/cache/lxc/debian/rootfs-jessie-ppc64le ... gpg: WARNING: unsafe ownership on configuration file `/home/ubuntu/.gnupg/gpg.conf' gpg: key 2B90D010: "Debian Archive Automatic Signing Key (8/jessie) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 Downloading debian minimal ... I: Retrieving InRelease I: Failed to retrieve InRelease I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010) E: Invalid Release file, no entry for main/binary-ppc64le/Packages Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for debian01 failed lxc-create: tools/lxc_create.c: main: 318 Error creating container debian01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1624028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624028] Re: lxc create using debian template fails on ppc64el
The message E: Invalid Release file, no entry for main/binary- ppc64le/Packages is explanatory as it expect arch being ppc64el Fixed command: sudo lxc-create -n debian04 -t debian -- -a ppc64el For sid, you can do: sudo lxc-create -n debian04 -t debian -- -a ppc64el -r sid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1624028 Title: lxc create using debian template fails on ppc64el Status in lxc package in Ubuntu: New Bug description: If I try to create a lxc container using the debian template, I get the following error on ppc64el arch: ➜ ~ sudo lxc-create -n debian01 -t debian debootstrap is /usr/sbin/debootstrap Checking cache download in /var/cache/lxc/debian/rootfs-jessie-ppc64le ... gpg: WARNING: unsafe ownership on configuration file `/home/ubuntu/.gnupg/gpg.conf' gpg: key 2B90D010: "Debian Archive Automatic Signing Key (8/jessie) " not changed gpg: Total number processed: 1 gpg: unchanged: 1 Downloading debian minimal ... I: Retrieving InRelease I: Failed to retrieve InRelease I: Retrieving Release I: Retrieving Release.gpg I: Checking Release signature I: Valid Release signature (key id 126C0D24BD8A2942CC7DF8AC7638D0442B90D010) E: Invalid Release file, no entry for main/binary-ppc64le/Packages Failed to download the rootfs, aborting. Failed to download 'debian base' failed to install debian lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for debian01 failed lxc-create: tools/lxc_create.c: main: 318 Error creating container debian01 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1624028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624285] Re: /etc/init.d/dbus checks for dbus-daemon in wrong location
Looks good at first glance as it is: /bin is a place for most commonly used terminal commands, like ls, mount, rm, etc. /usr contains the majority of user utilities and applications, and partly replicates the root directory structure, containing for instance, among others, /usr/bin/ and /usr/lib. some years back it was like your thinking. https://help.ubuntu.com/community/LinuxFilesystemTreeOverview ** Changed in: dbus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1624285 Title: /etc/init.d/dbus checks for dbus-daemon in wrong location Status in dbus package in Ubuntu: Incomplete Bug description: dbus 1.6.18-0ubuntu4.3 for Ubuntu 14.04 installs a /etc/init.d/dbus script that checks for /usr/bin/dbus-daemon instead of /bin/dbus- daemon . Evidently this is not a critical failure as something still starts a system dbus on my system: 5 102 2423 1 1 0 41004 3304 - Ss ? 3:07 dbus-daemon --system --fork Who, I haven't figured out yet. The usual suspect systemd seems to be innocent here, because AFAICT it's supposed to start the daemon with a different set of options: ExecStart=//bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation This makes it a little bit tricky to figure out how to relaunch the system dbus daemon... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1624285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
The same "missing $unit" is in /usr/share/upstart/systemd- session/upstart/systemd-graphical-session.conf. ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New ** Changed in: upstart (Ubuntu) Status: New => In Progress ** Changed in: upstart (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- 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/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates Status in gnome-session package in Ubuntu: In Progress Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: In Progress Bug description: Sometimes on session start unity-gtk-module.service runs too late or something, and $GTK_MODULES does not include "unity". It is in "systemctl --user show-environment" but not in a terminal bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624314] [NEW] Failing DPR unit tests
Public bug reported: With Qt 5.6. FAIL! : tst_UCUnitsDPR2::dpGridUnitDefaultWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitDefaultWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::dpGridUnitEightWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitEightWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::dpGridUnitSixteenWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitSixteenWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::dpGridUnitTwentyWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitTenWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::dpGridUnitDefaultWithDPR3() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::guGridUnitDefaultWithDPR3() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::dpGridUnitSixteenWithDPR3() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::guGridUnitSixteenWithDPR3() Compared floats are not the same (fuzzy compare) See also https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/console ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: High Status: New ** Tags: qt5.6 ** Changed in: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided => High ** Tags added: qt5.6 -- 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/1624314 Title: Failing DPR unit tests Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: With Qt 5.6. FAIL! : tst_UCUnitsDPR2::dpGridUnitDefaultWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitDefaultWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::dpGridUnitEightWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitEightWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::dpGridUnitSixteenWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitSixteenWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::dpGridUnitTwentyWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitTenWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::dpGridUnitDefaultWithDPR3() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::guGridUnitDefaultWithDPR3() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::dpGridUnitSixteenWithDPR3() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::guGridUnitSixteenWithDPR3() Compared floats are not the same (fuzzy compare) See also https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit- ci-amd64-devel/1201/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624317] [NEW] systemd-resolved breaks VPN with split-horizon DNS
Public bug reported: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd package in Ubuntu: New Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624316] [NEW] Performance unit tests crash
*** This bug is a duplicate of bug 1570478 *** https://bugs.launchpad.net/bugs/1570478 Public bug reported: * Start testing of tst_Performance * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) [New Thread 0x7fffee924700 (LWP 10948)] PASS : tst_Performance::initTestCase() PASS : tst_Performance::clean() PASS : tst_Performance::benchmark_theming(new theming, subtheming enabled, no theme change) RESULT : tst_Performance::benchmark_theming():"new theming, subtheming enabled, no theme change": 0.21 msecs per iteration (total: 56, iterations: 256) PASS : tst_Performance::benchmark_theming(new theming, subtheming enabled, with theme change) RESULT : tst_Performance::benchmark_theming():"new theming, subtheming enabled, with theme change": 0.23 msecs per iteration (total: 59, iterations: 256) QWARN : tst_Performance::benchmark_theming(old theming, subtheming enabled) file:///tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/performance/StyledItemOldTheming.qml:58:17: QML StyledItem: Mixing of Ubuntu.Components module versions 1.2 and 1.3 detected! PASS : tst_Performance::benchmark_theming(old theming, subtheming enabled) RESULT : tst_Performance::benchmark_theming():"old theming, subtheming enabled": 0.23 msecs per iteration (total: 61, iterations: 256) PASS : tst_Performance::benchmark_theming(subtheming, no changes on themes) RESULT : tst_Performance::benchmark_theming():"subtheming, no changes on themes": 3.0 msecs per iteration (total: 98, iterations: 32) PASS : tst_Performance::benchmark_theming(subtheming, change mid item) RESULT : tst_Performance::benchmark_theming():"subtheming, change mid item": 3.0 msecs per iteration (total: 98, iterations: 32) pure virtual method called terminate called without an active exception Thread 1 "performance" received signal SIGABRT, Aborted. 0x75e00418 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #0 0x75e00418 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x75e0201a in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7622384d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x762216b6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x76221701 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x763f in __cxa_pure_virtual () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x76c2b54a in QQmlPropertyPrivate::setBinding(QQmlProperty const&, QQmlAbstractBinding*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fffed7233b4 in UCTheme::PaletteConfig::restorePalette (this=this@entry=0x5a4800) at uctheme.cpp:278 #8 0x7fffed6e42e3 in UCTheme::PaletteConfig::~PaletteConfig (this=0x5a4800, __in_chrg=) at uctheme_p.h:124 #9 UCTheme::~UCTheme (this=0x5a47e0, __in_chrg=) at uctheme_p.h:41 #10 0x7fffed6e4556 in QQmlPrivate::QQmlElement::~QQmlElement (this=0x5a47e0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:98 #11 QQmlPrivate::QQmlElement::~QQmlElement (this=0x5a47e0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:98 #12 0x767c3053 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x767cc094 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x77b800ed in QQuickItem::~QQuickItem() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7fffed6cdefd in UCStyledItemBase::~UCStyledItemBase (this=0x57a9e0, __in_chrg=) at ../../include/UbuntuToolkit/5.5.0/UbuntuToolkit/private/../../../../../src/UbuntuToolkit/ucstyleditembase_p.h:32 #16 QQmlPrivate::QQmlElement::~QQmlElement (this=0x57a9e0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:98 #17 QQmlPrivate::QQmlElement::~QQmlElement (this=0x57a9e0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:98 #18 0x0040286e in tst_Performance::benchmark_theming (this=) at tst_performance.cpp:97 #19 tst_Performance::qt_static_metacall (_o=0x7fffd1c0, _id=, _a=, _c=) at .moc/tst_performance.moc:100 #20 0x767a2eba in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x767a8861 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x77fc
[Touch-packages] [Bug 1624316] Re: Performance unit tests crash
*** This bug is a duplicate of bug 1570478 *** https://bugs.launchpad.net/bugs/1570478 ** This bug has been marked a duplicate of bug 1570478 Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6 -- 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/1624316 Title: Performance unit tests crash Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: * Start testing of tst_Performance * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) [New Thread 0x7fffee924700 (LWP 10948)] PASS : tst_Performance::initTestCase() PASS : tst_Performance::clean() PASS : tst_Performance::benchmark_theming(new theming, subtheming enabled, no theme change) RESULT : tst_Performance::benchmark_theming():"new theming, subtheming enabled, no theme change": 0.21 msecs per iteration (total: 56, iterations: 256) PASS : tst_Performance::benchmark_theming(new theming, subtheming enabled, with theme change) RESULT : tst_Performance::benchmark_theming():"new theming, subtheming enabled, with theme change": 0.23 msecs per iteration (total: 59, iterations: 256) QWARN : tst_Performance::benchmark_theming(old theming, subtheming enabled) file:///tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/performance/StyledItemOldTheming.qml:58:17: QML StyledItem: Mixing of Ubuntu.Components module versions 1.2 and 1.3 detected! PASS : tst_Performance::benchmark_theming(old theming, subtheming enabled) RESULT : tst_Performance::benchmark_theming():"old theming, subtheming enabled": 0.23 msecs per iteration (total: 61, iterations: 256) PASS : tst_Performance::benchmark_theming(subtheming, no changes on themes) RESULT : tst_Performance::benchmark_theming():"subtheming, no changes on themes": 3.0 msecs per iteration (total: 98, iterations: 32) PASS : tst_Performance::benchmark_theming(subtheming, change mid item) RESULT : tst_Performance::benchmark_theming():"subtheming, change mid item": 3.0 msecs per iteration (total: 98, iterations: 32) pure virtual method called terminate called without an active exception Thread 1 "performance" received signal SIGABRT, Aborted. 0x75e00418 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #0 0x75e00418 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x75e0201a in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7622384d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x762216b6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x76221701 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x763f in __cxa_pure_virtual () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x76c2b54a in QQmlPropertyPrivate::setBinding(QQmlProperty const&, QQmlAbstractBinding*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fffed7233b4 in UCTheme::PaletteConfig::restorePalette (this=this@entry=0x5a4800) at uctheme.cpp:278 #8 0x7fffed6e42e3 in UCTheme::PaletteConfig::~PaletteConfig (this=0x5a4800, __in_chrg=) at uctheme_p.h:124 #9 UCTheme::~UCTheme (this=0x5a47e0, __in_chrg=) at uctheme_p.h:41 #10 0x7fffed6e4556 in QQmlPrivate::QQmlElement::~QQmlElement (this=0x5a47e0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:98 #11 QQmlPrivate::QQmlElement::~QQmlElement (this=0x5a47e0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:98 #12 0x767c3053 in QObjectPrivate::deleteChildren() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x767cc094 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x77b800ed in QQuickItem::~QQuickItem() () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #15 0x7fffed6cdefd in UCStyledItemBase::~UCStyledItemBase (this=0x57a9e0, __in_chrg=) at ../../include/UbuntuToolkit/5.5.0/UbuntuToolkit/private/../../../../../src/UbuntuToolkit/ucstyleditembase_p.h:32 #16 QQmlPrivate::QQmlElement::~QQmlElement (this=0x57a9e0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:98 #17 QQmlPrivate::QQmlElement::~QQmlElement (this=0x57a9e0, __in_chrg=) at /usr/include/x86_64-linux-gnu/qt5/QtQml/qqmlprivate.h:98 #18 0x0040286e in tst_Performance::benchmark_theming (this=) at tst_performance.cpp:97 #19 tst_Performance::qt_static_metacall (_o=0x7fffd1c0, _id=, _a=, _c=) at .moc/tst_performance.moc:100 #20 0x767a2eba in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGeneric
[Touch-packages] [Bug 1624314] Re: Failing DPR unit tests
*** This bug is a duplicate of bug 1570478 *** https://bugs.launchpad.net/bugs/1570478 ** This bug has been marked a duplicate of bug 1570478 Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6 -- 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/1624314 Title: Failing DPR unit tests Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: With Qt 5.6. FAIL! : tst_UCUnitsDPR2::dpGridUnitDefaultWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitDefaultWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::dpGridUnitEightWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitEightWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::dpGridUnitSixteenWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitSixteenWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::dpGridUnitTwentyWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR2::guGridUnitTenWithDPR2() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::dpGridUnitDefaultWithDPR3() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::guGridUnitDefaultWithDPR3() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::dpGridUnitSixteenWithDPR3() Compared floats are not the same (fuzzy compare) FAIL! : tst_UCUnitsDPR3::guGridUnitSixteenWithDPR3() Compared floats are not the same (fuzzy compare) See also https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit- ci-amd64-devel/1201/console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] [NEW] systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
Public bug reported: systemd-resolved, or more precisely the hook script /lib/systemd/system /systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: New Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624328] [NEW] tst_listitem failures
Public bug reported: Must be fixed for Qt 5.6. FAIL! : components::ListItemAPI::test_0_defaults() theme.palette.selected.background color by default FAIL! : components::ListItem13API::test_0_defaults() theme.palette.selected.background color by default See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull ** 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/1624328 Title: tst_listitem failures Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Must be fixed for Qt 5.6. FAIL! : components::ListItemAPI::test_0_defaults() theme.palette.selected.background color by default FAIL! : components::ListItem13API::test_0_defaults() theme.palette.selected.background color by default See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610230] Re: tst_expandablescolumn11 fails with Qt 5.6
tst_expandable.11.qml is also failing with TypeErrors in ExpandablesColumn. See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu- ui-toolkit-ci-amd64-devel/1201/consoleFull -- 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/1610230 Title: tst_expandablescolumn11 fails with Qt 5.6 Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_expandablescolumn.11.qml [...] QWARN : components::ExpandablesColumn::test_collapseByClickingOutside() ./_build/qml/Ubuntu/Components/ListItems/1.2/ExpandablesColumn.qml:127: TypeError: Type error [...] FAIL! : components::ExpandablesColumn::test_scrollToTop() Uncaught exception: Type error Loc:[./tests/unit/visual/tst_expandablescolumn.11.qml(115)] cf. tst_ubuntulistview.qml More information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1610230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624331] [NEW] tst_listitem_focus.13.qml unit test failure
Public bug reported: FAIL! : components::ListItemFocus::test_refocus_listview_on_last_focused_item(No content) 'Focus frame shown for the item' returned FALSE. () Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_listitem_focus.13.qml(504)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.6 -- 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/1624331 Title: tst_listitem_focus.13.qml unit test failure Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: FAIL! : components::ListItemFocus::test_refocus_listview_on_last_focused_item(No content) 'Focus frame shown for the item' returned FALSE. () Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_listitem_focus.13.qml(504)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624328] Re: tst_listitem failures
** Tags added: qt5.6 -- 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/1624328 Title: tst_listitem failures Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Must be fixed for Qt 5.6. FAIL! : components::ListItemAPI::test_0_defaults() theme.palette.selected.background color by default FAIL! : components::ListItem13API::test_0_defaults() theme.palette.selected.background color by default See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624285] Re: /etc/init.d/dbus checks for dbus-daemon in wrong location
What's incomplete here? Maybe I was wrong thinking that it should be clear that I'm *not* suggesting that things are installed to the wrong places. It's only the script in /etc/init.d that might need a correction - DAEMON=/usr/bin/dbus-daemon - UUIDGEN=/usr/bin/dbus-uuidgen + DAEMON=/bin/dbus-daemon + UUIDGEN=/bin/dbus-uuidgen with those changes it should work again if there are no outdated settings or assumptions later on in the script. If the script is no longer supposed to be used it should be removed from the package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1624285 Title: /etc/init.d/dbus checks for dbus-daemon in wrong location Status in dbus package in Ubuntu: Incomplete Bug description: dbus 1.6.18-0ubuntu4.3 for Ubuntu 14.04 installs a /etc/init.d/dbus script that checks for /usr/bin/dbus-daemon instead of /bin/dbus- daemon . Evidently this is not a critical failure as something still starts a system dbus on my system: 5 102 2423 1 1 0 41004 3304 - Ss ? 3:07 dbus-daemon --system --fork Who, I haven't figured out yet. The usual suspect systemd seems to be innocent here, because AFAICT it's supposed to start the daemon with a different set of options: ExecStart=//bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation This makes it a little bit tricky to figure out how to relaunch the system dbus daemon... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1624285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610231] Re: tst_sections.13 fails with Qt 5.6
Possibly also causes this failure: FAIL! : components::Page.head.sections::test_bug1511839() Section 0 is selected. Actual (): true Expected (): false Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_pagehead_sections_bug1511839.13.qml(60)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull -- 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/1610231 Title: tst_sections.13 fails with Qt 5.6 Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/visual/visual tests/unit/visual/tst_sections.13.qml [...] FAIL! : components::SectionsApi::initTestCase() Action 0 was triggered with selectedIndex: 1. Actual (): true Expected (): false Loc:[./tests/unit/visual/tst_sections.13.qml(149)] More information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1610231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1436203] Re: [Dash] unity8-dash crashed with ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"
I got this in qemu logging into unity8 session in yakkety. -- 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/1436203 Title: [Dash] unity8-dash crashed with ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: Testing unity8 on a Lenovo IdeaPad s10-3t. The welcome wizard completed successfully. Unity8 loads, the indicators are visible and working. However, nothing else works: the scope shell doesn't load, only the splash screen is shown with the progress indicator spinning, and you can see that periodically it's restarted. Upstart logs for unity8-shell show an infinite loop of these: == Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0' [1427269742.137055] Loader: Loading modules from: /usr/lib/i386-linux-gnu/mir/client-platform/ [1427269742.137918] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/dummy.so [1427269742.139587] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/mesa.so.2 [1427269742.140657] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/mesa.so QSocketNotifier: Can only be used with threads started with QThread QSocketNotifier: Can only be used with threads started with QThread QObject::startTimer: Timers can only be used with threads started with QThread QIBusPlatformInputContext: invalid bus. file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not defined UbuntuWindow - regular geometry file:///usr/share/unity8/Dash/Dash.qml:245: ReferenceError: scopeStyle is not defined ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE" in file ../../../src/ubuntumirclient/glcontext.cpp, line 70 Loading module: 'libubuntu_application_api_desktop_mirclient.so.2.9.0' [1427269746.575630] Loader: Loading modules from: /usr/lib/i386-linux-gnu/mir/client-platform/ [1427269746.576432] Loader: Loading module: /usr/lib/i386-linux-gnu/mir/client-platform/dummy.so ... == ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20150318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 ApportVersion: 2.16.2-0ubuntu4 Architecture: i386 Date: Tue Mar 24 17:31:02 2015 ExecutablePath: /usr/bin/unity8-dash InstallationDate: Installed on 2012-10-07 (898 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity8 StacktraceTop: QMessageLogger::fatal(char const*, ...) const () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 qt_assert(char const*, char const*, int) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so QOpenGLContext::destroy() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5 Title: unity8-dash crashed with SIGABRT in QMessageLogger::fatal() UpgradeStatus: Upgraded to vivid on 2015-01-31 (52 days ago) UserGroups: adm lpadmin nopasswdlogin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1436203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624337] [NEW] Scrollbar tests fail on Qt 5.6.
Public bug reported: FAIL! : components::Scrollbar::test_defaultStylingValues(vertical scrollbar) Wrong styling property default value. Actual (): #5d5d5d Expected (): #11 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(1205)] FAIL! : components::Scrollbar::test_defaultStylingValues(horizontal scrollbar) Wrong styling property default value. Actual (): #5d5d5d Expected (): #11 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(1205)] FAIL! : components::Scrollbar::test_dragThumbAndCheckStyling(vertical scrollbar) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(800)] FAIL! : components::Scrollbar::test_dragThumbAndCheckStyling(horizontal scrollbar) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(838)] and * Start testing of components * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) PASS : components::Scrollbar::initTestCase() FAIL! : components::Scrollbar::test_handlingOfMovingHeader(Standard header) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar_header.13.qml(230)] FAIL! : components::Scrollbar::test_handlingOfMovingHeader(Edit header (with extensions)) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar_header.13.qml(230)] PASS : components::Scrollbar::cleanupTestCase() Totals: 2 passed, 2 failed, 0 skipped, 0 blacklisted * Finished testing of components * See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.6 -- 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/1624337 Title: Scrollbar tests fail on Qt 5.6. Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: FAIL! : components::Scrollbar::test_defaultStylingValues(vertical scrollbar) Wrong styling property default value. Actual (): #5d5d5d Expected (): #11 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(1205)] FAIL! : components::Scrollbar::test_defaultStylingValues(horizontal scrollbar) Wrong styling property default value. Actual (): #5d5d5d Expected (): #11 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(1205)] FAIL! : components::Scrollbar::test_dragThumbAndCheckStyling(vertical scrollbar) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(800)] FAIL! : components::Scrollbar::test_dragThumbAndCheckStyling(horizontal scrollbar) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar.13.qml(838)] and * Start testing of components * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) PASS : components::Scrollbar::initTestCase() FAIL! : components::Scrollbar::test_handlingOfMovingHeader(Standard header) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar_header.13.qml(230)] FAIL! : components::Scrollbar::test_handlingOfMovingHeader(Edit header (with extensions)) Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_scrollbar_header.13.qml(230)] PASS : components::Scrollbar::cleanupTestCase() Totals: 2 passed, 2 failed, 0 skipped, 0 blacklisted * Finished testing of components * See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci-amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598300] Re: cups hang after a while
Nice to see some progress, but the initial problem description and mine is different from what has been discovered. The problem is not just the webinterface, it is cups itself (or the scheduler) which goes inactive and doesn't come back. Today I was able to invest more time. On my system there was still a client.conf in /etc/cups/ The man page says it is deprecated. I moved it to client.conf_bak and restarted cups. The scheduler is now running for over 3 hours. I will have an eye on this, but maybe this fixed my cups problem. -- 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/1598300 Title: cups hang after a while Status in cups package in Ubuntu: Confirmed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624343] [NEW] UbuntuListView TypeErrors
Public bug reported: Failing unit tests with Qt 5.6: * Start testing of components * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) PASS : components::UbuntuListView::initTestCase() PASS : components::UbuntuListView::test_collapseByClickingOutside() PASS : components::UbuntuListView::test_collapseOnClick() PASS : components::UbuntuListView::test_destroyAndRecreateExpanded() PASS : components::UbuntuListView::test_dimOthers() PASS : components::UbuntuListView::test_expandedItem() FAIL! : components::UbuntuListView::test_noScrollingNeeded() Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(116)] FAIL! : components::UbuntuListView::test_scrollIntoView() Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(142)] FAIL! : components::UbuntuListView::test_scrollToTop() Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(129)] PASS : components::UbuntuListView::cleanupTestCase() Totals: 7 passed, 3 failed, 0 skipped, 0 blacklisted * Finished testing of components * See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.6 ** Tags added: qt5.6 -- 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/1624343 Title: UbuntuListView TypeErrors Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Failing unit tests with Qt 5.6: * Start testing of components * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 5.4.0 20160609) PASS : components::UbuntuListView::initTestCase() PASS : components::UbuntuListView::test_collapseByClickingOutside() PASS : components::UbuntuListView::test_collapseOnClick() PASS : components::UbuntuListView::test_destroyAndRecreateExpanded() PASS : components::UbuntuListView::test_dimOthers() PASS : components::UbuntuListView::test_expandedItem() FAIL! : components::UbuntuListView::test_noScrollingNeeded() Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(116)] FAIL! : components::UbuntuListView::test_scrollIntoView() Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(142)] FAIL! : components::UbuntuListView::test_scrollToTop() Uncaught exception: Type error Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_ubuntulistview.10.qml(129)] PASS : components::UbuntuListView::cleanupTestCase() Totals: 7 passed, 3 failed, 0 skipped, 0 blacklisted * Finished testing of components * See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624343/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624342] [NEW] tst_textarea.11.qml unit test fails
Public bug reported: Fails with Qt 5.6. FAIL! : components::TextAreaAPI::test_0_color() TextArea.color is same as TextEdit.canUndo Actual (): #5d5d5d Expected (): #00 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textarea.11.qml(141)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.6 -- 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/1624342 Title: tst_textarea.11.qml unit test fails Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Fails with Qt 5.6. FAIL! : components::TextAreaAPI::test_0_color() TextArea.color is same as TextEdit.canUndo Actual (): #5d5d5d Expected (): #00 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textarea.11.qml(141)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624340] [NEW] tst_textfield.11.qml unit test failures
Public bug reported: Fails with Qt 5.6. FAIL! : components::TextFieldAPI::test_0_cursorRectangle() cursorRectangle 0 by default Actual (): QRectF(0, 4, 1, 16) Expected (): QRectF(0, 0, 0, 0) Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textfield.11.qml(168)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: qt5.6 -- 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/1624340 Title: tst_textfield.11.qml unit test failures Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Fails with Qt 5.6. FAIL! : components::TextFieldAPI::test_0_cursorRectangle() cursorRectangle 0 by default Actual (): QRectF(0, 4, 1, 16) Expected (): QRectF(0, 0, 0, 0) Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textfield.11.qml(168)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616858] Re: ActionBar overflow issues with Qt 5.6
** Branch linked: lp:~ci-train-bot/ubuntu-ui-toolkit/ubuntu-ui-toolkit- ubuntu-yakkety-1948 -- 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/1616858 Title: ActionBar overflow issues with Qt 5.6 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: With Qt 5.6 I'm seeing problems with the ActionBar. 1. tst_actionbar.13.qml passes but there's lots of warnings: QWARN : components::ActionBarApi::test_number_of_actions_in_overflow() ./_build/qml/Ubuntu/Components/Themes/Ambiance/1.3/OverflowPanel.qml:66: ReferenceError: modelData is not defined The unit test should be failing. And obviously there's a bug here. 2. Running tst_actionbar.13.qml in the launcher the overflow button is absent. More information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1616858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617745] Re: popupUtils.open() won't work inside Window with "null" caller
** Branch linked: lp:~ci-train-bot/ubuntu-ui-toolkit/ubuntu-ui-toolkit-
ubuntu-yakkety-1948
--
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/1617745
Title:
popupUtils.open() won't work inside Window with "null" caller
Status in Canonical System Image:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
I think I found a regression with popupUtils.open() in rc-proposed
(r512 on mako):
I have some code which is invoking a dialog in this way:
PopupUtils.open(Qt.resolvedUrl("DeleteConfirmation.qml"), null, {
... params... })
This now doesn't work, but it works on OTA-12.
This can cause serious regression in third party applications, if
dialogs stop appearing.
Furthermore, if I replace "null" with a valid item, things work again
but I get a warning on the console:
qml: 'caller' is DEPRECATED. It has no effect.
Which seems wrong, given that in the current stable documentation
there is absolutely no mention of the caller property being
deprecated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617745/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577828] Re: ActivityIndicator should respect theme activity color (i.e. it should be blue)
** Branch linked: lp:~ci-train-bot/ubuntu-ui-toolkit/ubuntu-ui-toolkit- ubuntu-yakkety-1948 -- 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/1577828 Title: ActivityIndicator should respect theme activity color (i.e. it should be blue) Status in Ubuntu UX: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: ActivityIndicator should use the color specified by theme.palette.normal.activity instead of hard coding orange, which is supposed to be used to indicate focus, not activity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1577828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616868] Re: Scrollbar thumb shows as hovered after touch release
** Branch linked: lp:~ci-train-bot/ubuntu-ui-toolkit/ubuntu-ui-toolkit- ubuntu-yakkety-1948 -- 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/1616868 Title: Scrollbar thumb shows as hovered after touch release Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: ubuntu-ui-toolkit r2079 The fix to bug #1608897 created another issue. Since MouseArea does not get the exited() signal on touch release (to be investigated if that's intended), dragging the thumb with touchscreen and releasing while the finger is still inside the area of the thumb will cause the thumb to show as hovered even after release. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1616868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616926] Re: Scrollbar thumb shows as hovered after mouse is released outside the thumb
** Branch linked: lp:~ci-train-bot/ubuntu-ui-toolkit/ubuntu-ui-toolkit- ubuntu-yakkety-1948 -- 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/1616926 Title: Scrollbar thumb shows as hovered after mouse is released outside the thumb Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: ubuntu-ui-toolkit r2079 The fix to bug #1608897 created another issue. The code that checks if the thumb is being hovered currently only checks the y position of the input event, an optimization that worked well with the previous assumption that releasing mouse would always reset the hover state (but that was causing bug #1608897). There were, in fact, 2 cases before: - input device moves away (no pressed buttons) -> onExited is fired -> hover is reset - input device moves away while press-hold is in progress --> onRelease will reset hover Now that the behaviour changed and release does not reset the hover state, we obviously need to check both x and y position To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1616926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1614045] Re: tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton
** Branch linked: lp:~ci-train-bot/ubuntu-ui-toolkit/ubuntu-ui-toolkit- ubuntu-yakkety-1948 -- 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/1614045 Title: tst_focus.13.qml trigger_via_keyboard is bogus for ComboButton Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: The cases for ComboButton in tst_focus.13.qml listed in test_trigger_via_keyboard_data use "button" as the item, which means they're not actually testing a ComboButton. Also the comboButton has no override mechanism in the test so it wouldn't be testable as-is. This needs to be corrected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1614045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1611327] Re: Disabled ListItem inside ListView takes focus but does not show focus ring
** 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/1611327
Title:
Disabled ListItem inside ListView takes focus but does not show focus
ring
Status in Ubuntu UX:
Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
Items outside of a ListView are skipped when using keyboard navigation
to change the focus. However, a ListItem inside a ListView takes the
focus even when it is disabled, but it does not show the focus frame
when focused.
For example, execute this QML program:
import QtQuick 2.4
import Ubuntu.Components 1.3
Item {
width: units.gu(50)
height: units.gu(50)
ListView {
anchors.fill: parent
delegate: ListItem {
enabled: index != 2
Label {
anchors.centerIn: parent
text: parent.enabled ? "enabled" : "disabled"
}
}
model: 5
}
}
Press TAB to focus on the ListView. Then press the down-cursor-key
twice to move the focus down inside the ListView. The focus will be on
the disabled item, but not focus frame is visible This is confusing
for the user since the focus seems to disappear, and the Item where
the focus seems to be (although invisible) cannot be triggered because
it is disabled.
Note: When fixing this bug, also test the solution for Horizontal
ListViews (and RightToLeft and BottomToTop directions), since I
encountered this bug in the scrolling toolbar (in progress) that has a
Horizontal, RightToLeft ListView.
==UX Fix===
Bypass focus for a disabled item and show focus immediately for the
next available enabled item.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1611327/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1597453] Re: [MIR] content-hub
** Changed in: content-hub (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1597453 Title: [MIR] content-hub Status in Canonical System Image: In Progress Status in content-hub package in Ubuntu: Fix Committed Bug description: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues at this time. It has been reviewed by security in the past for use on the phone. [Quality assurance] * This package has both unit tests and autopkgtests [Dependencies] Most dependencies are already in main with the exception of the following: * ubuntu-download-manager (bug #1488425) * qtbase-opensource-src-gles (the non-gles variant is in main) (doesn't need a MIR?) [Standards compliance] * This package uses cmake and is properly translated. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1569596] Re: contact-app when I select a contact object in the list I sometimes get the details of the previous one
I have reset the phone krillin to factory defaults, reloaded my contacts from a vcards file, the alarms, and the messages history etc... After done, the problem yet exists with OTA-12 : The first time you enter in the application "contacts", you will get the same result. I have realized that the first AND the last contact names does not appear in the list, in stead of the only first one. I can be quite sur it is not a missing frame painting. The problem is more general... It is really a screen refresh problem with, I imagine, supplying some bad index data. -- 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/1569596 Title: contact-app when I select a contact object in the list I sometimes get the details of the previous one Status in Canonical System Image: Incomplete Status in address-book-app package in Ubuntu: New Bug description: I am using the recent standard version 32 - OTA-10.1 on krillin (bq aquaris 4.5) Step to reproduce: 1- Restart the phone 2- go to the dash and preload the main applications: contact, messaging, and calendar. 3- Wait until calendar window comes up. 4- swith to contact application, and wait 10 seconds. 5- select one contact in the middle of the 1st screen to get its own details Actual Result: 6- realize you get the previous contact! Expected result: 6- should get the selected contact details Context: I have many contacts on the phone that I have transferred with vcards. Remember to select a contact that is on the first screen. Example demonstrating this issue: See attached video DSCN2210.AVI (sorry for the bad movie quality). Other notice: I have similar issue with the clock application, when I want to change the time of an event, another one is presented for modification (among 4 events). Difficult to reproduce... If you want I'll show you in another bugid report. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1569596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624378] [NEW] apt-key net-update should use trusted.gpg.d/
Public bug reported: apt-key net-update for the new world order /etc/apt/trusted.gpg is not longer preffered location for key updates. Instead, individual opengpg packets of exported public keys should be placed in /etc/apt/trusted.gpg.d Debian has already migrated to placing the keys there. To comply with /etc/apt/trusted.gpg.d structure, instead of updating the keys in the /etc/apt/trusted.gpg, imho apt-key net-update should download and place a /etc/apt/trusted.gpg.d/ubuntu-archive-netupdate.gpg key. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1624378 Title: apt-key net-update should use trusted.gpg.d/ Status in apt package in Ubuntu: New Bug description: apt-key net-update for the new world order /etc/apt/trusted.gpg is not longer preffered location for key updates. Instead, individual opengpg packets of exported public keys should be placed in /etc/apt/trusted.gpg.d Debian has already migrated to placing the keys there. To comply with /etc/apt/trusted.gpg.d structure, instead of updating the keys in the /etc/apt/trusted.gpg, imho apt-key net-update should download and place a /etc/apt/trusted.gpg.d/ubuntu-archive- netupdate.gpg key. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624378/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624378] Re: apt-key net-update should use trusted.gpg.d/
$ curl http://archive.ubuntu.com/ubuntu/project/ubuntu-archive- keyring.gpg.sigs 2>/dev/null | gpg --no-default-keyring --keyring /usr/share/keyrings/ubuntu-master-keyring.gpg --output /etc/apt/trusted.gpg.d/ubuntu-archive-netupdate.gpg --decrypt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1624378 Title: apt-key net-update should use trusted.gpg.d/ Status in apt package in Ubuntu: New Bug description: apt-key net-update for the new world order /etc/apt/trusted.gpg is not longer preffered location for key updates. Instead, individual opengpg packets of exported public keys should be placed in /etc/apt/trusted.gpg.d Debian has already migrated to placing the keys there. To comply with /etc/apt/trusted.gpg.d structure, instead of updating the keys in the /etc/apt/trusted.gpg, imho apt-key net-update should download and place a /etc/apt/trusted.gpg.d/ubuntu-archive- netupdate.gpg key. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624378/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623553] Re: [UX] camera app - accidentally touching the screen locks the input (focus, shot)
same thing with the tablet, people playing with my tablet are unable to take photos (most of the time i say, first users) because they accidentally touch the screen with the palm and the focus/shot button don't work super totally not good... -- 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/1623553 Title: [UX] camera app - accidentally touching the screen locks the input (focus, shot) Status in Canonical System Image: New Status in camera-app package in Ubuntu: Confirmed Bug description: [UX] camera app - accidentally touching the screen locks the input (focus, shot) arale/rc-proposed. due to the thin bezel and large screen size, i'm accidentally touching the screen in more than one place (multitouch?) and that locks the UI. so to test.. open the camera app, keep a finger on the screen and with another finger try to focus or take a photo. does nothing. this is totally not cool because until now i thought the UI locked up without realizing that i was barely touching with the another finger (i has many:P) the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624381] [NEW] add additional shortcut support for zoom/unzoom in US keyboards
Public bug reported: On US keyboards, the "+" (plus) key is in shifted position, and the "-" (minus) is not. All the other browsers (chrome, chromium, firefox) support the following shortcuts for zoom/unzoom and we should do the same, so user does not have to press ctrl+shift as that is not expected. zoom in: ctrl+plus ctrl+equals zoom out: ctrl+underscore ctrl+minus ** Affects: webbrowser-app (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Confirmed ** Changed in: webbrowser-app (Ubuntu) Importance: Undecided => High ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed ** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Summary changed: - add shortcut support for zoom in US keyboards + add additional shortcut support for zoom/unzoom in US keyboards -- 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/1624381 Title: add additional shortcut support for zoom/unzoom in US keyboards Status in webbrowser-app package in Ubuntu: Confirmed Bug description: On US keyboards, the "+" (plus) key is in shifted position, and the "-" (minus) is not. All the other browsers (chrome, chromium, firefox) support the following shortcuts for zoom/unzoom and we should do the same, so user does not have to press ctrl+shift as that is not expected. zoom in: ctrl+plus ctrl+equals zoom out: ctrl+underscore ctrl+minus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1624381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624381] Re: add additional shortcut support for zoom/unzoom in US keyboards
Note that this is only valid on US keyboard layouts. On other layouts, "+" and "=" may be located on entirely different keys (and same goes for "-" and "_"). I wonder whether firefox and chrome special-case the US layout, or enable those shortcuts regardless. -- 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/1624381 Title: add additional shortcut support for zoom/unzoom in US keyboards Status in webbrowser-app package in Ubuntu: Confirmed Bug description: On US keyboards, the "+" (plus) key is in shifted position, and the "-" (minus) is not. All the other browsers (chrome, chromium, firefox) support the following shortcuts for zoom/unzoom and we should do the same, so user does not have to press ctrl+shift as that is not expected. zoom in: ctrl+plus ctrl+equals zoom out: ctrl+underscore ctrl+minus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1624381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624027] Re: unable to create a fedora container on ppc64el
According to the list of images fedora22amd64default20160916_01:27 fedora22i386default20160916_01:27 fedora23amd64default20160916_01:58 fedora23i386default20160916_01:58 fedora24amd64default20160916_01:27 fedora24i386default20160916_01:27 arch = ppc64el is not supported The only supported image for ppc64el arch are: $ sudo lxc-create -n debian01 -t download |grep ppc64el debian jessie ppc64el default 20160907_22:42 debian sid ppc64el default 20160907_22:42 debian stretch ppc64el default 20160907_22:42 ubuntu trusty ppc64el default 20160907_03:49 ubuntu wilyppc64el default 20160907_03:49 ubuntu xenial ppc64el default 20160908_03:49 ubuntu yakkety ppc64el default 20160907_03:49 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1624027 Title: unable to create a fedora container on ppc64el Status in lxc package in Ubuntu: New Bug description: I am not able to create a 'fedora' container on ppc64el using the lxc templates: ➜ ~ sudo lxc-create -n fedora -t fedora Host CPE ID from /etc/os-release: This is not a fedora host and release missing, defaulting to 22 use -R|--release to specify release Checking cache download in /var/cache/lxc/fedora/ppc64le/22/rootfs ... Downloading fedora minimal ... Fetching release rpm name from http://ftp.icm.edu.pl/pub/Linux/dist/fedora-secondary/releases/22/Everything/ppc64le/os//Packages/f... % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 4380 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 194k0 194k0 0 40088 0 --:--:-- 0:00:04 --:--:-- 69182 Fetching fedora release rpm from http://ftp.icm.edu.pl/pub/Linux/dist/fedora-secondary/releases/22/Everything/ppc64le/os//Packages/f/fedora-release-22-1.noarch.rpm.. % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 23816 100 238160 0 31002 0 --:--:-- --:--:-- --:--:-- 30970 Fetching repos rpm name from http://ftp.icm.edu.pl/pub/Linux/dist/fedora-secondary/releases/22/Everything/ppc64le/os//Packages/f... % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 4380 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 194k0 194k0 0 52346 0 --:--:-- 0:00:03 --:--:-- 64301 Fetching fedora repos rpm from http://ftp.icm.edu.pl/pub/Linux/dist/fedora-secondary/releases/22/Everything/ppc64le/os//Packages/f/fedora-repos-22-1.noarch.rpm... % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 20440 100 204400 0 26047 0 --:--:-- --:--:-- --:--:-- 26071 Bootstrap Environment testing... Fedora Installation Bootstrap Build... Downloading stage 0 LiveOS squashfs file system from archives.fedoraproject.org... Have a beer or a cup of coffee. This will take a bit (~300MB). Fedora Master Mirror Servers Modules for Fedora Core and Extras have been removed, as this content is no longer updated. See the instructions below for how to mirror current content. See http://fedoraproject.org/wiki/Infrastructure/Mirroring for instructions. receiving incremental file list rsync: change_dir "/fedora/linux/releases/20/Fedora/ppc64le/os" (in fedora-archive) failed: No such file or directory (2) sent 8 bytes received 135 bytes 13.62 bytes/sec total size is 0 speedup is 0.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1655) [Receiver=3.1.1] Download of squashfs image failed. Fedora Bootstrap setup failed Failed to download 'fedora base' failed to install fedora lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for fedora failed lxc-create: tools/lxc_create.c: main: 318 Error creating container fedora To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1624027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623553] Re: [UX] camera app - accidentally touching the screen locks the input (focus, shot)
** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Bill Filler (bfiller) -- 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/1623553 Title: [UX] camera app - accidentally touching the screen locks the input (focus, shot) Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: [UX] camera app - accidentally touching the screen locks the input (focus, shot) arale/rc-proposed. due to the thin bezel and large screen size, i'm accidentally touching the screen in more than one place (multitouch?) and that locks the UI. so to test.. open the camera app, keep a finger on the screen and with another finger try to focus or take a photo. does nothing. this is totally not cool because until now i thought the UI locked up without realizing that i was barely touching with the another finger (i has many:P) the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
** Changed in: upstart (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 upstart in Ubuntu. https://bugs.launchpad.net/bugs/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates Status in gnome-session package in Ubuntu: In Progress Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Fix Committed Bug description: Sometimes on session start unity-gtk-module.service runs too late or something, and $GTK_MODULES does not include "unity". It is in "systemctl --user show-environment" but not in a terminal bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
** Branch linked: lp:~ubuntu-core-dev/upstart/ubuntu -- 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/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates Status in gnome-session package in Ubuntu: In Progress Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Fix Committed Bug description: Sometimes on session start unity-gtk-module.service runs too late or something, and $GTK_MODULES does not include "unity". It is in "systemctl --user show-environment" but not in a terminal bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624261] Re: [M10 HD] Video recorded from camera app is reproduced rotate 90 degrees.
Its odd that Cololer doesn't also have the issue, perhaps a qtubuntu quirk introduced this? ** Also affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Description changed: Environment Product: Freezer HD FW version: UBUNTU 15.04 (r14) HW version: MP Material: Description Steps to Reproduce: 1 - Go to Camera app 2 - Go to video and start to record. 3 - Stop record, go to gallery app and reproduce it. Actual Result: Video is reproduced rotate in 90 degrees. Expected Result: Video should be reproduced as the same way it was recorded. Reproducibility: 100% Additional info: The issue is reproducible only in HD device and with rear and front camera. + + See related bugs lp:1601887 and lp:1590415 ** Also affects: frieza 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/1624261 Title: [M10 HD] Video recorded from camera app is reproduced rotate 90 degrees. Status in Canonical System Image: New Status in frieza: New Status in camera-app package in Ubuntu: New Bug description: Environment Product: Freezer HD FW version: UBUNTU 15.04 (r14) HW version: MP Material: Description Steps to Reproduce: 1 - Go to Camera app 2 - Go to video and start to record. 3 - Stop record, go to gallery app and reproduce it. Actual Result: Video is reproduced rotate in 90 degrees. Expected Result: Video should be reproduced as the same way it was recorded. Reproducibility: 100% Additional info: The issue is reproducible only in HD device and with rear and front camera. See related bugs lp:1601887 and lp:1590415 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1624261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623901] Re: DUT does not locate. GPS is not working.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: location-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1623901 Title: DUT does not provide location quickly after a cold boot Status in Canonical System Image: Confirmed Status in krillin: New Status in vegetahd: New Status in location-service package in Ubuntu: Confirmed Bug description: Environment Product: VEGETA HD // KRILLIN FW version: UBUNTU 15.04 (r46) // UBUNTU (r66) HW version: MP Material: Description Steps to Reproduce: 1 - Activate Location detection 2 - Location Settings: Select “Using GPS, anonymised Wi-Fi and mobile network info. By selecting this option you accept the Nokia HERE terms and conditions. Actual Result: DUT does not locate. Neither Nearby nor HERE maps works because of this. Expected Result: DUT should locate as expected. Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623901] Re: DUT does not provide location quickly after a cold boot
It seems this is a duplicate of bug #596409 reported some time ago. ** Summary changed: - DUT does not locate. GPS is not working. + DUT does not provide location quickly after a cold boot ** Changed in: canonical-devices-system-image Importance: Critical => Medium ** Changed in: canonical-devices-system-image Milestone: 13 => backlog ** Changed in: location-service (Ubuntu) Assignee: (unassigned) => Thomas Voß (thomas-voss) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1623901 Title: DUT does not provide location quickly after a cold boot Status in Canonical System Image: Confirmed Status in krillin: New Status in vegetahd: New Status in location-service package in Ubuntu: Confirmed Bug description: Environment Product: VEGETA HD // KRILLIN FW version: UBUNTU 15.04 (r46) // UBUNTU (r66) HW version: MP Material: Description Steps to Reproduce: 1 - Activate Location detection 2 - Location Settings: Select “Using GPS, anonymised Wi-Fi and mobile network info. By selecting this option you accept the Nokia HERE terms and conditions. Actual Result: DUT does not locate. Neither Nearby nor HERE maps works because of this. Expected Result: DUT should locate as expected. Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623901] Re: DUT does not provide location quickly after a cold boot
Since it's (a) not a regression, and (b) clears up after a reboot, I'm tagging this as not critical, and to match the likely dupe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1623901 Title: DUT does not provide location quickly after a cold boot Status in Canonical System Image: Confirmed Status in krillin: New Status in vegetahd: New Status in location-service package in Ubuntu: Confirmed Bug description: Environment Product: VEGETA HD // KRILLIN FW version: UBUNTU 15.04 (r46) // UBUNTU (r66) HW version: MP Material: Description Steps to Reproduce: 1 - Activate Location detection 2 - Location Settings: Select “Using GPS, anonymised Wi-Fi and mobile network info. By selecting this option you accept the Nokia HERE terms and conditions. Actual Result: DUT does not locate. Neither Nearby nor HERE maps works because of this. Expected Result: DUT should locate as expected. Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
** Changed in: gnome-session (Ubuntu) Status: In Progress => Won't Fix ** Changed in: gnome-session (Ubuntu) Status: Won't Fix => Fix Committed -- 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/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates Status in gnome-session package in Ubuntu: Fix Committed Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Fix Committed Bug description: Sometimes on session start unity-gtk-module.service runs too late or something, and $GTK_MODULES does not include "unity". It is in "systemctl --user show-environment" but not in a terminal bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596409] Re: Cannot get the location on first fresh boot unless user reboot the phone
Possibly reported here also: bug #1623901 ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1596409 Title: Cannot get the location on first fresh boot unless user reboot the phone Status in Canonical System Image: Confirmed Status in location-service package in Ubuntu: New Bug description: current build number: 114 device name: turbo channel: ubuntu-touch/rc-proposed/meizu.en last update: 2016-06-27 10:44:11 version version: 114 version ubuntu: 20160624 version device: 20160617-82a5c0d version custom: 20160624-981-22-9 Steps: 1.Flash with latest image 2.Complete wizard and go to Nearby Scope 3.Pull down to refresh 4.Accept the location service prompt 5.Pull down nearby scope to refresh again actual=>The animation at bottom disappears in 1s, then nothing happens, still default content ask user to enable location 6.Go to today scope and pull down to refresh actual=>Location isn't detected 7.Open uNav app 8.Tap on center my location and accept the trust prompt actual=>fail to get location 9.Reboot device 10.Try to get location on today scope/nearby scope/map apps actual=>Location service works fine Expected result: Location should work well on first fresh boot Other info: Issue can also be reproduced on Krillin/Arale To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1596409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624022] Re: Alias 'browse' to sensible-browser
Advice from Chad is that we should symlink /usr/bin/browse to sensible-browser in the sensible-utils package. Looking at that now. ** Changed in: sensible-utils (Ubuntu) Assignee: (unassigned) => Will Cooke (willcooke) ** Changed in: sensible-utils (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sensible-utils in Ubuntu. https://bugs.launchpad.net/bugs/1624022 Title: Alias 'browse' to sensible-browser Status in sensible-utils package in Ubuntu: In Progress Bug description: The 'sensible-browser' command is very useful, but it's a bit unwieldy to use everywhere in docs. How about aliasing the simple 'browse' to sensible-browser, so I can recommend things like: sudo apt install foo; browse http://locahost:2022/ That would be crisp clean and friendly for current users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1624022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363480] Re: ubuntu-keyring imports the Ubuntu CD Signing Key as a key trusted by apt
This is correct and intended behavior I believe. By default, packages archives shipped on the ISO images are signed with the cdimage key, and are trusted. This means one can perform [dist-]upgrades from installation ISOs (note these are no longer produced by default). And enabled one to install packages from the ISOs (e.g. install updated openssl on a 14.04.0 host from the 14.04.1 server iso; another example install optional drivers off the desktop iso). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1363480 Title: ubuntu-keyring imports the Ubuntu CD Signing Key as a key trusted by apt Status in ubuntu-keyring package in Ubuntu: New Bug description: Please take this with a grain of salt as I'm not reporting it with a clean trusty install at my fingertips. ubuntu-keyring ships a /usr/share/keyrings/ubuntu-archive-keyring.gpg file that contains the Ubuntu CD Signing Keys (old and new): % gpg /usr/share/keyrings/ubuntu-archive-keyring.gpg pub 1024D/437D05B5 2004-09-12 Ubuntu Archive Automatic Signing Key sub 2048g/79164387 2004-09-12 pub 1024D/FBB75451 2004-12-30 Ubuntu CD Image Automatic Signing Key pub 4096R/C0B21F32 2012-05-11 Ubuntu Archive Automatic Signing Key (2012) pub 4096R/EFE21092 2012-05-11 Ubuntu CD Image Automatic Signing Key (2012) They end up being trusted by apt because the keyring is taken as the initial trusted key set in /etc/apt/trusted.gpg. This is most likely not what we want. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1363480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562308] Re: missing or duplicate lines caused by a wrapped line with wide characters
** Changed in: less (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1562308 Title: missing or duplicate lines caused by a wrapped line with wide characters Status in less package in Ubuntu: Confirmed Bug description: When you scroll down text with "j" key and encounter a wrapped line with wide characters (such as UTF8-encoded Japanese characters), "less" seems to show the whole wrapped line at a single "j" key, causing the view scroll down by 2 lines at once. Strangely, if you type "k" to scroll up, it does that by only 1 line. As a result, there is a missing line that should have been shown. Even stranger stuff (i.e., duplicate lines) happens when you type "j" and "k" alternately when a wrapped line with wide characters is at the bottom of the view. # Steps to reproduce 1. Open xterm. 2. Set the geometory of xterm to 71x22. 3. Open the attached lesstest.long_jap.txt with less (maybe you need environment variable LANG=ja_JP.UTF-8) 4. Type "j", then you will see "003" at the top, and a long wrapped line with Japanese characters at the bottom. 5. Type "k", then you will see "001" and "003" at the top. "002" is missing. # Expected behavior In step 4, only the first part of the wrapped line should be shown. In step 5, all "001", "002" and "003" should be shown. # Test Environment - Xubuntu 16.04 (Xenial) beta (in VirtualBox on Xubuntu 14.04) - less: 481-2.1 - xterm: 322-1ubuntu1 - Japanese environment (LANG=ja_JP.UTF-8) # Note - The same problem happens on xfce4-terminal (0.6.3-2ubuntu1) - lv (4.51-2.3build1) doesn't have such problem. - In "less" in Xubuntu 14.04 (version 458-2), this problem didn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1562308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624408] [NEW] ubuntu-keyring migrate to fragment files
*** This bug is a security vulnerability *** Public security bug reported: Instead of shipping a single keyring with 4 keys, ship each key individually in trusted.gpg.d and do not call apt-key update at all. Remove keys from /etc/apt/trusted.gpg This is similar to changes done in debian-archive-keyring 2012.1 upload. ** Affects: ubuntu-keyring (Ubuntu) Importance: Undecided Status: New ** Patch added: "ubuntu-keyring_2016.09.16.debdiff.asc" https://bugs.launchpad.net/bugs/1624408/+attachment/4742035/+files/ubuntu-keyring_2016.09.16.debdiff.asc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1624408 Title: ubuntu-keyring migrate to fragment files Status in ubuntu-keyring package in Ubuntu: New Bug description: Instead of shipping a single keyring with 4 keys, ship each key individually in trusted.gpg.d and do not call apt-key update at all. Remove keys from /etc/apt/trusted.gpg This is similar to changes done in debian-archive-keyring 2012.1 upload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1624408/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624406] [NEW] systemd-fsck test started to fail
Public bug reported:
http://autopkgtest.ubuntu.com/packages/s/systemd/yakkety/amd64 now often
fails with
==
FAIL: test_systemd_fsckd_with_failure (__main__.FsckdTest)
Ensure that a failing systemd-fsckd doesn't prevent system to boot
--
Traceback (most recent call last):
File
"/tmp/autopkgtest.WN0dWu/build.zlE/systemd-231/debian/tests/systemd-fsckd",
line 125, in test_systemd_fsckd_with_failure
self.assertTrue(self.was_running('plymouth-start'))
AssertionError: False is not true
Same assertion failure on some other systemd-fsckd tests.
** Affects: systemd (Ubuntu)
Importance: High
Assignee: Martin Pitt (pitti)
Status: In Progress
** Tags: autopkgtest yakkety
** Tags added: autopkgtest yakkety
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-16.09
--
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/1624406
Title:
systemd-fsck test started to fail
Status in systemd package in Ubuntu:
In Progress
Bug description:
http://autopkgtest.ubuntu.com/packages/s/systemd/yakkety/amd64 now
often fails with
==
FAIL: test_systemd_fsckd_with_failure (__main__.FsckdTest)
Ensure that a failing systemd-fsckd doesn't prevent system to boot
--
Traceback (most recent call last):
File
"/tmp/autopkgtest.WN0dWu/build.zlE/systemd-231/debian/tests/systemd-fsckd",
line 125, in test_systemd_fsckd_with_failure
self.assertTrue(self.was_running('plymouth-start'))
AssertionError: False is not true
Same assertion failure on some other systemd-fsckd tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624406/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363482] Re: ubuntu-keyring includes 1024D keys
Might as well just wait for precise EOL. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1363482 Title: ubuntu-keyring includes 1024D keys Status in Ubuntu CD Images: Fix Released Status in ubuntu-keyring package in Ubuntu: Confirmed Bug description: ubuntu-keyring as shipped in trusty contains old 1024D keys dating back to 2004 which are still being trusted for the main archive: % gpg /usr/share/keyrings/ubuntu-archive-keyring.gpg | grep 1024D pub 1024D/437D05B5 2004-09-12 Ubuntu Archive Automatic Signing Key pub 1024D/FBB75451 2004-12-30 Ubuntu CD Image Automatic Signing Key Given that newer 4096R keys are present and have been in precise (through -updates) and trusty, it seems to be about time to drop the older keys. (In the hope that apt does not chose on signatures it cannot verify, otherwise the publisher would need to stop signing with the old key as well.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1363482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622717] Re: "Quit" from quicklist doesn’t close all open windows, doesn’t actually quit the application
Related to bug #1624407 ? -- 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/1622717 Title: "Quit" from quicklist doesn’t close all open windows, doesn’t actually quit the application Status in Canonical System Image: Triaged Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: I’m attaching a sample click application that contains a simple qml scene that opens several windows. This can be installed on a device with: pkcon install-local --allow-untrusted fubar.osomon_0.4_all.click Initially, only one window is open, and tapping on any window opens one more window. If I reveal the launcher and long press on the app’s icon to select the "Quit" option, not all windows are closed: - if there is only one window open, it’s closed and the application successfully exits - if there are two windows open, only the second window is closed, the first one remains open (and consequently the application is still running) - if there are three windows open, only the first and third one are closed, the second one remains… Expected behaviour: when "Quit" is tapped, all open windows are closed, and the application exits. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1622717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565659] Re: Upgrade to 1.1.2 that was released in August 2016
YY has 1.1.2 now ** Changed in: alsa-utils (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1565659 Title: Upgrade to 1.1.2 that was released in August 2016 Status in alsa-utils package in Ubuntu: Fix Released Bug description: Please, upgrade to 1.1.1 that was released end of March 2016. See also http://www.alsa- project.org/main/index.php/Changes_v1.1.0_v1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1565659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624027] Re: unable to create a fedora container on ppc64el
Is it possible to add fedora for ppc64el arch images ? ** Changed in: lxc (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1624027 Title: unable to create a fedora container on ppc64el Status in lxc package in Ubuntu: Opinion Bug description: I am not able to create a 'fedora' container on ppc64el using the lxc templates: ➜ ~ sudo lxc-create -n fedora -t fedora Host CPE ID from /etc/os-release: This is not a fedora host and release missing, defaulting to 22 use -R|--release to specify release Checking cache download in /var/cache/lxc/fedora/ppc64le/22/rootfs ... Downloading fedora minimal ... Fetching release rpm name from http://ftp.icm.edu.pl/pub/Linux/dist/fedora-secondary/releases/22/Everything/ppc64le/os//Packages/f... % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 4380 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 194k0 194k0 0 40088 0 --:--:-- 0:00:04 --:--:-- 69182 Fetching fedora release rpm from http://ftp.icm.edu.pl/pub/Linux/dist/fedora-secondary/releases/22/Everything/ppc64le/os//Packages/f/fedora-release-22-1.noarch.rpm.. % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 23816 100 238160 0 31002 0 --:--:-- --:--:-- --:--:-- 30970 Fetching repos rpm name from http://ftp.icm.edu.pl/pub/Linux/dist/fedora-secondary/releases/22/Everything/ppc64le/os//Packages/f... % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 4380 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 194k0 194k0 0 52346 0 --:--:-- 0:00:03 --:--:-- 64301 Fetching fedora repos rpm from http://ftp.icm.edu.pl/pub/Linux/dist/fedora-secondary/releases/22/Everything/ppc64le/os//Packages/f/fedora-repos-22-1.noarch.rpm... % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 20440 100 204400 0 26047 0 --:--:-- --:--:-- --:--:-- 26071 Bootstrap Environment testing... Fedora Installation Bootstrap Build... Downloading stage 0 LiveOS squashfs file system from archives.fedoraproject.org... Have a beer or a cup of coffee. This will take a bit (~300MB). Fedora Master Mirror Servers Modules for Fedora Core and Extras have been removed, as this content is no longer updated. See the instructions below for how to mirror current content. See http://fedoraproject.org/wiki/Infrastructure/Mirroring for instructions. receiving incremental file list rsync: change_dir "/fedora/linux/releases/20/Fedora/ppc64le/os" (in fedora-archive) failed: No such file or directory (2) sent 8 bytes received 135 bytes 13.62 bytes/sec total size is 0 speedup is 0.00 rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1655) [Receiver=3.1.1] Download of squashfs image failed. Fedora Bootstrap setup failed Failed to download 'fedora base' failed to install fedora lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for fedora failed lxc-create: tools/lxc_create.c: main: 318 Error creating container fedora To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1624027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624415] [NEW] tcsh coredumps all the time on tab
Public bug reported: When a users having tcsh as its [login] shell presses tab key (autocompletion), tcsh coredumps immediately, always: admin.python ~ > gdb tcsh GNU gdb (Ubuntu 7.11.90.20160906-0ubuntu1) 7.11.90.20160906-git ... (gdb) run Starting program: /local/home/admin/tcsh admin.python ~ > ls . Suspended (tty output) admin.python ~ > fg gdb tcsh Program received signal SIGSEGV, Segmentation fault. __GI___rewinddir (dirp=0x771808) at ../sysdeps/posix/rewinddir.c:34 34 ../sysdeps/posix/rewinddir.c: No such file or directory. (gdb) quit A debugging session is active. Inferior 1 [process 25990] will be killed. Quit anyway? (y or n) y admin.python ~ > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Codename: yakkety ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1624415 Title: tcsh coredumps all the time on tab Status in apport package in Ubuntu: New Bug description: When a users having tcsh as its [login] shell presses tab key (autocompletion), tcsh coredumps immediately, always: admin.python ~ > gdb tcsh GNU gdb (Ubuntu 7.11.90.20160906-0ubuntu1) 7.11.90.20160906-git ... (gdb) run Starting program: /local/home/admin/tcsh admin.python ~ > ls . Suspended (tty output) admin.python ~ > fg gdb tcsh Program received signal SIGSEGV, Segmentation fault. __GI___rewinddir (dirp=0x771808) at ../sysdeps/posix/rewinddir.c:34 34../sysdeps/posix/rewinddir.c: No such file or directory. (gdb) quit A debugging session is active. Inferior 1 [process 25990] will be killed. Quit anyway? (y or n) y admin.python ~ > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1624415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its surfaces to be closed
Just marked unity7 also affected, as its implementation is similar (it’s Bamf windows instead of Mir surfaces, but essentially it behaves the same). ** Summary changed: - Closing an application doesn’t actually close it, it merely requests all its surfaces to be closed + Closing an application doesn’t actually close it, it merely requests all its windows to be closed ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1624407 Title: Closing an application doesn’t actually close it, it merely requests all its windows to be closed Status in qtmir package in Ubuntu: New Status in unity package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Currently in unity8, when requesting to "Quit" a running application from the launcher, what happens is that qtmir goes through all its associated windows/surfaces, and closes them one by one. Supposedly, when the last window is closed, the application terminates itself (but this is not necessarily the case, see https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed- prop). This prevents application authors from doing proper cleanup before the app is closed. For example in Qt, the QCoreApplication::aboutToQuit() signal is emitted only after all windows have been closed, so the application doesn’t get a chance to e.g. save the list of open windows (real use case for multi-window browser application which saves the current session). This is similar to unity7’s implementation by the way, but I think it’s wrong. Surely there must be a way (maybe toolkit-specific) to request an app to terminate itself (and fall back to closing all windows if not). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1624407/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
