Re: F42 Change Proposal: Fedora Plasma Workstation (System-Wide)

Kevin Kofler via devel writes: You make a good point there. The thing is, GNOME tries really hard to design for new users, whom they define as a user who has never before used a computer. So, someone who never used at a computer before sits down in front of a new, empty, Gnome desktop, and

Re: Three steps we could take to make supply chain attacks a bit harder

Christoph Erhardt writes: I strongly oppose this suggestion. While it would have prevented this particular backdoor as a side-effect, the primary effect of going without unit tests would be an outsize hole in Fedora's QA. There have been several suggestions here for ways that this specific

Re: Three steps we could take to make supply chain attacks a bit harder

Tim Landscheidt writes: A major factor seems to have been the discrepancy between "the source code" at GitHub & Co. that was probably scrutinized by many eyes and the shipped, but different artifact. So one step (as a inter-distribution effort) could be to continuously automatically compare

Re: F40 Change Proposal: Optimized Binaries for the AMD64 Architecture (System-Wide)

Oron Peled writes: • I.e: a developer that need cross-compilation, install the wanted toolchain(s) and all library packages are immediately available from standard repositories. I guess Fedora people that work on ARM/ARM64/RISC-V would love such a support. There are a number deb

Re: rpmbuild core dumps

Florian Weimer writes: * Sam Varshavchik: > Stephen Smoogen writes: > >>https://github.com/rpm-software-management/rpm/issues/ >>2826>https://github.com/rpm-software-management/rpm/issues/2826 >> >> >> And thanks for opening a bug. I will watch

Re: rpmbuild core dumps

Stephen Smoogen writes: https://github.com/rpm-software-management/rpm/issues/ 2826>https://github.com/rpm-software-management/rpm/issues/2826 And thanks for opening a bug. I will watch to see what happens.  I'm genuinely curious. Am I really the only one seeing this? The bug seems

Re: rpmbuild core dumps

