body:
--1582669430.5a6F06161.25738
Date: Tue, 25 Feb 2020 22:23:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1164903

            Bug ID: 1164903
           Summary: go1.14 release tracking
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: jkowalczyk-at-suse.com
          Reporter: jkowalczyk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

go1.14 (released 2019-02-25) is a major release of Go.
Minor releases of go1.14.x will be provided through August 2020.
This issue tracks go1.14.x releases packaged and submitted initially
to openSUSE:Factory and can be referenced in submissions to
additional repositories.

Go Release Cycle
https://github.com/golang/go/wiki/Go-Release-Cycle

Go Release history
https://golang.org/doc/devel/release.html

summary: go1.14 release tracking


--1582711844.c5eBDc70.1123
Date: Wed, 26 Feb 2020 10:10:44 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1164970

            Bug ID: 1164970
           Summary: [Build 20200225] gnuhealth_setup: Fails to launch gnuhealt since python-Werkzeug update
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1187258/modules/gnuh
                    ealth_setup/steps/13
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dimstar-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

## Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-gnuhealth@64bit fails in
[gnuhealth_setup](https://openqa.opensuse.org/tests/1187258/modules/gnuhealth_setup/steps/13)

python-Werkzeug was updated to version 1.0.0 with SR#777800

Seems Gnuhealth is not (yet) compatible to this version Werkzeug.

## Test suite description
Maintainer: okurz-at-suse.de
Test scenario for gnuhealth software stack

## Reproducible

Fails since (at least) Build
[20200225](https://openqa.opensuse.org/tests/1187258) (current job)

## Expected result

Last good: [20200224](https://openqa.opensuse.org/tests/1186364) (or more
recent)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit&test=gnuhealth&version=Tumbleweed)


--1582721936.F7Ccddf0.6731
Date: Wed, 26 Feb 2020 12:58:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165011

            Bug ID: 1165011
           Summary: systemd-mount cannot mount network mounts
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: tux93-at-opensuse.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Trying to mount a NFS mount with systemd-mount on openSUSE Leap 15.1 results in
`Failed to canonicalize path: No such file or directory`

Related Fedora / RHEL report:
https://bugzilla.redhat.com/show_bug.cgi?id=1708996

Upstream PR with fix:
https://github.com/systemd/systemd/pull/12765


--1582737789.82ed7C0.27533
Date: Wed, 26 Feb 2020 17:23:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165047

            Bug ID: 1165047
           Summary: CD tray closed immediately after ejecting media
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: ml.heimburg@t-online.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello,

after updating aaa_base to the version
aaa_base-84.87+git20180409.04c9dae-lp151.5.18.1.x86_64.rpm the CD tray closed
immediately after ejecting a media. So it is not possible to take the media out
of the CD tray, because the time is too short between the opening and closing
of the CD tray.
This behavior does not depend from any other programs. It is reproducible every
time when a CD, DVD or BD is injected in the CD tray.

With the version aaa_base-84.87+git20180409.04c9dae-lp151.5.15.1.x86_64.rpm all
media will be ejected correctly.

System opensuse Leap 15.1


body:
--1582795088.ADEADB70.32749
Date: Thu, 27 Feb 2020 09:18:08 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165110

            Bug ID: 1165110
           Summary: Post-build checks fail when encoutering non-ascii characters
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: christophe-at-krop.fr
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

opentoonz[1] started failing to build for Leap 15.x (including 15.2) with this
error:

[ 1983s] RPMLINT report:
[ 1983s] ===============
[ 2003s] 0 packages and 0 specfiles checked; 0 errors, 182 warnings.
[ 2003s] Traceback (most recent call last):
[ 2003s]   File "rpmlint.py", line 380, in <module>
[ 2003s]   File "rpmlint.py", line 166, in main
[ 2003s]   File "rpmlint.py", line 223, in runChecks
[ 2003s]   File "DuplicatesCheck.py", line 61, in check
[ 2003s] UnicodeEncodeError: 'ascii' codec can't encode character '\xf1' in
position 95: ordinal not in range(128)

ie, it chokes on 'ñ' contained in some folders name.

This prevents submitting the opentoonz update to Leap:15.2 [2]. The tumbleweed
build has no issue.

There are a couple folders which cause issues:
opentoonz-1.4.0 # ls -d

pkgs: opentoonz rpmlint-mini


--1582845544.a40aEf0.5031
Date: Thu, 27 Feb 2020 23:19:04 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165206

            Bug ID: 1165206
           Summary: Xen 4.12 DomU hang / freeze / stall / NMI watchdog bug soft lockup CPU #0 stuck under high load / upstream with workaround
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: glenbarney-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Executive Summary:

I am reporting a bug which appears to be related to Xen 4.12.  It is being
discussed upstream.  A workaround is available which I will describe.  Although
this is not a specific OpenSuse bug, I was asked to report it here by OpenSuse
team members, and am therefore doing so.

Short Version:

On OpenSuse 15.1 running Xen 4.12.1, with all zypper updates applied as of Feb
2020, DomU guests under high load will stall.  The Dom0 host will continue to
function normally, and report the guest running, with only a single error
message about network connectivity being lost.  Meanwhile the guest will become
unresponsive, even at the virtual console, and, depending on guest kernel
version will provide no output, or will provide running output about NMI
watchdog: BUG: soft lockup CPU#0 stuck.  Once the guest reaches this state, the
guest must be (xl) destroyed, it is not even capable of shutting itself down.

This bug first manifested itself when I upgraded my 42.3 hosts through 15.0 to
15.1.  That was five months ago.  Nobody else had reported this problem
anywhere that I could discover.  A number of avenues were tried, and things
tested.  Initially I thought it was something wrong with my guest; after
several months I was able to duplicate the issue on other hardware with fresh
loads of guest and host.  This led me to the OpenSuse Virtualization community
and, from there, to the Xen community.  BY the time I reached that point,
others had started to report similar issues.  We gathered on the Xen-users
list, and, with their help, sorted through options.

In the end, the problem was narrowed down to the "Credit2 Scheduler".
Apparently there is a bug in that section of Xen 4.12.1 which causes this
problem.  The workaround is to boot the physical host with the additional Xen
boot option "sched=credit".  This causes Xen to use the original "Credit
Scheduler" instead of "Credit2", and, without reported exception, this has
solved the problem for all those who reported it including myself.

I am given to understand that Xen 4.12.2 might include a fix for this, although
I have no personal knowledge of that.  Since I have the brief luxury of having
an extra physical host around, I now have, at the request of the Xen community,
  that one machine back on credit2 for testing purposes, and am feeding its
guest the necessary load to crash it again.  When it crashes, I will send them
the debugging output they have asked for, in the hope that it helps narrow this
down.

Conversations about this bug can be seen at these URLS:
https://lists.opensuse.org/opensuse-virtual/2020-01/date.html
https://lists.opensuse.org/opensuse-virtual/2020-02/date.html
https://lists.xenproject.org/archives/html/xen-users/2020-02/

I will include the details below as requested by team.

Long Version:

Problem:  Xen DomU guests randomly stall under high network/disk loads.  Dom0
is not affected.  Randomly means anywhere between 1 hour and 14 days after
guest boot - the time seems to shorten with (or perhaps the problem is
triggered by) increased network (and possibly disk) activity.

Symptoms on the DomU Guest:
1. Guest machine performs normally until the moment of failure.  No abnormal
log/console entries exist.
2. At the moment of failure, the guest's network goes offline.  No abnormal
log/console entries are written at that moment.
3. Processes which were trying to connect to the network start to consume
increasing amounts of CPU.
4. Load average of the guest starts to increase, continuing upward without
apparent bound.
5. If a high-priority bash shell is left logged in on the guest hvc0 console,
some commands might still be runnable; most are not.
6. If the guest console is not logged in, the console is frozen and doesn't
even echo characters.
7. Some guests will output messages on the console like this:
kernel: [164084.912966] NMI watchdog: BUG: soft lockup - CPU#16 stuck for 67s!
8. On some others,  I will also see output like:
BUG: workqueue lockup - pool cpus=20 node=0 flags=0x0 nice=-20 stuck for 70s!
9. Sometimes there is no output at all on the console.

Symptoms on the Dom0 Host:
The host is unaffected.  The only indication anything is happening on the host
are two log entries in /var/log/messages:
vif vif-6-0 vif6.0: Guest Rx stalled
br0: port 2(vif6.0) entered disabled state

Circumstances when the problem first occurred:
1. All hosts and guests were previously on OpenSuse 42.3 (Linux 4.4.180, Xen
4.9.4)
2. I upgraded one physical host to OpenSuse 15.1 (Linux 4.12.14, Xen 4.12.1).
3. The guest(s) started malfunctioning at that point.

Immediate steps taken while the guest was stalled, which did not help:
1. Tried to use high-priority shell on guest console to kill high-CPU
processes; they were unkillable.
2. Tried to use guest console to stop and restart network; commands were
unresponsive.
3. Tried to use guest console to shutdown/init 0.  This caused console to be
terminated, but guest would not otherwise shutdown.
4. Tried to use host xl interface to unplug/replug network bridges.
This appeared to work from host side, but guest was unaffected.

One thing which I accidentally discovered that *did* help:
1. Tried ending xl trigger nmi from the host to the guest.

When I trigger the stalled guest with an NMI, I get its attention.
The guest will print the following on the console:

Uhhuh. NMI received for unknown reason 00 on CPU 0.
Do you have a strange power saving mode enabled?
Dazed and confused, but trying to continue

In some cases (pattern not yet known), the guest will then immediately come
back online:  The network will come back online, and all processes will slowly
stop consuming CPU, and things will return to normal.   Existing network
connections were obviously terminated, but new connections are accepted.  In
that case, it's like the guest just magically comes back to life.

When this works, the host log shows:
vif vif-6-0 vif6.0: Guest Rx ready
br0: port 2(vif6.0) entered blocking state
br0: port 2(vif6.0) entered forwarding state

And all seems well... as if the guest had never stalled.

However, this is not reliable.  In some cases, the guest will print those
messages, but the processes will NOT recover, and the network will come back
impaired, or not at all.  When that happens, repeated NMIs do not help:  If the
guest doesn't recover the first time, it doesn't recover at all.

The *only* reliable way to fix this is to destroy the guest completely, and
recreate it.  The guest will then run fine... until the next stall.  But of
course a hard-destroy can't be a healthy thing for a guest machine, and that's
really not a solution.

Long-term mitigation steps which were tried which did not help.
1. Thought this was an SSH bug (since sshd processes were consuming high CPU),
installed latest OpenSSH.
2. Though maybe a PV problem, tried under HVM instead of PV.
3. Noted a problem with grant frames, applied the recommended fix for that, my
config now looks like:
# xen-diag gnttab_query_size 0 # Domain-0
domid=0: nr_frames=1, max_nr_frames=64
# xen-diag gnttab_query_size 1 # Xenstore
domid=1: nr_frames=4, max_nr_frames=4
# xen-diag gnttab_query_size 6 # My guest
domid=6: nr_frames=17, max_nr_frames=256
4. Thought maybe a kernel module might be at issue, reviewed list with OpenSuse
team.
5. Thought this might be a kernel mismatch, was referred to a new kernel by
OpenSuse team (4.12.13 for OpenSuse 42.3).  That changed some of the console
output behavior and logging, but did not solve the problem.
6. Thought this might be a general OS mismatch, tried upgrading the guest to
OpenSuse 15.1/Linux 4.12.14/Xen 4.12.1.  In this configuration, no console or
log output is generated on the guest at all, it just stalls.
7. Assumed (incorrectly, it now turns out) that something was just "wrong" with
my guest, tried a fresh load of host, and a fresh guest.
I thought that would solve it, but to my sadness, it did not.

Which means that this is now a reproducible bug.

Steps to reproduce:
1. Get a server.  I'm using a Dell PowerEdge R720, but this has happened on
several different Dell models.  My current server has two 16-core CPUs, and
128GB of RAM.
2. Load OpenSuse 15.1 (which includes Xen 4.12.1) on the server.  Boot it up in
Xen Dom0/host mode.
3. Create a new guest machine, also with 15.1/4.12.1.
4. Fire up the guest.
5. Put a lot of data on the guest (my guest has 3 TB of files and data).
6. Plug a crossover cable into your server, and plug the other end into some
other Linux machine.
7. From that other machine, start pounding the guest.  An rsync of the entire
data partition is a great way to trigger this.  If I run several outbound
rsyncs together, I can crash my guest in under 48 hours.  If I run 4 or 5, I
can often crash the guest in just 2 hours. If you don't want to damage your
SSDs on your other machine, here's my current command (my host is 192.168.1.10,
and my guest is 192.168.1.11, so I plug in some other machine and make it, say,
192.168.1.12, and then run:

nohup ssh 192.168.1.11 tar cf - --one-file-system /a | cat > /dev/null &

Where /a is my directory full of user data.  4-6 of these running
simultaneously will bring the guest to its knees in short order.

On my most recent test, I did the NMI trigger thing, and found this in the
guest's /var/log/messages after sending the trigger (i've removed tagging and
timestamping for clarity:)

Uhhuh. NMI received for unknown reason 00 on CPU 0.
Do you have a strange powersaving mode enabled?
Dazed and confused, but trying to continue
clocksource: timekeeping watchdog on CPU0: Marking clocksource 'tsc'
as unstable because the skew is too large:
clocksource: 'xen' wd_now: 58842b687eb3c wd_last: 55aa97ff29565 mask:
ffffffffffffffff
clocksource: 'tsc' cs_now: 58d3355ea9a87e cs_last: 585cca21d4f074
mask: ffffffffffffffff
tsc: Marking TSC unstable due to clocksource watchdog
BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=-20 stuck for 50117s!
Showing busy workqueues and worker pools:
workqueue events: flags=0x0
   pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=3/256
     pending: clocksource_watchdog_work, vmstat_shepherd, cache_reap
workqueue mm_percpu_wq: flags=0x8
   pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/256
     pending: vmstat_update
workqueue writeback: flags=0x4e
   pwq 52: cpus=0-25 flags=0x4 nice=0 active=1/256
     in-flight: 28593:wb_workfn
workqueue kblockd: flags=0x18
   pwq 1: cpus=0 node=0 flags=0x0 nice=-20 active=2/256
     pending: blk_mq_run_work_fn, blk_mq_timeout_work
pool 52: cpus=0-25 flags=0x4 nice=0 hung=0s workers=3 idle: 32044 18125

