Closed hackel closed 5 years ago
It seems to be several issues for you
1. A dbus connection error 2. Failure to get workspace layout (get_cardinal failed) *3. Segfault at exit
Number 3 is actually a known issue that I simply have been ignoring. When I was investigating it I did not get further than to the gtkmm lib and I suspect that this is inside it and therefore outside of scope for me.
Number 1 seems to be a failure to to connect through dbus. As timeit itself is not using dbus it must be one of the libraries that is getting data through it.
I have made a fresh install of Ubuntu 17.04 in a virtual box and compiled the latest version of timeit in it. When running it I do not get the number 3 fault but not the two other.
Question: Do you run something else than Xorg, like wayland or mir?
No, I'm still running Xorg, with GNOME shell. dbus is definitely working in general. I'm just not sure where it's getting that /tmp socket from (which doesn't exist). It should be using:
DBUS_SESSION_BUS_ADDRESS='unix:path=/run/user/1000/bus'
But since TimeIT isn't using dbus, I guess there's nothing you can/should do about it.
The 3rd issue isn't particularly important, I just mentioned it in case it was relevant.
When I have time I'll try to play around a bit in a VM and see if I can replicate it. Thanks for looking into this!
gnome-shell does not set some "Extended Window Manager Hints", in this case DESKTOP_LAYOUT. TimeIT tries to read it with failure as a result.
When I launch timeit, the above message prints to the console every second indefinitely until I exit.
Backtrace:
Then when I exit, it segfaults:
Backtrace:
It seems to be otherwise working normally. Idle time fires, etc. I've just upgraded to Ubuntu 17.04 (without recompiling), so perhaps it's related to that. I'm going to recompile the latest source and see what happens.
Edit: Exactly the same behaviour/backtrace after recompiling.