Package Details: fontsproto-git 2.1.3.0.r94.gdf8c05f-1

Git Clone URL: https://aur.archlinux.org/fontsproto-git.git (read-only)
Package Base: fontsproto-git
Description: X11 font extension wire protocol - Git version
Upstream URL: http://cgit.freedesktop.org/xorg/proto/fontsproto/
Licenses: custom
Conflicts: fontsproto
Provides: fontsproto=2.1.3.0.r94.gdf8c05f
Submitter: Det
Maintainer: Det
Last Packager: Det
Votes: 2
Popularity: 0.000000
First Submitted: 2010-12-07 20:45
Last Updated: 2015-06-14 01:17

Dependencies (2)

Required by (57)

Sources (1)

Latest Comments

Det commented on 2013-07-01 15:14

No, you're using the wrong 'executable'. "/opt/google/earth/free/googleearth" is just a script and "/usr/bin/google-earth" and "/opt/google/earth/free/google-earth" simply link to it.

GDB: $ LD_LIBRARY_PATH=/opt/google/earth/free/ gdb /opt/google/earth/free/googleearth-bin
(gdb) run: http://pastebin.com/qbCTznWt

Strace: $ LD_LIBRARY_PATH=/opt/google/earth/free/ strace -f /opt/google/earth/free/googleearth-bin: http://pastebin.com/SYcJA3d6

crashlog-*.txt's are naturally empty.

There's just something wrong with loading the websites (i.e. the renderer or something).

Det commented on 2013-07-01 15:10

Actually it does, since 7.1.1, but it's not very useful:

GDB: $ LD_LIBRARY_PATH=/opt/google/earth/free/ gdb /opt/google/earth/free/googleearth-bin
(gdb) run: http://pastebin.com/qbCTznWt

Strace: $ LD_LIBRARY_PATH=/opt/google/earth/free/ strace -f /opt/google/earth/free/googleearth-bin: http://pastebin.com/SYcJA3d6

crashlog-*.txt's are naturally empty.

Det commented on 2013-07-01 15:09

Actually it does, since 7.1.1, but it's not very useful:

GDB (LD_LIBRARY_PATH=/opt/google/earth/free/ gdb /opt/google/earth/free/googleearth-bin
(gdb) run): http://pastebin.com/qbCTznWt

Strace (LD_LIBRARY_PATH=/opt/google/earth/free/ strace -f /opt/google/earth/free/googleearth-bin): http://pastebin.com/SYcJA3d6

crashlog-*.txt's are naturally empty.

Det commented on 2013-04-17 14:11

@igorcard, they've never been automatic. Unless you specified your daemons in rc.conf or ran "vmware-modconfig --console --install-all" you _always_ had to manually run "/etc/rc.d/vmware start", which later became simply "rc.d start vmware". The only exception was Windows, where even there changing the services from "Automatic" to "Manual" would render VMware totally unusable. It's always relied on these things to be already running.

Now that we have systemd this command became "systemctl start vmware". To enable it on boot it's "systemctl enable vmware" (as instructed in the .install). This also invalidated the need for a 'VMware-USBArbitrator', which is an _rc.d_ script that has been replaced by 'vmware-usbarbitrator.service'. All it does is run "/usr/bin/vmware-usbarbitrator" and it will be automatically pulled in by 'vmware.service'.

@travis.hegner, it's what I do.

Det commented on 2013-04-17 14:11

@igorcard, they've never been automatic. Unless you specified your daemons in rc.conf or ran "vmware-modconfig --console --install-all" you _always_ had to manually run "/etc/rc.d/vmware start", which later became simply "rc.d start vmware". The only exception was Windows, where even there changing the services from "Automatic" to "Manual" would render VMware totally unusable. It's always relied on these things to be already running.

Now that we have systemd this command became "systemctl start vmware". To enable it on boot it's "systemctl enable vmware" (as instructed in the .install). This also invalidated the need for a 'VMware-USBArbitrator', which is an _rc.d_ script that has been replaced by 'vmware-usbarbitrator.service'. All it does is run "/usr/bin/vmware-usbarbitrator" and it's automatically pulled in by 'vmware.service'.

@travis.hegner, it's what I do.

Det commented on 2013-04-17 14:10

@igorcard, they've never been automatic. Unless you specified your daemons in rc.conf or ran "vmware-modconfig --console --install-all" you _always_ had to manually run "/etc/rc.d/vmware start", which later became simply "rc.d start vmware". The only exception was Windows, where even there changing the services from "Automatic" to "Manual" would render VMware totally unusable. It's always relied on these things to be already running.

Now that we have systemd this command became "systemctl start vmware". To enable it on boot it's "systemctl enable vmware" (as instructed in the .install). This also invalidated the need for a 'VMware-USBArbitrator', which is an _rc.d_ script that has been replaced by 'vmware-usbarbitrator.service'. All it does is run "/usr/bin/vmware-usbarbitrator" and it's automatically pulled in by starting 'vmware.service'.

@travis.hegner, it's what I do.

Det commented on 2013-04-17 14:09

@igorcard, they've never been automatic. Unless you specified your daemons in rc.conf or ran "vmware-modconfig --console --install-all" you _always_ had to manually run "/etc/rc.d/vmware start", which later became simply "rc.d start vmware". The only exception was Windows, where even there changing the services from "Automatic" to "Manual" would render VMware totally unusable. It's always relied on these things to be already running.

Now that we have systemd this command became "systemctl start vmware". To enable it on boot it's "systemctl enable vmware" (as instructed in the .install). This also invalidated the need for a 'VMware-USBArbitrator', which is an _rc.d_ script that has been replaced with 'vmware-usbarbitrator.service'. All it does is run "/usr/bin/vmware-usbarbitrator" and it's automatically pulled in by starting 'vmware.service'.

@travis.hegner, it's what I do.

Det commented on 2013-04-17 14:09

@igorcard, they've never been automatic. Unless you specified your daemons in rc.conf or ran "vmware-modconfig --console --install-all" you _always_ had to manually run "/etc/rc.d/vmware start", which later became simply "rc.d start vmware". The only exception was Windows, where even there changing the services from "Automatic" to "Manual" would render VMware totally unusable. It's always relied on these things to be already running.

Now that we have systemd this command became "systemctl start vmware". To enable it on boot it's "systemctl enable vmware" (as instructed in the .install). This also invalidated the need for a 'VMware-USBArbitrator', which is an _rc.d_ script that I replaced with 'vmware-usbarbitrator.service'. All it does is run "/usr/bin/vmware-usbarbitrator" and it's automatically pulled in by starting 'vmware.service'.

@travis.hegner, it's what I do.

Det commented on 2013-04-17 14:08

@igorcard, they've never been automatic. Unless you specified your daemons in rc.conf or ran "vmware-modconfig --console --install-all" you _always_ had to manually run "/etc/rc.d/vmware start", which later became simply "rc.d start vmware". The only exception was Windows, where even there changing the services from "Automatic" to "Manual" would render VMware totally unusable. It's always relied on these things to be already running.

Now that we have systemd this command became "systemctl start vmware". To enable it on boot it's "systemctl enable vmware" (as instructed in the .install). This also invalidated the need for a 'VMware-USBArbitrator'. This is an _rc.d_ script that I replaced with 'vmware-usbarbitrator.service'. All it does is run "/usr/bin/vmware-usbarbitrator" and it's automatically pulled in by starting 'vmware.service'.

@travis.hegner, it's what I do.

Det commented on 2013-04-17 14:08

@igorcard, they've never been automatic. Unless you specified your daemons in rc.conf or ran "vmware-modconfig --console --install-all" you _always_ had to manually run "/etc/rc.d/vmware start", which later became simply "rc.d start vmware". The only exception was Windows, where even there changing the services from "Automatic" to "Manual" would render VMware totally unusable. It's always relied on these things to already be running.

Now that we have systemd this command became "systemctl start vmware". To enable it on boot it's "systemctl enable vmware" (as instructed in the .install). This also invalidated the need for a 'VMware-USBArbitrator'. This is an _rc.d_ script that I replaced with 'vmware-usbarbitrator.service'. All it does is run "/usr/bin/vmware-usbarbitrator" and it's automatically pulled in by starting 'vmware.service'.

@travis.hegner, it's what I do

All comments