gedit is crashing again and again
I am using ubuntu mate 18.04 and I installed gedit in it alongside pluma (mate default text editor) so I can manage my text notes with gedit. I was also using this setup in ubuntu 16.04, ubuntu mate 16.04 and even in ubuntu mate 18.04 and it works really great. A few days ago I reinstalled my ubuntu mate, install gedit and some necessary plugins and now gedit is crashing in almost in all sessions. I used gedit to manage all my notes and journal entries but this problem is making it impossible. I removed and install gedit multiple time, check with and without plugins but nothing is working. Can anyone help?
update: when I launch this program in the terminal, it crashes after some time with the following error.
(gedit:26250): Gdk-ERROR **: 01:25:37.372: The program 'gedit' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
(Details: serial 2911131 error_code 16 request_code 18 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap
crash gedit mate text-editor evernote
asked Feb 10 at 11:10
ShahMoeenShahMoeen
6018
|
show 9 more comments
I am using ubuntu mate 18.04 and I installed gedit in it alongside pluma (mate default text editor) so I can manage my text notes with gedit. I was also using this setup in ubuntu 16.04, ubuntu mate 16.04 and even in ubuntu mate 18.04 and it works really great. A few days ago I reinstalled my ubuntu mate, install gedit and some necessary plugins and now gedit is crashing in almost in all sessions. I used gedit to manage all my notes and journal entries but this problem is making it impossible. I removed and install gedit multiple time, check with and without plugins but nothing is working. Can anyone help?
update: when I launch this program in the terminal, it crashes after some time with the following error.
(gedit:26250): Gdk-ERROR **: 01:25:37.372: The program 'gedit' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
(Details: serial 2911131 error_code 16 request_code 18 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap
crash gedit mate text-editor evernote
asked Feb 10 at 11:10
ShahMoeenShahMoeen
6018
1
catb.org/~esr/faqs/smart-questions.html We would love to help, but it is hard witout relavent information, or any information for that matter
– j-money
Feb 10 at 11:48
@j-money I sorry if this is a stupid question but can I ask which relevant information I need to provide, in order to get help
– ShahMoeen
Feb 10 at 12:12
2
The idea of trying another account is to eliminate something in your own directory causing the problem. Create a temporary account called "Guest", and try gedit there. Otherwise, rename~/.config/geditto~/.config/gedit.HOLD, then retry gedit and see if it works. Report back.
– heynnema
Feb 11 at 1:58
1
@heynnema I renamed gedit config folder and launch it with the terminal, this time it did not crash. Another thing I notice that ~/.config/gedit folder did not belong to the current user but root.
– ShahMoeen
Feb 11 at 15:18
1
Please re-read the complete answer. You probably started gedit from the terminal usingsudo gedit... and the fix is there...
– heynnema
Feb 11 at 15:58
|
show 9 more comments
I am using ubuntu mate 18.04 and I installed gedit in it alongside pluma (mate default text editor) so I can manage my text notes with gedit. I was also using this setup in ubuntu 16.04, ubuntu mate 16.04 and even in ubuntu mate 18.04 and it works really great. A few days ago I reinstalled my ubuntu mate, install gedit and some necessary plugins and now gedit is crashing in almost in all sessions. I used gedit to manage all my notes and journal entries but this problem is making it impossible. I removed and install gedit multiple time, check with and without plugins but nothing is working. Can anyone help?
update: when I launch this program in the terminal, it crashes after some time with the following error.
(gedit:26250): Gdk-ERROR **: 01:25:37.372: The program 'gedit' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
(Details: serial 2911131 error_code 16 request_code 18 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap
crash gedit mate text-editor evernote
asked Feb 10 at 11:10
ShahMoeenShahMoeen
6018
I am using ubuntu mate 18.04 and I installed gedit in it alongside pluma (mate default text editor) so I can manage my text notes with gedit. I was also using this setup in ubuntu 16.04, ubuntu mate 16.04 and even in ubuntu mate 18.04 and it works really great. A few days ago I reinstalled my ubuntu mate, install gedit and some necessary plugins and now gedit is crashing in almost in all sessions. I used gedit to manage all my notes and journal entries but this problem is making it impossible. I removed and install gedit multiple time, check with and without plugins but nothing is working. Can anyone help?
update: when I launch this program in the terminal, it crashes after some time with the following error.
(gedit:26250): Gdk-ERROR **: 01:25:37.372: The program 'gedit' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib length erro'.
(Details: serial 2911131 error_code 16 request_code 18 (core protocol) minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap
crash gedit mate text-editor evernote
crash gedit mate text-editor evernote
asked Feb 10 at 11:10
ShahMoeenShahMoeen
6018
asked Feb 10 at 11:10
ShahMoeenShahMoeen
6018
edited Feb 10 at 20:32
ShahMoeen
asked Feb 10 at 11:10
ShahMoeenShahMoeen
6018
asked Feb 10 at 11:10
ShahMoeenShahMoeen
6018
asked Feb 10 at 11:10
ShahMoeenShahMoeen
6018
6018
1
catb.org/~esr/faqs/smart-questions.html We would love to help, but it is hard witout relavent information, or any information for that matter
– j-money
Feb 10 at 11:48
@j-money I sorry if this is a stupid question but can I ask which relevant information I need to provide, in order to get help
– ShahMoeen
Feb 10 at 12:12
2
The idea of trying another account is to eliminate something in your own directory causing the problem. Create a temporary account called "Guest", and try gedit there. Otherwise, rename~/.config/geditto~/.config/gedit.HOLD, then retry gedit and see if it works. Report back.
– heynnema
Feb 11 at 1:58
1
@heynnema I renamed gedit config folder and launch it with the terminal, this time it did not crash. Another thing I notice that ~/.config/gedit folder did not belong to the current user but root.
– ShahMoeen
Feb 11 at 15:18
1
Please re-read the complete answer. You probably started gedit from the terminal usingsudo gedit... and the fix is there...
– heynnema
Feb 11 at 15:58
|
show 9 more comments
1
catb.org/~esr/faqs/smart-questions.html We would love to help, but it is hard witout relavent information, or any information for that matter
– j-money
Feb 10 at 11:48
@j-money I sorry if this is a stupid question but can I ask which relevant information I need to provide, in order to get help
– ShahMoeen
Feb 10 at 12:12
2
The idea of trying another account is to eliminate something in your own directory causing the problem. Create a temporary account called "Guest", and try gedit there. Otherwise, rename~/.config/geditto~/.config/gedit.HOLD, then retry gedit and see if it works. Report back.
– heynnema
Feb 11 at 1:58
1
@heynnema I renamed gedit config folder and launch it with the terminal, this time it did not crash. Another thing I notice that ~/.config/gedit folder did not belong to the current user but root.
– ShahMoeen
Feb 11 at 15:18
1
Please re-read the complete answer. You probably started gedit from the terminal usingsudo gedit... and the fix is there...
– heynnema
Feb 11 at 15:58
1
1
catb.org/~esr/faqs/smart-questions.html We would love to help, but it is hard witout relavent information, or any information for that matter
– j-money
Feb 10 at 11:48
catb.org/~esr/faqs/smart-questions.html We would love to help, but it is hard witout relavent information, or any information for that matter
– j-money
Feb 10 at 11:48
@j-money I sorry if this is a stupid question but can I ask which relevant information I need to provide, in order to get help
– ShahMoeen
Feb 10 at 12:12
@j-money I sorry if this is a stupid question but can I ask which relevant information I need to provide, in order to get help
– ShahMoeen
Feb 10 at 12:12
2
2
The idea of trying another account is to eliminate something in your own directory causing the problem. Create a temporary account called "Guest", and try gedit there. Otherwise, rename
~/.config/gedit to ~/.config/gedit.HOLD, then retry gedit and see if it works. Report back.– heynnema
Feb 11 at 1:58
The idea of trying another account is to eliminate something in your own directory causing the problem. Create a temporary account called "Guest", and try gedit there. Otherwise, rename
~/.config/gedit to ~/.config/gedit.HOLD, then retry gedit and see if it works. Report back.– heynnema
Feb 11 at 1:58
1
1
@heynnema I renamed gedit config folder and launch it with the terminal, this time it did not crash. Another thing I notice that ~/.config/gedit folder did not belong to the current user but root.
– ShahMoeen
Feb 11 at 15:18
@heynnema I renamed gedit config folder and launch it with the terminal, this time it did not crash. Another thing I notice that ~/.config/gedit folder did not belong to the current user but root.
– ShahMoeen
Feb 11 at 15:18
1
1
Please re-read the complete answer. You probably started gedit from the terminal using
sudo gedit... and the fix is there...– heynnema
Feb 11 at 15:58
Please re-read the complete answer. You probably started gedit from the terminal using
sudo gedit... and the fix is there...– heynnema
Feb 11 at 15:58
|
show 9 more comments
1 Answer
1
active
oldest
votes
From the comments...
We renamed ~/.config/gedit to ~/.config/gedit.HOLD, then retry gedit and see if it works. It worked. So something is wrong with this prefs folder. It's owned by root.
You probably started gedit in the terminal using sudo gedit, and you should be using sudo -H gedit. All GUI apps should be started this way from the terminal.
answered Feb 11 at 15:21
heynnemaheynnema
20.3k22258
I am again facing the same issue.
– ShahMoeen
Feb 12 at 21:42
@ShahMoeen How did you start gedit?
– heynnema
Feb 12 at 21:49
from start menu
– ShahMoeen
Feb 13 at 10:03
Did you put the original gedit config folder back, or did you leave the new one in place and delete the old folder? Have you added any gedit extensions? Is ~/.config owned by root, or your username?
– heynnema
Feb 13 at 13:51
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117110%2fgedit-is-crashing-again-and-again%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the comments...
We renamed ~/.config/gedit to ~/.config/gedit.HOLD, then retry gedit and see if it works. It worked. So something is wrong with this prefs folder. It's owned by root.
You probably started gedit in the terminal using sudo gedit, and you should be using sudo -H gedit. All GUI apps should be started this way from the terminal.
answered Feb 11 at 15:21
heynnemaheynnema
20.3k22258
I am again facing the same issue.
– ShahMoeen
Feb 12 at 21:42
@ShahMoeen How did you start gedit?
– heynnema
Feb 12 at 21:49
from start menu
– ShahMoeen
Feb 13 at 10:03
Did you put the original gedit config folder back, or did you leave the new one in place and delete the old folder? Have you added any gedit extensions? Is ~/.config owned by root, or your username?
– heynnema
Feb 13 at 13:51
add a comment |
From the comments...
We renamed ~/.config/gedit to ~/.config/gedit.HOLD, then retry gedit and see if it works. It worked. So something is wrong with this prefs folder. It's owned by root.
You probably started gedit in the terminal using sudo gedit, and you should be using sudo -H gedit. All GUI apps should be started this way from the terminal.
answered Feb 11 at 15:21
heynnemaheynnema
20.3k22258
I am again facing the same issue.
– ShahMoeen
Feb 12 at 21:42
@ShahMoeen How did you start gedit?
– heynnema
Feb 12 at 21:49
from start menu
– ShahMoeen
Feb 13 at 10:03
Did you put the original gedit config folder back, or did you leave the new one in place and delete the old folder? Have you added any gedit extensions? Is ~/.config owned by root, or your username?
– heynnema
Feb 13 at 13:51
add a comment |
From the comments...
We renamed ~/.config/gedit to ~/.config/gedit.HOLD, then retry gedit and see if it works. It worked. So something is wrong with this prefs folder. It's owned by root.
You probably started gedit in the terminal using sudo gedit, and you should be using sudo -H gedit. All GUI apps should be started this way from the terminal.
answered Feb 11 at 15:21
heynnemaheynnema
20.3k22258
From the comments...
We renamed ~/.config/gedit to ~/.config/gedit.HOLD, then retry gedit and see if it works. It worked. So something is wrong with this prefs folder. It's owned by root.
You probably started gedit in the terminal using sudo gedit, and you should be using sudo -H gedit. All GUI apps should be started this way from the terminal.
answered Feb 11 at 15:21
heynnemaheynnema
20.3k22258
edited Feb 11 at 16:02
answered Feb 11 at 15:21
heynnemaheynnema
20.3k22258
answered Feb 11 at 15:21
heynnemaheynnema
20.3k22258
answered Feb 11 at 15:21
heynnemaheynnema
20.3k22258
20.3k22258
I am again facing the same issue.
– ShahMoeen
Feb 12 at 21:42
@ShahMoeen How did you start gedit?
– heynnema
Feb 12 at 21:49
from start menu
– ShahMoeen
Feb 13 at 10:03
Did you put the original gedit config folder back, or did you leave the new one in place and delete the old folder? Have you added any gedit extensions? Is ~/.config owned by root, or your username?
– heynnema
Feb 13 at 13:51
add a comment |
I am again facing the same issue.
– ShahMoeen
Feb 12 at 21:42
@ShahMoeen How did you start gedit?
– heynnema
Feb 12 at 21:49
from start menu
– ShahMoeen
Feb 13 at 10:03
Did you put the original gedit config folder back, or did you leave the new one in place and delete the old folder? Have you added any gedit extensions? Is ~/.config owned by root, or your username?
– heynnema
Feb 13 at 13:51
I am again facing the same issue.
– ShahMoeen
Feb 12 at 21:42
I am again facing the same issue.
– ShahMoeen
Feb 12 at 21:42
@ShahMoeen How did you start gedit?
– heynnema
Feb 12 at 21:49
@ShahMoeen How did you start gedit?
– heynnema
Feb 12 at 21:49
from start menu
– ShahMoeen
Feb 13 at 10:03
from start menu
– ShahMoeen
Feb 13 at 10:03
Did you put the original gedit config folder back, or did you leave the new one in place and delete the old folder? Have you added any gedit extensions? Is ~/.config owned by root, or your username?
– heynnema
Feb 13 at 13:51
Did you put the original gedit config folder back, or did you leave the new one in place and delete the old folder? Have you added any gedit extensions? Is ~/.config owned by root, or your username?
– heynnema
Feb 13 at 13:51
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117110%2fgedit-is-crashing-again-and-again%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
catb.org/~esr/faqs/smart-questions.html We would love to help, but it is hard witout relavent information, or any information for that matter
– j-money
Feb 10 at 11:48
@j-money I sorry if this is a stupid question but can I ask which relevant information I need to provide, in order to get help
– ShahMoeen
Feb 10 at 12:12
2
The idea of trying another account is to eliminate something in your own directory causing the problem. Create a temporary account called "Guest", and try gedit there. Otherwise, rename
~/.config/geditto~/.config/gedit.HOLD, then retry gedit and see if it works. Report back.– heynnema
Feb 11 at 1:58
1
@heynnema I renamed gedit config folder and launch it with the terminal, this time it did not crash. Another thing I notice that ~/.config/gedit folder did not belong to the current user but root.
– ShahMoeen
Feb 11 at 15:18
1
Please re-read the complete answer. You probably started gedit from the terminal using
sudo gedit... and the fix is there...– heynnema
Feb 11 at 15:58