robert_ancellattente, awesome, thanks00:31
=== duflu_ is now known as duflu
=== maclin1 is now known as maclin
pittiGood morning05:15
hikikodesrt, here?07:07
hikikoTrevinho, ?07:07
hikikommm too early :)07:07
hikikoI just saw your logs07:07
hikikoanyway, I didn't know gtk didn't provide shape information but anyway the shape is only needed to find the alpha regions, so if gtk has the alpha information we can support windows with alpha07:09
hikikoabout the gtk side: I don't know if it's worth the pain to add it07:15
hikikoI just mentioned the problems it will fix07:15
=== ochosi_ is now known as ochosi
tjaaltondoes anyone know why ~/.Xmodmap is not being used anymore? apparently it broke around 13.1007:21
tjaaltonI guess it's inherited from gnome07:26
andyrockgood morning07:27
seb128good morning desktopers08:16
seb128hey andyrock tjaalton08:16
seb128tjaalton, I think gnome(unity)-settings-daemon used to load it, but see https://bugzilla.gnome.org/show_bug.cgi?id=725038#c308:17
ubot5Gnome bug 725038 in keyboard ".XCompose is ignored" [Normal,Resolved: notabug]08:17
seb128need a script like https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/common/input-device-example.sh?h=gnome-3-18 it seems08:18
tjaaltonseb128: well I meant .Xmodmap, and for that there's https://bugzilla.gnome.org/show_bug.cgi?id=72187308:19
ubot5Gnome bug 721873 in Config "xmodmap settings are reset after keyboard layout switching and resume" [Normal,New]08:19
seb128tjaalton, right, read the bug comment, don't stop to the title :p08:19
tjaaltonI did read it08:20
tjaaltonthat example script link from the bug didn't work08:20
tjaaltonbut ok08:20
tjaaltonthis might be a better approach than #6 from https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642 :)08:21
ubot5Launchpad bug 1243642 in xorg (Ubuntu) ".Xmodmap not automatically loaded on start" [Undecided,Confirmed]08:21
seb128tjaalton, yeah, they removed the file, see the url I copied, it's still in 3.1808:22
tjaaltonso I think providing something installed by default that users can use to shoot their foot with might be in order. nothing would be used by default08:23
seb128hey Laney! how are you?09:06
Laneyhey seb128!09:12
Laneygoooooooooooood thanks09:13
Laneyalthough it is cold09:13
Laneywe did alright at the quiz but didn't win :-(09:13
Laneyhow are you?09:13
seb128it' sunny here!09:13
seb128can't win everytime09:13
seb128it wouldn't be special/so nice anymore otherwise!09:13
Laneyyeah + everyone hates you then09:15
seb128so I figured you the other gtk theming issue I was looking at, or at least I found the line to backport to fix it, even if I don't understand what a .entry.flat is :p09:18
seb128or where the flat style is using for widgets09:18
seb128but seems that listview is one of those cases and that styling it there fixes the entry height issue09:19
ksamakhoy all09:19
LaneyA CSS class that is added when widgets that usually have a frame or border (like buttons or entries) should appear without it.09:20
seb128where did you get that definition?09:24
seb128but yeah, in any case it seems like listview editable row is built using a flat entry09:24
seb128I just don't know if flat entries are used in other context and what side effect that might have :-/09:25
seb128but well, adwaita/high contrast have the line I copied so it should be right (but it doesn't mean there isn't some more special cases needed on top)09:25
seb128the line was added as part of a big commit adding flat style09:26
seb128so difficult to get a sense for a logic set for the entry case09:26
seb128oh well, let's do those changes and see if everybody is happy or if we get new reports ;-)09:27
Laneywhat does the style do?09:27
seb128it set the padding to 2px09:28
seb128where normal entries have 5px 7px09:28
seb128.entry {09:28
seb128    padding: 5px 7px;09:28
LaneyI suppose it makes sense09:28
Laneyflat is an entry without a border09:28
seb128  .entry.flat, .entry.flat:focus {09:28
seb128    padding: 2px;09:28
Laneylike an inline thingy in a treeview09:29
seb128what I don't get is that if you set 3px there then it's back to being way to big09:29
Laneythe thing I pasted was from devhelp09:29
seb1282px feels a bit too shrinked09:29
seb128oh well, that's going to be good enough09:29
seb128I wonder if there is an issue like "if it doesn't fit in the row then the un-flat version is used"09:30
seb128Laney, thanks, doesn't explain why 3px making it go unflat (or look like it does, maybe it's something else) though ... but I don't want to spend the week on that, so it's going to stay this way with the 2px which is working09:48
alexarnaudhello everyone !10:07
seb128hey alexarnaud10:10
alexarnaudhey seb128, how are you?10:17
seb128alexarnaud, good, and you?10:32
Laneyricotz: hi, you do zeitgeist upstream stuff right? Trevinho wrote some patches - do you want them upstream? https://launchpadlibrarian.net/236160096/zeitgeist_0.9.16-upstart-and-vacuum-support.debdiff10:44
=== vrruiz_ is now known as rvr
desrthello world\n11:43
desrthikiko: hey11:43
ricotzLaney, hi, interesting, the upstart parts not so, a systemd service for the vaccum part would be better11:44
Trevinhoricotz: well, I don't know much about systemd services (yet) :)11:44
ricotzTrevinho, ok, upstart is dead though11:45
Trevinhoricotz: well, not for us :)11:45
Trevinhoat least, not in session11:45
Trevinhofor some time11:45
Trevinhobut I understand11:45
ricotzTrevinho, maybe you can take a look at making them systemd ones11:46
Trevinhoricotz: I could, but... Not in short time I think11:46
Trevinhoricotz: as for the vacuum side, I also was wondering whether removing some old data would be somewhat wanted...11:47
Laneyricotz: is systemd in the session a real thing yet?11:47
Laneyit's not on our side, anwyay11:47
Trevinhoricotz: I mean, I've the same db here I had during 10.10... So it's getting about 95MB sqlite file... This causes my zeitgeist-fts to use about 700-800Mb of resident memory. Always. Not sure whether it's a leak or something wrong with that (I had no time to play with massif yet)11:48
Trevinhothat indeed slows down the searches...11:48
TrevinhoLaney: ah, not related to this, but if you can publish https://requests.ci-train.ubuntu.com/#/ticket/1029 then seb128 could get his GS icon before beta.. :)11:49
ricotzTrevinho, "vaccum" isnt removing real data, just reorganize and drop unlinked data from the persistent file?11:49
Trevinhoricotz: yes, no removal11:50
ricotzLaney, hmm, I thought so it would11:50
Trevinhoricotz: it rebuilds avoiding fragmentation11:50
ricotzTrevinho, right11:50
Laneyricotz: anyway, we can handle that in the package but the vacuum program is probably good for you11:51
ricotzTrevinho, so having an option to drop old data could be interesting too11:52
ricotzLaney, absolutely11:52
LaneyTrevinho: the normal thing to do for upstart is to disable xdg autostart by putting a desktop file in /usr/share/upstart/xsg/autostart with Hidden=true11:55
* Laney will change that11:55
LaneyTrevinho: what's with this runner stuff?12:06
hikikohi desrt12:36
desrthey hikiki.. wanted to talk about the shadows12:39
desrtyou used xshape?12:40
Laneyhey desrt!12:40
* Laney missed your 'hi'12:40
desrtmorning, laney :)12:40
seb128hey desrt12:44
desrthello all you latecomers12:44
=== alan_g is now known as alan_g|lunch
=== hikiko is now known as hikiko|ln
=== hikiko|ln is now known as hikiko
hikikolol desrt say hikiko pls13:10
hikikoI didn't see it13:10
desrtoops.  typo :)13:10
hikiko/nick hikiki13:11
hikikoyes I used xshape, to find the alpha13:11
hikikothere are 3 different bugs related to the gtk windows the 2 of them can be solved unity-compiz side13:12
desrtah.... iirc that's not what we discussed13:12
desrtthe idea was to use the content of the pixels13:12
hikikothat's what I used I took it from the shape rectangles, I just didn't know that gtk windows don't provide us with shape info so I have to do it 1 more time for windows with alpha and not shape13:13
hikikothis will fix the shadows shape13:14
hikikobut not the black dots13:14
hikikowhich is a different prob I am trying to fix now13:14
hikikoblack dots are caused by buggy alpha blending somewhere in compiz13:14
hikikoI am debugging the opengl plugin13:14
hikikothey should be transparent13:14
hikikoand there's a 3rd issue13:16
hikikobut I don't know if gtk is maintained by us and we should fix it13:16
hikikoideally the alpha windows should provide the shape too13:16
hikikobecause if they don't, window managers will consider the transparent parts parts of the window13:17
hikikoand will receive events there13:17
hikikoanyway I guess that's not very important13:17
=== Guest92168 is now known as fredp
=== fredp is now known as Guest86707
ricotzTrevinho, btw, you should not leave those print() statements in13:38
alexarnaudseb128: very good thanks13:40
TrevinhoLaney: so, I was having lunch... Well, in order to make sure that dbus launches the upstart instance we need that... I'm doing that also in bamf. Since there's no support for upstart to launch dbus daemons and controlling them (It was something planned in theory, and documented too, but reverted for some reason)13:45
Trevinhoricotz: well... I wanted to add some output...13:45
Trevinhoricotz: and without any other logging... It had to be a very simple script (which I couldn't do in python because of the gir dependency which I didn't want to include)13:46
=== hikiko is now known as hikiko|ln
Trevinhohikiko|ln: let's go for a different solution, I'll work on it in the mean time... You can go back focusing in the ezoom thing since it's getting late.13:47
ricotzTrevinho, hmm, ok, FAIL needs a \n then13:54
Trevinhoricotz: no, because of the warning... It will add it13:54
ricotzor a some separation13:54
TrevinhoI added that in both cases initially... Then, it wasn't needed.13:54
LaneyTrevinho: https://paste.ubuntu.com/15187274/ ?13:56
=== alan_g|lunch is now known as alan_g
TrevinhoLaney: ehm, yeah, what?13:59
TrevinhoLaney: ah, you changed something?14:00
Laneyyes, I eliminated all the upstart stuff14:00
TrevinhoLaney: well, having upstart to manage it would have ensured that the service would have ran only when needed, and that could have been controlled by initctl... With actual respawn and such.14:01
Laneydbus will launch it again anyway14:02
Trevinhobut if you prefer this way...14:03
Laneyyou only really needed it to make an event that the vacuum event could block14:03
TrevinhoYeah, well, it will relaunch it when invoked...14:03
TrevinhoBUt it's fair, I would just have loved it to be controlled by upstart as it allows better management for us, and some logging... But indeed your version reduces a lot the diff with upstream and so it's more easy to manage (not that I expect many changes upstream side)14:04
Laneyit goes in the journal if launched by dbus which is nice :-)14:10
Laneythanks, going to upload this14:10
* Laney enjoys fast dash14:10
Laneyit feels like it makes a big difference14:10
=== hikiko|ln is now known as hikiko
seb128new snappy dash! ;-)14:15
hikikoTrevinho, let's wait for will because I think he expects that I solve the 2 issues14:17
Laneylunch then bike to tea shop in town14:22
seb128Laney, enjoy!14:22
seb128hikiko, I think it has been ongoing for long enough that it seems at risk for this cycle (we are past ff) and that we look for a plan B, that doesn't stop you to keep working on it, once it's working well we can see what we do, either push it or keep it on the side and use it next cycle14:23
seb128hikiko, but we are saying that it's almost ready to land since january, that proved to not be that simple and it's safe to have a fallback solution14:24
hikikobut I think I could give it a try14:27
seb128hikiko, thanks for the work on fixing those issues btw ;-)14:27
hikikountil next week14:27
hikikobecause, I think I'm close14:27
seb128yeah, that seems ok if you look at it a bit more14:28
hikiko(I'm not opposed to plan B)14:28
seb128Trevinho can think about plan B meanwhile14:28
seb128and we can see what we do next week14:28
seb128Trevinho, andyrock, thanks for the unity/gnome-software integration landing!14:28
desrtwhat stops us from simply setting an xshape from gtk?14:47
desrti mean, other than the "it will be hard" crap14:47
desrt"we may have to do some math"14:48
desrti guess, in any case, i'd prefer not to do the math, given that we have a working solution in the form of Trevinho's property14:48
Sweet5harkseb128: so, seems I cant push to the seeds bzr repo directly (would have been surprised if I could really), so how do I get https://code.launchpad.net/~bjoern-michaelsen/ubuntu-meta/libreoffice-human-to-breeze merged for bug 1506544?14:56
ubot5bug 1506544 in ubuntu-meta (Ubuntu) "Change default Theme for LibreOffice to Breeze for Ubuntu 16.04" [Undecided,New] https://launchpad.net/bugs/150654414:56
seb128Sweet5hark, seems like from the url that you used the wrong vcs?14:57
seb128Sweet5hark, you  should branch lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu.xenial edit, commit push to lp:~bjoern-michaelsen/ubuntu-seeds/<something> then merge propose it14:58
seb128the deb is built from the seed then by whoever does an upload14:59
seb128no need to merge anything to the source14:59
Sweet5harkseb128: I branched from that, but I _think_ lp was resisting pushing/creating that branch ... but it works now, so I must have gotten it wrong.15:03
Sweet5harkseb128: ok, pushed to ~bjoern-michaelsen/ubuntu-seeds/human-to-breeze now and added to bug, and now (after I pushed to the right location) it also works to merge propose it: https://code.launchpad.net/~bjoern-michaelsen/ubuntu-seeds/human-to-breeze/+merge/28703515:08
Sweet5harkseb128: thx15:08
seb128Sweet5hark, thanks15:08
ricotzSweet5hark, seb128, hi, would it be possible to do something about the size of the libreoffice icons (svgs), they are way to huge to be rendered in a reasonable time15:40
Sweet5harkricotz: hmmm, isnt that an upstream topic? I dont think only vendor patching that is helpful ...15:42
ricotzSweet5hark, it is, and you are upstream ;)15:43
Sweet5harkricotz: heh ;)15:43
ricotzI am wondering if there are complaints about it15:44
ricotzlike 1.3M for an icon is insane15:44
ricotzgiven it takes like 200ms to render this *only* this single icon it should also effect the performance of unity's application dash15:45
ricotz(at least on the time if it gets cached afterwards)15:46
Sweet5harkricotz: yeah, that is indeed unfortunate -- esp. since the icons arent really complex artwork anyway, so this is weird.15:57
Sweet5harkricotz:  https://github.com/LibreOffice/core/commit/250feedd8e50e5eb52682a194823567ba5287c60 <- take this as a starting point. doesnt seem to have been touched since then anymore (and pmladek isnt active on libreoffice anymore)15:58
Sweet5harkricotz: would be something to bring up with https://wiki.documentfoundation.org/Design15:58
ricotzSweet5hark, I see, could you make the current best person aware of that?16:13
Sweet5harkricotz: best file a bug upsteam with component UX-advise ...16:16
pittiLaney: bah, these worker emails are annoying -- I want my scalingstacks cleaned!!!16:19
Laneypitti: indeed!16:19
pittiLaney: but the lxd upgrade one this morning was a good warning (as it was an actual upgrade failure), so I don't really want to quiesce them either16:19
* Laney noticed that one16:19
Laneyare the rest just waiting for IS to whack stuff?16:19
pittiyeah, the two RTs I sent on Monday16:19
pittithere's always some DB resource leakage, but it went quite out of hand on lgw16:20
pittiwith 0 instances it claims I use 43 GB RAM16:20
Laneyawesome that it stores this separately in a buggy way16:21
ricotzSweet5hark, https://bugs.documentfoundation.org/show_bug.cgi?id=9814116:34
ubot5bugs.documentfoundation.org bug 98141 in ux-advise "SVG application icons too large/detailed" [Normal,Unconfirmed]16:34
Laneypitti: OOI, do you know why this didn't take down the lxd tests themselves too?16:39
Laneyit seems to not have been an upgrade there but I don't know why16:39
pittiLaney: good question16:40
pittiLaney: actually, the better question is why we got an upgrade of lxd during that (whatever) test16:40
pittiI purge lxc/lxd from the base images16:40
LaneyI assumed it was in the... oh16:40
pittiso any test dependency should be a new install, not an upgrade16:40
pittioh, wait16:41
pittiI purge lxd-client16:41
pittiand lxd doesn't depend on lxd-client (... any more), only recommends:16:41
pittiso I guess lxd is back in the base images16:41
* pitti updates the setup script to purge it harder16:41
=== davidcalle is now known as davidcalle_afk
Laneyso then why didn't it upgrade for lxd itself?16:42
pittithis was a new install of lxd (version 2.0.0~beta4-0ubuntu1, the broken one)16:44
pittiLaney: perhaps that was the version which demoted Depends: to Recommends:?16:44
* pitti checks16:45
pittihm, no16:45
pittiso one way or the other it wasn't on the images on that run16:45
Laneyjust wondering if we could have caught the breakage before it got to release :)16:46
pittiif lxd *was* on the images, then yes16:47
pittibut my intention is that the images are minimal16:47
pittiso we indeed don't do upgrade testing in adt, except for stuff which is in the base system16:47
pittiThe following packages will be upgraded:16:48
pitti  apparmor bind9-host dnsutils fuse isc-dhcp-client isc-dhcp-common16:48
pitti  libapparmor-perl libapparmor1 libelf1 libfuse2 lxd lxd-client os-prober16:48
pittithat was in the log of content-hub/i386 from this morning which exhibited the problem16:49
* Laney ran away16:49
pittiLaney: Creating nova instance adt-xenial-i386-content-hub-20160224-095421 from image ubuntu/ubuntu-xenial-daily-i386-server-20160223.1-disk1.img16:49
pittiLaney: got it16:49
Laneyyes I was just looking to check that16:49
LaneyCreating nova instance adt-xenial-amd64-lxd-20160224-051102 from image ubuntu/ubuntu-xenial-adt-amd64-server-20160224.img (UUID 18c30873-e2a8-4f44-80de-5e44b3cb3049)...16:49
Laneyfrom lxd16:49
pittiLaney: content-hub used a standard image while the earlier lxd used an adt pre-prepared image16:49
Laneyis that an accident?16:50
pittion bos01 I actually fixed the configuration to only use *adt* images16:50
pittibut this morning building the adt i386 image failed on lgw16:50
pittiso we don't have recent adt ones everywhere16:50
pittiLaney: so I could do the same as on bos and create adt images for all stable releases, and only use adt images16:51
pittinormally, it's "all images which match $release-$arch, take the most recent one"16:51
pittiso that we can take the standard cloud images for stable (or for devel if the daily build fails)16:52
pittiI did that on bos for ppc64 as standard cloud images have been seriously broken for several weeks now16:52
pittiok, so we know *why* it happened; it's less clear which way around we want to make that more predictable16:53
pittiwe have the really expensive way of always building/using adt images16:54
pittior live with that jitter16:55
Laneyis it really costly to do it?16:55
pittiLaney: it's immense on lcy01 (as only one attempt out of 20 succeeds)16:55
pittiit's almost always failing on lgw (due to the resource scarcity)16:56
pittiand reasonably straightforward on bos16:56
LaneyMaybe run a version of the setup script each time?16:56
pittiwe do16:56
pittiso it'll do that removal dance16:57
Laneymust be after dist-upgrading though16:57
pittibut so far I only purged lxd-client, not lxd16:57
pittiI just committed a fix to purge lxd and lxc too16:57
Laneyor why was the adt image okay?16:57
pittiso in that sense that will make it predictable again16:57
pittiLaney: because that got dist-upgraded from like wily, where lxd wasn't on the default install yet16:57
pitti(we've only had real xenial images for two or three weeks)16:58
Laneypitti: Okay, I guess this situation is good enough then until the l* regions get upgraded to a better openstack or whatever16:58
pittiLaney: with the setup script fix I just committted, lxd will at least be gone in both scenarios16:58
pittithus be predictable, i. e. adt or standard image should behave the same again, except that tests with the latter take 3 mins longer16:59
LaneyCan we ditch the adt image on bos01?16:59
pittiwell, not for ppc64el16:59
pittistandard cloud ppc64 images are broken, they don't boot17:00
pittimy life is so much fun17:00
* Laney screams17:00
pittiLaney: https://bugs.launchpad.net/cpc-core/+bug/1541757 FYI17:00
ubot5Error: launchpad bug 1541757 not found17:00
pittiyeah yeah, it's private but there17:01
pittidinner o'clock17:01
Laneysee you17:01
* Laney just filed a bug about doing upgrade testing17:01
Laneycould be interesting17:01
=== alan_g is now known as alan_g|EOD
ximionLaney, new AppStream release with all known bugs fixed will be out next weekend19:33
ximionmeanwhile, removing the appstream-data package from Xenial would be helpful, because it causes the old data and the new data to collide (LP: #1548157)19:33
ubot5Launchpad bug 1548157 in appstream-data (Ubuntu) "Remove appstream-data from Ubuntu (xenial)" [Undecided,New] https://launchpad.net/bugs/154815719:33
ximionis only noticed by people who have it installed, which is mainly KDE on Xenial19:34
=== ljp is now known as lpotter
Laneythanks ximion!20:37
LaneyI can't process that but maybe someone who can will see the link ;-)20:37
ximionLaney: that was my plan all along ;-)20:39
ximionI am also playing around with the idea of writing a more powerful data extractor in Go or D20:40
ximionnot yet sure what will come out of this (if it's productive at all), but playing with new languages is fun :)20:40
Laneyximion: can we put a date into the yaml header please?20:44
LaneyI have a suspicion that launchpad is being weird20:44
ximionLaney: I didn't want to put a date in there, since this will cause APT to re-download the data everytime, even if *only* the last-updated date has changed, causing useless downloads20:46
Laneyximion: couldn't you skip updating the file at all if nothing has changed?20:46
ximionimplementing a way to find out if data has changed and only updating the date when the data actually changed would be the sane thing to do, but that is more work to implement20:46
Laneymuch more?20:47
ximionwe would maybe need to hash all data and see if the hash has changed... - if LMDB returns components in a deterministic order20:47
ximion(which AFAIR it does...)20:47
Laneyjust thinking some flag if we found a component to update20:48
ximionatm, I would say quite some work, unless everything happens to work as one would expect ^^20:48
Laneyximion: so here https://github.com/ximion/appstream-dep11/blob/master/dep11/generator.py#L51 return a tuple (msgtxt, len(cpts)) and then here https://github.com/ximion/appstream-dep11/blob/master/dep11/generator.py#L213 set a flag to tell you to skip writing if nothing changed20:55
ximionLaney: if you check whether the returned components are valid or not, this should work...21:00
Laneyi'll try tomorrow or so21:01
ximionweird, my mind was thinking about a completely different project a few minutes ago :P21:01
ximionok, a feature like this sounds sane to me21:01
LaneyI'm just a bit suspicious21:01
Laneybecause I don't see apt downloading the new files for me very often21:01
Laneybut maybe they didn't actually change, but then the mtime has changed21:02
Laneybut that could be because we write them even if nothing changed21:02
ximionLaney: could also be one of the terrible multiprocessing issues, e.g. the one eating up logging data21:02
Laneywill at least be some information to go on21:03
seb128robert_ancell, is there an easy way to tell what gnome-software bugs are downstream or upstream?22:00
robert_ancellseb128, you kind of need to know which plugin the bug is coming from22:02
robert_ancellseb128, Anything in particular you want triaged?22:02
seb128robert_ancell, reported rather22:03
robert_ancellseb128, today, any bugs relating to apt installing / removing are us (distro patch), bugs relating to wrong information are probably appstream (not sure how much of that is us / upstream), though they may be incorrectly interpreted in g-s (us or upstream). Anything related to submitting reviews is us, downloading is technically upstream but practically us.22:04
seb128robert_ancell, ok, some ones22:04
robert_ancellIn short, just file against gnome-software and ping me is probably the safest method22:04
seb128- clicking on updates give little details22:04
seb128at less the (null) in the title is buggy22:04
robert_ancellseb128, I believe that content supposed to be provided in appstream, I haven't looked yet though.22:05
seb128also could we fetch changelogs from the same server update-manager does (is that supposed to work?)22:05
robert_ancellThe null is worrying, because that should show the package name22:05
robert_ancellseb128, this is where is gets complicated. The information can come from any plugin. So I think the vision is that appstream provides all opf this, it just doesn't do the actual installing / removing22:06
robert_ancellBut we can provide all the information ourselves in the apt plugin.22:06
robert_ancellAnd I think that will be the practical solution for many cases.22:06
seb128i think it was working when I tried a week or so ago22:06
seb128so like that one, I better report on launchpad?22:07
seb128we can triage from there22:07
robert_ancellseb128, yes, definitely report on LP first22:07
robert_ancellThen ping Laney / ximion and say "should this info come from appstream?"22:07
robert_ancellseb128, then you can try appstreamcli/appstream-util to try and work out if that information is present. And if it is, then it's a GNOME Software bug22:08
seb128things are listed fine in other sections22:09
seb128the (null) is just in the update section22:09
seb128robert_ancell, btw it still thinks that softwares come from third party/non free22:19
robert_ancellseb128, both third party and non-free?22:20
robert_ancellseb128, can you run with G_MESSAGES_DEBUG=all and check the app summary when you click on it?22:20
robert_ancellThat will show all the metadata we have22:20
seb128robert_ancell, http://people.canonical.com/~seb128/nonfree.png22:21
robert_ancellseb128, ah, the source field is blank for some reason22:22
robert_ancellThat's the info that is used to determine where it came from22:22
seb128I might have dpkg -i that one, sorry22:22
robert_ancellI'm thinking of just setting those in the apt plugin instead of relying on appstream22:22
robert_ancellseb128, as long as the package name is still standard it should show information22:23
seb128ok, others seems just "non-free"22:23
seb128sorry, closed wrong win22:25
robert_ancellBut yeah, I suspect G-S picked up the .desktop file for that but there is no appstream data for some reason22:25
seb128hum, it doesn't list evince22:39
seb128(gnome-software:32072): Gs-DEBUG: ignoring duplicate evince.desktop22:40
seb128that might be one for Laney22:41
ximionrobert_ancell: might be due to Ubuntu wanting to keep the old .desktop filenames for eternity22:44
ximionAS and GS don't expect that22:45
ximionrobert_ancell: might be due to Ubuntu wanting to keep the old .desktop filenames for eternity22:45
ximionAS and GS don't expect that22:45
ximionI'm just guessting though - components with an empty ID or name must never happen22:45
Laneyximion: stop trying to blame everything on that :(23:29
Laneyit made duplicate applications show up, and should be patched now (with a different approach to my as-glib patch)23:30
LaneyI just tried latest g-s and it doesn't show any uninstalled applications ("(gnome-software:13300): Gs-DEBUG: app invalid as state unknown robocode.desktop23:31
Laneygoing back to https://launchpad.net/ubuntu/+source/gnome-software/3.19.5+git20160212.a64f331-0ubuntu1/+build/9000701 works23:31
ximionLaney: that robocode-is-missing issue strikes again?23:31
Laneyand everything else23:32
ximionreally weird...23:32
ximionappstream-glib hasn't changed, and that is the critical part when it comes to reading metadata properly23:32
Laneyit's some g-s change between 3.19.5+git20160212.a64f331-0ubuntu1 and 3.19.91~git20160224.0779986-0ubuntu123:32
Laneybecause reverting makes it come back23:33
ximiondoes the apt backend set the app state to AVAILABLE or INSTALLED?23:33
Laneyximion: not sure, if you want to look I think https://git.gnome.org/browse/gnome-software/tree/?h=wip/rancell/apt should be current23:37
* Laney has to go to bed now though, sorry!23:37
ximionthe message suggests that the app state is never set and remains on it's initial value23:38
* ximion should sleep too23:38

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!