ssh: Could not resolve hostname slack-master: Name or service not known

Bug #1386372 reported by Juan Manuel García
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
slack (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Running ubuntu 14.04 LTS. with slack version 0.15.2 I get the following stack trace on a terminal when I try to start the program.

ssh: Could not resolve hostname slack-master: Name or service not known
rsync: did not see server greeting
rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.0]
FATAL[slack-getroles]: 'rsync --links --times -e ssh slack-master::slack/etc/roles.conf /var/cache/slack/_role_list' exited 5 at /usr/lib/slack/slack-getroles line 158.
FATAL[slack]: '/usr/lib/slack/slack-getroles' exited 5 at /usr/sbin/slack line 205.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in slack (Ubuntu):
status: New → Confirmed
Revision history for this message
Rael Gugelmin Cunha (rael-gc) wrote :

Any solution for that?

Revision history for this message
vallabh (vallabhjoshi09) wrote :

Initially I was trying to install 2.0.5th.deb version on ubuntu 14.04 but it was conflicting with exiting packeges and conf files to owerwrite.then I did
# sudo dpkg -i --force-overwrite slack-desktop-2.0.5-i386.deb
  Which gave slack icon in ubuntu-applications,but unable to run with producing above error.
  I replaced slack deb version with older one
# sudo dpkg -i slack-desktop-1.2.6-amd64.deb. (It was available on my server)

  It is working fine now ... :)

no longer affects: slack-desktop
Revision history for this message
Petr Michalec (epcim) wrote :

I got the same issue on environment where default user shell was 'fish'. If the 'slack' command is executed from bash shell it works fine.

Revision history for this message
Puneet Dokania (puneetkdokania) wrote :

remove the slack from the sbin: #sudo rm /usr/sbin/slack
now create a soft link: #sudo ln -s /usr/lib/slack/slack /usr/sbin/slack

This resolved the issue in my case. Now you can run slack from the terminal.

Revision history for this message
Andre Dias (aod7br) wrote :

Puneet solution also worked for me

Revision history for this message
Audrius Meskauskas (audrius-meskauskas) wrote :
Revision history for this message
Kai Kasurinen (kai-kasurinen) wrote :

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

Changed in slack (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for slack (Ubuntu) because there has been no activity for 60 days.]

Changed in slack (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Denis Lobanov (dulobanov) wrote :

Hello,

this issue is still exists, native slack deb archive contains broken version of the slack application and probably should be replaced with slack-desktop or renamed to slack-server.

den@hn:~$ slack
ssh: Could not resolve hostname slack-master: Temporary failure in name resolution
rsync error: errors with program diagnostics (code 13) at log.c(245) [Receiver=3.2.3]
FATAL[slack-getroles]: 'rsync --links --times -e ssh slack-master::slack/etc/roles.conf /var/cache/slack/_role_list' exited 13 at /usr/lib/slack/slack-getroles line 158.
FATAL[slack]: '/usr/lib/slack/slack-getroles' exited 13 at /usr/sbin/slack line 205.
den@hn:~$

Changed in slack (Ubuntu):
status: Expired → Confirmed
Revision history for this message
michael@linuxexam.com (x-michaer-x) wrote :

The issue still exists on 22.04.3, even when installing via `snap`.

The workaround listed in https://bugs.launchpad.net/ubuntu/+source/slack/+bug/1386372/comments/5 still works.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.