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 418395 - can not move the volume meter window
can not move the volume meter window
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
2.18.x
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2007-03-14 22:58 UTC by Sebastien Bacher
Modified: 2007-04-04 22:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Sebastien Bacher 2007-03-14 22:58:29 UTC 
The bug has been opened on https://launchpad.net/bugs/90227

"- repro:

applications -> sound & video -> volume monitor

A window opens... try to move it. I'm not able to do it.

- workaround:

resize first the window then you are able to move it..."
Comment 1 Elijah Newren 2007-03-15 01:00:04 UTC 
This turns out to be a copy-and-paste-and-forget-to-replace bug, with a one-liner fix.  The catch is that the line happens to be somewhat difficult to find (it took me a while), but I can help a new person who has some dedication find it.  And no, I won't fix this bug.  Some new person needs to come along and do so.  :)
Comment 2 Elijah Newren 2007-03-15 01:01:30 UTC 
(The new person should feel free to ask for hints after digging for a bit, because hints may well be needed.  It really wasn't quite where I expected it.)
Comment 3 Bruno Boaventura 2007-03-19 21:13:51 UTC 
Elijah,
Do you consider me as a new person? Maybe I need to leave this bug for another (newer) person.
Comment 4 Elijah Newren 2007-03-28 03:33:34 UTC 
Well, I was going to say wait a week or two to see if someone else wants to pick it up, but I somehow missed getting back to you for over a week already.  Go ahead and tackle it if you like.  Thanks!
Comment 5 Elijah Newren 2007-04-04 22:03:14 UTC 
Sorry, I guess I lied.  Twice.

There are actually three separate fixes to this bug.  Fixing any one of the issues will make this bug go away.  (But only one of them is a one-liner.)

As part of fixing up all the size increments/size limits stuff to get bugs like bug 329152 cleared out, I went ahead and fixed this one too.  Sorry, but it just didn't make sense to make a bunch of other changes (with two of them already fixing this bug as a side effect) and leave this one open.  (Leaving all three fixes out would have made fixing 329152 more difficult)