May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 934495] New: Firefox is in English even when Czech translation is installed and enabled
by bugzilla_noreply＠novell.com 29 Jul '20

29 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=934495 Bug ID: 934495 Summary: Firefox is in English even when Czech translation is installed and enabled Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: vpelcak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello. I have installed MozillaFirefox-translations-common-38.0.6-1.1.x86_64 and enabled Czech language in Add-ons -> Languages. However after start of Firefox it is still in English language. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1022224] New: Mozilla KDE integration does not handle multiple windows correctly
by bugzilla_noreply＠novell.com 29 Jul '20

29 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1022224 Bug ID: 1022224 Summary: Mozilla KDE integration does not handle multiple windows correctly Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- kmozillahelper is only started once per session, therefore multiple windows share a common pipe to talk to it. This is not an issue if only one window uses it as a time (only open a single file dialog, for instance), but there are some other queries that are not triggered by the user and thus can happen at any time. Currently neither firefox nor kmozillahelper handle this case correctly, the protocol needs to be adjusted for this. kmozillahelper has a workaround to only handle one command at a time, but this still allows for race conditions on the firefox side. As a result of this a user needs to close a file dialog before being able to open a downloaded file or open another file dialog. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1029032] New: hardware/flashrom: Operation not permitted and Segmentation fault
by bugzilla_noreply＠novell.com 28 Jul '20

28 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1029032 Bug ID: 1029032 Summary: hardware/flashrom: Operation not permitted and Segmentation fault Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: stepan(a)coresystems.de Reporter: sebix+novell.com(a)sebix.at QA Contact: opensuse-communityscreening(a)forge.provo.novell.com CC: trenn(a)suse.com Found By: --- Blocker: --- To find out the flash chip size of a notebook with libreboot I used `flashrom -p internal -V` as documented here: https://libreboot.org/docs/install/ (search for flashrom -p`) but this fails with multiple errors: > sudo flashrom -p internal -V [sudo] password for root: flashrom v0.9.9-r1955 on Linux 4.10.1-1-default (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.5.1, GCC 6.2.1 20160830 [gcc-6-branch revision 239856], little endian Command line (3 args): flashrom -p internal -V Calibrating delay loop... OS timer resolution is 2 usecs, 1959M loops per second, delay more than 10% too short (got 83% of expected delay), recalculating... 2177M loops per second, 10 myus = 10 us, 100 myus = 92 us, 1000 myus = 927 us, 10000 myus = 9095 us, 8 myus = 9 us, OK. Initializing internal programmer Found candidate at: 00000500-00000510 Found coreboot table at 0x00000500. Error accessing high tables, 0x100000 bytes at 0x00000000bdaac000 /dev/mem mmap failed: Operation not permitted Failed getting access to coreboot high tables. Using Internal DMI decoder. Error accessing DMI Table, 0x1000 bytes at 0x00000000bdab4000 /dev/mem mmap failed: Operation not permitted Segmentation fault Is it impossible to use flashrom on OpenSUSE? -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1078447] New: lcov and kernel-coverage issue in Leap 15
by bugzilla_noreply＠novell.com 27 Jul '20

27 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1078447 Bug ID: 1078447 Summary: lcov and kernel-coverage issue in Leap 15 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: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- During try to get kernel-coverage to Leap 15, we see a conflict problem, in lconv it was Conflicts: kernel-coverage < 0.1-49 , however we built all leap binary had prefix lp150 in the release number, eg lp150.74.1, therefor kernel-coverage is uninstallable. can't install kernel-coverage-0.1-lp150.74.1.noarch: package kernel-coverage-0.1-lp150.74.1.noarch requires lcov, but none of the providers can be installed package lcov-1.13-lp150.1.6.noarch conflicts with kernel-coverage < 0.1-49 provided by kernel-coverage-0.1-lp150.74.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1098041] New: bcm43xx-firmware incompatible with transactional-update
by bugzilla_noreply＠novell.com 27 Jul '20

27 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1098041 Bug ID: 1098041 Summary: bcm43xx-firmware incompatible with transactional-update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: afaerber(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kubic for RPi3 does not enable WiFi, as the used /usr/sbin/install-brcmfmac tries to write to a read-only file system. I suggest to use bind mounts of those files instead of symlinks, would that work? Or alternatively, link from /lib/firmware/brcm/...txt to /var/... inside the package and create the link inside /var/... in the script. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1132532] New: /usr/bin/xdg-open wants to open /usr/bin/pcmanfm but there is just /usr/bin/pcmanfm-qt
by bugzilla_noreply＠novell.com 27 Jul '20

27 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1132532 Bug ID: 1132532 Summary: /usr/bin/xdg-open wants to open /usr/bin/pcmanfm but there is just /usr/bin/pcmanfm-qt Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: mvetter(a)suse.com Reporter: holgi(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a Leap 15.1 LXQT environment: xdg-open from xdg-utils RPM wants to open /usr/bin/pcmanfm but not there is just /usr/bin/pcmanfm-qt So we either need a symlink pcmanfm -> pcmanfm-qt or xdg-open needs to check if it needs to call the one or the other. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1049703] New: llvm built with unsupported BUILD_SHARED_LIBS
by bugzilla_noreply＠novell.com 24 Jul '20

24 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1049703 Bug ID: 1049703 Summary: llvm built with unsupported BUILD_SHARED_LIBS 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: jslaby(a)suse.com QA Contact: qa-bugs(a)suse.de CC: idonmez(a)suse.com, mpluskal(a)suse.com Found By: --- Blocker: --- This causes issues with e.g. klee's cmake system: https://github.com/klee/klee/pull/686 LLVM docs says: BUILD_SHARED_LIBS is only recommended for use by LLVM developers. If you want to build LLVM as a shared library, you should use the LLVM_BUILD_LLVM_DYLIB option. See more at: https://github.com/klee/klee/pull/686#issuecomment-316741224 -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1021577] New: llvm 3.9.1 made some icons red
by bugzilla_noreply＠novell.com 24 Jul '20

24 Jul '20

http://bugzilla.suse.com/show_bug.cgi?id=1021577 Bug ID: 1021577 Summary: llvm 3.9.1 made some icons red 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: glin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After upgrading LLVM to 3.9.1, some icons in the system tray turned red. This only happened in the system using the open source AMD GPU driver. The upstream bugs: https://bugs.freedesktop.org/show_bug.cgi?id=99078 https://llvm.org/bugs/show_bug.cgi?id=31722 Some distro like gentoo reverted this patch to stop the detect: https://github.com/llvm-mirror/llvm/commit/c280d74837d8239fc6cf567576b766ca… -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1097602] New: Plasma Wayland: kate or notepad do not open txt file from dolphin but do so if called seperately
by bugzilla_noreply＠novell.com 23 Jul '20

23 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1097602 Bug ID: 1097602 Summary: Plasma Wayland: kate or notepad do not open txt file from dolphin but do so if called seperately Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- create a txt file and save it in, e.g. /home/"user" whatever it may be called. In a plasma-wayland session, try to open Dolphin to visualize the file. click on it and select "open with kate" or "open with notepad". Nothing happens. Try open with libreoffice (opens but the first instance will silently crash and immediately open again, working and displaying correctly the file. I then tried to open from the start menu a virgin kate or a virgin notepad. These do open. >From inside the program it is normally possible to open the aforementioned file without problems. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1094761] New: Kiwi does not produce ISO that are compliant with the ISO9660 specs
by bugzilla_noreply＠novell.com 23 Jul '20

23 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1094761 Bug ID: 1094761 Summary: Kiwi does not produce ISO that are compliant with the ISO9660 specs 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: pete(a)akeo.ie QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As per the following analysis by Thomas Schmitt, who investigated an error report reported against libcdio when trying to process openSUSE-Leap-15.0-DVD-x86_64.iso: http://lists.gnu.org/archive/html/libcdio-devel/2018-05/msg00008.html Specifically: ECMA-119, 7.3.3 "Both-byte orders" and 9.1.4 "Data Length (BP11 to BP18)" prescribe that the byte count of a data file is to be recorded as first a little-endian 32-bit number and then a big-endian 32-bit number. However, Kiwi only appears to patch the little-endian bytes into the ISO when it sets the final size of the affected files. For instance, you can find a file in openSUSE-Leap-15.0 that bears as size: e1 01 00 00 00 00 08 00 where the first four bytes are correct and the next four are wrong. This is probably because only the first four were overwritten by Kiwi, when it patched in the new size after manipulating the file content. Therefore, independently of a separate libcdio issue (which should gracefully warn when it finds such an inconsistency, rather than bail out), there is a definite problem with the way Kiwi updates the file sizes, as only seems to do half the job, which is in breach of the ECMA specs. Hopefully this specs compliance issue can be fixed for future releases of openSUSE. -- You are receiving this mail because: You are on the CC list for the bug.

2 9