|
Fri 06 Jul 2007 10:52:15 AM UTC, comment #14:
I move this bug from Fixed to Confirmed again since David observes it now.
May be we should rename with a better Summary?
|
Thu 28 Jun 2007 02:48:09 AM UTC, comment #13:
It is reported that this bug disappears in recent revision.
I mark it fixed and will close it later if there is no further information.
|
Tue 08 May 2007 09:34:33 AM UTC, comment #12:
I have been able to reproduce the freeze bug with r598 too.
Let me know about any other informations you need.
|
Mon 07 May 2007 09:05:37 PM UTC, comment #11:
Thanx for this information.
Now, the earliest version you can find is this:
branches/AzaleaBox/Azalea r598.
It is not in svn anymore, but can be retrieved using revision.
So anything between r598 to r666 is there.
Maybe you can try r598 first and see.
Thank you for all the trouble to test each revision.
|
Mon 07 May 2007 08:34:09 PM UTC, comment #10:
Thanks for feedback.
For some reasons I checked out the wrong revision and thought it was the right one because I read OpenBox in the contextual menu window.
After checking out the right copy (verified it with svn info and a log statement in openbox.m), well I have to report that I have observed the freeze bug with Azalea r666 too.
Should I try to reproduce the bug with more recent versions?
|
Thu 03 May 2007 04:34:52 PM UTC, comment #9:
r666 is the earliest version of Azalea. If it has the same bug, then it is inherited from OpenBox3, which is not going to be easy to fix.
The error "Internal Error: t1 or t2 should not be CurrentTime" only exists in the most recent revision, probably around r1600. So you should not be able to see it in r666. If so, you probably not really use r666.
So here is the question I have, are you sure you are using the r666 revision ? You can insert a NSLog in openbox.m to be sure you are using the right version.
If it is a window mapping issue, it is probably a bug around AZClientManager. But again, I cannot reproduce it to fix it.
|
Thu 03 May 2007 12:58:04 PM UTC, comment #8:
I tried several recent versions of Azalea in -trunk over the last month and always encountered the same issue. I haven't tried -stable though.
As you suggested in a recent mail, I tried with -r666 version of Azalea. I stumbled on the same problem. It now reminds me I always had this sort of crash with Azalea but never reported them. With -r666, it even crashed one or two times on the first xterm window created with Azalea contextual menu (displayed by right-click).
I spend an hour today trying to find some kind of patterns without success. The only new fact I have isolated is you can freeze Azalea by just creating and closing windows (no need to move them or click the title bar). After creating and closing 5, 15, 20 xterm emulator I usually get a freeze. When it happens, the normal arrow cursor is present so I would now say it's unrelated to cursor handling or display.
By creating, moving and closing windows a lot, it seems you can always get this freeze in the first 3 minutes of use.
By running Azalea from a failsafe terminal session, I observe no logging output on freeze. However on each window creation, Azalea logs two times: "Internal Error: t1 or t2 should not be CurrentTime". The timestamp of both logging statements is either the same time or separated by a small amount of time (precisely 1 millisecond).
Hope it helps a bit…
|
Sat 28 Apr 2007 07:19:42 PM UTC, comment #7:
Which version of Azalea do you use ?
The one in -stable or the one in -trunk ?
The information is not enough to figure out where could be the problem.
I would say it is probably a memory leak somewhere inside.
But I cannot reproduce the problem since every version of Azalea works for me.
If it happens to you every time,
maybe you can start with xterm, then manually start with Azalea
and see whether you can reproduce the problem.
It will be much easy for debugging.
Thanx.
Yen-Ju
|
Sat 28 Apr 2007 06:48:00 PM UTC, comment #6:
Sorry to be late to give you further infos.
I have observed this bug when running Azalea alone (iirc it happened each time I ran it), but not yet with OpenBox… OpenBox seems to run without issues, I will let you know if it finally happens with it too.
Most of time I get the crash, I have some sort of cursor (hand, resize etc.) displayed which isn't the normal arrow cursor. However I'm really not sure this is always true when I get the crash.
|
Thu 22 Mar 2007 05:47:42 PM UTC, comment #5:
So my question is whether it also happens when you run Azalea alone, not any other Etoile components ?
You can run it under Gnome and replace the metacity with Azalea as I suggested.
If it happens, can you run Openbox3 and see whether it has the same problem ?
I try to figure out whether it is caused by communication between Etoile components or by X protocols.
Running Azalea alone will help to nail down the problem.
|
Thu 22 Mar 2007 05:29:54 PM UTC, comment #4:
By Etoile, I mean the usual setup you get 'make install' and './setup.sh'… At the time of my bug report: System + Azalea + MenuServer
I have no Window Manager already running when I log in.
What I can add now is that it also happens when the hand cursor isn't used (usual arrow cursor visible).
The problem is the one you describe. Most of the time I cannot even kill the current X session, I have to reboot. On my set up it happens all the time after I have run Etoile between 3 or 10 minutes. We observed the same issue at Fosdem with the livecd, it just froze very often.
At this time, I'm unable to isolate a pattern, it seems to occur in a fully random manner. I still hope to find a pattern.
iirc I have observed this issue since December or probably before with any GNUstep repository versions (ditto for Etoile version used).
|
Tue 20 Mar 2007 08:13:45 PM UTC, comment #3:
I just had a freeze during reinstalling GNUstep and Etoile while Azalea is still running. It is so bad that even switching back to metacity cannot recover and I have to reboot from command-line. But after a reboot, everything work fine. So I guess the problems may root from version and linking issue.
|
Tue 20 Mar 2007 04:24:13 AM UTC, comment #2:
Now I notice the hand cursor. It is from Azalea.
But it never freeze after long time use for me.
|
Mon 19 Mar 2007 05:15:29 PM UTC, comment #1:
When you said "Etoile", which components did you exactly run ?
Azalea only or System + Azalea ?
If it is possible, run Azalea only (not System) and see.
If it is still freeze, run Openbox3 only and see.
If Azalea work fine, run AZDock only (not System) .
These are two components I can think about.
If you already have a EWMH window manager running when you log in,
run `openapp Azalea --replace &` to replace that WM with Azalea.
By the way, I don't remember the "hand" cursor.
Do you let GNUstep draw window decoration or Azalea ?
I never let GNUstep draw window decoration
and it is never tested with Azalea.
|
Mon 19 Mar 2007 10:03:44 AM UTC, original submission:
When I use Étoilé, usually after 3 or 5 minutes of use, I get a total freeze. At this point no interaction is possible and the cursor seems to be stuck in displaying the hand picture (the one appearing when you move a window by clicking on its content with control key pushed).
I think the bug arises when I click on a title bar. It's usually happen after 3 or 5 minutes of use.
To escape the freeze, I can still kill the X session to return to the login panel.
|
Related Recipes:
Étoilé - Bugs: bug #8752, Random freeze with hand cursor