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 512698 - crash in Open Folder: this time - right after ...
crash in Open Folder: this time - right after ...
Status: RESOLVED DUPLICATE of bug 511406
Product: nautilus
Classification: Core
Component: general
2.21.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-29 01:16 UTC by nemes.sorin
Modified: 2008-01-29 08:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description nemes.sorin 2008-01-29 01:16:10 UTC 
Version: 2.21.6

What were you doing when the application crashed?
this time - right after the previous report ( I need to reboot because density of the crash window pop-up ) - the crash was present right after machine boot into my gnome


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.21.5 2008-01-15 (Ubuntu)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Aurora-looks
Icon Theme: nuoveXT.2.2

Memory status: size: 123564032 vsize: 123564032 resident: 35790848 share: 16060416 rss: 35790848 rss_rlim: 4294967295
CPU usage: start_time: 1201569142 rtime: 418 utime: 255 stime: 163 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/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6a576c0 (LWP 5858)]
[New Thread 0xb68eab90 (LWP 5977)]
(no debugging symbols found)
0xb7ef4410 in __kernel_vsyscall ()

+ Trace 187139

Thread 1 (Thread 0xb6a576c0 (LWP 5858))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
    from /lib/tls/i686/cmov/libc.so.6
  • #7 ??
    from /usr/lib/libgdk_pixbuf-2.0.so.0
  • #8 ??
  • #9 ??
    from /usr/lib/libglib-2.0.so.0
  • #10 ??
  • #11 ??
    from /lib/tls/i686/cmov/libpthread.so.0
  • #12 ??
  • #13 ??
    from /usr/lib/libgobject-2.0.so.0
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 g_object_get_qdata
    from /usr/lib/libgobject-2.0.so.0
  • #18 strtol
    from /lib/tls/i686/cmov/libc.so.6
  • #19 ??
  • #20 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (23 sec old) ---------------------
(gnome-settings-daemon:5802): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Window manager warning: Log level 8: g_object_unref: assertion `G_IS_OBJECT (object)' failed
xrdb:  "*Label.background" on line 220 overrides entry on line 150
xrdb:  "*Text.background" on line 226 overrides entry on line 191
xrdb:  "*Label.foreground" on line 232 overrides entry on line 151
xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
Initializing nautilus-open-terminal extension
** (nautilus:5858): WARNING **: Unable to add monitor: Not supported
(gnome-panel:5857): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
  PID TTY          TIME CMD
 5806 ?        00:00:00 pulseaudio
(update-notifier:5869): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Gianluca Borello 2008-01-29 08:54:34 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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