September 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1203270] New: Samba 4.16.4+git.297.1497eb221ed-1.4 causes "Invalid argument" errors from NVidia Shield and Nautilus
by bugzilla_noreply＠suse.com 09 Sep '22

09 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203270 Bug ID: 1203270 Summary: Samba 4.16.4+git.297.1497eb221ed-1.4 causes "Invalid argument" errors from NVidia Shield and Nautilus Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: David(a)WalkerStreet.info QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- Attempts to mount authenticated shares from Samba 4.16.4+git.297.1497eb221ed-1.4 on Tumbleweed 20220907 result in "Invalid argument" errors. This occurs both for NVidia Shield Pro clients and Tumbleweed's current Nautilus (with gvfs-backend-samba 1.50.2-2.2). This is very similar to bug #1199973, which seems to be mostly resolved, though not closed. This bug, however, involves an additional client, as well as more recent software on Tumbleweed, as opposed to Leap. Sorry if this should have been an update to that previous bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203257] New: devel:languages:rust/rustup: Missing symlink for rust-analyzer
by bugzilla_noreply＠suse.com 09 Sep '22

09 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203257 Bug ID: 1203257 Summary: devel:languages:rust/rustup: Missing symlink for rust-analyzer Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: federico(a)suse.com Reporter: siegeltr(a)gmail.com QA Contact: screening-team-bugs(a)suse.de CC: alarrosa(a)suse.com, aplanas(a)suse.com, william.brown(a)suse.com Found By: --- Blocker: --- This package creates symlinks in /usr/bin/rust* -> rustup for the programs managed by rustup. But it leaves out rust-analyzer, which is available with current Rust versions. See ~/.rustup/toolchains/*/bin/*, the only one missing for the current toolchain is rust-analyzer. ``` trs@jelly:/usr/bin/ > ls ~/.rustup/toolchains/*/bin cargo cargo-fmt rust-analyzer rustdoc rust-gdb rust-lldb cargo-clippy clippy-driver rustc rustfmt rust-gdbgui trs@jelly:/usr/bin/ > rustup show Default host: x86_64-unknown-linux-gnu rustup home: /home/trs/.rustup nightly-x86_64-unknown-linux-gnu (default) rustc 1.65.0-nightly (c2804e6ec 2022-09-07) trs@jelly:/usr/bin/ > Information for package rustup: ------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : rustup Version : 1.25.1~0-1.2 Arch : x86_64 Vendor : openSUSE Installed Size : 8.8 MiB Installed : Yes Status : up-to-date Source package : rustup-1.25.1~0-1.2.src Upstream URL : https://github.com/rust-lang/rustup Summary : A tool for managing user Rust toolchains Description : A tool to manager user Rust toolchains. This is generally used by developers managing multiple parallel toolchains in their environment. trs@jelly:/usr/bin/ > ls -l /usr/bin/rustc lrwxrwxrwx 1 root root 6 Aug 31 12:07 /usr/bin/rustc -> rustup trs@jelly:/usr/bin/ > ls -l /usr/bin/rust-analyzer ls: cannot access '/usr/bin/rust-analyzer': No such file or directory trs@jelly:/usr/bin/ > ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1202206] qemu-kvm ignores -rtc param
by bugzilla_noreply＠suse.com 09 Sep '22

09 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1202206 Borislav Petkov <bpetkov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bpetkov(a)suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203266] New: Request for inclusion of the GEOPM Service in OpenSUSE Factory
by bugzilla_noreply＠suse.com 08 Sep '22

08 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203266 Bug ID: 1203266 Summary: Request for inclusion of the GEOPM Service in OpenSUSE Factory Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: Bugzilla Assignee: screening-team-bugs(a)suse.de Reporter: christopher.m.cantalupo(a)intel.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- The GEOPM Service software is openly developed and maintained by Intel: https://geopm.github.io/service.html The GEOPM developers use the OpenSUSE instance of the OBS service to build and distribute our packages: https://geopm.github.io/install.html HPE, Argonne National Lab, and the Leibniz Supercomputing Centre are all SUSE customers that are interested in using the GEOPM Service packages. The GEOPM developers would be grateful if these customers were able to obtain the GEOPM Service packages from the SUSE family of distributions rather than from the home:geopm project. An example of the GEOPM Service v2.0.0 build for OpenSUSE Tumbleweed is available here: https://build.opensuse.org/package/show/home:cmcantal/geopm-service Alejandro Vilches <alejandro.vilches(a)intel.com> is also a point of contact for this request. Thanks! Chris Cantalupo -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1203252] virt-manager regression - cannot add second virtio-scsi controller
by bugzilla_noreply＠suse.com 08 Sep '22

08 Sep '22

https://bugzilla.suse.com/show_bug.cgi?id=1203252 Charles Arnold <carnold(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|virt-bugs(a)suse.de |carnold(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181243] New: accounts-daemon[1065]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
by bugzilla_noreply＠suse.com 08 Sep '22

