November 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1197556] New: gnome42 completely unusable on Lenovo P15
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1197556 Bug ID: 1197556 Summary: gnome42 completely unusable on Lenovo P15 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: donald.vosburg(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Logging into GNOME on Lenovo P15 with DockStation results in hung system unable to launch applications. Keyboard and mouse become unresponsive, networking on dock gets disabled, and the only alternative is hard power-off. Using plasma on the same OS on the same hardware works perfectly. -- You are receiving this mail because: You are on the CC list for the bug.

1 20

[Bug 1198547] New: power-profiles-daemon package is missing in Leap 15.4
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1198547 Bug ID: 1198547 Summary: power-profiles-daemon package is missing in Leap 15.4 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- One of the main features of the new LTS Plasma was power profiles, but this package is missing in Leap 15.4. Is it possible to add it? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1176566] New: Installing ignition leads to unbootable system
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1176566 Bug ID: 1176566 Summary: Installing ignition leads to unbootable system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I've installed ignition locally on Tumbleweed, to be able to validate ignition files locally. After a reboot I was presented with an emergency shell, leading down a wild goose chase for disabling ignition permanently. It all went away after setting up a chroot and removing all traces of ignition, but it would be much much better if installing it would not lead to a broken system by default. I saw some errors related to the ignition generator, and the systemd unit file was broken, but could not save any logs unfortunately. But it should be easy enough to reproduce if anyone cares: # zypper in ignition # reboot (Might be related to #1172592) -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1200955] New: ansible-lint broken: ModuleNotFoundError: No module named 'ansiblelint'
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200955 Bug ID: 1200955 Summary: ansible-lint broken: ModuleNotFoundError: No module named 'ansiblelint' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: felix.niederwanger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The ansible-lint package on Tumbleweed complains about the missing ansiblelint module: > phoenix@racetrack-7290:~/Projects/geekoops> ansible-lint > Traceback (most recent call last): > File "/usr/bin/ansible-lint", line 5, in <module> > from ansiblelint.__main__ import _run_cli_entrypoint > ModuleNotFoundError: No module named 'ansiblelint' -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1200542] New: Regional preferences error with "default" locale
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200542 Bug ID: 1200542 Summary: Regional preferences error with "default" locale Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: smartinds(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859593 --> http://bugzilla.opensuse.org/attachment.cgi?id=859593&action=edit Screenshot with the solution When I configure in: Preferences > Formats > Region > es_PE (Per�) Result: Many of the details (Numbers, Date, Money) are in "Default" so if I save the config: $ locale locale: Cannot set LC_ALL to default locale: No existe el fichero o el directorio (Don't exist the file or directory) Also, some apps in python show error: locale.Error: unsupported locale setting BUT, if I config each detail with es_PE, all is OK. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1200391] New: Add country flag to the calendar in digital clock
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200391 Bug ID: 1200391 Summary: Add country flag to the calendar in digital clock Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: smartinds(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 859507 --> http://bugzilla.opensuse.org/attachment.cgi?id=859507&action=edit screenshot When I configure two or more calendars en the clock, the holidays of different countries are confusing BUT if flags are added it would be solved. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1189826] New: Severe screen flickering with kernel 5.13.12-1-default and i915
by bugzilla_noreply＠suse.com 12 Mar '23

12 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1189826 Bug ID: 1189826 Summary: Severe screen flickering with kernel 5.13.12-1-default and i915 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: javier(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My laptop's screen flickers so much with 5.13.12 that it renders my laptop unusable. One workaround is to close and open the lid. After resuming, it works fine - there is no flickering. Booting up from the KDE Live image works fine. I have used the same Tumbleweed version (20210820) as the one I have installed on my laptop. The only difference is that I have an encrypted /home partition on my laptop's SSD. Tested kernels: 5.10.16-1.3: OK 5.11.4-1.3: NON-OK 5.12.12-1: NON-OK 5.13.12-1: NON-OK KDE Plasma 5.22.4 KDE Frameworks 5.85.0 Qt 5.15.2 See the attachments for more details. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1204007] New: Use region-specific variant of noto sans/serif cjk fonts, not language-specific ones as source
by bugzilla_noreply＠suse.com 10 Mar '23

10 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1204007 Bug ID: 1204007 Summary: Use region-specific variant of noto sans/serif cjk fonts, not language-specific ones as source Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: i(a)marguerite.su QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I am the initial packager of google-noto-sans/serif-CJK-fonts and the maintainer of our fonts-config. In the early version of that package, I used region-specific variants. Later Mr. hillwood replaced them with language-specific variants and accepted the submit request by himself, then guoyunhe continued to update that package with language specific ones There is a known bug back in 2016 that Japanese variant wll always take effect due to the alphabetical order so you can not see any chinese variant. Nowadays in 2022, although pango/harfbuzz/freetype support opentype locl feature and language tagging underlying, this regression still exists because: 1. All Qt applications don��t support any opentype features because QFont doesn��t implemented such things 2. GTK supports them but rare application made use of that, eg: GIMP still can��t use opentype features although GTKFontChooser allows such usage since 3.24 3. Such usage needs programming, it does not mean users can simply set up font variant in system settings and the Simplified Chinese variant will apply everywhere. Every application/web page needs to enable opentype locl features during programming. So only professional application like Adobe CS 6 may adapt to it. We will not see it work out of the box in the foreseeable future. So the only benefit of using language-specific variants is its code point coverage, but seldom people needs to display Pan CJK everyday while everyone hates to see Japanese variant in charge under non-Japanese locales And openSUSE��s fonts-config were implemented with region-specific font names eg ��Noto Sans SC�� not ��Noto Sans CJK SC��. such packaging nearly destroyed those font configurations Please fix -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1084017] New: YaST in Leap 15 fails to set boot flags correctly
by bugzilla_noreply＠novell.com 10 Mar '23

10 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=1084017 Bug ID: 1084017 Summary: YaST in Leap 15 fails to set boot flags correctly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: Larry.Finger(a)lwfinger.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 762755 --> http://bugzilla.suse.com/attachment.cgi?id=762755&action=edit Compressed YaST2 logs My system has a GPT partitioning scheme and does not use EFI. I also put the boot block at the start of the active partition, and have generic boot code in the MBR. The active partition is indicated with the legacy_boot flag. A partial df for the system is: Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 60213124 9954072 47170668 18% / /dev/sda6 53826316 32795236 20576144 62% /var/tmp /dev/sda7 51255784 20631016 28050216 43% /TW /dev/sda4 60344404 22760752 36522788 39% /Leap42.3 /dev/sda5 711705020 393141448 282387980 59% /home tmpfs 809360 20 809340 1% /run/user/1000 Looking at the partitions with parted: GNU Parted 3.2 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: ATA Samsung SSD 850 (scsi) Disk /dev/sda: 1024GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: pmbr_boot Number Start End Size File system Name Flags 1 1049kB 9437kB 8389kB bios_grub 2 9437kB 16.8GB 16.8GB linux-swap(v1) swap 3 16.8GB 79.7GB 62.9GB ext4 4 79.7GB 143GB 62.9GB ext4 msftdata 5 143GB 883GB 741GB ext4 msftdata 6 883GB 939GB 56.1GB ext4 msftdata 8 939GB 971GB 31.5GB ext4 7 971GB 1024GB 53.5GB ext4 legacy_boot, msftdata (parted) quit In this case, partition number 7 will be booted. Running YaST => System => Boot Loader changes nothing. If I want the automatic boot to choose Leap 15.0, I need to manually toggle the legacy_boot flag on partitions 7 and 3. Attached is a compressed copy of the /var/log/YaST2/ directory. -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1204333] New: syslog-ng: Error opening file for writing; filename='/dev/tty1', error='Permission denied (13)'
by bugzilla_noreply＠suse.com 10 Mar '23

10 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1204333 Bug ID: 1204333 Summary: syslog-ng: Error opening file for writing; filename='/dev/tty1', error='Permission denied (13)' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Yesterday I updated my Tumbleweed machine after a few weeks of vacation. Since then I get this error message every so often: syslog-ng: Error opening file for writing; filename='/dev/tty1', error='Permission denied (13)' I checked the syslog-ng apparmor file, but it still contains /dev/tty1 rw, ls -l /dev/tty1 crw--w---- 1 root tty 4, 1 Oct 15 12:43 /dev/tty1 I'm not sure, if and how the permissions for /dev/tty1 have been changed, though. They seem to be identical on other machines, where syslog doesn't give that error message. -- You are receiving this mail because: You are on the CC list for the bug.

1 4