September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1165726] New: (g)vimtutor is broken
by bugzilla_noreply＠novell.com 01 Sep '21

01 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1165726 Bug ID: 1165726 Summary: (g)vimtutor is broken 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: stefan.bruens(a)rwth-aachen.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- (g)vimtutor is packaged in the vim package, but it depends on the tutor files in vim-data. vim-data is not a dependency of vim. As vimtutor is just a wrapper script, it is trivial to move it to the noarch vim-data package. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1190005] Ruby warning on console: URI.unescape is obsolete
by bugzilla_noreply＠suse.com 01 Sep '21

01 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190005 https://bugzilla.suse.com/show_bug.cgi?id=1190005#c2 --- Comment #2 from Ladislav Slez�k <lslezak(a)suse.com> --- Looks like a new Ruby warning, I found these usages in YaST: ./packager/src/lib/y2packager/clients/inst_productsources.rb:357: url_string = URI.unescape(url_string) ./packager/src/modules/SourceDialogs.rb:337: params["url"] = URI.unescape(new_url.to_s) ./packager/src/modules/SourceDialogs.rb:888: path = URI.unescape(parsed.path) Fortunately only three places in whole YaST... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189073] OpenEXR too old to build darktable with openEXR support
by bugzilla_noreply＠suse.com 01 Sep '21

01 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189073 https://bugzilla.suse.com/show_bug.cgi?id=1189073#c12 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #12 from Petr Gajdos <pgajdos(a)suse.com> --- openexr 3 is in Factory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189073] OpenEXR too old to build darktable with openEXR support
by bugzilla_noreply＠suse.com 01 Sep '21

01 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189073 Bug 1189073 depends on bug 1189344, which changed state. Bug 1189344 Summary: openvdb: does not build with openexr3 https://bugzilla.suse.com/show_bug.cgi?id=1189344 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189344] New: openvdb: does not build with openexr3
by bugzilla_noreply＠suse.com 01 Sep '21

01 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1189344 Bug ID: 1189344 Summary: openvdb: does not build with openexr3 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: pgajdos(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openvdb package does not build with OpenEXR 3 currently. If I understand correctly, OpenEXR is mandatory only for vdb_render binary build, see home:pgajdos:openexr3. It seems that others had removed OpenEXR from dependencies of openvdb: https://www.mail-archive.com/arch-commits@lists.archlinux.org/msg126965.html https://src.fedoraproject.org/rpms/openvdb/c/764be4a4fd96741887ce10a6f482ca… Upstream issue: https://github.com/AcademySoftwareFoundation/openvdb/issues/1034 Background: bug 1189073 Could you please help me with resolving this issue? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1190018] VUL-0: cgal: multiple code execution vulnerabilities in Nef polygon-parsing code
by bugzilla_noreply＠suse.com 01 Sep '21

01 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190018 https://bugzilla.suse.com/show_bug.cgi?id=1190018#c2 --- Comment #2 from Gianluca Gabrielli <gianluca.gabrielli(a)suse.com> --- Talos report was submitted in our issue tracker as #5345 [0], and it was fixed by the pull-request #5371 [1]. That pull-request was in: CGAL-5.1.3 and later releases, CGAL-5.2.1, and later releases, and CGAL-5.3. [0] https://github.com/CGAL/cgal/issues/5345 [1] https://github.com/CGAL/cgal/pull/5371 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190007] openSUSE Kernel version is old, can't install on my laptop.
by bugzilla_noreply＠suse.com 01 Sep '21

01 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190007 https://bugzilla.suse.com/show_bug.cgi?id=1190007#c5 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai(a)suse.com --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- We'll happily fix any bugs on Leap (if possible), of course, don't worry about that. The only problem is the lack of information. Definitely more detailed hardware information is needed. So, at first, could you try to install TW image at first (or run with the live image), and run hwinfo, and give the output? Please use attachment on Bugzilla. Also, please give the output of dmesg, too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1171800] New: lirc-core-0.9.4c missing lircd-setup.service
by bugzilla_noreply＠suse.com 01 Sep '21

01 Sep '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1171800 Bug ID: 1171800 Summary: lirc-core-0.9.4c missing lircd-setup.service Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: thomas.betker(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In lirc-core-0.9.4c, lircd-setup.service is missing (it's already missing in the original lirc-0.9.4c tarball), but it is wanted by lircd.service. /usr/lib/systemd/system/lircd-setup.service invokes /usr/sbin/lircd-setup, which executes the [modinit] section of /etc/lirc/lirc_options.conf. In my case, it should have modprobed the serial_ir driver; since that was skipped, the driver was not loaded, and lirc wouldn't work. lircd-setup is included in the lirc-core-0.9.4c package, so I simply installed lircd-setup.service from the lirc-0.9.4d tarball (this file is still the same in lirc-0.10.1). lirc now works fine for me. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1174390] Categories of updates are blank in YaST "Online update" module
by bugzilla_noreply＠suse.com 01 Sep '21

01 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1174390 https://bugzilla.suse.com/show_bug.cgi?id=1174390#c27 Ladislav Slez�k <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #27 from Ladislav Slez�k <lslezak(a)suse.com> --- Fixed in SLE15-SP3/Leap 15.3: libyui-4.1.4 (https://github.com/libyui/libyui/pull/48) Fixed in SLE15-SP4/Leap 15.4/Tumbleweed: libyui-4.2.16 (https://github.com/libyui/libyui/pull/49) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1190007] openSUSE Kernel version is old, can't install on my laptop.
by bugzilla_noreply＠suse.com 01 Sep '21

01 Sep '21

https://bugzilla.suse.com/show_bug.cgi?id=1190007 https://bugzilla.suse.com/show_bug.cgi?id=1190007#c4 --- Comment #4 from Chanryul Yoon <razorbacky(a)gmail.com> --- (In reply to Ancor Gonzalez Sosa from comment #2) > Well, it's actually things are not as straightforward as you may think. > > The kernel shipped with Leap is far from being a vanilla 5.3.18 Linux. On > top of that, it includes hundreds of patches for hardware enablement. So > don't trust the version number blindly. Regarding hardware support, the > kernel in Leap 15.3 is not "old"... or at least it's way more modern and > up-to-date than its version number suggests. > > Reassigning to the kernel guys for them to check whether it would be > possible to include support for your hardware or if there is any trick to > enable such support. Yes, i know, kernel is not old. Firmware and drivers and system service etc. Too many to do. I understand. I just want that. if you feeling bad, i��m really sorry. i��ll find another way. -- You are receiving this mail because: You are on the CC list for the bug.

1 0