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 480332 - crash in System Log: some activities with vmw...
crash in System Log: some activities with vmw...
Status: RESOLVED DUPLICATE of bug 442846
Product: gnome-utils
Classification: Deprecated
Component: logview
2.18.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-25 18:36 UTC by brunoxm
Modified: 2007-09-25 18:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description brunoxm 2007-09-25 18:36:02 UTC 
Version: 2.18.1

What were you doing when the application crashed?
some activities with vmware and USB Windows Mobile. Trying to define a connection.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 60571648 vsize: 60571648 resident: 30781440 share: 23113728 rss: 30781440 rss_rlim: 4294967295
CPU usage: start_time: 1190731838 rtime: 128 utime: 120 stime: 8 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208498464 (LWP 3814)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 165435

Thread 1 (Thread -1208498464 (LWP 3814))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 _gnome_marshal_BOOLEAN__INT_ENUM_BOOLEAN_ENUM_BOOLEAN
    from /usr/lib/libgnomeui-2.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 ??
    from /lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /usr/lib/libgnomeui-2.so.0
  • #11 _SmcProcessMessage
    from /usr/lib/libSM.so.6
  • #12 IceProcessMessages
    from /usr/lib/libICE.so.6
  • #13 ??
    from /usr/lib/libgnomeui-2.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 ??
    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 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (8 sec old) ---------------------
(gnome-system-log:3814): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gnome-system-log:3814): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gnome-system-log:3814): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gnome-system-log:3814): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gnome-system-log:3814): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gnome-system-log:3814): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gnome-system-log:3814): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-3818--718481311-1190731916 --active --geometry 210x47+0+31 --title root@vms:~ --working-di
--------------------------------------------------
Comment 1 Emmanuele Bassi (:ebassi) 2007-09-25 18:38:14 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 442846 ***