Originally posted by Akka
View Post
Announcement
Collapse
No announcement yet.
Power Management To See Changes In GNOME 3.8
Collapse
X
-
-
Kwin did the same thing when they integrated the screen lock in kwin some times ago. I think phoronix had a article about it?
Leave a comment:
-
Originally posted by quenlinlom View Post>Screensaver now part of the Gnome Shell executable
Why on Earth would you do that?
Leave a comment:
-
Originally posted by quenlinlom View Post>Screensaver now part of the Gnome Shell executable
Why on Earth would you do that?
So now all *box and Unity users would need to use the fugly XScreensaver?
In any case, gnome-screensaver has not been used for a while. It was something for fallback mode. It still can be used by Unity, MATE, etc.
Leave a comment:
-
Originally posted by Massa View PostNope. GNOME doesn't offer a "screensaver" anymore, rather that feature is presented as Lock Screen. The Lock Screen offers several functionality that is present in gnome-shell, like the message tray, top panel and more. As such reimplementing it in a separate module or process would be a waste of resources and poor coding practice.
Of course there's the concern that the Lock Screen process should never crash and reveal your contents but there's a specific helper process dedicated to just that.
Finally, if you're *that* concerned about GNOME being late to implement a *draft* of a fdo spec maybe you should have contribute that code yourself. That's how things get done in software, somebody has to write the code.
Leave a comment:
-
Originally posted by schmalzler View PostWoho, so from 3.8, gnome has one executable, that serves as desktop, window manager, compositor (all these already in <=3.6) and (new) screensaver. Long live modularity!
And the "inhibition" thing drove me crazy when using vlc in kde. All those damn answers from vlc-devs "it's kde's fault, not our", when kde supported the most recent inhibition draft. And now finally gnome will support it - and magically it will work on kde :/
Of course there's the concern that the Lock Screen process should never crash and reveal your contents but there's a specific helper process dedicated to just that.
Finally, if you're *that* concerned about GNOME being late to implement a *draft* of a fdo spec maybe you should have contribute that code yourself. That's how things get done in software, somebody has to write the code.
Leave a comment:
-
Originally posted by liam View PostAh, so since the Qt app, which should work so well across all platforms, has problems on the Qt based desktop, CLEARLY Gnome is to blame.
When are we going to learn? Gnome needs to go. Forget the two state solution. The problem is the two desktop state of affairs.
* gnome did not use it, instead they sticked with xdg-screensaver
* gnome devs say "xdg-screensaver sucks, buggy as hell - use gnome-session-inhibit"
* vlc-dev "than go and report the issues"
* gnome: "yeah we did that, but no response"
* finally - months later
* "come on, why could't we just implement the draft"
* -> instant fix from vlc (they could have fixed this for kde long time ago, but did not want...)
the whole story:
open VLC, load and play a movie longer than the time setting for dimming screen to save power. When reaching that setting the screen dims (or...
just watch how often it got closed and reopened
And no - I won't blame GNOME for buggy vlc, but for not adopting existing WORKING solutions (NIH...)
Leave a comment:
-
Originally posted by Rigaldo View PostAnd I totally agree, a single process doing everything isn't that good .. I don't get why they did that. There's certainly no reason it would cut down on dependencies or something.
Leave a comment:
-
Originally posted by schmalzler View PostWoho, so from 3.8, gnome has one executable, that serves as desktop, window manager, compositor (all these already in <=3.6) and (new) screensaver. Long live modularity!
And the "inhibition" thing drove me crazy when using vlc in kde. All those damn answers from vlc-devs "it's kde's fault, not our", when kde supported the most recent inhibition draft. And now finally gnome will support it - and magically it will work on kde :/
When are we going to learn? Gnome needs to go. Forget the two state solution. The problem is the two desktop state of affairs.
Leave a comment:
-
Originally posted by bwat47 View Postyeah unity actually seems much better in this respect for example. every unity service/lens/indicator etc... are different processes.
Leave a comment:
Leave a comment: