[Users] [Bug 3922] New: minimize to tray on startup not working
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Tue Nov 21 07:47:07 CET 2017
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3922
Bug ID: 3922
Summary: minimize to tray on startup not working
Classification: Unclassified
Product: Claws Mail
Version: 3.15.1
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Plugins/Notification
Assignee: users at lists.claws-mail.org
Reporter: daniel at ekpyron.org
Created attachment 1815
-->
http://www.thewildbeast.co.uk/claws-mail/bugzilla/attachment.cgi?id=1815&action=edit
Prevent notification_toggle_hide_show_window from being called on first run of
notification_trayicon_on_activate.
The minimize to tray on startup option of the notification plugin is not
working for me. Even if the option is enabled, the main window pops up whenever
claws-mail is run.
I tracked down the issue to the following: it seems that
notification_trayicon_on_activate in notification_trayicon.c is called on
startup, which then unconditionally calls
notification_toggle_hide_show_window(). Since the notification plugin prevented
the main window from being shown on startup, this toggle now shows the main
window.
I'm using a dirty workaround adjusts notification_trayicon_on_activate, so that
it does not call notification_toggle_hide_show_window() on its first run - I'm
attaching the corresponding patch. With this patch claws-mail behaves as
desired and indeed starts up as tray icon. However, this dirty workaround is of
course not a real solution, especially since it doesn't respect the
configuration options, but I hope it can indicate to you what's actually going
wrong.
My system is x86_64 Archlinux using a current LXQt Desktop. I've been
experiencing the issue for quite a while using different versions of LXQt and
LXDE on Archlinux. The issue is present when starting claws-mail from
command-line (or menu) as well as when running via autostart.
Thank you very much for looking into this!
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list