Bug 19810 - No F2 screenshots when we use 'vesa' driver as falback for 'fbdev' ("fb2png: cannot open framebuffer")
Summary: No F2 screenshots when we use 'vesa' driver as falback for 'fbdev' ("fb2png: ...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Low normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords: 6sta1
Depends on:
Blocks:
 
Reported: 2016-11-18 10:02 CET by Marja Van Waes
Modified: 2019-02-19 09:46 CET (History)
2 users (show)

See Also:
Source RPM: drakx-installer-stage2
CVE:
Status comment:


Attachments
Installation with no screenshots. (163.22 KB, application/x-xz)
2016-11-19 23:41 CET, Renato Dali
Details
Nothing in this directory... (70.29 KB, image/png)
2016-11-19 23:45 CET, Renato Dali
Details
Files in /root/drakx (84.09 KB, image/png)
2016-11-19 23:46 CET, Renato Dali
Details

Description Marja Van Waes 2016-11-18 10:02:55 CET
In this comment in another bug report:
https://bugs.mageia.org/show_bug.cgi?id=19598#c8

Renato Dali reported:

> F2 did not work, though a message did appear stating that screenshots would be
> in the above mentioned directory; alas, after reboot they weren't there.

@ Renato

Can you please attach /root/drakx/report.bug.xz of that install to this bug report?
Comment 1 Renato Dali 2016-11-19 23:41:34 CET
Created attachment 8680 [details]
Installation with no screenshots.
Comment 2 Renato Dali 2016-11-19 23:44:07 CET
Hi, Marja, sorry for the delay... I had to reinstall because in the meantime I did another install without taking screenshots.

In this one I pressed F2, got the warning about "Screenshots will be in..." and there they weren't after all.

Thanks for organizing the bugs, BTW.
Comment 3 Renato Dali 2016-11-19 23:45:37 CET
Created attachment 8681 [details]
Nothing in this directory...
Comment 4 Renato Dali 2016-11-19 23:46:47 CET
Created attachment 8682 [details]
Files in /root/drakx
Comment 5 Marja Van Waes 2016-11-20 00:05:23 CET
(In reply to Renato Dali from comment #1)
> Created attachment 8680 [details]
> Installation with no screenshots.

[marja@localhost Downloads]$ xzcat 19810report.bug.xz | grep fb2png
* running: fb2png -p /mnt/root/DrakX-screenshots/1.png
fb2png: cannot open framebuffer - No such file or directory* to put in /mnt/etc/modprobe.preload evdev
* running: fb2png -p /mnt/root/DrakX-screenshots/1.png
fb2png: cannot open framebuffer - No such file or directory* running: fb2png -p /mnt/root/DrakX-screenshots/1.png
fb2png: cannot open framebuffer - No such file or directory* running: gurpmi2 --auto-select with root /mnt
* running: fb2png -p /mnt/root/DrakX-screenshots/1.png
fb2png: cannot open framebuffer - No such file or directory* running: fb2png -p /mnt/root/DrakX-screenshots/1.png
fb2png: cannot open framebuffer - No such file or directory* running: fb2png -p /mnt/root/DrakX-screenshots/1.png
fb2png: cannot open framebuffer - No such file or directory* running: monitor-edid -v --perl
[marja@localhost Downloads]$

Keywords: NEEDINFO => (none)
Summary: F2 screenshots aren't in /root/DrakX-screenshots after install => F2 screenshots aren't in /root/DrakX-screenshots after install (fb2png: cannot open framebuffer )

Comment 6 Thierry Vignaud 2016-11-20 18:47:17 CET
I would say this is because on your system, fbdev didn't worked out.
And indeed:
* Trying with server Driver:fbdev
* Trying with server Driver:vesa

For the record, the fb2png tool only works if we use the fbdev driver.

What surprises me is that it happened with a Nvidia card.
This usually happens on very old intel cards.

I've added Xorg logs to installer logs but sadly, that only cover the last tried driver and thus we don't have logs for the fbdev driver.

That sayd, those logs are old (DrakX V17.46 was released in June, we're currently at 17.60)

CC: (none) => thierry.vignaud

Thierry Vignaud 2016-11-20 18:47:52 CET

Summary: F2 screenshots aren't in /root/DrakX-screenshots after install (fb2png: cannot open framebuffer ) => No F2 screenshots when we use 'vesa' driver as falback for 'fbdev' ("fb2png: cannot open framebuffer")

Comment 7 Thierry Vignaud 2016-11-20 18:48:52 CET
If someone knows about a more generic tool that still works when eg: clicking with right mouse (most x11 grabbers fails if the x11 cursor is "active"...)

Priority: Normal => Low

Comment 8 Renato Dali 2016-11-20 20:27:34 CET
Hi, Thierry,

Would this not work?

 xwd -root -out screenshot.xwd

(from

http://askubuntu.com/questions/226829/how-to-take-screenshot-of-an-x11-based-gui-from-a-text-terminal-such-as-tty1 )

Actually the mentioned page goes on to say why it would not work from a text console, but I assume that is not the case of the Mageia installer -- AFAIU it requires X11.

(BTW: Gimp opens xwd files)

I didn't understand quite well the part about logs... I always install Mageia 6 from a DVD burned with sta1. I'm not using a rolling image or nightly build (if something like that exists).
Comment 9 Thierry Vignaud 2016-11-20 22:31:34 CET
xwd is out b/c it doesn't grab an opened contextual menu.
Also we would need to convert from a very huge image to png/jpg.

Though it looks like scrot works fine
Comment 10 Mageia Robot 2016-11-20 23:27:05 CET
commit 5d92deb02d6980b5aa264d0b59d4b289d49cf099
Author: Thierry Vignaud <thierry.vignaud@...>
Date:   Sun Nov 20 22:31:45 2016 +0100

    use scrot instead of fb2png (mga#19810)
    
    rationale: fb2png only work with the 'fbdev' driver and thus doesn't
    work at all when fallbacking to the 'vesa' driver
---
 Commit Link:
   http://gitweb.mageia.org/software/drakx/commit/?id=5d92deb02d6980b5aa264d0b59d4b289d49cf099
Comment 11 Renato Dali 2016-11-21 03:06:08 CET
That's great news... thanks, Thierry.
Comment 12 Marja Van Waes 2019-02-19 09:46:30 CET
(In reply to Mageia Robot from comment #10)
> commit 5d92deb02d6980b5aa264d0b59d4b289d49cf099
> Author: Thierry Vignaud <thierry.vignaud@...>
> Date:   Sun Nov 20 22:31:45 2016 +0100
> 
>     use scrot instead of fb2png (mga#19810)
>     
>     rationale: fb2png only work with the 'fbdev' driver and thus doesn't
>     work at all when fallbacking to the 'vesa' driver
> ---
>  Commit Link:
>   
> http://gitweb.mageia.org/software/drakx/commit/
> ?id=5d92deb02d6980b5aa264d0b59d4b289d49cf099

Closing as fixed, then.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.