Odd Linux bug... Anyone else?

Discussion in 'General Discussion' started by VAX-11/780, Apr 9, 2017.

Thread Status:
Not open for further replies.
  1. VAX-11/780

    VAX-11/780 Avatar

    Messages:
    162
    Likes Received:
    331
    Trophy Points:
    30
    Location:
    Pensacola, Florida, Earth, Dimension C-137
    I'm running Elementary OS (simply a fork of Ubuntu) and seemingly at random when I try to fire up the SotA laucher, it will come up, check for updates, then 1 second later log me out of my OS session! LOL! I haven't got a clue... Anyone else?
     
  2. Alley Oop

    Alley Oop Bug Hunter Bug Moderator

    Messages:
    10,669
    Likes Received:
    16,050
    Trophy Points:
    153
    nope, that one's all yours!
     
  3. Barugon

    Barugon Avatar

    Messages:
    13,319
    Likes Received:
    20,800
    Trophy Points:
    153
    Gender:
    Male
    I've never experienced that one. Sorry.
     
  4. Sentinel2

    Sentinel2 Avatar

    Messages:
    1,027
    Likes Received:
    1,693
    Trophy Points:
    113
    I've run the game with Kubuntu, Ubuntu and Mint. Nothing like that has popped up. sorry ...

    perhaps you can look in your logs and see what's going on. Anything in the secure or syslogs?

    I'm curious why it's getting a signal to logout
     
  5. Damian Killingsworth

    Damian Killingsworth Avatar

    Messages:
    941
    Likes Received:
    1,440
    Trophy Points:
    93
    Location:
    Whyte Roc
    thats a new one!
    check /var/log/syslog for clues?
     
  6. VAX-11/780

    VAX-11/780 Avatar

    Messages:
    162
    Likes Received:
    331
    Trophy Points:
    30
    Location:
    Pensacola, Florida, Earth, Dimension C-137
    Below is the part where it crapped itself. The SotA launcher comes up for a second or two, then the screen salutes me, and I find myself at the login screen. Doesn't look like it's getting a signal to logout, though. Looks more like something is causing the desktop environment to slit its wrists, maybe? It doesn't seem to happen if I open a new virtual desktop and fire the launcher up there.

    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: (gala:5743): Gdk-ERROR **: The program 'gala' received an X Window System error.
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: This probably reflects a bug in the program.
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: The error was 'BadAlloc (insufficient resources for operation)'.
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: (Details: serial 40632 error_code 11 request_code 12 (core protocol) minor_code 0)
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: (Note to programmers: normally, X errors are reported asynchronously;
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: that is, you will receive the error a while after causing it.
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: To debug your program, run it with the GDK_SYNCHRONIZE environment
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: variable to change this behavior. You can then get a meaningful
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: backtrace from your debugger if you break on the gdk_x_error() function.)
    Apr 13 08:28:14 SupremeJerk-PC kernel: [ 4793.745744] traps: gala[5743] trap int3 ip:7fa5d1a23a5b sp:7ffe378df280 error:0
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: gnome-session-binary[5520]: WARNING: Application 'gala.desktop' killed by signal 5
    Apr 13 08:28:14 SupremeJerk-PC gnome-session-binary[5520]: WARNING: Application 'gala.desktop' killed by signal 5
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: (gala:6315): Gdk-ERROR **: The program 'gala' received an X Window System error.
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: This probably reflects a bug in the program.
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: The error was 'BadAlloc (insufficient resources for operation)'.
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: (Details: serial 1693 error_code 11 request_code 12 (core protocol) minor_code 0)
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: (Note to programmers: normally, X errors are reported asynchronously;
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: that is, you will receive the error a while after causing it.
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: To debug your program, run it with the GDK_SYNCHRONIZE environment
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: variable to change this behavior. You can then get a meaningful
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: backtrace from your debugger if you break on the gdk_x_error() function.)
    Apr 13 08:28:14 SupremeJerk-PC kernel: [ 4794.107043] traps: gala[6315] trap int3 ip:7f2534844a5b sp:7ffe78f8b980 error:0
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: (gnome-settings-daemon:5637): GnomeDesktop-WARNING **: Failed to refresh screen configuration after mutter was restarted: GDBus.Error:eek:rg.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: (gnome-settings-daemon:5637): GnomeDesktop-WARNING **: Failed to refresh screen configuration after mutter was restarted: GDBus.Error:eek:rg.freedesktop.DBus.Error.ServiceUnknown: The name :1.63 was not provided by any .service files
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: (gnome-settings-daemon:5637): GnomeDesktop-WARNING **: Failed to refresh screen configuration after mutter was restarted: GDBus.Error:eek:rg.freedesktop.DBus.Error.ServiceUnknown: The name :1.63 was not provided by any .service files
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: gnome-session-binary[5520]: WARNING: Application 'gala.desktop' killed by signal 5
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: gnome-session-binary[5520]: WARNING: App 'gala.desktop' respawning too quickly
    Apr 13 08:28:14 SupremeJerk-PC gnome-session[5520]: gnome-session-binary[5520]: CRITICAL: We failed, but the fail whale is dead. Sorry....
    Apr 13 08:28:14 SupremeJerk-PC gnome-session-binary[5520]: Unrecoverable failure in required component gala.desktop
    Apr 13 08:28:14 SupremeJerk-PC gnome-session-binary[5520]: WARNING: Application 'gala.desktop' killed by signal 5
    Apr 13 08:28:14 SupremeJerk-PC gnome-session-binary[5520]: WARNING: App 'gala.desktop' respawning too quickly
    Apr 13 08:28:14 SupremeJerk-PC gnome-session-binary[5520]: CRITICAL: We failed, but the fail whale is dead. Sorry....
    Apr 13 08:28:15 SupremeJerk-PC gnome-session[5520]: ICE default IO error handler doing an exit(), pid = 5793, errno = 11
    Apr 13 08:28:15 SupremeJerk-PC org.a11y.atspi.Registry[5626]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
    Apr 13 08:28:15 SupremeJerk-PC org.a11y.atspi.Registry[5626]: after 1221 requests (1221 known processed) with 0 events remaining.
     
    Last edited: Apr 13, 2017
  7. Sentinel2

    Sentinel2 Avatar

    Messages:
    1,027
    Likes Received:
    1,693
    Trophy Points:
    113
    I get the impression the desktop actually crashed and restarted again. Also, BadAlloc was recorded with insufficient resources. I'm curious what hardware you are running on. How much memory and so on. Maybe you need more memory. Or your memory is too fragmented?

    Just some thoughts...
     
  8. VAX-11/780

    VAX-11/780 Avatar

    Messages:
    162
    Likes Received:
    331
    Trophy Points:
    30
    Location:
    Pensacola, Florida, Earth, Dimension C-137
    Elementary OS, Loki 0.4
    MSI B85M-E45
    Intel i7-4790K @ 4GHz
    G.Skill 16GB DDR3 RAM @ 1600MHz
    EVGA NVIDIA GTX 970 w/ 4GB RAM
    Corsair Force-LE 960GB SSD
    Seagate ST2000DM001-1ER164 2TB HDD
    Corsair RM750i PSU

    I also edited my other response to say that I don't seem to experience the desktop crash when I open a new virtual desktop and then open the SotA launcher from there.
     
  9. Barugon

    Barugon Avatar

    Messages:
    13,319
    Likes Received:
    20,800
    Trophy Points:
    153
    Gender:
    Male
    "SupremeJerk-PC"... LOL.
     
    Three Eighty-Six likes this.
Thread Status:
Not open for further replies.