May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1124363] New: Temperature Plasmoid does not update the temperature of GPU and CPU (AMD 970 Chipset).
by bugzilla_noreply＠novell.com 21 Jul '20

21 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1124363 Bug ID: 1124363 Summary: Temperature Plasmoid does not update the temperature of GPU and CPU (AMD 970 Chipset). Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Minor Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Take a plasmoid for temperature control. Set to report: CPU, GPU, SSD, HDD temps. You will experience that: At the boot time, SDD and HDD temperatures will be reported correctly. Then, when doing: refresh temp data manually, the data for CPU and GPU appears. I tried to fiddle with the refresh time settings, with slower or faster refresh, size of character, size of plasmoid, orientation of plasmoid. It just does not update these two automagicly. But I set this minor because, once you DO set it manually, it just works. With an uptime of hours, days or weeks does not matter as it seems. I join two images of the fact (mentioned with Mathias Homan also in the opensuse (at) opensuse.org thread: Annoying bug / incompatibility with temperature plasmoid in TW. (05.02.2019). -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1116459] New: TW: since latest update recurrent crashes of akonadi_birthday resource.
by bugzilla_noreply＠novell.com 21 Jul '20

21 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1116459 Bug ID: 1116459 Summary: TW: since latest update recurrent crashes of akonadi_birthday resource. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 790076 --> http://bugzilla.opensuse.org/attachment.cgi?id=790076&action=edit akonadi birthdayressource crashes often but randomly during plasma sessions Konqi output I attach the output of konqi after the crash. Repeatable 1 out of 5 or 6 plasma sessions. Will happen during normal operation. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1061208] New: zypper segfaults upon refresh
by bugzilla_noreply＠novell.com 19 Jul '20

19 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1061208 Bug ID: 1061208 Summary: zypper segfaults upon refresh Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: richard(a)nod.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 742668 --> http://bugzilla.suse.com/attachment.cgi?id=742668&action=edit zypper core After adding the mozilla repo zypper crashes every time upon refresh. e.g. zypper> ref Repository 'go' is up to date. Repository 'libdvdcss repository' is up to date. Repository 'Packman Repository' is up to date. Retrieving repository 'mozilla' metadata -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------[/]Segmentation fault (core dumped) Core file is attached. -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 1042986] New: Missing build requires in e2fsprogs
by bugzilla_noreply＠novell.com 15 Jul '20

15 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1042986 Bug ID: 1042986 Summary: Missing build requires in e2fsprogs 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: lchiquitto(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- e2fsprogs.spec calls %{?regenerate_initrd_posttrans} in %post, but this macro is only available at build time if suse-module-tools is listed as a build requirement. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1133632] New: [20190424] dhcpd failed to start - rc_status: command not found
by bugzilla_noreply＠novell.com 14 Jul '20

14 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1133632 Bug ID: 1133632 Summary: [20190424] dhcpd failed to start - rc_status: command not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: anton.smorodskyi(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 803775 --> http://bugzilla.suse.com/attachment.cgi?id=803775&action=edit journalctl.log Since 20190424 wicked test on TW is failing while starting DHCP daemon with error - Apr 26 12:41:22.580892 susetest dhcpd[3090]: Starting ISC DHCPv4 Server [chroot]/usr/lib/dhcp/dhcpd: line 306: rc_status: command not found Full log in attachment First failing o3 job https://openqa.opensuse.org/tests/917604 -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1132954] New: Fonts do not display correctly.
by bugzilla_noreply＠novell.com 11 Jul '20

11 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1132954 Bug ID: 1132954 Summary: Fonts do not display correctly. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Observe the video to see the problem. Pay attention to two lines before the highlighted entry, how the underline disapears as the mouse goes down. It is less dramatic in the other lines that have no underline. Desktop is XFCE. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1078466] New: systemd: duplicated entries in tmpfiles.d
by bugzilla_noreply＠novell.com 10 Jul '20

