Hide Forgot
abrt 1.0.9 detected a crash. architecture: i686 Attached file: backtrace cmdline: pino comment: Pino crashes when I click on buttons in it. Each time it is started, something different triggers the crash. component: pino executable: /usr/bin/pino global_uuid: 6908adf5411311ab73a01b6f9bcb26e1b649ab51 kernel: 2.6.33.2-41.fc13.i686 package: pino-0.2.6-1.fc13 rating: 4 reason: Process /usr/bin/pino was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open Pino 2. Click on any of the toolbar buttons until it crashes
Created attachment 407214 [details] File: backtrace
Uninstalling and reinstalling pino fixes this it would appear.
pino-0.2.7-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/pino-0.2.7-1.fc13
--- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
pino-0.2.7-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
This still occurs as of 0.2.8. However, switching off "Enable window and button sounds" in the sound preferences capplet makes this not occur.
Would you get me a stack trace? http://fedoraproject.org/wiki/StackTraces It appears Pino is just triggering a bug elsewhere in the stack but a stack trace would be very useful to drill down on the details.
Created attachment 413929 [details] Stack trace I had to run this in gdb because abrtd doesn't seem to work for some reason.
This appears to not occur with Pino 0.2.10.
*** Bug 583969 has been marked as a duplicate of this bug. ***
The assert failure in pa_tls_set must have been fixed upstream by http://code.google.com/p/pino-twitter/source/detail?r=7774350dc5badd40807cf8d9d46f29b879f3f5c7 which removed the repeated calls to xmlCleanupParser(). This commit is present in 0.2.10. See http://lists.fedoraproject.org/pipermail/devel/2010-January/129117.html for explanation what's wrong with xmlCleanupParser().
*** Bug 596077 has been marked as a duplicate of this bug. ***
*** Bug 597844 has been marked as a duplicate of this bug. ***