Re: are there typical ways Fedora tends to break?
Am 15.07.22 um 20:41 schrieb Chris Murphy: Hi, I have a request for list regulars. The Fedora Workstation working group is curious if there's any pattern or categorization how Fedora installations typically break. i.e. the installation is successful, the system has been updated multiple times successfully, and then for whatever reason it breaks. Are most failures hardware related? Some are. They happen, but these happen once or twice a year. What portion of the failures are early boot failures? (Defined as bootloader, kernel, or early initramfs failures. But excludes being landed at a dracut prompt.) On BIOS-systems I am experiencing these once or twice a year kernel bugs. By far most often (1x per month): Networking issues. In recent years, I several times found myself in situations, I had to tweak details of network configurations, because Fedora's "vision" of network configuration did harmonize well with mine. (One recent such incident: Something in Fedora broke "domainname expansion".) What portion of all failures are fixable without reinstalling? The only occasion, I found myself reinstalling was something having screwed up the grub configuration on a BIOS multiboot system after a Fedora upgrade. Is the GRUB "rescue" menu entry ever useful in resolving problems? It's probably ten years or more, since I tried to used it. Nowadays, "rescue" is among the things I usually remove first from installations. Ralf ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: are there typical ways Fedora tends to break?
On 2022-07-15 11:41, Chris Murphy wrote: Is the GRUB "rescue" menu entry ever useful in resolving problems? I think I've used it once when I moved a hard drive or possibly a disk image to another computer. The problem is that it never gets updated, so by the time you need it, it's several releases old and might not even work with the installed system. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: how to setup a bridge interface bridged to wireless?
On 2022-07-15 11:34, Sbob wrote: I need to setup a bridge interface, bridged to my wireless interface. Can someone point me to how to do this? The simple answer is that you can't do that. No bridging to wireless. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: cpan build perl-PDL-Graphics-PLplot
On 2022-07-15 14:35, Patrick Dupre wrote:
I am trying to obtain perl-PDL-Graphics-PLplot
This package was retired a long time ago in Fedora because it failed to
build.
https://src.fedoraproject.org/rpms/perl-PDL-Graphics-PLplot
callback.c: In function 'labelfunc_callback':
callback.c:243:3: error: format not a string literal and no format arguments
[-Werror=format-security]
243 | snprintf( label_text, length, (char *)SvPV_nolen(ST(0)) );
| ^~~~
cc1: some warnings being treated as errors
This is bad code. You will need to figure out how to disable that
compiler option ("-Werror=format-security").
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: custom '.local' folder - ?
On 15Jul2022 16:12, lejeczek wrote: >would anybody know if user's '.local' folder, its path & name are >configurable in some way? >Perhaps by a var or/and os-wide configs? Maybe not, but nothing stops you making it, or particular things inside it, symlinks to better locations. My local machine: [~]fleet2*> ls -ld .local drwxr-xr-x 3 cameron cameron 96 27 Jun 2020 .local [~]fleet2*> L .local/ total 0 drwxr-xr-x3 cameron cameron96 27 Jun 2020 . drwxr-sr-x+ 223 cameron cameron 7136 16 Jul 08:22 .. drwxr-xr-x5 cameron cameron 160 26 Jul 2021 share [~]fleet2*> L .local/share total 0 drwxr-xr-x 5 cameron cameron 160 26 Jul 2021 . drwxr-xr-x 3 cameron cameron 96 27 Jun 2020 .. drwxr-xr-x 3 cameron cameron 96 27 Jun 2020 direnv drwx-- 4 cameron cameron 128 26 Jul 2021 fish lrwxrwxr-x 1 cameron cameron 12 14 Aug 2020 vt -> ../../var/vt I keep a lot of things in ~/var, a lot of configs in ~/rc, yea, even to the point of: [~]fleet2*> ls -ld .config lrwxrwxr-x 1 cameron staff 2 11 May 2017 .config -> rc and machine specific configs in ~/rc-local. Cheers, Cameron Simpson ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
cpan build perl-PDL-Graphics-PLplot
Hello,
I am trying to obtain perl-PDL-Graphics-PLplot
I downloaded
PDL-Graphics-PLplot-0.81.tar.gz
run
cpanspec PDL-Graphics-PLplot-0.81.tar.gz
to obtain the spec file
run
rpmbuild -bb perl-PDL-Graphics-PLplot.spec
Name: perl-PDL-Graphics-PLplot
Version:0.81
Release:1%{?dist}
Summary:PDL::Graphics::PLplot Perl module
License:CHECK(Distributable)
Group: Development/Libraries
URL:http://search.cpan.org/dist/PDL-Graphics-PLplot/
Source0:
http://www.cpan.org/modules/by-module/PDL/PDL-Graphics-PLplot-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildRequires: perl(ExtUtils::MakeMaker)
BuildRequires: perl(PDL)
BuildRequires: perl(Test::More) >= 0.88
Requires: perl(PDL)
Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo
$version))
%description
The interface consists of two levels. A low level interface which maps
closely to the PLplot C interface, and a high level, object-oriented
interface which is easier to use.
%prep
%setup -q -n PDL-Graphics-PLplot-%{version}
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor OPTIMIZE="$RPM_OPT_FLAGS"
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
find $RPM_BUILD_ROOT -type f -name '*.bs' -size 0 -exec rm -f {} \;
find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2>/dev/null \;
%{_fixperms} $RPM_BUILD_ROOT/*
%check
make test
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
%doc Changes META.json plplot.pd README
%{perl_vendorarch}/auto/*
%{perl_vendorarch}/PDL*
%{_mandir}/man3/*
%changelog
* Fri Jul 15 2022 Patrick Dupre 0.81-1
- Specfile autogenerated by cpanspec 1.78.
///
but I get:
setting SOURCE_DATE_EPOCH=1657843200
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.Y8RjCw
+ umask 022
+ cd /home/pdupre/rpmbuild/BUILD
+ cd /home/pdupre/rpmbuild/BUILD
+ rm -rf PDL-Graphics-PLplot-0.81
+ /usr/bin/gzip -dc
/home/pdupre/rpmbuild/SOURCES/PDL-Graphics-PLplot-0.81.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd PDL-Graphics-PLplot-0.81
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.iPMqZz
+ umask 022
+ cd /home/pdupre/rpmbuild/BUILD
+ CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
+ export CFLAGS
+ CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
+ export CXXFLAGS
+ FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-I/usr/lib64/gfortran/modules'
+ export FFLAGS
+ FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection
-I/usr/lib64/gfortran/modules'
+ export FCFLAGS
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now
-specs=/usr/lib/rpm/redhat/redhat-hardened-ld
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1
-Wl,-dT,/home/pdupre/rpmbuild/BUILD/PDL-Graphics-PLplot-0.81/.package_note-perl-PDL-Graphics-PLplot-0.81-1.fc36.x86_64.ld'
+ export LDFLAGS
+ LT_SYS_LIBRARY_PATH=/usr/lib64:
+ export LT_SYS_LIBRARY_PATH
+ CC=gcc
+ export CC
+ CXX=g++
+ export CXX
+ '[' -f /usr/lib/rpm/generate-rpm-note.sh ']'
+ /usr/lib/rpm/generate-rpm-note.sh perl-PDL-Graphics-PLplot 0.81-1.fc36 x86_64
+ cd PDL-Graphics-PLplot-0.81
+ /usr/bin/perl Makefile.PL INSTALLDIRS=vendor 'OPTIMIZE=-O2 -flto=auto
-ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall
-Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64
Re: are there typical ways Fedora tends to break?
On 7/15/22 12:41, Chris Murphy wrote: Is the GRUB "rescue" menu entry ever useful in resolving problems? I've rarely had to use that option, but I can best describe my experiences by quoting Captain Corcoran: "Hardly ever!" ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: are there typical ways Fedora tends to break?
On Fri, 15 Jul 2022 14:41:09 -0400 Chris Murphy wrote: > Is the GRUB "rescue" menu entry ever useful in resolving problems? I've never had any use for it. I tend to boot off a USB stick if I want to investigate a problem independent of the current software. > failure patterns that you tend to see The only consistent failure pattern I see is a new install locking up due to nouveau driver problems when web browsing. I always go with the default nouveau drivers when I install a new fedora version and for several years now, my system has always experienced these total lock up failures within a week, usually within 2 hours. They disappear once I install the rpmfusion nvidia drivers. (The failure is always a sudden lock up, leaving no clues in log files because the whole system is frozen, I'm only sure it is nouveau because it goes away when I switch to nvidia). Far less frequently I'll find that my wireless keyboard isn't talking following a reboot of a new kernel, only occasionally happens on new kernels, not consistent. A complete power cycle fixes it, but so does unplugging and plugging back in the USB dongle (which now sits out front in an easily reachable position on a hub :-). The only other consistent failures I see are user errors because I never read the release notes till I have to because I can't get sound to work when I then find pulse is gone and pipewire is the new thing and the config info I copied from previous system is wrong (just to pick a recent example, disappearing ifcfg file support in networking is another one). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: are there typical ways Fedora tends to break?
My impression is that audio has been install time problematic since F34. i always do a fresh install rather than update. overall workstation has been stellar despite its current EOL status. On Fri, Jul 15, 2022 at 11:43 AM Chris Murphy wrote: > Hi, > > I have a request for list regulars. > > The Fedora Workstation working group is curious if there's any pattern > or categorization how Fedora installations typically break. i.e. the > installation is successful, the system has been updated multiple times > successfully, and then for whatever reason it breaks. > > Are most failures hardware related? This could be broken down into > hard failure (drive or logic board failed) and soft failure (some > hardware configuration change and reverting the change resolves the > problem). > > What portion of the failures are early boot failures? (Defined as > bootloader, kernel, or early initramfs failures. But excludes being > landed at a dracut prompt.) > > What portion of the failures land the user at a dracut shell? > > What portion of the failures does the user get to a graphical shell > but can't login? > > What portion of the failures can the user login but there's some sort > of anomalous behavior? > > What portion of all failures are fixable without reinstalling? > > Is the GRUB "rescue" menu entry ever useful in resolving problems? > > Could everyone reading this try booting the "rescue" menu entry and > describe what happens? How does the actual behavior compare to what > you thought would happen? > > The questions list is not complete, feel free to add your own > categorizations / failure patterns that you tend to see. > > Thanks! > > > > -- > Chris Murphy > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
are there typical ways Fedora tends to break?
Hi, I have a request for list regulars. The Fedora Workstation working group is curious if there's any pattern or categorization how Fedora installations typically break. i.e. the installation is successful, the system has been updated multiple times successfully, and then for whatever reason it breaks. Are most failures hardware related? This could be broken down into hard failure (drive or logic board failed) and soft failure (some hardware configuration change and reverting the change resolves the problem). What portion of the failures are early boot failures? (Defined as bootloader, kernel, or early initramfs failures. But excludes being landed at a dracut prompt.) What portion of the failures land the user at a dracut shell? What portion of the failures does the user get to a graphical shell but can't login? What portion of the failures can the user login but there's some sort of anomalous behavior? What portion of all failures are fixable without reinstalling? Is the GRUB "rescue" menu entry ever useful in resolving problems? Could everyone reading this try booting the "rescue" menu entry and describe what happens? How does the actual behavior compare to what you thought would happen? The questions list is not complete, feel free to add your own categorizations / failure patterns that you tend to see. Thanks! -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
how to setup a bridge interface bridged to wireless?
All; I need to setup a bridge interface, bridged to my wireless interface. Can someone point me to how to do this? Thanks in advance ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Login screen users - hide - ?
lejeczek: >> Is it possible to hide somehow a user from Login screen, so >> such user/account would not show up in that list of users? Tom Horsley: > Probably depends on the login manager. I use sddm and have > this in /etc/sddm.conf > > # Comma-separated list of users that should not be listed > HideUsers=backup I concur. Long ago, I'd used one with very old Gnome that did allow you to hide some users, then they took that feature away. I don't know if they put it back, because I use Mate, now, and I haven't tried to see if it hides some users. Some installations provider a configuration app for modifying the login screen, some do not. At times I'd done that kind of thing by adjusting a config file by hand. In the past various features have come and then died, like being able to put user face pictures in the list of users on the login screen (the feature still being there, but didn't actually work). Sometimes I'd removed the list of users, and just had a login screen where you typed your username, then typed your password. You don't have to use the default login manager for your desktop. Though you may find your desktop made use of some features that only it set triggered. -- uname -rsvp Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
custom '.local' folder - ?
Hi guys would anybody know if user's '.local' folder, its path & name are configurable in some way? Perhaps by a var or/and os-wide configs? many thanks, L. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Login screen users - hide - ?
On 08/07/2022 12:50, Tom Horsley wrote: On Fri, 8 Jul 2022 12:26:58 +0100 lejeczek via users wrote: Is it possible to hide somehow a user from Login screen, so such user/account would not show up in that list of users? Probably depends on the login manager. I use sddm and have this in /etc/sddm.conf # Comma-separated list of users that should not be listed HideUsers=backup In my case "backup" is a rsync only user I have for doing backups. I'd guess other login managers have similar features, though perhaps configured entirely differently. Gnome/gdm has this: -> $ dconf read /org/gnome/login-screen/disable-user-list true so not selectively but choose users all, yet that too does not seem to work. thanks, L. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
