[03:33] <pavlushka> need some help
[05:22] <Hund> pavlushka: Don't ask for help, just ask and someone might be able to help you.
[05:23] <pavlushka> Hund, thanks for the suggestion.
[05:25] <pavlushka> Hund, how can i add bug logs manually to an existing bug which i reported manually
[05:26] <Hund> How did you report it in the first place?
[05:26] <pavlushka> using LP
[05:29] <pavlushka> using LP in the browser.
[05:29] <Hund> Just add a comment there then?
[05:31] <pavlushka> where the ubuntu-bug generates/stores the report?
[05:31] <pavlushka> where the ubuntu-bug generates/stores the report before submitting?
[05:32] <Hund> I guess so.
[05:32] <Hund> I haven't used Launchpad in years, but I guess it sounds a about right.
[05:32] <pavlushka> tell me where the ubuntu-bug generates/stores the report before submitting?
[05:35] <Hund> I have no idea. I always submitted the tickets myself.
[05:36] <pavlushka> ok, I'll try to find it. thanks
[13:04] <Jens1112> hello
[13:04] <Jens1112> how can you compile github zip files?
[13:05] <knome> depends on the zip file, please refer to the documentation of that github project
[13:05] <Jens1112> it does not say anything about ubuntu
[13:05] <Jens1112> just dependencies no install guide
[13:10] <knome> there is no single way that works for all packages in ubuntu either
[13:12] <Jens1112> okay then iv got to make my own way through it
[13:14] <Jens1112> if you ask me xubuntu is the best distro
[13:16] <knome> glad to hear you like xubuntu
[13:17] <Jens1112> ive install on my daddy machine, he likes
[13:17] <Jens1112> ;-)
[13:21] <pjotter> Hi knome!
[13:22] <pjotter> I'm sorry to say I haven't had any time to work on the gfx for the new xubuntu release. It's just too busy here, right now.
[13:47] <sancho_panza> hi! my network indicator disappeared from the status bar, what can i do to repristinate it?
[13:51] <knome> pjotter, i noticed; and i've drawn the xerus already
[14:04] <dkessel> sancho_panza: try running "nm-applet &" in a terminal
[14:06] <sancho_panza> dkessel, it returns: ' [1] 27085 '
[14:06] <sancho_panza> dkessel, nothing else happens :(
[14:06] <dkessel> it should only do that after it has created the indicator icon. have you tried logging out and in again?
[14:15] <sancho_panza> dkessel, i restarted my pc several times without resolving
[14:20] <dkessel> sancho_panza: are you sure you have not accidently removed the indicator area from the xfce panel ?
[14:21] <sancho_panza> i tried to "add new elements" but i can't find a separate applet for the network indicator
[14:21] <sancho_panza> so i removed the notification applet
[14:21] <sancho_panza> and then proceded to add it back again
[14:21] <sancho_panza> no results, network indicator still missing
[14:22] <dkessel> sancho_panza: unfortunately, i am not on xubuntu myself at the moment. but i believe there was somewhere where you could configure what should be displayed in the notification aread
[14:24] <sancho_panza> i'll try to follow some "too long to read" guides on the internet
[14:24] <sancho_panza> ty for helping me
[14:24] <dkessel> ok
[14:27] <krytarik> sancho_panza: That'd be "Indicator Plugin".
[14:28] <sancho_panza> yeah! it worked!
[14:28] <sancho_panza> but
[14:28] <sancho_panza> now i have TWO network icons on my status bar @___@
[14:31] <krytarik> Well, remove one of those. :P
[14:40] <pjotter> knome: Is there a preview available?
[14:44] <Jens1112> preview or wat?
[14:45] <pjotter> Jens1112: The xerus gfx for the new release
[14:52] <krytarik> pjotter: https://launchpad.net/ubuntu/+source/xubuntu-artwork/15.12.3
[14:55] <pjotter> krytarik: Thanks, but I was looking for the gfx of the slideshow on the live-cd installer
[14:55] <krytarik> Ah, right - one sec.
[14:58] <krytarik> pjotter: http://bazaar.launchpad.net/~ubiquity-slideshow/ubiquity-slideshow-ubuntu/html/download/pasi%40shimmerproject.org-20160310140751-ia6e4hof1dxt4iiv/xerus_art.png-20160310140738-p8t66o10hnqfrs8g-20/xerus_art.png
[14:59] <pjotter> Aaah! Great :)
[14:59] <mrkramps> ehehehehehehehe sweet ^^
[14:59] <krytarik> Indeed. :)
[14:59] <pjotter> There we have our little badger
[14:59] <mrkramps> nice one!
[15:00] <pjotter> I suppose this is going to be overlayed on top of a blue backdrop?
[15:03] <pjotter> Looks nice, knome!
[15:06] <krytarik> pjotter: Yep - more specifically: http://bazaar.launchpad.net/~ubiquity-slideshow/ubiquity-slideshow-ubuntu/html/view/head:/slideshows/xubuntu/slides/link/base.css#L153
[15:14] <Jens1112> ive want to see the upcoming realease as an preview
[15:14] <Jens1112> anyone seen about zhis?
[15:16] <pjotter> knome: Are you satisfied with the design yourself?
[15:16] <Jens1112> me?
[15:18] <pjotter> Well, sure... what do you think, Jens1112?
[15:19] <Jens1112> im not sure if the changes to unity are any good use
[15:19] <pjotter> What changes to unity?
[15:19] <Jens1112> nevermind
[15:20] <pjotter> I thought Xubuntu didn't have any unity stuff in it's release?
[15:22] <Jens1112> of course it doesnt
[16:01] <pjotter> Does anyone know  a site where I can upload a picture?
[16:02] <dkessel> imgur.com
[16:02] <krytarik> Or: http://en.zimagez.com/
[16:02] <pjotter> Ok, thanks! I wasn't sure if there was also some kind of pic sharing service from ubuntu?
[16:02] <krytarik> Nope.
[16:06] <pjotter> Ok. Knome (and others). This was what I was working on but unfortunately have not had the time to make a proper version of it: https://imgur.com/TtlXHnr
[16:07] <krytarik> !channels
[16:08] <pjotter> krytarik: Got it. I'll take this to #xubuntu-dev then ;)
[16:08] <krytarik> Thanks. :)
[16:08] <pjotter> np
[16:37] <black_pi> Xubuntu is the best distro out there!
[16:44] <tony1> does anyone know how to get the sound to work with the mail-notification applet with xubuntu 14.04? aplay /usr/share/mail-notification/new-mail.wav will work but selecting properties in the app and selecting "play sound when new mail arrives" does not work. it look like it tries to play but there is no sound.
[16:44] <tony1> I am not sure the command that applet uses or I would try it directly and look for errors
[17:04] <slee> hello, is there a way in xubuntu to lock window positions? so evrytime i open a certain program, it auro places it in the spot i want? i see compiz has the ability...just wondering if xubuntu already has something i'm not seeing befire i try and use compiz
[17:08] <flocculant> slee: pretty sure not as a default - but I use devilspie to do that
[17:09] <flocculant> https://help.ubuntu.com/community/Devilspie
[17:09] <slee> thanks
[18:01] <tony1> ok well I found the command in gconf and changed it. the default does not work. should have all the libs. anyway happy enough with aplay command
[21:05] <m3n3chm0> hello the last 3 days my laptop does not poweroff or reboot OK.. I mean in the splash screen it freezes and I have to push power button until it power off. I'm using xubuntu 15.10 and this is the first time I see this issue


