Bug 866927 - [abrt] glib-networking-2.34.0-1.fc18: got_proxies: Process /usr/libexec/glib-pacrunner was killed by signal 6 (SIGABRT)
Summary: [abrt] glib-networking-2.34.0-1.fc18: got_proxies: Process /usr/libexec/glib-...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: glib-networking
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ac826dd24efb1434d5824f3ee33...
: 954480 995740 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-16 10:44 UTC by redhat
Modified: 2014-02-05 12:35 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 12:35:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: core_backtrace (1.38 KB, text/plain)
2012-10-16 10:44 UTC, redhat
no flags Details
File: environ (1.05 KB, text/plain)
2012-10-16 10:45 UTC, redhat
no flags Details
File: event_log (1.14 KB, text/plain)
2012-10-16 10:45 UTC, redhat
no flags Details
File: backtrace (13.26 KB, text/plain)
2012-10-16 10:46 UTC, redhat
no flags Details
File: limits (1.29 KB, text/plain)
2012-10-16 10:46 UTC, redhat
no flags Details
File: cgroup (129 bytes, text/plain)
2012-10-16 10:47 UTC, redhat
no flags Details
File: smolt_data (3.15 KB, text/plain)
2012-10-16 10:47 UTC, redhat
no flags Details
File: maps (13.67 KB, text/plain)
2012-10-16 10:47 UTC, redhat
no flags Details
File: dso_list (2.61 KB, text/plain)
2012-10-16 10:47 UTC, redhat
no flags Details
File: proc_pid_status (922 bytes, text/plain)
2012-10-16 10:47 UTC, redhat
no flags Details
File: var_log_messages (4.36 KB, text/plain)
2012-10-16 10:47 UTC, redhat
no flags Details
File: open_fds (352 bytes, text/plain)
2012-10-16 10:47 UTC, redhat
no flags Details

Description redhat 2012-10-16 10:44:46 UTC
Description of problem:
Installing Gnome extension from extensions.gnome.org using firefox

Version-Release number of selected component:
glib-networking-2.34.0-1.fc18

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.15
backtrace_rating: 4
cmdline:        /usr/libexec/glib-pacrunner
crash_function: got_proxies
kernel:         3.6.1-1.fc18.x86_64

truncated backtrace:
:Thread no. 1 (3 frames)
: #4 got_proxies at glibpacrunner.c:51
: #6 g_simple_async_result_complete at gsimpleasyncresult.c:775
: #7 complete_in_idle_cb_for_thread at gsimpleasyncresult.c:843

Comment 1 redhat 2012-10-16 10:44:59 UTC
Created attachment 628090 [details]
File: core_backtrace

Comment 2 redhat 2012-10-16 10:45:12 UTC
Created attachment 628092 [details]
File: environ

Comment 3 redhat 2012-10-16 10:45:15 UTC
Created attachment 628093 [details]
File: event_log

Comment 4 redhat 2012-10-16 10:46:05 UTC
Created attachment 628094 [details]
File: backtrace

Comment 5 redhat 2012-10-16 10:46:14 UTC
Created attachment 628095 [details]
File: limits

Comment 6 redhat 2012-10-16 10:47:04 UTC
Created attachment 628096 [details]
File: cgroup

Comment 7 redhat 2012-10-16 10:47:11 UTC
Created attachment 628097 [details]
File: smolt_data

Comment 8 redhat 2012-10-16 10:47:13 UTC
Created attachment 628098 [details]
File: maps

Comment 9 redhat 2012-10-16 10:47:16 UTC
Created attachment 628099 [details]
File: dso_list

Comment 10 redhat 2012-10-16 10:47:27 UTC
Created attachment 628100 [details]
File: proc_pid_status

Comment 11 redhat 2012-10-16 10:47:32 UTC
Created attachment 628101 [details]
File: var_log_messages

Comment 12 redhat 2012-10-16 10:47:34 UTC
Created attachment 628102 [details]
File: open_fds

Comment 13 redhat 2012-10-16 13:41:17 UTC
Additional info: was using automatic proxy configuration specified in gnome-control-center

Comment 14 Dan Winship 2013-09-19 12:37:16 UTC
*** Bug 954480 has been marked as a duplicate of this bug. ***

Comment 15 Dan Winship 2013-09-19 12:37:53 UTC
*** Bug 995740 has been marked as a duplicate of this bug. ***

Comment 16 Dan Winship 2013-09-19 14:18:54 UTC
This is a bug in glib-networking's handling of libproxy errors, but it is most likely only getting hit because of bug 911066, and so the libproxy updates that have been submitted for that ought to fix it.

https://admin.fedoraproject.org/updates/libproxy-0.4.11-6.fc19
https://admin.fedoraproject.org/updates/libproxy-0.4.11-7.fc20

(no f18 update yet)

Comment 17 Fedora End Of Life 2013-12-21 09:07:58 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.

Comment 18 Fedora End Of Life 2014-02-05 12:35:47 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


Note You need to log in before you can comment on or make changes to this bug.