[00:34] <bobby> Anyone know why 3.7a5 isn't in the repositories anymore?
[00:35] <micahg> bobby: ?
[00:35] <bobby> 3.7a5... I can't find it in the repositories anywhere
[00:35] <micahg> bobby: what repo?
[00:36] <bobby> Daily build repository
[00:36] <bobby> It isn't there, where'd it go?
[00:36] <micahg> bobby: what release?
[00:36] <bobby> 3.7a5
[00:36] <micahg> bobby: no, Ubuntu release
[00:36] <bobby> Oh, 10.04
[00:36] <micahg> bobby: weird
[00:37] <micahg> it's there
[00:37] <bobby> I also tried Synaptic, wasn't there either
[00:37] <bobby> Really? Where?
[00:37] <micahg> bobby: firefox-3.7
[00:37] <bobby> Yeah, I just did a clean install and now can't find it
[00:37] <micahg> bobby: you need to add the PPA
[00:37] <bobby> I did
[00:37] <bobby> Nothing came up when I updated it though
[00:37] <bobby> I'm currently running 3.6.3
[00:37] <micahg> bobby: you mean it's missing or no updates
[00:37] <bobby> Yeah
[00:38] <micahg> bobby: no, it's a different pacakge
[00:38] <micahg> It's Minefield in the menu
[00:38] <bobby> Yeah, I know, it didn't load
[00:38] <micahg> bobby: what does apt-cache policy firefox-3.7 say, please use pastebin
[00:40] <bobby> Hang on, is 3.7 in a different repository now? I just did a clean install, and got it from the daily repository...
[00:40] <micahg> bobby: no, still in Ubuntu Mozilla Daily
[00:41] <BUGabundo>  *** 3.7~a5~hg20100506r41949+nobinonly-0ubuntu1~umd1 0
[00:41] <BUGabundo>         500 http://ppa.launchpad.net/ubuntu-mozilla-daily/ppa/ubuntu/ lucid/main Packages
[00:41] <micahg> bobby: yes
[00:41] <micahg> bobby: i've been at UDS so  I haven't had time to fix the dailies, they should resume normally next week
[00:42] <bobby> Oh okay, yeah I was looking there before...
[00:42] <bobby> Wait... That is Thunderbird lol
[00:43] <bobby> Oh yeah, so how is UDS? I've never been ;)
[00:43] <micahg> BUGabundo: it's early for you than me ATM :)
[00:43] <micahg> bobby: planning lots of great stuff
[00:43] <bobby> Wait... I have an idea!
[00:44] <bobby> Make firefox open in .000000000001 seconds!
[00:44] <micahg> bobby: that reminds me I need to fix the topic :)
[00:44] <bobby> :)
[00:44] <micahg> bobby: not going to happen, but FF4 should be much faster
[00:45] <bobby> What?
[00:45] <bobby> Oh yeah, I remember when we switched to Yahoo! for about a month
[00:45] <bobby> That was funny
[00:45] <BUGabundo> micahg: when do you expect FF4 to hit the repos?
[00:45] <micahg> BUGabundo: archive or PPA?
[00:45] <bobby> I think the alpha is supposed to be June (ish) from what I've heard
[00:46] <bobby> Not sure
[00:46] <BUGabundo> anywhere we can install it from
[00:46] <bobby> If I had to guess... It'll be something like nightly builds until October
[00:46] <micahg> BUGabundo: well, I think 3.7 is 4
[00:46] <bobby> No
[00:47] <bobby> 3.7 is 3.6.4
[00:47]  * micahg hasn't had time to keep up with blog posts
[00:47] <micahg> bobby: no
[00:47] <bobby> It isn't?
[00:47] <BUGabundo> NO
[00:47] <bobby> I read a blog post saying it was...
[00:47] <BUGabundo> na ah
[00:47] <bobby> No, I saw some slideshow confirming it...
[00:47] <bobby> Mozilla released it at some press conference
[00:47] <micahg> I meant the current builds
[00:48] <micahg> the firefox-3.7 codebase is what will become 4
[00:48] <bobby> oh oh
[00:48] <bobby> I'm not sure
[00:48]  * micahg should read belzner's blog
[00:48] <bobby> lol
[00:48] <bobby> I'm really looking forward to the new interface, is it looking anything like the mockups?
[00:48] <bobby> 4.0 Ubuntu mockups were EPIC
[00:49] <bobby> Oh no, that was the 3.7 mockups I think
[00:49] <micahg> not yet
[00:49] <BUGabundo> yeah
[00:49] <BUGabundo> they need to trim it
[00:49] <bobby> Yeah, the mockups were insane
[00:49] <BUGabundo> its toooo big
[00:49] <BUGabundo> I've trimed mine the most I can
[00:49] <bobby> Agreed, Mozilla also needs to decide what to do with the new home tab
[00:49] <BUGabundo> and I go to the extreme of leaving *just* the site
[00:49] <BUGabundo> nothing else
[00:49] <BUGabundo> a semi-fullscreen / quiosk mode
[00:50] <BUGabundo> I do F11, then super+f11
[00:50] <BUGabundo> LOL
[00:50] <fta> BUGabundo, in the 4.0 mockups, http:// is gone ;)
[00:50] <BUGabundo> its full screen without being full screen
[00:50] <micahg> so, OOPP was the big deal for 3.7 and that'll be in 3.6.4, so the rest of 3.7 will be 4.0
[00:50] <BUGabundo> fta: OH MAN :(
[00:50] <bobby> Really?
[00:50] <bobby> Wow...
[00:50] <bobby> I didn't hear about that
[00:51] <fta> once trunk move to 4.0, the bot will stop producing dailies
[00:51] <bobby> Well, of course
[00:51] <micahg> :(
[00:51] <bobby> https://wiki.mozilla.org/Firefox/3.7_Linux_Theme_Mockups
[00:51] <bobby> Loving it, loving it, loving it
[00:52] <bobby> One thing for Ubuntu, that I really want to see, is an epic speed boost
[00:52] <bobby> I'm liking the new... What's it called?
[00:52] <micahg> it'll be chromofox or firefium
[00:52] <bobby> For Netbooks and st00f
[00:52] <BUGabundo> unity
[00:52] <BUGabundo> its FAST
[00:52] <bobby> Yeah that
[00:52] <fta> i mean, until i update its configuration, but the package would need to be updated first.. tons of renaming and even more transition packages
[00:52] <BUGabundo> I admit it
[00:52] <bobby> I heard it was very buggy though
[00:52] <BUGabundo> not that much
[00:52] <BUGabundo> it works
[00:52] <BUGabundo> but I miss Compiz
[00:53] <bobby> I can't live without compiz
[00:53] <bobby> Wobbly windows <3
[00:53] <micahg> fta: I know, it's ok
[00:53] <bobby> Today I booted into Windows 7 for the first time in 3 weeks, just to update it and get Portal for free on Steam :)
[00:54] <bobby> Oh yeah, 3.7a5 failed to build it says on the daily build page...
[00:54] <bobby> https://wiki.mozilla.org/Firefox/Roadmap
[00:55] <bobby> There we go, that answers all questions about the roadmap :)
[00:55] <micahg> bobby: that's outdated
[00:55] <BUGabundo> "Nushio: and I'm betting that unlike chrome/ium, there'll be an option in about:config to enable http"
[00:55] <bobby> yeahh
[00:55] <bobby> Oh yeah, just saw updated Jan :P
[00:55] <bobby> Ah crap
[00:56] <bobby> GNOME is frozen
[00:56] <bobby> All I have is the text thing, and can't click on any windows
[00:56] <bobby> All I can do is type in here :(
[00:56] <bobby> Okay, nvm, fixed :P
[00:56] <bobby> Hate when that happens
[00:56] <bobby> O...M...G...
[00:57] <bobby> I was just looking through my drawer, and found my Windows 98 recovery disk for my ancient PC
[00:57] <bobby> OMG!
[00:57] <bobby> Netscape 4.0!...
[00:57]  * BUGabundo slaps bobby silly
[00:57] <bobby> I wonder...
[00:57] <bobby> Virtualbox time!
[00:58] <bobby> Oh yeah, anybody know the release date for 3.6.4?
[00:59] <micahg> bobby: delayed
[00:59] <bobby> Ah dang it... It's true?
[01:00] <bobby> Too bad
[01:01] <bobby> Anybody tried the Shell for GNOME yet?
[01:01] <micahg> bobby: a couple weeks
[01:01] <bobby> oh
[01:01] <micahg> bobby: you can test from security PPA
[01:01] <micahg> https://edge.launchpad.net/~ubuntu-mozilla-security/+archive/ppa
[01:02] <bobby> W00t!  a new W7 was my idea commercial! Love making fun of MS's horrible marketing campaigns :)
[01:02] <bobby> Wait, this is 3.7?
[01:02] <BUGabundo> bobby: did you take *TWO* expressos tonie?
[01:02] <bobby> No... Only 3 cokes...
[01:02] <bobby> Oh 3.6.4 got it
[01:02] <BUGabundo> 1l each ?
[01:04] <bobby> Okay, question:
[01:04] <micahg> bobby: that's not the final version but OOPP works
[01:04] <micahg> in most cases
[01:04] <bobby> How many builds are there of FF?
[01:04] <micahg> bobby: what do you mean?
[01:04] <bobby> I know there is: 3.7a5, 3.6.4 testing, 3.6.5pre, anything else?
[01:05] <micahg> not ATM
[01:05] <micahg> for Lucid at least
[01:05] <bobby> Oh, m'kay
[01:06] <bobby> Anyone see the Chrome 6 preview? "30-50% faster"
[01:08] <BUGabundo> erk
[01:08] <BUGabundo> I'm using it !
[01:08] <BUGabundo> 6.0.402.0 (47105) Ubuntu
[01:08] <bobby> Link pl0x?
[01:08] <bobby> I heard that Flash and Java support are very limited ATM though
[01:08] <micahg> bobby: chromium daily PPA
[01:09] <bobby> Thanks
[01:09] <BUGabundo> daily ppa ?
[01:10] <bobby> ppa:chromium-daily/ppa
[01:10] <bobby> I <3 open source :)
[01:12] <bobby> OMG, that was as fast as 3.7a5! nice!
[01:13] <bobby> I still like Firefox better though, mainly the addons and reliability :)
[01:14] <BUGabundo> welllllll
[01:14] <BUGabundo> nite every1
[01:15] <micahg> night BUGabundo
[01:16] <bobby> nite
[01:20] <bobby> I'm actually kind of annoyed at Firefox ATM...
[01:20] <bobby> Too many personas to choose from :(
[01:30] <DASPRiD> how about, choose none :P
[01:30] <DASPRiD> they make the browser ugly imho :)
[01:32] <bobby> Really? I can't live without them
[01:35] <DASPRiD> you have a very strange live, little buddy
[01:38] <bobby> Indeed... School, Ubuntu and food is about it :P
[01:38] <bobby> Not really, but you get the idea: open source FTW
[18:22] <cwillu_at_work> when a download completes, I get a notification bubble that pops up over and over again for a couple minutes;  is that just me, or does that happen to everyone? :p


[00:58] <wendar> shadeslayer: sweet!
[00:58] <wendar> shadeslayer: I got mine flashed (using your helpful tips), this should make updates much easier :)
[01:00] <wendar> shadeslayer: did this fix the issues you had with your transformer too?
[11:20] <Tm_T> agateau: rock'n'roll (:
[11:48] <Ezim> hi channel
[11:49] <Ezim> I wonder if we can get this for 12.10: http://kde-apps.org/content/show.php/Root+Actions+Servicemenu?content=48411
[11:49] <Ezim> by default
[13:12] <ScottK> Ezim: I don't think it's appropriate by default as that's not something most users would typically use.  Also, since we use kdesudo instead of kdesu, it likely would need some adaptation to work here.
[13:15] <Ezim> ScottK, okey. thats true. only suggestion. :)
[13:15] <ScottK> No problems with suggestions.
[15:59] <BluesKaj> Hey folks
[16:13] <bambee_> hi, I've a question: according to "dpkg -L kmix" libkdeinit4_kmix.so is installed in /usr/lib/kde4/libkdeinit. However according to kmix/debian/kmix.install it is installed in /usr/lib. I install kmix from master, so I would like to overwrite these files (in order to use the ones from master)
[16:18] <Ezim> http://www.omgubuntu.co.uk/2012/06/humble-bundle-devs-talk-gaming-on-linux
[16:18] <Ezim> :)
[16:49] <Riddell> bambee_: spooky
[16:50] <bambee_> ?
[16:50] <Riddell> bambee_: the moved kdeinit files
[16:50] <Riddell> I've not noticed that before but it'll be some cleverness from debian-qt-kde.mk
[16:51] <Riddell> you can just delete them though
[16:51] <Riddell> they just help speedup startup
[16:52] <apachelogger> Mamarok: http://www.youtube.com/watch?v=sTONayew73Y
[16:52] <apachelogger> happened to me ^^
[16:52] <bambee_> I will probably use neon, it's much cleaner :)  (use a separated prefix for development)
[16:52] <apachelogger> bambee_, Riddell: our dh magic does that
[16:52] <bambee_> really ? nice tool
[16:53] <apachelogger> no clue why upstream wants to have that kdeinit libs in the main lib dir
[16:53] <apachelogger> s/that//
[16:53] <kubotu> apachelogger meant: "no clue why upstream wants to have  kdeinit libs in the main lib dir"
[17:16] <apachelogger> shadeslayer: the uds app api stuff is in master already
[17:16] <apachelogger> primarily core/api.js and core/JsonHandler.qml
[17:16] <apachelogger> used in harmattan/SplashPage.qml only though
[17:17] <apachelogger> though I suppose that should give the general idea
[17:17] <apachelogger> essentially you use the jsonhandler to communicate with the api
[17:17] <apachelogger> and the handler spits out models
[17:19] <apachelogger> http://projects.developer.nokia.com/uds/browser/qml/core/JsonHandler.qml
[17:35] <Ezim> hi spacebug-
[17:35] <spacebug-> hello
[17:35] <spacebug-> ;)
[17:35] <Ezim> :) you can ask your question here and I hope they can help you out
[17:41] <spacebug-> I have problems with my sound playing like double speed. This happens first time I open "audio setup" in kmix while playing sound and it also happens every time the root user is trying to play sound when my normal user plays sound. Sound card is 'Creative Labs CA0106 Soundblaster' and I'm using Gstraeamer as backend though same thing happens if I try VLC backend so probobly not there the issue is. (12.04 system)
[17:44] <apachelogger> #kubuntu for support please
[17:44] <spacebug-> ok
[18:25] <yofel> home sweet home :)
[18:28] <debfx> where have you been?
[18:28] <Ezim> hmm I found kmix bug. that crasches the sound.
[18:28] <Ezim> if I take the volume up/down several times with kmix
[18:28] <Ezim> the sound start to sound weird
[18:29] <Ezim> https://bugs.launchpad.net/ubuntu/+source/kdemultimedia/+bug/963895
[18:30] <debfx> that bug says "fixed in 4.8.3"
[18:31] <Ezim> it is not really kmix that crashes it is sound that makes weird noice
[18:32] <yofel> debfx: trip to berlin (that's why I did almost nothing this week)
[18:33] <Ezim> will try see if veromix goes crazy on me. damn this bug.
[18:34] <BluesKaj> Ezim, it's an old rule in audio , leave the input volume at 80% or so and control the volume at the amplifier , which in most cases is the volume control on your speaker system
[18:34] <debfx> yofel: oh nice. so I can hand 4.8.4 over to you now? :P
[18:36] <yofel> debfx: I wouldn't mind if you kept working on it as well :P
[18:36] <Ezim> BluesKaj, :) okey... but this bug is annoying.
[18:38] <BluesKaj> Ezim, yes , using the speaker volume ctrl is one way to avoid the problem unti it's fixed
[18:38] <debfx> why haven't we fully automated the process anyway?
[18:38] <Ezim> BluesKaj, brb... will test stuff
[18:42] <yofel> debfx: because we didn't really manage to make a plan on how to do that yet. At least shadeslayer will have plenty of time soon ;)
[18:48] <shadeslayer> yus :D
[18:48] <shadeslayer> that's already at the top of my TODO list
[18:50] <apachelogger> shadeslayer: on top of your todo list should be "find out what takes up most developer time"
[18:50] <shadeslayer> apachelogger: that's there too
[18:51] <shadeslayer> along with fixing the UDS app ;P
[18:55] <shadeslayer> Riddell: have you seen the post about Fedora and EFI?
[19:06] <shadeslayer> yofel: debfx did you guys know about this : https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-daily
[19:07] <yofel> nope
[19:07] <shadeslayer> now you do
[19:07] <Adityab> What version of Webkit comes with the latest QtWebkit (2.2.1)?
[19:07] <shadeslayer> ;)
[19:07] <Adityab> And, is there a difference between the Webkit that comes with QtWebkit and the one that comes with Chromium?
[19:08] <shadeslayer> Adityab: QtWebkit vs Chromium ... I think so
[19:08] <shadeslayer> because they use V8 and I know that QtWebkit doesn't use V8 yet
[19:08] <Adityab> that's the Js engine
[19:08] <Adityab> I'm asking about webkit
[19:09] <shadeslayer> ah, as in version of webkit ... no idea
[19:09] <Adityab> the renderer, specifically :)
[19:10] <apachelogger> qtwebkit has a snapshot from webkit, so does chromium
[19:15] <Riddell> shadeslayer: nope, should I?
[19:16] <shadeslayer> Riddell: yep, remember our discussions about having 2 separate images, one for Mac and one for standard PC's ?
[19:16] <Riddell> yes
[19:17] <shadeslayer> the separate Mac ISO's will make sense only if we can get our Images to boot under EFI mode
[19:17] <Riddell> yofel: that qt5-edgers is a guy called zoltan who is wanting to help with qt 5 packaging
[19:18] <jussi> claydoh: ping
[19:18] <yofel> ah
[19:18] <claydoh> jussi: hi
[19:18]  * yofel wonders how that PPA managed to get armel builds
[19:20] <apachelogger> yofel: canonical only access
[19:20] <yofel> ah well
[19:23] <Riddell> yofel: canonical powahs
[19:36] <Ezim> hmm the bugs seems to be kubuntu specific
[19:36] <Ezim> I have no problem with mageia on my usb
[19:44] <Ezim> any one?
[19:52] <Ezim> apachelogger, online?
[19:53] <apachelogger> no
[19:53] <Ezim> :)
[19:54] <Ezim> apachelogger, I have problem with sound. kmix/volume high/down. repeating will make audio sound on youtube or amarok/clementine weird.
[19:54] <Ezim> I tested mageia on my usb and no such problem over there
[19:54] <Ezim> :(
[19:55]  * apachelogger blames pulseaudio
[19:55] <Ezim> so this must be kubuntu specific bug.
[19:55] <apachelogger> Ezim: define weird though
[19:55] <apachelogger> Ezim: that resoning is flawed btw
[19:55] <apachelogger> unless the software versions are the same
[19:55] <Ezim> apachelogger, also mageia comes with pulseaudio.
[19:56] <Ezim> apachelogger, one friend had exactly same problem with kubuntu but not ubuntu.
[19:56] <apachelogger> could be a kmix bug then
[19:57] <apachelogger> mageia doesn't have kmix 4.8.3 IIRC
[19:57] <apachelogger> that is to say... since I know the kmix code I find it entirely likely that it is kmix' fault
[19:58] <Ezim> apachelogger, maybe it is kde 4.8.3 bug. I did not notice it with 4.8.2
[19:59] <Ezim> apachelogger, it is driving me crazy... :(
[19:59] <Ezim> also veromix does not help
[19:59] <Ezim> or change phonon backend from gstreamer to vlc
[20:00] <Mamarok> apachelogger: don't worry, that happens to a lot of people
[20:01] <Ezim> Mamarok, same for you?
[20:01] <Mamarok> Ezim: no, my reply is about something else
[20:01] <Ezim> Mamarok, :) sorry then.
[20:02] <apachelogger> Ezim: veromix has the issue too?
[20:02] <Ezim> apachelogger, yes.
[20:02] <apachelogger> sounds more like a bug in pulseaudio/alsa then
[20:02] <Ezim> I removed kmix widget and added veromix. changed fn volume keys to veromix. same there.
[20:03] <Ezim> apachelogger, sound goes cracky when I do it or how I should descripe it.
[20:04] <Ezim> hmm maybe the big difference between mageia and kubuntu is that mageia comes with pulseaudio 2
[20:05] <Ezim> I just read the release not for there release
[20:05] <Ezim> *note
[20:07] <Ezim> apachelogger, then I do not really get why the same thing works in ubuntu for my friend and exactly same issue that I have is in kubuntu
[20:07] <apachelogger> *shrug*
[20:12] <Ezim> :(
[20:17] <Ezim> apachelogger, any idea? can I debug it?
[20:18] <apachelogger> Ezim: #pulseaudio might know
[20:18] <apachelogger> supposedly the pulse daemon should see why such behavior appears
[20:21] <Ezim> apachelogger, hmm... pulseaudio is the same for ubuntu and kubuntu. can this be phonon bug?
[20:21] <Ezim> kmix?
[20:21] <Ezim> kde 4.8.3
[20:22] <apachelogger> not if veromix has it too
[20:22] <apachelogger> and I'll exclude phonon seeing as one of the pulseaudio masters is maintaining the phonon pulse integration :P
[20:22] <Ezim> :( oki thx anyway...
[20:24] <Ezim> I really do not want to make new installation of any distro... tired
[20:51] <apachelogger> yofel: can you give me a list of what you do to update a package for a new kde release?
[20:53] <yofel> apachelogger: I tried to put that on https://wiki.kubuntu.org/Kubuntu/Ninjas/ReleasePackaging - Need to review that though, but it's roughly what I do
[20:54] <jussi> Hrm, I had a thought - one of the biggest barriers to entry to helping us out is getting your environment set up, pbuilder, keys, and everything else
[20:55]  * apachelogger is not thinking about barriers :P
[20:55] <yofel> I started a new page for ninja specific pbuilder setup once, but it's currently more of a information dump
[20:55] <apachelogger> the biggest one there is dpkg itself anyway :P
[20:55] <yofel> had other priorities
[20:56] <yofel> for environment setup you can mostly use the ubuntu one from dholbach, and there is a wiki page for the key setup somewhere I believe
[20:56] <apachelogger> yofel: other than actual building, what do you think takes up most time?
[20:56] <yofel> we should probably have a page with links to those though
[20:56] <apachelogger> well, and downloading ^^
[20:56] <Ezim> :( pulseaudio 2 did not work also
[20:57] <BluesKaj> Ezim, have you tried pavucontrol?
[20:57] <Ezim> even when I kill kmix and do not make it load at startup
[20:57] <Ezim> it does not work.
[20:58] <yofel> apachelogger: really anything that's manual. i.e.: log review, symbol update (that could be automated), symbol review (that not), fixing patches, updating .install files
[20:58] <Ezim> BluesKaj, I tried veromix. problem with that also.
[20:59] <apachelogger> yofel: mhhh, automated symbol update promotes sloopy or no review
[20:59] <BluesKaj> Ezim, when you daid, "it does not work" ..were you referring to pavucontrol?
[20:59] <BluesKaj> sai9d
[20:59] <Ezim> https://bugs.kde.org/show_bug.cgi?id=301069
[20:59] <Ezim> BluesKaj, veromix is the same thins as pavucontrol.
[21:00] <yofel> apachelogger: pkgkde-symbolshelper dumps any MISSING symbols to stdout. So you don't really need the log to see those
[21:00] <apachelogger> aye
[21:00] <BluesKaj> Ezim, is it ?
[21:00] <apachelogger> log parsing needs doing anyway
[21:00] <apachelogger> also for cmake deps
[21:00] <yofel> me and shadeslayer did some unfinished work there
[21:00] <apachelogger> though for that to work reliably in the long run upstream needs a policy on that
[21:00] <yofel> lying around in some github gist where it doesn't belong
[21:01] <Ezim> BluesKaj, is what?
[21:01] <apachelogger> http://gobarbra.com/hit/new-bd5866b23becaebabc1559f244c81a8d
[21:02] <yofel> ^^
[21:03] <BluesKaj> Veromix is a mixer for the Pulseaudio sound server , pavucontrol is somewhat differnt , but if you don't want to try it that's your call, Ezim
[21:04] <Ezim> BluesKaj, I have pavucontrol installed
[21:04] <Ezim> BluesKaj, what should I do with pavucontrol?
[21:06] <Ezim> BluesKaj, you mean I should try take volume up/down instead with pavucontrol all the time?
[21:09] <BluesKaj> Ezim, there is another option , that is to remove pulseaudio and veromix and pavucontrol etc altogether and let alsa and kmix run your audio ..you might not have any audio on websites tho ...depends on how alsa integrates with your soundcard/driver
[21:11] <Ezim> BluesKaj, I think the bug accured with kde 4.8.3
[21:11] <Ezim> did not notice anything before that
[21:11] <Ezim> so what happend to kmix or phonon with 4.8.3 I do not know
[21:11] <BluesKaj> Ezim, what's your soundcard ?
[21:12] <BluesKaj> the bug is most likely with pulseaudio
[21:13] <Ezim> BluesKaj, http://paste.kde.org/491894/
[21:13] <apachelogger> Ezim: nothing happened to phonon because phonon is not part of KDE SC and thus released at different times :P
[21:14] <Ezim> BluesKaj, I just tried pulseaudio 2 and same thing there.
[21:14] <shadeslayer> yofel: apachelogger this: https://gist.github.com/2162326 ?
[21:14] <Ezim> apachelogger, okey then what is the problem?
[21:14] <yofel> yeah, that one
[21:14] <yofel> the # probably? was right btw. There's at least one case ignored currently
[21:16] <BluesKaj> Ezim, well ,try it without pulse , no need to purge , just remove it
[21:17] <Ezim> BluesKaj, I need pulse to configure my mic and stuff like that.
[21:17] <BluesKaj> Ezim, I ran without pulseaudio for yrs just using my onboard sound
[21:18] <BluesKaj> alsamixer can configure your mic
[21:18] <Ezim> BluesKaj, sound is no issue, the problem is mic... BluesKaj I have tried alsamixer... anyway that would be my last option
[21:20] <BluesKaj> heh , that would be my first ...I'd love to get rid of pulseaudio if I didn't need webaudio
[21:34] <Ezim> BluesKaj, it seems to work now after removing pulseaudio.
[21:34] <Ezim> but thats weird.
[21:34] <apachelogger> JontheEchidna: http://imageshack.us/f/838/image4396.png/
[21:34] <Ezim> I have had during all my years buntu user problem with pulseaudio
[21:34] <Ezim> I still think the bug is on the kde side
[21:35]  * apachelogger points out that pulseaudio must not misbehave if a client does stupid things
[21:35] <apachelogger> so it may well be a bug in pulse and kmix, in which case both need fixing, but at any rate pulse needs fixing
[21:36] <Ezim> apachelogger, +1
[21:36] <Ezim> I can not reproduce it now...
[21:36] <Ezim> thats good.. but I want my pulseaudio back :)
[21:37] <shadeslayer> apachelogger: mockup?
[21:37] <apachelogger> u mock me up
[21:37] <shadeslayer> also, the Kubuntu G+ account makes some amazing artwork, any idea who's operating that ?
[21:37] <apachelogger> Ezim: report bugs then
[21:37] <apachelogger> shadeslayer: I do belive G+ is a social network as such you could simply ask there :P
[21:38] <apachelogger> more social I say
[21:38] <shadeslayer> ofcourse, just thought maybe it was someone here
[21:38] <apachelogger> not that I am aware of
[21:39] <shadeslayer> https://plus.google.com/s/Kubuntu
[21:39] <apachelogger> yofel: you know what I would love to do ... initial upgrade all the packages on a server
[21:39] <yofel> ?
[21:40] <Ezim> next problem I can here sound with my headphone but not from speakers
[21:40] <apachelogger> get all the sources on the server, update changelog and deps, then try to build according to dep graph
[21:40] <shadeslayer> apachelogger: actually, I have one better idea
[21:40] <yofel> that'll fail on the first failed patch
[21:40] <shadeslayer> but that will require a AWS instance for every package
[21:40] <apachelogger> yofel: assuming the patch is in a root dependency
[21:41] <apachelogger> so if it fails, a packager gets the relevant source, fixes it up and pushes
[21:41] <apachelogger> triggering a full rebuild of the entire tree
[21:41] <apachelogger> rinse and repeat until all is built
[21:41] <yofel> great idea - enjoy implementing it
[21:41] <apachelogger> I had that implemented half the way with the bat tools already :P
[21:42] <apachelogger> as always, implementation is not the problem
[21:42] <apachelogger> resources are
[21:42] <shadeslayer> I would really like to implement everything with bzr and recipes
[21:42] <debfx> we could do that in a ppa
[21:42] <apachelogger> as the building needed to be rather quickish
[21:42] <apachelogger> debfx: too long a wait with long build chains
[21:42] <apachelogger> though yes, in theory lunchpad should be used
[21:42] <shadeslayer> *nod*
[21:43] <apachelogger> of course that would require our packages to get built within a couple of minutes
[21:43] <apachelogger> (build start that is)
[21:43] <shadeslayer> recipes support revisions numbers, so we just want the relevant rev no.
[21:43] <yofel> not using a PPA requires a seperate server
[21:43] <apachelogger> for which lunchpad as too few slaves
[21:43] <shadeslayer> apachelogger: doesn't matter, we can initiate the build once we know the relevant rev no. for each package
[21:43] <apachelogger> yofel: you'd want a separate server eitherway
[21:43] <apachelogger> yofel: that can all be hyperthreaded
[21:43] <shadeslayer> so you could initiate builds a week before release
[21:44] <apachelogger> dep resolution is const, from that point on everything except build ignition can be done in parallel
[21:44] <shadeslayer> apachelogger: exactly, which why my idea involves multiple AWS instances
[21:44] <shadeslayer> you can queue AWS isntances one after the other
[21:45] <apachelogger> if you get the instances :P
[21:45] <shadeslayer> ofcourse :P
[21:45] <apachelogger> I mean, let's not fool ourselfs
[21:45] <Ezim> hmm... sound headache
[21:45] <shadeslayer> apachelogger: right, financial constraint :)
[21:45] <apachelogger> running the builds on a node architecture will be like cloning soyuz
[21:45] <apachelogger> or OBS
[21:45] <shadeslayer> ofcourse, you can also pause a entire AWS instance till it's processed in the queue
[21:45] <apachelogger> and I am not convinced that makes much sense
[21:46] <yofel> well, we could build our own OBS instance if we have a server
[21:46] <shadeslayer> so that should reduce costs, but still will cost alot
[21:46] <Ezim> BluesKaj, no my speakers do not work... :)
[21:46] <BluesKaj> Ezim, do you have sound on youtube now ?
[21:46] <yofel> needs someone's time to do
[21:46] <debfx> apachelogger: the waiting time usually isn't that long in the ninjas ppa
[21:46] <Ezim> BluesKaj, yes. but no sounds from speakers...
[21:46] <apachelogger> if we had a great number of root nodes on the same level then paralell building makes sense
[21:46] <apachelogger> but luckily that is not the case
[21:46] <apachelogger> debfx: depends on when you upload
[21:46] <shadeslayer> I have no idea how to contact the controllers of the kubuntu page
[21:46] <yofel> apachelogger: define "when"?
[21:47] <apachelogger> time
[21:47] <apachelogger> shadeslayer: controllers?
[21:47] <shadeslayer> apachelogger: s/controllers/owners
[21:47] <apachelogger> yofel: oh, btw, about OBS ... we'd then have to fix OBS' dpkg support
[21:47] <yofel> shadeslayer: kubuntu.org? canoncial sysadmins I believe - forget it
[21:47] <apachelogger> which would surely be appreciated though ^^
[21:47] <shadeslayer> yofel: nope, I'm talking about : https://plus.google.com/s/Kubuntu
[21:47] <yofel> apachelogger: OBS's dpkg support is fine, the apt archive URL's are a bit weird
[21:48] <yofel> ah
[21:48] <apachelogger> shadeslayer: wirte a post
[21:48] <apachelogger> yofel: no it is not :P
[21:48] <shadeslayer> that's the last resort :P
[21:48] <apachelogger> yofel: check out how it boostraps
[21:48] <apachelogger> has nothing todo with what deboostrap does
[21:48] <apachelogger> as it does not use deboostrap
[21:48] <jussi> fixing obs's dpkg support would be a good thing generally though...
[21:48] <apachelogger> though it should really
[21:48] <apachelogger> jussi: that's what I am saying
[21:48] <debfx> it should be fairly easy to implement this with PPAs: we'd just need a script the fetches the sources, does some modifications and uploads
[21:48] <yofel> ah, haven't look that deep
[21:48] <apachelogger> just pointing out that this needs doing
[21:48] <yofel> *looked
[21:49] <debfx> and another one that retries builds that failed because of missing dependencies
[21:49] <apachelogger> otherwise you'd not know whether a build in OBS would actually produce the same result in soyuz
[21:50] <shadeslayer> kdone
[21:50] <apachelogger> also
[21:51] <apachelogger> yofel: there is this ever so terrible problem that OBS is designed without folder support
[21:51] <yofel> side note: can you dump the todo list we're doing right now on a pad somewhere?
[21:51] <shadeslayer> I wish soyuz supported rebuilding a package once it detects a build dep was updated
[21:51] <yofel> urgh
[21:51] <apachelogger> yofel: todo list?
[21:51] <apachelogger> shadeslayer: OBS does that, for rpm anyway :P
[21:51] <shadeslayer> apachelogger: for automation and stuff that you're discussing right now ;)
[21:52] <apachelogger> that has limits to scalability though ^^
[21:52] <apachelogger> in fact it rebuilds all things depending on a package, regardless of whether the dependees failed
[21:52] <shadeslayer> apachelogger: yes, but what about debs, that's all we care about :P
[21:52] <apachelogger> not quite sure why it does that
[21:52] <apachelogger> perhaps to prevnet non-ABI dependent issue
[21:52] <yofel> auto-rebuilds would be great, but if we do that for neon we'll brind the datacenter down. So rather unreasonable
[21:52] <yofel> *bring
[21:52] <apachelogger> shadeslayer: haven't looked into it
[21:52] <shadeslayer> unless you want to make Kubuntu a RPM based distro
[21:53] <yofel> !yum
[21:53] <apachelogger> shadeslayer: I mean, at the end of the da it would be about exposing the relevant information to the obs scheduler
[21:53] <shadeslayer> yofel: haha
[21:53] <apachelogger> which is really just a matter of implementation
[21:53] <shadeslayer> *nod*
[21:53] <shadeslayer> what is OBS implemented in?
[21:53] <shadeslayer> please don't say python
[21:53] <yofel> ruby IIRC
[21:53] <apachelogger> perl
[21:53] <apachelogger> nah
[21:53] <apachelogger> only the frontend is rails
[21:53] <yofel> really perl?
[21:53] <yofel> ah
[21:53] <shadeslayer> heh
[21:53] <apachelogger> the actual backend shit is perl
[21:54] <yofel> perl is ~fine
[21:54] <apachelogger> beautiful perl as I might add
[21:54] <yofel> better than php at least
[21:54] <apachelogger> as if it was not enough to be perl :P
[21:54] <shadeslayer> well .. I have 0 idea about perl
[21:54] <shadeslayer> never written a single line in perl
[21:54] <apachelogger> shadeslayer: the secret to perl is codign by proxy
[21:54] <apachelogger> proxy = google :P
[21:54] <shadeslayer> so yay, not my responsibility to fix OBS
[21:54] <yofel> shadeslayer: a language full of $variables, @'s and hashes
[21:54] <shadeslayer> funky
[21:55] <apachelogger> it is a madman's prn really
[21:55] <shadeslayer> you mean it's perfect for you
[21:55] <apachelogger> no, you know, I like nice looking things
[21:57] <shadeslayer> ;)
[21:59] <apachelogger> ohohoh
[21:59] <apachelogger> yofel: who uploads the packages once done?
[21:59] <apachelogger> and how does that happen?
[22:01] <yofel> bzr up, review if done by someone else, bzr builddeb -S, another rebuild if unsure, dput
[22:01] <yofel> and uploads are done by whoever can upload and has time
[22:02] <yofel> ppa copies usually by me
[22:02] <apachelogger> so that person also needs to build the source again
[22:02] <apachelogger> why that needs fixing
[22:02] <yofel> and I have a script for that, so it's trivial
[22:02] <apachelogger> yofel: is that public?
[22:02] <yofel> kopypackages in kubuntu-dev-tools
[22:03] <apachelogger> I thought that copies on lunchpad?
[22:03] <debfx> so are we going to create bzr branches for SRUs or just "fetch from ppa and upload"?
[22:03] <yofel> uh, I said for PPA's
[22:04] <apachelogger> ah, missed that
[22:04] <yofel> debfx: we always did latter
[22:04] <apachelogger> so bzr->archive still needs a resolution
[22:04] <apachelogger> debfx: branching seems like an unnecessary overhead for SRUs
[22:05] <apachelogger> exception being kde-l10n which gets branched per series for some reason I do not recall :P
[22:05] <apachelogger> though I do remember having thought at least twice that we need to do it, so I assume there is deeper meaning to it ^^
[22:05] <debfx> do we have an easy way to download packages from the ninjas ppa? something like pull-ninjas-source?
[22:05] <yofel> you made the script error out if the bzr stuff is not committed on launchpad?
[22:06] <apachelogger> debfx: what for?
[22:06] <apachelogger> ninja must always be in sync with bzr
[22:06]  * yofel just uses apt-get source
[22:06] <apachelogger> and when you upload you really want to build the source from bzr+tar
[22:07] <yofel> + bzr builddeb downloads the tar itself as long as it can find it
[22:07] <apachelogger> yofel: does it do that form ninja?
[22:07] <yofel> as long as you have the deb-src for ninjas, yes
[22:07] <debfx> I think we should have branches for SRUs so the process for SRUs and uploads to the dev release follows the same process
[22:07] <apachelogger> yofel: cool
[22:08] <yofel> not sure if it needs the deb line too, I have both plus an apt pin
[22:08] <apachelogger> debfx: yes, if it were sufficiently automated
[22:09] <apachelogger> there is however one downside to that
[22:09] <apachelogger> you'd have to review the bzr history prior to SRU changes
[22:09] <yofel> you could probably make kgetsource auto-create the branch if you're building for a stable release.
[22:09] <apachelogger> as to avoid someone throwing in random changes that get picked up
[22:10] <apachelogger> yofel: first we need a naming policy for series branches ^^
[22:10] <yofel> append the series? That's what we do for l10n
[22:10] <apachelogger> -series
[22:10] <apachelogger> or .series
[22:11] <apachelogger> cuz seeds are .series
[22:11]  * apachelogger doesn't like it tho
[22:11] <yofel> l10n is -series
[22:11] <apachelogger> mhh
[22:28] <debfx> hm but how do we run list-missing in the ppa?
[22:29] <yofel> make pkg-kde-tools invoke it automatically maybe? Would currently require cdbs though
[22:32] <apachelogger> yofel: we can just steal it and put it in a shell script or somesuch ^^
[22:34] <yofel> did someone change the admin password for kubuntu.org?
[22:35] <apachelogger> its 123
[22:35] <apachelogger> yofel: seems like it
[22:35] <apachelogger> Riddell: ^
[22:35] <apachelogger> also
[22:35]  * apachelogger sends kisses
[22:42]  * apachelogger really thinks plasma needs a new menu
[22:45] <debfx> ok, so here is a script that does the initial ppa uploads for SRUs: http://paste.kde.org/491936/
[22:47] <apachelogger> debfx: shouldn't be hardcoded
[22:47] <apachelogger> kdesc
[22:47] <debfx> yeah and kdesc != gwenview ;)
[22:48] <debfx> we also need a log analyzer that parses cmake output, symbol diff, and list-missing
[22:48] <debfx> and a place where we can run lintian on all the packages
[22:49] <apachelogger> bringing us back to my ultimate scenario of having one central service to control that stuff :P
[22:50] <apachelogger> debfx: cmake needs discussion with upstream
[22:50] <apachelogger> in particualr they need to explicitly mark cmake information using reliable formats for parsing
[22:51] <apachelogger> also that is a pain in the butt with lunchpad because you have to query all the time to see if a build finished so you can get the log
[22:51] <debfx> well just the plain cmake output for manual review would be enough for now
[22:51] <apachelogger> if you can get hte log at all that is
[22:51] <debfx> yes, you can get the log
[22:51] <apachelogger> debfx: you cannot reliably identify the beginning and end of that either
[22:51] <apachelogger> so we'd have to digg into cmake
[22:52] <apachelogger> ultimately we'd have markers for cmakestart, cmakeend, and kdeinfostart, kdeinfoend
[22:52] <yofel> feel free to take ideas from https://gist.github.com/2162326
[22:52] <apachelogger> yofel: that aint reliable unfortunately
[22:52] <yofel> well, I made it too tight
[22:52] <debfx> it starts with dh_auto_configure and ends with dh_auto_build
[22:52] <apachelogger> if it were less tight it would be less reliable :P
[22:53] <yofel> that too
[22:53] <apachelogger> debfx: do we get that in the log?
[22:53] <debfx> yes
[22:53] <apachelogger> yofel: so what we need to do is ask upstream to simply add a line to print before and after their output
[22:53] <apachelogger> something unique
[22:53] <apachelogger> that does not change
[22:53] <yofel> the SUMMARY is reliably parseable
[22:53] <apachelogger> or we do it ourselfs by overloading theirmodule
[22:54] <apachelogger> brrrrrr
[22:54] <yofel> most split packages don't print one
[22:54] <apachelogger> yofel: not unless upstream commits to it
[22:54] <yofel> well, yeah
[22:55] <apachelogger> so ultimately we'd be able to grab the cmake summary section and cmake full logs out of the buid log
[22:55] <apachelogger> for most reviews former is sufficient
[22:55] <apachelogger> but knowing upstream developers latter is handy because they tend to forget to set summary information at times :P
[22:57] <yofel> s/at times/usually/
[22:57] <kubotu> yofel: You did something wrong... Try s/you/me/ or tell me "help sed"
[23:05] <rbelem> Darkwing, ping
[23:26] <Ezim> hmm will kde 4.8.4 be released?
[23:27] <Ezim> I thought kde was skipping it
[23:37] <yofel> Ezim: why? It's still in their schedule
[23:38] <yofel> if anything, we don't have a .5 anymore
[23:38] <Ezim> yofel, I think my problem will go away with kde 4.8.4 :)
[23:38] <Ezim> because pulseaudio+kmix worked like dream in 11.10 also kubuntu-backports ppa with kde 4.8.2
[23:39] <Ezim> so the problem is kde 4.8.3
[23:41] <shadeslayer> Ezim: s/will/might/ ;)
[23:41] <Ezim> :) yeah it might
[23:42] <Ezim> a friend did write bugreport to upstream
[23:42] <Ezim> so let us hope it will be fixed
[23:42] <Ezim> is it possible to go back to kde 4.8.2?
[23:43] <shadeslayer> !downgrade
[23:43] <shadeslayer> well .. hmm ..
[23:43] <apachelogger> same for KDE though :P
[23:43] <Ezim> :) not really want to downgrade to 11.10
[23:43] <apachelogger> Ezim: yeah, he reported the bug to me :P
[23:43]  * apachelogger is responsible for just about every multimedia bug :P
[23:43] <Ezim> apachelogger, did he... :)
[23:44] <Ezim> apachelogger, then run.. I will check you
[23:44] <Ezim> :P
[23:44] <Ezim> lol
[23:44] <shadeslayer> yes, blame apachelogger when your prn doesn't play
[23:45] <apachelogger> indeed so
[23:45] <Ezim> :)
[23:45] <apachelogger> which is why I fixed dragon to give better prn experience
[23:45] <apachelogger> still not quite happy with it tho
[23:46] <shadeslayer> does it read filenames for keywords xD
[23:46] <shadeslayer> like it did earlier
[23:46] <shadeslayer> or did you enhance it
[23:46] <Ezim> apachelogger, so you are harald? :)
[23:47] <yofel> he is indeed, at least while he's not a drunken butterfly looking for unicorns
[23:47] <Ezim> it was me that tried pulseaudio 2... https://launchpad.net/~ubuntu-audio-dev/+archive
[23:47] <yofel> pink unicorns that is
[23:47] <Ezim> but it did not work
[23:47] <Ezim> yofel, lol... :)
[23:48] <shadeslayer> which is most of the time
[23:49] <Ezim> apachelogger, so in kde 4.8.3 pulseaudio+kmix hate each other... on my laptop :)
[23:50] <shadeslayer> probably because kmix couldn't decide whether or not it wanted a horizontal or vertical layout as it's default :P
[23:50] <Ezim> oki... thats over my knownledge
[23:50] <Ezim> :)
[23:51] <rbelem> Darkwing, i'm adding allwinner specific changes to kernel debianization
[23:51] <shadeslayer> tbh, I doubt alot of people know of that discussion
[23:51] <apachelogger> what discussion?
[23:51] <shadeslayer> unless they're on the usability ML
[23:51]  * apachelogger already made a decision on that topic
[23:52] <shadeslayer> apachelogger: I lost interest after the post about the OS X volume slider
[23:52] <shadeslayer> because vertical layout ftw
[23:53] <apachelogger> lol
[23:53] <apachelogger> they don't matter, as I said
[23:53]  * Ezim will go to bed. I wish you all the best. apachelogger I hope you fix my issue, otherwise I will check you in my sleep. :P
[23:53] <apachelogger> the discussion it total bikeshedding coz 99% of the audience have flipping volume keys
[23:53] <shadeslayer> ^
[23:53] <shadeslayer> agreed :P
[23:53] <apachelogger> Ezim: nighty night
[23:54] <shadeslayer> Was anyone *for* horizontal layouts though? ( Apart from tdfischer )
[23:59]  * yofel wouldn't mind having the volume slider that you get when you click on the icon be horizontal
[23:59] <yofel> as that would actually be 90° to my panel...
[23:59] <yofel> currently if I click on the kmix icon, the volume panel covers the panel from the icon downward


