Information>Devices truncates inaccessible FSTAB mount names

Issue #460 resolved
prl created an issue

If an FSTAB network mount is inaccessible (e.g. server offline), then the entry for the mount in MENU>Information>Devices truncates the mount PI address/name (see attached screen shot).

Replication steps

Create (if necessary) a network file mount on a T series PVR using "Mount using FSTAB (mount at boot)".

Check that the mount's IP address, name and usage details are correctly shown in MENU>Information>Devices.

Exit MENU>Information>Devices and take the server for the mount off-line.

Return to MENU>Information>Devices and the mount's usage details will not be visible (correct), but the IP address and name are truncated.

Comments (6)

  1. prl reporter

    In the larger-font "heading lines" in the Information screens the item height (25) is not large enough for the font used (Regular;24), and character descenders are cut off. This can be seen in the "y" in the "Beyonwiz" text in the "Model:" entry in the attached screenshot. This (skin only) problem could also be fixed at the same time as the code fixes for the main bug.

  2. IanSav

    The font sizing problem is a skin issue. OverlayHD has fixed many occurrences of this type of error. Please don't change any code to address this issue.

  3. prl reporter

    I am well aware that the font sizing is a skin problem: "This (skin only) problem". I've just finished fixing it, only changing files in the easy-skin-aus-hd and Full-Metal-Wizard skins.

  4. IanSav

    I wasn't intending to insult you or your intelligence. I was trying to let you know that the issue you are changing is quite common. I also wanted to flag that I was hoping that you would not change the code in a way that changed the skin.

    Perhaps my comment didn't effectively convey this intended meaning.

  5. Peter Urbanec

    Fix bug #460: Information>Devices truncates inaccessible FSTAB mount names

    [Devices]

    Use the correct field for the share name when an FSTAB-mounted share's usage info can't be obtained (use self.makeWideNetworkEntry() instead of self.makeInfoEntry()).

    Also return an empty tuple instead of an empty string for consistency in Devices.mountInfo() if there's an exception from the stat() call.

    → <<cset 17c2a2f8f7f5>>

  6. Log in to comment