October 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1204172] New: kernel crash in drm ( [Build 20221010-1] openQA test fails in updates_packagekit_gpk )
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204172 Bug ID: 1204172 Summary: kernel crash in drm ( [Build 20221010-1] openQA test fails in updates_packagekit_gpk ) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://openqa.opensuse.org/tests/2790642/modules/upda tes_packagekit_gpk/steps/39 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: meissner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-15.3-DVD-Updates-x86_64-gnome@64bit-2G fails in [updates_packagekit_gpk](https://openqa.opensuse.org/tests/2790642/modules/u… ## Test suite description Revert schedule to working settings - dleuenberger, 20211117 ## Reproducible Fails since (at least) Build [20221010-1](https://openqa.opensuse.org/tests/2790642) (current job) ## Expected result Last good: [20221009-1](https://openqa.opensuse.org/tests/2790325) (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 4

[Bug 1203311] python-softlayer / xmlrpc y2038 problem
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1203311 https://bugzilla.suse.com/show_bug.cgi?id=1203311#c3 Matej Cepl <mcepl(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM Flags|needinfo?(bwiedemann(a)suse.c | |om) | --- Comment #3 from Matej Cepl <mcepl(a)suse.com> --- I think this bug should be better be resolved upstream. Of course, when the solution is found we will update our package as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204182] New: Ansible: Cannot find community.general.zyper
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204182 Bug ID: 1204182 Summary: Ansible: Cannot find community.general.zyper 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: pdostal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, when I use Ansible package from our official repositories I cannot use community.general.zypper module: > # zypper -n in ansible jq | cat; ( exit ${PIPESTATUS[0]} ); echo 8tCVo-$?- > Loading repository data... > Reading installed packages... > Resolving package dependencies... > > The following 24 recommended packages were automatically selected: > python3-selinux python310-Babel python310-Pygments python310-argon2-cffi python310-bcrypt python310-boto3 python310-botocore python310-click python310-dnspython python310-gssapi python310-h2 python310-hiredis python310-httplib2 python310-invoke python310-keyczar python310-lxml python310-pbkdf2 python310-python-memcached python310-pyvmomi python310-pywinrm python310-redis python310-rich python310-scrypt sshpass > > The following 71 NEW packages are going to be installed: > ansible jq libhiredis1_0_0 libjq1 libonig5 libsodium23 memcached python3-selinux python310-Babel python310-CommonMark python310-Deprecated python310-Jinja2 python310-MarkupSafe python310-PyNaCl python310-PyYAML python310-Pygments python310-anyio python310-argon2-cffi python310-argon2-cffi-bindings python310-async_timeout python310-bcrypt python310-boto3 python310-botocore python310-click python310-cssselect python310-dnspython python310-fluidity-sm python310-gssapi python310-h11 python310-h2 python310-hiredis python310-hpack python310-httpcore python310-httplib2 python310-httpx python310-hyperframe python310-invoke python310-jmespath python310-keyczar python310-lexicon python310-lxml python310-ntlm-auth python310-packaging python310-paramiko python310-passlib python310-pbkdf2 python310-pexpect python310-ply python310-ptyprocess python310-pyasn1 python310-pycryptodome python310-pyparsing python310-python-dateutil python310-python-memcached python310-pytz python310-pyvmomi python31 0-pywinrm python310-redis python310-requests-toolbelt python310-requests_ntlm python310-rfc3986 python310-rich python310-s3transfer python310-scrypt python310-simplejson python310-sniffio python310-typing_extensions python310-wrapt python310-xmltodict redis sshpass > > 71 new packages to install. > Overall download size: 38.7 MiB. Already cached: 0 B. After the operation, additional 247.6 MiB will be used. > Continue? [y/n/v/...? shows all options] (y): y > Retrieving package ansible-2.9.27-2.1.noarch (71/71), 12.4 MiB ( 95.9 MiB unpacked) > Retrieving: ansible-2.9.27-2.1.noarch.rpm [.done (5.2 MiB/s)] > > Checking for file conflicts: [.........done] > > (71/71) Installing: ansible-2.9.27-2.1.noarch [............done] > 8tCVo-0- > $ ansible-galaxy collection install community.general; echo FBad3-$?- > Process install dependency map > Starting collection install process > Installing 'community.general:5.7.0' to '/home/bernhard/.ansible/collections/ansible_collections/community/general' > FBad3-0- > $ ansible-playbook -i ~/ansible/hosts ~/ansible/main.yaml; echo dSsas-$?- > $ERROR! couldn't resolve module/action 'community.general.zypper'. This often indicates a misspelling, missing collection, or incorrect module path. The same happens also when I run the playbook as root user. But the same playbook works when I install Ansible using pip: > # pip3 install ansible; echo 8VS~k-$?- > Defaulting to user installation because normal site-packages is not writeable > Collecting ansible > Downloading ansible-6.4.0-py3-none-any.whl (41.5 MB) > �� 41.5/41.5 MB 26.4 MB/s eta 0:00:00 > > Collecting ansible-core~=2.13.4 > Downloading ansible_core-2.13.4-py3-none-any.whl (2.1 MB) > �� 2.1/2.1 MB 36.7 MB/s eta 0:00:00 > > Collecting packaging > Downloading packaging-21.3-py3-none-any.whl (40 kB) > �� 40.8/40.8 KB 7.6 MB/s eta 0:00:00 > > Requirement already satisfied: cryptography in /usr/lib64/python3.10/site-packages (from ansible-core~=2.13.4->ansible) (38.0.1) > Collecting resolvelib<0.9.0,>=0.5.3 > Downloading resolvelib-0.8.1-py2.py3-none-any.whl (16 kB) > Collecting PyYAML>=5.1 > Downloading PyYAML-6.0-cp310-cp310-manylinux_2_5_x86_64.manylinux1_x86_64.manylinux_2_12_x86_64.manylinux2010_x86_64.whl (682 kB) > �� 682.2/682.2 KB 27.3 MB/s eta 0:00:00 > > Collecting jinja2>=3.0.0 > Downloading Jinja2-3.1.2-py3-none-any.whl (133 kB) > �� 133.1/133.1 KB 23.7 MB/s eta 0:00:00 > > Collecting MarkupSafe>=2.0 > Downloading MarkupSafe-2.1.1-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (25 kB) > Requirement already satisfied: cffi>=1.12 in /usr/lib64/python3.10/site-packages (from cryptography->ansible-core~=2.13.4->ansible) (1.15.1) > Collecting pyparsing!=3.0.5,>=2.0.2 > Downloading pyparsing-3.0.9-py3-none-any.whl (98 kB) > �� 98.3/98.3 KB 25.4 MB/s eta 0:00:00 > > Requirement already satisfied: pycparser in /usr/lib/python3.10/site-packages (from cffi>=1.12->cryptography->ansible-core~=2.13.4->ansible) (2.21) > Installing collected packages: resolvelib, PyYAML, pyparsing, MarkupSafe, packaging, jinja2, ansible-core, ansible > WARNING: The scripts ansible, ansible-config, ansible-connection, ansible-console, ansible-doc, ansible-galaxy, ansible-inventory, ansible-playbook, ansible-pull and ansible-vault are installed in '/home/bernhard/.local/bin' which is not on PATH. > Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location. > WARNING: The script ansible-community is installed in '/home/bernhard/.local/bin' which is not on PATH. > Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location. > Successfully installed MarkupSafe-2.1.1 PyYAML-6.0 ansible-6.4.0 ansible-core-2.13.4 jinja2-3.1.2 packaging-21.3 pyparsing-3.0.9 resolvelib-0.8.1 > 8VS~k-0- > # ansible-galaxy collection install community.general; echo FBad3-$?- > Process install dependency map > Starting collection install process > Installing 'community.general:5.7.0' to '/home/bernhard/.ansible/collections/ansible_collections/community/general' > FBad3-0- > # ansible-playbook -i ~/ansible/hosts ~/ansible/main.yaml; echo dSsas-$?- > > PLAY [openQA Ansible test] > > TASK [Gathering Facts] > [WARNING]: Platform linux on host localhost is using the discovered Python interpreter at /usr/bin/python3.10, but future installation of another Python interpreter could change the meaning of that path. See https://docs.ansible.com/ansible-core/2.13/reference_appendices/interpreter… for more information. > ok: [localhost] > TASK [Install htop] > changed: [localhost] > > PLAY RECAP > localhost : ok=7 changed=6 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 > dSsas-0- Here is the playbook I use: > - name: openQA Ansible test > hosts: all > collections: > - community.general > tasks: > - name: Install htop > become: true > community.general.zypper: > name: htop > state: present This happens in Tumbleweed - I did not try other distribution yet. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1187566] New: Display connected to Thunderbolt 3 Docking Station is not detected on cold boot
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1187566 Bug ID: 1187566 Summary: Display connected to Thunderbolt 3 Docking Station is not detected on cold boot Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: eecdc3.opensuse(a)coders-haven.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using a HP Elitebook 1040 G4 notebook connected to a HP Thunderbolt 3 Docking Station, which in turn is connected to multiple USB devices and an external monitor via DisplayPort. Unfortunately, I am experiencing issues with this configuration as described below. I am using boltd from the hardware repository to authorize my Thunderbolt 3 Docking Station during startup. (Boot ACLs are not supported by my BIOS, as far as I can tell.) While devices connected to the docking station via USB will work afterwards, my external monitor, which is connected via DisplayPort, will not be detected automatically. Only when I manually reconnect the docking station after startup has completed, it will finally be detected (and awoken from standby). This leads me to believe that this issue is boot order related. (Previously, I was using openSUSE Leap 15.2 and a custom udev rule to authorize the docking station via sysfs and I did not experience this issue but the system would occasionally hang while booting instead. I have already tried the udev rule with openSUSE Leap 15.3 but this made the issue worse as the display was then only detected if I reconnected the external monitor itself.) Any help investigating this issue is appreciated as I do not have in-depth knowledge of the kernel or its Thunderbolt subsystem and cannot really make any progress towards a resolution on my own. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1183133] New: gkrellm doesn't remember startup position with two instances
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1183133 Bug ID: 1183133 Summary: gkrellm doesn't remember startup position with two instances Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: erbenton(a)comcast.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE Tumbleweed 20210115 (x86_64) KDE 5.78.0 Plasma 5.20.5 Qt: 5.15.2 gkrellm 2.3.11 If I start 2 instances of gkrellm and put one on each monitor and then shut them down they only remember one position the next time they are started. Starting two instances results in both starting at the exact same position on screen, one on top of the other. "allow multiple instances" is checked in the configuration dialog. In $HOME/.gkrellm2/data/startup_position i only see one set of coordinates which correspond to the last instance to shutdown, but only if the last of the two instances is moved (on screen)first, otherwise it never writes to the file and the stored coordinates are from the first instance to shutdown. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1203366] gpk-update-viewer cannot resume a broken download
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1203366 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |os.gnome.maintainers@gmail. | |com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204103] error: unpacking of archive failed on file /usr/lib/firmware/qcom/LENOVO/21BX;633f2acf: cpio: File from package already exists as a directory in system
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204103 https://bugzilla.suse.com/show_bug.cgi?id=1204103#c18 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #18 from Takashi Iwai <tiwai(a)suse.com> --- https://build.opensuse.org/request/show/1009318 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1202791] roundcubemail can't find Larry skin files
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

1 0

[Bug 1204103] error: unpacking of archive failed on file /usr/lib/firmware/qcom/LENOVO/21BX;633f2acf: cpio: File from package already exists as a directory in system
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

https://bugzilla.suse.com/show_bug.cgi?id=1204103 https://bugzilla.suse.com/show_bug.cgi?id=1204103#c17 --- Comment #17 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Fabian Vogt from comment #15) > The uncompressed kernel-firmware needs the same workaround. Indeed (although it shouldn't be used on normal systems at all). Will fix it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1204103] New: error: unpacking of archive failed on file /usr/lib/firmware/qcom/LENOVO/21BX;633f2acf: cpio: File from package already exists as a directory in system
by bugzilla_noreply＠suse.com 10 Oct '22

10 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1204103 Bug ID: 1204103 Summary: error: unpacking of archive failed on file /usr/lib/firmware/qcom/LENOVO/21BX;633f2acf: cpio: File from package already exists as a directory in system 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- error: unpacking of archive failed on file /usr/lib/firmware/qcom/LENOVO/21BX;633f2acf: cpio: File from package already exists as a directory in system error: kernel-firmware-qcom-20220930-1.1.noarch: install failed error: kernel-firmware-qcom-20220902-1.1.noarch: erase skipped ( 82/133) Installing: kernel-firmware-qcom-20220930-1.1.noarch ...............................................................[error] Installation of kernel-firmware-qcom-20220930-1.1.noarch failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. -- You are receiving this mail because: You are on the CC list for the bug.

1 25