Bug 19221

Summary:	gnome-sudoku doesn't start
Product:	Mageia	Reporter:	magnux77 <magnux77>
Component:	RPM Packages	Assignee:	GNOME maintainers <gnome>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, olav, zen25000
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	gnome-sudoku	CVE:
Status comment:

Description magnux77 2016-08-20 15:59:45 CEST

Description of problem:
When using the menu gnome-sudoku doesn't start.
When launched in command line :
(gnome-sudoku:15368): GLib-GIO-ERROR **: Settings schema 'org.gnome.sudoku' is not installed

Trappe pour point d'arrÃªt et de trace (core dumped)


Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. Install and run
2.
3.

Jani Välimaa 2016-08-20 16:14:30 CEST

Summary: Doesn't start => gnome-sudoku doesn't start

Comment 1 Marja Van Waes 2016-08-21 11:47:03 CEST

Assigning to all packagers collectively, since there is no registered maintainer for this package.

CC: (none) => marja11
Assignee: bugsquad => pkg-bugs

Comment 2 Jani Välimaa 2016-08-27 10:54:33 CEST

Which DE (Gnome/KDE/something else)?

Comment 3 Marja Van Waes 2016-09-07 11:47:04 CEST

re-assigning to the Gnome maintainers group.

Assignee: pkg-bugs => gnome

Jani Välimaa 2016-09-20 18:23:19 CEST

Keywords: (none) => NEEDINFO

Comment 4 Olav Vitters 2017-01-17 20:15:46 CET

Can you do an:
 rpm -ql gnome-sudoku

/usr/bin/gnome-sudoku
[..]
/usr/share/glib-2.0/schemas/org.gnome.sudoku.gschema.xml

Please verify that above file exists. Sounds like the trigger to update the gschema cache didn't run.

CC: (none) => olav

Comment 5 Barry Jackson 2017-03-23 23:46:08 CET

Probably duplicate of https://bugs.mageia.org/show_bug.cgi?id=18797

CC: (none) => zen25000

Comment 6 Barry Jackson 2017-04-05 14:41:31 CEST

Duplcate of 18797

running as root:
 glib-compile-schemas /usr/share/glib-2.0/schemas

will workaround this until fixed in bug 18797.

*** This bug has been marked as a duplicate of bug 18797 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE