Results 1 to 4 of 4

Thread: Qt Creator no Application Output

  1. #1
    Join Date
    Mar 2014
    Posts
    30

    Default Qt Creator no Application Output

    hello i have problem, with Aplication Output not printing like qDebug, qWarning, etc

    I test it with create new Qt Widget Applictaion and add code as below on main.cpp
    Code:
    #include "mainwindow.h"
    #include <QApplication>
    
    #include <QDebug>
    
    int main(int argc, char *argv[])
    {
        qDebug() << "Debug";
        qWarning() << "Warning";
        qInfo() << "Info";
        qCritical() << "Critical";
    
        QApplication a(argc, argv);
        MainWindow w;
        w.show();
    
        return a.exec();
    }
    the output only
    Code:
    16:43:41: Debugging starts
    16:43:45: Debugging has finished
    how to enable this in opensuse?

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,643
    Blog Entries
    3

    Default Re: Qt Creator no Application Output

    Traditionally, this sort of debug output used to show up in ".xsession-errors" (or similar). But lately, some of the desktops have been redirecting this to logs. Maybe it shows up in the output of "journalctl -b".
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  3. #3
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,306
    Blog Entries
    2

    Default Re: Qt Creator no Application Output

    I remember there have been questions about changes in Qt Creator debugging...
    Recommend searching these Forums for those posts.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  4. #4
    Join Date
    Mar 2014
    Posts
    30

    Default Re: Qt Creator no Application Output

    Quote Originally Posted by nrickert View Post
    Traditionally, this sort of debug output used to show up in ".xsession-errors" (or similar). But lately, some of the desktops have been redirecting this to logs. Maybe it shows up in the output of "journalctl -b".
    ahh you are right, the output shows in journalctl
    thanks for your reply I found solution only need to add "QT_LOGGING_TO_CONSOLE=1" on env variable

    Quote Originally Posted by tsu2 View Post
    I remember there have been questions about changes in Qt Creator debugging...
    Recommend searching these Forums for those posts.

    TSU
    sorry for create new thread about same problem i didnt mean that

    thank you for the reply btw

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •