January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 846807] 131.1 RC1 - I managed to destroy a btrfs - anyone wants to investigate it?
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=846807 http://bugzilla.opensuse.org/show_bug.cgi?id=846807#c9 Libor Pechacek <lpechacek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |lpechacek(a)suse.com Resolution|--- |FIXED --- Comment #9 from Libor Pechacek <lpechacek(a)suse.com> --- Given that all currently maintained openSUSE kernels are newer than v3.12 (the SLE 12 kernel), I am closing this issue as fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 989501] WARNING: CPU: 0 PID: 1690 at ../drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank+0x175/0x180 [drm]()
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=989501 http://bugzilla.suse.com/show_bug.cgi?id=989501#c20 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #20 from Takashi Iwai <tiwai(a)suse.com> --- Let's track in the upstream bugzilla. Meanwhile, if you see the same issue in openSUSE-42.2 kernel, feel free to reopen, or better clone to another bug. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 987873] New: VUL-0: CVE-2016-6173: nsd: malicious primary DNS servers can crash secondaries
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=987873 Bug ID: 987873 Summary: VUL-0: CVE-2016-6173: nsd: malicious primary DNS servers can crash secondaries Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: All Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software Assignee: mrueckert(a)suse.com Reporter: astieger(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: mrueckert(a)suse.com Found By: Security Response Team Blocker: --- Courtesy bug from the SUSE security team for server:dns/nsd via oss-sec http://seclists.org/oss-sec/2016/q3/19 "most DNS server implementations do not implement reasonable restrictions for zone sizes. This allows an explicitly configured primary DNS server for a zone to crash a secondary DNS server, affecting service of other zones hosted on the same secondary server." from https://lists.dns-oarc.net/pipermail/dns-operations/2016-July/015058.html > * [ For [LT] Secondary DNS Service ] > > See https://github.com/sischkg/xfer-limit > > Most of authoritative DNS server softwares do not have size limit of > zone transfer. He generated unlimited zone information at master > server, and transfered to slave servers. BIND 9, knot DNS and Power > DNS slave servers received unlimited zone informataion and died. > NSD slave DNS server received unlimited zone data and /tmp became full. > > He generated zone transfer size limit patch for BIND 9, Knot, NSD, > PowerDNS. Third party patches at https://github.com/sischkg/xfer-limit References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-6173 http://seclists.org/oss-sec/2016/q3/20 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 987307] New: Can not edit the wiki due to abuse filter
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=987307 Bug ID: 987307 Summary: Can not edit the wiki due to abuse filter Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Infrastructure Assignee: mrueckert(a)suse.com Reporter: tbechtold(a)suse.com QA Contact: lars.vogdt(a)microfocus.dmm Found By: --- Blocker: --- Since 3 days I try to update https://en.opensuse.org/index.php?title=openSUSE:Packaging_Python&action=ed… but the abuse filter is preventing this. I get: Your IP address has been automatically blocked because it was used by another user, who was blocked by Abuse filter. The reason given is: Autoblocked because your IP address has been recently used by "Fandonoberge". The block id is #443. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 818373] chattr cannot add compression flags (+c) to some files on btrfs
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=818373 http://bugzilla.opensuse.org/show_bug.cgi?id=818373#c12 --- Comment #12 from Libor Pechacek <lpechacek(a)suse.com> --- (In reply to Filipe Manana from comment #10) > Jeff has a patch that updates the documentation and makes lsattr show X > (FS_NOCOMP_FL) regardless of building with or without --enable-compression. FS_NOCOMP_FL is gone from e2fsprogs. It needs to be re-added for Btrfs. http://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/commit/lib/e2p/pf.c?id=4a0… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 818373] chattr cannot add compression flags (+c) to some files on btrfs
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=818373 http://bugzilla.opensuse.org/show_bug.cgi?id=818373#c11 Libor Pechacek <lpechacek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium CC| |lpechacek(a)suse.com Component|Basesystem |Kernel Version|Final |Current Product|openSUSE 12.3 |openSUSE Tumbleweed Severity|Major |Minor --- Comment #11 from Libor Pechacek <lpechacek(a)suse.com> --- Replicated with Tumbleweed 20161226, kernel 4.9.0-2-default. Contemplating about the FS_IOC_SETFLAGS IOCTL behavior, the logic ioctl.c:check_flags() looks ill to me. My thinking is that with FS_COMPR_FL I am telling kernel that I am willing to accept performance hit on file read and write operations in exchange for lower disk space consumption. It goes without saying that I don't know how much space I save and the savings can be anywhere between 0% to 99.9%. Therefore kernel pushing back against my request with -EINVAL, in the 0% savings scenario, makes absolutely no sense to me. It looks to me like the piece of code should be dropped. Opinions? diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c index 33f967d30b2a..8c9c5aa445dc 100644 --- a/fs/btrfs/ioctl.c +++ b/fs/btrfs/ioctl.c @@ -206,9 +206,6 @@ static int check_flags(unsigned int flags) FS_NOCOW_FL)) return -EOPNOTSUPP; - if ((flags & FS_NOCOMP_FL) && (flags & FS_COMPR_FL)) - return -EINVAL; - return 0; } -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1003886] systemd-sysctl Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or directory
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1003886 http://bugzilla.suse.com/show_bug.cgi?id=1003886#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkubecek(a)suse.com, | |tiwai(a)suse.com --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- I guess these are entries in /usr/lib/sysctl.d/50-default.conf from aaa_base: # Disable NAT'ing on Linuxbridges (bnc#845496) net.bridge.bridge-nf-call-ip6tables = 0 net.bridge.bridge-nf-call-iptables = 0 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 936573] New: home:darix:neovim/neovim: Bug: Unhandled OSC when using :term
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=936573 Bug ID: 936573 Summary: home:darix:neovim/neovim: Bug: Unhandled OSC when using :term Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: mrueckert(a)suse.com Reporter: damienradtke(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- After installing neovim and opening up the built-in terminal emulator (:term), it continuously reports this error: libvterm: Unhandled OSC 7 It looks like this is an error with how the libvterm dependency is built, as documented here: https://github.com/neovim/neovim/issues/2251 Tested with NVIM 0.0.0-alpha (compiled May 22 2015 21:13:03) running in GNOME Terminal 3.14.3-7.1, openSUSE 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1010125] New: Clean up the Mono project
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1010125 Bug ID: 1010125 Summary: Clean up the Mono project Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request Assignee: mrueckert(a)suse.com Reporter: matthias(a)mailaender.name QA Contact: adrian(a)suse.com Found By: --- Blocker: --- We need to do something about https://build.opensuse.org/project/show/Mono The request from dutchglory has been ignored for > 1 year. My https://build.opensuse.org/request/show/415017 is unanswered for > 4 months. Either delete/archive it or give someone, who is still active on OBS access. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1004945] Shutdown incomplete - default Kernel regression Tumbleweed > 4.6?
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=1004945 http://bugzilla.suse.com/show_bug.cgi?id=1004945#c1 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |tiwai(a)suse.com Resolution|--- |FIXED --- Comment #1 from Takashi Iwai <tiwai(a)suse.com> --- There was some shutdown problem that has been addressed recently, so supposedly this should have been fixed in 4.9 kernel. Please reopen if you still have the same problem with the latest kernel. -- You are receiving this mail because: You are on the CC list for the bug.

1 0