BeeBeep (LAN Messenger) does not work after installation
-
- Posts: 75
- Joined: Sat Dec 21, 2019 4:28 pm
BeeBeep (LAN Messenger) does not work after installation
Hello,
I want to replace a Windows machine by Linux MX and therefore need an internal, cross-platform LAN-messenger replacing Realpopup (Windows only).
I can install BeeBeep easily on Linux MX 19.3 64bit (package for Ubuntu), but it does not start after installation:
https://www.beebeep.net/
Could somebody fix that, please? Perhaps including BeeBeep in the MX repository? Thanks! Michael
I want to replace a Windows machine by Linux MX and therefore need an internal, cross-platform LAN-messenger replacing Realpopup (Windows only).
I can install BeeBeep easily on Linux MX 19.3 64bit (package for Ubuntu), but it does not start after installation:
https://www.beebeep.net/
Could somebody fix that, please? Perhaps including BeeBeep in the MX repository? Thanks! Michael
Re: BeeBeep (LAN Messenger) does not work after installation
Do you get any error messages? Did you check here? https://www.beebeep.net/help#install I was having problems to start it too, I solved it by installing these pkgsMichael_Logies wrote: Mon Feb 22, 2021 3:52 pm Hello,
I want to replace a Windows machine by Linux MX and therefore need an internal, cross-platform LAN-messenger replacing Realpopup (Windows only).
I can install BeeBeep easily on Linux MX 19.3 64bit (package for Ubuntu), but it does not start after installation:
https://www.beebeep.net/
Could somebody fix that, please? Perhaps including BeeBeep in the MX repository? Thanks! Michael
Code: Select all
sudo apt-get install libxcb-screensaver0 libxcb-screensaver0-dev
hope this helps!

Without each other's help there ain't no hope for us 

-
- Posts: 75
- Joined: Sat Dec 21, 2019 4:28 pm
Re: BeeBeep (LAN Messenger) does not work after installation
@Moltke Thanks for your fast reply! The packages seem to be complete on my german Linux MX, I don`t get error messages and no further packages are installed if I repeat installation. But the folder "/home/your-account/.local/share/MarcoMastroddiSW/BeeBEEP/" which is described on the install help page of BeeBeep did not come into existence.
Re: BeeBeep (LAN Messenger) does not work after installation
MX doesn't support BeepBeep, you'll have to contact its developers if it still doesn't work after you've read all of its support documentation on that website you linked. They do offer a portable version in that tarball download. Just downloaded it, extract it, right-click on the binary executable file, click Properties, check the box to allow it to run as a program, then run it. If that also doesn't work, see what I said above.
To request new or updated software packages be added to the MX Repositories, please read these instructions first, then post your request in the appropriate Package Requests/Status subforum for your version of MX: 19, 17/18 or 15/16.
To request new or updated software packages be added to the MX Repositories, please read these instructions first, then post your request in the appropriate Package Requests/Status subforum for your version of MX: 19, 17/18 or 15/16.
Please read the Forum Rules, How To Ask For Help, How to Break Your System and Don't Break Debian. Always include your full Quick System Info (QSI) with each and every new help request.
-
- Posts: 75
- Joined: Sat Dec 21, 2019 4:28 pm
Re: BeeBeep (LAN Messenger) does not work after installation
@JayM Thanks for your hints! I`m on a fresh install of Linux MX 19.3 (USB-SSD), because my internal Windows SSD broke yesterday. On this machine I only need a RDP-Client (Remmina) and a LAN-Messenger (BeeBeep seems to be the best cross-platform choice so far, tested many in the past).
I unpacked the tar-file for BeeBeep und did the dependency check described there. libqt4-core and libqt4-gui are missing, even after adding more repositories to Synaptic. Is this a technical limitation of Linux MX oder an ideological thing? Here is a user statistics for BeeBeep by linux distribution. All kinds of distributions, but Linux MX is missing: https://snapcraft.io/beebeep
Thanks!
I unpacked the tar-file for BeeBeep und did the dependency check described there. libqt4-core and libqt4-gui are missing, even after adding more repositories to Synaptic. Is this a technical limitation of Linux MX oder an ideological thing? Here is a user statistics for BeeBeep by linux distribution. All kinds of distributions, but Linux MX is missing: https://snapcraft.io/beebeep
Thanks!
Re: BeeBeep (LAN Messenger) does not work after installation
@Michael_Logies
those are snapcraft stats for the app by distro ...
snaps require systemd boot and mx boots with sysvinit by default
you can install snaps and then run the app if you boot with systemd .... (as far as i am aware ...which is not very far)
those are snapcraft stats for the app by distro ...
snaps require systemd boot and mx boots with sysvinit by default
you can install snaps and then run the app if you boot with systemd .... (as far as i am aware ...which is not very far)
Re: BeeBeep (LAN Messenger) does not work after installation
Have you tried it? Clearly you haven't because MX does support beebeep, why wouldn't it? Debian does. I use it and it works. I should mention however, that newest and latest, 5.8.4-1 doesn't, it complains about `Qt_5.12' not found but previous one, 5.8.2-1 does just fine. So yes, MX does support BeeBeep. @Michael_Logies probably installed the one which doesn't work, so all he needs to do is download the one that does https://sourceforge.net/projects/beebee ... b/download untill that dependency error gets resolved by its developer.JayM wrote: Mon Feb 22, 2021 8:11 pm MX doesn't support BeepBeep, you'll have to contact its developers if it still doesn't work after you've read all of its support documentation on that website you linked.

