Re: [Evolution] Restoring Evolution

2022-08-30 Thread Mr.J
That’s IT, I think. The external drive is formatted in FAT, and not exFAT. If 
both .tar.gz files were over 4gb, I (over) cooked my own goose. Talk about 
noobie errors. 

Thanks, Luigi. 
 
> On Aug 30, 2022, at 9:45 PM, Luigi Cantoni via evolution-list 
>  wrote:
> 
> 
> Someone else commented about file size limitations and this is far more of a 
> problem with MS type files systems.
> Check what type it is and if not one of the Linux/unix style ones change and 
> start again.
> You may find that works better.
> But remember non MS file system may/may not be readable by MS based systems.
> -- 
> Thanks
> Luigi 2
> 
> -Original Message-
> From: Mr. J 
> To: evolution-list@gnome.org
> Subject: Re: [Evolution] Restoring Evolution
> Date: Tue, 30 Aug 2022 21:33:49 -0700
> Mailer: Evolution 3.44.1-0ubuntu1
> 
> Update  
> 
> I started recovering the file with gzrt, et.
> al. https://www.aaronrenn.com/arenn/hacking/gzrt/gzrt.html and am
> getting closer.  So anyone who falls into such a hole may find some
> salvation.
> 
> However, and for the list: Recovering with gzrt and cpio gave me some
> error messages that certain (lots of) files/folders couldn't be
> created because they already existed.  That made me think the recover
> commands I had entered attempted to recreate the mail and data in my
> existing Evolution. So I did another Evolution backup (shame on me) of
> the existing Evolution data, to the same external hard drive, and then
> tried recover - thinking I would remove Evolution and reinstall it
> with no data.  I tested the backup .tar.gz to be careful, but I got
> the same error message that the file was invalid.  So I did a backup
> again, but this time to the internal hard drive.  Voila! Backup and
> Recover were successful.  So there's something about the process or
> the external hard drive (or both?) that prevents the creation of a
> valid .tar.gz backup file on my hard drive.  It was recently
> formatted, so I'm at a loss to explain.  
> 
> More to come.  (I hope the list will indulge me because I'm a noob on
> most of the Linux command structure.) 
> 
> IJ 
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Luigi Cantoni via evolution-list
Someone else commented about file size limitations and this is far more
of a problem with MS type files systems.
Check what type it is and if not one of the Linux/unix style ones
change and start again.
You may find that works better.
But remember non MS file system may/may not be readable by MS based
systems.
-- 
Thanks
Luigi 2

-Original Message-
From: Mr. J 
To: evolution-list@gnome.org
Subject: Re: [Evolution] Restoring Evolution
Date: Tue, 30 Aug 2022 21:33:49 -0700
Mailer: Evolution 3.44.1-0ubuntu1 

Update  

I started recovering the file with gzrt, et.
al. https://www.aaronrenn.com/arenn/hacking/gzrt/gzrt.html and am
getting closer.  So anyone who falls into such a hole may find some
salvation.

However, and for the list: Recovering with gzrt and cpio gave me some
error messages that certain (lots of) files/folders couldn't be
created because they already existed.  That made me think the recover
commands I had entered attempted to recreate the mail and data in my
existing Evolution. So I did another Evolution backup (shame on me) of
the existing Evolution data, to the same external hard drive, and then
tried recover - thinking I would remove Evolution and reinstall it
with no data.  I tested the backup .tar.gz to be careful, but I got
the same error message that the file was invalid.  So I did a backup
again, but this time to the internal hard drive.  Voila! Backup and
Recover were successful.  So there's something about the process or
the external hard drive (or both?) that prevents the creation of a
valid .tar.gz backup file on my hard drive.  It was recently
formatted, so I'm at a loss to explain.  

More to come.  (I hope the list will indulge me because I'm a noob on
most of the Linux command structure.) 

IJ 
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Mr. J
Update  

I started recovering the file with gzrt, et.
al. https://www.aaronrenn.com/arenn/hacking/gzrt/gzrt.html and am
getting closer.  So anyone who falls into such a hole may find some
salvation.

However, and for the list: Recovering with gzrt and cpio gave me some
error messages that certain (lots of) files/folders couldn't be
created because they already existed.  That made me think the recover
commands I had entered attempted to recreate the mail and data in my
existing Evolution. So I did another Evolution backup (shame on me) of
the existing Evolution data, to the same external hard drive, and then
tried recover - thinking I would remove Evolution and reinstall it
with no data.  I tested the backup .tar.gz to be careful, but I got
the same error message that the file was invalid.  So I did a backup
again, but this time to the internal hard drive.  Voila! Backup and
Recover were successful.  So there's something about the process or
the external hard drive (or both?) that prevents the creation of a
valid .tar.gz backup file on my hard drive.  It was recently
formatted, so I'm at a loss to explain.  

More to come.  (I hope the list will indulge me because I'm a noob on
most of the Linux command structure.) 

IJ 
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread c. marlow



On Tue, Aug 30, 2022, at 12:13 PM, Ralf Mardorf via evolution-list wrote:

> you are in favour of Evolution, just because it offers this option?
>
> Claws probably doesn't provide this feature for good reasons.


Yes it's quite nice that not only does it import my email from my POP3 days.. 
But, also the accounts, and settings are imported back into Evo and all I have 
to do is enter my password and I am back up and running! 

Chris
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Ralf Mardorf via evolution-list
On Tue, 2022-08-30 at 11:51 -0500, c. marlow wrote:
> > 
> I'd go back to Claws if the backup / restore feature was removed from
> Evo.

Hi,

you are in favour of Evolution, just because it offers this option?

Claws probably doesn't provide this feature for good reasons.

IMO this is the best solution for Evolution (Claws and any other MUA),
on Tue, 2022-08-30 at 17:43 +0100, Patrick O'Callaghan wrote:

> It's simple to get the same result as the current Backup function by
> just running a tar command on the command line. Perhaps that should be
> made explicit in the Help, with appropriate caveats, and the function
> removed from the UI to avoid misleading the user.

Regards,
Ralf

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Robert McDonald
On Tue, 2022-08-30 at 11:51 -0500, c. marlow wrote:
> > > On Tue, 2022-08-30 at 11:49 +0100, Pete Biggs wrote:
> 
> > > > I would possibly go as far as to say that that particular
> > > > functionality
> > > > has run its course and could be consigned to the big bit-bucket
> > > > in
> > > > the
> > > > sky.  
> 
> SEVERELY DISAGREE... I'd go back to Claws if the backup / restore
> feature was removed from Evo.
> 
> Even though I fully use IMAP now with Fastmail, I still use the
> Backup / Restore feature to restore the years of emails I have stored
> under " Saved on this computer" I think is what it says..  Also,  the
> backup and restore feature, restores not only my email but my account
> information too, to where when the restore is done, all I have to do
> is input my passwords and boom! I am back up and running in like 10
> sec.

I also appreciate this functionality.  I run the backup function
infrequently, and have used it to restore stuff to a new computer after
having backed up on the old one.  Seemed like it worked as I expected
based on the names of the menu items.  Found it handy to have something
that backs up what's needed while likely not including any recreatable
cache files.

-- 
Robert McDonald
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread c. marlow
>> On Tue, 2022-08-30 at 11:49 +0100, Pete Biggs wrote:

>>> I would possibly go as far as to say that that particular
>>> functionality
>>> has run its course and could be consigned to the big bit-bucket in
>>> the
>>> sky.  

SEVERELY DISAGREE... I'd go back to Claws if the backup / restore feature was 
removed from Evo.

Even though I fully use IMAP now with Fastmail, I still use the Backup / 
Restore feature to restore the years of emails I have stored under " Saved on 
this computer" I think is what it says..  Also,  the backup and restore 
feature, restores not only my email but my account information too, to where 
when the restore is done, all I have to do is input my passwords and boom! I am 
back up and running in like 10 sec.

Chris
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Matt Connell
On Tue, 2022-08-30 at 17:41 +0100, Patrick O'Callaghan wrote:
> On Tue, 2022-08-30 at 12:11 -0400, Matt Connell wrote:
> > On Tue, 2022-08-30 at 11:49 +0100, Pete Biggs wrote:
> > > Perhaps take it off the main 'File' menu and change it to
> > > something like "Save account settings" in the preferences and not
> > > backup the actual stored messages.
> > 
> > I support this, but not full removal.  I don't use it for
> > 'synchronizing' distinct machines, but I do tweak a lot of settings
> > based on need and I like to be able to undo what I may have broken.
> 
> So a backup that only copied settings would work for you?
> 

