From ArchWiki
Revision as of 00:54, 4 October 2017 by Lonaowna (talk | contribs) (Skype legacy version incompatible with new version: re)
Jump to: navigation, search

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 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: -- Alad (talk) 07:08, 21 August 2015 (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=''" 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, 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". -- 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)

Update: the old Skype will stop functioning on 1 July 2017.[1] Lonaowna (talk)

Thanks Lonaowna. Had to happen at some point! Well, I still vote for nuking this page at least after legacy Skype "stop[s] functioning". Even so, would it be worth keeping a shortened version of this page, that just explains that the beta is the web version in a wrapper? —Ostiensis (talk) 03:17, 5 June 2017 (UTC)
So the old client has been officially retired for 3 months now, but it seems that it is still (partially) working (see e.g. comments at skypeAUR).
I think it's time to delete the section about the old client. Even if it's still working now, it is bound to stop working sometime soon. Everyone currently using it can keep using it, but they don't need this page. People who don't use Skype on Arch yet should install the new client, and would be stupid to install the old client.
Lonaowna (talk) 18:01, 3 October 2017 (UTC)

I don't think an ad hominem attack was necessary. It's impossible to know how many other people have installed it, but I… don't think we are all stupid. Honest question though, what is the disadvantage of leaving this relevant section in for those that still do use the old client? —Ostiensis (talk) 22:47, 3 October 2017 (UTC)

Sorry, I didn't mean to attack anyone. Just saying that I would consider it a waste of time setting up/tweaking a program that can stop working at any moment. The people who have it running how they want it already don't need this page.
With the section gone we can better judge if this page is worth existing so we can take care of the archival proposal.
If you think it still has value I guess we can keep it a little longer. Lonaowna (talk) 00:54, 4 October 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)