openSUSE Forums > Archives > Novell Archives » MonoDevelop 0.11 fails to start on SuSE 10.1

Go Back   openSUSE Forums > Archives > Novell Archives
Forums FAQ Members List Search Today's Posts Mark Forums Read


Novell Archives Archived content from Novell openSUSE support forums

 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 24-May-2006, 08:59
mainsoft
Guest
 
Posts: n/a
Default MonoDevelop 0.11 fails to start on SuSE 10.1

Hi,

I have just installed MonoDevelop 0.11 on SuSE 10.1 and I get the following
error upon startup:

System.Runtime.Remoting.RemotingException: Unix transport error.

Server stack trace:
in <0x0008f> Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveM essageStatus
(System.IO.Stream networkStream, System.Byte[] buffer)
in <0x0017c>
Mono.Remoting.Channels.Unix.UnixClientTransportSin krocessMessage (IMessage
msg, ITransportHeaders requestHeaders, System.IO.Stream requestStream,
ITransportHeaders responseHeaders, System.IO.Stream responseStream)
in <0x0024c>
Mono.Remoting.Channels.Unix.UnixBinaryClientFormat terSink:SyncProcessMessage
(IMessage msg)

Exception rethrown at [0]:
---> System.Runtime.Remoting.RemotingException: Connection closed
in <0x0006c> Mono.Remoting.Channels.Unix.UnixMessageIO:StreamRe ad
(System.IO.Stream networkStream, System.Byte[] buffer, Int32 count)
in <0x00044> Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveM essageStatus
(System.IO.Stream networkStream, System.Byte[] buffer)--- End of inner
exception stack trace ---

in <0x0008f> Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveM essageStatus
(System.IO.Stream networkStream, System.Byte[] buffer)
in <0x0017c>
Mono.Remoting.Channels.Unix.UnixClientTransportSin krocessMessage (IMessage
msg, ITransportHeaders requestHeaders, System.IO.Stream requestStream,
ITransportHeaders responseHeaders, System.IO.Stream responseStream)
in <0x0024c>
Mono.Remoting.Channels.Unix.UnixBinaryClientFormat terSink:SyncProcessMessage
(IMessage msg)

Version 0.9 worked fine. Any idea? Any missing package? I have mono-core
1.1.13.

I'm wondering why the IDE needs to call into the Remoting classes upon
startup.

Thanks.

--
Patrick Philippot


  #2 (permalink)  
Old 24-May-2006, 09:03
Justin Grote [SysOp]
Guest
 
Posts: n/a
Default Re: MonoDevelop 0.11 fails to start on SuSE 10.1

mainsoft wrote:
> Version 0.9 worked fine. Any idea? Any missing package? I have mono-core
> 1.1.13.


Where did you get .9 from? AFAIK only .7 comes with SuSE 10.1.

--
Justin Grote
Novell Support Connection Sysop
Network Architect
JWG Networks
  #3 (permalink)  
Old 24-May-2006, 10:38
mainsoft
Guest
 
Posts: n/a
Default Re: MonoDevelop 0.11 fails to start on SuSE 10.1

> Where did you get .9 from? AFAIK only .7 comes with SuSE 10.1.

I did a fresh FTP install of SuSE Linux 101.1 and it came with MonoDevelop
0.9-33

--
Patrick Philippot

"Justin Grote [SysOp]" <jgrote@jwgnetworks.com> wrote in message
news:wIZcg.2937$Mr.672@prv-forum2.provo.novell.com...
> mainsoft wrote:
>> Version 0.9 worked fine. Any idea? Any missing package? I have mono-core
>> 1.1.13.

>
> Where did you get .9 from? AFAIK only .7 comes with SuSE 10.1.
>
> --
> Justin Grote
> Novell Support Connection Sysop
> Network Architect
> JWG Networks



  #4 (permalink)  
Old 24-May-2006, 11:51
Justin Grote [SysOp]
Guest
 
Posts: n/a
Default Re: MonoDevelop 0.11 fails to start on SuSE 10.1

mainsoft wrote:
>> Where did you get .9 from? AFAIK only .7 comes with SuSE 10.1.

>
> I did a fresh FTP install of SuSE Linux 101.1 and it came with MonoDevelop
> 0.9-33


Err, oops, two monodevelop threads going on today. I meant to ask where
you got .11, afaik only .9 comes with 10.1


--
Justin Grote
Novell Support Connection Sysop
Network Architect
JWG Networks
  #5 (permalink)  
Old 25-May-2006, 03:24
mainsoft
Guest
 
Posts: n/a
Default Re: MonoDevelop 0.11 fails to start on SuSE 10.1

>I meant to ask where you got .11, afaik only .9 comes with 10.1

On the Mono Project site: http://www.go-mono.com/download/suse-100-i586/ ,
this link:

http://www.go-mono.com/download/noar...ell.noarch.rpm

By the way, version 0.11 is supposed to add some support for the version 2.0
of the framework but AFAIK, version 2.0 still doesn't exist.

--
Patrick Philippot


"Justin Grote [SysOp]" <jgrote@jwgnetworks.com> wrote in message
news:qa0dg.3113$Mr.1149@prv-forum2.provo.novell.com...
> mainsoft wrote:
>>> Where did you get .9 from? AFAIK only .7 comes with SuSE 10.1.

>>
>> I did a fresh FTP install of SuSE Linux 101.1 and it came with
>> MonoDevelop 0.9-33

>
> Err, oops, two monodevelop threads going on today. I meant to ask where
> you got .11, afaik only .9 comes with 10.1
>
>
> --
> Justin Grote
> Novell Support Connection Sysop
> Network Architect
> JWG Networks



  #6 (permalink)  
Old 29-May-2006, 10:38
mainsoft
Guest
 
Posts: n/a
Default [Solution] Re: MonoDevelop 0.11 fails to start on SuSE 10.1

Hi,

The solution to this problem is to uninstall MonoDevelop and Mono, install
the latest version of Mono (1.1.15), re-install MonoDevelop 0.11 and start
MonoDevelop with the --ipc-tcp option.

--
Patrick Philippot
MainSoft Consulting Services
www.mainsoft.fr


"mainsoft" <patrick.philippot@mainsoft..xx.fr> wrote in message
news:VEZcg.2928$Mr.2544@prv-forum2.provo.novell.com...
> Hi,
>
> I have just installed MonoDevelop 0.11 on SuSE 10.1 and I get the
> following error upon startup:
>
> System.Runtime.Remoting.RemotingException: Unix transport error.
>
> Server stack trace:
> in <0x0008f>
> Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveM essageStatus
> (System.IO.Stream networkStream, System.Byte[] buffer)
> in <0x0017c>
> Mono.Remoting.Channels.Unix.UnixClientTransportSin krocessMessage
> (IMessage msg, ITransportHeaders requestHeaders, System.IO.Stream
> requestStream, ITransportHeaders responseHeaders, System.IO.Stream
> responseStream)
> in <0x0024c>
> Mono.Remoting.Channels.Unix.UnixBinaryClientFormat terSink:SyncProcessMessage
> (IMessage msg)
>
> Exception rethrown at [0]:
> ---> System.Runtime.Remoting.RemotingException: Connection closed
> in <0x0006c> Mono.Remoting.Channels.Unix.UnixMessageIO:StreamRe ad
> (System.IO.Stream networkStream, System.Byte[] buffer, Int32 count)
> in <0x00044>
> Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveM essageStatus
> (System.IO.Stream networkStream, System.Byte[] buffer)--- End of inner
> exception stack trace ---
>
> in <0x0008f>
> Mono.Remoting.Channels.Unix.UnixMessageIO:ReceiveM essageStatus
> (System.IO.Stream networkStream, System.Byte[] buffer)
> in <0x0017c>
> Mono.Remoting.Channels.Unix.UnixClientTransportSin krocessMessage
> (IMessage msg, ITransportHeaders requestHeaders, System.IO.Stream
> requestStream, ITransportHeaders responseHeaders, System.IO.Stream
> responseStream)
> in <0x0024c>
> Mono.Remoting.Channels.Unix.UnixBinaryClientFormat terSink:SyncProcessMessage
> (IMessage msg)
>
> Version 0.9 worked fine. Any idea? Any missing package? I have mono-core
> 1.1.13.
>
> I'm wondering why the IDE needs to call into the Remoting classes upon
> startup.
>
> Thanks.
>
> --
> Patrick Philippot
>



 

Bookmarks


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2