Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. QSettings sync() causes QWarning: setNativeLocks failed: Resource temporarily unavailable
Forum Updated to NodeBB v4.3 + New Features

QSettings sync() causes QWarning: setNativeLocks failed: Resource temporarily unavailable

Scheduled Pinned Locked Moved General and Desktop
linuxsetnativelockssyncsettingsqwarning
8 Posts 2 Posters 4.3k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    mmirsky
    wrote on 10 Jun 2015, 16:41 last edited by mmirsky 6 Nov 2015, 14:49
    #1

    I recently ported a Qt4 application to Qt5.4.1 (also tested Qt5.5.0 beta). I've experienced a handful of odd behavior since then. One of the issues involves QSettings sync() on Linux (mainly RHEL 6.6) . Specifically, I receive a QWarning immediately after calling sync() on my QSettings object:

    setNativeLocks failed: Resource temporarily unavailable

    The code that saves settings was not touched in the port from Qt4->Qt5, and appeared only after the upgrade. As far as I can tell, the settings seem to save despite the warning.

    I've tested this on a number of machines. The linux machines that it appears on have have a network mounted home directory. However, I've tried on virtual machines that are not network mounted, and the problem doesn't occur. This leads me to believe that it has something to do with writing the conf file over the network.

    Is there anything I can do to resolve this warning on my end? Is this a bug?

    I'd be glad to answer any more information if it will help to diagnose the problem. Thanks for your help!

    1 Reply Last reply
    0
    • S Offline
      S Offline
      SGaist
      Lifetime Qt Champion
      wrote on 10 Jun 2015, 20:46 last edited by
      #2

      Hi,

      Can you test with Qt 5.5 ?

      Interested in AI ? www.idiap.ch
      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

      1 Reply Last reply
      0
      • M Offline
        M Offline
        mmirsky
        wrote on 10 Jun 2015, 21:06 last edited by
        #3

        SGaist,

        Yeah, I can try. Downloading Qt 5.5 beta source now.

        Thanks.

        1 Reply Last reply
        0
        • M Offline
          M Offline
          mmirsky
          wrote on 11 Jun 2015, 14:42 last edited by
          #4

          Compiled and rebuilt with Qt5.5.0 (beta). Sadly, the problem persists.

          1 Reply Last reply
          0
          • S Offline
            S Offline
            SGaist
            Lifetime Qt Champion
            wrote on 11 Jun 2015, 21:32 last edited by
            #5

            Then you should check the bug report system to see if it's something known. If not, please consider opening a new report providing a minimal compilable example reproducing the behavior

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            1 Reply Last reply
            0
            • M Offline
              M Offline
              mmirsky
              wrote on 18 Jun 2015, 21:40 last edited by mmirsky
              #6

              I couldn't find a similar bug report, so I created one: QT_BUG.

              1 Reply Last reply
              0
              • S Offline
                S Offline
                SGaist
                Lifetime Qt Champion
                wrote on 18 Jun 2015, 22:24 last edited by
                #7

                Thanks for sharing

                Interested in AI ? www.idiap.ch
                Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                1 Reply Last reply
                0
                • M Offline
                  M Offline
                  mmirsky
                  wrote on 23 Jun 2015, 16:36 last edited by
                  #8

                  For future reference, the bug I logged was marked as a duplicate.

                  Here is the link to the original, QTBUG-43454.

                  1 Reply Last reply
                  0

                  • Login

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • Users
                  • Groups
                  • Search
                  • Get Qt Extensions
                  • Unsolved