marlam / bino

3D video player with support for 180°/360° video and Virtual Reality
https://bino3d.org
GNU General Public License v3.0
45 stars 14 forks source link

Can't open a file #5

Closed EtienneAb3d closed 2 years ago

EtienneAb3d commented 3 years ago

Compiled successfully on XUbuntu 20.10 (see #4).

The final binary is starting properly. But, when trying to open a media with "File/OpenFile(s)", I get a problem:

  1. after the short information message, the file selector is opening, but stay transparent (no content, only the window framing). It is really transparent, not simply frozen. If I move it, I see the other windows through it (not simply a static initial copy of them, as it may occur some times when a window is frozen).
  2. one CPU core/thread is running 100%
  3. I can close this transparent Window, and the application seems to still properly be running
  4. points 1 to 4 can be repeated several times

Console output is showing this:

bino: [wrn] Cannot initialize LIRC.
bino: [wrn] LibASS: Shaper: FriBidi 0.19.7 (SIMPLE) HarfBuzz-ng 2.6.4 (COMPLEX)
bino: [wrn] LibASS: Using font provider fontconfig
bino: [wrn] QXcbConnection: XCB error: 3 (BadWindow), sequence: 784, resource id: 13163934, major code: 40 (TranslateCoords), minor code: 0

The last line may be repeated when I'm trying to open a file, but not all the time. Here is a new example:

bino: [wrn] QXcbConnection: XCB error: 3 (BadWindow), sequence: 1046, resource id: 13174010, major code: 40 (TranslateCoords), minor code: 0

Any idea?

PS: "Open device(s)" is working properly. I can see my WebCam playing.

marlam commented 3 years ago

No idea. I cannot reproduce the problem.

Does the bino package in Ubuntu 20.10 work? If yes, then there's something wrong with your specific setup. If no, then maybe report a bug to them.

EtienneAb3d commented 3 years ago

Same problem with the official XUbuntu package. :-/

ansel-hub commented 3 years ago

Hi, same problem in Void Linux, compiled from source. I don't get the (BadWindow) warning message but on trying to open a file from the program a transparent openbox frame can be seen, I can move it around and it displays my desktop, and also the cpu rises.

marlam commented 3 years ago

That's bad news. I still cannot reproduce the error, so I'd like to collect some more information.

What desktop environment / window manager do you use? (I assume Xubuntu uses XFCE.) Maybe this only occurs with certain window managers.

ansel-hub commented 3 years ago

My desktop environment is LXDE and the window manager is Openbox

marlam commented 3 years ago

I still was not able to reproduce this.

Please try bino --log-file=log.txt --log-level=debug, maybe that produces some useful information.

If no messages labeled [dbg] show up in your log file, then your binary does not support debugging output. In that case, it would be helpful if you build from source and configure with --enable-debug.

In any case, messages labeled [inf] should always show up, and maybe that already helps.

beew commented 3 years ago

Similar issue on Ubuntu 20.04 LTS with default gnome desktop (and with Unity as well) On Gnome shell when click open files bino just freezes and turns grey, on Unity it open a transparent window. Same with bino-1.6.6 in repository and bino-1.6.7 compiled from source.

from terminal

bino --log-file=log.txt --log-level=debug

from log.txt

bino: [wrn] Cannot initialize LIRC.
bino: [wrn] LibASS: Shaper: FriBidi 0.19.7 (SIMPLE) HarfBuzz-ng 2.6.4 (COMPLEX)
bino: [wrn] LibASS: Using font provider fontconfig
marlam commented 3 years ago

Am answer on Stackoverflow and a note by Intel suggest to use unset SESSION_MANAGER before running Bino. Does that solve the problem? If so, the Stackoverflow answer suggests that the reason may be stale session files.

beew commented 3 years ago

Am answer on Stackoverflow and a note by Intel suggest to use unset SESSION_MANAGER before running Bino. Does that solve the problem? If so, the Stackoverflow answer suggests that the reason may be stale session files.

Nope, makes no difference and I don't experience this problem with other qt apps (I have many of them)

marlam commented 3 years ago

The three lines above were the complete content of the log file? No further messages, not even if you try to open a file from the command line ($ bino myvideo.mp4)?

beew commented 3 years ago

The three lines above were the complete content of the log file? No further messages, not even if you try to open a file from the command line ($ bino myvideo.mp4)?

There is no error message if open video directly with bino as above and it works (right click video and choose bino from context menu also works) The problem is when you start bino, then try to use open file dialogue to open a video

marlam commented 3 years ago

OK, let's go through the source code. Can you deactivate the Tip window in mainwindow.cpp lines 707-732, e.g. by changing if (_settings... to if (false && _settings...? Does that solve the problem?

marlam commented 2 years ago

Bino is currently being rewritten completely and will be based on Qt 6. This should fix these problems because Bino does not implement its own low level thread fiddling anymore. An initial version of the new Bino is already in the main git repository, you can try it.