November 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1084804] New: Plasma + Wayland: input method does not start
by bugzilla_noreply＠novell.com 19 Jan '22

19 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1084804 Bug ID: 1084804 Summary: Plasma + Wayland: input method does not start Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ftake(a)geeko.jp QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On Plasma + Wayland session, input method like IBus, Fcitx does not start anymore. This is simply because /etc/X11/xim, which has been a script to launch one of input methods, is not executed on a Wayland session. So we need to update our input method launcher script to support Wayland. How can we do that? What is the right way to set environment variables such as GTK_IM_MODULE and QT_IM_MODULE according to the current selected input method under on Wayland session? Workaround: Set GTK_IM_MODULE and QT_IM_MODULE in ~/.i18n and start ibus-daemon -xd or fcitx by using KDE auto start settings. However, both IBus and Fcitx will not work correctly due to other bugs and limitations related to Wayland. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1047498] New: gnuhealth not installable
by bugzilla_noreply＠novell.com 17 Jan '22

17 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1047498 Bug ID: 1047498 Summary: gnuhealth not installable Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: axel.braun(a)gmx.de, okurz(a)suse.com Found By: --- Blocker: --- Found by openQA (https://openqa.opensuse.org/tests/441262#step/gnuhealth_install/12) and confirmed by installcheck: can't install gnuhealth-3.2.0-1.1.noarch: nothing provides python3-caldav needed by gnuhealth-3.2.0-1.1.noarch nothing provides python3-cracklib needed by gnuhealth-3.2.0-1.1.noarch nothing provides python3-pyBarcode needed by gnuhealth-3.2.0-1.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 966599] New: home:j-engel/bacula: Bug
by bugzilla_noreply＠novell.com 15 Jan '22

15 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=966599 Bug ID: 966599 Summary: home:j-engel/bacula: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: jcnengel(a)gmail.com Reporter: marc(a)marcchamberlin.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Tried to download/install Bacula 7.4.0 using the 1 click installer and downloading the RPM package. I get the following error - nothing provides libbaccats-7.4.0.so()(64bit) needed by bacula-7.4.0-6.2.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 940478] New: ASL: rename conflicting-confusing package
by bugzilla_noreply＠novell.com 14 Jan '22

