1. 11 Mar, 2019 1 commit
  2. 05 Mar, 2019 1 commit
  3. 28 Feb, 2019 1 commit
  4. 21 Feb, 2019 1 commit
  5. 07 Feb, 2019 1 commit
  6. 10 Jan, 2019 1 commit
  7. 09 Jan, 2019 1 commit
  8. 31 Dec, 2018 1 commit
    • Michael Catanzaro's avatar
      Remove the browser plugin · 49133c72
      Michael Catanzaro authored
      The browser plugin is crashy and broken; there are dozens of bugs filed
      against it on Bugzilla and nobody is looking at them. Chrome and Firefox
      have both dropped support for NPAPI plugins. Epiphany still has support,
      but it's hidden behind a gsetting and all the UI to enable it has been
      removed, so very few users would be able to figure out how to enable.
      I've even previously considered blacklisting this plugin in the past due
      to all the crashes.
      Since this plugin has not actually worked in any browsers for a long
      time now, time to delete it.
  9. 23 Nov, 2018 1 commit
  10. 14 Nov, 2018 1 commit
  11. 08 Oct, 2018 1 commit
  12. 25 Sep, 2018 1 commit
  13. 03 Sep, 2018 1 commit
  14. 29 Aug, 2018 1 commit
  15. 20 Aug, 2018 1 commit
  16. 06 Aug, 2018 1 commit
  17. 01 Aug, 2018 1 commit
  18. 31 Jul, 2018 2 commits
    • Florian Müllner's avatar
      tools: Migrate changed overrides settings · d57dc94d
      Florian Müllner authored
      While the new per-desktop overrides in GIO are easier to use for
      both developers and users, it is still inconvenient for everyone
      who changed the defaults using the old overrides hack to lose
      their settings. Address this by running a small script on startup
      that migrates existing settings.
    • Didier Roche's avatar
      volume: Allow volume above 100% · d2a97e7f
      Didier Roche authored
      Depending on hardware and recorded volume level, turning up the speakers
      to the maximum volume may not be enough and the user will want to amplify
      the volume above 100%. Currently this requires opening the sound Settings
      panel which gets cumbersome when required repeatedly.
      To support this case better, allow raising the sound volume above 100%
      directly from the system menu if the feature is enabled via the
      `allow-volume-above-100-percent` key in `org.gnome.desktop.sound`.
  19. 30 Jul, 2018 2 commits
    • Daniel Drake's avatar
      Add check_cloexec_fds debug command · 49d8ff38
      Daniel Drake authored
      Add a debug command (to be executed manually via Alt+F2) to check
      that all of gnome-shell's file descriptors have the CLOEXEC flag set.
      This is important so that internal file descriptors do not get passed
      to apps when they are launched.
      It prints a warning message for every fd that does not have the flag set.
      fdwalk() is used from the standard library if available (it is not
      available in glibc), otherwise we use the same implementation as glib
      has internally.
    • Daniel Drake's avatar
      shell-app: remove child_setup from app launching · 4b522a02
      Daniel Drake authored
      When the amount of free memory on the system is somewhat low, gnome-shell
      will sometimes fail to launch apps, reporting the error:
        fork(): Cannot allocate memory
      fork() is failing here because while cloning the process virtual address
      space, Linux worries that the thread being forked may end up COWing the
      entire address space of the parent process (gnome-shell, which is
      memory-hungry), and there is not enough free memory to permit that to
      happen. This check is somewhat irrelevant because we are only forking
      to immediately exec(), which will discard the whole virtual address
      space anyway.
      This issue can be avoided by using a new optimized gspawn codepath in
      the latest glib development version, which uses posix_spawn() internally.
      For the optimized codepath to be used, we must not pass a child_setup
      function, so the the file descriptor management is reimplemented here
      using new glib API to pass fds to the child process. The old API will
      continue to be used on older glib versions.
      We must also change the spawn flags for this code path to be hit.
      I checked that gnome-shell's open file descriptors are all CLOEXEC
      so using G_SPAWN_LEAVE_DESCRIPTORS_OPEN should be safe.
      This will result in more resilient app launching when memory is low,
      since the optimized spawn path avoids cloning the virtual address
      space of the parent process (gnome-shell) and avoids the irrelevant
      memory overcommit check.
  20. 18 Jul, 2018 2 commits
  21. 17 Jul, 2018 1 commit
    • Iain Lane's avatar
      Add systemd units · a5937d1d
      Iain Lane authored
      So that we can be started by systemd --user, instead of gnome-session.
      There are three units:
        - gnome-shell.service: Start gnome-shell itself.
        - gnome-shell-x11.target, gnome-shell-wayland.target: Sync points for
          units that need to care if x11 or wayland is in use.
          gnome-settings-daemon will use these, for example.
  22. 09 Jul, 2018 1 commit
  23. 06 Jul, 2018 1 commit
  24. 24 May, 2018 1 commit
  25. 25 Apr, 2018 1 commit
  26. 23 Apr, 2018 1 commit
  27. 13 Apr, 2018 1 commit
  28. 09 Apr, 2018 1 commit
  29. 19 Mar, 2018 1 commit
  30. 12 Mar, 2018 1 commit
  31. 05 Mar, 2018 1 commit
  32. 21 Feb, 2018 4 commits
  33. 20 Feb, 2018 1 commit
    • Florian Müllner's avatar
      build: Minor cleanups · a347ed99
      Florian Müllner authored
      find_program() defaults to require the program in question, and as
      failing to locate it is now fatal, there's no longer a need for
      checking whether it was found later.
      Spotted by Michael Catanzaro.
  34. 10 Feb, 2018 1 commit
    • Mario Sanchez Prada's avatar
      build: Make sassc mandatory and always generate CSS files from Sass sources · c62e7a6a
      Mario Sanchez Prada authored
      The previous implementation of the CSS generation logic considered sassc
      an optional dependency and made sure for that reason that the result CSS
      files ended up in the source directory, so that they could be checked
      in and kept in sync with the source sass files.
      As we are making sassc a required dependency, we can now stop doing that
      extra work and simply rely on the CSS files being automatically generated
      each time the sass sources change. By doing this, we can now effectively
      get rid of the CSS files checked in the repo as well as of the parse_sass.sh
      script, since the CSS files will now live on the build directory only.