Kate gives out debug messages on the console from which it is started
up vote
6
down vote
favorite
I am new to Linux. I use Ubuntu 11.04. Whenever I open a file with kate from the commandline, with 'kate &' (or without ampersand), Kate starts out giving messages on the console. It continuously gives them out as I save a file or close one. They look like debug messages to me (sample below). I have used Synaptic package manager to install Kate. Uninstalling and installing the dev version did not make any change. Soon my console becomes cluttered. Is there a way to suppress these messages? There was nothing explicit in Kate settings either.
Thank you,
The messages look like
kate(13412)/kate-filetree KateFileTreeModel::handleInsert: BEGIN!
kate(13412)/kate-filetree KateFileTreeModel::handleInsert: creating a new root
kate(13412)/kate-filetree ProxyItem::ProxyItem: ProxyItem(0x1796840,0x0,-1,QObject(0x0)
....
kate(13435)/kate-filetree KateFileTreeModel::documentActivated: adding viewHistory ProxyItem(0x1eb7cf0,0x1eb6830,0,KateDocument(0x1d93ea0) , "Untitled" )
kate(13435)/kate-filetree KateFileTreeModel::updateBackgrounds: BEGIN!
kate(13435)/kate-filetree KateFileTreeModel::updateBackgrounds: END!
kate(13435)/kate-filetree KateFileTreeModel::documentActivated: END!
kate(13435)/kate-filetree KateFileTreePluginView::viewChanged: END!
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x5601b42
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x5601b42
linux ubuntu kate
asked Mar 29 '12 at 12:08
Elan
13314
migrated from stackoverflow.com Mar 31 '12 at 3:22
This question came from our site for professional and enthusiast programmers.
add a comment |
up vote
6
down vote
favorite
I am new to Linux. I use Ubuntu 11.04. Whenever I open a file with kate from the commandline, with 'kate &' (or without ampersand), Kate starts out giving messages on the console. It continuously gives them out as I save a file or close one. They look like debug messages to me (sample below). I have used Synaptic package manager to install Kate. Uninstalling and installing the dev version did not make any change. Soon my console becomes cluttered. Is there a way to suppress these messages? There was nothing explicit in Kate settings either.
Thank you,
The messages look like
kate(13412)/kate-filetree KateFileTreeModel::handleInsert: BEGIN!
kate(13412)/kate-filetree KateFileTreeModel::handleInsert: creating a new root
kate(13412)/kate-filetree ProxyItem::ProxyItem: ProxyItem(0x1796840,0x0,-1,QObject(0x0)
....
kate(13435)/kate-filetree KateFileTreeModel::documentActivated: adding viewHistory ProxyItem(0x1eb7cf0,0x1eb6830,0,KateDocument(0x1d93ea0) , "Untitled" )
kate(13435)/kate-filetree KateFileTreeModel::updateBackgrounds: BEGIN!
kate(13435)/kate-filetree KateFileTreeModel::updateBackgrounds: END!
kate(13435)/kate-filetree KateFileTreeModel::documentActivated: END!
kate(13435)/kate-filetree KateFileTreePluginView::viewChanged: END!
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x5601b42
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x5601b42
linux ubuntu kate
asked Mar 29 '12 at 12:08
Elan
13314
migrated from stackoverflow.com Mar 31 '12 at 3:22
This question came from our site for professional and enthusiast programmers.
This does not happen in any of the other applications.
– Elan
Mar 29 '12 at 12:12
add a comment |
up vote
6
down vote
favorite
up vote
6
down vote
favorite
I am new to Linux. I use Ubuntu 11.04. Whenever I open a file with kate from the commandline, with 'kate &' (or without ampersand), Kate starts out giving messages on the console. It continuously gives them out as I save a file or close one. They look like debug messages to me (sample below). I have used Synaptic package manager to install Kate. Uninstalling and installing the dev version did not make any change. Soon my console becomes cluttered. Is there a way to suppress these messages? There was nothing explicit in Kate settings either.
Thank you,
The messages look like
kate(13412)/kate-filetree KateFileTreeModel::handleInsert: BEGIN!
kate(13412)/kate-filetree KateFileTreeModel::handleInsert: creating a new root
kate(13412)/kate-filetree ProxyItem::ProxyItem: ProxyItem(0x1796840,0x0,-1,QObject(0x0)
....
kate(13435)/kate-filetree KateFileTreeModel::documentActivated: adding viewHistory ProxyItem(0x1eb7cf0,0x1eb6830,0,KateDocument(0x1d93ea0) , "Untitled" )
kate(13435)/kate-filetree KateFileTreeModel::updateBackgrounds: BEGIN!
kate(13435)/kate-filetree KateFileTreeModel::updateBackgrounds: END!
kate(13435)/kate-filetree KateFileTreeModel::documentActivated: END!
kate(13435)/kate-filetree KateFileTreePluginView::viewChanged: END!
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x5601b42
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x5601b42
linux ubuntu kate
asked Mar 29 '12 at 12:08
Elan
13314
I am new to Linux. I use Ubuntu 11.04. Whenever I open a file with kate from the commandline, with 'kate &' (or without ampersand), Kate starts out giving messages on the console. It continuously gives them out as I save a file or close one. They look like debug messages to me (sample below). I have used Synaptic package manager to install Kate. Uninstalling and installing the dev version did not make any change. Soon my console becomes cluttered. Is there a way to suppress these messages? There was nothing explicit in Kate settings either.
Thank you,
The messages look like
kate(13412)/kate-filetree KateFileTreeModel::handleInsert: BEGIN!
kate(13412)/kate-filetree KateFileTreeModel::handleInsert: creating a new root
kate(13412)/kate-filetree ProxyItem::ProxyItem: ProxyItem(0x1796840,0x0,-1,QObject(0x0)
....
kate(13435)/kate-filetree KateFileTreeModel::documentActivated: adding viewHistory ProxyItem(0x1eb7cf0,0x1eb6830,0,KateDocument(0x1d93ea0) , "Untitled" )
kate(13435)/kate-filetree KateFileTreeModel::updateBackgrounds: BEGIN!
kate(13435)/kate-filetree KateFileTreeModel::updateBackgrounds: END!
kate(13435)/kate-filetree KateFileTreeModel::documentActivated: END!
kate(13435)/kate-filetree KateFileTreePluginView::viewChanged: END!
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x5601b42
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x5601b42
linux ubuntu kate
linux ubuntu kate
asked Mar 29 '12 at 12:08
Elan
13314
asked Mar 29 '12 at 12:08
Elan
13314
asked Mar 29 '12 at 12:08
Elan
13314
asked Mar 29 '12 at 12:08
Elan
13314
asked Mar 29 '12 at 12:08
Elan
13314
13314
migrated from stackoverflow.com Mar 31 '12 at 3:22
This question came from our site for professional and enthusiast programmers.
migrated from stackoverflow.com Mar 31 '12 at 3:22
This question came from our site for professional and enthusiast programmers.
This does not happen in any of the other applications.
– Elan
Mar 29 '12 at 12:12
add a comment |
This does not happen in any of the other applications.
– Elan
Mar 29 '12 at 12:12
This does not happen in any of the other applications.
– Elan
Mar 29 '12 at 12:12
This does not happen in any of the other applications.
– Elan
Mar 29 '12 at 12:12
add a comment |
2 Answers
2
active
oldest
votes
up vote
11
down vote
accepted
This post on the KDE forum explains what it is doing and how to stop it.
http://forum.kde.org/viewtopic.php?f=22&t=93955
Because you did not disable debug-messages.
Open "kdebugdialog", search for "kate" and unselect all checkboxes. Now kate won't talk to you, anymore.
+1 after including the crucial bit of the linked page
– sehe
Mar 30 '12 at 13:32
This worked, but there were some dependencies, as on kdeui. The dependencies still give out debug messages. Some of them were not clear, where they come from, and I am reluctant to blanket remove all notifications from all applications.
– Elan
Mar 30 '12 at 14:31
add a comment |
up vote
1
down vote
Debug messages are usually written to the standard error, which is the filehandle denoted by 2 in the console. You can redirect that without affecting output to the standard out (file handle 1), by starting your application like this
kate 2>/dev/null
You can append the & if you'd like as well.
The number 2 here represents file handle 2, the > is a redirection operator in the shell, /dev/null is a "blackhole" device -- it eats up everything that is written to it, so it "disappears" (does not appear in console).
You can capture the standard error output by replacing /dev/null with a filename. In that case the output goes to the file, not to the console.
In case the application is writing debug messages to the standard output, you can replace the number 2 with number 1 (see above) -- note that in this case normal messages are going to be redirected as well.
You can redirect both standard out and error at the same time, the easiest way to do so is
kate 2>&1 1>/dev/null
Here the &1 denotes the file handle 1 where standard error should be redirected. The use of & is to differentiate it from the file named 1.
For further info on redirection, read the manual of your shell (e.g. bash)
I am using csh. From your description, I followed documentation to achieve redirecting both stderr and stdout to /dev/null. Apparently, redirecting only sdterr is not that trivial. Thanks for the generic explanation of the concept.
– Elan
Mar 30 '12 at 9:20
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
11
down vote
accepted
This post on the KDE forum explains what it is doing and how to stop it.
http://forum.kde.org/viewtopic.php?f=22&t=93955
Because you did not disable debug-messages.
Open "kdebugdialog", search for "kate" and unselect all checkboxes. Now kate won't talk to you, anymore.
+1 after including the crucial bit of the linked page
– sehe
Mar 30 '12 at 13:32
This worked, but there were some dependencies, as on kdeui. The dependencies still give out debug messages. Some of them were not clear, where they come from, and I am reluctant to blanket remove all notifications from all applications.
– Elan
Mar 30 '12 at 14:31
add a comment |
up vote
11
down vote
accepted
This post on the KDE forum explains what it is doing and how to stop it.
http://forum.kde.org/viewtopic.php?f=22&t=93955
Because you did not disable debug-messages.
Open "kdebugdialog", search for "kate" and unselect all checkboxes. Now kate won't talk to you, anymore.
+1 after including the crucial bit of the linked page
– sehe
Mar 30 '12 at 13:32
This worked, but there were some dependencies, as on kdeui. The dependencies still give out debug messages. Some of them were not clear, where they come from, and I am reluctant to blanket remove all notifications from all applications.
– Elan
Mar 30 '12 at 14:31
add a comment |
up vote
11
down vote
accepted
up vote
11
down vote
accepted
This post on the KDE forum explains what it is doing and how to stop it.
http://forum.kde.org/viewtopic.php?f=22&t=93955
Because you did not disable debug-messages.
Open "kdebugdialog", search for "kate" and unselect all checkboxes. Now kate won't talk to you, anymore.
This post on the KDE forum explains what it is doing and how to stop it.
http://forum.kde.org/viewtopic.php?f=22&t=93955
Because you did not disable debug-messages.
Open "kdebugdialog", search for "kate" and unselect all checkboxes. Now kate won't talk to you, anymore.
answered Mar 30 '12 at 13:30
Austin
+1 after including the crucial bit of the linked page
– sehe
Mar 30 '12 at 13:32
This worked, but there were some dependencies, as on kdeui. The dependencies still give out debug messages. Some of them were not clear, where they come from, and I am reluctant to blanket remove all notifications from all applications.
– Elan
Mar 30 '12 at 14:31
add a comment |
+1 after including the crucial bit of the linked page
– sehe
Mar 30 '12 at 13:32
This worked, but there were some dependencies, as on kdeui. The dependencies still give out debug messages. Some of them were not clear, where they come from, and I am reluctant to blanket remove all notifications from all applications.
– Elan
Mar 30 '12 at 14:31
+1 after including the crucial bit of the linked page
– sehe
Mar 30 '12 at 13:32
+1 after including the crucial bit of the linked page
– sehe
Mar 30 '12 at 13:32
This worked, but there were some dependencies, as on kdeui. The dependencies still give out debug messages. Some of them were not clear, where they come from, and I am reluctant to blanket remove all notifications from all applications.
– Elan
Mar 30 '12 at 14:31
This worked, but there were some dependencies, as on kdeui. The dependencies still give out debug messages. Some of them were not clear, where they come from, and I am reluctant to blanket remove all notifications from all applications.
– Elan
Mar 30 '12 at 14:31
add a comment |
up vote
1
down vote
Debug messages are usually written to the standard error, which is the filehandle denoted by 2 in the console. You can redirect that without affecting output to the standard out (file handle 1), by starting your application like this
kate 2>/dev/null
You can append the & if you'd like as well.
The number 2 here represents file handle 2, the > is a redirection operator in the shell, /dev/null is a "blackhole" device -- it eats up everything that is written to it, so it "disappears" (does not appear in console).
You can capture the standard error output by replacing /dev/null with a filename. In that case the output goes to the file, not to the console.
In case the application is writing debug messages to the standard output, you can replace the number 2 with number 1 (see above) -- note that in this case normal messages are going to be redirected as well.
You can redirect both standard out and error at the same time, the easiest way to do so is
kate 2>&1 1>/dev/null
Here the &1 denotes the file handle 1 where standard error should be redirected. The use of & is to differentiate it from the file named 1.
For further info on redirection, read the manual of your shell (e.g. bash)
I am using csh. From your description, I followed documentation to achieve redirecting both stderr and stdout to /dev/null. Apparently, redirecting only sdterr is not that trivial. Thanks for the generic explanation of the concept.
– Elan
Mar 30 '12 at 9:20
add a comment |
up vote
1
down vote
Debug messages are usually written to the standard error, which is the filehandle denoted by 2 in the console. You can redirect that without affecting output to the standard out (file handle 1), by starting your application like this
kate 2>/dev/null
You can append the & if you'd like as well.
The number 2 here represents file handle 2, the > is a redirection operator in the shell, /dev/null is a "blackhole" device -- it eats up everything that is written to it, so it "disappears" (does not appear in console).
You can capture the standard error output by replacing /dev/null with a filename. In that case the output goes to the file, not to the console.
In case the application is writing debug messages to the standard output, you can replace the number 2 with number 1 (see above) -- note that in this case normal messages are going to be redirected as well.
You can redirect both standard out and error at the same time, the easiest way to do so is
kate 2>&1 1>/dev/null
Here the &1 denotes the file handle 1 where standard error should be redirected. The use of & is to differentiate it from the file named 1.
For further info on redirection, read the manual of your shell (e.g. bash)
I am using csh. From your description, I followed documentation to achieve redirecting both stderr and stdout to /dev/null. Apparently, redirecting only sdterr is not that trivial. Thanks for the generic explanation of the concept.
– Elan
Mar 30 '12 at 9:20
add a comment |
up vote
1
down vote
up vote
1
down vote
Debug messages are usually written to the standard error, which is the filehandle denoted by 2 in the console. You can redirect that without affecting output to the standard out (file handle 1), by starting your application like this
kate 2>/dev/null
You can append the & if you'd like as well.
The number 2 here represents file handle 2, the > is a redirection operator in the shell, /dev/null is a "blackhole" device -- it eats up everything that is written to it, so it "disappears" (does not appear in console).
You can capture the standard error output by replacing /dev/null with a filename. In that case the output goes to the file, not to the console.
In case the application is writing debug messages to the standard output, you can replace the number 2 with number 1 (see above) -- note that in this case normal messages are going to be redirected as well.
You can redirect both standard out and error at the same time, the easiest way to do so is
kate 2>&1 1>/dev/null
Here the &1 denotes the file handle 1 where standard error should be redirected. The use of & is to differentiate it from the file named 1.
For further info on redirection, read the manual of your shell (e.g. bash)
Debug messages are usually written to the standard error, which is the filehandle denoted by 2 in the console. You can redirect that without affecting output to the standard out (file handle 1), by starting your application like this
kate 2>/dev/null
You can append the & if you'd like as well.
The number 2 here represents file handle 2, the > is a redirection operator in the shell, /dev/null is a "blackhole" device -- it eats up everything that is written to it, so it "disappears" (does not appear in console).
You can capture the standard error output by replacing /dev/null with a filename. In that case the output goes to the file, not to the console.
In case the application is writing debug messages to the standard output, you can replace the number 2 with number 1 (see above) -- note that in this case normal messages are going to be redirected as well.
You can redirect both standard out and error at the same time, the easiest way to do so is
kate 2>&1 1>/dev/null
Here the &1 denotes the file handle 1 where standard error should be redirected. The use of & is to differentiate it from the file named 1.
For further info on redirection, read the manual of your shell (e.g. bash)
answered Mar 29 '12 at 12:30
Attila
I am using csh. From your description, I followed documentation to achieve redirecting both stderr and stdout to /dev/null. Apparently, redirecting only sdterr is not that trivial. Thanks for the generic explanation of the concept.
– Elan
Mar 30 '12 at 9:20
add a comment |
I am using csh. From your description, I followed documentation to achieve redirecting both stderr and stdout to /dev/null. Apparently, redirecting only sdterr is not that trivial. Thanks for the generic explanation of the concept.
– Elan
Mar 30 '12 at 9:20
I am using csh. From your description, I followed documentation to achieve redirecting both stderr and stdout to /dev/null. Apparently, redirecting only sdterr is not that trivial. Thanks for the generic explanation of the concept.
– Elan
Mar 30 '12 at 9:20
I am using csh. From your description, I followed documentation to achieve redirecting both stderr and stdout to /dev/null. Apparently, redirecting only sdterr is not that trivial. Thanks for the generic explanation of the concept.
– Elan
Mar 30 '12 at 9:20
add a comment |
Thanks for contributing an answer to Super User!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fsuperuser.com%2fquestions%2f406896%2fkate-gives-out-debug-messages-on-the-console-from-which-it-is-started%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
This does not happen in any of the other applications.
– Elan
Mar 29 '12 at 12:12