TheNessus
February 25th, 2010, 07:56 PM
I've found a funny useful bug.
While running a virtual machine (XP) in full screen in its own workspace under KDE4.3, since I require the use of Microsoft Word, I've accidentally successfully forked Conky to the background of the virtual machine, with a separate Conky process running on the host machine.
In order for the KDE panel not to be above the full screen window of the virtual machine, I've designated the Virtual Box window to be above all. Then when it is on full screen in a separate workspace, I ran conky. This forked it in the virtual machine and not in the host machine. Then used feh to paint a background for the transparent conky. The background in both machines is identical so conky looks native. Then I ran a second conky in the host machine by minimizing the virtual machine first, forking the second conky to the host machine background. weird.
While running a virtual machine (XP) in full screen in its own workspace under KDE4.3, since I require the use of Microsoft Word, I've accidentally successfully forked Conky to the background of the virtual machine, with a separate Conky process running on the host machine.
In order for the KDE panel not to be above the full screen window of the virtual machine, I've designated the Virtual Box window to be above all. Then when it is on full screen in a separate workspace, I ran conky. This forked it in the virtual machine and not in the host machine. Then used feh to paint a background for the transparent conky. The background in both machines is identical so conky looks native. Then I ran a second conky in the host machine by minimizing the virtual machine first, forking the second conky to the host machine background. weird.