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 330940 - crash when switching from one picture to the next
crash when switching from one picture to the next
Status: RESOLVED DUPLICATE of bug 338800
Product: eog
Classification: Core
Component: general
2.12.x
Other other
: High critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-02-13 01:09 UTC by bfields
Modified: 2006-07-14 19:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description bfields 2006-02-13 01:09:43 UTC
Distribution: Debian testing/unstable
Package: EOG
Severity: Normal
Version: GNOME2.12.2 2.12.3
Gnome-Distributor: Debian
Synopsis: crash when switching from one picture to the next
Bugzilla-Product: EOG
Bugzilla-Component: general
Bugzilla-Version: 2.12.3
BugBuddy-GnomeVersion: 2.0 (2.12.1)
Description:
Description of the crash:

crashes (dumps me straight into dialog asking me if I want to run
bug-buddy)

Steps to reproduce the crash:
1. started eog with a dozen or so jpegs
2. browsed for a while
3. crash happened as I was using arrow key to switch to a new picture

Expected Results:


How often does this happen?

Not reliably reproduceable; happens maybe once out of 30 times or so


Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224508640 (LWP 14173)]
[New Thread -1236976720 (LWP 14175)]
[New Thread -1227457616 (LWP 14174)]
(no debugging symbols found)
0xb7732231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread -1224508640 (LWP 14173))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 eog_image_get_uri
  • #4 _gnome_vfs_monitor_do_cancel
    from /usr/lib/libgnomevfs-2.so.0
  • #5 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #6 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug created by bug-buddy at 2006-02-13 01:09 -------


Unknown version 2.12.3 in product EOG.  Setting version to "2.12.x".

Comment 1 Jan Rathmann 2006-02-14 09:50:50 UTC
I experience the same problem, allthough the crashes are happening more often (probably every second time i start EOG). It seems totally random, on which pictures the crash appears, usually it works well if I restart EOG and browse to the same picture again. I'm using Ubuntu Breezy AMD64.


(In reply to comment #0)
> Distribution: Debian testing/unstable
> Package: EOG
> Severity: Normal
> Version: GNOME2.12.2 2.12.3
> Gnome-Distributor: Debian
> Synopsis: crash when switching from one picture to the next
> Bugzilla-Product: EOG
> Bugzilla-Component: general
> Bugzilla-Version: 2.12.3
> BugBuddy-GnomeVersion: 2.0 (2.12.1)
> Description:
> Description of the crash:
> 
> crashes (dumps me straight into dialog asking me if I want to run
> bug-buddy)
> 
> Steps to reproduce the crash:
> 1. started eog with a dozen or so jpegs
> 2. browsed for a while
> 3. crash happened as I was using arrow key to switch to a new picture
> 
> Expected Results:
> 
> 
> How often does this happen?
> 
> Not reliably reproduceable; happens maybe once out of 30 times or so
> 
> 
> Additional Information:
> 
> 
> 
> Debugging Information:
> 
> Backtrace was generated from '/usr/bin/eog'
> 
> (no debugging symbols found)
> Using host libthread_db library "/lib/tls/libthread_db.so.1".
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread -1224508640 (LWP 14173)]
> [New Thread -1236976720 (LWP 14175)]
> [New Thread -1227457616 (LWP 14174)]
> (no debugging symbols found)
> 0xb7732231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
> #0  0xb7732231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
> #1  0xb7de62db in libgnomeui_module_info_get () from
> /usr/lib/libgnomeui-2.so.0
> #2  <signal handler called>
> #3  0x08068b40 in eog_image_get_uri ()
> #4  0xb7d5929b in _gnome_vfs_monitor_do_cancel ()
>    from /usr/lib/libgnomevfs-2.so.0
> #5  0xb77a58d6 in g_main_context_wakeup () from
> /usr/lib/libglib-2.0.so.0
> #6  0xb77a3b8c in g_main_context_dispatch () from
> /usr/lib/libglib-2.0.so.0
> #7  0xb77a6f6b in g_main_context_check () from
> /usr/lib/libglib-2.0.so.0
> #8  0xb77a72c7 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
> #9  0xb7ab22e1 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
> #10 0x08063577 in main ()
> 
> Thread 3 (Thread -1227457616 (LWP 14174)):
> #0  0xb772eb91 in pthread_cond_wait@@GLIBC_2.3.2 ()
>    from /lib/tls/libpthread.so.0
> No symbol table info available.
> #1  0x0806cea1 in eog_image_list_iter_equal ()
> No symbol table info available.
> #2  0xb77c1a71 in g_static_private_free () from
> /usr/lib/libglib-2.0.so.0
> No symbol table info available.
> #3  0xb772ccfd in start_thread () from /lib/tls/libpthread.so.0
> No symbol table info available.
> #4  0xb76c113e in clone () from /lib/tls/libc.so.6
> No symbol table info available.
> 
> Thread 2 (Thread -1236976720 (LWP 14175)):
> #0  0xb772eb91 in pthread_cond_wait@@GLIBC_2.3.2 ()
>    from /lib/tls/libpthread.so.0
> No symbol table info available.
> #1  0x0806cea1 in eog_image_list_iter_equal ()
> No symbol table info available.
> #2  0xb77c1a71 in g_static_private_free () from
> /usr/lib/libglib-2.0.so.0
> No symbol table info available.
> #3  0xb772ccfd in start_thread () from /lib/tls/libpthread.so.0
> No symbol table info available.
> #4  0xb76c113e in clone () from /lib/tls/libc.so.6
> No symbol table info available.
> 
> Thread 1 (Thread -1224508640 (LWP 14173)):
> #0  0xb7732231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
> No symbol table info available.
> #1  0xb7de62db in libgnomeui_module_info_get () from
> /usr/lib/libgnomeui-2.so.0
> No symbol table info available.
> #2  <signal handler called>
> No symbol table info available.
> #3  0x08068b40 in eog_image_get_uri ()
> No symbol table info available.
> #4  0xb7d5929b in _gnome_vfs_monitor_do_cancel ()
>    from /usr/lib/libgnomevfs-2.so.0
> No symbol table info available.
> #5  0xb77a58d6 in g_main_context_wakeup () from
> /usr/lib/libglib-2.0.so.0
> No symbol table info available.
> #6  0xb77a3b8c in g_main_context_dispatch () from
> /usr/lib/libglib-2.0.so.0
> No symbol table info available.
> #7  0xb77a6f6b in g_main_context_check () from
> /usr/lib/libglib-2.0.so.0
> No symbol table info available.
> #8  0xb77a72c7 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
> No symbol table info available.
> #9  0xb7ab22e1 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
> No symbol table info available.
> #10 0x08063577 in main ()
> No symbol table info available.
> #0  0xb7732231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
> 
> 
> 
> 
> ------- Bug created by bug-buddy at 2006-02-13 01:09 -------
> 
> 
> Unknown version 2.12.3 in product EOG.  Setting version to "2.12.x".
> 

Comment 2 Lucas Rocha 2006-02-22 21:08:18 UTC
Can you reproduce this bug with EOG CVS HEAD?
Comment 3 Jan Rathmann 2006-02-22 21:29:31 UTC
I would gladly try this, but I have to admit I'm much more only a normal user than a developer. Thus I don't have much experiences with "larger software projects", I came that far that I found a webinterface for the eog cvs repository on this url:

http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&dir=eog

but if I try to click anything, I just get an error (/registry/file.cgi not found). So what is the best way to download the repository files?
Comment 4 bfields 2006-02-23 04:23:22 UTC
"Can you reproduce this bug with EOG CVS HEAD?"

Nope, looks good so far.  Not entirely conclusive, since it wasn't immediately reproduceable before.

(Minor whine: would it be too much trouble to provide build/install instructions in README and/or INSTALL?  I eventually noticed the spec file and figured it out from there, but getting to that point was kind of time consuming....

Note to Jan Rathman: the procedure was something like
export CVSROOT=:pserver:anonymous@anoncvs.gnome.org:/cvs/gnome
cvs login
cvs co eog
cd eog
./autogen.sh --prefix=/usr/local
make
make install

but it'll only succeed if you have some libraries and stuff installed; on debian I think I needed
apt-get build-dep eog
apt-get install gnome-common libgnome-desktop-2
)
Comment 5 Jan Rathmann 2006-02-23 09:01:26 UTC
 
