LinuxQuestions.org
Help answer threads with 0 replies.
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-24-2018, 06:01 PM   #61
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 489

Rep: Reputation: 284Reputation: 284Reputation: 284

Quote:
Originally Posted by ChuangTzu View Post
Not going to hijack the thread, i'm not DV after all
In that case, please feel free to contribute something useful (something other than your usual snarking) to this thread. No one is perfect but in terms of contributions at LQ discussions, DV leaves you in the dust.

chris

Last edited by chris.willing; 09-24-2018 at 06:04 PM. Reason: politeness
 
1 members found this post helpful.
Old 09-24-2018, 06:15 PM   #62
ChuangTzu
Senior Member
 
Registered: May 2015
Location: Where ever needed
Distribution: Slackware/Salix, FreeBSD
Posts: 1,065

Rep: Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825Reputation: 825
Quote:
Originally Posted by chris.willing View Post
In that case, please feel free to contribute something useful (something other than your usual snarking) to this thread. No one is perfect but in terms of contributions at LQ discussions, DV leaves you in the dust.

chris
Considering it was in a discussion with the OP, is relevant to the use of Skype and was a continuation of an earlier suggestion, it may behoove you to review threads before taking things personally. Obviously, DV did not see the post as snarky or not contributing, given the content of his reply to my post and he obviously understood the content/meaning/intention of my post.

Lighten up.
 
Old 09-24-2018, 06:41 PM   #63
Wed
Member
 
Registered: Sep 2005
Location: Sweden
Distribution: Slackware
Posts: 173

Rep: Reputation: 34
The SIP protocol is properly standardardized and there are no lack of clients to use it.
 
1 members found this post helpful.
Old 09-24-2018, 07:21 PM   #64
chrisVV
Member
 
Registered: Aug 2010
Posts: 322

Rep: Reputation: 139Reputation: 139
Quote:
Originally Posted by chrisretusn View Post
During 'meson setup' I do get one warning. Since it's a warning not to worried about it. Though I am puzzled a bit.
Code:
Message: WARNING:
        The local user with the configured user name "nobody" of the nobody user does not have UID 65534 (it has 99).
        Your build will result in an user table setup that is incompatible with the local system.
In the linux kernel 65334 is the uid and gid number for overflows. See 'cat /proc/sys/fs/overflowuid' and 'cat /proc/sys/fs/overflowgid'. It is used by the kernel for subsystems which only support 16-bit IDs where an ID is encountered of greater than 65535. (In 16-bit two's complement it is -2.)

Some distributions map the nobody user and group to it: see https://lwn.net/Articles/695526/ for some discussion about that. logind and elogind synthesize nobody on UID/GID 65334 and report a mismatch when compiling if the local system has it on another number.

If you wanted to solve the warning, one answer is specify in /etc/passwd and /etc/group that ID 99 is for oldnobody and 65534 for nobody: that would prevent any files being unreachable. But the best thing is to ignore it. It almost certainly makes no difference in relation to skype or anything else you are going to meet in practice.
 
3 members found this post helpful.
Old 09-24-2018, 07:48 PM   #65
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 489

Rep: Reputation: 284Reputation: 284Reputation: 284
Quote:
Originally Posted by chrisretusn View Post
I patched the /usr/share/skypeforlinix/skypeforlinux to run elogind before starting skype and then kill it after quitting skype.
[snip]
The patch for skypeforlinux is attached.
A problem with this approach is that skype cannot then be started from the Applications->Internet (xfce) menu as an ordinary user; the script's command 'sudo -b /lib/elogind/elogind &' needs a command line to enter the user's password.

Maybe someone who knows how could write a .policy file so that the script could launch elogind using pkexec, which would pop up a dialog box to ask for a password. Ideally it should work with the user's password (like sudo) rather than root password. Any takers?

chris

Edit: I just tried it with gksudo (from SBo's gksu package) rather than plain sudo and that seems to work OK. It's one more thing to have to install though, so if we could make pkexec work like sudo it would still be preferable.

Last edited by chris.willing; 09-24-2018 at 08:16 PM. Reason: Mention gksudo
 
Old 09-24-2018, 10:43 PM   #66
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,071

Rep: Reputation: 1453Reputation: 1453Reputation: 1453Reputation: 1453Reputation: 1453Reputation: 1453Reputation: 1453Reputation: 1453Reputation: 1453Reputation: 1453
Quote:
Originally Posted by Wed View Post
The SIP protocol is properly standardardized and there are no lack of clients to use it.
Yep. I worked in that space for years at Nortel.

The only drawback is when you want to talk to an old-style landline or other non-SIP endpoints. \_(ツ)_/
 
Old 09-24-2018, 10:58 PM   #67
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,238

Rep: Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929Reputation: 929
Quote:
Originally Posted by chris.willing View Post
A problem with this approach is that skype cannot then be started from the Applications->Internet (xfce) menu as an ordinary user; the script's command 'sudo -b /lib/elogind/elogind &' needs a command line to enter the user's password.

Maybe someone who knows how could write a .policy file so that the script could launch elogind using pkexec, which would pop up a dialog box to ask for a password. Ideally it should work with the user's password (like sudo) rather than root password. Any takers?

chris

Edit: I just tried it with gksudo (from SBo's gksu package) rather than plain sudo and that seems to work OK. It's one more thing to have to install though, so if we could make pkexec work like sudo it would still be preferable.
I don't use skype so I'm not going to try, but it should also work with kdesu, in which case there's nothing additional to install (assuming a full Slackware installation).
 
Old 09-24-2018, 11:29 PM   #68
denydias
Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 113

Rep: Reputation: Disabled
I see you guys are advanced with elogind thing. I'm facing the same problem as the OP: no skype version works on -current anymore. I've been using skype rpm (after rpm2tgz) for years, but this is not an option anymore. Official snap never worked on Slackware, so it's not an option too.

I then ditched skype client out of my box and have been using skype web ever since. It works pretty nice even for audio and video calls. It has the drawback to keep a browser window open to interact with my skype contacts, but this proven to be a nice thing at the end as I can be online there only when I need to.

Maybe this could be a workaround while skype client complain in Slackware-current.
 
2 members found this post helpful.
Old 09-24-2018, 11:53 PM   #69
Gordie
Member
 
Registered: Aug 2007
Posts: 428

Rep: Reputation: 148Reputation: 148
Searching for skype for linux 8.30.0.50 gives few returns

https://answers.microsoft.com/en-us/...6-7a98dd285ee5
 
Old 09-25-2018, 04:42 AM   #70
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,288

Rep: Reputation: 5435Reputation: 5435Reputation: 5435Reputation: 5435Reputation: 5435Reputation: 5435Reputation: 5435Reputation: 5435Reputation: 5435Reputation: 5435Reputation: 5435
I would suggest that all Slackware Skype users open a new topic with microsoft support online, to make this issue more visible with their engineers.
It would not be hard for them to do as KDE and others have done before: accept ConsoleKit2's implementation of the dbus logind API and add support for it. This would take only a couple of lines of code.
See for instance how KWin does it: https://github.com/KDE/kwin/blob/9ad...logind.cpp#L66
 
5 members found this post helpful.
Old 09-25-2018, 07:08 AM   #71
Qury
Member
 
Registered: Feb 2004
Location: Dublin
Distribution: Slackware
Posts: 141

Rep: Reputation: 127Reputation: 127
Quote:
Originally Posted by Alien Bob View Post
I would suggest that all Slackware Skype users open a new topic with microsoft support online, to make this issue more visible with their engineers.
Good idea!

Here is the topic:
https://answers.microsoft.com/en-us/...=1537872777097

Hope you don't mind that i took most of what you mentioned.
 
4 members found this post helpful.
Old 09-25-2018, 08:37 AM   #72
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 867

Rep: Reputation: 319Reputation: 319Reputation: 319Reputation: 319
Quote:
Originally Posted by chrisVV View Post
If you wanted to solve the warning, one answer is specify in /etc/passwd and /etc/group that ID 99 is for oldnobody and 65534 for nobody: that would prevent any files being unreachable. But the best thing is to ignore it. It almost certainly makes no difference in relation to skype or anything else you are going to meet in practice.
Thanks for the information, that was interesting reading. Always learning things. As you have suggested I'm choosing to ignore it. I thought about "fixing" it when I first encounter the warning but, decided not to mostly as that link pointed out possible problems. I figure if it needed "fixing" our BDFL would be the one to do that.

I actually got two warnings, adding '-Dnobody-group=nogroup' to the build fix this error.
Code:
Message: WARNING:
        The local group with the configured group name "nobody" of the nobody group does not have UID 65534 (it has 99).
        Your build will result in an group table setup that is incompatible with the local system.
The output of meson setup gives these two messages. Just before the warning messages.
Code:
Message: maximum system UID is 999
Message: maximum system GID is 999
 
Old 09-25-2018, 10:01 AM   #73
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 867

Rep: Reputation: 319Reputation: 319Reputation: 319Reputation: 319
Quote:
Originally Posted by chris.willing View Post
A problem with this approach is that skype cannot then be started from the Applications->Internet (xfce) menu as an ordinary user; the script's command 'sudo -b /lib/elogind/elogind &' needs a command line to enter the user's password.
I can start skype via the (plasma) menu as a normal user.

I added an entry to sudoers to allow chris to run '/lib/elogind/elogind &' and 'killall elogind' with no password.
Code:
chris ALL= NOPASSWD: /lib/elogind/elogind, /bin/killall elogind
I could easily modify sudoer for other users.

Last edited by chrisretusn; 09-25-2018 at 10:52 AM.
 
Old 09-25-2018, 10:30 AM   #74
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 867

Rep: Reputation: 319Reputation: 319Reputation: 319Reputation: 319
Quote:
Originally Posted by montagdude View Post
I don't use skype so I'm not going to try, but it should also work with kdesu, in which case there's nothing additional to install (assuming a full Slackware installation).
A full install is a good assumption with me, with Ktown installed. <grin>

It does work with kdesu. There are issues. It's not seamless. A few seconds after the kdesu dialog appears, the skype window starts and covers up the password prompt dialog. Skype starts without elogind. It is eventually started after the password is entered and skype does not complain. Just annoying to have to click in the kdesu dialog to get it on tip again.

Then there is the killall after skype is closed, really don't like the idea of prompting for root password again.

I did try using 'wait' in the wrapper script thinking kdesu would die after passing the command to start elogind, but kdesu does not die, wait isn't going to work. I could use 'sleep' to delay long enough to enter the password but I'm fine with my solution. No prompts, elogind starts before skype and is kill after skype is exited. I just noticed skype is reported a new version... maybe we will get lucky.

Edit: Nope on the lucky. 8.31.76.93 still needs elogind.

Last edited by chrisretusn; 09-25-2018 at 10:46 AM.
 
Old 09-25-2018, 10:58 AM   #75
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Original Poster
Rep: Reputation: 1230Reputation: 1230Reputation: 1230Reputation: 1230Reputation: 1230Reputation: 1230Reputation: 1230Reputation: 1230Reputation: 1230
I use elogind as a traditional package, build after the SlackBuild I attached in a previous post. It works, and the Skype works like a charm too.

However, I noticed that elogind hijacked the computer power button, and now it execute right on the shutdown. Well, an eventual behavior like this was expected.

To note that by Plasma5 it was configured on Power Management to execute "Suspend"

The funny part is that a friend of mine, using slackware-curent and Plasma5 on a laptop, and who previously lamented of having issues with the LID (closing the display on laptop) which supposedly should go "Suspend", now using my elogind build to save his Skype, resulted also on his LID working fine now.

So, apparently elogind do its job better than ConsoleKit2. In fact, that's expected, because looks like everyone uses logind, either natively (from systemd) or as a cut away elogind. Then it is much better tested than that stray ConsoleKit, who nobody uses excluding us.

So, I will ask our friend Eric, IF is trivial to switch between ConsoleKit2 and elogind - and apparently the sole major distribution using today ConsoleKit2 instead of systemd or elogind is Slackware,

WHY we use ConsoleKit2 instead of elogind? And WHY we do NOT switched already to elogind too, as any other "systemd-free" distribution?

Heck, even the Devuan which forked Debian because systemd-hate politics uses elogind.

Last edited by Darth Vader; 09-25-2018 at 11:17 AM.
 
  


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 05:13 AM.

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