centos5 terminal crash after installation of updates

General support questions including new installations
Post Reply
ArthurFsun
Posts: 5
Joined: 2015/09/15 11:39:42

centos5 terminal crash after installation of updates

Post by ArthurFsun » 2015/09/15 11:43:59

I had installed Centos 5.9 in my x86_64 system and I installed update yesterday. Just now after I initiated the system, I found it has been upgraded to centos 5.11. But the bad thing is now I cannot open a terminal. When I try to open a terminal, it just gives out a bug buddy window. It reads,"The information about the crash has been successfully collected. Please provide some background about what you were doing when the application crashed.A valid email address is required. This will allow developers to contact you for more information if necessary.Sensitive data may be present in the debug information, so please review details below if you are concerned about transmitting passwords or other sensitive data."
But when I send the message, it failed:"Bug Buddy has encountered an error while submitting your report to the Bugzilla server. Details of the error are included below:Unable to analyze the response to XML-RPC ."

I don't know whether the terminal crash error was cause by intalling the updates. How could I fix this? Thanks in advance

Best regard

Yeping Sun

aks
Posts: 3073
Joined: 2014/09/20 11:22:14

Re: centos5 terminal crash after installation of updates

Post by aks » 2015/09/15 20:12:52

A lot of missing information.
Start simple, can you open a terminal while not in X?

ArthurFsun
Posts: 5
Joined: 2015/09/15 11:39:42

Re: centos5 terminal crash after installation of updates

Post by ArthurFsun » 2015/09/15 23:15:45

I can open consoles by Ctrl+Alt+F1~6 in the graphic interface, but when right click terminal in the graphic interface, a bug buddy window comes up, just like the information I gave above. And the bug buddy window give some error codes:


Code: Select all

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

Memory status: size: 252891136 vsize: 252891136 resident: 6291456 share: 5001216 rss: 6291456 rss_rlim: -1
CPU usage: start_time: 1442359230 rtime: 1 utime: 1 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

0x0000003a9340e0d5 in __libc_waitpid (pid=8539, stat_loc=0x7fff9d45ef9c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
32          return INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
#0  0x0000003a9340e0d5 in __libc_waitpid (pid=8539, stat_loc=0x7fff9d45ef9c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
#1  0x0000003082856be7 in ?? () from /usr/lib64/libgnomeui-2.so.0
#2  <signal handler called>
#3  0x00002af1909d2761 in gconv () from /usr/lib64/gconv/ISO8859-1.so
#4  0x0000003a92c1f1b4 in __gconv (cd=0x2457110, inbuf=0x7fff9d45f638, 
    inbufend=0x7fff9d45f75f "", outbuf=0x7fff9d45f640, 
    outbufend=<value optimized out>, irreversible=0x7fff9d45f590)
    at gconv.c:80
#5  0x0000003a92c1e7af in iconv (cd=0x2457098, inbuf=0x7fff9d45f638, 
    inbytesleft=0x7fff9d45f630, outbuf=0x245af5c, outbytesleft=0x7fff9d45f628)
    at iconv.c:53
#6  0x0000003f56218aaa in g_convert_with_iconv () from /lib64/libglib-2.0.so.0
#7  0x0000003f56218e3f in g_convert () from /lib64/libglib-2.0.so.0
#8  0x000000000040fe4a in gnome_vfs_get_mime_type ()
#9  0x0000000000419739 in gnome_vfs_get_mime_type ()
#10 0x0000003a92c1e144 in __libc_start_main (
    main=0x419140 <gnome_vfs_get_mime_type+39464>, argc=1, 
    ubp_av=0x7fff9d45fa98, init=<value optimized out>, 
    fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7fff9d45fa88) at libc-start.c:220
#11 0x000000000040f759 in gnome_vfs_get_mime_type ()
#12 0x00007fff9d45fa88 in ?? ()
#13 0x0000000000000000 in ?? ()

Thread 1 (process 8537):
#0  0x0000003a9340e0d5 in __libc_waitpid (pid=8539, stat_loc=0x7fff9d45ef9c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32
        oldtype = <value optimized out>
        result = <value optimized out>
#1  0x0000003082856be7 in ?? () from /usr/lib64/libgnomeui-2.so.0
No symbol table info available.
#2  <signal handler called>
No symbol table info available.
#3  0x00002af1909d2761 in gconv () from /usr/lib64/gconv/ISO8859-1.so
No symbol table info available.
#4  0x0000003a92c1f1b4 in __gconv (cd=0x2457110, inbuf=0x7fff9d45f638, 
    inbufend=0x7fff9d45f75f "", outbuf=0x7fff9d45f640, 
    outbufend=<value optimized out>, irreversible=0x7fff9d45f590)
    at gconv.c:80
        last_start = 0x7fff9d45f700 " !\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~"
        last_step = 1
        result = <value optimized out>
        fct = 0x2af1909d2530 <gconv>
        __PRETTY_FUNCTION__ = "__gconv"
#5  0x0000003a92c1e7af in iconv (cd=0x2457098, inbuf=0x7fff9d45f638, 
    inbytesleft=0x7fff9d45f630, outbuf=0x245af5c, outbytesleft=0x7fff9d45f628)
    at iconv.c:53
        instart = 0x7fff9d45f700 " !\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~"
        outstart = 0x24571a0 "Pp\364\222:"
        irreversible = <value optimized out>
        result = <value optimized out>
        __PRETTY_FUNCTION__ = "iconv"
