not an issue anymore
** Changed in: tracker (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: tracker (Ubuntu Hardy)
Status: Confirmed => Fix Released
--
tracker-extract crashed
https://bugs.launchpad.net/bugs/198863
You received this bug notification because you are a mem
Thanks! There must be a way to halt the indexing service more gracefully
too, maybe by limiting the resources it uses step by step? Let's here
what they have to say.
--
tracker-extract crashed
https://bugs.launchpad.net/bugs/198863
You received this bug notification because you are a member of Ub
Hi,
Savvas Radević [2008-03-13 15:09 -]:
> It looks like both sides could cooperate to solve this :) I know
> this is a minor "bug", but I've reported it in order to avoid
> further reports from other users. A more graceful failing would be
> great
I just uploaded an apport which understands
It looks like both sides could cooperate to solve this :) I know this is a
minor "bug", but I've reported it in order to avoid further reports from other
users.
A more graceful failing would be great
--
tracker-extract crashed
https://bugs.launchpad.net/bugs/198863
You received this bug notific
apport (0.104) hardy; urgency=low
[ Martin Pitt ]
* apport/crashdb_impl/launchpad.py, get_source_version(): re-escape the
package name so that it doesn't stumble over '+' and similar characters.
* apport/ui.py tests: assert that ProcEnviron is also included into bug
reports where we
Still, can't tracker-extractd fail a little more gracefully instead of
triggering a core dump in the kernel? If you don't have apport, then
you'll still get core dumps onto your disk. IMHO you should install a
signal handler and properly _exit() extractd if it gets such a signal
that indicates OOM
Ah, I see what you mean, I was too quick, sorry. Package hooks should
have the ability to completely suppress a report without even the dialog
box.
** Changed in: apport (Ubuntu Hardy)
Assignee: (unassigned) => Martin Pitt (pitti)
Status: Invalid => In Progress
--
tracker-extract cra
If you want to ignore a particular class of crashes, please add an
apport hook to tracker. Please see /usr/share/doc/apport/package-
hooks.txt.
** Changed in: tracker (Ubuntu Hardy)
Status: Invalid => Confirmed
--
tracker-extract crashed
https://bugs.launchpad.net/bugs/198863
You received
We don't want to pile up special cases in apport, that's why we have
package hooks.
** Changed in: apport (Ubuntu Hardy)
Status: Confirmed => Invalid
--
tracker-extract crashed
https://bugs.launchpad.net/bugs/198863
You received this bug notification because you are a member of Ubuntu
Bug
** Changed in: apport (Ubuntu)
Importance: Undecided => Low
Status: New => Confirmed
--
tracker-extract crashed
https://bugs.launchpad.net/bugs/198863
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Very well, I've added the package for apport, let's see what the apport
people say, I really hope they won't bounce back the ball to you in an
endless loop.
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
ubuntu hardy heron alpha 5 updated
Savvas Radević escribió:
> Well it could be a silent crash, there should be no prompts from apport
> to report the bug :)
>
That should be a wishlist against apport ;) We're doing what apport
let's us do...
--
tracker-extract crashed
https://bugs.launchpad.net/bugs/198863
You received this bug
Plus, the first crash said that it is damaged and can't be reported,
hence I reported that it can't be reported
--
tracker-extract crashed
https://bugs.launchpad.net/bugs/198863
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Well it could be a silent crash, there should be no prompts from apport
to report the bug :)
--
tracker-extract crashed
https://bugs.launchpad.net/bugs/198863
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
As the message explains, crashes in tracker-extract are the consequence
of limiting its resources (cpu, memory...), so there's no need to file
those bugs.
Let me know if the wording in the message isn't clear or can be
improved.
** Changed in: tracker (Ubuntu)
Status: New => Invalid
--
t
Another crash followed, explaining that "The problem cannot be reported:
Crashes in tracker-extract are intended so that tracker-extract doesn't
consume many resources."
I can upload the crash report, but it's quite big, about 20mb, I've
archived it in case you need it
** Attachment added: "crash
** Attachment added: "crash-tracker-extract.png"
http://launchpadlibrarian.net/12446076/crash-tracker-extract.png
** Description changed:
ubuntu hardy heron alpha 5 updated
$ apt-cache policy tracker
tracker:
Installed: 0.6.6-0ubuntu1
Candidate: 0.6.6-0ubuntu1
Version tab
17 matches
Mail list logo
