GNOME Bugzilla – Bug 140336
Closing "About" dialogue crashes camorama
Last modified: 2005-08-29 16:24:20 UTC
Distribution: Debian testing/unstable Package: camorama Severity: normal Version: GNOME2.4.1 0.17 Gnome-Distributor: GNOME.Org Synopsis: Closing "About" dialogue crashes camorama Bugzilla-Product: camorama Bugzilla-Component: User Interface Bugzilla-Version: 0.17 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Having opened the "About" dialog, and chosen the "Close" button, camorama crashes Steps to reproduce the crash: 1. start camorama 2. select "About" from the menu 3. click the "Close" button Expected Results: camorama will crashes How often does this happen? Every time Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/camorama' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1086264736 (LWP 16483)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x406613ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 46124
Thread 1 (Thread 1086264736 (LWP 16483))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-17 23:51 ------- Unknown version 0.17 in product camorama. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "camorama". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Duplicate *** This bug has been marked as a duplicate of 120953 ***
I think this was marked as a duplicate by mistake. Reopening.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
No response, closing. Please reopen if you can provide the requested information.