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 463468 - crash in Open Folder:
crash in Open Folder:
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
: 464939 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-04 17:59 UTC by aeon
Modified: 2007-08-23 17:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description aeon 2007-08-04 17:59:22 UTC
Version: 2.18.3

What were you doing when the application crashed?



Distribution: Debian 3.1 (sarge)
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-1-amd64 #1 SMP Sun Jul 29 13:54:41 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks-graphite
Icon Theme: Crux

Memory status: size: 466513920 vsize: 466513920 resident: 38273024 share: 17403904 rss: 38273024 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186244684 rtime: 2289 utime: 2006 stime: 283 cutime:986 cstime: 45 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47688584867280 (LWP 26927)]
(no debugging symbols found)
0x00002b5f56d54c7f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47688584867280 (LWP 26927))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #4 g_log
    from /usr/lib/libglib-2.0.so.0
  • #5 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 g_sequence_sort_changed_iter
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_list_store_set_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_list_store_set
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libeel-2-2.18.so
  • #14 eel_mime_application_chooser_new
    from /usr/lib/libeel-2-2.18.so
  • #15 ??
  • #16 ??
  • #17 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #18 ??
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (26035 sec old) ---------------------
** (nm-applet:3176): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.15" is not allowed to own the service "or
** (nm-applet:3176): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.15" is not allowed to own the service "or
** (nm-applet:3176): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.15" is not allowed to own the service "or
** (nm-applet:3176): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.15" is not allowed to own the service "or
** (nm-applet:3176): WARNING **: <WARNING>	 nma_dbus_init (): nma_dbus_init() could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.15" is not allowed to own the service "or
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Susana 2007-08-06 15:11:20 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.
Could you please install some debugging packages [1], start the application as normal, and 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] debugging packages for nautilus, pango, gtk, glib, gnome-vfs, libgnome and libgnomeui. More details can be found here:
http://live.gnome.org/GettingTraces
Comment 2 Susana 2007-08-10 14:22:16 UTC
*** Bug 464939 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2007-08-23 17:31:48 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 ***