I believe so.  Settings would include all of the nits I've tracked down
over the years and set the way I like, such as "make sure you only send
emails to Work.com domain from Work.com SMTP account" and the like.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Patrick O'Callaghan
On Wed, 2022-08-31 at 00:22 +0800, Netsol.link wrote:
> > I would support this, though I'm sure some people might be upset
> > about
> > it. No-one expects their browser to have a built-in backup method,
> > so
> > why should their email system? I don't think other MUAs do this.
> > 
> > poc
> > ___
> You right some of us maybe a bit put-off if this function was to be
> removed. I use it sparingly (2 or 3 times a year) as a backup of
> emails
> and contacts. I also regularly trim my emails to keep the file size
> small and when I do a backup, I delete the oldest one so I only ever
> have 2 backup files.
> I have also used backup/restore to transfer from one computer to
> another usually without any issues. I once got into trouble but it
> was
> my one fault, because I stupidly backed-up from a newer version and
> tried restored to an older version! (different distros have different
> versions in their repos!?). I got out of that one because I also
> regularly 'image' my drive (using Rescuezilla). I don't use a backup
> utility as my data is mostly not critical and does not change that
> much
> (I'm retired)

I'm also retired, but I still run a nightly backup.

> As for other MUAs I don't know about Linux once, but, coming from
> Windows, MS Oultlook keeps everything in one file (.pst) so it's easy
> to just copy this file to a backup drive, no need for a
> backup/restore
> function. 
> Unfortunately none of that helps the OP with his corrupted backup - I
> have not enough knowledge to offer any advice - sorry.

It's simple to get the same result as the current Backup function by
just running a tar command on the command line. Perhaps that should be
made explicit in the Help, with appropriate caveats, and the function
removed from the UI to avoid misleading the user.

poc
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Patrick O'Callaghan
On Tue, 2022-08-30 at 12:11 -0400, Matt Connell wrote:
> On Tue, 2022-08-30 at 11:49 +0100, Pete Biggs wrote:
> > Perhaps take it off the main 'File' menu and change it to
> > something like "Save account settings" in the preferences and not
> > backup the actual stored messages.
> 
> I support this, but not full removal.  I don't use it for
> 'synchronizing' distinct machines, but I do tweak a lot of settings
> based on need and I like to be able to undo what I may have broken.

So a backup that only copied settings would work for you?

poc
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Netsol.link
On Tue, 2022-08-30 at 12:03 +0100, Patrick O'Callaghan wrote:
> On Tue, 2022-08-30 at 11:49 +0100, Pete Biggs wrote:
> > 
> > > 
> > > I've suggested in the past that we should change the terminology
> > > and
> > > call it something else, but so far no-one has come up with a good
> > > alternative name. Any suggestions would be welcome.
> > > 
> > I agree entirely with you. I think the "backup/restore" is
> > generally
> > abused rather than used - in that it used for things it was never
> > meant
> > to be used for.
> > 
> > Even the real use for it (i.e. transferring settings to another
> > machine) is mis-used for syncing things between multiple machines
> > by
> > some people. Yes, the argument of "it works so why not" is OK,
> > except
> > when it no longer works when doing that and people grouch that
> > something broke.
> > 
> > I would possibly go as far as to say that that particular
> > functionality
> > has run its course and could be consigned to the big bit-bucket in
> > the
> > sky.  Perhaps take it off the main 'File' menu and change it to
> > something like "Save account settings" in the preferences and not
> > backup the actual stored messages.
> 
> I would support this, though I'm sure some people might be upset
> about
> it. No-one expects their browser to have a built-in backup method, so
> why should their email system? I don't think other MUAs do this.
> 
> poc
> ___
You right some of us maybe a bit put-off if this function was to be
removed. I use it sparingly (2 or 3 times a year) as a backup of emails
and contacts. I also regularly trim my emails to keep the file size
small and when I do a backup, I delete the oldest one so I only ever
have 2 backup files.
I have also used backup/restore to transfer from one computer to
another usually without any issues. I once got into trouble but it was
my one fault, because I stupidly backed-up from a newer version and
tried restored to an older version! (different distros have different
versions in their repos!?). I got out of that one because I also
regularly 'image' my drive (using Rescuezilla). I don't use a backup
utility as my data is mostly not critical and does not change that much
(I'm retired)
As for other MUAs I don't know about Linux once, but, coming from
Windows, MS Oultlook keeps everything in one file (.pst) so it's easy
to just copy this file to a backup drive, no need for a backup/restore
function. 
Unfortunately none of that helps the OP with his corrupted backup - I
have not enough knowledge to offer any advice - sorry.

JP 
 
> 
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://mail.gnome.org/mailman/listinfo/evolution-list

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Ralf Mardorf via evolution-list
On Tue, 2022-08-30 at 10:29 -0400, Adam Tauno Williams wrote:
> Table-After-Creation is a good rule.

Hi,

when using tar by command line it's necessary to do it, not only to
check that the archive is not corrupt, but also to rule out user errors,
such as path typos or not having thought of globbing. Even if we could
trust the exit status of tar, we can't trust ourselves. You're having a
bad day and using the asterisk in the path inappropriately, that's it.
You get an intact archive, but with wrong content from a completely
wrong path, by a typo that does replace a "/" by a "*" or at least you
might be missing hidden directories or hidden files, if the path ends
with a "/*". One should always keep in mind that some people win the
lottery or are struck by lightning. IOW a typo or carelessness can
happen, too.

Regards,
Ralf
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Matt Connell
On Tue, 2022-08-30 at 11:49 +0100, Pete Biggs wrote:
> Perhaps take it off the main 'File' menu and change it to
> something like "Save account settings" in the preferences and not
> backup the actual stored messages.

I support this, but not full removal.  I don't use it for
'synchronizing' distinct machines, but I do tweak a lot of settings
based on need and I like to be able to undo what I may have broken.
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Mr.J

> On Aug 30, 2022, at 7:39 AM, Pete Biggs  wrote:
> 
> I know it's no solace to the OP
Well, that said a mouthful. I agree the “restore” function should be called 
“replace” or the like, and a simple warning (I.e. “Do not rely on 
backup/restore for routine preservation of your emails.”) would have helped. To 
compound matters, my regular backups didn’t include the evolution folder. 

Oh well. No comparison to the flooding in Bangladesh, etc.   



___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Ralf Mardorf via evolution-list
On Tue, 2022-08-30 at 11:49 +0100, Pete Biggs wrote:
> I would possibly go as far as to say that that particular functionality
> has run its course and could be consigned to the big bit-bucket in the
> sky.

Hi,

_yes_, announce that you will remove it and unless no user should veto,
remove it.

> Perhaps take it off the main 'File' menu and change it to
> something like "Save account settings" in the preferences and not
> backup the actual stored messages.

_No_, don't do things by halves. Away with it!

Regards,
Ralf
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] “cannot VACUUM from within a transaction”

2022-08-30 Thread Andre Klapper via evolution-list
On Tue, 2022-08-30 at 14:43 +, Joakim Tjernlund wrote:
> > never mind, I accidentally noticed there's one filled already:
> > https://gitlab.gnome.org/GNOME/evolution/-/issues/1786
> >
>
> I did the:
> gdb --pid=`pidof evolution` --ex "b camel_db_maybe_run_maintenance" -
> -ex c
> (gdb) t a a bt
> (gdb) c
>
> Got this just before the error:
[...]

Please report that in the existing ticket instead, and first make sure
that debug symbols for evolution, evolution-data-server, libsoup2,
gnutls are installed/compiled.

Thanks,
andre
--
Andre Klapper  |  ak...@gmx.net
https://blogs.gnome.org/aklapper/

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] “cannot VACUUM from within a transaction”

