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 348069 - Crash on opening File Browser (nautilus)
Crash on opening File Browser (nautilus)
Status: RESOLVED DUPLICATE of bug 335114
Product: nautilus
Classification: Core
Component: Desktop
unspecified
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-20 01:07 UTC by fbruman
Modified: 2006-07-20 08:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description fbruman 2006-07-20 01:07:22 UTC
From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.14.0
Subject: Crash on opening File Browser (nautilus)

Distribution: Ubuntu 6.06 (dapper)
Package: nautilus
Severity: Normal
Version: GNOME2.14.2 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Crash on opening File Browser
Bugzilla-Product: nautilus
Bugzilla-Component: Desktop
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Copied a file in the already open File Browser, thereafter clicking an
USB memorystick on the Desktop expecting it to open the File Browser
showing the content of the USB device. This triggered the error and
Bug Buddy.

Steps to reproduce the crash:
1. Copy a file in an already open File Browser
2. (Left-)Click an USB device (memorystick) on the Desktop

Expected Results:
Triggering of error/crash message and Bug Buddy starting.

How often does this happen?
1.st time

Additional Information:
I've tried to reproduce the error but without any luck(!).
At the time of the crash I was running amaroK, Firestarter and a gnome-terminal
window (no jobs running though).

Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225598592 (LWP 5046)]
[New Thread -1227052112 (LWP 5069)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225598592 (LWP 5046))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_lookup
    from /usr/lib/libglib-2.0.so.0
  • #6 nautilus_file_get_string_attribute
  • #7 nautilus_file_get_string_attribute
  • #8 nautilus_directory_unref
  • #9 nautilus_directory_unref
  • #10 egg_recent_item_unref
  • #11 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #0 __kernel_vsyscall




-- 
All is One, except Zero




------- Bug created by bug-buddy at 2006-07-20 01:07 -------

Comment 1 Teppo Turtiainen 2006-07-20 08:24:18 UTC
Thanks for the bug report. 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?


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