Description of problem: nheko not works well on i586, I can't see replies to messages and not always render well the storyline https://www.imagebam.com/view/MESI56B https://www.imagebam.com/view/MESI56B https://www.imagebam.com/view/MESI569 https://www.imagebam.com/view/MESI568 I terminal I see many times this message [2024-03-13 12:41:55.058] [qml] [warning] qrc:/qml/MessageView.qml:457:17: Unable to assign QString to QDateTime (qrc:/qml/MessageView.qml:457, ) [2024-03-13 12:41:55.058] [qml] [warning] qrc:/qml/TimelineRow.qml:287: TypeError: Property 'toLocaleTimeString' of object is not a function (qrc:/qml/TimelineRow.qml:287, ) [2024-03-13 12:41:55.058] [qml] [warning] qrc:/qml/MessageView.qml:481:17: Unable to assign QString to int (qrc:/qml/MessageView.qml:481, ) Reproducible always
This is a second bug about something not working on 32-bit. Please say whether you are on real hardware (post inxi -MSG), or VirtualBox; TJ This is another 32-bit problem it would be nice to have confirmation of from another relevant tester; if possible, please...
CC: (none) => andrewsfarm, lewyssmith
(In reply to Lewis Smith from comment #1) > This is a second bug about something not working on 32-bit. Please say > whether you are on real hardware (post inxi -MSG), or VirtualBox; > > TJ > This is another 32-bit problem it would be nice to have confirmation of from > another relevant tester; if possible, please... RH mageia 9 i586 I have this info at hand, later I'll post the required info LC_ALL=C lscpu Architecture: i686 CPU op-mode(s): 32-bit, 64-bit Address sizes: 36 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 2 On-line CPU(s) list: 0,1 Vendor ID: GenuineIntel BIOS Vendor ID: Intel(R) Corporation Model name: Intel(R) Pentium(R) Dual CPU T2370 @ 1.73GHz BIOS Model name: Intel(R) Pentium(R) Dual CPU T2370 @ 1.73GHz FFFF CPU @ 1.7GHz BIOS CPU family: 185 CPU family: 6 Model: 15 Thread(s) per core: 1 Core(s) per socket: 2 Socket(s): 1 Stepping: 13 CPU(s) scaling MHz: 61% CPU max MHz: 1733.0000 CPU min MHz: 800.0000 BogoMIPS: 3458.00 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe nx lm constant_tsc arch_perfmon pebs bts cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx1 6 xtpr pdcm lahf_lm pti dtherm
(In reply to Lewis Smith from comment #1) > This is a second bug about something not working on 32-bit. Please say > whether you are on real hardware (post inxi -MSG), or VirtualBox; > > TJ > This is another 32-bit problem it would be nice to have confirmation of from > another relevant tester; if possible, please... I brought it up at today's meeting. I'd do it, but I know nothing about the software, so I don't know that I am relevant...
By 'relevant' I meant with 32-bit hardware!
Upstream blame to QT https://github.com/Nheko-Reborn/nheko/issues/1690#issuecomment-2000319678
That link says: "First, we aren't going to rush the release. We're working on stabilizing a few things from the Qt 6 port, after which there should be a new release. Second, IIRC the issue in the linked bug report has been mentioned before and IMO appears to be a Qt issue rather than an issue on our end. (Potentially related to #1564 FWIW) We appreciate your understanding of this. Just bear with us, there should be a new release before too long :)" The last linked bug: https://github.com/Nheko-Reborn/nheko/issues/1564 is "Special unicode characters cause message not to render"; last very recent comment: "can't reproduce this anymore on 0.11.3-eaf9ae31, seems like it probably got fixed at some point, possibly with a newer qt version". So this is another 'upstream' bug, and it looks as if we must wait for the new release and a subsequent update. Our current version is the latest released. But wait! Do we know whether this is just for x32, and it works (or not) on x64? That upstream bug makes no mention of hardware.
Status: NEW => UPSTREAMSource RPM: nheko => nheko-0.11.3-4.1.mga9.src.rpmKeywords: (none) => UPSTREAM
(In reply to Lewis Smith from comment #6) > But wait! Do we know whether this is just for x32, and it works (or not) on > x64? That upstream bug makes no mention of hardware. I just can say that in my 64b not happen
Not good luck for my after testing the mesa packages in bug#34190 on i586