Difference between revisions of "Talk:Skype"

From ArchWiki
Jump to navigation Jump to search
(Skype legacy version incompatible with new version: re)
(Skype legacy version incompatible with new version: re)
Line 111: Line 111:
:::Oops, false news. "[https://community.skype.com/t5/Linux/Skype-for-Linux-End-of-life/m-p/4593845/highlight/true#M17642 At this time we are not retiring any of the existing working Linux Clients.]" [[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 01:41, 11 February 2017 (UTC)
:::Oops, false news. "[https://community.skype.com/t5/Linux/Skype-for-Linux-End-of-life/m-p/4593845/highlight/true#M17642 At this time we are not retiring any of the existing working Linux Clients.]" [[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 01:41, 11 February 2017 (UTC)
::Nah, just alternative facts. 😁 Okay, good to know; thanks for following up. In that case, IMO there's no need to retire this page yet. -- [[User:Ostiensis|Ostiensis]] ([[User talk:Ostiensis|talk]]) 06:31, 11 February 2017 (UTC)
== Systemd-nspawn security ==
== Systemd-nspawn security ==

Revision as of 06:32, 11 February 2017

Skype phones

What about skype phones? Is there a way to make them work with Linux? For instance, I have a Philips voip0801B/37. Are there open source drivers for these sort of things? -- Kc8tpz 11:58, October 1, 2007‎

Hey look if you can make it work as a generic kind/device type.
In regards to the other Linux distributions which would be the most likely to work with Arch? If you look at skype.com you will find packages for Debian, etc.. I've managed to get Flash Player in Arch x64 from using the ndiswrapper scripts from Ubuntu, any idea?
-- Dextrose 19:11, September 11, 2008‎

%wheel ALL=(skype) NOPASSWD: /usr/bin/skype

I have found that Skype runs as a special user if '%skype' is used instead of '%wheel'.

—This unsigned comment is by Slr (talk) 11:05, 13 October 2012‎. Please sign your posts with ~~~~!


I tried to secure Skype following the instructions in the article. Unfortunately it didn't work. Now i fixed it. For me to work, I needed a few modifications:

I added the following content to /etc/tomoyo/domain_policy.conf

file read /usr/share/locale/\*/LC_MESSAGES/\*
file read /usr/lib/gconv/\*

Otherwise skype doesn't adapt to the system language.

Furthermore just appending the in the article mentioned entries to /etc/tomoyo/exception_policy.conf doesn't work. Tomoyo didn't respect the lines

initialize_domain /usr/bin/skype from any
initialize_domain /usr/lib32/skype/skype from any

Therefore I moved them to the already existing entries of the form initialize_domain * in the configuration file. If this is also true for others, it might be a good idea to modify the article at least mentioning the latter one. Or perhaps it's a bug in tomoyo? --Marcus-aurelius (talk) 09:50, 8 June 2013 (UTC)


I fixed systemd-nspawn script a bit but I still can't make PulseAudio and my webcam work in the container. -- Yellow block (talk) 20:05, 19 October 2015 (UTC)

grsec profile

Is there any grsec profile available? Thanks in advance,--Xan (talk) 18:09, 13 March 2015 (UTC) If you whitelist "em" for /usr/share/skypeforlinux/skypeforlinux, the GUI loads just fine. Video calls and everything load no problem tancrackers (talk) 23:20, October 25, 2016 (UTC)

Skype hangs while logging in - missing dependency

Not sure if this is the right place to post this.

Skype might hang while logging in - the wheel will spin showing it's working, but it won't log in or display the main window. This is because it's missing libgnomeui - if you install this package it works perfectly. This should thus probably be a dependency.

Please file a bug: https://bugs.archlinux.org -- Alad (talk) 07:08, 21 August 2015 (UTC)


I think Docker could also be used to run skype in a save environment. What do you think? —This unsigned comment is by Ph1r3ph0x (talk) 27 August 2015‎. Please sign your posts with ~~~~!

See [1]. — Kynikos (talk) 07:56, 28 August 2015 (UTC)
Skype runs unprivileged within the container and the article talks about privileged processes. If we find this way insecure because base container system can be exploited, "systemd-nspawn" and "Use Skype with special user" sections should also be removed. Personally I think this level of sandboxing is good enough for many people. We can put a warning that the sandboxing is not 100% bullet-proof though. — Yellow block (talk) 07:07, 26 October 2015 (UTC)
I agree with you, honestly I also think that generic warnings about vulnerabilities are a bit useless, after all they can be everywhere... Maybe some words should be better spent in the Docker article itself. What about also reintroducing the previous instructions as an alternative? — Kynikos (talk) 10:33, 27 October 2015 (UTC)
Okay, I expanded the section a little. I can add some information about security into "Securing Skype" introduction after I collect relevant URLs. — Yellow block (talk) 08:18, 28 October 2015 (UTC)
Uh thanks, although actually I don't see the need to duplicate the detailed installation instructions in this article, personally I liked it better when there was just a link to the image and the upstream instructions. Also, there are many Skype images, maybe it's more fair to give more generalized instructions here and point users to the external manuals.
That said, it will be very interesting if you expand the article on security.
Kynikos (talk) 14:56, 30 October 2015 (UTC)
I made the suggested corrections but left info about sameersbn image. I tried a few others and they didn't work very well or required separate container with Pulseaudio. This one is tested and offers more features and he even fixed a bug for me quickly. — Yellow block (talk) 20:04, 1 November 2015 (UTC)
Looks good to me, well done :) Do you still want to further expand the article? Otherwise you can close this discussion. — Kynikos (talk) 13:53, 3 November 2015 (UTC)
No follow-up, closing. -- Alad (talk) 19:53, 9 August 2016 (UTC)


I'd like to add something like this at the end of the section:

"If you're using an application launcher that uses the $PATH (like dmenu) variables, you might want to change exec line in the file /usr/bin/skype directly like this (remember to make a backup before!):

 exec /usr/bin/apulse "$LIBDIR/skype/skype" "$@"

Freebe (talk) 11:12, 11 November 2015 (UTC)

Hi, I suppose you're referring to the Skype#Skype sound section. The modification you suggest would not survive a package upgrade, if I were you I'd use a shell alias for the skype command, maybe that's something worth adding to the article. See Dmenu#Support_for_shell_aliases for having dmenu see aliases (you may want to reupload the package to AUR). Alternatively, you can try to put a new wrapping script in the PATH, like /usr/local/bin/paskype that in turn launches skype with apulse. — Kynikos (talk) 03:05, 12 November 2015 (UTC)

Skype web version as a Chromium app

What do you think of adding a new short section, after "Skype for Linux Alpha", that mentions the possibility and details to run "chromium --app='https://web.skype.com/'" as an alternative to the new client? This may be useful to people who do not want to install a binary blob from AUR. Andreyv (talk) 09:25, 17 August 2016 (UTC)

Skype legacy version incompatible with new version

According to https://wiki.debian.org/skype, legacy Skype can not message or call anybody using the new version on any platform. If so, this note should be added to the wiki page here and enough to kill off using the legacy client completely. Bulletmark (talk) 01:57, 25 October 2016 (UTC)

  • This seems false. I'm using the legacy version, and I can still call and message people on the most recent OS X version. Ostiensis (talk) 01:54, 25 October 2016 (UTC)
The old Skype client cannot join new style group chats. There are also some reports of one-on-one video and voice chat no longer working between the old Linux client and some newer clients, but I'm not sure about that. Lonaowna (talk) 14:26, 25 October 2016 (UTC)

After installing it today and logging in alongside the up-to-date Android client, I made the following observations:

  • Messages that I send on the mobile client do not show up on desktop and vice versa.
  • Contacts can still receive messages from both clients.
  • Most recent messages are synced, but only received messages (seems to be ~20 days).
  • Group chats do not show up at all on desktop, even when a new message should be received (I don't know if all grup chats have been converted to new ones).

Not being able to have reliable cross-platform chat history, or participating in group chats anymore should be noted in the main article, given someone can confirm my findings. --Krukai (talk) 19:12, 30 January 2017 (UTC)

I propose to archive this article, it seems that support gets progressively worse. The web client is not documented on this article besides installing some AUR package, probably due to it being a "wrapper for web.skype.com". -- Alad (talk) 19:19, 30 January 2017 (UTC)
One additional observation: messages that the desktop client 'catches' first are not synced to mobile as well. Given how all messages are properly synced across devices otherwise, it seems that the old protocol messes with server-side data in ways it should not be able to. At this point any further server update might silently break other features, until the client is completely unusable. --Krukai (talk) 20:50, 30 January 2017 (UTC)
I'm not sure if we can "vote" here, but I think we should leave this page up. Skype is clearly a piece of crap, but some of us rely on it for work or otherwise, due to its widespread use elsewhere. The new wrapper still does not have feature parity, although it looks like it's heading that way. Until then, I think this collection of fixes and information is still useful. -- Ostiensis (talk) 23:01, 30 January 2017 (UTC)
I'd say nuke it: Microsoft will shut down the old client in March. Lonaowna (talk) 01:00, 7 February 2017 (UTC)
That thread seems speculative to me. However, if they are correct, and the old client is really EOL, then why don't we just nuke the page on 1 March? Being EOL would be pretty unequivocal. -- Ostiensis (talk) 03:53, 7 February 2017 (UTC)
There are multiple people reporting it, but I can't find an official Microsoft page. But waiting until 1 March is a good idea in any case. Lonaowna (talk) 09:58, 7 February 2017 (UTC)
Oops, false news. "At this time we are not retiring any of the existing working Linux Clients." Lonaowna (talk) 01:41, 11 February 2017 (UTC)
Nah, just alternative facts. 😁 Okay, good to know; thanks for following up. In that case, IMO there's no need to retire this page yet. -- Ostiensis (talk) 06:31, 11 February 2017 (UTC)

Systemd-nspawn security

Hello, can someone provide me more details on how secure systemd-nspawn is? I have limited knowledge about this but since there is a warning message saying that it is not fully secure, can someone point out a link or something more specific? Maybe a syntax example? Thank you. Alex.theoto (talk) 18:19, 14 November 2016 (UTC)