broo stuck on initializing #11
Comments
|
murmur.txt says: So something is already running on port 64738. Check if you did not open multiple instances of mumble-server. You can kill processes with: $ broo -q # If broo is running
$ sudo pkill -9 -f mumble # Kills mumble and mumble-serverAlternate way is to just restart your machine (not the Linux style but ok). |
|
Ping. Will close issue after 7 days if no reply. |
Same and I tested it and didn't work OS: Ubuntu 22.04
|
|
@ErfanBahramali In your case, it seems like the client isn't joining. Did you setup correctly, maybe it is prompting for certificate? You can use |
I still didn't succeed 🚶♂️
|
|
@ErfanBahramali On mobile it is failing because you're specifying localhost IP. Localhost for mobile is the mobile itself. You need to give the computer's IP (which Broo shows at the end, but since it is being stuck, it did not reach that point). The script is stuck because the script expects a message in the log (hence you see Can you tell your Mumble version? Also, can you try the setup again and this time installing from source? Here is my mumble_client.out for reference.Here's how successful run looks like, if you are curious.
|
|
Oh of course, the murmur log says it is 1.5. So it should ideally work. The script was made earlier, and I'm on 1.6 right now and it still works. Run In another terminal, run What do you observe? Also, if you didn't install from an APT repo, reinstalling from source won't hurt. Maybe picked up a bug? |
|
|
|
Damn. Try the following commands one by one (in place of the mumble command as mentioned earlier). Do you get similar output? (That ServerHandler line is the key) |
-
-
|
|
Damn wth, this is weird! Does updating to mumble from master branch solve it? The setup script can install from upstream repo for you. Please try that. |
|
I was thinking about this. It'd be pretty weird for it to be a mumble bug. I used to use 1.5 too. Is this happening because of QT's offscreen platform unable to make the connection? $ ldd /usr/local/bin/mumble | grep Qt
libQt5Network.so.5 => /lib/x86_64-linux-gnu/libQt5Network.so.5 (0x00007f4b3cc55000)
libQt5Xml.so.5 => /lib/x86_64-linux-gnu/libQt5Xml.so.5 (0x00007f4b3e186000)
libQt5Sql.so.5 => /lib/x86_64-linux-gnu/libQt5Sql.so.5 (0x00007f4b3d824000)
libQt5Svg.so.5 => /lib/x86_64-linux-gnu/libQt5Svg.so.5 (0x00007f4b3d7cc000)
libQt5Widgets.so.5 => /lib/x86_64-linux-gnu/libQt5Widgets.so.5 (0x00007f4b3c400000)
libQt5Gui.so.5 => /lib/x86_64-linux-gnu/libQt5Gui.so.5 (0x00007f4b3bc00000)
libQt5TextToSpeech.so.5 => /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 (0x00007f4b3e162000)
libQt5DBus.so.5 => /lib/x86_64-linux-gnu/libQt5DBus.so.5 (0x00007f4b3cbc4000)
libQt5Core.so.5 => /lib/x86_64-linux-gnu/libQt5Core.so.5 (0x00007f4b3b600000)Anyways, do try installing mumble from master. |
|
NB: The author of the PR referenced above has the same problem (mumble not connecting offscreen). |
|
Back to this. The multiple warning messages |
|
If anyone is comfortable with programming and faces this issue, please comment here if you can help. CC: @ernesto-glz If this last ditch effort fails (highly likely tbh), I'll go ahead and add testing during setup in order to disable offscreen for those who don't support. This is a very weird bug in QT (which does not happen for me and many others), the offscreen may not be connecting to network in this case. While we are not QT devs, superficially examining it won't hurt, and this can serve as a record for other people which can potentially fix it. In Mumble source code (Sprinkle print statements in the function, like Full stepsCopied from $ cd /tmp
$ git clone https://github.com/mumble-voip/mumble.git --depth 1
$ cd mumble
$ git submodule update --init --recursive --depth 1
$ mkdir build && cd build
$ export CMAKE_BUILD_PARALLEL_LEVEL=`nproc`
$ release_id=$(python "../scripts/mumble-version.py")
$ version="$release_id~git$(git rev-parse --short HEAD)+broo"
$ cmake \
-DBUILD_NUMBER=0 \
-DRELEASE_ID=$release_id \
-DCMAKE_UNITY_BUILD=ON \
-Dalsa=OFF \
-Dcrash-report=OFF \
-Doptimize=ON \
-Dpackaging=ON \
-Dplugins=OFF \
-Dqtspeech=ON \
-Dtranslations=OFF \
-Dwasapi=OFF \
-Dxboxinput=OFF \
..
# Build
$ make -j`nproc`
# Run mumble-server in a separate terminal
$ mumble-server -ini ~/.config/broo/murmur.ini -fg
# Run and test compiled mumble
$ ./mumble "mumble://127.0.0.1" -platform offscreen |
|
@siddhpant I have a new PC and this has never happened since I installed a new Fedora 38 on it. Anyway, I did the tests and those 2 events are being triggered and executed correctly but since I can't reproduce the problem this I don't think will be of much help. |
|
@ernesto-glz cool, thanks! |
|
Added a timeout test during setup. The command will timeout if it is stuck, so we configure it to show the GUI and not use the offscreen mode. This does cause the GUI to show up, but cannot be helped, as I cannot test the issue as I cannot reproduce it. |
I tried running this on ubuntu 22 LTS but broo is stuck on initializing.
The text was updated successfully, but these errors were encountered: