Hi All
Trinity 3.5.13.2 on Debian Wheezy oftentimes crash when I attempt to logout with some apps open, krusader or others. ksmserver seems crashed, I have searched mailing lists, but no similar topic have found, please confirm the glitch.
Do someone have some solution ?
Dolly Pete
I had another problem: logging out freezes on "Saving your settings" dialog. I disabled "Fancy fadeout" (or sth like that) and "Show progress when logging out" (or, again, something like that - writting from memory) in KControlCenter and the problem disappeared. Try it, maybe it will help
Janek
Dnia czwartek, 6 lutego 2014, dollyclone@hushmail.com napisał:
Hi All
Trinity 3.5.13.2 on Debian Wheezy oftentimes crash when I attempt to logout with some apps open, krusader or others. ksmserver seems crashed, I have searched mailing lists, but no similar topic have found, please confirm the glitch.
Do someone have some solution ?
Dolly Pete
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net 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
I have installed trinity on both my machine and another. Both are debian wheezy running kde4, with now trinity added to that.
On my machine it works like a charm. (Many thanks for all the hard work!) On the other though, when one clicks on the start menu icon and moves the mouse over the menu, it crashes when it reaches the "System" menu entry. After that, the menu and the entire taskbar vanish, and the only practical option is to end the session. All other menu items work fine.
I am wondering if there is some odd interaction with kde4 going on (but then it doesn't happen on my machine). BTW, in KDE4, the menu still works fine.
Looking for any suggestions. Should I rebuild the menus inside trinity? If so, how to do that? I don't want to mess with kde4 by mistake, as it is the only WM currently working, since this bug is a show-stopper.
All ideas gratefully received.