pitivi issueshttps://gitlab.gnome.org/GNOME/pitivi/-/issues2024-03-11T16:19:14Zhttps://gitlab.gnome.org/GNOME/pitivi/-/issues/2659Clip Title UI disappearing2024-03-11T16:19:14ZEnguerrand de RibaucourtClip Title UI disappearingIn some conditions, the UI for Title Clips disappears. The box under Clip/Transition turns empty when a Title Clip is selected. It is no longer possible to change the Title for instance. Unfortunately I haven't been able to produce a min...In some conditions, the UI for Title Clips disappears. The box under Clip/Transition turns empty when a Title Clip is selected. It is no longer possible to change the Title for instance. Unfortunately I haven't been able to produce a minimal xges to reproduce. With the proper file, the issue can be resolved by selecting a different clip (not a title) and restarting Pitivi. The disappearing only happens when the last selected element was a title when Pitivi was closed, then re-opened.
![image](/uploads/88617813fbc739982c2b478051e2e82d/image.png)https://gitlab.gnome.org/GNOME/pitivi/-/issues/2658The keyframe mechanism is too hard to understand2024-02-24T07:36:26Zisan kolatThe keyframe mechanism is too hard to understandThe keyframing system in Pitivi is way too confusing to understand. Here is a clip of me literally trying to understand the keyframing system.![Recording__00000](/uploads/ca0c8202a2b8ef15670819edebdfa8af/Recording__00000.mp4)
I would app...The keyframing system in Pitivi is way too confusing to understand. Here is a clip of me literally trying to understand the keyframing system.![Recording__00000](/uploads/ca0c8202a2b8ef15670819edebdfa8af/Recording__00000.mp4)
I would appreciate it if you epic devs would make the keyframe system something like the one you can find in like... for example Shotcut and stuff.https://gitlab.gnome.org/GNOME/pitivi/-/issues/2657my CPU usage during editing a vidéo2024-01-17T10:11:44ZStéphan RICHARDmy CPU usage during editing a vidéoHello, in the daily use of Pitivi, depending on the actions I take, Pitivi starts to freeze for very variable durations. Very often Pitivi resumes its operation afterwards but somtimes I have to kill it . My PC is equipped with a 4-core ...Hello, in the daily use of Pitivi, depending on the actions I take, Pitivi starts to freeze for very variable durations. Very often Pitivi resumes its operation afterwards but somtimes I have to kill it . My PC is equipped with a 4-core processor but when Pitivi is frozen, only one of these 4 cores is running (at 100%). It can be randomly this or that core, sometimes the load of the core swap from one core to another...
![Capture_d\_écran_du_2024-01-15_08-08-41](/uploads/1840b59a712bfdf848c20efb9b157911/Capture_d_%C3%A9cran_du_2024-01-15_08-08-41.png)
![Capture d’écran du 2024-01-15 08-19-31.png](/uploads/06742412b2163fa5566db6614f1f7329/Capture_d_%C3%A9cran_du_2024-01-15_08-19-31.png)
As you can see at this moment Pitivi is freezing for a few minutes and the CPU usage is 25% (1/4 core) used by python3 process .
I'am on Debian-12-amd64-gnome and I using Pitivi 2023_03 wich installed from flathub .
Is it possible to optimize this?
THANKS
Stephanhttps://gitlab.gnome.org/GNOME/pitivi/-/issues/2656Unable to move in the timeline2023-12-21T09:11:40ZStéphan RICHARDUnable to move in the timelineGood morning,
I just installed a brand new debian gnome 12. I immediately uninstalled the pitivi version from the debian repositories and therefore installed the pre-built version from the flathub repository.
So my installed version is 2...Good morning,
I just installed a brand new debian gnome 12. I immediately uninstalled the pitivi version from the debian repositories and therefore installed the pre-built version from the flathub repository.
So my installed version is 2023_03.
I therefore encounter a rather annoying problem: It is impossible for me to move around in the timiline using the red cursor.
When I click on it it is impossible for me to get hold of it.
Thank you in advance for your help .
Here is the feedback from my terminal from installation until the launch of Pitivi:
```
root@debian:~# flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
root@debian:~# flatpak install flathub org.pitivi.Pitivi
Looking for matches…
Required runtime for org.pitivi.Pitivi/x86_64/stable (runtime/org.gnome.Platform/x86_64/44) found in remote flathub
Do you want to install it? [Y/n]: y
org.pitivi.Pitivi permissions:
ID Branch Op Remote Download
1. [✓] org.freedesktop.Platform.GL.default 22.08 i flathub 147,5 Mo / 146,8 Mo
2. [✓] org.freedesktop.Platform.GL.default 22.08-extra i flathub 17,9 Mo / 146,8 Mo
3. [✓] org.freedesktop.Platform.VAAPI.Intel 22.08 i flathub 13,6 Mo / 13,4 Mo
4. [✓] org.freedesktop.Platform.openh264 2.2.0 i flathub 887,2 Ko / 944,3 Ko
5. [✓] org.gnome.Platform.Locale 44 i flathub 6,4 Mo / 340,6 Mo
6. [✓] org.gnome.Platform 44 i flathub 330,6 Mo / 326,9 Mo
7. [✓] org.pitivi.Pitivi.Codecs stable i flathub 9,6 Mo / 9,3 Mo
8. [✓] org.pitivi.Pitivi.Locale stable i flathub 30,6 Ko / 1,9 Mo
9. [✓] org.pitivi.Pitivi stable i flathub 174,1 Mo / 158,0 Mo
Warning: Removing magic mime rule from exports
ID Branch Op Remote Download
1. [✓] org.freedesktop.Platform.GL.default 22.08 i flathub 147,5 Mo / 146,8 Mo
2. [✓] org.freedesktop.Platform.GL.default 22.08-extra i flathub 17,9 Mo / 146,8 Mo
3. [✓] org.freedesktop.Platform.VAAPI.Intel 22.08 i flathub 13,6 Mo / 13,4 Mo
4. [✓] org.freedesktop.Platform.openh264 2.2.0 i flathub 887,2 Ko / 944,3 Ko
5. [✓] org.gnome.Platform.Locale 44 i flathub 6,4 Mo / 340,6 Mo
6. [✓] org.gnome.Platform 44 i flathub 330,6 Mo / 326,9 Mo
7. [✓] org.pitivi.Pitivi.Codecs stable i flathub 9,6 Mo / 9,3 Mo
8. [✓] org.pitivi.Pitivi.Locale stable i flathub 30,6 Ko / 1,9 Mo
9. [✓] org.pitivi.Pitivi stable i flathub 174,1 Mo / 158,0 Mo
Warning: Removing magic mime rule from exports
Warning: Removing magic mime rule from exports
Installation complete.
root@debian:~# exit
déconnexion
stephan@debian:~$ flatpak run org.pitivi.Pitivi
Note that the directories
'/var/lib/flatpak/exports/share'
'/home/stephan/.local/share/flatpak/exports/share'
are not in the search path set by the XDG_DATA_DIRS environment variable, so
applications installed by Flatpak may not appear on your desktop until the
session is restarted.
** (gst-plugin-scanner:6): CRITICAL **: 09:21:09.761: Couldn't g_module_open libpython. Reason: /usr/lib/x86_64-linux-gnu/libpython3.10.so: cannot open shared object file: No such file or directory
(pitivi:2): GStreamer-Video-CRITICAL **: 09:23:34.944: gst_video_frame_map_id: assertion 'info->finfo->format == meta->format' failed
(pitivi:2): Gtk-CRITICAL **: 09:24:04.416: gtk_tree_model_filter_real_unref_node: assertion 'elt->ref_count > 0' failed
(pitivi:2): Gtk-CRITICAL **: 09:24:04.417: gtk_tree_model_filter_real_unref_node: assertion 'elt->ref_count > 0' failed
(pitivi:2): Gtk-CRITICAL **: 09:24:04.417: gtk_tree_model_filter_real_unref_node: assertion 'elt->ref_count > 0' failed
(pitivi:2): Gtk-CRITICAL **: 09:24:04.417: gtk_tree_model_filter_real_unref_node: assertion 'elt->ref_count > 0' failed
(pitivi:2): GStreamer-CRITICAL **: 09:26:31.084: gst_object_unref: assertion 'object != NULL' failed
(pitivi:2): GES-CRITICAL **: 09:26:31.084: ges_layer_get_auto_transition: assertion 'GES_IS_LAYER (layer)' failed
(pitivi:2): GStreamer-CRITICAL **: 09:26:37.515: gst_object_unref: assertion 'object != NULL' failed
(pitivi:2): GES-CRITICAL **: 09:26:37.515: ges_layer_get_auto_transition: assertion 'GES_IS_LAYER (layer)' failed
(pitivi:2): GStreamer-Video-CRITICAL **: 09:28:10.494: gst_video_frame_map_id: assertion 'info->finfo->format == meta->format' failed
Traceback (most recent call last):
File "/app/lib/pitivi/python/pitivi/application.py", line 361, in _undo_cb
self.action_log.undo()
File "/app/lib/pitivi/python/pitivi/undo/undo.py", line 313, in undo
self._run(stack.undo)
File "/app/lib/pitivi/python/pitivi/undo/undo.py", line 346, in _run
operation()
File "/app/lib/pitivi/python/pitivi/undo/undo.py", line 119, in undo
self._perform_actions(self.done_actions[::-1], "undo")
File "/app/lib/pitivi/python/pitivi/undo/undo.py", line 112, in _perform_actions
raise UndoError("Delayable actions failed to apply: {} {}".format(delayed_actions, delayed_reasons))
pitivi.undo.base.UndoError: Delayable actions failed to apply: [<timeline.TransitionClipRemovedAction object at 0x7f6f475962c0 (pitivi+undo+timeline+TransitionClipRemovedAction at 0x55c71e446da0)>] {<timeline.TransitionClipRemovedAction object at 0x7f6f475962c0 (pitivi+undo+timeline+TransitionClipRemovedAction at 0x55c71e446da0)>: ConditionsNotReadyYetError('transition has not been created yet')}
(pitivi:2): GStreamer-Video-CRITICAL **: 09:33:23.348: gst_video_frame_map_id: assertion 'info->finfo->format == meta->format' failed
(pitivi:2): GStreamer-Video-CRITICAL **: 09:33:31.331: gst_video_frame_map_id: assertion 'info->finfo->format == meta->format' failed
(pitivi:2): GStreamer-Video-CRITICAL **: 09:33:31.352: gst_video_frame_map_id: assertion 'info->finfo->format == meta->format' failed
(pitivi:2): GStreamer-Video-CRITICAL **: 09:33:31.372: gst_video_frame_map_id: assertion 'info->finfo->format == meta->format' failed
(pitivi:2): GStreamer-Video-CRITICAL **: 09:33:31.396: gst_video_frame_map_id: assertion 'info->finfo->format == meta->format' failed
```
Stephanhttps://gitlab.gnome.org/GNOME/pitivi/-/issues/2655git tag version doesn't match tarball version2023-11-29T20:08:44ZJeremy Bichagit tag version doesn't match tarball version[meson.build](meson.build) declares that the latest version is `2023.03` and the tarball release is `https://download.gnome.org/sources/pitivi/2023/pitivi-2023.03.tar.xz` in https://download.gnome.org/sources/pitivi/2023/
However, the c...[meson.build](meson.build) declares that the latest version is `2023.03` and the tarball release is `https://download.gnome.org/sources/pitivi/2023/pitivi-2023.03.tar.xz` in https://download.gnome.org/sources/pitivi/2023/
However, the corresponding git tag is 2023.03.0
Please use the same version number format. This would help me with the Debian packaging scripts.https://gitlab.gnome.org/GNOME/pitivi/-/issues/2654blog.pitivi.org misconfigured2023-11-13T11:36:20ZAlexandre Frankeblog.pitivi.org misconfiguredblog.pitivi.org was a thing once, but now it looks like a wordpress.com page for an account that is not configured properly. I’m guessing it is supposed to be replaced with [pitivi.org/news](https://pitivi.org/news). In that case, can yo...blog.pitivi.org was a thing once, but now it looks like a wordpress.com page for an account that is not configured properly. I’m guessing it is supposed to be replaced with [pitivi.org/news](https://pitivi.org/news). In that case, can you set up a redirect?
Planet GNOME has a feed for @aleb with a blog.pitivi.org URL. There is a working personal blog as well. Do we want to remove the former, or replace it with the News page?https://gitlab.gnome.org/GNOME/pitivi/-/issues/2653Some effects settings don't work properly when moving the settings slider bac...2023-10-03T06:22:07ZWill SeirSome effects settings don't work properly when moving the settings slider back and forth.I am using fedora 38, GNOME, X11, and the flatpak release of pitivi. I have a webm showing me a sample mp4 and applying the glitch effect, but some settings that are meant to be a slider are being treated as like a boolan switch either 0...I am using fedora 38, GNOME, X11, and the flatpak release of pitivi. I have a webm showing me a sample mp4 and applying the glitch effect, but some settings that are meant to be a slider are being treated as like a boolan switch either 0 or 1, off or on, which you'll see in the webm demonstration. I have not yet tested this on native RPM yet.
![pitivi-recording](/uploads/a33c14ca31d1c8e66caa7d625a116d58/pitivi-recording.webm)
You can't see the mouse because the GNOME screenshot recorder didn't pick it up. Now, when I click the keyframe button to the right of the slider and then click the reset to default button, THEN it works as it should.https://gitlab.gnome.org/GNOME/pitivi/-/issues/2652Pitivi should not phoning home without consent2023-08-23T19:00:02ZAlex CostPitivi should not phoning home without consentI've noticed that Pitivi makes network requests without the user's consent or knowledge.
In this way Pitivi is exposing user's data to the server, such us when is using the app and the user's IP address.
Since the user did not give any c...I've noticed that Pitivi makes network requests without the user's consent or knowledge.
In this way Pitivi is exposing user's data to the server, such us when is using the app and the user's IP address.
Since the user did not give any consent nor has been informed, this may be considered a spyware activity.https://gitlab.gnome.org/GNOME/pitivi/-/issues/2651Playhead not movable with mouse2023-07-16T12:01:45ZBernhard DonaubauerPlayhead not movable with mouseHello,
I'm on Fedora 38 with PiTiVi Version 2023.03 installed from the Fedora repositories.
In this environment it is not possible to grab the playhead with the mouse and move it.
Grettings,
BernhardHello,
I'm on Fedora 38 with PiTiVi Version 2023.03 installed from the Fedora repositories.
In this environment it is not possible to grab the playhead with the mouse and move it.
Grettings,
Bernhardhttps://gitlab.gnome.org/GNOME/pitivi/-/issues/2650Undo deleting an effect generates application crash modal2023-04-20T13:51:35ZMcKellan ClarkeUndo deleting an effect generates application crash modal## Summary of bug
When the user has multiple (more than one) effects, if the user deletes any of the effects _except the bottommost effect_, and then undos that deletion, the `Sorry, something didn't work right` modal is generated. Then,...## Summary of bug
When the user has multiple (more than one) effects, if the user deletes any of the effects _except the bottommost effect_, and then undos that deletion, the `Sorry, something didn't work right` modal is generated. Then, if the user either attempts to save changes to the project, save the project or close the project without saving, the application deadlocks.
### Steps to reproduce
1. Create a new project.
2. Put a clip on a layer of the project. The bug happens regardless of the clip used, so the sample clips provided by Pitivi work here.
3. Select the clip on the timeline.
4. Add multiple effects to the clip.
5. Delete one of any of the effects _except for the bottommost effect_, as shown by the highlighted effects in the below screenshot:
![image](/uploads/7441a776458de0f545f25c0dc1188bbc/image.png)
6. Undo this change. At this point, the `Sorry, something didn't work right` modal is generated.
7. Either save changes to the project, save the project as a project file, or discard changes using the above modal. At this point, the application deadlocks.
### Back traces
Back trace for the `Sorry, something didn't work right` modal:
[pitivi_modal_trace.txt](/uploads/b558a6ba1538b33c1f0e37ee0f8eb80e/pitivi_modal_trace.txt)
Back trace for the deadlock:
[pitivi_deadlock_trace.txt](/uploads/f8e1062b4be25ebb619225f164d17dfc/pitivi_deadlock_trace.txt)
### Scenario file
[20230420-074200_home_ubuntu_pitivi-dev_pitivi_data_undo_delete_effect.scenario](/uploads/0609c086252821a953843cb11e1107be/20230420-074200_home_ubuntu_pitivi-dev_pitivi_data_undo_delete_effect.scenario)https://gitlab.gnome.org/GNOME/pitivi/-/issues/2649Keyframes curve not visible in development environment2023-04-14T06:48:06ZElijah SmithKeyframes curve not visible in development environmentWhen I run Pitivi on my developer environment, I'm unable to see the yellow keyframe curve on all clips.
Steps to reproduce:
1. Install and setup [development environment](https://developer.pitivi.org/HACKING.html?gi-language=undefined)...When I run Pitivi on my developer environment, I'm unable to see the yellow keyframe curve on all clips.
Steps to reproduce:
1. Install and setup [development environment](https://developer.pitivi.org/HACKING.html?gi-language=undefined).
2. Run Pitivi, and create a new project.
3. Add a clip to the timeline.
4. Click on the clip.
The keyframe curve does not appear on my devopment environment. However, it will appear when I use Pitivi installed from Flathub. Here is an example on attempting to select/manipulate keyframes on each installation, using an audio clip from the test samples given in the repo.
Flathub:
![Screencast_from_04-13-2023_10_06_31_PM](/uploads/9a9a52e9c564dbc94b529c3d90ca169e/Screencast_from_04-13-2023_10_06_31_PM.gif)
Development Environment:
![Screencast_from_04-13-2023_10_24_48_PM](/uploads/846d30a91f75aa572fb54d32e77bd888/Screencast_from_04-13-2023_10_24_48_PM.gif)https://gitlab.gnome.org/GNOME/pitivi/-/issues/2648Hacking in docker: No permissions to creating new namespace - ignoring: Read-...2023-04-03T19:08:53ZsdbbsHacking in docker: No permissions to creating new namespace - ignoring: Read-only file systemI'm trying to do https://developer.pitivi.org/HACKING.html?gi-language=undefined in a Docker image of Ubuntu 20.04 - this is how far I got:
```
(ptv-flatpak) user@0070be4e453d:~/pitivi-dev/pitivi_git$ ptvtests
Running in sandbox: gst-v...I'm trying to do https://developer.pitivi.org/HACKING.html?gi-language=undefined in a Docker image of Ubuntu 20.04 - this is how far I got:
```
(ptv-flatpak) user@0070be4e453d:~/pitivi-dev/pitivi_git$ ptvtests
Running in sandbox: gst-validate-launcher /home/user/pitivi-dev/pitivi_git/tests/ptv_testsuite.py --dump-on-failure
flatpak build --device=dri --env=PITIVI_DEVELOPMENT=1 --env=PYTHONUSERBASE=/app/ --env=CC=ccache gcc --env=CXX=ccache g++ --filesystem=xdg-run/gvfsd --filesystem=xdg-run/at-spi/bus --share=network --socket=pulseaudio --socket=session-bus --socket=wayland --socket=x11 --talk-name=org.freedesktop.Flatpak --env=PITIVI_REPO_DIR=/home/user/pitivi-dev/pitivi_git --env=LC_CTYPE=C.UTF-8 --env=GST_ENCODING_TARGET_PATH=/app/share/gstreamer-1.0/encoding-profiles/:/app/share/pitivi/encoding-profiles/: --env=GST_PLUGIN_SYSTEM_PATH=/app/lib/gstreamer-1.0/: --env=FREI0R_PATH=/app/lib/frei0r-1/: --env=GST_PRESET_PATH=/app/share/gstreamer-1.0/presets/:/app/share/pitivi/gstpresets/: /home/user/pitivi-dev/pitivi-prefix gst-validate-launcher /home/user/pitivi-dev/pitivi_git/tests/ptv_testsuite.py --dump-on-failure
bwrap: No permissions to creating new namespace, likely because the kernel does not allow non-privileged user namespaces. On e.g. debian this can be enabled with 'sysctl kernel.unprivileged_userns_clone=1'.
```
Ok, so let me try this recommended `sysctl kernel.unprivileged_userns_clone=1`:
```
(ptv-flatpak) user@0070be4e453d:~/pitivi-dev/pitivi_git$ sysctl kernel.unprivileged_userns_clone=1
sysctl: setting key "kernel.unprivileged_userns_clone", ignoring: Read-only file system
(ptv-flatpak) user@0070be4e453d:~/pitivi-dev/pitivi_git$ sudo sysctl kernel.unprivileged_userns_clone=1
[sudo] password for user:
sysctl: setting key "kernel.unprivileged_userns_clone", ignoring: Read-only file system
```
Well... no dice `:(` What do I do here?
EDIT: if I run this with the administrator user of the docker image, that is via `sudo su`, I get instead:
bwrap: Creating new namespace failed: Operation not permittedhttps://gitlab.gnome.org/GNOME/pitivi/-/issues/2647HACKING.md: how to exit development environment?2023-08-23T18:30:36ZsdbbsHACKING.md: how to exit development environment?Current https://developer.pitivi.org/HACKING.html?gi-language=undefined says:
> Whenever you want to hack on Pitivi, start a new terminal and enter the development environment:
>
> ```
> $ cd pitivi-dev/pitivi && source bin/pitivi-env
...Current https://developer.pitivi.org/HACKING.html?gi-language=undefined says:
> Whenever you want to hack on Pitivi, start a new terminal and enter the development environment:
>
> ```
> $ cd pitivi-dev/pitivi && source bin/pitivi-env
> ...
> ```
>
> ... Note the prompt changes:
>
> (ptv-flatpak) $
>
> By entering the development environment, you get: ...
So - how do I *exit* this development environment? For instance, to exit a Python venv, one typically calls `deactivate` - but there is no such command here ...
Hopefully the answer is not CTRL-D, as that would probably kill my `ssh` session, where I'm trying to build pitivi from source ... (EDIT - yes, it both exits my docker environment, and the ssh shell, so make sure to run `sudo docker images && sudo docker ps -a` and possibly commit the container, it's its difficult to go back where you were)https://gitlab.gnome.org/GNOME/pitivi/-/issues/2646Unexplained initialize step makes Pitivi unusable for normal length movies2023-07-09T17:18:50ZEllieUnexplained initialize step makes Pitivi unusable for normal length moviesThe unexplained initialize step during render seems to make Pitivi unusable for normal length movies of about two hours. It makes some `python3` process eat up to 8-9GB of memory then is shot down by earlyoom after half an hour of not sh...The unexplained initialize step during render seems to make Pitivi unusable for normal length movies of about two hours. It makes some `python3` process eat up to 8-9GB of memory then is shot down by earlyoom after half an hour of not showing what it's even doing. This is for a regular feature length movies and 4-5 simple contrast/saturation effects. Handbrake needs about 2GB memory to encode such a movie, so this doesn't really seem to be a reasonable resource use just for a few simple color effects on top. It also makes me simply unable to export this now, so this isn't just an "it's kinda slow" minor performance issue but seems to turn this software basically unusable for any ~~normal~~ feature length project.
earlyoom output:
```
Apr 02 08:17:33 emeraldpc earlyoom[1756]: process exited after 0.1 seconds
Apr 02 08:17:33 emeraldpc earlyoom[1756]: sending SIGTERM to process 1606853 uid 1000 "python3": badness 1032, VmRSS 7766 MiB
Apr 02 08:17:33 emeraldpc earlyoom[1756]: low memory! at or below SIGTERM limits: mem 2.54%, swap 10.00%
Apr 02 08:17:33 emeraldpc earlyoom[1756]: mem avail: 392 of 15724 MiB ( 2.50%), swap free: 560 of 12287 MiB ( 4.56%)
```
**Version of Pitivi tested**: Version 2022.06 (via FlatHub)
**Linux distribution tested on:** Fedora 37https://gitlab.gnome.org/GNOME/pitivi/-/issues/2645"co located POCs unavaliable" Error when stepping the playhead through transi...2023-03-31T07:01:48ZDersterDaBeast"co located POCs unavaliable" Error when stepping the playhead through transitionsWhile stepping the playhead through transitions created by overlapping clips the following errors begin popping up in the console.
```
0:00:37.861589738 2 0x7f564009dc10 ERROR libav :0:: co located POCs unavailable
...While stepping the playhead through transitions created by overlapping clips the following errors begin popping up in the console.
```
0:00:37.861589738 2 0x7f564009dc10 ERROR libav :0:: co located POCs unavailable
0:00:40.462644062 2 0x7f564009dc10 ERROR libav :0:: co located POCs unavailable
0:00:41.888221662 2 0x7f564009dc10 ERROR libav :0:: co located POCs unavailable
0:00:44.127852199 2 0x7f564009dc10 ERROR libav :0:: co located POCs unavailable
0:00:48.304947369 2 0x7f564009dc10 ERROR libav :0:: co located POCs unavailable
0:00:48.557154740 2 0x7f564009dc10 ERROR libav :0:: co located POCs unavailable
```
I am using an Oracle Virtualbox VM and set up my environment following the [Hacking on Pitivi instructions](https://developer.pitivi.org/HACKING.html?gi-language=undefined). I am currently on the latest release of Pitivi, [Release 2023.03](https://gitlab.gnome.org/GNOME/pitivi/-/commit/06414db5ab7d6e0e5f1b174183b376c60c6e642d).
To recreate the errors you can follow these steps:
1. Start Pitivi and create a new project.
2. Import `30fps_numeroted_frames_blue.webm` and `30fps_numeroted_frames_red.mkv` from `pitivi/tests/samples`.
3. Add the `30fps_numeroted_frames_blue.webm` to the timeline on Layer 0 followed by `30fps_numeroted_frames_red.mkv` directly after it on the same layer.
4. Pull the `30fps_numeroted_frames_red.mkv` clip left of the timeline to timecode 00:02 to create a new transition from the blue clip to the red clip.
5. Then step the playhead across this transition using the arrow keys and the errors should start being printed in the console.
6. Occasionally other errors are generated but these are not re-creatable in my experience.
I found that [Issue #1991](https://gitlab.gnome.org/GNOME/pitivi/-/issues/1991) had the same error but this appears to be unrelated.https://gitlab.gnome.org/GNOME/pitivi/-/issues/2644Mismatch gnome version an stable Pitivi2023-04-13T21:19:36ZgrandtoubabMismatch gnome version an stable PitiviHeLlo,
As I get the warning that gnome 42 is out of life I try to use Pitivi stable version with gnome 43.
That is impossible!
```
flatpak install org.gnome.Platform
Looking for matches…
Similar refs found for ‘org.gnome.Platform’ in re...HeLlo,
As I get the warning that gnome 42 is out of life I try to use Pitivi stable version with gnome 43.
That is impossible!
```
flatpak install org.gnome.Platform
Looking for matches…
Similar refs found for ‘org.gnome.Platform’ in remote ‘flathub’ (system):
1) runtime/org.gnome.Platform/x86_64/3.24
2) runtime/org.gnome.Platform/x86_64/3.26
3) runtime/org.gnome.Platform/x86_64/3.28
4) runtime/org.gnome.Platform/x86_64/3.30
5) runtime/org.gnome.Platform/x86_64/3.32
6) runtime/org.gnome.Platform/x86_64/3.34
7) runtime/org.gnome.Platform/x86_64/3.36
8) runtime/org.gnome.Platform/x86_64/3.38
9) runtime/org.gnome.Platform/x86_64/40
10) runtime/org.gnome.Platform/x86_64/41
11) runtime/org.gnome.Platform/x86_64/42
12) runtime/org.gnome.Platform/x86_64/43
13) runtime/org.gnome.Platform/x86_64/44
Which do you want to use (0 to abort)? [0-13]: 12
ID Branch Op Remote Download
1. [✓] org.freedesktop.Platform.GL.default 22.08 i flathub 138,3 Mo / 137,7 Mo
2. [✓] org.freedesktop.Platform.GL.default 22.08-extra i flathub 9,5 Mo / 137,7 Mo
3. [✓] org.freedesktop.Platform.openh264 2.2.0 i flathub 1,2 Mo / 944,3 Ko
4. [✓] org.gnome.Platform.Locale 43 i flathub 2,2 Mo / 340,5 Mo
5. [✓] org.gnome.Platform 43 i flathub 350,2 Mo / 329,0 Mo
Installation complete.
guy@debian:~$ flatpak list
Name Application ID Version Branch Installation
Mesa org.freedesktop.Platform.GL.default 21.3.9 21.08 system
Mesa org.freedesktop.Platform.GL.default 22.3.5 22.08 system
Mesa (Extra) org.freedesktop.Platform.GL.default 22.3.5 22.08-extra system
openh264 org.freedesktop.Platform.openh264 2.1.0 2.0 system
openh264 org.freedesktop.Platform.openh264 2.1.0 2.2.0 system
GNOME Application Platform version 42 org.gnome.Platform 42 system
GNOME Application Platform version 43 org.gnome.Platform 43 system
Pitivi org.pitivi.Pitivi 2022.06 stable system
Codecs org.pitivi.Pitivi.Codecs stable system
guy@debian:~$ flatpak uninstall org.gnome.Platform
Similar installed refs found for ‘org.gnome.Platform’:
1) runtime/org.gnome.Platform/x86_64/43 (system)
2) runtime/org.gnome.Platform/x86_64/42 (system)
3) All of the above
Which do you want to use (0 to abort)? [0-3]: 2
Info: applications using the runtime org.gnome.Platform branch 42:
org.pitivi.Pitivi
Really remove? [y/n]: n
guy@debian:~$ flatpak update org.pitivi.Pitivi
Looking for updates…
Info: runtime org.gnome.Platform branch 42 is end-of-life, with reason:
The GNOME 42 runtime is no longer supported as of March 21, 2023. Please ask your application developer to migrate to a supported platform.
Info: applications using this runtime:
org.pitivi.Pitivi
Nothing to do.
```
Where is the Pitivi version using Ghome 43?https://gitlab.gnome.org/GNOME/pitivi/-/issues/2643gnome 42 end of life2023-03-24T09:07:43Zgrandtoubabgnome 42 end of lifeHello
Here the message from flatpak update
```
Info: runtime org.gnome.Platform branch 42 is end-of-life, with reason:
The GNOME 42 runtime is no longer supported as of March 21, 2023. Please ask your application developer to migrate ...Hello
Here the message from flatpak update
```
Info: runtime org.gnome.Platform branch 42 is end-of-life, with reason:
The GNOME 42 runtime is no longer supported as of March 21, 2023. Please ask your application developer to migrate to a supported platform.
Info: applications using this runtime:
org.pitivi.Pitivi
```
Do you plan to upgrade to gnome 43?2023.03Alexandru Băluțalexandru.balut@gmail.comAlexandru Băluțalexandru.balut@gmail.comhttps://gitlab.gnome.org/GNOME/pitivi/-/issues/2642ci: Use ci initiative flatpak template2023-03-25T17:19:56ZThibault Saunierci: Use ci initiative flatpak templateThe [GNOME citemplates](https://gitlab.gnome.org/GNOME/citemplates/) repository provides a template to simplify implementing flatpak deployments in gitlab ci. We should use that instead of our complex setup.
More information can be foun...The [GNOME citemplates](https://gitlab.gnome.org/GNOME/citemplates/) repository provides a template to simplify implementing flatpak deployments in gitlab ci. We should use that instead of our complex setup.
More information can be found here: https://gitlab.gnome.org/GNOME/Initiatives/-/wikis/DevOps-with-Flatpakhttps://gitlab.gnome.org/GNOME/pitivi/-/issues/2641Developer Console Font Color change failure2023-02-20T08:06:48ZRhythm NarulaDeveloper Console Font Color change failureFont Color of Developer console doesn't change when Theme of pitivi is changed to light mode from dark
Steps to Reproduce-
1.Enable Developer console plugin
2.Change theme from dark to light mode
3.Open Developer console
PFB the at...Font Color of Developer console doesn't change when Theme of pitivi is changed to light mode from dark
Steps to Reproduce-
1.Enable Developer console plugin
2.Change theme from dark to light mode
3.Open Developer console
PFB the attached screenshot of Developer Console when opened in light mode
![Screenshot_from_2023-02-20_13-20-06](/uploads/c974423745f54d0e33c78588139c289a/Screenshot_from_2023-02-20_13-20-06.png)https://gitlab.gnome.org/GNOME/pitivi/-/issues/2640Adding an effect via Drag and Drop fails2023-03-09T19:59:41ZyatinAdding an effect via Drag and Drop failsPoC:
- Add a clip to the timeline
- Select the clip
- Try to drag and drop an effect from the Effects Library onto the Clips tab -> Effects section (not the clip in the timeline, that works)
- The effect isn't added, and an error[1] ...PoC:
- Add a clip to the timeline
- Select the clip
- Try to drag and drop an effect from the Effects Library onto the Clips tab -> Effects section (not the clip in the timeline, that works)
- The effect isn't added, and an error[1] is printed to console
- Other ways of adding effects work fine
[1] Error:
```
Traceback (most recent call last):
File "/app/lib/pitivi/python/pitivi/clipproperties.py", line 894, in _drag_data_received_cb
self.clip.set_top_effect_index(effect, top_effect_index)
OverflowError: -1 not in range 0 to 4294967295
```2023.03Rhythm NarulaRhythm Narula