[16:53] <flocculant> Unit193: so cursor bug - you linked to comment, but I can't see if there's a patch or anything - doesn't appear to be, so are we currently in 'Yup, there's a bug - no-one has a clue why' state?
[16:53] <flocculant> and evening all
[20:31] <ochosi> evening everyone
[20:31] <knome> hello
[20:38] <ochosi> Unit193: make distcheck is fixed in clipman
[20:39] <Unit193> flocculant: The statement was "Well it's marked fixed in Debian, lets make Unit193 tell us why!"  So I did, the last comment was basically that Corsac saw what we did, but the response he got was "file your own bug"
[20:39] <Unit193> ochosi: Nice!
[21:28] <Unit193> make[2]: *** No rule to make target 'xfce4-session-settings.glade', needed by 'distdir'.  Stop.   not sure if problem, or I'm missing a switch.


[14:48] <skellat> This looks hideous: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763499
[14:49] <jenni> [ #763499 - RFP: uselessd -- a project to reduce systemd to a base initd, process supervisor and transactional dependency system, while minimizing intrusiveness and isolationism. - Debian Bug report log[...] ] - https://j.mp/ZrDgNP
[15:21] <dzho> skellat: ah, a systemd fan then?
[15:21] <skellat> No
[15:21] <skellat> Just...sometimes you have to let things be finished
[15:22] <skellat> The number of potential re-openers in the Debian debate almost kept it going forever
[15:25] <dzho> you can't declare something finish and, well, if you look at the project page you can see that these are people who probably DGAF about Debian debates.
[15:25] <dzho> putting this as they have in a FreeBSD context.
[15:25] <skellat> DGAF?
[15:25] <dzho> don't give a fsck
[15:26] <dzho> the problems with systemd aren't going to just poof disappear
[15:26] <skellat> Oh, I know
[15:26] <skellat> systemd still bothers me
[15:26] <dzho> ok, then I don't get why you'd want to hush discussion about it
[15:27] <skellat> I just want to see it in a proper Debian release and a proper *buntu release
[15:27] <skellat> And then we can mercilessly tear it apart
[15:28] <dzho> because we haven't had a chance to do that already?
[15:28] <skellat> Ubuntu-side, not really
[15:28] <skellat> Debian-side...Jessie has been a roiling cauldron lately
[15:28] <dzho> this is one of those things where you declare darkness the new standard
[15:29] <skellat> If we end up with releases we just disavow
[15:29] <skellat> Well
[15:29] <skellat> That'll say something too
[15:30] <dzho> I thought that was everything with Unity already ;-)
[15:30] <skellat> Well, I look forward to testing reports if they ever exist of Ubuntu GNOME 14.10
[15:31] <skellat> Since Unity is at least tested
[15:31] <skellat> UG is slotting in GNOME 3.12 very, very, very late after Feature Freeze and there really isn't testing of it
[15:31]  * dzho shrugs
[15:31] <skellat> As in, it started hitting archive yesterday
[15:32]  * skellat notes that Xubuntu is fabulous
[15:32] <dzho> I tried lubuntu and found it not to my liking, xubuntu is better but still a bit rough here and there.
[15:33] <dzho> for my purposes, of course, I'm not a desktop connoisseur
[15:33] <skellat> The systemd issue in *buntu is going to get interesting soon as Ubuntu GNOME has pieces/parts more tightly integrated with systemd than you'd otherwise expect.  They also haven't been playing nice with the release schedule and have some things that hit that impact everybody else now that Mark committed to systemd *buntu-side.
[15:34] <dzho> I can tell you I won't much care about it until 2016
[15:34] <dzho> with the change up in release cycles I've lost track completely of non-LTS
[15:34] <dzho> other than AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA don't use them if you don't have to!
[15:35] <skellat> I'm actually glad we only support the non-LTS semi-annuals for only 9 months
[15:35] <dzho> we just threw away a big pile of release disks for intermediate releases because dropped support for them makes them a real PITA
[15:35] <dzho> its even hard to upgrade them.
[15:35] <skellat> If we botch one, we can disavow it soon enough as End of Life
[15:35] <dzho> the thing is, short support lifetimes for that stuff make people even less likely to use it, and hence, to test
[15:36] <dzho> but, I guess Ubuntu already gets far more bugs than it can digest as is
[15:36] <skellat> With the GNOME flavour not playing nice and GNOME's tight systemd integration...16.04 might see us reconsider systemd if we really start having breakages
[15:37] <dzho> and won't that be fun, with the Redhat constellation of distros going "must be you, works for us" and everyone from the *BSDs to the proprietary OSen and mobile folks going "haha Linux"
[15:38] <skellat> We could always rebase to BSD :-)
[15:38]  * skellat starts giggling
[15:38] <dzho> which would get back to sabdfl's apple-wannabe fetish
[15:40] <skellat> Just did a dist-upgrade on my Jessie box...since when is there a vlc-plugin-samba package?
[15:40] <dzho> hahaha
[15:40] <dzho> oh
[15:40] <dzho> I guess that makes sense
[15:40] <dzho> or . . . does it?
[15:40] <dzho> hmmm.
[15:40] <skellat> 2.2.0~pre3-1
[15:41] <dzho> oh, right.
[15:41]  * dzho was getting vlc and vnc mixed up
[15:41] <skellat> I don't remember VLC having a samba plugin before
[15:43] <skellat> And packages.d.o says it didn't exist in Wheezy
[15:43] <skellat> Hunh
[15:44] <skellat> Must be people approaching samba-like shares as a new-fangled, in their view, way to share media files
[15:45]  * skellat goes to answer the door, the doorbell just rang
[16:51]  * skellat heads out to pay bills and visit township hall
[19:16] <Unit193> Shorter does kind of make sense though, the people using them tend to upgrade more anyway.  I don't really see them going back to upstart, means re-picking up systemd-shim and keeping it up to par with systemd proper.  It's only going to get harder to use non-systemd Linux. :/


[00:07] <LLStarks> ohsix, is there any way to force compat-wireless to just build in the iwlwifi folder? the flags suck and still force everything else to be built.
[00:39] <LLStarks> ohsix, you can't bisect a folder? can you?
[00:40] <ohsix> yea, you can restrict the bisect to files in a directory, or to a single file
[00:53] <LLStarks> ohsix, can't because of unmarked tree files
[00:53] <LLStarks> *untracked working tree files
[02:36] <psusi> ok, so I have a reproducible bug where the kernel gets stuck in the uninterruptable state.  the output of sysrq-w isn't detailed enough to be very helpful.  any suggestions on where to proceed from here?
[02:41] <psusi> maybe a way to get the full call stack with parameters?
[02:41] <jk-> psusi: sysrq-t ?
[02:41] <jk-> won't have parameters though...
[02:42] <jk-> that should have the same output as W, but include all tasks
[02:42] <psusi> it's in the D state so w identifies and dumps it... t shows the same info just for all processes doesn't it?
[02:42] <psusi> yea
[02:42] <psusi> I don't need the other tasks... just trying to get more details on what the blocked one is doing
[02:43] <jk-> the backtrace should give a decent amount of info, could you pastebin it?
[02:43] <psusi> sure
[02:44] <psusi> http://pastebin.com/6Yc5Ke1D
[02:45] <psusi> all I can figure from that is that dmraid is issuing some kind of ioctl and device-mapper is waiting for something
[02:48] <jk-> psusi: could you file a bug and include this info?
[02:48] <psusi> I'm actually investigating an existing bug #666577
[02:48] <ubot2> Launchpad bug 666577 in dmraid (Ubuntu) "dmraid fails on start with ICH9R under RAID 5 (affects: 2) (heat: 12)" [Undecided,New] https://launchpad.net/bugs/666577
[02:48] <jk-> looks like dmraid is waiting for another thread to finish with the device, or something is refcounting wrongly
[02:48] <psusi> should I file a new one or just add linux to this one?
[02:50] <psusi> I got the original user to attach the raid metadata and I compiled dmraid with the testing option enabled, and set up loop and dm devices to simulate his disks and then tried to activate like he did... got the same results, only I could see that the task was stuck and hit sysrq-w
[02:50] <jk-> try sysrq-t too; that may show a task that holds a refcount to the device
[02:51] <psusi> ok.. let me reproduce it again
[03:00] <psusi> jk-, weird, starts off looking like: http://pastebin.com/wvifq9g9
[03:02] <jk-> psusi: I think you're missing some of the earlier lines of that dmesg output, could you copy from a little earlier in the log?
[03:03] <psusi> jk-, updated with the whole shebang
[03:04] <jk-> same URL?
[03:04] <psusi> yep
[03:04] <psusi> err... wait, no... http://pastebin.com/xYR4bwhx
[03:04] <jk-> looks better :)
[03:05] <jk-> so you're getting errors beforehand?
[03:07] <psusi> nope... dm-9 seems to be the new device it is trying to create
[03:10] <psusi> and it seems to still exist... it's an error target
[03:11] <psusi> hrm... I wonder if udev is doing something to the newly created device that is triggering a race condition
[05:54] <LLStarks> ohsix, i've done.
[05:54] <LLStarks> *done it
[05:54] <LLStarks> i found the commits
[05:54] <ohsix> nice, what was it?
[05:54] <LLStarks><PHONE_NUMBER>afbaac1b8a74ee21aeb013e817ac7d or a6866ac93e6cb68091326e80b4fa4619a5957644
[05:55] <LLStarks> i'm going to do a compat-wireless splice and test them
[05:56] <ohsix> the commit messages look interesting
[05:58] <LLStarks> i'd place my bets on<PHONE_NUMBER>afbaac1b8a74ee21aeb013e817ac7d
[06:59] <LLStarks> now for the waiting game. by now, every single dev on lk wireless general has seen my message.
[11:44] <xclaesse> FYI, pcie_ports=compat option at boot fixes the kworker issue I have in natty
[11:44] <xclaesse> I had same issue with maverick but process was kslowd
[11:44] <xclaesse> https://bugs.launchpad.net/bugs/662946
[11:44] <ubot2> Launchpad bug 662946 in linux (Ubuntu Maverick) (and 2 other projects) "linux kernel 2.6.35 slows down the whole system because of kslowdxxx processes (affects: 39) (dups: 2) (heat: 212)" [Medium,Incomplete]
[11:45] <xclaesse> someone should set that bug as affecting natty too
[11:45] <xclaesse> latest working kernel is lucid :(
[15:45] <po4> hi room
[17:39] <apw> tgardner, thats better, now by the fire :)
[17:39] <tgardner> apw, wow, that didn't take long
[17:46] <apw> tgardner, no indeed, the traffic is awsome
[17:48] <apw> quite how i don't know though, it was supposed to be the worse of the year
[17:49] <tgardner> apw, timing is everything
[18:14] <tgardner> apw, pushed 'UBUNTU: [Config] Added autofs4.ko to -virtual flavour' to natty master-next
[18:24] <apw> tgardner, cool thanks
[18:27]  * apw eyes a gin and tonic
[18:28]  * tgardner thinks apw should be _fondling_ a gin and tonic
[18:28] <LLStarks> why is git.kernel.org so slow?
[18:29] <apw> LLStarks, generally or instantaeously ?  there is no obvious load on the machine which serves it
[18:29] <LLStarks> slow for cloning and gitweb
[18:29] <LLStarks> and i have a 30mbit conn
[18:29] <mjg59> LLStarks: Likely because the Android source release was last week and it's hosted on the same servers
[18:30] <LLStarks> GINGERBREAD!!!!!!!!! CURSE YOU!!!!!!!!!!!!1
[18:30] <apw> heheh
[18:30] <LLStarks> "503 - The load average on the server is too high "
[18:30] <apw> LLStarks, heh i miss read the machine name ...
[18:31] <mjg59> apw: master.kernel.org isn't used for general serving, so the load there is probably much lower
[18:31] <apw> mjg59, indeed, should have thoguht of that :)
[18:31] <LLStarks> btw apw, i'm closing in on a fix for the iwl3945 speed issues that were introduced in the maverick cycle between 2.6.35-rc2 and rc3.
[18:32] <LLStarks> well, not a fix, but a specific commit that can be reverted.
[18:32] <apw> LLStarks, nice, what you found?
[18:32] <apw> tgardner, ^^#
[18:32] <LLStarks> down to 4 candidate commits.
[18:32] <apw> nice
[18:32] <apw> i assume you are bisecting
[18:32] <LLStarks> a6866ac93e6cb68091326e80b4fa4619a5957644
[18:32] <LLStarks> yes
[18:32] <LLStarks><PHONE_NUMBER>afbaac1b8a74ee21aeb013e817ac7d
[18:32] <LLStarks> 7d47618a2ade0cb6d8a0b2597029c383c1662fa0
[18:32] <LLStarks> 6db6340c42d027b6364d49fa99d69019aca24de4
[18:33] <LLStarks> i  can only assume a6866 is the culprit since its the largest
[18:33] <LLStarks> or 7d4
[18:34] <LLStarks> rather
[18:35] <LLStarks> i'm trying to narrow further, but i hate kernel compilation. is there an easy way to compile iwlwifi on its own without splicing patches into a compat-wireless tree?
[18:35] <tgardner> apw, saw that earlier this AM on the wireless mailing list
[18:36] <apw> LLStarks, not that i know of, i generally just do full rebuilds every time
[18:37] <LLStarks> can i offload the build to a farm or something?
[18:37] <apw> LLStarks, i have a build machine i use at home for them
[18:41] <LLStarks> hopefully, it be sufficient to pull a 2.6.34 release commit for compat-wireless and then patch upwards towards the bug.
[18:42] <LLStarks> but even then, compat-wireless pisses me off since intel/iwlwifi driver selection builds everything but that directory.
[18:45] <LLStarks> god. android needs its own vcs repo server.
[18:45] <LLStarks> i never see vanilla kernel releases bog down the server this bad.
[19:14] <apw> tgardner, right have gin and tonic in hand ... so am going to call it a day
[19:16] <kees> apw: that's the way to start the holiday :)
[19:43] <Keybuk> apw, kees: that's the way to start the working day too
[19:46] <kees> Keybuk: heheh
[21:32]  * jjohansen lunch
[23:39] <Keybuk> yofel: thanks


