This particular crash shouldn't be a problem in more recent versions of
Kubuntu.
** Changed in: strigi (Ubuntu)
Status: Confirmed => Fix Released
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification because you
semm to have this problem on kubuntu intrepid.
changing importance to: pain in the ass.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Don't use strigi on ubuntu. The backend, redland, is obsolete and won't
be change for intrepid for sesame2. And so strigi is taking forever to
index a large disk with a lot of cpu time...
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received
I've got a Core 2 Duo, and strigidaemon is eating 49% of system
resources (I'm guessing that means it's hanging one core completely).
What do I do? pdftotext is also zombie-fied.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bu
Careful
>From memory I tried uninstalling it and adept uninstalled my entire
kubuntu-desktop (ie lot's of *important* packages). If you do choose to
uninstall, make sure you click on the "Preview" button in Adept Manager
before you click on "Apply" so you can see which packages it's about ot
u
Same problem here + my strigi folder size is 3.6gb!!!
More here about fat strigi folder:
https://bugs.launchpad.net/ubuntu/+source/strigi/+bug/227280
Can i remove safely such a program that is eating my cpu, ram and home folder
usage?? I don't even use it.
Btw: Kubuntu 8.04 w/ 3.5.9 kde.
Still happening on Kubuntu hardy 8.04, running vanilla kde3.5. deamin
ois NOT indexing ATM
top:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
6211 ber 20 0 118m 64m 3312 S 51.9 12.9 52:28.66 strigidaemon
strigi:/status
Documents in queue 0
Documents indexed
Experiencing the same on Kubuntu 7.10.
Currently up to 6mins of near 100% cpu time on a core 2 duo system.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
it's still not working
I hate to kill the daemon everytime I boot my pc! Will there be a solution in
the near future?
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification because you are a member of Ubuntu
Bugs, which
In gutsy the daemon use 100% cpu after kde starts. Each time I have to go to
the web interface and click on STOP. Then the daemon pass stopping and the cpu
goes quiet.
strigi-daemon 0.5.6-0ubuntu1
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
Kubuntu 7.10 64 bit on Asus V1S. The same problem here , Strigi uses
between 50 and 100% on a Core 2 Duo. even though it says it is idling.
And it has been running for 5 workdays.
Please note this bug as well
https://bugs.launchpad.net/ubuntu/+source/strigi/+bug/157343.
--
strigidaemon causes 10
Sorry for comment spam, but here, an hour later, strigi went into idle
mode and has stayed there for 15 minutes, using 0 cpu time.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification because you are a member of Ubuntu
The daemon also responds to the Stop daemon button now.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
u
Behavior has changed on my system as of 10/16. Strigi no longer appears
to hang, it successfully indexes close to 40x more files than it did
previously (which I'm assuming is everything in the index directories) ,
and then goes into idling mode, and the CPU usage apparently goes to 0.
Then, randoml
My system has been running for seven hours now, and every three minutes
or so it suddenly goes into VERY heavy load (70% CPU; I've even seen
99%) while Strigi does... something.
I never seem to get more than one or two minutes of no load.
--
strigidaemon causes 100% CPU and crashes after a while
strigi 0.5.6-0ubuntu1, it is no longer crashing, but the cpu usage
during indexing bug is still there.
now i observe that strigi only uses 100% cpu when indexing, and then
drops back down once strigi:/status reports its idling. before high cpu
usage would continue even after indexing was complete.
The problem is still there with version 0.5.6-0ubuntu1. This bug renders
kubuntu unusable with laptops because it drains the battery.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification because you are a member of Ubu
For me it is not crashing after the update, but is is indexing even if its
status shows that it is idle and I am still able to click on Start Indexing.
Also it consumes 100% of my CPU while indexing.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
Upgraded strigi-daemon to 0.5.6-0ubuntu1. Strigi no longer takes up
100% CPU, instead it crashes a while after starting indexing. Basically
after I updated this morning, I deleted .strigi/ and tried to index
again. Strigi crashes continually after the first 200 documents
indexed.
--
strigidaem
For me, I have discovered that strigi crashes if it is hung in the way
described and start indexing is called. I attached a core file of that
crash in the hope it will be useful.
** Attachment added: "core"
http://launchpadlibrarian.net/9891409/core
--
strigidaemon causes 100% CPU and crashes
I believe that there is just a bug. The CPU load is too high for an
indexing daemon. If you compare it with Tracker or Google desktop on the
same PC you will see that these ones are much more lighter.
Hope that the stable release of Kubuntu 7.10 fixes it. Anyway tracker
works goot, aso in KDE.
--
I guess that it is because it is indexing information, then when you
search through this applet, then it will show that required information,
the only you can do is stop the daemon, by killing the process, then
open the configuration, preferences and stop daemon, it had works fine
for me until now
Same behaviour in strigi-daemon 0.5.5-2ubuntu2 :(
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
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-
Well, even as "non-coders" we can all help fix this bug by writing the
most detailed accurate bug descriptions we can, providing hardware and
package info on our systems to find commonalities and including
appropriate logs / crash reports / and other output info.
For example, is this a Kubuntu onl
Paul,
kubuntu-desktop only recomends strigi related stuff, so you can
easily/safely un-install. (see above:
https://bugs.launchpad.net/ubuntu/+source/strigi/+bug/128876/comments/10
and http://packages.ubuntu.com/gutsy/metapackages/kubuntu-desktop)
The Right Thing™ would be to try and fix this bug
Mem: 1035636k total, 1014148k used,21488k free,97120k buffers
Swap: 1951888k total,34692k used, 1917196k free, 569292k cached
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
6420 thorns18 0 52600 8624 3092 S 30.0 0.8 22:09.58 strigidaemon
6814 thorns
One of my systems reports this when strigidaemon is started from CLI:
WARNING: field "TODO_tracknumber" is not define in .fieldproperties ontology
database.
WARNING: field "TODO_discnumber" is not define in .fieldproperties ontology
database.
Segmentation fault.
--
strigidaemon causes 100% CPU
Worth considering... (from the comment at
https://bugs.launchpad.net/ubuntu/+source/strigi/+bug/137753/comments/2)
"by default, strigi also indexes ~/.strigi..."
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification be
Same here, with the upgrade from feisty to gutsy.
Originally, I thought that poppler-utils specifically pdftotext was causing the
100% CPU usage. But after a second look, I don't think that this is the
problem.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.ne
Upgrade from feisty to gutsy on my main machine and I have the same
problem using strigi...
100% CPU Usage until I press the "Start indexing" that crashes it.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification becau
You killed the processor!? What with, an axe??
On 28/09/2007, bugmenot <[EMAIL PROTECTED]> wrote:
>
> I can confirm I am having this same problem as of 20070928 using Tribe
> 5(?) of Kubuntu. The fan was running all the time and the processor was
> maxed. When I looked to see what was pushing the
I can confirm I am having this same problem as of 20070928 using Tribe
5(?) of Kubuntu. The fan was running all the time and the processor was
maxed. When I looked to see what was pushing the processor so hard I
found that strigidaemon was using over 98% of the CPU. I killed the
processor and thing
Same for me:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
25341 martin18 0 105m 28m 3288 S 99 1.4 141:28.03 strigidaemon
14287 root 16 0 182m 110m 13m S0 5.6 1:32.07 Xorg
I was surprised about the heat of my CPU, well strigi explains
everything. I w
I am also seeing this problem on the current Gutsy snapshot.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing l
Basically the same here.
I just updated all packages today on my Kubuntu Gutsy and now I'm
getting 60-90% CPU usage pretty much full time, even though daemon is
reported as "Idling". Killing the strigidaemon and strigiapplet
processes speeds things up dramatically.
Documents in queue 0
Docum
I observe the same behavior on my desktop computer that has lots of
files, although, on my laptop, with few files, strigi starts up, and
stays using 0% CPU.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification because
Strigi packages are only Recommended by kubuntu-desktop, therefore you
can safely remove them without removing kubuntu-desktop package.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
You received this bug notification because you are a member of U
I can confirm this too except strigidaemon does not crash on my PC, just
keeps running and using all my CPU for as long as forever :-/
It is though configurable through strigi:/ and restartable, after which
it stops using the CPU at 100%.
I can't remove (since I don't really need such an applicat
I have the same problem here just after boot.
I did an strace as Guillaume mentioned before and I get the following output...
[EMAIL PROTECTED]:~$ strace -p `pidof strigidaemon`
Process 5309 attached - interrupt to quit
accept(7, {sa_family=AF_FILE, path="��▒+"}, [2]) = 8
recvfrom(8, "g", 1, 0, NU
Gillaume, I don't think such a shite CPU exists. Konq and KMail may very
well appear to have frozen (and recover suddenly when strigidaemon dies)
if the strigidaemon is drinking all the juice of the system.
In my case it doesn't, however this issue is a pain in the arse I have
to say, I need to ki
About Fred comments:
Kmail and Konqueror both work fine here. Perhaps this is related to your CPU
power, which can't handle both a 100% eating strigidaemon and the other apps
(but I don't know which CPU you're using, so this is just an idea).
In my case I use a rather powerfull CPU with 2 cores
Same here on Gutsy.
Strigi successfully indexed all my files but keeps eating 100% CPU for some
minutes, while strigi:/status report the daemon as idle:
Documents in queue 0
Documents indexed 27934
Index size 359 MB
Status idling
Unique words indexed 198042
if I strace the process w
I can confirm this on Tribe5. Strigi also seems to crash konqueror and kmail.
It starts up at boot with no way to edit this behavior.
At least removing strigi lets Konqueror and kmail behave stabily.
--
strigidaemon causes 100% CPU and crashes after a while
https://bugs.launchpad.net/bugs/128876
The same for Gutsy Tribe 5 on x86 (generic kernel). Strigi has three
processes (double core Intel M CPU), one is quite nice (19), the other
two have normal priority. Two of the processes just eat all power. None
seems to crash.
--
strigidaemon causes 100% CPU and crashes after a while
https://bug
the same here, on amd64 kubuntu gutsy.
top command shows 190 %CPU for strigidaemon and both cpu cores are 0.0%id
thats while indexing, if i leave the daemon doing nothing it takes 50% of each
cpu cores.
as you can imagine while indexing the cpu gets really hot.
--
strigidaemon causes 100% CPU an
I can confirm this on my system. Will try to build debug version and try
to reproduce.
** Changed in: strigi (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Luka Renko
Status: New => In Progress
--
strigidaemon causes 100% CPU and crashes after a while
https://bug
** Description changed:
Hi!
on my just installed kubuntu-tribe3 i noticed that the cpu-fan was running
all the time. Top showed me that strigidaemon was running at nearly 100% all
the time. strigi:/ showed me the following:
--
47 matches
Mail list logo