The new issue is a different bug that the one described there, don't
reopen closed bugs but open new ones rather
** Changed in: glib2.0 (Ubuntu)
Status: Triaged => Fix Released
--
glib-compile-schemas trigger not run after installation GCalctool
https://bugs.launchpad.net/bugs/602175
You
this bug also causes the same problems with evince
--
glib-compile-schemas trigger not run after installation GCalctool
https://bugs.launchpad.net/bugs/602175
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in ubuntu.
--
desktop
I just added myself to the list as being effected by this bug...
I'm running Linux 2.6.35-19 generic i686 (fully updated Maverick) on an
Intel P4 Extreme Edition based machine.
I don't care for Empathy. I purged Empathy from my system and installed
Pidgin, when I first installed Maverick.
I che
Experiencing the same symptoms as Yuri.
Removing Empathy shouldn't break other programs this way, should it?
** Changed in: glib2.0 (Ubuntu)
Status: Fix Released => Triaged
--
glib-compile-schemas trigger not run after installation GCalctool
https://bugs.launchpad.net/bugs/602175
You rec
For me, the workaround command fails with:
> No such schema `org.gnome.Empathy.conversation' specified in override
file `/usr/share/glib-2.0/schemas/ubuntu-artwork.gschema.override'
This is probably because I had uninstalled empathy before. After
reinstalling empathy, `sudo glib-compile-schemas
/
This bug was fixed in the package glib2.0 - 2.25.10-1ubuntu2
---
glib2.0 (2.25.10-1ubuntu2) maverick; urgency=low
* Updated the trigger work to the current debian svn version,
thanks to Josselin for the review of our changes and improvements
* debian/libglib2.0-0.dirs, debian/
The issue is that the trigger registering schemas doesn't work when the
directory is not there which is an issue when the first schemas is
installed, reinstalling the deb should workaround the issue
** Package changed: gcalctool (Ubuntu) => glib2.0 (Ubuntu)
** Changed in: glib2.0 (Ubuntu)
I can confirm this bug myself.
It seems that this is a packaging issue, the GSettings scheme isn't compiled
with the glib-compile-schemas trigger.
However, not everyone is having this bug.
I am using the amd64 version of Ubuntu, just as the reporter.
** Summary changed:
- gcalctool crashed wit
** Attachment added: "ThreadStacktrace.txt"
http://launchpadlibrarian.net/51451517/ThreadStacktrace.txt
** Attachment removed: "CoreDump.gz"
http://launchpadlibrarian.net/51450412/CoreDump.gz
** Changed in: gcalctool (Ubuntu)
Importance: Undecided => Medium
** Tags removed: need-amd64-
** Attachment added: "Stacktrace.txt"
http://launchpadlibrarian.net/51451516/Stacktrace.txt
--
gcalctool crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/602175
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to g
StacktraceTop:
g_settings_schema_new (
g_settings_constructed (
g_object_newv (object_type=,
g_object_new_valist (object_type=38743808,
g_object_new (object_type=38743808,
--
gcalctool crashed with signal 5 in g_object_newv()
https://bugs.launchpad.net/bugs/602175
You received this bug not
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/51450412/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/51450413/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/51450414/Disassembly.txt
** Attachm
12 matches
Mail list logo
