I have an almost 32 MB large .xsession-errors file: root@impala:/home/rose/Txt/src/Test/Octave(24)# ll ~rose/.xsession-errors -rw------- 1 rose rose 32602196 Apr 9 11:34 /home/rose/.xsession-errors mostly filled with the following messages: (acroread:23691): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (acroread:23691): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (evolution:6590): evolution-mail-CRITICAL **: e_mail_folder_uri_from_folder: assertion `CAMEL_IS_FOLDER (folder)' failed (evolution:6590): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave [1330776491,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application [1330776492,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] Page for group 0 is not ready [1330776492,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] Page for group 0 is not ready [1330776492,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] Page for group 0 is not ready [1330905493,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] Page for group 0 is not ready [1330905493,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] Page for group 0 is not ready [1330905493,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] Page for group 0 is not ready [1330908363,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] Page for group 1 is not ready [1330908363,000,gkbd-status.c:gkbd_status_set_current_page_for_group/] Page for group 1 is not ready [1330908379,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1330908379,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1330908379,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1 ![1330908379,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 0 is not equal to the current group from the event: 1
Not sure what you expect here. Many gui programs have lots of output that in most cases looks more fatal than it acutally is. Truncating this file if it gets too large is your job.
Hi Alex, normally the size of my .xsession-errors is smaller than 1MB, so I was confused about the size of 32 MB. About one hour ago I truncated the size to zero (>~rose/.xsession-errors) and now I have again more than 400 lines of: ![1333966653,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 I have not seen this line before and I can see such a line on other systems. So I have the feeling that something with xkb is out of order. OK, I will log out and log in again, maybe reboot the system, and see what happens.
And now, a little bit later I have more than 10000 lines with xklavier_evt_xkb.c:xkl_xkb_process_x_event in .xsession-errors: root@impala:/root(9)# grep "xklavier_evt_xkb.c:xkl_xkb_process_x_event" /home/rose/.xsession-errors | wc 10440 177487 1576714 I feel, that looks not good.
After rebooting ~/.xsession-errors stays small, as expected: root@impala:/root(4)# du -s ~rose/.xsession-errors 8 /home/rose/.xsession-errors Regards
