[kmail2] [Bug 371859] Segfault of kmail when removing a mail

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=371859

Christoph Feck  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED

--- Comment #4 from Christoph Feck  ---


*** This bug has been marked as a duplicate of bug 368371 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 371859] Segfault of kmail when removing a mail

[Jan-Matthias Braun]

https://bugs.kde.org/show_bug.cgi?id=371859

--- Comment #3 from Jan-Matthias Braun  ---
(In reply to Michael.Calmer from comment #2)
> (In reply to Jan-Matthias Braun from comment #1)
> > I do have a question. I am experiencing problems with current QtWebEngine
> > based kmail too: Sometimes, the mail display will become empty after a short
> > delay. Changing to another mail and then back has a slight chance of not
> > triggering this behaviour. If the mail display is blank and I trigger any
> > message related, e.g., reply, forward, delete, kmail crashes.
> 
> My crash happens not only while removing a mail. 

action, I wanted to write: any nessage releted action. ^^

> > But if I redisplay the message and do the same action while the display is
> > intact, everything will work fine.
> 
> Well, I cannot make the message visible. "redisplay" is not really working
> for me.

So you never see the message? I can at least see it shortly before it
vanishes...

> > Do you observe similar behaviour? Or should I file a new bug.
> 
> Sounds a bit similar to what I see. 
> 
> > My backtrace hints to QtWebEngine. But unfortunately, I am using
> > self-compiled qt 5.7 and the debug build for QtWebEngine is exhausting my
> > disk space, i.e., my backtrace is worthless.
> 
> I also saw other bugreports which point to this component together with the
> use of the "nouveau" driver.

I am using an up-to-date proprietary nvidia driver.

I will try to get some useful debug information.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 371859] Segfault of kmail when removing a mail

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=371859

--- Comment #2 from michael.cal...@gmx.de ---
(In reply to Jan-Matthias Braun from comment #1)
> I do have a question. I am experiencing problems with current QtWebEngine
> based kmail too: Sometimes, the mail display will become empty after a short
> delay. Changing to another mail and then back has a slight chance of not
> triggering this behaviour. If the mail display is blank and I trigger any
> message related, e.g., reply, forward, delete, kmail crashes.

My crash happens not only while removing a mail. 

> But if I redisplay the message and do the same action while the display is
> intact, everything will work fine.

Well, I cannot make the message visible. "redisplay" is not really working for
me.

> Do you observe similar behaviour? Or should I file a new bug.

Sounds a bit similar to what I see. 

> My backtrace hints to QtWebEngine. But unfortunately, I am using
> self-compiled qt 5.7 and the debug build for QtWebEngine is exhausting my
> disk space, i.e., my backtrace is worthless.

I also saw other bugreports which point to this component together with the use
of the "nouveau" driver.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 371859] Segfault of kmail when removing a mail

[Jan-Matthias Braun]

https://bugs.kde.org/show_bug.cgi?id=371859

Jan-Matthias Braun  changed:

   What|Removed |Added

 CC||jan_br...@gmx.net

--- Comment #1 from Jan-Matthias Braun  ---
Hi Michael,

I do have a question. I am experiencing problems with current QtWebEngine based
kmail too: Sometimes, the mail display will become empty after a short delay.
Changing to another mail and then back has a slight chance of not triggering
this behaviour. If the mail display is blank and I trigger any message related,
e.g., reply, forward, delete, kmail crashes.
But if I redisplay the message and do the same action while the display is
intact, everything will work fine.

Do you observe similar behaviour? Or should I file a new bug.

My backtrace hints to QtWebEngine. But unfortunately, I am using self-compiled
qt 5.7 and the debug build for QtWebEngine is exhausting my disk space, i.e.,
my backtrace is worthless.

Cheers,

Jan

-- 
You are receiving this mail because:
You are the assignee for the bug.