[01:41] <Guest29017> Hey...
[06:10] <lordievader> Good morning
[10:59] <o_a> Hello, all. My cursor gets giant in newly opened applications after a while. Any idea why?
[10:59] <o_a> I'm using  a dual-monitor setup
[10:59] <hateball> o_a: so if you move the cursor out to another app, it shrinks?
[10:59] <o_a> Yup
[10:59] <hateball> :D
[11:00] <hateball> That's a weird one
[11:00] <hateball> o_a: Any difference between Qt or GTK apps?
[11:00] <o_a> Lemme see
[11:01] <o_a> Apparently not
[11:02] <o_a> hateball:  Newly opened applications get the big cursor no matter the toolkit
[11:04] <hateball> o_a: can you screenshot it?
[11:07] <o_a> Yup, just a sec
[11:10] <o_a> hateball: Normal cursor: https://i.imgur.com/pvFj3dN.png
[11:11] <o_a> Big cursor: https://i.imgur.com/xRb1ig0.png
[11:13] <hateball> super weird
[11:13] <hateball> afraid I don't have any good ideas
[11:37] <BluesKaj> Hey folks
 @o_a, o_a it could be something related to the DPI settings, I have a similar problem when connectong my 4K tv
 *Connecting
[14:32] <o_a> IrcsomeBot: I'm connecting a 1080p monitor
[14:32] <o_a> It could have more to do with resolution than with dpi
[15:08] <jonathan_x> If the installer (of 16.04) exits at installing Grub because grub fails to be installed, was that the last stage or does there come more after it?
[15:08] <jonathan_x> Cause it was only at 66%.
[15:09] <jonathan_x> But I've had to reinstall so many times already, I want to keep this install.
[15:10] <jonathan_x> I mean retry the installer.
[15:12] <jonathan_x> Anyone?
[15:12] <jonathan_x> What am I missing if it exits at grub?
[15:12] <BluesKaj> jonathan_x,grub is usually the last app to be installed , but if it detects another OS with grub already installed it will skip grub install.
[15:12] <jonathan_x> Okay
[15:12] <jonathan_x> So I should be fine, if I install it myself.
[15:13] <jonathan_x> I just wanted to install it on a sdcard that wasn't connected yet but I didn't want to go back in the installer so I just put it to some LV but then it failed.
[15:13] <BluesKaj> from another OS ?
[15:14] <jonathan_x> No I just wanted to boot from external card.
[15:14] <jonathan_x> But the installer doesn't allow skipping grub.
[15:14] <BluesKaj> \is this an rpi or similar?
[15:15] <jonathan_x> I don't know if it tries to configure stuff after grub, I think usually it does some of that.
[15:15] <jonathan_x> No just dual booting but I don't want it on the main disk.
[15:15] <jonathan_x> I want to press F8 in BIOS ;-).
[15:15] <BluesKaj> why not?
[15:15] <jonathan_x> Just because.
[15:15] <jonathan_x> So no configuration after Grub?
[15:15] <BluesKaj> usually not
[15:16] <jonathan_x> Okay thanks.
[15:16]  * BluesKaj shrugs ...just because ?
[15:17] <BluesKaj> that's no reason
 Good day everyone!
[16:01] <jonathan_x> I like to forget to mount /boot in chroot and then watch Grub not have a clue what is going on :D.
[16:01] <jonathan_x> Or yeah... :p.
[16:03] <jonathan_x> Only took me 15 minutes to find out what "Cannot find device lvmid/asdFADFASDFasDFAsdf/ASDFASDFASDFAsasdf meant.
[16:04] <jonathan_x> But I guess it is done now, reminded me to install thin-provisioning-tools for cache_repair and put it in initramfs lol.
[16:11] <jonathan_x> Oh my god updateinitramfs doing weird stuff lsinitramfs --> var/tmp/mkinitramfs_QVAigx/sbin/cache_check
 any suggestion about a good .csv editor ?
 (no libreoffice)
[16:46] <mparillo> Perl? http://www.perlmonks.org/?node_id=1126133
[17:08] <user|85739> hallo! i am upgrading from a previus version and i do not seem to see any plasma panels :(
[17:08] <user|85739> any ideas on what to do ?
[18:48] <xperia> multiple views on konverstion?
[19:18] <marshwallow> Did anyone here had problems running KDE alongside Cinnamon?
[19:18] <marshwallow> Er, or knows how to handle funky errors that might come up in that process?
[19:19] <marshwallow> I'm having black boxes all over the place.
[19:19] <marshwallow> Icons, panel, desktop wallpaper.
[19:19] <marshwallow> Ubuntu 17.04, amd64.
[20:17] <jonathan_x> So it took me about 8 hours to install Kubuntu.
[20:18] <jonathan_x> Because I was doing a FakeRaid install and Ubiquity deletes files when Grub cannot be installed.
[20:18] <jonathan_x> So the files for dmraid and libdmraid were actually missing...
[20:19] <jonathan_x> Add to that that the initramfs script for dmraid doesn't actually activate the entire array.
[20:20] <jonathan_x> And I should have just looked online but I thought it would be easy :p.
[20:30] <jonathan_x> I want to add some to the Ubuntu wiki but I don't know where it starts.
[20:35] <genii> jonathan_x: Next time just use the server install disc to create and install to RAID, then after forst boot install kubuntu-desktop
[20:36] <genii> You'll cut 7 hours off your install time
[20:37] <Unit193> kubuntu-desktop^  rather. :3
[20:37] <genii> Unit193: Hah, yes
[21:22] <R13ose> Part of my screen is white and I can't see behind this, how do I fix this?
[21:35] <user|45504> hello all


[10:48] <Tm_T> Good day to all
[18:58] <guntbert> is the new process for becoming op already active? if yes - where can I see applications?
[19:05] <jussi01> guntbert: not really, its a week or so away yet.
[19:05] <guntbert> ok- please ignore my cross posted question in -ops then
[19:06] <jussi01> :)
[19:08] <Tm_T> (:
[19:20] <guntbert> btw - I'm definitely *not* gonna apply - in case my question sounds as if ...
[19:27] <bikcmp> Hello, I'd like a ubuntu cloak
[19:27] <bikcmp> And I need approval for it, who can approve it?
[19:27] <Pici> bikcmp: What is your launchpad id?
[19:27] <bikcmp> Pici: Launchpad?
[19:27]  * bikcmp reads up
[19:28] <Pici> bikcmp: You need to be an approved Ubuntu Member to qualify for an Ubuntu cloak.
[19:28] <Pici> !membership | bikcmp
[19:28] <bikcmp> ah, I've been using ubuntu on my netbook, I'll reister now
[19:29] <Pici> bikcmp: There is an approval process,  you would need to show that you have made sustained contributions to Ubuntu.
[19:29] <Pici> AS that link explains.
[19:30] <bikcmp> :/
[19:30] <bikcmp> I just use ubuntu on my netbook and wanted to display it :P
[19:31] <Pici> Sorry, we don't offer user cloaks at this time.
[22:01]  * _marx_ has 2?
[22:01] <_marx_> how do i remove auto ops from a channel
[22:02] <_marx_> how do i mute a bot
[22:02] <_marx_> channel in ? is -us-nc
[22:03]  * _marx_ finds rtfm and wtfm replies pleasing
[22:07] <m4v> check http://freenode.net/using_the_network.shtml
[22:25] <_marx_> m4v: i've seen that it doesn't tell me how to change it once a channel is setup
[22:54] <m4v> _marx_: check /msg chanserv help
[22:54] <m4v> you probably want to look at /msg chanserv help flags


 @Jorge Sánchez, https://www.falkon.org/download/
[05:44] <patrick__> hi
[07:24] <lordievader> Good morning
[09:31] <ocean416> Hi, i just tried a linux game. After closing it, i have no border in all other windows anymore. I can't resize window, can't nbring one on top
[09:37] <ocean416> Is there a shortcut to fix that
[10:08] <BluesKaj> Howdy folks
[10:22] <Kon-> ocean416: Go to terminal and try "kwin --replace"
[10:23] <Kon-> You can even run this command in krunner
[10:28] <ocean416> Thank you, that worked!
[10:30] <ocean416> It was not easy to get the keyboard focus to the terminal window. butbe everything isbfune now.
[10:32] <Kon-> ocean416: If you can't get to the terminal easily, try Alt+Space or Alt+F2 to bring down Krunner. It can run programs, switch windows, or run some commands itself
[10:33] <Kon-> Just type what you want in the box
[12:38] <pragmaticenigma> Howdy everyone, Does anyone know a permenent solution to disabling Baloo? I have used it's own configuration tools to attempt to disable it, yet I still continue to see it working in the background in my logs. I need this completely turned off, how can I do that without nuking KDE?
[12:51] <BluesKaj> pragmaticenigma, system-settings>workspace>search>filesearch, uncheck filesearch, then in Plasma search , uncheck desktop search
[12:52] <pragmaticenigma> Those are all disabled... I need baloo actually removed
[12:52] <pragmaticenigma> it is the reason that mounting and unmounting drives is causing udisk to hang
[12:53] <pragmaticenigma> balooctl status report inactive... I should not see org.kde.runners.baloo[1204]: QSocketNotifier: Can only be used with threads started with QThread or any other message from baloo in my logs
[12:57] <BluesKaj> pragmaticenigma, I have balookf5 installed, but it's not running anywhere, perhaps also thru system-settings> startup&shutdowwn?background services> uncheck and stop 'search folder updater'
[12:57] <pragmaticenigma> BluesKaj: all of the options for file search are disabled where they can be
[12:58] <BluesKaj> do you have akonadi server running too?
[12:58] <pragmaticenigma> no
[13:00] <pragmaticenigma> what also bothers me is that I cannot disable or change the ondemand "Directory Watcher" service
[13:00] <BluesKaj> then I don't know why baloo is running, since i have done all of the above settings and there's no baloo in ksysguard process
[13:02] <pragmaticenigma> I don't have a process... it is appearing in my logs...
[13:05] <BluesKaj> which log?i don't see anything in /var/log/syslog
[13:06] <pragmaticenigma> journalctl is where I'm finding it
[13:59] <BluesKaj> pragmaticenigma, https://bbs.archlinux.org/viewtopic.php?id=193169, these commands should work
[20:43] <daniel> Hey
[20:43] <Swahilian> Hey
[20:43] <Swahilian> How do I use the kde partition manager?
[20:44] <Swahilian> I need to partition my HDD but my linux knowing friend has autism and can't use his words to tell me because he's mad that I want to change from kubuntu to ubuntu
[20:44] <Swahilian> how do I convince him to help me or how do I partition my hdd?
[21:05] <zanna> buonasera.
[22:10] <mparillo> buona sere, ma
[22:10] <mparillo> !it


[05:23] <aRustyDev> Anyone have an idea why when I try to autoinstall with cloud-init it downloads the user-data file, but its always empty?
[20:35] <fly> howdy, y'all. I am wondering, how much of a dreadful mistake would be to diy parsing cloud-init data, or should I bite the bullet and use the python thingie?
[20:37] <minimal> fly: python thingie? you mean cloud-init?
[20:38] <fly> Yes
[20:39] <fly> I know it's a weird question but I'm coming up with ideas on how to add python to our images that are all very contorted
[20:39] <minimal> what do you mean by "parsing cloud-init data"?
[20:39] <minimal> you mean to use for boot-time configuration?
[20:39] <fly> yeah, I wonder how big is the spec to parse it myself
[20:40] <minimal> there's more to cloud-init that just parsing YAML data
[20:40] <minimal> s/that/than/
[20:40] <minimal> there are alternative to cloud-init written in various languages but none of them has the full feature set/functionality of cloud-init
[20:48] <minimal> fly?
[20:48] <fly> hello
[20:49] <minimal> you didn't comment on my previous msgs
[20:49] <minimal> so you are looking to write yet another cloud-init alternative?
[20:49] <fly> I was looking for reasons not to write one
[20:50] <fly> I am also wondering how well python cloud-init would work on my niche system that is supposedly supported
[20:50] <minimal> as I said there are multiple alternatives, each with limitations
[20:50] <minimal> niche? custom OS?
[20:50] <fly> yeah it's netbsd
[20:50] <minimal> NetBSD is support by cloud-init AFAIK
[20:51] <minimal> along with FreeBSD and (I think) DragonBSD
[20:55] <fly> my grand idea is to maybe have netbsd itself ship images that do cloud-init by default, but it's not super straightforward to make it a solution people would be happy with, lots of technical debt, I'm trying to consider other options :-)
[20:56] <fly> and I'm a bit of a perfectionist
[20:56] <fly> and wondering how well it'd all work in the end as I'm not sure anyone has been using cloud-init on netbsd
[20:57] <minimal> NetBSD is listed as supported: https://cloudinit.readthedocs.io/en/latest/topics/availability.html
[20:58] <minimal> so obviously as NetBSD stuff has been added to cloud-init in the past that implies there are people who use/have used it
[20:58] <fly> mhm
[20:59] <minimal> as for NetBSD images with cloud-init build in, I am the Alpine Linux package maintainer for cloud-init and I have written a shell script to generate disk images with cloud-init enabled
[20:59] <fly> I guess the one thing I encoutnered with cloud-init was already resolved
[21:00] <minimal> so I'm aware of what's involved to get c-i integrated with an OS


[14:29] <cpaelzer> slowly lighting the MIR campfire
[14:29] <eslerm> o/
[14:30] <cpaelzer> double booked, I hope attention is enough to do this well ...
[14:30] <cpaelzer> shout if I fail :-)
[14:30] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[14:30] <meetingology> Meeting started at 14:30:38 UTC.  The chair is cpaelzer.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[14:30] <meetingology> Available commands: action, commands, idea, info, link, nick
[14:30] <cpaelzer> Ping for MIR meeting - didrocks joalif slyon sarnold cpaelzer jamespage ( eslerm dviererbe )
[14:30] <cpaelzer> #topic current component mismatches
[14:30] <cpaelzer> Mission: Identify required actions and spread the load among the teams
[14:30] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[14:30] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[14:31] <cpaelzer> the old jaraco that we know for openstack
[14:31] <slyon> o/
[14:31] <cpaelzer> not more yet for https://launchpad.net/ubuntu/noble
[14:31] <sarnold> good morning
[14:31] <cpaelzer> #topic New MIRs
[14:31] <cpaelzer> Mission: ensure to assign all incoming reviews for fast processing
[14:31] <didrocks> o/ (I’m exceptionnally here this week)
[14:31] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir
[14:31] <cpaelzer> happy, I hope that means no sick-at-home being the reason didrocks
[14:32] <cpaelzer> we have a bunch (much less than expected due to massaging dependencies and function) perl items that need review
[14:32] <cpaelzer> 5 of them are waiting for a reviewer
[14:32] <cpaelzer> I need TBH that I can not take any before the sprint
[14:33] <cpaelzer> is any of you having enough capacity to take one for this or next week?
[14:33] <didrocks> I can take a second one (I couldn’t due to the sprint and final rush do the one I had previous one) and do it before EOW
[14:33] <slyon> I can take one
[14:33] <didrocks> next week, I don’t want to commit with the sprint
[14:33] <slyon> There's a list of priorities for those MIRs in https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/comments/11
[14:33] -ubottu:#ubuntu-meeting- Launchpad bug 2023971 in libmail-dmarc-perl (Ubuntu) "[MIR] libmail-dmarc-perl" [Undecided, Incomplete]
[14:34] <cpaelzer> of those https://bugs.launchpad.net/ubuntu/+source/libregexp-common-perl/+bug/2039563 and https://bugs.launchpad.net/ubuntu/+source/libnet-ip-perl/+bug/2039456 are already assigned
[14:34] -ubottu:#ubuntu-meeting- Launchpad bug 2039563 in libregexp-common-perl (Ubuntu) "[MIR] libregexp-common-perl (as a libmail-dmarc-perl dependency)" [Undecided, New]
[14:34] -ubottu:#ubuntu-meeting- Launchpad bug 2039456 in libnet-ip-perl (Ubuntu) "[MIR] libnet-ip-perl (as libmail-dmarc-perl dependency)" [Undecided, New]
[14:35] <cpaelzer> https://bugs.launchpad.net/ubuntu/+source/libnet-idn-encode-perl/+bug/2038929 has been reviewed and back on miriam until action has been taken
[14:35] -ubottu:#ubuntu-meeting- Launchpad bug 2038929 in libnet-idn-encode-perl (Ubuntu) "[MIR] libnet-idn-encode-perl (as libmail-dmarc-perl dependency)" [Undecided, Incomplete]
[14:35] <cpaelzer> let us distribute a few more as we have capacity
[14:35] <cpaelzer> slyon: didrocks: could you just pick one each from https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir ?
[14:35] <slyon> So let me take libfile-sharedir-perl ?
[14:35] <cpaelzer> sure
[14:36]  * slyon assigned himself
[14:36] <didrocks> I will take libemail-abstract-perl
[14:36] <slyon> didrocks: that's one of the lower priority ones..
[14:36] <didrocks> abstract and perl in the same package name, what could go wrong? :)
[14:36] <didrocks> ah
[14:36] <cpaelzer> in terms of prio according to the post would be better https://bugs.launchpad.net/ubuntu/+source/libclass-inspector-perl/+bug/2039569
[14:36] <didrocks> I got the list the other way around
[14:36] -ubottu:#ubuntu-meeting- Launchpad bug 2039569 in libclass-inspector-perl (Ubuntu) "[MIR] libclass-inspector-perl (libfile-sharedir-perl dependency as libmail-dmarc-perl dependency)" [Undecided, New]
[14:36] <didrocks> good to me, picking that one
[14:36] <cpaelzer> ok, we'll slowly churn through all of those
[14:36] <didrocks> if I can stay away from any abstraction, that’s a bonus (somewhat :p)
[14:36] <cpaelzer> and let us just be happy it seems there won't be ~50 of them
[14:37] <didrocks> until debian sync starts, we’ll see…
[14:37] <cpaelzer> ok, going on ...
[14:37] <cpaelzer> #topic Incomplete bugs / questions
[14:37] <cpaelzer> Mission: Identify required actions and spread the load among the teams
[14:38] <cpaelzer> #link https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.subscriber=ubuntu-mir
[14:40] <slyon> I think there's nothing actionable here
[14:40] <slyon> the libnet-idn-encode-perl MIR might be dropped by changing to another dependency, which is already in main
[14:40] <cpaelzer> agreed
[14:40] <didrocks> agreed
[14:40] <cpaelzer> leaving the check of that to miriam
[14:40] <cpaelzer> #topic Process/Documentation improvements
[14:41] <cpaelzer> Mission: Review pending process/documentation pull-requests or issues
[14:41] <cpaelzer> #link https://github.com/canonical/ubuntu-mir/pulls
[14:41] <cpaelzer> #link https://github.com/canonical/ubuntu-mir/issues
[14:41] <cpaelzer> the renovate auto branch is handled
[14:41] <cpaelzer> we can close #38
[14:41] <slyon> +1
[14:42] <cpaelzer> all the others are long term cases waiting for the right time
[14:42] <cpaelzer> nothing to act
[14:42] <cpaelzer> #topic MIR related Security Review Queue
[14:42] <cpaelzer> Mission: Check on progress, do deadlines seem doable?
[14:42] <cpaelzer> Some clients can only work with one, some with the other escaping - the URLs point to the same place.
[14:42] <cpaelzer> #link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=%5BMIR%5D&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir
[14:42] <cpaelzer> #link https://bugs.launchpad.net/~ubuntu-security/+bugs?field.searchtext=[MIR]&assignee_option=choose&field.assignee=ubuntu-security&field.bug_reporter=&field.bug_commenter=&field.subscriber=ubuntu-mir
[14:42] <cpaelzer> Internal link
[14:42] <cpaelzer> - ensure your teams items are prioritized among each other as you'd expect
[14:42] <cpaelzer> - ensure community requests do not get stomped by teams calling for favors too much
[14:42] <cpaelzer> #link https://warthogs.atlassian.net/jira/software/c/projects/SEC/boards/594
[14:43] <cpaelzer> slyon: seeing https://bugs.launchpad.net/ubuntu/+source/libemail-simple-perl/+bug/2031491 in there
[14:43] -ubottu:#ubuntu-meeting- Launchpad bug 2031491 in libemail-simple-perl (Ubuntu) "[MIR] libemail-simple-perl ( libemail-mime-perl dependency as libmail-dmarc-perl dependency)" [Undecided, Incomplete]
[14:43] <eslerm> not much news, we've been discussing perl fuzzing and Andrei is writing documentation tips
[14:43] <cpaelzer> slyon: was my explanation of not being a dup enough that we mark it new?
[14:44] <eslerm> this work will begin after the sprint, we'll likely have several dedicated people involved
[14:44] <eslerm> a deadline by NN has been agreed to with Miriam
[14:45] <cpaelzer> ok, thanks eslerm
[14:45]  * slyon reading context on libemail-simple-perl
[14:46] <slyon> Okay. I requested a differentiation of the two stacks. You came to the conclusion that they should be considered non-duplicates.
[14:46] <cpaelzer> yes
[14:46] <slyon> So having that in the security queue seems correct. right?
[14:46] <cpaelzer> it is like mutt and thunderbird :-) but for perl
[14:47] <slyon> ACK. wfm
[14:47] <cpaelzer> thanks, I updated the case
[14:47] <slyon> But I guess we still need security ACK for the other/new stack
[14:47] <cpaelzer> #topic Any other business?
[14:47] <sarnold> ha :)
[14:47] <cpaelzer> yes we still need security, it is only back to "new" not to and "final and done" state
[14:48] <sarnold> my apologies for not getting the scheduling survey done :( it's been busy that it's always fallen out of my mental todo list
[14:48] <didrocks> you are not the only one :)
[14:48] <cpaelzer> exactly
[14:48] <eslerm> it would be nice to meet up during the sprint
[14:48] <didrocks> but yeah, would be great to settle that for post-sprint
[14:48] <sarnold> and i'll send my apologies for next week
[14:48] <cpaelzer> ha eslerm, that was just what I wanted to ask
[14:48] <eslerm> :)
[14:48] <cpaelzer> should I schedule something in Riga engineering week?
[14:49] <cpaelzer> give me an agenda item or two worth to see you over more than just a beer at a bar :-)
[14:49] <sarnold> I'd very much like us all to get together and have it be scheduled so that we don't wind up with yet another sprint with only half of us getting together
[14:49] <slyon> Yes, please. Maybe we can just use the usual MIR meeting slot, as we've done in the past?
[14:49] <didrocks> I think it’s been quite some time we haven’t done that, it would be great, but quick, the calendars are filing up quite fast :p
[14:49] <didrocks> as long as it’s booked to not be double booked, I’m fine
[14:50] <sarnold> yes :( so much double and triple-booking :(
[14:50] <cpaelzer> yes
[14:50] <cpaelzer> let me have a look right now ...
[14:50] <didrocks> but the MIR meeting slot is already booked for me in my case :/
[14:51] <cpaelzer> them original slot is gone for me too
[14:52] <cpaelzer> friday after lunch or before lightning talks is available to all of us
[14:53] <eslerm> after lunch sounds nice, in case people wanted to meet for lunch as well
[14:53] <cpaelzer> yep
[14:53] <didrocks> sounds good to me :)
[14:53] <slyon> wfm
[14:54] <cpaelzer> sent
[14:54] <cpaelzer> thanks
[14:54] <cpaelzer> anything else?
[14:54] <sarnold> thanks! \o/
[14:54] <sarnold> nothing else from me
[14:55] <cpaelzer> neither from me
[14:55] <didrocks> thanks!
[14:55] <slyon> nothing
[14:55] <cpaelzer> ok
[14:55] <slyon> thanks cpaelzer, all!
[14:55] <cpaelzer> next week some of us will be at the planning sprint already
[14:55] <cpaelzer> might be rather silent here
[14:55] <cpaelzer> whoever is left can lead the lonely meeting then
[14:55] <cpaelzer> bye
[14:55] <cpaelzer> #endmeeting
[14:55] <meetingology> Meeting ended at 14:55:31 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-10-24-14.30.moin.txt
[14:55] <eslerm> thanks all o/
[14:55] <sarnold> thanks cpaelzer, all :)
[18:59]  * vorlon waves
[18:59] <rbasak> o/
[19:00] <amurray> o/
[19:01] <seb128> hey
[19:02] <amurray> hey seb128
[19:02] <amurray> looks like sil2100 is not around - I'll kick things off then
[19:02] <vorlon> sil2100 was under the weather today
[19:03] <amurray> #startmeeting Ubuntu Technical Board
[19:03] <meetingology> Meeting started at 19:03:03 UTC.  The chair is amurray.  Information about MeetBot at https://wiki.ubuntu.com/meetingology
[19:03] <meetingology> Available commands: action, commands, idea, info, link, nick
[19:03] <amurray> #topic Apologies
[19:03] <amurray> sil2100 is out
[19:03] <amurray> #topic Action review
[19:04] <amurray> ACTION: seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage
[19:05] <seb128> to carry over I guess?
[19:05] <amurray> yeah - I don't have any update on this myself either
[19:06] <amurray> #action seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage
[19:06] <meetingology> ACTION: seb128/amurray/sil200 to help drafting the snap-store Ubuntu-specific tracks usage
[19:06] <amurray> ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:06] <rbasak> Carry over please
[19:06] <amurray> #action rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:06] <meetingology> ACTION: rbasak to draft a proposal of the DMB-proposed inactivity expiration policy for TB ratification
[19:06] <amurray> ACTION: rbasak to follow up on finding consensus on question of test plans for third party apps
[19:07] <rbasak> Carry over please
[19:07] <amurray> #action rbasak to follow up on finding consensus on question of test plans for third party apps
[19:07] <meetingology> ACTION: rbasak to follow up on finding consensus on question of test plans for third party apps
[19:07] <amurray> ACTION: rbasak to open wider discussion on third-party repo policy
[19:08] <rbasak> Carry over please
[19:08] <amurray> #action rbasak to open wider discussion on third-party repo policy
[19:08] <meetingology> ACTION: rbasak to open wider discussion on third-party repo policy
[19:09] <amurray> ACTION: seb128 to continue working with SRU, AA, Release, Backporters and Security teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations
[19:09] <seb128> to carry over, there were no news since the last meeting
[19:09] <amurray> #action seb128 to continue working with SRU, AA, Release, Backporters and Security teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations
[19:09] <meetingology> ACTION: seb128 to continue working with SRU, AA, Release, Backporters and Security teams to document their membership process and link to it from https://wiki.ubuntu.com/TechnicalBoard#Team_Delegations
[19:10] <amurray> ACTION: vorlon to write up draft guidelines for packages in the archive that download from the Internet
[19:10] <vorlon> carry over please
[19:10] <amurray> #action vorlon to write up draft guidelines for packages in the archive that download from the Internet
[19:10] <meetingology> ACTION: vorlon to write up draft guidelines for packages in the archive that download from the Internet
[19:10] <amurray> #topic Scan the mailing list archive for anything we missed (standing item)
[19:11] <amurray> ubuntu-advantage-tools SRU exception policy review
[19:11] <amurray> #link https://lists.ubuntu.com/archives/technical-board/2023-October/002767.html
[19:11] <rbasak> I think that one is done from the TB perspective.
[19:11] <rbasak> There's an ongoing discussion with the release team.
[19:11] <amurray> oh sorry yes I see now
[19:11] <amurray> nothing else on the mailing list then that I can see
[19:12] <amurray> #topic Check up on community bugs and techboard bugs
[19:12] <amurray> #link https://bugs.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard
[19:12] <amurray> #link https://bugs.launchpad.net/techboard
[19:12] <amurray> nothing new here either that I can see
[19:13] <amurray> although I do wonder about the "Inactive DMB members can stall DMB progress" bug
[19:13] <amurray> #link https://bugs.launchpad.net/techboard/+bug/2015921
[19:13] -ubottu:#ubuntu-meeting- Launchpad bug 2015921 in techboard "Inactive DMB members can stall DMB progress" [Undecided, Triaged]
[19:13] <amurray> is this still seen as an issue from the DMB side?
[19:13] <rbasak> That's related to my action item above
[19:14] <rbasak> It's not currently an issue, so that's why I haven't prioritised it.
[19:14] <rbasak> But I should sort it out so it's done before it becomes an issue again.
[19:14] <amurray> ah cool - fair enough - thanks rbasak
[19:14] <amurray> #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
[19:15] <amurray> looks like it's me :)
[19:15] <amurray> #agreed next meeting chair: amurray, backup: rbasak
[19:15] <meetingology> AGREED: next meeting chair: amurray, backup: rbasak
[19:15] <amurray> #topic AOB
[19:16] <vorlon> last meeting we had also deferred, due to low attendance, seb128's discussion topic from the mailing list
[19:16] <vorlon> wrt freeze exception request reviews
[19:17] <amurray> #link https://lists.ubuntu.com/archives/technical-board/2023-September/002763.html
[19:18] <amurray> is that the one?
[19:18] <vorlon> yes
[19:18] <seb128> right, but to be honest I'm unsure how to move that forward at this point
[19:18] <vorlon> well there are two responses I want to make
[19:18] <rbasak> With my TB hat on, I think that the release team should have the opportunity to address seb128's concerns in the first instance, before the TB go any further.
[19:18] <seb128> I still feel like things aren't working and I see no sign of the release team having an hand on the issue
[19:19] <seb128> but at the same time I feel like other board members don't agree with that view so perhaps it's only me
[19:19] <vorlon> first is to say that after this mail, we took stock within the release team and identified that the FFe request queue was a gap in our internal processes; so we set up a (light-touch) vanguard rotation to ensure they were being processed
[19:20] <seb128> ah, that's good to read (a public reply to say so would also have been nice)
[19:21] <vorlon> and second, seeing this message rankled not only because it jumped over attempting to first resolve the question with the release team (pings on #ubuntu-release are not how you have a discussion about such topics, we have an ubuntu-release@ mailing list for this which was never attempted before escalating to the TB) but also because there are clearly mismatched expectations of what the FFe process
[19:21] <vorlon> is for
[19:23] <vorlon> the FFe process exists in part to ensure the Release Team has a healthy overview of the remaining in-flight development work for the cycle, so we can help the engineering teams make sound priority trade-offs where necessary in order to not jeopardize the release schedule or the quality of the product
[19:24] <vorlon> if anyone has an *urgent* FFe request, I quite frankly think that represents a failure of planning, because the teams should have known, before it was urgent, what work covered by freeze exceptions they were still planning on landing
[19:24] <vorlon> and file the bugs at that point for discussion and review
[19:25] <vorlon> so if we want to have a longer discussion of what the SLA should be for release team reviews of FFe requests, let's have that discussion on the ubuntu-release mailing list please, and not inject the TB into it
[19:26] <seb128> that's orthogonal to the issue imho
[19:26] <seb128> or you are arguing that the release team being understaffed and onboarding one new member by year is a feature and not a bug?
[19:26] <seb128> the bug in question was late and not important
[19:26] <vorlon> the issue you escalated in that email was that you didn't think the Release Team was doing an adequate job of responding to FFe requests, which is what I am addressing with my comments
[19:27] <seb128> the problem isn't the urgency, is the difficulty to get a reply or to find an active member to engage with
[19:28] <seb128> vorlon, at the time of that email you were basically the only release team member actively doing review, when you were not around things were not moving
[19:28] <seb128> I'm glad you are active but relying on so few people isn't sane imho, which is the issue I'm trying to resolve
[19:30] <vorlon> I have previously made my position clear on why the understaffing of the release team, which is an undisputed problem, is not something to be solved quickly
[19:30] <vorlon> and I have nothing further to say on that
[19:31] <vorlon> also while I may have been the only release team member you noticed doing reviews on your bugs, it's not true that I was the only one doing reviews; but we still had a process gap wrt making sure the queue was being worked
[19:33] <amurray> ok, so from what I can see, whilst I acknowledge there is a perceived issue with understaffing on the release team, they have enacted a process to help with the FFe reviews going forward (being the most visible symptom)
[19:34] <amurray> so I don't feel the TB needs to step in at this stage personally
[19:34] <seb128> let's dismiss it then, at least I've tried
[19:35] <rbasak> I think it's appropriate to leave an initial discussion on this between seb128 and the release team. But wearing no hats and acting only as an observer, I'd like to make an observation.
[19:35] <rbasak> It doesn't necessarily follow that a perception that there isn't a sufficient response from the existing release team means that more release team members are required.
[19:35] <rbasak> There may be other issues, such as process.
[19:35] <rbasak> Further, adding more members means inconsistency in decisions, unless you also tackle that. As we've seen in the SRU team.
[19:35] <rbasak> I suggest that you focus on what you perceive to be the issue in the release team's performance, and leave it to the release team to decide how they want to handle that.
[19:35] <rbasak> If after discussion with them (I'd expect a thread on the mailing list) there is an impasse, only then would a TB escalation be appropriate. Such an escalation should focus on what it is that the release team is in your view failing to deliver, rather than presuming the solution is to add release team members.
[19:37] <seb128> well, I think I will just give up at this point but thanks
[19:38] <seb128> I do think it would be better to have a release team with time and capacity to be actively engaged and responsive
[19:38] <seb128> but Steve pointed out that it's not in the release team mission currently, so that would mean having a project discussion of what the release team should be
[19:39] <rbasak> actively engaged and responsive> In responding to FFe requests, or more broadly?
[19:39] <rbasak> AIUI, Steve only talked about FFes.
[19:39] <seb128> FFe is one time of the cycle where it's more visible but not only
[19:39] <rbasak> And acknowledged a gap that has now been addressed.
[19:40] <rbasak> OK, but FFe response time is the only objective complaint that I've seen, unless I'm missing something?
[19:41] <seb128> my initial emails have example of uploads stuck in the unapproved queue for several days around milestones
[19:41] <seb128> which community contributor and flavor leads also found problematic
[19:41] <rbasak> To be clear, I'm not trying to disagree with your perception seb128. I am just unable to respond to it because we can only realistically address specifics when they are pointed out.
[19:42] <seb128> I could go do a poll in the coredev/motu set about how they feel about their interactions with the release team, especially on engagements and delay
[19:43] <seb128> just to see if that's seen as a real problem by the other project members
[19:43] <rbasak> I don't see how that would be constructive. The release team need objective feedback, not subjective feelings.
[19:43] <seb128> but I'm unsure it would help eithe
[19:43] <seb128> how would you get objective feedback?
[19:44] <seb128> I've collected a number of specific examples and situations in my original email
[19:44] <seb128> from coredev, flavors, etc
[19:44] <rbasak> I suggest you start by starting a thread on ubuntu-release@ when you have an issue that you think isn't get the response you expect from the release team.
[19:44] <rbasak> That gives the release team an opportunity to respond and fix the issue.
[19:45] <seb128> my issue there is that the release team agree they are understaffed
[19:45] <seb128> ok, they can't onboard more than 1 new member by cycle max
[19:45] <seb128> but check https://launchpad.net/~ubuntu-release/+members#active
[19:45] <rbasak> If after a few of those you're still unhappy, then you could point to those threads as concrete examples of how you think the release team is failing to meet your expectations.
[19:46] <seb128> thanks, I will think about it
[19:46] <seb128> I just feel like I'm not able to get anywhere, because it's easy to just dismiss concerns
[19:46] <rbasak> I'm not willing to go into a discussion about understaffing or onboarding rates here, since that doesn't directly relate to performance, and your complaint seems to be about performance. As I said above, it's up to them how they want to address any performance concerns, but first they have to be concretely raised with them.
[19:47] <seb128> my worry is that the situation is just going to drive away the remaining contributors we have
[19:47] <seb128> and no metrics is going to tell us that until we have no community left
[19:47] <rbasak> That's a valid concern, but I really think that the only way to make progress is to turn those into concrete examples eg. via the ML as above.
[19:48] <seb128> ok, well let's wrap the discussion on that note
[19:49] <amurray> fair enough - thanks for the candour folks - any other items anyone wants to raise?
[19:49] <rbasak> OK, thanks. My final note: it's certainly not my intention to dismiss your concerns. Unfortunately I don't think they are actionable right now, and I'm trying really hard to turn this into something actionable.
[19:51] <seb128> rbasak, thanks, I just feel like it's an uphill battle and I'm unsure I've the energy to go forward with it atm but let's see
[19:51] <seb128> amurray, not from me
[19:53] <amurray> #endmeeting
[19:53] <meetingology> Meeting ended at 19:53:09 UTC.  Minutes at https://ubottu.com/meetingology/logs/ubuntu-meeting/2023/ubuntu-meeting.2023-10-24-19.03.moin.txt
[19:53] <rbasak> Thanks all!
[19:53] <seb128> thanks!
[19:53] <vorlon> amurray, rbasak, seb128: thanks!
[19:53] <amurray> indeed - thanks everyone


[00:00] <maco> im hoping that people will read that before filing bugs and do it right
[00:00] <xteejx> bug 159982, affects current Kubuntu releases, can someone take a look please?
[00:00] <ubot4> Launchpad bug 159982 in kdepim "KMail using mixed locale template in replies" [Undecided,New] https://launchpad.net/bugs/159982
[00:02] <dtchen> jerone-mobile: do you mean "practically" or "partially"?
[00:02] <dtchen> jerone-mobile: in https://bugs.edge.launchpad.net/ubuntu/+source/pulseaudio/+bug/418617/comments/39 , that is
[00:02] <jerone-mobile> dtchen, ? which commnt
[00:02] <ubot4> Launchpad bug 418617 in pulseaudio "Sound Prefrences applet does not offer a way for laptop users to use mic jack attached mic" [Undecided,New]
[00:03] <jerone-mobile> dtchen, think meant "partially" for the bug at least
[00:04] <jerone-mobile> dtchen, but the big issue is resolved
[00:04] <dtchen> jerone-mobile: ok
[00:04] <jerone-mobile> dtchen, the other is minor really
[00:04] <dtchen> jerone-mobile: i agree there's a UI nit-pick
[00:04] <jerone-mobile> dtchen, focus for next release
[00:04] <dtchen> right
[00:04] <dtchen> i'm not going to be focusing on it for Karmic at least
[00:04] <dtchen> thanks again for testing
[00:06] <dtchen> xteejx: have you mentioned it in #kubuntu-devel?
[00:06] <dtchen> (it doesn't appear so, but my irc client's activity indicator sometimes lies)
[00:07] <dtchen> err, there's a #kubuntu-bugs, too, IIRC
[00:26] <BUGabundo> bou pra caminha
[00:41] <hggdh> dtchen, request sent...
[00:43] <dtchen> hggdh: thanks much
[00:51] <xteejx> bug 160071, its a developer type report, very confusing i haven't a clue what it means, can someone with more of a brain than me take a look please? :) lol
[00:51] <ubot4> Launchpad bug 160071 in libdebian-installer "Logger Framework Conducive to Creating Zombie Processes When Syslog is Restarted" [Undecided,New] https://launchpad.net/bugs/160071
[00:52] <xteejx> if theres anyone here of course ;)
[01:04] <xteejx> What is the commit interval for ext3 with laptops on battery is it still 5 seconds?
[01:05] <mzz> xteejx: last time I checked: yes
[01:06] <mzz> xteejx: zombie processes are usually pretty ignorable
[01:07] <mzz> xteejx: (if you're a developer: you should clean them up if your code is causing them. If you're a user: you can usually ignore them, since they don't take up a significant amount of resources unless there's tons of them)
[01:08] <xteejx> mzz, I'm only asking because of a bug report, more of a wishlist really: bug 150448
[01:08] <ubot4> Launchpad bug 150448 in compiz "compiz.real crashed with SIGSEGV (dup-of: 145360)" [Medium,New] https://launchpad.net/bugs/150448
[01:08] <ubot4> Launchpad bug 145360 in compiz "compiz.real crashed with SIGSEGV in doPoll()" [Medium,Fix released] https://launchpad.net/bugs/145360
[01:08] <xteejx> bug 160448, sorry
[01:08] <ubot4> Launchpad bug 160448 in util-linux "the commit interval for the ext3 filesystem should be higher than 5 seconds for laptop users by default (at least while on battery)" [Wishlist,Incomplete] https://launchpad.net/bugs/160448
[01:09] <mzz> well, notice that bug isn't marked fixed
[01:10] <xteejx> it was never wishlisted either, i only just done it....
[03:19] <bcurtiswx> Bug #408530 and Bug #443340  i believe they are the same, and the first has the better report.. but both have a large amount of duplicates, does launchpad still complain about that?
[03:19] <ubot4> Launchpad bug 408530 in empathy "empathy assertion failure: empathy:ERROR:empathy-tp-chat.c:1391:empathy_tp_chat_acknowledge_message: assertion failed: (m != NULL)" [Medium,Triaged] https://launchpad.net/bugs/408530
[03:19] <ubot4> bcurtiswx: Bug 443340 on http://launchpad.net/bugs/443340 is private
[03:19] <bcurtiswx> for those who can read private reports ;-)
[03:21] <bcurtiswx> im gonna go check it and publicize it if i can
[03:32] <micahg> bcurtiswx: yeah, you still have to manually move the dupes AFAIK
 that sucks
