[SOLVED] Kmail acting up (again)...
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 10 of 10
  1. #1
    Join Date
    Oct 2005
    Location
    Rio Grande do Sul, Brazil
    Posts
    185
    Linux (Fedora) Firefox 62.0

    Kmail acting up (again)...

    I posted this grumble in the KDE forum some weeks ago:
    https://forum.kde.org/viewtopic.php?...404217#p404217
    and had very few replies...
    So, here goes nothing in the Fedora Forum:
    ===================================
    OS: Fedora 28 64bits

    Exactly one year ago, I posted some complaints about kmail breaking down and/or freezing the desktop:
    https://forum.kde.org/viewtopic.php?f=215&t=141683

    For the last few months, kmail has been working well, almost without glitches, but since the last update issued a couple of days ago by the fedora updates repo about KDE things, the hurdle started all over again. >
    Exactly the same behavior as before: kmail works for a short time then it breaks down and/or freezes the desktop. Some times I can open a new session with Ctrl-Alt-F2 and send a KILL signal, but sometimes I cannot do even that and have to force a reboot.

    Anyone else out there having the same issues lately?
    ===================================

    Today I posted:
    ==================================
    Today Fedora distributed another update of kmail (v. 18.04.3-2.fc28.x86_64). I was hoping they'd fixed the bug, but... still the same... :'(
    I start kmail, it stays up for some time and then, without any warning or error message, it goes away...
    ==================================

    I don't believe I'm the only one having this problem...
    I just want someone to give me some hints on where I could look and/or what I could do in order to identify what the problem is...
    Rudi Gaelzer
    Registered Linux user # 153741

  2. #2
    Join Date
    Jun 2004
    Location
    Maryland, US
    Posts
    7,418
    Linux (Fedora) Firefox 62.0

    Re: Kmail acting up (again)...

    Try opening a terminal window and run kmail by just typing "kmail"

    There's a good chance that when it dies, you'll get a useful warning or error message text to the console. One of the negatives of gui desktops is they tend to throw away the output messages from the application.

  3. #3
    Join Date
    Oct 2005
    Location
    Rio Grande do Sul, Brazil
    Posts
    185
    Linux (Fedora) Firefox 62.0

    Re: Kmail acting up (again)...

    Quote Originally Posted by marko
    Try opening a terminal window and run kmail by just typing "kmail"

    There's a good chance that when it dies, you'll get a useful warning or error message text to the console. One of the negatives of gui desktops is they tend to throw away the output messages from the application.
    It's worth a try. I'll do it tomorrow when I get back to my office and then will let you know what happened.
    Rudi Gaelzer
    Registered Linux user # 153741

  4. #4
    Join Date
    Oct 2005
    Location
    Rio Grande do Sul, Brazil
    Posts
    185
    Linux (Fedora) Firefox 62.0

    Re: Kmail acting up (again)...

    So, I followed marko's suggestion. Started kmail from the terminal (Konsole) and kept it running until it crashed.
    This is the output in term:
    ------------------------------------------------------------------------------------
    ~>kmail
    "Item query returned empty result set"
    "Item query returned empty result set"
    nouveau: kernel rejected pushbuf: No such file or directory
    nouveau: ch12: krec 0 pushes 0 bufs 1 relocs 0
    nouveau: ch12: buf 00000000 00000002 00000004 00000004 00000000
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 8430, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 8433, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 8436, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    org.kde.pim.messagelist: Requested invariant for storage row index 133 not found in history
    org.kde.pim.messagelist: Requested invariant for storage row index 135 not found in history
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 12287, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 12310, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 12330, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 12739, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 12749, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 12752, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    org.kde.pim.messagecore: Serious mailing list header parsing error!
    org.kde.pim.messagecore: Serious mailing list header parsing error!
    org.kde.pim.messagecore: Serious mailing list header parsing error!
    org.kde.pim.messagecore: Serious mailing list header parsing error!
    org.kde.pim.messagecore: Serious mailing list header parsing error!
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 14031, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 14041, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 14044, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    QFont::setPixelSize: Pixel size <= 0 (0)
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 21493, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 21503, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 21506, resource id: 90177601, major code: 130 (Unknown), minor code: 3
    kmail: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed.
    Received signal 6
    #0 0x7fc3e21bea2e <unknown>
    #1 0x7fc3e21beb40 <unknown>
    #2 0x7fc3e21bf177 <unknown>
    #3 0x7fc3ee0c4f30 <unknown>
    #4 0x7fc3ee0c4eab __GI_raise
    #5 0x7fc3ee0af5b9 __GI_abort
    #6 0x7fc3ee0af491 __assert_fail_base.cold.0
    #7 0x7fc3ee0bd612 __GI___assert_fail
    #8 0x7fc3b8fcecd7 nouveau_pushbuf_data
    #9 0x7fc3b8fcec37 nouveau_pushbuf_data
    #10 0x7fc3b8fced6f <unknown>
    #11 0x7fc3b8fcf1bf <unknown>
    #12 0x7fc3b8fcfdd4 nouveau_pushbuf_kick
    #13 0x7fc3b97cca9a <unknown>
    #14 0x7fc3b9455c4f <unknown>
    #15 0x7fc3b95b6a8f <unknown>
    #16 0x7fc3baf4e1c7 <unknown>
    #17 0x7fc3f3ce64aa <unknown>
    #18 0x7fc3ef3c145f QOpenGLContext::swapBuffers()
    #19 0x7fc3ef5e72cc QPlatformBackingStore::composeAndFlush()
    #20 0x7fc3be160138 <unknown>
    #21 0x7fc3ef8e6cbb <unknown>
    #22 0x7fc3ef8e878b <unknown>
    #23 0x7fc3ef8e9aa2 <unknown>
    #24 0x7fc3ef8e9c41 <unknown>
    #25 0x7fc3ef901435 QWidgetPrivate::syncBackingStore()
    #26 0x7fc3ef9196f8 QWidget::event()
    #27 0x7fc3efa22d68 QMainWindow::event()
    #28 0x7fc3f2527e2b KMainWindow::event()
    #29 0x7fc3f25715e9 KXmlGuiWindow::event()
    #30 0x7fc3ef8da475 QApplicationPrivate::notify_helper()
    #31 0x7fc3ef8e1b90 QApplication::notify()
    #32 0x7fc3eefe1c36 QCoreApplication::notifyInternal2()
    #33 0x7fc3eefe4e0b QCoreApplicationPrivate::sendPostedEvents()
    #34 0x7fc3ef032507 <unknown>
    #35 0x7fc3d999388d g_main_context_dispatch
    #36 0x7fc3d9993c58 <unknown>
    #37 0x7fc3d9993cf0 g_main_context_iteration
    #38 0x7fc3ef032293 QEventDispatcherGlib:rocessEvents()
    #39 0x7fc3be1d17c5 <unknown>
    #40 0x7fc3eefe0b7b QEventLoop::exec()
    #41 0x7fc3eefe8c46 QCoreApplication::exec()
    #42 0x55b5d1f8ca6f <unknown>
    #43 0x7fc3ee0b111b __libc_start_main
    #44 0x55b5d1f8cc1a _start
    r8: 0000000000000000 r9: 00007fff1a12c5f0 r10: 0000000000000008 r11: 0000000000000246
    r12: 00007fc3b8fd0952 r13: 00007fc3b8fd0968 r14: 00000000000002d3 r15: 0000000000000000
    di: 0000000000000002 si: 00007fff1a12c5f0 bp: 00007fc3ee211f68 bx: 0000000000000006
    dx: 0000000000000000 ax: 0000000000000000 cx: 00007fc3ee0c4eab sp: 00007fff1a12c5f0
    ip: 00007fc3ee0c4eab efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
    trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
    [end of stack trace]
    Calling _exit(1). Core file will not be generated.
    Rudi Gaelzer
    Registered Linux user # 153741

  5. #5
    Join Date
    Oct 2005
    Location
    Rio Grande do Sul, Brazil
    Posts
    185
    Linux (Fedora) Firefox 62.0

    Re: Kmail acting up (again)...

    I forgot to mention that after kmail crashed, akonadiserver kept running in the background, taking 100% out of one of the cores.
    So, I had to manually close the processes, otherwise it would keep on getting the emails without the client.
    Rudi Gaelzer
    Registered Linux user # 153741

  6. #6
    Join Date
    Feb 2005
    Location
    London, UK
    Posts
    734
    Windows 7 Chrome 69.0.3497.100

    Re: Kmail acting up (again)...

    Read these, looks like either qt5-qtwebengine has been updated/fixed (are you using an old version?) or you need to install a version from copr:

    https://bugzilla.redhat.com/show_bug.cgi?id=1485203
    https://bugzilla.redhat.com/show_bug.cgi?id=1350275

  7. #7
    Join Date
    Oct 2005
    Location
    Rio Grande do Sul, Brazil
    Posts
    185
    Linux (Fedora) Firefox 62.0

    Re: Kmail acting up (again)...

    Quote Originally Posted by HaydnH
    Read these, looks like either qt5-qtwebengine has been updated/fixed (are you using an old version?) or you need to install a version from copr:

    https://bugzilla.redhat.com/show_bug.cgi?id=1485203
    https://bugzilla.redhat.com/show_bug.cgi?id=1350275
    Thank you for the reply.
    My F28 box is fully updated and, AFAIK, I have the latest QtWebEngine installed:
    ---------
    ~>dnf list installed | grep qtwebengine
    qt5-qtwebengine.x86_64 5.11.1-4.fc28 @updates
    ---------

    Looking again at the log, the culprit seems to be:
    -----------
    kmail: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed.
    Received signal 6
    #0 0x7fc3e21bea2e <unknown>
    #1 0x7fc3e21beb40 <unknown>
    #2 0x7fc3e21bf177 <unknown>
    #3 0x7fc3ee0c4f30 <unknown>
    #4 0x7fc3ee0c4eab __GI_raise
    #5 0x7fc3ee0af5b9 __GI_abort
    #6 0x7fc3ee0af491 __assert_fail_base.cold.0
    #7 0x7fc3ee0bd612 __GI___assert_fail
    #8 0x7fc3b8fcecd7 nouveau_pushbuf_data
    #9 0x7fc3b8fcec37 nouveau_pushbuf_data
    ...
    ------------
    If the problem is with Nouveau, I could try to install the nVidia driver from RPMFusion...
    What do you think?
    Rudi Gaelzer
    Registered Linux user # 153741

  8. #8
    Join Date
    Feb 2005
    Location
    London, UK
    Posts
    734
    Windows 7 Chrome 69.0.3497.100

    Re: Kmail acting up (again)...

    See comment 3 on this one re: copr: https://bugzilla.redhat.com/show_bug.cgi?id=1485203

  9. #9
    Join Date
    Oct 2005
    Location
    Rio Grande do Sul, Brazil
    Posts
    185
    Linux (Fedora) Firefox 62.0

    Re: Kmail acting up (again)...

    Quote Originally Posted by HaydnH
    See comment 3 on this one re: copr: https://bugzilla.redhat.com/show_bug.cgi?id=1485203
    I noticed that comment. I'm still looking for alternatives before I have to resort to installing updates from other repos.
    BTW, I guess I found exactly the same bug already reported at bugs.kde.org:
    https://bugs.kde.org/show_bug.cgi?id=381955
    Rudi Gaelzer
    Registered Linux user # 153741

  10. #10
    Join Date
    Oct 2005
    Location
    Rio Grande do Sul, Brazil
    Posts
    185
    Linux (Fedora) Firefox 62.0

    Re: Kmail acting up (again)...

    So, as was mentioned in other threads, I decided to install and use nVidia's driver.
    Been doing that for some days already and kmail has been behaving.
    I conclude that the ultimate cause for this problem must be indeed some bug with Nouveau.
    Rudi Gaelzer
    Registered Linux user # 153741

Similar Threads

  1. KMail filter acting very strange
    By CrazyCaver in forum Using Fedora
    Replies: 1
    Last Post: 28th August 2014, 12:12 PM
  2. gnome 3 acting very odd
    By thh420 in forum Using Fedora
    Replies: 5
    Last Post: 31st August 2011, 02:33 AM
  3. Pirtu (YUM?) acting up.
    By Thetargos in forum Using Fedora
    Replies: 6
    Last Post: 1st July 2007, 10:15 AM
  4. saslauthd acting up!
    By SatelliteX in forum Servers & Networking
    Replies: 0
    Last Post: 14th December 2006, 04:57 AM
  5. yum is acting up
    By VStrider in forum Using Fedora
    Replies: 4
    Last Post: 13th April 2005, 03:21 AM

Posting Permissions

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