Re: [Evolution] Crashing Evolution 3.46.0 ?

2022-10-10 Thread Paul Smith
On Mon, 2022-10-10 at 09:46 +0200, Milan Crha via evolution-list wrote:
> Do you have enabled sender's photos, or RSS, or remote content
> loading, or... I do not know off head what all can call libsoup in
> the evolution process while viewing messages, I'm sorry.

Remote content loading is set to "never" but I do sometimes use C-i to
force it on some messages.  However, definitely the crash does not
happen directly when I do that.  It might happen when viewing messages
which contain images that I have cached by running C-i previously
however...?  I get email from various dev service tools like CI/CD and
code review tools, that contain small images that I've previously
downloaded.

Just to note I haven't been able to find a reproducible case here; for
example when Evolution crashes and I restart it and look at the message
that had just been selected when I got a crash, it works fine.

It seems like it must be some kind of timing issue, or something.

I will try to be more aware of what I'm doing when the crash happens,
to see if it's more likely when viewing certain classes of email.

FWIW I don't use RSS and haven't enabled sender's photos.
___
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] Crashing Evolution 3.46.0 ?

2022-10-10 Thread Milan Crha via evolution-list
On Mon, 2022-10-10 at 09:46 +0200, Milan Crha via evolution-list wrote:
> I would file this as an issue into their bug tracker:

Hi,
I opened a bug there for you:
https://gitlab.gnome.org/GNOME/libsoup/-/issues/308

If you could, please, CC yourself there, in case they'd have additional
questions.
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] Crashing Evolution 3.46.0 ?

2022-10-10 Thread Milan Crha via evolution-list
On Fri, 2022-10-07 at 15:41 -0400, Paul Smith wrote:
> Is the 0x some kind of overwritten memory due to
> being freed, or something?

Hi,
yes, it can be, but I'm not sure (I've no idea whether there are any
functions enabled in Flatpak to overwrite pointer addresses after
free).

> (gdb) bt full
> #0  0x7f8002abc8fb in g_mutex_lock
> (mutex=mutex@entry=0xaab2) at ../glib/gthread-
> posix.c:1529
>     gaicae_oldval = 0
> #1  0x7f7ffc8977d1 in soup_connection_manager_cleanup
> (manager=0x, cleanup_idle=cleanup_idle@entry=0) at
> ../libsoup/soup-connection-manager.c:516
>     conns = 
> #2  0x7f7ffc8a8b45 in async_run_queue
> (session=session@entry=0x55e754ed96c0) at ../libsoup/soup-
> session.c:1821
>     priv = 0x55e754ed9620
>     items = 0x0
>     i = 
> #3  0x7f7ffc8a8c35 in queue_dispatch (source=,
> callback=, user_data=) at
> ../libsoup/soup-session.c:184
>     session = 0x55e754ed96c0

The backtrace shows a problem in libsoup3, possibly calling
(asynchronously) soup_connection_manager_cleanup() on an object, which
had been already freed. It looks like that from the backtrace at least,
I do not know libsoup internals that well.

I would file this as an issue into their bug tracker:
https://gitlab.gnome.org/GNOME/libsoup/-/issues

Evolution itself doesn't do many libsoup calls on its own, only a few.
Do you have enabled sender's photos, or RSS, or remote content loading,
or... I do not know off head what all can call libsoup in the evolution
process while viewing messages, I'm sorry.

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] Crashing Evolution 3.46.0 ?

2022-10-07 Thread Paul Smith
On Fri, 2022-10-07 at 15:27 -0400, Paul Smith wrote:
> I just installed org.gnome.Sdk.Debug flatpak, maybe that has the
> right stuff in it?

I suspect that was it because when I attached to Evolution via GDB this
time, it took about 3 minutes to load all the stuff and get me to a
(gdb) prompt :).

I can see that the gdb process is about 4.5G resident ... yikes!

OK here's the full backtrace with more info, from the previous core.

Is the 0x some kind of overwritten memory due to being
freed, or something?

