libreport version: 2.0.8 abrt_version: 2.0.7 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: g_type_check_instance_cast executable: /usr/bin/gnome-shell kernel: 3.3.0-1.fc17.x86_64 pid: 1326 pwd: /home/mtiihone reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) time: Sun 25 Mar 2012 05:37:43 PM EEST uid: 1001 username: mtiihone backtrace: Text file, 69555 bytes build_ids: Text file, 7462 bytes dso_list: Text file, 21838 bytes maps: Text file, 95505 bytes var_log_messages: Text file, 17817 bytes environ: :XDG_VTNR=1 :XDG_SESSION_ID=2 :HOSTNAME=quadvadis.localdomain :IMSETTINGS_INTEGRATE_DESKTOP=yes :SHELL=/bin/bash :TERM=dumb :HISTSIZE=1000 :XDG_SESSION_COOKIE=3eaa7b368cdfaf4372ecda170000000b-1332681998.391005-235037016 :GNOME_KEYRING_CONTROL=/home/mtiihone/.cache/keyring-mu0GdD :IMSETTINGS_MODULE=none :'JAVA_OPTS=-XX:+UseG1GC -Xmx1024m -Doracle.jdbc.maxCachedBufferSize=0 -Dnet.sf.ehcache.skipUpdateCheck=true -XX:+TieredCompilation -XX:MaxPermSize=512m -noverify -Djava.security.egd=file:///dev/urandom -Dsun.java2d.xrender=True' :USER=mtiihone :USERNAME=mtiihone :'MAVEN_OPTS=-XX:+UseG1GC -Xmx1024m -Doracle.jdbc.maxCachedBufferSize=0 -Dnet.sf.ehcache.skipUpdateCheck=true -XX:+TieredCompilation -XX:MaxPermSize=512m -noverify -Djava.security.egd=file:///dev/urandom' :MAIL=/var/spool/mail/mtiihone :PATH=/home/mtiihone/.local/bin:/home/mtiihone/bin:/home/mtiihone/jdk/bin:/home/mtiihone/maven/bin:/home/mtiihone/ant/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin :DESKTOP_SESSION=gnome :QT_IM_MODULE=xim :PWD=/home/mtiihone :XMODIFIERS=@im=none :KDE_IS_PRELINKED=1 :GNOME_KEYRING_PID=1100 :LANG=en_US.utf8 :GDM_LANG=en_US.utf8 :KDEDIRS=/usr :GDMSESSION=gnome :HISTCONTROL=ignoredups :XDG_SEAT=seat0 :HOME=/home/mtiihone :SHLVL=1 :LOGNAME=mtiihone :CVS_RSH=ssh :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-1EIBSOAir1,guid=1ac19d145d306e1f9f04f54300000022 :'LESSOPEN=||/usr/bin/lesspipe.sh %s' :WINDOWPATH=1 :XDG_RUNTIME_DIR=/run/user/mtiihone :DISPLAY=:0 :XAUTHORITY=/var/run/gdm/auth-for-mtiihone-FkNthM/database :_=/usr/bin/gnome-session :GNOME_DESKTOP_SESSION_ID=this-is-deprecated :SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1105,unix/unix:/tmp/.ICE-unix/1105 :GPG_AGENT_INFO=/home/mtiihone/.cache/keyring-mu0GdD/gpg:0:1 :SSH_AUTH_SOCK=/home/mtiihone/.cache/keyring-mu0GdD/ssh :DESKTOP_AUTOSTART_ID=10d81231f75ef3915f133268199922530800000011050000
Created attachment 572554 [details] File: build_ids
Created attachment 572555 [details] File: dso_list
Created attachment 572556 [details] File: var_log_messages
Created attachment 572557 [details] File: maps
Created attachment 572558 [details] File: backtrace
What this backtrace shows is libnm-glib returning an array with invalid data to GNOME Shell, which crashes trying to convert it to GLib. It's hard to tell what function returned the invalid data - one of: nm_client_get_devices() nm_client_get_active_connections() nm_device_wifi_get_access_points() is most likely, since they are array-returning functions called by GNOME Shell. Knowing what circumstances this occurs in would help a lot.
I logged in, clicked firefox, and the shell crashed. backtrace_rating: 4 Package: gnome-shell-3.4.1-2.fc17 OS Release: Fedora release 17 (Beefy Miracle)
It crashes on service NetworkManager restart with NetworkManager-0.9.4-5.git20120403.fc17.x86_64 backtrace_rating: 4 Package: gnome-shell-3.4.0-1.fc17 OS Release: Fedora release 17 (Beefy Miracle)
I was installing an update with yum. While I did that, gnome-shell chrashed and was restarted. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 578926 [details] File: backtrace
Just starting LibreOffice while making some updates. backtrace_rating: 4 Package: gnome-shell-3.4.1-3.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Crashed for me on the same style while I was making some changes in VPN settings via the Network Manager (GUI).
updating fedora, in the cleanup phase backtrace_rating: 4 Package: gnome-shell-3.4.1-3.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Crash occurred whilst upgrading packages via yum. Cleanup of sssd package was ongoing at time of crash backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 580719 [details] File: backtrace
browsing web using firefox while yum upgrade running in the terminal backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 580943 [details] File: backtrace
I was running "update" to obtain the latest updates. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 580980 [details] File: backtrace
Booted then, started a yum upadate via terminal. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 581158 [details] File: backtrace
Updateing packages by 'yum apdate' backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
Created attachment 581173 [details] File: backtrace
*** Bug 817016 has been marked as a duplicate of this bug. ***
The problem occurred during installation of a series of updated packages from Fedora's package repos. Other than that I was just using my computer as normal. The packages being updated were: Updated: NetworkManager.x86_64 1:0.9.4-3.git20120403.fc16 NetworkManager-glib.x86_64 1:0.9.4-3.git20120403.fc16 NetworkManager-gnome.x86_64 1:0.9.4-3.git20120403.fc16 NetworkManager-gtk.x86_64 1:0.9.4-3.git20120403.fc16 PackageKit.x86_64 0:0.6.22-2.fc16 PackageKit-command-not-found.x86_64 0:0.6.22-2.fc16 PackageKit-device-rebind.x86_64 0:0.6.22-2.fc16 PackageKit-glib.x86_64 0:0.6.22-2.fc16 PackageKit-gstreamer-plugin.x86_64 0:0.6.22-2.fc16 PackageKit-gtk-module.x86_64 0:0.6.22-2.fc16 PackageKit-gtk3-module.x86_64 0:0.6.22-2.fc16 PackageKit-yum.x86_64 0:0.6.22-2.fc16 PackageKit-yum-plugin.x86_64 0:0.6.22-2.fc16 autocorr-en.noarch 1:3.4.5.2-12.fc16 evolution.x86_64 0:3.2.3-3.fc16 evolution-NetworkManager.x86_64 0:3.2.3-3.fc16 evolution-bogofilter.x86_64 0:3.2.3-3.fc16 evolution-help.noarch 0:3.2.3-3.fc16 flac.x86_64 0:1.2.1-8.fc16 gnome-color-manager.x86_64 0:3.2.3-2.fc16 ibus-hangul.x86_64 0:1.4.1-1.fc16 im-chooser.x86_64 0:1.5.2.2-1.fc16 im-chooser-common.x86_64 0:1.5.2.2-1.fc16 libipa_hbac.x86_64 0:1.8.2-10.fc16 libmtp.x86_64 0:1.1.3-2.fc16 libreoffice-base.x86_64 1:3.4.5.2-12.fc16 libreoffice-calc.x86_64 1:3.4.5.2-12.fc16 libreoffice-core.x86_64 1:3.4.5.2-12.fc16 libreoffice-draw.x86_64 1:3.4.5.2-12.fc16 libreoffice-graphicfilter.x86_64 1:3.4.5.2-12.fc16 libreoffice-impress.x86_64 1:3.4.5.2-12.fc16 libreoffice-javafilter.x86_64 1:3.4.5.2-12.fc16 libreoffice-langpack-en.x86_64 1:3.4.5.2-12.fc16 libreoffice-math.x86_64 1:3.4.5.2-12.fc16 libreoffice-ogltrans.x86_64 1:3.4.5.2-12.fc16 libreoffice-opensymbol-fonts.noarch 1:3.4.5.2-12.fc16 libreoffice-pdfimport.x86_64 1:3.4.5.2-12.fc16 libreoffice-presentation-minimizer.x86_64 1:3.4.5.2-12.fc16 libreoffice-presenter-screen.x86_64 1:3.4.5.2-12.fc16 libreoffice-report-builder.x86_64 1:3.4.5.2-12.fc16 libreoffice-ure.x86_64 1:3.4.5.2-12.fc16 libreoffice-writer.x86_64 1:3.4.5.2-12.fc16 libreoffice-xsltfilter.x86_64 1:3.4.5.2-12.fc16 libv4l.x86_64 0:0.8.7-1.fc16 mdadm.x86_64 0:3.2.3-7.fc16 pixman.x86_64 0:0.24.4-1.fc16 pixman-devel.x86_64 0:0.24.4-1.fc16 radvd.x86_64 0:1.8.2-3.fc16 ruby-libs.x86_64 0:1.8.7.358-1.fc16 selinux-policy.noarch 0:3.10.0-84.fc16 selinux-policy-targeted.noarch 0:3.10.0-84.fc16 sssd.x86_64 0:1.8.2-10.fc16 sssd-client.x86_64 0:1.8.2-10.fc16 systemd.x86_64 0:37-19.fc16 systemd-sysv.x86_64 0:37-19.fc16 systemd-units.x86_64 0:37-19.fc16 thunderbird.x86_64 0:12.0-1.fc16 ypbind.x86_64 3:1.35-2.fc16 backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 581278 [details] File: backtrace
NetworkManager-0.9.4-4.git20120403.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/NetworkManager-0.9.4-4.git20120403.fc16
I really don't know when the problem happens, it seems to be random... backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 581335 [details] File: backtrace
Package NetworkManager-0.9.4-4.git20120403.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.4-4.git20120403.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-7168/NetworkManager-0.9.4-4.git20120403.fc16 then log in and leave karma (feedback).
System was updated using yum (sudo yum update) backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 581811 [details] File: backtrace
I just was updating the system using the bash. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora 16
Created attachment 582018 [details] File: backtrace
I was away from my computer and this ABRT notice waiting for me when I came back. That's all I know, and nothing appears to be broken. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 583061 [details] File: backtrace
Clicked on battery icon, but probably this is extension's fault. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 583953 [details] File: backtrace
I did a yum update to the latest version, rebooted, and logged in. Then abrt told me the shell crashed. backtrace_rating: 4 Package: gnome-shell-3.4.1-3.fc17 OS Release: Fedora release 17 (Beefy Miracle)
while updating fresh installed f16 after enabling testing repo backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 585377 [details] File: backtrace
Gnome-shell memory use grows over time, and has done so since I installed F16. When it gets to about 2G virtual memory used, it crashes. On a nearly identical system with unsupported Intel Graphics, I run the same applications with gnome3 in fallback mode, which does not have the memory leak. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne)
I have no longer seen this crash after tinstalling he fixed NetworkManager packages. And the constant flow of duplcate reports seems to have stopped too.
opened google chrome immediately after starting the computer and logging in. google chrome did open fine. I can't detect that anything bad actually happened. backtrace_rating: 4 Package: gnome-shell-3.4.1-4.fc17 OS Release: Fedora release 17 (Beefy Miracle)
After applying the latest system updates to Fedora 16, gnome abends and complains about what it can do. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne)
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.