First I’d like to say that just yesterday I upgraded my 11.4 to the new 12.1 and I really like the added polish. Very nice work and kudos to all who contributed to its development.
My question is this:
On start up, after the KDE desktop is loaded, I get an error involving Nepomuk that it could not initialize or (something). I followed the bug reporting instructions and created a new bug report account to help the developers on my end. However, I got an error saying that there was not enough information to send and I am missing the “bug report” files and to go to the repositories and download them. I saved the report file for sending later and looked for the additional files using all sorts of searches and I can’t seem to find what ones I need to install. I want to help out any way I can and I figured that sending in my reports with all pertinent information associated would be the first place to start.
Just looking for a little nudge in the right direction,
So generally, you don’t have to attach anything unless you want to. There are several information fields you must fill out in order for someone trying to understand the problem and can reproduce it. Be very kind, even though it may be hard to do so because many if not most of these people are working on the bugs on their own time and in any event you need to give then a good reason to investigate your problem request. My number one suggestion is to read through other bug reports to see what everyone else is doing and try to emulate it. I did find a helpful site on filing bug reports here:
Among other things, you’ll get this message (in fact, three similar notifications a few minutes after boot in oS 11.4) if Nepomuk’s semantic environment is disabled in system-settings>workspace search (or similar, I’m translating from portuguese). If so, it’s not an error, no need to report.
I disabled akonadi by editing the file “$HOME/.config/akonadi/akonadiserverrc” and changing the “StartServer=” line to “false” (was “true”). As far as I know, akonadi still starts, reads that config file, then goes away.
I installed via direct download through the terminal. I’ve been working out some bugs since then which are just minor irritations. I’ll go through the repository list again thanks. I will try the terminal commands as you have suggested and see what that turns up. I copied down the exact info for the nepomuk bug from re-booting.
Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault
[KCrash Handler] #6 0x00007fc2b138afda in ?? () from /usr/lib64/kde4/nepomukstorage.so #7 0x00007fc2b138b0fc in ?? () from /usr/lib64/kde4/nepomukstorage.so #8 0x00007fc2b138b1d9 in ?? () from /usr/lib64/kde4/nepomukstorage.so #9 0x00007fc2b114d8a7 in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib64/libsopranoserver.so.1 #10 0x00007fc2b1389dfc in ?? () from /usr/lib64/kde4/nepomukstorage.so #11 0x00007fc2b1389ea9 in ?? () from /usr/lib64/kde4/nepomukstorage.so #12 0x00007fc2bfd3b455 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #13 0x00007fc2bfd409f9 in QObject::~QObject() () from /usr/lib64/libQtCore.so.4 #14 0x00007fc2b1389113 in ?? () from /usr/lib64/kde4/nepomukstorage.so #15 0x00007fc2bfd3b455 in QObjectPrivate::deleteChildren() () from /usr/lib64/libQtCore.so.4 #16 0x00007fc2bfd409f9 in QObject::~QObject() () from /usr/lib64/libQtCore.so.4 #17 0x00000000004047f9 in _start ()
It’s going to depend on what software you use. I expect that kmail and Kontact both require akonadi to be running. I happen to not be using those, and I have not yet run into any problems with disabling akonadi.
However, I got an error saying that there was not enough information to send and I am missing the “bug report” files and to go to the repositories and download them.
If I understand correctly (I had a similar thing happen with KPolicy-Kit), what you are seeing is a bug reporting mechanism from within KDE, it sends the report directly to the upstream KDE developers.
What it needs is the appropriate symbolic debug info, and if you enable the debug repository (via YAST) for openSUSE 12.1 (while the reporting mechanism is still active) the reporting tool will automatically install the required debug packages so the symbolic debug info can be included in the report.
You will also be required to Register/Login to the KDE site (which is where I had trouble; their server was down).
Guess what I ended up doing? I re-installed the whole kabash from the disk iso. It’s like an entirely different build than the 11.4 upgrade from download. It’s MUCH faster and I have no errors at all. The entire file configuration is completely different. It’s working flawlessly now and I would have to suggest to others to go the same direction. Since I save everything to external drive, putting everything back after a fresh installation was rather painless.