SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Slackware64 14.2 Xfce Exit Slooowwww
Using Slackware64 14.2 Xfce.
Going to the Applications Menu and selecting Log Out, it takes roughly three minutes for the pop-up menu to show; also, once selected the window manager seems to stop responding, for example GKrellM freezes after a few seconds when Log Out is selected from the Applications Menu.
I can't see anything that would cause this -- can anybody else?
Maybe the home filesystem is full and saving the session state takes longer than normal? Or the disk holding the home filesystem is dying, which you might not notice until you save something like the session state in it.
Are you using kdm to log in? ~/.xsession-errors may tell you something in that case.
Yes, I know a few things on what causes this. The logout issues are caused by the *kits and they do not provide any helpful messages when they fail. But I figured out the obscure ways they run.
Make sure upower is running by running "upower --dump". If it returns "unable to query", it's likely upower can't run due to a runtime loaded dependency
Make sure polkit's binaries has its libraries satisfied "ldd /usr/lib/polkit-1/*"
Generally you'll need js185, libimobiledevice, and usbmuxd, I think.
upower --dump
(upower:2225): libupower-glib-WARNING **: Couldn't enumerate devices: Message recipient disconnected from message bus without replying
(upower:2225): UPower-WARNING **: failed to enumerate: Message recipient disconnected from message bus without replying
Power management is on.
The list you provided
Code:
polkit appears to be there (it's a long list of stuff)
js185 appears to be there
locate js185
/var/log/scripts/js185-1.0.0-x86_64-1
/var/log/packages/js185-1.0.0-x86_64-1
/usr/doc/js185-1.0.0
/usr/doc/js185-1.0.0/README
/usr/doc/js185-1.0.0/README.html
/usr/lib64/libmozjs185.so.1.0.0
/usr/lib64/libmozjs185.so
/usr/lib64/libmozjs185.so.1.0
/usr/lib64/pkgconfig/mozjs185.pc
locate libimobiledevice produces a long list of stuff
locate usbmuxd produces a long list of stuff
And, I have no clue what to do about the upower messages.
This is a full install of Slackware 64 14.2 (the root partition is formatted when I install Slackware, other partitions are not formatted, simply added to /etc/fstab).
Tiz a puzzlement.
Oops, forgot, I'm logged in as root so there is no problems with the /home (or any other) directory. The freezing up problem exists with logging out root and with logging out users.
# upower --dump
Daemon:
daemon-version: 0.9.23
can-suspend: yes
can-hibernate: yes
on-battery: no
on-low-battery: no
lid-is-closed: no
lid-is-present: no
is-docked: no
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
Gosh, this is getting to be fun.
Code:
/usr/lib/polkit-1/polkitd
Error switcing to user polkitd: Error calling getpwnam(): Success
Exiting with code 1
So, no it's not running. Also, it's not in /usr/lib64, it's in /usr/lib (at least on the laptop as well as on a stable 14.1 desktop).
I'm wondering about the error message "switching the user polkitd." Is there supposed to be a user polkitd somewhere or other? I mean, why the heck would it be calling getpwnam in the first place?
I'm also wondering about
Code:
pita-root-/var/log/packages: ls *polkit*
polkit-0.113-x86_64-2
polkit-gnome-0.105-x86_64-1
polkit-kde-agent-1-9d74ae3_20120104git-x86_64-2
polkit-kde-kcmodules-1-001bdf7_20120111git-x86_64-2
polkit-qt-1-0.103.0-x86_64-1
And if one of those is screwed up or missing some dependency.
/usr/lib/polkit-1/polkitd
Error switcing to user polkitd: Error calling getpwnam(): Success
Exiting with code 1
So, no it's not running. Also, it's not in /usr/lib64, it's in /usr/lib (at least on the laptop as well as on a stable 14.1 desktop).
I'm wondering about the error message "switching the user polkitd." Is there supposed to be a user polkitd somewhere or other? I mean, why the heck would it be calling getpwnam in the first place?
I'm also wondering about
Code:
pita-root-/var/log/packages: ls *polkit*
polkit-0.113-x86_64-2
polkit-gnome-0.105-x86_64-1
polkit-kde-agent-1-9d74ae3_20120104git-x86_64-2
polkit-kde-kcmodules-1-001bdf7_20120111git-x86_64-2
polkit-qt-1-0.103.0-x86_64-1
And if one of those is screwed up or missing some dependency.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
Quote:
Originally Posted by gezley
Perhaps this is not a *kit issue at all, but rather DNS- or NFS-related. Or something to do with your iptables rules.
Probably not -- DNS is not running, nor is NFS or iptables. I use fixed-IP for all systems with /etc/resolv.conf and /etc/hosts. I have HughsNet satellite service and use their DNS servers (that, I believe, are on the satellites). Only thing available around here and you can't get to my servers from the outside world -- Hughes doesn't want anybody running a web page on their services and you just can't get from there to here.
I jumped the gun a little bit on the polkitd path since I saw you were on a 64-bit system. No big deal.
So I think the message above really just means we're launching it incorrectly, so we need to go at this a different angle. So I double checked how polkit is launched from XFCE, and its /usr/libexec/polkit-gnome-authentication-agent-1. Please try running that at the command line.
Also please check ~/.xsession-errors or the tty you launched startx from like mentioned earlier. We might need to check for messages on the xfce session or console kit...
Yup, that was the problem, no polkitd in /etc/passwd. Put the entry in /etc/passwd, /etc/group and /etc/shadow (yeah I know you're not supposed to do that but I triple-checked it).
And, I know why it was not there (because it wasn't there in Slackware 14.1).
And, it's my own damned fault.
Thank you all for your input and taking the time and trouble to do so, every bit certainly helped.
What I do when a new release comes is copy /etc to a general-purpose partition I have named, for no really good reason I can remember, /spares. This has worked through I don't know how many Slackware releases, so I boot the DVD, run setup and let the root partition get formatted but do not format any of the others, including /opt, /usr/local, /spares, /var/lib/virtual, /var/lib/mysql, /var/lib/postpgl and a couple others.
That way, hundreds of gigabytes of files, add-on software, and whatever else does not get blown away (and I don't have burn DVDs or copy to another server and all that). I just leave 'em in place and add the partitions to /etc/fstab. I can get away with that because all my systems are mapped the same even though there is different stuff on different systems -- two data base servers, on MariaDB/MySQL and the other PostgreSQL.
The Slackware distribution installs everything in the root partition; used to be some things got put in /opt but not any more. The whole thing in one partition and it's about 8.1 G.
So, back to the copy of /etc in /spares (here's where I burnt my own fingers): I simply copy /etc/passwd, /etc/group and /etc/shadow from /spares/etc in /etc.
That has worked wonderfully for years and I've gotten lazy and don't check to see if there are any changes in /etc/passwd. From 14.1 to 14.2 polkitd was added and that was exactly why the problems I created happened.
I'm pretty sure that there is somewhere in the documentation a note about polkikd in the passwd file. Did I read any of the doc? Why, no, I did not because I've always done it this way and it's always worked just fine (it takes about 20 minutes from boot to functional system the way I've been doing it for, like, years).
From now on it's going to be diff passwd, group and shadow before just blindly copying and, oh, yeah, RTFM stupid,
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
