July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220520] Configure remote printer: does not disable local cups entirely
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1220520 https://bugzilla.suse.com/show_bug.cgi?id=1220520#c1 Johannes Meixner <jsmeix(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Johannes Meixner <jsmeix(a)suse.com> --- In general regarding the YaST printer module: In practice the YaST printer module is no longer acually further developed since it was "converted from YCP to Ruby by YCP Killer" that happened in July 2013, see the yast2-printer.changes entry ---------------------------------------------------------- Wed Jul 31 08:37:43 UTC 2013 - yast-devel(a)opensuse.org - converted from YCP to Ruby by YCP Killer (https://github.com/yast/ycp-killer) - version 3.0.0 ---------------------------------------------------------- at https://build.opensuse.org/package/view_file/YaST:Head/yast2-printer/yast2-… My last change is dated Mon Jan 19 14:51:39 UTC 2015 and my last actual development enhancements are dated before it was "converted from YCP to Ruby by YCP Killer". Since that time the YaST printer module is kept working as is as far as possible with reasonable effort by YaST team members who know about how to deal with their generated Ruby code. Since my YCP code was converted into generated Ruby code it is no longer my code and it is no longer code that I could further develop with reasonable effort. Because the YaST printer module is based on the traditional way how printing had worked with CUPS <= 1.5.4 (in particular for printing in the network) within a traditional system environment at that time (in particular before systemd - i.e. with old SysVinit), the YaST printer module has various shortcomings and bugs with nowadays CUPS within a nowadays system environment. According to https://bugzilla.suse.com/page.cgi?id=status_resolution_matrix.html I can only close it as "wontfix" because this issue is a bug but I cannot fix it in practice in foreseeable future. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1222446] New: cups-filters should require /usr/bin/pdftops
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1222446 Bug ID: 1222446 Summary: cups-filters should require /usr/bin/pdftops Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: brunopitrus(a)hotmail.com QA Contact: jsmeix(a)suse.com Target Milestone: --- Found By: --- Blocker: --- I was getting mysterious “Filter failed“ errors when trying to print. Enabling debug output from CUPS revealed that it was due to `/usr/lib/cups/filter/pdftops` trying to execute `pdftops` which is in the `poppler-tools` package which i did not have installed. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227408] Ardour: unable to export in fast mode
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227408 https://bugzilla.suse.com/show_bug.cgi?id=1227408#c2 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alarrosa(a)suse.com --- Comment #2 from Takashi Iwai <tiwai(a)suse.com> --- Let's add the package maintainer to Cc. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227408] New: Ardour: unable to export in fast mode
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227408 Bug ID: 1227408 Summary: Ardour: unable to export in fast mode Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: ferdinando.vivacqua(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Using Ardour, I'm not able to export any session anymore in any format, because the output is very distorted, even with all plugin disabled. It works properly in the real-time mode. Probably related to recent update of pipewire stack -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1226676] Installation: kdump reports an error if systemd-boot has been selected for bootloader
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226676 https://bugzilla.suse.com/show_bug.cgi?id=1226676#c8 --- Comment #8 from Alberto Planas Dominguez <aplanas(a)suse.com> --- (In reply to Jiri Bohac from comment #7) > By default kdump relies on the /boot/vmlinuz symlink (or other image name > variants on non-x86 archs). This points to the last installeed kernel. > When a specific kernel version is requested by setting KDUMP_KERNELVER=xxx > then it relies on the /boot/vmlinuz-xxx symlink. If a BLS-compatible bootloader is used, the kernel now lives in the ESP, a different FAT32 partition that we mount in /boot/efi > When I installe with sdboot, sdbootutil-rpm-scriptlets is installed instead > of suse-module-tools-scriptlets and no such symlinks are created. Yes, the sdbootutil-rpm-scriptlets package is in the process of being removed. All the functionality is merged back unto the suse-module-tools-scriptlets. The chages were submitted to Factory recently, but they are still under review > One way of fixing this would be to create the symlinks in > sdbootutil-rpm-scriptlets. > Another way would be for kdump to look for the kernels elsewhere. I prefer this option. Now suse-module-tools-scriptlets knows about BLS and sdbootutil, that is used to install a new kernel, update initrd and create boot entries. For BLS the responsibility of synchronizing all the boot related stuff is moving into sdbootutil, that under the hood uses the data provided by bootctl, that is the real canonical source of information Ideally mkdumprd should also known about BLS and ask bootctl about the default boot entry, the active one, or the one that correspond to an specific kernel. It will return the information of there it is the kernel, initrd, the cmdline uses and all the information allocated for this entry. > To me the post scriplet seems to be an ideal place to deal with this, > without kdump having to embed knowledge of the location of kernel images > which could be fragile. That is the shift of this model. There is no need to use links to represent the current default kernel. There are boot entries that capture this information and a tool to retrieve it (bootctl). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223617] systemd-tmpfiles-setup finds configuration in /etc/tmpfiles.d as duplicate instead of overridding base config
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1223617 https://bugzilla.suse.com/show_bug.cgi?id=1223617#c6 Radoslav Kolev <radoslav.kolev(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #6 from Radoslav Kolev <radoslav.kolev(a)suse.com> --- Closing as invalid, as it's the expected behaviour. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225784] clang: Please subpackage compiler-rt libraries
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225784 https://bugzilla.suse.com/show_bug.cgi?id=1225784#c4 --- Comment #4 from Daan De Meyer <daan.j.demeyer(a)gmail.com> --- > Thanks for the hint! The static libraries should never be needed at runtime, so what might the reason be to put them in that package? Maybe because they're all coming from compiler-rt? Same goes for the builtin headers. But the remaining files are roughly what I'd imagine. Yeah they all "belong" to compiler-rt in a sense. If you'd like to not have them in the compiler-rt package I would prefer having a compiler-rt-static package or so instead of keeping them in the clang package. I'm not sure what the opensuse packaging guidelines have to say about this though. > What about the directory? The shared runtime libraries don't live in %{_libdir}, so without RPATH the loader won't find them. I would again follow the other distributions here, they don't put these in %{_libdir} so I wouldn't do so in opensuse either. I currently build systemd with "-Wl,-rpath=$(clang --print-file-name="")lib/linux" when building with sanitizers to make sure the loader can find the libraries at runtime, so it's not an issue (for me) that these are not in %{_libdir}. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223617] systemd-tmpfiles-setup finds configuration in /etc/tmpfiles.d as duplicate instead of overridding base config
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1223617 https://bugzilla.suse.com/show_bug.cgi?id=1223617#c5 --- Comment #5 from Radoslav Kolev <radoslav.kolev(a)suse.com> --- I don't know the exact reasons, but it's the upstream behaviour. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1156112] Docker does not work after boot.
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1156112 https://bugzilla.suse.com/show_bug.cgi?id=1156112#c11 Jonathan Kang <songchuan.kang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(miso(a)hlavki.eu) --- Comment #11 from Jonathan Kang <songchuan.kang(a)suse.com> --- Sorry that I picked up this issue late. Is this still re-prorducable in latest tumbleweed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227317] Can't turn off tap to click on trackpad
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227317 https://bugzilla.suse.com/show_bug.cgi?id=1227317#c7 --- Comment #7 from Rick Spencer <rick.spencer(a)suse.com> --- Actually, I found in gnome-tweaks a setting called "Don't use mouse click emulation" which was the functoinality I was looking for originally. -- You are receiving this mail because: You are on the CC list for the bug.

1 0