abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/pgadmin3 comment: teh row was actually deleted, but pgadmin crashes afterwards component: pgadmin3 crash_function: sqlTable::DeleteRows executable: /usr/bin/pgadmin3 global_uuid: 5ab718bb167bfb16e0729af59062797ef77bce5d kernel: 2.6.32.16-141.fc12.x86_64 package: pgadmin3-1.10.3-2.fc12 rating: 4 reason: Process /usr/bin/pgadmin3 was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1. opened a db with pgadmin 2. 'view all rows' on some very simple table (3 cols: id, string, string) 3. select a row to delete 4. use keyboard 'del' 5. confirm "do you really want ...?" using keyboard 'return'
Created attachment 433688 [details] File: backtrace
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. Thank you for reporting this bug and we are sorry it could not be fixed.
I don't know if there is any interest in changing the state of this closed bug, but I thought I'd mention that I've submitted a patch for this problem to the pgAdmin project since people with this problem are likely to find this bug. Here is what I've submitted: http://www.mail-archive.com/pgadmin-hackers@postgresql.org/msg19605.html