Summary: | printer - Systemsettings crashes when selecting new driver for installed printer | ||
---|---|---|---|
Product: | [Frameworks and Libraries] print-manager | Reporter: | Matthew <zenomorph.ebe> |
Component: | general | Assignee: | Daniel Nicoletti <dantti12> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 4.11.3 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Matthew
2013-11-25 13:44:47 UTC
I went back to my system and logged onto a Gnome session and used it's printer configuration tool to see if the instaleld driver worked with gnome, it didn't. I still had the problem where the printer wouldn't produce an output, just made noises like it was going to print. However under Gnome, I wasn't getting any problems with selecting drivers, they could be selected but didn't do anything more than before. As a last resort I removed the printer completely, then re-added the samsung ML-2510 in the usual way. This time however when I selected the ML-2510 to install, the next step was that the installer came up with a new driver pack to be installed, which wasn't indicated when I installed the same printer under KDE. The extra package it was asking for now was Driver for QPDL/SPL2 printers (Samsung and several Xerox printers). Now when the installation had finished, the printer operated correctly. It appears to me now that when I installed the Samsung ML-2510 under a KDE session, the installation process had not correctly pulled in the relevent driver pack it should have, so only part of the installation had been carried out. Could it therefore be that the KDE printer installation process doesn't search for the required dependencies? I can not reproduce your issue, it works for me, if you can still reproduce it, please attach the process to gdb and provide us a backtrace or more info like which exact driver did you use. This is likely crashing CUPS but our UI shouldn't be affected by that. I was advised years ago that this bug was expired, being as it was reported in 2013. However I think the bug got solved by some subsequent updates in KDE and Gnome. |