1 |
Martin Larsson wrote: |
2 |
> Remy Blank wrote: |
3 |
>> has the following permissions: |
4 |
>> -rw-rw-r-- 1 root root 3244 mai 20 08:49 gdk-pixbuf.loaders |
5 |
>> So you might just want to try and chmod it to 664. |
6 |
> |
7 |
> Trying that gave me: |
8 |
> (null): file ../../pango-1.4.1/pango/shape.c: line 75 (pango_shape): |
9 |
> assertion failed: (glyphs->num_glyphs > 0) |
10 |
> |
11 |
> (process:9070): GLib-GObject-CRITICAL (recursed) **: file |
12 |
> ../../glib-2.4.8/gobject/gobject.c: line 1561 (g_object_ref): |
13 |
> assertion `G_IS_OBJECT (object)' failed |
14 |
> aborting... |
15 |
|
16 |
Well, then that was only part of the problem. Two ideas I can offer: |
17 |
|
18 |
- There might be other files with broken permissions. You could try |
19 |
finding them with something like: |
20 |
|
21 |
find /opt/vmware -perm 0400 -o -perm 0600 -o -perm 0700 |
22 |
|
23 |
If this finds any, set the permissions correctly (usually the owner and |
24 |
group have the same permission bits, and the write bit is removed for |
25 |
world). |
26 |
|
27 |
- Try to run "revdep-rebuild -pv" and see if you have any broken |
28 |
dependencies in libraries used by vmware, and if so, re-emerge them. |
29 |
|
30 |
> So. I'll be running as root, I guess. :*) |
31 |
|
32 |
Personally, I would *never* ever do that. But hey, it's your computer. |
33 |
|
34 |
-- Remy |
35 |
|
36 |
|
37 |
Remove underscore and suffix in reply address for a timely response. |
38 |
|
39 |
-- |
40 |
gentoo-user@g.o mailing list |