January 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1194482] openssh: denies login if disk full
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194482 https://bugzilla.suse.com/show_bug.cgi?id=1194482#c2 --- Comment #2 from Hans Petter Jansson <hpj(a)suse.com> --- Sorry for the wonderful formatting, hard to tell what bz is going to do sometimes :) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194482] openssh: denies login if disk full
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194482 https://bugzilla.suse.com/show_bug.cgi?id=1194482#c1 Hans Petter Jansson <hpj(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Hans Petter Jansson <hpj(a)suse.com> --- I think that message is a red herring. It's just an unfortunately worded debug message regarding pledge(). From clientloop.c: > } else if (options.update_hostkeys) { > debug("pledge: filesystem full"); > if (pledge("stdio rpath wpath cpath unix inet dns proc tty", > NULL) == -1) > fatal_f("pledge(): %s", strerror(errno)); The problem is likely something else, might be something outside openssh too. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194161] %prein: /usr/lib/module-init-tools/kernel-scriptlets/kmp-pre: No such file or directory
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194161 https://bugzilla.suse.com/show_bug.cgi?id=1194161#c5 --- Comment #5 from Ulrich Windl <Ulrich.Windl(a)rz.uni-regensburg.de> --- (In reply to Larry Finger from comment #4) > That file (/usr/lib/module-init-tools/kernel-scriptlets/kmp-pre) is a link > to kmp-script in that same directory. It is part of package > suse-module-tools. > > Does YaST or zypper show this package to be installed? If not, please > install it now. If shown to be installed, does using YaST to force a > reinstall help? I have suse-module-tools-15.3.15-3.17.1.x86_64, and I have this link: ll /usr/lib/module-init-tools/kernel-scriptlets/kmp-pre lrwxrwxrwx 1 root root 10 7. Dez 08:46 /usr/lib/module-init-tools/kernel-scriptlets/kmp-pre -> kmp-script I also saw that suse-module-tools was installed before the error was reported: (1284/5706) Installing: suse-module-tools-15.3.6-1.1.x86_64 (1307/5706) Installing: virtualbox-kmp-preempt-6.1.30_k5.3.18_59.34-lp153.2.15.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1172549] openssh: add socket file too?
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1172549 https://bugzilla.suse.com/show_bug.cgi?id=1172549#c2 Hans Petter Jansson <hpj(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #2 from Hans Petter Jansson <hpj(a)suse.com> --- Thanks for suggesting it. Do you know if we need to patch any code for this? I'm guessing no? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194495] New: Yast NFS client configuration fails
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194495 Bug ID: 1194495 Summary: Yast NFS client configuration fails Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jimoe(a)sohnen-moe.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 855122 --> http://bugzilla.opensuse.org/attachment.cgi?id=855122&action=edit Yast log of failure to save NFS client data When I start the edit of a NFS client entry, this appears: ----[ message ]---- This entry uses old ways of specifying the NFS protocol version that do not longer work as they used to do it (like the usage of 'nfs4' as file system type or the usage of 'minorversion' in the mount options). Editing the entry will change how the version is specified, with no possibility to use old outdated method again. Proceed and edit? ----[ end ]---- Note: Those "old ways" were created when the entry was saved today. They replace entries like "Defaults". I select Continue. I edit/create an entry. I select OK to save edit I select OK to end edit session. Result: ----[ message ]---- Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Caller: /usr/share/YaST2/lib/yast2/popup.rb:79:in `show' Details: wrong number of arguments (given 2, expected 1) ----[ end ]---- -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194494] New: Package conflict resolution dialog in Yast is frustrating and cumbersome for large number of conflicts
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194494 Bug ID: 1194494 Summary: Package conflict resolution dialog in Yast is frustrating and cumbersome for large number of conflicts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: bob(a)muhlenberg.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- If you are trying to upgrade and encounter a large number of package conflicts ( say thousands of them ) the behavior of the GUI is extremely cumbersome or perhaps buggy. In the Yast2 conflict resolver dialog, the list which presents a radio button choice for each conflict, there are no defaults nor a way to resolve largely cosmetic conflicts like vendor change. I seem to remember there at least being defaults, so perhaps this is a bug when huge numbers of conflicts are found. As an example, TeXlive, which has 8,800 separate packages, generates 8,800 separate conflicts. There needs to be a "yes, for the love of God, I get it, change of vendor, blah, blah, blah" option as there is no way to resolve this at install time. Even if you do decide to power through it an hit space bar to select the first option ( usually the correct one ) and press TAB to continue to the next conflict, the list of conflicts has a horizontal scroll bar, and the entire list is shifted to the left - meaning you cannot see the radio buttons and option text. Since TAB seems to intentionally navigate to the next conflict, it should probabaly not be scrolling the pane hard left and leave the H-scroll position unchanged. ( IMO its better to leave the H-scroll position alone than mess with it. ) A means to auto advance to the next decision might make clicking viable. However manually scrolling is necessary. For a 1000 item list, this is challenging. After making changes, Try Again spins for a while then seems to return you to the same list, without having refreshed it - same items are selected, horizontal scroll position is the same. I'm not sure it is actually working or doing anything other than returning you to the same dialog. It may not actually be functioning properly processing a huge list. Some of these are still issues when only a couple conflicts are present, but it is easier to navigate through it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194419] X11:common:Factory/fltk: Passing '-pie' in LDFLAGS breaks any shared lib build using fltk-config
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194419 https://bugzilla.suse.com/show_bug.cgi?id=1194419#c7 Dirk Mueller <dmueller(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Dirk Mueller <dmueller(a)suse.com> --- Thanks Matthias, indeed it seems to be pie without any additonal -pie flag. submitted an update that removed this override. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194109] New: [Build 20211227] openQA test fails in qgis
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194109 Bug ID: 1194109 Summary: [Build 20211227] openQA test fails in qgis Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: PowerPC-64 URL: https://openqa.opensuse.org/tests/2108134/modules/qgis /steps/9 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-ppc64le-extra_tests_gnome@ppc64le fails in [qgis](https://openqa.opensuse.org/tests/2108134/modules/qgis/steps/9) On ppc64le QA, qgis is not installable, as the dep chain cannot be re-built > osc r openSUSE:Factory:PowerPC -a ppc64le -r standard qgis -v standard ppc64le unresolvable: nothing provides PDAL-devel nothing provides pkgconfig(pdal) >= 2.2.0 > osc r openSUSE:Factory:PowerPC -a ppc64le -r standard -v PDAL standard ppc64le failed ## Test suite description Maintainer: QE Core, asmorodskyi. Extra tests which were designed to run on gnome ## Reproducible Fails since (at least) Build [20210302](https://openqa.opensuse.org/tests/1652729) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=ppc64le&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1194126] VirtualBox share clipboard support for Wayland
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194126 https://bugzilla.suse.com/show_bug.cgi?id=1194126#c9 Larry Finger <Larry.Finger(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #9 from Larry Finger <Larry.Finger(a)gmail.com> --- (In reply to Andrei Borzenkov from comment #8) > (In reply to Larry Finger from comment #7) > > I reinstalled a TW KDE system in my TW VM. Now I can run Wayland and test my > > system. I discovered the following: > > > > When I login after boot to Plasma(Wayland), the shared volumes are mounted > > by vboxsf, but screen resize can only be changed in Settings, not be pulling > > on the corners. Is this the expected behavior? The shared clipboard does not > > work even after enabling and starting the vboxclient-clipboard service. > > > > I do not know what you are testing. The virtualbox-guest-tools-6.1.30-622.2 > still installs vboxclient-clipboard.service as system unit and I already > told you it was not going to work. It must be user service stared as part of > user session (or it can be started by any other means offered by desktop > environment; I never claimed this is the only possible solution, I quite > clear said "proof of concept"). I was testing a local version built with osc. I chose that to save a little build time on OBS. The service file is installed into %{buildroot}%{_userunitdir}/vboxclient-clipboard.service and the user versions of the pre- and post-macros are used. The file list for the guest tools package shows the service file in the correct directory. > > > > > If I logout of the Wayland session and login using X11, the screen resizes > > the way I expect, and everything works. > > When you log into X11 VBoxClient is started via xinit script. It is > unrelated to the service vboxclient-clipboard.service. I know that. I was just trying to understand how screen resizing worked under Wayland as I will be the one getting the complaints when screen resizing doesn't work the way it does under X11. > > > Is "After=graphical-session.target" the correct condition? Something is > > killing the service. Perhaps it is starting too early. > > > > This is what worked for me. I wanted to be sure desktop session startup is > complete. > > > Why isn't "/usr/bin/VBoxClient --clipboard" working for me? > > > > You did not say anything about testing it. You said your service did not > work, that is not the same. This command most certainly worked for me when > started explicitly in Wayland GNOME session. Just as my example systemd > *user* service. I enabled the service with a 'systemctl --user enable vboxclient-clipboard'. I then rebooted and logged into Wayland. At that point, 'systemctl --user status vboxclient-clipboard' showed the following:' �� vboxclient-clipboard.service - VirtualBox shared clipboard for Wayland Loaded: loaded (/usr/lib/systemd/user/vboxclient-clipboard.service; enabled; vendor preset: disabled) Active: inactive (dead) I then issued a 'systemctl --user restart vboxclient-clipboard'. At that point, 'systemctl --user status vboxclient-clipboard' showed the following: �� vboxclient-clipboard.service - VirtualBox shared clipboard for Wayland Loaded: loaded (/usr/lib/systemd/user/vboxclient-clipboard.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2022-01-10 13:41:21 CST; 42s ago Process: 1828 ExecStart=/usr/bin/VBoxClient --clipboard (code=exited, status=0/SUCCESS) Main PID: 1831 (VBoxClient) Tasks: 4 (limit: 2332) Memory: 3.5M CPU: 10ms CGroup: /user.slice/user-1000.slice/user(a)1000.service/app.slice/vboxclient-clipboard.service ��1831 /usr/bin/VBoxClient --clipboard ��1832 /usr/bin/VBoxClient --clipboard Jan 10 13:41:21 localhost.localdomain systemd[1459]: Starting VirtualBox shared clipboard for Wayland... Jan 10 13:41:21 localhost.localdomain systemd[1459]: Started VirtualBox shared clipboard for Wayland. At this point, /usr/bin/VBoxClient --clipboard should have been run, but I still got no shared clipboard. Finally, I ran that command manually, and still no shared clipboard. I just pushed my current working version to https://build.opensuse.org/repositories/home:lwfinger:branches:Virtualizati… It is still building, but it should be done within the hour. I verified that the publish flag is still set for x86_64. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1193965] New: pcmanfm is highly out-of-date
by bugzilla_noreply＠suse.com 10 Jan '22

10 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193965 Bug ID: 1193965 Summary: pcmanfm is highly out-of-date 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: Other Assignee: screening-team-bugs(a)suse.de Reporter: rdkracz(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The version in the openSUSE Leap repository is from Dec 10, 2016. There were three releases (Apr 21, 2018; Dec 17, 2018; Feb 5, 2021) so far. -- You are receiving this mail because: You are on the CC list for the bug.

1 6