I wasn’t able to resolve the original issue I was having but I did manage to get the program to run just fine from a live DVD (though granted, running on a different computer – my 6 or 7 year old laptop). As such, I thought that I’d leave some feedback for others. After becoming frustrated with using another Linux NLE when a clip on my timeline just suddenly dissappeared (possibly due to something I did wrong), I decided to go the next level in getting Shotcut to run. Guessing that it doesn’t like the Intel graphics on my HTPC computer, I decided to try Shotcut using the exact same O/S (Linux Mint 18, MATE edition) except running on my old laptop and from a Live DVD. I’m happy to say that although Shotcut wouldn’t run from the main menu (something I think I can easily fix), the script itself did run from the terminal. And BTW, I installed Shotcut from the “unofficial” PPA… My immediate motivation to find a good video editing solution that I can use in Linux is that I wanted to create a short “Emergency Broadcast System” video to prank my wife into thinking that we’re about to get nuked, lol. So once I got Shotcut up and running from a Live DVD on my old laptop, it worked flawlessly, and just as important, intuitively. Now to ready myself for a week or more of sleeping on the couch… Really exceptional work, guys, I’m a convert, whether I have to boot from a live media or not! 
I have the same problem since the November’s release.
I agree with Dan it is probably a Qt5 problem.
For my side I am using Linux Mint 17.1 with Xfce, I was waiting for an distrib update but apparently the problem is not fixed 
.
I tryed the “export QT_DEVICE_PIXEL_RATIO=1” before launch but I still have the same issue.
I have to check the other way Dan spoke about.
Anyway even with old release, … shotcut is a very nice and easy solution
To add to the discussion…
If it helps - I’m using Shotcut 17.01.02 on Linux Mint 18.1, with Cinnamon and xserver-xorg-video nouveau (rather than the Nvidia 340 (recommend) ) and all seems to work well
Hardware: Sony Vaio Laptop, Intel i5, 4g ram, dual boot within Windows 7 as alternative.
Good luck with yours
I confirm it runs well with Mint 18.1 Cinnamon 64bit and the nvidia drivers in my case. It is a huge performance difference compared to the intel card.
I just updated to Mint 18.1 Xfce with Nvidia 960 and I still have the problem.
I already tried to used the xorg-video nouveau solution but in my case, I do not know why the resolution fall down to an unusable level.
For the moment I am trying to compile from the source but in my system the Qt C++11 libraries are missing, I guess the Qt version of Mint Serena Xfce is not the good one
BTW I’m using the Nvidia 375.26 driver from the ppa:graphics-drivers/ppa, but I am pretty sure it should run on the one provided by the main repository.
Hi Nick_name,
I just upgrade to Nvidia 375.26 but result is the same.
This behavior is weird. I am also thinking the fact I use a Xeon, perhaps some graphics instruction are not available ?
Sorry, I wish I could be of help, but I don’t know how. Maybe you could paste what’s shown when you run shotcut from the terminal?
Hi Nick_name,
At the beginning of this thread you have the output of the shotcut command from a console.
This is the last lines Debug message :
[Debug ] EncodeDock::EncodeDock(QWidget*) end
[Debug ] JobsDock::JobsDock(QWidget*) begin
[Debug ] JobsDock::JobsDock(QWidget*) end
[Debug ] MainWindow::readWindowSettings begin
[Warning] <> QWidget::setMinimumSize: (propertiesDock/QDockWidget) Negative sizes (300,-1) are not possible
[Warning] <> QWidget::setMaximumSize: (propertiesDock/QDockWidget) Negative sizes (524287,-1) are not possible
[Warning] <> QWidget::setMinimumSize: (PlaylistDock/PlaylistDock) Negative sizes (36,-1) are not possible
[Warning] <> QWidget::setMaximumSize: (PlaylistDock/PlaylistDock) Negative sizes (524287,-1) are not possible
[Warning] <> QWidget::setMinimumSize: (FiltersDock/FiltersDock) Negative sizes (300,-1) are not possible
[Warning] <> QWidget::setMaximumSize: (FiltersDock/FiltersDock) Negative sizes (524287,-1) are not possible
[Warning] <> QWidget::setMinimumSize: (AudioPeakMeterDock/ScopeDock) Negative sizes (0,-1) are not possible
[Warning] <> QWidget::setMaximumSize: (AudioPeakMeterDock/ScopeDock) Negative sizes (524287,-1) are not possible
[Warning] <> QWidget::setMinimumSize: (JobsDock/JobsDock) Negative sizes (12,-1) are not possible
[Warning] <> QWidget::setMaximumSize: (JobsDock/JobsDock) Negative sizes (524287,-1) are not possible
[Warning] <> QWidget::setMinimumSize: (AudioWaveformDock/ScopeDock) Negative sizes (0,-1) are not possible
[Warning] <> QWidget::setMaximumSize: (AudioWaveformDock/ScopeDock) Negative sizes (524287,-1) are not possible
[Debug ] MainWindow::readWindowSettings end
[Debug ] LeapNetworkListener::start begin
[Debug ] MainWindow::MainWindow() end
[Warning] <> QWidget::setMinimumSize: (MainWindow/MainWindow) The largest allowed size is (16777215,16777215)
[Warning] <> QWidget::setMinimumSize: (MainWindow/MainWindow) The largest allowed size is (16777215,16777215)
[Debug ] Database::run Database version is 1
[Warning] <> QPainter::begin: Paint device returned engine == 0, type: 3
[Warning] <> QPainter::setPen: Painter not active
[Warning] <> QPainter::setFont: Painter not active
[Warning] <> QPainter:
Painter not active, aborted
[Warning] <> QPainter::begin: Paint device returned engine == 0, type: 3
[Warning] <> QPainter::setRenderHint: Painter must be active to set rendering hints
[Warning] <> QPainter::setPen: Painter not active
[Warning] <> QPainter: Painter not active, aborted
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
[Debug ] FiltersDock::resetQview begin
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete attachment.
[Debug ] <> QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
[Debug ] Mlt::GLWidget::initializeGL begin
[Info ] Mlt::GLWidget::initializeGL OpenGL vendor “NVIDIA Corporation”
[Info ] Mlt::GLWidget::initializeGL OpenGL renderer “GeForce GTX 960/PCIe/SSE2”
[Info ] Mlt::GLWidget::initializeGL OpenGL threaded? true
[Info ] Mlt::GLWidget::initializeGL OpenGL ES? false
[Debug ] Mlt::GLWidget::initializeGL end
Floating point exception
I run now the 378.09 Nvidia driver.
I you have any idea ?
Thank you for help 
Floating point exception seems to be the show stopper. You also have this other thread
Not sure what binary you are starting but try running
/usr/local/Shotcut/Shotcut.app/bin/shotcut
I always get a segfault if I run
/usr/local/Shotcut/Shotcut.app/shotcut
THAT IS INCORRECT AND NOT SUPPORTED.
From the Shotcut FAQ page:
Shotcut will not start on Linux…
Some file managers do not like the launcher icon provided with the
binary download from this site. The launcher icon was tested
successfully on GNOME Nautilus and KDE Dolphin.
open a terminal/console window cd to the location where you have extracted Shotcutenter Shotcut.app/shotcut
Please do not try to run bin/shotcut; always use the wrapper script in the Shotcut.app
folder! If it still does not start, then it should report that some
libraries could not be loaded.
Understood. I may have been mixing up my memories on this one - I was sure I had a machine where launching the correct launch ended in a segfault but it worked if I ran the binary directly. Unfortunately I don’t have that machine any more to double check.
Hi Realflash,
I tried both the shell script /usr/local/Shotcut/Shotcut.app/shotcut and the binary in bin dir for both I source the file source-me, … no success.
But i instead of Xfce I run Kde, it is ok, shotcut 1702 is ok. Probably the graphic environment of Xfce is not up to date enough for shotcut, especialy the Qt support.
Thank you for taking care of my post.
Just for info, with Cinnamon it does not run
All of my successful tests were using Cinnamon desktop. Your mileage may vary.
I think it fits in here:
Running Linux Mint 18.1 with Cinnamon
Can run Shotcut, but everytime the Screensaver starts, the Shotcuts GUI “disappears”; any rendering-process continues running though…
Between Mint/Cinnamon and Shotcut, there seems to be something “not playing well together”… (can’t supply a debug-log as the rendering-process is still going (and as it only runs on one core on my system, i’ll wait the 3 hours - maybe the vid is finished after it (if not, i’ll have to restart tomorrow… (any hint to start shotcut with a higher verbose (getting a log-file written would be great)?)
If I use KDE, shotcut run perfectly, then I switch to kde for my Shotcut session .
Hi Dan,
for information, the status of the problem I had, shotcut was runing only under Kde, change.
I just purchase a new monitor and I switched from 1080p resolution to 4K resolution.
I try to launch shotcut and … miracle it is runing :o)
If this behavior give you any idea about this weird issue.
Anyway thank you very much for your nice work.