Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 163826 - Cannot prevent KsCD from starting when CD inserted
Summary: Cannot prevent KsCD from starting when CD inserted
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-21 14:20 UTC by Jerry Amundson
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-07-21 21:21:06 UTC


Attachments (Terms of Use)

Description Jerry Amundson 2005-07-21 14:20:18 UTC
Description of problem:
Cannot prevent KsCD from starting when CD inserted. I've tried many ways -
Control Center, /etc/fstab, haldaemon, etc. but have found no way to prevent
KsCD from starting when a CD is inserted. It is *real* annoying when trying to
rip a few songs from many cd's to have KsCD activate each time.... Aargh.... 

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

How reproducible:
Always

Steps to Reproduce:
1.Insert CD.
2.Quit KsCD
3.Go to 1.
  
Actual results:
KsCD starts.

Expected results:
A way to have no results, i.e. have *nothing* start.

Additional info:
In this particular case, I'm ripping songs using, for example, Sound Juicer. I
want to prevent KsCD, or anything else, from taking over.

Comment 1 Jerry Amundson 2005-07-21 14:21:44 UTC
Oh, I went to KDE first... http://bugs.kde.org/show_bug.cgi?id=109408

Comment 2 Ngo Than 2005-07-21 21:21:06 UTC
if you want to disable this feature, you should please remove 
$HOME/.kde/Autostart/Autorun.desktop


Note You need to log in before you can comment on or make changes to this bug.