barathrm
barathrm
Verified that my DM rooms have the m.direct flag set using devtools in element desktop, and have tried logging out and in again 2 times in element x android, as...
creating a new DM in element desktop, it popped up as a room, not a DM, in element X android. it correctly showed up as a DM in element dekstop.
Thanks for following up! I looked at the json in `m.direct`, but I couldn't see any immediate issues. I made a backup of the contents and added them back with...
Tried logging out and in again, and this time it took 6 tries IIRC. Tried cross-verifying from schildichat, element desktop, and tried closing and reopening the element x app in-between...
My element causes between 50-80% cpu usage according to top, even though there are no visible changes in the GUI. I don't have an animated profile picture. I'd love to...
Works great! I'm not qualified to comment on the code change itself, but I compiled and tested your changes using a desktop and mobile browser and imo it makes the...
> @barathrm I'm guessing this is because the submodules are not fetched when building? :) hm I dont understand :thinking: the above error means that make (?) installed the files...
Here are the [logs](https://build.opensuse.org/package/live_build_log/home:fawz:mooltipass/moolticute-testing/openSUSE_Tumbleweed/x86_64) from OBS showing the file being installed (but not packaged by me, hence the error) > [ 102s] /usr/bin/qmake-qt5 -install qinstall /home/abuild/rpmbuild/SOURCES/moolticute-testing-1.03.17.r0.gba0f3a0/src/QZXing/src/QZXing.h /home/abuild/rpmbuild/BUILDROOT/moolticute-testing-1.03.17.r0.gba0f3a0-58.1.x86_64/usr/include/QZXing.h > [ 102s]...
Okay just double-checked the OBS logged and the first build failed when moolticute-testing was bumped from v1.03.15-testing to v1.03.16-testing. So I *assume* it's somehow related to the submodule transition, but...