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 365572 - crash in Image Viewer: clicked "previous", then...
crash in Image Viewer: clicked "previous", then...
Status: RESOLVED DUPLICATE of bug 348651
Product: eog
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-27 04:15 UTC by offby1
Modified: 2006-10-27 22:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description offby1 2006-10-27 04:15:52 UTC 
Version: 2.16.1

What were you doing when the application crashed?
clicked "previous", then "next"


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

Memory status: size: 78360576 vsize: 0 resident: 78360576 share: 0 rss: 29622272 rss_rlim: 0
CPU usage: start_time: 1161921569 rtime: 0 utime: 5399 stime: 0 cutime:5109 cstime: 0 timeout: 290 it_real_value: 0 frequency: 0

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

(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 -1226184512 (LWP 28563)]
[New Thread -1265177696 (LWP 28575)]
[New Thread -1227490400 (LWP 28570)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 78671

Thread 1 (Thread -1226184512 (LWP 28563))

  • #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 cmsSetLanguage
    from /usr/lib/liblcms.so.1
  • #5 ??
  • #0 __kernel_vsyscall 






Comment 1


Fabio Bonelli





          2006-10-27 14:42:37 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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






Comment 2


offby1





          2006-10-27 21:36:15 UTC
        



I don't know what questions you're referring to -- the only question I saw in that report was "could you provide a stack trace", and the other reporter already did.






Comment 3


Fabio Bonelli





          2006-10-27 22:39:02 UTC
        



Hi,

we need a stacktrace with debugging symbols. Those stacktraces aren't enough.
Thank you.