Summary: | kdenlive crashes when changing clip-text colour | ||
---|---|---|---|
Product: | [Applications] kdenlive | Reporter: | Germano Massullo <germano.massullo> |
Component: | User Interface & Miscellaneous | Assignee: | Jean-Baptiste Mardelle <jb> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | cgiraud, em1_24, rdieter, snd.noise, wegwerf-1-2-3 |
Priority: | NOR | Keywords: | triaged |
Version: | 16.08.2 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Germano Massullo
2015-04-16 17:01:02 UTC
Do you confirm the bug? AFAIK this tracker is for frameworks versions of kdenlive... older versions should be reported to mantis i think. (In reply to farid from comment #2) > AFAIK this tracker is for frameworks versions of kdenlive... older versions > should be reported to mantis i think. What do you mean? Mantis is announced "close" (but still alive) and I cannot create any account on Mantis. Germano, what do you call "clip-text color" ? Kdenlive 0.9.10 .deb x86 UbuntuStudio: crash not reproduced with "Color Clip" and "Title clip" with 1 colored text inside. (In reply to Cyril Giraud from comment #4) > Mantis is announced "close" (but still alive) and I cannot create any > account on Mantis. > > Germano, what do you call "clip-text color" ? You add a text to the movie, then you try to change its colour Germano please test if this is fixed in the latest version 16.04.2 and mark as solved if possible. (In reply to farid from comment #6) > Germano please test if this is fixed in the latest version 16.04.2 and mark > as solved if possible. As soon I get the update on my distro's repository, I will do the tests :-) Kdenlive 0.9.x is unsupported. I am facing the same issue with version 16.08.2 on ArchLinux! I never faced it with the previous version. Hope a soon fix :) Ibrahim, please post a useful crash backtrace, but please only the relevant crash thread. As I don't see crashes on my Kubuntu 16.04LTS this looks suspiciously like a distro packaging error. (In reply to Wegwerf from comment #10) > Ibrahim, please post a useful crash backtrace, but please only the relevant > crash thread. As I don't see crashes on my Kubuntu 16.04LTS this looks > suspiciously like a distro packaging error. Here it is, also I got another crash once I try to save the project ! When I try to change the "title clip" colour : Thread 27 (Thread 0x7fff72ffd700 (LWP 8736)): #0 0x00007fffee32410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x00007fffc1cf15ed in () at /usr/lib/mlt/libmltsdl.so #2 0x00007fffee31e454 in start_thread () at /usr/lib/libpthread.so.0 #3 0x00007fffefe637df in clone () at /usr/lib/libc.so.6 Thread 26 (Thread 0x7fff808a0700 (LWP 8735)): #0 0x00007fffefe5a551 in ppoll () at /usr/lib/libc.so.6 #1 0x00007fffe7c2b99d in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #2 0x00007fffe7c2bf8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 #3 0x00007fffc1a87eed in () at /usr/lib/libSDL-1.2.so.0 #4 0x00007fffc1a5b800 in () at /usr/lib/libSDL-1.2.so.0 #5 0x00007fffc1a63fe8 in () at /usr/lib/libSDL-1.2.so.0 #6 0x00007fffc1aa58a9 in () at /usr/lib/libSDL-1.2.so.0 #7 0x00007fffee31e454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x00007fffefe637df in clone () at /usr/lib/libc.so.6 Thread 25 (Thread 0x7fff810a1700 (LWP 8734)): #0 0x00007fffee32410f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x00007ffff6fa8243 in () at /usr/lib/libmlt.so.6 ----------------------------------------------------------------------------------- When I press Save Button : Thread 23 (Thread 0x7fff7ade0700 (LWP 8791)): #0 0x00007fffefe5ef19 in syscall () at /usr/lib/libc.so.6 #1 0x00007fffe80ef03a in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x00007fffe807de89 in () at /usr/lib/libglib-2.0.so.0 #3 0x00007fffe80d1aa6 in () at /usr/lib/libglib-2.0.so.0 #4 0x00007fffe80d10d5 in () at /usr/lib/libglib-2.0.so.0 #5 0x00007fffee31e454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x00007fffefe637df in clone () at /usr/lib/libc.so.6 Thread 22 (Thread 0x7fff7b5e1700 (LWP 8790)): #0 0x00007fffefe5ef19 in syscall () at /usr/lib/libc.so.6 #1 0x00007fffe80ef03a in g_cond_wait_until () at /usr/lib/libglib-2.0.so.0 #2 0x00007fffe807de89 in () at /usr/lib/libglib-2.0.so.0 #3 0x00007fffe80d1aa6 in () at /usr/lib/libglib-2.0.so.0 #4 0x00007fffe80d10d5 in () at /usr/lib/libglib-2.0.so.0 #5 0x00007fffee31e454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x00007fffefe637df in clone () at /usr/lib/libc.so.6 Thread 21 (Thread 0x7fff83666700 (LWP 8788)): #0 0x00007fffefe5a551 in ppoll () at /usr/lib/libc.so.6 #1 0x00007fffe7c2b99d in pa_mainloop_poll () at /usr/lib/libpulse.so.0 #2 0x00007fffe7c2bf8e in pa_mainloop_iterate () at /usr/lib/libpulse.so.0 Sorry, but I asked to post only the stacktrace of the crashing thread. Gdb will indicate whicht thread crashed. All other backtraces are meaningless as they show these threads were idle. I recently reported a similar report but it also affects changing color clip color: https://bugs.kde.org/show_bug.cgi?id=371416 should i close that one and post the backtrace here? I guess I figured the issue. Last update of Arch Linux with Gnome DE has changed Gnome from using Xorg to Wayland, which is not ready to use yet, that caused Kdenlive & other applications that were reported in Arch community not to run or run buggy. So the solution is to switch from Wayland to Xorg, and to do that you have to : from GDM interface, beneath the Password Entry box there is perfrences icon ( a small icon), press on it and choose xorg, and it is supposed to work as default in the next startup. If it didn't run as default, follow this instruction : "But if for some reason that doesn't work the file the setting is being saved into when you select "Gnome on Xorg" is "/var/lib/AccountsService/users/<user_name>". Change the "XSession=" line to be "XSession=gnome-xorg". Don't mess with the gdm user file there, do it on your user file." the solution was taken from this thread : https://bbs.archlinux.org/viewtopic.php?id=218319 @Wegwerf Thanks for helping :) it is cool to see a support team who responds fast. @Farid I think this will solve your problem too. Farid, makes sense to me to set the other report as a duplicate of this. Go for it...! *** Bug 371416 has been marked as a duplicate of this bug. *** Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! The problem is no longer happening on 18.04.3 |