UBport new device porting problem

doniks

disable with kernel param apparmor=0

properly fix with patching see here https://pad.ubports.com/p/porting-faq

amrith

@doniks yes that disabled apparmor but still no luck

dobey

@amrith said in UBport new device porting problem:

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" member="DeviceAdded" name=":1.12" mask="receive" pid=18156 label="snap.telegram-desktop.telegram-desktop" peer_pid=1081 peer_label="unconfined"

This is surely from your PC. Snaps cannot be used on UT.

@amrith said in UBport new device porting problem:

I asked in halium telegram groups and they have mentioned it is better to askUbports .

Check the /home/phablet/.cache/upstart/unity8.log I think. Does this occasionally flash away and then back to the animation? Also maybe check /var/log/syslog.

amrith

@dobey sorry i should have guessed when i saw telegram in the log. but anyway i have disabled apparmor

No it just stays in the ubuntu loading screen , the animation is alive(not getting stuck or frozen).
Is there a way to see console messages instead of ubuntu loading screen?

yes i will check those logs too

doniks

@doniks said in UBport new device porting problem:

see here https://pad.ubports.com/p/porting-faq

check the /run/user/32011 fix from the pad

amrith

@doniks checked it just now file already exits

amrith

@dobey /home/phablet/.cache/unity8.log dives error: file does not exist

Stefano

@amrith Contact this guy https://github.com/Vince1171

Find him on Telegram @Vince or here @vince1171

He is porting for Op2, Op3/t, Op5 , so he might be able to help as he said those devices has similar issues.

doniks

@amrith said in UBport new device porting problem:

@dobey /home/phablet/.cache/unity8.log dives error: file does not exist

I think it's in ~/.cache/upstart/

doniks

@amrith said in UBport new device porting problem:

@doniks checked it just now file already exits

Correct owner and permission? Maybe the dbus fix right below it? Otherwise the unity logs as per docs

doniks

@amrith said in UBport new device porting problem:

Is there a way to see console messages instead of ubuntu loading screen?

Search for syslog in the pad

dobey

@doniks said in UBport new device porting problem:

I think it's in ~/.cache/upstart/

Oops, yes it is. sorry.

amrith

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

amrith

@amrith maybe @vince1171 can help me

doniks

@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.

amrith

@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?

amrith

@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

poVoq

Did anyone ever look into an OnePlus X (onyx) port again?
I found this which points to a possibly working port:
https://forum.xda-developers.com/oneplus-x/general/rom-ubuntu-touch-oneplusx-t4048635
https://github.com/ubports-onyx/ubports-ci