Package Details: skypeforlinux-bin 8.133.0.202-1

Git Clone URL: https://aur.archlinux.org/skypeforlinux-bin.git (read-only, click to copy)
Package Base: skypeforlinux-bin
Description: Skype for Linux
Upstream URL: https://www.skype.com/
Keywords: skype
Licenses: custom
Conflicts: skype, skypeforlinux
Provides: skype, skypeforlinux
Submitter: Hanabishi
Maintainer: Hanabishi
Last Packager: Hanabishi
Votes: 330
Popularity: 1.05
First Submitted: 2024-03-04 17:57 (UTC)
Last Updated: 2024-11-21 03:34 (UTC)

Pinned Comments

Hanabishi commented on 2024-07-31 07:28 (UTC) (edited on 2024-08-20 13:25 (UTC) by Hanabishi)

There is a problem with Skype being stuck on the login screen on first launch. That happens when your org.freedesktop.secrets provider doesn't have a keyring configured, i.e. also first launch.

I don't know if this is a quirk of libsecret or Skype itself, but we can't do pretty much anything about it anyway.

Solutions are simple though:

  1. Despite the login screen being stuck, the login itself is actually successful. So just kill it and run Skype again, it should be fine after that.

  2. Configure your default keyring manually (using seahorse, kwalletmanager etc.) before running Skype.

bulletmark commented on 2020-04-30 10:01 (UTC) (edited on 2022-06-13 00:22 (UTC) by bulletmark)

To get automatic login, install a package that provides org.freedesktop.secrets, e.g. gnome-keyring.

To get a systray icon, install libappindicator-gtk3. On GNOME, then install the appindicator extension.

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 31 Next › Last »

mozo commented on 2021-04-15 07:39 (UTC)

No problems on my end.

Hi-Angel commented on 2021-04-15 07:21 (UTC)

While building I get this error:

warning: https unexpectedly said: 'Version/.git/objects/pack/pack-597ac35cba0f518c446371def883eb47473b7891.keep

Is it only me?

Just built skype, everything is fine, I see no error. So yeah, it's either something on your side, or some sporadic failure on some server.

Any pointers?

Looks as a git related error, but I don't see anything git-related in PKGBUILD. Might it be you're using some aur-helper, and the error come from it when it tried to download the PKGBUILD?

pescepalla commented on 2021-04-15 06:53 (UTC)

While building I get this error:

warning: https unexpectedly said: 'Version/.git/objects/pack/pack-597ac35cba0f518c446371def883eb47473b7891.keep

Is it only me? Any pointers?

bulletmark commented on 2021-04-14 12:53 (UTC) (edited on 2021-04-14 12:53 (UTC) by bulletmark)

@txtsd, it was out of date because there was a new stable version which I just updated to now. Note that 8.*.0.* are stable versions, 8.*.76.* are preview versions.

txtsd commented on 2021-04-14 11:30 (UTC)

Is it normal for the stable package to show an available update which is actually a preview build?

Hi-Angel commented on 2021-03-04 20:27 (UTC) (edited on 2021-03-04 20:29 (UTC) by Hi-Angel)

Fun thing is Skype. While following in defence of swap, I replaced the vm.swappiness = 10 I usually used with much larger vm.swappiness = 100 (which btw was worth it, despite me having a slow HDD, not an SSD. Although might be because I also use zswap), and I expected Skype to be one of the 1st apps on my system to go into swap, since I only use it once in the morning, and throughout the rest of the day it just idles in background. Well, for some reason it is far from reality. Skype has 6 processes, and all of them went through, I think, 2 swap storms upon me getting critically low on RAM, with 0 (zero!) kilobytes in SWAP (I monitor it with smem -kc "name user pid vss pss rss swap")! Only on 3rd swap storm Skype has gotten just a tiny bit of its memory into SWAP (0, 0, 1.8M, 24.0K, 1.2M, 2.9M). For comparison: the 2.9M-in-swap process is surrounded (in terms of PSS) by emacs and plasma, that has 6.1M and 53.8M in swap respectively.

Idk yet why Skype behaves that way, but am very curious. An interesting behavior, and can't say one I like. So, anyway, just sharing, in case someone might have an insight into it, or just might be interested.

bodograumann commented on 2021-03-04 17:08 (UTC) (edited on 2021-03-04 17:08 (UTC) by bodograumann)

I was able to work around the current alsa problem by creating aliases in the ~/.asoundrc:

pcm.call {
  type hw
  card PCH
  device 0
}

pcm.mic_call {
  type hw
  card PCH
  device 0
}

pcm.loopback_call {
  type hw
  card PCH
  device 0
}

nimbusflow commented on 2021-02-28 23:30 (UTC)

Thanks @mozo. It's working when I use apulse, so I'm guessing it's an ALSA-related problem. These links I found seem to suggest that too:

https://forums.gentoo.org/viewtopic-p-8577792.html

https://forum.mxlinux.org/viewtopic.php?t=63324

mozo commented on 2021-02-28 00:09 (UTC)

@nimbusflow Everything is ok on my end.

nimbusflow commented on 2021-02-27 23:56 (UTC)

Ever since I updated to 8.69.0.77-1 I can't make/answer calls - every time I do, skype automatically logs me out. This happens even with test calls.

Anyone else having similar issues? I haven't tried to downgrade to 8.68.0.100 yet.