What is the problem to this? (I tried in Ubuntu and worked perfectly)




EDIT: Same problem updating

I had 2 goes at installing LL 4.0 on my laptop (previously on 3.x). Seems to be working well now, thanks. Some good improvements. I'm still getting to grips with the system, so please excuse any mistakes.

I don't see anything that indicates Linux Lite during the bootup process. I do have a black screen during some of the bootup, and it has a sort of animated progress wheel near the center bottom. Is that normal? Is it the new bootup screen? If so, it is a nice improvement on the yellow screen with feather. But I'm confused because I don't have anything to indicate LL on bootup.

I also don't see any indication of where the current boot splash screen background is located in the file system. Does anyone know where it is? In 3.x it was in /usr/share/plymouth/themes/liteboot/ but now there is no liteboot folder.

Is what I'm seeing normal for LL 4.0?

Greetings! I have just installed a fresh new copy of Linux Lite 4.0 and it's great so far. I only ran in a couple of issues, most of which I have worked around, but this one...

Whenever I watch an HTML5 video in fullscreen (YouTube, Gfycat, etc), when I click the fullscreen button after watching a video, the Firefox windows goes back to an unmaximized window state, despite the window being maximized before going in fullscreen. It doesn't happen in Chromium, it didn't happen in Linux Lite 3.8, so... any help would be very, very welcome!

Also, in case the fix is easy... evince throws me segmentation faults whenever I try to start it. I'm using okular instead for now and it works fine, it's just not as lightweight...

Thank you for reading!

MS already is a substantial user of github so not much of a surprise, but still kinda sad in some ways.

https://www.bloomberg.com/news/articles/...ite-github

TC

Hi, all is working and looking great so far, except for this delay seemingly related to the time it takes the video card to inicialize.

I have a HP Pavilion-dv7t-4100 notebook:
Intel i7 with 8 GB RAM, 128 GB SSD

In lspci the vga card shows> [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M]

The same notebook with Lite 3.8 would take a total of about 17 seconds to boot up

Now in Lite 4.0 takes about 50.

After a little playing around with systemd-analyze, dmesg, etc

I found out that if I change this line in grub:

from: GRUB_CMDLINE_LINUX=""

to:    GRUB_CMDLINE_LINUX="radeon.modeset=0""

I "get back" those extra 30 seconds...

(but it seems that the video card is not accelerated with this option enabled)

I don't know how the Lite 3.8 handled the Video Card... but if I could just make Lite 4.0 deal with the card the previous way ... may be I could make it boot faster.

This is what I get if I issue the command: dmesg | grep radeon

Quote:dmesg | grep radeon
[    4.427994] [drm] radeon kernel modesetting enabled.
[    4.428141] fb: switching to radeondrmfb from VESA VGA
[    4.429269] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[    4.429274] radeon 0000:01:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
[    4.429441] [drm] radeon: 1024M of VRAM memory ready
[    4.429442] [drm] radeon: 1024M of GTT memory ready.
[    4.463948] [drm] radeon: dpm initialized
[    4.467027] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[    4.488005] radeon 0000:01:00.0: WB enabled
[    4.488012] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0x000000008d69b640
[    4.488017] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0x000000000303539b
[    4.488744] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c418 and cpu addr 0x000000000419b92b
[    4.488754] radeon 0000:01:00.0: radeon: MSI limited to 32-bit
[    4.488840] radeon 0000:01:00.0: radeon: using MSI.
[    4.488894] [drm] radeon: irq initialized.
[    5.404166] [drm] radeon atom DIG backlight initialized
[    6.300528] fbcon: radeondrmfb (fb0) is primary device
[    6.300767] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[    6.387026] [drm] Initialized radeon 2.50.0 20080528 for 0000:01:00.0 on minor 0
[  64.483228] Modules linked in: ccm binfmt_misc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_hda_codec_idt btusb videobuf2_core btrtl snd_hda_codec_generic snd_hda_codec_hdmi btbcm arc4 btintel videodev iwldvm snd_hda_intel bluetooth snd_hda_codec mac80211 media snd_hda_core intel_powerclamp snd_hwdep coretemp ecdh_generic snd_pcm kvm snd_seq_midi irqbypass snd_seq_midi_event intel_cstate iwlwifi snd_rawmidi hp_wmi input_leds joydev snd_seq sparse_keymap wmi_bmof serio_raw snd_seq_device i7core_edac snd_timer cfg80211 snd hp_accel mei_me soundcore shpchp mei lpc_ich lis3lv02d input_polldev mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq dm_mirror dm_region_hash dm_log radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect

Hi to All guys ,

I have an Atheros AR9287 chipset.
I have a problem with the WIFI connection after a fresh  V4.0 install.
The problem is that after inserted the password to connect to DHCP server the system try to connect succesfully just for a second or Two and then disconnect. after this it tries to connect and disconnect infinitely .

I give a sight to system log ( but i'm not an expert ) and seem to see something related to WLAN hard blocked . I also don't know how to hold the messages in log view and stop scrolling.

Could any one give me a hand to solve this problem. Thanks

PS with V3.8 I didnt have any problem with WIFI. All worked fine.

I installed 4.0 yesterday, and the only problem is with boot time. Seems slower than 3.8. I tried removing Virtual Box as suggested in Release Notes, but I'm not sure I did it correctly. It didn't help in any case. I simply pasted the commands into Terminal and ran them. But they were multiple commands, and I've never been sure of what to do with "Code-Select." If this was wrong, how should I go about doing this?

mike

Got these errors when running update from welcome screen:

Hit:1 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Ign:2 http://ppa.launchpad.net/abiword-stable/ppa/ubuntu bionic InRelease
Hit:3 http://repo.linuxliteos.com/linuxlite diamond InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu bionic-security InRelease
Hit:5 http://archive.canonical.com/ubuntu bionic InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease
Hit:7 http://ppa.launchpad.net/apandada1/brigh...ler/ubuntu bionic InRelease
Hit:8 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease
Hit:9 http://ppa.launchpad.net/otto-kesselgulasch/gimp/ubuntu bionic InRelease
Hit:10 http://ppa.launchpad.net/teejee2008/ppa/ubuntu bionic InRelease
Err:11 http://ppa.launchpad.net/abiword-stable/ppa/ubuntu bionic Release
  404  Not Found [IP: 91.189.95.83 80]
Reading package lists...
E: The repository 'http://ppa.launchpad.net/abiword-stable/ppa/ubuntu bionic Release' does not have a Release file.

I decided after some problems to go for LL 4.0 Did want to stay with 3.8 but rather then do notting i am trying to get the problems solved.
The installation worked fine, system boots but there are 2 problems i cant get solved and need some help with.

1st problem is:
When i boot up the laptop i get error messages. But it boots anyway. The display resolution is 1366x768.The messages i get are:
error: no suitable video mode found.
error: no video mode activated.
error: no video mode activated.

2nd problem:
I cant get the Trim on SSD to work.I followed the steps in the manual.
When i do sudo leafpad /etc/rc.local the rc.local file is empty, notting in there.Copied and paste the info from the manual and edited it to my disc setup
When i do the last command to disable weekly cron job for Trim, i get the following message
sudo mv -v /etc/cron.weekly/fstrim /fstrim
[sudo] password for theo:
mv: cannot stat '/etc/cron.weekly/fstrim': No such file or directory

After reboot there is no trimlog

I noticed that Conky was included in LL 4.0. I like that, because I love Conky. Unfortunately Conky Manager does not work on Ubuntu 18.04 and neither does it on LL 4.0. So what is the use of including Conky if the Conky Manager does not work? It could have been known at the time of release of LL 4.0.