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 701992 - Inconsistent behavior in File Roller when creating a new archive
Inconsistent behavior in File Roller when creating a new archive
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2013-06-11 09:07 UTC by Ewan.LEBIDEAU-CANEVET
Modified: 2013-07-09 14:03 UTC
See Also:
GNOME target: ---
GNOME version: 3.7/3.8



Description Ewan.LEBIDEAU-CANEVET 2013-06-11 09:07:25 UTC
User can notice that opening two "new archive" windows will have inconsistent behavior - writing in the focused window actually writes in the unfocused window.

Steps :

1. Boot System
2. Start File Roller
3. Click on new archive
4. From the top bar, select again "new archive"
5. Observe you have 2 "new archive windows", one focused and one unfocused
6. Try to click on the other unfocused window, observe you can't
7. Start writing on the focused window, observe that you actually write in the unfocused one

Expected outcome

You can focus any of the 2 windows and typing in the focused one does not show test in the unfocused window

Actual outcome

Can't switch windows and text is inputted into wrong window
Comment 1 Paolo Bacchilega 2013-06-12 08:40:01 UTC
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 2 Philippe "RzR" Coval 2013-07-09 13:04:11 UTC
I tested file-roller 3.8.3 and it still behave the same ... is that fix also integrated on gnome-3-8 branch ? if not why ?

My expected behaviour will be to focus on the existing dialog
Comment 3 Paolo Bacchilega 2013-07-09 14:03:46 UTC
The problem is fixed only in current development version (3.9.3), I forgot to fix it for the 3.8 series, it will be available in version 3.8.4.