2022-08-30 Thread Joakim Tjernlund via evolution-list
On Tue, 2022-08-30 at 15:59 +0200, Milan Crha via evolution-list wrote:
> On Tue, 2022-08-30 at 15:19 +0200, Milan Crha via evolution-list wrote:
> > Maybe open a bug against the evolution-data-server [1] (these things
> > are done in the libcamel, which is there), to not have this lost in
> > the
> > mailing list. I can move it elsewhere, if it'll turn out to not be in
> > the evolution-data-server code base.
> 
>   Hi,
> never mind, I accidentally noticed there's one filled already:
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.gnome.org%2FGNOME%2Fevolution%2F-%2Fissues%2F1786data=05%7C01%7Cjoakim.tjernlund%40infinera.com%7Cccc2fd64991f4cfae7f208da8a8fe99a%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C637974647968005886%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=HBNTtGLe47T2%2FsA%2BnFH5ZUFjfvnmsKl8%2FPjCfOZ5kcU%3Dreserved=0
> 

I did the:
gdb --pid=`pidof evolution` --ex "b camel_db_maybe_run_maintenance" --ex c
(gdb) t a a bt
(gdb) c

Got this just before the error:
(gdb) t a a bt

Thread 71 (Thread 0x7ff016ffd640 (LWP 29434) "pool-evolution"):
#0  0x7ff0ca9b7e00 in camel_db_maybe_run_maintenance () at 
/usr/lib64/libcamel-1.2.so.63
#1  0x7ff0ca9d438f in camel_folder_expunge_sync () at 
/usr/lib64/libcamel-1.2.so.63
#2  0x7ff0bd4e0153 in e_mail_folder_expunge_sync () at 
/usr/lib64/evolution/libemail-engine.so
#3  0x7ff0bd4e0338 in  () at /usr/lib64/evolution/libemail-engine.so
#4  0x7ff0c9cc01e9 in run_in_thread (job=, c=0x5603848e5cd0 
[CamelOperation], _data=0x560386672ac0) at 
/var/tmp/portage/dev-libs/glib-2.72.3/glib-
2.72.3/gio/gsimpleasyncresult.c:899
#5  0x7ff0c9ca3076 in io_job_thread (task=, 
source_object=, task_data=0x560385a7bc00, cancellable=) at /var/tmp/portage/dev-
libs/glib-2.72.3/glib-2.72.3/gio/gioscheduler.c:85
#6  0x7ff0c9cd4ee4 in g_task_thread_pool_thread 
(thread_data=0x56038650a560, pool_data=) at 
/var/tmp/portage/dev-libs/glib-2.72.3/glib-2.72.3/gio/gtask.c:1452
#7  0x7ff0ca8b2c44 in g_thread_pool_thread_proxy (data=) at 
/var/tmp/portage/dev-libs/glib-2.72.3/glib-2.72.3/glib/gthreadpool.c:354
#8  0x7ff0ca8b234d in g_thread_proxy (data=0x56037e0f0060) at 
/var/tmp/portage/dev-libs/glib-2.72.3/glib-2.72.3/glib/gthread.c:827
#9  0x7ff0c979084a in start_thread (arg=) at 
pthread_create.c:442
#10 0x7ff0c981444c in clone3 () at 
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 18 (Thread 0x7ff0adfef640 (LWP 9297) "ReceiveQueue"):
#0  0x7ff0c980759f in __GI___poll (fds=0x7ff090007c50, nfds=0x2, 
timeout=0x) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff0ca887f9e in g_main_context_poll (priority=, 
n_fds=0x2, fds=0x7ff090007c50, timeout=, context=0x7ff0908e2d90) 
at /var/tmp/portage/dev-
libs/glib-2.72.3/glib-2.72.3/glib/gmain.c:4516
#2  g_main_context_iterate (context=0x7ff0908e2d90, block=block@entry=0x1, 
dispatch=dispatch@entry=0x1, self=) at 
/var/tmp/portage/dev-libs/glib-2.72.3/glib-
2.72.3/glib/gmain.c:4206
#3  0x7ff0ca8882f3 in g_main_loop_run (loop=0x7ff090aac470) at 
/var/tmp/portage/dev-libs/glib-2.72.3/glib-2.72.3/glib/gmain.c:4411
#4  0x7ff0c3f94de0 in WTF::RunLoop::run() () at 
/usr/lib64/libjavascriptcoregtk-4.0.so.18
#5  0x7ff0c3f3ac3a in  () at /usr/lib64/libjavascriptcoregtk-4.0.so.18
#6  0x7ff0c3f97959 in  () at /usr/lib64/libjavascriptcoregtk-4.0.so.18
#7  0x7ff0c979084a in start_thread (arg=) at 
pthread_create.c:442
#8  0x7ff0c981444c in clone3 () at 
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 17 (Thread 0x7ff0aeffd640 (LWP 24060) "evolution"):
#0  0x7ff0c980759f in __GI___poll (fds=fds@entry=0x7ff0aeffc050, 
nfds=nfds@entry=0x2, timeout=timeout@entry=0xea60) at 
../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff0ca897a17 in poll (__timeout=__timeout@entry=0xea60, __nfds=0x2, 
__fds=__fds@entry=0x7ff0aeffc050) at /usr/include/bits/poll2.h:39
#2  0x7ff0c9cc462e in g_socket_condition_timed_wait 
(socket=socket@entry=0x560385998fa0 [GSocket], 
condition=condition@entry=G_IO_IN, timeout_us=,
cancellable=cancellable@entry=0x560381518920 [GCancellable], 
error=error@entry=0x7ff01c32cb98) at 
/var/tmp/portage/dev-libs/glib-2.72.3/glib-2.72.3/gio/gsocket.c:4466
#3  0x7ff0c9cc484e in block_on_timeout (socket=socket@entry=0x560385998fa0 
[GSocket], condition=condition@entry=G_IO_IN, 
timeout_us=timeout_us@entry=0x,
start_time=start_time@entry=0x11ec1e111ae, 
cancellable=cancellable@entry=0x560381518920 [GCancellable], 
error=error@entry=0x7ff01c32cb98) at /var/tmp/portage/dev-libs/glib-
2.72.3/glib-2.72.3/gio/gsocket.c:3201
#4  0x7ff0c9cc55bf in g_socket_receive_with_timeout (socket=0x560385998fa0 
[GSocket], buffer=0x7ff0405dd233 " \r\n", size=0x5, 
timeout_us=0x,
cancellable=0x560381518920 [GCancellable], error=0x7ff01c32cb98) at 
/var/tmp/portage/dev-libs/glib-2.72.3/glib-2.72.3/gio/gsocket.c:3249
#5  

