#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 #ftp #service #proftpd #ubuntu-20.04 Strange ProFTPD behaviour, seems duplicate installation

Bounty: 50

I have a strange problema with a fresh install of ProFTPD on Ubuntu 20 LTS.
I noticed that after changing some option on the configuration files, when I run services proftpd restart the modifications does not apply, only if I restart the system the changes will make effects.

So I try to sop the service with services proftpd stop but I can keep connecting with the ftp client. So there is something weird here. Can you help me on what to verify?

some output

root@b205d:~# which proftpd
/usr/sbin/proftpd
root@b205d:~# whereis proftpd
proftpd: /usr/sbin/proftpd /usr/lib/proftpd /etc/proftpd /usr/share/proftpd /usr/share/man/man8/proftpd.8.gz


Get this bounty!!!

#StackBounty: #windows-10 #grub #bootloader #veracrypt #ubuntu-20.04 Switch bootloader order MBR: GRUB before VeraCrypt in Legacy dual …

Bounty: 50

Scenario

The following steps were executed:

  1. Installed Windows 10 Pro N on a single disk
  2. Installed dual boot Ubuntu 20.04 on the same disk, which installs GRUB bootloader
  3. Installed VeraCrypt on Windows and performed complete system disk encryption
    • Full disk encryption installs the VeraCrypt bootloader, which is placed in front of the GRUB bootloader on the Master Boot Record (MBR), meaning the GRUB bootloader towards Ubuntu is not available anymore/skipped. In the VeraCrypt bootloader one can either:
      • Press ESC, which does not turn towards GRUB, indicating the Windows 10 install is corrupted since it’s encrypted
      • Enter password correctly, which directly skips the GRUB bootloader, successfully loading Windows 10 and resulting in Ubuntu 20.04 not being accessible/bootable anymore because the GRUB bootloader is skipped

According to this link, one can install something like EasyUEFI to switch the order, placing GRUB in front of VeracCypt, however EasyUEFI does not work on the specified laptop, (acer aspire 7750G) since I was not able to find and enable an UEFI setting option. The device has InsydeH20 setup utility Rev. 3.5 and I assume that only has BIOS (legacy boot), and no UEFI.

Question

How can one switch the order of GRUB to before VeraCrypt in a system with legacy boot such that Ubuntu is accessible again with the full disc encryption?

Attempts

  1. I tried sticking the drive into an UEFI laptop to open it with EasyUEFI to change the MBR, but the program won’t show the disk details, meaning I am not able to shift a bootloader up nor down.
  2. I tried to switch the bootloader to put the Grub loader above Veracrpyt with bcdedit. The command bcedit /enum outputs:
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=DeviceHarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {f1c50cdb-e01f-11ea-8662-d17332f8934a}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    Windowssystem32winload.exe
description             Windows 10
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {f1c50cdd-e01f-11ea-8662-d17332f8934a}
displaymessageoverride  Recovery
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              Windows
resumeobject            {f1c50cdb-e01f-11ea-8662-d17332f8934a}
nx                      OptIn
bootmenupolicy          Standard

I have not yet identified which/whether the grub bootloader is in here. I think current is the VeraCrypt bootloader that points towards the Windows bootloader with: resumeobject {f1c50cdb-e01f-11ea-8662-d17332f8934a}. I would think that if I can find the object ID of the Grub boot loader, I perhaps refer to that from resumeobject, or create a new Grub boot loader entry and add it in front of current. But I have not yet determined how I could make a new entry to add the Grub boot loader to the front with bcdedit.


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: #ubuntu #hyper-v #sr-iov #ubuntu-20.04 SR-IOV not working on Ubuntu 20.04 (hyper-v), works fine on 18.04 LTS

Bounty: 50

I’m running Ubuntu server virtual machines on a Windows Server 2019 system using Hyper-V.
The system is equipped with an Intel I350 network adapter. (The Ubuntu VM’s recognize it as “Ethernet controller: Intel Corporation I350 Virtual Function (rev 01)” )

The Ubuntu 18.04 machines are using SR-IOV out of the box.
These are using the kernel: 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

When I upgraded these 18.04 machines to the latest HWE kernel, SR-IOV stopped working.
Hyper-V reports the network adapters state to be degraded (SR-IOV not operational)
I submitted a bug on launchpad about this issue, over a year ago, but never received an answer (https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1818400)

With the new Ubuntu 20.04 release I’m having the same problem. SR-IOV is not working out of the box on these new Ubuntu VM either.

Does someone here know how to get SR-IOV working on newer kernels? Or how to raise this bug with the Ubuntu developers so that it gets their attention?

What I’ve already tried:
I’ve compared the kernel modules loaded between the 18.04 and 20.04 machines.
On the 20.04 machine I enabled all the missing modules from the 18.04, inside the /etc/modules file:

  • ib_cm
  • ib_core
  • ib_iser
  • iscsi_tcp
  • iw_cm
  • rdma_cm
  • libiscsi
  • libiscsi_tcp
  • pcbc

I noticed these three modules could not be loaded on 20.04:

  • pps_core
  • ptp
  • aes_x86_64


Get this bounty!!!