GLib-GIO-ERROR causing system start-up delay with latest release
Submitted by an unknown user
Assigned to Jim Nelson
Link to original bug (#717977)
Description
---- Reported by shotwell-maint@gnome.bugs 2011-08-30 16:21:00 -0700 ----
Original Redmine bug id: 4073
Original URL: http://redmine.yorba.org/issues/4073
Searchable id: yorba-bug-4073
Original author: Forage -
Original description:
Hi,
An error is occurring right after logging in, causing quite a significant start-up delay. This started to happen after I updated Shotwell to version 0.11 from https://launchpad.net/~yorba/+archive/ppa
Because my system seems to hang for a short while right after logging in I started looking at the logs and in syslog I found:
Aug 31 00:23:37 Khazad-dum gnome-session1912: WARNING: Application 'gsettings-data-convert.desktop' failed to register before timeout
This let me to perform gsettings-data-convert manually in the terminal, resulting in:
_$ gsettings-data-convert
GLib-GIO-ERROR **: Settings schema 'org.yorba.shotwell.sharing' does not contain a key named 'default-service'
aborting...
Aborted_
This is the cause of the system freeze as far as I can tell since I can't find any other obvious problems in the logs.
Version: Shotwell 0.11
OS: Ubuntu 11.04 (x86)
Also: When I updated Shotwell I found to weird that it required a system reboot to complete. This should never be required for such an application, should it?
Let me know if you need any more information.
Related issues:
- related to shotwell - 4056: Ensure all publishing keys are converted from GConf to GS... (Fixed)
- related to shotwell - 3981: [norepro] Crashes on startup with assertion failure in so... (Fixed)
- related to shotwell - 4072: Shotwell preferences are lost when restarting Shotwell (G... (Fixed)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Jim Nelson about 2 years ago
- Priority changed from Normal to High
- Target version set to 0.11.1
We've seen something similar to this in #3981 (which is an unrelated bug, so this problem is ticketed in #4056 (closed)). I thought maybe this had to do with running Shotwell from its build directory, but as you upgraded from our PPA, that's not the issue.
Do you happen to know what version of Shotwell you were running before you upgraded?
Also, you're correct, you shouldn't have to reboot your system when you install Shotwell. Is it possible other packages were installed by Synaptic as well, and that they required the reboot?
Also, I don't know why your login is taking so long. It looks like a gsettings-data-convert problem. We don't execute the program until you run Shotwell.
Comment 2
Updated by Forage - about 2 years ago
Before the update I had version 0.10 installed, also from the same PPA. I checked the history and Shotwell was the only package installed/updated that day (August 25). No other installations nor updates where done on the day before and the day after, so it has to be Shotwell requiring the reboot.
Right after the update, the indicator icon of the menu with the logout- shutdown options turned red, meaning a reboot is required. Running GNOME- classic by the way, not GNOME Shell or Unity.
Comment 3
Updated by Jim Nelson about 2 years ago
Ok -- thanks for the info, this will help us repro it here and get a fix out!
Comment 4
Updated by Jim Nelson about 2 years ago
- Assignee set to Jim Nelson
Comment 5
Updated by Jim Nelson about 2 years ago
- Status changed from Open to 5
- Resolution set to fixed
Fixed in r05ac3bb5 The default-service element wasn't present in the gsettings schema, causing gsettings-data-convert to yarf every time.
This might fix #4072 (closed), but I can't reproduce that problem to begin with. (Eric, can you try reproing it with the latest trunk?) This might also close #4056 (closed), but more investigation is required.
Forage, I don't know if you can download our trunk and build and test yourself, but you're welcome to try. I was able to reproduce the problem here and this patch fixes it. So, if you can't, this should be solved in 0.11.1.
Comment 6
Updated by Forage - about 2 years ago
Thanks for fixing this Jim.
I can build and test it myself no problem, but I'm always hesitant to replace exiting software with self-compiled versions. Installing it next to the existing Shotwell is no option in this case. I'd rather wait for 0.11.1, which I assume won't take weeks to be released.
P.s. please disable the CKeditor in this issue tracker. It's a PITA to use and it makes the update e-mails pretty much useless with all the HTML code included ;-)
Comment 7
Updated by Jim Nelson about 2 years ago
Understood, Forage. Can't give you a specific date when 0.11.1 will be out, but hopefully it's sooner rather than later.
Removing CKEditor is definitely something we want to do: #3878 Unfortunately we're short- staffed right now and working hard to get 0.11.1 out the door.
Comment 8
Updated by Forage - about 2 years ago
Fix confirmed to work, thanks! No more 10 sec wait when logging in.
Also, no reboot required when updating this time.
Comment 9
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:54 UTC ---
This bug was previously known as bug 4073 at http://redmine.yorba.org/show_bug.cgi?id=4073
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.11.1
Resolution: RESOLVED FIXED