08 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1181243 Bug ID: 1181243 Summary: accounts-daemon[1065]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: suseino(a)riseup.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 845399 --> http://bugzilla.opensuse.org/attachment.cgi?id=845399&action=edit journal This error shows up in journal: accounts-daemon[1065]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed Attaching journal excerpt. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1180621] New: fritzing fails to load parts
by bugzilla_noreply＠suse.com 08 Sep '22

08 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180621 Bug ID: 1180621 Summary: fritzing fails to load parts 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: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The starting up fritzing ( fritzing-0.9.4-1.4.x86_64 ) I get the following error dialog: Title: Regenerating parts database Contents: Unable to find parts git repository I press OK to continue and am prompted with multiple error dialogs such as: - "Cannot read screw_terminal_2_3.5mm.fzp: No such file or directory." - "Unable to find the following 143 parts..." Fritzing then starts up but there are no parts to add to the sketches. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202534] New: After 5.19 upgrade, system does not shutdown to reboot complaining about blkdev_get_no_open
by bugzilla_noreply＠suse.com 08 Sep '22

08 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202534 Bug ID: 1202534 Summary: After 5.19 upgrade, system does not shutdown to reboot complaining about blkdev_get_no_open Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: David.Boyd49(a)twc.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After 5.19 kernel upgrade, system does not shutdown to reboot Console is flooded with two messages: blkdev_get_no_open xxx callbacks suppressed and block device autoloading is deprecated and will be removed This message is repeated a dozen or more times. This sequence repeats forever (actually, for at least twenty minutes ... I hit reset). Problem was not detected through the 5.18 series of kernels -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1202589] New: during reboot/shutdown when stopping MD devices: infinite loop due to busy MD device
by bugzilla_noreply＠suse.com 08 Sep '22

08 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202589 Bug ID: 1202589 Summary: during reboot/shutdown when stopping MD devices: infinite loop due to busy MD device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: walter.haidinger(a)gmx.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Preliminary note: I'm still trying to figure out what package/change is causing this or when exactly this started. I'm updating on a daily basis. Unfortunately so far I can only describe the symptom. Problem: Shutdown scripts run in an infinite loop (ran at least for ~ 15 minutes) upon reboot or shutdown. Console shows: Stopping MD /dev/md1 (9:1). Could not stop MD /dev/md1: Device or resource busy Not all MD devices stopped, 1 left. Detaching DM devices. Not all DM devices detached, 1 left. Stopping MD devices. Stopping MD /dev/md2 (9:2). md: md2 stopped. Stopping MD /dev/md1 (9:1). Could not stop MD /dev/md1: Device or resource busy Not all MD devices stopped, 1 left. Detaching DM devices. ... The cycle repeats. Now, /dev/md1 holds /dev/ssd/root and thus it might a busy because of some other dependency (e.g. fs which couldn't be remounted and was re-mounted ro or else). Point is, reboot/shutdown did work previously until about a week or so where busy MD devices were logged but then the sequence continued. This is how it llooked like: Stopping MD /dev/md1 (9:1). Could not stop MD /dev/md1: Device or resource busy Not all MD devices stopped, 1 left. Detaching DM deSuccessfully changed into root pivot. Returning to initrd... dracut: Taking over mdmon processes. dracut Warning: Killing all remaining processes dracut Warning: Killing all remaining processes dracut Warning: Unmounted /oldroot. dracut Warning: Unmounted /oldroot. dracut: Disassembling device-mapper devices dracut: Waiting for mdraid devices to be clean. dracut: Disassembling mdraid devices. md1: detected capacity change from 440139776 to 0 md: md1 stopped. mdadm: stopped /dev/md1 Rebooting. Any hints for howto further debug this are appreciated. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1203261] New: [Build 272.2] openQA test fails in yast2_control_center - incorrect expectation of ports 15.5 update repo
by bugzilla_noreply＠suse.com 08 Sep '22

08 Sep '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1203261 Bug ID: 1203261 Summary: [Build 272.2] openQA test fails in yast2_control_center - incorrect expectation of ports 15.5 update repo Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: aarch64 URL: https://openqa.opensuse.org/tests/2626739/modules/yast 2_control_center/steps/45 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation ports 15.5 update repo is not expected to exist at all as we've dropped in 15.3 while we've started to build leap for all arches in single repo (exception for armv7) test/yast fails on repo being missing openQA test in scenario opensuse-15.5-DVD-aarch64-yast2_gui@aarch64 fails in [yast2_control_center](https://openqa.opensuse.org/tests/2626739/modules/yas… ## Test suite description Maintainer: qsf-y Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests. Temporarily added YAST2_GUI_TERMINATE_PREVIOUS_INSTANCES to see if helps. This variable triggers code which terminates all yast2 processes before starting new one. (see poo#26104). ## Reproducible Fails since (at least) Build [257.1](https://openqa.opensuse.org/tests/2525349) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 0