Seeking help resolving repeating journalctrl errors

Help
1

I’m running the latest unstable version of NixOS (25.05.20250315 Warbler) with GNOME desktop. The system is generally stable, but I’m experiencing recurring errors that are flooding my journalctl logs. Specifically, these two errors:

Mar 18 14:48:41 pika .gnome-shell-wr[2716]: g_source_get_id: assertion 'source->context != NULL' failed
Mar 18 14:48:50 pika .gnome-shell-wr[2716]: (../libsoup/soup-message-queue-item.c:46):soup_message_queue_item_destroy: runtime check failed: (soup_message_get_connection (item->msg) == NULL)

I suspect a GNOME Shell extension might be causing this, but disabling extensions hasn’t resolved the issue. I’ve also struggled to identify which applications have libsoup as a dependency.

Any help or pointers to track down the source of these errors would be greatly appreciated. These errors are generating thousands of log entries daily.

Thank you in advance.

2

nix-tree (3rd party tool) might help you examine reverse deps here.

3

Thanks @waffle8946. nix-tree is a great tool for confirming dependencies when you know the initial package. What I’m looking to do, is start with the library and work back to all the applications that have it as a dependency.

For example using nix-tree I confirmed that libsoup-3.6.4 is indeed a dependency in gnome-shell-47.4, but what I want is a list of all packages that include libsoup-3.6.4 as a dependency. gnome-shell-47.4 would be one of the packages, but how do I find the others?

4

The tool lists all immediate parents.
Alternatively, you can use the tool to get the full store path(s) for the library, then run nix why-depends --all /run/current-system <path>.