Bug 12176 - File Tabs become unresponsive
Summary: File Tabs become unresponsive
Status: RESOLVED DUPLICATE of bug 10790
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.3
Hardware: PC Windows
: --- normal
Target Milestone: 4.0.9 (from master)
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-05-09 02:28 UTC by Simon Jefferies
Modified: 2013-06-24 16:18 UTC (History)
1 user (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 10790

Description Simon Jefferies 2013-05-09 02:28:00 UTC
Open Xamarin studio, open solution, run MonoGame project to a breakpoint. Stop execution.

Notice the tabs to files that were open by the breakpoint are no longer functional.
Comment 1 Mikayla Hutchinson [MSFT] 2013-05-09 10:27:31 UTC
I would guess this is because of the broken GTK# installation discovered in bug 12175, since this issue was supposed to have been fixed by GTK# 2.12.21.
Comment 2 Mikayla Hutchinson [MSFT] 2013-05-15 17:32:12 UTC

*** This bug has been marked as a duplicate of bug 10790 ***
Comment 3 PJ 2013-06-24 16:18:53 UTC
This bug was marked as fixed for Xamarin Studio 4.0.9, which is currently in the beta channel. Try it out!