[01:28] <Waffl3x> someone teach me how to kubuntu
[01:28] <Waffl3x> :D
[01:29] <Waffl3x> but for real, its really overwhelming, so many new things
[01:29] <Waffl3x> activities, whatever those are
[01:32] <pinksoviet> Pretty new myself. It's interesting enough :>
[01:33] <Waffl3x> I agree
[01:33] <Waffl3x> its very interesting
[01:33] <Waffl3x> I just wish I could figgure it out
[01:34] <Waffl3x> I feel like it comes with too much
[01:34] <Waffl3x> there are certain things you should have to download yourself, like all the damn widjets it comes with
[01:34] <malc_calc> well, you know about virtual desktops already? Having more than 1 Desktop?
[01:34] <Waffl3x> some of them only specific people would use
[01:34] <Waffl3x> like the binary clock
[01:34] <Waffl3x> malc_calc: negative
[01:35] <pinksoviet> This is my 2nd week testing it out, and the recent Netflix support greatly helped, haha.
[01:36] <Waffl3x> malc_calc: explain virtual desktops please :D
[01:37] <pinksoviet> Press Ctrl+F2
[01:37] <malc_calc> waffl, go to system settings, find 'workspace behaviour'. play with the options there, try help menues, google the rest
[01:37] <pinksoviet> Ctrl+F1 to go back to your first virtual desktop
[01:37] <malc_calc> cannot teach you in 5 min, but that should give you an idea, and you can always set defaults again
[01:40] <Waffl3x> malc_calc: I found it in options earlier, couldnt figgure it out that well
[01:41] <Waffl3x> best I did was set up an action to grid them
[01:41] <Waffl3x> which was cool
[01:41] <Waffl3x> multi taskbars are weird too
[01:41] <malc_calc> the idea is having more than one desktop where you can put your windows, and it's old, old, old. activities is more: an activity is an entirely new SET of desktops (if you use virt. desktops), and other than virtual desktops, an activity can have very different settings from another, i.e. wallpaper, different set of widgets. It's not as big a change as logging in as a different user, but more of a change than changing from one
[01:41] <malc_calc> virtual desktop to another
[01:42] <Waffl3x> so
[01:42] <malc_calc> lookup the terms in wikipedia best
[01:42] <Waffl3x> activities is extended virtual desktops
[01:42] <Waffl3x> no wait
[01:42] <Waffl3x> thats not right is it
[01:43] <Waffl3x> you know what I want to do now
[01:43] <malc_calc> whatever word we put to it, YOU'll have to figure how it works!
[01:43] <Waffl3x> I just had the greatest idea
[01:44] <malc_calc> idea
[01:44] <Waffl3x> im trying to figgure out how complicated it would have to be
[01:44] <Waffl3x> but basically a little device to copy your clipboard to another computer
[01:45] <Waffl3x> Im thinking the best way to do it
[01:45] <Waffl3x> actually that might be over complicated
[01:46] <Waffl3x> do you think you could do it with just a usb key
[01:46] <Waffl3x> obviously this isnt as great as I made it sound :D
[01:46] <malc_calc> a lot of apps to use a mobile device as remote do that. kde connect.
[01:46] <Waffl3x> :O
[01:46] <Waffl3x> how
[01:46] <Waffl3x> so I can
[01:47] <Waffl3x> do they both need to be linux
[01:47] <Waffl3x> yes they do
[01:47] <Waffl3x> dont they
[01:47] <malc_calc> android is half linux, but they don't necessarily need to be the same
[01:47] <Waffl3x> :O
[01:47] <Waffl3x> yes
[01:47] <Waffl3x> this is good
[01:48] <Waffl3x> I want to set this up with my phone
[01:48] <Waffl3x> in fact
[01:48] <Waffl3x> I want to link all my devices in some way
[01:48] <Waffl3x> who knew there was such a big world of computing I was missing
[01:50] <Waffl3x> how do you eneable desktop cube?
[01:51] <malc_calc> u want to check virt. desktops? 1st thing  u do: system settings->workspace behaviour->virtual desktops->desktops->layout->number of desktops-> 4 (or any number you want. don't forget to 'Apply' changes. if u want, go to switching tab and pick desktop effects. apply changes, when u're done, try pulling a window OVER the right or the left edge of the screen. if it works, you'll understand virt.desktops
[01:53] <Waffl3x> I got that
[01:53] <Waffl3x> but
[01:53] <malc_calc> cube: where i just said in switching, but in different context syst.settings>desktop effects
[01:53] <Waffl3x> why is cube greyed out
[01:53] <malc_calc> ooop..
[01:54] <malc_calc> you're sure you already have more than one virt.desktop? forgotten to apply changes?
[01:54] <Waffl3x> yes I do
[01:54] <malc_calc> guessing
[01:54] <Waffl3x> I tryed 4
[01:54] <Waffl3x> and I tryed 6
[01:55] <malc_calc> still there the 4 when you go to same settings page again?
[01:56] <malc_calc> can you drag windows from one desktop to another?
[01:56] <Waffl3x> yes
[01:56] <Waffl3x> I have it set to switch without windows too though
[01:56] <Waffl3x> and that works
[01:57] <malc_calc> so have i, but cube effect greyed out.. o.O ?? have old computer, old graphics card, no compositing effects?
[01:57] <Waffl3x> negative
[01:57] <Waffl3x> its like 2 or 3 years old
[01:58] <Waffl3x> gtx 560 or 550
[01:58] <Waffl3x> amd fx 8350
[01:58] <malc_calc> guessing, or maybe someoner else has better clue, 243 users here..
[02:00] <malc_calc> cannot reproduce your problem, i get no animation, slide, fade, and cube as options for desktop switching effects, none greyed out
[02:00] <Waffl3x> its not desktop switching effect
[02:01] <Waffl3x> I get those
[02:01] <Waffl3x> its the screen edges option
[02:01] <Waffl3x> btw
[02:02] <Waffl3x> is there any way to get the task manager to only show windows that are on the current desktop?
[02:02] <Waffl3x> nevermind :D
[02:02] <Waffl3x> found it
[02:02] <malc_calc> 'cube effect greyed out' you said, that's not screen edges.
[02:02] <Waffl3x> im a little confused, whats the difference between current screen and current desktop...
[02:02] <Waffl3x> oh
[02:02] <Waffl3x> I see
[02:03] <malc_calc> don't think I'm any more wise than you, if I can help, it's luck
[02:04] <Waffl3x> can I get other desktops to have different icons and widgets?
[02:04] <malc_calc> never trtied, but the option is there in the settings
[02:05] <Waffl3x> sweet
[02:06] <malc_calc> the icons on the desktop seems to be funny in KDE anyway, need a folder widget to see some
[02:06] <malc_calc> just put file in home/myname/Desktop doesn't bring it to the desktop
[02:08] <malc_calc> my favorite widget is eyes so far. if i 'get more widgets', half of them tend to crash in one or another way. want to try if KDE is better implemented in OpenSuse
[02:10] <Waffl3x> whats eyes?
[02:10] <Waffl3x> also
[02:10] <malc_calc> kubuntu has official support, but few developpers and much work. on OpenSuse KDE is default
[02:11] <malc_calc> eyes is a widget, a port of an age-old joke forX
[02:11] <Waffl3x> wheres the hotkey setting for desktop grid?
[02:12] <malc_calc> forgot
[02:12] <Waffl3x> :/
[02:12] <malc_calc> there's an extra desktop switcher widget, too
[02:12] <Waffl3x> also you just mentioned it, but why is the desktop so weird in kubuntu
[02:12] <Waffl3x> I can drag stuff on to it to make shortcuts
[02:12] <Waffl3x> but I cant move them after
[02:13] <Waffl3x> and it wont show files in the desktop folder
[02:13] <malc_calc> well, you go to virt.desktop settings againg, all the possible hotkeys are there for you to study, configure or make your own
[02:13] <Waffl3x> desktop grid isnt there
[02:14] <malc_calc> moving things you have to unlock widgets, i think right click on empty space gives the opt
[02:15] <Waffl3x> okay weird
[02:15] <Waffl3x> my icon disapeared
[02:15] <Waffl3x> just now
[02:16] <malc_calc> ghost in the machine :9
[02:16] <malc_calc> :)
[02:16] <Waffl3x> ikr
[02:16] <Waffl3x> so everything on the  desktop counts as a widget?
[02:16] <Waffl3x> also
[02:16] <Waffl3x> widgets arnt locked and I still cant move the icon
[02:17] <malc_calc> hang on, I leave you to play for some time, will look at other things now. if you scream for help every 10 min, you should get attention ....
[02:18] <Waffl3x> im playing at the same time though
[02:18] <Waffl3x> D:
[02:18] <malc_calc> i believe everything counts as widget, and if you approach a unlocked widget with the mouse, a panel pops out with move, resize, remove etc intuitive options
[02:18] <Waffl3x> OH
[02:18] <Waffl3x> THATS HOW YOU MOVE IT
[02:18] <Waffl3x> ty
[02:19] <Waffl3x> are you able to explain why files in desktop dont show up on the desktop?
[02:19] <malc_calc> figure it. there should be a KDE handbook, and CTRL-f brings you a facility to search for a word or term practically everywhere  if text's involved
[02:20] <malc_calc> no, cannot explain. their new concept of what a desktop is, my guess
[02:20] <malc_calc> but bye , maybe back later
[02:20] <Waffl3x> ok
[02:20] <Waffl3x> I wonder why theres a desktop folder then
[02:20] <Waffl3x> :/
[02:21] <Waffl3x> thanks for the help
[04:25] <reuben_> Hello all, Have any of you had problems with mono applications falling back to the fallback mouse cursor?
[05:24] <reuben_> Hello all, Have any of you had problems with mono applications falling back to the fallback mouse cursor? If so what was the solution?
[06:15] <soee> good morning
[06:45] <pinksoviet> mornin
[07:25] <lordievader> Good morning.
[08:27] <Yossarianuk> hi - just seen 14.04 has another libssl update -> 1.0.1f-1ubuntu2.7 is this just related to the poodle attack or are there other issues fixed also ?
[08:34] <valorie> !ssl
[08:35] <tsimpson> Yossarianuk: the fixed issues should be listed in the changelog at the bottom of this page: https://launchpad.net/ubuntu/trusty/+source/openssl/1.0.1f-1ubuntu2.7
[08:35] <valorie> hmmm, I was sure we had a link to the bulletins about it
[08:35] <Yossarianuk> tsimpson: cheers
[08:36] <Yossarianuk> (I resolved the poodle issue yesterday on all our servers.... Just checking if I now have to qa the new updates...)
[08:38] <tsimpson> you can always use "apt-get changelog <package>" to see what's new in a package, if you need even more details launchpad can show you the changes or you could download and inspect the source ;)
[08:42] <__Shimon__> guys! how to run KUbuntu KDE Plasma 5?
[08:43] <__Shimon__> I've downloaded, but was unable to run it with VirtualBox and boot from a USB stick.
[08:44] <__Shimon__> I understand, that this is beta, but, it should provide something reliable, for example, booting.  =(
[08:49] <lordievader> valorie: Lots of factiods have been removed from ubottu lately.
[08:59] <spinach> morning
[08:59] <lordievader> o/
[08:59] <spinach> \o
[09:01] <spinach> having one hell of a time getting this old epson scanner running. there's a set of binaries to install through the seiko epson website, but only two of the three install and i'm left with software that doesn't recognize the scanner at all.
[09:01] <spinach> (epson perfection 4490/gt-x750)
[09:03] <spinach> the last binary, when i go to install it, the option to do so is just grayed out in qapt.
[09:48] <spinach> after adding my scanner's id info to epkowa.conf and epson.conf and epson2.conf and then adding saned to the scanner group the scanner now occasionally whirs but still does not open
[10:47] <azaki> This may be a stupid question, but if I install Kubuntu with Plasma 5 on a machine now, will it properly upgrade without issues when Plasma 5 becomes the default/stable/etc? or will I have to reinstall?
[10:47] <azaki> I'd like to use Plasma 5 soon without having to wait for it, I noticed that recently Kubuntu started offering it as a "preview", which is why I ask.
[11:36] <benvantende> hey people, i just updated (latest 14.10) to plasma 5.1, which is all awesome. my desktop becomes unresponsive however at a certain point. mouse moves but i cannot do a thing. what could be a likely cause? windows decorations?
[11:57] <Walex> benvantende: it could be very many things indeed and it happens with KDE 4 too.
[11:58] <Walex> benvantende: in one case it was a JavaScript script inside Firefox running at 100% CPU, so there
[11:58] <benvantende> thanks for responding ...
[11:59] <benvantende> i run fine for 30 minutes now. that is cool ;)
[11:59] <Walex> benvantende: if you can SSH in you can look at 'top' and 'iostat -dkxz 1' to see what's going oin
[11:59] <benvantende> walwx: it does not seem due to 100% cpu somewhere
[12:00] <benvantende> i have top running mostly, but when the desktop freezes there is not much you can do is there?
[12:00] <Walex> it could be graphics CPU driver too, e.g. the intel one often gets into trouble with pipeline stalls
[12:01] <Walex> benvantende: "when the desktop freezes there is not much you can do" that's why I mentioned having an SSH session in
[12:01] <benvantende> right
[12:53] <MoonUnit`> still no 14.10 RC then
[12:56] <BluesKaj> Hey all
[15:43] <pkulas> Hey, where can I get logs from plasma5? Many times plasma5 freeze for few seconds.
[15:50] <skinux> What is the most recommended command to perform packages upgrade?
[15:53] <Snowhog> skinux: "I" use sudo apt-get update first, followed by sudo apt-get dist-upgrade
[15:53] <skinux> Okay.
[16:28] <pkulas> dolphin crash so many times :(
[16:33] <andy123> dolphin crash :D http://www.youtube.com/watch?v=6lyDspzxSrw
[16:35] <pkulas> :D
[16:38] <libreSSL> "D
[16:38] <libreSSL> *:D
[17:38] <rivo> hi
[17:44] <geoextra> Hey, will Kubuntu 14.10 shipped with Plasma 5 by default?
[17:45] <BluesKaj> geoextra, no, not yet, it's not ready for a full launch. There are still a lot of bugs to work out. on kf5 and plsama 5 desktop
[17:47] <BluesKaj> I used it for a while but got frustrated so I reinstalled plasma 4
[17:47] <geoextra> Okay, thank you :)
[17:48] <BluesKaj> personally I didn't care for the "looks" available
[17:49] <marc___> Hello
[17:50] <marc___> Is it possible to dump an image of Kubuntu into a SSHD so I can boot from that?
[18:18] <marc___> Sorry mi internet connection went down. I was asking if it is possible to dump a Kubuntu image to a SSHD so I can boot from it later on?
[18:19] <lordievader> marc___: If you mean SSD.. perhaps but it won't be pretty or good for performance. (I assume here that you mean with 'dump' extract.)
[18:20] <marc___> I mean solid state hard disk. Why it won't be good for performace? Kubuntu doesn't fully support this kind of disks?
[18:20] <lordievader> marc___: The live-cd uses a squashfs...
[18:21] <marc___> I want to extract the image but in a way that the disk is a boot disk and I am not sure how the do it so it boots later
[18:21] <marc___> that is the problem... I can't use a livecd
[18:21] <lordievader> marc___: Why not?
[18:22] <marc___> It is quite complex: I have 2 computers, one of them is this one, where I am running XP as I need to use a soft that only works with Windowz
[18:22] <marc___> I want to install Kubuntu in the 2nd PC
[18:23] <lordievader> I fail to see the problem.
[18:23] <marc___> but both are notebooks and the 2nd PC doesn't have anywhere to put the SSD but where the CD unit goes (using an adaptor)
[18:23] <lordievader> marc___: Use a live-usb.
[18:23] <marc___> that 2nd PC also cannot boot from USB or external DVD from BIOS
[18:23] <genii> The image is a hybrid image, you can just dd it to something like a USB stick or even a hard drive, and it still works.
[18:24] <marc___> so my idea is to download the image with this 1st PC (running XP), while I have the SSD as secondary, extract it to that disk
[18:24] <marc___> but this is the part I don't know: How can I extract it to make sure that when I remove this SSD and I put it as primary on the 2nd PC it will boot?
[18:25] <lordievader> marc___: Why not use the XP machine to install it to that disk and after swap the disk back to the original machine.
[18:25] <marc___> the XP machine has a primary disk which I don't want to remove as the connector was failing, but I can still put the SSD as secondary disk
[18:27] <marc___> What soft do you recommend me to use to extract the image while in XP?
[18:28] <lordievader> marc___: As I said, I'd put the SSD in the XP machine, boot up using a live-usb and installing Kubuntu on the SSD. And afterwards putting it back in the original machine.
[18:28] <marc___> I can't do that as this PC doesn't support USB boot
[18:28] <lordievader> Live-dvd then ;)
[18:29] <marc___> I can't as the DVD unit goes where the SSD is located
[18:29] <marc___> I still have external DVD but I cannot boot from that
[18:29] <genii> You should just get dd for windows off of http://www.chrysocome.net/downloads/dd-0.6beta3.zip and then dd the image file to the SSD
[18:31] <marc___> I am reading about DD it looks very complex
[18:31] <genii> It's not.
[18:32] <lordievader> It can be a dangerous tool though, if poorly understood.
[18:32] <genii> In linux the command would be like: sudo dd if=imagefile.img of=/dev/sdX      ...for instance where X is drive letter
[18:34] <genii> marc___: In Windows the command would be similar to:   dd if-c:\temp\iso-filename.iso od=d:    ( if SSD is drive D: )
[18:36] <marc___> and that will write to the SSD to then I can boot from it? Is not necessary to format the SSD first? (It is currently NTFS)
[18:41] <marc___> genii: did you see my question at 34 past?
[18:41] <genii> marc___: Not necessary to format it.
[18:42] <genii> The dd command will directly overwrite whatevers on it
[18:43] <marc___> ok I will try, many thanks, I'll let you know, however it may take time as I need to do a backup of the SSD and under XP it is ultra-slow
[19:50] <David1965> has anyone noticed that BASH has a problem called shell-shock and needs to be patched and made available pronto otherwise the hackers will have a field day taking down the whole Internet
[19:51] <lordievader> David1965: That has been patched for months ;)
[19:52] <lordievader> David1965: Just run 'sudo apt-get update&& sudo apt-get dist-upgrade'
[19:52] <David1965> no I tried the test to check for this problem and it says that the bash installed on my machine is vonerable
[19:52] <EvilRoey> lordievader:  heh
[19:52] <EvilRoey> hey all
[19:52] <lordievader> David1965: What version of Kubuntu are you running?
[19:52] <lordievader> Hey EvilRoey.
[19:53] <David1965> not running kbubunu but Linux Mint 17 64bit Qiana
[19:53] <lordievader> David1965: Linux Mint is not supported here, please see #linuxmint for that.
[21:43] <elw0od> hi all
[22:09] <detached09> Anyone around that can help me out right quick?
[22:10] <elw0od> detached09: assk
[22:10] <detached09> I have my Windows partition on /dev/sda5. I need to mount C:\Users\me\Downloads to /home/downloads. I had it set up previously, but I don't remember what I did.
[22:11] <detached09> and when I reinstalled, I didn't think to backup /etc/fstab first.
[22:12] <detached09> I remember it had something to do with using the UUID, which I have, but I don't remember the exact line I need to enter and Google isn't helping like it did last time.
[22:16] <elw0od> detached09: use gparted to see which one has a windows filesystem
[22:16] <elw0od> without changing anything
[22:16] <detached09> It's /dev/sda5.
[22:17] <detached09> The whole drive automounts under /media/me/UUID/ but previously I had Downloads mapped to /home/downloads where all my programs download stuff.
[22:21] <elw0od> detached09: so you need to re-set the mounting point?
[22:22] <detached09> yeah
[22:22] <elw0od> blkid /dev/sda5
[22:23] <elw0od> or simply blkid to see them all
[22:23] <detached09>  /dev/sda5: UUID="1AECB266ECB23BB7" TYPE="ntfs"
[22:24] <elw0od> so, in fstab search for this uuid and set your desired mounting point
[22:25] <detached09> I don't want to mount the whole drive there though. Which is where I'm running into the problem.
[22:27] <detached09> I'm just trying to mount the Windows downloads folder in /home/downloads. The rest of it can stay in /media/me/UUID/


[02:48] <UForgotten> The following packages have unmet dependencies: mythweb : Depends: mythtv-common (>= 2:0.25.0+fixes.20120510.f22e556-0ubuntu0mythbuntu4) but 2:0.25.0+fixes.20120509.7fbcfb4-0ubuntu0mythbuntu4 is to be installed
[02:48] <UForgotten> just an fyi - I can't install mythweb after updating from the mythbuntu repo.
[02:49] <UForgotten> those are some gnarly package names :(
[02:49] <tgm4883> mythtv-common is a gnarly package name?
[02:50] <UForgotten> ok, version string :P
[02:50] <tgm4883> I'll agree, but it's all important info
[02:52] <UForgotten> seems like it would be easy to create a dependency hell with the +fixes.yaddayadda if say more than one release per day happened.
[02:52] <Zinn> UForgotten: Please watch your language.
[02:53] <patdk-lap> that is what the 7fbcfb4 is for
[02:53] <UForgotten> what if you hash 7f first then a0 later?
[02:53] <UForgotten> pwned.
[02:54] <patdk-lap> is it a hash?
[02:54] <tgm4883> I'm not entirely sure why you would get into dependency hell
[02:54] <Zinn> tgm4883: Please watch your language.
[02:54] <UForgotten> for teh lulz.
[02:55] <UForgotten> just dont release more than once per day and you're fine :)
[02:55] <tgm4883> well the 7fbcfb4 is the git revision
[02:55] <UForgotten> I figured as much
[02:55] <tgm4883> which should be ever increasing
[02:55] <UForgotten> no, its a sha hash - the number can be anything.
[02:56] <tgm4883> ok
[02:56] <UForgotten> but thats not the point.  the point is, somebody broke dependencies on mythweb, so who can I politely ask to fix it :)
[02:56]  * tgm4883 doesn't do much with git, more with bzr
[02:57] <tgm4883> UForgotten, apt-get update?
[02:57] <UForgotten> tgm4883: that's what I did to get that error...
[02:57] <tgm4883> apt-get -f install?
[02:57]  * patdk-lap doubts they are broken
[02:57] <patdk-lap> I know I have this issue too
[02:57] <patdk-lap> I think you have to uninstall mythvideo
[02:58] <patdk-lap> update, then reinstall it
[02:58] <UForgotten> wierd
[02:58] <tgm4883> patdk-lap, mythvideo?
[02:58] <UForgotten> isnt mythvideo part of myth core now?
[02:58] <tgm4883> mythvideo doesn't exist anymore
[02:58] <tgm4883> UForgotten, yes
[02:58] <patdk-lap> yep
[02:58] <patdk-lap> oh, mythweb I mean
[02:58] <UForgotten> MYTHWEB is not YET installed
[02:59] <tgm4883> UForgotten, have you tried the -f install?
[02:59] <UForgotten> have not tried that, but should not have to force it if dependencies were correct
[02:59] <tgm4883> that doesn't mean force
[02:59] <patdk-lap> oh, you got a strange repo sync :)
[02:59] <patdk-lap> a newer mythweb than mythtv
[03:00] <patdk-lap> some mirror isn't syncing correctly, it sounds like
[03:00] <tgm4883> patdk-lap, doubtful
[03:00] <UForgotten> no, happens all the time
[03:00] <UForgotten> crappy cdn's
[03:00] <patdk-lap> heh?
[03:00] <tgm4883> strange
[03:01] <tgm4883> I've never had that happen
[03:01] <patdk-lap> mythweb depends on 20120510? but only 20120509 available
[03:01] <patdk-lap> sounds like a packaging mirror issue
[03:01] <UForgotten> someone rolled a mythweb fix and somehow its out of sync with myth-common
[03:03] <tgm4883> actually no, I don't think that is possible
[03:03] <UForgotten> anything's possible given chaos theory
[03:03] <patdk-lap> good movie :)
[03:03] <tgm4883> I mean the mirror sync issue
[03:03] <tgm4883> that can't happen
[03:03] <patdk-lap> ya, the package list would be mirrored
[03:03] <tgm4883> exactly
[03:04] <patdk-lap> so it happened where ever the package list came from
[03:04] <UForgotten> if you only have one server, it can't happen
[03:04] <UForgotten> the second you introduce a second server, it can happen :)
[03:04] <tgm4883> UForgotten, no it cannot
[03:04] <patdk-lap> no, it would give a different error
[03:04] <patdk-lap> file not found
[03:04] <patdk-lap> but the dependency would be fine
[03:04] <tgm4883> you are implying that the list of packages on the 2nd server is generated on the 2nd server
[03:04] <tgm4883> it's not, the list is transfered as well
[03:05] <UForgotten> ok, so to recap
[03:05] <UForgotten> the package itself references a non-existent package
[03:05] <patdk-lap> no
[03:05] <tgm4883> but that isn't the error you said
[03:05] <patdk-lap> you haven't downloaded any packages yet
[03:05] <patdk-lap> the package list is not right
[03:06] <UForgotten> where are the dependencies maintained? in the package list itself? not in the package?
[03:06] <UForgotten> must be a debian thing
[03:06] <patdk-lap> both
[03:06] <tgm4883> I see what happened
[03:07] <tgm4883> Unfortunately I don't have a fix for you right now
[03:08] <UForgotten> thats ok, as long as someone knows about it.
[03:08] <UForgotten> oh btw I tuned my file system and mysql settings
[03:08] <UForgotten> mythfilldb runs in 4 minutes flat
[03:09] <patdk-lap> 4min?
[03:09] <tgm4883> UForgotten, what did you change?
[03:09] <patdk-lap> I can't remember it ever taking >1min
[03:09] <UForgotten> yep. pretty sick considering it took 30+ mins before
[03:10] <tgm4883> I'm running some tests right now on some new defaults
[03:10] <UForgotten> tgm4883: http://www.mythtv.org/wiki/Optimizing_Performance
[03:10] <Zinn> [www.mythtv.org] Optimizing Performance - MythTV Official Wiki
[03:10] <UForgotten> tgm4883: there's a mysql section
[03:10] <UForgotten> for the fs, added noatime,barrier=0
[03:11] <patdk-lap> those are really just normal mysql adjustments
[03:11] <UForgotten> I added more tho
[03:11] <UForgotten> well
[03:11] <tgm4883> yea we can't really make that a generic end all be all
[03:11] <UForgotten> not more items, more memory
[03:11] <patdk-lap> mysql is unlikely to use more memory
[03:11] <patdk-lap> and that assumes myisam database
[03:12] <patdk-lap> if you want it even faster, switch it to innodb
[03:12] <patdk-lap> and tune for innodb instead of myisam
[03:12] <UForgotten> sure, there's tons of innodb tunings
[03:12] <UForgotten> but I didn't want to deal with all the alter tables :)
[03:12] <UForgotten> erll
[03:12] <patdk-lap> no, you don't want to altertable all of them
[03:12] <UForgotten> in this case alter database
[03:12] <tgm4883> UForgotten, are you using the default innodb engine or myisam?
[03:12] <patdk-lap> just the tables that change
[03:12] <tgm4883> in 12.04?
[03:13] <UForgotten> tgm4883: I'm using whatever mythbuntu ships with, probably myisam
[03:13] <tgm4883> nope, innodb in 12.04
[03:13] <tgm4883> it's the default in mysql 5.5
[03:13] <CyberKnet> hi tgm4883. Do you know if I have to switch to the 0.26 repository to get this patch? https://github.com/MythTV/mythtv/commit/f81f712537b63502814d1f274c7da14196cedd8c
[03:13] <Zinn> [github.com] Fixes #9830. Refs #10519. Fixes channel change on PVR350. Â· f81f712 Â· MythTV/mythtv Â· GitHub
[03:14] <UForgotten> tgm4883: I hate to break it to you but its myisam
[03:14] <tgm4883> CyberKnet, I hate git, so I have no idea :)
[03:14] <tgm4883> is it in the 0.25 branch?
[03:14] <CyberKnet> tgm: it's a post 0.25 patch
[03:14] <tgm4883> UForgotten, I hate to break it to you, but it's innodb
[03:14] <CyberKnet> but I wasn't sure if you guys were pulling stuff into a 0.25-fixes that I would get with 12.04, or if it requires moving to the 0.26 branch
[03:14] <CyberKnet> s/branch/repository
[03:14] <tgm4883> UForgotten, http://dev.mysql.com/doc/refman/5.5/en/innodb-storage-engine.html
[03:15] <Zinn> [dev.mysql.com] MySQL :: MySQL 5.5 Reference Manual :: 14.3 The InnoDB Storage Engine
[03:15] <patdk-lap> UForgotten, did you upgrade to 12.04 from something else?
[03:15] <UForgotten> tgm4883: ls /var/lib/mysql/mythconverg
[03:15] <tgm4883> UForgotten, InnoDB is a high-reliability and high-performance storage engine for MySQL. Starting with MySQL 5.5, it is the default MySQL storage engine. Key advantages of InnoDB include:
[03:15] <UForgotten> tgm4883: there are .MYD and .MYI files in there
[03:15] <tgm4883> UForgotten, so?
[03:15] <UForgotten> tgm4883: clean install of mythbuntu on a brand new hard drive
[03:16] <UForgotten> tgm4883: so those would not exist if it were innodb.  tell me the mysql root password and I will prove it
[03:16] <tgm4883> UForgotten, correct, upstream specifically makes some tables myisam (actually most of them)
[03:16] <UForgotten> well there you go
[03:16] <UForgotten> so its not innodb :)
[03:16] <UForgotten> by _default_ sure
[03:16] <tgm4883> UForgotten, the fact that you have to ask me the mysql root password proves you don't know what your talking about ;)
[03:16] <UForgotten> tgm4883: I can break into it in 2 seconds
[03:16] <patdk-lap> heh, just look for frm files, without MYD files
[03:16] <tgm4883> UForgotten, break what?
[03:17] <UForgotten> authentication in mysql
[03:17] <UForgotten> --skip-grant-tables
[03:17] <tgm4883> UForgotten, god I hope so, it's set to your first users password :)
[03:17] <tgm4883> and easily resettable via
[03:17] <tgm4883> !mysql
[03:17] <Zinn> If you are having problems connecting to your mysql database, perform the following to reconfigure it: [1] sudo dpkg-reconfigure mysql-server-5.1 (pay attention to the root password you set, you will need it later)  [2] sudo dpkg-reconfigure mythtv-database [3] sudo dpkg-reconfigure mythtv-common
[03:17] <UForgotten> sql
[03:17] <UForgotten> nice
[03:19] <tgm4883> so to reiterate what I was saying, the default storage engine in myql 5.5 is innodb. Upstream makes most tables myisam. mythweather tables are innodb (not sure if upstream specified this) and temp tables are the system default
[03:19] <UForgotten> ok, I have no argument with that statement.
[03:19] <UForgotten> what I was arguing was about all tables being myisam.
[03:19] <tgm4883> so issues with mythfilldatabase taking a really long time are due to the innodb switch with regards to temp tables
[03:20] <UForgotten> so you're saying innodb is slower on the temp tables?
[03:20] <patdk-lap> if you didn't give innodb any ram, it will be painful
[03:20] <tgm4883> UForgotten, only because it isn't tweaked
[03:20] <patdk-lap> default is 8megs :(
[03:21] <tgm4883> I'm trying to reproduce, but it seems to take about 12 - 15 minutes on my backend no matter what I throw at it
[03:21] <patdk-lap> innodb loves ram
[03:21] <UForgotten> tgm4883: seems like it would be trivial to tweak both innodb and myisam, if you assume all users have 512mb of ram and make that a requirement
[03:21] <tgm4883> UForgotten, well yes, and that is why we are looking at tweaking it. There are a few issues though
[03:21] <tgm4883> 1) I cannot reproduce the issue
[03:21] <patdk-lap> you want to dedicate 512megs of ram to mysql that is normally only 50-200megs?
[03:22] <UForgotten> I didnt say dedicate 512 megs to mysql
[03:22] <tgm4883> 2) we didn't know about this issue until after release
[03:22] <UForgotten> I meant to assume they HAVE 512 and adjust tunings accordingly
[03:22] <UForgotten> tgm4883: if you're taking 12-15 minutes, you are reproducing the issue
[03:22] <patdk-lap> 512megs isn't enough ram for a combined frontend/backend
[03:22] <CyberKnet> tgm4883: given that mine took 2.5h if you have something you want to try, let me know.
[03:23] <CyberKnet> I have 8gb ram in a dedicated back end, so I can throw as much memory at it as you want.
[03:23] <tgm4883> That couldn't have happened better if I asked :)
[03:23] <UForgotten> a full empty run took 7 hours before
[03:23] <patdk-lap> how large is the temp tables?
[03:25] <tgm4883> CyberKnet, what options are you running with when testing mythfilldatabase?
[03:25] <tgm4883> UForgotten, ^
[03:25] <UForgotten> no options
[03:25] <UForgotten> just mythfilldatabase
[03:25] <UForgotten> I dont know how large the temp tables got
[03:26] <CyberKnet> tgm4883: none. just mythfilldatabase on the command line - although I had just removed and re-added all my channels so I had no channel data.
[03:27] <CyberKnet> if there's a way to remove all the guide data without necessarily having to rescan my channels I'd love that more than having to rescan channels again :)
[03:28] <CyberKnet> It took quite a while to rescan the HD channels.
[03:28] <UForgotten> --dd-grab-all does that I think
[03:29] <UForgotten> it will still probably update channels
[03:29] <UForgotten> CyberKnet: what file system are you running?  probably some tweaks there
[03:29] <CyberKnet> ext4
[03:29] <UForgotten> ok definitely add noatime,barrier=0 to your options
[03:29] <UForgotten> that made a huge difference for me
[03:30] <UForgotten> instead of 2MB/s writes I get 5 MB/s now
[03:30] <CyberKnet> that's a dangerous change to make though.
[03:30] <UForgotten> not really
[03:30] <CyberKnet> if you live in an area with unreliable power.
[03:30] <UForgotten> its just disabling a feature.
[03:30] <UForgotten> you should never run a pc without a ups
[03:30] <UForgotten> ever
[03:30] <CyberKnet> ext4's failure mode on an irregular unmount is pretty bad.
[03:30] <CyberKnet> Sure. Or if you get a kernel panic.
[03:31] <CyberKnet> I'd like to say it never happens, but it wouldn't be true.
[03:31] <UForgotten> well thats a different story lol
[03:31] <CyberKnet> ;)
[03:31] <tgm4883> yea
[03:31] <tgm4883> --dd-grab-all                   refresh full data using DataDirect
[03:31] <tgm4883> I wasn't running that before, so I'm running it now
[03:31] <patdk-lap> UForgotten, try adding this to mysql: innodb_flush_log_at_trx_commit=2
[03:31] <CyberKnet> and I can never remember the sysreq magic keys
[03:31] <CyberKnet> there's an acronym for the keys to press and the order to press them, but I never remember.
[03:31] <CyberKnet> ext4 on root, xfs on video
[03:32] <patdk-lap> heh, I'm running mysql + video on zfs
[03:32] <tgm4883> CyberKnet, busier backwards
[03:32] <tgm4883> or Raising Elephants Is So Utterly Boring
[03:33] <tgm4883> I always remember busier though
[03:33] <tgm4883> as in, I'd be busier if I didn't have to reboot this box
[03:33] <CyberKnet> hahaha
[03:33] <CyberKnet> yeah
[03:33] <CyberKnet> I need to write it on paper and then tape it above my sysreq key :)
[03:34] <CyberKnet> tgm4883: ok, the patch in question for trac 9830 is in the fixes/0.25 branch. Is that building for 12.04 ?
[03:34] <tgm4883> yes
[03:34] <tgm4883> are you running amd64 or i386?
[03:34] <CyberKnet> amd64
[03:34] <tgm4883> then you will want to wait
[03:34] <tgm4883> probably 10 hours
[03:35] <tgm4883> that should be safe :)
[03:35] <tgm4883> UForgotten is running amd64 as well
[03:35] <CyberKnet> Linux thunder 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[03:35] <CyberKnet> I will want to wait 10 hours?
[03:35] <tgm4883> yea
[03:35] <CyberKnet> and there will be an update via apt-get?
[03:36] <tgm4883> otherwise you'll be like "why is it telling me it can't install mythtv-common!"
[03:36] <tgm4883> yea
[03:36] <UForgotten> heh
[03:36] <CyberKnet> aaah :)
[03:36] <CyberKnet> hah
[03:36] <CyberKnet> sweet, thanks tgm4883 :)
[03:36] <tgm4883> CyberKnet, in reality, you can watch for the amd64 builds to finish building here https://launchpad.net/~mythbuntu/+archive/0.25/+packages
[03:36] <Zinn> [launchpad.net] Packages in “0.25” : 0.25 : “Mythbuntu Developers” team
[03:36] <CyberKnet> I updated last night, so I don't mind waiting 24 hours.
[03:36] <tgm4883> but they aren't scheduled to start for 9 more hours
[03:36] <CyberKnet> can I still switch repos via dpkg-reconfigure, or do I have to use mcc?
[03:37] <tgm4883> you have to use MCC in 12.04
[03:37] <CyberKnet> does it have a command line counterpart?
[03:37] <tgm4883> if you really really don't want to use MCC, there is a cmd line way
[03:37] <CyberKnet> It's not that I mind MCC, it's nice.
[03:37] <CyberKnet> it's that I'm frequently not at the head of my backend :)
[03:37] <tgm4883> yea
[03:38] <CyberKnet> and VNC ... well it's VNC, right? :D
[03:38] <CyberKnet> over a LAN it's fine. over SSH ... not so much :)
[03:38] <tgm4883> you can add any PPA via apt-add-repository, such as 'apt-add-repository ppa:mythbuntu/0.25'
[03:38] <CyberKnet> anyways, I think I have them both on 0.25 right now anyway, so I'll update in a few hours.
[03:38] <CyberKnet> oh, cool.
[03:39] <tgm4883> that will probably confuse the MCC plugin though, I haven't tested that
[03:39] <CyberKnet> If I'm completely honest though, I will promptly forget that though, and bug you about it next time. :D
[03:39] <CyberKnet> I'll just make a habit of waiting to use MCC
[03:39] <CyberKnet> that will make us all happy.
[03:40] <CyberKnet> MCC really is quite a nice utility. And as of yet, I haven't heard myself offering to make it work in text mode :D
[03:40] <CyberKnet> ncurses.
[03:41] <CyberKnet> tgm4883: I'm about to be gone for 15 mins or so. Anything you need/want me to try mysql-related before I do?
[03:41] <tgm4883> CyberKnet, nope, I'm running another test right now that seems to be taking longer, so I'll wait until it finishes
[03:41] <tgm4883> if it's reproduced the issue, I can actually work on the tweaks
[03:42] <CyberKnet> nice. thanks for your hard work on this man. :)
[03:42] <CyberKnet> uh... stupid question ... how do I find out what version of myth packages I have installed from the command line?
[03:43] <tgm4883> dpkg -l mythtv*
[03:43] <tgm4883> or you could ask the binaries
[03:43] <tgm4883> mythfrontend --version
[03:43] <tgm4883> mythbackend --version
[03:44] <CyberKnet> hmmmm
[03:44] <CyberKnet> I think that I should already have that patch then.
[03:44] <CyberKnet> it was post 0.25 but my packages are 2:0.25.0+fixes.20120423.46062bf-0ubuntu0mythbuntu3
[03:46] <CyberKnet> which if I am reading that correctly should have an update made on 2012-04-02 15:03:40
[03:46] <CyberKnet> https://github.com/MythTV/mythtv/blob/fixes/0.25/mythtv/libs/libmythtv/mpegrecorder.cpp
[03:46] <Zinn> [github.com] mythtv/mythtv/libs/libmythtv/mpegrecorder.cpp at fixes/0.25 Â· MythTV/mythtv Â· GitHub
[03:46] <CyberKnet> Zinn is such a clever cookie.
[03:46] <Zinn> Hi CyberKnet, something I can help you with today?  I am a bot, use !help to see what I can do.
[03:47] <CyberKnet> anyways. that is not good news for me.
[03:47] <UForgotten> Zinn, can you calculate the airspeed velocity of a laden swallow?
[03:47] <Zinn> Hi UForgotten, something I can help you with today?  I am a bot, use !help to see what I can do.
[03:47] <UForgotten> !help
[03:47] <CyberKnet> I was hoping to fix an issue with the PVR-500 that occurred since I upgraded to 0.25.
[03:47] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[03:47] <CyberKnet> back to back recordings on the same tuner seem to keep both tuners on the card until reboot.
[03:47] <CyberKnet> drat.
[03:47] <CyberKnet> ok.
[03:47] <CyberKnet> thanks tgm4883.
[03:50] <UForgotten> tgm4883: mythfilldatabase --dd-grab-all finished in 15 minutes
[03:51] <tgm4883> UForgotten, mine is still going on the default settings
[03:51] <tgm4883> so I'd say it's reproduced
[03:51] <tgm4883> but I'll wait for it to finish so I can gauge how much better it gets
[03:51] <UForgotten> ok. have fun. g'night
[03:51] <tgm4883> night
[23:32] <a8s0lut0> hey hey, having loads of issues with mythbuntu 12.04 out of the box
[23:33] <a8s0lut0> anyone available to chat for a minute?  Love the product, was super pumped for mythbuntu 12.04, i figured it'd be nothing but improvements
[23:33] <a8s0lut0> that and my 11.10 quit tuning channels.. anyway..
[23:35] <a8s0lut0> 1) HDMI doesn't work after reboot (installed w/ VGA output)           2) HDHomeRun_config can't find my tuners    3) sound doesn't work (when HDMI did for a minute, and i can't find "sound preferences"!!
[23:40] <a8s0lut0> 4) VNC doesn't connect, but is running.
[23:41] <a8s0lut0> I had to overcome those in 11.10 but googling forums and things mostly worked
[23:41] <a8s0lut0> this time, not so much


[03:58] -queuebot:#ubuntu-release- Unapproved: python-fitsio (zesty-proposed/universe) [0.9.10+dfsg-1build1 => 0.9.10+dfsg-1ubuntu1] (no packageset)
[03:59] -queuebot:#ubuntu-release- Unapproved: accepted python-fitsio [source] (zesty-proposed) [0.9.10+dfsg-1ubuntu1]
[04:52] -queuebot:#ubuntu-release- Unapproved: blacs-mpi (zesty-proposed/universe) [1.1-37ubuntu3 => 1.1-38] (no packageset) (sync)
[04:52] -queuebot:#ubuntu-release- Unapproved: accepted blacs-mpi [sync] (zesty-proposed) [1.1-38]
[04:52] -queuebot:#ubuntu-release- Unapproved: xbase64 (zesty-proposed/universe) [3.1.2-11 => 3.1.2-12] (no packageset) (sync)
[04:53] -queuebot:#ubuntu-release- Unapproved: accepted xbase64 [sync] (zesty-proposed) [3.1.2-12]
[06:41] -queuebot:#ubuntu-release- Unapproved: node-mocha (zesty-proposed/universe) [1.20.1-2 => 1.20.1-7] (no packageset) (sync)
[06:42] -queuebot:#ubuntu-release- Unapproved: accepted node-mocha [sync] (zesty-proposed) [1.20.1-7]
[06:59] <rbasak> o/
[07:00] <rbasak> I'm going to swap my SRU day to today as I'll be busy with the sponsorship party on Wednesday
[07:00] <rbasak> infinity: ^
[07:04] <rbasak> apw: when you're in, please could you take a look at releasing mysql-5.7 to xenial-updates please? I think it's ready. The dep8 failure looks like it's an intentional environment thing?
[07:57] -queuebot:#ubuntu-release- Unapproved: accepted makedev [source] (precise-proposed) [2.3.1-89ubuntu3]
[08:00] -queuebot:#ubuntu-release- Unapproved: accepted makedev [source] (trusty-proposed) [2.3.1-93ubuntu2~ubuntu14.04.1]
[08:00] -queuebot:#ubuntu-release- Unapproved: accepted makedev [source] (xenial-proposed) [2.3.1-93ubuntu2~ubuntu16.04.1]
[08:01] -queuebot:#ubuntu-release- Unapproved: accepted makedev [source] (yakkety-proposed) [2.3.1-93ubuntu2~ubuntu16.10.1]
[08:13] <jbicha> rbasak: ostree/yakkety is not an autopkgtest regression: http://autopkgtest.ubuntu.com/packages/f/flatpak/yakkety/s390x http://autopkgtest.ubuntu.com/packages/f/flatpak/yakkety/armhf
[09:07] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.10.0-14.16~16.04.1] (no packageset)
[09:45] -queuebot:#ubuntu-release- Unapproved: gnome-dvb-daemon (zesty-proposed/universe) [1:0.2.91~git20170110-2 => 1:0.2.91~git20170110-2build1] (no packageset)
[09:46] -queuebot:#ubuntu-release- Unapproved: accepted gnome-dvb-daemon [source] (zesty-proposed) [1:0.2.91~git20170110-2build1]
[09:51] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.10.0-14.16~16.04.1]
[09:54] <flexiondotorg> Please unblock mate-desktop/1.18.0-0ubuntu2
[09:54] <flexiondotorg> Please unblock mate-settings-daemon/1.18.0-0ubuntu2
[09:55] <flexiondotorg> Please unblock caja-dropbox/1.18.0-0ubuntu2
[10:28] <Laney> flexiondotorg: There is no block, just a queue freeze which is reviewed regularly. I'm about to do a pass.
[10:32] <flexiondotorg> Ah, OK. Thanks Laney
[11:18] -queuebot:#ubuntu-release- Unapproved: accepted snapd-glib [source] (zesty-proposed) [1.9-0ubuntu1]
[11:26] -queuebot:#ubuntu-release- Unapproved: accepted thunderbird [source] (zesty-proposed) [1:45.8.0+build1-0ubuntu1]
[11:28] <rbasak> Laney: are you able to stop phasing of cups 2.1.3-4ubuntu0.2 in xenial-updates please?
[11:28] <Laney> rbasak: I think you probably need an AA
[11:29] <rbasak> Looks like there are a ton of reports so the fix to bug 1642966 didn't work.
[11:29] <rbasak> Laney: ah. I thought you were!
[11:29] <rbasak> apw: ^
[11:29] <rbasak> xnox: ^
[11:29] <Laney> assuming that the SRU team can't do it themselves
[11:29] <Laney> nope!
[11:29] <rbasak> I believe we can't.
[11:31] <Laney> When do you unphase vs. removing the package?
[11:31] <Laney> Just OOI
[11:31] <rbasak> No sure.
[11:31] <rbasak> Not sure.
[11:31] <rbasak> In this case removal might be appropriate I think.
[11:36] -queuebot:#ubuntu-release- Unapproved: adplug (zesty-proposed/universe) [2.2.1+dfsg3-0.3 => 2.2.1+dfsg3-0.4] (no packageset) (sync)
[11:37] -queuebot:#ubuntu-release- Unapproved: accepted adplug [sync] (zesty-proposed) [2.2.1+dfsg3-0.4]
[11:38] -queuebot:#ubuntu-release- Unapproved: apt-dpkg-ref (zesty-proposed/universe) [5.3.1+nmu1 => 5.3.1+nmu2] (no packageset) (sync)
[11:39] -queuebot:#ubuntu-release- Unapproved: accepted apt-dpkg-ref [sync] (zesty-proposed) [5.3.1+nmu2]
[11:39] -queuebot:#ubuntu-release- Unapproved: boxer-data (zesty-proposed/universe) [10.5.14 => 10.5.15] (no packageset) (sync)
[11:40] -queuebot:#ubuntu-release- Unapproved: accepted boxer-data [sync] (zesty-proposed) [10.5.15]
[11:44] <xnox> rbasak, Laney - removal is still a regression, as people will not get the other fix, which is ultimately causing the upgrade failures......
[11:50] <rbasak> xnox: I don't follow. The bug that causes the maintainer script failure (a race?) is not fixed. Correct?
[11:53] <xnox> cups in xenial-release prematurely shutsdown preventing people from accessing the web interface https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300
[11:53] <xnox> when attempting to fix that, it was discovered that upgrade scripts fail because systemd units end up being silly
[11:55] <xnox> not everyone is affected by either upgrade bug; or the web interface bug.
[11:56] <xnox> we never got a reliable reproducer for the upgrade failure
[11:56] -queuebot:#ubuntu-release- Unapproved: accepted gnome-dictionary [source] (zesty-proposed) [3.24.0-0ubuntu1]
[11:58] <rbasak> xnox: OK, but given the SRU resulted in further reports, the bug still exists, right?
[11:58] -queuebot:#ubuntu-release- Unapproved: accepted xfdashboard [source] (zesty-proposed) [0.6.1-0ubuntu1]
[11:58] <rbasak> By "the bug" I mean the systemd problem.
[11:58] <xnox> correct
[11:59] <xnox> or at least a similar issue is still manifesting itself elsehow.
[11:59] <rbasak> By removing the latest SRU we'll stop people hitting the systemd problem, which they are right now.
[11:59] <xnox> e.g. i still think it's correct to keep what was done in .2 but further fixes are needed.
[11:59] <rbasak> They then won't get the web interface fix
[11:59] <xnox> true
[11:59] <rbasak> But from the point of view of users unaffected by the web interface problem, it's a "regression" they won't hit then.
[12:00] <rbasak> So IMHO, we should do that pending a full fix for the systemd issue.
[12:01] <Laney> IIUC you could copy .1 back into -updates
[12:01] <rbasak> I don't think that'll help.
[12:01] <xnox> .1 never made into -updates because of failure to upgrade
[12:01] <Laney> Help whajt?
[12:01] <Laney> Oh
[12:01] <rbasak> *Any* update to cups has the race that leads to the maintainer script failure.
[12:01] <Laney> I thought that one was released
[12:01] <xnox> nope mark hit upgrade failure and kindly makred it block-proposed =)
[12:01] <xnox> or some suhc
[12:02] <Laney> Then I think killing this one is right
[12:04] -queuebot:#ubuntu-release- Unapproved: accepted mir [source] (zesty-proposed) [0.26.2+17.04.20170322.1-0ubuntu2]
[12:08] <Laney> flexiondotorg: Could I trouble you to include patch headers please?
[12:08] <Laney> and the changelog is most uninformative
[12:09] <flexiondotorg> This is for mate-desktop and mate-settings-daemon right?
[12:09] <Laney> Yeh
[12:12] -queuebot:#ubuntu-release- Unapproved: wmaker (zesty-proposed/universe) [0.95.7-7 => 0.95.7-8] (no packageset) (sync)
[12:12] -queuebot:#ubuntu-release- Unapproved: accepted wmaker [sync] (zesty-proposed) [0.95.7-8]
[12:17] <Laney> flexiondotorg: and https://launchpadlibrarian.net/312618974/caja-dropbox_1.18.0-0ubuntu1_1.18.0-0ubuntu2.diff.gz <- did you mean to remove 2003_execute_via_dbus_launch.patch?
[12:17] <Laney> (also, Popen has an env= argument)
[12:18] <flexiondotorg> Ah, yes. 2003_execute_via_dbus_launch.patch should have been dropped.
[12:18]  * Laney invokes the reject-o-tron
[12:18] <flexiondotorg> I'll resubmit mate-desktop, mate-settings-daemon and caja-dropbox later with the changes you've suggested.
[12:19] <Laney> If you want to fix nautilus-dropbox as well, I wouldn't complain :-)
[12:19] <flexiondotorg> Laney Can I upload with the same versions, now that are being rejected, or should I bump them to -0ubuntu3?
[12:19] <Laney> You can re-use
[12:20] <flexiondotorg> OK, I'll do nautilus-dropbox too.
[12:20] <Laney> Fanx
[12:20] -queuebot:#ubuntu-release- Unapproved: rejected caja-dropbox [source] (zesty-proposed) [1.18.0-0ubuntu2]
[12:21] -queuebot:#ubuntu-release- Unapproved: rejected mate-desktop [source] (zesty-proposed) [1.18.0-0ubuntu2]
[12:21] -queuebot:#ubuntu-release- Unapproved: rejected mate-settings-daemon [source] (zesty-proposed) [1.18.0-0ubuntu2]
[12:21] <Laney> also communicating with Dropbox about their borkedness would be good, but not strictly required
[12:21] <flexiondotorg> I've tried.
[12:22] <Laney> (for nautilus-dropbox you would presumably look at XDG_CURRENT_DESKTOP and only do this hack if it is Unity)
[12:23] <Laney> "Unity" in os.environ.get("XDG_CURRENT_DESKTOP", "").split(":") or something
[12:24]  * Laney gets hungry
[12:28] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-system-settings [sync] (zesty-proposed) [0.4+17.04.20170324-0ubuntu1]
[12:34] -queuebot:#ubuntu-release- Unapproved: accepted youker-assistant [source] (zesty-proposed) [2.2.7-0ubuntu1]
[12:39] <flexiondotorg> Laney, Yes. For nautilus-dropbox I check it required for Unity.
[12:39] <Laney> Neato wheetos
[12:39] -queuebot:#ubuntu-release- Unapproved: rejected indicator-china-weather [source] (zesty-proposed) [2.2.1-0ubuntu1]
[12:41] -queuebot:#ubuntu-release- Unapproved: accepted lirc [sync] (zesty-proposed) [0.9.4c-8]
[12:42] <Laney> I left a package in the queue for someone else to enjoy
[12:42] -queuebot:#ubuntu-release- Unapproved: accepted budgie-desktop [source] (zesty-proposed) [10.2.9-3ubuntu4]
[12:52] <jibel> could someone review ubuntu-ui-extras in the unapproved queue? it goes with ubuntu-system-settings that has just been approved
[13:14] <apw> jibel, in zesty ?
[13:14] <jibel> apw, yes
[13:14] <apw> jibel, /me hates on syncs
[13:19] <rbasak> apw: see cups discussion above please. Are you able to do a phasing stop or delete from xenial-updates?
[13:21] <apw> i can delete that, what version was there before ?
[13:22] <rbasak> I believe there was nothing in xenial-updates. I'll check.
[13:22] <apw> jibel, the diff here is vast, ugg
[13:23] <rbasak> Yeah, AFAICS 2.1.3-4 only in the release pocket.
[13:24] <apw> rbasak, is there a bug for the regression
[13:24] <apw> so i can ref it
[13:29] <rbasak> Yes, one moment
[13:29] <rbasak> apw: let's use 1676380 to track today's "regression".
[13:33] <apw> rbasak, gone modulo the publisher
[13:36] <rbasak> Thank you! I'll sort out the bugs.
[13:37] <ginggs> anyone know of something that changed in armhf and s390x autopkgtesters between 2017-01-29 and 2017-03-02?  varnish now fails its autopkgtests  - Port "6081" should be listening with tcp
[13:38] <ginggs> ^ blocks pcre3 migration
[13:39] <xnox> ginggs, firewall upgrades? =)
[13:40] <infinity> xnox: I assume that's a local loopback.
[13:41] <infinity> Certainly looks like it should be.
[13:41] <infinity> So, something lxc/lxdish is going on there.
[13:42] <infinity> Laney: ^
[13:42] <Laney> Yes?
[13:42] <Laney> Did someone run it locally?
[13:43] <ginggs> Laney: not on the affected architectures
[13:43] <xnox> ginggs, locally on amd64 but with e.g. lxd runner
[13:43] <infinity> Oh.  Or.
[13:44] <infinity> ginggs: It could be as simple as the test not depending on net-tools, and those chroots being "cleaner"?
[13:44] <infinity> Since the tests uses 'netstat' to determine if the port is open, and netstat was demoted out of essential.
[13:45] <ginggs> ah, ok, let me try locally with lxd runner
[13:45] <infinity> On 2017-01-27
[13:45] <infinity> Which would sort of match your timeline.
[13:47] <xnox> oooooh
[13:48] <infinity> Of course, I'm having a heck of a time finding the string netstat here now. :P
[13:51] <infinity> Ah-ha.
[13:51] <infinity> Found it.
[13:56] <infinity> ginggs: Assuming it's not LXC screwing with you, but just the net-tools demotion, then my ruby-specinfra upload will fix it.
[13:57] -queuebot:#ubuntu-release- Unapproved: ruby-specinfra (zesty-proposed/universe) [2.66.0-1 => 2.66.0-1ubuntu1] (no packageset)
[13:57] <infinity> ginggs: https://launchpad.net/ubuntu/+source/ruby-specinfra/2.66.0-1ubuntu1
[13:58] -queuebot:#ubuntu-release- Unapproved: accepted ruby-specinfra [source] (zesty-proposed) [2.66.0-1ubuntu1]
[13:58] <ginggs> infinity: ta!
[13:59] <infinity> (If it is an LXC issue, my upload is still correct, it just might not fix your bug :P)
[14:02] <Laney> https://paste.ubuntu.com/24260974/
[14:02] <LocutusOfBorg> hello apw, or any AA, can you please move libboost-filesystem-dev to main?
[14:02] <LocutusOfBorg> I'm working to remove boost1.61 and mir is unhappy
[14:02] <infinity> Laney: Kay, so it's LXC not letting us bind to some ports?
[14:03] <Laney> No
[14:03] <infinity> Oh, I misread.
[14:03] <infinity> It's net-tools.  Check.
[14:03] <infinity> So, we have an inverse bug that some of our testing chroots aren't clean enough.
[14:04] <infinity> Laney: I somehow read the second run as a failure.  In my defense I just woke up. ;)
[14:04] <LocutusOfBorg> BTW boost-default is already in main, not sure why it is half in universe
[14:05] <infinity> LocutusOfBorg: Reference to mir unhappiness?
[14:05] <LocutusOfBorg> mirtest-dev/amd64 unsatisfiable Depends: libboost-filesystem-dev
[14:05] <infinity> It being half in universe is correct, as only the bits with deps end up in main.
[14:05] <LocutusOfBorg> oh indeed
[14:06] <LocutusOfBorg> my bad, to make mir less pita during boost transitions, we ended up in depending on the -dev package
[14:06] <LocutusOfBorg> instead of the runtime one
[14:06] <LocutusOfBorg> http://launchpadlibrarian.net/312291835/mir_0.26.2+17.04.20170322.1-0ubuntu1_0.26.2+17.04.20170322.1-0ubuntu2.diff.gz
[14:06] <LocutusOfBorg> such stuff -         libboost-filesystem1.61.0 | libboost-filesystem1.58.0 | libboost-filesystem1.55.0,
[14:06] <LocutusOfBorg> is unmaintainable
[14:06] <LocutusOfBorg> +         libboost-system-dev, <-- this is really better to me
[14:07] <LocutusOfBorg> so, at the end just the -dev package needs promoting
[14:07] <LocutusOfBorg> to make the whole Borg community happy
[14:07]  * LocutusOfBorg BTW nice article on slashdot wrt Ubuntu Beta!
[14:07] <infinity> That should show up on component-mismatches-proposed.  Did that change *just* get uploaded?
[14:08] <infinity> Yeah, it did.
[14:08] <infinity> So, our reports should yell at us shortly.  I might wait on that to see if they say something else.
[14:08] <LocutusOfBorg> as you wish :) yes, I'm working on removing boost1.61 from main/archive
[14:08] <philroche> infinity: RE. gce-compute-image-packages lp:1668327 Patches for all suites in -proposed have been verified. GCE are eager to get this released, would you be able to move these from -proposed to -updates? https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1668327
[14:22] <infinity> philroche: Sure thing.
[14:22] <philroche> infinity: Thanks
[14:24] <infinity> LocutusOfBorg: Err, that mir upload is still wrong.
[14:25] <infinity> LocutusOfBorg: If your goal is to remove all boost << 1.62, not removing the versioned deps won't get you far. :P
[14:25] <infinity> LocutusOfBorg: Oh.  OR I MISSED THE '-' in the diff.
[14:25] <infinity> Man, I really need to wake up before I type.
[14:25] <infinity> Nevermind me. :P
[14:26] <mapreri> man, I was already yelling :|
[14:26] <mapreri> infinity: don't do it again! :>
[14:26] <infinity> I think I should find some breakfast and/or coffee before I continue.
[14:27] <infinity> Two "I can't read" moments within half an hour isn't a good record.
[14:27] <mapreri> coffee that way -------->
[14:33] <jbicha> any Archive Admin interested in reviewing switcheroo-control in the Zesty new queue? it's a small pkg required for GNOME 3.24's dual gpu feature
[14:38] <ginggs> infinity: your ruby-specinfra upload did indeed fix varnish autopkgtests, thanks
[14:47] <infinity> ginggs: \o/
[14:57] -queuebot:#ubuntu-release- Unapproved: binutils-m68hc1x (zesty-proposed/universe) [1:2.18-8 => 1:2.18-9] (no packageset) (sync)
[14:57] -queuebot:#ubuntu-release- Unapproved: accepted binutils-m68hc1x [sync] (zesty-proposed) [1:2.18-9]
[15:07] -queuebot:#ubuntu-release- Unapproved: lvm2 (zesty-proposed/main) [2.02.167-1ubuntu2 => 2.02.167-1ubuntu5] (core)
[15:08] <LocutusOfBorg> lol infinity <3
[15:08] <LocutusOfBorg> the problem is not ENOCOFFEE
[15:08] <LocutusOfBorg> but EMONDAY
[15:08] <LocutusOfBorg> you are not alone
[15:09] <LocutusOfBorg> in Italy we just had daylight saving time switch, and I did woke up one hour before today, so my body has a two hours "jet lag" right now :)
[15:12] -queuebot:#ubuntu-release- Unapproved: s390-tools (zesty-proposed/main) [1.37.0-0ubuntu2 => 1.37.0-0ubuntu3] (core)
[15:15] <xnox> oh we are in the full frozen mode now.... horum.
[15:19] <infinity> xnox: A cherrypick that adds the new version to the changelog doesn't seem like a cherrypick?  What's the difference between this and just updating to the point release?
[15:20] <infinity> stgraber: That lvm2 upload is a bit wonky.  It seems to entirely scrub the previous versions from history?
[15:20] <infinity> stgraber: http://launchpadlibrarian.net/312918372/lvm2_2.02.167-1ubuntu4_2.02.167-1ubuntu5.diff.gz
[15:21] <xnox> infinity, 342 files changed, 3778 insertions(+), 3688 deletions(-) of refactor; rewriting of argument parsing; whitespace changes; and header includes reordering.
[15:21] <xnox> https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1671497/comments/4
[15:21] <xnox> and minor renames of files and/or macros
[15:21] <infinity> xnox: Ahh, so maybe the bit here that's rubbing me the wrong way is you adding "1.37.1" news items to README, which implies this is 1.37.1
[15:22] <infinity> xnox: When really, it's 1.37.0 with a couple of upstream cherrypicks.
[15:22] <xnox> well i've cherrypicked all the worthy fixes.... all of which are described by the changelog entry, hence the pick up of the changelog entry too.
[15:23] <infinity> xnox: Yeah, but the way you've rewritten the readme says "this is 1.37.1", which it isn't.
[15:23] <infinity> Not even close.
[15:23] <xnox> true
[15:24] <infinity> This is what patch headers are for.  Don't muck with the upstream README, IMO.
[15:24] <xnox> i could take those changelog entries out of the patch; and stick them into debian/changelog instead?!
[15:24] <xnox> patch header is not end-user visible....
[15:24] <infinity> The debian changelog being more verbose also is never a bad idea.
[15:25] <infinity> Patch headers should record origin (assuming this was from a VCS, not just a diff of a tarball), and debian/changelog can absolutely document the bugs fixed.
[15:25] <xnox> public VCS :`(
[15:26] <xnox> there is this java webapp one has to click through to get to the tarball and accept GPL EULA
[15:26] <infinity> Mucking with the upstream readme would be more acceptable to me if you documneted the changes under "1.37.0 + Ubuntu patches" or something, but it still seems gross to document it there.
[15:26] <infinity> Hahahaha.  Have you told them that's BS?  We've done so in the past (with IBM even, I think), and won the argument.
[15:27] <infinity> Since the GPL explicitly places no burden on people downloading, only people redistributing.
[15:27] <infinity> Thus it's not an EULA at all.
[15:27] <xnox> i have. and they started to download the tarball and attach it to a launchpad bug reports for me.
[15:27] <infinity> *cough*
[15:27] <infinity> I'm laughing too hard to type.
[15:27]  * xnox now feels for real to be back from vacation
[15:28] <xnox> There was cause and effect and change of behaviour.... but an enterpice solution with a personal butler service.
[15:29] <infinity> Wow.  You win the creative spelling of the day award.
[15:29] <infinity> apw: Sorry, xnox's "enterpice" beats anything you'll come up with today.
[15:29] <rbalint> hi, who should be pinged for binary package removals? LP: #1671423
[15:30] <philroche> infinity: Thanks for the gce-compute-image-packages work :)
[15:32] <infinity> rbalint: A quick investigation looks like that bug should be titled "bcftools is FTBFS on 32-bit arches"?
[15:33] <xnox> infinity, i have not been typing on a keyboard for a whole week. (there was no wifi at the slope of the resort, where i was staying) my words per minute are way down.
[15:33] <infinity> Or... Some arches.
[15:33] <xnox> infinity, i already talked today about the release meetings at bluefun with pat as well.
[15:34] <rbalint> infinity: well it looks unlikely to be fixed #819617
[15:35] <rbalint> infinity: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819617  FTBFS: any-i386 - floating point idiosyncracies
[15:35] <rbalint> rbalint: rbalint more patience :-)
[15:37] <rbalint> rbalint: infinity and kineticstools does not migrate due to the missing build
[15:38] <infinity> rbalint: Well, that was a long read.  Tempted to go read the upstream report too, but I have better things to do. ;)
[15:39] <rbalint> infinity: did not want to push you that far :-)
[15:41] <mapreri> apw: should I suppose you didn't manage to push the armhf timeout change to autopkgtest workers?  (re: diffoscope timeouting)
[15:41] <infinity> rbalint: Done.
[15:42] <rbalint> infinity: thanks!
[15:42] -queuebot:#ubuntu-release- Unapproved: rejected s390-tools [source] (zesty-proposed) [1.37.0-0ubuntu3]
[15:44] <infinity> jibel: Ugh.  That ubuntu-ui-extras upload is very not feature-freeze friendly.
[15:45] <stgraber> infinity: hmm, I wonder what's going on here... I uploaded 0ubuntu2 a couple weeks back and nothing since
[15:46] -queuebot:#ubuntu-release- New sync: ubuntu-filemanager-app (zesty-proposed/primary) [0.4+17.04.20170323-0ubuntu1]
[15:46] <infinity> stgraber: https://launchpad.net/ubuntu/+source/lvm2/+publishinghistory
[15:46] <stgraber> infinity: and rmadison tells me the only lvm2 in zesty right now is 2.02.167-1ubuntu2 (nothing in zesty-proposed)
[15:46] <infinity> stgraber: publishing history shows some upload and the deletion action?
[15:47] <infinity> s/the/then/
[15:47] <infinity> stgraber: By you, even. :P
[15:47] <infinity> stgraber: So, okay, let me diff against ubuntu2 to get something more readable.
[15:47] <stgraber> infinity: ah, yeah, almost forgot about that. It was a mistargeted PPA upload that made it to proposed and that I wiped from the archive before it had a chance to build
[15:48] <infinity> stgraber: Yep, the diff against ubuntu2 is indeed much more readably sane.  Accepting.
[15:48] -queuebot:#ubuntu-release- Unapproved: isso (zesty-proposed/universe) [0.10.6-2 => 0.10.6-2ubuntu1] (no packageset)
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted isso [source] (zesty-proposed) [0.10.6-2ubuntu1]
[15:49] -queuebot:#ubuntu-release- Unapproved: accepted lvm2 [source] (zesty-proposed) [2.02.167-1ubuntu5]
[15:50] <infinity> slangasek: When the personal/unity8/whatever session landed in the default install, did we also do away with their blanket exception to abuse freezes?  I suspect we should have, not sure if we explicitly did?
[15:51] <infinity> (Asking because of a current landing that is very freeze-unfriendly)
[15:51] <infinity> (Which only affects the unity8 session)
[15:51] <infinity> (More stuff in brackets)
[15:58] <jibel> infinity, agreed it is not freeze friendly at all
[15:59] <jibel> infinity, hence my question last week if we could have an overlay for zesty, a blanket exception would work too
[16:00]  * infinity fixed ubuntu-archive-tools a bit better for powerpc removal.
[16:00] <davmor2> ( infinity ) thought I'd put you in () being as you loved them so much
[16:00] <infinity> jibel: My preference would be for removing the unity8 session from the default install, but I suspect I'd lose that argument. :/
[16:01] <jibel> infinity, right, that would stay your preference
[16:12] -queuebot:#ubuntu-release- Unapproved: chrome-gnome-shell (zesty-proposed/universe) [8.2-0ubuntu1 => 8.2-0ubuntu2] (ubuntugnome)
[16:39] -queuebot:#ubuntu-release- Unapproved: update-manager (trusty-proposed/main) [1:0.196.22 => 1:0.196.23] (core)
[16:40] <slangasek> infinity, jibel: what's freeze-unfriendly about it?  unity8 is supposed to have strong upstream CI such that the release team should feel comfortable granting exceptions
[16:41] <infinity> slangasek: Did you look at the diff before making that statement?
[16:41] <slangasek> no, of course not
[16:41] <slangasek> what's in the diff? :)
[16:42] <infinity>  127 files changed, 6353 insertions(+), 1101 deletions(-)
[16:42] -queuebot:#ubuntu-release- Unapproved: rejected update-manager [source] (trusty-proposed) [1:0.196.23]
[16:42] <infinity> http://paste.ubuntu.com/24261929/
[16:43] <bdmurray> rbasak: I fix update-manager thanks for spotting that!
[16:43] <infinity> slangasek: I'm sure their CI is lovely, but that's a whole lot of change.
[16:43] <slangasek> infinity: ok. does it change the packaging?
[16:44] <infinity> And I don't buy the "upstream's CI is so good we don't care about freezes anymore" argument, or we'd take new versions of a lot more software than we do.
[16:44] <infinity> slangasek: No, it doesn't change the packaging.  How's that relevant?
[16:45] <slangasek> lots of upstreams have CI.  not a lot of upstreams have CI that it's been worth our time to grant exceptions around
[16:46] <slangasek> it's relevant because we should be able to trust upstream to be the authority on the quality of their code, and we should only have to get involved for integration questions
[16:47] -queuebot:#ubuntu-release- Unapproved: xorg-server (zesty-proposed/main) [2:1.18.4-1ubuntu9 => 2:1.19.3-1ubuntu1] (desktop-core, xorg)
[16:47] <jibel> slangasek, it adds printing support to ubuntu-system-settings
[16:47] <jibel> ie not a bug fix
[16:48] <jibel> OTOH, it has CI + manual verification of the silo
[16:48] <infinity> slangasek: So, I understand that's the argument we used for ci-train landings, I don't think we EVER used it for freeze exceptions.  The exception they had previously was based on the code not being delivered with the regular distro cadence.
[16:48] <infinity> slangasek: And I still don't buy the "Canonical upstreams are unique snowflakes wrt CI" argument.  Saying it doesn't make it true.
[16:49] <slangasek> I didn't say they were unique snowflakes
[16:49] <slangasek> what I'm saying is that if there are other upstreams with strong CI that are worth our effort to develop exceptions for, I would be ok with that
[16:50] <infinity> So, you'd be happy with new systemd upstream versions breaking freezes?
[16:54] <slangasek> I'm not sure I would consider systemd upstream's CI "strong", the coverage might be a bit weak
[16:55] <slangasek> I do actually in principle prefer having that package in a state that we can rely on the CI instead of constantly worrying about what may have broken with a package update
[17:01] -queuebot:#ubuntu-release- Unapproved: neutron (zesty-proposed/main) [2:10.0.0-0ubuntu3 => 2:10.0.0-0ubuntu4] (openstack, ubuntu-server)
[17:09] -queuebot:#ubuntu-release- Unapproved: linux-signed (zesty-proposed/main) [4.10.0-14.16 => 4.10.0-15.17] (core, kernel) (sync)
[17:09] -queuebot:#ubuntu-release- Unapproved: linux (zesty-proposed/main) [4.10.0-14.16 => 4.10.0-15.17] (core, kernel) (sync)
[17:10] -queuebot:#ubuntu-release- Unapproved: linux-meta (zesty-proposed/main) [<IP_ADDRESS>.16 => <IP_ADDRESS>.17] (core, kernel) (sync)
[17:11] <infinity> rtg: Aww, crap.  Did my request just miss a new upload? :P
[17:11] <infinity> Oh well.
[17:11] -queuebot:#ubuntu-release- Unapproved: neutron-lbaas (zesty-proposed/universe) [2:10.0.0-0ubuntu1 => 2:10.0.0-0ubuntu2] (openstack)
[17:11] <rtg> infinity, well, -15 was already built in the PPA. It'll show up in -16
[17:12] <infinity> rtg: Off-by-1 error?  That's 14.
[17:12] <rtg> infinity, I just promoted -15 to -proposed
[17:12] <infinity> rtg: Oh, off-by-dumb error, I was reading the left side of queuebot's messages. ;)
[17:13] <rtg> infinity, your patch will make kernel freeze (in -16)
[17:13] <infinity> rtg: Ta.  It's currently making my tools lie, so I'm hoping to see that clear up.
[17:20] <nacc> infinity: would you be willing to process the src:vm-builder removal for 17.04? I think it would also require removing src:sandbox-upgrader and I'm not sure if the latter is used by the release team or not (i'm assuming not given that it's in universe)
[17:21] <nacc> infinity: LP: #1618899
[17:23] <infinity> rtg: Due to powerpc removal, the config/ changes are unreviewable (as expected).  Can you swear on a stack of bibles that nothing actually changed beyond "remove powerpc && updateconfigs"?
[17:25] <infinity> Oh, I guess I could review the final configs from the binaries instead.  I might do that to be paranoid.
[17:45] -queuebot:#ubuntu-release- Unapproved: munin (trusty-proposed/main) [2.0.19-3ubuntu0.3 => 2.0.19-3ubuntu0.4] (ubuntu-server)
[17:48] <rbalint> is there anything to be done for LP: #1672941 ?
[17:54] -queuebot:#ubuntu-release- Unapproved: stress-ng (zesty-proposed/universe) [0.07.26-1 => 0.07.27-1] (no packageset) (sync)
[17:55] -queuebot:#ubuntu-release- Unapproved: accepted stress-ng [sync] (zesty-proposed) [0.07.27-1]
[18:00] <rtg> infinity, only one config change other then powerpc, "UBUNTU: [Config] CONFIG_PINCTRL_GEMINILAKE=m"
[18:02] -queuebot:#ubuntu-release- Unapproved: neutron (xenial-proposed/main) [2:8.4.0-0ubuntu1 => 2:8.4.0-0ubuntu2] (openstack, ubuntu-server)
[18:04] -queuebot:#ubuntu-release- Unapproved: neutron (yakkety-proposed/main) [2:9.2.0-0ubuntu1 => 2:9.2.0-0ubuntu2] (openstack, ubuntu-server)
[18:06] <infinity> rtg: Kay, I'm diffing config-$(uname -r) from the binaries to confirm.
[18:29] -queuebot:#ubuntu-release- Unapproved: mate-desktop (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.0-0ubuntu2] (ubuntu-mate)
[18:31] -queuebot:#ubuntu-release- Unapproved: neutron-lbaas (xenial-proposed/main) [2:8.3.0-0ubuntu2 => 2:8.3.0-0ubuntu3] (openstack, ubuntu-server)
[18:31] -queuebot:#ubuntu-release- Unapproved: mate-settings-daemon (zesty-proposed/universe) [1.18.0-0ubuntu1 => 1.18.0-0ubuntu2] (ubuntu-mate)
[18:44] <tjaalton> i've uploaded xorg-server update to zesty, it was acked by Laney
[18:44] <mapreri> http://people.canonical.com/~ubuntu-archive/transitions/html/html/boost1.62.html
[18:44] <mapreri> this was last generated the 21st.  What happened?
[18:53] <barry> any thoughts on what we should do about emacs25.1+1-3ubuntu3?  It's been held up for several weeks due to failing/crashing tests on arm64  all other arches are fine.
[18:55] <nacc> barry: dannf has been looking into it
[18:55] <nacc> barry: but it's not easily reproducible, unfortunately
[18:55] <dannf> yeah, i haven't been able to reproduce it all for weeks now
[18:55] <nacc> barry: and it appears that it may have been happening for some time
[18:56] <barry> nacc, dannf thanks for looking into it.  have either of you looked to see if upstream has a bug on that?  i could look if you haven't yet.
[18:57] <dannf> barry: i did at the time and didn't see one. i also tried to reproduce w/ all usptream code back when i could reproduce it, and i couldn't break upstream
[18:58] <nacc> barry: i've not done any digging beyond what dannf has done -- i just have packages blocked by it :)
[18:58] <barry> dannf: that's interesting.  so perhaps it's a debian or ubuntu delta?
[18:58] <barry> nacc: :)
[18:59] <dannf> barry: my hope was that i could reproduce it in debian and get a bug filed there - iirc, the build failure is correlated with the REL_ALLOC=no change in debian
[18:59] <barry> i don't see anything in a quick search of gmame.emacs.bugs
[19:02] <barry> dannf: gotcha.  well, if i can help in any way, please do ping.  i don't have direct access to arm64 h/w tho.
[19:03] <dannf> barry: there's a canonical porterbox, but when i could reproduce it, it was only in a vm
[19:04] <barry> dannf: yep
[19:04] <dannf> barry: i'm sure we could provide you with hw access though
[19:04] <barry> dannf: that would be great
[19:07] <dannf> doko: is the mcdivitt you have deployed from our maas shareable?
[19:42] -queuebot:#ubuntu-release- Unapproved: rejected xorg-server [source] (zesty-proposed) [2:1.19.3-1ubuntu1]
[19:53] -queuebot:#ubuntu-release- Unapproved: accepted linux [sync] (zesty-proposed) [4.10.0-15.17]
[19:55] -queuebot:#ubuntu-release- Unapproved: accepted mate-desktop [source] (zesty-proposed) [1.18.0-0ubuntu2]
[19:55] -queuebot:#ubuntu-release- Unapproved: accepted neutron-lbaas [source] (zesty-proposed) [2:10.0.0-0ubuntu2]
[19:55] -queuebot:#ubuntu-release- Unapproved: accepted mate-settings-daemon [source] (zesty-proposed) [1.18.0-0ubuntu2]
[19:58] -queuebot:#ubuntu-release- Unapproved: accepted chrome-gnome-shell [source] (zesty-proposed) [8.2-0ubuntu2]
[19:58] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (zesty-proposed) [2:10.0.0-0ubuntu4]
[20:06] -queuebot:#ubuntu-release- Unapproved: accepted linux-meta [sync] (zesty-proposed) [<IP_ADDRESS>.17]
[20:06] -queuebot:#ubuntu-release- Unapproved: accepted linux-signed [sync] (zesty-proposed) [4.10.0-15.17]
[20:12] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (zesty-proposed/main) [4.10.0-15.17] (core, kernel)
[20:19] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (zesty-proposed) [4.10.0-15.17]
[20:19] -queuebot:#ubuntu-release- New: accepted nama [sync] (zesty-proposed) [1.208-1]
[20:19] -queuebot:#ubuntu-release- New: accepted sdpb [sync] (zesty-proposed) [1.0-3]
[20:19] <rbalint> barry: you probably also saw in #842852 that emacs25.1+1-3 seems to fix crashes on amd64
[20:21] <rbalint> barry: letting it migrate manually seems to be a better state for zesty, maybe we hit a VM bug on arm64?
[20:22] <infinity> Letting it migrate "manually" breaks a ton of rdeps.
[20:22] -queuebot:#ubuntu-release- New binary: sdpb [ppc64el] (zesty-proposed/none) [1.0-3] (no packageset)
[20:22] -queuebot:#ubuntu-release- New binary: sdpb [s390x] (zesty-proposed/none) [1.0-3] (no packageset)
[20:22] -queuebot:#ubuntu-release- Packageset: 70 entries have been added or removed
[20:22] <infinity> emacs isn't exactly a leaf package.
[20:23] -queuebot:#ubuntu-release- New binary: sdpb [arm64] (zesty-proposed/none) [1.0-3] (no packageset)
[20:23] -queuebot:#ubuntu-release- New binary: sdpb [i386] (zesty-proposed/none) [1.0-3] (no packageset)
[20:23] <infinity> As much as I wish it were, so I could remove it from the archive and tell barry to just snap it instead. :P
[20:24] -queuebot:#ubuntu-release- New binary: sdpb [amd64] (zesty-proposed/universe) [1.0-3] (no packageset)
[20:24] -queuebot:#ubuntu-release- New binary: sdpb [armhf] (zesty-proposed/universe) [1.0-3] (no packageset)
[20:24] <barry> >:-|
[20:25] <infinity> :)
[20:26]  * barry joins forces with rbalint
[20:31] <barry> rbalint: it looks like 842852 might already be fixed with -3 so we should try to get that through proposed first
[20:32] <infinity> Is it possible that it's the backtrace code that's choking, and fixing the warnings spit out in the build would paper over it?
[20:33] <infinity> Curiously, the Debian build doesn't throw warning on that same .el file (though it does on later ones).
[20:33] <infinity> That's a bit WTF.
[20:33] <barry> infinity: i was thinking something similar
[20:33] <barry> yeah
[20:38] <nacc> infinity: yeah, that's what made it a bit confusing
[20:38] <nacc> infinity: iirc, dannf's debugging
[20:39] <nacc> infinity: and we were trying to guess if the parallel=1 fix just papered over it before, but don't anymore (at least not consistently)
[20:39] <infinity> I also wonder if building on real hardware would fix it.
[20:39] <nacc> right
[20:39] <infinity> Cause we still have the power to do that.
[20:40] <infinity> Err, I might have the power to do that.  Maybe not.
[20:40] <nacc> i think that would be worth trying, if its possible :)
[20:42] <dannf> infinity: i think it is likely that real hw woudl fix it
[20:43] <infinity> That's disconcerting.
[20:43] <barry> indeed
[20:51] -queuebot:#ubuntu-release- Unapproved: xorg-server (zesty-proposed/main) [2:1.18.4-1ubuntu9 => 2:1.19.3-1ubuntu1] (desktop-core, xorg)
[20:53] <tjaalton> Laney: new attempt ^
[21:04] -queuebot:#ubuntu-release- Unapproved: julia (zesty-proposed/universe) [0.4.7-6 => 0.4.7-6ubuntu1] (no packageset)
[21:04] -queuebot:#ubuntu-release- Unapproved: accepted julia [source] (zesty-proposed) [0.4.7-6ubuntu1]
[21:25] -queuebot:#ubuntu-release- Unapproved: eject (zesty-proposed/main) [2.1.5+deb1+cvs20081104-13.1 => 2.1.5+deb1+cvs20081104-13.1ubuntu1] (core)
[21:32] -queuebot:#ubuntu-release- Unapproved: debian-installer (zesty-proposed/main) [20101020ubuntu500 => 20101020ubuntu501] (core)
[21:53] <tsimonq2> infinity: Is there any chance you would let a new Lubuntu slideshow package in to Zesty within the next... idk... week? that would fix some glaring problems
[21:54] <infinity> tsimonq2: Yup.
[21:54] <infinity> tsimonq2: Slideshows kinda get a pass for obvious reasons.  You can't take screenshots of your finished product until post-freeze, when it's finished.
[21:55] <infinity> cyphermox: Which reminds me, do we have a slideshow update for Ubuntu for zesty, or is that going to be the usual last-minute panic?
[21:56] <infinity> Wow, it's had three revisions in zesty!
[21:56] <infinity> A miracle.
[21:56] <tsimonq2> infinity: bug 1633148 and another bug which shows our incorrect website is in a screenshot (lubuntu.net which someone is squatting versus lubuntu.me, our new one)
[21:56] <tsimonq2> infinity: That would be the main fixes.
[21:56] <tsimonq2> infinity: But I'm glad for the ack, thank you. :)
[21:56] <infinity> tsimonq2: Yeah, all good.
[21:59] <tsimonq2> infinity: Yeah, gilir was having doubts about uploading a slideshow at this point because of FF, I'll let him know you gave it an ack ;)
[22:09] <tsimonq2> infinity: He still hasn't gotten back to me on lubuntu-next yet, fyi
[22:21] -queuebot:#ubuntu-release- Unapproved: runc (zesty-proposed/universe) [1.0.0~rc2-0ubuntu3 => 1.0.0~rc2+docker1.12.6-0ubuntu1] (no packageset)
[22:22] -queuebot:#ubuntu-release- Unapproved: accepted runc [source] (zesty-proposed) [1.0.0~rc2+docker1.12.6-0ubuntu1]
[22:24] <bdmurray> infinity: Are you doing any SRU work today? I've a couple of uploads I'd prefer not to self-approve.
[22:24] <infinity> bdmurray: rbasak was taking my day, but I can look at a couple, I suspect he's EOD by now.
[22:25] <bdmurray> infinity: its update-manager & update-notifier in T and X, somebody already approved Y.
[22:28] <infinity> bdmurray: Way to look out for 2038 in a punctual manner.
[22:31] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (trusty-proposed) [1:0.196.23]
[22:33] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (trusty-proposed) [0.154.1ubuntu3]
[22:34] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (xenial-proposed) [3.168.4]
[22:35] <infinity> bdmurray: Done.
[22:35] <bdmurray> infinity: thanks
[22:35] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (xenial-proposed) [1:16.04.6]
[22:36] -queuebot:#ubuntu-release- Unapproved: caja-dropbox (zesty-proposed/multiverse) [1.18.0-0ubuntu1 => 1.18.0-0ubuntu2] (ubuntu-mate)
[22:43] <cyphermox> infinity: it's still a panic
[22:43] <cyphermox> infinity: I'm mangling the translations right now, about to test it
[22:43] <infinity> cyphermox: I dunno, I see an upload 7 days ago that looks promising.
[22:43] <cyphermox> it looks promising except for all the places where it still says 16.10.
[22:44] <infinity> \o/
[23:28] -queuebot:#ubuntu-release- Unapproved: zfs-linux (zesty-proposed/main) [<IP_ADDRESS>-5ubuntu1 => <IP_ADDRESS>-5ubuntu2] (core)
[23:38] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (zesty-proposed) [<IP_ADDRESS>-5ubuntu2]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (zesty-proposed) [20101020ubuntu501]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted eject [source] (zesty-proposed) [2.1.5+deb1+cvs20081104-13.1ubuntu1]
[23:40] <infinity> flexiondotorg: That caja XDG_CURRENT_DESKTOP change will have a lot of knock-on effects.  Can you not just yell at dropbox instead?
[23:41] <infinity> flexiondotorg: Or is that somehow limited to only being in the environment when dealing with dropbox itself?
[23:42] <flexiondotorg> infinity So I discussed this with Laney earlier.
[23:43] <flexiondotorg> I've also prepare a debdiff for nautilus-dropbox, that checks if XDG_CURRENT_DESKTOP includes 'Unity' before exporting a modified environment.
[23:43] <flexiondotorg> I've tried, and am still trying, to get the attention of Dropbox.
[23:44] <infinity> flexiondotorg: Okay, maybe I'm mireading this.  Is the environment here limited to running some dropbox binary, and not being pushed back to the user's desktop environment?
[23:44] <flexiondotorg> The caja-dropbox changes is deliberately made this way so all DE can benefit.
[23:44] <flexiondotorg> LXDE, XFCE and MATE have been using my patched caja-dropbox for about a year now.
[23:44] <infinity> Question not being answered. :)
[23:45] <flexiondotorg> The environment change it just in the content of the Dropbox binary, not the whole session.
[23:45] <infinity> Right, okay.  Then it's fine.  I mean, super gross, but fine.
[23:45] <infinity> It was that context I was missing.
[23:45] <flexiondotorg> I was getting there :-)
[23:45] <infinity> Cause in the desktop session, claiming to be another DE ends up doing VERY WEIRD THINGS.
[23:45] <flexiondotorg> Indeed.
[23:46] <flexiondotorg> Laney asked me to fix nautilus-dropbox, the debdiff is ready and the approach used there was agreed with Laney.
[23:46] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1559249/comments/7
[23:46] <infinity> Oh, you no can upload that?
[23:46] <flexiondotorg> I have no super powers.
[23:46] <infinity> Slacker.
[23:47] <flexiondotorg> Says you. It's 00:45 here ;-)
[23:47] <flexiondotorg> infinity So if you can take a look at the debdiff for nautilus-dropbox that would be grand.
[23:48] <flexiondotorg> http://www.webupd8.org/2017/03/fix-dropbox-indicator-menu-not-working.html
[23:48] <infinity> flexiondotorg: So, I like the nautilus diff better, from my paranoid POV.
[23:48] <flexiondotorg> Yep.
[23:48] <infinity> flexiondotorg: As you're clearly only applying that env to the Popen.
[23:48] <infinity> flexiondotorg: Don't suppose that same clarity could be applied to the caja one?
[23:49] <flexiondotorg> Like I say, caja-cropbox is being used by XFCE and LXDE users too.
[23:49] <infinity> Yes...
[23:49] <infinity> I just mean, use the env.copy, then pass new_env trick.
[23:49] <infinity> Since changing os.env directly is less obviously not a leak.
[23:49] <flexiondotorg> And, in my testing, without passing a faux XDG_CURRENT_DESKOP recent Dropbox just doesn't work.
[23:50] <flexiondotorg> So use the say limit for just MATE in caja-dropbox?
[23:50] <infinity> I don't need you to explain the fix any more.  I get it.  I'm just asking it to look like the nautilus fix.
[23:51] <infinity> (minus the if)
[23:51] <flexiondotorg> Ah, right.
[23:51] <flexiondotorg> Can do.
[23:51] <infinity> ie: new_env = os.environment.copy(); new_env['XDG_CURRENT_DESKTOP'] = 'Unity'; sub.Popen(blah, env=new_env)
[23:52] <flexiondotorg> Wilco
[23:52] <infinity> Thanks.  I'm not an expert on python and os.env, but altering the environment directly when you really care about the env of a fork makes me twitch a bit.
[23:52] <infinity> So, better safe than lolz.
[23:53] <infinity> And I'll sponsor the nautilus fix for you, looks sane enough.
[23:53] <flexiondotorg> infinity Cheers. I'll let Laney know in the morning. I'll rework the caja-dropbox patch.
[23:54] <infinity> Ta.
[23:55] -queuebot:#ubuntu-release- Unapproved: rejected caja-dropbox [source] (zesty-proposed) [1.18.0-0ubuntu2]
[23:57] <infinity> flexiondotorg: Please use update-maintainer to update maintainers on Ubuntu changes, rather than setting the maintainer to yourself. ;)
[23:58] <infinity> flexiondotorg: Fixed that and the version number, and uploaded.
[23:58] <flexiondotorg> infinity OK. Noted. First time doing a change like that.
[23:58] -queuebot:#ubuntu-release- Unapproved: aptdaemon (yakkety-proposed/main) [1.1.1+bzr982-0ubuntu16.1 => 1.1.1+bzr982-0ubuntu16.2] (kubuntu, ubuntu-desktop)
[23:58] <flexiondotorg> infinity Thanks.
[23:59] -queuebot:#ubuntu-release- Unapproved: nautilus-dropbox (zesty-proposed/multiverse) [2015.10.28-1 => 2015.10.28-1ubuntu1] (xubuntu)


 Uhm... There's no Ubuntu 20.12 (re @bittin1: also the last Ubuntu regular Images for this year Ubuntu 20.12 will be out in around 4 hours)
 Each month's builds have a label assigned. For example, this month's builds are/will be labeled as 21.01. The label 20.12 was given to December 2020's (last month's) builds. (re @Maik_aD: Uhm... There's no Ubuntu 20.12)
[18:08] <Maik> @rs2009 seriously, in all these year i never heard of that.


[04:02] <xubuntu57w> Hello, I just installed xubuntu 18.04. It is using the onboard video in 1080p but the desktop is bigger than the screen. How do I fix that?
[04:04] <Kumool> Settings > Display xubuntu57w
[04:06] <Kumool> i have no clue either, SRC_PATH is supposed to be a variable, but instead it just says SRC_PATH?
[04:06] <Kumool> woops
[04:07] <xubuntu57w> Kumool: There isn't anything in there to tweak the display. I can change the resolution but it is already on the right resolution.
[04:07] <Kumool> ah, margins
[04:07] <xubuntu57w> Something like that. I'm missing the top 5-10% of the display
[04:07] <Kumool> desktop?
[04:08] <xubuntu57w> effectively my desktop is bigger than the screen
[04:08] <Kumool> desktop monitor i mean or laptop?
[04:09] <xubuntu57w> It's a Asrock Miniitx w/ an i3-8100
[04:09] <xubuntu57w> I'm displaying on a samsung HDTV
[04:09] <xubuntu57w> It is using the display port jack with a display port to hdmi cable.
[04:10] <Kumool> i have a clue but i doubt that's it, i'd suggest googling more or waiting for an answer :(
[04:11] <xubuntu57w> I've been trying to google but not getting much traction...
[04:12] <xubuntu57w> Lots of experience with Linux but first time using onboard video and miniitx.
[04:15] <Kumool> lets see... some solutions are... messing with the margin on Settings>workspaces; dealing with the actual monitor settings; actually configuring Xorg by hand
[04:15] <Kumool> or using another monitor
[04:16] <xubuntu57w> I'm thinking I may simply not have the right video drivers enabled. I'm used to Nvidia stuff...
[04:16] <Kumool> ah, that too
[04:17] <xubuntu57w> There is probably some kind of Intel video driver package or something... Just guessing...
[04:18] <Kumool> just use the OSS one
[09:38] <fran> hi!
[09:38] <diogenes_> hi
[09:38] <Guest87333> I need to upgrade xubuntu
[09:40] <Guest87333> What command do I need to acutalizar the distribution of Xubuntu?
[09:41] <diogenes_> Guest87333, read this: * appa<EMAIL_ADDRESS>has joined
[09:41] <diogenes_> oops
[09:41] <diogenes_> sorry
[09:41] <diogenes_> https://docs.xubuntu.org/current/user/C/migrating-upgrading.html
[09:41] <diogenes_> this ^^^
[09:44] <Guest87333> thanks, i think the problem is "autoremove" Thanks!! diogenes
[17:18] <xubuntu45w> Hello, recently I have installed xubuntu 18.04 bionic and I have a problem with LibreOffice. When open presentations created with my old ubuntu16 I cannot see the inserted *eps figure. I only see a square i the place that the figure was supposed to be, I can select it and resize it, but I cannot see the contect of the figure porperly. Any idea? I would like to fix it instead of coming back to an old version.
[19:20] <xubuntu53w> hey folks
[19:20] <xubuntu53w> good evening
[19:20] <xubuntu53w> got the weirdest behavior in my ubuntu
[19:20] <xubuntu53w> *xubuntu
[19:20] <xubuntu53w> after a few minutes(somtimes less) of usage, my mouse click actions change to something random
[19:21] <xubuntu53w> like, left click becomes "open thunar" or behaves like left click
[19:21] <xubuntu53w> and so on
[19:21] <xubuntu53w> xubuntu was installed recently
[19:21] <xubuntu53w> the problem happens even when using a external mouse
[23:12] <xubuntu04d> help
[23:13] <xubuntu04d> alguém ai ?
[23:15] <xubuntu04d> help, please
[23:16] <xubuntu04d> I me not search from story
[23:16] <xubuntu04d> I me not store
[23:16] <well_laid_lawn> !pt


[01:28] <Mark___> hi, there seems to be a corrupt pkg in the au apt archive... "Failed to fetch http://au.archive.ubuntu.com/ubuntu/pool/main/s/s2tc/libtxc-dxtn-s2tc0_0~git20131104-1.1_amd64.deb Hash Sum mismatch". It is okay if I update sources.list to use http://archive.ubuntu.com. Any suggestions on where to report this issue?
[02:03] <blahdeblah> Mark___: #ubuntu-mirrors for starters
[02:05] <blahdeblah> Mark___: just pasting your message there
[02:22] <Mark___> great, thanks for that!
[02:23] <blahdeblah> Mark___: Mirror admin is on it
[02:25] <Mark___> ok, cheers
[02:28] <blahdeblah> Mark___: anyway, make #ubuntu-mirrors your first port of call for that sort of thing in future - there's a listed Vanguard most of the time. :-)
[02:31] <Mark___> blahdeblah: ok, thanks again for your help


[09:18] <rmg51> Morning
[09:54] <JonathanD> Morning.
[12:19] <teddy-dbear> Morning peoples, dogs, turkeys and everything else
[13:53] <InHisName> Morning assorted crew
[14:34] <ChinnoDog> morning
[15:09] <lamella> morning
[15:17] <ChinnoDog> lamella?
[15:17] <lamella> post-op lamalex
[15:17] <ChinnoDog> That is what I was thinking.
[15:18] <ChinnoDog> lady_lamalex++