Bug 130717 - Using k3b Under Gnome
Summary: Using k3b Under Gnome
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: GNOME (show other bugs)
Version: Final
Hardware: i686 Other
: P5 - None : Enhancement
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-26 10:55 UTC by Karl Eichwalder
Modified: 2007-01-26 12:26 UTC (History)
0 users

See Also:
Found By: Documentation
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Eichwalder 2005-10-26 10:55:58 UTC 
Inter-application communication between k3b and the Gnome(?) hardware detection does not seem to exist.

My computer has a DVD drive and a DVD writer.
Under Gnome I started k3b for ripping and burning a data CD-ROM.  When I finished  ripping the medium, k3b offered button for pulling a blank medium into the second drive (the writer).  Once I pressed "close tray" (or something like that), the GNOME hardware detection kicked in and asked me what I want to do with the blank medium.

That's confusing, because the user expects k3b to be responsible for this ripping and writing action.

I'm not sure whether it is theoretically possible, to make these applications communicate properly (D-BUS?).
Comment 1 JP Rosevear 2005-10-26 11:58:55 UTC 
There is currently a discussion underway on the utopia list about dbus communication to solve this problem, its a general issue moving to hal/dbus/g-v-m/k-v-m
Comment 2 Stephan Kulow 2007-01-26 11:50:21 UTC 
this is outdated, right?
Comment 3 Karl Eichwalder 2007-01-26 12:26:14 UTC 
I did not try lately, so let's assume it is working now.  I did not see a similar report elsewhere.  If you feel different, please re-open.