On Sat, 07 Apr 2018 23:34:26 + Wido said:
> Hi Ross, I don't think sid has the debug symbols from E22.3, which is the
> verion I have.
>
> Raster, the problem was indeed in the driver version. When I rolled back to
> 386.111 and enabled opengl evas engine, the error logs disapeared ¯\_(ツ)_/¯
Hi Ross, I don't think sid has the debug symbols from E22.3, which is the
verion I have.
Raster, the problem was indeed in the driver version. When I rolled back to
386.111 and enabled opengl evas engine, the error logs disapeared ¯\_(ツ)_/¯
El sáb., 7 de abr. de 2018 a la(s) 15:15, Ross Vandegrif
On Sat, Apr 07, 2018 at 04:27:58PM +, Wido wrote:
> Unfortunately, sparky doesn't provides debug symbols, and I'm over
> compiling.
Since you're running buster, you can install the packages from sid. Debug
symbols are also packaged, see instructions at:
https://wiki.debian.org/HowToGetABacktr
What could I do to better show you the issue?
Unfortunately, sparky doesn't provides debug symbols, and I'm over
compiling.
Here's the complete output of the .xsession-error. These 4 messages keeps
showing permanently. I did one of the suggested backtraces, since all 4 are
the same, but I know th
On Sat, 07 Apr 2018 04:33:52 + Wido said:
> Hi,
>
> I'm currently using E 22.3 with Debian test (buster). I'm geting E from the
> Sparky repos. Also, I have an Nvidia 1050 with propietary blobs (from
> debian non-free)
>
> Recently, E started misbehaving, high cpu and suddenly my home parti
