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

Thread: Plasma crashses - cannot connect to X

  1. #1

    Default Plasma crashses - cannot connect to X

    Hello there,

    still continue to experience major problems here in Leap 15.
    On battery (so far this has happened only while on battery) with me working in Firefox, Plasma crashed all of the sudden. At least, that's what I assume, as I notice that the taskbar is gone.
    Upon opening a tty to try restarting it I get a

    Could not connect to any X display
    message.

    Here is the corresponding log file: https://1drv.ms/u/s!AlcQ3ZGfWrfqgZ5EBTF2xC5ymeRP9w
    Just download and open it in kate. It's a simple text file.

    Thanks.

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    19,883
    Blog Entries
    1

    Default Re: Plasma crashses - cannot connect to X

    Quote Originally Posted by SF6 View Post
    Hello there,

    still continue to experience major problems here in Leap 15.
    On battery (so far this has happened only while on battery) with me working in Firefox, Plasma crashed all of the sudden.
    Upon opening a tty to try restarting it I get a



    message.

    Here is the corresponding log file: https://1drv.ms/u/s!AlcQ3ZGfWrfqgZ5EBTF2xC5ymeRP9w
    Just download and open it in kate. It's a simple text file.

    Thanks.
    It's preferable to upload such files to https://susepaste.org/ or https://pastebin.com/, than make users download files for inspection. With the susepaste site, there is the associated utility that makes uploading simple eg
    Code:
    dean@linux-kgxs:~> susepaste -e 60  /var/log/Xorg.0.log
    Pasted as:
       http://susepaste.org/98393396
       http://paste.opensuse.org/98393396
    Link is also in your clipboard.
    dean@linux-kgxs:~>
    The -e option specifies how long the paste will be stored on the server (in seconds). Normally a few months or perhaps a year (604800) might be appropriate.
    openSUSE Leap 15.0; KDE Plasma 5

  3. #3

    Default Re: Plasma crashses - cannot connect to X

    I tried susepaste but it gave me a 404 error.
    However, the command line works:

    http://susepaste.org/15100717

    EDIT: Maybe not, still 404.

    See pastebin:

    https://pastebin.com/JDhC0t8J

  4. #4

    Default Happened again - Firefox crashed first then Plasma - XFS errors?

    It happened again. First Firefox crashed, then at the same time basically Plasma. All I could to was issuing a reboot command.

    See log: http://susepaste.org/34197639

    It happened at 15:10.
    What's strange, that it now also throws out XFS error messages.

    Help would be much appreciated.

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    19,883
    Blog Entries
    1

    Default Re: Happened again - Firefox crashed first then Plasma - XFS errors?

    Code:
    1. 15:10:01.302955+09:00 computer kernel: [64498.762037] XFS (dm-3): Metadata corruption detected at xfs_inode_buf_verify+0x72/0xf0 [xfs], xfs_inode block 0xe45e820
    2. 15:10:01.302976+09:00 computer kernel: [64498.762038] XFS (dm-3): Unmount and run xfs_repair
    3. 15:10:01.302979+09:00 computer kernel: [64498.762039] XFS (dm-3): First 64 bytes of corrupted metadata buffer:
    4. 15:10:01.302981+09:00 computer kernel: [64498.762041] ffff8801b9d73000: 49 4e 00 00 03 02 00 00 00 00 03 e8 00 00 00 64 IN.............d
    5. 15:10:01.302983+09:00 computer kernel: [64498.762042] ffff8801b9d73010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    6. 15:10:01.302984+09:00 computer kernel: [64498.762044] ffff8801b9d73020: 5b c0 23 3d 05 02 65 44 5b c0 23 3d 15 ef e4 4e [.#=..eD[.#=...N
    7. 15:10:01.302985+09:00 computer kernel: [64498.762045] ffff8801b9d73030: 5b c0 2a ab 19 0a 6e 62 00 00 00 00 00 00 00 00 [.*...nb........
    8. 15:10:01.302986+09:00 computer kernel: [64498.762076] XFS (dm-3): Metadata corruption detected at xfs_inode_buf_verify+0x72/0xf0 [xfs], xfs_inode block 0xe45e820
    9. 15:10:01.302988+09:00 computer kernel: [64498.762076] XFS (dm-3): Unmount and run xfs_repair
    10. 15:10:01.302989+09:00 computer kernel: [64498.762077] XFS (dm-3): First 64 bytes of corrupted metadata buffer:
    Your system looks to be suffering XFS filesystem corruption. Make sure any important data is backed up before attempting to repair it.

    http://xfs.org/docs/xfsdocs-xml-dev/...fs-repair.html
    https://www.thegeekdiary.com/running...s-filesystems/
    https://docs.fedoraproject.org/en-US...xfsrepair.html
    openSUSE Leap 15.0; KDE Plasma 5

  6. #6

    Default Re: Plasma crashses - cannot connect to X

    I don't quite get this.
    Let me show you why:

    1. The SSD is only half a year old (MX500, latest firmware).
    2. I have installed Leap 15 just three weeks ago using its default settings (BTRFS / XFS /home, however with full disk encryption/LVM),
    3. Plasma crashes - cannot connect to X -> So I reboot issueing a reboot command (and for some reason this has only happened on battery yet)

    And now the file system got corrupted? Why?
    The same crash happened before with the exact same symptoms, except the log didn't have and XFS errors:

    1. Crash
    http://susepaste.org/36282386
    2. Crash
    http://susepaste.org/26418765

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    19,883
    Blog Entries
    1

    Default Re: Plasma crashses - cannot connect to X

    Try the following...create a new user (via YaST) and then log in to the new user account, and see how that goes.

    This might also be worth a shot (for existing user)...
    Code:
    kbuildsycoca5 --noincremental 2> /dev/null
    Code:
    rm -fr ~/.cache/
    Restart the X-server with CTRL+ALT+Backspace.
    openSUSE Leap 15.0; KDE Plasma 5

  8. #8

    Default Re: Plasma crashses - cannot connect to X

    Hi,

    thanks for your help. I will try that.

    For now, it has happened a third time. This time, just a couple of minutes after I had booted into the system on battery.
    Right now I'm using the machine without any issue connected to AC.

    I observed Plasma gone at around 14:49~14:50. Here's the log.

    3. Crash
    http://susepaste.org/32740458



  9. #9
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,414

    Default Re: Plasma crashses - cannot connect to X

    That log has more than a dozen instances of failed, including one BTRFS related with a segfault. Maybe this has a hardware problem root. What happens if you open an IceWM session instead of Plasma?
    Reg. Linux User #211409 *** multibooting since 1992
    Primary: 42.3,TW,15.0 & 13.1 on Haswell w/ RAID
    Secondary: eComStation (OS/2)&42.3 on 965P/Radeon
    Tertiary: TW,15.0,42.3,Fedora,Debian,more on Kaby Lake,Q45,Q43,G41,G3X,965G,Cedar,Caicos,Oland,GT218&&&

  10. #10

    Default Re: Plasma crashses - cannot connect to X

    So I tried one of your suggestions and did

    Code:
    kbuildsycoca5 --noincremental 2> /dev/null
    and deleted the cache directory

    Code:
    rm -fr ~/.cache/
    However, it happened again just recently:

    4. Crash at around 17:12~17.13.
    http://susepaste.org/17369202

    I will now create a new user and see if it happens again.

Page 1 of 2 12 LastLast

Posting Permissions

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