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 765067 - Broken progress bar popover for copy items after closing all nautilus windows and opening a new one
Broken progress bar popover for copy items after closing all nautilus windows...
Status: RESOLVED DUPLICATE of bug 764060
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-04-14 18:02 UTC by Atri
Modified: 2016-07-02 13:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Scrrenshot of broken progress popover (448.14 KB, image/png)
2016-04-14 18:02 UTC, Atri
Details

Description Atri 2016-04-14 18:02:17 UTC
Created attachment 326044 [details]
Scrrenshot of broken progress popover

See attached screenshot which shows how the broken copy progress popover looks like (black shaded region in the sidebar is my doing to obscure my google-drive user names). To reproduce this:

1. Start copying a file to some new location.
2. While the copying is in progress, close all open nautilus windows.
3. Open a new nautilus window.
Bingo!
Comment 1 Christian Stadelmann 2016-04-15 14:58:43 UTC
In my case (gnome 3.20, nautilus 3.20.0, gtk 3.20.2, running on wayland) the popover doesn't show up any more at all.
Comment 2 Atri 2016-04-15 17:05:08 UTC
Just to clarify: I am running my gnome session under X11.
Comment 3 Atri 2016-04-15 19:35:16 UTC
Indeed if I use a wayland session, I can confirm exactly what Christian says in c2.
Comment 4 Neil Herald 2016-04-17 08:36:54 UTC
The original bug raised is a dup of 764060. Sounds like c2 is a separate issue.
Comment 5 Amit Mendapara 2016-06-22 15:33:07 UTC
Same issue: https://bugs.archlinux.org/task/49493
Comment 6 Ernestas Kulik 2016-07-02 13:07:30 UTC

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