Thanks for reporting this. I looked into this bug, and the current
description says that goa-daemon and gvfs-goa-volume-monitor consume
about 32MB of RAM even when no GNOME Online Account is logged in. While
that's a fair observation, it doesn't yet describe a concrete problem —
just a resource usage note.
For this to be actionable as a bug report, I'd need you to clarify the
actual issue:
1. What specifically goes wrong? For example, does an application fail to
connect because these daemons run without accounts? Do they cause performance
problems, crashes, or incorrect behaviour?
2. What would you expect instead? (e.g., "these processes should not start at
all when no GOA account is configured")
If you can provide:
- A clear description of the symptom and expected behaviour
- Steps to reproduce (e.g., "on a fresh install with no GNOME Online Accounts
added, run `ps aux | grep goa-daemon` and observe X")
- Any relevant log output from `journalctl --user -u goa-daemon` or similar
that would help us evaluate whether this is a bug worth investigating.
If there's no functional problem and the concern is just memory usage,
that might be better tracked as a feature request rather than a defect.
Thanks for your patience!
** Changed in: gnome-online-accounts (Ubuntu)
Status: New => Incomplete
** Changed in: gvfs (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046580
Title:
goa-daemon and gvfs-goa-volume-monitor run without a goa login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2046580/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