Re: [Evolution] Restoring Evolution

2022-08-30 Thread Pete Biggs
On Tue, 2022-08-30 at 10:29 -0400, Adam Tauno Williams wrote:
> > My guess is, that Evolution isn't the culprit, but tar is the
> > culprit.
> 
> The only reliable mechanism to verify a tar archive is valid is to
> table it.  :(
> 
> Table-After-Creation is a good rule.
> 
I know it's no solace to the OP, but my experience is that people don't
care about backups and their integrity until they need one and it
doesn't work.  No matter how many times you tell people to check the
backups, they never do - until that fateful day and they realise "I
should have listened".

P.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Adam Tauno Williams
> My guess is, that Evolution isn't the culprit, but tar is the
> culprit.

The only reliable mechanism to verify a tar archive is valid is to
table it.  :(

Table-After-Creation is a good rule.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] “cannot VACUUM from within a transaction”

2022-08-30 Thread Joakim Tjernlund via evolution-list
On Tue, 2022-08-30 at 15:19 +0200, Milan Crha via evolution-list wrote:
> On Tue, 2022-08-30 at 12:47 +0200, Joakim Tjernlund via evolution-list
> wrote:
> > Failed to expunge folder “Infinera : Deleted Items”.
> > The reported error was “cannot VACUUM from within a transaction”.
> > 
> > Seems like the operation is successful though, Deleted Items is empty
> 
>   Hi,
> the vacuum is ran on the database level, to make the corresponding
> folders.db file smaller.
> 
> I tried it here, but it did not trigger the condition, maybe my
> folders.db file doesn't need the vacuum call. Just in case, do you know
> the version of the sqlite in your system please? I do not think they
> changed anything relevant, I only want to make sure I'll use a similar
> version as you.

dev-db/sqlite-3.39.2 but I have seen this on and off for quite a while.
I usually have hundreds of mail in Deleted Items(even 1000-2000 sometimes),
maybe it depends on number of emails to purge?

> 
> Maybe open a bug against the evolution-data-server [1] (these things
> are done in the libcamel, which is there), to not have this lost in the
> mailing list. I can move it elsewhere, if it'll turn out to not be in
> the evolution-data-server code base.
> 
>   Thanks and bye,
>   Milan
> 
> [1] 
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.gnome.org%2FGNOME%2Fevolution-data-server%2F-%2Fissuesdata=05%7C01%7Cjoakim.tjernlund%40infinera.com%7C33bbf5471427459f116108da8a8a659c%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C637974624280261209%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=PBQnwTKSWZzh7gG3TcupiqDWqlHcRe3eoVqFsIzxDPc%3Dreserved=0
> 
> ___
> evolution-list mailing list
> evolution-list@gnome.org
> To change your list options or unsubscribe, visit ...
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.gnome.org%2Fmailman%2Flistinfo%2Fevolution-listdata=05%7C01%7Cjoakim.tjernlund%40infinera.com%7C33bbf5471427459f116108da8a8a659c%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C637974624280417430%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=TJJBBc00Md5zxb%2FisIhlldHsTj7ems1DfUCLkc1Pdx8%3Dreserved=0

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Adam Tauno Williams
> Thanks, Luigi. The USB hard drive was not disconnected at all.
> Evolution did the backup and finished. Could the size of the file
> caused the problem? 

Potentially, there are a lot of variables.  Depending on the filesystem
of the USB drive the file could be limited to ~2GB or ~4GB.

It is always good to verify a backup file is valid [yes, optimally a
tool will tell you about all possible failures - in reality this very
rarely happens, even with tools designed for that purpose].

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] “cannot VACUUM from within a transaction”

2022-08-30 Thread Milan Crha via evolution-list
On Tue, 2022-08-30 at 15:19 +0200, Milan Crha via evolution-list wrote:
> Maybe open a bug against the evolution-data-server [1] (these things
> are done in the libcamel, which is there), to not have this lost in
> the
> mailing list. I can move it elsewhere, if it'll turn out to not be in
> the evolution-data-server code base.

Hi,
never mind, I accidentally noticed there's one filled already:
https://gitlab.gnome.org/GNOME/evolution/-/issues/1786

Bye,
Milan

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] “cannot VACUUM from within a transaction”

2022-08-30 Thread Milan Crha via evolution-list
On Tue, 2022-08-30 at 12:47 +0200, Joakim Tjernlund via evolution-list
wrote:
> Failed to expunge folder “Infinera : Deleted Items”.
> The reported error was “cannot VACUUM from within a transaction”.
> 
> Seems like the operation is successful though, Deleted Items is empty

Hi,
the vacuum is ran on the database level, to make the corresponding
folders.db file smaller.

I tried it here, but it did not trigger the condition, maybe my
folders.db file doesn't need the vacuum call. Just in case, do you know
the version of the sqlite in your system please? I do not think they
changed anything relevant, I only want to make sure I'll use a similar
version as you.

Maybe open a bug against the evolution-data-server [1] (these things
are done in the libcamel, which is there), to not have this lost in the
mailing list. I can move it elsewhere, if it'll turn out to not be in
the evolution-data-server code base.

