|
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. |
Nope, the /home directory is not full (and I checked the existing file systems) it's about 26% used.
upower --dump produces interesting error messages: Code:
upower --dumpThe list you provided Code:
polkit appears to be there (it's a long list of stuff)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. |
Maybe upowerd is not started. Can you try running: /usr/libexec/upowerd
You have stated that you did a full install, but can you still please check ldd on these binaries? |
FWIW, upower should return something like this:
Code:
# upower --dump |
Quote:
Code:
ldd /usr/lib/polkit-1/* | pgAnd the daemon: Code:
pita-root-/root: /usr/libexec/upowerd |
Bah, a spidery mess. Ok, can you check if polkitd is running now? If it is not, can you run it?
/usr/lib64/polkit-1/polkitd If it's not that, and it is running ok, then the only thing left I see on my XFCE is /usr/libexec/polkit-gnome-authentication-agent-1 Check that out too, but make sure polkitd is running first. |
Gosh, this is getting to be fun.
Code:
/usr/lib/polkit-1/polkitdI'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*This is getting just a little weird. |
Quote:
|
Quote:
Code:
$ grep polkitd /etc/passwd |
Quote:
Plus, the next post may just have the answer. Thanks for the thought. |
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... |
Quote:
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, Thank you |
You shouldn't think you're the only one who has done that to themselves. :D
|
| All times are GMT -5. The time now is 06:38 PM. |