-- Logs begin at Mon 2017-09-25 14:50:06 EDT, end at Mon 2017-09-25 17:12:11 EDT. --
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:49 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:55:50 hostname evolution-calen[4969]: e_cal_recur_generate_instances_sync: assertion 'icaltime_compare (interval_start, interval_end) < 0' failed
sept. 25 14:56:02 hostname gsd-print-notif[5066]: Source ID 2 was not found when attempting to remove it
sept. 25 14:56:02 hostname kerneloops-applet.desktop[5184]: kerneloops-applet: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.
sept. 25 14:56:02 hostname evolution-calen[4969]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx4925x2: La connexion est fermée
sept. 25 14:56:02 hostname tracker-extract[5181]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (**) Option "fd" "21"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) event8  - (II) Asus Wireless Radio Control: (II) device removed
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (**) Option "fd" "24"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) event5  - (II) Video Bus: (II) device removed
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (**) Option "fd" "25"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) event4  - (II) Video Bus: (II) device removed
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (**) Option "fd" "26"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) event1  - (II) Power Button: (II) device removed
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (**) Option "fd" "27"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) event2  - (II) Sleep Button: (II) device removed
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (**) Option "fd" "28"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) event6  - (II) Logitech Logitech Wireless Headset: (II) device removed
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (**) Option "fd" "29"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) event12 - (II) USB2.0 HD UVC WebCam: USB2.0 HD: (II) device removed
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (**) Option "fd" "30"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) event9  - (II) Asus WMI hotkeys: (II) device removed
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (**) Option "fd" "31"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) event3  - (II) AT Translated Set 2 keyboard: (II) device removed
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (**) Option "fd" "32"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) event7  - (II) ETPS/2 Elantech Touchpad: (II) device removed
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) UnloadModule: "libinput"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) systemd-logind: releasing fd for 13:71
sept. 25 14:56:02 hostname evolution-calen[4990]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx4925x3: La connexion est fermée
sept. 25 14:56:02 hostname systemd[3028]: telepathy-mission-control-5.service: Failed with result 'exit-code'.
sept. 25 14:56:02 hostname evolution-addre[5036]: Error releasing name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx5017x2: La connexion est fermée
sept. 25 14:56:02 hostname tracker-miner-f[5186]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
sept. 25 14:56:02 hostname tracker-miner-f[5186]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
sept. 25 14:56:02 hostname tracker-miner-f[5186]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
sept. 25 14:56:02 hostname tracker-miner-f[5186]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
sept. 25 14:56:02 hostname tracker-miner-f[5186]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
sept. 25 14:56:02 hostname indicator-appli[5191]: Could not grab DBus properties for :1.93: The connection is closed
sept. 25 14:56:02 hostname indicator-appli[5191]: Name Lost
sept. 25 14:56:02 hostname zeitgeist-datah[5521]: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
sept. 25 14:56:02 hostname zeitgeist-fts[5535]: Error releasing name org.gnome.zeitgeist.SimpleIndexer: The connection is closed
sept. 25 14:56:02 hostname zeitgeist-fts[5535]: zeitgeist-fts.vala:252: The connection is closed
sept. 25 14:56:02 hostname tracker-extract[5181]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
sept. 25 14:56:02 hostname tracker-extract[5181]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
sept. 25 14:56:02 hostname tracker-extract[5181]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
sept. 25 14:56:02 hostname tracker-extract[5181]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
sept. 25 14:56:02 hostname tracker-miner-f[5186]: Error while sending AddMatch() message: La connexion est fermée
sept. 25 14:56:02 hostname tracker-miner-f[5186]: Error while sending AddMatch() message: La connexion est fermée
sept. 25 14:56:02 hostname tracker-miner-f[5186]: Error while sending AddMatch() message: La connexion est fermée
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) UnloadModule: "libinput"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) systemd-logind: releasing fd for 13:67
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) UnloadModule: "libinput"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) systemd-logind: releasing fd for 13:73
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) UnloadModule: "libinput"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) systemd-logind: releasing fd for 13:76
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) UnloadModule: "libinput"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) systemd-logind: releasing fd for 13:70
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) UnloadModule: "libinput"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) systemd-logind: releasing fd for 13:66
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) UnloadModule: "libinput"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) systemd-logind: releasing fd for 13:65
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) UnloadModule: "libinput"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) systemd-logind: releasing fd for 13:68
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) UnloadModule: "libinput"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) systemd-logind: releasing fd for 13:69
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) UnloadModule: "libinput"
sept. 25 14:56:02 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) systemd-logind: releasing fd for 13:72
sept. 25 14:56:04 hostname /usr/lib/gdm3/gdm-x-session[4747]: (II) Server terminated successfully (0). Closing log file.
sept. 25 14:56:04 hostname unknown[5672]: g_slice_set_config: assertion 'sys_page_size == 0' failed
sept. 25 14:56:04 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): emitting SessionIsActive
sept. 25 14:56:04 hostname unknown[5674]: g_slice_set_config: assertion 'sys_page_size == 0' failed
sept. 25 14:56:04 hostname gnome-session-binary[2601]: DEBUG(+): emitting SessionIsActive
sept. 25 14:56:05 hostname synology-cloud-station-drive-autostart.desktop[5200]: QProcess: Destroyed while process ("/home/username/.CloudStation/CloudStation.app/bin/cloud-drive-connect") is still running.
sept. 25 14:56:05 hostname synology-cloud-station-drive-autostart.desktop[5200]: ICE default IO error handler doing an exit(), pid = 5453, errno = 32
sept. 25 14:56:05 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmSystemd: received logind signal: SessionRemoved
sept. 25 14:56:05 hostname gnome-session-binary[2601]: DEBUG(+): GsmSystemd: received logind signal: SessionRemoved
sept. 25 14:56:05 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmSystemd: ignoring SessionRemoved signal
sept. 25 14:56:05 hostname gnome-session-binary[2601]: DEBUG(+): GsmSystemd: ignoring SessionRemoved signal
sept. 25 14:56:14 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmSystemd: received logind signal: SessionNew
sept. 25 14:56:14 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmSystemd: ignoring SessionNew signal
sept. 25 14:56:14 hostname gnome-session-binary[2601]: DEBUG(+): GsmSystemd: received logind signal: SessionNew
sept. 25 14:56:14 hostname gnome-session-binary[2601]: DEBUG(+): GsmSystemd: ignoring SessionNew signal
sept. 25 14:56:14 hostname unknown[5711]: g_slice_set_config: assertion 'sys_page_size == 0' failed
sept. 25 14:56:14 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): emitting SessionIsActive
sept. 25 14:56:14 hostname gnome-session-binary[2601]: DEBUG(+): emitting SessionIsActive
sept. 25 14:56:15 hostname org.gnome.ScreenSaver[5663]: Unable to init server: Impossible de se connecter : Connexion refusée
sept. 25 14:56:15 hostname gnome-screensav[5737]: Impossible d'ouvrir l'affichage : 
sept. 25 14:56:15 hostname gnome-session-binary[5715]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erreur lors de l’appel de StartServiceByName pour org.gnome.ScreenSaver : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
sept. 25 14:56:15 hostname gnome-session-binary[5715]: WARNING: Could not parse desktop file evolution-alarm-notify.desktop or it references a not found TryExec binary
sept. 25 14:56:15 hostname gnome-session-binary[5715]: WARNING: Could not parse desktop file indicator-weather.desktop or it references a not found TryExec binary
sept. 25 14:56:15 hostname gnome-session-binary[5715]: WARNING: Could not parse desktop file gnome-settings-daemon.desktop or it references a not found TryExec binary
sept. 25 14:56:15 hostname gnome-session-binary[5715]: WARNING: Could not parse desktop file gnome-sound-applet.desktop or it references a not found TryExec binary
sept. 25 14:56:15 hostname gnome-session-binary[5715]: WARNING: Could not parse desktop file tracker-miner-user-guides.desktop or it references a not found TryExec binary
sept. 25 14:56:15 hostname org.gnome.Shell.desktop[5747]: glamor: EGL version 1.4 (DRI2):
sept. 25 14:56:15 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 14:56:15 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 14:56:16 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 14:56:16 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 14:56:16 hostname spice-vdagent[5914]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
sept. 25 14:56:16 hostname gnome-session-binary[5715]: WARNING: App 'spice-vdagent.desktop' exited with code 1
sept. 25 14:56:16 hostname gsd-wacom[5915]: gsd_device_mapper_get: assertion 'screen != NULL' failed
sept. 25 14:56:16 hostname gsd-wacom[5915]: gsd_device_manager_get: assertion 'screen != NULL' failed
sept. 25 14:56:16 hostname gsd-wacom[5915]: invalid (NULL) pointer instance
sept. 25 14:56:16 hostname gsd-wacom[5915]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
sept. 25 14:56:16 hostname gsd-wacom[5915]: invalid (NULL) pointer instance
sept. 25 14:56:16 hostname gsd-wacom[5915]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
sept. 25 14:56:16 hostname gsd-wacom[5915]: gsd_device_manager_list_devices: assertion 'GSD_IS_DEVICE_MANAGER (manager)' failed
sept. 25 14:56:16 hostname gsd-sharing[5904]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
sept. 25 14:56:16 hostname gsd-sharing[5904]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
sept. 25 14:56:17 hostname gsd-rfkill[5899]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'UPower' on the module 'power'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'SignalManager' on the module 'convenience'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'SoundDeviceChooserBase' on the module 'base'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'SETTINGS_SCHEMA' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'SHOW_INPUT_SLIDER' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property '_extends' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'PlayerMenu' on the module 'widget'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'MINOR_VERSION' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'gsettings' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'MEDIAPLAYER_INDICATOR_POSITION_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'IndicatorPosition' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'AggregateMenuIndicator' on the module 'panel'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'compileTemplate' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'MEDIAPLAYER_COVER_STATUS_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'MEDIAPLAYER_STATUS_TEXT_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'MEDIAPLAYER_STATUS_SIZE_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'MEDIAPLAYER_HIDE_AGGINDICATOR_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'PlayerManager' on the module 'manager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'MEDIAPLAYER_KEEP_ACTIVE_OPEN_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'DBusMenu' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'WORKAROUND_RELOAD_TYPE_REGISTER' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'StatusNotifierWatcher' on the module 'statusNotifierWatcher'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'StatusNotifierWatcher' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 14:56:17 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'HIDE_ON_SINGLE_DEVICE' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'SHOW_PROFILES' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'ICON_THEME' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'HIDE_MENU_ICONS' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'PORT_SETTINGS' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'SHOW_OUTPUT_DEVICES' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'ICON_THEME_COLORED' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'ICON_THEME_MONOCHROME' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:17 hostname gnome-shell[5747]: Some code accessed the property 'SHOW_INPUT_DEVICES' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:18 hostname indicator-appli[6128]: Unable to get watcher name 'org.kde.StatusNotifierWatcher'
sept. 25 14:56:18 hostname org.gnome.Shell.desktop[5747]: Window manager warning: "XF86RFKill" is not a valid accelerator
sept. 25 14:56:19 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 14:56:19 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).
sept. 25 14:56:19 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 14:56:19 hostname gnome-shell[5747]: JS ERROR: TypeError: tray is undefined
                                          moveToTop@/home/username/.local/share/gnome-shell/extensions/TopIcons@phocean.net/extension.js:115:1
sept. 25 14:56:19 hostname gnome-shell[5747]: Some code accessed the property 'State' on the module 'docking'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:19 hostname gnome-shell[5747]: Some code accessed the property 'Logger' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:19 hostname gnome-shell[5747]: Some code accessed the property 'AppIndicator' on the module 'appIndicator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:19 hostname gnome-shell[5747]: Some code accessed the property 'StatusNotifierItem' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:19 hostname gnome-shell[5747]: Some code accessed the property 'connectSmart' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:19 hostname gnome-shell[5747]: Some code accessed the property 'IndicatorStatusIcon' on the module 'indicatorStatusIcon'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:19 hostname gnome-shell[5747]: Some code accessed the property 'IconActor' on the module 'appIndicator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:19 hostname gnome-shell[5747]: Some code accessed the property 'IconCache' on the module 'iconCache'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:19 hostname gnome-shell[5747]: Some code accessed the property 'SNIStatus' on the module 'appIndicator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:19 hostname gnome-shell[5747]: Some code accessed the property 'Client' on the module 'dbusMenu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:19 hostname tracker-extract[6113]: Could not insert metadata for item "file:///home/username/Documents/investissement_locatif.ods": Unable to insert multiple values for subject `urn:uuid:0c788ddf-2f49-9938-e464-6c1a3b63b7ac' and single valued property `nie:contentCreated' (old_value: '<untransformable>', new value: '<untransformable>')
sept. 25 14:56:19 hostname tracker-extract[6113]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 14:56:19 hostname tracker-extract[6113]: Could not insert metadata for item "file:///home/username/Documents/huber-klein-classiques.pdf": Subject `urn:uuid:c6c54ad5-5bfd-7a3f-681b-63bf1328b503' is not in domain `nfo:Image' of property `nfo:orientation'
sept. 25 14:56:19 hostname tracker-extract[6113]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 14:56:19 hostname tracker-extract[6113]: Could not insert metadata for item "file:///home/username/Documents/Impots/recu_fiscal_2349818_6447507_restosducoeur.pdf": Subject `urn:uuid:da84ad9a-4d2a-ff0e-00ba-fe42b4c44c73' is not in domain `nfo:Image' of property `nfo:orientation'
sept. 25 14:56:19 hostname tracker-extract[6113]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 14:56:19 hostname tracker-extract[6113]: Could not insert metadata for item "file:///home/username/Pictures/Seychelles/104___07/MDG_4041.MP4": Unable to insert multiple values for subject `urn:uuid:ded7fa6a-bc6c-db20-3046-a60eaabbeaa1' and single valued property `nfo:hasHash' (old_value: '126593', new value: '130531')
sept. 25 14:56:19 hostname tracker-extract[6113]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 14:56:19 hostname tracker-extract[6113]: Could not insert metadata for item "file:///home/username/Pictures/Seychelles/104___07/MDG_4041.MP4": Unable to insert multiple values for subject `urn:uuid:ded7fa6a-bc6c-db20-3046-a60eaabbeaa1' and single valued property `nfo:hasHash' (old_value: '126593', new value: '130532')
sept. 25 14:56:19 hostname tracker-extract[6113]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 14:56:19 hostname tracker-extract[6113]: Could not insert metadata for item "file:///home/username/Pictures/20170907/S%C3%A9quence%2001.avi": Unable to insert multiple values for subject `urn:uuid:59788b72-bd0f-5887-9b24-9e577f630e98' and single valued property `nfo:hasHash' (old_value: '130360', new value: '130533')
sept. 25 14:56:19 hostname tracker-extract[6113]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 14:56:19 hostname tracker-extract[6113]: Could not insert metadata for item "file:///home/username/Pictures/20170907/S%C3%A9quence%2001.avi": Unable to insert multiple values for subject `urn:uuid:59788b72-bd0f-5887-9b24-9e577f630e98' and single valued property `nfo:hasHash' (old_value: '130360', new value: '130534')
sept. 25 14:56:19 hostname tracker-extract[6113]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 14:56:20 hostname gnome-shell[5747]: Some code accessed the property 'refreshPropertyOnProxy' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 14:56:20 hostname gnome-software[6122]: plugin appstream took 1,6 seconds to do setup
sept. 25 14:56:32 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 14:56:33 hostname tracker-miner-f[6118]:   (Sparql buffer) Error in task 0 (file:///home/username/Documents) of the array-update: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 14:56:33 hostname tracker-miner-f[6118]: Could not execute sparql: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 14:56:33 hostname tracker-miner-f[6118]:   (Sparql buffer) Error in task 1 (file:///home/username/Musique) of the array-update: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 14:56:33 hostname tracker-miner-f[6118]: Could not execute sparql: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 14:56:33 hostname tracker-miner-f[6118]:   (Sparql buffer) Error in task 2 (file:///home/username/Pictures) of the array-update: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 14:56:33 hostname tracker-miner-f[6118]: Could not execute sparql: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 14:56:38 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 14:56:38 hostname zeitgeist-datah[6469]: zeitgeist-datahub.vala:227: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
sept. 25 14:56:47 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 14:56:52 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 14:56:53 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 14:56:54 hostname gnome-terminal-[6494]: Allocating size to GtkBox 0x55b9cc8012c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 14:56:54 hostname gnome-terminal-[6494]: Allocating size to GtkBox 0x55b9cc8012c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 14:56:54 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 14:56:56 hostname gnome-terminal-[6494]: Allocating size to GtkBox 0x55b9cc2676d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 14:56:56 hostname gnome-terminal-[6494]: Allocating size to GtkBox 0x55b9cc2676d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 14:56:56 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 14:58:40 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 14:58:41 hostname gnome-terminal-[6494]: Allocating size to GtkBox 0x55b9cc801f20 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 14:58:41 hostname gnome-terminal-[6494]: Allocating size to GtkBox 0x55b9cc801f20 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 14:58:42 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 14:58:43 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 14:58:46 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 14:58:53 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 14:58:55 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 14:59:07 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 14:59:14 hostname gnome-terminal-[6494]: Allocating size to GtkBox 0x55b9cc801c60 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 14:59:14 hostname gnome-terminal-[6494]: Allocating size to GtkBox 0x55b9cc801c60 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ac1e10
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268a616e0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126849acb0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ced7d0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126848f380
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268c9b3b0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cde740
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ce3760
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268496080
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ce5220
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ce5370
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ce5460
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ce5540
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ce5680
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126843b370
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ceea40
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ceebe0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ceed50
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ceee60
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ceefa0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cef140
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cef2b0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cef450
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cef610
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cef760
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cdf490
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cdf630
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cdf7d0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cdd4e0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cdd650
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268497af0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x5612687b1d80
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cee870
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ce3490
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268ce35e0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268499ec0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cf0480
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cef8d0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cefb20
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cefcf0
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268cf0110
sept. 25 14:59:19 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268479be0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e51fc0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e68910
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269c17b00
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a4a6be0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x5612696c0a30
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a4a3d40
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a8683e0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf71b0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf7350
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a8680f0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268770820
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf94e0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf9770
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf7a70
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf7e50
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf80e0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf8430
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf8780
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf8ad0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf8e20
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bbae0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bbe30
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bc180
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bc4d0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bc820
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bcb70
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bcec0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bd210
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a4a6a00
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0be0a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0be3f0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0be740
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bea90
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bede0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bf130
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bf480
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bf7d0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bfb20
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bfe70
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0c01c0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268dca650
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268d34bb0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0c06c0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0c0810
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0c0a50
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991dd00
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991df90
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991e2a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991e5f0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991e880
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991eb10
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991eda0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991f030
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991f380
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991f6d0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991fa20
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991fd30
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269920000
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991e130
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf57c0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268770780
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126991f950
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0c0960
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bf090
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bea00
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bcdd0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bbd40
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf89e0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x5612687709c0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bc730
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269922290
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x5612699225c0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269922800
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae1b70
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae1de0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae2070
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae2300
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae2610
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae28a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae2b30
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae2dc0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae3050
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae33a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae3630
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae38c0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae3b50
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae3de0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae4070
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae4290
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae4510
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae4860
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae4af0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae4e00
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae5090
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae5320
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae55b0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae58d0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae5b60
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae5df0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae6080
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae63a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae66c0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae6990
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbbc70
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbbf40
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbc260
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbc580
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbc8a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbcbc0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbcee0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbd200
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbd490
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbd7a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbda30
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbdcc0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbdf90
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbe240
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbe450
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbd440
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae4470
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbcd60
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dbc110
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae62b0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae2210
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dc07f0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269dc0a60
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bd510
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x56126a0bd7a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269920b60
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269920f00
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e628e0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e62c30
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e62f80
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e632d0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e63620
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e63970
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e63cc0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269bf8d30
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e63530
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269920dd0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561269ae6540
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268d39d30
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268d3a060
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268d3a390
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268d3a6c0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268d3a9f0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268d3ad20
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e64960
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e64cb0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e64e50
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e65120
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e65440
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e655e0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e658b0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e65bd0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e65d70
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e65fb0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e66300
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e664a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e666e0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e66a30
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e66d80
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e670d0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e672f0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e67530
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e676d0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e67820
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e67aa0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e67e40
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e68640
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e64190
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e64530
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e34d80
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e35090
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e35360
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e35700
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e35a20
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e35d40
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e36060
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e36330
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e366d0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e369a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e36c70
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e36f00
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e37210
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e68160
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e683f0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e37890
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e37be0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e37f30
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e38280
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e385d0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e388a0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e37490
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e38b60
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e38cb0
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e38e00
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e39060
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e39200
sept. 25 14:59:22 hostname nautilus[7024]: Unexpected plugin response.  This probably indicates a bug in a Nautilus extension: handle=0x561268e393b0
sept. 25 14:59:55 hostname eog[7490]: Impossible d'ouvrir le fichier « /home/username/.cache/thumbnails/normal/5e61f31aaecb1673318da6da3ed149fb.png » : Aucun fichier ou dossier de ce type
sept. 25 15:00:51 hostname gnome-shell[5747]: clutter_actor_is_visible: assertion 'CLUTTER_IS_ACTOR (self)' failed
sept. 25 15:00:52 hostname org.gnome.Shell.desktop[5747]: polkit-agent-helper-1: pam_authenticate failed: Authentication failure
sept. 25 15:01:14 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmPresence: setting idle: 1
sept. 25 15:01:14 hostname gnome-session-binary[2601]: DEBUG(+): GsmPresence: setting idle: 1
sept. 25 15:01:14 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): Updating systemd idle status: 1
sept. 25 15:01:14 hostname gnome-session-binary[2601]: DEBUG(+): Updating systemd idle status: 1
sept. 25 15:01:22 hostname gnome-shell[5747]: clutter_actor_is_visible: assertion 'CLUTTER_IS_ACTOR (self)' failed
sept. 25 15:01:31 hostname gnome-keyring-daemon[5706]: asked to register item /org/freedesktop/secrets/collection/login/85, but it's already registered
sept. 25 15:01:31 hostname gnome-keyring-daemon[5706]: asked to register item /org/freedesktop/secrets/collection/login/85, but it's already registered
sept. 25 15:02:04 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:02:07 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:03:00 hostname org.gnome.Shell.desktop[5747]: Window manager warning: last_user_time (777978) is greater than comparison timestamp (777972).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
sept. 25 15:03:00 hostname org.gnome.Shell.desktop[5747]: Window manager warning: 0x2400001 (Report a b) appears to be one of the offending windows with a timestamp of 777978.  Working around...
sept. 25 15:03:00 hostname org.gnome.Shell.desktop[5747]: Window manager warning: last_user_time (778010) is greater than comparison timestamp (778005).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
sept. 25 15:03:00 hostname org.gnome.Shell.desktop[5747]: Window manager warning: 0x2400001 (Report a b) appears to be one of the offending windows with a timestamp of 778010.  Working around...
sept. 25 15:03:36 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:03:53 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:03:58 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:04:09 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:04:12 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:04:17 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:04:18 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:04:20 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:04:22 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:04:23 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:04:36 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:04:38 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:05:05 hostname systemd-tmpfiles[12996]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
sept. 25 15:05:14 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[5943]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 15:06:40 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:09:36 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:09:51 hostname zeitgeist-datah[6453]: zeitgeist-datahub.vala:210: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required
sept. 25 15:09:51 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:09:52 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:11:15 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:11:18 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:11:22 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:11:26 hostname nautilus[7024]: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed
sept. 25 15:11:26 hostname nautilus[7024]: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed
sept. 25 15:11:26 hostname nautilus[7024]: gdk_window_show_internal: assertion 'GDK_IS_WINDOW (window)' failed
sept. 25 15:11:26 hostname nautilus[7024]: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed
sept. 25 15:11:26 hostname nautilus[7024]: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed
sept. 25 15:11:28 hostname nautilus[7024]: gtk_widget_get_mapped: assertion 'GTK_IS_WIDGET (widget)' failed
sept. 25 15:11:28 hostname nautilus[7024]: gdk_window_is_visible: assertion 'GDK_IS_WINDOW (window)' failed
sept. 25 15:11:28 hostname nautilus[7024]: gtk_widget_set_opacity: assertion 'GTK_IS_WIDGET (widget)' failed
sept. 25 15:11:28 hostname nautilus[7024]: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed
sept. 25 15:11:37 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:11:39 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:11:43 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:11:49 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:12:26 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:13:38 hostname NetworkManager[1131]: <warn>  [1506366818.9879] sup-iface[0x556510319820,wlan0]: connection disconnected (reason 6)
sept. 25 15:14:13 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:16:16 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:16:34 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:17:09 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:17:21 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:18:17 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:20:37 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:22:48 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:25:15 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:27:52 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:32:14 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:33:10 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:33:56 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:34:21 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:35:18 hostname gnome-software[6122]: no app for changed ubuntu-appindicators@ubuntu.com
sept. 25 15:35:18 hostname gnome-software[6122]: no app for changed ubuntu-dock@ubuntu.com
sept. 25 15:35:18 hostname gnome-shell[5747]: Some code accessed the property 'PanelIndicator' on the module 'panel'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 15:35:18 hostname gnome-software[6122]: no app for changed mediaplayer@patapon.info
sept. 25 15:35:18 hostname gnome-software[6122]: no app for changed alternate-tab@gnome-shell-extensions.gcampax.github.com
sept. 25 15:35:18 hostname gnome-software[6122]: no app for changed nohotcorner@azuri.free.fr
sept. 25 15:35:18 hostname gnome-software[6122]: no app for changed sound-output-device-chooser@kgshank.net
sept. 25 15:35:18 hostname gnome-software[6122]: no app for changed bettervolume@tudmotu.com
sept. 25 15:35:18 hostname gnome-software[6122]: no app for changed TopIcons@phocean.net
sept. 25 15:35:18 hostname gnome-shell[5747]: Source ID 260 was not found when attempting to remove it
sept. 25 15:35:18 hostname gnome-shell[5747]: Source ID 740 was not found when attempting to remove it
sept. 25 15:35:18 hostname gnome-software[6122]: no app for changed system-monitor@paradoxxx.zero.gmail.com
sept. 25 15:35:19 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 15:35:19 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 15:35:19 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).
sept. 25 15:36:47 hostname gnome-software[6122]: no app for changed ubuntu-dock@ubuntu.com
sept. 25 15:36:47 hostname gnome-software[6122]: no app for changed ubuntu-appindicators@ubuntu.com
sept. 25 15:36:47 hostname gnome-software[6122]: no app for changed system-monitor@paradoxxx.zero.gmail.com
sept. 25 15:36:47 hostname gnome-software[6122]: no app for changed bettervolume@tudmotu.com
sept. 25 15:36:47 hostname gnome-software[6122]: no app for changed mediaplayer@patapon.info
sept. 25 15:36:47 hostname gnome-software[6122]: no app for changed nohotcorner@azuri.free.fr
sept. 25 15:36:48 hostname gnome-software[6122]: no app for changed sound-output-device-chooser@kgshank.net
sept. 25 15:36:48 hostname gnome-software[6122]: no app for changed alternate-tab@gnome-shell-extensions.gcampax.github.com
sept. 25 15:36:48 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 15:36:48 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).
sept. 25 15:36:48 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 15:37:15 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:39:01 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:39:02 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:39:27 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:39:28 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:39:30 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 15:39:33 hostname gnome-software[6122]: no app for changed alternate-tab@gnome-shell-extensions.gcampax.github.com
sept. 25 15:39:33 hostname gnome-software[6122]: no app for changed sound-output-device-chooser@kgshank.net
sept. 25 15:39:33 hostname gnome-software[6122]: no app for changed nohotcorner@azuri.free.fr
sept. 25 15:39:33 hostname gnome-software[6122]: no app for changed mediaplayer@patapon.info
sept. 25 15:39:33 hostname gnome-software[6122]: no app for changed bettervolume@tudmotu.com
sept. 25 15:39:33 hostname gnome-shell[5747]: Source ID 41345 was not found when attempting to remove it
sept. 25 15:39:33 hostname gnome-shell[5747]: Source ID 41358 was not found when attempting to remove it
sept. 25 15:39:33 hostname gnome-software[6122]: no app for changed system-monitor@paradoxxx.zero.gmail.com
sept. 25 15:39:33 hostname gnome-software[6122]: no app for changed ubuntu-appindicators@ubuntu.com
sept. 25 15:39:33 hostname gnome-software[6122]: no app for changed ubuntu-dock@ubuntu.com
sept. 25 15:39:34 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).
sept. 25 15:39:34 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 15:39:34 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 15:56:16 hostname evolution-sourc[5797]: secret_service_search_sync: must specify at least one attribute to match
sept. 25 16:00:59 hostname upowerd[2727]: energy 32,589000 bigger than full 32,552000
sept. 25 16:02:59 hostname upowerd[2727]: energy 32,774000 bigger than full 32,589000
sept. 25 16:04:59 hostname upowerd[2727]: energy 32,952000 bigger than full 32,774000
sept. 25 16:06:59 hostname upowerd[2727]: energy 33,107000 bigger than full 32,952000
sept. 25 16:08:59 hostname upowerd[2727]: energy 33,255000 bigger than full 33,107000
sept. 25 16:10:59 hostname upowerd[2727]: energy 33,396000 bigger than full 33,255000
sept. 25 16:12:59 hostname gnome-software[6122]: no app for changed ubuntu-dock@ubuntu.com
sept. 25 16:12:59 hostname gnome-software[6122]: no app for changed ubuntu-appindicators@ubuntu.com
sept. 25 16:12:59 hostname gnome-software[6122]: no app for changed system-monitor@paradoxxx.zero.gmail.com
sept. 25 16:12:59 hostname gnome-software[6122]: no app for changed bettervolume@tudmotu.com
sept. 25 16:12:59 hostname gnome-software[6122]: no app for changed mediaplayer@patapon.info
sept. 25 16:12:59 hostname gnome-software[6122]: no app for changed nohotcorner@azuri.free.fr
sept. 25 16:12:59 hostname gnome-software[6122]: no app for changed sound-output-device-chooser@kgshank.net
sept. 25 16:12:59 hostname gnome-software[6122]: no app for changed alternate-tab@gnome-shell-extensions.gcampax.github.com
sept. 25 16:12:59 hostname upowerd[2727]: energy 33,522000 bigger than full 33,396000
sept. 25 16:13:00 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 16:13:00 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 16:13:00 hostname org.gnome.Shell.desktop[5747]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).
sept. 25 16:13:02 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:13:13 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:13:15 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:13:16 hostname gnome-shell[5747]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:14:22 hostname sudo[566]: pam_unix(sudo:auth): conversation failed
sept. 25 16:14:22 hostname sudo[566]: pam_unix(sudo:auth): auth could not identify password for [username]
sept. 25 16:14:33 hostname gnome-keyring-daemon[5706]: asked to register item /org/freedesktop/secrets/collection/login/154, but it's already registered
sept. 25 16:14:34 hostname gnome-keyring-daemon[5706]: asked to register item /org/freedesktop/secrets/collection/login/155, but it's already registered
sept. 25 16:14:35 hostname gnome-boxes[1172]: Failed to measure available space: L'emplacement indiqué n'est pas pris en charge
sept. 25 16:14:35 hostname gnome-boxes[1172]: Failed to measure available space: L'emplacement indiqué n'est pas pris en charge
sept. 25 16:14:35 hostname gnome-boxes[1172]: Failed to measure available space: L'emplacement indiqué n'est pas pris en charge
sept. 25 16:14:35 hostname gnome-boxes[1172]: Failed to measure available space: L'emplacement indiqué n'est pas pris en charge
sept. 25 16:14:35 hostname gnome-boxes[1172]: Failed to measure available space: L'emplacement indiqué n'est pas pris en charge
sept. 25 16:14:35 hostname gnome-boxes[1172]: Failed to measure available space: L'emplacement indiqué n'est pas pris en charge
sept. 25 16:14:59 hostname upowerd[2727]: energy 33,640000 bigger than full 33,522000
sept. 25 16:15:11 hostname gnome-boxes[1172]: spice_gtk_session_request_auto_usbredir: assertion 's->auto_usbredir_reqs > 0' failed
sept. 25 16:15:11 hostname gnome-shell[5747]: clutter_actor_lower: Actor of type ClutterActor is not inside a container
sept. 25 16:15:11 hostname gnome-shell[5747]: _cogl_pipeline_override_uniform: assertion 'cogl_is_pipeline (pipeline)' failed
sept. 25 16:16:01 hostname systemd[3028]: gnome-terminal-server.service: Failed with result 'exit-code'.
sept. 25 16:16:01 hostname org.gnome.Shell.desktop[5747]: (EE)
sept. 25 16:16:01 hostname org.gnome.Shell.desktop[5747]: Fatal server error:
sept. 25 16:16:01 hostname org.gnome.Shell.desktop[5747]: (EE) failed to read Wayland events: Connection reset by peer
sept. 25 16:16:01 hostname org.gnome.Shell.desktop[5747]: (EE)
sept. 25 16:16:01 hostname gnome-session-binary[5715]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
sept. 25 16:16:01 hostname synology-cloud-station-drive-autostart.desktop[6144]: The X11 connection broke (error 1). Did the X11 server die?
sept. 25 16:16:01 hostname synology-cloud-station-drive-autostart.desktop[6144]: QThread: Destroyed while thread is still running
sept. 25 16:16:01 hostname gnome-session-binary[5715]: WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1
sept. 25 16:16:01 hostname gnome-session-binary[5715]: Unrecoverable failure in required component org.gnome.Shell.desktop
sept. 25 16:16:01 hostname gnome-session-binary[5715]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
sept. 25 16:16:01 hostname gnome-session-binary[5715]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
sept. 25 16:16:01 hostname org.gnome.SettingsDaemon.Power.desktop[5894]: xcb_connection_has_error() a retourné vrai
sept. 25 16:16:01 hostname kerneloops-applet.desktop[6115]: kerneloops-applet: Fatal IO error 11 (Ressource temporairement non disponible) on X server :0.
sept. 25 16:16:01 hostname org.a11y.atspi.Registry[5778]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
sept. 25 16:16:01 hostname org.a11y.atspi.Registry[5778]:       after 3069 requests (3069 known processed) with 0 events remaining.
sept. 25 16:16:01 hostname gsd-rfkill[5899]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
sept. 25 16:16:02 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmSystemd: received logind signal: SessionRemoved
sept. 25 16:16:02 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmSystemd: ignoring SessionRemoved signal
sept. 25 16:16:02 hostname gnome-session-binary[2601]: DEBUG(+): GsmSystemd: received logind signal: SessionRemoved
sept. 25 16:16:02 hostname gnome-session-binary[2601]: DEBUG(+): GsmSystemd: ignoring SessionRemoved signal
sept. 25 16:16:02 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): emitting SessionIsActive
sept. 25 16:16:02 hostname gnome-session-binary[2601]: DEBUG(+): emitting SessionIsActive
sept. 25 16:16:02 hostname unknown[2837]: g_slice_set_config: assertion 'sys_page_size == 0' failed
sept. 25 16:16:02 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmPresence: setting idle: 0
sept. 25 16:16:02 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): Updating systemd idle status: 0
sept. 25 16:16:02 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmPresence: setting non-idle status 0
sept. 25 16:16:02 hostname gnome-session-binary[2601]: DEBUG(+): GsmPresence: setting idle: 0
sept. 25 16:16:02 hostname gnome-session-binary[2601]: DEBUG(+): Updating systemd idle status: 0
sept. 25 16:16:02 hostname gnome-session-binary[2601]: DEBUG(+): GsmPresence: setting non-idle status 0
sept. 25 16:16:02 hostname www-browser[2984]: *** err
sept. 25 16:16:02 hostname www-browser[2984]: checking tty name failed
sept. 25 16:16:02 hostname www-browser[2984]: *** err
sept. 25 16:16:02 hostname www-browser[2984]: Oh, oh, it's an error! possibly I die!
sept. 25 16:16:10 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmSystemd: received logind signal: SessionNew
sept. 25 16:16:10 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmSystemd: ignoring SessionNew signal
sept. 25 16:16:10 hostname gnome-session-binary[2601]: DEBUG(+): GsmSystemd: received logind signal: SessionNew
sept. 25 16:16:10 hostname gnome-session-binary[2601]: DEBUG(+): GsmSystemd: ignoring SessionNew signal
sept. 25 16:16:10 hostname unknown[3001]: g_slice_set_config: assertion 'sys_page_size == 0' failed
sept. 25 16:16:10 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): emitting SessionIsActive
sept. 25 16:16:10 hostname gnome-session-binary[2601]: DEBUG(+): emitting SessionIsActive
sept. 25 16:16:10 hostname org.gnome.ScreenSaver[5663]: Unable to init server: Impossible de se connecter : Connexion refusée
sept. 25 16:16:10 hostname gnome-screensav[3030]: Impossible d'ouvrir l'affichage : 
sept. 25 16:16:10 hostname gnome-session-binary[3006]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erreur lors de l’appel de StartServiceByName pour org.gnome.ScreenSaver : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
sept. 25 16:16:10 hostname gnome-session-binary[3006]: WARNING: Could not parse desktop file evolution-alarm-notify.desktop or it references a not found TryExec binary
sept. 25 16:16:10 hostname gnome-session-binary[3006]: WARNING: Could not parse desktop file indicator-weather.desktop or it references a not found TryExec binary
sept. 25 16:16:10 hostname gnome-session-binary[3006]: WARNING: Could not parse desktop file gnome-settings-daemon.desktop or it references a not found TryExec binary
sept. 25 16:16:10 hostname gnome-session-binary[3006]: WARNING: Could not parse desktop file gnome-sound-applet.desktop or it references a not found TryExec binary
sept. 25 16:16:10 hostname gnome-session-binary[3006]: WARNING: Could not parse desktop file tracker-miner-user-guides.desktop or it references a not found TryExec binary
sept. 25 16:16:11 hostname org.gnome.Shell.desktop[3041]: glamor: EGL version 1.4 (DRI2):
sept. 25 16:16:11 hostname pulseaudio[3061]: [pulseaudio] pid.c: Stale PID file, overwriting.
sept. 25 16:16:11 hostname pulseaudio[3061]: [pulseaudio] sink.c: Default and alternate sample rates are the same.
sept. 25 16:16:11 hostname pulseaudio[3061]: [pulseaudio] source.c: Default and alternate sample rates are the same.
sept. 25 16:16:11 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 16:16:11 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 16:16:12 hostname org.gnome.Shell.desktop[3041]: current session already has an ibus-daemon.
sept. 25 16:16:12 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 16:16:12 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 16:16:12 hostname spice-vdagent[3117]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
sept. 25 16:16:12 hostname gnome-session-binary[3006]: WARNING: App 'spice-vdagent.desktop' exited with code 1
sept. 25 16:16:12 hostname gsd-wacom[3121]: gsd_device_mapper_get: assertion 'screen != NULL' failed
sept. 25 16:16:12 hostname gsd-wacom[3121]: gsd_device_manager_get: assertion 'screen != NULL' failed
sept. 25 16:16:12 hostname gsd-wacom[3121]: invalid (NULL) pointer instance
sept. 25 16:16:12 hostname gsd-wacom[3121]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
sept. 25 16:16:12 hostname gsd-wacom[3121]: invalid (NULL) pointer instance
sept. 25 16:16:12 hostname gsd-wacom[3121]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
sept. 25 16:16:12 hostname gsd-wacom[3121]: gsd_device_manager_list_devices: assertion 'GSD_IS_DEVICE_MANAGER (manager)' failed
sept. 25 16:16:12 hostname gsd-sharing[3112]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
sept. 25 16:16:12 hostname gsd-sharing[3112]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit gnome-remote-desktop.service not loaded.
sept. 25 16:16:13 hostname gsd-rfkill[3107]: g_object_notify: object class 'CcRfkillGlib' has no property named 'kernel-noinput'
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'UPower' on the module 'power'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'SignalManager' on the module 'convenience'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'SoundDeviceChooserBase' on the module 'base'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'SETTINGS_SCHEMA' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'SHOW_INPUT_SLIDER' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property '_extends' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'PlayerMenu' on the module 'widget'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'MINOR_VERSION' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'gsettings' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'MEDIAPLAYER_INDICATOR_POSITION_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'IndicatorPosition' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'AggregateMenuIndicator' on the module 'panel'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'compileTemplate' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'MEDIAPLAYER_COVER_STATUS_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'MEDIAPLAYER_STATUS_TEXT_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'MEDIAPLAYER_STATUS_SIZE_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'MEDIAPLAYER_HIDE_AGGINDICATOR_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'PlayerManager' on the module 'manager'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'MEDIAPLAYER_KEEP_ACTIVE_OPEN_KEY' on the module 'settings'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'DBusMenu' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'WORKAROUND_RELOAD_TYPE_REGISTER' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'StatusNotifierWatcher' on the module 'statusNotifierWatcher'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'StatusNotifierWatcher' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 16:16:13 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'HIDE_ON_SINGLE_DEVICE' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'SHOW_PROFILES' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'ICON_THEME' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'HIDE_MENU_ICONS' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'PORT_SETTINGS' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'SHOW_OUTPUT_DEVICES' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'ICON_THEME_COLORED' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'ICON_THEME_MONOCHROME' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:13 hostname gnome-shell[3041]: Some code accessed the property 'SHOW_INPUT_DEVICES' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:14 hostname org.gnome.Shell.desktop[3041]: Window manager warning: "XF86RFKill" is not a valid accelerator
sept. 25 16:16:14 hostname indicator-appli[3305]: Unable to get watcher name 'org.kde.StatusNotifierWatcher'
sept. 25 16:16:14 hostname hplip-systray.desktop[3306]: error: Unable to lock /home/username/.hplip/hp-systray.lock. Is hp-systray already running?
sept. 25 16:16:14 hostname /hp-systray[3306]: hp-systray[3306]: error: Unable to lock /home/username/.hplip/hp-systray.lock. Is hp-systray already running?
sept. 25 16:16:14 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).
sept. 25 16:16:14 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 16:16:14 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 16:16:14 hostname gnome-shell[3041]: JS ERROR: TypeError: tray is undefined
                                          moveToTop@/home/username/.local/share/gnome-shell/extensions/TopIcons@phocean.net/extension.js:115:1
