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 480246 - crash in Home Folder: search for pidgin file
crash in Home Folder: search for pidgin file
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-09-25 14:53 UTC by love-peace999
Modified: 2007-09-29 00:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description love-peace999 2007-09-25 14:53:55 UTC 
What were you doing when the application crashed?
search for pidgin file


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.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 504369152 vsize: 504369152 resident: 33849344 share: 21946368 rss: 33849344 rss_rlim: 18446744073709551615
CPU usage: start_time: 1190731968 rtime: 151 utime: 139 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496372784 (LWP 8959)]
[New Thread 1168148816 (LWP 8985)]
(no debugging symbols found)
0x00000036cf4c82e6 in poll () from /lib64/libc.so.6

+ Trace 165382

Thread 2 (Thread 1168148816 (LWP 8985))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strstr
    from /lib64/libc.so.6
  • #4 ??
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomevfs-2.so.0
  • #7 gnome_vfs_directory_visit_uri
    from /usr/lib64/libgnomevfs-2.so.0
  • #8 ??
  • #9 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #10 start_thread
    from /lib64/libpthread.so.0
  • #11 clone
    from /lib64/libc.so.6 


----------- .xsession-errors (2890 sec old) ---------------------
you got it!!!!!!!!!!!!!111
IM: seq: 633645 ----- msg seq: 6257
sender version: 0x1103
EvaPacketManager::processReceiveIM -- Here we got
0: 18 a1 d7 42 24 c9 b4 6a 
8:  0  9 ab 2d db 85 31 4a 
16: 1f 40  0 84 11  3 18 a1 
24: d7 42 24 c9 b4 6a d1 76 
32: dd  6 57 78 61 99 66 cc 
40: 52  d 7c b6 12 1a  0 81 
48: 18 71 46 f9 15  e  1  2 
56:  0  0  0  1  0  0  0  0 
64:  0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2007-09-29 00:45:33 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 ***