[size=1em]Using Linux Lite 3.2 with a Canon MG5650 all single sided pages print perfectly as expected every time.[/size]

[size=1em]Duplex pages also printed perfectly as expected every time UNTIL VERY RECENTLY however, now whenever I try to print using duplex printing , the first page always starts printing 28mm higher up the page, therebye cutting off part of the document, regardles of what type of file is being printed. No settings have been changed in the printer configuration files although I have tried deleting and reinstalling the printer without any success.[/size]

[size=1em]As I said, both options worked perfectly up until very recently so I can only assume that one of the recent updates may have caused this issue but I am at a loss as to how to solve it and would very much appreciate any help that you guys might be able to offer [/size]

Please help me, I'm a newbie.  Upon trying to install the software. I'm able to select the language, presented two options to select updating and installing third party, but the third process  I receive an Install crashed message that follows  (no drive appears either):

We're sorry; the installer crashed. After you close this window, we'll allow you to file a bug report using the integrated bug reporting tool. This will gather information about your system and your installation process. The details will be sent to our bug tracker and a developer will attend to the problem as soon as possible.
Traceback (most recent call last):
  File "/usr/lib/ubiquity/plugins/ubi-partman.py", line 1297, in on_partition_list_edit_activate
    self.partman_dialog(devpart, partition, create=False)
  File "/usr/lib/ubiquity/ubiquity/plugin.py", line 48, in wrapper
    return target(self, *args, **kwargs)
  File "/usr/lib/ubiquity/plugins/ubi-partman.py", line 978, in partman_dialog
    if ('can_resize' not in partition or not partition['can_resize'] or
TypeError: argument of type 'NoneType' is not iterable

As usual update your Firefox browser. Personally, I do not use it. Prefer Opera and Chrome.

https://security.gentoo.org/glsa/201701-15

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: