After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 789797 - gnome-shell sometimes segfaults in init_output on HDMI hotplug events
gnome-shell sometimes segfaults in init_output on HDMI hotplug events
Status: RESOLVED DUPLICATE of bug 789501
Product: gnome-shell
Classification: Core
Component: general
3.24.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-11-02 02:34 UTC by Robert Hancock
Modified: 2017-11-02 02:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Robert Hancock 2017-11-02 02:34:12 UTC
I have seen a bug across several GNOME versions where gnome-shell sometimes segfaults when a TV and AV receiver connected to the machine is turned off. This obviously triggers at least one, if not several HDMI hotplug events. It's not 100% reproducible but happens often enough to be annoying.

The ABRT bug report from Fedora against version 3.24.3 is here:

https://bugzilla.redhat.com/show_bug.cgi?id=1485786

with the stack trace being:

 #0 init_output at backends/native/meta-monitor-manager-kms.c:829
 #1 init_outputs at backends/native/meta-monitor-manager-kms.c:1175
 #2 meta_monitor_manager_kms_read_current at backends/native/meta-monitor-manager-kms.c:1213
 #3 meta_monitor_manager_read_current_state at backends/meta-monitor-manager.c:1719
 #4 handle_hotplug_event at backends/native/meta-monitor-manager-kms.c:1608
 #5 on_uevent at backends/native/meta-monitor-manager-kms.c:1624
 #10 monitor_event at gudev/gudevclient.c:104
 #15 meta_run at core/main.c:648

This problem has happened since around version 3.22 starting in March 2017.
Comment 1 Jonas Ådahl 2017-11-02 02:53:48 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

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