[00:52] <Auctus> any ideas what it might be so i can dig deeper? just a vs code problem, graphics drivers, X11/whatever, something else?
[01:12] <alnr> after upgrade youtube videos wont start, it says "if playback wont being restart device", what is wrong?
[07:53] <Auctus> dell keyboard backlight timeout doesnt seem to work right in 18.04
[07:53] <Auctus> i think its set to 0sec delay even though the file here says 10sec http://www.dell.com/support/article/nz/en/nzdhs1/sln308123/how-to-configure-the-keyboard-backlight-time-out-interval-in-ubuntu-linux?lang=en
[07:54] <Auctus> worked fine in 16.04 
[07:54] <Auctus> im using an e7440
[07:54] <Auctus> does anybody even read this channel or should i just go harass some mailing list somewhere
[07:54] <lotuspsychje> here's fine Auctus 
[07:54] <lotuspsychje> !info xbacklight | Auctus could try this?
[07:54] <ubottu> Auctus could try this?: xbacklight (source: xbacklight): simple utility to set the backlight level. In component universe, is optional. Version 1.2.1-1build1 (bionic), package size 7 kB, installed size 24 kB
[07:55] <lotuspsychje> Auctus: checking your syslog or dmesg for acpi errors could be usefull or place a new !bug
[07:55] <Auctus> oh the LCD backlight works fine, as it always has, im talking about the keyboard backlight
[07:56] <Auctus> changing the brightness of the keyboard backlight is supported and works fine, shows the little icon on screen just llike changing the LCD backlight does (diff icons obviously)
[07:57] <Auctus> the timeout isnt working though, so the light fades out the second you touch a key, instead of remaining lit for 10s as it should be
[07:58] <lotuspsychje> Auctus: i would go for a new !bug mate, as your issue is pretty specific
[07:58] <lotuspsychje> Auctus: if it works in xenial, will be usefull to file the bug for 18.04 and mention that too
[07:58] <Auctus> where do i do that
[07:59] <lotuspsychje> !bug
[07:59] <ubottu> If you find a bug in Ubuntu or any of its derivatives, please report it using the command « ubuntu-bug <package> » - See https://help.ubuntu.com/community/ReportingBugs for other ways to report bugs.
[07:59] <Auctus> thanks
[07:59] <lotuspsychje> Auctus: feel free to share the url in here afterwards
[07:59] <Auctus> will do in a few minutes
[08:00] <lotuspsychje> Auctus: a few pointers to get luck on solving is try steps yourself as test, and fine more users to test same issue
[08:01] <Auctus> dunno how many userrs have this model of laptop, i guess it was a fairly popular business / ultrabook model some years ago, i just bought a refurb one in great shape
[08:01] <Auctus> dell e7440
[08:02] <Auctus> with a haswell cpu
[08:02]  * Auctus creates a launchpad account for bug reporting
[08:02] <lotuspsychje> cool
[08:06] <Auctus> "please provide your full name" -> first name No, last name Thanks, but then I decided I'd rather be Kevin Flynn from Tron. Now I'm on the Grid, lol.
[08:07] <lotuspsychje> lol
[08:09] <Auctus> this page is tremendously verbose. It should be broken into several
[08:11] <lotuspsychje> Auctus: broken?
[08:13] <Auctus> it took me some time to find out how to get to the page to report the bug
[08:13] <Auctus> which is at https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect
=== Smedles_ is now known as Smedles
[08:16] <lotuspsychje> Auctus: you can ubuntu-bug package-here from terminal to make all that automatic
[08:16] <lotuspsychje> it will create a page for you
[08:21] <Auctus> so i have learned if you change that file it will in fact start working, but it is in fact ignoring the default 10s and behaving as though its set to 0
[08:22] <Auctus> i assume i should still report this as a bug? it's a minor one lol
[08:22] <Auctus> might save someone else 20 minutes in the future though
[08:22] <lotuspsychje> Auctus: sure, creating the bug and then solve it yourself is very usefull for the community
[08:23] <lotuspsychje> Auctus: also perhaps devs might enable this by default instead of manually tune yourself?
[08:24] <Auctus> yeah thats my hope
[08:24] <Auctus> https://bugs.launchpad.net/ubuntu/+bug/1756815
[08:24] <ubottu> Launchpad bug 1756815 in Ubuntu "(18.04 only) dell keyboard backlight timeout is wrong / ignoring default 10s to be 0s" [Undecided,New]
[08:24] <lotuspsychje> lemme check
[08:26] <lotuspsychje> Auctus: looks pretty good, but i would perhaps add solution seperate in a new reply at bottom
[08:26] <lotuspsychje> aka: solution: edit file...
[08:29] <Auctus> will do in a minute also trying to cook dinner :p
[08:29] <lotuspsychje> sure tnx for adding the bug anyway Auctus 
[08:45] <Auctus> lotuspsychje: heres another one, only affects visual studio code on 18.04, also worked fine on 16.04: https://i.imgur.com/D5NsWjZ.png
[08:45] <Auctus> https://i.imgur.com/4k8MAlw.png
[08:45] <Auctus> weird garbage around the characters 
[08:46] <Auctus> idk if its somehow a webkit thing or something, i should install chromium and look at that and see if it affects that too
[08:46] <Faux> Are you on nouveau?
[08:46] <Auctus> Faux: whats that
[08:46] <Auctus> how do i check
[08:46] <Faux> You said you're using an intel card, not an nvidia card.
[08:46] <Faux> (So it doesn't apply.)
[08:47] <Faux> https://github.com/Microsoft/vscode/issues/37623 looks like your screenshot.
[08:47] <Faux> Fixed three days ago.
[08:48] <Auctus> Faux: are you a wizard? i was googling this for like 2 hours today and didnt find that
[08:49] <Faux> I'm an expert on the names of text issues, yes. :)
[08:55] <ktecho> Hey. Anyone willing to give a hand to debug a problem between Kubuntu a NetworkManager? The problem is that Wifi doesn't connect at startup. It errors out saying that it doesn't have "secret" or password or something like that. But if I click the "Connect" button after, it works ok.
[08:55] <ktecho> I don't know if the problem could be that KWallet is not available at boot, but it's available later, so it works when I click the button. This is with 18.04 updated. I have the relevant logs from NetworkManager here:   https://paste.ubuntu.com/p/fmcF6B5T6x/
[08:58] <ktecho> I can provide any log or try everything you need, so we make sure this don't get to 18.04 official
[09:01] <lotuspsychje> ktecho: system up to date? tryed network-manager restart?
[09:03] <ktecho> lotuspsychje: system up to date. If I  do network-manager restart, it connects to the wifi too. The problem ocurrs just while booting. If I restart the service, it works. If I click "Connect" button, it works.
[09:03] <ktecho> occurs*
[09:05] <lotuspsychje> hmm thats weird indeed
[09:06] <ktecho> I think the problem could be the ono described here:    https://bbs.archlinux.org/viewtopic.php?id=233519
[09:06] <ktecho> When I boot, KWallet is not available, so it doesn't work. But if later on I try to "Connect", KWallet is available so it provides the wifi password. Makes sense?
[09:09] <ktecho> It seems like this workaround works for some people at forums:  "Try to set “Store password for all users (not encrypted)” in the Wi-Fi Security tab. I know it’s not the optimal solution, but it works for me."
[09:10] <ktecho> Because if you set your password as "not encrypted", it's managed by NetworkManager itself instead of KWallet.
[09:10] <lotuspsychje> ktecho: you might wanna place a new !bug for this
[09:10] <ktecho> I'll test this, but would like to know if it's anyone interested in fixing this. Maybe Kubuntu devs.
[09:10] <lotuspsychje> ktecho: another test could be trying network-manager from proposed
[09:11] <lotuspsychje> !info network-manager
[09:11] <ubottu> network-manager (source: network-manager): network management framework (daemon and userspace tools). In component main, is optional. Version 1.10.4-1ubuntu3 (bionic), package size 1523 kB, installed size 6468 kB
[09:11] <lotuspsychje> this si your version ktecho ?
[09:12] <ktecho> 1.10.4-1ubuntu3 yes
[09:13] <lotuspsychje> kk
[09:14] <ktecho> Didn't know about proposed. Just enabled it, but there's no network-manager update
[09:16] <ktecho> lotuspsychje: You're right that I should open a bug report. It's just that I've seen so many networkmanager bugs that don't get attention...
[09:16] <ktecho> but I'm opening a bug right now and provide all the info I can
[09:16] <lotuspsychje> i got one running myself
[09:17] <lotuspsychje> ubuntu-bug network-manager
[09:17] <lotuspsychje> 2 chipsets on different machines no eth network can be connected
[09:18] <ktecho> regular ethernet or wifi?
[09:18] <lotuspsychje> ethernet on my side
[09:18] <lotuspsychje> wifi works like a charm on gnome here
[09:19] <ktecho> weird, as these days we have drivers for almost every network card. Do you have the "linux-firmware" package installed?
[09:19] <lotuspsychje> yeah
[09:20] <lotuspsychje> a ralink chipset & 3com
[09:20] <lotuspsychje> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755248
[09:20] <ubottu> Launchpad bug 1755248 in network-manager (Ubuntu) "Network card does not connect anymore" [Undecided,New]
[09:23] <ktecho> doesn't seem like a driver problem. NetworkManager then
[09:24] <lotuspsychje> yeah it work at early bionic stage
[09:24] <lotuspsychje> then after few updates broke
[09:24] <lotuspsychje> i guess final might solve that
[09:25] <lotuspsychje> probable your case aswell ktecho 
[09:26] <lotuspsychje> anyway bbl for work
[09:26] <ktecho> I don't know. But it would be nice to have it fixed before final. Anyways, the problem don't hit me so hard because I rarely reboot my pc. I suspend it, and it resumes back with wifi on. But wants to have it fixed for other people because it's annoying.
[09:26] <ktecho> bbl
[09:27] <lotuspsychje> ktecho: yeah agree, bug it and lets c what happens
[13:21] <NotHere> any option to turn off bell on ubuntu 18.04? I can even change the bell sound by selecting a different sound theme, but when I choose "No Sounds" as the theme, I still get sounds
[13:21] <NotHere> the "No Sounds" theme option, has the "Ubuntu" theme sounds
[13:21] <NotHere> MATE enviroment in ubuntu-mate
[13:25] <NotHere> "Mute" works btw...
[13:31] <eoli3n> Hi
[13:32] <eoli3n> is there any prebuild of xubuntu 18.04 ?
[13:32] <eoli3n> or i should work on ubuntu 18.04 daylibuild
[13:32] <eoli3n> ?
[13:32] <eoli3n> i need to start to test my ansible playbook, it is huge and will necessite a lot of work to migrate i think, so i need to start early
[14:04] <tfgbd_> Why does my machine power off while booting Ubuntu?
[14:05] <tfgbd_> I'm using the latest 18.x from a few days ago
[14:07] <tfgbd_> My computer has an Atom Baytrail
[14:10] <tfgbd_> I know support of these is very expirimental
=== caravena_ is now known as caravena
[17:42] <flocculant> eoli3n: there are dailies of xubuntu 18.04
=== Elimin8r is now known as Elimin8er