March 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1113695] New: Kernel modules aren't signed
by bugzilla_noreply＠novell.com 14 Jul '22

14 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1113695 Bug ID: 1113695 Summary: Kernel modules aren't signed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- CONFIG_MODULE_SIG is not set in the openSUSE_15.0 branch. CONFIG_EFI_SECURE_BOOT_LOCK_DOWN (x86_64) isn't set, either. This came about in ug 1049122. Has been fixed in TW (2539ea5663ec1db9b69ecd44039361dac704d209) -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1048177] New: hplip device manager (hp-toolbox) stalls trying to start/stop printer
by bugzilla_noreply＠novell.com 14 Jul '22

14 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1048177 Bug ID: 1048177 Summary: hplip device manager (hp-toolbox) stalls trying to start/stop printer Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: martin.wilck(a)suse.com QA Contact: jsmeix(a)suse.com Found By: --- Blocker: --- hplip-3.17.4-1.1.x86_64 Trying to stop/start printer using hp-toolbox tab "Printer Control", the Qt GUI starts hanging. "cupsd" is seen in top with 75% CPU. strace shows that hp-toolbox is constantly trying to send commands via the cups socket and gets "HTTP/1.1 401 Unauthorized" errors. > 21127 14:56:41.581250 sendto(20, "POST /admin/ HTTP/1.1\r\nAuthorization: Basic cm9vdDo=\r\nContent-Length: 154\r\nContent-Type: application/ipp\r\nHost: localhost:0\r\nUser-Agent: CUPS/2.2.3 (Linux 4.11.8-1-default; x86_64) IPP/2.0\r\nExpect: 100-continue\r\n\r\n", 214, 0, NULL, 0) = 214 > 21127 14:56:41.581272 sendto(20, "\2\0\0\20\0\0\0\1\1G\0\22attributes-charset\0\5utf-8H\0\33attributes-natural-language\0\5en-usE\0\vprinter-uri\0\"ipp://localhost/printers/ENVY_5530B\0\24requesting-user-name\0\4root\3", 154, 0, NULL, 0) = 154 > 21127 14:56:41.581419 recvfrom(20, "HTTP/1.1 401 Unauthorized\r\nConnection: close\r\nContent-Language: en_US\r\nContent-Length: 521\r\nContent-Type: text/html; charset=utf-8\r\nDate: Tue, 11 Jul 2017 12:56:41 GMT\r\nWWW-Authenticate: Basic realm=\"CUPS\", trc=\"y\"\r\nAccept-Encoding: gzip, deflate, identity"..., 2048, 0, NULL, NULL) = 879 > ... > 21127 14:56:41.581972 sendto(20, "POST /admin/ HTTP/1.1\r\nAuthorization: Basic cm9vdDo=\r\nContent-Length: 154\r\nContent-Type: application/ipp\r\nHost: localhost:0\r\nUser-Agent: CUPS/2.2.3 (Linux 4.11.8-1-default; x86_64) IPP/2.0\r\nExpect: 100-continue\r\n\r\n", 214, 0, NULL, 0) = 214 > 21127 14:56:41.581992 sendto(20, "\2\0\0\20\0\0\0\1\1G\0\22attributes-charset\0\5utf-8H\0\33attributes-natural-language\0\5en-usE\0\vprinter-uri\0\"ipp://localhost/printers/ENVY_5530B\0\24requesting-user-name\0\4root\3", 154, 0, NULL, 0) = 154 > 21127 14:56:41.582132 recvfrom(20, "HTTP/1.1 401 Unauthorized\r\nConnection: close\r\nContent-Language: en_US\r\nContent-Length: 521\r\nContent-Type: text/html; charset=utf-8\r\nDate: Tue, 11 Jul 2017 12:56:41 GMT\r\nWWW-Authenticate: Basic realm=\"CUPS\", trc=\"y\"\r\nAccept-Encoding: gzip, deflate, identity"..., 2048, 0, NULL, NULL) = 879 This is a default cups setup, no special permissions configured. cupsd.conf: # All printer operations require a printer operator to authenticate... <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs> AuthType Default Require user @SYSTEM Order deny,allow </Limit> So it's not surprising that the permission isn't granted, but it's wrong to keep trying. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1036463] New: Please take over /usr/lib/modules-load.d/sg.conf
by bugzilla_noreply＠novell.com 14 Jul '22

14 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1036463 Bug ID: 1036463 Summary: Please take over /usr/lib/modules-load.d/sg.conf Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi kernel maintainers, Currently systemd package ships the following file: $ cat /usr/lib/modules-load.d/sg.conf # load sg module at boot time sg I don't know if it's still needed but if so it doesn't seem appropriate to ship it through systemd since it seems to be a workaround for a missing driver dependency or something similar. Would you take this file over ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

2 94

[Bug 1127690] New: haveged: Couldn't initialize HAVEGE rng 9
by bugzilla_noreply＠novell.com 12 Jul '22

