[12:23] <BluesKaj> Hiyas all
[13:08] <BluesKaj> could be a windows read/write permissions issue
[13:08] <diogenes_> Velizar Peshev, windows 10
[13:12] <hateball> Velizar, turn off fast startup or what the feature is called in Windows
[13:12] <hateball> It only hibernates the disk, doesnt properly unmount it, which is why it is read-only in Linux
[13:13] <Javabean> another trick is to select reboot in windows, and interupt it at the bios/uefi post.
[13:14] <BluesKaj> interesting hateball, oddly enough I used to have a similar issue with W7
[13:15] <hateball> BluesKaj: windows can mark the ntfs partition dirty for various reasons if it doesnt shut down cleanly, which would give the same problem
[13:15] <hateball> but since windows 8 this fast startup has been a feature that guarentees that it is a problem :p
[13:15] <BluesKaj> ok
[13:16] <hateball> same thing can happen on linux really, which typically triggers an fsck on the next boot
[13:17] <BluesKaj> I wasn't the primaryuser on W7, it was my wife's pc
[15:35] <thxffo> does agios still hangout here?
[15:38] <sekisushai> hello
[15:39] <sekisushai> i've recently installed kubuntu 18.04 LTS on a Dell XPS 13
[15:39] <sekisushai> the resolution of the screen is 3840x2160
[15:39] <sekisushai> and the DPI is only 96x96
[15:39] <sekisushai> is there a way to permanently scale up the DPI ?
 @sekisushai, Dpi can be found in system settings under font. I recommend 144 our 168 but set as needed. Restart plasma or logout/login to ensure new dpi it's applied everywhere.
[20:02] <jubo2> Hi. A frind is having a Kubuntu 18.04.1 that is broken in such a way that at the end of the boot there is just a blinking text-mode cursor in the upper-left corner and the mouse cursor is there and moves with the mouse movements
[20:03] <jubo2> I don't know what has gone wrong with it. He says he didn't touch any system settings nor did he upgrade anything before the system broke
[20:04] <jubo2> I told him to go to GRUB and we tried running dpkg, which installed one package with no info about what package was installed
[20:05] <jubo2> (from the recovery mode of course)
[20:05] <jubo2> Any ideas?
[20:06] <jalcine> sounds like sddm isn't starting but X has
[20:06] <jalcine> try installing another login manager? (like `gdm`)
[20:06] <jalcine> or `lxdm` (more friendly and lighter)
[20:07] <jubo2> jalcine: how do I install another login manager (from the recovery mode menu) ?
[20:16] <jubo2> jalcine: he doesn't have ethernet and the WiFi is not up in the root shell so 'apt intall lxdm' fails
[20:16] <jalcine> oh damn
[20:16] <jalcine> you should be able to enable networking from the recovery menu
[20:17] <jubo2> I'm looking at askubuntu.com and it says to 'ifconfig wlan0 up' in the root shell. Will this work?
[20:17] <jalcine> wlan0 might not be the name of the card
[20:18] <jalcine> a change was made to make it similar to `wlp1s0`
[20:18] <jalcine> run `ifconfig` first to see what's available
[20:19] <jubo2> jalcine: command 'ifconfig' is not installed on his system
[20:23] <jubo2> jalcine: he was able to run 'service network-manager start' which turned the WiFi light on but still unable to download any software
[20:28] <jalcine> have you run `nmcli` to confirm it's connected to a network?
[20:29] <jalcine> that should open an CLI interface that'd let you connect/see networks (wireless, wired, etc)
[20:41] <jubo2> jalcine: NetworkManager is not running and we are unable to start it with 'systemctl start NetworkManager.service'
[20:41] <jubo2> because 'systemctl' does not seem to be installed on the system (!)
[20:42] <diogenes_> jubo2, it's: systemctl restart NetworkManages
[20:42] <diogenes_> NetworkManager*
[20:43] <jubo2> diogenes_: the emergency root shell claims that 'systemctl' is not installed
[20:43] <diogenes_> try with sudo
[20:43] <jubo2> the shell is a root shell
[20:43] <jubo2> I can see the '#' sign in there
[20:44] <jubo2> so I don't see what difference 'sudo' would have
[20:45] <jubo2> is there a way to reconfigure / fix the sddm from the root shell?
[20:45] <jubo2> coz we don't seem to be able to bring networking up
[20:49] <jubo2> ok. now he says he has networking via connecting his phone to the USB port
[21:20] <jubo2> jalcine: ok. we managed to turn on the networking (in the recovery menu (dohh)) and installed LXDM and it started ok. Now the desktop environment is wholly different
[21:20] <jubo2> I was of the understanding that the SDDM was only for the login screen
[21:21] <jubo2> I now that we have access to a working system we can proceed to try to fix the SDDM somehow (maybe later)
[21:29] <jubo2> Thanks for your help jalcine and diogenes_
[21:29] <jubo2> I need to catch some shut-eye now and look into fixing the SDDM tomorrow
[21:29] <diogenes_> jubo2, yw
[21:29] <jubo2> The first thing that comes to mind is to purge it and re-install it
[21:29] <diogenes_> jubo2, also it's configs
[21:30] <jubo2> diogenes_: doesn't purge remove the configs as well
[21:30] <diogenes_> i forgot where it's configs lie, in /etc/ or /var
[21:30] <diogenes_> or someplace else
[21:30] <jubo2> diogenes_: in /etc
[21:30] <diogenes_> ok
[21:30]  * diogenes_ is offline
[21:30] <jubo2> gn