[Webkit-unassigned] [Bug 260343] New: segfault in evolution during gmail add new account oauth2 request
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Aug 17 04:45:53 PDT 2023
https://bugs.webkit.org/show_bug.cgi?id=260343
Bug ID: 260343
Summary: segfault in evolution during gmail add new account
oauth2 request
Product: WebKit
Version: Other
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebKitGTK
Assignee: webkit-unassigned at lists.webkit.org
Reporter: i400sjon+webkit at gmail.com
CC: bugs-noreply at webkitgtk.org
Created attachment 467306
--> https://bugs.webkit.org/attachment.cgi?id=467306&action=review
various debug information
When adding a new gmail account the program locks up when the gmail oauth2 dialogue is presented.
The initial "enter email" web-dialogue is fine but pressing on next bugs out.
If the email box is blanked out then it presents the "enter an email or phone number" error message with no problems.
If an invalid email is entered it also bugs out.
The bug causes the web-dialogue to blank out and the url to clear when tabbing from evolution to another program and back (or clicking on another application if evolution is not full screen).
The "cancel" button below the web-dialogue can be pressed and it closes the window.
I have attached a file containing:
inxi output.
evolution command line debug output (including bug).
active xorg.conf.
joburnalctl segfault information.
webkit information from within evolution (reports the same no matter if WEBKIT_DISABLE_COMPOSITING_MODE= is 1 or 0). Should be noted that copy to clipboard button doesn't!
I should also note that when I had 64G of ram in this laptop it would hard crash (like just randomly power off and the uefi bios would report "0" memory even though linux would report 64G and memtest would report 64G and pass with no problems).
The amd spec is for 64G(2*32); the HP spec is for 16G(2*8); I currently have 32G(2*16) and have had no crashing issues since (multiple months).
Just to make sure this was not the problem I downgraded to 16G and still got the same bugs. The reports are with 32G.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20230817/9e65dc09/attachment.htm>
More information about the webkit-unassigned
mailing list