After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 617038 - [backup-restore] evolution is not able to quit while taking backup
[backup-restore] evolution is not able to quit while taking backup
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: general
2.30.x (obsolete)
Other Linux
: High major
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 631115 631651 631843 634144 637421 638636 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-04-28 06:59 UTC by Akhil Laddha
Modified: 2011-04-07 15:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30

Attachments
Screen shot (19.15 KB, image/png)
2010-04-28 06:59 UTC, Akhil Laddha 		Details
Attaching backtrace (2.63 KB, application/octet-stream)
2010-09-29 15:42 UTC, Jon Cosby 		Details
Output from Evolution backup (1.65 KB, text/plain)
2010-10-03 17:48 UTC, Jon Cosby 		Details

Description Akhil Laddha 2010-04-28 06:59:51 UTC 
Created attachment 159756 [details]
Screen shot

evolution 2.31.1

1. File -> Backup settings
2. Option 'restart after backup' enable

Evolution keep showing 'shutting down evolution' but cann't do it.

lakhil@linux-r6qu:~> ps -ef | grep evo
lakhil    2608  2131  0 08:51 ?        00:00:00 evolution-alarm-notify
lakhil   20365  2763  6 12:18 pts/2    00:00:17 evolution-backup --gui --backup --restart /home/lakhil/Desktop/evolution-backup.tar.gz
lakhil   20460 20365  0 12:19 pts/2    00:00:00 evolution --quit
lakhil   20540 18382  0 12:23 pts/3    00:00:00 grep evo

could be due to bug 600861
Comment 1 Akhil Laddha 2010-04-28 07:02:56 UTC 
As evolution doesn't progress further, i do 'cancel' the backup operation but now evolution won't even start.

lakhil@linux-r6qu:~> ps -ef | grep evo
lakhil    2608  2131  0 08:51 ?        00:00:00 evolution-alarm-notify
lakhil   18679     1  0 11:57 pts/3    00:00:00 evolution --quit
lakhil   18765     1  0 12:03 pts/2    00:00:00 evolution --quit
lakhil   18773     1  0 12:04 pts/2    00:00:00 evolution --quit
lakhil   18789     1  0 12:05 pts/2    00:00:00 evolution --quit
lakhil   19555     1  0 12:09 pts/2    00:00:00 evolution --quit
lakhil   19864 18681  0 12:12 pts/4    00:00:00 grep evo


Program received signal SIGINT, Interrupt.
0xffffe430 in __kernel_vsyscall ()
(gdb) bt

+ Trace 221585

  • #0 __kernel_vsyscall
  • #1 connect
    at ../sysdeps/unix/sysv/linux/i386/socket.S line 61
  • #2 try_client
    at uniquebackend-bacon.c line 268
  • #3 unique_backend_bacon_request_name
    at uniquebackend-bacon.c line 462
  • #4 unique_backend_request_name
    at ./uniquebackend.c line 265
  • #5 unique_app_constructor
    at ./uniqueapp.c line 281
  • #6 IA__g_object_newv
    at gobject.c line 1261
  • #7 IA__g_object_new_valist
    at gobject.c line 1377
  • #8 IA__g_object_new
    at gobject.c line 1095
  • #9 create_default_shell
    at main.c line 388
  • #10 main
    at main.c line 526 






Comment 2


Tobias Mueller





          2010-04-29 14:03:30 UTC
        



Oh. That looks like the new backup kill thing has problems. mbarnes pushed something about evolutoin --quit and evolutoin --kill... CCing Matthew.






Comment 3


Matthew Barnes





          2010-04-29 17:39:32 UTC
        



Well, if the process is hung up on something during shutdown then we need to fix that.  Killing the process programmatically is just papering over the -real- issue, and can cause data loss or corruption.






Comment 4


Milan Crha





          2010-06-29 12:11:38 UTC
        



There were some fixes recently with "evolution --quit", in bug #603468.

