On 06/22/2012 08:16 PM, Omer Akram wrote:
> run 'gnome-settings-daemon' from terminal and see if the menus still
> have icons or not. though the dual menus things is totally new for me.
>
Omer you where right. There is something wrong with:
gnome-settings-daemon
running it in terminal produced this:
gnome-settings-daemon
(gnome-settings-daemon:9577): color-plugin-WARNING **: failed to get
edid: unable to get EDID for output
[1340831700,000,xklavier.c:xkl_engine_start_listen/] The
backend does not require manual layout management - but it is provided
by the application
(gnome-settings-daemon:9577): Gdk-WARNING **: The program
'gnome-settings-daemon' received an X Window System error. This
probably reflects a bug in the program. The error was 'BadMatch
(invalid parameter attributes)'. (Details: serial 1798 error_code 8
request_code 148 minor_code 22) (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
GDK_SYNCHRONIZE environment variable to change this behavior. You can
then get a meaningful backtrace from your debugger if you break on the
gdk_x_error() function.)
On 06/22/2012 08:16 PM, Omer Akram wrote: settings- daemon' from terminal and see if the menus still
> run 'gnome-
> have icons or not. though the dual menus things is totally new for me.
>
Omer you where right. There is something wrong with: daemon
gnome-settings-
running it in terminal produced this:
gnome-settings- daemon
(gnome- settings- daemon: 9577): color-plugin- WARNING **: failed to get 000,xklavier. c:xkl_engine_ start_listen/ ] The
edid: unable to get EDID for output
[1340831700,
backend does not require manual layout management - but it is provided
by the application
(gnome- settings- daemon: 9577): Gdk-WARNING **: The program settings- daemon' received an X Window System error. This
'gnome-
probably reflects a bug in the program. The error was 'BadMatch
(invalid parameter attributes)'. (Details: serial 1798 error_code 8
request_code 148 minor_code 22) (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
GDK_SYNCHRONIZE environment variable to change this behavior. You can
then get a meaningful backtrace from your debugger if you break on the
gdk_x_error() function.)