[00:03] <bluesabre> evening all
[00:04] <bluesabre> While I'd rather not fork a fairly new package, I'm not opposed to trying to get -pa-plugin up to indicator-sound in usefulness
[00:04] <bluesabre> ... and then probably do some things better
[01:26] <david__> Hi xubuntu-dev, I'm here to discuss on the permissions on the use of the xubuntu word and trademark as far as advertising xubuntu in YouTube video/commercials, print ads, stickers... (I actually asked for the trademark permission for Canonical, however the form is only for Ubuntu.) I was actually escorted here to Xubuntu community contacts.
[01:26] <david__> ...as described in the email I have received from Canonical Legal "...With respect to XUBUNTU, you will need to contact the Xubuntu community directly to discuss your proposed use.  You can find their contact details on the following website: https://xubuntu.org/..."
[05:37] <Unit193> bluesabre: Why would one fork it?  Why not just give andrzejr a free patch...?  There's not even a bug requesting it yet, and as far as the mic, Xfce Bug 12097.
[05:37] <Unit193> ("If you can produce a patch I will gladly review it and push it to git.")
[10:48] <bluesabre> Unit193: I was thinking it was kinda in a different direction from indicator-sound, but should probably review again
[13:35] <Spass> flocculant: I'm starting the application testcases from testing tracker now and I have very minor issues with first one (Catfish), should I just write it in the comment section on the tracker, here or to you directly?
[13:42] <Spass> I'm asking because maybe there's no reason to call them "issues", maybe just testcases are slightly outdated
[15:19] <Spass> bug 1689842
[15:20] <Spass> question - should I edit my bug report to something different than Private?
[16:09] <flocculant> Spass: as I said yesterday - the testcases are well out of date - report bug on manual testcase project via the link I gave you - if it's not a testcase bug then I can deal with it
[16:09] <flocculant> chances are that anything you find is in fact a testcase bug
[16:22] <Spass> flocculant: thanks, when I'm not sure about things, I'm just writing info in a comment section, I will let you know when I'm done testing, some are completed already, maybe something will be useful for you guys http://packages.qa.ubuntu.com/qatracker/milestones/377/builds/146768/testcases
[16:24] <flocculant> everything's useful there :)
[17:43] <Spass> Xubuntu 17.10 is using very old xfce4-power-manager version, I have 3 issues related to it on my laptop right now
[17:54] <Spass> "Zarro Boogs found." lol
[18:53] <Spass> Power Manager is a mess on my laptop :/ done testing for today, I added some comments on the tracker, biab
[20:29] <flocculant> Spass: yea - pretty sure plan is to make sure things are ported to gtk3 - I'm using 1.6.0+git version from https://launchpad.net/~xubuntu-dev/+archive/ubuntu/ppa
[20:31] <flocculant> bluesabre: what are our plans for updating things like that in standard Xubuntu this cycle? akxwi-dave and I are planning to ramp up package testing
[20:31] <flocculant> consequently - testcases need looking at - don't really want to be doing that too often in the cycle :)
[20:32] <knome> basically any updates shouldn't affect testcases as the GTK3 replacements should be identical (eg. no new features)
[20:32] <flocculant> well ... are they though?
[20:32] <knome> and i guess the idea is to push to main repositories when something is stable and all of its dependencies are satisfiable from the main repositories
[20:32] <knome> in the majority of cases, yes they are
[20:33] <knome> and it feels unlikely that the minority is affecting testcases either - as it's not something major that's changed
[20:37] <flocculant> luckily for you notifications isn't tested ;)
[20:37] <knome> i didn't say nothing changes
[20:37] <knome> but any changes to features are very much frowned upon on xfce already :P
[20:38] <flocculant> Spass: I've edited the power result - you'd put Xfce bug numbers in the critical fails - they have to be Launchpad ones I'm afraid
[20:40] <flocculant> knome: really? notification is the same now as it's always been? ochosi will be upset that all the changes there haven't been noticed ;)
[20:40] <knome> i didn't say that either
[20:41] <knome> and this comment was meant for the GTK migration anyway, not "always"
[20:41] <flocculant> my issue is whether we're going to have to keep changing testcases through the cycle
[20:41] <knome> my answer it's very unlikely that this would happen
[20:41] <knome> ís
[20:41] <knome> eh, +is
[20:41] <Spass> flocculant: thanks, I didn't want to duplicate what was already on Bugzilla, and I read "Bugs are tracked in Xfce Bugzilla." on xfce4-power-manager LP page
[20:41] <flocculant> ok - but the question was for bluesabre :D
[20:42] <knome> flocculant, i acknowledge... but i'm sure he'll be giving a similar answer which you'll have to wait for a while
[20:42] <knome> but feel free to do so ;)
[20:43] <flocculant> Spass: yea - but we have to put LP numbers on the trackers - otherwise it looks rather odd - it had linked to bug 12317
[20:43] <flocculant> and the other was a Soundblaster one :)
[20:43] <knome> soundblaster ftw
[20:43] <Spass> too bad I can't submit 'Failed' without any bug number
[20:44] <flocculant> knome: indeed
[20:44] <flocculant> Spass: yea I know, but it stops bizarre failures of testcases :)
[20:45] <Spass> that's why I left 'Running' on Catfish and light-locker and I added some comments
[20:45] <knome> i guess we could file a bug saying "the required bugs aren't tracked on LP" and use that if only bugzilla bugs appear...
[20:45] <Spass> in fact they're finished with small issues
[20:46] <flocculant> Spass: because we're such a small team - it's fine for the time being to pass them and make comments - we do read those
[20:46] <Spass> flocculant: ok, so I 'll change them to passed, was worrying my comments won't be noticed :)
[20:47] <knome> well they're not passed...
[20:48] <flocculant> knome: and also - because the testcases need to be 'this button' and not 'this switch' or whatever - changes do need to be made - otherwise we get spurious things commented
[20:49] <flocculant> so - we do need to know if there are planned changes from gtk2 to gtk3 if we're doing package testing
[20:49] <knome> flocculant, right... that's a good point but i hope we do not have too many widgets changing :)
[20:49] <Spass> knome: but they're not 'Running' any more and I can't mark them as 'Failed' without a bug #, and I wasn't sure my minor issues/comments deserve a bug report
[20:49] <knome> flocculant, one thing we could do is to list widgets that are going to be deprecated (or in other words, need replacing) already
[20:49] <flocculant> Spass: for the moment please don't worry yourself about that - what I'm after here is testing the testcases against the packages
[20:50] <flocculant> just do what I say for now
[20:50] <knome> Spass, rather leave them "running" than mark "passed"
[20:51] <flocculant> Spass: please ignore anyone but me here
[20:51] <Spass> is there a fourth option? like 'Undecided' :P
[20:52] <flocculant> at the moment this isn't about testing packages
[20:52] <flocculant> we need the testcases checked
[20:52] <knome> Spass, no... just keep them "running" please
[20:52] <Spass> I'm just planning to finish all the testcases this week, and hopefully some of my comments will help, but I guess I know everything what I'll write there already
[20:52] <flocculant> that's all I'm interested in currently
[20:53] <flocculant> Spass: I need bug reports on whether the testcase is correct
[20:53] <flocculant> that is what we need
[20:56] <Spass> to that point only Catfish testcase needs to be updated I think, it seems there was a slightly interface change
[20:58] <Spass> and Thunar with "Wastebasket/Rubbish Bin", unless that's what it's called on en_GB (I'm using en_US on 17.10 I think...)
[20:58] <Spass> minor things
[20:59] <flocculant> things like that we can't really do much about
[20:59] <flocculant> it's usually rubbish bin here
[21:00] <flocculant> except for in places plugin and on desktop etc
[21:00] <flocculant> anyway - I'm done for the night
[21:40] <bluesabre> evening all
[21:40] <knome> hello bluesabre
[21:41] <bluesabre> flocculant: GTK+3 ports, application updates, possibly pulseaudio-plugin to replace indicator-sound... or being prepared to replace indicators in general
[21:46] <bluesabre> Regarding the ports, they should get a good look because a lot of gtk2 xfce is deprecated and has to be replaced with all new everything


[00:56] <Nivex> "Ubuntu 11.10 has migrated away from /var/run, /var/lock and /dev/shm and now uses /run, /run/lock and /run/shm instead (respectively)."
[00:56] <Nivex> Why?
[13:18] <BugeyeD> Nivex: i hate it. while i understand wanting to "move forward" and improve things, breaking portability without a _great_ reason just p's me off.
[13:19]  * holstein wonders how the move to wayland is coming...
[14:10]  * BugeyeD too. that is sure to result in malcontent for some folks, but at least the reasoning seems to have some merit. while i'm accustomed to X, i'm surprised it's gone this long without being replaced. it's fairly horrible from a networking and security standpoint.
[15:32] <holstein> yeah, im still hopeful that the positives outweigh the negatives
[15:32] <holstein> its all open, so getting the functionalitly ported over *should* be possible
[15:33] <holstein> i doubt i will miss much


[00:52] <cyphermox> probably won't be fixed in time; we'll see
[00:53] <cyphermox> lyn||ian: it's on my list, but respins depend on not just me, and I don't think a non-crippling installer bug is sufficient rationale alone to cause a respin.
[01:12] <lyn||ian> cyphermox, oh ok
[01:13] <lyn||ian> at least it is not as bad as I first thought
[04:32] -queuebot:#lubuntu-devel- Builds: Lubuntu Alternate amd64 [Zesty Final] has been updated (20170411)
[04:32] -queuebot:#lubuntu-devel- Builds: Lubuntu Alternate i386 [Zesty Final] has been updated (20170411)
[04:51] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop amd64 [Zesty Final] has been updated (20170411)
[04:51] -queuebot:#lubuntu-devel- Builds: Lubuntu Desktop i386 [Zesty Final] has been updated (20170411)


[02:35] <Stalevar> That's cool, but does anybody know what netmgrd is and how to kill it? It is originated from android image file, and it's listening to many udp ports which is really suspicious. Is it a virus?