LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-23-2018, 11:09 AM   #31
ChuangTzu
Senior Member
 
Registered: May 2015
Location: Where ever needed
Distribution: Slackware/Salix, FreeBSD
Posts: 1,065

Rep: Reputation: 835Reputation: 835Reputation: 835Reputation: 835Reputation: 835Reputation: 835Reputation: 835
Lightbulb


Quote:
Originally Posted by Darth Vader View Post
Everyone knows already what should be done to avoid those kinds of problems.

BUT that thing will not be done, because of a bunch of guys loves to play fundamentalists.
I was waiting for you to swing this back around to your real point.
 
Old 09-23-2018, 01:15 PM   #32
bamunds
Member
 
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2 FVWM
Posts: 547

Rep: Reputation: 147Reputation: 147
So we don't want our family and friends to be protected from phishing and identity theft or interrupted streams with lousy compression and huge overhead? Sorry I think it important to educate family and friends about what MS is really doing with the Skype data and they gladly switched to WIRE.
Cheers.
 
3 members found this post helpful.
Old 09-23-2018, 01:42 PM   #33
perbh
Member
 
Registered: May 2008
Location: Republic of Texas
Posts: 310

Rep: Reputation: 55
Quote:
Originally Posted by frankbell View Post
I don't want to seem rude, but, I must say, spoken like someone who has limited contacts with run-of-the-mill typical Windows and Mac users. They are not going to leave what they are used to--especially not Mac users trapped in the walled orchard.

Face it, we persons here at LQ are geeks who love taking computers and operating systems apart and putting them back together.

We are not typical.

I'll use my girl friend for an example. She is a sane and savvy Windows user. She doesn't have problems with viruses and Trojans because she doesn't visit dodgy websites, she runs an AV and a firewall, and she delights in identifying and deleting spammy emails; she has antennae that quiver at the sight of a phish. But after almost a decade, I haven't been able to convert her to Linux because she needs her MSOffice because it's what she knows.
lol lol - you just described my wife (apart from the antennas!!) - she once got hit by clicking on a link that said 'chaze.com' (rather than 'chase.com') - duhhh! I have since (tried to) teach her to mouse-over on a link to see what it actually points to. Probably won't help much ...
 
Old 09-23-2018, 02:44 PM   #34
hitest
Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 5,586

Rep: Reputation: 1636Reputation: 1636Reputation: 1636Reputation: 1636Reputation: 1636Reputation: 1636Reputation: 1636Reputation: 1636Reputation: 1636Reputation: 1636Reputation: 1636
I stopped using Skype about the time that Microsoft bought it and not for ideological reasons. Over time it functioned less well on Slackware.
I'm looking forward to Slackware 15.0.
 
2 members found this post helpful.
Old 09-23-2018, 02:45 PM   #35
RadicalDreamer
Member
 
Registered: Jul 2016
Location: USA
Distribution: Slackware64-Current
Posts: 890

Rep: Reputation: 408Reputation: 408Reputation: 408Reputation: 408Reputation: 408
Quote:
Originally Posted by khronosschoty View Post
What should be done (?), please spell it out! I'm sitting here imagining that you are saying that, "everyone knows we should adopt systemd", and other things like that.
He did sort of:
Quote:
Originally Posted by Darth Vader View Post
Excuse me? Now an AMD Phenom x4 9650 at 2.3GHz is obsolete?

AND, the same Skype release worked fine before upgrading the GLIBC to 2.28 on Slackware-current.
This is a campaign against GLIBC 2.28+.
 
2 members found this post helpful.
Old 09-23-2018, 03:03 PM   #36
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 369
Blog Entries: 2

Rep: Reputation: 168Reputation: 168
Quote:
Originally Posted by RadicalDreamer View Post
He did sort of:

This is a campaign against GLIBC 2.28+.
I see, thank you.
 
Old 09-23-2018, 07:43 PM   #37
chrisVV
Member
 
Registered: Aug 2010
Posts: 322

Rep: Reputation: 139Reputation: 139
Quote:
Originally Posted by Darth Vader View Post
Like the title says.

