After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 305510 - Trying to run Sabayon from an edit window to edit that same profile causes the edit window to go away
Trying to run Sabayon from an edit window to edit that same profile causes th...
Status: RESOLVED FIXED
Product: sabayon
Classification: Deprecated
Component: general
SVN trunk
Other Linux
: Normal normal
: ---
Assigned To: Maintainers of sabayon
Maintainers of sabayon
Depends on:
Blocks:
 
 
Reported: 2005-05-26 04:28 UTC by Rosanna Yuen
Modified: 2007-09-19 19:52 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Rosanna Yuen 2005-05-26 04:28:52 UTC 
1) Start Sabayon
2) Add new profile
3) Edit profile
4) In edit window, start Sabayon
5) Select the same profile
6) Select "Edit"
7) Window goes away

As to what I expected, I wasn't expecting to be allowed to run Sabayon
recursively.  But I couldn't resist.
Comment 1 Mark McLoughlin 2005-06-07 16:33:57 UTC 
Heh, not entirely sure what we're going to do about this. Perhaps create a dummy
applications menu with <Exclude><Filename>sabayon.desktop</Filename></Exclude>
and use $XDG_CONFIG_DIRS to point to it

Would need to consider how that would interact with any menu editing you do in
the session, though.
Comment 2 Mark McLoughlin 2005-06-09 13:46:33 UTC 
Simpler fix might be to just set an env variable (e.g. $SABAYON_SESSION_RUNNING)
and sabayon might pop up an error dialog if that env variable is set.

(i.e. you get an error dialog if you run Sabayon from within a Sabayon prototype
session)
Comment 3 Mark McLoughlin 2005-06-13 14:49:46 UTC 
Okay, fixed on HEAD now:

2005-06-13  Mark McLoughlin  <markmc@redhat.com>

        Don't allow running Sabayon within a Sabayon session.
        Fixes bug #305510

        * lib/protosession.py:
        (ProtoSession.__start_session): set $SABAYON_SESSION_RUNNING

        * admin-tool/sabayon: pop up an error dialog if
        $SABAYON_SESSION_RUNNING is set.