You are not logged in.
Klipper and Kmix do not launch at startup, despite being in /usr/share/autostart. I had to add them to my own autostart config. I assume Kmix fails to start because of audio issues, but Klipper? I have no idea.
Pulseaudio has some extremely odd bugs. Whenever I plug in an external hard drive or launch GParted, KDE asks to forget about pulseaudio because it stopped running. If I try to relaunch it ever again until my computer reboots, I get this output:
$ $ pulseaudio --start
E: [autospawn] core-util.c: Failed to create secure directory (/run/user/1000/pulse): Permission denied
W: [autospawn] lock-autospawn.c: Cannot access autospawn lock.
E: [pulseaudio] main.c: Failed to acquire autospawn lockPulseaudio manages to run if I launch it with sudo, but then none of my applications recognize it:
$ sudo pulseaudio --start
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
No protocol specified
E: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned trueWhen my system is under heavy load from something like a file transfer or a virtual machine, pulseaudio pauses itself for entire minutes at a time--usually around 10--leaving my music just hanging there, not playing. Its nice value doesn't change this behavior whatsoever, though I should note that it is not launching in realtime as it's supposed to (last I remember).
Finally, the sound server just otherwise feels finnicky. Everytime I run pulseaudio -k, I'm honestly afraid I won't be able to start it again without a reboot. I can't say whether it actually is crash-happy or failed-start-happy when it's not being affected by the previously mentioned bugs.
Offline
The first error indicates what the problem is, what's the permissions on that directory? You should never run pulseaudio as root, anyway.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
Klipper and Kmix do not launch at startup, despite being in /usr/share/autostart. I had to add them to my own autostart config. I assume Kmix fails to start because of audio issues, but Klipper? I have no idea.
Did you install and activate appmenu-qt? If so, then take a look at this one: https://bugs.kde.org/show_bug.cgi?id=317926
Offline
Welp, I found the source of all my problems (including a bug I didn't mention where I mounted an NTFS drive through KDE and didn't have write permissions). I've noticed the /run directory that I've never seen in another distro before, and I've noticed that there are folders in places like /run/media and /run/user that are named after my username or id. I would assume those folders are supposed to be owned by me, because the fact that they weren't was wreaking havoc on both pulseaudio and my mounted drives. I've chowned all the /run dirs that are named after me, and I think that's fixed most of these issues.
Is that not what I'm supposed to do in Arch, though? Since the Arch installer and pacman configured my system this way and the wiki guides never mentioned /run, it just seems like I did something wrong here. And now I'm worried about other problems resulting from this run directory. Frankly, putting a pulseaudio lock and my mounted drives in a strictly-root-owned directory seems like a dumb choice. Do I have to worry about other apps being broken?
EDIT: Yup, confirmed, fixing pulseaudio has fixed Kmix as well. Klipper, however, still won't auto-launch without that extra config. I dont have appmenu-qt installed (forgot to mention before).
Last edited by Cadeyrn (2013-06-27 07:40:59)
Offline