On 07/22/2019 10:52 AM, Lucas dos Santos wrote: > I did some more tests and finally found the culprit: it was libice package! > > Instead upgrading the system at once, I upgraded package after > package, one after one, until I find out which one was causing the > problem. When I upgraded libice-1.0.9-2 to libice-1.0.10-1 I couldn't > start Trinity. Once I downgraded it back to 1.0.9-2 Trinity worked > normally again. > > For now I will keep the old version of libice in my system. Damn good work. Thank you for the effort. This has apparently hit suse/KDE3 as well on Tumbleweed. We'll spread your results and see if we can't get it solve. You should write a bug on trinity bugzilla so it can be tracked and worked. Thanks again. -- David C. Rankin, J.D.,P.E. --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
