• Re: SID KDE Plasma 6.2

    From George at Clug@21:1/5 to All on Sun Dec 1 12:00:01 2024
    On Sunday, 01-12-2024 at 21:40 Timothy M Butterworth wrote:
    All,

    You may want to avoid upgrading KDE Plasma to 6.2 in sid. I upgraded it earlier and after a reboot I only get a black screen when logging in.

    Whenever someone says, KDE Plasma and black screen together, I think "nvidia drivers".

    I doubt that is your issue. But do you have an Nvidia GPU in the computer?

    George.



    It is good to see KDE Plasma 6 making its way into sid though.

    Tim

    --
    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
    ⠈⠳⣄⠀⠀


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Sun Dec 1 12:50:01 2024
    On Sunday, 01-12-2024 at 21:40 Timothy M Butterworth wrote:
    All,

    You may want to avoid upgrading KDE Plasma to 6.2 in sid. I upgraded
    it
    earlier and after a reboot I only get a black screen when logging
    in.

    Whenever someone says, KDE Plasma and black screen together, I think
    "nvidia drivers" and Wayland.

    I doubt that is your issue. But do you have an Nvidia GPU in the
    computer?


    I had wondered if there is currently a difference between Trixie and
    SID, I believe that is a YES.



    https://wiki.debian.org/DebianReleases



    *

    testing [1] - The next generation release (Trixie [2]).


    *

    unstable [3] - The unstable development release (Sid [4]), where new
    or updated packages are introduced.



    https://packages.debian.org/sid/nvidia-driver
    Package: nvidia-driver (535.216.03-1) [non-free]



    Not sure if it helps, but I just ran updates on my Debian Trixie (not
    SID) KDE test PC which has  an Intel i5 and a Nvidia 2070 GPU.



    Wayland never works on my Trixie KDE Nvidia system because of the 535
    drives. I believe 650-655 drivers might work but have not bothered to
    prove this.


    I can log in using X11 and gathered the follow info, if it interests
    you. 


    Operating System: Debian GNU/Linux 12
    KDE Plasma Version: 6.2.3
    KDE Frameworks Version: 6.6.0
    Qt Version: 6.7.2
    Kernel Version: 6.11.10-amd64 (64-bit)
    Graphics Platform: X11
    Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
    Memory: 15.6 GiB of RAM
    Graphics Processor: NVIDIA GeForce RTX 2070/PCIe/SSE2





    $ plasmashell --version
    Qt: Session management error: None of the authentication protocols
    specified are supported
    plasmashell 5.27.11





    $ uname -r
    6.11.10-amd64
    $ lsb_release -a
    No LSB modules are available.
    Distributor ID: Debian
    Description:    Debian GNU/Linux trixie/sid
    Release:        n/a
    Codename:       trixie





    $ env | grep -E -i 'x11|xorg|wayland|plasma'
    DESKTOP_SESSION=plasma
    XDG_SESSION_TYPE=x11 MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service/memory.pressure




    $ lspci -k | grep -A 2 -E '(3D|VGA)'
    01:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce
    RTX 2070 Rev. A] (rev a1)
           Subsystem: ASUSTeK Computer Inc. Device 8784        Kernel driver in use: nvidia



    $ cat /proc/driver/nvidia/version
    NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.216.01  Tue Sep
    17 16:54:04 UTC 2024
    GCC version:  gcc version 14.2.0 (Debian 14.2.0-8)

    George.





    It is good to see KDE Plasma 6 making its way into sid though.

    Tim

    --
    ⢀⣴⠾⠻⢶⣦⠀
    ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
    ⠈⠳⣄⠀⠀


    Links:
    ------
    [1] https://wiki.debian.org/DebianTesting
    [2] https://wiki.debian.org/DebianTrixie
    [3] https://wiki.debian.org/DebianUnstable
    [4] https://wiki.debian.org/DebianSid

    <html>
    <head>
    <style type="text/css">
    body,p,td,div,span{
    font-size:13px; font-family:Arial, Helvetica, sans-serif;
    };
    body p{
    margin:0px;
    }
    </style>
    </head>
    <body>On Sunday, 01-12-2024 at 21:40 Timothy M Butterworth wrote:<br>
    &gt; All,<br>
    &gt; <br>
    &gt; You may want to avoid upgrading KDE Plasma to 6.2 in sid. I upgraded it<br>
    &gt; earlier and after a reboot I only get a black screen when logging in.<br>

    Whenever someone says, KDE Plasma and black screen together, I think "nvidia drivers" and Wayland.<br>
    <br><div>
    I doubt that is your issue. But do you have an Nvidia GPU in the computer?</div><div><br></div><div>I had wondered if there is currently a difference between Trixie and SID, I believe that is a YES.<br></div><div><br></div><div>https://wiki.debian.org/
    DebianReleases<br><ul><li><p class="line891"><a href="https://wiki.debian.org/DebianTesting">testing</a> - The next generation release (<a href="https://wiki.debian.org/DebianTrixie">Trixie</a>). <span class="anchor" id="line-42"></span></p></li><li><p
    class="line891"><a href="https://wiki.debian.org/DebianUnstable">unstable</a> - The unstable development release (<a href="https://wiki.debian.org/DebianSid">Sid</a>), where new or updated packages are introduced. </p></li></ul></div>
    <br><div>https://packages.debian.org/sid/nvidia-driver</div><div>Package: nvidia-driver (535.216.03-1) [non-free] <br></div><div><br></div><div>Not sure if it helps, but I just ran updates on my Debian Trixie (not SID) KDE test PC which has&nbsp; an
    Intel i5 and a Nvidia 2070 GPU. <br></div><div><br></div><div>Wayland never works on my Trixie KDE Nvidia system because of the 535 drives. I believe 650-655 drivers might work but have not bothered to prove this. </div><div><br></div><div>I can log in
    using X11 and gathered the follow info, if it interests you.&nbsp;</div><div><br></div><div>Operating System: Debian GNU/Linux 12<br><b>KDE Plasma Version: 6.2.3</b><br>KDE Frameworks Version: 6.6.0<br>Qt Version: 6.7.2<br>Kernel Version: 6.11.10-amd64 (
    64-bit)<br><b>Graphics Platform: X11</b><br>Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz<br>Memory: 15.6 GiB of RAM<br><b>Graphics Processor: NVIDIA</b> GeForce RTX 2070/PCIe/SSE2<br></div><div><br></div><div><br></div><div><span style="font-
    family:monospace"><span style="color:#000000;background-color:#ffffff;">$ plasmashell --version
    </span><br>Qt: Session management error: None of the authentication protocols specified are supported
    <br>plasmashell 5.27.11<br>
    <br><br></span></div><div><br></div><div><span style="font-family:monospace"><span style="color:#000000;background-color:#ffffff;">$ uname -r
    </span><br>6.11.10-amd64
    <br><span style="color:#000000;background-color:#ffffff;">$ lsb_release -a </span><br>No LSB modules are available.
    <br>Distributor ID: Debian
    <br>Description: &nbsp;&nbsp;&nbsp;Debian GNU/Linux trixie/sid
    <br>Release: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;n/a
    <br>Codename: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;trixie <br></span></div><div><span style="font-family:monospace"><span style="color:#000000;background-color:#ffffff;"><br></span></span></div><div><span style="font-family:monospace"><span style="color:#000000;background-color:#ffffff;"><br></span></span></div>
    <div><span style="font-family:monospace"><span style="color:#000000;background-color:#ffffff;">$ env | grep -E -i 'x11|xorg|wayland|plasma'
    </span><br>DESKTOP_SESSION=plasma
    <br>XDG_SESSION_TYPE=x11 <br>MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service/memory.pressure
    <br></span></div><div><span style="font-family:monospace"><span style="color:#000000;background-color:#ffffff;"><br></span></span></div><div><span style="font-family:monospace"><span style="color:#000000;background-color:#ffffff;">$ lspci -k | grep -A 2 -
    E '(3D|VGA)'
    </span><br>01:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] (rev a1)
    <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Subsystem: ASUSTeK Computer Inc. Device 8784
    <br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Kernel driver in use: nvidia
    <br></span></div><div><span style="font-family:monospace"><span style="color:#000000;background-color:#ffffff;"><br></span></span></div><div><span style="font-family:monospace"><span style="color:#000000;background-color:#ffffff;">$ cat /proc/driver/
    nvidia/version
    </span><br>NVRM version: NVIDIA UNIX x86_64 Kernel Module &nbsp;535.216.01 &nbsp;Tue Sep 17 16:54:04 UTC 2024
    <br>GCC version: &nbsp;gcc version 14.2.0 (Debian 14.2.0-8) <br> <br>George.</span></div><div><span style="font-family:monospace"><br></span></div>


    &gt; <br>
    &gt; It is good to see KDE Plasma 6 making its way into sid though.<br>
    &gt; <br>
    &gt; Tim<br>
    &gt; <br>
    &gt; -- <br>
    &gt; ⢀⣴⠾⠻⢶⣦⠀<br>
    &gt; ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system<br>
    &gt; ⢿⡄⠘⠷⠚⠋⠀ <a href="https://www.debian.org" target="_blank" class="normal-link">https://www.debian.org</a>/<br>
    &gt; ⠈⠳⣄⠀⠀<br>
    &gt;</body></html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Mon Dec 2 00:10:01 2024
    On Monday, 02-12-2024 at 03:20 Timothy M Butterworth wrote:
    On Sun, Dec 1, 2024 at 10:12 AM George at Clug wrote:



    On Sunday, 01-12-2024 at 21:40 Timothy M Butterworth wrote:
    All,

    You may want to avoid upgrading KDE Plasma to 6.2 in sid. I
    upgraded it
    earlier and after a reboot I only get a black screen when
    logging in.

    Whenever someone says, KDE Plasma and black screen together, I
    think
    "nvidia drivers".

      I doubt that is your issue. But do you have an Nvidia GPU in
    the computer?

    George.


    No, I do not have Nvidia. I have Sid in a VM. The black screen is
    strange
    because I have a visible mouse pointer. I also get crash reporter
    popups.



    "A black screen with only a visible mouse pointer" is one of the
    issues I have seen on computers with an Nvidia GPU, hence to me it was
    likely you had an Nvidia GPU, since you do not, then I suspect that
    the issue is related to the Graphics type that you have selected for
    your VM, maybe changing this to virtio and enabling OpenGL?


    FYI: My Debian Testing VM with KDE Plasma Wayland is working well
    after updates.



    What GPU does your computer have?, and what Graphics system is your
    VM using? (Which graphics driver and Display protocol do you use ?)


    Were you using a Wayland session or an X11 session? 



    Do you get to see the SDDM login screen or is that black with a mouse
    pointer, too?



    I use a Radeon RX 6600 GPU. In Virt-Manager, my Display is Spice
    server, Address, Hypervisor default, Port set to Auto. OpenGL is not
    selected.

    On my Debian Bookworm i7 Intel computer, I had a Debian Testing VM
    with Cinnamon, so I cloned this VM, ran updates and then installed
    kde-full. During the installation I selected "sddm" for the default
    display manager. 



    When I rebooted I could see the SDDM login screen, and for the
    "Session", I selected Plasma (Wayland), then logged in normally.
    Everything was working as expected.



    If I selected the QXL video type, then when I booted up, the VM hung
    during loading and no mouse pointer.  When I changed back to the
    virtio driver, all worked well and I was able log in and watch youtube
    videos.


    Please let me know if I can help.


    Here are my VM settings for the display



     
    *
     




     
     
     



    ----------------------------------


    When using Cinnamon I usually enable "OpenGL" too, so I tried this
    too.




     
       
     
     




     
    *
     
     



    ===========================================================================

    # apt update && apt update && apt full-upgrade --autoremove -y && apt autoremove -y && apt clean
    Hit:1 http://security.debian.org/debian-security testing-security
    InRelease
    Hit:2 http://deb.debian.org/debian testing InRelease
    Hit:3 http://deb.debian.org/debian testing-updates InRelease
    Hit:4 http://deb.debian.org/debian testing-backports InRelease
    All packages are up to date.
    Hit:1 http://security.debian.org/debian-security testing-security
    InRelease
    Hit:2 http://deb.debian.org/debian testing InRelease
    Hit:3 http://deb.debian.org/debian testing-updates InRelease
    Hit:4 http://deb.debian.org/debian testing-backports InRelease
    All packages are up to date.
    Summary:
      Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
    Summary:
      Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0

    # lsb_release -a
    No LSB modules are available.
    Distributor ID: Debian
    Description:    Debian GNU/Linux trixie/sid
    Release:        n/a
    Codename:       trixie

    # uname -r
    6.11.10-amd64

    # env | grep -E -i 'x11|xorg|wayland|plasma'
    DESKTOP_SESSION=plasmawayland MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1004.slice/user@1004.service/session.slice/plasma-plasmashell.service/memory.pressure
    WAYLAND_DISPLAY=wayland-0
    PLASMA_USE_QT_SCALING=1
    QT_WAYLAND_FORCE_DPI=96

    # lspci -k | grep -A 2 -E '(3D|VGA)'
    00:01.0 VGA compatible controller: Red Hat, Inc. Virtio 1.0 GPU (rev
    01)
            Subsystem: Red Hat, Inc. Device 1100
            Kernel driver in use: virtio-pci


    ===========================================================================

    <html>
    <head>
    <style type="text/css">
    body,p,td,div,span{
    font-size:13px; font-family:Arial, Helvetica, sans-serif;
    };
    body p{
    margin:0px;
    }
    </style>
    </head>
    <body>On Monday, 02-12-2024 at 03:20 Timothy M Butterworth wrote:<br>
    &gt; On Sun, Dec 1, 2024 at 10:12 AM George at Clug &lt;Clug@goproject.info&gt; wrote:<br>
    &gt; <br>
    &gt; &gt;<br>
    &gt; &gt;<br>
    &gt; &gt; On Sunday, 01-12-2024 at 21:40 Timothy M Butterworth wrote:<br>
    &gt; &gt; &gt; All,<br>
    &gt; &gt; &gt;<br>
    &gt; &gt; &gt; You may want to avoid upgrading KDE Plasma to 6.2 in sid. I upgraded it<br>
    &gt; &gt; &gt; earlier and after a reboot I only get a black screen when logging in.<br>
    &gt; &gt;<br>
    &gt; &gt; Whenever someone says, KDE Plasma and black screen together, I think<br>
    &gt; &gt; "nvidia drivers".<br>
    &gt; &gt;<br>
    &gt; &gt;&nbsp;&nbsp;I doubt that is your issue. But do you have an Nvidia GPU in the computer?<br>
    &gt; &gt;<br>
    &gt; &gt; George.<br>
    &gt; &gt;<br>
    &gt; <br>
    &gt; No, I do not have Nvidia. I have Sid in a VM. The black screen is strange<br>
    &gt; because I have a visible mouse pointer. I also get crash reporter popups.<br>
    &gt; <br><div><br></div><div>"A black screen with only a visible mouse pointer" is one of the issues I have seen on computers with an Nvidia GPU, hence to me it was likely you had an Nvidia GPU, since you do not, then I suspect that the issue is related
    to the Graphics type that you have selected for your VM, maybe changing this to virtio and enabling OpenGL?</div><div><br></div><div>FYI: My Debian Testing VM with KDE Plasma Wayland is working well after updates.<br></div><div><br></div><div><div>
    What GPU does your computer have?, and what Graphics system is your VM
    using? (Which graphics driver and Display protocol do you use ?)</div><div><br></div>Were you using a Wayland session or an X11 session?&nbsp; <br></div><div><br></div><div>Do you get to see the SDDM login screen or is that black with a mouse pointer,
    too?<br></div><div><br></div><div>I use a Radeon RX 6600 GPU. In Virt-Manager, my Display is Spice server,
    Address, Hypervisor default, Port set to Auto. OpenGL is not selected.</div> <br><div>On my Debian Bookworm i7 Intel computer, I had a Debian Testing VM with Cinnamon, so I cloned this VM, ran updates and then installed kde-full. During the installation I selected "sddm" for the default display manager.&nbsp; <br></div><div><br></
    <div>When I rebooted I could see the SDDM login screen, and for the "Session", I selected Plasma (Wayland), then logged in normally. Everything was working as expected. <br></div><div><br></div><div>If I selected the QXL video type, then when I
    booted up, the VM hung during loading and no mouse pointer.&nbsp; When I changed back to the virtio driver, all worked well and I was able log in and watch youtube videos.</div><div><br></div><div>Please let me know if I can help.</div><div><br></div><
    Here are my VM settings for the display</div><div><br></div><div>&lt;graphics type="spice" port="5900" autoport="yes" listen="127.0.0.1"&gt;<br>&nbsp; &lt;listen type="address" address="127.0.0.1"/&gt;<br>&nbsp; &lt;image compression="off"/&gt;<br>&
    lt;/graphics&gt;<br><br></div><div>&lt;video&gt;<br>&nbsp; &lt;model type="virtio" heads="1" primary="yes"/&gt;<br>&nbsp; &lt;alias name="video0"/&gt;<br>&nbsp; &lt;address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/&gt;<br>&lt;/
    video&gt;</div><div><br></div><div>----------------------------------</div><div><br></div><div>When using Cinnamon I usually enable "OpenGL" too, so I tried this too.<br></div><div><br></div><div>&lt;video&gt;<br>&nbsp; &lt;model type="virtio" heads="1"
    primary="yes"&gt;<br>&nbsp;&nbsp;&nbsp; &lt;acceleration accel3d="yes"/&gt;<br>&nbsp; &lt;/model&gt;<br>&nbsp; &lt;address type="pci" domain="0x0000" bus="0x00" slot="0x01" function="0x0"/&gt;<br>&lt;/video&gt;</div><div><br></div><div>&lt;graphics type="
    spice"&gt;<br>&nbsp; &lt;listen type="none"/&gt;<br>&nbsp; &lt;image compression="off"/&gt;<br>&nbsp; &lt;gl enable="yes" rendernode="/dev/dri/by-path/pci-0000:03:00.0-render"/&gt;<br>&lt;/graphics&gt;</div><div><br></div>=================================
    ==========================================<br><br># apt update &amp;&amp; apt update &amp;&amp; apt full-upgrade --autoremove -y &amp;&amp; apt autoremove -y &amp;&amp; apt clean<br>Hit:1 http://security.debian.org/debian-security testing-security
    InRelease<br>Hit:2 http://deb.debian.org/debian testing InRelease<br>Hit:3 http://deb.debian.org/debian testing-updates InRelease<br>Hit:4 http://deb.debian.org/debian testing-backports InRelease<br>All packages are up to date.<br>Hit:1 http://security.
    debian.org/debian-security testing-security InRelease<br>Hit:2 http://deb.debian.org/debian testing InRelease<br>Hit:3 http://deb.debian.org/debian testing-updates InRelease<br>Hit:4 http://deb.debian.org/debian testing-backports InRelease<br>All
    packages are up to date.<br>Summary:<br>&nbsp; Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0<br>Summary:<br>&nbsp; Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0<br><br># lsb_release -a<br>No LSB modules are available.<br>
    Distributor ID: Debian<br>Description:&nbsp;&nbsp;&nbsp; Debian GNU/Linux trixie/sid<br>Release:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; n/a<br>Codename:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; trixie<br><br># uname -r<br>6.11.10-amd64<br><br># env | grep -
    E -i 'x11|xorg|wayland|plasma'<br>DESKTOP_SESSION=plasmawayland<br>MEMORY_PRESSURE_WATCH=/sys/fs/cgroup/user.slice/user-1004.slice/user@1004.service/session.slice/plasma-plasmashell.service/memory.pressure<br>WAYLAND_DISPLAY=wayland-0<br>PLASMA_USE_QT_
    SCALING=1<br>QT_WAYLAND_FORCE_DPI=96<br><br># lspci -k | grep -A 2 -E '(3D|VGA)'<br>00:01.0 VGA compatible controller: Red Hat, Inc. Virtio 1.0 GPU (rev 01)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subsystem: Red Hat, Inc. Device 1100<br>&nbsp;&nbsp;
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Kernel driver in use: virtio-pci<br><br><br><div>===========================================================================</div><div><br></div><br><div><br></div></body></html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dominique Dumont@21:1/5 to All on Fri Dec 6 20:20:02 2024
    On Monday, 2 December 2024 04:56:09 CET Timothy M Butterworth wrote:
    Were you using a Wayland session or an X11 session?

    Wayland

    On my side, kde6 with wayland does not work in a VirtualBox VM.

    I had to switch to X11

    HTH

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Sat Dec 7 07:50:01 2024
    On Saturday, 07-12-2024 at 05:35 Dominique Dumont wrote:
    On Monday, 2 December 2024 04:56:09 CET Timothy M Butterworth wrote:
    Were you using a Wayland session or an X11 session?

    Wayland

    On my side, kde6 with wayland does not work in a VirtualBox VM.

    I had to switch to X11

    Dominique,

    Thanks for your comment.

    What GPU does the computer running the virtual machine use? That is, what brand and model is the video card on the computer running Virtual Box?

    What version of VirtualBox are you using?

    I found a comment on the internet that suggests VirtualBox 7.1 under debian12 does not support 3D acceleration.

    $ vboxmanage modifyvm deb-cube --accelerate3d on
    VBoxManage: error: The graphics controller does not support the given feature

    As I use KVM, I am able to run KDE with Wayland on my computers which have AMD Radeon graphics cards, when enabling OpenGL support (Requires 'Listen type' to be set to None')

    Has anyone had success with getting Mice to work correctly for 3D games run in VMs?

    I installed Minecraft into a Debian Testing, KDE Wayland, VM and ran Minecraft, Minecraft runs, however the mouse did not work correctly, when in a game world, I could not use (move around with) the mouse inside the Minecraft World correctly. When I
    tested X11, the mouse behaved differently but not correctly in X11 either.

    After adding a second mouse to my PC, (a logitech USB Wireless mouse and keyboard), in Virt-Manager, I selected "Redirect USB device" and selected "Logitech USB receiver". Then the logitech USB Wireless mouse worked normally within the Minecraft game
    World, allowing me to move around normally. However the logitech USB Wireless mouse did not operate correctly in the KDE environment, and I had to use the PC's (normally used) mouse in KDE, to start the Minecraft Launcher and to select the Minecraft '
    Play' button, and to select between "Singleplayer" and "Multiplayer" options to join the Minecraft World. Once in the World, it was only the logitech USB Wireless mouse which worked normally. My PC is not too powerful so while this worked, it is not
    something I want to do for "gaming", lol.

    I also tried TuxRacer. The USB redirected logitech USB Wireless mouse worked well for selecting options within the game. However the mouse is not required for playing this game, so it was not much of a test for mice functionality.

    I find this strange behaviour which I cannot easily explain.


    Via Virt-Manager I tried to 'Remove' the virtual mouse , e.g. <input type="mouse" bus="ps2"/> but this option is greyed out, so I was not able to do so. I was hoping if I removed KVM's virtual mouse, the USB redirected mouse would work better. I what
    what others have tried and maybe succeeded in doing?




    George.





    HTH







    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dominique Dumont@21:1/5 to All on Sun Dec 8 16:00:02 2024
    On Saturday, 7 December 2024 07:47:24 CET George at Clug wrote:
    What GPU does the computer running the virtual machine use? That is, what brand and model is the video card on the computer running Virtual Box?

    AFAIK, there's no specific brand and model. Virtual box emulates VGA and SVGA [1].

    What version of VirtualBox are you using?

    7.1

    I found a comment on the internet that suggests VirtualBox 7.1 under
    debian12 does not support 3D acceleration.

    $ vboxmanage modifyvm deb-cube --accelerate3d on
    VBoxManage: error: The graphics controller does not support the given
    feature

    I did not try that. I don't need it for work.

    All the best

    [1] https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/emul-hardware.html

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrew M.A. Cater@21:1/5 to Dominique Dumont on Sun Dec 8 16:30:01 2024
    On Sun, Dec 08, 2024 at 03:39:08PM +0100, Dominique Dumont wrote:
    On Saturday, 7 December 2024 07:47:24 CET George at Clug wrote:

    What version of VirtualBox are you using?

    7.1

    I found a comment on the internet that suggests VirtualBox 7.1 under debian12 does not support 3D acceleration.


    Debian does not support virtualbox in Debian stable because of a difference
    of opinion with the upstream provider about the practicability of security updates, as I understand it.

    The version in sid is there to prove the practicability of packaging, I
    think. In any event, sid is not intended as a Debian release.

    Can I suggest that you ask Oracle for help on this?

    The alternative is to switch from Virtualbox (and now also Broadcom VMWare)
    and use kvm/aqemu. For myself, I prefer to use virt-manager as a front end
    to virtualisation.

    With every good wish, as ever,

    Andy
    (amacater@debian.org)

    I did not try that. I don't need it for work.

    All the best

    [1] https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/emul-hardware.html





    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Sun Dec 8 23:50:01 2024
    On Monday, 09-12-2024 at 01:39 Dominique Dumont wrote:
    On Saturday, 7 December 2024 07:47:24 CET George at Clug wrote:
    What GPU does the computer running the virtual machine use? That is, what brand and model is the video card on the computer running Virtual Box?

    AFAIK, there's no specific brand and model. Virtual box emulates VGA and SVGA

    Are you going to use Virtual Box on a number of different physical computers?

    Sorry, I was not clear, "What physical video card/s are in the host (the computer acting as the hypervisor) ?" I am not asking about the guest's virtual video device.

    This can make a difference.
    AFAIK, VMware Workstation cannot run 3D graphics if your host (physical computer) is using a Radeon video graphics card.
    AFAIK, KVM/QEMU cannot run 3D graphics (OpenGL) if your host (physical computer) is using a Nvidia video graphics card.

    I am considering installing both Nvidia and Radeon video cards in my host (e.g. my PC that is acting as a hypervisor) so I run both/either VMware and KVM.


    [1].

    What version of VirtualBox are you using?

    7.1

    At least that is the latest, AFAIK.

    I found a comment on the internet that suggests VirtualBox 7.1 under debian12 does not support 3D acceleration.

    $ vboxmanage modifyvm deb-cube --accelerate3d on
    VBoxManage: error: The graphics controller does not support the given feature

    I did not try that. I don't need it for work.

    I hope you have success. The good thing about Virtual Box is you can run your VMs on either Windows or Linux computers. At least that is what I believe.

    As I don't run Windows at this time, I use KVM/QEMU using Virt-Manager to manage the VMs. I do have VMware Player installed, for running a few old VMs that I created a number of years ago when I used to run Windows. Sadly because I currently only have a
    Radeon video card in my PC, I cannot enable WMware's 3D support.

    I hope you have success in your efforts, whether you stay VirtualBox or change to KVM/QEMU. Please let us know if you do.

    I will comment that I have not found enabling 3D support has been useful for anything other than running 'Cinnamon without software rendering'. I have not found virtualised 3D graphics useful for gaming, maybe for demonstration, but not actual use. For
    gaming, I understand that GPU passthrough is required, which I have not personally tried. For gaming, I would prefer to use Wine/Steam or to have a separate PC, or to Dual boot.

    George.


    All the best

    [1] https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/emul-hardware.html






    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dominique Dumont@21:1/5 to All on Mon Dec 9 15:20:01 2024
    On Sunday, 8 December 2024 23:40:36 CET George at Clug wrote:
    Are you going to use Virtual Box on a number of different physical
    computers?

    No. I use VirtualBox only on the compute of a customer that requires me to
    work on his Windows PC. VirtualBox is my preferred solution to work with Linux on a Windows machine.

    Sorry, I was not clear, "What physical video card/s are in the host (the computer acting as the hypervisor) ?" I am not asking about the guest's virtual video device.

    It's a dual card with Intel UHD graphics and Nvidia Quatro T2000.

    I hope you have success in your efforts, whether you stay VirtualBox or change to KVM/QEMU. Please let us know if you do.

    As the guest Pc runs Windows, I cannot try kvm/qemu.

    All the best

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hector@21:1/5 to Dominique Dumont on Mon Dec 9 18:30:01 2024
    On 10/12/24 02:59, Dominique Dumont wrote:

    As the guest Pc runs Windows, I cannot try kvm/qemu.

    I've run Windows in kvm/qemu before.

    Richard

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrew M.A. Cater@21:1/5 to Dominique Dumont on Mon Dec 9 21:40:02 2024
    On Mon, Dec 09, 2024 at 02:59:48PM +0100, Dominique Dumont wrote:
    On Sunday, 8 December 2024 23:40:36 CET George at Clug wrote:
    Are you going to use Virtual Box on a number of different physical computers?

    Sorry, I was not clear, "What physical video card/s are in the host (the computer acting as the hypervisor) ?" I am not asking about the guest's virtual video device.

    It's a dual card with Intel UHD graphics and Nvidia Quatro T2000.


    I only know these from trying to install Debian on high-end gamer laptops.
    You get a choice of chipsets but it might be difficult to persuade this
    to work straightforwardly for a VM

    I hope you have success in your efforts, whether you stay VirtualBox or change to KVM/QEMU. Please let us know if you do.

    As the guest Pc runs Windows, I cannot try kvm/qemu.


    If the PC runs Windows, you could potentially use WSL2, I suppose.

    All the very best, as ever,

    Andy

    All the best






    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Mon Dec 9 23:40:01 2024
    Hi,


    I use VirtualBox only on the compute of a customer that requires me
    to work on his Windows PC. 
    VirtualBox is my preferred solution to work with Linux on a Windows
    machine.



    For me, Debian Bookworm KDE with Wayland runs well as a guest in
    VirtualBox on Windows.


    On Tuesday, 10-12-2024 at 00:59 Dominique Dumont wrote:
    On Sunday, 8 December 2024 23:40:36 CET George at Clug wrote:
    Are you going to use Virtual Box on a number of different physical computers?

    No. I use VirtualBox only on the compute of a customer that requires
    me to
    work on his Windows PC. VirtualBox is my preferred solution to work
    with Linux
    on a Windows machine.


    Requirements:
    1) Windows host

    2) Windows host with Nvidia available

    3) Commerical environment but wanting to use free solutions (Y/N)
    4) Guest will be KDE Plasma 6.2 with Wayland (is Wayland a
    requirement?)
    5) Unknown which, if any particular program/s is/are required to be
    run in the Debian guest.



    VMware Player is no longer available as a supported option.


    KVM/QEMU only runs on Linux


    VirtualBox is only free if not using VirtualBox Extension Pack, but I
    doubt you need this.


    The free to use VirtualBox does come with "VirtualBox Guest Additions"
    for linux (selected from menu)



    So I would agree, VirtualBox sounds like your best solution.


    On a Windows 10 PC, (i5 with Nvidia 970), I installed VirtualBox
    7.1.4, creaated a VM, with 'Enable 3d Acceleration', installed Debian
    Bookworm KDE, logged in using Wayland session, installed the
    "VirtualBox Guest Additions" for linux, then installed glmark2-wayland
    whose score was 130.

    I think it might be a bit unstable in KDE I disabled  in "Activity
    Power Settings" the settings for 'Never turn off the screen' and
    'Never shut down the computer or let it go to sleep'.


    For me, Debian Bookworm KDE with Wayland runs well as a guest in
    VirtualBox on Windows. I have not tried SID as yet.



    George.



    $ env | grep -E -i 'x11|xorg|wayland|plasma'
    DESKTOP_SESSION=plasmawayland
    XDG_SESSION_TYPE=wayland
    WAYLAND_DISPLAY=wayland-0
    PLASMA_USE_QT_SCALING=1
    QT_WAYLAND_FORCE_DPI=96


    $ lspci -k | grep -A 2 -E '(3D|VGA)'
    00:02.0 VGA compatible controller: VMware SVGA II Adapter
            Subsystem: VMware SVGA II Adapter
            Kernel driver in use: vmwgfx
            Kernel modules: vmwgfx


    # apt install build-essential dkms linux-headers-$(uname -r)

    In KDE, I copied the VBoxLinuxAdditions.run from the ISO image to the
    user's Downloads folder, in terminal changed into that folder and as
    root, ran:
    # apt install build-essential dkms linux-headers-$(uname -r)
    # chmod +x VBoxLinuxAdditions.run
    # ./VBoxLinuxAdditions.run





    Sorry, I was not clear, "What physical video card/s are in the
    host (the
    computer acting as the hypervisor) ?" I am not asking about the
    guest's
    virtual video device.

    It's a dual card with Intel UHD graphics and Nvidia Quatro T2000.

    I hope you have success in your efforts, whether you stay
    VirtualBox or
    change to KVM/QEMU. Please let us know if you do.

    As the guest Pc runs Windows, I cannot try kvm/qemu.

    It has been a while since I used VMware Player or VMware Workstation
    for business. However since the Host has Nvidia, I would personally
    opt for VMware Workstation to run a 3D guest virtual machine.

    What is best and what is available change with time. What is best
    today, might not even be available tomorrow, but we can only go on
    what is best now, with some understanding on what is possible in the
    future. I do not have current experience with VirtualBox.

    https://en.wikipedia.org/wiki/VMware_Workstation_Player
    VMware Workstation Player was discontinued in May 2024 when VMware
    Workstation Pro became free for personal use.

    The below link is information for Linux hosts. https://www.virtualbox.org/wiki/X11Guest3D

    General info, I think?
    https://www.xda-developers.com/how-use-gpu-virtualbox/


    All the best







    <html>
    <head>
    <style type="text/css">
    body,p,td,div,span{
    font-size:13px; font-family:Arial, Helvetica, sans-serif;
    };
    body p{
    margin:0px;
    }
    </style>
    </head>
    <body><div>Hi,</div><div><br></div><div>&gt; I use VirtualBox only on the compute of a customer that requires me to work on his Windows PC.&nbsp;</div><div>&gt; VirtualBox is my preferred solution to work with Linux on a Windows machine. <br></div><div><
    </div><div>For me, Debian Bookworm KDE with Wayland runs well as a guest in VirtualBox on Windows.

    </div><div><br></div><div>On Tuesday, 10-12-2024 at 00:59 Dominique Dumont wrote:</div>
    &gt; On Sunday, 8 December 2024 23:40:36 CET George at Clug wrote:<br>
    &gt; &gt; Are you going to use Virtual Box on a number of different physical<br>
    &gt; &gt; computers?<br>
    &gt; <br>
    &gt; No. I use VirtualBox only on the compute of a customer that requires me to <br>
    &gt; work on his Windows PC. VirtualBox is my preferred solution to work with Linux <br>
    &gt; on a Windows machine. <br><div><br></div>
    Requirements:<br><div>1) Windows host <br></div><div>2) Windows host with Nvidia available<br></div><div>3) Commerical environment but wanting to use free solutions (Y/N)</div><div>4) Guest will be KDE Plasma 6.2 with Wayland (is Wayland a requirement?)</
    <div>5) Unknown which, if any particular program/s is/are required to be run in the Debian guest.<br></div><div><br></div><div>VMware Player is no longer available as a supported option.</div><div><br></div><div>KVM/QEMU only runs on Linux</div><div><
    </div><div>VirtualBox is only free if not using VirtualBox Extension Pack, but I doubt you need this.</div><div><br></div><div>The free to use VirtualBox does come with "VirtualBox Guest Additions" for linux (selected from menu)<br></div><div><br></
    <div>So I would agree, VirtualBox sounds like your best solution.</div><div><br></div>On a Windows 10 PC, (i5 with Nvidia 970), I installed VirtualBox 7.1.4, creaated a VM, with 'Enable 3d Acceleration', installed Debian Bookworm KDE, logged in using
    Wayland session, installed the "VirtualBox Guest Additions" for linux, then installed glmark2-wayland whose score was 130.<br><br><div>I think it might be a bit unstable in KDE I disabled&nbsp; in "Activity Power Settings" the settings for 'Never turn
    off the screen' and 'Never shut down the computer or let it go to sleep'.</div><div><br></div><div>For me, Debian Bookworm KDE with Wayland runs well as a guest in VirtualBox on Windows. I have not tried SID as yet.<br></div><div><br></div><div>George.<
    </div><div><br></div><div>$ env | grep -E -i 'x11|xorg|wayland|plasma'<br>DESKTOP_SESSION=plasmawayland<br>XDG_SESSION_TYPE=wayland<br>WAYLAND_DISPLAY=wayland-0<br>PLASMA_USE_QT_SCALING=1<br>QT_WAYLAND_FORCE_DPI=96<br><br><br>$ lspci -k | grep -A 2 -E
    '(3D|VGA)'<br>00:02.0 VGA compatible controller: VMware SVGA II Adapter<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Subsystem: VMware SVGA II Adapter<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Kernel driver in use: vmwgfx<br>&nbsp;&nbsp;&nbsp;&nbsp;&
    nbsp;&nbsp;&nbsp; Kernel modules: vmwgfx<br><br><br># apt install build-essential dkms linux-headers-$(uname -r)<br><br>In KDE, I copied the VBoxLinuxAdditions.run from the ISO image to the user's Downloads folder, in terminal changed into that folder
    and as root, ran:<br># apt install build-essential dkms linux-headers-$(uname -r)<br># chmod +x VBoxLinuxAdditions.run<br># ./VBoxLinuxAdditions.run<br><br></div><div><br></div>
    &gt; <br>
    &gt; &gt; Sorry, I was not clear, "What physical video card/s are in the host (the<br>
    &gt; &gt; computer acting as the hypervisor) ?" I am not asking about the guest's<br>
    &gt; &gt; virtual video device.<br>
    &gt; <br>
    &gt; It's a dual card with Intel UHD graphics and Nvidia Quatro T2000.<br>
    &gt; <br>
    &gt; &gt; I hope you have success in your efforts, whether you stay VirtualBox or<br>
    &gt; &gt; change to KVM/QEMU. Please let us know if you do.<br>
    &gt; <br>
    &gt; As the guest Pc runs Windows, I cannot try kvm/qemu.<br>

    It has been a while since I used VMware Player or VMware Workstation for business. However since the Host has Nvidia, I would personally opt for VMware Workstation to run a 3D guest virtual machine.<br>

    What is best and what is available change with time. What is best today, might not even be available tomorrow, but we can only go on what is best now, with some understanding on what is possible in the future. I do not have current experience with
    VirtualBox.<br>

    <a target="_blank" class="blue" href="https://en.wikipedia.org/wiki/VMware_Workstation_Player">https://en.wikipedia.org/wiki/VMware_Workstation_Player</a><br>
    VMware Workstation Player was discontinued in May 2024 when VMware Workstation Pro became free for personal use.<br>

    The below link is information for Linux hosts.<br>
    <a target="_blank" class="blue" href="https://www.virtualbox.org/wiki/X11Guest3D">https://www.virtualbox.org/wiki/X11Guest3D</a><br>

    General info, I think?<br>
    <a target="_blank" class="blue" href="https://www.xda-developers.com/how-use-gpu-virtualbox">https://www.xda-developers.com/how-use-gpu-virtualbox</a>/<br>

    &gt; <br>
    &gt; All the best<br>
    &gt; <br>
    &gt; <br>
    &gt; <br>
    &gt; <br>
    &gt; <br>
    &gt;
    </body></html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dominique Dumont@21:1/5 to All on Wed Dec 18 19:50:01 2024
    On Monday, 9 December 2024 18:18:42 CET Richard Hector wrote:
    On 10/12/24 02:59, Dominique Dumont wrote:
    As the guest Pc runs Windows, I cannot try kvm/qemu.

    I've run Windows in kvm/qemu before.

    Bummer, I got it wrong.

    The host PC is windows and the guest is Debian/sid.

    Sorry for the blunder.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)