[Evolution] All settings not being backed up

2018-07-04 Thread Douglas Summers
[Evolution 3.28.1, Mint-19-XFCE]

When I restored my previous backup (same Evolution version, different
OS; I used the Backup option from the File menu), it looks like none of
my folder archive settings made it. Where are these stored?
___
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] evolution client crashing at startup

2018-07-04 Thread John Edward Serink
Hi Milan:

Thank you for the prompt response.
Comments below:

On Wed, 2018-07-04 at 14:33 +0200, Milan Crha via evolution-list wrote:
> On Wed, 2018-07-04 at 16:18 +0800, John Serink wrote:
> > ...
> 
>   Hi,
> please, try to send in Plain Text here, not in HTML.
Yes, sorry about that. I had to use gmail inside a browser and it defaults to 
HTML.
Evolution (what I am using to write this) is setup for plain text but it was 
broken when I
wrote you.
> Using reply to list (Ctrl+L) is preferred, at least by me.
> Top-posting is also kind of bad on this list.
Again, a web-browser gmail thing, sorry about that.
> 
> Anyway, back to the issue:
> 
> > (evolution:1684): Gdk-WARNING **: 16:14:27.887: Native Windows wider
> > or taller than 32767 pixels are not supported
> 
> Let's start with the above. Could you run on console these commands,
> please:
> 
>   $ gsettings get 
> org.gnome.evolution.window:/org/gnome/evolution/shell/window/ width
>   $ gsettings get 
> org.gnome.evolution.window:/org/gnome/evolution/shell/window/ height
> 
> They will show what size the window has stored. You can reset it to its
> defaults with:
> 
> $ gsettings reset-recursively 
> org.gnome.evolution.window:/org/gnome/evolution/shell/window/
jserink@jserinki7 ~ $ gsettings get
org.gnome.evolution.window:/org/gnome/evolution/shell/window/ width
49129
jserink@jserinki7 ~ $ gsettings get
org.gnome.evolution.window:/org/gnome/evolution/shell/window/ height
884
jserink@jserinki7 ~ $ gsettings reset-recursively
org.gnome.evolution.window:/org/gnome/evolution/shell/window/
jserink@jserinki7 ~ $ gsettings get
org.gnome.evolution.window:/org/gnome/evolution/shell/window/ width
0

After resetting to defaults, evolution started no problem. THANKYOU for this.
Will file in my useful-tidbits to know folder.

> If it's it, then I've no idea how those values could get insane.
Pass, me neither. Especially considering it happened, at least the crash 
happened, when I
wasn't even at my desk and my computer was locked.

Never mind, its fixed now, thanx

Cheers,
john
> 
> > (evolution:1684): Gdk-ERROR **: 16:14:28.153: The program 'evolution'
> > received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'BadAlloc (insufficient resources for operation)'.
> >   (Details: serial 1856 error_code 11 request_code 53 (core protocol)
> > minor_code 0)
> >   (Note to programmers: normally, X errors are reported
> > asynchronously;
> >that is, you will receive the error a while after causing it.
> >To debug your program, run it with the GDK_SYNCHRONIZE environment
> >variable to change this behavior. You can then get a meaningful
> >backtrace from your debugger if you break on the gdk_x_error()
> > function.)
> 
> If it's not it, then, please, follow the instructions above. It might
> be hard to get to the function when the debug symbols are missing. This
> symbol is from gtk+. Once you have them, the commands might be:
> 
>$ export GDK_SYNCHRONIZE=1
>$ gdb evolution --ex "b gdk_x_error" --ex r --ex "bt" --ex "t a a bt" --ex 
> q
> 
> where you'll be asked to confirm that you want to make the breakpoint
> pending (there's some switch for it too, but I do not recall it). Thus
> just answer 'y', when you'll be asked for something by gdb.
> 
>   Thanks and 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
___
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] evolution client crashing at startup

2018-07-04 Thread Milan Crha via evolution-list
On Wed, 2018-07-04 at 16:18 +0800, John Serink wrote:
> ...

Hi,
please, try to send in Plain Text here, not in HTML.
Using reply to list (Ctrl+L) is preferred, at least by me.
Top-posting is also kind of bad on this list.

Anyway, back to the issue:

> (evolution:1684): Gdk-WARNING **: 16:14:27.887: Native Windows wider
> or taller than 32767 pixels are not supported

Let's start with the above. Could you run on console these commands,
please:

  $ gsettings get org.gnome.evolution.window:/org/gnome/evolution/shell/window/ 
width
  $ gsettings get org.gnome.evolution.window:/org/gnome/evolution/shell/window/ 
height

They will show what size the window has stored. You can reset it to its
defaults with:

$ gsettings reset-recursively 
org.gnome.evolution.window:/org/gnome/evolution/shell/window/

If it's it, then I've no idea how those values could get insane.

> (evolution:1684): Gdk-ERROR **: 16:14:28.153: The program 'evolution'
> received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadAlloc (insufficient resources for operation)'.
>   (Details: serial 1856 error_code 11 request_code 53 (core protocol)
> minor_code 0)
>   (Note to programmers: normally, X errors are reported
> asynchronously;
>that is, you will receive the error a while after causing it.
>To debug your program, run it with the GDK_SYNCHRONIZE environment
>variable to change this behavior. You can then get a meaningful
>backtrace from your debugger if you break on the gdk_x_error()
> function.)

If it's not it, then, please, follow the instructions above. It might
be hard to get to the function when the debug symbols are missing. This
symbol is from gtk+. Once you have them, the commands might be:

   $ export GDK_SYNCHRONIZE=1
   $ gdb evolution --ex "b gdk_x_error" --ex r --ex "bt" --ex "t a a bt" --ex q

