After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 374723 - crash in gThumb Image Viewer: connecting creative zen ...
crash in gThumb Image Viewer: connecting creative zen ...
Status: RESOLVED DUPLICATE of bug 372412
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2006-11-13 15:33 UTC by notrenneks
Modified: 2007-01-05 13:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description notrenneks 2006-11-13 15:33:34 UTC 
What were you doing when the application crashed?
connecting creative zen vision M mp3 player



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 85295104 vsize: 0 resident: 85295104 share: 0 rss: 17092608 rss_rlim: 0
CPU usage: start_time: 1163431926 rtime: 0 utime: 228 stime: 0 cutime:180 cstime: 0 timeout: 48 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gthumb'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226910032 (LWP 18513)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 86090

Thread 1 (Thread -1226910032 (LWP 18513))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 ??
    from /usr/lib/libgphoto2/2.2.1/ptp2.so
  • #6 ??
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2006-11-13 18:00:37 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 2


Michael Chudobiak





          2006-11-29 19:22:36 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!







Comment 3


Michael Chudobiak





          2007-01-05 13:03:36 UTC
        



This is actually a duplicate of bug 372412.

*** This bug has been marked as a duplicate of 372412 ***