Le lundi 05 mars 2018 à 19:49:52+0100, Pierre-Elliott Bécue a écrit :
> Le lundi 05 mars 2018 à 19:08:04+0100, ydir...@free.fr a écrit :
> > Hello,
> >
> > That does not fix the init issue, likely 2 different problems:
> >
> > $ gaminggearfxinfo
> >
> > ** (process:21432): WARNING **: Could not
Le lundi 05 mars 2018 à 19:08:04+0100, ydir...@free.fr a écrit :
> Hello,
>
> That does not fix the init issue, likely 2 different problems:
>
> $ gaminggearfxinfo
>
> ** (process:21432): WARNING **: Could not initialize fx system
> $ echo $?
> 1
Actually, they're not.
I guess upstream splitt
Hello,
That does not fix the init issue, likely 2 different problems:
$ gaminggearfxinfo
** (process:21432): WARNING **: Could not initialize fx system
$ echo $?
1
- Mail original -
> De: "Pierre-Elliott Bécue"
> À: 891...@bugs.debian.org, ydir...@free.fr
> Envoyé: Lundi 5 Mars 2018
Hi,
Sorry for the delay in my answer, but package "gaminggearfxinfo" doesn't
exist so I never received your bug report.
Please, be cautious when you make a report to provide the appropriate
package name. :)
Anyway, thanks for your bug report.
Can you try to create the missing directory as root
Package: gaminggearfxinfo
Version: 0.15.1-7
Can't tell if the missing plugin dir is *the* problem.
Seems also strange that "Could not initialize fx system" is only reported as a
warning and not as a fatal error.
$ gaminggearfxinfo
** (process:4089): WARNING **: Error opening directory
'/usr/l
5 matches
Mail list logo
