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.

Sign up for GitHub

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

Jump to bottom

No default panel with latest Master. Dual Monitor of different size. #78

Closed
BrianA-MN opened this issue May 12, 2020 · 6 comments · Fixed by #81
Closed

No default panel with latest Master. Dual Monitor of different size. #78

BrianA-MN opened this issue May 12, 2020 · 6 comments · Fixed by #81
Assignees
@ThomasAdam
Labels
type:bug Something's broken!
Milestone
1.0

Comments

@BrianA-MN
Copy link

Hi Thomas,
This is on a Slackware64 14.2 with Nouveau driving a NVIDIA GS8400GX with dual outputs to a DVI at 1600x900 and VGA at 1280x1024. The .config works under 2.6.9 but not 3.0.0. You asked for the config and xsession-errors log, which are attached. I'm just a tester, but willing to help with more testing or explanation of system config or Slackware configs. Cheers, BrianA_MN
config.txt
1.txt
@ThomasAdam
Copy link
Member

Thanks, @BrianA-MN. Please can you also attach the output from xrandr?

@BrianA-MN
Copy link
Author

Here is xrandr.
xrandr-out.txt

@BrianA-MN BrianA-MN reopened this May 13, 2020
@BrianA-MN
Copy link
Author

Sorry I was only trying to leave comment and file.

@ThomasAdam
Copy link
Member

Hi @BrianA-MN,

It looks as though you don't have a monitor marked as primary. Please can you try setting one of your monitors as primary. For example:

xrandr --output <NAME_OF_MONITOR> --primary

Perhaps add this to the top of your ~/.xsession or ~/.xinitrc script (however you're starting FVWM3), and try again...

Kindly,
Thomas

ThomasAdam added a commit that referenced this issue May 13, 2020
@ThomasAdam
randr: assign one output as primary
a030041 
RandR doesn't guarantee that there is always one monitor marked as
primary.  Certain operations in FVWM expect this, therefore if a primary
monitor hasn't been set, assign the first monitor found as a default.

Helps address #78
@ThomasAdam
Copy link
Member

Hi @BrianA-MN,

Further to my previous comment, you should also checkout the ta/primary-if-none branch and see if that fixes your problem. This change assigns the first output FVWM3 finds as primary in the case no primary monitor is found.

@ThomasAdam ThomasAdam mentioned this issue May 13, 2020
Merged
@ThomasAdam ThomasAdam added the type:bug Something's broken! label May 13, 2020
@ThomasAdam ThomasAdam self-assigned this May 13, 2020
@ThomasAdam ThomasAdam added this to the 1.0 milestone May 13, 2020
@ThomasAdam ThomasAdam linked a pull request May 13, 2020 that will close this issue
randr: assign one output as primary #81
Merged
@BrianA-MN
Copy link
Author

Thomas, I finally compiled, packaged and installed this ta/primary-if-none patch and it didn't resolve the issue of no right screen. Is there a special file or where is the code embedded so I could do a diff? Thanks BrianA_MN

ThomasAdam added a commit that referenced this issue May 22, 2020
@ThomasAdam
randr: assign one output as primary
b6d6265 
RandR doesn't guarantee that there is always one monitor marked as
primary.  Certain operations in FVWM expect this, therefore if a primary
monitor hasn't been set, assign the first monitor found as a default.

Helps address #78
ThomasAdam added a commit that referenced this issue May 22, 2020
@ThomasAdam
randr: assign one output as primary
3f1c91c 
RandR doesn't guarantee that there is always one monitor marked as
primary.  Certain operations in FVWM expect this, therefore if a primary
monitor hasn't been set, assign the first monitor found as a default.

Helps address #78
ThomasAdam added a commit that referenced this issue May 22, 2020
@ThomasAdam
randr: assign one output as primary
b3475d7 
RandR doesn't guarantee that there is always one monitor marked as
primary.  Certain operations in FVWM expect this, therefore if a primary
monitor hasn't been set, assign the first monitor found as a default.

Helps address #78
mikeandmore pushed a commit to mikeandmore/fvwm3 that referenced this issue Nov 28, 2020
@ThomasAdam @mikeandmore
randr: assign one output as primary
dd8b1ac 
RandR doesn't guarantee that there is always one monitor marked as
primary.  Certain operations in FVWM expect this, therefore if a primary
monitor hasn't been set, assign the first monitor found as a default.

Helps address fvwmorg#78
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ThomasAdam ThomasAdam

Labels
type:bug Something's broken!
Projects
FVWM3
Status: Done
Milestone
1.0
Development

Successfully merging a pull request may close this issue.

randr: assign one output as primary fvwmorg/fvwm3
2 participants
@ThomasAdam @BrianA-MN