Bug 470118 - Geometry info is not displayed for moving or resizing.
Summary: Geometry info is not displayed for moving or resizing.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-workspace
Version: 9
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-05 20:39 UTC by Steven W. Orr
Modified: 2009-02-06 16:24 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-06 16:19:10 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 174798 0 None None None Never

Description Steven W. Orr 2008-11-05 20:39:35 UTC
Description of problem:

kdebase-4.1.2-5.fc9.i386
Geometry info is not displayed when moving or resizing when the option to display it is set.


How reproducible:

System Settings -> Window Behavior -> Display Geometry When Moving or Resizing.
(make sure the box is checked).

Then move or resize a window.


Steps to Reproduce:
1. Check the box described above.
2. Move or resize a window.
3. Note that the geo info is not displayed
  
Actual results:

It's not displayed

Expected results:

It should be displayed.

Additional info:

Let me know if I can supply more.

Comment 1 Kevin Kofler 2008-11-05 21:34:36 UTC
KWin is in kdebase-workspace.

Comment 2 Rex Dieter 2008-11-10 16:50:38 UTC
confirmed, report upsream to bugs.kde.org please.  (else I'll do it it... eventually).

Comment 3 Steven W. Orr 2008-11-10 17:26:23 UTC
This is reported to kde.

http://bugs.kde.org/show_bug.cgi?id=174798

Comment 4 Steven M. Parrish 2009-02-06 16:19:10 UTC
Thanks for reporting upstream.  Will monitor for resolution.

Comment 5 Rex Dieter 2009-02-06 16:24:41 UTC
bonus: I *think* this is fixed in kde42 too (but don't quote me on that, don't have time to recheck)


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