Switchboard stopped working

Bug #1033270 reported by sonay
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Switchboard
Won't Fix
Undecided
Unassigned

Bug Description

It doesn't start anymore. When started from the terminal, the problem persists with the following log:

[_LOG_LEVEL_INFO 22:16:58.849515] switchboard-app.vala:501: Welcome to System Settings
[_LOG_LEVEL_INFO 22:16:58.849594] switchboard-app.vala:502: Version: 0.9
[_LOG_LEVEL_INFO 22:16:58.849656] switchboard-app.vala:503: Report any issues/bugs you mind find to lp:switchboard
[_LOG_LEVEL_WARN 22:16:58.903064] [Gtk] Theme parsing error: gtk-widgets.css:1273:25: Failed to import: Error opening file: No such file or directory
[_LOG_LEVEL_WARN 22:16:58.920327] switchboard-app.vala:512: Unknown option --version
[_LOG_LEVEL_INFO 22:16:58.922764] Application.vala:71: Switchboard version: 0.9
[_LOG_LEVEL_INFO 22:16:58.922835] Application.vala:73: Kernel version: 3.2.0-27-generic
[_LOG_LEVEL_FATAL 22:16:58.925953] [GLib] g_strrstr: assertion `haystack != NULL' failed
[_LOG_LEVEL_FATAL 22:16:58.925998] Switchboard will not function properly.
[_LOG_LEVEL_FATAL 22:16:59.010103] [GLib-GIO] This application can not open files.
[_LOG_LEVEL_FATAL 22:16:59.010163] Switchboard will not function properly.
[_LOG_LEVEL_WARN 22:16:59.021217] [Gdk] The program 'switchboard' received an X Window System error.This probably reflects a bug in the program.The error was 'GLXBadRenderRequest'. (Details: serial 410 error_code 177 request_code 154 minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)

If this information is not sufficient, let me know how to collect more.

Tags: crash
Revision history for this message
sonay (deserialkiller) wrote :

Looks like the issue was with AMD propietary drivers, using open source AMD drivers fixed the issue

Revision history for this message
Cody Garver (codygarver) wrote :

elementary OS blacklists proprietary AMD drivers because there is nothing we can do about this and similar bugs. Hopefully AMD improves or open sources their drivers soon.

Changed in switchboard:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.