Bug 797228 - k3b No optical drive found
Summary: k3b No optical drive found
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kdelibs
Version: 16
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-24 15:54 UTC by Kyle Pablo
Modified: 2012-02-25 00:53 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-24 23:29:13 UTC
Type: ---

Attachments (Terms of Use)
udisk dump (2.19 KB, application/octet-stream)
2012-02-24 15:54 UTC, Kyle Pablo 		no flags Details
udisk dump 2 (2.46 KB, application/octet-stream)
2012-02-24 15:55 UTC, Kyle Pablo 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Kyle Pablo 2012-02-24 15:54:14 UTC 
Description of problem:
K3b reports: No optical drive found.
K3b did not find any optical device in your system.
Solution: Make sure HAL daemon is running, it is used by K3b for finding devices.

Version-Release number of selected component (if applicable):
2.0.2

How reproducible:
everytime

Steps to Reproduce:
1. start k3b
2.
3.
  
Actual results:
No optical drive found.
K3b did not find any optical device in your system.
Solution: Make sure HAL daemon is running, it is used by K3b for finding devices.

Expected results:
no error message

Additional info:
Comment 1 Kyle Pablo 2012-02-24 15:54:59 UTC 
Created attachment 565631 [details]
udisk dump
Comment 2 Kyle Pablo 2012-02-24 15:55:38 UTC 
Created attachment 565632 [details]
udisk dump 2
Comment 3 Kevin Kofler 2012-02-24 16:21:15 UTC 
As we explained on IRC, the message is misleading, HAL is dead and gone. There's no HAL in Fedora 16 at all, and it's not expected to be needed. Several of us have K3b running just fine, without HAL.
Comment 4 Kyle Pablo 2012-02-24 23:29:13 UTC 
Found the solution.  I need to be a member of cdrom group.
Comment 5 Kevin Kofler 2012-02-25 00:53:03 UTC 
That shouldn't really be needed, but if it works for you… I don't think anybody else has had this problem so far. Strange.
Note You need to log in before you can comment on or make changes to this bug.