How to prevent a scrollbar with momentum scrolling from hiding itself on iOS Safari?

When you add -webkit-overflow-scrolling: touch; to a scrollable element such as a div for instance, you gain a smoother scrolling experience (native momentum scrolling) but then, you lose the ability to have the scrollbar constantly shown. Because for some obscure reason, Apple decided it’s good UX to hide the scrollbar most of the time.

The problem is that when only 3 items show in your scrollable content and the rest isn’t partially cut, you have no hint telling users that there is a scrollbar and that more items are available.

I would like to know if there is a way to have a scrollable div with momentum scrolling but that never hides itself.

Is being evil aligned, in and of itself, an evil act?

As asked in the title. Is being an evil aligned creature, in and of itself, considered an evil act. I was playing a Paladin at one point, and my more chaotically aligned party members wanted me to take part in a coup of an admittedly Lawful Evil aligned mayor of a town. I felt I couldn’t because while he was evil aligned, he was the lawfully elected mayor of the town, and as much as I am sworn to root out evil, I am also sworn to uphold the law.

my party mentioned how he was evil aligned and therefor I should have attacked him on sight, but i purposed that being Evil aligned is not an evil act. I can only act against them if they actually do something Evil.

Why python script stops executing the statement of loop but the process itself is alive?

i am running face recognition python script on Ubutnu 18.04 as a daemon which takes pictures from another server with ssh request and performs operations on them . i have this code in python script which is always running but the statement of while loop stops being executed . the process itself is alive

While true:  ssh request to another server to recieve pictures   time.sleep(1) 

i check the directory of another server and the pictures are present there

Ubuntu changes line itself while typing with the built-in Keyboard

Ubuntu community,

I have a really disgusting trouble while typing with built-in keyboard on Ubuntu 16.04.06 LTS, the problem is that (I do not know why)while I am typing the line changes or it just delete everything and a lot of weird things, I re-installed the software, update it and nothing worked.

Have you any idea? help please.

Best regards, Santiago

Network manager opened by itself

I left my computer on overnight because it had some updates to install, and I didn’t feel like waiting for it to reboot just to shut it down. However, when I logged back in this morning, the network manager was open and it was displaying all the information for my wifi network.

Anyone know why it happened? Or was someone remotely accessing my computer?

How can I make the ‘modified date’ column of a list reflect when the contents of folder were last modified, not the folder itself?

I am using SharePoint online for work. I have a subsite with 2 WebParts, both of which are lists (XsltListViewWebPart). Each list has folders, with each folder having a number of documents within.

I’d like the ‘modified’ date on the list with the folders to reflect the date that the most recent item within that folder was modified, not the date the folder was modified (meaning if I chose to re-name it or something).

I have done many searches, and the most closely related post I’ve found is here: Showing Folder's modified date as most recently edited documents's modified date in that folder …And it has gone unanswered for 3 years.

Any help or suggestions are appreciated.

Suspend puts computer to sleep, then immediatly wakes itself up

The computer will suspend for a matter of seconds, then without touching anything on my mouse, nor moving it and not touching my keyboard it will wake itself up.

I have tried using: cat /usr/local/sbin/select-resume-devices

Which looks like, I select microftsoft keyboard and save. It makes no difference:

enter image description here

#!/bin/bash #  # Script to create resume udev rules for USB devices # # Depends on zenity # 09/05/2012 - V1.0 by Nicolas Bernaerts  # udev file to generate UDEV_FILE="/etc/udev/rules.d/90-hid-wakeup-enable.rules"  # set separator as CR IFS=$  '\n'  # list all USB devices, excluding root & hubs LIST_DEVICE=(`lsusb | grep -v "0000:0000" | grep -iv "hub" | sed 's/^.*[0-9a-f]\:[0-9a-f]* \(.*\)$  //g'`)  # loop thru the devices array to generate zenity parameter for DEVICE in "$  {LIST_DEVICE[@]}" do   # if needed, remove [xxx] from device name as it gives trouble with grep   DEVICE=`echo "$  DEVICE" | sed 's/\[.*\]//g'`    # add it to the parameters list   ARR_PARAMETER=( FALSE $  {DEVICE} $  {ARR_PARAMETER[@]} ) done  # display the dialog box to choose devices TITLE="Wakeup - Enable USB devices" TEXT="Please, select USB devices you want to use to resume your computer" CHOICE=`zenity --list --width=600 --height=250 --text=$  TEXT --title=$  TITLE --checklist --column "Select" --column "Device name" "$  {ARR_PARAMETER[@]}"`  # slit the device choice into an array IFS="|" read -a ARR_CHOICE <<< "$  CHOICE"  # if at least one device has been selected, initialise udev rules file [ $  {#ARR_CHOICE[@]} -gt 0 ] && echo "# udev rule for USB wake-up of selected devices" > $  UDEV_FILE [ $  {#ARR_CHOICE[@]} -gt 0 ] && echo "#" >> $  UDEV_FILE  # loop thru the selected devices to create udev rules for DEVICE_NAME in "$  {ARR_CHOICE[@]}" do   # get current device data   DEVICE_DATA=`lsusb | grep "$  {DEVICE_NAME}" | sed 's/^.*ID \([0-9a-f]*\):\([0-9a-f]*\).*$  /|/g'`   DEVICE_VENDOR=`echo $  DEVICE_DATA | cut -d"|" -f1`   DEVICE_PRODUCT=`echo $  DEVICE_DATA | cut -d"|" -f2`    # create udev rule for current device   DEVICE_RULE="SUBSYSTEM==\"usb\", ATTRS{idVendor}==\"$  DEVICE_VENDOR\", ATTRS{idProduct}==\"$  DEVICE_PRODUCT\" RUN+=\"/usr/local/sbin/enable-wakeup $  env{DEVPATH}\" "    # add udev rule for current device   echo "# $  {DEVICE_NAME}" >> $  UDEV_FILE   echo $  {DEVICE_RULE} >> $  UDEV_FILE done  # if at least one device has been selected, display notification TITLE="USB resume enabled" TEXT="Your USB devices are resume enabled.\nTo finalize configuration you have to do one of these actions :\n- replug USB devices\n- reboot the computer" [ $  {#ARR_CHOICE[@]} -gt 0 ] && notify-send --icon=media-eject $  TITLE $  TEXT 

What my wakeup looks like

hutber@hutber:~$   cat /proc/acpi/wakeup Device  S-state   Status   Sysfs node PEG0      S4    *enabled   pci:0000:00:01.0 PEGP      S4    *disabled  pci:0000:01:00.0 PEG1      S4    *disabled PEGP      S4    *disabled PEG2      S4    *disabled PEGP      S4    *disabled SIO1      S3    *disabled  pnp:00:00 PS2K      S4    *disabled PS2M      S4    *disabled UAR1      S4    *disabled  pnp:00:01 RP01      S4    *enabled   pci:0000:00:1c.0 PXSX      S4    *disabled RP02      S4    *disabled PXSX      S4    *disabled RP03      S4    *disabled PXSX      S4    *disabled RP04      S4    *disabled PXSX      S4    *disabled RP05      S4    *disabled PXSX      S4    *disabled RP06      S4    *enabled   pci:0000:00:1c.5 PXSX      S4    *disabled  pci:0000:04:00.0 RP07      S4    *enabled   pci:0000:00:1c.6 PXSX      S4    *enabled   pci:0000:05:00.0 RP08      S4    *enabled   pci:0000:00:1c.7 PXSX      S4    *disabled  pci:0000:06:00.0 RP09      S4    *enabled   pci:0000:00:1d.0 PXSX      S4    *disabled  pci:0000:08:00.0 RP10      S4    *disabled PXSX      S4    *disabled RP11      S4    *disabled PXSX      S4    *disabled RP12      S4    *disabled PXSX      S4    *disabled RP13      S4    *disabled PXSX      S4    *disabled RP14      S4    *disabled PXSX      S4    *disabled RP15      S4    *disabled PXSX      S4    *disabled RP16      S4    *disabled PXSX      S4    *disabled RP17      S4    *disabled  pci:0000:00:1b.0 PXSX      S4    *disabled RP18      S4    *disabled PXSX      S4    *disabled RP19      S4    *disabled PXSX      S4    *disabled RP20      S4    *disabled PXSX      S4    *disabled RP21      S4    *disabled PXSX      S4    *disabled RP22      S4    *disabled PXSX      S4    *disabled RP23      S4    *disabled PXSX      S4    *disabled RP24      S4    *disabled PXSX      S4    *disabled GLAN      S4    *enabled   pci:0000:00:1f.6 XHC   S4    *enabled   pci:0000:00:14.0 XDCI      S4    *disabled HDAS      S4    *disabled  pci:0000:00:1f.3 CNVW      S4    *disabled 

