Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

File Capabilities?



  • I get this error and don't know how to do what it's asking me.

    @Starting remote process.
    W/dalvikvm( 1162): PR_CAPBSET_DROP 0 failed: Invalid argument. Please make sure your kernel is compiled with file capabilities support enabled.
    W/dalvikvm( 1162): PR_CAPBSET_DROP 1 failed: Invalid argument. Please make sure your kernel is compiled with file capabilities support enabled.
    @

    This is an android app created using Necessitas.
    Windows 8, Qt 4.8 , Qt Creator 3.0


  • Moderators

    Hi,

    The Qt 4.8 port for Android is old, incomplete and unsupported. I recommend using Qt 5.2.1 (or even Qt 5.3) instead.



  • I've been told that before but it's to hard for me to deal with at the moment. I know this code should work, it's a group's open source.


  • Moderators

    I see. I've never seen this error before, I'm afraid. I suggest waiting for someone else with experience to answer your question.

    If you don't get any answers after a few days, subscribe and post to the "Interest mailing list":http://lists.qt-project.org/mailman/listinfo/interest -- Qt engineers who work with low-level details are active there.



  • Well I took your advice and ported the application to Qt 5.2.1 but I still get same error.

    @Starting remote process.
    W/dalvikvm( 1054): PR_CAPBSET_DROP 0 failed: Invalid argument. Please make sure your kernel is compiled with file capabilities support enabled.
    W/dalvikvm( 1054): PR_CAPBSET_DROP 1 failed: Invalid argument. Please make sure your kernel is compiled with file capabilities support enabled.
    W/dalvikvm( 1054): PR_CAPBSET_DROP 2 failed: Invalid argument. Please make sure your kernel is compiled with file capabilities support enabled.@


  • Moderators

    Does your app run? This post suggests that it's a harmless warning message: http://androidforum.tytung.com/news-for-pr-capbset-drop-0-failed-invalid-argument-t133.html



  • Yea, the app runs for the most part. I am just trying to get to the underlying problem by troubleshooting each error one at a time. I suppose i could let this one go for now and move on...


Log in to reply