sept. 25 16:16:14 hostname gnome-shell[3041]: Some code accessed the property 'State' on the module 'docking'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:15 hostname tracker-extract[3293]: Could not insert metadata for item "file:///home/username/Documents/investissement_locatif.ods": Unable to insert multiple values for subject `urn:uuid:0c788ddf-2f49-9938-e464-6c1a3b63b7ac' and single valued property `nie:contentCreated' (old_value: '<untransformable>', new value: '<untransformable>')
sept. 25 16:16:15 hostname tracker-extract[3293]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 16:16:15 hostname tracker-extract[3293]: Could not insert metadata for item "file:///home/username/Documents/huber-klein-classiques.pdf": Subject `urn:uuid:c6c54ad5-5bfd-7a3f-681b-63bf1328b503' is not in domain `nfo:Image' of property `nfo:orientation'
sept. 25 16:16:15 hostname tracker-extract[3293]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 16:16:15 hostname tracker-extract[3293]: Could not insert metadata for item "file:///home/username/Documents/Impots/recu_fiscal_2349818_6447507_restosducoeur.pdf": Subject `urn:uuid:da84ad9a-4d2a-ff0e-00ba-fe42b4c44c73' is not in domain `nfo:Image' of property `nfo:orientation'
sept. 25 16:16:15 hostname tracker-extract[3293]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 16:16:15 hostname tracker-extract[3293]: Could not insert metadata for item "file:///home/username/Pictures/Seychelles/104___07/MDG_4041.MP4": Unable to insert multiple values for subject `urn:uuid:ded7fa6a-bc6c-db20-3046-a60eaabbeaa1' and single valued property `nfo:hasHash' (old_value: '126593', new value: '130542')
sept. 25 16:16:15 hostname tracker-extract[3293]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 16:16:15 hostname tracker-extract[3293]: Could not insert metadata for item "file:///home/username/Pictures/Seychelles/104___07/MDG_4041.MP4": Unable to insert multiple values for subject `urn:uuid:ded7fa6a-bc6c-db20-3046-a60eaabbeaa1' and single valued property `nfo:hasHash' (old_value: '126593', new value: '130543')
sept. 25 16:16:15 hostname tracker-extract[3293]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 16:16:15 hostname tracker-extract[3293]: Could not insert metadata for item "file:///home/username/Pictures/20170907/S%C3%A9quence%2001.avi": Unable to insert multiple values for subject `urn:uuid:59788b72-bd0f-5887-9b24-9e577f630e98' and single valued property `nfo:hasHash' (old_value: '130360', new value: '130544')
sept. 25 16:16:15 hostname tracker-extract[3293]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 16:16:15 hostname tracker-extract[3293]: Could not insert metadata for item "file:///home/username/Pictures/20170907/S%C3%A9quence%2001.avi": Unable to insert multiple values for subject `urn:uuid:59788b72-bd0f-5887-9b24-9e577f630e98' and single valued property `nfo:hasHash' (old_value: '130360', new value: '130545')
sept. 25 16:16:15 hostname tracker-extract[3293]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
sept. 25 16:16:16 hostname gnome-software[3302]: plugin appstream took 1,5 seconds to do setup
sept. 25 16:16:21 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[3148]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 16:16:24 hostname gnome-shell[3041]: Some code accessed the property 'Logger' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:24 hostname gnome-shell[3041]: Some code accessed the property 'AppIndicator' on the module 'appIndicator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:24 hostname gnome-shell[3041]: Some code accessed the property 'StatusNotifierItem' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:24 hostname gnome-shell[3041]: Some code accessed the property 'connectSmart' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:24 hostname gnome-shell[3041]: Some code accessed the property 'IndicatorStatusIcon' on the module 'indicatorStatusIcon'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:24 hostname gnome-shell[3041]: Some code accessed the property 'IconActor' on the module 'appIndicator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:24 hostname gnome-shell[3041]: Some code accessed the property 'IconCache' on the module 'iconCache'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:26 hostname gnome-shell[3041]: Some code accessed the property 'SNIStatus' on the module 'appIndicator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:26 hostname gnome-shell[3041]: Some code accessed the property 'Client' on the module 'dbusMenu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:27 hostname gnome-shell[3041]: Some code accessed the property 'refreshPropertyOnProxy' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
sept. 25 16:16:28 hostname gnome-terminal-[3421]: Allocating size to GtkBox 0x55c79dae86d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 16:16:28 hostname gnome-terminal-[3421]: Allocating size to GtkBox 0x55c79dae86d0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 16:16:29 hostname tracker-miner-f[3298]:   (Sparql buffer) Error in task 0 (file:///home/username/Documents) of the array-update: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 16:16:29 hostname tracker-miner-f[3298]: Could not execute sparql: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 16:16:29 hostname tracker-miner-f[3298]:   (Sparql buffer) Error in task 1 (file:///home/username/Pictures) of the array-update: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 16:16:29 hostname tracker-miner-f[3298]: Could not execute sparql: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 16:16:29 hostname tracker-miner-f[3298]:   (Sparql buffer) Error in task 2 (file:///home/username/Musique) of the array-update: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 16:16:29 hostname tracker-miner-f[3298]: Could not execute sparql: UNIQUE constraint failed: nie:DataObject.nie:url
sept. 25 16:16:59 hostname upowerd[2727]: energy 33,751000 bigger than full 33,640000
sept. 25 16:17:09 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:17:13 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:18:22 hostname gnome-keyring-daemon[2997]: asked to register item /org/freedesktop/secrets/collection/login/85, but it's already registered
sept. 25 16:18:22 hostname gnome-keyring-daemon[2997]: asked to register item /org/freedesktop/secrets/collection/login/85, but it's already registered
sept. 25 16:18:51 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:18:53 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:18:59 hostname upowerd[2727]: energy 33,862000 bigger than full 33,751000
sept. 25 16:19:30 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:19:34 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:19:35 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:20:59 hostname upowerd[2727]: energy 33,958000 bigger than full 33,862000
sept. 25 16:21:10 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): GsmPresence: setting idle: 1
sept. 25 16:21:10 hostname gnome-session-binary[2601]: DEBUG(+): GsmPresence: setting idle: 1
sept. 25 16:21:10 hostname /usr/lib/gdm3/gdm-wayland-session[2573]: gnome-session-binary[2601]: DEBUG(+): Updating systemd idle status: 1
sept. 25 16:21:10 hostname gnome-session-binary[2601]: DEBUG(+): Updating systemd idle status: 1
sept. 25 16:22:59 hostname upowerd[2727]: energy 33,966000 bigger than full 33,958000
sept. 25 16:23:03 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:23:17 hostname org.gnome.Shell.desktop[3041]: Window manager warning: last_user_time (5595036) is greater than comparison timestamp (5595034).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
sept. 25 16:23:17 hostname org.gnome.Shell.desktop[3041]: Window manager warning: 0x2a00010 (Launchpad ) appears to be one of the offending windows with a timestamp of 5595036.  Working around...
sept. 25 16:23:18 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:23:20 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[3148]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 16:23:22 hostname gnome-terminal-[3421]: Allocating size to GtkBox 0x55c79e11e470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 16:23:22 hostname gnome-terminal-[3421]: Allocating size to GtkBox 0x55c79e11e470 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 16:24:26 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:24:27 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:24:28 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:24:48 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:24:55 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:24:56 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:29:28 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:29:30 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:30:15 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:30:24 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:30:34 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:30:38 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:30:40 hostname org.gnome.SettingsDaemon.MediaKeys.desktop[3148]: Warning: DESKTOP_STARTUP_ID not set and no fallback available.
sept. 25 16:30:42 hostname gnome-terminal-[3421]: Allocating size to GtkBox 0x55c79dae82b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 16:30:42 hostname gnome-terminal-[3421]: Allocating size to GtkBox 0x55c79dae82b0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?
sept. 25 16:30:45 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:30:50 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:31:37 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:32:13 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:32:18 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:32:50 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:34:01 hostname upowerd[2727]: energy 34,313000 bigger than full 33,966000
sept. 25 16:35:12 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:35:14 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:37:17 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:37:19 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:38:06 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:38:18 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:38:19 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:38:29 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:38:31 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:40:00 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:40:56 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:41:43 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:41:57 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:44:57 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:45:35 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:50:34 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:50:40 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:51:35 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:51:39 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:56:26 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:56:27 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:56:31 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:56:32 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:56:47 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:56:59 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:59:40 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 16:59:57 hostname gnome-terminal-[3421]: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed
sept. 25 17:00:43 hostname gnome-shell[3041]: clutter_actor_is_visible: assertion 'CLUTTER_IS_ACTOR (self)' failed
sept. 25 17:03:27 hostname gnome-shell[3041]: clutter_actor_is_visible: assertion 'CLUTTER_IS_ACTOR (self)' failed
sept. 25 17:05:51 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 17:05:51 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).
sept. 25 17:05:51 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 17:05:56 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 17:05:56 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 17:05:56 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).
sept. 25 17:06:03 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 17:06:03 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym 73 with keysym 73 (keycode 27).
sept. 25 17:06:03 hostname org.gnome.Shell.desktop[3041]: Window manager warning: Overwriting existing binding of keysym ff09 with keysym ff09 (keycode 17).
sept. 25 17:08:37 hostname pkexec[3846]: username: Error executing command as another user: Request dismissed [USER=root] [TTY=unknown] [CWD=/home/username] [COMMAND=/usr/lib/gnome-control-center/cc-remote-login-helper disable]
sept. 25 17:10:30 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed
sept. 25 17:10:31 hostname gnome-shell[3041]: g_source_remove: assertion 'tag > 0' failed