April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1221512] New: scanner MFC-J5620DW not anymore recognized by xsane or YaST2
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221512 Bug ID: 1221512 Summary: scanner MFC-J5620DW not anymore recognized by xsane or YaST2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: Willy.Weisz(a)univie.ac.at QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since the last upgrade of Tumbleweed (including kernel 6.7.7) Xsane doesn't find my Brother MFC-J5620DW. Also YaST2 doesn't find it. Up to the previous level of Tumbleweed the scanner connected via WiFi worked fine with the Brother-provided driver (brscan4-0.4.4-4.x86_64). The printer part of the 4-in-1 MFC-J5620DW works as before. What's the problem? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1218099] New: VUL-0: CVE-2023-50471: cjson: segmentation violation in function cJSON_InsertItemInArray
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1218099 Bug ID: 1218099 Summary: VUL-0: CVE-2023-50471: cjson: segmentation violation in function cJSON_InsertItemInArray Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/388143/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: mardnh(a)gmx.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: andrea.mattiazzo(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- cJSON v1.7.16 was discovered to contain a segmentation violation via the function cJSON_InsertItemInArray at cJSON.c. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-50471 https://github.com/DaveGamble/cJSON/issues/802 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1218098] New: VUL-0: CVE-2023-50472: cjson: segmentation violation in function cJSON_SetValuestring
by bugzilla_noreply＠suse.com 25 May '24

25 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1218098 Bug ID: 1218098 Summary: VUL-0: CVE-2023-50472: cjson: segmentation violation in function cJSON_SetValuestring Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://smash.suse.de/issue/388144/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: mardnh(a)gmx.de Reporter: smash_bz(a)suse.de QA Contact: security-team(a)suse.de CC: andrea.mattiazzo(a)suse.com Target Milestone: --- Found By: Security Response Team Blocker: --- cJSON v1.7.16 was discovered to contain a segmentation violation via the function cJSON_SetValuestring at cJSON.c. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-50472 https://github.com/DaveGamble/cJSON/issues/803 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1214013] New: Shutdown did not finish (PC was not powered off, no obvious error logged)
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1214013 Bug ID: 1214013 Summary: Shutdown did not finish (PC was not powered off, no obvious error logged) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 868645 --> https://bugzilla.suse.com/attachment.cgi?id=868645&action=edit Screenshot when shutdown should power off the PC Maybe the issue is related to an MD-RAID being verified (see Bug 1214004), but the system did not power off. The last message in journal were: Aug 05 01:47:01 pc.site systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Aug 05 01:47:01 pc.site systemd[1]: Stopping Device-mapper event daemon... Aug 05 01:47:01 pc.site dmeventd[1125]: dmeventd detected break while being idle for 0 second(s), exiting. Aug 05 01:47:01 pc.site dmeventd[1125]: dmeventd shutting down. Aug 05 01:47:01 pc.site systemd[1]: dm-event.service: Deactivated successfully. Aug 05 01:47:01 pc.site systemd[1]: Stopped Device-mapper event daemon. Aug 05 01:47:01 pc.site systemd[1]: Reached target System Shutdown. Aug 05 01:47:01 pc.site systemd[1]: Reached target Late Shutdown Services. Aug 05 01:47:01 pc.site systemd[1]: systemd-poweroff.service: Deactivated successfully. Aug 05 01:47:01 pc.site systemd[1]: Finished System Power Off. Aug 05 01:47:01 pc.site systemd[1]: Reached target System Power Off. Aug 05 01:47:01 pc.site systemd[1]: Shutting down. Aug 05 01:47:01 pc.site systemd-shutdown[1]: Syncing filesystems and block devices. Aug 05 01:47:03 pc.site systemd-shutdown[1]: Sending SIGTERM to remaining processes... Aug 05 01:47:03 pc.site haveged[1265]: haveged: Stopping due to signal 15 Aug 05 01:47:03 pc.site haveged[1265]: haveged starting up Aug 05 01:47:03 pc.site systemd-journald[1132]: Journal stopped I'm also adding a screenshot showing the last messages (that would last until I pressed the power button). Kernel was 5.14.21-150500.55.12-default The only other thing that looked unusual was this: ... Aug 05 01:46:59 pc.site systemd[1]: Stopped Record System Boot/Shutdown in UTMP. Aug 05 01:46:59 pc.site systemd[1]: Stopping Security Auditing Service... Aug 05 01:46:59 pc.site systemd-cryptsetup[3123]: Device cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 is still in use. Aug 05 01:46:59 pc.site systemd-cryptsetup[3123]: Failed to deactivate: Device or resource busy Aug 05 01:46:59 pc.site systemd[1]: systemd-cryptsetup@cr_md\x2duuid\x2dfe1588c4:a2140388:5b4117ba:4e4339b9\x2dpart5.service: Control process exited, code=exited, status=1> Aug 05 01:46:59 pc.site systemd[1]: systemd-cryptsetup@cr_md\x2duuid\x2dfe1588c4:a2140388:5b4117ba:4e4339b9\x2dpart5.service: Failed with result 'exit-code'. Aug 05 01:46:59 pc.site systemd[1]: Stopped Cryptography Setup for cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5. Aug 05 01:46:59 pc.site auditd[1679]: The audit daemon is exiting. Aug 05 01:46:59 pc.site kernel: kauditd_printk_skb: 50 callbacks suppressed Aug 05 01:46:59 pc.site kernel: audit: type=1305 audit(1691192819.741:562): op=set audit_pid=0 old=1679 auid=4294967295 ses=4294967295 subj=unconfined res=1 Aug 05 01:46:59 pc.site auditctl[3127]: enabled 0 Aug 05 01:46:59 pc.site auditctl[3127]: failure 1 Aug 05 01:46:59 pc.site auditctl[3127]: pid 0 Aug 05 01:46:59 pc.site auditctl[3127]: rate_limit 0 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_limit 64 Aug 05 01:46:59 pc.site auditctl[3127]: lost 0 Aug 05 01:46:59 pc.site auditctl[3127]: backlog 1 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_wait_time 15000 Aug 05 01:46:59 pc.site auditctl[3127]: backlog_wait_time_actual 0 Aug 05 01:46:59 pc.site auditctl[3127]: No rules Aug 05 01:46:59 pc.site kernel: audit: type=1305 audit(1691192819.853:563): op=set audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=unconfined res=1 Aug 05 01:46:59 pc.site systemd[1]: auditd.service: Deactivated successfully. Aug 05 01:46:59 pc.site systemd[1]: Stopped Security Auditing Service. Aug 05 01:46:59 pc.site systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully. Aug 05 01:46:59 pc.site systemd[1]: Stopped Create Volatile Files and Directories. Aug 05 01:47:00 pc.site systemd[1]: dracut-shutdown.service: Deactivated successfully. Aug 05 01:47:00 pc.site systemd[1]: Stopped Restore /run/initramfs on shutdown. Aug 05 01:47:00 pc.site systemd[1]: Stopped target Local File Systems. Aug 05 01:47:00 pc.site systemd[1]: Unmounting /home... ... The LUKS device cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 contains the PV for the system VG, so it makes no sense trying to deactivate that before unmounting the system filesystems. Layout is like this: # pvs PV VG Fmt Attr PSize PFree /dev/mapper/cr_md-uuid-fe1588c4:a2140388:5b4117ba:4e4339b9-part5 system lvm2 a-- 199,98g 3,88g # vgs VG #PV #LV #SN Attr VSize VFree system 1 6 0 wz--n- 199,98g 3,88g # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert android system Vwi-aotz-- 50,00g thinpool 55,19 floppies system Vwi-a-tz-- 1,00g thinpool 15,18 home system -wi-ao---- 50,00g root system -wi-ao---- 32,00g swap system -wi-ao---- 4,00g thinpool system twi-aotz-- 110,00g 25,23 22,76 (System was upgraded from Leap 15.4 where shutdown worked) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1221702] New: Bluetooth headphones not reconnecting upon logging in
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221702 Bug ID: 1221702 Summary: Bluetooth headphones not reconnecting upon logging in Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai(a)suse.com Reporter: kjchmielewski(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873633 --> https://bugzilla.suse.com/attachment.cgi?id=873633&action=edit hwinfo I installed opensuse leap 15.6 beta on my laptop using official ISO, then I installed the pipewire-pulseaudio package. Next, I paired Bluetooth headphones in the Bluetooth settings, and the output device was correctly added in the sound settings. The problem is that after logging out or restarting the system, the headphones do not automatically connect if they are turned on all the time. I have to turn off and turn on the headphones' power again, or initiate connection manually for them to connect and become available as an output device in the sound settings. Is this expected beheviour? In leap version 15.5, this works as I expect, that is, after logging out or restarting, the Bluetooth connection disconnects, but upon logging in, the devices are automatically connected, even if they are continuously powered on and there is no need to turn them on again, or reconnect manually. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1222175] New: rustc 1.77 adds spurious -Cstrip=debuginfo to buildline
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222175 Bug ID: 1222175 Summary: rustc 1.77 adds spurious -Cstrip=debuginfo to buildline Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: brunopitrus(a)hotmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- This produces policy-violating packages with missing debuginfo. See eg. bitwarden build log: https://build.opensuse.org/package/live_build_log/devel:languages:nodejs/bi… Seems to be a regression from rust 1.76. A robust workaround is to explicitely add `Cstrip=none` to RUSTFLAGS. (This is e.g. what Fedora already does) -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1222343] New: protobuf linking issue
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222343 Bug ID: 1222343 Summary: protobuf linking issue Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: openSUSE Leap 15.5 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jonaski(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recently, I'm getting several linking errors while building strawberry on leap. Full log can be seen on https://build.opensuse.org/package/show/multimedia:apps/strawberry This happened a few weeks ago, and it seem to be the same issue on both Leap 15.5 and 15.6, it is not an issue on Tumbleweed or any other linux distribution (Fedora, Debian and Ubuntu builds fine). I suspect an issue with the protobuf library on Leap. From the build log: [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: CMakeFiles/strawberry-tagreader.dir/tagreaderworker.cpp.o: in function `google::protobuf::internal::ArenaStringPtr::SetBytes(void const*, unsigned long, google::protobuf::Arena*)': [ 76s] /usr/include/google/protobuf/arenastring.h:495:(.text+0x44e): undefined reference to `google::protobuf::internal::ArenaStringPtr::Set(absl::lts_20240116::string_view, google::protobuf::Arena*)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadertaglib.cpp.o): in function `google::protobuf::internal::ArenaStringPtr::Set(char const*, unsigned long, google::protobuf::Arena*)': [ 76s] /usr/include/google/protobuf/arenastring.h:470:(.text+0x9935): undefined reference to `google::protobuf::internal::ArenaStringPtr::Set(absl::lts_20240116::string_view, google::protobuf::Arena*)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: /usr/include/google/protobuf/arenastring.h:470:(.text+0x9976): undefined reference to `google::protobuf::internal::ArenaStringPtr::Set(absl::lts_20240116::string_view, google::protobuf::Arena*)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::SongMetadata::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:2565:(.text+0x1886): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::IsMediaFileRequest::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:2769:(.text+0x18a6): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::IsMediaFileResponse::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3007:(.text+0x18c6): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::ReadFileRequest::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3211:(.text+0x18e6): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o): in function `spb::tagreader::ReadFileResponse::GetMetadata() const': [ 76s] /home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3463:(.text+0x1906): undefined reference to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' [ 76s] /usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: ../libstrawberry-tagreader/liblibstrawberry-tagreader.a(tagreadermessages.pb.cc.o):/home/abuild/rpmbuild/BUILD/strawberry-1.0.23/build/ext/libstrawberry-tagreader/tagreadermessages.pb.cc:3939: more undefined references to `google::protobuf::internal::AssignDescriptors(google::protobuf::internal::DescriptorTable const* (*)(), absl::lts_20240116::once_flag*, google::protobuf::Metadata const&)' follow [ 76s] collect2: error: ld returned 1 exit status -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1219132] New: [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219132 Bug ID: 1219132 Summary: [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3889391/modules/Sysc tl/steps/136 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation # Test messages # Sysctl_kernel_sched_energy_aware # failure: ValueError: invalid literal for int() with base 10: '' Possibly this is a kernel issue - possibly the kernel just no longer exposes this and the test should not care. Please advise openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-sys-param-check@64bit fails in [Sysctl](https://openqa.opensuse.org/tests/3889391/modules/Sysctl/steps/136) ## Test suite description RAM size is set to 2048, some kernel parameters change with total RAM https://github.com/openSUSE/sys-param-check ## Reproducible Fails since (at least) Build [20240123](https://openqa.opensuse.org/tests/3888589) ## Expected result Last good: [20240122](https://openqa.opensuse.org/tests/3886345) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223117] New: Fcitx5 can't work for Qt6 based apps
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223117 Bug ID: 1223117 Summary: Fcitx5 can't work for Qt6 based apps Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: sauntor(a)yeah.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- There is only fcitx5 plugin for qt5 (a.k. fcitx5-qt5, which supplies /usr/lib64/qt5/plugins/platforminputcontexts/libfcitx5platforminputcontextplugin.so), but no package supplies the the plugin for qt6! As for this reason, apps developed with Qt6 (like Qt Creator) can't use fcitx5 as the input method. Tumbleweed seems has the same problem too. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217466] New: Missing fonts for Indic and south Asian languages.
by bugzilla_noreply＠suse.com 23 May '24

23 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217466 Bug ID: 1217466 Summary: Missing fonts for Indic and south Asian languages. Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Desktop Environment Assignee: rbrown(a)suse.com Reporter: sebastian(a)cozycabin.se QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0 Build Identifier: After installing, I noticed a lack of font support for a lot of Indic and south Asian languages. They are both pretty populous areas so it seems like an oversight to not include their basic fonts in the default installation. Reproducible: Always Steps to Reproduce: 1. Open Firefox from Flatpak (as installed by default). 2. Go to https://meta.wikimedia.org/wiki/List_of_Wikipedias 3. Look at the "Other languages" box at the top of the page. Actual Results: I see TOFU for several languages including Kannada. Expected Results: I expected to see all languages in that box be rendered by default. I did a bit of research, and we are talking about at least these ones, listed in order of native speakers counted in millions (based on quick Wikipedia data): | Language | Native Speakers | L2 Speakers | | ---------- | -----------------:| --------------:| | Telugu | 83 | 13 | | Kannada | 44 | 15 | | Burmese | 33 | 10 | | Khmer | 17 | 1 | | Santali | 7.6 | - | | Shan | 4.7 | - | | Tulu | 1.85 | - | | Manipuri | 1.8 | 1.2 | | Tibetan | 1.2 | - | | Mon | 0.9 | - | | Pa'O | 0.86 | - | | Dzongkha | ~0.2 | ~0.4 | | ========== | ================= | ============== | | Total | 196.11 million | 40.6 million | While it would be nice to have all of them, I don't think that should be a priority, but having at least fonts for the top ones seems reasonable. That would be a very small impact while being very useful to a large number of people. Fedora for instance, have already done some of this research which we could leverage. Which I found here: https://fedoraproject.org/wiki/Changes/Indic_Noto_fonts It basically would include including these fonts in the pattern, in both Sans and Sans-Serif versions: - google-noto-sans-bengali-vf-fonts - google-noto-sans-devanagari-vf-fonts - google-noto-sans-gujarati-vf-fonts - google-noto-sans-kannada-vf-fonts - google-noto-sans-oriya-vf-fonts - google-noto-sans-tamil-vf-fonts - google-noto-sans-telugu-vf-fonts As an alternative, there is the indic-fonts package which Fedora intended to switch away from, Zypper marks it as being only 6.2 MiB when installed. This does not to my knowledge include fonts for Khmer or Burmese, so that would require some additional research. Unfortunately I don't know any of these languages so I can not comment on any specifics when it comes to which font should be used for which language. -- You are receiving this mail because: You are on the CC list for the bug.

1 4