And I for one, I consider this being a terrible huge issue, because the Skype is the software which I use to communicate with my family, with my friends, and with my colleagues at work.

Everyone uses Skype, so I should, if I want to communicate with them.

Oh, and that ELOGIND does not compile in Slackware-current in any version released. Apparently the Slackware is so long way away of Gentoo, that's not worth considering that ELOGIND.

I am very disappointed.
elogind-238.1 compiles for me. What errors do you get? (Admittedly I am using PAM but elogind is supposed to compile without it.)

However it won't help you because even the latest (logind) versions of skype crash on start-up with the most recent glibc in slackware-current (glibc-2.28). Given that glibc is not supposed to break ABI on its minor version bumps, that is odd - it isn't supposed to do that.
 
Old 09-23-2018, 07:51 PM   #38
chrisVV
Member
 
Registered: Aug 2010
Posts: 322

Rep: Reputation: 139Reputation: 139
Quote:
Originally Posted by chrisVV View Post
However it won't help you because even the latest (logind) versions of skype crash on start-up with the most recent glibc in slackware-current (glibc-2.28). Given that glibc is not supposed to break ABI on its minor version bumps, that is odd - it isn't supposed to do that.
Arch users seem to be suffering the same problem: https://bugs.archlinux.org/task/59550 .
 
Old 09-23-2018, 08:14 PM   #39
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 490

Rep: Reputation: 284Reputation: 284Reputation: 284
Quote:
Originally Posted by chrisVV View Post
Arch users seem to be suffering the same problem: https://bugs.archlinux.org/task/59550 .
Maybe that will quieten down the "why do you want to use Skype" crowd. It seems other apps are affected by the new glibc-2.28 too so better hope your favourite apps aren't included. You could possibly even thank Skype for exhibiting the problem, hence DV for starting discussion here on how to possibly fix it (perhaps along with your favourite app).

chris
 
2 members found this post helpful.
Old 09-23-2018, 08:18 PM   #40
chrisVV
Member
 
Registered: Aug 2010
Posts: 322

Rep: Reputation: 139Reputation: 139
Quote:
Originally Posted by chrisVV View Post
elogind-238.1 compiles for me. What errors do you get? (Admittedly I am using PAM but elogind is supposed to compile without it.)

However it won't help you because even the latest (logind) versions of skype crash on start-up with the most recent glibc in slackware-current (glibc-2.28). Given that glibc is not supposed to break ABI on its minor version bumps, that is odd - it isn't supposed to do that.
Ah, the good news is that the latest recompilation of skype (version 8.31.76.88) fixes the problem with glibc-2.28. So you need to get elogind working. What compilation error are you getting?

The only problem I have experienced with elogind is that running it can stop xfce's shutdown/reboot options working correctly, possibly because it interferes with ConsoleKit, so it is best to start it in the skypeforlinux script and stop it when skype is closed.
 
Old 09-23-2018, 11:55 PM   #41
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Original Poster
Rep: Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231
Quote:
Originally Posted by chrisVV View Post
Ah, the good news is that the latest recompilation of skype (version 8.31.76.88) fixes the problem with glibc-2.28. So you need to get elogind working. What compilation error are you getting?
This one: https://github.com/elogind/elogind/issues/74

Code:
ninja -C build
ninja: Entering directory `build'
[1/323] Compiling C object 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o'.
FAILED: src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o 
ccache cc -Isrc/libelogind/src@libelogind@@elogind@sta -Isrc/libelogind -I../src/libelogind -Isrc/basic -I../src/basic -Isrc/shared -I../src/shared -Isrc/systemd -I../src/systemd -Isrc/login -I../src/login -Isrc/core -I../src/core -I../src/libelogind/sd-bus -I../src/libelogind/sd-id128 -Isrc/sleep -I../src/sleep -Isrc/update-utmp -I../src/update-utmp -I. -I../ -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -O0 -g -Wextra -Werror=undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time -Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -include config.h -fPIC -pthread -fvisibility=default  -MD -MQ 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o' -MF 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o.d' -o 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o' -c ../src/libelogind/sd-bus/bus-error.c
In file included from ../src/basic/util.h:47,
                 from ../src/libelogind/sd-bus/bus-error.c:34:
../src/basic/missing.h:1387:8: error: redefinition of ‘struct statx_timestamp’
 struct statx_timestamp {
        ^~~~~~~~~~~~~~~
In file included from /usr/include/sys/stat.h:446,
                 from ../src/basic/util.h:38,
                 from ../src/libelogind/sd-bus/bus-error.c:34:
/usr/include/bits/statx.h:25:8: note: originally defined here
 struct statx_timestamp
        ^~~~~~~~~~~~~~~
In file included from ../src/basic/util.h:47,
                 from ../src/libelogind/sd-bus/bus-error.c:34:
../src/basic/missing.h:1392:8: error: redefinition of ‘struct statx’
 struct statx {
        ^~~~~
In file included from /usr/include/sys/stat.h:446,
                 from ../src/basic/util.h:38,
                 from ../src/libelogind/sd-bus/bus-error.c:34:
/usr/include/bits/statx.h:36:8: note: originally defined here
 struct statx
        ^~~~~
[2/323] Compiling C object 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-container.c.o'.
FAILED: src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-container.c.o
Quote:
Originally Posted by chrisVV View Post
The only problem I have experienced with elogind is that running it can stop xfce's shutdown/reboot options working correctly, possibly because it interferes with ConsoleKit, so it is best to start it in the skypeforlinux script and stop it when skype is closed.
I believe that the issue of ELOGIND is bigger than this and our Dutch Overlord stopped his experiments with elogind for Plasma5 for a very reason:

The systemd-logind (hence the elogind) is a evolution of ConsoleKit which we use today even in -current, and offer a similar functionality as basis.

Then you cannot use them simultaneous, because they will step on each other shoes.

The real issue with Slackware looks like is that we are stuck from whatever reasons on this "old" ConsoleKit which apparently is about of being abandoned.

Please look there: https://github.com/ConsoleKit2/ConsoleKit2

The last activity is from 11 months ago.

I believe they they moved to systemd-logind with all family, including the dog and chickens.

-------------------------------------

However, I wonder if that elogind is the proper solution and replacement of systemd-logind while looking there: https://github.com/elogind/elogind/issues/70

Yes, people! There are many other software which uses its functionalities. And which shall be adapted eventually to elogind.

Last edited by Darth Vader; 09-24-2018 at 12:23 AM.
 
2 members found this post helpful.
Old 09-24-2018, 12:02 AM   #42
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Original Poster
Rep: Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231
Quote:
Originally Posted by RadicalDreamer View Post
This is a campaign against GLIBC 2.28+.
Reverting to GLIBC 2.27 will be only a temporary solution.

I am intelligent enough to see that is not worth a campaign "pro-2.27", because sooner or later that last "non-logind" Skype will stop working becoming obsolete.

Last edited by Darth Vader; 09-24-2018 at 12:09 AM.
 
1 members found this post helpful.
Old 09-24-2018, 02:08 AM   #43
RadicalDreamer
Member
 
Registered: Jul 2016
Location: USA
Distribution: Slackware64-Current
Posts: 890

Rep: Reputation: 408Reputation: 408Reputation: 408Reputation: 408Reputation: 408
Quote:
Originally Posted by Darth Vader View Post
Reverting to GLIBC 2.27 will be only a temporary solution.

I am intelligent enough to see that is not worth a campaign "pro-2.27", because sooner or later that last "non-logind" Skype will stop working becoming obsolete.
What is your solution? Replace Consolekit with Elogind or install the software which shall not be named?
 
Old 09-24-2018, 02:14 AM   #44
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 490

Rep: Reputation: 284Reputation: 284Reputation: 284
Quote:
Originally Posted by Darth Vader View Post
This one: https://github.com/elogind/elogind/issues/74

Code:
ninja -C build
ninja: Entering directory `build'
[1/323] Compiling C object 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o'.
FAILED: src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o 
ccache cc -Isrc/libelogind/src@libelogind@@elogind@sta -Isrc/libelogind -I../src/libelogind -Isrc/basic -I../src/basic -Isrc/shared -I../src/shared -Isrc/systemd -I../src/systemd -Isrc/login -I../src/login -Isrc/core -I../src/core -I../src/libelogind/sd-bus -I../src/libelogind/sd-id128 -Isrc/sleep -I../src/sleep -Isrc/update-utmp -I../src/update-utmp -I. -I../ -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -O0 -g -Wextra -Werror=undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit-function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time -Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector -fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -include config.h -fPIC -pthread -fvisibility=default  -MD -MQ 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o' -MF 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o.d' -o 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-error.c.o' -c ../src/libelogind/sd-bus/bus-error.c
In file included from ../src/basic/util.h:47,
                 from ../src/libelogind/sd-bus/bus-error.c:34:
