Re: [Bug 1883174] Re: Some (or all) desktop icons are missing
Another lazy way around this is to do Alt-F2, then type in R. Might be easier than creating a folder then deleting it. On 7/2/2021 4:12 AM, martin turyagyenda wrote: > I have gotten a lazy way around this, it is not really a fix but it > works. Around Feb this year(2021) or march give or take I had the same > problem but when I read through the ubuntu community and then others > like me who never made a fresh install from 14 lts then to 18 then to > 20. I was highly sure that I had missed something .. being a windows > user originally my first instinct was to create a new folder just like > was recommended, I did that for a while and it worked . however the > system prompted me to upgrade a few times then it worked perfect, all > was showing. But after a while I got the same issues again from an > upgrade from the main server. Trust me, all I did was right click-create > new folder-name it then when it was created and all my desktop folders > came back. it is lazy but it works mostly when you have upgraded from > previous version > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some (or all) desktop icons are missing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844699] Re: The snap plugin is not claiming the desktop id correctly
** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #804 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/804 ** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/-/issues/804 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1844699 Title: The snap plugin is not claiming the desktop id correctly To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1844699/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934520] Re: Nautilus very slow to start after 20.04 upgrade
$ dpkg -l | grep nautilus ii gir1.2-nautilus-3.0:amd64 1:3.36.3-0ubuntu1 amd64libraries for nautilus components - gir bindings ii libnautilus-extension1a:amd64 1:3.36.3-0ubuntu1 amd64libraries for nautilus components - runtime version ii nautilus 1:3.36.3-0ubuntu1 amd64file manager and graphical shell for GNOME ii nautilus-data 1:3.36.3-0ubuntu1 all data files for nautilus ii nautilus-extension-gnome-terminal 3.36.2-1ubuntu1~20.04 amd64GNOME terminal emulator application - Nautilus extension ii nautilus-sendto 3.8.6-3ubuntu0.20.04.1 amd64easily send files via email from within Nautilus ii python3-nautilus1.2.3-1ubuntu1 amd64Python binding for Nautilus components (Python 3 version) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934520 Title: Nautilus very slow to start after 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934520] Re: Nautilus very slow to start after 20.04 upgrade
Output for journalctl -b 0 ** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+attachment/5508647/+files/journalctl -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934520 Title: Nautilus very slow to start after 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934520] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1934520/+attachment/5508646/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934520 Title: Nautilus very slow to start after 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934520] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1934520/+attachment/5508645/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934520 Title: Nautilus very slow to start after 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934520] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1934520/+attachment/5508644/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934520 Title: Nautilus very slow to start after 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934520] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1934520/+attachment/5508643/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934520 Title: Nautilus very slow to start after 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934520] [NEW] Nautilus very slow to start after 20.04 upgrade
Public bug reported: Nautilus takes up to 50 seconds to start, even in save or open dialogs. Attached is the output for time strace -y -f -t -T -o /tmp/nautilus.strace2 nautilus --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-08-11 (1421 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Tags: focal Uname: Linux 5.4.0-73-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-27 (431 days ago) UserGroups: root wireshark _MarkForUpload: True usr_lib_nautilus: dropbox 2020.03.04 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal freeze nautilus ** Attachment added: "strace output" https://bugs.launchpad.net/bugs/1934520/+attachment/5508642/+files/nautilus.strace2 ** Tags added: apport-collected focal ** Description changed: Nautilus takes up to 50 seconds to start, even in save or open dialogs. Attached is the output for time strace -y -f -t -T -o /tmp/nautilus.strace2 nautilus + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2017-08-11 (1421 days ago) + InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) + Package: nautilus 1:3.36.3-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 + Tags: focal + Uname: Linux 5.4.0-73-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-27 (431 days ago) + UserGroups: root wireshark + _MarkForUpload: True + usr_lib_nautilus: dropbox 2020.03.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1934520 Title: Nautilus very slow to start after 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1883174] Re: Some (or all) desktop icons are missing
I have gotten a lazy way around this, it is not really a fix but it works. Around Feb this year(2021) or march give or take I had the same problem but when I read through the ubuntu community and then others like me who never made a fresh install from 14 lts then to 18 then to 20. I was highly sure that I had missed something .. being a windows user originally my first instinct was to create a new folder just like was recommended, I did that for a while and it worked . however the system prompted me to upgrade a few times then it worked perfect, all was showing. But after a while I got the same issues again from an upgrade from the main server. Trust me, all I did was right click-create new folder-name it then when it was created and all my desktop folders came back. it is lazy but it works mostly when you have upgraded from previous version -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some (or all) desktop icons are missing To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1887652] Re: Wayland not available with proprietary Nvidia drivers even when nvidia-drm.modeset=1 is set
** Changed in: gdm3 (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: mutter (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1887652 Title: Wayland not available with proprietary Nvidia drivers even when nvidia-drm.modeset=1 is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887652/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934470] Re: gnome-initial-setup should detect screen scale change
I think in GTK you need to connect to "notify::scale-factor" on a GtkWidget or GtkWindow. https://developer.gnome.org/gtk3/stable/GtkWidget.html#GtkWidget--scale- factor ** No longer affects: mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1934470 Title: gnome-initial-setup should detect screen scale change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1934470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934470] [NEW] gnome-initial-setup should detect screen scale change
Public bug reported: gnome-initial-setup detects size-changed event on GdkScreen, but when screen scale is changed the resize event is not triggered, causing it not reevaluating the small screen detection. Replacing it with monitors-changed can resolve this issue. ** Affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: mutter (Ubuntu) Status: New => Invalid ** Also affects: gnome-initial-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1934470 Title: gnome-initial-setup should detect screen scale change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1934470/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934457] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R
** Summary changed: - /usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_object_unref:on_window_icon_changed:g_closure_invoke:signal_emit_unlocked_R + gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() ** Summary changed: - gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() + gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon ** Summary changed: - gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon + gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4436 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4436 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4436 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1934457 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1934457/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934458] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist()
Maybe related to bug 1934457 and https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4436 ** Summary changed: - /usr/bin/gnome-shell:11:g_type_check_instance_cast:on_window_icon_changed:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist + gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() ** Summary changed: - gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() + gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4436 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4436 ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1934458 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934458] [NEW] gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() fro
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/29945d56fd6502de24678bddb8f825c97977fcbb 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1934458 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1934458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934457] [NEW] gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/eca665045730307781118f49eecca44ef0b9ea17 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/. ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute impish kylin-21.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1934457 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1934457/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930359] Re: gdm fails to start in a VMware Horizon VDI environment with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: glib2.0 (Ubuntu Focal) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1930359 Title: gdm fails to start in a VMware Horizon VDI environment with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1930359/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930359] Re: gdm fails to start in a VMware Horizon VDI environment with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates
Hi Daniel,
Yes, I am sure this is the same issue that they are experiencing there,
and I now believe the issue lies in glib, and not mutter.
When we install mutter-common, it calls the libglib2.0-0 hook to
recompile the gsettings schemas.
The customer provided me with a tarball of their
/usr/share/glib-2.0/schemas directory, and I have spent the day looking
at it.
I deleted all the schemas from a test 20.04 VM, and extracted the
tarball of their schemas in place, and rebooted the VM.
>From there, the same exact problems occurred. Each program could not
load the compiled gschema file, and hit a breakpoint in the glib
library.
Jul 2 13:41:04 ubuntu tracker-miner-f[1235]: No GSettings schemas are
installed on the system
Jul 2 13:41:04 ubuntu tracker-extract[1234]: No GSettings schemas are
installed on the system
Jul 2 13:41:04 ubuntu kernel: [ 13.280095] show_signal: 7 callbacks
suppressed
Jul 2 13:41:04 ubuntu kernel: [ 13.280097] traps: tracker-miner-f[1235] trap
int3 ip:7fb6202ac295 sp:7fff0d5c7cd0 error:0 in
libglib-2.0.so.0.6400.6[7fb62027+84000]
Jul 2 13:41:04 ubuntu kernel: [ 13.281163] traps: tracker-extract[1234] trap
int3 ip:7f8718ac3295 sp:7ffe774d1c40 error:0 in
libglib-2.0.so.0.6400.6[7f8718a87000+84000]
Jul 2 13:41:00 ubuntu gnome-session[1175]: gnome-session-binary[1175]:
GLib-GIO-ERROR: No GSettings schemas are installed on the system
Jul 2 13:41:00 ubuntu gnome-session[1175]: aborting...
Jul 2 13:41:00 ubuntu gnome-session-binary[1175]: GLib-GIO-ERROR: No GSettings
schemas are installed on the system#012aborting...
Jul 2 13:41:00 ubuntu gdm3: GdmDisplay: Session never registered, failing
Jul 2 13:41:00 ubuntu gdm3: GdmLocalDisplayFactory: maximum number of X
display failures reached: check X server log for errors
Jul 2 13:41:00 ubuntu gdm3: Child process -1157 was already dead.
Now, looking closer, we see their gschema.compiled file exists. This
means that we aren't dealing with a missing file and it not being re-
created, but instead a corrupted gschema.compiled file.
I rebuilt the file with:
$ sudo glib-compile-schemas /usr/share/glib-2.0/schemas/
and rebooted, and the system came up normally. Very interesting.
>From there, I rebuilt the file several times, each time checking the
sha256 value. Each time it was exactly the same, so the compile process
appears to be deterministic.
I then did a binary diff of the corrupted gschema.compiled file, and a
freshly rebuilt one.
I found two bytes were different:
$ cmp -l ~/schemas/gschemas.compiled
/usr/share/glib-2.0/schemas/gschemas.compiled | gawk '{printf "%08X %02X
%02X\n", $1, strtonum(0$2), strtonum(0$3)}'
376F E3 25
3771 A4 65
$ xxd ~/schemas/gschemas.compiled > ~/corrupt.bin
$ xxd /usr/share/glib-2.0/schemas/gschemas.compiled > ~/working.bin
$ diff ~/corrupt.bin ~/working.bin
887,888c887,888
< 3760: 0515 7837 e300 x7..
< 3770: a455 6f72 672e 676e 6f6d .U..org.gnom
---
> 3760: 0515 7837 2500 x7%.
> 3770: 6555 6f72 672e 676e 6f6d eU..org.gnom
I need to determine exactly how these two bytes ended up different.
I think we are chasing two bugs here:
1) A bug which generates a corrupted gschema.compiled file.
2) A bug where we cannot parse a corrupted gschema.compiled file gracefully.
Since my VM was generating a lot of coredumps for each process, I took a
look. I downloaded the debug symbols of glib2.0 for 20.04 and opened a
crashdump in gdb.
(gdb) bt
#0 _g_log_abort (breakpoint=1) at ../../../glib/gmessages.c:554
#1 0x7f635e381579 in g_logv (log_domain=0x7f635e6006ff "GLib-GIO",
log_level=G_LOG_LEVEL_ERROR, format=,
args=args@entry=0x7ffe83d1e730) at ../../../glib/gmessages.c:1373
#2 0x7f635e381743 in g_log (log_domain=log_domain@entry=0x7f635e6006ff
"GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_ERROR,
format=format@entry=0x7f635e6217b8 "No GSettings schemas are installed on
the system") at ../../../glib/gmessages.c:1415
#3 0x7f635e5ad1fa in g_settings_set_property (object=,
prop_id=2, value=, pspec=) at
../../../gio/gsettings.c:591
#4 0x7f635e46b681 in object_set_property (nqueue=0x55a285fd8e20,
value=0x7ffe83d1e910, pspec=0x55a285fd4570, object=0x55a285fe3570) at
../../../gobject/gobject.c:1565
#5 g_object_new_internal (class=class@entry=0x55a285fee870,
params=params@entry=0x7ffe83d1e9b0, n_params=n_params@entry=1) at
../../../gobject/gobject.c:1971
#6 0x7f635e46d378 in g_object_new_valist (object_type=,
first_property_name=, var_args=var_args@entry=0x7ffe83d1eb00) at
../../../gobject/gobject.c:2262
#7 0x7f635e46d6cd in g_object_new (object_type=,
first_property_name=) at ../../../gobject/gobject.c:1780
#8 0x55a285196a5c in ?? ()
#9 0x55a28517cfe6 in ?? ()
#10 0x7f635e0180b3 in __libc_start_main (main=0x55a28517c8d0, argc=4,
argv=0x7ffe83d1edc8, init=, fini=,
rtld_fini=,
