marking as confirmed by the number of duplicates, sometime goes wrong
with schemas registration on upgrade sometimes. We don't log schemas
registration at the moment which makes not easy to know what happened
after that. Something that should be worked next cycle
** Changed in: gconf2 (Ubuntu)
** Bug 62966 has been marked a duplicate of this bug
--
Configuration editor reports that no schema can be found since latest dapper
updates
https://launchpad.net/bugs/50150
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Bug 62982 has been marked a duplicate of this bug
--
Configuration editor reports that no schema can be found since latest dapper
updates
https://launchpad.net/bugs/50150
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
probably a bug somewhere on an issue on your machine during the upgrade.
If there is a bug the right way is to fix it and not to register all the
schemas for eveybody as a workaround
--
Configuration editor reports that no schema can be found since latest dapper
updates
Downgrading is not part of the normal workflow. You can do it using apt
pinning by example. Your patch is not correct, there is no reason to
register all the schemas on gconf installation, all the packages
shipping a schemas register it themself
--
Configuration editor reports that no schema can
Your patch is not correct, there is no reason to register all the
schemas on gconf installation, all the packages shipping a schemas
register it themself
So then why were all schemas lost upon upgrading gconf?
--
Configuration editor reports that no schema can be found since latest dapper
I happened to reboot this weekend and had a shock. What I ended up
doing was just downgrading to Gnome 2.14. It seems to be a problem with
the GConf schemas but I just decided to downgrade everything and wait
until someone else fixed it.
Downgrading is rather awkward with the Debian system but
Ok, I upgraded back to Gnome 2.15 and used the fix in the link:
$ sudo gconf-schemas --register /usr/share/gconf/schemas/*.schemas
This should probably be added to the gconf2.postinst to end further
confusion.
--
Configuration editor reports that no schema can be found since latest dapper
Well, here's a patch to the gconf2.postinst so hopefully it will be
added.
--
Configuration editor reports that no schema can be found since latest dapper
updates
https://launchpad.net/bugs/50150
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Changed in: gconf (Ubuntu)
Status: Unconfirmed = Needs Info
--
Configuration editor reports that no schema can be found since latest dapper
updates
https://launchpad.net/bugs/50150
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
what schemas did people have to reinstall? Some people had similar issue
but that's not likely to be due to gconf, maybe some random error on the
target system leading to have the schemas not installed?
** Changed in: gconf (Ubuntu)
Importance: Untriaged = Low
Assignee: (unassigned) =
config-manager not involved. Closing this task.
** Changed in: config-manager (Ubuntu)
Status: Unconfirmed = Rejected
--
Configuration editor reports that no schema can be found since latest dapper
updates
https://launchpad.net/bugs/50150
--
desktop-bugs mailing list
metacity-themes not involved. Closing this task.
** Changed in: metacity-themes (Ubuntu)
Status: Unconfirmed = Rejected
--
Configuration editor reports that no schema can be found since latest dapper
updates
https://launchpad.net/bugs/50150
--
desktop-bugs mailing list
Are all these bugs about Automatix? It's not supported by Ubuntu at all
and a separate project.
--
Configuration editor reports that no schema can be found since latest dapper
updates
https://launchpad.net/bugs/50150
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Bug 50133 has been marked a duplicate of this bug
--
Configuration editor reports that no schema can be found since latest dapper
updates
https://launchpad.net/bugs/50150
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I had the same problem after a fresh install and then a full upgrade.
To fix it I had to reregister the gconf schemas
(howto here: http://ubuntuforums.org/showpost.php?p=1164346postcount=11)
Hope this helps someone...
--
Configuration editor reports that no schema can be found since latest
** Bug 50205 has been marked a duplicate of this bug
--
Configuration editor reports that no schema can be found since latest dapper
updates
https://launchpad.net/bugs/50150
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I installed the package manager Automatix and updated Java and a few
other codecs as well. Everything was fine until I shutdown and rebooted.
When I logged in I now have the exact issues detailed in this report.
--
Configuration editor reports that no schema can be found since latest dapper
I ran the...
sudo apt-get upgrade
Which seems to have fixed the issue regarding the desk panels where as before I
minimized and the windows would disapear, now the properly dock.
I also notcied that my time format has reverted back to the correct display.
Before it was shown just
4:37 PM and
Merging package from Bug 50148 here as they are duplicates of each
other.
** Changed in: config-manager (Ubuntu)
Sourcepackagename: config-manager = gconf
** Also affects: config-manager (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
** Also affects: metacity-themes (Ubuntu)
20 matches
Mail list logo
