I'm not sure if this belongs in here or in "Support"

Hello strangers.

First of all, I’m not a complete Linux virgin, but I am definitely a Linux noob.
Second of all, please note. This Is My Own Fault.

Thinking that the best place to start with a fresh install on a brand-new build would be to learn the package manager, I jumped straight into trying to learn dnf before I read the “Big Fat Warning” and the “ROME major upgrade expected” posts.

I then proceded to do

sudo dnf dsync --allowerasing --refresh

Now I suspect that this may be the cause of some errors / warnings I have since gotten installing packages.

Doing

sudo dnf in wine.znver1

gave me

[MIRROR] libzstd-1.5.7-1-omv2590.znver1.rpm: Curl error (16): Error in the HTTP2 framing layer for ``https://mirror.freedif.org/openmandriva/rolling/repository/znver1/main/release/libzstd-1.5.7-1-omv2590.znver1.rpm``
[MIRROR] wine-10.4-1-omv2590.znver1.rpm: Curl error (16): Error in the HTTP2 framing layer for ``https://mirror.freedif.org/openmandriva/rolling/repository/znver1/main/release/wine-10.4-1-omv2590.znver1.rpm``

during the process, and

warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() insteadwarning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() insteadwarning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.spawn() or rpm.execute() instead
Complete!

When it finished.

And then, installing HDAJackRetask from Discover gave me a
“The PackageKit daemon has crashed”
Pop-up warning.

I also had some weirdness installing ProtonPass (which I didn’t think to record at the time).
The flathub page was reporting “something went wrong”.
Installing it using Flatpak from the CLI (a new thing for me) it got stuck on the 3’rd package then failed.
But, I then installed it from Discover (Which I probably shouldn’t have done ?) and it seemed to complete just fine, and has been working normally since from what I can tell.
I’m not so sure this would be related to any issues caused by having distro synced though.

So, the questions I need to ask are.

  1. Have I missed including anything important in this post? (I did read the “How to get better results” post by ben79, but my mind is like a collander when I’m manic like this)
  2. Are these warnings / errors actually worth worrying myself, and this forum, about?
  3. If so, should this be posted in “Support” as a single post, or as 2, or 3, or 4 posts?
  4. Is my Big Fat Mistake (How could I be so oblivious to something so obvious?) likely to cause more, and more serious, problems down the line? & Would I therefore be better off just reinstalling from scratch right now?

I hope this post didn’t seem too abrupt, or brief to the point of rudeness. It was originally several Kate pages, and a couple of hours, worth of oversharing my tech-life story, but luckily I caught myself and whittled it down to what is, hopefully, just the right amount of pertinent information.

Thank you in advance for any advice you may wish to offer me.

(-:

Hi and welcome!

Mistakes are natural. It is fine.

I am not sure but, are you running Cooker? That is the development version. I tried distro syncronizing it a few days ago and it ended up removing the whole task-plasma6!

Even though I did manage to run it and update it fine before… the second clean baremetal install didn’t go so well.

Back on topic, Rome is usually a slow roll. Updating it should not be an issue, though make sure you have the latest ISO. There are times when the devs are syncing the cooker repositories with the rome ones, at that time it is not a good idea to synchronize. They do inform it here though, so check back often!

If you need maximum stability, do check out Rock. It is a very solid foundation… xD

Have had no problems with it that I didn’t cause to myself.

Best of luck.

Fox

I also see this warnings. As much as I can see it is just deprecation warning for some commands and not affecting the system.

Correct sequence is to run sudo dnf clean all; dnf clean all; before running distro-sync command. You could/should use the ‘System Update’ utility that takes care of it for us.

System updates via Discover is discouraged (although the team is working on that too) but I’m not sure if general software installation is also discouraged. In any case we have DnfDrake for regular packages and FlatDrake for flatpaks which the team may be able to provide better support for.

If any of the application is not working it would be better if you raise issue under ‘Support’. Try ‘System Update’ tool first to properly update your system though.

Edit: It is really difficult to deal with this many problems on one post. I do wish people would not do this. For one thing I am not sure I understand all of what is written so I answer about what I believe I do know. Nonetheless I try to help new users as much as I can to the limits of my knowledge.

  1. [quote=“Mortistik, post:1, topic:8288”]
    Have I missed including anything important in this post?
    [/quote]

This should probably be a Support post not Coffee Break. In Support your first post has a template with questions, the answers help us to help you. For example your first error message shows /rollling/repository and znver1 so we can assume you are using ROME for AMD CPU (newer than 2017). But it is best not to assume things in problem solving.

Are these warnings / errors actually worth worrying myself, and this forum, about?
[/quote]

The Curl error (16): Error in the HTTP2 framing layer for might be temporary. I just checked in a ROME VM and there does not appear to be any systemic problem. sudo dnf in wine works and would install on this system.

You can ignore this one.

This looks like your dnf transaction succeeded.

  1. [quote=“Mortistik, post:1, topic:8288”]
    If so, should this be posted in “Support” as a single post, or as 2, or 3, or 4 posts?
    [/quote]

As stated above in Support. One topic or issue per forum post. Otherwise how would other users find a post about their problem if it is buried in a thread with 3 or 4 issues?

  1. [quote=“Mortistik, post:1, topic:8288”]
    Is my Big Fat Mistake (How could I be so oblivious to something so obvious?) likely to cause more, and more serious, problems down the line? & Would I therefore be better off just reinstalling from scratch right now?
    [/quote]

What mistake? Did the software (wine) install? You can find out if it installed with this command rpm -qa wine. That command will either show the installed version of wine or return nothing.

  1. You did not write a 5th question but:

Slow down
Take some deep breathes
Congratulate yourself on being open to learning.

1 Like

A point of all users especially new users or “Linux noobs” or novices.

This is an example of posting what you think other people need to know instead of posting all the output of a command. Our default repository setup uses multiple mirrors and if one does not work it (called MirrorBits) will automatically redirect to the next mirror that has the correct metadata. So it does happen that there can be errors for a specific mirror but the transaction continues anyway.

Again, (and assuming I understand @Mortistik’s post):

That shows the end of a successfully completed dnf transaction.

Pre Script
I just re-read those last few posts in the major upgrade thread (for something like the fourth time) (while proofreading this before hitting the reply button) and I think I did misinterpret it and dsyncing is actually fine right now!
(FFS, all this was probably for nothing! Ohh well, better to post it anyway and let everyone know I’m a fool up-front rather than try to hide it. lol)
So now you all know, I’m pretty sure this whole thing was much ado about nothing, so if you don’t feel like reading 3ish pages for basically no reason I don’t blame you in the slightest, and apologise again for the time you have already wasted.
I’m going to hit reply on the post, as-is, anyway, since the questions are still basically valid, even if the situation that led me to them was apparently entirely in my mind. So if you feel like spending some time reading it to give some feedback, or even just for a laugh, feel free.

Preface

Firstly, @secretfirefox , @sigvirt , and @ben79 . Thank you all for your time and patience in replying. Please forgive me for I think I am about to waste even more of it.

Secondly, I think I made a mess of that first post, and it came out confusing where I had thought it was clear. My apologies.

Beneath this italicised preface I will try to rework that first post to be better organised and hopefully clearer. (being able to include links now may help in this a little)

Beneath that, I will quote/refer to your replies in order to check my understanding and/or confirm where I think I have answers to any of my questions.

Reworked Post

MSI X870E_Ryzen 5 9950X3d_RX9070XT_ROME_X11_KDE Plasma 6.3.4

I have a handful of hierarchically interrelated questions concerning posting etiquette / best practice within these forums in general, and within the “Support” category in particular.

1. Posts in “Support” should be 1 issue per thread! However, if I have several small issues that seem likely to to be caused by a single, initial mistake/issue, should I still post them separately, or tie them all into a single thread?

2. The smaller issues referred to in Q1 are errors/warnings that may be too minor to be worth posting in “Support” at all. Should I do so anyway?

3. On the other hand, the initial mistake may well cause more, and more serious problems down the line. Should I therefore have posted it, and this whole thread, in “Support” in the first place?

4. Given that this post is not in “Support”, and is not really about the tech issues themselves, it seems posting system specs should not be necessary. On the other hand, it does touch on technical issues, so system specs probably should be included. Should I post those specs or not?
(Note. I decided to meet ½ way and included bare minimum specs at the top)

Details of what led me to these questions

Hopefully I have included just enough detail here, rather than too much, or too little.

re Q1

I have gotten several warnings / errors on installing programs, both through CLI and through Discover. While trying to work through these problems by myself I came across the
Big Fat Warning
pinned thread, which lead me to the
ROME major upgrade expected
thread.

I read the whole thread, and am under the impression that ROME installs are currently (as of the last post) not ready for distro syncing due to currently merging Cooker into ROME. Unfortunately, learning dnf was my first step after installing, and “dsync” was one of the first things I did with it, before even installing those packages.

This led me to strongly suspect that missing that Big Fat Warning was my Big Fat Mistake, and the root cause of at least some of those errors.

Hence the question. Should all of the subsequent issues (listed below) be posted in “Support” in a single thread about prematurely “dsync”ing my ROME install? Or should I separate them all into their own threads?

re Q2

-When I installed ProtonPass using Flatpak from the terminal it stuck on installing the 3rd package then failed.
The Flathub page for the app had, at the time, been returning “Something went wrong”
I then tried installing it using Discover, it completed successfully (was doing this a bad idea given it had already failed from the CLI?)
I didn’t actually think this would be related to the premature distro-sync, given it was using Flatpak, and the wait on distro-sync is, from my understanding, related to renaming dnf packaging under Plasma 5–6.

-I then installed Wine from the CLI.
It returned some Errors and Warnings during the install. I did copy and save those warnings and errors at the time if you want them.
Given that this was directly through the dnf package manager, rather than Flatpak, I thought it might be related to the premature dsync.

-I then tried to install HDAJackRetask using Discover (I was scared of the terminal again by now).
It gave me a warning pop-up that said
”The PackageKit daemon has crashed”
This was when I started looking for answers to all the above errors, and thereby came across the “Big Fat Warning” and “ROME major upgrade” threads.
Given the warnings returned, and the nature of the thread about not syncing ROME, I thought it likely to be related.

Are any of these sub-issues actually serious enough to be worth posting in “Support” at all? What sort of boundaries are there around what’s worth posting in there? I can’t imagine it helpfull if every little quirk or glitch got ANOTHER post in Support, but I suspect that sometimes those little things actually do end up being big things.
At first I thought mine were not, and was not going to worry. Then I found the “major upgrade” thread, and started worrying.

re Q3

-Is upgrading in this period where Cooker is rolled into Rome going to cause worse problems down the line, meaning I should have just posted this whole thing straight into “Support” as a single thread in the first place?
OR
-Is it not that big of a deal, and I just need to run the commands mentioned in the first post of the “major upgrade” thread later? Or is that first post outdated now? (It was posted on Nov. 2022)
OR
-Have; I misinterpreted the “major upgrade” thread completely; and dsync-ing my install was perfectly fine; and all of these tech related questions are frivolous and unnecessary because I’m worrying over literally nothing?

-The real, underlying question is
“If I post something in “Support” that turns out to be essentially frivolous and/or unnecessary, and/or literally nothing, is that bad form / bad etiquette? (Especially given the prominence of the permanent thread about this issue.) Are there potential bars or bans for pointless posting?

Replies to replies

@secretfirefox

I am not sure but, are you running Cooker?

I’m sorry, I had just updated my profile to include ROME before I started this thread and assumed it would somehow display it in my posts. Silly assumption.

There are times when the devs are syncing the cooker repositories with the rome ones, at that time it is not a good idea to synchronise. They do inform it here though, so check back often!

Me finding that thread is sort of what led to this whole debacle of a post /-:

If you need maximum stability, do check out Rock. It is a very solid foundation… xD

I decided to go with OMLx (rather than Bazzite or some such) and specifically ROME, because I want to actually “learn how to Linux”, including recovering from when it becomes unstable.

@sigvirt

Correct sequence is to run sudo dnf clean all; dnf clean all; before running distro-sync command.

I did do
sudo dnf clean all
before dsync ing. Should it actually be
sudo dnf clean all; dnf clean all
Is that not just running the same command twice in one line? Or have I misunderstood what the ; character does?
Any clarity you can offer on this would be welcome.

System updates via Discover is discouraged (although the team is working on that too) but I’m not sure if general software installation is also discouraged

My aim is to learn to do as much as possible through the CLI anyway, starting with all the package management and system update stuff.

In any case we have DnfDrake for regular packages and FlatDrake for flatpaks which the team may be able to provide better support for.

I haven’t seen *FlatDrake* anywhere in the Application Menu, or even mentioned in forums or the wiki (though I have by no means read all of either of these yet), and it doesn’t come up through the “KRunner Settings” search thingy either. To be honest, I have only tried using DnfDrake to search for some packages, and haven’t really explored it properly. Is FlatDrake perhaps folded somewhere into the same GUI as DnfDrake?

@ben79

I am not sure I understand all of what is written

What mistake?

The “Big Fat Mistake” was supposed to refer to me missing the “Big Fat Warning” /-: .

I’m really sorry. I originally wrote that post in Kate using
Markdown Reference
for links, then when I pasted it into the post and hit send it wouldn’t let me use links. Then I didn’t think to check whether it still read clearly without those links to refer to after I removed them.

Not that checking would have helped anyway, I obviously wasn’t very clear in the original post, links or no links )-:
I always have this problem. Attempting to be clear always seems to end in a “wall of text”, then when I try to prune it down to be concise it ends up being utterly UN-clear. That original Kate document was over 2 pages long. Now this current reply is over three pages and has been upgraded to a LibreOffice document.

