Description of problem: kmail shows same email and does not move to next email. moving the mouse shows same message over and over again... org.kde.pim.webengineviewer: WebEngine render process crashed ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 Version-Release number of selected component (if applicable): mga8beta2 How reproducible: You will need to have some mail in kmail. I copied a maildir type subfolder{cur, new, tmp} from a working kmail to .local/share/local-mail/inbox-2019/{cur/ new/ tmp/} Then opened a terminal, and ran kmail. pointing to inbox-2019, I clicked on an email which rendered, you will notice clicking other emails still shows the first email chosen, but at the same time the terminal is scrolling a lot of crash reports every time you move the mouse. Steps to Reproduce: 1. create a subfolder in kmail, such as inbox-temp with email from an earlier version of kmail 2. select an email to view 3. point to the viewing panel (to read the email)and move the mouse. 4. you will note that kmail keeps coming to the surface. More information about searching for: kde 3rdparty/chromium/sandbox/linux/seccomp-bpf-helper shows [solved] https://bugzilla.redhat.com/show_bug.cgi?id=1773289 solved upstream as something to do with clock_nanosleep also debian points towards qt5 engine: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969360 gentoo has a workaround - not a fix - here: https://forums.gentoo.org/viewtopic-t-1081038-start-0.html
Upstream bug you refered is fixed since QT 5.15.0.alpha1 https://bugreports.qt.io/browse/QTBUG-81313?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aworklog-tabpanel Since we use QT 5.15.0 and I can't reproduce this on my freshly Magiea 8 Cauldron install since Beta 1 ISO and always updated. So my question is : Have you updated all packages by adding online repositories and do: # urpmi --auto-update
CC: (none) => ouaurelien
URL: (none) => https://bugreports.qt.io/browse/QTBUG-81313?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aworklog-tabpanel
Hi Aurelien, I've been trying to maintain 32bit as far as possible (for printer driver, and wine32, plus doing 32bit development sometimes finds some bugs that are not seen in 64bit). 1. Classic install (32bit) - from iso copied to USBstick. 2. video set to Xorg vesa (since NV42GL [Quadro FX 3450/4000 SDI] is obsolete since mga6). 3. copied email files to ./local/share/local-mail/inbox-2019/{cur/*, new/*, tmp/*} since the kmail wizard doesn't complete (maybe only for large inbox folders - small folder of 93 emails worked). 4. tried kmail2 - failed. 5. updated everything. 6. tried kmail2 - failed. 7. created a new user and tried a new user - with sqlite instead of mysql. Do this mod before running anything with akonadi ( https://shevchuk.co/notes/2018/03/04/reduce-akonadi-memory-usage-to-40-mb ). No change. 8. updated everything - wrote bug report. 8. just updated everything now - this morning. 9. interesting....today... from terminal...ran kmail.... seems I can now move between emails, much better, however....the crash report remains scrolling along. I also note that kmail keeps trying to steal focus on screen repaints, so it keeps coming into focus while I attempted to write this additional comment. I had to close kmail to be able to complete this comment. ...however... it is improved from yesterday. 10. I will perform a restart right now - to ensure I'm seeing today's changes and nothing from yesterday's update.
Performed reboot - appears I can navigate through a small folder "inbox-2019" of about 100 emails. from terminal ran kmail.... these are the various errors that scroll by (depending on which view pane you look at): this is for the email view panel: org.kde.pim.webengineviewer: WebEngine render process crashed ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 this is from one of the other panels: org.kde.pim.webengineviewer: WebEngine render process crashed qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3267, resource id: 96469063, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3293, resource id: 96469063, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3299, resource id: 96469063, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3307, resource id: 96469063, major code: 130 (Unknown), minor code: 3 I'm not sure when I hit this since most of the errors is the first (above): org.kde.pim.webengineviewer: WebEngine render process crashed org.kde.pim.akonadicore: Received response with a different tag! This error starts right from the beginning: Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Connection to speech-dispatcher failed Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls") qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 1852, resource id: 96469063, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 1857, resource id: 96469063, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 1860, resource id: 96469063, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 1868, resource id: 96469063, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 1875, resource id: 96469063, major code: 130 (Unknown), minor code: 3 qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 1882, resource id: 96469063, major code: 130 (Unknown), minor code: 3 ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 org.kde.pim.webengineviewer: WebEngine render process crashed ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 org.kde.pim.webengineviewer: WebEngine render process crashed this statement shows up at the end when shutting down kmail: Connection to speech-dispatcher failed If any of the above messages help improve kmail - great! If not, well...okay. kmail continues to steal focus (had firefox overlapping kmail), also had kwrite overlapping a small corner of kmail, and kmail had to bring itself into main focus again - but this is probably another bug to resolve.
testing (above) done on user (with akonadi / mysql).
(In reply to Joe Da Silva from comment #3) > this is from one of the other panels: > org.kde.pim.webengineviewer: WebEngine render process crashed > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3267, > resource id: 96469063, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3293, > resource id: 96469063, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3299, > resource id: 96469063, major code: 130 (Unknown), minor code: 3 > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3307, > resource id: 96469063, major code: 130 (Unknown), minor code: 3 xcb arrors are irrelevant for this bug. It's QT logging facility bug. > I'm not sure when I hit this since most of the errors is the first (above): > org.kde.pim.webengineviewer: WebEngine render process crashed > org.kde.pim.akonadicore: Received response with a different tag! > This error starts right from the beginning: > Connection to speech-dispatcher failed > Connection to speech-dispatcher failed Also in x86_64 hardware, as speech-dispatcher not installed by default. Missing dependency? This should be a other bug report candidate. > Cannot initialize model with data QJsonObject() . missing: > QJsonValue(string, "urls") > ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc: > **CRASHING**:seccomp-bpf failure in syscall 0403 > org.kde.pim.webengineviewer: WebEngine render process crashed > ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc: > **CRASHING**:seccomp-bpf failure in syscall 0403 > org.kde.pim.webengineviewer: WebEngine render process crashed > I think this should be reported upstream. I will try to reproduce this on a 32 bit vm, but I get no such bug with my x86_64 installation. So. 32 bits version could have a bug? Assigning to KDE Team maintainers for forensics.
Target Milestone: --- => Mageia 8Summary: mga8beta2 - kmail2 - org.kde.pim.webengineviewer: WebEngine render process crashed => kmail2 - org.kde.pim.webengineviewer: WebEngine render process crashedAssignee: bugsquad => kdeHardware: All => i586
Source RPM: (none) => kmail-20.08.0-1.mga8.src.rpm
Thanks Aurelien, Bugzilla created for Kmail, upstream for original bug: https://bugs.kde.org/show_bug.cgi?id=426547 I mentioned about the second bug - we will see if another bugreport is needed for the other defect. FYI - the debian bug report also mentions something about 32bit near the end of it's bug report but maybe it might be for something similar - I did not follow-up on that vector - mentioned as: "The syscalls are not the same. The new ones are using 64-bit time instead of 32-bit: clock_nanosleep vs. clock_nanosleep_time64" Yes - 32bit appears to have a bug, or bugs. I expect there are a lot of "int/uint" style values that don't translate well between 32bit/64bit code.
Should be fixed with qtwebengine5-5.15.1-2.mga8!
CC: (none) => geiger.david68210
Confirmed - do not see this error message anymore: org.kde.pim.webengineviewer: WebEngine render process crashed ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0403 NOTE: Tested in xfce (since Plasma was down with these lastest set of patches).
more updates - confirmed again - works well in Plasma. Error message not seen. I think this ticket can be closed.
Thank you for the +ve feedback.
Resolution: (none) => FIXEDStatus: NEW => RESOLVEDCC: (none) => lewyssmith