[00:04] <Spass> tomreyn, do you have "xscreensaver" package installed? if yes try to remove it, but that's just a blind guess
[00:05] <brainwash> probably the case
[00:05] <brainwash> or gnome-screensaver if that thing is still available
[00:11] <brainwash> tomreyn: or https://github.com/the-cavalry/light-locker/issues/87
[00:37] <tomreyn> right, gnome-screensaver is running
[00:39] <tomreyn> it's not ticked on the session and startup list, though
[08:27] <brainwash> tomreyn: did you figure out why gnome-screensaver is started?
[09:41] <jarnos> Why is the caret needed? https://xubuntu.org/news/introducing-xubuntu-core/
[09:42] <jarnos> I think it chould not match anything as it is the last character.
[09:54] <Spass> correct me if I'm wrong, but I think this article was written before "xubuntu-core" package was included in the repos, so that command uses tasksel task
[09:54] <Spass> and I guess the caret isn't needed anymore
[09:56] <Spass> jarnos, https://shantanugoel.com/2010/10/23/apt-get-caret/
[10:46] <brainwash> Spass: it is needed
[10:46] <brainwash> Spass: see bug 1754872
[10:47] <brainwash> mostly read my last comments in that report
[10:49] <brainwash> (the issue applies to xubuntu-core also)
[13:06] <tomreyn> brainwash: i think it was still started from when i had been running gdm. i've since rebooted and it's not running now.
[13:08] <brainwash> tomreyn: so, everything working properly now?
[13:17] <tomreyn> not really. if the screen goes off now, when i reactivate it i ghet a black screen with a frozen mouse pointer.
[13:18] <tomreyn> and there's no way to recover from it other than a reboot. systemctl stop lightdm gets stuck, doesn't return to the shell. and recovering the running session is impossible.
[13:23] <tomreyn> and after reboot i get to see this http://i.imgur.com/divQyJX.png
[13:28] <brainwash> oh boy
[13:29] <brainwash> that is light-locker-settings though
[13:29] <brainwash> the configuration app for light-locker
[13:29] <tomreyn> yes, i had opened it to see whether my settings are still correct
[13:30] <tomreyn> sadly, this 'experience' drives me right back to ubuntu proper. at lest for now,
[13:30] <tomreyn> i'dl ike to help debugging more but i really need a stable desktop
[13:30] <brainwash> I think l-l-s is not even needed in 18.04. the settings can be accessed via the power manager settings.
[13:31] <tomreyn> the unrecoverable black screen is more of a concern, though ;)
[13:31] <brainwash> yep
[16:00] <hk238> hi I have xubuntu on another system the /boot drive gets filled up with initrd files and runs out of space so you cant update
[16:01] <hk238> anyway to fix this?
[16:19] <diogenes_> hk238, 16.04?
[16:38] <hk238> I dont know which version this is
[16:56] <diogenes_> hk238, terminal > lsb_release -a
[16:56] <hk238> 16.04
[16:57] <diogenes_> 1st what you did wrong is that you made a separate /boot partition 2nd try in terminal: sudo apt autoremove
[17:09] <hk238> yeah
[17:09] <hk238> it's pretty  common to make a separate boot partition and xubuntu didn't make any effort saying it wasn't a good idea
[17:10] <diogenes_> it's not xubuntu's thing, it's the common mistake that all the new users come across at some point
[17:10] <diogenes_> i was not an exception
[17:12] <hk238> so far only with xubuntu I've had this problem :D
[17:12] <hk238> but yeah at least it's a lesson learned, maybe I'll make a bigger boot partition next time, or won't make a separate one
[17:13] <hk238> but currently the fix seems to be reinstalling linux :o
[17:13] <diogenes_> yeah, don't make a separate /boot
[17:30] <hk238> or can also make a larger boot
[19:00] <knome> if xubuntu notified users every time they do something that might not be a good idea, it would be full of disclaimer popups...
[19:01] <knome> i guess the installer could mention this, but that would be generic *buntu*, not something the xubuntu developers would engineer
[23:01] <Stek_Turku> hi all
[23:04] <Stek_Turku> on my 64 bit notebook i have installed a 32 bit 16.04 lts (root partition and home partition are different). Can i install xubuntu 18.04 lts 64 bit over the previous 32 bit? can i use the same home partition? what does it happen on my dara and my 32 bit progscalready installed?
[23:31] <Spass> hello Stek_Turku, first of all - backup all your important data before doing anything. I think you'll be completely fine installing 64-bit 18.04 on that "/" partition (and formatting it) and choosing your existing /home partition to be used
[23:33] <Stek_Turku> @Spass: Thanks
[23:33] <Spass> I don't think that there's any architecture related stuff on /home, but maybe someone more knowledgable here will confirm