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 510174 - crash in File Browser: I was going into the pro...
crash in File Browser: I was going into the pro...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-17 13:23 UTC by Carlos
Modified: 2008-01-17 19:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Carlos 2008-01-17 13:23:22 UTC 
Version: 2.18.3

What were you doing when the application crashed?
I was going into the properties of the pendrive.


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 78311424 vsize: 78311424 resident: 27119616 share: 16363520 rss: 27119616 rss_rlim: 4294967295
CPU usage: start_time: 1200575658 rtime: 436 utime: 394 stime: 42 cutime:123 cstime: 34 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6d0c6b0 (LWP 5372)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 185701

Thread 1 (Thread 0xb6d0c6b0 (LWP 5372))

  • #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 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (17 sec old) ---------------------
** (gnome-cups-icon:5171): WARNING **: IPP request failed with status 1280
capplet-common-Message: cleanup_cb: Enter
xscreensaver: 08:13:56: 0: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 08:13:56: 0: for window 0x2000583 (nautilus / Nautilus)
xscreensaver: 08:14:01: -1: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 08:14:01: -1: for window 0x2000583 ((null) / (null))
** (gnome-cups-icon:5171): WARNING **: No se pudo iniciar el icono de la bandeja del sistema porque no se pudo contactar con el servidor CUPS.
/usr/lib/iceweasel/firefox-bin: Symbol `SSL_ImplementedCiphers' has different size in shared object, consider re-linking
xscreensaver: 08:17:45: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 08:17:45: 0: for window 0x20002c1 (gnome-terminal / Gnome-terminal)
xscreensaver: 08:19:40: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 08:19:40: 0: for window 0x20002c1 (gnome-terminal / Gnome-terminal)
xscreensaver: 08:21:26: 0: unrecognised ClientMessage "_NET_ACTIVE_WINDOW" received
xscreensaver: 08:21:26: 0: for window 0x240001c (file-roller / File-roller)
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-17 19:05:18 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 355018 ***