transmission doesn't restore to the same location when using notification area icon

Bug #343436 reported by shemgp
6
Affects Status Importance Assigned to Milestone
Transmission
Invalid
Unknown
compiz (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: transmission

I've enabled Show icon in the desktop Notification Area and when i minimize it using that icon and restore it once again, most of the times transmission doesn't show up in the previous location. It goes down and right a little bit. So if i minimize and restore it for a couple of times, it will slowly go to the bottom right of the screen.

Description: Ubuntu jaunty (development branch)
Transmission version: 1.51-0ubuntu1

Changed in transmission (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris Coulson (chrisccoulson) wrote : Re: [Bug 343436] Re: transmission doesn't restore to the same location when using notification area icon

importance low

On May 11, 2009 7:30 PM, "Krzysztof Klimonda" <
<email address hidden>> wrote:

** Changed in: transmission (Ubuntu)
      Status: New => Confirmed

--
transmission doesn't restore to the same location when using notification
area icon
https://bugs.launchpad.net/bugs/343436
You received this bug notification because you are subscribed to
transmission in ubuntu.

Status in “transmission” source package in Ubuntu: Confirmed

Bug description:
Binary package hint: transmission

I've enabled Show icon in the desktop Notification Area and when i minimize
it using that icon and restore it once again, most of the times transmission
doesn't show up in the previous location. It goes down and right a little
bit. So if i minimize and restore it for a couple of times, it will slowly
go to the bottom right of the screen.

Description: Ubuntu jaunty (development branch)
Transmission version: 1.51-0ubuntu1

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Hey Krzysztof, seeing as you're working on the merge, it would be good if you can test if this is still an issue in 1.60? If it is, then this should be forwarded to the upstream bug tracker.

Thanks

Changed in transmission (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Krzysztof Klimonda (kklimonda) wrote :

Yes, I've confirmed it with 1.60 and I'm writing a bug report to the upstream bts.

Changed in transmission (Ubuntu):
status: Incomplete → Confirmed
Changed in transmission (Ubuntu):
status: Confirmed → Triaged
Changed in transmission:
status: Unknown → New
Revision history for this message
Krzysztof Klimonda (kklimonda) wrote :

@Chris: Thanks for helping in triaging this bug. It is indeed a problem with compiz as I get following result when running transmission with it enabled:

[kklimonda@lilith result]$ transmission
** Message: saving window location as x 449, y 25
** Message: setting window location to x 449, y 25
** Message: saving window location as x 449, y 25
** Message: setting window location to x 449, y 25
** Message: saving window location as x 449, y 25
** Message: setting window location to x 449, y 25
** Message: saving window location as x 450, y 54
** Message: setting window location to x 450, y 54
** Message: saving window location as x 450, y 54
** Message: setting window location to x 450, y 54
** Message: saving window location as x 451, y 83
** Message: setting window location to x 451, y 83
** Message: saving window location as x 451, y 83
** Message: setting window location to x 451, y 83
** Message: saving window location as x 452, y 112
** Message: setting window location to x 452, y 112
** Message: saving window location as x 452, y 112
** Message: setting window location to x 452, y 112
** Message: saving window location as x 453, y 141
** Message: setting window location to x 453, y 141
** Message: saving window location as x 453, y 141
** Message: setting window location to x 453, y 141
** Message: saving window location as x 454, y 170
** Message: setting window location to x 454, y 170
** Message: saving window location as x 454, y 170
** Message: setting window location to x 454, y 170
** Message: saving window location as x 455, y 189
** Message: setting window location to x 455, y 189

What's weird is that I can't reproduce it with neither Banshee nor Rhythmbox so Transmission must do something in a different way..
What would be the best way to proceed with this bug? I'm afraid that when I submit it to compiz they will tell me that it is transmission bug and you will point to metacity and deny it..
Choices.. choices.. :)

Revision history for this message
Charles Kerr (charlesk) wrote :

I've written a small test program that has the relevant bits in Transmission. It tries to show/hide a "hello world" window twenty times so that you can see if it stairsteps down the window or not.

If the test program stairsteps for you, probably it should be passed along to the compiz developers for testing.

The program: http://transmission.pastebin.com/f3d9e1ff3

Raw download: http://transmission.pastebin.com/pastebin.php?dl=f3d9e1ff3

How to compile: cc `pkg-config --cflags --libs gtk+-2.0` hello.c -o hello

Changed in transmission:
status: New → Invalid
Revision history for this message
Charles Kerr (charlesk) wrote :

Chris and/or Krzysztof, could you please the test program above to see if it stairsteps in compiz too?

Revision history for this message
Charles Kerr (charlesk) wrote :
Revision history for this message
Charles Kerr (charlesk) wrote :
Revision history for this message
Charles Kerr (charlesk) wrote :

I went ahead and did it myself.

Attached above are videos of the "hello.c" program stairstepping in compiz, and the same program not stairstepping without compiz. It seems like this is a compiz bug, not a transmission one.

One of the launchpad masters should reassign this ticket to compiz.

affects: transmission (Ubuntu) → compiz (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.