Application: nepomukservicestub (0.2) KDE Platform Version: 4.7.2 (4.7.2) "release 9" Qt Version: 4.7.4 Operating System: Linux 2.6.37.6-0.7-desktop x86_64 Distribution: "openSUSE 11.4 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Nothing. Simply rebooted for the first time after upgrading to KDE 4.7.2. -- Backtrace: Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #6 0x00007f06fc829d82 in Nepomuk::Repository::close (this=0x7d69a0) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/repository.cpp:86 #7 0x00007f06fc829ead in Nepomuk::Repository::~Repository (this=0x7d69a0, __in_chrg=<value optimized out>) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/repository.cpp:75 #8 0x00007f06fc829f89 in Nepomuk::Repository::~Repository (this=0x7d69a0, __in_chrg=<value optimized out>) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/repository.cpp:76 #9 0x00007f06fc5b4d5f in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib64/libsopranoserver.so.1 #10 0x00007f06fc828c75 in Nepomuk::Core::~Core (this=0x6f7bc0, __in_chrg=<value optimized out>) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/nepomukcore.cpp:45 #11 0x00007f06fc828cf9 in Nepomuk::Core::~Core (this=0x6f7bc0, __in_chrg=<value optimized out>) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/nepomukcore.cpp:48 #12 0x00007f070b095e64 in QObjectPrivate::deleteChildren (this=0x7d8a80) at kernel/qobject.cpp:1964 #13 0x00007f070b09abb2 in QObject::~QObject (this=0x7d76f0, __in_chrg=<value optimized out>) at kernel/qobject.cpp:946 #14 0x00007f06fc827ee3 in ~Storage (this=<value optimized out>, __in_chrg=<value optimized out>) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/storage.cpp:54 #15 Nepomuk::Storage::~Storage (this=<value optimized out>, __in_chrg=<value optimized out>) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/storage.cpp:56 #16 0x00007f070b095e64 in QObjectPrivate::deleteChildren (this=0x6f7190) at kernel/qobject.cpp:1964 #17 0x00007f070b09abb2 in QObject::~QObject (this=0x6f4d10, __in_chrg=<value optimized out>) at kernel/qobject.cpp:946 #18 0x00000000004048d9 in Nepomuk::ServiceControl::~ServiceControl (this=0x6f4d10, __in_chrg=<value optimized out>) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/servicestub/servicecontrol.cpp:39 #19 0x00007f070b095e64 in QObjectPrivate::deleteChildren (this=0x62b870) at kernel/qobject.cpp:1964 #20 0x00007f070b09abb2 in QObject::~QObject (this=0x7fffc668ee50, __in_chrg=<value optimized out>) at kernel/qobject.cpp:946 #21 0x00007f07091a7e63 in QApplication::~QApplication (this=0x7fffc668ee50, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1088 #22 0x00000000004040a4 in main (argc=36, argv=0x7fffc668f298) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/servicestub/main.cpp:102 Possible duplicates by query: bug 271726, bug 270804, bug 270745, bug 270427, bug 270334. Reported using DrKonqi
Sorry about that. Already fixed.
*** Bug 283759 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > Sorry about that. Already fixed. In which version will the fix be available? 4.7.3?
(In reply to comment #3) > (In reply to comment #1) > > Sorry about that. Already fixed. > > In which version will the fix be available? 4.7.3? Yes, as this bug reports states in 4.7.3. However, I also posted the fix to the packagers list hoping that distributions will provide updated packages soon.
*** Bug 284074 has been marked as a duplicate of this bug. ***
*** Bug 284149 has been marked as a duplicate of this bug. ***
*** Bug 284229 has been marked as a duplicate of this bug. ***
*** Bug 284278 has been marked as a duplicate of this bug. ***
*** Bug 284373 has been marked as a duplicate of this bug. ***
*** Bug 284500 has been marked as a duplicate of this bug. ***
*** Bug 284518 has been marked as a duplicate of this bug. ***
*** Bug 284645 has been marked as a duplicate of this bug. ***
*** Bug 284647 has been marked as a duplicate of this bug. ***
*** Bug 284674 has been marked as a duplicate of this bug. ***
*** Bug 284679 has been marked as a duplicate of this bug. ***
*** Bug 284908 has been marked as a duplicate of this bug. ***
*** Bug 284906 has been marked as a duplicate of this bug. ***
*** Bug 284942 has been marked as a duplicate of this bug. ***
*** Bug 284956 has been marked as a duplicate of this bug. ***
*** Bug 284960 has been marked as a duplicate of this bug. ***
*** Bug 284965 has been marked as a duplicate of this bug. ***
*** Bug 284992 has been marked as a duplicate of this bug. ***
*** Bug 285044 has been marked as a duplicate of this bug. ***
Created attachment 64969 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: - Fresh start-up - Only desktop widgets and tray services are loaded. -- Backtrace (Reduced): #7 0xb3a2cecc in Nepomuk::Repository::close (this=0xa14e5d8) at ../../../../nepomuk/services/storage/repository.cpp:86 #8 0xb3a2d01c in Nepomuk::Repository::~Repository (this=0xa14e5d8, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:75 #9 0xb3a2d122 in Nepomuk::Repository::~Repository (this=0xa14e5d8, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:76 #10 0xb39d4aaf in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #11 0xb3a2b920 in Nepomuk::Core::~Core (this=0xa14fa78, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
*** Bug 285239 has been marked as a duplicate of this bug. ***
*** Bug 285241 has been marked as a duplicate of this bug. ***
*** Bug 285220 has been marked as a duplicate of this bug. ***
*** Bug 285183 has been marked as a duplicate of this bug. ***
*** Bug 285248 has been marked as a duplicate of this bug. ***
*** Bug 285334 has been marked as a duplicate of this bug. ***
*** Bug 285344 has been marked as a duplicate of this bug. ***
*** Bug 285371 has been marked as a duplicate of this bug. ***
*** Bug 285379 has been marked as a duplicate of this bug. ***
*** Bug 285407 has been marked as a duplicate of this bug. ***
*** Bug 285443 has been marked as a duplicate of this bug. ***
*** Bug 285452 has been marked as a duplicate of this bug. ***
*** Bug 285569 has been marked as a duplicate of this bug. ***
*** Bug 285582 has been marked as a duplicate of this bug. ***
*** Bug 285585 has been marked as a duplicate of this bug. ***
will it be possible for normal user to apply the patch manually? if yes, can you please provide the patch detail?
*** Bug 285612 has been marked as a duplicate of this bug. ***
(In reply to comment #40) > will it be possible for normal user to apply the patch manually? > if yes, can you please provide the patch detail? 4.7.3 has been released. :)
*** Bug 285619 has been marked as a duplicate of this bug. ***
*** Bug 285870 has been marked as a duplicate of this bug. ***
(In reply to comment #42) > (In reply to comment #40) > > will it be possible for normal user to apply the patch manually? > > if yes, can you please provide the patch detail? > > 4.7.3 has been released. :) 4.7.3 is no better than 4.7.2 in this respect. https://bugs.kde.org/show_bug.cgi?id=285789
Thank you very much, I am waiting for people to put the link openSUSE KDE 4.7.3 update in the URL of the new version. Nacho. El 07/11/11 00:08, Vadym Krevs escribió: > https://bugs.kde.org/show_bug.cgi?id=283604 > > > > > > --- Comment #45 from Vadym Krevs <vkrevs yahoo com> 2011-11-06 23:08:31 --- > (In reply to comment #42) >> (In reply to comment #40) >>> will it be possible for normal user to apply the patch manually? >>> if yes, can you please provide the patch detail? >> 4.7.3 has been released. :) > 4.7.3 is no better than 4.7.2 in this respect. > https://bugs.kde.org/show_bug.cgi?id=285789 >
Thank you very much, I am waiting for people to put the link openSUSE KDE 4.7.3 update in the URL of the new version. Nacho. El 06/11/11 21:35, Lamarque V. Souza escribió: > https://bugs.kde.org/show_bug.cgi?id=283604 > > > Lamarque V. Souza <lamarque@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |bbfk@gmx.net > > > > > --- Comment #44 from Lamarque V. Souza <lamarque kde org> 2011-11-06 20:35:34 --- > *** Bug 285870 has been marked as a duplicate of this bug. *** >
@Sebastian people are still complaining about this bug even though I added a branch diff to our 4.7.2 packages on October 19. Can you point me to the git commit fixing this so I know we have it?
The new reports may be https://bugs.kde.org/show_bug.cgi?id=285789
I have upgrade to KDE 4.7.3, but then also itś crashing, somewhere I have seen that this bug will be fixed in 4.7.4, can we apply this patch manually?
On 15/11/11 09:29, Will Stephenson wrote: > https://bugs.kde.org/show_bug.cgi?id=283604 > > > > > > --- Comment #49 from Will Stephenson<wstephenson kde org> 2011-11-15 09:29:13 --- > The new reports may be https://bugs.kde.org/show_bug.cgi?id=285789 > A warning, check the neopmuk log file. mine reached 185GB and crashed my computer.
On 15/11/11 10:13, pinakvashi@gmail.com wrote: > https://bugs.kde.org/show_bug.cgi?id=283604 > > > > > > --- Comment #50 from<pinakvashi gmail com> 2011-11-15 10:13:11 --- > I have upgrade to KDE 4.7.3, but then also itś crashing, somewhere I have seen > that this bug will be fixed in 4.7.4, can we apply this patch manually? > check your neopmuk log file. mine reached 185 and crashed my computer.
*** Bug 286199 has been marked as a duplicate of this bug. ***
*** Bug 286210 has been marked as a duplicate of this bug. ***
*** Bug 286096 has been marked as a duplicate of this bug. ***
*** Bug 286547 has been marked as a duplicate of this bug. ***
*** Bug 286645 has been marked as a duplicate of this bug. ***
*** Bug 286902 has been marked as a duplicate of this bug. ***
*** Bug 287012 has been marked as a duplicate of this bug. ***
(In reply to comment #52) > On 15/11/11 10:13, pinakvashi@gmail.com wrote: > > https://bugs.kde.org/show_bug.cgi?id=283604 > > > > > > > > > > > > --- Comment #50 from<pinakvashi gmail com> 2011-11-15 10:13:11 --- > > I have upgrade to KDE 4.7.3, but then also itś crashing, somewhere I have seen > > that this bug will be fixed in 4.7.4, can we apply this patch manually? > > > check your neopmuk log file. mine reached 185 and crashed my computer. I have kept the quota on /var so itś not increasing beyond and deleting the old ones.
*** Bug 287080 has been marked as a duplicate of this bug. ***
*** Bug 287161 has been marked as a duplicate of this bug. ***
*** Bug 287208 has been marked as a duplicate of this bug. ***
@Sebastian Trueg: Please can you explicitly confirm the status of this bug? It reads at the top as FIXED, and you keep marking new reports as duplicates of this. However, the report clearly states that this is fixed in KDE 4.7.3, which is released. I have KDE 4.7.3 and I still have this bug, and I see that others do too. There was a previous statement that this would be fixed in 4.7.4, but I can't find that now, and 4.7.4 is still not out. So, is this bug fixed in 4.7.3? in which case shall I submit a new bug report since I have it on 4.7.3? Or do I need to wait for 4.7.4, and if so, what is the due date for that? Thanks!
(In reply to comment #64) > @Sebastian Trueg: > > Please can you explicitly confirm the status of this bug? It reads at the top > as FIXED, and you keep marking new reports as duplicates of this. However, the > report clearly states that this is fixed in KDE 4.7.3, which is released. I > have KDE 4.7.3 and I still have this bug, and I see that others do too. There > was a previous statement that this would be fixed in 4.7.4, but I can't find > that now, and 4.7.4 is still not out. > So, is this bug fixed in 4.7.3? in which case shall I submit a new bug report > since I have it on 4.7.3? Or do I need to wait for 4.7.4, and if so, what is > the due date for that? > > Thanks! You do not see this bug but bug 285789.
Thanks!
*** Bug 287438 has been marked as a duplicate of this bug. ***
*** Bug 287526 has been marked as a duplicate of this bug. ***
Created attachment 66127 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: - Unusual behavior I noticed: - Custom settings of the application: "Nepomuk crashed on first KDE startup after upgrade to 4.7.2" Note: The bug report's title is often written by its reporter and may not reflect the bug's nature, root cause or other visible symptoms you could use to compare to your crash. Please read the complete report and all the comments below. Note: This bug report has 52 duplicate reports. That means this is probably a common crash. Please consider only adding a comment or a note if you can provide new valuable information which was not already mentioned. Bug Report Status: Closed (Fixed in version "4.7.3") Affected Component: nepomuk (general) Description of the bug Application: nepomukservicestub (0.2) KDE Platform Version: 4.7.2 (4.7.2) "release 9" Qt Version: 4.7.4 Operating System: Linux 2.6.37.6-0.7-desktop x86_64 Distribution: "openSUSE 11.4 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Nothing. Simply rebooted for the first time after upgrading to KDE 4.7.2. -- Backtrace: Application: Nepomuk Service Stub (nepomukservicestub), signal: Segmentation fault 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [KCrash Handler] #6 0x00007f06fc829d82 in Nepomuk::Repository::close (this=0x7d69a0) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/repository.cpp:86 #7 0x00007f06fc829ead in Nepomuk::Repository::~Repository (this=0x7d69a0, __in_chrg=) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/repository.cpp:75 #8 0x00007f06fc829f89 in Nepomuk::Repository::~Repository (this=0x7d69a0, __in_chrg=) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/repository.cpp:76 #9 0x00007f06fc5b4d5f in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib64/libsopranoserver.so.1 #10 0x00007f06fc828c75 in Nepomuk::Core::~Core (this=0x6f7bc0, __in_chrg=) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/nepomukcore.cpp:45 #11 0x00007f06fc828cf9 in Nepomuk::Core::~Core (this=0x6f7bc0, __in_chrg=) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/nepomukcore.cpp:48 #12 0x00007f070b095e64 in QObjectPrivate::deleteChildren (this=0x7d8a80) at kernel/qobject.cpp:1964 #13 0x00007f070b09abb2 in QObject::~QObject (this=0x7d76f0, __in_chrg=) at kernel/qobject.cpp:946 #14 0x00007f06fc827ee3 in ~Storage (this=, __in_chrg=) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/storage.cpp:54 #15 Nepomuk::Storage::~Storage (this=, __in_chrg=) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/services/storage/storage.cpp:56 #16 0x00007f070b095e64 in QObjectPrivate::deleteChildren (this=0x6f7190) at kernel/qobject.cpp:1964 #17 0x00007f070b09abb2 in QObject::~QObject (this=0x6f4d10, __in_chrg=) at kernel/qobject.cpp:946 #18 0x00000000004048d9 in Nepomuk::ServiceControl::~ServiceControl (this=0x6f4d10, __in_chrg=) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/servicestub/servicecontrol.cpp:39 #19 0x00007f070b095e64 in QObjectPrivate::deleteChildren (this=0x62b870) at kernel/qobject.cpp:1964 #20 0x00007f070b09abb2 in QObject::~QObject (this=0x7fffc668ee50, __in_chrg=) at kernel/qobject.cpp:946 #21 0x00007f07091a7e63 in QApplication::~QApplication (this=0x7fffc668ee50, __in_chrg=) at kernel/qapplication.cpp:1088 #22 0x00000000004040a4 in main (argc=36, argv=0x7fffc668f298) at /usr/src/debug/kde-runtime-4.7.2/nepomuk/servicestub/main.cpp:102 Possible duplicates by query: bug 271726, bug 270804, bug 270745, bug 270427, bug 270334. Reported using DrKonqi Additional Comments Comment 1: Sorry about that. Already fixed. Comment 3: (In reply to comment #1) > Sorry about that. Already fixed. In which version will the fix be available? 4.7.3? Comment 4: (In reply to comment #3) > (In reply to comment #1) > > Sorry about that. Already fixed. > > In which version will the fix be available? 4.7.3? Yes, as this bug reports states in 4.7.3. However, I also posted the fix to the packagers list hoping that distributions will provide updated packages soon. Comment 24: Created an attachment (id=64969) New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: - Fresh start-up - Only desktop widgets and tray services are loaded. -- Backtrace (Reduced): #7 0xb3a2cecc in Nepomuk::Repository::close (this=0xa14e5d8) at ../../../../nepomuk/services/storage/repository.cpp:86 #8 0xb3a2d01c in Nepomuk::Repository::~Repository (this=0xa14e5d8, __in_chrg=) at ../../../../nepomuk/services/storage/repository.cpp:75 #9 0xb3a2d122 in Nepomuk::Repository::~Repository (this=0xa14e5d8, __in_chrg=) at ../../../../nepomuk/services/storage/repository.cpp:76 #10 0xb39d4aaf in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #11 0xb3a2b920 in Nepomuk::Core::~Core (this=0xa14fa78, __in_chrg=) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45 Comment 40: will it be possible for normal user to apply the patch manually? if yes, can you please provide the patch detail? Comment 42: (In reply to comment #40) > will it be possible for normal user to apply the patch manually? > if yes, can you please provide the patch detail? 4.7.3 has been released. :) Comment 45: (In reply to comment #42) > (In reply to comment #40) > > will it be possible for normal user to apply the patch manually? > > if yes, can you please provide the patch detail? > > 4.7.3 has been released. :) 4.7.3 is no better than 4.7.2 in this respect. https://bugs.kde.org/show_bug.cgi?id=285789 Comment 46: Thank you very much, I am waiting for people to put the link openSUSE KDE 4.7.3 update in the URL of the new version. Nacho. El 07/11/11 00:08, Vadym Krevs escribió: > https://bugs.kde.org/show_bug.cgi?id=283604 > > > > > > --- Comment #45 from Vadym Krevs 2011-11-06 23:08:31 --- > (In reply to comment #42) >> (In reply to comment #40) >>> will it be possible for normal user to apply the patch manually? >>> if yes, can you please provide the patch detail? >> 4.7.3 has been released. :) > 4.7.3 is no better than 4.7.2 in this respect. > https://bugs.kde.org/show_bug.cgi?id=285789 > Comment 48: @Sebastian people are still complaining about this bug even though I added a branch diff to our 4.7.2 packages on October 19. Can you point me to the git commit fixing this so I know we have it? Comment 49: The new reports may be https://bugs.kde.org/show_bug.cgi?id=285789 Comment 50: I have upgrade to KDE 4.7.3, but then also itś crashing, somewhere I have seen that this bug will be fixed in 4.7.4, can we apply this patch manually? Comment 51: On 15/11/11 09:29, Will Stephenson wrote: > https://bugs.kde.org/show_bug.cgi?id=283604 > > > > > > --- Comment #49 from Will Stephenson 2011-11-15 09:29:13 --- > The new reports may be https://bugs.kde.org/show_bug.cgi?id=285789 > A warning, check the neopmuk log file. mine reached 185GB and crashed my computer. Comment 52: On 15/11/11 10:13, pinakvashi@gmail.com wrote: > https://bugs.kde.org/show_bug.cgi?id=283604 > > > > > > --- Comment #50 from 2011-11-15 10:13:11 --- > I have upgrade to KDE 4.7.3, but then also itś crashing, somewhere I have seen > that this bug will be fixed in 4.7.4, can we apply this patch manually? > check your neopmuk log file. mine reached 185 and crashed my computer. Comment 60: (In reply to comment #52) > On 15/11/11 10:13, pinakvashi@gmail.com wrote: > > https://bugs.kde.org/show_bug.cgi?id=283604 > > > > > > > > > > > > --- Comment #50 from 2011-11-15 10:13:11 --- > > I have upgrade to KDE 4.7.3, but then also itś crashing, somewhere I have seen > > that this bug will be fixed in 4.7.4, can we apply this patch manually? > > > check your neopmuk log file. mine reached 185 and crashed my computer. I have kept the quota on /var so itś not increasing beyond and deleting the old ones. Comment 64: @Sebastian Trueg: Please can you explicitly confirm the status of this bug? It reads at the top as FIXED, and you keep marking new reports as duplicates of this. However, the report clearly states that this is fixed in KDE 4.7.3, which is released. I have KDE 4.7.3 and I still have this bug, and I see that others do too. There was a previous statement that this would be fixed in 4.7.4, but I can't find that now, and 4.7.4 is still not out. So, is this bug fixed in 4.7.3? in which case shall I submit a new bug report since I have it on 4.7.3? Or do I need to wait for 4.7.4, and if so, what is the due date for that? Thanks! Comment 65: (In reply to comment #64) > @Sebastian Trueg: > > Please can you explicitly confirm the status of this bug? It reads at the top > as FIXED, and you keep marking new reports as duplicates of this. However, the > report clearly states that this is fixed in KDE 4.7.3, which is released. I > have KDE 4.7.3 and I still have this bug, and I see that others do too. There > was a previous statement that this would be fixed in 4.7.4, but I can't find > that now, and 4.7.4 is still not out. > So, is this bug fixed in 4.7.3? in which case shall I submit a new bug report > since I have it on 4.7.3? Or do I need to wait for 4.7.4, and if so, what is > the due date for that? > > Thanks! You do not see this bug but bug 285789. Comment 66: Thanks! -- Backtrace (Reduced): #7 0x051a2ec7 in Nepomuk::Repository::close (this=0x93072d0) at ../../../../nepomuk/services/storage/repository.cpp:86 #8 0x051a301c in Nepomuk::Repository::~Repository (this=0x93072d0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:75 #9 0x051a3122 in Nepomuk::Repository::~Repository (this=0x93072d0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:76 #10 0x058f1aaf in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #11 0x051a1920 in Nepomuk::Core::~Core (this=0x9307100, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
*** Bug 287732 has been marked as a duplicate of this bug. ***
*** Bug 287976 has been marked as a duplicate of this bug. ***
*** Bug 288024 has been marked as a duplicate of this bug. ***
*** Bug 288110 has been marked as a duplicate of this bug. ***
*** Bug 288176 has been marked as a duplicate of this bug. ***
*** Bug 288247 has been marked as a duplicate of this bug. ***
*** Bug 288387 has been marked as a duplicate of this bug. ***
Created attachment 66568 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4 - What I was doing when the application crashed: i restarted x server after upgrading to nightly update. and nepomuk crashed. i drive a 12.04 alpha kubuntu, with kde 4.7.4 -- Backtrace (Reduced): #7 0x021d3108 in Nepomuk::Repository::close (this=0x9b504b8) at ../../../../nepomuk/services/storage/repository.cpp:96 #8 0x021d324c in Nepomuk::Repository::~Repository (this=0x9b504b8, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:78 #9 0x021d3352 in Nepomuk::Repository::~Repository (this=0x9b504b8, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:79 #10 0x024eeaaf in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #11 0x021d1b00 in Nepomuk::Core::~Core (this=0x9b51888, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
*** Bug 288653 has been marked as a duplicate of this bug. ***
*** Bug 288623 has been marked as a duplicate of this bug. ***
Created attachment 66690 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: Everytime i restart the system it crashes. -- Backtrace (Reduced): #6 0x00007f956887fb8e in Nepomuk::Repository::close (this=0x1a477a0) at ../../../../nepomuk/services/storage/repository.cpp:86 #7 0x00007f956887fccc in Nepomuk::Repository::~Repository (this=0x1a477a0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:75 #8 0x00007f956887fda9 in Nepomuk::Repository::~Repository (this=0x1a477a0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:76 #9 0x00007f9568624ed7 in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #10 0x00007f956887e9fc in Nepomuk::Core::~Core (this=0x19e6f80, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
Created attachment 66705 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4 - What I was doing when the application crashed: Logging in KDE session. I'm using KDE 4.7.3, so it's still unsolved bug. -- Backtrace (Reduced): #6 0x00007f35d9cede4a in Nepomuk::Repository::close (this=0x1484810) at ../../../../nepomuk/services/storage/repository.cpp:96 #7 0x00007f35d9cedf6c in Nepomuk::Repository::~Repository (this=0x1484810, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:78 #8 0x00007f35d9cee049 in Nepomuk::Repository::~Repository (this=0x1484810, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:79 #9 0x00007f35d9ab4ed7 in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #10 0x00007f35d9cecc6c in Nepomuk::Core::~Core (this=0x140c290, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
*** Bug 288919 has been marked as a duplicate of this bug. ***
Created attachment 66754 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4 - What I was doing when the application crashed: nepomuk service stub crashes on startup constantlly. kde 4.7.3 kubuntu 12.04 kernel 3.2.0-4 -- Backtrace (Reduced): #7 0x041f8108 in Nepomuk::Repository::close (this=0x8c90d40) at ../../../../nepomuk/services/storage/repository.cpp:96 #8 0x041f824c in Nepomuk::Repository::~Repository (this=0x8c90d40, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:78 #9 0x041f8352 in Nepomuk::Repository::~Repository (this=0x8c90d40, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:79 #10 0x027b8aaf in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #11 0x041f6b00 in Nepomuk::Core::~Core (this=0x8c8da88, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
Created attachment 66829 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4 - What I was doing when the application crashed: Nothing. I installed KDE in ubentu 11.10. The first time I started KDE the application didn't crashed. Now, every time I start KDE it shows me this message. -- Backtrace (Reduced): #6 0x00007f225cac7ba5 in Nepomuk::Repository::close (this=0x166b450) at ../../../../nepomuk/services/storage/repository.cpp:89 #7 0x00007f225cac7ccc in Nepomuk::Repository::~Repository (this=0x166b450, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:75 #8 0x00007f225cac7da9 in Nepomuk::Repository::~Repository (this=0x166b450, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:76 #9 0x00007f225c88eed7 in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #10 0x00007f225cac69fc in Nepomuk::Core::~Core (this=0x16663d0, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
*** Bug 290219 has been marked as a duplicate of this bug. ***
*** Bug 290305 has been marked as a duplicate of this bug. ***
*** Bug 290293 has been marked as a duplicate of this bug. ***
*** Bug 290263 has been marked as a duplicate of this bug. ***
Created attachment 67673 [details] New crash information added by DrKonqi nepomukservicestub (0.2) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4 - What I was doing when the application crashed: starting up Oneiric 11.10 with KDE 4.7.3. crash occurs imediately desktop is loaded. -- Backtrace (Reduced): #7 0x01690108 in Nepomuk::Repository::close (this=0x88f74a8) at ../../../../nepomuk/services/storage/repository.cpp:96 #8 0x0169024c in Nepomuk::Repository::~Repository (this=0x88f74a8, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:78 #9 0x01690352 in Nepomuk::Repository::~Repository (this=0x88f74a8, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/repository.cpp:79 #10 0x039b1aaf in Soprano::Server::ServerCore::~ServerCore() () from /usr/lib/libsopranoserver.so.1 #11 0x0168eb00 in Nepomuk::Core::~Core (this=0x88f99a8, __in_chrg=<optimized out>) at ../../../../nepomuk/services/storage/nepomukcore.cpp:45
*** Bug 294422 has been marked as a duplicate of this bug. ***
*** Bug 297694 has been marked as a duplicate of this bug. ***
*** Bug 303588 has been marked as a duplicate of this bug. ***