elementary
Replies: 3 comments 5 replies
-
|
Posts like this may be cathartic for you, but they're not actionable. If you're experiencing an issue, please file individual issue reports. We have an issue reporting guide here if you need help: https://docs.elementary.io/contributor-guide/feedback/reporting-issues
This is a limitation of X11. We can't fix this until we can run the greeter as part of the Wayland session which means rewriting a whole lot of things. We're getting closer to being able to do this, but there are some accessibility features that are missing in the versions of libraries available to us and we need to write a new on screen keyboard and probably other things. It's a long term goal, but it is not easy to fix.
We don't. The greeter has not been rewritten. We make incremental changes to address feedback, fix issues, add requested features. But we haven't done a rewrite since 2019
I genuinely wish this is how software worked. If you could do this, you would be the world's first trillionaire for sure. All we can do is address reported issues as they come in. I've personally not experienced any slow load times or freezes in the greeter, so it would be really helpful if you could report those issues properly and someone can take a look
This is objectively false. Of the things you mentioned, only the Dock has changed and we had to rewrite the Dock to work with Wayland. A lot of people have worked really hard on the Dock and I don't appreciate you calling it "half baked". This is not a constructive way to participate in this community. Be respectful of the people giving their time to making this software. We forked Shotwell over 11 years ago with Jim's blessing because Yorba was disbanded. Videos is 14 years old and has been the same app the entire time. Screenshot is 9 years old.
We've typically closed dozens of issue reports every month and I get feedback from folks all the time that it's the most solid operating system they've ever used 🤷♀️
Again, if you are experiencing issues, please report them. We can't take action on things that aren't being reported. Issues can be very hardware specific or the result of some system modification or something else that can't be widely reproduced without a detailed report. We want to fix the things you're experiencing, but we can't do that without an issue report |
Beta Was this translation helpful? Give feedback.
-
The only cathartic aspect of this conversation is receiving your arguments that everything is working, when I have two machines running eOS versions that carry on the same bugs and regressions I've shared above. @danirabbit could you describe the QA process before you roll out a new version? Particularly:
Like all of these are core basic functionality, as much as I feel special, idt my setup is so unique that all of these stars align particularly just for me. Fyi all my machines are x1 nano / x1 carbon devices, there's really nothing special hardware-wise there. Please help me understand how the QA processes work at eOS, because it makes little sense for me to contribute back if this is not even part of the software cycle for you guys. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
|
Look, I honestly can't spend a bunch of time justifying myself to you in the hopes you'll file an issue report when there are folks who have already filed reports that I could spend me time working with instead. If you don't want to participate you don't have to. Have a great day |
Beta Was this translation helpful? Give feedback.
-
|
I think you're misunderstanding the importance of the different ways to contribute. I genuinely want to understand how does the team sign off on releases. We can keep you busy with bug reports, but clearly that's not scaling well if every release we need to fix the same issues over and over. As a team leader, I think it's pretty normal to clarify the way your team operates in order to enable contributions beyond bug reports and translations. Nobody is asking you to justify for things beyond your public role/responsibility. |
Beta Was this translation helpful? Give feedback.
-
tbh the bug reports ive filed, theyve been fixed - or if details were needed i provided them (ok i still need to for one in Gala) when working, i make sure it works, reliably, on my end. I cant test for all machines. theres issues i dont know how to fix. Lack of skill, lack of experience, lack of time, lack of interest too - or i cant reproduce them. I then simply take a pass - maybe another dev will know. I cant tell you better than this, on my end and experience. |
Beta Was this translation helpful? Give feedback.
-
|
Came back just to drop this. That's from using the screenshot tool. |
Beta Was this translation helpful? Give feedback.
-
|
Well thats not super helpful. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I think the attitude is very important, and maybe he didn´t say in a nice way, so not good from him, but the important is the message. I've been waiting and trying to use Elementary OS 8 because I like the aesthetics, but it's impossible for me at least, because the installer just crashes. Today I tried again with the lastest release, and the same.... please guys, can you fix this problem? because this is the first thing a person is going to pass to install it, so if we can't install it, we won't use it and we won't give you any feedback apart from the installer. I installed eOS 7.1, but the browser doesn´t open, the store is slow, it doesn´t detect the brightness the screen or the battery charging, so no way i´m using a distro that has so many bugs and the new one I can't use it anyways... What I mean is.. guys, fix the critical bugs please, and open a crowdfunding, make ads, ask for contribute to this to more developers or whatever, because I think you had so much hype in the past and you had even the potential to become the most popular distro for a normal user, but you lost it with this slow and critical fixes... you should write in the blog each 2 weeks with bug fixes and releases, but that´s not happening. Or at least, every month. I hope you th best, but you need to do something else if you really want people to use this OS. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
before I start with my rant, I'd like to thank the team behind for pushing forward this project. I've started using eOS years ago, and it's been one of my favorite OSS projects to watch.
Now the rant. OS v8.0.1 is the most broken releases I've hard in many years! Just period.
I have no idea who runs the QA for these releases but pretty much anything you'd touch is pure frustration!
The never ending greeter fiasco
Every year you guys work on the greeter, and every release ships with a broken greeter! From random freezes when hitting enter to unlock with the password, to abysmal load times after hibernation wakeups, to general freezes with 100% CPU throttling.
@danirabbit I resepect your opinions about UI/UX, but seriously, no one's going to wait for minutes to unlock the screen or keep restarting their laptop to enjoy these design elements you're so big on.
UX-wise, it's just crazy to me that in all these years the screen locking stops my music from playing, disconnects my bluetooth headphones and locks me out while a video is playing.
My only question to you guys here is: wtf do you keep rewriting the same piece of software with every release?! Can you fix it once and forever.
The greeter has two jobs:
Standard apps circus
Standard apps just keep changing with every release! You take off stuff that has been working and replace it with half-baked alternatives just because it's designed by your team. This needs to stop!
From a new docking panel that's half baked, to the Shotwell fork that doesn't work on importing videos/photos properly from cameras, to a basic screen shot tool that just silently crashes on every 2/3 of the times I need to use it.
Oh and the never working video player with mp4, that literally just made me switch back to the upstream standard player: WHICH JUST WORKS!
Can you pls stop experimenting with releases on your userbase?!
You had all of these apps working just fine in the last release. None of this shit works now!
I'm not even going to mention trying to change some of the default shortcuts. Every couple of weeks I need to manually remap my menu launch keys for no clear reasons!
The failed installer
I'm an advanced linux user. And even though I can install my os manually from a minimal CLI environment, I don't want this.
We're in 2025 and if you take eOS and do custom partioning of the disk, the installer with just freeze!
I have no idea why and how this is still possible, but somehow you've managed to break down one of the basic features of the installer. Just go switch off from lvm and make regular native partitions and you should be able to replicate it.
Closing thoughts
I'm on eOS v8 for already about 3 months. It's the first time in many years I'm considering moving away and to stop supporting this project. I have a feeling you guys lost it! I don't know how you measure your success, but if you'll keep ignoring the basic requirements of shipping good software, there's really no point in all of us spending our time on this project.
I hope this rings a bit as a wakeup call, because otherwise this is tiresome.
Hugs
Beta Was this translation helpful? Give feedback.
All reactions