September 2021 - openSUSE Factory - openSUSE Mailing Lists

Sorry, we're having trouble playing this video.,Learn More
by Constant Brouerius van Nidek 06 Sep '21

06 Sep '21

Every time I want to play vidroe on my Firefox I get the following information on my screen. At first I assumed it was a memory problem but after extending my memory to 8Gb the problem still exists. I My system is Tumbleweed fully updated. Firefox offer to learn more ends in an invitation to update Firefox which it already is. Where do I look at the origin of the problem and how can I get my system working.

3 2

aarch64: test -r with bash issue
by Frans de Boer 06 Sep '21

06 Sep '21

It took me some time, but somehow bash is not behaving as expected within a qemu-aarch64 chroot jail. If I do the following: if test -r <some file>; then echo ok; fi Then the reply is 'ok' under normal x86_64 TW. However, when I started a chroot jail using qemu-aarch64 the reply stays empty. Only when I execute if test *!* -r <some file>; then echo ok; fi the response is 'ok'. And <some file> is always the same. I start the jail with the next command: /usr/bin/qemu-aarch64 -strace -cpu cortex-a53 -L /newroot /newroot/usr/sbin/chroot "/newroot" \ /usr/bin/env -i \ HOME=/root \ TERM="$TERM" \ PS1='(lfs chroot) \u:\w\$ ' \ PS4='(${BASH_SOURCE}:${LINENO}: ${FUNCNAME[0]} - [${SHLVL},${BASH_SUBSHELL}, $?] ' \ PATH=/usr/bin:/usr/sbin \ /usr/bin/bash --login +h Also, I copied a static version of qemu-aarch64 /and/ qemu_binfmt into /newroot/usr/bin - I also tried my own compiled version of qemu-aarch64-static, with the same result. Programs run, but bash seems to have this specific issue with the -r test. Other flags I tested -f, -s, -x etc. are working correctly. The -r flags is the only flag which - I presume - really does a reading test, while others test availability and some file flags. Maybe binfmt is to blame?? It is blocking me from compiling programs under aarch64 because the configure script is using these tests. If I change the ´-r´ flag within configure into a ´-s´, everything does work well. Regards, Frans.

5 8

rpmlint time measurement leads to a new release?
by munix9 06 Sep '21

06 Sep '21

Hi, since recently a current rpmlint under Factory/TW on OBS leads to the fact that a final compare finds a difference and thus a new release is created, because the timing of rpmlint differs from the old build. Is this intentional and reasonable? eg. https://build.opensuse.org/package/live_build_log/home:munix9/android-tools… [ 400s] rpmlint.log files differ: [ 400s] --- /tmp/tmp.yUsDRbZz79 2021-09-04 10:10:33.236000000 +0000 [ 400s] +++ /tmp/tmp.CRk2h2aSLQ 2021-09-04 10:10:33.236000000 +0000 [ 400s] @@ -13,7 +13,7 @@ [ 400s] /opt/testing/share/rpmlint/security.toml [ 400s] /opt/testing/share/rpmlint/users-groups.toml [ 400s] /opt/testing/share/rpmlint/world-writable-whitelist.toml [ 400s] - 4 packages and 0 specfiles checked; 0 errors, 0 warnings, 0 badness; has taken 2.1 s [ 400s] + 4 packages and 0 specfiles checked; 0 errors, 0 warnings, 0 badness; has taken 2.2 s

6 8

New Tumbleweed snapshot 20210902 released!
by Dominique Leuenberger 04 Sep '21

