September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1203084] New: Brightness keys not working in Plasma in Panasonic CF-AX2
by bugzilla_noreply＠suse.com 03 Sep '22

03 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203084 Bug ID: 1203084 Summary: Brightness keys not working in Plasma in Panasonic CF-AX2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: email(a)chanjp.me QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a Panasonic CF-AX2, installed with the latest (at this time of publishing) version of Tumbleweed, the brightness keys appear to fail to work on KDE Plasma despite showing the brightness indicator on-screen. Probing with ls /sys/class/backlight/ showed two options: intel_backlight panasonic Using echo 800 | sudo tee /sys/class/backlight/intel_backlight/brightness I was able to change the brightness on my screen, but not when the options were passed to "panasonic" as the brightness keys were doing. Further investigation using the `brightnessctl -l` command to see and set brightness confirmed brightness values were being pushed to one device only (panasonic), and not the one that actually affected brightness ("intel_backlight). As an interesting aside, I installed the Enlightenment desktop environment which as part of its boot-up process, popped up a message about acpi I couldn't catch fast enough and automagically just worked for brightness control. While trying to fix this bug, I encountered this entry for Powerdevil in KDE which seems to indicate that this kind of behaviour should be fixed when encountering multiple backlight devices. https://invent.kde.org/plasma/powerdevil/-/commit/761fc8a4bf4bd70bcd9aca63f… Fix: Adding the following to the kernel boot option resolves the issue: acpi_osi=linux acpi_backlight=video The second entry is probably the most important of the two options, but I figured I might as well play it safe with both acpi options. After confirming brightness toggle now works, ls /sys/class/backlight/ Now shows: acpi_video0 intel_backlight panasonic -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200544] xbell no longer working
by bugzilla_noreply＠suse.com 03 Sep '22

03 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1200544 https://bugzilla.suse.com/show_bug.cgi?id=1200544#c21 --- Comment #21 from Takashi Iwai <tiwai(a)suse.com> --- The previous kernel is still kept on the system after installing a new test kernel, and you can choose which kernel to boot at GRUB menu, so there is little risk. At best, download kernel-default, kernel-default-extra and kernel-default-optional rpm packages from the repo, and install those via zypper install % zypper install kernel-default*.rpm You might need to pass --oldpackage option to zypper install due to the nature of a rpm packaging. Once after testing, you can uninstall those package again via zypper rm. % zypper rm kernel-default-5.14.21-150400.1.1.g203aa60 (which will uninstall all three packages in a shot) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203083] New: Since Tumbleweed 20220831, PackageKit runs forever whenever I log into X
by bugzilla_noreply＠suse.com 03 Sep '22

03 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203083 Bug ID: 1203083 Summary: Since Tumbleweed 20220831, PackageKit runs forever whenever I log into X Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: screening-team-bugs(a)suse.de Reporter: antoine.mechelynck(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: Community User Blocker: --- I'm not sure I'm filing this bug where it belongs; feel free to move it if not. There was yesterday an enormous update (more than 10700 packages) to Tumbleweed. Before then, when I logged into X, PackageKit ran for some minutes and then stopped, so I could (once it had stopped) run zypper in a konsole terminal. After rebooting from this enormous update, PackageKit runs forever (or at least for hours) whenever I log into X, so I cannot anymore run zypper in konsole because PackageKit is locking the library. Temporary solution: 1. Log out of X and log in to a text console 2. Wait a few seconds and make sure that process "Zypp-main" has gone away. 3. zypper rm PackageKit (written in CamelCase; and answer yes when it asks for confirmation) 4. Log back into X. Now that PackageKit has been uninstalled, it won't misbehave. P.S. "Tumbleweed 20220831" comes from the greeting I get now in text consoles, inviting me to log in. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1200544] xbell no longer working
by bugzilla_noreply＠suse.com 03 Sep '22

03 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1200544 https://bugzilla.suse.com/show_bug.cgi?id=1200544#c20 --- Comment #20 from GDPR Deletion <agesen(a)cs.stanford.edu> --- Thank you Takashi-san. I may need a bit of guidance for how to apply the experimental kernel. I'm happy to try it out once, but if it somehow doesn't work, how do I prevent my computer from going bad? Is there a try-once-and-automatically revert approach? Also, how do I get from http://download.opensuse.org/repositories/home:/tiwai:/bsc1200544/pool/ to a live, booted kernel on my laptop? Thanks, Ole -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203047] New: package for Huion graphic tablet
by bugzilla_noreply＠suse.com 02 Sep '22

02 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203047 Bug ID: 1203047 Summary: package for Huion graphic tablet Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: opensuse(a)titlis.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please add support for Huion graphic tablets. Huion offers official linux support since April 2022 and is regularly updating the driver since. Unfortunately, the driver is only available as deb pkg and as source pkg (tar.xz) Huion tablets: https://www.huion.com Driver change log: https://www.huion.com/dowload/driver-update-log.html Newest driver: https://driverdl.huion.com/driver/X10_G930L_Q630M/HuionTablet_v15.0.0.103.2… The last link seems to be in a product specific web folder, but I assume this is the same driver for all Huion products -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1194610] VUL-0: CVE-2021-43860: flatpak: Permissions granted to applications can be hidden from the user at install time
by bugzilla_noreply＠suse.com 02 Sep '22

02 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1194610 Michael Gorse <mgorse(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mgorse(a)suse.com Assignee|gnome-bugs(a)suse.de |mgorse(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1191507] VUL-0: CVE-2021-41133: flatpak: Sandbox bypass via recent VFS-manipulating syscalls
by bugzilla_noreply＠suse.com 02 Sep '22

02 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1191507 Michael Gorse <mgorse(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mgorse(a)suse.com Assignee|gnome-bugs(a)suse.de |mgorse(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203081] New: the power source does not use a battery
by bugzilla_noreply＠suse.com 02 Sep '22

02 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203081 Bug ID: 1203081 Summary: the power source does not use a battery Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: shukrullojon.dev(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- in the battery status it is always shows charging when the power is not connected -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1202798] manpages-l10n creates sigsuspend.2.gz.gz symlinks
by bugzilla_noreply＠suse.com 02 Sep '22

02 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202798 http://bugzilla.opensuse.org/show_bug.cgi?id=1202798#c6 Antoine Belvire <antoine.belvire(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #6 from Antoine Belvire <antoine.belvire(a)opensuse.org> --- Fixed in both Tumbleweed and Leap 15.4. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203077] New: k3d build fails because of go panic
by bugzilla_noreply＠suse.com 02 Sep '22

02 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203077 Bug ID: 1203077 Summary: k3d build fails because of go panic Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- k3d builds are failing for all architectures because of a panic in go. https://build.opensuse.org/package/live_build_log/openSUSE:Factory:zSystems… [ 230s] panic: Something in this program imports go4.org/unsafe/assume-no-moving-gc to declare that it assumes a non-moving garbage collector, but your version of go4.org/unsafe/assume-no-moving-gc hasn't been updated to assert that it's safe against the go1.19 runtime. If you want to risk it, run with environment variable ASSUME_NO_MOVING_GC_UNSAFE_RISK_IT_WITH=go1.19 set. Notably, if go1.19 adds a moving garbage collector, this program is unsafe to use. [ 230s] [ 230s] goroutine 1 [running]: [ 230s] go4.org/unsafe/assume-no-moving-gc.init.0() -- You are receiving this mail because: You are on the CC list for the bug.

1 0