[Touch-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
Launchpad has imported 19 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=776147.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2016-12-15T18:58:19+00:00 aaronfranke wrote:
Line 430 of gio/glocalfilemonitor.c doesn't handle case
G_FILE_MONITOR_EVENT_MOVED, crashing many programs.
The list of programs affected includes but is not limited to:
xfdesktop
https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1598360
pcmanfm https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1598488
and caja https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1598359
The affected code can be found at
https://github.com/GNOME/glib/blob/master/gio/glocalfilemonitor.c and
looks like this:
switch (event_type)
{
(other conditions are located here)
case G_FILE_MONITOR_EVENT_MOVED:
/* was never available in this API */
default:
g_assert_not_reached ();
}
This matches with the g_assertion_message() crash that these programs
are experiencing. So, I think we've found the culprit, and the solution
would be to do something to handle case G_FILE_MONITOR_EVENT_MOVED so
that these programs do not crash. Alternatively, if this API function
should never be used, then the maintainers of these programs should be
notified of this easily reproducible bug and be shown how to fix it.
Right now, many packages that come default on major distros such as
Ubuntu flavors are completely broken.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/comments/7
On 2017-11-10T01:22:55+00:00 Bugzilla-tecnocode wrote:
*** Bug 790148 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/comments/10
On 2017-11-10T01:35:07+00:00 Robert Ayrapetyan wrote:
Why not to move:
case G_FILE_MONITOR_EVENT_MOVED:
under:
case G_FILE_MONITOR_EVENT_RENAMED:
so they will handle same way (because they are *almost* same right?).
G_FILE_MONITOR_EVENT_RENAMED branch even operates with names like
"G_FILE_MONITOR_WATCH_MOVES" and "G_FILE_MONITOR_SEND_MOVED" internally.
Apparently "was never available in this API" is not true because of the
list of affected apps.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/comments/11
On 2017-11-10T15:12:26+00:00 Bugzilla-tecnocode wrote:
Created attachment 363349
kqueue: Fix invalid emission of G_FILE_MONITOR_EVENT_MOVED event
That event is deprecated, and the kqueue backend can’t provide enough
information to go alongside the event (i.e. the name of the new file).
Use G_FILE_MONITOR_EVENT_DELETED instead.
Quite disappointed in the kqueue documentation for this: I cannot find a
single piece of documentation or example about how NOTE_RENAME is
supposed to communicate the new name of the file.
If it turns out that this is possible, the code can be amended again in
future. At least now it doesn’t abort.
Signed-off-by: Philip Withnall
Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/comments/12
On 2017-11-10T15:29:14+00:00 Bugzilla-tecnocode wrote:
(In reply to Robert from comment #2)
> Why not to move:
> case G_FILE_MONITOR_EVENT_MOVED:
>
> under:
> case G_FILE_MONITOR_EVENT_RENAMED:
>
> so they will handle same way (because they are *almost* same right?).
> G_FILE_MONITOR_EVENT_RENAMED branch even operates with names like
> "G_FILE_MONITOR_WATCH_MOVES" and "G_FILE_MONITOR_SEND_MOVED" internally.
Because that would be fixing the symptom of the problem, rather than the
underlying cause. This problem hasn’t been fixed already because
nobody’s found time to investigate it yet.
> Apparently "was never available in this API" is not true because of the list
> of affected apps.
I just spent a bit of time looking into it, and it seems this is caused
by the kqueue backend sending through an invalid event. I’ve attached a
patch for that.
If you weren’t using FreeBSD (or another system which uses kqueue, like
OS X), please let me know. There’s a potential bug in the inotify
backend where a -1 return value from ih_mask_to_EventFlags() can be
passed through to g_file_monitor_source_handle_event(), but I’m not 100%
sure that’s possible due to other checks beforehand.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/comments/13
On 2017-11-10T15:49:29+00:00 Robert Ayrapetyan wrote:
Hm, I
[Touch-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
** Bug watch added: bugzilla.gnome.org/ #776147 https://bugzilla.gnome.org/show_bug.cgi?id=776147 ** Also affects: glib via https://bugzilla.gnome.org/show_bug.cgi?id=776147 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1494897 Title: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Fix Released Bug description: I was opening "War Thunder"- Steam game and when I changed settings in game and it restarted I saw also in desktop error-message. I do not remember did I have anything from "nautilus" open. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 11 22:00:01 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2015-09-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_file_monitor_source_handle_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1494897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
Fixed in 2.56 ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1494897 Title: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached Status in glib2.0 package in Ubuntu: Fix Released Bug description: I was opening "War Thunder"- Steam game and when I changed settings in game and it restarted I saw also in desktop error-message. I do not remember did I have anything from "nautilus" open. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 11 22:00:01 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2015-09-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_file_monitor_source_handle_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
Downstream bug: https://bugzilla.xfce.org/show_bug.cgi?id=12556 ** Bug watch added: Xfce Bugzilla #12556 https://bugzilla.xfce.org/show_bug.cgi?id=12556 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1494897 Title: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached Status in glib2.0 package in Ubuntu: Confirmed Bug description: I was opening "War Thunder"- Steam game and when I changed settings in game and it restarted I saw also in desktop error-message. I do not remember did I have anything from "nautilus" open. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 11 22:00:01 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2015-09-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_file_monitor_source_handle_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=776147 ** Bug watch added: GNOME Bug Tracker #776147 https://bugzilla.gnome.org/show_bug.cgi?id=776147 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1494897 Title: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached Status in glib2.0 package in Ubuntu: Confirmed Bug description: I was opening "War Thunder"- Steam game and when I changed settings in game and it restarted I saw also in desktop error-message. I do not remember did I have anything from "nautilus" open. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 11 22:00:01 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2015-09-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_file_monitor_source_handle_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
** Summary changed: - nautilus crashed with SIGABRT in g_assertion_message() + various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1494897 Title: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached Status in glib2.0 package in Ubuntu: Confirmed Bug description: I was opening "War Thunder"- Steam game and when I changed settings in game and it restarted I saw also in desktop error-message. I do not remember did I have anything from "nautilus" open. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 11 22:00:01 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2015-09-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_file_monitor_source_handle_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
