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 404751 - crash in Open Folder: descomprimir un fichero ...
crash in Open Folder: descomprimir un fichero ...
Status: RESOLVED DUPLICATE of bug 368534
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 404752 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-02-05 21:23 UTC by josertd
Modified: 2007-02-21 20:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description josertd 2007-02-05 21:23:09 UTC
What were you doing when the application crashed?
descomprimir un fichero rar y mover ficheros a una carpeta recién creada	


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 226902016 vsize: 226902016 resident: 37744640 share: 20770816 rss: 37744640 rss_rlim: -1
CPU usage: start_time: 1170687790 rtime: 1501 utime: 1359 stime: 142 cutime:274 cstime: 38 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 47108434434640 (LWP 5953)]
(no debugging symbols found)
0x00002ad84582ceef in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47108434434640 (LWP 5953))

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

Comment 1 Bruno Boaventura 2007-02-05 22:21:28 UTC
*** Bug 404752 has been marked as a duplicate of this bug. ***
Comment 2 Marc-Andre Lureau 2007-02-05 23:57:07 UTC
Fixed in the development version. The fix will be available in the next major release. Thank you for your bug report.


*** This bug has been marked as a duplicate of 352592 ***
Comment 3 André Klapper 2007-02-21 16:55:19 UTC
@marc-andre: the problem with the traces in bug 352592, bug 368958 and bug 368534 is that they are very generic. the traces do not exactly match each other, and alex (nautilus dev) told me that "it's hard to tell, would be nice to see the assert output". perhaps this is nitpicking, but i'd really like to try to keep nautilus bugzilla as clean as possible, because the nautilus-2.16 situation was already pretty critical a few months ago.
thanks for all the work and help!
Comment 4 André Klapper 2007-02-21 16:55:49 UTC
Josertd: Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 368534 ***
Comment 5 Marc-Andre Lureau 2007-02-21 20:24:57 UTC
@andre: thanks to you, you are a real bug *killer*! I would like to have enough time to help more - hopefully, guys like you are tracking everything ;)

Regarding the nautilus bugs, what do you mean exactly? that I should have marked the bug as duplicate of bug 368534? Ok, I will pay careful attention next time.

I was always wondering how you manage to find duplicate for evolution. This is kind of harder.

Thanks again!