Bug 720478 - sabayon / xguest not configureable
Summary: sabayon / xguest not configureable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: sabayon
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-11 18:44 UTC by Harald Reindl
Modified: 2015-03-03 23:01 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 18:49:47 UTC
Type: ---


Attachments (Terms of Use)

Description Harald Reindl 2011-07-11 18:44:11 UTC
hi

i need to edit the user-profile to get somehow firefox automatically started with some kiosk-extension and there should run a shellscript restarting firefox if it does not running

no idea how do this and "sabayon" only crashs after select "xguest"

where are these configurations?
add a "firefox.desktop" to the "xguest.zip" has no effect

it would be really usefuller to have such a mode instead a full-featured desktop

[root@kiosk sabayon]# cat /root/sabayon-debug-log-2011-07-11-20-37-50.txt
===== BEGIN MILESTONES (/usr/sbin/sabayon) =====
MainThread 2011/07/11 20:37:48.0687 (admin-tool): Creating profiles dialog
MainThread 2011/07/11 20:37:48.0887 (admin-tool): Starting main loop
MainThread 2011/07/11 20:37:50.6637 (admin-tool): Got fatal error: sabayon-session exited with a FATAL ERROR (exit code 1)
MainThread 2011/07/11 20:37:50.8494 (admin-tool): Terminating main loop
MainThread 2011/07/11 20:37:50.8495 (admin-tool): Exiting abnormally; dumping log due to a fatal error
===== END MILESTONES (/usr/sbin/sabayon) =====
===== BEGIN RING BUFFER (/usr/sbin/sabayon) =====
MainThread 2011/07/11 20:37:48.0687 (admin-tool): Creating profiles dialog
MainThread 2011/07/11 20:37:48.0887 (admin-tool): Starting main loop
MainThread 2011/07/11 20:37:49.8788 (USER): Starting to edit profile 'xguest'
MainThread 2011/07/11 20:37:50.6637 (admin-tool): Got fatal error: sabayon-session exited with a FATAL ERROR (exit code 1)
MainThread 2011/07/11 20:37:50.8488 (USER): Finishing editing profile
MainThread 2011/07/11 20:37:50.8494 (admin-tool): Terminating main loop
MainThread 2011/07/11 20:37:50.8495 (admin-tool): Exiting abnormally; dumping log due to a fatal error
===== END RING BUFFER (/usr/sbin/sabayon) =====


This configuration for the debug log can be re-created
by putting the following in /etc/sabayon/sabayon-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines = 1000
[root@kiosk sabayon]#

Comment 1 Fedora End Of Life 2012-08-07 18:49:48 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.