Bug 140483 – Crashed when I wasn't even doing anything in Nautilus.

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 140483 - Crashed when I wasn't even doing anything in Nautilus.


Summary:	Crashed when I wasn't even doing anything in Nautilus.


Status:	RESOLVED DUPLICATE of bug 108205

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.2.x
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2004-04-20 01:38 UTC by kim.karlsson
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.1/2.2

Description kim.karlsson 2004-04-19 11:38:20 UTC

Package: nautilus
Severity: critical
Version: 2.2.1
Synopsis: Crashed when I wasn't even doing anything in Nautilus.
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
Was working in Kylix 3 and a terminal when nautilus crashed.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?
First time, so quite rarely.

Additional Information:




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1088002944 (LWP 13608)]
[New Thread 1184049216 (LWP 13627)]
[New Thread 1175660736 (LWP 13626)]
[New Thread 1167272256 (LWP 13625)]
[New Thread 1158883776 (LWP 13624)]
[New Thread 1150495296 (LWP 13623)]
[New Thread 1142106816 (LWP 13622)]
[New Thread 1133718336 (LWP 13621)]
[New Thread 1125329856 (LWP 13620)]
[New Thread 1116941376 (LWP 13619)]
[New Thread 1099668672 (LWP 13618)]
0xffffe002 in ??
    ()

+ Trace 46175

Thread 1 (Thread 1088002944 (LWP 13608))

#0 ??
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 gtk_widget_get_toplevel
at gtkwidget.c line 5356
#4 gtk_main_get_window_group
at gtkmain.c line 1569
#5 gtk_main_do_event
at gtkmain.c line 1394
#6 gdk_event_dispatch
at gdkevents-x11.c line 2018
#7 g_get_current_time
from /usr/lib/libglib-2.0.so.0
#8 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#11 gtk_main
at gtkmain.c line 1092
#12 main
#13 __libc_start_main
from /lib/tls/libc.so.6
#0 ??





------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-19 21:38 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Martin Wehner 2004-04-19 15:03:23 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 108205 ***