Bug 113747 - suseplugger launches process, when not configured to do so
Summary: suseplugger launches process, when not configured to do so
Status: RESOLVED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: KDE (show other bugs)
Version: Beta 3
Hardware: Other All
: P5 - None : Critical
Target Milestone: ---
Assignee: Stephan Kulow
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-29 07:24 UTC by Klaus Singvogel
Modified: 2005-09-01 15:22 UTC (History)
0 users

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

Attachments
susepluggerrc.klaus (2.06 KB, text/plain)
2005-08-29 08:47 UTC, Klaus Singvogel 		Details
View All 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 Klaus Singvogel 2005-08-29 07:24:52 UTC 
I disabled the suseplugger to start k3b, when inserting a blank CD-R:  
In the past the k3b reads again the TOC of the cdwriter and usually its  
doing this during a burn process --> the blank CD is for the trash.  
  
Therefore I disabled suseplugger starting any processes for a blank CD. 
--------------------------------------------------------------  
prompt> grep -i blank $HOME/.kde/share/config/susepluggerrc  
CDdefaultApp_CDblank_doAsk=false  
CDdefaultApp_CDblank_doStart=true  
CDdefaultApp_CDblank_doAsk=false  
CDdefaultApp_CDblank_doStart=false  
--------------------------------------------------------------  
This worked fine in 9.3. 
 
Now, in 10.0-beta3, suseplugger ignores this configuration and starts k3b. :(
Comment 1 Stephan Kulow 2005-08-29 08:27:07 UTC 
I guess, your grep shows the problem: CDdefaultApp_CDblank_doStart=true  
 
I need the whole file
Comment 2 Klaus Singvogel 2005-08-29 08:47:04 UTC 
Created attachment 47933 [details]
susepluggerrc.klaus
Comment 3 Klaus Singvogel 2005-08-29 08:48:35 UTC 
Sorry, didn't saw the  CDdefaultApp_CDblank_doStart=true  (I guess it's Monday 
morning). 
 
But nevertheless, the behavior changed now by the migration: 9.3 -> 10.0
Comment 4 Stephan Binner 2005-09-01 08:58:19 UTC 
Adrian says "fix it" :-)
Comment 5 Stephan Kulow 2005-09-01 15:22:11 UTC 
the point is the configure dialog is evily dangerous and I removed this 
"feature" from the configure dialog. But you stil need to cleanup your 
susepluggerrc