xsessions-error msg's - Mandriva

This is a discussion on xsessions-error msg's - Mandriva ; 2008.1 2.6.22.12-desktop-1mdv kde 3.5.7 Found this while looking thru my xsessions-error file. There must be dozens of this same error one after another. Any idea's what I might have configured wrong that is bringing up these error's ? Tia,Dale QDate::setYMD: ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: xsessions-error msg's

  1. xsessions-error msg's

    2008.1
    2.6.22.12-desktop-1mdv
    kde 3.5.7

    Found this while looking thru
    my xsessions-error file.
    There must be dozens of this same error
    one after another.
    Any idea's what I might
    have configured wrong that is
    bringing up these error's ?
    Tia,Dale

    QDate::setYMD: Invalid date 0008-08-00
    QDate::setYMD: Invalid date 0008-08-00
    QDate::setYMD: Invalid date 0008-08-00
    QDate::setYMD: Invalid date 0008-08-00

  2. Re: xsessions-error msg's

    Dale wrote:
    > 2008.1
    > 2.6.22.12-desktop-1mdv
    > kde 3.5.7
    >
    > Found this while looking thru
    > my xsessions-error file.
    > There must be dozens of this same error
    > one after another.
    > Any idea's what I might
    > have configured wrong that is
    > bringing up these error's ?
    > Tia,Dale
    >
    > QDate::setYMD: Invalid date 0008-08-00
    > QDate::setYMD: Invalid date 0008-08-00
    > QDate::setYMD: Invalid date 0008-08-00
    > QDate::setYMD: Invalid date 0008-08-00


    It looks like you machine does not have the date set.

    In a console window, run the command
    date
    and see if it provides the proper date.
    If not, man date
    for information on how I set my machine. I think
    you can also set date/time in the MCC graphic
    interface and the KDE Control Center graphic interface.

    Cheers!

    jim b.

    --
    UNIX is not user unfriendly; it merely
    expects users to be computer-friendly.

  3. Re: xsessions-error msg's

    Jim Beard wrote:

    > Dale wrote:
    >> 2008.1
    >> 2.6.22.12-desktop-1mdv
    >> kde 3.5.7
    >>
    >> Found this while looking thru
    >> my xsessions-error file.
    >> There must be dozens of this same error
    >> one after another.
    >> Any idea's what I might
    >> have configured wrong that is
    >> bringing up these error's ?
    >> Tia,Dale
    >>
    >> QDate::setYMD: Invalid date 0008-08-00
    >> QDate::setYMD: Invalid date 0008-08-00
    >> QDate::setYMD: Invalid date 0008-08-00
    >> QDate::setYMD: Invalid date 0008-08-00

    >
    > It looks like you machine does not have the date set.
    >
    > In a console window, run the command
    > date
    > and see if it provides the proper date.
    > If not, man date
    > for information on how I set my machine. I think
    > you can also set date/time in the MCC graphic
    > interface and the KDE Control Center graphic interface.
    >
    > Cheers!
    >
    > jim b.
    >

    Thanks Jim but the date and time
    come up correct when looking at
    the KDE Control Center.

  4. Re: xsessions-error msg's

    On Tue, 05 Aug 2008 16:28:15 -0400, Dale wrote:
    > Jim Beard wrote:
    >
    >> Dale wrote:
    >>> 2008.1
    >>> 2.6.22.12-desktop-1mdv
    >>> kde 3.5.7
    >>>
    >>> Found this while looking thru
    >>> my xsessions-error file.
    >>> QDate::setYMD: Invalid date 0008-08-00
    >>> QDate::setYMD: Invalid date 0008-08-00

    >>

    > Thanks Jim but the date and time
    > come up correct when looking at
    > the KDE Control Center.


    My suggestion:
    click up a terminal.
    rm ~/.xsession-errors
    exit

    logout.

    login,
    click up a terinal
    grep QDate ~/.xsession-errors

    If nothing returned,

    tail -f ~/.xsession-errors

    Now run each app you normally run and see what creates it.

    I do not have the error in my ~/.xsession-errors file.

    I know I always get into the KDE Control Center and made sure
    that "Start with an empth session" is set under Session Manager under
    KDE Components after new install or deletion of ~/.kde*


  5. Re: xsessions-error msg's

    Bit Twister wrote:

    > On Tue, 05 Aug 2008 16:28:15 -0400, Dale wrote:
    >> Jim Beard wrote:
    >>
    >>> Dale wrote:
    >>>> 2008.1
    >>>> 2.6.22.12-desktop-1mdv
    >>>> kde 3.5.7
    >>>>
    >>>> Found this while looking thru
    >>>> my xsessions-error file.
    >>>> QDate::setYMD: Invalid date 0008-08-00
    >>>> QDate::setYMD: Invalid date 0008-08-00
    >>>

    >> Thanks Jim but the date and time
    >> come up correct when looking at
    >> the KDE Control Center.

    >
    > My suggestion:
    > click up a terminal.
    > rm ~/.xsession-errors
    > exit
    >
    > logout.
    >
    > login,
    > click up a terinal
    > grep QDate ~/.xsession-errors
    >
    > If nothing returned,
    >
    > tail -f ~/.xsession-errors


    Here's what I got after
    tail -f ~/.xsession-errors

    [dale@localhost ~]$ tail -f ~/.xsession-errors
    WeaverThreadLogger: thread (ID: 1) suspended.
    WeaverThreadLogger: thread (ID: 2) suspended.
    WeaverThreadLogger: thread (ID: 3) suspended.
    WeaverThreadLogger: thread (ID: 4) suspended.
    Weaver dtor: destroying inventory.
    WeaverThreadLogger: thread (ID: 1) destroyed.
    WeaverThreadLogger: thread (ID: 2) destroyed.
    WeaverThreadLogger: thread (ID: 3) destroyed.
    WeaverThreadLogger: thread (ID: 4) destroyed.
    Weaver dtor: done

    Is this info helpful as far as what it shows
    or due I need to run more prog's
    >
    > Now run each app you normally run and see what creates it.
    >
    > I do not have the error in my ~/.xsession-errors file.
    >
    > I know I always get into the KDE Control Center and made sure
    > that "Start with an empth session" is set under Session Manager under
    > KDE Components after new install or deletion of ~/.kde*



  6. Re: xsessions-error msg's

    On Fri, 08 Aug 2008 14:25:34 -0400, Dale wrote:
    >
    > Here's what I got after
    > tail -f ~/.xsession-errors


    Well, your QDate problem cleared up. :-)


    > [dale@localhost ~]$ tail -f ~/.xsession-errors
    > WeaverThreadLogger: thread (ID: 1) suspended.
    > Weaver dtor: destroying inventory.
    > WeaverThreadLogger: thread (ID: 1) destroyed.
    > Weaver dtor: done
    >
    > Is this info helpful as far as what it shows
    > or due I need to run more prog's


    If you are wanting to hunt down your QDate problem, you have
    either fixed the problem or have not executed the program
    causing the QDate entries.

    Your call.

+ Reply to Thread