Re: Network problems with f39
On 12/19/23 01:53, Samuel Sieb wrote: On 12/18/23 22:12, Robert McBroom via users wrote: Upgraded legacy bios laptop from f37 to f39. Use command line boot. User login cycles and returns to login prompt. Can boot system on command line as root. The network does not connect with a dependency failure on NetworkManager. Not cleared on a reinstall of NetworkManager. It's not a NetworkManager issue. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: Start request repeated too quickly. Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: dbus-broker.service: Failed with result 'exit-code'. Dec 18 09:46:38 dv7t.attlocal.net audit: BPF prog-id=74 op=UNLOAD Dec 18 09:46:38 dv7t.attlocal.net systemd[1]: Failed to start dbus-broker.service - D-Bus System Message Bus. This is the problem you need to resolve. I don't know why. You'll need to find out why the dbus broker can't run. I would have expected more details in the log. -- I'm not sure what to look for in the journal. Does this section show the problem? Sequence repeats several times Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Warning -- SELinux targeted policy relabel is required. Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** Relabeling could take a very long time, depending on file Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: *** system size and speed of hard drives. Dec 18 09:27:07 dv7t.attlocal.net selinux-autorelabel[860]: Running: /sbin/fixfiles -T 0 restore Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Looking up NSS user entry for 'systemd-oom'... Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: NSS returned no entry for 'systemd-oom' Dec 18 09:27:08 dv7t.attlocal.net dbus-broker-launch[866]: Invalid user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9: user="systemd-oom" Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started dbus-broker.service - D-Bus System Message Bus. Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 18 09:27:11 dv7t.attlocal.net kernel: kauditd_printk_skb: 15 callbacks suppressed Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1130 audit(1702909631.147:131): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1191]: ERROR launcher_run_child @ ../src/launch/launcher.c +347: Permission denied Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: ERROR service_add @ ../src/launch/service.c +1011: Transport endpoint is not connected Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: launcher_add_services @ ../src/launch/launcher.c +804 Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: launcher_run @ ../src/launch/launcher.c +1415 Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: run @ ../src/launch/main.c +152 Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: main @ ../src/launch/main.c +178 Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[866]: Exiting due to fatal error: -107 Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: dbus-broker.service: Failed with result 'exit-code'. Dec 18 09:27:11 dv7t.attlocal.net audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1131 audit(1702909631.164:132): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dbus-broker comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Dec 18 09:27:11 dv7t.attlocal.net audit: BPF prog-id=57 op=LOAD Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1334 audit(1702909631.171:133): prog-id=57 op=LOAD Dec 18 09:27:11 dv7t.attlocal.net audit: BPF prog-id=56 op=UNLOAD Dec 18 09:27:11 dv7t.attlocal.net kernel: audit: type=1334 audit(1702909631.173:134): prog-id=56 op=UNLOAD Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus... Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1195]: Looking up NSS user entry for 'systemd-oom'... Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1195]: NSS returned no entry for 'systemd-oom' Dec 18 09:27:11 dv7t.attlocal.net dbus-broker-launch[1195]: Invalid user-name in /usr/share/dbus-1/system.d/org.freedesktop.oom1.conf +9: user="systemd-oom" Dec 18 09:27:11 dv7t.attlocal.net systemd[1]: Started
Re: Machine locks on reboot from suspend
Tim: >> Certain suspend modes require a suitable power supply, too. They don't >> switch off fully, some power circuits are required to stay up, and >> supply sufficient current to the motherboard. It also requires all the >> hardware to support suspending, some will not wake up, or wake up in a >> scrambled mode requiring some kind of software reset to be done. And >> the drivers have to support it too, especially if the hardware requires >> resetting during wake. Chris Adams: > This is all 100% standardized, not some magic extra bits as you seem to > imply. Not magic... Switch mode power supplies are notorious for not ageing well (my background is electronics engineering and servicing, I don't think them reliable at all), you can easily end up with a PSU that no-longer keeps things alive over time. Not to mention that while some PC builders will deliberately put a PSU in that's far more than's needed, others do the opposite. Or swap a motherboard and don't think about upgrading the supply, too. It used to be that the stand-by supply really only had to supply a tiny bit of current to keep the keyboard awake for the user to use it to wake up the PC, and perhaps a trickle for the RAM circuitry, too. Now there's more things wanting a stand-by supply. And if you're unlucky enough to have some of that hardware designed by shonky brothers who never cared to iron out the bugs before sale, suspending and waking may be one of unreliable things that was only kinda fixed up by a windows driver update. One experience people have had is that suspending and resuming works for the few minutes they tested it for, but doesn't when the system is left suspended for a long period. That can be a supply that fully shutdown when it shouldn't, or motherboard bugs. I deal with gremlins all the time, and they're ever-present. I find it a refreshing surprise when things "just work." > And for the most part, outside of hardware only found in servers > (e.g. SAS cards and high-speed NICs), the chips and drivers for notebook > and desktop hardware are the same. As I said before, there seems to be a greater expectation of being able to suspend laptop hardware than desktop. It helps desktops that more things are on the motherboard, these days, and all designed and tested together by the manufacturer. Back when everything was a plug-in daughter card, things were very hit and miss. But there's certainly been reports in recent years about PCs mysteriously crashing, that turned out to be related to this: > IIRC Windows 11 defaults to suspending after a relatively brief idle > time now (as does Fedora desktop), so that computer vendors can meet > "green" power requirements. This means that virtually all normal > desktop hardware is expected to fully handle suspend/resume. Which will eventually be a good thing for reliability, but this is quite a recent thing. Not so great for people (as widely reported) who found their PCs locked in a coma when they went away for a while. -- uname -rsvp Linux 3.10.0-1160.105.1.el7.x86_64 #1 SMP Thu Dec 7 15:39:45 UTC 2023 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Machine locks on reboot from suspend
Once upon a time, Tim said: > I got the impression that only laptops seem to have reasonably well > working suspend, and suspect that little effort is put into designing > and testing desktops to suspend well. That may have improved with > increasing demands for so-called green technology. But, in the past > suspending was dire. And I don't recall people really wanting to > suspend desktops. Certainly the windows fraternity was forever > rebooting, and used to the idea that lots of things just don't work. I've been suspending my desktops for years with very little trouble. My only recent annoyance is that my current video card (Radeon RX570) trips something in the kernel to cause it to take 10 seconds to resume (tried to bisect but the issue popped up in the middle of an unrelated issue that broke it completely, so never resolved). And every once in a while (like maybe every couple of months of daily suspend/resume), the atlantic driver for my 10G NIC craps out. > Certain suspend modes require a suitable power supply, too. They don't > switch off fully, some power circuits are required to stay up, and > supply sufficient current to the motherboard. It also requires all the > hardware to support suspending, some will not wake up, or wake up in a > scrambled mode requiring some kind of software reset to be done. And > the drivers have to support it too, especially if the hardware requires > resetting during wake. This is all 100% standardized, not some magic extra bits as you seem to imply. And for the most part, outside of hardware only found in servers (e.g. SAS cards and high-speed NICs), the chips and drivers for notebook and desktop hardware are the same. IIRC Windows 11 defaults to suspending after a relatively brief idle time now (as does Fedora desktop), so that computer vendors can meet "green" power requirements. This means that virtually all normal desktop hardware is expected to fully handle suspend/resume. -- Chris Adams -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Machine locks on reboot from suspend
On Tue, 2023-12-19 at 14:26 -0500, Jeffrey Walton wrote: > Don't suspend. I find it is hit or miss whether things work correctly > with ACPI Sleep States (S0 - S5). In particular, S3 and above. I got the impression that only laptops seem to have reasonably well working suspend, and suspect that little effort is put into designing and testing desktops to suspend well. That may have improved with increasing demands for so-called green technology. But, in the past suspending was dire. And I don't recall people really wanting to suspend desktops. Certainly the windows fraternity was forever rebooting, and used to the idea that lots of things just don't work. Certain suspend modes require a suitable power supply, too. They don't switch off fully, some power circuits are required to stay up, and supply sufficient current to the motherboard. It also requires all the hardware to support suspending, some will not wake up, or wake up in a scrambled mode requiring some kind of software reset to be done. And the drivers have to support it too, especially if the hardware requires resetting during wake. Hibernating, or suspend to disk, was usually reliable. It was basically a RAM dump to disk, then completely switch off. The only tricky bit was waking up had to read the resume information rather than just cold boot. It often had to be manually configured where to read that from. Though, having said all that, did the computer suspend and resume properly in the past? -- NB: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the list. The following system info data is generated fresh for each post: uname -rsvp Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53 UTC 2023 x86_64 -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Gnome's terminal/console fonts ?
On Tue, 2023-12-19 at 09:13 +0100, lejeczek via users wrote: > And my question about _only_ mono fonts being available in Ghome's > terminal (while other terminals choose any font) ? I don't recall Gnome Terminal handling proportional fonts well at any time. They were chooseable, but the rendition is madly spaced apart into a fixed-width grid. Proportional fonts were always going to make a mess in a terminal screen, anyway. There's so many things that need a tabular display to be sanely legible, but the textual output is blankspace tabulated, and that will be inconsistent. -- NB: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the list. The following system info data is generated fresh for each post: uname -rsvp Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53 UTC 2023 x86_64 -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Machine locks on reboot from suspend
On Tue, Dec 19, 2023 at 12:47 PM Matthew Saltzman wrote: > > I have a Dell Precision 5820 Xeon with nVidia GeForce GT 1030 graphics > for video and a Quadro 4000 that I was playing with for GPU algorithms. > I have a fresh (fully updated) install of Fedora 39 with the nouveau > driver. > > When I resume from suspend, no video shows. I can still ssh to the > machine, though. If I issue 'sudo shutdown -r now' from an ssh session, > the machine freezes. I can still ping, but I can't ssh (connection > refused errors). The only way I can regain control of the machine is to > power down by holding down the button on the front of the machine and > start from cold. > > The proprietary nVidia driver doesn't exhibit the same problem. > > In addition to the above, this machine has a problem where on boot, it > doesn't show the menu with kernels to select from. It displays "booting > in insecure mode", then goes directly to booting with the latest > kernel. I haven't changed any grub options since the install and I > don't have this problem on any other machine I use. I can get the menu > with ESC, but I can't figure out why it doesn't display by default. By > now, I do have two kernels installed. > > Any thoughts on a solution? For the first problem, I'm not sure what > component to report on in Bugzilla. Don't suspend. I find it is hit or miss whether things work correctly with ACPI Sleep States (S0 - S5). In particular, S3 and above. Plus, suspending to ram and to disk is considered a security vulnerability. And when you suspend to disk, I believe you need to use LUKS. The vulnerability is why some distros disable suspend out of the box. Jeff -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Machine locks on reboot from suspend
On 12/19/2023 10:46 AM, Matthew Saltzman wrote: The proprietary nVidia driver doesn't exhibit the same problem. You're better off removing those and using the akmods from rpmfusion as you don't have to reinstall the drivers every time you install a new kernel. -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Machine locks on reboot from suspend
I have a Dell Precision 5820 Xeon with nVidia GeForce GT 1030 graphics for video and a Quadro 4000 that I was playing with for GPU algorithms. I have a fresh (fully updated) install of Fedora 39 with the nouveau driver. When I resume from suspend, no video shows. I can still ssh to the machine, though. If I issue 'sudo shutdown -r now' from an ssh session, the machine freezes. I can still ping, but I can't ssh (connection refused errors). The only way I can regain control of the machine is to power down by holding down the button on the front of the machine and start from cold. The proprietary nVidia driver doesn't exhibit the same problem. In addition to the above, this machine has a problem where on boot, it doesn't show the menu with kernels to select from. It displays "booting in insecure mode", then goes directly to booting with the latest kernel. I haven't changed any grub options since the install and I don't have this problem on any other machine I use. I can get the menu with ESC, but I can't figure out why it doesn't display by default. By now, I do have two kernels installed. Any thoughts on a solution? For the first problem, I'm not sure what component to report on in Bugzilla. Thanks for any help. -- Matthew Saltzman School of Mathematical and Statistical Sciences Clemson University mjs AT clemson DOT edu -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Is this possible?: Convert /dev/sdd[1-5] Ext4 => /dev/sdd [btrfs - whole disk] - without losing data in sdd5 (old /home)
ahh the blipvert! On 19/12/2023 11:50, Philip Rhoades via users wrote: People, I have been using Fedora since Core 1 and still have the old HDs and I have kept using ext[234] FSs just for simplicity / consistency up to the current time (F39) - but now I want to experiment with btrfs and I was thinking I could go through the exercise of converting an old SATA boot drive where I am still using /dev/sdd5 (the old /home partition) as one of a few backup partitions / drives for current live data from my workstation and some small servers. At first I was thinking I could delete ext4 parts 1-4, replace them with a new btrfs partition and then maybe somehow use btrfs-convert to integrate the remaining ext4 part 5 into the new part 1? . . but what I really want to do is create a new btrfs using the _whole_ of the disk - but somehow avoid having to spend a LONG time copying back about 4TB (to the 8TB drive) - the only way I could see that possibility working is to somehow do a recovery on the rest of the disk after the newly-created btrfs only takes up part of the beginning of the disk but leaves the old ext4 dirs and files recoverable somehow from near the beginning of the disk to just past halfway on the disk . . This is just an interesting idea for experimenting with - it is not the end of the world if it is not possible or if it might be possible but difficult and I crash the drive in the experiment . . Any feedback / comments from HD gurus appreciated! Thanks, Phil. -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Is this possible?: Convert /dev/sdd[1-5] Ext4 => /dev/sdd [btrfs - whole disk] - without losing data in sdd5 (old /home)
On Tue, Dec 19, 2023 at 7:51 AM Philip Rhoades via users < users@lists.fedoraproject.org> wrote: > People, > > I have been using Fedora since Core 1 and still have the old HDs and I > have kept using ext[234] FSs just for simplicity / consistency up to the > current time (F39) - but now I want to experiment with btrfs and I was > thinking I could go through the exercise of converting an old SATA boot > drive where I am still using /dev/sdd5 (the old /home partition) as one > of a few backup partitions / drives for current live data from my > workstation and some small servers. > > At first I was thinking I could delete ext4 parts 1-4, replace them with > a new btrfs partition and then maybe somehow use btrfs-convert to > integrate the remaining ext4 part 5 into the new part 1? I think the process would be to delete the disposable partitions, expand the remaining partition to the full drive, and then convert. The conversion needs extra space for BTRF metadata, but I think it preserves the existing data blocks. At work we copied data to a (large, striped) filesystem, processed it, and then moved the results to long-term storage, rinse and repeat. We found that drive failure rates increased around end-of-warranty, so I worry about intensive disk activity on older drives pushing them to failure. > . . but what I > really want to do is create a new btrfs using the _whole_ of the disk - > but somehow avoid having to spend a LONG time copying back about 4TB (to > the 8TB drive) - the only way I could see that possibility working is to > somehow do a recovery on the rest of the disk after the newly-created > btrfs only takes up part of the beginning of the disk but leaves the old > ext4 dirs and files recoverable somehow from near the beginning of the > disk to just past halfway on the disk . > My reading of the btrfs-convert man page is that the ext4 data blocks are preserved, so the main concern is to avoid having btrfs metadata fragmented if the free space in the old ext4 partition is fragmented. Filesystem work better when they have plenty of elbow room. -- George N. White III -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Is this possible?: Convert /dev/sdd[1-5] Ext4 => /dev/sdd [btrfs - whole disk] - without losing data in sdd5 (old /home)
People, I have been using Fedora since Core 1 and still have the old HDs and I have kept using ext[234] FSs just for simplicity / consistency up to the current time (F39) - but now I want to experiment with btrfs and I was thinking I could go through the exercise of converting an old SATA boot drive where I am still using /dev/sdd5 (the old /home partition) as one of a few backup partitions / drives for current live data from my workstation and some small servers. At first I was thinking I could delete ext4 parts 1-4, replace them with a new btrfs partition and then maybe somehow use btrfs-convert to integrate the remaining ext4 part 5 into the new part 1? . . but what I really want to do is create a new btrfs using the _whole_ of the disk - but somehow avoid having to spend a LONG time copying back about 4TB (to the 8TB drive) - the only way I could see that possibility working is to somehow do a recovery on the rest of the disk after the newly-created btrfs only takes up part of the beginning of the disk but leaves the old ext4 dirs and files recoverable somehow from near the beginning of the disk to just past halfway on the disk . . This is just an interesting idea for experimenting with - it is not the end of the world if it is not possible or if it might be possible but difficult and I crash the drive in the experiment . . Any feedback / comments from HD gurus appreciated! Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: p...@pricom.com.au -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: f39:: dnfdragora broken
On 13/12/23 05:38, Adrian Sevcenco wrote: Hi! For any kind of selection in installed packages dnfdragora breaks with dnfdaemon AttributeError: 'NoneType' object has no attribute 'replace' AFTER the list is returned in the windown ... is this known? Is there where can i report this on the fedora side? (as the upstream can fary away in version and fixex w.r.t the version packaged) You might need to supply more information on what you are trying to do. I set dnfdragora to only display installed package and clicking on an entry did nothing. I had the double click on an entry the first time to display all the information on the package and there after single clicking on an entry showed all the information. I didn't get any failures as such. regards, Steve Thanks a lot! Adrian -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue OpenPGP_0x594338B1DE179AB2.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature -- ___ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Gnome's terminal/console fonts ?
On 16/12/2023 21:21, George N. White III wrote: On Sat, Dec 16, 2023 at 3:36 AM lejeczek via users wrote: Hi guys. My Gnome's default terminal does only select from _mono_ type of fonts & I remember it could choose any font. Alternative solutions, such a _terminator_ do allow to select any font. In Gnome's terminal 'font scaling' also seems "broken" - certainly on my Fedora - I select "Liberation Mono" and I start size at 6 and keep increasing by small fraction and the font does not seem changing until suddenly, at some given size it "jumps" the size & ... shape too. I do not suppose it's my environment - I've been upgrading my Fedora since... forever, as opposed to "clean" install - and I think it's rather "broken" terminal, but.. I wanted to consult other Fedorians to be sure. Using a fresh install of F39, in Gnome Terminal "Preferences" I selected the "Unnamed" Profile, set "Custom font" to Liberation Mono, and click on the "Custom Font" bar to get a "Choose A Terminal Font" window. The size changes in the window and the terminal also changes to match when I close the "Chose ..." window. I have TrueType Liberation fonts: % fc-list | grep LiberationMono /usr/share/fonts/liberation-mono/LiberationMono-Regular.ttf: Liberation Mono:style=Regular /usr/share/fonts/liberation-mono/LiberationMono-Bold.ttf: Liberation Mono:style=Bold /usr/share/fonts/liberation-mono/LiberationMono-BoldItalic.ttf: Liberation Mono:style=Bold Italic /usr/share/fonts/liberation-mono/LiberationMono-Italic.ttf: Liberation Mono:style=Italic Liberation Mono as the example I might not remembered exactly: some range and no change < 6.366 > changes visibly substantially range no change < 6.875 > again changes visibly quite a bit Also does not seem that "Cell spacing" _width_ works "properly" And my question about _only_ mono fonts being available in Ghome's terminal (while other terminals choose any font) ? 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, report it: https://pagure.io/fedora-infrastructure/new_issue
