Bug#886419: systray-mdstat: complains at startup, despite everything appears to be fine
On Mon, 16 Nov 2020 04:32:37 +0100 Axel Beckert wrote: [...] > Just uploaded 1.2.0-1 to Debian Unstable. I closed this bug report as > I strongly suspect that your issues are gone with using different > backend libraries for notifications now. > > Please try out and check if that's really the case. If not, please > reopen with details about how the issue manifests now with the new > release. I've just tried the new version: it fails to start. I reported the issue in a separate bug report... -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgp1A_HA4goeF.pgp Description: PGP signature
Bug#886419: systray-mdstat: complains at startup, despite everything appears to be fine
Hi Francesco, Francesco Poli wrote: > > > Please ping me, when the new version is in Debian testing (or, at > > > least, in unstable): I will give it a try. > > > > Will do. > > Thanks. Just uploaded 1.2.0-1 to Debian Unstable. I closed this bug report as I strongly suspect that your issues are gone with using different backend libraries for notifications now. Please try out and check if that's really the case. If not, please reopen with details about how the issue manifests now with the new release. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#886419: systray-mdstat: complains at startup, despite everything appears to be fine
On Thu, 17 Sep 2020 01:13:06 +0200 Axel Beckert wrote: [...] > Francesco Poli wrote: [...] > > Well, I would call it a dialog window, since I have to click on the OK > > button, in order to (cleanly) close it... > > Please see the attached screenshot (or, rather, "windowshot"). > > Ok, I guess that's heavily depending on the notifyd being used. I've > seen notification in many different styles. There are e.g. GNOME and > KDE on the fancy side and dunst on the very simplistic side. I this can be useful to know, I use Fluxbox... > > The content is what I'd expect in a notification. > > And yes, upon start it shows you the current state. Maybe I should add > an option or so to disable this. It could be nice, but it's not on the top of my priority list... [...] > > By looking at the code, it seems that the complaint is generated > > because some exception is caught: [...] > > Does this ring some bell? > > Not really. Load of the code is borrowed from code examples of the > libraries or from fdpowermon and tweaked until it did what I wanted. > So I don't have really an idea what exactly > "Glib::Object::Introspection->setup" does and which reasons may exist > for it to fail. I just know it's needed to make this run. Well, that seems to be the direction in which the investigation has to be pushed... [...] > > Please ping me, when the new version is in Debian testing (or, at > > least, in unstable): I will give it a try. > > Will do. Thanks. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpXEimfFX0Xq.pgp Description: PGP signature
Bug#886419: systray-mdstat: complains at startup, despite everything appears to be fine
Ciao Francesco,
Francesco Poli wrote:
> > A dialog window? It should be a notification, no real window.
>
> Well, I would call it a dialog window, since I have to click on the OK
> button, in order to (cleanly) close it...
> Please see the attached screenshot (or, rather, "windowshot").
Ok, I guess that's heavily depending on the notifyd being used. I've
seen notification in many different styles. There are e.g. GNOME and
KDE on the fancy side and dunst on the very simplistic side.
The content is what I'd expect in a notification.
And yes, upon start it shows you the current state. Maybe I should add
an option or so to disable this.
> > I don't know and can't remember that I ever saw that myself (and at
> > least currently can't reproduce it).
>
> I still see this complaint:
>
> $ systray-mdstat
> no notify because setup failed:
>
> By looking at the code, it seems that the complaint is generated
> because some exception is caught:
>
> 66 try {
> 67 Glib::Object::Introspection->setup(
> 68 basename => 'Notify',
> 69 version => '0.7',
> 70 package => "Systray::Mdstat::Notify",
> 71 );
> 72 Systray::Mdstat::Notify->init();
> 73 } catch {
> 74 say "no notify because setup failed: $@";
> 75 $use_notify = 0;
> 76 };
>
> Does this ring some bell?
Not really. Load of the code is borrowed from code examples of the
libraries or from fdpowermon and tweaked until it did what I wanted.
So I don't have really an idea what exactly
"Glib::Object::Introspection->setup" does and which reasons may exist
for it to fail. I just know it's needed to make this run.
> > > Moreover, I would love to see Gtk stop complaining.
> > > Is there anything that can be done to fix the issue reported by Gtk,
> > > if it is an issue at all?
> >
> > I must admit, I have no idea.
> [...]
>
> The Gtk complaint is gone, so never mind!
Ok. :-)
> I am overwhelmed, so I am afraid I won't have much time to build the
> package myself.
No problem.
> Please ping me, when the new version is in Debian testing (or, at
> least, in unstable): I will give it a try.
Will do.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#886419: systray-mdstat: complains at startup, despite everything appears to be fine
On Wed, 16 Sep 2020 00:52:30 +0200 Axel Beckert wrote:
> Control: tag -1 + unreproducible
>
> Hi Francesco,
>
> sorry for the very late reply.
Hello Axel, thanks for your reply all the same.
>
> Francesco Poli (wintermute) wrote:
> > As soon as I start it, it complains on stdout (and Gtk complains on
> > stderr):
> >
> > $ systray-mdstat
> > no notify because setup failed:
> > Gtk-Message: GtkDialog mapped without a transient parent. This is
> > discouraged.
> >
> > In the meanwhile, a dialog window appears, informing me that all my md
> > devices are OK.
>
> A dialog window? It should be a notification, no real window.
Well, I would call it a dialog window, since I have to click on the OK
button, in order to (cleanly) close it...
Please see the attached screenshot (or, rather, "windowshot").
>
> > But then, why the complaint on stdout?
>
> I don't know and can't remember that I ever saw that myself (and at
> least currently can't reproduce it).
I still see this complaint:
$ systray-mdstat
no notify because setup failed:
By looking at the code, it seems that the complaint is generated
because some exception is caught:
66 try {
67 Glib::Object::Introspection->setup(
68 basename => 'Notify',
69 version => '0.7',
70 package => "Systray::Mdstat::Notify",
71 );
72 Systray::Mdstat::Notify->init();
73 } catch {
74 say "no notify because setup failed: $@";
75 $use_notify = 0;
76 };
Does this ring some bell?
>
> > I haven't found any trace of needed setup in the documentation.
>
> There is none. Should work out of the box and does for me. :-/
Well, it does seem to work, but it complaints at each start...
>
> > Moreover, I would love to see Gtk stop complaining.
> > Is there anything that can be done to fix the issue reported by Gtk,
> > if it is an issue at all?
>
> I must admit, I have no idea.
[...]
The Gtk complaint is gone, so never mind!
[...]
> In case you're curious, you could build the soon-to-be 1.2.0-1 package
> from a git checkout of https://github.com/xtaran/systray-mdstat and if
> that fixes it, I'll close the bug report with the upload. Otherwise,
> I'd wait for your feedback after uploading 1.2.0-1 and then
> retroactively close this bug report if it's fixed.
I am overwhelmed, so I am afraid I won't have much time to build the
package myself.
Please ping me, when the new version is in Debian testing (or, at
least, in unstable): I will give it a try.
Thanks for any help you may provide.
--
http://www.inventati.org/frx/
There's not a second to spare! To the laboratory!
. Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpAblU4R7XOW.pgp
Description: PGP signature
Bug#886419: systray-mdstat: complains at startup, despite everything appears to be fine
Control: tag -1 + unreproducible Hi Francesco, sorry for the very late reply. Francesco Poli (wintermute) wrote: > As soon as I start it, it complains on stdout (and Gtk complains on > stderr): > > $ systray-mdstat > no notify because setup failed: > Gtk-Message: GtkDialog mapped without a transient parent. This is > discouraged. > > In the meanwhile, a dialog window appears, informing me that all my md > devices are OK. A dialog window? It should be a notification, no real window. > But then, why the complaint on stdout? I don't know and can't remember that I ever saw that myself (and at least currently can't reproduce it). > I haven't found any trace of needed setup in the documentation. There is none. Should work out of the box and does for me. :-/ > Moreover, I would love to see Gtk stop complaining. > Is there anything that can be done to fix the issue reported by Gtk, > if it is an issue at all? I must admit, I have no idea. I'm not really experienced in writing GUI applications and fought a lot especially with GTK. GTK being an always moving target is also one of the reasons why I didn't work on this project for quite a while. Took me ages to get this working with GTK3 instead of GTK2. And everything seemed to get just more complicated. Since for the upcoming 1.2.0 bascially the whole GUI backend stuff changed, I wouldn't be surprised if this issue will be gone with 1.2.0. But since I can't reproduce this, I can't test it. In case you're curious, you could build the soon-to-be 1.2.0-1 package from a git checkout of https://github.com/xtaran/systray-mdstat and if that fixes it, I'll close the bug report with the upload. Otherwise, I'd wait for your feedback after uploading 1.2.0-1 and then retroactively close this bug report if it's fixed. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#886419: systray-mdstat: complains at startup, despite everything appears to be fine
Package: systray-mdstat Version: 1.1.0-1 Severity: normal Hello, thanks for developing and packaging this little nice notifier! I am giving it a try, when I noticed something weird. As soon as I start it, it complains on stdout (and Gtk complains on stderr): $ systray-mdstat no notify because setup failed: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. In the meanwhile, a dialog window appears, informing me that all my md devices are OK. Since this is the same exact conclusion I can draw from /proc/mdstat, I assume that systray-mdstat is working correctly. But then, why the complaint on stdout? What does it mean, anyway? Which setup failed? What am I supposed to do, in order to fix the setup? I haven't found any trace of needed setup in the documentation. Am I missing or misunderstanding something? Moreover, I would love to see Gtk stop complaining. Is there anything that can be done to fix the issue reported by Gtk, if it is an issue at all? Please let me know and/or fix the bug. Bye and thanks for your time! -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (800, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systray-mdstat depends on: ii libfile-sharedir-perl 1.104-1 ii libgtk3-perl 0.032-1 ii libtry-tiny-perl 0.30-1 ii perl 5.26.1-3 systray-mdstat recommends no packages. Versions of packages systray-mdstat suggests: ii fbpanel 7.0-4 pn smart-notifier -- no debconf information
