[05:01] <RAOF> Oh, dear.  You know things are going wrong when you start to think “you know, this would be much easier if mesa just used autotools like a sensible project.  How much effort could it really be, I wonder…”
[05:05] <ilmari> let met guess, you found out just how much effort it was?
[09:59] <BUGabundo> good morning
[09:59] <BUGabundo> 3D accelaration broke last night
[09:59] <BUGabundo> with the _unsupported_ 3D support in nouveau in natty
[14:53] <kklimonda> bah, how can I see what makes my X use 30% of cpu all the time?
[14:53] <kklimonda> well, it's probably firefox but why? :/
[14:54] <hyperair> wasn't there an xtop or something
[14:54] <ilmari> xrestop
[14:54] <ilmari> not sure if it shows cpu time spent on behalf of clients, though
[14:55] <kklimonda> I should probably restart my system anyway - X is using over 200MB..
[20:45] <joumetal> does bug #674112 have enough information to be confirmed (backtrace)
[20:45] <ubot4> Launchpad bug 674112 in xorg (Ubuntu) "XOrg Segmentation Fault with XServer when running MultiSeatX (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/674112


[14:13] <louisdk> I've a backend and a frontend. That'll not connect. Mythbuntu 12.04 with Mythtv 0.27. frontend says that the IP might be wrong, but everything  seems all right and the backend server is running.
[14:20] <Hydroponx> what address is the backend listening on ?
[14:21] <Hydroponx> and is your mysql user account configured to allow remote connections ?
[14:31] <louisdk> Hydroponx: The backend is configured with bind-adress <IP_ADDRESS> which is also typed in mythtv-setup. When connecting from the backend with "mysql -umythtv -pPassword -h <IP_ADDRESS>.
[14:52] <Hydroponx> can you connect to mysql directly from the remote frontend machine?
[14:59] <louisdk> Hydroponx: Yes I can.
[15:08] <louisdk> If I type "telnet localhost 6543" on the backend I get in. However if I type "telnet <IP_ADDRESS> 6543" from the frontend I'm unable to connect. I don't understand this as the pin code on the backend is set to 0000 and therefore i should allow other frontends to connect.
[15:14] <Hydroponx> firewall ?
[15:14] <Hydroponx> or is your backend only configured for localhost  ?
[15:27] <louisdk> Hyldroponx: I have no firewall on the internal network. And as I see it my backend is configured for 192.168.1.x. Conf files: http://pastebin.com/F8d9vDUC
[15:28] <louisdk> <IP_ADDRESS> is the ip of my backend
[15:36] <Hydroponx> well, mysql is configured for all addresses, yes
[15:36] <Hydroponx> but, can you telnet to <IP_ADDRESS> 6543 on the backend itself?
[15:37] <louisdk> Yes. telnet <IP_ADDRESS> 6543 works fine on the backend.
[15:39] <Hydroponx> and can you browse the internet from the frontend?
[15:40] <louisdk> wait. I can also to <IP_ADDRESS> 6543 from my laptop but not from my frontend, so this must be a network problem on the frontend. Yes I can browse the network on the frontend and ping google.com
[15:47] <tgm4883> louisdk, do you have a firewall on the backend?
[15:48] <louisdk> tgm4883. No I don't. It's a newly installed machine and I've even disabled ufw.
[15:48] <tgm4883> hmm
[15:50] <Hydroponx> whats output of route show?
[16:06] <louisdk> nmap output from my laptop: http://pastebin.com/X9kYWrJP - Same on frontend.


[01:00] <utkarsh2102> vorlon: apologies for not checking it thoroughly and thanks for fixing it! \o/
[06:37] <juliank> vorlon: sil2100 wanted to skip test them
[07:06] <sil2100> mwhudson: hey! Is the fix for https://bugs.launchpad.net/subiquity/+bug/1946668 already available in the stable channel?
[07:08] <sil2100> jibel: morning! Will you be helping us with some regular desktop testing this release?
[07:24] <jibel> sil2100, Good morning, yes, as usual
[07:35] <sil2100> Thank you ;)
[07:36] <sil2100> This might not be the *final* image, but hm, who knows
[07:37]  * sil2100 feels a bit weak today, bad timing
[07:47] <juliank> sil2100: did you skiptest the packages?
[07:47] <juliank> sil2100: yesterday, the meta packages
[07:48] <juliank> sil2100: db-defaults|init-system-helpers|java-common|lsb|ruby-defaults|tcltk-defaults
[07:48] <juliank> sil2100: because vorlon was complaining that none of them were skiptested apparently
[08:00] <sil2100> I did!
[08:00] <sil2100> Did I put wrong versions..?
[08:01] <sil2100> https://git.launchpad.net/~ubuntu-release/britney/+git/hints-ubuntu/commit/?id=cf04445d9050f199f60b8171a8aaf02c93544a43 <- did I miss something here?
[08:03] -queuebot:#ubuntu-release- Unapproved: retext (impish-proposed/universe) [7.2.1-3 => 7.2.2-1] (no packageset) (sync)
[08:03] <sil2100> juliank: most of the packages actually migrated, so I don't know what vorlon was complaining about?
[08:04] <juliank> sil2100: it was 8 hours ago, probably last lines in your backlog for yesterday
[08:04] <juliank> > juliank: so you dropped metapackage-triggered autopkgtest runs; was there also coordination to skiptest these packages so they would migrate? I see base-files was skiptest'ed, but no others
[08:04] <juliank> >  (and 2075 tests 'in progress' on update_excuses, but only 1161 in the queue)
[08:04] -queuebot:#ubuntu-release- Unapproved: accepted retext [sync] (impish-proposed) [7.2.2-1]
[08:05] <sil2100> I think vorlon was just confused, as you can see above ^
[08:05] <juliank> ok
[08:05] <juliank> just wanted to check with you
[08:06] <sil2100> I think it's good, I mean, I might have missed a package or two but I *think* what was supposed to go in went in
[08:06] <sil2100> Maybe vorlon thought we were letting more packages in
[08:14] <paride> sil2100, hi! so it's pretty clear now that https://bugs.launchpad.net/snapd/+bug/1946656 is not a snapcraft.io issue :/
[08:15] <sil2100> paride: yeah... ;/
[08:17] <mwhudson> sil2100: no, let me fix that
[08:20] <sil2100> mwhudson: thanks! And yeah, I see that the snapd team is helping out, but since we already know this is serious, I added LP: #1946656 as a release blocker
[08:21] <sil2100> So if you and dbungert could put a high priority on this one (in case it's somehow subiquity doing something funny!), that'd be awesome ;)
[08:44] <paride> jibel, hi! I can't reach venonat anymore, and it's also offline on the platform-qa-jenkins
[08:44] <paride> are you perhaps doing some cleanup or maintenance there?
[08:47] <mwhudson> ahh
[08:47] <mwhudson> sil2100: for sure
[08:47] <mwhudson> somehow we have two copies of the requests library in the snap :(
[08:48] <jibel> paride, no, I didn't touch anything
[08:55] <paride> jibel, not a good day for venonat to go down :/ I'm looking for a bmc address for the machine
[09:06] -queuebot:#ubuntu-release- Unapproved: gdm3 (impish-proposed/main) [41~rc-0ubuntu1 => 41~rc-0ubuntu2] (desktop-core)
[09:07] <seb128> sil2100, ^ would be nice if we could get that one accepted, it can be turned into a 0 day SRU if really needed but if we get a respin it would be nice to let in, it should fix the session selection being unreliable
[09:09] <mwhudson> sil2100: so i think i have a patch for bug 1946656, do you want me to try to get it landed now or is it ok if it waits for dbungert to have a look at it?
[09:19] <sil2100> mwhudson: you're close to EODing, right? Since of course we'd like to get this landed and released into stable ASAP so we can respin, but if you feel that it would be best to get dbungert's review first, we can wait. Dan has the power to push to stable, right?
[09:19] <sil2100> seb128: let me get to you in a moment!
[09:20] <mwhudson> sil2100: i am basically asleep, yes
[09:21] <mwhudson> sil2100: dan and steve can both push to stable
[09:22] <paride> Once there's .snap available I can verify the fix via `livefs_edit --inject-snap`
[09:24] <mwhudson> paride, sil2100: https://github.com/canonical/subiquity/pull/1094
[09:26] <paride> mwhudson, thanks! I'll build a snap from that branch and test it
[09:28] <sil2100> mwhudson: ok, let's wait for Dan then, thanks for prepping the fix! ;)
[09:28] <mwhudson> sil2100: yeah time to crash
[09:34] -queuebot:#ubuntu-release- Unapproved: linux-firmware-raspi2 (impish-proposed/restricted) [4-0ubuntu3 => 5-0ubuntu1] (raspi)
[09:48] -queuebot:#ubuntu-release- Unapproved: mate-media (impish-proposed/universe) [1.26.0-0ubuntu1 => 1.26.0-0ubuntu2] (ubuntu-mate)
[10:04] -queuebot:#ubuntu-release- Unapproved: mate-notification-daemon (hirsute-proposed/universe) [1.24.1-1 => 1.26.0-0ubuntu2] (ubuntu-mate, ubuntukylin)
[10:08] -queuebot:#ubuntu-release- Unapproved: accepted oem-sutton.simon-baird-meta [sync] (focal-proposed) [20.04~ubuntu3]
[10:12] -queuebot:#ubuntu-release- Unapproved: accepted oem-sutton.newell-cade-meta [sync] (focal-proposed) [20.04~ubuntu3]
[10:23] <sil2100> waveform: uh oh what's this linux-firmware-raspi upload in the queue? Can you give me more context? Is this making the video hang situation better?
[10:25] <sil2100> Ah, no, it's actually for the no-display thing, right?
[10:25] <sil2100> This bug is confusing me
[10:25] <sil2100> Since people are basically using this one bug for like talking about two bugs
[10:27] <waveform> sil2100, sure -- I'd forgotten about this in all the mess around the video freeze thing: a pre-condition of the kernel fix for the no-display bug is a firmware bump for compatibility with the kernel side of things
[10:28] <waveform> had it in the PPA for testing, but completely forgot to push it the archive
[10:28] <waveform> however, this does nothing for the video freeze issue
[10:29] <sil2100> ouch, but we basically need it for the no-display bug to be fixed? And I suppose it's quite serious, right?
[10:30] <waveform> correct
[10:34] <waveform> (I should add while it is obviously serious, it does appear limited to a smaller number of monitors -- we've only had a couple of reproduction cases, while the freeze issue appears ubiquitous albeit less than immediate depending on the connected monitor)
[10:35] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware-raspi2 [source] (impish-proposed) [5-0ubuntu1]
[10:48]  * sil2100 needs to AFK for a bit
[11:02] <seb128> sil2100, did you get to review the gdm upload? it's a tiny patch should be easy to review
[11:30] <Wimpy> Please reject mate-notification-daemon (hirsute-proposed/universe) 1.26.0-0ubuntu2
[11:30] <Wimpy> hirsute ^
[11:31] -queuebot:#ubuntu-release- Unapproved: mate-notification-daemon (impish-proposed/universe) [1.26.0-0ubuntu1 => 1.26.0-0ubuntu2] (ubuntu-mate, ubuntukylin)
[11:55] <sil2100> Wimpy: on it
[11:56] <sil2100> seb128: not yet, will get to it - we might pull it since we might be respinning desktop
[11:56] <Wimpy> sil2100: ty
[11:57] -queuebot:#ubuntu-release- Unapproved: rejected mate-notification-daemon [source] (hirsute-proposed) [1.26.0-0ubuntu2]
[12:00] <sil2100> seb128: I'll accept it, and we can think of migrating it into release
[12:01] -queuebot:#ubuntu-release- Unapproved: accepted gdm3 [source] (impish-proposed) [41~rc-0ubuntu2]
[12:07] <sil2100> hmm, I wonder if maybe the freeze block is botched or something? I don't see linux-firmware-raspi2 in it
[12:08] <sil2100> Even though it's seeded for ubuntu-server-raspi
[12:08] <waveform> sil2100, should be seeded for desktop too -- something to do with it being in restricted maybe?
[12:09] <seb128> sil2100, thx
[12:12] <sil2100> waveform: hm, maybe, I don't know how generate-freeze-block works - anyway, right now it was good that it is migrating, but we need to keep this in mind
[12:12] <sil2100> bdmurray, vorlon: ^
[12:16] <jchittum> marked bug 1944004 as fixed released. If anyone else wants to spin up some s390x or ppcle64 lxd stuff to test, please do. Public cloud pipelines have happy test runs so far leading up to release
[12:17] <sil2100> jchittum: hey! Any blockers from the cloud POV we should still be keeping an eye out for impish?
[12:25] <jchittum> It doesn't look like it. the snapd issue is solved, and the cloud-init + google cloud agent seems unblocked (though it's a workaround, not root cause fixed, I believe)
[12:31] <sil2100> \o/
[12:33] <sil2100> juliank: hey! How's the glib fix going? I saw one review already, you think you can prep an upload now?
[12:36] <juliank> sil2100: no review yet, just comment from NM folks
[12:37] <juliank> sil2100: Philip Withnall just tagged it a minute ago, so maybe it gets reviewed _soon_?
[12:37] <juliank> sil2100: So I can still upload it we can always fix it in proposed
[12:42] -queuebot:#ubuntu-release- Unapproved: glib2.0 (impish-proposed/main) [2.68.4-1build1 => 2.68.4-1ubuntu1] (core, i386-whitelist)
[12:42] <juliank> sil2100: ^ there it is
[12:43] <sil2100> \o/
[12:43] <sil2100> I'll review it in a sec
[12:47] <sil2100> juliank: ok, I see one review comment on the PR!
[12:48] <sil2100> But in generall it looks like a +1
[12:53] <juliank> sil2100: shall I implement the suggestion and reupload?
[12:53] <juliank> it's certainly cleaner that way
[13:02] <juliank> sil2100: The new patch is much smaller, it's nice
[13:05] <sil2100> \o/
[13:05] <sil2100> juliank: if you're confident that it works, upload away o/
[13:05] <juliank> sil2100: uploaded
[13:07] -queuebot:#ubuntu-release- Unapproved: glib2.0 (impish-proposed/main) [2.68.4-1build1 => 2.68.4-1ubuntu1] (core, i386-whitelist)
[13:08] -queuebot:#ubuntu-release- Unapproved: rejected glib2.0 [source] (impish-proposed) [2.68.4-1ubuntu1]
[13:10] -queuebot:#ubuntu-release- Unapproved: accepted glib2.0 [source] (impish-proposed) [2.68.4-1ubuntu1]
[13:11] <bdmurray> sil2100: ubiquity uploaded
[13:11] <sil2100> \o/
[13:11] <sil2100> Reviewing as well
[13:12] -queuebot:#ubuntu-release- Unapproved: ubiquity (impish-proposed/main) [21.10.9 => 21.10.10] (desktop-core)
[13:12] <sil2100> juliank: once the package is built, can you give it a spin to confirm that it's all working as expected and give me a sign?
[13:12] <juliank> sure
[13:16] -queuebot:#ubuntu-release- Unapproved: glm (impish-proposed/main) [<IP_ADDRESS>+ds-1 => <IP_ADDRESS>+ds-1ubuntu1] (ubuntu-desktop)
[13:20] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (impish-proposed) [21.10.10]
[13:24] <juliank> ugh it's still running tests
[13:40] <juliank> sil2100: verified the built binaries
[13:45] <sil2100> juliank: \o/
[13:46] <sil2100> Let me put an unblock hint for that
[13:46] <sil2100> Same for ubiquity
[13:48] <sil2100> seb128: I also put an unblock for gdm3, but please double-check if the binary in -proposed works as expected
[13:49] <seb128> sil2100, ack, thank you!
[13:49] <seb128> sil2100, we are keeping the stack of rebulding in proposed for release?
[13:50] <sil2100> seb128: you mean the no-change rebuilds?
[13:50] <seb128> yes
[13:51] <sil2100> Yeah, those stay blocked, we'll pull them off into JJ
[13:52] <sil2100> Since it's just too late and there's too many, we'd have to slip by a week at least to get them all migrated for impish
[13:52] <dbungert> sil2100: catching up on scrollback, I see we have a plausible fix for subiquity/snapd
[13:53] <sil2100> dbungert: hey! Good to see you! Yes, there's a fix that mwhudson prepared and wanted you to review+merge+release if all good
[13:53] <dbungert> reading it now
[13:53] <sil2100> Thanks
[14:02] <bdmurray> dbungert: There'll also be a new version of ubiquity on the install media later today which should fix bug 1942648. So if you can test that later that would be helpful.
[14:03] <dbungert> bdmurray: will do
[14:43] <vorlon> sil2100, juliank: oh, poor eyesight, I didn't find the skiptest hints that were added but I see them now ;)
[14:58] <bdmurray> vorlon: with the removal of azure-cli do we also want to add it to the sync blacklist as it is in Debian?
[14:59] <vorlon> sil2100, bdmurray: generate-freeze-block: unfortunately this script uses the local apt cache to associate seeded binaries with source packages, which means that if armhf/arm64 is not in your apt sources on the host system, it doesn't land in the block hint
[14:59] <vorlon> bdmurray: my understanding of the removal is that it's removed because it's currently broken, not because it's unfixably broken; but I didn't review the rationale for azure-cli removal since apw had already done it
[15:00] <apw> vorlon, the version in debian is anchient and broken, upstream changes about every two weeks seemingly
[15:00] <bdmurray> "Microsoft further recommends their own PPAs"
[15:00] <bdmurray> that was the part I was thinking about
[15:00] <vorlon> apw: then perhaps you want to add it to the sync blacklist, per bdmurray's question :)
[15:01] <CodeMouse92> I was in that meeting with MS, btw.
[15:02] <CodeMouse92> MS requested that azure-cli be removed because it's too many versions behind, and they didn't *exactly* own the packaging.
[15:02] <apw> vorlon, ack
[15:02] <CodeMouse92> They are WANTING to package a newer version themselves, and hoping for MIR, but there are some other factors that may hold that back.
[15:02] <juliank> sil2100, vorlon So I requeued all tests a couple hours that got lost in deletions; the running to normal queue and running-alwaysfail to huge. But now I uploaded glib2.0 and queues are huge again :(
[15:03] <juliank> shall we move the glib2.0 ahead of the others / into the normal queue?
[15:03] <vorlon> juliank: huge queue backlog seems relatively small now; we could juggle but I'm not sure it actually matters?  I'd give it a few hours and see
[15:04] <vorlon> when does sil2100 want this migrated by
[15:04] <vorlon> I'll work back from that target ;)
[15:04] <dbungert> sil2100: I have merged the subiquity/snapd PR, and am starting the release process there
[15:04] <juliank> I guess it's on all images, so ASAP?
[15:04] <paride> dbungert, great
[15:04] <vorlon> juliank: in that case maybe we want a skiptest
[15:05] <juliank> possibly, maybe he already is planning on / has added one
[15:05] -queuebot:#ubuntu-release- Unapproved: util-linux (impish-proposed/main) [2.36.1-8ubuntu1 => 2.36.1-8ubuntu2] (core, i386-whitelist)
[15:05] <juliank> vorlon: I wonder if we should queue self-tests (foo triggers foo) on normal queue even if foo is huge otherwise
[15:05] <paride> dbungert, I noticed that at the moment we have subiquity 21.10.2+git12.06a2626d in latest/stable/ubuntu-20.10. Is having a +gitX version in stable intended?
[15:06] <juliank> because those self-tests could provide timely feedback on lazy uploaders / syncs :D
[15:06] <paride> dbungert, or was it "stable but not really", and now we'll try to go with 21.10.3?
[15:07] <juliank> which reminds me I did not run the glib2.0 autopkgtests
[15:07] <juliank> I'll move up the self-test
[15:07] <juliank> on amd64
[15:08] <dbungert> paride: that's an appropriate git commit id for post-21.10.2, for a fix for the disk format confirm dialog.  I'm guessing that version was promoted as part of testing that fix.  I'm starting the process to replace with 21.10.3.
[15:09] <paride> dbungert, good, that matches what I expected, thanks
[15:11] <bdmurray> vorlon: so how do you use generate-freeze-block?
[15:11] <vorlon> juliank: I wouldn't object, though I'm not sure it gives us very much benefit overall
[15:11] <vorlon> bdmurray: I'm not sure I've ever been the one to use it officially :)
[15:12] <juliank> vorlon: I think we have uploads failing their own tests a couple of times, could be useful if you then don't need to run all the huge tests :)
[15:12] <vorlon> bdmurray: running it an environment that has all the archs added as dpkg --add-architecture would solve this problem
[15:12] <juliank> people forget to run locally, or it only fails in the cloud :D
[15:13] <sil2100> vorlon: I'd like the glib2.0 migrated ASAP ;)
[15:14] <vorlon> sil2100: so will you skiptest it?  any tests you want to see finish before doing so?
[15:14] <sil2100> Since this is a release blocker fix that I'd like to have in release before we respin
[15:14] <sil2100> eh, crap, forgot glib2.0 triggers so much
[15:14] <vorlon> :)
[15:15] <sil2100> I'd for sure like to see if glib2.0 ADT tests pass
[15:15] <vorlon> ubiquity is also still building
[15:15] <vorlon> on riscv64
[15:15] <sil2100> Rest I think we could just skiptest
[15:16] <sil2100> juliank: considering the nature of the change, would it make sense to also wait for network-manager ADT tests?
[15:16] <sil2100> I don't actually know what we test there tho
[15:16] <vorlon> ok then let me queue those tests in the regular queue
[15:17] <juliank> I did requeue glib2.0 itself and its running already
[15:17] <juliank> I just copied them and did not clean up the dupes so far
[15:17] <sil2100> Thanks!
[15:18] <sil2100> vorlon: so basically right now we're waiting for the following to migrate: glib2.0, ubiquity, gdb3 + waiting for dbungert to push the new subiquity to stable
[15:19]  * vorlon nods
[15:19] <sil2100> *gdm3
[15:19] <vorlon> and that's the subiquity workaround for the snapd restart hang?
[15:19] <dbungert> vorlon: yes
[15:19] <vorlon> (so we're not waiting for snapd itself?)
[15:19] <sil2100> Well, gdm3 is a bit optional, same for ubiquity, but since we respin a lot it made sense to include those
[15:19] <sil2100> vorlon: that's correct, yes
[15:26] <dbungert> paride: 21.10.3 on latest/candidate
[15:28] <paride> dbungert, thanks, I'm baking it into an ISO right now
[15:31] -queuebot:#ubuntu-release- Unapproved: zfs-linux (hirsute-proposed/main) [2.0.2-1ubuntu5.3 => 2.0.2-1ubuntu5.4] (core, kernel-dkms)
[15:39] <paride> dbungert, tested and LGTM, I updated https://bugs.launchpad.net/ubuntu-cdimage/+bug/1946656
[15:39] <dbungert> paride: great, ty
[15:39] <dbungert> I'm letting an autoinstall test run, I've already done a manual test
[15:42] <sil2100> \o/
[15:43] <dbungert> sil2100: subiquity 21.10.3 on channel latest/stable/ubuntu-21.10
[15:45] <sil2100> Great news, thanks a lot o/
[15:50] <bdmurray> vorlon: I ran generate-freeze-block in a chroot w/ the dpkg architectures added and uh the number of packages in the freeze was reduced
[15:53] <sil2100> uh
[15:54]  * vorlon squints :)
[15:54] <vorlon> bdmurray: with all components enabled as well?
[15:54] <bdmurray> indeed, I'm double checking in a VM though
[15:58] <bdmurray> oh, do I also need to configure ports.ubuntu.com?
[15:58] <vorlon> bdmurray: oh yes, you would
[15:59] <vorlon> sorry :)
[16:03] <sil2100> I see that for the new ubiquity the casper ADT tests for amd64 failed, I retried them - but the test failure seems unrelated to anything in ubiquity
[16:05] <sil2100> So I might eventually skiptest ubiquity as well
[16:05]  * vorlon nods
[16:32] <bdmurray> Thanks to vorlon of 10 years ago for https://wiki.ubuntu.com/MultiarchHowto
[16:33] <bdmurray> vorlon: so I added them to /etc/dpkg/dpkg.cfg.d/multiarch and updated sources.list and ran apt-get update and now I still have the same number of packages being output by generate-freeze-block
[16:34] <bdmurray> I confirmed my cache is good via apt-cache policy hello:$arch
[16:40] <sergiodj> vorlon: hi there.  do you think we can proceed with 0-day SRU for u-a-t on Impish?  I'm holding back the uploads for the other series until we get this sorted out
[16:41] <sergiodj> FWIW, the u-a-t team improved the Test Case section of https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1942929.  I reviewed it and it looks good for me
[16:42] <xnox> bdmurray:  i think /etc/dpkg/dpkg.cfg.d/multiarch has not been used for years now. one adds architectures with dpkg --add-architecture and then in sources.list one can specify required architectures in [] as options after deb.
[16:57] <sil2100> I go AFK now for some moments, but I skiptested ubiquity
[16:58] <sil2100> vorlon, bdmurray: I'd say that once we have some positive results on glib2.0 and network-manager tests for the glib2.0 upload, we should skiptest it and let it migrate as well
[16:58] <sil2100> Can you guys keep an eye on it?
[16:59] <bdmurray> I'll keep both my eyes on it
[17:03] <paride> sil2100, do you plan to trigger the build of another round of dailies today?
[17:04] <bdmurray> paride: yes, because of glib2.0
[17:05] <paride> bdmurray, good to hear, as I want to retrigger the iso tests with images with the new subiquity
[17:09] -queuebot:#ubuntu-release- Unapproved: zfs-linux (focal-proposed/main) [0.8.3-1ubuntu12.13 => 0.8.3-1ubuntu12.14] (core, kernel-dkms)
[17:30] <bdmurray> Ah, making progress with generate-freeze-block.
[17:45] <bdmurray> So these would get added to the freeze-block after some hackery
[17:45] <bdmurray> https://paste.ubuntu.com/p/6gXvxHWGYY/
[17:46] <bdmurray> That all seems reasonable so I'll them in
[17:49] <bdmurray> Well except the freeze is britney's hints has less than what I have even without my changes...
[17:56] <bdmurray> I've pushed a new freeze hints
[18:02] <juliank> glib2.0 itself looks good, nm passed on ppc64el so far
[18:03] <bdmurray> juliank: thanks for the update
[18:03] <juliank> I'm just excited :D
[18:17] <vorlon> sergiodj: 0-day SRU is fine; I haven't accepted it yet into -proposed because I didn't want to cause any confusion vs mastering the release media
[18:18] <sergiodj> vorlon: awesome, so I will go ahead and perform the remaining uploads.  thanks
[18:27] <laney> good luck team ;-)
[18:28] <laney> sort of missing tonight's all nighter :D
[18:30] <vorlon> you have my permission to stay up all night anyway
[18:40] <bdmurray> network-manager and glib2.0 passed on amd64 now
[19:00] <juliank> bdmurray: hooray
[19:00] <sil2100> \o/
[19:00] <sil2100> Ok, let me skiptest it after a quick look
[19:02] <sil2100> Seeing that the glib2.0 tests passed on armhf, amd64, ppc64el and s390x - I think it's safe to say we have coverage of at least those two core test suites
[19:03] <bdmurray> Where did the arm64 test go?
[19:04] <vorlon> into a queue
[19:04] <sil2100> And I see it's rather green in other tests too, one regression I see so far, looking at it
[19:04] <bdmurray> update_excuses said it was running
[19:05] <sil2100> hm hmmm
[19:05] <bdmurray> oh, does it say test in progress for everything in the queue?
[19:05] <sil2100> Bail out! GLib-Net:ERROR:../tls/base/gtlsconnection-base.c:1400:g_tls_connection_base_handshake_thread_verify_certificate: assertion failed: (priv->handshake_context)
[19:05] <sil2100> FAIL: libgdata/contacts.test (Child process killed by signal 6)
[19:05] <vorlon> bdmurray: yes
[19:05] <sil2100> Probably unrelated, but it makes me shiver a bit
[19:07] <sil2100> Worrying, since I didn't see this failure before there
[19:08] <juliank> sil2100: looks unrelated, how would network online monitoring break tls handshake
[19:09] <juliank> sil2100: where was that?
[19:09] <sil2100> And it's perfectly fine for other arches, weird!
[19:09] <sil2100> https://autopkgtest.ubuntu.com/packages/libg/libgdata/impish/armhf
[19:10] <juliank> sil2100: I see that on 2021-09-10 20:22 for the gobject-introspection/1.68.0-1build1 libffi/3.4.2-1ubuntu3	 run too
[19:10] <sil2100> \o/
[19:11] <sil2100> Anyway, checked other failures, all flaky tests
[19:16] <mwhudson> good mirning
[19:16] <mwhudson> *morning
[19:16] <mwhudson> how extremely on fire are we feeling today
[19:17] <sil2100> Morning!
[19:17] <sil2100> Less on fire than in my morning I suppose
[19:18] <mwhudson> that's good
[19:20] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (xenial-proposed/main) [27.2.2~16.04.1 => 27.3~16.04.1] (no packageset)
[19:21] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (bionic-proposed/main) [27.2.2~18.04.1 => 27.3~18.04.1] (core)
[19:23] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (focal-proposed/main) [27.2.2~20.04.1 => 27.3~20.04.1] (core)
[19:39] -queuebot:#ubuntu-release- Unapproved: barbican (hirsute-proposed/main) [2:12.0.0-0ubuntu1 => 2:12.0.0-0ubuntu2] (openstack)
[19:58] -queuebot:#ubuntu-release- Unapproved: ubuntu-advantage-tools (hirsute-proposed/main) [27.2.2~21.04.1 => 27.3~21.04.1] (core)
[20:19] <bdmurray> sil2100: glib2.0 seems to have migrated now, shall I create new images?
[20:22] <sil2100> oooh, already?
[20:22] <sil2100> bdmurray: do we have all ubiquity, glib2.0, gdm3?
[20:23] <sil2100> bdmurray: if yes, please spin images indeed o/
[20:25] -queuebot:#ubuntu-release- Unapproved: geonkick (impish-proposed/universe) [2.8.0-0ubuntu1 => 2.8.0-0ubuntu2] (ubuntustudio)
[20:26] <Eickmeyer[m]> ^ That should be good for a 0-day SRU.
[20:37] <bdmurray> rebuilding the world now
[20:54] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Impish Final] has been updated (20211012)
[20:55] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Impish Final] has been updated (20211012)
[21:03] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Impish Final] has been updated (20211012)
[21:05] <RikMills> mparillo: https://i.imgur.com/jXJTxJ2.png
[21:05] <RikMills> bdmurray: ^^
[21:08] <bdmurray> hunh, I checked ubuntu-quality and ubuntu-flavors but not here
[21:11] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Impish Final] has been updated (20211012)
[21:11] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Impish Final] has been updated (20211012)
[21:12] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Impish Final] has been updated (20211012)
[21:13] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Impish Final] has been updated (20211012)
[21:14] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Impish Final] has been updated (20211012)
[21:28] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Impish Final] has been updated (20211012)
[21:39] <bdmurray> dbungert: bug 1942648 should be testable now
[21:46] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Impish Final] has been updated (20211012)
[21:46] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Impish Final] has been updated (20211012)
[21:46] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Impish Final] has been updated (20211012)
[21:46] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Impish Final] has been updated (20211012)
[22:02] <mparillo> bdmurray: If the question is why did I add https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1890173 that is because my bug https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681144 was marked as a duplicate
[22:04] <mparillo> It is not a critical bug, but it certainly is a bug.
[22:05] <bdmurray> mparillo: both of those bugs are quite old could you open a new one?
[22:05] <mparillo> The bug is reproducible in a VM. None of the slideshow links open.
[22:05] <mparillo> Sure.
[22:06] <bdmurray> mparillo: slideshow links are different than the release notes link which first shows up
[22:07] <mparillo> Then my original bug should not be a duplicate.
[22:08] <bdmurray> Let's start off with a new bug and see what we can do about sorting this out
[22:09] <dbungert> bdmurray: bitlocker thing looks resolved
[22:09] <bdmurray> dbungert: cool, thanks for checking
[22:11] <mparillo> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1946803
[22:12] <bdmurray> mparillo: thanks and this is with an impish image?
[22:12] <mparillo> Yup. Let me get the SHA256
[22:13] <mparillo> 282b5125da5a952e8ce59652fe35be618e71a0cfee497715bf91219fbe8cacf9 *impish-desktop-amd64.iso
[22:14] <mparillo> But it has been that way since at least 17.04. I am pretty sure I have tested this on almost every release and beta reported it every time.
[22:16] <mparillo> Also at least one time, I tested on Lubuntu (looks like the 17.10 beta back when once or twice the shipped LXQt and LXDE) and it was on their LXQt installer back then.
[22:23] <vorlon> sil2100, bdmurray: fyi I've just updated https://wiki.ubuntu.com/ReleaseProcess to document the bits that I've been doing each release cycle to clean up i386 binaries; this ought to be officially part of the release process instead of something in my head
[22:23] <vorlon> (I would put it on the discourse, but the checklist seems to be a comment rather than part of the post, oops?  But anyway, it's done for this cycle)
[22:23] <bdmurray> vorlon: you can still edit the checklist
[22:23] <vorlon> ah?
[22:24] <vorlon> interesting
[22:24] <bdmurray> I see a pencil in the header of the comment
[22:24] <vorlon> well anyway, it's done for this cycle, but feedback appreciated so it's clear what to do for the future
[22:25] <vorlon> for the moment the script is in foundations-sandbox which is not public, but better than it being local to my machine
[22:25] <vorlon> also the script is terrible
[22:28] <bdmurray> mparillo: okay, I've recreated the issue
[22:29] <mparillo> Thank you.
[22:30] <mparillo> As I said, I never thought it was a critical bug, but it is good to see it live again.
[22:30] <mparillo> There was this guy once who used to call that kind of thing a paper-cut.
[22:46] -queuebot:#ubuntu-release- Unapproved: mate-menus (impish-proposed/universe) [1.26.0-0ubuntu1 => 1.26.0-0ubuntu2] (ubuntu-mate)
[23:30] <bdmurray> I don't know where our riscv64 builds went
[23:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Impish Final] has been updated (20211012)
[23:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Impish Final] has been updated (20211012)
[23:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unleashed [Impish Final] has been updated (20211012)
[23:40] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Impish Final] has been updated (20211012)
[23:49] <bdmurray> well there they are!
[23:50] <jawn-smith> nice, good timing


[00:10] <chu> Anyone care to pop into #ubuntu for a second?
[01:02] <cprofitt> hey all
[01:02] <bazhang> hi
[02:09] <elky> if mr sparky shows up here, someone give him a lecture about how racism is bad, since he just tried to tell chu that trailerpark people in california are "indians"
[02:17] <LordOfTime> someone should watch WHAT_UP if he comes back, he was being extremely counterproductive and trolling in #ubuntu.
[03:03] <AtomicSpark> Random.
[04:34] <jagginess> AcidRain has been banned on perl and is trolling on #ubuntu
[06:33] <bazhang> DFrostedWang, how can we help you
[08:09] <chu> Hey speak of the devil - hello ikonia :)
[08:15] <ikonia> ?
[12:08] <bazhang> chakra is arch?
[12:08] <bioterror> yes and no
[12:09] <bazhang> ok
[12:09] <bazhang> so a kind of arch MINT
[12:09] <bioterror> yep
[12:09] <bioterror> lives it's own life
[12:10] <jussi> its a MUTANT!
[12:10] <DJones> You called?
[12:11] <jussi> hehe
[12:11] <jussi> DJones: no, you are an extreme mutant, sorry
[12:11] <jussi> :P
[12:11] <bioterror> Toxic Avenger?
[12:11] <DJones> Thank you, its nice to know my talents are appreciated
[12:11] <DJones> bioterror: Only when I eat baked beans
 !beer test
