Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid short option '\xbe' #27

Open
sdumetz opened this issue May 19, 2014 · 4 comments
Open

invalid short option '\xbe' #27

sdumetz opened this issue May 19, 2014 · 4 comments

Comments

@sdumetz
Copy link

sdumetz commented May 19, 2014

I have an error message each time topcube start :

(process:12963): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/goption.c:2162: ignoring invalid short option '\xbe' (-66) in entry (null):http://google.com

It does not make topcube crash, but is kinda annoying as I can't figure out where it came from or it's effects.

@springmeyer
Copy link

This looks like an issue I've hit before. If so, it is in my opinion/experience a bug not in topcube but older linux versions (due to older glib?). You can work around by passing short options, see https://github.com/mapbox/tilemill/issues/1244 for more details.

@sdumetz
Copy link
Author

sdumetz commented Jun 5, 2014

The problem seems the same, however your fix didn't work for me. Still the same error.

The strange thing is that whatever the url I call topcube with, the error always point to http://google.com. This seems linked to topcube.cpp :

static gchar *url = const_cast<char*>("http://google.com");

When I change the URL there, the error also changes.

Also, when adding g_print lines to topcube.cpp to try to locate error source, the resulting error changes to things like invalid short option '\xf3'

I'm quite confused on what I should do about it.

@springmeyer
Copy link

Maybe try upgrading your debian/ubuntu version to 14.04 - the error will likely go away.

@sdumetz
Copy link
Author

sdumetz commented Jun 20, 2014

I tried updating with latest debian stable and error is still there.

I'll try using unstable package on some VM to see if it can really solve thsi problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants