Created attachment 168138 [details] gdbtrace.log Description: go to Insert > Audio or Video > select the video file and it crashes immediately. The file plays correctly in video players (vlc. totam). It crash with any video I tested. Also, when I try to edit a slide with video as soon as the slide appears on screen (in them main panel, slide panel, or the slide sorter) Impress crashes Steps to Reproduce: 1.Open a blank presentation 2.Insert > Audio or Video 3. select video file 4. crashes immediately. Actual Results: Crash Expected Results: Video inserted into presentation Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.0.3.1 Build ID: 00(Build:1) CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: en-US (en_IL); UI: en-US Ubuntu package version: 1:7.0.3-0ubuntu0.20.10.1 Calc: threaded
Created attachment 168139 [details] strace.log
Created attachment 168161 [details] bt with debug symbols On pc Debian x86-64 with master sources updated today, I don't a crash but an assertion (I use enable-dbgutil). Since bt of assertion is completely different than your bt, I don't think we can consider I confirm the bugtracker.
Julien Nabet committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f4e496af66bc6a779f600158cc42b986d654f143 Related tdf#138888: fix assertion on avmedia/MediaControlBase It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
@Julien: I wonder about this commit to be honest. The initial report was against 7.0.3 but your commit says "Regression from: commit 36b3b357fe2a882db6a5f5a006239e16200fb847 [...]" which isn't yet in 7.0.x. (only in master and -7-1) Asking myself whether I need to backport a fix to 7.0.4 which will definitely be what will be in the next Debian release or not....
(In reply to Rene Engelhard from comment #4) > @Julien: I wonder about this commit to be honest. > > ... > Asking myself whether I need to backport a fix to 7.0.4 which will > definitely be what will be in the next Debian release or not.... The commit doesn't fix the bug, it just fixes the assertion, see https://bugs.documentfoundation.org/show_bug.cgi?id=138888#c2. That's why I put "Related tdf#138888", not "tdf#138888" Let's remove target to make it even more explicit.
I see, thanks
Do you have any idea how I can solve the problem? the same LO version on other computer works perfectly.
(In reply to Gilad Ravid from comment #7) > Do you have any idea how I can solve the problem? the same LO version on > other computer works perfectly. What's the distrib of the other pc? Ubuntu 20.10 too? What's the graphic/chipset card also? It seems the pc you got the crash has Intel 915 graphic card/chipset. Perhaps a graphic driver pb? It could also be a missing gstream lib on your system. Compare gstream libs between both pcs (including versions). To install LO, did you use Ubuntu repo (ppa or not) or did you download LO from TDF website?
(In reply to Julien Nabet from comment #8) > (In reply to Gilad Ravid from comment #7) The other computer is a desktop with Nvidia card. both installed with ubuntu 20.10 and uses the LO that comes with the distribution. the desktop has some i386 gstreamer libs, installed them on the laptop did not change the behavior.
(In reply to Gilad Ravid from comment #9) > (In reply to Julien Nabet from comment #8) > > (In reply to Gilad Ravid from comment #7) > > The other computer is a desktop with Nvidia card. both installed with ubuntu > 20.10 and uses the LO that comes with the distribution. the desktop has some > i386 gstreamer libs, installed them on the laptop did not change the > behavior. Is your graphic card driver up-to-date too? You can try this: https://wiki.documentfoundation.org/QA/FirstSteps but if you still reproduce this, the only next step I see to investigate is to build sources with symbols+debug enabled https://wiki.documentfoundation.org/Development/BuildingOnLinux Now you must know that the build process make take some hours depending on your config.
This is open for a long time. If I insert video attachment 158818 [details] in LO 7.2+ in Linux Mint Gtk3, I see a full screen image from that file and menu, not normall Impress UI. I can play video though, no crash in general. So not sure should it be confirmed with all the differences or not. Reported, please test with the same video and give example video, even better from some of the existing bugs.
*** Bug 139234 has been marked as a duplicate of this bug. ***
No repro in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: c5ca46e75e28ba4245d8544ca53c71fea87d1bbd CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: ru-RU (ru_RU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-07-20_00:22:42 Calc: threaded Please update your office to the latest version and try again.
Same issue, Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 12; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Ubuntu package version: 1:7.2.1-0ubuntu3
Even with a gif on a slide I get: soffice.bin crashed with SIGABRT. Ubuntu 21.10. And even when the slide is not presenting - just trying to get to the slide triggers a crash.
Whoever tests this, should not conclude with new LO that bug is gone, rather it should be first reproduced with older LO, versions here. This is not general bug, but something distro or card/driver specific.
Gilad, Kara, Petr, please check whether you have gstreamer, in Ubuntu it's gstreamer1.0-gtk3 I set Needinfo as this is not a general reproducible bug.
Interesting. When I install the FLATPAK of 7.3.2.2 no issues. When I install the Ubuntu DEBs of 7.3.2.2 - I see the crashes and GUI freeze.
No response here if gstreamer1.0-gtk3 is installed in Ubuntu. We can only conclude it's not general LO ie NotOurBug, rather Ubuntu/Debian bug. If someone disagrees, please explain.