On 08/12/2020 20:50, Sreyan Chakravarty wrote:
On Tue, Dec 8, 2020 at 1:54 PM Ed Greshko <ed.gres...@greshko.com
<mailto:ed.gres...@greshko.com>> wrote:
Well, you didn't "solve" it. You just reverted to a working condition.
You've not identified what
caused the problems.
Exactly.
No, I just updated from within a konsole instance and depending on what
"tracer" tells me
I either logout/login or reboot.
What do you mean by "tracer" ?
tracer is a program to detect stale files.
Tracer determines which applications use outdated files and prints them.
For special kind of applications such as services or daemons, it sug‐
gests a standard command to restart it. Detecting whether file is out‐
dated or not is based on a simple idea.
install python3-tracer
All I get is "Complete" at the end of the dnf update.
You should file a Bugzilla.
Yes, but what information do I put in the bug ?
Links to your journal output as well as the dnf transaction log.
I mean I can't just say my system is broken after a dnf update, can I ?
Probably could use that as the subject.
I don't even know which component is causing the problem. All I know is that
after the update, my KDE is broken.
Looks like sddm would be a place to start. If the person reviewing the BZ
tinks a better component is
in order they will make the change.
---
The key to getting good answers is to ask good questions.
_______________________________________________
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
