Version: unspecified (using KDE 4.4.5) OS: Linux The file .xsession-errors is in the $HOME directory within 2-3 days big up to 1.5 GB. This behavior occurs to me since the update to KDE to 4.4.5. Here is an example of errors in entry .xsession-errors which occurs very often. --- [/usr/bin/nepomukservicestub] "/usr/bin/nepomukservicestub(2966)" Error in thread 140103007581968 : "SQLExecDirect failed on query 'sparql prefix nco:<http://www.semanticdesktop.org/ontologies/2007/03/22/nco#>SELECT DISTINCT ?person WHERE { graph ?g { ?person a nco:PersonContact ; ?person <http://akonadi-project.org/ontologies/aneo#akonadiItemId> ?itemId . nco:hasEmailAddress ?email . ?email nco:emailAddress "root@redfox"^^<http://www.w3.org/2001/XMLSchema#string> . } } LIMIT 10' (iODBC Error: [OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SQ074: Line 1: SP030: SPARQL compiler, line 1: syntax error at '?itemId' before '.')" --- Reproducible: Always Steps to Reproduce: The error messages are produced continuously during a KDE session.
This is an akonadi problem. Some component does produce an invalid query which is performed over and over again. Also a flooded .xsession-error is something that should be solved independent of this bug, right?
Am Donnerstag 05 August 2010, 09:49:55 schrieb Sebastian Trueg: > https://bugs.kde.org/show_bug.cgi?id=246720 > > > Sebastian Trueg <trueg@k3b.org> changed: > > What |Removed |Added > --------------------------------------------------------------------------- > - CC| |kdepim-bugs@kde.org, > > | |trueg@k3b.org > > Component|general |general > Product|nepomuk |Akonadi > > > > > --- Comment #1 from Sebastian Trueg <trueg k3b org> 2010-08-05 09:49:54 > --- This is an akonadi problem. Some component does produce an invalid > query which is performed over and over again. > Also a flooded .xsession-error is something that should be solved > independent of this bug, right? Hallo Sebastian, ich weiß allerdings nicht wie ich den Fehler abstellen soll. Generell müsste der Loglevel kleiner sein, d.h. nicht soviele Meldungen dürften ins Errorlog schreiben. Es werden leider in der xession-errors auch sehr viele andere Ereignisse mit protokolliert. Ich habe das Wachstum der .xsession-errors über zwei Stunden vefolgt (Ausgabe von ls und wc). Wobei ich das exorbitante Wachstum noch nicht wieder reproduzieren konnte. [05-08-2010 08:50:01] -rw------- 1 michael michael 3772 Aug 5 08:49 /home/michael/.xsession-errors 33 .xsession-errors [05-08-2010 10:50:01] -rw------- 1 michael michael 682329 Aug 5 10:49 /home/michael/.xsession- errors 3874 .xsession-errors Grüße Michael Singer With Google translated: Hi Sebastian, I do however not know how to stop the errors. In general, the log level should be smaller, i.e. not as many messages should write in the Errorlog. There unfortunately are logged in with the xession-errors there are many other events. I have the growth of the xsession-errors followed over two hours (output of ls and wc). Although I could not reproduce the exorbitant growth again. [05-08-2010 08:50:01] -rw------- 1 michael michael 3772 Aug 5 08:49 /home/michael/.xsession-errors 33 .xsession-errors [05-08-2010 10:50:01] -rw------- 1 michael michael 682329 Aug 5 10:49 /home/michael/.xsession- errors 3874 .xsession-errors Regards Michael Singer
(In reply to comment #1) > This is an akonadi problem. Some component does produce an invalid query which > is performed over and over again. > Also a flooded .xsession-error is something that should be solved independent > of this bug, right? I agree on the last point, if it's not filled by akonadi debug, it could be something else. The fix should come from the distro side. See for example https://bugs.launchpad.net/bugs/60448 (yes, it's a few years old) There are two workarounds : * run kdebugdialog and check the "Disable all debug output" box, * Delete the .xsession-errors file after starting KDE if you don't need it a one line script in ~/.kde/Autostart should be enough (eg: sleep 10 && rm -f $HOME/.xsession-errors)
Is this bug still reproducable? I don't see what's wrong with the query though...
Hi Tobias, You can close the bug report, the error no longer occurs. Michael