I just checked the MainWindow.ui again (I remebered from when i looked at that some time ago).Īs hacst said, the log and chat widgets are now "QDockWidgets". Maybe just change that, but I guess others have tried that already. Mumble/src/mumble/CustomElements.cpp - line 110 But as it does I was thinking that maybe there is a bug in the layout of these interesting, the suggested, seems to exist still. Thus it should never disappear completely. However we do set the minimum height for the widget to be as high as a single character. From what I have read, dock widgets in qt (which the Chat is) adapt the size according to their content widgets. If that works, you are spared the effort :P I'll probably try to reproduce the bug in a VM first. It will use your settings but as long as you don't change them, that should be fine. Yeah you don't have to install the compiled version. These all keep some sort of information, chat logs, contacts, etc. I think this will require a few compiles but only minor changes between them so they should be really fast (after the first one that is). alfg/nginx-rtmp.Logging in as the SuperUser to a new Mumble Server. For this we can add print statements into the code. The plan would be track down where and based on what the size of the chat is set. Maybe you need to install qt5-concurrent in addition. Travis file should be pretty up to date yes. The important bit is that you can run the built client on a machine that shows the error. Regarding the bug in general, are you using a more recent version of Qt or what makes you think thats the reason?Įspecially considering you don't have the bug? I would have suggested to use a Virtual machine (which I would need to set up first), but that would maybe taint the result. What are the debug options? (haven't seen them in the install doc)Īnd what about usability? Can we build a version that can run alongside the already installed versions? I hope I don't have to rebuild stuff a thousand times □ ? Never really used debug flags to be honest □. I set debug options, compile it and then we can see special logs? We could potentially search for the bug together by adding debug-statements as needed :) I guess the requirements shown in the travis file are the most recent? Well, I always have an lxd container ready for compiling. Ok, a different patch then? Or for now, no patch? Note: A zombie process is a leftover process that has not entirely ended. If you notice a zombie process when starting Murmur, you must install the redhat-lsb-core package. Patch will be against master, so you'd have to build the patch PRĪs I wrote above though I think the patch I had in mind doesn't make much sense after all. To instruct CentOS to automatically start the service upon next reboot, run the following command: sudo systemctl enable rvice.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |