gnome-maps issueshttps://gitlab.gnome.org/GNOME/gnome-maps/-/issues2022-08-24T20:31:31Zhttps://gitlab.gnome.org/GNOME/gnome-maps/-/issues/436Export image when maximized freezes app until window resize2022-08-24T20:31:31ZAnselm SchülerExport image when maximized freezes app until window resizeTo reproduce:
---
1. Open Maps
2. Maximize the app
3. Select “Export as Image” from the menu
4. Save the image
5. Attempt to zoom or pan using the mouse
Result:
---
Maps doesn’t respond to zooming or panning until the window is minimize...To reproduce:
---
1. Open Maps
2. Maximize the app
3. Select “Export as Image” from the menu
4. Save the image
5. Attempt to zoom or pan using the mouse
Result:
---
Maps doesn’t respond to zooming or panning until the window is minimized againhttps://gitlab.gnome.org/GNOME/gnome-maps/-/issues/423Process 14311 (org.gnome.Maps) crashed and dumped core.2022-08-24T20:32:00ZRon KaplanProcess 14311 (org.gnome.Maps) crashed and dumped core.gnome.Maps crashs on startup
[log_messages](/uploads/3a8e1e1e4298f040ceac5dc64b286ea6/log_messages)Error Log Comment This usually indicates a programming error in the crashing program and
should be reported to its vendor as a bug.gnome.Maps crashs on startup
[log_messages](/uploads/3a8e1e1e4298f040ceac5dc64b286ea6/log_messages)Error Log Comment This usually indicates a programming error in the crashing program and
should be reported to its vendor as a bug.https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/357Crash when touching the map2022-08-24T20:32:17ZMichal VasilekCrash when touching the mapWhen touching anywhere in the UI, gnome-maps crashes.
I am using gnome-maps 40, gjs 1.68 and GTK 4.1.1.
terminal output:
```
%: gnome-maps
Gdk-Message: 12:29:36.799: Unable to load fleur from the cursor theme
(org.gnome.Maps:10678): Gd...When touching anywhere in the UI, gnome-maps crashes.
I am using gnome-maps 40, gjs 1.68 and GTK 4.1.1.
terminal output:
```
%: gnome-maps
Gdk-Message: 12:29:36.799: Unable to load fleur from the cursor theme
(org.gnome.Maps:10678): Gdk-CRITICAL **: 12:31:53.990: gdk_window_get_root_coords: assertion 'GDK_IS_WINDOW (window)' failed
(org.gnome.Maps:10678): Gdk-CRITICAL **: 12:31:53.990: gdk_window_get_display: assertion 'GDK_IS_WINDOW (window)' failed
Segmentation fault (core dumped)
```
backtrace:
```
warning: Can't open file /memfd:wayland-cursor (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:gdk-wayland (deleted) during file-backed mapping note processing
warning: Can't open file /usr/lib/libpango-1.0.so.0.4800.0 during file-backed mapping note processing
warning: Can't open file /usr/lib/libpangoft2-1.0.so.0.4800.0 during file-backed mapping note processing
warning: Can't open file /usr/lib/libpangocairo-1.0.so.0.4800.0 during file-backed mapping note processing
warning: .dynamic section for "/usr/lib/libpangoft2-1.0.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libinput.so.10" is not at the expected address (wrong library or version mismatch?)
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/gjs /usr/share/gnome-maps/org.gnome.Maps --gapplication-service'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f9da5b70804 in _gdk_event_queue_append (display=display@entry=0x0, event=event@entry=0x55a7019a49f0) at gdkevents.c:137
137 gdkevents.c: No such file or directory.
[Current thread is 1 (Thread 0x7f9dae8a2fc0 (LWP 11643))]
#0 0x00007f9da5b70804 in _gdk_event_queue_append (display=display@entry=0x0, event=event@entry=0x55a7019a49f0) at gdkevents.c:137
#1 0x00007f9da5bd05e0 in _gdk_wayland_display_deliver_event (display=0x0, event=0x55a7019a49f0) at gdkeventsource.c:158
#2 0x00007f9da5bc76cd in emulate_touch_crossing (window=<optimized out>, device=<optimized out>, source=<optimized out>, touch=touch@entry=0x55a701b03fe0, type=type@entry=GDK_ENTER_NOTIFY, time_=time_@entry=7639086, mode=GDK_CROSSING_NORMAL, subwindow=0x0) at gdkdevice-wayland.c:691
#3 0x00007f9da5bc95de in touch_handle_master_pointer_crossing (time=7639086, touch=0x55a701b03fe0, seat=0x55a7000ea040) at gdkdevice-wayland.c:2486
#4 touch_handle_down (wl_touch=<optimized out>, y=94772, x=220456, id=<optimized out>, wl_surface=<optimized out>, time=7639086, serial=11773, data=0x55a7000ea040) at gdkdevice-wayland.c:2521
#5 touch_handle_down (data=0x55a7000ea040, wl_touch=<optimized out>, serial=11773, time=7639086, wl_surface=<optimized out>, id=<optimized out>, x=220456, y=94772) at gdkdevice-wayland.c:2493
#6 0x00007f9db08c4e6d in ffi_call_unix64 () at ../src/x86/unix64.S:101
#7 0x00007f9db08c42aa in ffi_call_int (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=<optimized out>) at ../src/x86/ffi64.c:669
#8 0x00007f9da537d8fe in wl_closure_invoke (closure=closure@entry=0x55a702980a90, target=<optimized out>, target@entry=0x55a7000fbfe0, opcode=opcode@entry=0, data=<optimized out>, flags=<optimized out>) at ../src/connection.c:1018
#9 0x00007f9da537dfcb in dispatch_event (display=display@entry=0x55a7000b79e0, queue=<optimized out>, queue=<optimized out>) at ../src/wayland-client.c:1452
#10 0x00007f9da537e19c in dispatch_queue (queue=0x55a7000b7ab0, display=0x55a7000b79e0) at ../src/wayland-client.c:1598
#11 wl_display_dispatch_queue_pending (display=0x55a7000b79e0, queue=0x55a7000b7ab0) at ../src/wayland-client.c:1840
#12 0x00007f9da537e1ec in wl_display_dispatch_pending (display=<optimized out>) at ../src/wayland-client.c:1903
#13 0x00007f9da5bd06d4 in _gdk_wayland_display_queue_events (display=<optimized out>) at gdkeventsource.c:201
#14 0x00007f9da5b6bc90 in gdk_display_get_event (display=display@entry=0x55a7000d0170) at gdkdisplay.c:442
#15 0x00007f9da5bd03d2 in gdk_event_source_dispatch (base=<optimized out>, callback=<optimized out>, data=<optimized out>) at gdkeventsource.c:120
#16 0x00007f9db0fc567b in g_main_dispatch (context=0x55a6ff803180) at ../glib/gmain.c:3337
#17 g_main_context_dispatch (context=0x55a6ff803180) at ../glib/gmain.c:4055
#18 0x00007f9db0fc5928 in g_main_context_iterate (context=context@entry=0x55a6ff803180, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4131
#19 0x00007f9db0fc59df in g_main_context_iteration (context=context@entry=0x55a6ff803180, may_block=may_block@entry=1) at ../glib/gmain.c:4196
#20 0x00007f9db0e182a5 in g_application_run (application=0x55a6ff8d50f0, argc=-617827932, argv=<optimized out>) at ../gio/gapplication.c:2560
#21 0x00007f9db08c4e6d in ffi_call_unix64 () at ../src/x86/unix64.S:101
#22 0x00007f9db08c42aa in ffi_call_int (cif=<optimized out>, fn=<optimized out>, rvalue=<optimized out>, avalue=<optimized out>, closure=<optimized out>) at ../src/x86/ffi64.c:669
#23 0x00007f9db10e60fb in Function::invoke (this=0x55a7000cd250, context=<optimized out>, args=..., this_obj=..., r_value=<optimized out>) at ../gi/function.cpp:965
#24 0x00007f9db10e66ff in Function::call (context=0x55a6ff82aa50, js_argc=<optimized out>, vp=<optimized out>) at /usr/include/mozjs-78/js/RootingAPI.h:596
#25 0x00007f9dafd7f145 in CallJSNative (args=..., reason=<optimized out>, native=0x7f9db10e6600 <Function::call(JSContext*, unsigned int, JS::Value*)>, cx=0x55a6ff82aa50) at ../../vm/Interpreter.cpp:493
#26 js::InternalCallOrConstruct (cx=0x55a6ff82aa50, args=..., construct=<optimized out>, reason=<optimized out>) at ../../vm/Interpreter.cpp:565
#27 0x00007f9dafd725d5 in Interpret (cx=0x55a6ff82aa50, state=...) at ../../vm/Interpreter.cpp:3312
#28 0x00007f9dafd7e8ee in js::RunScript (cx=0x55a6ff82aa50, state=...) at ../../vm/Interpreter.cpp:465
#29 0x00007f9dafd80a26 in js::ExecuteKernel (cx=cx@entry=0x55a6ff82aa50, script=..., script@entry=..., envChainArg=..., envChainArg@entry=..., newTargetValue=..., evalInFrame=..., evalInFrame@entry=..., result=..., result@entry=...) at ../../vm/Interpreter.cpp:840
#30 0x00007f9dafd80b16 in js::Execute (cx=cx@entry=0x55a6ff82aa50, script=script@entry=..., envChain=envChain@entry=..., rval=rval@entry=...) at ../../vm/Stack.h:113
#31 0x00007f9dafe8d449 in EvaluateSourceBuffer<char16_t> (cx=cx@entry=0x55a6ff82aa50, scopeKind=<optimized out>, env=..., env@entry=..., optionsArg=..., srcBuf=..., rval=...) at /builddir/firefox-78.2.0/js/src/vm/CompilationAndEvaluation.cpp:498
#32 0x00007f9dafe8d59c in JS::Evaluate (cx=0x55a6ff82aa50, envChain=..., envChain@entry=..., options=..., srcBuf=..., rval=rval@entry=...) at ../../vm/Scope.h:309
#33 0x00007f9db111007c in GjsContextPrivate::eval_with_scope (this=0x55a6ff81d0a0, scope_object=..., script=<optimized out>, script_len=<optimized out>, filename=<optimized out>, retval=...) at /usr/include/mozjs-78/js/RootingAPI.h:903
#34 0x00007f9db11144a5 in GjsContextPrivate::eval (error=0x7ffedb2ccb08, exit_status_p=0x7ffedb2ccb00, filename=0x55a6ff7e8740 "/usr/share/gnome-maps/org.gnome.Maps", script_len=189, script=0x55a6ff8186e0 "#!/usr/bin/gjs\nimports.package.start({ name: \"gnome-maps\",\n", ' ' <repeats 24 times>, "version: \"40.0\",\n", ' ' <repeats 24 times>, "prefix: \"/usr\",\n", ' ' <repeats 24 times>, "libdir: \"/usr/lib64\" });\n", this=0x55a6ff81d0a0) at /usr/include/mozjs-78/js/RootingAPI.h:596
#35 gjs_context_eval (js_context=0x7ffedb2cc9c0, js_context@entry=0x55a6ff81d1c0, script=script@entry=0x55a6ff8186e0 "#!/usr/bin/gjs\nimports.package.start({ name: \"gnome-maps\",\n", ' ' <repeats 24 times>, "version: \"40.0\",\n", ' ' <repeats 24 times>, "prefix: \"/usr\",\n", ' ' <repeats 24 times>, "libdir: \"/usr/lib64\" });\n", script_len=script_len@entry=189, filename=filename@entry=0x55a6ff7e8740 "/usr/share/gnome-maps/org.gnome.Maps", exit_status_p=exit_status_p@entry=0x7ffedb2ccb00, error=error@entry=0x7ffedb2ccb08) at ../gjs/context.cpp:1042
#36 0x000055a6fd9cfdbd in define_argv_and_eval_script (filename=0x55a6ff7e8740 "/usr/share/gnome-maps/org.gnome.Maps", len=189, script=0x55a6ff8186e0 "#!/usr/bin/gjs\nimports.package.start({ name: \"gnome-maps\",\n", ' ' <repeats 24 times>, "version: \"40.0\",\n", ' ' <repeats 24 times>, "prefix: \"/usr\",\n", ' ' <repeats 24 times>, "libdir: \"/usr/lib64\" });\n", argv=<optimized out>, argc=<optimized out>, js_context=0x55a6ff81d1c0) at ../gjs/console.cpp:191
#37 main (argc=<optimized out>, argv=<optimized out>) at ../gjs/console.cpp:384
```https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/223Maps frozen after setting up OSM account2022-08-24T20:45:25ZDavid HeidelbergMaps frozen after setting up OSM accountwhen I set up OSM account, Maps freezes. When I rerun, it works correctly, until I go to OSM account settings. Then, after closing it, it freezes again and prints g_error_free.
I can test patches and do any debug if needed. GNOME Maps 3...when I set up OSM account, Maps freezes. When I rerun, it works correctly, until I go to OSM account settings. Then, after closing it, it freezes again and prints g_error_free.
I can test patches and do any debug if needed. GNOME Maps 3.34.0.https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/206gnome-maps crashes/fail-to-start in wayland session2022-08-24T20:33:36ZJagadeesh Kotragnome-maps crashes/fail-to-start in wayland sessionGnome 3.34 Latest release on Arch Linux (Up-to-Date)
I get the following message if i try to start `gnome-maps`
`
Gdk-Message: 10:27:08.804: Error 71 (Protocol error) dispatching to Wayland display.
`Gnome 3.34 Latest release on Arch Linux (Up-to-Date)
I get the following message if i try to start `gnome-maps`
`
Gdk-Message: 10:27:08.804: Error 71 (Protocol error) dispatching to Wayland display.
`https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/179Segfault after moving looking at OSM account2022-08-26T19:40:44ZYotamSegfault after moving looking at OSM accountCrash log: [crash.txt](/uploads/bef4880e1c13e1600a1a90ecca5a9341/crash.txt)
Steps to reproduce:
1. Open GNOME Maps with a signed in account
2. Click on Set Up OpenStreetMap account
3. Close the modal
4. Zoom out/in a bit
5. It should se...Crash log: [crash.txt](/uploads/bef4880e1c13e1600a1a90ecca5a9341/crash.txt)
Steps to reproduce:
1. Open GNOME Maps with a signed in account
2. Click on Set Up OpenStreetMap account
3. Close the modal
4. Zoom out/in a bit
5. It should segfaulthttps://gitlab.gnome.org/GNOME/gnome-maps/-/issues/162Can't start Gnome Maps latest Flatpak version: "Clutter-Gtk-ERROR **: 08:21:1...2022-08-24T20:35:38ZMCan't start Gnome Maps latest Flatpak version: "Clutter-Gtk-ERROR **: 08:21:10.584: *** Unsupported backend."I installed latest Gnome Maps from Flathub and get below error. I'm running Ubuntu 18.04.2.
```bash
~$ flatpak run org.gnome.Maps
(org.gnome.Maps:2): Clutter-Gtk-ERROR **: 08:21:10.584: *** Unsupported backend.
~$ flatpak run org.gnom...I installed latest Gnome Maps from Flathub and get below error. I'm running Ubuntu 18.04.2.
```bash
~$ flatpak run org.gnome.Maps
(org.gnome.Maps:2): Clutter-Gtk-ERROR **: 08:21:10.584: *** Unsupported backend.
~$ flatpak run org.gnome.Maps --version
3.32.0
```https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/156[Wayland] Taking a screenshot of the application window results in an empty area2022-08-28T18:06:26ZChristian Stadelmann[Wayland] Taking a screenshot of the application window results in an empty areaSteps to reproduce:
1. have a GNOME/Wayland session
2. start gnome-maps
3. take a screenshot of the window only (by using Alt+PrtScr)
4. have a look at the screenshot
What should happen:
It should show the map content. This does work fi...Steps to reproduce:
1. have a GNOME/Wayland session
2. start gnome-maps
3. take a screenshot of the window only (by using Alt+PrtScr)
4. have a look at the screenshot
What should happen:
It should show the map content. This does work fine if getting a screenshot of the whole window (only pressing PrtScr)
What happens:
The window is missing the map: ![Screenshot](/uploads/7b1ffbfaab340af300d822803006bfb0/Bildschirmfoto_von_2019-02-27_21-13-53.png)
Additional information:
* On previous versions of GNOME, when the zoom controls where an overlay to the map, the zoom controls would be shown in the screenshot.
* Popover menus (e.g. when getting information for a location) are not drawn in the screenshot either.
* Old downstream bug report where the bug has affected other Gtk3/Wayland applications as well: https://bugzilla.redhat.com/show_bug.cgi?id=1384560
* This issue does affect other Gtk/Wayland applications too, e.g. Firefox ([another downstream bug report](https://bugzilla.redhat.com/show_bug.cgi?id=1683378)).
Version information:
gtk3-3.24.1-2.fc29.x86_64
glib2-2.58.3-1.fc29.x86_64
clutter-1.26.2-7.fc29.x86_64
clutter-gtk-1.8.4-4.fc29.x86_64
libwayland-client-1.16.0-1.fc29.x86_64
gnome-shell-3.30.2-1.fc29.x86_64
mutter-3.30.2-2.fc29.x86_64
libchamplain-0.12.16-4.fc29.x86_64
cogl-1.22.2-11.fc29.x86_64
cairo-1.16.0-3.fc29.x86_64
This is probably a bug in some library being used by GNOME Maps, but I can't tell which one. Please let me know so I can open a bug report there.https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/131Display gets messed up when routing panel is active2019-09-10T06:45:41ZAdam WilliamsonDisplay gets messed up when routing panel is activeTo reproduce with current Fedora 29 (with gnome-maps 3.30.1), just run Maps, right-click somewhere, and select 'Route from here'. The routing panel to the right of the map opens, but half of it is not visible, seemingly covered in some s...To reproduce with current Fedora 29 (with gnome-maps 3.30.1), just run Maps, right-click somewhere, and select 'Route from here'. The routing panel to the right of the map opens, but half of it is not visible, seemingly covered in some sort of odd white...layer. If you then resize the window, the whole routing panel disappears behind the white layer, and the window stops being square (the right hand side of the window sort of bleeds past the X button, is the best way I can describe it).
Additionally, if you then right-click anywhere and click 'What's Here?' after triggering the above bug, Maps crashes.
There's [a video](https://bugzilla.redhat.com/attachment.cgi?id=1492297) and [a backtrace](https://bugzilla.redhat.com/attachment.cgi?id=1492639) attached to [the downstream bug](https://bugzilla.redhat.com/show_bug.cgi?id=1637751).
Find recent F29 images at https://www.happyassassin.net/nightlies.html .https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/129Cannot move the map or zoom using the mouse on wayland2020-12-23T19:18:04ZLaurent BigonvilleCannot move the map or zoom using the mouse on waylandHello,
Using gnome-maps 3.30.1 under wayland, I cannot move the map or zoom using the mouse on wayland
If I force the GDK_BACKEND to x11 it works as expectedHello,
Using gnome-maps 3.30.1 under wayland, I cannot move the map or zoom using the mouse on wayland
If I force the GDK_BACKEND to x11 it works as expectedhttps://gitlab.gnome.org/GNOME/gnome-maps/-/issues/105maps does not start2022-08-24T20:35:06ZBugzillamaps does not start## Submitted by Matthias Clasen `@matthiasc`
**[Link to original bug (#790443)](https://bugzilla.gnome.org/show_bug.cgi?id=790443)**
## Description
This is a fresh f27 install in a boxes vm:
starting maps, I get:
Gjs-Message: JS W...## Submitted by Matthias Clasen `@matthiasc`
**[Link to original bug (#790443)](https://bugzilla.gnome.org/show_bug.cgi?id=790443)**
## Description
This is a fresh f27 install in a boxes vm:
starting maps, I get:
Gjs-Message: JS WARNING: [resource:///org/gnome/Maps/js/mapView.js 299]: reference to undefined property "_mapType"
Gjs-Message: JS WARNING: [resource:///org/gnome/Maps/js/placeEntry.js 98]: Too many arguments to method Gtk.TreeModelFilter.set_visible_func: expected 1, got 3
Gjs-Message: JS WARNING: [resource:///org/gnome/Maps/js/placeEntry.js 98]: Too many arguments to method Gtk.TreeModelFilter.set_visible_func: expected 1, got 3
Gjs-Message: JS WARNING: [resource:///org/gnome/Maps/js/routeEntry.js 61]: reference to undefined property "GdkWaylandWindow"
Gjs-Message: JS WARNING: [resource:///org/gnome/Maps/js/placeEntry.js 98]: Too many arguments to method Gtk.TreeModelFilter.set_visible_func: expected 1, got 3
Gjs-Message: JS WARNING: [resource:///org/gnome/Maps/js/placeEntry.js 98]: Too many arguments to method Gtk.TreeModelFilter.set_visible_func: expected 1, got 3
Gjs-Message: JS WARNING: [resource:///org/gnome/Maps/js/placeEntry.js 98]: Too many arguments to method Gtk.TreeModelFilter.set_visible_func: expected 1, got 3
(org.gnome.Maps:2346): Gdk-WARNING **: Native Windows taller than 65535 pixels are not supported
This is 3.26.2https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/69[CRASH] Gnome-Maps crashes on startup2020-12-23T19:51:35ZBugzilla[CRASH] Gnome-Maps crashes on startup## Submitted by Max Mustermann
**[Link to original bug (#768068)](https://bugzilla.gnome.org/show_bug.cgi?id=768068)**
## Description
Since I upgraded from Fedora 23 to 24 (in a VMware Workstation Player 12 guest) Gnome-maps crashes...## Submitted by Max Mustermann
**[Link to original bug (#768068)](https://bugzilla.gnome.org/show_bug.cgi?id=768068)**
## Description
Since I upgraded from Fedora 23 to 24 (in a VMware Workstation Player 12 guest) Gnome-maps crashes on start-up. I see the application window for a short while, but it closes immediately.
Starting Gnome-maps from a terminal window returns the following messages:
(gnome-maps:5618): Gtk-WARNING **: Theme parsing error: application.css:14:30: The style property GtkButton:image-spacing is deprecated and shouldn't be used anymore. It will be removed in a future version
(gnome-maps:5618): Gtk-WARNING **: Theme parsing error: application.css:15:31: The style property GtkWidget:interior-focus is deprecated and shouldn't be used anymore. It will be removed in a future version
VMware: vmw_ioctl_command error Invalid argument.
It also tells me that a memory dump is written (but I don't know where).
In GNOME-Logs I see a line
[drm:vmw_execbuf_process [vmwgfx]] *ERROR* Invalid SVGA3D command: 1181https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/55Modal dialogs break the map view mouse events2022-08-24T20:34:48ZBugzillaModal dialogs break the map view mouse events## Submitted by Marius Stanciu
**[Link to original bug (#763179)](https://bugzilla.gnome.org/show_bug.cgi?id=763179)**
## Description
Hi, new around here!
Popping any modal dialog ( then closing it ) while keeping the mouse inside ...## Submitted by Marius Stanciu
**[Link to original bug (#763179)](https://bugzilla.gnome.org/show_bug.cgi?id=763179)**
## Description
Hi, new around here!
Popping any modal dialog ( then closing it ) while keeping the mouse inside the main window makes the map view ignore all the mouse events ( such as clicks, drags, right-click context menus etc ).
Here's a gif depicting it on my (Fedora) system:
https://media.giphy.com/media/3o7abrnkUoKlHl6wuY/giphy.gif
After a lot of trial and error and research I figured out it was a Clutter bug ( might report it later on their bug thingie), specifically, the interaction between Clutter and Gdk.
I have found a workaround/fix by changing the clutter's windowing backend to X11
(the default is Gdk ) but I am not really sure about the implications of such a change ( although everything seems to be fine on my machine ).
I will attach a patch containing my hotfix.
### Depends on
* [Bug 758350](https://bugzilla.gnome.org/show_bug.cgi?id=758350)https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/38Popovers don't animate2023-08-11T21:31:18ZBugzillaPopovers don't animate## Submitted by Hashem Nasarat
**[Link to original bug (#760488)](https://bugzilla.gnome.org/show_bug.cgi?id=760488)**
## Description
For some reason the GtkPopovers we use and some of the GtkButtons within them don't animate like t...## Submitted by Hashem Nasarat
**[Link to original bug (#760488)](https://bugzilla.gnome.org/show_bug.cgi?id=760488)**
## Description
For some reason the GtkPopovers we use and some of the GtkButtons within them don't animate like the rest of Gtk+.
In the marker popover the circular button doesn't animate on hover but the square buttons do for some reason.
http://webm.land/w/oKWC/https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/31MapView not refreshing properly leaving bits of popovers around2023-08-11T21:31:17ZBugzillaMapView not refreshing properly leaving bits of popovers around## Submitted by Andreas Nilsson
**[Link to original bug (#758350)](https://bugzilla.gnome.org/show_bug.cgi?id=758350)**
## Description
it doesn't go away
### Blocking
* [Bug 763179](https://bugzilla.gnome.org/show_bug.cgi?id=763...## Submitted by Andreas Nilsson
**[Link to original bug (#758350)](https://bugzilla.gnome.org/show_bug.cgi?id=758350)**
## Description
it doesn't go away
### Blocking
* [Bug 763179](https://bugzilla.gnome.org/show_bug.cgi?id=763179)https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/26Search popup disappears but bits left over map2024-02-19T20:36:45ZBugzillaSearch popup disappears but bits left over map## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#756558)](https://bugzilla.gnome.org/show_bug.cgi?id=756558)**
## Description
Typing the first letter of a contact's name, the search popup will show, typing the wron...## Submitted by Bastien Nocera `@hadess`
**[Link to original bug (#756558)](https://bugzilla.gnome.org/show_bug.cgi?id=756558)**
## Description
Typing the first letter of a contact's name, the search popup will show, typing the wrong letter afterwards should hide the popup, but bits of it are left on top of the map.
The left-overs disappear if I maximise the window, or the map is moved.https://gitlab.gnome.org/GNOME/gnome-maps/-/issues/2Long press support for touch2023-09-18T07:06:22ZBugzillaLong press support for touch## Submitted by Jean-François Fortin Tam `@jfft`
**[Link to original bug (#709605)](https://bugzilla.gnome.org/show_bug.cgi?id=709605)**
## Description
Would be great if doing a "long" click on the map (and other areas where require...## Submitted by Jean-François Fortin Tam `@jfft`
**[Link to original bug (#709605)](https://bugzilla.gnome.org/show_bug.cgi?id=709605)**
## Description
Would be great if doing a "long" click on the map (and other areas where required) did the same as right-clicking, otherwise these contextual features are inaccessible on touch devices.
### Depends on
* [Bug 789218](https://bugzilla.gnome.org/show_bug.cgi?id=789218)