guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ivanmarcus <>
Subject Re: SSH issue with Ubuntu 18.04 - updated detail - Resolved
Date Thu, 16 Aug 2018 21:02:43 GMT
To follow on from this.

In looking to see if there was an issue with the local mirror I found 
that /etc/apt/sources.list contained just the three main repositories, 
none for Universe/Multiverse.

Adding these repositories (per meant 
that the requisite dependencies for Guacamole became available per 
Nick's findings.

I'm not sure why this happened - I've not used 18.04 much as all my 
servers are yet to be upgraded from 16.04, so haven't had much 
experience with any foibles it may have - but it's possibly something to 
do with the initial base install not having internet access. This is by 
design in the network I was running it within (although once installed 
and the nic configured etc it does have full access); it's not been an 
issue with previous versions of Ubuntu, however 18.04 may treat things 

If I find out anything further I'll update this post, although I expect 
for most people installing Guacamole this won't be an issue - if there's 
going to be some esoteric problem it's usually only me that has it!

On 17/08/2018 7:39 a.m., ivanmarcus wrote:
> No, nothing disabled. This was a clean version of server, installed in 
> a VM, following which the only commands issued were to set a root pw, 
> su, update, upgrade and the requisite package install for Guacamole...
> Maybe I'll redo the base install just to see if there was anything amiss.
> Otherwise thanks for the suggestion but as mentioned I'm not concerned 
> about it and realise there are easier ways to install, it's more about 
> trying to find out why this is occurring in case it happens to anyone 
> else and/or there's a need to update install detail I guess (although 
> I really think this problem is an outlier as I see others have 
> installed Guacamole on 18.04 ok).
> I did wonder if it could be something to do with the local (NZ) 
> mirror, but haven't got any further than that at this stage.
> On 16/08/2018 11:57 p.m., brian mullan wrote:
>> Did you disable any of the "repositories" ?
>> Install & run synaptic and search there for the lib you need using 
>> just the root of the name (ie libssh for example).
>> On Thu, Aug 16, 2018, 7:53 AM M D Barber < 
>> <>> wrote:
>>     does 18.04 not have the same option as 16.04 during the install
>>     to set different roles for the server? (and thus i assume install
>>     a different range of packages from the selection)
>>     Nick Couchman wrote:
>>>     On Thu, Aug 16, 2018 at 1:00 AM ivanmarcus <
>>>     <>> wrote:
>>>         Thanks Nick, I can only assume I must be special then :-)
>>>         apt-get install build-essential autoconf libtool m4
>>>         libpng-dev libjpeg-dev libcairo-dev libossp-uuid-dev
>>>         libtelnet-dev libpango1.0-dev libfreerdp-dev libssh2-1-dev
>>>         libwebp-dev libvncserver-dev libpulse-dev libvorbis-dev
>>>         Reading package lists... Done
>>>         Building dependency tree
>>>         Reading state information... Done
>>>         Note, selecting 'libcairo2-dev' instead of 'libcairo-dev'
>>>         Package libssh2-1-dev is not available, but is referred to
>>>         by another package.
>>>         This may mean that the package is missing, has been
>>>         obsoleted, or
>>>         is only available from another source
>>>         E: Unable to locate package libossp-uuid-dev
>>>         E: Unable to locate package libtelnet-dev
>>>         E: Unable to locate package libfreerdp-dev
>>>         E: Package 'libssh2-1-dev' has no installation candidate
>>>         This is from a bare 18.04 server install, updated/upgraded.
>>>     Yeah, that's pretty much what I'm doing - I'm using 18.04.1,
>>>     Server ISO, and update/upgrade, but we should be getting to the
>>>     same point.  Very strange.
>>>     -Nick
>>     <>
>>     	Virus-free.
>>     <>
>>     <#m_3265151677212653926_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

View raw message