Hide Forgot
Description of problem:pavucontrol over x11vnc locks up network Version-Release number of selected component (if applicable): x11vnc-0.9.12-18.fc15.x86_64 pavucontrol-0.9.10-2.fc15.x86_64 How reproducible: Always Steps to Reproduce: 1.start x11vnc as user 2.from remote machine connect to x11vnc 3.open pavucontrol 4. my whole network goes down, I even have to reboot my router Actual results: network goes down Expected results: pavucontrol should open without affecting my network. Additional info: I really wasnt even sure how to file this, pavucontrol works fine locally but I use my machine as a media center and have to adjust the volume/settings. This was not a problem with f14.
Firstly thank you for the bugreport. How it is reproducible? Do you have physical access to that machine too? Can you look on logs?
(In reply to comment #1) > Firstly thank you for the bugreport. > How it is reproducible? Do you have physical access to that machine too? Can > you look on logs? yes I have access to it, just let me know what files you would like and I will provide what ever you need. Thanks
Initially run commands ifconfig route -n before and after run pavucontrol over vnc session. Attach output as files there. Also look relevant messages in main log (tail /var/log/messages).
Created attachment 496121 [details] route -n
Created attachment 496122 [details] ifconfig
ok a little more digging and it has something to do with the marvell 88E8053 PCI-E nic (em1 on my machine) ifdown em1 ssh to eth0 (nvidia ck804) start x11vnc Connect to x11vnc through eth0 run pavucontroll no problems Marvel card---linksys dd-wrt 24sp2--x11vnc, run pavucontroll fails nvidia card---linksys dd-wrt 24sp2--x11vnc, run pavucontroll works fine Someone who knows how to capture and decipher network packets is going to have to figure this out which is over my head. If there is anything else I can provide please let me know. Thank you.
You don't provide route and interfaces information after network fail. And in any case I very doubt it may have relation to x11vnc.
(In reply to comment #7) > You don't provide route and interfaces information after network fail. > > And in any case I very doubt it may have relation to x11vnc. Route and interface information did not change.
What did??
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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