#StackBounty: #18.04 #docker #visual-studio-code Having trouble setting default keyboard in visual studio code when developing inside a…

Bounty: 50

I’m having trouble following this guide on Ubuntu 18.04 when working with a specific repository (if anyone would like to follow along, the repo is here). When I try to follow this step:

Select Remote-Containers: Open Folder in Container… from the command
list that appears, and open the root folder of the project you just
cloned.

I run into an issue where Visual Studio code asks me to “Select the keyboard layout for this machine.” As follows:

...
[62625 ms] Setting up netbase (5.4) ...
[62645 ms] Setting up libwebp6:amd64 (0.5.2-1) ...
[62654 ms] Setting up zlib1g-dev:amd64 (1:1.2.8.dfsg-5) ...
[62664 ms] Setting up libdb-dev:amd64 (5.3.1) ...
[62673 ms] Setting up libjsoncpp1:amd64 (1.7.4-3) ...
[62682 ms] Setting up libvorbisfile3:amd64 (1.3.5-4+deb9u2) ...
[62691 ms] Setting up libedit2:amd64 (3.1-20160903-3) ...
[62701 ms] Setting up libgmp-dev:amd64 (2:6.1.2+dfsg-1) ...
[62710 ms] Setting up libx265-95:amd64 (2.1-2+b2) ...
[62719 ms] Setting up keyboard-configuration (1.164) ...
[62790 ms] debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
[63090 ms] Configuring keyboard-configuration
----------------------------------

Please select the layout matching the keyboard for this machine.

[63090 ms]   1. English (US)
  2. English (US) - Cherokee
  3. English (US) - English (Colemak)
  4. English (US) - English (Dvorak alternative international no dead keys)
  5. English (US) - English (Dvorak)
[63091 ms]   6. English (US) - English (Dvorak, international with dead keys)
[63091 ms]   7. English (US) - English (Macintosh)
  8. English (US) - English (Programmer Dvorak)
[63091 ms]   9. English (US) - English (US, alternative international)
  10. English (US) - English (US, international with dead keys)
  11. English (US) - English (US, with euro on 5)
[63091 ms]   12. English (US) - English (Workman)
  13. English (US) - English (Workman, international with dead keys)
[63091 ms]   14. English (US) - English (classic Dvorak)
[63091 ms]   15. English (US) - English (international AltGr dead keys)
[63091 ms]   16. English (US) - English (left handed Dvorak)
[63091 ms]   17. English (US) - English (right handed Dvorak)
  18. English (US) - English (the divide/multiply keys toggle the layout)
  19. English (US) - Russian (US, phonetic)
  20. English (US) - Serbo-Croatian (US)
[63091 ms]   21. Other
[63092 ms] Keyboard layout: 

But I’m unable to actually type in the terminal in VS Code to choose a keyboard? I’ve found a couple other responses to this here where you can do something like this inside the dockerfile: DEBIAN_FRONTEND=noninteractive apt-get install keyboard-configuration But that doesn’t seem to solve the issue either. I’ve tried this entire process on a Macbook just to make sure it’s not just me and it gets past this step just fine, which makes me think it’s an Ubuntu-related problem (or at least vs code on ubuntu problem) but I’m at a bit of a loss on how to get past this.

You can see the dockerfile here (if it helps):

FROM debian:stretch-slim

#
# avoid warnings by switching to noninteractive
ENV DEBIAN_FRONTEND=noninteractive

ARG USERNAME=neko
ARG USER_UID=1000
ARG USER_GID=$USER_UID

