Summary: | data CD not recognized on KDE | ||
---|---|---|---|
Product: | [Unmaintained] solid | Reporter: | LeLorrain <mechlinge> |
Component: | libsolid-hal | Assignee: | Alberto Villa <avilla> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | afiestas, antoine.contal |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Mandriva RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
LeLorrain
2010-11-16 00:10:45 UTC
I have the same issue. And it gets even weirder. I have two computers running KDE 4.4.3, with the same mobo, same CD device, same linux distribution (Mandriva 2010.1), and same kernel (2.6.33.7). For one of them, KDE sees the CD-R perfectly and prompts me to mount it and so on. For the other one, nothing, KDE does not react at all when I insert the CD-R, just like the original reporter describes. I can mount the CD-R with konsole or with another desktop manager. But neither Dolphin nor the relevant plasmoid acknowledge the inserted CD. How can I help debug this? Is this reproducible in KDE 4.10? @alberto what about freeBSD ? Hi,
I was not expecting this still followed!
My CDs are correctly read on KDE 4.10. Just that on one of my 2 drivers, impossible to eject manualy the disk (the "Eject" button is operational).
> From: afiestas@kde.org
> To: mechlinge@hotmail.com
> Subject: [solid] [Bug 257030] data CD not recognized on KDE
> Date: Sun, 3 Mar 2013 15:46:50 +0000
>
> https://bugs.kde.org/show_bug.cgi?id=257030
>
> Alex Fiestas <afiestas@kde.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |NEEDSINFO
> CC| |afiestas@kde.org
> Resolution|--- |WAITINGFORINFO
>
> --- Comment #2 from Alex Fiestas <afiestas@kde.org> ---
> Is this reproducible in KDE 4.10?
>
> @alberto what about freeBSD ?
>
> --
> You are receiving this mail because:
> You reported the bug.
Awesome then ! there is already another bug reported for the ejecting problem we'll try to fix it ASAP. Thanks for the feedback ! |