Bug 1539879

Summary: Plugging in an MTP phone crashes gnome-shell drive-menu
Product: [Fedora] Fedora Reporter: Sean Sheedy <redhat>
Component: gnome-shell-extensionsAssignee: Florian Müllner <fmuellner>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 27CC: airlied, alexl, bskeggs, caillon+fedoraproject, debarshir, dimitris.on.linux, fmuellner, htl10, jglisse, john.j5live, mad_fer_it, michel, neyzanrumi, ofourdan, otaylor, pikachu.2014, rhughes, rstrode, sandmann, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 19:39:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journalctl output for crash when phone plugged in
none
journalctl output for crash when logging in with phone plugged in
none
Package versions for system reproducing the crash none

Description Sean Sheedy 2018-01-29 19:14:07 UTC
Created attachment 1387953 [details]
journalctl output for crash when phone plugged in

Description of problem:
Plugging a Samsung phone into a USB port and connecting via MTP causes Xwayland to crash.  Attempts to log in through gdm with the phone already plugged in crash as well.  Unplugging the phone allows log ins to work again.

Version-Release number of selected component (if applicable):
1.19.6-2.fc27.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Log in via gdm / Gnome shell / X11
2. Plug in phone to USB port
3. Boom

Actual results:
Xwayland crashes

Expected results:
Don't crash

Additional info:
The crash does not produce a traceback that's usable by the abrt crash reporting system.

Comment 1 Sean Sheedy 2018-01-29 19:15:13 UTC
Created attachment 1387954 [details]
journalctl output for crash when logging in with phone plugged in

Comment 2 Sean Sheedy 2018-01-29 19:16:21 UTC
Created attachment 1387955 [details]
Package versions for system reproducing the crash

Comment 3 Olivier Fourdan 2018-01-30 06:27:37 UTC
Actually, this is not an Xwayland crash:

  Stack trace of thread 8800:
  #0  0x00007f3d073ca66b raise (libc.so.6)
  #1  0x00007f3d073cc381 abort (libc.so.6)
  #2  0x0000000000594d3a OsAbort (Xwayland)
  #3  0x0000000000599f03 AbortServer (Xwayland)
  #4  0x000000000059ad25 FatalError (Xwayland)
  #5  0x00000000004233ad xwl_read_events (Xwayland)
  #6  0x00000000005928b1 ospoll_wait (Xwayland)
  #7  0x000000000058c0bb WaitForSomething (Xwayland)
  #8  0x0000000000557ed3 Dispatch (Xwayland)
  #9  0x000000000055c170 dix_main (Xwayland)
  #10 0x00007f3d073b400a __libc_start_main (libc.so.6)
  #11 0x0000000000422a9a _start (Xwayland)

Because gnome-shell/mutter starts Xwayland with “-core” any FatalError() will cause Xwayland to generte a core file, but this is not acrash, it's an abort() caused by the Wayland compositor (gnome-shell/mutter) crashing.

This can be seen in the provided logs, just before Xwayland aborts, gnome-shell had crashed:

  Jan 29 10:45:28 hhhhh.dddddd.org gnome-shell[8756]: g_object_set: assertion 'G_IS_OBJECT (object)' failed

This is a gnome-shell issue.

Comment 4 Olivier Fourdan 2018-01-30 07:11:12 UTC
Can you reproduce without the drive-menu extension in gnome-shell?

Comment 5 Olivier Fourdan 2018-01-30 10:01:00 UTC
I think this is gnome-shell-extension-drive-menu (but can't find that in the package list, so moving to gnome-shell-extensions)

Comment 6 Sean Sheedy 2018-01-30 16:41:14 UTC
Disabling just the "Removable drive menu" made no difference.  However, disabling all gnome-shell extensions prevented the crash.

Comment 7 Hin-Tak Leung 2018-01-30 18:54:39 UTC
argh, me too...

Comment 8 247 2018-02-02 19:52:24 UTC
seems that downgrading the gjs component solves the problem...or at least it solved my problem...

Comment 9 Dimitris 2018-02-02 21:14:25 UTC
This version of gjs in testing seems to fix this for me:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-653f7b61ef

Comment 10 Neyzan 2018-02-06 19:49:21 UTC
This seems to be a general issue with all usb storage devices, but as gjs 1.50.4 has been moved to stable (see the link in the previous comment by Dimitris) a simple update to this version should solve the problem.

Comment 11 Ben Cotton 2018-11-27 17:11:24 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Ben Cotton 2018-11-30 19:39:53 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.