Those path effects again. I think you are right. In every group I had a problem with, there were no doubt some objects with path effects. And groups without them, I don't think I ever had problems with. The latter ones are relatively few, which is why I haven't considered it much. (I really _like_ the "shaped paths" that you can draw with pen or bezier tool.)
If I come across anything to contradict it, I will tell you, but for now, I think we can indeed assume path effects to be a factor in this.
Note though that I have many groups with path effects that (for some reason) I can ungroup without problems. Also, in my experience (on Ubuntu), this seems completely non-random. Either a group has a problem or it hasn't. And if it has (like the one in my test file), I can NEVER ungroup it with v0.92. (I have tried that one many, many times now.)
I don't know whether there is something specific about the Linux build, or the Ubuntu build 0.92.0+66 (received via the inkscape.dev/stable ppa) causing this, or there are indeed some preferences I could set to avoid this issue. The latter case would be nice to find out about, even if just as a workaround until 0.92 works as reliably as 0.91 did for me.
Those path effects again. I think you are right. In every group I had a problem with, there were no doubt some objects with path effects. And groups without them, I don't think I ever had problems with. The latter ones are relatively few, which is why I haven't considered it much. (I really _like_ the "shaped paths" that you can draw with pen or bezier tool.)
If I come across anything to contradict it, I will tell you, but for now, I think we can indeed assume path effects to be a factor in this.
Note though that I have many groups with path effects that (for some reason) I can ungroup without problems. Also, in my experience (on Ubuntu), this seems completely non-random. Either a group has a problem or it hasn't. And if it has (like the one in my test file), I can NEVER ungroup it with v0.92. (I have tried that one many, many times now.)
I don't know whether there is something specific about the Linux build, or the Ubuntu build 0.92.0+66 (received via the inkscape.dev/stable ppa) causing this, or there are indeed some preferences I could set to avoid this issue. The latter case would be nice to find out about, even if just as a workaround until 0.92 works as reliably as 0.91 did for me.