Issue 4966 in pharo: Every single window becomes part of the background

Status: New
Owner: ----
Labels: Milestone-1.3 Type-Bug

New issue 4966 by [hidden email]: Every single window becomes  part of  
the  background
http://code.google.com/p/pharo/issues/detail?id=4966

Hi,  i'm  experiencing a strange  bug. It seems  to  happen  randomly. When  
i use a pharo image and i  leave  several windows opened and then  try to  
save and quit,  Pharo  saves  the image,  shuts down and  every seems   ok,  
but then,  i reopen my image...  all the  windows that  were opened  are  
still   there, however if a  click any of them, pharo's  menu  shows  up,  
like if  i were  clicking on the  classic white  background. Also,  if the  
most  recently windows  was a workspace,  i  can   write  on  it,  test  
code, but if i click,  the  menu shows up...    . Notice  that  i did  
also  experienced this  bug with  Pharo 1.2.  I'm attaching two  pictures  
to show this  bug.



Attachments:
        bug1.png  102 KB
        bug2.png  121 KB


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Cc: [hidden email]

Comment #1 on issue 4966 by [hidden email]: Every single window  
becomes  part of  the  background
http://code.google.com/p/pharo/issues/detail?id=4966

i remember experiencing same behavior on ubuntu. i was unable to do  
anything with UI, cannot type etc. but then if i run image using vm from  
console, it works.
I don't remember details , (maybe it was cured by not running from console  
but from shortcut on desktop), but it was only few times and i didn't put  
much attention to it.
I think it is more VM related than image related.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 4966 by [hidden email]: Every single window becomes  
part of  the  background
http://code.google.com/p/pharo/issues/detail?id=4966

Thanks for the response, and yes,  it's  like you said,  i'm using ubuntu  
10.04  64 bits and this bug it's totally  random,  but  also  not  
frequently,  i  wonder if it's then  related to ubuntu  specifically.  
Anyway, i just try not  to leave an opened  workspace.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 4966 by [hidden email]: Every single window  
becomes  part of  the  background
http://code.google.com/p/pharo/issues/detail?id=4966

I got this problem from time to time on mac.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 4966 by [hidden email]: Every single  
window becomes  part of  the  background
http://code.google.com/p/pharo/issues/detail?id=4966

Here is my experience trawled up from my earlier post to the maillist...

I have just opened a Pharo image on Windows 7 that I haven't touched in  
months.  This was originally derived from the Pharo.1.2.1.OneCick, and the  
TitleBar > 'Display Version Information'  indicates "About Pharo on Win32 -  
Pharo4.1.1 from Mar 3 2011".

I assume the image was left in good working order, but now when opening the  
image the 16 windows that were open (including a pinned World Menu) are not  
responding to any mouse click.  Clicking over them brings up a fresh World  
Menu as if I just clicked on the background.  From this fresh World Menu, I  
can open a properly functioning Workspace and Browser.

It seems like a snapshot "old" windows have become the background image,  
except that from the window-bar and bottom of screen going "Windows >  
Collapse All Windows" does collapse the "old" windows - and "Windows >  
Expand All Windows" restores them, but they still cannot be selected.

One of the "old" windows is a dialog box "Question: Save changes before  
quitting Yes/No/Cancel" which is the single "old" window I can select.  
Choosing Yes or No closes the image and choosing Cancel keeps me in the  
image, but still with none of the "old" windows selectable.   Perhaps it  
has something to do with being half way through closing the image and  
walking away while "save changes" dialog was open, and in the meantime the  
power dropped out to the machine - but that is wild speculation.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #5 on issue 4966 by [hidden email]: Every single window  
becomes  part of  the  background
http://code.google.com/p/pharo/issues/detail?id=4966

Ok, found something!!

I do not know how to reproduce it, but when it happens, the morphs are just  
locked.  Evaluate the following and see:

World submorphs select: #isLocked

And I get a great list of morphs locked :(.

Now I'm tracking how ther are locked...


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Accepted

Comment #6 on issue 4966 by [hidden email]: Every single window  
becomes  part of  the  background
http://code.google.com/p/pharo/issues/detail?id=4966

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Cc: -[hidden email]

Comment #7 on issue 4966 by [hidden email]: Every single window  
becomes  part of  the  background
http://code.google.com/p/pharo/issues/detail?id=4966

looks like the bug in modal window management, since if i am correct, this  
is the only things which using #isLocked properties.

a possible way how this can happen is when you open some modal window and  
then you got an error with debugger, and just close the debugger ignoring  
it.
as result all morphs which were locked by entering this 'modal' mode will  
stay locked.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Labels: -Milestone-1.3

Comment #8 on issue 4966 by [hidden email]: Every single window  
becomes  part of  the  background
http://code.google.com/p/pharo/issues/detail?id=4966

I will remove the 1.3 tag from this one... (not a show=stopper for 1.3, as  
it happens not very often)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Closed

Comment #9 on issue 4966 by [hidden email]: Every single window  
becomes  part of  the  background
http://code.google.com/p/pharo/issues/detail?id=4966

Nobody has seen this for a while... I will close the issue (we can re-open  
is at any time)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker