February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 953735] New: Change libqt5-creator name to qt5-creator
by bugzilla_noreply＠novell.com 03 Apr '22

03 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=953735 Bug ID: 953735 Summary: Change libqt5-creator name to qt5-creator Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ronisbr(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi! In Tumbleweed, I have been using the package qt-creator to develop Qt applications for a long time. I have always complained about the old version, since qt-creator is 3.2.2 and the newest version available is 3.5.1. However, it turns out that the newest version is already available in Tumbleweed (and in Leap) under the name libqt5-creator. Is there any good reason to name the package as libqt5-creator? I think this is very confusing. Since it has a lib* in the name, I did not even look at the description, so I was using a very old version all the time. Thus, I am wondering if it is possible to change the name of libqt5-creator to qt5-creator or something else. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1099804] New: Gnucash is unable to retrieve and open guide files in openSUSE LEAP 15.0
by bugzilla_noreply＠novell.com 01 Apr '22

01 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1099804 Bug ID: 1099804 Summary: Gnucash is unable to retrieve and open guide files in openSUSE LEAP 15.0 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: michele.di.pede(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using openSUSE Leap 15.0 with KDE. Gnucash is not able to locate and open the guide file despite the gnucash-docs package is correctly installed. I tried to dig a bit deeper with this invocation: gnucash --debug --extra --log gnc.gui=debug This is the relevant part of the trace file: [...] * 10:00:08 DEBUG <gnc.gui> [enter ../gnucash/gnome-utils/gnc-file.c:gnc_post_file_open()] filename * 10:00:14 DEBUG <gnc.gui> [gnc_gnome_help] Attempting to opening help uri ghelp:gnucash-guide * 10:00:16 CRIT <gnc.gui> [gnc_gnome_help()] La posizione specificata non è supportata [...] Last trace is the italian translation for "The specified position is not supported". In my system the gnucash configuration file /.gnucash/config.auto is not present despite it is mentioned in gnucash man help file. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1014929] New: GNOME:Apps/gnucash-docs: Bug
by bugzilla_noreply＠novell.com 01 Apr '22

01 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1014929 Bug ID: 1014929 Summary: GNOME:Apps/gnucash-docs: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: os.gnome.maintainers(a)gmail.com Reporter: adrian.klaver(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Need to add a dependency for yelp to package. Covers the case where the package is being installed on system that is not using GNOME as its desktop, eg using KDE. Without yelp you get the following message when trying to open the GnuCash Help: "GnuCash could not find the files for the help documentation. " even though gnucash-docs is installed. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1091802] New: openldap2: incomplete macro expansion(?) in script
by bugzilla_noreply＠novell.com 01 Apr '22

01 Apr '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1091802 Bug ID: 1091802 Summary: openldap2: incomplete macro expansion(?) in script Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: GuoHouzuo(a)gmail.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de CC: mpluskal(a)suse.com, varkoly(a)suse.com Found By: --- Blocker: --- The following product is going to be upgraded: openSUSE Tumbleweed 20180427-0 -> 20180501-0 x86_64 base openSUSE (38/73) Installing: openldap2-2.4.46-33.1.x86_64 ...................................................[done] Additional rpm output: /usr/sbin/openldap_update_modules_path.sh: line 1: s: command not found Updating /etc/sysconfig/openldap ... -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1040589] New: bash/gcc/gzip/python differ between builds because of profiling
by bugzilla_noreply＠novell.com 31 Mar '22

31 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1040589 Bug ID: 1040589 Summary: bash/gcc/gzip/python differ between builds because of profiling Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: rguenther(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matz(a)suse.com Found By: Development Blocker: --- In https://build.opensuse.org/project/prjconf/openSUSE:Factory we have %do_profiling 1 and because of that in our bash.spec we enable gcc's 'profile feedback directed optimizations' but that causes the jobs.o and resulting bash binary to differ between builds, even when running on the same build host. And because of that, build-compare always thinks there is a change and triggers a re-publish and rebuild of depending packages We also have such binary diffs in gcc6 and gcc6.spec calls a make profiledbootstrap The do_profiling macro is used in bash gzip hello python3-base python-base sed xz and in http://rb.zq1.de/compare.factory-20170523/bash-compare.out http://rb.zq1.de/compare.factory-20170523/gcc6-compare.out http://rb.zq1.de/compare.factory-20170523/gzip-compare.out http://rb.zq1.de/compare.factory-20170523/python-base-compare.out http://rb.zq1.de/compare.factory-20170523/python3-base-compare.out we have strange diffs in assembler that I could not trace down to other sources of non-determinism until today. Diffs did go away when building without profiling (it was harder to disable for gcc6 and bash though) Do the profiles just count invocations of functions or do they depend on the type and speed of the system? In the first case, it should be possible to fix the profiling runs to be deterministic, but for that it would be useful to be able to see the differences between runs. How could I diff gcc's .gcda files? -- You are receiving this mail because: You are on the CC list for the bug.

2 15

[Bug 1127000] New: qemu smb share leaves a lot of zombies
by bugzilla_noreply＠novell.com 30 Mar '22

30 Mar '22

http://bugzilla.suse.com/show_bug.cgi?id=1127000 Bug ID: 1127000 Summary: qemu smb share leaves a lot of zombies Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: brogers(a)suse.com Found By: --- Blocker: --- With this commandline: /usr/bin/qemu-system-x86_64 -machine accel=kvm -k en-us -smp 4 -daemonize -pidfile /tmp/qemu.pid.30512 -device virtio-rng-pci -device ich9-usb-ehci1,multifunction=on,id=ehci -device ich9-usb-uhci1,masterbus=ehci.0,multifunction=on -device ich9-usb-uhci2,masterbus=ehci.0,firstport=2,multifunction=on -device ich9-usb-uhci3,masterbus=ehci.0,firstport=4,multifunction=on -drive file=/home/new/win.qcow2,discard=unmap -soundhw ac97 -spice disable-ticketing,gl=on,unix,addr=/tmp/qemu-spice.30512.sock -device virtio-serial -chardev spicevmc,id=vdagent,name=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -net user,smb=/home/smb,hostfwd=tcp::3389-:3389 -net nic,model=rtl8139 -rtc base=localtime -vga qxl -device usb-tablet -m 1G After some time running, I see a lot of smbd zombie processes: > xslaby 30546 2.4 7.4 2572952 1213920 ? Tl úno24 60:58 /usr/bin/qemu-system-x86_64 -machine accel=kvm -k en-us -smp 4 -daemonize -pidfile /tmp/qemu.pid.30512 -device virtio-rng-pci -device ich9-usb-ehci1,multifunction=on,id=ehci -device ich9-usb-uhci1,masterbus=ehci.0,multifunction=on -device ich9-usb-uhci2,masterbus=ehci.0,firstport=2,multifunction=on -device ich9-usb-uhci3,masterbus=ehci.0,firstport=4,multifunction=on -drive file=/home/new/win.qcow2,discard=unmap -soundhw ac97 -spice disable-ticketing,gl=on,unix,addr=/tmp/qemu-spice.30512.sock -device virtio-serial -chardev spicevmc,id=vdagent,name=vdagent -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2 -net user,smb=/home/smb,hostfwd=tcp::3389-:3389 -net nic,model=rtl8139 -rtc base=loca ltime -vga qxl -device usb-tablet -m 1G > xslaby 30600 0.0 0.1 49892 20088 ? Ss úno24 0:01 \_ /usr/sbin/smbd -l /tmp/qemu-smb.ZIY0XZ -s /tmp/qemu-smb.ZIY0XZ/smb.conf > xslaby 30602 0.0 0.0 45440 4892 ? S úno24 0:00 \_ /usr/sbin/smbd -l /tmp/qemu-smb.ZIY0XZ -s /tmp/qemu-smb.ZIY0XZ/smb.conf > xslaby 30603 0.0 0.0 45432 3328 ? S úno24 0:00 \_ /usr/sbin/smbd -l /tmp/qemu-smb.ZIY0XZ -s /tmp/qemu-smb.ZIY0XZ/smb.conf > xslaby 32070 0.0 0.0 0 0 ? Z úno24 0:00 \_ [smbd] <defunct> > xslaby 1184 0.0 0.0 0 0 ? Z úno24 0:00 \_ [smbd] <defunct> > xslaby 2708 0.0 0.0 0 0 ? Z úno24 0:00 \_ [smbd] <defunct> > xslaby 2902 0.0 0.0 0 0 ? Z úno24 0:00 \_ [smbd] <defunct> > xslaby 3834 0.0 0.0 0 0 ? Z úno24 0:00 \_ [smbd] <defunct> > xslaby 4514 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 7508 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 9429 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 10975 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 12896 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 14454 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 16387 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 18100 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 19775 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 21479 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 31399 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 2457 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 4636 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 6490 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 8795 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 10394 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 12068 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 13606 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 15829 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 17444 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 19211 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 20870 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 22653 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 25946 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 27950 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 29908 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 31403 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 378 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 1887 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 3610 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 5101 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 6557 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 8027 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 9534 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 10978 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 12442 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 13894 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 15346 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 16831 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 18284 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 19741 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 21197 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 22659 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 24110 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 25926 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 27476 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 29449 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 30944 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 32378 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 1418 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 2914 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 5694 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 7345 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 8838 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 10286 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 11743 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 13175 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 14215 0.0 0.0 0 0 ? Z úno25 0:00 \_ [smbd] <defunct> > xslaby 15492 0.0 0.0 0 0 ? Z 06:38 0:00 \_ [smbd] <defunct> > xslaby 18349 0.0 0.0 0 0 ? Z 06:53 0:00 \_ [smbd] <defunct> > xslaby 20043 0.0 0.0 0 0 ? Z 07:08 0:00 \_ [smbd] <defunct> > xslaby 21654 0.0 0.0 0 0 ? Z 07:23 0:00 \_ [smbd] <defunct> > xslaby 23364 0.0 0.0 0 0 ? Z 07:38 0:00 \_ [smbd] <defunct> > xslaby 24473 0.0 0.0 0 0 ? Z 07:53 0:00 \_ [smbd] <defunct> > xslaby 26134 0.0 0.0 0 0 ? Z 08:08 0:00 \_ [smbd] <defunct> > xslaby 27373 0.0 0.0 0 0 ? Z 08:23 0:00 \_ [smbd] <defunct> > xslaby 28757 0.0 0.0 0 0 ? Z 08:38 0:00 \_ [smbd] <defunct> > xslaby 29947 0.0 0.0 0 0 ? Z 08:53 0:00 \_ [smbd] <defunct> > xslaby 31154 0.0 0.0 0 0 ? Z 09:08 0:00 \_ [smbd] <defunct> > xslaby 32462 0.0 0.0 0 0 ? Z 09:23 0:00 \_ [smbd] <defunct> > xslaby 1347 0.0 0.0 0 0 ? Z 09:38 0:00 \_ [smbd] <defunct> > xslaby 2581 0.0 0.0 0 0 ? Z 09:53 0:00 \_ [smbd] <defunct> > xslaby 4173 0.0 0.0 0 0 ? Z 10:08 0:00 \_ [smbd] <defunct> > xslaby 5370 0.0 0.0 0 0 ? Z 10:23 0:00 \_ [smbd] <defunct> > xslaby 6652 0.0 0.0 0 0 ? Z 10:38 0:00 \_ [smbd] <defunct> > xslaby 7813 0.0 0.0 0 0 ? Z 10:53 0:00 \_ [smbd] <defunct> > xslaby 9252 0.0 0.0 0 0 ? Z 11:08 0:00 \_ [smbd] <defunct> > xslaby 10823 0.0 0.0 0 0 ? Z 11:23 0:00 \_ [smbd] <defunct> > xslaby 12232 0.0 0.0 0 0 ? Z 11:38 0:00 \_ [smbd] <defunct> > xslaby 13917 0.0 0.0 0 0 ? Z 11:53 0:00 \_ [smbd] <defunct> > xslaby 16442 0.0 0.0 0 0 ? Z 12:08 0:00 \_ [smbd] <defunct> > xslaby 18652 0.0 0.0 0 0 ? Z 12:23 0:00 \_ [smbd] <defunct> They should be reaped when new one starts, IMO. I am using $ qemu-kvm --version QEMU emulator version 3.1.0 from the Virtualization project. But it does not matter, it happens for a long time. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1077154] New: VUL-0: CVE-2018-1000003: pdns-recursor: input validation bugs in DNSSEC validators components
by bugzilla_noreply＠novell.com 29 Mar '22

29 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1077154 Bug ID: 1077154 Summary: VUL-0: CVE-2018-1000003: pdns-recursor: input validation bugs in DNSSEC validators components Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other URL: https://smash.suse.de/issue/198758/ OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: amajer(a)suse.com Reporter: abergmann(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- CVE-2018-1000003 Improper input validation bugs in DNSSEC validators components in PowerDNS version 4.1.0 allow attacker in man-in-the-middle position to deny existence of some data in DNS via packet replay. References: http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-1000003 http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-1000003.html https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-201… -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1118064] New: Firefox 60.3.0 makes openSuse 15.0 hang/freeze
by bugzilla_noreply＠novell.com 26 Mar '22

26 Mar '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1118064 Bug ID: 1118064 Summary: Firefox 60.3.0 makes openSuse 15.0 hang/freeze Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: pierrelud(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Firefox 60.3.0 makes openSuse 15.0 hang/freeze Happens after opening some tabs an surfing a bit. Any support info? Why does openSuse just hang? -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1112361] New: snapper list shows invalid chars in fr_FR.UTF8
by bugzilla_noreply＠novell.com 22 Mar '22

22 Mar '22

http://bugzilla.suse.com/show_bug.cgi?id=1112361 Bug ID: 1112361 Summary: snapper list shows invalid chars in fr_FR.UTF8 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: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The output of 'snapper list' can include invalid chars in fr_FR.UTF8: # LANG=fr_FR.UTF8 snapper ls # | Type | Pre # | Date | Utilisateur | Espace utilisé | Nettoyer | Description | Données utilisateur ----+--------+-------+---------------------------------+-------------+----------------+----------+-----------------------+-------------------- [...] 6* | single | | jeu. 18 oct. 2018 11:07:13 CEST | root | 1�020,00 Kio | | | -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1127188] New: cannot update kernel configuration with cross-compiler
by bugzilla_noreply＠novell.com 22 Mar '22

22 Mar '22

http://bugzilla.suse.com/show_bug.cgi?id=1127188 Bug ID: 1127188 Summary: cannot update kernel configuration with cross-compiler 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- SUSE cross-compilers do not include libc. Some kernel configuration options depend on compiler features including the ability to link userspace binaries. This differs between native compilers and cross-compilers causing different configuration to be generated. The kernel build fails when the configuration changes. -- You are receiving this mail because: You are on the CC list for the bug.

2 18