search

NatronGitHub / Natron

Open-source video compositing software. Node-graph based. Similar in functionalities to Adobe After Effects and Nuke by The Foundry.
http://NatronGitHub.github.io
GNU General Public License v2.0
4.63k stars 338 forks source link

Moving (drag) Curve Editor Tab causes Natron to close #536

Open likeka opened 4 years ago

likeka commented 4 years ago

Problem

Just installed 2.3.15 in a fresh Ubuntu. As I'm using a dual monitor setup, started to play around with the tabs and windows. When moving (click and hold) the "Curve Editor" Tab Natron just closes. Focusing to the tab is working (just one click) as expected This happens in Snap Store installation and the installer from the webpage (cool installer btw).

Expected behavior: Tab should be able to be moved.

Actual behavior: Natron closes.

Verbose output from terminal:

Natron Version 2.3.15
Copyright (C) 2013-2018 INRIA and Alexandre Gauthier-Foichat
>>>Use the --help or -h option to print usage.<<<
Qt: Session management error: None of the authentication protocols specified are supported
Info: init.py script not loaded (this is not an error)
Info: initGui.py script not loaded (this is not an error)
X Error:  GLXBadContext
  Request Major code 152 (GLX)
  Request Minor code 6 ()
  Error Serial #9688
  Current Serial #9687

Steps to Reproduce

  1. Open Natron
  2. Click and hold the curve editor tab
  3. Move your mouse

You may submit a link to any screenshots/videos that can be used to understand how to reproduce the issue.

Versions

This bug was mentioned Here

rodlie commented 4 years ago

Had similar issue in the past, this was resolved by upgrading/downgrading the graphics driver (Mesa). What kind of graphics card and driver are you using?

likeka commented 4 years ago

Hi rodlie, my video card is an Intel HD Graphics 4000

lspci output: VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) DeviceName: 64 Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 35 Memory at d4000000 (64-bit, non-prefetchable) [size=4M] Memory at c0000000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features Kernel driver in use: i915 Kernel modules: i915

Let me know if this helps.

rodlie commented 4 years ago

I'm able to replicate with an Intel HD Graphics 3000 on Ubuntu 20.04. Note that I am not able to replicate on a different distro, so it's seems it's the Mesa stack on Ubuntu 20.04 that may be a bit "touchy".

likeka commented 4 years ago

So, probably not a Natron issue itself. I know the card is old and also not the best (or even close) for this type of software, so I guess this can be marked as not to be fixed as long as it remains in Ubuntu and those old cards. Thanks for the comments. Let me know if I can help in any way.

rodlie commented 4 years ago

The card is more than good enough, One of my workstations uses Intel HD Graphics 4600 and works great with Natron.

likeka commented 4 years ago

Cool. I'll see what drivers can I test and update tomorrow. Regards.

rodlie commented 4 years ago

After some further testing it seems this issue is a bug and just looked similar to an older issue we had. I'm currently testing Ubuntu with intel/amd and moving the curve editor will end the program no matter what.

rodlie commented 3 years ago

Finally got a Linux workstation up-and-running (been on an Intel GPU laptop since July), on CentOS 7 with the NVIDIA driver everything works just fine. Seems like this bug only triggers (on) Mesa drivers.

rodlie commented 3 years ago

Probably the same. The only combo where the Curve Editor works perfectly on Linux is with RHEL/CentOS 7.x and NVIDIA drivers (might need to be specific there as-well, 460 works), everything else (after v7) fails.

I have tried debugging this in the past, but since this is a crash in X.org, it hard to pinpoint exactly what the problem is (at least for me, has something to do with the paint function in the curve editor I believe).

rhysday commented 3 years ago

Well it 100% triggers when dragging on the tab to pop out the curve editor window. This is the error msg I will put it here for reference:

X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 7370 Current serial number in output stream: 7371

rodlie commented 2 years ago

Works in RB-2.5 with Qt5 running on Ubuntu 22.04 (Wayland) with Intel UHD Graphics 620.