Ubuntu 18.04 restarting by itself after shutdown

I know there are already plenty questions here related to this one, but I can’t find an answer which solves my problem.

I’ve installed a fresh Ubuntu 18.04 on a Dell Optiplex 9020 SFF. And now I’m trying to make WOL – Wake On Lan – working. The first step I’ve done was to activate WOL in BIOS and deactivate Deep Sleep. And it seems to just work as expected.

I can shutdown PC and wake it up with a magic packet (and do it an unlimited number of times).

But if I choose to restart/reboot, the PC will do it normally and then if I try to shut it down (with the button on the top-right of the screen (or with a shutdown now, shutdown -H now) it will shutdown, wait 3 seconds, and then reboot by itself. The only way to shut it down is to long press the hardware power button. And then it reworks as expected (with WOL) until the next reboot/restart is issued.

I’ve tried several things in /etc/default/grub like adding acpi=force apm=power_off or noapic or reboot=a,w followed by an update-grub. I’ve also updated my BIOS to latest version (A25). But nothing works.

I think the problem is when I trigger a reboot, something change somewhere and make following shutdown working a bit differently and cause computer to reboot by itself.

I’ve maybe a clue after investigating journalctl. When I trigger a normal shutdown (without a reboot before):

sept. 07 00:57:28 barbie systemd[1]: Reached target Shutdown. sept. 07 00:57:28 barbie systemd[1]: Reached target Final Step. sept. 07 00:57:28 barbie systemd[1]: Starting Power-Off... sept. 07 00:57:28 barbie systemd[1]: Shutting down. sept. 07 00:57:28 barbie kernel: printk: systemd-shutdow: 40 output lines suppressed due to ratelimiting sept. 07 00:57:28 barbie systemd-shutdown[1]: Syncing filesystems and block devices. sept. 07 00:57:28 barbie systemd-shutdown[1]: Sending SIGTERM to remaining processes... sept. 07 00:57:28 barbie systemd-journald[431]: Journal stopped 

And when I trigger a shutdown (with a reboot before):

sept. 07 00:59:08 barbie systemd[1]: Reached target Shutdown. sept. 07 00:59:08 barbie systemd[1]: Reached target Final Step. sept. 07 00:59:08 barbie systemd[1]: Starting Power-Off... sept. 07 00:59:08 barbie systemd[1]: Shutting down. sept. 07 00:59:08 barbie kernel: printk: systemd-shutdow: 39 output lines suppressed due to ratelimiting sept. 07 00:59:08 barbie systemd-shutdown[1]: Syncing filesystems and block devices. sept. 07 00:59:08 barbie systemd-journald[426]: Journal stopped 

Note the missing line: systemd-shutdown[1]: Sending SIGTERM to remaining processes... Maybe it explains why the computer reboot by itself ?

That’s all I’ve done so far. Your clues/ideas are welcome. Thanks!