I don't know if we can update to md5 i will ask eventually if any earlier versions don't solve this issue.

an workaround who solve the problem an half, is to start MD go to addin manager and disable all Subversion modules, then i was able to open project, but still another stack strace from gdb/console.
Most important is, i use SVN addin to manage my project on sourceforge.net

I released on testing 4.0.14-5 that should fix the problem.
As soon as build system has finish you can test it.

Thanks Angelo for your work!

Eric please test them by enabling update/testing repo and disable it later.

i have a biggest issue from the moment :D
i had format my secondary swap and get an blocking boot error about dracut and resume device.
I will see that after

ok, i have enabled the repo core update testing, i have now the MD 4.0.14 not the 4.0.14-5.
with subervsion activated, the project was open fine, (no yet tested and use SVN on one of my project).
i continuous to have an stackstrace, but perhaps it come from my project who use old GTK2-C# library.
thanks

I have uploaded monodevelop monodevelop-debugger-gdb and monodevelop-database packages for Mageia 4.

You can test this issue by having a monodevelop project released to svn, it does 
not matter having the repository reachable. With the old version monodevelop
crashes after project selection (on opening), with the new one it does not.


Suggested advisory:
========================

Updated monodevelop packages fix a crash opening projects working with svn.

========================

Updated packages in core/updates_testing:
========================
monodevelop-4.0.14-1.mga4.noarch.rpm                
monodevelop-database-4.0.14-1.mga4.noarch.rpm       
monodevelop-database-devel-4.0.14-1.mga4.noarch.rpm 
monodevelop-debugger-gdb-4.0.14-1.mga4.noarch.rpm  

Source RPMs: 
monodevelop-4.0.14-1.mga4.src.rpm 
monodevelop-database-4.0.14-1.mga4.src.rpm
monodevelop-debugger-gdb-4.0.14-1.mga4.src.rpm

yes it is right, we can change bug severity from critical to minor.

