Only caveat: metainformation for searchresults, which hung beagle-search
previously, isn't filled in automatically and metainfo for a
searchresult only appears after a click on the searchresult.
I think thats a known bug/feature of beagle-search - that the
information is only shown after
Here is the startup script in the recent debian dbus-x11 package:
/etc/X11/Xsession.d/75dbus_dbus-launch
...
(from http://packages.debian.org/sid/i386/dbus-x11/filelist)
--
dbus does not start automatically in Hardy
https://bugs.launchpad.net/bugs/207157
You received this bug notification
I checked with the dbus-x11 package in other distributions. They contain
an xinit startup script which starts dbus with X. I couldnt check the
contents of the dbus-x11 in hardy, but others are installing dbus-x11 to
fix this problem. Of course the relevant apps need to also depend on
dbus-x11.
--
Same on inspiron 1100 w/ Hardy. Identical lshal/lshal -m outputs so not
attaching anything. I can do some tests if needed. Thanks.
--
[Hardy] Guidance-power-manager doesn't know when laptop is mains unplugged
https://bugs.launchpad.net/bugs/213128
You received this bug notification because you
We should fix the package.
Then use the files for the beagle-firefox package for Intrepid. That is
based on beagle-0.3.7 and contains a compatible extension.
--
Beagle extension designated as incompatible with latest version of firefox 3
https://bugs.launchpad.net/bugs/239579
You received this
Alexander,
Pasting from the email about the nomination of the extension on
addons.mozilla.org ...
---
Your nominated add-on, Beagle Indexer, has been reviewed by a Mozilla Add-ons
editor who decided to retain your add-on in the sandbox.
Review Information:
I am one of the upstream developers.
This bug can be closed at it is not related to Ubuntu.
* The beagle extension packaged in Ubuntu Hardy is not meant to be used in
Firefox-3.
* The beagle extension the reporter used was from addons.mozilla.org.
* The beagle extension in the Intrepid version
I didnt try but based on the above information, this problem will happen
if you try to open a chat search result. Thats when libgalago is called.
Also take a look at the duplicate bugs for more information.
--
System.DllNotFoundException: libgalago
https://bugs.launchpad.net/bugs/186049
You
Upstream rejected it. The extension included with beagle-0.3.5 and
earlier was not fully compatible with firefox-3. beagle-0.3.6 later came
out with a compatible extension. If ubuntu didnt change anything in the
extensions then the extension would work fine as intended (i.e. pre-
beagle-0.3.6
*** This bug is a duplicate of bug 186049 ***
https://bugs.launchpad.net/bugs/186049
** This bug has been marked a duplicate of bug 186049
System.DllNotFoundException: libgalago
--
Crash beagle-search then search to a Pidgin history
https://bugs.launchpad.net/bugs/238709
You received
Same issue here. Hardy + all available updates.
Why is the status of this bug incomplete ?
--
Brightness function keys reversed
https://bugs.launchpad.net/bugs/220310
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Ah... this will cause a problem. You need to add /home/eric/Mail/Mail to
the exclude-directory list in beagle-settings (i.e. tell beagle's
filesystem crawler to leave thunderbird's email to thunderbird crawler
only). Remove ~/.beagle/Indexes/FileSystemIndex and then start beagled.
The re-indexing
*** This bug is a duplicate of bug 186049 ***
https://bugs.launchpad.net/bugs/186049
** This bug has been marked a duplicate of bug 186049
System.DllNotFoundException: libgalago
--
beagle crash while trying to open messenger application
https://bugs.launchpad.net/bugs/228903
You received
file:///home/eric/Mail/Mail/eric.sagnard/ct.sbd/Ricci.msf
this does not look like thunderbird email !!! Isnt it supposed to be in
~/.thunderbird or something like that ?
--
beagle search does not open thundbird any more..
https://bugs.launchpad.net/bugs/228787
You received this bug notification
Can you start beagle-search from a terminal, search for some email, try
to open the email and then paste here the terminal contents ?
--
beagle search does not open thundbird any more..
https://bugs.launchpad.net/bugs/228787
You received this bug notification because you are a member of Ubuntu
dbus not starting by default in KDE - isnt this some kind of major bug
?
importance is still undecided and no one seems to care about this
problem. What is the ubuntu way to at least mark a bug as confirmed ?
Can users mark it as confirmed ?
--
dbus does not start automatically in Hardy
Debian unstable has 0.3.7-1 (7 more days to enter testing). Maybe
grabbing from unstable would be better.
--
Please merge beagle 0.3.4-1 from debian sid
https://bugs.launchpad.net/bugs/224318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Disabling the EvolutionDataServer backend might help. There are similar
crash bugs filed against evolution-sharp which beagle uses.
--
Beagle does not index Thunderbird mails
https://bugs.launchpad.net/bugs/221073
You received this bug notification because you are a member of Ubuntu
Bugs, which
Moving the bug to galago-sharp since thats where the bug actually is.
** Changed in: galago-sharp (Ubuntu)
Sourcepackagename: beagle = galago-sharp
--
System.DllNotFoundException: libgalago
https://bugs.launchpad.net/bugs/186049
You received this bug notification because you are a member of
As mentioned in the comments of LP #62163, you might have to install
dbus-x11 and restart kdm.
--
dbus does not start automatically in Hardy
https://bugs.launchpad.net/bugs/207157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Possibly some missing package or incorrect dependency; as a result of
which whatever is starting dbus for you is not exporting the required
environment variable DBUS_SESSION_BUS_ADDRESS (this variable is not
required by only beagle; it is must available feature of dbus)
--
dbus does not start
Ok - I changed the subject of the bug to reflect the true reason; this
should get the required attention. I still believe its some bug in your
system; this is too major a bug to go unnoticed.
** Summary changed:
- beagle dbus integration broken for battery detection
+ dbus does not start
*** This bug is a duplicate of bug 186049 ***
https://bugs.launchpad.net/bugs/186049
** This bug has been marked a duplicate of bug 186049
System.DllNotFoundException: libgalago
--
crash when previewing an IM conversation in search results (missing DLL
libgalago)
Shouldnt this be filed with X for this to get fixed ?
--
beagle dbus integration broken for battery detection
https://bugs.launchpad.net/bugs/207157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Do you have DBUS_SESSION_BUS_ADDRESS set ? and dbus running ?
--
beagle dbus integration broken for battery detection
https://bugs.launchpad.net/bugs/207157
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Well ... dbus session bus address has to be set for any application to
contact dbus. Could be a hardy error. BTW, if you log in via ssh, then
dbus session is not set and you have to set it manually.
--
beagle dbus integration broken for battery detection
https://bugs.launchpad.net/bugs/207157
Then its a kdm bug. dbus-launch (or dbus-daemon --session, IIRC) is
supposed to export that environment variable. KDE does not use a lot of
dbus otherwise you would have noticed it somewhere else too.
--
beagle dbus integration broken for battery detection
https://bugs.launchpad.net/bugs/207157
See if this helps:
https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/194608
--
BeagleDaemon.exe crashed with SIGSEGV in mono_class_from_typeref()
https://bugs.launchpad.net/bugs/202871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Depends on #193715
--
beagled dependency not met
https://bugs.launchpad.net/bugs/194608
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This is due to the new gnome in which gconf-sharp dropped its dependency
on glib. Fix is given here and is in upstream too
http://bugzilla.gnome.org/show_bug.cgi?id=514252
--
Merge beagle 0.3.3-2 from Debian(Unstable)
https://bugs.launchpad.net/bugs/193715
You received this bug notification
*** This bug is a duplicate of bug 194608 ***
https://bugs.launchpad.net/bugs/194608
** This bug has been marked a duplicate of bug 194608
beagled dependency not met
--
beagle search daemon doesn't work
https://bugs.launchpad.net/bugs/200132
You received this bug notification because you
Any progress on this one ?
--
Merge beagle 0.3.3-2 from Debian(Unstable)
https://bugs.launchpad.net/bugs/193715
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Simone, you are facing
https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/194608
A lot of people are complaining about this, ubuntu should fix their build asap.
--
crash for other application (beagled-helper)
https://bugs.launchpad.net/bugs/84699
You received this bug notification
About the taglib-sharp, it was reported in
https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/194608
Debian-0.3.3-2 might have fixed it, not sure.
--
System.DllNotFoundException: libgalago
https://bugs.launchpad.net/bugs/186049
You received this bug notification because you are a member of
** Bug watch added: GNOME Bug Tracker #386028
http://bugzilla.gnome.org/show_bug.cgi?id=386028
** Also affects: beagle via
http://bugzilla.gnome.org/show_bug.cgi?id=386028
Importance: Unknown
Status: Unknown
--
beagle dosn't index 7zip file
https://bugs.launchpad.net/bugs/179023
The problem is fixed in the hardy version.
--
sqlite version mismatch causes problems in Evolution backend
https://bugs.launchpad.net/bugs/153051
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Osmo, the mozilla-thunderbird errors were due to a faulty Thunderbird
backend which was actually disable upstream but strangely enabled in
ubuntu. That and the other errors were fixed in 0.3.0 which was
released a month ago. The ICSharpCode.SharpZipLib.Zip.ZipException is
not fatal, it just
0.3.1 has entered debian! Aren't there automatic ways to make ubuntu
packages from debian packages ?
--
New upstream release (0.3.1)
https://bugs.launchpad.net/bugs/177473
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
This really depends on
https://bugs.launchpad.net/ubuntu/+source/gmime2.2/+bug/157127
How do you add dependson bug number in launchpad ?
--
[gutsy] Email subject not displayed in beagle-search and kerry
https://bugs.launchpad.net/bugs/139558
You received this bug notification because you are a
** Summary changed:
- Missing package dependency prevents indexing beagle to index kmail
+ libgmime2-cil should depend on libgmime2
** Description changed:
In this thread
https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/139558 we found at
that when installing beagle on a kubuntu
Panagiotis, just in case if beagled is still running or if you happen to
find this again, could you send the output of
$ beagle-index-info
$ beagle-status
$ ls -l ~/.beagle/Log/
In two terminals, do
$ tail -f ~/.beagle/Log/current-Beagle
$ tail -f ~/.beagle/Log/current-IndexHelper
(it will keep
Well, it is well eshtablished now that the current intel driver in xorg does
not work with 1100 and other 845 based video cards. There are discussions about
this in xorg mailing list and other distro bugzilla (e.g. Mandriva). Apparently
the LVDS driver isnt implemented.
As expected the Gutsy
Jared, Thunderbird Indexing is disabled in the beagle-0.2.18 release due to
memory and CPU usage problems. Looks like it is enabled on your computer; maybe
the ubuntu packager enables it. I suggest turning it off by doing this as user
from the command line
$ beagle-config daemon DenyBackend
Shouldn't libgmime2.2-cil depend on libgmime2 ? Can you take this up
with libgmime2-cil people ... if there is a dependency problem that
should be resolved urgently. There are other programs that depend on
libgmime2-cil.
--
[gutsy] Email subject not displayed in beagle-search and kerry
*** This bug is a duplicate of bug 93064 ***
https://bugs.launchpad.net/bugs/93064
** This bug has been marked a duplicate of bug 93064
beagle-search crashes when selecting a gaim conversation
--
beagle-search crashes with GLib.GException: Couldn't recognize the image file
format
Aha ... you have a non-english language. There was a known issue with
languages using , as a decimal separator - there is a ubuntu update
waiting to be approved to fix this,
Then there is a separate issue (beagle-search isnt affected by the locale
problem but kerry is). Somehow your email dont
** Attachment added: 1190008426.8665.Vm9xj:2,S
http://launchpadlibrarian.net/10155871/1190008426.8665.Vm9xj%3A2%2CS
I works correctly on my machine :( EMails are extracted using
gmime-sharp (gmime-cil depending on how it is packaged) which depends
on gmime. So, there could be some problem
Can you attach the output of
$ beagle-query --verbose amazon
The output will be quite large, so redirect it to a file and attach the
file. Just cross check that the same query is giving no subject/no
sender in beagle-search.
--
[gutsy] Email subject not displayed in beagle-search and kerry
it wasn't, after a sudo apt-get install python-beagle it workes fine.
Is there a simple way to tell the user about that or could it be added
to the prerequisites of deskbar-applet, as a normal user expects this to
work.
IMO, python-beagle _should_ be added as a prerequisite to deskbar.
--
Is the python-beagle package installed ? It is needed.
--
libbeagle should be compiled with python support
https://bugs.launchpad.net/bugs/149979
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I am also an (unfortunate) 1100 user. I was trying out the gutsy rc1
live cd and noticed how it failed to detect my video card and monitor
and started using vesa. Furthermore, once I logged out, it refused to
return me to the login screen. :(
Anyway, brianglass/raveenys, the IgnoreEDID trick
I checked and found 0.2.18 (the upstream package) was uploaded for
Gutsy.
--
beagled crashes
https://bugs.launchpad.net/bugs/128804
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
if you are using 0.2.14+, then you can send
$kill -SIGUSR2 `pidof beagled-helper`
which will print the name of the file beagled-helper is stuck at in the log
file ~/.beagle/Log/current-IndexHelper
(from http://beagle-project.org/Troubleshooting_CPU)
--
beagled-helper uses 100% CPU
if you are using 0.2.14+, then you can send
$kill -SIGUSR2 `pidof beagled-helper`
which will print the name of the file beagled-helper is stuck at in the log
file ~/.beagle/Log/current-IndexHelper
(from http://beagle-project.org/Troubleshooting_CPU)
--
beagled-helper needs 100% CPU after some
The bug with xdgmime might be hard to fix. It is really hard to detect
correct rfc822 files with all the different headers MUAs put it. Still
its a good idea to let them know.
If there are hidden directories, then even with the bug fixed, it will
not improve current situation. Someone has to
This has been implemented upstream. Check here for details:
http://mail.gnome.org/archives/dashboard-hackers/2007-September/msg00012.html
--
Index all Maildir folders
https://bugs.launchpad.net/bugs/139547
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
beagle can index zip files since a long time. Possibly you are using a
rather old version.
--
Archive indexing is needed.
https://bugs.launchpad.net/bugs/139314
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
So its more a gtk-sharp/mono/PPC bug. I think they should be notified.
Can someone change the product so that the mono guys can see this and
work on this ?
--
SIGSEGV in beagle-search
https://bugs.launchpad.net/bugs/133377
You received this bug notification because you are a member of Ubuntu
This has something to do with the recent mono. These are similar problems in
monodevelop and banshee.
http://lists.ximian.com/pipermail/monodevelop-list/2007-August/006512.html
http://www.mail-archive.com/debian-bugs-rc%40lists.debian.org/msg109852.html
--
SIGSEGV in beagle-search
I am told that without gmcs, the performance will be slow(er). I have no
actual experience though.
--
beagled exceptions reported in log file
https://bugs.launchpad.net/bugs/115260
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
This was fixed upstream either in 0.2.16.3 or if not, 0.2.17
--
beagle seems to interfer with other applications
https://bugs.launchpad.net/bugs/115682
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
** Bug watch added: GNOME Bug Tracker #393456
http://bugzilla.gnome.org/show_bug.cgi?id=393456
** Also affects: beagle (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=393456
Importance: Unknown
Status: Unknown
--
beagle don't allow to add additional paths for indexing
I checked that page. Konqueror crashes as it is on that page. The
stacktrace shows somefault in libpcre0. This is a konqueror bug, nothing
to do with beagle.
Beagle does not crash for me with this page. I suspect if beagle crashed
in the original report, it must have been a coincidence. There are
This is upstream commit
http://svn.gnome.org/viewcvs/beagle?rev=3736view=rev
Beagle ignores a lot of patterns, but *.db was not among them, I added it it.
http://svn.gnome.org/viewcvs/beagle?rev=3747view=rev
--
smarter beagle configuration for excluding items
Beagle (and other xml-serializer + asp.net based apps) requires gmcs to
run. I asked Joe (maintainer of Beagle) about this, and he says that
beagle package should depend on whatever package gmcs is.
--
beagled exceptions reported in log file
https://bugs.launchpad.net/bugs/115260
You received
the strange thing is that it seems that the index builder removes
files and readds them into the index
Beagle is supposed to check if a file is already indexed, if not it
prints the -file:/// and +file:/// and proceeds to add the file to the
index. The actual file is indexed between these two
Actually, I would rather see the documentation one.
The application is working ok. The reason you see files being repeated
is, build-index does not have any filter (parser) for screensaver
desktop files, so when the indexer gets such a file it says Error:
Could not filter file: No desktop entry
Yeah, the ionice is supposed to lower the io priority. Actually, if you check
the first two lines of the log, you will see Debug: Set best effort IO
priority to lowest level (7)
Debug: Reniced process to 19 - which means beagle is already trying to play
fare.
Could you attach one of the
I figured out the problem. The docbook parser is failing to parse those
files, thus those files are getting filtered again on re-indexing. It
really cannot be avoided, since users can always install updated filters
before re-running build-index.
The bad thing is that the docbook filter decides
exe, dll, .o etc binary files are already ignored. Are you seeing them
appearing in the log file ?
The last suggestion in already in place upstream.
--
smarter beagle configuration for excluding items
https://bugs.launchpad.net/bugs/115289
You received this bug notification because you are a
Rodrigo, if you are still seeing the problem can you attach the log
files (from ~/.beagle/Log/).
--
Beagle continues to index data while laptop is on battery power
https://bugs.launchpad.net/bugs/91974
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Ok. Can someone re-open the upstream bug please ?
Thanks.
--
beagle doesn't look for liferea feed in ~/.liferea_1.2 folder
https://bugs.launchpad.net/bugs/103295
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Someone above said Have you tried removing the .liferea directory?
After running Liferea 1.2 it says you should do that. ... Though, after
running liferea again, it gave me a .liferea symlink to .liferea_1.2. -
can anyone else confirm if this is the case ? If liferea indeed creates
the symlink,
Beagle filling the hard disk is an unfortunate side effect of the main
bug which is basically a duplicate of 108957.
Fix for 108957 has been released upstream in 0.2.17
--
beagle throws exceptions, fills hard drive with logs
https://bugs.launchpad.net/bugs/24
You received this bug
Upstream release 0.2.17 fixes the problem.
--
Beagle doesn't handle coma in mail folder name
https://bugs.launchpad.net/bugs/108957
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Mabye I'm just impatient. After a wait (what I consider a long wait) it
does go away, so maby things are working as intented and it just takes a
long time to index my files? But I just booted and now have the message.
This is the output of the command you requested:
~$ beagle-info --status
Is the error always for those files/directory or it changes ?
Also, can you attach the log files of beagled and index-helper ?
--
beagle stuck in indexing loop
https://bugs.launchpad.net/bugs/104647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Which version of beagle are you using ?
--
beagle stuck in indexing loop
https://bugs.launchpad.net/bugs/104647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
If the problem is still there, could you attach the output of (while beagle is
running and the notification is being shown)
$ beagle-info --status
--
Beagle search keeps telling me Your data is being indexed
https://bugs.launchpad.net/bugs/106513
You received this bug notification because you
Philip,
could you do the following ? (it will be very helpful).
1) Put this in your .gdbinit in your home directory
---8-
define mono_backtrace
select-frame 0
set $i = 0
while ($i $arg0)
set $foo = mono_pmip ($pc)
if ($foo == 0x00)
frame
else
printf #%d %p
I have had the same problem here, but I cannot reproduce it. I stopped
beagle-build-index using 'killall beagle-build-index', and the logs
confirm that it stopped normally. But anyway, it was eating all CPU,
apparently building a new index because I have recently upgraded to
Feisty.
I
I dont think I can remove the attachment, I dont have the permission.
Kerry (the KDE client) has the notification system. No mechanism to
pause it though.
Adding a ready made index is a good idea. Any feisty dev listening ???
--
beagle-build-index hangs and must be killed
Its a .exe because thats the naming convention used for .Net binaries.
It should not be confused with a win32 executable :-). What's in a name
?!
--
[apport] BeagleDaemon.exe crashed with SIGSEGV
https://launchpad.net/bugs/92662
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Yes you are right. These information is pretty much useless for mono
apps. If you will, see if you can reproduce the crash by starting
beagled from a terminal (give --fg --mono-debug as an argument, it
will generate verbose output stacktrace). If beagled crashes, it will
leave a stacktrace which
No it isnt normal. However, it could be that beagled in just wrapping up before
exiting. You can try the following.
$ tail -f ~/.beagle/Log/current-Beagle
This will keep printing whatever the log messages. Do a beagle-shutdown, see
what messages show up in the log. If beagle is in the middle of
Upstream is faster in exiting when SIGTERM is sent. If it persists, I
would be curious to know how long it is taking to exit after the signal
is sent ? In general, if beagle is in the middle of indexing a huge
file, it will finish that file and then exit.
--
Beagle loses file index on restart
Can you run open a terminal and give this command:
beagle-build-index --debug /usr/lib/beagle/BuildIndex.exe --target
/tmp/beagledocindex --disable-directories --recursive --allow-pattern
*.xml,*.html,*.docbook /usr/share/doc /usr/local/share/doc /opt/kde3/share/doc
/opt/gnome/share/gnome/help
Enigma, you seem to be having the problem on a regular basis. With a little
effort, you may be able to provide valuable input in identifying the problem.
After you login, in a terminal give,
$ beagled --replace --fg
This will start beagle in the terminal and print all kind of lines
saying what
kill -9 (kill -SIGKILL) should never be sent to any program which is not
hanged. Ever tried sending SIGKILL to any filesystem or kernel process ?
You should use SIGTERM or SIGINT. kill -9 can not be handled by the
process and so beagle exits with an inconsistent state. Even if the
issue in the
apport crashdump is not very useful for mono apps like beagle. Mono
stacktrace is the one that is needed. Please follow the instructions at
http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login to
help us get a mono stacktrace.
--
mono-jit crashed
https://launchpad.net/bugs/89768
--
MKersloot, when you say catching the errors does not reveal any useful
information. It only shows there are recurrences in my calendar - I
presume you are doing the 2~/.beagle/crash thing as mentioned in the
wiki. I am still interested in the contents of that file because it
should not contain the
apport crashdump is not very useful for mono apps like beagle. Mono
stacktrace is the one that is needed. Please follow the instructions at
http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login to
help us get a mono stacktrace.
--
[apport] mono crashed with SIGSEGV
The crash might be a random one. If you want, there are some
instructions at http://beagle-
project.org/Troubleshooting#Beagle_crashes_on_login on how to get the
mono stacktrace when beagle crashes. We'll appreciate if you follow the
steps and help us obtain a mono stacktrace.
--
[apport] mono
Do you have the package mono-mcs installed ? This package is necessary
for beagle. If not, can you install this and let us know if it crashes
even then.
--
[apport] beagled crashed with SIGSEGV
https://launchpad.net/bugs/89911
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
To figure out what is crashing beagle we need the mono stracktrace.
Please see this http://beagle-
project.org/Troubleshooting#Beagle_crashes_on_login
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This does not seem to be due to anything in beagle. For more
information, you need to attach the mono stacktrace. Please see this
http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login
--
beagle crashed right after reboot
https://launchpad.net/bugs/69136
--
ubuntu-bugs mailing list
The crash could be a random one. From other's reports, it does not seem to be
any problem inside beagle.
To figure out what is crashing beagle we need the mono stracktrace when it
crashed. Please see this
http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login
--
Mono crashed on
To figure out what is crashing beagle we need the mono stracktrace.
Please see this http://beagle-
project.org/Troubleshooting#Beagle_crashes_on_login
--
[apport] beagled crashed with SIGSEGV
https://launchpad.net/bugs/88591
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Or, you can follow the instructions given in
http://beagle-project.org/Troubleshooting#Beagle_crashes_on_login
to collect the mono stacktrace. The mono stacktrace is necessary in finding out
what is causing the crash.
--
beagled crash on startup
https://launchpad.net/bugs/88715
--
Unfortunately the apport crash dump is not very useful. Please run the
command from a terminal. When buildindex crashes, it will leave the mono
stacktrace on the terminal which is useful.
$ beagle-build-index --debug /usr/lib/beagle/BuildIndex.exe --target
/tmp/beagle-index-documentation
1 - 100 of 127 matches
Mail list logo
