GNOME Bugzilla – Bug 156354
crash on change from medium (default) to large image
Last modified: 2014-02-24 22:45:47 UTC
Distribution: Debian testing/unstable Package: camorama Severity: normal Version: GNOME2.8.1 0.17 Gnome-Distributor: Ubuntu Synopsis: crash on change from medium (default) to large image Bugzilla-Product: camorama Bugzilla-Component: User Interface Bugzilla-Version: 0.17 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Opened camorama. Picture was not right; black and white wavy lines. Thought I'd try to change the size of the window. Using the menu option to change from a "medium" picture to a large one produced the crash. Debugging Information: Backtrace was generated from '/usr/bin/camorama' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/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 1087333376 (LWP 6929)] (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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in __kernel_vsyscall ()
+ Trace 51297
Thread 1 (Thread 1087333376 (LWP 6929))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-10-24 23:27 ------- 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, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was thomas@lunde.net. 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.
Appears to be a unique stack trace.
*** Bug 342472 has been marked as a duplicate of this bug. ***
Short of the very last function call, the stacktraces for bug 154867, bug 156333 and bug 156354 are identical. Maybe those functions share a common issue?
This project is not under active development anymore. It is currently unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping (bug 725098) to reflect reality. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.