Hide Forgot
Description of problem: when running terminator with xfce4 on Fedora 19 when starting bicon everything seems to be normal but when running ncurses application the resolution for some reason changes to 640x480. resizing the window and exiting the application does not help . only exiting bicon and reset the terminal helps Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 885257 [details] bicon in 640x480 It seems bicon works fine in my box. Attached my screenshot. Which ncurses application did you try? gnome-screenshot can take the screenshot: % gnome-screenshot -i
Hay , I am using XFCE4 with terminator (terminal application) and mutt for my email , I am attaching a screenshot of before and after I am getting it with more then one application the same thing occur with newsbeuter
Created attachment 888396 [details] the bicon command befor mutt/newsbeuter
Created attachment 888397 [details] the bicon command after mutt/newsbeuter after I am exiting bicon and run the reset command the terminal goes back to normal size
I don't see any problems with mutt or newsbeuter.
Hay, is there any more direction I can check to see the why my resolution is very small when working with bicon and ncurses application ?
I have no idea. You may like to ask upstream directly: http://projects.arabeyes.org/project.php?proj=BiCon
Hi, I have did some investigation and a notice that the $COLUMNS and $LINES have changes after I run the bicon command. if I set them manually then the ncurses application run as it should me@localhost ~ $ echo $LINES 49 me@localhost ~ $ echo $COLUMNS 140 me@localhost ~ $ bicon BiCon started me@localhost ~ $ echo $LINES 24 me@localhost ~ $ echo $COLUMNS 80 is there anything that can be done to preserve the right values ? thanks in advanced
(In reply to Oren Oichman from comment #8) > me@localhost ~ $ echo $LINES > 49 > me@localhost ~ $ echo $COLUMNS > 140 > me@localhost ~ $ bicon > BiCon started > me@localhost ~ $ echo $LINES > 24 > me@localhost ~ $ echo $COLUMNS > 80 I don't see that change when bicon starts. But I saw LINES and COLUMNS are reset when bicon exits. I noticed $HOME/.bashrc is loaded when bicon starts. Your login script might change that values. BTW, bicon is a wrapper shell script and it calls bicon.bin
bicon-0.4-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/bicon-0.4-1.fc19
Could you check if your problem exists in bicon 0.4?
Since no reply, I close this with the update and will integrate the new bicon in f19 too later.
bicon-0.4-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
Hi, the problem still presist I did a workaround in the bashrc file : [[ -z $lines ]] && export lines=$LINES [[ -z $columns ]] && export columns=$COLUMNS if [[ $COLUMNS != $columns ]] && [[ ! -z $columns ]] ; then export COLUMNS=$columns; fi if [[ $LINES != $lines ]] && [[ ! -z $lines ]] ; then export LINES=$lines; fi for some reason the base values are 24x80 is there a why to change the defualt values
I don't see the default values in my view. It would be good for you to file a bug in upstream since I cannot reproduce your bug: http://projects.arabeyes.org/project.php?proj=BiCon
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.