Bug 315412

Summary:	Crashes as I open notably
Product:	[Unmaintained] nepomuk	Reporter:	Prashast Kumar Rajput <prashast.rocksss>
Component:	general	Assignee:	Nepomuk Bugs Coordination <nepomuk-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	nepomuk-bugs, thomas.friedrichsmeier
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Prashast Kumar Rajput 2013-02-18 20:18:36 UTC

Application: notably (0.3)
KDE Platform Version: 4.9.5 (Compiled from sources)
Qt Version: 4.8.4
Operating System: Linux 3.6.11-1.fc17.x86_64 x86_64
Distribution: "Fedora release 17 (Beefy Miracle)"

-- Information about the crash:
I installed it on my system successfully and then as i try to run, it crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: Notably (notably), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#5  0x000000368dd760f0 in KService::library() const () from /lib64/libkdecore.so.5
#6  0x000000368de136c2 in KPluginLoader::KPluginLoader(KService const&, KComponentData const&, QObject*) () from /lib64/libkdecore.so.5
#7  0x0000000000433572 in createInstance<Nepomuk2::AnnotationPlugin> (error=0x0, args=..., parent=0x0, parentWidget=0x0, this=0x0) at /usr/include/kde4/KDE/../kservice.h:556
#8  createInstance<Nepomuk2::AnnotationPlugin> (error=0x0, args=..., parent=0x0, this=0x0) at /usr/include/kde4/KDE/../kservice.h:536
#9  Annotator::Annotator (this=0x648700, parent=<optimized out>) at /home/experot/notably/src/annotation/annotator.cpp:33
#10 0x0000000000433700 in Annotator::instance () at /home/experot/notably/src/annotation/annotator.cpp:47
#11 0x000000000041c3f1 in NoteEdit::NoteEdit (this=0x136fe60, parent=<optimized out>) at /home/experot/notably/src/noteedit.cpp:69
#12 0x000000000041c05d in NoteWidget::NoteWidget (this=0x13885a0, parent=<optimized out>, f=...) at /home/experot/notably/src/notewidget.cpp:42
#13 0x000000000041b24a in MainWindow::setupGUI (this=this@entry=0x13896d0) at /home/experot/notably/src/mainwindow.cpp:80
#14 0x000000000041bbe2 in MainWindow::MainWindow (this=0x13896d0, parent=<optimized out>, f=...) at /home/experot/notably/src/mainwindow.cpp:64
#15 0x0000000000418846 in main (argc=1, argv=0x7fffe6724798) at /home/experot/notably/src/main.cpp:48

Reported using DrKonqi

Comment 1 Jekyll Wu 2013-02-19 02:37:13 UTC

> #5  0x000000368dd760f0 in KService::library() const () from /lib64/libkdecore.so.5
> #6  0x000000368de136c2 in KPluginLoader::KPluginLoader(KService const&, KComponentData const&, QObject*) () from /lib64/libkdecore.so.5

Please install debug symbols for kdelibs and provide a better backtrace .

Comment 2 Thomas Friedrichsmeier 2013-03-07 17:45:54 UTC

Hi!

Sorry, to intrude, I'm just a passer-by, who came here while looking for ideas on a similar backtrace in a totally different application. But:

> Please install debug symbols for kdelibs and provide a better backtrace .

What more are you hoping for? Full debug info is available for notably sources, and everything except the two latest calls. But if you will look at what leads up to this for a second, notice the value of "this" in

> createInstance<Nepomuk2::AnnotationPlugin> (error=0x0, args=..., parent=0x0, this=0x0) at /usr/include/kde4/KDE/../kservice.h:536

Now check lines 32 and 33 from annotator.cpp in the notably sources:

    KService::Ptr ptr = KService::serviceByDesktopName("personannotationplugin");
    static Nepomuk2::AnnotationPlugin* personPlugin = ptr->createInstance<Nepomuk2::AnnotationPlugin>();

So, quite simply "personannotationplugin" could not be found. Arguably the Annotator-ctor should check ptr. But in fact, quite likely the reporter simply forgot to 'make install' (to the correct prefix!).

Could you please do so, and check whether the problem persists, after that?

Comment 3 Andrew Crouthamel 2018-09-04 15:22:26 UTC

Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug. Development has moved to Baloo, please try again using the latest version and applications, and submit a new ticket for frameworks-baloo if you still have an issue. Thank you!