| Summary: | system-config-printer segfaults when it asks for User/passwprd | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | w unruh <unruh> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | doktor5000, luigiwalser, mageia, makowski.mageia, thierry.vignaud, yann.cantin |
| Version: | 5 | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | system-config-printer | CVE: | |
| Status comment: | |||
|
Description
w unruh
2015-10-11 20:57:46 CEST
Can you run it from console and report any errors you see? A stacktrace would be useful too. There is no registered maintainer for this package in our maintainers database, so adding some packagers in CC. Packagers, if working on this please assign to yourself and maybe add yourself as maintainer in the maintainers database. Keywords:
(none) =>
NEEDINFO Cannot reproduce. Please provide accurate details for reproducing and a stack trace from the segfault. Status:
NEW =>
UNCONFIRMED It may be that it was a problem with 2.0.3 since it has not reoccured in the past day when I reinstalled 2.0.2 (with the 100%CPU bug fix installed-- Bug 16738) And it was not there from "day 1". It suddenly popped up. Ie, it is one of those sporadic bugs-- Sorry. If you do not see it, and right now I do not see it, I will have to wait and see if it crops up again. It was a bare little window which simply asked for Username Password with boxes for text entry and nothing else to indicate what was asking for this (except for the truncated title on the window bar mentioned above). From the console, there was a comment from Gtk but I cannot reproduce it now. I did have a trace, but stored it in /tmp on a mga5 system, and of course that did not survive the reboot. Note sure where stack traces are stored. Ahh, so the issue may have been related to the CUPS 2.0.3 in updates_testing. One tester indicated some other issues with that, so I need to update it again, probably to 2.0.4, and see if that works better. As far as the stack traces, usually if our configuration tools crash they launch drakbug which gives you a way to save the stack trace or submit it directly to Bugzilla. I'm not sure if s-c-p does as it's not a native drakconf tool (or at least if it does when run directly rather than through drakconf). Gtk errors printed to the console could be useful too. There was no drakbug launched, either when run from the command line or from MCC. The printer setup window simply disappeared. Ie, the segfault was not handled well by the program. If it happens again I will try to see if I can capture something. It may have been related to 2.0.3 but it is hard to see how that would have launched a gtk request for password. The Gtk error was just a comment that something (I have forgotten) was deprecated. Sorry I cannot be of more help. I have spent way way way too much time on these printer isues. The system seems to be working now, and I cannot spend more time on it. If you launched it from a root shell, it's not clear why it would have been asking you for a password at all. Also, sometimes gtk+ and associated libraries spit out non-fatal messages, so we don't know yet whether it would have been helpful. Anyway, no problem. If you see this again, let us know. If not, then great. I'll close this for now as it cannot be reproduced. Status:
UNCONFIRMED =>
RESOLVED Yes, I agree, I could not figure out why root should still demand a password. And the crash did not seem to produce a core file. Just a straight crash. Very strange. (In reply to David Walser from comment #4) drakbug is only used by tools that are written in perl & that use our modules. s-c-p is written in python... => So no drakbug for it |