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

[Linux] ERROR:browser_main_loop.cc(212)] GLib: GError set over the top of a previous GError or uninitialized memory. #12381

Open
core-ai-bot opened this issue Aug 31, 2021 · 3 comments

Comments

@core-ai-bot
Copy link
Member

Issue by revolverXD
Monday Sep 09, 2013 at 17:30 GMT
Originally opened as adobe/brackets#5135


Hello.

I recently compiled and installed Brackets on Fedora 19,
The Application works without Any problem until i preform the following set of actions:
Help -> Show Extension Folder -> move my mouse to the left upper corner(hot corner,i use gnome-shell) -> Brackets crashes with the following error:

drefaely@localhost:~$ [0909/201735:ERROR:browser_main_loop.cc(212)] GLib: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Operation not supported [0909/201735:ERROR:browser_main_loop.cc(212)] <unknown>: Error launching preview (null) /home/drefaely/bin/brackets: line 3: 15224 Segmentation fault (core dumped) /home/drefaely/.local/bin/brackets/Brackets

The file /home/drefaely/bin/brackets is a simple script i put in the path to execute Brackets.

I know you Fedora is not supported at the moment but there is a chance you can recreate it on supported Distributions.

@core-ai-bot
Copy link
Member Author

Comment by jasonsanjose
Monday Sep 09, 2013 at 20:56 GMT


Thanks@revolverXD. Tagging medium priority.

@core-ai-bot
Copy link
Member Author

Comment by radorodopski
Friday Oct 24, 2014 at 05:43 GMT


I think it's quite possible that adobe/brackets-shell#477 fixes this.

@core-ai-bot
Copy link
Member Author

Comment by radorodopski
Thursday Nov 20, 2014 at 09:42 GMT


@revolverXD could you try running 1.0 and let me know if the issue still exists?

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

1 participant