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

Bug#935179: qstopmotion: crashes when plazing video and no frame selected



Package: qstopmotion
Version: 2.4.1-1
Severity: important

1. I opened qtopmotion.
2. Because the program crashed during the last session, it asked me if I
wanted to continue my      last session.
3. I answered "No".
4. I started a new project.
5. I confirmed the project description without changing the defaults.
6. I clicked on the tab "project".
7. I imported pictures by clicking the import-button.

If I now click on the "play" button the program crashes with a segmentation
fault.
The output on the terminal is:
--
QObject::connect: No such signal QPushButton::triggered()
QObject::connect: No such signal QPushButton::triggered()
QXcbConnection: XCB error: 3 (BadWindow), sequence: 3857, resource id:
41984629, major code: 40 (TranslateCoords), minor code: 0
Segmentation fault
--

But if I select the first frame before clicking on the play button the program
works.

-- System Information:
Debian Release: 10.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages qstopmotion depends on:
ii  libc6              2.28-10
ii  libgcc1            1:8.3.0-6
ii  libgphoto2-6       2.5.22-3
ii  libgphoto2-port12  2.5.22-3
ii  libqt5core5a       5.11.3+dfsg1-1
ii  libqt5gui5         5.11.3+dfsg1-1
ii  libqt5multimedia5  5.11.3-2
ii  libqt5widgets5     5.11.3+dfsg1-1
ii  libqt5xml5         5.11.3+dfsg1-1
ii  libqwt-qt5-6       6.1.4-1
ii  libstdc++6         8.3.0-6
ii  libv4l-0           1.16.3-3

Versions of packages qstopmotion recommends:
ii  ffmpeg     7:4.1.4-1~deb10u1
ii  v4l-utils  1.16.3-3

qstopmotion suggests no packages.

-- no debconf information


Reply to: