Menu

#1113 Xephyr -screen WxH fails

future release
closed-works-for-me
None
5
2016-08-08
2014-11-22
pavelo
No

Xephyr (think, Xnest on steroids) from the xorg-server package does not seem to agree with fluxbox - it fails to set its window to the proper size. Given that it works in other window managers, I think this is an issue with fluxbox. Steps to reproduce:

  1. $ Xephyr -screen 640x480 :1
  2. Observe that the window size is not correct (probably something like 100x100)
  3. start a different window manager (e.g. xfwm4)
  4. $ Xephyr -screen 640x480 :1
  5. Observe that the window size is correct.

If you need any additional info or traces, I will be happy to provide them.

Discussion

  • Mathias Gumz

    Mathias Gumz - 2014-11-23

    i can not confirm this behaviour:

    $> Xephyr -screen 640x480 :1 &
    $> xprop WM_NORMAL_HINTS  <click-to-xephyr>
    WM_NORMAL_HINTS(WM_SIZE_HINTS):
        program specified minimum size: 640 by 480
        program specified maximum size: 640 by 480
    

    have you tried to reproduce this behaviour with a fresh fluxbox-configuration?

    $> mv .fluxbox .fluxbox-current
    $> fluxbox
    

    i suspect some rule in your .fluxbox/apps to enforce the dimension to 100x100.

     
  • Mathias Gumz

    Mathias Gumz - 2014-11-23
    • assigned_to: Mathias Gumz
     
  • pavelo

    pavelo - 2014-11-23

    I tried it with a fresh config, but no help. xprop reports the sizes correctly, but the window is still small, as shown in the screenshot attached.

     
  • Mathias Gumz

    Mathias Gumz - 2014-11-24

    in your a.png-screenshot i see a running pager, a keyboard-layout-switcher, battery stats, volume and a theme which does not look like default.

    to make the issue reproducible you should really start with an empty fluxbox.

    error on my side: xprop is the wrong tool, xwininfo is the more appropriate one:

    $> xwininfo | grep "\-geometry"
    

    and here, on my machine, it reports whatever i tell xephyr to use as its dimensions.

     
  • pavelo

    pavelo - 2014-11-24

    Ok, you got me there. :) I had restarted fluxbox and not the entire session.

    Here is a new screenshot, this time with a full restart.

    As you can see, the issue still remains. And xwininfo reports the size as 100x100.

    I am unsure why this does not happen for you. I have tried this with fluxbox 1.3.2 1.3.5 and git. The xorg-server version I used is 1.5.0. I will try it with a newer version later.

     
  • Mathias Gumz

    Mathias Gumz - 2014-11-24

    and you are sure that the .fluxbox/apps file is empty? what's in your .Xresources file?

     
  • pavelo

    pavelo - 2014-11-24

    I have no .Xresources. My apps file does not contain anything which could relate to Xephyr and the same thing happens with a completely empty file. All attempts of forcing a specific size with the apps file also fail.

    Another interesting thing is that when I try to resize the window (alt+right click), the window border drawn by fluxbox is of the correct size (640x480). However, i cannot increase or decrease the size of the window.

     
  • Mathias Gumz

    Mathias Gumz - 2014-11-26

    this issue looks odd to me. i can not reproduce it.

     
  • Mathias Gumz

    Mathias Gumz - 2015-01-21
    • Group: v1.3.5 --> future release
     
  • Mathias Gumz

    Mathias Gumz - 2015-01-21
    • summary: Xephyr window resize fails --> Xephyr -screen WxH fails
     
  • Thomas Luebking

    Thomas Luebking - 2016-07-30

    Not reproducible here either, but it sounds as if the maximum window size hint is set.

    @pavelo
    Is this still a problem for you?
    In case, please attach the full output of "xprop" on the xephyr window.

     
  • pavelo

    pavelo - 2016-08-08

    Hmm... I have tried this out today, and it seems to be working fine. I guess some update of something made the problem go away. I guess we can close that now...

     
  • Thomas Luebking

    Thomas Luebking - 2016-08-08
    • status: open --> closed-works-for-me
     
  • Thomas Luebking

    Thomas Luebking - 2016-08-08

    Thank you for the update and confirmation of the status quo.

     

Log in to post a comment.

MongoDB Logo MongoDB