Search results for

Re: New Slowroll update 20241030T2221 released!

by Felix Miata

Bernhard M. Wiedemann composed on 2024-10-31 07:19 (UTC+0100): > Jon Cosby wrote: >> When are the snapshots released > The version bumps are released around the 9th of each month, so the next > one is planned for 2024-11-09 > I was wondering if the notifications of daily updates are too spammy > here. Should I send them elsewhere? I don't know about elsewhere, but I consider them nominally spammy here. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

4 days, 16 hours

Re: Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

by ASSI

Andrei Borzenkov writes: > man zypper > zypper search --recommends > zypper info --supplements Hmmm. Doesn't seem to tell me where the whole thing started, but at least I found that systemd-boot was also installed (have yet to find out why) and that was what kept pulling sdbootutil in (alongside shim which of course is actually needed to facilitate UEFI secure boot). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

3 days, 2 hours

Re: Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

by ASSI

ASSI writes: > Andrei Borzenkov writes: >> Why do you have sdbootutil installed if you are not using systemd-boot? > > I don't know. I had to manually remove it at some time (based on advice > on this list) and either I forgot to do it on this machine (this is an > older system that I don't use regularly anymore) or it got pulled in > again at a later time. Removing it manbually resolves the issue and no > error message is shown when installing a kernel. I updated that system again today and the same thing happened, as something has pulled in sdbootutil again. Since I can cleanly remove it, it is either a recommendation or a weak dependency, how do find out what is causing sdbootutil to get installed on this machine? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

3 days, 6 hours

Re: Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

by Andrei Borzenkov

01.11.2024 19:47, ASSI wrote: > ASSI writes: >> Andrei Borzenkov writes: >>> Why do you have sdbootutil installed if you are not using systemd-boot? >> >> I don't know. I had to manually remove it at some time (based on advice >> on this list) and either I forgot to do it on this machine (this is an >> older system that I don't use regularly anymore) or it got pulled in >> again at a later time. Removing it manbually resolves the issue and no >> error message is shown when installing a kernel. > > I updated that system again today and the same thing happened, as > something has pulled in sdbootutil again. Since I can cleanly remove > it, it is either a recommendation or a weak dependency, how do find out > what is causing sdbootutil to get installed on this machine? > man zypper zypper search --recommends zypper info --supplements > > Regards, > Achim.

3 days, 5 hours

Re: Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

by David Walker

sdbootutil reappeared on my aarch64 systems, but not my x86_64 systems. On all systems... > zypper info --supplements sdbootutil Loading repository data... Reading installed packages... Information for package sdbootutil: ----------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : sdbootutil Version : 1+git20241017.34ee974-1.1 Arch : aarch64 Vendor : openSUSE Installed Size : 75.9 KiB Installed : Yes (automatically) Status : up-to-date Source package : sdbootutil-1+git20241017.34ee974-1.1.src Upstream URL : https://en.opensuse.org/openSUSE:Usr_merge Summary : script to install shim with sd-boot Description : Hook scripts to install shim along with systemd-boot Supplements : [2] (grub2-x86_64-efi-bls and shim) (systemd-boot and shim) On the aarch64 systems... > zypper se -x grub2-x86_64-efi-bls shim systemd-boot Loading repository data... Reading installed packages... S | Name | Summary | Type ---+--------------+----------------------------+-------- i+ | shim | UEFI shim loader | package i | systemd-boot | A simple UEFI boot manager | package On the x86_64 systems... > zypper se -x grub2-x86_64-efi-bls shim systemd-boot Loading repository data... Reading installed packages... S | Name | Summary | Type ---+----------------------+--------------------------------------------+-------- | grub2-x86_64-efi-bls | Image for Boot Loader Specification (BLS-> | package i+ | shim | UEFI shim loader | package | systemd-boot | A simple UEFI boot manager | package I pretty sure I didn't install systemd-boot on the aarch64 systems (and its status is "i", not "i+"). I'm not sure how to read the " (systemd-boot and shim)" under Supplements, but I'm guessing the presence of systemd-boot, along with shim, is what's causing the installation of sdbootutil. David On 11/1/24 10:17 AM, Andrei Borzenkov wrote: > 01.11.2024 19:47, ASSI wrote: >> ASSI writes: >>> Andrei Borzenkov writes: >>>> Why do you have sdbootutil installed if you are not using >>>> systemd-boot? >>> >>> I don't know. I had to manually remove it at some time (based on >>> advice >>> on this list) and either I forgot to do it on this machine (this is an >>> older system that I don't use regularly anymore) or it got pulled in >>> again at a later time. Removing it manbually resolves the issue and no >>> error message is shown when installing a kernel. >> >> I updated that system again today and the same thing happened, as >> something has pulled in sdbootutil again. Since I can cleanly remove >> it, it is either a recommendation or a weak dependency, how do find out >> what is causing sdbootutil to get installed on this machine? >> > > man zypper > zypper search --recommends > zypper info --supplements > >> >> Regards, >> Achim.

