[Dx-packages] [Bug 1589605] Re: evolution-calendar-factory uses lots of memory
Even large memory usage for 16.04 clean install with empty calendar and without any online accounts added. ** Changed in: evolution-data-server (Ubuntu) Status: Expired => 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/1589605 Title: evolution-calendar-factory uses lots of memory Status in evolution package in Ubuntu: Invalid Status in evolution-data-server package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Expired Bug description: As filed under bug #1342123 (under Canonical System Image, i.e. for mobile installs) by several users, including desktop installs, evolution-calendar-factory (previsouly in 14.04) then evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of megabytes of memory (~ 300 Mio in my case). This might have to do with having lots of linked calendars (Google Agenda or other). Another user on my system has much fewer Google Agendas than me and her memory usage of evolution-calendar-factory-subprocess is less, but still close to 100 Mio. There have been random crashes of the process, mostly directly upon login, always caused by addressing memory out of range. There used to be a workaround by invoking the process a second time, which caused it to exit more or less gracefully. This is not the case anymore in 16.04. Unfortunately, searching Google leads to the bug #1342123 which concerns "Canonical System Image", and several users have replied even though it does not only concern mobile installs, which is not immediately self-evident when you are not aware what "Canonical System Image" stands for… To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+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 798153] Re: metacity should support _NET_RESTACK_WINDOW
** Changed in: unity-2d (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/798153 Title: metacity should support _NET_RESTACK_WINDOW Status in Unity: Incomplete Status in unity-2d: New Status in metacity package in Ubuntu: Invalid Status in unity package in Ubuntu: Incomplete Status in unity-2d package in Ubuntu: Incomplete Bug description: Binary package hint: metacity Metacity (and hopefully mutter), should support the atom _NET_RESTACK_WINDOW ad explained in this specification: http://standards.freedesktop.org/wm-spec/wm-spec-1.3.html#id2506866 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/798153/+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 1350523] Re: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.
Hello Carla, or anyone else affected, Accepted frame into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/frame/2.5.0daily13.06.05+16.04.20160809-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: frame (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to frame in Ubuntu. https://bugs.launchpad.net/bugs/1350523 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. Status in frame: In Progress Status in compiz package in Ubuntu: Won't Fix Status in frame package in Ubuntu: Fix Released Status in compiz source package in Xenial: Invalid Status in frame source package in Xenial: Fix Committed Bug description: [Impact] Unity might crash on systems with touch screen or multi-gesture supporting touchpads. [Test case] The crash is pretty random, it happens in some cases where unity is locked and after a suspension. Without having to touch any input. [Regression Potential] Regression potential: fix is very safe. We're just removing asserts in code, returning safe values and printing errors instead. Not sure if the cause is running autopilot tests. ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AssertionMessage: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. 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] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 30 21:46:07 2014 DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2014-02-13 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) MachineType: System manufacturer System Product Name ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7 Signal: 6SourcePackage: compiz StacktraceTop: __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92 __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101 frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N
[Dx-packages] [Bug 1350523] Re: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.
** Description changed: + [Impact] + + Unity might crash on systems with touch screen or multi-gesture + supporting touchpads. + + [Test case] + + The crash is pretty random, it happens in some cases where unity is + locked and after a suspension. Without having to touch any input. + + [Regression Potential] + + Regression potential: fix is very safe. We're just removing asserts in + code, returning safe values and printing errors instead. + + Not sure if the cause is running autopilot tests. - ProblemType: Crash - DistroRelease: Ubuntu 14.10 + ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: - + .tmp.unity.support.test.1: - + ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AssertionMessage: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. 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] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 30 21:46:07 2014 DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: - NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: NVIDIA Corporation Device [10de:0491] + NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2014-02-13 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) MachineType: System manufacturer System Product Name ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7 - Signal: 6 - SourcePackage: compiz + Signal: 6SourcePackage: compiz StacktraceTop: - __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92 - __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101 - frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6 - ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 - ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 + __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92 + __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101 + frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6 + ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 + ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1
[Dx-packages] [Bug 1350523] Re: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.
** Also affects: frame (Ubuntu) Importance: Undecided Status: New ** Also affects: compiz (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: frame (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: compiz (Ubuntu Xenial) Status: New => Invalid ** Changed in: frame (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to frame in Ubuntu. https://bugs.launchpad.net/bugs/1350523 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. Status in frame: In Progress Status in compiz package in Ubuntu: Won't Fix Status in frame package in Ubuntu: Fix Released Status in compiz source package in Xenial: Invalid Status in frame source package in Xenial: New Bug description: [Impact] Unity might crash on systems with touch screen or multi-gesture supporting touchpads. [Test case] The crash is pretty random, it happens in some cases where unity is locked and after a suspension. Without having to touch any input. [Regression Potential] Regression potential: fix is very safe. We're just removing asserts in code, returning safe values and printing errors instead. Not sure if the cause is running autopilot tests. ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AssertionMessage: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. 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] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 30 21:46:07 2014 DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2014-02-13 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) MachineType: System manufacturer System Product Name ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7 Signal: 6SourcePackage: compiz StacktraceTop: __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92 __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101 frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
[Dx-packages] [Bug 798153] Re: metacity should support _NET_RESTACK_WINDOW
** Changed in: metacity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/798153 Title: metacity should support _NET_RESTACK_WINDOW Status in Unity: Incomplete Status in unity-2d: New Status in metacity package in Ubuntu: Invalid Status in unity package in Ubuntu: Incomplete Status in unity-2d package in Ubuntu: New Bug description: Binary package hint: metacity Metacity (and hopefully mutter), should support the atom _NET_RESTACK_WINDOW ad explained in this specification: http://standards.freedesktop.org/wm-spec/wm-spec-1.3.html#id2506866 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/798153/+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 1611466] Re: Calendar crashes on ESC typing.
what ubuntu version and desktop environment do you use? -- 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/1611466 Title: Calendar crashes on ESC typing. Status in indicator-datetime package in Ubuntu: Incomplete Bug description: When you click on date, it opens the calendar, if you type the ESC button on keyboard, the graphical interface crashes and in a few seconds it restart. During this few seconds or a minute, all the system stay frozen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1611466/+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 1611466] Re: Calendar crashes on ESC typing.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => High ** Changed in: indicator-datetime (Ubuntu) Status: New => Incomplete -- 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/1611466 Title: Calendar crashes on ESC typing. Status in indicator-datetime package in Ubuntu: Incomplete Bug description: When you click on date, it opens the calendar, if you type the ESC button on keyboard, the graphical interface crashes and in a few seconds it restart. During this few seconds or a minute, all the system stay frozen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1611466/+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 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
it was closed as invalid for indicator-power because the problem is in powerd ... so a new task against powerd was opened -- 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/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in powerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+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 1589605] Re: evolution-calendar-factory uses lots of memory
I can confirm it still exists on 16.04. Any news regarding this? -- 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/1589605 Title: evolution-calendar-factory uses lots of memory Status in evolution package in Ubuntu: Invalid Status in evolution-data-server package in Ubuntu: Expired Status in indicator-datetime package in Ubuntu: Expired Bug description: As filed under bug #1342123 (under Canonical System Image, i.e. for mobile installs) by several users, including desktop installs, evolution-calendar-factory (previsouly in 14.04) then evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of megabytes of memory (~ 300 Mio in my case). This might have to do with having lots of linked calendars (Google Agenda or other). Another user on my system has much fewer Google Agendas than me and her memory usage of evolution-calendar-factory-subprocess is less, but still close to 100 Mio. There have been random crashes of the process, mostly directly upon login, always caused by addressing memory out of range. There used to be a workaround by invoking the process a second time, which caused it to exit more or less gracefully. This is not the case anymore in 16.04. Unfortunately, searching Google leads to the bug #1342123 which concerns "Canonical System Image", and several users have replied even though it does not only concern mobile installs, which is not immediately self-evident when you are not aware what "Canonical System Image" stands for… To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+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 1589605] Re: evolution-calendar-factory uses lots of memory
on 16.04 btw -- 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/1589605 Title: evolution-calendar-factory uses lots of memory Status in evolution package in Ubuntu: Invalid Status in evolution-data-server package in Ubuntu: Expired Status in indicator-datetime package in Ubuntu: Expired Bug description: As filed under bug #1342123 (under Canonical System Image, i.e. for mobile installs) by several users, including desktop installs, evolution-calendar-factory (previsouly in 14.04) then evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of megabytes of memory (~ 300 Mio in my case). This might have to do with having lots of linked calendars (Google Agenda or other). Another user on my system has much fewer Google Agendas than me and her memory usage of evolution-calendar-factory-subprocess is less, but still close to 100 Mio. There have been random crashes of the process, mostly directly upon login, always caused by addressing memory out of range. There used to be a workaround by invoking the process a second time, which caused it to exit more or less gracefully. This is not the case anymore in 16.04. Unfortunately, searching Google leads to the bug #1342123 which concerns "Canonical System Image", and several users have replied even though it does not only concern mobile installs, which is not immediately self-evident when you are not aware what "Canonical System Image" stands for… To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+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 1342123] Re: evolution-calendar-factory always running with high memory usage
still getting this bug on 16.04 it has 3 process over 40mb each! -- 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/1342123 Title: evolution-calendar-factory always running with high memory usage Status in Canonical System Image: Confirmed Status in evolution-data-server package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: At boot the process is using over 100MB on my mako (build 129) I sync'd a fairly large set of calendar events from google previously Does this process need to be running all the time? Can we streamline it to not read so much of the data set, which it appears to be doing? With no calendar entries (i.e. removing .local/share/evolution/xxx/calendar.ics) the process still uses over 30MB (looking at RSS with ps aux --sort -rss ) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1342123/+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 1589605] Re: evolution-calendar-factory uses lots of memory
still happening, 3x process using 40mb+ ram each! -- 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/1589605 Title: evolution-calendar-factory uses lots of memory Status in evolution package in Ubuntu: Invalid Status in evolution-data-server package in Ubuntu: Expired Status in indicator-datetime package in Ubuntu: Expired Bug description: As filed under bug #1342123 (under Canonical System Image, i.e. for mobile installs) by several users, including desktop installs, evolution-calendar-factory (previsouly in 14.04) then evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of megabytes of memory (~ 300 Mio in my case). This might have to do with having lots of linked calendars (Google Agenda or other). Another user on my system has much fewer Google Agendas than me and her memory usage of evolution-calendar-factory-subprocess is less, but still close to 100 Mio. There have been random crashes of the process, mostly directly upon login, always caused by addressing memory out of range. There used to be a workaround by invoking the process a second time, which caused it to exit more or less gracefully. This is not the case anymore in 16.04. Unfortunately, searching Google leads to the bug #1342123 which concerns "Canonical System Image", and several users have replied even though it does not only concern mobile installs, which is not immediately self-evident when you are not aware what "Canonical System Image" stands for… To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+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
