| Summary: | NetworkManager freezes gnome-shell | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Carlos Fernando <uranio23> | ||||||||
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | dcbw, jklimes | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-02-13 13:51:39 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
Carlos Fernando
2012-01-23 21:38:06 UTC
It looks like a gnome-shell issue. Do you have problems with Gnome fallback mode? Do you have problems when you switch off WiFi? Please switch to a tty and get the following details: 1) $ rpm -q gnome-shell 2) ~/.xsession-errors 3) /var/log/messages (In reply to comment #1) > It looks like a gnome-shell issue. > Do you have problems with Gnome fallback mode? > Do you have problems when you switch off WiFi? > > Please switch to a tty and get the following details: > 1) $ rpm -q gnome-shell > 2) ~/.xsession-errors > 3) /var/log/messages Here is the output from the first command. $ rpm -q gnome-shell gnome-shell-3.2.1-2.fc16.x86_64 I attached my ~/.xsession-errors and /var/log/messages output ... Created attachment 558511 [details]
xsession-errors output file
Created attachment 558512 [details]
var_log_messages output file
(In reply to comment #1) > It looks like a gnome-shell issue. > Do you have problems with Gnome fallback mode? > Do you have problems when you switch off WiFi? > > Please switch to a tty and get the following details: > 1) $ rpm -q gnome-shell > 2) ~/.xsession-errors > 3) /var/log/messages BTW: I haven't used fallback mode a lot, just when removing gnome-shell and I don't think I had any troubles. Yes, in fact if I turn off any network interface gnome-shell will freeze. And maybe this is important, whenever I make gnome-shell freeze, if I remove it from a tty and reboot, it starts in fallback mode, then I can see that the NetworkManager has disabled ALL the network interfaces, I mean, the "Enable Networking" option in not checked. Hmm, not sure about gnome-shell issues. Maybe this is similar: https://bbs.archlinux.org/viewtopic.php?id=127534 But, I see some problems with your wireless driver rtl8187. It keeps disconnecting in about 5 mins. There could be a problem in recent kernels as indicated in http://permalink.gmane.org/gmane.linux.kernel.wireless.general/84576 Also, limiting the rate is a workaround for rtl8187 issues: https://wiki.archlinux.org/index.php/Rtl8187_wireless Could you grab output of 'dmesg'? Created attachment 558740 [details]
dmesg output file
(In reply to comment #1) > It looks like a gnome-shell issue. > Do you have problems with Gnome fallback mode? > Do you have problems when you switch off WiFi? > > Please switch to a tty and get the following details: > 1) $ rpm -q gnome-shell > 2) ~/.xsession-errors > 3) /var/log/messages I just made some test with Fallback mode, so far, the issue is gone while in fallback, unplugging my USB WiFi adapter does not freeze the system and I can disable/enable Networking with no troubles. Also rtl8187 feels a lot more stable in fallback mode, in gnome-shell sometimes it takes a lot of time to connect and even then it's not really connected yet. 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. |