[03:34] <bcurtiswx> micahg: you agree that 408530 is the better bug tho?
[03:34] <bcurtiswx> join #launchpad
[03:34] <bcurtiswx> whoops
[03:34] <micahg> bcurtiswx: bug 78596...
[03:34] <ubot4> Launchpad bug 78596 in malone "Automatically handle moving duplicates across when duplicating a bug with dupes" [High,Triaged] https://launchpad.net/bugs/78596
[03:35] <bcurtiswx> high and triaged... and 78596... <facepalm>
[03:36] <micahg> yeah, I think so
[04:09] <shawn_> Hello is this where I report bugs?
[04:11] <mzz> shawn_: no, that'd be launchpad or using ubuntu-bug on a ubuntu system. This is where you get help using those though.
[04:11] <bcurtiswx> shawn_, which package are you reporting against?
[04:12] <shawn_> Well I want to report a bug with the Remote Desktop Viewer
[04:12] <shawn_> In Jaunty
[04:17] <bcurtiswx> yeah use ubuntu-bug
[04:17] <shawn_> Whats that
[04:17] <benedikt> shawn_: open a terminal an write "ubuntu-bug" :-)
[04:18] <mzz> shawn_: if you go to http://bugs.ubuntu.com/ and click the "report a bug" link (on the right) you're taken to a wiki page telling you (among other things) how to invoke ubuntu-bug
[04:18] <benedikt> reading the man page also works.
[04:19] <shawn_> Gah this seems way too annoying xD
[04:27] <sbeattie> shawn_: actually, it's even easier than what the others suggested; open the Remote Desktop Viewer, click on the help menu and then select "Report a Problem"
[04:27] <shawn_> Ohhh
[04:43] <Omar87> Hi all.
[04:43] <Omar87> The system keeps crashing and logging out on me. (Karmic).
[05:12] <mzz> Omar87: anything in /var/log/Xorg.0.log.old?
[05:12] <mzz> Omar87: or ~/.xsession-errors.old?
[07:06] <Laibsch> What's the fastest way to merge two bugs that already have a high number of dupes themselves?
[07:29] <Laibsch> Can somebody who can read stacktraces please take a look at bug 338217 and bug 199592 to confirm or disconfirm whether those two are dupes?
[07:29] <ubot4> Launchpad bug 338217 in scim-bridge "scim-bridge crashed with SIGSEGV in scim::Module::unload()" [Medium,Incomplete] https://launchpad.net/bugs/338217
[07:29] <ubot4> Launchpad bug 199592 in scim-bridge "scim-bridge crashed with SIGSEGV in scim::Module::unload()" [Medium,Confirmed] https://launchpad.net/bugs/199592
[07:35] <thekorn> good morning
[07:57] <Omar87> mzz,  /var/log/Xorg.0.log.old :  http://pastebin.com/m4cea3dd4
[07:58] <mzz> Omar87: so that looks like it's cut off. Anything interesting logged in /var/log/gdm?
[07:59] <Omar87> mzz, ~/.xsession-errors.old : http://pastebin.com/m4761ddab
[07:59] <mzz> Omar87: yeah, that's X crashing
[08:01] <Omar87> I found those: http://pastebin.com/d10ba800e
[08:17] <Omar87> mzz, so what now?
[08:18] <mzz> Omar87: anything interesting below /var/log/gdm/?
[08:18] <Omar87> I found those: http://pastebin.com/d10ba800e
[08:19] <mzz> Omar87: it reads as if gdm crashed badly enough that it didn't write the crash reason to its own log, but it might've dumped it to stderr, which'd end up somewhere below /var/log/gdm/
[08:19] <mzz> err, as if *X* crashed...
[08:19] <mzz> Omar87: try :0.log.1
[08:22] <Omar87> mzz, http://pastebin.com/d6ac5f77b
[08:23] <mzz> I'll read in a minute, multitasking...
[08:23] <Omar87> mzz, tyt
[08:25] <mzz> #
[08:26] <mzz> drmRadeonCmdBuffer: -12. Kernel failed to parse or rejected command stream. See dmesg for more info.
[08:26] <mzz> Omar87: so pastebin dmesg
[08:26] <mzz> Omar87: this is the sort of thing that might already have a ubuntu bug though
[08:28] <Omar87> mzz, http://pastebin.com/d6415a399
[08:28] <mzz> Xorg: page allocation failure. order:4, mode:0x40d0
[08:28] <mzz> that's not good
[08:29] <mzz> Omar87: things to do include: search ubuntu-bugs for this, check if the x-updates ppa has a better driver, ask #radeon if this dmesg output is known
[08:29] <mzz> err, s/ubuntu-bugs/launchpad/
[08:30] <Omar87> mzz, so where do I look now?
[08:31] <mzz> see above
[08:32] <Omar87> s/ubuntu-bugs/launchpad?
[08:33] <mzz> well, "search ubuntu-bugs" doesn't work :) I meant "search http://bugs.ubuntu.com/" aka the bug tracker on launchpad
[09:31] <Laibsch1> Can somebody who can read stacktraces please take a look at bug 338217 and bug 199592 to confirm or disconfirm whether those two are dupes?
[09:31] <ubot4> Launchpad bug 338217 in scim-bridge "scim-bridge crashed with SIGSEGV in scim::Module::unload()" [Medium,Incomplete] https://launchpad.net/bugs/338217
[09:32] <ubot4> Launchpad bug 199592 in scim-bridge "scim-bridge crashed with SIGSEGV in scim::Module::unload()" [Medium,Confirmed] https://launchpad.net/bugs/199592
[09:34] <mzz> they definitely look extremely similar to me
[09:34] <mzz> but I may be missing something, since the "retraced" stack trace doesn't match exactly
[10:21] <iamfossy> hi all , anyone has USB auto-mount bug in Karmic  ?
[10:21] <iamfossy> can anyone reproduce the same ?
[10:22] <mzz> you're not being very specific
[10:22] <iamfossy> Error mounting: mount exited with exit code 1: helper failed with:
[10:22] <iamfossy> mount: wrong fs type, bad option, bad superblock on /dev/sdd1,
[10:22] <iamfossy>        missing codepage or helper program, or other error
[10:22] <iamfossy>        In some cases useful info is found in syslog - try
[10:22] <iamfossy>        dmesg | tail  or s
[10:22] <iamfossy> thats the error
[10:22] <iamfossy> when i plug in a USB
[10:23] <mzz> if you try to mount directly does it fail the same way?
[10:23] <iamfossy> i've checked it with multiple USB's
[10:23] <mzz> also, what does "file -s /dev/sdd1" say?
[10:23] <mzz> also, what it said about dmesg
[10:24] <iamfossy> the file command with sudo reports as follows : /dev/sdd1: x86 boot sector, code offset 0x58, OEM-ID "MSWIN4.1", sectors/cluster 8, reserved sectors 2176, Media descriptor 0xf8, heads 255, hidden sectors 63, sectors 15695808 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 15296, reserved3 0x800000, serial number 0xa84562fb, unlabeled
[10:24] <mzz> hmm, that sounds not completely insane
[10:24] <iamfossy> whats the problem ?
[10:25] <iamfossy> and the dmesg | tails reports as follows :
[10:25] <iamfossy> [14419.518036] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[10:25] <iamfossy> [14419.520735] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[10:25] <iamfossy> [14419.520740]  sdd: sdd1
[10:25] <iamfossy> [14419.528033] sd 8:0:0:0: [sdd] Assuming drive cache: write through
[10:25] <iamfossy> [14419.528038] sd 8:0:0:0: [sdd] Attached SCSI removable disk
[10:25] <iamfossy> [14420.349881] UDF-fs: No anchor found
[10:25] <iamfossy> [14420.349885] UDF-fs: Rescanning with blocksize 2048
[10:25] <iamfossy> [14420.421185] UDF-fs: No anchor found
[10:25] <iamfossy> [14420.421190] UDF-fs: No partition found (1)
[10:25] <iamfossy> [14420.754820] ISOFS: Unable to identify CD-ROM format.
[10:25] <mzz> pastebins are your friend
[10:25] <mzz> and that's odd, I wonder why it's attempting those
[10:25] <iamfossy> Oops sorry
[10:26] <iamfossy> btw i've the latest updates to karmic
[10:26] <iamfossy> any idea or a fix ?
[10:27] <iamfossy> i googled aroung , and saw everywhere in ubuntu forums
[10:27] <iamfossy> was not able to see such error
[10:28] <iamfossy> @mzz any ideas / fixes / solutions ?
[10:29] <mzz> see earlier comment about manual mounting
[10:30] <iamfossy> thats the way i do it now , i manually mount the flash drives , then gksu nautilus to read/write to it
[10:30] <iamfossy> is this the problem with everyone or only me ?
[10:32] <mzz> I can't say I've noticed it
[10:32] <mzz> how are you mounting? Specifically: are you passing "-t vfat" or the like?
[10:33] <mzz> I'd attempt to find out how "mount" ends up getting called, although I'm not sure what a convenient way to do that would be
[10:33] <iamfossy> it never mounts automaticallt , i use this : sudo mount /dev/sdd1 /mnt
[11:12] <xteejx> hi all
[11:15] <Kmos> Could some make bug 451838 public?
[11:15] <ubot4> Kmos: Bug 451838 on http://launchpad.net/bugs/451838 is private
[11:16] <xteejx> hang on
[11:17] <xteejx> Kmos, this bug is fixed
[11:17] <Kmos> thank you
[11:18] <xteejx> Kmos, no, I mean the bug has been fixed already, but I'll mark it Public, have checked it
[11:18] <Kmos> yeah, I know it was fixed
[11:18] <xteejx> ahh
[11:18] <Kmos> I just need to make one duplicate of it
[11:18] <Kmos> =)
[11:18] <xteejx> no worries :)
[11:19] <Kmos> done
[11:19] <Kmos> :)
[11:19] <Kmos> thank
[11:19] <Kmos> thanks
[11:32] <indus> xteejx: hello
[11:33] <xteejx> indus, hi
[11:33] <indus> xteejx: you know, i downgraded bios and it seems the soft reset messages went away, but cd/dvd didnt work anyway
[11:33] <xteejx> indus, so the drive is physically "broken", its not software?
[11:33] <indus> xteejx: actually i have a bandwidth cap per month, and so cant download kernel yet
[11:34] <indus> xteejx: works beautifully in windows
[11:34] <indus> xteejx: actually i dont remember whether messages disappeared , i upgraded to latest bios anyway
[11:34] <xteejx> xteejyx, still a problem then, thats a shame...glad to see the soft ata messages went though, its one step closer to fixing it, in fact you may not have to test a mainline kernel now, i'll have a look
[11:35] <indus> xteejx: no no wait, iam not sure it disappeared i am saying
[11:35] <indus> xteejx: but the drive wasnt detected still , so i went back to new bios
[11:36] <xteejx> indus, ohhh ok, well no worries i'm in the middle of doing other stuff, but will check back on my gmail account if there's any updates :)
[11:36] <indus> xteejx: believe me, this is  a  amd 690 g chipset issue
[11:36] <indus> xteejx: i will test mainline in a day or so
[11:36] <xteejx> ok
[11:36] <indus> xteejx: just double click on deb and install?
[11:37] <xteejx> ermmm im not sure, it's all explained in the link, but i *think* so yes
[11:37] <indus> xteejx: ok thanks for all the help really
[11:37] <indus> i had lost hope of any fix
[11:38] <xteejx> indus, no worries, do you remember the bug number, i can't find it
[11:40] <xteejx> got it, no worries
[11:41] <indus> so you are at this moment chatting with kernel devs?
[11:41] <indus> i need some technical info
[11:41] <indus> what does soft reset mean
[11:48] <xteejx> indus, no, I'm at work flitting between Ubuntu and work
[11:50] <indus> ok then ill see u later, dont let anyone escape :P
[11:59] <xteejx> lol
[14:47] <sean> ?
[14:48] <Guest89768> i need help oeth a bug in update manager
[14:50] <Guest89768> can any one in here help me resolve a bug in update manager?
[15:37] <hggdh> ah well. Another shoot and run
[16:02] <iamfossy> hello everyone
[16:02] <iamfossy> i've a technical issue with fstab
[16:02] <iamfossy> is there anyone to help ?
[16:03] <iamfossy> my problem is detailed here : http://pastebin.com/m27c0cdbe
[16:04] <iamfossy> updated with my fstab  entries
[16:04] <iamfossy> http://pastebin.com/m32aa8372
[16:04] <iamfossy> the /dev/sdd1 is my flash drive partition , i do not know why it is being recognised as cdrom in fstab
[16:04] <iamfossy> any fix for this ?
[16:23] <hggdh> iamfossy: what version of Ubuntu are you running?
[17:09] <quentusrex> Is there a way to see the list of bugs for the karmic beta?
[17:09] <d3xter> hey guys
[17:13] <bdmurray> howdy
[17:13] <d3xter> after upgrading to 9.10, dimming of my lcd with my fn-keys stopped working. While Ubuntu is booting, the fn-keys work as expected. is this bug related to the intel-driver?
[17:15] <thekorn> hi all!
[17:15] <thekorn> quentusrex, you mean targeted to karmic beta?
[17:16] <thekorn> quentusrex, they are listed on https://edge.launchpad.net/ubuntu/+milestone/ubuntu-9.10-beta
[20:15] <BUGabundo> hey fellows
[21:04] <hggdh> hey fellows
[21:06] <Ueland> o/
[21:06] <BUGabundo> ola hggdh
[21:06] <hggdh> ola BUGabundo, log time
[21:06] <hggdh> s/log/long/
[21:07] <BUGabundo> really??
[21:08] <BUGabundo> what? one week or so?
[21:12] <hggdh> long time no matter ;-)
[21:43] <elleuca> hi, could someone try to check this bug? https://bugs.launchpad.net/bugs/451974
[21:43] <ubot4> Launchpad bug 451974 in compiz "Black video minimizing Totem window" [Undecided,New]
[22:26] <bdmurray> mrand: you might be interested in bug 453377
[22:26] <ubot4> Launchpad bug 453377 in ubuntu "[ubuntu karmic] mythtv-frontend does not prevent display being put to sleep during tv watching" [Undecided,New] https://launchpad.net/bugs/453377
[22:27] <paran> if somebody have karmic, linux-backports-modules-karmic-generic and iwlagn, then please take a quick look at my bug 453064
[22:27] <ubot4> Launchpad bug 453064 in linux-backports-modules-2.6.31 "Incorrect Intel firmware file name" [Undecided,New] https://launchpad.net/bugs/453064
[22:27] <BUGabundo> there are already backports??
[22:28] <BUGabundo> aren't those supposed to kick in *after* release?
[22:28] <paran> yeah, latest bleeding edge compat-wireless
[22:29] <BUGabundo> ahhh
[22:29] <paran> probably too much new intrusive changes to just throw it into the normal kernel
[22:29] <BUGabundo> due to archive freeze?
[22:29] <bdmurray> well the kernel freezes a bit before the final freeze
[22:31] <paran> the normal kernel probably like to stick closer to unmodified 2.6.31
[22:32] <paran> I run backports as that version of iwlagn supports power management (iwconfig wlan0 power on) which saves 1-2W on my laptop :)
[22:32] <BUGabundo> ahh
[22:47] <elleuca> hi, could someone try to check this bug? https://bugs.launchpad.net/bugs/451974
[22:47] <ubot4> Launchpad bug 451974 in compiz "Black video minimizing Totem window" [Undecided,New]
[23:15] <bcurtiswx> dtchen: what happened with the simultaneous output in pulse?
[23:19] <dtchen> bcurtiswx: I'm not sure what you mean?
[23:20] <dtchen> paran: it's no longer compat-wireless bleeding but whatever's tracked in the next linux version
[23:20] <bcurtiswx> dtchen: sound preferences --> output tab --> no simultaneous output
[23:20] <dtchen> paran: currently it's synced with 2.6.32-rc4
[23:20] <bcurtiswx> dtchen: hmm, maybe that setting got reset in an update
[23:20] <dtchen> paran: details of the change are in the changelog for linux-backports-modules-2.6.31
[23:21] <dtchen> BUGabundo: no, for several releases now, lbm has been uploaded prior to RC
[23:21] <bcurtiswx> dtchen: pavucontrol has nothing
[23:21] <dtchen> bcurtiswx: I don't use that, sorry. I use paprefs first.
[23:22] <BUGabundo> paprefs?
[23:22] <BUGabundo> that's new to me
[23:23] <dtchen> paprefs is deprecated, really.
[23:23] <bcurtiswx> dtchen: it should allow you to make that option in sound preferences
[23:23] <dtchen> hum!
[23:23] <dtchen> i wonder how many people are running ext4 as /home who are getting these weird muted Master/PCM/Front issues
[23:23] <BUGabundo> +1
[23:24] <BUGabundo> seems fixed to me for a few days
[23:24] <bcurtiswx> i have that.. whats the issue?
[23:24] <BUGabundo> haven't seen it happening recently
[23:24] <BUGabundo> I do have the audio team PPA
[23:25] <paran> dtchen: imho compat-wireless-2.6.32-rc4 is quite bleeding edge compared to 2.6.31 :)
[23:25] <dtchen> paran: well, yes. thankfully it works much better for my hardware.
[23:26] <dtchen> BUGabundo: the audio team PPA has older packages than what's in Karmic proper.
[23:26] <BUGabundo> ok
[23:26] <BUGabundo> so you think ext4 may be the root of the prob?
[23:26] <bcurtiswx> dtchen: so the only way to get simultaneous output is paprefs?
[23:27] <dtchen> bcurtiswx: no, but it's probably the easiest way for you at this moment, given that it's not exposed properly in gnome-volume-control (a bug, of course)
[23:27] <bcurtiswx> dtchen: ahh ok... do you know if its reported already?
[23:29] <bcurtiswx> i.e. i'd be happy to report it if not
[23:29] <dtchen> bcurtiswx: probably, but it really is quite low on my hit list
[23:29] <dtchen> as in I won't even look at it for Karmic
[23:30] <paran> dtchen: I mainly wanted the PS. hopefully it might also improve wpa2-enterpsie stability whan I am at work
[23:30] <bcurtiswx> dtchen: well i'll see if i can find it and post a workaround
[23:30] <hggdh> well, I am running pure Karmic right now (i.e., no PPAs), and do not get sound muted at start
[23:31] <dtchen> bcurtiswx: the workaround would be "install paprefs, use it (System> Preferences> PulseAudio Preferences> Simultaneous Output)
[23:31] <dtchen> hggdh: is /home on ext4?
[23:31] <hggdh> dtchen: yes. And paprefs was not installed so far
[23:32] <hggdh> and encrypted (/home/myself, I mean)
[23:32] <dtchen> hggdh: right, paprefs is for a different issue altogether
[23:32] <dtchen> hmm, ok. that's two data points.
[23:32] <dtchen> BUGabundo: do you have encrypted lvm / or ecryptfs /home?
[23:33] <BUGabundo> dtchen: no
[23:33] <BUGabundo> dtchen: full disk is a single partition of ext4
[23:33] <hggdh> dtchen: also, I run LVM, with many mount points
[23:33] <BUGabundo> no separate /home
[23:34] <dtchen> BUGabundo: / hggdh: what's the output from head -6 /proc/asound/card*/codec*
[23:35] <BUGabundo> dtchen: $ head -6 /proc/asound/card*/codec* | pastebinit  http://paste.ubuntu.com/295018/
[23:37] <hggdh> dtchen: http://pastebin.ubuntu.com/295019/
[23:39] <hggdh> brb
[23:42] <dtchen> oooh, excellent
[23:42] <dtchen> now I can use the two of you as guinea pigs!
[23:42] <BUGabundo> lolol
[23:42]  * BUGabundo is away watching TV shows in a role
[23:57] <bdrung> dtchen: is bug #453158 a bug in pulseaudio or alsa?
[23:57] <ubot4> Launchpad bug 453158 in xmms2 "problem with xmms2 toggleplay" [Undecided,New] https://launchpad.net/bugs/453158
[23:57] <bdrung> dtchen: i saw a similar bug filed against vlc


[13:33] <duanedesign> hello BTians
[13:43] <duanedesign> CCD/7
[17:17] <fabchampion> test
[19:59] <soren> o/
[19:59]  * stgraber waves
[19:59]  * geser waves too
[20:01] <stgraber> cjwatson, persia, cody-somerville: ping
[20:01] <cody-somerville> I'm here
[20:03] <cjwatson> hi, almost forgot about this meeting
[20:04] <geser> should we start?
[20:05] <cjwatson> please
[20:05] <stgraber> we have quorum and it's 5min past meeting time, so I think we can start, others can join later
[20:05] <geser> #startmeeting
[20:05] <MootBot> Meeting started at 14:05. The chair is geser.
[20:05] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[20:05] <geser> [LINK] https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda
[20:05] <MootBot> LINK received:  https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda
[20:05] <geser> [TOPIC] Review of previous action items
[20:06] <MootBot> New Topic:  Review of previous action items
[20:06] <geser> * Cody Somerville to send e-mail requesting feedback from developers on Marco Rodrigues application to participate in Ubuntu Development.
[20:06] <geser> cody-somerville: did you write that mail?
[20:06] <cody-somerville> I didn't get around to doing this. I meant to ask a few other board members for advice on how to best word the e-mail.
[20:07] <cody-somerville> I'm not overly familiar with the original incident so it might even be best for someone else to take the action item from me.
[20:08] <cjwatson> I'm not particularly familiar with it either
[20:08]  * stgraber neither
[20:09] <geser> so that leaves only soren, persia and me
[20:11] <geser> but I have no idea what to write in that e-mail
[20:13] <cody-somerville> I nominate persia ;)
[20:13] <geser> I'm not sure how to move forward as we need more feedback from developers but on the other hand Marco is forbidden to contribute to development
[20:14] <cjwatson> didn't we discuss this in the last meeting?
[20:15] <geser> yes, but I don't remember if we had a plan to move forward besides ask for more feedback
[20:15] <cjwatson> if we don't ask, we'll never know
[20:16] <cjwatson> my thesis in the last meeting is that Marco has been contributing to enough things that are related to Ubuntu (most notably Debian) that there ought to be some developers who've had meaningful interactions with him recently
[20:17] <ScottK> I can guarantee there will be some that respond "No, he's caused enough trouble before, not worth the risk".
[20:17] <cjwatson> I know - I do feel obligated to gather wide feedback though.
[20:17] <ScottK> Sure.
[20:18] <cody-somerville> I have to admit that I'm not a big fan of publicly calling attention to someone for their previously negative behavior.
[20:18] <ari-tczew> I think that we should give chance for Marco R.
[20:19] <geser> cody-somerville: should we use LP feature to mail all ubuntu-dev members asking for feedback/opionions instead?
[20:19] <ScottK> That would suffer from an unfortunate lack of transparency.
[20:20] <cjwatson> I would rather get honest feedback, which I hope people can trust the DMB to summarise accurately, than have people not want to express honest opinions because they're worried about giving negative feedback in public
[20:21] <ari-tczew> you want to get more feedback. I would like give a feedback, but I'm not familiar with work this guy.
[20:21] <ScottK> ari-tczew: Then you aren't really in a position to give feedback, are you?
[20:22] <geser> I could write an e-mail to ubuntu-devel(?) asking for feedback/opionions and set reply-to to the DMB list
[20:22] <cody-somerville> I also want to makes sure we do the Right Thing (TM) here and set a precedent that we'll be happy to follow in the future for similar cases.
[20:22] <ari-tczew> ScottK: I want to tell, that you should (I'm nobody important) give chance him. then he can show his improvement.
[20:23]  * soren just got off the phone... catching up
[20:23] <cjwatson> ari-tczew: the original "please don't contribute here any more" mail from the MOTU Council gave very specific requirements which must be met.  One of those was positive advocacy from developers working with him.
[20:23] <cjwatson> ari-tczew: we're not asking for general feedback here; we're seeking to give him a chance to meet that specific requirement.
[20:24] <ari-tczew> cjwatson: ok, so I'm quite right now. :]
[20:24] <ari-tczew> s/quite/quiet
[20:24] <cjwatson> (https://lists.ubuntu.com/archives/ubuntu-motu/2008-January/003067.html)
[20:25] <geser> so we are looking for MOTUs who volunteer to work together with Marco to be able to judge if he changed?
[20:25] <stgraber> geser: +1 on sending to ubuntu-devel with Reply-To to dmb, also indicating that answers will be kept private and that DMB will make a summary of the feedback received
[20:27] <ari-tczew> geser: let's ask coolbhavi for this one. he propably is interested in sponsoring.
[20:28] <cody-somerville> hmmm
[20:28] <cjwatson> ari-tczew: currently, Marco is barred from contributing through sponsors, FYI
[20:28] <cjwatson> again, please see the logs of the last meeting, where there was discussion of this point
[20:29] <cody-somerville> Reading the statement from the MOTU again, I don't see any stipulation that the MOTU supporting his wish to come back have to have any experience working with him directly.
[20:29] <cjwatson> stgraber's plan looks good to me
[20:30] <geser> cody-somerville: would you comment on someone who you didn't work with?
[20:30] <cjwatson> I'm disappointed that we're basically going over old ground here
[20:30] <cody-somerville> It isn't asking for that. It asks for MOTUs to actively support the wish
[20:31] <cjwatson> cody-somerville: I can support that interpretation, but let's issue a call for feedback and get it over with
[20:31]  * soren approves of stgraber's plan, too
[20:31] <cjwatson> if we don't put a specific requirement in the mail that the MOTUs in question have worked with Marco, we can then assess the strength of the feedback when it comes back
[20:32] <geser> should we also ask Marco for a list of MOTUs supporting him (as required by the decision) instead of looking for them ourselves?
[20:33] <cody-somerville> I'm happy to get it over with but I do have reservations about a general call for feedback. It may make it more difficult for Marco to try and participate in the Ubuntu community as folks who don't know him may form an unfounded opinion of him based.
[20:33] <geser> (of course we can do both)
[20:33] <cody-somerville> based on googling up his name or what not after getting the e-mail.
[20:33] <cody-somerville> I think a general call for feedback may be unnecessarily embarrassing.
[20:34] <cjwatson> geser: Marco would probably (reasonably) argue that he'd attempted to provide that in his application
[20:35] <cjwatson> cody-somerville: if we're not willing to issue a call, then we should just say that we don't feel the support he's amassed in his application meets the bar of "active support", given our discussions last week
[20:36] <cody-somerville> I'm happy to support Marco's application to this board for an appeal of his ban based on the spirit of the Ubuntu project and duration of the time that has past since his ban.
[20:36] <cjwatson> given that the DMB members didn't on the whole seem to find the endorsements overwhelming, as I understood it?
[20:36] <cody-somerville> Which would leave the board to decide his application based on the second requirement " A solid indication of changes in the work style."
[20:37] <cjwatson> or let me put it differently: if we aren't willing to issue a call for feedback, we should get off the pot and vote :-)
[20:37] <cjwatson> (I ought not to prejudge the outcome)
[20:38] <cjwatson> We could also, if desired, vote separately on a probationary period, as Cody suggested last week.
[20:39] <geser> please tell me if I should start a vote
[20:39] <stgraber> I'd really prefer getting more feedback (as suggested before) and based on that vote on 1) letting him contribute again 2) probationary period (and if so, how long) 3) keeping the ban
[20:40] <cody-somerville> I'd like to table this again. I'd prefer Marco at least have an opportunity to address the board before we vote.
[20:40] <stgraber> though maybe we can vote on whether or not to ask for more feedback on the list
[20:40] <stgraber> cody-somerville: should we have to vote without further feedback, I'd also like to hear from him before we vote
[20:41] <cjwatson> we already voted last week to issue a call for feedback from developers
[20:41] <cjwatson> why vote on that again?
[20:41] <cody-somerville> May I also suggest that we seek input from the CC and TB on how to proceed with this? I think this is the first time any council in Ubuntu has had to consider something like this and it would be nice to set a precedent that the TB and CC are happy with.
[20:42] <stgraber> oops, sorry, memory issue ;) /me should re-read last meeting's log ;)
[20:42] <cjwatson> not that I'm biased as a TB member, but I think the CC is better-qualified for this kind of thing
[20:42] <cjwatson> (and I think that would be appropriate, yes)
[20:43] <geser> so everyone agree that we should contact CC for help?
[20:45] <cjwatson> I do, and I also think we should carry out the results of our previous vote on calling for feedback.  I don't currently see how to resolve that with Cody's objection expressed today.
[20:46] <stgraber> I also agree with contacting the CC
[20:48] <cjwatson> how can we move this forward?  we're nearly 50 minutes in
[20:48] <geser> [ACTION] geser to contact the CC asking for help with Marco's appeal
[20:48] <MootBot> ACTION received:  geser to contact the CC asking for help with Marco's appeal
[20:49] <cody-somerville> Lets table the action and move on. We can discuss it further on mailing list.
[20:49] <cjwatson> Looks like we have to now.
[20:49] <geser> if nobody objects let's move to the next topic
[20:51] <geser> [TOPIC] MOTU application: Felix Geyer
[20:51] <MootBot> New Topic:  MOTU application: Felix Geyer
[20:51] <geser> [LINK] https://wiki.ubuntu.com/FelixGeyer/MOTUApplication
[20:51] <MootBot> LINK received:  https://wiki.ubuntu.com/FelixGeyer/MOTUApplication
[20:51] <cjwatson> gosh, what a lot of endorsements.
[20:51] <geser> debfx: are you here?
[20:52] <debfx> hi :)
[20:53] <stgraber> lots of very good endorsements
[20:53] <cody-somerville> indeed
[20:54]  * ajmitch would endorse based on virtualbox alone :)
[20:55] <cody-somerville> debfx, How and when did you get involved with Ubuntu?
[20:55] <geser> looks like this is an easier topic than the previous one :)
[20:55] <stgraber> geser: definitely :)
[20:56] <debfx> cody-somerville: I submitted some patches for the virtualbox package, I think it was in early 2009
[20:57] <cody-somerville> I'm ready to vote.
[20:57] <stgraber> me too
[20:57]  * soren too
[20:58] <cjwatson> yep
[20:58] <geser> [VOTE] Should Felix Geyer (debfx) become a MOTU?
[20:58] <MootBot> Please vote on:  Should Felix Geyer (debfx) become a MOTU?.
[20:58] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[20:58] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[20:58] <cjwatson> +1 # most complete application I've seen all year
[20:58] <MootBot> +1 received from cjwatson. 1 for, 0 against. 0 have abstained. Count is now 1
[20:58] <geser> +1
[20:58] <MootBot> +1 received from geser. 2 for, 0 against. 0 have abstained. Count is now 2
[20:58] <cody-somerville> +1
[20:58] <MootBot> +1 received from cody-somerville. 3 for, 0 against. 0 have abstained. Count is now 3
[20:59] <stgraber> +1 based on plenty of very good testimonials + extremely complete application
[20:59] <MootBot> +1 received from stgraber. 4 for, 0 against. 0 have abstained. Count is now 4
[20:59] <geser> soren: ?
[20:59] <soren> +1
[20:59] <MootBot> +1 received from soren. 5 for, 0 against. 0 have abstained. Count is now 5
[21:00] <geser> [ENDVOTE]
[21:00] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[21:00] <soren> Sorry, fell asleep waiting for the vote start :)
[21:00] <stgraber> that was an easy one ;)
[21:00] <stgraber> congrats debfx
[21:00] <debfx> stgraber: thanks :)
[21:01] <geser> ok, who wants to be the next chair?
[21:02] <stgraber> depends exactly when is next meeting I guess. If I'm not wrong, it's going to be at UDS at 8am on the Monday
[21:02] <geser> I'm not mistaken the next one should be Oct 25th, 12 UTC
[21:03] <soren> So you agree. Good :)
[21:03] <soren> (12 UTC being 8 AM UDS time)
[21:03] <geser> or do plan to skip the next one due to UDS?
[21:04]  * cjwatson won't be unjetlagged yet by Monday, so 8am is doable for me
[21:04] <soren> I'm not sure. I'll be attending UDS, but may be commuting in at that time.
[21:05] <stgraber> It's the same timezone for me and I'll have been in Orlando for quite a few days by then anyway, so it should be doable for me too
[21:05] <stgraber> we just need to see if we will have quorum or not, depending on who'll be traveling at the time (as most of DMB will be in Orlando I guess)
[21:06] <stgraber> the first session is at 10am, so we should be fine having DMB, breakfast and then go to the intro session
[21:06]  * geser isn't at UDS and doesn't have time at 12 UTC anyways
[21:08] <stgraber> ok, so let's keep it at the scheduled time and date and I'm fine chairing that one
[21:08] <geser> anything else before I close the meeting?
[21:09] <ajmitch> what happened with the call for nominations for the DMB?
[21:09] <geser> ajmitch: buried in cjwatson's TODO
[21:09] <cjwatson> I have been trying to hand it off
[21:09] <ajmitch> aha, which was a little less important than the release :)
[21:09] <cjwatson> in fact I thought geser had taken it ...?
[21:10] <geser> cjwatson: I could if I would know how to setup the voting (or who to ask about it)
[21:11] <cjwatson> if you're trying to do it in Launchpad, ask #launchpad for help
[21:11] <ScottK> Please be trying to do it with CIVS.
[21:11] <cjwatson> if you're trying to do it the way we did the vote that instituted the DMB, I believe that was done using http://www.cs.cornell.edu/andru/civs.html
[21:11] <cjwatson> ScottK: I was getting there :)
[21:12] <geser> cjwatson: that's the first question already: if LP or CIVS
[21:12] <stgraber> CIVS would be nice
[21:13] <cjwatson> let's do CIVS
[21:13] <geser> ok, I try to setup a CIVS poll
[21:14] <geser> anything else?
[21:15] <stgraber> nope
[21:15] <geser> #endmeeting
[21:15] <MootBot> Meeting finished at 15:15.


