Anybody tried to migrate Ubuntu (in this particular case 21.10 in use) from virtual machine (powered by VirtualBox, if this concerns) to WSL? Migration within one single host.
How well could imaging source (v.m.) then restoring to target (WSL) work? Hardware layer has a good chance to differ.
Atom text editor https://atom.io is installed on Ubuntu 20.04 and used by single user. It was installed from Ubuntu classic binary package. The mission is for this machine to migrate Atom to snap app. For this all what was done so far is to install Atom snap. In next step migration should be completed. The goal is to retain UX - complete local and user-specific configuration.
However if to start Atom snap by executing snap run atom the running instance has access to all packages installed to Atom classic installation and few others (recent oopen projects, recent open files lists). Means Atom snap uses yet gets visible local and user-specific configuration generated once by Atom classic package. This way it is hard to see how to conduct migration steps.
How to migrate installed Firefox (installed once from classic package) to snap. Latter one still not installed. Aimed goal: To have Firefox in snap app as well as unchanged user experience in Firefox after this migration is completed. Will it suffice to understand Firefox generic user data usage/local configuration as well as how snaps are working in general? In other words: Any specifics regarding Firefox machin-local/user configuration when Firefox is installed in snap (except snap framework specifics)?
usu@U02:~$ sudo aa-complain /var/lib/snapd/apparmor/profiles/snap.brave.brave
Profile for /var/lib/snapd/apparmor/profiles/snap.brave.brave not found, skipping
usu@U02:~$
usu@U02:~$ sudo aa-complain /var/lib/snapd/apparmor/profiles/snap-update-ns.brave
Profile for /var/lib/snapd/apparmor/profiles/snap-update-ns.brave not found, skipping
usu@U02:~$
however
usu@U02:~$ ls -alh /var/lib/snapd/apparmor/profiles/snap*brave*
-rw-r--r-- 1 root root 62K Jun 25 20:37 /var/lib/snapd/apparmor/profiles/snap.brave.brave
-rw-r--r-- 1 root root 438K Jun 25 20:37 /var/lib/snapd/apparmor/profiles/snap-update-ns.brave
usu@U02:~$
What's going on?
I am doing that because Brave browser snap app does not start. I believe I was able to start it once directly after installation completion to make some configuration. That's all. All subsequent start attempts fail. I start it from GNOME dock. Ubuntu 18.04 with latest updates installed.
`usysconf' is not present on this Ubuntu nor package manager offers to for installation, however
it is possible to start Brave from command line
usu@U02:~$ snap run brave
Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
Gkr-Message: secret service operation failed: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.103" (uid=1000 pid=3622 comm="/snap/brave/59/opt/brave.com/brave/brave " label="snap.brave.brave (enforce)") interface="org.freedesktop.DBus.Peer" member="Ping" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=1603 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined")
[3762:3762:0625/225153.096288:ERROR:sandbox_linux.cc(368)] InitializeSandbox() called with multiple threads in process gpu-process.
[3622:3755:0625/225153.305846:ERROR:rewards_service_impl.cc(185)] Failed to read file: /home/biri/snap/brave/59/.config/BraveSoftware/Brave-Browser/Default/ledger_state
[3779:3779:0625/225153.420928:ERROR:ledger_impl.cc(345)] Failed to initialize wallet
[3622:3622:0625/225154.488392:ERROR:CONSOLE(0)] "Fetch API cannot load https://pdfjs.robwu.nl/logpdfjs. Redirects to data: URL are allowed only when mode is "no-cors".", source: chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/pdfHandler.html (0)
[3622:3622:0625/225154.488465:ERROR:CONSOLE(0)] "Uncaught (in promise) TypeError: Failed to fetch", source: chrome-extension://oemmndcbldboiebfnladdacbdfmadadm/pdfHandler.html (0)
[3622:3622:0625/225541.304923:ERROR:CONSOLE(1)] "Uncaught ReferenceError: brave_new_tab is not defined", source: chrome://newtab/ (1)
[3622:3622:0625/225548.256027:ERROR:CONSOLE(1)] "Uncaught ReferenceError: brave_new_tab is not defined", source: chrome://settings/ (1)
[3622:3753:0625/225638.475561:ERROR:printer_manager_dialog_linux.cc(83)] Failed to open printer manager dialog
[3622:3992:0625/225640.690851:ERROR:printer_manager_dialog_linux.cc(83)] Failed to open printer manager dialog
[3622:3753:0625/225642.535546:ERROR:printer_manager_dialog_linux.cc(83)] Failed to open printer manager dialog
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
[3622:3622:0625/230002.943704:ERROR:CONSOLE(1247)] "Uncaught TypeError: Cannot set property 'annotationAvailable' of undefined", source: chrome://print/pdf/pdf_viewer.js (1247)
usu@U02:~$
It does not suffice to start Brave once from CL, to skip welcome tour than to start from Dock. Every attempt to start from GNOME fails. There is no extensions installed named pdfhandler or so.
Ubuntu 18.04 Desktop
GIMP snap installed (graphic images manipulation)
AppArmor in use as installed then configured by Canonical
All them in virtual machine hypervisored by VmWare
Host machine shares a folder with guest machine. Shared folder is mounted to /mnt/hm-sf/.
On system was found also:
/var/lib/snapd/apparmor/profiles/snap.gimp.gimp
The problem is GIMP snap can't open files from VB shared folder.
To fix it local modification of GIMP apparmor profile was implemented then placed to
/etc/apparmor.d/local/snap.gimp.gimp.
So /etc/apparmor.d/local/snap.gimp.gimp looks now like:
/mnt/hm-sf/**/ r,
/mnt/hm-sf/**[^/] rw,
Subsequent profile reload however fails:
$ sudo apparmor_parser -R /etc/apparmor.d/local/snap.gimp.gimp
AppArmor parser error for /etc/apparmor.d/local/snap.gimp.gimp in \
/etc/apparmor.d/local/snap.gimp.gimp at line 1: syntax error, \
unexpected TOK_MODE, expecting TOK_OPEN
How to fix it?
UPDATEI realized snap architecture features own security layer - snap permissions. Quite possibly it interconnects to AppArmor. Interestingly it provides really convenient GUI interface in Snap Store app for each installed snap app. I used it to enable access to removal media for GIMP snap - and it helps. Possibly it is built that way snap permission was last closed gate on the path to VB shared folder, all were being open. No need to dig into apparmor rules. Hopefully will find soon little time to look into GIMP rules to identify matching one.
Which is the role of Apache2 HTTP server if it concerns Ubuntu 18.04 Desktop in its original form, means as released by Canonical?
I wonder if Apache2 installed and running on 18.04 machine here is result of distro makers' decision or rather result of past package installation on my own. Currently HTTP server is not needed so if stock 18.04 does not need that, it is likely to be removed from machines here.
Any idea?
There are plenty of blogs and sources of other kinds explaining Apache2 installation. I didn't manage to find there answer to question asked here. No wonder Apache2 installation and Apache2 role in Bionic Beaver are two different problems.
Were there any changes in apparmore profile for Chriomium browser since 16.04 LTS?
Ubuntu 17.x was skipped. We ran 16.04, now B.Beaver. With transition to Beaver Chriomium stopped to be able to access VirtualBox shared folder. Ubuntu is virtual machine.
The question is also why no profile was found for Chromium at apparmore's default profiles location?
Is it possible for anyone to use list attached here (packages going to be removed by apt-get autoremove) for judgement if it safe to complete apt-get autoremove?
Question above arises as previous attempt to conduct autoremove completed in Bionic Beaver without graphical environment.
user@stationC:~$ sudo apt-get autoremove
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
breeze-icon-theme fonts-dejavu fonts-dejavu-extra gir1.2-geocodeglib-1.0
gnome-todo-common icoutils kde-runtime kde-runtime-data kde-style-breeze
kde-style-breeze-qt4 kdelibs-bin kdelibs5-data kdelibs5-plugins kdiff3-doc
kdoctools libattica0.4 libdlrestrictions1 libedataserverui-1.2-2 libgnome-todo
libgpgme++2v5 libkactivities6 libkcmutils4 libkde3support4 libkdeclarative5
libkdecore5 libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4
libkf5style5 libkfile4 libkhtml5 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4
libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkpty4
libkrosscore4 libktexteditor4 libkxmlrpcclient4 libntrack-qt4-1 libntrack0 libphonon4
libplasma3 libpolkit-qt-1-1 libqca2 libqca2-plugins libqt4-qt3support
libsolid4 libstreamanalyzer0v5 libstreams0v5 libthreadweaver4 ntrack-module-libnl-0
oxygen-icon-theme phonon phonon-backend-gstreamer
phonon-backend-gstreamer-common plasma-scriptengine-javascript
0 upgraded, 0 newly installed, 63 to remove and 8 not upgraded.
After this operation, 164 MB disk space will be freed.
Do you want to continue? [Y/n]
The goal is to preserve B. Beavers original graphical stack even if to do apt-get autoremove.
Found existing questions with matching headline are dated deep in the past so me considers them as unrelated.
One of first operations for Ubuntu machine here after upgrade to Bionic B. completed (from 16.04.x LTE) was to start sudo apt-get autoremove. Unfortunately that operation resulted in GUI typical for Beaver B. been gone, I am no GNOME nor Desktop env. expert, so hard for me to use here proper technical terms. Bionic B. looked like be free from GNOME and that stack.
Today, few weeks later, autoremove is pending again as storage space goes to limits due to numerous and frequently kernel updates. I afraid if I do it now again Bionic B. typical look&feel goes away. Attached is picture which lists items autoremove attempts to delete. Can one see here suspicious points?
ttt@comp22:~$ sudo apt-get autoremove
[sudo] password for ttt:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
breeze-icon-theme fonts-dejavu fonts-dejavu-extra gir1.2-geocodeglib-1.0 gnome-todo-common icoutils kde-runtime kde-runtime-data kde-style-breeze
kde-style-breeze-qt4 kdelibs-bin kdelibs5-data kdelibs5-plugins kdiff3-doc kdoctools libattica0.4 libdlrestrictions1 libedataserverui-1.2-2 libgnome-todo
libgpgme++2v5 libkactivities6 libkcmutils4 libkde3support4 libkdeclarative5 libkdecore5 libkdesu5 libkdeui5 libkdewebkit5 libkdnssd4 libkemoticons4
libkf5style5 libkfile4 libkhtml5 libkio5 libkjsapi4 libkjsembed4 libkmediaplayer4 libknewstuff3-4 libknotifyconfig4 libkntlm4 libkparts4 libkpty4
libkrosscore4 libktexteditor4 libkxmlrpcclient4 libntrack-qt4-1 libntrack0 libphonon4 libplasma3 libpolkit-qt-1-1 libqca2 libqca2-plugins libqt4-qt3support
libsolid4 libstreamanalyzer0v5 libstreams0v5 libthreadweaver4 ntrack-module-libnl-0 oxygen-icon-theme phonon phonon-backend-gstreamer
phonon-backend-gstreamer-common plasma-scriptengine-javascript
0 upgraded, 0 newly installed, 63 to remove and 2 not upgraded.
After this operation, 164 MB disk space will be freed.
Do you want to continue? [Y/n]
Ubuntu guest running in virtual machine powered by Oracle VirtualBox 5.2.18. Virtualbox shared folders worked pretty well here until the upgrade from 16.04 to Bionic Beaver was conducted. After upgrade the guest's Web Browser can't open V.B. shared folder (e.g. on filling the form for file upload to web site). Error message popping up on attempt to navigate to shared folder from "open file" dialog reads: .... permission denied. However leaving browser then navigating to shared folder from Nautilus manually works fine.
All instances of web browser run as current user which has no problems to view and manipulate shared folder from Nautilus. Also file ownerships, group and access mode are same in 18.04 as in 16.04 backup. The browser is Chromium, however problems were reproducible also with Firefox.
/etc/fstab does not include any line for mount of vboxsf type, also in 16.04 backup which works fine.
User, the browser is running under and that one logged locally to Beaver and testing shared folder access manually using Nautilus, is in 'vboxsf' user group. That assignment was removed by Beaver installation-by-upgrade. Mount point is /media/sf_exchange :
$ ls -alh /media
total 44K
drwxr-xr-x 12 root root 4.0K Aug 18 19:25 .
drwxr-xr-x 24 root root 4.0K Aug 16 20:38 ..
drwxrwx--- 1 root vboxsf 680 Aug 18 22:10 sf_exchange
...
Version of installed guest additions is in sync with used Virtual Box version.
What might be possible reason and possible solution?
=====================
UPDATE upon interesting hint from Mr. T
$ sudo cat /sys/kernel/security/apparmor/profiles | grep .*chrom.*
snap.chromium.chromium (enforce)
snap-update-ns.chromium (enforce)
/usr/lib/lightdm/lightdm-guest-session//chromium (enforce)
$
Following found also in system log at time stamp corresponding to navigating to shared folder from Chromium's Open File dialog:
AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" \
name="/media/sf_exchange/" pid=4288 comm="pool" requested_mask="r" \
denied_mask="r" fsuid=1000 ouid=0
$ sudo cat /var/lib/snapd/apparmor/profiles/snap.chromium.chromium | grep exchange
$ sudo cat /var/lib/snapd/apparmor/profiles/snap.chromium.chromium | grep -e '/media'
$
$ sudo find / -path *apparmor* -name *snap.chromium.chromium*
/var/lib/snapd/apparmor/profiles/snap.chromium.chromium
/var/cache/apparmor/snap.chromium.chromium
find: ‘/run/user/1000/gvfs’: Permission denied
$
so no explicit rule to forbid mount point. How to find then the blocking rule?
Same problems with Firefox as reported previously are no more reproducible.
Newly switched from 16.04 LTS to Bionic Beaver. Yet in 16.04 several smb servers were stored to Nautilus server history (or so, sorry don't know the exact terminology). Now after upgrade to B. Beaver file manager (possibly it is still Nautilus, however one source in web stresses it was GNOME's default file manager called Files) the list of servers visited in the past is empty.
How to migrate
~/.config/nautilus/servers
generated by 16.04's Nautilus to Beaver's default file manager?
According to System Monitor app Nautilus is in operation (Beaver), no app like Files is listed over there.
Following description can be found in Ubuntu Software Center (Ubuntu 16.04 LTS) for Automake package:
Automake 1.15 fails to work in a number of situations that Automake 1.4, 1.6, 1.7, 1.8, 1.9, 1.10, 1.11 and 1.14 did, so previous versions are available as separate packages.
Few questions arise from this:
Why are versions 1.12 and 1.13 not mentioned in the list?
Fact that 1.15 fails to work in a number of situation - is this a problem of Automake or integration-in-Ubuntu's one?
Description mentions previous versions are available as separate packages - where is that availability, GNU or other automake distribution servers or Ubuntu packages distribution system?
Didn't find existing question this kind. However Ubuntu Firefox only is affected.
Problem was not observed with Firefox on other systems. The router in local network offers its GUI via web interface with access under router's IP. I connect to its GUI using https. Ubuntu Firefox claims every time the connection was not secure SEC_ERROR_UNKNOW_ISSUER. This is not yet the problem I like to discuss here.
The problem is myself lets Firefox to apply exception to that URL and store this exception permanently. In end-effect exception is not permanent but volatile - I have to do it every time when connecting to router GUI There are some cases where it is not reproducible, however hard to describe conditions that exceptional observation was made under.
Is this a well-known problem? Solutions known?
