[00:02] <claydoh> wee http://kubuntuforums.net/forums/index.php?action=dlattach;topic=3118745.0;attach=8877;image
[05:00] <IceMatroX> are you guys working on a reg fix for the AMD FX-8150?
[05:04] <IceMatroX> ?
[05:05] <dtchen> IceMatroX: more context, please?
[05:07] <IceMatroX> some dude posted on his blog that the kubuntu guys where working on a reg fix for the new AMD processors
[05:08] <IceMatroX> http://quinetiam.com/?p=2356
[05:15] <IceMatroX> so is this in the works?
[05:23] <MatroX> ?
[05:25] <MatroX> anyone here?
[08:55]  * afiestas was looking at rekonq announcement when he wondered, what QtWebkit version is kubuntu using?
[08:55]  * afiestas got surprised, 2.2 !!
[08:55] <afiestas> great work !
[10:17] <bambee> hi
[11:41] <apachelogger> afiestas_: didn't you fix bug 872098 at uds?
[11:45] <yofel> apachelogger: do you know who could look at bug 875660?
[11:45] <apachelogger> coling
[11:46] <afiestas_> apachelogger: yes, it should be fixed
[11:46] <afiestas_> if lightdm didn't broke it
[11:46] <yofel> apachelogger: can I go and ping him? And where should the bug on bugs.kde.org go?
[11:47] <apachelogger> yes you can, yes it should
[11:47] <apachelogger> it actually is likely a phonon issue
[11:47] <apachelogger> unless configured otherwise phonon's pulse integration will make the selection
[11:48] <apachelogger> so I'd guess that the pulse kde device module thing is not loaded in time for knotify to start doing things, leading to PA-less knotify which then of course uses alsa based device selection which ends up in a mess
[11:49] <apachelogger> afiestas_: seems robert broke it again then
[11:51] <ulysses> I got a strange open file dialog sometimes: http://people.ubuntu.com/~ulysses/filedialog.png
[11:52] <apachelogger> that is
[11:52] <apachelogger> ehm
[11:52] <apachelogger> interesting
[11:53] <apachelogger> as if the fontmatrix was wrong or something
[11:53] <apachelogger> ulysses: maybe ask in #kde if they have seen this sort of issue before
[11:54]  * apachelogger would think that it is either an issue in dolphin, kdelibs or qt
[11:54] <ulysses> kdelibs or qt, it's in lokalize
[11:56] <ulysses> I can't reproduce in Kate
[11:57] <apachelogger> can you reproduce it everytime with lokalize?
[11:57] <apachelogger> also you are probably right, the filedialog probably does not use the dolphin kpart ^^
[11:57] <ulysses> No, it's total random
[11:59] <apachelogger> ok
[11:59] <apachelogger> kdelibs or qt it is
[12:01] <ulysses> No answer in #kde yet
[12:13] <apachelogger> meh
[12:14] <apachelogger> problem is we cannot even check whether it is qt because qt's file open dialog does not do line breaks it seems
[12:14] <apachelogger> it only elides
[12:14] <apachelogger> oh my
[12:14] <apachelogger> ulysses: try with a different style than oxygen
[12:14] <apachelogger> ulysses: and with a different font than ubuntu
[12:15] <apachelogger> if you can still reproduce the issue we at least know that the problem is not with those two things
[12:20] <ulysses> apachelogger: I changed the plasma them and the font, the issue remains
[12:23] <apachelogger> ulysses: oh, not plasma, the widget style
[12:23] <apachelogger> to plastique perferrably
[12:24]  * apachelogger likes how one review of 11.10 complains about the usage of raster before it was stable
[12:24] <apachelogger> fun fact is: raster has been the reference rendering method for Qt for ages
[12:24] <apachelogger> 4.4 or something
[12:24] <ulysses> no change, with Plastique I can still reproduce
[12:26]  * yofel hasn't gotten any raster issues in 11.10 at all
[12:34] <apachelogger> yofel: because there aren't any :P
[12:34] <yofel> good ;)
[12:35] <apachelogger> people just like to sounds smart by saying things that are wrong but appear very informed to others who do not know that they are wrong :S
[12:35] <apachelogger> ulysses: also after reboot? (plastique + font other than ubuntu)
[12:36] <ulysses> maybe later, I'll go to Szeged soon
[12:47] <apachelogger> kubotu: map szeged, hu
[12:47] <kubotu> http://maps.google.com/maps?f=q&q=szeged,+hu
[12:47]  * apachelogger gets the feeling that using a netbook while it is upgrading is a bad idea
[12:47] <ulysses> :)
[12:48] <ulysses> have to go, see you later
[12:48] <ulysses> o/
[12:48] <apachelogger> o/
[14:53] <ghostcube> any info why kubuntu does not power off in kernel 3.x ? like postet here
[14:53] <ghostcube> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/859075
[14:53] <yofel> shuts down fine here
[14:53]  * yofel goes reading the bug
[15:06] <debfx> ghostcube: what does system settings -> login screen -> shutdown -> halt say?
[15:06] <ghostcube> moment pls
[15:07] <ghostcube> (sbin/halt
[15:07] <debfx> I had a similar problem after upgrading to a kde 4.7 beta version that set a wrong halt command
[15:07] <debfx> ghostcube: it should be "/sbin/shutdown -h -P now"
[15:07] <ghostcube> ok i will change it
[15:08] <debfx> ghostcube: have you upgraded from natty to oneiric final or before the release?
[15:09] <ghostcube> as final came out
[15:09] <ghostcube> not beta
[15:09] <yofel> to 4.7 before 4.7.0 ?
[15:09] <ghostcube> yes i get 4.7.0 from ppa
[15:09] <ghostcube> then did an upgrade to omeiric
[15:10] <ghostcube> *n
[15:12] <ghostcube> maybe this should be as a comment inside the bug report?
[15:12] <ghostcube> so everyone noticing this can check this command?
[15:14] <yofel> it is fixed in 4.7.2, but those that already have a wrong command set will probably have to change it by hand
[15:14] <ghostcube> will leave it as comment then
[15:15] <yofel> ghostcube: actually it's fixed in 4.7.1 too
[15:16] <ghostcube> hmm i pull the kde updates from the ppa could be its just there since this time.
[15:16] <ghostcube> but as some other  noticing its for them the same situation
[15:17] <ghostcube> so its better to check for this, as to use this shortvut workarround
[16:22] <ulysses> apachelogger: I tried to reproduce the open file dialog issue on the train with Plastique and Ubuntu font, but I can't
[17:16] <apachelogger> ulysses: sounds very related to oxygen then
[17:16] <ulysses> apachelogger: I guess too
[17:20] <BarkingFish> Aha! One of the people I wanted to speak to is here at least :)  ximion - have you got a couple of minutes to spare please? I'm trying to get hold of the source to packagekit and kpackagekit, and I understand you were the packager.  Do you still have copies of the source files please?
[17:22] <yofel> BarkingFish: you can fetch the archive source with 'apt-get source <package>'
[17:23] <BarkingFish> er, no I can't.  It wants to send me apper instead, which I don't want.  I want the source to kpackagekit prior to the dist upgrade - i.e, before it broke
[17:24] <yofel> BarkingFish: install ubuntu-dev-tools -> pull-lp-source kpackagekit natty
[17:25] <BarkingFish> ok, doing that now.  I need to set up my kit again anyhow, generate some new keys, etc
[17:26] <BarkingFish> kpackagekit will make a return :P
[17:26] <BarkingFish> i practically guarantee it :)
[17:27] <yofel> talk to dantti first what can be improved in apper
[17:28] <yofel> you don't usually resurrect legacy software ;)
[17:29] <BarkingFish> i may not resurrect it, I may just do enough to make it work locally, yofel.
[17:29] <BarkingFish> it'd be nice to have it back, since i now have 3 progs doing the job of one where they were altogether before
[17:34] <ximion> BarkingFish: why exactly do you want kpackagekit back?
[17:34] <ximion> it is really legacy software
[17:35] <ximion> it won't even compile without many modifications
[17:35] <ximion> e.g. you would have to port it to packagekit-qt2 first
[17:35] <ximion> better improve Apper, dantti is always open to new suggestions
[17:36] <ulysses> iirc Apper == KPackageKit, right? just renamed and improved
[17:36] <BarkingFish> ximion, I wanted kpackagekit back because I found apper didn't have the same inbuilt functionality that kpackagekit had - instead of using the one program to install software, get my updates and deal with the software sources, I'm now using three individual progs to do the same job.
[17:37] <BarkingFish> it's a matter of integrating the original functionality of kpackagekit into apper. If that can be done, kpackagekit can stay buried.
[17:38] <ximion> ulysses: yes - Apper ist the non-technical, user-friendly name of KPackageKit
[17:38] <ximion> BarkingFish: it's still one program...
[17:38] <ximion> the Apper KCM
[17:38] <ximion> this tool can handle updates, software sources and packages :)
[17:38] <ximion> there aren't three programs
[17:39] <ximion> GNOME-PackageKit does this, but not Apper...
[17:39] <BarkingFish> So, where are the button links in the interface?
[17:40] <BarkingFish> My primary concern is that transitioning from kpackagekit as I knew it, to apper as it is now, without the same UI, is sort of odd.
[17:40] <yofel> ximion: how do you open software-properties-kde from apper
[17:41] <yofel> ah, nvm
[17:41] <yofel> possible - but rather hard to find
[17:41] <BarkingFish> which it shouldn't be, yofel
[17:42] <BarkingFish> this was the issue with kmail2 - the old interface worked, the new one using akonadi and nepomuk was hardly user friendly. This is no different.
[17:42] <ximion> matter of taste, IMO
[17:42] <BarkingFish> it's a matter of "can a new user find it without having to ask for help?", ximion
[17:42] <ximion> but it's better to modify the interface of Apper as you need than taking KPK as starting point for a new PK-based package manager
[17:43] <BarkingFish> and the answer would be "no" at this point :)
[17:43] <ximion> user sees "Updates" in the main field, and can click on it
[17:43] <ximion> some applies to installed software
[17:43] <ximion> only the settings are a little bit harder to find
[17:44] <BarkingFish> and again, they shouldn't be.  apper would be perfect with the minor modification of putting those 3, easy to spot links back on the left side of the UI.
[17:45] <yofel> IMO it was a better UI layout too
[17:45] <yofel> the current one feels a bit... cramped
[17:45] <BarkingFish> agreed
[17:45] <BarkingFish> it's all shoved into one small space you have to go looking for stuff in.
[17:46] <BarkingFish> yofel, remember the "edit origins" button I was looking for last night?
[17:46] <BarkingFish> I *just* found it
[17:47] <BarkingFish> main UI, click on the spanner in the top right, click settings, select Software origins
[17:48] <yofel> yeah, I only found it just now too
[17:48] <BarkingFish> This is what I should have been able to do direct from the old UI links - not go hunting for it
[17:48] <yofel> as I searched through apper too when you asked
[17:48] <yofel> and back then I never realized there's a little wrench in the corner
[17:48] <BarkingFish> I'll catch dantti at some point, or maybe file this on launchpad as a wish
[17:48]  * yofel isn't a fan of icon-less buttons AND not a fan of text-less buttons unless they're huge
[17:49] <BarkingFish> it needs doing, even if only for the sake of user friendliness. You shouldn't need to look for it, it should be visible "on impact"
[17:53] <ximion> BarkingFish, yofel: The reason to change the layout was to remove the "dead space" of the bug icon bar on the left and make more space available for package & application display
[17:53] <ximion> but you really should talk to dantti about this
[17:54] <ximion> maybe he can do something for Apper 0.7.2
[17:54] <BarkingFish> We can only hope, ximion :)
[17:54] <ximion> for me, the new layout works - but I knew where every option was, so you might be right ^^
[18:02] <BarkingFish> well this is much fun.  I've filled out a wish on the kde bugzilla, and it won't submit :)
[18:04] <BarkingFish> never mind, it's gone through
[18:04] <BarkingFish> yofel, https://bugs.kde.org/show_bug.cgi?id=284209
[18:19] <Kottizen> when I change desktop background I can either load my own picture or get one from kde-look.org; how does the communication between my desktop and kde-look.org work? I'd like to start an own site for that purpose, but offer faster downloads, no ads and no "This refers to an HTML page. Would you like to visit it?"-messages - how would I integrate it with KDE/Kubuntu?
[18:27] <apachelogger> Kottizen: http://www.freedesktop.org/wiki/Specifications/open-collaboration-services
[18:44] <Kottizen> apachelogger: thanks
[19:01] <yofel> apachelogger: did you ever finish fixing kgamma?
[20:06] <cure_> Hi :) i was wondering about the rumor that windows 7 need´s some registry patch so Bulldozer can perform 40-70% faster is this true ?
[20:07] <BarkingFish> cure_, this isn't a windows channel, maybe you could try ##windows
[20:09] <cure_> yes okey im sorry i was told to come here and ask :D
[20:09] <cure_> but thanks anyway
[20:17] <BarkingFish> cure_, who told you to come here and ask?
[20:18] <BarkingFish> We don't and never have dealt with windows, this channel is only for the development of a linux distribution called Kubuntu
[20:19] <sheytan> apachelogger: i used your pic in my adress book for a screenshot on my blog. Is that bad?
[20:19] <cure_> http://kubuntuforums.net/forums/index.php?topic=3118749
[20:20] <cure_> yes okey i didint know better :)
[20:20] <BarkingFish> that thread mentions nothing about windows 7 :)
[20:20] <cure_> pease
[20:21] <cure_> no i was wondering about the bulldozer :) not windows 7 i just put that in my fyrst question
[20:21] <BarkingFish> in that case, it was just confusing :)
[20:21] <BarkingFish> You came and mentioned windows 7, i thought you wanted to know for windows 7...
[20:22] <BarkingFish> I would have no idea about the AMD bulldozer in Kubuntu, so I'll hand that up to the rest of the devs :)  Anyone else have any ideas?
[20:22] <cure_> no just over all :) thank you
[21:03] <BarkingFish> This could be interesting, devs - and I could do with some advice.  How do you file a bug on a package when you don't know what the package is which you need to file a bug against??? :)
[21:04] <BarkingFish> Allow me to explain - there is a user in #kubuntu who is unable to run alsactl store 0 on his sound card, gets told that Home directory /home/george isn't his.  I just tried the same command here and got the same response.
[21:04] <kyofel> a) common sense b) guessing c) thinking hard and guessing again
[21:05] <kyofel> o.O
[21:05] <BarkingFish> I've seen several people over the last day or two in oneiric with this very issue.  But I don't know whether it's a fault with alsactl, with the permissions settings, something else...
[21:06] <kyofel> BarkingFish: sudo alsactl... or without sudo?
[21:06] <BarkingFish> with sudo
[21:06] <BarkingFish> without sudo you get cannot open /var/lib/asound.state - Permission denied
[21:06] <kyofel> true, confirmed
[21:07] <BarkingFish> to be exact, you get: alsactl: save_state:1547: Cannot open /var/lib/alsa/asound.state for writing: Permission denied
[21:07] <kyofel> BarkingFish: workaround: sudo -i -> then run alsactl store 0 as root
[21:08] <BarkingFish> No protocol specified
[21:08] <BarkingFish> xcb_connection_has_error() returned true
[21:08] <BarkingFish> brb
[21:08] <kyofel> note: I have no idea what that is actually supposed to do
[21:10] <BarkingFish> what, the alsactl command?
[21:10] <BarkingFish> or sudo -i?
[21:11] <kyofel> alsactl store 0
[21:11] <BarkingFish> right, it stores the last state of the soundcard at 0 - volume, muted channels, etc
[21:12] <BarkingFish> and restores them next time you use the soundcard
[21:14] <BarkingFish> So at least we know it's happening - I'll file it as a bug on the launchpad and we can go from there.
[21:43] <apachelogger> sheytan: technically I could sue you :P
[21:44] <apachelogger> but as long as it is a pic of me nakkid I won't  :P
[21:45] <sheytan> apachelogger: thank you!
[21:45] <sheytan> btw, nothing came out from my cover :(
[21:45] <apachelogger> also I do not understand the blog language so I couldn't know if you write something nice in addition to violating my copyright on my own picture :P
[21:46] <apachelogger> sheytan: cover?
[21:46] <apachelogger> what cover? where cover? what for? where to? how so?
[21:46]  * apachelogger should be in bed
[21:46] <sheytan> It's a nice article about google and kontact :)
[21:46] <sheytan> cd cover for kubuntu
[21:46] <sheytan> i sent it to you :(
[21:47] <apachelogger> oh, what mail?
[21:48] <apachelogger> don't you know that you are supposed to tell me when you send something by mail because apachelogger never reads mails unless he gets told to? :P
[21:48] <sheytan> apachelogger: i sent a link to it, here, on kubuntu-devel and to you on priv
[21:48] <sheytan> and pinged you couple of times
[21:49] <apachelogger> hm
[21:49] <apachelogger> I only see a pink pyth0rn in the query
[21:49] <apachelogger> anywho
[21:49]  * apachelogger does not know what to do with the cover
[21:49] <apachelogger> sheytan: what do you want to do with the cover?
[21:50] <sheytan> apachelogger: sometime ago you showed me a oneiric todo, where was madsheytan: do kubuntu cd cover, which i didn't know about. So i said i will anyway and i did. Then it got all released.
[21:51] <apachelogger> hm
[21:51] <apachelogger> sheytan: I do very much believe that this should have been done at least 1 week prior to release
[21:51] <sheytan> let me atleast show it to ya :)
[21:52] <apachelogger> the cover is primarily used on the CDs canonical sells in the shop and sends to locos
[21:52] <sheytan> i did it few days before
[21:52] <apachelogger> oh well
[21:52] <apachelogger> sheytan: try getting in touch with the canonical design team
[21:52] <apachelogger> they will know all about it
[21:52] <sheytan> apachelogger: leave it for next relelase :)
[21:53] <apachelogger> sheytan: even so I'd contact canonical design *now* and find out what to do and just about when the gfx need to be done
[21:54] <apachelogger> that way we can make sure it gets done in time and forwarded to the right people at the right time
[21:55] <apachelogger> sheytan: https://launchpad.net/~canonical-ux/+members
[21:55] <apachelogger> try anyone from here
[21:55] <sheytan> i will, but not today :)
[21:55] <apachelogger> sheytan: do you ahve the graphics at hand?
[21:56] <apachelogger> cause I am about to go back to bed, so you'd better hurry showing them to me :P
[21:56] <sheytan> apachelogger: i bet you'll wait :D
[21:58] <sheytan> http://img12.imageshack.us/img12/6359/front2ns.jpg
[21:59] <apachelogger> very nice
[21:59]  * sheytan is glad :)
[21:59] <apachelogger> sheytan: though, a backgroundish thing behind the kubuntu text would be even better
[21:59] <apachelogger> right now kubuntu and the circle have a bit of a contrast war going on
[22:00] <sheytan> ill tune it for the next release
[22:00] <sheytan> even started a list with things that i'm worried about and how to fix it :)
[22:00] <sheytan> where's the  upcoming uds?
[22:00] <apachelogger> oh, btw, I can tell you for sure that a back design is necessary etc
[22:00] <sheytan> i mean where will be
[22:00] <apachelogger> also see https://wiki.ubuntu.com/DIYMarketing#A11.10_artwork
[22:00] <sheytan> what ya mean with 'backdesign'?
[22:01] <apachelogger> back of the cd cover
[22:01] <apachelogger> next uds is in orlando
[22:01] <sheytan> already got it :)
[22:01] <apachelogger> the uds in may is not yet decided
[22:01] <apachelogger> (though I reckon chances are it is going to be in budapest)
[22:02] <apachelogger> which is very healthy for my wallet
[22:02] <apachelogger> anywho
[22:02] <apachelogger> -> be
[22:02] <apachelogger> d
[22:02] <apachelogger> nini
[22:03] <sheytan> damn
[22:03]  * kyofel is off to bed too
[22:03] <sheytan> to far
[22:03] <kyofel> gn
[22:03] <sheytan> germany or czech would be perfect for me
[22:03] <sheytan> or poland ;d
[22:03] <sheytan> then i could come with my car
[22:04] <kyofel> budapest isn't that much further...
[22:05] <sheytan> it's like 700km from my place
[22:05] <sheytan> how long does uds take?
[22:06] <kyofel> a week
[22:06] <kyofel> and I drove ~600KM to get to the desktop summit this year
[22:06] <sheytan> like 7 days?
[22:07] <kyofel> hm, more like 5 IIRC
[22:07] <sheytan> but how come it's in may, when ubuntu gets released in april?
[22:07] <kyofel> mon-fri
[22:07] <kyofel> sheytan: it's always 2-3 weeks post-release
[22:08] <sheytan> which means 2-3 after relelase?
[22:08] <kyofel> yeah
[22:09] <sheytan> so the upcoming one should be like in december not may next year?
[22:09] <kyofel> sheytan: may next year is UDS for 12.10
[22:09] <kyofel> uds-p is
[22:09] <kyofel> !uds
[22:09] <sheytan> oh, so US, no, thank you :)
[22:10] <sheytan> maybe next time
[22:10] <kyofel> I hope I'll be able to make it to UDS-Q, but we'll see
[22:11] <sheytan> kyofel whats the difference between uds and uds-q?
[22:12] <kyofel> sheytan: q = whatever name sabdfl comes up for 12.10
[22:16] <sheytan> apachelogger: http://img37.imageshack.us/img37/2121/back2ot.jpg
[22:18]  * kyofel hugs yofel
[22:40] <cure_> does anyone here know if this is true http://i54.tinypic.com/b54m0y.png ?
[23:10] <Daskreech> cure_: What's that from?
[23:11] <cure_> thats from overclockers
[23:11] <cure_> last night
[23:11] <cure_> forums
[23:12] <cure_> overclock.net im sorry
[23:13] <Daskreech> Well they have a 8 core AMD playing with I'll sign up :)
[23:14] <cure_> :)
[23:14] <cure_> im not sure if this is right but i realy hope so
[23:15] <cure_> there are no benchmarks yet


[18:59] <ibeardslee> morning
[18:59] <ibeardslee> hah beat chilts
[19:05] <snail> morning
[20:09] <ojwb> morning
[20:09] <ajmitch_> morning
[20:28] <thumper> morning
[21:14] <Atamira> morning
[23:57] <ojwb> when they say "3 years on desktop" and "5 years on server" for LTS releases, what does that actually mean?
[23:57] <ojwb> is it that desktop-related packages in main only get 3 years?