abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: abrt-backtrace --single-thread --remove-exit-handlers --frame-depth=5 --remove-noncrash-frames /var/spool/abrt/ccpp-1282838760-1749/backtrace component: abrt crash_function: yyresolveAction executable: /usr/bin/abrt-backtrace kernel: 2.6.35.2-9.fc14.x86_64 package: abrt-1.1.13-2.fc14 rating: 4 reason: Process /usr/bin/abrt-backtrace was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1282839879 uid: 500 How to reproduce ----- 1.Crashed while submitting another non-ABRT crash. 2. 3.
Created an attachment (id=441274) File: backtrace
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Crash occurred while submitting a crash report for an unrelated crash (mutter). 2. 3.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.trying to debug a crash 2. 3.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) Comment ----- Abrt was generating backtrace from xine crash, and nothing happened for the long time. I closed the dialog and abrt crash was reported.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Was submitting a crash report for mutter. 2.After abrt downloaded all the debuginfo packages it hung. 3.Quit out of abrt, then relaunched and saw the abrt crash listed along with the original mutter crash report.
This bug is fixed in current ABRT git version.
*** Bug 632589 has been marked as a duplicate of this bug. ***
*** Bug 627698 has been marked as a duplicate of this bug. ***
*** Bug 573333 has been marked as a duplicate of this bug. ***
*** Bug 616988 has been marked as a duplicate of this bug. ***
Package: abrt-1.1.13-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I was generating backtrace for crashed Eclipse (in OpenJDK) 2. 3.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Tried to send a crash report of LyX 2. Agreed to send the backtrace 3. abrt crashed
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Use wrong (old) password when trying to report to bugzilla 2. 3. Comment ----- Versions: abrt-1.1.13-2.fc14.x86_64
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Tryed to generate backtrace info for a bugreport (for psi messenger) 2. That took over two hours, so i canceled it 3. Tried it againt and it worked but then i got this error
Package: abrt-1.1.13-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Executing automatic Bug 2.Crash 3.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Crash while fetching backtrace for mutter. Not sure if it's reproducible.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) Comment ----- Clicked to report a crash.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Report gtk-gnash 2.Stuck in generating backtrace 3.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. Comment ----- I'm getting this crash when i'm report a bug with ABRT
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. writing comment to new bug 2. freeze aplication 3.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.was reporting a crash from hugin 2.filled in the info 3.got tired of waiting on the "generating backtrace" dialog 4.left pc on overnight, when checked status in the morning the "generating backtrace" dialog was still open 5.got the crash when closed the dialog via the window manager "x" (close gadget) Comment ----- Was reporting a crash from hugin, got tired of waiting on the "generating backtrace" dialog, got the crash when closed the dialog via the window manager "x" (close gadget).
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Attempted to send a bug report. 2. Error message appeared .
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. many tabs open (on line radio, facebook, yahoo mail, grooveshark, etc) 2. when opening yahoo mail, impossible to proceed, chrashes at all time 3. unsure how to repeat the exact crash, but it does very often in a number of situations. Comment ----- See point 3. Opera so far is better than FF, although I need FF for Zotero, FB and email (opera is not reliable). Thanks
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.trying to write a bugreport 2.freeze 3.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. problem
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.abrt was busy downloading debuginfo packages for an unrelated crash report 2.after it was done downloading/installing debuginfo packages, abrt stopped making progress 3.closed abrt, then reopened it to finish reporting original crash report and abrt had it's own crash report to submit
Since this bug seems to affect lots of people, we need to backport the fix from the git repository, or prepare a new fix for the current version. I am going to work on it during this week.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. set now bug 2. 3.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) Comment ----- Was attempting to report java openjdk crash. Genratiing backtrace never completed and had to close dialog. Which caused this crash of abort.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Reporting for a bug in gnome-panel. 2. Was stuck on "generating backtrace" for several minutes. 3. I closed the abrt window. 4. Clicked on "Report" button again. 5. Crash detected in abrt.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I think I was generating report for metacity crash.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open xsane (Applications::Graphics::Scanner Tool) 2. Splash screen appears 3. Splash screen disappears, the real windows attempt to open and immediatly disappear - crash. Comment ----- Fresh Fedora 14 install. My scanner is an HP Officejet 6500 all-in-one I am able to scan using "Simple Scan"
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) Comment ----- Opening some backtrace for something.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) Comment ----- I was reporting a bug to Shotwell.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Started video call with service
Package: abrt-1.1.13-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Running abrt 2. 3.
Package: abrt-1.1.13-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- when I trying to sent you a bug
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Not sure, froze up while trying to generate backtrace 2. 3. Comment ----- Not sure what happened.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.start ABRT and view one bug 2.crash ABRT 3. Comment ----- This bug which I processing is about compiz crash
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. ABRT hangs while processing a large backtrace 2. Close ABRT window
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.just try to send bug report. 2. 3.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Sending a bug report about openjdk this came up 2. 3.
abrt-1.1.14-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/abrt-1.1.14-1.fc14
abrt-1.1.14-1.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/abrt-1.1.14-1.fc13
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- ABRT seemed to have locked up while generating a backtrace for another program crash. I closed the dialog window, resulting in ABRT crashing.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Source unknown, seen in ABRT after using ABRT.
abrt-1.1.14-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/abrt-1.1.14-1.fc14
*** Bug 652346 has been marked as a duplicate of this bug. ***
*** Bug 653065 has been marked as a duplicate of this bug. ***
*** Bug 653446 has been marked as a duplicate of this bug. ***
*** Bug 651850 has been marked as a duplicate of this bug. ***
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Eclipse CDT crash 2. ABRT open and i try to report 3. ABRT try to create the backtrace, but never end Comment ----- I try to wait half a hour witout sucess. I edit /etc/abrt/abrt.conf and change MaxCrashReport = 0 to remove the limit of reports (was the default 1000 MiB).
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.don't know why, sudden get this error. 2. 3.
*** Bug 655271 has been marked as a duplicate of this bug. ***
abrt-1.1.14-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
abrt-1.1.14-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.