Results 1 to 10 of 10

Thread: kmail5 sementation fault crash

  1. #1
    Join Date
    Jun 2008
    Location
    London
    Posts
    172

    Default kmail5 sementation fault crash

    A two user system, kmail fails on both accounts after a Tumbleweed update, via "Software Updates" in user account system tray

    Code:
    linux-6dbk:~ # cat /etc/os-release
    NAME="openSUSE Tumbleweed"
    # VERSION="20161003"
    ID=opensuse
    ID_LIKE="suse"
    VERSION_ID="20161003"
    PRETTY_NAME="openSUSE Tumbleweed"
    ANSI_COLOR="0;32"
    CPE_NAME="cpe:/o:opensuse:tumbleweed:20161003"
    BUG_REPORT_URL="https://bugs.opensuse.org"
    HOME_URL="https://www.opensuse.org/"
    The underlying mail system seems to be working, mail is retrieved and occasionally it is possible to send and receive and email but kmail persistently crashes on both accounts.

    The crash report couldn't generate anything useful

    A slightly later version (since downgraded) from KDE:applications returns the same problem

    running kmail from command line produces this

    Code:
    1005/192735:ERROR:browser_main_loop.cc(217)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.
     void AdblockManager::reloadConfig() false    AdBlock::AdblockManager(0x1e3f580)
    this does not work on a KActionCollection containing actions!
    org.kde.akonadi.ETM: GEN true false false
    org.kde.akonadi.ETM: collection: QVector()
    org.kde.akonadi.ETM: 
    org.kde.akonadi.ETM: Subtree:  4 QSet(55, 54, 53, 52, 59, 58, 57, 56, 63, 62, 61, 60, 35, 34, 33, 32, 39, 38, 37, 36, 43, 42, 41, 40, 47, 46, 44, 19, 18, 17, 16, 23, 22, 21, 20, 27, 26, 25, 24, 31, 30, 29, 28, 7, 6, 4, 11, 15, 14, 13, 12, 112, 119, 118, 117, 116, 123, 122, 121, 120, 99, 98, 97, 96, 103, 102, 101, 100, 105, 104, 111, 83, 82, 81, 80, 87, 86, 85, 84, 91, 90, 89, 88, 95, 94, 93, 92, 67, 66, 65, 64, 71, 70, 69, 68, 75, 74, 73, 72, 79, 78, 77, 76, 50, 49, 48)
    org.kde.akonadi.ETM: collection: "Alex"
    org.kde.akonadi.ETM: Fetch job took  273 msec
    org.kde.akonadi.ETM: was collection fetch job: collections: 106
    org.kde.akonadi.ETM: first fetched collection: "Local Folders"
    org.kde.akonadi.ETM: collection: "Home Start"
    org.kde.akonadi.ETM: collection: QVector()
    org.kde.akonadi.ETM: Fetch job took  342 msec
    org.kde.akonadi.ETM: was collection fetch job: collections: 6
    org.kde.akonadi.ETM: first fetched collection: "Search"
    org.kde.akonadi.ETM: Fetch job took  247 msec
    org.kde.akonadi.ETM: was item fetch job: items: 26
    org.kde.akonadi.ETM: Fetch job took  231 msec
    org.kde.akonadi.ETM: was item fetch job: items: 562
    org.kde.akonadi.ETM: Fetch job took  209 msec
    org.kde.akonadi.ETM: was collection fetch job: collections: 0
    org.kde.akonadi.ETM: collection: "inbox"
    org.kde.akonadi.ETM: Fetch job took  74 msec
    org.kde.akonadi.ETM: was item fetch job: items: 103
    nouveau: kernel rejected pushbuf: No such file or directory
    nouveau: ch15: krec 0 pushes 0 bufs 1 relocs 0
    nouveau: ch15: buf 00000000 00000002 00000004 00000004 00000000
    nouveau: kernel rejected pushbuf: No such file or directory
    nouveau: ch15: krec 0 pushes 0 bufs 2 relocs 0
    nouveau: ch15: buf 00000000 00000002 00000004 00000004 00000000
    nouveau: ch15: buf 00000001 00000006 00000004 00000000 00000004
    nouveau: kernel rejected pushbuf: No such file or directory
    nouveau: ch15: krec 0 pushes 0 bufs 1 relocs 0
    nouveau: ch15: buf 00000000 00000002 00000004 00000004 00000000
    org.kde.akonadi.ETM: collection: "Addison Singers"
    org.kde.akonadi.ETM: Fetch job took  70 msec
    org.kde.akonadi.ETM: was item fetch job: items: 3
    js: Uncaught ReferenceError: qt is not defined
    js: Uncaught ReferenceError: qt is not defined
    js: Uncaught ReferenceError: qt is not defined
    *** KMail got signal 11 (Exiting)
    *** Dead letters dumped.
    QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
    KCrash: Application 'kmail' crashing...
    KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
    sock_file=/run/user/1000/kdeinit5__0
    [1005/192759:ERROR:gles2_cmd_decoder.cc(2109)] [.CommandBufferContext.RenderWorker-0x1a0dcd0]GL ERROR :GL_OUT_OF_MEMORY : ScopedTextureBinder::dtor: <- error from previous GL command
    [1005/192759:ERROR:gles2_cmd_decoder.cc(4471)] Error: 5 for Command kCopySubTextureCHROMIUM
    [1005/192759:ERROR:gles2_cmd_decoder.cc(3579)]   GLES2DecoderImpl: Trying to make lost context current.
    [1005/192759:ERROR:gles2_cmd_decoder.cc(3579)]   GLES2DecoderImpl: Trying to make lost context current.
    [1005/192759:FATAL:scoped_file.cc(30)] Check failed: 0 == IGNORE_EINTR(close(fd)). : Bad file descriptor
    #0 0x7f25aa0c7b5e base::debug::StackTrace::StackTrace()
    #1 0x7f25aa0de7fe logging::LogMessage::~LogMessage()
    #2 0x7f25aa0dfa0c logging::ErrnoLogMessage::~ErrnoLogMessage()
    #3 0x7f25aa0da571 base::internal::ScopedFDCloseTraits::Free()
    #4 0x7f25a9d6b9fb IPC::internal::PlatformFileAttachment::~PlatformFileAttachment()
    #5 0x7f25a9d6ba19 IPC::internal::PlatformFileAttachment::~PlatformFileAttachment()
    #6 0x7f25a9d6989f IPC::MessageAttachmentSet::~MessageAttachmentSet()
    #7 0x7f25a9d68d68 IPC::Message::~Message()
    #8 0x7f25a99bf6f2 content::GpuChannelMessageQueue::MessageProcessed()
    #9 0x7f25a99c012d content::GpuChannel::HandleMessage()
    #10 0x7f25aa138989 base::debug::TaskAnnotator::RunTask()
    #11 0x7f25aa0e4d89 base::MessageLoop::RunTask()
    #12 0x7f25aa0e5969 base::MessageLoop::DeferOrRunPendingTask()
    #13 0x7f25aa0e5e22 base::MessageLoop::DoWork()
    #14 0x7f25aa0e7c89 base::MessagePumpDefault::Run()
    #15 0x7f25aa0f968a base::RunLoop::Run()
    #16 0x7f25aa0e4165 base::MessageLoop::Run()
    #17 0x7f25aa1113ea base::Thread::ThreadMain()
    #18 0x7f25aa10dab7 base::(anonymous namespace)::ThreadFunc()
    #19 0x7f25b4201454 start_thread
    #20 0x7f25be3743ff __GI___clone
    
    Unable to start Dr. Konqi
    Any thoughts including how to roll back kmail to an earlier version appreciated

  2. #2
    Join Date
    Jun 2008
    Location
    London
    Posts
    172

    Default Re: kmail5 segmentation fault crash

    another thread with a similar issue reports (contents of mail) success by installing libqt5-qtwebengine-5.7.0-4.1 - I have this installed

    the HTML issue seems to be the same - kmail is stable provided one does not try to read HTML formatted mail

    de-installing nouveau stabilizes kmail but unfortunately renders system unusable for all practical purposes

  3. #3
    Join Date
    Jun 2008
    Location
    London
    Posts
    172

    Default Re: kmail5 sementation fault crash

    installing the nvidia driver solved the usability problem but not the nouveau problem

  4. #4
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,861
    Blog Entries
    14

    Default Re: kmail5 sementation fault crash

    Quote Originally Posted by gerrygavigan View Post
    installing the nvidia driver solved the usability problem but not the nouveau problem
    It's either nouveau or the nvidia driver. There currently are two issues: the one with kmail not showing html mail, which is fixed in the package mentioned that was released through the TW Update repo, the other one being qtwebengine not playing nicely with the nouveau driver. Once you want to use the nvidia driver, you have to blacklist the nouveau driver so that it doesn't get loaded.
    A thing that could ( maybe ) cause issues now that you have the nvidia driver installed, is that the nvidia driver is actually installed, but not loaded because nouveau is not blacklisted, or still in initrd.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  5. #5
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,861
    Blog Entries
    14

    Default Re: kmail5 sementation fault crash

    To add: what you describe in your first post, has been fixed with the new qt5-qtwebengine package. These crashes are not related to nvidia.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  6. #6
    Join Date
    Jun 2008
    Location
    London
    Posts
    172

    Default Re: kmail5 sementation fault crash

    Quote Originally Posted by Knurpht View Post
    A thing that could ( maybe ) cause issues now that you have the nvidia driver installed, is that the nvidia driver is actually installed, but not loaded because nouveau is not blacklisted, or still in initrd.
    Thank you and sorry for lack of clarity.

    To be more clear, the system is now working. The problem was the nouveau driver, identification assisted by the discussion on the kmail body thread. However installing nvidia (a separate PITA) sidestepped the nouveau problem, which I could not solve, even by trying out versions from SUSE nouveau developers' repositories

  7. #7
    Join Date
    Jun 2008
    Location
    London
    Posts
    172

    Default Re: kmail5 sementation fault crash

    Quote Originally Posted by Knurpht View Post
    To add: what you describe in your first post, has been fixed with the new qt5-qtwebengine package. These crashes are not related to nvidia.
    The new version of libqt5-qtwebengine (5.7.0-4.1) made no difference to my nouveau problem, installing nvidia sidestepped it

  8. #8

    Default Re: kmail5 sementation fault crash

    Quote Originally Posted by gerrygavigan View Post
    The new version of libqt5-qtwebengine (5.7.0-4.1) made no difference to my nouveau problem, installing nvidia sidestepped it
    There are known problems with running QtWebengine (what kdepim5 uses for the message display) on nouveau, because of problems/limitations in nouveau.

    See here:
    http://lists.opensuse.org/opensuse-f.../msg00187.html

    Installing the nvidia driver should fix it, or setting the environment variable "LIBGL_ALWAYS_SOFTWARE=1" (see http://www.mesa3d.org/envvars.html).

    E.g. run ""LIBGL_ALWAYS_SOFTWARE=1 qupzilla"
    (setting it globally is probably not a good idea, as that will make all
    applications, including Plasma the desktop, to use software OpenGL rendering
    then)
    You should exchange "qupzilla" with kmail or kontact of course.
    Last edited by wolfi323; 06-Oct-2016 at 12:06.

  9. #9
    Join Date
    Jun 2008
    Location
    London
    Posts
    172

    Default Re: kmail5 sementation fault crash

    Quote Originally Posted by wolfi323 View Post
    There are known problems with running QtWebengine [...] on nouveau, because of problems/limitations in nouveau.
    That's a bit of a shame. I've been using nvidia since 1998 as much habit as anything else.

    When I installed Tumbleweed as an upgrade from 12.1 on this system (first built in 2007) about six months ago I was pleased to see that nouveau seemed to be good enough. Using nVidia sort of weakens the value of Tumbleweed.

    No doubt it will get there.

  10. #10

    Default Re: kmail5 sementation fault crash

    Quote Originally Posted by gerrygavigan View Post
    No doubt it will get there.
    Well, blame NVidia for that.

    Although, as mentioned on the opensuse-factory mailinglist today, WIP patches that should fix (or at least make it more unlikely) this particular problem have been backported to Leap 42.2.

    I'm pretty sure that this will end up in Tumbleweed too at some time.
    You may want to add a comment to https://bugzilla.opensuse.org/show_bug.cgi?id=997171 though to make sure or speed it up.
    Last edited by wolfi323; 06-Oct-2016 at 12:47.

Posting Permissions

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