At least myself I was never able to do something else than text messages with Skype for Web.

In all honesty, it works with video calls, but with Edge under Windows 10 .

And there are rumors that sometimes it worked also with audio calls under Linux, while using Chrome (the closed source one, not Chromium)

Regarding desktop sharing, there's no such things for Skype for Web.

Has Skype only recently introduced a dependency on a login1 server? I have successfully run Skype on both Slackware64 14.2 and Slackware64-current over the last few months. This applies up to and including Skype version 7.1.11 from early April (I haven't tried anything more recent).

1 members found this post helpful.

Yes, it does use the services of a login1 server since long time ago.

And, how Slackware does not ships one, the SBo package installs also a login1 mock server.

However, having installed both ConsoleKit2 and a login1 server, whether mock or a real one, may confuse other software, which finds the mock server and tries to use it.

Notably, this is the case of current Plasma5 for slackware-current, which apparently prefers a login1 server.

Probably the KDE4 form Slackware 14.2 (or -current) works with no issues, preferring the ConsoleKit2 instead.

Care to explain this unfounded statement?

I think that statement is based on a previous thread that if the skypeforlinux package is installed that uses the skype-dbus-mock causes Plasma5 to break when trying to shutdown or reboot.

I've not tested this to ensure the validity of the bug report, I just remember the thread. LuckyCyborg was being his/her usual attacking self saying that the skypeforlinux SBo maintainer should've provided a warning for a bug nobody knew about that apparently only happens when running -current with ktown.

The way I read the last few posts, LuckyCyborg is suggesting the replacement of ConsoleKit2 with elogind.
My problem is I find the arguments spurious, being based on edge cases.
Good for you, but is Wayland really ready for the prime time?
Actually, companies and Microsoft are pushing for the adoption of Microsoft Teams as it is more capable with multiplatform support. (I recently built the Linux client from SlackBuilds.org) There is no Linux support for the Skype for Business app that companies use.
Personal computers have generally lacked the hardware to support multiseat.

1 members found this post helpful.

Unfortunately, I am able to confirm that the latest skypeforlinux package from SlackBuilds.org interacts badly even with the latest and last Plasma5 build shipped by Mr. Hameleers, under the following setup:

- slackware64-current updated up to Thu May 28 and installed in a Kingston SDD of 240GB as sole operating system
- Plasma5 updated up to the Final Release (this one with broken kinfocenter)
- skype4linux 8.59.0.77 (latest on SBo at this date) built and installed via sbopkg
- SDDM autologin to an unprivileged user
- skypeforlinux logged in a valid Skype account and launched at desktop startup

The issue manifests like this: when you execute shutdown or reboot from the "Leave" section of KickOff, the desktop will be closed and will remain a black screen with a visible mouse. Manualy deleting the Python script /usr/bin/skype-dbus-mock will restore the Plasma5 power controls after a reboot, but skypeforlinux will not work anymore.

Anyway, this issue was already confirmed by various users and apparently is quite easy to be reproduced - usually being about threads regarding power control issues with Plasma5 fixed by skypeforlinux removal and this happened even long time after the cited thread, like is this one:

https://www.linuxquestions.org/quest...e5-4175671193/

I would like to beg the esteemed forum user basmadrigal to stop his usual attacks started against certain forum users who does not fully follow the current ideology established by the esteemed Elders Council.

PS. I remember to the esteemed forum user basmadrigal that the one who questioned (in the cited thread) this lack of information from SBo README of skypeforlinux was me, not the thread's OP.

3 members found this post helpful.

If you want to use Skype but without installing a broken login1 implementation, you can try the Skype online version and wrap it as a Chromium app.
I gave instructions in the same thread mentioned above: https://www.linuxquestions.org/quest...5/#post6048481

Who knows? But certainly we will never know, if we avoid playing with it just because the Church ministers said that the sole god is ConsoleKit2...

Probably, but even in real life I know a serious amount of persons asked to work or learn from home, who are also asked for a functional Skype setup.

What you believe that is needed for a computer to support multiseat, hardware wise?

How I still don't did myself this particular setup, I asked one of my friends who did it with Fedora while using this right now. He claims that he followed this documentation:

https://www.freedesktop.org/wiki/Sof...emd/multiseat/

I know, is about THAT thing docs, but apparently elogind does the things in a similar manner.

So, my friend said that for a full multiseat setup, you need at least a graphics card capable to drive two independent outputs, like are the older than dirt NVidia GeForce 210 or ATI Radeon 4350, the ability to connect 2 mouses and 2 keyboards via USB ports and two independent audio cards, like the audio embedded in motherboard and a cheap USB audio device.

Apparently, a multiseat setup requires a quite cheap hardware, after all.

No, Sir! I tested again several minutes ago, and today Skype on-line refuses the latest Firefox from -current as incompatible browser, and even with your latest Chromium build, it offers only text messages.

glib-networking-2.64.3
https://download.gnome.org/sources/g...-2.64.3.tar.xz

I am running skype 8.58.0.93 on my slackware 14.2 without problems. Built from a .deb package manually.

Yes, BUT we talk about slackware-current and skypeforlinux interactions with desktops like Plasma5, which is radical different situation than Slackware 14.2 and its KDE4.

I believe nobody questioned the good work of skypeforlinux package from SBo under Slackware 14.2 and KDE4.

There's a skype client on flathub.org as well which you could try looking into, just have to get flatpak running which is all available on slackbuilds.org

Take note that MS is retiring some of the capabilities of Skype relatively soon and pushing very hard for businesses to migrate to Teams. I'm running the Linux-native Teams preview on an unmodified Slackware-current install. Take that as you will.

1 members found this post helpful.