[00:48] <ScottK> eMyller: Dropped a bad patch you won't care about unless you're either using the new Ubuntu touch stuff or a wacom tablet.
[00:48] <ScottK> eMyller: The PPA breaks the former and fixes the latter.
[00:52] <eMyller> ScottK: i added the repo to my sources
[00:52] <eMyller> was too lazy to get the ntrack packages only
[00:53] <eMyller> ScottK: and HELL IT WORKS
[00:53] <eMyller> :)
[03:44] <ScottK> Unless you care about touch stuff the PPA Qt packages are just fine.
[03:49] <eMyller> ScottK: my netbook's screen gets smudged when I touch it, but np at all.
[03:50] <ScottK> :-)
[03:51] <eMyller> ok, now my natty is almost perfect
[03:52] <eMyller> i just need to make the gpu stuff smoother :\
[03:52] <eMyller> (intel)
[03:56] <ScottK> For me Intel on Natty is way better than it was on Maverick.
[03:56] <ScottK> Still not perfect, but way better.
[03:56] <eMyller> maverick was very smoother
[03:56] <fei> Hi
[03:56] <eMyller> blur worked beautifully
[03:56] <eMyller> * even blur
[03:57] <fei> I'm a kubuntu user from Chima
[03:57] <eMyller> hi, fei
[03:57] <fei> China
[03:57] <ScottK> Hello fei. Welcome.
[03:57] <ScottK> eMyller: Which Intel?
[03:57] <eMyller> ScottK: what driver are you using?
[03:57] <fei> I have something in trouble,could you help me?
[03:58] <ScottK> fei: For help, you should try #kubuntu.
[03:58] <ScottK> eMyller: Whatever is default for Intel.  It's mostly i945.
[03:58] <fei> I have try,but they tell me to come here
[03:58] <ScottK> OK.  What's the problem.
[03:58] <ScottK> No promises, but I'll at least listen to the problem.
[03:58] <fei> when I resize the konsole window, the system crashed
[03:59] <fei> thank you
[03:59] <ScottK> eMyller: Blur and some effects are slower, but that's Kwin changes in 4.6, not Intel.
[03:59] <ScottK> fei: Did the Dr. Konqi crash reporting tool start up after it crashed?
[03:59] <fei> no
[04:00] <fei> the system no respon
[04:00] <fei> I have to reboot
[04:00] <ScottK> It crashes and the system doesn't respond at all?
[04:00] <fei> ye
[04:00] <eMyller> wow
[04:00] <eMyller> ScottK: mine is a N10 gpu
[04:01] <ScottK> Oh.  I don't have any of those.
[04:01] <fei> nvidia gpu
[04:01] <ScottK> fei: Does the screen go black? What exactly happens?
[04:01] <fei> I have installed nvidia driver
[04:01] <fei> not go black
[04:02] <eMyller> it was horribly unusable (really) with default natty drivers; i had to install xorg-edgers'.
[04:02] <eMyller> now i have a burning cpu (not the gpu one!)
[04:02] <ScottK> Sounds like either an nvidia or X problem, not strictly KDE then fei.
[04:02] <fei> o
[04:02] <ScottK> fei: I hate to redirect you again, but in #ubuntu-x they can probably help you better.
[04:03] <eMyller> fei: try to remove you kwin and konsole settings
[04:03] <fei> ok,thank you
[04:03] <fei> I will try
[04:03] <ScottK> I don't know anything about using nvidia myself, so I can't help further.
[04:03] <eMyller> fei: rm ~/.kde/share/config/{konsolerc,kwinrc}
[04:03] <ScottK> That does sound like it's worth a try.
[04:04] <fei> ok,thank you
[04:04] <multipass> hi, im unable to get iphone4 to mount in 11.04, all i can get is the camera. any idea?
[04:04] <eMyller> fei: then do a hard logout and try again
[04:04] <ScottK> multipass: Ask in #ubuntu as it's not likely Kubuntu specific.
[04:04] <fei> ok
[04:04] <eMyller> ScottK: indeed, the #kubuntu channel lacks of good support. :S
[04:05] <ScottK> Well we need more people who know what they are doing to help then.
[04:05] <multipass> its kubuntu specific, im able to get iphone4 working in ubuntu 10.10, and in 11.04, it works out of the box, ScottK
[04:05] <ScottK> Odd.
[04:05] <eMyller> lol
[04:05] <ScottK> Then #kubuntu.
[04:05]  * ScottK has no iPhone of any kind, so can't help with that one.
[04:06] <eMyller> multipass: just out of curiosity, do a sudo fdisk -l and see if anything there matches your iphone storage
[04:07] <eMyller> ScottK: it seems they're redirecting to here. :P
[04:07] <ScottK> Which is what happens from time to time.
[04:07] <ScottK> My usual response is "That doesn't make this the support channel", but I felt briefly generous tonight.
[04:08] <asobi> linux could always use more support to gain more users
[04:08] <multipass> hmm, nothing
[04:09] <eMyller> asobi: ##linux is awesome
[04:09] <multipass> just my 3 harddrives
[04:09] <eMyller> the problem are the distros spread support
[04:09] <eMyller> multipass: ok, so that is definitely kde-specific; there's something odd happening.
[04:09] <ScottK> The next place to look is /dev.  Look at it with and without the iPhone plugged in and see if the list changes.
[04:10] <ScottK> You can use that to find the device name.
[04:10] <asobi> right. more support in general across all distros
[04:10] <ScottK> It would also help if it sucked less.
[04:10] <dantti_> ScottK: is it too hard to downgrade to mav?
[04:10] <asobi> well, gentoo or arch users probably don't need support ~_~
[04:11] <ScottK> dantti_: Downgrading is not supported.
[04:11] <eMyller> dantti_: why are you willing to do it?
[04:11] <dantti_> ScottK: yes, taht what I thought, but natty x, nvidia, kernel... something is killing me
[04:11] <ScottK> It's not supported in Debian type distros and it's not supported by KDE, so you're out on all counts.
[04:12] <ScottK> You can possibly install the maverick kernel and run that.
[04:12] <dantti_> or my gpu got broken :P
[04:12] <dantti_> if I maximize my konsole it freezes now and I have to reboot :P
[04:13] <dantti_> not counting the when the screen get completely corrupted... but pc still responds
[04:13] <ScottK> dantti_: That sounds similar to the problem fei is having.
[04:14] <ScottK> You might see what's up in #ubuntu-x as well.
[04:14] <dantti_> ScottK: yes... I bet on nvidia drivers but..
[04:14] <ScottK> There is no but.  You had me at nVidia.
[04:14] <dantti_> anyways thanks..
[04:14] <ScottK> Sorry I don't have a better answer.
[04:15] <dantti_> that's fine, it's just that it's upsetting to work with these problems ...
[04:16] <eMyller> dantti_: there are always workarounds
[04:16] <maco> is it possible kubuntu doesnt ship with the libs?
[04:16] <eMyller> life wouldn't be beautiful it it wasn't difficult lol
[04:16] <eMyller> maco: what libs?
[04:16] <asobi> emy the philosopher^^
[04:17] <eMyller> hehe
[04:18] <dantti_> eMyller: like? (I was thinking on trying to use mav nvidia driver... but I'm not sure if that would work...
[04:18] <eMyller> dantti_: i think it's worth a try
[04:18] <maco> usbmuxd and ifuse?
[04:18] <eMyller> anyway i can't give you a straightforward answer because i don't have a nvidia gpu. unfortunately.
[04:19] <fei> maye open source nivedia will be ok
[04:19] <fei> driver
[09:43] <bulldog98> Hi guys. I did the packaging for kontact 4.6 rc1 and uploaded it to staging.
[11:22] <bulldog98> https://code.launchpad.net/~bulldog98/kdepim-runtime/ubuntu-4.6/+merge/60387
[11:22] <bulldog98> https://code.launchpad.net/~bulldog98/kdepim/ubuntu-4.6/+merge/61530
[12:47] <rbelem__> apachelogger: ping
[12:53] <c2tarun> I think today is the day when tarballs for kde sc 4.7 should be released. What is the time?
[13:05] <ScottK> When they are ready.
[13:10] <apachelogger> rbelem: pong
[13:19] <rbelem___> apachelogger: do you think we should send the tablet list to ubuntu-devel or directly to ogra, rsalveti?
[13:31]  * ScottK recommends handling it privately.
[13:40] <steveire> ScottK: Is the kdepim 46 doesn't build against kdelibs47 thing still an issue? trueg hasn't fixed it, and I need to decide whether I need to just revert his patches
[13:41] <ScottK> steveire: I think it's an upstream question, but I also think Thiago's "If you're going to do that call it KDE 5.0" response is germane.
[13:42] <steveire> Me too
[14:35] <eMyller> 'morning fellas
[14:56] <Quintasan_> \o
[14:56] <Quintasan> SO FREAKIN HOT
[14:57] <eMyller> Quintasan: come to here and meet true hotness
[14:58] <Quintasan> eMyller: more than 30*C celsius?
[14:58] <eMyller> hahaah
[14:58] <eMyller> yes.
[14:58] <Quintasan> sup, 32 in here
[14:58] <eMyller> kinda that in here too
[14:59] <eMyller> but that's what the meters say. there is also the polution dome to make things worse.
[15:17]  * yofel watches the tunderstorm outside
[15:18] <yofel> 23°C
[15:22] <jussi> we have rain here....
[15:32] <sheytan> JontheEchidna: hey dude. Do you need help in Muon SC UI improvements?
[15:36] <shadeslayer> HAHAHAHA
[15:36] <shadeslayer> Quintasan: it's flipping 45oC here
[15:37] <shadeslayer> on the good days it comes down to 30ocC
[15:40] <apachelogger> rather  warm in austria
[15:40] <apachelogger> dang, no jr
[15:41]  * apachelogger ponders whether '''D-Bus method call failed: org.freedesktop.DBus.Error.ServiceUnknown: The name com.redhat.NewPrinterNotification was not provided by any .service files''' is ubuntu specific
[15:42] <shadeslayer> com.redhat ... that doesn't sound too good
[15:42] <apachelogger> system-config-printer whatever it is called implements that
[15:42] <shadeslayer> apachelogger: oh did you get my message ?
[15:42] <apachelogger> as redhat originally worte that plunder and it never ended up on fdo
[15:42] <shadeslayer> hehe
[15:42] <apachelogger> shadeslayer: can you plz fix kamoso to not build depend on liblvc-dev
[15:42] <shadeslayer> apachelogger: the one about OMAP4
[15:43] <shadeslayer> apachelogger: will have a go at it tonight maybe
[15:43] <apachelogger> isnt it tonight already?
[15:43] <apachelogger> no message about omap4
[15:43] <shadeslayer> [01:10:29] <shadeslayer> apachelogger: Question: What do we wish to accomplish by supporting Kubuntu on OMAP4? i'm still trying to figure out what OMAP4  offers over OMAP3
[15:44] <apachelogger> I am not targeting omap4
[15:44] <apachelogger> you are
[15:44] <apachelogger> so you should actually know what you want to accomplish
[15:44] <apachelogger> as I mentioned the other day there are only 2 or 3 consumer devices on the market with omap4
[15:44] <shadeslayer> yeah ^^
[15:45] <shadeslayer> apachelogger: but what does OMAP4 offer better than OMAP3?
[15:45] <apachelogger> ask wikipedia
[15:46] <shadeslayer> i can't find a satisfactory answer to that
[15:46] <shadeslayer> tried
[15:46] <apachelogger> OMAP4430 and OMAP4440 use dual-core ARM Cortex-A9, a PowerVR SGX540 integrated 3D graphics accelerator which runs at a clock frequency of 300 MHz compared to previous incarnations of SGX540 typically at 200 MHz making it theoretically 50% faster, and an IVA3 multimedia hardware accelerator with a programmable DSP that enables 1080p Full HD and multi-standard video encode/decode.[6][7][8][9][10][11] OMAP 4 will use ARM-Cortex A9s with ARMs
[15:46] <apachelogger> SIMD engine (Media Processing Engine, aka NEON) which may have a significant performance advantage in some cases over Nvidia Tegra 2s Cortex-A9s with non-vector floating point units.[12] It also uses a dual-channel LPDDR2 memory controller compared to Nvidia Tegra 2s single-channel memory controller.
[15:46] <shadeslayer> yes i saw that
[15:46] <shadeslayer> i was coming to the point about video cards
[15:47] <shadeslayer> from what i've learnt most of the optimizations would go into the compiler itself
[15:47] <shadeslayer> gcc in this case
[15:48] <shadeslayer> apachelogger: how well does Kubuntu Mobile run on OMAP3 ?
[15:51] <apachelogger> it starts
[15:52] <didrocks> are the branches in ~kubuntu-members still in use? they seems private to all members and so don't reflect uploader rights
[15:53] <apachelogger> didrocks: kubuntu-packagers is the latest and greatest
[15:53] <yofel> didrocks: they're in kubuntu-packagers now, which is -members and ubuntu-core-dev
[15:53] <didrocks> need to update some vcs-bzr then ;)
[15:53] <didrocks> thanks!
[15:53] <apachelogger> yofel: are there still branches in kubuntu-members?
[15:54] <yofel> not that I know of, but the Vcs- links in the packages probably still point there (where it wasn't updated yet)
[15:54] <apachelogger> ah
[16:05] <shadeslayer> apachelogger: is it usable?
[16:06] <apachelogger> shadeslayer: define usable
[16:07] <apachelogger> rbelem: do we have some hi quality photo/video of kubuntu mobile on n900?
[16:07] <shadeslayer> apachelogger: can i play a movie on it? can i browse the web? can i make a phone call via the N900
[16:07] <shadeslayer> +/
[16:07]  * apachelogger only has shitty cams except for the one on the n900 itself... ;)
[16:07] <shadeslayer> erm
[16:07] <shadeslayer> hehe
[16:07] <apachelogger> shadeslayer: no
[16:07] <apachelogger> as it is a tech previe
[16:07] <apachelogger> w
[16:07] <shadeslayer> no to all of the above?
[16:07] <apachelogger> you could browse the web
[16:08] <shadeslayer> okay so WiFi works, but video is shot?
[16:08] <apachelogger> but seeing as our web browser likes to render in the cpu right now, it would not be much pleasure I assume
[16:08] <apachelogger> plus the whole thing is not finger proof anyway ^^
[16:08] <shadeslayer> hmm ... okay ... make Kubuntu usable on OMAP*
[16:08] <shadeslayer> or lets say ARM
[16:09] <shadeslayer> much more fancy :P
[16:09] <apachelogger> you better be reading documentation on arm and omap before saying things like that
[16:09] <shadeslayer> apachelogger: yeah thats what i do in my free time these days
[16:09] <shadeslayer> also trying to rope in a prof who can help me out there
[16:10] <rbelem> apachelogger, hum i think we dont have
[16:11] <apachelogger> rbelem: do you have a setup right now? + a sensible cam
[16:12] <rbelem> apachelogger, i dont have a ready setuo, but i can setup in some min
[16:12] <apachelogger> only if you have time :)
[16:12] <apachelogger> not that urgent
[16:12] <rbelem> apachelogger, i forgot to give you the class 10 microsd :-(
[16:12] <rbelem> apachelogger, cool :-) i will do that in my lunch time
[16:14] <apachelogger> rbelem: the alternative to class 10 microsd is making ofono work and replace maemo on the HD with kubuntu mobile ^^
[16:14] <apachelogger> that said, do you actually know if that is easily possible + would you be able to restore maemo
[16:18] <Nightrose> folks i still need more SoK mentors/projects - if anyone is up for that pretty please let me know - i have way more students than i can currently match with mentors
[16:20] <jussi> harald!!!! apachelogger!!! http://is.gd/swWjo6
[16:20] <jussi> :D
[16:21] <apachelogger> is it ofono for n900?
[16:21] <apachelogger> jussi: WTF is it green
[16:21] <jussi> because of the grass unicorns eat...
[16:21] <jussi> :P
[16:22] <apachelogger> that sounds silly
[16:22] <jussi> LOL
[16:23] <rbelem> apachelogger, yup... a cold flash
[16:29] <bulldog98> http://revu.ubuntuwire.com/p/kcm-grub2
[16:29] <bulldog98> new version packaged
[16:33] <Quintasan> apachelogger: make it pink then
[16:33] <JontheEchidna> sheytan: did you have any particular changes in mind?
[16:33] <sheytan> JontheEchidna a lot of ;)
[16:34] <JontheEchidna> bulldog98: ;)
[16:34] <JontheEchidna> er
[16:34] <JontheEchidna> sheytan: ;)
[16:34] <sheytan> first of all i would love to see something like a start page.
[16:34] <JontheEchidna> b is not even next to s O-o
[16:34]  * Quintasan silently pokes agateau
[16:34] <Quintasan> UI specialist!
[16:35] <sheytan> JontheEchidna, I will make some mocks when i come back home ;)
[16:35] <JontheEchidna> sheytan: btw, there is interest in a Muon Mobile. It's pretty much a clean slate
[16:35] <Quintasan> MOBILEZ?!
[16:35] <Quintasan> cool
[16:36] <sheytan> JontheEchidna, well, that would be next step for me. First I want to concentrate on Muon of kubuntu (couse you kick off kpk) which is kinda sed :(
[16:36] <sheytan> i liked kpk
[16:37] <sheytan> but if we can do Muon a cooler one, then i'm with your decision
[16:37] <apachelogger> rbelem: that sounds scary ^^
[16:37] <JontheEchidna> brb rebootin'
[16:38] <debfx> bulldog98: kcm-grub2 0.5.0 is already in the archive
[16:41] <agateau> Quintasan: what should I look at?
[16:42] <rbelem> :-O
[16:42] <Quintasan> agateau: well, sheytan wants to propose some changes to Muon and if we want to have Muon by default then it HAS to have sensible UI, doesn't it?
[16:43] <agateau> Quintasan: agreed, I was just wondering if there was some existing ui I should look at (couldn't find anything reading the backlog)
[16:44] <Quintasan> sheytan or jtechidna: poking agateau and showing him mockup (if you agree to change something) would be a good idea IMO
[16:48] <bulldog98> debfx: ah ok
[16:49] <JontheEchidna> oh, aurelien. hi :)
[16:49] <agateau> JontheEchidna: hi!
[16:49] <bulldog98> JontheEchidna: are you planing to upload libqapt to debian?
[16:49] <steveire> kdepim 4.6 should build with kdelibs master again (Though I haven't tried it yet) http://bugs.kde.org/268595
[16:50] <JontheEchidna> agateau: I made a lot of the changes to Muon Package Manager: http://i.imgur.com/88DHt.png
[16:50] <JontheEchidna> I haven't gotten around to the software center changes yet
[16:50] <bulldog98> steveire: I got it build with 4.6
[16:50] <agateau> JontheEchidna: much nicer!
[16:50] <apachelogger> +1
[16:51] <agateau> JontheEchidna: great to see you manage to reduce the top part of the details tab to one line
[16:51] <apachelogger> I still find the filter widget horrible ^^
[16:51] <JontheEchidna> bulldog98: somebody has put packages for libqapt in mentors.debian.org, but they seem to be stuck there. I've been pondering maintaining it myself, but I'll have to set up a virtualbox for debian or something first
[16:51] <apachelogger> maybe one of these days KDE might grow a good one :S
[16:51] <bulldog98> JontheEchidna: use pbuilder magic
[16:51] <bulldog98> that works
[16:51] <Quintasan> JontheEchidna: ^
[16:51] <sheytan> agateu Quintasan JontheEchidna will do some mocks today propalby ;)
[16:52] <JontheEchidna> to maintain it in debian I'd have to actually check to make sure the packages work
[16:52] <agateau> JontheEchidna: isn't it possible to move the "Reinstallation" button in the "Mark for:" combo box?
[16:52] <Quintasan> JontheEchidna: and you have just to maintain it in Debian only
[16:52] <Quintasan> :P
[16:53] <JontheEchidna> agateau: That's not a combobox. It's a sub-menu for different types of removal
[16:53] <JontheEchidna> remove vs purge
[16:53] <JontheEchidna> (definitely not something I'd expose in the software center as an option) ;-)
[16:53] <bulldog98> you could use a setting to set that
[16:54] <bulldog98> and a right click to use the other option
[16:54] <JontheEchidna> http://i.imgur.com/3FEOM.png
[16:54] <agateau> JontheEchidna: I see
[16:55] <Nightrose> JontheEchidna: i pushed a season of kde student to you - did you find time to reply to him?
[16:55] <JontheEchidna> I don't think I've heard from him...
[16:56] <JontheEchidna> I'll feel really bad if this was a while back :(
[16:56] <Nightrose> JontheEchidna: it was ;-) - it should have been in an email from me i think
[16:56] <Nightrose> would be nice if you could check
[16:58] <agateau> JontheEchidna: still it feels weird that one button has a submenu and the other does not... mmm... one could just provide 3 buttons, but that could be a bit overkill... need to think about it
[17:02] <JontheEchidna> brb, mother having computer problems
[17:06] <JontheEchidna> back
[17:06] <JontheEchidna> Nightrose: ah, two weeks ago. That was finals week ;-)
[17:07] <Nightrose> JontheEchidna: heh np - would be nice if you could get back to him - really having problems matching the students up - i have over 90 now for SoK and 51 for gsoc
[17:07] <Nightrose> slightly more than my mentor pool :D
[17:07] <JontheEchidna> heh
[17:08] <JontheEchidna> It sounds like he wants to get in to documentation?
[17:08] <Nightrose> might be - not entirely sure
[17:09] <shadeslayer> Nightrose: looks like everyone who applied for GSoC and did not get selected applied for SoK :D
[17:09] <Nightrose> shadeslayer: actually also a lot of those who didn't
[17:09] <JontheEchidna> I don't think there's really a technical solution for that. Identifying when or why a piece of hardware isn't working isn't easy. (In most cases the computer itself is oblivious that it is not working). Improving documentation to include tips on how to deal with that would be best
[17:09] <Nightrose> JontheEchidna: can you maybe reply with that?
[17:09] <JontheEchidna> yeah
[17:15] <JontheEchidna> Nightrose: sent
[17:16] <Nightrose> JontheEchidna: thx!
[17:16] <JontheEchidna> I referred him to our docs guys, hope he can handle a bit of runaround :P
[17:17] <Nightrose> heh yeah
[18:10] <bambee> evening
[18:40] <yofel> note: I'm off sick till tomorrow, c
[18:40] <yofel> *cu :(
[18:57] <apachelogger> JontheEchidna: what do we think of a library that adds pure virtual functions without soversion bump?
[18:58] <JontheEchidna> that would change the vtable, would it not?
[18:58] <JontheEchidna> not abi compatible, I don't think
[18:58] <apachelogger> yes, that is if there is a vtable to begin with
[18:58]  * apachelogger finds the horriblyness at lower level much worse
[18:59] <JontheEchidna> kde wiki says that abi should be ok if there was already a vtable
[18:59] <JontheEchidna> but not ok if there wasn't one already
[18:59] <apachelogger> appA builds with libB.so.0.0, does not with libB.so.0.0 :D
[18:59] <apachelogger> I mean
[18:59] <apachelogger> srsly
[18:59] <JontheEchidna> and this class can't have any subclasses
[19:00] <apachelogger> JontheEchidna: actually not
[19:01] <apachelogger> you can reimpl a virtual function of a base in a leaf
[19:01] <bambee> there is a bug or a detailed description about "Fix dolphin file property preview tab" ?
[19:03] <apachelogger> JontheEchidna: if you add a new virtual function to the vtable, the table changes
[19:03] <bambee> (I am working on userconfig but I can help for other tasks ;) )
[19:03] <apachelogger> meaning table lookups of leaf classes (assuming leaf classes are not privately contained within the own source) will fail
[19:05] <apachelogger> JontheEchidna: basically whenever you release a class with virtual functions you are stuck with those virtuals until you break ABI, as any change to the functions can potentially change the vtable thus breaking ABI
[19:05] <JontheEchidna> "just don't touch that shit; it'll probably break"
[19:05] <apachelogger> aye
[19:05] <apachelogger> anyhow
[19:06] <apachelogger> even if I were to accept the fact that it breaks binary compatibility
[19:06] <apachelogger> *pure* virtual also breaks source compatibility
[19:06] <apachelogger> gives me a stroke just thinking about that
[19:08] <apachelogger>     virtual ~HAsyncOp() = 0;
[19:08]  * apachelogger giggles
[19:09] <apachelogger> so it would seem the class is pure virtual because the API consumer is supposed to implement refcounting
[19:09] <apachelogger> a very interesting design choice right there
[19:09] <JontheEchidna> that sounds like something that should never be left to the consumer to do
[19:10] <apachelogger> assuming the author is no moron he must have had a reason for this
[19:13] <apachelogger>     HAsyncOpPrivate* h_ptr;
[19:14] <apachelogger> I wonder what the pimpl in the private class is called
[19:15] <apachelogger>     HClientAction* q_ptr;
[19:15] <apachelogger> ok
[19:15] <apachelogger> wtf
[19:16] <apachelogger> that does not make any sense
[19:16] <apachelogger> JontheEchidna: guess what the visible ptr of the private class is called
[19:16] <apachelogger> it is not d_ptr btw ;)
[19:17] <JontheEchidna> q_ptr
[19:17] <apachelogger> no
[19:17] <JontheEchidna> oh, that's how you get back out to the public class from the private class
[19:18] <apachelogger> yeah, I mean the other way around ... public to private
[19:18] <JontheEchidna> d_ptr
[19:18] <apachelogger> no
[19:18] <JontheEchidna> in sane apis
[19:18] <apachelogger> JontheEchidna:     HAsyncOpPrivate* h_ptr;
[19:18] <JontheEchidna> lol
[19:18] <apachelogger> :D :D :D
[19:18] <apachelogger> that is how you know someone did not quite understand the meaning of why d and why q ^^
[19:19] <apachelogger> I mean
[19:19] <apachelogger> if you call public ot private h, then at least call private to public micro ^^
[19:19] <apachelogger>     HClientAction* μ_ptr;
[19:19] <apachelogger> ^^
[19:19] <JontheEchidna> lol
[19:19] <apachelogger> :D :D :D
[19:19] <JontheEchidna> does the c standard allow that?
[19:19] <apachelogger> prolly not
[19:19] <JontheEchidna> and do compilers support that, is the real question
[19:20] <JontheEchidna> lol
[19:20] <apachelogger> which is why you do not choose h as pimpl name :P
[19:21] <apachelogger> http://paste.kde.org/72787/
[19:21] <apachelogger> this is also cool
[19:21] <apachelogger> "we are public, and we have a function invokethemaster, and remember we are still public, and we have a qba.... oh and did I mention we are public?, yeah, we also have dtor and ctor"
[19:22]  * apachelogger considers code too similar to prn to find this code there enjoyable
[19:23] <apachelogger> argh, will is not around
[19:23]  * apachelogger wanted to do some upnp enablement
[19:42] <sheytan> JontheEchidna: hey, does Muon SC have an option for updating packages?
[19:42] <sheytan> i didin't see any :|
[19:44] <sheytan> JontheEchidna: the worst thing about it now, is the left panel with software sources
[19:47] <DarkwingDuck> sheytan: did I show you th banner I created?
[19:48] <DarkwingDuck> http://people.ubuntu.com/~david.wonderly/Graphics/Oneiric/
[19:48] <sheytan> DarkwingDuck nope
[19:48] <sheytan> prietty simple and nice :)
[19:49] <Quintasan> nice
[19:49] <DarkwingDuck> sheytan: You do graphics for Kubuntu aye?
[19:49] <sheytan> DarkwingDuck: yep
[19:50] <DarkwingDuck> sheytan: We need ot get together then. :) I'm leaning inkscape quickly and want to continue that.
[19:51] <sheytan> DarkwingDuck: help is always welcome :)
[19:51] <sheytan> i'm working on muon SC mockup now
[19:51] <sheytan> if we want a software center we have to do it right
[19:51] <DarkwingDuck> Okay good. Mimicing the website?
[19:52] <sheytan> DarkwingDuck: what's mimicing? :D
[19:53] <DarkwingDuck> mirror the look.
[19:53] <DarkwingDuck> Thanks Quintasan
[19:53] <sheytan> DarkwingDuck: do you want me to show the website to ya?
[19:54] <DarkwingDuck> sheytan: Sure!
[19:55] <sheytan> DarkwingDuck: sec
[19:55] <sheytan> i even can show you what's already done live :D
[19:55] <DarkwingDuck> :D
[19:55] <DarkwingDuck> sheytan: you going to be online tomorrow?
[19:56] <DarkwingDuck> Or, in 5 or 6 hours?
[19:56] <sheytan> DarkwingDuck: i'm generally online between 20:00 and 00:00 poland time
[19:56] <sheytan> DarkwingDuck:  http://staging.kubuntu.violetech.org/
[19:56] <sheytan> please don't publish this link anywhere else :)
[19:57] <DarkwingDuck> o.O
[19:57] <DarkwingDuck> sheytan: we are def going to start working together.
[19:57] <DarkwingDuck> BRB
[19:57] <DarkwingDuck> Need to make a phone call
[19:58] <sheytan> DarkwingDuck: what we need now is a web dev, that can finish the page. Mine doesn't have time :(
[20:05] <Quintasan> oh god
[20:05] <Quintasan> we seriously have Ballmer's Peak on TODO
[20:05] <Quintasan> :DDD
[20:06] <persia> Did you forget to mark the spec "Implemented"?
[20:07] <Quintasan> no idea
[20:07] <Quintasan> We should change that
[20:07] <ScottK> It's marked implemented.
[20:07]  * ScottK did so.
[20:07] <ScottK> Dunno why apachelogger added it to TODO as it's done.
[20:07] <Quintasan> \o/
[20:08] <apachelogger> follow ups
[20:08] <apachelogger> also our qt is broken
[20:08] <DarkwingDuck> sheytan: we'll talk
[20:08] <Quintasan> I think apachelogger wants more research
[20:08] <sheytan> DarkwingDuck: sure
[20:08]  * apachelogger is applying for kde e.v. membership ... one of the key missions of KDE e.v. is research
[20:09] <Quintasan> apachelogger: Wait, what, why Qt is broken? -_-
[20:09] <DarkwingDuck> sheytan: I do webdev stuff
[20:09] <apachelogger> https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/785318
[20:09] <Quintasan> oh wait, timeout
[20:09] <Quintasan> :/
[20:09] <sheytan> DarkwingDuck: good. I have all the current code, can share with ya so you can look what you can do :)
[20:10] <DarkwingDuck> sheytan: Aye, is it on LP?
[20:10] <Quintasan> apachelogger: is it as severe as I think?
[20:10] <Quintasan> like OpenGL renderer wouldn't work with this bug
[20:10] <apachelogger> no
[20:11] <apachelogger> I think it is just crap brought up by the particular test case
[20:11] <Quintasan> oh
[20:11] <Quintasan> >Kindly thrash Fridge people for refusing and ignoring Project Neon in person
[20:12] <ScottK> Seems like an odd thing for LSB testing to bring up since LSB wants Qt3.
[20:12]  * apachelogger doesnt even know what that means
[20:12] <sheytan> DarkwingDuck: nope, when i upload it will share with ya
[20:12] <apachelogger> ScottK: half our symbols fail lsb testing actually :S
[20:12] <Quintasan> ScottK: So we don't care about that?
[20:12] <apachelogger> (gdb) p this_registeredInterpolators
[20:12] <apachelogger> $8 = {pointer = {_q_value = 0x0}, destroyed = true}
[20:12] <apachelogger> all kap0tt
[20:12] <ScottK> Fortunately we aren't an LSB compliant distro, so we aren't actually required to care.
[20:12] <DarkwingDuck> sheytan: Awesome
[20:12] <Quintasan> cool
[20:13] <ScottK> LSB compliance is good, but it's wishlist really.
[20:15] <apachelogger> #0  QGlobalStaticDeleter<QVector<QVariant (*)(void const*, void const*, double)> >::~QGlobalStaticDeleter (
[20:15] <apachelogger>     this=0x7ffff6699b28, __in_chrg=<value optimized out>)
[20:15] <apachelogger>     at ../../include/QtCore/../../src/corelib/global/qglobal.h:1824
[20:15] <apachelogger> #1  0x00007ffff765fd3d in __cxa_finalize (d=0x7ffff6699700) at cxa_finalize.c:56
[20:15] <apachelogger> #2  0x00007ffff62639d6 in __do_global_dtors_aux () from /usr/lib/libQtCore.so.4
[20:15] <apachelogger> #3  0x0000000000000000 in ?? ()
[20:15] <apachelogger> ok
[20:16] <apachelogger> so clearly the global var gets eaten before the unregister is issued
[20:16] <apachelogger> hence the nil ptr in the global pod
[20:18] <apachelogger> ScottK: what do we do with that bug?
[20:18]  * apachelogger would think gcc should take care of proper finalization order on library unloading
[20:18] <apachelogger> then again it would be easily solved by checking the ptr before actually tring to access it
[20:19] <ScottK> Make a good bugreport for upstream and send it there.
[20:19] <ScottK> It doesn't sound like something to diverge from Debian or upstream over.
[20:19] <apachelogger> question is, is it upstream or our gcc maybe screwing us over
[20:20] <apachelogger> the reporter suggests only youbuntoo is broken
[20:20] <ScottK> Debian too.
[20:20] <apachelogger> oh, still could be gcc though *shrug*
[20:20] <ScottK> The intrepid reporter doesn't say what other distros might not be broken.
[20:20] <ScottK> True.
[20:22] <apachelogger> ScottK: I do not feel like reporting a bug upstream :P
[20:23] <ScottK> Maybe post your findings in the bug and invite the reporter to do so.
[20:23] <apachelogger> I think I'll just close and leave it to the reporter to throw the information at upstream
[20:23] <apachelogger> all the information should be there
[20:45] <debfx> phonon-backend-gstreamer still needs SRU verification on armel
[20:46] <debfx> do we even have actual arm users?
[20:47] <apachelogger> me
[20:47] <debfx> with working sound?
[22:25] <apachelogger> debfx: I think it had sound eventually, not particularly high focus for me seeing as plasma itself runs like crap right now
[22:26] <apachelogger> still not unimportant to have it actually available
[22:37] <ScottK> Oooh.  Blog post.
[22:38] <ScottK> "Phonon developer says sound 'not particularly high focus for me'".
[22:38] <apachelogger> s/Phonon/Kubuntu
[22:40]  * ScottK thinks apachelogger is a phonon developer.
[22:40]  * apachelogger is bi-developer
[22:40] <ScottK> TMI
[22:43] <DarkwingDuck> lol
[22:51] <cnd> ScottK, I just requested a merge to fix a FTBFS from the packaging branch
[22:51] <cnd> simple patch removal completion
[22:51] <ScottK> Thanks.
[22:51] <ScottK> apachelogger: Got time to look at a Qt merge?  ^^^
[22:58] <apachelogger> question is not do I have time, question is am i sober enough
[22:59] <apachelogger> where be this mystical merge?
[23:02] <cnd> apachelogger, https://code.launchpad.net/~chasedouglas/qt/fix-patch-removal/+merge/61668
[23:02] <cnd> extremely simple
[23:02] <cnd> the previous commit deleted the patches
[23:02] <cnd> but forgot to remove them from the quilt series file
[23:03] <apachelogger> I see
[23:03] <apachelogger> also, I think the one who broke it should process the merge request
[23:03] <apachelogger> Quintasan: pingpingping ^
[23:05] <apachelogger> cnd: thanks for the fix, unless it is super urgent, let's wait for Quintasan to integrate and upload
[23:06] <cnd> apachelogger, sure, np


[03:28] <ivoks> anyone around? :)
[03:15] <zul> heylo
[03:16] <alehke> hi
[05:42] <Keybuk> would anyone admit to knowing much about inotify?
[09:50] <st3> we reported a critical bug about bcm43xx here: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/85404
[09:50] <st3> we are receiving a lot of bug reports from ubuntu users, please fix it asap
[09:50] <st3> thank you
[11:33] <BenC> st3: for one, ogra was getting bcm43xx crashes and/or poor performance
[11:33] <st3> what does poor performance mean?
[11:33] <BenC> damnit, and ogra just left
[11:34] <BenC> poor performance means if he was more than 10 feet from the AP, he lost connection
[11:34] <st3> note that 4311 and 4318 are partially supported
[11:34] <BenC> I think that performance issues are mostly 4318 related
[11:34] <st3> there are big issues with interferences and power transmission
[11:34] <BenC> but the oopses are an issue regardless
[11:34] <BenC> he has an AMD64 laptop with 1G ram
[11:35] <BenC> and I thought that might be related, but didn't have time to debug his system
[11:35] <st3> ah yes, there are some experimental patches by larry finger
[11:35] <BenC> give me a few minutes to pull up some bug reports
[11:35] <st3> you should have included that ones, instead
[11:35] <BenC> wth is that bug report unchangeable by me?
[11:35] <st3> i don't know, the bug was filed by michael
[11:36] <st3> (link: ftp://lwfinger.dynalias.org/patches)
[11:36] <BenC> oh, viewstatus
[11:36] <st3> (e.g. ftp://lwfinger.dynalias.org/patches/patch_2.6.20_for_DMA_over_1GB)
[11:36] <BenC> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/77280
[11:37] <BenC> that's an unload bug
[11:37] <BenC> ogra's oops happened at random times during usage
[11:38] <st3> it's softmac related
[11:39] <st3> by the way, did you have him check /proc/interrupts?
[11:39] <BenC> the oops totally locked his box, so checking anything was impossible
[11:39] <BenC> If I remember right, the oops was in interrupt
[11:39] <st3> even with netconsole?
[11:40] <st3> is linux-source-2.6.20 (Ubuntu) a vanilla kernel?
[11:40] <BenC> netconsole doesn't bring the box out of a total lockup :)
[11:40] <BenC> it's mostly vanilla
[11:40] <st3> any patches related to softmac?
[11:40] <BenC> none
[11:41] <st3> he should enable full debugging output for both softmac and bcm43xx, and paste some more lines from dmesg right before the oops
[11:42] <st3> ogra, BenC was telling me about your oops
[11:42] <ogra> right, i didnt have it since some time ..
[11:43] <st3> i think you should enable full debugging output for both softmac and bcm43xx, then post a bug report to<EMAIL_ADDRESS>[11:43] <ogra> but with the recent kernel i have it complaining about my firmware being to old
[11:43] <st3> with the ubuntu kernel, you mean?
[11:44] <ogra> indeed
[11:44] <st3> that's completely broken
[11:44] <st3> it uses a very old version of -d80211 branch
[11:44] <ogra> i only use ubuntu kernels, i dont have the time for kernel compiling :)
[11:44] <ogra> well, then BenC should update that :)
[11:44] <st3> we received a lot of bug reports from ubuntu users for that kernel version
[11:45] <st3> anyway, could you try to enable debugging options in the kernel?
[11:45] <ogra> dunno, BenC do we have a debug kernel ?
[11:46] <BenC> ogra: There's only small amounts of debug enabled, like softlockup
[11:46] <ogra> shouldnt we have a dbg image for tests ?
[11:47] <ogra> with everything thats possible switched on ?
[11:47] <st3> you could just recompile those modules, btw
[11:47] <ogra> (and a big warning note indeed)
[11:49] <BenC> ogra: Sure, if we want to double the amount of time and diskspace required to do it
[11:49] <BenC> e.g. i386 is already 5 kernels.....doing 10 would be really slow
[11:49] <ogra> indeed
[11:49] <zul> shazbut
[11:50] <ogra> well, i'm back to 2.6.20-5-generic, since -8 doesnt work at all ... -5 was completely stable, i havent seen any oopses with it
[11:51] <st3> what does it mean translated to vanilla naming scheme?
[11:54] <st3> so you didn't get that oops with the kernel you call -5, right?
[11:55] <ogra> thats the package version ...
[11:55] <ogra> right, i dot get them with the older version
[11:55] <st3> which i can assume is plain 2.6.20, no git snapshot, right?
[11:56] <ogra> i know BenC added some fixes during the oslo sprint so these might be the ones fixing it for me
[11:56] <st3> isn't there a changelog or something like that?
[11:56] <ogra> they must have appeared between -3 and -5 ....
[11:56] <BenC> st3: in git, debian/changelog
[11:56] <ogra> i think there is even a git tree
[11:57] <st3> is there a gitweb setup somewhere?
[11:57] <st3> (sorry, but i never used ubuntu, i'm not used to this)
[11:58] <st3> ah ok found it
[12:08] <st3> well, i can't find any related commit in git
[12:08] <st3> if you want to help, please send bug reports with debugging info to<EMAIL_ADDRESS>and stating exactly what kernel are you using, thank you
[12:08] <st3> bye
[12:12] <BenC> st3: Our git is available from kernel.org
[12:13] <st3> i saw it
[12:14] <st3> http://www.kernel.org/git/?p=linux/kernel/git/bcollins/ubuntu-2.6.git;a=summary isn't it?


[00:04] -queuebot:#ubuntu-release- New binary: rust-gix-glob [riscv64] (noble-proposed/universe) [0.14.0-1] (no packageset)
[00:04] -queuebot:#ubuntu-release- New binary: rust-gix-url [riscv64] (noble-proposed/universe) [0.25.1-1] (no packageset)
[00:05] -queuebot:#ubuntu-release- New binary: rust-gix-fs [riscv64] (noble-proposed/universe) [0.8.0-1] (no packageset)
[00:06] -queuebot:#ubuntu-release- New binary: rust-p384 [riscv64] (noble-proposed/universe) [0.13.0-1] (no packageset)
[00:10] -queuebot:#ubuntu-release- New binary: rust-usb-ids [riscv64] (noble-proposed/universe) [1.2023.7-1] (no packageset)
[01:52] -queuebot:#ubuntu-release- New binary: rustc [riscv64] (noble-proposed/main) [1.72.1+dfsg0ubuntu1-0ubuntu1] (i386-whitelist)
[08:54] <schopin> ubuntu-archive: could an AA publish the rustc binaries currently in the queue? (I have 1.73 ready to upload, it just needs 1.72 available first)
[09:15] -queuebot:#ubuntu-release- New: accepted cowsql [s390x] (noble-proposed) [1.15.3-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-command [s390x] (noble-proposed) [0.2.10-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-fs [s390x] (noble-proposed) [0.8.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-glob [armhf] (noble-proposed) [0.14.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-glob [riscv64] (noble-proposed) [0.14.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-url [arm64] (noble-proposed) [0.25.1-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-url [ppc64el] (noble-proposed) [0.25.1-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-orion [armhf] (noble-proposed) [0.17.6-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-orion [riscv64] (noble-proposed) [0.17.6-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-p384 [arm64] (noble-proposed) [0.13.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-command [riscv64] (noble-proposed) [0.2.10-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-glob [arm64] (noble-proposed) [0.14.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-glob [s390x] (noble-proposed) [0.14.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-url [riscv64] (noble-proposed) [0.25.1-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-orion [s390x] (noble-proposed) [0.17.6-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-p384 [ppc64el] (noble-proposed) [0.13.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-p384 [s390x] (noble-proposed) [0.13.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-usb-ids [armhf] (noble-proposed) [1.2023.7-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-usb-ids [riscv64] (noble-proposed) [1.2023.7-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rustc [riscv64] (noble-proposed) [1.72.1+dfsg0ubuntu1-0ubuntu1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-fs [riscv64] (noble-proposed) [0.8.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-url [armhf] (noble-proposed) [0.25.1-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-p384 [armhf] (noble-proposed) [0.13.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-usb-ids [arm64] (noble-proposed) [1.2023.7-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-usb-ids [s390x] (noble-proposed) [1.2023.7-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-glob [ppc64el] (noble-proposed) [0.14.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-p384 [riscv64] (noble-proposed) [0.13.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-orion [ppc64el] (noble-proposed) [0.17.6-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-usb-ids [ppc64el] (noble-proposed) [1.2023.7-1]
[09:15] -queuebot:#ubuntu-release- New: accepted cowsql [amd64] (noble-proposed) [1.15.3-1]
[09:15] -queuebot:#ubuntu-release- New: accepted cowsql [armhf] (noble-proposed) [1.15.3-1]
[09:15] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-535 [amd64] (noble-proposed) [535.146.02-0ubuntu1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-command [amd64] (noble-proposed) [0.2.10-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-command [armhf] (noble-proposed) [0.2.10-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-fs [amd64] (noble-proposed) [0.8.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-fs [armhf] (noble-proposed) [0.8.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-glob [amd64] (noble-proposed) [0.14.0-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-url [s390x] (noble-proposed) [0.25.1-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-orion [arm64] (noble-proposed) [0.17.6-1]
[09:15] -queuebot:#ubuntu-release- New: accepted cowsql [arm64] (noble-proposed) [1.15.3-1]
[09:15] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-535 [arm64] (noble-proposed) [535.146.02-0ubuntu1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-command [ppc64el] (noble-proposed) [0.2.10-1]
[09:15] -queuebot:#ubuntu-release- New: accepted rust-gix-fs [ppc64el] (noble-proposed) [0.8.0-1]
[09:16] -queuebot:#ubuntu-release- New: accepted rust-orion [amd64] (noble-proposed) [0.17.6-1]
[09:16] -queuebot:#ubuntu-release- New: accepted rust-usb-ids [amd64] (noble-proposed) [1.2023.7-1]
[09:16] -queuebot:#ubuntu-release- New: accepted rustc [arm64] (noble-proposed) [1.72.1+dfsg0ubuntu1-0ubuntu1]
[09:16] -queuebot:#ubuntu-release- New: accepted tinygltf [arm64] (noble-proposed) [2.8.19+dfsg-1]
[09:16] -queuebot:#ubuntu-release- New: accepted tinygltf [ppc64el] (noble-proposed) [2.8.19+dfsg-1]
[09:16] -queuebot:#ubuntu-release- New: accepted tinygltf [s390x] (noble-proposed) [2.8.19+dfsg-1]
[09:16] -queuebot:#ubuntu-release- New: accepted cowsql [ppc64el] (noble-proposed) [1.15.3-1]
[09:16] -queuebot:#ubuntu-release- New: accepted rust-gix-fs [arm64] (noble-proposed) [0.8.0-1]
[09:16] -queuebot:#ubuntu-release- New: accepted rust-p384 [amd64] (noble-proposed) [0.13.0-1]
[09:16] -queuebot:#ubuntu-release- New: accepted rustc [s390x] (noble-proposed) [1.72.1+dfsg0ubuntu1-0ubuntu1]
[09:16] -queuebot:#ubuntu-release- New: accepted tinygltf [riscv64] (noble-proposed) [2.8.19+dfsg-1]
[09:16] -queuebot:#ubuntu-release- New: accepted rust-gix-command [arm64] (noble-proposed) [0.2.10-1]
[09:16] -queuebot:#ubuntu-release- New: accepted rustc [amd64] (noble-proposed) [1.72.1+dfsg0ubuntu1-0ubuntu1]
[09:16] -queuebot:#ubuntu-release- New: accepted rust-gix-url [amd64] (noble-proposed) [0.25.1-1]
[09:16] -queuebot:#ubuntu-release- New: accepted tinygltf [armhf] (noble-proposed) [2.8.19+dfsg-1]
[09:16] -queuebot:#ubuntu-release- New: accepted rustc [armhf] (noble-proposed) [1.72.1+dfsg0ubuntu1-0ubuntu1]
[09:16] -queuebot:#ubuntu-release- New: accepted rustc [ppc64el] (noble-proposed) [1.72.1+dfsg0ubuntu1-0ubuntu1]
[09:16] -queuebot:#ubuntu-release- New: accepted rustc [i386] (noble-proposed) [1.72.1+dfsg0ubuntu1-0ubuntu1]
[09:16] -queuebot:#ubuntu-release- New: accepted tinygltf [amd64] (noble-proposed) [2.8.19+dfsg-1]
[11:49] -queuebot:#ubuntu-release- New binary: rust-pasetors [amd64] (noble-proposed/universe) [0.6.7-1] (no packageset)
[11:49] -queuebot:#ubuntu-release- New binary: rust-pasetors [s390x] (noble-proposed/universe) [0.6.7-1] (no packageset)
[11:50] -queuebot:#ubuntu-release- New binary: rust-pasetors [arm64] (noble-proposed/universe) [0.6.7-1] (no packageset)
[11:51] -queuebot:#ubuntu-release- New binary: rust-pasetors [armhf] (noble-proposed/universe) [0.6.7-1] (no packageset)
[11:52] -queuebot:#ubuntu-release- New binary: rust-pasetors [ppc64el] (noble-proposed/universe) [0.6.7-1] (no packageset)
[12:00] -queuebot:#ubuntu-release- New binary: rust-pasetors [riscv64] (noble-proposed/universe) [0.6.7-1] (no packageset)
[12:26] <ahasenack> jbicha: hi, there is a bit of reluctance in releasing "big" desktop packages today, due to the shutdown, because if we have to revert, we might have to scramble
[12:26] <ahasenack> jbicha: do you have a preference on what should be released first? fonts-noto-color-emoji  will be released today
[12:29] <jbicha> ahasenack: I think osinfo-db should be low risk. Mutter has some fixes that people have been asking for
[12:29] -queuebot:#ubuntu-release- New: accepted rust-pasetors [amd64] (noble-proposed) [0.6.7-1]
[12:29] -queuebot:#ubuntu-release- New: accepted rust-pasetors [armhf] (noble-proposed) [0.6.7-1]
[12:29] -queuebot:#ubuntu-release- New: accepted rust-pasetors [riscv64] (noble-proposed) [0.6.7-1]
[12:29] -queuebot:#ubuntu-release- New: accepted rust-pasetors [arm64] (noble-proposed) [0.6.7-1]
[12:29] -queuebot:#ubuntu-release- New: accepted rust-pasetors [s390x] (noble-proposed) [0.6.7-1]
[12:29] -queuebot:#ubuntu-release- New: accepted rust-pasetors [ppc64el] (noble-proposed) [0.6.7-1]
[12:30] <ahasenack> jbicha: is mutter detangled from gnome-shell in this batch?
[12:30] <jbicha> gnome-characters will need to wait until January because I want the emoji font phased to 100% first
[12:30] <jbicha> ahasenack: yes
[13:01] -queuebot:#ubuntu-release- New binary: rustc [i386] (noble-proposed/main) [1.73.0+dfsg0ubuntu1-0ubuntu1] (i386-whitelist)
[13:32] -queuebot:#ubuntu-release- New binary: rustc [s390x] (noble-proposed/main) [1.73.0+dfsg0ubuntu1-0ubuntu1] (i386-whitelist)
[13:33] -queuebot:#ubuntu-release- New binary: rustc [amd64] (noble-proposed/main) [1.73.0+dfsg0ubuntu1-0ubuntu1] (i386-whitelist)
[13:33] -queuebot:#ubuntu-release- New binary: rustc [ppc64el] (noble-proposed/main) [1.73.0+dfsg0ubuntu1-0ubuntu1] (i386-whitelist)
[14:45] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (mantic-proposed) [23.10.57]
[14:58] -queuebot:#ubuntu-release- Unapproved: accepted alacarte [source] (lunar-proposed) [3.44.2-1ubuntu0.1]
[14:59] -queuebot:#ubuntu-release- Unapproved: accepted alacarte [source] (jammy-proposed) [3.44.1-1ubuntu0.1]
[15:55] -queuebot:#ubuntu-release- New binary: rustc [arm64] (noble-proposed/main) [1.73.0+dfsg0ubuntu1-0ubuntu1] (i386-whitelist)
[16:23] <ricotz> apw, hi, please note that the nvidia-graphics-drivers-535 update for jammy is missing
[16:23] <ricotz> https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535
[17:19] <xnox> ricotz: i'm not too sure, but i think that is intentional for now, i think that update is delayed until next year.
[17:19] <xnox> cc: apw
[17:23] -queuebot:#ubuntu-release- New: accepted rustc [amd64] (noble-proposed) [1.73.0+dfsg0ubuntu1-0ubuntu1]
[17:23] -queuebot:#ubuntu-release- New: accepted rustc [i386] (noble-proposed) [1.73.0+dfsg0ubuntu1-0ubuntu1]
[17:23] -queuebot:#ubuntu-release- New: accepted rustc [s390x] (noble-proposed) [1.73.0+dfsg0ubuntu1-0ubuntu1]
[17:23] -queuebot:#ubuntu-release- New: accepted rustc [arm64] (noble-proposed) [1.73.0+dfsg0ubuntu1-0ubuntu1]
[17:23] -queuebot:#ubuntu-release- New: accepted rustc [ppc64el] (noble-proposed) [1.73.0+dfsg0ubuntu1-0ubuntu1]
[17:23] <ricotz> xnox, seems weird to be intentionally without any mention in https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2045913
[17:23] -ubottu:#ubuntu-release- Launchpad bug 2045913 in nvidia-graphics-drivers-535 (Ubuntu Mantic) "Update the NVIDIA 535 driver" [High, In Progress]
[18:16] <xnox> will check things
[18:45] -queuebot:#ubuntu-release- Unapproved: rejected guice [source] (focal-proposed) [4.2.1-1ubuntu0.1~20.04]
[18:45] -queuebot:#ubuntu-release- Unapproved: rejected maven [source] (focal-proposed) [3.6.3-1ubuntu0.1~20.04]
[19:32] -queuebot:#ubuntu-release- Unapproved: maven (focal-proposed/universe) [3.6.3-1 => 3.6.3-1ubuntu0.1] (i386-whitelist)
[19:33] -queuebot:#ubuntu-release- Unapproved: guice (focal-proposed/universe) [4.2.1-1 => 4.2.1-1ubuntu0.1] (i386-whitelist)
[19:36] -queuebot:#ubuntu-release- Unapproved: accepted maven [source] (focal-proposed) [3.6.3-1ubuntu0.1]
[19:37] -queuebot:#ubuntu-release- Unapproved: accepted guice [source] (focal-proposed) [4.2.1-1ubuntu0.1]
[20:17] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-desktop-icons-ng [source] (mantic-proposed) [46+really47.0.7-0ubuntu1]
[21:06] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell [source] (focal-proposed) [3.36.9-0ubuntu<IP_ADDRESS>]
[21:09] <tsimonq2> +
[21:09] <tsimonq2> Whoooops.
[21:35] -queuebot:#ubuntu-release- Unapproved: impressive (jammy-proposed/universe) [0.13.0~beta2-2 => 0.13.0~beta2-2ubuntu0.1] (no packageset)


 Whooaa .. someone somewhere done a lot of homework to make that happen .
[18:15] <lotuspsychje> this1 is like interesting to send to your friends email :p
[18:39] <lotuspsychje> http://news.softpedia.com/news/you-can-now-install-discord-app-as-a-snap-on-ubuntu-other-gnu-linux-distros-515473.shtml
[18:39] <lotuspsychje> interesting snap
[18:45] <lotuspsychje> !snap
[18:45] <lotuspsychje> !snapd
[18:45] <lotuspsychje> !snappy
[18:45] <ubot5`> Ubuntu Core is a rendition of Ubuntu with transactional updates using "snappy". For discussion and support, please visit #snappy and see http://www.ubuntu.com/snappy/
[18:46] <lotuspsychje> would it be cool to add https://uappexplorer.com/apps?type=snappy latest snaps to trigger?
[18:49] <lotuspsychje> nacc: this the app that guy talking about? https://uappexplorer.com/app/acestreamplayer.vs
[18:50] <nacc> lotuspsychje: yeah it's on my todo list :)
[18:50] <nacc> lotuspsychje: it takes some effort to teach the bot about it
[18:54] <lotuspsychje> 865 snaps dear lord
[18:55] <nacc> lotuspsychje: yeah
[18:55] <nacc> lotuspsychje: and it's only going to grow for now
[18:56] <lotuspsychje> nacc: i was trying to find a way to show latest snaps..now i got it :p
[18:57] <lotuspsychje> still weird to see uappexplorer when ubuntu-touch gonna end..
[19:12] <lotuspsychje> bbl guys, have a nice evening


[10:18] <Hamidreza>  Hi, I would appreciate if someone help me on this : https://pastebin.ubuntu.com/p/VwVWMG39cf/
[10:50] <RoyK> Hamidreza: check the output of ss - netstat is deprecated - anyway, I guess this just means it's listening to both protocols, which sometimes show they are merged, somehow. You really cannot connect to ipv4 with ipv6. That'll be like talking greenlandic to an englishman - doesn't work too well…
[10:52] <Hamidreza> RoyK, so why it is binding like this? I'm giving the program the exact name
[12:19] <RoyK> Hamidreza: did you check output from ss?
[13:13] <qman__> Hamidreza: linux supports a feature where programs can bind on both ipv4 and ipv6 on the same port, and it shows up as an ipv6 bind, but the kernel still accepts ipv4 connections
[13:13] <qman__> the weirder thing in your post is that you have two binds on the same port, which should be impossible
[13:13] <qman__> also, ss is a drop-in replacement for netstat, accepts the same arguments, the output is slightly different though
[13:14] <sigv> qman__: SO_REUSEPORT allows re-using a port since Linux 3.9: https://lwn.net/Articles/542629/
[13:18] <qman__> strange, but ok
[13:20] <qman__> in any case, Hamidreza, the app shown there is binding on *:8080, using the aforementioned feature, so the bind shows up as :::8080 and is dual stack
[13:21] <qman__> 8080 is typically used as an HTTP alternative port, so I wouldn't expect a database to use it, but it's not impossible; if it is, though, it's not binding on a specific IP, it's binding on any IP
[13:51] <cpaelzer> ijohnson: glad I could help with that apparmor issue
[13:52] <cpaelzer> ijohnson: is there any further follow on needed from me?
[13:54] <ijohnson> cpaelzer: hello, no I think I'm good I know what the issue is and how to work around it now, so everything is good again for me :-)
[13:54] <ijohnson> well at least when it comes to using swtpm + qemu, the rest of the world maybe not quite so positive, but that's an orthogonal concern :-)
[14:13] <teward> cpaelzer: ping
[14:18] <RoyK> qman__: it's not impossible to bind to a single port when the source port is different
[14:20] <RoyK> qman__: otherwise, large webservers would be all singlethreaded
[14:20] <qman__> binding to a listening port doesn't specify a remote source
[14:21] <RoyK> qman__: bind() ; fork()
[14:22] <qman__> the remote side is *
[14:22] <qman__> the scenario you describe is not relevant here
[15:36] <jamespage> smb: about? I have a bcache related question
[15:37] <jamespage> when the bcache gc thread runs bcache pauses all frontend IOPS until its completed - but I can't tell whether thats tied to the cache device, pausing IO's to all backing devices it supports, or tied to each backing device
[15:46] <smb> jamespage, about yes, but I could not answer that question from the top of my head. With stacked devices it could also be the throttling mechanism that somehow tries to limit IO in when the backing device is slow
[17:04] <ThothCastel> for a home/lab network where linux/mac/win10pro are present on the same network....  to make use of 'LDAP like'  authentication, is Ubuntu Server best for that or is it best to run Samba 4 as opposed to enabling the 'ldap server' side  of ubuntu?
[17:08] <ThothCastel> or actually is ubuntu domain controller based on samba 4?
[22:35] <qman__> ThothCastel: if you want proper windows support, you need a samba 4 AD DC - I'm not sure what that option does, exactly, there's a few different possibilities


[00:13] <doctormo> Ah found it, backports-modules damn it
[00:23] <ogasawara> rtg: so doko submitted bug 285779 yesterday.  patch is upstream to cherrypick.  what's the possibility of getting it into Intrepid prior to Intrepid final or will it need to wait as an SRU post Intrepid release?
[01:47] <TheMuso> Does anybody know how I may be able to debug an ExpressCard slot that seems to not be hot-pluggable in Linux? shpchp is loaded, but I have to start Linux with an ExpressCard in the slot for it to be detected and its driver loaded.
[02:25] <rtg> ogasawara: the xfs barrier detection patch is in <IP_ADDRESS>, all of which I cherry-picked last night.
[02:25] <ogasawara> rtg: ok cool.  thanks
[02:25] <rtg> wandering off now...
[06:11] <nigel_c> Apart from adding/removing/changing symbol exports, does anything else affect the ABI?
[08:18] <amitk> Ng: the boot crashes seem to automagically disappeared with the fix for e100e...
[08:36] <nigel_c> NCommander: got it building; thanks for the pointer. Now I'm seeking to figure out abi issues (as you'll see from above)
[09:09] <abogani> amitk: Sorry to bother you. I have a little question about lrm: Who could help me?
[09:12] <amitk> abogani: what is it about?
[09:13] <abogani> amitk: In debian/copyright i can find right information about broadcom and ltmodem but nothing about madwifi.
[09:15] <abogani> I know it is a silly thing but my package is blocked by that!
[09:16] <amitk> abogani: i though BenC fixed the copyright in the last upload. Maybe it still needs work
[09:18] <abogani> amitk: Where you downloaded that code? www.madwifi.org?
[09:20] <amitk> abogani: yes
[09:20] <abogani> amitk: Thanks. Sorry for disturb.
[09:20] <amitk> abogani: no worries
[09:25] <Ng> amitk: yeah, I guess it kinda makes sense that yanking a weird corruption causing bug settles down some other weird corruption issues :)
[09:25] <Ng> so now I'm down to just two weird bugs :)
[12:55] <NCommander> amitk, hola
[13:06] <amitk> NCommander: ahoy
[13:11] <NCommander> amitk, I plan on attending today kernel team meeting, SHould I add my work on the ports and lpia kernel to the team reports page?
[13:12] <amitk> NCommander: Team reports are generally meant for Canonical kernel developers to let community know what we've been upto
[13:13] <NCommander> I see.
[13:13] <amitk> But you could add a line to meeting agenda regarding your work on ports
[13:14] <amitk> and announce your intentions so that other developers know whats coming and there is less duplication of effort
[13:15] <rtg> amitk: are you having any success with ath5k?
[13:15] <NCommander> amitk, if I wish to apply to the kernel team, does that get brought up at the meaning or ...?
[13:16] <amitk> rtg: not really. We need new stuff from upstream. Are you done yet? :)
[13:16] <amitk> NCommander: wish to apply as in get an account on kernel.u.c?
[13:17] <rtg> amitk: I uploaded LBM, but I'm not sure its much better. I need to work on some key repeat issues today, so don't know if I'll get to it.
[13:18] <amitk> rtg: ar2424 loads up both ath5k and madwifi. Do we check for PCI id uniqueness in our driver lists? modules.alias perhaps?
[13:18] <NCommander> amitk, well, isn't that what kernel team membership is?
[13:18] <amitk> NCommander: BenC has already mentioned he is handling your account creation, right?
[13:19] <NCommander> right, but I didn't know if this was like other teams where you had to be formally voted in or
[13:19]  * NCommander should just say he's extremely lost ;-)
[13:19] <rtg> amitk: there is no PCI uniqueness, which is kind of a problem. you don't know if madwifi supports the NIC until it looks at the RF chip.
[13:19] <amitk> NCommander: no it isnt. It will be done. Account creation processes take some time.
[13:19] <NCommander> oh, ok
[13:20]  * NCommander knew it took time, just wanted to make sure there wasn't nothing else I had to do
[13:20] <NCommander> I look forward to improving ports :-)
[13:20] <amitk> NCommander: I mean there is no voting. You have been 'approved' :)
[13:20] <NCommander> woooo
[13:20] <NCommander> amitk, and now ports has a <IP_ADDRESS> based kernel
[13:21] <rtg> amitk: do you know of the madwifi DKMS package on my PPA? It _does_ support the AR2424.
[13:21] <NCommander> so if it gets merged into the main line, it will be a matter of rebase and then merge
[13:21] <NCommander> (or life is easy)
[13:22] <amitk> rtg: i didn't know of DKMS package. But madwifi isn't a problem. Samsung Q1 AR2424 works with madwifi; doesn't with ath5k.
[13:22] <rtg> amitk: ah, ok. I'll be the ath5k ANI is failing to converge and it resets all of time?
[13:22] <amitk> rtg: on the other hand, the AR2425 chip on EEE PC seems to have same PCI id, but it works with ath5k
[13:23] <amitk> so I can't even remove that PCI id from the ath5k driver
[13:23] <amitk> rtg: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/284354
[13:23] <rtg> amitk: you might have to have a blacklist file specific to the platform. ugh!
[13:25] <amitk> rtg: how do I blacklist by platform? Do you mean add a blacklist-samsungq1 file in /etc/modprobe.d ?
[13:26] <rtg> amitk: Are you creating an image for this unit? Or is it running the standard distro install?
[13:27] <amitk> rtg: separate image. So you want to stuff a blacklist file into /etc/modprobe.d somewhere?
[13:28] <amitk> no way to do this in code then
[13:29] <rtg> amitk: yep - you'll have to have a patch in module-utils-init that blacklists the ath5k, but this only works if the image is unique to the samsungq1.
[13:30] <amitk> rtg: it is a generic mobile image :-/
[13:30] <rtg> hmm, that is a problem.
[13:31] <rtg> amitk: you said ath5k _does_ work for some AR chips?
[13:31] <amitk> rtg: AR2425 on eee pc
[13:31] <rtg> amitk: have you tried LBM on the samsungq1?
[13:31] <rtg> we are talking Intrepid, right?
[13:32] <amitk> rtg: intrepid and no lbm attempted yet
[13:33] <amitk> rtg: looks like there are two opposing bugs - 284354 for samsung (madwifi works; ath5k does) and 182489 (ath5k works; madwifi doesn't)
[13:34] <amitk> rtg: and both don't work out of the box since they require to blacklist one or the other driver manually
[13:34] <rtg> hmm, need coffee.
[13:50] <rtg> amitk: maybe this is a case where we need jockey support, e.g., blacklist madwifi by default but allow jockey to change the blacklist to ath5k.
[13:50] <rtg> similar to the wl driver dilemma.
[13:55] <amitk> rtg: where are the jockey rules that would make the determination?
[13:56] <rtg> amitk: jockey is written by pitti to allow you to make choices as to which driver is used. consider the nVidia case where you have the 2-D and 3-D drivers available.
[13:57] <rtg> Its System->Administration->Hardware Drivers
[13:57] <amitk> rtg: I know about jockey. I was wondering if it can take platform specific rules
[13:58] <rtg> amitk: quirks? I dunno.
[13:58] <rtg> I sure am having Bresnan problems this morning.
[14:05] <amitk> rtg: bresnan? your isp?
[14:06] <rtg> amitk: yep. I had to switch to my alternate route
[14:49] <amitk> 10:46 < slangasek> the comments in bug #284109 say that CONFIG_FTRACE is a performance hit without CONFIG_DYNAMIC_FTRACE,    lieb           even when ftrace is not being used; can anyone confirm that?  Do we need to get CONFIG_FTRACE turned      lool           off for release?
[14:49] <amitk> rtg: ^
[14:49] <amitk> pardon the random nicks in between, cut paste issue
[14:52] <rtg> amitk: CONFIG_DYNAMIC_FTRACE is disabled as of 2.6.27-12
[14:52] <amitk> rtg: CONFIG_FTRACE is being questioned here
[14:52] <apt_get> Hi
[14:52] <rtg> amitk: uh, lemme look.
[14:53] <apt_get> I have two modems USB.   AIKO and YISO.  The 2 connection works.   but no at same time.
[14:53] <apt_get> can I modprobe usbserial two times? for the two vendor cards?
[14:58] <amitk> rtg: lbm fixes my samsung q1 problem. No chance we can get these changes into our kernel?
[15:00] <rtg> amitk: hmm, FTRACE is enabled. can you think of a good reason _not_ to turn it off?
[15:01] <rtg> amitk: if you copy the LBM ath5k over the kernel copy, does it still compile and work?
[15:01] <amitk> rtg: wasn't FTRACE being used by one of the other tracing systems?
[15:02] <amitk> rtg: will copy and test and provide diff if it works
[15:03] <amitk> rtg: no kernel uploads before release?
[15:03] <rtg> amitk: it seems like a total debug feature to me. if its causing performance hits, then I think it has to go.
[15:04] <amitk> rtg: no kernel uploads before release?
[15:05] <rtg> amitk: definitely. I'm think we ought to have one today.
[15:05] <rtg> s/think/thinking/
[15:05] <amitk> BenC1 seemed to disagree ^
[15:06] <rtg> amitk: I was off-channel, so didn't see  his arguments against.
[15:07] <amitk> rtg: he expressed surprise on #ubuntu-devel
[15:07] <amitk> rtg: I figured you would want to get in the stable updates in before release
[15:07] <rtg> amitk: surprise that we might want to upload a kernel?
[15:07] <amitk> rtg: yeah
[15:08] <rtg> BenC needs to get over here and defend himself before I accuse him of smoking drugs.
[15:09] <amitk> rtg: disabling FTRACE might cause an ABI bump though?
[15:09] <rtg> amitk: possibly.
[15:13] <NCommander> amitk, wouldn't have FTRACE on cause some performance hit?
[15:13] <BenC1> rtg: I wasn't arguing against it, just didn't know one was planned
[15:13] <rtg> BenC1: since when do I ever plan anything?
[15:13] <BenC1> rtg: I thought you already disabled ftrace and it wasn't an ABI bump
[15:13] <amitk> NCommander: yes
[15:14] <amitk> BenC1: DYNAMIC_FTRACE != FTRACE
[15:14] <NCommander> amitk, ok, good, I am not loosing my mind
[15:14] <BenC1> Ah
[15:14] <rtg> BenC1: it was CONFIG_HAVE_DYNAMIC_FTRACE
[15:15] <BenC> which is the mechanism that will hopefully replace ptrace one day?
[15:15] <elmo> utrace
[15:16] <rtg> BenC: I think so. That was the presentation Rostedt gave at the plumbers conf
[15:16] <BenC> Am I correct that ftrace in general basically adds padding to function prologue/epilogue to insert instrumentation for debugging?
[15:17] <BenC> or am I thinking of some other debug crud?
[15:17] <rtg> BenC: yep - says it add 5 bytes to the prologue/epilogue
[15:17] <rtg> BenC: I'm thinking we want to turn it off.
[15:18] <BenC> If it doesn't exclude static functions, that sounds like a _huge_ waste of memory in the kernel
[15:18] <rtg> BenC: well, it is a debug function. I wonder how it got turned on in the first place.
[15:18] <BenC> IIRC, amitk asked for it to be turned on :)
[15:19] <rtg> BenC: disabling it is almost guarenteed to cause an ABI bump. I'm test building right now.
[15:19]  * amitk looks at BenC in shock
[15:19] <BenC> amitk: I could be remembering wrong (highly likely)
[15:20] <BenC> I know it was a request from someone, and there were good arguments for it
[15:22] <rtg> I'm sure not finding a log entry from Ubuntu regarding FTRACE.
[15:23] <BenC> pretty sure that was disabled way before intrepid
[15:23] <BenC> I'm wondering if the problem is more of a bad interaction with gcc than in ftrace itself
[15:24] <amitk> BenC: FTRACE wasn't in older 2.6.24 kernels.
[15:26] <BenC> rtg: I totally agree though, kill it
[15:26] <BenC> Although I'm sure it will break whatever userspace tools are there to use it
[15:27]  * NCommander checks to see the -lpia kernel has FTRACE enabled
[15:27] <rtg> BenC: Steve will be really happy about an ABI bump at this late stage (!not).
[15:27] <BenC> He may not even allow it
[15:28] <rtg> I can't see releasing a kerbnel with performance killing cruft in it.
[15:28] <rtg> kernel, even
[15:28] <NCommander> Yup, it does
[15:29] <NCommander> BenC & rtg, want me to go test build the lpia kernels w.o FTRACE?
[15:29] <amitk> Steve was the one who brought up this bug.
[15:29] <rtg> NCommander: can't hurt.
[15:30] <NCommander> yay, more kernel fun :-)
[15:42]  * abogani happy to have already done that work :)
[15:43] <rtg> BenC: looks like disabling FTRACE only removes one symbol (mcount), so we might be able to get by without an ABI bump.
[15:44]  * NCommander is now building the lpia kernels
[15:44] <NCommander> Just to confirm, DYMANIC_FTRACE is ok?
[15:45] <amitk> NCommander: no, turn it off
[15:45] <rtg> DYMANIC_FTRACE == much badness
[15:45]  * NCommander makes it go poof
[15:45] <amitk> NCommander: could you make sure that ports doesn't have it too?
[15:45] <NCommander> I doubt it, ports kernel is old
[15:46]  * NCommander was checking as soon as he got the lpia kernel going
[15:46] <NCommander> my build environment got screwed
[15:47] <BenC> rtg: Nope
[15:47] <BenC> rtg: mcount is most likely used by any module that was compiled against ftrace enabled kernel
[15:47] <NCommander> The ports kernel predates FTRACE
[15:47] <NCommander> (CONFIG_FTRACE IS MIA)
[15:48] <NCommander> Er
[15:48] <NCommander>  If it's runtime disabled
[15:48] <NCommander> (the bootup default), then the overhead of the instructions is very
[15:48] <NCommander> small and not measurable even in micro-benchmarks.
[15:48] <NCommander> (from CONFIG_FTRACE help)
[15:48] <rtg> BenC: so you think LRM/LBM stuff will be affected, huh. I suppose. drat.
[15:49] <NCommander> If its disabled by default on boot-up, do we really need to kill it?
[15:50] <BenC> NCommander: just the added bits to the function are what seem to be causing the problem
[15:50] <NCommander> I must have missed that part
[15:51] <NCommander> Whats the problem specificly :-)?
[15:51] <NCommander> oh, and lpia build underway
[15:51] <BenC> NCommander: ftrace instrumentation is causing random memory corruption problems
[15:51] <NCommander> Ew
[15:51] <BenC> well, not random, but it affects random things
[15:51] <NCommander> Ok, building now, it will take about two hours for the build run to finish
[15:53] <amitk> BenC: No. CONFIG_FTRACE wasn't causing the random corruption. CONFIG_DYNAMIC_FTRACE was. CONFIG_FTRACE was only adding overhead according to bug #284109
[15:54] <rtg> amitk: correct.
[15:54] <BenC> So if CONFIG_FTRACE isn't causing problems, why worry about it before release?
[15:54] <BenC> And what exactly does DYNAMIC_FTRACE do?
[15:54] <rtg> BenC: its not causing problems, just runtime overhead.
[15:54]  * NCommander looks
[15:55] <BenC> rtg: It's immeasurable according to docs
[15:55] <BenC> rtg: Not much more than a bit of memory waste
[15:55] <rtg> BenC: true, but Steve is the one that brought it up.
[15:55] <amitk> BenC: slangasek brought up the bug late last night.
[15:55] <NCommander> I could see FTRACE being usable, and we might be able to avoid an ABI bump if we just disable DYMANIC_FTRACE vs. FTRACE
[15:56] <rtg> BenC: its hard to imagine that it has only negligible impact. its on _every_ fucntion call.
[15:57] <BenC> rtg: but it's a set of nops, IIRC, and any decent CPU can pipeline that right through (no different than our dynamic UP setup for single cpu systems)
[15:58] <amitk> Documentation/ftrace.txt isn't very clear. I quote "If CONFIG_DYNAMIC_FTRACE is set, the system will run with
[15:58] <amitk> virtually no overhead when function tracing is disabled"
[16:00] <rtg> amitk: do you remember the LP bug number?
[16:00] <amitk> bug #284109
[16:00] <amitk> it seems mere speculation in the bug report, no hard numbers.
[16:01] <rtg> amitk: hmm, no real info there.
[16:02] <NCommander> so we kill just FTRACE_DYMANIC, or both FTRACE and FTRACE_DYMANIC?
[16:02] <rtg> BenC, amitk: I'm inclined to leave it alone until someone can prove or disprove a performance hit.
[16:03] <rtg> NCommander: just CONFIG_DYNAMIC_FTRACE for now
[16:05] <NCommander> With a little luck that will prevent the ABI breakage
[16:05] <amitk> NCommander: DYNAMIC_FTRACE doesn't bump abi
[16:06] <NCommander> THat's what I was hoping :-)
[16:23] <apt_get> I have two modems USB.   AIKO and YISO.  The 2 connection works.   but no at same time.
[16:23] <apt_get> can I modprobe usbserial two times? for the two vendor cards?
[16:26] <jdong> apt_get: the module should making devices for both cards
[16:27] <jdong> modprobing twice doesn't do anything that modprobing once doesn't.
[16:27] <amitk> rtg: diff between in-kernel ath5k and lbm version is quit large. It also depends on changed structures in include/net. So no easy way of just forward porting ath5k driver. It is all or nothing.
[16:27] <amitk> apt_get: do you need to use module params for usbserial?
[16:32] <apt_get> jdong i only can use the device if I 'modprobe usbserial vendor=0x0eab product=0xc893'
[16:33] <apt_get> but the other device use another vender and product
[16:36] <jdong> mm, I see, amitk is on the spot then
[16:37] <apt_get> amitk: can I use the both? at same time?
[16:46] <Keybuk> rtg: I have to send the entire mail, again?
[16:46] <NCommander> brb
[16:54] <rtg> Keybuk: that is what greg k-h prefers. otherwise they have to keep track of it manually.
[16:55] <rtg> Keybuk: also, send it to the maintainer. otherwise it'll just get lost in the merge blizzard
[16:55] <Keybuk> I don't follow
[16:55] <Keybuk> so what should I do?
[16:56] <Keybuk> 1) mail the patch again
[16:56] <Keybuk> 2) cc<EMAIL_ADDRESS>?
[16:56] <Keybuk> 3) cc someone else ?
[16:56] <rtg> Keybuk: add the Cc, change the subject to [PATCH v2], and email it To: the maintainer as well as Cc LKML.
[16:56] <Keybuk> how do I change the subject?  git auto-generates the [PATCH] bit
[16:57] <Keybuk> who is "the maintainer" ?
[16:57] <rtg> The 'Cc<EMAIL_ADDRESS>goes in the bosy of the commit.
[16:57] <rtg> s/bosy/body/
[16:57] <Keybuk> err, wtf?
[16:57] <elmo> it can't go into stable till it's in mainline?
[16:57] <rtg> elmo: correct
[16:57] <Keybuk> Cc goes in the header, no?
[16:57] <elmo> so why are we sending it to stable@ already?
[16:58] <rtg> Keybuk: tell you what, I'll format the patch and send it to you.
[16:58] <apt_get> i´m trying to make the both usb modems work. But or one or other!  at same time i cant do that
[16:59] <rtg> elmo: greg and chris have said they don't want a direct Cc, they prefer that it be in the body of the commit. that way it gets handled automatically.
[17:00] <elmo> rtg: sure.  I just thought you couldn't cc (direct or otherwise) stable until it was accepted into mainline
[17:00] <elmo> rtg: (which this hasn't been, yet, AFAIK?)
[17:00] <rtg> elmo: correct
[17:01] <apw> this allows whomeever merges it to decide if its still stable material, if they do they merge it with the Cc: and the stable people can pick those up programattically from linus' tree, thus only getting stuff which has hit mainline
[17:02] <rtg> Keybuk: the list of maintainers for most subsystems is kept in MAINTAINERS at the root of the kernel tree.
[17:02] <elmo> I'm pretty sure the maintainer for IPMI stuff is still Corey Minyard (sp?)
[17:03] <Keybuk> yes
[17:03] <Keybuk> the guy who's named just above the one line I added in my patch :-/
[17:04] <rtg> Keybuk: hmm, the email that I received did not have his address.
[17:05] <Keybuk> it's in the body ;)
[17:06] <Keybuk> plz wave magick wand to make kernel peeps merge patch kthx :p
[17:07] <rtg> Keybuk: in order for the patch to bubble up into mainline, it generally has to go through the subsystem maintainer. He's not likely to see it on LKML because of the volume, so you have to send it to him directly.
[17:08] <Keybuk> can you do that for me?
[17:08] <rtg> Keybuk: working on it.
[17:17] <apt_get> Cant I modprobe two times usbserial module?   i´m trying to make 2 usb modems work.
[17:17] <mjg59> apt_get: No
[17:17] <apt_get> or I modprobe with onde vendor, or woth another
[17:18] <apt_get> =o(
[17:19] <Keybuk> ben
[17:20] <NCommander> what's beh Keybuk
[17:21] <Keybuk> ww
[17:28] <apw> rtg your hardy-next tree, is that the latest kernel about for hardy or do we have a later one
[17:29] <NCommander> amitk & BenC disabling FTRACE_DYMANIC (without FTRACE) does not break the ABI
[17:29] <rtg> apw: I need to update it since its missing a couple of important patches, e.g. DYNAMIC_FTRACE
[17:30] <NCommander> ^on lpia
[17:31] <NCommander> DO we need any more changes to land in the tree, or should I submit the patchset?
[17:33] <rtg> NCommander: you might have to wait a bit for amitk to return. another 30 minutes perhaps
[17:33] <NCommander> rtg, is lpia going to be folded into the main kernel packages, or is that going to remain separate?
[17:34] <rtg> separate
[17:35] <NCommander> what was the rationale for keeping it separate?
[17:35] <rtg> disparate release schedules between lpia and distro
[17:37]  * NCommander is surprised it didn't get stuck in -ports
[17:37] <rtg> its not community maintained.
[17:37] <elmo> umm, what?
[17:37] <elmo> oh
[17:38] <NCommander> oh
[17:38]  * NCommander is learning a great many things from just two days in #u-kernel
[17:39] <apt_get> exist a way to make usbserial use two diferent devices?? please
[17:40] <apt_get> I remember that with NE2000 old driver we can make a copy of the module and modprobe the second... and make two cards to work together
[17:41] <NCommander> rtg, so if powerpc/sparc may be pulled back into main linux, then does that mean changes w.r.t to the support status on PowerPC and sparc?
[17:41] <BenC> apt_get: it automatically does
[17:42] <BenC> apt_get: I would be surprised if it didn't connect to both devices...it's hot-plug (and thus multidevice) capable
[17:42] <apt_get> no it doesnt
[17:42] <rtg> NCommander: not for the foreseeable future
[17:42] <apt_get> with lsusb  i can see the 2 devices
[17:42] <BenC> apt_get: show me dmesg with both devices connected
[17:42] <apt_get> lsusb
[17:42] <apt_get> Bus 002 Device 003: ID 19d2:fffe
[17:42] <apt_get> Bus 002 Device 002: ID 0eab:c893
[17:42]  * NCommander feels somewhat confused then ....
[17:43] <BenC> apt_get: the old ne2k driver was ISA and also not hot-plug, so that's not even a comparison
[17:43] <apt_get> to make /dev/ttyUSB0 work, I need 'modprobe usbserial vendor=0x0eab product=0xc893'
[17:43] <apt_get> but the other card dont work. because usbserial only see the vendor i had specified
[17:43] <BenC> apt_get: please pastebin dmesg...I can't help much just based on what you are telling me
[17:44] <apt_get> ok
[17:44] <BenC> apt_get: then instead of passing it on the module command line, use the newid file in sysfs for that device
[17:46] <NCommander> rtg, I'm testing the bootability of the linux-lpia kernel, looks good so far
[17:46] <rtg> NCommander: did you ever have any failures while DYNAMIC_FTRACE was enabled?
[17:46] <NCommander> rtg, no
[17:47] <NCommander> Both lpia kernel flavors built fine
[17:48] <apt_get> newid file in sysfs?
[17:50] <BenC> apt_get: new_id
[17:50] <BenC> apt_get: /sys/bus/usb-serial/drivers/generic/new_id
[17:51] <amitk> NCommander: I am going to do a fresh rebase of the lpia kernel on top of the ubuntu intregrated tree once it is prepped for release.
[17:52] <amitk> NCommander: but your Kconfig changes can be applied as a separate patch in the meanwhile
[17:52] <NCommander> amitk, what Kconfig changes? I only changed the config files ...
[17:52] <amitk> NCommander: config file changes == Kconfig changes
[17:53] <NCommander> oh
[17:53] <NCommander> I'm just making sure the image boots right now
[17:57] <NCommander> what was the FTRACE bug number?
[17:58] <amitk> it was the e1000e bug, search for that on LP
[17:58] <NCommander> Oh, that was caused that?!
[17:58] <NCommander> Damn
[18:01] <amitk> meeting in #ubuntu-meeting
[18:46] <mnemo> amitk: I added more info about the patch in this bug --> https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/285572
[18:46] <mnemo> do you think you can push this patch given the additional information?
[18:53] <apt_get> BenC:  its working now.  with option module
[18:53] <apt_get> and with /sys/bus/usb-serial/drivers/option1/new_id  u have said
[18:55] <mnemo> im looking for someone who can help me review and push a tiny kernel patch for intrepid
[18:55] <mnemo> apt_get: do you know how to get stuff merged?
[19:03] <NCommander> That was educational
[19:03] <amitk> mnemo: i am going to add the x server guy on this bug. He has to agree to carry his side of the patch first
[19:05] <mnemo> amitk: bryce harrington has agreed to merge his part if you merge the kernel part
[19:05] <mnemo> bryce is online at irc as well if you want to talk to him (nickname "bryce")
[19:06] <amitk> mnemo: I know bryce :) In that case I can push it in.
[19:07] <mnemo> okay sweet... that's awesome... let's make it happen... :)
[19:08] <NCommander> arg, I closed the meeting window, who was talking about the kernel on arm?
[19:09] <amitk> NCommander: me. busy now. Lets talk next week or something. It isn't urgent
[19:09] <amitk> NCommander: re ARM
[19:12] <NCommander> amitk, I mailed you the lpia patch
[19:17] <amitk> mnemo: patch is in. Go after bryce.
[19:17] <mnemo> will do
[19:19] <rtg> amitk: can you copy the mailing list?
[19:20] <amitk> rtg: umm... I pushed the patch in. Do you want me to post the patch to ML instead?
[19:20] <rtg> amitk: mail it as well, so that it gets some notice.
[19:23] <amitk> rtg: ack
[19:30] <amitk> NCommander: thanks for patch. In future, send all patches to<EMAIL_ADDRESS>so that it doesn't get bottlenecked on me.
[19:31] <amitk> greaaaat
[20:40] <amitk> NCommander: thanks for patch. In future, send all patches to<EMAIL_ADDRESS>so that it doesn't get bottlenecked on me.
[20:41] <NCommander> amitk, alright
[20:43] <GnarusLeo> Hi geeks! I have been using the howto found on "https://help.ubuntu.com/community/Kernel/Compile#Alternate%20Build%20Method:%20The%20Old-Fashioned%20Debian%20Way" for building my own kernel.It is built out of the vanilla kernel. The kernel compiles, and install allright. The problem is when I want to build modules, I get an error of a missing /arch/Makefile_32.cpu" file. After som googling, I found that this is indeed a bug: "https:
[20:43] <GnarusLeo> //bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/195673" Is there any way around, without a real dirty fix? Thanks in advance
[20:44] <GnarusLeo> So the ASM bug posted on that site will be an issue for me as well
[22:13] <kirkland> what's the state of the e1000e driver in intrepid?
[22:15] <rtg> kirkland: its as good as it gets. root cause was DYNAMIC_FTRACE
[22:15] <NCommander> kirkland, I think its been unblacklisted since the issue was FTRACE_DYMANIC
[22:15] <NCommander> lol
[22:17] <kirkland> rtg: NCommander: cool, thanks, guys
[22:18] <NCommander> rtg, did that kernel get uploaded yet?
[22:19] <GnarusLeo> https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/195673 <-- really need a workaround. Anyone got anything? Would be much appriciated
[22:19] <rtg> NCommander: https://edge.launchpad.net/ubuntu/+source/linux
[22:20] <NCommander> nice
[22:21] <rtg> GnarusLeo: looks like to me that you're pointing to the wrong place for headers. It ought to be something like /usr/src/linux-headers-2.6.27-7-generic
[22:23] <GnarusLeo> but its on a custom build?
[22:23] <GnarusLeo> rtg, thanks for answering :)
[22:24] <rtg> GnarusLeo: it looks like you are trying to build against un-prepped headers.
[22:25] <GnarusLeo> so I have to prep the headers? Sounds difficult
[22:25] <rtg> GnarusLeo: what is custom abuot your build?
[22:26] <GnarusLeo> we are building a new kernel based upon  vanilla, for the acer aspire one.
[22:26] <GnarusLeo> and we are really stumped on this
[22:26] <rtg> GnarusLeo: so why is this an Ubuntu problem? Are you starting with an Ubuntu package?
[22:27] <GnarusLeo> rtg, it is a custom kernel built off ubuntu
[22:27] <Syco54645_AAO> ok, GnarusLeo i am here now
[22:27] <GnarusLeo> actually, here is Syco54645, he was the one who actually built it, unfortunally, I have to leave in a few mins
[22:28] <rtg> GnarusLeo: I assume the customization is largely in the .config file?
[22:28] <Syco54645_AAO> and unfortunately i cannot reproduce the error
[22:28] <GnarusLeo> rtg, correct
[22:28] <Syco54645_AAO> rtg: it is completely in the config file, just removed unneeded things
[22:28] <rtg> Syco54645_AAO: did you start with one of the flavours, like generic?
[22:29] <Syco54645_AAO> rtg: i used vanilla from kernel.org
[22:29] <NCommander> oh yay, the powerpc <IP_ADDRESS> doesn't boot
[22:29] <NCommander> wooo
[22:30] <rtg> Syco54645_AAO: are you trying to build an out-of-tree module?
[22:30] <Syco54645_AAO> rtg: i used this to build fakeroot make-kpkg --initrd --append-to-version=-some-string-here kernel-image kernel-headers
[22:31] <Syco54645_AAO> rtg: not sure what you mean by that
[22:31] <GnarusLeo> rtg, he is trying to build just the plain old madwifi drivers
[22:31] <Syco54645_AAO> i did not modufy the source
[22:31] <GnarusLeo> kernel modules
[22:31] <Syco54645_AAO> but yes, trying to build madwifi is where the issue crept up, i assume any module will cause the issue
[22:32] <rtg> ok. madwifi is out of tree,e.g., its not part of the kernel. therefore it must use the correct headers. right?
[22:32] <GnarusLeo> yes
[22:32] <Syco54645_AAO> ah ok, that is what i thought out of tree meant...
[22:33] <GnarusLeo> rtg, actually, neither of us put the bug up on launchpad. It just came up on googling our issue
[22:33] <rtg> then, back to my original point. you have to have the headers package installed for the flavour against which you are building.
[22:34] <Syco54645_AAO> rtg: people did install the headers that were created by my compile, if that is what you meant.
[22:34] <Syco54645_AAO> when i compile, it produces two deb files, one is headers, the other is kernel image
[22:35] <rtg> Syco54645_AAO: so, if you get the Hardy kernel package, then 'debuild -b', you should get a number of .debs
[22:36] <Syco54645_AAO> ok
[22:36] <Syco54645_AAO> i have the generic kernel package on here
[22:36] <Syco54645_AAO> but am not in that kernel, in the one that i built
[22:36] <rtg> Syco54645_AAO: you have to have the Ubuntu kernel package.
[22:37] <Syco54645_AAO> rtg: well i didnt remove it, so it should still be there.  it is in /boot
[22:37] <rtg> Syco54645_AAO: the source package.
[22:38] <rtg> Syco54645_AAO: 'apt-get source linux-image'
[22:39] <GnarusLeo> rtg, why will we need the old kernel headers, if we made new ones?
[22:40] <rtg> GnarusLeo, Syco54645_AAO: maybe you guys ought to read https://wiki.ubuntu.com/KernelMaintenance 'cause I don't think we're on the same page.
[22:42] <Syco54645_AAO> rtg: i am honestly just confused as to why when i compile vanilla and create a header and image deb file and then install it with dpkg i can compile things, but give it out to others and they cannot.  it complains about the makefile_32 file in a location that i do not even have, but again, it works fine for me
[22:42] <rtg> dunno
[22:43] <Syco54645> like gnarusleo said, he found a bug report related to it.  others have found bug reports before related to it but no fixes.
[22:43] <Syco54645> so either i am doing something really wrong and missing something on the kernel compile page of the wiki
[22:43] <Syco54645> or it is missing something
[22:43] <Syco54645> or that method just does not work any longer
[22:43] <rtg> as far as I can tell, it folks trying to do things for which the package was not designed. you're on your own there.
[22:44] <amitk> Syco54645: hmm... can you acutally compile the kernel using this --> fakeroot make-kpkg --initrd --append-to-version=-some-string-here
[22:44] <Syco54645> amitk: that is how i did it, except with "kernel-image kernel-headers" on the end
[22:45] <amitk> Syco54645: that is probably a debian'ism. Not sure if it hits the right targets. Use 'debuild -b' and then report back.
[22:45] <Syco54645> ok
[22:46] <amitk> Syco54645: or 'fakeroot debian/rules binary-custom-<flavourname>' for a single flavour if you are using the custom-binary method
[22:46] <Syco54645_AAO> um said debuild is not there, and that it is not in apt
[22:47] <rtg> yum?
[22:47] <Syco54645_AAO> i am on ubuntu
[22:48] <rtg> sudo apt-get install devscripts
[22:49]  * amitk is outta here... good night folks
[22:49] <Syco54645_AAO> later amitk
[22:49] <pgraner> amitk: night
[22:49] <Syco54645_AAO> rtg: that worked, running debuild -b now
[22:49] <rtg> rtg is outta here
[22:50] <Syco54645_AAO> well debuild failed
[22:50] <Syco54645_AAO> oh well
[22:50] <Syco54645_AAO> ill call it a night there