Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: konsole segmentation fault

  1. #1
    Join Date
    Dec 2015
    Location
    Italy
    Posts
    30

    Default konsole segmentation fault

    It happens every time i quit konsole (either via button or "exit" command). Does anybody have a solution?

    Thanks,

    Dan

    Here is developer info:

    Code:
    Application: konsole (konsole), signal: Segmentation fault
    
    Using host libthread_db library "/lib64/libthread_db.so.1".
    
     [KCrash Handler]
     #6  0x00007f26e0abb023 in  () at /usr/lib64/libQt5DBus.so.5
     #7  0x00007f26e0ab12c7 in  () at /usr/lib64/libQt5DBus.so.5
     #8  0x00007f26e0ab1529 in  () at /usr/lib64/libQt5DBus.so.5
     #9  0x00007f26e0aa45e5 in  () at /usr/lib64/libQt5DBus.so.5
     #10 0x00007f26e0aa4699 in  () at /usr/lib64/libQt5DBus.so.5
     #11 0x00007f26e624fb39 in __run_exit_handlers () at /lib64/libc.so.6
     #12 0x00007f26e624fb85 in  () at /lib64/libc.so.6
     #13 0x00007f26e6239b2c in __libc_start_main () at /lib64/libc.so.6
     #14 0x00000000004007ee in _start ()
    La realtà è irriducibile al significato. - Luigi Pirandello

  2. #2

    Default Re: konsole segmentation fault

    Quote Originally Posted by danfloyd111 View Post
    It happens every time i quit konsole (either via button or "exit" command). Does anybody have a solution?
    Your backtrace doesn't tell anything, you'd need to install the corresponding debuginfo packages (libQt5DBus5-debuginfo at least, as that's where the crash is).

    Btw, this doesn't happen here.

    Does it crash if you just open konsole and close it again immediately?
    Or are you doing anything special to cause the crash, like opening several tabs e.g.
    If there's a command running when you close it, konsole shows a warning dialog, maybe it's related to that?

    And, are you using the nvidia driver?
    There are known problems when closing konsole that are caused by nvidia.

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

    Default Re: konsole segmentation fault

    First, have you ever updated your system?
    If not, run this at least once after your original install
    Code:
    zypper up
    If that doesn't fix your problem,
    You can try "force re-installing" Konsole which would re-install its original configuration.
    Code:
    zypper in -f Konsole
    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
    Feb 2010
    Location
    Germany
    Posts
    2,611

    Default Re: konsole segmentation fault

    Quote Originally Posted by danfloyd111 View Post
    It happens every time i quit konsole (either via button or "exit" command). Does anybody have a solution?
    Up until now I haven't had any Konsole issues but, I do experience intermittent Qt5 crashes with Leap 42.1 and, I'm submitting them to the KDE folks.
    Currently, my list of installed debuginfo packages doesn't support the following object files:
    • /usr/lib64/dri/r600_dri.so
    • /usr/lib64/libglib-2.0.so.0
    • /usr/lib64/libQt5Qml.so.5
    • /usr/lib64/libQt5Core.so.5
    • /usr/lib64/libQt5Gui.so.5
    • /usr/lib64/libQt5Quick.so.5

    Plus some others where the KCrash Handler was at a total loss:
    Code:
    #42 0x00007f52072afc27 in ()
    #43 0x00007f51d854c110 in ()
    #44 0x00007ffe558b2300 in ()
    #45 0x0003000000000000 in ()
    #46 0x0001000000000001 in ()
    #47 0x0000000002b50340 in ()
    #48 0x00007f508c13c39c in ()
    #49 0x0000000000000001 in ()
    #50 0x0000000000000000 in ()

  5. #5
    Join Date
    Dec 2015
    Location
    Italy
    Posts
    30

    Default Re: konsole segmentation fault

    Does it crash if you just open konsole and close it again immediately?
    Or are you doing anything special to cause the crash, like opening several tabs e.g.
    If there's a command running when you close it, konsole shows a warning dialog, maybe it's related to that?

    And, are you using the nvidia driver?
    Yes, it crash if I just open konsole and close it immediately, I wasn't doing anything special to cause the crash, just a
    Code:
    zypper lp
    in a single tab with no warning dialogs.
    I have an "optimus" laptop with Nvidia discrete card and bumblebee-nvidia drivers installed but I use it very rarely.

    First, have you ever updated your system?
    Searching for updates is the first thing I do when I login

    You can try "force re-installing" Konsole which would re-install its original configuration.
    I will try and let you know,

    thanks to all !
    La realtà è irriducibile al significato. - Luigi Pirandello

  6. #6
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,611

    Default Re: konsole segmentation fault

    Quote Originally Posted by danfloyd111 View Post
    I have an "optimus" laptop with Nvidia discrete card and bumblebee-nvidia drivers installed but I use it very rarely.
    Please take a look at both of these articles: <https://wiki.archlinux.org/index.php/NVIDIA_Optimus> <https://wiki.archlinux.org/index.php/Bumblebee>

    The following in the Bumblebee article may be relevant:
    Installing Bumblebee with Intel/Nouveau
    Warning: This method is deprecated and will most likely not work anymore. Use the nvidia module instead. If you want nouveau, use PRIME.

  7. #7
    Join Date
    Dec 2015
    Location
    Italy
    Posts
    30

    Default Re: konsole segmentation fault

    Quote Originally Posted by dcurtisfra View Post
    Please take a look at both of these articles: <https://wiki.archlinux.org/index.php/NVIDIA_Optimus> <https://wiki.archlinux.org/index.php/Bumblebee>

    The following in the Bumblebee article may be relevant:
    Installing Bumblebee with Intel/Nouveau
    Warning: This method is deprecated and will most likely not work anymore. Use the nvidia module instead. If you want nouveau, use PRIME.
    Thank you, I was aware of that advice when I installed bumblebee then I chose Intel/Nvidia combination. But bumblebee never caused a problem like this one on my machine, Konsole started this strange behaviour just few days ago and I not remeber any "particular" update or action that I performed before of these events.

    I've performed
    Code:
    zypper in -f konsole
    with no result: konsole still crashes on exit.

    Again thank you all (and sorry for my english).

    D.
    La realtà è irriducibile al significato. - Luigi Pirandello

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

    Default Re: konsole segmentation fault

    Quote Originally Posted by danfloyd111 View Post
    Thank you, I was aware of that advice when I installed bumblebee then I chose Intel/Nvidia combination. But bumblebee never caused a problem like this one on my machine, Konsole started this strange behaviour just few days ago and I not remeber any "particular" update or action that I performed before of these events.

    I've performed
    Code:
    zypper in -f konsole
    with no result: konsole still crashes on exit.

    Again thank you all (and sorry for my english).

    D.
    Did you also update your system before re-installing konsole?
    Code:
    zypper up
    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!

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

    Default Re: konsole segmentation fault

    If "zypper up' doesn't work, and assuming this is a problem unique to your system (I can't re-produce your problem),

    You can re-install your system replacing <every> file which does a more thorough job than simply "zypper dup"
    Code:
    zypper dup --replacefiles
    That will take a very long time to run, depending on your network connection and the speed of your disk subsystem.

    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!

  10. #10

    Default Re: konsole segmentation fault

    Quote Originally Posted by dcurtisfra View Post
    Up until now I haven't had any Konsole issues but, I do experience intermittent Qt5 crashes with Leap 42.1 and, I'm submitting them to the KDE folks.
    Currently, my list of installed debuginfo packages doesn't support the following object files:
    • /usr/lib64/dri/r600_dri.so
    Well, it's not so difficult...
    rpm -qf tells you from which package a file comes.
    And the debug symbols are normally in packagename-debuginfo.

    E.g.:
    Code:
    $ rpm -qf /usr/lib64/dri/r600_dri.so
    Mesa-10.3.7-91.18.1.x86_64
    $ zypper se Mesa
    Daten des Repositories laden ...
    Installierte Pakete lesen ...
    
    S | Name                               | Zusammenfassung            | Typ       
    --+------------------------------------+----------------------------+-----------
    i | DirectFB-Mesa                      | Mesa backend of Graphics-> | Paket     
      | DirectFB-Mesa-debuginfo            | Debug information for pa-> | Paket     
    i | Mesa                               | System for rendering int-> | Paket     
      | Mesa                               | System for rendering int-> | Quellpaket
    i | Mesa-32bit                         | System for rendering int-> | Paket     
      | Mesa-debuginfo                     | Debug information for pa-> | Paket     
      | Mesa-debuginfo-32bit               | Debug information for pa-> | Paket     
      | Mesa-debugsource                   | Debug sources for packag-> | Paket     
    ...
    (the -debugsource packages are only necessary to see the actual source code in a debugger)

    The rest:
    • /usr/lib64/libglib-2.0.so.0

    libglib-2_0-0-debuginfo

    • /usr/lib64/libQt5Qml.so.5

    libQtQuick-debuginfo

    • /usr/lib64/libQt5Core.so.5

    libQt5Core5-debuginfo

    • /usr/lib64/libQt5Gui.so.5

    libQt5Gui5-debuginfo

    • /usr/lib64/libQt5Quick.so.5

    libQtQuick5-debuginfo

    If the crash involves r600_dri.so, it's unlikely to be a bug in KDE though I think...
    (and Qt5 is not developed by the KDE folks either)

    Plus some others where the KCrash Handler was at a total loss:
    Code:
    #42 0x00007f52072afc27 in ()
    #43 0x00007f51d854c110 in ()
    #44 0x00007ffe558b2300 in ()
    #45 0x0003000000000000 in ()
    #46 0x0001000000000001 in ()
    #47 0x0000000002b50340 in ()
    #48 0x00007f508c13c39c in ()
    #49 0x0000000000000001 in ()
    #50 0x0000000000000000 in ()
    Looks like some random memory/stack corruption to me...
    Useless though, as it doesn't provide the slightest hint what is crashing where.

    @danfloyd111:
    As you are using intel, try this, it may help:
    https://en.opensuse.org/SDB:Switch_x...o-intel_to_UXA

    It may even be worth a try to uninstall xf86-video-intel and use the generic modesetting driver instead.
    This is reported to be more stable and even faster on some systems (it still uses the intel kernel driver and OpenGL hardware support, basically the only thing missing is 2D acceleration but it uses glamor for that, i.e. OpenGL).
    Last edited by wolfi323; 19-Aug-2016 at 04:12.

Page 1 of 2 12 LastLast

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
  •