After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 701248 - Gnome-shell crashes every 10 minutes
Gnome-shell crashes every 10 minutes
Status: RESOLVED INCOMPLETE
Product: gnome-shell
Classification: Core
Component: drivers
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-05-30 07:45 UTC by cx42net
Modified: 2017-03-08 14:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description cx42net 2013-05-30 07:45:37 UTC
It's been a while since gnome-shell crash when I bring back my computer from screen shutdown to active.

I have the "Aww snap" message, and I have to restart the session.

But recently, this happens very too often, without any clear action from my part (except like surfing the web), and it's getting very annoying.

I tried to upload the bug report but it can't send it, indicating an error with RPC ...

In dmesg, the only things that pops out is this line :

> [  307.909337] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! 

I have a AMD Phenom X6, 8gb ram, SSD, two screen (in dual mode).
Comment 1 cx42net 2013-05-30 08:42:27 UTC
The RPC error :

--- Running report_Bugzilla ---
Connexion à Bugzilla sur https://bugzilla.gnome.org
Vérification des duplications
fatal: RPC failed at server.  quicksearch is not a valid parameter for the Bugzilla::Bug::match
function.
('report_Bugzilla' exited with 1)
Comment 2 Rui Matos 2013-05-30 09:26:39 UTC
(In reply to comment #0)
> In dmesg, the only things that pops out is this line :
> 
> > [  307.909337] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12! 
> 
> I have a AMD Phenom X6, 8gb ram, SSD, two screen (in dual mode).

Looks like a driver issue. Can you try either an older or a newer kernel?
Comment 3 cx42net 2013-05-30 12:04:09 UTC
I'm using 

> Linux localhost.localdomain 3.9.4-200.fc18.x86_64 #1 SMP Fri May 24 20:10:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I can go back up to the last two kernels (that's the auto configuration of my Fedora) but this bugs is present from a greater moment (I opened a similar ticket about a month ago with all the dumps (uploaded manually from Bug Report) but I couldn't find it now.)
Comment 4 Rui Matos 2013-05-30 12:06:36 UTC
You can get older kernels for Fedora from

http://koji.fedoraproject.org/koji/packageinfo?packageID=8
Comment 5 André Klapper 2013-05-30 15:09:32 UTC
[Offtopic for this bug report]

(In reply to comment #1)
> The RPC error :

RPC error of what? And "Upload the bug report" with what tool? You likely want to file a bug about Fedora's ABRT tool then.
Comment 6 cx42net 2013-05-31 07:19:36 UTC
So, an update, I'm trying the kernel 

> Linux localhost.localdomain 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

And I also got this crash.

A look in dmesg shows the same error :

> [63980.301768] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -12!

(before this, it's not related because there is a timelapse of 50000, and after, it's SELinux talks, so I guess it's not relevant)

Should I look in an older version of the kernel ?
Comment 7 cx42net 2013-05-31 07:32:36 UTC
Well, it clearly seems to be a driver located problem. I'm gonna try to install the propriatery driver and update it the result here (in case someone else is having the same trouble), but now I don't believe it's related to Gnome.

(So if you prefer to close this before I give my update, go ahead ;)).

Thanks for your help!
Comment 8 cx42net 2013-05-31 08:00:45 UTC
Well, I can't try the propriatery driver because it's currently not supported by Fedora (black screen) ...
Comment 9 Milan Bouchet-Valat 2013-05-31 09:31:01 UTC
So please report this to bugzilla.kernel.org. Since you are using a recent kernel, they will be interested in fixing this. But please test whether this happens without dual screen too.
Comment 10 André Klapper 2017-03-08 01:04:12 UTC
cx42net: Is this still an issue nowadays on GNOME 3.22 or 3.20?
Comment 11 cx42net 2017-03-08 09:15:32 UTC
Hi André,

well, it's been a long time and I've changed my hardware since, but as far as I remember, I didn't had this problem for a long time, so yeah I believe you can close it (at least for me) :)
Comment 12 André Klapper 2017-03-08 14:26:01 UTC
Thanks! :) Closing as incomplete....