[01:09] Does anyone else have the problem where after resuming a suspended session it brings you to the login screen instead of the unlock screen? And then logging in again just seems to hang the system? It happens to me randomly, like maybe 1 in 15 suspends. It is also something specific to 18.04 because I didn't have this problem at all in 17.10. [04:29] exit === himcesjf_ is now known as him-cesjf === Katnip is now known as Guest72708 === Katnip is now known as Guest96858 === Guest96858 is now known as Katnip === Katnip is now known as Guest15049 === Guest15049 is now known as Katnip [08:38] hi there i went to system settings > appearance > application style > gnome application style(gtk) and changed the gtk2 and gtk3 themes to breeze dark and everthing became dark including libreoffice, chrome, gedit, mouseedit etc. but when i reverted back to Breeze all applications turned as eariler but libreoffice still remains dark [08:38] can somebody help fix this ? === pataijozsef is now known as pataijozsef_ === Taggnostr is now known as Taggnostr2 [10:50] Hi folks [12:10] Hello. My system is booting the lowlatency kernel by default.. on startup no grub menu is shown. How do I access the grub menu? [12:10] This is relevant because my 20GB /-partition is shot full almost to the brim and I'd like to get rid of the lowlatency kernel to save space [12:11] I did do a 'sudo apt remove linux-lowlatency' but that saved merely 20kb [12:11] because it did not delete the lowlatency image .. probably because it is in use [12:13] I'd like to upgrade to 18.04.01 when that becomes possible but with only 600MB empty space in the /-partition I'm afraid the /-partition will fill up during the distribution upgrade and break the system [12:18] jubo2: The package you removed is a meta-package. Run `sudo apt autoremove` to remove the orphaned packages. [12:19] lordievader: I did run 'sudo apt autoremove' [12:19] Looking at 'last' the lowlatency kernel is in use atm [12:19] jubo2: What is the output of 'dpkg -l|grep linux-image'? [12:20] lordievader: a long list ... I see even 4.10 kernels there. How do I remove 'em? [12:21] 4.13 is the latest version it shows [12:21] I'm on Kubuntu 17.10 [12:21] jubo2: `sudo apt purge ` [12:23] lordievader: is that safe? I'm afraid I'll break something if I start purging stuff [12:24] jubo2: What I usually do is remove all kernels except for the current running one and the latest one. [12:26] I removed the 4.10 one but zero bytes were freed [12:29] jubo2: `dpkg-query -W --showformat='${Installed-Size}\t${Package}\n' | sort -nr | less` is always a nice oneliner to see what packages consume the most. [12:29] jubo2, run: dpkg -l '*linux*' | nc termbin.com 9999 [12:29] share the link [12:38] diogenes_: http://termbin.com/k6vc [12:38] I just want a clean and safe way to get rid of the old kernel images and get space on the /-partition [12:39] removing the 4.10 kernel with 'sudo apt purge' freed 0 bytes of space [12:39] also the output of: ls /boot | nc termbin.com 9999 [12:39] and: uname -r | nc termbin.com 9999 [12:41] diogenes_: http://termbin.com/27px contains only one line: '4.13.0-46-lowlatency' [12:42] jubo2, try: sudo dpkg --purge --force-all linux-image-4.10.0-21-generic [12:42] of course do always have a bootable usb with kubuntu :) [12:43] yeah. I got many bootable USBs [12:43] see if after that you get some free space [12:44] ok. I try it [12:45] also: sudo dpkg --purge --force-all linux-image-4.10.0-21-generic [12:45] oh i already gave it :) [12:46] I didn't do a 'df' before the command so I don't see much change [12:47] the command didn't output anything about saving space [12:47] I try to remove another kernel and doing a 'df' before and after [12:48] now: sudo dpkg --purge --force-all inux-headers-4.10.0-21-lowlatency [12:48] and so one, using that list [12:49] diogenes_: it says "dpkg: warning: ignoring request to remove linux-headers-4.10.0-21-lowlatency which isn't installed" [12:49] go down the list [12:49] pick next one [12:49] ok [12:50] be careful not to purge this one: 4.13.0-46-lowlatency [12:51] that did free a little bit of disk space [12:51] good, now next one, there is a huge list [12:51] so I purge them one-by-one? [12:51] yes [12:51] oh ok.. thanks for help diogenes_ [12:52] np [13:23] Uhh.. diogenes_ .. after purging another kernel there is actually _less_ space on the /-partition [13:23] this is really really annoying [13:32] yeah.. each time I purge a kernel image the /-partition just fills up. This is agravating behaviour [13:33] Couldn't we just have a Linux that does something by itself to keep the /-partition from filling up [13:35] jubo2, try to remove the headers too [13:39] and now after removing some of them, try: sudo apt sutoremove [13:41] s/sutoremove/autoremove [13:42] running 'df' repeatedly shows remaining disk space disappearing by the second [13:42] something very wrong with this system [13:43] could be activity in the /tmp though [13:45] diogenes_: there are headers only for the 4.13 kernels [13:45] Whoever said 15GB is enough for /-partition? I have 20GB and am struggling to keep some space free there [13:45] jubo2, yes look in /tmp [13:47] nope. tmp is using only 368kb [13:48] 'sudo apt autoremove' just comments that it isn't doing anything [13:50] I'm losing free space at an alarming rate [13:50] I'm starting to think the OS is compromised by some attack [13:51] jubo2, don't worry :) try: sudo apt autoclean [13:52] diogenes_: I tried 'sudo apt autoclean' to no avail [13:52] ncdu / [13:53] and see where your space has gone [13:54] jubo2, ok meybe this script can help: http://dpaste.com/3XQHPJ6 [13:56] diogenes_: maybe but I'm kind of weary of running scripts I don't understand [13:56] /usr is taking up 6.6GB [14:14] going offline for a moment to make backups (including the irc logs, that's why the logoff) === pan is now known as Guest25691 [16:32] anyone here that is using the latest verion of virtualbox [17:55] help, my computer is doing strange things [17:59] all my panels would freeze in such way that they'd wodk but not update their appearance (clock would display static time, charts would stop etc.) but it'd be responsive to clicking if you did it blindly [18:01] today, I woke up my computer from suspend to ram and the widgets were unfrozen. I got lots of popups about some directories not being qriteable, so I rebooted... well, it became unresponsive so I had to ctr+alt+F2, login and then type reboot, it worked [18:03] but after rebooting and typing in the luks password, there's no gui logon screen, just a busybox built-in shell (ash) [18:04] and (initramfs) [18:05] *writeable [18:32] okay, I typed exit and it told me to run fsck manually [18:35] okay, fsck helped [18:35] all I had to do was run fsck in the directory it printed [18:36] and then yes to all [18:39] I'd like to suggest that it would have been a lot more user friendly if it would do that automatically or suggest doing it automatically, in a simillar fashion to checkdisk. While this modifies the filesystem and could theoretically damage it, to an average user such a computer that requires fiddling with ash shell is of no use anyway [18:39] hey guys! how do I tell the file indexing to not only index my system drive (SSD) but also my additional data drive (HDD)? The HDD is set to automount on login. The system is Kubuntu 18.04 === amine is now known as Guest44629 [21:08] Guest25691: your question intrigued me so I tried [21:08] since my computer is also set up like that [21:09] what I did was type baloo in krunner (alt+space) and then remove DATA from the list not to be scanned [21:10] select it, click the minus button, then "apply" [23:16] valorie: thanks for your answer! unfortunately I already did that. still no search results from the HDD. [23:16] hmmm [23:16] perhaps ask in #kde ? [23:17] in euro-working hours, preferably