[Touch-packages] [Bug 1624967] Re: $TERM is not set for /etc/rc.local
But causing some output for example with echo in /etc/rc.local causes it to be written on the console on booting. Or is this the expected behavior even if the journal is used? -- 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/1624967 Title: $TERM is not set for /etc/rc.local Status in systemd package in Ubuntu: Invalid Bug description: I'm using Ubuntu 16.10 dev with systemd 231-6 and after upgrading from upstart to systemd I'm noticing that a setterm command fails that I have put into /etc/rc.local in the past (to make specific settings on the console without requiring a login). On making a look at this I figured out that $TERM is not set at default anymore and maybe it makes sense to set it at default again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624967/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620937] Re: konsole crashes on startup since Qt update in yakkety
This bug was fixed in the package qtbase-opensource-src - 5.6.1+dfsg- 3ubuntu5~1 --- qtbase-opensource-src (5.6.1+dfsg-3ubuntu5~1) yakkety; urgency=medium * debian/patches/dbusmenu-Don-t-leave-dangling-pointers-when-menus-ar.patch: - Fix a crasher in qdbusmenu code (LP: #1620937) * debian/patches/QMenuBar-Get-rid-of-QMenuBarPrivate-nativeMenuBar.patch: - Improve menu bar code, but for now allow_native_menubar.diff is still needed. -- Timo Jyrinki Fri, 16 Sep 2016 05:08:05 + ** Changed in: qtbase-opensource-src (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1620937 Title: konsole crashes on startup since Qt update in yakkety Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: You can find the valgrind trace at http://paste.ubuntu.com/23144852/ Something wrong seems to be happening in the qdbusmenu code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620937/+subscriptions -- Mailing list: https://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 1624967] Re: $TERM is not set for /etc/rc.local
Sworddragon [2016-09-19 6:52 -]: > But causing some output for example with echo in /etc/rc.local causes it > to be written on the console on booting. Or is this the expected > behavior even if the journal is used? It's what "journal+console" does, yes -- it's similar to "tee". -- 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/1624967 Title: $TERM is not set for /etc/rc.local Status in systemd package in Ubuntu: Invalid Bug description: I'm using Ubuntu 16.10 dev with systemd 231-6 and after upgrading from upstart to systemd I'm noticing that a setterm command fails that I have put into /etc/rc.local in the past (to make specific settings on the console without requiring a login). On making a look at this I figured out that $TERM is not set at default anymore and maybe it makes sense to set it at default again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624967/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
in my /etc/cups/client.conf (now /etc/cups/client.conf_bak) are two lines: ServerName NameoftheremoteCUPSServer ServerName localhost The remote CUPS Server is running Version 1.5.3 and my client 2.0.2. -- 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 1625024] [NEW] Receive phone call, sound via BT speaker by default.
Public bug reported: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 63 device name: krillin channel: ubuntu-touch/rc/bq-aquaris.en last update: 2016-09-05 13:29:03 version version: 63 version ubuntu: 20160903 version tag: OTA-13-rc version device: 20160606-ab415b2 version custom: 20160831-991-38-18 https://prod.practitest.com/p/1548/qtest_runs/5967362/edit Precondition: Connect BT speaker with phone. Step: 1. Call DUT from secondary phone. 2. Receive the phone call 3. Check the sound icon is via BT speaker by default, but the BT speaker isn't support to voice call. Expect result: The call should use phone by default, not the BT speaker. ** Affects: telepathy-ofono (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-ofono in Ubuntu. https://bugs.launchpad.net/bugs/1625024 Title: Receive phone call, sound via BT speaker by default. Status in telepathy-ofono package in Ubuntu: New Bug description: Information: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 63 device name: krillin channel: ubuntu-touch/rc/bq-aquaris.en last update: 2016-09-05 13:29:03 version version: 63 version ubuntu: 20160903 version tag: OTA-13-rc version device: 20160606-ab415b2 version custom: 20160831-991-38-18 https://prod.practitest.com/p/1548/qtest_runs/5967362/edit Precondition: Connect BT speaker with phone. Step: 1. Call DUT from secondary phone. 2. Receive the phone call 3. Check the sound icon is via BT speaker by default, but the BT speaker isn't support to voice call. Expect result: The call should use phone by default, not the BT speaker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1625024/+subscriptions -- Mailing list: https://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 1620937] Re: konsole crashes on startup since Qt update in yakkety
Timo: thanks for the upload! FWIW, allow_native_menubar.diff will be merged upstream as part of https://codereview.qt-project.org/171083. -- 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/1620937 Title: konsole crashes on startup since Qt update in yakkety Status in qtbase-opensource-src package in Ubuntu: Fix Released Bug description: You can find the valgrind trace at http://paste.ubuntu.com/23144852/ Something wrong seems to be happening in the qdbusmenu code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Also affects: ubuntu-touch-meta (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-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in ubuntu-touch-meta package in Ubuntu: New Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594944] Re: Setup.exec() for existing account type results in blank full screen window
No updates, I was waiting for some feedback on the attached branch. I've now put that into https://requests.ci-train.ubuntu.com/#/ticket/1962 Let's see how it goes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1594944 Title: Setup.exec() for existing account type results in blank full screen window Status in Canonical System Image: In Progress Status in webapps-sprint: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Bug description: If an account already exists, calling Setup.exec() again results in a blank window being overlaid on top of the application which made the request. There is no way to close this window. This API is what the online accounts integration in the scopes API relies upon, to allow logging in to accounts, and so we have come to rely upon this API as well in multiple places, as a means to log into the Ubuntu One account, when it is necessary to do so. However, due to this issue, the only way to reliably present a login window at an appropriate time, is to delete the account when it appears to have been invalidated by the server, and to then present the login window to create a new account. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Prebuilt ubuntu-touch meta package that depends on systemd-sysv instead. ** Attachment added: "ubuntu-touch_1.264xenial13_arm64.deb" https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1625023/+attachment/4743479/+files/ubuntu-touch_1.264xenial13_arm64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
Thanks Doug! Ack, I'll change it to use "powersave" again then. ** Changed in: systemd (Ubuntu) Status: Fix Released => In Progress -- 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/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00% native_irq_return_iret | 0.
[Touch-packages] [Bug 1621950] Re: Cpu load 99-100% of Smartscope
I'll look into whether we're doing any unnecessary spinning while retrieving remote scopes. Unfortunately however, we have seen this behaviour before but it seemed to be limited to specific HW+SW configurations (E.g. Bug #1496875). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1621950 Title: Cpu load 99-100% of Smartscope Status in Canonical System Image: Incomplete Status in unity-scopes-api package in Ubuntu: New Bug description: Smartscope always in top (cpu load 99-100%) Meizu MX4 OTA-12 stable top - 22:39:36 up 1 day, 4:15, 1 user, load average: 0.00, 0.01, 0.05 Tasks: 321 total, 13 running, 308 sleeping, 0 stopped, 0 zombie %Cpu0 : 2.9 us, 4.9 sy, 0.0 ni, 92.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu4 : 35.2 us, 64.8 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 1937784 total, 1176564 used, 761220 free,19248 buffers KiB Swap: 524284 total,0 used, 524284 free. 187348 cached Mem 21308 phablet 20 0 380652 7304 5648 S 99.1 0.4 1:09.39 smartscope+ 21324 root 20 06288 1300816 R 3.8 0.1 0:10.33 top 1754 root 20 0 853780 13060 9284 S 1.0 0.7 6:19.79 unity-syst+ 19931 root 10 -10 0 0 0 S 1.0 0.0 0:00.45 rx_thread 21244 root 20 0 0 0 0 S 1.0 0.0 0:02.50 kworker/0:2 1 root 20 03948 2428 1080 S 0.0 0.1 0:26.57 init 2 root 20 0 0 0 0 S 0.0 0.0 0:00.04 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:04.13 ksoftirqd/0 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:+ 7 root -99 0 0 0 0 S 0.0 0.0 0:01.86 migration/0 8 root 20 0 0 0 0 S 0.0 0.0 0:19.10 rcu_preempt 9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh 10 root 20 0 0 0 0 S 0.0 0.0 0:00.32 rcu_sched 11 root -99 0 0 0 0 R 0.0 0.0 0:01.63 migration/1 12 root 20 0 0 0 0 R 0.0 0.0 0:00.82 ksoftirqd/1 14 root 0 -20 0 0 0 S 0.0 0.0 0:00.04 kworker/1:+ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1621950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625035] [NEW] calendar october rwice day 30.
Public bug reported: I just check the calendar and found the attachement. Wierd if October has two day 30. Ubuntu 15.04 OTA-12 on Bq aquaris E5 HD ubuntu ed. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "screenshot20160918_191706767.png" https://bugs.launchpad.net/bugs/1625035/+attachment/4743480/+files/screenshot20160918_191706767.png ** Package changed: upstart-app-launch (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart-app-launch in Ubuntu. https://bugs.launchpad.net/bugs/1625035 Title: calendar october rwice day 30. Status in Ubuntu: New Bug description: I just check the calendar and found the attachement. Wierd if October has two day 30. Ubuntu 15.04 OTA-12 on Bq aquaris E5 HD ubuntu ed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1625035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576942] Re: package python-apt 0.9.3.5ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1576942 Title: package python-apt 0.9.3.5ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in python-apt package in Ubuntu: Confirmed Bug description: i got error after updateing the ubuntu ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-apt 0.9.3.5ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Sat Apr 30 13:52:36 2016 DuplicateSignature: package:python-apt:0.9.3.5ubuntu1:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-04-29 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: python-apt Title: package python-apt 0.9.3.5ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1576942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Append debian build version so that it doesn't confuse dpkg. ** Attachment added: "ubuntu-touch_1.264xenial13+systemd_arm64.deb" https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1625023/+attachment/4743481/+files/ubuntu-touch_1.264xenial13+systemd_arm64.deb ** Attachment removed: "ubuntu-touch_1.264xenial13_arm64.deb" https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1625023/+attachment/4743479/+files/ubuntu-touch_1.264xenial13_arm64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
The #17 kernel has no oops. Network and bridge are brought up after boot, however there is no network connectivity on the bridge. "sudo service networking restart" fixes that and after that everything works. -- 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 Status in bridge-utils source package in Xenial: New Status in linux source package in Xenial: Confirmed Status in bridge-utils source package in Yakkety: New 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+0x21
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Differences between list of packages install upstart and/or systemd service files: # diff -Nu /tmp/upstart-packages.list /tmp/systemd-packages. --- /tmp/upstart-packages.list 2016-09-19 05:55:03.849426548 + +++ /tmp/systemd-packages.list 2016-09-19 05:56:15.139426552 + @@ -1,80 +1,40 @@ -account-polld -address-book-service -address-book-updater +accountsservice alsa-utils -android-tools-adbd -apparmor apport apport-noui -biometryd-bin +apt bluetooth-touch bluez -buteo-syncfw cgmanager -cgroup-lite -ciborium click -console-setup console-setup-linux cron dbus -gnome-keyring -history-service -hostname ifupdown -indicator-bluetooth -indicator-datetime -indicator-display -indicator-keyboard -indicator-location -indicator-messages -indicator-network -indicator-power -indicator-session -indicator-sound -indicator-transfer keyboard-configuration -kmod -libertine-tools -libunity-scopes1.0 lightdm lxc1 lxc-android-config -media-hub -mediascanner2.0 -mountall -mtp-server network-manager -nuntium ofono -openssh-client openssh-server -passwd -pay-service -procps +openvpn +packagekit +plymouth +policykit-1 +ppp repowerd resolvconf -rfkill +rsync rsyslog -session-migration -sync-monitor -telephony-service -tone-generator -ubuntu-app-launch -ubuntu-location-provider-here -ubuntu-location-service-bin -ubuntu-push-client -ubuntu-touch-customization-hooks +rtkit +systemd ubuntu-touch-session udev +udisks2 ufw -unity8 -unity-scope-click-departmentsdb -upstart -upstart-watchdog +upower ureadahead urfkill -url-dispatcher -usensord -util-linux whoopsie +wpasupplicant -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1621950] Re: Cpu load 99-100% of Smartscope
Hmmm... On my SIM card also left internet trafic limit. And maybe when i connect to wifi, CPU load stops. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1621950 Title: Cpu load 99-100% of Smartscope Status in Canonical System Image: Incomplete Status in unity-scopes-api package in Ubuntu: New Bug description: Smartscope always in top (cpu load 99-100%) Meizu MX4 OTA-12 stable top - 22:39:36 up 1 day, 4:15, 1 user, load average: 0.00, 0.01, 0.05 Tasks: 321 total, 13 running, 308 sleeping, 0 stopped, 0 zombie %Cpu0 : 2.9 us, 4.9 sy, 0.0 ni, 92.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st %Cpu4 : 35.2 us, 64.8 sy, 0.0 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 1937784 total, 1176564 used, 761220 free,19248 buffers KiB Swap: 524284 total,0 used, 524284 free. 187348 cached Mem 21308 phablet 20 0 380652 7304 5648 S 99.1 0.4 1:09.39 smartscope+ 21324 root 20 06288 1300816 R 3.8 0.1 0:10.33 top 1754 root 20 0 853780 13060 9284 S 1.0 0.7 6:19.79 unity-syst+ 19931 root 10 -10 0 0 0 S 1.0 0.0 0:00.45 rx_thread 21244 root 20 0 0 0 0 S 1.0 0.0 0:02.50 kworker/0:2 1 root 20 03948 2428 1080 S 0.0 0.1 0:26.57 init 2 root 20 0 0 0 0 S 0.0 0.0 0:00.04 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:04.13 ksoftirqd/0 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:+ 7 root -99 0 0 0 0 S 0.0 0.0 0:01.86 migration/0 8 root 20 0 0 0 0 S 0.0 0.0 0:19.10 rcu_preempt 9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh 10 root 20 0 0 0 0 S 0.0 0.0 0:00.32 rcu_sched 11 root -99 0 0 0 0 R 0.0 0.0 0:01.63 migration/1 12 root 20 0 0 0 0 R 0.0 0.0 0:00.82 ksoftirqd/1 14 root 0 -20 0 0 0 S 0.0 0.0 0:00.04 kworker/1:+ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1621950/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Re: systemd-fsck test started to fail
https://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=614740914
** Changed in: systemd (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624406
Title:
systemd-fsck test started to fail
Status in systemd package in Ubuntu:
Fix Committed
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 1577596] Re: ntpd not started when using ntpdate
Sorry, I missed the link: [1] https://lists.ubuntu.com/archives/ubuntu- devel/2016-August/039484.html ** Changed in: ntp (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate Status in init-system-helpers package in Ubuntu: Confirmed Status in ntp package in Ubuntu: Won't Fix Bug description: After updating from 14.04 to 16.04 on a number of my systems, ntpd no longer starts at boot on any of those systems. `systemctl status ntp` shows: ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon. May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon. Manually starting it using `systemctl start ntp` works fine. However, systemd does not seem to want to start it automatically at boot time. As best as I can tell based on trial and error, there is something special about the combination of the service being named "ntp.service" and the service depending on network.target. However, I haven't been able to identify exactly what is causing this. If I copy the init script to any other name, everything works fine: cp /etc/init.d/ntp /etc/init.d/ntpd Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd" systemctl enable ntpd # After a reboot, ntpd.service is started, but ntp.service is not. If I remove "$network" from the "# Required-Start: $network $remote_fs $syslog" line in /etc/init.d/ntp, then systemd starts it automatically ... But of course it is started before the network comes up, so it fails. If I replace /etc/init.d/ntp with a file containing only the following, systemd won't try to start it automatically at boot: #!/bin/sh ### BEGIN INIT INFO # Provides: ntp # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 4 5 # Default-Stop: 1 # Short-Description: Start NTP daemon ### END INIT INFO echo "script was run" >> /ntp.log If I rename that same dummy script to /etc/init.d/ntp2, it is started automatically at boot. However, grepping the systemd source code and my systemd config files for ntp doesn't seem to find anything that might cause this behavior: /etc/systemd# grep -iR ntp * timesyncd.conf:#NTP= timesyncd.conf:#FallbackNTP=ntp.ubuntu.com /lib/systemd# grep -R ntp * system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd Binary file systemd-networkd matches Binary file systemd-timedated matches Binary file systemd-timesyncd matches What else can I do to debug this further? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577596] Re: ntpd not started when using ntpdate
I think that this belongs to the class of bugs we discussed on ubuntu- devel recently[1]. The summary is: 1. ntpdate is deprecated 2. Various patches got polished, tested and provided to Debian but not yet picked up 3. We are unwilling to add more delta to Debian for a deprecated binary So if they are merged in Debian we will pick it up in the next Release, but unlikely do an SRU for it. Therefore, I'm marking this bug as Won't Fix for the ntp package in Ubuntu, and encourage users to use systemd-timesyncd instead. If there is a fix that doesn't involve adding a delta to Ubuntu for the ntpdate package, then we can do that, however. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate Status in init-system-helpers package in Ubuntu: Confirmed Status in ntp package in Ubuntu: Won't Fix Bug description: After updating from 14.04 to 16.04 on a number of my systems, ntpd no longer starts at boot on any of those systems. `systemctl status ntp` shows: ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon. May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon. Manually starting it using `systemctl start ntp` works fine. However, systemd does not seem to want to start it automatically at boot time. As best as I can tell based on trial and error, there is something special about the combination of the service being named "ntp.service" and the service depending on network.target. However, I haven't been able to identify exactly what is causing this. If I copy the init script to any other name, everything works fine: cp /etc/init.d/ntp /etc/init.d/ntpd Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd" systemctl enable ntpd # After a reboot, ntpd.service is started, but ntp.service is not. If I remove "$network" from the "# Required-Start: $network $remote_fs $syslog" line in /etc/init.d/ntp, then systemd starts it automatically ... But of course it is started before the network comes up, so it fails. If I replace /etc/init.d/ntp with a file containing only the following, systemd won't try to start it automatically at boot: #!/bin/sh ### BEGIN INIT INFO # Provides: ntp # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 4 5 # Default-Stop: 1 # Short-Description: Start NTP daemon ### END INIT INFO echo "script was run" >> /ntp.log If I rename that same dummy script to /etc/init.d/ntp2, it is started automatically at boot. However, grepping the systemd source code and my systemd config files for ntp doesn't seem to find anything that might cause this behavior: /etc/systemd# grep -iR ntp * timesyncd.conf:#NTP= timesyncd.conf:#FallbackNTP=ntp.ubuntu.com /lib/systemd# grep -R ntp * system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd Binary file systemd-networkd matches Binary file systemd-timedated matches Binary file systemd-timesyncd matches What else can I do to debug this further? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1616413] Re: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all
Hi, Sorry for the late reply. Currently, the following are the physical connections to the tower: HDMI connection with monitor, USB connections for keyboard and mouse, and of course the power. I am still not getting any sound either through the built in speakers, or when I plug in headphones. I have attached the log with this file. Thanks for all the help, and please let me know if you need further information. ** Attachment added: "pulseverbose.log" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1616413/+attachment/4743499/+files/pulseverbose.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/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 1625078] [NEW] lxc 2.0.4-0ubuntu3 ADT test failure with linux 4.8.0-11.12
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/l/lxc/20160918_102256@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/i386/l/lxc/20160918_103635@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/l/lxc/20160918_150303@/log.gz ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-4.8 ** Tags added: kernel-4.8 -- 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/1625078 Title: lxc 2.0.4-0ubuntu3 ADT test failure with linux 4.8.0-11.12 Status in lxc package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/l/lxc/20160918_102256@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/i386/l/lxc/20160918_103635@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/l/lxc/20160918_150303@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1625078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625078] Re: lxc 2.0.4-0ubuntu3 ADT test failure with linux 4.8.0-11.12
Seem like a temporary failure when trying to import the `GPG` key. -- 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/1625078 Title: lxc 2.0.4-0ubuntu3 ADT test failure with linux 4.8.0-11.12 Status in lxc package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/l/lxc/20160918_102256@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/i386/l/lxc/20160918_103635@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/l/lxc/20160918_150303@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1625078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625100] [NEW] systemd 231-6 ADT test failure with linux 4.8.0-11.12
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/s/systemd/20160918_093714@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/s/systemd/20160918_231904@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-4.8 ** Tags added: kernel-4.8 -- 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/1625100 Title: systemd 231-6 ADT test failure with linux 4.8.0-11.12 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/s/systemd/20160918_093714@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/s/systemd/20160918_231904@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625095] [NEW] SMS notification only happens after screen is turned on
Public bug reported: Steps: * make sure the phone is in deep sleep * send a text to it Expected: * phone wakes up, notification sound is played and the notification is displayed Current: * nothing, until you turn the screen on * the notification happens immediately after the screen is turned on ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20160909.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Sep 19 11:32:43 2016 InstallationDate: Installed on 2016-09-17 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160917-020305) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: telephony-service (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf vivid ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1625095 Title: SMS notification only happens after screen is turned on Status in Canonical System Image: New Status in telephony-service package in Ubuntu: New Bug description: Steps: * make sure the phone is in deep sleep * send a text to it Expected: * phone wakes up, notification sound is played and the notification is displayed Current: * nothing, until you turn the screen on * the notification happens immediately after the screen is turned on ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20160909.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Sep 19 11:32:43 2016 InstallationDate: Installed on 2016-09-17 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160917-020305) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 987220] Re: [Dell Inspiron 1720] System does not power off reliably when "Shut Down" chosen from GUI
I installed, from pendrive, Ubuntu 16.04 LTS in dell inspiron 1501 (with windows XP), the windows poweroff normally, but ubuntu do not: it goes shutdown apparently normally but finally do not power off the labtop. The last lines reported are: All fylesystems unmounted Deactivating swaps All swaps deactivated Detaching loop devices All loop devices detached Detachig DM devices All DM devices detached Powering off and the labtop do not power off Ther is a significant note in the previous lines before those lines: Process 1043 (plymouthd) has benn marked to be ecluded form killing... I am new and no expert linux -- 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/987220 Title: [Dell Inspiron 1720] System does not power off reliably when "Shut Down" chosen from GUI Status in Session Menu: Invalid Status in gnome-session package in Ubuntu: Invalid Status in indicator-session package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in upstart package in Ubuntu: Invalid Status in gnome-session source package in Precise: Invalid Status in indicator-session source package in Precise: Invalid Status in linux source package in Precise: Confirmed Status in upstart source package in Precise: Invalid Status in Debian: New Bug description: Shutting down the computer using the menue does not work always correct. It often does not complete turn off the computer. The power LED and the LED of the bluetooth unit remain on. Also the fan is still running and won't stop. Shutting down the computer with "sudo shutdown -h now" using the terminal works fine. I am using a Dell Inspiron 1720. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/987220/+subscriptions -- Mailing list: https://launchpad.net/~touch-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: canonical-devices-system-image Status: In Progress => Fix Committed ** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- 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: Fix Released 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 1625023] Re: switch to systemd on ubuntu phone xenial
** Also affects: android-tools (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-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625100] Re: systemd 231-6 ADT test failure with linux 4.8.0-11.12
amd64 failed in "upstream" tests during image preparation: The file /dev/loop4p1 does not exist and no size was specified. F: Failed to mkfs -t ext3 This might be just a rare race condition (I've never seen it). Does it reproduce on retry? ppc64el: - One failure is due to linux-image-extra-4.8.0-11-generic losing scsi_debug (kernel bug) - The other is a regression in tmpfiles: Sep 18 22:23:56 autopkgtest systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=killed, status=11/SEGV That needs to be investigated more closely; the segfault is certainly a systemd bug, presumably a code path now triggered by different kernel behaviour. -- 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/1625100 Title: systemd 231-6 ADT test failure with linux 4.8.0-11.12 Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/s/systemd/20160918_093714@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/s/systemd/20160918_231904@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libunwind (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1590236 Title: perf --call-graph dwarf doesn't record correct call graph Status in libunwind package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Bug description: 1. What you expected to happen Profiling program by "perf --call-graph dwarf" shows correct call-graph in perf report 2. What actually happened perf report doesn't show correct call graph. Then perf is re-builded from source. During building, perf configure detection says stock libunwind's debug_frame feature is not enabled. It leads perf can't record program's call-graph correctly. 3. How it is solved on my local machine a. get libunwind source by apt-get source libunwind-dev. b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && ./configure --enable-debug-frame c. build libunwind and install it to /usr/lib/local d. get kernel source by apt-get source linux and compile perf with following command: CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make e. perf call-graph works! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libunwind-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic aarch64 ApportVersion: 2.20.1-0ubuntu2 Architecture: arm64 Date: Wed Jun 8 03:33:05 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: libunwind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock
Man, this is so annoying! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576424 Title: Gimp crashes with text tool & caps lock Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: Gimp crashes with a segfault when I use caps lock while renaming a layer. Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver (available from the Additional Drivers tab). In that same tab, I also have enabled Processor microcode firmware for Intel CPUs. Terminal tells me Gimp version is 2.8.16-1ubuntu1 I'm not very experienced with bug reporting and not sure what other information I need to supply. Gimp was absolutely rock solid on this machine with 15.10, so it may be a Xubuntu issue. Hope someone can take a look at this. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1576424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625107] [NEW] Xenial overlay PPA: unity8-desktop-session deps conflict with kubuntu-desktop install deps
Public bug reported: Environment: Xenial + Overlay PPA, all packages updated as of 14th Sept 2016 Description: Team's machine. It had unity8-desktop-session installed, I tried installing kubuntu-desktop but that failed. 1) Installed kubuntu-desktop and that removed unity8-desktop-session (I did not notice that in the long list of modifications to packages so I let it go on) 2) Tried getting unity8-desktop-session back and had 2 problems: a) unity-scope-click depends packagekit ---> packagekit can't be installed because python3-aptdaemon.pkcompat Conflicts: packagekit ---> I can't remove python3-aptdaemon.pkcompat because "packagekit-tools Depends: python3-aptdaemon.pkcompat OR packagekit-system-interface OR packagekit" b) /usr/share/accounts/services/google-im.service is owned by both kde- config-telepathy-accounts and accounts-plugin-google which is required by unity-scope-gdrive I fixed this by "apt remove unity-scope-gdrive account-plugin-google kde-telepathy-minimal kde-telepathy" otherwise kubuntu-desktop installation would not even complete After fixing b it let me install unity8-desktop-session warning me that it was uninstalling python3-aptdaemon.pkcompat even though packagekit- tools depends on it ** 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/1625107 Title: Xenial overlay PPA: unity8-desktop-session deps conflict with kubuntu- desktop install deps Status in unity8 package in Ubuntu: New Bug description: Environment: Xenial + Overlay PPA, all packages updated as of 14th Sept 2016 Description: Team's machine. It had unity8-desktop-session installed, I tried installing kubuntu-desktop but that failed. 1) Installed kubuntu-desktop and that removed unity8-desktop-session (I did not notice that in the long list of modifications to packages so I let it go on) 2) Tried getting unity8-desktop-session back and had 2 problems: a) unity-scope-click depends packagekit ---> packagekit can't be installed because python3-aptdaemon.pkcompat Conflicts: packagekit ---> I can't remove python3-aptdaemon.pkcompat because "packagekit- tools Depends: python3-aptdaemon.pkcompat OR packagekit-system- interface OR packagekit" b) /usr/share/accounts/services/google-im.service is owned by both kde-config-telepathy-accounts and accounts-plugin-google which is required by unity-scope-gdrive I fixed this by "apt remove unity-scope-gdrive account-plugin-google kde-telepathy-minimal kde-telepathy" otherwise kubuntu-desktop installation would not even complete After fixing b it let me install unity8-desktop-session warning me that it was uninstalling python3-aptdaemon.pkcompat even though packagekit-tools depends on it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1625107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph
Perf utility from linux-tools is affected for AArch64. ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1590236 Title: perf --call-graph dwarf doesn't record correct call graph Status in libunwind package in Ubuntu: Confirmed Status in linux-meta package in Ubuntu: New Bug description: 1. What you expected to happen Profiling program by "perf --call-graph dwarf" shows correct call-graph in perf report 2. What actually happened perf report doesn't show correct call graph. Then perf is re-builded from source. During building, perf configure detection says stock libunwind's debug_frame feature is not enabled. It leads perf can't record program's call-graph correctly. 3. How it is solved on my local machine a. get libunwind source by apt-get source libunwind-dev. b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && ./configure --enable-debug-frame c. build libunwind and install it to /usr/lib/local d. get kernel source by apt-get source linux and compile perf with following command: CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make e. perf call-graph works! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libunwind-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic aarch64 ApportVersion: 2.20.1-0ubuntu2 Architecture: arm64 Date: Wed Jun 8 03:33:05 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: libunwind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577321] Re: package linux-image-extra-3.16.0-70-generic 3.16.0-70.90~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1577321 Title: package linux-image-extra-3.16.0-70-generic 3.16.0-70.90~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d /initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: uninstall problem ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.16.0-70-generic 3.16.0-70.90~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-71.91~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-71-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 Date: Mon May 2 10:02:49 2016 DuplicateSignature: package:linux-image-extra-3.16.0-70-generic:3.16.0-70.90~14.04.1:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2014-04-18 (744 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.6 apt 1.0.1ubuntu2.13 SourcePackage: initramfs-tools Title: package linux-image-extra-3.16.0-70-generic 3.16.0-70.90~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1577321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph
IMO, the AArch64 libunwind port (included via AArch64-port.diff debian
patch) should be setting enable_debug_frame to "yes" for aarch64
alongside arm in confirure.ac:
AC_MSG_CHECKING([whether to load .debug_frame sections])
AC_ARG_ENABLE(debug_frame,
AS_HELP_STRING([--enable-debug-frame],[Load the ".debug_frame" section if
available]),, [
case "${target_arch}" in
(arm) enable_debug_frame=yes;;
(*) enable_debug_frame=no;;
esac])
if test x$enable_debug_frame = xyes; then
AC_DEFINE([CONFIG_DEBUG_FRAME], [], [Enable Debug Frame])
fi
AC_MSG_RESULT([$enable_debug_frame])
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1590236
Title:
perf --call-graph dwarf doesn't record correct call graph
Status in libunwind package in Ubuntu:
Confirmed
Status in linux-meta package in Ubuntu:
New
Bug description:
1. What you expected to happen
Profiling program by "perf --call-graph dwarf" shows correct call-graph in
perf report
2. What actually happened
perf report doesn't show correct call graph. Then perf is re-builded from
source. During building, perf configure detection says stock libunwind's
debug_frame feature is not enabled. It leads perf can't record program's
call-graph correctly.
3. How it is solved on my local machine
a. get libunwind source by apt-get source libunwind-dev.
b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i &&
./configure --enable-debug-frame
c. build libunwind and install it to /usr/lib/local
d. get kernel source by apt-get source linux and compile perf with
following command:
CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make
e. perf call-graph works!
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libunwind-dev (not installed)
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic aarch64
ApportVersion: 2.20.1-0ubuntu2
Architecture: arm64
Date: Wed Jun 8 03:33:05 2016
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000']
failed with exit code 1: Hint: You are currently not seeing messages from other
users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
SourcePackage: libunwind
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625068] Re: aethercast binaries disappeared from the system
I agree ubuntu-system-settings should just handle seemlessly the existence or non-existence of aethercast on the system (meaning proposition 2.). If u-s-s does not cope well with this package being gone, it should be a Depends instead of a Suggests. But that is a different thing. But that being said, on touch images we *require* aethercast to be installed by default, so it should be added to the seeds. I will take care of that. ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Also affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-touch-meta (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-touch-meta (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625068 Title: aethercast binaries disappeared from the system Status in Canonical System Image: New Status in aethercast package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: In Progress Status in ubuntu-touch-meta package in Ubuntu RTM: In Progress Bug description: After update to 182, the aethercast binaries disappeared from the system, leaving the external display page in system-settings broken. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 182 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en last update: 2016-09-18 20:11:35 version version: 182 version ubuntu: 20160917 version device: 20160824-d33b825 version custom: 20160831-992-8-12 UPDATE: I've been told the change to make aethercast an option suggestion in system-settings caused to not have aethercast pulled in in the image builds. It seems like there are 2 fixes needed: a) Seed aethercast in relevant phone images b) fix system-settings to hide the external display section when aethercast is not around. Currently the button is there but just does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625116] [NEW] RT3290 not working
Public bug reported: My WiFi RT3290 does not work on Ubuntu. Neither I remember it working on any previous version. I don't have good knowledge of command line or linux. But I am using ubuntu as my primary OS. Currently I am using usb wifi adapter to connect to internet. I have followed almost every guide available on internet like downloading driver from mediatek website or someone's dropbox folder and then compiling or changing linux kernels. I don't know why still I can't make it work. I want this device to work out of box for next ubuntu version. Let me know if you need any further information about collecting logs of my system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 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 CurrentDesktop: X-Cinnamon Date: Mon Sep 19 15:45:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-07 (12 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlxaca2131a2daf proto static metric 600 169.254.0.0/16 dev wlxaca2131a2daf scope link metric 1000 192.168.0.0/24 dev wlxaca2131a2daf proto kernel scope link src 192.168.0.109 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlxaca2131a2daf wifi connected /org/freedesktop/NetworkManager/Devices/2 UnitedNepal ff526f85-e18b-4713-ae67-f3fbfa290c4b /org/freedesktop/NetworkManager/ActiveConnection/0 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1625116 Title: RT3290 not working Status in network-manager package in Ubuntu: New Bug description: My WiFi RT3290 does not work on Ubuntu. Neither I remember it working on any previous version. I don't have good knowledge of command line or linux. But I am using ubuntu as my primary OS. Currently I am using usb wifi adapter to connect to internet. I have followed almost every guide available on internet like downloading driver from mediatek website or someone's dropbox folder and then compiling or changing linux kernels. I don't know why still I can't make it work. I want this device to work out of box for next ubuntu version. Let me know if you need any further information about collecting logs of my system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 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 CurrentDesktop: X-Cinnamon Date: Mon Sep 19 15:45:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-07 (12 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlxaca2131a2daf proto static metric 600 169.254.0.0/16 dev wlxaca2131a2daf scope link metric 1000 192.168.0.0/24 dev wlxaca2131a2daf proto kernel scope link src 192.168.0.109 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlxaca2131a2daf wifi connected /org/freedesktop/NetworkManager/Devices/2 UnitedNepal ff526f85-e18b-4713-ae67-f3fbfa290c4b /org/freedesktop/NetworkManager/ActiveConnection/0
[Touch-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph
Status changed to 'Confirmed' because the bug affects multiple users. ** 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 libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1590236 Title: perf --call-graph dwarf doesn't record correct call graph Status in libunwind package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: 1. What you expected to happen Profiling program by "perf --call-graph dwarf" shows correct call-graph in perf report 2. What actually happened perf report doesn't show correct call graph. Then perf is re-builded from source. During building, perf configure detection says stock libunwind's debug_frame feature is not enabled. It leads perf can't record program's call-graph correctly. 3. How it is solved on my local machine a. get libunwind source by apt-get source libunwind-dev. b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && ./configure --enable-debug-frame c. build libunwind and install it to /usr/lib/local d. get kernel source by apt-get source linux and compile perf with following command: CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make e. perf call-graph works! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libunwind-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic aarch64 ApportVersion: 2.20.1-0ubuntu2 Architecture: arm64 Date: Wed Jun 8 03:33:05 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: libunwind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph
** Package changed: linux-meta (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 libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1590236 Title: perf --call-graph dwarf doesn't record correct call graph Status in libunwind package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: 1. What you expected to happen Profiling program by "perf --call-graph dwarf" shows correct call-graph in perf report 2. What actually happened perf report doesn't show correct call graph. Then perf is re-builded from source. During building, perf configure detection says stock libunwind's debug_frame feature is not enabled. It leads perf can't record program's call-graph correctly. 3. How it is solved on my local machine a. get libunwind source by apt-get source libunwind-dev. b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && ./configure --enable-debug-frame c. build libunwind and install it to /usr/lib/local d. get kernel source by apt-get source linux and compile perf with following command: CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make e. perf call-graph works! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libunwind-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic aarch64 ApportVersion: 2.20.1-0ubuntu2 Architecture: arm64 Date: Wed Jun 8 03:33:05 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: libunwind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625128] [NEW] indicator menu should be dismissed when power button is pressed
Public bug reported: Steps to reproduce: 1) have the device locked 2) pull down an indicator (for example, the network one) 3) press the power button (the displays switches off) 4) press the power button on Expected result: I can see the time and infographics. Actual result: the network menu is still there. Usually I use indicator while my phone is locked, typically to turn on or off the network connection, without unlocking the phone. The if after half an hour I want to switch on my phone just to quickly have a look at the time, it's quite annoying to find the indicator menu still there. Note that this behaviour does not happen if you pulled down the indicator when the phone was unlocked: in that case, the indicator menu is correctly dismissed. ** 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/1625128 Title: indicator menu should be dismissed when power button is pressed Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: 1) have the device locked 2) pull down an indicator (for example, the network one) 3) press the power button (the displays switches off) 4) press the power button on Expected result: I can see the time and infographics. Actual result: the network menu is still there. Usually I use indicator while my phone is locked, typically to turn on or off the network connection, without unlocking the phone. The if after half an hour I want to switch on my phone just to quickly have a look at the time, it's quite annoying to find the indicator menu still there. Note that this behaviour does not happen if you pulled down the indicator when the phone was unlocked: in that case, the indicator menu is correctly dismissed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1625128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625107] Re: Xenial overlay PPA: unity8-desktop-session deps conflict with kubuntu-desktop install deps
** Package changed: unity8 (Ubuntu) => unity8-desktop-session (Ubuntu) -- 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/1625107 Title: Xenial overlay PPA: unity8-desktop-session deps conflict with kubuntu- desktop install deps Status in unity8-desktop-session package in Ubuntu: New Bug description: Environment: Xenial + Overlay PPA, all packages updated as of 14th Sept 2016 Description: Team's machine. It had unity8-desktop-session installed, I tried installing kubuntu-desktop but that failed. 1) Installed kubuntu-desktop and that removed unity8-desktop-session (I did not notice that in the long list of modifications to packages so I let it go on) 2) Tried getting unity8-desktop-session back and had 2 problems: a) unity-scope-click depends packagekit ---> packagekit can't be installed because python3-aptdaemon.pkcompat Conflicts: packagekit ---> I can't remove python3-aptdaemon.pkcompat because "packagekit- tools Depends: python3-aptdaemon.pkcompat OR packagekit-system- interface OR packagekit" b) /usr/share/accounts/services/google-im.service is owned by both kde-config-telepathy-accounts and accounts-plugin-google which is required by unity-scope-gdrive I fixed this by "apt remove unity-scope-gdrive account-plugin-google kde-telepathy-minimal kde-telepathy" otherwise kubuntu-desktop installation would not even complete After fixing b it let me install unity8-desktop-session warning me that it was uninstalling python3-aptdaemon.pkcompat even though packagekit-tools depends on it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8-desktop-session/+bug/1625107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625128] Re: indicator menu should be dismissed when power button is pressed
*** This bug is a duplicate of bug 1595569 *** https://bugs.launchpad.net/bugs/1595569 I believe this is a duplicate of bug #1595569 and fixed for OTA13 - please undupe if you can still reproduce in a new image. ** This bug has been marked a duplicate of bug 1595569 Indicators panel doesn't close when turning screen off -- 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/1625128 Title: indicator menu should be dismissed when power button is pressed Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: 1) have the device locked 2) pull down an indicator (for example, the network one) 3) press the power button (the displays switches off) 4) press the power button on Expected result: I can see the time and infographics. Actual result: the network menu is still there. Usually I use indicator while my phone is locked, typically to turn on or off the network connection, without unlocking the phone. The if after half an hour I want to switch on my phone just to quickly have a look at the time, it's quite annoying to find the indicator menu still there. Note that this behaviour does not happen if you pulled down the indicator when the phone was unlocked: in that case, the indicator menu is correctly dismissed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1625128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph
** Also affects: libunwind (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1590236 Title: perf --call-graph dwarf doesn't record correct call graph Status in libunwind package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libunwind source package in Xenial: New Status in linux source package in Xenial: New Bug description: 1. What you expected to happen Profiling program by "perf --call-graph dwarf" shows correct call-graph in perf report 2. What actually happened perf report doesn't show correct call graph. Then perf is re-builded from source. During building, perf configure detection says stock libunwind's debug_frame feature is not enabled. It leads perf can't record program's call-graph correctly. 3. How it is solved on my local machine a. get libunwind source by apt-get source libunwind-dev. b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && ./configure --enable-debug-frame c. build libunwind and install it to /usr/lib/local d. get kernel source by apt-get source linux and compile perf with following command: CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make e. perf call-graph works! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libunwind-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic aarch64 ApportVersion: 2.20.1-0ubuntu2 Architecture: arm64 Date: Wed Jun 8 03:33:05 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: libunwind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380702] Re: No keyboards shortcuts in QT apps
Experiencing this issue with TeXstudio on Ubuntu 16.04. The workaround mentioned in #14 appears to work while we wait for a fix. Thank you all for working on this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1380702 Title: No keyboards shortcuts in QT apps Status in appmenu-qt5: In Progress Status in Canonical System Image: In Progress Status in sni-qt: New Status in qtbase-opensource-src package in Ubuntu: In Progress Bug description: In some apps built using QT4 & 5, menu shortcuts are greyed out and inoperant. Only alt and FKeys-based shortcuts work. Others, notably ctrl+c for copying, do not. This is quite serious ; mail me for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1380702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
I added the PPA and upgraded, but I am still getting this error: "pulseaudio[1800]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to a2dp_sink: Not connected" when I have tried to change from HSP to A2DP. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625137] [NEW] Layouts unit tests fail on Yakkety
Public bug reported: /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2/tests/checkresults.sh /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2/tests/*.xml || exit 1; pep8 /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2 || exit 1; 3 fatal warnings which MUST be fixed: layouts Only warnings, but our shell script checks for warnings and makes them fatal. * Start testing of tst_Layouts * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 6.2.0 20160914) PASS : tst_Layouts::initTestCase() [New Thread 0x7fffe1824700 (LWP 19588)] [New Thread 0x7fffe1023700 (LWP 19589)] [New Thread 0x7fffe0822700 (LWP 19590)] [New Thread 0x7fffe0021700 (LWP 19591)] [New Thread 0x7fffdf820700 (LWP 19592)] [Thread 0x7fffdf820700 (LWP 19592) exited] PASS : tst_Layouts::testCase_NoLayouts() [New Thread 0x7fffdf820700 (LWP 19593)] [Thread 0x7fffdf820700 (LWP 19593) exited] PASS : tst_Layouts::testCase_SimpleLayout() [New Thread 0x7fffdf820700 (LWP 19594)] [Thread 0x7fffdf820700 (LWP 19594) exited] PASS : tst_Layouts::testCase_SimpleLayout_Medium() [New Thread 0x7fffdf820700 (LWP 19595)] [Thread 0x7fffdf820700 (LWP 19595) exited] PASS : tst_Layouts::testCase_SimpleLayout_Large() [New Thread 0x7fffdf820700 (LWP 19596)] [Thread 0x7fffdf820700 (LWP 19596) exited] PASS : tst_Layouts::testCase_OverlappingCondition() [New Thread 0x7fffdf820700 (LWP 19597)] [Thread 0x7fffdf820700 (LWP 19597) exited] PASS : tst_Layouts::testCase_ExternalLayouts() [New Thread 0x7fffdf820700 (LWP 19598)] [Thread 0x7fffdf820700 (LWP 19598) exited] PASS : tst_Layouts::testCase_ExternalLayouts_Medium() [New Thread 0x7fffdf820700 (LWP 19599)] [Thread 0x7fffdf820700 (LWP 19599) exited] PASS : tst_Layouts::testCase_ExternalLayouts_Large() [New Thread 0x7fffdf820700 (LWP 19600)] [Thread 0x7fffdf820700 (LWP 19600) exited] PASS : tst_Layouts::testCase_NestedLayouts() [New Thread 0x7fffdf820700 (LWP 19601)] [Thread 0x7fffdf820700 (LWP 19601) exited] PASS : tst_Layouts::testCase_NestedLayouts_ExtraLarge() [New Thread 0x7fffdf820700 (LWP 19602)] [Thread 0x7fffdf820700 (LWP 19602) exited] PASS : tst_Layouts::testCase_ResizingContainers() [New Thread 0x7fffdf820700 (LWP 19603)] XFAIL : tst_Layouts::testCase_CurrentLayoutChange() Layout change should not happen when component is not defined Loc: [tst_layouts.cpp(387)] [Thread 0x7fffdf820700 (LWP 19603) exited] PASS : tst_Layouts::testCase_CurrentLayoutChange() [New Thread 0x7fffdf820700 (LWP 19604)] XFAIL : tst_Layouts::testCase_PositioningOnLayoutChange() Layout change should not happen when component is not defined Loc: [tst_layouts.cpp(408)] [Thread 0x7fffdf820700 (LWP 19604) exited] PASS : tst_Layouts::testCase_PositioningOnLayoutChange() [New Thread 0x7fffdf820700 (LWP 19605)] [Thread 0x7fffdf820700 (LWP 19605) exited] PASS : tst_Layouts::testCase_LaidOutItemsOutsideOfLayout() [New Thread 0x7fffdf820700 (LWP 19606)] [Thread 0x7fffdf820700 (LWP 19606) exited] PASS : tst_Layouts::testCase_OverlaidInItemLayout() [New Thread 0x7fffdf820700 (LWP 19607)] [Thread 0x7fffdf820700 (LWP 19607) exited] PASS : tst_Layouts::testCase_AnchorFilledReparenting() [New Thread 0x7fffdf820700 (LWP 19608)] [Thread 0x7fffdf820700 (LWP 19608) exited] PASS : tst_Layouts::testCase_AnchorFilledMargins() [New Thread 0x7fffdf820700 (LWP 19609)] [Thread 0x7fffdf820700 (LWP 19609) exited] PASS : tst_Layouts::testCase_AnchorFilledSeparateMargins() [New Thread 0x7fffdf820700 (LWP 19610)] [Thread 0x7fffdf820700 (LWP 19610) exited] PASS : tst_Layouts::testCase_AnchorCenteredInDefault() [New Thread 0x7fffdf820700 (LWP 19611)] [Thread 0x7fffdf820700 (LWP 19611) exited] PASS : tst_Layouts::testCase_AnchorVerticalCenter() [New Thread 0x7fffdf820700 (LWP 19612)] [Thread 0x7fffdf820700 (LWP 19612) exited] PASS : tst_Layouts::testCase_AnchorVerticalCenterOffset() [New Thread 0x7fffdf820700 (LWP 19613)] [Thread 0x7fffdf820700 (LWP 19613) exited] PASS : tst_Layouts::testCase_AnchorHorizontalCenter() [New Thread 0x7fffdf820700 (LWP 19614)] [Thread 0x7fffdf820700 (LWP 19614) exited] PASS : tst_Layouts::testCase_AnchorHorizontalCenterOffset() [New Thread 0x7fffdf820700 (LWP 19615)] [Thread 0x7fffdf820700 (LWP 19615) exited] PASS : tst_Layouts::testCase_AnchorCenterWithOffset() [New Thread 0x7fffdf820700 (LWP 19616)] [Thread 0x7fffdf820700 (LWP 19616) exited] PASS : tst_Layouts::testCase_AnchorLeft() [New Thread 0x7fffdf820700 (LWP 19617)] [Thread 0x7fffdf820700 (LWP 19617) exited] PASS : tst_Layouts::testCase_AnchorTop() [New Thread 0x7fffdf820700 (LWP 19618)] [Thread 0x7fffdf820700 (LWP 19618) exited] PASS : tst_Layouts::testCase_AnchorRight() [New Thread 0x7fffdf820700 (LWP 19619)] [Thread 0x7fffdf820700 (LWP 19619) exited] PASS : tst_Layouts::testCase_AnchorBottom() [New Thread 0x7fffdf820700 (LWP 19620)] [Thread 0x7fffdf820700 (LWP 19620) exited] PASS : tst_Layouts::testCase_AnchorAll() [New T
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
pitti, can we please have a config option to disable "ondemand"? As originally reported, one some workloads, it seems setting to powersave/ondemand causes high load with CPUs checking to see if they need to enter powersave state. While the original report included perf report for the acpi-cpufreq driver, it was also seen with intel_pstate (and was why we decided to try switch to acpi-cpufreq). -- 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/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpui
[Touch-packages] [Bug 1625137] Re: Layouts unit tests fail on Yakkety
A lot of other tests also have the libpng warnings, but it seems they are not fatal there. -- 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/1625137 Title: Layouts unit tests fail on Yakkety Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2/tests/checkresults.sh /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2/tests/*.xml || exit 1; pep8 /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2 || exit 1; 3 fatal warnings which MUST be fixed: layouts Only warnings, but our shell script checks for warnings and makes them fatal. * Start testing of tst_Layouts * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 6.2.0 20160914) PASS : tst_Layouts::initTestCase() [New Thread 0x7fffe1824700 (LWP 19588)] [New Thread 0x7fffe1023700 (LWP 19589)] [New Thread 0x7fffe0822700 (LWP 19590)] [New Thread 0x7fffe0021700 (LWP 19591)] [New Thread 0x7fffdf820700 (LWP 19592)] [Thread 0x7fffdf820700 (LWP 19592) exited] PASS : tst_Layouts::testCase_NoLayouts() [New Thread 0x7fffdf820700 (LWP 19593)] [Thread 0x7fffdf820700 (LWP 19593) exited] PASS : tst_Layouts::testCase_SimpleLayout() [New Thread 0x7fffdf820700 (LWP 19594)] [Thread 0x7fffdf820700 (LWP 19594) exited] PASS : tst_Layouts::testCase_SimpleLayout_Medium() [New Thread 0x7fffdf820700 (LWP 19595)] [Thread 0x7fffdf820700 (LWP 19595) exited] PASS : tst_Layouts::testCase_SimpleLayout_Large() [New Thread 0x7fffdf820700 (LWP 19596)] [Thread 0x7fffdf820700 (LWP 19596) exited] PASS : tst_Layouts::testCase_OverlappingCondition() [New Thread 0x7fffdf820700 (LWP 19597)] [Thread 0x7fffdf820700 (LWP 19597) exited] PASS : tst_Layouts::testCase_ExternalLayouts() [New Thread 0x7fffdf820700 (LWP 19598)] [Thread 0x7fffdf820700 (LWP 19598) exited] PASS : tst_Layouts::testCase_ExternalLayouts_Medium() [New Thread 0x7fffdf820700 (LWP 19599)] [Thread 0x7fffdf820700 (LWP 19599) exited] PASS : tst_Layouts::testCase_ExternalLayouts_Large() [New Thread 0x7fffdf820700 (LWP 19600)] [Thread 0x7fffdf820700 (LWP 19600) exited] PASS : tst_Layouts::testCase_NestedLayouts() [New Thread 0x7fffdf820700 (LWP 19601)] [Thread 0x7fffdf820700 (LWP 19601) exited] PASS : tst_Layouts::testCase_NestedLayouts_ExtraLarge() [New Thread 0x7fffdf820700 (LWP 19602)] [Thread 0x7fffdf820700 (LWP 19602) exited] PASS : tst_Layouts::testCase_ResizingContainers() [New Thread 0x7fffdf820700 (LWP 19603)] XFAIL : tst_Layouts::testCase_CurrentLayoutChange() Layout change should not happen when component is not defined Loc: [tst_layouts.cpp(387)] [Thread 0x7fffdf820700 (LWP 19603) exited] PASS : tst_Layouts::testCase_CurrentLayoutChange() [New Thread 0x7fffdf820700 (LWP 19604)] XFAIL : tst_Layouts::testCase_PositioningOnLayoutChange() Layout change should not happen when component is not defined Loc: [tst_layouts.cpp(408)] [Thread 0x7fffdf820700 (LWP 19604) exited] PASS : tst_Layouts::testCase_PositioningOnLayoutChange() [New Thread 0x7fffdf820700 (LWP 19605)] [Thread 0x7fffdf820700 (LWP 19605) exited] PASS : tst_Layouts::testCase_LaidOutItemsOutsideOfLayout() [New Thread 0x7fffdf820700 (LWP 19606)] [Thread 0x7fffdf820700 (LWP 19606) exited] PASS : tst_Layouts::testCase_OverlaidInItemLayout() [New Thread 0x7fffdf820700 (LWP 19607)] [Thread 0x7fffdf820700 (LWP 19607) exited] PASS : tst_Layouts::testCase_AnchorFilledReparenting() [New Thread 0x7fffdf820700 (LWP 19608)] [Thread 0x7fffdf820700 (LWP 19608) exited] PASS : tst_Layouts::testCase_AnchorFilledMargins() [New Thread 0x7fffdf820700 (LWP 19609)] [Thread 0x7fffdf820700 (LWP 19609) exited] PASS : tst_Layouts::testCase_AnchorFilledSeparateMargins() [New Thread 0x7fffdf820700 (LWP 19610)] [Thread 0x7fffdf820700 (LWP 19610) exited] PASS : tst_Layouts::testCase_AnchorCenteredInDefault() [New Thread 0x7fffdf820700 (LWP 19611)] [Thread 0x7fffdf820700 (LWP 19611) exited] PASS : tst_Layouts::testCase_AnchorVerticalCenter() [New Thread 0x7fffdf820700 (LWP 19612)] [Thread 0x7fffdf820700 (LWP 19612) exited] PASS : tst_Layouts::testCase_AnchorVerticalCenterOffset() [New Thread 0x7fffdf820700 (LWP 19613)] [Thread 0x7fffdf820700 (LWP 19613) exited] PASS : tst_Layouts::testCase_AnchorHorizontalCenter() [New Thread 0x7fffdf820700 (LWP 19614)] [Thread 0x7fffdf820700 (LWP 19614) exited] PASS : tst_Layouts::testCase_AnchorHorizontalCenterOffset() [New Thread 0x7fffdf820700 (LWP 19615)] [Thread 0x7fffdf820700 (LWP 19615) exited] PASS : tst_Layouts::testCase_AnchorCenterWithOffset() [New Thread 0x7fffdf820700 (LWP 19616)] [Thread 0x7fffdf820700 (LWP 19616) exited] P
[Touch-packages] [Bug 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()
Please test from https://requests.ci-train.ubuntu.com/#/ticket/1960 and report back - builds are complete now. -- 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/1618590 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1618590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590236] Re: perf --call-graph dwarf doesn't record correct call graph
We may need to rebuild perf after libunwind is rebuilt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1590236 Title: perf --call-graph dwarf doesn't record correct call graph Status in libunwind package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in libunwind source package in Xenial: New Status in linux source package in Xenial: New Bug description: 1. What you expected to happen Profiling program by "perf --call-graph dwarf" shows correct call-graph in perf report 2. What actually happened perf report doesn't show correct call graph. Then perf is re-builded from source. During building, perf configure detection says stock libunwind's debug_frame feature is not enabled. It leads perf can't record program's call-graph correctly. 3. How it is solved on my local machine a. get libunwind source by apt-get source libunwind-dev. b. enable CONFIG_DEBUG_FRAME in libunwind configuration: autoreconfig -i && ./configure --enable-debug-frame c. build libunwind and install it to /usr/lib/local d. get kernel source by apt-get source linux and compile perf with following command: CFLAGS=-I/usr/local/include/ LDFLAGS="-lunwind -L/usr/local/lib/" make e. perf call-graph works! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libunwind-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic aarch64 ApportVersion: 2.20.1-0ubuntu2 Architecture: arm64 Date: Wed Jun 8 03:33:05 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: libunwind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1590236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1609003] Re: tty users logouts not correctly recorded
** Description changed: 1) Release: Ubuntu Gnome 14.04.4 and Xubuntu 14.04.4 2) Version of package: util-linux 2.20.1-5.1ubuntu20.7 3) I would expect that: when a user makes a new login, the number of "users" shown in uptime and w is incremented, and when the user makes a logout that number is decremented. 4) Instead, this does not happen when the login is made through a local tty. If a user logs in through a ttyx (by pressing from the GUI Ctrl+Alt+Fx), and then logs out, the number of users shown in the outputs of w and uptime still considers him. This number of users (shown in w and uptime) is in fact always incremented when a new ttyx with a successful login is used; but it is never decremented when that user logs out (unless there is a reboot, obviously). After a login from just the GUI, the system is: $ uptime 17:16:09 up 7:05, 1 users, load average: 0,43, 0,50, 0,38 $ who user :0 2016-08-02 10:21 (:0) Then I press Ctrl+Alt+F1 and I log in into /dev/tty1. While I'm logged in, it is correctly shown that $ uptime 17:21:09 up 7:05, 2 users, load average: 0,40, 0,20, 0,31 $ who - lgking :0 2016-08-02 10:21 (:0) - lgking tty1 2016-08-02 10:25 + user :0 2016-08-02 10:21 (:0) + user tty1 2016-08-02 10:25 Then I log out from tty1. The situation is the following: $ uptime 17:26:09 up 7:05, 2 users, load average: 0,35, 0,21, 0,32 $ who user :0 2016-08-02 10:21 (:0) So the output of who is correct, but uptime still indicates 2 users logged in the system. The same happens with w, which indicates 2 users connected, but then lists just one of them (the only one actually connected!). The numbers and the times are just an example. Maybe the getty is not working properly with utmp? This systematically happened in two different machines, with Ubuntu Gnome 14.04.4 and Xubuntu 14.04.4. I didn't check the box, but this may be a security vulnerability, because it shows in a wrong way the number of connected users. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: util-linux 2.20.1-5.1ubuntu20.7 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 2 17:24:49 2016 InstallationDate: Installed on 2014-05-31 (794 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1609003 Title: tty users logouts not correctly recorded Status in util-linux package in Ubuntu: Confirmed Bug description: 1) Release: Ubuntu Gnome 14.04.4 and Xubuntu 14.04.4 2) Version of package: util-linux 2.20.1-5.1ubuntu20.7 3) I would expect that: when a user makes a new login, the number of "users" shown in uptime and w is incremented, and when the user makes a logout that number is decremented. 4) Instead, this does not happen when the login is made through a local tty. If a user logs in through a ttyx (by pressing from the GUI Ctrl+Alt+Fx), and then logs out, the number of users shown in the outputs of w and uptime still considers him. This number of users (shown in w and uptime) is in fact always incremented when a new ttyx with a successful login is used; but it is never decremented when that user logs out (unless there is a reboot, obviously). After a login from just the GUI, the system is: $ uptime 17:16:09 up 7:05, 1 users, load average: 0,43, 0,50, 0,38 $ who user :0 2016-08-02 10:21 (:0) Then I press Ctrl+Alt+F1 and I log in into /dev/tty1. While I'm logged in, it is correctly shown that $ uptime 17:21:09 up 7:05, 2 users, load average: 0,40, 0,20, 0,31 $ who user :0 2016-08-02 10:21 (:0) user tty1 2016-08-02 10:25 Then I log out from tty1. The situation is the following: $ uptime 17:26:09 up 7:05, 2 users, load average: 0,35, 0,21, 0,32 $ who user :0 2016-08-02 10:21 (:0) So the output of who is correct, but uptime still indicates 2 users logged in the system. The same happens with w, which indicates 2 users connected, but then lists just one of them (the only one actually connected!). The numbers and the times are just an example. Maybe the getty is not working properly with utmp? This systematically happened in two different machines, with Ubuntu Gnome 14.04.4 and Xubuntu 14.04.4. I didn't check the box, but this may be a security vulnerability, because it s
[Touch-packages] [Bug 1625137] Re: Layouts unit tests fail on Yakkety
I temporarily disable the test here https://code.launchpad.net/~tpeeters /ubuntu-ui-toolkit/disable-layouts-tests/+merge/306077 ** 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/1625137 Title: Layouts unit tests fail on Yakkety Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2/tests/checkresults.sh /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2/tests/*.xml || exit 1; pep8 /«BUILDDIR»/ubuntu-ui-toolkit-1.3.2104+16.10.20160919.2 || exit 1; 3 fatal warnings which MUST be fixed: layouts Only warnings, but our shell script checks for warnings and makes them fatal. * Start testing of tst_Layouts * Config: Using QtTest library 5.6.1, Qt 5.6.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 6.2.0 20160914) PASS : tst_Layouts::initTestCase() [New Thread 0x7fffe1824700 (LWP 19588)] [New Thread 0x7fffe1023700 (LWP 19589)] [New Thread 0x7fffe0822700 (LWP 19590)] [New Thread 0x7fffe0021700 (LWP 19591)] [New Thread 0x7fffdf820700 (LWP 19592)] [Thread 0x7fffdf820700 (LWP 19592) exited] PASS : tst_Layouts::testCase_NoLayouts() [New Thread 0x7fffdf820700 (LWP 19593)] [Thread 0x7fffdf820700 (LWP 19593) exited] PASS : tst_Layouts::testCase_SimpleLayout() [New Thread 0x7fffdf820700 (LWP 19594)] [Thread 0x7fffdf820700 (LWP 19594) exited] PASS : tst_Layouts::testCase_SimpleLayout_Medium() [New Thread 0x7fffdf820700 (LWP 19595)] [Thread 0x7fffdf820700 (LWP 19595) exited] PASS : tst_Layouts::testCase_SimpleLayout_Large() [New Thread 0x7fffdf820700 (LWP 19596)] [Thread 0x7fffdf820700 (LWP 19596) exited] PASS : tst_Layouts::testCase_OverlappingCondition() [New Thread 0x7fffdf820700 (LWP 19597)] [Thread 0x7fffdf820700 (LWP 19597) exited] PASS : tst_Layouts::testCase_ExternalLayouts() [New Thread 0x7fffdf820700 (LWP 19598)] [Thread 0x7fffdf820700 (LWP 19598) exited] PASS : tst_Layouts::testCase_ExternalLayouts_Medium() [New Thread 0x7fffdf820700 (LWP 19599)] [Thread 0x7fffdf820700 (LWP 19599) exited] PASS : tst_Layouts::testCase_ExternalLayouts_Large() [New Thread 0x7fffdf820700 (LWP 19600)] [Thread 0x7fffdf820700 (LWP 19600) exited] PASS : tst_Layouts::testCase_NestedLayouts() [New Thread 0x7fffdf820700 (LWP 19601)] [Thread 0x7fffdf820700 (LWP 19601) exited] PASS : tst_Layouts::testCase_NestedLayouts_ExtraLarge() [New Thread 0x7fffdf820700 (LWP 19602)] [Thread 0x7fffdf820700 (LWP 19602) exited] PASS : tst_Layouts::testCase_ResizingContainers() [New Thread 0x7fffdf820700 (LWP 19603)] XFAIL : tst_Layouts::testCase_CurrentLayoutChange() Layout change should not happen when component is not defined Loc: [tst_layouts.cpp(387)] [Thread 0x7fffdf820700 (LWP 19603) exited] PASS : tst_Layouts::testCase_CurrentLayoutChange() [New Thread 0x7fffdf820700 (LWP 19604)] XFAIL : tst_Layouts::testCase_PositioningOnLayoutChange() Layout change should not happen when component is not defined Loc: [tst_layouts.cpp(408)] [Thread 0x7fffdf820700 (LWP 19604) exited] PASS : tst_Layouts::testCase_PositioningOnLayoutChange() [New Thread 0x7fffdf820700 (LWP 19605)] [Thread 0x7fffdf820700 (LWP 19605) exited] PASS : tst_Layouts::testCase_LaidOutItemsOutsideOfLayout() [New Thread 0x7fffdf820700 (LWP 19606)] [Thread 0x7fffdf820700 (LWP 19606) exited] PASS : tst_Layouts::testCase_OverlaidInItemLayout() [New Thread 0x7fffdf820700 (LWP 19607)] [Thread 0x7fffdf820700 (LWP 19607) exited] PASS : tst_Layouts::testCase_AnchorFilledReparenting() [New Thread 0x7fffdf820700 (LWP 19608)] [Thread 0x7fffdf820700 (LWP 19608) exited] PASS : tst_Layouts::testCase_AnchorFilledMargins() [New Thread 0x7fffdf820700 (LWP 19609)] [Thread 0x7fffdf820700 (LWP 19609) exited] PASS : tst_Layouts::testCase_AnchorFilledSeparateMargins() [New Thread 0x7fffdf820700 (LWP 19610)] [Thread 0x7fffdf820700 (LWP 19610) exited] PASS : tst_Layouts::testCase_AnchorCenteredInDefault() [New Thread 0x7fffdf820700 (LWP 19611)] [Thread 0x7fffdf820700 (LWP 19611) exited] PASS : tst_Layouts::testCase_AnchorVerticalCenter() [New Thread 0x7fffdf820700 (LWP 19612)] [Thread 0x7fffdf820700 (LWP 19612) exited] PASS : tst_Layouts::testCase_AnchorVerticalCenterOffset() [New Thread 0x7fffdf820700 (LWP 19613)] [Thread 0x7fffdf820700 (LWP 19613) exited] PASS : tst_Layouts::testCase_AnchorHorizontalCenter() [New Thread 0x7fffdf820700 (LWP 19614)] [Thread 0x7fffdf820700 (LWP 19614) exited] PASS : tst_Layouts::testCase_AnchorHorizontalCenterOffset() [New Thread 0x7fffdf820700 (LWP 19615)] [Thread 0x7fffdf820700 (LWP 19615) exited] PASS : tst_Layouts::testCase_AnchorCenterWithOffset() [New Thread 0x7fffdf820700 (L
[Touch-packages] [Bug 1625095] Re: SMS notification only happens after screen is turned on
I often experience the same issue with Telegram notifications. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1625095 Title: SMS notification only happens after screen is turned on Status in Canonical System Image: New Status in telephony-service package in Ubuntu: Confirmed Bug description: Steps: * make sure the phone is in deep sleep * send a text to it Expected: * phone wakes up, notification sound is played and the notification is displayed Current: * nothing, until you turn the screen on * the notification happens immediately after the screen is turned on ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20160909.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Sep 19 11:32:43 2016 InstallationDate: Installed on 2016-09-17 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160917-020305) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625095] Re: SMS notification only happens after screen is turned on
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telephony-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1625095 Title: SMS notification only happens after screen is turned on Status in Canonical System Image: New Status in telephony-service package in Ubuntu: Confirmed Bug description: Steps: * make sure the phone is in deep sleep * send a text to it Expected: * phone wakes up, notification sound is played and the notification is displayed Current: * nothing, until you turn the screen on * the notification happens immediately after the screen is turned on ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20160909.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Sep 19 11:32:43 2016 InstallationDate: Installed on 2016-09-17 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160917-020305) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1008050] Re: After resume from suspend, power-indicator is unaware of battery changes
I'm having this issue - however unplugging the charging cable immediately updates the correct percentage. I'm running Ubuntu 16.04 LTS and I've put in some Unity tweaks, but this shouldn't matter. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1008050 Title: After resume from suspend, power-indicator is unaware of battery changes Status in indicator-power: Incomplete Status in indicator-power package in Ubuntu: Incomplete Status in upower package in Ubuntu: Confirmed Bug description: When resuming from suspend, power-indicator seems to be frozen. Remaining time is not updated, even if I (un)plug AC. Only way to restore normal operation without reboot is to start gnome- power-manager... the indicator becomes responsive again. Probably related to https://bugs.launchpad.net/indicator- power/+bug/983928 and/or https://bugs.launchpad.net/indicator- power/+bug/994745 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1008050/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625095] Re: SMS notification only happens after screen is turned on
Possibly duplicate of bug #1516696 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1625095 Title: SMS notification only happens after screen is turned on Status in Canonical System Image: New Status in telephony-service package in Ubuntu: Confirmed Bug description: Steps: * make sure the phone is in deep sleep * send a text to it Expected: * phone wakes up, notification sound is played and the notification is displayed Current: * nothing, until you turn the screen on * the notification happens immediately after the screen is turned on ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20160909.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Sep 19 11:32:43 2016 InstallationDate: Installed on 2016-09-17 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160917-020305) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625095] Re: SMS notification only happens after screen is turned on
*** This bug is a duplicate of bug 1516696 *** https://bugs.launchpad.net/bugs/1516696 Yeah thanks, I couldn't find the original bug. ** This bug has been marked a duplicate of bug 1516696 SMS notifications are received only when the phone is unlocked -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1625095 Title: SMS notification only happens after screen is turned on Status in Canonical System Image: New Status in telephony-service package in Ubuntu: Confirmed Bug description: Steps: * make sure the phone is in deep sleep * send a text to it Expected: * phone wakes up, notification sound is played and the notification is displayed Current: * nothing, until you turn the screen on * the notification happens immediately after the screen is turned on ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: telephony-service 0.1+15.04.20160909.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf Date: Mon Sep 19 11:32:43 2016 InstallationDate: Installed on 2016-09-17 (2 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160917-020305) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516696] Re: SMS notifications are received only when the phone is unlocked
** Changed in: canonical-devices-system-image Status: Incomplete => Confirmed ** Changed in: canonical-devices-system-image Assignee: Michał Sawicz (saviq) => Alejandro J. Cura (alecu) ** Changed in: canonical-devices-system-image Milestone: None => backlog ** Also affects: telephony-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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1516696 Title: SMS notifications are received only when the phone is unlocked Status in Canonical System Image: Confirmed Status in powerd: New Status in Unity System Compositor: New Status in indicator-messages package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: WHAT HAPPENED: The phone stays quiet while locked but once the power button is pressed (unlocked), SMS notification are received with vibration, notification bubble and sound alert. The message received shows that it was actually received 10 minutes ago. This happened multiple times already but I think I ignored them and this seems to have started after OTA-7 was released. EXPECTED: The phone should have the vibration, notification bubble/indicator and sound alert even if the phone is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1516696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625150] [NEW] Add account-polld-plugins-go to unity8-based images
Public bug reported: The account-polld package is already included in the phone images; however, I have a silo [1] in which I'm completely rewriting the project, and splitting all the go-based plugins into a separate new project called account-polld-plugins-go. This contains the plugins for checking gmail, twitter, Google calendar in the background. It depends on account-polld, and account-polld recommends this package (turning that into a "Depends" would create a cyclic dependency and be anyway wrong, as account-polld can live well without this package). That's why I'm asking for this package to be included in the image, once the silo lands. [1] https://requests.ci-train.ubuntu.com/#/ticket/1924 ** Affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Assignee: Łukasz Zemczak (sil2100) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625150 Title: Add account-polld-plugins-go to unity8-based images Status in ubuntu-touch-meta package in Ubuntu: New Bug description: The account-polld package is already included in the phone images; however, I have a silo [1] in which I'm completely rewriting the project, and splitting all the go-based plugins into a separate new project called account-polld-plugins-go. This contains the plugins for checking gmail, twitter, Google calendar in the background. It depends on account-polld, and account-polld recommends this package (turning that into a "Depends" would create a cyclic dependency and be anyway wrong, as account-polld can live well without this package). That's why I'm asking for this package to be included in the image, once the silo lands. [1] https://requests.ci-train.ubuntu.com/#/ticket/1924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1625150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625149] Re: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
*** This bug is a duplicate of bug 1621396 *** https://bugs.launchpad.net/bugs/1621396 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1621396, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1625149/+attachment/4743587/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1625149/+attachment/4743590/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1625149/+attachment/4743597/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1625149/+attachment/4743599/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1625149/+attachment/4743600/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1625149/+attachment/4743601/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1625149/+attachment/4743604/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1621396 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1625149 Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() Status in systemd package in Ubuntu: New Bug description: issue at system startup ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-6 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 CrashCounter: 1 Date: Mon Sep 19 09:58:36 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1200 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x55de8b868257:cmpl $0x1,0x4(%rax) PC (0x55de8b868257) ok source "$0x1" ok destination "0x4(%rax)" (0x0004) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (16 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Felipe: have you tried reboot and remove and add the device again? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625068] Re: aethercast binaries disappeared from the system
** Changed in: ubuntu-touch-meta (Ubuntu) Status: In Progress => Fix Committed ** Changed in: ubuntu-touch-meta (Ubuntu RTM) 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-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625068 Title: aethercast binaries disappeared from the system Status in Canonical System Image: New Status in aethercast package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Fix Committed Status in ubuntu-touch-meta package in Ubuntu RTM: Fix Committed Bug description: After update to 182, the aethercast binaries disappeared from the system, leaving the external display page in system-settings broken. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 182 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en last update: 2016-09-18 20:11:35 version version: 182 version ubuntu: 20160917 version device: 20160824-d33b825 version custom: 20160831-992-8-12 UPDATE: I've been told the change to make aethercast an option suggestion in system-settings caused to not have aethercast pulled in in the image builds. It seems like there are 2 fixes needed: a) Seed aethercast in relevant phone images b) fix system-settings to hide the external display section when aethercast is not around. Currently the button is there but just does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
With https://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?id=94a70093 it uses powersave on intel_pstate again, like in xenial. > pitti, can we please have a config option to disable "ondemand"? Indeed, right now it is statically enabled, so it can only be disabled with "systemctl mask ondemand". I'll make it dynamically enabled so that it can be disabled with the usual systemctl enable/disable. -- 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/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi |
[Touch-packages] [Bug 1612460] Re: [MIR] unity-scopes-shell
Could it be reviewed from silo 73 it's getting tight for 16.10 so would be better to get the feedback without having to wait for the landing to be through ** Changed in: unity-scopes-shell (Ubuntu) Status: Incomplete => New -- 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/1612460 Title: [MIR] unity-scopes-shell Status in unity-scopes-shell package in Ubuntu: New Bug description: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues [Quality assurance] * This package has unit tests [Dependencies] * [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/ubuntu/+source/unity-scopes-shell/+bug/1612460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625068] Re: aethercast binaries disappeared from the system
This bug was fixed in the package ubuntu-touch-meta 1.221vivid46 in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable- phone-overlay --- ubuntu-touch-meta (1.221vivid46) vivid; urgency=medium * Added aethercast to touch (LP: #1625068) -- Łukasz 'sil2100' Zemczak Mon, 19 Sep 2016 13:50:42 +0200 ** Changed in: ubuntu-touch-meta (Ubuntu RTM) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625068 Title: aethercast binaries disappeared from the system Status in Canonical System Image: New Status in aethercast package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Fix Committed Status in ubuntu-touch-meta package in Ubuntu RTM: Fix Released Bug description: After update to 182, the aethercast binaries disappeared from the system, leaving the external display page in system-settings broken. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 182 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en last update: 2016-09-18 20:11:35 version version: 182 version ubuntu: 20160917 version device: 20160824-d33b825 version custom: 20160831-992-8-12 UPDATE: I've been told the change to make aethercast an option suggestion in system-settings caused to not have aethercast pulled in in the image builds. It seems like there are 2 fixes needed: a) Seed aethercast in relevant phone images b) fix system-settings to hide the external display section when aethercast is not around. Currently the button is there but just does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612461] Re: [MIR] unity-scopes-api
** Changed in: unity-scopes-api (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1612461 Title: [MIR] unity-scopes-api Status in unity-scopes-api package in Ubuntu: New Bug description: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues [Quality assurance] * This package has unit tests [Dependencies] * [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/ubuntu/+source/unity-scopes-api/+bug/1612461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612270] Re: [MIR] qdjango
** Changed in: qdjango (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qdjango in Ubuntu. https://bugs.launchpad.net/bugs/1612270 Title: [MIR] qdjango Status in qdjango package in Ubuntu: New Bug description: [Availability] * Available in universe [Rationale] * This package is required by unity8 infographics [Security] * No known security issues at this time. [Quality assurance] * This package has unit tests. [Dependencies] All dependencies are already in main [Standards compliance] * This package uses qmake and does not require translations. [Maintenance] * This package is maintained by Jeremy Laine, upstream in Debian and actively in use on the phone images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qdjango/+bug/1612270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625172] [NEW] [MIR] address-book-service
Public bug reported: [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: * buteo-sync-plugins-contacts-google (This dep is required for address-book-updater) [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 ** Affects: address-book-service (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~renatofilho/address-book-service/no-sync-dep -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1625172 Title: [MIR] address-book-service Status in address-book-service package in Ubuntu: New 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: * buteo-sync-plugins-contacts-google (This dep is required for address-book-updater) [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/ubuntu/+source/address-book-service/+bug/1625172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624470] Re: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop
** Branch linked: lp:~ahayzen/webbrowser-app/fix-depends-on-non- notifyable-prop-001 -- 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/1624470 Title: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop Status in webbrowser-app package in Ubuntu: Confirmed Bug description: This is a fairly recent regression, that test used to pass reliably on desktop. As not much has changed in the browser code itself, I suspect changes somewhere else in the stack maybe. When run on my xenial+overlay laptop in a unity7 session, webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs and eventually times out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1624470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618726] Re: ifup & ifdown crash if multiple interfaces are listed in no-scripts
** Changed in: ifupdown (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1618726 Title: ifup & ifdown crash if multiple interfaces are listed in no-scripts Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Xenial: Fix Committed Status in ifupdown package in Debian: Fix Released Bug description: [Impact] ifup and ifupdown segfault if multiple interfaces are listed in no-scripts This is a trivially reproducible crash in ifup/ifdown, with a patch attached. [Test Case] Steps to reproduce: 1) echo no-scripts foo bar >> /etc/network/interfaces 2) ifup baz Expected results: Unknown interface baz Actual results: Segmentation fault (core dumped) It's irrelevant whether the second interface is on the same no-scripts line or separate one. This will crash just the same: echo no-scripts foo >> /etc/network/interfaces echo no-scripts bar >> /etc/network/interfaces [Regression potential] Seems slight. The patch fixes a clear bug in code that is only used to process the no-scripts (and apparently no-auto-down) stanzas. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1618726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624470] Re: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop
** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) => Andrew Hayzen (ahayzen) ** Changed in: webbrowser-app (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1624470 Title: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop Status in webbrowser-app package in Ubuntu: In Progress Bug description: This is a fairly recent regression, that test used to pass reliably on desktop. As not much has changed in the browser code itself, I suspect changes somewhere else in the stack maybe. When run on my xenial+overlay laptop in a unity7 session, webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs and eventually times out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1624470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Joakim, I think my problem is related to gdm. Additionally to your packages I needed to apply this fix: https://askubuntu.com/questions/689281/pulseaudio-can-not-load- bluetooth-module-15-10-16-04 Now everything is working nicely, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()
Sorry, no, I didn't build qtbase from source to test. I've added the silo, but I still get a crash with this same stack trace when the scope is destroyed. I guess further fixes in Qt are required beyond these changes perhaps. -- 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/1618590 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1618590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625078] Re: lxc 2.0.4-0ubuntu3 ADT test failure with linux 4.8.0-11.12
*** This bug is a duplicate of bug 1623424 *** https://bugs.launchpad.net/bugs/1623424 ** This bug has been marked a duplicate of bug 1623424 lxc autopkgtest regression -- 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/1625078 Title: lxc 2.0.4-0ubuntu3 ADT test failure with linux 4.8.0-11.12 Status in lxc package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/l/lxc/20160918_102256@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/i386/l/lxc/20160918_103635@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/l/lxc/20160918_150303@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1625078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595348] Re: Web browser dissapears too often
Can we check the incidence of crashes on errors.u.c ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Bill Filler (bfiller) ** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623424] Re: lxc autopkgtest regression
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- 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/1623424 Title: lxc autopkgtest regression Status in lxc package in Ubuntu: Confirmed Bug description: http://autopkgtest.ubuntu.com/packages/lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1623424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()
** Also affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu) Status: Confirmed => Incomplete -- 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/1618590 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() Status in qtbase-opensource-src package in Ubuntu: Incomplete Status in unity-scope-click package in Ubuntu: New Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1618590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
I see. It seems to work just fine for lightdm. Glad you figured it out though. And you are very welcome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()
Ok then :( If you also double-chcecked your libqt5core5 (etc) are version 5.6.1+dfsg-3ubuntu6~1 For qtbase, we can continue to follow http://code.qt.io/cgit/qt/qtbase.git/log/src/dbus?h=5.6 and https://codereview.qt- project.org/#/q/owner:%22Thiago+Macieira%22+status:open,n,z for any patches to try, but otherwise we should try to workaround the issue. If you can describe the remaining problems or even produce an easy test case for upstream, please file a bug at https://bugreports.qt.io/ for Thiago to see. Gustavo Boiko has been hard at reworking telepathy-qt to work with the new QDBus behaviors in 5.6, here are references to what kind of changes he has needed to do: http://launchpadlibrarian.net/280893997/telepathy-qt_0.9.6.1-6ubuntu1_0.9.6.1-7ubuntu2.diff.gz http://launchpadlibrarian.net/284273846/telepathy-qt_0.9.6.1-7ubuntu2_0.9.6.1-9ubuntu6.diff.gz -- 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/1618590 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() Status in qtbase-opensource-src package in Ubuntu: Incomplete Status in unity-scope-click package in Ubuntu: New Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1618590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1621824] Re: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap."
** Changed in: console-setup (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1621824 Title: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap." Status in console-setup package in Ubuntu: Confirmed Bug description: == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 == State: Open by: knodelk on 23 August 2016 14:00:43 Seeing the following error message in the Ubuntu dmesg log following IPL to Ubuntu on system with Ubuntu 16.04.1 installed: # dmesg -T --level=alert,crit,err [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. This appears to be something that can be ignored so manufacturing will be ignoring this message until directed otherwise. ==> all systemd related messages: # dmesg -T | grep systemd [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le. [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to . [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event daemon FIFOs. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log). [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name Lookups. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd communication Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required static device nodes for the current kernel... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information manager... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice system-serial\x2dgetty.slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Uncomplicated firewall... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Set console keymap... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Debug File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted POSIX Message Queue File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Huge Pages File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Create list of required static device nodes for the current kernel. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Nameserver information manager. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Uncomplicated firewall. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Main process exited, code=exited, status=1/FAILURE [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Unit entered failed state. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Failed with result 'exit-code'. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted RPC Pipe File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Load Kernel Modules. [Tue Aug 23 09:20:12 2016] system
[Touch-packages] [Bug 1625201] [NEW] "lvconvert --repair" destroys thin pool LV
Public bug reported: Hi If pool meta is 16GB , lvconvert --repair will destroy logical volumes. After rapair logical volumes inside the pool can not be activated again. Steps to reproduce: truncate --size 100GiB /tmp/test losetup /dev/loop1 /tmp/test pvcreate /dev/loop1 vgcreate vg02 /dev/loop1 lvcreate -n pool0meta -L 16G vg02 lvcreate -n pool0 -L 16GiB vg02 lvcreate -n data -V 1GiB --thinpool vg02/pool0 vgchange -a n vg02 lvconvert --repair vg02/pool0 # vgchange -a y vg02 device-mapper: resume ioctl on (252:3) failed: Invalid argument Unable to resume vg02-pool0-tpool (252:3) device-mapper: resume ioctl on (252:3) failed: Invalid argument Unable to resume vg02-pool0-tpool (252:3) 1 logical volume(s) in volume group "vg02" now active Syslog : [6039585.407800] device-mapper: thin: 252:2: metadata device (4145152 blocks) too small: expected 4161600 [6039585.407859] device-mapper: table: 252:2: thin-pool: preresume failed, error = -22 [6039586.535215] device-mapper: thin: 252:2: metadata device (4145152 blocks) too small: expected 4161600 [6039586.535258] device-mapper: table: 252:2: thin-pool: preresume failed, error = -22 [6039613.657170] device-mapper: thin: 252:3: metadata device (4145152 blocks) too small: expected 4161600 [6039613.657212] device-mapper: table: 252:3: thin-pool: preresume failed, error = -22 [6039614.716005] device-mapper: thin: 252:3: metadata device (4145152 blocks) too small: expected 4161600 [6039614.716047] device-mapper: table: 252:3: thin-pool: preresume failed, error = -22 Workaround for this is to shirk pool meta ( only when it is possible: You have free space in VG, and when meta will fit ) : thin_dump /dev/mapper/vg02-pool0_tmeta > lvm_meta_dum lvcreate -n pool0meta2 -L 12G vg02 thin_restore -i lvm_meta_dump -o /dev/mapper/vg02-pool0meta2 lvconvert --thinpool vg02/pool0 --poolmetadata vg02/pool0meta2 -- Kind Regards Marek Grzybowski ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Sep 19 13:29:54 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 LC_MESSAGES=POSIX SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (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 lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1625201 Title: "lvconvert --repair" destroys thin pool LV Status in lvm2 package in Ubuntu: New Bug description: Hi If pool meta is 16GB , lvconvert --repair will destroy logical volumes. After rapair logical volumes inside the pool can not be activated again. Steps to reproduce: truncate --size 100GiB /tmp/test losetup /dev/loop1 /tmp/test pvcreate /dev/loop1 vgcreate vg02 /dev/loop1 lvcreate -n pool0meta -L 16G vg02 lvcreate -n pool0 -L 16GiB vg02 lvcreate -n data -V 1GiB --thinpool vg02/pool0 vgchange -a n vg02 lvconvert --repair vg02/pool0 # vgchange -a y vg02 device-mapper: resume ioctl on (252:3) failed: Invalid argument Unable to resume vg02-pool0-tpool (252:3) device-mapper: resume ioctl on (252:3) failed: Invalid argument Unable to resume vg02-pool0-tpool (252:3) 1 logical volume(s) in volume group "vg02" now active Syslog : [6039585.407800] device-mapper: thin: 252:2: metadata device (4145152 blocks) too small: expected 4161600 [6039585.407859] device-mapper: table: 252:2: thin-pool: preresume failed, error = -22 [6039586.535215] device-mapper: thin: 252:2: metadata device (4145152 blocks) too small: expected 4161600 [6039586.535258] device-mapper: table: 252:2: thin-pool: preresume failed, error = -22 [6039613.657170] device-mapper: thin: 252:3: metadata device (4145152 blocks) too small: expected 4161600 [6039613.657212] device-mapper: table: 252:3: thin-pool: preresume failed, error = -22 [6039614.716005] device-mapper: thin: 252:3: metadata device (4145152 blocks) too small: expected 4161600 [6039614.716047] device-mapper: table: 252:3: thin-pool: preresume failed, error = -22 Workaround for this is to shirk pool meta ( only when it is possible: You have free space in VG, and when meta will fit ) : thin_dump /dev/mapper/vg02-pool0_tmeta > lvm_meta_dum lvcreate -n pool0meta2 -L 12G vg02 thin_restore -i lvm_meta_dump -o /dev/mapper/vg02-pool0meta2 lvconvert --thinpool vg02/pool0 --poolmetadata vg02/pool0meta2 -- Kind Regards Marek Grzybowski ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-
[Touch-packages] [Bug 1612460] Re: [MIR] unity-scopes-shell
** Changed in: unity-scopes-shell (Ubuntu) Status: New => Fix Committed -- 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/1612460 Title: [MIR] unity-scopes-shell Status in unity-scopes-shell package in Ubuntu: Fix Committed Bug description: [Availability] * Available in universe [Rationale] * This package is required by unity8 [Security] * No known security issues [Quality assurance] * This package has unit tests [Dependencies] * [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/ubuntu/+source/unity-scopes-shell/+bug/1612460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1621824] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2016-09-19 09:50 EDT--- Here is the output of "systemctl status -l keyboard-setup.service" root@rcx2d407:~# systemctl status -l keyboard-setup.service * keyboard-setup.service - Set console keymap Loaded: loaded (/lib/systemd/system/keyboard-setup.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2016-09-15 11:24:18 CDT; 4min 59s ago Process: 9369 ExecStart=/usr/bin/loadkeys /etc/console-setup/cached.kmap.gz (code=exited, status=1/FAILURE) Main PID: 9369 (code=exited, status=1/FAILURE) Sep 15 11:24:18 rcx2d407 systemd[1]: Starting Set console keymap... Sep 15 11:24:18 rcx2d407 loadkeys[9369]: Couldn't get a file descriptor referring to the console Sep 15 11:24:18 rcx2d407 systemd[1]: keyboard-setup.service: Main process exited, code=exited, status=1/FAILURE Sep 15 11:24:18 rcx2d407 systemd[1]: Failed to start Set console keymap. Sep 15 11:24:18 rcx2d407 systemd[1]: keyboard-setup.service: Unit entered failed state. Sep 15 11:24:18 rcx2d407 systemd[1]: keyboard-setup.service: Failed with result 'exit-code'. root@rcx2d407:~# -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1621824 Title: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap." Status in console-setup package in Ubuntu: Confirmed Bug description: == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 == State: Open by: knodelk on 23 August 2016 14:00:43 Seeing the following error message in the Ubuntu dmesg log following IPL to Ubuntu on system with Ubuntu 16.04.1 installed: # dmesg -T --level=alert,crit,err [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. This appears to be something that can be ignored so manufacturing will be ignoring this message until directed otherwise. ==> all systemd related messages: # dmesg -T | grep systemd [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le. [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to . [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event daemon FIFOs. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log). [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name Lookups. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd communication Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required static device nodes for the current kernel... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information manager... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice system-serial\x2dgetty.slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Uncomplicated firewall... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Set console keymap... [Tu
[Touch-packages] [Bug 1612497] Re: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
You have a broken third party service installed named "ITMAgents1" that you will need to remove. ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1612497 Title: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in util-linux package in Ubuntu: Invalid Bug description: error during update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 12 11:58:46 2016 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2016-05-28 (75 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1612497/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
> I'll make it dynamically enabled https://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?id=19e67c70 ** Changed in: systemd (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 sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle |
[Touch-packages] [Bug 1590005] Re: Focus can go be moved inside ListItem in a horizontal ListView
** 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/1590005
Title:
Focus can go be moved inside ListItem in a horizontal ListView
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Committed
Bug description:
Run this code:
import QtQuick 2.4
import Ubuntu.Components 1.3
Item {
width: units.gu(50)
height: units.gu(50)
ListView {
anchors.fill: parent
model: 10
orientation: ListView.Horizontal
delegate: ListItem {
width: units.gu(5)
height: units.gu(5)
Button {
activeFocusOnTab: false
anchors {
fill: parent
margins: units.gu(1)
}
text: "Button #" + index
}
}
}
}
Use TAB to select the first ListItem in the list. Pressing the LEFT
arrow after that will put the focus on the Button in the first
ListItem (you can see the focus outline changing).
The same happens when using keyboard navigation to go to the last
ListItem and then pressing the RIGHT cursor key.
I could not reproduce the issue with a vertical ListView.
This gives problems for the new Toolbar with scrolling icons inside
it, because there I am wrapping an AbstractButton inside a ListItem in
order to be able to get cursor key navigation until this bug is fixed:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-
toolkit/+bug/1573616
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1590005/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1577596] Re: ntpd not started when using ntpdate
Thanks for the update Robie. I was not aware of ntpdate being deprecated (appears to have been deprecated years ago). For those like myself that require ntpd (the suggested alternative systemd-timesyncd uses sntp which may not suffice in all use cases), I think the best fix/workaround is to merely remove the ntpdate package. I didn't really use ntpdate anymore and suspect it was still installed from an earlier version of Ubuntu in my case (I've performed a fair number of inline upgrades on system). Historically, ntpdate was run prior to starting ntpd in case the clock was too far off for ntpd to sync. In looking at the ntp package further, I see that /etc/default/ntp includes the '-g' option which allows ntpd to perform a one time sync that would accommodate a clock with any delta. This in itself makes ntpdate unneeded for those running ntp service. Additionally, ntpd can also be run with arguments to simulate behavior of ntpdate if needed. So, if I understand correctly, the ntp package really has no bug (at least related to starting at boot). Issue was really due to bug with deprecated ntpdate package which should be removed if running ntp anyway. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate Status in init-system-helpers package in Ubuntu: Confirmed Status in ntp package in Ubuntu: Won't Fix Bug description: After updating from 14.04 to 16.04 on a number of my systems, ntpd no longer starts at boot on any of those systems. `systemctl status ntp` shows: ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon. May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon. Manually starting it using `systemctl start ntp` works fine. However, systemd does not seem to want to start it automatically at boot time. As best as I can tell based on trial and error, there is something special about the combination of the service being named "ntp.service" and the service depending on network.target. However, I haven't been able to identify exactly what is causing this. If I copy the init script to any other name, everything works fine: cp /etc/init.d/ntp /etc/init.d/ntpd Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd" systemctl enable ntpd # After a reboot, ntpd.service is started, but ntp.service is not. If I remove "$network" from the "# Required-Start: $network $remote_fs $syslog" line in /etc/init.d/ntp, then systemd starts it automatically ... But of course it is started before the network comes up, so it fails. If I replace /etc/init.d/ntp with a file containing only the following, systemd won't try to start it automatically at boot: #!/bin/sh ### BEGIN INIT INFO # Provides: ntp # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 4 5 # Default-Stop: 1 # Short-Description: Start NTP daemon ### END INIT INFO echo "script was run" >> /ntp.log If I rename that same dummy script to /etc/init.d/ntp2, it is started automatically at boot. However, grepping the systemd source code and my systemd config files for ntp doesn't seem to find anything that might cause this behavior: /etc/systemd# grep -iR ntp * timesyncd.conf:#NTP= timesyncd.conf:#FallbackNTP=ntp.ubuntu.com /lib/systemd# grep -R ntp * system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd Binary file systemd-networkd matches Binary file systemd-timedated matches Binary file systemd-timesyncd matches What else can I do to debug this further? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579135] Re: AppArmor profile reloading causes an intermittent kernel BUG
This bug was fixed in the package linux - 4.4.0-38.57 --- linux (4.4.0-38.57) xenial; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1620658 * CIFS client: access problems after updating to kernel 4.4.0-29-generic (LP: #1612135) - Revert "UBUNTU: SAUCE: (namespace) Bypass sget() capability check for nfs" - fs: Call d_automount with the filesystems creds * apt-key add fails in overlayfs (LP: #1618572) - SAUCE: overlayfs: fix regression in whiteout detection linux (4.4.0-37.56) xenial; urgency=low [ Tim Gardner ] * Release Tracking Bug - LP: #1618040 * [Feature] Instruction decoder support for new SKX instructions- AVX512 (LP: #1591655) - x86/insn: perf tools: Fix vcvtph2ps instruction decoding - x86/insn: Add AVX-512 support to the instruction decoder - perf tools: Add AVX-512 support to the instruction decoder used by Intel PT - perf tools: Add AVX-512 instructions to the new instructions test * [Ubuntu 16.04] FCoE Lun not visible in OS with inbox driver - Issue with ioremap() call on 32bit kernel (LP: #1608652) - lpfc: Correct issue with ioremap() call on 32bit kernel * [Feature] turbostat support for Skylake-SP server (LP: #1591802) - tools/power turbostat: decode more CPUID fields - tools/power turbostat: CPUID(0x16) leaf shows base, max, and bus frequency - tools/power turbostat: decode HWP registers - tools/power turbostat: Decode MSR_MISC_PWR_MGMT - tools/power turbostat: allow sub-sec intervals - tools/power turbostat: Intel Xeon x200: fix erroneous bclk value - tools/power turbostat: Intel Xeon x200: fix turbo-ratio decoding - tools/power turbostat: re-name "%Busy" field to "Busy%" - tools/power turbostat: add --out option for saving output in a file - tools/power turbostat: fix compiler warnings - tools/power turbostat: make fewer systems calls - tools/power turbostat: show IRQs per CPU - tools/power turbostat: show GFXMHz - tools/power turbostat: show GFX%rc6 - tools/power turbostat: detect and work around syscall jitter - tools/power turbostat: indicate SMX and SGX support - tools/power turbostat: call __cpuid() instead of __get_cpuid() - tools/power turbostat: correct output for MSR_NHM_SNB_PKG_CST_CFG_CTL dump - tools/power turbostat: bugfix: TDP MSRs print bits fixing - tools/power turbostat: SGX state should print only if --debug - tools/power turbostat: print IRTL MSRs - tools/power turbostat: initial BXT support - tools/power turbostat: decode BXT TSC frequency via CPUID - tools/power turbostat: initial SKX support * [BYT] display hotplug doesn't work on console (LP: #1616894) - drm/i915/vlv: Make intel_crt_reset() per-encoder - drm/i915/vlv: Reset the ADPA in vlv_display_power_well_init() - drm/i915/vlv: Disable HPD in valleyview_crt_detect_hotplug() - drm/i915: Enable polling when we don't have hpd * [Feature]intel_idle enabling on Broxton-P (LP: #1520446) - intel_idle: add BXT support * [Feature] EDAC: Update driver for SKX-SP (LP: #1591815) - [Config] CONFIG_EDAC_SKX=m - EDAC, skx_edac: Add EDAC driver for Skylake * [Feature] KBL: Sandy Peak(3168) WiFi/BT support (LP: #1591648) - Bluetooth: Add support for Intel Bluetooth device 3168 [8087:0aa7] * MacBookPro11,4 fails to poweroff or suspend (LP: #1587714) - SAUCE: PCI: Workaround to enable poweroff on Mac Pro 11 * Support Edge Gateway's Bluetooth LED (LP: #1512999) - SAUCE: Bluetooth: Support for LED on Edge Gateways - SAUCE: Bluetooth: Use host bridge subsystem IDs to identify Edge Gateways * Please add support for alps touchpad. (LP: #1616813) - [Config] CONFIG_HID_ALPS=m - HID: add Alps I2C HID Touchpad-Stick support - HID: alps: struct u1_dev *priv is internal to the driver - HID: alps: pass correct sizes to hid_hw_raw_request() - HID: alps: match alps devices in core - HID: alps: a few cleanups * DINO2M - System hangs with a black screen during s4 stress test (LP: #1616781) - x86/power/64: Fix kernel text mapping corruption during image restoration * Xenial update to v4.4.17 stable release (LP: #1611833) - USB: OHCI: Don't mark EDs as ED_OPER if scheduling fails - x86/quirks: Apply nvidia_bugs quirk only on root bus - x86/quirks: Reintroduce scanning of secondary buses - x86/quirks: Add early quirk to reset Apple AirPort card - dmaengine: at_xdmac: align descriptors on 64 bits - dmaengine: at_xdmac: fix residue corruption - dmaengine: at_xdmac: double FIFO flush needed to compute residue - mm, sl[au]b: add __GFP_ATOMIC to the GFP reclaim mask - mm, compaction: abort free scanner if split fails - fs/nilfs2: fix potential underflow in call to crc32_le - mm, compaction: prevent VM_BUG_ON when terminating freeing scanner - mm, meminit: always return a valid node from early_pfn_to_nid -
[Touch-packages] [Bug 1625068] Re: aethercast binaries disappeared from the system
This bug was fixed in the package ubuntu-touch-meta - 1.283 --- ubuntu-touch-meta (1.283) yakkety; urgency=medium * Refreshed dependencies * Added aethercast to touch (LP: #1625068) * Added oxideqt-codecs-extra to touch [arm64] * Added unity-webapps-qml to touch [arm64] -- Łukasz 'sil2100' Zemczak Mon, 19 Sep 2016 14:15:59 +0200 ** Changed in: ubuntu-touch-meta (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625068 Title: aethercast binaries disappeared from the system Status in Canonical System Image: New Status in aethercast package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu RTM: Fix Released Bug description: After update to 182, the aethercast binaries disappeared from the system, leaving the external display page in system-settings broken. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 182 device name: turbo channel: ubuntu-touch/rc-proposed/meizu-pd.en last update: 2016-09-18 20:11:35 version version: 182 version ubuntu: 20160917 version device: 20160824-d33b825 version custom: 20160831-992-8-12 UPDATE: I've been told the change to make aethercast an option suggestion in system-settings caused to not have aethercast pulled in in the image builds. It seems like there are 2 fixes needed: a) Seed aethercast in relevant phone images b) fix system-settings to hide the external display section when aethercast is not around. Currently the button is there but just does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()
** Tags added: qt5.6 -- 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/1618590 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() Status in Canonical System Image: New Status in qtbase-opensource-src package in Ubuntu: Incomplete Status in unity-scope-click package in Ubuntu: New Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615757] Re: click install fails on 16.10, causing user install and autopkgtest failures
This bug was fixed in the package click - 0.4.45.1+16.10.20160916-0ubuntu1 --- click (0.4.45.1+16.10.20160916-0ubuntu1) yakkety; urgency=medium * Kill gpg-agent (if possible) after running debsigs in integration tests. * Copy integration test GPG keyring to a temporary directory so that the GPG agent socket name doesn't end up being too long. -- Colin Watson Fri, 16 Sep 2016 17:46:25 + ** Changed in: click (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1615757 Title: click install fails on 16.10, causing user install and autopkgtest failures Status in click package in Ubuntu: Fix Released Bug description: click crashed with: click crashed with subprocess.CalledProcessError in run(): Command '['dpkg', '--force-not-root', '--force-bad-path', '--force- architecture', '--instdir', '/opt/click.ubuntu.com/com.ubuntu.filemanager/0.4.525', '--admindir', '/opt/click.ubuntu.com/com.ubuntu.filemanager/0.4.525/.click', '--path-exclude', '*/.click/*', '--log', '/opt/click.ubuntu.com/.click/log', '--no-triggers', '--install', '/home/emanuele/Scaricati/com.ubuntu.filemanager_0.4.525_multi.click']' returned non-zero exit status 1 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: click 0.4.44+16.10.20160811.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Mon Aug 22 11:16:02 2016 ExecutablePath: /usr/bin/click InstallationDate: Installed on 2016-08-21 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterpreterPath: /usr/bin/python3.5 ProcCmdline: /usr/bin/python3 /usr/bin/click install --user emanuele /home/emanuele/Scaricati/com.ubuntu.filemanager_0.4.525_multi.click ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 LANGUAGE=it SHELL=/bin/bash PythonArgs: ['/usr/bin/click', 'install', '--user', 'emanuele', '/home/emanuele/Scaricati/com.ubuntu.filemanager_0.4.525_multi.click'] SourcePackage: click Title: click crashed with subprocess.CalledProcessError in run(): Command '['dpkg', '--force-not-root', '--force-bad-path', '--force-architecture', '--instdir', '/opt/click.ubuntu.com/com.ubuntu.filemanager/0.4.525', '--admindir', '/opt/click.ubuntu.com/com.ubuntu.filemanager/0.4.525/.click', '--path-exclude', '*/.click/*', '--log', '/opt/click.ubuntu.com/.click/log', '--no-triggers', '--install', '/home/emanuele/Scaricati/com.ubuntu.filemanager_0.4.525_multi.click']' returned non-zero exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1615757/+subscriptions -- Mailing list: https://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 1577596] Re: ntpd not started when using ntpdate
Hi Rick, On Mon, Sep 19, 2016 at 02:17:58PM -, Rick Frey wrote: > So, if I understand correctly, the ntp package really has no bug (at > least related to starting at boot). Issue was really due to bug with > deprecated ntpdate package which should be removed if running ntp > anyway. That's right. In Trusty, you may not be permitted to remove the ntpdate package without removing a task metapackage (generally undesirable). IIRC, I noted in the ML thread some options to disable ntpdate instead. Since Xenial, it makes sense just to not have ntpdate installed at all, IMHO. Though I still welcome further discussion if there are use cases this breaks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate Status in init-system-helpers package in Ubuntu: Confirmed Status in ntp package in Ubuntu: Won't Fix Bug description: After updating from 14.04 to 16.04 on a number of my systems, ntpd no longer starts at boot on any of those systems. `systemctl status ntp` shows: ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon. May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon. Manually starting it using `systemctl start ntp` works fine. However, systemd does not seem to want to start it automatically at boot time. As best as I can tell based on trial and error, there is something special about the combination of the service being named "ntp.service" and the service depending on network.target. However, I haven't been able to identify exactly what is causing this. If I copy the init script to any other name, everything works fine: cp /etc/init.d/ntp /etc/init.d/ntpd Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd" systemctl enable ntpd # After a reboot, ntpd.service is started, but ntp.service is not. If I remove "$network" from the "# Required-Start: $network $remote_fs $syslog" line in /etc/init.d/ntp, then systemd starts it automatically ... But of course it is started before the network comes up, so it fails. If I replace /etc/init.d/ntp with a file containing only the following, systemd won't try to start it automatically at boot: #!/bin/sh ### BEGIN INIT INFO # Provides: ntp # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 4 5 # Default-Stop: 1 # Short-Description: Start NTP daemon ### END INIT INFO echo "script was run" >> /ntp.log If I rename that same dummy script to /etc/init.d/ntp2, it is started automatically at boot. However, grepping the systemd source code and my systemd config files for ntp doesn't seem to find anything that might cause this behavior: /etc/systemd# grep -iR ntp * timesyncd.conf:#NTP= timesyncd.conf:#FallbackNTP=ntp.ubuntu.com /lib/systemd# grep -R ntp * system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd Binary file systemd-networkd matches Binary file systemd-timedated matches Binary file systemd-timesyncd matches What else can I do to debug this further? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1478319] Re: Wifi doesn't reconnect to AP if it uses the same SSID than another AP
@jean-baptiste do you still see this? -- 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/1478319 Title: Wifi doesn't reconnect to AP if it uses the same SSID than another AP Status in Canonical System Image: Incomplete Status in network-manager package in Ubuntu: Expired Bug description: current build number: 68 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-24 08:00:20 version version: 68 version ubuntu: 20150724 version device: 20150709-8965e37 version custom: 20150716-819-8-42 My ISP (Free in France) provides a hotspot service so that customers can use the connection of any other customer using a generic open Wifi connection (for reference http://www.free.fr/assistance/2303.html - in French) The SSID is called 'FreeWifi' on all the boxes but obviously APs are all different since it's customers' DSL routers. When I connect to one of this access point, suspend the phone and resume it in another location where the SSID is available but from a different AP, the phone doesn't connect to this AP and the list of networks in the network-indicator doesn't refresh and still show the list of network from the previous location. I have to forget the network called 'FreeWifi' and reconnect in order to refresh the list and make it work. It's 100% reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1478319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625217] [NEW] udev sometimes doesn't apply systemd tag to devices
Public bug reported: Since upgrading this machine to yakkety I've seen periodic hangs during booting. If I wait long enough systemd give up and drops to maintenance mode. Looking in the journal I see events like this: Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid- 63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk-by \x2duuid-63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed out. Searching on the internet indicates that this happen if devices reported by udev don't have the "systemd" tag, and I find that they do not have the tag when the boot times out but they do have the tag when boot does not time out. This happens once for every 3 or 4 boots and with both 4.4 and 4.8 kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm info --export-db' from a timed-out boot. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-6 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 19 09:27:08 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-19 (577 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago) dmi.bios.date: 05/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "Output of 'journalctl -xb'" https://bugs.launchpad.net/bugs/1625217/+attachment/4743654/+files/journal.txt -- 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/1625217 Title: udev sometimes doesn't apply systemd tag to devices Status in systemd package in Ubuntu: New Bug description: Since upgrading this machine to yakkety I've seen periodic hangs during booting. If I wait long enough systemd give up and drops to maintenance mode. Looking in the journal I see events like this: Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid- 63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk- by\x2duuid- 63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed out. Searching on the internet indicates that this happen if devices reported by udev don't have the "systemd" tag, and I find that they do not have the tag when the boot times out but they do have the tag when boot does not time out. This happens once for every 3 or 4 boots and with both 4.4 and 4.8 kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm info --export-db' from a timed-out boot. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-6 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 19 09:27:08 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-19 (577 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago) dmi.bios.date: 05/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625100] Re: systemd 231-6 ADT test failure with linux 4.8.0-11.12
** 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/1625100 Title: systemd 231-6 ADT test failure with linux 4.8.0-11.12 Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/amd64/s/systemd/20160918_093714@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-canonical-kernel-team-unstable/yakkety/ppc64el/s/systemd/20160918_231904@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625217] Re: udev sometimes doesn't apply systemd tag to devices
** Attachment added: "Output of 'udevadm info --export-db'" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+attachment/4743665/+files/udev-db.txt -- 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/1625217 Title: udev sometimes doesn't apply systemd tag to devices Status in systemd package in Ubuntu: New Bug description: Since upgrading this machine to yakkety I've seen periodic hangs during booting. If I wait long enough systemd give up and drops to maintenance mode. Looking in the journal I see events like this: Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid- 63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk- by\x2duuid- 63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed out. Searching on the internet indicates that this happen if devices reported by udev don't have the "systemd" tag, and I find that they do not have the tag when the boot times out but they do have the tag when boot does not time out. This happens once for every 3 or 4 boots and with both 4.4 and 4.8 kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm info --export-db' from a timed-out boot. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-6 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 19 09:27:08 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-19 (577 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago) dmi.bios.date: 05/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Milestone: None => x1 ** Changed in: unity-scope-click (Ubuntu) Assignee: (unassigned) => Rodney Dawes (dobey) ** Changed in: qtbase-opensource-src (Ubuntu) Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki) -- 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/1618590 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() Status in Canonical System Image: New Status in qtbase-opensource-src package in Ubuntu: Incomplete Status in unity-scope-click package in Ubuntu: New Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619918] Re: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error)
** Changed in: linux (Ubuntu Vivid) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1619918 Title: lsattr 32bit does not work on 64bit kernel (Inappropriate ioctl error) Status in e2fsprogs package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in e2fsprogs source package in Trusty: Invalid Status in linux source package in Trusty: Fix Committed Status in e2fsprogs source package in Vivid: Invalid Status in linux source package in Vivid: Fix Committed Status in e2fsprogs source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in e2fsprogs source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Bug description: I run an amd64 kernel on trusty. The e2fsprogs package was still the 32 bit i386 variety. This lead to the following situation (for essentially all files on a btrfs partition). $ lsattr /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko lsattr: Inappropriate ioctl for device While reading flags on /lib/modules/3.13.0-95-generic/kernel/drivers/staging/lustre/lustre/ptlrpc/ptlrpc.ko The problem was resolved by installing e2fsprogs:amd64. https://patchwork.kernel.org/patch/7517361/ might be related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1619918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
