Urgent notifications not showing up in fullscreen mode

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite
1












I'm on Ubuntu 18.04. I did a clean install, all is nice and quite stable, but I can't see urgent notifications in fullscreen mode (es. YouTube videos in Google Chrome, movies on MPV, Totem or VLC). I tried using --urgency-critical and -u critical, and I saw they're working in normal use as I have to click on the X button to remove them, but this command doesn't put them on top like in 17.10. I don't understand if it's a Gnome Shell bug or I have to do something new.
It's really annoying because I don't see the battery low notification and my laptop switches off everytime I watch a movie. I have to control myself, not comfortable, really.
Anyone knows a workaround or something?







share|improve this question

























    up vote
    1
    down vote

    favorite
    1












    I'm on Ubuntu 18.04. I did a clean install, all is nice and quite stable, but I can't see urgent notifications in fullscreen mode (es. YouTube videos in Google Chrome, movies on MPV, Totem or VLC). I tried using --urgency-critical and -u critical, and I saw they're working in normal use as I have to click on the X button to remove them, but this command doesn't put them on top like in 17.10. I don't understand if it's a Gnome Shell bug or I have to do something new.
    It's really annoying because I don't see the battery low notification and my laptop switches off everytime I watch a movie. I have to control myself, not comfortable, really.
    Anyone knows a workaround or something?







    share|improve this question























      up vote
      1
      down vote

      favorite
      1









      up vote
      1
      down vote

      favorite
      1






      1





      I'm on Ubuntu 18.04. I did a clean install, all is nice and quite stable, but I can't see urgent notifications in fullscreen mode (es. YouTube videos in Google Chrome, movies on MPV, Totem or VLC). I tried using --urgency-critical and -u critical, and I saw they're working in normal use as I have to click on the X button to remove them, but this command doesn't put them on top like in 17.10. I don't understand if it's a Gnome Shell bug or I have to do something new.
      It's really annoying because I don't see the battery low notification and my laptop switches off everytime I watch a movie. I have to control myself, not comfortable, really.
      Anyone knows a workaround or something?







      share|improve this question













      I'm on Ubuntu 18.04. I did a clean install, all is nice and quite stable, but I can't see urgent notifications in fullscreen mode (es. YouTube videos in Google Chrome, movies on MPV, Totem or VLC). I tried using --urgency-critical and -u critical, and I saw they're working in normal use as I have to click on the X button to remove them, but this command doesn't put them on top like in 17.10. I don't understand if it's a Gnome Shell bug or I have to do something new.
      It's really annoying because I don't see the battery low notification and my laptop switches off everytime I watch a movie. I have to control myself, not comfortable, really.
      Anyone knows a workaround or something?









      share|improve this question












      share|improve this question




      share|improve this question








      edited Jun 12 at 16:24
























      asked Jun 11 at 22:25









      nplezka

      1051114




      1051114




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote













          Yes this is very annoying. For workaround, I use zenity's warning dialog-box. It has the benefit of popping up even over full-screen applications:



          zenity --warning --text='Battery Low' --no-wrap



          Getting the current battery percentage programmatically via script is very easy, but will require a little bit of research on your part, because of variability among systems and manufacturers. Start from here.




          Here is my script setup:



          This is batteryLevel.sh :



          #!/bin/bash

          upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep percentage | sed -r 's/[^0-9]*([0-9]+).*/1/'


          This is batteryStatus.sh :



          #!/bin/bash

          upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep state | sed -r 's/.*: +(.*)/1/'


          Finally, this is batteryInfoNotify.sh :



          #!/bin/bash

          upperThreshold=99
          lowerThreshold=20

          echo upperThreshold=$upperThreshold
          echo lowerThreshold=$lowerThreshold

          zenity --info --text='Battery level monitoring started...' --no-wrap 2>&1 >/dev/null

          while [[ true ]]; do
          status=$(~/Scripts/batteryStatus.sh)
          level=$(~/Scripts/batteryLevel.sh)
          msg="Battery Level now is $level%"

          echo "Battery $level% and $status"

          case $status in
          charging | fully-charged)
          if [[ $level -gt $upperThreshold ]]; then
          echo 'Upper threshold crossed...'
          zenity --warning --text="$msg" --no-wrap --timeout=8 2>&1 >/dev/null
          espeak -v en+m7 -p 60 "$msg"
          fi
          ;;
          discharging)
          if [[ $level -lt $lowerThreshold ]]; then
          echo 'Lower threshold crossed...'
          zenity --warning --text="$msg" --no-wrap --timeout=8 2>&1 >/dev/null
          espeak -v en+m7 -p 60 "$msg"
          fi
          ;;
          *)
          echo unexpected battery status
          ;;
          esac

          sleep 30s
          done


          All of these are in my ~/Scripts and batteryInfoNotify.sh is called at session startup everytime because I set it up so in GNOME Startup Appications.






          share|improve this answer























          • very good answer, really useful !
            – damadam
            Jun 14 at 8:00










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045744%2furgent-notifications-not-showing-up-in-fullscreen-mode%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          2
          down vote













          Yes this is very annoying. For workaround, I use zenity's warning dialog-box. It has the benefit of popping up even over full-screen applications:



          zenity --warning --text='Battery Low' --no-wrap



          Getting the current battery percentage programmatically via script is very easy, but will require a little bit of research on your part, because of variability among systems and manufacturers. Start from here.




          Here is my script setup:



          This is batteryLevel.sh :



          #!/bin/bash

          upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep percentage | sed -r 's/[^0-9]*([0-9]+).*/1/'


          This is batteryStatus.sh :



          #!/bin/bash

          upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep state | sed -r 's/.*: +(.*)/1/'


          Finally, this is batteryInfoNotify.sh :



          #!/bin/bash

          upperThreshold=99
          lowerThreshold=20

          echo upperThreshold=$upperThreshold
          echo lowerThreshold=$lowerThreshold

          zenity --info --text='Battery level monitoring started...' --no-wrap 2>&1 >/dev/null

          while [[ true ]]; do
          status=$(~/Scripts/batteryStatus.sh)
          level=$(~/Scripts/batteryLevel.sh)
          msg="Battery Level now is $level%"

          echo "Battery $level% and $status"

          case $status in
          charging | fully-charged)
          if [[ $level -gt $upperThreshold ]]; then
          echo 'Upper threshold crossed...'
          zenity --warning --text="$msg" --no-wrap --timeout=8 2>&1 >/dev/null
          espeak -v en+m7 -p 60 "$msg"
          fi
          ;;
          discharging)
          if [[ $level -lt $lowerThreshold ]]; then
          echo 'Lower threshold crossed...'
          zenity --warning --text="$msg" --no-wrap --timeout=8 2>&1 >/dev/null
          espeak -v en+m7 -p 60 "$msg"
          fi
          ;;
          *)
          echo unexpected battery status
          ;;
          esac

          sleep 30s
          done


          All of these are in my ~/Scripts and batteryInfoNotify.sh is called at session startup everytime because I set it up so in GNOME Startup Appications.






          share|improve this answer























          • very good answer, really useful !
            – damadam
            Jun 14 at 8:00














          up vote
          2
          down vote













          Yes this is very annoying. For workaround, I use zenity's warning dialog-box. It has the benefit of popping up even over full-screen applications:



          zenity --warning --text='Battery Low' --no-wrap



          Getting the current battery percentage programmatically via script is very easy, but will require a little bit of research on your part, because of variability among systems and manufacturers. Start from here.




          Here is my script setup:



          This is batteryLevel.sh :



          #!/bin/bash

          upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep percentage | sed -r 's/[^0-9]*([0-9]+).*/1/'


          This is batteryStatus.sh :



          #!/bin/bash

          upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep state | sed -r 's/.*: +(.*)/1/'


          Finally, this is batteryInfoNotify.sh :



          #!/bin/bash

          upperThreshold=99
          lowerThreshold=20

          echo upperThreshold=$upperThreshold
          echo lowerThreshold=$lowerThreshold

          zenity --info --text='Battery level monitoring started...' --no-wrap 2>&1 >/dev/null

          while [[ true ]]; do
          status=$(~/Scripts/batteryStatus.sh)
          level=$(~/Scripts/batteryLevel.sh)
          msg="Battery Level now is $level%"

          echo "Battery $level% and $status"

          case $status in
          charging | fully-charged)
          if [[ $level -gt $upperThreshold ]]; then
          echo 'Upper threshold crossed...'
          zenity --warning --text="$msg" --no-wrap --timeout=8 2>&1 >/dev/null
          espeak -v en+m7 -p 60 "$msg"
          fi
          ;;
          discharging)
          if [[ $level -lt $lowerThreshold ]]; then
          echo 'Lower threshold crossed...'
          zenity --warning --text="$msg" --no-wrap --timeout=8 2>&1 >/dev/null
          espeak -v en+m7 -p 60 "$msg"
          fi
          ;;
          *)
          echo unexpected battery status
          ;;
          esac

          sleep 30s
          done


          All of these are in my ~/Scripts and batteryInfoNotify.sh is called at session startup everytime because I set it up so in GNOME Startup Appications.






          share|improve this answer























          • very good answer, really useful !
            – damadam
            Jun 14 at 8:00












          up vote
          2
          down vote










          up vote
          2
          down vote









          Yes this is very annoying. For workaround, I use zenity's warning dialog-box. It has the benefit of popping up even over full-screen applications:



          zenity --warning --text='Battery Low' --no-wrap



          Getting the current battery percentage programmatically via script is very easy, but will require a little bit of research on your part, because of variability among systems and manufacturers. Start from here.




          Here is my script setup:



          This is batteryLevel.sh :



          #!/bin/bash

          upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep percentage | sed -r 's/[^0-9]*([0-9]+).*/1/'


          This is batteryStatus.sh :



          #!/bin/bash

          upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep state | sed -r 's/.*: +(.*)/1/'


          Finally, this is batteryInfoNotify.sh :



          #!/bin/bash

          upperThreshold=99
          lowerThreshold=20

          echo upperThreshold=$upperThreshold
          echo lowerThreshold=$lowerThreshold

          zenity --info --text='Battery level monitoring started...' --no-wrap 2>&1 >/dev/null

          while [[ true ]]; do
          status=$(~/Scripts/batteryStatus.sh)
          level=$(~/Scripts/batteryLevel.sh)
          msg="Battery Level now is $level%"

          echo "Battery $level% and $status"

          case $status in
          charging | fully-charged)
          if [[ $level -gt $upperThreshold ]]; then
          echo 'Upper threshold crossed...'
          zenity --warning --text="$msg" --no-wrap --timeout=8 2>&1 >/dev/null
          espeak -v en+m7 -p 60 "$msg"
          fi
          ;;
          discharging)
          if [[ $level -lt $lowerThreshold ]]; then
          echo 'Lower threshold crossed...'
          zenity --warning --text="$msg" --no-wrap --timeout=8 2>&1 >/dev/null
          espeak -v en+m7 -p 60 "$msg"
          fi
          ;;
          *)
          echo unexpected battery status
          ;;
          esac

          sleep 30s
          done


          All of these are in my ~/Scripts and batteryInfoNotify.sh is called at session startup everytime because I set it up so in GNOME Startup Appications.






          share|improve this answer















          Yes this is very annoying. For workaround, I use zenity's warning dialog-box. It has the benefit of popping up even over full-screen applications:



          zenity --warning --text='Battery Low' --no-wrap



          Getting the current battery percentage programmatically via script is very easy, but will require a little bit of research on your part, because of variability among systems and manufacturers. Start from here.




          Here is my script setup:



          This is batteryLevel.sh :



          #!/bin/bash

          upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep percentage | sed -r 's/[^0-9]*([0-9]+).*/1/'


          This is batteryStatus.sh :



          #!/bin/bash

          upower -i /org/freedesktop/UPower/devices/battery_BAT1 | grep state | sed -r 's/.*: +(.*)/1/'


          Finally, this is batteryInfoNotify.sh :



          #!/bin/bash

          upperThreshold=99
          lowerThreshold=20

          echo upperThreshold=$upperThreshold
          echo lowerThreshold=$lowerThreshold

          zenity --info --text='Battery level monitoring started...' --no-wrap 2>&1 >/dev/null

          while [[ true ]]; do
          status=$(~/Scripts/batteryStatus.sh)
          level=$(~/Scripts/batteryLevel.sh)
          msg="Battery Level now is $level%"

          echo "Battery $level% and $status"

          case $status in
          charging | fully-charged)
          if [[ $level -gt $upperThreshold ]]; then
          echo 'Upper threshold crossed...'
          zenity --warning --text="$msg" --no-wrap --timeout=8 2>&1 >/dev/null
          espeak -v en+m7 -p 60 "$msg"
          fi
          ;;
          discharging)
          if [[ $level -lt $lowerThreshold ]]; then
          echo 'Lower threshold crossed...'
          zenity --warning --text="$msg" --no-wrap --timeout=8 2>&1 >/dev/null
          espeak -v en+m7 -p 60 "$msg"
          fi
          ;;
          *)
          echo unexpected battery status
          ;;
          esac

          sleep 30s
          done


          All of these are in my ~/Scripts and batteryInfoNotify.sh is called at session startup everytime because I set it up so in GNOME Startup Appications.







          share|improve this answer















          share|improve this answer



          share|improve this answer








          edited Jun 21 at 17:33


























          answered Jun 14 at 7:35









          AneesAhmed777

          1264




          1264











          • very good answer, really useful !
            – damadam
            Jun 14 at 8:00
















          • very good answer, really useful !
            – damadam
            Jun 14 at 8:00















          very good answer, really useful !
          – damadam
          Jun 14 at 8:00




          very good answer, really useful !
          – damadam
          Jun 14 at 8:00












           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1045744%2furgent-notifications-not-showing-up-in-fullscreen-mode%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

          Trouble downloading packages list due to a “Hash sum mismatch” error

          How do I move numbers in filenames, in a batch renaming operation?