May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1159029] New: nagstamon broken
by bugzilla_noreply＠novell.com 14 Jun '21

14 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1159029 Bug ID: 1159029 Summary: nagstamon broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: thalunil(a)kallisti.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Similar to # 1119547 nagstamon is broken for me with Xorg. When setting "xhost +localhost" it works as expected... [Errno 2] No such file or directory: '/home/acb/.nagstamon/nagstamon.pid' Traceback (most recent call last): File "/usr/bin/nagstamon", line 60, in <module> from Nagstamon.QUI import (APP, File "/usr/lib/python3.6/site-packages/Nagstamon/QUI/__init__.py", line 6303, in <module> statuswindow = StatusWindow() File "/usr/lib/python3.6/site-packages/Nagstamon/QUI/__init__.py", line 904, in __init__ self.ewmh = EWMH() File "/usr/lib/python3.6/site-packages/Nagstamon/thirdparty/ewmh.py", line 50, in __init__ self.display = _display or display.Display() File "/usr/lib/python3.6/site-packages/Nagstamon/thirdparty/Xlib/display.py", line 80, in __init__ self.display = _BaseDisplay(display) File "/usr/lib/python3.6/site-packages/Nagstamon/thirdparty/Xlib/display.py", line 62, in __init__ display.Display.__init__(*(self, ) + args, **keys) File "/usr/lib/python3.6/site-packages/Nagstamon/thirdparty/Xlib/protocol/display.py", line 129, in __init__ raise error.DisplayConnectionError(self.display_name, r.reason) Xlib.error.DisplayConnectionError: Can't connect to display ":0.0": b'Invalid MIT-MAGIC-COOKIE-1 key' -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1159192] New: moonjit/lua51-luajit replacement: neovim isn't able to build with moonjit
by bugzilla_noreply＠novell.com 10 Jun '21

10 Jun '21

http://bugzilla.suse.com/show_bug.cgi?id=1159192 Bug ID: 1159192 Summary: moonjit/lua51-luajit replacement: neovim isn't able to build with moonjit Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- lua51-luajit has been replaced by moonjit in openSUSE Tumbleweed and Leap 15.2, BuildRequires lua51-luajit-devel just not work anymore, adapt to this replacement, BuildRequires luajit-devel should just work. https://build.opensuse.org/package/show/openSUSE:Factory/neovim -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1149774] New: Maintenance test update for Leap 15.2
by bugzilla_noreply＠novell.com 10 Jun '21

10 Jun '21

http://bugzilla.suse.com/show_bug.cgi?id=1149774 Bug ID: 1149774 Summary: Maintenance test update for Leap 15.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mschnitzer(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a tracker bug for the maintenance test update for Leap 15.2 -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1087706] New: games:tools/steam: Bug steam on openSUSE Tumbleweed 20180329 fails on startup with "libGL error: failed to load driver"
by bugzilla_noreply＠novell.com 09 Jun '21

