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 493198 - (svillalba) crash in File Browser: View propierties of imag...
(svillalba)
crash in File Browser: View propierties of imag...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-03 22:40 UTC by svillalba
Modified: 2007-11-06 11:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description svillalba 2007-11-03 22:40:18 UTC
Version: 2.18.3

What were you doing when the application crashed?
View propierties of image jpg into Desktop


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 69152768 vsize: 69152768 resident: 19574784 share: 14082048 rss: 19574784 rss_rlim: 4294967295
CPU usage: start_time: 1194129643 rtime: 89 utime: 83 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

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

Thread 1 (Thread 0xb6e256b0 (LWP 5969))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "sebastian"
/etc/gdm/Xsession: Beginning session setup...
SESSION_MANAGER=local/pulga:/tmp/.ICE-unix/5891
Advertencia del gestor de ventanas: Ocurrió un error al leer el archivo de sesión guardado /home/sebastian/.metacity/sessions/default0.ms: Falló al abrir el archivo «/home/sebastian/.metacity/sess
** Message: No iniciando el servidor de escritorio remoto
Initializing gnome-mount extension
** Message: drive = 0
** Message: volume = 0
(gnome-panel:5968): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24
Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store))
aborting...
--------------------------------------------------
Comment 1 André Klapper 2007-11-05 08:00:55 UTC
Thanks for taking the time to report this bug.
Unfortunately, the 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.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui.

More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 svillalba 2007-11-05 23:56:18 UTC
(In reply to comment #1)
> Thanks for taking the time to report this bug.
> Unfortunately, the 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.
> 
> Could you please help fixing this by installing some debugging packages [1],
> start the application as normal, and try to reproduce the crash, if possible?
> 
> Once bug-buddy pops up, you can find the stacktrace in the 'Details', now
> containing way more information. Please copy that stacktrace and paste it as a
> comment here. Thanks in advance!
> 
> [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2,
> libgnome, and libgnomeui.
> 
> More details can be found here: http://live.gnome.org/GettingTraces

Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 71192576 vsize: 71192576 resident: 23875584 share: 15560704 rss: 23875584 rss_rlim: 4294967295
CPU usage: start_time: 1194300810 rtime: 418 utime: 368 stime: 50 cutime:20 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6d756b0 (LWP 4042)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6d756b0 (LWP 4042))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/cmov/libc.so.6
  • #6 abort
    from /lib/i686/cmov/libc.so.6
  • #7 IA__g_logv
  • #8 IA__g_log
  • #9 IA__g_assert_warning
  • #10 gtk_list_store_compare_func
    at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 1677
  • #11 node_find_closest
    at gsequence.c line 1136
  • #12 node_insert_sorted
    at gsequence.c line 1301
  • #13 g_sequence_sort_changed_iter
    at gsequence.c line 566
  • #14 gtk_list_store_sort_iter_changed
    at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 1758
  • #15 IA__gtk_list_store_set_valist
    at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 901
  • #16 IA__gtk_list_store_set
    at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 934
  • #17 ??
    from /usr/lib/libeel-2-2.18.so
  • #18 ??
  • #19 ??
  • #20 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (5012 sec old) ---------------------
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:864:(snd_pcm_dmix_open) unable to open slave
...Too much output, ignoring rest...
--------------------------------------------------

Best regards
Comment 3 André Klapper 2007-11-06 11:00:01 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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