Bug 387006 – crash in Home Folder: rpm -ivh magicor-1.0-0.2...

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 387006 - crash in Home Folder: rpm -ivh magicor-1.0-0.2...


Summary:	crash in Home Folder: rpm -ivh magicor-1.0-0.2...


Status:	RESOLVED INCOMPLETE

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-18 01:00 UTC by tekhug
Modified:	2007-03-04 23:24 UTC

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

Description tekhug 2006-12-18 01:00:00 UTC

What were you doing when the application crashed?
rpm -ivh magicor-1.0-0.2.rc2.fc6.noarch.rpm
et en même temps j utilsé gftp pour telecharger des paquet venant de ftp.belnet.be


Distribution: Red Hat Enterprise Linux Client release 4.92 (Tikanga)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 166780928 vsize: 0 resident: 166780928 share: 0 rss: 30314496 rss_rlim: 0
CPU usage: start_time: 1166367981 rtime: 0 utime: 2449335 stime: 0 cutime:1808797 cstime: 0 timeout: 640538 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208265008 (LWP 3178)]
(no debugging symbols found)
0x0035c402 in __kernel_vsyscall ()

+ Trace 95012

Thread 1 (Thread -1208265008 (LWP 3178))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/nosegneg/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_signal_get_invocation_hint
from /lib/libgobject-2.0.so.0
#5 g_signal_has_handler_pending
from /lib/libgobject-2.0.so.0
#6 g_signal_handlers_disconnect_matched
from /lib/libgobject-2.0.so.0
#7 gtk_ui_manager_new_merge_id
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_ui_manager_new_merge_id
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_ui_manager_new_merge_id
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_ui_manager_new_merge_id
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_ui_manager_new_merge_id
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_ui_manager_new_merge_id
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_ui_manager_get_ui
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#16 g_main_context_check
from /lib/libglib-2.0.so.0
#17 g_main_loop_run
from /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/i686/nosegneg/libc.so.6
#21 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 André Klapper 2006-12-22 00:58:22 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.
Could you please install some debugging packages [1], start nautilus as normal,
and reproduce the crash, if possible?
Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for nautilus, glib, gtk, pango, gnome-vfs and
libgnome(ui).
More details can be found here:
http://live.gnome.org/GettingTraces/DistroSpecificInstructions

Comment 2 André Klapper 2007-03-04 23:24:52 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!