[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnash-commit] [bug #46949] fb-gnash left console in unusable state afte

From: Nutchanon Wetchasit
Subject: [Gnash-commit] [bug #46949] fb-gnash left console in unusable state after exiting
Date: Sun, 31 Jan 2016 11:10:03 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:25.5) Gecko/20150606 Firefox/31.9 PaleMoon/25.5.0

Follow-up Comment #7, bug #46949 (project gnash):

Current git version of Framebuffer Gnash now turn console back to text mode
properly when stopped by `fscommand("quit")` ActionScript, `--once`
command line switch, SIGINT (Ctrl+C), and SIGTERM (`killall fb-gnash`).

Screenshot after running `fb-gnash -v secondframeexit12-repaint.swf`:
(Test SWF from file #36046, bug #27981; with `set ignoreFSCommand false` in

Screenshot after running `fb-gnash -v --once 12frames.swf`:

Screenshot after running `fb-gnash -v 12frames.swf` and pressed Ctrl+C:

Screenshot after running `fb-gnash -v 12frames.swf` and used `killall

You'd see that in every case, the console came back to text mode when Gnash
terminated. You'd also see that there's a "Segmentation fault" error shown
at the end of each run too.

Screenshots are attached in `` as a

This bug could be now marked as fixed.
The segmentation fault problem is filed separately as bug #47029.

Gnash: 0.8.11dev (git e705394 29-Jan-2016)
Framebuffer: inteldrmfb `/dev/fb0` 1366x768 32-bit
System: Debian GNU/Linux 7.0 Wheezy i386

(file #36217)

Additional Item Attachment:

File name: Size:17 KB


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]