Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

I install gnome-shell-debuginfo, libgnome-desktop-3-2-debuginfo.

"After installing the relevant debugging information packages, just make the program crash again" -- OK

"Bug Buddy should then pop up and gather all information for you. You should then copy-and-paste the trace from bug-buddy into your previously filed bug report. We ask you to add the information as an attachment, if possible."

But Bug Buddy does not start automatically!

Then:
bug-buddy  --appname gnome-shell --pid 10374
bug-buddy  --appname gnome-shell --pid 10384

But: Bug Buddy не удалось определить версию рабочей среды GNOME. Возможно, не установлен компонент gnome-desktop. (Bug Buddy could not determine the version of the operating environment GNOME. Perhaps the component is not installed gnome-desktop)
(bug-buddy:11237): Gtk-WARNING **: Загружаемый модуль тем не найден в module_path: «murrine»,
I/O warning : failed to load external entity "/usr/share/gnome-about/gnome-version.xml"

But: libgnome-desktop-3-2 installed 
And: 
$cat /usr/share/gnome/gnome-version.xml 
<?xml version="1.0" encoding="UTF-8"?>
<gnome-version>
 <platform>3</platform>
 <minor>2</minor>
 <micro>1</micro>
 <distributor>SUSE</distributor>

Maybe I just will perform on the workstation you need a commands and will lay out their conclusion?

P.S. Buddy's bug is another story (bug report)...

(In reply to comment #3)

> P.S. Buddy's bug is another story (bug report)...
Affected version is Bug Buddy 2.32...hm...Why such an old version?...

I fear you'll have to get a backtrace by hand: :-(
https://live.gnome.org/GnomeShell/Debugging

(In reply to comment #5)
> I fear you'll have to get a backtrace by hand: :-(
> https://live.gnome.org/GnomeShell/Debugging

I'll do it, but a bit later...
P.S. I will use one computer for debugging.

Created attachment 206272 [details]
ScreenLog Of Debug

Something went wrong. Details in the attachment(In reply to comment #7)
> Created an attachment (id=206272) [details]
> ScreenLog Of Debug

Thanks, but there's been a problem when running the xenv.sh script:
/home/leon/bin/xenv.sh: line 2: /proc//environ: Нет такого файла или каталога (which means No such file or directory)

The problem is that 'pgrep -u $USER gnome-session' doesn't seem to have returned anything. Could you run this command from a shell and tell us what's the result? 

If the result is empty, you can simply set the gnome_session variable by hand to contain the PID: run 'ps ax|grep gnome-session', note the PID, and then run
'export gnome-session=(type PID here)' before calling the script.

Created attachment 206290 [details]
ScreeLog with replace variable on pid

Replay to Comment 9

Sorry, I really don't understand what you did in that session. Don't try to run gnome-shell in gdb until you're sure that the 'gnome_session' variable contains the right PID. Could you answer my questions verbally instead of posting that weird log? ;-)

(In reply to comment #11)
> Sorry, I really don't understand what you did in that session. Don't try to run
> gnome-shell in gdb until you're sure that the 'gnome_session' variable contains
> the right PID. Could you answer my questions verbally instead of posting that
> weird log? ;-)

pgrep -u $USER gnome-session works ---- this only works if I login via gnome-shell!

If I can not login via gnome-shell, and login to the VT2, then:
Command: pgrep -u $USER gnome-session ---empty output, i.e.:
$ pgrep -u $USER gnome-session
$

I ran this command: 
$pgrep -u gnome-session
$3590
I.e., gnome-shell is running, but not on behalf of the user

cat ~/bin/xenv.sh 
gnome_session=$(pgrep -u $USER gnome-session)
eval export $(sed 's/\o000/\n/g;' < /proc/3590/environ | grep DISPLAY)
eval export $(sed 's/\o000/\n/g;' < /proc/3590/environ | grep XAUTHORITY)
eval export $(sed 's/\o000/\n/g;' < /proc/3590/environ | grep DBUS_SESSION_BUS_ADDRESS)

I.e. I changed the variable to a specific pid.

When you run this script ($ ~/bin/xenv.sh) I got the following errors:
cat ~/Документы/Bugs/screenlog.2 | grep Отказано
/home/leon/bin/xenv.sh: line 2: /proc/3590/environ: Отказано в доступе
/home/leon/bin/xenv.sh: line 3: /proc/3590/environ: Отказано в доступе
/home/leon/bin/xenv.sh: line 4: /proc/3590/environ: Отказано в доступе
(Access is denied)

Then I ran this command:
leon@comp:~> sudo ~/bin/xenv.sh 
root's password:
leon@comp:~> gdb /usr/bin/gnome-shell
GNU gdb (GDB) SUSE (7.3-41.1.2)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
(gdb) run --replace
Starting program: /usr/bin/gnome-shell --replace
...
Missing separate debuginfo for /usr/lib64/....
Try: zypper install -C "debuginfo(build-id)=...."
This GDB was configured as "x86_64-suse-linux".
For bug reporting instructions, please see:
...
Ошибка менеджера окон: Unable to open X display 
[Inferior 1 (process 3795) exited with code 01]
(gdb) quit

P.S. Maybe I log into gnome-shell, and VT2 and do all the steps again?

Created attachment 206308 [details]
Maybe I log into gnome-shell, and VT2 and do all the steps again?

Maybe I log into gnome-shell, and VT2 and do all the steps again?

leon@comp:~> cat ~/bin/xenv.sh 
gnome_session=$(pgrep -u $USER gnome-session)
eval export $(sed 's/\o000/\n/g;' < /proc/2142/environ | grep DISPLAY)
eval export $(sed 's/\o000/\n/g;' < /proc/2142/environ | grep XAUTHORITY)
eval export $(sed 's/\o000/\n/g;' < /proc/2142/environ | grep DBUS_SESSION_BUS_ADDRESS)

To be clear: you should start a normal GNOME session, including gnome-shell, then go to the VT and run these steps. gnome-shell will be replaced as needed. ATM, you're probably trying to access information about somebody else's gnome-session process, thus the failure.

(In reply to comment #14)
> To be clear: you should start a normal GNOME session, including gnome-shell,
> then go to the VT and run these steps. gnome-shell will be replaced as needed.
> ATM, you're probably trying to access information about somebody else's
> gnome-session process, thus the failure.

Created an attachment (id=206308) [details]
I log into gnome-shell, and VT2 and do all the steps again

leon@comp:~> cat ~/bin/xenv.sh 
gnome_session=$(pgrep -u $USER gnome-session)
eval export $(sed 's/\o000/\n/g;' < /proc/2142/environ | grep DISPLAY)
eval export $(sed 's/\o000/\n/g;' < /proc/2142/environ | grep XAUTHORITY)
eval export $(sed 's/\o000/\n/g;' < /proc/2142/environ | grep
DBUS_SESSION_BUS_ADDRESS)

dmesg | grep segfault
[  501.297660] gnome-shell[2325]: segfault at 2ba95f008 ip 00007f7131a02ba8 sp 00007ffff0447860 error 4 in libglib-2.0.so.0.3000.1[7f71319a0000+f6000]
[  684.656402] gnome-shell[26997]: segfault at 61257016 ip 00007f8b4f34f890 sp 00007ffff25b36a8 error 4 in libgobject-2.0.so.0.3000.1[7f8b4f31c000+4d000]
[  945.688820] gnome-shell[27669]: segfault at 30b852008 ip 00007fdadea87ba8 sp 00007fff27916be0 error 4 in libglib-2.0.so.0.3000.1[7fdadea25000+f6000]
[ 1758.657080] gnome-shell[19125]: segfault at 35fa20107 ip 00007f170e3a7ba8 sp 00007fff3cda1570 error 4 in libglib-2.0.so.0.3000.1[7f170e345000+f6000]
[ 2421.458271] gnome-shell[19638]: segfault at 100000007 ip 00007f3e9c0a5ba8 sp 00007fffa5fbf680 error 4 in libglib-2.0.so.0.3000.1[7f3e9c043000+f6000]

The options for which this problem could arise:
1. Apparmor
2. ATI Radeon HD 5470 (ATI Catalyst 12.1) + Gnome-Shell

But it is not ruled out a bug in the gnome-shell itself

Ah, if you're using Catalyst, then you probably get hit by bug 668930, especially since the log you posted above says the bug occurs in libgobject. So I don't think it's worth trying to get a trace anymore.

If you have the possibility to try the free Nouveau driver, it would be interesting to check that the bug isn't present there too. You may use a Live CD to test a recent enough distribution.

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

I worked a little with the free driver Radeon. 

"Radeon is an open source Xorg driver for ATI Radeon cards. It is particularly useful for users of openSUSE 11.4 that have cards that ATI/AMD declared legacy cards, since the old Catalyst 9.3 driver does not support recent versions of the Linux kernel or Xorg.

It is in many respects better than the proprietary fglrx driver, though the 3D performance is not as good."

P.S. Nouveau: Accelerated Open Source driver for nVidia cards

Thank you all for your help!

Yes, the problem is really in 12.1 AMD fglrx drivers:
-- https://bugzilla.gnome.org/show_bug.cgi?id=668800 (openSUSE 12.1+fglrx 12.1)
-- https://bugzilla.gnome.org/show_bug.cgi?id=668930 (Linux mint 12+fglrx 12.1)
-- https://bugzilla.redhat.com/show_bug.cgi?id=702257 (Fedora 15+fglrx 12.1)

-- https://bugzilla.gnome.org/show_bug.cgi?id=663155#c4 (GNOME 3.2.X+FGLRX 12.1)
-- http://ati.cchtml.com/show_bug.cgi?id=99
-- http://ati.cchtml.com/show_bug.cgi?id=264
-- http://ati.cchtml.com/show_bug.cgi?id=283

-- http://ati.cchtml.com/show_bug.cgi?id=339
P.s. We must send all of our bugs on ati bagtracker

As Milan already said:
Alex: Please don't paste the same links in all Catalyst bugs you know of. These
are not always the same problem. For example, the first series of bugs is about
a crash, while the others are about image corruption.