| Summary: | [abrt] gnome-shell-3.2.1-2.fc16: Process /usr/bin/gnome-shell was killed by signal 5 (SIGTRAP) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Charles R. Anderson <cra> | ||||||||||||||
| Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> | ||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 16 | CC: | adam820, browning48ky, christian.vrl, dcbw, eu, geigor, JDP803, jklimes, jonathan.robie, maxamillion, otaylor, raflexras, samkraju, walters | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | abrt_hash:dfa8ce5dbd4c321d5c52a6e94ec502c653f7ce40 | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2013-02-13 20:02:42 UTC | Type: | --- | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Charles R. Anderson
2011-11-18 22:32:14 UTC
Created attachment 534510 [details]
File: dso_list
Created attachment 534511 [details]
File: maps
Created attachment 534512 [details]
File: backtrace
Backtrace analysis of bugs across components suggests the actual bug is in component NetworkManager or dbus-glib instead of component gnome-shell, reassigning to NetworkManager. Bug #708686 from component NetworkManager was found to be similar to this bug. This comment is automatically generated. *** Bug 708686 has been marked as a duplicate of this bug. *** restarting NetworkManager while wlan0 down & macchanger used. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Created attachment 579132 [details]
File: backtrace
conflict for some reason with openssh server; I've disable networkManager inorder to re-enable it only after reinstalled sshd (running now) and it soon crashed backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-2.git20120403.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Created attachment 579465 [details]
File: backtrace
just starting NetwotkManager.service by systemctl start after a fresh yum-updated packages backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-3.git20120403.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Created attachment 581536 [details]
File: backtrace
When booting the computer, it crashed, while restarting the service backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 OS Release: Fedora release 16 (Verne) attempted to restart NetworkManager after it failed on boot. systemctl restart NetworkManager.service backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 OS Release: Fedora release 16 (Verne) reboot login - login fails and returns to login screen login - nm-applet doesn't start. NewtorkManager is running sudo NetworkManager restart backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) crash on startup. executed: # systemctl restart NetworkManager.service error occurred. backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 OS Release: Fedora release 16 (Verne) sudo service restart NetworkManager, using Gnome 3. backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 OS Release: Fedora release 16 (Verne) Looks like you're getting a lot more reports for NetworkManager-gnome-0.9.4-6.git20120521.fc16 Maybe this release made things worse? I never had this problem before I upgraded to this version. inkscape crash occurred and this failure occurred immediately afterward. backtrace_rating: 4 Package: gnome-shell-3.2.2.1-1.fc16 OS Release: Fedora release 16 (Verne) Booting, login, restart NetowrkManager, for net. backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 OS Release: Fedora release 16 (Verne) 1. log-in 2. NetworkManager applet icon does not show on upper right corner 3. execute "sudo systemctl restart NetworkManager.service" 4. NetworkManager applet icon now shows but generate this error backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 OS Release: Fedora release 16 (Verne) Have exact same issue. 1. reboot 2. login screen (do nothing) 3. login screen (reloads - return to login screen) messages show gnome-sessions entering debug mode 4. login - nm-applet doesn't start. NewtorkManager is running 5. sudo NetworkManager restart Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 OS Release: Fedora release 16 (Verne) between 4. and 5. I notice this error (consistent with GUI) when I try to list connections. [root@lverissimo ~]# nmcli con list ** (process:3671): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. [dduncan@dduncan ~]$ sudo systemctl restart NetworkManager.service backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 OS Release: Fedora release 16 (Verne) terminal:
/sbin/service NetworkManager restart
Connection doesn't auto matically start on boot up, so I have to do this in terminal to start NM.
It works but gives this error.
backtrace_rating: 4
Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16
OS Release: Fedora release 16 (Verne)
NetworkManager service is running but I have no status icon/applet on my gnome toolbar. If I type... sudo systemctl restart NetworkManager.service The status icon/applet appears but the fault occurs (and I am then unable to launch the vpn connection which has worked for years). backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 OS Release: Fedora release 16 (Verne) Restarted service because icon not present in taskbar. backtrace_rating: 4 Package: NetworkManager-gnome-0.9.4-6.git20120521.fc16 OS Release: Fedora release 16 (Verne) After my recent update of the following packages this problem stopped. I guess kernel update was the solution. Updated: 1:qt-4.8.2-4.fc16.x86_64 Updated: 1:qt-x11-4.8.2-4.fc16.x86_64 Updated: 1:qt-assistant-4.8.2-4.fc16.x86_64 Updated: 1:qt-doc-4.8.2-4.fc16.noarch Updated: 1:control-center-filesystem-3.2.3-1.fc16.x86_64 Updated: selinux-policy-3.10.0-90.fc16.noarch Updated: selinux-policy-targeted-3.10.0-90.fc16.noarch Updated: 1:control-center-3.2.3-1.fc16.x86_64 Updated: 1:qt-demos-4.8.2-4.fc16.x86_64 Updated: 1:qt-examples-4.8.2-4.fc16.x86_64 Updated: 1:qt-postgresql-4.8.2-4.fc16.x86_64 Updated: 1:qt-mysql-4.8.2-4.fc16.x86_64 Installed: kernel-devel-3.4.6-1.fc16.x86_64 Updated: kernel-headers-3.4.6-1.fc16.x86_64 Updated: kernel-tools-3.4.6-1.fc16.x86_64 Updated: 1:qt-4.8.2-4.fc16.i686 Installed: kernel-3.4.6-1.fc16.x86_64 Updated: VirtualBox-4.1.18-1.fc16.x86_64 Installed: kmod-VirtualBox-3.4.6-1.fc16.x86_64-4.1.18-1.fc16.2.x86_64 Updated: 1:qt-x11-4.8.2-4.fc16.i686 Updated: kmod-VirtualBox-4.1.18-1.fc16.2.x86_64 Updated: kmod-VirtualBox-3.4.4-4.fc16.x86_64-4.1.18-1.fc16.x86_64 Updated: 1:qt-devel-4.8.2-4.fc16.i686 Erased: kmod-VirtualBox-3.3.8-1.fc16.x86_64-4.1.16-1.fc16.2.x86_64 Hi, I take back what I said on previus post. It did work for 3 days, but it fall back to error and now I have to restart service everytime after logon This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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 to click on "Clone This Bug" and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. |