Bug#589707: [pkg-mono-group] Processed: Re: Bug#589707: /usr/bin/mono: Segfault in mono runtime

[Fabian Fagerholm]

On Sat, 2010-08-07 at 01:08 +0200, Mirco Bauer wrote:
 I just upgraded from Mono 2.6.3 to 2.6.7 while having a plenty of Mono
 applications running (like Smuxi, Tomboy, Banshee, etc) and had no
 issues with starting new applications nor with the currently running
 ones.
 
 I believe though that the .wapi stuff could be related. Have you used
 fakeroot or something that fiddles with HOME? as that can pretty badly
 break Mono, see:
 http://pkg-mono.alioth.debian.org/cli-policy/ch-mono.html#s-mono-disable-shm

No fakeroot, no fiddling with $HOME – just plain installed packages.
I've been tracking testing for quite a while, so it's perfectly possible
that my setup is not 100% in shape.

 As I can't reproduce this issue I am setting severity to important for
 now.

Fair enough. I had some more mono-related trouble: Tomboy won't start
and I get a gdb backtrace if I run it in the console. The same thing
happens with a number of other mono-based packages.

Since Tomboy was the only reason for having mono installed, I switched
to Gnote and uninstalled mono...

If there's any additional tests I should run, please let me know.

-- 
Fabian Fagerholm fa...@paniq.net


signature.asc
Description: This is a digitally signed message part

Bug#589707: [pkg-mono-group] Processed: Re: Bug#589707: /usr/bin/mono: Segfault in mono runtime

[Mirco Bauer]

severity 589707 important
tags 589707 + unreproducible
thanks

On Wed, 21 Jul 2010 08:51:03 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

 retitle 589707 Running mono apps can prevent upgrade from working
 thanks
 
 On Tue, 2010-07-20 at 11:50 +0100, Jo Shields wrote:
  I don't think you've installed it fully - mono-gac should never be
  marked as pn.
  
  Are you sure mono-runtime is installed?
 
 Yes, it was installed. The reason for that status was that no
 mono-related packages could be fully installed, they all crashed at
 some point during the installation.
 
 However, I found the reason: I had Tomboy running. Ripping out all
 mono-related packages, killing the tomboy process, and reinstalling,
 allowed mono to work again.
 
 Apparently, some mono upgrades require that all processes running
 under an old runtime version be stopped. Retitling accordingly. No
 idea how to detect or fix something like this – the only reason I
 have mono installed is because of Tomboy.

I just upgraded from Mono 2.6.3 to 2.6.7 while having a plenty of Mono
applications running (like Smuxi, Tomboy, Banshee, etc) and had no
issues with starting new applications nor with the currently running
ones.

I believe though that the .wapi stuff could be related. Have you used
fakeroot or something that fiddles with HOME? as that can pretty badly
break Mono, see:
http://pkg-mono.alioth.debian.org/cli-policy/ch-mono.html#s-mono-disable-shm

As I can't reproduce this issue I am setting severity to important for
now.

PS: please don't use -qu...@b.d.o next time, I had to copy my reply
from the webinterface of the BTS...
-- 
Regards,

Mirco 'meebey' Bauer

PGP-Key ID: 0xEEF946C8

FOSS Developermee...@meebey.net  http://www.meebey.net/
PEAR Developermee...@php.net http://pear.php.net/
Debian Developer  mee...@debian.org  http://www.debian.org/



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org