http://bugzilla.suse.com/show_bug.cgi?id=993401
Bug ID: 993401
Summary: grub2-install for EFI installs an EFI entry that is
not bootable
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.1
Hardware: aarch64
OS: openSUSE 42.1
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Bootloader
Assignee: jsrain(a)suse.com
Reporter: alan(a)softiron.co.uk
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Running grub2-install does not yield a bootable entry in EFI's boot menu. On
Leap and Tumbleweed, this means booting relies instead on the startup.nsh in
the EFI partition.
This occurs on Aarch64 with both AMD/AMI firmware and
Tianocore/edk2/OpenPlatformPkg firmware.
Steps to reproduce:
1. Install Leap 42.1 from the OEM image
2. Restart and boot the system
2a. Observe that the startup.nsh (in the EFI partition) is used to boot the
system.
3. Reboot again, but During boot-up, enter the EFI menu.
3a. Observe that in the boot manager in the EFI menus, there is no entry for
Leap.
4. Restart the system or select the UEFI shell option, booting from startup.nsh
5. From the command prompt in Leap, run:
grub2-install /dev/sda
6. Reboot the system
7. During start-up enter the EFI menu.
7a. Observe that in the EFI menu there is an entry called
opensuse-leap42.1-arm-jeos-devel-efi, or something like it.
8. Select the opensuse-leap* boot menu item and try to boot it.
9. Observe that it does not boot, and returns to the boot menu.
10. Select the UEFI Shell option, and observe that it will boot using
startup.nsh.
11. From the Linux command prompt, run "efibootmgr -v"
11a. Observe that the entry for opensuse-leap* is truncated :(
11b. Note the same can be observed by running "dumpstore" from the EFI
environment.
Note: The same thing happens if the bootloader is re-installed using "yast2
bootloader".
Note that this is broken in Leap, but works fine in SLES, probably because the
path and OS name for SLES is so much shorter.
Interestingly, if I try to add my own entry with the proper path:
efibootmgr -c -d /dev/sda -p 1 --loader
"EFI\\opensuse-leap42.1-arm-jeos-devel-efi\\grubarm64.efi" -L
Test_Entry_By_Alan
and then inspect it with:
efibootmgr -v
I see my entry is truncated too :(
Boot0007* Test_Entry_By_Alan
HD(1,800,64004,cb3a713f-f051-4c9c-b643-b9e1358f6c2d)File(EFI\opensuse-leap42.1-arm-jeos-devel-ef)
In summary, grub2-install and/or efibootmgr is simply putting a boot entry into
NVRAM that is truncated and not valid.
Thanks!
Alan.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1079439
Bug ID: 1079439
Summary: New area for ARCES Inter-Department Research Center
Bologna
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: OBS Request
Assignee: mrueckert(a)suse.com
Reporter: marco.giusti(a)posteo.de
QA Contact: adrian(a)suse.com
Found By: ---
Blocker: ---
We first reached OBS at ARCES[1] after the demand of porting our
application, Virtualbricks[2], to SLE 12. Even without any experience
with SUSE or RPM, OBS allowed us to easily create the needed packages
and to deliver the software to our partners. Convinced of the benefits
of OBS we want to exploit it more. Following the advice from adrianS_ in
#opensuse-buildservice here I ask for a dedicated space that could be
recognized as connected to us, ideally with arces.unibo.it in the name.
Here[3] you can see the results of my attempts made with my account.
For a confirmation of the officiality* of my request you can contact
Carlo Caini[4], Associate Professor at ARCES, who directed the development
of Virtualbricks the last years.
A few words about Virtualbricks and how it is exploited by ARCES.
Virtualbricks is a frontend for the management of Qemu Virtual Machines
(VMs) and VDE virtualized network devices (switches, channel emulators,
etc.). Although it can be used to manage isolated VMs, its peculiar aim
is to design and manage testbeds consisting of many VMs interconnected
by VDE elements. In other words, it allows to extend the concept of VM
to testbeds, which thanks to Virtualbricks can become entirely
software-defined.
Among the wide variety of possible applications, we have academic
research and teaching on computer networks. In particular, we would
like to use this space as main hub to distribute our software to the
students of the course Protocols and Architectures for Space Networks,
master degrees in TLC and Computer Engineering of the University of
Bologna, as well as to our research partners, including some European
space agencies (ESA, DLR).
Thank you for taking this request in account.
Marco
* Although this request received the consensus of the Director of ARCES,
this space will not be recognized as *official* by the University of
Bologna i.e. it will not receive any direct support from University of
Bologna outside our own effort to maintain it.
[1] http://www.arces.unibo.it/en
[2] https://github.com/virtualsquare/virtualbricks
[3] https://build.opensuse.org/project/show/home:marcogiusti
[4] https://www.unibo.it/sitoweb/carlo.caini/en
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1062260
Bug ID: 1062260
Summary: Repository medical gone ... where are the packages?
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: All
OS: openSUSE Factory
Status: NEW
Severity: Major
Priority: P5 - None
Component: 3rd party software
Assignee: opensuse-communityscreening(a)forge.provo.novell.com
Reporter: werner(a)suse.com
QA Contact: opensuse-communityscreening(a)forge.provo.novell.com
Found By: ---
Blocker: ---
I'd like to know where the packages of the former repository medical are
located?
I'm missing the packages aeskulap, xmedcon, ...
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1093827
Bug ID: 1093827
Summary: imagewriter fails with dbus error
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: SUSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: hacking(a)mail.quatrox.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
SUSE Studio Image Writer (imagewriter) does not work for me (in Tumbleweed).
The GUI opens and I select the image and device and click write.
Then it asks to umount the disk (if it is already mounted).
The partitions are now unmounted.
It now asks me to confirm to overwrite the content of the device, and I click
OK.
Now nothing is happening for maybe 30 seconds.
Then a dialog window appears with the following text:
DBUS error (sdc): Did not receive reply. Possible causes include:
the remote application did not send a reply, the message bus
security policy blocked the reply, the reply timeout expired, or the
network connection was broken.
The dialog only gives me the option to accept this by pressing OK.
Then a new dialog appears with the following text:
Couldn't open /dev/sdc: Resource temporarily unavailable
Again, I have to press OK.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1046309
Bug ID: 1046309
Summary: Popup title is not hidden in installation
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
URL: https://trello.com/c/jO8YkgSc
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: jreidinger(a)suse.com
QA Contact: jsrain(a)suse.com
CC: dimstar(a)opensuse.org, fabian(a)ritter-vogt.de,
fvogt(a)suse.com, jreidinger(a)suse.com, kossebau(a)kde.org,
lnussel(a)suse.com, lslezak(a)suse.com, mkravec(a)suse.com,
okurz(a)suse.com
Depends on: 1037891
Found By: ---
Blocker: ---
+++ This bug was initially created as a clone of Bug #1037891 +++
IMHO the regression is (see comment #36):
* openSUSE Leap 42.1 had no title whatsoever for popups during installation
(unless remote ssh install)
* openSUSE Leap 42.3 has a title that is overly long and prone to touch the
border of the window -> ugly and not adding information
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1012825
Bug ID: 1012825
Summary: YaST2 hung "retrieving cracklib-dict-full.rpm
extension" if rpm passed in DUD
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: PowerPC-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: normand(a)linux.vnet.ibm.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Created attachment 704263
--> http://bugzilla.suse.com/attachment.cgi?id=704263&action=edit
installation_overview-y2logs.tar.bz2
YaST2 hung "retrieving cracklib-dict-full.rpm extension"
while investigating bug https://bugzilla.suse.com/show_bug.cgi?id=1009472
I tried to pass a DUD=*dud containing the rpm*.rpm
The consequence is that YaST2 hungs at "retrieving cracklib-dict-full.rpm
extension"
The y2log ends is stuck at Calling: extend,
note that there is no /var/log/extend in reported tarball
and no trace of extend in /var/log/linuxrc.log
steps:
===
$mkdud -c /tmp/boo1009472.dud --install instsys --force -d 20161122
/tmp/powerpc-utils-1.3.2-9.ppc64le.rpm /tmp/rpm-4.12.0.1-0.ppc64le.rpm
===
/var/lib/openqa/script/client jobs post
ISO=openSUSE-Tumbleweed-DVD-ppc64le-Snapshot20161122-Media.iso ARCH=ppc64le
BUILD=20161122 DESKTOP=minimalx DISTRI=opensuse DVD=1 FLAVOR=DVD HDDSIZEGB=40
MACHINE=ppc64le-multipath MULTIPATH=1 OFW=1 QEMU=ppc64 QEMUCPU=host QEMUCPUS=8
QEMURAM=4096 QEMUTHREADS=8 TEST=install_minimalx VERSION=Tumbleweed
Test=install_minimalx VGA=std WORKER_CLASS=qemu_ppc64le
DUD=http://stade.lab.toulouse-stg.fr.ibm.com/~normand/boo1009472.dud
=== extract y2log
install(8235) [Ruby] modules/InstExtensionImage.rb:386 Calling: extend
'cracklib-dict-full.rpm'
===
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=973590
Bug ID: 973590
Summary: weird layout of bootloader screen
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: dmueller(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
While updating the openQA needle for openSUSE on AArch64 people noted that the
"indentation" of the items in the ncurses ui looks slightly awkward.
Is it intended that there is this huge empty space at the top left corner?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=958483
Bug ID: 958483
Summary: 3rd party application UI is not behaving as required
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: 2015*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: tchvatal(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
When using 3rd party module (like Virtualization) that tries to install
additional packages it at this moment works like this when you are in X
environment:
For each package there is pop-up showing progress and then this pop-up is
closed.
This causes severe issue if user runs compoziting enabled environment.
Imagine it like disco-bulb turning on and off as only on-top window is supposed
to be rendered right and all the underlying windows are greyed out.
More apps you install the more "funky" blinking you get.
Prefferable solution would be to somehow include the yast2 sw_single interface
that has the bottom progressbar and prints the installed packages.
Added value would be mostly for openSUSE, where the default DE's have enabled
compositing, but also for SLE case it would get at minimal prettier and at best
more understandable about what is happening for the installed packages.
For openSUSE it is quite commonly reported issue as I closed 3-4 during the
bugzilla cleanup mentioning this problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1121578
Bug ID: 1121578
Summary: python-aiohttp Factory version unable to build on Leap
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.1
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: mlin(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
In order to fix python-aiohttp build failure in Leap 15.1, python-aiohttp's
Factory version has submitted to Leap, however this version unable to build on
Leap due to missing deps,
https://build.opensuse.org/package/show/openSUSE:Leap:15.1:Staging:adi:21/p…
Note that, a problem is, python-Cython is one of the dep does not have greater
enough version in Leap, and python-Cython is from SLE.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1057976
Bug ID: 1057976
Summary: Patch for gtk3 (openSUSE-2017-1032) requires
vietnamese, inuktitut, thai, and amharic
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.2
Hardware: x86-64
OS: openSUSE 42.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: libzypp
Assignee: zypp-maintainers(a)forge.provo.novell.com
Reporter: Ulrich.Windl(a)rz.uni-regensburg.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 740114
--> http://bugzilla.opensuse.org/attachment.cgi?id=740114&action=edit
Screen shot showing Yast's suggestions
When online updating the gtk3-3.20.10-5.3.1 to gtk3-3.20.10-5.6.1, Yast2
insists to add additional language modules like
gtk3-immodule-{ietnamese,inuktitut,thai,amharic} which I don't need. See
attachment.
--
You are receiving this mail because:
You are on the CC list for the bug.