[08:31] <jumpingvaibhav> Hi degville
[14:03] <rahulmetre03> hello!
[15:29] <Vansh> Hi
[21:42] <Akshara> Hi
[23:33] <Yash_> hi
[23:48] <AlexGabriel> Hi Friends!!


[18:23] <juliank> just leaving that here, but snap-store on 20.04 breaks installing .deb files? https://www.reddit.com/r/Ubuntu/comments/gh5rcp/til_snap_store_killed_ubuntusoftware_on_default/?utm_medium=android_app&utm_source=share
[18:23] <juliank> also I can't refresh to latest/stable/ubuntu-20.04 channel on groovy, but not sure that's a bug
[18:35] <juliank> hmm seems to work for me (on groovy), maybe they had stable installed before, and not the ubuntu-20.04 channel


[09:24] <ppisati> brb
[10:41] <siretart> apw: sorry for being a PITA :(
[10:43] <apw> siretart, ?
[10:43] <siretart> apw: your patch for fixing the xattr issue in overlayfs does not seem to be sufficient
[10:43] <siretart> bug #1039402
[10:43] <ubot2`> Launchpad bug 1039402 in linux "[quantal] overlayfs over r/o NFS mount fails to overwrite existing files" [Medium,In progress] https://launchpad.net/bugs/1039402
[10:44] <apw> what specifically are you doing and what is failing
[10:44] <apw> and how is it failing
[10:44] <siretart> apw: have you seen the screenshot? it documents my testcase pretty precisely
[10:44] <siretart> https://launchpadlibrarian.net/113349441/screenshot-bug1038075.png
[10:45] <siretart> apw: interestingly, a 'rm /etc/resolv.conf && echo foo >/etc/resolv.conf' does succeed
[10:46]  * apw goes retest, as thats my test case too
[10:47] <apw> siretart, the rm echo combination would indeed avoid the bug
[10:57] <siretart> apw: TBH, I'm not sure about your patch. you check for ovl_copy_up_xattr() returning -EOPNOTSUPP. However, if the underlying fs does not support it, I'd expect the vfs_listxattr call in line 32 to already indicates that (line 34), in which case '0' is returned
[10:59] <apw> siretart, heh and looking in there i would expect so too, though i ended up at this fix not by inspection but by debugging it and confirming we were returnign that error code
[11:00] <apw> siretart, and indeed my machine here running the -pre1 of the kernel i sent you works
[11:00] <apw> hmmm
[11:01] <siretart> so maybe the fix is correct but incomplete
[11:01] <apw> except your test is identicle to mine, so i cannot see how i am not testing the same way you are
[11:02]  * apw goes check that the -pre1 and final kernels behave the same
[11:03]  * siretart goes installing the kernel on bare metal as well
[11:05]  * henrix -> lunch
[11:08] <siretart> apw: funny, I cannot reproduce the problem when booting 'normally', but it does still persist in the nfsroot scenario that involves the 'live-boot' package
[11:09] <apw> siretart, so the kernel fixes something then
[11:09] <apw> i can only assume it is about how the nfs mount is mounted
[11:10] <siretart> hmm.. maybe the -o nolock option?
[11:12] <siretart> apw: indeed, it seems that -o nolock does make a difference. can you confirm that?
[11:13] <apw> siretart, sigh, will do
[11:19] <apw> ok confirmed it works in my testing without -o nolock with the kernels i posted
[11:20] <siretart> yes, I can confirm that too
[11:20] <siretart> however, in that nfsroot environment there is no nfs locking daemon available
[11:24] <apw> siretart, how can i confirm its mounted nolock ?  as my testing mounting -o nolock works
[11:25] <siretart> apw: grep ',nolock,' /proc/mounts
[11:26] <apw> siretart, ok its not there dispite  asking for it
[11:26] <apw> siretart, can you paste your entire mount line please
[11:26] <siretart> mount -o nolock -o ro -t nfs <IP_ADDRESS>:/i4lab.stand/proj/fai/nfsroot.quantal64 /mnt
[11:27] <siretart> results in this line in /proc/mounts for me:
[11:27] <siretart> <IP_ADDRESS>:/i4lab.stand/proj/fai/nfsroot.quantal64/ /mnt nfs ro,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=<IP_ADDRESS>,mountvers=3,mountport=57036,mountproto=udp,local_lock=all,addr=<IP_ADDRESS> 0 0
[11:30] <apw> siretart, ok i am simply unable to mount the damn thing no-lock, is there anything special on the export side?
[11:31] <apw> siretart, oh and you are mounting as v3 there ... mine defaults to v4
[11:31] <siretart> I'm using these export options: (ro,no_root_squash,sync,no_subtree_check,insecure)
[11:32] <siretart> yeah, we have disabled v4 as we have experienced a number of problems with it (*cough*solaris*cough*)
[11:34] <apw> siretart, ok how have you disabled v4
[11:34] <apw> i suspect that is why i am not seeing it
[11:36] <siretart> apw: I'm checking. but maybe you can force it by using '-o vers=3' as mount options?
[11:37] <apw> ahh that does it
[11:38] <apw> siretart, ok, so this is yet a third bug, i am starting to hate you :)
[11:38] <apw> siretart,  i have it reproducing now, its definatly something different as it has a differnet error code to user space
[11:38] <apw> siretart, i am also a bit confused by the nosupp thing as that should be caught in copy_xattr and clearly is not
[11:39] <apw> siretart, so will go debug it yet more ... bloody nfs
[11:39] <siretart> apw: you have my sympathy :-(
[11:40] <siretart> I know that we have disabled v4 in the automounter, but that's not relevant here. would need to ask folks here how we did it, but it seems that's not relevant anymore
[11:47] <siretart> just FTR, we disable NFSv4 by setting RPCNFSDCOUNT="-N 4 200" in /etc/default/nfs-kernel-server
[12:50] <ppisati> infinity: can you promote 3.5.0-209.15?
[12:50] <ppisati> rtg: do i need to send an email to ubuntu-installer for every upload? don't they follow -meta?
[12:51] <rtg> ppisati, might be a little early in the day for Adam. you need to send an email to the installer list for every ABI bump because it requires manual intervention in the d-i
[12:51] <ppisati> rtg: ok
[13:02] <stgraber> hello, I'm being nagged about bug 995998 as it's affecting quite a few thin client deployments, can the fix be cherry-picked in 12.04?
[13:02] <ubot2`> Launchpad bug 995998 in linux "fix hp t5745 and hp st4757 lvds patch in drm" [Medium,Confirmed] https://launchpad.net/bugs/995998
[13:03] <rtg> stgraber, seems pretty straightforward
[13:06] <cking> iso testing thursday is taking longer than I anticipated today :-/
[15:02]  * ogasawara back in 20
[16:00] <infinity> ppisati / rtg: No one normally sends us mail about ABI bumps, I just promote and do the bumps based on what's in proposed.
[16:02] <rtg> infinity, actually, we're _supposed_ to send email notifications of ABI bumps. whether they are actually necessary depends on the person uploading the d-i
[16:04] <infinity> rtg: Do you actually do so?  If so, it's to a list I'm not subscribed to, and I do most of the d-i ABI uploads. :P
[16:04] <infinity> (Anyhow, the only reason I didn't do omap4 yesterday was because I was tossing around the idea of doing some d-i bugfixes in the same upload)
[16:06] <rtg> infinity, ubuntu-installers and<EMAIL_ADDRESS>are the 2 lists that get the ABI bump announcement
[16:06] <infinity> Ahh, well, I am subscribed to kernel-team, I just rarely read it. ;)
[16:07] <infinity> Anyhow, I don't need the reminders, so it's moot.  I agree that it's still good practice to send them.
[16:26] <xnox> rtg: infinity: maybe the ABI bump emails were relevant before we were using $dev-proposed. It was an indication to me - do not do partial dist-upgrade until things settle.
[16:29] <ppisati> do any of you have a working dvi <-> vga adapter?
[16:29] <ppisati> i bought one but it seems it's not working...
[16:30] <cking> ppisati, co-incidentally, I just picked one up that works as you asked that question
[16:30] <ppisati> doh!
[16:30] <ppisati> brand?
[16:30] <ppisati> shape? price?
[16:30] <cking> no idea, let me send a photo of the pins
[16:32] <ppisati> mine is exactly this one: http://www.qvs.com/images/DVI_VGA_ADAP.jpg
[16:32] <cking> ppisati, see http://en.wikipedia.org/wiki/Digital_Visual_Interface, mine is the DVI-A
[16:32] <ppisati> bought from amazon
[16:32] <cking> yep, looks the same to me
[16:33] <cking> DVI-A (analogue) for VGA
[16:33] <cking> I love DVI, so many standards in one handle socket
[16:33] <ppisati> :(
[16:33] <cking> s/handle/handy/
[19:12]  * ogasawara lunch
[19:21]  * cking -> EOD
[22:15] <cyphermox> hey; seems like there's a bad side effect to a fix included in 3.2.0-29.45; just thought to bring it up if you run into other reports of it: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1035590
[22:15] <ubot2`> Ubuntu bug 1035590 in linux "Kernel update on 10 Aug 2012 affects nm-applet signal strength" [High,Confirmed]
[23:57] <herton> cyphermox, yes, the fix that brought this bug should be this: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;a=commit;h=d5b65f764c414a8da02c479f7fa57cfaee603fd3
[23:57] <herton> came through 3.2 stable update
[23:57] <herton> at least we think it is this one, that was the only change to ipw
[23:59] <herton> cyphermox, should we revert it, or will this be handled through nm? I think we can't ask stable upstream to revert this, seems just something that affects our nm+kernel


[14:26] <jussi> akgraner: akgraner akgraner!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WOW!!!! THANK YOU SO MUCH!!!
[14:26]  * jussi hugs akgraner
[14:59] <nigelb> what'd she do?
[14:59]  * nigelb scrolls up
[15:57] <jussi> nigelb: I got a package from her, with a few things for our little bubbles... :D  :)
[16:44] <nigelb> jussi: \o/
[21:32] <cjohnston> AlanBell: ping
[21:32] <AlanBell> o/
[21:32] <cjohnston> you were behind pad.ubuntu.com correct?
[21:33] <AlanBell> yeah
[21:34] <cjohnston> 2 things... we need to update the tag to #uds-p, and two, can we make it to where pad.u.c doesn't say welcome to uds, blah blah blah, but the pad when used for UDS it says welcome to uds and has tags and all
[21:34] <AlanBell> yeah, I know where to make those changes
[21:35] <AlanBell> well actually I don't know how to tell when it is in a UDS context
[21:35] <AlanBell> I can point out the locations and file an RT to request someone to change them
[21:35] <cjohnston> is the team stuff something that may work? so make a team UDS-P ?
[21:35] <AlanBell> I have no access to the box
[21:35] <cjohnston> right
[21:35] <cjohnston> we just need to get the changes started
[21:36] <AlanBell> I don't know how the team stuff works
[21:36] <cjohnston> hmm
[21:36] <cjohnston> I wonder if Daviey does?
[21:48] <AlanBell> I think we established it wouldn't get us openID integration and we didn't want to get people registering on it
[21:50] <AlanBell> /usr/share/etherpad/etherpad/src/themes/default/templates/misc/pad_default.ejs
[21:51] <AlanBell> that is a very simple file containing a boilerplate license comment and the text you want to be pre-populated
[21:51] <AlanBell> it is part of the theme template so if we could use a specific UDS template then we could have a different one to the default theme
[21:52] <AlanBell> but passing the theme name on the query string was a bit broken at the time so we ended up customising the default theme
[21:53] <AlanBell> cjohnston: do you have a bug with the text you want in the default pad?
[21:54] <cjohnston> I think what's there now s/uds-o/uds-p is good for UDS.. Beyond that.. just for creating a random new pad.. "Welcome" seems fine to me?
[21:55] <AlanBell> ok, I can chuck in an RT requesting the s/uds-o/uds-p/ change for now
[21:56] <cjohnston> please cc me
[21:59] <AlanBell> Ticket 18035
[22:44] <cjohnston> ty


[06:27] -lugito:#lubuntu-devel- [Lubuntu CI] jobgenerator just succeeded after failing: https://ci.lubuntu.me/job/jobgenerator/843/
[08:37] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-notificationd just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-notificationd/304/
[08:37] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-notificationd just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-notificationd/304/
[09:07] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lximage-qt just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lximage-qt/324/
[09:07] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lximage-qt just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lximage-qt/324/
[09:27] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lximage-qt just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lximage-qt/70/
[09:43] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-session just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-session/318/
[10:19] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-session just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-session/318/
[10:19] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_screengrab/74/
[11:16] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/654/
[11:16] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/654/
[11:26] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/493/
[11:31] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/654/
[11:41] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/331/
[11:57] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_libfm-qt/572/
[11:57] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/145/
[11:57] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/145/
[12:12] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_libfm-qt/572/
[12:33] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/483/
[12:33] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/483/
[12:52] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/141/
[12:54] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/332/
[13:03] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/142/
[13:04] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_libfm-qt/572/
[13:04] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/493/
[15:48] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-policykit just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-policykit/545/
[16:54] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-sudo just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-sudo/559/
[16:54] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-sudo just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-sudo/307/
[18:41] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/72/
[19:02] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/72/
[19:46] <The_LoudSpeaker> lxqt-build-tools has small minor conflicts.
[19:46] <The_LoudSpeaker> installing the dev tools rn.
[19:53] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/310/
[19:55] <wxl> go get 'em raman!
[19:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_qtermwidget/771/
[19:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_qterminal/90/
[20:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qterminal/390/
[20:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qterminal/390/
[20:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/310/
[20:18] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/598/
[20:18] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/105/
[20:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/357/
[20:22] <The_LoudSpeaker> https://p.ip.fi/7DBw how do I go about here?
[20:22] <The_LoudSpeaker> keep ubuntu side? in that case I will need to do so using a patch.
[20:22] <The_LoudSpeaker> wait
[20:22] <The_LoudSpeaker> figured.
[20:23] <The_LoudSpeaker> considering no ubuntu patch did this. this means this can go away.
[20:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_qtermwidget/771/
[20:25] <The_LoudSpeaker> but why is there a 1 after ubuntu in the previous name I mean why is it lxqt-build-tools-0.7.0-0ubuntu1 and not lxqt-build-tools-0.7.0-0ubuntu0 considering there's no debian/patches
[20:25] <The_LoudSpeaker> ?
[20:25] <The_LoudSpeaker> ^ wxl
[20:25] <wxl> afaik it's always at least 1
[20:25] <wxl> let me explain it like this:
[20:25] <wxl> 0.7.0 = upstream
[20:26] <wxl> 0.7.0-1 = upstream with Debian packaging
[20:26] <The_LoudSpeaker> is that so? I don't remember. always thought it equalled no of patches.
[20:26] <wxl> 0.7.0-0ubuntu1 = upstream with Debian packaging essentially merged to Ubuntu (no changes)
[20:26] <The_LoudSpeaker> yeah I know the numbering. number before ubuntu is debian side patches and after it is ubuntu side ones.
[20:26] <The_LoudSpeaker> oh okay. so 1 is default then
[20:26] <The_LoudSpeaker> TIL
[20:27] <wxl> so if there's a package in debian it will always *AT LEAST* be -1
[20:27] <wxl> and if we do nothing to it, it will be -0ubuntu1
[20:27] <wxl> if we make a change on our own, then -1ubuntu1
[20:27] <wxl> does that make sense?
[20:29] <The_LoudSpeaker> yup.
[20:39] <The_LoudSpeaker> dpkg-source: warning: lxqt-build-tools-0.8.0-1ubuntu1/debian/changelog(l11): found end of file where expected more change data or trailer
[20:39] <The_LoudSpeaker> ^ this to be ignored ?
[20:40] <The_LoudSpeaker> oh wait
[20:40] <The_LoudSpeaker> nvm
[20:42] <The_LoudSpeaker> standards version to be 4.5.1 only right?
[20:42] <The_LoudSpeaker> ^ wxl
[20:43] <wxl> i'd have to look it up off hand
[20:43] <The_LoudSpeaker> debian side it's .1
[20:44] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-notificationd FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-notificationd/305/
[20:44] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm just failed after being unstable: https://ci.lubuntu.me/job/focal_stable_sddm/599/
[20:44] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/106/
[20:45] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/358/
[20:56] <The_LoudSpeaker> side quest: why does writing hirsute as distro name in dch give me a lintian error?
[20:56] <The_LoudSpeaker> side quest2: I am sure standards version is 4.5.1 but lintian also gives me a warning saying newer than current used.
[20:57] <The_LoudSpeaker> i am building this in a hirsute lxc container.
[20:57] <The_LoudSpeaker> cc: lubuntu-dev
[20:59] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lximage-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lximage-qt/71/
[20:59] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lximage-qt just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_lximage-qt/325/
[21:00] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lximage-qt just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_lximage-qt/325/
[21:01] <wxl> good question
[21:02] <wxl> new version of libx11 apparently fixes crashes in 18.04 so we should probably sru if it hasn't already https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/comments/99
[21:03] <wxl> gee my old container is wiped sigh
[21:04] <wxl> i think you're on your own for a while until i get that fixed up unless @kc2bez can confirm/deny
[21:20] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab FAILURE: https://ci.lubuntu.me/job/hirsute_stable_screengrab/75/
[21:20] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/494/
[21:20] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab FAILURE: https://ci.lubuntu.me/job/hirsute_stable_screengrab/75/
[21:20] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-session just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_lxqt-session/319/
[21:20] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-config/655/
[21:30] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_libfm-qt/484/
[21:30] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libfm-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_libfm-qt/143/
[21:35] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/146/
[21:50] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libfm-qt just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_libfm-qt/573/
[21:51] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-sudo just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-sudo/560/
[21:51] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-sudo just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_lxqt-sudo/308/
[22:06] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_qterminal/90/
[22:06] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qtermwidget FAILURE: https://ci.lubuntu.me/job/focal_stable_qtermwidget/771/
[22:17] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal FAILURE: https://ci.lubuntu.me/job/groovy_stable_qterminal/391/
[22:17] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal FAILURE: https://ci.lubuntu.me/job/groovy_stable_qterminal/391/
[22:17] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm just failed after being unstable: https://ci.lubuntu.me/job/focal_stable_sddm/599/
[22:17] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/106/
[22:17] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/358/
[22:27] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget FAILURE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/310/
[22:30] <kc2bez> Oh dang, no bot here! That had been broken for a bit. I have to read the daily scroll back.
[22:34] <kc2bez> I haven't bumped anything to 4.5.1 standards yet.
[22:34] <kc2bez> I don't remember getting lintian errors for Hirsute.
[22:35] <kc2bez> wxl: theloudspeaker is there anything else I missed?
[22:44] <wxl> @kc2bez: that's really it. but did you do anything about the bot?
[22:44] <kc2bez> I made a ticket for teward and sent him a message on Telegram
[22:45] <kc2bez> It is on his infra now, not sure if we have access to that or not. If I do I have no idea how.
[22:45] <teward> i'm lazy on the SSH access implementation atm :P
[22:45] <teward> err:toomuchtodo
[22:45] <kc2bez> No worries as long as you are around
[22:46] <kc2bez> It looks like there was a netsplit way back that might have dorked things up.
[22:46] <teward> and is still fubaring things
[22:46] <kc2bez> awesome
[22:46] <teward> *reboots container*
[22:48] <teward> nope still fubar hmmm
[22:48] <kc2bez> Fair enough, keep us posted.
[22:51] <teward> hmmmmmmmmmmmmm
[23:02] <teward> it's not back yet but... almost
[23:02] <kc2bez> ok


  Because it's 7pm, apparently.
[09:05] <RAOF> Oops.
[09:06] <chrisccoulson> heh :)
[09:09] <mlankhorst> heya
[09:10] <chrisccoulson> hi mlankhorst
[12:07] <xclaesse> is there a reason why ubuntu 12.04 installs libreoffice-gtk and not libreoffice-gtk3 ?
[12:17] <MrChrisDruif> xclaesse; because libreoffice-gnome depends on libreoffice-gtk and not both on libreoffice-gtk && libreoffice-gtk3
[12:18] <mitya57> xclaesse: IIRC because it's not working yet
[12:19] <mitya57> xclaess: maybe Sweetshark can tell more
[12:23] <MrChrisDruif> I just installed -gtk3 but I'm not noticing any differences...?
[12:25] <mitya57> MrChrisDruif: remove -gtk and you'll be greeted by Windows95-style controls :)
[12:27] <MrChrisDruif> mitya57; maybe by removing -gtk it also removes -gnome which does that?
[12:28] <MrChrisDruif> Anyhow, I'm off for some groceries
[12:28] <mitya57> MrChrisDruif: from -gnome package description:
[12:28] <mitya57> > This package contains the GIO support and a GConf backend.
[12:28] <mitya57> I don't think it's related to the UI
[12:52] <Laney> #
[13:44] <xclaesse> MrChrisDruif, mitya57: ok thanks, it seems it's more work that just installing -gtk3 instead of -gtk... maybe too early to make the change... :)
[16:03] <ronoc> chrisccoulson, ping
[16:06] <ronoc> thunderbird is really acting up on me ...
[16:06] <ronoc> i can barely view my emails
[16:06] <ronoc> not to mention send 'em
[16:06] <ronoc> got move venue back in 10
[18:06] <hoonteke> ronoc: still there?  If this is with 12.04, my experience was similar.  I thought it was just Thunderbird, but I now think it's some interaction with Unity.  (both 2d and 3d)
[18:06] <ronoc> hoonteke, exactly
[18:06] <hoonteke> Why?  I was generally having performance and stability issues with Compiz, and finally got fed up enough to try some other desktop environments.
[18:06] <hoonteke> I ended up on OpenBox, and now Thunderbird is downright zippy.
[18:07] <ronoc> the dbus-daemon acting up is not good thing.
[18:07] <ronoc> wow
[18:07] <ronoc> i need to talk to chris coulson
[18:07] <hoonteke> ronoc: I never diagnosed /exactly/ what was going on, but did *nothing* to futz with thunderbird.
[18:07] <hoonteke> the only thing I changed was unity to openbox.
[18:07] <ronoc> hoonteke, i was trying to tidy up my mails that was all
[18:08] <ronoc> weird
[18:08] <hoonteke> FWIW, I tried many variants, including unity 2d and 3d, gnome 3, "classic", and so on.  all were having issues.  I did not try XFCE, but settled on OpenBox when the whole experience was just plain faster and used a *heckuva* lot less resources.
[18:10] <hoonteke> ronoc: the frustrating thing is I *like* where Canonical is going with the UI of Unity.  But I need to be able to work, and that boils down to speed of interaction for me.
[18:11] <hoonteke> ronoc: and unfortunately, "speed of interaction" boils down to "use less resources" and "don't crash, ever".  Neither of which Unity satisfies.  sigh.
[18:11] <ronoc> hoonteke, well there must be something going on, i'm sure we'll fix it asap
[18:11] <ronoc> i'll talk with chrisccoulson
[18:12] <hoonteke> ronoc: oh ... missed the detail thatyou're a dev type.  Thought you were a "regular user" like me.  Heh, promise I wasn't trying to lament the situation, but help commiserate.  :-)
[18:13] <ronoc> hoonteke, no problem, thanks for the feedback :)
[18:19] <hoonteke> ronoc: as an interested party and Ubuntu advocate, is there a patch mailing list to which I can subscribe to watch various code commits?  For instance, I subscribe to<EMAIL_ADDRESS>to watch various commits go by.
[18:19] <hoonteke> I've been so far unable to find a Unity patch mailing list.
[18:22] <ronoc> i don't think there is patch mailing list, there the dev mailing list though hoonteke
[18:22] <ronoc> http://unity.ubuntu.com/contact-us/
[18:22] <ronoc> okay gotta run
[18:22] <ronoc> speak later
[18:22] <hoonteke> ronoc: FWIW, I think Chris is at least peripherally aware of this issue, as Wayne specifically CC'd him on this bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=562977  .  (Comments 16+.)  Can't say if it's high on his TODO list though, as this has been an issue since 2008 or so
[18:23] <ubot2> Mozilla bug 562977 in Mail Window Front End "thunderbird progress bar activity puts CPU at 20%" [Minor,Unconfirmed: ]
[18:23] <hoonteke> okay.  seeya
[18:23] <ronoc> ok good to know
[18:23] <ronoc> thank
[18:24] <hoonteke> np.  thanks for the contact-us link.
[18:29] <ronoc> np hoonteke
[18:29] <ronoc> okay now I'm gone :)
[18:29] <hoonteke> ha
[18:29] <hoonteke> believe it when I "see" it
[21:24] <robert_ancell> desrt, hey, I always find GUADEC never clearly shows the schedule - what days do you plan to be there? 26-1st?
[22:09] <chrisccoulson> hmmm, i wish i could undock without having to log out of my session
[22:28] <robert_ancell> chrisccoulson, why do you need to log out?
[22:29] <chrisccoulson> robert_ancell, i get a GPU hang if compiz is running
[22:29] <chrisccoulson> (when i disconnect an external screen)
[22:29] <robert_ancell> chrisccoulson, oh, fun
[22:29] <chrisccoulson> yeah :(
[22:30] <robert_ancell> chrisccoulson, oh, btw, do you know of any reason not to update quantal webkitgtk to 1.9?
[22:30] <robert_ancell> or are we all just waiting for someone else to do it
[22:30] <chrisccoulson> robert_ancell, i'm not sure. i think seb talked to micah about this last week, but i don't remember the outcome
[22:31] <robert_ancell> people really need to file bugs for these from the versions page so we know what to do
[22:32] <chrisccoulson> ah, it's here: http://irclogs.ubuntu.com/2012/05/25/%23ubuntu-desktop.html#t07:49
[22:33] <robert_ancell> chrisccoulson, ta
[22:33] <robert_ancell> chrisccoulson, oh, what's with the arm/ppc build failures for tb/ff?
[22:33] <chrisccoulson> robert_ancell, i'm not sure about armel, and ppc is on the list of architectures that i mostly ignore ;)
[22:33] <chrisccoulson> ppc hasn't built for a while
[22:33] <robert_ancell> yeah, does someone go around and fix those up?
[22:34] <robert_ancell> they seem to go away eventually
[22:34] <robert_ancell> actually, does anyone know why we even bother supporting ppc anymore?
[22:34] <chrisccoulson> robert_ancell, no, they mostly get ignored. i'm still not sure why we haven't killed ppc already
[22:34] <chrisccoulson> yeah, i wonder the same ;)
[22:34] <robert_ancell> is the only hardware old macs?
[22:34] <chrisccoulson> i think so
[22:35] <RAOF> And pre-patch PS3s :)
[22:35] <chrisccoulson> the only person i know with ppc hardware is the person who reported bug 926495
[22:35] <ubot2> Launchpad bug 926495 in thunderbird "FTBFS on powerpc (again)" [High,Fix released] https://launchpad.net/bugs/926495
[22:36] <chrisccoulson> who is the only person to notice that firefox doesn't build ;)
[22:38] <robert_ancell> I only notice because it's at the top of the versions page.  Perhaps we should just blacklist ppc
[22:39] <chrisccoulson> yeah, i don't think anyone looking at that is really all that concerned with ppc :)
[22:39] <robert_ancell> it must actually be getting to the point where we could just feasibly support amd64 and armhf and be done with it
[22:39] <TheMuso> Yeah, I used to care about PPC< but lost interest after nobody stepped up from the community to help...
[22:39] <TheMuso> Those who care about ppc should just go to Debian IMO.
[22:40] <chrisccoulson> robert_ancell, well, apart from i386, we're almost there. i was told last week not to worry about armel issues too :)
[22:40] <jbicha> now's a good time to kill it with non-PAE support getting killed & 12.04 being supported until 2017
[22:41] <robert_ancell> who decides?  The TB?
[22:41] <TheMuso> And the x32 ABI is possibly coming at some point...
[22:42] <chrisccoulson> yeah, i was just about to mention that too
[22:48] <chrisccoulson> i think now is a good time to log out and undock, before my head explodes from all this assembler :)
[22:48]  * chrisccoulson gets all the fun bugs


[00:57] <daftykins> is _denis_ a known trouble maker?
[00:57] <daftykins> seems to be up to trollworthy antics
[01:15] <daftykins> oh well nm
 i dont use c shell, its homework
[09:58] <k1l> can #ubuntu do my math and physics homework too? :)
 knoten i can help you
[14:28] <bazhang> seems up to no good
[14:28] <genii> Hm
[14:29] <bazhang> announcing he wants to be 'haxor'
 what is best webmail that may support linux command line?
[16:48] <bazhang> web cli?
[16:49] <Pici> you can use mutt with gmail
[16:51] <bazhang> !best
[16:51] <bazhang> what!!
[16:55] <genii> I wonder if pine/alpine would work also
[16:55] <bazhang> he wants no client at all
[16:55] <bazhang> unix makes it easy!
[16:56] <Unit193> genii: Yes.
[16:56] <genii> Interesting
[16:57] <genii> ( our telnet and ssh login systems use Pine for email)
 gmail and famous webmail servies don't seem text base
[16:58] <bazhang> he wants gmail-cli
[16:59] <tonyyarusso> Wouldn't any cli imap client work, not necessarily gmail-specific?
[17:01] <bazhang> he wants the famous, but sure
 i want to renew it
[17:31] <bazhang> from cli
[17:32] <bazhang> putting together the puzzle pieces 'hack google' is the output
[17:45]  * genii slides the old fart some coffee
[18:22] <bazhang> Flong> Paul^^, EFI = No Trust
[18:25] <Flong> bazhang, nice
[18:26] <Flong> I don't trust the UEFI and reccomend not trusting it so I get banned.
[18:26] <bazhang> Flong, take the fud elsewhere
[18:26] <Flong> How long until my ban is up. One month?
[18:26] <Flong> bazhang, not FUD, proven time after time
[18:26] <bazhang> its not remotely welcome in support channels
[18:26] <Flong> I'll stop speaking it in #ubuntu
[18:26] <bazhang> you are banned
[18:26] <Flong> bazhang, Discussing how to lock down your distro is.
[18:27] <bazhang> so thats correct
[18:27] <Flong> I want to dispute my ban with an operator.
[18:27] <bazhang> for spreading nonsense about uefi?
[18:28] <Flong> bazhang, many documents have proven it in the past.
[18:28] <Flong> That is not the point of me being in #ubuntu-ops however
[18:28] <Flong> I'm here to dispute my ban. If you would like me to talk to you about the OT subject feel free to PM me
[18:29] <bazhang> no need
[18:29] <bazhang> and the ban stays
[18:29] <Flong> How long?
[18:29] <bazhang> no time limit determined
[18:29] <Flong> because differing views?
[18:30] <bazhang> false info is not a 'differing view'
[18:30] <bazhang> its simply false
[18:30] <Flong> bazhang, Again proven time after time.
[18:30] <Flong> Just because you disagree with a fact doesn't make it any less of a fact.
[18:31] <Pici> This discussion of UEFI has no place in #ubuntu regardless if it is true or not.
[18:31] <Flong> Pici, I will stop it then.
[18:31] <Flong> Either way my question belongs in #ubuntu-server more than #ubuntu
[18:32] <Flong> It's not a server related question though, it's more of a desktop related one
[22:09] <genii> Got it already
[22:11] <genii> @comment 69366 Rant of Ubuntu "broke their computer", profanity.
[22:15] <Unit193> Mildly amusing.
[22:15]  * Unit193 runs off to ##windows to see the second half.
[22:52] <Unit193> NANOOK ended up just resorting to spamming to get kbanned.
[22:54] <genii> Spamming in ##windows ?
[22:54] <Unit193> Aye.
[22:55] <genii> We'll probably see them again.
[22:55] <genii> I only removed, no +b
[22:56] <genii> I imagine they'll find a proxy or such and return inside of a few days
[23:09] <PerfM> lol
[23:13] <PerfM> bekks can't take a joke man
[23:13] <genii> @comment 69369 Abuse, profanity
[23:14] <PerfM> wow this is how you log trolls
[23:14] <PerfM> this is so exciting
[23:15] <PerfM> what is beside my number
[23:28] <genii> @comment 69370 Profanity
[23:43] <genii> @comment 69372 Abusive PMs to other users
[23:43] <PerfM> :(
[23:43] <PerfM> that's mean
[23:46] <genii> @comment 69374 Forced to +b