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 478212 - crash in Home Folder: ao plugar um ipod e abri...
crash in Home Folder: ao plugar um ipod e abri...
Status: RESOLVED DUPLICATE of bug 425157
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 481542 486736 487185 487410 488013 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-18 23:08 UTC by jose.rob.jr
Modified: 2007-11-04 23:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
backtrace for nautilus crash. (25.28 KB, text/plain)
2007-11-02 15:20 UTC, Hussam Al-Tayeb
Details

Description jose.rob.jr 2007-09-18 23:08:10 UTC
What were you doing when the application crashed?
ao plugar um ipod e abrir o nautilus em /media/IPOD o computador ficou extremamente lento e nenhum arquivo foi exibido na janela (talvez por conta do lag). Reiniciei o X no atalho do teclado e loguei de novo. Os icones do desktop e o papel de parede não foi carregado. Tentei abrir o nautilus pelo menu do gnome e nada (isso com o pc ainda lento porque não tirei o ipod). Reiniciei o X denovo e mudei a sessão para fluxbox. Abri o nautilus no menu dele e fui até /media/IPOD. Consegui abrir com escrita normalmente (criei um diretório pra testar). Passei os arquivos e na hora de desmontar eu fiz manualmente. umount /media/IPOD. após este comando uma janela de depuração de erros apareceu (estou escrevendo nela), e o ipod continuou falando que não podia remover o cabo. Repeti o comando, mas parecia que já estava desmontado, então removi o cabo assim mesmo. 

Resumo: o gnome travou quando pluguei o ipod. mas não acredito que foi o nautilus porque usei ele no fluxbox. Quando desmontei manualmente apareceu uma janela pra reportar erros (na qual estou escrevendo)


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.2 2007-08-18 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-gentoo-r2 #1 Sat Sep 1 20:55:05 BRT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: OSX

Memory status: size: 246210560 vsize: 246210560 resident: 30814208 share: 19034112 rss: 30814208 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190156053 rtime: 231 utime: 199 stime: 32 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47019221691568 (LWP 14284)]
0x00002ac3820abb0f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47019221691568 (LWP 14284))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    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 nautilus_connect_background_to_file_metadata
  • #9 ??
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 ??
  • #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 ---------------------
(nautilus:14284): Eel-CRITICAL **: wrap_table_get_num_fitting: assertion `max_child_size > 0' failed
(nautilus:14284): Eel-CRITICAL **: wrap_table_get_num_fitting: assertion `max_child_size > 0' failed
apps file failure
apps file failure
(nautilus:14284): Eel-CRITICAL **: wrap_table_get_num_fitting: assertion `max_child_size > 0' failed
(nautilus:14284): Eel-CRITICAL **: wrap_table_get_num_fitting: assertion `max_child_size > 0' failed
apps file failure
** (nautilus:14284): WARNING **: destroyed file still being monitored
** ERROR **: file nautilus-directory-background.c: line 616 (nautilus_connect_background_to_file_metadata): assertion failed: (NAUTILUS_IS_FILE (old_file))
aborting...
--------------------------------------------------
Comment 1 palfrey 2007-10-15 12:46:28 UTC
*** Bug 486736 has been marked as a duplicate of this bug. ***
Comment 2 Christian Kirbach 2007-10-19 22:27:38 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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 3 Christian Kirbach 2007-10-19 22:27:39 UTC
*** Bug 487410 has been marked as a duplicate of this bug. ***
Comment 4 Christian Kirbach 2007-10-19 22:27:48 UTC
*** Bug 488013 has been marked as a duplicate of this bug. ***
Comment 5 Christian Kirbach 2007-10-19 22:28:00 UTC
*** Bug 487185 has been marked as a duplicate of this bug. ***
Comment 6 Christian Kirbach 2007-10-19 22:28:13 UTC
*** Bug 481542 has been marked as a duplicate of this bug. ***
Comment 7 André Klapper 2007-10-21 16:45:42 UTC
Thanks for taking the time to report this bug.
Unfortunately, the 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 help fixing this by installing some debugging packages [1], start the application as normal, and try to 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] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui.

More details can be found here: http://live.gnome.org/GettingTraces
Comment 8 Hussam Al-Tayeb 2007-11-02 15:20:48 UTC
Created attachment 98386 [details]
backtrace for nautilus crash.

if the backtrace is still missing anything, please let me know.
Comment 9 Jürg Billeter 2007-11-04 20:08:30 UTC
Reopening as a better backtrace has been attached.
Comment 10 André Klapper 2007-11-04 23:27:01 UTC
ah, thanks. this is the same issue as bug 425157, therefore marking as a duplicate.

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