Re: Beagle 1.3-1 configuration on Debian AMD64?
Hi, On Wed, 2006-01-11 at 19:03 +0100, Joost Kraaijeveld wrote: > I don't know if this is the correct mailing list for my questions (if > not, what should be the list to ask?). This is the best place. > I have a few questions: > > - Is it correct that the Gnome configuration applet does not store any > additional paths? I'm not sure I understand what specifically you're asking here. The beagle preferences pane only stores the info in the GUI. > - Beagle only starts up once in a while. Most times it crashes on my > machine with a 2.6.15-1-amd64-k8-smp (stock Debian Sid) kernel. Is it > possible to run Beagle reliable? There's no way to know without more information. :) Can you please file a bug at bugzilla.gnome.org, including the logs from ~/.beagle/Log? Thanks, Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 1.3-1 configuration on Debian AMD64?
Hi Joe, On Wed, 2006-01-11 at 14:31 -0500, Joe Shaw wrote: > This is the best place. OK > > I have a few questions: > > > > - Is it correct that the Gnome configuration applet does not store any > > additional paths? > > I'm not sure I understand what specifically you're asking here. The > beagle preferences pane only stores the info in the GUI. I assume that if I add directories outside my home directory (e.g. /usr/src and /usr/share/doc) that after dismissing the applet en reopening the applet again my added entries should still be visible. They are not. I think they should be stored in one of the config files but I am unsure which one and what syntax. > > - Beagle only starts up once in a while. Most times it crashes on my > > machine with a 2.6.15-1-amd64-k8-smp (stock Debian Sid) kernel. Is it > > possible to run Beagle reliable? > > There's no way to know without more information. :) > > Can you please file a bug at bugzilla.gnome.org, including the logs from > ~/.beagle/Log? I will do that later, probably tomorrow but I almost always get the following message in my term: = Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. = Stacktrace: in <0xb> (wrapper managed-to-native) System.Runtime.InteropServices.Marshal:PtrToStringAnsi (intptr) Native stacktrace: mono-beagled(mono_handle_native_sigsegv+0x88) [0x511138] mono-beagled [0x4dffc8] /lib/libpthread.so.0 [0x2b1827a0] /lib/libc.so.6(strlen+0x30) [0x2b58ce60] mono-beagled(mono_string_new+0x39) [0x4a5f79] [0x42b62023] TIA -- Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 e-mail: [EMAIL PROTECTED] web: www.askesis.nl ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 1.3-1 configuration on Debian AMD64?
Hi, On Wed, 2006-01-11 at 21:03 +0100, Joost Kraaijeveld wrote: > I assume that if I add directories outside my home directory > (e.g. /usr/src and /usr/share/doc) that after dismissing the applet en > reopening the applet again my added entries should still be visible. > They are not. I think they should be stored in one of the config files > but I am unsure which one and what syntax. That is probably this bug: http://bugzilla.gnome.org/show_bug.cgi?id=324904 Which is fixed in CVS now. > I will do that later, probably tomorrow but I almost always get the > following message in my term: > > = > Got a SIGSEGV while executing native code. This usually indicates > a fatal error in the mono runtime or one of the native libraries > used by your application. > = > > Stacktrace: > > in <0xb> (wrapper managed-to-native) > System.Runtime.InteropServices.Marshal:PtrToStringAnsi (intptr) > > Native stacktrace: > > mono-beagled(mono_handle_native_sigsegv+0x88) [0x511138] > mono-beagled [0x4dffc8] > /lib/libpthread.so.0 [0x2b1827a0] > /lib/libc.so.6(strlen+0x30) [0x2b58ce60] > mono-beagled(mono_string_new+0x39) [0x4a5f79] > [0x42b62023] A segfault makes me think that this isn't a bug in Beagle, but I don't have a x86-64 box so I can't really check up on this. Do other mono-based apps like Tombody, F-Spot, etc. run? Is anyone else out there running Beagle on an Opteron? (Preferably Debian) Joe ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
Re: Beagle 1.3-1 configuration on Debian AMD64?
= > > Got a SIGSEGV while executing native code. This usually indicates > > a fatal error in the mono runtime or one of the native libraries > > used by your application. > > = > > > > Stacktrace: > > > > in <0xb> (wrapper managed-to-native) > > System.Runtime.InteropServices.Marshal:PtrToStringAnsi (intptr) > > > > Native stacktrace: > > > > mono-beagled(mono_handle_native_sigsegv+0x88) [0x511138] > > mono-beagled [0x4dffc8] > > /lib/libpthread.so.0 [0x2b1827a0] > > /lib/libc.so.6(strlen+0x30) [0x2b58ce60] > > mono-beagled(mono_string_new+0x39) [0x4a5f79] > > [0x42b62023] > > A segfault makes me think that this isn't a bug in Beagle, but I don't > have a x86-64 box so I can't really check up on this. Do other > mono-based apps like Tombody, F-Spot, etc. run? Is anyone else out > there running Beagle on an Opteron? (Preferably Debian) > Also, where are you getting your mono packages? The default debian repo or else ware? If you want a quick fix, building the latest stable mono (1.1.12) from source might help, debian is currently making some major lib changes in unstable/testing. -- Cheers, Kevin Kubasik http://kubasik.net/blog ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
RE: Beagle 1.3-1 configuration on Debian AMD64?
> Also, where are you getting your mono packages? The default debian > repo or else ware? Yep, just a plain apt-get install. > If you want a quick fix, building the latest stable > mono (1.1.12) from source might help, debian is currently making some > major lib changes in unstable/testing. I am using libmono0 1.1.12-1 right now, which is the version you suggest I assume. I will see if it is possible to install the whole mono development environment to compile Beagle without changing too much of my machine (which is basicaly a Etch machine with just enought Sid to run Beagle). Groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 e-mail: [EMAIL PROTECTED] web: www.askesis.nl ___ Dashboard-hackers mailing list Dashboard-hackers@gnome.org http://mail.gnome.org/mailman/listinfo/dashboard-hackers
