Bug 10272 - MonoDevelop does not start
Summary: MonoDevelop does not start
Status: RESOLVED DOWNSTREAM
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8.6
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-02-13 08:06 UTC by Bradford Hovinen
Modified: 2013-02-15 13:45 UTC (History)
1 user (show)

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


Attachments
Fix for bug (779 bytes, patch)
2013-02-14 05:23 UTC, Bradford Hovinen
Details


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 DOWNSTREAM

Description Bradford Hovinen 2013-02-13 08:06:20 UTC
MonoDevelop gives me the following every time I launch it:

hovinen@ubuntu:~$ monodevelop
WARNING [2013-02-13 14:03:06Z]: Inotify watch limit is too low (8192).
MonoDevelop will switch to managed file watching.
See http://monodevelop.com/Inotify_Watches_Limit for more info.
ERROR [2013-02-13 14:03:06Z]: Error while reading welcome page contents.
System.ArgumentNullException: Argument cannot be null.
Parameter name: stream
  at System.IO.StreamReader.Initialize (System.IO.Stream stream, System.Text.Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize) [0x00000] in <filename unknown>:0 
  at System.IO.StreamReader..ctor (System.IO.Stream stream, System.Text.Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize) [0x00000] in <filename unknown>:0 
  at System.IO.StreamReader..ctor (System.IO.Stream stream) [0x00000] in <filename unknown>:0 
  at (wrapper remoting-invoke-with-check) System.IO.StreamReader:.ctor (System.IO.Stream)
  at System.Xml.Linq.XDocument.Load (System.IO.Stream stream) [0x00000] in <filename unknown>:0 
  at MonoDevelop.Ide.WelcomePage.WelcomePageBranding..cctor () [0x00000] in <filename unknown>:0 
Basedir=/usr/lib/monodoc

This occurs after the small title-window appears but before the main window appears. After this it hangs and does not show a window.

This started to occur after the program while running stopped responding. I killed the process and tried to restart it. Since then it always gives me the above error. Neither logging out nor rebooting have any effect.
Comment 1 Bradford Hovinen 2013-02-14 05:23:20 UTC
Created attachment 3372 [details]
Fix for bug

On further examination, it appears that this bug has been fixed in a later version. However, upgrading to this version is not possible in my environment. Therefore, I request that this patch, which appears to fix the problem, be applied to version 2.8.6.3 and an update be released. Thank you in advanced.
Comment 2 Mikayla Hutchinson [MSFT] 2013-02-14 14:04:58 UTC
Are you sure that patch fixes the startup problem? That exception is handled, so it should be harmless.

What is your environment?
Comment 3 Bradford Hovinen 2013-02-15 06:28:44 UTC
The patch definitely fixes the problem. It is exactly the diff on that file between 3.0.6 and 2.8.6. I haven't investigated the commit-log, though.

The OS is Ubuntu 12.04 and I installed the standard Ubuntu-packages.
Comment 4 Mikayla Hutchinson [MSFT] 2013-02-15 13:45:17 UTC
I recommend you file this patch with the Ubuntu packager then, maybe they can make a hotfix release.

Upstream we are only supporting 3.x.