March 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1083476] New: Build sanity checks force packages to own directories that already belong to another package
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1083476 Bug ID: 1083476 Summary: Build sanity checks force packages to own directories that already belong to another package 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: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Some sanity checks are done during the build of packages by OBS (near the end of the build process). However one of them seems incorrect: [ 150s] ... running 50-check-binary-kernel-log [ 150s] ... running 50-check-debuginfo [ 150s] ... testing for empty debuginfo packages [ 150s] ... running 50-check-filelist [ 150s] ... checking filelist [ 151s] systemd-mini-237-292.1.i586.rpm: directories not owned by a package: [ 151s] - /usr/lib/modprobe.d In this case systemd installs a file in /usr/lib/modprobe.d but it seems wrong to force systemd to own the directory since it belongs to kmod. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 967176] erlang-wx has wrong wx requirements.
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=967176 SMASH SMASH <smash_bz(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| | maint:planned:update -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1080344] BUG: sleeping function called from invalid context at ../fs/buffer.c:1396
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1080344 SMASH SMASH <smash_bz(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:6666:important |ibs:running:6666:important | |maint:planned:update -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084661] New: Drop Bitstream Speedo Fonts
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1084661 Bug ID: 1084661 Summary: Drop Bitstream Speedo Fonts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: sndirsch(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- - Drop font-bitstream-speedo-1.0.2.tar.bz2, Speedo font format is deprecated since X11R7.0 (released 2005-12-21) -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 971221] New: Last desktop kernel update (3.11.10-34 to 3.12.53-40.1) breaks ethernet
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=971221 Bug ID: 971221 Summary: Last desktop kernel update (3.11.10-34 to 3.12.53-40.1) breaks ethernet Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: llevrel(a)yahoo.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I update my opensuse 13.1 once a week, usually on Mondays. Yesterday's update pulled kernel 3.12.53-40.1-desktop to replace 3.11.10-34-desktop. This morning, no ethernet connectivity after booting. Reverting to 3.11.10-34-desktop and rebooting restores connectivity. lspci -k: 00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03) Subsystem: Hewlett-Packard Company Compaq 6910p Kernel driver in use: e1000e Kernel modules: e1000e Wifi works with both kernel versions. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1074891] Error on upgrade process of bootloader and calling the bootloader customisation through YAST2
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1074891 http://bugzilla.suse.com/show_bug.cgi?id=1074891#c11 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #11 from Josef Reidinger <jreidinger(a)suse.com> --- workaround in cfa merged -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1055993] New: syslog-ng consuming 100% cpu
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1055993 Bug ID: 1055993 Summary: syslog-ng consuming 100% cpu Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 738530 --> http://bugzilla.opensuse.org/attachment.cgi?id=738530&action=edit syslog-ng.conf For no apparent reason syslog-ng started consuming 100% cpu in openSuSE Leap 42.3. This didn't happen in Leap 42.2. The configuration file didn't change since. syslog-ng.conf is attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1076839] [Build 20180117] installer startup: kexec failed
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1076839 http://bugzilla.suse.com/show_bug.cgi?id=1076839#c20 --- Comment #20 from Steffen Winterfeldt <snwint(a)suse.com> --- Yes, but I would very much like to avoid this kind of code. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1084670] New: screen lock: password input focus on multimonitor setup
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1084670 Bug ID: 1084670 Summary: screen lock: password input focus on multimonitor setup 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: P.Suetterlin(a)royac.iac.es QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using my laptop (Lenovo T460p) for work both at home and at the office. At the office I have a docking station with a second monitor, set up as an area next to the main screen (i.e., not in copy mode). Normal procedure is to only suspend the laptop (close lid), and resume, which starts the lock screen. If I resume, or lock the screen, in the dual monitor config, lock screen and unlock prompts are displayed on both screens. But only one of the password fields can get the input focus. That is, I can click the password field e.g. on the laptop screen, and enter my password. It shows up as bullets, but only on that screen. The input field on the other monitor stays empty. I can move the mouse cursor to the second screen, but clicking the input field there does *not* move the focus there. I am not able to input anything. I can however click on any of the entries (like switch user, login). But if I click 'login' it uses the (empty) password from that screen and of course fails to unlock the session. The first time I have noticed this was in TW 20180227, likely because the input focus was on the second screen there, as I could not enter my password on the laptop screen. At that time, I did not look at the second screen at all, sorry. I only had a closer look after finding some older (redhat-related) postings regarding input focus. But the issue seems new, I've been using this laptop for more than 1 1/2 years in sucht dual-config without seeing this once. In case it's relevant: The laptop has an optimus setup, but I use the CPU-included one (i7 - HD530, using intel driver) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1076839] [Build 20180117] installer startup: kexec failed
by bugzilla_noreply＠novell.com 09 Mar '18

09 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=1076839 http://bugzilla.suse.com/show_bug.cgi?id=1076839#c19 --- Comment #19 from Michal Suchanek <msuchanek(a)suse.com> --- There is a workaround - you just try both calls. A final solution is under discussion with upstream. -- You are receiving this mail because: You are on the CC list for the bug.

1 0