#
# install neko dependencies
RUN set -eux; apt-get update; 
    apt-get install -y --no-install-recommends wget ca-certificates pulseaudio openbox dbus-x11 xserver-xorg-video-dummy supervisor; 
    apt-get install -y --no-install-recommends libcairo2 libxcb1 libxrandr2 libxv1 libopus0 libvpx4; 
    #
    # create a non-root user
    groupadd --gid $USER_GID $USERNAME; 
    useradd --uid $USER_UID --gid $USERNAME --shell /bin/bash --create-home $USERNAME; 
    adduser $USERNAME audio; 
    adduser $USERNAME video; 
    adduser $USERNAME pulse; 
    #
    # setup pulseaudio
    mkdir -p /home/$USERNAME/.config/pulse/; 
    echo "default-server=unix:/tmp/pulseaudio.socket" > /home/$USERNAME/.config/pulse/client.conf; 
    #
    # workaround for an X11 problem: http://blog.tigerteufel.de/?p=476
    mkdir /tmp/.X11-unix; chmod 1777 /tmp/.X11-unix; chown $USERNAME /tmp/.X11-unix/; 
    #
    # make directories for neko
    mkdir -p /etc/neko /var/www /var/log/neko; chmod 1777 /var/log/neko; chown $USERNAME /var/log/neko/;  
    chown -R $USERNAME:$USERNAME /home/$USERNAME; 
    #
    # clean up
    apt-get clean -y; 
    rm -rf /var/lib/apt/lists/* /var/cache/apt/*

#
# add gst to env
ENV PATH=/gst/local/bin:$PATH
ENV LD_LIBRARY_PATH=/gst/local/lib:$LD_LIBRARY_PATH
ENV PKG_CONFIG_PATH=/gst/local/lib/pkgconfig:$PKG_CONFIG_PATH

#
# copy gst
COPY .build/gst/local /gst/local/

#
# env
ENV USER=$USERNAME
ENV DISPLAY=:99.0

#
# copy configuation files
COPY .docker/files/dbus /usr/bin/dbus
COPY .docker/files/openbox.xml /etc/neko/openbox.xml
COPY .docker/files/neko/supervisord.conf /etc/neko/supervisord/neko.conf
COPY .docker/files/supervisord.conf /etc/neko/supervisord.conf
COPY .docker/files/xorg.conf /etc/neko/xorg.conf
COPY .docker/files/default.pa /etc/pulse/default.pa

#
# neko files
COPY client/dist/ /var/www
COPY server/bin/neko /usr/bin/neko

#
# neko env
ENV NEKO_PASSWORD=neko
ENV NEKO_ADMIN=admin
ENV NEKO_BIND=:8080

#
# run neko
CMD ["/usr/bin/supervisord", "-c", "/etc/neko/supervisord.conf"]


Get this bounty!!!

#StackBounty: #boot #18.04 #kernel Sporadic Kernel panic – not syncing

Bounty: 50

Sometimes, typically in the first minute after booting I get the following error on my Ubuntu 18.04 LTS setup:

Kernel panic - not syncing: Timeout: Not all CPUs entered broadcast exception handler
[....] Shutting down cpus with NMI
[....] Kernel Offset: 0xe4000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff
[....] Rebooting in 30 seconds..

After that the machine just freezes and never reboots. The PC also has a dual boot setup with windows 10 which never crashes.

Any idea what might be causing this?


Get this bounty!!!

#StackBounty: #networking #drivers #18.04 How to resolve acer_wmi errors filling up kern.log and syslog?

Bounty: 100

Recently bought an Acer Predator Helios 300 and was able to create a working Ubuntu 18.04 and Windows dual boot setup in my third attempt.

I really have my doubts whether all the modules have integrated successfully, hence, I keep an eye out for recurring errors in syslog and kern.log. And currently, both the files are being cluttered with the following message:

acer_wmi: Unknown function number - 11 - 0

They occur every minute. The exact logs look like this:

Mar 25 06:52:37 rand_user667 kernel: [ 1095.786969] acer_wmi: Unknown function number - 11 - 0
Mar 25 06:53:28 rand_user667 kernel: [ 1146.197270] acer_wmi: Unknown function number - 11 - 0
Mar 25 06:54:18 rand_user667 kernel: [ 1196.610322] acer_wmi: Unknown function number - 11 - 0
Mar 25 06:55:08 rand_user667 kernel: [ 1247.024422] acer_wmi: Unknown function number - 11 - 0
Mar 25 06:55:57 rand_user667 kernel: [ 1295.635244] acer_wmi: Unknown function number - 11 - 0
Mar 25 06:56:47 rand_user667 kernel: [ 1346.046235] acer_wmi: Unknown function number - 11 - 0
Mar 25 06:57:38 rand_user667 kernel: [ 1396.452391] acer_wmi: Unknown function number - 11 - 0
Mar 25 06:58:28 rand_user667 kernel: [ 1446.860010] acer_wmi: Unknown function number - 11 - 0
Mar 25 06:59:19 rand_user667 kernel: [ 1497.276243] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:00:07 rand_user667 kernel: [ 1545.880528] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:00:59 rand_user667 kernel: [ 1598.088886] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:01:48 rand_user667 kernel: [ 1646.698326] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:02:38 rand_user667 kernel: [ 1697.102227] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:03:29 rand_user667 kernel: [ 1747.510677] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:04:19 rand_user667 kernel: [ 1797.919387] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:05:08 rand_user667 kernel: [ 1846.332304] acer_wmi: Unknown function number - 9 - 1
Mar 25 07:05:08 rand_user667 kernel: [ 1846.536522] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:05:58 rand_user667 kernel: [ 1896.952896] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:06:49 rand_user667 kernel: [ 1947.381534] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:07:39 rand_user667 kernel: [ 1997.789819] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:08:30 rand_user667 kernel: [ 2048.195628] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:09:20 rand_user667 kernel: [ 2098.595164] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:10:10 rand_user667 kernel: [ 2148.993292] acer_wmi: Unknown function number - 11 - 0
Mar 25 07:11:01 rand_user667 kernel: [ 2199.383051] acer_wmi: Unknown function number - 11 - 0

Did some Googling around to find out that acer_wmi is a helper module. And most of the posts related to acer_wmi ultimately leads to blacklisting of the module. However, all of them had a non-functioning WiFi and they blocked acer_wmi to resolve that issue. The Wifi on my computer is working fine (although the connection seems to be a little slow).

I stumbled upon this post which talks about the necessity of blocking acer_wmi. I followed the steps, did a rfkill list all :

1: acer-wireless: Wireless LAN
    Soft blocked: no
    Hard blocked: no
2: acer-bluetooth: Bluetooth
    Soft blocked: no
    Hard blocked: no
3: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
4: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no

None of them are blocked.

Next command was lsmod | grep acer_wmi:

acer_wmi               24576  0
sparse_keymap          16384  1 acer_wmi
wmi                    32768  3 intel_wmi_thunderbolt,acer_wmi,wmi_bmof
video                  49152  2 acer_wmi,i915

I don’t understand the output at all. But my guess is it lists the services that are attached with acer_wmi. In the aforementioned URL, there are two modules attached to sparse_keymap. So blacklisting acer_wmi from my computer will quite likely disable sparse_keymap?

Is blocking acer_wmi the solution to cluttering of the logs? What should I do? Please advice.


Get this bounty!!!

#StackBounty: #drivers #18.04 #wacom #input-devices #peripherals Wacom Intuos S only recognized in Android Mode

Bounty: 150

The original title of this question was “Only left half of Wacom Intuos S is working”. The text of the original question preserved below. I have since figured out part of the problem, so I am updating this question.

I am using a Wacom Intuos S on Ubuntu 18.04. If I plug it into the laptop, the device automatically goes into Android mode. This is a known issue with Ubuntu. This is confirmed by the output of libwacom-list-local-devices (output shown in the original question) as well as the output of lsusb which lists the vendor ID of the device as 2d1f (as noted in the link above on the issue). The tablet then behaves erratically.

I can toggle the pad to PC mode by holding the leftmost and rightmost button for a few seconds. The tablet then seems to successfully switch to PC mode: lsusb recognizes the device, the vendor ID updates to the correct value, and the indicator light turns on more brightly. However, now the device does not work at all: the cursor does not respond to the movement of the stylus, it is not recognised by Settings (gnome-control-center), and libwacom-list-local-devices does not list it at all. xsetwacom --list devices also comes up empty.

On my home laptop (very similar to my work laptop) switching the pad to PC mode fixes the issue: I can use the tablet without changing anything or updating any drivers. This is also true for a colleague, who was struggling with exactly the same issue (also on Ubuntu). This suggests to me that my attempt to get my drivers into their most recent versions on my work PC is actually what broke the tablet.

What do I need to do so that my tablet is recognized by my Ubuntu PC when it is in PC mode?


Original question text:

My new Wacom Intuos S connects to my Ubuntu laptop, and responds to input, but only its left half (or really, left third) works properly. In the image below I have marked the area that works properly.

Wacom Intuos S with red rectangle on left part of pad

If I move my stylus outside the rectangular area, my cursor still responds to vertical movement (i.e. moving my stylus still causes my cursor to go up and down) but no longer to horizontal movement (i.e. moving my stylus does not cause my cursor to move left to right).

Listing my devices with xsetwacom lists only my stylus and eraser — this is inconsistent with an example I found elsewhere, which lists also a cursor and a pad — but I am not sure if that relates to the problem.

mees@mees-ThinkPad-L480:~$ xsetwacom --list devices
Wacom Co.,Ltd. Intuos S stylus      id: 9   type: STYLUS    
Wacom Co.,Ltd. Intuos S eraser      id: 16  type: ERASER    

Running libwacom-list-local-devices seems to give a relevant hint to the problem:

[Device]
Name=Wacom Intuos S (Android Mode)
DeviceMatch=usb:2d1f:0374;
Class=Bamboo
Width=2
Height=4
IntegratedIn=
Layout=intuos-s-p3.svg
Styli=0;

[full output omitted, can report if necessary]

The reported height and width seem to match the aspect ratio of the part of the device I am actually able to use. I can find the config file (?) that lists the information above, and simply edit the width field to have a different value (e.g. 5), but that does not actually change anything except the output of libwacom-list-local-devices (I have changed it back to the default value of 2 for now).

This problem seems to be Ubuntu-specific: I have tried the tablet on my boyfriend’s Windows laptop, and it works correctly (after installing the relevant drivers). I have also tried it on my personal laptop, which is nearly identical to my work laptop (also a Lenovo Thinkpad with Ubuntu 18.04) and I have the same problems.

What can I do to get my Intuos pad to work properly? Or how can I effectively troubleshoot?

Please let me know if I should provide any further/more detailed information.


Get this bounty!!!

#StackBounty: #18.04 #sound #alsa No microphone in Ubuntu 18.04 on HP elitebook

Bounty: 50

I installed Ubuntu 18.04 on my new HP elitebook 850 G6 after erasing windows. I could not get audio input part working though..
Fn F8 key is orange all the time and this is how settings looks like.

sound

I installed pavucontrol, but that didn’t change anything. What I have noticed is that I cannot check “set as fallback” permanently.

pavucontrol

Also tried editing /etc/modprobe.d/alsa-base.conf by adding

options snd-hda-intel model=auto

Sound control still does not recognize any microphone


Get this bounty!!!

#StackBounty: #drivers #18.04 #wine #amd-graphics #amdgpu Easiest way to check if Wine uses my discrete GPU (AMD)?

Bounty: 50

I’m using dedicated AMD GPU (HD 8570M) and it’s installed correctly in my system.

  *-display                 
   description: Display controller
   product: Sun PRO [Radeon HD 8570A/8570M]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@0000:01:00.0
   version: 00
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi bus_master cap_list rom
   configuration: driver=amdgpu latency=0
   resources: irq:26 memory:b0000000-b7ffffff memory:b8000000-b803ffff ioport:4000(size=256) memory:b8040000-b805ffff

But upon playing game in Wine— it is barely playable, in Windows they DO ran smoothly, and I can confirm Windows actually uses the GPU. I suspected Wine uses my integrated Intel graphics instead.

How would I check that in Wine ? Is there any easy way to figure it out?


Get this bounty!!!

#StackBounty: #networking #18.04 #ssh #samba Slow Samba write speeds, but SSH, FTP is fast

Bounty: 50

I’ve encountered a recent problem with my Samba server (18.04). I have gigabit networking on both ends, but I seem to only get write speeds of about 2MB/s. However, using SSH or FTP, I can transfer files at around 30MB/s which is about what I can expect from my hard drives, so I’m pretty sure the problem is isolated to Samba. Read speeds are about what should be expected. I’ve only noticed this issue recently with 18.04, after I switched from 16.04. I’ve tried tweaking MTU’s, buffers, cache and other things to no avail. I’ve put a fresh install of 18.04 server on another machine and used samba just to see if a fresh install would help, but the issue seems universal to all my machines running 18.04. Any help would be greatly appreciated. My samba conf right now is just the default.


Get this bounty!!!

#StackBounty: #18.04 #suspend Laptop doesn't suspend when closing lid or on manual trigger, then suspends after entering password

Bounty: 50

I am using Ubuntu 18.04 on a Lenovo Thinkpad T480s.
And suspend no longer works.

  1. When triggering suspend through the power options, it takes me to the login screen instead of suspending. After entering my password it goes to sleep.
  2. Similarly, when closing the lid, the laptop stays powered on (fan spinning and LED is solid). I open the lid and I see the login screen. After entering my password it goes to sleep.

How can I find the cause of this issue?


Get this bounty!!!

#StackBounty: #18.04 #suspend Laptop doesn't suspend when closing lid or on manual trigger, then suspends after entering password

Bounty: 50

I am using Ubuntu 18.04 on a Lenovo Thinkpad T480s.
And suspend no longer works.

  1. When triggering suspend through the power options, it takes me to the login screen instead of suspending. After entering my password it goes to sleep.
  2. Similarly, when closing the lid, the laptop stays powered on (fan spinning and LED is solid). I open the lid and I see the login screen. After entering my password it goes to sleep.

How can I find the cause of this issue?


Get this bounty!!!

#StackBounty: #18.04 #suspend Laptop doesn't suspend when closing lid or on manual trigger, then suspends after entering password

Bounty: 50

I am using Ubuntu 18.04 on a Lenovo Thinkpad T480s.
And suspend no longer works.

  1. When triggering suspend through the power options, it takes me to the login screen instead of suspending. After entering my password it goes to sleep.
  2. Similarly, when closing the lid, the laptop stays powered on (fan spinning and LED is solid). I open the lid and I see the login screen. After entering my password it goes to sleep.

How can I find the cause of this issue?


Get this bounty!!!