Without each other's help there ain't no hope for us 

-
- Posts: 3602
- Joined: Tue Jun 14, 2016 2:02 pm
Re: BeeBeep (LAN Messenger) does not work after installation
First, Everybody just chill a bit here.
Lets make some things a bit more clear and laid out since there is some confusion. Especially around the term "support".
Potential for installation and usability does not equal "support". Linux Distros do not "support" applications just because it can be installed in some way shape or form.
Linux Distros support applications by creating and "maintaining" a package of the application from start to finish (dependency resolution, testing, troubleshooting, and updating). A "Package Maintainer" they are about as close to official "support" as you'll get (besides the actual application developer) because they volunteer to take responsibility of the said application package for the Distro. Users and in our case Qualified Guides also help "support" by testing and troubleshooting.
Now to the Facts:
BeeBEEP provides (supports) several Linux installs:
- Ubuntu 18.04 via a .deb,
- Snaps (via an unofficial snap)
- "portable" packages via a tarball
There are only 10 packaged versions of BeeBEEP in repositories, looks like maybe 5 total actual Distros "supporting" BeeBEEP.
https://repology.org/project/beebeep/versions
The link above shows "created" packages for repositories, these may or may not be officially supported and they may not be maintained current.
Packaged versions does not specifically entail that something is really "supported" or not, or if it can actually be installed or not.
For example: Chocolatey, winget, freshcode aren't Distros.
Note the fact that Debian is NOT on that list at the link, therefore Debian does NOT maintain (support) a package of BeeBEEP at this time.
The Snap can be (should) run on MX Linux as MX does "support" Snaps, but as already stated, you have too boot using systemd.
There is no technical or ideological mumbo jumbo about any of that, its just a fact.
The linked page to the Snap install statistics has nothing to do with Distros "supporting" BeeBEEP or not.
This page simply lists the Distros "used by" users who have it installed via Snap. NOT Distros supporting BeeBEEP via Snap.
Again, go back to the Repology link to see which distros created (possibly maintain (support) current) packages in their repos.
JayM is right, we don't "support" (yet) BeeBEEP directly. That doesn't mean you can't install it and we won't help you with it though.
And that doesn't mean we can't maintain (support) a package of BeeBEEP in the future.
Now to the good stuff:
directly at @Michael_Logies
The process to get "support" for an application "in MX" is a Package Request as Jay stated, but do not worry about doing one, I'm acknowledging the request right now.
JayM said the Portable package works and it seems some hacky workarounds will allow the .deb package to work.
Honestly I would use the Portable package as it comes from (supported?) by the actual developer. Trying to cram a cube through a circle hole with the .deb is not going to work well long term. And you should NOT be enabling repos to do such cramming unless you know exactly what you are doing. See JayM's or my signature blocks about breaking stuffs.
With all that out of the way, like I said your request to get BeeBEEP packaged and easily installable in MX Linux is acknowledged.
Its going to be awhile (few weeks) before I can give you a status update, unless someone else decides to tackle it. But again in the meantime I would try the Portable package, if it works then use that, if not then post back here for assistance on that.
@Moltke appreciate you're help with this, really. But please do not state that MX "supports" an application just because it can be installed one way or another. "Installs and works under/with" and "Supports" are two different things. Neither MX nor Debian directly "support" BeeBEEP.
It can confuse new users. Also, pretty sure JayM tried the .deb, but told the OP to attempt to use the Portable version (which he did also test) because of the fact that it can help limit breakage from randomly trying things like the OP has now done by enabling (unknown said) repos.
Edited for Distros "used by" users

