[00:14] <d1n0saur> hello all
[01:27] <Quantos> Hi, I'm running KUbuntu 18.04 and I would like to know how to reduce the length of time that it takes to log off or shutdown
[01:27] <Quantos> I have it set to start with a new session each time
[02:19] <DarwinElf> in Slackware, Konsole does great, letting me use a default profile.  In Kubuntu, Konsole doesn't, ignoring that I've set a default profile... it loads a non-profile Konsole session each time.  How do I get it to enforce using my setting of a default profile?
[03:08] <Perdellian> valorie: nah, I gave it a break last night
[03:08] <Perdellian> I think my /boot might've been larger before, come to think of it
[03:14] <valorie> so there is bootchart
[03:14] <valorie> which I don't know how to use, but that's what the developers use to make things quicker
[03:15] <valorie> DarwinElf: sounds like a bug!
[03:15] <valorie> the easy way to file one is `ubuntu-bug konsole` in the commandline
[03:15] <Perdellian> so, sanity check... after doing 'cryptsetup luksOpen /dev/sda5 computername-crypt', I should be able to see all my LVM stuff in that, right?
[03:15] <valorie> Perdellian: sorry, haven't a clue about that
[03:15] <Perdellian> {p,l,v}scan and {p,l,v}display do nothing
[03:15] <Perdellian> show nothing, that is
[03:16] <Perdellian> (and yes, running with sudo
[03:16] <Perdellian> )
[03:17] <valorie> hopefully someone who knows hops in
[03:22] <DarwinElf> ok
[03:32]  * Perdellian wonders if they should just find another live image and try from there
[04:05] <Quantos> Okay, I just upgraded Plasma and the slow shutdown is fixed
[04:05] <Quantos> So ignore my previous
[05:16] <valorie> good to hear!
[11:05] <MarcWeber> I tried apt-get update & upgrade but the update gui still says there are apps to be updated and firefox is still old.
[11:06] <MarcWeber> The system wasn't updated for 2 years, I had to copy paste sources.list from recent installation.
[11:06] <MarcWeber> So what is making the difference ?
[11:22] <MarcWeber> I was missing dist-upgrade ..
[12:20] <hateball> MarcWeber: yea you will need dist-upgrade (or apt full-upgrade) for version upgrades
[12:23] <BluesKaj> Howdy all
[12:25] <lordievader> Good afternoon
[12:27] <chrisrc1111> hello. i have a strange problem with sharing folders via samba. i can access some folders (security = user), but not others. in the latter case the log says "_servicenumber: couldn't find chris ...
[12:58] <jubo2> Hi valorie. My friend just phoned me up and said his Kubuntu just started working again. The he used to have was that the login screen did not show up: only a blinking text cursor in the top-lefthand-side and the mouse cursor. I asked him if he did anything.. such as 'sudo apt upgrade', but he told me no. This was really weird that (apparently) the SDDM broke by itself and now fixed by itself. Thank you very much for your help and info on the issue!
[12:59] <jubo2> Another Kubuntu back to operational (just a little weird not knowing how it broke nor how it got fixed)
[13:18] <jubo2> Reboot for upgrades. BBIAB
[14:26] <steve12345> are there any methods to disable right click activating menu items as an option or config file
[14:27] <steve12345> it's an accessibility issue for me
[14:29] <steve12345> https://i.imgur.com/kDoavPJ.png
[14:29] <steve12345> fresh install of kubuntu 18.10
[14:29] <steve12345> the mouse menu is weird
[14:34] <hateball> steve12345: I am not sure I understand
[14:34] <hateball> ah
[14:35] <steve12345> the screenshot is a secondary issue
[14:35] <hateball> you mean you rightclick to bring up a context menu, and then another rightclick activates the hilighted menu item
[14:35] <steve12345> well actually a single right click can open a context menu, and then activate a menu item
[14:35] <steve12345> in the up action of the click
[14:36] <steve12345> there are a few people online in my searching for a solution to this behavior confirming it
[14:36] <steve12345> in google
[14:36] <steve12345> it must be how I and those people use their mice
[14:37] <steve12345> it happens to me on kde plasma 4 all the time
[14:38] <hateball> well plasma 4 is kinda dead, but that is another issue
[14:38] <hateball> the same thing however happens in plasma 5 as well
[14:38] <steve12345> wooops
[14:38] <steve12345> I mean plasma 5
[14:38] <steve12345> too many version numbers in my head
[14:39] <steve12345> is there a hack or workaround
[14:44] <steve12345> back
[14:44] <steve12345> had to reboot
[18:48] <skeledrew_> Hello. I have a dependency issue with apt that I'm hoping to get some help with. I am trying to create a portable setup for Kodi but I'm getting `kodi-bin:amd64 Depends on libegl1-x11:amd64 < none @un H > can't be satisfied!` Installing libegl-mesa, which contains that lib, doesn't work. Here's a complete run of the command: https://pastebin.com/mM2ZAYAX. Running Kubuntu 18.04. If anyone has ideas how to fix this and similar issue
[19:06] <acheronuk> skeledrew_: 2:17.6+git20171114.2125-final-0trusty
[19:06] <acheronuk> so you have a PPA for trusty enabled, or some left over conflicting packages from one
[19:08] <skeledrew_> acheronuk yes I'm using trusty as I have a similar issue using bionic, but with more things broken IIRC. I'll revert and try again to get that particular output
[19:09] <acheronuk> skeledrew_: well, if the packages are from an unsupported PPA we may be limited to what we can suggest
[19:20] <skeledrew_> acheronuk: I have the same issue when using Bionic: https://pastebin.com/4jfFxxms. I appended the contents of sources.list. Unfortunately I may not be able to do anything about the trusty source as it is included by the tool I'm using (AppImage creator)
[19:28] <acheronuk> what is the output of 'apt-cache policy libegl1 libegl-mesa0'
[19:54] <skeledrew_> acheronuk: https://pastebin.com/88PU3LbG
[19:56] <skeledrew_> Also if it helps, this is the tool I'm using: https://github.com/AppImage/AppImages/blob/master/pkg2appimage
[19:58] <jubo2> y0. My friend's SDDM broke again (after it had fixed itself with no action taken on part of the user). Looking at my own machine the /var/log/sddm.log is an empty file. Where can I find the relevant log?
[19:59] <jubo2> He got the same system as me, Kubuntu 18.04.1
[20:08] <acheronuk> skeledrew_: you have a package installed, or in a repo that wants to install it, that depends on older versions of mesa and libegl than are in the ubuntu-updates
[20:12] <acheronuk> in a clean and updated bionic VM, kodi from that PPA has no conflict. so it is something extra you have I guess
[20:16] <skeledrew_> acheronuk: how can I go about checking and fixing this? The only packages which should be installed are software-properties-common and kodi (for Kodi), and libcurl-slim and gnutls-patched (for pkg2appimage) along with their dependencies
[20:18] <acheronuk> one way is by sequentially listing the packages on an apt command
[20:18] <skeledrew_> I'm also running on a clean system (the other apps which I'm using have also been portablized), and I'm pretty sure Kodi will install fine with sudo, but that's what I'm trying to avoid in the first place
[20:19] <acheronuk> e.g: do 'apt-get install kodi software-properties-common'
[20:19] <acheronuk> see what is says can't be installed
[20:19] <acheronuk> add that to the apt line, and try again
[20:19] <acheronuk> and repeat
[20:20] <acheronuk> usually that eventually spits out a comprehensible reason
[20:21] <skeledrew_> I can't run it directly like that without using root. Is there a way to sandbox the operation if I use sudo?
[20:24] <skeledrew_> acheronuk: Adding to the generated apt-get command however gives `E: Package 'libegl1-x11' has no installation candidate`
[20:29] <acheronuk> libegl1-x11 is a virtual package that used to be provided by mesa on trusty, but does not exist on amd64 architecture on bionic
[20:30] <skeledrew_> Is there a way to determine how exactly it is resolved for Kodi?
[20:46] <acheronuk> difficult as 'apt-cache rdepends' does not pick up virtual packages
[20:47] <jubo2> Ok. Situation solved by moving the /etc/sddm.conf into safe keeping and regenerating sane defaults with 'sddm --example-config > /etc/sddm.conf'. My friend is young and not very attentive so I'm pretty sure he broke the conf by doing something he didn't understand. Infuriating that he wouldn't admit to it. But happy end. Another Kubuntu back up and operational! :D :D
[20:56] <skeledrew_> acheronuk thanks for the guidance. I was able to get the dependencies to resolve properly by rolling back to trusty with only `deb http://archive.ubuntu.com/ubuntu/ trusty main restricted universe multiverse` as added source and getting a single missing dependency from http://mirrors.kernel.org/ubuntu/pool/main/m/mesa/libgbm1_10.1.0-4ubuntu5_amd64.deb
[20:57] <acheronuk> skeledrew_: great. :)
[20:58] <skeledrew_> Now I only need to patch the bins to make the paths relative `bin/kodi: 170: bin/kodi: /usr/lib/x86_64-linux-gnu/kodi/kodi.bin: not found`
[22:20] <denza242> what's the recommended tool for making a liveusb
[22:23] <Perdellian> I used dd_rescue
[22:23] <Perdellian> less tetchy than using dd itself
[22:39] <genii> denza242: Since the ISO images are hybrid, you can just dd them directly to the USB stick
[22:41] <genii> Perdellian: The possible problem using ddrescue instead of regular dd is that ddrescue will continue going if it hits errors, so if the image is corrupt, or the area it's trying to write to is corrupt, you won't know
[23:19] <denza242> is 18.10 fairly stable?
[23:20] <jacky> yeah
[23:20] <jacky> I use it on my personal/work laptops!
[23:44] <valorie> denza242: using it right now
[23:44] <valorie> in fact, since the beta
[23:44] <valorie> zero problems