tomreyn | dropheaders: things will be different startinng 20.04 LTS: https://discourse.ubuntu.com/t/ubuntu-20-04-lts-survey/13616 https://discourse.ubuntu.com/t/server-installer-plans-for-20-04-lts/13631 | 05:44 |
---|---|---|
tomreyn | err not the survey link but this one https://discourse.ubuntu.com/t/please-review-design-for-automated-server-installs/11923 | 05:45 |
dropheaders | oh nice | 06:29 |
dropheaders | thank you | 06:29 |
lordievader | Good morning | 07:14 |
=== aditya is now known as adityaduggal | ||
=== adityaduggal_ is now known as adityaduggal | ||
=== lotuspsychje_ is now known as lotuspsychje | ||
=== cpaelzer__ is now known as cpaelzer | ||
yildizabdullah | I use Ubuntu Server (18.04.3 LTS) | 10:40 |
yildizabdullah | I cannot access gnome-terminal via VNC session | 10:40 |
yildizabdullah | There is an error as "Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling StartServiceByName for org.gnome.Terminal: Timeout was reached" | 10:41 |
yildizabdullah | in VNC log file | 10:41 |
yildizabdullah | My VNC xstartup file includes | 10:41 |
yildizabdullah | gnome-panel &gnome-settings-daemon &metacity &nautilus & | 10:41 |
yildizabdullah | sorry | 10:42 |
yildizabdullah | gnome-panel & | 10:42 |
yildizabdullah | gnome-settings-daemon & | 10:42 |
yildizabdullah | metacity & | 10:42 |
yildizabdullah | nautilus & | 10:42 |
yildizabdullah | I also get the following error when I start my VNC session | 10:42 |
yildizabdullah | gnome-settings-daemon: command not found | 10:43 |
yildizabdullah | I've already installed gnome-settings-daemon | 10:43 |
yildizabdullah | How can I fix this? | 10:43 |
weedmic | yildizabdullah: is the server setup to: allow vnc connections, does the connector have an account on the server, does the server have gnome installed, there are a lot of possible problems. can you connect with the same user via ssh? if yes, that would narrow some things down. | 10:43 |
yildizabdullah | It was working yesterday | 10:44 |
yildizabdullah | Yes, I can connect to the machine via SSH | 10:44 |
weedmic | same user via ssh, but not vnc? and it worked same user yesterday? sounds like you may need to restart the VNC daemon on the server - but this is untrue if others can use VNC, then it sounds like an rights issue. | 10:46 |
yildizabdullah | I can open a VNC session, see my Desktop and access the filesystem from file explorer menu | 10:46 |
yildizabdullah | How can I post my log file here? | 10:47 |
yildizabdullah | Is there an easy way | 10:47 |
weedmic | so you see a "terminal" when you connect, if yes, did you try "startx" to get the desktop environment to start | 10:47 |
yildizabdullah | No, | 10:48 |
yildizabdullah | there is no terminal menu | 10:48 |
weedmic | then what did you mean by "my Desktop and access the filesystem" "Desktop"? | 10:48 |
yildizabdullah | sorry for misunderstanding | 10:49 |
yildizabdullah | I can see my Desktop | 10:49 |
yildizabdullah | and open emacs, gvim, etc. | 10:49 |
weedmic | what do you mean by "Desktop"? | 10:49 |
yildizabdullah | I see a toolbar at the top of the screen which only shows Applications and Places | 10:50 |
weedmic | do you mean that you do reach the server and gnome is working and that is what you mean by "desktop" - that you see gnome? | 10:50 |
yildizabdullah | I only see these two menu items | 10:50 |
weedmic | so gnome is working on remote server, but you are missing two "menu items" or "icons" - and they were there yesterday? if yes, which two items? | 10:51 |
yildizabdullah | https://i.stack.imgur.com/S8feZ.png | 10:53 |
yildizabdullah | This is a screenshot of my screen | 10:53 |
weedmic | interesting, looks like "x" loads, but not the desktop environment. is this remote server a VM? | 10:55 |
yildizabdullah | It is a VM and runs on top VMware vSphere | 10:56 |
weedmic | It may go away by rebooting the VM. I have only seen this on VM servers running on windoze hosts. | 10:56 |
yildizabdullah | I tried rebooting VM dozens of times | 10:57 |
yildizabdullah | https://pasteboard.co/IS2TG3U.png | 10:58 |
yildizabdullah | This is the VNC log file | 10:58 |
weedmic | interesting - try #vbox (if it is virtualbox) - ppl there are pretty good at this. I know nothing of windows and have not used it in aeons. To me I believe you have a problem with the VM. | 10:58 |
yildizabdullah | OK thanks | 10:59 |
[fre] | Hello Guys, tomreyn, ... ;) | 11:01 |
weedmic | #vbox may be able to help you fix the VM - or at least help you prove it either is or is not the VM. | 11:01 |
[fre] | After checking the md5sum of the ISO-live-server 18.4.3... it seems I have the good download of a not booting VM. | 11:04 |
[fre] | The ISO keeps booting with a kernel panick, unable to unpack the initramfs. | 11:04 |
[fre] | on VMware that is. | 11:04 |
weedmic | when installing the media on the VM - did you pick the right environment / and simulated HW? | 11:06 |
[fre] | most probably, yes. :) It's pretty basic... I'll verify after noon. Just wondering what else I could have chosen that may block it. | 11:27 |
lordievader | [fre]: How is the ISO presented in the VM? | 11:32 |
weedmic | with this, the temperature of "what" is being measured/reported (by sensors)? https://pastebin.com/GVni4J9u | 11:35 |
tomreyn | cpu cores, or i'm not getting the question right. | 11:37 |
weedmic | I also thought it was the CPUs, but that isa adapter thing threw me off. I also don't get why it only counts some, there are 20 cores 40 threads, but I just figured they did not all have sensors. tomreyn | 12:14 |
=== Wryhder is now known as Lucas_Gray | ||
=== Wryhder is now known as Lucas_Gray | ||
weedmic | If I were to delete ~/.cache/, and there is a directory in there called "systemsettings", I should lose all my icon placements, and other systemsettings? or is it just some temporary cache data that is really unimporant as those sets are saved in a .conf file? | 15:54 |
weedmic | delete not the directory, but the contents and subdirectories under .cashe/ - i was unclear | 15:56 |
lordievader | Cache should be cache. If the programmer respected that is something else. A safe way of testing this is renaming/moving the folder. | 16:45 |
[fre] | lordievader, tomreyn. It was caused by a machine that had been created with too small RAM. :) Ramdisk wasn't entirely extractable in RAM. (seems 256M is not enough these times :D ). | 17:05 |
tomreyn | [fre]: thanks for reporting back, and yes, your systems and VMs should comply with the documented minimum requirements. ;) | 17:39 |
sdeziel | 256M is a bit cramped indeed but if you use the -virtual kernel, IIRC that was still bootable | 17:45 |
sdeziel | [fre]: I have a small Bionic VM with 232MB assigned, runs decently OK ;) | 17:46 |
sdeziel | https://paste.ubuntu.com/p/TvNR4MRd6j/ nginx is super light in RAM ;) | 17:47 |
=== Futurian_ is now known as Futurian |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!