After Europe ditched Windows, China follows suit with its own home-grown Linux distros

Yeah same thing I’m thinking all the same.

Monitor isn’t getting the wake command,
Display drivers don’t get EDID, so the display doesn’t get any signal until the first active pole which is 10 seconds after the machine has actually woken up which then wakes the display, which sends the EDID which initialize the drivers.
No, I'm sure you're right about the overall flow, I meant that I'm not getting locked out of my pc, because I know better than to hit Enter 23 times. I use Ctrl to wake it up for exactly this reason.

I wonder if switching to HDMI would help. It's on DP now for reasons, but it doesn't HAVE to be.
 
No, I'm sure you're right about the overall flow, I meant that I'm not getting locked out of my pc, because I know better than to hit Enter 23 times. I use Ctrl to wake it up for exactly this reason.

I wonder if switching to HDMI would help. It's on DP now for reasons, but it doesn't HAVE to be.
The lockout is a me issue, it’s domained, 3 incorrect logins locks the account for 5 minutes.

I’m thinking we’re having the same issue it just manifests differently for us.

You are in-front of it when it happens, so you have a 30s wait going “why the hell are you so slow”.

Mine are support tickets saying “came back from break and now my account is locked”
 
You'd think after all this time hardware manufacturers would get it right. Well, you'd hope it at least.
 
You'd think after all this time hardware manufacturers would get it right. Well, you'd hope it at least.
PC’s don’t correctly support CEC because computers are classified as a multi-tasking command hub.
To support it on such a device requires dedicated signal pins back to the GPU for each port, that balloons costs for the likes of Nvidia and AMD as the pins off the GPU chip are each very expensive and consume a non proportional amount of physical space.

Things get even more complicated when it comes to multi monitor configurations.

Then you have different power states for different devices with different OS’s each doing it differently. So most have up, Intel seems to have it right but only on the Pro CPUs, and only with select monitors… The Dell Pro series ones for example.

TL;DR
Licensing Fees and Competing Standards make supporting it in the wild too expensive.
 
I wonder if they tried working with the open source developers on the issues or not.
I assume they would have been.... But I am kind of an Ass so maybe I should stop assuming anything.

Anyways, this is the suite they were using.

https://www.collaboraonline.com/collabora-office/

But if you search the issues they reported, you will find people complaining about those same issues going back a solid 4 years.

Microsoft synchronizes the majority of their O365 functionality through OneDrive and SharePoint as a unified interface and hosting mechanism. I don't know of a good Linux-based alternative that does the same, and it would appear that they couldn't either.
 
While I can't read the posts of the user in question as they're on my block list with good reason, the only issue here is MS themselves. Compatibility issues exist between differing versions of MS Office, MS worked to actively manipulate the OOXML standard that would have removed all compatibility issues between office suits once and for all.
 
I wonder if they tried working with the open source developers on the issues or not.
I dunno if you've ever contributed to an OSS project but you'll find that it isn't uncommon to have maintainers that are dickheads and communities that will perpetually bike shed anything they don't like/want. While there are projects out there who badly want and welcome contributions and will change, there's also plenty that have become little cliques and you have a hell of a time getting anything done.

That aside, the "just contribute the change you want" is not something all orgs can do. If they don't have devs, that is a big ask. You are asking them to create a new team, hire people, get them integrated and up to speed, and then have them work on the things they want. Doable, but expensive and time consuming. It's not hard to understand why some orgs when faced with the choice of that, or go to a commercial product that does what you want elect the commercial product.

And if you AREN'T a dev? Forget about it. The answer, almost universally, is "Don't whine, if you want it done, contribute the code!" OSS devs are not interested in just doing things people ask for. It makes sense, they are either doing it for free or doing it because a company does pay them to do it (and thus they are doing what that company wants) but it means that you will have basically 0% success going and saying "Hey here are issues I have, would you be willing to change them?"
 
I assume they would have been.... But I am kind of an Ass so maybe I should stop assuming anything.

Anyways, this is the suite they were using.

https://www.collaboraonline.com/collabora-office/

But if you search the issues they reported, you will find people complaining about those same issues going back a solid 4 years.

Microsoft synchronizes the majority of their O365 functionality through OneDrive and SharePoint as a unified interface and hosting mechanism. I don't know of a good Linux-based alternative that does the same, and it would appear that they couldn't either.

The little bit I read about it is that the attempt was pretty half-hearted. It is entirely possible that the higher ups wanted a trial and whoever was put in charge of it wanted it to fail so they picked something they knew would have problems. Otherwise, why only try one alternative and then pack it in?

I mean, I get why O365 is such a behemoth. It does what large scale organizations want it to do even if it has become a bloated mess. It still does the job. It is hard for an open standard to reach that level of cross-application integration all with cloud storage/linking.
 
The little bit I read about it is that the attempt was pretty half-hearted. It is entirely possible that the higher ups wanted a trial and whoever was put in charge of it wanted it to fail so they picked something they knew would have problems. Otherwise, why only try one alternative and then pack it in?

I mean, I get why O365 is such a behemoth. It does what large scale organizations want it to do even if it has become a bloated mess. It still does the job. It is hard for an open standard to reach that level of cross-application integration all with cloud storage/linking.
A lot of people said that this seems like it was setup to fail. Open Office would have been another good choice for Denmark to try. It's hard to believe we still have problems with something like a word processor?
 
A lot of people said that this seems like it was setup to fail. Open Office would have been another good choice for Denmark to try. It's hard to believe we still have problems with something like a word processor?
Collabora is primarily maintained in Europe, and part of this whole project is to try to move away from software maintained by non-European sources, but Open Office doesn't support collaborative co-authoring of documents, which is a must-have for most government workflows.

And never underestimate the levels of incompetence government office workers are capable of achieving; they will surprise you every time.
 
Collabora is primarily maintained in Europe, and part of this whole project is to try to move away from software maintained by non-European sources, but Open Office doesn't support collaborative co-authoring of documents, which is a must-have for most government workflows.

And never underestimate the levels of incompetence government office workers are capable of achieving; they will surprise you every time.

That's one of the reasons that I figured it was setup to fail because I doubt the IT folks wanted to do the extra work associated with getting open office products to work. So, far easier for them to so the absolute minimum and then point and declare that O365 is the obvious only choice ... because that'll make their life easier.
 
Back
Top