Bug 199472

Summary: Default Printer setting is not honoured by KDE apps
Product: [Unmaintained] kdelibs Reporter: Hrishikesh Mehendale (हृषीकेश मेहेंदळे) <hashinclude>
Component: print-dialogAssignee: John Layt <jlayt>
Status: RESOLVED WORKSFORME    
Severity: normal CC: codestruct, jlayt, m.weghorn
Priority: NOR Keywords: triaged
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: The screenshot described in the bug report

Description Hrishikesh Mehendale (हृषीकेश मेहेंदळे) 2009-07-08 22:00:16 UTC 
Version:           4.2.2 (KDE 4.2.2) (using 4.2.2 (KDE 4.2.2), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.28-11-generic

I have multiple network printers configured within KDE. However, KDE print applications (konqueror, okular, ...) all use the first printer I added as their default printer, rather than using the actual default printer.

My setup:

All printers are HP 300x series network laser printers.

1st Added: "borg"
2nd Added: "pavo" **current default**
3rd Added: "ara"

The System Settings -> Printers panel shows this info correctly (if I select "borg", it shows "The current default is pavo"). However, if I open up the print dialog from KDE apps (from Konqueror in the screenshot), all apps always default to "borg", which was the first one I added, even after I tried disabling that printer!
Comment 1 Hrishikesh Mehendale (हृषीकेश मेहेंदळे) 2009-07-08 22:01:38 UTC 
Created attachment 35168 [details]
The screenshot described in the bug report
Comment 2 John Layt 2009-07-09 11:42:30 UTC 
Probably related to a know Qt bug.  Can you confirm which version of Qt you are using?
Comment 3 Hrishikesh Mehendale (हृषीकेश मेहेंदळे) 2009-07-09 18:23:40 UTC 
I'm using qt 4.5.0-0ubuntu4.1 (stock Ubuntu 9.04 x86_64)
Comment 4 Gregor Mi 2014-09-23 19:19:32 UTC 
This seems to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=207375
Comment 5 Michael Weghorn 2018-01-16 15:12:25 UTC 
This bug report is quite old and I cannot reproduce.

@Hrishikesh Mehendale (हृषीकेश मेहेंदळे):
Do you still encounter the described problem with current versions of KDE applications?
Comment 6 Michael Weghorn 2018-05-10 19:29:00 UTC 
(In reply to Michael Weghorn from comment #5)
> This bug report is quite old and I cannot reproduce.
> 
> @Hrishikesh Mehendale (हृषीकेश मेहेंदळे):
> Do you still encounter the described problem with current versions of KDE
> applications?

I'm setting the bug status to NEEDSINFO for now, since the question has not been answered yet and I am unable to reproduce.
Comment 7 Andrew Crouthamel 2018-09-28 03:34:04 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-29 02:23:13 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!