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 520583 - crash in Open Folder:
crash in Open Folder:
Status: RESOLVED DUPLICATE of bug 519050
Product: nautilus
Classification: Core
Component: general
2.21.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-05 19:47 UTC by JP Rosevear
Modified: 2008-03-06 16:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description JP Rosevear 2008-03-05 19:47:34 UTC 
Version: 2.21.92

What were you doing when the application crashed?



Distribution: openSUSE 11.0 (i586) Alpha2
Gnome Release: 2.21.91 2008-03-03 (SUSE)
BugBuddy Version: 2.21.90

System: Linux 2.6.24.1-6-default #1 SMP 2008/02/22 15:49:32 UTC i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gilouche
Icon Theme: Industrial

Memory status: size: 115769344 vsize: 115769344 resident: 14573568 share: 21794816 rss: 36368384 rss_rlim: 1806254080
CPU usage: start_time: 1204746323 rtime: 207 utime: 189 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb68e46d0 (LWP 30600)]
[New Thread 0xb38f2b90 (LWP 30614)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 191417

Thread 1 (Thread 0xb68e46d0 (LWP 30600))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/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 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 trash_state_changed_cb
    at nautilus-pathbar.c line 211
  • #10 g_cclosure_marshal_VOID__BOOLEAN
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #12 ??
    from /usr/lib/libgobject-2.0.so.0
  • #13 ??
  • #14 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (77669 sec old) ---------------------
[TypeConverter       ][DEBUG  ] Convert note/tomboy -> note using [('note', 'note', {})] (TypeConverter.py:208)
DEBUG:TypeConverter:Convert note/tomboy -> note using [('note', 'note', {})]
[TypeConverter       ][DEBUG  ] [('note', 'note', {})] (TypeConverter.py:149)
DEBUG:TypeConverter:[('note', 'note', {})]
[TypeConverter       ][DEBUG  ] Skipping note -> note (TypeConverter.py:167)
DEBUG:TypeConverter:Skipping note -> note
[Syncronization      ][INFO   ] Putting data note://tomboy/85473ef4-e947-4e86-bcb1-d9955973a1cb --> None into EvoMemoTwoWay-file:///home/jpr/.evolution/memos/local/system (Synchronization.py:37)
INFO:Syncronization:Putting data note://tomboy/85473ef4-e947-4e86-bcb1-d9955973a1cb --> None into EvoMemoTwoWay-file:///home/jpr/.evolution/memos/local/system
[modules.Evolution   ][INFO   ] Creating new object (EvolutionModule.py:84)
INFO:modules.Evolution:Creating new object
[modules.Tomboy      ][DEBUG  ] Getting note: note://tomboy/49685404-8133-4c35-8eeb-a850bc94ece2 (TomboyModule.py:157)
DEBUG:modules.Tomboy:Getting note: note://tomboy/49685404-8133-4c35-8eeb-a850bc94ece2
[Syncronization      ][DEBUG  ] 1WAY PUT: Tomboy Notes (note://tomboy/49685404-8133-4c35-8eeb-a850bc94ece2) -----> Evolution Memos (Synchronization.py:454)
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-03-06 16:32:25 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 519050 ***