[Dx-packages] [Bug 1318741] [NEW] hud-service spins at 100% cpu
Public bug reported: I've seen this intermittently. $ top -b -n1|head #top - 17:32:32 up 8:33, 4 users, load average: 2.04, 2.15, 1.66 Tasks: 353 total, 2 running, 350 sleeping, 1 stopped, 0 zombie %Cpu(s): 11.4 us, 3.8 sy, 0.0 ni, 84.6 id, 0.2 wa, 0.1 hi, 0.0 si, 0.0 st KiB Mem: 12182620 total, 11934092 used, 248528 free, 166328 buffers KiB Swap: 12455932 total, 3412 used, 12452520 free. 5905344 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2909 james 20 0 1068520 258608 57852 R 100.6 2.1 9:51.79 hud-service 22497 james 20 0 1683732 926356 67876 S 62.9 7.6 5:19.45 emulator-x86 1690 root 20 0 550036 186848 157316 S 18.9 1.5 17:05.96 Xorg $ sudo cat /proc/2909/stack [] 0x $ sudo strace -p 2909 -fFv -s 1024 -o /tmp/hud-service.log Process 2909 attached with 4 threads Process 2909 detached Process 2962 detached Process 2966 detached Process 3012 detached ^C strace attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: hud 13.10.1+14.04.20140402-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 12 17:30:45 2014 InstallationDate: Installed on 2014-04-11 (30 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: hud UpgradeStatus: Upgraded to utopic on 2014-05-08 (4 days ago) upstart.window-stack-bridge.log: Could not get window property "_UNITY_OBJECT_PATH" "/org/ayatana/bamf/window/100665112" ** Affects: hud (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: "hud-service.strace" https://bugs.launchpad.net/bugs/1318741/+attachment/4110793/+files/hud-service.strace -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1318741 Title: hud-service spins at 100% cpu Status in “hud” package in Ubuntu: New Bug description: I've seen this intermittently. $ top -b -n1|head #top - 17:32:32 up 8:33, 4 users, load average: 2.04, 2.15, 1.66 Tasks: 353 total, 2 running, 350 sleeping, 1 stopped, 0 zombie %Cpu(s): 11.4 us, 3.8 sy, 0.0 ni, 84.6 id, 0.2 wa, 0.1 hi, 0.0 si, 0.0 st KiB Mem: 12182620 total, 11934092 used, 248528 free, 166328 buffers KiB Swap: 12455932 total, 3412 used, 12452520 free. 5905344 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2909 james 20 0 1068520 258608 57852 R 100.6 2.1 9:51.79 hud-service 22497 james 20 0 1683732 926356 67876 S 62.9 7.6 5:19.45 emulator-x86 1690 root 20 0 550036 186848 157316 S 18.9 1.5 17:05.96 Xorg $ sudo cat /proc/2909/stack [] 0x $ sudo strace -p 2909 -fFv -s 1024 -o /tmp/hud-service.log Process 2909 attached with 4 threads Process 2909 detached Process 2962 detached Process 2966 detached Process 3012 detached ^C strace attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: hud 13.10.1+14.04.20140402-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 12 17:30:45 2014 InstallationDate: Installed on 2014-04-11 (30 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: hud UpgradeStatus: Upgraded to utopic on 2014-05-08 (4 days ago) upstart.window-stack-bridge.log: Could not get window property "_UNITY_OBJECT_PATH" "/org/ayatana/bamf/window/100665112" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1318741/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1318741] Re: hud-service spins at 100% cpu
*** This bug is a duplicate of bug 1300722 *** https://bugs.launchpad.net/bugs/1300722 backtrace from connecting to hud-service with gdb. ** Attachment added: "hud-service.gdb" https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1318741/+attachment/4110798/+files/hud-service.gdb -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1318741 Title: hud-service spins at 100% cpu Status in “hud” package in Ubuntu: New Bug description: I've seen this intermittently. $ top -b -n1|head #top - 17:32:32 up 8:33, 4 users, load average: 2.04, 2.15, 1.66 Tasks: 353 total, 2 running, 350 sleeping, 1 stopped, 0 zombie %Cpu(s): 11.4 us, 3.8 sy, 0.0 ni, 84.6 id, 0.2 wa, 0.1 hi, 0.0 si, 0.0 st KiB Mem: 12182620 total, 11934092 used, 248528 free, 166328 buffers KiB Swap: 12455932 total, 3412 used, 12452520 free. 5905344 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2909 james 20 0 1068520 258608 57852 R 100.6 2.1 9:51.79 hud-service 22497 james 20 0 1683732 926356 67876 S 62.9 7.6 5:19.45 emulator-x86 1690 root 20 0 550036 186848 157316 S 18.9 1.5 17:05.96 Xorg $ sudo cat /proc/2909/stack [] 0x $ sudo strace -p 2909 -fFv -s 1024 -o /tmp/hud-service.log Process 2909 attached with 4 threads Process 2909 detached Process 2962 detached Process 2966 detached Process 3012 detached ^C strace attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: hud 13.10.1+14.04.20140402-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 12 17:30:45 2014 InstallationDate: Installed on 2014-04-11 (30 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: hud UpgradeStatus: Upgraded to utopic on 2014-05-08 (4 days ago) upstart.window-stack-bridge.log: Could not get window property "_UNITY_OBJECT_PATH" "/org/ayatana/bamf/window/100665112" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1318741/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
Just hit this again whilst browsing in firefox. The only Qt app I have running (I think) is spotify. ~/.cache/upstart/hud.log shows the offending entry as: (hud-service:7316): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Hit DBusMenu safety valve for menu at :1.19 /com/canonical/menu/1600078 Hit DBusMenu safety valve for menu at :1.19 /com/canonical/menu/1600078 (ad infinitum) d-feet shows 1:19 to be upowerd which appears to be doing squat: $ sudo cat /proc/$(pidof upowerd)/stack [] poll_schedule_timeout+0x49/0x70 [] do_sys_poll+0x428/0x540 [] SyS_poll+0x65/0x100 [] tracesys+0xe1/0xe6 [] 0x -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObjec
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
Doh! Thankfully, I still have d-feet running and all the apps that were running before I had to kill hud-service. On the session bus, 1:19 is /usr/lib/firefox/firefox - the first object path I see for firefox is: /com/canonical/menu/1600078. Presumably, we could add some extra details (atleast the pid) to DBusMenuCollector::openMenu() make tracking this issue down easier? -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
Hit it again, and again it is triggered by firefox. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7fda833dbe04 in g_main_context_dispatch ()
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
Correct. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7fda833dbe04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
Had 2 further cases of this in the last couple of days. What's interesting though is that I now have a script that monitors for CPU hogs. The script correctly detected hud-service spinning... *but* after a period of time (<1m), it stopped spinning. Attached is the log fwiw. ** Attachment added: "hud.log" https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1300722/+attachment/4113179/+files/hud.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QOb
[Dx-packages] [Bug 1342586] Re: [utopic] [proposed] cgmanager breaks lightdm login
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1342586 Title: [utopic] [proposed] cgmanager breaks lightdm login Status in “systemd” package in Ubuntu: New Status in “systemd-shim” package in Ubuntu: New Bug description: The latest 'proposed' systemd-shim 6.3-ubuntu1 package install cgmanager. As a result X is first killed and then its impossible to login again. This happen on Utopic i386 with unity-greeter, systemd-boot and a gtx 750 nvidia card. The bad experience: - trying to purge cgmanager also wants to remove a bunch of packages that will deeply break the system - X can be started but the login always fail - there is no way to open a terminal (ctrl+t) or (ctrl+alt+t) from X - even cant get a command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1342586/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1342586] Re: [utopic] [proposed] cgmanager breaks lightdm login
Note: systemd packaging branch is out-of-date. Attached patch stops a NULL deref which would explain this issue. ** Patch added: "Don't nih_unref NULL value." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1342586/+attachment/4154594/+files/bug-1342586.patch -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1342586 Title: [utopic] [proposed] cgmanager breaks lightdm login Status in “systemd” package in Ubuntu: New Status in “systemd-shim” package in Ubuntu: New Bug description: The latest 'proposed' systemd-shim 6.3-ubuntu1 package install cgmanager. As a result X is first killed and then its impossible to login again. This happen on Utopic i386 with unity-greeter, systemd-boot and a gtx 750 nvidia card. The bad experience: - trying to purge cgmanager also wants to remove a bunch of packages that will deeply break the system - X can be started but the login always fail - there is no way to open a terminal (ctrl+t) or (ctrl+alt+t) from X - even cant get a command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1342586/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1345505] Re: lock screen leaks keystrokes to window "behind" greeter
** Summary changed: - lock scren leaks keystrokes to window "behind" greeter + lock screen leaks keystrokes to window "behind" greeter -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1345505 Title: lock screen leaks keystrokes to window "behind" greeter Status in “unity” package in Ubuntu: New Bug description: When my machine comes out of suspend, I am shown the lightdm greeter. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345505/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Still unclear why memory is being cached in Upstart address space, but I'm starting to think this might be a libdbus issue. What is triggering the memory rise though is unity-panel-service: stopping this from running results in no memory increase within the Session Init. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Incomplete Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Incomplete Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Right - recall that I am testing on i386 as I don't have mako/maguro :) However, note that on Touch, the upstart code in unity8 (plugins/Unity/Indicators/indicatorsmanager.cpp) is almost identical to the upstart code in unity-panel-service (unity/services/panel- service.c). Is it possible to somehow disable the loading of /usr/lib/i386-linux- gnu/unity8/qml/Unity/Indicators/libIndicatorsQml.so in the unity8-private package on mako/maguro to see if that stops the memory bloat? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Incomplete Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Incomplete Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Re #41, interesting that unity-panel-service *is* installed on Touch image though :) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in “linux” package in Ubuntu: Incomplete Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Confirmed Status in “linux” source package in Saucy: Incomplete Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Confirmed Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
This problem can now be demonstrated with a single connection to upstart that makes the following calls: dbus_connection_open() nih_dbus_proxy_new () The problem is not seen if the app instead calls: - nih_dbus_connect (upstart_session, disconnect_handler) - nih_dbus_proxy_new () - nih_main_loop() Or, - nih_dbus_connect (upstart_session, NULL) - nih_dbus_proxy_new () - nih_main_loop() Specifically, the problem appears to be that when an app calls dbus_connection_open(), one or more of the functions in nih_dbus_setup() should be being called to allow libdbus to interrupt the apps main loop and request callbacks are run to clean up resources. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
The problem is not observed when the only connections to upstart are the standard upstart bridges (since they use nih_dbus_connect()). For reference, here is nih_dbus_setup() which includes one or more calls that unity seemingly should be calling itself: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/saucy/libnih/saucy/view/head:/nih- dbus/dbus_connection.c#L202 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Note that disabling libIndicatorsQml.so with #44 did not resolve the problem. However, I am confident this is because there were other connections to the Session Init (probably resulting from libupstart-app- launch1). This does need to be confirmed though. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Run as: $ spam.sh ** Attachment added: "spam.sh" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3872619/+files/spam.sh -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
Program attached in #51 demonstrates the incorrect calling behaviour. To demonstrate the correct behaviour change the #if0/else/endif such that rather than calling dbus_connection_open(), the program calls nih_dbus_connect(). nih_dbus_connect(): No memory growth. dbus_connection_open(): Memory growth. ** Summary changed: - uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch + uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes session upstart to consume massive amounts of memory on Ubuntu Touch
C program to trigger this bug. Run it in an environment with UPSTART_SESSION set (such as a desktop/Touch environment), then run the about-to-be attached spam.sh script. ** Attachment added: "trigger-bug-1235649.c" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3872618/+files/trigger-bug-1235649.c -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Note that the following call on the server side does not resolve the issue: while (dbus_connection_dispatch (connection) == DBUS_DISPATCH_DATA_REMAINS) ; -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Neither does calling the following help: dbus_connection_flush (connection); -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Just got a much more interesting valgrind run. Juicy excerpt: ==9366== 147,560 bytes in 1,190 blocks are still reachable in loss record 187 of 188 ==9366==at 0x402B965: calloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==9366==by 0x408E730: dbus_malloc0 (dbus-memory.c:572) ==9366==by 0x407983B: dbus_message_new_empty_header (dbus-message.c:1153) ==9366==by 0x4079D0F: dbus_message_new_method_return (dbus-message.c:1319) ==9366==by 0x80835F5: control_emit_event_reply (com.ubuntu.Upstart.c:2098) ==9366==by 0x806BC6C: event_finished (event.c:501) ==9366==by 0x806B26F: event_poll (event.c:259) ==9366==by 0x4044B63: nih_main_loop (main.c:609) ==9366==by 0x804D507: main (main.c:688) ==9366== ==9366== 228,394,752 bytes in 2,386 blocks are still reachable in loss record 188 of 188 ==9366==at 0x402BB88: realloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==9366==by 0x408E778: dbus_realloc (dbus-memory.c:678) ==9366==by 0x408F08C: reallocate_for_length (dbus-string.c:349) ==9366==by 0x408F12B: set_length (dbus-string.c:390) ==9366==by 0x408F1A9: open_gap (dbus-string.c:411) ==9366==by 0x408FA67: copy (dbus-string.c:1198) ==9366==by 0x408FCCE: _dbus_string_copy_len (dbus-string.c:1368) ==9366==by 0x408DCF8: marshal_len_followed_by_bytes (dbus-marshal-basic.c:726) ==9366==by 0x408DD95: marshal_string (dbus-marshal-basic.c:758) ==9366==by 0x408DF60: _dbus_marshal_write_basic (dbus-marshal-basic.c:840) ==9366==by 0x4075CD7: _dbus_type_writer_write_basic_no_typecode (dbus-marshal-recursive.c:1601) ==9366==by 0x40768BB: _dbus_type_writer_write_basic (dbus-marshal-recursive.c:2323) ==9366== ==9366== LEAK SUMMARY: ==9366==definitely lost: 28 bytes in 1 blocks ==9366==indirectly lost: 24 bytes in 1 blocks ==9366== possibly lost: 12,907 bytes in 290 blocks ==9366==still reachable: 228,607,834 bytes in 3,732 blocks ==9366== suppressed: 0 bytes in 0 blocks ** Attachment added: "vg.log" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3877842/+files/vg.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Another valgrind log taken using the same precedure as above. However, this time I waited until the init process was consuming over 2GB of RAM. Top showed: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 15329 james 20 0 2463m 2,0g 12m R 100,0 26,1 6:51.59 memcheck-x86-li Once again, the biggest offender by a huge margin is dbus: ==15329== 1,153,679,208 bytes in 12,025 blocks are still reachable in loss record 208 of 208 ==15329==at 0x402BB88: realloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==15329==by 0x408E778: dbus_realloc (dbus-memory.c:678) ==15329==by 0x408F08C: reallocate_for_length (dbus-string.c:349) ==15329==by 0x408F12B: set_length (dbus-string.c:390) ==15329==by 0x408F1A9: open_gap (dbus-string.c:411) ==15329==by 0x408FA67: copy (dbus-string.c:1198) ==15329==by 0x408FCCE: _dbus_string_copy_len (dbus-string.c:1368) ==15329==by 0x408DCF8: marshal_len_followed_by_bytes (dbus-marshal-basic.c:726) ==15329==by 0x408DD95: marshal_string (dbus-marshal-basic.c:758) ==15329==by 0x408DF60: _dbus_marshal_write_basic (dbus-marshal-basic.c:840) ==15329==by 0x4075CD7: _dbus_type_writer_write_basic_no_typecode (dbus-marshal-recursive.c:1601) ==15329==by 0x40768BB: _dbus_type_writer_write_basic (dbus-marshal-recursive.c:2323) ==15329== ==15329== LEAK SUMMARY: ==15329==definitely lost: 28 bytes in 1 blocks ==15329==indirectly lost: 24 bytes in 1 blocks ==15329== possibly lost: 133,265 bytes in 315 blocks ==15329==still reachable: 1,154,753,166 bytes in 18,194 blocks ==15329== suppressed: 0 bytes in 0 blocks ** Attachment added: "vg-20131015.log.gz" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878397/+files/vg-20131015.log.gz -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Hi Steve, The trace in #59 was produced by: - Running Upstart via valgrind which upstart linked against debug builds of nih and dbus. - Running a single instance of the test program (#51). - Running spam.sh (#52). - Waiting until init was consuming ~200MB, then sending SIGTERM to the init/valgrind process. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: New Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
I can now recreate the memory bloat using a basic NIH D-Bus server program and associated client program. 1) Run the server as: $ ./test_nih_dbus_server unix:abstract=/com/hunt/james/foo com.hunt.james.Foo /com/hunt/james/Foo 2) Run the client as: $ ./test_nih_dbus_client unix:abstract=/com/hunt/james/foo com.hunt.james.Foo 3) Run the updated spammer as: $ ./spam_dbus_server.sh 4) Run top and watch the memory used by test_nih_dbus_server creep up. The problem seems to be caused by the call to notify_clients() - this sends a signal to every connected client every time the spam_dbus_server.sh sends its data to the server. Commenting out the call to notify_clients() stop the memory bloating issue. The function echo_handled() that is called by notify_clients() is analogous to control_emit_event_emitted() in Upstart parlance. Again, running valgrind on the server shows the same stack traces as above: ==30015== 91,750,175 bytes in 7,617 blocks are still reachable in loss record 164 of 164 ==30015==at 0x402BB88: realloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==30015==by 0x408E778: dbus_realloc (dbus-memory.c:678) ==30015==by 0x408F08C: reallocate_for_length (dbus-string.c:349) ==30015==by 0x408F12B: set_length (dbus-string.c:390) ==30015==by 0x408F1A9: open_gap (dbus-string.c:411) ==30015==by 0x408FA67: copy (dbus-string.c:1198) ==30015==by 0x408FCCE: _dbus_string_copy_len (dbus-string.c:1368) ==30015==by 0x408DCF8: marshal_len_followed_by_bytes (dbus-marshal-basic.c:726) ==30015==by 0x408DD95: marshal_string (dbus-marshal-basic.c:758) ==30015==by 0x408DF60: _dbus_marshal_write_basic (dbus-marshal-basic.c:840) ==30015==by 0x4075CD7: _dbus_type_writer_write_basic_no_typecode (dbus-marshal-recursive.c:1601) ==30015==by 0x40768BB: _dbus_type_writer_write_basic (dbus-marshal-recursive.c:2323) ** Attachment added: "test_nih_dbus_server.c" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878663/+files/test_nih_dbus_server.c -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Attachment added: "spam_dbus_server.sh" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878665/+files/spam_dbus_server.sh -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Attachment added: "test_nih_dbus_client.c" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878664/+files/test_nih_dbus_client.c -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
Valgrind log from test_nih_dbus_server.c run using 'valgrind --num- callers=100 ...'. ** Attachment added: "vg-test_nih_dbus_server.log.gz" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3878682/+files/vg-test_nih_dbus_server.log.gz -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
TBC, using the patch on #69 results in no memory bloat. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
FWICS D-Bus is behaving as designed: since the client has not called dbus_connection_set_wakeup_main_function(), and since D-Bus messaging is reliable, all libdbus is able to do when a signal is sent to a connection is cache any messages the client has not yet processed in the hope that at some future point it might consume them. The key part of the D-Bus code that explains this is dbus_connection_send_preallocated_unlocked_no_update(): -- /* Now we need to run an iteration to hopefully just write the messages * out immediately, and otherwise get them queued up */ _dbus_connection_do_iteration_unlocked (connection, NULL, DBUS_ITERATION_DO_WRITING, -1); /* If stuff is still queued up, be sure we wake up the main loop */ if (connection->n_outgoing > 0) _dbus_connection_wakeup_mainloop (connection); -- As shown, the messages (signals in the case of Upstart) are added to the client connection queue, but since the client called dbus_connection_open() rather than nih_dbus_connect(), no mainloop handler is registered to allow the client to deal with the signals sent to it. >From the upstart perspective, a fix is to call >dbus_connection_has_messages_to_send() and ignore that connection if the client still has unprocessed messages (patch attached). >From the D-Bus perspective, it would be useful to introduce a new public API: dbus_bool_t dbus_connection_has_wakeup_main_function (DBusConnection *connection); This would allow Upstart and other D-Bus server applications to detect erroneous client connections. ** Patch added: "bug-1235649.diff" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1235649/+attachment/3879222/+files/bug-1235649.diff -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
We already have bug 1203595 for having the Session Init connect to the D-Bus session bus. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: upstart (Ubuntu) Status: Fix Released => Incomplete ** Changed in: upstart (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: New Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: In Progress Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: New Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: upstart Assignee: (unassigned) => James Hunt (jamesodhunt) ** Changed in: upstart Status: New => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Upstart: Fix Committed Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: In Progress Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: Confirmed Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1288152] [NEW] keyboard shortcuts overlay does not specify super+L for lockscreen
Public bug reported: (Long) Pressing the super (aka "windows") key displays the "Keyboard Shortcuts" overlay. However, this summary does not show that Super+L is now a shortcut for locking the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Mar 5 09:55:53 2014 InstallationDate: Installed on 2010-10-21 (1231 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-01 (123 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1288152 Title: keyboard shortcuts overlay does not specify super+L for lockscreen Status in “unity” package in Ubuntu: New Bug description: (Long) Pressing the super (aka "windows") key displays the "Keyboard Shortcuts" overlay. However, this summary does not show that Super+L is now a shortcut for locking the screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Wed Mar 5 09:55:53 2014 InstallationDate: Installed on 2010-10-21 (1231 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-01 (123 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1288152/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295639] [NEW] move to workspace loses track of window entirely
Public bug reported: Moving a window to another workspace using the context menu options "Move to Workspace right" or "Move to Another Workspace" causes unity to lose track of the window entirely - it disappears never to return. Note: the processes associated with the windows *are* still running as shown by xlsclients. Moving the windows manually to another workspace (by shifting the window almost off the screen to the right or bottom, then changing to the appropriate workspace and pulling the half-obscured window into that workspace) works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Fri Mar 21 11:36:12 2014 InstallationDate: Installed on 2010-10-21 (1247 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-01 (139 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295639 Title: move to workspace loses track of window entirely Status in “unity” package in Ubuntu: New Bug description: Moving a window to another workspace using the context menu options "Move to Workspace right" or "Move to Another Workspace" causes unity to lose track of the window entirely - it disappears never to return. Note: the processes associated with the windows *are* still running as shown by xlsclients. Moving the windows manually to another workspace (by shifting the window almost off the screen to the right or bottom, then changing to the appropriate workspace and pulling the half-obscured window into that workspace) works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140318-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Fri Mar 21 11:36:12 2014 InstallationDate: Installed on 2010-10-21 (1247 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-11-01 (139 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1295639/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1399710] [NEW] no audible warning of high volume level
Public bug reported: Additional to the work done on bug 1373404, I think we need to consider adding an audio warning when the volume crosses the threshold value. The way android works is that the user is asked if they want to allow higher volume levels (they must click "ok"). Our approach is to just display a visual warning. That's fine (assuming it complies with all legal regs), but it isn't helpful from an accessibility perspective. Obviously folk can hear when levels become painful high, but how about we insert an audible warning when the user crosses the threshold? I'd suggest we do both of the following to indicate an audible warning: 1) Mute (or atleast lower) the currently playing audio streams. 2) Play two beeps in quick succession (at the original volume level prior to mute/lowering). Once the beeps have been played, the volume level will be restored to the appropriate (higher) level. ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1399710 Title: no audible warning of high volume level Status in indicator-sound package in Ubuntu: New Bug description: Additional to the work done on bug 1373404, I think we need to consider adding an audio warning when the volume crosses the threshold value. The way android works is that the user is asked if they want to allow higher volume levels (they must click "ok"). Our approach is to just display a visual warning. That's fine (assuming it complies with all legal regs), but it isn't helpful from an accessibility perspective. Obviously folk can hear when levels become painful high, but how about we insert an audible warning when the user crosses the threshold? I'd suggest we do both of the following to indicate an audible warning: 1) Mute (or atleast lower) the currently playing audio streams. 2) Play two beeps in quick succession (at the original volume level prior to mute/lowering). Once the beeps have been played, the volume level will be restored to the appropriate (higher) level. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1399710/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1399710] Re: no audible warning of high volume level
Another use-case for this is if you start playing music, lock the screen and put the phone in your pocket. Realising the volume is too low, you raise it without removing the phone from your pocket. Again, we should warn the user that they are about to cross the threshold somehow as they are not currently looking at the screen (which is off anyway). -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1399710 Title: no audible warning of high volume level Status in Ubuntu UX bugs: New Status in indicator-sound package in Ubuntu: Incomplete Bug description: Additional to the work done on bug 1373404, I think we need to consider adding an audio warning when the volume crosses the threshold value. The way android works is that the user is asked if they want to allow higher volume levels (they must click "ok"). Our approach is to just display a visual warning. That's fine (assuming it complies with all legal regs), but it isn't helpful from an accessibility perspective. Obviously folk can hear when levels become painful high, but how about we insert an audible warning when the user crosses the threshold? I'd suggest we do both of the following to indicate an audible warning: 1) Mute (or atleast lower) the currently playing audio streams. 2) Play two beeps in quick succession (at the original volume level prior to mute/lowering). Once the beeps have been played, the volume level will be restored to the appropriate (higher) level. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1399710/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1345505] Re: lock screen leaks keystrokes to window "behind" greeter
I've found a way to trigger this without needing to suspend (which hopefully will make it easier to debug :-)... 1) Open a terminal. 2) Run: "sleep 5 && gnome-terminal --maximize" 3) Quickly (before 5 seconds has elapsed), press "CTRL+l" to lock the screen. 4) Don't touch keyboard or mouse for about 10 seconds to give the lock screen time to dim the screen to black. 5) *Before* the cursor disappears (normally happens about 2 seconds after the screen is fully black), tpe random characters or hold down a key continually until the lock screen is displayed again. 6) Either delete the characters in the password box and reenter you actual password, or press return and enter you actual password. 7) Observe that the maximised gnome-terminal that is now revealed shows atleast a subset of the keys you typed when the screen was locked. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1345505 Title: lock screen leaks keystrokes to window "behind" greeter Status in “unity” package in Ubuntu: New Bug description: When my machine comes out of suspend, I am shown the lightdm greeter. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345505/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: upstart Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1235649 Title: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch Status in Touch Landing Plan: Fix Released Status in Unity: Confirmed Status in Upstart: Fix Released Status in “linux” package in Ubuntu: Invalid Status in “systemd” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Confirmed Status in “upstart” package in Ubuntu: Fix Released Status in “linux” source package in Saucy: Invalid Status in “systemd” source package in Saucy: Invalid Status in “unity” source package in Saucy: Confirmed Status in “upstart” source package in Saucy: Fix Released Bug description: using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir. running the same session with surfaceflinger only consumes 1MB per minute. in both cases the system starts to swap heavily at some point, making the UI unresponsive. http://paste.ubuntu.com/6196223/ has the top output of a Mir session after 30min, the UI just got completely unresponsive when this snapshot was taken. http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger session where the screen was off for about 10min apparently the leak only occurs while the screen is on, it seems to be permanently there but in the case of surfaceflinger it hits less hard. To manage notifications about this bug go to: https://bugs.launchpad.net/landing-plan/+bug/1235649/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1349128] Re: Ubuntu 14.04 lock screen doesn't accept keyboard input (until using indicators)
@n-zbuntu-4: actually, it can - see https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345505/comments/3 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1349128 Title: Ubuntu 14.04 lock screen doesn't accept keyboard input (until using indicators) Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: Ubuntu 14.04 login screen doesn't accept keyboard input in the password box after my system has resumed from a sleep (=lid opening), so I can't relogin anymore Excpected behaviour: the login screen should accept keyboard input and show them as stars in the password box. Workaround: click on any indicator in the upper right corner, and close the menu. After that, keyboard input is accepted again. $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 System is fully updated. Problem started to happen one or two weeks ago, so around mid July 2014. === A way to reproduce this is described at: - https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345505/comments/6 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349128/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1351389] [NEW] power off / restart and cancel buttoms too close together
Public bug reported: The 3 buttons are currently stacked vertically but: 1) The spacing between them looks cramped. 2) The height of each button is too low to be comfortable. If you compare this menu with the Android equivalent, on Android the buttons actually touch _but_ they are atleast as tall as a finger is wide. This seems like a good policy wrt height. We don't appear to be space-constrained here so I'd suggest making the buttoms more spaced out and taller. ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1351389 Title: power off / restart and cancel buttoms too close together Status in “indicator-power” package in Ubuntu: New Bug description: The 3 buttons are currently stacked vertically but: 1) The spacing between them looks cramped. 2) The height of each button is too low to be comfortable. If you compare this menu with the Android equivalent, on Android the buttons actually touch _but_ they are atleast as tall as a finger is wide. This seems like a good policy wrt height. We don't appear to be space-constrained here so I'd suggest making the buttoms more spaced out and taller. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1351389/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1352253] [NEW] hotkey to toggle microphone mute (ALT + F4) shows a speaker, not a microphone
Public bug reported:
This is incorrect for 2 reasons:
1) The overlay should show a microphone icon since that is what is being
toggled.
2) It's currently using the same icon as the speaker / sound output mute hotkey
(ALT + F1).
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute':
(true, '', []), 'phone-settings': (true, '', []), 'mic-volume': (true,
'', [<0.510009765625>]), 'scroll': (true, 'i', []), 'vlc.desktop': (true, '',
[<{'running': , 'state': <'Paused'>}>]), 'previous.vlc.desktop': (true,
'', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '',
[<{'running': , 'state': <'Paused'>}>]), 'previous.rhythmbox.desktop':
(true, '', []), 'volume': (true, 'i', [<0.350067138671875>]),
'play-playlist.vlc.desktop': (true, 's', []), 'root': (true, '', [<{'title':
<'Son'>, 'accessible-desc': <'Volume (35%)'>, 'icon': <('themed',
<['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume',
'audio']>)>, 'visible': }>]), 'play.rhythmbox.desktop': (true, '',
[<'Paused'>]), 'play-playlist.rhythmbox.desktop': (true, 's', []),
'next.rhythmbox.desktop': (true, '', []), 'play.vlc.desktop': (true, '',
[<'Paused'>])},)
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Aug 4 10:39:43 2014
InstallationDate: Installed on 2014-04-11 (114 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to utopic on 2014-05-08 (87 days ago)
** Affects: indicator-sound (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug utopic
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1352253
Title:
hotkey to toggle microphone mute (ALT + F4) shows a speaker, not a
microphone
Status in “indicator-sound” package in Ubuntu:
New
Bug description:
This is incorrect for 2 reasons:
1) The overlay should show a microphone icon since that is what is being
toggled.
2) It's currently using the same icon as the speaker / sound output mute
hotkey (ALT + F1).
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-sound 12.10.2+14.10.20140611-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ActionStates: ({'next.vlc.desktop': (true, signature '', @av []), 'mute':
(true, '', []), 'phone-settings': (true, '', []), 'mic-volume': (true,
'', [<0.510009765625>]), 'scroll': (true, 'i', []), 'vlc.desktop': (true, '',
[<{'running': , 'state': <'Paused'>}>]), 'previous.vlc.desktop': (true,
'', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop': (true, '',
[<{'running': , 'state': <'Paused'>}>]), 'previous.rhythmbox.desktop':
(true, '', []), 'volume': (true, 'i', [<0.350067138671875>]),
'play-playlist.vlc.desktop': (true, 's', []), 'root': (true, '', [<{'title':
<'Son'>, 'accessible-desc': <'Volume (35%)'>, 'icon': <('themed',
<['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume',
'audio']>)>, 'visible': }>]), 'play.rhythmbox.desktop': (true, '',
[<'Paused'>]), 'play-playlist.rhythmbox.desktop': (true, 's', []),
'next.rhythmbox.desktop': (true, '', []), 'play.vlc.desktop': (true, '',
[<'Paused'>])},)
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Aug 4 10:39:43 2014
InstallationDate: Installed on 2014-04-11 (114 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409)
SourcePackage: indicator-sound
UpgradeStatus: Upgraded to utopic on 2014-05-08 (87 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1352253/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1352449] [NEW] reminders expire when screen off
Public bug reported: Occaionally my phone makes the usual wood-tap sound to tell me there is a reminder. But if I don't press the power button to put the screen on within a few seconds, the reminder is expired and removed from the display before I have had a chance to view them. This is fine if I *do* actually hear the reminder tone since I can look at the Upcoming pull-down, but what if I don't hear it? We should consider taking the approach used by iOS and Android to display these items until the user takes some action if the screen is off at the time the reminders occur. ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1352449 Title: reminders expire when screen off Status in “indicator-messages” package in Ubuntu: New Bug description: Occaionally my phone makes the usual wood-tap sound to tell me there is a reminder. But if I don't press the power button to put the screen on within a few seconds, the reminder is expired and removed from the display before I have had a chance to view them. This is fine if I *do* actually hear the reminder tone since I can look at the Upcoming pull-down, but what if I don't hear it? We should consider taking the approach used by iOS and Android to display these items until the user takes some action if the screen is off at the time the reminders occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1352449/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1355706] [NEW] Indicator icon should be monochrome
Public bug reported: Currrently, if you have undisplayed notifications, the notification icon shows as a green bell. Since all the other notification icons are monochromatic, I think the behaviour should be: - no undisplayed notifications: show an unfilled white bell (or simply don't display the icon?) - undisplayed notifications: show a filled white bell. Using image r185. ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1355706 Title: Indicator icon should be monochrome Status in “indicator-messages” package in Ubuntu: New Bug description: Currrently, if you have undisplayed notifications, the notification icon shows as a green bell. Since all the other notification icons are monochromatic, I think the behaviour should be: - no undisplayed notifications: show an unfilled white bell (or simply don't display the icon?) - undisplayed notifications: show a filled white bell. Using image r185. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1355706/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357252] Re: Upstart jobs specifying cgroup fail to start occasionally
** Also affects: systemd-shim (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: Upstart jobs specifying cgroup fail to start occasionally Status in Ubuntu Application Launcher: Incomplete Status in Upstart: In Progress Status in “cgmanager” package in Ubuntu: Confirmed Status in “systemd-shim” package in Ubuntu: New Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357252] Re: Upstart jobs specifying cgroup fail to start occasionally
After a lot of testing, I think I've found the cause - when lightdm starts the session init, logind is supposed to setup the cgroups. But that isn't happening. Normally, logind would do that by asking systemd, but in our case it talks to systemd-shim. sytemd-shim then asks cgmanager to create the cgroups. However, currently systemd-shim does not fail if cgmanager cannot be contacted. So I think the proper fix is to change systemd- shim to either block or fail hard if cgmanager is not contactable or unable to create the requested cgroups. It would also be beneficial to arrange for systemd-shim output to be captured since currently all stdout and stderr is discarded when it is run via /usr/share/dbus-1 /system-services/org.freedesktop.systemd1.service. A "quick fix" however is to change dbus's 'start on' condition to ensure it doesn't start until cgmanager is ready. The simplest fix being: $ echo "start on cgmanager-ready" | sudo tee -a /etc/init/dbus.override -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: Upstart jobs specifying cgroup fail to start occasionally Status in Ubuntu Application Launcher: Incomplete Status in Upstart: Invalid Status in “cgmanager” package in Ubuntu: Confirmed Status in “systemd-shim” package in Ubuntu: New Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357252] Re: Upstart jobs specifying cgroup fail to start occasionally
** Changed in: upstart Status: In Progress => Invalid ** Changed in: upstart Importance: Critical => Undecided -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: Upstart jobs specifying cgroup fail to start occasionally Status in Ubuntu Application Launcher: Incomplete Status in Upstart: Invalid Status in “cgmanager” package in Ubuntu: Confirmed Status in “systemd-shim” package in Ubuntu: New Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357252] Re: Upstart jobs specifying cgroup fail to start occasionally
** Changed in: systemd-shim (Ubuntu) Assignee: (unassigned) => Stéphane Graber (stgraber) ** Summary changed: - Upstart jobs specifying cgroup fail to start occasionally + systemd-shim fails to handle cgmanager being unavailable -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: systemd-shim fails to handle cgmanager being unavailable Status in Ubuntu Application Launcher: Incomplete Status in Upstart: Invalid Status in “cgmanager” package in Ubuntu: Confirmed Status in “systemd-shim” package in Ubuntu: New Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357252] Re: upstart can race with cgmanager when using remove-on-empty
** Summary changed: - systemd-shim fails to handle cgmanager being unavailable + upstart can race with cgmanager when using remove-on-empty ** Changed in: upstart Status: Invalid => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: upstart can race with cgmanager when using remove-on-empty Status in Ubuntu Application Launcher: Invalid Status in Upstart: In Progress Status in “cgmanager” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357252] Re: upstart can race with cgmanager when using remove-on-empty
>From @teds findings: "The Upstart job creates the cgroup as it goes through each phase in the job, but it sets the cgroup to be destroyed when all of its PIDs are gone. When starting the second or later task (what ever that might be, seems to be post-stop a lot though) there is then a race between starting that task and the cgroup being destroyed if all of the PIDs in the group have exited with the main job. On entering the function to create the task the group is created, and if right then cgmanager realizes the PIDs are gone it deletes it before the new PID can be added." The solution is to not mark created cgroups 'remove-on-empty' immediately after they are created, but instead to request cgmanager mops up the cgroups after the last job processes cgroups have been created. Note that this approach works correctly for system jobs which specify the cgroup stanza. However, it is not currently reliable for session jobs since because logind does not clean up cgroups itself, systemd-shim arranges for this to happen on behalf of the users session by marking the logind-created cgroups 'remove-on-empty' and letting cgmanager clean up which brings us back to the problem which the upstart changes are designed to fix. So, further works is required to resolve this problem by enhancing systemd-shim to implement 'abandoncgroup' and 'stopsession' so that logind works as expected. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: upstart can race with cgmanager when using remove-on-empty Status in Ubuntu Application Launcher: Invalid Status in Upstart: In Progress Status in “cgmanager” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1363134] [NEW] systemd-shim needs to grow support for abandoncgroup and stopsession
Public bug reported: The fix for upstart bug 1357252 has highlighted the fact that systemd- shim does not support functionality required by logind, namely: - abandoncgroup (delete if possible) - stopsession(kill all tasks and remove cgroup) Because of this, systemd-shim sets the remove-on-empty bit on all cgroups that are created under the users logind session. As a result, when an upstart user job running under the upstart session init asks cgmanager to create a cgroup, that cgroup is created and inherits the remove-on-empty bit set by systemd-shim. This can result in failed upstart jobs since when a subsequent job process (a secondary process that runs as part of a single overall upstart job) is started by upstart, it may fail to move the pid into the already-created cgroup since cgmanager may have (just) deleted it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 7-1 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 29 16:21:28 2014 InstallationDate: Installed on 2014-04-11 (139 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: systemd-shim UpgradeStatus: Upgraded to utopic on 2014-05-08 (113 days ago) ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1363134 Title: systemd-shim needs to grow support for abandoncgroup and stopsession Status in “systemd-shim” package in Ubuntu: New Bug description: The fix for upstart bug 1357252 has highlighted the fact that systemd- shim does not support functionality required by logind, namely: - abandoncgroup (delete if possible) - stopsession(kill all tasks and remove cgroup) Because of this, systemd-shim sets the remove-on-empty bit on all cgroups that are created under the users logind session. As a result, when an upstart user job running under the upstart session init asks cgmanager to create a cgroup, that cgroup is created and inherits the remove-on-empty bit set by systemd-shim. This can result in failed upstart jobs since when a subsequent job process (a secondary process that runs as part of a single overall upstart job) is started by upstart, it may fail to move the pid into the already-created cgroup since cgmanager may have (just) deleted it. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd-shim 7-1 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 29 16:21:28 2014 InstallationDate: Installed on 2014-04-11 (139 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: systemd-shim UpgradeStatus: Upgraded to utopic on 2014-05-08 (113 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1363134/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357252] Re: upstart can race with cgmanager when using remove-on-empty
Bug 1363134 raised for the systemd-shim work. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: upstart can race with cgmanager when using remove-on-empty Status in Ubuntu Application Launcher: Invalid Status in Upstart: In Progress Status in “cgmanager” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1365535] Re: Desktop fails to start properly after 14.04 > 14.10
This sounds like a unity issue as I've seen no evidence of Upstart misbehaving yet. That .xsession-errors log would be useful to have if you can attach it though. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1365535 Title: Desktop fails to start properly after 14.04 > 14.10 Status in “unity” package in Ubuntu: New Status in “upstart” package in Ubuntu: New Bug description: Yesterday I upgraded my laptop from 14.04 to 14.10 - after the upgrade, when I logged in, I saw Unity on the left with the icons I expected, and the bar across the top, however the time and date, network indicator icon, sound icon, etc were missing.. Clicking on any of the icons in Unity didn't load anything... Couldn't load the dash.. Keyboard shortcuts such as ctrl+alt+t failed to load the terminal. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Thu Sep 4 10:30:43 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-29 (66 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: Session UpstartRunningSessionCount: 1 UpstartRunningSessionVersion: upstart 1.13.1 UpstartRunningSystemVersion: init (upstart 1.13.1) mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-08-28T00:30:06 mtime.conffile..etc.cron.daily.upstart: 2014-08-28T00:35:25 mtime.conffile..etc.upstart.xsessions: 2014-08-28T00:30:06 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1365535/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1365875] [NEW] mail notification displayed even when phone locked
Public bug reported: I had just woken up the phone (screen was displaying the welcome greeter) but had not yet unlocked the device (I have set a pin code) when a mail notification appeared on screen that divulged the sender. This is a privacy issue. ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1365875 Title: mail notification displayed even when phone locked Status in “indicator-messages” package in Ubuntu: New Bug description: I had just woken up the phone (screen was displaying the welcome greeter) but had not yet unlocked the device (I have set a pin code) when a mail notification appeared on screen that divulged the sender. This is a privacy issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1365875/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357252] Re: upstart can race with cgmanager when using remove-on-empty
** Changed in: upstart Status: In Progress => Fix Released ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New ** Changed in: upstart (Ubuntu) Assignee: (unassigned) => James Hunt (jamesodhunt) ** Changed in: upstart (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: upstart can race with cgmanager when using remove-on-empty Status in Ubuntu Application Launcher: Invalid Status in Upstart: Fix Released Status in “cgmanager” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1365875] Re: mail notification displayed even when phone locked
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1365875 Title: mail notification displayed even when phone locked Status in The Unity 8 shell: New Status in “indicator-messages” package in Ubuntu: New Bug description: I had just woken up the phone (screen was displaying the welcome greeter) but had not yet unlocked the device (I have set a pin code) when a mail notification appeared on screen that divulged the sender. This is a privacy issue. To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1365875/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1369468] [NEW] no warning when volume increased to maximum and headphones plugged
Public bug reported: Android gives the user a warning if they attempt to raise the volume to 100% when headphones are plugged. This is a sensible precaution both to save the user from tinnitus and to avoid any potential legal repercussions. ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1369468 Title: no warning when volume increased to maximum and headphones plugged Status in “indicator-sound” package in Ubuntu: New Bug description: Android gives the user a warning if they attempt to raise the volume to 100% when headphones are plugged. This is a sensible precaution both to save the user from tinnitus and to avoid any potential legal repercussions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1369468/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1357252] Re: upstart can race with cgmanager when using remove-on-empty
Back link to test plan: https://wiki.ubuntu.com/Process/TestPlans /systemd-shim -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1357252 Title: upstart can race with cgmanager when using remove-on-empty Status in Ubuntu Application Launcher: Invalid Status in Upstart: Fix Released Status in “cgmanager” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Status in “upstart” package in Ubuntu: Fix Released Status in “cgmanager” package in Ubuntu RTM: Fix Released Status in “upstart” package in Ubuntu RTM: Fix Released Bug description: After the ubuntu-app-launch landing in #188 (http://people.canonical.com/~ogra/touch-image-stats/188.changes), UI Toolkit autopilot tests have started failing, see http://ci.ubuntu.com/smokeng/utopic/touch/mako/190:20140815:20140811.1/9676/ubuntuuitoolkit/ and the #188 results too. It's different tests each time, but a bit above 10 of them tend to fail on each full run. Reproducable locally, where I got 11 such failures. To reproduce: [terminal 1] 1. flash/update device if needed 2. adb shell 3. apt install ubuntu-ui-toolkit-autopilot 4. powerd-cli display on bright # leave running, also unlock the screen so that lenses are shown [terminal 2] 5. phablet-config autopilot --dbus-probe enable # wait until finishes 6. phablet-test-run ubuntuuitoolkit A full test suite run will take around 0.5h and should produce a bunch of 'Application failed to start.':s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-app-launch/+bug/1357252/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
Just got this running hud 14.10+14.10.20140924-0ubuntu1. Just typing in a console and my CPU chewing script popped up a window to alert me to the fact. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () fr
