QFileSystemWatcher: failed to add paths: /root/.config/ibus/busīus::open: Can not get ibus-daemon's address. QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory Qt: Session management error: None of the authentication protocols specified are supported This is a workaround though and in the long run live-usb-creator should really be split in a front-end and a back-end, with the front-end not running as root. So this can be worked around by making live-usb-creator to the same from code, and / or modifying the launcher. Note that there is a workaround for qt4 described in bug 1185893:
Note I've also discussed this with the some qt people and it is fixed in qt5, and currently there are no plans to fix this for qt4, there answer to this problem is: Do not run gui apps as root. I realize this is sometimes easiest, but we should not ship anything setup this way ootb and/or depending on this (running as root). So I'm re-opening this.Īlso gui apps should really not run as root, ever. I then tried to start Spyder and basically saw the same behaviour: a lot of those errors reported above, and the Spyder window just popped up blank. This actually is a feature because people are now getting proper protection of unauthorized accesses to their shared memory segments where before anyone could access them (as the X-server was doing the accessing and it ran as root). X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (XCopyArea) And the created graph window was just blank. As explained in bug 1185893 this has been discussed on the xorg-devel list and we do not consider this an Xorg bug, the problem is lack of proper error checking of the MIT SHM extension related X calls in the app / toolkit.
0 kommentar(er)