Confirming Answered Questions

re Q1

Based on

It is really difficult to deal with this many problems on one post. I do wish people would not do this.

It should have been 4 separate posts. However…

As stated above in Support. One topic or issue per forum post. Otherwise how would other users find a post about their problem if it is buried in a thread with 3 or 4 It is really difficult to deal with this many problems on one post.

This was sort of the crux of my dilemma. If I make separate posts/threads for each small issue (potentially non-issue), then the answer could well be within only one of the threads. On the other hand, if I make a single post/thread, then the smaller issues may be missed by others entirely.

Essentially, did I actually have 4 issues, or was it only really 1 (or even 0) issues.

I’m still unsure.

re Q2

Based on

I also see this warnings. As much as I can see it is just deprecation warning for some commands and not affecting the system.

The Curl error (16): Error in the HTTP2 framing layer for might be temporary.

You can ignore this one.

And

This looks like your dnf transaction succeeded.

And also based on the fact that all of the applications are installed, and seem to be running properly (although I’ve never used wine before so I wouldn’t really know if it is)
I think it safe to assume that the answer to Q2 is

“The errors and warnings given when installing Proton Pass and Wine are not actually issues at all, and are probably not worth posting about in Support”
and probably
”Warning and Error messages in the terminal are probably not worth posting about in future, beter to wait until there are actual failurs or usage problems in general”

