http://bugzilla.suse.com/show_bug.cgi?id=1106751
Bug ID: 1106751
Summary: iptables does not work with kernel-default-base
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-maintainers(a)forge.provo.novell.com
Reporter: fvogt(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Initially reported as
https://github.com/kubic-project/automation/pull/474#issuecomment-417329301
Docker (and cri-o) do not work in Kubic VM images as iptables does not work:
g47:~ # iptables -L
iptables: No chain/target/match by that name.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=944832
Bug ID: 944832
Summary: installing updates during shutdown causes reboot
Classification: openSUSE
Product: openSUSE Distribution
Version: 42.1 Milestone 2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
Assignee: bnc-team-gnome(a)forge.provo.novell.com
Reporter: ohering(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
fresh leap milestone 2.
I switched from the iso install source to the online oss repo. This repo had a
few differend packages compared to the iso. The gnome software installer
recognized them as updates. Once I had to shutdown the system it offered a knob
to install pending updates, then shutdown. I enabled that box, and hit return.
I think nothing was downloaded, but the box did a reboot instead of the
expected shutdown.
If that feature is not ready yet I suggest to hide it for the time being to
really and always do a reliable powerdown if that was requested.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093592
Bug ID: 1093592
Summary: redshift doesn't work after geoclue2 update
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X11 Applications
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: dmarcoux(a)posteo.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 770512
--> http://bugzilla.opensuse.org/attachment.cgi?id=770512&action=edit
redshift error
Hello,
I updated to the latest snapshot (2018 05 15) and since then, redshift with
geoclue2 doesn't work. After launching, it displays an error (see attachment).
This wasn't happening with the previous snapshot I had, but I'm not sure which
one. The issue seems to arise due to changes within the recent revisions of the
geoclue2 package, so as far as 2 months ago. So by looking at the snapshots, I
suspect it is in one of those:
- 2018 03 04
- 2018 04 24
- 2018 05 11
- 2018 05 13
The workaround is to provide the latitude and longitude manually with the
option -l.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111657
Bug ID: 1111657
Summary: python-cffi build fail with glibc maintenance update
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.1
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: mlin(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
With glibc maintenance update https://build.opensuse.org/request/show/639803 ,
python-cffi build failed due to it can not pass unittest[1]. Both package are
from SLE.
[1]
https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.1:Stagin…
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1136584
Bug ID: 1136584
Summary: osc build requires running in a checked out directory
even with --alternative-project
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.1
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Development
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: mkubecek(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Since upgrading my Leap 15.0 system to Leap 15.1, "osc build" requires current
directory to be a checked out working copy even when "--alternative-project"
argument is used:
> mike@unicorn:~/work/git/sle-ksource/kernel-source> osc build --alternative-project openSUSE:Factory kernel-default.spec
> Error: "/srv/git/sle-ksource/kernel-source" is not an osc package working copy.
Leap 15.0 and 42.3 version did not require this and the example used to work
with only package contents in current directory (and no .osc/* metadata).
Last known good version: 0.162.1-lp150.1.3 (Leap 15.0)
First known bad version: 0.165.0-lp151.1.1 (Leap 15.1)
According to Jiří Slabý, 0.164.2 also works.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1089025
Bug ID: 1089025
Summary: [diff] osc diff -r rev1:rev2 is not always working as
expected
Classification: Internal Novell Products
Product: openSUSE Build Service
Version: 2.5
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: osc
Assignee: adrian(a)suse.com
Reporter: eich(a)suse.com
QA Contact: adrian(a)suse.com
Found By: Development
Blocker: ---
'osc diff' is not always producing output reliably: Using it on a devel
project, it looks like it produces no output when the submission to factory has
been 'folded back' - which is quite annoying.
In science/netcdf-cxx4 on OBS a 'osc diff -r 22:20' (or osc 'diff -r 20:22')
produces no output nor does it for any earlier commits.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1024727
Bug ID: 1024727
Summary: Cannot login to Bugzilla using Bugzilla "login" button
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Bugzilla
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: qantas94heavy(a)gmail.com
QA Contact: novbugzilla-bugs(a)forge.provo.novell.com
Found By: ---
Blocker: ---
Created attachment 713674
--> http://bugzilla.opensuse.org/attachment.cgi?id=713674&action=edit
Unprocessed PHP file
I attempted to login to Bugzilla by clicking the "Login" button on the Bugzilla
home page, which took me to the following URL:
https://login.microfocus.com/nidp/idff/sso?id=132&sid=5&option=credential&s…
Instead of receiving the page as usual, it appears to load some scripts from
the following URL:
https://www.suse.com/common/inc/include.php?file=headers/hdr_head.html
The PHP file there appears to be unprocessed, which is most likely causing the
issue here.
I was only able to login by going through the openSUSE wiki then going back to
Bugzilla.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1047225
Bug ID: 1047225
Summary: LUKS password doesn't show up when booting with
nomodeset
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: tiwai(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Install a TW system with the standard procedure for LVM+encrpption as suggested
by installer on KVM. It works fine with the graphical LUKS password.
But when you boot with nomodeset boot option, the boot process hangs without
asking the LUKS password.
This didn't happen on openSUSE Leap 42.2 / 42.3. And when I upgrade only
plymouth packages on the Leap system, it starts showing the same problem.
So, it's a regression in the recent plymouth package.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1096833
Bug ID: 1096833
Summary: VUL-0: matrix-synapse: event visibility rules not
applied correctly
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.0
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Security
Assignee: okurz(a)suse.com
Reporter: astieger(a)suse.com
QA Contact: security-team(a)suse.de
Found By: ---
Blocker: ---
from https://github.com/matrix-org/synapse/releases/tag/v0.31.1
Changes in synapse v0.31.1 (2018-06-08)
v0.31.1 fixes a security bug in the get_missing_events federation API
where event visibility rules were not applied correctly.
We are not aware of it being actively exploited but please upgrade asap.
Bug Fixes:
Fix event filtering in get_missing_events handler (PR #3371)
https://github.com/matrix-org/synapse/commit/ad9edd1d968f19dd4d7c65102fe552…
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1029190
Bug ID: 1029190
Summary: Support for package variants according to the
evaluation of bigger regular expressions
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: All
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: Development
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: Markus.Elfring(a)web.de
QA Contact: qa-bugs(a)suse.de
CC: astieger(a)suse.com
Found By: ---
Blocker: ---
I noticed that the parameter “--with-link-size=2” is used so far in a package
specification.
https://build.opensuse.org/package/view_file/openSUSE:Factory/pcre2/pcre2.s…
This setting limits the size of regular expressions. I would like to work with
bigger search patterns occasionally. So I suggest to generate also variants for
this software with an internal link size of 3 (and 4) for the data processing
with 8 and 16 bit characters.
See also:
Selection of system properties for the regular expressions engine at run time
https://bugs.exim.org/show_bug.cgi?id=1922
By the way:
How do you think about to use the specifications “LDFLAGS“ und
“%{?_smp_mflags}“ as parameters for the script “%configure“ there?
--
You are receiving this mail because:
You are on the CC list for the bug.