Bug 1027034

Created attachment 820079 [details]
File: backtrace

Created attachment 820080 [details]
File: build_ids

Created attachment 820081 [details]
File: cgroup

Created attachment 820082 [details]
File: core_backtrace

Created attachment 820083 [details]
File: dso_list

Created attachment 820084 [details]
File: environ

Created attachment 820085 [details]
File: limits

Created attachment 820086 [details]
File: maps

Created attachment 820087 [details]
File: open_fds

Created attachment 820088 [details]
File: proc_pid_status

Created attachment 820089 [details]
File: var_log_messages

(In reply to Dan Mossor from comment #0)
> Truncated backtrace:
> Thread no. 1 (10 frames)
>  #2 Py_FatalError at /usr/src/debug/Python-2.7.5/Python/pythonrun.c:1697
>  #3 PyEval_RestoreThread at /usr/src/debug/Python-2.7.5/Python/ceval.c:375
>  #4 Connection_end_allow_threads at cupsconnection.c:348
>  #5 Connection_adminSetServerSettings at cupsconnection.c:3891

~> python-cups

So, tstate is NULL here. That can't really happen, following the logic of the code.

PyEval_SaveThread() is always called before this PyEval_RestoreThread() call, and the value is saved into memory already allocated (self). If low memory conditions caused PyEval_SaveThread() to fail and end up with a NULL value to return, it would have already called Py_FatalError(). We know Py_FatalError() is working OK because that's what PyEval_RestoreThread() called to abort.

That only really leaves the possibility of a memory scribble in cupsAdminSetServerSettings.

The only likely-looking candidate in cupsAdminSetServerSettings() that I can see is invalidate_cupsd_cache():

static void
invalidate_cupsd_cache(
    _cups_globals_t *cg)                /* I - Global data */
{
  cupsFreeOptions(cg->cupsd_num_settings, cg->cupsd_settings);

  cg->cupsd_hostname[0]  = '\0';
  cg->cupsd_update       = 0;
  cg->cupsd_num_settings = 0;
  cg->cupsd_settings     = NULL;
}

...but I can't really see how cg would end up being bad.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.