GNOME Bugzilla – Bug 795514
Totem UI artifacts and general performance issues
Last modified: 2018-05-19 08:01:25 UTC
Created attachment 371340 [details] Totem log Hello! After updating Gnome to 3.28.X, Totem got some update that made the software completely unusable for me. 1) Seeking does not work 2) Pause button does not respond 3) Next/Previos does not respond 4) Seeking menu does not work when clicking on a time frame to jump to 5) Full screen creates strange red visual artifacts 6) The video timer looks strange. Some visual artifacts are present 7) Playback of a video is very slow. There is some serious lag I have made an illustrative video of the problem hosted here: https://webmshare.com/rarKQ I have some logs by using GST_DEBUG_NO_COLOR=1 GST_DEBUG=*:2 totem 2> log These logs are attached here. Totem version: totem 3.26.0+37+g84700147-1 Gstreamer version: gstreamer 1.14.0-1 My system information: System Information PROCESSOR: Intel Core i5-4570 @ 3.60GHz Core Count: 4 Extensions: SSE 4.2 + AVX2 + AVX + RDRAND + FSGSBASE Cache Size: 6144 KB Microcode: 0x24 Scaling Driver: intel_pstate powersave GRAPHICS: MSI AMD Radeon RX 470/480/570/580 Display Driver: modesetting 1.19.1 Monitor: BenQ xl2411t Screen: 1920x1080 MOTHERBOARD: ASUS B85-PLUS Memory: 16384MB Chipset: Intel 4th Gen Core DRAM Network: Realtek RTL8111/8168/8411 DISK: 128GB Samsung SSD 840 + 1000GB Seagate ST1000DM010-2DM1 + 1000GB Seagate ST1000DM003-1CH1 File-System: btrfs Mount Options: relatime rw space_cache ssd subvol=/ subvolid=5 Disk Scheduler: CFQ OPERATING SYSTEM: Arch rolling Kernel: 4.16.3-1-ARCH (x86_64) Desktop: GNOME Shell 3.28.1 Compiler: GCC 7.3.1 20180312
Does the same thing happen with Cheese, or Maps? It's very likely bugs in the Mesa stack.
Maps sort of works. Map shows and buttons react but scroll wheel does nothing, strange artefacts at the lower right corner(Above text OpenStreetMap) and feels a bit sluggish. Cheese runs but I have no camera so I cannot really test it. Console shows some errors tough: (cheese:30568): cheese-CRITICAL **: 23:32:52.347: cheese_camera_device_get_name: assertion 'CHEESE_IS_CAMERA_DEVICE (device)' failed (cheese:30568): GLib-CRITICAL **: 23:32:52.347: g_variant_new_string: assertion 'string != NULL' failed (cheese:30568): GLib-CRITICAL **: 23:32:52.347: g_variant_ref_sink: assertion 'value != NULL' failed (cheese:30568): GLib-GIO-CRITICAL **: 23:32:52.347: g_settings_schema_key_type_check: assertion 'value != NULL' failed (cheese:30568): GLib-CRITICAL **: 23:32:52.347: g_variant_get_type_string: assertion 'value != NULL' failed (cheese:30568): GLib-GIO-CRITICAL **: 23:32:52.347: g_settings_set_value: key 'camera' in 'org.gnome.Cheese' expects type 's', but a GVariant of type '(null)' was given (cheese:30568): GLib-CRITICAL **: 23:32:52.347: g_variant_unref: assertion 'value != NULL' failed ** (cheese:30568): CRITICAL **: 23:32:52.347: cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device != NULL' failed
If it's really a problem of Mesa, can you guide me to giving their developers with enough information to work on?
I'm afraid not, similar problems happened in Fedora, but were eventually fixed. You should report it to your distribution first.
*** Bug 796223 has been marked as a duplicate of this bug. ***
https://bugs.freedesktop.org/show_bug.cgi?id=106441