| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
libnm's NMSecretAgentOld is a GInitable and requires explicit
initialization.
Fixes: 3722a190468f5ce5898db8838611bc826d3153f1
|
| |
|
|
|
|
| |
Fixes: 4d7546e7d0e56c3a102a12ba03695eac6f8109f8
|
|\
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=736911
|
| | |
|
| |
| |
| |
| |
| | |
We only care about TERM/INT, and those are already handled OK by
the event loop. We don't need custom handling for them.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Based on a patch by Jiří Klimeš.
|
| |
| |
| |
| | |
Based on a patch by Jiří Klimeš.
|
| |
| |
| |
| | |
It might get used where NMA_* won't be.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add a new libnm-based version of libnm-gtk, called "libnma" (which
matches the naming convention of the functions better anyway). Also,
rename the files from nm-* to nma-*.
Drop nm-wireless-dialog (which was deprecated in favor of
nma-wifi-dialog) and nm-ui-utils.h (whose functionality has been
merged into NMDevice in libnm).
(libnm-glib to libnm porting mostly based on a patch by Jiří Klimeš.)
|
| |
| |
| |
| |
| |
| | |
Also, drop the "ssid" parameter from wireless_security_validate(),
since it would need to be different between the two versions, but it
turns out it's not actually used anyway.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Remove "PKG_CHECK_MODULES(GOBJECT, gobject-2.0)", which wasn't being
used, and which was already implied by other checks.
Remove a bunch of unecessary AC_SUBST() calls in configure.ac.
(PKG_CHECK_MODULES automatically substs the variables it sets.)
Remove GNOME_MAINTAINER_MODE_DEFINES, which just sets a bunch of
irrelevant flags like BONOBO_DISABLE_DEPRECATED.
|
| |
| |
| |
| |
| | |
The current version of gnome-bluetooth does not support plugins, so
there's no reason to keep this around any more.
|
| |
| |
| |
| |
| |
| | |
Anyone upgrading directly from 0.8 to 1.2 will just lose their old
non-system connections. (Which they probably would have anyway, since
the migration tool only gets run if nm-applet does...)
|
|/
|
|
|
| |
Delete the custom-marshaller code and use g_cclosure_marshal_generic()
everywhere.
|
| |
|
| |
|
|
|
|
|
| |
'pixbuf' isn't used for indicator+icon-name, but is used for
indicator+icon-data and non-indicator cases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It seems that many implementations don't support pixmaps at all,
instead using only the icon-name. Unfortunately that means that
these implementations' users loose some valuable information like
encryption status of the AP, but it's better than showing no
icon at all.
There are two solutions to this problem:
1) extend dbusmenu to allow multiple icons, which we would use to
show both the signal bars and a lock icon, much like Mac OS X and
iOS. This is preferable.
2) add all possible icon combinations (5 signal bars * 2 encryption
states). This is less easy for theme authors to work with and
means shipping more icons. Not preferred. Work on dbusmenu instead.
|
|
|
|
|
|
| |
Remove the separate adhoc icon in the menu, and just replace the signal
bars with the adhoc icon for these networks. Consolidate some code
paths between normal and indicator modes.
|
|\
| |
| |
| |
| |
| |
| | |
For the moment only pixmaps are passed for WiFi/WWAN menu items
are passed instead of the icon name. Not all implementations
of appindicator/dbusmenu support pixmap data (Enlightenment is
one that does not) but we'll work on that.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add new configure option --with-appindicator which implies a optional
dependency on libappindicator. This is the way systray is done in the
current versions of Unity, KDE and Enlightenment and others. Some of the
systray implementations already dropped support for Xembed, others are
going to, mostly to gain independence on X11 as part of being ported to
Wayland.
Keep the previous functionality intact.
(many cleanups and consolidations by dcbw)
https://bugzilla.gnome.org/show_bug.cgi?id=740574
|
| |
| |
| |
| |
| | |
Without this patch the VPN items won't display correctly in appindicator
mode.
|
| |
| |
| |
| |
| | |
Without this patch, the VPN items would sometimes not show at all
in appindicator mode.
|
| | |
|
|/
|
|
|
|
| |
Collapse some of the setters into nm_network_menu_item_new() since
these properties actually never change. Add some ATK descriptions
too.
|
|
|
|
|
|
|
|
| |
This is especially useful when debugging with G_DEBUG=fatal-warnings
in cases when you don't expect the agent to register successfully,
e.g. due to an already registered nm-applet.
https://bugzilla.gnome.org/show_bug.cgi?id=744163
|
|
|
|
|
|
| |
Add --keep-above, to tell nm-c-e to mark all of its windows "keep
above". (For use by anaconda, to keep them from getting lost under its
fullscreen window.)
|
| |
|
|
|
|
|
|
| |
Add an empty applet_schedule_update_menu() that would later be used
by the appindicator code. Prepare the code for the final appindicator
patch.
|
|
|
|
|
|
|
| |
Whenever possible, return icon name from applet_update_icon() and only
load it in foo_set_icon().
https://bugzilla.gnome.org/show_bug.cgi?id=740574
|
|
|
|
|
|
| |
NetworkManager 1.0 and later don't support the old ModemManager, and
the applet doesn't support old versions of NetworkManager, so remove
the obsolete support and bump the version requirements to NM 1.0+.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Finalization is reordered in a way that allows seamless implementation
of appindicator mode. Initialization now only includes objects that
actually need some.
https://bugzilla.gnome.org/show_bug.cgi?id=740574
|
|
|
|
|
|
|
|
|
| |
With appindicator patches, when built with --enable-indicator,
setup_widgets has to build the whole menu and thus requires access to
NetworkManager data. The patch doesn't cause any harm in non-indicator
mode.
https://bugzilla.gnome.org/show_bug.cgi?id=740574
|
|
|
|
|
|
|
|
| |
The widgets are owned by their respective containers. They get unreffed
and disposed with the menu item. This caused problems with the
appindicator patches where the whole menu is destroyed and recreated.
https://bugzilla.gnome.org/show_bug.cgi?id=740574
|
| |
|
|
|
|
|
|
| |
The method is called `dispose`, not `class_dispose`.
https://bugzilla.gnome.org/show_bug.cgi?id=744164
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If we cannot get an icon name to use based on the access tech, don't segfault.
Instead, just ignore the access tech icon.
Program received signal SIGSEGV, Segmentation fault.
0xb6ffb07a in g_str_hash () from /usr/lib/libglib-2.0.so.0
(gdb) bt full
#0 0xb6ffb07a in g_str_hash () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#1 0xb6ffa4a8 in g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#2 0x0805dfef in nma_icon_check_and_load ()
No symbol table info available.
#3 0x0806e778 in mobile_helper_get_status_pixbuf ()
No symbol table info available.
#4 0x0806f042 in mobile_helper_get_icon ()
No symbol table info available.
#5 0x080724d2 in ?? ()
No symbol table info available.
#6 0x0805e80a in ?? ()
No symbol table info available.
#7 0xb7008130 in ?? () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#8 0xb700b8d3 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#9 0xb700bce9 in ?? () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#10 0xb700c099 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
No symbol table info available.
#11 0x08056654 in main ()
https://bugs.archlinux.org/task/43576
https://bugzilla.gnome.org/show_bug.cgi?id=744421
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=726018
|
|
|
|
|
|
|
| |
Make sure we only ever have one of the "Don't show this again" button that
will trigger disabling notifications. Otherwise we end up with multiple
instances of the same button in notifications because one gets added every
time a new notification stacks on top of an existing one.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We were setting -DNM_VERSION_MAX_ALLOWED=NM_VERSION_0_9_10, but if you
don't set NM_VERSION_MIN_REQUIRED, it defaults to
NM_VERSION_CUR_STABLE, which meant that we were setting MIN to 1_0 and
MAX to 0_9_10, which clearly won't work. Fix this by setting MIN to
0_9_10 too (since that's still the version we're requiring in
configure).
https://bugzilla.gnome.org/show_bug.cgi?id=743343
|