IPTUX always runs in background
I configured IPTUX to run in background by mistake.
The next time when i start it always runs in back ground. i tried to reinstall and also reinstalled with synaptic. still it starts in background.
Thanks,
Kavin
background
asked Jun 28 '12 at 5:16
KavinKavin
112
add a comment |
I configured IPTUX to run in background by mistake.
The next time when i start it always runs in back ground. i tried to reinstall and also reinstalled with synaptic. still it starts in background.
Thanks,
Kavin
background
asked Jun 28 '12 at 5:16
KavinKavin
112
add a comment |
I configured IPTUX to run in background by mistake.
The next time when i start it always runs in back ground. i tried to reinstall and also reinstalled with synaptic. still it starts in background.
Thanks,
Kavin
background
asked Jun 28 '12 at 5:16
KavinKavin
112
I configured IPTUX to run in background by mistake.
The next time when i start it always runs in back ground. i tried to reinstall and also reinstalled with synaptic. still it starts in background.
Thanks,
Kavin
background
background
asked Jun 28 '12 at 5:16
KavinKavin
112
asked Jun 28 '12 at 5:16
KavinKavin
112
asked Jun 28 '12 at 5:16
KavinKavin
112
asked Jun 28 '12 at 5:16
KavinKavin
112
asked Jun 28 '12 at 5:16
KavinKavin
112
112
add a comment |
add a comment |
4 Answers
4
active
oldest
votes
I am stuck in the same situation but I know one thing for sure that you can modify the %gconf.xml file directly using
sudo nano <config file path>/%gconf.xml
which should be located in any of the following locations
~/.cache/iptux
~/.gconf/apps/iptux
~/.config/iptux
I did modify the file but when I restart the system it seems to have reverted back to the original.
The entry in the file that you need to look for, to modify is:
name="hide_startup" mtime="1343670281" type="bool" value="true"
change it to:
name="hide_startup" mtime="1343670281" type="bool" value="false"
I believe, the reason for the file reverting back to the previous state is that iptux process must be running in the background and hence not allowing changes to the file.
What I am looking for is a way to kill the iptux process before modifying the config file, but can't find a process for iptux.
Will research it a bit and let you know if I find the process name.
What I found out was, that you cannot stop iptux as it doesn't have a process of its own but relies on other processes (won't get in depth here) but My solution would be to start Ubuntu in repair mode, by pressing F8 a bit after the bios screen disappears (before the Ubuntu Loading Screen) and select repair... or was it recovery mode... but you get the idea. You can then use the terminal to modify the file. In this way iptux won't have started and the file should be modified fine.
– exIT Solutions
Jul 31 '12 at 13:19
Let me know how it goes. I can't try this as my issue is a step up... I am having the issue on the Thin Client rather than the server. I'll probably try to shutdown the thin client then modify the config file.
– exIT Solutions
Jul 31 '12 at 13:20
Yep, that worked for me. Guess you'll have to logout of your profile and log in as administrator or root (not recommended) then modify the file or start terminal in so called safe mode or recovery mode
– exIT Solutions
Jul 31 '12 at 13:29
What I found out was it doesn't matter if iptux is running in the background but so as long as the profile (login) that is creating the problem is not in use or locked. What this means is that if you simply log out and log in as another user or admin you should be able to modify the problem profile's iptux config file (xml)
– exIT Solutions
Jul 31 '12 at 13:32
I suggest to use sudo nano /home/<your username>/<iptux config file path>/%gconf.xml and modify to false as discussed earlier.
– exIT Solutions
Aug 1 '12 at 1:19
add a comment |
I also had the same problem. The solution was as specified by exIT Solutions is :
First locate the
%gconf.xmlfile in your pc. Mine was in~/.gconf/apps/iptux/%gconf.xml.
Edit it with any Text Editor.Second search for the line:
entry name="hide_startup" mtime="1410256594" type="bool" value="true"
and changed it to:
entry name="hide_startup" mtime="1410256594" type="bool" value="false"
Save the file and logout. After logging in I started iptux and it worked fine.
edited Sep 9 '14 at 14:01
Luís de Sousa
9,0441752100
answered Sep 9 '14 at 13:35
Jignesh PatelJignesh Patel
11
add a comment |
I also had the same problem. So i uninstalled iptux and removed all the files related to iptux in the system. Then i reinstalled iptux and it worked.
edited Oct 28 '14 at 13:24
Community♦
1
answered Jul 8 '13 at 6:26
rohitrounakrohitrounak
1
1
Welcome to Ask Ubuntu rohitrounak! Even though your answer attempts to answer the question, it would be better to add the actual steps on how you did this, as in the actual commands. This is so that (1) you can help other people that don't know the commands, and (2) the person that asked the question seems to have already tried reinstalling IPTUX, but maybe you did more actions than what he did. You can edit your answer and include the steps.
– Alaa Ali
Jul 8 '13 at 7:18
add a comment |
I faced same issue and didn't found ~/.gconf/apps/iptux/%gconf.xml file.
But I fixed the it.
First locate iptux installation directory,
locate iptux
search for line /something/something/.iptux/config.json
Edit this line in file,
"hide_startup" : true,
true to false.
Or any other option you need.
answered Jan 4 at 13:32
user910446user910446
1
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%2f156995%2fiptux-always-runs-in-background%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
I am stuck in the same situation but I know one thing for sure that you can modify the %gconf.xml file directly using
sudo nano <config file path>/%gconf.xml
which should be located in any of the following locations
~/.cache/iptux
~/.gconf/apps/iptux
~/.config/iptux
I did modify the file but when I restart the system it seems to have reverted back to the original.
The entry in the file that you need to look for, to modify is:
name="hide_startup" mtime="1343670281" type="bool" value="true"
change it to:
name="hide_startup" mtime="1343670281" type="bool" value="false"
I believe, the reason for the file reverting back to the previous state is that iptux process must be running in the background and hence not allowing changes to the file.
What I am looking for is a way to kill the iptux process before modifying the config file, but can't find a process for iptux.
Will research it a bit and let you know if I find the process name.
What I found out was, that you cannot stop iptux as it doesn't have a process of its own but relies on other processes (won't get in depth here) but My solution would be to start Ubuntu in repair mode, by pressing F8 a bit after the bios screen disappears (before the Ubuntu Loading Screen) and select repair... or was it recovery mode... but you get the idea. You can then use the terminal to modify the file. In this way iptux won't have started and the file should be modified fine.
– exIT Solutions
Jul 31 '12 at 13:19
Let me know how it goes. I can't try this as my issue is a step up... I am having the issue on the Thin Client rather than the server. I'll probably try to shutdown the thin client then modify the config file.
– exIT Solutions
Jul 31 '12 at 13:20
Yep, that worked for me. Guess you'll have to logout of your profile and log in as administrator or root (not recommended) then modify the file or start terminal in so called safe mode or recovery mode
– exIT Solutions
Jul 31 '12 at 13:29
What I found out was it doesn't matter if iptux is running in the background but so as long as the profile (login) that is creating the problem is not in use or locked. What this means is that if you simply log out and log in as another user or admin you should be able to modify the problem profile's iptux config file (xml)
– exIT Solutions
Jul 31 '12 at 13:32
I suggest to use sudo nano /home/<your username>/<iptux config file path>/%gconf.xml and modify to false as discussed earlier.
– exIT Solutions
Aug 1 '12 at 1:19
add a comment |
I am stuck in the same situation but I know one thing for sure that you can modify the %gconf.xml file directly using
sudo nano <config file path>/%gconf.xml
which should be located in any of the following locations
~/.cache/iptux
~/.gconf/apps/iptux
~/.config/iptux
I did modify the file but when I restart the system it seems to have reverted back to the original.
The entry in the file that you need to look for, to modify is:
name="hide_startup" mtime="1343670281" type="bool" value="true"
change it to:
name="hide_startup" mtime="1343670281" type="bool" value="false"
I believe, the reason for the file reverting back to the previous state is that iptux process must be running in the background and hence not allowing changes to the file.
What I am looking for is a way to kill the iptux process before modifying the config file, but can't find a process for iptux.
Will research it a bit and let you know if I find the process name.
What I found out was, that you cannot stop iptux as it doesn't have a process of its own but relies on other processes (won't get in depth here) but My solution would be to start Ubuntu in repair mode, by pressing F8 a bit after the bios screen disappears (before the Ubuntu Loading Screen) and select repair... or was it recovery mode... but you get the idea. You can then use the terminal to modify the file. In this way iptux won't have started and the file should be modified fine.
– exIT Solutions
Jul 31 '12 at 13:19
Let me know how it goes. I can't try this as my issue is a step up... I am having the issue on the Thin Client rather than the server. I'll probably try to shutdown the thin client then modify the config file.
– exIT Solutions
Jul 31 '12 at 13:20
Yep, that worked for me. Guess you'll have to logout of your profile and log in as administrator or root (not recommended) then modify the file or start terminal in so called safe mode or recovery mode
– exIT Solutions
Jul 31 '12 at 13:29
What I found out was it doesn't matter if iptux is running in the background but so as long as the profile (login) that is creating the problem is not in use or locked. What this means is that if you simply log out and log in as another user or admin you should be able to modify the problem profile's iptux config file (xml)
– exIT Solutions
Jul 31 '12 at 13:32
I suggest to use sudo nano /home/<your username>/<iptux config file path>/%gconf.xml and modify to false as discussed earlier.
– exIT Solutions
Aug 1 '12 at 1:19
add a comment |
I am stuck in the same situation but I know one thing for sure that you can modify the %gconf.xml file directly using
sudo nano <config file path>/%gconf.xml
which should be located in any of the following locations
~/.cache/iptux
~/.gconf/apps/iptux
~/.config/iptux
I did modify the file but when I restart the system it seems to have reverted back to the original.
The entry in the file that you need to look for, to modify is:
name="hide_startup" mtime="1343670281" type="bool" value="true"
change it to:
name="hide_startup" mtime="1343670281" type="bool" value="false"
I believe, the reason for the file reverting back to the previous state is that iptux process must be running in the background and hence not allowing changes to the file.
What I am looking for is a way to kill the iptux process before modifying the config file, but can't find a process for iptux.
Will research it a bit and let you know if I find the process name.
I am stuck in the same situation but I know one thing for sure that you can modify the %gconf.xml file directly using
sudo nano <config file path>/%gconf.xml
which should be located in any of the following locations
~/.cache/iptux
~/.gconf/apps/iptux
~/.config/iptux
I did modify the file but when I restart the system it seems to have reverted back to the original.
The entry in the file that you need to look for, to modify is:
name="hide_startup" mtime="1343670281" type="bool" value="true"
change it to:
name="hide_startup" mtime="1343670281" type="bool" value="false"
I believe, the reason for the file reverting back to the previous state is that iptux process must be running in the background and hence not allowing changes to the file.
What I am looking for is a way to kill the iptux process before modifying the config file, but can't find a process for iptux.
Will research it a bit and let you know if I find the process name.
edited Aug 1 '12 at 9:00
community wiki
4 revs, 2 users 81%
exIT Solutions
What I found out was, that you cannot stop iptux as it doesn't have a process of its own but relies on other processes (won't get in depth here) but My solution would be to start Ubuntu in repair mode, by pressing F8 a bit after the bios screen disappears (before the Ubuntu Loading Screen) and select repair... or was it recovery mode... but you get the idea. You can then use the terminal to modify the file. In this way iptux won't have started and the file should be modified fine.
– exIT Solutions
Jul 31 '12 at 13:19
Let me know how it goes. I can't try this as my issue is a step up... I am having the issue on the Thin Client rather than the server. I'll probably try to shutdown the thin client then modify the config file.
– exIT Solutions
Jul 31 '12 at 13:20
Yep, that worked for me. Guess you'll have to logout of your profile and log in as administrator or root (not recommended) then modify the file or start terminal in so called safe mode or recovery mode
– exIT Solutions
Jul 31 '12 at 13:29
What I found out was it doesn't matter if iptux is running in the background but so as long as the profile (login) that is creating the problem is not in use or locked. What this means is that if you simply log out and log in as another user or admin you should be able to modify the problem profile's iptux config file (xml)
– exIT Solutions
Jul 31 '12 at 13:32
I suggest to use sudo nano /home/<your username>/<iptux config file path>/%gconf.xml and modify to false as discussed earlier.
– exIT Solutions
Aug 1 '12 at 1:19
add a comment |
What I found out was, that you cannot stop iptux as it doesn't have a process of its own but relies on other processes (won't get in depth here) but My solution would be to start Ubuntu in repair mode, by pressing F8 a bit after the bios screen disappears (before the Ubuntu Loading Screen) and select repair... or was it recovery mode... but you get the idea. You can then use the terminal to modify the file. In this way iptux won't have started and the file should be modified fine.
– exIT Solutions
Jul 31 '12 at 13:19
Let me know how it goes. I can't try this as my issue is a step up... I am having the issue on the Thin Client rather than the server. I'll probably try to shutdown the thin client then modify the config file.
– exIT Solutions
Jul 31 '12 at 13:20
Yep, that worked for me. Guess you'll have to logout of your profile and log in as administrator or root (not recommended) then modify the file or start terminal in so called safe mode or recovery mode
– exIT Solutions
Jul 31 '12 at 13:29
What I found out was it doesn't matter if iptux is running in the background but so as long as the profile (login) that is creating the problem is not in use or locked. What this means is that if you simply log out and log in as another user or admin you should be able to modify the problem profile's iptux config file (xml)
– exIT Solutions
Jul 31 '12 at 13:32
I suggest to use sudo nano /home/<your username>/<iptux config file path>/%gconf.xml and modify to false as discussed earlier.
– exIT Solutions
Aug 1 '12 at 1:19
What I found out was, that you cannot stop iptux as it doesn't have a process of its own but relies on other processes (won't get in depth here) but My solution would be to start Ubuntu in repair mode, by pressing F8 a bit after the bios screen disappears (before the Ubuntu Loading Screen) and select repair... or was it recovery mode... but you get the idea. You can then use the terminal to modify the file. In this way iptux won't have started and the file should be modified fine.
– exIT Solutions
Jul 31 '12 at 13:19
What I found out was, that you cannot stop iptux as it doesn't have a process of its own but relies on other processes (won't get in depth here) but My solution would be to start Ubuntu in repair mode, by pressing F8 a bit after the bios screen disappears (before the Ubuntu Loading Screen) and select repair... or was it recovery mode... but you get the idea. You can then use the terminal to modify the file. In this way iptux won't have started and the file should be modified fine.
– exIT Solutions
Jul 31 '12 at 13:19
Let me know how it goes. I can't try this as my issue is a step up... I am having the issue on the Thin Client rather than the server. I'll probably try to shutdown the thin client then modify the config file.
– exIT Solutions
Jul 31 '12 at 13:20
Let me know how it goes. I can't try this as my issue is a step up... I am having the issue on the Thin Client rather than the server. I'll probably try to shutdown the thin client then modify the config file.
– exIT Solutions
Jul 31 '12 at 13:20
Yep, that worked for me. Guess you'll have to logout of your profile and log in as administrator or root (not recommended) then modify the file or start terminal in so called safe mode or recovery mode
– exIT Solutions
Jul 31 '12 at 13:29
Yep, that worked for me. Guess you'll have to logout of your profile and log in as administrator or root (not recommended) then modify the file or start terminal in so called safe mode or recovery mode
– exIT Solutions
Jul 31 '12 at 13:29
What I found out was it doesn't matter if iptux is running in the background but so as long as the profile (login) that is creating the problem is not in use or locked. What this means is that if you simply log out and log in as another user or admin you should be able to modify the problem profile's iptux config file (xml)
– exIT Solutions
Jul 31 '12 at 13:32
What I found out was it doesn't matter if iptux is running in the background but so as long as the profile (login) that is creating the problem is not in use or locked. What this means is that if you simply log out and log in as another user or admin you should be able to modify the problem profile's iptux config file (xml)
– exIT Solutions
Jul 31 '12 at 13:32
I suggest to use sudo nano /home/<your username>/<iptux config file path>/%gconf.xml and modify to false as discussed earlier.
– exIT Solutions
Aug 1 '12 at 1:19
I suggest to use sudo nano /home/<your username>/<iptux config file path>/%gconf.xml and modify to false as discussed earlier.
– exIT Solutions
Aug 1 '12 at 1:19
add a comment |
I also had the same problem. The solution was as specified by exIT Solutions is :
First locate the
%gconf.xmlfile in your pc. Mine was in~/.gconf/apps/iptux/%gconf.xml.
Edit it with any Text Editor.Second search for the line:
entry name="hide_startup" mtime="1410256594" type="bool" value="true"
and changed it to:
entry name="hide_startup" mtime="1410256594" type="bool" value="false"
Save the file and logout. After logging in I started iptux and it worked fine.
edited Sep 9 '14 at 14:01
Luís de Sousa
9,0441752100
answered Sep 9 '14 at 13:35
Jignesh PatelJignesh Patel
11
add a comment |
I also had the same problem. The solution was as specified by exIT Solutions is :
First locate the
%gconf.xmlfile in your pc. Mine was in~/.gconf/apps/iptux/%gconf.xml.
Edit it with any Text Editor.Second search for the line:
entry name="hide_startup" mtime="1410256594" type="bool" value="true"
and changed it to:
entry name="hide_startup" mtime="1410256594" type="bool" value="false"
Save the file and logout. After logging in I started iptux and it worked fine.
edited Sep 9 '14 at 14:01
Luís de Sousa
9,0441752100
answered Sep 9 '14 at 13:35
Jignesh PatelJignesh Patel
11
add a comment |
I also had the same problem. The solution was as specified by exIT Solutions is :
First locate the
%gconf.xmlfile in your pc. Mine was in~/.gconf/apps/iptux/%gconf.xml.
Edit it with any Text Editor.Second search for the line:
entry name="hide_startup" mtime="1410256594" type="bool" value="true"
and changed it to:
entry name="hide_startup" mtime="1410256594" type="bool" value="false"
Save the file and logout. After logging in I started iptux and it worked fine.
edited Sep 9 '14 at 14:01
Luís de Sousa
9,0441752100
answered Sep 9 '14 at 13:35
Jignesh PatelJignesh Patel
11
I also had the same problem. The solution was as specified by exIT Solutions is :
First locate the
%gconf.xmlfile in your pc. Mine was in~/.gconf/apps/iptux/%gconf.xml.
Edit it with any Text Editor.Second search for the line:
entry name="hide_startup" mtime="1410256594" type="bool" value="true"
and changed it to:
entry name="hide_startup" mtime="1410256594" type="bool" value="false"
Save the file and logout. After logging in I started iptux and it worked fine.
edited Sep 9 '14 at 14:01
Luís de Sousa
9,0441752100
answered Sep 9 '14 at 13:35
Jignesh PatelJignesh Patel
11
edited Sep 9 '14 at 14:01
Luís de Sousa
9,0441752100
edited Sep 9 '14 at 14:01
Luís de Sousa
9,0441752100
edited Sep 9 '14 at 14:01
Luís de Sousa
9,0441752100
9,0441752100
answered Sep 9 '14 at 13:35
Jignesh PatelJignesh Patel
11
answered Sep 9 '14 at 13:35
Jignesh PatelJignesh Patel
11
answered Sep 9 '14 at 13:35
Jignesh PatelJignesh Patel
11
11
add a comment |
add a comment |
I also had the same problem. So i uninstalled iptux and removed all the files related to iptux in the system. Then i reinstalled iptux and it worked.
edited Oct 28 '14 at 13:24
Community♦
1
answered Jul 8 '13 at 6:26
rohitrounakrohitrounak
1
1
Welcome to Ask Ubuntu rohitrounak! Even though your answer attempts to answer the question, it would be better to add the actual steps on how you did this, as in the actual commands. This is so that (1) you can help other people that don't know the commands, and (2) the person that asked the question seems to have already tried reinstalling IPTUX, but maybe you did more actions than what he did. You can edit your answer and include the steps.
– Alaa Ali
Jul 8 '13 at 7:18
add a comment |
I also had the same problem. So i uninstalled iptux and removed all the files related to iptux in the system. Then i reinstalled iptux and it worked.
edited Oct 28 '14 at 13:24
Community♦
1
answered Jul 8 '13 at 6:26
rohitrounakrohitrounak
1
1
Welcome to Ask Ubuntu rohitrounak! Even though your answer attempts to answer the question, it would be better to add the actual steps on how you did this, as in the actual commands. This is so that (1) you can help other people that don't know the commands, and (2) the person that asked the question seems to have already tried reinstalling IPTUX, but maybe you did more actions than what he did. You can edit your answer and include the steps.
– Alaa Ali
Jul 8 '13 at 7:18
add a comment |
I also had the same problem. So i uninstalled iptux and removed all the files related to iptux in the system. Then i reinstalled iptux and it worked.
edited Oct 28 '14 at 13:24
Community♦
1
answered Jul 8 '13 at 6:26
rohitrounakrohitrounak
1
I also had the same problem. So i uninstalled iptux and removed all the files related to iptux in the system. Then i reinstalled iptux and it worked.
edited Oct 28 '14 at 13:24
Community♦
1
answered Jul 8 '13 at 6:26
rohitrounakrohitrounak
1
edited Oct 28 '14 at 13:24
Community♦
1
edited Oct 28 '14 at 13:24
Community♦
1
edited Oct 28 '14 at 13:24
Community♦
1
1
answered Jul 8 '13 at 6:26
rohitrounakrohitrounak
1
answered Jul 8 '13 at 6:26
rohitrounakrohitrounak
1
answered Jul 8 '13 at 6:26
rohitrounakrohitrounak
1
1
1
Welcome to Ask Ubuntu rohitrounak! Even though your answer attempts to answer the question, it would be better to add the actual steps on how you did this, as in the actual commands. This is so that (1) you can help other people that don't know the commands, and (2) the person that asked the question seems to have already tried reinstalling IPTUX, but maybe you did more actions than what he did. You can edit your answer and include the steps.
– Alaa Ali
Jul 8 '13 at 7:18
add a comment |
1
Welcome to Ask Ubuntu rohitrounak! Even though your answer attempts to answer the question, it would be better to add the actual steps on how you did this, as in the actual commands. This is so that (1) you can help other people that don't know the commands, and (2) the person that asked the question seems to have already tried reinstalling IPTUX, but maybe you did more actions than what he did. You can edit your answer and include the steps.
– Alaa Ali
Jul 8 '13 at 7:18
1
1
Welcome to Ask Ubuntu rohitrounak! Even though your answer attempts to answer the question, it would be better to add the actual steps on how you did this, as in the actual commands. This is so that (1) you can help other people that don't know the commands, and (2) the person that asked the question seems to have already tried reinstalling IPTUX, but maybe you did more actions than what he did. You can edit your answer and include the steps.
– Alaa Ali
Jul 8 '13 at 7:18
Welcome to Ask Ubuntu rohitrounak! Even though your answer attempts to answer the question, it would be better to add the actual steps on how you did this, as in the actual commands. This is so that (1) you can help other people that don't know the commands, and (2) the person that asked the question seems to have already tried reinstalling IPTUX, but maybe you did more actions than what he did. You can edit your answer and include the steps.
– Alaa Ali
Jul 8 '13 at 7:18
add a comment |
I faced same issue and didn't found ~/.gconf/apps/iptux/%gconf.xml file.
But I fixed the it.
First locate iptux installation directory,
locate iptux
search for line /something/something/.iptux/config.json
Edit this line in file,
"hide_startup" : true,
true to false.
Or any other option you need.
answered Jan 4 at 13:32
user910446user910446
1
add a comment |
I faced same issue and didn't found ~/.gconf/apps/iptux/%gconf.xml file.
But I fixed the it.
First locate iptux installation directory,
locate iptux
search for line /something/something/.iptux/config.json
Edit this line in file,
"hide_startup" : true,
true to false.
Or any other option you need.
answered Jan 4 at 13:32
user910446user910446
1
add a comment |
I faced same issue and didn't found ~/.gconf/apps/iptux/%gconf.xml file.
But I fixed the it.
First locate iptux installation directory,
locate iptux
search for line /something/something/.iptux/config.json
Edit this line in file,
"hide_startup" : true,
true to false.
Or any other option you need.
answered Jan 4 at 13:32
user910446user910446
1
I faced same issue and didn't found ~/.gconf/apps/iptux/%gconf.xml file.
But I fixed the it.
First locate iptux installation directory,
locate iptux
search for line /something/something/.iptux/config.json
Edit this line in file,
"hide_startup" : true,
true to false.
Or any other option you need.
answered Jan 4 at 13:32
user910446user910446
1
answered Jan 4 at 13:32
user910446user910446
1
answered Jan 4 at 13:32
user910446user910446
1
answered Jan 4 at 13:32
user910446user910446
1
1
add a comment |
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%2f156995%2fiptux-always-runs-in-background%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
