May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1098264] New: gnome-keyring-daemon couldn't access control socket: /run/user/420470/keyring/control
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1098264 Bug ID: 1098264 Summary: gnome-keyring-daemon couldn't access control socket: /run/user/420470/keyring/control Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: jmader2(a)gmu.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting `gnome-session` produces the following message on the console, ** Message: couldn't access control socket: /run/user/420470/keyring/control: No such file or directory This socket does exist (at least later). -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1097726] New: xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1097726 Bug ID: 1097726 Summary: xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: jmader2(a)gmu.edu QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 774097 --> http://bugzilla.suse.com/attachment.cgi?id=774097&action=edit X server log After a similar autoinstall with AutoYaST as Leap 42.3, Leap 15.0 does not start gdm, ● display-manager.service - X Display Manager Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-06-14 13:22:39 EDT; 25min ago Main PID: 1855 (gdm) Tasks: 3 (limit: 4915) CGroup: /system.slice/display-manager.service └─1855 /usr/sbin/gdm gdm[1855]: Child process -2033 was already dead. gdm[1855]: Child process 2023 was already dead. gdm[1855]: Unable to kill session worker process gdm[1855]: GdmDisplay: display lasted 0.879208 seconds gdm[1855]: Child process -2075 was already dead. gdm[1855]: Child process 2065 was already dead. gdm[1855]: Unable to kill session worker process gdm[1855]: GdmDisplay: display lasted 0.844312 seconds gdm[1855]: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors gdm[1855]: Child process -2118 was already dead. -- You are receiving this mail because: You are on the CC list for the bug.

2 17

[Bug 1124129] New: tmpfiles.d/kubernetes.conf uses legacy path, systemd complaining
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1124129 Bug ID: 1124129 Summary: tmpfiles.d/kubernetes.conf uses legacy path, systemd complaining Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- >From the logs: 2019-01-28T01:14:45.443906+00:00 localhost systemd-tmpfiles[499]: [/usr/lib/tmpfiles.d/kubernetes.conf:1] Line references path below legacy directory /var/run/, updating /var/run/kubernetes 342206222 /run/kubernetes; please update the tmpfiles.d/ drop-in file accordingly. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 974800] New: unable to run go-5 on armv7
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=974800 Bug ID: 974800 Summary: unable to run go-5 on armv7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: armv7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmueller(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- running go-5 on tumbleweed/armv7hl gives an endless hang, e.g. as seen on "go-5 version". gdb gives: Program received signal SIGINT, Interrupt. 0xb639b750 in __pthread_mutex_unlock_usercnt ( mutex=0xb6fff4dc <_rtld_local+1244>, decr=1) at pthread_mutex_unlock.c:73 73 pthread_mutex_unlock.c: No such file or directory. (gdb) p i No symbol "i" in current context. (gdb) bt #0 0xb639b750 in __pthread_mutex_unlock_usercnt ( mutex=0xb6fff4dc <_rtld_local+1244>, decr=1) at pthread_mutex_unlock.c:73 #1 0xb64cb4ec in __GI___dl_iterate_phdr ( callback=0xb64cb4ec <__GI___dl_iterate_phdr+436>, data=0x10415c54, data@entry=0x10415c4c) at dl-iteratephdr.c:83 #2 0xb64cc3b0 in __gnu_Unwind_Find_exidx (pc=pc@entry=3057612094, pcount=0x10415c74, pcount@entry=0x10415c6c) at ../sysdeps/arm/find_exidx.c:74 #3 0xb637c4f0 in get_eit_entry (ucbp=ucbp@entry=0x10415c88, return_address=3057612094) at ../../../libgcc/unwind-arm-common.inc:210 #4 0xb637cc50 in __gnu_Unwind_Backtrace (trace=0xb6cef380 <unwind>, trace_argument=0x10415f28, entry_vrs=<optimized out>) at ../../../libgcc/unwind-arm-common.inc:567 #5 0xb637d700 in _Unwind_Backtrace () at ../../../libgcc/config/arm/libunwind.S:360 #6 0xb6cef440 in backtrace_full (state=<optimized out>, skip=skip@entry=0, callback=<optimized out>, error_callback=<optimized out>, data=0x10415f54, data@entry=0x10415f4c) at ../../../libbacktrace/backtrace.c:106 #7 0xb69d92d4 in runtime_callers (skip=skip@entry=1, locbuf=locbuf@entry=0x10418074, m=m@entry=32, keep_thunks=keep_thunks@entry=0 '\000') at ../../../libgo/runtime/go-callers.c:168 #8 0xb69e8adc in mcommoninit (mp=mp@entry=0x10418000) ---Type <return> to continue, or q <return> to quit---c at ../../../libgo/runtime/proc.c:808 #9 0xb69eb3d4 in runtime_allocm (p=p@entry=0x0, stacksize=stacksize@entry=-1, ret_g0_stack=ret_g0_stack@entry=0x0, ret_g0_stacksize=ret_g0_stacksize@entry=0x0) at ../../../libgo/runtime/proc.c:1146 #10 0xb69eb47c in newm (fn=0xb69ede60 <sysmon>, p=p@entry=0x0) at ../../../libgo/runtime/proc.c:1433 #11 0xb69ed3ec in runtime_main (dummy=<optimized out>) at ../../../libgo/runtime/proc.c:575 #12 0xb69eaf60 in kickoff () at ../../../libgo/runtime/proc.c:235 #13 0xb63f7540 in setcontext () at ../sysdeps/unix/sysv/linux/arm/setcontext.S:82 Backtrace stopped: previous frame identical to this frame (corrupt stack?) -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1119634] New: go: multi-version installation is broken on version switch
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1119634 Bug ID: 1119634 Summary: go: multi-version installation is broken on version switch Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The way that multi-version Go works on openSUSE is through update-alternatives. One aspect of this is a profile.d script that sets GOROOT= to the current version. This means that changing the Go version will make GOROOT incorrect in the current login session -- which results in broken builds and other fun problems. Zygmunt Krynicki pointed out that this is completely unnecessary -- each Go compiler binary contains a correct GOROOT. So this explicit setting is the only reason upgrades are broken. Removing it will fix the problem entirely. -- You are receiving this mail because: You are on the CC list for the bug.

2 26

[Bug 1082409] New: Major regression in usability of go package
by bugzilla_noreply＠novell.com 04 Jun '20

04 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1082409 Bug ID: 1082409 Summary: Major regression in usability of go package Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmacvicar(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- By accident I discovered that I could not compile software because my go was pointing to go1.4 scanner_test.go:7:2: cannot find package "github.com/dmacvicar/someproject" in any of: /usr/lib64/go1.4/src/github.com/dmacvicar/someproject (from $GOROOT) I never installed go1.4 So I tried to remove it: $ sudo zypper rm go go1.4 go1.6 [sudo] password for root: Loading repository data... Reading installed packages... Resolving package dependencies... The following 9 packages are going to be REMOVED: go go1.4 go1.4-doc go1.4-race go1.6 go1.6-doc go1.6-race go-doc go-race I try to install go again: $ sudo zypper in go Loading repository data... Reading installed packages... Resolving package dependencies... The following 11 NEW packages are going to be installed: go go1.4 go1.4-doc go1.4-race go1.6 go1.6-doc go1.6-race go1.9 go1.9-doc go1.9-race go-race The following recommended package was automatically selected: go1.9-doc Again 1.4! I imagined go required go1.4 or something like that, but I locked go1.4 and I was still able to install go. I think the problem lies in that both "go" and "go1.9" provide "go = 1.9", and on top of that "go" requires "go1.9". What is the point of the "go" package? It only confuses the solver. Every goX.X package can still "provide go". That way only the latest will get installed. Additionally, what is the point in having go1.4 there? Is it only to build the whole chain? Then there is a problem with GOROOT. Installing a newer go, updates the alternatives but GOROOT is still pointing to the go1.4 go. -- You are receiving this mail because: You are on the CC list for the bug.

2 40

[Bug 1116959] New: fwupd cannot update firmware
by bugzilla_noreply＠novell.com 03 Jun '20

03 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1116959 Bug ID: 1116959 Summary: fwupd cannot update firmware Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: kacper.pluta(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I wanted to update firmware of my Logitech Unifying receiver and unfortunately it cannot be done on Leap 15. I am getting the following message: Not compatible with bootloader version: failed predicate [BOT03.0[0-1]_* regex BOT03.02_B0009] -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1011815] New: [Build 20161121] Console messages writes over YaST configuration page in terminal
by bugzilla_noreply＠novell.com 03 Jun '20

03 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1011815 Bug ID: 1011815 Summary: [Build 20161121] Console messages writes over YaST configuration page in terminal Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: http://openqa.opensuse.org/tests/309124/modules/yast2_ samba/steps/37 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: zluo(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ui_gnome@64bit fails in [yast2_samba](http://openqa.opensuse.org/tests/309124/modules/yast2_samba/st… dmesg messages writes over YaST configuration screen and breaks needle match. ## Reproducible Fails since (at least) Build [20161121](http://openqa.opensuse.org/tests/308999) ## Expected result The message should not show up at all to screen. Last good: [20161120](http://openqa.opensuse.org/tests/308402) (or more recent) ## Further details Always latest result in this scenario: [latest](http://openqa.opensuse.org/tests/latest?arch=x86_64&version=Tumblew… -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1090346] New: zypp suppresses error output from InstallAppdata.sh
by bugzilla_noreply＠novell.com 03 Jun '20

03 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1090346 Bug ID: 1090346 Summary: zypp suppresses error output from InstallAppdata.sh Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- zypp/RepoManager.cc has special code to call /usr/lib/zypp/plugins/appdata/InstallAppdata.sh. In Bug 1090345 this command seems to have failed but there's no output to debugging due to this redirection. Please consider not redirecting to /dev/null. -- You are receiving this mail because: You are on the CC list for the bug.

2 14

[Bug 1099880] New: yast2 Bug: Packman and NVIDIA repositories do not show in the list of online community repositories
by bugzilla_noreply＠novell.com 03 Jun '20

03 Jun '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1099880 Bug ID: 1099880 Summary: yast2 Bug: Packman and NVIDIA repositories do not show in the list of online community repositories Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: simonizor(a)protonmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I'm not sure when this started happening exactly, but I first encountered it 2 days ago when trying to help someone add media codecs after installing Tumbleweed. The Packman and NVIDIA repositories no longer show in the list of community repositories to add when going from `Software Repositories` -> click `Add` button in lower left corner -> select `Community Repositories` -> click `Next`. Both Packman and NVIDIA used to show in this list, neither are showing for me and a few other people that I've asked to look also. I already have the Packman repo added, so AFAIK, it shouldn't show in the list of community repos to add anymore, but NVIDIA should as I haven't added that. Screenshot of the `Community Repositories` list: https://u.teknik.io/vVS9A.png -- You are receiving this mail because: You are on the CC list for the bug.

2 3