> Note to Jan Rathman: the procedure was something like
> export CVSROOT=:pserver:anonymous@anoncvs.gnome.org:/cvs/gnome
> cvs login
> cvs co eog
> cd eog
> ./autogen.sh --prefix=/usr/local
> make
> make install
> 
> but it'll only succeed if you have some libraries and stuff installed; on
> debian I think I needed
> apt-get build-dep eog
> apt-get install gnome-common libgnome-desktop-2
> )
> 
OK, I tried that, the autogen.sh-script seems (at least) to run without errors, but when I try the make-command, it just says (translated to english):

make: *** No targets specified and no »make«-control-file found. closing.

I'm not sure what to do about it, i have checked that there are many files called "Makefile.am" in the subdirectories.
Comment 6 bfields 2006-02-24 00:12:01 UTC
> OK, I tried that, the autogen.sh-script seems (at least) to run without errors,
> but when I try the make-command, it just says (translated to english):
>
> make: *** No targets specified and no »make«-control-file found. closing.

I bet the autogen.sh script actually failed--it produces a lot of output, and my memory is that the first time I ran it (and it failed, because I didn't have some stuff installed) it wasn't totally obvious that it had failed.
Comment 7 Jan Rathmann 2006-02-24 07:25:52 UTC
> I bet the autogen.sh script actually failed--it produces a lot of output, and
> my memory is that the first time I ran it (and it failed, because I didn't have
> some stuff installed) it wasn't totally obvious that it had failed.
> 

I checked it again, seems that indeed it didn't report clearly that I had a too old version of automake installed. But still no success, now I get the following output by autogen.sh:

______________________________________

/usr/bin/gnome-autogen.sh
checking for autoconf >= 2.53...
  testing autoconf2.50... not found.
  testing autoconf... found 2.59
checking for automake >= 1.7...
  testing automake-1.7... not found.
  testing automake-1.8... not found.
  testing automake-1.9... found 1.9.5
checking for glib-gettext >= 2.2.0...
  testing glib-gettextize... found 2.8.3
checking for intltool >= 0.30...
  testing intltoolize... found 0.34.1
checking for pkg-config >= 0.14.0...
  testing pkg-config... found 0.19
checking for gnome-common >= 2.3.0...
  testing gnome-doc-common... found 2.12.0
Checking for required M4 macros...
Checking for forbidden M4 macros...
Processing ./configure.in
Running glib-gettextize... Ignore non-fatal messages.
Copying file mkinstalldirs
Copying file po/Makefile.in.in

Please add the files
  codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4
  progtest.m4
from the /usr/share/aclocal directory to your autoconf macro directory
or directly to your aclocal.m4 file.
You will also need config.guess and config.sub, which you can get from
ftp://ftp.gnu.org/pub/gnu/config/.

Running intltoolize...
Running gnome-doc-common...
Running aclocal-1.9...
aclocal:configure.in:135: warning: macro `AM_GCONF_SOURCE_2' not found in library
configure.in:32: warning: AC_ARG_PROGRAM invoked multiple times
Running autoconf...
configure.in:32: warning: AC_ARG_PROGRAM invoked multiple times
configure.in:135: error: possibly undefined macro: AM_GCONF_SOURCE_2
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.

_______________________________________


Make still fails with the same message, I obeyed the instructions in the autogen-output to copy/download the named files, but still no sucess. 


Comment 8 Lucas Rocha 2006-02-27 20:36:35 UTC
bfields, are you using EOG in a AMD64 machine too?
Comment 9 Jan Rathmann 2006-03-07 19:11:58 UTC
A maybe interesting update concerning this bug: The crashes only seems to appear if the EOG-Window is NOT maximized, if it is maximized, everything seems to run perfectly stable, very strange.
Comment 10 Damien Durand 2006-07-14 19:42:45 UTC

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