October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1100765] New: gimp create from screenshot snap region is missing in french and error
by bugzilla_noreply＠novell.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1100765 Bug ID: 1100765 Summary: gimp create from screenshot snap region is missing in french and error Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Translations Assignee: ke(a)suse.com Reporter: conde.philippe(a)skynet.be QA Contact: ke(a)suse.com Found By: --- Blocker: --- Created attachment 776591 --> http://bugzilla.opensuse.org/attachment.cgi?id=776591&action=edit gimp in english with 3 options Hello, in gimp select create image ==> from screenshot in Enclish you have 3 options (see attachment gimp_englishok.png) - take a screenshot of a single window - take screenshot of entire screen - select a region to grab in french the third option is missing (see attachment gimp_frenchbad.png) if I select in french one of the two available options I receive an error (see attachment gimp_error.png Erreur d’exécution « Capture d’écran » : GDBus.Error:org.freedesktop.DBus.Error.UnknownObject: No such object path '/Screenshot' -- You are receiving this mail because: You are on the CC list for the bug.

2 25

[Bug 1201730] New: Upgrade to LEAP 15.4 breaks installing official Vagrant package with vagrant-libvirt
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1201730 Bug ID: 1201730 Summary: Upgrade to LEAP 15.4 breaks installing official Vagrant package with vagrant-libvirt Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: markus.zimmermann(a)symflower.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just installed a new machine with LEAP 15.4. This is actually the first time I tried it on our development environment stack. One major part of our devenv is broken with 15.4: Vagrant with libvirt as its backend cannot be installed **This worked flawless with LEAP 15.3. We cannot upgrade because of this problem.** Here is a reproducer that works repeatedly for me on a newly installed 15.4 and on a machine where i upgraded from 15.3 to 15.4. We usually install the official version of Vagrant (so we can reproduce bugs for specific versions) and also install specific plugins: E.g.: # Remove everything related to Vagrant and building with bundler: rm -rf .vagrant/ ~/.vagrant.d/ ~/.bundle # Install Vagrant manually from the official source. sudo zypper --no-gpg-checks --non-interactive install https://releases.hashicorp.com/vagrant/2.2.19/vagrant_2.2.19_x86_64.rpm Create a directory "foobar", cd into it, and create a Vagrantfile ``` # -*- mode: ruby -*- # vi: set ft=ruby : VAGRANTFILE_API_VERSION = '2' Vagrant.configure(VAGRANTFILE_API_VERSION) do |config| config.vagrant.plugins = { "vagrant-libvirt" => { "version" => "0.9.0" } } config.vm.box = 'generic/ubuntu2004' config.vm.box_version = '4.0.4' config.vm.box_check_update = false config.vm.hostname = 'foobar' config.vm.provider :libvirt do |libvirt| libvirt.cpus = 2 libvirt.memory = 2048 end end ``` # Create the VM with debugging output. Remember to press Y+ENTER when asked to install the libvirt plugin. vagrant --debug up What you will see is an error that we cannot compile ruby-libvirt (the libvirt dependency). The output references the log file ruby-libvirt-0.8.0/mkmf.log Which mainly failed with ``` "gcc -o conftest -I/opt/vagrant/embedded/include/ruby-2.7.0/x86_64-linux -I/opt/vagrant/embedded/include/ruby-2.7.0/ruby/backward -I/opt/vagrant/embedded/include/ruby-2.7.0 -I. -I/opt/vagrant/embedded/include -I/opt/vagrant/embedded/include -I/opt/vagrant/embedded/include -I./include -O3 -std=c99 -fPIC conftest.c -L. -L/opt/vagrant/embedded/lib -Wl,-rpath,/opt/vagrant/embedded/lib -L/opt/vagrant/embedded/lib -Wl,-rpath,/opt/vagrant/embedded/lib -L. -L/opt/vagrant/embedded/lib -L/opt/vagrant/embedded/lib64 -Wl,-rpath=/opt/vagrant/embedded/lib:/opt/vagrant/embedded/lib64 -fstack-protector-strong -rdynamic -Wl,-export-dynamic -L/opt/vagrant/embedded/lib -Wl,-rpath,/opt/vagrant/embedded/lib -Wl,-rpath,'/../lib' -Wl,-rpath,'/../lib' -lruby -lvirt -lm -lc" /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libssh.so.4: undefined reference to `EVP_KDF_CTX_new_id@OPENSSL_1_1_1d' /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libssh.so.4: undefined reference to `EVP_KDF_ctrl@OPENSSL_1_1_1d' /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libssh.so.4: undefined reference to `EVP_KDF_CTX_free@OPENSSL_1_1_1d' /usr/lib64/gcc/x86_64-suse-linux/7/../../../../x86_64-suse-linux/bin/ld: /usr/lib64/libssh.so.4: undefined reference to `EVP_KDF_derive@OPENSSL_1_1_1d' ``` As you can see. We cannot install vagrant-libvirt with LEAP 15.4. Mainly because we cannot compile ruby-libvirt. This worked flawless with LEAP 15.3. Now i was desperate so i looked a little closer and tried different scenarios. The only scenario i found that actually worked: When we add the repositories https://download.opensuse.org/repositories/devel:/languages:/ruby/15.4 and https://download.opensuse.org/repositories/Virtualization:/vagrant/15.4 We can install the the current version of "vagrant" which is 2.2.19 from the virtualization-vagrant repository. The package automatically installs "ruby3.1" (from the ruby repository) and some ruby3.1-* packages (from the virtualization-vagrant repository) AND also "vagrant-libvirt" in an completely outdated version. That we need to deinstall, so we can compile it on our own (please do not install this packages automatically, most users might not even want that package). After deinstalling "vagrant-libvirt". We need to install "ruby3.1-rubygem-ruby-libvirt", "ruby3.1-rubygem-fog-core" and "ruby3.1-rubygem-fog-libvirt" (from the virtualization-vagrant repository). The last one greets us with the problem that "ruby:3.1.0:nokogiri" cannot be found in any repository. We need to install it anyway. We can try again: # Remove everything related to Vagrant and building with bundler: rm -rf .vagrant/ ~/.vagrant.d/ ~/.bundle # Create the VM with debugging output. Remember to press Y+ENTER when asked to install the libvirt plugin. vagrant up This time, the compilation and installation works, even though we are breaking a reference. Conclusion: - We can compile+install+use the vagrant-libvirt plugin on our own. However, we are bound to the Vagrant version in the virtualization-vagrant repository. - Since we are bound to a specific Vagrant version, and we cannot simply install vagrant-libvirt, we cannot upgrade to 15.4. This is a major blocker for us. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1193742] New: go1.18 release tracking
by bugzilla_noreply＠suse.com 11 Jan '23

11 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1193742 Bug ID: 1193742 Summary: go1.18 release tracking Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: jkowalczyk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- go1.18 (expected February 2022) is a major release of Go. Minor releases of go1.18.x will be provided through February 2023. This issue tracks go1.18.x releases packaged and submitted initially to openSUSE:Factory and can be referenced in submissions to additional repositories. Go Release Cycle https://github.com/golang/go/wiki/Go-Release-Cycle Go Release history https://golang.org/doc/devel/release.html -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1198124] New: chromium: Opening and closing media controls triggers segmentation fault
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1198124 Bug ID: 1198124 Summary: chromium: Opening and closing media controls triggers segmentation fault Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: victhor.foster(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 857852 --> http://bugzilla.opensuse.org/attachment.cgi?id=857852&action=edit gdb backtrace Chromium 100.0.4896.60-1.1 suffers from a bug that causes the entire browser to crash with either a segfault or a general protection fault, triggered by opening then closing the media controls. Steps to reproduce: 1. Open any site that plays back media (youtube, spotify, etc) 2. Click on the media control button on the toolbar 3. Click on the button again, to close the dialog Actual result: Chromium crashes with a segfault or a general protection fault. Expected result: Media control dialog closes. Build: Tumbleweed 20220403 x86_64 CPU: Intel Core i7-7200U GPU: Intel HD Graphics 620 No command line options or flags were used, other than any set by the distribution's /usr/bin/chromium script. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1182148] New: systemd-analyze verify is unhappy with /usr/lib/systemd/system/mcelog.service systemd unit
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1182148 Bug ID: 1182148 Summary: systemd-analyze verify is unhappy with /usr/lib/systemd/system/mcelog.service systemd unit 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: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: azhou(a)suse.com, dmueller(a)suse.com, fcrozat(a)suse.com, guillaume.gardet(a)arm.com, lubos.kocman(a)suse.com, meissner(a)suse.com, mlin(a)suse.com, nwr10cst-oslnx(a)yahoo.com, qzhao(a)suse.com, stasiek(a)michalski.cc, yfjiang(a)suse.com Found By: --- Blocker: --- When running systemd-analyze verify ~/.config/systemd/user/*.service I get a list of errors on unrelated systemd units: /usr/lib/systemd/system/mcelog.service:11: Standard output type syslog is obsolete, automatically updating to journal. Please update your unit file, and consider removing the setting altogether. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1199821] New: gdb build fails with GCC 13
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1199821 Bug ID: 1199821 Summary: gdb build fails with GCC 13 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: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package fails due to an out-of-date patch: gdb-6.6-buildid-locate-rpm.patch that causes: conftest.c:47:27: error: conflicting types for 'rpmtsInitIterator' due to enum/integer mismatch; have 'struct rpmdbMatchIterator_s *(struct rpmts_s * const, rpmTag, const void *, size_t)' {aka 'struct rpmdbMatchIterator_s *(struct rpmts_s * const, enum rpmTag_e, const void *, long unsigned int)'} [-Werror=enum-int-mismatch] 47 | extern rpmdbMatchIterator rpmtsInitIterator(const rpmts ts, rpmTag rpmtag, | ^~~~~~~~~~~~~~~~~ In file included from conftest.c:38: /usr/include/rpm/rpmts.h:344:20: note: previous declaration of 'rpmtsInitIterator' with type 'struct rpmdbMatchIterator_s *(struct rpmts_s * const, rpmDbiTagVal, const void *, size_t)' {aka 'struct rpmdbMatchIterator_s *(struct rpmts_s * const, int, const void *, long unsigned int)'} 344 | rpmdbMatchIterator rpmtsInitIterator(const rpmts ts, rpmDbiTagVal rpmtag, | ^~~~~~~~~~~~~~~~~ -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1138135] New: gui version of yast's automatic update configuration fails to change anything
by bugzilla_noreply＠novell.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1138135 Bug ID: 1138135 Summary: gui version of yast's automatic update configuration fails to change anything Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dpbasti(a)wp.pl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I enter the automatic update configuration from gui and enable it. I click on OK - it closes as if everything was fine. I enter the automatic update configuration again and I see it is disabled - so all my changes were disregarded So I switch to console yast. I enable auto update in the config - click ok and now i get prompted to trust pgp keys for certain repos. After having dont that and and reruning the console yast auto update config again I see that now the changes persisted. I now tried to lunch gui version and it also shows auto update as enabled. I tired to disable this feature in gui to check if gui yast can do it. It failed t apply changes again. COnclusion: FOr some reason gui yast auto update config fails to save that the feature is enabled or disabled. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1104571] New: 3g 4g modem connects but no traffic possible
by bugzilla_noreply＠novell.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1104571 Bug ID: 1104571 Summary: 3g 4g modem connects but no traffic possible Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi I have a dual boot Opensuse Leap15/Ubuntu 18.04 system on HP G2 laptop with 4g modem. In ubuntu all works fine In opensuse I added the connection in KDE - all default options -my carrier was listed. The modem get's connected - receives default route, IP assignment, DNS but for some reason no data is being sent/received - not even a simple ping 8.8.8.8 works here are the params ip addr show 5: wwan0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 7a:c6:53:8c:bf:03 brd ff:ff:ff:ff:ff:ff inet 100.101.44.242/30 brd 100.101.44.243 scope global noprefixroute wwan0 valid_lft forever preferred_lft forever ip route show default via 100.101.44.241 dev wwan0 proto static metric 20700 100.101.44.240/30 dev wwan0 proto kernel scope link src 100.101.44.242 metric 700 and also the logs of netowork manager sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2045] device (cdc-wdm0): Activation: starting connection 'Play Online' (f77e62a8-66e0-4f34-b70e-f54a907a0630) sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2046] audit: op="connection-activate" uuid="f77e62a8-66e0-4f34-b70e-f54a907a0630" name="Play Online" pid=3812 uid=1000 result="success" sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2047] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2048] manager: NetworkManager state is now CONNECTING sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect started... sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (4/8): Wait to get fully enabled sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (5/8): Register sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (6/8): Bearer sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (7/8): Connect sie 11 07:37:55 laprus ModemManager[1580]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2087] modem["cdc-wdm0"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested) sie 11 07:37:55 laprus kdeinit5[3768]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus plasmashell[3812]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus kdeinit5[3768]: plasma-nm: Unhandled active connection state change: 1 sie 11 07:37:55 laprus plasmashell[3812]: plasma-nm: Item "Play Online" : active connection state changed to 1 sie 11 07:37:55 laprus plasmashell[3812]: plasma-nm: NetworkManager state changed to 4 sie 11 07:37:55 laprus plasmashell[3812]: plasma-nm: Item "Play Online" : active connection changed to 1 sie 11 07:37:55 laprus ModemManager[1580]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (8/8): All done sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3919] modem["cdc-wdm0"]: modem state changed, 'connecting' --> 'connected' (reason: user-requested) sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3936] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3939] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3942] modem-broadband[cdc-wdm0]: IPv4 static configuration: sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: address 100.101.44.242/30 sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: gateway 100.101.44.241 sie 11 07:37:55 laprus avahi-daemon[1565]: Joining mDNS multicast group on interface wwan0.IPv4 with address 100.101.44.242. sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: DNS 185.89.185.2 sie 11 07:37:55 laprus avahi-daemon[1565]: New relevant interface wwan0.IPv4 for mDNS. sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: DNS 89.108.202.21 sie 11 07:37:55 laprus avahi-daemon[1565]: Registering new address record for 100.101.44.242 on wwan0.IPv4. sie 11 07:37:55 laprus kdeinit5[3768]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus avahi-daemon[1565]: Joining mDNS multicast group on interface wwan0.IPv6 with address fe80::16b5:7d4d:10ab:f6ae. sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3956] device (cdc-wdm0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus avahi-daemon[1565]: New relevant interface wwan0.IPv6 for mDNS. sie 11 07:37:55 laprus avahi-daemon[1565]: Registering new address record for fe80::16b5:7d4d:10ab:f6ae on wwan0.*. sie 11 07:37:55 laprus kdeinit5[3768]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3970] device (cdc-wdm0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3971] device (cdc-wdm0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3972] manager: NetworkManager state is now CONNECTED_LOCAL sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.4262] manager: NetworkManager state is now CONNECTED_SITE sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.4263] policy: set 'Play Online' (wwan0) as default for IPv4 routing and DNS sie 11 07:37:55 laprus nscd[1604]: 1604 monitored file `/etc/resolv.conf` was written to sie 11 07:37:55 laprus plasmashell[3812]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus plasmashell[3812]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus NetworkManager[1843]: nisdomainname: you must be root to change the domain name sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.5272] device (cdc-wdm0): Activation: successful, device activated. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1114273] New: Broadband connection established but all packages dropped
by bugzilla_noreply＠novell.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1114273 Bug ID: 1114273 Summary: Broadband connection established but all packages dropped Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tested https://bugzilla.opensuse.org/show_bug.cgi?id=1104571 on 2018.10.31 Tumbleweeed. The same result as on Leap15. All RX and all TX packages are dropped Connection is established, signal strength is good, IP is obtained, Routing is set to default gw received from 4g modem, DNS servers are also received. Cannot even ping gateway. The same setup works as soon as I boot Ubuntu with no different settings in NetworkManager. wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500 inet 10.111.71.20 netmask 255.255.255.248 broadcast 10.111.71.23 inet6 fe80::73fb:926a:b538:f135 prefixlen 64 scopeid 0x20<link> ether 7a:c6:53:8c:bf:03 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 1280 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 42 dropped 0 overruns 0 carrier 0 collisions 0 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1200457] New: iscsi.service cannot start at microos
by bugzilla_noreply＠suse.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1200457 Bug ID: 1200457 Summary: iscsi.service cannot start at microos Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: matwey.kornilov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I am running microOS 20220611 with open-iscsi-2.1.7-90.1.x86_64. When I try to start iscsi.service the following error appears: Jun 12 19:16:09 localhost.localdomain systemd[1]: Starting Login and scanning of iSCSI devices... Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: Maybe you are not root? Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: Could not lock discovery DB: /etc/iscsi/lock.write: No such file or directory Jun 12 19:16:09 localhost.localdomain iscsiadm[1009]: iscsiadm: No records found Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: Maybe you are not root? Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: Could not lock discovery DB: /etc/iscsi/lock.write: No such file or directory Jun 12 19:16:09 localhost.localdomain iscsiadm[1017]: iscsiadm: No records found Jun 12 19:16:09 localhost.localdomain iscsiadm[1018]: iscsiadm: Could not get list of targets from firmware. (err 21) Jun 12 19:16:09 localhost.localdomain systemd[1]: Finished Login and scanning of iSCSI devices. -- You are receiving this mail because: You are on the CC list for the bug.

1 1