../src/basic/missing.h:1387:8: error: redefinition of ‘struct statx_timestamp’
 struct statx_timestamp {
        ^~~~~~~~~~~~~~~
In file included from /usr/include/sys/stat.h:446,
                 from ../src/basic/util.h:38,
                 from ../src/libelogind/sd-bus/bus-error.c:34:
/usr/include/bits/statx.h:25:8: note: originally defined here
 struct statx_timestamp
        ^~~~~~~~~~~~~~~
In file included from ../src/basic/util.h:47,
                 from ../src/libelogind/sd-bus/bus-error.c:34:
../src/basic/missing.h:1392:8: error: redefinition of ‘struct statx’
 struct statx {
        ^~~~~
In file included from /usr/include/sys/stat.h:446,
                 from ../src/basic/util.h:38,
                 from ../src/libelogind/sd-bus/bus-error.c:34:
/usr/include/bits/statx.h:36:8: note: originally defined here
 struct statx
        ^~~~~
[2/323] Compiling C object 'src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-container.c.o'.
FAILED: src/libelogind/src@libelogind@@elogind@sta/sd-bus_bus-container.c.o
This part of the problem is fixed for me by applying the attached patch.

chris
Attached Files
File Type: txt redef_statx.diff.txt (1.2 KB, 16 views)
 
3 members found this post helpful.
Old 09-24-2018, 03:42 AM   #45
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 490

Rep: Reputation: 284Reputation: 284Reputation: 284
Latest skype running in a -current VM with elogind (patched as per previous post) running in background.

Click image for larger version

Name:	skypeoncurrent.png
Views:	48
Size:	182.5 KB
ID:	28656

For elogind to run, I had to make a symlink in /run to /var/run/dbus because elogind looks for /run/dbus/system_bus_socket at startup. Maybe that's a location that can be set at build time but the symlink works well enough for now.

Yep, 'find src/ -type f |xargs grep run\/dbus' gives:
Code:
src/basic/def.h:#define DEFAULT_SYSTEM_BUS_ADDRESS "unix:path=/run/dbus/system_bus_socket"
src/libelogind/sd-bus/test-bus-vtable.c:#define DEFAULT_BUS_PATH "unix:path=/run/dbus/system_bus_socket"
src/libelogind/sd-bus/sd-bus.c:        strncpy(b->sockaddr.un.sun_path, "/var/run/dbus/system_bus_socket", sizeof(b->sockaddr.un.sun_path));
so it's easy enough to set that path correctly when building elogind.

chris

Last edited by chris.willing; 09-24-2018 at 04:26 AM. Reason: mention dbus symlink
 
6 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
unkown cause for systemd failure state - systemd-logind cannot start org.freedesktop.systemd1 after server reboot mario.p Linux - Server 5 07-30-2018 03:11 AM
[SOLVED] will slackware drop newer KDE versions or go systemd rob.rice Slackware 73 04-23-2017 02:03 PM
[SOLVED] How to compile latest sources using older gcc glibc versions and run them? nirvaanr Linux - Software 4 06-08-2016 10:32 AM
[SOLVED] removing previous older kernels "vmlinuz" when updates get newer versions james2b Linux - Newbie 7 09-12-2011 05:13 AM
how to use older versions of glibc turls Programming 4 07-07-2004 04:40 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:50 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration