[07:32] <_novgorod> hey everyone, looking for a bit of help with what i'm hoping to be a minor (crossing fingers*) audio issue in the latest lts.. anyone keen to offer aid?
[07:35] <willcooke> morning all
[07:35] <_novgorod> morning willcooke
[07:35] <_novgorod> willcooke, well, actually it's about half past midnight here but still, morning/evening.. whichever suits ya
[07:36] <willcooke> :))
[07:36] <willcooke> Hi _novgorod
[07:37] <_novgorod> willcooke, greetings to you
[07:40] <_novgorod> willcooke, you make the leap to 18.04 yet?
[07:41] <willcooke> _novgorod, oh yes!  Long ago
[07:43] <seb128> good morning desktopers
[07:43] <seb128> hey willcooke
[07:43] <_novgorod> willcooke, right on. i only just recently. i grew fond of my previous dual boot and didn't want to make the leap right away
[07:45] <willcooke> _novgorod, nothing wrong with being a bit cautious :)
[07:48] <duflu> _novgorod, what is the problem exactly?
[07:48] <_novgorod> not so much cautious as i was in love with the old set of partitions. the dual boot served me well. in the end, it was the lack of space on my drive.. needed more
[07:50] <_novgorod> duflu, not exactly sure, i know that i took an update recently and out of neglect failed to read it, it started at boot and i'm sure i just clicked away to get to something else. either way, my audio has been finicky at best
[07:50] <_novgorod> duflu, it's coming out rather muffled now, as opposed to crisp.
[07:51] <duflu> _novgorod, the first thing to check is that you're not using any audio extension cables. Poor quality connections can completely destroy the sound, even remove voice/instruments completely
[07:51] <duflu> (how that happens I don't know, but it does)
[07:51] <_novgorod> duflu, i don't cable
[07:52] <_novgorod> bluetooth from time to time, but never cable.
[07:52] <_novgorod> bluetooth audio is fine btw
[07:52] <_novgorod> no problems there.
[07:53] <duflu> _novgorod, want to reword that? If it's not cable and not bluetooth then what is it? :)
[07:53] <_novgorod> duflu, system audio.. on it's own without bluetooth is damaged.
[07:54] <duflu> _novgorod, sounds non-obvious. I would suggest making a bug so we can see the details. Just run "ubuntu-bug pulseaudio"
[07:56] <duflu> _novgorod, another idea: check your sound settings and ensure you have not allowed volume over 100%, because going over 100% will usually cause distortion
[07:57] <oSoMoN> good morning desktoppers
[07:57] <duflu> Morning oSoMoN
[07:58] <_novgorod> duflu, i don't exceed that i'm aware of, which part of the bug would be most helpful?
[07:59] <duflu> _novgorod, not sure yet. Just submit everything that gets attached automatically
[08:00] <oSoMoN> hey duflu
[08:02] <Laney> hey hey
[08:05] <duflu> Morning Laney
[08:09] <seb128> lut oSoMoN, en forme ?
[08:09] <seb128> hey Laney, how are you?
[08:09] <_novgorod> duflu, sent
[08:10]  * duflu waits for mail
[08:11] <oSoMoN> seb128, ça va, et toi?
[08:11] <oSoMoN> hey laney
[08:11] <seb128> ça va bien, il fait moins chaud !
[08:12] <oSoMoN> looks like it's raining for good now, we've had a few showers yesterday and last night but they never lasted more than 2 mins
[08:15] <Laney> hey duflu seb128 oSoMoN
[08:15]  * Laney is decent
[08:16] <Laney> looking cloudy today
[08:16]  * Laney hopes for rain
[08:18] <willcooke> Laney, how is the allotment holding up?  Anything still alive?
[08:18] <Laney> hey willcooke
[08:19] <Laney> we've put half of a reservoir on it over the past few weeks
[08:20] <Laney> thank goodness for hosepipes /o\
[08:20] <Laney> corn is getting nice and fat
[08:20] <Laney> winter squash are already making vines all over the place
[08:22] <_novgorod> duflu, just checked status, service not found :/
[08:30] <duflu> _novgorod, can you share the text output from 'ubuntu-bug pulseaudio' ?
[08:30] <willcooke> Laney, when Brexit comes and we're all starving, I'll come to you cap-in-hand for a bowl of soup then
[08:30] <willcooke> https://www.theguardian.com/politics/2018/aug/09/im-already-stockpiling-readers-preparing-for-a-messy-brexit
[08:30] <willcooke> !!
[08:31] <duflu> That title makes more sense with the ':
[08:32] <willcooke> :)
[08:32] <willcooke> With articles like that they need to stock pile readers
[08:32] <duflu> And this is the room where I keep my subscribers
[08:33] <_novgorod> duflu, i don't have screenshot setup
[08:33] <willcooke> duflu, lol
[08:33] <duflu> _novgorod, just paste a little bit of the error message and surrounding text here?
[08:35]  * duflu hates having to debug the bug reporting tool but this isn't the first time
[08:39] <_novgorod> duflu, wouldn't let me copy/paste/right click inside of bug window.. here is what i got
[08:39] <_novgorod> duflu, Error: comman ['pacmd'.list'] failed with exit code 1: Home directory not accessible: Permission denied. No PulseAudio daemon running, or not running as session daemon.
[08:39] <_novgorod> Error: command*
[08:39] <duflu> _novgorod, OK. Don't use 'sudo'. Just run the command as yourself
[08:40] <duflu> _novgorod, but if "No PulseAudio daemon running" then that's the first problem. You won't have sound at all (in most apps) if that's true
[08:41] <duflu> That's something I do have a solution for, but it isn't the muffled problem you originally mentioned
[08:43] <_novgorod> duflu, pulse list that gave error previously doesn't list error anymore, still no copy/paste function. it not reads off a list of a dozen indexes
[08:44] <duflu> _novgorod, when you run 'ubuntu-bug pulseaudio' you should eventually be shown a web link. You need to click on and follow that link to finish creating the bug report
[08:45] <_novgorod> duflu, currently i have the same muffled sound in vlc, spotify, and streaming media. i do not have sound adjusting volume.
[08:46] <duflu> _novgorod, OK. If the commands don't work for you then please just create a new bug on this web page: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug
[08:47] <duflu> Then when you have a bug open you will be able to paste more details about what you see in that
[08:50] <_novgorod> duflu, creating new bug now
[08:55] <_novgorod> duflu, i feel like this process used to be easier..
[09:01] <_novgorod> duflu, link sent
[09:03] <jamesh> and now there's hail
[09:25] <_novgorod> duflu, Thanks for your help with all this, much appreciated. i'll check back on the bug a bit later.
[09:26] <duflu> _novgorod, no problem. My day ends soon and it sounds like yours should have already
[09:26] <_novgorod> duflu, you're correct. i'm overdue by about 5 maybe 6 hrs on my end.
[09:27] <_novgorod> duflu, again, many thanks!
[09:30] <tseliot> Laney: hi, it looks like this merge got lost in your last upload of gdm in cosmic. Can you fix it, please? https://code.launchpad.net/~albertomilone/ubuntu/+source/gdm3/+git/gdm3/+merge/351810
[09:32] <Laney> ok, sorry about that
[09:34] <tseliot> np, I'm just trying to get LP: #1778011 fixed for good
[09:40] <seb128> oSoMoN, what version of libreoffice are we aiming at having in cosmic?
[09:56] <Laney> tseliot: there you go
[09:59] <tseliot> Laney: thanks. Did you update git too?
[09:59] <oSoMoN> seb128, 6.1.0
[09:59] <oSoMoN> thanks for filing that tracking bug, btw
[10:00] <seb128> oSoMoN, ok, I opened a bug about it so it's listed on version, might be worth a trello card also?
[10:00] <seb128> oSoMoN, yw!
[10:00] <oSoMoN> seb128, yep, trello card just created
[10:00] <seb128> thx
[10:00] <oSoMoN> https://trello.com/c/PPpAxvXb/197-libreoffice-61-in-cosmic
[10:10] <Laney> tseliot: yeah
[10:13] <duflu> seb128, if I am redesigning Ubuntu patches from scratch (rebasing) on a newer Debian package and have zero history from Ubuntu then should the changelog still show the Ubuntu history or is it fine to only have one Ubuntu entry above Debian?
[10:15] <seb128> I never bothered to keep old changelog entries but I know some people disagree wtih that
[10:16] <duflu> Yeah I have previously kept the Ubuntu changelog and just inserted the latest one from Debian, which is neither
[10:16] <seb128> in practice if a package get in sync and delta again we don't bother remerging old changelogs as well
[10:16] <seb128> which I think is not that different
[10:16] <duflu> seb128, yes it is a "sync" and I am rewriting Ubuntu patches from scratch. So just use the Debian history?
[10:17] <seb128> sounds fine to me yes
[10:17] <duflu> Previous update: 2017-08-09
[10:17] <duflu> Today: 2018-08-09
[10:17] <duflu> It's fate
[10:21] <seb128> hehe
[10:21] <seb128> what package is that?
[10:22] <duflu> seb128, mpv
[10:22] <willcooke> :)
[10:23] <seb128> back to video decoding work? ;)
[10:23] <tseliot> Laney: thanks! :)
[10:24] <duflu> seb128, yeah there are bugs we can soon close. And it's convenient that Debian has jumped to the latest now
[14:48] <seb128> Laney, can you help with gbp? I'm getting confused again :/
[14:49] <seb128> I did "gbp clone pkg-gnome:gnome-bluetooth", downloaded http://ftp.acc.umu.se/pub/gnome/sources/gnome-bluetooth/3.28/gnome-bluetooth-3.28.2.tar.xz and did a gbp import-orig if the tarball
[14:51] <seb128> it seems to have worked but upstream/latest is ahead of 1 commit compared to origin/upstream/latest and seems to be missing the upstream individual commits between .0 and .2
[14:51] <seb128> it feels wrong but I'm unsure what I missed or what didn't work
[14:55] <seb128> hum, maybe I need a -upstream-vcs-tag= since the tags are not standard
[15:03] <seb128> right, that was it
[15:03] <seb128> Laney, unping
[15:11] <Laney> nice
[15:12] <Laney> you can add "upstream-vcs-tag = invalid" or something to debian/gbp.conf, that makes it error instead of not taking the tag at all
[15:13] <seb128> sounds like maybe a good default for pkg-gnome components?
[15:13] <Laney> yeh I think a couple already have it
[15:13] <seb128> (or maybe "good default" at all, unsure how tagging is handled in other projects)
[15:13] <seb128> k, so I can just commit such changes?
[15:13] <Laney> yep
[15:13] <seb128> thx
[15:14] <Laney> might want to check I didn't make it up though
[15:14] <Laney> well I didn't make it up, but that specific line might not be exactly right
[15:15] <seb128> k, I'm going to look for other cases in pkg-gnome and copy what they did to be sure :)
[15:15] <Laney> # Upstream tags in this project are not conveniently named for this
[15:15] <Laney> upstream-vcs-tag = invalid
[15:16] <Laney> gnome-settings-daemon
[15:17] <seb128> thx
[15:17] <seb128> interesting one as well, https://salsa.debian.org/gnome-team/eog/commit/dcb4deb1
[15:17] <seb128> the
[15:17] <seb128> "[import-orig]
[15:17] <seb128> postimport = dch -v%(version)s New upstream release; git add debian/changelog; debcommit
[15:17] <seb128> "
[15:17] <seb128> bit
[15:17] <seb128> I wonder if that should be standard/default as well
[15:18] <Laney> I wouldn't mind it without the debcommit
[15:19]  * Laney likes to add NEWS entries in there
[15:19] <seb128> yeah, I don't think that one is needed
[15:19] <seb128> but dch/add would be nice
[15:19] <Laney> also patch-numbers = False I think would be a good one
[15:19] <seb128> should perhaps be a default in gbp though, I don't know why you wouldn't want to do that
[15:22] <seb128> tkamppeter, the new ghostscript is unhappy on ppc64el, the build seems to stuck on " ./soobj/aux/echogs -e .dev -a- ./soobj/xpswrite -include ./soobj/vector -include ./soobj/libtiff" and get killed after 2 hours, same after a retry now
[15:22] <seb128> that leads to cups/cups-filter/etc to fail to build also on that arch
[15:23] <seb128> which is going to make them block in cosmic-proposed until ghostscript is resolved
[17:08] <Laney> epic yak shaving session is over
[17:09]  * Laney enjoys being on the bleeding edge gnome train again
[17:09] <Laney> night!
[17:11] <seb128> night Laney!
[17:11] <seb128> & well done :)
[18:39] <willcooke> bye bye everyone
[18:39] <willcooke>  /drnick
[21:22] <robert_ancell> ximion, could you upload appstream-glib 0.7.11 to debian? Should be an easy update
[21:23] <robert_ancell> ximion, also should probably discuss if it makes sense to add the developer verified quirk into the AppStream spec
[21:34] <robert_ancell> kenvandine, oh I set up a build server on canonistack for my builds.
[21:34] <robert_ancell> I seem to be getting failures that don't happen on the GNOME builders - did you have to do anything special to set it up?
[21:35] <robert_ancell> Also, I have to add it for every project which is a pain, but I think not possible to work around unless you belong to a group you control.