RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1808900 - Drag-n-Drop (DND) frequently delayed in nautilus under wayland
Summary: Drag-n-Drop (DND) frequently delayed in nautilus under wayland
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gtk3
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Carlos Garnacho
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-01 22:55 UTC by Leon Fauster
Modified: 2021-09-01 07:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-09-01 07:27:02 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Leon Fauster 2020-03-01 22:55:59 UTC 
Description of problem:

Following are observed under RHEL8, GNOME+WAYLAND session:
Drag and drop files under nautilus have huge delays. See
https://gitlab.gnome.org/GNOME/gtk/issues/211


Version-Release number of selected component (if applicable):

$ rpm -qa |egrep "^gtk3|^nautilus"
nautilus-3.28.1-10.el8.x86_64
gtk3-3.22.30-4.el8.x86_64


How reproducible:
Open two nautilus windows and drag and drop back and forth until ...


Actual results:
Huge interaction delays in UI (files moved very delayed)


Expected results:
drop without delay


Additional info:
see above URI
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/1057
https://bugzilla.redhat.com/show_bug.cgi?id=1648569
Comment 1 Ondrej Holy 2020-03-02 12:58:21 UTC 
As per the linked merge request, this seems to be clearly gtk issue, thus changing the component.
Comment 2 Tomas Popela 2020-03-16 09:40:28 UTC 
Adding Carlos as an assignee as he has done the upstream patch. Also setting ITR to 8.3.
Comment 3 Leon Fauster 2020-03-20 14:37:08 UTC 
For verification I applied the patch https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/1057.patch into the current gtk3-3.22.30-4 EL8.1 version. The rebuild shows good results. No delays while DnD and so far no regressions.
Comment 4 Leon Fauster 2020-05-11 12:17:43 UTC 
I consider this a blocker bug (usage context: workstation with default config (wayland)). Any status update?
Comment 5 Tomas Pelka 2020-05-11 16:58:42 UTC 
Honestly I was not able to reproduce.

Can you see anything in journal when drag-n-drop?
Comment 6 Leon Fauster 2020-06-24 13:52:07 UTC 
Current setup (Version 8.2):

$ rpm -qa |egrep '^mutter|^gtk|^nauti'|sort
gtk2-2.24.32-4.el8.x86_64
gtk3-3.22.30-5.el8.x86_64
gtkmm24-2.24.5-5.el8.x86_64
gtkmm30-3.22.2-2.el8.x86_64
gtksourceview3-3.24.9-1.el8.x86_64
gtkspell-2.0.16-15.el8.x86_64
gtkspell3-3.0.9-5.el8.x86_64
gtk-update-icon-cache-3.22.30-5.el8.x86_64
gtk-vnc2-0.9.0-2.el8.x86_64
mutter-3.32.2-36.el8_2.x86_64
nautilus-3.28.1-12.el8.x86_64
nautilus-extensions-3.28.1-12.el8.x86_64
nautilus-sendto-3.8.6-2.el8.x86_64


While trying to drag two selected PDF files into a new created directory. Two times, both with delays around 10-25 seconds.
 


# journalctl -f
Jun 24 15:40:32 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:40:32 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:40:32 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:40:32 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:40:43 stand.localdomain nautilus[8192]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Jun 24 15:40:43 stand.localdomain nautilus[8192]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 24 15:40:54 stand.localdomain nautilus[8192]: g_file_get_path: assertion 'G_IS_FILE (file)' failed
Jun 24 15:40:54 stand.localdomain nautilus[8192]: g_file_get_path: assertion 'G_IS_FILE (file)' failed
Jun 24 15:41:12 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:41:12 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:41:22 stand.localdomain nautilus[8192]: Source ID 11858 was not found when attempting to remove it
Jun 24 15:41:57 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:41:57 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:41:57 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:42:01 stand.localdomain nautilus[8192]: g_file_get_path: assertion 'G_IS_FILE (file)' failed
Jun 24 15:44:01 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:44:01 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:44:01 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:44:01 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:44:08 stand.localdomain nautilus[8192]: gdkselection-wayland.c:261: error reading selection buffer: Vorgang wurde abgebrochen
Jun 24 15:44:17 stand.localdomain nautilus[8192]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Jun 24 15:44:17 stand.localdomain nautilus[8192]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jun 24 15:44:26 stand.localdomain nautilus[8192]: g_file_get_path: assertion 'G_IS_FILE (file)' failed
Jun 24 15:44:26 stand.localdomain nautilus[8192]: g_file_get_path: assertion 'G_IS_FILE (file)' failed
Comment 7 Leon Fauster 2020-06-24 14:03:51 UTC 
Maybe relevant. Because I noticed that the "fall down" selection menu (like in evolution recipients with multiple adresses) does not appears on one screen (main), just on the second screen? (Maybe an issue for a separate bugzilla entry).

This is a dual screen setup (2x HDMI). Albeit the DND issue happens while using the one or other screen.

Do not known if xdpyinfo is the right tool to collect information (Wayland display manager is used).

$ xdpyinfo |head -66
name of display:    :0
version number:    11.0
vendor string:    The X.Org Foundation
vendor release number:    12006000
X.Org version: 1.20.6
maximum request size:  16777212 bytes
motion buffer size:  256
bitmap unit, bit order, padding:    32, LSBFirst, 32
image byte order:    LSBFirst
number of supported pixmap formats:    7
supported pixmap formats:
    depth 1, bits_per_pixel 1, scanline_pad 32
    depth 4, bits_per_pixel 8, scanline_pad 32
    depth 8, bits_per_pixel 8, scanline_pad 32
    depth 15, bits_per_pixel 16, scanline_pad 32
    depth 16, bits_per_pixel 16, scanline_pad 32
    depth 24, bits_per_pixel 32, scanline_pad 32
    depth 32, bits_per_pixel 32, scanline_pad 32
keycode range:    minimum 8, maximum 255
focus:  None
number of extensions:    24
    BIG-REQUESTS
    Composite
    DAMAGE
    DOUBLE-BUFFER
    DRI3
    GLX
    Generic Event Extension
    MIT-SCREEN-SAVER
    MIT-SHM
    Present
    RANDR
    RECORD
    RENDER
    SHAPE
    SYNC
    X-Resource
    XC-MISC
    XFIXES
    XFree86-VidModeExtension
    XINERAMA
    XInputExtension
    XKEYBOARD
    XTEST
    XVideo
default screen number:    0
number of screens:    1

screen #0:
  dimensions:    3840x1200 pixels (1040x325 millimeters)
  resolution:    94x94 dots per inch
  depths (7):    24, 1, 4, 8, 15, 16, 32
  root window id:    0x3a0
  depth of root window:    24 planes
  number of colormaps:    minimum 1, maximum 1
  default colormap:    0x27
  default number of colormap cells:    256
  preallocated pixels:    black 0, white 16777215
  options:    backing-store WHEN MAPPED, save-unders NO
  largest cursor:    3840x1200
  current input event mask:    0xda0003
    KeyPressMask             KeyReleaseMask           StructureNotifyMask      
    SubstructureNotifyMask   SubstructureRedirectMask PropertyChangeMask       
    ColormapChangeMask       
  number of visuals:    270
  default visual id:  0x28
Comment 8 Matthias Clasen 2020-06-29 19:33:05 UTC 
This has a an upstream fix. Lets pick this up for 8.4
Comment 13 RHEL Program Management 2021-09-01 07:27:02 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.