On Wed, Jan 17, 2018 at 14:03:02 -0800,
Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote:
On Wed, 2018-01-17 at 15:53 -0600, Bruno Wolff III wrote:
On Fri, Jan 12, 2018 at 14:25:36 -0600,
Bruno Wolff III <bruno@xxxxxxxx> wrote:
>
> I was able to recreate the problem while upgrading and am in the
> middle of doing a sort of bisect to get identify the problem package.
> Once I do, I'll file a real bug report.
I isolated this to m17n-db and filed bug 1535672.
https://bugzilla.redhat.com/show_bug.cgi?id=1535672
Nice debugging work, Bruno!
It hasn't been enough for other people to reproduce yet. I still don't know
why it affects only one of the two machines I use with desktops. They are
both x86_64. I may need to play with this on an older laptop that is currently
using i686, but that I have been meaning to move to x86_64. I can at least
get it up to date and do a quick check to see if it is affected using i686.
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
