| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
indicator mode
Remove the separator after the active connection, and put a new separator
between devices. Also ensure that connection items show themselves, otherwise
they don't get picked up by dbusmenu-gtk.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
GtkImageMenuItems are deprecated and we shouldn't use them anymore.
So don't; appindicator/dbusmenu can handle GtkImages in normal
GtkMenuItems now with the 16.04.0 release.
appindicator/dbusmenu also strips Pango markup so we can remove
the conditionals around label text.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GtkImageMenuItem is deprecated and we should use fewer of them. Most
GTK-based desktop environments seem to have stopped showing icons in
menus by default anyway. This will allow us to simplify the code
for both the regular applet and the appindictor version. So:
1) remove the stock icons from the static menu items so they won't
be displayed
2) override gtk-menu-images to TRUE for later appindicator changes,
since we actually want our custom menu item images displayed, just
not the stock ones (that we just removed anyway)
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
When compiling with --with-appindicator, I got a lot of criticals due
to missing icons. First, ensure we call nm_icons_reload() as needed.
Then, better cope with errors loading icons.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
nma_icon_check_and_load() uses the fallback_icon when it fails
to load the icon.
Probably a fallback_icon should be always present. But nma_icons_reload()
goes through some lengths to cope with an error creating the
fallback_icon. So, either we assert that the fallback_icon is always
present, or users of nma_icon_check_and_load() must cope with a NULL
icon. Do the latter.
|
| |
| |
| |
| | |
This way, we only log a warning about a missing icon once.
|
| | |
|
| | |
|
|/
|
|
| |
To get nm_g_object_unref().
|
|
|
|
| |
Who uses IPv4 anyway?
|
|
|
|
|
|
|
|
|
|
|
| |
attempting to remove it
Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff316081b in _g_log_abort (breakpoint=1) at gmessages.c:324
324 G_BREAKPOINT ();
Missing separate debuginfos, use: dnf debuginfo-install dbus-glib-0.106-1.fc23.x86_64 GConf2-3.2.6-15.fc23.x86_64 libgcc-5.3.1-2.fc23.x86_64
(gdb) bt
(gdb)
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Caught the following valgrind error on
network-manager-applet-1.2.0-0.3.beta1.fc24:
== Invalid read of size 8
== at 0x822471D: g_type_check_instance (gtype.c:4137)
== by 0x8218B63: g_signal_handlers_disconnect_matched (gsignal.c:2925)
== by 0x129B3D: update_active_ap (applet-device-wifi.c:1195)
== by 0x129C92: wifi_device_state_changed (applet-device-wifi.c:1219)
== by 0x11C96E: foo_device_state_changed_cb (applet.c:2308)
== by 0xF2FCC57: ffi_call_unix64 (in /usr/lib64/libffi.so.6.0.2)
== by 0xF2FC6B9: ffi_call (in /usr/lib64/libffi.so.6.0.2)
== by 0x81FF279: g_cclosure_marshal_generic_va (gclosure.c:1604)
== by 0x81FE7A6: _g_closure_invoke_va (gclosure.c:867)
== by 0x821A1D7: g_signal_emit_valist (gsignal.c:3294)
== by 0x821A82E: g_signal_emit (gsignal.c:3441)
== by 0x7ED59DC: g_simple_async_result_complete (gsimpleasyncresult.c:801)
This happens, because we hookup the access-point at the device, without
taking any strong references or otherwise ensuring proper lifetime
handling.
Fix that, by registering a weak-ref to the access-point, so that we
notice when the access-point gets destroyed. Note that we don't want
to take strong references, because neither device, access-point nor
applet should keep each other alive only because of an active
access-point.
Also, instead of registering the access-point at the device, register
it at the applet. In principle there could be multiple applet instances
and it is wrong that they all try to register the access-point on the
same device.
https://mail.gnome.org/archives/networkmanager-list/2016-March/msg00039.html
|
|
|
|
|
|
| |
CID 59915 (#1 of 1): Logically dead code (DEADCODE)
dead_error_line: Execution cannot reach this statement:
g_set_error_literal(error, ....
|
|
|
|
|
|
|
|
| |
The world is a better place now.
CID 59916 (#1 of 2): Logically dead code (DEADCODE)
dead_error_line: Execution cannot reach the expression "" inside this
statement: if (!strcmp((band ? band : ....
|
|
|
|
|
|
| |
CID 59917 (#1 of 1): Missing break in switch (MISSING_BREAK)
unterminated_case: The case for value 1 is not terminated by a 'break'
statement.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Coverity thinks we're no good at string manipulation.
Can't argue with that.
(Not a security issue; the user could overflow the buffer by typing a
too long WEP key, but no privilege boundary is crossed.)
CID 59920 (#1 of 1): Copy into fixed size buffer (STRING_OVERFLOW)
2. fixed_size_dest: You might overrun the 65 byte fixed-size string
sec->keys[sec->cur_index] by copying key without checking the length.
CID 59919 (#1 of 1): Copy into fixed size buffer (STRING_OVERFLOW)
1. fixed_size_dest: You might overrun the 65 byte fixed-size string
sec->keys[sec->cur_index] by copying key without checking the length.
CID 59918 (#1 of 1): Copy into fixed size buffer (STRING_OVERFLOW)
4. fixed_size_dest: You might overrun the 65 byte fixed-size string
sec->keys[i] by copying tmp without checking the length.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
rh#1313866 and rh#1314650 show a crash due to "g_assert (s_con)".
It's unclear how this can happen, but for now downgrade the crash
to a warning.
https://bugzilla.redhat.com/show_bug.cgi?id=1313866
https://bugzilla.redhat.com/show_bug.cgi?id=1314650
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When buiding with "CFLAGS=-O0 -Werror", introspection.m4 passes
those flags to the compiler, which then get mixed with the
system-provided flags "-D_FORTIFY_SOURCE=2". Which in turn causes
a fatal warning.
$ export CFLAGS=-O0; ./autogen.sh --enable-more-warnings=error && make
Workaround that, by injecting "-Wno-error" to the CFLAGS, like we
do for NetworkManager (commit f6272144e98c00db18cf6708aceab96e6e7b1705).
Related: https://bugzilla.gnome.org/show_bug.cgi?id=757934
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=762950
|
|
|
|
|
|
| |
Fixes: aa69f9c7cd441e1b091bf4c400182b27b0fb8314
https://bugzilla.gnome.org/show_bug.cgi?id=762944
|
| |
|
| |
|
|\
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=762421
|
| |
| |
| |
| |
| |
| |
| |
| | |
Seems we can hit
(nm-applet:4985): nm-applet-CRITICAL **: nma_icons_reload: assertion 'applet->isize > 0' failed
which can only happen if the icon-size reported by "size-changed" is
negative. Avoid that.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- adjust the signature of nma_icons_reload() to the "changed" signal
of GtkIconTheme.
- don't return TRUE or FALSE depending on success (note that we
already asserted that FALSE must not happen). Instead, log
a warning with g_critical(), which is more graceful.
- free @fallback_icon, avoiding leaking the icon on multiple
invocations.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
nma_icon_check_and_load() would not take an additional reference
for the @fallback_icon.
Note that nma_icons_free() would not unref the icon if it equals the
fallback_icon, but destroying @icon_cache would. So, during finalize()
we hit the bug, but also when nma_icons_reload() replaces
@fallback_icon.
https://bugzilla.gnome.org/show_bug.cgi?id=762421
https://bugzilla.redhat.com/show_bug.cgi?id=1284671
https://bugzilla.redhat.com/show_bug.cgi?id=1279937
|
| | |
|
| |
| |
| |
| | |
... and some whitespace.
|
| | |
|
|/ |
|
|\
| |
| |
| | |
Cleanup includes.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Every internal source file should include "nm-default.h"
as first. Therefore, also include "nm-config.h" via the
default header.
|