04 Sep '21

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports Packages changed: AppStream bluez (5.60 -> 5.61) cryptsetup (2.3.6 -> 2.4.0) hplip (3.21.4 -> 3.21.6) libzypp (17.28.1 -> 17.28.2) rubygem-sassc selinux-policy transactional-update (3.5.1 -> 3.5.2) === Details === ==== AppStream ==== Subpackages: AppStream-lang libAppStreamQt2 libappstream4 - Create and install a Vala API file ==== bluez ==== Version update (5.60 -> 5.61) Subpackages: libbluetooth3 - update to version 5.61: * Fix issue with A2DP while waiting for command response. * Fix issue with A2DP when SetConfiguration fails. * Fix issue with device removal handling. * Fix issue with storing discoverable setting. * Add support for Central Address Resolution characteristic. * Add support for admin policy plugin. ==== cryptsetup ==== Version update (2.3.6 -> 2.4.0) Subpackages: cryptsetup-lang libcryptsetup12 libcryptsetup12-32bit libcryptsetup12-hmac - As YaST passes necessary parameters to cryptsetup anyway, we do not necessarily need to take grub into consideration. So back to Argon2 to see how it goes. - need to use PBKDF2 by default for LUKS2 as grub can't decrypt when using Argon. - crypsetup 2.4.0 (jsc#SLE-20275) * External LUKS token plugins * Experimental SSH token * Default LUKS2 PBKDF is now Argon2id * Increase minimal memory cost for Argon2 benchmark to 64MiB. * Autodetect optimal encryption sector size on LUKS2 format. * Use VeraCrypt option by default and add --disable-veracrypt option. * Support --hash and --cipher to limit opening time for TCRYPT type * Fixed default OpenSSL crypt backend support for OpenSSL3. * integritysetup: add integrity-recalculate-reset flag. * cryptsetup: retains keyslot number in luksChangeKey for LUKS2. * Fix cryptsetup resize using LUKS2 tokens. * Add close --deferred and --cancel-deferred options. * Rewritten command-line option parsing to avoid libpopt arguments memory leaks. * Add --test-args option. - Use LUKS2 as default format on Tumbleweed. It provides some additional features which other tools (e.g. systemd-cryptenroll) rely on. GRUB 2.06 supports unlocking LUKS2 volumes meanwhile. ==== hplip ==== Version update (3.21.4 -> 3.21.6) Subpackages: hplip-hpijs hplip-sane - Update to 3.21.6 New upstream release, added support for new distributions ==== libzypp ==== Version update (17.28.1 -> 17.28.2) - Workaround Bug 1189788: Don't allow ZYPP_SINGLE_RPMTRANS=1 on a not UsrMerged Tumbleweed system. - version 17.28.2 (22) ==== rubygem-sassc ==== Subpackages: ruby2.7-rubygem-sassc ruby3.0-rubygem-sassc - fix rpmlintrc naming which fixes the TW build with rpmlint 2 ==== selinux-policy ==== Subpackages: selinux-policy-targeted - Modified fix_systemd.patch to allow systemd gpt generator access to udev files (bsc#1189280) - fix rebootmgr does not trigger the reboot properly (boo#1189878) * fix managing /etc/rebootmgr.conf * allow rebootmgr_t to cope with systemd and dbus messaging - Properly label cockpit files - Allow wicked to communicate with network manager on DBUS (bsc#1188331) - Added policy module for rebootmgr (jsc#SMO-28) ==== transactional-update ==== Version update (3.5.1 -> 3.5.2) Subpackages: dracut-transactional-update libtukit0 transactional-update-zypp-config tukit - Version 3.5.2 - tukit: Fix overlay syncing errors with SELinux [bsc#1188648] - Don't print message for `shell` with --quiet [gh#openSUSE/transactional-update#69]

1 0

Start using transaction file triggers for ldconfig?
by Dan Čermák 03 Sep '21

03 Sep '21

Hi list, now that boo#1041742 [1] appears to be resolved in Tumbleweed, is there anything stopping us from adding transaction file triggers into glibc to run ldconfig automatically? Then we could finally get rid of all the %post -n libnfoo%{libversion} -p /sbin/ldconfig %postun -n libfoo%{libversion} -p /sbin/ldconfig scripts in _every_ single spec file out there. Cheers, Dan Footnotes: [1] https://bugzilla.suse.com/show_bug.cgi?id=1041742 -- Dan Čermák <dcermak(a)suse.com> Software Engineer Development tools SUSE Software Solutions Germany GmbH Maxfeldstr. 5 90409 Nuremberg Germany (HRB 36809, AG Nürnberg) Managing Director: Felix Imendörffer

8 27

Tumbleweed - Review of the week 2021/35
by Dominique Leuenberger / DimStar 03 Sep '21

03 Sep '21

Dear Tumbleweed users and hackers, This week has shown that Tumbleweed is indeed back at full speed. We have published new snapshots daily. Of course, that also means we could rely on not receiving broken things that managed to slip through stagings without being noticed. So thanks go mostly to the developers/maintainers who submitted pre-tested things. And openQA of course! The snapshots were numbered 0826…0901. The most notable changes during this week included: * The missing pieces of the GNOME 40.4 update (complete now) * rpmlint 2.1 * openssl 1.1.1l * pipewire 0.3.34 * Linux kernel 5.13.13 The staging projects are currently filled with those major changes: * Mesa 21.2.1 * Mozilla Firefox 91.0.2 * systemd 249.4 * Linux kernel 5.14.0 * KDE Plasma 5.22.5 * KDE Applications 21.08.1 * glibc 2.34: bug tracking remaining failures: boo#1189079 * shadow 4.9: boo#1190145 and boo#1190146 Cheers, Dominique

1 0

New Tumbleweed snapshot 20210901 released!
by Dominique Leuenberger 03 Sep '21

03 Sep '21

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… Please do not reply to this email to report issues, rather file a bug on bugzilla.opensuse.org. For more information on filing bugs please see https://en.opensuse.org/openSUSE:Submitting_bug_reports Packages changed: graphviz graphviz-addons === Details === ==== graphviz ==== Subpackages: graphviz-plugins-core libgraphviz6 - Changelog Update for SLES: The Following patches have been backported to SLES and are therefore missing from the Factory changelog: * graphviz-2.40.1-fix-dot-segfault.patch (bsc#1151207) * graphviz-out-of-bounds-write.patch (bsc#1185833) * graphviz-null_dereference.patch (bsc#1185833) ==== graphviz-addons ==== Subpackages: graphviz-gd graphviz-gnome - Changelog Update for SLES: The Following patches have been backported to SLES and are therefore missing from the Factory changelog: * graphviz-2.40.1-fix-dot-segfault.patch (bsc#1151207) * graphviz-out-of-bounds-write.patch (bsc#1185833) * graphviz-null_dereference.patch (bsc#1185833)

1 0

State of the retroarch package
by Martin Jungblut 02 Sep '21

02 Sep '21

Hello folks, first time posting here. I have a change request I'd like to submit to the retroarch package, it's a simple change, but I'd like to understand why the original decision was made in the first place, in case I'm missing something. To that end, I've also submitted this comment to the package's page itself on OBS: https://build.opensuse.org/package/show/Emulators/retroarch#comment-1510367 But I have a feeling the mailing list might be a good place to discuss this as well. I don't think the retroarch-config.patch file is required. Please correct me if I'm wrong. Here's my rationale: I think it would be better for users to be able to download extra cores using RetroArch's built-in online updater, rather than hiding that feature and providing cores as multiple, sometimes outdated packages. Not all cores are available as packages right now, but they may be installed via the Online Updater, but only if the user is smart enough to re-enable it. I think it would be better for us to drop the libretro* packages altogether, and ship a build of RetroArch that focuses on using the Online Updater. We already ship Steam, and people download games through Steam itself, so I don't think the idea of distributing cores via RetroArch's own solution to be a bad one. For my own purposes, I'm maintaining my own build here: https://build.opensuse.org/package/show/home:martinjungblut/retroarch But I'd love for this to be solved, rendering my package obsolete. Any thoughts are greatly appreciated, Thanks in advance

1 0

since yesterday no sound on laptop
by Mathias Homann 02 Sep '21

02 Sep '21

Hi, all of a sudden sound has stopped working on my laptop. I'm on TW 20210830, I already tried going back several snapshots all the way to 20210827, didn't help. Any ideas? What info do you guys need to help figuring this out? as soon as I log into KDE I see this in the kernel output: snd_hda_codec_realtek ehdaudio0D0: didn't find PCM for DAI Digital Codec DAI snd_hda_codec_realtek ehdaudio0D0: ASoC: error at snd_soc_dai_startup on Digital Codec DAI: -22 Digital Playback and Capture: soc_pcm_open() failed (-22) HDA Digital: ASoC: dpcm_be_dai_startup() failed at Digital Playback and Capture (-22) HDA Digital: dpcm_fe_dai_startup() failed (-22) snd_hda_codec_realtek ehdaudio0D0: didn't find PCM for DAI Digital Codec DAI snd_hda_codec_realtek ehdaudio0D0: ASoC: error at snd_soc_dai_startup on Digital Codec DAI: -22 Digital Playback and Capture: soc_pcm_open() failed (-22) HDA Digital: ASoC: dpcm_be_dai_startup() failed at Digital Playback and Capture (-22) HDA Digital: dpcm_fe_dai_startup() failed (-22) mio:~ # hwinfo --sound 19: PCI 1f.3: 0401 Multimedia audio controller [Created at pci.386] Unique ID: nS1_.HGCy71q8xS8 SysFS ID: /devices/pci0000:00/0000:00:1f.3 SysFS BusID: 0000:00:1f.3 Hardware Class: sound Device Name: "Onboard - Sound" Model: "Intel Tiger Lake-LP Smart Sound Technology Audio Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa0c8 "Tiger Lake-LP Smart Sound Technology Audio Controller" SubVendor: pci 0x1462 "Micro-Star International Co., Ltd. [MSI]" SubDevice: pci 0x12e2 Revision: 0x20 Driver: "sof-audio-pci-intel-tgl" Driver Modules: "snd_sof_pci_intel_tgl" Memory Range: 0x6053188000-0x605318bfff (rw,non-prefetchable) Memory Range: 0x6053000000-0x60530fffff (rw,non-prefetchable) IRQ: 173 (2013 events) Module Alias: "pci:v00008086d0000A0C8sv00001462sd000012E2bc04sc01i00" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Driver Info #1: Driver Status: snd_sof_pci_intel_tgl is active Driver Activation Cmd: "modprobe snd_sof_pci_intel_tgl" Config Status: cfg=yes, avail=yes, need=no, active=unknown Any ideas? Cheers MH -- Mathias Homann Mathias.Homann(a)openSUSE.org telegram: https://telegram.me/lemmy98 irc: [lemmy] on freenode and ircnet obs: lemmy04 gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102

5 11

Re: TW: Issue with Intel graphics
by Axel Braun 02 Sep '21

02 Sep '21

Thanks for confirming the issue. I booted back into 20210810 snapshot and issue disappeared I have created https://bugzilla.opensuse.org/show_bug.cgi?id=1190095 for this Cheers Axel Am Mittwoch, 1. September 2021, 18:53:14 CEST schrieb Владимир Давыденко: > confirm > > ср, 1 сент. 2021 г. в 18:20, Axel Braun <docb(a)opensuse.org>: > > Hi, > > > > I did a dup from 20210810 to 20210828, and since then I noticed a very > > slow > > redraw on KDE Plasma: when scolling in a terminal or in a window, the > > screen > > looks 'broken' for a moment, then the rendering is back. > > > > 30: PCI 02.0: 0300 VGA compatible controller (VGA) > > > > [Created at pci.386] > > Unique ID: _Znp.WlxwpsiDkK3 > > SysFS ID: /devices/pci0000:00/0000:00:02.0 > > SysFS BusID: 0000:00:02.0 > > Hardware Class: graphics card > > Model: "Intel CoffeeLake-H GT2 [UHD Graphics 630]" > > Vendor: pci 0x8086 "Intel Corporation" > > Device: pci 0x3e9b "CoffeeLake-H GT2 [UHD Graphics 630]" > > SubVendor: pci 0x17aa "Lenovo" > > SubDevice: pci 0x229f > > Driver: "i915" > > Driver Modules: "i915" > > Memory Range: 0xe9000000-0xe9ffffff (rw,non-prefetchable) > > Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable) > > I/O Ports: 0x4000-0x403f (rw) > > Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) > > IRQ: 143 (1116926 events) > > Module Alias: "pci:v00008086d00003E9Bsv000017AAsd0000229Fbc03sc00i00" > > > > Driver Info #0: > > Driver Status: i915 is active > > Driver Activation Cmd: "modprobe i915" > > > > Config Status: cfg=new, avail=yes, need=no, active=unknown > > > > Switching to nvidia chipset (prime-select) the issue is gone. > > > > Anyone else to confirm this issue? > > > > Cheers > > Axel -- Dr. Axel Braun <docb(a)opensuse.org> Member of the openSUSE Board

1 1