** Description changed: + [Impact] + Gedit crashes when it is closed while a file is being loaded or just after the file has been loaded. + + The bug is a regression in Disco: in Cosmic Gedit is built using + autotools while in Disco we use meson. During the port to meson upstream + forgot to port a build option (in particular 'enable-gvfs-metadata', + enabled by default). Without this option a broken - and untested - code + path is activated. + + To fix thisd bug we should reintroduce the 'enable-gvfs-metadata' + option. + + [Test case] + 1. Create a big text file + 2. Open gedit + 3. Close the window while the file is still being loaded + + Also check there are no more reports in e.u.c. + + [Regression Potential] + The change affects the way gedit stores the file metadata. Try for example + 1. open a file + 2. focus a random line + 3. close the file + 4. re-open the file + 5. make sure the random line that you focused in point 2. is focused + + [Original report] The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/011263859266370f9e85de3368ab51716dadbf28 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.
** Description changed: [Impact] Gedit crashes when it is closed while a file is being loaded or just after the file has been loaded. The bug is a regression in Disco: in Cosmic Gedit is built using autotools while in Disco we use meson. During the port to meson upstream forgot to port a build option (in particular 'enable-gvfs-metadata', enabled by default). Without this option a broken - and untested - code path is activated. - To fix thisd bug we should reintroduce the 'enable-gvfs-metadata' - option. + To fix this bug we should reintroduce the 'enable-gvfs-metadata' option. [Test case] 1. Create a big text file 2. Open gedit 3. Close the window while the file is still being loaded Also check there are no more reports in e.u.c. [Regression Potential] The change affects the way gedit stores the file metadata. Try for example 1. open a file 2. focus a random line 3. close the file 4. re-open the file 5. make sure the random line that you focused in point 2. is focused [Original report] The Ubuntu Error Tracker has been receiving reports about a problem regarding gedit. This problem was most recently seen with package version 3.32.0-1, the problem page at https://errors.ubuntu.com/problem/011263859266370f9e85de3368ab51716dadbf28 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1822753 Title: /usr/bin/gedit:11:gedit_metadata_manager_set:gedit_document_set_metadata:save_metadata:gedit_document_dispose:g_object_unref To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1822753/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