where you'll be asked to confirm that you want to make the breakpoint
pending (there's some switch for it too, but I do not recall it). Thus
just answer 'y', when you'll be asked for something by gdb.

Thanks and 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] evolution client crashing at startup

2018-07-04 Thread John Serink
Sorry about that:
jserinki7 /home/jserink # equery list evolution
 * Searching for evolution ...
[I-O] [  ] mail-client/evolution-3.28.1:2.0


On Wed, Jul 4, 2018 at 4:18 PM, Patrick O'Callaghan  wrote:

> On Wed, 2018-07-04 at 12:08 +0800, John Serink wrote:
> > At yesterday at ~1750 hours after I had left the office evolution crashed
> > with this message in /var/log/everything/current:
> > Jul 03 17:53:21 [kernel] [35619.245683] traps: evolution[7152] trap int3
> > ip:7fb480d52741 sp:7fff17464fb0 error:0 in
> > libglib-2.0.so.0.5502.0[7fb480d01000+116000]
> >
> > This morning I tried to run the client and again, I got this:
> > Jul 04 08:07:37 [gnome-keyring-daemon] asked to register item
> > /org/freedesktop/secrets/collection/Default_5fkeyring/57785, but it's
> > already registered
> > Jul 04 08:07:37 [kernel] [86875.548505] traps: evolution[17690] trap int3
> > ip:7f1f5186c741 sp:7fff4e11d620 error:0 in
> > libglib-2.0.so.0.5502.0[7f1f5181b000+116000]
> >
> > These are the packages that were updated yesterday, maybe that has
> > something to do with it?
> [...]
>
> What I don't see anywhere is a mention of what version of Evolution
> you're using.
>
> 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
>



-- 
John Edward Serink
Product Applications Engineer,
Advanced Positioning
Trimble Navigation Singapore PTE Ltd.
80 Marine Parade Road,
Co. Reg. No. 199204958W
#22-06 Parkway Parade
Singapore 449269
Tel 65-6348-2212
Fax 65-6348-2232
DID 65-6348-2178
HP  65-9129-4250
Skype: johnserink
___
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] evolution client crashing at startup

2018-07-04 Thread Patrick O'Callaghan
On Wed, 2018-07-04 at 12:08 +0800, John Serink wrote:
> At yesterday at ~1750 hours after I had left the office evolution crashed
> with this message in /var/log/everything/current:
> Jul 03 17:53:21 [kernel] [35619.245683] traps: evolution[7152] trap int3
> ip:7fb480d52741 sp:7fff17464fb0 error:0 in
> libglib-2.0.so.0.5502.0[7fb480d01000+116000]
> 
> This morning I tried to run the client and again, I got this:
> Jul 04 08:07:37 [gnome-keyring-daemon] asked to register item
> /org/freedesktop/secrets/collection/Default_5fkeyring/57785, but it's
> already registered
> Jul 04 08:07:37 [kernel] [86875.548505] traps: evolution[17690] trap int3
> ip:7f1f5186c741 sp:7fff4e11d620 error:0 in
> libglib-2.0.so.0.5502.0[7f1f5181b000+116000]
> 
> These are the packages that were updated yesterday, maybe that has
> something to do with it?
[...]

What I don't see anywhere is a mention of what version of Evolution
you're using.

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] evolution client crashing at startup

2018-07-04 Thread John Serink
Hi Milan:

When running from the console, got this:
jserink@jserinki7 ~ $ evolution

(evolution:28496): Gdk-WARNING **: 16:09:13.347: Native Windows wider or
taller than 32767 pixels are not supported

(evolution:28496): Gdk-ERROR **: 16:09:13.663: The program 'evolution'
received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 2273 error_code 11 request_code 53 (core protocol)
minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap


Rebuilding with debug info now.

Cheers,
john

On Wed, Jul 4, 2018 at 3:18 PM, Milan Crha via evolution-list <
evolution-list@gnome.org> wrote:

> On Wed, 2018-07-04 at 12:08 +0800, John Serink wrote:
> > Looking for some tips on how to chase this down.
>
> Hi,
> could you make sure you build with debug symbols (or install debug info
> packages) and then get the backtrace of the crash, please? That would
> be like this:
>
>$ gdb evolution --ex r --ex "t a a bt" --ex q
>
> This should show where the crash happened and eventually also why,
> because there can also be a runtime warning on the console of
> evolution, which is not logged in the journal.
>
> Please check the gdb output for any private information, like
> passwords, email address, server addresses,... I usually search for
> "pass" at least (quotes for clarity only), before sharing it in public.
> 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
>



-- 
John Edward Serink
Product Applications Engineer,
Advanced Positioning
Trimble Navigation Singapore PTE Ltd.
80 Marine Parade Road,
Co. Reg. No. 199204958W
#22-06 Parkway Parade
Singapore 449269
Tel 65-6348-2212
Fax 65-6348-2232
DID 65-6348-2178
HP  65-9129-4250
Skype: johnserink
___
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] evolution client crashing at startup

2018-07-04 Thread Milan Crha via evolution-list
On Wed, 2018-07-04 at 12:08 +0800, John Serink wrote:
> Looking for some tips on how to chase this down.

Hi,
could you make sure you build with debug symbols (or install debug info
packages) and then get the backtrace of the crash, please? That would
be like this:

   $ gdb evolution --ex r --ex "t a a bt" --ex q

This should show where the crash happened and eventually also why,
because there can also be a runtime warning on the console of
evolution, which is not logged in the journal.

Please check the gdb output for any private information, like
passwords, email address, server addresses,... I usually search for
"pass" at least (quotes for clarity only), before sharing it in public.
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