[Dx-packages] [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked
Comment #13 describes a problem with a different alarm sound played then expected. I believe that could be the same situation as in bug #1596924 (sound change need to be confirmed) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1588526 Title: [mako] Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+subscriptions -- Mailing list: https://launchpad.net/~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 1633319] Re: memory leak in indicator-datetime
@April_J No my hardware is Samsung -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-datetime-service is consuming all the system memory from 3.7GB up to 32 GB in 30 seconds. The system kills the indicator- datetime-service process and indicator-datetime-service restarts and memory consumption repeats until killed again. All swap memory is consumed in this pattern. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 00:12:00 2016 EcryptfsInUse: Yes SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked
The suggestion of no longer supporting the Nexus 4 (comment #24) is worrying, as there are no current OEM devices for sale and few enough supported models. This deprecation isn't mentioned anywhere else (that I could find) and flies in the face of these current pages: https://developer.ubuntu.com/en/phone/devices/ https://developer.ubuntu.com/en/phone/devices/devices/ This doesn't *appear* to be the official line from Canonical and probably shouldn't be stated as fact or used as the basis for any decisions until confirmed in a more official capacity. I've just updated the clock app on my Nexus 4 to version 3.8.487. The update's fix list doesn't mention a fix for the alarm issue discussed above, so I'll continue testing because I care about this (as do others). I don't plan to change device any time soon either! ;) Additionally, comment #13 above describes the bug affecting the BQ Aquarius M10, not the Nexus 4. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1588526 Title: [mako] Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+subscriptions -- Mailing list: https://launchpad.net/~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 1633319] Re: memory leak in indicator-datetime
Ran valgrind on the indicator-datetime-service with the following command trying to track down the origin of the issue. The following command and parameters were used: G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service ** Attachment added: "valgrind.log" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+attachment/4761235/+files/valgrind.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-datetime-service is consuming all the system memory from 3.7GB up to 32 GB in 30 seconds. The system kills the indicator- datetime-service process and indicator-datetime-service restarts and memory consumption repeats until killed again. All swap memory is consumed in this pattern. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 00:12:00 2016 EcryptfsInUse: Yes SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1633558] [NEW] indicator-applet is using 100% of cpu and initctl too in ubuntu 16.10
Public bug reported: The computer is working slow, not programm running and 100% of cpu for indicator-applet and 100% of cpu for initctl, I don't know if there is a relation or are different reasons for each process. System updated to ubuntu 16.10 from 16.04 and gnome-panel. If I kill it: killall indicator-applet-complete It asks for restart and no more cpu usage after restart. initctl keeps at 99% after that so probably are different problems. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-applet-complete 12.10.2+15.04.20141127.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm wl nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Oct 14 18:55:55 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-applet-complete InstallationDate: Installed on 2016-04-29 (167 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_ES PATH=(custom, no user) LANG=es_ES.UTF-8 SourcePackage: indicator-applet UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) ** Affects: indicator-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety ** Description changed: The computer is working slow, not programm running and 100% of cpu for indicator-applet and 100% of cpu for initctl, I don't know if there is a relation or are different reasons for each process. aded ubuntu 16.10 from 16.04 and gnome-panel. + + If I kill it kill: + killall indicator-applet-complete + + It asks for restart and no more cpu usage after restart. + + initctl keeps at 99% after that so probably are different problems. + ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-applet-complete 12.10.2+15.04.20141127.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm wl nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Oct 14 18:55:55 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-applet-complete InstallationDate: Installed on 2016-04-29 (167 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: - XDG_RUNTIME_DIR= - SHELL=/bin/bash - LANGUAGE=es_ES - PATH=(custom, no user) - LANG=es_ES.UTF-8 + XDG_RUNTIME_DIR= + SHELL=/bin/bash + LANGUAGE=es_ES + PATH=(custom, no user) + LANG=es_ES.UTF-8 SourcePackage: indicator-applet UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) ** Description changed: The computer is working slow, not programm running and 100% of cpu for indicator-applet and 100% of cpu for initctl, I don't know if there is a relation or are different reasons for each process. aded ubuntu 16.10 from 16.04 and gnome-panel. - If I kill it kill: + If I kill it: killall indicator-applet-complete It asks for restart and no more cpu usage after restart. initctl keeps at 99% after that so probably are different problems. - ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-applet-complete 12.10.2+15.04.20141127.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm wl nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Oct 14 18:55:55 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-applet-complete InstallationDate: Installed on 2016-04-29 (167 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_ES PATH=(custom, no user) LANG=es_ES.UTF-8 SourcePackage: indicator-applet UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) ** Description changed: The computer is working slow, not programm running and 100% of cpu for indicator-applet and 100% of cpu for initctl, I don't know if there is a relation or are different reasons for each process. - aded ubuntu 16.10 from 16.04 and gnome-panel. + System updated to ubuntu 16.10 from 16.04 and gnome-panel. If I kill it: killall indicator-applet-complete It asks for restart and no more cpu usage after restart. initctl keeps at 99% after that so probably are different problems. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-applet-complete 12.10.2+15.04.20141127.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
[Dx-packages] [Bug 1633319] Re: memory leak in indicator-datetime
@dklongley -- Can you let me know if you're also running on System76 hardware? I am attempting to reproduce this now. Thank you! -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-datetime-service is consuming all the system memory from 3.7GB up to 32 GB in 30 seconds. The system kills the indicator- datetime-service process and indicator-datetime-service restarts and memory consumption repeats until killed again. All swap memory is consumed in this pattern. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 00:12:00 2016 EcryptfsInUse: Yes SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list
** Branch linked: lp:~3v1n0/unity8/calendar-day-selection -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1541125 Title: Clicking a date in the new calendar doesn't change the indicator's appointment list Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: Invalid Status in qmenumodel package in Ubuntu: In Progress Status in ubuntu-settings-components package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Triaged Bug description: Now that we've got a calendar in indicator-datetime in Unity 8, there are a few features from Unity 7 that we should decide if/how we're goint to handle in Unity 8. * Show Week Numbers * Highlight days of the month that include appointments * Unity tells indicator-datetime what calendar day has been clicked so that the "upcoming appointments" list can be adjusted accordingly These are currently implemented as fields in a GAction state dictionary and documented in http://bazaar.launchpad.net/~indicator- applet-developers/indicator-datetime/trunk.15.10/view/head:/README ... however that was all done for Unity 7, and IMO it would make sense to improve the unity<->indicator API here so that Unity8 doesn't have to deal with key-variant map GAction states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1541125/+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 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list
** Also affects: qmenumodel (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-settings-components (Ubuntu) Importance: Undecided Status: New ** Changed in: qmenumodel (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-settings-components (Ubuntu) Status: New => Fix Committed ** Changed in: ubuntu-settings-components (Ubuntu) Status: Fix Committed => In Progress ** Changed in: ubuntu-settings-components (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: qmenumodel (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: indicator-datetime (Ubuntu) Status: New => Invalid ** Changed in: qmenumodel (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-settings-components (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1541125 Title: Clicking a date in the new calendar doesn't change the indicator's appointment list Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: Invalid Status in qmenumodel package in Ubuntu: In Progress Status in ubuntu-settings-components package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Triaged Bug description: Now that we've got a calendar in indicator-datetime in Unity 8, there are a few features from Unity 7 that we should decide if/how we're goint to handle in Unity 8. * Show Week Numbers * Highlight days of the month that include appointments * Unity tells indicator-datetime what calendar day has been clicked so that the "upcoming appointments" list can be adjusted accordingly These are currently implemented as fields in a GAction state dictionary and documented in http://bazaar.launchpad.net/~indicator- applet-developers/indicator-datetime/trunk.15.10/view/head:/README ... however that was all done for Unity 7, and IMO it would make sense to improve the unity<->indicator API here so that Unity8 doesn't have to deal with key-variant map GAction states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1541125/+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 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list
** Branch linked: lp:~3v1n0/qmenumodel/variant-string-parser -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1541125 Title: Clicking a date in the new calendar doesn't change the indicator's appointment list Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: Now that we've got a calendar in indicator-datetime in Unity 8, there are a few features from Unity 7 that we should decide if/how we're goint to handle in Unity 8. * Show Week Numbers * Highlight days of the month that include appointments * Unity tells indicator-datetime what calendar day has been clicked so that the "upcoming appointments" list can be adjusted accordingly These are currently implemented as fields in a GAction state dictionary and documented in http://bazaar.launchpad.net/~indicator- applet-developers/indicator-datetime/trunk.15.10/view/head:/README ... however that was all done for Unity 7, and IMO it would make sense to improve the unity<->indicator API here so that Unity8 doesn't have to deal with key-variant map GAction states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1541125/+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 1633319] Re: memory leak in indicator-datetime
I get the same as described by the original poster. I have disabled the service for now. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1633319 Title: memory leak in indicator-datetime Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 16.10 on the System76 Serval WS indicator-datetime-service is consuming all the system memory from 3.7GB up to 32 GB in 30 seconds. The system kills the indicator- datetime-service process and indicator-datetime-service restarts and memory consumption repeats until killed again. All swap memory is consumed in this pattern. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 00:12:00 2016 EcryptfsInUse: Yes SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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