14 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=940478 Bug ID: 940478 Summary: ASL: rename conflicting-confusing package Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: All OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: alinm.elena(a)gmail.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE:Factory already has an "asl" package, and recently gained an "ASL" package. This very same name is, I will argue, confusing for both users and developers, as they only differ in case, and case is not something people pay sufficient attention to when e.g. reporting bugs or discussing. I suggest to rename the ASL package. Considering that "asl library" yields lots of different things on Google already, a package name like "advsimlib" might work better than "asllib". Confer with the asl.org.il team perhaps. [ The current plan is to reject, in the direct future, same-name submissions to Factory which only differ in casing. On a related notem, libzypp even falls over currently (but probably intentionally; see bug #940477). ] -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1089434] New: enchant-2 voikko backend installed but not hunspell backend despite en.GB language settings
by bugzilla_noreply＠novell.com 13 Jan '22

13 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1089434 Bug ID: 1089434 Summary: enchant-2 voikko backend installed but not hunspell backend despite en.GB language settings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This must have happened fairly recently, but I noticed only after finding every English word marked in red when composing emails. Apparently, enchant-2 does not automatically install the hunspell backend despite one's locale setting being set to en.GB. The voikko backend is installed, however, thus automatically treating all spell-checking inputs as Finnish (and marking them obviously). Manually installing enchant-2-backend-hunspell did the trick, since the correct myspell dicts were already installed. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1116225] New: qemu ALSA backend broken
by bugzilla_noreply＠novell.com 05 Jan '22

05 Jan '22

http://bugzilla.suse.com/show_bug.cgi?id=1116225 Bug ID: 1116225 Summary: qemu ALSA backend broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KVM Assignee: kvm-bugs(a)forge.provo.novell.com Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It seems that qemu ALSA backend is broken. When I start an audio playback on VM, the whole VM including GUI stalls. Tested qemu 3.0.0 with qemu-audio-alsa package. Switching to PA backend seems working, so this might be specific to the audio backend. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1060506] New: libkolabxml packages differ for every build
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1060506 Bug ID: 1060506 Summary: libkolabxml packages differ for every build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: lbeltrame(a)kde.org Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: matthias(a)mailaender.name Found By: Development Blocker: --- When working on the reproducible builds project for openSUSE I found that libkolabxml packages differ for every build unless ASLR is disabled in the build system. This indicates either usage of unitinialized memory (compare [1]) or using (randomized) pointers in output. /usr/lib64/libkolabxml.so.1.1.6 differs because of /home/abuild/rpmbuild/BUILD/libkolabxml-1.1.6/build/kolabformat-xcal-schema.cxx 2018-10-30 08:42:53.622040000 +0000 @@ -9014,9 +9014,9 @@ 0x00, 0x01, 0x6d, 0x09, 0x00, 0x01, 0x3f, 0x07, 0x00, 0x01, 0x23, 0x07, 0x00, 0x01, 0x53, 0x0a, 0x00, 0x01, 0x68, 0x07, 0x00, 0x01, 0x7f, 0x09, 0x00, 0x01, 0x4e, 0x04, 0x00, 0x01, 0xfe, 0xff, 0xff, 0xff, 0x1d, 0x00, - 0x06, 0x0e, 0x00, 0x06, 0xe8, 0x08, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, + 0x06, 0x0e, 0x00, 0x06, 0x25, 0x07, 0x00, 0x01, 0xff, 0xff, 0xff, 0xff, 0x00, 0x03, 0x0c, 0x00, 0x06, 0x58, 0x53, 0x41, 0x6e, 0x6e, 0x6f, 0x74, - 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x03, 0x11, 0x09, 0x00, 0x05, 0x3c, + 0x61, 0x74, 0x69, 0x6f, 0x6e, 0x00, 0x03, 0xb6, 0x01, 0x00, 0x05, 0x3c, 0x00, 0xff, 0x78, 0x73, 0x3a, 0x61, 0x6e, 0x6e, 0x6f, 0x74, 0x61, 0x74, [...] which probably comes from # Compile Schemas add_custom_command(OUTPUT kolabformat-xcal-schema.cxx COMMAND ${XSDBIN} --verbose --array-name iCalendar_schema --output-dir ${CMAKE_BINARY_DIR} ${SCHEMAS} which might be from ./compiled/xsdbin.cxx and/or involving the xsd package [1] https://build.opensuse.org/package/view_file/M17N/gcin/gcin-reproducible.pa… -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1061219] New: trackerbug: packages do not build reproducibly from including uninitialized memory
by bugzilla_noreply＠novell.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1061219 Bug ID: 1061219 Summary: trackerbug: packages do not build reproducibly from including uninitialized memory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Other Assignee: bwiedemann(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Development Blocker: --- See also https://reproducible-builds.org/ When packages write uninitialized memory into files that are packaged it results in binaries that differ on every build. These thus trigger rebuilds of depending packages and are published to mirrors and users when actually nothing really changed. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1101756] New: enable specification of custom GRUB_DISTRIBUTOR= in UEFI bootloader installation
by bugzilla_noreply＠novell.com 31 Dec '21

31 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1101756 Bug ID: 1101756 Summary: enable specification of custom GRUB_DISTRIBUTOR= in UEFI bootloader installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mrmazda(a)earthlink.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 777382 --> http://bugzilla.opensuse.org/attachment.cgi?id=777382&action=edit 15.0 y2logs from host ab250 YaST2 currently offers no opportunity to specify a custom name to facilitate multiboot hosts. It needs one. Because it does not, e.g. when installation of Leap follows installation of Tumbleweed, the previous UEFI configuration is destroyed. The BIOS boot manager may or may not accommodate a proper selection of the preferred choice from the EFI/ESP partition. In the Leap follows TW case I just tried with an Asus B250M-C/CSM Kaby Lake motherboard with AMI BIOS version 1205 of 2018-05-11, the BIOS did not. As I normally do during installation, I deselected probe foreign OS. In attempting to avoid this overwrite, during installation of 15.0 I used vi to edit /mnt/etc/default/grub to include GRUB_DISTRIBUTOR="opensuse150". Actual bootloader installation at the end of overall installation changed it to GRUB_DISTRIBUTOR=, with the result that next boot only offered 15.0 to the exclusion of TW's /boot/grub2/custom.cfg which contains the custom stanzas for the other installed distros. I was forced to "choose" only 15.0 at next boot. I did work around that by using e on the 15.0 stanza to specify the TW kernel and initrd. Current EFI boot configuration: # efibootmgr BootCurrent: 0000 BootOrder: 0000,0001,0002 Boot0000* opensuse Boot0001* debian Boot0002* UEFI OS Expected EFI boot configuration subsequent to 15.0 installation was: # efibootmgr BootCurrent: 0000 BootOrder: 0000,0001,0002,0003,0004 Boot0000* opensuseTW Boot0001* debian Boot0002* ubuntu Boot0003* opensuse150 Boot0004* UEFI OS -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1109968] New: Daisy chained DisplayPort v1.2 screens randomly doesn't resume
by bugzilla_noreply＠novell.com 31 Dec '21

31 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1109968 Bug ID: 1109968 Summary: Daisy chained DisplayPort v1.2 screens randomly doesn't resume Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: jkohoutek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When resuming from blank power saving, sometimes some of the displays connected trough Daisy chained DisplayPort v1.2 doesn't resume. Which one of the display doesn't wake up is random. GPU: Intel® HD Graphics 520 (Skylake GT2) Displays: 2x 1920x1080 Dell U2414H -- You are receiving this mail because: You are on the CC list for the bug.

2 7