I rarely have problems with Linux or Windows that I cannot solve myself, so this information is really just a heads up concerning Windows 10, openssh for Windows, and live Ubuntu bootrepair disks for those here who are not terminal people.

I have a full (developer mode) up to date Windows 10 with openssh installed dual booting with Linux Lite 3.2 (legacy) This machine had a beta copy of Linux Lite 3.0 64bit on it originally, as I generally use it for testing Linux alongside Windows 10. I installed Linux Lite 3.2 on it the other day removing the 3.0 beta installation entirely. Linux Lite 3.2 worked perfectly, but Windows 10 left me the dreaded BSOD 0xc000000e code. I repaired Windows via the Windows install disk, not noticing at first that now an entry for ssh_d server appeared on my Windows login screen which was not previously there. After repairing Windows 10 of course Linux Lite would not boot. I tried the live Ubuntu bootrepair disk, and it could not get Linux Lite to boot though Windows 10 still booted. I used a super grub 2 live disk then (Rescatux) and Linux Lite would once again boot, however Windows returned to the BSOD 0xc000000e code. To make a long story short at this point, I had to restore Windows 10 again from the Windows install disk, and afterwards uninstall openssh for Windows, after which the Ubuntu live boot repair disk worked. It seems that Ubuntu bootrepair expects UIDs and of course openssh server which is separately bootable from Windows 10 masks the UIDs with its own headers. The BIOS are set to ATA on this machine as well, and ATA in the advanced settings of Ubuntu boot repair did not work returning unknown device. The whole time, after several frustrating runs the grub menu remained, but only able to boot one OS or the other, never both. I am somewhat adept with Windows and at first used several different methods from Linux Lite to attempt the boot repair and file system checks, Gparted partition activation, ntfsfix, testdisk, etc. all to no avail. I was only able to get both systems booting again by uninstalling openssh from Windows 10 first.

TC

I have installed Kwin on my Lite 3.2 x86_64  thought I'd share.  https://en.wikipedia.org/wiki/KWin


Copy - Paste into the terminal the following. Your password will be asked

 

Hi all,

I have Linux Lite 3.2 64-bit installed in an Intel NUC6i5SYK. Everything worked out of the box great except for one thing: Microsoft Surface Ergonomic Bluetooth Keyboard. Linux lite seems to pair the keyboard correctly as you can see from the output of bluetoothctl info:

[bluetooth]# info F1:8D:75:97:13:1B
Device F1:8D:75:97:13:1B
  Name: Ergonomic Keyboard
  Alias: Ergonomic Keyboard
  Appearance: 0x03c1
  Icon: input-keyboard
  Paired: yes
  Trusted: yes
  Blocked: no
  Connected: yes
  LegacyPairing: no
  UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
  UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
  UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
  UUID: Battery Service          (0000180f-0000-1000-8000-00805f9b34fb)
  UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)

However, when I press any key nothing happens. A few suspicious things:
-The LED light on the keyboard keeps blinking even after the pairing (usually once it is paired it stops)
-The bluetooth wizard (or the bluetoothctl terminal commands) never asked for a PIN

The keyboard works pairing it with my MacOS laptop, so that should not be a problem. Any ideas what could be wrong?

Thanks,
Fernando

Spatry named Linuxlite number two of his five top distros for 2016 for new linux users.

https://www.youtube.com/watch?v=Bztcmykf0Os

Nice one.

Jocklad 

My LL3.2, doesn't detect my s-video output when I connect it to my tv.

It worked fine in 2.8 but in 3.2 it doesn't detect it.

Any fixes or solutions for this?

Hi All,

LL3.2 on an HP Proliant Server.

After a few updates and a reboot I now find myself at a black screen (no mouse pointer). The yellow splash screen comes up for a few seconds but then goes to black. I can crtl/alt/f1 to a prompt and login but no GUI. The server is running as I have still access to Web based apps running on Apache and I can still login to Webmin.

Is there a way to reinstall the GUI and/or login routine?

Thanks.

I've been using full disk encryption with cryptsetup in my LL2.8 (Lenovo) for over a year now.
So far no problem, but I noticed a change in booth process since a recent cryptsetup update. Everytime I log in with a correct pw, this is what I get:

Jerry et al,
I received two phone calls over the holidays from persons interested in downloading and installing LL. Both were running Windows 10 on their home boxes. They had both gone to the LL home page, and with their Edge browsers could not wade through the ads. Selecting "allow all" sent both of their browsers to a blank page loop. Talking them through the problem over the phone was a nightmarish proposition to say the least. I eventually sent them to distrowatch, where they found the download link for sourceforge. Both have successfully installed dual boot systems now. The ads at distrowatch, and sourceforge were no problem. I tested the LLhome situation yesterday myself and indeed was able to produce the blank page loop on the little womans Edge browser as well. It is not a user friendly situation for Windows users to be driven from the LL home page. Check your advertisers for malware update viruses (redirect trojans) and heuristic trojans with Kaspersky, not Clam. This will find Windows malware if it is there without false positive problems. Blank page loops are almost always redirect malware.

I had no problem with the LLhome from Debian 8.5.

TC

Hello,
I usually save my user and password info for several sites and as of the last update, Firefox is not remembering either.
I've tried uninstalling and reinstalling with no luck. What can I do to fix this?

This will cover many applications, but not all.

1. Open your home folder.

2. Press Ctrl + H (to show hidden files)\

3. Open the .gtkrc-2.0 file, add the following to a new line starting at the bottom of the file: