[ubuntu-mono] [Bug 1811444] Re: out-of-the-box monodoc-http fails to show documentation

Daniel Llewellyn daniel at bowlhat.net
Fri Jan 11 17:28:00 UTC 2019


Also affects xenial, though mono-complete does not install the monodoc-
http package as a dependency. I needed to manually install monodoc-http
after mono-complete to test whether it failed.

** Tags added: xenial

** Tags added: bionic

-- 
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to mono-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1811444

Title:
  out-of-the-box monodoc-http fails to show documentation

Status in mono-tools package in Ubuntu:
  New

Bug description:
  The out-of-the-box configuration for monodoc-http, which is pulled by
  installing mono-complete, does not find any documentation. It is
  configured to look for documentation at /mono/lib/monodoc-ios/ and
  reports an HTTP 500 error when trying to navigate to
  http://localhost:8084/monodoc.

  ----
  System.ArgumentException
  basedir
  Parameter name: Base documentation directory at '/mono/lib/monodoc-ios/' doesn't exist
  Description: HTTP 500.Error processing request.

  Details: Non-web exception. Exception origin (name of application or
  object): monodoc.

  Exception stack trace:
    at Monodoc.RootTree.LoadTree (System.String basedir, System.Boolean includeExternal) [0x00031] in <496c0b0510da4601a8fa1704154167ef>:0 
    at Mono.Website.Global.Application_Start () [0x0002d] in <b585f8eef00841eab80ae6a6ea48bfd2>:0 
    at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
    at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00038] in <8f2c484307284b51944a1a13a14c0266>:0
  ----

  Should the documentation path be changed? what to? Should we change
  monodoc-http to ensure it depends upon an appropriate documentation
  package to provide the path that the server is configured to serve? Or
  should we do both?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: monodoc-http 4.2-2.2
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 11 17:06:25 2019
  InstallationDate: Installed on 2018-12-13 (28 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
  PackageArchitecture: all
  SourcePackage: mono-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mono-tools/+bug/1811444/+subscriptions



More information about the Ubuntu-mono mailing list