[16:54] <CarlFK> where can I find docs or something for in-target ?
[16:55] <CarlFK> "apt-install or in-target is already running... "
[16:55] <CarlFK> #ansible sivel: CarlFK: that indicates that you do not have /dev/shm which is required for multiprocessing SemLock
[16:56] <CarlFK> that was using chroot /target - I suspect in-target would address that


[19:53] <OvenWerks> Eickmeyer[m]: studio-controls 2.1.1 is up
[20:38] <Eickmeyer[m]> OvenWerks: Thanks!
[20:41] <OvenWerks> Eickmeyer[m]: for 2.2 I am looking at how to deal with mutiple USB devices that have the same name, man, prod and serial no (generally no serial number)
[20:41] <Eickmeyer[m]> OvenWerks: Ok, cool. Sounds like a challenge!
[20:43] <OvenWerks> Eickmeyer[m]: I am thinking of calling all USB devices USB_number and then keeping their snd name, man prod bus and port in the DB. Th euser will be able to name the jack client that zita uses
[20:43] <Eickmeyer[m]> Should work in theory.
[20:44] <OvenWerks> There are a lot of USB devices called Device or Codec
[20:44] <OvenWerks> depending on the chip it is based on.
[20:45] <OvenWerks> Many are C-media who's manufacture code is Intel
[20:45] <OvenWerks> (or maybe Intel is their biggest customer)
[20:50] <Eickmeyer[m]> Something.
 Eickmeyer: where's your SRU bug?
