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 562379 - crash in Open Folder: clicked on a "mount poin...
crash in Open Folder: clicked on a "mount poin...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-26 21:06 UTC by wesc
Modified: 2008-11-29 09:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description wesc 2008-11-26 21:06:41 UTC
Version: 2.20.0

What were you doing when the application crashed?
clicked on a "mount point" in the left pane which should have (it has worked in the past) mounted an SMB share on a windows XP machine


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Tue May 27 15:38:35 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 99532800 vsize: 99532800 resident: 26189824 share: 10756096 rss: 26189824 rss_rlim: 4294967295
CPU usage: start_time: 1226278826 rtime: 7644 utime: 6480 stime: 1164 cutime:42 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ba3720 (LWP 5612)]
[New Thread 0xb3facb90 (LWP 22940)]
(no debugging symbols found)
0xb7f52424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6ba3720 (LWP 5612))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
QObject::connect: Cannot connect QSignal::intSignal(int) to (null)::popupClassViewAction( int )
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x42002c6 specified for 0x420027b (Find in Fi).
QObject::connect: Cannot connect QSignal::intSignal(int) to (null)::popupClassViewAction( int )
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x42002c6 specified for 0x420027b (Find in Fi).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x34002c6 specified for 0x340027b (Find in Fi).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x42002c6 specified for 0x420027b (Find in Fi).
QObject::connect: Cannot connect QSignal::intSignal(int) to (null)::popupClassViewAction( int )
QObject::connect: Cannot connect QSignal::intSignal(int) to (null)::popupClassViewAction( int )
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x42002c6 specified for 0x420027b (Find in Fi).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x42002c6 specified for 0x420027b (Find in Fi).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x42002c6 specified for 0x420027b (Find in Fi).
** (nautilus:5612): WARNING **: Hit unhandled case 46 (Timeout reached) in fm_report_error_loading_directory
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 A. Walton 2008-11-29 09:43:55 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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