#6  0x0000003f56218aaa in g_convert_with_iconv () from /lib64/libglib-2.0.so.0
No symbol table info available.
#7  0x0000003f56218e3f in g_convert () from /lib64/libglib-2.0.so.0
No symbol table info available.
#8  0x000000000040fe4a in gnome_vfs_get_mime_type ()
No symbol table info available.
#9  0x0000000000419739 in gnome_vfs_get_mime_type ()
No symbol table info available.
#10 0x0000003a92c1e144 in __libc_start_main (
    main=0x419140 <gnome_vfs_get_mime_type+39464>, argc=1, 
    ubp_av=0x7fff9d45fa98, init=<value optimized out>, 
    fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7fff9d45fa88) at libc-start.c:220
        result = <value optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {251568172032, 
                -4991263815003668972, 0, 140735831997072, 0, 0, 
                4991187450693025300, -4985944922116850156}, 
              mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7fff9d45fa90, 
              0x0}, data = {prev = 0x0, cleanup = 0x0, 
              canceltype = -1656358256}}}
        not_first_call = <value optimized out>
#11 0x000000000040f759 in gnome_vfs_get_mime_type ()
No symbol table info available.
#12 0x00007fff9d45fa88 in ?? ()
No symbol table info available.
#13 0x0000000000000000 in ?? ()
No symbol table info available.
A debugging session is active.

    Inferior 1 [process 8537] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
Would these help fix my problem?

ArthurFsun
Posts: 5
Joined: 2015/09/15 11:39:42

Re: centos5 terminal crash after installation of updates

Post by ArthurFsun » 2015/09/16 15:50:10

When I use the command "gnome-terminal" in console (initiated by Ctrl+Alt+F1), I get the following error message:

(gnome-terminal:4702): Gtk-WARNING**:cannot open display

How is it caused? How to fix it?

Thank you in advance.

gerald_clark
Posts: 10642
Joined: 2005/08/05 15:19:54
Location: Northern Illinois, USA

Re: centos5 terminal crash after installation of updates

Post by gerald_clark » 2015/09/16 16:44:39

That is not what he meant.
You did not specify what terminal you are having problems with.
Can you open a normal text terminal when not in X?
Gnome terminal cannot open without X.
If you are running aterm or xterm, or rxvt in X can you run gnome-terminal from within that terminal?
If not, what error messages do you get?

ArthurFsun
Posts: 5
Joined: 2015/09/15 11:39:42

Re: centos5 terminal crash after installation of updates

Post by ArthurFsun » 2015/09/17 15:47:53

That is not what he meant.
You did not specify what terminal you are having problems with.
Can you open a normal text terminal when not in X?
Gnome terminal cannot open without X.
If you are running aterm or xterm, or rxvt in X can you run gnome-terminal from within that terminal?
If not, what error messages do you get?
gerald_clark

Posts: 9792
Joined: 2005/08/05 15:19:54
Location: Northern Illinois, USA

Actually I don't really know the exact definitions of different terminals. But it is the gnome-terminal that gets wrong. When I try to open a gnome-terminal by right-click the mouse and click the "terminal" option from the appeared menu, a bug buddy window comes up which reports the crash of gnome-terminal, as I described in the above posts.

In the desktop interface, by Ctrl+Alt+F1, I can enter the text terminal. What do you call this terminal? In this terminal, when I input "xterm", I get the following error:

xterm Xt error: Can't open display: %s
xterm: DISPLAY is not set

Also in this text terminal, if I input the command "gnome-terminal", I get the following error:

(gnome-terminal:4869): Gtk-WARNING **: cannot open display:

However, if I input the command "aterm" or "rxvt", I can open a aterm or a rxvt terminal. In these two terminals, when I input the command "gnome-terminal", the same bug buddy windows comes up as when right-click the terminal option in desktop interface.

Although I can use aterm or rxvt, but I still feel gnome-terminal is the most convenient for me. So I strongly expect to fix it. Could anyone do some help?

aks
Posts: 3073
Joined: 2014/09/20 11:22:14

Re: centos5 terminal crash after installation of updates

Post by aks » 2015/09/17 16:10:06

When I use the command "gnome-terminal" in console (initiated by Ctrl+Alt+F1), I get the following error message:

(gnome-terminal:4702): Gtk-WARNING**:cannot open display

How is it caused? How to fix it?
That's a red herring - you can't run gnome-terminal outside of Gnome (and gnome requires X to be running).
In the desktop interface, by Ctrl+Alt+F1, I can enter the text terminal. What do you call this terminal? In this terminal, when I input "xterm", I get the following error:

xterm Xt error: Can't open display: %s
xterm: DISPLAY is not set
Ditto for xterm - which requires X (the clue is in the name).

Seemingly you can access "conventional" terminals (well ttys) via CTRL+ALT+Fx.
What seems broken is gnome-terminal and/or very important parts of Gnome (to wit, libgnomeui, libglib etc.).

Have you changed them? I guess the easiest way to check is rpm -Va to verify all files. Can you run other terminals (like xterm) within your X session? Also, just a guess, but have you got your locale setup correctly?

Post Reply