12 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1127690 Bug ID: 1127690 Summary: haveged: Couldn't initialize HAVEGE rng 9 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: aarch64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- haveged can not be started on the mustang boards when running leap 51.1 adding the "--data 16" option as workaround allows starting the daemon, please see also: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866306 -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1119619] New: certbot does not renew certificates (again)
by bugzilla_noreply＠novell.com 11 Jul '22

11 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1119619 Bug ID: 1119619 Summary: certbot does not renew certificates (again) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: jimc(a)math.ucla.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Formerly I had python-certbot-0.26.1-1.1.noarch and it could renew certs. Now I have python3-certbot-0.28.0-2.1.noarch on OpenSuSE Tumbleweed VERSION="20181208" This is the one with the dependency on python-mock restored/added. It says "No renewals were attempted" on both of my hosts that use certbot. I tracked this down to a (non) migration issue: formerly the state dir was /etc/certbot but now it is /etc/letsencrypt, which of course contains no lineages, so no renewals were attempted. Workaround: mv /etc/letsencrypt /etc/letsencrypt.empty mv /etc/certbot /etc/letsencrypt ln -s letsencrypt certbot The symlink is so explicit filenames in config files, or symlinks in e.g. /etc/openssl/private, will still find the cert and key until I locate and fix them. Tested: my Apache webserver still can authenticate using the (not quite expired) old cert. I ran "certbot renew", its webroot challenges were acceptable (despite some DNAT stuff), and the report was: Congratulations, all renewals succeeded... (list of 1 renewed cert). Testing: the webserver successfully uses the new cert. By the way, old logs are in /var/log/certbot which is still there but is supplanted by /var/log/letsencrypt. It would be nice if the python3-certbot and python2-certbot packages had a migration script for users who are having trouble figuring out why their certs are not being renewed. I'm not sure whether migration scripts in packages should be reported upstream, or to the distro; if the former, let me know and I'll open a ticket upstream. Also I set the component to "security" since the X.509 certificate's purpose is security, but if a different component would be more appropriate please feel free to change it. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1110456] New: rsyslog not logging most messages
by bugzilla_noreply＠novell.com 07 Jul '22

07 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1110456 Bug ID: 1110456 Summary: rsyslog not logging most messages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On SLES, all messages I see in journalctl are also available in /var/log/messages. On Kubic, where we use rsyslog, nearly no message I see in journalctl can be found in /var/log/messages. So something with journalctl and rsyslog is configured wrong. -- You are receiving this mail because: You are on the CC list for the bug.

2 11

[Bug 1068678] New: Package rsyslog requires package system-user-news
by bugzilla_noreply＠novell.com 07 Jul '22

07 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1068678 Bug ID: 1068678 Summary: Package rsyslog requires package system-user-news Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When installing rsyslog in Tumbleweed there are warning messages that the user news is not present (chown: invalid user: 'news:news'). Unless rsyslog is changed to not using news, the package should require the package "system-user-news". -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1027942] New: virt-manager: Missing upstream bug fixes
by bugzilla_noreply＠novell.com 05 Jul '22

05 Jul '22

http://bugzilla.suse.com/show_bug.cgi?id=1027942 Bug ID: 1027942 Summary: virt-manager: Missing upstream bug fixes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: carnold(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There are upstream patches fixing bugs needed for this version of virt-manager. -- You are receiving this mail because: You are on the CC list for the bug.

2 37

[Bug 1036208] New: GNOME:Factory/libostree: remount service not loaded on install
by bugzilla_noreply＠novell.com 04 Jul '22

04 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1036208 Bug ID: 1036208 Summary: GNOME:Factory/libostree: remount service not loaded on install Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: os.gnome.maintainers(a)gmail.com Reporter: sebix+novell.com(a)sebix.at QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- During my todays zypper dup run, I got this output: ( 72/408) Installing: libostree-2017.3-1.1.x86_64 ......................................................................................................[done] Additional rpm output: Failed to disable unit: No such file or directory Failed to stop ostree-remount.service.service: Unit ostree-remount.service.service not loaded. Is this a bug? The file is there: > find /usr/lib/systemd/ -name "*ostree*" /usr/lib/systemd/system/ostree-prepare-root.service /usr/lib/systemd/system/ostree-remount.service -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1084811] New: E-sata hotplugging stopped working since kernel 4.15
by bugzilla_noreply＠novell.com 03 Jul '22

03 Jul '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1084811 Bug ID: 1084811 Summary: E-sata hotplugging stopped working since kernel 4.15 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: attila.schler(a)atskler.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have noticed that on my Dell E6520 notebook the e-sata hotplugging stopped working since kernel 4.15. Currently I can observe this problem with kernel: 4.15.7-1.6-x86_64 4.16.0-rc4-4.g7a5941a-x86-64 The e-sata cable is OK, and an e-sata device can be used with kernel 4.15 if it is turned on and plugged in before powering on my notebook. (The e-sata hotplugging works well with the Leap kernel 4.12.14-lp150.5.3-x86_64.) ___ (I’m not an advanced user, but I’m ready to follow detailed instructions.) -- You are receiving this mail because: You are on the CC list for the bug.

2 2