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 434221 - crash in Computer: I was cutting pictures f...
crash in Computer: I was cutting pictures f...
Status: RESOLVED DUPLICATE of bug 362346
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-28 22:38 UTC by lowrider.vato
Modified: 2007-04-28 22:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description lowrider.vato 2007-04-28 22:38:09 UTC 
What were you doing when the application crashed?
I was cutting pictures from one folder and pasting them into another folder.


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 384581632 vsize: 384581632 resident: 16736256 share: 24158208 rss: 40894464 rss_rlim: 1792327680
CPU usage: start_time: 1177787208 rtime: 1826 utime: 1602 stime: 224 cutime:190 cstime: 35 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47033148764800 (LWP 5704)]
(no debugging symbols found)
0x00002ac6bf9dcc5f in waitpid () from /lib64/libpthread.so.0

+ Trace 131167

Thread 1 (Thread 47033148764800 (LWP 5704))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /opt/gnome/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #6 g_log
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #8 fm_directory_view_bump_zoom_level
  • #9 g_closure_invoke
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #10 g_signal_override_class_closure
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /opt/gnome/lib64/libgobject-2.0.so.0
  • #13 fm_directory_view_bump_zoom_level
  • #14 g_source_get_current_time
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #16 g_main_context_prepare
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /opt/gnome/lib64/libglib-2.0.so.0
  • #18 gtk_main
    from /opt/gnome/lib64/libgtk-x11-2.0.so.0
  • #19 POA_Nautilus_MetafileMonitor__init
  • #20 __libc_start_main
    from /lib64/libc.so.6
  • #21 g_cclosure_marshal_VOID__ENUM
  • #22 ??
  • #23 ??
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


palfrey





          2007-04-28 22:57:02 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 362346 ***