Crash by dragging to another screen with different scaling factor
This might be somehow connected to: GNOME/mutter#3296
If I drag the Obfuscate window to the secound screen, that is with a different scale and rotated by 90°, the application crashes. The crash also happens if the window was created on that secound screen that is rotated
This is the flatpak
RUST_BACKTRACE=full flatpak run com.belmoussaoui.Obfuscate
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/widgets/drawing_area.rs:567:38
stack backtrace:
0: 0x5c1fd9c1a6ba - <unknown>
1: 0x5c1fd9c3912e - <unknown>
2: 0x5c1fd9c18515 - <unknown>
3: 0x5c1fd9c1a485 - <unknown>
4: 0x5c1fd9c1badf - <unknown>
5: 0x5c1fd9c1b81b - <unknown>
6: 0x5c1fd9c1c088 - <unknown>
7: 0x5c1fd9c1bf42 - <unknown>
8: 0x5c1fd9c1ab26 - <unknown>
9: 0x5c1fd9c1bc92 - <unknown>
10: 0x5c1fd9b37a53 - <unknown>
11: 0x5c1fd9b37aed - <unknown>
12: 0x5c1fd9b43ada - <unknown>
13: 0x5c1fd9b527f2 - <unknown>
14: 0x5c1fd9b3eab0 - <unknown>
15: 0x70536c694f1e - <unknown>
16: 0x70536c697ef8 - g_object_setv
17: 0x70536c698ff1 - g_object_set_property
18: 0x5c1fd9b4202a - <unknown>
19: 0x5c1fd9b440d2 - <unknown>
20: 0x5c1fd9b50b3a - <unknown>
21: 0x5c1fd9b3f6af - <unknown>
22: 0x5c1fd9b6bfc6 - <unknown>
23: 0x70536c68f442 - g_closure_invoke
24: 0x70536c6a35c8 - <unknown>
25: 0x70536c6aa575 - g_signal_emit_valist
26: 0x70536c6aa743 - g_signal_emit
27: 0x70536c693a54 - <unknown>
28: 0x70536c696bf8 - g_object_notify_by_pspec
29: 0x70536c09e92b - <unknown>
30: 0x70536c09e985 - <unknown>
31: 0x70536c09e985 - <unknown>
32: 0x70536c09e985 - <unknown>
33: 0x70536c09e985 - <unknown>
34: 0x70536c09e985 - <unknown>
35: 0x70536c09e985 - <unknown>
36: 0x70536c68f442 - g_closure_invoke
37: 0x70536c6a35c8 - <unknown>
38: 0x70536c6aa575 - g_signal_emit_valist
39: 0x70536c6aa743 - g_signal_emit
40: 0x70536c693a54 - <unknown>
41: 0x70536c696942 - g_object_notify
42: 0x70536c27ca9b - <unknown>
43: 0x70536c27d402 - <unknown>
44: 0x70536af59056 - <unknown>
45: 0x70536af57acd - <unknown>
46: 0x70536af582a3 - ffi_call
47: 0x70536b221eee - <unknown>
48: 0x70536b2226d3 - <unknown>
49: 0x70536b2228bc - wl_display_dispatch_queue_pending
50: 0x70536c273a20 - <unknown>
51: 0x70536c238e77 - <unknown>
52: 0x70536c273666 - <unknown>
53: 0x70536bbece89 - g_main_context_dispatch
54: 0x70536bbed3e8 - <unknown>
55: 0x70536bbed483 - g_main_context_iteration
56: 0x70536c9ce36d - g_application_run
57: 0x5c1fd9b4ec1b - <unknown>
58: 0x5c1fd9b577be - <unknown>
59: 0x5c1fd9b490f3 - <unknown>
60: 0x5c1fd9b45209 - <unknown>
61: 0x5c1fd9c14a1c - <unknown>
62: 0x5c1fd9b57965 - <unknown>
63: 0x70536b82958a - <unknown>
64: 0x70536b82964b - __libc_start_main
65: 0x5c1fd9b38045 - <unknown>
66: 0x0 - <unknown>
Is all I get (but I dont know how to have better backtraces for flatpak. Since I can recreate it all the time it shouldnt be a problem to include them once I figured that out.
Here is a recording of the crash: