Bug 37472 - Xamarin Studio often gets stuck in a modal state
Summary: Xamarin Studio often gets stuck in a modal state
Status: RESOLVED DUPLICATE of bug 34250
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 5.10 (C6SR3)
Hardware: Macintosh Mac OS
: --- major
Target Milestone: master
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-01-07 05:25 UTC by bryan costanich
Modified: 2016-01-08 16:35 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED DUPLICATE of bug 34250

Description bryan costanich 2016-01-07 05:25:02 UTC
Xamarin Studio will often get stuck in a modal state where none of the menu items are accessible.

This is most often repro'd when you open up the preferences window, switch to another app, switch back to XS, close the preferences window.

Note, the version info below is because i'm using a preview version for F# support, but it also happens in 5.10, and many people see it.

=== Xamarin Studio ===

Version 6.0 (build 1752)
Installation UUID: 6be4db6f-9150-4514-8d35-ce3356a9f542
Runtime:
	Mono 4.2.1 (explicit/6dd2d0d)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 402010102

=== Xamarin.Profiler ===

Not Installed

=== Apple Developer Tools ===

Xcode 7.2 (9548)
Build 7C68

=== Xamarin.Mac ===

Version: 2.4.0.109 (Business Edition)

=== Xamarin.iOS ===

Version: 9.4.0.0 (Business Edition)
Hash: 7322991
Branch: master
Build date: 2015-12-08 16:20:29-0500

=== Xamarin.Android ===

Version: 6.0.0.34 (Business Edition)
Android SDK: /Users/bryancostanich/Library/Developer/Xamarin/android-sdk-mac_x86
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.2   (API level 17)
		4.3   (API level 18)
		4.4   (API level 19)
		5.0   (API level 21)

SDK Tools Version: 24.0.2
SDK Platform Tools Version: 21.0.0
SDK Build Tools Version: 21.1.2

Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

Version: 0.3.7
Location: /Applications/Xamarin Android Player.app

=== Build Information ===

Release ID: 600001752
Git revision: 82f4627b45b35ff833ffd6fe8dcd8601b595b0a2
Build date: 2015-11-04 11:57:18-05
Xamarin addins: 22dfcd8727ec2315920dc0c22d77470698c2b839
Build lane: monodevelop-lion-roslyn

=== Operating System ===

Mac OS X 10.11.2
Darwin BryanLePuter.local 15.2.0 Darwin Kernel Version 15.2.0
    Fri Nov 13 19:56:56 PST 2015
    root:xnu-3248.20.55~2/RELEASE_X86_64 x86_64
Comment 1 Max Xie 2016-01-07 09:36:34 UTC
The same bug comes to me, especially use the open file dialog, then click the dropdownlist to change location.
Comment 2 Frost 2016-01-07 09:49:09 UTC
The main menu is disabled since I run the NSOpenPanel or NSSavePanel and click the directory comboBox in it. 
It seems is a same problem as above description.
Comment 3 Frost 2016-01-07 09:49:59 UTC
The problem only occur on Mac OS X 10.11.2.
Comment 4 gero 2016-01-07 09:50:17 UTC
Keep on tracking this bug, suppose some body can make a solution。
Comment 5 Lluis Sanchez 2016-01-08 16:35:40 UTC

*** This bug has been marked as a duplicate of bug 34250 ***