July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1226458] New: guix problem when installing/building some packages
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226458 Bug ID: 1226458 Summary: guix problem when installing/building some packages 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: javier_vm(a)protonmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I wanted to install a package form a git repo. So I created my own package manifest and did `guix package -m package.scm`. It fetched all dependencies but then I got this error: ``` guix build: error: while setting up the build environment: getting attributes of path `/etc/services': No such file or directory ``` I could solve it after `touch /etc/services`. Not sure why guix needs this at all (it has not written anything on the file). But it needs it, so I suggest the file is created in the package installation. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1226279] New: kernel panic in systemd-testsuite VM after switch_root
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226279 Bug ID: 1226279 Summary: kernel panic in systemd-testsuite VM after switch_root Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)suse.de Reporter: thomas.blume(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Running the systemd-testsuite with next systemd update from: https://download.opensuse.org/repositories/home:/fbui:/systemd:/v256/openSU… results in a kernel panic after switch root: --> [ OK ] Reached target Switch Root. Starting Switch Root... [ 33.072568][ T173] systemd-journald[173]: Received SIGTERM from PID 1 (systemd). [ 33.505266][ T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [ 33.505803][ T1] CPU: 0 PID: 1 Comm: systemd Not tainted 6.9.3-1-default #1 openSUSE Tumbleweed fda7b62a76dc21b6c4b75014796eda70ffed4444 [ 33.506381][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 [ 33.506841][ T1] Call Trace: [ 33.507470][ T1] <TASK> [ 33.507702][ T1] dump_stack_lvl+0x5a/0x80 [ 33.508279][ T1] panic+0x10b/0x2be [ 33.508419][ T1] do_exit.cold+0x14/0x14 [ 33.508555][ T1] ? __slab_free+0xbf/0x2a0 [ 33.508700][ T1] do_group_exit+0x30/0x80 [ 33.508856][ T1] __x64_sys_exit_group+0x18/0x20 [ 33.509033][ T1] do_syscall_64+0x82/0x170 [ 33.509175][ T1] ? __memcg_slab_free_hook+0xef/0x140 [ 33.509345][ T1] ? update_load_avg+0x7e/0x7e0 [ 33.509506][ T1] ? update_load_avg+0x7e/0x7e0 [ 33.509659][ T1] ? set_next_entity+0xd0/0x190 [ 33.509809][ T1] ? finish_task_switch.isra.0+0x99/0x2e0 [ 33.509986][ T1] ? __schedule+0x3d0/0x15b0 [ 33.510131][ T1] ? rcu_core+0x1f2/0x4b0 [ 33.510267][ T1] ? lapic_next_event+0x15/0x20 [ 33.510424][ T1] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 33.510729][ T1] RIP: 0033:0x7fd4c32ca1c5 [ 33.511135][ T1] Code: 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 90 90 ba e7 00 00 00 eb 06 0f 1f 44 00 00 f4 89 d0 0f 05 <48> 3d 00 f0 ff ff 76 f3 f7 d8 89 05 5b 49 01 00 eb e9 66 0f 1f 84 [ 33.511740][ T1] RSP: 002b:00007ffd5cbfa068 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7 [ 33.512374][ T1] RAX: ffffffffffffffda RBX: 00007fd4c32d33c8 RCX: 00007fd4c32ca1c5 [ 33.512623][ T1] RDX: 00000000000000e7 RSI: 00007ffd5cbf9730 RDI: 000000000000007f [ 33.512873][ T1] RBP: 00007fd4c323eaaf R08: 0000000000000001 R09: ffffffffffffffff [ 33.513112][ T1] R10: 00007fd4c329f000 R11: 0000000000000202 R12: 0000000000000002 [ 33.513351][ T1] R13: 000000000000000f R14: 00007fd4c323eac0 R15: 0000000000000000 [ 33.513625][ T1] </TASK> [ 33.514204][ T1] Kernel Offset: 0x28a00000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 33.514734][ T1] Rebooting in 90 seconds.. --< The panic doesn't appear when adding a -cpu parameter with model Haswell or newer (see https://www.qemu.org/docs/master/system/qemu-cpu-models.html section: "Preferred CPU models for Intel x86 hosts" for details), e.g.: /usr/bin/qemu-system-x86_64 -m 1024M -nographic -cpu Haswell -kernel /boot/vmlinuz-6.9.3-1-default -initrd /boot/initrd-6.9.3-1-default -drive format=raw,cache=unsafe,file=/var/tmp/systemd-tests/default.img -append 'root=LABEL=systemd_boot console=ttyS0' succeeds, but: /usr/bin/qemu-system-x86_64 -m 1024M -nographic -cpu IvyBridge -kernel /boot/vmlinuz-6.9.3-1-default -initrd /boot/initrd-6.9.3-1-default -drive format=raw,cache=unsafe,file=/var/tmp/systemd-tests/default.img -append 'root=LABEL=systemd_boot console=ttyS0' panics. Reproducer: 1. Install systemd and systemd-testsuite from: https://download.opensuse.org/repositories/home:/fbui:/systemd:/v256/openSU… 2. go to testsuite directory and create the test image: cd /usr/lib/systemd/tests/integration-tests/ NO_BUILD=1 make -C TEST-02-UNITTESTS QEMU_TIMEOUT=90 clean setup 3. run the above qemu-system-x86_64 command with a -cpu parameter IvyBridge or older -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1222695] lensfun‑update‑data command does not work
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222695 https://bugzilla.suse.com/show_bug.cgi?id=1222695#c2 Valentin Lefebvre <valentin.lefebvre(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |valentin.lefebvre(a)suse.com --- Comment #2 from Valentin Lefebvre <valentin.lefebvre(a)suse.com> --- (In reply to Andreas from comment #0) > The lensfun‑update‑data command does not work. To update the lensfun > database, you need to specify the full path to the program > /usr/bin/lensfun-update-data Thanks for the report. Andreas, could you please provide more information about the issue you are facing ? Are there any logs ? Which version did you used ? `rpm -qa lensfun-tools`. I just tested on a fresh Leap container with `lensfun-tools-0.3.2-150400.3.2.2.x86_64` and no errors come trough. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225994] New: [Build 20240605-2] gnuhealth starts failed with "trytond" package version=6.0.46
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225994 Bug ID: 1225994 Summary: [Build 20240605-2] gnuhealth starts failed with "trytond" package version=6.0.46 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 URL: https://openqa.opensuse.org/tests/4249991/modules/gnuh ealth_setup/steps/14 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: richard.fan(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes Created attachment 875322 --> https://bugzilla.suse.com/attachment.cgi?id=875322&action=edit screen shot ## Description With "trytond" package version= "6.0.46", I can see below error messages in gnuhealth tests, please see attached file. I did some investigation and try to downgrade the package version to "6.0.38", the issue is gone. see openqa result. can you please help confirm? please let me know if you need to access my setup to debug. ## Observation openQA test in scenario opensuse-15.5-DVD-Updates-x86_64-gnuhealth@64bit fails in [gnuhealth_setup](https://openqa.opensuse.org/tests/4249991/modules/gnuhealt… ## Test suite description Maintainer: community packages Test scenario for gnuhealth software stack. * 2020-11-17: Temporarily added `QEMUCPU=host` needed to prevent openCV crashes within the SUT, see [boo#1178453](https://bugzilla.opensuse.org/show_bug.cgi?id=1178453) but I removed it again to not hide the product issue. * 2021-03-12: Added `QEMUCPU=host` again as there was no better solution found so far. ## Reproducible Fails since (at least) Build [20240520-3](https://openqa.opensuse.org/tests/4208876) ## Expected result Last good: [20240520-2](https://openqa.opensuse.org/tests/4208599) (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 11

[Bug 1227259] Upgrade of mariadb creates new system table files as owner "root" when it needs to be "mysql"
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227259 Lukas Ocilka <locilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de Assignee|yast2-maintainers(a)suse.de |screening-team-bugs(a)suse.de Component|Installation |Other -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227265] New: windows:mingw:win{32|64}/mingw{32|64}-gdb:conflicts with file from install mingw32|64-binutils
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227265 Bug ID: 1227265 Summary: windows:mingw:win{32|64}/mingw{32|64}-gdb:conflicts with file from install mingw32|64-binutils Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: ralf.habacker(a)freenet.de Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: mkbosmans(a)gmail.com Target Milestone: --- Found By: --- Blocker: --- File /usr/x86_64-w64-mingw32/sys-root/mingw/share/info/sframe-spec.info.gz from install of mingw64-binutils-2.42-lp155.33.1.noarch (Cross-toolchain for 64-bit windows and 64-bit windows packages) conflicts with file from install of mingw64-gdb-14.2-lp155.1.6.noarch (Cross-toolchain for 64-bit windows and 64-bit windows packages) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1226065] New: Trackpad does not work after suspend/resume
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226065 Bug ID: 1226065 Summary: Trackpad does not work after suspend/resume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: David(a)WalkerStreet.info QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The trackpad on my Framework Gen 11 laptop stopped working after a suspend/resume cycle. The problem turned out to be that I had accidentally enabled secure boot: Jun 06 19:18:01 homelap8.WalkerStreet.info kernel: mousedev: PS/2 mouse device common for all mice Jun 06 19:18:05 homelap8.WalkerStreet.info kernel: Lockdown: vmmouse_detect: raw io port access is restricted; see man kernel_lockdown.7 Disabling secure boot fixes the trackpad problem and eliminates the lockdown log message. It looks like there's some issue in mousedev when secure boot is enabled. -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 1227221] Blank Screen After Booting Kernel 6.4.0-150600.23.7.3 Post Leap Logo on MacBook Pro 5.1
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227221 https://bugzilla.suse.com/show_bug.cgi?id=1227221#c23 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jacopo.radice@out | |look.com) | Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #23 from Takashi Iwai <tiwai(a)suse.com> --- Good to hear! As long as it's working, no need for further debugging. Let's close. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215633] gvfs-udisks2-volume-monitor crashes, causing delays in applications
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1215633 https://bugzilla.suse.com/show_bug.cgi?id=1215633#c16 Alynx Zhou <alynx.zhou(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |UPSTREAM Status|NEW |RESOLVED --- Comment #16 from Alynx Zhou <alynx.zhou(a)suse.com> --- Could we close this if no crash is happening now? The GFileInfo output seems related to this bug: https://gitlab.gnome.org/GNOME/gimp/-/issues/9994, and should be fixed upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227260] New: [Build 20240701-3] leap 15.6 system role 'Transactional Server' is missing, is it by design
by bugzilla_noreply＠suse.com 02 Jul '24

02 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227260 Bug ID: 1227260 Summary: [Build 20240701-3] leap 15.6 system role 'Transactional Server' is missing, is it by design Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other URL: https://openqa.opensuse.org/tests/4311967/modules/syst em_role/steps/6 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: richard.fan(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes Created attachment 875818 --> https://bugzilla.suse.com/attachment.cgi?id=875818&action=edit screenshot ## Description During the leap15.6 installation, I can't see 'Transactional Server' system role any more, is it by design? Please see attached file. Thanks ## Observation openQA test in scenario opensuse-15.6-DVD-Updates-x86_64-create_hdd_transactional_server@64bit fails in [system_role](https://openqa.opensuse.org/tests/4311967/modules/system_role/… ## Test suite description create qcow2 image for extra_tests_transactional_server. Maintainer: Zaoliang Luo <zluo(a)suse.com> ## Reproducible Fails since (at least) Build [20240501-1](https://openqa.opensuse.org/tests/4121908) ## Expected result Last good: (unknown) (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 5