Guayadeque crashing gnome shell
  • This is something that is happening for a while. Actually from the moment I started to use gnome shell but I was always thinking that it is for some other reason and that the next version of gnome will fix that. But that never happened. I've been trying with different themes, without all extension and nothing helped. Each time the quayadeque is running the crash will occur at some point. And now after 3 weeks of not using quayadeque because I was travelling and I never listen anything on my laptop I didn't have a single crash of gnome shell. But in last two days since I'm at home again I had a couple of them already. And now I'm sure that guayadeque is causing this. But the problem is that doing backtrace doesn't help because quayadeque continues to run normally and there's no error of any kind. At some point before I had a song that would cause this every single time I started it. But still, guayadeque itself was running normally, the song was playing and quayadeque did add another on the playlist and backtrace was useless. Only the shell was chrased.
    So what to do? Where should I look for some log files or something that could help to determine the cause of this behaviour.
  • I have been using Gnome Shell and Guayadeque together since the first release of Gnome 3.2 and I really have never encountered any crashing that was related to Guayadeque, it is normally caused by an extension, but if you are experiencing different results perhaps you could try one of the following.

    The fastest route here could be number 3, updating Guayadeque. You said you were trying to run a backtrace, did you run it after running guayadeque from terminal like so: gdb guayadeque, run, bt
    1. Update to the latest Gnome Shell available for you. For me the latest is 3.2.2.1 which I believe was patched due to faults in the original 3.2. The newest available for some is 3.4.* but I haven't tested it out with Guayadeque so I personally don't know.

    2. Make sure you have disabled ALL extensions first, that means everything, sometimes certain extensions work fine on their own, but have different reactions to running programs or the window manager itself.

    3. Try updating Guyadeque, which version are you using now? Perhaps you should install and run the debug version from svn using the instructions here:
    http://guayadeque.org/forums/index.php?p=/page/installing#InstallSVN

    For debug you just follow the note from the svn page: ( Note: If you want to build a debug version instead of run ./build you need to run ./buildd )


    Lets say you ran Guayadeque for 1 hour, and the crashes started happening. Does it restart the shell, or does it crash completely to where you have to either find a way to restart it yourself, or kill x with ctrl+alt+backspace? How often do you think the crashes occur in that 1 hour period, like, how many crashes?
  • 1. Gnome shell is the latest stable version 3.4.1. But It was the same since 3.2.

    2. I tried that. Not just disabling them, but removing all of them. Didn't help.

    3. Well, I updated to svn 1819 today but I wasn't using it since. Anyway, I'm using svn version all the time and I know how to do a backtrace but the problem is that even after shell crashes guayadeque continues to function as expected so there's nothing to do.

    Shell is the only thing that crash, I end up with only one workspace and all the windows are gone. The programs are still there, running but I can't move them or anything. I can only close them through their menu or with keyboard shortcuts. And all I can do is to kill X.
    And it doesn't happen after certain time of playing but randomly. Like I said, once I had a song that caused that every time. But still, guayadeque was playing and backtrace was of no use. And the reason why I think that this is somehow related to guayadeque is because in 3 weeks without using guayadeque I didn't have a single crash. And now in 2 days it happened 3 or 4 times already. And since I still have apport, it tells me that gnome shell is crashed but it can't send that report anywhere and I don't know what to look in it. Is there any log file created with apport that I could attach here or something?
  • I dont know about apport, but. If you could kindly post everything that happens when you try to run a backtrace, the log of running from gdb>guayadeque, or the log of just running guayadeque from terminal, maybe there will be something in that log that will help.

    To be able to restore Gnome Shell after a crash of this nature you can follow these instructions I posted a few months back here:

    http://askubuntu.com/questions/102118/how-to-restart-gnome-shell-after-a-crash-short-of-killing-x/104324#104324

    This will give you back gnome shell and the ability to retrieve any logs, like the scroll back of gdb/terminal and maybe apport even.
  • well, I know about that but as I said, it's not the guayadeque that crash but gnome shell. And to restart shell this way I have to close quayadeque first. As long as it is running restarting shell with terminal doesn't do much because it crashes again instantly. And after quitting guayadeque via menu and typing "bt" in terminal all I get is "no stack".
  • if its gnome shell who crash why dont you make a backtrace of gnome shell running gnome shell from gdb ?
  • well, I tried that. But after restarting shell in a way mention above I get " no stack". The only thing that indicates that gome shell is crashed is that apport window that pops up.
    Meanwhile I found one album that cause this behaviour each and every time. I'll upload it somewhere later so that someone else can try with it.
  • If it crashes again after restarting with terminal, in terminal there will be a huge log from running gnome-shell, and you will also be able to restart again from terminal in most cases.

    In any case, after it crashes from terminal you need to close guayadeque, and paste the log from the terminal that you ran gnome-shell in. That was the whole point of running gnome-shell from terminal.

    Do this: Close guayadeque, open terminal and run gnome-shell --replace then start guayadeque. As soon as gnome-shell crashes, close guayadeque, restart shell from in new tab in terminal or a new terminal, and post the log of the old terminal where it crashed from.
  • Edited above post.
  • OK, I just realised something and I'm sure that I did try it before but.........
    Anyway, one extension is causing this. It's media player indicator extension. I can live without it so it's not a big deal.
    But still, why does this happening with only certain songs? When I realised that some songs (all from the same album) causing crash I deleted that album and downloaded another copy and I still have the same behaviour. OK, maybe it was the same copy but with a different name. And I did edit all the tags with easy tag and all my albums are edited in a same way. I don't see anything different in those song from all the others.

    THX for bearing with me.

    @ anonbeat: I would like to report this to extension author, but do you have any idea what triggers this and why with only some songs?
  • If you can send me link to the album I may try it here when I have some time. You can email me to anonbeat at gmail dot com

  • I've finally nailed it. :)
    The problem was cover actually. Cover.jpeg was very large some 3... x 2... pixels. It was not a problem for guayadeque but since the extension also shows cover it was the problem for extension.

    I hope this is it, the real reason. I don't have time now for some further testing but I'll do it tomorrow. I'll enlarge some covers and try to play song from that album. And I will post back the results.

    THX for help guys.
  • You should post a bug report @ the author as well so perhaps they can fix the extension. If it's the one from e.g.o you can save time by posting the bug report to their github:

    https://github.com/eonpatapon/gnome-shell-extensions-mediaplayer/issues
  • Im glad you tracked down the problem

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In with Google Sign In with OpenID

In this Discussion