June 2018 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 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 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 1087982] New: XFCE Terminal does not update the tittle correctly because of error in /etc/bash.bashrc
by bugzilla_noreply＠novell.com 02 Jun '20

02 Jun '20

http://bugzilla.suse.com/show_bug.cgi?id=1087982 Bug ID: 1087982 Summary: XFCE Terminal does not update the tittle correctly because of error in /etc/bash.bashrc Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a repeat of Bug 1076927, but for Leap 15.0, so that it can be solved before release. Photo of issue. See attachment 756971 The XFCE Terminal application does not update the tittle correctly. For instance, I "su -" but the tittle shows "terminal - user@hostname", where it should show "terminal - root@hostname" (see attached photo). This is affecting all releases since some update, from 42.2 and up to Tumbleweed. The problem is probably this. Compare "set | less" Settings on the XFCE term SHLVL=2 TERM=xterm-256color UID=1000 USER=cer ... ppwd () { true } but on (working) xterm: SHLVL=2 TERM=xterm TS1=$'\E7\E]2;%s@%s:%s\a\E]1;%s\a\E8' UID=1000 USER=cer ... ppwd () { local dir; local -i width; test -n "$TS1" || return; dir="$(dirs +0)"; let width=${#dir}-18; test ${#dir} -le 18 || dir="...${dir#$(printf "%.*s" $width "$dir")}"; if test ${#TS1} -gt 17; then printf "$TS1" "$USER" "$HOST" "$dir" "$HOST"; else printf "$TS1" "$USER" "$HOST" "$dir"; fi } It appears to be set or not in /etc/bash.bashrc # Set xterm prompt with short path (last 18 characters) # if path tput hs 2>/dev/null || path tput -T $TERM+sl hs 2>/dev/null ; then ... unset _isl _tsl _fsl _sc _rc ppwd () { local dir local -i width test -n "$TS1" || return; dir="$(dirs +0)" let width=${#dir}-18 test ${#dir} -le 18 || dir="...${dir#$(printf "%.*s" $width "$dir")}" if test ${#TS1} -gt 17 ; then printf "$TS1" "$USER" "$HOST" "$dir" "$HOST" else printf "$TS1" "$USER" "$HOST" "$dir" fi } else ppwd () { true; } fi Minas-Anor:~ # rpm -qf /etc/bash.bashrc aaa_base-84.87+git20180208.8eeab90-lp150.2.1.x86_64 Minas-Anor:~ # This was working correctly till some update. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 966057] New: RPM pacakges won't regenerate initrd on removal
by bugzilla_noreply＠novell.com 29 May '20

29 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=966057 Bug ID: 966057 Summary: RPM pacakges won't regenerate initrd on removal Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Currently there are two macros in /etc/rpm/macros.initrd: %regenerate_initrd_post, to be called in the %post and %postun sections and %regenerate_initrd_posttrans, to be called in %posttrans. %regenerate_initrd_post simply sets a flag that the initrd has to be rebuilt after the transaction. The posttrans macros takes care of that. Now, that works fine for installation (%post -> %posttrans) and upgrades (%postun -> %post -> %posttrans), but on removal, %posttrans is never run. How could that be implemented properly? -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1003939] New: enlightenment doesn't honor system locale
by bugzilla_noreply＠novell.com 28 May '20

28 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1003939 Bug ID: 1003939 Summary: enlightenment doesn't honor system locale Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- - install Beta3 in different locale (German in this case) - select XFCE - in summary screen go to software, unselect XFCE and select Englightenment - first log in presents wizard which is only partially in German - Desktop ends up in US locale with US clock and US keyboard even though system settings say de_DE -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1095795] New: acl package does not build reproducibly from gettext
by bugzilla_noreply＠novell.com 27 May '20

27 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1095795 Bug ID: 1095795 Summary: acl package does not build reproducibly from gettext Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: pth(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: jeffm(a)suse.com Blocks: 1047218 Found By: Development Blocker: --- When building the 'acl' package twice (1 minute apart), results always differ and cause unnecessary rebuild and republish in OBS /usr/share/locale/en(a)quot/LC_MESSAGES/acl.mo differs (GNU message catalog (little endian), revision 0.0, 53 messages) @@ -290,8 +290,8 @@ 00001210 67 69 64 2d 42 75 67 73 2d 54 6f 3a 20 61 63 6c |gid-Bugs-To: acl| 00001220 2d 64 65 76 65 6c 40 6e 6f 6e 67 6e 75 2e 6f 72 |-devel(a)nongnu.or| 00001230 67 0a 50 4f 2d 52 65 76 69 73 69 6f 6e 2d 44 61 |g.PO-Revision-Da| -00001240 74 65 3a 20 32 30 31 38 2d 30 36 2d 30 34 20 30 |te: 2018-06-04 0| -00001250 39 3a 33 33 2b 30 30 30 30 0a 4c 61 73 74 2d 54 |9:33+0000.Last-T| +00001240 74 65 3a 20 32 30 33 33 2d 30 37 2d 30 36 20 32 |te: 2033-07-06 2| +00001250 32 3a 34 36 2b 30 30 30 30 0a 4c 61 73 74 2d 54 |2:46+0000.Last-T| 00001260 72 61 6e 73 6c 61 74 6f 72 3a 20 41 75 74 6f 6d |ranslator: Autom| and same for en@boldquot The problem goes away when leaving out the special 'en' translations in acl-2.2.52/po/LINGUAS -en@boldquot -en@quot but there is probably a nicer solution in gettext. maybe unrelated: something in gettext seems to use the COPYRIGHT_HOLDER value from acl-2.2.52/po/Makevars in a bad way to update the copyright line: +++ /home/abuild/rpmbuild/BUILD/acl-2.2.52/po/en(a)quot.po 2033-07-06 22:46:22.762783318 +0000 @@ -1,7 +1,7 @@ # English translations for acl package. -# Copyright (C) 2018 Silicon Graphics, Inc. +# Copyright (C) 2033 Silicon Graphics, Inc. # This file is distributed under the same license as the acl package. -# Automatically generated, 2018. +# Automatically generated, 2033. ... "Report-Msgid-Bugs-To: acl-devel(a)nongnu.org\n" -"POT-Creation-Date: 2018-06-04 09:33+0000\n" -"PO-Revision-Date: 2018-06-04 09:33+0000\n" +"POT-Creation-Date: 2033-07-06 22:46+0000\n" +"PO-Revision-Date: 2033-07-06 22:46+0000\n" -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1067478] New: clang-4.0.1 does not produce reproducible binaries
by bugzilla_noreply＠novell.com 27 May '20

27 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1067478 Bug ID: 1067478 Summary: clang-4.0.1 does not produce reproducible binaries Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: msrb(a)suse.com Blocks: 1061219 Found By: Development Blocker: --- minimal reproducer: osc co openSUSE:Factory/gnustep-libobjc2 cd $_ osc build --noservice chroot /var/tmp/build-root/standard-x86_64/ cd /home/abuild/rpmbuild/BUILD/libobjc2-1.8.1 head -n 348 arc.m > t.m for i in $(seq 4) ; do clang -c t.m 2>/dev/null ; md5sum t.o ; done Actual Results: af35c53170b6d118e1e78ed5b8f2529c t.o 5c1f40dc0874460958b0b05ed3a55f70 t.o de320e239b0feb5431a889ff187389a9 t.o de320e239b0feb5431a889ff187389a9 t.o When running setarch `arch` -R clang to disable ASLR or leaving out the last function in t.m (e.g. head -n 315 arc.m > t.m) it does produce consistent results. -- You are receiving this mail because: You are on the CC list for the bug.

2 4