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]: NextCloud Windows Desktop not compatible with Matrox Graphics multiscreen card #4984

Closed
6 of 8 tasks
TxUtc opened this issue Sep 29, 2022 · 2 comments
Closed
6 of 8 tasks

Comments

@TxUtc
Copy link

TxUtc commented Sep 29, 2022

⚠️ Before submitting, please verify the following: ⚠️

Bug description

NextCloud cannot be launched (background service or foreground) on a Windows 10 PC equipped with Matrox Graphics card.
I tested it for the card Matrox M9140 LP PCIex16, driver version 2.5.0.213 (2/17/2016), card bios version 994-4124, v4.1.4, v2.4.1

The installation process works fine. Just after the reboot, NextCloud background is not launched (whereas autolaunch box was checked during install). Launching manually NextCloud fails to open NextCloud user interface.

Steps to reproduce

1- Launch Nexcloud on a PC equipped with Matrox Card specified earlier

Expected behavior

NextCloud should open user interface to ask for the account info for the first launch

Which files are affected by this bug

not specified

Operating system

Windows

Which version of the operating system you are running.

Windows 10

Package

Other

Nextcloud Server version

23.0.1

Nextcloud Desktop Client version

3.5.0

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

Are you using an external user-backend?

  • Default internal user-backend
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Nextcloud Server logs

No logs generated as NextCloud fails to start.

Additional info

@joshtrichards
Copy link
Member

May have been fixed by #4582 and/or #4821 in v3.6.0.

Are you still able to reproduce this?

@joshtrichards
Copy link
Member

Closing after >6 months without a response. Presuming fixed.

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

No branches or pull requests

2 participants