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 462279 - crash in Home Folder: Pesquisando usando o bot...
crash in Home Folder: Pesquisando usando o bot...
Status: RESOLVED DUPLICATE of bug 454799
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-31 20:36 UTC by hugolf
Modified: 2007-07-31 21:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description hugolf 2007-07-31 20:36:48 UTC
What were you doing when the application crashed?
Pesquisando usando o botão de pesquisa existente na barra superior.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 138690560 vsize: 138690560 resident: 50327552 share: 23281664 rss: 50327552 rss_rlim: 4294967295
CPU usage: start_time: 1185880352 rtime: 14185 utime: 13056 stime: 1129 cutime:26 cstime: 13 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208666400 (LWP 2447)]
[New Thread -1299887216 (LWP 6035)]
(no debugging symbols found)
0x00b70402 in __kernel_vsyscall ()

Thread 2 (Thread -1299887216 (LWP 6035))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strstr
    from /lib/libc.so.6
  • #5 ??
  • #6 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #7 ??
  • #8 ??
  • #9 ??


----------- .xsession-errors (7611 sec old) ---------------------
==========================================================================
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, s16le, 64.0 kbit/4.54% (ratio: 8005->176400)
Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg))
==========================================================================
AO: [alsa] 44100Hz 2ch s16le (2 bytes per sample)
Starting playback...
A:   3.0 V:   3.0 A-V:  0.006 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   3.0 V:   3.0 A-V: -0.016 ct: -0.003   2/  2 ??% ??% ??,?% 0 0              
A:   3.0 V:   3.1 A-V: -0.042 ct: -0.0
A: 932.6 V: 932.4 A-V:  0.190 ct:  0.019 340/340 ??% ??% ??,?% 0 0              
A: 932.6 V: 932.5 A-V:  0.171 ct:  0.022 341/341 ??% ??% ??,?% 0 0              
A: 932.7 V: 932.5 A-V:  0.167 ct:  0.0
A:1121.4 V:1121.2 A-V:  0.202 ct:  0.020 550/550 ??% ??% ??,?% 0 0              
A:1121.4 V:1121.2 A-V:  0.182 ct:  0.024 551/551 ??% ??% ??,?% 0 0              
A:1121.4 V:1121.3 A-V:  0.179 ct:  0.0
A:1154.4 V:1154.3 A-V:  0.154 ct:  0.015 578/578 ??% ??% ??,?% 0 0              
A:1154.4 V:1154.3 A-V:  0.139 ct:  0.019 579/579 ??% ??% ??,?% 0 0              
A:1161.3 V:1161.1 A-V:  0.207 ct:  0.0
A:1206.8 V:1206.6 A-V:  0.124 ct:  0.012 859/859 ??% ??% ??,?% 0 0              
A:1222.9 V:1222.8 A-V:  0.119 ct:  0.012 860/860 ??% ??% ??,?% 0 0              
A:1222.9 V:1222.8 A-V:  0.107 ct:  0.0
A:1254.5 V:1254.2 A-V:  0.218 ct:  0.022 971/971 ??% ??% ??,?% 0 0              
A:1254.5 V:1254.3 A-V:  0.196 ct:  0.025 972/972 ??% ??% ??,?% 0 0              
A:1254.5 V:1254.3 A-V:  0.193 ct:  0.0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Martin Wehner 2007-07-31 21:42:02 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 454799 ***