Gnome unstable unusable /usr/bin/gnome-panel killed sig 11

General support questions
ChrisTheBA
Posts: 27
Joined: 2014/06/10 22:05:16

Gnome unstable unusable /usr/bin/gnome-panel killed sig 11

Post by ChrisTheBA » 2015/04/29 20:58:49

Newbie and not even knowing how to see what my video driver is. I read some article here regarding an Nvidia update, and rollback to 340 display. The steps attempted merely said that the package requested didn't even exist. I don't even know that's my video card (but it likely is nvidia 4xxx series?, maybe).

When updates were applied (1 week back?) and system was rebooted, starting Gnome produces display jerking up and down, and no menu displayed. System is borderline unusable, and I must have Desktop running for my file backups product Crashplan to run(!) So I'm running Gnome even though loggin in causes the display to go mad.

/usr/bin/gnome-panel process /usr/bin/gnome-panel was killed by signal 11.

This has been occurring about a week, and two recent patches have no effect. I'm not knowledgeable enough to even know how to look at, remove, or upgrade a display driver. Is that even what it is?

Please help,
Chris

giulix63
Posts: 1305
Joined: 2014/05/14 10:06:37
Location: UK

Re: Gnome unstable unusable /usr/bin/gnome-panel killed sig

Post by giulix63 » 2015/04/30 07:10:51

Try this: Get as far as you can in the booting process, then switch to a console typing Ctrl-Alt-F2. Login as root and install inxi from epel:

Code: Select all

yum install inxi
Then please post the output of:

Code: Select all

inxi -GS
grep \(EE\) `ls -ltr /var/log/Xorg*log |awk '{print $9}' |tail -1`
using CentOS pastebin. Also please describe what sort of system we're talking about (server/desktop/notebook/etc. brand, model).
Root is evil: Do not use root (sudo) to run any of the commands specified in my posts unless explicitly indicated. Please, provide the necessary amount of context to understand your problem/question.

ChrisTheBA
Posts: 27
Joined: 2014/06/10 22:05:16

Re: Gnome unstable unusable /usr/bin/gnome-panel killed sig

Post by ChrisTheBA » 2015/05/04 19:03:56

Run result was as follows:

[chris@centos65 inxi]$ inxi -GS
System: Host: centos65 Kernel: 2.6.32-504.16.2.el6.x86_64 x86_64 (64 bit)
Console: tty 0 Distro: CentOS release 6.6 (Final)
Graphics: Card: Advanced Micro Devices [AMD/ATI] RV610 [Radeon HD 2400 PRO/XT]
Display Server: N/A drivers: ati,radeon (unloaded: vesa,fbdev)
tty size: 80x24 Advanced Data: N/A out of X
[chris@centos65 inxi]$


However that command produced:

$ grep /{EE}\ 'ls -ltr /var/log/Xorg*log |awk '{print $9}' |tail -1'
-bash: [chris@centos65: command not found
[chris@centos65 inxi]$ grep: } |tail -1: No such file or directory
-bash: grep:: command not found
tail: option used in invalid context -- 1


I originally built this to run Windows XP, it's got a Winfast motherboard, single core Athlon processor, 1GB RAM, with onboard sound, video, network etc. et. al.
Thanks!

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

Re: Gnome unstable unusable /usr/bin/gnome-panel killed sig

Post by gerald_clark » 2015/05/04 19:54:15

grep \(EE\) `ls -ltr /var/log/Xorg*log |awk '{print $9}' |tail -1`
grep /{EE}\ 'ls -ltr /var/log/Xorg*log |awk '{print $9}' |tail -1'

DO you see the 4 mistakes you made there?

ChrisTheBA
Posts: 27
Joined: 2014/06/10 22:05:16

Re: Gnome unstable unusable /usr/bin/gnome-panel killed sig

Post by ChrisTheBA » 2015/05/14 20:31:19

[chris@centos65 ~]$ grep \(EE\) `ls -ltr /var/log/Xorg*log |awk '{print $9}' |tail -1`
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 432.930] (EE) Server terminated successfully (0). Closing log file.

ChrisTheBA
Posts: 27
Joined: 2014/06/10 22:05:16

Re: Gnome unstable unusable /usr/bin/gnome-panel killed sig

Post by ChrisTheBA » 2015/05/14 20:41:43

I have no idea what all that's about. But when I boot into Windows XP, Device Manager Shows me a ATI Radeon HD 2400 XT. Since the introduction to Linux class never even addresses drivers I have no idea how to uninstall, update, replace or configure a driver that's blown up. Alas.

Where might I find a tutorial, and how does one stop those automatic updates that we need/must install, from thrashing old unsupported hardware that was working, but updates take out of compatibility? Are installation scripts for driver updates not checking that the hardware they're installing to is even compatible? That seems to be a rather serous oversight.

lightman47
Posts: 1522
Joined: 2014/05/21 20:16:00
Location: Central New York, USA

Re: Gnome unstable unusable /usr/bin/gnome-panel killed sig

Post by lightman47 » 2015/05/15 12:14:05

and how does one stop those automatic updates that we need/must install,
Don't say yes to them. No updates are done without your approval.

giulix63
Posts: 1305
Joined: 2014/05/14 10:06:37
Location: UK

Re: Gnome unstable unusable /usr/bin/gnome-panel killed sig

Post by giulix63 » 2015/05/16 08:11:00

Just erase them. What does

Code: Select all

rpm -qa |grep nvidia
return?
Root is evil: Do not use root (sudo) to run any of the commands specified in my posts unless explicitly indicated. Please, provide the necessary amount of context to understand your problem/question.

ChrisTheBA
Posts: 27
Joined: 2014/06/10 22:05:16

Re: Gnome unstable unusable /usr/bin/gnome-panel killed sig

Post by ChrisTheBA » 2015/05/27 21:48:12

lightman47 wrote:
and how does one stop those automatic updates that we need/must install,
Don't say yes to them. No updates are done without your approval.

My concern is that the command line update 'sudo yum...' finds and ask to install ALL updates.
It gives you a chance to install them all y/N. If i say N, I get no updates, including what may be security updates I need?
Or is there a way I can deselect some updates, and choose to receive the rest? Remember, I cannot run Gnome or a graphical GUI since it's crashed currently.

ChrisTheBA
Posts: 27
Joined: 2014/06/10 22:05:16

Re: Gnome unstable unusable /usr/bin/gnome-panel killed sig

Post by ChrisTheBA » 2015/05/27 21:58:10

giulix63 wrote:Just erase them. What does

Code: Select all

rpm -qa |grep nvidia
return?

I don't know what 'Just erase them' means. Erase what, and how?


To answer the question :

rpm -qa | grep nvidia
returns nothing. Nothing happens.
I've finally figured out I'm not using an Nvidia card, I think, maybe.

So circling back to the very beginning, I need to figure out why I'm seeing


Gnome was killed by signal 11, and my screen is jumping up and down rapidly, before it completely crashes the entire system if left running for about five minutes. I am able, if I do it quickly, to do an "sudo init 3" and recover back to text level mode, but it has to be quick before the entire system crash.

-frustrated
Chris

Post Reply