Not sure if it's the emerald ebuild or emerald-themes, but when upgrading to 0.1.3 there are no decorations. When launching Emerald Themer and clicking on a theme, a dialog box appears with says "Invalid Theme File / Name" This happens for every theme.
Ok here's something else: I upgraded emerald/beryl and glib at the same time. I did notice the following emerald-theme-manager via strace: open("/usr/share/emerald/themes/Mirage//buttons.restore.png", O_RDONLY|O_LARGEFILE) = 9 open("/home/marduk/.emerald/theme//buttons.restore.png.MA3IKT", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 9 open("/usr/share/emerald/themes/Mirage//buttons.max.png", O_RDONLY|O_LARGEFILE) = 9 open("/home/marduk/.emerald/theme//buttons.max.png.6ISIKT", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 9 open("/usr/share/emerald/themes/Mirage//theme.screenshot.png", O_RDONLY|O_LARGEFILE) = 9 open("/home/marduk/.emerald/theme//theme.screenshot.png.U1SIKT", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 9 open("/usr/share/emerald/themes/Mirage//buttons.min.png", O_RDONLY|O_LARGEFILE) = 9 open("/home/marduk/.emerald/theme//buttons.min.png.KSRIKT", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 9 open("/usr/share/emerald/themes/Mirage//theme.ini", O_RDONLY|O_LARGEFILE) = 9 open("/home/marduk/.emerald/theme//theme.ini.SBSIKT", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0666) = 9 I was confused by the weird file names. Also emerald-theme-manager shows all the themes as having no engine. On a hunch I decided to downgrade glib from2.12.5 to 2.12.4-r1. After I did that the emerald-theme-manager comes up fine. It shows the engines and can click on a theme. However, I still get no decorations. Also, after the downgrade, strace doesn't show those funky file names. So I think it has something to do with glib and possibly something else since simply downgrading glib fixes some of the issues but not all of them.
I am having the same issue as well. I have not tried anything related to glib however.
When I went into the beryl-settings app, some of the options (like dbus) which where enabled before were disabled. I enabled dbus and a few others and re-started emerald and my decorations came back. So I'm not sure if the issue was glib or the beryl settings, but I'm thinking it's both. Could someone *not* downgrade glib but enable dbus, etc in beryl to see what effect it has?
I also have the similar problem. After upgrading to glib-2.12.5 I lost my previous settings of beryl, and could not change the settings anymore(it complained unable to access some files, or something the like, when I ran beryl-manager in a terminal and changed the settings ). Things went fine when I downgraded glib to 2.12.4-r1.
I just upgraded too first there was a theme, set by default but after trying to choose one with emerald-theme-manager the theme simply disappeared I tried to enable dbus but somehow beryl-settings cant write the settings file does anyone experience the same problem? strace gives: access("/home", F_OK) = 0 stat("/home", {st_mode=S_IFDIR|0755, st_size=208, ...}) = 0 access("/home/tux", F_OK) = 0 stat("/home/tux", {st_mode=S_IFDIR|0755, st_size=920, ...}) = 0 access("/home/tux/.beryl", F_OK) = 0 stat("/home/tux/.beryl", {st_mode=S_IFDIR|0755, st_size=144, ...}) = 0 access("/home/tux/.beryl/", F_OK) = 0 stat("/home/tux/.beryl/", {st_mode=S_IFDIR|0755, st_size=144, ...}) = 0 open("/home/tux/.beryl/settings", O_RDONLY) = 4 fstat(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 close(4) = 0 write(2, "\n(beryl-settings:17893): GLib-CR"..., 113 (beryl-settings:17893): GLib-CRITICAL **: g_key_file_set_value: assertion `g_key_file_is_key_name (key)' failed ) = 113 lstat("/home/tux/.beryl/settings", {st_mode=S_IFLNK|0777, st_size=34, ...}) = 0 readlink("/home/tux/.beryl/settings", "/home/tux/.beryl/settings1.Profile", 256) = 34 gettimeofday({1166601990, 104184}, NULL) = 0 open("/home/tux/.beryl/settings1.Profile.ELDVKT", O_RDWR|O_CREAT|O_EXCL, 0666) = 4 fcntl(4, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE) fstat(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2b362d1ee000 lseek(4, 0, SEEK_CUR) = 0 close(4) = 0 munmap(0x2b362d1ee000, 4096) = 0 rename("/home/tux/.beryl/settings1.Profile.ELDVKT", "/home/tux/.beryl/settings1.Profile") = 0 so maybe its really an issue with glib I also noticed that the permissions of 'Scaled_Black_Mod' didn't match those of the other themes in /usr/share/emerald/themes/ but changing theme didn't help btw, why has version 0.1.2 been removed from portage? I'd liked to try the old emerald-themes package for example ok, actualy I just found the old files but they seem to be just the same (even of the same size) this is a little confusing, haven't there been any changes since 0.1.2? (I meen to emeralds-themes) well, this might be because of the user-update function in emerald-theme-manager I'm on amd64, maybe someone should change Hardware to All
(In reply to comment #4) > I also have the similar problem. After upgrading to glib-2.12.5 I lost my > previous settings of beryl, and could not change the settings anymore(it > complained unable to access some files, or something the like, when I ran > beryl-manager in a terminal and changed the settings ). Things went fine when I > downgraded glib to 2.12.4-r1. > Same here and i'm on amd64 too
same bug here, amd64 box. running beryl-settings from console and click on any settings item, I got the following error: (beryl-settings:14186): GLib-CRITICAL **: g_key_file_set_value: assertion `g_key_file_is_key_name (key)' failed and the ~/.beryl/settings file never got saved, even if I copy a settings file to overwrite it, once beryl-settings run, the settings in that file got wiped out.
$ cat /etc/portage/package.mask =dev-libs/glib-2.12.5 downgraded to glib-2.12.4-r1 solved the problem.
Try upgrading to 2.12.5, then emerge -1 beryl-core beryl-plugins beryl-manager beryl-settings emerald x11-themes/emerald-themes <beryl-dbus> - And again, make sure you have unmerged x11-misc/emerald-themes FIRST.
(In reply to comment #9) > Try upgrading to 2.12.5, then emerge -1 beryl-core beryl-plugins beryl-manager > beryl-settings emerald x11-themes/emerald-themes <beryl-dbus> - And again, make > sure you have unmerged x11-misc/emerald-themes FIRST. > It didn't work here, I had to downgrade glib again
I'm also running the AMD64 arch with beryl. I had the same problem where I could change any settings in the emerald manager or beryl settings manager. A downgrade of glib fixed the problem.
For people who can't change settings. Try removing your .beryl and .emerald directories and see if that allows you to write after that. Its also been known to solve some of the issues. I can't reproduce this, mostly because I've never had decorations with beryl X_X
*** Bug 158653 has been marked as a duplicate of this bug. ***
Same issues here on amd64, removing the beryl and emerald directories does not fix the problem.
*** Bug 158646 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > Could someone *not* downgrade glib but enable dbus, etc in beryl to see what > effect it has? None. This glib version is junk...
Alright, bit of research. Its possibly a glib bug as suspected by some users. Various bugs from other sources. http://bugs.beryl-project.org/trac/ticket/439 http://bugzilla.gnome.org/show_bug.cgi?id=387823
I'm the submitter of Bug 158646... First Beryl is not the only application that breaks with the upgrade to glib 2.12.5, so why make it a specific Beryl problem is a mystery too me. I referred in my bug report to several problems after the upgrade too 2.12.5, all experienced by myself and reported by other in the forums. But strange enough I can't refer to this, is not done....
glib-2.12.5-r1 fixes the other problem. Please test if it fixes emerald-themes too. 2.12.5 started following the appropriate standard for key names with GKeyFile to the letter, which made some things like gnome-vfs MIME type caches not work anymore as the key name didn't validate (it used chars like '.', '/' and '+' in the name). If emerald-themes GKeyFile usage doesn't deviate from the standard more than gnome-vfs does then it should be fixed now - please test
Looks fixed here Thx
Fixed here as well.
Well thats a couple of confirmed fixes then, so looks like this is solved for the issues mentioned. ^.^. Thank you both for testing it and reporting back.