--
(gdb) bt full
#0  0x7f8002abc8fb in g_mutex_lock (mutex=mutex@entry=0xaab2) 
at ../glib/gthread-posix.c:1529
gaicae_oldval = 0
#1  0x7f7ffc8977d1 in soup_connection_manager_cleanup 
(manager=0x, cleanup_idle=cleanup_idle@entry=0) at 
../libsoup/soup-connection-manager.c:516
conns = 
#2  0x7f7ffc8a8b45 in async_run_queue 
(session=session@entry=0x55e754ed96c0) at ../libsoup/soup-session.c:1821
priv = 0x55e754ed9620
items = 0x0
i = 
#3  0x7f7ffc8a8c35 in queue_dispatch (source=, 
callback=, user_data=) at 
../libsoup/soup-session.c:184
session = 0x55e754ed96c0
#4  0x7f8002a655d1 in g_main_dispatch (context=) at 
../glib/gmain.c:3444
dispatch = 0x7f7ffc8a8c10 
prev_source = 0x0
begin_time_nsec = 92966318517724
was_in_call = 0
user_data = 0x0
callback = 0x0
cb_funcs = 0x0
cb_data = 0x0
need_destroy = 
source = 0x7f7f245bd760
current = 0x55e750584020
i = 0
__func__ = "g_main_dispatch"
#5  g_main_context_dispatch (context=) at ../glib/gmain.c:4162
#6  0x7f8002a65b28 in g_main_context_iterate (context=0x55e75051c4e0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../glib/gmain.c:4238
max_priority = 2147483647
timeout = 82
some_ready = 1
nfds = 3
allocated_nfds = 
fds = 
begin_time_nsec = 92966311173981
#7  0x7f8002a65e0f in g_main_loop_run (loop=loop@entry=0x55e750c5b170) at 
../glib/gmain.c:4438
__func__ = "g_main_loop_run"
#8  0x7f8002442145 in gtk_main () at ../gtk/gtkmain.c:1329
loop = 0x55e750c5b170
#9  0x55e74efad86e in main (argc=, argv=) at 
/run/build/evolution/src/shell/main.c:784
shell = 0x55e75057c1f0 [EShell]
settings = 
success = 
error = 0x0

___
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] Crashing Evolution 3.46.0 ?

2022-10-07 Thread Paul Smith
On Thu, 2022-10-06 at 10:17 -0400, Paul Smith wrote:
> On Thu, 2022-10-06 at 08:26 +0200, Milan Crha via evolution-list
> wrote:
> > Some info on the debugging of the Flatpak apps is here:
> > https://docs.flatpak.org/en/latest/debugging.html
> 
> Hopefully the next time I get a crash I'll have some useful
> details...

I got a crash but not many details.  I added org.gnome.Evolution.Debug
flatpak but the crash happens in glib and I can't seem to figure out
how to add debug libraries for this, on my system.  Ideas?  I tried
adding org.gnome.Platform.Debug but got no such flatpak.  I just
installed org.gnome.Sdk.Debug flatpak, maybe that has the right stuff
in it?  Anyway I'll let you know when I get the core again.

Anyway here's what the core says:
--
(evolution.bin:37): GLib-GObject-CRITICAL **: 14:40:45.658: g_object_ref: 
assertion '!object_already_finalized' failed

Thread 1 "evolution.bin" received signal SIGSEGV, Segmentation fault.
0x7f8002abc8fb in g_mutex_lock () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

(gdb) bt full
#0  0x7f8002abc8fb in g_mutex_lock () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f7ffc8977d1 in soup_connection_manager_cleanup () at 
/usr/lib/x86_64-linux-gnu/libsoup-3.0.so.0
#2  0x7f7ffc8a8b45 in async_run_queue () at 
/usr/lib/x86_64-linux-gnu/libsoup-3.0.so.0
#3  0x7f7ffc8a8c35 in queue_dispatch () at 
/usr/lib/x86_64-linux-gnu/libsoup-3.0.so.0
#4  0x7f8002a655d1 in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f8002a65b28 in g_main_context_iterate.constprop () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f8002a65e0f in g_main_loop_run () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f8002442145 in gtk_main () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#8  0x55e74efad86e in main (argc=, argv=) at 
/run/build/evolution/src/shell/main.c:784
shell = 0x55e75057c1f0
settings = 
success = 
error = 0x0


___
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] Crashing Evolution 3.46.0 ?

2022-10-06 Thread Paul Smith
On Thu, 2022-10-06 at 08:26 +0200, Milan Crha via evolution-list wrote:
> Some info on the debugging of the Flatpak apps is here:
> https://docs.flatpak.org/en/latest/debugging.html

Thanks for that info.  I started evolution in the background inside a
flatpak --devel container, then attached to it with gdb -p from within
the container.

Hopefully the next time I get a crash I'll have some useful details...
___
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] Crashing Evolution 3.46.0 ?

2022-10-06 Thread Milan Crha via evolution-list
On Wed, 2022-10-05 at 15:33 -0400, Paul Smith wrote:
> Yesterday I updated my flatpak to Evolution 3.46.0 (from Evolution
> 3.44.x) and I'm having something of a hard time adjusting.  I'm
> running it on Ubuntu 20.04 which has native Gnome 3.36.8.

Hi,
it had been mentioned here already, see this thread (with some replies
in this month):
https://mail.gnome.org/archives/evolution-list/2022-September/msg00142.html

It's hard to say what's going on without a backtrace. That might not
necessarily point to the faulty place, but maybe it'll help a bit at
least. Debugging Flatpak applications is tricky, even more trickier for
the Evolution (notice of the `evolution.bin` in the warning, the
`/app/bin/evolution` is a wrapper script, which runs necessary services
before the `evolution.bin` binary is started).

Some info on the debugging of the Flatpak apps is here:
https://docs.flatpak.org/en/latest/debugging.html

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] Crashing Evolution 3.46.0 ?

2022-10-05 Thread Dr. John H. Lauterbach
-Original Message-
From: Michael via evolution-list 
Reply-To: michaeljke...@outlook.com
To: evolution-list@gnome.org
Subject: Re: [Evolution] Crashing Evolution 3.46.0 ?
Date: Wed, 05 Oct 2022 15:16:01 -0500

And literally after I hit send my Evolution crashed after being rock solid with 
no
crashes for 2 days... back to the drawing board.

-Original Message-
From: Michael via evolution-list 
Reply-To: michaeljke...@outlook.com
To: evolution-list@gnome.org
Subject: Re: [Evolution] Crashing Evolution 3.46.0 ?
Date: 10/05/2022 03:12:08 PM

I was having crashing issues after updating to 3.46 via flatpak update and 
opted to
just remove it and reinstall it. All has been well since.

-Original Message-
From: Paul Smith 
Reply-To: p...@mad-scientist.net
To: evolution-list@gnome.org
Subject: [Evolution] Crashing Evolution 3.46.0 ?
Date: 10/05/2022 02:33:05 PM

Yesterday I updated my flatpak to Evolution 3.46.0 (from Evolution
3.44.x) and I'm having something of a hard time adjusting.  I'm running
it on Ubuntu 20.04 which has native Gnome 3.36.8.

The biggest issue is that this version of Evolution has crashed twice
on me, so far in two days.  I was running from the command line with
some EWS debugging enabled; the failure message is:

(evolution.bin:26): GLib-GObject-CRITICAL **: 14:50:07.182: g_object_ref: 
assertion
'!object_already_finalized' failed
/app/bin/evolution: line 33:    26 Segmentation fault  (core dumped)
/app/bin/evolution.bin "$@"

journalctl reported:

Oct 05 14:50:07 llin-psh13-dsa kernel: traps: evolution.bin[26345] general 
protection
fault ip:7fa738e7f8fb sp:7ffc82903e18 error:0 in libglib-
2.0.so.0.7400.0[7fa738dee000+95000]

Unfortunately because this is a development system I have disabled the
systemd-coredump facility so I don't know how to access any flatpak
coredumps (using corectl doesn't work on my system, because during
development I want my cores to not be "managed" for me).

I don't think I was doing anything particular at the time; it's
possible this happened while email was being retrieved?

I have one IMAPX account, one GMail account, and one Exchange account
using EWS.  The GMail and Exchange accounts are configured via GOA.

If anyone knows how to find these coredumps I'm happy to take a look;
else maybe the above assertion will be helpful in some way.

Running 3.44.1-0ubuntu1  under Ubuntu Unity 22.04 on three PCs without problems.
 John
___
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] Crashing Evolution 3.46.0 ?

2022-10-05 Thread Michael via evolution-list
And literally after I hit send my Evolution crashed after being rock
solid with no crashes for 2 days... back to the drawing board.

-Original Message-
From: Michael via evolution-list 
Reply-To: michaeljke...@outlook.com
To: evolution-list@gnome.org
Subject: Re: [Evolution] Crashing Evolution 3.46.0 ?
Date: 10/05/2022 03:12:08 PM

I was having crashing issues after updating to 3.46 via flatpak update
and opted to just remove it and reinstall it. All has been well since.

-Original Message-
From: Paul Smith 
Reply-To: p...@mad-scientist.net
To: evolution-list@gnome.org
Subject: [Evolution] Crashing Evolution 3.46.0 ?
Date: 10/05/2022 02:33:05 PM

Yesterday I updated my flatpak to Evolution 3.46.0 (from Evolution
3.44.x) and I'm having something of a hard time adjusting.  I'm running
it on Ubuntu 20.04 which has native Gnome 3.36.8.

The biggest issue is that this version of Evolution has crashed twice
on me, so far in two days.  I was running from the command line with
some EWS debugging enabled; the failure message is:

(evolution.bin:26): GLib-GObject-CRITICAL **: 14:50:07.182:
g_object_ref: assertion '!object_already_finalized' failed
/app/bin/evolution: line 33:    26 Segmentation fault  (core
dumped) /app/bin/evolution.bin "$@"

journalctl reported:

Oct 05 14:50:07 llin-psh13-dsa kernel: traps: evolution.bin[26345]
general protection fault ip:7fa738e7f8fb sp:7ffc82903e18 error:0 in
libglib-2.0.so.0.7400.0[7fa738dee000+95000]

Unfortunately because this is a development system I have disabled the
systemd-coredump facility so I don't know how to access any flatpak
coredumps (using corectl doesn't work on my system, because during
development I want my cores to not be "managed" for me).

I don't think I was doing anything particular at the time; it's
possible this happened while email was being retrieved?

I have one IMAPX account, one GMail account, and one Exchange account
using EWS.  The GMail and Exchange accounts are configured via GOA.

If anyone knows how to find these coredumps I'm happy to take a look;
else maybe the above assertion will be helpful in some way.
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.gnome.org%2Fmailman%2Flistinfo%2Fevolution-listdata=05%7C01%7C%7Cb337058f05174b38e9cf08daa708784c%7C84df9e7fe9f640afb435%7C1%7C0%7C638005952064061433%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=J%2FWv0tN9Bwkzb52SR%2BXIvtxWDlnOnCLUTvIznJD5So8%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
___
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] Crashing Evolution 3.46.0 ?

2022-10-05 Thread Michael via evolution-list
I was having crashing issues after updating to 3.46 via flatpak update
and opted to just remove it and reinstall it. All has been well since.

-Original Message-
From: Paul Smith 
Reply-To: p...@mad-scientist.net
To: evolution-list@gnome.org
Subject: [Evolution] Crashing Evolution 3.46.0 ?
Date: 10/05/2022 02:33:05 PM

Yesterday I updated my flatpak to Evolution 3.46.0 (from Evolution
3.44.x) and I'm having something of a hard time adjusting.  I'm running
it on Ubuntu 20.04 which has native Gnome 3.36.8.

The biggest issue is that this version of Evolution has crashed twice
on me, so far in two days.  I was running from the command line with
some EWS debugging enabled; the failure message is:

(evolution.bin:26): GLib-GObject-CRITICAL **: 14:50:07.182:
g_object_ref: assertion '!object_already_finalized' failed
/app/bin/evolution: line 33:    26 Segmentation fault  (core
dumped) /app/bin/evolution.bin "$@"

journalctl reported:

Oct 05 14:50:07 llin-psh13-dsa kernel: traps: evolution.bin[26345]
general protection fault ip:7fa738e7f8fb sp:7ffc82903e18 error:0 in
libglib-2.0.so.0.7400.0[7fa738dee000+95000]

Unfortunately because this is a development system I have disabled the
systemd-coredump facility so I don't know how to access any flatpak
coredumps (using corectl doesn't work on my system, because during
development I want my cores to not be "managed" for me).

I don't think I was doing anything particular at the time; it's
possible this happened while email was being retrieved?

I have one IMAPX account, one GMail account, and one Exchange account
using EWS.  The GMail and Exchange accounts are configured via GOA.

If anyone knows how to find these coredumps I'm happy to take a look;
else maybe the above assertion will be helpful in some way.
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.gnome.org%2Fmailman%2Flistinfo%2Fevolution-listdata=05%7C01%7C%7Cb337058f05174b38e9cf08daa708784c%7C84df9e7fe9f640afb435%7C1%7C0%7C638005952064061433%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=J%2FWv0tN9Bwkzb52SR%2BXIvtxWDlnOnCLUTvIznJD5So8%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


[Evolution] Crashing Evolution 3.46.0 ?

2022-10-05 Thread Paul Smith
Yesterday I updated my flatpak to Evolution 3.46.0 (from Evolution
3.44.x) and I'm having something of a hard time adjusting.  I'm running
it on Ubuntu 20.04 which has native Gnome 3.36.8.

The biggest issue is that this version of Evolution has crashed twice
on me, so far in two days.  I was running from the command line with
some EWS debugging enabled; the failure message is:

(evolution.bin:26): GLib-GObject-CRITICAL **: 14:50:07.182: g_object_ref: 
assertion '!object_already_finalized' failed
/app/bin/evolution: line 33:26 Segmentation fault  (core dumped) 
/app/bin/evolution.bin "$@"

journalctl reported:

Oct 05 14:50:07 llin-psh13-dsa kernel: traps: evolution.bin[26345] general 
protection fault ip:7fa738e7f8fb sp:7ffc82903e18 error:0 in 
libglib-2.0.so.0.7400.0[7fa738dee000+95000]

Unfortunately because this is a development system I have disabled the
systemd-coredump facility so I don't know how to access any flatpak
coredumps (using corectl doesn't work on my system, because during
development I want my cores to not be "managed" for me).

I don't think I was doing anything particular at the time; it's
possible this happened while email was being retrieved?

I have one IMAPX account, one GMail account, and one Exchange account
using EWS.  The GMail and Exchange accounts are configured via GOA.

If anyone knows how to find these coredumps I'm happy to take a look;
else maybe the above assertion will be helpful in some way.
___
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
https://mail.gnome.org/mailman/listinfo/evolution-list