[hafqa] [hafqa] [Bug 794] New: sapwood doesn't start for privsep applications
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Tue Oct 3 18:24:55 EEST 2006
- Previous message: [hafqa] [Bug 792] New: no way to debug hildon-home applets
- Next message: [hafqa] [Bug 792] no way to debug hildon-home applets
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://maemo.org/bugzilla/show_bug.cgi?id=794 Summary: sapwood doesn't start for privsep applications Product: haf Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sapwood AssignedTo: tommi.komulainen at nokia.com ReportedBy: mike at w4g.org QAContact: hafqa at maemo.org I have an application that priviledge seperates itself. It starts setuid root, spawns a uid0 daemon, drops all priviledges back to that of "user" and then initializes gtk, osso, glib etc. All priviledged operations occur in the daemon after the unpriviledged UI sends a request over a shared socket. If I run the UI as root it works fine. If I clear the setuid bit on the file and run it from the user then the UI works fine (of course the application is then useless). But if I run the setuid file from the user's context I get this sapwood error: `/usr/lib/sapwood/sapwood-server' MUST be started before applications ipsec-auth[1446]: GLIB WARNING ** default - sapwood-theme: Failed to load pixmap file /usr/share/themes/theme3/gtk-2.0/../images/qgn_plat_single_line_input.png: Failed to connect to sapwood server using `/tmp/sapwood-:0.0': Connection refused -- Configure bugmail: https://maemo.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
- Previous message: [hafqa] [Bug 792] New: no way to debug hildon-home applets
- Next message: [hafqa] [Bug 792] no way to debug hildon-home applets
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]