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

Overlay opens on the wrong screen (Two monitors the same model) #343

Closed
DarkArc opened this issue Aug 6, 2024 · 3 comments
Closed

Overlay opens on the wrong screen (Two monitors the same model) #343

DarkArc opened this issue Aug 6, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@DarkArc
Copy link

DarkArc commented Aug 6, 2024

Steps to Reproduce

Steps to reproduce the behavior:

  1. Setup the overlay to open on the secondary monitor

Expected behavior

The overlay opens on the secondary monitor

Problematic behavior

The overlay opens on the primary monitor

Desktop (please complete the following information):

Operating System: Fedora Linux 40
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
Kernel Version: 6.9.12-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7950X 16-Core Processor
Memory: 61.9 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: ASUS

Installation Method

flatpak (io.github.trigg.discover_overlay 0.7.4)

Discord client information

  • Install method : flatpak (com.discordapp.Discord)
  • Version : 0.0.62

Additional context

I think the issue is that if you look at my overlay location settings, both monitors show up with the same name. So even when I fix it to pick the secondary monitor, it finds the primary monitor first because they have the same model number.

I can fix it by changing the entry selected in the drop down.

@DarkArc DarkArc added the bug Something isn't working label Aug 6, 2024
@trigg
Copy link
Owner

trigg commented Aug 14, 2024

This is fixed in latest, but it looks like Flatpak fell behind in one stable version. I'll try to get a release out very soon

@trigg
Copy link
Owner

trigg commented Aug 14, 2024

(for the sake of completeness of my documentation)

Linked to #334

@DarkArc
Copy link
Author

DarkArc commented Aug 18, 2024

Thanks, can confirm this is now fixed.

@DarkArc DarkArc closed this as completed Aug 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants