| Summary: | printer margin settings are forgotten at restart | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Martin Senftleben <linux> |
| Component: | print-dialog | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | bugs.kde.attila, cdennett, emilio.recio, habista, illumilore, info, kollix, linux, mathieu, postix, psychonaut, richard.llom |
| Priority: | NOR | ||
| Version: | SVN | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Martin Senftleben
2009-06-28 14:56:58 UTC
can confirm. It even does not store the settings between two printouts. But this is a KDE global problem. Reassigning. *** Bug 228931 has been marked as a duplicate of this bug. *** Due to the information that my Bug 228931 is a duplicate from this i answer here. Hello! Don't get me wrong but i guess that this is not a question of Qt 4.8 or other versions. Under KDE 3x (Qt 3x) the printer dialog was excellent! I was able to set the margins and save the settings. All i would like to do is to save my settings (like the printer dialog under KDE 3x). Every time i am trying to print, i have to click on "Properties", then set the margins, after that i have to click on "Options >>", select the tab "HTML settings" uncheck "printer friendly mode", uncheck "print header" and so on. I hate to say that, but this is so stupid! Isn't it? You can't tell in every office all the user: Hey guys! Remember if you print, don't forget to click here, click there ..... and do this on every single print. This is not user-optimized. Thank you for listening to me. As the one who brought this up: it is one of the basic functionality one can expect, that printer settings are storable. This problem bugs me for 9 months now, and still no change. Every time I print out a mail, I have to reset the margins - for every single print. That was working fine with KDE 3, and nobody can say that this is "not yet" implemented in KDE 4. It should never have gone away. how should I work with kde4, when I cannot print as I used to? is kde4 all about "nice effects" or should it be something that can be used to work with? but working people need snow on the desktop ... it seems to be essential ... sure fire Trying Kubuntu Lucid RC to see if this issue is fixed, and unfortunately it is not. I'll also note that I think this bug and 164899 are duplicates. Surely this is the same issue I reported in Bug 256975? If so, the resolution is "UPSTREAM"; the issue has been reported on the Qt bug tracker here: http://bugreports.qt.nokia.com/browse/QTBUG-15351 I'm on Gnome now, so this bug doesn't bug me any more... Well, regardless, one of these bugs should be marked as the duplicate of the other. I don't have authorization to do that; perhaps as the reporter you could do so, Martin. Sorry, I missed that point. However, I'm not sure if the bug reported at http://bugreports.qt.nokia.com/browse/QTBUG-15351 is the same as the one that I reported here. They may be related, however. But: I do not remember that just clicking on properties and then on OK solved the problem. i had to set the margins according to my needs. And: I had that problem observed only in KMail, and I'm sure other programs use the QT-library as well. As I have no option to verify the duplicity, I would rather keep this report than marking it as a duplicate. *** Bug 205802 has been marked as a duplicate of this bug. *** *** Bug 300088 has been marked as a duplicate of this bug. *** If this bug really is a duplicate, or at least somehow related, to Bug 256975, then it should be noted that the upstream bug report has been marked as resolved for Qt 5.0: https://bugreports.qt-project.org/browse/QTBUG-15351 I left a comment on the qt bug and asked for a backport to qt 4.8. So lets wait (and hope) and see. Any news on the Qt 4.8 state with respect to this issue? Yes. I contacted John Layt (already some month ago) and he said he will try to bring this fix to the next qt 4.8 patch release. And just some days ago the qt bug was updated: Akseli Salovaara updated Bug QTBUG-15351 Margin settings are ignored unless Printer Properties dialog is opened first Change By: Akseli Salovaara (24/Apr/14 3:28 PM) Fix Version/s: 4.8.7 (Next patch release) I think this is good news. :-) *** Bug 308367 has been marked as a duplicate of this bug. *** Can you still reproduce the issue with some more recent version of Okular (22.04+)? Hi, this bug has not been fixed since 2009. I know only one application which can remember the printer margin settings. This is KWrite and perhaps Kate. KWrite stores this information in the file "kwriterc" in the section [Kate Print Settings][Margins]. Can someone please finally fix this bug? Operating System: Fedora Linux 35 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.2 Kernel Version: 5.18.13-100.fc35.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4770T CPU @ 2.50GHz Memory: 7.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 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 mark the bug 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! Hi, kdelibs (version 4 and earlier) is no longer maintained since a few years. KDE Frameworks 5 or 6 might already have resolved this bug. If not, please re-open against the matching framework if feasible or against the application that shows the issue. We then can still dispatch it to the right Bugzilla product or component. Greetings Christoph Cullmann |