May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1132953] New: Can not eject media, the button is overwritten
by bugzilla_noreply＠novell.com 14 Feb '20

14 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1132953 Bug ID: 1132953 Summary: Can not eject media, the button is overwritten Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 803305 --> http://bugzilla.opensuse.org/attachment.cgi?id=803305&action=edit Photo of problem See attached photo -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1132255] New: Xfce panel doesn’t hide
by bugzilla_noreply＠novell.com 14 Feb '20

14 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1132255 Bug ID: 1132255 Summary: Xfce panel doesn’t hide Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: ivo.grimaldi(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- xfce panel setting as intelligently or hide always, doesn't hide and a full screen window goes down the panel. 1. Right click on panel and select properties 2. set up intelligently or hide always 3. save and close 4. open full screen a program 5. see window goes down the panel, and panel doesn't hide a possible solution open a terminal sudo killall xfce4-panel xfce4-panel & or xfce4-panel -r -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1135127] New: Error with xfce4-display-settings
by bugzilla_noreply＠novell.com 14 Feb '20

14 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1135127 Bug ID: 1135127 Summary: Error with xfce4-display-settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Macintosh OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: andres(a)otondo.cl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I just installed OpenSuse Tumbleweed, and when I try to open the xfce4-display-settings it show this error No protocol specified (xfce4-display-settings:5262): xfce4-display-settings-CRITICAL **: 21:50:37.044: xfce_randr_mode_width: assertion 'mode != NULL' failed (xfce4-display-settings:5262): xfce4-display-settings-CRITICAL **: 21:50:37.044: xfce_randr_mode_height: assertion 'mode != NULL' failed Segmentation fault (core dumped). My hardware is a Macbook Pro mid 2012 with an LG external screen connected trough VGA. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1084015] New: Include fixes from en_US "translation" to sources
by bugzilla_noreply＠novell.com 13 Feb '20

13 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1084015 Bug ID: 1084015 Summary: Include fixes from en_US "translation" to sources Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: sbrabec(a)suse.com QA Contact: jsrain(a)suse.com CC: locilka(a)suse.com, padraig.dillon(a)microfocus.com Found By: --- Blocker: --- Created attachment 762751 --> http://bugzilla.opensuse.org/attachment.cgi?id=762751&action=edit problems in en_US In past, strings were fixed in RC phase by introduction of and en_US translation. It was expected, that it will be incorporated back to the code after release. Years passed, and it did not happen. Some of these hotfixes are 16 years old. Now we have a bunch of strange en_US "translations" that needs to be reviewed and included. It consist of: 1. English typo and stylistic fixes. These should be included, and existing translations to other languages updated to keep them. Example: https://github.com/yast/yast-autoinstallation/blob/f93f318b744c21557201c278… en_US changed "Frametitle" to "Frame Title". All existing translations are probably OK. To keep existing translations, it requires coordinated merge of these changes and translation updates. 2. Formatting fixes. The good: English is OK. The bad: All translators translated the source string, not the fixed en_US string. With a bit of luck, it is possible to mass fix translations. Example: https://github.com/yast/yast-add-on/blob/0c44e966702b0aefc2439eb0da384260a4… en_US removed the trailing "\n" All translations have incorrect formatting. 3. Formatting fixes that change meaning of the string. The good: English is OK. The bad: All translators translated the source string with the incorrect meaning, not the fixed en_US string. Example: https://github.com/yast/yast-apparmor/blob/afd62f82724f750d7af850f60f6d52a2… en_US made a question from the sentence. All translators translated the source string, not the fixed en_US string. Impact on the translation meaning is unknown. 4. Hot fixes of apparent nonsense. All translators translated the source string, not the fixed en_US string. With a bit of luck, it is possible to mass fix translations. Example: https://github.com/yast/yast-apparmor/blob/afd62f82724f750d7af850f60f6d52a2… en_US removed the nonsense "? " at the beginning. Translators were not aware that "? " is a mistake, and used it in the translations. And finally, en_GB mixes all the above plus: 5. Changes for British English. As nobody actively maintains en_GB, it causes very strange result: I an few strings, AppArmor is called AppArmour, in all other "untranslated" strings, AppArmor is the name. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1117074] New: aws-cli missing autocompletion after install
by bugzilla_noreply＠novell.com 10 Feb '20

10 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1117074 Bug ID: 1117074 Summary: aws-cli missing autocompletion after install Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- aws-cli package contains scripts for autocompletion, but install these scripts is missing. I need to set them manually. It looks like bug, git has autocompletion right after package install. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 966255] New: System does not boot
by bugzilla_noreply＠novell.com 09 Feb '20

09 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 Bug ID: 966255 Summary: System does not boot Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: rjschwei(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- kernel 4.4.0.3 Has encrypted user partition. Hangs at Ignoring BGRT: Invalid version 0 (expected 1) This appears to happen right before the point where I would expect to enter my passphrase. -- You are receiving this mail because: You are on the CC list for the bug.

1 34

[Bug 1107525] New: Raise default file descriptor limits to meet Valve Proton requirements
by bugzilla_noreply＠novell.com 08 Feb '20

08 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1107525 Bug ID: 1107525 Summary: Raise default file descriptor limits to meet Valve Proton requirements Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Valve released beta version of Proton / Steam play. Next Leap 15.1 should meet minimal requirements. One of them is file descriptor limits: https://github.com/zfigura/wine/blob/esync/README.esync "If you get something like "eventfd: Too many open files" and then things start crashing, you've probably run out of file descriptors. esync creates one eventfd descriptor for each synchronization object, and some games may use a large number of these. Linux by default limits a process to 4096 file descriptors, which probably was reasonable back in the nineties but isn't really anymore. (Fortunately Debian and derivatives [Ubuntu, Mint] already have a reasonable limit.)" -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1110722] New: pocl uses compile-time CPU detection
by bugzilla_noreply＠novell.com 08 Feb '20

08 Feb '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1110722 Bug ID: 1110722 Summary: pocl uses compile-time CPU detection Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Major Priority: P5 - None Component: Development Assignee: osukup(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: mpluskal(a)suse.com Blocks: 1100677 Found By: Development Blocker: --- Steps to Reproduce: osc co Factory/pocl && cd $_ osc build --no-service --vm-type=kvm --build-opt=--vm-custom-opt="-cpu qemu64" +compare result to one without build-opt using /usr/lib/build/pkg-diff.sh $rpm1 $rpm2 Was previously solved with https://build.opensuse.org/request/show/626138 /usr/lib64/libpocl.so.2.2.0 differs in assembler output --- /tmp/tmp.3iZr1DZRz5/tmp.MomrQD5u2D 2018-09-26 04:41:09.682694138 +0000 +++ /tmp/tmp.3iZr1DZRz5/tmp.3XC0iGKeQV 2018-09-26 04:41:09.750694493 +0000 @@ -93827,10 +93827,10 @@ lea offset(%rsp),%rdi lea offset(%rsp),%rsi callq <_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_assignERKS4_@plt> - mov %r12,%rax - sub offset(%rsp),%rax - cmp $something,%rax - jbe <_ZL14kernel_libraryP13_cl_device_id + ofs> + mov offset(%rsp),%rax + or $something,%rax + cmp %r12,%rax + je <_ZL14kernel_libraryP13_cl_device_id + ofs> lea offset(%rip),%rsi # <supported_image_formats + ofs> In the build-root I can see: /home/abuild/rpmbuild/BUILD/pocl-1.2/build/CMakeCache.txt 2033-10-28 17:46:42.015636815 +0000 @@ -411,7 +411,7 @@ LINK_COMMAND:FILEPATH=/usr/bin/ld //The Host CPU to use with llc -LLC_HOST_CPU:STRING=haswell +LLC_HOST_CPU:STRING=pentium2 //LLVM assembler LLVM_AS:FILEPATH=/usr/bin/llvm-as @@ -837,7 +837,7 @@ Hwloc_hwloc_PREFIX:INTERNAL= Hwloc_hwloc_VERSION:INTERNAL= //Autodetected CPU -LLC_HOST_CPU_AUTO:INTERNAL=haswell +LLC_HOST_CPU_AUTO:INTERNAL=pentium2 might be an upstream pocl bug, where the result of CPU detection accidentally gets used during build -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1068707] New: bcache broken on s390x
by bugzilla_noreply＠novell.com 08 Feb '20

08 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1068707 Bug ID: 1068707 Summary: bcache broken on s390x Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- trying to repeat on s390x what worked on aarch64 ... OBS_WORKER_DISK=/dev/mapper/3600a098051764b2d515d436d66416b4f wipefs -f -a $OBS_WORKER_DISK modprobe zram num_devices=1 modprobe bcache echo 8G > /sys/block/zram0/disksize wipefs -f -a /dev/zram0 make-bcache --wipe-bcache --block 4k --bucket 2M -B $OBS_WORKER_DISK -C /dev/zram0 # up to here it seemed to work, but: echo /dev/zram0 > /sys/fs/bcache/register -bash: echo: write error: Invalid argument in dmesg: [1256250.924470] zram: Added device: zram0 [1256258.363017] zram0: detected capacity change from 0 to 8589934592 [1256269.146000] bcache: register_bcache() error opening /dev/dm-2: Not a bcache superblock [1256275.462897] bcache: register_bcache() error opening /dev/zram0: Not a bcache superblock so the written superblock is not recognized ... endianess issue ? -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1105173] New: cmis-client - Fails to build with Boost 1.68.0
by bugzilla_noreply＠novell.com 07 Feb '20

07 Feb '20

http://bugzilla.suse.com/show_bug.cgi?id=1105173 Bug ID: 1105173 Summary: cmis-client - Fails to build with Boost 1.68.0 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: tchvatal(a)suse.com Reporter: amajer(a)suse.com QA Contact: qa-bugs(a)suse.de CC: cbosdonnat(a)suse.com Blocks: 1105081 Found By: --- Blocker: --- New Boost library has been released and unfortunately this package fails to build with it. The new boost library is soon submitted to devel:libraries:c_c++/boost and will be submitted to openSUSE:Factory shortly. https://build.opensuse.org/package/show/home:adamm:boost_test/cmis-client [ 163s] xml-utils.cxx:34:10: fatal error: boost/uuid/sha1.hpp: No such file or directory [ 163s] #include <boost/uuid/sha1.hpp> [ 163s] ^~~~~~~~~~~~~~~~~~~~~ [ 163s] compilation terminated. This is caused by removal of compatibility SHA1 header from Uuid boost library. -- You are receiving this mail because: You are on the CC list for the bug.

1 13