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

No multimonitor support #2084

Open
ghost opened this Issue Jun 19, 2016 · 6 comments

Comments

Projects
None yet
3 participants
@ghost

ghost commented Jun 19, 2016

Qubes OS version (e.g., R3.1):

R3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

N/A


Expected behavior:

Under Application Launcher/System Tools/System Settings/Display and Monitor there should be options for multiple monitors.

Actual behavior:

Just settings for the compositor is available.

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jun 20, 2016

Member

Discussion thread: https://groups.google.com/d/topic/qubes-users/2GNCpyZy2tk/discussion

Micah Lee wrote:

It appears that there are some missing packages in dom0. I solved this
by installing kscreen:

$ sudo qubes-dom0-update kscreen

This made KDE recognize my external monitor, but I still couldn't find
the configuration tool in System Settings. However I figured out that I
could open it like this:

$ kcmshell5 kscreen

Member

andrewdavidwong commented Jun 20, 2016

Discussion thread: https://groups.google.com/d/topic/qubes-users/2GNCpyZy2tk/discussion

Micah Lee wrote:

It appears that there are some missing packages in dom0. I solved this
by installing kscreen:

$ sudo qubes-dom0-update kscreen

This made KDE recognize my external monitor, but I still couldn't find
the configuration tool in System Settings. However I figured out that I
could open it like this:

$ kcmshell5 kscreen

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jun 23, 2016

Member

Several users have run into this problem.

Member

andrewdavidwong commented Jun 23, 2016

Several users have run into this problem.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jun 25, 2016

Member

Automated announcement from builder-github

The package pykickstart-2.13-3.fc23 has been pushed to the r3.2 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

Member

marmarek commented Jun 25, 2016

Automated announcement from builder-github

The package pykickstart-2.13-3.fc23 has been pushed to the r3.2 testing repository for dom0.
To test this update, please install it with the following command:

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing

Changes included in this update

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jul 28, 2016

Member

Automated announcement from builder-github

The package pykickstart-2.13-3.fc23 has been pushed to the r3.2 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

Member

marmarek commented Jul 28, 2016

Automated announcement from builder-github

The package pykickstart-2.13-3.fc23 has been pushed to the r3.2 stable repository for dom0.
To install this update, please use the standard update command:

sudo qubes-dom0-update

Or update dom0 via Qubes Manager.

Changes included in this update

@TheBubblePopped

This comment has been minimized.

Show comment
Hide comment
@TheBubblePopped

TheBubblePopped Feb 25, 2018

It would be nice if it could recognize the settings in the end after the restart ( kscreen) or if the problem would be solved after 2 years without doing additional work to get it running

TheBubblePopped commented Feb 25, 2018

It would be nice if it could recognize the settings in the end after the restart ( kscreen) or if the problem would be solved after 2 years without doing additional work to get it running

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Feb 25, 2018

Member

@TheBubblePopped: It looks like this bug was resolved back in Jun-Jul 2016 (which is why it's been closed since then). I'm guessing that you're experiencing a regression, so I'm reopening this.

Member

andrewdavidwong commented Feb 25, 2018

@TheBubblePopped: It looks like this bug was resolved back in Jun-Jul 2016 (which is why it's been closed since then). I'm guessing that you're experiencing a regression, so I'm reopening this.

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