[Webkit-unassigned] [Bug 246206] [GTK] webkit2gtk 2.38.0 cause issue to lightdm-webkit2-greeter (can't login)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=246206

Michael Catanzaro <mcatanzaro at gnome.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mcatanzaro at gnome.org
            Summary|webkit2gtk 2.38.0 cause     |[GTK] webkit2gtk 2.38.0
                   |issue to                    |cause issue to
                   |lightdm-webkit2-greeter     |lightdm-webkit2-greeter
                   |(can't login)               |(can't login)

--- Comment #2 from Michael Catanzaro <mcatanzaro at gnome.org> ---
Note: this has also been reported at https://github.com/Litarvan/lightdm-webkit-theme-litarvan/issues/186 and https://github.com/NoiSek/Aether/issues/115.

(In reply to Dave from comment #0)
> Please ask if more info are needed.

The other users who noticed this had a bunch of warnings and criticals in the console output, e.g. from https://github.com/Litarvan/lightdm-webkit-theme-litarvan/issues/186#issuecomment-1257277177 we see:

(WebKitWebProcess:9872): GLib-WARNING **: 20:34:52.728: ../glib/glib/giounix.c:412Error while getting flags for FD: Bad file descriptor (9)

(WebKitWebProcess:9872): GLib-WARNING **: 20:34:52.732: Invalid file descriptor.
Connected: 0
Error: Failed to write to daemon: Bad file descriptor

To investigate this, we'd want to see a gdb backtrace to the very first warning, taken with G_DEBUG=fatal-warnings. That will point directly to the problematic file descriptor. Otherwise, no way to know where it's coming from.

-- 
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/20221007/78d65a19/attachment.htm>