@richp I’m not scarred at all. I’ll admit that my BS tolerance is quite low, coming from the swamps of Louisiana. I will also admit that I have called people a lot worse. I thought it was pretty tame, but it offended some folks and for that, I am sorry.
1 Like
@WilsonPhillips It’s important to call’em like you see’em something we brits are not very good at. I try but after rereading my post I realized that I still need to apologize first, so i’m still more english than i would like to admit. And I still think that a good cup of tea solves 90% of all problems and drinking too much coffee causes about the same. You will probably call BS on that.
In my 54 yrs of life experience. Starting out a conversation such as “I really tried” that also includes no actual evidence of trying while stating empty reasons of usability is one of two things.
- A small troll that is mostly a virtue signal to friends and followers to gain clout with them.
- A cry for attention that they didnt really want to try as hard as it required. Because something got hard and it didnt “just work” right out of the box.
If someone’s gonna give up that easy on a distro they should just go back to Windows or Mac cause those “just work”.
In this case I would say it was the first reason. A justification that he was looking for to stick with Arch. Whether it was so he could go back to the Arch friends and family and state a bunch of fallicies about the “unfriendly community” here who didnt try to help (when he didnt ask for it). Only for him to get a pat on the back that Arch is superior to all distros cause it “just works”.
I’m not apologizing for this. I know a troll when I see them.
2 Likes
That’s it, I’m going back to slackware!
3 Likes
Really guys, replace OM/OMLx with Foo in each OP’s message and you’ll get a perfect Arch advertising you can post in any distro forum.
Trust but try yourself.
.
The one I really need is picard
Easy to post in any forum.
Publish a console log is harder instead, especially if you actually did nothing 
Same goes for:
I never posted before because a lot of the issues I had are the same/similar issues that a lot of users are already posting about, and many of the responses boil down to, “We’re working on it.” “We’ll get to it.” etc. etc. I’m not the type to make duplicate posts just to be “seen” or “heard”
Where you won’t find devs’ replies like these?
Everywhere reported issues often are replied “Ok we’ll have a look” or “The issue is being worked”
It’s expected, be it a sort of automatic reply (aka ignore) or genuine statement…
While trying to be neutral responding to the first message, the more the OP posted the more I got convinced of my the original feeling.
2 Likes
Although I don’t have a lot of experience with Linux, I’ve seen this type of comments in the community, and well, throughout my life overall many times.
I think we can all relate to OP’s frustration with using one product that didn’t stood up to our expectations. It’s tough to keep a cool head when dealing with this frustration, I know… on both sides. With no actionable feedback to work on, and not even some proactive troubleshooting to try and work things out. Being empathetic in these situations can go a long way to turn a wrong into a right.
But I know nothing about bots or trolls, so I could be wrong about the best way to handle this online.
2 Likes
I was in the same boat. I had been using Arch for years because it worked well for me, and I like a rolling release. I would still be using it if their politics hadn’t turned me away. I found OM via a Lunduke video. I have managed to get OM to do everything I need so I’m sticking with it. I was very much on the fence for several days and almost went back to Arch.
There are a ton of people here who will gladly help when asked.
3 Likes
I do agree there have been some hiccups form me first coming here and trying the system. I have found a couple things from using this and contiuning with this OS.
First, I do feel the influx of people have created more polish within the system. I feel things are constantly getting better.
Second, I feel some of my issues have been self induced. I feel there were a few things I tried to do that messed with the core system. I made sure I did a CLEAN install and reconfigure things from scratch, Also, I feel I have to lean into using some qt alternatives to the gtk applications I had been using as they seem to work more smoothly within the system. Some of that came since cinnamon is not working at the moment. Though I feel the setup for KDE has been just as nice once I figured the system out.
I know I could have easily gone back to either my Mint or Arch installs, but I figure I needed to stick with my principals and use an OS that doesn’t hate me. I also feel the community here have been inviting and helpful if I had any comments or questions.
5 Likes
Outside of this, where exactly should one report broken packages? I’ve found one or two, but based off of the website I haven’t found anything specifying where these issues should be reported to.
You can report issues in Support if you do not want a GH account, or you can report here:
1 Like
1 Like
You can follow the 2-steps way:
- First please read How to get better results when posting about problems
- Open new topic in Support category so other can discuss and confirm the bug (or you can get useful help)
- If there is not any quick solution then file a bug report at github.
If you don’t have a gh account someone will do for you.
1 Like
Making a forum post about any issues is a good way to start. Github reports like Zeroability linked to is another good option, just try to look for duplicate reports first. Reaching out to other users and devs on the matrix channels can also be helpful.
1 Like
Post issues in Support. If you know how, file a Bug Report on GitHub. If you don’t know how, ask someone to do it for you.
Hint: The first bug report is hard. The second one is easy. 
2 Likes
I would like to respectfully point out that OM is not a product. It is a passion project run by volunteers. In the case of an actual product made available for monetary gain, I absolutely agree with you.
4 Likes
Of course, I didn’t mean to imply otherwise. I’ve experience this myself already twice, one of the best Linux communities that I’ve seen already!
My point was regarding the frustration that people feel when things don’t work as expected. This frustration is very real, just like the passion and pride that people feel when making a prod… something that they have devoted themselves to. What I wanted to say is that we should try to be more empathetic towards people feeling that way because it’s the perfect time to be as understanding as we can.
It’s no excuse to start yelling or claiming stuff out of thin air… of course not. But for those who are willing to help, that’s the best time to keep a cool temper. Frustrated people are not necessarily irrational. The next day, they may be feeling much more willing to collaborate and take the time to answer questions and whatnot, especially when they see that others are putting up with their initial “cries” for help.
I would absolutely slam the door in their faces if the attitude continues, of course
2 Likes
Did anyone ever happen to read this?
Most likely the ‘older’ users did, I can bet.
Old still current sort of “bible”, or vademecum if you prefer.
I believe I should add the link here somewhere in Resources or so 
3 Likes
As a follow up to the picard package not being installable, being the root cause of @eunichron’s issues and my reporting of this bug on their behalf.
As per the GitHub issue update yesterday from @zeroability, an upgraded picard package has been fixed up and is available in the Cooker package repositories for testing, which will eventually migrate to Rome/rolling if no issues are reported by testers.
In less than a day of the package being reported as having issues the OMLx package maintainers have fixed the package up and are waiting on users to test the upgraded package and report any issues.
If nothing had been reported, truth be told a less than 2 minute task to report, this would have remained an issue for the next person who wanted to install picard to come across.
Without issues such as this being reported the package maintainer team will always be unaware of their being any issue with a package.
By being pro-active in reporting issues as you come across them and taking a few minutes out of your day to report them, even by way of a forum post and providing those details here, most package issues can be resolved in a timely manner for the betterment of OMLx and all who choose to use it.
Kudos to the packaging team for the quick turnaround. 
5 Likes
Completely agree with you on the reality of the frustration. Wasn’t trying to derail the thread but this is kind of a pet peeve of mine. Also agree that the more experienced users can make more of an effort to be understanding.
2 Likes