May 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1036799] Please add "advisor" to hunspell's and LibreOffice's US dictionaries
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036799 http://bugzilla.suse.com/show_bug.cgi?id=1036799#c2 --- Comment #2 from Petr Gajdos <pgajdos(a)suse.com> --- (In reply to Leon Meier from comment #1) > FYI: https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/en_US.dic > does not contain "advisor" either. However, I'm not sure whether that > dictionary is the source for OpenSuse's dictionaries, and, even if so, who > would be the maintainer. Yes, we are using these sources. Could you please fill an upstream bug and reference it here? https://bugs.documentfoundation.org/ Thank you -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1037115] New: kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available)
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1037115 Bug ID: 1037115 Summary: kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- During boot systemd seems to read more randomness than available. Maybe it's related to using encrypted filesystems. Example: May 02 08:50:45 linux-n9gv systemd[1]: RTC configured in localtime, applying delta of 120 minutes to system time. May 02 08:50:45 linux-n9gv kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available) May 02 08:50:45 linux-n9gv kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available) May 02 08:50:45 linux-n9gv kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available) May 02 08:50:45 linux-n9gv systemd[1]: systemd 228 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNU May 02 08:50:45 linux-n9gv systemd[1]: Detected architecture x86-64. May 02 08:50:45 linux-n9gv systemd[1]: Running in initial RAM disk. May 02 08:50:45 linux-n9gv systemd[1]: Set hostname to <linux-n9gv>. May 02 08:50:45 linux-n9gv kernel: random: systemd-cryptse: uninitialized urandom read (16 bytes read, 10 bits of entropy available) May 02 08:50:45 linux-n9gv kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available) May 02 08:50:45 linux-n9gv kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available) May 02 08:50:45 linux-n9gv kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available) May 02 08:50:45 linux-n9gv kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available) May 02 08:50:45 linux-n9gv kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available) May 02 08:50:45 linux-n9gv kernel: random: systemd: uninitialized urandom read (16 bytes read, 10 bits of entropy available) May 02 08:50:45 linux-n9gv systemd[1]: Reached target Swap. This is for an AMD Phenom II CPU, but I see similar with an Intel Core Gen 4 CPU (that should have a built-in random generator). -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1036979] python2-qt4 posttrans fails
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036979 http://bugzilla.suse.com/show_bug.cgi?id=1036979#c2 --- Comment #2 from Olaf Hering <ohering(a)suse.com> --- posttrans scriptlet (using /bin/sh): if [ -e "/usr/bin/pyuic4}-2.7" ]; then update-alternatives --install /usr/bin/pyuic4 pyuic4 /usr/bin/pyuic4-2.7 27 \ fi -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036799] Please add "advisor" to hunspell's and LibreOffice's US dictionaries
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036799 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pgajdos(a)suse.com Assignee|bnc-team-screening(a)forge.pr |tchvatal(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036939] graphics/ImageMagick: Broken jpeg2000 support
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036939 http://bugzilla.suse.com/show_bug.cgi?id=1036939#c1 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Petr Gajdos <pgajdos(a)suse.com> --- Please install ImageMagick-extra package. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1031550] New: Installation summary system type is always KDE Plasma Desktop
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1031550 Bug ID: 1031550 Summary: Installation summary system type is always KDE Plasma Desktop Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers(a)suse.de Reporter: jmader2(a)gmu.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When using autoyast, the system type is always reported as KDE Plasma Desktop at the installation summary screen, despite selecting only gnome patterns and no KDE. <patterns config:type="list"> <pattern>gnome</pattern> <pattern>gnome_admin</pattern> <pattern>gnome_basis</pattern> <pattern>gnome_basis_opt</pattern> </patterns> and /etc/sysconfig/displaymanager does end up, DISPLAYMANAGER="gdm" -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1035824] New: Game endless-sky-0.9.4-3.1.x86_64 freezes the display sporadically
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1035824 Bug ID: 1035824 Summary: Game endless-sky-0.9.4-3.1.x86_64 freezes the display sporadically Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sebastian.parschauer(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The game endless-sky with version 0.9.4-3.1 is unplayable on openSUSE Leap 42.1. It sporadically freezes the whole screen especially on the space map and on the outfitter screen after 20min of playing at max. Once it was possible to use Ctrl + Alt + F2 to capture the kernel stack trace and the gdb backtrace but I've noticed that no debuginfo package is built. I could only see that libxcb is involved and that it is hanging in poll(). Usually it crashes in a way that also switching the login terminal is not possible and even a kdump can't be triggered by sysrq-c. It happens both in window mode and fullscreen mode. Other games like e.g. Chromium B.S.U. or Warzone 2100 work fine. HW is a Lenovo Thinkpad X250 laptop. Display manager: gdm Window manager GNOME 3 Will build with debuginfo and retest, will update to version 0.9.6 and retest. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1036630] [Build 20170425] openQA test fails in yast2_dns_server: saving the configuration failed
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036630 http://bugzilla.suse.com/show_bug.cgi?id=1036630#c5 --- Comment #5 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Oliver Kurz from comment #3) > so the change was introduced between Build20170329 and Build20170331 and I > guess it's some "pattern" change or something? Should the yast configuration > module now required whatever provides the "named" service now? named is still using LSB init scripts and no systemd services. But could be a duplicate of bsc#1035062 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1035062] Tumbleweed no longer executes scripts in /etc/init.d
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1035062 http://bugzilla.suse.com/show_bug.cgi?id=1035062#c9 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrick.schaaf(a)yalwa.com --- Comment #9 from Thorsten Kukuk <kukuk(a)suse.com> --- *** Bug 1036819 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036819] named no longer starts on boot
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036819 http://bugzilla.suse.com/show_bug.cgi?id=1036819#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- systemd still uses 15 year old compat links ... *** This bug has been marked as a duplicate of bug 1035062 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0