[05:28] <orated> Hello! I read that next release of Ubuntu will be of  ~750MB which will fit in DVD. What is the reason for it? And why keeping it only little more than 100MB for it to go out of CD?
[12:16] <BluesKaj> Hey all


[01:15] <[insert_name_her> so do i have to build this myself or what?
[10:12] <lool> hahaha gentoo on freerunner
[10:13] <lool> "This mean you can cross- and natively compile a basic system..."
[10:13] <lool> Native compile   \o/
[10:31] <ogra> lool, well, isnt OE the same as gentoo, only smaller ?
[21:49] <sof> Hi
[21:49] <sof> Does anyone know of a calibration tool that works on ARM?


[05:50] <hikiko> hello
[08:21] <larsu> good morning!
[08:24] <pitti> larsu: hey Lars!
[08:24] <pitti> hello hikiko, too!
[08:24] <pitti> pretty lonely here with folks travelling..
[08:25] <larsu> indeed. Morgen pitti!
[08:43] <alexarnaud> Good morning all
[08:43] <alexarnaud> hikiko: Hi
[08:54] <willcooke> morning gang
[08:54] <larsu> hi alexarnaud and willcooke!
[09:01] <ksamak> hoy all
[09:10] <Laney> hey!
[09:10] <Laney> sorry for being late
[09:10] <larsu> g'day Laney!
[09:10] <Laney> got a friend over to paint in our living room
[09:11] <Laney> had to show her where all the stuff is
[09:11] <Laney> hey larsu
[09:12] <larsu> what's she painting?
[09:13] <Laney> starting with the skirting
[09:13] <Laney> then window frames
[09:13] <Laney> then walls
[09:13] <Laney> then if that goes really well, part of the outside wall!
[09:13] <Laney> basically we/I could have done it, but we didn't over 15 months or however long we have been here now
[09:13] <Laney> and she was looking for jobs to do
[09:14] <Laney> seemed fair
[09:14] <larsu> cool :)
[09:14] <alexarnaud> Laney: it's a good deal yeah
[09:38] <pitti> hey Laney!
[09:38] <Laney> hi there pitti!
[09:38] <Laney> what's up?
[09:39] <Laney> are you having a good sprint?
[09:39] <pitti> Laney: guess what -- handholding LXC workers and making adt-run more robust against more errors :)
[09:39] <pitti> Laney: I do, yes! (but in the afternoon/night)
[09:39] <pitti> the three guys kept me full-time busy with questions, MPs, setup, etcl
[09:40] <pitti> but they all managed to set up the infra in juju-local, and start hacking on it
[09:40] <Laney> great
[09:41] <Laney> I thought that it was going to cover errors, CI train and other related bits too
[09:41] <Laney> seems not?
[09:41] <pitti> Laney: not this sprint, this is for p-m
[09:41] <pitti> Laney: we'll have 3 more sprints for the other pieces of infra
[09:42] <pitti> Laney: today we want to look into a web/SSO based test retry button
[09:42] <Laney> nice!
[09:43] <Laney> I guess that will be the first dynamic piece on the server
[09:44] <pitti> yeah, scary
[09:44] <pitti> so far everythign is nice and read-only
[09:44] <pitti> Laney: btw, do you know why http://autopkgtest.ubuntu.com/packages/g/glib2.0/xenial/s390x/ is so flappy?
[09:45] <pitti> Laney: is that a matter of running against more triggers in -proposed, or just a flaky test and I'll retry until it sticks?
[09:45] <Laney> pitti: I didn't really look yet
[09:45] <Laney> is it always the same failure?
[09:46] <pitti> Laney: I'm still trying to find the failure; it's not "FAIL:", it's not "ERROR:", goddammit world, agree to some common string to search for
[09:46] <pitti> it's not "not ok" either
[09:47] <Laney> pitti: "killed by signal"
[09:48] <pitti> GLib-GIO:ERROR:/build/glib2.0-dQLvhN/glib2.0-2.47.4/./gio/tests/gdbus-proxy.c:826:fail_test: code should not be reached
[09:48] <pitti> # GLib-GIO:ERROR:/build/glib2.0-dQLvhN/glib2.0-2.47.4/./gio/tests/gdbus-proxy.c:826:fail_test: code should not be reached
[09:48] <pitti> cleaning up pid 6856
[09:48] <pitti> Test glib/gdbus-proxy.test failed: Child process killed by signal 6
[09:48] <pitti> I think that's the one
[09:48] <Laney> oh man, gdbus tests
[09:49] <pitti> failure in<EMAIL_ADDRESS>looks different
[09:49] <pitti> (/usr/lib/glib2.0/installed-tests/glib/gdbus-threading:6884): GLib-GIO-ERROR **: connection had too many refs
[09:49] <pitti> cleaning up pid 6886
[09:49] <pitti> Test glib/gdbus-threading.test failed: Child process killed by signal 5
[09:49] <Laney> still gdbus though
[09:49] <Laney> so at least the same area
[09:49] <pitti> same on the next failure
[09:49] <Laney> I think we know someone who speaks dbus quite well
[09:49]  * Laney looks west
[09:50] <Laney> could try to get it in an accessible instance
[09:50] <pitti><EMAIL_ADDRESS>is pcre, but I think that was due to pinning
[09:50] <Laney> pcre broke every arch
[09:50] <Laney> and is fixed
[09:50] <pitti> Laney: can you ssh<EMAIL_ADDRESS>?
[09:51] <pitti> Laney: I mean firewall-wise (I didn't import your key yet)
[09:51] <Laney> pitti: yeah
[09:51] <Laney> I know the password :)
[09:51]  * Laney h4x0r
[09:51] <pitti> Laney: ah, ok -- I just did ssh-import-id lp:laney
[09:51] <Laney> I've stolen this before to test stuff
[09:52] <pitti> "12345, the same combination that I use on my luggage!"
[09:52] <pitti> Laney: so I guess I'll just retry some more, and if I get bored I force it?
[09:52] <pitti> not really libselinux' fault anyway
[09:53] <Laney> well... I'm going to upload a new upstream release to experimental today
[09:53] <Laney> and sync that later or tomorrow
[09:53] <pitti> but nice, glib2.0 is the last s390x specific regression, I managed to fix all the other ones
[09:54] <pitti> all other regrssions happen on all arches
[09:58] <Laney> adt-xenial-rva0ksiq  RUNNING  <IP_ADDRESS>  -     -       NO
[09:58] <Laney> ubuntu@aupkg01:~$ lxc-console -n adt-xenial-rva0ksiq
[09:58] <Laney> adt-xenial-rva0ksiq is not running
[09:58] <Laney> thanks lxc!
[09:59] <pitti> Laney: is that s390x?
[09:59] <pitti> ah yeah, that
[09:59] <pitti> $ sudo lxc-attach -n adt-xenial-rva0ksiq systemctl  status
[09:59] <pitti> Laney: ^ that clearly works
[10:00] <pitti> Laney: but I've never used lxc-console
[10:01] <Laney> pitti: ah right
[10:01] <Laney> lxc-start-ephemeral printed out that command for me to use
[10:01] <Laney> oh right, sudo, /me fails
[10:06] <pitti> ah, I finally know how to fix these eternal armhf hangs
[10:06]  * Laney runs one of the tests in a loop
[10:06] <pitti> Laney: hah! lucky day! http://autopkgtest.ubuntu.com/packages/g/glib2.0/xenial/s390x/
[10:07] <pitti> http://autopkgtest.ubuntu.com/packages/g/glib2.0/ -> IMPECCABLE!
[10:07] <Laney> perfect package, no problems here
[10:07]  * Laney coughs
[10:07] <Laney> GLib-GIO:ERROR:/build/glib2.0-dQLvhN/glib2.0-2.47.4/./gio/tests/gdbus-proxy.c:826:fail_test: code should not be reached
[10:07] <Laney> # GLib-GIO:ERROR:/build/glib2.0-dQLvhN/glib2.0-2.47.4/./gio/tests/gdbus-proxy.c:826:fail_test: code should not be reached
[10:07] <Laney> woot
[10:08]  * Laney saves this state for a certain ARL
[10:08] <pitti> ARL?
[10:08] <pitti> oh, ARL!
[10:08]  * pitti hugs desrt
[10:14] <Laney> larsu: heeeeeeeeeeeey larsu
[10:15] <Laney> gtk css help required
[10:16] <Laney> larsu: I was looking at webkit scrollbars (see devhelp on xenial for example)
[10:16] <Laney> as far as I can tell it is drawing them itself instead of using gtk's ones
[10:16] <Laney> https://sources.debian.net/src/webkit2gtk/2.10.4+dfsg1-1/Source/WebCore/platform/gtk/ScrollbarThemeGtk.cpp/ <- this is the file in question
[10:17] <Laney> but there is some bug with drawing the background, it gets glitchy after you scroll
[10:18] <Laney> https://paste.ubuntu.com/14581466/ adding those two rules makes it look somewhat normal (probably acceptable)
[10:18] <Laney> wondering if you can help suggest the right way to do it
[10:45] <andyrock> monring
[10:45] <andyrock> *morning
[10:45] <willcooke> hey andyrock
[11:03] <larsu> Laney: hm no clue. Let me check
[11:03] <larsu> does it work with Adwaita?
[11:05] <Laney> umm didn't actuallyt ry
[11:06] <larsu> it does
[11:06] <Laney> yeah sort of
[11:06] <larsu> sort of? Works fine for me
[11:06] <Laney> they are obviously still custom scrollbars there though
[11:06] <larsu> ah, true
[11:06] <larsu> maybe they just don't draw them in that case, but let ebkit handle them?
[11:07] <Laney> yeah but still themed
[11:07] <Laney> so I guess we can find out which rules are needed and put those in
[11:08] <larsu> hm but I can't find anything :/
[11:11] <larsu> Laney: they're not doing anything webkit specific, but setting backgrounds (like your patch)
[11:17] <larsu> your patch makes it work for webkit windows, but breaks the style of other windows
[11:17] <Laney> I know, it applies to too much
[11:18] <Laney> just wanted to see if it was fixable by styling at all
[11:18] <Laney> I also don't know why you have to have the .scrollbar.slider rule since the same thing is in the theme already
[11:18] <Laney> but there's no slider without it
[11:19] <larsu> I see it without it
[11:19] <larsu> or I misunderstand what I mean :)
[11:21] <Laney> weird, I need both rules
[11:25] <Laney> larsu: do you think you could look at this please? if you have time
[11:25] <larsu> yep, already doing it :)
[11:25] <Laney> I have a load of stuff ready to move to webkit2
[11:25] <Laney> and kick the shitty old one out
[11:25] <larsu> \o/
[11:26] <Laney> thanks!
[11:26] <Laney> keep bumping into mcatanzaro on bugs too
[11:26] <Laney> seems he is also doing this for fedora
[11:26] <larsu> hehe
[11:44] <Sweet5hark> libreoffice 5.1.0~rc2 finished building locally. now lets see about libreoffice-l10n
[12:06] <larsu> Laney: could you try it out please? https://code.launchpad.net/~larsu/ubuntu-themes/webkit-scrollbar
[12:09] <Laney> okay!
[12:21] <Laney> larsu: is it less rounded than the regular scrollbars?
[12:22] <Laney> otherwise it looks good to me
[12:22] <Sweet5hark> question: how do you get gcc to commit an internal compiler error?
[12:22] <Sweet5hark> (gcc6 that is)
[12:23] <Sweet5hark> answer: LibreOffice, based on technology breaking your toolchain since 1985 ...
[12:27] <larsu> Laney: no change in the roundedness
[12:27] <larsu> but appears like it to me as well
[12:28] <Laney> might be because they are wider
[12:28] <Laney> so look more square
[12:29] <larsu> I wonder why
[12:29] <larsu> should be the same as expanded overlay scrollbars
[12:31] <larsu> Laney: ah, webkit seems to calculate slider width slightly differently. Good enough to keep like this?
[12:36] <Laney> larsu: yeah if it's not fixable in the theme
[12:58] <Laney> jdstrand: hi, would it be possible for someone to get to bug #1475021 quite soon please?
[12:58] <Laney> we have appstream-glib in depwait for some time on this
[13:00]  * Laney back soon
[13:21] <willcooke> https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1534085
[13:21] <willcooke> \o/
[13:21] <willcooke> thanks Laney
[14:08] <Laney> willcooke: woot
[14:16] <desrt> Laney, pitti: good morning
[14:16] <desrt> everyone else, good morning as well :)
[14:18] <Laney> hi desrt!!!!
[14:18] <desrt> Laney: what's going on here?
[14:18] <Laney> EVERYTHING (not much) is BROKEN (sometimes doesn't work)
[14:19] <Laney> some gdbus tests seem not very good on s390x
[14:19] <desrt> i noticed that assert is tied to a timeout...
[14:19] <desrt> i don't suppose the test machine is super-slow...
[14:20] <Laney> i think that it is the opposite
[14:20] <Laney> do you have VPN?
[14:20] <desrt> yes
[14:21] <Laney> ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no<EMAIL_ADDRESS>[14:21]  * desrt clicks a couple of buttons and lets NM do the work
[14:22] <Laney> then screen -r
[14:22] <desrt> does ubuntu@ have a password? :)
[14:22] <Laney> I imported your key
[14:22] <Laney> allegedly
[14:22] <desrt> okay.
[14:22] <Laney> but you could try to guess the password
[14:23] <desrt> i'm in
[14:23] <desrt> my yubikey seems to have trouble resuming from suspend...
[14:23] <Laney> screen window 0 and 1 show the two which have failed on the real instances lately
[14:23] <Laney> and FYI you are inside an lxc container there
[14:24] <jdstrand> Laney: re 1475021 - I'll talk to tyhicks about it
[14:24] <Laney> thanks jdstrand, we'd like to get the ground prepared for uploading gnome-software quite soon
[14:24] <Laney> so that the universe can explode with enough time for us to glue it back together
[14:24] <larsu> morning desrt!
[14:24] <larsu> how goes?
[14:25] <desrt> good
[14:25] <desrt> wishing i had glasses
[14:25] <larsu> come to Berlin. Took them 1 day
[14:25] <desrt> i went to a place here.  they did the test and sent me away.
[14:25] <Laney> i showed rosie the picture of larsu with specs
[14:25] <Laney> she approved
[14:25] <jdstrand> Laney: ack
[14:25] <larsu> Laney: :)
[14:25] <Laney> "they look like mine"
[14:25] <larsu> Laney: say hi to her!
[14:26] <Laney> will do!
[14:27]  * Laney wonders how/what the ubucon people are doing
[14:27] <Laney> guess it's still kind of early there
[14:28] <jdstrand> Laney: question for you-- just otoh, can you think of a reason why dlna wouldn't work on xenial in rhythmbox any more when it has the same upstream version as wily (and the Ubuntu delta didn't have any relevant changes), grilo is the same as wily and grilo-plugins only has one irrelevant change over wily?
[14:29] <jdstrand> (it the dleyna code in grilo that handles this afaik)
[14:30] <desrt> Laney: how do i get other screens into the container?
[14:30] <Laney> jdstrand: hmm, nope, I tried this out a couple of weeks ago
[14:30] <jdstrand> Laney: the dlna server just doesn't show up any more (but daap still does)
[14:30] <Laney> desrt: ctrl-a, <n>
[14:30] <desrt> i know the screen part :p
[14:30] <jdstrand> Laney: it worked for you a couple of weeks ago?
[14:30] <desrt> i'm missing the 'not in the container' part
[14:30] <Laney> oh right, SSH to its IP
[14:31] <Laney> thought you might be a tmuxer or something
[14:31] <Laney> jdstrand: well I could be confused about the difference between dlna and daap to be honest
[14:31] <Laney> I shared my library between two rhythmboxen
[14:31] <jdstrand> I see
[14:31] <jdstrand> I think rhythmbox exports as daap, iirc
[14:32] <jdstrand> exports/shares, whatever the terminology is
[14:32] <Laney> does it work with another client?
[14:32] <jdstrand> well, yes, wily rhythmbox :)
[14:32] <jdstrand> the minidlna server didn't change
[14:32] <tjaalton> codec search seems broken on xenial
[14:32] <jdstrand> I only upgraded to wily
[14:33] <jdstrand> I have both forked-daapd and minidlna exporting at home
[14:33] <jdstrand> and rhythmbox used to see both on wily. on xenial, it only sees daapd
[14:33] <jdstrand> tjaalton: it doesn't even see the server at all
[14:34] <jdstrand> (and it can play all the files from daapd)
[14:34] <jdstrand> so I don't think it is codec related
[14:34] <Laney> ok, I'll try to look
[14:34] <Laney> is there a bug that you can assign to me?
[14:34] <tjaalton> this was just an observation on my local machine with totem trying to play bbb :)
[14:34] <tjaalton> fresh install, can't find codecs to install
[14:34] <jdstrand> Laney: minidlna is really easy to setup. apt-get it, then adjust the config file for a dir of music
[14:35] <tjaalton> though I guess it's due to the software manager migration
[14:35] <jdstrand> Laney: I can. I'll work up a reproducer too. thanks
[14:36] <Laney> thanks!
[14:36] <Laney> I just want to be assigned something so I have less chance of forgetting :)
[14:39] <desrt> uhh
[14:39] <desrt> gdbus-proxy is failing on my machine this morning
[14:39] <desrt> dispite discheck having worked only two days ago
[14:39] <desrt> that's neat.
[14:40] <Laney> tjaalton: looks like something happened to break sessioninstaller
[14:44] <tjaalton> yeah
[14:44] <tjaalton> just saw the trace
[14:58] <desrt> okay.  back to not failing.  great.
[14:58]  * desrt made a mistake
[15:05] <Laney> tjaalton: https://paste.debian.net/366793/ ?
[15:08] <tjaalton> Laney: hang on
[15:09]  * Laney grips tight
[15:09] <desrt> Laney: gdb on this machine seems to be ... not great
[15:09] <Laney> oh?
[15:10] <desrt> even with debug symbols installed there are fairly big gaps in the backtraces
[15:11] <tjaalton> Laney: nope :/
[15:12] <Laney> tjaalton: did you kill the daemon?
[15:12] <Laney> it fixed it for me
[15:12] <tjaalton> ah
[15:12] <Laney> xnox: is gdb on s390x supposed to be working properly?
[15:12] <tjaalton> Laney: correct, works
[15:13] <xnox> Laney, yes....
[15:13] <xnox> Laney, do you have bugs =)
[15:13] <Laney> meet desrt
[15:13] <Laney> tjaalton: cool!
[15:13] <Laney> I'll upload that then, thanks for reporting
[15:13] <Laney> just kicked a stair and now my toe is bleeding
[15:14] <Laney> probably should have kept the nail shorter :/
[15:14]  * Laney goes to clean that up
[15:14] <desrt> xnox: hi.  seeing weird backtraces on a x390 machine :)
[15:14] <xnox> desrt, x390 ssl cert? or s390x machine?
[15:14] <desrt> uh.  the other one :)
[15:14] <desrt> isn't the ssl thing x509? :)
[15:15] <tjaalton> Laney: thanks :)
[15:23] <pitti> Laney: ok, I think I should have finally stopped the worker log spam, sorry
[15:23] <Laney> pitti: pinning fun I assume
[15:24] <pitti> Laney: that, and unclear to me why it happened; but I built a new wily base image, it only happened for wily ..
[15:24] <Laney> :/
[15:24] <pitti> Laney: and then I screwed up a fix from this morning which was supposed to fix the s390 tmpfails
[15:24] <pitti> (which didn't show in local testing)
[15:24] <pitti> but should be all good now
[15:24] <pitti> well, I still need to fix the eternal armhf hangs, but at least I now know how
[15:25] <pitti> (and what happens)
[15:25] <pitti> i. e. I can't fix the hung containers, but at least have adt-run ignore them insted of waiting forever
[15:29] <desrt> Laney: cannot reproduce on a fresh build >:|
[15:29] <desrt> Laney: can you tell me a bit more about the setup here?  these are installed tests running against a new library version, or what?
[15:31] <Laney> desrt: build/install versions should be the same
[15:34] <Laney><EMAIL_ADDRESS>[15:35] <Laney> they are both 2.47.4-1 there
[15:35] <desrt> nod.
[15:50] <andyrock> if i do
[15:50] <andyrock> g_signal_emit (...., g_strdup(...))
[15:51] <andyrock> I'm supposed to g_free the string in the callback right?
[15:52] <andyrock> desrt: ^^^
[15:52] <desrt> uh
[15:52] <desrt> don't do that :)
[15:52] <andyrock> or it's automatic?
[15:52] <desrt> g_signal_emit will fire the signal directly in place
[15:53] <desrt> so as long as the string in question will survive until g_signal_emit() returns, you don't need to dup it
[15:53] <andyrock> so I can free after g_signal_emit
[15:53] <andyrock> right?
[15:53] <desrt> in fact, depending on the signal, it may also dup the string for itself (and free it)
[15:53] <desrt> yes.  definitely.
[15:54] <desrt> but maybe you don't need to dup it at all, is what i'm saying...
[15:55] <desrt> but in any case: absolutely do not g_strdup() something you pass to g_signal_emit() and free() inside a handler.  that is absolutely broken.
[15:55] <desrt> and not just 'in theory' -- there is no guarantee that the string passed to the handler will have the same pointer value as the string passed to g_signal_emit() -- only that it will have the same value (as a string)
[15:55] <andyrock> ok thanks! :)
[16:31] <qengho> If I'm merging a package from Debian, and I quote the patches that will remain in the package, should I also reference the Debian bugs with "closes: #nnnn"? That seems weird.
[16:32] <Laney> You don't have to, but it's nice to have them referred to somewhere
[16:32] <Laney> the patch header is fine for that
[16:35] <qengho> Thx
[17:13] <desrt> Laney: got a working theory
[17:14] <desrt> it's a stretch, though
[17:17] <qengho> dpm: Hi. Some translations team didn't respond to join requests. I advised a would-be contributor to message admins individually, wait, and then open a Question against Launchpad. Was that right?
[17:18] <dpm> qengho, it used to be, but nowadays no one really looks at those questions. The best thing might be to send an e-mail to ubuntu-translators@ubuntu(dot)com
[17:19] <Laney> desrt: real bug or test bug?
[17:20] <desrt> test bug
[17:20] <desrt> like usual
[17:20] <desrt> still investigating...
[17:20] <Laney> fun
[17:21] <Laney> no need to waste all day on it if you have better things to be doing
[17:35] <desrt> Laney: actually, i've binned that first theory and am now tending toward 'actual bug'
[17:36] <desrt> the proxy does a sequence of things in order to get the service to start up... first it tries to StartServiceByName... and if that fails then it does GetNameOwner in order to figure out if it already exists
[17:37] <desrt> the problem is that maybe for some random reason (like a well-placed exec()) the service might pop into existence in between those two and the process may receive a NameOwnerChanged
[17:37] <desrt> in both cases, gdbus will try to GetAll properties on the service... which it seems to be doing twice
[17:37] <desrt> that much, at least, is a bug in the proxy
[17:38] <desrt> so ya... one of those this-timing-issue-would-never-happen-in-the-real-world issues
[17:38] <desrt> but it's a legit issue
[17:40] <Laney> and I guess the test is making a new proxy async then execing the service
[17:41] <desrt> the weird thing is that it should result in the async call finishing twice, as far as i can tell
[17:41] <desrt> and instead, it's finishing zero times
[17:41] <desrt> very odd
[17:42]  * desrt curses the gigantic ugly asyncinit state machine in here
[17:44] <desrt> hilariously, this could just be an entirely unrelated bug because it also happens in the case where the test runs properly
[17:44]  * desrt sighs
[17:58]  * Laney hugs desrt
[17:58] <Laney> it's going to be okay
[17:58]  * Laney goes off to roast a chicken
[18:13] <Mirv> is there a bug for "lightdm doesn't show user background anymore and theme seems a bit resetted (domain name has grey background and date is black font etc)"
[18:13] <Mirv> I have had it before 14.04 out of the blue and it happened again. I can't figure out how I fixed it last time, but I remember it was not straight-forward.
[18:13] <Mirv> like uninstalling / resetting config files for lightdm + unity-greeter not enough
[18:32] <Mirv> I meant, before on 14.04 and now again on 14.04. well, I'll eventually have time to find out the fix and at least document that somewhere.
[19:01] <willcooke> night night all
[22:12] <attente> robert_ancell: hey, which branches of gnome-software should i be looking at?
[22:12] <robert_ancell> attente, wip/rancell/ubuntu-reviews-3-18
[22:13] <attente> ubuntu-ratings?
[22:13] <robert_ancell> attente, that's been merged into ubuntu-reviews
[22:14] <attente> robert_ancell: ok
[22:14] <attente> robert_ancell: i can't see ubuntu-ratings on the remote though
[22:15] <robert_ancell> attente, https://git.gnome.org/browse/gnome-software?h=wip%2Francell%2Freviews-3-18
[22:15] <robert_ancell> I'll delete the other branches


[00:38] <Unit193> Adri2000: Howdy!  First off, thanks for maintaining filezilla.  Have you considered using wxgtk-gtk3?