Bug 432192 – crash in System Log: running in background, n...

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 432192 - crash in System Log: running in background, n...


Summary:	crash in System Log: running in background, n...


Status:	RESOLVED DUPLICATE of bug 378764

Product:	gnome-utils
Classification:	Deprecated
Component:	logview
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-04-22 09:08 UTC by paulthompson
Modified:	2007-04-22 13:40 UTC

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

Description paulthompson 2007-04-22 09:08:21 UTC

Version: 2.16.0

What were you doing when the application crashed?
running in background, no user interaction


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 17:27:49 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 173150208 vsize: 0 resident: 173150208 share: 0 rss: 52903936 rss_rlim: 0
CPU usage: start_time: 1177075886 rtime: 0 utime: 5881 stime: 0 cutime:5271 cstime: 0 timeout: 610 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/sbin/gnome-system-log'

(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 -1208695088 (LWP 26596)]
0x00419402 in __kernel_vsyscall ()

+ Trace 129683

Thread 1 (Thread -1208695088 (LWP 26596))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/libc.so.6
#5 name_sort_func
at gtkfilechooserdefault.c line 5836
#6 gtk_tree_model_sort_level_find_insert
at gtktreemodelsort.c line 1739
#7 gtk_tree_model_sort_row_inserted
at gtktreemodelsort.c line 1787
#8 _gtk_marshal_VOID__BOXED_BOXED
at gtkmarshalers.c line 1346
#9 IA__g_closure_invoke
at gclosure.c line 490
#10 signal_emit_unlocked_R
at gsignal.c line 2440
#11 IA__g_signal_emit_valist
at gsignal.c line 2199
#12 IA__g_signal_emit
at gsignal.c line 2243
#13 IA__gtk_tree_model_row_inserted
at gtktreemodel.c line 1496
#14 do_files_added
at gtkfilesystemmodel.c line 1755
#15 IA__g_cclosure_marshal_VOID__POINTER
at gmarshal.c line 601
#16 IA__g_closure_invoke
at gclosure.c line 490
#17 signal_emit_unlocked_R
at gsignal.c line 2440
#18 IA__g_signal_emit_valist
at gsignal.c line 2199
#19 IA__g_signal_emit_by_name
at gsignal.c line 2267
#20 fs_module_create
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#21 actually_dispatch_callback
at gnome-vfs-monitor.c line 284
#22 g_idle_dispatch
at gmain.c line 3928
#23 IA__g_main_context_dispatch
at gmain.c line 2045
#24 g_main_context_iterate
at gmain.c line 2677
#25 IA__g_main_loop_run
at gmain.c line 2881
#26 IA__gtk_main
at gtkmain.c line 1148
#27 gtk_main_quit
at gtkmain.c line 1209
#28 __libc_start_main
from /lib/libc.so.6
#29 gtk_main_quit
at gtkmain.c line 1209
#0 __kernel_vsyscall



----------- .xsession-errors (18 sec old) ---------------------
starting indexing...
indexing #1 - /root/Desktop
flushing all words
Finished indexing. Waiting for new events...
You can not run beagle as root.  Beagle is designed to run from your own
user account.  If you want to create multiuser or system-wide indexes, use
the beagle-build-index tool.
You can override this setting using the beagle-config or beagle-settings tools.
Introspect error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the ne
Introspect error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the ne
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
** (bug-buddy:5724): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Comment 1 Bruno Boaventura 2007-04-22 13:40:21 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 378764 ***