new to linux/ubuntu. need help big problem can p.@.y some one for solution
 

bascily this is a short version of a longest post im still waiting to get posted by this site. i have a nitro 5 laptop runing Ubuntu 18.04.1 LTS but i dont think its running well im missing activies menu and bar. also i have 10 white lines of text on start up.

will pay some one with experience to fix these problems for me. so that means figuring out the text at start up. (cause it moves to fast to write down). and solving them. m system is running UEFI boot. has 2 gpus(which always cause problems in my experience. they are rx550 and the integrated one with the processor ///AMD® Fx-9830p radeon r7, 12 compute cores 4c+8g × 4 ///)also have ssd and hdd. and yeah hope some one can help!! thanks

No one here works for money, so you'll probably get some dusty answers on that! However I can give you one or two hints on how to troubleshoot this for yourself.

First, what reason do you have to think that what you see on startup are error messages? Most distros show some informative text during boot. You can recover this information by looking at the system logs in /var/log. The main one will be your systemd journal, viewable using the journlctl command; the journalctl man page will tell you how to use it. Most distros also bleed off some of the journal information into text logs such as boot.log (the log of the current boot), and sys.log, kern.log or messages (which are cumulative files). If these are present, you can view them in any editor or text viewer.

The absent features that you describe would be part of your graphical desktop, so that's probably where your problem lies and not in the underlying system. You haven't said what desktop you are using; is it Unity? I think that's the default for Ubuntu. Give us some more information and someone can help you find a solution. But remember, this isn't a help desk and no one here is at your beck and call.

Just for info, Ubuntu switched back to Gnome as the default desktop environment for 18.04. Of course the OP may be using something else.

triple (!) post of
https://www.linuxquestions.org/quest...on-4175642510/
and
https://www.linuxquestions.org/quest...ts-4175642512/

When hazel wrote 'journlctl', I think she meant 'journalctl' (at least, that's what worked on my machine with Ubuntu 18.04). hazel: thanks for the info -- I didn't know that command.

Thanks for the correction! That was a typo on my part. The journalctl command is quite interesting because it has options to filter information, for example displaying lines relevant to a particular daemon process. With text logs, you just have to scan through them. On the other hand, most people prefer text logs because you can always access them without needing a special program to do so.

hi guys thanks for the reply. just for your information i have a masters degree in using google search. cant find any file or folder named var. then again i dont know if my OS installed completely from the youtube videos ive seen i should have stuff on the left on my desktop. i will post a reply when i get round to the rest of the things you have said to try.
many thanks
sean

here is a bunch of stuff from another post. its basicy same question. i did some commands

<pre><font color="#8AE234"><b>sean1@sean1-Nitro-AN515-41</b></font>:<font color="#729FCF"><b>~</b></font>$ uname -rvm
4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64
<font color="#8AE234"><b>sean1@sean1-Nitro-AN515-41</b></font>:<font color="#729FCF"><b>~</b></font>$ cat /etc/*release*
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION=&quot;Ubuntu 18.04.1 LTS&quot;
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION=&quot;Ubuntu*GamePack 16.04 UALinux&quot;
NAME=&quot;Ubuntu&quot;
VERSION=&quot;18.04.1 LTS (Bionic Beaver)&quot;
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=&quot;Ubuntu 18.04.1 LTS&quot;
VERSION_ID=&quot;18.04&quot;
HOME_URL=&quot;https://www.ubuntu.com/&quot;
SUPPORT_URL=&quot;https://help.ubuntu.com/&quot;
BUG_REPORT_URL=&quot;https://bugs.launchpad.net/ubuntu/&quot;
PRIVACY_POLICY_URL=&quot;https://www.ubuntu.com/legal/terms-a...y-policy&quot;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
<font color="#8AE234"><b>sean1@sean1-Nitro-AN515-41</b></font>:<font color="#729FCF"><b>~</b></font>$ lspci -k
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1576
Subsystem: Acer Incorporated [ALI] Device 1213
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 1577
Subsystem: Acer Incorporated [ALI] Device 1213
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo (rev cc)
Subsystem: Acer Incorporated [ALI] Carrizo
Kernel driver in use: amdgpu
Kernel modules: amdgpu
00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Kabini HDMI/DP Audio
Subsystem: Acer Incorporated [ALI] Kabini HDMI/DP Audio
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 157b
00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 157c
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 157c
Kernel driver in use: pcieport
Kernel modules: shpchp
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 157b
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 157c
Kernel driver in use: pcieport
Kernel modules: shpchp
00:08.0 Encryption controller: Advanced Micro Devices, Inc. [AMD] Device 1578
Subsystem: Acer Incorporated [ALI] Device 1213
00:09.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 157d
00:09.2 Audio device: Advanced Micro Devices, Inc. [AMD] Device 157a
Subsystem: Acer Incorporated [ALI] Device 1213
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 20)
Subsystem: Acer Incorporated [ALI] FCH USB XHCI Controller
Kernel driver in use: xhci_hcd
00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 49)
Subsystem: Acer Incorporated [ALI] FCH SATA Controller [AHCI mode]
Kernel driver in use: ahci
Kernel modules: ahci
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 49)
Subsystem: Acer Incorporated [ALI] FCH USB EHCI Controller
Kernel driver in use: ehci-pci
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 4a)
Subsystem: Acer Incorporated [ALI] FCH SMBus Controller
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11)
Subsystem: Acer Incorporated [ALI] FCH LPC Bridge
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1570
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1571
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1572
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1573
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1574
Kernel driver in use: fam15h_power
Kernel modules: fam15h_power
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 1575
01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01)
Subsystem: Acer Incorporated [ALI] RTL8411B PCI Express Card Reader
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
01:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
Subsystem: Acer Incorporated [ALI] RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Kernel driver in use: r8169
Kernel modules: r8169
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
Subsystem: Lite-On Communications Inc QCA6174 802.11ac Wireless Network Adapter
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Polaris12 (rev ff)
Kernel driver in use: amdgpu
Kernel modules: amdgpu
<font color="#8AE234"><b>sean1@sean1-Nitro-AN515-41</b></font>:<font color="#729FCF"><b>~</b></font>$ journalctl -b
-- Logs begin at Thu 2018-11-15 17:33:27 GMT, end at Sun 2018-11-18 16:44:02 GMT. --
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: <b>Linux version 4.15.0-39-generic (buildd@lgw01-amd64-054) (gcc version 7.3.0 (U</b>
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=cc6206be-ad
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: KERNEL supported cpus:
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: Intel GenuineIntel
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: AMD AuthenticAMD
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: Centaur CentaurHauls
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: [Firmware Info]: CPU: Re-enabling disabled Topology Extensions Support.
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: x86/fpu: Supporting XSAVE feature 0x001: &apos;x87 floating point registers&apos;
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: x86/fpu: Supporting XSAVE feature 0x002: &apos;SSE registers&apos;
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: x86/fpu: Supporting XSAVE feature 0x004: &apos;AVX registers&apos;
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using &apos;standa
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: e820: BIOS-provided physical RAM map:
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000086fff] usable
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: BIOS-e820: [mem 0x0000000000087000-0x0000000000087fff] reserved
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: BIOS-e820: [mem 0x0000000000088000-0x000000000009ffff] usable
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000bffff] reserved
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000b93b4fff] usable
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: BIOS-e820: [mem 0x00000000b93b5000-0x00000000b9db4fff] ACPI NVS
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: BIOS-e820: [mem 0x00000000b9db5000-0x00000000befbdfff] usable
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: BIOS-e820: [mem 0x00000000befbe000-0x00000000bf1bdfff] type 20
Nov 18 16:21:09 sean1-Nitro-AN515-41 kernel: BIOS-e820: [mem 0x00000000bf1be000-0x00000000bf8bdfff] reserved
<span style="background-color:#FFFFFF"><font color="#300A24">lines 1-23</font></span>
</pre>

Absolute paths to files must begin with "/" to indicate that the path starts with the root directory. You need to go to "/var", not "var". It must be there. I never heard of a Linux distro that didn't have a /var directory.

do i search with the thing in the top right? or do i need to type this in a terminal. i am new to ubuntu. but so far no luck in finding this var. i tryed searching in system settings also in places/ home

wow i found some thing eles in my menu just called logs i clicked it and read this 16:21:21 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
16:21:21 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
16:21:13 lightdm: PAM adding faulty module: pam_kwallet5.so
16:21:13 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
16:21:12 wpa_supplicant: dbus: Failed to construct signal
16:21:12 lightdm: PAM adding faulty module: pam_kwallet5.so
16:21:11 bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
16:21:11 kernel: dell_smbios: Unable to run on non-Dell system
16:21:09 kernel: [drm:dc_create [amdgpu]] *ERROR* DC: Number of connectors is zero!
16:21:09 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched
16:21:09 kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!
16:21:09 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2!
16:21:09 kernel: Problem loading UEFI:db X.509 certificate (-65)
16:21:09 kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xbfbb9000-0xbfbbcfff]

also found this . still cant see var folder.

Nov 18 18:14:33 sean1-Nitro-AN515-41 nm-applet[1980]: Can't set a parent on widget which has a parent
Nov 18 18:14:33 sean1-Nitro-AN515-41 nm-applet[1980]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 18 18:14:33 sean1-Nitro-AN515-41 nm-applet[1980]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 18 18:14:33 sean1-Nitro-AN515-41 nm-applet[1980]: Can't set a parent on widget which has a parent
Nov 18 18:14:36 sean1-Nitro-AN515-41 gnome-panel.desktop[1845]: RuntimeError: object at 0x7f4e598dc7d0 of type FolderColorMenu is not initialized
Nov 18 18:14:40 sean1-Nitro-AN515-41 gnome-panel.desktop[1845]: message repeated 8 times: [ RuntimeError: object at 0x7f4e598dc7d0 of type FolderColorMenu is not initialized]
Nov 18 18:15:08 sean1-Nitro-AN515-41 gnome-panel.desktop[1845]: main.go:192: cannot change mount namespace of snap "gnome-logs" according to change mount (/snap/gtk-common-themes/818/share/icons/Suru /snap/gnome-logs/45/data-dir/icons/Suru none bind,ro 0 0): cannot use "/snap/gtk-common-themes/818/share/icons/Suru" as bind-mount source: not a directory
Nov 18 18:15:11 sean1-Nitro-AN515-41 gnome-panel.desktop[1845]: Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", line 10: Having multiple values in <test> isn't supported and may not work as expected
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6319.627245] [drm] RBRx2 pass VS=1, PE=0
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6860.878865] kauditd_printk_skb: 30 callbacks suppressed
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6860.878868] audit: type=1400 audit(1542564925.665:42): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/proc/5068/mountinfo" pid=5068 comm="gmain" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6860.879083] audit: type=1400 audit(1542564925.665:43): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/etc/fstab" pid=5068 comm="gnome-logs" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6860.879119] audit: type=1400 audit(1542564925.665:44): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/proc/5068/mountinfo" pid=5068 comm="gnome-logs" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6860.879161] audit: type=1400 audit(1542564925.665:45): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/proc/5068/mounts" pid=5068 comm="gnome-logs" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:25 sean1-Nitro-AN515-41 gnome-logs[5068]: Error creating IO channel for /proc/self/mountinfo: Permission denied (g-file-error-quark, 2)
Nov 18 18:15:25 sean1-Nitro-AN515-41 dbus-daemon[938]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.138' (uid=1000 pid=5068 comm="gnome-logs " label="snap.gnome-logs.gnome-logs (enforce)")
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6861.058616] audit: type=1400 audit(1542564925.845:46): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/proc/5068/mountinfo" pid=5068 comm="gnome-logs" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6861.058623] audit: type=1400 audit(1542564925.845:47): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/proc/5068/mounts" pid=5068 comm="gnome-logs" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:25 sean1-Nitro-AN515-41 systemd[1]: Starting Hostname Service...
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6861.068306] audit: type=1400 audit(1542564925.857:48): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/home/sean1/.bashrc" pid=5068 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6861.068353] audit: type=1400 audit(1542564925.857:49): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/home/sean1/.bash_logout" pid=5068 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6861.068403] audit: type=1400 audit(1542564925.857:50): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/home/sean1/.profile" pid=5068 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:25 sean1-Nitro-AN515-41 kernel: [ 6861.068433] audit: type=1400 audit(1542564925.857:51): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/home/sean1/.kshrc" pid=5068 comm="pool" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:26 sean1-Nitro-AN515-41 dbus-daemon[938]: [system] Successfully activated service 'org.freedesktop.hostname1'
Nov 18 18:15:26 sean1-Nitro-AN515-41 systemd[1]: Started Hostname Service.
Nov 18 18:15:44 sean1-Nitro-AN515-41 kernel: [ 6879.247067] kauditd_printk_skb: 16 callbacks suppressed
Nov 18 18:15:44 sean1-Nitro-AN515-41 kernel: [ 6879.247070] audit: type=1400 audit(1542564944.033:68): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/proc/5068/mountinfo" pid=5068 comm="gnome-logs" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:44 sean1-Nitro-AN515-41 kernel: [ 6879.247076] audit: type=1400 audit(1542564944.033:69): apparmor="DENIED" operation="open" profile="snap.gnome-logs.gnome-logs" name="/proc/5068/mounts" pid=5068 comm="gnome-logs" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
Nov 18 18:15:44 sean1-Nitro-AN515-41 nautilus-classic.desktop[1862]: RuntimeError: object at 0x7f60eabeb7d0 of type FolderColorMenu is not initialized
Nov 18 18:16:04 sean1-Nitro-AN515-41 nautilus-classic.desktop[1862]: message repeated 3 times: [ RuntimeError: object at 0x7f60eabeb7d0 of type FolderColorMenu is not initialized]
Nov 18 18:17:01 sean1-Nitro-AN515-41 CRON[5293]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 18 18:17:01 sean1-Nitro-AN515-41 kernel: [ 6956.856372] memclean (5295): drop_caches: 1
Nov 18 18:17:01 sean1-Nitro-AN515-41 kernel: [ 6956.892131] memclean (5295): drop_caches: 2
Nov 18 18:17:01 sean1-Nitro-AN515-41 kernel: [ 6956.931875] memclean (5295): drop_caches: 3
Nov 18 18:17:25 sean1-Nitro-AN515-41 nautilus-classic.desktop[1862]: RuntimeError: object at 0x7f60eabeb7d0 of type FolderColorMenu is not initialized
Nov 18 18:18:31 sean1-Nitro-AN515-41 nautilus-classic.desktop[1862]: message repeated 3 times: [ RuntimeError: object at 0x7f60eabeb7d0 of type FolderColorMenu is not initialized]
Nov 18 18:18:44 sean1-Nitro-AN515-41 dbus-daemon[1406]: [session uid=1000 pid=1406] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.137' (uid=1000 pid=5399 comm="/usr/bin/gnome-terminal.real " label="unconfined")
Nov 18 18:18:44 sean1-Nitro-AN515-41 systemd[1334]: Starting GNOME Terminal Server...
Nov 18 18:18:44 sean1-Nitro-AN515-41 dbus-daemon[1406]: [session uid=1000 pid=1406] Successfully activated service 'org.gnome.Terminal'
Nov 18 18:18:44 sean1-Nitro-AN515-41 systemd[1334]: Started GNOME Terminal Server.
Nov 18 18:18:59 sean1-Nitro-AN515-41 nautilus-classic.desktop[1862]: RuntimeError: object at 0x7f60eabeb7d0 of type FolderColorMenu is not initialized
Nov 18 18:19:17 sean1-Nitro-AN515-41 nm-applet[1980]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 18 18:19:17 sean1-Nitro-AN515-41 nm-applet[1980]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 18 18:19:17 sean1-Nitro-AN515-41 nm-applet[1980]: Can't set a parent on widget which has a parent
Nov 18 18:19:22 sean1-Nitro-AN515-41 nautilus-classic.desktop[1862]: RuntimeError: object at 0x7f60eabeb7d0 of type FolderColorMenu is not initialized
Nov 18 18:21:41 sean1-Nitro-AN515-41 nautilus-classic.desktop[1862]: RuntimeError: object at 0x7f60eabeb7d0 of type FolderColorMenu is not initialized
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: g_action_print_detailed_name: assertion 'g_action_name_is_valid (action_name)' failed
Nov 18 18:21:55 sean1-Nitro-AN515-41 gnome-system-lo[5442]: gtk_application_set_accels_for_action: assertion 'detailed_action_name != NULL' failed
Nov 18 18:21:58 sean1-Nitro-AN515-41 nm-applet[1980]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 18 18:21:58 sean1-Nitro-AN515-41 nm-applet[1980]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 18 18:21:58 sean1-Nitro-AN515-41 nm-applet[1980]: Can't set a parent on widget which has a parent
Nov 18 18:21:58 sean1-Nitro-AN515-41 nm-applet[1980]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 18 18:21:58 sean1-Nitro-AN515-41 nm-applet[1980]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Nov 18 18:21:58 sean1-Nitro-AN515-41 nm-applet[1980]: Can't set a parent on widget which has a parent
Nov 18 18:22:01 sean1-Nitro-AN515-41 wpa_supplicant[954]: wlp2s0: WPA: Group rekeying completed with 42:9b:cd:93:07:60 [GTK=TKIP]

Slow down, will you! You are floundering about like a fish in a net, trying to do several things at once. I suggested looking in the logs because you were worried about some startup messages that you couldn't read but thought might be errors. I am pretty sure they are not errors. The missing items that you describe in your first post indicate a gnome configuration problem and not something wrong with your basic system that would show up at boot. You need to understand that in Linux, unlike Windows, the graphical desktop is quite separate from the underlying system. Unfortunately gnome is a large complex desktop and I don't use it so I can't help you there. There are other people here who can.

Now as regards the file system. You had better get to know it if you want to be confident in using Linux. Unlike in Windows, the whole file system is yours to explore. It's like a house: if you have lost something at home, you know what room it is likely to be in. You don't look for a missing kitchen knife in the bathroom! In the same way, things in Linux tend to be found in particular places. The main directories like /var and /home are like rooms.

You have a graphical file manager (nautilus) to explore your filesystem, or you can open a terminal. I haven't used nautilus for a long time but I seem to remember that it had a left-hand window with a schematic tree of the locations, while the right-hand window showed the files. Try Filesystem on the left side (not Places: that will take you to only a few special folders). Or in a terminal, type (for example) "cd /var" to get to the var directory. Or just use the log reading facility that you have found on your menu. Those logs are situated in /var, whether you believe it or not!

By the way, when you post a lot of output please put it between code tags. It's almost unreadable otherwise.

im going to try a different iso. what is best for support to fix laptop? im missing nautilus i dont have it. can you give me a example of what u mean between code tages. sorry i am very desperate to fix laptop...

In 'advanced mode' highlight th text and click on the '#' symbol. That will wrap the text you've highlighted inside code tags, so that it displays in an easier to read format. Or you can do it manually:
will display as

i dont know what advance mode is. i will watch youtube for it.


i have reinstalled linux with iso from offical download. seems better i got stuff on left now. like the bar. also didnt see as many white text in start up


this is in important logs folder.
23:57:15 wpa_supplicant: dbus: Failed to construct signal

23:57:12 dhclient: receive_packet failed on wlp2s0: Network is down

23:51:26 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

23:51:25 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files

23:51:13 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

23:51:10 wpa_supplicant: dbus: Failed to construct signal

23:51:08 kernel: dell_smbios: Unable to run on non-Dell system

23:51:08 kernel: [drm:dc_create [amdgpu]] *ERROR* DC: Number of connectors is zero!

23:51:08 kernel: amdgpu: [powerplay] Voltage value looks like a Leakage ID but it's not patched

23:51:08 kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!

23:51:08 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2!

23:51:08 kernel: Couldn't get size: 0x800000000000000e

23:51:08 kernel: Problem loading UEFI:db X.509 certificate (-65)

23:51:08 kernel: tpm_crb MSFT0101:00: can't request region for resource [mem 0xbfbb9000-0xbfbbcfff]



duno why there is dell stuff. i have acer laptop.. amd cpu and gpu

When you do a quick post in this forum, there are two buttons at the bottom of the text window. One says "Post Quick Reply" and the other says "Go Advanced". If you press the second one, you get a lot of extra formatting options.

Don't watch YouTube so much. There is an awful lot of bad info out there. People are always screwing up their systems doing things they saw on YouTube and then we have to help them clear up the mess. When you are working in Linux, work slowly and systematically. Don't panic. Don't do anything if you don't know what you are doing or why you are doing it. Collect information, work out where the problem is likely to lie, then get help to solve it. And don't try to fix several things at once. There's plenty of time.

You get all sorts of odd messages in log files, especially systemd log files. Don't take them too seriously.