09 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1087706 Bug ID: 1087706 Summary: games:tools/steam: Bug steam on openSUSE Tumbleweed 20180329 fails on startup with "libGL error: failed to load driver" Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: matthias(a)mailaender.name Reporter: okurz(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: opensuse(a)dstoecker.de Found By: --- Blocker: --- ## Observation Trying to develop an openQA test for "steam" I stepped into the issue reported on https://askubuntu.com/questions/614422/problem-with-installing-steam-on-ubu… with "libGL error: failed to load driver" where the workaround mentioned in https://askubuntu.com/a/614458 works. ## Reproducible On openSUSE Tumbleweed 20180329 but I think I have seen the same error already on openSUSE Leap 15.0 whereas the installation on openSUSE Leap 42.3 was fine. ## Problem https://build.opensuse.org/request/show/452542 removed some patches to remove libstdc but maybe this is still - or again - needed. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1166974] New: gnome-calendar is frozen for several seconds on the initial start
by bugzilla_noreply＠novell.com 09 Jun '21

09 Jun '21

http://bugzilla.suse.com/show_bug.cgi?id=1166974 Bug ID: 1166974 Summary: gnome-calendar is frozen for several seconds on the initial start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: gnome-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello team Seems like gnome-calendar is stuck for several seconds during initial startup. Or at least I can't really move the the application window for something like 8 seconds, until all calendars are refreshed. I have relatively simple setup * personal gmail calendar with one calendar oly * office365 with 3 calendar (openSUSE Rel-eng, team one, and personal one). Can this be addressed in a way that the "waiting for sync" part doesn't block the entire application? It's perfectly expected not to fully visualize calendar part, it's just that app should not be stuck. Thank you -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1140121] New: Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found
by bugzilla_noreply＠novell.com 07 Jun '21

07 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 Bug ID: 1140121 Summary: Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting a few weeks (at least 4) agao, I get the message "Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found" in my journal. It seems to stem from NetworkManager start, but I'm not really sure. Starting the service systemd-resolved.service stops this message, but gives lots of other errors including a partial break of connecivity. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1161754] New: [usb-c] System loses USB NIC in Docking Station at random Times
by bugzilla_noreply＠novell.com 05 Jun '21

05 Jun '21

http://bugzilla.suse.com/show_bug.cgi?id=1161754 Bug ID: 1161754 Summary: [usb-c] System loses USB NIC in Docking Station at random Times Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: oneukum(a)suse.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- Created attachment 828223 --> http://bugzilla.suse.com/attachment.cgi?id=828223&action=edit Kernel log On a laptop (Dell Precision 5520) the 1GB NIC is contained in the docking station which is connected via USB-C. With kernel 4.12.14-lp151.28.36-default this device gets 'lost' at random times. 1. The kernel shows no obvious signs of the device getting lost. The lines like: usb 3-1.4: reset high-speed USB device number 6 using xhci_hcd don't seem to occur when the device gets lost. 2. The network device is no longer disappears from the lsusb output. 3. In the more annoying cases, the network device 'hangs': and 'ip addr' hangs in a 'sendto' to a netlink socket. In other cases, the device disappears from the 'ip addr' output, unplugging and plugging the docking station causes the devices to re-enumerated. NOTE: in the attached log, the re-docking happens after the 202556.480017 timestamp. The issue seems to start once the machine has been suspended and/or redocked after a boot. The issue did not occur on a Leap 42.3 kernel. -- You are receiving this mail because: You are on the CC list for the bug.

2 22

[Bug 1162112] New: xmvn produces unreproducible output
by bugzilla_noreply＠novell.com 05 Jun '21

05 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1162112 Bug ID: 1162112 Summary: xmvn produces unreproducible output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: fstrba(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1062303 Found By: Development Blocker: --- While working on reproducible builds for openSUSE, I found that xmvn creates .xml files with randomness per setUuid( UUID.randomUUID().toString() ) in xmvn-tools/xmvn-install/src/main/java/org/fedoraproject/xmvn/tools/install/JavaPackage.java xmvn-tools/xmvn-install/src/main/java/org/fedoraproject/xmvn/tools/install/impl/DefaultArtifactInstaller.java +++ new//usr/share/maven-metadata/jackson-parent.xml 2019-11-20 12:00:00.0000 00000 +0000 @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="UTF-8"?> <metadata xmlns="http://fedorahosted.org/xmvn/METADATA/3.0.0"> - <uuid>84081e46-b2dd-41c9-b0e1-3e89752c546d</uuid> + <uuid>c67ba8dc-3f70-4b4e-95b4-c0afdf000afe</uuid> <artifacts> <artifact> <groupId>com.fasterxml.jackson</groupId> @@ -8,7 +8,7 @@ <extension>pom</extension> <version>2.10</version> <path>/usr/share/maven-poms/jackson-parent/jackson-parent.pom</path> - <uuid>59d7475c-e3da-4430-ad13-b75a5ccd70da</uuid> + <uuid>1bf0dc1e-77d4-4634-a520-60f749c63940</uuid> <properties> That could be replaced by setUuid( UUID.nameUUIDFromBytes(somethingspecific.getBytes()).toString() ); Another source of non-determinism is filesystem readdir order: /usr/share/maven-metadata/openjfx.xml differs (XML document text) --- old//usr/share/maven-metadata/openjfx.xml 2020-01-22 00:00:00.000000000 +0 000 +++ new//usr/share/maven-metadata/openjfx.xml 2020-01-22 00:00:00.000000000 +0 000 @@ -273,9 +273,10 @@ <artifactId>javafx-media</artifactId> <classifier>linux</classifier> <version>11.0.6</version> - <path>/usr/share/java/openjfx/javafx-media-linux.jar</path> + <path>/usr/lib64/java/openjfx/javafx-media-linux.jar</path> <uuid>d41d8cd9-8f00-3204-a980-0998ecf8427e</uuid> <properties> + <native>true</native> <xmvn.resolver.disableEffectivePom>true</xmvn.resolver.disableEffective Pom> </properties> </artifact> @@ -329,9 +330,10 @@ <artifactId>javafx-swing</artifactId> <classifier>linux</classifier> <version>11.0.6</version> - <path>/usr/share/java/openjfx/javafx-swing-linux.jar</path> + <path>/usr/lib64/java/openjfx/javafx-swing-linux.jar</path> <uuid>d41d8cd9-8f00-3204-a980-0998ecf8427e</uuid> <properties> + <native>true</native> <xmvn.resolver.disableEffectivePom>true</xmvn.resolver.disableEffectivePom> </properties> </artifact> @@ -397,9 +399,10 @@ <artifactId>javafx-web</artifactId> <classifier>linux</classifier> <version>11.0.6</version> - <path>/usr/share/java/openjfx/javafx-web-linux.jar</path> + <path>/usr/lib64/java/openjfx/javafx-web-linux.jar</path> <uuid>d41d8cd9-8f00-3204-a980-0998ecf8427e</uuid> <properties> + <native>true</native> <xmvn.resolver.disableEffectivePom>true</xmvn.resolver.disableEffectivePom> </properties> </artifact> but here the two results are not even equivalent - is that a bug? -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1169460] New: Hibernation -> Resume -> Restart sequence causes grub2-once to prevent start of auditd.service
by bugzilla_noreply＠novell.com 04 Jun '21

04 Jun '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1169460 Bug ID: 1169460 Summary: Hibernation -> Resume -> Restart sequence causes grub2-once to prevent start of auditd.service Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: beppe85(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is another manifestation of the issues caused by reloading of PID1 in systemd, usually a `systemctl enable/disable` during boot. In this scenario, the service grub2-once.service is enabled for the restart subsequent to hibernation. The unit disables itself when it runs. To keep the same behavior without the side-effect, a compromise can be reached if it avoids disabling itself during boot. It can be delayed to after boot completes, or kept enabled at all times running based on a condition. Steps to reproduce: 1. Hibernate 2. Resume 3. Restart Actual result: 1. auditd.service fails during boot sequence Expected result: 1. System boots without failures -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1061205] New: [HPC, Lmod] Make package lua-lmod Arch-dependent
by bugzilla_noreply＠novell.com 04 Jun '21

04 Jun '21

http://bugzilla.suse.com/show_bug.cgi?id=1061205 Bug ID: 1061205 Summary: [HPC, Lmod] Make package lua-lmod Arch-dependent Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de CC: nmoreychaisemartin(a)suse.com Found By: Development Blocker: --- Lmod is written in Lua only and doesn't ship any *.so plugins. At first glance it therefore looks like a candidate for an Arch independent package. This however is not true: the search path for .so files gets hard-coded into some lua files, thus other Lua packages which are used by Lmod and require .so files won't work any more. Therefore make the lua-lmod package arch dependent (only the doc packages may be arch-independent). -- You are receiving this mail because: You are on the CC list for the bug.

2 17