Bug 11298

One more clue from journalctl:

Sep 27 12:35:25 ... goa[2120]: goa-daemon version 3.10.0 starting [main.c:117, main()]
Sep 27 12:35:25 ... goa[2120]: Error preparing AM: Process /usr/libexec/mission-control-5 received signal 11 [goatpaccountlinker.c:510, account_manager_prepared_cb()]
Sep 27 12:35:25 ... kernel: mission-control[2130]: segfault at 10001 ip 00007fc588a109b1 sp 00007fff731aaf10 error 4 in libgobject-2.0.so.0.3800.0[7fc5889fb000+4f000]

CC: (none) => jamagallon

There is now new version of mission-control available. Is it segfaulting the same way?

Keywords: Triaged => NEEDINFO
CC: (none) => mageia

dmorgan you are still the maintainer. Please clean your packages maintainship 
(I asked you without effect already)

Keywords: (none) => Triaged
CC: (none) => dmorganec

$ mgarepo maintdb get telepathy-mission-control
nobody

He's not. Your maintainer info is probably outdated..

looks like the text file is not so well updated, I will wait more next time i see something like that, sorry

I doubt this is a mission-control problem directly, as it was updated to 5.14.1 in early May (before Mageia 3).  It has been since updated to 5.16.0.  However, telepathy-glib was updated to 0.21.2 the day you filed this bug, so it could have been the cause.  I just updated it again to 0.22.0, so hopefully this is fixed.  Let us know.  Thanks.

Thanks, I will check as soon as I get the updates...

Is anybody having issues with mission-control using 100% cpu? I'm adding a screenshot of tops 20 mins after booting the computer.

CC: (none) => philippe.l

Created attachment 4435 [details]
telepathy-mission-control high cpu usage

This is for MGA4 alpha 3 with telepathy-mission-control 5.16.0

Yep, me too. Sometines it generates a crash in dmesg, sometimes the
100% cpu hang, sometimes both...

After the latest updates, I get again a segfault for gdm session:

[12420.384575] mission-control[5245]: segfault at 23 ip 00007ffad4ad1837 sp 00007fff52db8240 error 4 in libglib-2.0.so.0.3800.0[7ffad4a6e000+fe000]

The user daemon seems to be running:

werewolf:~> ps -ef | grep miss
magallon  5415     1  0 01:17 ?        00:00:00 /usr/libexec/mission-control-5
magallon  5823  5799  0 01:20 pts/1    00:00:00 grep miss

but something weird is going on, because if I try to add an Online Accout
in Gnome Control Panel, it hangs:

Oct 16 01:22:38 werewolf.home gnome-session[5265]: (gnome-control-center:5875): GoaBackend-CRITICAL **: goa_provider_get_provider_features: assertion 'GOA_PROVIDER_GET_CLASS (provider)->get_provider_f...= NULL' failed
Oct 16 01:22:38 werewolf.home gnome-session[5265]: (gnome-control-center:5875): GoaBackend-CRITICAL **: goa_provider_get_provider_features: assertion 'GOA_PROVIDER_GET_CLASS (provider)->get_provider_f...= NULL' failed
Oct 16 01:22:38 werewolf.home gnome-session[5265]: (gnome-control-center:5875): GoaBackend-CRITICAL **: goa_provider_get_provider_features: assertion 'GOA_PROVIDER_GET_CLASS (provider)->get_provider_f...= NULL' failed
Oct 16 01:22:38 werewolf.home gnome-session[5265]: (gnome-control-center:5875): GoaBackend-CRITICAL **: goa_provider_get_provider_features: assertion 'GOA_PROVIDER_GET_CLASS (provider)->get_provider_f...= NULL' failed
Oct 16 01:22:38 werewolf.home gnome-session[5265]: (gnome-control-center:5875): GoaBackend-CRITICAL **: goa_provider_get_provider_features: assertion 'GOA_PROVIDER_GET_CLASS (provider)->get_provider_f...= NULL' failed
Oct 16 01:22:38 werewolf.home kernel: gnome-control-c[5875]: segfault at 0 ip           (null) sp 00007fff46f17d28 error 14 in gnome-control-center[400000+377000]

Thomas Backlund added some patches to telepathy-mission-control on January 5th.  Hopefully they fix this.

CC: (none) => tmb

Is this fixed?

Keywords: NEEDINFO, Triaged => (none)
CC: (none) => nic

Closing as FIXED since no one reported that it's broken since comment #12 has been made. Reopen if needed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED