Restoring from panel animation not opposite to minimise animation

Bug #146446 reported by will_in_wi
10
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: compiz

To reproduce, enable compiz.
Start rhythmbox.
click on the icon in the notification area twice.

Notice that when it minimizes, the window shrinks down and disappears into the icon. When it restores, the window appears as if you had just opened it.

I would expect that the window start small at the icon and then zoom out to occupy its place on the screen.

Revision history for this message
David Portwood (dzportwood) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, this compiz package is not from the official Ubuntu repositories, and as such is not supported here. Please report this bug upstream at [WWW] https://bugs.freedesktop.org/enter_bug.cgi?product=xorg . Thanks!

Changed in compiz:
status: New → Invalid
Revision history for this message
David Portwood (dzportwood) wrote :

I closed the wrong set of bugs, sorry.

Changed in compiz:
assignee: nobody → compiz
status: Invalid → New
Changed in compiz:
importance: Undecided → Low
Changed in compiz:
status: New → Confirmed
Revision history for this message
Robert Ancell (robert-ancell) wrote :

Are there any other examples of this? Note that Rhythmbox no longer minimises to the panel.

Changed in compiz (Ubuntu):
status: Confirmed → Triaged
summary: - Rhythmbox's minimize to the status bar is inconsistent in compiz
+ Restoring from panel animation not opposite to minimise animation
Revision history for this message
Scott (scott-l-barlow) wrote :

I have what I believe is a related problem. It seems that Compiz recognizes the Rhythmbox animation differently then I'd expect.

For example, I have set the animation for "Minimize Animation" to be burn. Now if I open Rhythmbox and then use the minimize button, it burns as expected. Then when I expand it again, it "burns" back onto the screen. This is all normal and all as I would expect. However, if I click on the rhythmbox button up by the clock to minimize/close/hide it, it begins to burn but will only burn for a second or so before it just all disappears. It seems to last an exact amount of time, i.e. if I make the burn animation go really, really quick then it finishes in time...if I make it go really slow, then it just barely begins to burn before it just all disappears.

Also, when I click the rhythmbox button again to bring it back out, it doesn't use burn at all. This animation seems to be controlled by whatever is set for the "Close Animation." I know that doesn't make sense...since we are opening it, not closeing it. But for me, the close animation is what shows when I open it from the tray. NOte though, that at least it works correctly - it burns all the way, it doesn't just do part of it and then appear.

Revision history for this message
Scott (scott-l-barlow) wrote :

Oh, scratch those last couple sentences...it also is messed up when using the close animation to open rhythmbox. It only shows the last portion of the animation instead of the whole thing, so a similar problem as when closing it.

Revision history for this message
Scott (scott-l-barlow) wrote :

Similarly...when I open and close pidgin by using the icon in the top left (notification area?), it seems to only use the setting for "Close Animation." I just set everything to defaults and only turned close animation to burn. Pidgin uses the burn animation when I use that button to open and close pidgin...

Revision history for this message
Scott (scott-l-barlow) wrote :

Sorry to post so many new messages...but I've also noticed that when all settings are set as default, then pidgn uses the "glide 2" when opened and "fade" when closed - which are correct. But then if I change either one of those to something else (say burn), then both opening and closing of pidgin via the icon in the notification/tray use the new setting...bizarre.

Revision history for this message
jhfhlkjlj (fdsuufijjejejejej-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in compiz (Ubuntu):
status: Triaged → Incomplete
assignee: compiz packagers (compiz) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for compiz (Ubuntu) because there has been no activity for 60 days.]

Changed in compiz (Ubuntu):
status: Incomplete → Expired
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.