Installing Google Chrome Remote Desktop messed up my box
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I was playing around with Chrome Remote Desktop and after a restart of my Ubuntu Gnome 17.04 box, things got really weird. First, I was prompted for a second entry of my password. Then, all my Google Chrome extensions were reset. And, finally, I noticed that I had no sound whatsoever.
After digging around in the audio settings, I discovered the following:
It looks like the original sound output was switched over to Chrome Remote Desktop with no option to reset it. Overall my computer felt like I was logged into a guest setting.
How the heck do I fix this?
sound google-chrome
edited Nov 2 '17 at 8:01
Bilesh Ganguly
306111
asked Oct 10 '17 at 22:21
tclicktclick
7916
add a comment |
I was playing around with Chrome Remote Desktop and after a restart of my Ubuntu Gnome 17.04 box, things got really weird. First, I was prompted for a second entry of my password. Then, all my Google Chrome extensions were reset. And, finally, I noticed that I had no sound whatsoever.
After digging around in the audio settings, I discovered the following:
It looks like the original sound output was switched over to Chrome Remote Desktop with no option to reset it. Overall my computer felt like I was logged into a guest setting.
How the heck do I fix this?
sound google-chrome
edited Nov 2 '17 at 8:01
Bilesh Ganguly
306111
asked Oct 10 '17 at 22:21
tclicktclick
7916
add a comment |
I was playing around with Chrome Remote Desktop and after a restart of my Ubuntu Gnome 17.04 box, things got really weird. First, I was prompted for a second entry of my password. Then, all my Google Chrome extensions were reset. And, finally, I noticed that I had no sound whatsoever.
After digging around in the audio settings, I discovered the following:
It looks like the original sound output was switched over to Chrome Remote Desktop with no option to reset it. Overall my computer felt like I was logged into a guest setting.
How the heck do I fix this?
sound google-chrome
edited Nov 2 '17 at 8:01
Bilesh Ganguly
306111
asked Oct 10 '17 at 22:21
tclicktclick
7916
I was playing around with Chrome Remote Desktop and after a restart of my Ubuntu Gnome 17.04 box, things got really weird. First, I was prompted for a second entry of my password. Then, all my Google Chrome extensions were reset. And, finally, I noticed that I had no sound whatsoever.
After digging around in the audio settings, I discovered the following:
It looks like the original sound output was switched over to Chrome Remote Desktop with no option to reset it. Overall my computer felt like I was logged into a guest setting.
How the heck do I fix this?
sound google-chrome
sound google-chrome
edited Nov 2 '17 at 8:01
Bilesh Ganguly
306111
asked Oct 10 '17 at 22:21
tclicktclick
7916
edited Nov 2 '17 at 8:01
Bilesh Ganguly
306111
asked Oct 10 '17 at 22:21
tclicktclick
7916
edited Nov 2 '17 at 8:01
Bilesh Ganguly
306111
edited Nov 2 '17 at 8:01
Bilesh Ganguly
306111
edited Nov 2 '17 at 8:01
Bilesh Ganguly
306111
306111
asked Oct 10 '17 at 22:21
tclicktclick
7916
asked Oct 10 '17 at 22:21
tclicktclick
7916
asked Oct 10 '17 at 22:21
tclicktclick
7916
7916
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
This is what I did to fix the same issue. This way you don't have to restart your machine:
sudo rm -rf ~/.config/chrome-remote-desktop
killall pulseaudio
pulseaudio --start
gnome-shell --replace
It was also affecting my Gnome Apps. I was mad because I spent hours thinking it was because of my Yubikey since it's a U2F/FIDO2 Security Key. So I made sure to be forceful. I hope this is a cure-all for some folks until Google can make some fixes, I sent a feedback report to them about this.
edited Feb 14 at 7:37
Class
1035
answered Apr 27 '18 at 20:31
Dillyn BarberDillyn Barber
7113
This guy is a life saver.
– Dennis
Nov 23 '18 at 6:48
1
I got very irritated when my gome-terminal would not start anymore and had not noticed the sound issues. Your remark on other Gnome Apps being affected was helpful!
– alexurba
Dec 1 '18 at 13:13
You are seriously a god among men. No CTRL+ALT+T terminal hot key response. No audio devices except for Chrome Remote Desktop 'sink'. And it was asking for a duplicate key-ring password on every log-in. I was just about to reinstall ubuntu from scratch which takes me hours after configuring everything and reinstalling apps and cloning code repos. Thank you so so so much for saving me from having to go through all of that trouble from the bottom of my heart. I had no idea what was wrong with Ubuntu but I knew it was a serious configuration issue that I wouldn't be able to personally sort out.
– anon58192932
Jan 1 at 20:52
this: killall pulseaudio pulseaduio --start is enough for 16.04 with unity
– ses
Jan 16 at 18:23
add a comment |
There is some problem with Chrome Remote Desktop with Ubuntu. To get your system sound back for all applications you should remove the extension from both Chrome and Ubuntu.
Run the following command:
sudo apt-get remove chrome-remote-desktop
and restart Ubuntu.
edited Jan 20 '18 at 18:00
Chai T. Rex
4,20711536
answered Jan 20 '18 at 17:51
Gambheer SinghGambheer Singh
212
add a comment |
I found that by removing (rather, renaming) the ~/.config/chrome-remote-desktop directory and restarting, my sound defaulted to the standard line out.
answered Dec 29 '17 at 1:41
user776434user776434
111
add a comment |
I used this command to refresh the devices.
pacmd unload-module module-udev-detect && pacmd load-module module-udev-detect
It did the job, the sound test worked. Although, I was still not able to hear the sound in Chrome (YouTube or Hangouts, for example).
At least for now I ended up uninstalling Chrome remote desktop from my machine.
edited Jan 20 '18 at 17:59
Chai T. Rex
4,20711536
answered Nov 2 '17 at 6:24
Simonas BalciusSimonas Balcius
111
add a comment |
Somehow I manage to make the audio work in Ubuntu 18.04 with Chrome Remote Desktop still installed, by creating file .chrome-remote-desktop-session in user folder
cd ~
touch .chrome-remote-desktop-session
and put this lines to the file
unset PULSE_CONFIG_PATH
unset PULSE_RUNTIME_PATH
unset PULSE_SINK
unset PULSE_STATE_PATH
DESKTOP_SESSION=ubuntu XDG_CURRENT_DESKTOP=Unity /usr/sbin/lightdm-session 'gnome-session --session=ubuntu'
I don't know if restarting ubuntu is required or not, but I realize this works after reboot
Ref: https://bugs.chromium.org/p/chromium/issues/detail?id=496885
answered Oct 21 '18 at 0:37
obladaobladiobladaobladi
112
This worked very well for me. Even the gnome-terminal started showing up again.
– shaoyl85
Dec 3 '18 at 23:45
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%2f963756%2finstalling-google-chrome-remote-desktop-messed-up-my-box%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is what I did to fix the same issue. This way you don't have to restart your machine:
sudo rm -rf ~/.config/chrome-remote-desktop
killall pulseaudio
pulseaudio --start
gnome-shell --replace
It was also affecting my Gnome Apps. I was mad because I spent hours thinking it was because of my Yubikey since it's a U2F/FIDO2 Security Key. So I made sure to be forceful. I hope this is a cure-all for some folks until Google can make some fixes, I sent a feedback report to them about this.
edited Feb 14 at 7:37
Class
1035
answered Apr 27 '18 at 20:31
Dillyn BarberDillyn Barber
7113
This guy is a life saver.
– Dennis
Nov 23 '18 at 6:48
1
I got very irritated when my gome-terminal would not start anymore and had not noticed the sound issues. Your remark on other Gnome Apps being affected was helpful!
– alexurba
Dec 1 '18 at 13:13
You are seriously a god among men. No CTRL+ALT+T terminal hot key response. No audio devices except for Chrome Remote Desktop 'sink'. And it was asking for a duplicate key-ring password on every log-in. I was just about to reinstall ubuntu from scratch which takes me hours after configuring everything and reinstalling apps and cloning code repos. Thank you so so so much for saving me from having to go through all of that trouble from the bottom of my heart. I had no idea what was wrong with Ubuntu but I knew it was a serious configuration issue that I wouldn't be able to personally sort out.
– anon58192932
Jan 1 at 20:52
this: killall pulseaudio pulseaduio --start is enough for 16.04 with unity
– ses
Jan 16 at 18:23
add a comment |
This is what I did to fix the same issue. This way you don't have to restart your machine:
sudo rm -rf ~/.config/chrome-remote-desktop
killall pulseaudio
pulseaudio --start
gnome-shell --replace
It was also affecting my Gnome Apps. I was mad because I spent hours thinking it was because of my Yubikey since it's a U2F/FIDO2 Security Key. So I made sure to be forceful. I hope this is a cure-all for some folks until Google can make some fixes, I sent a feedback report to them about this.
edited Feb 14 at 7:37
Class
1035
answered Apr 27 '18 at 20:31
Dillyn BarberDillyn Barber
7113
This guy is a life saver.
– Dennis
Nov 23 '18 at 6:48
1
I got very irritated when my gome-terminal would not start anymore and had not noticed the sound issues. Your remark on other Gnome Apps being affected was helpful!
– alexurba
Dec 1 '18 at 13:13
You are seriously a god among men. No CTRL+ALT+T terminal hot key response. No audio devices except for Chrome Remote Desktop 'sink'. And it was asking for a duplicate key-ring password on every log-in. I was just about to reinstall ubuntu from scratch which takes me hours after configuring everything and reinstalling apps and cloning code repos. Thank you so so so much for saving me from having to go through all of that trouble from the bottom of my heart. I had no idea what was wrong with Ubuntu but I knew it was a serious configuration issue that I wouldn't be able to personally sort out.
– anon58192932
Jan 1 at 20:52
this: killall pulseaudio pulseaduio --start is enough for 16.04 with unity
– ses
Jan 16 at 18:23
add a comment |
This is what I did to fix the same issue. This way you don't have to restart your machine:
sudo rm -rf ~/.config/chrome-remote-desktop
killall pulseaudio
pulseaudio --start
gnome-shell --replace
It was also affecting my Gnome Apps. I was mad because I spent hours thinking it was because of my Yubikey since it's a U2F/FIDO2 Security Key. So I made sure to be forceful. I hope this is a cure-all for some folks until Google can make some fixes, I sent a feedback report to them about this.
edited Feb 14 at 7:37
Class
1035
answered Apr 27 '18 at 20:31
Dillyn BarberDillyn Barber
7113
This is what I did to fix the same issue. This way you don't have to restart your machine:
sudo rm -rf ~/.config/chrome-remote-desktop
killall pulseaudio
pulseaudio --start
gnome-shell --replace
It was also affecting my Gnome Apps. I was mad because I spent hours thinking it was because of my Yubikey since it's a U2F/FIDO2 Security Key. So I made sure to be forceful. I hope this is a cure-all for some folks until Google can make some fixes, I sent a feedback report to them about this.
edited Feb 14 at 7:37
Class
1035
answered Apr 27 '18 at 20:31
Dillyn BarberDillyn Barber
7113
edited Feb 14 at 7:37
Class
1035
edited Feb 14 at 7:37
Class
1035
edited Feb 14 at 7:37
Class
1035
1035
answered Apr 27 '18 at 20:31
Dillyn BarberDillyn Barber
7113
answered Apr 27 '18 at 20:31
Dillyn BarberDillyn Barber
7113
answered Apr 27 '18 at 20:31
Dillyn BarberDillyn Barber
7113
7113
This guy is a life saver.
– Dennis
Nov 23 '18 at 6:48
1
I got very irritated when my gome-terminal would not start anymore and had not noticed the sound issues. Your remark on other Gnome Apps being affected was helpful!
– alexurba
Dec 1 '18 at 13:13
You are seriously a god among men. No CTRL+ALT+T terminal hot key response. No audio devices except for Chrome Remote Desktop 'sink'. And it was asking for a duplicate key-ring password on every log-in. I was just about to reinstall ubuntu from scratch which takes me hours after configuring everything and reinstalling apps and cloning code repos. Thank you so so so much for saving me from having to go through all of that trouble from the bottom of my heart. I had no idea what was wrong with Ubuntu but I knew it was a serious configuration issue that I wouldn't be able to personally sort out.
– anon58192932
Jan 1 at 20:52
this: killall pulseaudio pulseaduio --start is enough for 16.04 with unity
– ses
Jan 16 at 18:23
add a comment |
This guy is a life saver.
– Dennis
Nov 23 '18 at 6:48
1
I got very irritated when my gome-terminal would not start anymore and had not noticed the sound issues. Your remark on other Gnome Apps being affected was helpful!
– alexurba
Dec 1 '18 at 13:13
You are seriously a god among men. No CTRL+ALT+T terminal hot key response. No audio devices except for Chrome Remote Desktop 'sink'. And it was asking for a duplicate key-ring password on every log-in. I was just about to reinstall ubuntu from scratch which takes me hours after configuring everything and reinstalling apps and cloning code repos. Thank you so so so much for saving me from having to go through all of that trouble from the bottom of my heart. I had no idea what was wrong with Ubuntu but I knew it was a serious configuration issue that I wouldn't be able to personally sort out.
– anon58192932
Jan 1 at 20:52
this: killall pulseaudio pulseaduio --start is enough for 16.04 with unity
– ses
Jan 16 at 18:23
This guy is a life saver.
– Dennis
Nov 23 '18 at 6:48
This guy is a life saver.
– Dennis
Nov 23 '18 at 6:48
1
1
I got very irritated when my gome-terminal would not start anymore and had not noticed the sound issues. Your remark on other Gnome Apps being affected was helpful!
– alexurba
Dec 1 '18 at 13:13
I got very irritated when my gome-terminal would not start anymore and had not noticed the sound issues. Your remark on other Gnome Apps being affected was helpful!
– alexurba
Dec 1 '18 at 13:13
You are seriously a god among men. No CTRL+ALT+T terminal hot key response. No audio devices except for Chrome Remote Desktop 'sink'. And it was asking for a duplicate key-ring password on every log-in. I was just about to reinstall ubuntu from scratch which takes me hours after configuring everything and reinstalling apps and cloning code repos. Thank you so so so much for saving me from having to go through all of that trouble from the bottom of my heart. I had no idea what was wrong with Ubuntu but I knew it was a serious configuration issue that I wouldn't be able to personally sort out.
– anon58192932
Jan 1 at 20:52
You are seriously a god among men. No CTRL+ALT+T terminal hot key response. No audio devices except for Chrome Remote Desktop 'sink'. And it was asking for a duplicate key-ring password on every log-in. I was just about to reinstall ubuntu from scratch which takes me hours after configuring everything and reinstalling apps and cloning code repos. Thank you so so so much for saving me from having to go through all of that trouble from the bottom of my heart. I had no idea what was wrong with Ubuntu but I knew it was a serious configuration issue that I wouldn't be able to personally sort out.
– anon58192932
Jan 1 at 20:52
this: killall pulseaudio pulseaduio --start is enough for 16.04 with unity
– ses
Jan 16 at 18:23
this: killall pulseaudio pulseaduio --start is enough for 16.04 with unity
– ses
Jan 16 at 18:23
add a comment |
There is some problem with Chrome Remote Desktop with Ubuntu. To get your system sound back for all applications you should remove the extension from both Chrome and Ubuntu.
Run the following command:
sudo apt-get remove chrome-remote-desktop
and restart Ubuntu.
edited Jan 20 '18 at 18:00
Chai T. Rex
4,20711536
answered Jan 20 '18 at 17:51
Gambheer SinghGambheer Singh
212
add a comment |
There is some problem with Chrome Remote Desktop with Ubuntu. To get your system sound back for all applications you should remove the extension from both Chrome and Ubuntu.
Run the following command:
sudo apt-get remove chrome-remote-desktop
and restart Ubuntu.
edited Jan 20 '18 at 18:00
Chai T. Rex
4,20711536
answered Jan 20 '18 at 17:51
Gambheer SinghGambheer Singh
212
add a comment |
There is some problem with Chrome Remote Desktop with Ubuntu. To get your system sound back for all applications you should remove the extension from both Chrome and Ubuntu.
Run the following command:
sudo apt-get remove chrome-remote-desktop
and restart Ubuntu.
edited Jan 20 '18 at 18:00
Chai T. Rex
4,20711536
answered Jan 20 '18 at 17:51
Gambheer SinghGambheer Singh
212
There is some problem with Chrome Remote Desktop with Ubuntu. To get your system sound back for all applications you should remove the extension from both Chrome and Ubuntu.
Run the following command:
sudo apt-get remove chrome-remote-desktop
and restart Ubuntu.
edited Jan 20 '18 at 18:00
Chai T. Rex
4,20711536
answered Jan 20 '18 at 17:51
Gambheer SinghGambheer Singh
212
edited Jan 20 '18 at 18:00
Chai T. Rex
4,20711536
edited Jan 20 '18 at 18:00
Chai T. Rex
4,20711536
edited Jan 20 '18 at 18:00
Chai T. Rex
4,20711536
4,20711536
answered Jan 20 '18 at 17:51
Gambheer SinghGambheer Singh
212
answered Jan 20 '18 at 17:51
Gambheer SinghGambheer Singh
212
answered Jan 20 '18 at 17:51
Gambheer SinghGambheer Singh
212
212
add a comment |
add a comment |
I found that by removing (rather, renaming) the ~/.config/chrome-remote-desktop directory and restarting, my sound defaulted to the standard line out.
answered Dec 29 '17 at 1:41
user776434user776434
111
add a comment |
I found that by removing (rather, renaming) the ~/.config/chrome-remote-desktop directory and restarting, my sound defaulted to the standard line out.
answered Dec 29 '17 at 1:41
user776434user776434
111
add a comment |
I found that by removing (rather, renaming) the ~/.config/chrome-remote-desktop directory and restarting, my sound defaulted to the standard line out.
answered Dec 29 '17 at 1:41
user776434user776434
111
I found that by removing (rather, renaming) the ~/.config/chrome-remote-desktop directory and restarting, my sound defaulted to the standard line out.
answered Dec 29 '17 at 1:41
user776434user776434
111
answered Dec 29 '17 at 1:41
user776434user776434
111
answered Dec 29 '17 at 1:41
user776434user776434
111
answered Dec 29 '17 at 1:41
user776434user776434
111
111
add a comment |
add a comment |
I used this command to refresh the devices.
pacmd unload-module module-udev-detect && pacmd load-module module-udev-detect
It did the job, the sound test worked. Although, I was still not able to hear the sound in Chrome (YouTube or Hangouts, for example).
At least for now I ended up uninstalling Chrome remote desktop from my machine.
edited Jan 20 '18 at 17:59
Chai T. Rex
4,20711536
answered Nov 2 '17 at 6:24
Simonas BalciusSimonas Balcius
111
add a comment |
I used this command to refresh the devices.
pacmd unload-module module-udev-detect && pacmd load-module module-udev-detect
It did the job, the sound test worked. Although, I was still not able to hear the sound in Chrome (YouTube or Hangouts, for example).
At least for now I ended up uninstalling Chrome remote desktop from my machine.
edited Jan 20 '18 at 17:59
Chai T. Rex
4,20711536
answered Nov 2 '17 at 6:24
Simonas BalciusSimonas Balcius
111
add a comment |
I used this command to refresh the devices.
pacmd unload-module module-udev-detect && pacmd load-module module-udev-detect
It did the job, the sound test worked. Although, I was still not able to hear the sound in Chrome (YouTube or Hangouts, for example).
At least for now I ended up uninstalling Chrome remote desktop from my machine.
edited Jan 20 '18 at 17:59
Chai T. Rex
4,20711536
answered Nov 2 '17 at 6:24
Simonas BalciusSimonas Balcius
111
I used this command to refresh the devices.
pacmd unload-module module-udev-detect && pacmd load-module module-udev-detect
It did the job, the sound test worked. Although, I was still not able to hear the sound in Chrome (YouTube or Hangouts, for example).
At least for now I ended up uninstalling Chrome remote desktop from my machine.
edited Jan 20 '18 at 17:59
Chai T. Rex
4,20711536
answered Nov 2 '17 at 6:24
Simonas BalciusSimonas Balcius
111
edited Jan 20 '18 at 17:59
Chai T. Rex
4,20711536
edited Jan 20 '18 at 17:59
Chai T. Rex
4,20711536
edited Jan 20 '18 at 17:59
Chai T. Rex
4,20711536
4,20711536
answered Nov 2 '17 at 6:24
Simonas BalciusSimonas Balcius
111
answered Nov 2 '17 at 6:24
Simonas BalciusSimonas Balcius
111
answered Nov 2 '17 at 6:24
Simonas BalciusSimonas Balcius
111
111
add a comment |
add a comment |
Somehow I manage to make the audio work in Ubuntu 18.04 with Chrome Remote Desktop still installed, by creating file .chrome-remote-desktop-session in user folder
cd ~
touch .chrome-remote-desktop-session
and put this lines to the file
unset PULSE_CONFIG_PATH
unset PULSE_RUNTIME_PATH
unset PULSE_SINK
unset PULSE_STATE_PATH
DESKTOP_SESSION=ubuntu XDG_CURRENT_DESKTOP=Unity /usr/sbin/lightdm-session 'gnome-session --session=ubuntu'
I don't know if restarting ubuntu is required or not, but I realize this works after reboot
Ref: https://bugs.chromium.org/p/chromium/issues/detail?id=496885
answered Oct 21 '18 at 0:37
obladaobladiobladaobladi
112
This worked very well for me. Even the gnome-terminal started showing up again.
– shaoyl85
Dec 3 '18 at 23:45
add a comment |
Somehow I manage to make the audio work in Ubuntu 18.04 with Chrome Remote Desktop still installed, by creating file .chrome-remote-desktop-session in user folder
cd ~
touch .chrome-remote-desktop-session
and put this lines to the file
unset PULSE_CONFIG_PATH
unset PULSE_RUNTIME_PATH
unset PULSE_SINK
unset PULSE_STATE_PATH
DESKTOP_SESSION=ubuntu XDG_CURRENT_DESKTOP=Unity /usr/sbin/lightdm-session 'gnome-session --session=ubuntu'
I don't know if restarting ubuntu is required or not, but I realize this works after reboot
Ref: https://bugs.chromium.org/p/chromium/issues/detail?id=496885
answered Oct 21 '18 at 0:37
obladaobladiobladaobladi
112
This worked very well for me. Even the gnome-terminal started showing up again.
– shaoyl85
Dec 3 '18 at 23:45
add a comment |
Somehow I manage to make the audio work in Ubuntu 18.04 with Chrome Remote Desktop still installed, by creating file .chrome-remote-desktop-session in user folder
cd ~
touch .chrome-remote-desktop-session
and put this lines to the file
unset PULSE_CONFIG_PATH
unset PULSE_RUNTIME_PATH
unset PULSE_SINK
unset PULSE_STATE_PATH
DESKTOP_SESSION=ubuntu XDG_CURRENT_DESKTOP=Unity /usr/sbin/lightdm-session 'gnome-session --session=ubuntu'
I don't know if restarting ubuntu is required or not, but I realize this works after reboot
Ref: https://bugs.chromium.org/p/chromium/issues/detail?id=496885
answered Oct 21 '18 at 0:37
obladaobladiobladaobladi
112
Somehow I manage to make the audio work in Ubuntu 18.04 with Chrome Remote Desktop still installed, by creating file .chrome-remote-desktop-session in user folder
cd ~
touch .chrome-remote-desktop-session
and put this lines to the file
unset PULSE_CONFIG_PATH
unset PULSE_RUNTIME_PATH
unset PULSE_SINK
unset PULSE_STATE_PATH
DESKTOP_SESSION=ubuntu XDG_CURRENT_DESKTOP=Unity /usr/sbin/lightdm-session 'gnome-session --session=ubuntu'
I don't know if restarting ubuntu is required or not, but I realize this works after reboot
Ref: https://bugs.chromium.org/p/chromium/issues/detail?id=496885
answered Oct 21 '18 at 0:37
obladaobladiobladaobladi
112
edited Oct 21 '18 at 0:51
answered Oct 21 '18 at 0:37
obladaobladiobladaobladi
112
answered Oct 21 '18 at 0:37
obladaobladiobladaobladi
112
answered Oct 21 '18 at 0:37
obladaobladiobladaobladi
112
112
This worked very well for me. Even the gnome-terminal started showing up again.
– shaoyl85
Dec 3 '18 at 23:45
add a comment |
This worked very well for me. Even the gnome-terminal started showing up again.
– shaoyl85
Dec 3 '18 at 23:45
This worked very well for me. Even the gnome-terminal started showing up again.
– shaoyl85
Dec 3 '18 at 23:45
This worked very well for me. Even the gnome-terminal started showing up again.
– shaoyl85
Dec 3 '18 at 23:45
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%2f963756%2finstalling-google-chrome-remote-desktop-messed-up-my-box%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
