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 462743 - crash in Terminal: Configuring Oracle
crash in Terminal: Configuring Oracle
Status: RESOLVED DUPLICATE of bug 161843
Product: gnome-terminal
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-02 10:37 UTC by cheema
Modified: 2007-08-02 17:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description cheema 2007-08-02 10:37:45 UTC
Version: 2.18.1

What were you doing when the application crashed?
Configuring Oracle


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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 58126336 vsize: 58126336 resident: 27574272 share: 21397504 rss: 27574272 rss_rlim: 4294967295
CPU usage: start_time: 1185999074 rtime: 644 utime: 511 stime: 133 cutime:36 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-terminal'

(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 -1208649488 (LWP 2874)]
[New Thread -1215100016 (LWP 2879)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208649488 (LWP 2874))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strlen
    from /lib/libc.so.6
  • #5 vfprintf
    from /lib/libc.so.6
  • #6 vasprintf
    from /lib/libc.so.6
  • #7 g_vasprintf
    from /lib/libglib-2.0.so.0
  • #8 g_strdup_vprintf
    from /lib/libglib-2.0.so.0
  • #9 g_print
    from /lib/libglib-2.0.so.0
  • #10 ??
  • #11 _gnome_marshal_BOOLEAN__INT_ENUM_BOOLEAN_ENUM_BOOLEAN
    from /usr/lib/libgnomeui-2.so.0
  • #12 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #16 ??
    from /usr/lib/libgnomeui-2.so.0
  • #17 _SmcProcessMessage
    from /usr/lib/libSM.so.6
  • #18 IceProcessMessages
    from /usr/lib/libICE.so.6
  • #19 ??
    from /usr/lib/libgnomeui-2.so.0
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #24 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
warning: .dynamic section for "/lib/libglib-2.0.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libORBitCosNaming-2.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libdbus-glib-1.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libavahi-glib.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Iestyn Pryce 2007-08-02 17:19:34 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 161843 ***