Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Explorer fails to start with virtual desktop turned on #3492

Open
Akeem29 opened this issue Sep 5, 2024 · 0 comments
Open

[Bug]: Explorer fails to start with virtual desktop turned on #3492

Akeem29 opened this issue Sep 5, 2024 · 0 comments

Comments

@Akeem29
Copy link

Akeem29 commented Sep 5, 2024

Describe the bug

When I'm launching applications with virtual desktop turned off - they launch normally, whether they're launched through the command line or through the GUI. But when I'm trying to launch the app with Virtual Desktop turned on - they don't launch and when I launch them through the command line I get the following error (in this case with Notepad++ 8.6.9):

c:\Program Files\Notepad++>0124:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0124:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."

If I'll launch the app with Virtual Desktop turned off in the bottle settings but turned on in per-application overrides - they do launch, but without taskbar
Log.txt

To Reproduce

  1. Make a new bottle
  2. Install an application (for example Notepad++)
  3. Turn on "Virtual Desktop" in the Advanced Display Settings
  4. Launch the application

Package

Flatpak from Flathub

Distribution

Fedora Linux 40 (Workstation Edition)

Debugging Information

Official Package: true
Version: '51.13'
DE/WM: gnome-xorg
Display:
    X.org: true
    X.org (port): :0
    Wayland: false
Graphics:
    vendors:
        nvidia: &id002
            vendor: nvidia
            envs:
                __NV_PRIME_RENDER_OFFLOAD: '1'
                __GLX_VENDOR_LIBRARY_NAME: nvidia
                __VK_LAYER_NV_optimus: NVIDIA_only
            icd: /usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/nvidia_icd.json
            nvngx_path: /usr/lib/x86_64-linux-gnu/GL/nvidia-555-58-02/extra/nvidia/wine
        intel: &id001
            vendor: intel
            envs:
                DRI_PRIME: '1'
            icd: /usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/intel_hasvk_icd.x86_64.json:/usr/lib/x86_64-linux-gnu/GL/vulkan/icd.d/intel_icd.x86_64.json:/usr/lib/i386-linux-gnu/GL/vulkan/icd.d/intel_hasvk_icd.i686.json:/usr/lib/i386-linux-gnu/GL/vulkan/icd.d/intel_icd.i686.json
    prime:
        integrated: *id001
        discrete: *id002
Kernel:
    Type: Linux
    Version: 6.10.6-200.fc40.x86_64
Disk:
    Total: 8259121152
    Free: 8258949120
RAM:
    MemTotal: 15.4GiB
    MemAvailable: 8.6GiB
Bottles_envs: null

Troubleshooting Logs

Log is too long to fit in 65536 characters, so it is provided as a text file embedded in "Describe the bug" section

Additional context

It doesn't seem to be related to #2120, since CMD output is entirely different

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant