| Summary: | Update openshot-qt to latest upstream version | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | William Kenney <wilcal.int> |
| Component: | RPM Packages | Assignee: | Rémi Verschelde <rverschelde> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fri, geiger.david68210, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | openshot-qt-2.2.0-1.mga6.noarch.rpm | CVE: | |
| Status comment: | |||
| Attachments: | konsole output of openshot-qt-2.3.4-1.mga6.txt | ||
|
Description
William Kenney
2017-05-19 15:15:46 CEST
Assigning to the registered maintainer. CC:
(none) =>
marja11 *** Bug 19600 has been marked as a duplicate of this bug. *** Working on it. CC:
(none) =>
geiger.david68210
Rémi Verschelde
2017-06-02 10:39:15 CEST
Summary:
openshot-qt has migrated to ver v2.3.3 =>
Update openshot-qt to latest upstream version Please test openshot-qt-2.3.4-1.mga6. If it's working properly, I'll have it obsolete the old GTK+ openshot-1.4.3-10.mga6 which was kept as early openshot-qt versions used to be very crash prone. When will it be in the repo or is it working its way through now? Created attachment 9384 [details]
konsole output of openshot-qt-2.3.4-1.mga6.txt
Unhandled exception :(
Started from konsole, attached output.
Looks like what 2.2 spewed out here yesterday...
All other *openshot* were uninstalled previous boot.
64 bit, my production workstation svarten.
Hm, do I remembe you f(In reply to Morgan Leijström from comment #7) > Created attachment 9384 [details] > konsole output of openshot-qt-2.3.4-1.mga6.txt Hm, do I remember you from previous invalid bug reports because you installed Qt 5.7 on your system while Mageia 6's is Qt 5.6? :) You'll always get issues with Qt5 applications if you run a different version than the one they were built for, but in such cases you're on your own. Namely:
app:INFO qt5 version: 5.7.0
app:INFO pyqt5 version: 5.7
Those were never packaged in Cauldron:
http://madb.mageia.org/package/show/source/1/application/0/release/cauldron/name/qtbase5
http://madb.mageia.org/package/show/source/1/application/0/release/cauldron/name/python-qt5
Many thanks to all for a tremendous job to get this one in just under the wire. It will be a shining application in our distro. Ok, it's trickled through to mirrors.kernel.org and my local repo has it now. Update went smoothly, launch was trouble free and a quick construction of a short video using multiple sources went without a hitch. That video exported without a problem and was view-able by VLC. Outstanding. IMO likely folks will migrate to 2.3.4, or whatever it becomes, quickly and away from 1.4.3. 2.x is still an evolving technology but is way better then most, if not all, NLE's on the Linux platform. Thanks for the tests! :) Assuming that it would work for Morgan with Qt 5.6, closing as FIXED. I will obsolete the old openshot-1.4.3 version. Status:
ASSIGNED =>
RESOLVED NLE = (N)on (L)inear (Video) (E)ditor (In reply to Rémi Verschelde from comment #12) > Thanks for the tests! :) Assuming that it would work for Morgan with Qt 5.6, > closing as FIXED. I will obsolete the old openshot-1.4.3 version. If it's possible I'd leave things as they are. 1.4.3 is old reliable and 4.3.2 et al is still a rapidly evolving technology. It takes a lot of using it to make sure everything works. Also I wanted to say that 2.x is similar to 1.x but it's like a completely different application in the way it works. So there's going to be some getting used to time. That is why I suggest that the two reside together in M6 and then obsolete 1.x at M7. There will be no updates to 1.x to support and test. ____Regarding qt versions: Ugh. You have good memory! I searched and found i even opened Bug 20146 - openshot-qt give unhandled exception at launch Forgot that myself...! And as per this and that bugs this is the only program that show a problem. Where do it read that info from? I only have qt 5.6.2 and python-qt 5.6 packages installed, system say... and i dont remember compiling any qt things, but could be part of something else i compiled...? FIXED: I uninstalled all 33 packages python-qt5, (5.6.8), and 33 packages python3-qt5 , reinstalled openshot-qt that pulled in the python3-qt5 it needed. AND NOW openshot-qt launch cleanly, and report correct versions for both qt5 and pyqt5. openshot-qt also launches cleanly on my yesterday fresh installed mga6 i586 Plasma default + updates on thinkpad T43. It needed 549 MB incl dependencies. I have no time to play with it now. Many thanks for your work Rémi! - on this and much else :) Again, sorry to repeat myself, 1.x is like a warm friendly puppy, works and has been around for years. 2.x is the new kid on the block even the documentation is lagging. But it has great promise and everyone may migrate to it very quickly. But keeping 1.x around for one release cycle would be prudent. (In reply to William Kenney from comment #17) > Again, sorry to repeat myself, 1.x is like a warm friendly puppy, works and > has been around for years. 2.x is the new kid on the block even the > documentation is lagging. But it has great promise and everyone may migrate > to it very quickly. But keeping 1.x around for one release cycle would be > prudent. openshot 1.4.3 was released in 2012 and is no longer supported upstream; I think it's best for Mageia users to give the new version a chance (2.0 was released 1.5 years ago, 2.3.4 is getting relatively mature), and best for the upstream developers too. From what I've read, openshot 1.x had many limitations due to the libraries it relied upon, which are alleviated by the new libopenshot and libopenshot-audio used by 2.x. Update test OK from openshot-qt 2.2 on my wifes 64 bit cauldron. (Only verified clean launch so far) I see there is a fork "Libreshot" started from 1.4.3 and still going. It even have a sub-forum hosted @ openshot http://openshotusers.com/forum/viewforum.php?f=29 But of course hard for normal users to install. As much as i have experienced relearning woes on immature spiffy programs and agree with William there, i think it is really time to move to 2.3+ now. Seem not too complicated https://www.youtube.com/watch?v=U7BXKYlrf-g but of course the devil is in the details (and bugs) > I see there is a fork "Libreshot" started from 1.4.3 and still going. It even have a sub-forum hosted @ openshot http://openshotusers.com/forum/viewforum.php?f=29 Hm, I had high hopes when I read that but it seems to be dead already: https://github.com/XXLRay/libreshot/commits/master They weren't able to keep the original commit history, then just a few simple changes and development stopped right after they renamed openshot to libreshot... so little chance to actually see a stable release. I was able to successfully install the M5 version of OpenShot 1.4.3 on M6 and that from the M5 repo. So IMO there's probably no reason to carry OpenShot 1.4.3 into the M6 repo. If you want it you can always go back and get it. |