10 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1078466 Bug ID: 1078466 Summary: systemd: duplicated entries in tmpfiles.d Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: systemd-maintainers(a)suse.de Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Jan 31 04:02:54 susetest systemd-tmpfiles[6871]: [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path "/var/tmp", ignoring. Jan 31 04:02:54 susetest systemd-tmpfiles[6871]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 31 04:02:54 susetest systemd-tmpfiles[6871]: [/usr/lib/tmpfiles.d/var.conf:19] Duplicate line for path "/var/cache", ignoring. Jan 31 04:02:54 susetest systemd-tmpfiles[6871]: [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring. Jan 31 04:02:54 susetest systemd-tmpfiles[6871]: [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path "/var/spool", ignoring. -- You are receiving this mail because: You are on the CC list for the bug.

2 16

[Bug 1083723] New: Kernels from Kernel:* are not signed by the SUSE key -- cannot be secure-booted
by bugzilla_noreply＠novell.com 10 Jul '20

10 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1083723 Bug ID: 1083723 Summary: Kernels from Kernel:* are not signed by the SUSE key -- cannot be secure-booted Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: General Assignee: adrian(a)suse.com Reporter: jslaby(a)suse.com QA Contact: adrian(a)suse.com CC: jlee(a)suse.com, mls(a)suse.com Found By: --- Blocker: --- Would it be possible to add the SUSE key (which is used for signing released openSUSE:* kernels) to sign also kernels in the Kernel:* space on OBS and Devel:Kernel:* space in IBS? This would allow for enabling secure boot even when one uses kernel-of-the-day from the above repos. And there are plenty of those people (from developers like me to users as can be seen on the opensuse lists). -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 1124857] New: Lightdm "No protocol specified" in session
by bugzilla_noreply＠novell.com 10 Jul '20

10 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1124857 Bug ID: 1124857 Summary: Lightdm "No protocol specified" in session Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: p.seiler(a)linuxmail.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 796417 --> http://bugzilla.opensuse.org/attachment.cgi?id=796417&action=edit lightdm_logs When I start a session with lightdm(-gtk-greeter) all my graphical application print the error/warning "no protocol specified". I searched for the issue a long time and then I thought this is caused by an outdated configuration from updating my openSUSE from one version to another several times. So reinstalling didn't work either. Testing it with another user produced the same result. Steps to reproduce: 1 .install lightdm with gtk-greeter # zypper install lightdm lightdm-gtk-greeter # update-alternatives --config default-displaymanager -> set the value to lightdm-gtk-greeter 2. Restart your computer. (Restarting xdm.service didn't work to reproduce the issue when another displaymanager/X Session was already active) 2. When the display manager shows up, switch to a session like icewm 3. login 4. start a terminal and type "firefox" for example. Then you should see "no protocol specified" several times. Personally I use i3 as my window manager. When starting i3 from gdm everything looks fine. When I switch to lightdm after gdm was used, the error also doesn't occur. Starting a fresh X Session with lightdm causes this error. /var/log/Xorg.0.log, .xsession-errors and /var/log/lightdm content attached. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1118508] New: libldb1 version mismatch in Samba dsdb component 1.4.3 vs 1.4.2
by bugzilla_noreply＠novell.com 09 Jul '20

09 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1118508 Bug ID: 1118508 Summary: libldb1 version mismatch in Samba dsdb component 1.4.3 vs 1.4.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Samba Assignee: samba-maintainers(a)SuSE.de Reporter: micromy(a)free.fr QA Contact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- Hello, This morning I've upgraded my Tumbleweed from 20181129 to 20181203. Along the component updated is libldb1: 2018-12-05 08:18:11 <1> (3787) [zypper++] Summary.cc(readPool):135 <install> U_Ts_(58581)libldb1-1.4.3-1.1.x86_64(repo-oss) 2018-12-05 08:18:11 <1> (3787) [zypper++] Summary.cc(readPool):135 <install> U_Ts_(58582)libldb1-32bit-1.4.3-1.1.x86_64(repo-oss) 2018-12-05 08:18:11 <1> (3787) [zypper++] Summary.cc(readPool):135 <uninstall> I_TsU(106244)libldb1-1.4.2-1.1.x86_64(@System) 2018-12-05 08:18:11 <1> (3787) [zypper++] Summary.cc(readPool):135 <uninstall> I_TsU(106245)libldb1-32bit-1.4.2-1.1.x86_64(@System) After reboot my workstation doesn't allow me to connect because sssd was down with the following message in journalctl : déc. 05 08:30:17 sssd[1032]: ldb: module version mismatch in ../source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.4.3 module_version=1.4.2 déc. 05 08:30:17 sssd[1032]: ldb: failed to initialise module /usr/lib64/ldb/samba/acl.so : Unavailable déc. 05 08:30:17 sssd[1032]: ldb: failed to initialise module /usr/lib64/ldb/samba : Unavailable déc. 05 08:30:17 sssd[1032]: SSSD couldn't load the configuration database [5]: Input/output error. Module /usr/lib64/ldb/samba/acl.so is part of package samba-dsdb-modules version 4.9.1+git.101.212e237d8ef-1.1.x86_64. After removing it using "zypper rm samba-dsdb-modules", sssd could start again and the LDAP connexion work fine. A way to test this case without impacting sssd process is to use ldbsearch binary (from the package ldb-tools): - With samba-dsdb-modules version 4.9.1+git.101.212e237d8ef-1.1.x86_64, it crash with the following messages: ldb: module version mismatch in ../source4/dsdb/samdb/ldb_modules/acl.c : ldb_version=1.4.3 module_version=1.4.2 ldb: failed to initialise module /usr/lib64/ldb/samba/acl.so : Unavailable ldb: failed to initialise module /usr/lib64/ldb/samba : Unavailable - After removing samba-dsdb-modules, the help of ldbsearch is displayed. It seems I don't need samba-dsdb-modules yet, so it's a good workaround for my own case, but the tight dependence between libldb1 and Samba dsdb module seems to be a hard point (I've found some older articles in Google on other GNU Liunx distrib). Thank you for updating samba-dsdb-modules soon. -- You are receiving this mail because: You are on the CC list for the bug.

2 4