I have

25019.271313] audit: type=1107 audit(1568197260.187:772): pid=1080 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_signal" bus="system" path="/org/freedesktop/NetworkManager" interface="org.freedesktop.NetworkManager" bolded textmember="DeviceAdded" name=":1.12" mask="receive" pid=18156 label="snap.telegram-desktop.telegram-desktop" peer_pid=1081 peer_label="unconfined"

details:
I am porting halium and ubports ubuntu touch to my phone oneplus x onyx
it has kernel 3.4 and i have successfully generated system image boot image and have boot into Ubuntu touch loading screen (with 4-5 dots as animation). It gets stuck there nothing happens after that .

I asked in halium telegram groups and they have mentioned it is better to askUbports .
How to solve Apparmour =denied ?
I am also adding full dmesg logs here
dmesg log
logcat
(Is anyone having any apparmor related patches for kernel 3.4 to work please share)

1. how to patch for this to work?

update1;
unity8.log link

Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
std::exception::what: could not select EGL config for use with framebuffer
  
[1971-04-04:15:32:35.724] ERROR: QMirServer - Mir failed to start

TEST_EGL_CONFIGS
output

TEST_EGL

root@ubuntu-phablet:~# test_egl
library "libgui.so" wasn't loaded and RTLD_NOLOAD prevented it
Segmentation fault  

update 2 :
So i have understood the main problem here Mir doesnt start unity8 because EGL thows exception at

select_egl_config_with_format() 

function
as given in logs
previous errors were caused by ownership as well as permission problem
update 3
sudo chown -R $USER /dev/input
$ QML_BAD_GUI_RENDER_LOOP=1 QT_QPA_PLATFORM=mirserver unity8
should start unity8 successfully once accidentally but was just flickering although i will have to fix the screen resolution.
problem seems to be 1. ownership
2.environment variables not set properly
3.Dbus errors

@doniks said in UBport new device porting problem:

@amrith said in UBport new device porting problem:

update1;
unity8.log link

Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >
std::exception::what: could not select EGL config for use with framebuffer
  
[1971-04-04:15:32:35.724] ERROR: QMirServer - Mir failed to start

Is this now still your latest status? I'm a bit lost between the verious posts and updates. I don't know this error.

Are you aware that ubports has their own telegram group focused on porting? Maybe try there.

found this issue https://github.com/ubports/ubuntu-touch/issues/494

@doniks said in Porting Halium to Nexus 7 deb:

Gave it another spin.

The general steps to get deb working are much simplified since it's all in github now: https://github.com/Halium/halium-devices/blob/halium-7.1/manifests/asus_deb.xml - just follow the halium documentation. However, I'm wondering whether I should leave the OP as is, some people have expressed that it helped them in their ports to see the journey ...

Plasma mobile hasn't been sleeping. I can tell that the newer images work much better than previously.

For ubports, I made another attempt, but no GUI so far. Any tipps appreciated!

What I did in detail:

• Follow the steps on https://docs.ubports.com/en/latest/porting/introduction.html
• in rootstock-touch-install
  • insert the line do_shell "rm -f /data/system.img" as the first line in prepare_ubuntu_system, otherwise we have that thing left over from halium
  • insert the line IMAGE_SIZE=$(( $IMAGE_SIZE * 2 ))right after that variable is set, otherwise the image is too small, so I just double it
  • delete the line do_shell "ln /data/ubuntu.img /data/system.img", otherwise I end up with an empty system.img on the device ... Not sure what the problem was exactly, I think something goes wrong with the loop devices stepping on each others toes .. not sure
• now I can install using the latest ubports xenial root fs: build 298 form https://ci.ubports.com/job/xenial-rootfs-armhf/
• at first that wouldn't boot, so ...
• I make ubports boot a bit more verbose halium/ubports-boot
  • append quite=n debug=y to the UBPORTS_BOOTIMG_COMMANDLINE in Android.mk
  • insert [ -f /dev/kmsg ] || mknod -m 600 /dev/kmsg c 1 11 in initramfs/init right before the mkdir -p /var/lock line
  • change the line in initramfs/scripts/functions : _log_msg() from printf "$@" to printf "$@" | tee /dev/kmsg
  • now I could sprinkle around log_warning_msg blabla in initramfs/init and see everything nicely in last_kmsg.
  • eventually I found that it panics at the line: mount -n -o move /proc ${rootmnt}/proc ... I have simply commented this line for the moment, that avoids the panic and
• now it boots into the ubports rootfs
• however, no GUI comes up
• in /var/log/lightdm/lightdm.log I see

Launching process 2998: /usr/share/ubuntu-touch-session/usc-wrapper --file '/run/mir_socket' --from-dm-fd 11 --to-dm-fd 14 --vt 1
[...]
DisplayServer: Unity system compositor stopped

• usc-wrapper is a script. when I run the command inside: unity-system-compositor --disable-overlays=false --spinner=$SNAP/usr/bin/unity-system-compositor-spinner --file '/run/mir_socket' --from-dm-fd 11 --to-dm-fd 14 --vt 1
• I get a Segmentation fault (core dumped)
• when I run at the same time /system/bin/logcat | grep -Eve "NetlinkListener|rmt_storage" I don't see anything logged at the time of the segfault

logcat: http://paste.ubuntu.com/p/kz7JSTfgTR/
syslog: http://paste.ubuntu.com/p/JVQJ2mg98G/
dmesg: http://paste.ubuntu.com/p/MPvwKtYhsS/

Not sure what to do next. Maybe try halium-boot, maybe check the

lxc-checkconfig: http://paste.ubuntu.com/p/5Z6w8Kwcm6/

it still flags some things. Also, mabye related, I get

# lxc-attach -n android
lxc-attach: cgroups/cgfs.c: lxc_cgroupfs_attach: 2538 could not move attached process 10995 to cgroup of container
lxc-attach: attach.c: lxc_attach: 992 Expected to receive sequence number 0: No such file or directory.

However,

# lxc-info -n android
Name:           android
State:          RUNNING
PID:            1116
IP:             10.15.19.82
IP:             192.168.179.127

and it's all seemingly good enough for plasma mobile, so not sure.

Again, tips welcome!

this was the post i was referring you

@doniks yes and i saw your logs and i see your last update was no gui being loaded and unity-compositor stopped working. i have the exact same problem .
Do you remember what you did to solve the issue?
I did ask but no one has any answer .
can you point me to your git?

I have exactly same errors you have , unity-compositor stopped and if you run it as from the startup script you get segmentation fault
however
once you boot> login to ssh
execute

$sudo chown -R $USER /dev/input
$QML_BAD_GUI_RENDER_LOOP=1 QT_QPA_PLATFORM=mirserver unity8

while ubuntu spinner is active , you will get some flashes and you can see the unity is working in background.

@amrith maybe @vince1171 can help me

@Lakotaubp said in Porting Halium to Nexus 7 deb:

@amrith You might need to sign up/in for the link to work.

No i am already signed in . it shows 404 error

@doniks said in Porting Halium to Nexus 7 deb:

May I introduce:

the Halium Porting Error Knowledge Base

https://gist.github.com/doniks/2ac14a1bb6750165bf782f62139c8aab#file-gistfile1-txt-L61

the link is not working

@dobey its ok i got the log. MIR has problem starting i have added logs

@doniks not found

this porting journal(idk what to call this) is really helpful thank you