Bug 399515 – crash in Open Folder: apriva paggina web:www.t...

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 399515 - crash in Open Folder: apriva paggina web:www.t...


Summary:	crash in Open Folder: apriva paggina web:www.t...


Status:	RESOLVED DUPLICATE of bug 361777

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-22 19:46 UTC by pasqualebelle
Modified:	2007-01-23 00:14 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description pasqualebelle 2007-01-22 19:46:17 UTC

What were you doing when the application crashed?
apriva paggina web:www.tiscali.it


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 150736896 vsize: 0 resident: 150736896 share: 0 rss: 47714304 rss_rlim: 0
CPU usage: start_time: 1169487344 rtime: 0 utime: 5692 stime: 0 cutime:5116 cstime: 0 timeout: 576 it_real_value: 0 frequency: 2272

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226758480 (LWP 4751)]
[New Thread -1352156256 (LWP 5455)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 104373

Thread 1 (Thread -1226758480 (LWP 4751))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gdk_window_foreign_new_for_display
from /usr/lib/libgdk-x11-2.0.so.0
#5 _gtk_selection_request
from /usr/lib/libgtk-x11-2.0.so.0
#6 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#7 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#8 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#12 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#14 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#15 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#17 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 POA_Nautilus_MetafileMonitor__init
#20 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#21 ??
#0 __kernel_vsyscall

Comment 1 palfrey 2007-01-23 00:14:56 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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