So, three bugs with Deadline Monitor on linux.
Some baseline info:
Deadline 5 beta 1
Linux (Fedora 13, 64 bit)
Mono:
Mono JIT compiler version 2.6.4 (tarball Mon Jun 21 19:26:21 UTC 2010)
Copyright © 2002-2010 Novell, Inc and Contributors. mono-project.com
TLS: __thread
GC: Included Boehm (with typed GC and Parallel Mark)
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Display Driver: nvidia 260.19.29
Number of monitors: 2 (2x 1920x1200)
Desktop Environment: Gnome
Bug #1: Monitor fails to quit if quit from ‘File’->‘Exit’. The main window goes away, but it silently hangs after that. If I quit by clicking the close window ‘x’ button, Monitor exits all the way.
Repeatability on my end: Every time.
Bug #2: Launching Monitor causes a strange blank white ‘window’/rectangle that appears underneath the splash screen, right after the splash screen goes away. Refresh draw events don’t seem to occur on this rectangle, as windows/etc that are dragged over that region leave a ‘trail’. It behaves as though it’s a window that’s under the main Monitor window in terms of how it behaves in desktop environment focus.
Repeatability on my end: Seems to only happen if I leave the mouse still and don’t click anywhere while Monitor is starting and the splash screen is up.
Bug #3: Tooltip boxes stay visible as ‘always on top’ if focus is taken away from Monitor while they’re up, and stay on top of other non-Monitor windows.
Repeatability on my end: Annoyingly random. I can’t get this one to reliably happen. I put it at about ~50% of the times when I intentionally tried to get it to happen.
Cheers!
-Matt
Hey Matt,
We’ll have to set up a Fedora 13 VM to test this out. I’m downloading the ISO right now.
I don’t recall any of this behavior with Fedora 12 (the last version of Fedora we tested against), but I will try this as well.
I should note that Deadline 5.0 will list Mono 2.6.7 as its requirement, so it might be worth trying to upgrade to that version if possible.
Cheers,
Will do. Mono 2.6.4 is the version that’s in the Fedora repository. I’ll add the novell mono repository to our machines and upgrade to 2.6.4.
Cheers!
-Matt
I think Fedora’s development repository (rawhide) also has the 2.6.7 version.
Just upgraded to mono 2.6.7, and the bugs are still present.
I didn’t see 2.6.7 in the rawhide repos, so I just added right from novell.
Mono info:
Mono JIT compiler version 2.6.7 (tarball Mon Jul 19 18:28:58 UTC 2010)
Copyright © 2002-2010 Novell, Inc and Contributors. www.mono-project.com
TLS: __thread
GC: Included Boehm (with typed GC and Parallel Mark)
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Cheers!
-Matt
Hey Matt,
Thanks for the update. We’re still trying to get a Fedora 13 VM set up here, but we’re having all sorts of problems. The Live CD image won’t boot, so we tried a network install. The install seemed to go fine, but now Fedora just hangs while booting up. Hopefully we’ll get this figured out soon.
Cheers,
Update!
So we gave up with the 64 bit version of Fedora 13. No matter what we tried, it would either run painfully slow or not boot up at all. So we installed the 32 bit version, and it appears to be running fine. We should have a chance to install Mono and Deadline next week and start doing some tests.
Cheers,
Alright, the 32-bit version of Fedora 13 is running nicely and we installed Mono 2.6.7 and Deadline. I was able to reproduce all three problems you listed.
-
From the tests we’ve run, this only seems to occur on Fedora 13. It doesn’t happen on openSuse, or on Windows and OSX. It only affects the Monitor, as none of the other applications seem to have this problem. We haven’t traced the root of the problem yet, but being able to reproduce it is a good start!
-
I was actually able to reproduce this on openSuse and Fedora. I never noticed on openSuse, because it seems to appear behind the splash screen and the Monitor. When I minimized everything, there it was. This is actually a dummy window that acts as a parent to the splash screen, and even though we set its visibility to False, it was still appearing. We’re a little more explicit now on how how we control its visibility, and that seems to have fixed the problem. So the fix for this will be rolled out in beta 3.
-
I had no problem reproducing by making the tool tip visible and then using Alt+Tab to give focus to another window. However, I’m not sure what we can do about it, since the tooltips are controlled by Mono. I did find that if I moved the mouse over the tooltip again, it disappeared (even though it was in front of the new window that had focus). So while I guess this is a bit annoying, we won’t look into finding a workaround for this since it’s not going to come up often, and when it does, the impact is pretty minimal.
Cheers,
Oh, forgot to ask a question regarding (1). Do you know if this is a regression? In other words, did you ever see this problem with 4.1?
Cheers,
I don’t remember having this problem with bug #1 before with 4.1, so it may indeed be a regression. However, I usually close Monitor with the ‘Close Window’ button, and this only came to my attention recently when someone couldn’t start Monitor (since it was still zombified from the previous closing).
Cheers!
-Matt
Bug #1 should also be fixed in beta release 3. We tweaked our “exit” code a bit on the Monitor, and the problem no longer occurs on our Fedora 13 installation. It wasn’t like we were doing anything complicated, so I still don’t fully understand why it wasn’t working in the first place. Oh well…