Sven Luther wrote:
On Sat, Dec 03, 2005 at 02:34:14PM +0100, Attilio Fiandrotti wrote:Sven Luther wrote:On Sat, Dec 03, 2005 at 12:50:19AM +0200, Guillem Jover wrote:Hi, On Fri, Dec 02, 2005 at 10:18:40AM +0100, Attilio Fiandrotti wrote:If the bug is fixed when hw-acceleration is disabled i think a good idea would be making the libdirectfb or the gtk-rootskel udeb containing anto /etc/directfbrc configuration file that contains#prevents DFB from using hardware acceleration no-hardware #lets user dumping screen by pressing "Stamp" key screenshot-dir=/Mmm, Attilio, i don't think this file should be hardcoded like that, but better provided by rootskel-gtk, or generated from rootskel-gtk at early runtime, as we may wish to make it configurable from /proc/cmdline, and dosome more advanced matching depending on graphic card used or architecture, asi proposed yesterday.yes, now i'm convinced too that the right place for the "/etc/dirctfbrc" file is not the libdirectfb-lib; maybe the gtk-rootskel is a better choice for a "static" configuration file. I know that installation logs can be retrived via an http server at the end of the installation, so maybe we should tell DFB to place the screen dumps where they can be accessed by the web server (that may need some modifications to be able to serve dumps), could this be a good idea?Yes, definitively. i think it takes all from /var/log or something such, notsure.If we could access screendump files via HTTP server, would still be useful a d-i boot option that tells DFB where the screendumps shall be placed?Don't think so, but hey.Anyway i think giving the user the ability to take dumps of the screen could be very useful for bugreporting, what do you think?Yes. mayeb we could have some special key (maybe even the "prt scr" one :) when pushed at any time, do such a screenshot :), and maybe add some infoabout the context of the screenshots in a separate file ?
to be able to track this down later i've opened a new "wishlist" bug against cdebconf-gtk.
ciao Attilio