Summary: | sys-apps/qingy-1.0.0: Fallback to textmode with>=x11-drivers/nvidia-drivers-270.41.06 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dustin Polke <DuPol> |
Component: | [OLD] Unspecified | Assignee: | Michele Noberasco (RETIRED) <s4t4n> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | games |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Debug log |
Description
Dustin Polke
2011-06-22 13:48:43 UTC
Still present with nvidia-drivers-270.41.19. Hi Dustin, dingy does nothing more than use DirectFB for its GUI. If the GUI is fails for you (and worked with previous nvidia-drivers), it is either a problem with nvidia-drivers or DirectFB, not with qingy. As a first step, you should try other DirectFB-enabled applications (such as the links browser) and see whether they fail, too. Regards, Michele Hi Michele, (In reply to comment #2) > Hi Dustin, > > dingy does nothing more than use DirectFB for its GUI. If the GUI is fails for > you (and worked with previous nvidia-drivers), it is either a problem with > nvidia-drivers or DirectFB, not with qingy. > > As a first step, you should try other DirectFB-enabled applications (such as > the links browser) and see whether they fail, too. I tried with mplayer which I had already installed with USE=directfb and it plays movies correctly outside X environment. I will try to find which line of code triggers the invalid permissions debug line and see why. The permission error is spit out by DirectFB but I have no clue how to debug this. I CC mainainers of DirectFB. Maybe I can get pointers from them. I have now updated to DirectFB-1.4.9-r1 but both 1.4.5 and 1.4.9-r1 throw the invalid permissions line and qingy fails to start the GUI. I emerged DirectFB with USE=debug but there is no additional output on syslog. If anyone can give me a hint to track this down, I really appreciate. I switched over to nouveau driver and with that one, qingy works as expected. DirectFB is a set of patches to operate on the framebuffer directly which means its not using nvidia-drivers. So its likely its not initializing things correctly once nvidia-drivers has accessed the card when starting up X. Using DirectFB and X at the same time is definitely not something that I'm sure would work. It sounds like you got another way to work around this though so marking this as obsolete. If you return to nvidia-drivers and the issue crops up again, run nvidia-bug-report.sh and e-mail the output along with a description of the issue to linux-bugs@nvidia.com |