Bug 1387337 - with a socks proxy set, gnome randomly freeze black screen
Summary: with a socks proxy set, gnome randomly freeze black screen
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-20 16:27 UTC by danielemi
Modified: 2016-12-06 10:55 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1385412
Environment:
Last Closed: 2016-12-06 10:55:25 UTC
Type: Bug


Attachments (Terms of Use)

Description danielemi 2016-10-20 16:27:29 UTC
Description of problem:
when a socks proxy is set, gnome freezes black screen, randomly without halting the system

Version-Release number of selected component (if applicable):
Fedora 24 4.7.6-200.fc24.x86_64

Please note:
I'm inside a VirtualBox VM where Fedora is my Guest OS.
I installed the VirtualBox Guest Additions ver 5.1.7-110797
I have configured the KVM acceleratetion.
I have configured the VM network to Bridged Adapter.
I'm using Snort in Fedora. 

How reproducible:
happens randomly 

Steps to Reproduce:
1. Configure a socks proxy in NetworkManager

Actual results:
Randomly the screen freeze blank, although the system appears not halted but not possible to interact with it


Expected results:


Additional info:
unset the sock proxy all run normally

Comment 1 Blueowl 2016-12-06 10:04:46 UTC
I doubt it is NetworkManager issue. Rather it seems like a graphics-related problem, possibly related to the virtual machine.

Would you describe in more detail how to reproduce the problem. And please capture some logs, like dmesg output and journalctl -b 0.

Comment 2 danielemi 2016-12-06 10:48:24 UTC
Unfortunately, in the meanwhile
- I switched to Fedora 25 Host and Guest with QEMU/KVM, erasing Windows/Virtual Box
- I haven't more details to add in the reproducing steps that I can remember.

The black screen appeared only after set the socks proxy (I did a couple of tries to reproduce the prb). And my system was completely stable.

I underline that I used socks proxies only.

Comment 3 Thomas Haller 2016-12-06 10:55:25 UTC
I assume, you configured the proxy in gnome-control-center's network dialog. Note that NetworkManager is not involved with that.

Since it seems no longer reproducible, I close this bug. Please re-open if additional information can be provided. Thanks.


Note You need to log in before you can comment on or make changes to this bug.