Impatience is bad -- clutter leaving ghosts?

Bug #224700 reported by Jamie Bennett
4
Affects Status Importance Assigned to Milestone
Entertainer Media Center
Triaged
Low
Unassigned

Bug Description

** IMPORTED FROM GOOGLE CODE **

Reported by nox.hand, Feb 27, 2008

Yeah, this is sorta a bug for the ones who like to be FAST in menus. Go to
any menu where you can go back two slides (with the slide effect ON), and
then press Backspace twice fast'ish. You will now have an echo of where you
pressed back last time, which will not disappeare before quit.

Running Ubuntu 7.10, Entertainer Revision 203

Screenshot provided.

 Screenshot.png
993 KB Download
Comment 1 by nox.hand, Feb 27, 2008

Oh, and yeah, sorry I overdid it on the screenshot;). I also forgot to edit priority.
Not a HUGE bug but would turn off new users that are a bit fast.

Comment 2 by rockstar.dev, Mar 06, 2008

I can't reproduce this on my system. Could you provide more details?

What is your video card?
What version of clutter are you running?

Comment 3 by nox.hand, Mar 06, 2008

Roger. *whips out project laptop*

I have just noticed today, that it is *not* impatience that is causing it, for if one
navigates normally it happens, too. I am thinking it *may* be my resolution doing it.
Running at 1024x768 and having Full Screen downscale 1440x900 may not be wise? Will
have to see when resolution independence is fixed :)

I have an Intel 82852/855GM graphics card in this laptop, and clutter version (got it
from the o-hand repo) says in python when I import it that it is version 0.6.0

But yes, I am thinking it may indeed just be the resolution doing it. Not quite sure.

It works fine if I disable effects though, so for now, just no effects =)

Tags: defect
Revision history for this message
Jamie Bennett (jamiebennett) wrote :
Revision history for this message
Matt Layman (mblayman) wrote :

I've confirmed this in the past by replicating what nox.hand did. I just had no way to indicate it as confirmed in Google Code.

Changed in entertainer:
importance: Undecided → Low
status: New → Confirmed
Paul Hummer (rockstar)
Changed in entertainer:
status: Confirmed → Triaged
Revision history for this message
Joshua Scotton (joshuascotton) wrote :

this is the same on mine

Revision history for this message
Andrew (and471) wrote :

Same here, it happens to me

Revision history for this message
John 'nox' Hand (john-nox-hand) wrote :

Well, the best way for me to reproduce it usually is to go deep into the RSS reader, and then quickly move back out through menus. That usually does it for me. However, been a while since I got Entertainer running, I am trying to make it run on OpenSuSE at the moment, but dependencies are annoying ;)

Changed in entertainer:
assignee: nobody → samuel-buffet
status: Triaged → In Progress
Revision history for this message
Samuel Buffet (samuel-buffet) wrote :

When we press the *back* key to quickly, we start another change of screen without reaching the end of the first one (=> we do not remove the previous screen's Actors from the stage)

I've done a fix which freeze key events as long as screens transitions are not finished.

Revision history for this message
John 'nox' Hand (john-nox-hand) wrote : Re: [Bug 224700] Re: Impatience is bad -- clutter leaving ghosts?

I may be quite wrong, but won't that potentially open up another bug, where
if a transition fails or stalls due to computer power, you will not be able
to do anything else?

As said I am likely wrong :)

On Sun, Oct 5, 2008 at 8:55 PM, Samuel Buffet <email address hidden>wrote:

> When we press the *back* key to quickly, we start another change of
> screen without reaching the end of the first one (=> we do not remove
> the previous screen's Actors from the stage)
>
> I've done a fix which freeze key events as long as screens transitions
> are not finished.
>
> --
> Impatience is bad -- clutter leaving ghosts?
> https://bugs.launchpad.net/bugs/224700
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Samuel Buffet (samuel-buffet) wrote :

2008/10/5 John 'nox' Hand <email address hidden>:
> I may be quite wrong, but won't that potentially open up another bug, where
> if a transition fails or stalls due to computer power, you will not be able
> to do anything else?
>
> As said I am likely wrong :)

Hi John, and thanks to comment.

Yes your are right, if a transition fails then you have to kill and restart.

Btw, the probability to have a failure there is very low(1) and the
probability to have a *quick* user is much much higher.

I'll discuss of that with others.

Thanks again.

Samuel,

(1) :
Between the moment where the freezing starts up to where it's released
there's no more than 20 lines of code with mainly Clutter stuff.

Changed in entertainer:
assignee: Samuel Buffet (samuel-buffet) → nobody
status: In Progress → Triaged
Revision history for this message
John 'nox' Hand (john-nox-hand) wrote : +Hi+
Revision history for this message
John 'nox' Hand (john-nox-hand) wrote :
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.