[18:49] <Psi-Jack> * RaTTuS|BIG Gives e-bree to test
[18:49] <Psi-Jack> Noticing of an auto-responder bot. ;)
[18:50] <mneptok> CTCPs as mIRC. which really says nothing.
[18:50] <Unit193> heh, I was right, it is MIRC.
[18:50] <Psi-Jack> heh
[18:51] <Psi-Jack> Anyways, laters. ;)
[19:32] <IdleOne> DFrostedWang: Can I help you with something?
[19:32] <DFrostedWang> No, my client auto joins
[19:32] <DFrostedWang> Sorry
[19:34] <Unit193> IdleOne: bf in k-ot
[19:35] <IdleOne> yeah, I don't have access to change it
 Dr_willis: whoops I rm rf'd /!
[23:24] <bazhang> apparently thinks that's funny


[00:00] <charlie-tca> It does. It let's us know what the images are doing, which lets the developers know what is broken.
[02:55] <Unit193> Bug 807338 is a dupe of Bug #811524 ?? Not quite... Not in my mind anyway
[02:58] <charlie-tca> not anymore
[02:59] <Unit193> Thanks, I got that change in my email and I didn't want to change it since that person has way more karma :P
[03:03] <charlie-tca> If that person really thinks they are duplicates, he needs to state why
[03:04] <charlie-tca> He probably got that karma by marking that a duplicate
[03:04] <Unit193> (I didn't look at the correct sign) I'm also new to bug reporting.
[03:34] <micahg> Unit193: don't worry about karma much, people can get it for all types of silly things, good things as well, I'd suggest installing firefox-lp-improvements from ppa:gm-dev-launchpad and you can see who's in bug control on each comment
[03:34] <micahg> Unit193: even then, if you think there's a problem, feel free to raise it, we're only human
[03:37] <Unit193> micahg: Thanks. I have LP_karma_suffix 1.2, I just looked at the wrong person in the other report (Sure I'm an idiot, but the person had over 10K). Thanks for saying I should say something about it as I did this time (Wasn't sure if I should bother)
[03:37] <micahg> Unit193: asking never hurts
[03:37] <Unit193> I know karma is also VERY lose
[03:38] <micahg> I actually think it should be a dupe of bug 809890
[03:39] <Unit193> That very well could be
[03:45] <charlie-tca> micahg: comment if you mark it a dup, please
[03:45] <micahg> I usually just use the standard dupe comment when I dupe stuff
[03:45] <charlie-tca> Although I will trust you further than the 29 points of karma
[03:47] <Unit193> Hmmm... I guess I need to search more before reporting a bug... (I have 55 so far :P )
[03:49] <micahg> Unit193: most of my karma at this point is uploads, then bugs, I used to have a lot of karma in the answers section
[03:50] <charlie-tca> I used to have karma, too
[03:50] <micahg> charlie-tca: you still do :)
[03:51] <charlie-tca> micahg: if you don't dup those, I will investigate tomorrow. too tired tonight.
[03:51] <charlie-tca> I have a small amount now, I should be over 10,000 by this point in the cycle
[03:53] <micahg> well, a lot of people are doing bug things, which I think might be good
[03:53] <Unit193> I'm a tester/irc helper, not a bug reporter/dev.  I should be more able to run one tomorrow
[03:53] <charlie-tca> hm, picked up an old Dell desktop at a yardsale for 10 dollars, come to find out, 2.8GHz p4, 1GB ram, and 64bit. needs an up-to-date video card to go with the 160GB SATA drive in it
[03:53] <micahg> \o/
[03:54] <charlie-tca> I took it because they really wanted to get rid of it...
[03:56] <Unit193> I would do real installs if I could figure out a way to get it installed without using CDs or flash (I know, taking out all the options)
[03:56] <charlie-tca> You can, you can make the image run in a loop and install from the hard drive.
[03:57] <charlie-tca> You should google for that
[03:57] <charlie-tca> or I will ask tomorrow, when a user I know is doing that is online
[03:59] <charlie-tca> hm, got to go bang my head on the pillow now.
[03:59] <charlie-tca> good night
[04:09] <Unit193> Good night
[04:10] <micahg> night charlie-tca
[13:34] <charlie-tca> Good morning
[17:08] <charlie-tca> mr_pouit: Is this going to cause us more trouble than it is worth?
[17:08] <charlie-tca> http://blog.launchpad.net/bug-tracking/automatic-confirmation
[17:10]  * micahg thinks that makes sense to some extent
[17:12] <charlie-tca> I have seen too many bugs marked confirmed that never get looked at, since confirmed should mean there is enough information to work on it
[17:16] <micahg> nope, confirmed just means it can be reproduced (or at least it should mean that, otherwise triaged is worthless)
[17:17] <charlie-tca> \o/
[17:17] <charlie-tca> that's right
[17:17] <charlie-tca> I forgot that part, huh?
[17:18] <micahg> :)
[19:19] <knome> is it only me, or is "new separator" on alacarte not working?
[21:43] <charlie-tca> Unit193: how to install without a cd or usb drive -
[21:43] <charlie-tca> http://p.bugabundo.net/tag/grub2
[21:45] <Unit193> charlie-tca: Alright, that may be something to try
[21:52] <charlie-tca> and, if that don't work, try http://ubuntuforums.org/showthread.php?t=1549847
[21:53] <Unit193> Is Xubuntu trying to be lightweight?
[21:53] <charlie-tca> lighter than Ubuntu
[21:53] <charlie-tca> depends on your definition of lightweight