That led me to search around, and I tripped over this:
https://wiki.debian.org/Xen/Clocksource , which describes a guest hanging with
the message "clocksource/0: Time went backwards/" Although I did not see this
message, and this is not directly on point with OpenSuse (since our /proc
structure doesn't include some of the switches mentioned), I did notice
clocksource references in the logs (see above), and that led me back to:
https://doc.opensuse.org/documentation/leap/virtualization/html/book.virt/cha-xen-manage.html,
and specifically the tsc_mode setting.  I have no idea if it's relevant, but I
since I'm out of ideas and have nothing better to try, I have now booted my
guest into tsc_mode=1 and am stress testing it to see if it fares any better
this way.

I had originally thought that I was the only person with this problem, and
that's why I thought a fresh guest would fix it - the problem followed me
around different servers, so that made sense.  Over the past weeks I've set up
a fresh guest on my fresh host, and, just on a whim, did the above stress
testing on it... it lasted for 36 hours.

That led me to start searching the net again, and I found that, just in the
past few weeks, another person has reported what seems to be the same problem,
only he reported it to Xen-users (so I assume he's on a different distro - see
https://lists.xenproject.org/archives/html/xen-users/2020-02/msg00015.html for
the overall message.)  Nobody has responded to him yet... but I'm about to...
I'm going to send this report there too.   He states that the problem is
limited to Xen 4.12 and 4.13, and that rolling back to Xen 4.11 solves the
problem.

Conclusion:

After sending the above mentioned report, I spent several weeks working with
the team on Xen-users, led by one of their volunteers, who helped narrow this
down.  It turns out 4 or 5 other people were impacted (so far).  One of the
other affected users tried the credit scheduler option - and it turned out that
mitigated the issue.

I will be sending debugging information to them as soon as I am able to
generate it, hopefully within the next day or two.


--1582881197.107C74C47.3299
Date: Fri, 28 Feb 2020 09:13:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165235

            Bug ID: 1165235
           Summary: Undefined symbol error when running bemenu
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: amk-at-amk.ie
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

When running be menu i recieve the following error:

> /usr/lib64/bemenu/bemenu-renderer-curses.so: undefined symbol: get_wch

related to: https://github.com/Cloudef/bemenu/issues/26


--1582902790.A0AF3a0.9943
Date: Fri, 28 Feb 2020 15:13:10 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1165293

            Bug ID: 1165293
           Summary: keepassx window hides immediately after shown
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: msuchanek-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Sometimes when clicking the tray icon to show keepasx window it is shown and
then hidden again immediately


--1582905497.58B4e0.24957
Date: Fri, 28 Feb 2020 15:58:17 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165303

            Bug ID: 1165303
           Summary: VUL-1: CVE-2020-6802: python-bleach: mutation XSS vulnerability
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
               URL: https://smash.suse.de/issue/253881/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: atoptsoglou-at-suse.com
        QA Contact: security-team-at-suse.de
          Found By: Security Response Team
           Blocker: ---

CVE-2020-6802

 Calls to ``bleach.clean`` allowing ``noscript`` and one or more of
  the raw text tags (``title``, ``textarea``, ``script``, ``style``,
  ``noembed``, ``noframes``, ``iframe``, and ``xmp``) were vulnerable
  to a mutation XSS.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-6802
http://people.canonical.com/~ubuntu-security/cve/2020/CVE-2020-6802.html
https://bugzilla.mozilla.org/show_bug.cgi?id=1615315


body:
--1582908022.bf865F0.11817
Date: Fri, 28 Feb 2020 16:40:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165313

            Bug ID: 1165313
           Summary: miredo spams syslog with debug messages
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Network
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dev.rindeal+opensuse-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Example:

```
06:29:23 localhost miredo[1477]: <IPV6_ADDRESS_REDACTED>: ping returned 0
06:29:23 localhost miredo[1477]: Connecting <unknown>: NOT trusted, NOT valid,
0 pings, 0 bubbles
06:29:23 localhost miredo[1477]: <IPV6_ADDRESS_REDACTED>: ping returned 0
06:29:24 localhost miredo[1477]: Connecting <unknown>: NOT trusted, NOT valid,
0 pings, 0 bubbles
06:29:24 localhost miredo[1477]: <IPV6_ADDRESS_REDACTED>: ping returned 0
06:29:24 localhost miredo[1477]: Connecting <unknown>: NOT trusted, NOT valid,
0 pings, 0 bubbles
06:29:24 localhost miredo[1477]: <IPV6_ADDRESS_REDACTED>: ping returned 0
06:29:26 localhost miredo[1477]: Connecting <unknown>: NOT trusted, NOT valid,
0 pings, 0 bubbles
06:29:26 localhost miredo[1477]: <IPV6_ADDRESS_REDACTED>: ping returned 0
06:29:28 localhost miredo[1477]: Connecting <unknown>: NOT trusted, NOT valid,
0 pings, 0 bubbles
```

Quick fix:

`/etc/systemd/system/miredo-client.service.d/override.conf`:
```
[Service]
LogLevelMax=info
```

`miredo-server.service` will need the same patch.

Proper fix is on the source code level, I have prepared a patch and will be
working with upstream to get it into mainline.

summary: miredo spams syslog with debug messages


body:
--1582995432.1f770.27900
Date: Sat, 29 Feb 2020 16:57:12 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1165352

            Bug ID: 1165352
           Summary: htop -s PERCENT_MEM segfaults
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: luis.chamberlain-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

htop segfaults when you use the shorter version of sort. For instance this
works:

htop --sort-key PERCENT_MEM

But this segfaults:

htop -s PERCENT_MEM

summary: htop -s PERCENT_MEM segfaults


--1583005288.cFB46CfC0.17272
Date: Sat, 29 Feb 2020 19:41:28 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165355

            Bug ID: 1165355
           Summary: graphics/qview: resources are not fetched correctly from upstream
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dev.rindeal+opensuse-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Upstream stores the resources using Git LFS, but your source package doesn't
resolve the LFS links to their content.

For example `/usr/share/icons/hicolor/64x64/apps/qview.png` now contains

```
version https://git-lfs.github.com/spec/v1
oid sha256:9aa4f8cb73dfc3ce8935dcc3815e65e8963dc4e7abab0c1d8729285240c723bc
size 5105
```

instead of an actual image.


--1583007237.f5AB8b3E3.2698
Date: Sat, 29 Feb 2020 20:13:57 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165357

            Bug ID: 1165357
           Summary: [Build 595.1] openQA test fails in check_upgraded_service - registered segfault
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
               URL: https://openqa.opensuse.org/tests/1191058/modules/chec
                    k_upgraded_service/steps/8
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: lubos.kocman-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hello

this test expected to receive a message containing BTRFS, however segfault was
registered instead. Can you please investigate?

## Observation

openQA test in scenario
opensuse-15.2-DVD-x86_64-zdup-Leap-42.3-gnome@64bit_cirrus fails in
[check_upgraded_service](https://openqa.opensuse.org/tests/1191058/modules/check_upgraded_service/steps/8)

## Test suite description

## Reproducible

Fails since (at least) Build [563.1](https://openqa.opensuse.org/tests/1161579)

## Expected result

Last good: [557.1](https://openqa.opensuse.org/tests/1153417) (or more recent)

## Further details

Always latest result in this scenario:
[latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensuse&flavor=DVD&machine=64bit_cirrus&test=zdup-Leap-42.3-gnome&version=15.2)


--1583009526.3adFDB40.19082
Date: Sat, 29 Feb 2020 20:52:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165359

            Bug ID: 1165359
           Summary: kmozillahelper crash, presumably due to uploading file
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: opensuse.lietuviu.kalba-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 831640
  --> http://bugzilla.opensuse.org/attachment.cgi?id=831640&action=edit
Backtrace

Application: kmozillahelper (5.0.5)
Qt Version: 5.9.7
Frameworks Version: 5.55.0
Operating System: Linux 4.12.14-lp151.28.36-default x86_64
Distribution: "openSUSE Leap 15.1"

In Firefox I selected DOCX file, I selected to open it with LibreOffice instead
of saving it (thus document was saved in /tmp/mozilla_USER0/ directory). After
some modifications, I saved document into another location but with same name.
Then I selected to upload this document. Site reported that for unknown reason
uploaded document/archive is corrupted; I tried several times; but problem was
same. Finally I get this kmozillahelper crash.
See attachement for backtrace.


body:
--1583131318.8afaDE9.12641
Date: Mon, 2 Mar 2020 06:41:58 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1165389

            Bug ID: 1165389
           Summary: README points to non-existing README.md
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: schwab-at-suse.com
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

libcrypt1 contains a symlink README pointing to non existing README.md
/usr/share/doc/packages/libcrypt1/README

summary: README points to non-existing README.md


body:
--1583151729.edAB1f6B0.15626
Date: Mon, 2 Mar 2020 12:22:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165436

            Bug ID: 1165436
           Summary: AUDIT-0: timeshift: Security review
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: security-team-at-suse.de
          Reporter: malcolmlewis-at-cableone.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Hi
I have submitted the timeshift package to the Archiving:Backup development
repository and request a review the following error and added to defaults for
inclusion in Tumbleweed;

E: polkit-untracked-privilege (Badness: 10000) in.teejeetech.pkexec.timeshift
(auth_admin:auth_admin:auth_admin)

The privilege is not listed in /etc/polkit-default-privs.*

https://build.opensuse.org/package/show/Archiving:Backup/timeshift

summary: AUDIT-0: timeshift: Security review


body:
--1583177796.CE0E0.23710
Date: Mon, 2 Mar 2020 19:36:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165480

            Bug ID: 1165480
           Summary: Pari/GP data from optional packages not found by gp (e.g., pari-elldata)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: x86-64
                OS: openSUSE 13.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: akruppa-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Files installed by packages pari-elldata, pari-galdata, pari-galpol,
pari-seadata
 all get installed under /usr/share/pari/data/ (e.g., pari-elldata installs
file
/usr/share/pari/data/elldata/ell0).

However, the Pari gp program expects these files in /usr/share/pari/elldata/,
without the intermediate "data/ subdirectory. Example:

alex@lily:~> gp -qf
? r=ellinit("11a1")
  ***   at top-level: r=ellinit("11a1")
  ***                   ^---------------
  *** ellinit: error opening elldata file: `/usr/share/pari/elldata/ell0'.
  ***   Break loop: type 'break' to go back to GP prompt
break>

pkgs: pari-elldata pari-galdata pari-galpol pari-seadata


body:
--1583222552.f1Cc10.18927
Date: Tue, 3 Mar 2020 08:02:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165517

            Bug ID: 1165517
           Summary: lldb has a wrong version string
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: martin.liska-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

$ lldb -v
lldb version 9.0.1 ( revision %{_llvm_revision})

summary: lldb has a wrong version string


body:
Build Identifier:

When installing `docker-compose` at 04.03.2020 from default opensuse 15.1
repos, getting the message
Problem: docker-compose-1.17.0-lp151.3.2.noarch conflicts with python-PyYAML >=
4 provided by python2-PyYAML-5.1.2-lp151.2.3.1.x86_64

Reproducible: Always

Steps to Reproduce:
1. Run sudo zypper install docker-compose
Actual Results:
Dependency conflict

Expected Results:
docker-compose installed

summary: docker-compose conflicting with  python-PyAML


--1583423531.fBeAe0.12657
Date: Thu, 5 Mar 2020 15:52:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165826

            Bug ID: 1165826
           Summary: VUL-0: CVE-2020-6420: chromium: multiple security issues fixed in 80.0.3987.132
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Security
          Assignee: tchvatal-at-suse.com
          Reporter: wolfgang.frisch-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The Chromium stable channel was updated to version 80.0.3987.132 [1].

It contains 4 security fixes:

* CVE-2020-6420: Insufficient policy enforcement in media.
* Various fixes from internal audits, fuzzing and other initiatives [2].

[1]
https://chromereleases.googleblog.com/2020/03/stable-channel-update-for-desktop.html
[2] https://crbug.com/1057473


body:
--1583427818.5b4fD4.10043
Date: Thu, 5 Mar 2020 17:03:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165837

            Bug ID: 1165837
           Summary: mtools requires glibc-locale
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: pgajdos-at-suse.com
          Reporter: lnussel-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: meissner-at-suse.com
            Blocks: 1165830
          Found By: ---
           Blocker: ---

mtools requires glibc-locale which is quite big. Does that make sense?
Maybe it needs glibc-locale-base instead for the libs in there?

summary: mtools requires glibc-locale


--1583484766.dBeDd0.32337
Date: Fri, 6 Mar 2020 08:52:46 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1165894

            Bug ID: 1165894
           Summary: Python3 conflicts with python2 on idle subpkg
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: mcepl-at-suse.com
          Reporter: tchvatal-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

found conflict of python-idle-2.7.17-lp152.9.1.x86_64 with
python3-idle-3.6.10-lp152.1.1.x86_64
  /usr/share/icons/hicolor/16x16/apps/idle.png
  /usr/share/icons/hicolor/32x32/apps/idle.png
  /usr/share/icons/hicolor/48x48/apps/idle.png


--1583588474.2F616ce73.31160
Date: Sat, 7 Mar 2020 13:41:14 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165975

            Bug ID: 1165975
           Summary: amd64_edac_mod does not load after CPU upgrade
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: seroton10-at-gmail.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

On a server with an AMD Ryzen 7 2700X CPU, I use the following output, written
during boot, to verify that DRAM ECC is enabled:

Mar 04 23:31:58 blackbox kernel: smpboot: CPU0: AMD Ryzen 7 2700X Eight-Core
Processor (family: 0x17, model: 0x8, stepping: 0x2)
[cut]
Mar 04 23:31:58 blackbox kernel: EDAC MC: Ver: 3.0.0
[cut]
Mar 04 23:32:06 blackbox kernel: EDAC amd64: Node 0: DRAM ECC enabled.
Mar 04 23:32:06 blackbox kernel: EDAC amd64: F17h detected (node 0).
Mar 04 23:32:06 blackbox kernel: EDAC MC: UMC0 chip selects:
Mar 04 23:32:06 blackbox kernel: EDAC amd64: MC: 0:  8192MB 1:  8192MB
Mar 04 23:32:06 blackbox kernel: EDAC amd64: MC: 2:  8192MB 3:  8192MB
Mar 04 23:32:06 blackbox kernel: EDAC MC: UMC1 chip selects:
Mar 04 23:32:06 blackbox kernel: EDAC amd64: MC: 0:  8192MB 1:  8192MB
Mar 04 23:32:06 blackbox kernel: EDAC amd64: MC: 2:  8192MB 3:  8192MB
Mar 04 23:32:06 blackbox kernel: EDAC amd64: using x8 syndromes.
Mar 04 23:32:06 blackbox kernel: EDAC amd64: MCT channel count: 2
Mar 04 23:32:06 blackbox kernel: EDAC MC0: Giving out device to module
amd64_edac controller F17h: DEV 0000:00:18.3 (INTERRUPT)
Mar 04 23:32:06 blackbox kernel: EDAC PCI0: Giving out device to module
amd64_edac controller EDAC PCI controller: DEV 0000:00:18.0 (POLLED)
Mar 04 23:32:06 blackbox kernel: AMD64 EDAC driver v3.5.0

After upgrading the CPU to an AMD Ryzen 9 3900X (no other hardware or software
changes were made), I only see the first line mentioning EDAC in the log:

Mar 07 13:44:12 blackbox kernel: smpboot: CPU0: AMD Ryzen 9 3900X 12-Core
Processor (family: 0x17, model: 0x71, stepping: 0x0)
[cut]
Mar 07 13:44:12 blackbox kernel: EDAC MC: Ver: 3.0.0

An attempt to manually load the AMD EDAC driver fails:

# modprobe amd64_edac_mod
modprobe: ERROR: could not insert 'amd64_edac_mod': No such device

Would it be possible to add or backport the missing hardware support in the
Leap 15.1 kernel?


body:
--1583592811.7dcf04.22889
Date: Sat, 7 Mar 2020 14:53:31 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165976

            Bug ID: 1165976
           Summary: [trackerbug] lxd 3.22 update
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Containers
          Assignee: containers-bugowner-at-suse.de
          Reporter: asarai-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

- Update to LXD 3.22. The full upstream changelog is available from:
  https://discuss.linuxcontainers.org/t/lxd-3-22-has-been-released/7027
  + Resource limits for projects
  + nftables backend for firewalling
  + Container: Hugepages in unprivileged containers
  + VM: Support for 9p disk devices
  + VM: File templating support

summary: [trackerbug] lxd 3.22 update


--1583655150.0aa5B3.20010
Date: Sun, 8 Mar 2020 08:12:30 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1165987

            Bug ID: 1165987
           Summary: The sddm user has no permissions on Nvidia based X servers
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: x86-64
                OS: SUSE Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: KDE Workspace (Plasma)
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: werner-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: fabian@ritter-vogt.de, fvogt-at-suse.com,
                    sndirsch-at-suse.com
        Depends on: 1151290
          Found By: ---
           Blocker: ---

The sddm user has no permissions on Nvidia based X servers whicb results in a
black X11 screen and an abort() of the sddm-helper program

Simple solution is to add the user sddm to the group video


--1583697343.bBA082f0.8836
Date: Sun, 8 Mar 2020 19:55:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166007

            Bug ID: 1166007
           Summary: dovecot -> master: Fatal: execv(/usr/lib/dovecot/script-login) failed: Permission denied
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: AppArmor
          Assignee: suse-beta-at-cboltz.de
          Reporter: opensuse-at-mike.franken.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Dovecot is up and running, but after activating post-login scripting according
to https://wiki2.dovecot.org/PostLoginScripting I get several errors from
dovecot:

---------------------------------------------------------------------------
dovecot[17836]: master: Fatal: execv(/usr/lib/dovecot/script-login) failed:
Permission denied
dovecot[17833]: master: Error: service(imap-postlogin): command startup failed,
throttling for 60 secs
dovecot[17836]: imap-postlogin: Fatal: master: service(imap-postlogin): child
18460 returned error 84 (exec() failed)
dovecot[17836]: imap(<username>): Error: fd_read(/run/dovecot/imap-postlogin)
failed: Connection reset by peer (connection created 59893 msecs ago, client
created 59893 msecs ago: session=92VFKV2gysPAqAE+, rip=192.168.1.62,
auth_pid=17850, client-pid=17992, client-id=1, post-login script
/run/dovecot/imap-postlogin started 59892 msecs ago)
dovecot[17836]: imap(<username>): Error: fd_read(/run/dovecot/imap-postlogin)
failed: Connection reset by peer (connection created 29586 msecs ago, client
created 29586 msecs ago: session=r9UTK12gVMTAqAE+, rip=192.168.1.62,
auth_pid=17850, client-pid=18377, client-id=1, post-login script
/run/dovecot/imap-postlogin started 29585 msecs ago)
---------------------------------------------------------------------------

Excerpt from my audit.log:

type=AVC msg=audit(1583697228.382:38487): apparmor="DENIED" operation="exec"
profile="dovecot" name="/usr/lib/dovecot/script-login" pid=19176 comm="dovecot"
requested_mask="x" denied_mask="x" fsuid=0 ouid=0

After having deactivated apparmor, dovecot runs without spitting error
messages.
This is, what I added to /etc/dovecot/conf.d/10-master.conf:

service imap {
  executable = imap imap-postlogin
}
service imap-postlogin {
  executable = script-login /usr/local/bin/dovecot-postlogin.sh
  user = $default_internal_user
  unix_listener imap-postlogin {
  }
}


--1583750808.0CDA0Ce4.6690
Date: Mon, 9 Mar 2020 10:46:48 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1166067

            Bug ID: 1166067
           Summary: nfs-utils hack to avoid python dependency does not work anymore
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: nfbrown-at-suse.com
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: lnussel-at-suse.com
          Found By: ---
           Blocker: ---

nfs-utils has the following code:
# hack to avoid automatic python dependency
chmod 644 %{buildroot}%{_sbindir}/{mountstats,nfsiostat}

This does not seem to work anymore.


--1583773416.aEa30.23118
Date: Mon, 9 Mar 2020 17:03:36 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166114

            Bug ID: 1166114
           Summary: security:netfilter/shorewall: Bug non-major, point/dot release `zypper up` incorrectly stops/blocks running shorewall svc
    Classification: openSUSE
           Product: openSUSE.org
           Version: unspecified
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: 3rd party software
          Assignee: toganm-at-dinamizm.com
          Reporter: pgnet.dev-at-gmail.com
        QA Contact: bnc-team-screening-at-forge.provo.novell.com
                CC: bruno@ioda-net.ch
          Found By: ---
           Blocker: ---

on

    lsb_release -rd
        Description:    openSUSE Leap 15.1
        Release:        15.1

with

    uname -rm
        5.5.8-24.gfb4c60d-default x86_64

    rpm -qa | grep -i "iptables"
        iptables-1.8.4-172.5.x86_64

I install shorewall pkgs from opensuse distro security:netfilter, tracking
regular updates.

currently installed are

    shorewall-5.2.3.6-237.5.noarch
    shorewall6-lite-5.2.3.6-237.5.noarch
    shorewall-core-5.2.3.6-237.5.noarch
    shorewall-init-5.2.3.6-237.5.noarch
    shorewall-lite-5.2.3.6-237.5.noarch

on each/every 'zypper' update that picks up even a NON-major update


--1583787420.44DB3b0.27473
Date: Mon, 9 Mar 2020 20:57:00 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1166139

            Bug ID: 1166139
           Summary: build of six without setuptools leads to pip issues
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: dmueller-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

pip 10.x requires eggs to be build via setuptools, otherwise uninstalling  a
package leads to:

ERROR: Cannot uninstall 'six'. It is a distutils installed project and thus we
cannot accurately determine which files belong to it which would lead to only a
partial uninstall


--1583870471.8fEe6c0f3.15820
Date: Tue, 10 Mar 2020 20:01:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1166288

            Bug ID: 1166288
           Summary: Enable  vte in remote-viewer build to support multiple spice displays (eg: qemu-kvm -display spice-app)
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: brogers-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

As of qemu v4.0, a simple interface for doing spice U/I has been enabled via
the qemu command line option: qemu-kvm -display spice-app.

When using spice in this way, remote-viewer has (in this simple default config)
3 displays, the main graphical display, plus a display window for serial I/O,
as well as another for the human monitor. This mirrors what is also available
for SDL and GTK based U/I.

Unfortunately, when selecting the display for either the serial or Human
Monitor, the window that pops up indicates that Console support is compiled
out. It would be helpful to have access to the momitor and serial screens under
spice, just as it has been for SDL and GTK over these years that it's been
enabled there.

I've found that simply adding a BuildRequires: vte-devel to the virt-viewer
spec file is all that is needed to get this support included in remote-viewer.


body:
--1583909533.bE11410.24935
Date: Wed, 11 Mar 2020 06:52:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166317

            Bug ID: 1166317
           Summary: kaffeine cannot save keyboard shortcuts
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: KDE Applications
          Assignee: opensuse-kde-bugs-at-opensuse.org
          Reporter: dieter.jurzitza@t-online.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The distributed kaffeine (kaffeine-2.0.17-lp151.1.1.x86_64.rpm) is not able to
store modifications of the shortkeys. After modifying a readily assigned
shortkey (say arrow right from 15s forward to next channel) and pressing the
arrow right key twice or three times the old setting is restored and kept for
no good reason.
Switching to the version 18 as distributed with tumbleweed solves this issue.
Please provide an update for the leap distribution as well.
Thank you
take care

Dieter Jurzitza

summary: kaffeine cannot save keyboard shortcuts


body:
--1583942979.38883Cc00.11435
Date: Wed, 11 Mar 2020 16:09:39 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1166404

            Bug ID: 1166404
           Summary: Pan not able to post to any newsgroups
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X11 Applications
          Assignee: screening-team-bugs-at-suse.de
          Reporter: jason.evans-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 832569
  --> http://bugzilla.suse.com/attachment.cgi?id=832569&action=edit
screenshot

Pan version 0.146-1.1

When trying to post to any newsgroup, it fails with the error:

Error: Bad email address

I have confirmed that the email address is in a good format.

Screenshot attached.

summary: Pan not able to post to any newsgroups


body:
--1583968125.61260eA0.15276
Date: Wed, 11 Mar 2020 23:08:45 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166426

            Bug ID: 1166426
           Summary: /usr/bin/eclipse crashes on first start
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: lubos.kocman-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Eclipse on latest Leap 15.2 crashes right at the start (first and second
attempt right after installation).

Outcome: Popup dialog points me to the logfile containing crash data.

lkocman@linux:~> rpm -qa | grep eclipse
eclipse-pde-4.9.0-lp152.1.12.x86_64
eclipse-ecf-core-3.14.1-lp152.1.10.x86_64
eclipse-swt-4.9.0-lp152.1.12.x86_64
eclipse-jdt-4.9.0-lp152.1.12.noarch
eclipse-emf-core-2.15.0~gitd1e5fdd-lp152.1.10.x86_64
eclipse-platform-4.9.0-lp152.1.12.x86_64
eclipse-equinox-osgi-4.9.0-lp152.1.12.x86_64
lkocman@linux:~>

lkocman@linux:~> cat
~/.eclipse/org.eclipse.platform_793567567_linux_gtk_x86_64/configuration/1583967877560.log
!SESSION 2020-03-12 00:04:37.401
-----------------------------------------------
eclipse.buildId=4.9.0.v20191115-1709
java.version=11.0.6
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments:  -os linux -ws gtk -arch x86_64

!ENTRY org.eclipse.equinox.simpleconfigurator 4 0 2020-03-12 00:04:37.807
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Exception in
org.eclipse.equinox.internal.simpleconfigurator.Activator.start() of bundle
org.eclipse.equinox.simpleconfigurator.
    at
org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:803)
    at
org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:732)
    at
org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1005)
    at
org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:357)
    at org.eclipse.osgi.container.Module.doStart(Module.java:584)
    at org.eclipse.osgi.container.Module.start(Module.java:452)
    at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1685)
    at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1665)
    at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1627)
    at
org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:267)
    at org.eclipse.osgi.container.Module.doStart(Module.java:584)
    at org.eclipse.osgi.container.Module.start(Module.java:452)
    at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:191)
    at
org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:431)
    at
org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:450)
    at org.eclipse.osgi.launch.Equinox.start(Equinox.java:118)
    at
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:329)
    at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:242)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
    at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1474)
Caused by: java.lang.IllegalStateException: The System Bundle was updated. The
framework must be restarted to finalize the configuration change
    at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:84)
    at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:189)
    at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:204)
    at
org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:64)
    at
org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:782)
    at
org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
    at java.base/java.security.AccessController.doPrivileged(Native Method)
    at
org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:775)
    ... 25 more
Root exception:
java.lang.IllegalStateException: The System Bundle was updated. The framework
must be restarted to finalize the configuration change
    at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:84)
    at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:189)
    at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:204)
    at
org.eclipse.equinox.internal.simpleconfigurator.Activator.start(Activator.java:64)
    at
org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:782)
    at
org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
    at java.base/java.security.AccessController.doPrivileged(Native Method)
    at
org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:775)
    at
org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:732)
    at
org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:1005)
    at
org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:357)
    at org.eclipse.osgi.container.Module.doStart(Module.java:584)
    at org.eclipse.osgi.container.Module.start(Module.java:452)
    at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1685)
    at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1665)
    at
org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1627)
    at
org.eclipse.osgi.container.SystemModule.startWorker(SystemModule.java:267)
    at org.eclipse.osgi.container.Module.doStart(Module.java:584)
    at org.eclipse.osgi.container.Module.start(Module.java:452)
    at org.eclipse.osgi.container.SystemModule.start(SystemModule.java:191)
    at
org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:431)
    at
org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:450)
    at org.eclipse.osgi.launch.Equinox.start(Equinox.java:118)
    at
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:329)
    at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:242)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
    at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1474)

!ENTRY org.eclipse.osgi 4 0 2020-03-12 00:04:37.809
!MESSAGE Bundle org.eclipse.equinox.simpleconfigurator_1.3.100.v20191115-1709
[2] is not active.

!ENTRY org.eclipse.osgi 4 0 2020-03-12 00:04:37.811
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure
that the org.eclipse.core.runtime bundle is resolved and started (see
config.ini).
    at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:81)
    at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:391)
    at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:246)
    at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
    at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.base/java.lang.reflect.Method.invoke(Method.java:566)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1501)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1474)

pkgs: eclipse eclipse-ecf eclipse-emf

summary: /usr/bin/eclipse crashes on first start


body:
--1584006792.4Af3dad11.27847
Date: Thu, 12 Mar 2020 09:53:12 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1166467

            Bug ID: 1166467
           Summary: taglib fails to build in Leap
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mlin-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

taglib FTBFS due to fails to pass brp-35-rpath[1]

[   83s] calling /usr/lib/rpm/brp-suse.d/brp-35-rpath
[   83s] ERROR: RPATH "/home/abuild/rpmbuild/BUILD/taglib-1.11.1/build/taglib"
on
/home/abuild/rpmbuild/BUILDROOT/taglib-1.11.1-lp152.8.7.x86_64/usr/bin/framelist
is not allowed
[   83s] ERROR: RPATH
"/home/abuild/rpmbuild/BUILD/taglib-1.11.1/build/bindings/c" on
/home/abuild/rpmbuild/BUILDROOT/taglib-1.11.1-lp152.8.7.x86_64/usr/bin/tagreader_c
is not allowed
[   83s] ERROR: RPATH "/home/abuild/rpmbuild/BUILD/taglib-1.11.1/build/taglib"
on
/home/abuild/rpmbuild/BUILDROOT/taglib-1.11.1-lp152.8.7.x86_64/usr/bin/tagreader_c
is not allowed
[   83s] ERROR: RPATH "/home/abuild/rpmbuild/BUILD/taglib-1.11.1/build/taglib"
on
/home/abuild/rpmbuild/BUILDROOT/taglib-1.11.1-lp152.8.7.x86_64/usr/bin/strip-id3v1
is not allowed
[   83s] ERROR: RPATH "/home/abuild/rpmbuild/BUILD/taglib-1.11.1/build/taglib"
on
/home/abuild/rpmbuild/BUILDROOT/taglib-1.11.1-lp152.8.7.x86_64/usr/bin/tagwriter
is not allowed
[   83s] ERROR: RPATH "/home/abuild/rpmbuild/BUILD/taglib-1.11.1/build/taglib"
on
/home/abuild/rpmbuild/BUILDROOT/taglib-1.11.1-lp152.8.7.x86_64/usr/bin/tagreader
is not allowed
[   83s] error: Bad exit status from /var/tmp/rpm-tmp.B2qkVe (%install)

[1]
https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.2:Staging:A/taglib/standard/x86_64

summary: taglib fails to build in Leap


body:
--1584021757.E58830AE0.4422
Date: Thu, 12 Mar 2020 14:02:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166503

            Bug ID: 1166503
           Summary: libzbc fails with -fno-common
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: martin.liska-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

The package fails here:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:M/libzbc/standard/x86_64

Please take a look at the META issue for the instructions.

summary: libzbc fails with -fno-common


--1584047651.b555ee185.32110
Date: Thu, 12 Mar 2020 21:14:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166537

            Bug ID: 1166537
           Summary: osc rq accept - forwarding request causes backtrace
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: marco.strigl-at-suse.com
          Reporter: suse-beta-at-cboltz.de
        QA Contact: qa-bugs-at-suse.de
                CC: suse-tux-at-gmx.de
          Found By: ---
           Blocker: ---

When accepting a SR to a devel project, osc asks if I want to forward the SR to
Factory. I answered "y", but got this nice backtrace instead of a SR to
Factory:

# osc rq accept 784420
Result of change request state: ok
openSUSE:Factory
Forward this submit to it? ([y]/n)y
Traceback (most recent call last):
  File "/usr/bin/osc", line 41, in <module>
    r = babysitter.run(osccli)
  File "/usr/lib/python3.8/site-packages/osc/babysitter.py", line 64, in run
    return prg.main(argv)
  File "/usr/lib/python3.8/site-packages/osc/cmdln.py", line 344, in main
    return self.cmd(args)
  File "/usr/lib/python3.8/site-packages/osc/cmdln.py", line 367, in cmd
    retval = self.onecmd(argv)
  File "/usr/lib/python3.8/site-packages/osc/cmdln.py", line 501, in onecmd
    return self._dispatch_cmd(handler, argv)
  File "/usr/lib/python3.8/site-packages/osc/cmdln.py", line 1232, in
_dispatch_cmd
    return handler(argv[0], opts, *args)
  File "/usr/lib/python3.8/site-packages/osc/commandline.py", line 2652, in
do_request
    project, package, html.escape(msg, quote=False))
NameError: name 'html' is not defined

Wild guess: missing "import html"?

Note: commandline.py has an "import html" in do_submitrequest(), but this
import isn't visible to do_request(). Also note that there are more functions
in this file that call html.escape() without importing html before and will
probably break in a similar way. Doing the "import html" in the file header
instead of inside the functions might be a good idea.


body:
--1584104434.EAed18740.2754
Date: Fri, 13 Mar 2020 13:00:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166605

            Bug ID: 1166605
           Summary: GCC 10: syslinux build fails
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: martin.liska-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Fails here:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:Gcc7/syslinux/standard/x86_64

with:

[  129s] ld: libmenu/libmenu.a(tui.o):(.bss+0x0): multiple definition of
`outreg'; libmenu/libmenu.a(syslnx.o):(.bss+0x0): first defined here
[  129s] ld: libmenu/libmenu.a(tui.o):(.bss+0x40): multiple definition of
`inreg'; libmenu/libmenu.a(syslnx.o):(.bss+0x40): first defined here
[  129s] ld: libmenu/libmenu.a(menu.o):(.bss+0x8): multiple definition of
`ACTION_VALID'; complex.o:(.bss+0x164): first defined here
[  129s] ld: libmenu/libmenu.a(menu.o):(.bss+0x4): multiple definition of
`ACTION_INVALID'; complex.o:(.bss+0x160): first defined here
[  129s] ld: libmenu/libmenu.a(help.o):(.bss+0x48): multiple definition of
`ACTION_INVALID'; complex.o:(.bss+0x160): first defined here
[  129s] ld: libmenu/libmenu.a(help.o):(.bss+0x4c): multiple definition of
`ACTION_VALID'; complex.o:(.bss+0x164): first defined here
[  129s] ld: libmenu/libmenu.a(com32io.o):(.bss+0x40): multiple definition of
`inreg'; libmenu/libmenu.a(syslnx.o):(.bss+0x40): first defined here
[  129s] ld: libmenu/libmenu.a(com32io.o):(.bss+0x0): multiple definition of
`outreg'; libmenu/libmenu.a(syslnx.o):(.bss+0x0): first defined here
[  129s] make[2]: *** [../MCONFIG:82: complex.elf] Error 1
[  129s] make[2]: Leaving directory
'/home/abuild/rpmbuild/BUILD/syslinux-4.04/com32/cmenu'

summary: GCC 10: syslinux build fails


--1584109597.fcEcbF5.5589
Date: Fri, 13 Mar 2020 14:26:37 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166623

            Bug ID: 1166623
           Summary: hplip with python 3.8 requires python3-distro.
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Printing
          Assignee: jsmeix-at-suse.com
          Reporter: conde.philippe-at-skynet.be
        QA Contact: jsmeix-at-suse.com
          Found By: ---
           Blocker: ---

hello,

I received this error when starting hp (command hp-toolbox).
hp-toolbox

HP Linux Imaging and Printing System (ver. 3.19.12)
HP Device Manager ver. 15.0

Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Traceback (most recent call last):
  File "/usr/share/hplip/base/password.py", line 85, in get_distro_name
    os_name = platform.dist()[0]
AttributeError: module 'platform' has no attribute 'dist'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/hp-toolbox", line 280, in <module>
    toolbox = ui.DevMgr5(__version__, device_uri,  None)
  File "/usr/share/hplip/ui5/devmgr5.py", line 235, in __init__
    core =  CoreInstall(MODE_CHECK)
  File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
    self.passwordObj = password.Password(ui_mode)
  File "/usr/share/hplip/base/password.py", line 118, in __init__
    self.__readAuthType()  # self.__authType
  File "/usr/share/hplip/base/password.py", line 140, in __readAuthType
    distro_name = get_distro_name().lower()
  File "/usr/share/hplip/base/password.py", line 87, in get_distro_name
    import distro
ModuleNotFoundError: No module named 'distro'

I addded python3-distro and this solves the problem; This package must be
required by installation op hplip.

Regards


--1584114685.b1c6cf13.13209
Date: Fri, 13 Mar 2020 15:51:25 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166632

            Bug ID: 1166632
           Summary: AC 3168NGW WLAN controller inactive after upgrade of Kernel to 28-40 on 13-03-2020
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: x86-64
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Kernel
          Assignee: kernel-maintainers-at-forge.provo.novell.com
          Reporter: j.r.hudson-at-virginmedia.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After upgrade to kernel 28.40 on 13-03-2020 AC 3168NGW WLAN driver no longer
works; it works if previous kernel 28.36 is used instead.
The problem does not occur with ath10k_pci on another device.


--1584172033.aF160.22630
Date: Sat, 14 Mar 2020 07:47:13 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1166667

            Bug ID: 1166667
           Summary: Relinking to absolute path creates warning about absolute path
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: kukuk-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

We have scipts which create absolute links from relative links:
[    4s] INFO: relinking /bin/arch -> /usr/bin/busybox (was ../usr/bin/busybox)
[    4s] INFO: relinking /bin/ash -> /usr/bin/busybox (was ../usr/bin/busybox)
[    4s] INFO: relinking /bin/base64 -> /usr/bin/busybox (was
../usr/bin/busybox)

Afterwards we warn because there are absolute links:
[    5s] warning: absolute symlink: /bin/arch -> /usr/bin/busybox
[    5s] warning: absolute symlink: /bin/ash -> /usr/bin/busybox
[    5s] warning: absolute symlink: /bin/base64 -> /usr/bin/busybox

Either we want absolute links, then we should not warn about them. Or we don't
want absolute links,then we should not replace relative links with absolute
links.


--1584180729.217B20.28494
Date: Sat, 14 Mar 2020 10:12:09 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166669

            Bug ID: 1166669
           Summary: susepaste command from openSUSE shell logins is failing with "Paste failed :-("
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
               URL: https://progress.opensuse.org/issues/56189
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mrmazda-at-earthlink.net
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Initial Summary:
susepaste command from openSUSE shell logins is failing with "Paste failed :-("

To reproduce:
1-login to shell or xterm or konsole or or or or...
2-susepaste -n mynick -e 10080 /var/log/Xorg.0.log

Actual results:
1-paste quickly appears on https://paste.opensuse.org/lists
2-shell reports "Paste failed :-("

Expected results:
1-paste quickly appears on https://paste.opensuse.org/lists
2-shell reports the URL of the successful paste

Notes:
1-https://lists.opensuse.org/opensuse/2020-01/msg00429.html has an ostensibly
fixed script.
2-https://progress.opensuse.org/issues/56189 was reported in August.
3-Issues began last June:
https://lists.opensuse.org/opensuse/2019-06/msg00050.html
4-September thread reporting failure:
https://lists.opensuse.org/opensuse/2019-09/msg00350.html
5-This creates obstacle for helping people reporting trouble in the forums


body:
--1584403326.DdBf6.8825
Date: Tue, 17 Mar 2020 00:02:06 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166820

            Bug ID: 1166820
           Summary: geany causes coredump on quit
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: x86-64
                OS: openSUSE Factory
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: GNOME
          Assignee: gnome-bugs-at-suse.de
          Reporter: mail@bernhard-voelker.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Since a longer time, I'm seeing ~400M 'core' files in various directories
on my oS:TW systems, so I though I'd better report it.

Simple reproducer:
- boot,
- login to openbox window manager,
- start a 'gnome-terminal',
- run 'geany somefile' (or with '&' to set it into background, no matter),
- wait until geany has come up,
- close geany via the 'X' of the window manager,
  or via menu 'File -> Quit' (doesn't matter which).
--> Segmentation fault (core dumped)

Backtrace:

gdb /usr/bin/geany core
/usr/share/gdb/python/gdb/command/prompt.py:48: SyntaxWarning: "is not" with a
literal. Did you mean "!="?
  if self.value is not '':
/usr/share/gdb/python/gdb/command/prompt.py:60: SyntaxWarning: "is not" with a
literal. Did you mean "!="?
  if self.value is not '':
GNU gdb (GDB; openSUSE Tumbleweed) 8.3.1
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-suse-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.opensuse.org/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/geany...
Reading symbols from /usr/lib/debug/usr/bin/geany-1.36-2.1.x86_64.debug...
[New LWP 5507]
[New LWP 5514]
[New LWP 5513]
[New LWP 5523]
[New LWP 5522]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `geany debugsource'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f6f9d4d9722 in vte_start (widget=0x56253b412180) at vte.c:497
497                if (! vf->vte_terminal_spawn_sync(VTE_TERMINAL(widget),
VTE_PTY_DEFAULT,
[Current thread is 1 (Thread 0x7f6f9b533140 (LWP 5507))]
(gdb) bt
#0  0x00007f6f9d4d9722 in vte_start (widget=0x56253b412180) at vte.c:497
#1  0x00007f6f9c72531e in g_cclosure_marshal_VOID__BOOLEANv (closure=<optimized
out>, return_value=<optimized out>, instance=<optimized out>, args=<optimized
out>, marshal_data=<optimized out>, n_params=<optimized out>,
param_types=0x56253b4085c0)
    at ../gobject/gmarshal.c:272
#2  0x00007f6f9c7230e6 in _g_closure_invoke_va (closure=0x56253b4833f0,
return_value=0x0, instance=0x56253b412180, args=0x7ffef715f070, n_params=1,
param_types=0x56253b4085c0) at ../gobject/gclosure.c:873
#3  0x00007f6f9c73f428 in g_signal_emit_valist (instance=0x56253b412180,
signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7ffef715f070) at
../gobject/gsignal.c:3306
#4  0x00007f6f9c73fbcf in g_signal_emit (instance=<optimized out>,
signal_id=<optimized out>, detail=detail@entry=0) at ../gobject/gsignal.c:3453
#5  0x00007f6f98c98f07 in vte::platform::Widget::emit_child_exited (status=9,
this=0x56253b412020) at ../src/widget.hh:47
#6  vte::platform::Widget::dispose (this=0x56253b412020) at
../src/widget.cc:135
#7  vte::platform::Widget::dispose (this=0x56253b412020) at
../src/widget.cc:131
#8  vte_terminal_dispose (object=0x56253b412180) at ../src/vtegtk.cc:412
#9  0x00007f6f9c729a4e in g_object_run_dispose (object=0x56253b412180) at
../gobject/gobject.c:1130
#10 0x00007f6f9ccfe729 in gtk_widget_destroy (widget=<optimized out>) at
gtkwidget.c:4776
#11 0x00007f6f9d5016eb in vte_close () at vte.c:402
#12 do_main_quit () at libmain.c:1353
#13 do_main_quit () at libmain.c:1274
#14 0x00007f6f9d503558 in main_quit () at libmain.c:1415
#15 0x00007f6f9d537e69 in on_window_delete_event
(widget=widget@entry=0x56253aed0510, event=event@entry=0x56253b099710,
gdata=<optimized out>) at callbacks.c:85
#16 0x00007f6f9ccb6a5b in _gtk_marshal_BOOLEAN__BOXEDv (closure=0x56253adaf8b0,
return_value=0x7ffef715f380, instance=<optimized out>, args=<optimized out>,
marshal_data=<optimized out>, n_params=<optimized out>,
param_types=0x56253aa5ec90) at gtkmarshalers.c:129
#17 0x00007f6f9c7230e6 in _g_closure_invoke_va (closure=0x56253adaf8b0,
return_value=0x7ffef715f380, instance=0x56253aed0510, args=0x7ffef715f450,
n_params=1, param_types=0x56253aa5ec90) at ../gobject/gclosure.c:873
#18 0x00007f6f9c73f06a in g_signal_emit_valist (instance=0x56253aed0510,
signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7ffef715f450) at
../gobject/gsignal.c:3306
#19 0x00007f6f9c73fbcf in g_signal_emit
(instance=instance@entry=0x56253aed0510, signal_id=<optimized out>,
detail=detail@entry=0) at ../gobject/gsignal.c:3453
#20 0x00007f6f9cd01c62 in gtk_widget_event_internal (event=0x56253b099710,
widget=0x56253aed0510) at gtkwidget.c:7808
#21 gtk_widget_event_internal (widget=0x56253aed0510, event=0x56253b099710) at
gtkwidget.c:7677
#22 0x00007f6f9ce42149 in gtk_main_do_event (event=0x56253b099710) at
gtkmain.c:1818
#23 gtk_main_do_event (event=<optimized out>) at gtkmain.c:1687
#24 0x00007f6f9cbaf6e4 in _gdk_event_emit (event=0x56253b099710) at
gdkevents.c:73
#25 _gdk_event_emit (event=0x56253b099710) at gdkevents.c:67
#26 0x00007f6f9cb7e1f2 in gdk_event_source_dispatch
(source=source@entry=0x56253a99b1c0, callback=<optimized out>,
user_data=<optimized out>) at gdkeventsource.c:367
#27 0x00007f6f9c633008 in g_main_dispatch (context=0x56253a99b2b0) at
../glib/gmain.c:3216
#28 g_main_context_dispatch (context=context@entry=0x56253a99b2b0) at
../glib/gmain.c:3881
#29 0x00007f6f9c633390 in g_main_context_iterate (context=0x56253a99b2b0,
block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at
../glib/gmain.c:3954
#30 0x00007f6f9c633663 in g_main_loop_run (loop=0x56253f429830) at
../glib/gmain.c:4148
#31 0x00007f6f9ce3bd75 in gtk_main () at gtkmain.c:1325
#32 0x00007f6f9d510104 in main_lib (argc=<optimized out>, argv=<optimized out>)
at libmain.c:1259
#33 0x00007f6f9d5f7ceb in __libc_start_main (main=0x5625392e7050 <main>,
argc=2, argv=0x7ffef715fa08, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7ffef715f9f8) at ../csu/libc-start.c:308
#34 0x00005625392e708a in _start () at ../sysdeps/x86_64/start.S:120

Let me know if you need more information.
Thanks.

summary: geany causes coredump on quit


--1584406151.CD540.24268
Date: Tue, 17 Mar 2020 00:49:11 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1166821

            Bug ID: 1166821
           Summary: psqlODBC fails to build with postgresql12 in Leap 15.2
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mlin-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

After default postgresql moved to postgresql12, psqlODBC fails to build with
postresql12, full build log
https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.2/psqlODBC/standard/x86_64


--1584525874.334b3.20498
Date: Wed, 18 Mar 2020 10:04:34 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1166948

            Bug ID: 1166948
           Summary: util-linux causes rpm verification errors
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Basesystem
          Assignee: sbrabec-at-suse.com
          Reporter: fvogt-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: dmueller-at-suse.com, meissner-at-suse.com
          Found By: ---
           Blocker: ---

After doing a plain default install, rpm -qV util-linux complains about:

# rpm -qV util-linux
.M.......    /usr/bin/mount
.M.......    /usr/bin/su
.M.......    /usr/bin/umount

It seems like those files are missing %verify(not mode).


body:
--1584532972.C4ef8e5.19222
Date: Wed, 18 Mar 2020 12:02:52 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1166965

            Bug ID: 1166965
           Summary: kernel-docs fail to build occasionally with python 3.8
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: jslaby-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: mkubecek-at-suse.com
        Depends on: 1158289
          Found By: ---
           Blocker: ---

kernel-docs need 8.2G of memory with python 3.8 now. It used to be 2.2G on
SLE15-SP2 (python 3.6). I don't have numbers for 3.7, but the build did not
fail in factory, now it fails quite often.

> [  776s] writing output... [ 55%] media/uapi/dvb/audio-continue .. media/uapi/dvb/frontend-property-terrestrial-systems
> [  783s] [  768.244238] Out of memory: Killed process 4174 (sphinx-build) total-vm:1256996kB, anon-rss:517292kB, file-rss:0kB, shmem-rss:0kB, UID:399 pgtables:2508kB oom_score_adj:0
> [  842s] writing output... [ 59%] media/uapi/dvb/frontend-stat-properties .. media/uapi/rc/lirc-set-wideband-receiver
> [  847s]
> [  847s] Exception occurred:
> [  847s]   File "/usr/lib64/python3.8/multiprocessing/connection.py", line 383, in _recv
> [  847s]     raise EOFError
> [  847s] EOFError

I indeed can increase the constraints, but 4 times larger memory footprint is
too much... This must be a bug or leak.

https://build.opensuse.org/packages/kernel-docs/job_history/Kernel:stable/standard/x86_64

pkgs: kernel-source python-Sphinx


--1584542187.e02AD5.14376
Date: Wed, 18 Mar 2020 14:36:27 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1166981

            Bug ID: 1166981
           Summary: System settings --> Themes broken in Cinnamon 4.2.3
    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-at-forge.provo.novell.com
          Reporter: timothyadams-at-ymail.com
        QA Contact: xorg-maintainer-bugs-at-forge.provo.novell.com
          Found By: ---
           Blocker: ---