Lets make some things a bit more clear and laid out since there is some confusion. Especially around the term "support".
Potential for installation and usability does not equal "support". Linux Distros do not "support" applications just because it can be installed in some way shape or form.
Linux Distros support applications by creating and "maintaining" a package of the application from start to finish (dependency resolution, testing, troubleshooting, and updating). A "Package Maintainer" they are about as close to official "support" as you'll get (besides the actual application developer) because they volunteer to take responsibility of the said application package for the Distro. Users and in our case Qualified Guides also help "support" by testing and troubleshooting.
Now to the Facts:
BeeBEEP provides (supports) several Linux installs:
- Ubuntu 18.04 via a .deb,
- Snaps (via an unofficial snap)
- "portable" packages via a tarball
There are only 10 packaged versions of BeeBEEP in repositories, looks like maybe 5 total actual Distros "supporting" BeeBEEP.
https://repology.org/project/beebeep/versions
The link above shows "created" packages for repositories, these may or may not be officially supported and they may not be maintained current.
Packaged versions does not specifically entail that something is really "supported" or not, or if it can actually be installed or not.
For example: Chocolatey, winget, freshcode aren't Distros.
Note the fact that Debian is NOT on that list at the link, therefore Debian does NOT maintain (support) a package of BeeBEEP at this time.
The Snap can be (should) run on MX Linux as MX does "support" Snaps, but as already stated, you have too boot using systemd.
There is no technical or ideological mumbo jumbo about any of that, its just a fact.
The linked page to the Snap install statistics has nothing to do with Distros "supporting" BeeBEEP or not.
This page simply lists the Distros "used by" users who have it installed via Snap. NOT Distros supporting BeeBEEP via Snap.
Again, go back to the Repology link to see which distros created (possibly maintain (support) current) packages in their repos.
JayM is right, we don't "support" (yet) BeeBEEP directly. That doesn't mean you can't install it and we won't help you with it though.
And that doesn't mean we can't maintain (support) a package of BeeBEEP in the future.
Now to the good stuff:
directly at @Michael_Logies
The process to get "support" for an application "in MX" is a Package Request as Jay stated, but do not worry about doing one, I'm acknowledging the request right now.

JayM said the Portable package works and it seems some hacky workarounds will allow the .deb package to work.
Honestly I would use the Portable package as it comes from (supported?) by the actual developer. Trying to cram a cube through a circle hole with the .deb is not going to work well long term. And you should NOT be enabling repos to do such cramming unless you know exactly what you are doing. See JayM's or my signature blocks about breaking stuffs.
With all that out of the way, like I said your request to get BeeBEEP packaged and easily installable in MX Linux is acknowledged.
Its going to be awhile (few weeks) before I can give you a status update, unless someone else decides to tackle it. But again in the meantime I would try the Portable package, if it works then use that, if not then post back here for assistance on that.
@Moltke appreciate you're help with this, really. But please do not state that MX "supports" an application just because it can be installed one way or another. "Installs and works under/with" and "Supports" are two different things. Neither MX nor Debian directly "support" BeeBEEP.

Edited for Distros "used by" users
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.
-
- Posts: 75
- Joined: Sat Dec 21, 2019 4:28 pm
Re: BeeBeep (LAN Messenger) does not work after installation
@SwampRabbit Thanks into the swamp for clarification and for future efforts on BeeBeep. ;-) I tried the portable version of BeeBeep, but it did not start running with Linux MX. I then installed Linux Mint parallel to Linux MX. And following the instructions, https://snapcraft.io/install/beebeep/mint, BeeBeep was up and running after a few minutes. I`m using another instance of Linux MX and would like to stick to one distro, but at the moment I need BeeBeep on Linux Mint. (I`m a dentist and we are communicating reception to treatment room to treatment room with a LAN Messenger (former Realpopup, now BeeBeep), so we really need such a program constantly). I opened a ticket for the developer of BeeBeep (corrected, not: Linux MX): https://sourceforge.net/p/beebeep/tickets/792/
Last edited by Michael_Logies on Tue Feb 23, 2021 2:27 pm, edited 2 times in total.
-
- Posts: 3602
- Joined: Tue Jun 14, 2016 2:02 pm
Re: BeeBeep (LAN Messenger) does not work after installation
@Michael_Logies
Fully understand the need. But I like said the Snap package will (should) work OOTB with MX if you boot with systemd. We don’t boot with systemd by default, therefore Snaps won’t work by default. Easy fix to test is to just boot with systemd.
I’m afraid you didn’t open a ticket with MX Linux development team, you opened a ticket with the BeeBEEP developers. Unless that is what you meant.
As far as the portable version not working, please let us know which specific one you tried? And reread JayM’s post as he said it worked kinda easily.
I am interested in the fact that you are using MX in a business environment, but a discussion for another time.
Fully understand the need. But I like said the Snap package will (should) work OOTB with MX if you boot with systemd. We don’t boot with systemd by default, therefore Snaps won’t work by default. Easy fix to test is to just boot with systemd.
I’m afraid you didn’t open a ticket with MX Linux development team, you opened a ticket with the BeeBEEP developers. Unless that is what you meant.
As far as the portable version not working, please let us know which specific one you tried? And reread JayM’s post as he said it worked kinda easily.
I am interested in the fact that you are using MX in a business environment, but a discussion for another time.
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.