I reported this bug from a system without an SSD. Recently, I have not
seen the kernel messages appear however--currently on linux 4.2.5.
On Sun, Nov 1, 2015 at 10:04 PM, <email address hidden> wrote:
> *Comment # 235 <https://bugs.freedesktop.org/show_bug.cgi?id=54226#c235>
> on bug 54226 <https://bugs.freedesktop.org/show_bug.cgi?id=54226> from
> <email address hidden> <email address hidden> *
>
> FWIW, my issue (https://bugs.freedesktop.org/show_bug.cgi?id=54226#c191), was
> resolved by uninstalling various components, re-installing and updating them. I
> have a hunch (completely unproven) that it was a transparent bit-fail issue
> from the SSD. By un-installing and re-installing, the files were likely
> installed to a different location on the drive. It wasn't configuration, as I
> tried erasing, and even rolling back to defaults, with the problem still
> persisting. As it was almost daily, prior to uninstall, and hasn't happened
> since the install, this is all I can attribute it to.
>
> HTH someone.
>
> ------------------------------
> You are receiving this mail because:
>
> - You are on the CC list for the bug.
>
>
Created attachment 119432 28908-0. html
attachment-
I reported this bug from a system without an SSD. Recently, I have not
seen the kernel messages appear however--currently on linux 4.2.5.
On Sun, Nov 1, 2015 at 10:04 PM, <email address hidden> wrote:
> *Comment # 235 <https:/ /bugs.freedeskt op.org/ show_bug. cgi?id= 54226#c235> /bugs.freedeskt op.org/ show_bug. cgi?id= 54226> from /bugs.freedeskt op.org/ show_bug. cgi?id= 54226#c191), was ------- ------- ------- --
> on bug 54226 <https:/
> <email address hidden> <email address hidden> *
>
> FWIW, my issue (https:/
> resolved by uninstalling various components, re-installing and updating them. I
> have a hunch (completely unproven) that it was a transparent bit-fail issue
> from the SSD. By un-installing and re-installing, the files were likely
> installed to a different location on the drive. It wasn't configuration, as I
> tried erasing, and even rolling back to defaults, with the problem still
> persisting. As it was almost daily, prior to uninstall, and hasn't happened
> since the install, this is all I can attribute it to.
>
> HTH someone.
>
> -------
> You are receiving this mail because:
>
> - You are on the CC list for the bug.
>
>