November 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1032849] New: M17N:fonts/adobe-sourcehanserif-fonts, M17N:fonts/adobe-sourcehansans-fonts: incomplete package or wrong naming
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1032849 Bug ID: 1032849 Summary: M17N:fonts/adobe-sourcehanserif-fonts, M17N:fonts/adobe-sourcehansans-fonts: incomplete package or wrong naming Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: jnweiger(a)gmail.com Reporter: guoyunhebrave(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: thomas.schraitle(a)suse.com Found By: --- Blocker: --- Adobe Source Han Serif and Source Han Sans font families are CJK font families. They include Simple Chinese, Traditional Chinese, Japanese and Korean fonts. However, adobe-sourcehanserif-fonts and adobe-sourcehansans-fonts only include Taiwan (Traditional Chinese) fonts. We need to add Simple Chinese, Japanese and Korean fonts or we rename these packages, adding "tc". -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1077015] New: zypper dup/up on Btrfs consume 100% CPU and freeze desktop
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1077015 Bug ID: 1077015 Summary: zypper dup/up on Btrfs consume 100% CPU and freeze desktop 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: guoyunhebrave(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When doing zypper dup or zypper up on Btrfs root partition, a Btrfs process will consume 100% CPU and freeze desktop. Then I have to force shutdown machine by pressing the power button. When reboot system, it cannot boot into system. I run rescue system and use 'btrfs check /dev/sda3' to repair Btrfs file system. Then I can boot to my system. My friend Michael Du has the similar problem with his Tumbleweed system. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1100672] Cargo/Rustc fails on tumbleweed container
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1100672 http://bugzilla.opensuse.org/show_bug.cgi?id=1100672#c2 Luke Jones <jones_ld(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |william(a)blackhats.net.au Flags| |needinfo?(william@blackhats | |.net.au) --- Comment #2 from Luke Jones <jones_ld(a)protonmail.com> --- The compiler itself is able to be used for bare-metal programming, and so doesn't require the rust-std to be installed. rust-std is a "recommends" package due to this. Can you confirm that $rustc -V works fine please? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114391] New: nm-applet background not painted in lxpanel
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1114391 Bug ID: 1114391 Summary: nm-applet background not painted in lxpanel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 788202 --> http://bugzilla.opensuse.org/attachment.cgi?id=788202&action=edit screenshot of lxpanel with broken nm-applet The nm-applet background is not pained in lxpanel. This seems to be a recent regression - was not problem earlier. However, I am not sure what triggered the issue. I was restarting both lxpanel and nm-applet quite often due to some communication problem between the applet and the daemon and lxpanel crashing. Nonetheless, after reboot the background is no longer painted. I am not sure if this is nm-applet or lxpanel problem. Other applets do not show the issue but they are probably LXDE-specific and might just be bug-compatible. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1114388] New: yast get error while update time with ntp server like pool.ntp.org
by bugzilla_noreply＠novell.com 02 Nov '18

02 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1114388 Bug ID: 1114388 Summary: yast get error while update time with ntp server like pool.ntp.org Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: virex(a)mail.ru QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- yast get the error: Cannot connect to server, while updating time from ntp (pool.ntp.org) but ntpdate pool.ntp.org work fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 931296] [plasma5 packaging] cannot unlock locked screen (kcheckpass failure)
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=931296 http://bugzilla.opensuse.org/show_bug.cgi?id=931296#c28 --- Comment #28 from Björn Voigt <bjoernv(a)arcor.de> --- (In reply to Wolfgang Bauer from comment #27) > This one was fixed over 3 years ago. OK thanks, I understand. BTW, is it still necessary to call pam-config -d --unix2 pam-config -a --unix in the postinstall section of kscreenlocker? Some arguments against this solution / work-around: - pam_unix2 is gone since years in TW (software.opensuse.org says, that pam-modules contained pam_unix2 until Leap 42.3) - pam_unix2 was already deprecated since longer time - pam_unix is standard on TW - the kscreenlocker package potentially modifies PAM configuration not only for itself, but for other PAM services, which can cause problems for configurations, where pam_unix is not desired - if the pam_unix2 to pam_unix conversation is still desired (e.g. for the use case that Leap 42.3 systems should be directly updated to Tumbleweed), then the pam-config calls should be made within a more central RPM package (e.g. within "pam") - the only use case for this solution is, that someone updates Leap 42.3 to TW or Leap 15.0 and within the upgrade process the screenlocker starts and no other RPM package (e.g. "pam") has replaced the pam_unix2 configuration. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114383] New: chkstat is not always called after Zypper has installed packages
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1114383 Bug ID: 1114383 Summary: chkstat is not always called after Zypper has installed packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In the old openSUSE times, after each Yast package installation SuSEconfig was called, with did some useful things like checking and applying permissions from /etc/permissions*. Permissions in /etc/permissions* now have to be checked and applied with "chkstat --system --set". Unfortunately Zypper (and maybe Yast (not tested)) do not always call "chkstat --system --set" after packages are updated. As a result permissions may be incorrect after updates and before the user manually calls "chkstat --system --set". For instances the following use case can lock out users: Prerequisite for this example: some special PAM configuration (e.g. pam_yubico) only work, if /usr/lib64/libexec/kcheckpass is set with SGID bit. * user is logged in * user installs updates with "zypper dup" * user locks the screen * user tries to unlock the screen * /usr/lib64/libexec/kcheckpass is changed after "zypper dup" (permissions are standard: -rwxr-xr-x) * kscheckpass fails, user is locked out -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1114258] New: Latest update of kcheckpass breaks custom PAM configuration
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1114258 Bug ID: 1114258 Summary: Latest update of kcheckpass breaks custom PAM configuration Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the latest kscreenlocker changes to resolve bug #931296 manual changes of /etc/pam.d/kscreenlocker get lost after each kscreenlocker update. It is not important, which manual changes are made. I show my changes as an example. My desktop is secured with a Yubikey as a second factor: $ cat /etc/pam.d/kscreenlocker #%PAM-1.0 auth requisite pam_yubico.so <some additional parameters> auth include common-auth account include common-account password include common-password session required pam_loginuid.so session include common-session If I update kscreenlocker my manual configuration are reset and I get: $ cat /etc/pam.d/kscreenlocker #%PAM-1.0 auth include common-auth account include common-account password include common-password session required pam_loginuid.so session include common-session No other PAM service shows this problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1113586] XEN: kernel BUG at ../drivers/block/xen-blkfront.c:338!
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1113586 http://bugzilla.suse.com/show_bug.cgi?id=1113586#c6 --- Comment #6 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1113586) was mentioned in https://build.opensuse.org/request/show/645932 15.0 / kernel-source -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1113151] Out of date package: openSUSE:Factory/libisoburn is out of date
by bugzilla_noreply＠novell.com 01 Nov '18

01 Nov '18

http://bugzilla.suse.com/show_bug.cgi?id=1113151 Asterios Dramis <asterios.dramis(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS -- You are receiving this mail because: You are on the CC list for the bug.

1 0