June 2019 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 1060111] New: bash: have: command not found
by bugzilla_noreply＠novell.com 30 Dec '21

30 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1060111 Bug ID: 1060111 Summary: bash: have: command not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: matthias(a)mailaender.name QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just encountered this in openSUSE Tumbleweed where every terminal displays > bash: have: command not found upon startup. http://www.jerous.org/2016/09/19/bash-have-not-found describes the problem and proposes a solution. I don't know if it is the correct approach. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1136292] New: ktorrent don't find the file "http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz"
by bugzilla_noreply＠novell.com 22 Dec '21

22 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1136292 Bug ID: 1136292 Summary: ktorrent don't find the file "http://geolite.maxmind.com/download/geoip/database/Ge oLiteCountry/GeoIP.dat.gz" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: x3.141592(a)yahoo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 805988 --> http://bugzilla.opensuse.org/attachment.cgi?id=805988&action=edit ktorrent message Please see the attachment. I get this message when I start ktorrent. -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 937067] New: efi=1 does not seem to work anymore
by bugzilla_noreply＠novell.com 17 Dec '21

17 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=937067 Bug ID: 937067 Summary: efi=1 does not seem to work anymore Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: kukuk(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- In the past, you could add efi=1 as argument for the installer, and your system was setup for EFI boot, even if the detection fails. This works only partly with Tumbleweed 20150630: the bootloader still installs and configures grub2-x86_64-efi, but the storage proposal does not create a vfat /boot/EFI partition anymore. This works with SLES12, haven't tested openSUSE 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1138031] New: [trackerbug] Initial LXD submission (3.13)
by bugzilla_noreply＠novell.com 16 Dec '21

16 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1138031 Bug ID: 1138031 Summary: [trackerbug] Initial LXD submission (3.13) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: asarai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tracking bug for the submission of LXD 3.13 to Leap. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 997918] New: TW 20160901: unable to dup since docker-compose conflicts with python-requests
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=997918 Bug ID: 997918 Summary: TW 20160901: unable to dup since docker-compose conflicts with python-requests Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: robert.munteanu(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: fcastelli(a)suse.com Found By: --- Blocker: --- Another iteration of bug #984309 Problem: docker-compose-1.7.1-2.2.noarch conflicts with python-requests >= 2.11 provided by python-requests-2.11.1-1.1.noarch Solution 1: deinstallation of docker-compose-1.7.1-2.2.noarch Solution 2: keep obsolete python-requests-2.10.0-3.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1072403] New: [Build 20171211] openQA test fails in docker_compose
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1072403 Bug ID: 1072403 Summary: [Build 20171211] openQA test fails in docker_compose Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: http://openqa.opensuse.org/tests/557372/modules/docker _compose/steps/14 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_in_textmode@64bit fails in [docker_compose](http://openqa.opensuse.org/tests/557372/modules/docker_comp… ## Reproducible Fails since (at least) Build [20170428](http://openqa.opensuse.org/tests/395051) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](http://openqa.opensuse.org/tests/latest?test=extra_tests_in_textmod… docker-compose is no longer installable, as python-texttable has been updated to version 1.1.1 (from 0.8.3) in sr 555176 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1062084] New: docker-compose broken because of python-docker-py
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1062084 Bug ID: 1062084 Summary: docker-compose broken because of python-docker-py Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: jc(a)phocean.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Docker-compose broke after the last update, because of a broken dependancy on python-docker-py. % sudo zypper in docker-compose Chargement des données du dépôt... Lecture des paquets installés... Résolution des dépendances des paquets... Problème : rien ne fournit python-docker-py >= 1.10.3, qui est requis par docker-compose-1.8.1-1.2.noarch Solution 1 : ne pas installer docker-compose-1.8.1-1.2.noarch Solution 2 : casser docker-compose-1.8.1-1.2.noarch en ignorant certaines de ses dépendances % zypper info python-dockerpty Chargement des données du dépôt... Lecture des paquets installés... Informations sur paquet python-dockerpty : ------------------------------------------ Dépôt : openSUSE:Tumbleweed Nom : python-dockerpty Version : 0.4.1-1.3 Arch : noarch Fabricant : openSUSE Taille une fois installé : 78,6 KiB installé : Non État : non installé Paquet source : python-dockerpty-0.4.1-1.3.src Résumé : Docker API Client Description : Provides the functionality needed to operate the pseudo-tty (PTY) allocated to a docker container, using the Python client. % zypper info docker-compose Chargement des données du dépôt... Lecture des paquets installés... Informations sur paquet docker-compose : ---------------------------------------- Dépôt : openSUSE:Tumbleweed Nom : docker-compose Version : 1.8.1-1.2 Arch : noarch Fabricant : openSUSE Taille une fois installé : 512,9 KiB installé : Non État : non installé Paquet source : docker-compose-1.8.1-1.2.src Résumé : Define and run complex applications using Docker Description : Compose is a tool for defining and running complex applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running. Compose is great for development environments, staging servers, and CI. We don't recommend that you use it in production yet. Previously known as Fig. -- You are receiving this mail because: You are on the CC list for the bug.

2 23

[Bug 1004927] New: Upgrade to docker-compose 1.8.1
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1004927 Bug ID: 1004927 Summary: Upgrade to docker-compose 1.8.1 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Docker in Leap 42.2 was updated to 1.12, but docker-compose, which can use new capabilities stuck on version 1.6.1. Please update docker-compose too. -- You are receiving this mail because: You are on the CC list for the bug.

2 3