Arch Linux User Repository

Hi @bunnybooboo, VidyoDesktop broke with an update to qt a few months ago. Unfortunately Vidyo stopped supporting Vidyo Desktop on Linux a long time ago and so I doubt we will see any attempts to fix this problem. The current version (3.6.3_017) was released back in March 2016. Since it is closed source the only way that we have found to run it succesfully is by using a systemtray application.

If you run trayer (which is installed as a dependency) before running Vidyo Desktop, Vidyo works without any issues. This is unfortunate but it is an upstream issue.

After a successful build I get the following output:

libpng warning: iCCP: known incorrect sRGB profile

QPainter::begin: Widget painting can only begin as a result of a paintEvent

Object::connect: No such slot

VDCallWindow::OnHideMuteToolbarsWhenWindowDeactivate() in ../source/VDController.cpp:3847

Object::connect: (receiver name: 'VDCallWindow')

got fs = ext 4

supports ext4 get_tag_value-54-50-56-55-101-56

QObject: Cannot create children for a parent that is in a different thread. (Parent is VDVidyoClientPlugIn(0x6748ae0), parent's thread is VDVidyoClientPlugIn(0x6748ae0), current thread is QThread(0x6255af0)

QObject: Cannot create children for a parent that is in a different thread. (Parent is VDVidyoClientPlugIn(0x6748ae0), parent's thread is VDVidyoClientPlugIn(0x6748ae0), current thread is QThread(0x6255af0)

QObject: Cannot create children for a parent that is in a different thread. (Parent is VDVidyoClientPlugIn(0x6748ae0), parent's thread is VDVidyoClientPlugIn(0x6748ae0), current thread is QThread(0x6255af0)

QObject: Cannot create children for a parent that is in a different thread. (Parent is VDVidyoClientPlugIn(0x6748ae0), parent's thread is VDVidyoClientPlugIn(0x6748ae0), current thread is QThread(0x6255af0) Object::connect: No such signal VDController::StartDownload(bool) in ../source/VDController.cpp:753

QObject::moveToThread: Cannot move objects with a parent No systemtrayicon available

QThread::wait: Thread tried to wait on itself

/bin/VidyoDesktop: line 6: 22530 Segmentation fault (core dumped) /opt/vidyo/VidyoDesktop/$EXEC $option $audioflag $@

@seadanda thanks for your help. Unfortunately, reinstalling Vidyo from scratch and cleaning the Plasma cache didn't work. While experimenting, I found that I don't get any segfault in double screen because xembedsniproxy is automatically started by Plasma in my system; if I kill it then I have to rely on the trayer workaround (or any other xembed systray). However in single screen the crash happens in any case, and before the crash that happens on dual screen without any active xembed systray. Sadly I found no solution on the web since all of the segfault reports seems to be due to missing xembed systray. At this point I give up, since fortunately at work I always have a dual monitor setup. Maybe I'll try another DE when I will have time.

@snack in terms of Vidyo:

# pacman -Rn vidyodesktop

$ rm -r ~/.vidyo

removes everything related to vidyo desktop on your machine. You won't have to rebuild any dependencies when you reinstall.

However I think the issue is more likely to be with your Plasma Desktop config. Check out https://wiki.archlinux.org/index.php/KDE#Troubleshooting - maybe clearing the cache is what you want to do. Just make sure to be prepared to lose any modifications you've made from the default unless you back up.

Failing that, I think it could be one for the Arch forums as I have zero experience with the Plasma Desktop. Good luck!

@seadanda I had to prepare a new installation on another machine, and on that machine Vidyo works also in single screen with Plasma desktop; so I can confirm your findings. I think that something is screwed on my main system. How can I completely wipe out any config file so to mimick a fresh installation?

@snack Today I made a fresh arch install in a VM, installed the plasma group and vidyodesktop worked out of the box (didn't have to start trayer first) for both a single-monitor and dual-monitor setup. I don't know what is going wrong for you I'm afraid!

Very weird that you run into problems for one monitor but not two. It could be a setting for your systray in plasma that Vidyo doesn't like. Might be worth fiddling with different settings to try to see if it helps.

Sorry for the delay - been busy with work.

@seadanda This is what happens when I launch trayer and then Vidyo in a single-monitor setup:

$ trayer

another systray already running

Then in another terminal:

$ VidyoDesktop

libpng warning: iCCP: known incorrect sRGB profile

QPainter::begin: Widget painting can only begin as a result of a paintEvent

Object::connect: No such slot VDCallWindow::OnHideMuteToolbarsWhenWindowDeactivate() in ../source/VDController.cpp:3847

Object::connect: (receiver name: 'VDCallWindow')

/usr/bin/VidyoDesktop: line 6: 6269 Segmentation fault (core dumped) /opt/vidyo/VidyoDesktop/$EXEC $option $audioflag $@

=======================

Same but with dual-monitor:

$ trayer

another systray already running

Then in another terminal:

$ VidyoDesktop

libpng warning: iCCP: known incorrect sRGB profile

QPainter::begin: Widget painting can only begin as a result of a paintEvent

Object::connect: No such slot VDCallWindow::OnHideMuteToolbarsWhenWindowDeactivate() in ../source/VDController.cpp:3847

Object::connect: (receiver name: 'VDCallWindow')

got fs = ext 4

supports ext4 get_tag_value-98-54-101-54-49-54

QObject: Cannot create children for a parent that is in a different thread.

(Parent is VDVidyoClientPlugIn(0x300ea70), parent's thread is VDVidyoClientPlugIn(0x300ea70), current thread is QThread(0x2ad53f0)

QObject: Cannot create children for a parent that is in a different thread.

(Parent is VDVidyoClientPlugIn(0x300ea70), parent's thread is VDVidyoClientPlugIn(0x300ea70), current thread is QThread(0x2ad53f0)

QObject: Cannot create children for a parent that is in a different thread.

(Parent is VDVidyoClientPlugIn(0x300ea70), parent's thread is VDVidyoClientPlugIn(0x300ea70), current thread is QThread(0x2ad53f0)

QObject: Cannot create children for a parent that is in a different thread.

(Parent is VDVidyoClientPlugIn(0x300ea70), parent's thread is VDVidyoClientPlugIn(0x300ea70), current thread is QThread(0x2ad53f0)

Object::connect: No such signal VDController::StartDownload(bool) in ../source/VDController.cpp:753

QObject::moveToThread: Cannot move objects with a parent

Object::connect: No such slot VDFavoritesListViewContext::OnContactRoomsFeetched(VDRequestResponseRoomList,VDContactsModel) in ../source/VDFavoritesWindow.cpp:102

Object::connect: (sender name: 'VDFavoritesWindow')

QObject: shared QObject was deleted directly. The program is malformed and may crash.

QObject: shared QObject was deleted directly. The program is malformed and may crash.

=======================

Note that I'm using Plasma desktop, and that launching trayer results in the warning message above and the disappearance of the Plasma panel. But It does not affect the behavior of Vidyo at all. I can provide versions of installed packages if it's needed, let me know.

@snack OK well I've tested the trayer fix on both one- and two-monitor setups running dwm and the same for GNOME3 (both X11 and Wayland). For all setups VidyoDesktop did not run unless trayer was launched first (all segfault errors) but worked without issues with trayer. Could you post the error message and I'll look into it.

@greyltc I found the same, two monitors doesn't work unless I run trayer first.

I generally run vidyo with two monitors and launching trayer before launching vidyo is the only way I can get it to work. Haven't done any testing with only one monitor.

@seadanda unfortunately the trayer trick does not fix my single-monitor segfault. I use a Plasma desktop, and starting trayer I get "another systray already running", then launching VidyoDesktop I get the segfault. Fortunately it still works when in dual-monitor.