[Dx-packages] [Bug 1642634] Re: indicator-datetime uses excessive memory
@rael-gc is experiencing this issue still with 18.04 on duplicate bug post... https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1652789 -- 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/1642634 Title: indicator-datetime uses excessive memory Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: On my Aquaris 4.5, OTA-13, indicator-datetime 15.10+15.04.20160820.1-0ubuntu1, it uses too much RSS. A typical RSS is 315892, almost three times as much as unity8. I believe this is an OTA regression. I'm not sure if it regressed from OTA-11 or OTA-12. Just now, I got caught in an oom killer loop with constant killing of unity8-dash because of this, making my phone unusable. I had to kill indicator-datetime manually. It then restarted automatically and now uses 80456 RSS only. I see bug 1633319 exists complaining about a memory leak. It's not exactly the same version since mine is 15.10+15.04.20160820.1-0ubuntu1 and that one is 15.10+16.10.20160820.1-0ubuntu1. But perhaps the upstream versions are the same or something? Perhaps the two are dupes, but I'll let someone more familiar make that determination. I have only a handful of alarms (perhaps five on average; rarely more) but I do have my Google calendar syncing with perhaps hundreds of events. However, there's no reason that this should cause indicator- datetime to use more RSS; it shouldn't be keeping these in memory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642634/+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 1652789] Re: indicator-datetime-service using high volumes of ram/memory
*** This bug is a duplicate of bug 1642634 *** https://bugs.launchpad.net/bugs/1642634 I feel your pain -- 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/1652789 Title: indicator-datetime-service using high volumes of ram/memory Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I have noticed every time my computer boots into Ubuntu, it freezes up with the mouse lagging and then unfreezes. I notice the SSD making huge amounts of read/writes (which I imagine is into virtual memory/swap space). I have to leave the computer for 15 mins or so before coming back to it. I noticed `indicator-datetime-service` was using a lot of RAM in `System Monitor`. So I killed it, and it comes back again each time I kill the process. So I clicked 'Stop' with has seemed to have temporary fixed the problem. Obviously now the correct time is not displayed on the task bar. indicator-datetime: Installed: 15.10+16.10.20160820.1-0ubuntu1 Candidate: 15.10+16.10.20160820.1-0ubuntu1 Version table: *** 15.10+16.10.20160820.1-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status Description:Ubuntu 16.10 Release:16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1652789/+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 1652789] Re: indicator-datetime-service using high volumes of ram/memory
*** This bug is a duplicate of bug 1642634 *** https://bugs.launchpad.net/bugs/1642634 Happened to me on 18.04 (with Unity). To the point that my system got frozen with indicator-datetime-service consuming 11.5 GB of 16GB RAM. -- 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/1652789 Title: indicator-datetime-service using high volumes of ram/memory Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I have noticed every time my computer boots into Ubuntu, it freezes up with the mouse lagging and then unfreezes. I notice the SSD making huge amounts of read/writes (which I imagine is into virtual memory/swap space). I have to leave the computer for 15 mins or so before coming back to it. I noticed `indicator-datetime-service` was using a lot of RAM in `System Monitor`. So I killed it, and it comes back again each time I kill the process. So I clicked 'Stop' with has seemed to have temporary fixed the problem. Obviously now the correct time is not displayed on the task bar. indicator-datetime: Installed: 15.10+16.10.20160820.1-0ubuntu1 Candidate: 15.10+16.10.20160820.1-0ubuntu1 Version table: *** 15.10+16.10.20160820.1-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status Description:Ubuntu 16.10 Release:16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1652789/+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 1861481] Re: language-options causes live CD sessions to be untranslated
The reason that this regression doesn't affect ubuntu-desktop, might be that unlike LightDM, GDM doesn't have that Ubuntu-specific patch to use /usr/share/language-tools/language-options. So, I subscribed "lightdm (Ubuntu)" to the affected packages, in case we just want to drop the Ubuntu-specific patch, and that way make lightdm not pass LANGUAGE when it shouldn't. I think that this won't address the source of the regression, but it will make the problem not appear in flavors that use lightdm which should be good enough. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in accountsservice package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+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
