Hi. Here is what I get in "userpriv" mode: gcc -DPACKAGE_NAME=\"qingy\" -DPACKAGE_TARNAME=\"qingy\" -DPACKAGE_VERSION=\"0.2.3\" -DPACKAGE_STRING=\"qingy\ 0.2.3\" -DPACKAGE_BUGREPORT=\"noberasco.gnu@disi.unige.it\" -DPACKAGE=\"qingy\" -DVERSION=\"0.2.3\" -D_GNU_SOURCE=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_FCNTL_H=1 -DHAVE_GRP_H=1 -DHAVE_LASTLOG_H=1 -DHAVE_PATHS_H=1 -DHAVE_PWD_H=1 -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_TIME_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LINUX_KD_H=1 -DHAVE_LINUX_VT_H=1 -DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_DIRENT_H=1 -DHAVE_SYS_WAIT_H=1 -DHAVE_LIBCRYPT=1 -I. -I. -march=pentium -Os -fomit-frame-pointer -pipe -W -Wall -DSHADOW_PASSWD -DUSE_PAM -DLinux -c `test -f 'creatercfile.c' || echo './'`creatercfile.c gcc -march=pentium -Os -fomit-frame-pointer -pipe -W -Wall -DSHADOW_PASSWD -DUSE_PAM -DLinux -lpam -lpam_misc -ldl -o creatercfile creatercfile.o -lcrypt ./creatercfile directfbrc.qingy /usr/bin/fbset open /dev/fb0: Permission denied make[1]: *** [directfbrc.qingy] Error 1 make[1]: Leaving directory `/var/tmp/portage/qingy-0.2.3/work/qingy-0.2.3/media' make: *** [all-recursive] Error 1 /dev/fb0 is a symlink to /dev/fb/0, which seems to be owned by my user: crw------- 1 thomas root 29, 0 jan 20 11:13 /dev/fb/0 So I'm not sure wether this is a wrong (too restrictive) configuration on my side, or if it is the qingy build process that should be changed so that it doesn't try to open this device. Any opinion? It builds fine if I remove the "userpriv" feature (sandbox is not a problem). Reproducible: Always Steps to Reproduce:
In userpriv mode things run as user portage. In any case I don't think that any compilation routine has any business with a framebuffer device.
In fact it use "fbset" at compile time to create a directfb config file. In bug #37740 (where an ebuild for 0.3.0 was submitted), I've proposed a solution to move this task to the pkg_config() function. I think it can easily be backported to this version, tell me if you are interrested.
I would close this bug as WONTFIX, because: - qingy 0.2.3 is an old version (0.3.0 is much better anyway) - qingy 0.3.0 ebuild in portage does not have the solution proposed in BUG #37740, which is imho a messy one anyway - I'm about to release version 0.4.0 which solves upstream all the issues presented in #37740: - /etc will contain only configuration files, - themes will go to /usr/share/qingy, - screen savers to /usr/lib/qingy/screensavers - most important make no longer wants to run 'fbset' as I was able to write some code to get framebuffer resolution without resorting to external utilities Plus of course it offers a number of other fixes and enhancements.
> I'm about to release version 0.4.0 which solves upstream all > the issues presented in #37740 Great :)