[01:48] <Croran> I am having some trouble with using the Alt key for keyboard shortcuts in Bionic.
[01:50] <Croran> running sudo showkey -k in a termal and then pressing Alt+PrtSc shows a press and release for keycode 56 (Alt) before another press for Alt and then press and release for PrtSc and then release for Alt.
[01:50] <Croran> I didn't press Alt twice, so there should only be one release. I hope that gives someone a clue to help me.
[01:53] <Croran> I do have multiple keyboard 'languages' installed - English (US), and English (US, Intl, with dead keys), but I have English (US) currently selected.
[02:19] <robert_ancell> jamesh, any feedback you want to give on https://github.com/snapcore/snapd-glib/pull/64 ?
[02:19] <gitbot> snapcore issue (Pull request) 64 in snapd-glib "Support new /v2/interfaces&select= API, deprecate old API" [Open]
[02:20] <robert_ancell> I changed a few small things, but it's mostly your original branch.
[02:28] <jamesh> robert_ancell: looks good.  I never got around to trying to extend the snapd side of the API to provide the info I wanted, which is why my PR languished
[06:11] <didrocks> good morning
[06:12] <duflu> Morning didrocks
[06:13] <didrocks> hey duflu
[07:24] <seb128> hey didrocks, duflu, good morning desktopers
[07:24] <didrocks> salut seb128
[07:24] <seb128> didrocks, en forme ? passé un bon w.e ?
[07:25] <jibel> hi all
[07:26] <ricotz> hey desktopers
[07:26] <ricotz> I am hoping dealing with armagadd-on-2.0 is top priority
[07:26] <ricotz> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1827727
[07:26] <ubot5`> Ubuntu bug 1827727 in Mozilla Firefox "All plugins disabled due to expired cert" [Critical,Confirmed]
[07:26] <didrocks> seb128: oreilles très bof, sinon ça va, et toi ?
[07:26] <didrocks> salut jibel
[07:27] <seb128> didrocks, :-(
[07:27] <seb128> hey jibel, had a good w.e?
[07:27] <seb128> hey ricotz
[07:27] <didrocks> hey ricotz
[07:27] <ricotz> seb128, didrocks, hi
[07:27] <seb128> ricotz, Oliver and chrisccoulson were discussing it over the w.e so I guess it is
[07:28] <ricotz> ok, no one is to blame here, except mozilla :(
[07:30] <jibel> seb128, ça a été et toi?
[07:31] <seb128> w.e tranquille ici
[07:31] <seb128> ricotz, I wonder how they managed to screw like that :-/
[07:42] <duflu> Oh hi seb128
[07:43] <seb128> hey duflu, had a good w.e? how is monday going so far?
[07:43] <duflu> seb128, the weekend was productive but uneventful. I fixed things and I cleaned things. Same today really. You?
[07:46] <seb128> w.e was nice, we still were in the north of France at my gf's place, didn't do much out but it was relaxing. We drove back yesterday, no issue nor traffic jam which was good. Back to my normal desk today!
[07:47] <duflu> Sounds nice
[07:50] <oSoMoN> good morning desktoppers
[07:50] <didrocks> salut oSoMoN
[07:50] <oSoMoN> salut didrocks
[07:54] <duflu> Hi oSoMoN
[07:59] <seb128> lut oSoMoN, en forme ? bon w.e ?
[08:00] <oSoMoN> hi duflu
[08:01] <oSoMoN> salut seb128 ! très bon week-end au sud de la Catalogne, premier bain de mer de l’année :) et toi?
[08:02] <seb128> oSoMoN, bon w.e, dans le nord de la France par contre et 11°C donc pas de quoi se baigner ... ;)
[08:05] <jibel> petit joueur ;)
[08:14] <Nafallo> o/
[08:16] <oSoMoN> salut jibel, hey Nafallo
[08:32] <Nafallo> hehe. found the workaround for the firefox bug in the ticket atleast ;-)
[08:42] <oSoMoN> Nafallo, do you mean bug #1827727 ?
[08:43] <ubot5`> bug 1827727 in Mozilla Firefox "All plugins disabled due to expired cert" [Critical,Confirmed] https://launchpad.net/bugs/1827727
[09:03] <ricotz> oSoMoN, hi, please upload ff 66.0.4 build3
[09:03] <oSoMoN> on it
[09:03] <ricotz> okay
[09:11] <Nafallo> oSoMoN: yeah, https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1827727/comments/22
[09:11] <ubot5`> Ubuntu bug 1827727 in Mozilla Firefox "All plugins disabled due to expired cert" [Critical,Confirmed]
[09:11] <Nafallo> just need to remember to require signatures again when the package is updated :-)
[09:13] <oSoMoN> Nafallo, mozilla rolled out an updated certificate via the Normandy mechanism, you should have gotten it without the need to do anything on your part, provided you didn't disable Normandy in your settings (it's enabled by default)
[09:18] <Nafallo> hmm. well, I definately had the bug before I changed things. how can I check if Normandy worked?
[09:19] <Nafallo> app.normandy.first_run = false
[09:19] <Nafallo> .enabled = true
[09:19] <tomreyn> about:studies would list a 'study' referring to the mozilla bugzilla id
[09:20] <Nafallo> pref-flip-search-composition-57-release-1413565 only one on the list
[09:21] <Nafallo> we do alter settings as part of our corporate install though ;-)
[09:22] <tomreyn> i think you also need app.shield.optoutstudies.enabled;true (which should be the same as "Allow Firefox to install and run studies" at about:preferences#privacy i *think*
[09:22] <Nafallo> pref("datareporting.policy.dataSubmissionEnabled", false); ← this could be related :-)
[09:23] <Nafallo> but yeah, rather than attempting to change policy, I'll wait for the .4 update ;-)
[09:24] <oSoMoN> Nafallo, I'm preparing it at the moment
[09:24] <Nafallo> :-)
[10:40] <dupondje> Nafallo<EMAIL_ADDRESS>[10:40] <dupondje> you can just install this :)
[11:40] <Nafallo> dupondje: ta :-)
[13:27] <GunnarHj> https://irclogs.ubuntu.com/2019/05/03/%23ubuntu-desktop.html#t12:03
[13:28] <GunnarHj> seb128, sil2100: Please see my question about possible langpack update. ^
[13:29] <seb128> GunnarHj, hey, Lukazs is around today, also I'm unsure it's of high importance in a non LTS cycle
[13:30] <seb128> I mean it would be nice to fix, but if it's not fixed it's also not the end of the world
[13:31] <seb128> it's a non LTS and most user understand english and that's not an UI you use every day
[13:31] <GunnarHj> seb128: Yeah, it's to determine the importance I asked you. Let's sil2100 decide.
[13:52] <sil2100> GunnarHj: hey! Looking
[14:30] <sil2100> GunnarHj: hm, I guess it's something worth consideration, but more like something to do if there's any free cycles
[14:31] <sil2100> GunnarHj: problem is also that we'd either have to do it tranditionally, with a call-for-testing and such, which as we know will result in possibly only 3-4 languages being updated
[14:32] <sil2100> Or risk it with updating all, since we have no automation set up for the testing
[14:55] <Trevinho> morning ppl
[15:03] <seb128> good morning trevinho, how are you? had a good w.e?
[15:04] <Trevinho> seb128: yeah, good one. Great sightseeing in oaxaca area, thanks... yours?
[15:04] <seb128> was nice, in the north of france, most relaxed which was good
[15:05] <Trevinho> I went to "hierve el agua", which are infinity natural pools. Amazing.
[15:12] <GunnarHj> sil2100: True. To address this issue it would be sufficient to update the language-pack-gnome-$LANG files only.
[15:13] <GunnarHj> sil2100: Btw, you mentioned a while ago that you'd bring up the testing approach for langpack updates at a sprint. Did you ever do that, and if so, what was the reaction?
[15:22] <seb128> Trevinho, nice :)
[15:22] <seb128> trevinho, https://code.launchpad.net/~khurshid-alam/indicator-appmenu/ignore-desktop/+merge/366990 is probably for you to review
[15:23] <seb128> trevinho, oh and well done fixing that gnome-shell ellipsizing issue ;-)
[15:47] <Trevinho> seb128: oh well was easy enough actually... But incredible how a "typo" was preserved for so many releases
[17:41] <teward> anyone have the timeline for Firefox updates?
[17:41] <teward> someone in #ubuntu was asking since the latest 66.0.4 firefox came out < 24 hours ago
[17:50] <sarnold> teward: it looks like builds are in progress https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages
[17:50] <teward> trust sarnold to always know things lol
[17:53] <sarnold> man I'd be lost without my firefox history..
[17:54] <sarnold> (seriously, that's half the friction keeping me from trying qutebrowser.. the knowledge that (a) i'd need to bring over my entire firefox history to qute before using it (b) that I'd need to figure out some way to bring my entire qute history over to firefox when I'm inevitably dissapointed and try to switch back)
[22:08] <JanC> seems like gnome shell in 19.04 also crashes if you have "world clocks" configured (so anybody who had those configured in cosmic won't be able to log in after upgrading to disco)
[22:16] <sarnold> ow :(
[22:17] <JanC> or anybody who configures those after is locked out on reboot/relogin, it seems
[22:18] <JanC> something I've mentioned before: I really don't understand why some JavaScript is allowed to crash the desktop so easily
[22:37] <JanC> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827953
[22:37] <ubot5`> Ubuntu bug 1827953 in gnome-shell (Ubuntu) "when you have "world clocks" configured (e.g. from the Gnome Clocks application), Gnome Shell crashes on login, resulting in a login loop" [Undecided,New]
[22:38] <sarnold> JanC: could you put in that that worked in .. bionic? cosmic? and dies in disco -- that'd probably help whoever looks at it
[22:38] <JanC> I used that in previous versions, yes
[22:41] <JanC> it's sort of explicit from where I mention it crashes if you had it configured before upgrading  :)
[22:42] <JanC> and the "expected behaviour" is how it worked before
[22:43] <sarnold> JanC: woot, thanks!
[22:44] <JanC> I clarified that a bit
[22:46] <JanC> I often chat with people on the US east coast, west coast, in between, Pakistan, Australia, etc.
[22:47] <JanC> so it's useful to have quick acces to their local time sometimes  ;)
[22:47] <sarnold> yeah, one page of my android launcher is devoted entirely to the clock.. ten different timezones on the thing (counting mine)
[22:49] <JanC> Gnome Shell really needs to get a somewhat stable API
[22:51] <JanC> I've seen Gnome Shell crash because some extension used an API version current-2 (so 1 year or so) function
[22:52] <JanC> 1 year old
[23:02] <JanC> also see what I mentioned in here yesterday (quite some people end up with that login loop on upgrade because some extension crashes)
[23:02] <JanC> because some extension crashes Gnome Shell
[23:03] <sarnold> double-ow :(
[23:05] <JanC> I didn't file a bug on that yet because I wasn't sure what caused my crash/loop, but looking at sites like AskUbuntu they mention a couple extensions that cause issues


[00:01] <pramiti> it requires compilation of  kdepim, kdepimlibs, akonadi, and baloo from master.
[00:01] <ikonia> kmail is just a mail app - gsoc is totally different
[00:01] <pramiti> can u tell me how to proceed next ?
[00:01] <ikonia> proceed with what ?
[00:02] <valorie> pramiti: GSoc is not suitable for beginners, no
[00:02] <pramiti> after building environment, how should i start debugging..
[00:02] <valorie> pramiti: http://blogs.fsfe.org/myriam/2013/04/15/so-you-want-to-be-a-summer-of-code-student/
[00:03] <ikonia> pramiti: debugging what ?
[00:03] <valorie> you will need a current kubuntu version, not Ubuntu anyway
[00:03]  * valorie goes off to dinner
[00:04] <pramiti> i want to work on this bug https://bugs.kde.org/show_bug.cgi?id=329039
[00:04] <ikonia> ok, so what's stopping you ?
[00:04] <pramiti> it says relevant code is here baloo/src/file/metadatamover.cpp
[00:04] <pramiti> i cant find the source code
[00:05] <ikonia> you have to install the source package
[00:07] <pramiti> ikonia: i wanted to know. if i download the source and then made some changes. how will i run the appliacation again
[00:07] <pramiti> application*
[00:07] <ikonia> you'd have to rebuild it
[00:08] <pramiti> but i dont understand this.. sudo apt-get kdepim dont install the source code somewhere ?
[00:08] <pramiti> i have to individually download it from git ?
[00:09] <ikonia> no, thats the binary package
[00:09] <ikonia> apt-get source kdepim will download the source package
[00:09] <pramiti> okk.. then i will make changes in sorce package and build it ?
[03:20] <kyfella> Hey ya'll
[03:21] <kyfella> Was out most of the evening.  Doing some backups this evening.  Wow, this is a lotta junk to backup
[03:21] <kyfella> lordie, still working on that triple clicking issue in 13.10
[03:21] <kyfella> Once I get this junk backed up, I am going to wipe it out
[03:42] <kyfella> Any of you guys out there tonight
[03:51] <BleuzMan> hi all, i'm using kubuntu on a computer given to me, it already had it installed. , so anyway. when i click a check box it does not show any X or check in the box.. it's doing this on all gui/de boxes. the boxes are recognized by the os as checked but it's not showing it as so on the screen
[03:51] <BleuzMan> does anyone have any ideas on how to fix that?
[04:50] <frogonwheels> BleuzMan: try a different theme?
[04:51] <frogonwheels> BleuzMan: sounds like a video card issue
[05:24] <alphacrypt> hey I made a full upgrade and got new kernels?
[05:24] <alphacrypt> but it makes a kernel panic at start?
[05:24] <alphacrypt> can I fix or remove it?
[05:42] <one> just downloaded a trojan
[05:42] <one> any way to get rid of it?
[05:43] <one> or do I just ride it?
[05:43] <one> yeeeeeeeeeeee!
[05:43] <one> white horseys everywhere
[05:44] <one> open a tunnel
[05:44] <rww> !antivirus
[05:44] <one> let me look at the digital maps of the new bird syztem
[05:45] <rww> !pony-#ubuntu-offtopic
[05:46] <one> White stallion
[05:46] <one> crack those death machines
[05:46] <one> show me!
[05:47] <one> show me the mappings
[05:48] <one> kmon cracker
[05:48] <one> this is the show me state
[05:48] <one> united state
[05:48] <one> kmon
[05:48] <one> show me the mappings
[05:49] <one> I've got a bunch of horses
[05:49] <one> kmon
[05:49] <one> show me the mappings
[05:49] <valorie> one: please stay on topic
[05:51] <one> whoa!
[05:51] <one> I said ok
[05:56] <one> if I plug in my eee
[05:57] <one> does someone on here want to ssh in and put the software on
[05:57] <one> eee no surrendur
[05:59] <valorie> what software, one?
[05:59] <one> well if it has to be 'ontopic' Kubuntu
[06:00] <valorie> you can install software yourself, using either the gui or the commandline
[06:00] <one> I have other requests though
[06:00] <valorie> you were already told the name of the offtopic channel by rww
[06:00] <one> I want HNS
[06:00] <one> true HNS
[06:01] <one> not this second edition stuff where something keeps editing things
[06:02] <rww> what is an HNS?
[06:02] <rww> oh, you moved, nvm
[06:14] <lordievader> Good morning.
[06:15] <alphacrypt> hey
[06:15] <alphacrypt> how to start something in background, like dolphin sudo in terminal, & behind and nothing happens
[06:16] <lordievader> alphacrypt: Putting an & behind a command usually works. An alternative is hitting ctrl+z and then typing bg<enter>.
[06:17] <alphacrypt> lets try
[06:17] <alphacrypt> nice it works
[06:18] <alphacrypt> & way will not work with sudo dolphin somehow?
[06:19] <lordievader> alphacrypt: Also it is a good idea to use 'kdesudo' for gui apps in KDE.
[06:19] <alphacrypt> ok
[06:19] <lordievader> If you want to run them as root, that is.
[06:19] <alphacrypt> but there its the same problem?
[06:20] <alphacrypt> would like to be able to use the terminal window not to have it in query as "logwindow"
[06:20] <lordievader> Don't know. Rarely start Dolphin from the terminal, starting it as root is even more rare for me.
[06:20] <alphacrypt> ok
[06:20] <lordievader> ls and cd is a good enough filebrowser for me :)
[06:21] <alphacrypt> youre linuxuser as it should be :D
[06:21] <lordievader> ;)
[06:37] <alphacrypt> hey guys got new kernels and it just panics
[06:38] <valorie> alphacrypt: are you using the beta?
[06:38] <alphacrypt> 13.10
[06:39] <valorie> hmmm
[06:39] <valorie> please file a bug
[06:39] <alphacrypt> how to do?
[06:39] <valorie> sounds serious
[06:39] <alphacrypt> using older kernel
[06:39] <valorie> !bug
[06:39] <valorie> this will be an ubuntu-bug
[06:39] <valorie> not KDE
[06:40] <alphacrypt> maybe I use the wrong saying
[06:40] <valorie> no, I get what you are saying
[06:40] <alphacrypt> if I boot it I got stucked log and there stands something like panic but I am not that good
[06:40] <alphacrypt> ok
[06:40] <lordievader> alphacrypt: What kernel version are you trying to boot?
[06:40] <lordievader> !info linux-image-generic
[06:40] <alphacrypt> how to get it to know
[06:40] <alphacrypt> !info linux-image-generic
[06:40] <lordievader> alphacrypt: You can see in grub.
[06:41] <alphacrypt> yes
[06:41] <alphacrypt> on runningsystem
[06:41] <lordievader> Current for Saucy is <IP_ADDRESS>.19
[06:41] <alphacrypt> otherwise wanna type it down
[06:41] <alphacrypt> yes that ones
[06:41] <alphacrypt> should be 19 have also 18 as seperate but I'm not sure with that
[06:42] <lordievader> alphacrypt: Hmm, <IP_ADDRESS> works here. But like valorie says, file a bug.
[06:45] <alphacrypt> ok /var/log/kern.log there it should be right
[06:45] <alphacrypt> but its always the most current one?
[06:45] <alphacrypt> so I need to get the error and then just backup the file?
[06:49] <alphacrypt> ohhh
[06:49] <alphacrypt> there are lot of different ones see it because of timestamps
[06:49] <lordievader> Err, it might be that he automatically makes it kern.log.1, but that might also be logrotate's doing.
[06:50] <alphacrypt> yes there are lot more files with numbers
[06:50] <alphacrypt> ok I search for panic
[06:50] <alphacrypt> hmm
[06:50] <alphacrypt> no
[06:51] <alphacrypt> its fine, have to note the error down and make find... in terminal something like that?
[06:51] <alphacrypt> grep?
[06:51] <alphacrypt> lets try that
[06:55] <lordievader> When it panics it will not be able to write to the log (probably)
[07:29] <alphacrypt> it would help to know if the kernel would be replaced?
[07:30] <alphacrypt> so now got the problem and won't use that one but will it be sometime resolved or can I update it?
[07:37] <valorie> alphacrypt: to discuss the matter directly with the devels who work on the k/ubuntu kernel, try #ubuntu-kernel
[07:37] <valorie> very friendly folks there
[07:37] <alphacrypt> ok thanks
[08:24] <TuxMario> Hello, Have you any softwareto  recommand  for video recording of the desktop ? Thanks
[08:27] <valorie> TuxMario: muon discover doesn't show you anything cool?
[08:28] <lordievader> TuxMario: "apt-cache search desktop record" shows quite a few things. Not sure if there is anything good in there though.
[08:29] <valorie> what's nice about discover is the ratings and reviews
[08:43] <TuxMario> Valorie: I didn't know Muon Discover. Usefull ! I already tested recordmydesktop but Kazam is recommanded (5 stars) I'll have a look. Thanks
[08:45] <valorie> TuxMario: as of 14.04 it will be our default software center
[08:46] <valorie> developed by our own kubuntu guys
[08:47] <TuxMario> Lordievade: Thanks for this command even if answers are not very interresting this time
[08:59] <valorie> apt-cache search is useful for a lot of stuff
[09:13] <TuxMario> Valorie: Muon Discover is very good. Congratulations to Kubuntu team! , apt-cache serach is now in my personnal FAQ. Bye
[09:13] <lordievader> TuxMario: Have fun :)
[10:38] <oscarr> hello
[10:38] <lordievader> Hey oscarr
[10:38] <lordievader> How are you doing?
[10:40] <oscarr> fine, but have problem. I did install kubuntu 13.10 on my ant`s notebook and now i have problem because she has many wma audio files, and she wants to burn them to cd. But there is issue - K3B crashes averytime when trying to add wma-file to project
[10:41] <oscarr> on my pc i have debian with kde and k3b works perfectly
[10:41] <lordievader> oscarr: Convert them to wav before burning with K3B?
[10:42] <oscarr> she is 60years old and before was on windows ... she need complex solution
[10:42] <oscarr> i have to repair k3b
[10:43] <oscarr> i know that its not k3b bug itself but its bug of avcodec library used in ubuntu
[10:44] <oscarr> its part of ffmpeg
[10:44] <lordievader> oscarr: File a bug then.
[10:44] <lordievader> Wasn't avcodec a fork of ffmpeg?
[10:44] <oscarr> that bug is known from 2011
[10:44] <oscarr> yes
[10:44] <oscarr> avcodec is fork of ffmpeg for ubuntu
[10:45] <oscarr> and the question is: how to change avcodec to real ffmpeg
[10:45] <oscarr> ?
[10:46] <lordievader> oscarr: ffmpeg is still in the repo, but I'm not sure if that will fix your problem.
[10:46] <lordievader> !info ffmpeg
[10:49] <oscarr> i have to try
[10:49] <lordievader> !info avcodec
[11:27] <BluesKaj> "Morning
[12:07] <Incertus> can anyone help me with this: https://forum.kde.org/viewtopic.php?f=224&t=120157 ?
[12:48] <daddy> hi
[12:59] <DaveInFL> Good morning, hoping that someone can help me out.  I just installed v13 of Kubuntu and when it boots and gets to the login screen both the keyboard and mouse are not working.  When the PC boots I am able to get into the BIOS, so I know that the keyboard is working just fine, and it (and the mouse) were both fine during installation.
[12:59] <DaveInFL> I can't do anything at all, not even trouble shoot since I can't log into the machine :(  Anyone ever come across this issue?
[13:00] <BluesKaj> DaveInFL, 13.04 or 13.10?
[13:00] <DaveInFL> The very latest I think...13.10
[13:01] <DaveInFL> Yes, 13.10, that was the only option available to download for 13.x. There wasn't a 13.04 version listed.
[13:01] <BluesKaj> the KB and mouse are usb ?
[13:02] <DaveInFL> Correct
[13:03] <DaveInFL> The mouse and keyboard go through a KVM switch, but was working just fine during installation.  I did try and plug the keyboard directly into the PC but same issue.  Hard to tell if it's just the keyboard/mouse that are not working or if the box has simply crashed!
[13:04] <DaveInFL> Also, it was the 64bit version of Kubuntu that I downloaded
[13:06] <BluesKaj> DaveInFL, try the recovery kernel in grub and if your KB is till working choose "repair broken packages" in the dialog
[13:07] <DaveInFL> I don't even see a grub screen when it boots up! I see the screen that lets me get into the BIOS, and then the screen goes black and the next thing I see is the graphical login screen.
[13:08] <DaveInFL> Sounds like something is wrong and it's not the keyboard/mouse.
[13:08] <BluesKaj> hold the left shift key down after the bios screen to get grub
[13:09] <DaveInFL> Ok, let me give that a try..thanks.
[13:12] <DaveInFL> Ok, just booted to the recovery kernel and a screen comes up with options like: resume, clean, dkpg, etc.  However, cursor keys not working! Very wierd
[13:13] <BluesKaj> could be an ACPI problem, hardware discovery
[13:16] <DaveInFL> No idea...like I said, mouse/keyboard worked just fine during install process!
[13:16] <DaveInFL> I've installed a few different kinds of Linux on this PC and this is the first time I am seeing something like this.  Perhaps I will try version 12.04 and see how that reacts.
[13:18] <BluesKaj> you may need to reinstall with the KB and mouse directly connected, but that's just a guess...I've seen hardware recognition problems before but not after the logibn page loads
[13:20] <DaveInFL> All the other flavours of Linux I have installed I have left the keyboard/mouse in the KVM.  Ok, will give it another try with version 12.04 and see...otherwise I guess I will have to find another flavour of Linux.  Thanks for your help.
[13:34] <__Roey> hi all
[13:34] <__Roey> BluesKaj:  hey!
[13:34] <__Roey> I have trouble hearing sound on my work PC
[13:34] <__Roey> alsamixer shows everything at 100% though
[13:36] <BluesKaj> __Roey,  is the automute enabled in alsamixer ? and which audio chip ?
[13:40] <__Roey> BluesKaj:  82801JI (ICH10 Family) HD Audio Controlle
[13:43] <BluesKaj> hmm, __Roey, cat /proc/asound/modules
[13:43] <__Roey>  0 snd_hda_intel
[13:43] <__Roey>  1 snd_usb_audio
[13:43] <__Roey>  2 snd_hda_intel
[13:45] <BluesKaj> __Roey, then run that command I gave you the other day, the intel driver isn't loading, sudo modprobe snd_hda_intel
[13:46] <BluesKaj> it's listed as card 0, which correct but's not loading due to that bug with intel audio drivers after updates/upgrades etc
[13:46] <miraiE> hi everyone, I wanna make package for plasma widegt, I've found this https://wiki.ubuntu.com/Packaging/Training/Logs/2009-06-18 and it's what I want to do, but I can't find the debian/* example files. where else I can find such tutorial?
[13:47] <__Roey> BluesKaj:  it's loaded
[13:47] <__Roey> BluesKaj:  snd_hda_intel          52267  6
[13:47] <__Roey> BluesKaj:  what was the command, which one?
[13:48] <BluesKaj> sudo modprobe snd_hda_intel
[13:48] <__Roey> yeah that just returns back to the command prompt without outputting anything
[13:48] <BluesKaj> and a reboot might be needed
[13:48] <__Roey> I do lsmod | grep snd_hda_intel, and I see it is loaded
[13:48] <__Roey> BluesKaj:  ahhh that's right
[13:48] <__Roey> just like my system at home
[13:49] <BluesKaj> yes when there's no output that means the driver is loaded correctly, othewise there would be an error
[13:50] <EvilRoey> aye okay.
[13:50] <EvilRoey> So I will try seeing if rebooting fixes the issue
[14:12] <yossarianuk> hi - is kde 4.13 still being planned to be used for 14.04 ?
[14:15] <BluesKaj> yossarianuk, I think so because we're running 4.12.90 on 14.04 here
[14:16] <yossarianuk> good stuff !
[14:16] <yossarianuk> will save having to add the ppa to get it....
[14:19] <BluesKaj> yeah Final Release is less than a month away
[14:19] <BluesKaj> for 14.04
[14:24] <yossarianuk> well 4.12 on 13.10 is very nice
[15:01] <Guillem_> Is there any way of telling kwin not to use the full screen size?
[15:01] <yossarianuk> Guillem_: sorry what do you mean ?
[15:03] <Guillem_> I've a laptop which current nvidia drivers don' t allow resolutions other than 1920x1080
[15:03] <Guillem_> this is painful when connecting a beamer to make presentations
[15:04] <pruebassdetodo_> .
[15:04] <pruebassdetodo_> .
[15:04] <Guillem_> nvidia driver, whoever lets me choose 1024x748(Scaled) but when I do that, desktop is clipped but dimensions are still 1920x1080 (maximized windows, for instance go larger than the view)
[15:05] <pruebassdetodo> .
[15:05] <Guillem_> mwm, xfwm and compiz honor the new size
[15:05] <pruebassdetodo_> .
[15:05] <Guillem_> metacity, mutter and kwin do not
[15:06] <Guillem_> question is, if there is any way to tell kwin, "hey, just use a portion of the available space"
[15:12] <BluesKaj> Guillem_, which nvidia driver are you using?
[15:15] <Guillem_> 319.60
[15:17] <BluesKaj> Guillem_,ok which kubuntu version ?
[15:18] <Guillem_> 13.10
[15:18] <Guillem_> at 12.04 I could not do the (scaled) thing. The (scaled) thing plays with viewportin, viewportout and paning
[15:18] <BluesKaj> Guillem_, then youi should be using the 331 driver, it should be available in additional drivers
[15:23] <Guillem_> BluesKaj:  I can only choose between 304 and 319
[15:27] <BluesKaj> Guillem_, have you updated/upgraded lately?
[15:27] <Guillem_> not very lately but well after 13.10 release itself
[15:28] <DaveInFL> Morning all. Not sure who was helping me earlier with the keyboard/mouse issue but I installed 13.10 32-but and that seemed to work fine.  Now I am up and running with Kubuntu, mouse and keyboard working :)
[15:28] <BluesKaj> Guillem_, suggest you do so and dist-upgrade as well
[15:29] <BluesKaj> Guillem_, that will bring in the latest versions of kde/kwin for your OS
[15:30] <DaveInFL> Coming from Mandriva/Mageia will take some getting used too and one thing I seem to be missing right now is the entire system settings, aka, control panel for windows.  With Mageia it was all centralised and easy to navigate around.  Under Kubuntu I am having a hard time trying to find (gui) where I can change the network settings so that I force the system to a static IP address and not use DHCP.. I can't find where to do that.
[15:30] <DaveInFL> Under system settings there is an internet section but nothing that will let me change from DHCP to static, unless I am completely missing something.
[15:34] <Guillem_> BluesKaj: but 331 is not in the 13.10 repositories, is it?
[15:34] <BluesKaj> Guillem_, it should be
[15:36] <BluesKaj> DaveInFL, this tut is somewhat dated and there's one change needed for /etc/resolv.conf path, it's been changed to /etc/resolvconf/resolv.conf.d/base
[15:36] <BluesKaj> DaveInFL, http://www.cyberciti.biz/faq/setting-up-an-network-interfaces-file/
[15:37] <yossarianuk> Guillem_: the most annoying thing about ubuntu (and its variants) is they don't have the latest nvidia driver
[15:37] <yossarianuk> they ship a version with known bugs in *fixed in later versions) and that don;t support the latest hardware in the name of 'stability'
[15:38] <yossarianuk> its not like they can fix the issues (its closes source..)
[15:38] <yossarianuk> *closed*
[15:38] <BluesKaj> DaveInFL, /etc/resolv.conf still exists but it's overwritten by /etc/resolvconf/resolv.conf.d/base
[15:38] <yossarianuk> the latest nvidia driver (running on opensuse + arch) speeds up pretty much all openGL apps...
[15:39] <DaveInFL> BluesKaj, thanks for that, but shouldn't there be a GUI under system settings for this also?
[15:39] <Guillem_> As far as I check,  331 is not in the 13.10 repos nor in the upcoming 14.04
[15:39] <Guillem_> I should use a ppa (as xorg-edgers) to install it
[15:40] <BluesKaj> Guillem_, if you update and dist-upgrade, the repos should make 331 available
[15:40] <yossarianuk> so the majority of ubuntu + variants are going to miss out on a fairly good speed up.....
[15:41] <BluesKaj> yos so what do you suggest Guillem_ do then ?
[15:41] <BluesKaj> yossarianuk,^
[15:44] <yossarianuk> http://news.softpedia.com/news/NVIDIA-334-21-Drives-Brings-Significant-Performance-Improvements-for-OpenGL-Applications-430519.shtml
[15:45] <yossarianuk> well this is the issue really....
[15:45] <yossarianuk> There should be the latest package....
[15:45] <yossarianuk> when 14.04 is out - i'll maintain a PPA ......
[15:46] <yossarianuk> (don't like x-swat/xorg edgers) they have a habit of updating other packages also.
[15:47] <yossarianuk> you could install manually - but Ubuntu makes that hassle..
[15:47] <yossarianuk> i.e
[15:47] <yossarianuk> http://ubuntuhandbook.org/index.php/2014/03/install-nvidia-driver-334-21-ubuntu-linux/
[15:47] <yossarianuk> (be aware you may have no X after a kernel update, etc).
[15:47] <Guillem_> https://launchpad.net/~joe-yasi/+archive/xorg-related/+build/5569509 ?
[15:48] <yossarianuk> there is this
[15:48] <yossarianuk> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1287753
[15:48] <yossarianuk> for gaming you want the driver.
[15:48] <yossarianuk> if you want to play steam games you want this driver....
[15:49] <yossarianuk> it should be the default.
[15:50] <BluesKaj> yossarianuk, he's just looking for a decent resolution for his laptop, didn't mention gaming afaik
[15:50] <yossarianuk> ah - sorry to confuse the issue.
[15:51] <yossarianuk> Guillem_: you 'could' trythe manual install
[15:51] <BluesKaj> I might try the 334 driver on my desktop pc altho I have no graphics issue there atm
[15:51] <yossarianuk> http://ubuntuhandbook.org/index.php/2014/03/install-nvidia-driver-334-21-ubuntu-linux/
[15:51] <DaveInFL> Another question.  When I do su - <password> it doesn't work.  Not sure why? Only password i
[15:51] <yossarianuk> Guillem_: have you got an xorg.conf?
[15:51] <DaveInFL>  have is my user password.  I didn't see anything during he install to set the root password
[15:52] <yossarianuk> DaveInFL: you need to set a root pass
[15:52] <yossarianuk> i.e
[15:52] <yossarianuk> do
[15:52] <yossarianuk> sudo passwd root
[15:52] <DaveInFL> Thanks
[15:52] <yossarianuk> create a pass - then  su -
[15:52] <DaveInFL> Got it..working now :)
[15:55] <Guillem_> btm I'm going to try 331 from ppa:ubuntu-xswat/x-updates
[15:55] <yossarianuk> ok
[15:55] <yossarianuk> if you still have no joy
[15:55] <BluesKaj> DaveInFL, afaik in order to keep your IP static network manager has to be removed
[15:55] <yossarianuk> try creating an xorg.conf.
[15:55] <Guillem_> I'dont want to install the driver manually... I love the automatic kernel module
[15:57]  * BluesKaj shrugs you shouldn't need a ppa to install the 331 driver
[15:57] <BluesKaj> Guillem_,^
[15:57] <BluesKaj> unless your nvidia card really old
[15:57] <BluesKaj> is
[15:58] <Guillem_> repos don't know about my card...
[15:58] <BluesKaj> Guillem_, which card is it?
[15:58] <BluesKaj> err gpu
[15:59] <Guillem_> Quadro FX 1800M
[16:00]  * dougl googles Quadro FX 1800M
[16:02] <Guillem_> BluesKaj: I don't get it. It is at precise but not at saucy
[16:03] <Guillem_> https://launchpad.net/ubuntu/saucy/+search?text=nvidia-331
[16:04] <Guillem_> vs
[16:04] <Guillem_> https://launchpad.net/ubuntu/precise/+search?text=nvidia-331
[16:05] <Guillem_> OK, I'm rebooting...
[16:08] <dougl> what is the issue with the 1800M?
[16:08] <dougl> no x or poor performance?
[16:09] <Guillem_> Same behaviour.
[16:10] <dougl> Guillem_, sorry what is the issue - not that I can help but am curious and joined late
[16:11] <rcw2> skype has been crashing a lot in Kubuntu 13.10... anyone know if the Kubuntu team is planning to invest more time to resolve the issues in the future, or are they focusing on something else instead
[16:16] <Guillem_> The problem is that my laptop monitor refuses to reduce the resolution. This is a pain when using a beamer, since I cannot do clone displays (laptop resolution is 1920x1080 much larger than typical beamers nowadays)
[16:17] <Guillem_> With nvidia-settings I can reduce the resolution by "scaling" which does sort of viewport manipulation. But, KDE does not adapt to such change.
[16:18] <Guillem_> Neither does GNOME (mutter/mecacity)
[16:18] <Guillem_> Compiz and XFCE do adapt to such change
[16:19] <Guillem_> Thus, I can workaround this by using XFCE (or XFCE+Compiz) when presenting.... just now I had switched to KDE and was confortable with it :P
[16:19] <dougl> and there ya have it :P
[16:19] <EvilRoey> BluesKaj:  hai
[16:20] <dougl> and just as I expected I am completely useless - lol
[16:20] <EvilRoey> BluesKaj:  I'm getting mailed every few minutes with a message like "ERROR: creating snapshot toplevel/toplevel.20140319-1201 -> toplevel.20140319-1201 failed. File exists"  <-- this message comes from the backup script I've put in with crontab -e.  I don't understand why there are like 22 mails about this in root's mail.
[16:20] <BluesKaj> Guillem_, what kind of connection to the beamer, hdmi or vga ?
[16:20] <Guillem_> Just explaining the problem is challenging :P
[16:20] <EvilRoey> BluesKaj:  is it repeating it? is it just re-mailing me agian and again?
[16:21] <EvilRoey> is it tryi ng to issue the command again?
[16:21] <EvilRoey> repeatedly?
[16:21] <Guillem_> BluesKaj: vga. However, I can change the resolution at the monitor which I use through a docking-station (not sure if that is VGA or hdmi)
[16:21] <dougl> Guillem_, yes... I can see that, that card is how old - I derived less than 5 years from my googling confusion?
[16:22] <BluesKaj> EvilRoey, I have no clue , which command ?
[16:23] <Guillem_> hmm, perhaps less than 5 years  old I would guess
[16:23] <Guillem_> "xrandr --q1"  shows several modes, but xrandr only shows the nominal resolution one
[16:26] <dougl> Guillem_, and it is based on the gt2xx architecture... I would guess at using the driver for a 280 and wreck everything and re install... and be no further a head - hope that saves you some trouble.
[16:26] <Guillem_> and I'm seeing that "xrand --q1 -s 0 " (which is 1024x768) does swich to that resolution but KDE doesn't adapt to the resolution change either
[16:26]  * dougl hates resolution issues
[16:27] <dougl> ... aspect ratios in particular
[16:27] <BluesKaj> Guillem_, so essentially ytou're connecting to an outboard monitor, check the setting in system settings>display&monitor>display configuration with the beamer connected. There should be a second display option to set up the outboard resolution
[16:28] <Guillem_> BluesKaj: second monitor behaves just OK
[16:28] <Guillem_> BluesKaj: is just I cannot reduce first monitor resolution to match second monitor
[16:28]  * dougl wants to know what a beamer is?
[16:28] <Guillem_> projector
[16:28] <Guillem_> beamer==projector
[16:29] <dougl> ah!!! we are getting a new one at church
[16:29] <Guillem_> (I'm not a native speaker)
[16:29] <dougl> cant tell
[16:48] <BluesKaj> brb
[16:57] <dougl> Guillem_, what is the model of your beamer?
[16:57] <Guillem_> no idea
[17:42] <SvenOostenbrink> Hi there, on 13.10, since the last update which I applied yesterday, when the screen locks, I no longer see the unlock window asking me for my password. I only see the blue curves background wallpaper, thats it, and I can no longer unlock the laptop, I have to reboot.  Is this a known bug? Also, is there maybe a command line way that I could force unlock from there until there is a solution?
[18:56] <jmzc> hi
[18:56] <lordievader> Hey jmzc
[18:56] <bprompt> allo
[18:57] <jmzc> what is the best solution to reader-writer problem , with reader & writer running on different JVM ? I guess that I must lock the file, but I don't know if there is any better solution
[18:58] <lordievader> jmzc: I get the feeling this question is beter suited for #java
[18:58] <jmzc> lordievader: right ... it was my fault
[18:58] <lordievader> jmzc: Not to worrt ;)
[18:58] <lordievader> worry*
[18:59]  * bprompt hands jmzc  his #java with cream and cinnamon on top
[19:27] <windows> hello
[19:30] <bprompt> allo
[21:56] <Guest57108> anyone know the answer to this one?  I installed Kubuntu 13.10 and there is a darn bug with recognition of USB mouse and keyboard once you get to the LVM Encryption screen. It will work fine up to that point.  Anyone know how to use a live usb to mount an encrypted drive so I can make a modification to initramfs
[21:57] <Guest57108> bug is listed in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194
[21:58] <Guest57108> ubottu, are you saying that that is supposed to be fixed?
[21:59] <jussi> Guest57108: ubottu is a bot :)
[21:59] <Guest57108> oh
[21:59] <jussi> but it appears to be fixed
[21:59] <Guest57108> well, in that case, here is the problem
[22:00] <Guest57108> If I install 13.10 64-bit with an encrypted LVM volume, and then reboot, I can't get the damn keyboard to work to type in an encryption password.  How then can I download the critical fixed patch? LOL
[22:00] <Guest57108> it appears to be a catch 22.  darned if you do, darned if you don't
[22:01] <Guest57108> Any ideas out there?
[22:02] <Guest57108> frankly, I would be willing to try anything at this point
[22:03] <Guest57108> Do I need to back down to 13.04 and then upgrade it?
[22:12] <jussi> Guest57108: there are several workarounds int that bug
[22:12] <Guest57108> what are they
[22:13] <jussi> Guest57108: with all due respect, please read the bug.
[22:19] <valorie> SvenOostenbrink: I don't see it either until the keyboard is used, then the login bit pops right up
[22:20] <valorie> does that not happen for you?
[22:22] <SvenOostenbrink> Nope.. I see it always right away and after this update, I dont ever see it again.. keyboard / mouse does nothing
[22:26] <danielNakata1984> hello every one
[22:44] <valorie> SvenOostenbrink: please file a bug -- you can do it from the konsole if you want, `ubuntu-bug lock-screen`
[22:44] <valorie> !bug | SvenOostenbrink
[22:45] <SvenOostenbrink> valorie: Will do, tks! Is there a way to unlock the screen from the command line, until this is finished? This way, at the very least, I won't have to reboot on every screenlock..
[22:47] <valorie> hmmm, that I don't know
[22:47] <valorie> you might ask that in the bug!
[22:47] <SvenOostenbrink> btw, I guess its ubuntu-bug lockout? "lock-screen" package doesnt exist
[22:47] <valorie> or perhaps `screensaver`
[22:48] <valorie> !info lockout
[22:48] <valorie> I don't think it's that
[22:48] <valorie> !info screensaver
[22:48] <valorie> pfff
[22:48] <SvenOostenbrink> screensaver doesn't seem to exist
[22:48] <SvenOostenbrink> ah, there you go :)
[22:50] <valorie> !info screenlock
[22:51] <valorie> try xscreensaver