Re: F17: DirectFB
Trying to run directfb on F17 I noticed 5 issues: 1) libdirectfb_vdpau.so: undefined symbol: XUnlockDisplay (Bug 852740: fixed) 2) Unable to run DirectFB as a normal user (Bug 852745: open) 3) permissions on /dev/tty* and /dev/fb* not set by udev (probably should be addressed and fixed under Bug 852745) 4) inteldrmfb driver emulation of fbdev interface incomplete (Bug 853268: open) 5) directfb needs updated to 1.6.1 (no bug yet) I tested the fix in Bug 852740 and that bug is fixed in 1.5.3-8 in F17 although the other errors still keep directfb from working. Is there anything else I can do to help test and get directfb upgraded to 1.6.1 and working for both regular and root users? Gerry -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/29/2012 06:52 PM, Gerry Reno wrote: (!) DirectFB/core/vt: Error opening `/dev/tty1'! -- Permission denied (!) DirectFB/Core: Could not initialize 'system_core' core! -- A general initialization error occured (#) DirectFBError [DirectFBCreate() failed]: A general initialization error occured Segmentation fault I set the perms in the udev rules to 0666 but the tty does not setup that way for some reason. Did you reboot after setting the udev rules? My /dev/tty0 and /dev/tty1 are 0660. (I'm running Fedora 18). If you chmod 660 /dev/tty*, does it work? ~tom == Fedora Project -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/30/2012 09:00 AM, Tom Callaway wrote:
On 08/29/2012 06:52 PM, Gerry Reno wrote:
(!) DirectFB/core/vt: Error opening `/dev/tty1'!
-- Permission denied
(!) DirectFB/Core: Could not initialize 'system_core' core!
-- A general initialization error occured
(#) DirectFBError [DirectFBCreate() failed]: A general initialization
error occured
Segmentation fault
I set the perms in the udev rules to 0666 but the tty does not setup
that way for some reason.
Did you reboot after setting the udev rules? My /dev/tty0 and /dev/tty1
are 0660. (I'm running Fedora 18).
If you chmod 660 /dev/tty*, does it work?
~tom
==
Fedora Project
Yes, these settings have been through many reboots and they are not setting the
tty mode correctly.
When I chmod g+r tty{0,1} the permission error goes away but it has other
problems with setting 1024x768 for fbdev.
$ dfbinfo
~~| DirectFB 1.6.1 |~~
(c) 2001-2012 The world wide DirectFB Open Source Community
(c) 2000-2004 Convergence (integrated media) GmbH
(*) DirectFB/Core: Single Application Core. (2012-08-29 21:15)
(*) Direct/Memcpy: Using libc memcpy()
(*) Direct/Thread: Started 'Fusion Dispatch' (-1) [MESSAGING OTHER/OTHER
0/0] 8388608...
(*) Direct/Thread: Started 'VT Switcher' (-1) [CRITICAL OTHER/OTHER 0/0]
8388608...
(*) Direct/Thread: Started 'VT Flusher' (-1) [DEFAULT OTHER/OTHER 0/0]
8388608...
(*) DirectFB/FBDev: Found 'inteldrmfb' (ID 0) with frame buffer at
0xc0064000, 8100k (MMIO 0x, 0k)
(*) Direct/Thread: Started 'Hotplug with Linux Input' (-1) [INPUT
OTHER/OTHER 0/0] 8388608...
(*) DirectFB/Input: Hot-plug detection enabled with Linux Input Driver
(*) DirectFB/Input: Hot-plug detection enabled with Input Hub Driver
(*) Direct/Thread: Started 'Keyboard Input' (-1) [INPUT OTHER/OTHER 0/0]
8388608...
(*) DirectFB/Input: Keyboard 0.9 (directfb.org)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/Graphics: MMX Software Rasterizer 0.7 (directfb.org)
(*) DirectFB/Core/WM: Default 0.3 (directfb.org)
(!!!) *** ONCE [no mode found for 1024x768] *** [fbdev.c:1354 in
dfb_fbdev_find_mode()]
(*) FBDev/Mode: Setting 1024x768 RGB32
(*) FBDev/Mode: Switched to 1024x768 (virtual 1024x768) at 32 bit (RGB32),
pitch 7680
(!) DirectFB/FBDev: Could not set gamma ramp-- Invalid argument
(*) FBDev/Mode: Setting 1024x768 RGB16
(*) FBDev/Mode: Switched to 1024x768 (virtual 1024x768) at 16 bit (RGB16),
pitch 7680
(!) DirectFB/FBDev: Could not set gamma ramp-- Invalid argument
Screen (00) FBDev Primary Screen(primary screen)
Caps: VSYNC POWER_MANAGEMENT
Layer (00) FBDev Primary Layer (primary layer)
Type:GRAPHICS
Caps:SURFACE BRIGHTNESS CONTRAST SATURATION
Input (00) Keyboard(primary keyboard)
Vendor ID: 0x
Product ID: 0x
Type: KEYBOARD
Caps: KEYS
Min. Keycode: 0
Max. Keycode: 127
Gerry
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
If I run the command under root I see a more extensive output but having same problems w/1024x768: # dfbinfo ~~| DirectFB 1.6.1 |~~ (c) 2001-2012 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Single Application Core. (2012-08-29 21:15) (*) Direct/Memcpy: Using libc memcpy() (*) Direct/Thread: Started 'Fusion Dispatch' (-1) [MESSAGING OTHER/OTHER 0/0] 8388608... (*) Direct/Thread: Started 'VT Switcher' (-1) [CRITICAL OTHER/OTHER 0/0] 8388608... (*) Direct/Thread: Started 'VT Flusher' (-1) [DEFAULT OTHER/OTHER 0/0] 8388608... (*) DirectFB/FBDev: Found 'inteldrmfb' (ID 0) with frame buffer at 0xc0064000, 8100k (MMIO 0x, 0k) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: Power Button (1) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: AT Translated Set 2 keyboard (2) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: Hewlett-Packard HP f2100a Opti (3) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: SynPS/2 Synaptics TouchPad (4) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: Video Bus (5) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: Logitech Logitech Illuminated K (6) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: Logitech Logitech Illuminated K (7) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: Video Bus (8) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: ST LIS3LV02DL Accelerometer (9) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: HP Truevision HD (10) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: HP WMI hotkeys (11) 0.1 (directfb.org) (*) Direct/Thread: Started 'Hotplug with Linux Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: Hot-plug detection enabled with Linux Input Driver (*) DirectFB/Input: Hot-plug detection enabled with Input Hub Driver (*) Direct/Thread: Started 'Keyboard Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: Keyboard 0.9 (directfb.org) (*) Direct/Thread: Started 'PS/2 Input' (-1) [INPUT OTHER/OTHER 0/0] 8388608... (*) DirectFB/Input: IMPS/2 Mouse 1.0 (directfb.org) (*) DirectFB/Genefx: MMX detected and enabled (*) DirectFB/Graphics: MMX Software Rasterizer 0.7 (directfb.org) (*) DirectFB/Core/WM: Default 0.3 (directfb.org) (!!!) *** ONCE [no mode found for 1024x768] *** [fbdev.c:1354 in dfb_fbdev_find_mode()] (*) FBDev/Mode: Setting 1024x768 RGB32 (*) FBDev/Mode: Switched to 1024x768 (virtual 1024x768) at 32 bit (RGB32), pitch 7680 (!) DirectFB/FBDev: Could not set gamma ramp-- Invalid argument (*) FBDev/Mode: Setting 1024x768 RGB16 (*) FBDev/Mode: Switched to 1024x768 (virtual 1024x768) at 16 bit (RGB16), pitch 7680 (!) DirectFB/FBDev: Could not set gamma ramp-- Invalid argument Screen (00) FBDev Primary Screen(primary screen) Caps: VSYNC POWER_MANAGEMENT Layer (00) FBDev Primary Layer (primary layer) Type:GRAPHICS Caps:SURFACE BRIGHTNESS CONTRAST SATURATION Input (10) Power Button Vendor ID: 0x Product ID: 0x0001 Type: Caps: KEYS Min. Keycode: -1 Max. Keycode: -1 Input (00) AT Translated Set 2 keyboard(primary keyboard) Vendor ID: 0x0001 Product ID: 0x0001 Type: KEYBOARD REMOTE Caps: KEYS Min. Keycode: 0 Max. Keycode: 127 Input (01) Hewlett-Packard HP f2100a Opti (primary mouse) Vendor ID: 0x03f0 Product ID: 0x2003 Type: MOUSE Caps: KEYS AXES BUTTONS Min. Keycode: -1 Max. Keycode: -1 Max. Axis: 2 Max. Button: 2 Input (11) SynPS/2 Synaptics TouchPad Vendor ID: 0x0002 Product ID: 0x0007 Type: MOUSE Caps: KEYS AXES BUTTONS Min. Keycode: -1 Max. Keycode: -1 Max. Axis: 1 Max. Button: 1 Input (12) Video Bus
Re: F17: DirectFB
On 08/30/2012 09:26 AM, Gerry Reno wrote: If I run the command under root I see a more extensive output but having same problems w/1024x768: (*) DirectFB/Core/WM: Default 0.3 (directfb.org) (!!!) *** ONCE [no mode found for 1024x768] *** [fbdev.c:1354 in dfb_fbdev_find_mode()] Gerry, what's the video card in that computer, and are you using an out-of-Fedora driver? ~tom == Fedora Project -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
After manually setting tty0 and tty1 using the previous chmod command now when I reboot I get a strange mix of tty settings. Originally they would all have permissions like this: crw--w. 1 root tty 4, 10 Aug 30 2012 /dev/tty10 But now they are a mix of settings: # ls -l /dev/tty* crw-rw-rw-. 1 root tty 5, 0 Aug 30 2012 /dev/tty crw-rw. 1 root tty 4, 0 Aug 30 2012 /dev/tty0 crw-rw. 1 root tty 4, 1 Aug 30 2012 /dev/tty1 crw--w. 1 root tty 4, 10 Aug 30 2012 /dev/tty10 crw--w. 1 root tty 4, 11 Aug 30 2012 /dev/tty11 crw--w. 1 root tty 4, 12 Aug 30 2012 /dev/tty12 crw--w. 1 root tty 4, 13 Aug 30 2012 /dev/tty13 crw--w. 1 root tty 4, 14 Aug 30 2012 /dev/tty14 crw--w. 1 root tty 4, 15 Aug 30 2012 /dev/tty15 crw--w. 1 root tty 4, 16 Aug 30 2012 /dev/tty16 crw--w. 1 root tty 4, 17 Aug 30 2012 /dev/tty17 crw--w. 1 root tty 4, 18 Aug 30 2012 /dev/tty18 crw--w. 1 root tty 4, 19 Aug 30 2012 /dev/tty19 crw-rw. 1 root tty 4, 2 Aug 30 2012 /dev/tty2 crw--w. 1 root tty 4, 20 Aug 30 2012 /dev/tty20 crw--w. 1 root tty 4, 21 Aug 30 2012 /dev/tty21 crw--w. 1 root tty 4, 22 Aug 30 2012 /dev/tty22 crw--w. 1 root tty 4, 23 Aug 30 2012 /dev/tty23 crw--w. 1 root tty 4, 24 Aug 30 2012 /dev/tty24 crw--w. 1 root tty 4, 25 Aug 30 2012 /dev/tty25 crw--w. 1 root tty 4, 26 Aug 30 2012 /dev/tty26 crw--w. 1 root tty 4, 27 Aug 30 2012 /dev/tty27 crw--w. 1 root tty 4, 28 Aug 30 2012 /dev/tty28 crw--w. 1 root tty 4, 29 Aug 30 2012 /dev/tty29 crw-rw. 1 root tty 4, 3 Aug 30 2012 /dev/tty3 crw--w. 1 root tty 4, 30 Aug 30 2012 /dev/tty30 crw--w. 1 root tty 4, 31 Aug 30 2012 /dev/tty31 crw--w. 1 root tty 4, 32 Aug 30 2012 /dev/tty32 crw--w. 1 root tty 4, 33 Aug 30 2012 /dev/tty33 crw--w. 1 root tty 4, 34 Aug 30 2012 /dev/tty34 crw--w. 1 root tty 4, 35 Aug 30 2012 /dev/tty35 crw--w. 1 root tty 4, 36 Aug 30 2012 /dev/tty36 crw--w. 1 root tty 4, 37 Aug 30 2012 /dev/tty37 crw--w. 1 root tty 4, 38 Aug 30 2012 /dev/tty38 crw--w. 1 root tty 4, 39 Aug 30 2012 /dev/tty39 crw-rw. 1 root tty 4, 4 Aug 30 2012 /dev/tty4 crw--w. 1 root tty 4, 40 Aug 30 2012 /dev/tty40 crw--w. 1 root tty 4, 41 Aug 30 2012 /dev/tty41 crw--w. 1 root tty 4, 42 Aug 30 2012 /dev/tty42 crw--w. 1 root tty 4, 43 Aug 30 2012 /dev/tty43 crw--w. 1 root tty 4, 44 Aug 30 2012 /dev/tty44 crw--w. 1 root tty 4, 45 Aug 30 2012 /dev/tty45 crw--w. 1 root tty 4, 46 Aug 30 2012 /dev/tty46 crw--w. 1 root tty 4, 47 Aug 30 2012 /dev/tty47 crw--w. 1 root tty 4, 48 Aug 30 2012 /dev/tty48 crw--w. 1 root tty 4, 49 Aug 30 2012 /dev/tty49 crw-rw. 1 root tty 4, 5 Aug 30 2012 /dev/tty5 crw--w. 1 root tty 4, 50 Aug 30 2012 /dev/tty50 crw--w. 1 root tty 4, 51 Aug 30 2012 /dev/tty51 crw--w. 1 root tty 4, 52 Aug 30 2012 /dev/tty52 crw--w. 1 root tty 4, 53 Aug 30 2012 /dev/tty53 crw--w. 1 root tty 4, 54 Aug 30 2012 /dev/tty54 crw--w. 1 root tty 4, 55 Aug 30 2012 /dev/tty55 crw--w. 1 root tty 4, 56 Aug 30 2012 /dev/tty56 crw--w. 1 root tty 4, 57 Aug 30 2012 /dev/tty57 crw--w. 1 root tty 4, 58 Aug 30 2012 /dev/tty58 crw--w. 1 root tty 4, 59 Aug 30 2012 /dev/tty59 crw-rw. 1 root tty 4, 6 Aug 30 2012 /dev/tty6 crw--w. 1 root tty 4, 60 Aug 30 2012 /dev/tty60 crw--w. 1 root tty 4, 61 Aug 30 2012 /dev/tty61 crw--w. 1 root tty 4, 62 Aug 30 2012 /dev/tty62 crw--w. 1 root tty 4, 63 Aug 30 2012 /dev/tty63 crw-rw. 1 root tty 4, 7 Aug 30 2012 /dev/tty7 crw-rw. 1 root tty 4, 8 Aug 30 2012 /dev/tty8 crw-rw. 1 root tty 4, 9 Aug 30 2012 /dev/tty9 crw-rw. 1 root dialout 166, 0 Aug 30 2012 /dev/ttyACM0 crw-rw. 1 root dialout 4, 64 Aug 30 2012 /dev/ttyS0 crw-rw. 1 root dialout 4, 65 Aug 30 2012 /dev/ttyS1 crw-rw. 1 root dialout 4, 66 Aug 30 2012 /dev/ttyS2 crw-rw. 1 root dialout 4, 67 Aug 30 2012 /dev/ttyS3 Gerry -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/30/2012 09:40 AM, Tom Callaway wrote: On 08/30/2012 09:26 AM, Gerry Reno wrote: If I run the command under root I see a more extensive output but having same problems w/1024x768: (*) DirectFB/Core/WM: Default 0.3 (directfb.org) (!!!) *** ONCE [no mode found for 1024x768] *** [fbdev.c:1354 in dfb_fbdev_find_mode()] Gerry, what's the video card in that computer, and are you using an out-of-Fedora driver? ~tom == Fedora Project My laptop has one of the new Intel i7 Ivy Bridge CPU w/iGPU (Intel HD4000) plus Nvidia Geforce GT 650M Gerry -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/30/2012 09:47 AM, Gerry Reno wrote: On 08/30/2012 09:40 AM, Tom Callaway wrote: On 08/30/2012 09:26 AM, Gerry Reno wrote: If I run the command under root I see a more extensive output but having same problems w/1024x768: (*) DirectFB/Core/WM: Default 0.3 (directfb.org) (!!!) *** ONCE [no mode found for 1024x768] *** [fbdev.c:1354 in dfb_fbdev_find_mode()] Gerry, what's the video card in that computer, and are you using an out-of-Fedora driver? ~tom == Fedora Project My laptop has one of the new Intel i7 Ivy Bridge CPU w/iGPU (Intel HD4000) plus Nvidia Geforce GT 650M I did not install any third-party driver. Just installed and ran F17 as-is out of the box. Gerry -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 8/30/12 9:26 AM, Gerry Reno wrote: (*) DirectFB/FBDev: Found 'inteldrmfb' (ID 0) with frame buffer at 0xc0064000, 8100k (MMIO 0x, 0k) So this says you're using the intel drm driver... (*) DirectFB/Core/WM: Default 0.3 (directfb.org) (!!!) *** ONCE [no mode found for 1024x768] *** [fbdev.c:1354 in dfb_fbdev_find_mode()] (*) FBDev/Mode: Setting 1024x768 RGB32 (*) FBDev/Mode: Switched to 1024x768 (virtual 1024x768) at 32 bit (RGB32), pitch 7680 (!) DirectFB/FBDev: Could not set gamma ramp-- Invalid argument (*) FBDev/Mode: Setting 1024x768 RGB16 (*) FBDev/Mode: Switched to 1024x768 (virtual 1024x768) at 16 bit (RGB16), pitch 7680 (!) DirectFB/FBDev: Could not set gamma ramp-- Invalid argument ... and this I believe is saying that drm's emulation of an fbdev interface is rather incomplete. Which I believe means either directfb needs to be taught about KMS, or KMS's fbdev emulation needs to be better, or both. - ajax -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/30/2012 11:16 AM, Adam Jackson wrote: On 8/30/12 9:26 AM, Gerry Reno wrote: (*) DirectFB/FBDev: Found 'inteldrmfb' (ID 0) with frame buffer at 0xc0064000, 8100k (MMIO 0x, 0k) So this says you're using the intel drm driver... (*) DirectFB/Core/WM: Default 0.3 (directfb.org) (!!!) *** ONCE [no mode found for 1024x768] *** [fbdev.c:1354 in dfb_fbdev_find_mode()] (*) FBDev/Mode: Setting 1024x768 RGB32 (*) FBDev/Mode: Switched to 1024x768 (virtual 1024x768) at 32 bit (RGB32), pitch 7680 (!) DirectFB/FBDev: Could not set gamma ramp-- Invalid argument (*) FBDev/Mode: Setting 1024x768 RGB16 (*) FBDev/Mode: Switched to 1024x768 (virtual 1024x768) at 16 bit (RGB16), pitch 7680 (!) DirectFB/FBDev: Could not set gamma ramp-- Invalid argument ... and this I believe is saying that drm's emulation of an fbdev interface is rather incomplete. Which I believe means either directfb needs to be taught about KMS, or KMS's fbdev emulation needs to be better, or both. - ajax Opened bug: https://bugzilla.redhat.com/show_bug.cgi?id=853268 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/28/2012 11:57 AM, Gerry Reno wrote: On 08/27/2012 10:59 PM, Ilyes Gouta wrote: Hi Gerry, Try contacting the main dev. mailing-list of DirectFB. I'm sure you'll get an answer there. Btw, DirectFB-1.5.3 is rather old, DirectFB-1.6.1 is rather the latest stable release. -Ilyes Thanks Ilyes. I'll try posting over on the directfb dev list. Gerry DirectFB says that there are Fedora packaging errors which are causing the undefined symbol on XUnlockDisplay and inability to run as normal user. Opened bugs: https://bugzilla.redhat.com/show_bug.cgi?id=852740 https://bugzilla.redhat.com/show_bug.cgi?id=852745 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/29/2012 09:25 AM, Gerry Reno wrote: DirectFB says that there are Fedora packaging errors which are causing the undefined symbol on XUnlockDisplay and inability to run as normal user. Upstream is wrong, btw. The dlopen problem is caused by the fact that they don't pass the $(X11VDPAU_LIBS) to the LDFLAGS for linking libdirectfb_vdpau.la. The core issue behind why dfbinfo doesn't run as a normal user is due to the fact that the Linux kernel requires CAP_SYS_TTY_CONFIG to do any TTY ioctl() calls. UID 0 (root) has that, but normal users do not. It is possible to give a binary that capability using the setcap command. The missing udev rules also factor into this, I suspect. Last but not least, I believe a normal user needs to be in at least the tty and video groups. (and they need to be active, as reported by `groups`). Since there is no real way to handle this in the package, it just needs to be done by any user who wants to use dfbinfo: usermod -a -G tty video USERNAME I made an updated package (1.6.1) that has these fixes applied and sets the CAP_SYS_TTY_CONFIG capability to the dfbinfo binary. (Other DirectFB binaries probably need the same magic, but as I am not a DirectFB user, I can't really say which ones.) Please note that I could only get the dfbinfo results as an unprivileged user from the console (not from within X), and those results are not identical to what I get when I run it as root. When I tried to run it from X, my X session crashed and the kernel panicked. Good times. :) Anyways, Gerry, please test and let me know if these packages work for you, and once I hear back, I'll push out updates. http://koji.fedoraproject.org/koji/taskinfo?taskID=4435408 ~tom == Fedora Project -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On Wed, Aug 29, 2012 at 8:33 PM, Tom Callaway tcall...@redhat.com wrote: The core issue behind why dfbinfo doesn't run as a normal user is due to the fact that the Linux kernel requires CAP_SYS_TTY_CONFIG to do any TTY ioctl() calls. UID 0 (root) has that, but normal users do not. It is possible to give a binary that capability using the setcap command. The missing udev rules also factor into this, I suspect. Last but not least, I believe a normal user needs to be in at least the tty and video groups. (and they need to be active, as reported by `groups`). Since there is no real way to handle this in the package, it just needs to be done by any user who wants to use dfbinfo: usermod -a -G tty video USERNAME I made an updated package (1.6.1) that has these fixes applied and sets the CAP_SYS_TTY_CONFIG capability to the dfbinfo binary. (Other DirectFB binaries probably need the same magic, but as I am not a DirectFB user, I can't really say which ones.) Per http://forums.grsecurity.net/viewtopic.php?f=7t=2522 , giving the program CAP_SYS_TTY_CONFIG is basically equivalent to making it setuid-root. Was the code designed to be run in such a risky setup? Mirek -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 8/29/12 3:06 PM, Miloslav Trmač wrote: On Wed, Aug 29, 2012 at 8:33 PM, Tom Callaway tcall...@redhat.com wrote: I made an updated package (1.6.1) that has these fixes applied and sets the CAP_SYS_TTY_CONFIG capability to the dfbinfo binary. (Other DirectFB binaries probably need the same magic, but as I am not a DirectFB user, I can't really say which ones.) Per http://forums.grsecurity.net/viewtopic.php?f=7t=2522 , giving the program CAP_SYS_TTY_CONFIG is basically equivalent to making it setuid-root. Was the code designed to be run in such a risky setup? Capabilities: still useless. - ajax -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/29/2012 03:16 PM, Adam Jackson wrote: On 8/29/12 3:06 PM, Miloslav Trmač wrote: On Wed, Aug 29, 2012 at 8:33 PM, Tom Callaway tcall...@redhat.com wrote: I made an updated package (1.6.1) that has these fixes applied and sets the CAP_SYS_TTY_CONFIG capability to the dfbinfo binary. (Other DirectFB binaries probably need the same magic, but as I am not a DirectFB user, I can't really say which ones.) Per http://forums.grsecurity.net/viewtopic.php?f=7t=2522 , giving the program CAP_SYS_TTY_CONFIG is basically equivalent to making it setuid-root. Was the code designed to be run in such a risky setup? Capabilities: still useless. Unsure. That is the reason it was failing, though. Seems like it wouldn't be a good idea to enable CAP_SYS_TTY_CONFIG by default though. ~tom == Fedora Project -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/29/2012 02:33 PM, Tom Callaway wrote: On 08/29/2012 09:25 AM, Gerry Reno wrote: DirectFB says that there are Fedora packaging errors which are causing the undefined symbol on XUnlockDisplay and inability to run as normal user. Upstream is wrong, btw. The dlopen problem is caused by the fact that they don't pass the $(X11VDPAU_LIBS) to the LDFLAGS for linking libdirectfb_vdpau.la. The core issue behind why dfbinfo doesn't run as a normal user is due to the fact that the Linux kernel requires CAP_SYS_TTY_CONFIG to do any TTY ioctl() calls. UID 0 (root) has that, but normal users do not. It is possible to give a binary that capability using the setcap command. The missing udev rules also factor into this, I suspect. Last but not least, I believe a normal user needs to be in at least the tty and video groups. (and they need to be active, as reported by `groups`). Since there is no real way to handle this in the package, it just needs to be done by any user who wants to use dfbinfo: usermod -a -G tty video USERNAME I made an updated package (1.6.1) that has these fixes applied and sets the CAP_SYS_TTY_CONFIG capability to the dfbinfo binary. (Other DirectFB binaries probably need the same magic, but as I am not a DirectFB user, I can't really say which ones.) Please note that I could only get the dfbinfo results as an unprivileged user from the console (not from within X), and those results are not identical to what I get when I run it as root. When I tried to run it from X, my X session crashed and the kernel panicked. Good times. :) Anyways, Gerry, please test and let me know if these packages work for you, and once I hear back, I'll push out updates. http://koji.fedoraproject.org/koji/taskinfo?taskID=4435408 ~tom == Fedora Project Thanks Tom. I'll try to check your updates later today and report back. Gerry -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
Gerry, You could also use DirectFB's X11 system module, so that you can run DirectFB-based applications in a usual X11 window. You can tell DirectFB so by using the DFBARGS environment variable: $ export DFBARGS=system=x11,mode=1280x800 (probably also w/ disable-module=gl) $./your_directfb_application Nicolas Chauvet is now upstreaming changes for Fedora to directfb-dev ML. -Ilyes On Wed, Aug 29, 2012 at 8:29 PM, Gerry Reno gr...@verizon.net wrote: On 08/29/2012 02:33 PM, Tom Callaway wrote: On 08/29/2012 09:25 AM, Gerry Reno wrote: DirectFB says that there are Fedora packaging errors which are causing the undefined symbol on XUnlockDisplay and inability to run as normal user. Upstream is wrong, btw. The dlopen problem is caused by the fact that they don't pass the $(X11VDPAU_LIBS) to the LDFLAGS for linking libdirectfb_vdpau.la. The core issue behind why dfbinfo doesn't run as a normal user is due to the fact that the Linux kernel requires CAP_SYS_TTY_CONFIG to do any TTY ioctl() calls. UID 0 (root) has that, but normal users do not. It is possible to give a binary that capability using the setcap command. The missing udev rules also factor into this, I suspect. Last but not least, I believe a normal user needs to be in at least the tty and video groups. (and they need to be active, as reported by `groups`). Since there is no real way to handle this in the package, it just needs to be done by any user who wants to use dfbinfo: usermod -a -G tty video USERNAME I made an updated package (1.6.1) that has these fixes applied and sets the CAP_SYS_TTY_CONFIG capability to the dfbinfo binary. (Other DirectFB binaries probably need the same magic, but as I am not a DirectFB user, I can't really say which ones.) Please note that I could only get the dfbinfo results as an unprivileged user from the console (not from within X), and those results are not identical to what I get when I run it as root. When I tried to run it from X, my X session crashed and the kernel panicked. Good times. :) Anyways, Gerry, please test and let me know if these packages work for you, and once I hear back, I'll push out updates. http://koji.fedoraproject.org/koji/taskinfo?taskID=4435408 ~tom == Fedora Project Thanks Tom. I'll try to check your updates later today and report back. Gerry -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
Tom,
Ok, I tried testing with the following settings:
$ ls -l /dev/tty{,0,1} /dev/fb{,0}
lrwxrwxrwx. 1 root root 3 Aug 21 21:52 /dev/fb - fb0
crw-rw-rw-. 1 root video 29, 0 Aug 21 21:52 /dev/fb0
crw-rw-rw-. 1 root tty5, 0 Aug 21 21:52 /dev/tty
crw--w. 1 root tty4, 0 Aug 21 21:52 /dev/tty0
crw--w. 1 root tty4, 1 Aug 21 21:52 /dev/tty1
$ groups
greno tty wheel dialout video vboxusers
$ grep greno /etc/group
tty:x:5:greno
wheel:x:10:greno
video:x:39:greno
dialout:x:18:greno
greno:x:1000:
vboxusers:x:988:greno
$ cat /etc/udev/rules.d/40-permissions.rules
KERNEL==fb[0-9]*, GROUP=video, MODE=0666
KERNEL==tty[0-9]*,GROUP=tty, MODE=0666
KERNEL==mice, MODE=0666
The result is this:
$ dfbinfo
~~| DirectFB 1.6.1 |~~
(c) 2001-2012 The world wide DirectFB Open Source Community
(c) 2000-2004 Convergence (integrated media) GmbH
(*) DirectFB/Core: Single Application Core. (2012-08-29 21:15)
(*) Direct/Memcpy: Using Generic 64bit memcpy()
(*) Direct/Thread: Started 'Fusion Dispatch' (-1) [MESSAGING OTHER/OTHER
0/0] 8388608...
(!) DirectFB/core/vt: Error opening `/dev/tty1'!
-- Permission denied
(!) DirectFB/Core: Could not initialize 'system_core' core!
-- A general initialization error occured
(#) DirectFBError [DirectFBCreate() failed]: A general initialization error
occured
Segmentation fault
I set the perms in the udev rules to 0666 but the tty does not setup that
way for some reason.
Gerry
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/29/2012 06:43 PM, Ilyes Gouta wrote: Gerry, You could also use DirectFB's X11 system module, so that you can run DirectFB-based applications in a usual X11 window. You can tell DirectFB so by using the DFBARGS environment variable: $ export DFBARGS=system=x11,mode=1280x800 (probably also w/ disable-module=gl) $./your_directfb_application Nicolas Chauvet is now upstreaming changes for Fedora to directfb-dev ML. -Ilyes That's great. I am using something similar through my .directfbrc file: $ cat ~/.directfbrc system=fbdev depth=16 mode=1024x768 autoflip-window force-windowed # autoport=2 Gerry -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/27/2012 10:59 PM, Ilyes Gouta wrote: Hi Gerry, Try contacting the main dev. mailing-list of DirectFB. I'm sure you'll get an answer there. Btw, DirectFB-1.5.3 is rather old, DirectFB-1.6.1 is rather the latest stable release. -Ilyes Thanks Ilyes. I'll try posting over on the directfb dev list. Gerry -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
On 08/24/2012 06:56 PM, Gerry Reno wrote: I have had no success whatsoever getting DirectFB to run under F17 as a regular user on my HP laptop. # yum list DirectFB Installed Packages directfb.x86_64 1.5.3-7.fc17 @updates I have discussed the problems on the DirectFB mailing list and they direct me back to the distro. When trying to run any DirectFB command as a regular user I get permission errors like this: $ dfbinfo ~~| DirectFB 1.5.3 |~~ (c) 2001-2010 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Single Application Core. (2012-05-19 15:35) (*) Direct/Memcpy: Using Generic 64bit memcpy() (!) DirectFB/core/vt: Error opening `/dev/tty1'! -- Permission denied (!) DirectFB/Core: Could not initialize 'system_core' core! -- A general initialization error occured (#) DirectFBError [DirectFBCreate() failed]: A general initialization error occured Even when I go and change the permissions on /dev/ttyX and /dev/fb/0 and then put those into udev rules then I still get an error about MEDIUMRAW mode. I am able to run some DirectFB commands as root but that is no good for creating app for general user. Can anyone, developer, packager, shed some light on why DirectFB will not run on F17 as a regular user? Thank you. . So after fixing permissions on tty and fb I can get to here: $ dfbinfo ~~| DirectFB 1.5.3 |~~ (c) 2001-2010 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Single Application Core. (2011-08-23 22:08) (!) DirectFB/fbdev/vt: K_MEDIUMRAW failed! -- Operation not permitted (!) DirectFB/Core: Could not initialize 'system_core' core! -- A general initialization error occured (#) DirectFBError [DirectFBCreate() failed]: A general initialization error occured $ What needs to be done to fix this error? Google is absolutely no help. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: F17: DirectFB
Hi Gerry, Try contacting the main dev. mailing-list of DirectFB. I'm sure you'll get an answer there. Btw, DirectFB-1.5.3 is rather old, DirectFB-1.6.1 is rather the latest stable release. -Ilyes On Aug 28, 2012 1:04 AM, Gerry Reno gr...@verizon.net wrote: On 08/24/2012 06:56 PM, Gerry Reno wrote: I have had no success whatsoever getting DirectFB to run under F17 as a regular user on my HP laptop. # yum list DirectFB Installed Packages directfb.x86_64 1.5.3-7.fc17 @updates I have discussed the problems on the DirectFB mailing list and they direct me back to the distro. When trying to run any DirectFB command as a regular user I get permission errors like this: $ dfbinfo ~~| DirectFB 1.5.3 |~~ (c) 2001-2010 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Single Application Core. (2012-05-19 15:35) (*) Direct/Memcpy: Using Generic 64bit memcpy() (!) DirectFB/core/vt: Error opening `/dev/tty1'! -- Permission denied (!) DirectFB/Core: Could not initialize 'system_core' core! -- A general initialization error occured (#) DirectFBError [DirectFBCreate() failed]: A general initialization error occured Even when I go and change the permissions on /dev/ttyX and /dev/fb/0 and then put those into udev rules then I still get an error about MEDIUMRAW mode. I am able to run some DirectFB commands as root but that is no good for creating app for general user. Can anyone, developer, packager, shed some light on why DirectFB will not run on F17 as a regular user? Thank you. . So after fixing permissions on tty and fb I can get to here: $ dfbinfo ~~| DirectFB 1.5.3 |~~ (c) 2001-2010 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Single Application Core. (2011-08-23 22:08) (!) DirectFB/fbdev/vt: K_MEDIUMRAW failed! -- Operation not permitted (!) DirectFB/Core: Could not initialize 'system_core' core! -- A general initialization error occured (#) DirectFBError [DirectFBCreate() failed]: A general initialization error occured $ What needs to be done to fix this error? Google is absolutely no help. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
F17: DirectFB
I have had no success whatsoever getting DirectFB to run under F17 as a regular user on my HP laptop. # yum list DirectFB Installed Packages directfb.x86_64 1.5.3-7.fc17 @updates I have discussed the problems on the DirectFB mailing list and they direct me back to the distro. When trying to run any DirectFB command as a regular user I get permission errors like this: $ dfbinfo ~~| DirectFB 1.5.3 |~~ (c) 2001-2010 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Single Application Core. (2012-05-19 15:35) (*) Direct/Memcpy: Using Generic 64bit memcpy() (!) DirectFB/core/vt: Error opening `/dev/tty1'! -- Permission denied (!) DirectFB/Core: Could not initialize 'system_core' core! -- A general initialization error occured (#) DirectFBError [DirectFBCreate() failed]: A general initialization error occured Even when I go and change the permissions on /dev/ttyX and /dev/fb/0 and then put those into udev rules then I still get an error about MEDIUMRAW mode. I am able to run some DirectFB commands as root but that is no good for creating app for general user. Can anyone, developer, packager, shed some light on why DirectFB will not run on F17 as a regular user? Thank you. . -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