(In reply to Eric Petit from comment #9)
> yes it is right, we can change bug severity from critical to minor.


monodevelop from updates_testing has fixed the crash on your 64 bits system, correct?

And you're saying the severity can change from critical to minor, because whoever suffers from those crashes can now download a good MD from updates_testing?

CC: (none) => marja11

yes that fix the crash, but stack straces still here.

I don't have any stack trace here...
please upload it maybe it could be useful to understand, and maybe evaluate to
use the higher version, if compatible with the system

ti see them yu need to add the --no-redirect arguments( see monodevelop --help)

http://pastebin.com/ybTEF9Pk

when i tried to run this old app, i got an error message, google give the answer, it was an mono RT version problem, i added mono=4 like that
exec mono --runtime=v4.0  "/usr/lib/rebootinfe/RebootInFE.exe" "$@"
to solve the problem
Also, i have old GTK 2 reference, perhaps it could be the badboy

i have stack trace for every thing at that point...
anyway from your attachment i can see:
MonoDevelop.VersionControl.Subversion.SubversionException: The working copy at '/home/eric/Projects/RebootInFE'
is too old (format 10) to work with client version '1.8.8 (r1568071)' (expects format 31). You need to upgrade the working copy first.
as suggested go at /home/eric/Projects/RebootInFE and give the following command:
svn upgrade

btw i also saw such a message, but in a dialog before monodevelop self closure

yes, my svn format is old, but it is only an warning, not a stack straces of MD, at this point MD is runing.

You don't have to reduce the level of this bug. because who has mga4 has a
crash. What i don't understand is what kind of trace you have.
if i enable that option in md (--no-redirect) i got stack traces for every action
i do even create a new project.but i can work and the project run.
The svn must be upgraded otherwhise from your client (not only the monodevelop
one) you won't be able to update or work on your copy.

If you have another problem (the trace, please let me know which is the problem
provide the "offending project" and i would try to fix it) but open another bug.
I can open svn projects now, i can diff them (i haven't tested ci/co because
i don't have the access), but as far as i can say it works.

For QA team, if this bug is too long to follow, once we can say it's fixed i will
open a new one with the advisory text and reference if you prefer to.

CC: (none) => matteo.pasotti
Severity: minor => critical

hmm and it seems not to be a warning:
ERROR [2014-07-18 21:06:08Z]: MonoDevelop.VersionControl.Subversion.SubversionException: The working copy at '/home/eric/Projects/RebootInFE'
is too old (format 10) to work with client version '1.8.8 (r1568071)' (expects format 31). You need to upgrade the working copy first.
 
  at MonoDevelop.VersionControl.Subversion.Unix.SvnClient.CheckError (IntPtr error, Nullable`1 allowedError) [0x000aa] in /home/iurt...

Testing MGA4-64

I've installed MonoDevelop monodevelop-4.0.12-2.mga4 and created a new project. When adding an svn repo it crashed when I clicked ok. I did not have a previous project I could open which had an svn within it though adding a new repo seems to cause the same crash.

Upgraded to monodevelop-4.0.14-1.mga4 and tried the same test with no error.

In comment #3 it is mentioned 4.0.14-5, unsure if this is a typo as only 4.0.14-1 exists. I also could not reproduce the stack traces from comment #11.

ok angello, as we say (for me) the svn crash is "fixed" with the 4.0.14 version.
the option is :
MonoDevelop 4.0.14
Options:
      --no-splash            Do not display splash screen.
      --ipc-tcp              Use the Tcp channel for inter-process
                               comunication.
      --new-window           Do not open in an existing instance of MonoDevelop
  -h, -?, --help             Show help
      --perf-log             Enable performance counter logging
      --no-redirect          Disable redirection of stdout/stderr to a log file
[eric@localhost ~]$ 
 i will try an svn CO

ok, did svn upgrade :
http://pastebin.com/b7UkBeke
all the Stack traces turn around GTK/GTK#, all i saw on the web is an version problem between gtk 1,2 and 3 and mono/net 1,2,3 et 4
WARNING [2014-07-19 00:10:37Z]: GLib-GObject-Warning: Attempt to add property __gtksharp_55_MonoDevelop_Ide_Gui_Components_ZoomableCellRendererPixbuf::image after class was initialised
Stack trace: 
   at GLib.Object.gtksharp_register_property(IntPtr , IntPtr , IntPtr , IntPtr , UInt32 , IntPtr , Boolean , Boolean )
   at GLib.Object.AddProperties(GType gtype, System.Type t)
   at GLib.Object.RegisterGType(System.Type t)
   at GLib.Object.LookupGType(System.Type t)
   at GLib.Object.LookupGType()
   at GLib.Object.CreateNativeObject(System.String[] names, GLib.Value[] vals)
   at Gtk.Object.CreateNativeObject(System.String[] names, GLib.Value[] vals)
   at Gtk.CellRendererPixbuf..ctor()
   at MonoDevelop.Ide.Gui.Components.ZoomableCellRendererPixbuf..ctor() in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui.Components/ExtensibleTreeView.cs:line 2488
   at MonoDevelop.Ide.Gui.Components.ExtensibleTreeView.Initialize(MonoDevelop.Ide.Gui.Components.NodeBuilder[] builders, MonoDevelop.Ide.Gui.Components.TreePadOption[] options, System.String contextMenuPath) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui.Components/ExtensibleTreeView.cs:line 175
   at MonoDevelop.Ide.Gui.Pads.TreeViewPad.Initialize(MonoDevelop.Ide.Gui.Components.NodeBuilder[] builders, MonoDevelop.Ide.Gui.Components.TreePadOption[] options, System.String contextMenuPath) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui.Pads/TreeViewPad.cs:line 91
   at MonoDevelop.Ide.Gui.Pads.SolutionPad.Initialize(MonoDevelop.Ide.Gui.Components.NodeBuilder[] builders, MonoDevelop.Ide.Gui.Components.TreePadOption[] options, System.String contextMenuPath)
   at MonoDevelop.Ide.Gui.Pads.ProjectPad.ProjectSolutionPad.Initialize(MonoDevelop.Ide.Gui.Components.NodeBuilder[] builders, MonoDevelop.Ide.Gui.Components.TreePadOption[] options, System.String contextMenuPath) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui.Pads.ProjectPad/ProjectSolutionPad.cs:line 47
   at MonoDevelop.Ide.Codons.SolutionPadCodon.<CreatePad>m__48() in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Codons/SolutionPadCodon.cs:line 92
   at MonoDevelop.Ide.Gui.Pads.TreeViewPad.Initialize(IPadWindow container) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui.Pads/TreeViewPad.cs:line 70
   at MonoDevelop.Ide.Codons.PadCodon.InitializePadContent(IPadWindow window) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Codons/PadCodon.cs:line 92
   at MonoDevelop.Ide.Gui.DefaultWorkbench.CreatePadContent(Boolean force, MonoDevelop.Ide.Codons.PadCodon padCodon, MonoDevelop.Ide.Gui.PadWindow window, MonoDevelop.Components.Docking.DockItem item) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui/DefaultWorkbench.cs:line 1273
   at MonoDevelop.Ide.Gui.DefaultWorkbench+<AddPad>c__AnonStorey43.<>m__40(System.Object , System.EventArgs ) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui/DefaultWorkbench.cs:line 1330
   at MonoDevelop.Components.Docking.DockItem.SetupContent(System.Object ob, System.EventArgs args) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Components.Docking/DockItem.cs:line 195
   at System.Reflection.MonoMethod.InternalInvoke(System.Reflection.MonoMethod , System.Object , System.Object[] , System.Exception ByRef )
   at System.Reflection.MonoMethod.Invoke(System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) in /home/iurt/rpmbuild/BUILD/mono-3.2.3/mcs/class/corlib/System.Reflection/MonoMethod.cs:line 230
   at System.Reflection.MethodBase.Invoke(System.Object obj, System.Object[] parameters) in /home/iurt/rpmbuild/BUILD/mono-3.2.3/mcs/class/corlib/System.Reflection/MethodBase.cs:line 114
   at System.Delegate.DynamicInvokeImpl(System.Object[] args) in /home/iurt/rpmbuild/BUILD/mono-3.2.3/mcs/class/corlib/System/Delegate.cs:line 424
   at System.MulticastDelegate.DynamicInvokeImpl(System.Object[] args) in /home/iurt/rpmbuild/BUILD/mono-3.2.3/mcs/class/corlib/System/MulticastDelegate.cs:line 72
   at System.Delegate.DynamicInvoke(System.Object[] args) in /home/iurt/rpmbuild/BUILD/mono-3.2.3/mcs/class/corlib/System/Delegate.cs:line 398
   at GLib.Signal.ClosureInvokedCB(System.Object o, GLib.ClosureInvokedArgs args)
   at GLib.SignalClosure.Invoke(GLib.ClosureInvokedArgs args)
   at GLib.SignalClosure.MarshalCallback(IntPtr raw_closure, IntPtr return_val, UInt32 n_param_vals, IntPtr param_values, IntPtr invocation_hint, IntPtr marshal_data)
   at Gtk.Widget.gtk_widget_show(IntPtr )
   at Gtk.Widget.Show()
   at MonoDevelop.Components.Docking.DockGroup.SizeAllocate(Rectangle newAlloc) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Components.Docking/DockGroup.cs:line 365
   at MonoDevelop.Components.Docking.DockGroup.SizeAllocate(Rectangle newAlloc) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Components.Docking/DockGroup.cs:line 470
   at MonoDevelop.Components.Docking.DockLayout.SizeAllocate(Rectangle rect) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Components.Docking/DockLayout.cs:line 90
   at MonoDevelop.Components.Docking.DockContainer.OnSizeAllocated(Rectangle rect) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Components.Docking/DockContainer.cs:line 149
   at Gtk.Widget.sizeallocated_cb(IntPtr widget, IntPtr allocation)
   at Gtk.Widget.gtksharp_widget_base_size_allocate(IntPtr , IntPtr )
   at Gtk.Widget.OnSizeAllocated(Rectangle allocation)
   at MonoDevelop.Components.Docking.DockFrame.OnSizeAllocated(Rectangle allocation) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Components.Docking/DockFrame.cs:line 975
   at Gtk.Widget.sizeallocated_cb(IntPtr widget, IntPtr allocation)
   at Gtk.Widget.gtksharp_widget_base_size_allocate(IntPtr , IntPtr )
   at Gtk.Widget.OnSizeAllocated(Rectangle allocation)
   at MonoDevelop.Ide.Gui.WorkbenchWindow.OnSizeAllocated(Rectangle allocation) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide.Gui/WorkbenchWindow.cs:line 115
   at Gtk.Widget.sizeallocated_cb(IntPtr widget, IntPtr allocation)
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at MonoDevelop.Ide.IdeApp.Run() in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide/Ide.cs:line 387
   at MonoDevelop.Ide.IdeStartup.Run(MonoDevelop.Ide.MonoDevelopOptions options) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide/IdeStartup.cs:line 291
   at MonoDevelop.Ide.IdeStartup.Main(System.String[] args) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Ide/MonoDevelop.Ide/IdeStartup.cs:line 538
   at MonoDevelop.Startup.MonoDevelopMain.Main(System.String[] args) in /home/iurt/rpmbuild/BUILD/monodevelop-4.0.14/src/core/MonoDevelop.Startup/MonoDevelop.Startup/MonoDevelopMain.cs:line 17
WARNING [2014-07-19 00:10:37Z]: GLib-GObject-Warning: Attempt to add property __gtksharp_55_MonoDevelop_Ide_Gui_Components_ZoomableCellRendererPixbuf::image-expander-open after class was initialised
Stack trace:

here you have only warnings now... does that prevent to use monodevelop?
I could try newer version, (from 4.1 or 4.2) but i don't know if they add new
features and regressions...

@David comment #19 the source tarball is 4.0.14-5 that is last
4.0.x released[1]. If this version has problems i can tr to build 4.1 or 4.2
as said.

But sorry if i'm back on this subject, is the trace a problem? and in
the case should it be related to this bug?

[1] http://download.mono-project.com/sources/monodevelop/

(In reply to Angelo Naselli from comment #22)
> here you have only warnings now... does that prevent to use monodevelop?
> I could try newer version, (from 4.1 or 4.2) but i don't know if they add new
> features and regressions...
> 
> @David comment #19 the source tarball is 4.0.14-5 that is last
> 4.0.x released[1]. If this version has problems i can tr to build 4.1 or 4.2
> as said.
> 
> But sorry if i'm back on this subject, is the trace a problem? and in
> the case should it be related to this bug?
> 
> [1] http://download.mono-project.com/sources/monodevelop/

At this point(just open an project) it isn' t an problem.
I use #monodevelop irc Chanel, what md team an user say is: in md v 5.xx most of bug and problems was solved

Sorry i use my (french) phone.
***team AND users

:) developers and co. always push for the last release :)
what we need to understand if what you see is a "real" issue or just little
problem, and in any case identify the problems to see if there are fixings.
You could also try to explain the problem you see with someone in french 
by using our irc/mails, just asking to report that to me... to skip 
language problems...

monodevelop is a leaf package, if the one released is good enough to maintain
i propose to open a new bug for a backport of the 5.0.1 version so that you can use the last one. I will provide it in the case.

btw with --no-redirect md 5.0.1 writes a lot of stack traces as well...

:)

Eric, this is Ok for you now mga4 64bit?

with this specific version provided, it's seem okay, it run

Thanks, and David's previous test too, adding mga4 64 ok

Just repeating comment 8 for ease of reference

---------------------------------------------------------
I have uploaded monodevelop monodevelop-debugger-gdb and monodevelop-database packages for Mageia 4.

You can test this issue by having a monodevelop project released to svn, it does 
not matter having the repository reachable. With the old version monodevelop
crashes after project selection (on opening), with the new one it does not.


Suggested advisory:
========================

Updated monodevelop packages fix a crash opening projects working with svn.

========================

Updated packages in core/updates_testing:
========================
monodevelop-4.0.14-1.mga4.noarch.rpm                
monodevelop-database-4.0.14-1.mga4.noarch.rpm       
monodevelop-database-devel-4.0.14-1.mga4.noarch.rpm 
monodevelop-debugger-gdb-4.0.14-1.mga4.noarch.rpm  

Source RPMs: 
monodevelop-4.0.14-1.mga4.src.rpm 
monodevelop-database-4.0.14-1.mga4.src.rpm
monodevelop-debugger-gdb-4.0.14-1.mga4.src.rpm
-----------------------------------------------------------

Whiteboard: (none) => mga4-64-ok

Testing complete mga4 32

Before
------
After starting monodevelop, in the Version Control menu, selected Checkout and entered a random url as the Url. eg. svn://mageia.org Clicked OK and it crashed.

After
-----
It now shows an expected error that it is unable to connect to the repository.

I don't have a real one to connect it to but as it's been confirmed to be working this is enough to show it trying.

Whiteboard: has_procedure mga4-64-ok => has_procedure mga4-32-ok mga4-64-ok

Using mageia svn (duh!) it does work :)

Url: svn://svn.mageia.org/svn/packages

It starts to download the svn repo, so cancelled the operation.

Validating. Advisory uploaded.

Could sysadmin please push to 4 updates

Thanks

Keywords: (none) => validated_update
Whiteboard: has_procedure mga4-32-ok mga4-64-ok => has_procedure advisory mga4-32-ok mga4-64-ok
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2014-0165.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED