> ** Changed in: beagle (Ubuntu)
>Status: Incomplete => Fix Released
The status was changed to "Fix Released". I am interested to know what was the
fix. Link to the relevant patch or some relevant discussion or any other
pointers ?
--
Beagle crash on startup
https://bugs.launchpad.net/
** Changed in: beagle (Ubuntu)
Status: Incomplete => Fix Released
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
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@list
** Changed in: beagle (Ubuntu)
Importance: Undecided => Medium
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
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.ubunt
Gary: Use a newer version. 0.2.16.3 is in feisty, or you can get
updated edgy packages here: http://beagle-project.org/files/ubuntu/edgy/
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Received the error on reboot, had been trying to set up samba
connections to a windows file server.
** Attachment added: "_usr_bin_beagled.1000.crash"
http://librarian.launchpad.net/7731670/_usr_bin_beagled.1000.crash
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
You receiv
Joe, I sent you my
.beagle/Indexes/FileSystemIndex/FileAttributesStore.db . Unfortunately
the log file has been erased because I waited so long to reply, and
beagle apparently creates a new file every time my laptop comes back
from sleep.
The good news is that the crash seems to be gone after I u
Philip: interesting. It would be helpful if you could email me the logs
and the DB file, if possible. ([EMAIL PROTECTED])
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
The crash only occurs with the "files" backend:
beagled --backend files --fg --debug
I set only the directory /etc/sound/events to be indexed. No
IndexHelper log file is created, and the current-Beagle log file
(~/.beagle/Log/current-Beagle) mentions "/etc" only on the second-last
line:
Philip: Interesting. Can you check the logs (in ~/.beagle/Log) to see
what files it might be crashing on?
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-
Beagled stops crashing if I remove /etc from the list of directories to
index, in addition to my home directory. If any subdirectory of /etc is
listed , beagled crashes as above. Other root subdirectories, such as
/usr have no effect either way.
--
Beagle crash on startup
https://bugs.launchpad
Beagled does not crash if I attach it to the gdb process. It crashes
reliably if I start it without. The gdb output is attached.
** Attachment added: "gdb output"
http://librarian.launchpad.net/7508140/beagled_crash_gdb.txt
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
You
Cascade: if you're running the released version of Feisty, can you
attach your ~/.beagle/Log/current-Beagle file to the bug? It should
have the printed output from Mono when it crashed.
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
You received this bug notification because yo
Beagle crashed for no apparent reason - well nothing I did anyway. I was just
composing a note with the gapplet Sticky Notes 2.16.1.
Dump attached. On startup,
** Attachment added: "_usr_bin_beagled.1000.crash"
http://librarian.launchpad.net/7472104/_usr_bin_beagled.1000.crash
--
Beagle cras
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 %
Yeah, very bizarre!
The next thing to try would be to attach gdb to the process and get a
threaded stack trace when it crashes.
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
> ** Attachment added: ""beagled --fg" from sh"
>http://librarian.launchpad.net/7124666/beagled_crash_4.txt
Beagle must be messing (exposing ?) up something deep inside mono.
Even mono sigsegv handler is not getting invoked!
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
Yo
Of course, you are right that the reported address boundary error is
Fish-specific.
It's interesting that this bug does not occur on my other Ubuntu 6.10
box, which should have the same versions of Beagle and other Mono apps
and libraries. But the content that is indexed is different.
** Attachm
Oh, I see that you describe what fish is above. :) Can you try running
it under bash or another shell instead?
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
What is "fish"?
Normally when a mono app crashes it prints out a bunch of stuff to the
console about its stack trace at the time, but it doesn't seem to happen
for you because (I am guessing) that fish is trapping it.
--
Beagle crash on startup
https://bugs.launchpad.net/bugs/71383
You received
Attached is a crash "stacktrace" (report) generated using the second
method described on http://beagle-
project.org/Troubleshooting#Beagle_crashes_on_login . It ends with an
address boundary error.
Beagled crashes not only when I log in, but consistently every time I
start it. I just start it fr
I should say that the other suggested methods of creating a stacktrace
-- "beagled 2> ~/.beagle/crash" and using "exec -a $PROCESS_NAME
$CMDLINE 2>~/.beagle/crash &" /usr/bin/beagled create an empty file.
There is no output.
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-
Here is a second report, which also ends with an address boundary error,
but is slightly different, and so I include it for our common amusement.
** Attachment added: "output from "beagled --fg""
http://librarian.launchpad.net/7101011/beagled_crash_2.txt
--
Beagle crash on startup
https://la
Same thing, attach beagle log.
** Attachment added: "Beagle .beagle/Log directory after crash."
http://librarian.launchpad.net/7097626/beagle.log.tar.bz2
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
Same thing
** Attachment added: "full report"
http://librarian.launchpad.net/7040127/_usr_bin_beagled.1000.crash
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Same here, edgy intel 32bit
** Attachment added: "dump"
http://librarian.launchpad.net/6825727/_usr_bin_beagled.1000.crash
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
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
https://lists.ubuntu.com/ma
Thanks Kevin. Unfortunately the log files dont point to anything wrong in
beagle. Its extremely important to figure out the right stacktrace -
unfortunately the apport crashdump is not very helpful for mono programs. Can
you change your beagled startup code as
"beagled 2>~/.beagle/crash"
(inst
Here you go, I only started having the problem recently, (last few days)
so I've only included the logs for about a week.
** Attachment added: "Beagle Logs"
http://librarian.launchpad.net/6600595/beaglelog.tar.gz
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mai
Hi,
The crash dump is not entirely useful for beagle. It will be helpful if
anyone who saw the problem could attach the ~/.beagle/Log directory
(tar-gzipped) to the bug.
Thanks.
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
same problem. ubuntu edgy. intel.
** Attachment added: "beagle crash at startup"
http://librarian.launchpad.net/6506316/_usr_bin_beagled.1000.crash
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/m
Same here
** Attachment added: "crash report"
http://librarian.launchpad.net/5909329/_usr_bin_beagled.1000.crash
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Yeah I've got the same problem with an AMD64 X2 4200 running Edgy
(32bit). Crashed on startup.
** Attachment added: "Crash report"
http://librarian.launchpad.net/5807751/_usr_bin_beagled.1000.crash
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubunt
same here feisty amd64
** Attachment added: "crash report file"
http://librarian.launchpad.net/5800744/beagle.bjI_up.apport
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
The same on Edgy Eft AMD64.
** Attachment added: "Beagled crash (Edgy Eft AMD64)"
http://librarian.launchpad.net/5756703/_usr_bin_beagled.1000.crash
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
same here i attached my crash report
** Attachment added: "beagled crash"
http://librarian.launchpad.net/5451379/_usr_bin_beagled.1000.crash
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
Same here. Edgy Eft.
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: mono (Ubuntu)
Sourcepackagename: mono => beagle
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This looks to be a mono bug.
** Changed in: beagle (Ubuntu)
Sourcepackagename: beagle => mono
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
dump attached
** Attachment added: "dump"
http://librarian.launchpad.net/5052774/_usr_bin_beagled.1001.crash
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Summary changed:
- crash
+ Beagle crash on startup
** Changed in: beagle (Ubuntu)
Status: Unconfirmed => Needs Info
--
Beagle crash on startup
https://launchpad.net/bugs/71383
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
40 matches
Mail list logo
