Ubuntu
evolution-indicator package

Disabling and Enabling "Evolution Indicator" plugin closes evolution

Bug #566877 reported by Aleksander Morgado
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evolution
Unknown
Medium
evolution-indicator (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: evolution

Way to reproduce:
 * In the menu, open the Plugin Manager: Plugin Edit->Plugins
 * Disable the "Evolution Indicator" plugin
 * Enable again the "Evolution Indicator" plugin

Evolution is closed.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: evolution 2.28.3-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Mon Apr 19 21:31:14 2010
ExecutablePath: /usr/bin/evolution
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100308)
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SourcePackage: evolution

Revision history for this message
Aleksander Morgado (aleksander-m) wrote :
bbordwell (benbordwell)
summary: - Disabling and Enabling a plugin closes evolution
+ Disabling and Enabling "Evolution Indicator" plugin closes evolution
Changed in evolution (Ubuntu):
status: New → Confirmed
Revision history for this message
bbordwell (benbordwell) wrote :

Edited the name since this only affects the evolution indicator plugin which i believe is Ubuntu specific so I will not file this upstream unless someone says to do so.

(gdb) c
Continuing.
[New Thread 0x7f82ff41f710 (LWP 11678)]
[New Thread 0x7f83011c3710 (LWP 11679)]
[Thread 0x7f83011c3710 (LWP 11679) exited]

Program received signal SIGABRT, Aborted.
0x00007f831b629a75 in *__GI_raise (sig=<value optimized out>)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
 in ../nptl/sysdeps/unix/sysv/linux/raise.c
(gdb) c
Continuing.
[Thread 0x7f82ff41f710 (LWP 11678) exited]
[Thread 0x7f830c6ac710 (LWP 11466) exited]
[Thread 0x7f830beab710 (LWP 11467) exited]
[Thread 0x7f830928e710 (LWP 11473) exited]
[Thread 0x7f83023c8710 (LWP 11474) exited]

Program terminated with signal SIGABRT, Aborted.
The program no longer exists

That is the output in GDB if a full backtrace would be helpful I can upload one, just let me know.

Revision history for this message
bbordwell (benbordwell) wrote :

This may be a duplicate of 543394 but I am not sure so I am not going to mark it as such.

Revision history for this message
Aleksander Morgado (aleksander-m) wrote :

Actually, this is not only Indicator-plugin specific. I have noticed the same using Tracker 0.8 plugin for evolution.

The Tracker developers state (not exactly quoting) that when the plugin is disabled, the DBus connections are not properly unregistered from the DBus session, and when the plugin is enabled again, it cannot properly re-register the DBus connections (as already there) and thus, exit() gets called.

It makes sense, as Evolution also probably uses DBus to communicate with the indicator-applet.

So it's probably a bug specific to ePlugins which register DBus connections.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. The issue is an upstream one and it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Changed in evolution (Ubuntu):
importance: Undecided → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for sending the bug to GNOME

Changed in evolution (Ubuntu):
status: Confirmed → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in evolution:
status: Unknown → Incomplete
Revision history for this message
bbordwell (benbordwell) wrote :

changing to evolution-indicator as suggested by upstream.

affects: evolution (Ubuntu) → evolution-indicator (Ubuntu)
Revision history for this message
bbordwell (benbordwell) wrote :
Bug Watch Updater (bug-watch-updater)
Changed in evolution:
status: Incomplete → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in evolution:
importance: Unknown → Medium
status: Invalid → Unknown
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.