301453 2012-06-08 15:42:05 +0000 nepomuk regression just after 4.8.3. 2013-02-02 14:54:16 +0000 1 1 10 Unmaintained nepomuk general 4.8 Arch Linux Linux RESOLVED FIXED regression NOR critical --- 277705 1 ht990332 trueg aacid alejandronova alien cfeck desintegr dilfridge eli eric.lemoussu franz.trischberger ht990332 hubn3rd korgens manfred.kitzbichler me modax.reg moro.engelhardt rdieter red4fireluv04 scarpino than wikt.sztw+kdebugs zerg 40 oldest_to_newest 1263588 0 ht990332 2012-06-08 15:42:05 +0000 this regessed just after the 29th of april 2012 in KDE/4.8 branch definitely on the 29th or 30th of april in kdelibs. downstream bug report. https://bugs.archlinux.org/30190 many applications will crash if nempomuk/strigi is enabled. kmail will crash if a message is selected. Note: This was not a problem in KDE 4.8.3 but regressed after the release and is still in KDE 4.8.4 Reproducible: Always Steps to Reproduce: enable nepomuk/strigi desktop search. open kmail and select an email. Actual Results: nepomuk feeder process crashes. and kmail goes down too forum post. https://bbs.archlinux.org/viewtopic.php?id=142935 1263708 1 wikt.sztw+kdebugs 2012-06-08 22:14:09 +0000 When I create two new folders, and try to move first into second, dolphin crashes. 1263779 2 ht990332 2012-06-09 08:14:42 +0000 reverting http://quickgit.kde.org/index.php?p=kdelibs.git&a=commit&h=a43824a200ed76cef48a90bd3aee8547698b7c91 fixes it for me 1263836 3 cfeck 2012-06-09 11:45:57 +0000 Raising severity, as it affects multiple applications and default setting is "nepomuk enabled". 1263884 4 aacid 2012-06-09 13:41:58 +0000 There is definitely something weird going on. If i add Q_ASSERT(!m_factories.hasLocalData()); to the KSycocaFactorySingleton constructor it asserts when nepomukserver is running but works correctly when nepomukserver is not running. Something is writing way off memory maybe? Couldn't find anything usefuf with valgrind 1263890 5 korgens 2012-06-09 13:53:17 +0000 The error in my system happens when I try to start kmail. It always crashes. Just after that, if I click on nepomuk notification icon it also crashes. Here is the bare output: $ kmail QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kmail2(1435)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: kmail2(1435)/kdepimlibs (mailtransport): Could not access Outbox. kmail2(1435)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory! QObject: Cannot create children for a parent that is in a different thread. (Parent is Nepomuk::ResourceManager(0x207f6e0), parent's thread is QThread(0x1be8260), current thread is QThread(0x21df420) *** KMail got signal 11 (Exiting) *** Dead letters dumped. 1263892 6 alejandronova 2012-06-09 13:59:47 +0000 This bug, in fact, is so severe that it would merit a 4.8.4.1 release. The following apps are affected. - Gwenview: Instant crash while trying to open a folder. - Dolphin: If you open the Information panel when Nepomuk is enabled, nothing appears. If you enabled Dolphin tooltips, Dolphin will crash. - KMail: It will crash instantly when you try to Reply To a mail. - Even Danbooru Client crashes while trying to save images (this is to certify that this is a Nepomuk bug). This affects ONLY KDE 4.8.4. This doesn't affect KDE 4.8.3. Also, KDE 4.8.80 doesn't seem to be affected either. 1264085 7 franz.trischberger 2012-06-10 07:08:47 +0000 This dolphin bug was reported yesterday: https://bugs.kde.org/show_bug.cgi?id=301499 It's marked as a Duplicate, the original bug is quite old, and it was caused by an old soprano-version. As the backtraces look quite similar, I thought that soprano could be the cause here, too. I am running latest stable (2.7.6), and get those crashes, too. So I upgraded to 2.7.56 (alpha? beta? don't know...) - and all crashes are gone! Everything just works! 1264104 8 scarpino 2012-06-10 08:09:35 +0000 Confirmed. Upgrading to soprano 2.7.56 on KDE 4.8.4 fixed the crash! 1264215 9 alejandronova 2012-06-10 13:43:38 +0000 There are no crashes here! But please, leave this open; we shouldn't depend on Soprano trunk if we are in the stable branch; if we do that, releases and branching don't make any sense. 1264222 10 aacid 2012-06-10 13:55:09 +0000 Yes, asking for a soprano increase from 4.8.3 to 4.8.4 is unacceptable. 1264359 11 colin.thomson 2012-06-10 21:24:49 +0000 I can confirm soprano-2.7.57 on 4.8.4 fixes the crash problems mentioned in this report on my Fedora17 box. 1264372 12 sait.a.umar 2012-06-10 21:36:54 +0000 There seems to be a discrepancy between the patch applied to nepomuk in the git and the kdelibs 4.8.4 source. I see the extra line below if ( forced || (!m_socketConnectFailed && !localSocketClient.isConnected()) ) { delete localSocketModel; localSocketModel = 0; localSocketClient.disconnect(); <======== THIS LINE IS EXTRA QString socketName = KGlobal::dirs()->locateLocal( "socket", "nepomuk-socket" ); If I remove that the crashes stop as well. The git patch that changed the first line above does not have that line in the patch! 1264437 13 eli 2012-06-11 04:31:11 +0000 (In reply to comment #11) > I can confirm soprano-2.7.57 on 4.8.4 fixes the crash problems mentioned in > this report on my Fedora17 box. Me too. 1264445 14 franz.trischberger 2012-06-11 06:07:17 +0000 (In reply to comment #12) > There seems to be a discrepancy between the patch applied to nepomuk in > the git and the kdelibs 4.8.4 source. > > I see the extra line below > localSocketClient.disconnect(); <======== THIS LINE IS EXTRA > If I remove that the crashes stop as well. The git patch that changed the > first line above does not have that line in the patch! That's just a workaround. Soprano::LocalSocketClient::disconnect() did not change between soprano-2.7.6 and latest betas. IMHO disconnect() is needed, because otherwise you will get an error in the case force is true. LocalSocketClient::connect() checks if there is a connection, yet, and if it won't reconnect but set an error (for both stable and beta soprano). The problems we are facing here are - as so often in the past - Qt Sockets. Trueg complained about it in the past and after 2.7.6 finally fixed it with the new Soprano::Socket-class. I extracted a pach from the diff between stable and beta, that simply replaces Qt Sockets with Soprano::Socket and installed 2.7.6 with it. It runs stable since about a day. 1265532 15 scarpino 2012-06-13 20:16:02 +0000 Up. Can you fix this (or confirm that reverting a43824a200ed76cef48a90bd3aee8547698b7c91 is ok) so people can use Nepomuk again? 1265592 16 me 2012-06-13 22:04:02 +0000 Reverted the following commits in KDE/4.8.x branch - commit 3708be2d09700b21f934c2129218e1c7ea44efdf Author: Sebastian Trueg <trueg@kde.org> Date: Mon Apr 30 16:34:21 2012 +0200 Disconnect before re-connecting. Soprano does not do that for us. commit a43824a200ed76cef48a90bd3aee8547698b7c91 Author: Sebastian Trueg <trueg@kde.org> Date: Mon Apr 30 14:51:10 2012 +0200 Always rec-connect if forced (ie. when Nepomuk server restarts) This should fix the issue. 1266477 17 me 2012-06-17 18:01:11 +0000 *** Bug 302039 has been marked as a duplicate of this bug. *** 1270763 18 agateau 2012-06-28 16:05:01 +0000 *** Bug 301790 has been marked as a duplicate of this bug. *** 1270765 19 agateau 2012-06-28 16:05:41 +0000 *** Bug 301474 has been marked as a duplicate of this bug. *** 1270768 20 agateau 2012-06-28 16:07:44 +0000 *** Bug 301685 has been marked as a duplicate of this bug. ***