Bug 688005 - F15 SVN commit dialog does not display correctly
Summary: F15 SVN commit dialog does not display correctly
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse-subclipse
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Robert Marcano
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-16 02:00 UTC by Jim Hayward
Modified: 2011-03-25 01:15 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-24 20:51:49 UTC
Type: ---


Attachments (Terms of Use)

Description Jim Hayward 2011-03-16 02:00:07 UTC
Description of problem:
The SVN commit dialog in F15 only displays the text asking you to enter a comment and the cancel/ok buttons. There isn't anywhere to enter the comment. You cannot resize the dialog to try and expose the missing widgets.

Version-Release number of selected component (if applicable):
eclipse-platform-3.6.1-5.fc15.x86_64
eclipse-subclipse-1.6.17-1.fc15.noarch
eclipse-cdt-7.0.1-5.fc15.x86_64

Screenshot of the dialog
http://www.linuxexperience.net/screens/svn_commit_dialog.png

Comment 1 Mat Booth 2011-03-20 17:24:45 UTC
This might be a Gnome 3 problem, for some reason you can no longer resize dialogs with Alt-MiddleClick like you can in Gnome 2.

Comment 2 Andrew Overholt 2011-03-24 19:30:52 UTC
I just installed F15.  I'm testing with an upstream Eclipse and Subclipse and can both see the commit message entry box and resize the dialogue.  Is it possible that something has been fixed in GNOME since you filed this bug?

Comment 3 Mat Booth 2011-03-24 20:51:49 UTC
Yes, when I updated my laptop today there was a whole slew of Gnome3 updates from update-testing. I am no longer experiencing the issue. I think this can be closed.

Jim, if you are experiencing this problem after pulling the latest F15 updates from updates-testing, please reopen.

Comment 4 Jim Hayward 2011-03-25 01:15:58 UTC
Works for me now after 205 updates today. One of today's updates must have fixed it. The problem still existed yesterday. Thanks.


Note You need to log in before you can comment on or make changes to this bug.