By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 51 - Add Printer Wizard has error when run from Print Manager
Summary: Add Printer Wizard has error when run from Print Manager
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdeadmin (show other bugs)
Version: 3.5.10
Hardware: i386 Linux
: P5 minor
Assignee: Timothy Pearson
URL:
Depends on: 54
Blocks:
  Show dependency tree / graph
 
Reported: 2009-03-11 19:16 CDT by James
Modified: 2012-10-19 15:31 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

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 James 2009-03-11 19:16:40 CDT 
The Add Printer Wizard, when run with the ¨Add / Add Printers/Class¨ button from Print Manager in Administrator Mode, /opt/kde3/bin/kaddprinterwizard, from kdelibs4c2a-kde3, after selecting ¨Next¨ from ¨Local Port Selection¨, there are two successive popup windows ¨Error - KDE Control Module¨, with the same message ¨Unable to start the creation of the driver database. The execution of make_driver_db_cups failed.¨

When the Add Printer Wizard is run directly from the Print System applet, or from the command line, with or without sudo, there is no problem.
Comment 1 Timothy Pearson 2009-03-16 11:09:20 CDT 
Just ran into this myself on a client's system.  Not yet sure what is causing it, but a temporary fix is to link /opt/kde3/bin/make_driver_db_cups to /usr/bin/make_driver_db_cups.  

It is quite likely that the root KControl environment needs the PATH variable set--I will investigate as time allows.
Comment 2 James 2009-03-16 16:50:59 CDT 
This problem may be caused by the debian version of sudo, which is compiled with the SECURE_PATH build option.  With this build option, "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin".  You may see this by running "sudo env".

It also seems that no amount of tweaking /etc/sudoers will change this behaviour, no matter many years of bug reports.  So, the only way to change PATH in sudo is to recompile sudo, and add /opt/kde3/bin to the compile-time SECURE_PATH.

Note that, while /opt/kde3/bin may appear after /usr/local/*, /opt/kde3/bin must appear BEFORE /usr/bin in the PATH list.

James
Comment 3 Timothy Pearson 2009-03-16 18:47:41 CDT 
I forgot about that!  I have a sudo-kde3 package built with the correct SECURE_PATH, but it is currently broken due to bug 54, therefore I'm marking this bug to depend on it.

Thanks for the reminder!
Comment 4 Timothy Pearson 2009-10-15 08:21:06 CDT 
Fixed on Karmic.