Bug 743898 - Sabayon crash when trying to edit profile through VNC
Summary: Sabayon crash when trying to edit profile through VNC
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sabayon
Version: 6.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Tomas Smetana
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-06 12:31 UTC by Martin Simon
Modified: 2016-09-20 02:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-14 12:16:57 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Martin Simon 2011-10-06 12:31:09 UTC
Description of problem:
When trying edit sabayon profile through VNC, got fatal error alert and sabayon crashed.

Version-Release number of selected component (if applicable):
sabayon-2.29.92-3.el6

How reproducible:
100%

Steps to Reproduce:
1. Connect to the remote machine through VNC
2. Start Sabayon and create any profile (if you don't have any)
3. Click Edit
  
Actual results:
Fatal error alert followed by crash of sabayon

Expected results:
Opening new window with session and no crash

Additional info:
Terminal output:
"
MainThread 2011/10/06 08:15:59.5590 (admin-tool): Creating profiles dialog
MainThread 2011/10/06 08:15:59.6196 (admin-tool): Starting main loop
MainThread 2011/10/06 08:16:02.0610 (USER): Starting to edit profile 'aaa'
No protocol specified
Traceback (most recent call last):
  File "/usr/libexec/sabayon-session", line 26, in <module>
    import gtk
  File "/usr/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py", line 64, in <module>
    _init()
  File "/usr/lib/python2.6/site-packages/gtk-2.0/gtk/__init__.py", line 52, in _init
    _gtk.init_check()
RuntimeError: could not open display
MainThread 2011/10/06 08:16:02.3410 (admin-tool): Got fatal error: sabayon-session exited with a FATAL ERROR (exit code 1)
MainThread 2011/10/06 08:16:02.6255 (USER): Finishing editing profile
MainThread 2011/10/06 08:16:02.6262 (admin-tool): Terminating main loop
MainThread 2011/10/06 08:16:02.6262 (admin-tool): Exiting abnormally; dumping log due to a fatal error
Dumped debug log to /root/sabayon-debug-log-2011-10-06-08-16-02.txt
"

Comment 2 RHEL Program Management 2011-10-06 12:49:13 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Tomáš Bžatek 2011-10-06 13:38:47 UTC
(In reply to comment #0)
> When trying edit sabayon profile through VNC, got fatal error alert and sabayon
> crashed.
Does it work in real X session? Is the VNC session running under ordinary user or root? Do you get consolehelper prompt for root password if VNC is running as user?

> RuntimeError: could not open display
This looks like a Xephyr or a kind of fork issue... If you run `Xephyr :5` (choose the free display number), does it work?

Comment 9 Suzanne Logcher 2012-02-14 23:17:06 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.


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