Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Volume indicator disappears when mouse is used #137

Open
nickwinlund opened this issue Jul 19, 2019 · 4 comments
Open

Volume indicator disappears when mouse is used #137

nickwinlund opened this issue Jul 19, 2019 · 4 comments

Comments

@nickwinlund
Copy link

Expected behaviour

Volume indicator adjustment

Actual behaviour

Volume indicator disappears when mouse is used on it

MATE general version

marco 1.20.1

Package version

Linux Distribution

Linux Mint 19.1

===================================================================
GDB Log
warning: core file may not match specified executable file.
[New LWP 2091]
[New LWP 2103]
[New LWP 2099]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `mate-volume-control-applet'.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7f3dd7d89f00 (LWP 2091))]

@lukefromdc
Copy link
Member

While I have never had this problem, this is the correct place to open the issue. Please fill out the rest of the template though, as otherwise many here won't work on it. In particular you should also open a downstream bug report with LinuxMint (which I'm pretty sure builds their own MATE packages rather than using Ubuntu's or at least they used to). I suspect this may be another distro-specific bug, thus the need for a downstream issue to go with this

I've never once had this happen except when hacking on experimental code on the applet and even then not on mouseover. Also useful would be the backtrace generated by gdb, run
thread apply all bt full
to get it

@nickwinlund
Copy link
Author

nickwinlund commented Jul 19, 2019 via email

@lukefromdc
Copy link
Member

Not much more I can do myself as I cannot duplicate the issue. I am on Debian, now with mate 1.23 but never had this happen on 1.20 when I was using it some time back.

https://bugs.launchpad.net/linuxmint has not been configured, I don;t know where LinuxMint takes bug reports as a result, but Ubuntu takes theirs at https://bugs.launchpad.net/ubuntu and Mint's forums are at https://forums.linuxmint.com/

@clefebvre this is something you should take a look at as you work on Mint and this is rather serious, it blocks using the volume control

@ifohancroft
Copy link

I can confirm the issue on Manjaro with MATE version 1.26.0 with mate-media version 1.26.0-1
Sometimes (maybe once or twice a day or every other day) when you hover over mate-volume-control-status-icon) it will crash with the following output (I presuming the output is sent to stderr):

(mate-volume-control-status-icon:116748): Gtk-WARNING **: 19:30:43.174: Calling gtk_widget_realize() on a widget that isn't inside a toplevel window is not going to work very well. Widgets must be inside a toplevel container before realizing them.

(mate-volume-control-status-icon:116748): GLib-GObject-CRITICAL **: 19:30:43.176: g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(mate-volume-control-status-icon:116748): Gdk-CRITICAL **: 19:30:43.176: gdk_window_get_scale_factor: assertion 'GDK_IS_WINDOW (window)' failed
**
Gtk:ERROR:../gtk/gtk/gtkwidget.c:5875:gtk_widget_get_frame_clock: assertion failed: (window != NULL)
Bail out! Gtk:ERROR:../gtk/gtk/gtkwidget.c:5875:gtk_widget_get_frame_clock: assertion failed: (window != NULL)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants