matousc's questions

I need to open onboard keyboard over full screen browser (Chrome) from Python.

The python call is:

onscreen_keyboard = subprocess.Popen(['onboard', ])
os.system("wmctrl -a onboard -b above")

The python commands are called by button in html page that is opened in the browser.

Problem is, that it does not work always. Sometimes (especially after I switch to browser and go to fullscreen via F11 key) it does not open the kyboard. In this situation I need to exit the fullscreen (now the onboard appear!!! or probably was hidden there all the time). If I close the onboard and switch to fullscreen it works - I can call and close the onboard.

So the problematic scenario:

1. I switch to browser, switch to fullscreen
2. I call the onboard, it does NOT appear
3. I exit the fullscreen, close the onboard and switch the fullscreen on again
4. I call the onboard and it appears correctly. After I close it, I can call it again.

Why it does not work in the first time I switch to the browser from other window? How to fix it and make the onboard behavior consistent?

(note: the exactly same behavior I can see in Firefox, I test it on Ubuntu 18 and 16).

I am trying to install Midori to Ubuntu, starting with:

$ sudo add-apt-repository ppa:midori

The response is:

 Midori Browser
    http://twotoasts.de/index.php/midori/

This PPA is signed. To add the GPG key to your apt keyring:
   sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com A69241F1
Starting with Karmic, adding the PPA and its key is as simple as:
   sudo add-apt-repository ppa:midori

You may also want to use the WebKit-team PPA:
     https://launchpad.net/~webkit-team/+archive/ppa
You can find unstable Midori versions at
    https://launchpad.net/~midori/+archive/midori-dev
 More info: https://launchpad.net/~midori/+archive/ubuntu/ppa
Press [ENTER] to continue or Ctrl-c to cancel adding it.

Hit:1 http://security.ubuntu.com/ubuntu bionic-security InRelease
Ign:2 http://ppa.launchpad.net/midori/ppa/ubuntu xenial InRelease                                                               
Hit:3 http://ch.archive.ubuntu.com/ubuntu bionic InRelease                                                                      
Ign:4 http://ppa.launchpad.net/midori/ppa/ubuntu bionic InRelease                                                         
Hit:5 http://ch.archive.ubuntu.com/ubuntu bionic-updates InRelease                             
Hit:6 http://ch.archive.ubuntu.com/ubuntu bionic-backports InRelease                                                     
Err:7 http://ppa.launchpad.net/midori/ppa/ubuntu xenial Release                                                          
  404  Not Found [IP: 91.189.95.83 80]
Err:8 http://ppa.launchpad.net/midori/ppa/ubuntu bionic Release                                     
  404  Not Found [IP: 91.189.95.83 80]
Hit:9 http://archive.canonical.com/ubuntu bionic InRelease               
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/midori/ppa/ubuntu xenial Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/midori/ppa/ubuntu bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Is there an easy way how to deal with that?

I installed Ubuntu 17.10 successfully in dualbot with Win10. It works for a while. But now it does not start.

Description:

When I select Ubuntu in Grub, it starts writing messages into console - standard procedure before the Ubuntu load screen appears. But before the loading screen displays, it stuck in black screen. Few "console like" messages appears instead of black screen in random intervals, but only for such a short time that it is impossible to read it. However it seems that there is no error or important message.

Occurence:

I am not sure why it starts, probably installation of some updates. It works few times after If I choose to load system with older Kernel. Now it does not load always, no matter what kernel is selected.

What I tried:

I tried to repair packages with advanced options in grub. It seems to finish corectly, but system still does not load.

UPDATE:

My friend has the same problem now. The fix was to boot with older Kernel. So it seems that new linux kernel cause to problem with Ubuntu 17.10.

However I cannot do this fix because I already do not have to working Kernel (someone <16 probably). The Kernels I have:

• 4.13.0-25-generic
• 4.13.0-21-generic
• 4.13.0-19-generic
• 4.13.0-16-generic

How to install it?

I tried:

I logged into root console with recovery mode option and remout the filesystem to enable apt:

mount -o rw,remount /

After I check the list of available Kernels and try to install older one:

sudo apt-get update
sudo apt-get install linux-image-4.13.0-15-generic 

I get the "unable to locate package" error. No matter what version of core I tried. I find out that it is because of a lack of Internet - I verified this with pinging google.

So I tried "network" option in Recovery Menu - no change, still not working.

After I tried How to connect to internet from recovery mode? However I stuck on:

sudo cp /etc/resolv.conf /mnt/etc/

• cp: cannot stat 'etc/resolv.conf': No such file or directory

How to fix this?

How to enable internet in recovery console?

How to install older Kernel correctly?

How to update GRUB without screwing it?

Thanks for any advice.

I just upgraded to Ubuntu 17.04 from Ubuntu 16.04. And I have a problem to connect to network with cloned MAC address.

I changed the address in usual way (I tried ip link and ifconfig) according to standard procedure - I check name of the device, shut it down, change address, set it up, check it. The address is changed successfully (I checked that with ifconfig and ip link) and the procedure worked at Ubuntu 16. However, if I try to connect to wired network, it fail and my MAC address is set back to original one.

Again, the used procedure was working on Ubuntu 16 correctly, the problem occur now on Ubuntu 17.

I did something terrible to my SD card and I do not know how to format it.

I do not see the card with Nautilus, Gparted, nor fdisk. So I am not able to use answers from other questions I found here.

However, the output of $ ls -la /dev/sd* is

brw-rw---- 1 root disk 8,  0 bře 17 18:34 /dev/sda
brw-rw---- 1 root disk 8,  1 bře 17 18:31 /dev/sda1
brw-rw---- 1 root disk 8,  2 bře 17 18:34 /dev/sda2
brw-rw---- 1 root disk 8,  5 bře 17 18:31 /dev/sda5
brw-rw---- 1 root disk 8, 16 bře 17 18:34 /dev/sdb
brw-rw---- 1 root disk 8, 17 bře 17 18:34 /dev/sdb1
brw------- 1 root root 8, 32 bře 17 18:38 /dev/sdc

The sdc is the broken card I think - I can see sda and sdb with gparted and I know what they are.

How can I fix the card? Any idea?