Comment 80 for bug 213494

This bug is not a new one, and seems to be stalled as far as a fix, if it is a sufficient workaround (are there any cases where this doesn't workaround the problem?) It seems that usability would be key, and that workaround fixes it on several of my machines, I know that is slightly limited, but seems like a very viable workaround. It doesn't seem that collecting any further data is going to result in a solution that will come around any time soon, because as stated, this isn't new. Perhaps I missed the previous reasons, I did breeze through them, and mostly it is talk of using something different (parcelite klipper, etc.) those aren't even workarounds, they are abandonment. I believe that actually the times it didn't work are not related to the glipper startup crashing bug, but rather a memory limitation type bug. I too have crashed glipper in this way, however playing around with the settings has stopped that problem. I'm not a programmer, so it is only my observations and opinions take it for what it is worth. I think end userability ranks higher than attempting to milk a dry cow for more information. The majority of users (of which I venture to guess don't even visit this page) just delete it and install parcelite or klipper without a second thought. Don't take this as a reproach, it is just my opinion from one of the end users.

Shane