[22:34] <ikonia> telling people to blindly use upgrade-manager -d
[22:35] <OerHeks> first thing i read is a Warning: ...
[22:35] <ikonia> it's just not acceptable for providers to write this sort of document
[22:37] <FManTropyx> digital ocean is utter garbage
[22:37] <gtl> hmmm
[22:37] <tgm4883> in any case, case we get back to assisting the user?
[22:38] <gtl> i have server running there, so i thought they have the right tutorial
[22:38] <ikonia> I'm not going to support unacceptable supported boxes
[22:38] <ikonia> I suggest you talk to digitial ocean to support their guide and the situation it puts your host in
[22:38] <tgm4883> ikonia: that's fine, you don't have to...
[22:38] <ikonia> these provideers should not be able to write garbage info and expect the commuity to pick it up
[22:38] <ImperiusR4> hi
[22:39] <ImperiusR4> i am from argentina!
[22:39] <gtl> thanks ikonia - next time, i will go for other tutorial even being hosted there
[22:39] <gtl> i was just thinking that they have easy tutorials
[22:39] <ikonia> because they suck and are bad, so they are "easy"
[22:40] <ikonia> gtl: there is no tutorial - because ther is no upgrade path yet
[22:40] <gtl> hmm
[22:40] <ikonia> so any tutorial that says there is an upgrade path is bad/wrong
[22:40] <gtl> let me quickly write them then
[22:40] <guest-MVgE3r> hi
[22:40] <tgm4883> gtl: have you checked that other doc posted yet?
[22:41] <gtl> which doc tgm?
[22:41] <gtl> the one you posted?
[22:42] <tgm4883> gtl: the one Bashing-om posted
[22:44] <gtl> i only tried to diable the new naming scheme, i think it is not working
[22:49] <martin__> Hi all, is there anyone that can help me with fault finding a java/firefox issue i am having...
[22:50] <ikonia> martin__: just state your problem and people will help if they can
[22:50] <martin__> ok, so I seem to be having a few issues getting the java plugin to show up in firefox
[22:52] <martin__> I've got java showing up and have tried creating a symbolic link in /usr/lib/mozilla/plugins but when ever I restart the browser the plugin does not appear to be showing up
[22:59] <MrJones> hi
[22:59] <MrJones> service exim4 start   doesn't actually start exim4 for me
[22:59] <MrJones> how can I find out why? it says "Starting MTA ...done." but no exim4 is actually running afterwards
[23:00] <MrJones> nothing interesting in /var/log/exim4/mainlog either
[23:00] <MrJones> and since it doesn't tell me what command it actually ran, I don't know how to manually launch it to actually get some idea on what is happening
[23:00] <MrJones> is the stdout of the launch stored somewhere? is there something else logged somewhere by the service command which could help me?
[23:05] <sharkman8u> What are some opinions on Kdenlive?
[23:12] <GarettMcCarty> Can one make money developing open source software?
[23:15] <tgm4883> GarettMcCarty: OT for this channel, you might ask in #ubuntu-offtopic
[23:15] <Guest37382> yellow!
[23:18] <Guest37382> hello world!
[23:18] <Guest37382> i wish to chat
[23:18] <tgm4883> !OT | Guest37382
[23:25] <gtl> thanks tgm4883 . need to go sleeping now. good night
[23:25] <gtl> and iknoia too
[23:37] <Lost_> Marco
[23:43] <Guy1524> is it possible to ssh to host A and from the connection ssh to host B, if host B is not visible to the client
[23:46] <SchrodingersScat> Guy1524: if host b is behind a firewall then you'll maybe want to look at reverse tunnels
[23:50] <Guy1524> SchrodingersScat: k


[01:02] <zkriesse> akgraner: ping
[18:13] <akgraner> because I kept getting kicked out of the wiki then the etherpad decided not to work  - grrrr I started adding links for issue 207
[18:13] <akgraner> https://docs.google.com/Doc?docid=0AdKZelXU8Y2LZGNrcHRkYmhfODlkODNxNnRnZA&hl=en
[18:14] <akgraner> so if someone wants to start work on it you can
[18:14] <akgraner> I am almost finished with issue 206  - sigh
[18:14] <akgraner> but it will go out today  - thank goodness
[18:17]  * nigelb hugs akgraner
[18:18] <akgraner> nigelb, thanks :-)  I know this is a test...
[18:18] <akgraner> I just know it - someone has a since of humor
[18:19] <nigelb> test
[18:19] <nigelb> ?
[18:19] <akgraner> nigelb, you know something like "God is testing me" :-P
[18:48] <akgraner> hey can someone post this on the Fridge please - https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-August/000747.html
[18:48] <nhandler> akgraner: Yep
[18:48] <akgraner> nhandler, if you look at the last bug day announcement it should be easy to just copy and paste the new information
[18:49] <akgraner> nm  you know what you are doing :-)
[19:40] <akgraner> internalkernel, ping
[19:42] <akgraner> ok I have to add the in this issue and UWN will be ready
[19:42] <nhandler> Great job akgraner
[19:42] <akgraner> anyone want to volunteer to check it for spelling errors and hotlinks
[19:43] <akgraner> nhandler, thanks
[19:43]  * nhandler goes to post sabdfl's announcement on the fridge
[19:43] <akgraner> thanks
[19:44] <akgraner> I was going to ask but you beat me too it
[19:50] <nhandler> Story is up. I also added a new category forit
[19:51] <akgraner> thanks!
[19:51] <akgraner> you rock!
[21:02] <akgraner> Finally!
[21:02] <akgraner> The new edition of the Ubuntu Weekly Newsletter is now available here:
[21:02] <akgraner> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue206
[21:02] <zkriesse> nice
[21:03] <akgraner> it's still too long but since 207 is started on the googledoc hopefully we can get ahead of the game this week
[21:04] <akgraner> who is going to grab which sections?
[21:04] <akgraner> just so I can check with you all during the week and know how to plan accordingly
[21:04] <akgraner> the summaries only need to be a couple sentences
[21:05] <akgraner> and you can use the RSS feed summaries if they make sense to include them
[21:14] <Pendulum> akgraner: awesome job!
[21:14] <akgraner> Pendulum, thank you  - and thank you for all your help!
[21:15] <Pendulum> you're welcome :)
[21:15] <nigelb> I've grabbed loco news for 207.
[21:57] <scott_ev> akgraner: I'll have upcoming meetings & events done early
[21:57] <akgraner> scott_ev, thanks
[21:57] <scott_ev> np
[21:57] <akgraner> also leave the LoCo events
[21:57] <akgraner> :-)
[21:57] <scott_ev> huh?
[21:58] <akgraner> leave off the LoCo Team meetings
[21:59] <akgraner> scott_ev, you can't read my mind :-)
[21:59] <akgraner> we are getting ready to move those to another calendar this week  - so we can go live with the new Fridge site and all that good stuff
[22:04] <scott_ev> ah
[22:04] <scott_ev> I must miss out on a lot, I didn't know there was going to be a new fridge site
[22:10] <internalkernel> akgraner: ding...
[22:10] <akgraner> internalkernel, dong
[22:10] <internalkernel> hows it...
[22:10] <akgraner> internalkernel, can you take ownership of In the Press this week
[22:11] <akgraner> I've already started posting some things to the googledoc
[22:11] <akgraner> I need to update the wiki pages now and get things posted to the Forums and fridge
[22:11] <internalkernel> yeah, that should be doable...
[22:11] <akgraner> ok thanks  - I'll touch base again on Thursday to see how goes everything ok?
[22:11] <internalkernel> my life is still basically upside down, but more and more is comng together... I should have enough spare time to sift through my feeds
[22:12] <akgraner> holstein, can you look at the in other news this week
[22:12] <internalkernel> that sounds good, I'll probably need a nudge or perhaps a kick on thursday
[22:12] <akgraner> Pendulum, rocks the ITB sections
[22:13] <akgraner> highvoltage, can you do the Planet sections this week?
[22:13] <akgraner> I'll update the wiki's now so everyone can see it coming together for next week
[22:17] <Pendulum> akgraner: do you have a list of places you tend to check for ITB? can you e-mail it to me if you do?
[22:17] <Pendulum> (I have a few in my feed reader, but not a huge number)
[22:19] <akgraner> yep let me finish updating all this and I'll send them to you
[22:19] <akgraner> :-)
[22:26] <holstein> akgraner: im in
[22:26] <holstein> where is the 'working directory' ?
[22:26] <holstein> the ietherpad?
[22:27] <holstein> http://ietherpad.com/UWN
[22:27] <akgraner> googledoc  - I'll move everything I have so far over in just a few minutes - just posted issue 206 to the forums
[22:27] <holstein> OK
[22:27] <holstein> https://docs.google.com/Doc?docid=0AdKZelXU8Y2LZGNrcHRkYmhfODlkODNxNnRnZA&hl=en
[22:28]  * holstein is on it :)
[22:42] <highvoltage> akgraner: yep yep!
[22:42] <akgraner> thanks y'all
[22:43] <highvoltage> akgraner: could you start the 207 page so long? do you have a template you usually copy and paste it from? I could do that too I guess
[22:43] <akgraner> highvoltage, yep one sec
[22:43] <akgraner> you'll see it in just a second
[22:44] <highvoltage> ok great
[23:00] <akgraner> ok links and summaries have been added to Issue 207 on the googledoc, the ietherpad and the wiki
[23:00] <akgraner> hope that gives everyone an easy start


[00:02] -queuebot:#lubuntu-devel- Unapproved: accepted lubuntu-meta [source] (noble-proposed) [24.04.10]
[00:07] -queuebot:#lubuntu-devel- Unapproved: accepted lubuntu-default-settings [source] (noble-proposed) [24.04.10]
[20:01] <wxl> arraybolt3: fyi matrix is dead again
[20:02] <arraybolt3> ah fun
[22:38] -queuebot:#lubuntu-devel- Unapproved: lubuntu-artwork (noble-proposed/universe) [24.04.4 => 24.04.5] (lubuntu)


 I forgot to give them back to you yesterday, sorry!
