[01:07] <valorie> lovin' it too! also from Murrica
[03:10] <bobdobbs> Hi all. I've got an issue with kde desktop on ubuntu 20.04. The panel bar thing seems to stop working in an particular way...
[03:11] <bobdobbs> At first the clock seems to stop working. It stops at a particular time and just stays at that time.
[03:12] <bobdobbs> You know how the panel advertises the apps that are minimised? Well, after the clock stops working, something odd happens:
[03:12] <bobdobbs> If I click on a minimised app in the panel to pop it up to the desktop, sometimes the wrong app appears.
[03:13] <bobdobbs> It's as if the panel is still working, but isn't repainting.
[03:13] <bobdobbs> So I'm clicking on the app that was painted there before the bug kicked in... and not the app that I want
[03:14] <bobdobbs> Some things still work. Like the grid icon that opens up the application browser.
[03:14] <bobdobbs> But that makes sense - because it's always in that position, it's position is never repainted
[03:14] <bobdobbs> It's a bit like playing battleships when I want to re-open an app
[03:16] <bobdobbs> The only way I can work around the issue is to completely log out and log in again
 Eheu
[12:46] <BluesKaj> Hi all
[13:14] <noob8650> I have been having issues with auto-hiding the panel. On my laptops screen it works but on the secondary Monitor connected via HDMI  the panel doesn't auto-hide. What can I do? [Kubuntu 20.04, KDE 5.18.8, KDE Frameworks 5.68.0, Qt 5.12.8, Linux 5.13.0-39-generic]
[13:45] <nikola_> hi guys. i upgraded from 20.04 to 22.04 and it was flawless. but now afte some updates i don't have "battery and brightness" widget in system tray. anyone have the same issue?
[13:47] <BluesKaj> nikola_, right click in the system tray and choose configure, then check the entries section
[13:49] <nikola_> already checked that, even if i choose "always shown" it does not show
[13:49] <nikola_> thank you for the tip/help :)
[13:50] <BluesKaj> are your updates/upgrades up to date ?
[13:52] <nikola_> yes, i think some update broke it, it was working yesterday. 22.04 is not official yet, i expect bugs, but this is annoying :)
[13:53] <user|95> My terminal has stopped appearing. How can I get it to return?
[15:27] <BluesKaj> !specs
[15:48] <alkisg> Wth, where's MATE there? :D
 Folks... just downloaded and tested out Kubuntu (daily) 22.04
 It's friggin magnificent!
 Seriously... the best desktop experience I've had.
 In terms of completeness of a Desktop, I've always recommended Linux Mint to Noobs... but with this version Plasma in Kubuntu and all the things that Kubuntu team has done to give it a complete experience... its just about par.
 One thing that I'd like them to do is enable Flatpak and Flathub by default in the Discover store... I know this is Ubuntu project, and Ubuntu Promotes SNAPs... but that would be my only criticism... because a new comer would not necessary do a search for 'flatpak' in Discover, and then choose to click on 'plasma-discover-flatpak-backend'... and then click 'add Flathub' after they reboot it.
 But outside that... this is as close to flawless that I've ever seen for PLASMA Distro!
[23:46] <user|27> como instalo kubuntu en windows 10
[23:46] <user|27> ?


[20:00] -ChanServ:#ubuntu-bd- pavlushka added *!ns22@fedora/rhct to the AKICK list.
[20:02] -ChanServ:#ubuntu-bd- pavlushka added FiXato to the AKICK list.
[20:03] -ChanServ:#ubuntu-bd- pavlushka removed FiXato from the AKICK list.
[20:03] -ChanServ:#ubuntu-bd- pavlushka added *!*ns22@fedora/rhct to the AKICK list.
[20:05] -ChanServ:#ubuntu-bd- pavlushka removed *!*ns22@fedora/rhct from the AKICK list.
[20:05] -ChanServ:#ubuntu-bd- pavlushka removed *!ns22@fedora/rhct from the AKICK list.
[20:06] -ChanServ:#ubuntu-bd- pavlushka added *!*ns22@fedora/rhct to the AKICK list, expires in 1 day, 0:00:00.


[13:52] <maetthew> Hello people! I'm trying to ditch Windows in favor of Budgie and so far I'm very pleased with it. I have an issue though I'm hoping to get some help with. I've been googling for approx 2 hrs trying to find out how to easily connect my Android device to Budgie and I found KDEConnect which seems to work ok except for a few quirks. One of them being I can't send any SMS (as in there are no option in the indicator menu). Anyone here
[13:52] <maetthew> have experience with Budgie and KDEConnect?
[13:53] <maetthew> Or do you have any other suggestions in terms of software to accomplish this?
[19:32] <MrAureliusR> maetthew: If you use Android and you want to send SMS, just use messages.android.com
[19:33] <MrAureliusR> I love it
[21:17] <maetthew> MrAureliusR: I'd rather not. Trying to stay away as much as possible from Google. Textra does it for me
[21:18] <MrAureliusR> ... yet you use an Android phone?
[21:18] <maetthew> Heh, knew youd say that :) I'm not that "hardcore", to me there isn't really anything better. I just try to keep it as barebones and minimal as possible
[21:19] <MrAureliusR> :P
[21:19] <MrAureliusR> well, it's just the built-in messages app in a browser tab, basically
[21:19] <MrAureliusR> I couldn't live without it now that they've introduced it
[21:19] <maetthew> Hmm
[21:19] <MrAureliusR> I tried to sort of hack it into Windows back when I used windows and it *sorta* worked


[07:01] <YoBoY> bonjour
[14:57]  * Cheesehead drops by to read the scrollback
[17:11]  * DarwinSurvivor drops by because Cheesehead's comment triggered irssi's "unread messages" flag for the channel


[00:10] <ikonia> and he's gone
[00:56] <ikonia> I'm going to table the idea of "pass a common sense test in #ubuntu before getting +v" to the council, it's a mess
[00:57] <ikonia> (I'm of course being sarcastic)
[01:03] <ikonia> hello myriam_rs
[01:04] <ikonia> myriam_rs: can we help you today ?
[01:07] <ikonia> myriam_rs: I would appreciate you responding
[01:13] <ikonia> !idle | myriam_rs
[01:16] <ikonia> !ops | myriam_rs
[01:17] <ikonia> sorry, harsh call
[01:18] <pleia2> ikonia: that's Mamarok, she is always here :)
[01:18] <ikonia> never seen that nick
[01:19] <ikonia> and she's not identified, didn't know, thank you
[01:25] <ikonia> oh dear
[01:28] <ikonia> ossurayy1ot: hello
[01:28] <ikonia> ooh, it's tony
[01:28] <ikonia> lots of different nicks
[01:32] <nhandler> This is where stalker.pl comes in handy
[01:33] <IdleOne> I got one
[01:48] <Myrtti> ikonia: mr-rich? im on mobile, impossible to do anything
[01:49] <ikonia> Myrtti: I'll look
[01:49] <ikonia> not been following
[01:50] <ikonia> thanks Myrtti
[01:52] <Myrtti> no problem, that's why I noticed him  .because hequit on excess flood so often it fit on my phone screen
[01:52] <ikonia> I had too many people on the go
[01:52] <Myrtti> stupid phone keyboard
[01:53] <Myrtti> noticed that too
[01:53] <ikonia> didn't see him joining/parting
[02:14] <Mamarok> sorry, I had some connection problems
[02:28] <famicube64> haaaaaaaaaaar har har
[02:32] <Myrtti> right
[02:40] <_Synergy_> ubuntu ops : bots are refusing me access to #ubuntu saying I have https://help.ubuntu.com/community/FixDCCExploit
[02:40] <_Synergy_> but I'm on port #7000 (ssl) not 6667 or whatever that page says
[02:40] <_Synergy_> the bot will not test me, can someone here manually test me pls (or fix the bots)
[02:41] <_Synergy_> for the past 10 min I get:    <FloodBot1> _synergy_: Sorry, you'll have to wait a little longer, we are experiencing problems... hold tight!  I need to leave but if anyone could keep an eye on them please do.
[21:35] <Tm_T> on it, thanks
[21:37] <IdleOne> ork?
[21:37] <CarlFK> (03:36:53 PM) ork left the room (quit: Remote host closed the connection).
[21:37] <Tm_T> yup
[21:37] <IdleOne> sorry, didn't see him at first
[22:23] <Tm_T> K'night
[22:23] <IdleOne> night Tm_T and Merry Christmas!
[22:24] <Tm_T> it's saturday for me, but thanks
[22:24] <Tm_T> ->


[08:38] <knittl> once I install pcmanfm, it is used everywhere. How can I switch back to nautilus? (without removing pcmanfm)
[08:46] <lordievader> Good morning.
[11:14] <BluesKaj> Howdy all


[05:18] <NickZ> I'm getting a strange error on ubuntu bionic server install; it's attempting to run zpool and failing because it's not installed
[05:20] <NickZ> https://pastebin.com/CpiyUrMy
[05:20] <NickZ> anyone else run into this?
[05:20] <NickZ> relevant line starts at 162
[05:26] <X-Rob> NickZ: at a guess, you have an existing zfs pool there and curtin doesn't know how to handle it. Disconnect the drives?
[05:31] <NickZ> nope, these are completely clean drives
[05:32] <NickZ> manually partitioning the drives prior to install seems to resolve the issue
[06:30] <^Squirrel^> hi, can I get help for ubuntu gere?
[06:32] <hateball> !ask | ^Squirrel^
[06:33] <^Squirrel^> I have a folder /proc/4838/cwd that is 9.4G, process 4838 identified as Samba - I think it is killing my server - is it normal that it should be so big, and if not, how to I get it back to normal size?
[06:33] <^Squirrel^> my server being the server on which that ubuntu runs, of course
[06:36] <lordievader> Good morning
[06:37] <^Squirrel^> alternative question: I have a partition for /, one for /home and one for /var. I would like to find the larger files for the / partition, a way that doesn't scan the other (mounted) partitions even if linked to it - is there a way to do that?
[06:37] <^Squirrel^> morning lordievader
[06:39] <keithzg[m]> Hah, just ran the 16.04 -> 18.04 upgrade on a server with molly-guard installed, and molly-guard cancelled the automatic reboot afterwards
[06:40] <lordievader> ^Squirrel^: `du -x` skips directories on different file systems, as per the man page.
[06:42] <^Squirrel^> thanks
[06:42] <^Squirrel^> so "du -x /" is what I should run?
[06:52] <^Squirrel^> ok that works, still doesn't tell me what is filling my 10G of /root folder
[06:52] <^Squirrel^> folder/partition
[06:56] <mdeslaur> rbasak: are you planning on working on that mysql merge?
[06:57] <mdeslaur> rbasak: or is lars doing it?
[06:58] <rbasak> mdeslaur: we're taking care of it. Lars has a branch up for review. I'm hoping to get to it today, but I'm not sure.
[06:58] <mdeslaur> rbasak: ok, cool, thanks!
[07:04] <^Squirrel^> lordievader, is there a way to check what size the folders are (the sum of the files in that folder and subfolders) on a server (no GUI)
[07:07] <rbasak> ^Squirrel^: du. See the du manpage for details of -s and -c.
[07:07] <rbasak> Or you can use baobab on a desktop machine connecting over ssh.
[07:07] <sarnold> ^Squirrel^: du -shx /*  may be useful
[07:08] <^Squirrel^> thank, will try. Root space free is 0  I can't install anything new
[07:08] <^Squirrel^> I have ssh access too yes
[07:13] <lordievader> du is installed by default.
[07:15] <^Squirrel^> rsalveti, sarnold, I use these thanks
[07:15] <^Squirrel^> lordievader, yes, of course
[07:15] <^Squirrel^> this is weird
[07:16] <^Squirrel^> df reports that my root partition is 0, but sudo du xhc reports 3.6G is used. / is a 10G partition
[07:17] <^Squirrel^> I am using LVM, can it be the reason?
[07:19] <lordievader> Might simply be removed files in use.  df sees those, du doesn't.
[07:22] <^Squirrel^> so what does "removed files in use" mean?
[07:23] <^Squirrel^> I have rebooted the server, this partition is still full
[07:23] <^Squirrel^> that's 5G worth of dark matter
[07:24] <jelly> ^Squirrel^: no, lvm is not the reason.  Look for unlinked files still in use by opened processes.
[07:25] <sarnold> a reboot is a good way to fix that though :/
[07:25] <^Squirrel^> I rebooted already, twice, to no avail
[07:25] <^Squirrel^> jelly, how do I do this?
[07:25] <sarnold> lsof or fuser are the usual tools
[07:25] <jelly> you might have files hiding under a mountpoint below this one
[07:25] <jelly> lsof -n +L1
[07:26] <sarnold> jelly: ooh +1
[07:26] <jelly> but if you rebooted that would have cleared the processes
[07:26] <^Squirrel^> no output of this lsof
[07:26] <^Squirrel^> lsof -n +L1
[07:27] <jelly> how many mountpoints do you have other than / ?
[07:27] <jelly> with real filesystems or bind mounts
[07:27] <jelly> (also, doing anything with /* is bad form, avoid)
[07:28] <^Squirrel^> expcluding tmpfs and udev, 16
[07:28] <jelly> umount everything else under / and retry du -x /
[07:28] <sarnold> jelly: how else would you get a list of all top-level files and directories?
[07:28] <jelly> siwtch
[07:28] <^Squirrel^> in reality, about 8 I explicitly mounted
[07:28] <jelly> sarnold: ls -ld, not du
[07:29] <jelly> or echo
[07:29] <^Squirrel^> including /var
[07:29] <^Squirrel^> and /home
[07:29] <sarnold> jelly: ls and echo do not summarize the sizes of all files linked in all directories underneath those top-level directories
[07:29] <jelly> sarnold: what use are sizes of files in /proc
[07:30] <sarnold> jelly: good point.
[07:31] <^Squirrel^> ok jelly, this might be getting somewhere - umounted -a then I get a total which corresponds more to df outuput
[07:31] <jelly> (procfs is slow, in might take half an hour just traversing that on a busy system)
[07:33] <jelly> du can very well traverse directories on its own, no need to help it with *
[07:34] <jelly> ^Squirrel^: look at directory contents previously hidden under other mountpoints
[07:35] <sarnold> ^Squirrel^: btw, once you've got some space to install new packages, ncdu may be to your liking :)
[07:35] <^Squirrel^> I tried to install ncdu, can't :P
[07:36] <^Squirrel^> but once I find the problem here, I will
[07:36] <^Squirrel^> I need to create a root user now - I can't unmount /home otherwise
[07:36] <sylario> I have a problem, I have a 16.04 server that lose all network connectivity from time to time. I can see the DHCP addresses in ip a, but I cannot ping it and it cannot ping anything
[07:37] <jelly> sure you can, just get your CWD ass out of /home
[07:37] <sylario> Network come back with sudo systemctl restart networking
[07:37] <jelly> (but having root is always nice, for other reasons)
[07:38] <^Squirrel^> lol I could just CWD out indeed
[07:38] <jelly> or as they call it in sh, "cd"
[07:38] <jelly> lsof -n|grep /home
[07:39] <^Squirrel^> but I can't umount home, cause I'm still logged into a user using /home...
[07:45] <^Squirrel^> ok /home umounted...
[07:47] <^Squirrel^> jelly, du -x / still reports some of the umounted folders...
[07:48] <^Squirrel^> yup. that's it :)
[07:48] <^Squirrel^> I knwo the problem now
[07:48] <^Squirrel^> Yay!
[07:48] <^Squirrel^> thanks guys!
[07:50] <^Squirrel^> Solved!
[07:52] <^Squirrel^> thanks jelly especially :)
[08:10] <sylario> What can I do to investigate losing connectivity after a reboot?
[08:11] <sylario> The system has the correct IPs, but there is no connectivity at all without rebooting networking
[08:11] <sylario> from syslog and apache, I can see the machine rebooted around the time of the problem
[08:15] <tomreyn> sylario: maybe the dhcp server wasn't working by the time your system booted up again?
[08:15] <tomreyn> oh you saiid it got the correct ips, sorry
[08:15] <sylario> It's some kind of xen hosting I think
[08:16] <tomreyn> so does resolving not work then, or are remote (and what about local) targets not reachable if addressed via ip address either?
[08:17] <tomreyn> * lacal targets, such as you gateway
[08:18] <sylario> I have access via an emergency console, I cannot ping google or the french taxes office from the problematic server, I cannot ping any of the server's IPs
[08:18] <sylario> sudo systemctl restart networking solve everything
[08:18] <tomreyn> the servers' LAN or WAN IPs?
[08:19] <tomreyn> and where from
[08:19] <sylario> It has only public IPs, not addresses in private ranges
[08:21] <tomreyn> ok so i'm wondering whether while this problem occurs, you could, from the server, ping <IP_ADDRESS> or <IP_ADDRESS> or the servers' gateway (as listed by ip route | grep ^default)
[08:21] <sylario> I try to ping it from public IPs from two different ISP, and I connect on it with an emergency console provided by the hosting company
[08:21] <sylario> I did not try that
[08:22] <tomreyn> in case you wont be able to ping the gateway when it happens again, talk to your hosting company.
[08:23] <tomreyn> in the meantime review /var/log/syslog to get a better idea of why the network didn't come up fully after the reboot.
[08:27] <sylario> tomreyn: thx for your help, i'll try that as soon as I can test on the server.
[08:27] <sylario> It will go in the next ticket
[12:18] <vimes> hello! I just rented an Ubuntu VPS but I see some weird traffic spikes, I wondered if any one had some recomendations for some good traffic montioring tool, preferably that saves traffic so I can see when traffic spiked and what caused it, a web gui would be nice but terminal works too. preferably open source
[12:20] <sarnold> vimes: perhaps ntopng is the tool you want
[12:21] <vimes> thanks! I'll check it out sarnold
[12:58] <rbasak> vimes: iftop for realtime viewing. Not sure about looking later though. It would make sense for it to have a pcap replay feature but I don't see that.
[16:31] <tobias-urdin> jamespage: heads up on possible upgrade path bug for keystone, dont know how to add ubuntu tracking
[16:31] <tobias-urdin> https://bugs.launchpad.net/keystone/+bug/1793347
[16:34] <tobias-urdin> coreycb: ^
[16:43] <bin_bash> are auto-upgrades enabled by default? I have a vm that was provisioned and it was, and I'm trying to determine if this is a provisioning problem or a distro problem.
[17:00] <leftyfb> bin_bash: I don't know for sure, but you can easily find out by spending the 1 minute it takes to do the server install from usb onto a device
[17:00] <bin_bash> sure if i had a device to install it on
[17:00] <bin_bash> but i dont so i'm asking here
[17:10] <tobias-urdin> jamespage: coreycb and another possible one https://bugs.launchpad.net/nova/+bug/1793353
[17:13] <pragmaticenigma> bin_bash: Virtual Box is a decent way to test things with temporarily
[17:17] <nacc> based upon a bionic lxd, it seems like some sources are enabled. That is the cloud image, though, not necessarily the same as the base server install
[17:19] <pragmaticenigma> I thought server enabled root and -security by default... I just can't find the documentation on it.
[17:22] <bin_bash> pragmaticenigma: sure if that was a viable option, but it's not unfortunately.
[17:22] <bin_bash> nacc: that's pretty terrible...
[17:23] <pragmaticenigma> bin_bash: what do you mean by terrible?
[17:23] <bin_bash> pragmaticenigma: if i install a package of a specific version on a freshly provisioned VM, and then come back the next day, the package shouldn't have been upgraded.
[17:23] <bin_bash> but that's exactly what happened.
[17:25] <pragmaticenigma> bin_bash: If it is truly the default of -security having been enabled, then the version didn't change, a patch was applied to mitigate a security vulnerability. What package was auto-updated on you?
[17:25] <bin_bash> nodejs
[17:25] <bin_bash> APT::Periodic::Update-Package-Lists "1";
[17:25] <bin_bash> APT::Periodic::Unattended-Upgrade "1";
[17:26] <bin_bash> this was the content of /etc/apt/apt.conf.d/20auto-upgrades
[17:27] <pragmaticenigma> bin_bash: what about the 50* one?
[17:28] <bin_bash> do you want the whole thing in a paste?
[17:28] <bin_bash> it's actually mostly commented out
[17:29] <bin_bash> pragmaticenigma: https://0bin.net/paste/rLMnSMn5X4TrAjtu#8GTWJhVLB7ukZuOZw8G5nCySn5G7pdsV6ZcAGrf+I1Z
[17:30] <pragmaticenigma> bin_bash: If what I've found so far is true, only the first two are not commented out... the rest are... specifically -security isn't commented out
[17:30] <pragmaticenigma> bin_bash: the link says there is no paste there
[17:30] <bin_bash> then someone else must have clicked it
[17:30] <bin_bash> is there a bot that crawls links and opens them?
[17:31] <pragmaticenigma> anyone in this room could have clicked that before I got the chance to
[17:32] <bin_bash> Unattended-Upgrade::Allowed-Origins {
[17:32] <bin_bash>         "${distro_id}:${distro_codename}";
[17:32] <bin_bash>         "${distro_id}:${distro_codename}-security";
[17:32] <bin_bash> "${distro_id}ESM:${distro_codename}"
[17:32] <bin_bash> thats the only uncommented part
[17:32] <pragmaticenigma> including the bots... with the spam attack on freenode
[17:32] <bin_bash> oh and this
[17:32] <bin_bash> Unattended-Upgrade::DevRelease "false";
[17:32] <bin_bash> i mean it was mere seconds between pasting and you trying to click, so it must have been something automatic. never had that problem in another channel, most bots just fetch metadata
[17:33] <pragmaticenigma> okay, from what you have posted so far then... your instance is setup to only auto update security patches.
[17:33] <bin_bash> hm
[17:33] <bin_bash> even this though?
[17:33] <bin_bash> "${distro_id}:${distro_codename}";
[17:33] <bin_bash> that doesn't have -security
[17:34] <pragmaticenigma> that is your "root" store... the items in there do not change until a point release occurs, suchas 18.04.1 to 18.04.2
[17:34] <bin_bash> plus if i specifically install a version (which I did), that should add some kind of flag, right?
[17:34] <pragmaticenigma> bin_bash: no... those are defined in another file, explicately by the person doing the sysadmin
[17:35] <bin_bash> =/
[17:41] <pragmaticenigma> I wish I could find release notes to verify the enabled by default for you. Short of installing (which I can't do at my present location) I can't find anything online to verify other than a bug that 16.04 ignored a users selection of no unattended updates
[17:42] <bin_bash> yeah thats what i was looking for as well
[17:42] <bin_bash> but didn't find it
[17:43] <bin_bash> thank you for looking though
[17:43] <pragmaticenigma> bin_bash: the closest that I can find is Ubuntu Desktop Gnome/unity have installed the package by default, and in Debian, the default configuration is to enable the main or root and the "-security" by default
[17:44] <bin_bash> hm interesting
[17:44] <pragmaticenigma> bin_bash: I know that Ubuntu Desktop asks during installation, and by default has "Install security updates without confirmation" preselected
[17:44] <bin_bash> this is jsut a weird one-off package. gotta have node6 for this dumb  thing -.-
[17:45] <pragmaticenigma> bin_bash: I was partitially expecting you to mention something about GhostScript, as there were some significant security vulnerabilities patched in the last 24 hours
[17:45] <bin_bash> ahh
[17:46] <bin_bash> well i had a helluva time installing node6 at all. every other time ive done it on 16.04 i just added the source list and then apt install and it was fine
[17:46] <bin_bash> this time i had to specify the version
[17:48] <pragmaticenigma> I wish I were more familiar with it... I know 18.04 some foundational pieces where significantly changes (netplan, etc) that have made some rather hard support questions
[17:52] <pragmaticenigma> bin_bash: Found it! The default config file for the unattended-upgrades package has main and -security enabled by default in 50unattended-upgrades
[17:52] <bin_bash> it seems like something that should be documented
[17:52] <bin_bash> oooo
[17:52] <bin_bash> where did you find that
[17:52] <pragmaticenigma> https://launchpad.net/ubuntu/+source/unattended-upgrades/1.1ubuntu<IP_ADDRESS>
[17:52] <bin_bash> thank you!
[17:52] <pragmaticenigma> rather: https://launchpad.net/ubuntu/+source/unattended-upgrades
[17:53] <bin_bash> perfect
[17:53] <bin_bash> i read that as "unintended upgrades"
[17:53] <bin_bash> hahaha which is more fitting -.-
[17:54] <pragmaticenigma> yeah... I go back and forth on whether I want to enable it... sometimes I get really tired of the prompts on Desktop... at the same time, I run MythTV and don't want it to decide to apply updates in the middle of a recording and trigger the daemon to restart
[17:55] <pragmaticenigma> I typically install all instances from the mini.iso release. In part because I can still install to 32 bit machines with it, and it's the same dialog prompts no matter what the final version I'm intending to install
[17:55] <pragmaticenigma> and depending how far into the release we are, I don't have to spend an extra hour or two installing updates after installing the release
[17:57] <pragmaticenigma> bin_bash: from this, I would assume the author of your vm included/installed the unattended upgrades package. Assuming they either clicked through accepting the default selections or installed the package after the fact, I don't think it was the vm's authors intent to misconfigure. As much as trying to follow the defaults offered by the original installation
[17:58] <pragmaticenigma> bin_bash: it really should be better documented. it's even harder for server as most the documentation highlights the desktop installations more than server. I would assume Canonical would rather people installing server sign up for a support plan
[18:06] <bin_bash> it's just so frustrating. i dont think anything should automatically update on a server, that's just asking for problems.
[18:08] <pragmaticenigma> bin_bash: Agree'd to a degree... the problem is the number of systems that get abandoned or aren't maintainted regularly that really could benefit such that they don't fall vicitm to someone's bot net
[18:11] <pragmaticenigma> at minimum at least the security holes are plugged. If the unattended update broke your nodeJs application, that is really strange. unless it's the tenuous behavior of node6 (?) and ubuntu 18.04 you experienced?=
[18:13] <bin_bash> well the thing is that im installing it from nodesource
[18:13] <bin_bash> this is the official way of doing it according to nodejs
[18:13] <bin_bash> https://nodejs.org/en/download/package-manager/
[18:13] <bin_bash> unfortunately something must have changed in 18.04
[18:13] <bin_bash> because previously i just added the source, apt install, done
[18:13] <bin_bash> this time even after adding the source it STILL installed the one from the main repo
[18:14] <bin_bash> i had to do apt install nodejs=6.14.1-1nodesource1
[18:14] <bin_bash> this time, it's weird
[18:18] <pragmaticenigma> not too wiered... beneath the instructions for installing to Debian/Ubuntu... it mentions it only supports 16.04 and 14.04
[18:18] <pragmaticenigma> so I think that might be the root of your issue
[18:39] <bin_bash> ooh i didnt even see that
[18:40] <bin_bash> still though i dont think 18.04 was LTS when this was published
[18:42] <pragmaticenigma> probably not, and there are a lot of under the hood changes with 18.04 that they might be trying to hammer out
[18:43] <bin_bash> yea
[18:43] <bin_bash> bleh
[18:43] <bin_bash> effed up to call it LTS when theyre still fixing things
[18:43] <bin_bash> absurd
[18:47] <pragmaticenigma> bin_bash: depends on your perspecitve... If you take NodeJS out of the equation, 18.04 by itself is very stable (i'm currently running it) ... since nodejs team have to react to the change (they can't exactly see into what Canonical is planning for ubuntu) it takes a while before they get their dependencies and scripts polished and ready. There were some significant changes in 18.04 starting with the netowrk
[18:47] <pragmaticenigma> management, and even the daemon managment
[18:47] <bin_bash> im not just talking about nodejs though
[18:48] <bin_bash> in general a server shouldn't do upgrades without intervention by default
[18:48] <bin_bash> think about php for example. there are many platforms that only work on php 7.0 or php 7.1 but not both. if php were security-upgraded to 7.1, that could cause a huge problem
[18:58] <nacc> bin_bash: release don't upgrade major versions
[18:58] <nacc> generally
[18:59] <nacc> bin_bash: "LTS" has nothing to do with "bug-free"
[18:59] <bin_bash> but thats exactly what happened with nodejs lol so i can't really expect it to not happen with other packjages
[18:59] <nacc> bin_bash: you weren't using an ubuntu version
[18:59] <nacc> bin_bash: so go complain to node, not here.
[18:59] <bin_bash> what?
[19:00] <bin_bash> the problem was with the core ubuntu repo.
[19:00] <nacc> bin_bash: you were using some external repository, right?
[19:00] <bin_bash> i was TRYING to
[19:00] <bin_bash> but it kept overriding it
[19:00] <nacc> bin_bash: what is 'it'?
[19:01] <bin_bash> apt/synaptic
[19:01] <nacc> bin_bash: i think maybe you just don't understand how packages work...
[19:01] <bin_bash> i think maybe you're not understanding what i'm saying
[19:01] <nacc> bin_bash: are you complaining that 18.04 has 8.10.0 while you wanted 6.14.1 ?
[19:01] <bin_bash> If I were to install weechat on debian from the weechat repos
[19:01] <nacc> full stop.
[19:01] <nacc> weechat repos?
[19:01] <nacc> debian?
[19:01] <bin_bash> apt wouldnt then override that for the core repos
[19:01] <bin_bash> it's called an example
[19:02] <nacc> if the weechat version in debian was greater than from weechat then yes it would.
[19:02] <nacc> bin_bash: i am fairly sure you just didn't check versions of packages via `apt-cache policy`, didn't bother to pin, and are complaining about that.
[19:03] <bin_bash> no, i'm complaining that the system made an internal, automatic decision to upgrade a package from another repository
[19:04] <nacc> bin_bash: what 'other' repository?
[19:04] <nacc> bin_bash: apt-cache policy nodejs, please
[19:04] <bin_bash> and for the record, i /DID/ check apt-cache policy
[19:04] <nacc> (if nodejs is the package you are worried about)
[19:04] <bin_bash> jesus fuck. i literally said I installed the package from nodesource. overnight, ubuntu upgraded that package from the extra repository
[19:04] <nacc> because the version in ubuntu is greater
[19:05] <nacc> you are choosing to run some third party repositroy
[19:05] <bin_bash> except it shouldn't do that bny default
[19:05] <nacc> and didn't bother to configure your apt sources appropriately to pin it
[19:05] <nacc> that's your opinion.
[19:08] <_KaszpiR_> bin_bash apt-pin
[19:10] <bin_bash> _KaszpiR_: thats not a command. apt-cache search doesn't even return anything
[19:10] <_KaszpiR_> https://jaqque.sbih.org/kplug/apt-pinning.html
[19:10] <bin_bash> regardless, if i install a package from one repo, it shouldn't be overriden by a package from another repo
[19:10] <bin_bash> ive literally never encountered that on any distro
[19:10] <_KaszpiR_> not really
[19:11] <_KaszpiR_> welcome to debian :/
[19:11] <bin_bash> ive been using debian for years
[19:11] <bin_bash> and this is the first time running into this
[19:11] <bin_bash> ¯\_(ツ)_/¯
[19:11] <_KaszpiR_> heh, lucky you, then
[19:11] <_KaszpiR_> got that many times
[19:12] <bin_bash> maybe because usually the other repo has newer versions rather than older
[19:12] <bin_bash> i'm used to running outdated packages on arch because nothing is automated, everything is deliberate
[19:13] <pragmaticenigma> bin_bash: The repos are just storage containers... the repos themselves don't set a hierarchy. the packages themselves do with their naming convention since they sort alphanumerically. Debian happens to come earlier in the alphabet than Ubuntu... therefor an Ubuntu package is going to get precendence since it occurs later in the alphabet
[19:14] <pragmaticenigma> assuming the package name is of 6nodejs-ubuntu-18.04 versus 6nodejs-debian-9
[19:14] <bin_bash> pragmaticenigma: tbh mostly my upset is regarding a package being changed in any way without my deliberate action, and having this set as a default parameter and also not well-documented is porblematic
[19:15] <pragmaticenigma> I assure you it's documented somewhere... but the joy of linux is... where?
[19:17] <bin_bash> i didnt say totally undocumented, i just said not well-documented. :P
[19:18] <pragmaticenigma> I have the same premise
[19:22] <nacc> appears to have changed in ubuntu with https://git.launchpad.net/ubuntu/+source/unattended-upgrades/commit/?id=558990e4
[19:22] <nacc> not 100% on that
[19:22] <nacc> it used to be -security only, though, and then the release pocket was added
[19:23] <pragmaticenigma> nacc: that jives with what I found in the package from launchpad
[19:24] <nacc> in this case, it wouldn't matter, though, actually
[19:24] <nacc> a newer version is in ubuntu, period
[19:25] <nacc> and the -security case has been that way for quite some time
[19:25] <nacc> maybe unattended-upgrades became installed by default, dunno
[19:27] <pragmaticenigma> nacc: I remember seeing it somewhere that server began installing it by default, but I just can't find a release note or documentation on it
[21:33] <grandy> hello, probably a dumb question: how to I get cloud-init to write the netplan file ?
[21:37] <grandy> i edited the clout-init file but not sure what command makes it generate the outputs
[21:38] <nacc> grandy: cloud-init runs once at boot
[21:39] <grandy> nacc: hmm, my ubuntu server install has a comment in the netplan that it was generated by cloud-init. I modified the cloud-init file in question and rebooted, but it did not update the netplan file.  Just trying to add another network interface
[21:42] <nacc> grandy: which file did you edit?
[21:45] <grandy> nacc: /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg
[21:46] <nacc> smoser: rharper --^ ? i don't know, tbh; does it need to be in the initrd instead?
[21:48] <grandy> nacc: i added the enx... interface, eno1 was already configured: https://pastebin.com/m6vyvDeJ
[21:49] <smoser> grandy: that will only be written once per instance.
[21:49] <smoser> so if the instance-id has not changed, changes to that will not get updated to the system.
[21:49]  * smoser has to go afk.
[21:49] <grandy> smoser: ahh, ok, so it's mainly for the intial config of the machine... where would i add a new network interface?
[21:50] <nacc> grandy: what do you mean 'add a new network interface'? You mean just the configuration for it, right?
[21:50] <grandy> smoser: yeah just to tell it to bring it up and use dhcp
[21:51] <nacc> grandy: i think you just want to put that in your netplan config file, no?
[21:51] <grandy> smoser: there is a configuration in /etc/netplan that is generated by cloud init, but it warns that it might be regenerated.
[21:51] <nacc> grandy: i mean, you can add another file in /etc/netplan, aiui
[21:52] <grandy> nacc: ahh ok, this is the contents of /etc/netplan/50-cloud-init...
[21:52] <grandy> https://www.irccloud.com/pastebin/RxCAvqeg/
[21:52] <nacc> grandy: right, so leave that one alone (i think)
[21:52] <nacc> grandy: and add nother (see `man netplan`)
[21:53] <grandy> nacc: ahh ok, so  then where would I change the config for eno1 ? a new file also?  Just wondering in case i have to do that later.
[21:54] <grandy> nacc: it must be that cloud-init is meant for ephemeral instances, in which case it seems to make sense.
[21:54] <nacc> grandy: see the manpage, you can override settings with appropriately named files
[21:54] <nacc> grandy: cloud-init initializes an instance based upon cloud-provided data (among other things)
[21:55] <grandy> nacc: ok will do, yeah ok, this is starting to make sense now, just installed ubuntu server and it's been a few years since I have configured my own server so was not really up to speed on cloud-init ... thanks much for the help
[21:56] <nacc> grandy: sure, their docs are good toohttps://cloudinit.readthedocs.io/en/latest/topics/examples.html
[21:57] <grandy> nacc: yeah i was reading over them a bit when I thought it was meant for ongoing config updates and was thinking wow this looks like a great approach to config.
[22:12] <grandy> nacc: it worked. thanks again
[22:13] <nacc> grandy: cool, np!


[05:23] <pitti> coreycb: nova 2:12.0.0-0ubuntu1 consistently fails on ppc64el (http://autopkgtest.ubuntu.com/packages/n/nova/wily/ppc64el/) now -- is that just bad luck due to the flaky test, or did something in the startup scripts change?
[05:23] <pitti> coreycb: this holds back the new nova and cinder
[05:23] <pitti> Good morning
[05:28] <pitti> jamesh: FYI, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#mediascanner2 has been stuck in -proposed for 24 days already
[05:28] <pitti> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[05:28] <pitti> it apparently makes ubuntu-desktop-next, ubuntu-pocket-desktop, ubuntu-touch, unity-scope-mediascanner2 uninstallable
[05:29] <pitti> I suppose some cleanup is needed there -- mediascanner vs. mediascanner2?
[05:57] <tjaalton> hrm, every time I change back to my user I get a dialog that prompts the password (org.fdo.accounts.change-own-user-data).. why's that?
[05:57] <tjaalton> hitting cancel doesn't work
[05:58] <tjaalton> seems to be polkit-agent-helper-1
[06:00] <pitti> me too, I now get two screenlocks -- first the classic gnome-screensaver one (new and unwanted), then the lightdm one
[06:02] <tjaalton> also, configuring software-center ran unattended-upgrades shutdown in the middle of dist-upgrade, that was a bit inconvenient :)
[06:09] <Mirv> @pilot in
[06:42] <dholbach> good morning
[06:42] <pitti> hey dholbach, wie gehts? happy wily week!
[06:42] <dholbach> gut geht's - und dir?
[06:42] <dholbach> and the same to you all :)
[06:44] <pitti> prima, danke
[06:45] <pitti> let's let the werewolf howl :)
[06:46] <jamesh> pitti: sorry, was out getting lunch.  The hold up for mediascanner2 is https://bugs.launchpad.net/ubuntu/+source/qtubuntu-media/+bug/1500859
[06:47] <pitti> uh, the fix has been stalled for 14 days?
[06:47] <pitti> well, if you don't need it for wily
[06:47] <pitti> jamesh: thanks for pointing out
[06:49] <jamesh> pitti: the short version is that qtubuntu-media has an explicit dependency on the libmediascanner-2.0-3 package despite not actually using that library anywhere.
[06:49] <jamesh> we realised that the the libmediascanner package hadn't been renamed as part of the gcc5 transition despite it having cxx11 symbols
[06:50] <jamesh> I missed this depenedency when putting together the landing.
[07:13] <jamesh> pitti: I made a followup comment on the bug.  The fix Jim mentions doesn't seem to have anything to do with it, which would be why mediascanner didn't get unblocked.
[08:53] <zzarr> Hello! I have the phablet-tools installed and still I get Unnamed
[08:53] <zzarr> upps, that's not the entire message
[08:54] <zzarr> "Are developer tools installed.. 0 ..developer tools are not installed." that's the message
[08:55] <zzarr> don't mind the "Unnamed" it was in my clipboard for some reason
[09:26] <seb128> bdmurray, do you know what's the issue with those retracing https://errors.ubuntu.com/problem/ca548de54520eed2ecd28da2c3d9413dd37f8f18 https://errors.ubuntu.com/problem/2ebfd81699a9dba286619318826c3c894a0475a4 https://errors.ubuntu.com/problem/450b4926ce084cb9a2f76872612446fb0ed62084?
[10:35] <darkxst> seb128, they are probably retracing the ppa
[10:35] <darkxst> ppa's?
[10:36] <darkxst> possibly picking up ppa's without ddebs enabled
[10:55] <zzarr> does QBluetooth work in OTA-7?
[10:55] <zzarr> or is the apparmor rule not implemented yet?
[11:02] <Mirv> @pilot out
[11:02] <Mirv> zzarr: is there a bug open about that?
[11:05] <zzarr> Mirv, not that I know about, I don't think it would be considered a bug, it's just not implemented yet (if not in OTA-7)
[11:10] <Mirv> zzarr: apparmor policy changes would need a bug, a proposal and a check by security team. it won't happen by itself if there's not a bug about it, since there are a lot of apparmor denials happening and there's no process on checking all of those and doing something about those.
[11:11] <Mirv> zzarr: I believe https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu is the correct package to file against
[11:11] <Mirv> mentioning at least how the apparmor problem is triggered and what does it look like
[11:12] <zzarr> I'll file a rapport if it's not fixed in the OTA-7 release which will be released today
[11:36] <seb128> darkxst, thanks for the suggestion, could be
[11:58] <LocutusOfBorg1> Unit193, can you please look at debian bug 802143?
[12:08] <Laibsch> wgrant, cjwatson, infinity: I'd like to revisit discussion http://irclogs.ubuntu.com/2015/03/18/%23ubuntu-devel.html#t05:33 http://irclogs.ubuntu.com/2015/03/18/%23ubuntu-devel.html#t11:42 AKA "allow bug-control team to accept or reject release pocket nominations in LP"
[12:09] <Laibsch> I'd hope it could be implemented soonish. Once the consensus is there (which I think it was half a year ago), it's more or less simply the flip of a bit in permissions.
[12:12] <Laibsch> While we are at it, would some kind soul please accept nomination for trusty for bug 1287424 and if possible even move along the SRU?
[12:12] <Laibsch> I already have other tickets for that software I'd like to get an SRU for eventually.
[12:13] <cjwatson> I've accepted the nomination
[12:13] <Laibsch> awesome. thank you, cjwatson
[12:13] <cjwatson> I think the next step in that discussion was:
 infinity: I don't think that there would be serious issues with letting bug supervisors add series tasks without going through nominations, now that task deletion exists.
[12:31] <cjwatson> Laibsch: I think it's something like http://paste.ubuntu.com/12860146/, but um.  May take a while to sort out all the details there.
[12:33] <Laibsch> Wow, actually quite involved! I thought it was simply to set a permission bit in an authentication database table and not this much code change.  Well, I hope it can land soon.
[12:34] <cjwatson> Laibsch: No, if you want to think of it this way it's more that several permission bits are currently conflated into one in an awkward way.
[12:35] <cjwatson> So you can see why it didn't happen straight away ...
[12:48] <doko> seb128, do you know the background why packagekit 0.9.x was pulled from proposed? I read https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1470655 but this doesn't have much background, and I can't find any in closed bug reports
[12:49] <seb128> doko, because it's abi/api incompatible with 0.8 and aptdaemon (and maybe others) needed to be ported and Riddell (who did the update) preferred to revert
[12:50] <seb128> doko, why?
[13:14] <doko> seb128, because I was bitten by it, with -proposed enabled. is there a plan to do the 1.0 update for 16.04?
[13:16] <seb128> doko, we are looking at doing it yes
[13:16] <seb128> doko, I made aptdaemon depends on packagekit (<< 0.9) that should have forced apt to tell you there is a problem to resolve
[13:16] <seb128> e.g remove aptdaemon or downgrade packagekit
[13:17] <seb128> also that's the kind of issues than proposed users might hit
[13:22] <jdstrand> Mirv: fyi, I wouldn't say there is no process. people need to file bugs. afaik, all the denials I'm aware of have bugs with comments on what needs to be done to fix them. some are policy adjustments, others are platform/sdk adjustments
[13:22] <jdstrand> and no one has mentioned anything about bluetooth yet
[13:22] <jdstrand> (to me at least-- in terms of policy)
[13:22] <jdstrand> so yes, please file a bug
[13:23] <jdstrand> (oh, and for bugs that need policy adjustments, I don't know of any that are open-- I definitely try to stay on top of those)
[13:23] <smoser> Odd_Bloke, did you get what you needed wrt uefi images ? just now looking at week-old backscrolls
[13:24] <smoser> fwiw: ppc64el boots with qemu-system-ppc64: https://gist.github.com/smoser/7a07d9f8929dc11b4ed9
[13:47] <Odd_Bloke> smoser: Yeah, I think I did; thanks for the pointer to that gist!
[13:49] <doko> seb128, Laney: I was looking into cross building openjdk-8/9, and seeing that the gnome stack isn't yet completely multi-arched. is this something we could look at for 16.04?
[13:50] <seb128> it would be good to have, unsure who would be interested to work on that though
[13:50] <Laney> feel free
[13:50] <Laney> via debian wherever possible
[13:52] <seb128> hum
[13:52] <seb128> who broke launchpad bugs duplicates? ;-)
[13:52]  * seb128 looks at wgrant and cjwatson
[13:52] <seb128> bug_id: got 'unicode', expected int: u'1507332'
[13:53] <seb128> when trying to mark a bug duplicate of another one
[13:53] <cjwatson> seb128: bug with an oops id please, I'll track it down
[13:53] <seb128> cjwatson, I don't get an oops
[13:54] <cjwatson> seb128: what exactly are you doing?
[13:54] <seb128> just that message in red
[13:54] <seb128> opening https://bugs.launchpad.net/ubuntu/+source/gnome-system-log/+bug/1500806
[13:54] <seb128> click on "mark as duplicate" on the right
[13:54] <seb128> I get the popup dialog to enter a bug
[13:54] <cjwatson> oh
[13:54] <seb128> I write 1500806
[13:54] <seb128> and get the error I just copied in red
[13:55] <cjwatson> it's a regression from the fix for bug 581748
[13:55] <cjwatson> you can work around it by middle-clicking the "mark as duplicate" link so that you get the HTML form rather than the AJAX one
[13:55] <cjwatson> I'll see about an urgent fic
[13:55] <cjwatson> *fix
[13:57] <seb128> cjwatson, https://bugs.launchpad.net/launchpad/+bug/1507604
[13:57] <seb128> cjwatson, thanks
[13:57] <cjwatson> thanks
[14:16] <seb128> cyphermox, is bug #1507330 known?
[14:17] <cyphermox> seb128: now it is.
[14:17] <seb128> cyphermox, that's why I was pointing it ;-)
[14:18] <seb128> cyphermox, I fixed a similar bug in apturl on friday, had to move the height_request property from the textview to the srolledwindows
[14:18] <seb128> unsure what changed, I guess it's new GTK...
[14:18] <seb128> that one might be similar
[14:19] <cyphermox> if so, yuck
[14:21] <doko> Laney, mediascanner2 is still blocked on qtubuntu-media, LP: #1500859
[14:21] <Laney> see #ubuntu-touch
[14:22] <seb128> cyphermox, totally non tested/random try, but maybe http://paste.ubuntu.com/12861228/
[14:22] <seb128> cyphermox, if you know how to easy spawn the ubiquity UI to test
[14:23] <cyphermox> bleh
[14:23] <cyphermox> yeah, I know how
[14:23] <cyphermox> worth a try I guess
[14:23] <seb128> is there an easy way?
[14:23] <seb128> out of download an iso, boot it in live mode and test from there
[14:23] <cyphermox> yeah, I run an iso and change what I need
[14:23] <cyphermox> ah
[14:23] <seb128> lol
[14:23] <cyphermox> I usually always have the isos ready, downloaded
[14:23] <seb128> I'm downloading one
[14:24] <seb128> I can test the patch if you are busy on other things
[14:24] <seb128> just needs some 20 minutes or so
[14:25] <cyphermox> it's fine I already was preparing an upload, and already had a vm with ubiquity spun up on it
[14:25] <seb128> great
[14:27] <cyphermox> almost.
[14:27] <cyphermox> but not quite.
[14:31] <cyphermox> oh wait, I did the change wrong
[14:32] <cyphermox> yay
[14:32] <seb128> ?
[14:33] <cjwatson> seb128: I've asked for a rollback of the last LP deployment
[14:33] <seb128> cjwatson, thanks
[14:34] <cjwatson> Having trouble reproducing this in the test suite, but I can absolutely see it on qastaging :-/
[14:35] <cjwatson> And setting a breakpoint on the relevant bit of JS hangs firefox
[14:35] <seb128> cjwatson, is rolling back cheap? because the bug is easy to workaround so I guess if it's fixing today having it around for a few hours is not the end of the world
[14:35] <cjwatson> Awesome
[14:35] <cjwatson> seb128: Cheap enough and I'm not sure how long it will take me to fix
[14:35] <seb128> k
[14:36] <cjwatson> Since my first three attempts to reproduce in tests haven't gone anywhere yet
[15:36] <seb128> dpm, pitti, wgrant, do you know why https://translations.launchpad.net/ubuntu/wily/+source/evolution/+imports is empty (out of the manual upload I just did)?
[15:36] <seb128> the .po should be imported no?
[15:37] <seb128> https://launchpadlibrarian.net/221324437/buildlog_ubuntu-wily-amd64.evolution_3.16.5-1ubuntu2_BUILDING.txt.gz has a translations tarball
[15:52] <cjwatson> seb128: https://code.launchpad.net/~cjwatson/launchpad/fix-bug-picker-search/+merge/274910 and singing the I-hate-JavaScript song.  Hopefully we can roll this out again tomorrow
[15:53] <seb128> cjwatson, nice, thanks for fixing it ;-)
[16:13] <kirkland> rbanffy: nice :-)
[16:13] <rbanffy> kirkland, ?
 In any case, byobu users who use mu font (all three of them, me included) will be happy to know I added a ⟫ in late May.
[16:15] <rbanffy> kirkland, :-)
[16:15] <apw> rsalveti, yo, just looking at your rtl8812au upload, there are a number of files in here without clear copyright information though your copyright claims they are GPLv2, do you have some suplementary information to that effect ?
[16:16] <hallyn_> xnox: did you see any problems in https://mentors.debian.net/packages/my ?
[16:16] <hallyn_> uh, https://mentors.debian.net/package/netcf
[16:16] <rsalveti> apw: I saw a few that were indeed missing, but minor headers and iirc (last time I check), those files were also in the upstream kernel (under another driver)
[16:17] <xnox> hallyn_: i did not but have run out of time to upload it.
[16:18] <xnox> hallyn_: i've set a reminder to do it tonight, when i am back home.
[16:18] <xnox> sorry about the delay.
[16:20] <rsalveti> apw: I can cross check again, but most of the ones that were missing are not even required by the build
[16:20] <rsalveti> so they can be removed
[16:20] <hallyn_> xnox: gotcha, thanks
[16:20] <rsalveti> just didn't remove because the tarball is directly from the vendor
[16:21] <apw> rsalveti, i'll see if i can confirm they are in the upstream kernel
[16:21] <rsalveti> the hal ones under OUTSRC-BTCoexist are probably not, and not used during the build
[16:21] <rsalveti> so I can upload without them
[16:22] <rsalveti> let me check again which files are actually used
[16:24] <apw> rsalveti, that is the sketchiest directory for use
[16:24] <apw> suew
[16:24] <apw> sure
[16:25] <rsalveti> apw: in this case (since it comes from the upstream tarball), should I upload a new orig tarball without them or just make a patch to remove them?
[16:25] <apw> rsalveti, we don't want them in the archive, so repacking +dfsg stylee seems appropriate
[16:26] <rsalveti> alright
[16:26] <bdmurray> seb128: I'll have a look at those crashs
[16:26] <seb128> bdmurray, thanks
[16:47] <gdfuego> I just filed a fun bug in Precise
[16:47] <gdfuego> https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1507681
[17:07] <bdmurray> seb128: One of the retraces failed in the following way - http://pastebin.ubuntu.com/12863467/. So apport did not return a crash signature.
[17:30] <bdmurray> seb128: that's true for both the libunity crash and the trust-store crash. the missing debug symbol messages are incidental.
[17:32] <seb128> bdmurray, the one you pastebined has an useful stacktrace though
[17:32] <seb128> just missing the first symbol
[17:39] <bdmurray> seb128: I think the any missing symbol is cause for apport to return None for a crash signature.
[17:40] <seb128> bdmurray, oh, ok, do you know if that's by design or a bug?
[17:40] <kdub> my thinkpad (x201 tablet) is having a tough time booting with the daily live usb stick made with usb-creator-gtk... could this be a uefi problem maybe?
[17:42] <bdmurray> seb128: I think its by design - https://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/report.py#L1233 "If StacktraceTop has unknown functions or the report lacks any of those fields, return None.
[17:43] <rsalveti> apw: should be all good now, let me know if you need any other info
[17:43] <seb128> bdmurray, I think the intend was to avoid having one function being a signature
[17:43] <seb128> but maybe pitti can confirm
[17:44] <seb128> it feels like in that case we could do better, because ?? followed by 4 detailed function is useful
[18:09] <bdmurray> seb128: I reported bug 1507711 about this.
[18:09] <seb128> bdmurray, thanks
[18:22] <infinity> seb128: Were you handling the component-mismatches promotions from your seeding, or shall I?  (I don't want to double-override).
[18:29] <seb128> infinity, I did it
[18:30] <infinity> seb128: Kay.  I'll wait for the publisher to catch up and look at the result.
[18:45] <slangasek> hrm.  I just got email from google saying that a recently used device logged in insecurely to my google account, and it points to my IP address. Is Online Accounts not up to speed with current login protocols?
[18:47] <ogra_> slangasek, you usually get that if you connect a device for the first time ...
[18:47] <ogra_> well, i do
[18:56]  * xnox gets that every time i login from an annonymous window. or e.g. logging out with one google account, to relogin with a different one.
[18:57] <slangasek> ogra_: it's not a new device, it's my existing laptop
[18:58] <slangasek> and I've never had his error before
[18:58] <ogra_> token expired ?
[20:42] <slangasek> pitti: http://autopkgtest.ubuntu.com/packages/p/python3.4/trusty/ results regressed between .1 and .3, with no relevant code changes.  Same tests pass in package build.  Could this be related to the recent lxc profile questions?
[21:08] <Unit193> Heh, /var/lib/dpkg/info/keyboard-configuration.postinst: 1: /var/lib/dpkg/info/keyboard-configuration.postinst: udpkg: not found


[02:23] -queuebot:#ubuntu-quality- Builds: Xubuntu Desktop amd64 [Jammy Beta] has been marked as ready
 @Leokolb For future reference, inability to install using btrfs would not be a "critical" bug. Those are reserved for release-blocking bugs. Calamares can still install on other, better-supported file formats, so btrfs isn't a blocker.
 I would disagree, I don't necessarily think that we don't support it but I do think it doesn't need to be marked as critical
 It's still something I would think we should fix before the release
 Still not a release blocker.
 You have every right to make the choice for your flavor but for us I think we're gonna stick with it as a release blocker
 Additionally, manual partitioning deviates from the prescribed testcase in which the issue was reported.
 @tsimonq2 I'm talking about test results on Ubuntu Studio's test cases.
 Sounds good. In that case, your call (re @Eickmeyer: @tsimonq2 I'm talking about test results on Ubuntu Studio's test cases.)
[02:45] -queuebot:#ubuntu-quality- Builds: Ubuntu Studio DVD amd64 [Jammy Beta] has been marked as ready
 I only reprorted a bug i discovered while testing - i made no reference to it being a release stopper - ?? (re @Eickmeyer: @Leokolb For future reference, inability to install using btrfs would not be a "critical" bug. Those are reserved for release-blocking bugs. Calamares can still install on other, better-supported file formats, so btrfs isn't a blocker.)
 You listed it as critical. (re @Leokolb: I only reprorted a bug i discovered while testing - i made no reference to it being a release stopper - ??)
 It failed the test ..not being able to reboot is a failure - is it not? (re @Eickmeyer: You listed it as critical.)
 Not if you deviate from the test case. The test case did not call for manual partitioning. (re @Leokolb: It failed the test ..not being able to reboot is a failure - is it not?)
 Moreover, with Ubuntu Studio, we don't care about btrfs.
 Ok I am very sorry - the but for Lubuntu it is still a failure - I will be more careful in the future
 For Lubuntu, that's fine. Just make sure that you're keeping the testcases divided. :)
 you could have sent me a PM about this...unhappy for the critism - i work hard at what I do (re @Eickmeyer: For Lubuntu, that's fine. Just make sure that you're keeping the testcases divided. :))
 I understand, and for that I apologize. When it comes to Ubuntu Studio stuff, just ping me before marking stuff critical if there's any question. (re @Leokolb: you could have sent me a PM about this...unhappy for the critism - i work hard at what I do)
 The test case does not mention what partition type should be selected - would be nice to specify ext4 / xfs etc (re @Eickmeyer: I understand, and for that I apologize. When it comes to Ubuntu Studio stuff, just ping me before marking stuff critical if there's any question.)
 The test case says simply to click "Erase Disk and Install" nothing about doing any manual partitioning. (re @Leokolb: The test case does not mention what partition type should be selected - would be nice to specify ext4 / xfs etc)
 ok - my mistake - was only trying to help - not many others are testing UbuntuStudio on the qa site -
 You're welcome to continue as-is with Lubuntu as well (re @Leokolb: ok - my mistake - was only trying to help - not many others are testing UbuntuStudio on the qa site -)
 There's a reason (iirc) we have extended testcases :)
 tks @tsimonq2 I just keep prodding on.. (re @tsimonq2: You're welcome to continue as-is with Lubuntu as well)
 @Leokolb FYI, If I seem overly short or what-not, I'm terribly sorry. I just apologized to the entire Lubuntu Development channel.
 No problem. (re @Eickmeyer: @Leokolb FYI, If I seem overly short or what-not, I'm terribly sorry. I just apologized to the entire Lubuntu Development channel.)
[07:50] -queuebot:#ubuntu-quality- Builds: Ubuntu Budgie Desktop amd64 [Jammy Beta] has been marked as ready
[08:59] -queuebot:#ubuntu-quality- Builds: Ubuntu Desktop (Canary) amd64 [Jammy Beta] (20220329.1) has been added
[08:59] -queuebot:#ubuntu-quality- Builds: Ubuntu MATE Desktop amd64 [Jammy Beta] has been marked as ready
[09:22] -queuebot:#ubuntu-quality- Builds: Kubuntu Desktop amd64 [Jammy Beta] has been marked as ready
[10:03] -queuebot:#ubuntu-quality- Builds: Ubuntu Desktop (Canary) amd64 [Jammy Beta] has been updated (20220331)
[12:46] -queuebot:#ubuntu-quality- Builds: Ubuntu Kylin Desktop amd64 [Jammy Beta] has been marked as ready
[14:32] -queuebot:#ubuntu-quality- Builds: Ubuntu Server arm64+raspi [Jammy Beta] has been marked as ready
[14:32] -queuebot:#ubuntu-quality- Builds: Ubuntu Server riscv64+unmatched [Jammy Beta] has been marked as ready
[14:32] -queuebot:#ubuntu-quality- Builds: Ubuntu Server armhf+raspi [Jammy Beta] has been marked as ready
[14:39] -queuebot:#ubuntu-quality- Builds: Lubuntu Desktop amd64 [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Desktop amd64 [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity amd64 [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity ppc64el [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity s390x [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Desktop arm64+raspi [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity riscv64 [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Server Subiquity arm64 [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Base amd64 [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Base armhf [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Base riscv64 [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Base arm64 [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Base s390x [Jammy Beta] has been marked as ready
[14:40] -queuebot:#ubuntu-quality- Builds: Ubuntu Base ppc64el [Jammy Beta] has been marked as ready
 2257