Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
I now discovered that openbox actually starts but works bad, the screen from sddm remains so it seems to be stuck, and the images of the windows remain: immagini
I had this problem on my other Debian 10 computer with gdm3 but openbox started with the blackscreen, after some time it was fixed.
I don't know what happened.
I use OpenBox with the xcompmgr compositor started from xdm without issue in Debian 10. sddm accommodates X11 and or Wayland while OpenBox is strictly X11. sddm also leans toward Qt while OpenBox is strictly gtk. I wonder if you are having compositor issues with sddm starting Wayland? OpenBox will not composite with Wayland.
shep wrote:OpenBox will not composite with Wayland.
Wayland is just a protocol. Display servers that use the protocol are called compositors because they also act as compositing window managers but Wayland compositors cannot be used in the same way as xcompmgr, compton or picom.
But it works so we don't need to worry about that now.
Scorpion wrote:I set gdm3 as DM and I have the same problem (windows "afterimages") but openbox starts with the black background.
You need to set a wallpaper, as I mentioned earlier.
Install the feh package and use it to open whichever image file you want to use as your desktop background, right-click on the image in feh and select File → Background → Set Filled (or whatever option is required) and add this line to ~/.config/openbox/autostart:
Remove the ampersand from the end of the line, it is not needed.
If you use my line you can change the wallpaper by opening the desired image with feh and using the right-click menu options I listed instead of editing the autostart file manually.