Bug 886833 - [abrt] pgadmin3-1.16.0-1.fc19: weak_refs_notify: Process /usr/bin/pgadmin3 was killed by signal 11 (SIGSEGV)
Summary: [abrt] pgadmin3-1.16.0-1.fc19: weak_refs_notify: Process /usr/bin/pgadmin3 wa...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pgadmin3
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Devrim Gündüz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e9bd34e44acf2ec8b58393ad554...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-13 10:03 UTC by Janusz Pyzio
Modified: 2015-02-17 14:37 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-02-17 14:37:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (21.08 KB, text/plain)
2012-12-13 10:03 UTC, Janusz Pyzio
no flags Details
File: cgroup (126 bytes, text/plain)
2012-12-13 10:03 UTC, Janusz Pyzio
no flags Details
File: core_backtrace (1.72 KB, text/plain)
2012-12-13 10:04 UTC, Janusz Pyzio
no flags Details
File: dso_list (12.44 KB, text/plain)
2012-12-13 10:04 UTC, Janusz Pyzio
no flags Details
File: environ (1.40 KB, text/plain)
2012-12-13 10:04 UTC, Janusz Pyzio
no flags Details
File: limits (1.29 KB, text/plain)
2012-12-13 10:04 UTC, Janusz Pyzio
no flags Details
File: maps (59.60 KB, text/plain)
2012-12-13 10:04 UTC, Janusz Pyzio
no flags Details
File: open_fds (671 bytes, text/plain)
2012-12-13 10:04 UTC, Janusz Pyzio
no flags Details
File: proc_pid_status (1.04 KB, text/plain)
2012-12-13 10:04 UTC, Janusz Pyzio
no flags Details
File: smolt_data (2.75 KB, text/plain)
2012-12-13 10:04 UTC, Janusz Pyzio
no flags Details
File: var_log_messages (461 bytes, text/plain)
2012-12-13 10:04 UTC, Janusz Pyzio
no flags Details
File: xsession_errors (2.76 KB, text/plain)
2012-12-13 10:04 UTC, Janusz Pyzio
no flags Details

Description Janusz Pyzio 2012-12-13 10:03:46 UTC
Description of problem:
When I try add new column to table

Version-Release number of selected component:
pgadmin3-1.16.0-1.fc19

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/pgadmin3
crash_function: weak_refs_notify
executable:     /usr/bin/pgadmin3
kernel:         3.7.0-2.fc19.x86_64
remote_result:  598989
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #1 weak_refs_notify at gobject.c:2469
 #3 gdk_event_translate at gdkevents-x11.c:2217
 #4 _gdk_events_queue at gdkevents-x11.c:2336
 #10 gtk_main at gtkmain.c:1257
 #11 wxEventLoop::Run at src/gtk/evtloop.cpp:76
 #12 wxAppBase::MainLoop at src/common/appcmn.cpp:312
 #13 wxEntry at src/common/init.cpp:448

Comment 1 Janusz Pyzio 2012-12-13 10:03:55 UTC
Created attachment 662825 [details]
File: backtrace

Comment 2 Janusz Pyzio 2012-12-13 10:03:58 UTC
Created attachment 662826 [details]
File: cgroup

Comment 3 Janusz Pyzio 2012-12-13 10:04:03 UTC
Created attachment 662827 [details]
File: core_backtrace

Comment 4 Janusz Pyzio 2012-12-13 10:04:07 UTC
Created attachment 662828 [details]
File: dso_list

Comment 5 Janusz Pyzio 2012-12-13 10:04:09 UTC
Created attachment 662829 [details]
File: environ

Comment 6 Janusz Pyzio 2012-12-13 10:04:11 UTC
Created attachment 662830 [details]
File: limits

Comment 7 Janusz Pyzio 2012-12-13 10:04:13 UTC
Created attachment 662831 [details]
File: maps

Comment 8 Janusz Pyzio 2012-12-13 10:04:15 UTC
Created attachment 662832 [details]
File: open_fds

Comment 9 Janusz Pyzio 2012-12-13 10:04:17 UTC
Created attachment 662833 [details]
File: proc_pid_status

Comment 10 Janusz Pyzio 2012-12-13 10:04:20 UTC
Created attachment 662834 [details]
File: smolt_data

Comment 11 Janusz Pyzio 2012-12-13 10:04:22 UTC
Created attachment 662835 [details]
File: var_log_messages

Comment 12 Janusz Pyzio 2012-12-13 10:04:25 UTC
Created attachment 662836 [details]
File: xsession_errors

Comment 13 Fedora End Of Life 2013-04-03 14:33:34 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 14 Fedora End Of Life 2015-01-09 17:32:00 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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.

Comment 15 Fedora End Of Life 2015-02-17 14:37:21 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.