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 618727 - gtk_rc_get_style_by_paths can return NULL
gtk_rc_get_style_by_paths can return NULL
Status: RESOLVED FIXED
Product: libgnomekbd
Classification: Core
Component: Indicator
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: libgnomekbd maintainers
Sergey V. Udaltsov
: 619769 631168 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-05-15 18:26 UTC by Jiri Cerny
Modified: 2010-10-04 01:06 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch solving the problem (1.42 KB, patch)
2010-05-15 18:26 UTC, Jiri Cerny 		none Details | Review

Description Jiri Cerny 2010-05-15 18:26:51 UTC 
Created attachment 161131 [details] [review]
patch solving the problem

In functions gkbd_indicator_config_load_font and gkbd_indicator_config_load_colors,  gtk_rc_get_style_by_paths returns NULL in some situations. 

I can trigger it by changing the color in gnome-appearance-properties -> Modify -> Colors -> change some color. 

A simple patch attached.
Comment 1 Sergey V. Udaltsov 2010-05-15 20:57:51 UTC 
Your patch looks correct, I'll commit it - but could you please explain, how do you manage to get style = NULL?
Comment 2 Sergey V. Udaltsov 2010-05-15 21:00:40 UTC 
ok, in git. thanks!
Comment 3 Jiri Cerny 2010-05-16 15:39:05 UTC 
I explained it in the bug report. It is sufficient to change a color the theme selector, or to change the theme, and I get style = NULL. Do not ask me why.
Comment 4 Sergey V. Udaltsov 2010-05-16 15:50:56 UTC 
Well, actually my question was "why":) Sorry, I did not make myself clear. Anyway, it is fixed now. Thank you.
Comment 5 Rui Matos 2010-05-27 09:45:37 UTC 
*** Bug 619769 has been marked as a duplicate of this bug. ***
Comment 6 Fabio Durán Verdugo 2010-10-04 01:06:36 UTC 
*** Bug 631168 has been marked as a duplicate of this bug. ***