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 470320 - crash in System Log: I just configure the dov...
crash in System Log: I just configure the dov...
Status: RESOLVED DUPLICATE of bug 355887
Product: gnome-utils
Classification: Deprecated
Component: logview
2.16.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-26 00:42 UTC by Rajkumar_C
Modified: 2007-09-25 18:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Rajkumar_C 2007-08-26 00:42:14 UTC 
Version: 2.16.0

What were you doing when the application crashed?
I just configure the dovecot and view the log message during dovecot login.


Distribution: CentOS release 5 (Final)
Gnome Release: 2.16.0 2007-02-18 (CentOS)
BugBuddy Version: 2.16.0

Memory status: size: 307023872 vsize: 307023872 resident: 15220736 share: 7917568 rss: 15220736 rss_rlim: -1
CPU usage: start_time: 1188059086 rtime: 7961 utime: 7702 stime: 259 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496432864 (LWP 8365)]
(no debugging symbols found)
0x00000033f440d895 in waitpid () from /lib64/libpthread.so.0

+ Trace 157920

Thread 1 (Thread 46912496432864 (LWP 8365))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 strchr
    from /lib64/libc.so.6
  • #4 strrchr
    from /lib64/libc.so.6
  • #5 gtk_main_quit
  • #6 gtk_main_quit
  • #7 gtk_main_quit
  • #8 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #9 g_signal_override_class_closure
    from /lib64/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #12 gtk_tree_view_scroll_to_cell
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 gtk_tree_view_get_hadjustment
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 gtk_marshal_BOOLEAN__VOID
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #16 g_signal_override_class_closure
    from /lib64/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #19 gtk_widget_get_default_style
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #21 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #22 gdk_add_client_message_filter
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #23 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #24 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #26 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #27 gtk_main_quit
  • #28 __libc_start_main
    from /lib64/libc.so.6
  • #29 gtk_main_quit
  • #30 ??
  • #31 ??
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Emmanuele Bassi (:ebassi)





          2007-09-25 18:54:04 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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