Hi,
Apologies on starting a new thread..
I have been running some tests this afternoon after rebuilding/updating soprano to 2.7.57-1 from F18 src.rpm
Now the Kmail crash and others mentioned in bug #301453 on kde.bugs are not reproducible anymore here with nepomuk enabled. Gwenview being the other severe bug rendering it unusable with nepomuk enabled.
https://bugs.kde.org/show_bug.cgi?id=301453
I will continue testing but it does look promising :)
Colin
On Sunday 10 June 2012 18:27:06 Colin J Thomson wrote:
Hi,
Apologies on starting a new thread..
I have been running some tests this afternoon after rebuilding/updating soprano to 2.7.57-1 from F18 src.rpm
Now the Kmail crash and others mentioned in bug #301453 on kde.bugs are not reproducible anymore here with nepomuk enabled. Gwenview being the other severe bug rendering it unusable with nepomuk enabled.
https://bugs.kde.org/show_bug.cgi?id=301453
I will continue testing but it does look promising :)
Colin
Looking forward to it.
Thanks Collin
Eli
On Sunday 10 Jun 2012 20:39:33 Eli Wapniarski wrote:
On Sunday 10 June 2012 18:27:06 Colin J Thomson wrote:
Apologies on starting a new thread..
I have been running some tests this afternoon after rebuilding/updating soprano to 2.7.57-1 from F18 src.rpm
Now the Kmail crash and others mentioned in bug #301453 on kde.bugs are not reproducible anymore here with nepomuk enabled. Gwenview being the other severe bug rendering it unusable with nepomuk enabled.
https://bugs.kde.org/show_bug.cgi?id=301453
I will continue testing but it does look promising :)
Colin
Looking forward to it.
Well I can say soprano-2.7.57 fixes all the crash problems here Eli, I'll add this comment to the above bug report.
Cheers
Colin
On Sunday 10 June 2012 22:08:27 Colin J Thomson wrote:
On Sunday 10 Jun 2012 20:39:33 Eli Wapniarski wrote:
On Sunday 10 June 2012 18:27:06 Colin J Thomson wrote:
Apologies on starting a new thread..
I have been running some tests this afternoon after rebuilding/updating soprano to 2.7.57-1 from F18 src.rpm
Now the Kmail crash and others mentioned in bug #301453 on kde.bugs are not reproducible anymore here with nepomuk enabled. Gwenview being the other severe bug rendering it unusable with nepomuk enabled.
https://bugs.kde.org/show_bug.cgi?id=301453
I will continue testing but it does look promising :)
Colin
Looking forward to it.
Well I can say soprano-2.7.57 fixes all the crash problems here Eli, I'll add this comment to the above bug report.
All right :).... I rebuilt the srpm that was sitting in koji. Installed, rebooted (for luck :) ) and clicked on reply to list. And I'm replying.... Yay !!!!! No crashing .... Yay!!!!!! and no fiddling with nepomuk settings.... Yay!!!!!
:) :) :)
I will let everyone know whats happening after a bit of usage.
Thanks you so very much Colin.
Eli
OK...
Day 1.... Things seem good. No crashing when loading external references, and I am having no trouble replying
Eli
On Monday 11 Jun 2012 22:58:19 Eli Wapniarski wrote:
OK...
Day 1.... Things seem good. No crashing when loading external references, and I am having no trouble replying
Still no problems/crashes seen here either Eli with soprano-2.7.57/4.8.4 which is running on my main machine.
FYI there has been some discussion using a dev version of soprano in this report:
https://bugzilla.redhat.com/show_bug.cgi?id=830178
Overall though 4.8.4 is running great for me now.
Colin
On 06/10/2012 12:27 PM, Colin J Thomson wrote:
I have been running some tests this afternoon after rebuilding/updating soprano to 2.7.57-1 from F18 src.rpm
OK, so a short followup. Looks like the upstream commits that were causing this nepomuk regression were found, and included in kdelibs-4.8.4-4 builds. this means we are *not* going to update soprano to 2.7.57+.
I know at least some of your either manually grabbed soprano-2.7.57 or got it from kde-unstable or even while we temporarily (for about ~1 day) had it in kde-testing.
If that includes you, my current recommendation would be to downgrade back to soprano-2.7.5 or 2.7.6 (if not using kde-4.9beta2 stuff from rawhide or f17 kde-unstable).
One easy way to do accomplish the downgrade includes running:
yum distro-sync
-- rex
If that includes you, my current recommendation would be to downgrade back to soprano-2.7.5 or 2.7.6 (if not using kde-4.9beta2 stuff from rawhide or f17 kde-unstable).
One easy way to do accomplish the downgrade includes running:
yum distro-sync
Thanks Rex for letting us know about the updated kde-libs. I downgraded soprano and updated kde-libs and I'm replying without a crash. Yay!!!!
However, when I ran the reccommended yum command I got output that included the text below. As such, a yum update would be required in any case. And because of that I would suggest that
yum downgrade soprano* yum update
would be better
Eli
---> Package kde-settings.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-kdm.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-kdm.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-ksplash.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-ksplash.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-plasma.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-plasma.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-pulseaudio.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-pulseaudio.noarch 0:4.8-14.fc17 will be erased ---> Package nfs-utils.x86_64 1:1.2.6-0.fc17 will be a downgrade ---> Package nfs-utils.x86_64 1:1.2.6-3.fc18 will be erased ---> Package qt-settings.noarch 0:4.8-13.fc17 will be a downgrade ---> Package qt-settings.noarch 0:4.8-14.fc17 will be erased
Eli Wapniarski wrote:
---> Package kde-settings.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-kdm.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-kdm.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-ksplash.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-ksplash.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-plasma.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-plasma.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-pulseaudio.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-pulseaudio.noarch 0:4.8-14.fc17 will be erased ---> Package qt-settings.noarch 0:4.8-13.fc17 will be a downgrade ---> Package qt-settings.noarch 0:4.8-14.fc17 will be erased
These are from kde-settings-4.8-14.fc17, now superseded by kde-settings-4.8-15.fc17 in updates-testing. (Rex, can you please also put that into kde-testing? It looks like kde-testing is stuck on -13.)
https://admin.fedoraproject.org/updates/FEDORA-2012-9374
---> Package nfs-utils.x86_64 1:1.2.6-0.fc17 will be a downgrade ---> Package nfs-utils.x86_64 1:1.2.6-3.fc18 will be erased
This is a Rawhide (F18) build of nfs-utils you have installed (on a F17 system) for some reason. Unless you did that deliberately, going back to the F17 version is probably the right thing to do.
Kevin Kofler
On Friday 15 June 2012 02:03:26 Kevin Kofler wrote:
Eli Wapniarski wrote:
---> Package kde-settings.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-kdm.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-kdm.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-ksplash.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-ksplash.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-plasma.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-plasma.noarch 0:4.8-14.fc17 will be erased ---> Package kde-settings-pulseaudio.noarch 0:4.8-13.fc17 will be a downgrade ---> Package kde-settings-pulseaudio.noarch 0:4.8-14.fc17 will be erased ---> Package qt-settings.noarch 0:4.8-13.fc17 will be a downgrade ---> Package qt-settings.noarch 0:4.8-14.fc17 will be erased
These are from kde-settings-4.8-14.fc17, now superseded by kde-settings-4.8-15.fc17 in updates-testing. (Rex, can you please also put that into kde-testing? It looks like kde-testing is stuck on -13.)
https://admin.fedoraproject.org/updates/FEDORA-2012-9374
---> Package nfs-utils.x86_64 1:1.2.6-0.fc17 will be a downgrade ---> Package nfs-utils.x86_64 1:1.2.6-3.fc18 will be erased
This is a Rawhide (F18) build of nfs-utils you have installed (on a F17 system) for some reason. Unless you did that deliberately, going back to the F17 version is probably the right thing to do.
Kevin Kofler
Thanks for pointing that out. Didn't notice it. Wow that was bizarre. The computer was updated via yum dist-sync. I will indeed do that
Eli