May 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1037126] binutils: enable as-needed by default
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1037126 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1035599] GNOME:Apps/abiword: black page/canvas
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.novell.com/show_bug.cgi?id=1035599 http://bugzilla.novell.com/show_bug.cgi?id=1035599#c7 Paul Dufresne <dufresnep(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS --- Comment #7 from Paul Dufresne <dufresnep(a)gmail.com> --- The patch works (I had ommited to install libabiword package too, that's why it was not working for me previously). My Build repository is at: https://build.opensuse.org/package/binaries/home:dufrp:branches:GNOME:Apps/… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1035599] GNOME:Apps/abiword: black page/canvas
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.novell.com/show_bug.cgi?id=1035599 http://bugzilla.novell.com/show_bug.cgi?id=1035599#c6 --- Comment #6 from Paul Dufresne <dufresnep(a)gmail.com> --- Created attachment 723487 --> http://bugzilla.novell.com/attachment.cgi?id=723487&action=edit tested working patch from upstream (well redone with quilt) Don't forget to install both abiword and libabiword generated packages. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036342] New: [20170424]: gnome-session segfault in libgtk-3.so.0.2200.11
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1036342 Bug ID: 1036342 Summary: [20170424]: gnome-session segfault in libgtk-3.so.0.2200.11 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: markos.chandras(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, Ever since I updated to 20170424 I can't get gnome session to start. gdm is stuck in an infinite loop and I can see the following issue on dmesg [ 209.298800] gnome-session-f[2668]: segfault at 0 ip 00007fb96a6e78a9 sp 00007ffc3a8734b0 error 4 in libgtk-3.so.0.2200.11[7fb96a3f8000+708000] [ 256.323964] gnome-session-f[3378]: segfault at 0 ip 00007f7a6bfe08a9 sp 00007ffd9c426de0 error 4 in libgtk-3.so.0.2200.11[7f7a6bcf1000+708000] I can't tell if the previous snapshot worked for me because I haven't update in a while. Please let me know if you need more information from me -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 1027181] Do not embed ruby into YaST2
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1027181 http://bugzilla.opensuse.org/show_bug.cgi?id=1027181#c1 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Josef Reidinger <jreidinger(a)suse.com> --- embedded ruby is added -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036590] [Build 20170425] openQA test fails in firewall_enabled
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036590 http://bugzilla.suse.com/show_bug.cgi?id=1036590#c3 --- Comment #3 from Oliver Kurz <okurz(a)suse.com> --- Hi Matthias, thank you for taking a look into this. (In reply to Matthias Gerstner from comment #2) > Who is supposed to install and enable SuSEfirewall2 in the openQA setup? > Where does it happen? maybe that part wasn't clear from the description. The scenario is an upgrade scenario from openSUSE 12.2(!) to the current openSUSE Tumbleweed snapshot. In this scenario there is a pre-installed qcow image with openSUSE 12.2 which has the firewall installed and enabled by default. Following the screenshots in the openQA test openqa.opensuse.org/tests/393541/ (or more recent in the same scenario) you should be able to follow the rough set of actions conducted: * on a virtual machine with the aforementioned qcow image as virtual hard disk (you can get it from https://openqa.opensuse.org/tests/393541/asset/hdd/openSUSE-12.2-x86_64.hda) * an openSUSE Tumbleweed NET CD/DVD is booted * "Upgrade" is selected * An "offline upgrade" is conducted * The upgraded installation is booted * Same tests as for a clean install are conducted including the firewall test -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1030548] [Build 9.7] openQA test fails in yast2_bootloader "error: install device isn't specified"
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1030548 http://bugzilla.suse.com/show_bug.cgi?id=1030548#c5 --- Comment #5 from Josef Reidinger <jreidinger(a)suse.com> --- mchang - same happen on my system when doing zypper dup in Tumbleweed. I debug it and found where is problem. shim passes wrong target to grub2-install see my console session: pepa:/home/jreidinger # grub2-install --no-nvram --removable Installing for i386-pc platform. grub2-install: error: install device isn't specified. pepa:/home/jreidinger # grub2-install --no-nvram --removable --target=x86_64-efi Installing for x86_64-efi platform. Installation finished. No error reported. pepa:/home/jreidinger # shim-install --config-file=/boot/grub2/grub.cfg --no-nvram --removable copying /usr/lib64/efi/grub.efi to /boot/efi/EFI/boot/grub.efi Installing for i386-pc platform. /usr/sbin/grub2-install: error: install device isn't specified. so shim-install do not pass target and grub2-install for unknown reason try to use i386-pc. shim-install do not recognize --target option, so I cannot help there with passing it explicitly. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1036590] [Build 20170425] openQA test fails in firewall_enabled
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1036590 http://bugzilla.suse.com/show_bug.cgi?id=1036590#c2 --- Comment #2 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- Thanks for the report. The only change in sr#483163 related to the startup of SuSEfirewall2 that comes to my mind would be this one: > --- SuSEfirewall2_init.service > +++ SuSEfirewall2_init.service > @@ -3,6 +3,8 @@ > Before=network.service > DefaultDependencies=false > Requires=sysinit.target > +After=sysinit.target > +RequiresMountsFor=/dev/shm > Conflicts=firewalld.service So if for some reason in the openQA context the sysinit.target is not reached or mounting of /dev/shm does not happen then this might explain the failing test. I've tested a minimal server install of openSUSE-Tumbleweed-NET-x86_64-Snapshot20170429-Media.iso and after installing and enabling SuSEfirewall2 everything works as expected. After reboot the firewall is up. However, the firewall is not installed and enabled by default. The installer doesn't ask about it. Don't know why that is different in Tumbleweed than in other SUSE distros. Who is supposed to install and enable SuSEfirewall2 in the openQA setup? Where does it happen? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1035062] Tumbleweed no longer executes scripts in /etc/init.d
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.suse.com/show_bug.cgi?id=1035062 http://bugzilla.suse.com/show_bug.cgi?id=1035062#c12 --- Comment #12 from Thorsten Kukuk <kukuk(a)suse.com> --- It's a trivial fix for systemd-sysv-convert you need: --- systemd-sysv-convert (revision 81277f7f3786474d7a4cf7ed9b820cd3) +++ systemd-sysv-convert (working copy) @@ -39,7 +39,7 @@ service=$1 runlevel=$2 priority=-1 -for l in $(ls /etc/rc.d/rc$runlevel.d/) ; do +for l in $(ls /etc/init.d/rc$runlevel.d/) ; do initscript=$(basename $l) if [ ${initscript:0:1} != "S" -o ${initscript:3} != "$service" ]; then continue -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1035062] New: Tumbleweed no longer executes scripts in /etc/init.d
by bugzilla_noreply＠novell.com 02 May '17

02 May '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1035062 Bug ID: 1035062 Summary: Tumbleweed no longer executes scripts in /etc/init.d Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jeromed(a)tpg.com.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As per the tital the latest updates of TW no longer execute scripts in /etc/init.d. The following are 2 examples of the problem I have encounted. 1 - I have a cut down TW server running named and openvpn. Noticed since the second last update neither the openvpn and named scripts now execute on init and I have to manually run them. 2 - To confirm point I also have a TW install on a laptop with KDE and virtual box no longer runs, complains of missing drivers. Upon investigating further vbox have 2 scripts in /etc/init.d that needs to execute on startup, manually running them fixes any issues with VirtualBox. Please let me know if you need any further information, i could not find any meaningful message in dmesg or journalctl. Cheers and thanks Jerome -- You are receiving this mail because: You are on the CC list for the bug.

1 8