Diodon sometimes does not show up in system tray
Sometimes diodon does not appear in the system tray, but the process keeps running. When that happens killing diodon and restarting it makes it appear on the system tray. I am using Ubuntu 20.04 with MATE Desktop.
Question information
- Language:
- English Edit question
- Status:
- Expired
- For:
- Diodon Edit question
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
I haven't seen this before. It sounds like Diodon is not responding.
Could you therefore start Diodon the following way and once the indicator disappears attach the log file to this question.
G_MESSAGES_
Revision history for this message
|
#2 |
Here is the log I got after the indicator disappeared:
(diodon:1616): GLib-GIO-DEBUG: 14:52:55.672: _g_io_module_
(diodon:1616): dconf-DEBUG: 14:52:55.672: watch_fast: "/org/appmenu/
(diodon:1616): dconf-DEBUG: 14:52:55.672: unwatch_fast: "/org/appmenu/
(diodon:1616): dconf-DEBUG: 14:52:55.673: watch_established: "/org/appmenu/
(diodon:1616): GLib-GIO-DEBUG: 14:52:55.680: _g_io_module_
(diodon:1616): dconf-DEBUG: 14:52:55.740: watch_fast: "/org/appmenu/
(diodon:1616): dconf-DEBUG: 14:52:55.740: unwatch_fast: "/org/appmenu/
(diodon:1616): dconf-DEBUG: 14:52:55.741: watch_established: "/org/appmenu/
(diodon:1616): GLib-DEBUG: 14:52:55.744: unsetenv() is not thread-safe and should not be used after threads are created
(diodon:1616): Gtk-DEBUG: 14:52:55.744: Connecting to session manager
** (diodon:1616): DEBUG: 14:52:55.744: main.vala:86: Activate DiodonApplication (Version 1.9.0-daily)
(diodon:1616): dconf-DEBUG: 14:52:55.744: watch_fast: "/net/launchpad
(diodon:1616): dconf-DEBUG: 14:52:55.744: watch_fast: "/net/launchpad
(diodon:1616): dconf-DEBUG: 14:52:55.745: watch_established: "/net/launchpad
(diodon:1616): dconf-DEBUG: 14:52:55.745: watch_established: "/net/launchpad
** (diodon:1616): DEBUG: 14:53:21.049: Name com.canonical.
(diodon:1616): dconf-DEBUG: 14:53:21.049: watch_fast: "/org/appmenu/
(diodon:1616): dconf-DEBUG: 14:53:21.049: unwatch_fast: "/org/appmenu/
(diodon:1616): dconf-DEBUG: 14:53:21.049: watch_established: "/org/appmenu/
** (diodon:1616): DEBUG: 14:53:46.055: controller.
** (diodon:1616): DEBUG: 14:53:46.056: zeitgeist-
** (diodon:1616): DEBUG: 18:21:57.831: utility.vala:154: Active window 0x3800003
** (diodon:1616): DEBUG: 18:21:57.868: utility.vala:180: Copied by process with pid 1618
** (diodon:1616): DEBUG: 18:21:58.070: utility.vala:97: Path is /usr/lib/
** (diodon:1616): DEBUG: 18:56:52.624: utility.vala:154: Active window 0x3800003
** (diodon:1616): DEBUG: 18:56:52.652: utility.vala:180: Copied by process with pid 1618
** (diodon:1616): DEBUG: 18:56:52.653: utility.vala:97: Path is /usr/lib/
** (diodon:1616): DEBUG: 19:21:57.299: utility.vala:154: Active window 0x3800220
** (diodon:1616): DEBUG: 19:21:57.299: utility.vala:180: Copied by process with pid 1618
** (diodon:1616): DEBUG: 19:21:57.299: utility.vala:97: Path is /usr/lib/
Revision history for this message
|
#3 |
It seems your are running an outdated version 1.9.0-daily.
Just a rough guess could it be that the ppa got deactivated when you upgraded to 20.04?
If so you can do the following (replace stable with daily if you want the daily branch) to activate again:
sudo add-apt-repository ppa:diodon-
sudo apt-get update
sudo apt install diodon
Does this work?
Revision history for this message
|
#4 |
I updated Diodon but the issue persists. Here are the logs:
(diodon:1547): GLib-GIO-DEBUG: 14:31:27.469: _g_io_module_
(diodon:1547): dconf-DEBUG: 14:31:27.469: watch_fast: "/org/appmenu/
(diodon:1547): dconf-DEBUG: 14:31:27.469: unwatch_fast: "/org/appmenu/
(diodon:1547): dconf-DEBUG: 14:31:27.469: watch_established: "/org/appmenu/
(diodon:1547): GLib-GIO-DEBUG: 14:31:27.472: _g_io_module_
(diodon:1547): dconf-DEBUG: 14:31:27.509: watch_fast: "/org/appmenu/
(diodon:1547): dconf-DEBUG: 14:31:27.509: unwatch_fast: "/org/appmenu/
(diodon:1547): dconf-DEBUG: 14:31:27.510: watch_established: "/org/appmenu/
(diodon:1547): GLib-DEBUG: 14:31:27.513: unsetenv() is not thread-safe and should not be used after threads are created
(diodon:1547): Gtk-DEBUG: 14:31:27.513: Connecting to session manager
** (diodon:1547): DEBUG: 14:31:27.514: main.vala:86: Activate DiodonApplication (Version 1.11.0)
(diodon:1547): dconf-DEBUG: 14:31:27.514: watch_fast: "/net/launchpad
(diodon:1547): dconf-DEBUG: 14:31:27.514: watch_fast: "/net/launchpad
(diodon:1547): dconf-DEBUG: 14:31:27.514: watch_established: "/net/launchpad
(diodon:1547): dconf-DEBUG: 14:31:27.514: watch_established: "/net/launchpad
** (diodon:1547): DEBUG: 14:31:54.275: Name com.canonical.
(diodon:1547): dconf-DEBUG: 14:31:54.275: watch_fast: "/org/appmenu/
(diodon:1547): dconf-DEBUG: 14:31:54.275: unwatch_fast: "/org/appmenu/
** (diodon:1547): DEBUG: 14:31:54.276: main.vala:86: Activate DiodonApplication (Version 1.11.0)
(diodon:1547): dconf-DEBUG: 14:31:54.276: watch_fast: "/net/launchpad
(diodon:1547): dconf-DEBUG: 14:31:54.276: watch_fast: "/net/launchpad
(diodon:1547): dconf-DEBUG: 14:31:54.277: watch_established: "/org/appmenu/
** (diodon:1547): DEBUG: 14:32:48.885: controller.
** (diodon:1547): DEBUG: 14:32:48.885: zeitgeist-
** (diodon:1547): DEBUG: 18:17:16.716: utility.vala:154: Active window 0x3800003
** (diodon:1547): DEBUG: 18:17:16.756: utility.vala:180: Copied by process with pid 1564
** (diodon:1547): DEBUG: 18:17:17.010: utility.vala:97: Path is /usr/lib/
** (diodon:1547): DEBUG: 18:38:55.316: utility.vala:154: Active window 0x3800193
** (diodon:1547): DEBUG: 18:38:55.444: utility.vala:180: Copied by process with pid 1564
** (diodon:1547): DEBUG: 18:38:55.445: utility.vala:97: Path is /usr/lib/
** (diodon:1547): DEBUG: 18:38:55.831: controller.
** (diodon:1547): DEBUG: 18:38:55.905: zeitgeist-
** (diodon:1547): DEBUG: 18:38:56.143: zeitgeist-
** (diodon:1547): DEBUG: 18:38:57.939: utility.vala:154: Active window 0x3800193
** (diodon:1547): DEBUG: 18:38:57.939: utility.vala:180: Copied by process with pid 1564
** (diodon:1547): DEBUG: 18:38:57.939: utility.vala:97: Path is /usr/lib/
** (diodon:1547): DEBUG: 18:38:57.939: controller.
** (diodon:1547): DEBUG: 18:38:57.939: zeitgeist-
** (diodon:1547): DEBUG: 18:38:57.939: zeitgeist-
** (diodon:1547): DEBUG: 18:39:31.370: utility.vala:154: Active window 0x3800193
** (diodon:1547): DEBUG: 18:39:31.370: utility.vala:180: Copied by process with pid 1564
** (diodon:1547): DEBUG: 18:39:31.370: utility.vala:97: Path is /usr/lib/
** (diodon:1547): DEBUG: 18:39:31.370: controller.
** (diodon:1547): DEBUG: 18:39:31.370: zeitgeist-
** (diodon:1547): DEBUG: 18:39:31.371: zeitgeist-
** (diodon:1547): DEBUG: 18:40:02.113: utility.vala:154: Active window 0x3800193
** (diodon:1547): DEBUG: 18:40:02.113: utility.vala:180: Copied by process with pid 1564
** (diodon:1547): DEBUG: 18:40:02.113: utility.vala:97: Path is /usr/lib/
** (diodon:1547): DEBUG: 18:40:02.113: controller.
** (diodon:1547): DEBUG: 18:40:02.114: zeitgeist-
** (diodon:1547): DEBUG: 18:40:02.114: zeitgeist-
Revision history for this message
|
#5 |
Do you have another application which uses the application indicator menu? And does this app have the same issue?
When looking at the log file all looks good to me and it could be that the application indicator crashes. And when you start Diodon again it calls the indicator through the Dbus service which makes it start again.
In this case the problem would not be with Diodon but with the application indicator service.
Revision history for this message
|
#6 |
I use Liferea, Deluge, Megasync, and have the Wifi and volume indicators. Diodon is the only indicator that disappears.
Revision history for this message
|
#7 |
I have finally gotten around to install Ubuntu MATE 20.04 on a virtual machine to try to reproduce your issue. I wasn't able too though. Diodon always remains in the notification area whatever I do.
Can you reproduce the issue so you know what action you take when Diodon disappears (maybe you are copying from a specific app or something)?
Also is the above log the complete log till Diodon actually disappears?
Revision history for this message
|
#8 |
The log is the complete log since Diodon starts until it disappears. I'll see if I can reproduce the issue but it doesn't happen frequently. Usually I notice Diodon is gone when I look at the tray and see it's missing.
Revision history for this message
|
#9 |
This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.