Re: Eel and Nautilus branched
On Mon, 2005-10-03 at 15:37 +0200, Christian Neumair wrote: Am Montag, den 03.10.2005, 09:28 -0400 schrieb Luis Villa: On 10/3/05, Alexander Larsson [EMAIL PROTECTED] wrote: Eel and Nautilus has been branched for 2.13. 2.12.x work go in the gnome-2-12 branch. Any interesting plans for 2.13/14? [1] and more fixes. I'm also quiet optimistic that we can finally get completely rid of bonobo/CORBA and integrate with a new metadata framework [2]. [1] http://live.gnome.org/Nautilus#UpcomingReleases [2] http://freedesktop.org/wiki/Standards/shared-filemetadata-spec I haven't looked in detail at the shared metadata spec, so I can't say much about it, but I'm very vary of switching to something new and unproved. Let me just say that its not at all decided that we will switch to this system. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander LarssonRed Hat, Inc [EMAIL PROTECTED][EMAIL PROTECTED] He's an old-fashioned zombie cat burglar from a doomed world. She's a ditzy paranoid magician's assistant with the power to see death. They fight crime! ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Sound Juicer branched
Sound Juicer has branched for development, stable branch is gnome-2-12 as expected. Ross -- Ross Burton mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Sound Juicer branched
Any plans for 2.13? [Yes, I'm going to ask this every time I see one of these :) Luis On 10/4/05, Ross Burton [EMAIL PROTECTED] wrote: Sound Juicer has branched for development, stable branch is gnome-2-12 as expected. Ross -- Ross Burton mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME-Applets Branched
quote who=Luis Villa In the future, you have updated: http://live.gnome.org/RoadMap to indicate what wonderful new features applets will have in 2.13. Luis (insert air guitar here) EXCELLENT! - Jeff -- linux.conf.au 2006: Dunedin, New Zealand http://linux.conf.au/ The beanbag is a triumph of modern day eclectic colourism... - Catie Flick ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME-Applets Branched
quote who=Luis Villa but your mail client probably looked at my Mail-Followup-To header and complied. :-) gmail displays that to the user as reply-to, which is damned irritating. EVIDENCE OF EVIL! - Jeff -- EuroOSCON: October 17th-20thhttp://conferences.oreillynet.com/eurooscon/ My computer is like 3 lines of code away from attaining sentience. I just have an off-by-one bug somewhere, and that's it: total consciousness. - Nat Friedman ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
MOTD implementation in gnome-session
Hi I have had this patch around for some time, and seems to work pretty well, so sending for comments and/or approval. It just makes gnome-session display the /etc/motd file on startup, using libnotify if available, or an ugly dialog if not. The 2 new files are to be placed in gnome-session/gnome-session -- Rodrigo Moya [EMAIL PROTECTED] ? depcomp ? stamp-h1 ? gnome-session/gsm-motd.c ? gnome-session/gsm-motd.h Index: ChangeLog === RCS file: /cvs/gnome/gnome-session/ChangeLog,v retrieving revision 1.601 diff -u -p -r1.601 ChangeLog --- ChangeLog 24 Sep 2005 14:06:25 - 1.601 +++ ChangeLog 4 Oct 2005 15:35:46 - @@ -1,3 +1,11 @@ +2005-10-04 Rodrigo Moya [EMAIL PROTECTED] + + * configure.in: look for libnotify. + + * gnome-session/Makefile.am: + * gnome-session/main.c (main): + * gnome-session/gsm-motd.[ch]: added MOTD implementation. + 2005-09-24 Erdal Ronahi [EMAIL PROTECTED] * configure.in: Added ku (Kurdish) to ALL_LINGUAS Index: configure.in === RCS file: /cvs/gnome/gnome-session/configure.in,v retrieving revision 1.518 diff -u -p -r1.518 configure.in --- configure.in 24 Sep 2005 14:06:25 - 1.518 +++ configure.in 4 Oct 2005 15:35:46 - @@ -59,6 +59,24 @@ PKG_CHECK_MODULES(SOUND_TEST, $ESOUND_MO PKG_CHECK_MODULES(GNOME_SESSION, gtk+-2.0 = $GTK_REQUIRED libgnomeui-2.0 = $LIBGNOMEUI_REQUIRED $ESOUND_MODULE) +dnl Check if libnotify is present + +LIBNOTIFY_REQUIRED=0.2.1 +LIBNOTIFY_CFLAGS= +LIBNOTIFY_LIBS= +PKG_CHECK_MODULES(LIBNOTIFY, libnotify = $LIBNOTIFY_REQUIRED, + HAVE_LIBNOTIFY=yes, HAVE_LIBNOTIFY=no) + +if test x$HAVE_LIBNOTIFY = xyes; then +AC_DEFINE(HAVE_LIBNOTIFY, 1, [libnotify available]) +AC_MSG_RESULT(available) +else +AC_MSG_RESULT(no) +fi + +AC_SUBST(LIBNOTIFY_CFLAGS) +AC_SUBST(LIBNOTIFY_LIBS) + dnl gconf checks AC_PATH_PROG(GCONFTOOL, gconftool-2, no) Index: gnome-session/Makefile.am === RCS file: /cvs/gnome/gnome-session/gnome-session/Makefile.am,v retrieving revision 1.108 diff -u -p -r1.108 Makefile.am --- gnome-session/Makefile.am 10 Jan 2005 16:36:40 - 1.108 +++ gnome-session/Makefile.am 4 Oct 2005 15:35:47 - @@ -4,6 +4,7 @@ defaultdir = $(datadir)/gnome INCLUDES = \ $(GNOME_SESSION_CFLAGS)\ + $(LIBNOTIFY_CFLAGS)\ $(STANDARD_PROPERTIES_CFLAGS) \ $(WARN_CFLAGS) \ $(DISABLE_DEPRECATED_CFLAGS) \ @@ -26,7 +27,7 @@ STANDARD_PROPERTIES_CFLAGS = -DDATADIR=\$(datadir)\ \ $(NULL) -gnome_session_LDADD = $(X_LIBS) $(GNOME_SESSION_LIBS) $(LIBWRAP_LIBS) +gnome_session_LDADD = $(X_LIBS) $(GNOME_SESSION_LIBS) $(LIBWRAP_LIBS) $(LIBNOTIFY_LIBS) gnome_session_save_LDADD = $(GNOME_SESSION_LIBS) gnome_session_remove_LDADD = $(GNOME_SESSION_LIBS) gnome_session_properties_LDADD = $(GNOME_SESSION_LIBS) @@ -95,6 +96,8 @@ gnome_session_SOURCES = \ gsm-keyring.h \ gsm-gsd.c \ gsm-gsd.h \ + gsm-motd.c \ + gsm-motd.h \ gsm-protocol.c \ gsm-protocol.h \ gsm-remote-desktop.c \ Index: gnome-session/main.c === RCS file: /cvs/gnome/gnome-session/gnome-session/main.c,v retrieving revision 1.67 diff -u -p -r1.67 main.c --- gnome-session/main.c 25 Jul 2005 07:13:53 - 1.67 +++ gnome-session/main.c 4 Oct 2005 15:35:48 - @@ -48,6 +48,7 @@ #include gsm-xrandr.h #include gsm-at-startup.h #include gsm-remote-desktop.h +#include gsm-motd.h /* Flag indicating autosave - user won't be prompted on logout to * save the session */ @@ -461,7 +462,11 @@ main (int argc, char *argv[]) if (a_t_support) /* the ATs are happier if the session has started */ gsm_assistive_technologies_start (); + gsm_motd_start (); + gtk_main (); + + gsm_motd_stop (); gsm_remote_desktop_cleanup (); /* gdm-motd.c - Message of the Day support in gnome-session. Copyright (C) 1998, 1999 Tom Tromey This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */ #include config.h #include glib/gi18n.h #include gtk/gtkmessagedialog.h #include libgnomevfs/gnome-vfs-ops.h #ifdef HAVE_LIBNOTIFY #include libnotify/notify.h #endif #include gsm-motd.h static gchar
Re: MOTD implementation in gnome-session
Hi Rodrigo, On Tue, 2005-10-04 at 17:40 +0200, Rodrigo Moya wrote: Hi I have had this patch around for some time, and seems to work pretty well, so sending for comments and/or approval. It just makes gnome-session display the /etc/motd file on startup, using libnotify if available, or an ugly dialog if not. The 2 new files are to be placed in gnome-session/gnome-session I the first thing worth discussing is why?. Why is it a good idea to show /etc/motd at login? Thanks, Mark. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
quote who=Mark McLoughlin I the first thing worth discussing is why?. Why is it a good idea to show /etc/motd at login? It's very handy for sysadmins to display information to the user at login. I've used zenity and very bad gnome-session hacks for this in the past. Our audience of desktop systems administrators will appreciate the feature. - Jeff -- Ubuntu USA Europe Tour: Oct-Nov 2005http://wiki.ubuntu.com/3BT So between a jazz musician, a murderer, and a congressperson, all called 'Dave Camp', I have a lot of pressure to be evil. - GNOME's Dave Camp ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Tue, 2005-10-04 at 16:48 +0100, Mark McLoughlin wrote: Hi Rodrigo, On Tue, 2005-10-04 at 17:40 +0200, Rodrigo Moya wrote: Hi I have had this patch around for some time, and seems to work pretty well, so sending for comments and/or approval. It just makes gnome-session display the /etc/motd file on startup, using libnotify if available, or an ugly dialog if not. The 2 new files are to be placed in gnome-session/gnome-session I the first thing worth discussing is why?. Why is it a good idea to show /etc/motd at login? for the same reason it is shown when you log in on a terminal. -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
shared memory usage tool - exmap
Hi, I've been working on a tool to help accurately account for shared memory usage amongst multiple processes (following some of the suggestions from the gnome wiki). This was suggested to me as a relevant place to mention it - if not then sorry, and please let me know if any other gnome lists might be appropriate. You can get the current version here: http://homepage.ntlworld.com/john.berthels/exmap (latest version is 0.3). Exmap comprises a kernel loadable module which exports the page identity (pfn) for each page in each VMA of a selected process. A perl/gtk2 app then uses this to walk the process list and build up a picture of how pages are shared amongst mapped files and processes. I've only got UI in for a fairly limited array of stats to far, but hope to add much more (the underlying data structures have significantly more info than is currently exposed). All suggestions on what would other info would be useful (and perhaps ideas on the best UI to present it) gratefully received. I've previously bothered some people off-list about an precursor to this tool (named shmap). Exmap uses a different approach (user space correlation of page pfn's) rather than mapcount from struct page. This appears to resolve the accuracy problems I was having with the previous system. I guess I'm saying it may be worth a second look :-) regards, jb ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Wed, 2005-10-05 at 01:53 +1000, Jeff Waugh wrote: quote who=Mark McLoughlin I the first thing worth discussing is why?. Why is it a good idea to show /etc/motd at login? It's very handy for sysadmins to display information to the user at login. I've used zenity and very bad gnome-session hacks for this in the past. Our audience of desktop systems administrators will appreciate the feature. What kind of information is it especially handy for? Perhaps when you upgrade the desktop and you want to warn people that stuff has changed? But not for stuff like internet will be down for a while today because people may not actually log out that often? Is login the best time to show this information or would you prefer if the user saw it immediately? Would you expect each user to see this information only once? i.e. if you immediately logged out and back in again should you see the same message? If you had several messages over the course of a number of days, would you expect someone who logs in once a week to see all those messages or just the most recent one? Is plain old ASCII the best way to convey this information? Or would it be nice if you could display e.g. HTML? ... I do get that something along these lines would be useful for admins, but it strikes me that some crufty old unix hacker designed /etc/motd at least a couple of decades ago and perhaps we could put some thought into how whether that design best meets a desktop admin's requirements? Cheers, Mark. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
Mark McLoughlin wrote: What kind of information is it especially handy for? Perhaps when you upgrade the desktop and you want to warn people that stuff has changed? But not for stuff like internet will be down for a while today because people may not actually log out that often? At a university, people will typically log in for 15 minutes, check eMail, course sites, etc. Then they will log out and go to class or lunch and come back and hour or two later. In the Windows network at my school they actually fullscreen-mode IE to show this sort of stuff. Extremely annoying. A notification-area message would be infinitely better. Is login the best time to show this information or would you prefer if the user saw it immediately? It might be nice to have GDM display this kind of information, polling for changes to /etc/motd every minute or so instead. Would you expect each user to see this information only once? i.e. if you immediately logged out and back in again should you see the same message? Sure, why not? snip I do get that something along these lines would be useful for admins, but it strikes me that some crufty old unix hacker designed /etc/motd at least a couple of decades ago and perhaps we could put some thought into how whether that design best meets a desktop admin's requirements? I think a very simple solution that is not overcomplicated (like remembering which messages have been read, etc) is a good thing. Anything more complicated is what eMail exists for. --Pat ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Tue, 2005-10-04 at 17:11 +0100, Mark McLoughlin wrote: On Wed, 2005-10-05 at 01:53 +1000, Jeff Waugh wrote: quote who=Mark McLoughlin I the first thing worth discussing is why?. Why is it a good idea to show /etc/motd at login? It's very handy for sysadmins to display information to the user at login. I've used zenity and very bad gnome-session hacks for this in the past. Our audience of desktop systems administrators will appreciate the feature. What kind of information is it especially handy for? Perhaps when you upgrade the desktop and you want to warn people that stuff has changed? But not for stuff like internet will be down for a while today because people may not actually log out that often? Is login the best time to show this information or would you prefer if the user saw it immediately? my patch listens for changes in /etc/motd, so whenever that changes, logged in users would see the message. Would you expect each user to see this information only once? i.e. if you immediately logged out and back in again should you see the same message? that is probably a problem, to show always the same message in systems that have nothing interesting in that file. The problem is how to deal with this? -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Tue, 2005-10-04 at 12:30 -0400, Pat Suwalski wrote: Is login the best time to show this information or would you prefer if the user saw it immediately? It might be nice to have GDM display this kind of information, polling for changes to /etc/motd every minute or so instead. some admins put sensible info on /etc/moptd, so we might not want to show it to anyone getting to the login screen. For that, /etc/issue might be better suited, although that is of no use for most users. -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Tue, 2005-10-04 at 18:24, Rodrigo Moya wrote: that is probably a problem, to show always the same message in systems that have nothing interesting in that file. The problem is how to deal with this? Have some [] Never show me this message again button which remembers the last MOTD datestamp and annoys the user only when it changes. The default should even be to *not* show the MOTD if it hasn't been touched since install time. Xav ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Tue, 2005-10-04 at 09:21 -0700, Sriram Ramkrishna wrote: It would be nice if it detects a change in the MOTD and notifies the user that it's changed (unless of course it already does that). it already does that -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Tue, 2005-10-04 at 18:33 +0200, Vincent Untz wrote: Le mardi 04 octobre 2005 à 17:40 +0200, Rodrigo Moya a écrit : Hi I have had this patch around for some time, and seems to work pretty well, so sending for comments and/or approval. It just makes gnome-session display the /etc/motd file on startup, using libnotify if available, or an ugly dialog if not. The 2 new files are to be placed in gnome-session/gnome-session Btw, there's a bug about this: http://bugzilla.gnome.org/show_bug.cgi?id=159604 Just thought I'd mention it so we can (hopefully) close the bug at the end of the discussion ;-) And Rodrigo can put his patch there as well :) --- Bastien Nocera [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: shared memory usage tool - exmap
On 04 Oct 2005 20:58:59 +0200, Soeren Sandmann [EMAIL PROTECTED] wrote: John Berthels [EMAIL PROTECTED] writes: I guess I'm saying it may be worth a second look :-) Well, it locks up my system hard (2.6.12-1.1446_FC5, ie. Fedora rawhide from a while back which might explain it), but if it does what you say it does it would certainly be a very useful tool to have. Yikes. I'll try and reproduce, (if I can easily set up an Fedora system) At what point did it lock? Running 'exmap.pl'? Could you try a 'make test' with the module loaded and see if you get any failures? Did you get a kernel lock/panic or just very high system load? There can be a short (few seconds) delay on startup, as it scans process and pages - I don't suppose it was that? Were you running a locally built GNOME with unstripped binaries by any chance? Its possible that the Elf symbol loading code is still active (but not currently displayed) and consuming a lot of CPU in that case - I'll take a look. Since I haven't seen it running, this may be irrelevant, but have you considered the approach of having the kernel module export an interface that would map any given pfn to a list of all its mappings? This would give an overview of how the physical RAM is actually shared by applications, rather than showing how an individual application is using physical RAM. (I think both ways of looking at memory would be useful). That is the sort of approach taken. All readable processes are examined, and the pfns correlated between them. For a given vma it might even be possible to tell whether the page had actually been added to the pagetable, or whether it was in the mapping, but not present in the pagetable. (I am possibly revealing my limited understanding of virtual memory here). Having that information would allow us to do things like quantify the cost of having applications still using GtkCList: if only one application used GtkCList, you'd see the physical GtkCList pages mapped into all gtk2 applications, but only present in the pagetable for the CList-using application. Same thing for other rarely-used code, of course. That is certainly within the remit of this tool. I'm working on displaying symbols from shared libraries which are mapped (hence the Elf code mentioned above) I've had that working in a previous version and hope to add it back into the newer exmap version soon, hopefully without the excessive CPU usage. Thanks for trying things out. I'll try and reproduce your problems and any further information gratefully received. regards, jb ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-utils patch
On 10/4/05, Rodrigo Moya [EMAIL PROTECTED] wrote: Hi Just found out a missing argument in a call to g_snprintf, in logview. Attached patch fixes it. Ok to commit? Is bugzilla not working? ;-) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-utils patch
On Tue, 2005-10-04 at 16:27 -0600, Elijah Newren wrote: On 10/4/05, Rodrigo Moya [EMAIL PROTECTED] wrote: Hi Just found out a missing argument in a call to g_snprintf, in logview. Attached patch fixes it. Ok to commit? Is bugzilla not working? ;-) I guess it is, but usually it is much quicker to send the patch directly, and when that doesn't work, add it to bugzilla :) -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-utils patch
On Wed, 2005-10-05 at 00:30 +0200, Rodrigo Moya wrote: On Tue, 2005-10-04 at 16:27 -0600, Elijah Newren wrote: On 10/4/05, Rodrigo Moya [EMAIL PROTECTED] wrote: Hi Just found out a missing argument in a call to g_snprintf, in logview. Attached patch fixes it. Ok to commit? Is bugzilla not working? ;-) I guess it is, but usually it is much quicker to send the patch directly, and when that doesn't work, add it to bugzilla :) Do you really want everyone on this list to be sending patches to applets, utilities, and applications in the Desktop release? Put them in bugzilla, that's what it's there for. --- Bastien Nocera [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-utils patch
On Tue, 2005-10-04 at 23:35 +0100, Bastien Nocera wrote: On Wed, 2005-10-05 at 00:30 +0200, Rodrigo Moya wrote: On Tue, 2005-10-04 at 16:27 -0600, Elijah Newren wrote: On 10/4/05, Rodrigo Moya [EMAIL PROTECTED] wrote: Hi Just found out a missing argument in a call to g_snprintf, in logview. Attached patch fixes it. Ok to commit? Is bugzilla not working? ;-) I guess it is, but usually it is much quicker to send the patch directly, and when that doesn't work, add it to bugzilla :) Do you really want everyone on this list to be sending patches to applets, utilities, and applications in the Desktop release? Put them in bugzilla, that's what it's there for. ok, ok :) -- Rodrigo Moya [EMAIL PROTECTED] ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: MOTD implementation in gnome-session
On Tue, Oct 04, 2005 at 06:43:26PM +0200, Markus Jonsson wrote: What about when the system shuts down? Can I be informed about that? Can I be alerted and logged out in a nice way when someone else runs shutdown -h on the system? If you're in this situation it's most likely not going to be at home and that a sysadmin is going to be doing the reboot. In which case, I would hope he would be using whatever communication method he has (like mail) to say he wants to reboot the box. Or alternatively, Some dork is trying to reboot the system, click if you agree it's okay to reboot? Now how much trouble would that cause? :-) sri ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