Thanks and bye,
Milan

[1] https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Patrick O'Callaghan
On Tue, 2022-08-30 at 11:49 +0100, Pete Biggs wrote:
> 
> > 
> > I've suggested in the past that we should change the terminology
> > and
> > call it something else, but so far no-one has come up with a good
> > alternative name. Any suggestions would be welcome.
> > 
> I agree entirely with you. I think the "backup/restore" is generally
> abused rather than used - in that it used for things it was never
> meant
> to be used for.
> 
> Even the real use for it (i.e. transferring settings to another
> machine) is mis-used for syncing things between multiple machines by
> some people. Yes, the argument of "it works so why not" is OK, except
> when it no longer works when doing that and people grouch that
> something broke.
> 
> I would possibly go as far as to say that that particular
> functionality
> has run its course and could be consigned to the big bit-bucket in
> the
> sky.  Perhaps take it off the main 'File' menu and change it to
> something like "Save account settings" in the preferences and not
> backup the actual stored messages.

I would support this, though I'm sure some people might be upset about
it. No-one expects their browser to have a built-in backup method, so
why should their email system? I don't think other MUAs do this.

poc
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Pete Biggs


> 
> I've suggested in the past that we should change the terminology and
> call it something else, but so far no-one has come up with a good
> alternative name. Any suggestions would be welcome.
> 
I agree entirely with you. I think the "backup/restore" is generally
abused rather than used - in that it used for things it was never meant
to be used for.

Even the real use for it (i.e. transferring settings to another
machine) is mis-used for syncing things between multiple machines by
some people. Yes, the argument of "it works so why not" is OK, except
when it no longer works when doing that and people grouch that
something broke.

I would possibly go as far as to say that that particular functionality
has run its course and could be consigned to the big bit-bucket in the
sky.  Perhaps take it off the main 'File' menu and change it to
something like "Save account settings" in the preferences and not
backup the actual stored messages.

P.

___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


[Evolution] “cannot VACUUM from within a transaction”

2022-08-30 Thread Joakim Tjernlund via evolution-list
I often get this error when I empty Deleted Items:

Failed to expunge folder “Infinera : Deleted Items”.
The reported error was “cannot VACUUM from within a transaction”.

Seems like the operation is successful though, Deleted Items is empty

On Evo 3.44.4 using an O365 company account

 Jocke
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Patrick O'Callaghan
On Mon, 2022-08-29 at 16:41 -0700, Mr. J wrote:
> Friends: I have been trying to restore yesterday's Evolution backup
> and get the message: 
> 
> File “/home/ij/Downloads/evolution-backup-20220828.tar.gz” is not a
> valid Evolution backup file.  
> 
> I created the backup file yesterday with Evolution's backup function,
> and I'm running the restore command from Evolution, but it's a
> restored version from a 2020.tar.gz file.  (I mistakenly thought
> restoring the data from that 2020 file would simply add to the
> existing Evolution system; instead I replaced all my current data
> with
> that from the 2020 file.)
> 
> I'm running Evolution 3.44.1-Oubuntu1 in Ubuntu 22.04.1 LTS, on a
> generic Intel Pentium CPU G4400.    When I created yesterday's
> backup,
> I put it in (backed it up to) an external USB hard drive. Thinking
> that might be the problem, I copied and pasted it to the local
> /home/ij  folder.

Once again I feel I have to bring up the (understandable)
misunderstanding about the Backup/Restore function in Evolution.

I'm afraid this isn't going to help with your current problem, which
others have commented on, but it's important to clarify that the
purpose of Backup/Restore is *not* for doing your daily backups. It can
be used in that way, but I think it's generally a bad idea. As you've
noticed, Backup copies *all* your data, and Restore overwrites *all* of
it. This is not how regular backups should be handled. Aside from being
very inefficient, it's also very dangerous, as you've discovered.

The best way to backup Evolution is as part of your regular home
directory backup procedure. You can do this any way you want, but any
reasonable backup solution will handle incremental backups, work
automatically, keep multiple generations of backups, allow selective
restoring, etc. Evo's built-in facility does none of that. It's just a
compressed tar file, with all that that implies.

I've suggested in the past that we should change the terminology and
call it something else, but so far no-one has come up with a good
alternative name. Any suggestions would be welcome.

To be clear, this is just my own opinion.

poc
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list


Re: [Evolution] Restoring Evolution

2022-08-30 Thread Ralf Mardorf via evolution-list
On Mon, 2022-08-29 at 18:33 -0700, Mr.J wrote:
> Could the size of the file caused the problem?

Hi,

yesno. It depends on the file system and the size of the archive, so
indeed, yes, the file can become too large to fit. When generating the
archive and the size or any other issue should be the cause for an
error, then tar should return an exit status greater than zero. IOW tar
should inform you about the error already when creating the archive
fails.

My guess is, that Evolution isn't the culprit, but tar is the culprit.

I'm doing regular backups by command line using tar and very seldom, but
OTOH that often that it stands out, the archives are corrupted. I'm
doing my backups by rotation on many different external drives, that are
for sure 100% ok. The backups are done by a script writing the exit
status of each tar command to a log file. All corrupted archives were
created with an exit status 0, IOW without an error. Btw. usually my
scripts are generate tar.gz archives, too.

When the archives are created and saved, my backups are not done. I
don't trust the exit status of tar. Right after the archives are saved I
open all archives for testing purpose. If an archive is corrupted, I
repeat the backup.

FWIW USB to SATA can be a pain, too. However, if something is fishy with
this, then you get informed about IO errors, a read-only drive or
similar. Such mistakes do not go unnoticed, the exit status of tar is
always greater than zero.

Regards,
Ralf
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list