Results 1 to 9 of 9

Thread: KDE(KScreen) is this a functional problem ( major or minor ) or just a logging issue?

  1. #1

    Default KDE(KScreen) is this a functional problem ( major or minor ) or just a logging issue?

    I've searched the forums and the bugs, and if this issue has been reported, I haven't found any mention of it.

    The hardware on the machine I'm using passed a suite of hardware diagnostics with no problems.

    I have only one video card, it has a VGA output and a DVI output; I am using ONLY the DVI output, and it is directly cabled to a monitor which works just fine. Yet, the messages further below, which I've enclosed in code tags, are what I see in the journal for just a single second.

    I have to accomplish some work which for me is very important, so although I normally use KDE I've temporarily switched to Gnome, since I can't afford delays.

    I'd appreciate any info., is this some known issue? If so, is it functional, e.g. likely to cause crashes, or is just overzealous use of log messages, or what?

    Or am I missing something; because it seems as if kscreen seems to think that the display has changed, but if I'm thinking correctly, it's showing the same display label for both the "before" and "after" display.

    Code:
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )
    Apr 03 13:38:56 dev-mach org.kde.KScreen[2585]: kscreen: Primary output changed from KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" ) to KScreen::Output(Id: 98 , Name: "DVI-D-1" ) ( "DVI-D-1" )

  2. #2

    Default Re: KDE(KScreen) is this a functional problem ( major or minor ) or just a logging issue?

    Quote Originally Posted by toes View Post
    I'd appreciate any info., is this some known issue? If so, is it functional, e.g. likely to cause crashes, or is just overzealous use of log messages, or what?
    Yes, this does look like a known issue:
    See http://bugzilla.opensuse.org/show_bug.cgi?id=974762, and more importantly https://bugs.kde.org/show_bug.cgi?id=355928

    Shouldn't cause any problems AFAIK, except for those messages in the xsession log (which is cleared on login).

    To get rid of the messages, you could upgrade by using the additional KDE:Qt5 and KDE:Frameworks5 repos (but be sure to do a full switch after adding the repos, to avoid problems).

    A workaround also seems to be to create a file ~/.config/QtProject/qtlogging.ini with this content, according to the KDE bug report:

    Code:
    [Rules]
    
    kscreen.debug=false
    This should disable all debug messages from kscreen AIUI.

  3. #3

    Default Re: KDE(KScreen) is this a functional problem ( major or minor ) or just a logging issue?

    Thanks for the information!

    Just to make sure that I understand, the two repositories of which you speak are:

    http://download.opensuse.org/reposit...USE_Leap_42.1/

    http://download.opensuse.org/reposit...USE_Leap_42.1/


    and when you say "be sure to do a full switch after adding the repos", you mean that I should make sure that I get all the related RPM's from those two repositories, during a single update? Is that correct?



  4. #4
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,749

    Default Re: KDE(KScreen) is this a functional problem ( major or minor ) or just a logging issue?

    You switch vendors.

    After adding the repos do a zypper lr -d to see the repo list

    note the numbers assigned to each new repo. Say the numbers are #A and #B

    then zypper dup --from #A --from #B

    were the #A and #B are the number seen in the repo list. This will switch the system to use things from these repos

    If unsure show zypper lr -d

  5. #5

    Default Re: KDE(KScreen) is this a functional problem ( major or minor ) or just a logging issue?

    Quote Originally Posted by gogalthorp View Post
    You switch vendors.

    After adding the repos do a zypper lr -d to see the repo list

    note the numbers assigned to each new repo. Say the numbers are #A and #B

    then zypper dup --from #A --from #B

    were the #A and #B are the number seen in the repo list. This will switch the system to use things from these repos

    If unsure show zypper lr -d
    Thanks, but as it happens, I generally don't use zypper. I'll have to see how the package names and version ID's from the installed packages compare to those in the other two repositories ( if I have the correct two repos. shown in my previous comment, since AFAIK, those two were not published in the list of "Community Repositories" ). But glancing at the manual page for zypper, it seems almost as if that's zypper's way of swapping repo. priorities and then doing an update for a list of packages; sounds as if the method-independent/short-answer to the final/summary question in my previous comment is, "yes". :-)

  6. #6
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,749

    Default Re: KDE(KScreen) is this a functional problem ( major or minor ) or just a logging issue?

    In Yast you can do the vendors switch by selecting view by repo for each repo then select change vendor at the top this will switch packages to the new repos

  7. #7

    Default Re: KDE(KScreen) is this a functional problem ( major or minor ) or just a logging issue?

    Quote Originally Posted by toes View Post
    Thanks for the information!

    Just to make sure that I understand, the two repositories of which you speak are:

    http://download.opensuse.org/reposit...USE_Leap_42.1/
    No.
    You should rather use http://download.opensuse.org/reposit...USE_Leap_42.1/, that contains the latest stable Qt5 release (5.6.0 at the moment).
    KDE:Qt56 is an *unstable* repo that always contains the latest Qt 5.6 git snapshot.

    Yes.

    The rest has been answered already.

    But again, just creating ~/.config/QtProject/qtlogging.ini with the posted content should also eliminate those debug messages.
    And the only "problem" here is too much debug output AIUI...

  8. #8

    Default Re: KDE(KScreen) is this a functional problem ( major or minor ) or just a logging issue?

    wolfi323,

    Thanks for clarifying which repo. to use. The ticket on the KDE site may have changed since you first viewed it. AIUI, it sounds as if an actual problem was fixed, beyond the initial setting of the debug output.

    Thanks for all your help!

  9. #9

    Default Re: KDE(KScreen) is this a functional problem ( major or minor ) or just a logging issue?

    Quote Originally Posted by toes View Post
    Thanks for clarifying which repo. to use. The ticket on the KDE site may have changed since you first viewed it. AIUI, it sounds as if an actual problem was fixed, beyond the initial setting of the debug output.
    Yes, there have been fixes made to Qt5 and KScreen, and the message has been disabled in KScreen 5.6 too.

    If you don't experience a real problem, there's nothing to fix though.
    The message itself is harmless as I wrote.

Tags for this Thread

Posting Permissions

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