May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1091603] New: iproute2: "ip route add default via <ipv6_address>" not parsed correctly
by bugzilla_noreply＠novell.com 01 Oct '21

01 Oct '21

http://bugzilla.suse.com/show_bug.cgi?id=1091603 Bug ID: 1091603 Summary: iproute2: "ip route add default via <ipv6_address>" not parsed correctly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mkubecek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With iproute2 4.16, command "ip route add default via ..." fails if an IPv6 address is supplied (unless "-6" is used): alaris:~ # ip route add default via 1::1 Error: inet address is expected rather than "1::1". This is a regression in version 4.16 fixed by commit d42c7891d26e utils: Do not reset family for default, any, all addresses -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1137520] New: openQA test fails in qemu with "corrupted size vs. prev_size: 0x000056322a96f680" or "malloc(): smallbin double linked list corrupted: 0x0000557b4ea753d0"
by bugzilla_noreply＠novell.com 29 Sep '21

29 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1137520 Bug ID: 1137520 Summary: openQA test fails in qemu with "corrupted size vs. prev_size: 0x000056322a96f680" or "malloc(): smallbin double linked list corrupted: 0x0000557b4ea753d0" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://openqa.opensuse.org/tests/949807/modules/first _boot/steps/1 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-5.12.80-Krypton-Live-x86_64-krypton-live-installation@64bit-2G fails in [first_boot](https://openqa.opensuse.org/tests/949807/modules/first_boot/ste… with an "incomplete" status due to qemu crashes. ## Test suite description Boots the openSUSE Krypton/Argon Live DVD and uses the installer to install with default settings, then reboots into the installed system. ## Reproducible Fails since at least 2019-03-19, see https://openqa.opensuse.org/tests/894616 ## Expected result Last good: 3 months ago, see https://openqa.opensuse.org/tests/876852 and further tests in the history that did not fail. ## Problem We had maintenance updates for qemu: ``` openqaworker4:~ # grep -i '|qemu|' /var/log/zypp/history 2018-10-01 13:49:07|install|qemu|2.11.2-lp150.7.9.1|x86_64||repo-update|feef165faae3f66a39d5339db9994a2620160ac930172adee9f3a529265dd9da| 2018-12-07 00:33:21|install|qemu|2.11.2-lp150.7.12.1|x86_64||repo-update|eef9ee9e02c90d20b97e7d7520e3748565f77e42b651acc2307664f45c217b7d| 2018-12-16 00:50:35|install|qemu|2.11.2-lp150.7.15.1|x86_64||repo-update|1ec34cf5f0df53881fa7050ac1dc805112b52a73b6fe68283a2bdff153336d8a| 2019-02-28 00:11:59|install|qemu|2.11.2-lp150.7.18.1|x86_64||repo-update|4f8871d87248bba24314cb1b4f8bcb93bb0ffc73ee5c752bf83ffc4efa48b3d3| 2019-05-20 16:52:47|install|qemu|2.11.2-lp150.7.22.1|x86_64||repo-update|419e55de487213462e848818ef975db252b671a4327c4e515f079eae287ef478| ``` ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?version=5.12.80&distri=ope… -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 952288] New: Find a way to set Adwaita as systemwide icon theme when installing GNOME DE
by bugzilla_noreply＠novell.com 28 Sep '21

