aave

Forum Replies Created

Viewing 1 post (of 1 total)
  • Author
    Posts
  • in reply to: Change resolution vs scale resize issues #43534
    aave
    Participant

    I have actually found 2 solutions and thought to share them here to help other Fluxbox users:

    The issue is indeed that fluxbox doesn’t know about any resolution. When you start it I guess it takes the Xorg default which is 1024. However after you chose to scale the screen to your client’s resolution (as shown on the picture) and in the small fluxbox area you select RESTART fluxbox from the menu, when Fluxbox reloads it will automatically scale to your resolution.

    This might be an acceptable solution for you if you don’t restart the remote machine regularly.

    A more permanent solution is to create an xorg.conf with the resolution you want it to default to, for example:

     

    Section “ServerLayout”
    Identifier     “X.org Configured”
    Screen      0  “Screen0” 0 0
    InputDevice    “Mouse0” “CorePointer”
    InputDevice    “Keyboard0” “CoreKeyboard”
    EndSection

    Section “Files”
    ModulePath   “/usr/lib/xorg/modules”
    FontPath     “/usr/share/fonts/X11/misc”
    FontPath     “/usr/share/fonts/X11/cyrillic”
    FontPath     “/usr/share/fonts/X11/100dpi/:unscaled”
    FontPath     “/usr/share/fonts/X11/75dpi/:unscaled”
    FontPath     “/usr/share/fonts/X11/Type1”
    FontPath     “/usr/share/fonts/X11/100dpi”
    FontPath     “/usr/share/fonts/X11/75dpi”
    FontPath     “/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType”
    FontPath     “built-ins”
    EndSection

    Section “Module”
    Load  “glx”
    Load  “record”
    Load  “dbe”
    Load  “dri2”
    Load  “extmod”
    Load  “dri”
    EndSection

    Section “InputDevice”
    Identifier  “Keyboard0”
    Driver      “kbd”
    EndSection

    Section “InputDevice”
    Identifier  “Mouse0”
    Driver      “mouse”
    Option        “Protocol” “auto”
    Option        “Device” “/dev/input/mice”
    Option        “ZAxisMapping” “4 5 6 7”
    EndSection

    Section “Monitor”
    Identifier   “Monitor0”
    VendorName   “Monitor Vendor”
    ModelName    “Monitor Model”
    EndSection

    Section “Device”
    ### Available Driver options are:-
    ### Values: <i>: integer, <f>: float, <bool>: “True”/”False”,
    ### <string>: “String”, <freq>: “<f> Hz/kHz/MHz”,
    ### <percent>: “<f>%”
    ### [arg]: arg optional
    #Option     “ShadowFB”               # [<bool>]
    #Option     “DefaultRefresh”         # [<bool>]
    #Option     “ModeSetClearScreen”     # [<bool>]
    Identifier  “Card0”
    Driver      “vesa”
    BusID       “PCI:0:2:0”
    EndSection

    Section “Screen”
    Identifier “Screen0”
    Device     “Card0”
    Monitor    “Monitor0”
    SubSection “Display”
    Viewport   0 0
    Depth     1
    Modes     “1920×1080”
    EndSubSection
    SubSection “Display”
    Viewport   0 0
    Depth     4
    Modes     “1920×1080”
    EndSubSection
    SubSection “Display”
    Viewport   0 0
    Depth     8
    Modes     “1920×1080”
    EndSubSection
    SubSection “Display”
    Viewport   0 0
    Depth     15
    Modes     “1920×1080”
    EndSubSection
    SubSection “Display”
    Viewport   0 0
    Depth     16
    Modes     “1920×1080”
    EndSubSection
    SubSection “Display”
    Viewport   0 0
    Depth     24
    Modes     “1920×1080”
    EndSubSection
    EndSection

    Trying to do delays in the .xsession file will not work, I think it completely ignores any sleep command in there. It would be useful for also having a delay before loading the wallpaper with /usr/bin/fbsetbg however regardless what delay you put there fbsetbg will always end up in defunct, if it’s run manually after the desktop loaded it works. Not a big deal for me as I have this terminal server up nonstop after loading.

Viewing 1 post (of 1 total)