On Mon, 2022-10-10 at 18:35 -0500, Tim McConnell via evolution-list
wrote:
> So now the question is do I file a bug with libglib or libsoup?
Hi,
Andre is right, there are missing the debug symbols, making the
backtrace useless for any real bug filling, but even with so sparse
information
On Mon, 2022-10-10 at 18:35 -0500, Tim McConnell wrote:
> I got the backtrace:
Please install debug packages for glib2 and libsoup3 to get a more
complete backtrace. The current one lacks any symbols.
> (gdb) evolution --ex r
That makes no sense and is not what Milan wrote.
Cheers,
andre
--
On Mon, 2022-09-26 at 07:15 +0200, Milan Crha via evolution-list wrote:
> On Fri, 2022-09-23 at 12:47 -0500, Tim McConnell via evolution-list
> wrote:
> > I'm on Evolution 3.45.3-2 and my logwatch has been reporting
> > segmentation faults for the last few days.
>
> Hi,
> I do not know wha
On Sun, 2022-10-09 at 22:36 +0100, Patrick O'Callaghan wrote:
> On Sun, 2022-10-09 at 14:27 -0500, Tim McConnell via evolution-list
> wrote:
> > > I would think so. The debugger just sets a signal trap, so I
> > > wouldn't
> > > expect the CPU usage to change, as Evo will run at normal speed
> > >
On Sun, 2022-10-09 at 14:27 -0500, Tim McConnell via evolution-list
wrote:
> > I would think so. The debugger just sets a signal trap, so I
> > wouldn't
> > expect the CPU usage to change, as Evo will run at normal speed
> > until
> > something "interesting" happens.
>
> [...]
> That's good, it
On Sat, 2022-10-08 at 11:48 +0100, Patrick O'Callaghan wrote:
> On Fri, 2022-10-07 at 16:44 -0500, Tim McConnell via evolution-list
> wrote:
> > > "gdb something --ex r" will just start "something" under the
> > > debugger
> > > and then let it run until it either exists or crashes. It won't
> > >
On Fri, 2022-10-07 at 16:44 -0500, Tim McConnell via evolution-list
wrote:
> > "gdb something --ex r" will just start "something" under the
> > debugger
> > and then let it run until it either exists or crashes. It won't
> > create
> > any files on its own.
> >
> > poc
> [...]
> Thanks for that i
On Fri, 2022-10-07 at 22:12 +0100, Patrick O'Callaghan wrote:
> On Fri, 2022-10-07 at 15:11 -0500, Tim McConnell via evolution-list
> wrote:
> > On Mon, 2022-09-26 at 07:15 +0200, Milan Crha via evolution-list
> > wrote:
> > > On Fri, 2022-09-23 at 12:47 -0500, Tim McConnell via evolution-
> > > li
On Fri, 2022-10-07 at 15:11 -0500, Tim McConnell via evolution-list
wrote:
> On Mon, 2022-09-26 at 07:15 +0200, Milan Crha via evolution-list
> wrote:
> > On Fri, 2022-09-23 at 12:47 -0500, Tim McConnell via evolution-list
> > wrote:
> > > I'm on Evolution 3.45.3-2 and my logwatch has been reportin
On Mon, 2022-09-26 at 07:15 +0200, Milan Crha via evolution-list wrote:
> On Fri, 2022-09-23 at 12:47 -0500, Tim McConnell via evolution-list
> wrote:
> > I'm on Evolution 3.45.3-2 and my logwatch has been reporting
> > segmentation faults for the last few days.
>
> Hi,
> I do not know wha
On Mon, 2022-10-03 at 08:07 +0200, Milan Crha via evolution-list wrote:
> On Sat, 2022-10-01 at 14:39 -0500, Tim McConnell via evolution-list
> wrote:
> > But for those that don't know it:
>
> Hi,
> I see, thanks. My memory is rusty, which doesn't help in many ways.
> I'm
> sorry about th
On Sat, 2022-10-01 at 14:39 -0500, Tim McConnell via evolution-list
wrote:
> But for those that don't know it:
Hi,
I see, thanks. My memory is rusty, which doesn't help in many ways. I'm
sorry about that.
> one when I clicked on a link from an email (job posting)
A process started from
On Sat, 2022-10-01 at 22:56 +0100, Pete Biggs wrote:
> On Sat, 2022-10-01 at 14:39 -0500, Tim McConnell via evolution-list
> wrote:
> > On Sat, 2022-10-01 at 10:36 +0200, Andre Klapper via evolution-list
> > wrote:
> > > On Fri, 2022-09-30 at 15:35 -0500, Tim McConnell via evolution-
> > > list
> >
On Sat, 2022-10-01 at 14:39 -0500, Tim McConnell via evolution-list
wrote:
> On Sat, 2022-10-01 at 10:36 +0200, Andre Klapper via evolution-list
> wrote:
> > On Fri, 2022-09-30 at 15:35 -0500, Tim McConnell via evolution-list
> > wrote:
> > > I did get these minor errors:
> >
> > These are not "er
On Sat, 2022-10-01 at 10:50 +0200, Ralf Mardorf via evolution-list
wrote:
> On Sat, 2022-10-01 at 10:36 +0200, Andre Klapper wrote:
> > We still have no idea what "Logwatch" is.
>
> Hi,
>
> maybe the OP does use https://wiki.archlinux.org/title/Logwatch ,
> also
> see https://sourceforge.net/proj
On Sat, 2022-10-01 at 10:36 +0200, Andre Klapper via evolution-list
wrote:
> On Fri, 2022-09-30 at 15:35 -0500, Tim McConnell via evolution-list
> wrote:
> > I did get these minor errors:
>
> These are not "errors" but output. Apart from one line, they are
> unrelated to Evolution. We still have n
On Sat, 2022-10-01 at 10:36 +0200, Andre Klapper wrote:
> We still have no idea what "Logwatch" is.
Hi,
maybe the OP does use https://wiki.archlinux.org/title/Logwatch , also
see https://sourceforge.net/projects/logwatch/
or https://ubuntu.com/server/docs/logwatch .
Regards,
Ralf
___
On Fri, 2022-09-30 at 15:35 -0500, Tim McConnell via evolution-list
wrote:
> I did get these minor errors:
These are not "errors" but output. Apart from one line, they are
unrelated to Evolution. We still have no idea what "Logwatch" is.
Cheers,
andre
--
Andre Klapper | ak...@gmx.net
https://b
Hi Milan,
So I've followed the steps you sent and now it doesn't crash. It hasn't
shown any segmentation faults in my Logwatch report either.
I have been doing upgrades as they are released for Debian Testing
(Bookworm) so that may have solved it?
While I was trying to recreate the issue, I did ge
On Fri, 2022-09-23 at 12:47 -0500, Tim McConnell via evolution-list
wrote:
> I'm on Evolution 3.45.3-2 and my logwatch has been reporting
> segmentation faults for the last few days.
Hi,
I do not know what logwatch is, nor how one gets more detailed
information out of it, but if you face e
Hi List,
I'm on Evolution 3.45.3-2 and my logwatch has been reporting
segmentation faults for the last few days.
This is what it's showing me:
- Kernel Begin
WARNING: Segmentation Faults in these executables
evolution : 2 Time(s)
21 matches
Mail list logo