| Summary: | Nepomuk crash while browsing with Iceweasel | ||
|---|---|---|---|
| Product: | [Unmaintained] nepomuk | Reporter: | David Eccles (gringer) <kde> |
| Component: | general | Assignee: | Sebastian Trueg <sebastian> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | georges, ian.hollander+kdebugs, john_moore, KaiUweBroulik2, kde, kde, manuavazquez, marsu1, mckisick, me, Sroka.Steven, stefano.marelli, sven, t.kijas, tevaughan, trueg, ulilicht, ve.ru, xcentricdave |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
David Eccles (gringer)
2011-09-16 08:15:20 UTC
Created attachment 63681 [details]
New crash information added by DrKonqi
nepomukservicestub (0.2) on KDE Platform 4.6.5 (4.6.5) using Qt 4.7.3
- What I was doing when the application crashed:
Same programs running as previously, browsing yeast database using Iceweasel
-- Backtrace (Reduced):
#8 0x00007fa67f356dbb in __libc_message (do_abort=<optimized out>, fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
#9 0x00007fa67f360606 in malloc_printerr (action=3, str=0x7fa67f4374e8 "malloc(): memory corruption (fast)", ptr=<optimized out>) at malloc.c:6283
#10 0x00007fa67f363ee8 in _int_malloc (av=0x7fa67f66de60, bytes=<optimized out>) at malloc.c:4308
[...]
#12 0x00007fa6817d3be5 in QString::QString (this=0x7fa666fca9d0, size=10) at tools/qstring.cpp:1099
#13 0x00007fa6818ac978 in QUtf8::convertToUnicode (chars=<optimized out>, len=9, state=0x0) at codecs/qutfcodec.cpp:183
Can this be reproduced with KDE 4.7? *** Bug 281868 has been marked as a duplicate of this bug. *** *** Bug 280203 has been marked as a duplicate of this bug. *** *** Bug 279927 has been marked as a duplicate of this bug. *** *** Bug 278789 has been marked as a duplicate of this bug. *** *** Bug 277419 has been marked as a duplicate of this bug. *** *** Bug 276903 has been marked as a duplicate of this bug. *** > Can this be reproduced with KDE 4.7?
I don't know. I don't have the luxury of trying this until Debian allows newer versions into their repositories.
I'm no longer getting crashes since upgrading a couple of days ago. Here are the Debian versions of packages on my computer now that I expect might be relevant:
$ aptitude show libnepomuk4 libqtcore4 kde-full | grep '\(Package\|Version\)'
Package: libnepomuk4
Version: 4:4.6.5-2
Package: libqtcore4
Version: 4:4.7.3-8
Package: kde-full
Version: 5:70
*** Bug 276242 has been marked as a duplicate of this bug. *** *** Bug 278520 has been marked as a duplicate of this bug. *** *** Bug 276125 has been marked as a duplicate of this bug. *** *** Bug 275553 has been marked as a duplicate of this bug. *** *** Bug 275169 has been marked as a duplicate of this bug. *** *** Bug 270643 has been marked as a duplicate of this bug. *** *** Bug 269135 has been marked as a duplicate of this bug. *** *** Bug 281587 has been marked as a duplicate of this bug. *** *** Bug 276373 has been marked as a duplicate of this bug. *** I no longer use Linux, and so no longer need to be informed of progress on this problem. More crashes, this time using a vesa Xorg driver -- I previously thought the bugs might have something to do with using the non-free nvidia drivers (this was because loading eclipse and localc caused a Xorg reset), so I'm in the process of getting nouveau drivers for my video card. Same versions of packages as above in comment 9. (In reply to comment #20) > More crashes, this time using a vesa Xorg driver -- I previously thought the > bugs might have something to do with using the non-free nvidia drivers (this > was because loading eclipse and localc caused a Xorg reset), so I'm in the > process of getting nouveau drivers for my video card. Same versions of packages > as above in comment 9. this is still not KDE 4.7 I assume? On 23/09/11 11:23, Sebastian Trueg wrote:
>> Same versions of packages as above in comment 9.
> this is still not KDE 4.7 I assume?
Yes, I believe so. The version numbering for KDE in Debian is a little
odd, but the versions for most KDE things seem to match the platform
version in the initial bug report.
*** Bug 282724 has been marked as a duplicate of this bug. *** I just wanted to add, that I get a segmentation fault of nepomukservicestub since I added folders which reside in TrueCrypt containers to the search list of strigi. No idea whether this is relevant, but this might be: 1.: I am using KDE-4.7.1 with QT-4.7.4 2.: Everything on my system is built with -ggdb, but drkonqi can't get a backtrace. Nothing. I have already cleaned the nepomuk database files in ~/.kde4/share/apps/nepomuk/repository/main/data/virtuosobackend/, but a few seconds after KDE starts up, the segfault is back. Hopefully I succeed in finding out why drkonqi all of a sudden is free of any backtrace, and then I'll report back. Five minutes ago I wanted to report that the problem is fixed by deleting the virtuoso data files again, upgrading strigi to version 0.7.6 and rebooting the machine. It started up fine, no crash in sight, nepomuk/strigi/akonadi working like a charm (unless you count in the fact that akonadi_nepomu_email_feeder ate up nearly 6 GB of memory, see Bug 279800). But now, after another restart, I get the segmentation fault again after starting Akonadi Server. All that drKonqi could produce was this: ------------ Application: nepomukservicestub (0.2) KDE Platform Version: 4.7.1 (4.7.1) (Compiled from sources) Qt Version: 4.7.4 Operating System: Linux 3.0.4-gentoo x86_64 -- Information about the crash: <Erklären Sie bitte ganz genau, was Sie machten, als das Programm abstürzte.> The crash can be reproduced some of the time. -- Backtrace: A useful backtrace could not be generated An https://bugs.kde.org berichten ------------ The "Backtrace" is nothing but this line: ------------ Application: Nepomuk-Dienst (nepomukservicestub), signal: Segmentation fault ------------ I am completely at sea how to generate a useful Backtrace. :-( ====== One thing is odd: There _are_ instances of nepomukservicestub currently running. But which should be there now and isn't? ------------ sed@sed-notebook ~ $ ps xfa | grep nepomuk | grep -v grep 4573 ? Sl 0:00 /usr/bin/nepomukserver 4590 ? SNl 0:03 \_ /usr/bin/nepomukservicestub nepomukstorage 4838 ? SN 0:00 \_ /usr/bin/nepomukservicestub nepomukbackupsync 4846 ? SNl 0:00 \_ /usr/bin/nepomukservicestub nepomukfilewatch 4847 ? SN 0:00 \_ /usr/bin/nepomukservicestub nepomukqueryservice 5144 ? SNl 0:01 \_ /usr/bin/nepomukservicestub nepomukstrigiservice 4668 ? S 0:00 /usr/bin/nepomukcontroller -session 10143143147fd000131711977700000042090027_1317131989_395876 5095 ? S 0:00 \_ /usr/bin/akonadi_nepomuk_calendar_feeder --identifier akonadi_nepomuk_calendar_feeder 5096 ? S 0:00 \_ /usr/bin/akonadi_nepomuk_contact_feeder --identifier akonadi_nepomuk_contact_feeder 5097 ? S 0:00 \_ /usr/bin/akonadi_nepomuk_email_feeder --identifier akonadi_nepomuk_email_feeder ------------ OH NO! I have posted in the wrong browser tab showing duplicate Bug 282724 ! Please forgive me posting again (and something that might be completely unrelated) but I have no idea whether comments can be "moved" or not. :-( I have seen something rather disturbing. In akonadiconsole I can see that my LDAP Adress book plugin no longer works (It did prior the last reboot) and states: "No KDE adress book plugin configured yet". Why is that? It _was_ configured and now it's gone. Further, while "Nepomuk Contact Feeder" is "Ready to index data", the "Nepomuk EMail Feeder" reports: "System busy, indexing suspended." (My system is idle.) I have now reconfigured the LDAP adress book, and it is working. And after starting kontact (which puts my E-Mail-Agents into online mode) the Nepomuk EMail Feeder switched to "Ready". Most probably this has nothing to do with the crash reported, but I thought better report this oddity, no matter how far fetched a connection seems, than ignoring possibly helpful information. ;-) *** Bug 277513 has been marked as a duplicate of this bug. *** Closing this as a duplicate of bug 275880 since I am fairly certain that it can be the only source of the problem. Hopefully the patch I posted there does also solve this crash. *** This bug has been marked as a duplicate of bug 275880 *** |