[20:51] <Eickmeyer[m]> @teward001: ERR:Busy
 ERR:Don'tCareYouBroughtTheIssueUpInitiallyWithThatBackportRequest
 s/backport/upload/
[20:57] <Eickmeyer[m]> @teward001: It was OvenWerks that started it, to be honest. Actually, it's the bug reports against studio-controls that brought it up.
[21:23] <wonko> OvenWerks: I just stumbled upon two identical USB audio devices so I thought I'd plug them in and give them a look and.......... They have actual serial numbers. :-D
[21:23] <wonko> https://gist.github.com/bhechinger/5c2bd0b43d43561cd7523d402b5aaa46
[21:24] <Eickmeyer[m]> @teward001: https://bugs.launchpad.net/ubuntu/+source/python-cffi/+bug/1912535
[21:25] <Eickmeyer[m]> OvenWerks: That's unexpected.
[21:26] <wonko> I don't know that those actual serial numbers are though because they don't match the serial numbers printed on the devices.
[21:26] <OvenWerks> wonko: do you have these products close by?
[21:26] <wonko> yeah, and if I go find a second usb cable I can even plug them both in at the same time. :)
[21:27] <OvenWerks> when they are plugged in, what is the ls /proc/asound/card*/
[21:27] <OvenWerks> one at a time is fine
[21:28] <wonko> How do I tell which one is the right on? I have 5. :-D
[21:28] <OvenWerks> one of the cards will have files called usbid and usbbus
[21:29] <wonko> got it
[21:29] <OvenWerks> I am wondering if another file with the serial number appears or is the serial gets added to usbid
[21:29] <wonko> https://gist.github.com/bhechinger/95c771457e1e4efb7cb97a4f57274c3e
[21:30] <OvenWerks> oh wow two streams
[21:30] <OvenWerks> two playback devices
[21:32] <OvenWerks> wonko: so now I want the contents of id (should be boring) stream0 and stream1 usbbus usbid and usbmixer
[21:32] <wonko> I'm not finding that serial anywhere here. I have no idea where usb-devices gets it unless it interrogates the devices directly for it
[21:33] <OvenWerks> it may be that the snd-usb driver doesn't bother to look for it because so few manufactures add it
[21:34] <OvenWerks> usb-devices gets it from /sys/devices/pci* somewhere
[21:34] <OvenWerks> it is a pain finding things in that tree though
[21:35] <OvenWerks> the length of two similar paths may vary
[21:35] <wonko> ok, refresh that last gist, added it all there
[21:38] <OvenWerks> wierd... only Pro,1,0 has 44k1
[21:39] <OvenWerks> Pro,0,1 where all the input is has only 48k and 96k
[21:39] <OvenWerks> Pro,0,0
[21:39] <wonko> Pro,1,0 I think might be the digital output
[21:40] <wonko> There is an optical SPDIF port
[21:40] <wonko> only for output though
[21:41] <wonko> https://us.creative.com/p/sound-blaster/sound-blaster-x-fi-surround-5-1-pro
[21:41] <wonko> That, btw
[21:41] <wonko> except dustier. :-D
[21:42] <OvenWerks> normally spdif is 48k but it does bring it's own clock
[21:42] <OvenWerks> normally spdif is 24 bit as well but it is possible to run at 16
[21:43] <wonko> Just a guess on my part, really
[21:45] <OvenWerks> wonko what does cat /proc/asound/pcm show?
[21:46] <wonko> https://gist.github.com/bhechinger/bf4d7a9a6084f328d22736320424b251
[21:47] <OvenWerks> good
[21:47] <OvenWerks> I'm covered :)
[21:48] <OvenWerks> I wonder how jack deals with them at different sample rates
[21:49] <OvenWerks> wonko actually one more thing for completeness: cd /tmp && wget https://community.ardour.org/files/adevices.sh && bash ./adevices.sh |pastebinit
[21:49] <OvenWerks> Thats all one line
[21:52] <wonko> https://paste.ubuntu.com/p/w48PnD7TxY/
[21:54] <OvenWerks> yeah what I thought, good, no subdevices
[21:55] <OvenWerks> I have saved it all for reference
[21:56] <wonko> great! Let me know if you need anything else or any testing. I'll probably bother getting jack setup after the FW device arrives (card gets here today, Echo.... whenever USPS gets around to it)
[21:56] <OvenWerks> wonko the spdif may be the surround kind that stuffs 6 ch on a two ch spdif line
[21:57] <OvenWerks> some "receivers" take that signal (proprietary I think) in
[21:57] <wonko> Your package is on its way to a USPS facility.
[21:58] <wonko> He dropped it off last night you bastards and your shitty tracking system.
[21:58] <OvenWerks> They were doing you a "favour" by dropping it off early :P
[21:59] <wonko> USPS has an appalling tracking system.
[21:59]  * OvenWerks didn't know sound blaster still was around
[21:59] <wonko> yeah, neither did I until four years ago when I bought those. :)
[22:00] <OvenWerks> must have lots of outputs on the back
[22:01] <OvenWerks> 6 outs in 4 connectors?
[22:05] <wonko> the sound blaster?
[22:06] <OvenWerks> yeah, it looks like headphone jacks for everything bu FL and FR
[22:06] <wonko> yeah, RCA for those, 3.5mm for everything else
[22:07] <OvenWerks> The problem for me with most consumer interfaces is they have more outputs than I need and not enough inputs. I can get by with two outputs but would really like more inputs at the same clock rate
[22:08] <wonko> That's why I got the KA6
[22:08] <OvenWerks> Thats the one that say MK2?
[22:08] <wonko> yes
[22:09] <wonko> https://www.native-instruments.com/en/products/komplete/audio-interfaces/komplete-audio-6/
[22:10] <OvenWerks> having two headphones out is nice
[22:11] <wonko> it really is
[22:15] <wonko> I'll lose that with the audiofire
[22:16] <wonko> which kinda sucks, but I can deal with that with some jack magic. :)
[22:16] <wonko> not that I've really used the second headphone jack in a while
[22:16] <OvenWerks> zita-ajbridge will take care of that
[22:17] <OvenWerks> Anyway, that you for the info in the SB boxes
[22:17] <wonko> any time
[22:18] <wonko> glad I happened to be digging through that box for something unrelated. :)


[13:10] <tsdgeos> davmor2: i can't reproduce https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1614070
[13:10] <tsdgeos> davmor2: it just rotates fine here :S
[13:11] <tsdgeos> Saviq: have you been able to reproduce ↑↑  ?
[13:11] <Saviq> tsdgeos, I've neither arale or turbo :/
[13:11] <Saviq> and it seems to be hw specific
[13:12] <davmor2> tsdgeos: what device are you on?
[13:12] <tsdgeos> davmor2: arale
[13:13] <davmor2> tsdgeos: arale is definitely doing it here
[13:14] <tsdgeos> davmor2: just to be sure what you're experiencing, is that the dash (or any app) doesn't rotate when rotating the phone, right?
[13:14] <davmor2> tsdgeos: anything but I tested and tailed on dash
[13:15] <davmor2> tsdgeos: ubuntu-device-flash touch --channel ubuntu-touch/rc-proposed/meizu.en --device arale --recovery-image ~/recovery-images/recovery-arale.img --bootstrap just to confirm we are flashing the same way
[13:17] <tsdgeos> davmor2: i'm not bootstrapping nor giving it a recovery image
[13:17] <tsdgeos> ubuntu-device-flash touch ubuntu-system --channel ubuntu-touch/rc-proposed/meizu.en
[13:17] <tsdgeos> here
[13:17] <tsdgeos> i cna try bootsrapping if you want
[13:17] <davmor2> tsdgeos: please you'll need the adb enabled recovery if you bootstrap
[13:18] <tsdgeos> davmor2: why?
[13:19] <davmor2> tsdgeos: without it it can't connect to recovery to do the flashing
[13:21] <tsdgeos> davmor2: i know it's a silly question, but just to make sure, you don't have the rotation lock enabled in the indicator, right?
[13:22] <davmor2> tsdgeos: nope and if you look at the paste in the bug you'll see it worked fine on the image before unity8 landed and died on the image after unity8 only change to the system was unity8
[14:00] <davmor2> tsdgeos: are you able to reproduce now?
[14:08] <tsdgeos> davmor2: nope
[14:09] <davmor2> tsdgeos: well we are reproducing it all over the place, turbo, krillin, arale, on fresh flashes jibel has reproduce on arale on upgrade but only after a reboot
[14:10] <tsdgeos> davmor2: must be the sun over here that makes it work
[14:12] <davmor2> rvr: is in the canaries I think sun has nothing to do with it ;)
[14:12] <davmor2> tsdgeos: ^
[14:12] <rvr> davmor2: he
[14:13] <tsdgeos> 26 (feels like 27) vs 28 (feels like 31)
[14:13] <tsdgeos> i still win
[14:20] <tsdgeos> davmor2: rvr: is something crashing?
[14:20] <tsdgeos> like the indicator or something
[14:23] <tsdgeos> i really can't reproduce
[14:23] <tsdgeos> rebooted like 10 times alrady
[15:09] <om26er> cimi, Hi!
[15:10] <om26er> cimi, I need to ask a bit about a recent change in unity8' artShapeLoader, in this branch: https://code.launchpad.net/~unity-team/unity8/unboxArtShapeLoader/+merge/298431
[15:13] <tsdgeos> om26er: ask
[15:14] <om26er> tsdgeos, the CroppedImageMinimumSourceSize in line 73, is that supposed to have visible:True when an image is being shown or False ?
[15:15] <om26er> tsdgeos, or to put should CroppedImageMinimumSourceSize be always visible when its parent artShapeLoader(line59) is visible ?
[15:16] <om26er> previously that was the case but with the above branch, CroppedImageMinimumSourceSize has its visible:False always. I thought thats a bug than intention.
[15:17] <tsdgeos> sorry? what do you mean CroppedImageMinimumSourceSize has visible: false always?
[15:20] <om26er> tsdgeos, the item CroppedImageMinimumSourceSize had its visible property `true` whenever its parent `artShapeLoader` was visible on screen. Today that is not the case.
[15:21] <om26er> CroppedImageMinimumSourceSize' visible property is always `false` now, which, I think is a bug.
[15:21] <tsdgeos> i don't know what you're talking about
[15:21] <tsdgeos> see 5.res
[15:21] <tsdgeos> there CroppedImageMinimumSourceSize visible property is true
[15:21] <tsdgeos> and i don't see how that branch changes anything
[15:21] <tsdgeos> since visible was and is
[15:22] <tsdgeos> visible: %4; \n\
[15:22] <tsdgeos> before and after the branch
[15:24] <om26er> tsdgeos, that's what I see in code after that branch our tests system-tests started to fail as they were selecting a visible CroppedImageMinimumSourceSize.
[15:24] <om26er> today if I do a autopilot search of the unity8-dash tree, none of the CroppedImageMinimumSourceSize has visible property as `true` anymore.
[15:25] <tsdgeos> none is a very strong word
[15:25] <tsdgeos> none of the ones you see
[15:26] <tsdgeos> and yes, only the concierge mode CroppedImageMinimumSourceSize should be set to true
[15:26] <tsdgeos> i'm sorry that you were using a wrong way to find stuff
[15:26] <om26er> I do dash.select_many('CroppedImageMinimumSourceSize', visible=True) it returns an empty list.
[15:27] <tsdgeos> correct
[15:27] <tsdgeos> what's the problem?
[15:28] <om26er> tsdgeos, I have to click a photo on the photo scope, based on its path on the device storage, I am filtering that by using `source` property of CroppedImageMinimumSourceSize
[15:29] <om26er> tsdgeos, a slightly different question: if artShapeLoader is visible, is the CroppedImageMinimumSourceSize also supposed to be `visible` ? Or it can vary.
[15:29] <om26er> ?
[15:30] <tsdgeos> om26er: it can vary
[15:30] <tsdgeos> that's why there's a
[15:30] <tsdgeos> visible: %4; \n\
[15:31] <tsdgeos> with %4 being isConciergeMode ? "true" : "false"
[15:32] <tsdgeos> om26er: so basically it should have almost ever been visible=true before either, may have been because some strange interaction, but basically you don't want to check for that
[15:33] <om26er> tsdgeos, good to know, I will change my code to artShapeLoader loader then, it has a artImage property which also contains the path of the image. Will that be fine ?
[15:34] <tsdgeos> om26er: artImage is the CroppedImageMinimumSourceSize
[15:36] <om26er> tsdgeos, right, thats correct, but artShapeLoader has a reference to artImage, see: http://paste.ubuntu.com/23064796/
[15:36] <tsdgeos> yes it has
[17:31] <mterry> Saviq: so about bug subscribers...  We currently have scripts that pay attention to unity-ui-bugs (rather than unity-ui-team).  Done because of a desire to avoid bugspam to team members.  We like to have bug subscribers for both a team that is in the scripts and a team that actually pays attention.  Ideally the same team.
[17:32] <mterry> If we don't mind the bugspam, we can switch scripts to look at unity-ui-team and sub them.  Else maybe just sub unity-ui-bugs and people can opt-in to bugs there
[17:43] <Saviq> mterry, ah you mean so that people can decide what they're subscribed to?
[17:44] <Saviq> sounds nice, we'll have to switch quite a bit of projects
[17:44] <Saviq> and make sure people know
[17:44] <mterry> Saviq: well I assume unity-ui-team is functional -- like we use that for LP permissions and what not.  If we are worried about bugspam to that team, we can use the existing opt-in team unity-ui-bugs.  (Though I don't know how anyone survives without heavy LP filtering anyway...)
[17:47] <om26er> When will application menus land in Unity8 ?
[17:50] <Saviq> om26er, under active work, some weeks out
[17:51] <om26er> Saviq, ok, are indicators also being worked on to be friendly on the desktop ?
[17:53] <om26er> another question: when will unity8 automatically scale on the desktop ? currently I have to add a environment variable
[17:56] <mterry> Saviq: it seems like unity-ui-team is already subscribed to most things.  In which case, the point of unity-ui-bugs is diminished.  The scripts might as well look at unity-ui-tea
[17:57] <Saviq> om26er, yes, pointer-friendly indicators are also under active work, will likely come before menus, as both need the same bits
[17:58] <Saviq> om26er, as for scaling we still need to decide a few things, especially wrt. how do clients request certain screen properties
[17:58]  * mterry goes afk
[17:59] <om26er> Saviq, thanks, a lot.
[23:49] <josharenson> Seeing a race in a test where a repeater says that its rendered (and the count is correct) but clicking a delegate isn't working sometimes... (a 1000 ms wait always fixes this). Anyone see anything like this?


[02:00] <gonyere> nobody willing to go where and help do what?
[02:01] <Unit193> Eat tacos, I'd think.
[02:01] <gonyere> lol
[02:01] <Unit193> (Sorry, taco obsession past week or two, dunno why.)  OLF, there was a call for talks.
[02:01] <gonyere> ahh. i ran a gnome booth there a couple times... fun, but not worth it by yourself.
[02:02] <jenni> h
[02:05] <Unit193> I can't do talks. :3
[02:09] <gonyere> why not?
[02:11] <Unit193> I don't do well in front of people, and even during prep I tend to presume things I shouldn't (in terms of people already knowing what I'm talking about, etc.)
[22:03] <yano> http://www.10tv.com/content/stories/2015/05/27/weather-alert-strong-storms-with-damaging-winds--hail-expected-tonight.html
[22:03] <jenni> [ WEATHER ALERT: Possible Strong Storms With Damaging Winds & Hail Tonight | WBNS-10TV Columbus, Ohio ] - https://j.mp/1QaTNbC
[22:11] <Unit193> Temp: 81 F (27 C) ~ Clear ~ Heat index: 82 F (28 C) ~ Humidity: 49% ~ Alert: Severe Thunderstorm Watch ~ Observed: Wed 27, 17:52


[01:08] <Kushiman> יש כאן מישהו?
[01:09] <Kushiman> Anyone here?
[01:10] <Kushiman> Nvm  I'll check in the morning
[01:10] <Kushiman> Good night