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 542046 - crash in Computer:
crash in Computer:
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-07-08 13:58 UTC by gauthier.sibille
Modified: 2008-07-08 21:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description gauthier.sibille 2008-07-08 13:58:51 UTC 
Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: ClearlooksClassic
Icon Theme: nuoveXT-1.6

Memory status: size: 122839040 vsize: 122839040 resident: 30420992 share: 16412672 rss: 30420992 rss_rlim: 4294967295
CPU usage: start_time: 1215525675 rtime: 99 utime: 88 stime: 11 cutime:0 cstime: 0 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 0xb6b97720 (LWP 5514)]
(no debugging symbols found)
0xb734a3d1 in waitpid () from /lib/libpthread.so.0

+ Trace 202319

Thread 1 (Thread 0xb6b97720 (LWP 5514))

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


----------- .xsession-errors (4220 sec old) ---------------------
Use of uninitialized value $fn in string eq at /usr/share/perl/5.10/File/Find.pm line 437.
Use of uninitialized value $fn in substitution (s///) at /usr/share/perl/5.10/File/Find.pm line 441.
Use of uninitialized value $fn in concatenation (.) or string at /usr/share/perl/5.10/File/Find.pm line 443.
Use of uninitialized value $fn in substr at /usr/share/perl/5.10/File/Find.pm line 445.
Use of uninitialized value $Name in substr at /usr/share/perl/5.10/File/Find.pm line 514.
Use of uninitialized value $fn in string eq at /usr/share/perl/5.10/File/Find.pm line 437.
Use of uninitialized value $fn in substitution (s///) at /usr/share/perl/5.10/File/Find.pm line 441.
Use of uninitialized value $fn in concatenation (.) or string at /usr/share/perl/5.10/File/Find.pm line 443.
Use of uninitialized value $fn in substr at /usr/share/perl/5.10/File/Find.pm line 445.
Use of uninitialized value $Name in substr at /usr/share/perl/5.10/File/Find.pm line 514.
Use of uninitialized value $fn in string eq at /usr/share/perl/5.10/File/Find.pm line 437.
Use of uninitialized value $fn in substitution (s///) at /usr/share/perl/5.10/File/Find.pm line 441.
Use of uninitialized value $fn in concatenation (.) or string at /usr/share/perl/5.10/File/Find.pm line 443.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 A. Walton 2008-07-08 21:55:04 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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