Closed EbonJaeger closed 1 year ago
If it helps, I tested TeamViewer on the Solus Gnome version (wayland) in virt-manager and could not reproduce similar behavior. As I prefer Budgie, I am using TV in Firefox, but this has reduced functionality. I will keep poking around, and if I come across a fix or workaround I will update this thread.
You won't find a fix on your own, and I'd be surprised if you found a workaround. The issue here (and the reason I posted tiredge) is almost certainly that Teamviewer isn't following the DBusMenu spec correctly, which causes the session to crash because my code rightfully expects all the data sent by applications to be laid out correctly. I can't tell from the stacktrace where exactly needs a check, but I'll poke around and see what I can find.
Description
After installing
teamviewer
, system crashed with error "Oh no, something has gone wrong" and then log out.Reported on the Solus forum here.
Budgie version
10.8
Operating System
Solus 4.4 Harmony
Steps to reproduce the issue
Actual result
TeamViewer starts before crashing to the Oops screen.
Expected result
No Oops screen.
Additional information
I was able to generate a core dump from this to get the following
gdb
trace:Seems to indicate that there was a problem creating a StatusNotifierItem for the tray. Unfortunately, causing the crash again when running
gdb
doesn't give anything more useful, either, at least in my VM.