#StackBounty: #brightness #xfce #xubuntu #xfce4 #ubuntu-20.04 What can you do when you've accidentally turned your brightness all o…

Bounty: 50

I’ve recently encountered something quite annoying in Xfce. I can control my brightness with my Fn key shortcuts only if I am not in a menu. This means that if I go in to the power manager plugin panel icon’s menu and accidentally turn my brightness all of the way down, blackening my screen, my only methods of restoring it are to click blindly in hopes of either getting off of the power manager’s menu or upping my brightness. As this may cause me to click on something undesirable, this is not a good method. However, being in a menu blocks all of my non-Syskey keyboard inputs, including Ctrl+Alt+T and my Fn keys, so it appears that my only other course of action is to REISUB or to change in to a tty that will also be totally black and therefore useless (the ttys also ignore my Fn keys).

My question then is this: What should I do when I’ve accidentally turned my brightness all of the way down with the power manager’s menu?


Get this bounty!!!

#StackBounty: #brightness #xfce #xubuntu #xfce4 #ubuntu-20.04 What can you do when you've accidentally turned your brightness all o…

Bounty: 50

I’ve recently encountered something quite annoying in Xfce. I can control my brightness with my Fn key shortcuts only if I am not in a menu. This means that if I go in to the power manager plugin panel icon’s menu and accidentally turn my brightness all of the way down, blackening my screen, my only methods of restoring it are to click blindly in hopes of either getting off of the power manager’s menu or upping my brightness. As this may cause me to click on something undesirable, this is not a good method. However, being in a menu blocks all of my non-Syskey keyboard inputs, including Ctrl+Alt+T and my Fn keys, so it appears that my only other course of action is to REISUB or to change in to a tty that will also be totally black and therefore useless (the ttys also ignore my Fn keys).

My question then is this: What should I do when I’ve accidentally turned my brightness all of the way down with the power manager’s menu?


Get this bounty!!!

#StackBounty: #brightness #xfce #xubuntu #xfce4 #ubuntu-20.04 What can you do when you've accidentally turned your brightness all o…

Bounty: 50

I’ve recently encountered something quite annoying in Xfce. I can control my brightness with my Fn key shortcuts only if I am not in a menu. This means that if I go in to the power manager plugin panel icon’s menu and accidentally turn my brightness all of the way down, blackening my screen, my only methods of restoring it are to click blindly in hopes of either getting off of the power manager’s menu or upping my brightness. As this may cause me to click on something undesirable, this is not a good method. However, being in a menu blocks all of my non-Syskey keyboard inputs, including Ctrl+Alt+T and my Fn keys, so it appears that my only other course of action is to REISUB or to change in to a tty that will also be totally black and therefore useless (the ttys also ignore my Fn keys).

My question then is this: What should I do when I’ve accidentally turned my brightness all of the way down with the power manager’s menu?


Get this bounty!!!

#StackBounty: #brightness #xfce #xubuntu #xfce4 #ubuntu-20.04 What can you do when you've accidentally turned your brightness all o…

Bounty: 50

I’ve recently encountered something quite annoying in Xfce. I can control my brightness with my Fn key shortcuts only if I am not in a menu. This means that if I go in to the power manager plugin panel icon’s menu and accidentally turn my brightness all of the way down, blackening my screen, my only methods of restoring it are to click blindly in hopes of either getting off of the power manager’s menu or upping my brightness. As this may cause me to click on something undesirable, this is not a good method. However, being in a menu blocks all of my non-Syskey keyboard inputs, including Ctrl+Alt+T and my Fn keys, so it appears that my only other course of action is to REISUB or to change in to a tty that will also be totally black and therefore useless (the ttys also ignore my Fn keys).

My question then is this: What should I do when I’ve accidentally turned my brightness all of the way down with the power manager’s menu?


Get this bounty!!!

#StackBounty: #brightness #xfce #xubuntu #xfce4 #ubuntu-20.04 What can you do when you've accidentally turned your brightness all o…

Bounty: 50

I’ve recently encountered something quite annoying in Xfce. I can control my brightness with my Fn key shortcuts only if I am not in a menu. This means that if I go in to the power manager plugin panel icon’s menu and accidentally turn my brightness all of the way down, blackening my screen, my only methods of restoring it are to click blindly in hopes of either getting off of the power manager’s menu or upping my brightness. As this may cause me to click on something undesirable, this is not a good method. However, being in a menu blocks all of my non-Syskey keyboard inputs, including Ctrl+Alt+T and my Fn keys, so it appears that my only other course of action is to REISUB or to change in to a tty that will also be totally black and therefore useless (the ttys also ignore my Fn keys).