In the Cinnamon desktop, clicking System Settings --> Themes should bring up an
option to change themes, icons and other settings.

This is now broken in Cinnamon 4.2.3 in Tumbleweed.  If I click 'Themes,'
nothing happens.

System Settings --> System Info also isn't functioning.


--1584549230.b0B3D50.21655
Date: Wed, 18 Mar 2020 16:33:50 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1167008

            Bug ID: 1167008
           Summary: libpython3_8-1_0 is missing runtime dependencies on python modules
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Development
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mkoutny-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

I updated gdb from 8.3.1-7.1 to 8.3.1-7.2 + it pulled in libpython3_8-1_0.
After that, gdb won't start with the following dump:

> $ gdb
> Could not find platform independent libraries <prefix>
> Could not find platform dependent libraries <exec_prefix>
> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
> Python path configuration:
>   PYTHONHOME = (not set)
>   PYTHONPATH = (not set)
>   program name = '/usr/bin/python'
>   isolated = 0
>   environment = 1
>   user site = 1
>   import site = 1
>   sys._base_executable = '/usr/bin/python'
>   sys.base_prefix = '/usr'
>   sys.base_exec_prefix = '/usr'
>   sys.executable = '/usr/bin/python'
>   sys.prefix = '/usr'
>   sys.exec_prefix = '/usr'
>   sys.path = [
>     '/usr/lib/python38.zip',
>     '/usr/lib64/python3.8',
>     '/usr/lib/lib-dynload',
>   ]
> Fatal Python error: init_fs_encoding: failed to get the Python codec of the filesystem encoding
> Python runtime state: core initialized
> ModuleNotFoundError: No module named 'encodings'
>
> Current thread 0x00007f17b7380f00 (most recent call first):
> <no Python frame>

