Version-Release number of selected component: python3-3.4.1-15.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/share/system-config-printer/system-config-printer.py crash_function: strlen executable: /usr/bin/python3.4 kernel: 3.17.1-302.fc21.x86_64+debug runlevel: N 5 type: CCpp uid: 21446 Truncated backtrace: Thread no. 1 (10 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:106 #1 __strdup at strdup.c:41 #2 password_callback at cupsconnection.c:411 #3 cupsDoAuthentication at auth.c:213 #4 cupsGetFd at getputfile.c:129 #6 Connection_getFile at cupsconnection.c:2382 #7 PyObject_Call at /usr/src/debug/Python-3.4.1/Objects/abstract.c:2067 #8 ext_do_call at /usr/src/debug/Python-3.4.1/Python/ceval.c:4580 #9 PyEval_EvalFrameEx at /usr/src/debug/Python-3.4.1/Python/ceval.c:2893 #10 PyEval_EvalCodeEx at /usr/src/debug/Python-3.4.1/Python/ceval.c:3607
Created attachment 949276 [details] File: backtrace
Created attachment 949277 [details] File: cgroup
Created attachment 949278 [details] File: core_backtrace
Created attachment 949279 [details] File: dso_list
Created attachment 949280 [details] File: environ
Created attachment 949281 [details] File: exploitable
Created attachment 949282 [details] File: limits
Created attachment 949283 [details] File: maps
Created attachment 949284 [details] File: open_fds
Created attachment 949285 [details] File: proc_pid_status
Created attachment 949286 [details] File: var_log_messages
Wonder if this should be filed against s-c-printer instead.
Another user experienced a similar problem: I was clicking to add a printer and it asked for my credentials via popup. After clicking continue/enter, it crashed. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/share/system-config-printer/system-config-printer.py crash_function: strlen executable: /usr/bin/python3.4 kernel: 3.17.1-302.fc21.x86_64 package: python3-3.4.1-16.fc21 reason: python3.4 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: tried to print out a pdf file to local printer, printer did start but stop halfway, generating a python3.4 alert. Maybe the mistake was that I did switch the system to standby just at the time when there was still a print job running. System could have warned me though or finished the job in the background? reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/python3 /usr/share/system-config-printer/scp-dbus-service.py crash_function: strlen executable: /usr/bin/python3.4 kernel: 3.17.2-300.fc21.x86_64 package: python3-3.4.1-16.fc21 reason: python3.4 killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Fixed upstream: https://git.fedorahosted.org/cgit/pycups.git/commit/?id=74b046042b29babe158dae21e269aeb04a684509
*** Bug 1147177 has been marked as a duplicate of this bug. ***
python-cups-1.9.69-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/FEDORA-2014-16280/python-cups-1.9.69-2.fc21
Package python-cups-1.9.69-2.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-cups-1.9.69-2.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-16280/python-cups-1.9.69-2.fc21 then log in and leave karma (feedback).
Package python-cups-1.9.70-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-cups-1.9.70-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-16280/python-cups-1.9.70-1.fc21 then log in and leave karma (feedback).
python-cups-1.9.70-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.