My question then is this: What should I do when I’ve accidentally turned my brightness all of the way down with the power manager’s menu?


Get this bounty!!!

#StackBounty: #brightness #xfce #xubuntu #xfce4 #ubuntu-20.04 What can you do when you've accidentally turned your brightness all o…

Bounty: 50

I’ve recently encountered something quite annoying in Xfce. I can control my brightness with my Fn key shortcuts only if I am not in a menu. This means that if I go in to the power manager plugin panel icon’s menu and accidentally turn my brightness all of the way down, blackening my screen, my only methods of restoring it are to click blindly in hopes of either getting off of the power manager’s menu or upping my brightness. As this may cause me to click on something undesirable, this is not a good method. However, being in a menu blocks all of my non-Syskey keyboard inputs, including Ctrl+Alt+T and my Fn keys, so it appears that my only other course of action is to REISUB or to change in to a tty that will also be totally black and therefore useless (the ttys also ignore my Fn keys).

My question then is this: What should I do when I’ve accidentally turned my brightness all of the way down with the power manager’s menu?


Get this bounty!!!

#StackBounty: #linux #xfce #xubuntu #xfce4 #ubuntu-20.04 Xfce's clock is slow to update after waking from suspend, is this normal?

Bounty: 50

I’m running Xubuntu 20.04, which I believe puts me on Xfce 4.14. This issue has got me in to some trouble when I return to my machine and contact people whilst having a completely wrong idea of what time it is. The issue can be triggered as follows:

  • Take a note of the time as reported by the panel’s clock and suspend to RAM before it changes.
  • Wait a while. I typically leave for hours, but I presume that a few minutes is sufficient.
  • Wake the machine and log back in.
  • Look at the time, it will still be stuck at what it was when you left.
  • I suspect that the time doesn’t change until you hit the end of the current minute. For example, if you leave at 8:30:45 and come back at 9:30:20, I suspect that it will take 40 seconds to update to 9:31.

Is this a known bug with known fixes?


Get this bounty!!!

#StackBounty: #xfce #xubuntu Why can I sometimes click on the edges of a maximized window?

Bounty: 50

I apologize if this question is vague. I’ve seen this oddity vary not just between programs, but between Firefox profiles, so I’m understandably quite confused and have no idea how to give replication steps.

My issue is that that some of my maximized windows are behaving differently from others. In some, they work just how I’d expect and their content takes up all of my screen except for the panel, meaning that they have no “edge” from which I could resize them without unmaximizing. In other maximized windows, I can move my cursor to any of their edges and I will discover that my cursor is truly on an edge and therefore I’m capable of resizing a window that claims to be maximized. Stranger still, I’ve discovered that RStudio has this issue on all of its edges except for its right one.

Why does this inconsistency exist? It’s causing some very annoying behavior. For example, if my cursor is in the wrong place while I’m trying to use it to scroll up my maximized text editor of choice (Geany), I sometimes end up resizing the window and ending up in a completely unintended place.


Get this bounty!!!

#StackBounty: #keyboard #xubuntu #keyboard-layout Install Dvorak International

Bounty: 50

I would like to install the following Dvorak International Keyboard Layout.

I have tried adding the file to /usr/share/X11/xkb/symbols/

and editing the file xfree86.xml but it is not selectable in xubuntu.

Is there a place I can file this as a bug? Ideally this should be modified to be just like Macs such that you simply need to drop in the file.

// Dvorak interational extended keyboard layout for linux
// version 1.01
// http://arjenvankol.com/dvorak.php
//
// Install instructions:
//
// Copy this file to your /etc/X11/xkb/symbols/pc directory.
// You may need root privileges to do so.
//
// Add the following line to /etc/X11/xkb/rules/xfree86.lst
//
// dvorak_intl  Dvorak international extended
//
// In order to make the keyboard layout available in GNOME,
// you should also modify /etc/X11/xkb/rules/xfree86.xml
// accordingly (this is an XML file and the format is mostly
// self-explanatory).
//
// 2007/12/19 23:25 +0100 Arjen van Kol

partial default alphanumeric_keys
xkb_symbols "basic" {

    name[Group1]= "Dvorak international extended";

    // Alphanumeric section

    key <TLDE> { [       dead_grave, dead_tilde ]   };

    key <AE01> { [      1,  exclam, exclamdown, U00B9 ] };
    key <AE02> { [      2,  at, U00B2 ]     };
    key <AE03> { [      3,  numbersign, U00B3 ] };
    key <AE04> { [      4,  dollar, currency, U00A3 ] };
    key <AE05> { [      5,  percent, EuroSign ] };
    key <AE06> { [      6,  dead_circumflex, U00BC ]};
    key <AE07> { [      7,  ampersand, U00BD ]  };
    key <AE08> { [      8,  asterisk, U00BE ]   };
    key <AE09> { [      9,  parenleft, U2018 ]  };
    key <AE10> { [      0,  parenright, U2019 ] };
    key <AE11> { [ bracketleft, braceleft, guillemotleft ] };
    key <AE12> { [ bracketright, braceright, guillemotright ] };

    key <AD01> { [  dead_acute, dead_diaeresis, U00E4, U00C4 ] };
    key <AD02> { [  comma,  less, U00E5, U00C5 ]    };
    key <AD03> { [      period, greater, U00F6, U00D6 ] };
    key <AD04> { [      p,  P, paragraph, degree ]  };
    key <AD05> { [      y,  Y, U00FC, U00DC ]   };
    key <AD06> { [      f,  F       ]   };
    key <AD07> { [      g,  G, U00E7, U00C7 ]   };
    key <AD08> { [      c,  C, copyright, U00A2 ]   };
    key <AD09> { [      r,  R, registered   ]   };
    key <AD10> { [      l,  L       ]   };
    key <AD11> { [  slash,  question, questiondown ]};
    key <AD12> { [  equal,  plus, U00D7, U00F7 ]    };

    key <AC01> { [      a,  A, U00E1, U00C1 ]   };
    key <AC02> { [      o,  O, U00E5, U00C5 ]   };
    key <AC03> { [      e,  E, U00E9, U00E9 ]   };
    key <AC04> { [      u,  U, U00FA, U00DA ]   };
    key <AC05> { [      i,  I, U00ED, U00CD ]   };
    key <AC06> { [      d,  D, U00F0, U00D0 ]   };
    key <AC07> { [      h,  H       ]   };
    key <AC08> { [      t,  T, U00FE, U00DE ]   };
    key <AC09> { [      n,  N, U00F1, U00D1 ]   };
    key <AC10> { [      s,  S, ssharp, section ]    };
    key <AC11> { [  minus,  underscore, yen ]   };
    key <BKSL> { [  backslash, bar, U00AC, brokenbar ]  };

    key <AB01> { [   semicolon, colon,ae, AE ] };
    key <AB02> { [      q,  Q, U00F8, U00D8 ]   };
    key <AB03> { [      j,  J       ]   };
    key <AB04> { [      k,  K       ]   };
    key <AB05> { [      x,  X       ]   };
    key <AB06> { [      b,  B       ]   };
    key <AB07> { [      m,  M, U00B5    ]   };
    key <AB08> { [      w,  W       ]   };
    key <AB09> { [      v,  V       ]   };
    key <AB10> { [      z,  Z       ]   };

    include "level3(ralt_switch)"
};


Get this bounty!!!

#StackBounty: #xubuntu #suspend #live-usb #ssd #19.10 Why would a suspend issue exist on an installed OS but not its Live Disk?

Bounty: 50

I’m trying to fix a strange suspend problem on Xubuntu 19.10. I was recently advised to test if this was a Xubuntu-only issue by trying the Live Disks for others OSs to see if the problem persisted there. In what turned out to be a smart move, I first tried the same Live Disk that Xubuntu 19.10 OS was installed from (in this case, a USB stick). To my surprise, the suspend issue exists on the installed OS but not the Live Disk.

How could this happen? To my knowledge, I’ve made no relevant changed to Xubuntu’s settings – after all, I’ve had this problem since installing – and aside from not having mounted the SSD that holds the Xubuntu installation, I know of almost nothing that would be used by the Live Disk in a way different to that of the real installation. My only guesses are as follows:

1) Some Xubuntu update that my real installation has that my Live Disk does not is causing the problem.

2) There is some issue with my SSD.

Are there any other alternatives? Where can I investigate the possibilities?

Note: This question isn’t for solving the suspend problem – that would be a near duplicate of the linked question. My interest here is specifically in how I can have a problem on an installation that is not on its Live Disk.


Get this bounty!!!