| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This will be used in gnome-initial-setup to determine what to show the user...
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=711428
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=719339
|
|
|
|
|
| |
If we don't have this #include, we get
-Wimplicit-function-declaration.
|
|
|
|
|
|
| |
The offline updates status file needs to be around for the failed text and also
if we're using gnome-software to review the changed updates. We're already
removing it in the callback even for the non-gnome-software case.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It lives in the Debian and Fedora packages at least, and I stopped
digging through downstream package crap after that. From the mailing
list discussion, yeah, while Marcel has a point, in practice, console
users can shut down the machine too...
And many downstreams ship NetworkManager with permissions such that
the user can control system networking to a large degree.
Given that, let's just pull this upstream, anyone who doesn't want it
can work on engineering something else (which is likely making
NetworkManager be a proxy).
The *real* reason I'm doing this is because it avoids librfkill-glib
as used by gnome-shell spewing a g_warning() on start.
https://bugzilla.gnome.org/show_bug.cgi?id=711373
|
|
|
|
| |
Since in Continuous, the gdbus-codegen for Shell ends up there.
|
|
|
|
|
|
|
|
| |
This helps having a clue of which monitor got mapped to the device, other than
waving the pen to check where the pointer ends up. Now gnome-shell is requested
to show an OSD on the monitor the device gets mapped to.
https://bugzilla.gnome.org/show_bug.cgi?id=710373
|
|
|
|
|
|
|
| |
All communication with the shell now goes through this object, both
for OSDs and requesting focus on the shell search entry. One notable
change is that ownership of the shell DBus name is now tracked through
GsdShell::g-name-owner.
|
|
|
|
|
| |
Currently only one helper function is provided to interface with ShowOSD, it
takes care of creating the GVariant with all provided arguments.
|
|
|
|
|
| |
This will be used across multiple plugins, so put it together with
the screensaver and session proxies.
|
|
|
|
|
| |
This is so labels are updated accordingly as soon as the setting
is changed.
|
|
|
|
|
|
|
|
|
| |
If the tablet is set to left-handed mode, invert the labels so
they look natural with the tablet physically rotated. CW and CCW
modes are also taken into account, so text is always displayed
from top to bottom, even though rotated 90 degrees.
https://bugzilla.gnome.org/show_bug.cgi?id=709667
|
|
|
|
|
| |
There could be situations where calling this without updating
button mappings is desired.
|
|
|
|
|
|
|
|
|
| |
Having an intermediate setting where the tablet is mapped to all monitors
comes up as a bit unintuitive, especially on 2 monitor setups, where one
click is required to switch to the other monitor, but then 2 clicks are
required to switch back.
https://bugzilla.gnome.org/show_bug.cgi?id=710373
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Export a property for whether the desktop icons are shown or not. This
will allow Gtk to decide if we should show the 'Desktop' item in the
places sidebar, according to if the user has enabled their desktop icons
or not. We use the value of the GSettings key 'show-desktop-icons' from
'org.gnome.desktop.background'.
https://bugzilla.gnome.org/show_bug.cgi?id=712302
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
fix possible race since notify_have_shell is getting called after the
managers are destroyed.
https://bugzilla.gnome.org/show_bug.cgi?id=711238
Conflicts:
plugins/xsettings/gsd-xsettings-manager.c
|
|
|
|
|
|
|
|
|
|
| |
There's no XF86AudioPlayPause key, just XF86AudioPlay,
even if the kernel does differentiate them (KEY_PLAYPAUSE vs.
KEY_PLAY).
We should send "PlayPause" instead of "Play" to the MPRIS client.
https://bugzilla.gnome.org/show_bug.cgi?id=705348
|
|
|
|
|
|
|
|
|
| |
1. Start MPRIS client, press key, works
2. Close MPRIS client, press key, (/) pops up
3. Start same MPRIS client as 1., press key, (/) pops up
That's because we never unset "connecting" to FALSE once we were
already connected to the MPRIS D-Bus proxy.
|
|
|
|
|
|
|
|
|
|
|
|
| |
We allow using the power key pretty much everywhere now, but
we also ensure that we never show interactive dialogues on the
lock screen (something that was possible with other suspend/power
buttons already if more than more than one user was logged in,
or an interactive shutdown was configured).
See https://bugzilla.redhat.com/show_bug.cgi?id=980692
https://bugzilla.gnome.org/show_bug.cgi?id=707095
|
|
|
|
|
|
|
|
| |
When VNC is in use, animations are disabled, thus ->disabled has
the same value as vnc_in_use, not the opposite.
Spotted by Yosef Or Boczko <yoseforb@gmail.com>, with help from
Jasper St. Pierre <jstpierre@mecheye.net>
|
| |
|
| |
|
|
|
|
| |
For the new API used for the backlight steps.
|
|
|
|
| |
As we use the new API.
|
|
|
|
|
|
|
|
| |
The timestamps are gint64 but we cast them down to guint32, which
can cause overflows. Avoid that by passing the timestamps as gint64
all around, even if they are ultimately unused.
https://bugzilla.gnome.org/show_bug.cgi?id=711066
|
| |
|
|
|
|
|
|
| |
Use min_backlight_step or 5% increments whichever is larger
https://bugzilla.gnome.org/show_bug.cgi?id=710380
|
|
|
|
|
|
|
|
| |
Hardware-blocked rfkills can't be toggled, so they should cause
a different "Airplane mode" UI in the shell and control center
(one that cannot be toggled)
https://bugzilla.gnome.org/show_bug.cgi?id=709684
|
|
|
|
|
|
|
|
| |
USB modems don't expose an rfkill device at the kernel layer,
so we need to go through NetworkManager (which in turn goes
through ModemManager) to disable them.
https://bugzilla.gnome.org/show_bug.cgi?id=709684
|
|
|
|
|
|
| |
Commit 6486696fb16140e3344564a28a75bd92ded5e9ea reworked this code,
listing it as UNTESTED. It is now tested, and needs at least this
fix.
|
|
|
|
|
|
|
| |
Shutdown is supposed to shutdown without asking, as "interactive"
already should do what we need for interactive shutdowns.
https://bugzilla.gnome.org/show_bug.cgi?id=698733
|
|
|
|
| |
They only differed by a single line.
|
|
|
|
|
|
|
|
|
|
|
| |
We merge the remote display object into XSettings, so that
we can override the enable-animations settings without modifying
GSettings. This was especially problematic on startup, or when
overriding user settings.
UNTESTED
https://bugzilla.gnome.org/show_bug.cgi?id=694692
|
|
|
|
|
|
| |
A lot of duplicated code here.
https://bugzilla.gnome.org/show_bug.cgi?id=706698
|
| |
|
|
|
|
|
| |
We don't need to listen to all the changed signals from UpClient,
as we're only interested in the lid state changing.
|
|
|
|
|
|
|
| |
And stop the warning sound as well.
That means, not when the battery state changes, or when
resuming, only when the warning level changes.
|
| |
|
|
|
|
|
| |
There's no need for the test suite to override GSD_ACTION_DELAY,
action is now taken on the UPower side.
|
|
|
|
|
|
| |
As it's UPower taking action, make sure that we stop the alert
sound before the action is taken. We might wake up to the sound
otherwise.
|