[Desktop-packages] [Bug 1589605] Re: evolution-calendar-factory uses lots of memory

2018-09-01 Thread Iván Pérez
I can confirm that this problem exists in 18.04 and that disabling the
linked Google account in Account Settings worked for me.

The chmod-based solution posted by titan-phpdevshell (#13) also worked,
but I expect that to stop working as soon as I upgrade.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evolution-data-server in Ubuntu.
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1738528] [NEW] Sound applet reflects volume of different device when bluetooth device auto-connects

2017-12-16 Thread Iván Pérez
Public bug reported:

As currently set up in Ubuntu 16.04, when an audio device connects via
bluetooth, it starts being used by programs automatically. However, the
sound applet still "points to" the previously selected audio output.
Therefore, changing the volume has no immediate audible effect.

The way to change that, currently, is to go to Sound settings, select
the bluetooth device as current output (again?), and then the volume
will change.

I would expect that, when a bluetooth device is connected, it starts
being used, *and* changing the volume immediately will affect the
bluetooth device.

I googled a bit, and people have suggested [1] that the file
/etc/pulse/default.pa should contain load-module module-switch-on-
connect before the volume is restored. My installation does not have
that line, but it does have:

### Should be after module-*-restore but before module-*-detect
load-module module-switch-on-port-available

According to [1], maybe this should be listed in that file *before* the
aforementioned module-*-restore lines.

[1] https://askubuntu.com/questions/233277/when-a-bluetooth-audio-
device-auto-connects-volume-settings-wont-work-until-i-m

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  As currently setup in Ubuntu 16.04, when an audio device connects via
  bluetooth, it starts being used by programs automatically. However, the
  sound applet still "points to" the previously selected audio output.
  Therefore, changing the volume has no immediate audible effect.
  
  The way to change that, currently, is to go to Sound settings, select
  the bluetooth device as current output (again?), and then the volume
  will change.
  
  I would expect that, when a bluetooth device is connected, it starts
  being used *and* changing the volume immediately will affect the
  bluetooth device.
  
  I googled a bit, and people have suggested [1] that the file
  /etc/pulse/default.pa should contain load-module module-switch-on-
  connect before the volume is restored. My installation does not have
  that line, but it does have:
  
  ### Should be after module-*-restore but before module-*-detect
  load-module module-switch-on-port-available
  
+ According to [1], this should be listed in that file *before* the
+ aforementioned module-*-restore lines.
+ 
  [1] https://askubuntu.com/questions/233277/when-a-bluetooth-audio-
  device-auto-connects-volume-settings-wont-work-until-i-m

** Package changed: openal-soft (Ubuntu) => pulseaudio (Ubuntu)

** Description changed:

- As currently setup in Ubuntu 16.04, when an audio device connects via
+ As currently set up in Ubuntu 16.04, when an audio device connects via
  bluetooth, it starts being used by programs automatically. However, the
  sound applet still "points to" the previously selected audio output.
  Therefore, changing the volume has no immediate audible effect.
  
  The way to change that, currently, is to go to Sound settings, select
  the bluetooth device as current output (again?), and then the volume
  will change.
  
  I would expect that, when a bluetooth device is connected, it starts
  being used *and* changing the volume immediately will affect the
  bluetooth device.
  
  I googled a bit, and people have suggested [1] that the file
  /etc/pulse/default.pa should contain load-module module-switch-on-
  connect before the volume is restored. My installation does not have
  that line, but it does have:
  
  ### Should be after module-*-restore but before module-*-detect
  load-module module-switch-on-port-available
  
  According to [1], this should be listed in that file *before* the
  aforementioned module-*-restore lines.
  
  [1] https://askubuntu.com/questions/233277/when-a-bluetooth-audio-
  device-auto-connects-volume-settings-wont-work-until-i-m

** Description changed:

  As currently set up in Ubuntu 16.04, when an audio device connects via
  bluetooth, it starts being used by programs automatically. However, the
  sound applet still "points to" the previously selected audio output.
  Therefore, changing the volume has no immediate audible effect.
  
  The way to change that, currently, is to go to Sound settings, select
  the bluetooth device as current output (again?), and then the volume
  will change.
  
  I would expect that, when a bluetooth device is connected, it starts
- being used *and* changing the volume immediately will affect the
+ being used, *and* changing the volume immediately will affect the
  bluetooth device.
  
  I googled a bit, and people have suggested [1] that the file
  /etc/pulse/default.pa should contain load-module module-switch-on-
  connect before the volume is restored. My installation does not have
  that line, but it does have:
  
  ### Should be after module-*-restore but before module-*-detect
  load-module module-switch-on-port-available
  
  According to [1], this should be listed in that file *before* the
  aforementioned module-*-r

[Desktop-packages] [Bug 1201659] Re: gnome-panel crashed with SIGSEGV in gweather_location_equal()

2014-03-04 Thread Iván Pérez
This bug affects me. I've reduced it to:
1) Go to panel, 1.1) expand locations, 1.2) click on edit.
2) Close.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1201659

Title:
  gnome-panel crashed with SIGSEGV in gweather_location_equal()

Status in “gnome-panel” package in Ubuntu:
  Confirmed

Bug description:
  Not sure what the context of this crash was, unfortunately.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: gnome-panel 1:3.6.2-0ubuntu11
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Mon Jul 15 21:43:59 2013
  ExecutablePath: /usr/bin/gnome-panel
  GsettingsChanges:
   
  InstallationDate: Installed on 2012-08-21 (328 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120821)
  MarkForUpload: True
  ProcCmdline: gnome-panel
  SegvAnalysis:
   Segfault happened at: 0x7fca3278cc45 :   mov
0x20(%rdi),%eax
   PC (0x7fca3278cc45) ok
   source "0x20(%rdi)" (0x0020) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-panel
  StacktraceTop:
   gweather_location_equal () from /usr/lib/libgweather-3.so.3
   gweather_location_entry_set_location () from /usr/lib/libgweather-3.so.3
   ?? () from /usr/lib/gnome-panel/4.0/libclock-applet.so
   ?? () from /usr/lib/gnome-panel/4.0/libclock-applet.so
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-panel crashed with SIGSEGV in gweather_location_equal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1201659/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp