I run #!++ in VirtualBox without* issues -- your main problem here is not installing the Guest Additions. Here's what you do:
At this point the Guest Additions should be installing. Once it's complete (it shouldn't take very long) you should shutdown your VM and start it back up. The screen resolution should automatically adjust to whatever size the enclosing window is, or the native resolution of your current monitor if you choose to use full-screen. There shouldn't be any need to use the native Display tools.
*Note: When I say without issue, I mean the VM runs flawlessly. Unfortunately #!++ (and possibly anything based off of Debian) seems to fall into the category of incomplete support so from testing and new VMs, I have yet to be able to get cross-directional clipboard and drag-n-drop to work.
If anyone has been able to get it working, please let me know how!
The full Debian upgrade manual can also be found here https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html (Crunchbangplusplus is basically just Debian under the hood)
Thanks for your reply. Interestingly: /u/computermouth released the next version of #!++ for testing only one day after the 32-Bit-test-release of Crunchbang Monara was released.
I think it should work with your card but sometimes compton can be a Diva ;-)
On the next time you will use compton write
in your config file...
next try... will it work better with the drivers from nvidia?
last try... post your problem on https://github.com/chjj/compton/issues
i'm a novice myself, and this is how i got to it: googled openbox keybindings, found this as the path to the keybindings file: ~/.config/openbox/rc.xml, found it with thunar and viewing hidden files, opened it in geany and ctrl-f "web browser", where you can change the command to execute a browser.
edit: this is the page that i used. i'm glad that your question got me to look this up :)
At first I was going to say yes, but honestly, I'm not quite sure. You could always just try booting the disc and seeing if your USB stick is available as an install-able medium. If not, I don't think the universal usb installer I used to use will work.
Dont use unetbootin for Debian images, the Live Session will work fine and when installing from the same usb-stick you have some mysterious Errors.
Look here https://www.debian.org/CD/faq/#write-usb or on windows use win32imager...
not all wireless drivers are included by default.
I would suggest you get something like this https://www.amazon.com/USB-Ethernet-Adapter-Gigabit-Switch/dp/B09GRL3VCN/
then you can try install your wifi drivers post installation
about the two network icons: i found a forum where people were asking about this, and somebody found that there were two places autostarting the network applet.
long story short, edit the openbox autostart file:
geany ~/.config/openbox/autostart
find the nm-applet string:
## Start nm-applet for systray nm-applet &
and comment it out:
## Start nm-applet for systray ##nm-applet &
save and reboot.
the other issue i don't have any way of checking it, but this might help
Not sure about Rufus, but I'm pretty sure it does not work with Unetbootin. Use this instead: https://sourceforge.net/projects/win32diskimager/, though, it'll take the whole flash drive, regardless of whether the iso files requires it.
Have you choose the correct Output device in your Audio settings? After the installation you have a device with "Equalizer" in the Name....
or take a look here:
http://www.webupd8.org/2013/03/install-pulseaudio-with-built-in-system.html
Oh boy, that's an interesting one. There are several programs out there for defining usable grids for quick snapping your windows to set positions. But I've never really used any of them. QuickTile sounds like it's one such program.
But as far as easily defining it within Openbox to just never cover conky? Not that I'm aware of. Seeing if conky can always run on top of windows might be possible and/or easier.
try this command in your terminal:
sudo libinput measure fuzz --fuzz=8
just use the default options and 1 when prompted. if it's too much you can reset it by doing the command again and changing 8 to a lower value like 4 or 2.
i got the info from here
https://wayland.freedesktop.org/libinput/doc/latest/touchpad-jitter.html
usually, when it says it can't detect the installation media it means you have written the image onto a USB incorrectly.
I use Rufus to make mine on a windows system and have to check the "dd mode" option to have it write the disk in a way that will allow it to boot.
Presumably, on a Linux system, you could just dd if=/path/to/iso of=/path/to/usb/stick bs=8M