3 days, 4 hours

Re: Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

by Andrei Borzenkov

01.11.2024 21:00, David Walker wrote: > > I pretty sure I didn't install systemd-boot on the aarch64 systems (and > its status is "i", not "i+"). I'm not sure how to read the " > (systemd-boot and shim)" under Supplements, but I'm guessing the > presence of systemd-boot, along with shim, is what's causing the > installation of sdbootutil. > Correct.

3 days, 4 hours

openSUSE:Factory - Build fail notification

by DimStar / Dominique Leuenberger

Dear Package maintainers and hackers. Below package(s) in openSUSE:Factory have had problems for at least 4 weeks. We tried to send out notifications to the configured bugowner/maintainers of the package(s), but so far no fix has been submitted. This probably means that the maintainer/bugowner did not yet find the time to look into the matter and he/she would certainly appreciate help to get this sorted. - codelite: Uninstallable: nothing provides libwx_baseu-suse.so.11.0.0()(64bit) needed by codelite-16.0.0.x86_64 Unless somebody is stepping up and submitting fixes, the listed package(s) are going to be removed from openSUSE:Factory. Kind regards, DimStar / Dominique Leuenberger <dimstar(a)opensuse.org>

3 days, 23 hours

Re: Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

by ASSI

David Walker writes: > Is your system also aarch64, Achim? I'm wondering if it seems that > systemd-boot is installed by default on aarch64 but not x86_64, or if > I've done something that caused it to be installed. No, x86_64; only one of my systems had this problem. It's also very similar to another one, the difference is that the system with the problem gets updated less often, so I think there was some packaging error in the past that somehow led to the situation. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

2 days, 15 hours

Re: Error: Bootloader not detected. /etc/sysconfig/bootloader has LOADER_TYPE="grub2-efi", but only "systemd-boot" or "grub2-bls" are recognized.

by David Walker

Is your system also aarch64, Achim? I'm wondering if it seems that systemd-boot is installed by default on aarch64 but not x86_64, or if I've done something that caused it to be installed. David On 11/1/24 1:31 PM, ASSI wrote: > Andrei Borzenkov writes: >> man zypper >> zypper search --recommends >> zypper info --supplements > Hmmm. Doesn't seem to tell me where the whole thing started, but at > least I found that systemd-boot was also installed (have yet to find > out why) and that was what kept pulling sdbootutil in (alongside shim > which of course is actually needed to facilitate UEFI secure boot). > > > Regards, > Achim.

2 days, 19 hours

Re: issue with libQt6Core.so.6 don't let me to dup my Tumbleweed

by Christian Boltz

Hello, Am Freitag, 25. Oktober 2024, 18:27 schrieb victorhck: > Everytime I lauch the command zypper says that > > "telegram-desktop-5.5.5-1.2.x86_64 installed requires > libQt6Core.so.6(Qt_6.7.3_PRIVATE_API)(64bit)" That's a known issue and was already discussed on the support mailinglist a few days ago. The good thing is that there's already a fix submitted: https://build.opensuse.org/request/show/1208908 The most boring solution is to wait until this SR reaches Tumbleweed. Regards, Christian Boltz -- > check up on dusted up coolers / vents etc. That is the first thing that I did, but I can't imagine that the amount of dust is automatically changing with the kernel ? [> David Haller and Raymond Wooninck in opensuse-factory]

1 week, 3 days

openSUSE Factory search results for query "a"