On Sun, Jun 10, 2012 at 12:43 PM, Brian Cluff
<brian@snaptek.com> wrote:
You can't just ignore those messages? They just just informational and aren't hurting anything?
In any case, you can make everything that gets spit out on the terminal go away by running it like this:
konqueror 2&>1 >/dev/null lb.html
That might not be what you are looking for, but it will work on any program that you want to be totally quiet, but you won't be able to tell if/why it crashes, unless you redirect it to a file instead of /dev/null
Brian Cluff
On 06/09/2012 02:51 PM,
joe@actionline.com wrote:
When I do (from the command line): firefox lb.htm ... it works perfectly.
No complaints.
When I do (from the command line): konqueror lb.htm ... it works fine,
but I get the series of complaints listed below.
Any idea how to stop those complaint messages?
Also, how can I execute either a firefox or konqueror activation of a
named 'htm' file from the command line without the terminal window having
to stay open?
$ konqueror lb.htm
konqueror(9218)/kdeui (kdelibs): Attempt to use QAction "konqbrowser" with
KXMLGUIFactory!
konqueror(9218)/kdeui (kdelibs): Attempt to use QAction "firefox" with
KXMLGUIFactory!
konqueror(9218)/kdeui (kdelibs): Attempt to use QAction "" with
KXMLGUIFactory!
QPainter::begin: Widget painting can only begin as a result of a paintEvent
QPainter::translate: Painter not active
QPainter::setClipRect: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active
QPainter::hasClipping: Painter not active
QPainter::setPen: Painter not active
QPainter::setBrush: Painter not active