=== telnet is now known as tel === tel is now known as telnet === brainwash_ is now known as brainwash === kallesbar_ is now known as kallesbar [06:53] Hello. On MATE I switched from 16.04 to 18.04 and found a regression in the volume control. The master slider only has an effect when pulling it to "0" (which seems to enable "mute"), any higher value causes -0 dB attenuation on my output. [06:53] vlt: as in upgrade? [06:53] The volume sliders in the "applications" tab work. [06:53] lotuspsychje: No, fresh install, same hardware. [06:54] vlt: ok, have you doublechecked !sound [06:54] * vlt will [06:55] vlt: perhaps also a pavucontrol testing [06:55] lotuspsychje: Thank you. [08:02] does this +1 channel cover all the flavors till thursday? [10:25] what is shim signed and does it require a reboot? [13:17] I'm doing some due dilligence, testing some of my deployment scripts against Ubuntu 18.04, and I notice that there's something weird going on with maven's Java dependencies. [13:18] I'm kinda lost in the depends and provides loop, trying to figure out if it's an error or if I should report it. [13:18] I want to use openjdk-8-jre-headless. The tomcat8-common package is ok with this, but maven seems to always pull in Java 10. [13:29] Ah, openjdk-8-jre-headless provides java7-runtime-headless, and maven depends on java7-runtime-headless. [13:30] So it must be one of maven's dependencies that is pulling in Java 10. [13:30] which version of maven? [13:36] ekennedy80: System default maven, currently 3.5.2-2. [13:54] from the maven project: "Maven 3.3+ require JDK 1.7 or above to execute " [13:54] I don't think Java 10 is a direct dependancy [14:05] ekennedy80: Yeah, it's an Ubuntu dependency issue. :) [14:05] I think something changed in the last two weeks, because I had been testing this recently and it worked. [14:07] And according to `aptitude why openjdk-11-jre-headless` I see maven indeed is the one that pulled in openjdk-11-jre-headless, despite it depending on: default-jre-headless (>= 2:1.7) | java7-runtime-headless [14:07] And openjdk-8-jre-headless actually provides java7-runtime-headless, so that should suffice. [14:07] Must be a bug. [14:08] stickyboy: what did you specify to install? [14:08] stickyboy: you have to specify explicitly openjdk-8-jre-headless, or it will use 11 [14:10] nacc: I installed openjdk-8-jdk-headless (JDK) which depends on openjdk-8-jre-headless (JRE) which provides java7-runtime-headless. [14:10] stickyboy: right, but your default jre is 11 [14:11] nacc, but I'm installing openjdk-8-jdk-headless manually. [14:11] stickyboy: to get maven to use java8 probably requires you to update-alternatives at a minimum [14:11] Err, explicitly. [14:11] stickyboy: so? [14:11] stickyboy: what does `java -version` say? [14:12] Wait, but first, doesn't this mean a logical OR for maven's depends: default-jre-headless (>= 2:1.7) | java7-runtime-headless [14:13] I don't want to have to install Java 8 and Java 10 and then update-alternatives. The openjdk-8-jre-headless satisfies maven's dependency. That's why I think there's a packaging bug. [14:13] it means either of those packages provide the necessary dependency for that stanza [14:13] it doesn't mean if you pick one or the other that's what the package will use [14:14] since default-jre-headless is probalby *also* installed [14:14] nacc: Right, I'm not talking about what maven will use. [14:14] I'm talking about maven pulling in Java 11. [14:14] then I don't know what you're talking about stickyboy [14:14] stickyboy: what was the explicit apt-get line you used? [14:14] apt install openjdk-8-jdk-headless maven [14:17] stickyboy: ok ... read the dependencies again and read what you wrote again [14:17] jdk vs. jre [14:18] nacc: JDK pulls in JRE, and the JRE satisfies the java7-runtime-headless dependency of maven. [14:18] hrm, that may not be it [14:18] :) [14:18] stickyboy: when i try to run it, i don't get any reference to 11 [14:18] Totally a bug. Now I know I'm not crazy. [14:18] also default-jre is 10 in ubuntu [14:18] nacc: Ok, let me do one more thing: lemme clean up my apt sources. [14:19] stickyboy: oh i do see it pulling in default-jre-headless, though [14:19] I'm running through my normal Ansible provisioning scripts for our stack. The same ones I've been using since 12.04, 14,04, 16.04, etc. [14:19] BTW there's definitely something brewing with Java versions in Ubuntu 18.04: https://lists.ubuntu.com/archives/ubuntu-release/2018-February/004275.html [14:20] And this was working two weeks ago. [14:20] yes, we will be SRUing in newer versions [14:20] Awesome, you're "we" (Ubuntu). :P [14:21] Basically, I want to run Tomcat 8 with OpenJDK 8. It was working two weeks ago when I first started porting our playbooks. The app was running. [14:22] I technically don't mind if Java 11 is sitting there unused on the system, though it seems erroneous and wasteful if I have Java 8 and did not explicitly pull in Java 11. [14:22] I know we have to take pre-releases with a grain of salt, too, so I usually just wait a few days and apt update and try again. [14:26] Hold that thought, BRB. [14:46] I'm back, nacc, if you're still around. [14:47] stickyboy: ack, although i'm on the phone [14:48] stickyboy: i'm trying to see why default-jre-headless is getting pulled in, it's some other dep, i think [14:48] No problem. [14:49] stickyboy: intersting [14:50] i installed opejdk-8-jdk-headless first [14:50] then maven [14:50] and it dtrt [14:50] so it seems like, possibly a bug in apt? [14:50] let me ask around [14:54] nacc: What's 'dtrt'? [14:54] Typo or ubuntu dev slang? :P [14:55] do the right thing [14:55] Ah ok. [14:58] Ah, you're right. If I install opejdk-8-jdk-headless first then maven does not pull in Java 11. [14:59] nacc: ^ [14:59] stickyboy: ack, i'm arguing with the dev [14:59] LOL [15:02] nacc: Also, I just purged everything and tried with aptitude. It does the right thing. [15:04] stickyboy: strange [15:07] stickyboy: ok, so this seems to be one of those thing sthat 'can happen' -- you can look for apt bugs on it, or you can just use the workaround i suggested, which shoiuld always work [15:08] nacc: Yeah, I'm already adding a workaround in my Ansible playbooks so that openjdk-8-jdk-headless is installed first in a separate transaction. [15:08] stickyboy: yep, that should always be safe, and resolves the dependency tree outside of the single command [15:08] which was probably just 'ahppening' to work in older releases where java8 was the only option [15:09] Thanks for helping me track it down. [15:09] stickyboy: np [15:09] stickyboy: sorry for dismissing it as PEBCAK at first :) [15:09] tbh, java in 18.04 appears to be a mess [15:09] stickyboy: apt developer says they can't find the bug, so if you do want to file one, that'd be great -- it's definitely an unexpected behavior [15:10] hello. i filed a bug on launchpad. how can i set it as a regression bug? [15:10] boboma: as in an update to an existing release? [15:11] boboma: there are no 'regressions' in bionic, because it hasn't release yet [15:11] *released [15:11] a regression between 17.10 and 18.04 [15:12] there's an sru-regression (or regression-update) tag [15:12] but not sure if there is one for releases [15:13] hm. ok. how long does it usually take until somebody responds to bug reports? [15:13] i mean the maintainer of the program that has the bug for example [15:14] nacc: I could be inclined to file a bug about the apt dependency issue. Never done it for Ubuntu, though. Is it through Launchpad? [15:20] stickyboy: yes [15:20] boboma: ... often there is not 'the maintainer' [15:20] boboma: and it depends on the package involved [15:21] stickyboy: ok, got more clarifcation [15:21] you can hold off on the bug [15:21] it is what i said originally [15:21] you need to specify the jre explicitly [15:22] if you don't, the dependency resolution order is undefined [15:22] ith appened to be ok for you before, because probably there was only 8 [15:22] and 8 happened to be the default [15:22] nacc: Ok. [15:23] What is the pratical difference between running docker via apt vs via snap ? [15:25] What would you choose? [15:25] stickyboy: so the 'right' way is to specify openjdk-8-jre-headless rather than jdk-headless, i think [15:25] stickyboy: and confirmd, no 11 instllation [15:27] sveinse: practical? not much i'd assume. docker snap will update more frequently [15:54] nacc: I need JDK though. :) [15:55] stickyboy: ok, but not for maven itself [15:55] stickyboy: so then you'd also install that separately (i think) (or it could be on the same line as maven, but it doesn't have to dow ith maven) [15:56] nacc: Ah, I see this does work: apt install openjdk-8-jre-headless openjdk-8-jdk-headless maven [15:56] Because I guess it happens in the same transaction. [15:57] stickyboy: right, that's what i was saying before (the only bit that matters is the first and last packages) [15:57] openjdk-8-jdk-headless is an entirely separate package tree [15:58] nacc: Logically, though, openjdk-8-jdk-headless brings in openjdk-8-jre-headless, which satisfies maven's dependencies. [15:58] So that's frustrating. :P [15:59] stickyboy: as I said, it's about "when" dependencies are resolved [15:59] stickyboy: apt doesn't go to that level of recursion, I think [16:00] Yah, that's a hard problem to solve. [16:00] I don't mind working around it. [16:00] Like you said, though, I never ran into this before because I was already using Java 8. [16:01] well, because java 8 was the defeault [16:01] so you actually were installing a second pacakge (default-jre) [16:01] it just happened to be the same as what you wanted [16:01] I was using Oracle (!) Java actually, but yes. [16:01] Enough with Oracle binary crap. [16:02] Open source, reproducible packages for the mf win. [16:07] I've made a partial upgrade and it now starts without X, startx logs me in Gnome session and I can't figure how can I get to my login screen so I can log in XFCE session which I normally run [16:08] logout kills X again and gets me to tty1 [16:19] Volkodav: sudo systemctl start lightdm [16:19] or gdm3 (maybe without the 3) [16:34] join #nextcloud [16:48] if I install docker with snap, how do I setup access for a user? I notice that there is no /var/lib/docker* nor is there a docker user/group to add oneself to, so I'm kinda stuck what to do next [16:58] whts the default filesystem in bionic? [16:59] tda: ext4 [16:59] nacc: still? thanks [17:00] tda: ... why would it change? [17:02] a few other distros switched over to xfs. i usually use it to due to it just working and generally having fewer problems [17:02] tda: ext4 also 'just works' and ... I can't remember the last time I had a filesystem problem on Linux [17:02] tda: xfs is great for large files, but historically had issues with small files (which is the much more common case on desktops) [17:03] tda: in any case, I don't think there is any driving impetus to move to anything else [17:03] (I use ntfs - I'll go back to mute) [17:03] lol [17:03] lol [17:03] anyone try flash friendly? === czesmir_ is now known as czesmir [19:48] hi [19:48] how do i hide the firefox top bar? [19:48] file, edit, view, etc...? [19:53] why does the gnome software center installs another version of firefox (the snap one) [20:03] why is there no vlc in apt? [20:05] pepermuntjes: there is - https://packages.ubuntu.com/bionic/vlc [20:05] thanks, forgot to enable that repo [20:05] whats better from repo or snap package? [20:06] pepermuntjes: honestly, I think it's subjective. I'm not really up-to-speed on the whole snap idea, which may contribute to what disdain I do have for it... [20:07] pepermuntjes: you forgot to enable the ubuntu repo? [20:07] nacc: universe [20:07] pepermuntjes: ah, so not a default install [20:08] doing some testing using a live disk on a virtual machine [21:34] if i install ubuntu 18.04 "freeze" will there be anything different from the 18.04 LTS coming out tomorrow? [21:38] !final | en1gma maybe a couple small bug fixes [21:38] en1gma maybe a couple small bug fixes: If you install a development version of Ubuntu Bionic and keep up with package updates, then you will be upgraded to the official release of 18.04 when it comes out. To make sure, type « sudo apt update && sudo apt full-upgrade » in a terminal. [21:42] ok. gonna grab a daily build then "Ubuntu 18.04 LTS (Bionic Beaver) Daily Build" [21:43] will the software updater to tell me to do it also? [21:45] en1gma: I'm don't know if there would be any notification if you're already running the beta [21:46] s/I'm/I * === Smedles_ is now known as Smedles [22:23] For some reason the hidraw kernel module isn't loaded on the VM I'm running. I can't figure out why. I can see hidraw compile flag was set to yes, but lsmod doesn't show hidraw. I'm on bionic latest, with the latest updates, etc [22:23] Is the latest bionic kernel missing the hidraw kernel module? [22:38] ayee: I cannot see this module on the current an previous kernels [22:42] hggdh: The weird thing is this: ➜ /boot cat config-4.15.0-19-generic|grep -i hidraw; uname -r CONFIG_HIDRAW=y 4.15.0-19-generic [22:42] It seems like it gets compiled in? [22:47] Hi all, the unstable release broke my computer :P [22:49] More specifically, I suspend my Kubuntu 18.04 RC 1 install on actual hardware, resume it, and my trackpad goes totally nuts. Touches respond erratically and also type gibberish into any focused text field. [22:49] ayee: doesn't that mean it is compiled *in* the kernel? [22:49] ayee: as opposed to CONFIG_HIDRAW=m [22:50] ayee: yes, it is built in the kernel, not as a module [22:50] will I automatically get the latest gnome if I upgrade from 17.10 to 18.04? Is there a way to upgrade "cleanly"? I have multiple accounts on this computer and would prefer to not reformat and reinstall if possible. I am on artful 17.10 at the moment. Thanks [22:52] kus: you will get (mostly) Gnome 3.28 [22:53] oh, even evolution is 3.28 [22:54] oh wow nice [22:54] but I have learned to never ever enter my google information in evolution. #neveragain [22:54] heh [22:54] It fills up all usable memory with all my useless Google junk [22:55] I mean yeah I should clean up my Google account but I am lazy [23:03] Guest57550: have you filed a bug report? [23:04] `ubuntu-bug packagename` in the commandline from the computer that gets the problem [23:04] packagename will be synaptic or libinput *I think* [23:05] apt policy synaptic (or apt-cache policy) will tell you if that is installed [23:06] Well, the computer is out of commission :P [23:06] I can boot in recovery mode but if I try to enable networking it also starts Xorg [23:07] and? [23:07] and I can't type any more because I don't have libinput or networking :P [23:07] oh [23:07] so I can't reinstall it [23:07] hmmm [23:07] you should be able to reinstall..... [23:07] Yeah, I thought the package would be cached at least [23:08] but no dice [23:08] did you have problems before with this machine? [23:08] I don't recall anyone mentioning such a problem before [23:09] There's variations on it in the bug tracker already, some of which are quite old [23:09] It's a Thinkpad X1 Yoga 2018 [23:09] strangeness [23:09] what happens when you try to reinstall? [23:10] I've forgotten the package name but I'm using 'apt install', and it tries to update the index [23:10] no, no, I mean, with a USB try a NEW install [23:10] maybe not of ubuntu, but perhaps something else that might have the driver you obv. need [23:11] did you have an Ubuntu install on that computer before? [23:11] well, I can reproduce the issue in NixOS [23:11] But that allegedly uses synaptics anyway [23:11] so, not an ubuntu problem, but a driver problem [23:11] And potentially power management problem >_< [23:12] my son used to buy new gaming laptops and have a heckuva time finding a distro that had suitable drivers [23:12] always different [23:12] mandriva, manjaro, ubuntu, arch [23:12] "Get a thinkpad" they said, "they are easier to use with linux", they said... [23:13] did you try it with a live session? [23:13] and again, did you already have linux installed on this laptop before, that was working [23:13] Yeah, the live session worked except I didn't notice the inability to resume. NixOS' previous release worked too [23:14] I'd like to get this issue into the tracker for the Kubuntu LTS release, but I'm not even sure which component is to blame :P [23:15] it's probably the kernel /driver and other than that I dunno [23:15] perhaps comment on one of those old bugs instead [23:16] and maybe try the next spin which will have a new kernel [23:16] I think