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 579146 - crashes on opening edit profile
crashes on opening edit profile
Status: RESOLVED DUPLICATE of bug 524204
Product: sabayon
Classification: Deprecated
Component: general
unspecified
Other All
: Normal critical
: ---
Assigned To: Maintainers of sabayon
Maintainers of sabayon
: 579149 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-04-16 13:12 UTC by Michel van Leeuwen
Modified: 2009-07-13 15:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Michel van Leeuwen 2009-04-16 13:12:15 UTC 
Steps to reproduce:
1. dutch version of ubuntu 8.10
2. profile editor crashes after adding a new profile, than push the edit button
3. window visible: keeps gray, a cross (mousepointer) show, than crashes



Stack trace:
===== BEGIN MILESTONES (/usr/bin/sabayon) =====
MainThread 2009/04/16 13:52:00.2910 (admin-tool): Creating profiles dialog
MainThread 2009/04/16 13:52:00.6689 (admin-tool): Starting main loop
MainThread 2009/04/16 13:52:15.6320 (admin-tool): Got fatal error: sabayon-session exited with a FATAL ERROR (exit code 1)
MainThread 2009/04/16 13:52:15.7589 (admin-tool): Terminating main loop
MainThread 2009/04/16 13:52:15.7590 (admin-tool): Exiting abnormally; dumping log due to a fatal error
===== END MILESTONES (/usr/bin/sabayon) =====
===== BEGIN RING BUFFER (/usr/bin/sabayon) =====
MainThread 2009/04/16 13:52:00.2910 (admin-tool): Creating profiles dialog
MainThread 2009/04/16 13:52:00.6689 (admin-tool): Starting main loop
MainThread 2009/04/16 13:52:11.4025 (USER): Starting to edit profile 'developer'
MainThread 2009/04/16 13:52:15.6320 (admin-tool): Got fatal error: sabayon-session exited with a FATAL ERROR (exit code 1)
MainThread 2009/04/16 13:52:15.7563 (USER): Finishing editing profile
MainThread 2009/04/16 13:52:15.7589 (admin-tool): Terminating main loop
MainThread 2009/04/16 13:52:15.7590 (admin-tool): Exiting abnormally; dumping log due to a fatal error
===== END RING BUFFER (/usr/bin/sabayon) =====


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

[debug log]
max lines = 1000

Other information:
Comment 1 palfrey 2009-04-22 11:44:17 UTC 
*** Bug 579149 has been marked as a duplicate of this bug. ***
Comment 2 Dariusz 2009-05-11 08:52:08 UTC 
I also observe the same on Ubuntu8.10 en:

===== BEGIN MILESTONES (/usr/bin/sabayon) =====
MainThread 2009/05/11 09:06:38.3705 (admin-tool): Creating profiles dialog
MainThread 2009/05/11 09:06:40.2686 (admin-tool): Starting main loop
MainThread 2009/05/11 09:06:55.9358 (admin-tool): ========== BEGIN SABAYON-SESSION LOG ==========
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
Xlib:  extension "RANDR" missing on display ":1.0".
/etc/profile: 3: source: not found
/etc/profile: 12: shopt: not found
/etc/profile: 13: shopt: not found
The program '-c' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 83 error_code 1 request_code 18 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
===== BEGIN MILESTONES (/usr/lib/sabayon/sabayon-session) =====
MainThread 2009/05/11 09:06:49.2960 (sabayon-session): Starting session window for profile_name='aa', profile_path='/tmp/profile-sabayon-admin--CqqhF.zip', display_number='1'
MainThread 2009/05/11 09:06:49.8801 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'aa', '--admin-log-config=/root/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmphZiI7c']
MainThread 2009/05/11 09:06:50.5084 (proto-session): Finished running sabayon-apply with normal exit status
MainThread 2009/05/11 09:06:52.4982 (sabayon-session): Entering main loop.  Wheeee!
MainThread 2009/05/11 09:06:55.9035 (sabayon-session): Terminating
===== END MILESTONES (/usr/lib/sabayon/sabayon-session) =====
===== BEGIN RING BUFFER (/usr/lib/sabayon/sabayon-session) =====
MainThread 2009/05/11 09:06:49.2960 (sabayon-session): Starting session window for profile_name='aa', profile_path='/tmp/profile-sabayon-admin--CqqhF.zip', display_number='1'
MainThread 2009/05/11 09:06:49.8801 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'aa', '--admin-log-config=/root/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmphZiI7c']
MainThread 2009/05/11 09:06:50.5084 (proto-session): Finished running sabayon-apply with normal exit status
MainThread 2009/05/11 09:06:52.4982 (sabayon-session): Entering main loop.  Wheeee!
MainThread 2009/05/11 09:06:55.9035 (sabayon-session): Terminating
===== END RING BUFFER (/usr/lib/sabayon/sabayon-session) =====


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

[debug log]
max lines = 1000

========== END SABAYON-SESSION LOG ==========
MainThread 2009/05/11 09:06:55.9363 (admin-tool): sabayon-session exited normally
MainThread 2009/05/11 09:07:29.0749 (admin-tool): Got fatal error: sabayon-session exited with a FATAL ERROR (exit code 1)
MainThread 2009/05/11 09:07:29.3270 (admin-tool): Terminating main loop
MainThread 2009/05/11 09:07:29.3271 (admin-tool): Exiting abnormally; dumping log due to a fatal error
===== END MILESTONES (/usr/bin/sabayon) =====
===== BEGIN RING BUFFER (/usr/bin/sabayon) =====
MainThread 2009/05/11 09:06:38.3705 (admin-tool): Creating profiles dialog
MainThread 2009/05/11 09:06:40.2686 (admin-tool): Starting main loop
MainThread 2009/05/11 09:06:46.8295 (USER): Starting to edit profile 'aa'
MainThread 2009/05/11 09:06:55.9358 (admin-tool): ========== BEGIN SABAYON-SESSION LOG ==========
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
Xlib:  extension "RANDR" missing on display ":1.0".
/etc/profile: 3: source: not found
/etc/profile: 12: shopt: not found
/etc/profile: 13: shopt: not found
The program '-c' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 83 error_code 1 request_code 18 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
===== BEGIN MILESTONES (/usr/lib/sabayon/sabayon-session) =====
MainThread 2009/05/11 09:06:49.2960 (sabayon-session): Starting session window for profile_name='aa', profile_path='/tmp/profile-sabayon-admin--CqqhF.zip', display_number='1'
MainThread 2009/05/11 09:06:49.8801 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'aa', '--admin-log-config=/root/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmphZiI7c']
MainThread 2009/05/11 09:06:50.5084 (proto-session): Finished running sabayon-apply with normal exit status
MainThread 2009/05/11 09:06:52.4982 (sabayon-session): Entering main loop.  Wheeee!
MainThread 2009/05/11 09:06:55.9035 (sabayon-session): Terminating
===== END MILESTONES (/usr/lib/sabayon/sabayon-session) =====
===== BEGIN RING BUFFER (/usr/lib/sabayon/sabayon-session) =====
MainThread 2009/05/11 09:06:49.2960 (sabayon-session): Starting session window for profile_name='aa', profile_path='/tmp/profile-sabayon-admin--CqqhF.zip', display_number='1'
MainThread 2009/05/11 09:06:49.8801 (proto-session): Running sabayon-apply: ['/usr/sbin/sabayon-apply', '-s', 'aa', '--admin-log-config=/root/sabayon-debug-log.conf', '--readable-log-config=/tmp/tmphZiI7c']
MainThread 2009/05/11 09:06:50.5084 (proto-session): Finished running sabayon-apply with normal exit status
MainThread 2009/05/11 09:06:52.4982 (sabayon-session): Entering main loop.  Wheeee!
MainThread 2009/05/11 09:06:55.9035 (sabayon-session): Terminating
===== END RING BUFFER (/usr/lib/sabayon/sabayon-session) =====


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

[debug log]
max lines = 1000

========== END SABAYON-SESSION LOG ==========
MainThread 2009/05/11 09:06:55.9363 (admin-tool): sabayon-session exited normally
MainThread 2009/05/11 09:06:56.2593 (USER): Finishing editing profile
MainThread 2009/05/11 09:07:20.3573 (USER): Starting to edit profile 'aa'
MainThread 2009/05/11 09:07:29.0749 (admin-tool): Got fatal error: sabayon-session exited with a FATAL ERROR (exit code 1)
MainThread 2009/05/11 09:07:29.3181 (USER): Finishing editing profile
MainThread 2009/05/11 09:07:29.3270 (admin-tool): Terminating main loop
MainThread 2009/05/11 09:07:29.3271 (admin-tool): Exiting abnormally; dumping log due to a fatal error
===== END RING BUFFER (/usr/bin/sabayon) =====


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

[debug log]
max lines = 1000
Comment 3 André Klapper 2009-07-13 15:48:25 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 524204 ***