[Solved] chromium file save error - somehow kde related?

genterminl · Last edited by genterminl on Fri Aug 11, 2017 10:31 pm; edited 1 time in total

Some time within the past few days, when trying to save a file from chromium, I get a popup "Unable to create io-slave. Cannot talk to klauncher: Not connected to D-Bus server." and the file save dialog does not show any folders, although the list of places on the left is OK, and it WILL save the file successfully in whatever folder it happened to start in. I've re-emerged everything kio related I can think of, with no change. Googling led me to setting KDE_FORK_SLAVES=1 before launching chromium from command line, but none of those posts gave any explanation of why it works or why it should be necessary. (I don't get the error if running chromium with su.) I do not have the problem with Firefox, but google-chrome does show the same symptoms. There were a number of suggestions to delete stuff under ~/.cache, but that didn't help.

mostly stable amd64 system with select testing packages
chromium 60.0.3112.78
google chrome 60.0.3112.90
plasma-workspace ~5.10.4-r2
kdesdk-kioslaves ~17.04.3
dbus 1.10.18

I'd love to know whether something is misconfigured, either on my part, or something KDE related.

Thanks for any suggestions, or even requests to post more details about my system.

asturm · Developer Joined: 05 Apr 2007 Posts: 8936

This sounds rather like a session problem. And the first question one has to ask in that case is not answered by your list; do you use systemd or consolekit or elogind, and how do you start your session?

genterminl · Posted: Fri Aug 11, 2017 10:03 pm Post subject:

Ah, I knew I missed something important.

openrc 0.28
eudev 3.1.5
consolekit 1.1.2

last line in .xinitrc is "exec ck-launch-session startkde"

asturm · Developer Joined: 05 Apr 2007 Posts: 8936

genterminl · Posted: Fri Aug 11, 2017 10:18 pm Post subject:

OK - that has changed more recently than I started using this approach. I'm in the middle of too much to restart X now, but I'll post back confirming if it works later today.

Can you point out what changed that requires those additional item in the launch line? I guess the main change is the explicit dbus-launch - was it just launched implicitly in the past? This used to work fine until very recently.

genterminl · Posted: Fri Aug 11, 2017 10:30 pm Post subject:

Asturm, thanks. That indeed fixed the problem. I'll mark solved. Any suggested changes to the Subject to let others find it more easily?

asturm · Developer Joined: 05 Apr 2007 Posts: 8936

genterminl · Posted: Fri Aug 11, 2017 10:45 pm Post subject:

Most peculiar then, since I've been on Plasma 5 since some time last year. I did recently change video card, and I know I played with my .xinitrc at that time, so it's certainly possible I trashed it at that time, but I thought it was working since then.

I suppose I'll never know. At least it's all working now.

Thanks again for the help.