Long-Term Supported Versions

Functions changed info

---------------diffs in glib2_libglib-2.0.so.0.6200.5_abidiff.out:----------------

Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added function

Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

---------------diffs in glib2_libgio-2.0.so.0.6200.5_abidiff.out:----------------

Functions changes summary: 0 Removed, 1 Changed, 0 Added function

Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

1 function with some indirect sub-type change:

[C]'function gboolean g_file_monitor_source_handle_event(GFileMonitorSource*, GFileMonitorEvent, const gchar*, const gchar*, GFile*, gint64)' at glocalfilemonitor.c:343:1 has some indirect sub-type changes:

parameter 1 of type 'GFileMonitorSource*' has sub-type changes:

  in pointed to type 'typedef GFileMonitorSource' at glocalfilemonitor.h:41:1:

    underlying type 'struct _GFileMonitorSource' at glocalfilemonitor.c:45:1 changed:

      type size hasn't changed

      1 data member change:

       type of 'gpointer _GFileMonitorSource::instance' changed:

         typedef name changed from gpointer to GWeakRef at gobject.h:884:1

         underlying type 'void*' changed:

           entity changed from 'void*' to 'struct {union {gpointer p;} priv;}' at gobject.h:881:1

           type size hasn't changed

       and name of '_GFileMonitorSource::instance' changed to '_GFileMonitorSource::instance_ref' at glocalfilemonitor.c:49:1

---------------diffs in glib2_libgmodule-2.0.so.0.6200.5_abidiff.out:----------------

---------------diffs in glib2_libgthread-2.0.so.0.6200.5_abidiff.out:----------------

---------------diffs in glib2_libgobject-2.0.so.0.6200.5_abidiff.out:----------------

---------------diffs in glib2_libgiofam.so_abidiff.out:----------------

Bug Catching

Buggy Content

Bug Description

Submit As Issue

It's a little complicated....

I'd like to ask someone.

Just a small problem.

I can fix it online!

Bug Type

Specifications and Common Mistakes

● Misspellings or punctuation mistakes;

● Incorrect links, empty cells, or wrong formats;

● Chinese characters in English context;

● Minor inconsistencies between the UI and descriptions;

● Low writing fluency that does not affect understanding;

● Incorrect version numbers, including software package names and version numbers on the UI.

Usability

● Incorrect or missing key steps;

● Missing prerequisites or precautions;

● Ambiguous figures, tables, or texts;

● Unclear logic, such as missing classifications, items, and steps.

Correctness

● Technical principles, function descriptions, or specifications inconsistent with those of the software;

● Incorrect schematic or architecture diagrams;

● Incorrect commands or command parameters;

● Incorrect code;

● Commands inconsistent with the functions;

● Wrong screenshots.

Risk Warnings

● Lack of risk warnings for operations that may damage the system or important data.

Content Compliance

● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

● Copyright infringement.

We may contact you through email in regard to the bug fixing solution. You will also be notified through email if you win any prize during the activity.