I noticed that operations with evolution-mapi can be really slow, especially item creation or modification, which is done in the e-addressbook/calendar-factory, and evolution itself is just waiting for a DBus message, same as camel's folder update is done even when application is quitting, but these (apart of the camel's one) are things we cannot do much about, can we?






Comment 5


Jon Cosby





          2010-08-29 14:47:46 UTC
        



Is there any progress on this? Backing up manually is giving people problems, it would be nice to be able to do this automatically again.






Comment 6


Milan Crha





          2010-09-20 15:13:50 UTC
        



I just tried to backup my settings in 2.31.92 by File->Backup Evolution settings... and it works as expected, no pending 'evolution --quit' process left.

Could you retest, please?






Comment 7


Jon Cosby





          2010-09-26 03:53:40 UTC
        



I can't get this version of Evolution started past the beta warning. I'm trying to test it on an openSUSE 11.3 VM.






Comment 8


Milan Crha





          2010-09-27 08:58:30 UTC
        



(In reply to comment #7)
> I can't get this version of Evolution started past the beta warning. I'm trying
> to test it on an openSUSE 11.3 VM.

What does it do, or rather doesn't? Try to get a backtrace of running evolution.






Comment 9


Jon Cosby





          2010-09-29 15:42:39 UTC
        



Created attachment 171342 [details]
Attaching backtrace

I should mention that I'm having issues the panel as well.






Comment 10


Akhil Laddha





          2010-10-02 02:09:27 UTC
        



*** Bug 631115 has been marked as a duplicate of this bug. ***






Comment 11


Jon Cosby





          2010-10-03 17:47:01 UTC
        



Okay, the desktop is fully functional (factory). Backing up Evolution produces an empty tarball. Output attached.






Comment 12


Jon Cosby





          2010-10-03 17:48:20 UTC
        



Created attachment 171634 [details]
Output from Evolution backup






Comment 13


Milan Crha





          2010-10-04 08:26:47 UTC
        



OK, so it couldn't find /home/chief/.evolution (we moved away from an issue from comment #7, right?) What is the evolution version, please? Because I do not know what is shipped in "openSUSE 11.3 VM", somehow. Being it 2.32.0, then your issue might be addressed in bug #629972






Comment 14


Jon Cosby





          2010-10-04 12:09:57 UTC
        



I'm not sure what was causing the problems mentioned in #7 and #9, maybe conflicting versions. I upgraded all packages to Gnome factory, and this has fixed the conflicts. I'm now running Evolution 2.32.0. Should I try to revert to 2.31.92?






Comment 15


Milan Crha





          2010-10-05 06:49:09 UTC
        



Nono, do not revert, let's consider it fixed :) Especially if it was some library conflict.






Comment 16


Milan Crha





          2010-10-21 11:47:04 UTC
        



*** Bug 631843 has been marked as a duplicate of this bug. ***






Comment 17


Akhil Laddha





          2010-11-06 04:38:56 UTC
        



*** Bug 634144 has been marked as a duplicate of this bug. ***






Comment 18


Akhil Laddha





          2010-11-18 04:31:15 UTC
        



*** Bug 631651 has been marked as a duplicate of this bug. ***






Comment 19


Akhil Laddha





          2011-01-04 10:17:02 UTC
        



*** Bug 638636 has been marked as a duplicate of this bug. ***






Comment 20


Akhil Laddha





          2011-01-27 05:17:03 UTC
        



*** Bug 637421 has been marked as a duplicate of this bug. ***






Comment 21


Akhil Laddha





          2011-02-17 06:35:21 UTC
        



I don't see problem in Evolution 2.32.1, shall we close the bug ?






Comment 22


Milan Crha





          2011-02-17 07:55:43 UTC
        



If it works fine for you with git master then I would say yes, please close this.






Comment 23


Tobias Mueller





          2011-04-07 15:12:25 UTC
        



Assuming this to be OBSOLETE. Please reopen if this is not the case.