Package Details: bluejeans 2.33.2-1

Git Clone URL: https://aur.archlinux.org/bluejeans.git (read-only, click to copy)
Package Base: bluejeans
Description: BlueJeans desktop app for video calls
Upstream URL: https://www.bluejeans.com
Keywords: bluejeans videocall voip
Licenses: proprietary
Submitter: delx
Maintainer: guzzisti
Last Packager: guzzisti
Votes: 31
Popularity: 0.000000
First Submitted: 2015-08-12 11:48 (UTC)
Last Updated: 2024-01-27 18:54 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

mundo03 commented on 2020-04-23 00:10 (UTC) (edited on 2020-04-27 16:46 (UTC) by mundo03)

updated to 2.1.2 and I am not getting the problem after restart and after suspend,hibernating or locking session.

edit: Happened again

jat255 commented on 2020-04-17 17:45 (UTC)

Following up (in a new comment to trigger alerts in case anyone is interested)... It seems as though the segfaults happen after each day, which for me involves putting my machine to sleep at the end of the day and waking it up the next. A reboot (while annoying) seems to fix it reliably for the day.

I have tried suspending and resuming to see if I can cause the segfaults on-demand, but it doesn't seem to work, so I'm not sure what triggers the segfaults to start.

jfchevrette commented on 2020-04-16 20:03 (UTC)

I just realized I am not getting segfaults anymore either. I didn't do anything special except that my system is kept up-to-date daily

ElijahLynn commented on 2020-04-16 01:49 (UTC)

I just installed this and got the segfaults, then I tried updating just some glib packages and borked by system (libffi.so.7 not found) so I symlinked so.6 and finally got networking up then ran a proper full upgrade and now I am back and this package isn't segfaulting anymore.

So, run a full system upgrade (yay) and it might work out with the new glib packages.

tobias_de commented on 2020-04-13 17:13 (UTC) (edited on 2020-04-13 17:16 (UTC) by tobias_de)

Also segfaults here. I ran it with gdb to get a backtrace, and it does indeed look like some glibc incompatibility? https://pastebin.com/RJmPvq8t

jat255 commented on 2020-04-09 21:25 (UTC) (edited on 2020-04-16 18:43 (UTC) by jat255)

I should add that I attended a couple meetings today using the desktop app that worked fine and did not segfault. Obviously, no change to the app, but I have done recent system upgrades, so perhaps one of the system library updates fixed this (for the time being, at least)?

EDIT: I have no idea what's going on, as I'm back to segfaulting today (2020-04-14) and there have been no changes to the application or any of the glibc libraries

EDIT 2: And after a reboot today, it all works fine. I'm extraordinarily confused.

EDIT 3: Daily update (4/16/2020), no reboot, and segfaulting again. I haven't figured out what makes it go bad reproducibly, but it's not updates, since I haven't updated since it was working yesterday. After a reboot, it's working again. So maybe other people can try just rebooting to see if that gets it to work?

eigenrick commented on 2020-04-09 20:43 (UTC)

Here is some likely context:

https://github.com/electron/electron/issues/13972

https://bugs.archlinux.org/task/59550

It looks like there was a bug in how electron used glibc. I think our only option at this point is to patch glibc in the way they did for the fedora copr.

kensmith commented on 2020-04-02 19:50 (UTC)

This is a bog standard bug in a call to strlen from that fiber client library. /tmp/bluejeans-v2\ Crashes contains some data that might be useful to a Bluejeans engineer. If someone from Bluejeans wants to reach out, I'd be happy to send them a crash file. Ping here with contact info to submit the crashes. Everyone is experiencing the exact same problem so you would likely only need on of them from one of us.

markuspeloquin commented on 2020-04-02 19:26 (UTC) (edited on 2020-04-02 19:43 (UTC) by markuspeloquin)

I'm actually using Fedora 31 and I'm getting the exact output as @jat255. When I first installed & used BlueJeans just two days ago (installed 2020-03-31T18:02:59Z), it worked. It has not updated since. I tried rm -rf ~/.config/bluejeans-v2 but it didn't help.

Update The latest Glibc symbol I see in any executable or '*.so*' file in /opt/BlueJeans is clock_gettime@@GLIBC_2.17, but I have Glibc 2.30. I also have no '*.so*' file on my system that has updated since BlueJeans worked.

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »