| Summary: | KDE/Solid show disks from both HAL and udisks (double disk list in kde). | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | Fest <fest.in> |
| Component: | libsolid | Assignee: | Kevin Ottens <ervin> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | fatgerman, linuxfever, maggsimo, malcolm, nemeskey.david, rafal.przemyslaw.malinowski, simmetric, victor.grischenko |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Fest
2010-12-03 02:09:48 UTC
Both hal and udisks running? If i understand output correctly, yes. ps aux| grep hal 102 1776 0.0 0.1 46900 5104 ? Ssl 11:02 0:00 /usr/sbin/hald --use-syslog --verbose=yes root 1777 0.0 0.0 20344 1392 ? S 11:02 0:00 hald-runner root 1805 0.0 0.0 22468 1372 ? S 11:02 0:00 hald-addon-input: Listening on /dev/input/event0 /dev/input/event1 102 1827 0.0 0.0 24276 1336 ? S 11:02 0:00 /usr/libexec/hald-addon-acp ps aux| grep udisk root 1977 0.2 0.0 122920 3728 ? Sl 11:03 0:00 /usr/libexec/udisks-daemon root 1984 0.0 0.0 40560 764 ? S 11:03 0:00 udisks-daemon: not polling any devices fest 2742 0.0 0.0 7952 876 pts/3 S+ 11:06 0:00 grep --colour=auto udisk That's the reason, then. So Solid checking both of them for info ? Why if from 4.6 Beta KDE depends on udisk ? KDE 4.6 can use both HAL and udisks for getting disks information. If both are running, KDE/solid will expose devices coming from both. *** Bug 258808 has been marked as a duplicate of this bug. *** *** Bug 258893 has been marked as a duplicate of this bug. *** I can confirm this. See bug 258893. (In reply to comment #5) > KDE 4.6 can use both HAL and udisks for getting disks information. > If both are running, KDE/solid will expose devices coming from both. I don't see the rationale for exposing devices coming from both. Is there even a use case, when the two frameworks report different devices? Also, I reckon the information provided by the frameworks should be sufficient to identify and filter duplicates. *** Bug 259224 has been marked as a duplicate of this bug. *** I can confirm that removing the HAL resolves the issue. However minimum gimp and k3b are depending on it. If the HAL and udev running at the same time you will get duplicate info about the battery as well. KDE Platform Version: 4.5.80 (4.6 Beta1) Qt Version: 4.7.1 Operating System: Linux 2.6.37-rc3-git1-6-desktop x86_64 Distribution: "openSUSE 11.4 Milestone 4 of 6 (x86_64)" *** Bug 259442 has been marked as a duplicate of this bug. *** *** Bug 259546 has been marked as a duplicate of this bug. *** *** Bug 259515 has been marked as a duplicate of this bug. *** *** Bug 259697 has been marked as a duplicate of this bug. *** SVN commit 1206281 by ervin: Seems the new backends now work good enough. So retire the old HAL backend on Linux, it's still the default on other unices though. On Linux it can be reactivated using the SOLID_HAL_LEGACY environment variable. CCMAIL: kde-hardware-devel@kde.org BUG: 258638 M +17 -9 solid/managerbase.cpp M +5 -0 tests/halbasictest.cpp M +2 -0 tests/halbasictest.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1206281 *** Bug 260297 has been marked as a duplicate of this bug. *** |