Summary: | kinfocenter doesn't show processor information | ||
---|---|---|---|
Product: | [Applications] kinfocenter | Reporter: | Toralf Förster <toralf.foerster> |
Component: | InfoSummary | Assignee: | David Hubner <hubn3rd> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dilfridge, ervin, hubn3rd, yabolus, yofel |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Toralf Förster
2010-01-14 11:00:26 UTC
issue still present in 4.3.5 Yes, this is due to Solid getting the information when compiled and not from the runtime backend ( Mainly because the Hal does not support this ) I shall look at better ways to improve this by talking to Solid developers. (In reply to comment #2) > Yes, this is due to Solid getting the information when compiled and not from > the runtime backend Ah- that's mean recompiling kinfocenter (4.4.2 in the mean while) won't solve ?DO O have to recompile kde-base/solid-runtime-4.4.2 or kde-base/solid-runtime-4.4.2 of my Gentoo system ? You need to recompile kdelibs/solid. I am not sure what package that is in gentoo Did it - no success - BTW I currently at 4.4.3 and issue is still present. Ok, I know what the problem is.. I have some time this week and shall try and fix the problem in solid. (In reply to comment #6) > Ok, I know what the problem is.. I have some time this week and shall try and > fix the problem in solid. Any news on this? Not yet, been far too buzy... I shall try to look at it this weekend! I looked into this. Processor information from HAL is awful, which is the problem. Now solid can have multiple backends I shall look at fixing this with a new backend or coding a udev backend for solid ( I am not sure if this is being worked on but if not I shall do it ) Unfortunately this is a feature and will not make it until 4.6 *** Bug 248836 has been marked as a duplicate of this bug. *** *** Bug 258446 has been marked as a duplicate of this bug. *** Fixed in KDE 4.6 thanks to the solid team |