It turned out my system was still on python 3.7 and manual upgrade (needed some
deps conflict resolution) to 3.8 fixed this issue.

It looks like the package libpython3_8-1_0 is missing (version) dependency on
python3-base.


--1584553170.D42Bf0.25161
Date: Wed, 18 Mar 2020 17:39:30 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1167013

            Bug ID: 1167013
           Summary: VUL-0: CVE-2020-10592: tor: CPU consumption DoS and timing patterns (TROVE-2020-002)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: bwiedemann-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: security-team-at-suse.de
          Found By: ---
           Blocker: ---

https://lists.torproject.org/pipermail/tor-announce/2020-March/000196.html

  o Major bugfixes (security, denial-of-service, backport from 0.4.3.3-alpha):
    - Fix a denial-of-service bug that could be used by anyone to
      consume a bunch of CPU on any Tor relay or authority, or by
      directories to consume a bunch of CPU on clients or hidden
      services. Because of the potential for CPU consumption to
      introduce observable timing patterns, we are treating this as a
      high-severity security issue. Fixes bug 33119; bugfix on
      0.2.1.5-alpha. Found by OSS-Fuzz. We are also tracking this issue
      as TROVE-2020-002 and CVE-2020-10592.

Fixed in 0.3.5.10, 0.4.1.9, and 0.4.2.7.


--1584553172.1B4fEdDB0.19682
Date: Wed, 18 Mar 2020 17:39:32 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1167014

            Bug ID: 1167014
           Summary: VUL-0: CVE-2020-10593: tor: circuit padding memory leak (TROVE-2020-004)
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Security
          Assignee: bwiedemann-at-suse.com
          Reporter: Andreas.Stieger-at-gmx.de
        QA Contact: security-team-at-suse.de
          Found By: ---
           Blocker: ---

https://lists.torproject.org/pipermail/tor-announce/2020-March/000196.html

  o Major bugfixes (circuit padding, memory leak, backport from 0.4.3.3-alpha):
    - Avoid a remotely triggered memory leak in the case that a circuit
      padding machine is somehow negotiated twice on the same circuit.
      Fixes bug 33619; bugfix on 0.4.0.1-alpha. Found by Tobias Pulls.
      This is also tracked as TROVE-2020-004 and CVE-2020-10593.

Fixed in 0.3.5.10, 0.4.1.9, and 0.4.2.7.


--1584609151.7c1Ad35.21693
Date: Thu, 19 Mar 2020 09:12:31 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1167068

            Bug ID: 1167068
           Summary: /var/lib/mailman/archives/mailman: user mailman can't access
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.1
          Hardware: Other
               URL: https://smash.suse.de/issue/245243/
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: mcepl-at-suse.com
          Reporter: jsegitz-at-suse.com
        QA Contact: qa-bugs-at-suse.de
                CC: jsegitz-at-suse.com, meissner-at-suse.com,
                    tchvatal-at-suse.com, wolfgang.frisch-at-suse.com,
                    wolfgang-at-rosenauer.org
          Found By: ---
           Blocker: ---

+++ This bug was initially created as a clone of Bug #1154328 +++

It seems that after the update on my 15.1 box I get permission errors like
mailman@ds9:~> /usr/bin/python -S /usr/lib/mailman/cron/disabled
Traceback (most recent call last):
  File "/usr/lib/mailman/cron/disabled", line 227, in <module>
    main()
  File "/usr/lib/mailman/cron/disabled", line 220, in main
    mlist.Save()
  File "/usr/lib/mailman/Mailman/MailList.py", line 617, in Save
    self.CheckHTMLArchiveDir()
  File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 241, in
CheckHTMLArchiveDir
    makelink(privdir, pubdir)
  File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 49, in makelink
    os.symlink(old, new)
OSError: [Errno 13] Permission denied

but also for other cron tasks.


--1584630883.0d2d0.14307
Date: Thu, 19 Mar 2020 15:14:43 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1167131

            Bug ID: 1167131
           Summary: virt-v2v fails importing ubuntu 18.04 LTS ova
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: x86-64
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Tools
          Assignee: virt-bugs-at-suse.de
          Reporter: mark-at-marktrompell.de
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

LANG=C virt-v2v -i ova ubuntu.ova -o libvirt -of qcow2 -os gnome-boxes
fails because of ubuntus kernel packaging. See
https://bugzilla.redhat.com/show_bug.cgi?id=1591248

This is fixed with
https://github.com/libguestfs/libguestfs/commit/500acb15f8f777e9fe99a60c4216daf84a92aae3.patch

I added the patch on
https://build.opensuse.org/package/show/home:Mark__T:branches:openSUSE:Leap:15.2/libguestfs


--1584631582.0cAB14.21142
Date: Thu, 19 Mar 2020 15:26:22 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1167132

            Bug ID: 1167132
           Summary: Firefox crashes if you try to authenticate using Kerberos
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Firefox
          Assignee: bnc-team-mozilla-at-forge.provo.novell.com
          Reporter: asn-at-cryptomilk.org
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

As soon as you try to authenticate with a web service using Kerberos, Firefox
segfaults!

MozillaFirefox-73.0.1-2.2.x86_64

Just running in gdb doesn't give any usable result:

(gdb) bt
#0  0x00005555555bb51e in mozalloc_abort(char const*)
(msg=msg@entry=0x5555555cc8d0 "Redirecting call to abort() to
mozalloc_abort\n") at
/usr/src/debug/MozillaFirefox-73.0.1-2.2.x86_64/memory/mozalloc/mozalloc_abort.cpp:33
#1  0x0000555555563ece in abort() () at
/usr/src/debug/MozillaFirefox-73.0.1-2.2.x86_64/memory/mozalloc/mozalloc_abort.cpp:82
#2  0x00007fff9d1846fc in  () at /usr/lib64/libcrypto.so.1.1
#3  0x00007fff9d121ac3 in  () at /usr/lib64/libcrypto.so.1.1
#4  0x00007fff9d0a40e1 in  () at /usr/lib64/libcrypto.so.1.1
#5  0x00007ffff7fe20aa in call_init.part () at /lib64/ld-linux-x86-64.so.2
#6  0x00007ffff7fe21a9 in _dl_init () at /lib64/ld-linux-x86-64.so.2

Frame #2 is OpenSSL_die()

Stack:
[0] from 0x00005555555bb51e in mozalloc_abort+46 at
/usr/src/debug/MozillaFirefox-73.0.1-2.2.x86_64/memory/mozalloc/mozalloc_abort.cpp:33
[1] from 0x0000555555563ece in abort+13 at
/usr/src/debug/MozillaFirefox-73.0.1-2.2.x86_64/memory/mozalloc/mozalloc_abort.cpp:82
[2] from 0x00007fff9d1846fc in OPENSSL_die+28
[3] from 0x00007fff9d121ac3
[4] from 0x00007fff9d0a40e1
[5] from 0x00007ffff7fe20aa in call_init.part
[6] from 0x00007ffff7fe21a9 in _dl_init+121
[7] from 0x00007ffff7f0c91d in _dl_catch_exception+-918323
[8] from 0x00007ffff7fe61f0 in dl_open_worker+1056
[9] from 0x00007ffff7f0c8c0 in _dl_catch_exception+-918416

If you don't have access to any Kerberos infrastructure you can use the one
from Fedora if you have an account:

$ cat /etc/krb5.conf.d/fedoraproject
[realms]
 FEDORAPROJECT.ORG = {
        kdc = https://id.fedoraproject.org/KdcProxy
 }
[domain_realm]
 .fedoraproject.org = FEDORAPROJECT.ORG
 fedoraproject.org = FEDORAPROJECT.ORG

If you have a ticket, e.g. visit https://bodhi.fedoraproject.org/


body:
--1584691958.2cD36a0.28348
Date: Fri, 20 Mar 2020 08:12:38 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.suse.com/show_bug.cgi?id=1167207

            Bug ID: 1167207
           Summary: Build python3-scandir in SLE
    Classification: openSUSE
           Product: openSUSE Distribution
           Version: Leap 15.2
          Hardware: Other
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Other
          Assignee: screening-team-bugs-at-suse.de
          Reporter: mlin-at-suse.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

python-scandir in SLE builds python2 only, since we're aiming to rely on
python3 more than ever, and also some of python modules are looking for
python3-scandir already, we should enable python3 support in python-scandir.

summary: Build python3-scandir in SLE


--1584701456.4D4ad7E0.22309
Date: Fri, 20 Mar 2020 10:50:56 +0000
MIME-Version: 1.0
Content-Type: text/plain

http://bugzilla.opensuse.org/show_bug.cgi?id=1167232

            Bug ID: 1167232
           Summary: Vagrant Tumbleweed 20200317 fails due to unsupported configuration PS2
    Classification: openSUSE
           Product: openSUSE Tumbleweed
           Version: Current
          Hardware: aarch64
                OS: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Virtualization:Other
          Assignee: virt-bugs-at-suse.de
          Reporter: guillaume.gardet-at-arm.com
        QA Contact: qa-bugs-at-suse.de
          Found By: ---
           Blocker: ---

Created attachment 833477
  --> http://bugzilla.opensuse.org/attachment.cgi?id=833477&action=edit
Screenshot of vagrant up failure on aarch64

While testing vagrant on Tumbleweed 20200317 on Raspberry Pi 3 B+, I got the
following error:

Error while creating domain: Error saving the server: Call to VirDomainDefine
Xml failed: unsupported configuration: ps2 is not supported by this QEMU binary

In attachment, you can the screenshot of the problem.