Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34008 - [kdelibs] solid actions for some kind of devices not working with udisk2
Attached to Project:
Arch Linux
Opened by Sergio Tridente (TioDuke) - Sunday, 24 February 2013, 23:05 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 06 March 2013, 08:40 GMT
Opened by Sergio Tridente (TioDuke) - Sunday, 24 February 2013, 23:05 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 06 March 2013, 08:40 GMT
|
DetailsDescription:
Solid actions do not work for some type of devices (like, for example, optical) since KDE SC 4.10. The culprit seems to be upstream changing from udisks to udisks2. I made the package myself with the following option -DWITH_SOLID_UDISKS2=OFF and now everything seems to work just fine. I know this is an upstream bug, but since KDE SC 4.10 supports both, I wanted to ask to change this package to use udisk2 for the time being until better support is added for udisks2. Additional info: * package version(s) 4.10.0-2 * config and/or log files etc. Steps to reproduce: Insert media, there is no option to read it (k3b, kaffeine, etc.). You just get a doplhin action (even for blank disks!!) |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Wednesday, 06 March 2013, 08:40 GMT
Reason for closing: Fixed
Additional comments about closing: kdelibs 4.10.1
Wednesday, 06 March 2013, 08:40 GMT
Reason for closing: Fixed
Additional comments about closing: kdelibs 4.10.1
Please report this missing feature upstream.
That said, udisks2 support on KDE SC 4.10.0 should be considered beta at the moment (that is why filing a bug report upstream is the right choice). Please consider this: the reason why udisks(2) is a dependency is _solid_. To my knowledge there is no other component in KDE that requires udisks(2). Then choosing udisks2 over udisks, which breaks the only KDE component requiring udisks(2), does not seem the right choice for the time being.
Please reconsider your decision.
You can mark this as solved. Thank you.