matplotlib-devel

[matplotlib-devel] BUG: Qt4Agg backend save figure io-slave error

[Philippe M. <phi...@ce...>]

Dear all,

When I use the Qt4Agg backend and I want to save the figure by clicking the 
save button, I get this Error message:

kfilemodule(5951): couldn't create slave: "Unable to create io-slave:
klauncher said: Protocole «  » inconnu.

It is like an empty string is given for the protocole name.

infos:
Distribution: Archlinux
Python 2.7.3
matplotlib 1.1.1
Kde 4.8.4
Linux  3.4.5-1-ARCH x86_64

Best regards,

Re: [matplotlib-devel] BUG: Qt4Agg backend save figure io-slave error

[Benjamin R. <ben...@ou...>]

On Thu, Jul 19, 2012 at 4:39 AM, Philippe MALLET
<phi...@ce...>wrote:

> Dear all,
>
> When I use the Qt4Agg backend and I want to save the figure by clicking the
> save button, I get this Error message:
>
> kfilemodule(5951): couldn't create slave: "Unable to create io-slave:
> klauncher said: Protocole «  » inconnu.
>
> It is like an empty string is given for the protocole name.
>
> infos:
> Distribution: Archlinux
> Python 2.7.3
> matplotlib 1.1.1
> Kde 4.8.4
> Linux  3.4.5-1-ARCH x86_64
>
> Best regards,
>
>
Philippe,

Was there a more complete traceback displayed?

Ben Root

Re: [matplotlib-devel] BUG: Qt4Agg backend save figure io-slave error

[Darren D. <dsd...@gm...>]

On Thu, Jul 19, 2012 at 5:39 AM, Philippe MALLET
<phi...@ce...> wrote:
> Dear all,
>
> When I use the Qt4Agg backend and I want to save the figure by clicking the
> save button, I get this Error message:
>
> kfilemodule(5951): couldn't create slave: "Unable to create io-slave:
> klauncher said: Protocole «  » inconnu.
>
> It is like an empty string is given for the protocole name.
>
> infos:
> Distribution: Archlinux
> Python 2.7.3
> matplotlib 1.1.1
> Kde 4.8.4
> Linux  3.4.5-1-ARCH x86_64

I don't think this is a matplotlib bug. It is probably a KDE
configuration problem specific to your system. See
http://forums.gentoo.org/viewtopic-t-601154.html.

You could try editing your backend_qt4.py, in the save_figure method,
to add QFileDialog.DontUseNativeDialog to the end of the list of
arguments passed to _getSaveFileName. But that is only a workaround.

Darren