Stephen Smoogen writes: I am trying to figure out the logic of this section: ```     static char * lastUname = NULL; // So lastUname is NULL     static uid_t lastUid;     if (!thisUname) {         lastUname = rfree(lastUname); // lastUname should still be NULL and we are freeing NULL and

Re: rpmbuild core dumps

Stephen Smoogen writes: I am guessing the problem is really with the free(lastUname) since the rfree Yes. Multiple execution threads will reach lastUname and try to free the same pointer. glibc rightfully complains about the double-free. isn't referred to (but not sure if an optimization

Re: rpmbuild core dumps

Sam Varshavchik writes: Looking at a diff between the 4.19.0 an 4.19.1 tags, a call to rpmfiStat() was added to fill_archive_entry(). The backtrace above shows the execution finding its way from rpmfiStat() into very-much-thread-unsafe code in rpmug.c That code is used only

Re: rpmbuild core dumps

Stephen Smoogen writes:                 #1  0x7f05dd8588ee raise (libc.so.6 + 0x3e8ee)                 #2  0x7f05dd8408ff abort (libc.so.6 + 0x268ff)                 #3  0x7f05dd8417d0 __libc_message.cold (libc.so.6 + 0x277d0)                 #4  0x7f05dd8b47a5

Re: rpmbuild core dumps

Stephen Smoogen writes: »My apologies for bad quoting.. email from phone. What version of rpm build is used and what are some packages which are rebuilt that show this issue. This may be needed if the core dump is due to something else in the environment like memory limits etc  It's

Re: F40 Change Proposal: Wifi MAC Randomization (System Wide)

Kevin Kofler via devel writes: Sam Varshavchik wrote: > The ostensible reason for this is that you cannot be tracked by your fixed > MAC across different APs. But different APs will typically be operated by different people, who have no access to each other's MAC address logs anyway. S

rpmbuild core dumps

It seems that rpmbuild dumps core at the end of the build process, every once in a while. Typical: Wrote: /__w/courier-libs/courier-libs/courier-authlib/rpm/RPMS/x86_64/courier-authlib-userdb-debuginfo-0.72.0.20231223-101.fc39.x86_64.rpm Wrote:

Re: F40 Change Proposal: Wifi MAC Randomization (System Wide)

Kevin Kofler via devel writes: Sam Varshavchik wrote: > Christopher Klooz writes: > >> Btw, does anyone know if this (in the practically-same manner) is really >> already introduced in Windows, Mac, Android by default? Globally? This > > Most recent Androi

Re: F40 Change Proposal: Wifi MAC Randomization (System Wide)

Christopher Klooz writes: Btw, does anyone know if this (in the practically-same manner) is really already introduced in Windows, Mac, Android by default? Globally? This Most recent Android phones, and iPhones do this by default. What they do is pin each randomized MAC address per AP.

Re: Re: shotcut compilation fails with "error: ‘hasPro’ was not declared in this scope"

Martin Gansser writes: I have copied the virtual machine from a Windows computer to my Fedora 38 computer and shotcut can no longer be compiled here, but it can on the Windows computer. Do I have to repair the file system on the Linux computer or do anything else? You snipped out the

Re: OpenCOLLADA need a little c++ help

Richard Shaw writes: error: possibly dangling reference to a temporary [-Werror=dangling- reference]   315 |                 const auto & parents = dae.root().selectNodes("//*[@sid]/.."); This is a complaint about a potential problem that might, just might be true. It can't be determined

Re: Deprecation of the aspell package

Mattia Verga via devel writes: I'd also like to raise attention to what I think is a misleading Change Summary: > Deprecating aspell package because it is no longer > Required/Buildrequired by any package in Fedora. This is clearly not true, as the change is about migrating package to another

Re: Deprecation of the aspell package

Lukas Javorsky writes: Hi, I would like to announce the Fedora change for the deprecation of the aspell package [1]. This package has a dead upstream and has been obsoleted (in most occurrences) by the hunspell package [2]. http://aspell.net/ does not seem to be dead to me. This is

Re: F39 proposal: Man-pages-ru Retirement (Self-Contained Change proposal)

Leslie Satenstein via devel writes: As a developer, and I believe, other developers who use C, C++, Rust,  etc, I would like to do a man  "whatever.h" to optain a list of the defines, and from that list, I would choose to select  the entry for which I need more information. Please give

Re: It’s time to transform the Fedora devel list into something new

Matthew Miller writes: I don't think this is _really_ a "there are two kinds of people in the world..." situation. Of course there are some people who have preferences (strong or weak) for one or the other, and completely legitimate pros and cons to each. But I don't want to "trade" anyone. I'd

Re: Is there convenient way to setup Fedora compilation flags outside of the RPM build?

Florian Weimer writes: After installing redhat-rpm-config, this works in bash and similar shells: $ eval `rpm --eval %set_build_flags` Maybe we can make it more clear in buildflags.md that this macro is a shell script fragment? I find it more convenient to generate parameters for an

Re: Is there convenient way to setup Fedora compilation flags outside of the RPM build?

Vitaly Zaitsev via devel writes: On 23/12/2022 19:21, Vít Ondruch wrote: Working with upstream on one issue [1], it seems that the culprit is in the Fedora compiler options. Is there some convenient way to set them up? rpm -E %optflags rpm -E '%__global_ldflags' is also needed for

Re: Karma for OpenSSL needed

Otto Liljalaakso writes: Kevin Fenzi kirjoitti 2.11.2022 klo 20.33: So, I suppose the web interface could offer signed copies if they exist, but might be confusing if you don't know what the various keys short hash is. Feel free to file a RFE for koji folks: https://pagure.io/koji I

Re: Request to change default /etc/resolv.conf symlink

Petr Menšík writes: If systemd-resolved ever becomes capable as a good DNS cache, we can return it back to domain port. I don't think it is ready for that. Search the archives of the users list for systemd-resolved complaints. I've done my share. Perhaps a bunch of them coming from

Re: F36 mock rebuild failure: cannot open linker script file

Zbigniew Jędrzejewski-Szmek writes: The issue is that in %prep, %buildsubdir is not defined, so the definition of %_package_note_file, which uses %buildsubdir, has a different value than in %build and later. Generally the best solution is to move the step that tries to make use of the package

F36 mock rebuild failure: cannot open linker script file

I'm taking a rather boring F35 SRPM and attempting to rebuild it in mock for F36. Its stock configure script, that tries to test-compile conftest.c fails thusly: gcc -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches - pipe -Wall -Werror=format-security

Re: No daemon-reload or restart with %systemd_postun_with_restart

Zbigniew Jędrzejewski-Szmek writes: > > That the service is "oneshot" matters for the "restart" part. What > > systemd actually does, is queue a "try-restart" job for the marked units. > > Since this service is not running, that should become noop. > > There seems to be a bug in the

Re: No daemon-reload or restart with %systemd_postun_with_restart

Zbigniew Jędrzejewski-Szmek writes: There are two separate steps here: "daemon-reload" and "restart testsystemd.service". Systemd is complaining about "daemon-reload" missing. It isn't internally cognizant of the fact that testsystemd.service should be restarted, that is managed by the rpm

Re: No daemon-reload or restart with %systemd_postun_with_restart

Ewoud Kohl van Wijngaarden writes: On Mon, Mar 21, 2022 at 07:12:23PM -0400, Sam Varshavchik wrote: Ewoud Kohl van Wijngaarden writes: On Mon, Mar 21, 2022 at 08:27:35AM -0400, Sam Varshavchik wrote: Ewoud Kohl van Wijngaarden writes: On Fri, Mar 18, 2022 at 06:22:08PM -0400, Sam

Re: No daemon-reload or restart with %systemd_postun_with_restart

Ewoud Kohl van Wijngaarden writes: On Mon, Mar 21, 2022 at 08:27:35AM -0400, Sam Varshavchik wrote: Ewoud Kohl van Wijngaarden writes: On Fri, Mar 18, 2022 at 06:22:08PM -0400, Sam Varshavchik wrote: The only thing that https://docs.fedoraproject.org/en-US/packaging- guidelines/Scriptlets

Re: No daemon-reload or restart with %systemd_postun_with_restart

Ewoud Kohl van Wijngaarden writes: On Fri, Mar 18, 2022 at 06:22:08PM -0400, Sam Varshavchik wrote: The only thing that https://docs.fedoraproject.org/en-US/packaging- guidelines/Scriptlets/ tells me to do is to put %systemd_postun_with_restart in my %post. However: 1) systemd complains

No daemon-reload or restart with %systemd_postun_with_restart

The only thing that https://docs.fedoraproject.org/en-US/packaging- guidelines/Scriptlets/ tells me to do is to put %systemd_postun_with_restart in my %post. However: 1) systemd complains that it wants a daemon-reload, in order to pick up an updated .service file 2) I still must manually

11 minutes to update the breeze-icon-theme package

I noticed that dnf update stuck for a while in the "Cleanup" phase of the breeze-icon-theme package. At the time this was taken: it spent 10 minutes with the CPU pegged at 100%, and it eventually finished at about the 11 and a half minute mark, and completed the rest of the update:

Re: CVE-2021-4034: why is pkexec still a thing?

Lennart Poettering writes: On Di, 01.02.22 09:01, Sam Varshavchik (mr...@courier-mta.com) wrote: > And an isolated process will be capable of rate-limiting itself in this > situation any better than a sudo process, which could do the same kind of > rate-limiting itself, exactly ho

Re: CVE-2021-4034: why is pkexec still a thing?

Lennart Poettering writes: On Di, 01.02.22 07:14, Sam Varshavchik (mr...@courier-mta.com) wrote: > Lennart Poettering writes: > > > On Mo, 31.01.22 18:32, Sam Varshavchik (mr...@courier-mta.com) wrote: > > > > > Lennart Poettering writes: > > > > > >

Re: CVE-2021-4034: why is pkexec still a thing?

Lennart Poettering writes: On Mo, 31.01.22 18:32, Sam Varshavchik (mr...@courier-mta.com) wrote: > Lennart Poettering writes: > > > See the discussion around seccomp and NNP. i.e. a new kernel facility > > was added precisely to ensure that seccomp cannot b

Re: CVE-2021-4034: why is pkexec still a thing?

Lennart Poettering writes: See the discussion around seccomp and NNP. i.e. a new kernel facility was added precisely to ensure that seccomp cannot be used to run code that is intended to be run privileged – under security policies in control by an unprivileged user. i.e. if you can take certain

Re: CVE-2021-4034: why is pkexec still a thing?

Demi Marie Obenour writes: What would break if sudo was replaced by an IPC service that ran sudo as if it was setuid root, without it actually being setuid root? I imagine the hardest part would be TTY handling, as not being able to Ctrl-C a command launched by sudo is a rather poor user

Re: CVE-2021-4034: why is pkexec still a thing?

Lennart Poettering writes: On Mo, 31.01.22 06:28, Sam Varshavchik (mr...@courier-mta.com) wrote: > > I vehemently disagree. The thing with setuid/setgid is that the > > invoked privileged process inherits a lot of implicit state and > > context that people aren't really

Re: CVE-2021-4034: why is pkexec still a thing?

Lennart Poettering writes: On Fr, 28.01.22 18:16, Sam Varshavchik (mr...@courier-mta.com) wrote: > Having said all of that: the suid bit itself is irrelevant. It is nothing > more than a convenient scapegoat to blame other bugs on. The same bug that's > exploitable in a suid binary

Re: CVE-2021-4034: why is pkexec still a thing?

Florian Weimer writes: > Well, that's precisely the problem that PK was supposed to address, > but then it descended down the JS rabbit hole... Not sure if we are talking about the same thing. I meant flooding the local socket (or similar) with requests, not access control. Create a

Re: During the first update after installation: Failed to connect to bus: Invalid argument

Peter Boy writes: While updating right after installation of Fedora Server 35 today I get: > Running Scriptlet: tzdata-2021b-1.fc35.noarch 306/306 > Failed to connect to bus: Invalid argument > > Failed to connect to bus: Invalid argument > > Failed to connect

Re: F35 3x slower boot than F34

Vitaly Zaitsev via devel writes: On 05/09/2021 09:55, Philip Rhoades via devel wrote: My response to situations in the past where resolving the SELinux issue was opaque (usually to do with MTAs if I recall correctly) . . was just to disable SELinux and move on . . In over 10 years with

Re: F35 3x slower boot than F34

Vitaly Zaitsev via devel writes: On 05/09/2021 14:52, Sam Varshavchik wrote: if only a great, overwhelming majority of Fedora package maintainers were able to write policies for their own packages and maintain it themselves because SELinux documentation was ample and easy to fllow https

Re: F35 3x slower boot than F34

Vitaly Zaitsev via devel writes: On 05/09/2021 09:19, Peter Boy wrote: Much to my chagrin, you describe the biggest problem in Fedora for years and the one why Fedora is falling further and further behind among distributions. The problem overshadows all that many positive features that

Re: F35 3x slower boot than F34

Miroslav Suchý writes: Dne 04. 09. 21 v 17:28 Sam Varshavchik napsal(a): Are you a package maintainer? Ok: please write an selinux policy for your package. Let me know when that's done. https://pagure.io/copr/copr/blob/main/f/selinux You are welcome. You did that 7 years ago, according

Re: F35 3x slower boot than F34

Stephen Gallagher writes: So it appears to be an SELinux issue. I suspect but cannot prove that it's related to a number of AVCs related to DBUS that I see in selinux-troubleshooter. I've watched SELinux come into existence, and its evolution over the years. It's clear to me that SELinux,

Re: F34 regression: nouveau crashes on kernel 5.12

Tim Jackson writes: I'm unfortunately no expert in this area, but as far as I can tell, certain(?) chipsets using the nouveau driver fail to resume from suspend on all 5.12 kernels, which leaves the system in an apparently unrecoverable state requiring a hard reboot. The same hardware

Re: The future of legacy BIOS support in Fedora.

Marius Schwarz writes: Am 30.06.20 um 15:34 schrieb Jóhann B. Guðmundsson: Given Hans proposal [1] introduced systemd/grub2/Gnome upstream changes it beg the question if now would not be the time to stop supporting booting in legacy bios mode and move to uefi only supported boot which has

Re: Remove old GPG keys?

Miroslav Suchý writes: Dne 03. 05. 21 v 17:06 Sam Varshavchik napsal(a): Yeah, so: 1) Someone has to remember to do this as part of every release 2) This doesn't do anything about add-on repositories' keys 3) I had pgp keys going all the way to F19, etc… My approach is slightly awkward

Re: Remove old GPG keys?

Miroslav Suchý writes: Dne 03. 05. 21 v 0:18 Sam Varshavchik napsal(a): Yes, I'm replying to this old thread. See it in the list archives. And, since then, doesn't look much has changed. Old pgp keys are still gathering dust, in everyone's rpm databases. I had nothing else to do this lazy

Re: Remove old GPG keys?

> I just stumbled upon > https://unix.stackexchange.com/questions/400634/does-anyone-bother-to-rem... > with the nice link to: > https://blog.laimbock.com/2014/05/02/how-to-remove-an-imported-gpg-key-fr... > And I wonder: is it a good idea to keep old gpg keys in RPM db? Or should we >

Re: Don't update to the latest f33!

Steve Dickson writes: On 2/15/21 6:19 PM, Sam Varshavchik wrote: > Steve Dickson writes: > >> Hello, >> >> I just updated to latest Fedora 33 and >> I no longer have any DNS name solution. >> The network is up... but... >> >> $ ping www.y

Re: Don't update to the latest f33!

Steve Dickson writes: Hello, I just updated to latest Fedora 33 and I no longer have any DNS name solution. The network is up... but... $ ping www.yahoo.com ping: www.yahoo.com: Name or service not known I changed nothing! How would be the bet way to debug this??? Inspect what it's your

Re: dropping php-imap (was Re: Orphaned packages looking for new maintainers)

Joe Orton writes: On Mon, Feb 08, 2021 at 06:43:29PM +, Gwyn Ciesla via devel wrote: > Can uw-imap be replaced with something else, or should someone pick it up? There has not been an upstream release since 2007 - the maintainer Mark Crispin sadly died in 2012, and nobody else has formed

Re: COMMERCIAL - Bosch - Architect

George Bastin writes: Sorry Marius, it is not a violation of any law. Right. By the way, banning everyone from an organization from using a mailing list: that's not a violation of any law, either. It would also not be a violation of any law to notify administrators of other mailing lists

Re: Fedora 34 Change: DNF/RPM Copy on Write enablement for all variants (System-Wide Change)

Neal Gompa writes: On Mon, Dec 21, 2020 at 1:14 PM Marius Schwarz wrote: > > If something really needs to change, it is the 50+ MB repo database that > gets downloaded. It takes ages on slow connections to download > and than you want to increase the size of the rpms too.. Doesn't sound >

Re: gpg-agents all over the place

Roberto Ragusa writes: On 12/16/20 2:55 AM, Kevin Kofler via devel wrote: Believe it or not, GNU/Linux is no longer a text-only operating system, nor are window managers just a container for terminal emulators. :-) But that is different than saying the GNU/Linux has become a no-text

Re: gpg-agents all over the place

Kevin Kofler via devel writes: Sam Varshavchik wrote: > But, for some reason that I do not understand, the existing terminal > interface always gets broken. Well, how prompts in terminal emulator sessions in the GUI should work is a design decision. Some people (like you, apparently)

Re: gpg-agents all over the place

Kevin Kofler via devel writes: Sam Varshavchik wrote: > I miss the days when gpg needed a passphrase it simply prompted a message > on standard output, turned off tty echo, and just read the password that I > typed in. > > But that was too simple, primitive, and bulletproof. I gu

Re: gpg-agents all over the place

Marius Schwarz writes: Hi, I sorry to tell you, that gpg-agents are inflating on numbers in Fedora systems: I miss the days when gpg needed a passphrase it simply prompted a message on standard output, turned off tty echo, and just read the password that I typed in. But that was too

Re: Serial Console with Fedora 33

Steve Dickson writes: Hello, How does one set up a serial console with F33? In the past I would edit kernelopts with grub2-editenv and set "console=tty0 console=ttyS0,115200n8". As well as set the following in /etc/grub2.conf terminal_output console #set timeout=5 serial --unit=0

Re: The future of legacy BIOS support in Fedora.

Arnoldas Skinderis writes: I'am also have Thikpads and MSI running BIOS and some of those machines  still are the beast in some terms. Dropping BIOS would pretty much force me to use something else. I don't want to lose Fedora. Ditto. My Thinkpad W520 is the best damn Fedora laptop.

Including local repos in a mock build

Is there a better way to include local repos in mock builds than doing something like this in my /etc/mock/default.cfg: include('fedora-32-x86_64.cfg') config_opts['dnf.conf'] = config_opts['dnf.conf'] + """ [my] name=My repository baseurl=http://jack/repos/$releasever/$basearch enabled=1

Re: The future of legacy BIOS support in Fedora.

Solomon Peachy writes: Even putting that aside, for the past several years CSM/BIOS has been slowly bitrotting due to a lack of real testing, as the last few Windows releases have mandated use of UEFI for preinstalled systems, plus the EOLing of Windows 7 and (especially) XP. That's only

Re: Fedora Jam switch to GNOME

er...@ericheickmeyer.com writes: Anyhow, I'd love to see a discussion about this as well as any guidance toward making this change. I know there would have to be a new kickstart along with Koji pointing toward said kickstart. I could make the kickstart, but I think I'd need Koji to look for it.

Re: What CPU extensions can we assume are available by arch?

Richard Shaw writes: I'm having trouble determining what the base CPU targets for Fedora can accommodate. For example, ss it safe to assume AVX2 on x86_64?  Nope. Linux thinkpad 5.5.16-200.fc31.x86_64 #1 SMP Wed Apr 8 16:43:33 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [ /proc/cpuinfo:

Re: gpg check failure installing from rawhide

Kevin Fenzi writes: On Sat, Mar 07, 2020 at 09:47:03AM -0500, Sam Varshavchik wrote: > Trying to follow the direction for a bug report against kernel, and install > the latest kernel from rawhide. > > The Bugzilla template says: > > 5. Does this problem occur with the lat

gpg check failure installing from rawhide

Trying to follow the direction for a bug report against kernel, and install the latest kernel from rawhide. The Bugzilla template says: 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run “sudo dnf install fedora-repos-rawhide“ followed by “sudo

Re: g++ 10: static declared in extern "C" inline function

Iñaki Ucar writes: On Sun, 9 Feb 2020 at 14:20, Sam Varshavchik wrote: > > Iñaki Ucar writes: > > > Thoughts? > > > > [1] https://gist.github.com/kevinushey/cfa848be2d39ddd110f893d9b6c5ac9c > > I managed to find the part of the C++ standard that specified the

Re: g++ 10: static declared in extern "C" inline function

Iñaki Ucar writes: Thoughts? [1] https://gist.github.com/kevinushey/cfa848be2d39ddd110f893d9b6c5ac9c I managed to find the part of the C++ standard that specified the semantics of extern "C" linkage, it is [dcl.link]. The term used is "language linkage". There is no such thing as an

Re: Is 50+ RPM Subpackages too extreme?

Chris writes: Hi guys, I just wanted to poll you for some advice.  My notification tool I maintain supports more than 50+ services now, but the only package isolation I do You should really count the number of texlive subpackages… pgpeYylRqybGZ.pgp Description: PGP signature

Re: Encrypted DNS in Fedora

Florian Weimer writes: * Michael Cronenworth: > On 11/4/19 2:17 PM, Florian Weimer wrote: >> We are not going to implement this directly in glibc. You should talk >> to a stub resolver on 127.0.0.1 instead. We do not want to link a >> cryptographic library into every process that queries an

Re: No longer supporting mailing lists:

Markus Larsson writes: « HTML content follows » On 26 August 2019 12:56:42 CEST, "Gerald B. Cox" wrote: What issues are you referring to? I don't believe it is reasonable to believe everything would work exactly the same with Discourse - but close enough should be sufficient. There are also

Re: How do I remove GLIBCXX_ASSERTIONS?

Tom Hughes writes: On 06/08/2019 09:37, Miroslav Lichvar wrote: Ok, but does that mean the program has to abort? Could gcc do anything dangerous here? If we were actually trying to catch undefined behavior (e.g. with -fsanitize=undefined), I suspect Fedora wouldn't even boot without a crash.

Re: How do I remove GLIBCXX_ASSERTIONS?

Georg Sauthoff writes: > I ended up tweaking my code to avoid the assertions, rather than disabling > them. For this particular situation, my original change was to try > > std::copy([0], [0]+foo.size(), std::back_insert_iterator{bar}); > > But that still tripped the assertion when the foo

Re: How do I remove GLIBCXX_ASSERTIONS?

Andrew Lutomirski writes: On a cursory search of the standard, I couldn't find where it says what operator* on this type of iterator does at all, let alone whether it's valid for one-past-the-end iterators, but I'm pretty sure that your code is, indeed, wrong. This finally piqued my curiosity

Re: How do I remove GLIBCXX_ASSERTIONS?

Tom Hughes writes: But I think upstream is giving very bad advice... That define does not "add extra crashes" in the way that they seem to think - well I mean it does literally but those crashes are reports of program errors on their part. Specifically in this case they appear to be accessing

Re: Fedora 32 System-Wide Change proposal: x86-64 micro-architecture update

A brief survey of my hardware and less than half of it supports avx2. I can't find a single enthusiastic endorsement for this proposal in this thread, so far; but if this proposal ends up being adopted, I hope that this gets announced well in advance, including a big fat banner on

Re: Reporting is disabled because the generated backtrace has low informational value

Chris Murphy writes: Please try to install debuginfo manually using the command: "debuginfo-install flatpak-1.4.1-1.fc30" and try again. That's your key piece of info. You're missing the debuginfo package, without it the backtrace has no info. With a native, directly-installed RPM, the

Bad locale environment in mock install

r(-,root,root,-) %post locale >/var/tmp/locale.log %changelog * Mon May 6 2019 Sam Varshavchik - - Initial build. pgpVIeyaVoyHE.pgp Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to de

Re: Upgrade to F30 gone wrong

Chris Murphy writes: In that case I expect that the rescue kernel+initramfs feature first appeared in dracut in Fedora 19, so that's the first time it would have noticed the pair are missing, and it would have created them at that time. But that's just a guess. This seems to be it. Two of my

Re: Upgrade to F30 gone wrong

Chris Murphy writes: If you see the rescue kernel+initramfs menu entry though, you do not have the bug under discussion, and you don't need to run 'grub2-install' - your GRUB is by definition functioning fine if you see this menu entry. I just inventoried my bricks. One, which has not been

Re: Upgrade to F30 gone wrong

Steve Grubb writes: Rescue mode? I couldn't find it. All references I could find to a rescue mode date back to 2013 or later. I would have liked a rescue mode because makes it easy to just chroot into your actual system from the livecd. Seems like we've lost something nice if its really been

Re: Upgrade to F30 gone wrong

Chris Murphy writes: This bug itself was expected to be an edge case, that not many users would be affected, in that not many would have a stale Fedora 20 or older bootloader. Surely 'grub2-install' would have been manually run, or the user has done a recent clean install since Fedora 20,

Re: Upgrade to F30 gone wrong

Chris Murphy writes: Actually, that's a problem too. The stale bootloader problem goes back to an era where it was possible to install the bootloader into the first sector of the boot partition, and in those cases, /dev/sda1 is actually valid. And again, no practical way to discover this

Re: IBM buying RedHat

Chris Murphy writes: The reported deal is $34 billion, and Red Hat's closing market cap on Friday was ~$20 billion, that's a big price premium. I'm not a lawyer let alone a securities lawyer, but my guess is if Red Hat management had refused the deal, I think they'd face shareholder lawsuits.

Re: hibernation — does it work for you?

Zbigniew Jędrzejewski-Szmek writes: If you perform hibernation (systemctl hibernate, or the equivalent through the GUI), does _your_ system suspend and resume correctly? Note: I'm not talking about the user-space configuration issues (resume= not set on the kernel command line, no swap, swap

Re: F29 Self Contained Change: Deprecate YUM 3

Jan Kurik writes: = Proposed Self Contained Change: Deprecate YUM 3 = https://fedoraproject.org/wiki/Changes/Deprecate_YUM_3 Owner(s): * Daniel Mach Remove yum (v3) and all related packages from Fedora. == Detailed description == Remove packages from the distribution: * createrepo We

Re: Hiding the grub menu by default on single OS installs

Hans de Goede writes: For F29 the plan is to just hide it (unless a previous boot failed) What is the exact criteria for "previous boot failed", I'm wondering. Even if you reach as far as the GDM screen it's still possible that something is so horked up to the point that you can't log in,

Re: F29 System Wide Change: Hide the grub menu

Jan Kurik writes: = Proposed System Wide Change: Hide the grub menu = https://fedoraproject.org/wiki/Changes/HiddenGrubMenu Owner(s): * Hans de Goede On systems with only a single OS installed, the grub menu does not offer any useful functionality, so we should hide it by default.

Re: script to run after hotspot authentication?

Paul Wouters writes: Hi, Is there a way to run a custom command after hotspot authentication? Fedora has/had some ways of detecting portals. dnssec-trigger, NetworkManager and Gnome3. I think the current method is supposed to be based on the latter. So I guess the problem that is used is

Re: gnome crashes after today upgrade

Tomasz Kłoczko writes: -- after only 3-4h on m primary desktop I've been able to collect descent number of core files # ls -la /var/lib/systemd/coredump/* -rw-r-+ 1 root root 1628938240 Feb  6 03:28 /var/lib/systemd/coredump/core.chrome.

Re: gnome crashes after today upgrade

Tomasz Kłoczko writes: On 3 February 2018 at 22:55, Richard Shaw <hobbes1...@gmail.com> wrote: Any news on the cause? I'm waiting to update until this is figured out... Still don't see any update about the issue. It is really pain in the a*s that Linux

Re: Firefox "Looking Glass" fiasco

Gerald B. Cox writes: Everyone makes mistakes - this wasn't the first by Mozilla and won't be the last.  I don't believe they are acting out of malice.  As long as they admit and correct mistakes as they go along that is fine with me. Here's the most complete statement from Mozilla that I

stg.pagure.io SSL cert error

While browsing around a sandbox project on stg.pagure.io, the release folder URL goes to https://releases.stg.pagure.org Firefox refuses open it because the server's SSL cert does not include this particular domain. Furthermore Firefox refuses to add an exception because of HSTS. Where

Re: Fedora 27 is here

Josh Boyer writes: On Wed, Nov 15, 2017 at 5:03 PM, Nicolas Chauvet wrote: > 2017-11-15 23:02 GMT+01:00 Nicolas Chauvet : >> Hi, >> >> Just want to say welcome to Fedora 27 ! >> >> The RPM Fusion repository is ready to server f27 content in time for >> the

Re: Remove old GPG keys?

Jonny Heggheim writes: On 11/01/2017 11:51 PM, Sam Varshavchik wrote: > I don't think much of expiring either. But keys for prior releases > should simply be removed, as part of the upgrade process, or on the > first boot after a successfull upgrade. > > Now, if we go this way,

Re: Remove old GPG keys?

Kevin Fenzi writes: I personally don't see much advantage in expiring old keys or the like. The only attack vector I can see is tricking someone into installing a package from an EOL release with a known vulnerablity, but if you can do that you likely can get them to just download it and

  1   2   3   >