[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#952901: marked as done (shotcut: Segmentation fault on 4K monitor)



Your message dated Wed, 26 May 2021 08:50:18 +0200
with message-id <cc544a4eed7a47932f1b766d9152b444@phys.ethz.ch>
and subject line shotcut: Segmentation fault on 4K monitor
has caused the Debian Bug report #952901,
regarding shotcut: Segmentation fault on 4K monitor
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
952901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952901
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: shotcut
Version: 20.02.17-2
Severity: important

Dear Maintainer,

When I try to run shotcut on a 4K monitor I get the following logs:

$ LANG=C shotcut
[Info   ] <Application::Application> Starting Shotcut version 20.02.21 
[Info   ] <Application::Application> Linux version 
[Info   ] <Application::Application> number of logical cores = 8 
[Info   ] <Application::Application> locale = QLocale(C, Default, Default) 
[Info   ] <Application::Application> install dir = "/usr/bin" 
[Info   ] <Application::Application> device pixel ratio = 2 
[Debug  ] <ShotcutSettings::log> language "C" 
[Debug  ] <ShotcutSettings::log> deinterlacer "onefield" 
[Debug  ] <ShotcutSettings::log> external monitor "" 
[Debug  ] <ShotcutSettings::log> GPU processing true 
[Debug  ] <ShotcutSettings::log> interpolation "bilinear" 
[Debug  ] <ShotcutSettings::log> video mode "" 
[Debug  ] <ShotcutSettings::log> realtime true 
[Debug  ] <ShotcutSettings::log> audio channels 2 
No appenders associated with category qt.qpa.xcb
[Warning] <> xcb_shm_create_segment() can't be called for size 17178820624, maximumallowed size is 4294967295
zsh: segmentation fault  LANG=C shotcut


And here's an extract of a more verbose log:

$ QT_LOGGING_RULES='*.debug=true' shotcut
...
[Debug  ] <> [ QWidgetWindow(0x55c4be7b5c20, name="QSplashScreenClassWindow") ] creating shared memory 17178820624 bytes for QSize(65534, 65534) depth 32 bits 32
No appenders associated with category qt.qpa.xcb
[Warning] <> xcb_shm_create_segment() can't be called for size 17178820624, maximumallowed size is 4294967295
No appenders associated with category qt.scaling
[Debug  ] <> QBackingStore::beginPaint new backingstore for QWidgetWindow(0x55c4be7b5c20, name="QSplashScreenClassWindow")
No appenders associated with category qt.scaling
[Debug  ] <>   source size QSize(65534, 65534) dpr 1
No appenders associated with category qt.scaling
[Debug  ] <>   destination size QSize(65534, 65534) dpr 2
...


And finally is an extract of the output of xrandr:

$ xrandr -q | head
Screen 0: minimum 8 x 8, current 3840 x 2160, maximum 32767 x 32767
HDMI-0 disconnected primary (normal left inverted right x axis y axis)
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
eDP-1-1 connected 3840x2160+0+0 (normal left inverted right x axis y axis) 346mm x 194mm
   3840x2160     60.00*+  59.98    48.02    59.97  
   3200x1800     59.96    59.94  
   2880x1620     59.96    59.97  
   2560x1600     59.99    59.97  
   2560x1440     59.99    59.99    59.96    59.95  



It looks like Qt tries to allocate some memory for the splash screen,
but with a size that's so large it doesn't really make sens.

Note that the requested amount of memory is exactly 65534*65534*4. And
this size is exactly twice the maximum screen size: 32767*32767. The
screen size is not an exact power of two, so this would be an odd
coincidence.

I don't know if the bug is rather in shotcut or in Qt. Or maybe in the
way they interact. Feel free to reassign this bug report if needs be.


Best regards,
Celelibi

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages shotcut depends on:
ii  libc6                          2.29-10
ii  libgcc-s1                      10-20200222-1
ii  libjs-three                    111+dfsg1-1
ii  libmlt++3                      6.20.0-1
ii  libmlt6                        6.20.0-1
ii  libqt5core5a                   5.12.5+dfsg-8
ii  libqt5gui5                     5.12.5+dfsg-8
ii  libqt5multimedia5              5.12.5-1+b1
ii  libqt5network5                 5.12.5+dfsg-8
ii  libqt5opengl5                  5.12.5+dfsg-8
ii  libqt5qml5                     5.12.5-5
ii  libqt5quick5                   5.12.5-5
ii  libqt5quickwidgets5            5.12.5-5
ii  libqt5sql5                     5.12.5+dfsg-8
ii  libqt5webkit5                  5.212.0~alpha3-7
ii  libqt5websockets5              5.12.5-2+b1
ii  libqt5widgets5                 5.12.5+dfsg-8
ii  libqt5xml5                     5.12.5+dfsg-8
ii  libstdc++6                     10-20200222-1
ii  melt                           6.20.0-1
ii  qml-module-qtgraphicaleffects  5.12.5-2+b1
ii  qml-module-qtqml-models2       5.12.5-5
ii  qml-module-qtquick-controls    5.12.5-1+b1
ii  qml-module-qtquick-controls2   5.12.5+dfsg-2+b1
ii  qml-module-qtquick-dialogs     5.12.5-1+b1
ii  qml-module-qtquick-extras      5.12.5-1+b1
ii  qml-module-qtquick-layouts     5.12.5-5
ii  qml-module-qtquick-window2     5.12.5-5
ii  qml-module-qtquick2            5.12.5-5

shotcut recommends no packages.

shotcut suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Neither me nor upstream can reproduce the bug you reported.
I'm closing this bug for now, if you have tried with the latest version, feel free to reopen it.
--- End Message ---

Reply to: