[SOLVED] skypeforlinux latest update not working

Gordie · 09-11-2018, 11:24 PM

I use ruario's script to repackage Skype for linux.

The last version skypeforlinux-8.29.0.50-x86_64-1ro works for Slackware64 14.2 as well as Current.

The latest version skypeforlinux-8.30.0.50-x86_64-1ro does not load. In 14.2 nothing happens at all even when I try with a terminal. No errors show.

In Current a blank space appears where the icon usually occupies space in the tray. After a brief interlude the blank space disappears. Again when using a terminal. No errors show.

I had to revert back to skypeforlinux-8.29.0.50-x86_64-1ro on both computers. A search of LQ and anywhere else I can think of bears no fruit

Darth Vader · 09-11-2018, 11:34 PM

Executing "/usr/share/skypeforlinux/skypeforlinux" aka The Real Thing, I got

Code:

bash-4.4# ./skypeforlinux --help

(skypeforlinux:9564): Gtk-WARNING **: 07:31:56.836: Theme parsing error: gtk.css:127:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version

(skypeforlinux:9564): Gtk-WARNING **: 07:31:56.836: Theme parsing error: gtk.css:128:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version

(skypeforlinux:9564): Gtk-WARNING **: 07:31:56.836: Theme parsing error: gtk.css:132:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn't be used anymore. It will be removed in a future version
dbus[9564]: dbus message iterator has already been closed, or is uninitialized or corrupt
  D-Bus not built with -rdynamic so unable to print a backtrace
Server response: <?xml version="1.0" encoding="UTF-8"
Aborted

SO, looks like skypeforlinux-8.30.0.50 is no longer compatible with Slackware. Maybe it wants to contact some kind of systemd service over DBUS?

jostber · 09-12-2018, 03:54 AM

There is a recent Skype package for Slackware in the Sya54m repository you might check out:

https://www.sya54m.eu/repository.php

Lysander666 · 09-12-2018, 05:54 AM

Thanks Darth et al. I will withhold upgrading till it's confirmed that the newer versions work.

Qury · 09-12-2018, 05:59 AM

the same dbus error is present on current as well.

Versions:
- slackware64-current updated to 2018-09-10 updates
- skypeforlinux-8.30.0.50-1

chrisretusn · 09-12-2018, 07:00 AM

Executing the shell in /usr/bin results in nothing. Executing as Darth Vader did, results in same error. Slackware64-current using skypeforlinux 8.30.0.50

Alien Bob · 09-12-2018, 08:03 AM

The latest version is skypeforlinux_8.30.76.41, but the tarball with the most recent timestamp (11 Sep versus 8 Sep) is skypeforlinux_8.30.0.50.
Perhaps try the 8.30.76.41 release to see if that works better?

Qury · 09-12-2018, 08:09 AM

So, i've done some googling and it turns out that libtool package should be built with the "--enable-asserts" switch. I've tried this and the error message has changed to the below.

Code:

bash-4.4$ ./skypeforlinux 
dbus[2097]: dbus message iterator has already been closed, or is uninitialized or corrupt
  /usr/lib64/libdbus-1.so.3(_dbus_print_backtrace+0x1f) [0x7fb06374409f]
  /usr/lib64/libdbus-1.so.3(_dbus_abort+0x9) [0x7fb063747079]
  /usr/lib64/libdbus-1.so.3(+0x3f48b) [0x7fb06373648b]
  /usr/lib64/libdbus-1.so.3(+0x28039) [0x7fb06371f039]
  /usr/lib64/libdbus-1.so.3(dbus_message_iter_get_arg_type+0x30) [0x7fb063720fa0]
  /usr/share/skypeforlinux/skypeforlinux() [0x2cbc4c9]
  /usr/share/skypeforlinux/skypeforlinux() [0x2cba5fc]
  /usr/share/skypeforlinux/skypeforlinux(_ZN4atom18PowerObserverLinux17OnInhibitResponseEPN4base13ScopedGenericIiNS1_8internal19ScopedFDCloseTraitsEEEPN4dbus8ResponseE+0x25) [0x4ea6495]
  /usr/share/skypeforlinux/skypeforlinux() [0x2cbda10]
  /usr/share/skypeforlinux/skypeforlinux() [0x2cc0480]
  /usr/share/skypeforlinux/skypeforlinux() [0x2cbde96]
  /usr/share/skypeforlinux/skypeforlinux() [0x2cc085f]
  /usr/share/skypeforlinux/skypeforlinux() [0x491a8eb]
  /usr/share/skypeforlinux/skypeforlinux() [0x493a089]
  /usr/share/skypeforlinux/skypeforlinux() [0x493a3a8]
  /usr/share/skypeforlinux/skypeforlinux() [0x493a781]
  /usr/share/skypeforlinux/skypeforlinux() [0x48dd759]
  /usr/share/skypeforlinux/skypeforlinux() [0x4950570]
  /usr/share/skypeforlinux/skypeforlinux() [0x2a4e68e]
  /usr/share/skypeforlinux/skypeforlinux() [0x2a4e48e]
  /usr/share/skypeforlinux/skypeforlinux() [0x2ab441d]
  /usr/share/skypeforlinux/skypeforlinux() [0x2900cc3]
  /usr/share/skypeforlinux/skypeforlinux() [0x2ca7bbc]
  /usr/share/skypeforlinux/skypeforlinux() [0x430de4d]
  /usr/share/skypeforlinux/skypeforlinux() [0x2ca6842]
  /usr/share/skypeforlinux/skypeforlinux(main+0x4d) [0x4dbe43d]
  /lib64/libc.so.6(__libc_start_main+0xe7) [0x7fb05d6afba7]
  /usr/share/skypeforlinux/skypeforlinux() [0x1806029]
Server response: <?xml version="1.0" encoding="UTF-8"
Aborted

The last version that works for me on current is 8.29.0.50

Qury · 09-12-2018, 08:20 AM

Quote:

Originally Posted by Alien Bob

The latest version is skypeforlinux_8.30.76.41, but the tarball with the most recent timestamp (11 Sep versus 8 Sep) is skypeforlinux_8.30.0.50.
Perhaps try the 8.30.76.41 release to see if that works better?

I've tried with the latest deb and rpm downloaded on 2018-09-12 (today), but it still gives me the same result as in my previous post

kjhambrick · 09-12-2018, 12:26 PM

Thanks to Gordie and All'Y'All for the heads up.

I unfortunately need Skype for work and I don't want it on my Win7 VM so I've been running ruario's SlackBuild on Slackware64 14.2

I guess I'll stay on skypeforlinux-8.18.0.6-x86_64-1ro for now ...(

old but working

)...

-- kjh

bassmadrigal · 09-12-2018, 01:57 PM

Quote:

Originally Posted by kjhambrick

I guess I'll stay on skypeforlinux-8.18.0.6-x86_64-1ro for now ...(

old but working

)...

As long as skype doesn't delete old versions, you should be able to pass a VERSION to the latest-skype.sh script and it should package that specific version.

This way, if you want, you can update to the newest version that still works.

Code:

VERSION=8.29.0.50 latest-skype.sh

Darth Vader · 09-12-2018, 02:11 PM

Quote:

Originally Posted by Alien Bob

The latest version is skypeforlinux_8.30.76.41, but the tarball with the most recent timestamp (11 Sep versus 8 Sep) is skypeforlinux_8.30.0.50.
Perhaps try the 8.30.76.41 release to see if that works better?

Eric, like I said already, I suspect that the latest Skype4Linux wants to contact some systemd service via DBUS, then fails.

You are kind to explain us about that systemd-logind emulation, about which you talked in the past? You know, the one needed by Plasma5 to work under Wayland.

Because I suspect that this is the one which S4L wants to talks with. Maybe we will need to install it for S4L in the future. Err, from now.

bassmadrigal · 09-12-2018, 02:29 PM

Quote:

Originally Posted by Darth Vader

Eric, like I said already, I suspect that the latest Skype4Linux wants to contact some systemd service via DBUS, then fails.

This error has showed up in past versions of skype without it being related to systemd, so let's hope Microsoft hasn't made that a requirement.

In the cases above, people were able to start skype as root, but it wouldn't open as a regular user (I'm not sure if it's the same problem here). According to the first link, it took several releases from MS to fix the issue.

Darth Vader · 09-12-2018, 02:33 PM

Quote:

Originally Posted by bassmadrigal

This error has showed up in past versions of skype without it being related to systemd, so let's hope Microsoft hasn't made that a requirement.

In the cases above, people were able to start skype as root, but it wouldn't open as a regular user (I'm not sure if it's the same problem here). According to the first link, it took several releases from MS to fix the issue.

Hmm, I do not tested as root yet, BUT I done it right now. The latest S4L does not work as "root" too.

Alien Bob · 09-12-2018, 05:41 PM

Quote:

Originally Posted by Darth Vader

Hmm, I do not tested as root yet, BUT I done it right now. The latest S4L does not work as "root" too.

I tried as root but that gave the exact same error. Only reverting to an older release worked. Running the executable under 'trace' did not give me any pointers either.