Description of problem: http://lists.kde.org/?l=kde&m=126584264104700&w=2 describes problem, probable cause and workaround Version-Release number of selected component (if applicable): 4.4.0 How reproducible: Always Steps to Reproduce: 1. Press Alt+F2 2. 3. Actual results: None Expected results: KRunner input widget Additional info:
Uh, our KDE 4.4.0 builds should be already built against Soprano 2.4.0, so the hypothesis of this being due to building against 2.3.73 and running against 2.4.0 looks wrong to me. Can you please post the output of: rpm -q kdelibs kdebase-workspace soprano
kdelibs-4.4.0-3.fc12.x86_64 kdebase-workspace-4.4.0-2.fc12.x86_64 soprano-2.4.0-0.1.fc12.x86_64 I see this on two machines, both x86_64.
Hmmm, those packages (and kdebase-runtime-4.4.0-2.fc12) in kde-redhat were indeed built against 2.3.73. This should be better with: kdelibs-4.4.0-4.fc12 kdebase-runtime-4.4.0-3.fc12 kdebase-workspace-4.4.0-2.fc12.1 from Koji which were built against soprano-2.4.0.
Looks like that's not the issue, thomasj_ said on IRC that updating those packages from Koji didn't help.
Can you please retest with soprano-2.4.0.1-1.fc12? http://koji.fedoraproject.org/koji/buildinfo?buildID=155619 (Rex also pushed it to kde-unstable.)
As upstream says this is fixed in soprano, 2.4.0.1, I'm just going to close this.
Did: sudo yum update with kde-unstable. logged out and in again. Pressed Alt+F2 and KRunner appeared. Seems to be resolved. Current packages: kdelibs-4.4.0-3.fc12.x86_64 kdebase-workspace-4.4.0-2.fc12.x86_64 soprano-2.4.0.1-1.fc12.x86_64
Thanks for the confirmation.
Let's make it clear that this and the other 2 Soprano-induced issues are all duplicates of the same (fixed) bug. *** This bug has been marked as a duplicate of bug 566061 ***