headers
GARNOME (bugzilla.gnome.org | 7 Oct 2007 15:55
Picon

[Bug 169564] reduce the number of unused shared libraries dependencies

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=169564

  GARNOME | general | Ver: unspecified

Gilles Dartiguelongue changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gilles.dartiguelongue <at> esiee.
                   |                            |org

-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=169564.
--

-- 
garnome-list mailing list
garnome-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/garnome-list
Permalink | Reply | 0 comments |
headers
Rohan Kulkarni | 11 Oct 2007 18:55
Picon

installing GNOME 2.20

Hello,
         I used garnome to install gnome 2.20.It has been installed in the directory /root/garnome.But still on system startup gnome 2.18.3 is coming up...How do I switch to gnome 2.20 directly after startup?

--

-- 
garnome-list mailing list
garnome-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/garnome-list
Permalink | Reply | 1 comment |
headers
Thomas | 12 Oct 2007 15:35
Picon
Picon

Garnome 2.20.0 - System Administartion

I am a new user of Garnome and a long time user of Slackware. Can anyone
give me some idea on how to get the System->Administration tools to work.
e.g network-admin.
When I try these I get:-
"The configuration could not be loaded"
"You are not allowed to access the system configuration"
The system log file shows:
"Liboobs WARNING The name org.freedesktop.SystemToolsBackends was not
provided in any .service files"

Thankyou in advance

Tom Gibson

--

-- 
garnome-list mailing list
garnome-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/garnome-list
Permalink | Reply | 4 comments |
headers
Karsten Bräckelmann | 12 Oct 2007 22:50
Picon

Re: installing GNOME 2.20


>          I used garnome to install gnome 2.20.It has been installed in
> the directory /root/garnome.But still on system startup gnome 2.18.3
> is coming up...

Do *NOT* build as root!  Please read the README, carefully.

You will not be able to use the build installed inside /root anyway,
without severely compromising your systems security.

You can delete that installed GARNOME, as well as the GARNOME build tree
(the extracted source tarball). You can not use either one as a regular
user -- neither running the installed GNOME, nor re-using the build
tree.

Regarding how to start your installed GNOME 2.20.0 (once you re-built
properly as user), please see the README and the provided documentation
and session script on our project page:
  http://gnome.org/projects/garnome/

> How do I switch to gnome 2.20 directly after startup?

Sounds like you do have some "auto login" enabled? In that case, it may
depend on your distribution. However, I assume they are using the
default GDM session for that user. So logging out, and back in with the
session changed should do it.

  guenther

-- 
char *t="\10pse\0r\0dtu\0. <at> ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

--

-- 
garnome-list mailing list
garnome-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/garnome-list
Permalink | Reply | 0 comments |
headers
GARNOME (bugzilla.gnome.org | 12 Oct 2007 23:12
Picon

[Bug 310474] add a 'root' sanity check to gar.conf.mk

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=310474

  GARNOME | general | Ver: unspecified

------- Comment #3 from Karsten Bräckelmann  2007-10-12 21:12 UTC -------
OK, finally tried implementing this. Turns out it isn't as easy as one would
think... Couple notes and discussion:

It's actually irrelevant which one is used, gar.mk or gar.gnome.mk. I do agree
however, that we do not need another variable. If, for some really strange
reason, a users needs to build as root, he can comment out a single line just
as wekk as set a variable. :)

Some code like this would do. Since it is not a target, it will be evaluated
when reading in the file, and crap out immediately. Regardless, if a target has
been completed before (running as user).

  UID ?= $(shell id -u )

  ifeq (${UID}, 0)
    $(error Cowardly refusing to run with superuser privileges)
  endif

'make' doesn't make it easy to confront the user with a meaningful, unambiguous
and eye-cathing error message. Anyway, figured out how to do that, so the error
message won't get lost in a bunch of 'make' chatter.

There is one tiny downside to this approach, though. Recursive 'make'.

Placing the root sanity check in gar.mk (or gar.gnome.mk) will be evaluated for
each garball. When buidling desktop/ for example (as per the README), this will
result in a single test and immediately crapping out for good -- IFF paranoid-
is being used.

This is due to how the top-level Makefile and the ones in each meta-garball are
calling 'make' recursively for it's contents. Now, the downside when attempting
to build desktop/ with a plain 'install' target as root is, that *each*
desktop/ garball will stop immedietaly with the exact same error message. Since
it is the same with this target and any other general problem, I believe we can
live with that.

(However, there is a possible solution: Including a dedicated sanity check file
from exactly tree top-level files -- gar.mk, category.mk and Makefile. This
just needs to be guarded by an ifndef and defining a variable to prevent
including and evaluating this multiple times, similar to C header includes.
Probably not worth the effort, though.)

Comments? Thoughts?

-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=310474.
--

-- 
garnome-list mailing list
garnome-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/garnome-list
Permalink | Reply | 0 comments |
headers
GARNOME (bugzilla.gnome.org | 13 Oct 2007 00:19
Picon

[Bug 310474] add a 'root' sanity check to gar.conf.mk

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=310474

  GARNOME | general | Ver: unspecified

------- Comment #4 from Karsten Bräckelmann  2007-10-12 22:19 UTC -------
Created an attachment (id=97149)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=97149&action=view)
proposed fix

-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=310474.
--

-- 
garnome-list mailing list
garnome-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/garnome-list
Permalink | Reply | 0 comments |
headers
GARNOME (bugzilla.gnome.org | 13 Oct 2007 00:26
Picon

[Bug 310474] add a 'root' sanity check to gar.conf.mk

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=310474

  GARNOME | general | Ver: unspecified

------- Comment #5 from Karsten Bräckelmann  2007-10-12 22:26 UTC -------
OK, after some discussion on IRC with Joseph:

Not including the second check in category.mk would result in this error be
thrown for each garball in desktop/, when running this:
  make -C desktop/ install

That is, using 'install' instead of 'paranoid-install'. Seems to be quite
common. Instead of 80-odd identical errors, this stops immediately after the
first one. Also useful to prevent *300* such error messages in the case of a
top-level 'make install'...

Downside: To actually build as root, one needs to change 2 files. Not that a
big deal, IMHO. However, much nicer. :)

I decided to go with gar.gnome.mk, because it is less cluttered and more
GARNOME specific anyway.

-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=310474.
--

-- 
garnome-list mailing list
garnome-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/garnome-list
Permalink | Reply | 0 comments |
headers
Peter | 13 Oct 2007 13:14
Picon
Favicon

Re: Garnome 2.20.0 - System Administartion

On Fri, 12 Oct 2007 14:35:00 +0100, Thomas wrote:

> I am a new user of Garnome and a long time user of Slackware. Can anyone
> give me some idea on how to get the System->Administration tools to
> work. e.g network-admin.
> When I try these I get:-
> "The configuration could not be loaded" "You are not allowed to access
> the system configuration" The system log file shows:
> "Liboobs WARNING The name org.freedesktop.SystemToolsBackends was not
> provided in any .service files"
> 
> Thankyou in advance
> 
> Tom Gibson

Sounds like a dbus issue. See the README. While Slackware-12 has dbus, 
garnome installs files in its own $GARNOME/etc and therein lies a problem. 
When the system loads dbus, it will not see the garnome dbus configuration.

In the README there is documentation to work around this.

#!/bin/bash

GARNOME=$HOME/garnome

## Use GARNOME's DBus, HAL, and Avahi

## Fedora users should uncomment this section
#if [ `grep "<user>messagebus</user>" $GARNOME/etc/dbus-1/system.conf` ]; 
then
#       cat $GARNOME/etc/dbus-1/system.conf | \
#       sed 's,<user>messagebus</user>,<user>dbus</user>,' > \
#       $GARNOME/etc/dbus-1/system.conf;
#fi

su -c "pkill dbus; \
       pkill avahi-daemon; \
       pkill avahi-dnsconfd; \
       pkill hald; \
       rm -rf $GARNOME/var/run/messagebus.pid; \
       rm -rf $GARNOME/var/run/avahi-daemon/pid; \
       rm -rf $GARNOME/var/run/haldaemon.pid; \
       $GARNOME/bin/dbus-daemon --system; \
       $GARNOME/sbin/avahi-daemon -D; \
       $GARNOME/sbin/avahi-dnsconfd -D; \
       $GARNOME/sbin/hald"

   Once the DBus, HAL, and Avahi daemons are running you must create a
   garnome-session script to start GARNOME. An example startup script
   would look like:

#!/bin/bash

GARNOME=$HOME/garnome

PATH=$GARNOME/bin:$PATH
LD_LIBRARY_PATH=$GARNOME/lib:$LD_LIBRARY_PATH
PYTHONPATH=$GARNOME/lib/python2.4/site-packages:$GARNOME/lib/python2.4/
site-packages/gtk-2.0
PKG_CONFIG_PATH=$GARNOME/lib/pkgconfig:/usr/lib/pkgconfig
GDK_USE_XFT=1
XDG_DATA_DIRS=$GARNOME/share
XDG_CONFIG_DIRS=$GARNOME/etc/xdg
MANPATH=$GARNOME/man:$MANPATH
DBUS_LAUNCH="$GARNOME/bin/dbus-launch --exit-with-session"

export PATH LD_LIBRARY_PATH PYTHONPATH PKG_CONFIG_PATH \
       GDK_USE_XFT XDG_DATA_DIRS XDG_CONFIG_DIRS MANPATH DBUS_LAUNCH

exec $DBUS_LAUNCH $GARNOME/bin/gnome-session

-- 
Peter

--

-- 
garnome-list mailing list
garnome-list@...
http://mail.gnome.org/mailman/listinfo/garnome-list
Permalink | Reply | 3 comments |
headers
Thomas | 13 Oct 2007 17:34
Picon
Picon

Re: Garnome 2.20.0 - System Administartion


----- Original Message -----
From: "Peter" <sw98234 <at> hotmail.com>
To: <garnome-list <at> gnome.org>
Sent: Saturday, October 13, 2007 12:14 PM
Subject: Re: Garnome 2.20.0 - System Administartion

> On Fri, 12 Oct 2007 14:35:00 +0100, Thomas wrote:
>
> > I am a new user of Garnome and a long time user of Slackware. Can anyone
> > give me some idea on how to get the System->Administration tools to
> > work. e.g network-admin.
> > When I try these I get:-
> > "The configuration could not be loaded" "You are not allowed to access
> > the system configuration" The system log file shows:
> > "Liboobs WARNING The name org.freedesktop.SystemToolsBackends was not
> > provided in any .service files"
> >
> > Thankyou in advance
> >
> > Tom Gibson
>
> Sounds like a dbus issue. See the README. While Slackware-12 has dbus,
> garnome installs files in its own $GARNOME/etc and therein lies a problem.
> When the system loads dbus, it will not see the garnome dbus
configuration.
>
> In the README there is documentation to work around this.
>
> #!/bin/bash
>
> GARNOME=$HOME/garnome
>
> ## Use GARNOME's DBus, HAL, and Avahi
>
> ## Fedora users should uncomment this section
> #if [ `grep "<user>messagebus</user>" $GARNOME/etc/dbus-1/system.conf` ];
> then
> #       cat $GARNOME/etc/dbus-1/system.conf | \
> #       sed 's,<user>messagebus</user>,<user>dbus</user>,' > \
> #       $GARNOME/etc/dbus-1/system.conf;
> #fi
>
> su -c "pkill dbus; \
>        pkill avahi-daemon; \
>        pkill avahi-dnsconfd; \
>        pkill hald; \
>        rm -rf $GARNOME/var/run/messagebus.pid; \
>        rm -rf $GARNOME/var/run/avahi-daemon/pid; \
>        rm -rf $GARNOME/var/run/haldaemon.pid; \
>        $GARNOME/bin/dbus-daemon --system; \
>        $GARNOME/sbin/avahi-daemon -D; \
>        $GARNOME/sbin/avahi-dnsconfd -D; \
>        $GARNOME/sbin/hald"
>
>    Once the DBus, HAL, and Avahi daemons are running you must create a
>    garnome-session script to start GARNOME. An example startup script
>    would look like:
>
> #!/bin/bash
>
> GARNOME=$HOME/garnome
>
> PATH=$GARNOME/bin:$PATH
> LD_LIBRARY_PATH=$GARNOME/lib:$LD_LIBRARY_PATH
> PYTHONPATH=$GARNOME/lib/python2.4/site-packages:$GARNOME/lib/python2.4/
> site-packages/gtk-2.0
> PKG_CONFIG_PATH=$GARNOME/lib/pkgconfig:/usr/lib/pkgconfig
> GDK_USE_XFT=1
> XDG_DATA_DIRS=$GARNOME/share
> XDG_CONFIG_DIRS=$GARNOME/etc/xdg
> MANPATH=$GARNOME/man:$MANPATH
> DBUS_LAUNCH="$GARNOME/bin/dbus-launch --exit-with-session"
>
> export PATH LD_LIBRARY_PATH PYTHONPATH PKG_CONFIG_PATH \
>        GDK_USE_XFT XDG_DATA_DIRS XDG_CONFIG_DIRS MANPATH DBUS_LAUNCH
>
> exec $DBUS_LAUNCH $GARNOME/bin/gnome-session
>
>
>
> --
> Peter
>
> --
> garnome-list mailing list
> garnome-list <at> gnome.org
> http://mail.gnome.org/mailman/listinfo/garnome-list
>
I am certain you are correct. However I had read the README file and I think
I am doing what it says. I have modified the Slackware start-up files in
/etc/rc.d to start the Garnome versions of hal,dbus & avahi. Do I need to
modify the config files in $GARNOME/etc/dbus?  Do I need to define special
users or groups?

Tom Gibson

--

-- 
garnome-list mailing list
garnome-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/garnome-list
Permalink | Reply | 2 comments |
headers
Peter | 13 Oct 2007 22:43
Picon
Favicon

Re: Garnome 2.20.0 - System Administartion

On Sat, 13 Oct 2007 16:34:00 +0100, Thomas wrote:

snip...

>>
> I am certain you are correct. However I had read the README file and I
> think I am doing what it says. I have modified the Slackware start-up
> files in /etc/rc.d to start the Garnome versions of hal,dbus & avahi. Do
> I need to modify the config files in $GARNOME/etc/dbus?  Do I need to
> define special users or groups?
> 
> Tom Gibson

By modifying the Slackware startup files to start garnome files is 
incorrect. They won't start because garnome won't be in the library search 
path. dbus is likely NOT loading.

If you're going to use dbus or hal from slackware, use the originals, do 
not use garnome. That said, follow the readme and do what it says. It does 
not say start dbus, hal, and avahi in your system startup scripts. It says 
to start it as a user after killing off similar system processes.

So
1) kill system dbus, hal, etc.
2) start garnome's dbus, hal, etc.
3) set paths as indicated and start a gnome session.
4) do not use garnome in system startup scripts. garnome is intended to be 
per user.

-- 
Peter

--

-- 
garnome-list mailing list
garnome-list@...
http://mail.gnome.org/mailman/listinfo/garnome-list
Permalink | Reply | 1 comment |

Gmane