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 675564 - Crash when trying to acces iFile webserver (iPod Touch 2g)
Crash when trying to acces iFile webserver (iPod Touch 2g)
Status: RESOLVED DUPLICATE of bug 675259
Product: nautilus
Classification: Core
Component: Location Bar
3.4.x
Other Linux
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-05-06 14:00 UTC by sandrotolksdorf
Modified: 2012-05-10 20:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description sandrotolksdorf 2012-05-06 14:00:44 UTC
When I try to access the iFile Webserver with the IP 192.168.178.24 on Port 10000, the nautilus window segfaults.
Comment 1 Cosimo Cecchi 2012-05-08 17:30:46 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 sandrotolksdorf 2012-05-08 22:25:13 UTC
Here is the stack trace you requested:

gdb nautilus
GNU gdb (GDB) 7.4.1
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
(gdb) run
Starting program: /usr/bin/nautilus 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0x7fffeb86f700 (LWP 7336)]
[New Thread 0x7fffeb06e700 (LWP 7337)]
[New Thread 0x7fffea665700 (LWP 7338)]
[New Thread 0x7fffd3b0a700 (LWP 7339)]
[New Thread 0x7fffd2695700 (LWP 7340)]
[New Thread 0x7fffcbfff700 (LWP 7341)]
[New Thread 0x7fffcb7fe700 (LWP 7342)]
[New Thread 0x7fffd1e94700 (LWP 7343)]
[New Thread 0x7fffd1693700 (LWP 7344)]
[New Thread 0x7fffd0e92700 (LWP 7345)]
[New Thread 0x7fffcaffd700 (LWP 7346)]
[New Thread 0x7fffca7fc700 (LWP 7347)]
[Thread 0x7fffeb06e700 (LWP 7337) exited]
[Thread 0x7fffca7fc700 (LWP 7347) exited]
[Thread 0x7fffd3b0a700 (LWP 7339) exited]
[Thread 0x7fffcb7fe700 (LWP 7342) exited]
[Thread 0x7fffd0e92700 (LWP 7345) exited]
[Thread 0x7fffd1693700 (LWP 7344) exited]
[Thread 0x7fffcbfff700 (LWP 7341) exited]
[Thread 0x7fffd2695700 (LWP 7340) exited]
[Thread 0x7fffd1e94700 (LWP 7343) exited]

Program received signal SIGSEGV, Segmentation fault.
nautilus_file_invalidate_attributes (file=file@entry=0x0, file_attributes=1023) at nautilus-file.c:7402
7402		nautilus_directory_cancel_loading_file_attributes (file->details->directory,
(gdb) 


I hope it helps you fixing the problem. If you need any further information please ask.

Thanks
Comment 3 Cosimo Cecchi 2012-05-08 22:40:16 UTC
Can you post a full trace please? When gdb stops, type "bt" into the prompt and paste the output you get.paste the output

Also, do you get this crash when typing the address directly in the location bar by hand? I just fixed a similar crash in git master.
Comment 4 sandrotolksdorf 2012-05-09 11:14:45 UTC
Here is the full trace:

(gdb) bt
  • #0 nautilus_file_invalidate_attributes
    at nautilus-file.c line 7402
  • #1 nautilus_file_invalidate_all_attributes
    at nautilus-file.c line 7436
  • #2 got_file_info_for_view_selection_callback
    at nautilus-window-manage-views.c line 823
  • #3 ready_callback_call
    at nautilus-directory-async.c line 1275
  • #4 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1857
  • #5 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_iteration
    from /usr/lib/libglib-2.0.so.0
  • #8 g_application_run
    from /usr/lib/libgio-2.0.so.0
  • #9 main
    at nautilus-main.c line 101

Yes, I type the location in by hand.
Comment 5 Cosimo Cecchi 2012-05-09 22:43:01 UTC
Okay, so this is turned out to be the same bug I had in mind, which is fixed in git master (and will be fixed in the next 3.4.2 release soon too).

*** This bug has been marked as a duplicate of bug 675259 ***
Comment 6 sandrotolksdorf 2012-05-10 20:16:14 UTC
OK, thanks for taking your time to look at it. Keep up the good work.