January 2019 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 1027448] New: Please use key release event for bracket completion plugin
by bugzilla_noreply＠novell.com 15 Dec '21

15 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1027448 Bug ID: 1027448 Summary: Please use key release event for bracket completion plugin Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: hillwoodroc(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 715892 --> http://bugzilla.opensuse.org/attachment.cgi?id=715892&action=edit bracketcompletion: use key release event to work with input method From: bgo#778737 https://bugzilla.gnome.org/show_bug.cgi?id=778737 Some user reported that ibus-libpinyin/ibus-pinyin doesn't work with gedit plugin bracket completion. I tried to modify the gedit plugin code, it seems work now. Please review it, thanks! How to reproduce it: 1. Switch to C/C++ mode, press "(", bracket completion works. 2. Switch input method to "Intelligent Pinyin" or "Pinyin", it doesn't work. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1098245] New: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
by bugzilla_noreply＠novell.com 14 Dec '21

14 Dec '21

http://bugzilla.suse.com/show_bug.cgi?id=1098245 Bug ID: 1098245 Summary: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: jmader2(a)gmu.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- starting `gnome-session` there is the console message, gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used I am currently working around this with, setcap cap_ipc_lock=+ep /usr/bin/gnome-keyring-daemon -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1002875] New: plymouth boot splash not working in tumbleweed
by bugzilla_noreply＠novell.com 12 Dec '21

12 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1002875 Bug ID: 1002875 Summary: plymouth boot splash not working in tumbleweed 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: cristian_anita(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi All, I recently made a fresh install of Tumbleweed 20160924 and plymouth splash screen does not appear at startup (only blinking cursor between grub2 and sddm) and shutdown (only some message about watchdog). plymouth-0.9.2-2.4 plymouth-branding-openSUSE-13.3-4.3 grub2-2.02~beta3-11.1 Same with latest TW update (20161003) Regards, Cristian ANITA -- You are receiving this mail because: You are on the CC list for the bug.

2 111

[Bug 972787] New: [gpg-agent] Rework agent startup for DM sessions.
by bugzilla_noreply＠novell.com 01 Dec '21

01 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=972787 Bug ID: 972787 Summary: [gpg-agent] Rework agent startup for DM sessions. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: eich(a)suse.com QA Contact: qa-bugs(a)suse.de CC: astieger(a)suse.com, meissner(a)suse.com, premysl.janouch(a)suse.com, werner(a)suse.com, xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Development Blocker: --- The gpg-agent for a user session is started by the script /etc/X11/xdm/sys.xsession. An openSUSE user pointed out to me that the socket handling of the gpg-agent has changed with gpg 2.1 - now neither a env file is written (the option --write-env-file is ignored) nor nor does anything use the env variable GPG_AGENT_INFO. Instead today a standard socket is used in $HOME/.gnupg/S.gpg-agent. Also check: https://gnupg.org/faq/whats-new-in-2.1.html If NFS mounted homes are desired, it can be handled as described in: https://wiki.gnupg.org/NFS This requires reworking of the gpg-agent startup (and possibly also of the ssh-agent) in sys.xsession. Any takers? -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1099755] New: /etc/hosts.allow /etc/hosts.deny not support ssh
by bugzilla_noreply＠novell.com 01 Dec '21

01 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1099755 Bug ID: 1099755 Summary: /etc/hosts.allow /etc/hosts.deny not support ssh Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: simon(a)becherer.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- wrong security feeling, because text of file /etc/hosts.allow is wrong. written is: # /etc/hosts.allow # See 'man tcpd' and 'man 5 hosts_access' for a detailed description # of /etc/hosts.allow and /etc/hosts.deny. # # short overview about daemons and servers that are built with # tcp_wrappers support: #. # package name | daemon path | token # ---------------------------------------------------------------------------- # ssh, openssh | /usr/sbin/sshd | sshd, sshd-fwd-x11, sshd-fwd-<port> # quota | /usr/sbin/rpc.rquotad | rquotad # tftpd | /usr/sbin/in.tftpd | in.tftpd # portmap | /sbin/portmap | portmap at least toke sshd to allow and deny will not work any more on actual systems (tumbleweed). (maybe others tokens also affected) so user (as i) with low background knowlidge will feel secure if they make settings like: sshd : ALL : deny sshd : 127.0.0.1 : allow sshd : 192.168.0.30 : allow but the system ignores this. -> leading text and maybe manpage has to be changed! -> or if this 2 files host.allow / hosts.deny ar complete obsolete, do not install it at all. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1087860] New: wine repeatedly asks to install wine-mono even though the package wine-mono was installed
by bugzilla_noreply＠novell.com 29 Nov '21

29 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1087860 Bug ID: 1087860 Summary: wine repeatedly asks to install wine-mono even though the package wine-mono was installed Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: http://lord.arch/tests/737/modules/wine/steps/26 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: meissner(a)suse.com Reporter: okurz(a)suse.com QA Contact: okurz(a)suse.com Found By: --- Blocker: --- ## Observation After installing packages "wine" and "wine-mono" explicitly on openSUSE Leap build 184.1 and calling wine on even a trivial Windows program a dialog pops up to download and install a "wine-mono" package which should be there already. This can now also be reproduced in an openQA test: scenario opensuse-15.0-DVD-x86_64-wine@64bit in [wine](http://lord.arch.suse.de/tests/737/modules/wine/steps/26) ## Reproducible Every time on a clean installation of wine on openSUSE Leap 15.0 and I think just the same on openSUSE Tumbleweed. Might also be on openSUSE Leap 42.3 but I am not sure about this. ## Expected result There should be no question for wine-mono installation if the system package is alread installed OR a better description of the system package describing what it is actually used for. I think the problem is that even if someone would answer "yes" to the question to install the internal (non-openSUSE) wine-mono package the next time the question pops up again but I'm not 100% sure on this. ## Further details Always latest result in this scenario: [latest](http://lord.arch/tests/latest?arch=x86_64&test=wine&machine=64bit&flavor=DVD&version=15.0&distri=opensuse) -- You are receiving this mail because: You are on the CC list for the bug.

2 3