[01:59] <willcooke> :D
[01:59] <kenvandine> willcooke: good
[01:59] <kenvandine> opening up stable/ubuntu-19.10 channels for arm64 snaps for xnox :)
[02:00] <kenvandine> he's building images
[05:57] <pieq> jibel, willcooke : Tonghua Night Market. It's all along the Linjiang street, so the easiest way to get there is: https://frama.link/adBP0wkA
[06:04] <jibel> pieq, thanks
[06:35] <oSoMoN> good morning desktoppers
[06:35] <willcooke> hi oSoMoN
[06:35] <oSoMoN> hey willcooke
[06:36] <didrocks> hey oSoMoN, willcooke
[06:36] <oSoMoN> everything alright in the East ?
[06:36] <oSoMoN> salut didrocks
[06:37] <willcooke> hey didrocks
[06:37] <willcooke> all good here!
[06:38] <willcooke> jibel is looking for more scary things to eat
[06:38] <oSoMoN> :)
[06:40] <jibel> willcooke, https://iot.eclipse.org/resources/iot-developer-survey/iot-developer-survey-2019.pdf
[06:41] <willcooke> thx
[07:09] <mpt> Laney, update-manager has explicitly said “I don’t want to be focused” when it opens automatically.  Last year it was a Thursday
[08:32] <willcooke> :dd
[08:32] <willcooke> ;DD
[08:33] <oSoMoN> :)
[08:42] <GunnarHj> Good morning seb128, Laney! Do any of you have time to review the MP:s at bug #1823778?
[08:42] <ubot5`> bug 1823778 in gnome-control-center (Ubuntu Bionic) "Unable to set Serbian as Language" [High,In progress] https://launchpad.net/bugs/1823778
[08:45] <Laney> AHHHHHHHHHHHHHHHHHHHH thanks, will try to soon
[08:47] <seb128> hey GunnarHj
[08:47] <seb128> thx laney
[08:49] <GunnarHj> Laney: Ok.
[10:43] <xnox> didrocks, jibel - can i ask you questions about canary images? =)
[10:43] <xnox> i see that livefs builds complete, but then nothing gets published.
[10:44] <xnox> i.e. http://cdimage.ubuntu.com/daily-live/20190425.1/
[10:45] <xnox> in http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu/eoan/daily-live-20190425.1.log
[10:45] <xnox> it looks like it is trying things, but then does nothing useful
[10:45] <xnox> [10:45] <xnox> Thu Apr 25 08:17:17 UTC 2019
[10:45] <xnox> No desktop image for amd64!
[10:45] <xnox> No images produced!
[10:45] <xnox> this in turn breaks the CI of regular Ubuntu desktop images. As utah, can't handle empty 25.1 publication
[10:46] <xnox> can the canary images, somehow not publish into the regular ubuntu desktop location? and not polute the /daily-images location?
[10:48] <xnox> oh it looks like today CI managed to catch 25 build of desktop https://platform-qa-jenkins.ubuntu.com/view/Eoan/
[10:48] <xnox> so testing is all good.
[10:48] <xnox> still interested in canary images, and whether you expect ubuntu-cdimage to actually publish something. Or are you only interested in cronned livefs builds at the moment?
[10:55] <Laney> there was an MR
[10:55] <Laney> sil2100 was looking at it and needed to discuss it with vorlon or something
[10:55] <Laney> IIRC
[10:59] <sil2100> Yeah, let me poke Steve about that
[10:59] <sil2100> I'd like his input on how we should proceed
[10:59]  * sil2100 writes that down not to forget
[11:01] <xnox> ah, i see.
[11:01] <xnox> right, cause i looked around on what's deployed, and it didn't look like there were enough pieces to assemble and publish canary
[11:02] <Laney> https://code.launchpad.net/~jibel/ubuntu-cdimage/support_ubuntu_subproject/+merge/365598
[11:03] <Laney> Trevinho: if you want to rebase your mutter/shell and prepare SRU bugs I can upload those
[11:03] <sil2100> xnox: yeah, it's not ready yet, it's running as a subproject now so each build of canary is separate from the ubuntu desktop one so it results in an unnecessary publisher bump
[11:03] <sil2100> xnox: we could just enable it to publish, but I'm not sure it that's the right way to go
[11:04] <xnox> ack
[11:04] <sil2100> xnox: anyway, subprojects were never really supposed to be used for things like these
[11:04] <xnox> yeah
[11:04] <xnox> sil2100, wait till i ask for arm64 desktop images ;-)
[11:04] <sil2100> xnox: if it's a separate image, it should be a separate project most probably ;p
[11:04] <sil2100> eeek
[11:05] <xnox> sil2100, or like a subarch.
[11:05] <xnox> sil2100, canary could be a subarch
[11:06] <sil2100> Yeah, or that
[11:06] <sil2100> Would be weird but yeah
[11:06] <sil2100> At least it would 'work correctly' ;)
[11:32] <andyrock> Laney: hi! I took a look at https://errors.ubuntu.com/problem/824c3c31a0b9558002bb74699b5542c32e7396ad
[11:32] <andyrock> can it be that during the upgrade from cosmic to disco tracker-store is started before the glib schemas are compiled/installed
[11:33] <andyrock> ?
[11:33] <Laney> hi andyrock
[11:34] <Laney> if something runs it, like via d-bus activation, I guess that could happen
[11:34] <andyrock> and how can we prevent it? like masking the systemd unit until the schemas are installed
[11:34] <Laney> it's not considered 'installed' by dpkg until the schemas are compiled
[11:34] <Laney> but the files are there on the system
[11:34] <Laney> so you can run it
[11:34] <Laney> any idea what that thing is?
[11:35] <andyrock> nope, maybe nautilus but I'm not sure
[11:36] <andyrock> would it be possible to mask tracker-store.service until the schemas are compiled? Some magic trick in debian/rules
[11:39] <Laney> not that I know of
[11:44]  * Laney doesn't have a cool idea right now
[11:47] <Laney> it's pretty far from the only thing that could go wrong if you use your system while we're in the middle of performing open heart surgery on it
[11:56] <andyrock> yeah, it's not a big issue because it should be a one time issue but we're going to hit the problem again when people will upgrade from bionic to ff
[11:56] <andyrock> if the cause is really this
[12:17] <didrocks> xnox: we asked sil2100 to publish the image, we have a PR which is needed, but maybe not enough and unreviewed for some weeks (the one Laney pointed out). Last I heard it's in foundation's hand :)
[12:17] <didrocks> so keep us posted, we would really like to have that image published
[12:28] <xnox> =)
[12:28] <xnox> har har
[12:32] <sil2100> didrocks: I disagree that it's unreviewed!
[12:33] <sil2100> didrocks: but yes, it is not enough
[12:33] <sil2100> ;)
[12:37] <didrocks> sil2100: I think this is the exact case subprojects would have some meaning, if we don't want to use them, they should be removed from cdimage and such :)
[12:38] <didrocks> sil2100: but I still think that the argument is passed to ubuntu-cdimage, to be ignored (this is why the tests were passing), which is a weird implementation IMHO :p
[12:38] <didrocks> still, there is no course of action hence the "unreviewed" (by the architect)
[12:39] <didrocks> (I really think that using another project for this, like it used to be for ubuntu-server-live is a hack)
[12:45] <sil2100> didrocks: yeah, actually this was my original understanding of how subprojects should work, but then it turned out it's not - and that actually it's best not to use subprojects if not needed ;p
[12:46] <sil2100> didrocks: I guess as per Dimitri's proposition, currently we *could* use subarchs for this, even though conceptually that's not the best fi
[12:46] <sil2100> *fit
[12:47] <didrocks> sil2100: yeah, don't really like this proposal as well (more hacks on hacks :p) but if subproject is going to be decommissioned, turning this in a real project is fine as well
[12:47] <didrocks> sil2100: I'll let you follow up on this. Hoping that next week we can have daily published images :)
[14:08] <xnox> is wubi and lupin-casper dead?
[14:10] <xnox> omg it's still going strong https://github.com/hakuna-m/wubiuefi/releases
[15:16] <Trevinho> sil2100: hey, would you add eoan to bileto?
[15:17] <sil2100> Trevinho: sure o/
[15:17] <sil2100> Wanted to do that yesterday but then... I forgot
[15:17] <sil2100> ;(
[15:17] <sil2100> Let me do that after the weekly meeting
[16:59] <sil2100> Trevinho: eoan's in Bileto now o/
[18:45] <Trevinho> sil2100: thanks :)
[18:45] <Trevinho> Laney: I will, but in hols now so, I'll do it next week at this point... I guess there's not too much hurry for it
[18:46] <Laney> sure, not from me anyway


[08:31] <Laney> slangasek: I added linux to long_tests for lxd; the latest results don't look like a timeout to me now. (You can see --timeout-test=40000 at the top of log output now.)
[08:52] -queuebot:#ubuntu-release- New: accepted ahven [amd64] (artful-proposed) [2.6-1.2]
[08:52] -queuebot:#ubuntu-release- New: accepted ahven [armhf] (artful-proposed) [2.6-1.2]
[08:52] -queuebot:#ubuntu-release- New: accepted ahven [ppc64el] (artful-proposed) [2.6-1.2]
[08:52] -queuebot:#ubuntu-release- New: accepted ahven [arm64] (artful-proposed) [2.6-1.2]
[08:52] -queuebot:#ubuntu-release- New: accepted ahven [s390x] (artful-proposed) [2.6-1.2]
[08:52] -queuebot:#ubuntu-release- New: accepted ahven [i386] (artful-proposed) [2.6-1.2]
[08:53] -queuebot:#ubuntu-release- New: accepted diceware [amd64] (artful-proposed) [0.9.1-4.1]
[08:53] -queuebot:#ubuntu-release- New: accepted importmagic [amd64] (artful-proposed) [0.1.7-1]
[08:53] -queuebot:#ubuntu-release- New: accepted kexi [arm64] (artful-proposed) [1:3.0.2-1]
[08:53] -queuebot:#ubuntu-release- New: accepted kexi [s390x] (artful-proposed) [1:3.0.2-1]
[08:53] -queuebot:#ubuntu-release- New: accepted kexi [armhf] (artful-proposed) [1:3.0.2-1]
[09:06] -queuebot:#ubuntu-release- Unapproved: pcl (xenial-proposed/universe) [1.7.2-14ubuntu<IP_ADDRESS> => 1.7.2-14ubuntu<IP_ADDRESS>] (no packageset)
[09:22] -queuebot:#ubuntu-release- New binary: gsl [s390x] (artful-proposed/main) [2.4+dfsg-6] (kubuntu, ubuntu-desktop)
[09:23] -queuebot:#ubuntu-release- New binary: gsl [ppc64el] (artful-proposed/main) [2.4+dfsg-6] (kubuntu, ubuntu-desktop)
[09:27] -queuebot:#ubuntu-release- New binary: gsl [i386] (artful-proposed/main) [2.4+dfsg-6] (kubuntu, ubuntu-desktop)
[09:28] -queuebot:#ubuntu-release- New binary: gsl [amd64] (artful-proposed/main) [2.4+dfsg-6] (kubuntu, ubuntu-desktop)
[09:30] -queuebot:#ubuntu-release- New binary: gsl [arm64] (artful-proposed/main) [2.4+dfsg-6] (kubuntu, ubuntu-desktop)
[09:33] <LocutusOfBorg> good morning, I would like to see curl migrate, and in order to see it I think I need to hint two tests, htslib/i386 and stenographer/ppc64el
[09:33] <LocutusOfBorg> both of them are regressed in release already, and curl has security fixes in
[09:36] -queuebot:#ubuntu-release- New binary: gsl [armhf] (artful-proposed/main) [2.4+dfsg-6] (kubuntu, ubuntu-desktop)
[09:38] -queuebot:#ubuntu-release- New binary: asterisk [ppc64el] (artful-proposed/universe) [1:13.17.0~dfsg-2ubuntu1] (no packageset)
[09:39] -queuebot:#ubuntu-release- New binary: asterisk [amd64] (artful-proposed/universe) [1:13.17.0~dfsg-2ubuntu1] (no packageset)
[09:40] -queuebot:#ubuntu-release- New binary: asterisk [i386] (artful-proposed/universe) [1:13.17.0~dfsg-2ubuntu1] (no packageset)
[09:41] -queuebot:#ubuntu-release- New binary: asterisk [s390x] (artful-proposed/universe) [1:13.17.0~dfsg-2ubuntu1] (no packageset)
[09:43] -queuebot:#ubuntu-release- New binary: asterisk [arm64] (artful-proposed/universe) [1:13.17.0~dfsg-2ubuntu1] (no packageset)
[09:44] -queuebot:#ubuntu-release- New binary: asterisk [armhf] (artful-proposed/universe) [1:13.17.0~dfsg-2ubuntu1] (no packageset)
[09:52] -queuebot:#ubuntu-release- New source: rdma-core (artful-proposed/primary) [15~rc1+git20170821-0ubuntu1]
[09:59] -queuebot:#ubuntu-release- New binary: gjs [amd64] (artful-proposed/main) [1.49.90-0ubuntu1] (desktop-extra, mozilla, ubuntu-desktop)
[09:59] -queuebot:#ubuntu-release- New binary: gjs [ppc64el] (artful-proposed/main) [1.49.90-0ubuntu1] (desktop-extra, mozilla, ubuntu-desktop)
[09:59] -queuebot:#ubuntu-release- New binary: gjs [i386] (artful-proposed/main) [1.49.90-0ubuntu1] (desktop-extra, mozilla, ubuntu-desktop)
[10:01] -queuebot:#ubuntu-release- New binary: gjs [arm64] (artful-proposed/main) [1.49.90-0ubuntu1] (desktop-extra, mozilla, ubuntu-desktop)
[10:01] -queuebot:#ubuntu-release- New binary: gjs [armhf] (artful-proposed/main) [1.49.90-0ubuntu1] (desktop-extra, mozilla, ubuntu-desktop)
[10:06] -queuebot:#ubuntu-release- New binary: libktorrent [ppc64el] (artful-proposed/universe) [2.0.90-0ubuntu1] (kubuntu)
[10:08] -queuebot:#ubuntu-release- New binary: libktorrent [amd64] (artful-proposed/universe) [2.0.90-0ubuntu1] (kubuntu)
[10:08] -queuebot:#ubuntu-release- New binary: libktorrent [s390x] (artful-proposed/universe) [2.0.90-0ubuntu1] (kubuntu)
[10:10] -queuebot:#ubuntu-release- New binary: libktorrent [i386] (artful-proposed/universe) [2.0.90-0ubuntu1] (kubuntu)
[10:11] -queuebot:#ubuntu-release- New binary: libktorrent [arm64] (artful-proposed/universe) [2.0.90-0ubuntu1] (kubuntu)
[10:11] -queuebot:#ubuntu-release- New binary: libktorrent [armhf] (artful-proposed/universe) [2.0.90-0ubuntu1] (kubuntu)
[10:12] -queuebot:#ubuntu-release- New: accepted asterisk [amd64] (artful-proposed) [1:13.17.0~dfsg-2ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted asterisk [armhf] (artful-proposed) [1:13.17.0~dfsg-2ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted asterisk [ppc64el] (artful-proposed) [1:13.17.0~dfsg-2ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted gsl [amd64] (artful-proposed) [2.4+dfsg-6]
[10:12] -queuebot:#ubuntu-release- New: accepted gsl [armhf] (artful-proposed) [2.4+dfsg-6]
[10:12] -queuebot:#ubuntu-release- New: accepted gsl [ppc64el] (artful-proposed) [2.4+dfsg-6]
[10:12] -queuebot:#ubuntu-release- New: accepted asterisk [arm64] (artful-proposed) [1:13.17.0~dfsg-2ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted asterisk [s390x] (artful-proposed) [1:13.17.0~dfsg-2ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted gsl [i386] (artful-proposed) [2.4+dfsg-6]
[10:12] -queuebot:#ubuntu-release- New: accepted asterisk [i386] (artful-proposed) [1:13.17.0~dfsg-2ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted gsl [s390x] (artful-proposed) [2.4+dfsg-6]
[10:12] -queuebot:#ubuntu-release- New: accepted gsl [arm64] (artful-proposed) [2.4+dfsg-6]
[10:12] -queuebot:#ubuntu-release- New: accepted libktorrent [amd64] (artful-proposed) [2.0.90-0ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted libktorrent [armhf] (artful-proposed) [2.0.90-0ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted libktorrent [ppc64el] (artful-proposed) [2.0.90-0ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted libktorrent [arm64] (artful-proposed) [2.0.90-0ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted libktorrent [s390x] (artful-proposed) [2.0.90-0ubuntu1]
[10:12] -queuebot:#ubuntu-release- New: accepted libktorrent [i386] (artful-proposed) [2.0.90-0ubuntu1]
[11:58] <LocutusOfBorg> apw, pleeeeeeeease hint virtualbox testsuite, because of virtualbox/kernel merges
[11:58] <LocutusOfBorg> Error! Module version 5.1.26_Ubuntu for vboxguest.ko
[11:58] <LocutusOfBorg> is not newer than what is already found in kernel 4.12.0-11-generic (5.1.26_Ubuntu).
[11:58] <LocutusOfBorg> You may override by specifying --force.
[11:58] <LocutusOfBorg> (or fix testsuite, even better :p )
[11:59]  * LocutusOfBorg grabs src:linux
[12:02] <LocutusOfBorg> mmm I don't understand where the test is located
[12:56] <apw> the test is located as part of dkms as an autodep8 test
[13:03] <apw> and that is a valid failure mode for that test in that one case
[13:13] <apw> LocutusOfBorg, hinted
[13:27] <LocutusOfBorg> thanks <3
[13:48] -queuebot:#ubuntu-release- New: accepted gjs [amd64] (artful-proposed) [1.49.90-0ubuntu1]
[13:48] -queuebot:#ubuntu-release- New: accepted gjs [armhf] (artful-proposed) [1.49.90-0ubuntu1]
[13:48] -queuebot:#ubuntu-release- New: accepted gjs [ppc64el] (artful-proposed) [1.49.90-0ubuntu1]
[13:48] -queuebot:#ubuntu-release- New: accepted gjs [arm64] (artful-proposed) [1.49.90-0ubuntu1]
[13:48] -queuebot:#ubuntu-release- New: accepted gjs [i386] (artful-proposed) [1.49.90-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New binary: budgie-desktop [i386] (artful-proposed/universe) [10.4-0ubuntu1] (no packageset)
[14:04] -queuebot:#ubuntu-release- New binary: budgie-desktop [ppc64el] (artful-proposed/universe) [10.4-0ubuntu1] (no packageset)
[14:05] -queuebot:#ubuntu-release- New binary: budgie-desktop [amd64] (artful-proposed/universe) [10.4-0ubuntu1] (no packageset)
[14:07] -queuebot:#ubuntu-release- New binary: budgie-desktop [arm64] (artful-proposed/universe) [10.4-0ubuntu1] (no packageset)
[14:07] -queuebot:#ubuntu-release- New binary: budgie-desktop [armhf] (artful-proposed/universe) [10.4-0ubuntu1] (no packageset)
[14:08] -queuebot:#ubuntu-release- New binary: budgie-desktop [s390x] (artful-proposed/universe) [10.4-0ubuntu1] (no packageset)
[14:37] -queuebot:#ubuntu-release- Unapproved: binutils (xenial-proposed/main) [2.26.1-1ubuntu1~16.04.4 => 2.26.1-1ubuntu1~16.04.5] (core)
[15:38] -queuebot:#ubuntu-release- New binary: evolution [ppc64el] (artful-proposed/universe) [3.25.91-0ubuntu1] (ubuntukylin)
[15:43] -queuebot:#ubuntu-release- New binary: evolution [i386] (artful-proposed/universe) [3.25.91-0ubuntu1] (ubuntukylin)
[15:44] -queuebot:#ubuntu-release- New binary: evolution [s390x] (artful-proposed/universe) [3.25.91-0ubuntu1] (ubuntukylin)
[15:46] -queuebot:#ubuntu-release- New binary: evolution [amd64] (artful-proposed/universe) [3.25.91-0ubuntu1] (ubuntukylin)
[15:49] -queuebot:#ubuntu-release- New binary: evolution [arm64] (artful-proposed/universe) [3.25.91-0ubuntu1] (ubuntukylin)
[15:51] -queuebot:#ubuntu-release- New binary: evolution [armhf] (artful-proposed/universe) [3.25.91-0ubuntu1] (ubuntukylin)
[16:43] <bdmurray> slangasek: I feel like http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#update-notifier is incorrectly marked as a regression
[16:44] <bdmurray> The u-m autopkgtest passed with 16.04.9 but the failure here is with u-m 16.04.8 which is a version number < the one that passed.
[17:12] -queuebot:#ubuntu-release- New binary: netty-tcnative-1.1 [ppc64el] (artful-proposed/universe) [1.1.33.Fork26-2] (no packageset)
[17:12] -queuebot:#ubuntu-release- New binary: honeysql-clojure [amd64] (artful-proposed/universe) [0.8.2-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: clj-digest-clojure [amd64] (artful-proposed/universe) [1.4.5-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: clj-time-clojure [amd64] (artful-proposed/universe) [0.14.0-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: typesafe-config-clojure [amd64] (artful-proposed/universe) [0.1.5-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: beckon-clojure [amd64] (artful-proposed/universe) [0.1.1-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: netty-tcnative-1.1 [arm64] (artful-proposed/universe) [1.1.33.Fork26-2] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: netty-tcnative-1.1 [i386] (artful-proposed/universe) [1.1.33.Fork26-2] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: core-async-clojure [amd64] (artful-proposed/universe) [0.3.443-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: ring-codec-clojure [amd64] (artful-proposed/universe) [1.0.1-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: netty-tcnative-1.1 [armhf] (artful-proposed/universe) [1.1.33.Fork26-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: prismatic-schema-clojure [amd64] (artful-proposed/universe) [1.1.6-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: netty-tcnative-1.1 [amd64] (artful-proposed/universe) [1.1.33.Fork26-2] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: netty-tcnative-1.1 [s390x] (artful-proposed/universe) [1.1.33.Fork26-2] (no packageset)
[17:31] -queuebot:#ubuntu-release- Unapproved: backuppc (xenial-proposed/main) [3.3.1-2ubuntu3.2 => 3.3.1-2ubuntu3.3] (core)
[20:00] -queuebot:#ubuntu-release- New source: kdav (artful-proposed/primary) [17.04.3-0ubuntu1]
[20:52] <slangasek> bdmurray: yes, that is a bug in how britney is defining 'regression'.  Should be fixed, but I usually just work around it by re-triggering the test with both packages from -proposed
[20:52] <slangasek> bdmurray: (which I'm doing now for u-m + u-n)
[20:54] <slangasek> bdmurray: and one reason for doing this is that we make sure that, having just fixed the autopkgtest for update-manager, we aren't silently letting it regress again with update-notifier
[21:01] -queuebot:#ubuntu-release- New source: py3c (artful-proposed/primary) [0.8-1]
[21:05] -queuebot:#ubuntu-release- New: accepted netty-tcnative-1.1 [amd64] (artful-proposed) [1.1.33.Fork26-2]
[21:05] -queuebot:#ubuntu-release- New: accepted netty-tcnative-1.1 [armhf] (artful-proposed) [1.1.33.Fork26-2]
[21:05] -queuebot:#ubuntu-release- New: accepted netty-tcnative-1.1 [ppc64el] (artful-proposed) [1.1.33.Fork26-2]
[21:05] -queuebot:#ubuntu-release- New: accepted netty-tcnative-1.1 [arm64] (artful-proposed) [1.1.33.Fork26-2]
[21:05] -queuebot:#ubuntu-release- New: accepted netty-tcnative-1.1 [s390x] (artful-proposed) [1.1.33.Fork26-2]
[21:05] -queuebot:#ubuntu-release- New: accepted netty-tcnative-1.1 [i386] (artful-proposed) [1.1.33.Fork26-2]
[21:05] -queuebot:#ubuntu-release- New: accepted budgie-desktop [amd64] (artful-proposed) [10.4-0ubuntu1]
[21:06] -queuebot:#ubuntu-release- New: accepted budgie-desktop [armhf] (artful-proposed) [10.4-0ubuntu1]
[21:06] -queuebot:#ubuntu-release- New: accepted budgie-desktop [ppc64el] (artful-proposed) [10.4-0ubuntu1]
[21:06] -queuebot:#ubuntu-release- New: accepted budgie-desktop [arm64] (artful-proposed) [10.4-0ubuntu1]
[21:06] -queuebot:#ubuntu-release- New: accepted budgie-desktop [s390x] (artful-proposed) [10.4-0ubuntu1]
[21:06] -queuebot:#ubuntu-release- New: accepted budgie-desktop [i386] (artful-proposed) [10.4-0ubuntu1]
[21:07] -queuebot:#ubuntu-release- New: accepted evolution [amd64] (artful-proposed) [3.25.91-0ubuntu1]
[21:07] -queuebot:#ubuntu-release- New: accepted evolution [armhf] (artful-proposed) [3.25.91-0ubuntu1]
[21:07] -queuebot:#ubuntu-release- New: accepted evolution [ppc64el] (artful-proposed) [3.25.91-0ubuntu1]
[21:07] -queuebot:#ubuntu-release- New: accepted py3c [source] (artful-proposed) [0.8-1]
[21:07] -queuebot:#ubuntu-release- New: accepted evolution [arm64] (artful-proposed) [3.25.91-0ubuntu1]
[21:07] -queuebot:#ubuntu-release- New: accepted evolution [s390x] (artful-proposed) [3.25.91-0ubuntu1]
[21:07] -queuebot:#ubuntu-release- New: accepted evolution [i386] (artful-proposed) [3.25.91-0ubuntu1]
[21:07] -queuebot:#ubuntu-release- New: accepted beckon-clojure [amd64] (artful-proposed) [0.1.1-1]
[21:07] -queuebot:#ubuntu-release- New: accepted clj-time-clojure [amd64] (artful-proposed) [0.14.0-1]
[21:07] -queuebot:#ubuntu-release- New: accepted honeysql-clojure [amd64] (artful-proposed) [0.8.2-1]
[21:07] -queuebot:#ubuntu-release- New: accepted ring-codec-clojure [amd64] (artful-proposed) [1.0.1-1]
[21:07] -queuebot:#ubuntu-release- New: accepted clj-digest-clojure [amd64] (artful-proposed) [1.4.5-1]
[21:07] -queuebot:#ubuntu-release- New: accepted prismatic-schema-clojure [amd64] (artful-proposed) [1.1.6-1]
[21:07] -queuebot:#ubuntu-release- New: accepted core-async-clojure [amd64] (artful-proposed) [0.3.443-1]
[21:07] -queuebot:#ubuntu-release- New: accepted typesafe-config-clojure [amd64] (artful-proposed) [0.1.5-1]
[21:08] -queuebot:#ubuntu-release- New: accepted kdav [source] (artful-proposed) [17.04.3-0ubuntu1]
[21:09] -queuebot:#ubuntu-release- New binary: py3c [amd64] (artful-proposed/universe) [0.8-1] (no packageset)
[21:11] -queuebot:#ubuntu-release- New binary: kdav [ppc64el] (artful-proposed/universe) [17.04.3-0ubuntu1] (no packageset)
[21:11] -queuebot:#ubuntu-release- New: accepted py3c [amd64] (artful-proposed) [0.8-1]
[21:12] -queuebot:#ubuntu-release- New binary: kdav [i386] (artful-proposed/universe) [17.04.3-0ubuntu1] (no packageset)
[21:12] -queuebot:#ubuntu-release- New binary: kdav [amd64] (artful-proposed/universe) [17.04.3-0ubuntu1] (no packageset)
[21:13] -queuebot:#ubuntu-release- New binary: kdav [arm64] (artful-proposed/universe) [17.04.3-0ubuntu1] (no packageset)
[21:13] -queuebot:#ubuntu-release- New binary: kdav [s390x] (artful-proposed/universe) [17.04.3-0ubuntu1] (no packageset)
[21:13] -queuebot:#ubuntu-release- New binary: kdav [armhf] (artful-proposed/universe) [17.04.3-0ubuntu1] (no packageset)
[21:14] -queuebot:#ubuntu-release- New: accepted kdav [amd64] (artful-proposed) [17.04.3-0ubuntu1]
[21:14] -queuebot:#ubuntu-release- New: accepted kdav [armhf] (artful-proposed) [17.04.3-0ubuntu1]
[21:14] -queuebot:#ubuntu-release- New: accepted kdav [ppc64el] (artful-proposed) [17.04.3-0ubuntu1]
[21:14] -queuebot:#ubuntu-release- New: accepted kdav [arm64] (artful-proposed) [17.04.3-0ubuntu1]
[21:14] -queuebot:#ubuntu-release- New: accepted kdav [s390x] (artful-proposed) [17.04.3-0ubuntu1]
[21:14] -queuebot:#ubuntu-release- New: accepted kdav [i386] (artful-proposed) [17.04.3-0ubuntu1]
[21:29] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [0.7.9-153-g16a7302f-0ubuntu1~16.04.2 => 0.7.9-233-ge586fe35-0ubuntu1~16.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[21:29] -queuebot:#ubuntu-release- Unapproved: cloud-init (zesty-proposed/main) [0.7.9-153-g16a7302f-0ubuntu1~17.04.2 => 0.7.9-233-ge586fe35-0ubuntu1~17.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[22:41] -queuebot:#ubuntu-release- New binary: ring-mock-clojure [amd64] (artful-proposed/universe) [0.3.1-1] (no packageset)
[22:42] -queuebot:#ubuntu-release- New binary: libi8x [amd64] (artful-proposed/universe) [0.0.5~pre1-1] (no packageset)
[22:42] -queuebot:#ubuntu-release- New binary: prismatic-plumbing-clojure [amd64] (artful-proposed/universe) [0.5.4-1] (no packageset)
[22:42] -queuebot:#ubuntu-release- New binary: libi8x [i386] (artful-proposed/universe) [0.0.5~pre1-1] (no packageset)
[22:43] -queuebot:#ubuntu-release- New binary: kmime [amd64] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:43] -queuebot:#ubuntu-release- New binary: kmime [i386] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:45] -queuebot:#ubuntu-release- New binary: kpimtextedit [amd64] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:45] -queuebot:#ubuntu-release- New binary: libi8x [ppc64el] (artful-proposed/universe) [0.0.5~pre1-1] (no packageset)
[22:46] -queuebot:#ubuntu-release- New binary: kmime [ppc64el] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:46] -queuebot:#ubuntu-release- New binary: kpimtextedit [i386] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:48] -queuebot:#ubuntu-release- New binary: kpimtextedit [ppc64el] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:49] -queuebot:#ubuntu-release- New binary: libkf5grantleetheme [amd64] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:50] -queuebot:#ubuntu-release- New binary: kmime [arm64] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:50] -queuebot:#ubuntu-release- New binary: kmime [s390x] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:50] -queuebot:#ubuntu-release- New binary: kmime [armhf] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:50] -queuebot:#ubuntu-release- New binary: libi8x [arm64] (artful-proposed/universe) [0.0.5~pre1-1] (no packageset)
[22:51] -queuebot:#ubuntu-release- New binary: kpimtextedit [arm64] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:52] -queuebot:#ubuntu-release- New binary: kpimtextedit [armhf] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[22:52] -queuebot:#ubuntu-release- New binary: kpimtextedit [s390x] (artful-proposed/universe) [17.04.3-0ubuntu1] (kubuntu)
[23:03] -queuebot:#ubuntu-release- New: accepted libi8x [amd64] (artful-proposed) [0.0.5~pre1-1]
[23:03] -queuebot:#ubuntu-release- New: accepted libi8x [i386] (artful-proposed) [0.0.5~pre1-1]
[23:03] -queuebot:#ubuntu-release- New: accepted prismatic-plumbing-clojure [amd64] (artful-proposed) [0.5.4-1]
[23:03] -queuebot:#ubuntu-release- New: accepted libi8x [arm64] (artful-proposed) [0.0.5~pre1-1]
[23:03] -queuebot:#ubuntu-release- New: accepted ring-mock-clojure [amd64] (artful-proposed) [0.3.1-1]
[23:03] -queuebot:#ubuntu-release- New: accepted libi8x [ppc64el] (artful-proposed) [0.0.5~pre1-1]
[23:08] -queuebot:#ubuntu-release- New sync: libreoffice-l10n (artful-release/primary) [1:5.3.4-0ubuntu1]
[23:13] -queuebot:#ubuntu-release- New sync: libreoffice-l10n (artful-proposed/primary) [1:5.4.0-0ubuntu1]
[23:22] -queuebot:#ubuntu-release- New sync: libreoffice-l10n (artful-release/primary) [1:5.3.4-0ubuntu1]


[02:26] <duflu> jamesh, pulseaudio 1:11.1-1ubuntu7.5 is still in proposed. Did you get an update on that?
[02:26] <jamesh> duflu: not yet.  I'll ping jdstrand about it.
[02:27] <jamesh> duflu: yesterday I noticed some problems with the mouse pointer on my desktop.  It looked a lot like https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865371
[02:27] <duflu> jamesh, sounds like progress: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196
[02:27] <jamesh> might be tied to the Radeon driver?
[02:28] <duflu> jamesh, yeah too many possible causes so please open a new bug from yours: ubuntu-bug gnome-shell
[02:36] <thumper> does anyone know who runs the matrix bridge?
[02:38] <sarnold> I've heard they actually have a person now
[02:48] <jamesh> duflu: here's a new bug report: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867080
[02:52] <duflu> Ta, jamesh
[02:53] <duflu> jamesh, can you please add output from 'lspci -k' ?
[02:55] <jamesh> duflu: done
[02:58] <duflu> jamesh, fixed in mutter 3.36.0
[03:01] <jamesh> duflu: I guess this is the same as https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1866371 then
[03:02] <duflu> yep
[03:03] <duflu> That was in the list of 90 bugs I am in the process of catching up on
[06:26] <jibel> hi all
[06:36] <duflu> Hi jibel
[06:45] <oSoMoN> good morning desktoppers
[06:54] <duflu> Hi oSoMoN
[06:59] <duflu> Good trip home?
[07:00] <oSoMoN> hey duflu. My trip was short an uneventful, how was yours?
[07:01] <duflu> oSoMoN, amazingly I have so far got away without a cold or flu, which is unusually good. The main flight was very full but I took a pill and slept most of it
[07:02] <oSoMoN> good! I haven't had any ubuflu symptom either, but then again my travel was negligible compared to yours
[07:09] <didrocks> good morning
[07:11] <duflu> Hi didrocks
[07:11] <oSoMoN> salut didrocks
[07:17] <didrocks> hey duflu, salut oSoMoN
[07:35] <duflu> Weird. Why has my focal desktop kept the login screen theming bugs that were fixed for my laptop last week?
[07:35] <duflu> Fully updated
[07:52] <jibel> same here
[07:52] <jibel> the login screen is fine but the shield is not
[08:07] <duflu> jibel, oh that's different again
[08:08] <duflu> Surely this is related to how old my install is. Probably doesn't happen in new installs
[08:08]  * duflu makes another USB stick
[08:08] <jibel> i'll try on today's build
[08:35] <duflu> jibel, adding a user account photo fixes one of the issues
[08:40] <seb128> goood morning desktopers!
[08:41] <duflu> Morning seb128
[08:41] <duflu> jibel, I forgot the centring bug is not yet fix-released (bug 1865563)
[08:42] <didrocks> salut seb128
[08:43] <seb128> hey duflu, didrocks, how are you?
[08:43] <duflu> seb128, travelled well and no longer jet lagged, I think. You?
[08:44] <seb128> duflu, ah, good to read! and no cold/flu/... on the way back this time?
[08:44] <seb128> I'm good, return trip was easy train for me :)
[08:44] <seb128> and week has been busy with GNOME 3.36 updates
[08:44] <didrocks> seb128: I’m good, thanks! You?
[08:44] <seb128> didrocks, I'm good thanks! played some tennis yesterday evening :)
[08:45] <duflu> seb128, yeah some element of luck there and also better practices
[08:45] <seb128> wasn't great because of the wind but still nice to be outside/moving
[08:47] <didrocks> nice
[09:02] <Wimpress> Hello desktopers
[09:03] <Laney> hey
[09:03] <seb128> hey Wimpress, how are you? had a good day off? got internet fixed?
[09:03] <seb128> hey Laney
[09:03] <duflu> Hi Wimpress and Laney
[09:03] <Wimpress> Yep. Good day off. Fixed network/internet in the afternoon.
[09:04] <Wimpress> Looks like it went wonky again in the early hours.
[09:04] <Wimpress> So....
[09:04] <Wimpress> duflu: o/
[09:04] <Wimpress> Did some live streams last night, basic debian/ubuntu package updates, testing, etc.
[09:05] <Wimpress> So internet did hold up for that, but died at the very end :(
[09:13] <jibel> can someone try today's iso on a real machine and tell me if it boots?
[09:13] <didrocks> hey Wimpress, Laney
[09:15] <jibel> uh, looks like image checksum is broken
[09:16] <jibel> this is bug 1867065
[09:18] <jibel> xnox, ^ I think it's for you
[09:18] <jibel> it's related to the checksum of the image
[09:56] <Wimpress> tseliot: Morning.
[09:57] <Wimpress> Have you seen any reports of the updated nvidia driver hard locking systems while updating initramfs?
[09:57] <Wimpress> My desktop hard locked while installing updates.
[09:59] <Wimpress> Got the system to boot, but trying to update/remove nvidia drivers hard locks the system everytime initramfs attempts to rebuild.
[09:59] <Wimpress> I'm on the 440 series driver.
[10:05] <Wimpress> OK. Kernel panics.
[10:06] <duflu> Wimpress, default kernel?
[10:06] <duflu> I noticed some complaints about 5.6
[10:06] <duflu> with nvidia-440
[10:07] <Wimpress> Yes, 5.4 kernel.
[10:07] <duflu> Different bug then
[10:08] <Wimpress> core dumps each time DKMS is updated when recovering via single user.
[10:08] <duflu> Wimpress, seb128, also I would have thought we should display the Ubuntu logo before then?...
[10:08] <seb128> before what?
[10:09] <duflu> before the kernel boots and potentially hangs
[10:09] <seb128> can we do that?
[10:09] <duflu> grub can surely?
[10:09] <Wimpress> That is working duflu.
[10:09] <seb128> I guess, unsure how much would that would be, feels late to start on that for this cycle
[10:09] <Wimpress> I see the Ubuntu logo.
[10:10] <duflu> Ah OK.
[10:10] <duflu> I don't on some machines
[10:10] <Wimpress> Also, I have recovered the system.
[10:10] <Wimpress> But this is non-recoverable with any graphics driver loaded.
[10:12] <seb128> Laney, mozjs68 has a test failure on i386, I retried once but same error :-/
[10:13] <Laney> I know, it was unlikely to be fixed with a retry
[10:13] <Laney> have been looking at it already
[10:13] <seb128> k, good :)
[10:13] <Laney> https://bugzilla.mozilla.org/show_bug.cgi?id=1621900
[10:13] <Wimpress> seb128: There are three merge proposal for Ubiquity Slideshow.
[10:13] <Wimpress> Will it help if I pull those into one MR?
[10:13] <seb128> Wimpress, no
[10:14] <Wimpress> OK
[10:15] <seb128> Wimpress, if you want to help you can review/accept the Mps
[10:15] <seb128> Wimpress, I can do the merge/upload but I'm not going to test flavor/have a call if they look right
[10:16] <seb128> Wimpress, the other option is to just merge without testing and trusting them to not screw their own slides
[10:16] <Wimpress> I can do the review.
[10:16] <seb128> thx
[10:16] <seb128> I will do the merge/upload if you ack the mps
[10:16] <Wimpress> I did a live stream about updating/testing Ubiquity slideshow last night.
[10:17] <seb128> you should get real days off sometime :)
[10:17] <Wimpress> Can I review my own MR? ;-)
[10:17] <Wimpress> I trust me.
[10:18] <Laney> Ah, that should be the person you trust *least*!
[10:18] <Laney> who wrote this and what was I thinking?
[10:19] <seb128> Wimpress, I'm fine review yours if you review the other ones
[10:21] <seb128> Laney, I retried libproxy/i386 autopkgtest with the right trigger, should be candidate now
[10:22] <Laney> cool
[10:22] <Laney> poor focal :(
[10:26] <Wimpress> seb128: OK, I'll review them this evening.
[10:27] <seb128> Wimpress, thanks
[10:28] <seb128> Laney, do you know if there is a way to ask for a debian autopkgtest retry?
[10:31] <Laney> seb128: excuses and/or ci.debian.net have retry links
[10:32] <seb128> Laney, sorry, it's not a failure, I just want to ask for a new try with what is current in unstable
[10:32] <seb128> https://ci.debian.net/packages/r/ruby-gnome/unstable/amd64/ didn't get tried yet with the new webkit2gtk
[10:34] <seb128> in fact there might be one in the queue if I read pending/ correctly
[10:34] <seb128> I guess I just need to wait then :)
[10:34] <Laney> ok
[10:34] <seb128> thx for the reply though!
[10:34] <Laney> but no I don't know how to schedule arbitrary jobs there
[10:35] <Laney> would be a question for #debci if you need it in future
[10:35] <seb128> ah, I didn't know they had a channel, thx
[10:41] <seb128> Laney, is that you that sponsored adwaita to Debian for Marco? if so could you gbp push the update?
[10:42] <Laney> ok
[10:42] <Laney> ping-fest
[10:42] <seb128> sorry :(
[10:42] <seb128> I will stop there :p
[10:43] <Laney> it's ok, means work is happening
[10:43] <seb128> thanks!
[10:43] <Laney> I needed to ask for him to push the upstream/foo tag on that one and then I guess didn't get notified or forgot to go back to it
[10:48] <seb128> Trevinho, hey, how are you? how is the dock fixing going?
[10:51] <xnox> jibel:  hey, the disk check goes, prints results, pauses a little or longer, continues to boot.
[10:51] <xnox> jibel:  currently pass & fail code paths are the same.
[10:52] <xnox> jibel:  the "lvm" fail message is a bit of a red herring, i should fix that to not confuse people.
[10:57] <jibel> xnox, yeah, I think the problem is that there is no feedback while the checksum is occuring, it takes time so people swtich to another console and see this message.
[10:57] <xnox> jibel:  but on the desktop it should be pretty
[10:57] <jibel> it is not
[10:57] <xnox> jibel:  the text messages are not pretty
[10:57] <xnox> jibel:  on the desktop plymouth should be painting pretty %
[10:58] <xnox> jibel:  something has regressed, if it's not pretty, let me download new image.
[10:58] <jibel> there is no feedback at all, no message or anything
[10:58] <jibel> just a black screen with the dell logo, the ubuntu logo and a spinning loading icon
[10:59] <xnox> jibel:  did somebody break plymouth theme?
[10:59] <seb128> xnox, the spînner logo maybe doesn't output thing like the ubuntu one was?
[10:59] <xnox> seb128:  so you switched the theme, without testing installer?
[10:59] <xnox> seb128:  great, spinner logo doesn't support any custom messages that we use in systemd-fsckd & casper. Installer image should use the ubuntu-logo splash theme
[11:00] <seb128> I guess yes
[11:00] <xnox> seb128:  and spinner theme is not suitable for us, as is, unless we ensure fsck:* messages are supported.
[11:00] <seb128> it also means we are regressing in installed system where fsck is happening?
[11:00] <xnox> seb128:  yes
[11:00] <seb128> Wimpress, ^
[11:00] <xnox> seb128:  because systemd-fsckd & plymouth integration is ubuntu-only.
[11:01] <xnox> seb128:  my system still uses ubuntu-logo => i guess my system is customized and I'm not getting stock focal experience then?
[11:01] <seb128> what does upstream do during fsck checks?
[11:01] <xnox> seb128:  nothing
[11:01] <seb128> do they display busyness in some other way?
[11:01] <xnox> they don't use filesystems that need fsck
[11:01] <seb128> xnox, either that or upgrade didn't pull the new recommends
[11:03] <xnox> seb128:  so my personal plan was to tweak ubuntu-logo theme to be "more like spinner", i.e. keep the vendor logo on screen, move the ubuntu logo down (to where gdm ubuntu logo is) and fade-in black to purple
[11:04] <seb128> xnox, wfm, the only reason I've been dealing with plymouth is that no one in foundation is actively taking care of it, but I would be happy to leave to people wanting to invest some work on getting us on a more modern look for boot splash
[11:04] <didrocks> xnox: systemd-fsckd isn’t ubuntu only, but having a plymouth theme support it is
[11:04] <xnox> seb128:  Wimpress: what's the driver for spinner theme? cause to fix things i could port fsck messages to the spinner theme; or do something inverse, make ubuntu-logo theme behave "more like spinner"
[11:05] <seb128> xnox, nicer user experience
[11:05] <xnox> seb128:  ack, let me play with spinner theme, to get a better feel for it.
[11:05] <seb128> especially for oem where like xps preinstalled where you have no grub menu
[11:05] <seb128> xnox, thanks!
[11:06] <xnox> seb128:  i guess it goes from dell logo, dell logo + spinner (a little bit), gdm?
[11:06] <seb128> xnox, yes
[11:06] <seb128> dell logo + spinner + ubuntu logo at the bottom of the screen
[11:06] <seb128> to be exact
[11:07] <xnox> seb128:  ooooh, and it's monochrome ubuntu logo
[11:07] <xnox> how black tie
[11:07] <seb128> yes, we got an updated logo in Frankfurt
[11:08] <seb128> xnox, also I'm about to update the spinner assets to be the yaru spinner
[11:08] <xnox> yeah, none of casper messages got printed with fsck progress
[11:08] <seb128> frederik provided me new assets
[11:08] <xnox> seb128:  do you have links as to how yaru spinner looks?
[11:09]  * xnox reboots
[11:09] <seb128> xnox, https://gitlab.freedesktop.org/Feichtmeier/plymouth/-/tree/master/themes/spinner the throbber-nnn files there
[11:14] <xnox> seb128:  it's a bit ugly with disk unlocking.
[11:15] <seb128> xnox, why? because the entry is placed to high on the screen?
[11:15] <xnox> seb128:  in ubuntu-logo, we poppped up the type password field below the centre logo, and hid it after typing password. In spinner, it removes dell logo, pushes the entry field for password, then hides it, jumps the unlock message possition, repaints the vendor logo.
[11:16] <xnox> seb128:  because it flickers the oem logo, instead of keeping it painted, and using the like spinner location for the entry field.
[11:16] <seb128> xnox, those are problem worth reporting upstream
[11:16] <seb128> but yeah, it could be better/get some extra polish
[11:16] <xnox> seb128:  as per Windows guidelines the area of the oem logo is not to be used for any messages or input.
[11:17] <xnox> seb128:  also there is flicker of the ubuntu logo. It seems like gdm "fades in" ubuntu logo on the bottom, although it is pixel perfect, it flickers a fade in of it.
[11:18] <xnox> cause it goes from white, instant to purple, fade in purple to white ubuntu logo.
[11:19] <xnox> seb128:  i wonder how quick it would be to make ubuntu-logo be spinner compatible. I.e. drop background painting, pop up oem logo, change ubuntu graphic, push it down => jobs done, in a non-regressive way
[11:19] <seb128> right, valid point/things we could improve if we have time/resources to look at those
[11:20] <xnox> seb128:  it might look slightly better, if at "spinner stop" one fades out ubuntu logo in plymouth
[11:20] <xnox> seb128:  fsckd messages support regression, imho is bad.
[11:20] <seb128> it's annoying indeed
[11:21] <seb128> could you open a bug about it?
[11:21] <seb128> we need to discuss what are our option/what we want to do
[11:21] <xnox> seb128:  what term do you use for new & old themes? spinner & ubuntu-logo? or bgrt & ubuntu-logo?
[11:22] <xnox> i see both in bugs =)
[11:22] <seb128> spinenr is the name of the theme
[11:22] <seb128> spinner
[11:22] <xnox> ack
[11:24] <xnox> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867130
[11:29] <xnox> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867131
[11:34] <seb128> xnox, thanks
[11:35] <xnox> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1867133
[11:44] <seb128> thx for the report, need to drop offline for a bit while relocating
[11:44] <Saviq> didrocks: I ran out of space on my zpool… can I just destroy the zsys snapshots? is there a database I'll need to clean somewhere?
[11:49] <didrocks> Saviq: waow, already? Your snapshots were taking so much space?
[11:49] <didrocks> yeah, remove them directly for now with zfs
[11:50] <didrocks> zfs destroy -r rpool@snapshot_name bpool@snapshot_name
[11:50] <didrocks> note that snapshots take no space if you don’t have any change
[11:50] <Saviq> didrocks: the problem is that you just never regain space…
[11:50] <didrocks> as it's a COW system
[11:51] <Saviq> (and I only have 128G atm)
[11:51] <didrocks> ah, that makes sense. You can adjust the gc if your need is a small machine
[11:52] <didrocks> dropping the conf file to the right place
[11:52] <didrocks> (and yeah, we only rely on zfs state, we don’t have a separate database on purpose to avoid async issues)
[11:53] <didrocks> zfs list -o space should be of help if you can print it out for our info with jibel
[11:53] <Saviq> Gah… recovery is busted…
[11:53] <didrocks> zfs list -o space -t snapshot
[11:53] <didrocks> also
[11:54] <didrocks> I thought that we kept in ubuntu as root an X% space for booting
[11:55] <Saviq> Need to boot from an external drive… we seem to lack the 5% root space… or well, it got filled with LXD
[11:58] <Saviq> Ok recovered enough to boot
[11:59] <didrocks> phew, if you can paste the space commands so that we see how much is taken by snapshots, that would be helpful
[12:07] <Saviq> didrocks: https://paste.ubuntu.com/p/RWbNT6p2j3/ https://paste.ubuntu.com/p/gPnqD3Qcbj/
[12:07] <Saviq> I don't think it gives it justice… I recovered almost 50G by dropping them
[12:10] <didrocks> hum. Indeed, the userdata ones are weird to not be the sum of them
[12:10] <didrocks> we’ll give it some tests
[12:16] <Saviq> I'll file a proper bug soon
[12:17] <Saviq> but I think that we've "lost" the 5% root buffer is something quite bad
[13:32] <jibel> xnox, seb128 the shutdown to reboot message also regressed cf bug 1865161
[13:33] <xnox> jibel:  i somehow feel like spinner theme is not showing any messages, yet to test this with plymouth-x11 to confirm
[13:33] <xnox> jibel:  wasn't spinner theme meant to be "non-interactive"
[13:36] <xnox> jibel:  maybe we need like layers on the desktop iso to have "installer" layer with ubuntu-logo theme instead of the spinner one
[13:55] <ogra> kenvandine, i think we can skip today, unless yuo have anything pressing (i was busy with customer stuff all week so nothing to talk about from my side)
[13:55] <kenvandine> ogra: sounds good
[13:56] <popey> is it known that today's daily takes an age to boot?
[13:56] <popey> sits at the spinner for quite a bit longer than usual
[13:57] <jibel> yes, it's the fsck without feedback
[13:57] <popey> oh, i am not seeing the checker
[13:57] <jibel> there is bug 1867065 and the 2 others xnox filed
[13:58] <popey> ta
[13:58] <jibel> bug 1867131
[13:59] <jibel> bug 1867130
[14:02] <jibel> is it known that snap cannot be installed on a fresh installation of focal?
[14:02] <jibel> I get "too early for opetaion, device not yet seeded, ...."
[14:03] <popey> we have seen that before a number of times
[14:03] <popey> happens in lxc containers for example if you create one, shell in, then immediately snap install something
[14:03] <jibel> the machine has been up for more than 1 hour now
[14:03] <jibel> it's a real machine
[14:03] <popey> oh
[14:03] <popey> a bug then
[14:03] <jibel> installed from today's build
[14:03] <popey> -> snap
[14:04] <jibel> livecd-rootfs bug. I thought it was fixed
[14:08] <seb128> jibel, did we just get the plymouth theme changing on the iso for some reason or has it been that way for weeks but nobody tested the iso during that timeframe?
[14:12] <jibel> week
[14:12] <jibel> singular
[14:13] <jibel> I just did a more intensive review this morning
[14:13] <jibel> otherwise it's automated and unnoticed
[14:15] <seb128> jibel, the seed change was done in january, that's week*s* :-) https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=f7e2db8231
[14:17] <jibel> seb128, maybe but it's been broken after the change to enable md5check in casper which was end of february
[14:17] <jibel> until then it was the aubergine boot screen without a spinner
[14:18] <seb128> jibel, well, we saw that working
[14:18] <seb128> I was mostly curious to know when it stopped working
[14:19] <seb128> but I guess we don't have enough data to say/didn't do enough regular testing
[14:19] <seb128> oh well
[14:19] <seb128> we should probably find a way to force the ubuntu-logo theme on the iso
[14:20] <seb128> it's a special case with the checksum, reboot, etc
[14:20] <seb128> unless fixing the fsck case/displaying of message for spinner fixes those cases...
[14:24] <jibel> seb128, I'd say it broke within the last 2 weeks. According to https://discourse.ubuntu.com/t/defaulting-to-verify-the-image-integrity-before-installing-on-desktop/13472/6 it was still the aubergine background and the checksum message was displayed
[14:24] <popey> I tested last week and it worked
[14:24] <jibel> yeah
[14:24] <popey> something changed between last week and this
[14:25] <seb128> oh well
[14:25] <seb128> software
[14:25] <jibel> popey, snap bug is https://bugs.launchpad.net/bugs/1864252
[14:25] <jibel> same symptoms as least
[14:25] <seb128> jibel, if we only we had worked on that trello card about storing images history, we could tell what changed and when :)
[14:26] <popey> https://youtu.be/YOUwdhNbHtk?t=519 - video proof of what it looked like on 1st march
[14:30] <hellsworth> good morning desktopers
[14:31] <seb128> hey Heather, how are you today?
[14:32] <hellsworth> feeling better. yesterday i felt a bit sick but seems it was nothing
[14:33] <seb128> oh, great that it was nothing!
[14:34] <hellsworth> yeah i was probably just being extra sensitive due to the world situation
[14:34] <Wimpress> hellsworth: Hello.


[03:55] <fu-fu_> So, anyone know a quick way to get packages for jaunty..? (Everything broke, my fault. This is the only linux disk I still have.)
[03:56] <Poisoned_Dragon> Jaunty?! How old is that?
[03:56] <fu-fu_> if ls -l / is anything to go by.. from 2009.
[03:56] <cfhowlett> fu-fu_, why?  end of life!  get a supported version and install.
[03:58] <fu-fu_> All I need is a quick fix, to get qemu so that I can fix btrfs in a vm and not have it crash my pc everytime I try anything.
[04:00] <cfhowlett> fu-fu_, perhaps "end of life" means something different where you're from ... :)
[04:04] <Poisoned_Dragon> fu-fu_, Google is your friend because, you're not going to get support for an end of life release here.
[04:04] <fu-fu_> I realized that, saddly I keep getting "Domain not found" when I go to google :/
[04:05] <Poisoned_Dragon> how can you get domain not found for google, if you're here?
[04:07] <fu-fu_> I have no idea, but I just tryed duckduckgo and it seems to work.
[04:10] <Poisoned_Dragon> Why stay on Jaunty for so long?
[04:13] <fu-fu_> I'm not staying on it, I just broke my arch linux install and this was the only disk I had at hand... I've given up trying to use it for anything more than downloading a new image to put on a flashdrive.
[04:15] <Poisoned_Dragon> oooooh... lol
[04:15] <cfhowlett> fu-fu_, you're on the internet, so you have access.  download a supported image and we can help
[04:15] <Poisoned_Dragon> probably as simple as giving him a address to wget with
[04:16] <cfhowlett> www.ubuntu.com  ???
[04:16] <Poisoned_Dragon> No.... the link to an iso he want's to download.
[04:16] <Poisoned_Dragon> His DNS is being retarded.
[04:16] <cfhowlett> Poisoned_Dragon, beyond my skillset ...
[04:16] <Poisoned_Dragon> what did you want to install, fu-fu_?
[04:17] <fu-fu_> xD, no I think my ISP or router is, my dns is working for everything else. (I am currently downloading the LTS of Xubuntu)
[04:17] <Poisoned_Dragon> Ah
[04:17] <Poisoned_Dragon> So, you're already golden.
[04:17] <cfhowlett> brilliant!
[04:18] <Poisoned_Dragon> How did you manage to break your arch install?
[04:18] <Poisoned_Dragon> Not that it's hard to do, or anything.
[04:19] <fu-fu_> Uhh, Don't run a virtual mechine, of /dev/sda when you booted from /dev/sda... It's more of a broken btrfs.
[04:19] <Poisoned_Dragon> What the hell, virtual partition inception?
[04:21] <fu-fu_> Virtual partiton? Nah. Just the same one being used twice, at the same time... basically all the open files in both mechines.. broke/vanished/weird btrfs/nfs bug.. (Odd, as it isn't a nfs...) so.. most of /lib and some of /bin
[04:23] <fu-fu_> I also broke my other install.. btrfs device add /dev/zram0 + crash = broken btrfs image.
[04:23] <Poisoned_Dragon> heh
[06:44] <xubuntu928> i am planning to try xu 13.10 pre-release on my laptop. does this release support uefi laptops?
[06:44] <bazhang> !saucy | xubuntu928
[06:45] <bazhang> xubuntu928, /join #ubuntu+1
[06:45] <xubuntu928> reason i ask rather than download and try it out is because my network connection is very slow
[06:45] <elfy> xubuntu928: it should do - but this isn't the channel to ask about it :)
[06:46] <xubuntu928> where should i ask about that @elfy?
[06:46] <elfy> read the comments just above ;)
[06:47] <Polyolyver> Hiya! I'm a Windows geek and Linux newbie; just installed Xubuntu on my secondary desktop. When I start some applications (so far, whatever browser was the default (since changed to Chromium with no probs), and Virtualbox), it instantly hard freezes, with a corrupted display (a repeating series of pixels, so there's a randomish pattern on the screen) - only solution is to hard reboot. Any pointers on where to start with this?
[06:47] <bazhang> xubuntu928, ------------>  #ubuntu+1   <-------------------
[06:47] <xubuntu928> oops! i am completely new here, @elfy. can u plz tell me what is this channel for?
[06:48] <xubuntu928> @bazhang, thanks for the redirect. but, i am interested in xubuntu not ubuntu. would #ubuntu+1 still be the right channel for my question?
[06:48] <xubuntu928> sorry if i am bothering you guys.
[06:48] <elfy> xubuntu928: read the topic :)
[06:48] <bazhang> xubuntu928, all go there
[06:48] <elfy> xubuntu928: ubuntu+1 is the dev version channel
[06:48] <bazhang> xubuntu928, kubuntu xubuntu ubuntu all go there
[06:49] <xubuntu928> ok! got it guys. thanks so much for your help.
[06:49] <elfy> xubuntu928: if you actually want to help with development - then we have #xubuntu-devel , but that is not a support channel
[06:50] <xubuntu928> i am on irc for the first time. :) and i am using the web interface from xubuntu.org. so, i will read up before posting questions next time. sorry! and thanks
[06:50] <elfy> welcome :)
[06:53] <Polyolyver> (just to add: even knowing the terms to search for would be helpful to me... Also, I added a keyboard shortcut I read about somewhere - don't have offhand, but CTRL-ALT-BACKSPACE to kill X or Xwindow or... I haven't learned what I'm killing yet -- but point is, the shortcut works and kicks me to a login window, but it doesn't work when this freeze happens -- if that helps)
[06:55] <elfy> Polyolyver: what graphics card, how much memory cpu etc you using?
[07:01] <Polyolyver> Sorry, the wife called for a quick favor. GeForce LE 6150, I think I have 4GB but might be 2GB RAM, and... I don't remember the processor offhand. Is there a way to see what Xubuntu thinks like you can in Windows? I can tell if it's right or not, but it's been too long since I got this box...
[07:03] <Polyolyver> AMD Sempron LE 1250
[07:03] <Polyolyver> Forgot the BIOS tells ya... I'm a software guy in my defense :)
[07:04] <elfy> lspci in a terminal
[07:04] <Polyolyver> and 2GB of ram...
[07:04] <elfy> will list pci cards
[07:04] <Polyolyver> getting back into OS to see what that says :)
[07:04] <elfy> vbox is likely to stutter a bit with ram I'd suspect
[07:08] <Polyolyver> ah, right, GeForce 6150SE nForce. heh. Crappy card.  Hmm... I'd be fine with it stuttering if that means slow - it's intended as a crutch because I want to switch to Linux for my desktop as I do 90% of my stuff in Chrome anyway... but I do sometimes need Windows-specific stuff... But the main concern right now is Xubuntu locking up on app launch (whichever the default browser was did the same thing at launch)
[07:08] <Unit193> GeForce 6150SE nForce 430?  Not hit that myself, same ram too.
[07:09] <Unit193> I'd say ssh in from another computer, check dmesg and logs in /var/log/
[07:10] <Polyolyver> like... tail /var/log/dmesg from another box and start the app to see what I get?
[07:11] <Unit193> dmesg is a command, and there's a syslog, xorg, and kernel logs in /var/log/
[07:12] <Unit193> (dmesg is in /var/log/ too, but still. :P )
[07:14] <Polyolyver> ahh, was confused b/c I see /var/log/dmesg, and it doesn't look like an executable to me. hehe.
[07:14] <Polyolyver> Is SSH enabled by default? Checked my IP with ifconfig, tried to SSH and connection refused...
[07:15] <Unit193> Nope.  I suppose that's not one of the first things everyone sets up.  Do TTYs work?
[07:16] <Polyolyver> I've never used a TTY before.
[07:17] <Unit193> !tty
[07:17] <Unit193> (Also, I'm about to head out, so hopefully elfy is still around.)
[07:18] <Polyolyver> tty1 apparently works; shows a login, 'starting crash report submission daemon', and that's it
[07:18] <Polyolyver> others show login prompt
[07:18] <Polyolyver> Is this a question of if it works when things are otherwise apparently frozen?
[07:19] <Unit193> Yes.
[07:19] <Polyolyver> I'm slow on the uptake sometimes. Checking...
[07:19] <Polyolyver> a-ha. Negative, they do not appear to work when locked/frozen (which state I am now in again)
[07:20] <Polyolyver> I'll sit here a sec in case you want me to try something else :)
[07:21] <Unit193> Bummer.  Well, I'd check the logs after reboot then, starting with syslog to see what's up.
[07:21] <Polyolyver> okies, rebooting
[07:21] <Polyolyver> Also, please don't wait around for me - whether anyone else is around or no, I have a borrowed box to work on, so this is something I'd like to try and solve, but not an emergency :)
[07:22] <Unit193> Yeah, I'm heading out now as my head is killing me.
[07:22] <Polyolyver> Thanks mightily for your help :) Hope your head feels better soon!
[12:32] <xubuntu040> hi
[12:32] <bgardner> xubuntu040: Hello
[13:17] <nextloop> hello. i am on xubuntu 13.04.  i use a vertical sidebar with a tasklist. now i want to rotate the tasklist so that the text appears horizontal. how to do that. setting /plugins/plugin2/rotate-vertically does not not show any effect
[14:13] <nyker> how to sync ipod touch ios 6 to xubuntu?
[14:15] <ElFizbanio> you shouldn't
[14:16] <M4rdukBR> https://help.ubuntu.com/community/PortableDevices/iPod
[14:25] <kRush> my user created during installation is in groups adm cdrom sudo dip plugdev lpadmin sambashare, where can I find what membership in each of these groups actually does? a newly created user is in none of them and I wonder where I need to add him
[14:30] <baizon> kRush: https://wiki.archlinux.org/index.php/Users_and_Groups
[14:31] <xubuntu866> Hello everybody, can somebody please explain why I'm getting black screen (fivth time) when trying to install drivers for AMD 7950, tried via software center and terminal
[14:32] <xubuntu866> No luck either by installing fglrx on software nor via AMD website...
[14:39] <Morrog> is anybody a gtk theme specialist here?
[15:21] <pinkydw> having an issue with installing xubuntu on a hardware raid, not sure I'm partitioning/formatting the array correctly.  I keep getting an error saying that it can't setup the swap area.
[15:22] <pinkydw> if it matters, trying to dual boot win7 for gaming
[15:26] <baizon> pinkydw: https://help.ubuntu.com/community/Installation/SoftwareRAID
[15:27] <pinkydw> thanks, I'll read through it when i get home
[17:14] <gdos> i am getting a permission denied error when attempting to move stuff to the trash can (using thunar).
[17:22] <GridCube> are you using thunar with root?
[17:38] <gdos> no.
[17:58] <church> Is there any way to get mac style global menu in xubuntu?
[18:00] <GridCube> church, not really
[18:00] <church> i saw something like xfce4 appmenu plugin .. for only old ubuntu versions :/
[18:02] <GridCube> yes
[18:03] <GridCube> but thats no longer possible, as its not mantained for current xfwm4 versions
[18:19] <gdos> church white not re-create the plugin?
[18:27] <church> i beleave problems stems from latest ubuntu (including appmenu indicators) being gtk3, but xfce4 - gtk2, no?
[18:28] <church> good that most DEs/WMs can be configured to look similar. bad that each has own limitations / limited miscellaneous plugins/applets sets
[18:30]  * church rarely upgrades distrib, so decided to install whatever is latest as of now, 13.10, but seems that gnome fallback option in it is much more limited/buggy then in 12.04, so finally started trying out alternatives
[18:30] <church> hate gnome3/unity, not too fond of kde, so hoped to get as much as possible from lightweight alternatives
[18:33] <__0x57__> I have compiz and emerald installed, and I have also selected a theme which i have downloaded, now the window decoratiosn have applied, but how come the font and the panel and everything else the theme is meant to modify has not worked ? any ideas
[18:35] <xubuntu604> Hmm...
[18:37] <xubuntu604> Are you 100% sure that you've applied these settings?
[18:38] <__0x57__> which settings?
[18:38] <xubuntu604> For the font and panel.
[18:38] <__0x57__> well this is my question
[18:38] <__0x57__> i thought when you click an emerald theme it aplpies aLL the settings
[18:38] <__0x57__> it seems to have only affected the windows
[18:39] <__0x57__> not the panel
[18:39] <xubuntu604> I see. You said you also had Compiz installed.
[18:39] <__0x57__> yeah
[18:39] <xubuntu604> Do they both work together, or do you need to interchange between them?
[18:40] <__0x57__> erm no everything seems to be fine, Im looking through the ccsm setings now to see if i have missed anything but.. not sure
[18:40] <xubuntu604> Yeah, try changing the panel and font settings for Compiz too.
[18:40] <xubuntu604> Tell me what happens after.
[18:41] <__0x57__> what i have done is compiz starts up, and then in window decoration settings, it is set to emerald insteal of gtk-decorator
[18:41] <__0x57__> is this right
[18:41] <__0x57__> ok where do youfind the panel and font settings in the ccsm, what heading is it under
[18:42] <xubuntu604> I think it's under the effects header, window decoration but I'm not certain.
[18:43] <__0x57__> not there
[18:44] <xubuntu604> What about desktop or general?
[18:45] <__0x57__> nope :/ also the desktop cube effect doesnt work would you have any idea why that isnt, and could these two issues be related
[18:46] <xubuntu604> I think the cube effects is disabled until the next update.
[18:46] <__0x57__> ahh ok
[18:46] <xubuntu604> Must be buggy.
[18:46] <__0x57__> im gonna try a reboot anyway
[18:46] <__0x57__> brb
[18:47] <xubuntu604> I wouldn't recommend Compiz and Emerald together by the way.
[18:47] <xubuntu604> See which you prefer more.
[18:47] <xubuntu604> Running them together causes conflicts.
[18:48] <xubuntu604> Unless Emerald requires compiz.
[18:48] <xubuntu604> I've confused myself.
[18:48] <__0x57__> no luck
[18:49] <xubuntu604> Emerald requires Compiz, doesn't it?
[18:49] <__0x57__> it seems really buggy using emerald with xubuntu
[18:49] <__0x57__> im not sure on the dependencies
[18:49] <__0x57__> i think emerald is justa  nice WM which intergrates with compiz ?
[18:49] <xubuntu604> Try Lubuntu. It's also lightweight.
[18:50] <__0x57__> i mean with emerald loaded now, i loaded up firefox and actually dragging the window via the title bar, the mouse wasnt registering i was clicking it, :S
[18:50] <xubuntu604> That's interesting...
[18:51] <xubuntu604> Try purging emerald and installing it again.
[18:51] <__0x57__> ok
[18:51] <xubuntu604> If you don't know how - sudo apt-get purge emerald
[18:51] <__0x57__> LOL so many things... i resized my term, and it starts resizing back to really small
[18:51] <__0x57__> WTF
[18:51] <__0x57__> i know cheers :)
[18:51] <GridCube> !language
[18:52] <xubuntu604> XD
[18:52] <xubuntu604> Sounds pretty messed up.
[18:52] <GridCube> compiz aint really supported anymore
[18:52] <xubuntu604> Really?
[18:53] <GridCube> pretty much
[18:53] <GridCube> except for unity
[18:53] <__0x57__> its not a big deal i suppose i just like the effects
[18:53] <xubuntu604> I don't use the usual XFCE effects.
[18:53] <__0x57__> its just one theme i want, and it needs emerald thats all
[18:53] <xubuntu604> I use Compiz because it eliminates screen tear.
[18:54] <__0x57__> yeah, there just some optional nice thigns like the cube
[18:55] <xubuntu604> Do you get kicked or banned for cursing in this chat?
[18:55] <__0x57__> i assume so
[18:55] <xubuntu604> Right after you said WTF, it mentioned not to use it.
[18:55] <__0x57__> yeah
[18:56] <GridCube> that was just a warning
[18:56] <GridCube> xubuntu604, please refrain to use that kind of language as well
[18:56] <GridCube> :=
[18:57] <GridCube> :)
[18:57] <xubuntu604> You have some immense power right there.
[18:58] <GridCube> P: not really
[18:58] <xubuntu604> Being able to change your name color and all.
[18:58] <xubuntu604> Hehehehehe.
[18:58] <GridCube> lol xubuntu604 thats just hilighting your name being mentioned
[18:59] <xubuntu604> Wait, how do you do it?
[18:59] <GridCube> i type your nick, using xu pressing tab and autocompleting it
[18:59] <GridCube> xubuntu604, like this
[18:59] <__0x57__> nice
[18:59] <GridCube> like __0x57__
[18:59] <__0x57__> liek GridCube
[19:00] <GridCube> see i press _ and tab
[19:00] <GridCube> exactly
[19:00] <xubuntu604> xubuntu604: Hohoho
[19:00] <__0x57__> lol althoughi  do hate it when you get those non interactive shells
[19:00] <xubuntu604> GridCube: Yehehehe
[19:00] <__0x57__> even no up arrows :P
[19:00] <GridCube> now your like is in red for me, instead of usual white, thats because my name was said
[19:00] <__0x57__> well what irc client are you using
[19:00] <xubuntu604> Makes sense.
[19:01] <GridCube> im using xchat, but thats an usual behaviour in any irc program
[19:01] <__0x57__> yeah but in mine it doesnt come up red
[19:01] <__0x57__> its orange or white, cant remember
[19:01] <xubuntu604> I hear that IRC is insecure.
[19:01] <__0x57__> its as secure as your connection..
[19:01] <GridCube> xubuntu604, __0x57__ this matters are not on the topic of support, so if we could move this chat to #xubuntu-offtopic
[19:02] <GridCube> that be great
[19:02] <__0x57__> aye cap'n
[19:03] <xubuntu604> What is with this enforcement!?
[19:03] <GridCube> !coc | xubuntu604
[19:03] <xubuntu604> What did you do to me?
[19:04] <GridCube> i sent you the Code of Conduct (coc) factoid :P
[19:04] <knome> xubuntu604, unless you have a support question, please keep to #xubuntu-offtopic or we might have to remove you from this channel. thanks for understanding
[19:06] <xubuntu604> That's just mean! Why isn't GridCube being warned? He doesn't have a support question.
[19:06] <knome> xubuntu604, if you want to discuss the policies further, you can join #ubuntu-ops.
[19:07] <GridCube> xubuntu604, thats because im inviting you to move to a better channel, not because i have a problem with you
[19:07] <GridCube> :)
[19:07] <xubuntu604> Oh, I see.
[19:07] <xubuntu604> Well, I'm just about to restart my computer anyway. So goodbye!
[19:21] <gdos> so how'd i get 2 versions of Python (2x & 3x) installed on my system? doesn't it come with 2x by default?
[19:25] <__0x57__> maybe you need both because you use a python app which required 3.x ?
[19:25] <__0x57__> its not a problem having bioth instaleld as some developers write code for python 3 which wont always with with 2.x
[20:40] <DJJeff> my Thunar and Mousepad keep locking up and freezing
[20:40] <DJJeff> I just ran a quick strace on the pid of the running Mousepad all I got was
[20:41] <DJJeff> root@gigabyte-H55M-UD2H:/# strace -p 4282 -fF
[20:41] <DJJeff> [pid  4282] write(2, "\n(mousepad:4282): GLib-GObject-C"..., 147
[20:41] <DJJeff> at it just hangs there
[20:41] <TheSheep> use lsof to see what file is that
[20:42] <TheSheep> but I guess 2 is stderr
[20:42] <TheSheep> you could look into your .xsessionerrors
[20:42] <DJJeff> [pid  4282] write(2, "\n(mousepad:4282): GLib-GObject-CRITICAL **: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed\n",
[20:46] <DJJeff> here is a big list of crap about pid 4282 | http://pastebin.com/5u7e7iga
[20:53] <DJJeff> I did apt-get purge mousepad and reinstalled it still locks up and freezes
[20:54] <DJJeff> same with Thunar
[20:54] <DJJeff> so its not that applications fault its something else
[20:55] <sindre> Hey. Quick question. I've installed Xubuntu with one user. But I want to be able to switch between a steam session and xbmc session. Is it possible to set up the login window with one icon for user with steam session and one for user with xbmc session?
[20:55] <DJJeff> here is output from ldd /usr/bin/mousepad | http://pastebin.com/kq57C157
[20:56] <sindre> By default settings you have to change the session before login in
[21:03] <DJJeff> I guess I should say im running libglib2.0-0  (2.38.0)
[21:07] <brainwash> DJJeff: any reason why 2.38?
[21:08] <DJJeff> is that bad?
[21:08] <DJJeff> I am running 13.10 Saucy
[21:08] <brainwash> xubuntu 13.04 does not ship with 2.38, 13.10 does
[21:09] <brainwash> which is not supported in this channel :/
[21:09] <brainwash> #ubuntu+1 or #xubuntu-devel
[21:12] <DJJeff> 13.10 is set to release this month
[21:12] <DJJeff> says https://wiki.ubuntu.com/Releases
[21:14] <brainwash> see https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[21:14] <brainwash> October 17th
[21:15] <brainwash> and you should consider filing a bug report on launchpad
[23:04] <kyo82> sera
[23:04] <kyo82> un aiuto per attivare i suoni di sistema? grazie
[23:06] <David-A> kyo82: espanol o portugese ? (this is for english, officially)
[23:06] <kyo82> sorry i'm italian
[23:06] <Unit193> !it
[23:07] <kyo82> thanks
[23:07] <kyo82> bye ;)
[23:14] <oswaldo> hi I blew up my original user and now I cant be root anymore
[23:14] <oswaldo> any recomendation?
[23:15] <David-A> oswaldo: if you have no other user with admin privileges on the system it will be a little difficult
[23:16] <oswaldo> David-A: can I do an init 3 or something?
[23:16] <Poisoned_Dragon> oswaldo, is the new account an admin account?
[23:17] <oswaldo> Poisoned_Dragon: no
[23:17] <Poisoned_Dragon> oops
[23:17] <oswaldo> we delete the default account
[23:17] <oswaldo> and the new accounts don't have that
[23:17] <oswaldo> I want to know how to make new accounts with admin accounts first of all
[23:18] <oswaldo> and then, if init 3 can recover the original root account
[23:18] <Poisoned_Dragon> the root account hasn't left
[23:18] <Poisoned_Dragon> it's still there
[23:18] <David-A> oswaldo: do you have an option for "recovery" mode in the grub boot menu?
[23:18] <oswaldo> yes
[23:19] <oswaldo> David-A: not sure, I am on the current system so I cant check
[23:19] <oswaldo> let me se the /boot folder
[23:25] <colehub> So.
[23:26] <colehub> Xubuntu.
[23:35] <JZA> hi I need to know how to boot into an SD card
[23:35] <JZA> I installed xubuntu into the SD card but fail during the grub setup
[23:35] <JZA> I wonder how can I boot into it from another USB drive
[23:35] <JZA> basically load the MBR and point to the SD card on the grub menu