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 374672 - crash in Open Folder: Abrir Servidores de Red
crash in Open Folder: Abrir Servidores de Red
Status: RESOLVED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-13 13:42 UTC by jgm
Modified: 2006-12-29 16:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jgm 2006-11-13 13:42:51 UTC 
What were you doing when the application crashed?
Abrir Servidores de Red


Distribution: openSUSE 10.2 (i586) Beta2
Gnome Release: 2.16.1 2006-11-07 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 104620032 vsize: 0 resident: 104620032 share: 0 rss: 10448896 rss_rlim: 0
CPU usage: start_time: 1163420316 rtime: 0 utime: 2225 stime: 0 cutime:1878 cstime: 0 timeout: 347 it_real_value: 0 frequency: 38

Backtrace was generated from '/opt/gnome/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 -1227847040 (LWP 24609)]
[New Thread -1303102576 (LWP 26888)]
(no debugging symbols found)
0xb7f87410 in ?? ()

+ Trace 86055







Comment 1


Diego Escalante Urrelo (not reading bugmail)





          2006-11-14 04:42:09 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 364864 ***






Comment 2


Karsten Bräckelmann





          2006-11-14 09:26:12 UTC
        



Nope, this is not the same issue. Well, actually hard to tell, cause the automatically gathered stacktrace doesn't show the actual crash at all.







Comment 3


Karsten Bräckelmann





          2006-11-14 09:27:11 UTC
        



Thanks for taking the time to report this bug.

Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols?

Please see http://live.gnome.org/GettingTraces for more information on how to do so.  Thanks!







Comment 4


Bruno Boaventura





          2006-12-29 16:41:15 UTC
        



Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!