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 490458 - crash in Open Folder: clicked on "Properties" ...
crash in Open Folder: clicked on "Properties" ...
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-10-26 09:40 UTC by djacovkis
Modified: 2007-11-09 14:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
stack trace (9.84 KB, text/plain)
2007-11-07 15:39 UTC, djacovkis
Details

Description djacovkis 2007-10-26 09:40:31 UTC
Version: 2.18.3

What were you doing when the application crashed?
clicked on "Properties" of an ODT file through the right-click menu. Have observed the same behaviour with JPEG files as well.


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: Gorilla
Icon Theme: Tango

Memory status: size: 82927616 vsize: 82927616 resident: 30883840 share: 18071552 rss: 30883840 rss_rlim: 4294967295
CPU usage: start_time: 1193387961 rtime: 2032 utime: 1892 stime: 140 cutime:0 cstime: 1 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 0xb6d696b0 (LWP 6560)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6d696b0 (LWP 6560))

  • #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 ---------------------
** Message: volume = 0
Can't create calendar for 2 (gdata, http://www.google.com/calendar/feeds/bm5ogikmm81q2b7nsiajqjophg%40group.calendar.google.com/private-a8aa388a68e0c7a3b3fa8546562dca84/basic): TypeError: Components.c
Can't create calendar for 3 (gdata, http://www.google.com/calendar/feeds/hvk95i64mc4eulqm0s3968ina0%40group.calendar.google.com/private-43f9f8cd8a351378c088c284520c02a9/basic): TypeError: Components.c
Can't create calendar for 4 (gdata, http://www.google.com/calendar/feeds/hq0u5rh22l5o65v2aduevcpsnk%40group.calendar.google.com/private-5224bcaf8b1df0a0a436d4996f51ec99/basic): TypeError: Components.c
** Message: drive = 0
** Message: volume = 0
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00055 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c00055 (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.0/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store))
aborting...
--------------------------------------------------
Comment 1 Christoph Wolk 2007-10-26 16:44:13 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 and reopen this bug or report a new one. Thanks in advance!
Comment 2 djacovkis 2007-11-07 15:39:59 UTC
Created attachment 98723 [details]
stack trace
Comment 3 djacovkis 2007-11-07 15:42:13 UTC
Reproduced the bug on an empty file, see the attached stack trace in #2.
Comment 4 Christoph Wolk 2007-11-09 14:27:02 UTC
Thanks for reporting back with such a nice stack trace!

I am quite sure that this is a duplicate of bug 440988, which results from
version incompatibilities. Updating some packages will likely fix it, see that
bug for more information.

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