Closed Bug 497090 Opened 16 years ago Closed 16 years ago

Camino won't minimise to dock

Categories

(Camino Graveyard :: Toolbars & Menus, defect)

Product:
Camino Graveyard
Component:
Toolbars & Menus
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: ovvldc, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.11) Gecko/2009060219 Camino/2.0b3 (like Firefox/3.0.11) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.11) Gecko/2009060219 Camino/2.0b3 (like Firefox/3.0.11) About 2/3 of the time, the yellow button on top of Camino's windows greys out. When this happens, I cannot minimise Camino into the dock. This condition comes seemingly randomly, then stays for hours on end and goes away again. It has been with me since Camino b2 at least. I am extremely annoyed by this condition, though it causes no problems other than clutter. Reproducible: Always Steps to Reproduce: 1. Browse normally for a while. 2. Check the window controls. 3.
Set to version=trunk
Version: unspecified → Trunk
I wonder if this is related to bug 461539. When this happens, can you hide Camino? Does it happen to all Camino windows simultaneously, or just individual windows? Is Window > Minimize also greyed out?
If I open a new window, that minises without problem. For the affected window, the Menu > Window> Minimise option is also greyed out. I think this is not the same as bug 461539, because hiding works just fine..
Oscar, there's nothing interesting in the Console, is there? Does it happen after you view plug-in content in a window? If you have multiple tabs in the window, does switching tabs (or creating a new tab) have any effect? (Every time I'd seen bug 461539, the menu was fine; the command just didn't work initially.)
Smokey, I hadn't thought of the console yet.. There's actually lots of stuff in my console log, but I am not sure it will help you: 09-06-09 11:33:00 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 11:33:39 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 11:35:27 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 11:45:33 com.apple.launchd[218] (0x10ae80.Locum[7041]) Exited: Terminated 09-06-09 13:42:30 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 13:42:31 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 13:54:20 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 13:57:51 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 14:54:01 [0x0-0x10010].org.mozilla.camino[250] CurrentSet updated to 8B16F418-3A6B-4D72-BAE4-641975F293C2 (Automatic) 09-06-09 14:54:09 com.apple.launchd[1] (org.samba.smbd[6120]) Stray process with PGID equal to this dead job: PID 6121 PPID 1 smbd 09-06-09 16:18:51 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:18:51 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:18:51 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:18:59 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:19:11 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:19:28 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:19:33 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:19:33 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:19:35 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:10 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:12 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:15 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:36 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:40 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:44 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:47 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:52 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:52 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:53 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:20:54 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:45:00 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:45:00 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:45:00 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 16:45:00 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 17:03:11 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called! 09-06-09 17:40:27 [0x0-0x10010].org.mozilla.camino[250] Tue Jun 9 17:40:27 c156103.chem.uu.nl Camino[250] <Error>: CGContextFlush: invalid context 09-06-09 17:43:15 [0x0-0x10010].org.mozilla.camino[250] Tue Jun 9 17:43:15 c156103.chem.uu.nl Camino[250] <Error>: CGContextFlush: invalid context 09-06-09 17:45:32 [0x0-0x10010].org.mozilla.camino[250] Debugger() was called!
All those Debugger() calls are instances of the Flash plugin loading. Do you have any idea if any of them happened around the time you first noticed the problem? It would be interesting to know if a fresh profile (using Troubleshoot Camino, or other means) fixes the problem, too. I wonder if maybe something screwy in the app plist could cause this.
Oscar, are you still seeing this periodically? If so, are you getting the same messages in the console (aside from the Debugger() spam from Flash)? I have no idea what 09-06-09 14:54:01 [0x0-0x10010].org.mozilla.camino[250] CurrentSet updated to 8B16F418-3A6B-4D72-BAE4-641975F293C2 (Automatic) is, but 09-06-09 17:40:27 [0x0-0x10010].org.mozilla.camino[250] Tue Jun 9 17:40:27 c156103.chem.uu.nl Camino[250] <Error>: CGContextFlush: invalid context could possibly be Gecko and the OS getting confused.
I'm still seeing this on occasion, but I haven't had the spare attention to investigate further. However, nearly all of it seems to be debugger() spam. I do have two CurrentSet messages from yesterday in my log, that roughly correspond with moments when I couldn't minimise. So I suppose those are linked, but still not sure. I'll get back on this when I have spare cycles. Best wishes, Oscar
Any news on this, Oscar? (I wonder if this is like bug 432983; that is, we're somehow getting confused with the plugin window? I know that sounds insane.)
I still see the inability to minimise. It usually happens when I get more tabs out (not neccessarily with Flash). Something like 20. I haven't tried a new profile yet. Sorry.
Well, it seems to have gone away since I updated to Snow Leopard. Before that I still had it regularly. I will let you know if it happens again.
OK; in the meantime, let's close this, but if you see it again, feel free to reopen.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.