Hello, I'm trying to configure dnf-automatic to automatically upgrade my system
on a daily basis and send me a summary via mailx using my mailgun account.
I have mailx configured and functioning as expected; I can use the 'mail' cmd
to send mail, and have other services using it to send mail.
The following gist has my /etc/dnf/automatic.conf; all I've really changed about
it is to specify to use 'command_email' and uncommented the default 'command_format'
and 'stdin_format', along with setting the from/to emails. I've dropped some
debug logs into the python it runs, and I can see it gets to the emitter fine.
I was even able to send an example email with the emmitter that was constructed
by manually setting the subject and body and running `emitters.commit()`!
The error I'm seeing in the dnf-automatic.service logs is:
Jul 29 06:45:16 <host>dnf-automatic: . . . message not sent.
Is this is a bug or do I have something misconfigured? Would be much appreciated
if someone could point me in the right direction.
I have tried and failed to display a SiXel image on xTerm console.
I have compiled libsixel from source from here:
since the Fedora COPR for libsixel does not
$ sudo dnf copr enable saahriktu/libsixel
Enabling a Copr repository. Please note that this repository is not part
of the main distribution, and quality may vary.
The Fedora Project does not exercise any power over the contents of
this repository beyond the rules outlined in the Copr FAQ at
and packages are not held to any quality or security level.
Please do not file bug reports about these packages in Fedora
Bugzilla. In case of problems, contact the owner of this repository.
Do you really want to enable
copr.fedorainfracloud.org/saahriktu/libsixel? [y/N]: y
Error: This repository does not have any builds yet so you cannot enable
Even though the COPR has 1 build I cannot add it for some reason:
Thus I had to build from source. The build of libsixel completed without
any errors. The complete config.log is here: https://pastebin.com/6c6ExwcL
The current xTerm package in Fedora has SiXel graphics enabled. But even
after doing all that I am unable to get any output:
$ img2sixel /home/sreyan/Pictures/neofetch_test.png
Is this a problem with xTerm or the libsixel library ?
If anyone has any ideas as to were I am going wrong, please let me know.
Can we use the GPU with fedora?
I currently use OpenMP to parallelize my code.
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988
> George N. White III <gnwiii(a)gmail.com> wrote:
> This might be https://bugzilla.redhat.com/show_bug.cgi?id=1750891
Thank you! One of the solutions there--deleting everything in
~/.cache/fontconfig/--seemed to restore my system's ability to see manually
installed fonts without having to re-run 'fc-cache' again. The explanations
described there make sense, too: while I can't be completely sure of the actual
sequence of events, I usually run 'fc-cache -fsv' after manually installing
fonts but I did remember slipping up once a while back and only using the '-fv'
Given that I'm using the same version of fontconfig that supposedly fixed the
problem, I suppose I should add a comment to that bug report that the issue
still exists in some form.
I want to create a bootable USB stick that runs fedora.
I do not want to create a Live-CD USB stick because live-CD
fails to boot on my main PC. And no one seems to know how to
fix this. By using a read-write USB stick I can add in debug
code to the boot process and try to findout what is hanging
the boot process.
What my google-fu is failed to do is figure out how to find
instruction on how to do this with getting live-CD instructions.
I'm guessing that I should be able to use anaconda or dnf to get
the heavy lifting done.
Does anyone know what the steps I need to follow are?