Bug#400239: This bug hasn't been fixed in DFSG-2
OK, we can close this bug. I found the problem. It wasn't /usr or any /usr/local or other software install problems. I setup a new user with default settings and lo and behold monodevelop worked. In my normal login, I was running bare bones fluxbox and the new profile was running gnome, so I got a basic gnome desktop setup and monodevelop worked in my profile. Then I eliminated fluxbox as a problem by logging in as the new user running fluxbox only. This also worked. So, I compared the .fluxbox/init between the new login and mine and found this statement that used to be required for Mozilla and had been listed for some early monodevelop problems. export MOZILLA_FIVE_HOME=/usr/lib/mozilla removing that, all is well. Seems like a bug honestly but I'm not sure in which package. XULRunner? Philip Nelson - http://xcskiwinn.org/community/blogs/panmanphil - Original Message From: Mirco Bauer <[EMAIL PROTECTED]> To: [EMAIL PROTECTED]; Philip Nelson <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Sent: Saturday, June 2, 2007 4:56:55 AM Subject: Re: Bug#400239: This bug hasn't been fixed in DFSG-2 tags 400239 + unreproducible thanks On Fri, 2007-06-01 at 19:45 -0700, Philip Nelson wrote: > Any updates on this bug? I just updated my system with everything in > unstable: it's not reproducible for anyone besides you, I believe you have something on your system modified that causes, like installing software packages (tarballs) in /usr/local or even worse /usr. Software like Mono, Gecko, Firefox, somethingFox, XulRunner it crashes in gecko which uses XulRunner. You should try xulrunner directly or from other application, I am not sure how to test xulrunner though directly. Since Mono 1.2.4-1 packages, I added handy -dbg packages, your stack trace is a bit obfuscated, please install: mono-dbg and mono-jit-dbg libmono0-dbg and try again to start MonoDevelop and attach a complete fresh stack trace here. -- Regards, Mirco 'meebey' Bauer PGP-Key: http://keyserver.noreply.org/pks/lookup?op=get&search=0xEEF946C8 -BEGIN GEEK CODE BLOCK- Version: 3.12 GIT d s-:+ a-- C++ UL$ P L++$>+++$ E- W+++$ N o? K- w++>! O M- V? PS PE+ Y- PGP++ t 5+ X++ R tv+ b+ DI? D+ G>++ e h! r->++ y? --END GEEK CODE BLOCK--
Bug#382294: libcdk5: libcdkw support
Package: libcdk5 Version: 5.0.20050424-2 Severity: wishlist G'day. The libcdk5 has a configure option of --with-ncursesw which adds wide character support to libcdk, giving a /usr/lib/libcdkw.so.5.0. I guess this could be done by either adding ncursesw as a dependancy to libcdk5 or by having a new libcdkw5 package which depends on ncursesw. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Versions of packages libcdk5 depends on: ii libc6 2.3.6-15 GNU C Library: Shared libraries libcdk5 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#400239: This bug hasn't been fixed in DFSG-2
I just updated to the version shown and this bug is still there. When it didn't come up at first, I deleted the .config?Monodevelop directory. then I got a sharing violation trying to write and read to addins.config at the same time. Now I get a minimal addins.config, repositories only, 2 listed. I get the stack trace in the original bug report. It fails after logging that MonoDevelop.Ide was loaded. I do have all the addins installed available in the repository. INFO MonoDevelop.Core.ILoggingService (null) - Initializing service: MonoDevelop.Core.PropertyService 6300 [-1225348208] INFO MonoDevelop.Core.ILoggingService (null) - Loaded add-in: MonoDevelop.Projects 6386 [-1225348208] INFO MonoDevelop.Core.ILoggingService (null) - Loaded add-in: MonoDevelop.Documentation 6746 [-1225348208] INFO MonoDevelop.Core.ILoggingService (null) - Loaded add-in: MonoDevelop.Core.Gui 6840 [-1225348208] INFO MonoDevelop.Core.ILoggingService (null) - Initializing service: MonoDevelop.Core.StringParserService 7966 [-1225348208] INFO MonoDevelop.Core.ILoggingService (null) - Loaded add-in: MonoDevelop.Projects.Gui 9353 [-1225348208] INFO MonoDevelop.Core.ILoggingService (null) - Loaded add-in: MonoDevelop.Ide Philip - http://xcskiwinn.org/community/blogs/panmanphil
Bug#400239: This bug hasn't been fixed in DFSG-2
--- Original Message From: Mirco Bauer <[EMAIL PROTECTED]> To: Philip Nelson <[EMAIL PROTECTED]>; [EMAIL PROTECTED] Sent: Sunday, April 15, 2007 9:30:58 AM Subject: Re: Bug#400239: This bug hasn't been fixed in DFSG-2 On Sun, 2007-04-15 at 06:26 -0700, Philip Nelson wrote: >> I just updated to the version shown and this bug is still there. When >> it didn't come up at first, I deleted the .config?Monodevelop >> directory. then I got a sharing violation trying to write and read to > addins.config at the same time. > You deleted the config directory while MonoDevelop was running? That's > not a good idea. I was under the impression that both my situation and the original bug report happened when monodevelop can't even start. So no, I didn't delete the folder when it was running because it doesn't come up without SIGSEGV. >> Now I get a minimal addins.config, repositories only, 2 listed. I get >> the stack trace in the original bug report. It fails after logging >> that MonoDevelop.Ide was loaded. I do have all the addins installed >> available in the repository. >> > Then I need a detailed description which steps you do to reproduce this > bug. Start clean, means delete ~/.config/MonoDevelop and start > MonoDevelop, describe what you do inside monodevelop, how you quit it > and what you do to let it crash. Else we have no chance to spot this bug > and finally fix it, upstream fixed several things already in this area, > that's why I closed it for the 0.13.1 upload. delete (or don't) .config/MonoDevelop start monodevelop 2>error.log & watch it crash send crash report to Mirco ;-) It comes up with the splash screen, then the ide starts to load. When launched from the console you see the the log4net INFO messages which I posted. That list is not always consistent though. Sometimes it gets farther. Then it crashes before you can do anything in the tool. The splash screen never goes away until the crash. > Also include the stack trace you get and give me the installed versions > of mono and gecko/xul: > dpkg -l|grep mono > dpkg -l|grep xul The stack trace starts with the same info as the original bug as I indicated, but here is one captured when starting monodevelop with .config/MonoDevelop cleared. I am pretty close to up to date debian unstable. Right now only an updated locales package hasn't been loaded by dist-upgade. ii libmono-accessibility1.0-cil 1.2.2.1-2 ii libmono-accessibility2.0-cil 1.2.2.1-2 ii libmono-bytefx0.7.6.2-cil1.2.2.1-2 ii libmono-cairo1.0-cil 1.2.2.1-2 ii libmono-corlib1.0-cil1.2.2.1-2 ii libmono-corlib2.0-cil1.2.2.1-2 ii libmono-data-tds1.0-cil 1.2.2.1-2 ii libmono-data-tds2.0-cil 1.2.2.1-2 ii libmono-firebirdsql1.7-cil 1.2.2.1-2 ii libmono-microsoft-build2.0-cil 1.2.2.1-2 ii libmono-npgsql2.0-cil1.2.2.1-2 ii libmono-oracle2.0-cil1.2.2.1-2 ii libmono-peapi1.0-cil 1.2.2.1-2 ii libmono-peapi2.0-cil 1.2.2.1-2 ii libmono-relaxng1.0-cil 1.2.2.1-2 ii libmono-security1.0-cil 1.2.2.1-2 ii libmono-security2.0-cil 1.2.2.1-2 ii libmono-sharpzip0.84-cil 1.2.2.1-2 ii libmono-sharpzip2.84-cil 1.2.2.1-2 ii libmono-sqlite2.0-cil1.2.2.1-2 ii libmono-system-data1.0-cil 1.2.2.1-2 ii libmono-system-data2.0-cil 1.2.2.1-2 ii libmono-system-runtime1.0-cil1.2.2.1-2 ii libmono-system-runtime2.0-cil1.2.2.1-2 ii libmono-system-web1.0-cil1.2.2.1-2 ii libmono-system-web2.0-cil1.2.2.1-2 ii libmono-system1.0-cil1.2.2.1-2 ii libmono-system2.0-cil1.2.2.1-2 ii libmono-winforms1.0-cil 1.2.2.1-2 ii libmono-winforms2.0-cil 1.2.2.1-2 ii libmono0 1.2.2.1-2 ii libmono1.0-cil 1.2.2.1-2 ii libmono2.0-cil 1.2.2.1-2 ii mono 1.2.2.1-2 ii mono-common 1.2.2.1-2 ii mono-devel 1.2.2.1-2 ii mono-gac 1.2.2.1-2 ii mono-gmcs1.2.2.1-2 ii mono-jit 1.2.2.1-2 ii mono-mcs 1.2.2.1-2 ii mono-runtime 1.2.2.1-2 ii mono-utils 1.2.2.1-2 ii mono-xsp-base1.2.1-2 ii mono-xsp2-base 1.2.1-2 ii monodevelop-boo 0.13.1+dfsg-2 ii monodevelop-java 0.13.1+dfsg-2 ii monodevelop-nunit0.13.1+dfsg-2 ii monodevelop-query0.13.1+dfsg-2 ii mo
Bug#364753: Bug with libnunit2.2-cil
Package: libnunit2.2-cil Version: 2.2.0-2 FYI, the dependencies in unstable for gnunit just got resolved but there is still a problem. Stacktrace is below. nunit-console still works fine. To reproduce, just start gnunit in unstable. ** (gnunit:24722): WARNING **: The class NUnit.Util.XmlResultVisitor could not be loaded, used in nunit.util, Version=2.2.0.0, Culture=neutral gnunit ** (gnunit:24727): WARNING **: The following assembly referenced from /usr/lib/mono/1.0/gnunit.exe could not be loaded: Assembly: nunit.util(assemblyref_index=8) Version:2.2.0.0 Public Key: (none) The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/mono/1.0). nunit.util should be in the GAC from what I can determine. Confirmed by Mirco Bauer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
