Summary: | Kontact crashes at restart, after showing prior disfunctional behavior in one of the following: filters, not showing mail or not filtering mail or archiving fails for a specific (alway different folder). | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | stakanov.s |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | REPORTED --- | ||
Severity: | crash | CC: | bugrprt21882 |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
stakanov.s
2021-03-13 12:12:50 UTC
Created attachment 137325 [details]
New crash information added by DrKonqi
kontact (5.14.2 (20.04.2)) using Qt 5.12.7
- What I was doing when the application crashed:
Looked at a Planet openSUSE news feed – "Rancher 2.5.7 with container in Azure".
Then, began to write a new KMail mail - Bong ... [ On Easter Sunday - GRRRrrrr!!!! ]
-- Backtrace (Reduced):
#5 0x00007f5eb752088a in QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, base::OnceCallback<void (int)>, GURL*) (this=0x55e3f97d6e20, request=0x7f5e1021f370, callback=..., newUrl=0x7f5e1021f560) at /usr/src/debug/libqt5-qtwebengine-5.12.7-lp152.2.9.x86_64/src/core/net/network_delegate_qt.cpp:245
#6 0x00007f5eb9407810 in net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*, base::OnceCallback<void (int)>, GURL*) () at ../../3rdparty/chromium/net/base/network_delegate.cc:33
#7 0x00007f5eb95638a0 in net::URLRequest::Start () at ../../3rdparty/chromium/net/url_request/url_request.cc:555
#8 0x00007f5eb8c90370 in content::ResourceLoader::StartRequestInternal () at ../../3rdparty/chromium/content/browser/loader/resource_loader.cc:633
#9 0x00007f5eb8c90ac5 in content::ResourceLoader::Resume () at ../../3rdparty/chromium/content/browser/loader/resource_loader.cc:552
(In reply to Don Curtis from comment #1) > Looked at a Planet openSUSE news feed – "Rancher 2.5.7 with container in > Azure". And, this is 100 % reproducible – had the news feed reopened to grab the title for this report, closed it and moved to write the e-Mail I was about to write before -- Bonggg!!!! ... (In reply to Don Curtis from comment #2) > And, this is 100 % reproducible – had the news feed reopened to grab the > title for this report, closed it and moved to write the e-Mail The News Feed has to have been closed - from display in a new Akregator tab. If it's open in a new Akregator tab, the segmentation fault doesn't occur. If another Planet openSUSE article is opened and the closed - for example "Interview auf gnulinux.ch" - the segmentation fault also occurs . . . |