VirtualBox Fedora 16 "Switch to fullscreen" weird behavior - fedora

I have 2 widescreen monitors, one is 19inch and the other is 23 inch.
I have installed Fedora 16 on VirtualBox [Windows 7 Host]. I installed the virtualbox guest additions and got the gnome-shell running, but I am running into some weird behavior. When I place the virtualBox linux guest machine window on the 23 inch and click "Switch to fullscreen", the window swaps monitors and moves to the 19inch monitor and goes fullscreen on that one instead of the 23inch.
How do I get it to go fullscreen on the 23inch ?
Help !
Thanks.

In fullscreen-mode (Host+F) you can press Host+Home to bring up a context menu:
View -> Virtual Screen 1 -> Use Host Screen 2

Related

Pulseaudio + Qemu high cpu usage

I am rerouting the audio input and output of a Qemu guest by using the following:
In Environment:
QEMU_AUDIO_DRV=pa
QEMU_PA_SINK=some_sink
QEMU_PA_SOURCE=some_source
QEMU_AUDIO_DAC_FIXED_FREQ=48000
QEMU_AUDIO_ADC_FIXED_FREQ=48000
some_sink is pactl load-module module-null-sink and some_source is a monitor of another null-sink.
I have also setup the default sampling rate of the hosts Pulseaudio to 48000 such that no resampling occurs:
/etc/pulse/daemon.conf:
default-sample-rate = 48000
Pulseaudio version:
$ pulseaudio --version
pulseaudio 13.99.1
The audio out is NOT output on the machine, but forwarded to another system for processing.
The setup works fine (there is audio in and out), but the Pulseaudio CPU usage (on an Intel Xeon 3.50GHz) as reported by top is constantly between 15%-30%, which to me seems like A LOT.
Not doing any resampling and just forwarding a byte stream seems to me like an inexpensive operation...
Is the high CPU usage expected in this setup - if yes, why?
How could I investigate/troubleshoot the reason of pulseaudio's high CPU usage?
I get this too, although not all the time and only on the machine that actually plays the sound.
I have VMs running zoom, citrix that the play audio through my laptop. Periodically on my laptop CPU goes to 30% or so.
pulseaudio -k; pulseaudio -D; fixes the cpu usage until it happens again.
(Annoyingly, once this is done, citrix sound doesn't work until citrix is restarted)

Headless Chrome and Selenium on Windows?

I've seen that headless Chrome came out in some form last month and I've seen that it can be interacted with via Selenium but the articles I've seen mostly mention Linux and MacOS. Is this available for windows (7 and /or 10) yet?
The Headless mode for Windows is available in Chrome 60 beta, and the stable version is likely to be also in the 60th version.
https://www.google.com/chrome/browser/beta.html
There are no differences in the launch of Selenium
Yes, I use it on windows but with version 59 (beta) there is still an empty window popping up.
I've been using Chrome in headless mode for months, with Chrome 59 on Windows.
My Karma config (for a custom Chrome headless) is as follows:
browsers: ['Chrome_headless'],
customLaunchers: {
Chrome_headless: {
base: 'Chrome',
flags: ['--headless', '--disable-gpu', '--disable-plugins', '--window-size=0,0', '--window-position=-9999,0']
}
},
There is no visible window with these commands.
However, updating to Chrome 60 seems to have killed this config as it no longer works (as of today)
I am using Chromedriver headless mode with the version 2.33 with the following config for Capybara:
Capybara.register_driver :chrome_headless do |app|
args = ["--window-size=1280,1696", "--no-sandbox", "--headless", "--disable-gpu", "--disable-infobars", "--disable-notifications"]
Capybara::Selenium::Driver.new(app, {:browser => :chrome, :args => args})
end
It's working right now in chrome 59 with chromedriver 2.31 (just released). The only annoying thing is an empty window popping up at the beginning (just a visual effect) which will be removed in chrome 60 (should be about to release)

Save resolution created with xrandr

I am having troubles with my screen resolution on my fedora 24.
The screen keep getting 1024x768 and the 1280x1024 is unavailable.
digging a little i found, on arch linux forum, this commands:
https://bbs.archlinux.org/viewtopic.php?id=73738
gtf 1280 1024 60
xrandr --newmode "1280x1024_60.00" 108.88 1280 1360 1496 1712 1024 1025 1028 1060 -HSync +Vsync
xrandr --addmode DVI-1 1280x1024_60.00
xrandr --output DVI-1 --mode 1280x1024_60.00
This solves my problem, but the new mode wont persists in a system reboot. Anyone knows how to force this config to me applied even after a system reboot?
Download autorandr to your desktop and try it
For example, I have laptop with hdmi output and second screen:
xrandr --output HDMI-0 --auto --left-of eDP-1-1
autorandr --save workstation1
autorandr --change
Where workstation1 is a custom setup to save. Any other name can be used, home, work, etc.
Or use arandr to save profile in file
you can put the prefered resolution to a file like below:
Create a file in /etc/X11/xorg.conf.d/
40-monitor.conf
Section "Monitor"
Identifier "VGA1"
Option "PreferredMode" "1280x1024"
EndSection
Restart your X system.
If it doesn't work try creating the next two files in the same path, and restarting again:
30-graphic.conf
Section "Device"
Identifier "Intel Integrated"
Driver "intel"
EndSection
50-screen.conf
Section "Screen"
Identifier "Default Screen"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "640x480"
EndSubSection
EndSection
Please read here for more details:
https://ask.fedoraproject.org/en/question/8301/how-do-i-change-my-monitors-resolution/

Selendroid is not working?

http://selendroid.io/setup.html
Here is given an example of what I should get when I open localhost at port 4444.
But instead I get:
{"value":{"os":{"name":"Windows 7","arch":"x86","version":"6.1"},"build":
{"browserName":"selendroid","version":"0.10.0"},"supportedDevices":[],"supportedApps":
[{"mainActivity":"io.selendroid.androiddriver.WebViewActivity","appId":"io.selendroid.androiddriver:0.10.0",
"basePackage":"io.selendroid.androiddriver"}]},"status":0}
A device is connected to the PC and it has no screenlock, but it is not detected.
What's wrong?
(I don't have exp with Selenium or Selendroid and trying to start now)
On your device, you need to switch ON the USB debugging which is under developer mode.
then type command on command promt: adb devices
it should display attached devices.

Sniffing for WOL packets on port 9

So I am using XBMC (a media center program) that has an Android app with a feature that allows you to send Wake on LAN "magic packets" to computers you have XBMC installed on. While this would be a great feature for me if I had a dedicated media PC that auto-ran XBMC on startup, I use it instead on my normal desktop PC.
What I would like to do is see if I can write a little listener script that would run on my PC that would listen for those magic packets sent over port 9 and just start the XBMC application.
Some of my friends say that you cannot listen on this port. The Google searches on "port 9", "wake on lan", and "simple TCP/IP" I've performed remain inconclusive as to weather or not this is possible.
With Python and pcap (winpcap and pypcap http://code.google.com/p/pypcap/). Not very nice but works for me.
import os, pcap
pc = pcap.pcap()
pc.setfilter('udp port 9 and (udp[8:4] == 0xFFFFFFFF and udp[12:2] == 0xFFFF)')
for ts, pkt in pc:
os.system(r'"C:\Program Files (x86)\XBMC\xbmc.exe"')
You should be able to do this on a Windows PC. However your program will not run on a *Nix style system without having superuser, or using a privilege escalator program like jsvc.