Bug 690306 - [gnome3] Fileoperations shown twice
Summary: [gnome3] Fileoperations shown twice
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Final
Hardware: 32bit openSUSE 11.4
: P5 - None : Normal with 1 vote (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 17:34 UTC by Thomas Anders
Modified: 2013-11-23 20:02 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Anders 2011-04-27 17:34:03 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux i686; rv:2.0.0) Gecko/20100101 Firefox/4.0

Fileoperations-Window is shown twice (ex. Copy File from A to B). Often happens when a transfer is in progress and you start another. 

Reproducible: Always

Steps to Reproduce:
1. Copy larger File from A to B
2. Copy another one
3. Got it =)
Actual Results:  
Operations shown twice

Expected Results:  
Shown just one Filetransfer
Comment 1 Richard Brown 2011-05-07 13:14:31 UTC 
I have also seen this problem. As with the initial report it doesn't appear to happen for the first nautilus file operation, but will show 2 operations for every subsequent operation while the first is being carried out

Appears to be totally cosmetic, I see no evidence that Nautilus is actually doing double file operations.
Comment 2 Aleksander Gut 2011-12-17 21:43:12 UTC 
Not exist in 12.1
Comment 3 Dominique Leuenberger 2013-11-23 20:02:22 UTC 
Dear Reporter,

Thank you for taking the time to report this bug and helping to make openSUSE better.

We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in openSUSE since the time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a current, supported openSUSE version.

When you test it and it is still an issue, kindly reopen this bug and move it to the tested version of openSUSE. 

Truly yours.