However, I am still wondering about the pop-up warning “The PackageKit daemon has crashed” from when I installed HDAJackRetask and whether this IS something for a Support post.

re Q3

I am still unsure whether having done the ROME upgrade prematurely is, or is going to be, an issue. I have tried to find the answer in the forums, but I either failed to find it, or didn’t recognise it when I did. So, given that I don’t even know if it IS an issue, I still don’t know whether I should open a Support thread.

re Q4

Still an open question.
Should I post specs in a thread about whether to post questions in the support thread that requires posting specs?

Close

Again, thank you all for your time and effort in reading and responding to this wordy, weirdo’s post. I truly appreciate any time you are willing to spend on this, and hope I have not wasted too much of it.

If it’s any consolation, I started this process at ~9.30 am, it is now 5.49 pm, and I have yet to paste it all into a reply box; check that the markdown formatting looks right; check for spelling; do a final check for clarity; hit the reply button; and do another final check for formatting, spelling and clarity after it hits the page.
I hope it was worth it, and that I have made my queries clearer now.

Thank you again.

:slight_smile:

Ps. It is 7.29 pm and I am FINALLY about to hit the reply button.
LOL

PPs.

Now I’m wondering if posting hypotheticals in the Support category is acceptable.

ie. Something like “If I HAD inadvertently dsync’d my ROME installation during the “major upgrade” cycle, what sort of errors or odd behaviours would alert me to that fact, and how would I go about fixing the mistake?

That is not needed. Just sudo dnf in wine.

Package management with Discover is currently highly experimental and you definitely should not manage your repos with it. KDE themselves do not want that used to manage system level software. It’s meant to behave like Apple’s Appstore and Microsoft’s Store where users can install applications without the need for administrative privileges.

This is the correct way to perform updates on all releases.

This is probably mirror timeouts. The mirror handler selects your closest one and provides the repos from there. Unless there was an error in the install

you don’t need to worry about this. It seems there wasn’t. The deprecated warning is also not a big deal.

We all understand the struggles it takes to get a system set up how you like no matter what one it is. No judgement here. You seem to genuinely want to learn more about what you did and should do, and I respect that. We take great care to make sure things are working so you can just install what you need and get to work (or play). You can always check the operation of the package once it has been installed and see if the program behaves as it should. Don’t worry about asking for help. As long as you want to learn we are willing to teach.

1 Like

This category is probably better than Support. We really need the template to be filled out and a reasonable amount of specific info in that category.

I am glad you got help already, but I just want to reply to your response to me.

Don’t worry. I am glad you seem interested on learning, and willing to take the steps for it. So no worries at all, really. We are not born knowing everything.

Ah, I don’t think you ran into some issue because they sync was happening. ROME has not update in a while, because the devs have a lot of things to work with now. So it is natural. I can only imagine how much work, testing, hair pulling, goes into making a stable system image or update to roll out to people without breaking everything. So, though ROME is rolling, it is not bleeding edge, and that is for stability, and that is great. Do not worry if it takes a while for updates to show up.
(In fact, I am going to move to ROME from Rock soon since I don’t want to reinstall after every major update.)

Ew, Bazzite. xP

But hey, I am sure you can learn how to Linux pretty well here. I am no terminal wizard, but I can do what I need to do most of the time, other wise I am willing to search and learn what I need. So it’s great.
If I may suggest, in your pursuit of ‘learning how to linux’, if you ever decide to venture into testing the development branch, do keep that to a separate SSD (say, if you decide to test and report bugs with Cooker). You still need your main system at the end of the day.

Ah, I saw you were using Discover to update stuff. I noticed that generally Discover doesn’t work for that among many distros, so I usually do updates/package installation through the terminal. It is so handy! I don’t need to search for each thing individually, and it is a major time saver. Don’t know some package name? Do guess, and use Tab for bash auto-completion and see the magic happen. Way better than an app store, for me. Though options are good, I think using the Terminal this way is a great way to ‘learn how to Linux’.

Wishing you the best.

2 Likes

Hi all

Thank you @secretfirefox @zeroability @ben79 and @sigvirt

I appreciate all of your time and effort to help me.

And sorry. I really made a confusing mess of that first post.
And the attempts to make it clearer in the second one only made it needlessly long winded and no less confusing anyway.

Your replies have helped me, especially with the tech related things.

I’m going to make a new post, focussed and short, asking just the one question, which I think I can nail down to just a few sentences now.

And I’m setting a new rule for myself from now on.

No writing posts in a word document and pasting it into the forum reply. If the reply window times-out, it means I am being to long winded and need to try again.

3 Likes

Your sentiment is appreciated and no apology is needed. We would actually prefer more information be provided than less. After all, no one knows your system better than you do because it’s yours.

I sometimes have to brain dump things like this. If it helps you, Discourse saves drafts so you can come back to it and make adjustments at any point before you post it. Sometimes you forgot something and you remember it a day later. It happens to me all the time. There is one such Draft I am composing for the TDE packages soon to be part of Cooker. Even with that buffer, I sometimes get things confused or the keyboard eats my inputs.

We are very understanding when it comes to various communication methods, so don’t be discouraged. The harsh criticism is reserved for the trolls. We set up Coffee break so people can just talk about stuff related to the distro, or not. We can always move a post that belongs in a different category, if needed.

4 Likes