28 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=952288 Bug ID: 952288 Summary: Find a way to set Adwaita as systemwide icon theme when installing GNOME DE Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: zaitor(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As of today, any user installing GNOME as DE will still end up with DMZ set as system cursor instead of Adwaita. (do a grep X_MOUSE_CURSOR /etc/sysconfig/windowmanager on your boxes). Now this is only noticed when users open up yast (and possibly odd 3'rd party apps) It's rather visually unpleasing, and something we should look into fixing. The easiest thing to do would probably be to add it to one of our branding packages, or even create a new one if needed. Ideally we should offer a "system option" in tweak tool, but that will probably be a lot of work. Patches/fixes welcome everyone. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 970624] New: Package Request: RetroFE
by bugzilla_noreply＠novell.com 28 Sep '21

28 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=970624 Bug ID: 970624 Summary: Package Request: RetroFE Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: zombie_ryushu(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I request that RetroFE be Packaged for SUSE. Sources can be found here. http://www.retrofe.com/download.php -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1160707] New: qemu VNC console corruption
by bugzilla_noreply＠novell.com 28 Sep '21

28 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1160707 Bug ID: 1160707 Summary: qemu VNC console corruption Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 URL: https://openqa.suse.de/tests/3773959/modules/update_ke rnel/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario sle-12-SP4-Server-DVD-Incidents-Kernel-aarch64-install_ltp+sle+Server-DVD-Incidents-Kernel@aarch64-virtio fails in [update_kernel](https://openqa.suse.de/tests/3773959/modules/update_kernel/steps/6) as a random problem sometimes appears on aarch64 test machines where the VM screen isn't properly cleared after boot and console output gets drawn over remnants of boot splash screen. Then the job fails because needles don't match. The problem appears less than once a week and job restart usually fixes it but it might be worth investigating further. ## Reproducible Sporadic ## Expected result Last good: [4.12.14-449.1.g4163e5c](https://openqa.suse.de/tests/3768894) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=aarch64&distri=sle&flavor=Server-DVD-Incidents-Kernel&machine=aarch64-virtio&test=install_ltp%2Bsle%2BServer-DVD-Incidents-Kernel&version=12-SP4) The problem appears on the osd (openqa.suse.de) aarch64 workers. OS is openSUSE Leap 15.1, qemu package versions: ``` $ sudo rpm -qa | grep qemu qemu-seabios-1.12.0-lp151.7.9.1.noarch qemu-arm-3.1.1.1-lp151.7.9.1.aarch64 qemu-ui-gtk-3.1.1.1-lp151.7.9.1.aarch64 qemu-ovmf-x86_64-0.1+svn17700-3.2.noarch qemu-3.1.1.1-lp151.7.9.1.aarch64 qemu-ipxe-1.0.0+-lp151.7.9.1.noarch qemu-block-rbd-3.1.1.1-lp151.7.9.1.aarch64 qemu-block-curl-3.1.1.1-lp151.7.9.1.aarch64 qemu-sgabios-8-lp151.7.9.1.noarch qemu-ui-sdl-3.1.1.1-lp151.7.9.1.aarch64 qemu-uefi-aarch64-2017+git1510945757.b2662641d5-lp151.10.1.noarch qemu-ui-curses-3.1.1.1-lp151.7.9.1.aarch64 qemu-ksm-3.1.1.1-lp151.7.9.1.aarch64 qemu-vgabios-1.12.0-lp151.7.9.1.noarch qemu-x86-3.1.1.1-lp151.7.9.1.aarch64 qemu-tools-3.1.1.1-lp151.7.9.1.aarch64 ``` ## Workaround Retrigger tests with new qemu instances -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1069468] New: Packages should no longer use /var/adm/fillup-templates
by bugzilla_noreply＠novell.com 27 Sep '21

27 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1069468 Bug ID: 1069468 Summary: Packages should no longer use /var/adm/fillup-templates Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: CONFIRMED Severity: Major Priority: P5 - None Component: Other Assignee: rbrown(a)suse.com Reporter: rbrown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 749776 --> http://bugzilla.opensuse.org/attachment.cgi?id=749776&action=edit fillup-templates list As discussed on the opensuse-packaging list there are significant problems with fillup-templates being located in /var/adm https://lists.opensuse.org/opensuse-packaging/2017-11/msg00017.html At time of writing, rpm in Tumbleweed now has support for a new rpm macro (%_fillupdir) which should be used instead to relocate the fillup templates to the new location of /usr/share/fillup-templates https://en.opensuse.org/index.php?title=openSUSE:Packaging_Conventions_RPM_… Any unchanged packages should be okay, as the rpm package's other macros that consume fillup-templates support both the old and new path. However to enable us to tidy up the /var subvolumes in all *SUSE distributions we to change all the packages to use the new path There are over 200 packages in Factory that currently use the old convention (List attached) I am working initially on the packages needed by CaaSP/Kubic, with my intention being to either do the rest soon after or ask the community to help with the rest. This bug is therefore a reference for all of these efforts -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1165535] New: System lockup under memory pressure using encrypted swap on SSD (failed command: WRITE FPDMA QUEUED)
by bugzilla_noreply＠novell.com 26 Sep '21

26 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1165535 Bug ID: 1165535 Summary: System lockup under memory pressure using encrypted swap on SSD (failed command: WRITE FPDMA QUEUED) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a system that uses an SSD for /boot and encrypted swap only (the rest is on a traditional hard disk), I had the following problem: I was working normally with the system, when I decided to launch "yast2 online_update". Unfortunately the system became terribly slow (practically not responding for minutes), so I could not do anything than press the Reset-button after having waited about 30 minutes. After reboot I see "odd" ATA errors related to the SSD. However the SSD is rather new and in good condition. So I guess the issue has to do with memory pressure. Here are the logs when things started to become slow: Mar 03 10:09:57 pc dbus-daemon[2706]: [session uid=1000 pid=2706] Successfully activated service 'org.gnome.evince.Daemon' Mar 03 10:09:57 pc systemd[2686]: Starting Evince document viewer... Mar 03 10:09:57 pc systemd[2686]: Started Evince document viewer. Mar 03 10:10:13 pc kernel: ata2: log page 10h reported inactive tag 5 Mar 03 10:10:14 pc kernel: ata2.00: exception Emask 0x1 SAct 0x7fffffdf SErr 0x0 action 0x0 Mar 03 10:10:14 pc kernel: ata2.00: irq_stat 0x40000009 Mar 03 10:10:14 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:10:14 pc kernel: ata2.00: cmd 61/08:00:e0:b0:7d/00:00:00:00:00/40 tag 0 ncq dma 4096 out res 40/00:00:e0:b0:7d/00:00:00:00:00/40 Emask 0x1 (device error) Mar 03 10:10:14 pc kernel: ata2.00: status: { DRDY } Mar 03 10:10:14 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:10:14 pc kernel: ata2.00: cmd 61/08:08:e8:b0:7d/00:00:00:00:00/40 tag 1 ncq dma 4096 out res 40/00:00:e0:b0:7d/00:00:00:00:00/40 Emask 0x1 (device error) Mar 03 10:10:14 pc kernel: ata2.00: status: { DRDY } Mar 03 10:10:14 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:10:14 pc kernel: ata2.00: cmd 61/08:10:f0:b0:7d/00:00:00:00:00/40 tag 2 ncq dma 4096 out res 40/00:00:e0:b0:7d/00:00:00:00:00/40 Emask 0x1 (device error) Mar 03 10:10:14 pc kernel: ata2.00: status: { DRDY } [...] Mar 03 10:10:14 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:10:14 pc kernel: ata2.00: cmd 61/08:f0:d8:b0:7d/00:00:00:00:00/40 tag 30 ncq dma 4096 out res 40/00:00:e0:b0:7d/00:00:00:00:00/40 Emask 0x1 (device error) Mar 03 10:10:14 pc kernel: ata2.00: status: { DRDY } Mar 03 10:10:14 pc kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 03 10:10:14 pc kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 03 10:10:14 pc kernel: ata2.00: configured for UDMA/133 Mar 03 10:10:14 pc kernel: ata2: EH complete Mar 03 10:10:14 pc kernel: ata2.00: Enabling discard_zeroes_data Mar 03 10:10:14 pc rsyslogd[1332]: message repeated 13 times: [-- MARK --] Mar 03 10:10:14 pc rsyslogd[1332]: action 'action 1' suspended (module 'builtin:ompipe'), retry 0. There should be messages before this one giving the reason for suspension. [v8.33.1 try http://www.rsyslog.com/e/2007 ] Mar 03 10:10:14 pc rsyslogd[1332]: action 'action 1' suspended (module 'builtin:ompipe'), next retry is Tue Mar 3 10:10:44 2020, retry nbr 0. There should be messages before this one giving the reason for suspension. [v8.33.1 try http://www.rsyslog.com/e/2007 ] [...] Mar 03 10:15:48 pc /usr/lib/gdm/gdm-x-session[2700]: (II) event2 - Logitech USB-PS/2 Optical Mouse: SYN_DROPPED event - some input events have been lost. Mar 03 10:16:17 pc /usr/lib/gdm/gdm-x-session[2700]: (II) event2 - Logitech USB-PS/2 Optical Mouse: SYN_DROPPED event - some input events have been lost. [...] Mar 03 10:25:13 pc systemd-journald[30532]: Journal started Mar 03 10:25:18 pc systemd-journald[30532]: System journal (/var/log/journal/89c660865c00403a9bacef32b6828556) is 856.0M, max 819.2M, 0B free. [...] Mar 03 10:25:19 pc kernel: ata2.00: exception Emask 0x50 SAct 0x7f000007 SErr 0x800 action 0x6 frozen Mar 03 10:25:19 pc kernel: ata2.00: irq_stat 0x08000000, interface fatal error Mar 03 10:25:19 pc kernel: ata2: SError: { HostInt } Mar 03 10:25:19 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:25:19 pc kernel: ata2.00: cmd 61/c8:00:38:06:78/01:00:00:00:00/40 tag 0 ncq dma 233472 out res 40/00:c0:00:00:72/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Mar 03 10:25:19 pc kernel: ata2.00: status: { DRDY } [...] Mar 03 10:25:19 pc kernel: ata2.00: failed command: WRITE FPDMA QUEUED Mar 03 10:25:19 pc kernel: ata2.00: cmd 61/40:f0:f8:00:78/05:00:00:00:00/40 tag 30 ncq dma 688128 out res 40/00:c0:00:00:72/00:00:00:00:00/40 Emask 0x50 (ATA bus error) Mar 03 10:25:19 pc kernel: ata2.00: status: { DRDY } Mar 03 10:25:19 pc kernel: ata2: hard resetting link Mar 03 10:25:19 pc kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Mar 03 10:25:19 pc kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 03 10:25:19 pc kernel: ata2.00: supports DRM functions and may not be fully accessible Mar 03 10:25:19 pc kernel: ata2.00: configured for UDMA/133 Mar 03 10:25:19 pc kernel: ata2: EH complete Mar 03 10:25:19 pc kernel: ata2.00: Enabling discard_zeroes_data [...] Mar 03 10:25:19 pc systemd-coredump[30527]: Process 28448 (systemd-journal) of user 0 dumped core. Mar 03 10:25:19 pc systemd-coredump[30527]: Coredump diverted to /var/lib/systemd/coredump/core.systemd-journal.0.92bd8e3e91344ef998c2c08ade695cd2.28448.1583227313000000.lz4 Mar 03 10:25:19 pc systemd-coredump[30527]: Stack trace of thread 28448: Mar 03 10:25:19 pc systemd-coredump[30527]: #0 0x00007f52360114f5 journal_file_move_to_object (libsystemd-shared-234.so) Mar 03 10:25:19 pc systemd-coredump[30527]: #1 0x00007f5236012f00 n/a (libsystemd-shared-234.so) Mar 03 10:25:19 pc systemd-coredump[30527]: #2 0x00007f5236013548 n/a (libsystemd-shared-234.so) Mar 03 10:25:19 pc systemd-coredump[30527]: #3 0x00007f523601470d journal_file_append_entry (libsystemd-shared-234.so) [...] Mar 03 10:25:54 pc systemd-journald[30532]: Journal stopped Mar 03 10:26:38 pc systemd-journald[30532]: Received SIGTERM from PID 1 (systemd). Mar 03 10:26:38 pc systemd-journald[30545]: Journal started Mar 03 10:26:38 pc systemd-journald[30545]: System journal (/var/log/journal/89c660865c00403a9bacef32b6828556) is 856.0M, max 819.2M, 0B free. [...] >From this point on I did not see any more ATA errors, but the system was still unusable, so I hit Reset: Mar 03 10:55:58 pc kernel: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=00:22:11:dd:00:11:a0:36:9f:b2:3f:25:08:00 SRC=1.9.154.170 1.9.5.2 LEN=44 TOS=0x00 PREC=0x00 TTL=5 6 ID=52696 PROTO=TCP SPT=47944 DPT=655 WINDOW=1024 RES=0x00 SYN URGP=0 OPT (020405B4) -- Reboot -- Mar 03 11:05:24 linux-abcd kernel: Linux version 4.12.14-lp151.28.36-default (geeko@buildhost) (gcc version 7.4.1 20190905 [gcc-7-branch revision 275407] (SUSE Linux) ) #1 SMP Fri Dec 6 13:50:27 UTC 2019 (8f4a495) Final note: The IP address and related identifyable information in the log has been anonymized for privacy. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1063638] New: btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance
by bugzilla_noreply＠novell.com 23 Sep '21

23 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1063638 Bug ID: 1063638 Summary: btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de CC: Antoine.Saroufim(a)gmail.com, aschnell(a)suse.com, auxsvr(a)gmail.com, dmitry(a)roshchin.org, dsterba(a)suse.com, ecsos(a)schirra.net, enadolski(a)suse.com, fcrozat(a)suse.com, fliu(a)suse.com, friedhelm.stappert(a)web.de, guenther(a)mpanrw.de, gweberbh(a)gmail.com, hannsj_uhl(a)de.ibm.com, harald.achitz(a)gmail.com, ingo.goeppert+suse(a)mailbox.org, jeffm(a)suse.com, kdejaeger(a)gmail.com, lnussel(a)suse.com, lpechacek(a)suse.com, ndcunliffe(a)gmail.com, okurz(a)suse.com, ortsacs(a)yahoo.es, rgoldwyn(a)suse.com, richard(a)nod.at, ronisbr(a)gmail.com, slindomansilla(a)suse.com, suse(a)bugs.jan.ritzerfeld.org, sven.heithecker(a)web.de, t.rother(a)netzwissen.de, tneo(a)gmx.com, ulrich.hobelmann+suse(a)gmail.com Depends on: 1017461 Found By: --- Blocker: --- ## Observation +++ This bug was initially created as a clone of Bug #1017461 +++ The first part of fixes have been done in bug 1017461 but it seems the btrfs maintenance tasks can still have a significant impact on system responsiveness. Running the btrfs maintenance jobs, e.g. * /etc/cron.monthly/btrfs-scrub * /etc/cron.weekly/btrfs-balance * /etc/cron.weekly/btrfs-trim can make the clock with seconds displayed stop for some seconds or the mouse cursor to get stuck for seconds ## Reproducible * Somehow cause lot of "dirty" data that needs balancing/scrubbing * Run the cron jobs * Observe the system responsiveness is hindered ## Expected result Interactive use of a machine should not be impacted ## Suggestion It looks like /usr/share/btrfsmaintenance/btrfs-scrub.sh checks for the variable "$BTRFS_SCRUB_PRIORITY" equalling "normal" from /etc/sysconfig/btrfsmaintenance but this is set to "idle" for me in the config file which causes that no I/O scheduling parameters are forwarded to the call of scrub at all which does not seem to make sense to me. Should it set `-c 3` for idle or `-c 2 -n 7` for best-effort prio 7 instead? -- You are receiving this mail because: You are on the CC list for the bug.

2 109

[Bug 1106850] New: xfig crashes if noto-sans-cjk-fonts are installed
by bugzilla_noreply＠novell.com 20 Sep '21

20 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1106850 Bug ID: 1106850 Summary: xfig crashes if noto-sans-cjk-fonts are installed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After I install the fonts noto-sans-cjk-fonts, when I start xfig I got these warnings in the terminal: Warning: Missing charsets in String to FontSet conversion Warning: Cannot convert string "-URW-Nimbus Roman No9 L-medium-r-normal--34-*-*-*-*-*-*-*,-kochi-mincho-medium-r-normal--34-*-*-*-*-*-jisx0208.1983-0,-baekmukttf-batang-medium-r-normal--34-*-*-*-*-*-ksc5601.1987-0,-*-times-medium-r-normal--34-*-*-*-*-*-*-*,-*-*-medium-r-normal--34-*-*-*-*-*-*-*,*--34-*-*-times-medium-r-normal--16-*-*-*-*-*-*-*,-*-*-medium-r-normal--16-*-*-*-*-*-*-*,*--16-*" to type FontSet Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset Warning: Missing charsets in String to FontSet conversion Warning: Unable to load any usable fontset and when I select File->Open (or Merge or Save As or Export) xfig crashes and print this error message: Error: Aborting: no fontset found If I remove all the noto-sans-cjk-fonts, then xfig works again. Whatever is causing the problem apparently it got fixed in tumbleweed (xfig works fine also with noto-sans-cjk-fonts installed). It would be good to apply the fix to 15.0 too. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1008682] New: Login difficulties with LXDM 0.5.3
by bugzilla_noreply＠novell.com 17 Sep '21

17 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1008682 Bug ID: 1008682 Summary: Login difficulties with LXDM 0.5.3 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: LXDE Assignee: andrea(a)opensuse.org Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I would like to achieve another graphical login with the software “LX Display Manager 0.5.3-1.1”. Unfortunately, I observed that it did not work as expected. -- You are receiving this mail because: You are on the CC list for the bug.

2 1