January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 996088] New: After updates today (29/08/16) efibootmgr: Could not set BootOrder: No space left on device
by bugzilla_noreply＠novell.com 28 Jan '22

28 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=996088 Bug ID: 996088 Summary: After updates today (29/08/16) efibootmgr: Could not set BootOrder: No space left on device Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: stuart(a)stella-maris.org.uk QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After performing an update today, 29/08/16, I decided to run efibootmgr -v as I have had issues before. I then found it returned BootCurrent: 0003 Timeout: 1 seconds No BootOrder is set; firmware will attempt recovery Boot0000* opensuse HD(1,GPT,2eca2750-fed6-4e3f-887f-27f183020fda,0x800,0x61800)/File(\EFI\opensuse\grubx64.efi) Boot0001* Hard Drive BBS(HD,,0x0) Boot0002* CD/DVD Drive BBS(CDROM,,0x0) After which I ran efibootmgr -o 0000,0001,0002 which returned efibootmgr: Could not set BootOrder: No space left on device I then tried both update-bootloader --reinit which failed, then grub2-install which failed as well. This ended up with no efi boot options at all. I had to resort to chrooting from TW rescue disk and re-install grub2 and recover my PC. So far I have not tried to run the update-bootloader --reinit or grub2-install again since recovering my system as I fear it will mess up the system once more. As part of the update various grub2 packages were updated all not at beta3-10 level, the zypper history shows dracut running but no apparent errors were reported there. -- 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 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 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 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 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 929755] New: shutter is missing perl(Gnome2) in Tumbleweed
by bugzilla_noreply＠novell.com 21 Nov '21

21 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=929755 Bug ID: 929755 Summary: shutter is missing perl(Gnome2) in Tumbleweed Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: f_koch(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.101 Safari/537.36 Build Identifier: flo@linux-mvsa:~> sudo zypper in shutter Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides perl(Gnome2) needed by shutter-0.93.1-1.1.noarch Solution 1: do not install shutter-0.93.1-1.1.noarch Solution 2: break shutter-0.93.1-1.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

2 12

[Bug 1012260] New: Clang++-3.8 symlink is missing
by bugzilla_noreply＠novell.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1012260 Bug ID: 1012260 Summary: Clang++-3.8 symlink is missing 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: alex.richardson(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- lrwxrwxrwx 1 root root 23 Oct 31 11:44 /usr/bin/clang -> /etc/alternatives/clang lrwxrwxrwx 1 root root 25 Oct 31 11:44 /usr/bin/clang++ -> /etc/alternatives/clang++ lrwxrwxrwx 1 root root 11 Oct 31 11:45 /usr/bin/clang-3.8 -> clang-3.8.1 -rwxr-xr-x 1 root root 99176 Oct 31 11:44 /usr/bin/clang-3.8.1 lrwxrwxrwx 1 root root 11 Oct 31 11:45 /usr/bin/clang++-3.8.1 -> clang-3.8.1 There should also be a symlink /usr/bin/clang++-3.8 -> /usr/bin/clang++-3.8.1 I am building some software that expects clang++-$MAJOR.$MINOR to exist and it would be nice if I didn't have to create that link myself. -- You are receiving this mail because: You are on the CC list for the bug.

2 2