[00:41] <Ophidd> hi guys o/  I'm hoping to find some guidance on the recovery of my (encrypted) home folder. Today my lubuntu(16LTS) would not boot, it displayed "ata1 SRST failed (errno=-16)". Some googling revealed this error shows up when something is wrong with the disk itself (sig!)(a Samsung SSD 128g). But the disk is detected in the BIOS, and GRUB loads correctly (selecting normal or recovery mode does not help, but GRUB is stored on the disk it
[00:42] <Ophidd> So I took the SSD out and booted on Lubuntu LiveUSB, and then plugged the SSD via USB (with converter ATA/USB). Now I can see with `lsblk` my partitions, with LVM and the lubuntu--vg-root thing. Conveniently the File Manager managed to mount it (I did not succeed with the cli) but all folders (bin,etc,lib...) are empty and the home folder does not even open. Everything seems vanished but `df -h` suggests the data is still (physically) 
[00:43] <Ophidd> Most importantly, "sudo pvscan" throws a lot of "read failed after 0 of 4096 at ..... Input/ouput error"
[01:40] <ShellcatZero> what is the proper place to set the TERM variable? It is currently set to xterm-256color in my .zshrc file, but this overrides GNU screen and tmux causing problems, since they both need TERM=screen to work properly.
[11:51] <Mijudwsauidhsakd> Hello
[12:09] <bumblebee> hi
[13:37] <miro345> I am looking for something
 Me too :|
[15:01] <bumblebee> hi. can you please help me installing a printer (canon pixma mg2950) on lubuntu 16.04?
[16:30] <ebebeb> is lxqt going to be default in 18.04?
[16:52] <qswz> man, I wish I could put a dark theme on leafpad
[16:53] <tsimonq2> ebebeb: No.
 @tsimonq2, :(
[16:56] <ebebeb> @tsiqmonq2 thanks
[18:52] <qswz> guys, when I use shortcuts defined on ~/.config/openbox/lubuntu-rc.xml
[18:52] <qswz> through which user are they ran?
[18:53] <qswz> because I need to allow one in sudoers.d, and putting my current user doesn't work
[18:54] <wxl> should be current user
[18:54] <qswz> hmm
[18:54] <wxl> you could edit the system wide and then any user will pick up on them, but it will still be the current user's openbox process
[19:06] <qswz> brb
[19:10] <qswz> ok it works fine
[19:10] <qswz> https://gist.github.com/caub/9281645c30e12b92c040795fcc17c205#gistcomment-2377969
[19:10] <qswz> ^ description
[19:10] <qswz> I was missing a "sudo"
[19:58] <pmatulis_> maybe we should consider moving away from openbox. it's a dead project
 @pmatulis_, Maybe once we move away from LXDE, which is also dead.
 Mir seems like an interesting project.
[20:11] <pmatulis_> lubot, i didn't realize LXDE is also defunct. geez
[21:01] <parhelia> eh? it's dead?
[21:02] <Unit193> https://git.lxde.org/gitweb/?p=lxde/lxpanel.git;a=summary - https://git.lxde.org/gitweb/?o=age
[21:04] <parhelia> I'm assuming because lxqt.
[21:06] <tsimonq2> Well, not "dead" dead, but development has severely slowed down.
[21:08] <parhelia> right.
[21:08] <wxl> i think it's safe to say that lxde has long been in a maintenence mode, whereas lxqt is in vigorous, active development
[21:08] <wxl> i mean this is really not new news
[21:28] <tsimonq2> foka: Hey!
[21:28] <foka> tsimonq2: Hey!
[21:28] <tsimonq2> So you said LO Writer works on amd64 but not i386?
[21:31] <foka> tsimonq2: Yes, apparently, though I was testing a SSD that was installed (plugged into SATA) on a HP desktop, and then tested it via USB-to-SATA adapter on my laptop.  Not sure if it had anything to do with it.  LO Calc, LO Impress, etc. all worked IIRC, but LO Writer would just crash.  Unfortunately, I was in a hurry, and didn't try too hard to collect any logs, and just decided to re-install amd64 because we had wanted Google Chrome on it and
[21:31] <foka> i386 is no longer supported.
[21:32] <foka> But yes, I will see if I could reproduce it in QEMU or maybe on a USB thumb drive and get more information first.
[21:35] <tsimonq2> OK, cool.
[21:35] <tsimonq2> Thanks!
[21:38] <foka> Another problem I ran into is with Ubiquity or d-i or just parted warning that the root partition starting at sector 2048 (i.e. at 1MiB) is not aligned, and insisted on starting the partition at sector 65535.  After some investigation, I think the most likely culprit is the USB-to-SATA adapter which reports a 33553920 value (= 65535×512) at /sys/block/sda/queue/optimal_io_size, and parted (thus d-i and Ubiquity?) trusting it completely?  I don't
[21:38] <foka>  think it is specifically related to Lubuntu though, but just wanted to share this information with you anyway, haha!
[21:39] <foka> (will report it soon after gathering more information, maybe to parted and/or d-i and/or Ubiquity and/or some place else.)
[21:44] <tsimonq2> OK.