Greetings,

I've already made a couple of posts in the Installing Software section but I thought perhaps a little info about my LL interests might be useful.

Some 8 years ago got myself a very nice 17" Toshiba Satellite to replace an earlier laptop which ran on Windows XP. The Tosh came with Vista ...which was awful from day 1. Slow, buggy, needlessly complicated and unreliable. I couldn't believe how my supposed upgrade turned out to be so much worse than the old one. Anyway, I was moaning about Vista (I had a lot to moan about) and somebody suggested I try Linux which would speed things up. I had a look at various distros and eventually selected Ubuntu 12.04 as being suited to my limited skillset and knowledge.

From that point, I can honestly say that I haven't looked back. Discovering the speed, stability and ease of use of Ubuntu made me realise that whole MS Windows catastrophe was something I no longer needed to be a part of. I've used almost every version of  Windows (in a business setting) starting with 3.11 in '94 through to W10 and imho 3.11 was probably the last truly decent one - being essentially a GUI for MS Dos. When it comes to Linux, I have had similar feelings about Ubuntu in that, over the years, it's gone from being lean and mean to getting increasingly porky and cumbersome ....and that's why LL seemed a good choice. Also, I have a chum who's been lecturing me about LL for the last couple of years and I really needed to him to just shut up :

Coming up to date: my lovely but venerable Tosh is still around but 3 years ago I got hold of a Lenovo Thinkpad T520. It's a bit on the heavy side but solidly built and very easy to access for basic hardware issues. Originally it had a single mechanical hard drive and 4gb of ram. Because, unfortunately, I still needed Windows for some programmes, it seemed reasonable to set up my drive as dual-boot. Over time, I'd gone from U12.04 to 16.04 and W7 through W8 to W10 and as I was doing this I was actually making it increasingly complex to set things up in a way that suited me and more importantly easily maintain them, so....

....I realised that if I wanted to make life simple, I needed to put my potential problems into completely different boxes which led me to look how I could physically separate OSs and Storage on the same laptop. Luckily for me, the T520 has both an mSATA port and a DVD drive and so my new set-up is as follows:

Main OS = LL 5.0 on a 30gb mSSD on the internal mSATA - most of it's root with just a few gb for home and no swap.
Secondary OS = W7 pro* on a 120gb SSD replacing the old clunker
Saved Storage  = 256gb SSD - caddy mounted in the DVD bay

I'm using MEGA for cloud storage and my day to day work stuff is synced to my PCs through that. I'm using about 30gb out of the 50gb capacity but there's apparently no limit to the number of accounts so I'm fairly ha ppy. I've cloned both OS drives to back-up SSDs and use another SSD for storage back-up for my non-cloud stuff. You can see that if and when I do have a problem, it's just a question of swapping a drive out - which takes a couple of minutes.

I had thought of buying a new machine but it seemed to me that most of the new stuff is much flimsier with some fairly crappy keyboards...and a fair few don't have easily removable batteries - atm I have two. I've increased ram from 4gb to 16gb (the extra really helps for some number crunching real time graphical representation stuff) and so from a hardware standpoint, I'm a happy bunny.

My transition to LL is going OK but apart from my expected idiot mistakes there are some unexpected hiccups which have made things less smooth than my transition from Windows to Ubuntu - and that did surprise me.

....and that's the story so far. I haven't had any real disasters but I've got into the "login loop of death" 4 times already and whilst I have tried a number of the work arounds, none have worked for me and I've ended up reinstalling LL....so I'm getting quite good at that now


*I went back to W7 Pro having dismissed W8 as garbage and struggling with W10 for far too long.

I have update error:

===========================Install Updates Error log===========================Install Updates could not successfully download and install available updates.Go to https://www.linuxliteos.com/forums/ and paste the log below into a new or existing thread for assistance.============ Log ===========E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2326 (apt-get)E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

So I'm over here working on making my work rig more open source. But I  ran into a snag . I can not figure why everyone telling me to go resolve when LL got openshot  in the alL software center? Is 0penshot more like vegas?? 

Sent from my moto z4 using Tapatalk

The "Ubiquity" installer used by the Ubuntu desktop is set to feature Active Directory (AD) integration with the upcoming Ubuntu 20.10 release.

Given it's late in the cycle and past the feature freeze, a feature freeze exception was sought and granted for adding this optional Active Directory support to the Ubuntu desktop installer.

During the user setup process in Ubiquity is going to be support in Ubuntu 20.10 with support for enabling Active Directory for log-ins. When checked, the user can login to an Active Directory configuration on their network while still creating a local Ubuntu account for administration purposes. The Ubiquity installer user interface allows specifying the domain, administrator, and password as well as a test for the domain.

The change with the Active Directory support is approved and heading into Ubuntu 20.10.

Ubuntu 20.10 is due for release next month with OpenZFS improvements, Linux 5.8 kernel usage, GNOME 3.38 desktop, and many other package updates.

Source - https://www.phoronix.com/scan.php?page=n...-Directory

I'm using an all-in-one printer scanner (MFC-9120CN) where the printer works but the scanner is not found by any scanning program. Even after installing the proper drivers from the Brother website. I had the problem with LL4 and LL5.

The problem is that the needed files are stored in /usr/lib64/sane and should be (also?) found in /usr/lib/sane. The solution is to create the directory and put a link for each file in /usr/lib64/sane in the new directory, like so (tested in LL5):

i am usin linux lite 4.8 but it takes too long to boot even after removing virtualbox. it takes around 3 mins

...and here we are again:

Have been happily using Amule for a few years on both W7 and Ubuntu 16.04LTS and am now trying to install it on LL5.0..... with almost the same issues as I had with Megasync, the difference that I can't seem to find a version that is compatible with Ubuntu 20.04. I've got as far as trying the one I found (amule_2.3.2-2_amd64.deb) which was described as being compatible with 18.04 and onward....but, nada.

Does any kind soul know of where I could get the right one for LL5.0?....or perhaps could advise me what I can do with another version to make it work?

hi every body i really need some help with this bug because it won't let install anything no matter what it won to install it just said the same. now I made it better, I just remove every driver  about androit and it made it  but leave this answer:

code=exited,
status=255/EXCEPTION)



muy buenas necesito ayuda por favor, resulta que tengo linux lite pero quiero flashear telefonos
:-\ como no soy diestro y ni siquiera programador (aunque entiendo varios terminos) se lo complicado que es el asunto de los drivers en android de hecho tengo un blu advance que está de darle por la jupa nada mas  8)
porque tengo la rom stock de dicho dispositivo, el punto es que soy novato en linux ubuntu aunque he visto lo mucho que ha progresado desde hace mucho sigue siendo tedioso y fustrante el intentar usar el sistema operativo para trabajar con telefonos
sin embargo me encontre la dream cast de linux  ;D me refiero a FWUL al ver que trae todo la puse en la pendrive  y listo booteo desde ahí pero todo se pierde y nunca me leyó el telefono el sp flash ni el simple adb pero fwul si lee el telefono.
al ver esto trate de installar todo en linux lite para no estar en esa vara de volver a instalar todo cada vez que quiera usar fwul.
lo hice empece una ardua instalacionde actualizaciones y cuando ya estaba cerca de acercarme. ta dán
> se descalabró tere en las gradas. (que rica tere) :
E: No se pudo obtener un bloqueo /var/cache/apt/archives/lock. Lo mantiene el proceso 5019 (synaptic)
N: Tenga en cuenta que eliminar el archivo de bloqueo no es una solución y puede dañar su sistema.
E: No se pudo bloquear el directorio /var/cache/apt/archives/
no sé pero todo lo que quiero instalar ahora no me deja porque el bendito android-23 ya existe y traté con una sugerencia que parecia arreglarlo pero solo me desinstaló repositorios obsoletos entre otras cosas obsoletas lo cual está bien pero me tiró esto para rematar:
Configurando android-androresolvd (1.3-1build1) ...
Job for android-androresolvd.service failed because the control process exited with error code.
See "systemctl status android-androresolvd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript android-androresolvd, action "start" failed.
● android-androresolvd.service - LSB: Updates /etc/resolv.conf from Android system props
    Loaded: loaded (/etc/init.d/android-androresolvd; generated)
    Active: failed (Result: exit-code) since Thu 2020-09-17 21:28:50 CST; 13ms ago
      Docs: manystemd-sysv-generator(8)
    Process: 10666 ExecStart=/etc/init.d/android-androresolvd start (code=exited, status=255/EXCEPTION)

sep 17 21:28:49 linuxlite-MS-7529 systemd[1]: Starting LSB: Updates /etc/resolv.conf from Android system props...
sep 17 21:28:50 linuxlite-MS-7529 android-androresolvd[10670]: Cannot access system properties via ANDROID_PROPERTY_WORKSPACE
environment setting.
sep 17 21:28:50 linuxlite-MS-7529 systemd[1]: android-androresolvd.service: Control process exited, code=exited, status=255/EX
CEPTION
sep 17 21:28:50 linuxlite-MS-7529 systemd[1]: android-androresolvd.service: Failed with result 'exit-code'.
sep 17 21:28:50 linuxlite-MS-7529 systemd[1]: Failed to start LSB: Updates /etc/resolv.conf from Android system props.
dpkg: error al procesar el paquete android-androresolvd (--configure):
el subproceso instalado paquete android-androresolvd script post-installation devolvió el código de salida de error 1
Configurando google-android-platform-23-installer (23+r03+nmu3) ...
make: se entra en el directorio '/var/cache/google-android-platform-23-installer'
cd /var/cache/google-android-platform-23-installer && unzip -ou platform-23_r03.zip
Archive:  platform-23_r03.zip
install -d -m0755 /usr/share/doc/google-android-platform-23
find /usr/share/doc/google-android-platform-23 | sort >> /var/lib/dpkg/info/google-android-platform-23-installer.list
chmod -R a+rX /var/cache/google-android-platform-23-installer/android-6.0/
chmod -R go-w /var/cache/google-android-platform-23-installer/android-6.0/
install -d -m0755 /usr/lib/android-sdk/platforms/
/usr/lib/android-sdk/platforms/android-23 already exists.
make: *** [Makefile:18: install] Error 1
make: se sale del directorio '/var/cache/google-android-platform-23-installer'
dpkg: error al procesar el paquete google-android-platform-23-installer (--configure):
el subproceso instalado paquete google-android-platform-23-installer script post-installation devolvió el código de salida de
error 2
y despues esto:

/usr/lib/android-sdk/platforms/android-23 already exists.
make: *** [Makefile:18: install] Error 1
make: se sale del directorio '/var/cache/google-android-platform-23-installer'
dpkg: error al procesar el paquete google-android-platform-23-installer (--configure):
el subproceso instalado paquete google-android-platform-23-installer script post-installation devolvió el código de salida de error 2
Se encontraron errores al procesar:
android-androresolvd
google-android-platform-23-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)

alguien sabe que está pasando porque yo no tengo la mas minima idea

Hello,

When I boot my laptop up without the charger plug in I get nothing but a black screen. But when I boot my laptop up with charger connected it boots fine.

Without the charger I can see the boot splash screen but guessing when it passes the boot splash screen it doesn’t take me to LightDM it just gives me a black screen.

Other distros it takes me to the login screen with or without the charger plugged in.

Here’s the computer specs:
CPU: AMD Ryzen 5 3500U
GPU: AMD Vega
Ram: 16GB

Thank you

LL5 is excellent. I am having issues getting my head around EUFI but that is another matter. The following problem was, I am pretty sure, also present in LL4.

After having a problem with a machine "seizing up" if left on for several days I investigated and think there is a problem with the Lite Widget (or conky, which it uses) grabbing more and more memory over time. I have confirmed this using LL5.0 on several machines, with both Intel and AMD processors and from 2GB to 12GB RAM. Some were totally new installs. My tests use the following script: