Ubuntu).
I think the relevant package is x11-common.
The display manager you are using (probably lightdm on Ubuntu, unless
you have deliberately installed a closer-to-upstream GNOME stack) is
also influential.
> I believe that
> gnome-session should be aware from which binary the output is c
Hi fellow Gnome Devs,
Since my most recent system upgrade (Ubuntu 16.04, ~gnome 3.18) I got
systemd and I noticed that _most_ gnome-session logs now endup in the
journal rather then in ~/.xsession-errors where it used to be stored
before (Ubuntu 14.04, ~gnome 3.10).
I generally like
On Tue, Jan 21, 2014 at 10:08 AM, Lennart Poettering
mzta...@0pointer.de wrote:
Heya,
I am typing this from a GNOME session that actually uses a kdbus user
bus instead of a dbus-daemon session bus (and also a kdbus system
bus). With this mail I'd like to start discussion of the changes I'd
On Tue, 28.01.14 09:56, Sriram Ramkrishna (s...@ramkrishna.me) wrote:
c) gnome-session currently has some special .desktop file support that
it uses to set up the session and run it (parsing stuff from
/etc/xdg/autostart). For that it forks off all
processes on its own
On Tue, Jan 28, 2014 at 12:28 PM, Lennart Poettering mzta...@0pointer.dewrote:
On Tue, 28.01.14 09:56, Sriram Ramkrishna (s...@ramkrishna.me) wrote:
c) gnome-session currently has some special .desktop file support that
it uses to set up the session and run it (parsing stuff from
On Wed, 22.01.14 21:31, Matthias Clasen (matthias.cla...@gmail.com) wrote:
The only thing I've seen in this discussion that I disagree with is the
idea to make the distinction between starting a service (in the background)
and launching the application (opening a window) implicit, by looking
Matthias Clasen matthias.cla...@gmail.com wrote:
...
The only thing I've seen in this discussion that I disagree with is the idea
to make the distinction between starting a service (in the background) and
launching the application (opening a window) implicit, by looking at
somewhat obscure
Hello Lennart, all,
Love the initiative here.
On 21/01/14 18:08, Lennart Poettering wrote:
So, the way I'd like this all to work is by simply emphasizing .desktop
files and bus activation a lot more, without actually emphasizing
systemd as backend implementation of anything. As both
On Wed, 22.01.14 11:01, Martyn Russell (mar...@lanedo.com) wrote:
Heya,
a) I'd like to see native D-Bus .service activation files deprecated
in dbus. Instead, for the user/session bus, I'd like to see
everything moved to .desktop files. Ryan recently extended the
.desktop spec
On Tue, Jan 21, 2014 at 1:08 PM, Lennart Poettering mzta...@0pointer.dewrote:
Heya,
I am typing this from a GNOME session that actually uses a kdbus user
bus instead of a dbus-daemon session bus (and also a kdbus system
bus). With this mail I'd like to start discussion of the changes I'd
Heya,
I am typing this from a GNOME session that actually uses a kdbus user
bus instead of a dbus-daemon session bus (and also a kdbus system
bus). With this mail I'd like to start discussion of the changes I'd
like to propose for GNOME to make this work a bit more smoothly.
As you might now
I've been working on getting systemd --user to support running my
session too, and I have a few comments from testing.
2014/1/21 Lennart Poettering mzta...@0pointer.de:
Heya,
I am typing this from a GNOME session that actually uses a kdbus user
bus instead of a dbus-daemon session bus
On Tue, 21.01.14 19:49, Giovanni Campagna (scampa.giova...@gmail.com) wrote:
I am typing this from a GNOME session that actually uses a kdbus user
bus instead of a dbus-daemon session bus (and also a kdbus system
bus). With this mail I'd like to start discussion of the changes I'd
like
On 21/01/14 19:22, Lennart Poettering wrote:
On Tue, 21.01.14 19:49, Giovanni Campagna (scampa.giova...@gmail.com) wrote:
This won't work, because the Exec line from .service has a different
purpose than the Exec line from .desktop: the first runs the service,
the second activates the
On Tue, 21.01.14 20:21, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
On 21/01/14 19:22, Lennart Poettering wrote:
On Tue, 21.01.14 19:49, Giovanni Campagna (scampa.giova...@gmail.com) wrote:
This won't work, because the Exec line from .service has a different
purpose than the
Hi,
I don't find how to launch gnome-panel when gnome starts. I have tried
to add an entry in gnome-session-properties without success.
So far I run: gnome-panel --replace after gnome has started.
Thanks for your help.
Marc
___
desktop-devel-list
On 14/10/13 13:19, Giovanni Campagna wrote:
2013/10/14 Marc des Garets m...@ttux.net:
Hi,
I don't find how to launch gnome-panel when gnome starts. I have tried to
add an entry in gnome-session-properties without success.
So far I run: gnome-panel --replace after gnome has started.
You
Le dimanche 27 janvier 2013, à 00:30 +0100, Lanoxx a écrit :
Hi,
in the man page of gnome-session I cannot find any explanation or
reference about the following fields in a .session file:
I guess it's best to look at
/usr/share/gnome-session/sessions/gnome.session as an example if the man
On 27/01/13 09:02, Vincent Untz wrote:
Le dimanche 27 janvier 2013, à 00:30 +0100, Lanoxx a écrit :
Hi,
in the man page of gnome-session I cannot find any explanation or
reference about the following fields in a .session file:
I guess it's best to look at
/usr/share/gnome-session/sessions
that?
You can define anything as a task.
So what is a task used for and why whom? Does gnome-session just
simply run any of the specified TASKs?
The idea behind this is to allow alternative software to be used instead
of some default part of GNOME. To be honest, it doesn't make much sense
in GNOME 3
and why would I want to do that?
You can define anything as a task.
So what is a task used for and why whom? Does gnome-session just
simply run any of the specified TASKs?
The idea behind this is to allow alternative software to be used instead
of some default part of GNOME. To be honest
the session not
fail if notify-osd cannot be started. So it's not required, just
recommended.
Does gnome-session hard code the valid provider names somewhere in its
soure, or is this some kind of interface that is known by the TASKS?
No, anything can be used.
What would happen if I just remove
/unstable/gnome-session/debian/scripts/gnome-wm?view=markup
Jeremy
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list
://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gnome-session/debian/scripts/gnome-wm?view=markup
Thanks. My bash skills are not that good, but if I see that right, then
line 33 is only executed if none of the programs in the list of
metacity mutter sawfish was found, right? Wouldnt it make more
Hi friends, I'am trying to develop a management tool for admins, and one of the
thing I need to do is detect when a gnome user start a gnome session, I use the
users command line, but it give all the users that are log in , but I only want
those one that have a gnome session up or X session up
On 03/24/2011 02:50 PM, Colin Walters wrote:
If you maintain a component talking to gnome-session, please look at:
https://bugzilla.gnome.org/show_bug.cgi?id=645690
Looking at this now that bugzilla is back up... What does it have to do
with gnome-session? Is this the right bug?
Cheers
On Sat, Mar 26, 2011 at 2:09 AM, Stef Walter st...@collabora.co.uk wrote:
On 03/24/2011 02:50 PM, Colin Walters wrote:
If you maintain a component talking to gnome-session, please look at:
https://bugzilla.gnome.org/show_bug.cgi?id=645690
Looking at this now that bugzilla is back up... What
Hi,
If you maintain a component talking to gnome-session, please look at:
https://bugzilla.gnome.org/show_bug.cgi?id=645690
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
; --no-prompt doesn't do anything with
--power-off).
Vincent
Le jeudi 24 février 2011, à 22:56 +, William Jon McCann a écrit :
commit 8663860ff44b9a5e441e4909a49eee4cfa08378d
Author: William Jon McCann jmcc...@redhat.com
Date: Thu Feb 24 17:38:13 2011 -0500
rename gnome-session-save
On Mon, 2011-02-28 at 13:56 +0100, Vincent Untz wrote:
Hi,
(I don't want to pick on Jon here; that's just the latest commit like
this one)
I would appreciate if patches could get posted on bugzilla for review,
instead of being committed directly without asking maintainers. I know
I'm not
On Mon, 2011-02-28 at 12:58 +, Bastien Nocera wrote:
On Mon, 2011-02-28 at 13:56 +0100, Vincent Untz wrote:
Hi,
(I don't want to pick on Jon here; that's just the latest commit like
this one)
I would appreciate if patches could get posted on bugzilla for review,
instead of
Hi Vincent,
I wrote most of gnome-session and am still listed as a maintainer.
So, I'm not sure what the problem is. I agree in principle with using
code review which is why I asked a few people to look the patch over
for me.
This is crunch time man. It is all about getting it done.
Thanks
Le lundi 28 février 2011, à 08:25 -0500, William Jon McCann a écrit :
Hi Vincent,
I wrote most of gnome-session and am still listed as a maintainer.
Actually, Dan wrote most of the new gnome-session ;-)
And I'm sorry, but with two commits in 2011, two commits in 2010 and 10
commits in 2009
Le lundi 28 février 2011, à 14:53 +0100, Vincent Untz a écrit :
Also, as I wrote, it's not about you specifically, I've seen this from
several people.
Just to make it extremely clear: this is the issue I have. If people
want to step up and become co-maintainers of my modules, then please
state
Hi,
I've created a gnome-2-32 branch for gnome-session in order to make
gtk3 build fixes on master.
See
https://bugzilla.gnome.org/show_bug.cgi?id=630277
For more details.
--Ray
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http
Hi, folks.
There's a bug in vino which talks about vino service restarting in a
loop, due to it being saved in the session AND being part of
auto-started applications.
http://bugzilla.gnome.org/show_bug.cgi?id=579355
My guess is that it's not a vino bug, but a gnome-session one, as it
affects
===
--- data/gnome-session.schemas.in (revisione 5252)
+++ data/gnome-session.schemas.in (copia locale)
@@ -47,18 +47,6 @@
/locale
/schema
schema
- key/schemas/apps/gnome-session/options/logout_option/key
- applyto/apps/gnome-session/options
Dan Winship wrote:
Matthias Clasen wrote:
Sounds fine to me to change the wrong key name. But is the description
factually true ? The last time I checked, gnome-session would not
bring
nautilus back when I killed it, until I added the autorestart key to
the nautilus desktop file.
It's
Ghee Teo wrote:
Dan Winship wrote:
Matthias Clasen wrote:
Sounds fine to me to change the wrong key name. But is the description
factually true ? The last time I checked, gnome-session would not
bring
nautilus back when I killed it, until I added the autorestart key to
the nautilus
under
/desktop/gnome/session/required_components). To be a required
component of the session means that removing a required
component from a running session (for instance killing related
process), gnome-session will start it next time you log in
anyway
.
(Each element names a key under
/desktop/gnome/session/required_components). To be a required
component of the session means that removing a required
component from a running session (for instance killing related
process), gnome-session will start it next time
Il giorno ven, 13/02/2009 alle 16.27 -0500, Dan Winship ha scritto:
Besides the - - _ fix, I'd just change the end to will
automatically add the required components back to the session at login
time if they do get removed. (ie, add at login time)
Applied on svn, thanks.
In gnome-session schema file there is a string that we forgot to fix:
List of components that are required as part of the session.
(Each element names a key under
/desktop/gnome/session/required-components.) The Session
Preferences will not normally allow users
Il giorno gio, 12/02/2009 alle 20.42 +0100, Luca Ferretti ha scritto:
PS also note that /schemas/apps/gnome-session/options/logout_option
GConf key is no longer used (it refers to old, all-in-one logout
dialog). Should we add a deprecated label in short description and
change the long
2009/2/12 Luca Ferretti elle@libero.it:
In gnome-session schema file there is a string that we forgot to fix:
List of components that are required as part of the session.
(Each element names a key under
/desktop/gnome/session/required-components.) The Session
Il giorno gio, 12/02/2009 alle 14.49 -0500, Matthias Clasen ha scritto:
2009/2/12 Luca Ferretti elle@libero.it:
In gnome-session schema file there is a string that we forgot to fix:
List of components that are required as part of the session.
(Each element names a key
Matthias Clasen wrote:
Sounds fine to me to change the wrong key name. But is the description
factually true ? The last time I checked, gnome-session would not
bring
nautilus back when I killed it, until I added the autorestart key to
the nautilus desktop file.
It's poorly-worded. It's
Hi,
2009/2/12 Luca Ferretti elle@libero.it:
Il giorno gio, 12/02/2009 alle 20.42 +0100, Luca Ferretti ha scritto:
PS also note that /schemas/apps/gnome-session/options/logout_option
GConf key is no longer used (it refers to old, all-in-one logout
dialog). Should we add a deprecated label
Hi.
2009/2/12 Luca Ferretti elle@libero.it:
Il giorno gio, 12/02/2009 alle 14.49 -0500, Matthias Clasen ha scritto:
2009/2/12 Luca Ferretti elle@libero.it:
In gnome-session schema file there is a string that we forgot to fix:
List of components that are required as part
Hi,
2009/2/12 Luca Ferretti elle@libero.it:
In gnome-session schema file there is a string that we forgot to fix:
List of components that are required as part of the session.
(Each element names a key under
/desktop/gnome/session/required-components.) The Session
Hi, folks.
What's the status of dbus interface for gnome session clients? I recall
it was unstable for 2.24, and it would be ready for 2.26.
This is important because we can drop EggSM and GnomeProgram from our
modules.
Cheers,
--
Jonh Wendell
http://www.bani.com.br
Hi all,
I've branched gnome-session for GNOME 2.24. The branch name is the usual
gnome-2-24.
Note that there was some changes that were not for 2.24 in trunk, so I
had to branch from revision 5150. This means that one translation (sv)
has been updated in trunk but not in gnome-2-24. Daniel, I
On Sat, 2008-06-28 at 17:44 +0200, Patryk Zawadzki wrote:
The point is XRender is close to its
tenth birthday yet still no one seems to care.
Except that it's rendering your entire desktop the way you can't do
without it?
--
behdad
http://behdad.org/
Those who would give up Essential
On Sat, Jun 28, 2008 at 7:15 PM, Behdad Esfahbod [EMAIL PROTECTED] wrote:
On Sat, 2008-06-28 at 17:44 +0200, Patryk Zawadzki wrote:
The point is XRender is close to its
tenth birthday yet still no one seems to care.
Except that it's rendering your entire desktop the way you can't do
without
Hi,
On Thu, Jun 26, 2008 at 11:43 AM, Patryk Zawadzki [EMAIL PROTECTED] wrote:
Metacity's compositor works pretty well here except for slow workspace
switching.
That should be addressed separately by switching from many-desktops
mode to small-viewport-over-a-large-desktop mode. Then you can
2008/6/27 Andrew Cowie [EMAIL PROTECTED]:
I've been very happy with stable and trunk Metacity with compositing
enabled, but the 2-3 second pause to redraw windows when changing
workspaces is really staggering.
Complain to the developers of your X driver to make their XRender faster.
I don't
session management,
I am totally ok with it as I choosed to test gnome-session 2.23; my
comments here are just ouf of fear users, when 2.24 is released, would
get the same problems.
Frederic
[1] http://bugzilla.gnome.org/show_bug.cgi?id=536685
Le jeudi 26 juin 2008, à 13:32 -0500, Diego Escalante Urrelo a écrit :
On 6/26/08, David Zeuthen [EMAIL PROTECTED] wrote:
On Thu, 2008-06-26 at 14:16 +0200, Rodrigo Moya wrote:
KDE applications are still using XSMP AFAIK, so we'll need to support
it in some way
We do? What happens
Get a better kernel then ;-). On a more serious note, didn't the recent
Firefox 3 O_SYNC fiasco on Linux make some file system developers
realize some short comings of current state of the kernel? If so,
Synchronous I/O is *very* slow but you need to discuss that mostly with
hardware vendors
On Fri, 2008-06-27 at 09:36 +0100, Alan Cox wrote:
That is why we have fsync/fdatasync and thread creation...
Yeah, if they were correctly implemented. But firefox fsync'ing its
sqlite db makes the whole system unusable for up to 20 seconds.
--
behdad
http://behdad.org/
Those who would
On Thu, 26 Jun 2008 16:02:24 -0600, Iain * [EMAIL PROTECTED] wrote:
On Thu, Jun 26, 2008 at 10:49 PM, Patryk Zawadzki [EMAIL PROTECTED]
wrote:
Nah, one thing about a compositor is that it keeps off-screen copies
of all the windows so it does not have to invalidate regions when the
stacking
Thanks for your email, I just asked yesterday morning Vincent about
the status of the dbus-based branch and this answers my questions.
William Jon McCann wrote:
I agree with that. Logout handling is broken too. The XSMP protocol
not only allows applications to be notified on logout (aka
On Wed, 2008-06-25 at 19:07 -0400, William Jon McCann wrote:
Hi,
Dan Winship and Lucas Rocha have done a nice job revamping the
gnome-session codebase. It was a meritorious task. You can read
about the design here:
http://live.gnome.org/SessionManagement/NewGnomeSession
What do you
On Thu, 2008-06-26 at 12:41 +1200, Callum McKenzie wrote:
On Thu, June 26, 2008 11:07 am, William Jon McCann wrote:
I don't think these are sufficient reasons to continue to solely rely
on XSMP. We can do these very well using D-Bus.
Can I assume from your use of the word solely that
Apropos, since we are talking about session management here: have you
guys ever thought of reuseíng upstart for managing session processes?
My thoughts exactly. We should at least talk to the upstart guys about
what code we can share.
___
I'm sorry if I missed something (I just woke up and my eyes and brain
aren't at 100% yet)...
Doing the startup in phases like that sounds to me to be suboptimal.
If we're halting the startup of a whole Desktop (or even Panel)
process just because we don't have a WM ready, it's going to add a lot
On Thu, Jun 26, 2008 at 3:43 PM, Alexander Jones [EMAIL PROTECTED] wrote:
* Currently, gnome-terminal starts up before the WM and if you run a
compositing WM, you get an RGB window unless you close it and open it
again.
That's because the gnome-terminal crew did an awesome job making sure
it
Agreed, we need to move towards expecting Composited as default and
Direct as a niche case, but this was just an example. :)
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
2008/6/26 Mathias Hasselmann [EMAIL PROTECTED]:
Am Donnerstag, den 26.06.2008, 15:28 +0100 schrieb Alexander Jones:
Agreed, we need to move towards expecting Composited as default and
Direct as a niche case, but this was just an example. :)
Guess Metacity's compositor needs to become much
On Thu, 2008-06-26 at 17:28 +0200, Patryk Zawadzki wrote:
2008/6/26 Mathias Hasselmann [EMAIL PROTECTED]:
Am Donnerstag, den 26.06.2008, 15:28 +0100 schrieb Alexander Jones:
Agreed, we need to move towards expecting Composited as default and
Direct as a niche case, but this was just an
On Thu, Jun 26, 2008 at 5:37 PM, Jürg Billeter [EMAIL PROTECTED] wrote:
On Thu, 2008-06-26 at 17:28 +0200, Patryk Zawadzki wrote:
* replacing the current compositor with a GL-based one; or
Please don't. I really want compositing but I can't use a GL-based one
on all systems, as for example
Hi,
Jürg Billeter wrote:
I really want compositing but I can't use a GL-based one
on all systems, as for example even with some recent Intel desktop
mainboards you can't have DRI with a screen area larger than 2048x2048,
which is easily reached with two monitors.
I don't mean to be
Hi,
On Thu, 2008-06-26 at 17:55 +0200, Dave Neary wrote:
Jürg Billeter wrote:
I really want compositing but I can't use a GL-based one
on all systems, as for example even with some recent Intel desktop
mainboards you can't have DRI with a screen area larger than 2048x2048,
which is
of a compositor is
translucency, everything else is just extra guff.
(Ironically, its working perfectly except for translucent windows...)
But none of this is relevent to the gnome-session discussion, so we
shall move it to a seperate thread.
iain
On Thu, 2008-06-26 at 14:16 +0200, Rodrigo Moya wrote:
KDE applications are still using XSMP AFAIK, so we'll need to support
it in some way
We do? What happens if we decide not to?
David
___
desktop-devel-list mailing list
On Thu, Jun 26, 2008 at 6:25 PM, Iain * [EMAIL PROTECTED] wrote:
If you are one of those people with a crap graphics card (or drivers)
I have been working on getting a strange hybrid compositor working
that I'm assuming should be much faster
so that you can have simple compositing to give
of this is relevent to the gnome-session discussion, so we
shall move it to a seperate thread.
Have you looked at xcompmgr? it might be a good starting point. I have
somewhere a hacked up version of xcompmgr which has some extra features.
Let me know if you'd like it.
And although you think
I don't mean to be impertinent, but isn't any screen bigger than
2048x2048 a major edge case? It's like desktop apps that only work on
screens bigger than 640x480... who cares at this stage? By the time
that's anything bug an edge case, won't the hardware have caught up?
It's far from an edge
On Thu, 2008-06-26 at 20:09 +0300, Karl Lattimer wrote:
I'm assuming you've turned on the appropriate xorg configuration
options to enable the correct acceleration
and none of that helped? I forget what they are, but I'm sure someone
will chime in.
ching
Section Extensions
On Thu, 2008-06-26 at 18:57 +0100, Ross Burton wrote:
On Thu, 2008-06-26 at 20:09 +0300, Karl Lattimer wrote:
I'm assuming you've turned on the appropriate xorg configuration
options to enable the correct acceleration
and none of that helped? I forget what they are, but I'm sure someone
On 6/26/08, David Zeuthen [EMAIL PROTECTED] wrote:
On Thu, 2008-06-26 at 14:16 +0200, Rodrigo Moya wrote:
KDE applications are still using XSMP AFAIK, so we'll need to support
it in some way
We do? What happens if we decide not to?
Tell them we are now using a better idea and that they
Am Donnerstag, den 26.06.2008, 17:55 +0200 schrieb Dave Neary:
Hi,
Jürg Billeter wrote:
I really want compositing but I can't use a GL-based one
on all systems, as for example even with some recent Intel desktop
mainboards you can't have DRI with a screen area larger than 2048x2048,
2008/6/26 Mathias Hasselmann [EMAIL PROTECTED]:
Laptop with 1280x768 wides screen LCD plus external monitor or projector
with 1024x768 resolution gives 2304x768 pixels. This setup absolutely
doesn't look exotic for me, but requires more than 2048 horizontal
pixels. When writing this I am
On Thu, 2008-06-26 at 18:02 +0100, Alan Cox wrote:
It's far from an edge case. Any situation with two monitors side by side
of 1024 pixel width causes the problem. Thats a pretty normal setup for
anyone doing art design, engineering or similar work.
Indeed.
(And yes I agree the
, composition managers would be
default those days. At least with Intel cards - AFAIK - composition is
far too slow still to be activated by default. Well, and those cards
are pretty common those days.
But none of this is relevent to the gnome-session discussion, so we
shall move it to a seperate
On Thu, Jun 26, 2008 at 6:13 PM, Patryk Zawadzki [EMAIL PROTECTED] wrote:
I'd say for me the only essential feature of a compositor is not
watching the goddamn windows redraw each time you switch apps and
workspaces.
Then you don't need a compositor
Turn it off. problem solved.
On Thu, Jun 26, 2008 at 6:09 PM, Karl Lattimer [EMAIL PROTECTED] wrote:
Have you looked at xcompmgr? it might be a good starting point. I have
somewhere a hacked up version of xcompmgr which has some extra features.
Let me know if you'd like it.
Good idea, wish I'd thought of that first...
David Zeuthen wrote:
KDE applications are still using XSMP AFAIK, so we'll need to support
it in some way
We do? What happens if we decide not to?
Yes we do; at least I believe so. I won't complain about my xterms as
they may be considered a legacy application but modern applications
On Thu, Jun 26, 2008 at 11:41 PM, Iain * [EMAIL PROTECTED] wrote:
On Thu, Jun 26, 2008 at 6:13 PM, Patryk Zawadzki [EMAIL PROTECTED] wrote:
I'd say for me the only essential feature of a compositor is not
watching the goddamn windows redraw each time you switch apps and
workspaces.
Then you
On Thu, Jun 26, 2008 at 10:49 PM, Patryk Zawadzki [EMAIL PROTECTED] wrote:
Nah, one thing about a compositor is that it keeps off-screen copies
of all the windows so it does not have to invalidate regions when the
stacking order changes.
To be totally honest, I've never really thought of that
On Thu, 2008-06-26 at 12:40 -0400, David Zeuthen wrote:
On Thu, 2008-06-26 at 14:16 +0200, Rodrigo Moya wrote:
KDE applications are still using XSMP AFAIK, so we'll need to support
it in some way
We do? What happens if we decide not to?
well, we'll get tons of bug reports about KDE apps
William Jon McCann wrote:
Hi,
Dan Winship and Lucas Rocha have done a nice job revamping the
gnome-session codebase. It was a meritorious task. You can read
about the design here:
http://live.gnome.org/SessionManagement/NewGnomeSession
The new code is much cleaner. Parts of the new design
On Thu, 2008-06-26 at 23:02 +0100, Iain * wrote:
On Thu, Jun 26, 2008 at 10:49 PM, Patryk Zawadzki [EMAIL PROTECTED] wrote:
Nah, one thing about a compositor is that it keeps off-screen copies
of all the windows so it does not have to invalidate regions when the
stacking order changes.
On Thu, 2008-06-26 at 23:02 +0100, Iain * wrote:
On Thu, Jun 26, 2008 at 10:49 PM, Patryk Zawadzki [EMAIL PROTECTED] wrote:
Nah, one thing about a compositor is that it keeps off-screen copies
of all the windows so it does not have to invalidate regions when the
stacking order changes.
On Thu, 2008-06-26 at 23:46 +0200, Frederic Peters wrote:
Yes we do; at least I believe so. I won't complain about my xterms as
they may be considered a legacy application but modern applications
written for the other major free desktop should not be left in the
cold.
Do you have a concrete
On Fri, Jun 27, 2008 at 12:08 AM, Bastien Nocera [EMAIL PROTECTED] wrote:
I think Patryk was thinking more of the case where the application
hangs and doesn't redraw. Which looks really bad. Compositors fix
that.
Exactly - that's the most common scenario - app X is bound to IO and
it won't
On Thu, Jun 26, 2008 at 11:34 PM, Patryk Zawadzki [EMAIL PROTECTED] wrote:
Exactly - that's the most common scenario - app X is bound to IO and
it won't receive redraw requests until another app stops trashing the
disk.
I'd suggest that thats a broken application that should be fixed,
rather
On Fri, Jun 27, 2008 at 12:51 AM, Iain * [EMAIL PROTECTED] wrote:
On Thu, Jun 26, 2008 at 11:34 PM, Patryk Zawadzki [EMAIL PROTECTED] wrote:
Exactly - that's the most common scenario - app X is bound to IO and
it won't receive redraw requests until another app stops trashing the
disk.
I'd
David Zeuthen wrote:
Yes we do; at least I believe so. I won't complain about my xterms as
they may be considered a legacy application but modern applications
written for the other major free desktop should not be left in the
cold.
Do you have a concrete example of a modern desktop
On Thu, Jun 26, 2008 at 11:59 PM, Patryk Zawadzki [EMAIL PROTECTED] wrote:
Well even if you try to read just a 10k file you can get stuck if
another application is causing excessive IO (and I tend to run such
applications). It's hard to delegate each disk operation to a separate
thread just
1 - 100 of 208 matches
Mail list logo
