[02:28] <LoverBoyV> When i try to run U1 i get this error http://ubuntu.pastebin.com/raw.php?i=nbZDUp6L
[02:30] <LoverBoyV> anybody even paying attention in here?
[02:31] <JontheEchidna> !patience
[02:31] <JontheEchidna> LoverBoyV: But, on that note, are python-ubuntuone* packages installed
[02:32] <LoverBoyV> lemme check
[02:32] <JontheEchidna> python-ubuntuone, python-ubuntuone-client and python-ubuntuone-storageprotocol
[02:32] <LoverBoyV> Yes, all three are installed
[02:33] <JontheEchidna> hrm... interesting
[02:33] <LoverBoyV> yup
[02:33] <JontheEchidna> I'm not an expert. (That was the obvious thing to check for) I'd suggest throwing yourself to the mercies of the bugtracker.
[02:33] <LoverBoyV> ok
[02:34] <JontheEchidna> But I think that the ubuntuone devs are pretty responsive to bugs, so there is hope
[02:35] <LoverBoyV> YAY!
[02:35] <LoverBoyV> that makes me happy
[02:35] <LoverBoyV> cause i just reinstalled and i had backed up everything to ubuntu one
[02:36] <JontheEchidna> It looks like 71% of the bugs filed against ubuntuone-client have at least been touched
[02:36] <LoverBoyV> thats good
[04:08] <Sarvatt> oh sweet, fglrx 10.6 that i put in x-updates works with xserver 1.8 now, http://pastebin.com/2Ti6wMNe
[05:55] <DanaG> bug 202490
[05:55] <DanaG> Interesting.
[05:55] <DanaG> New driver for the Ricoh MMC controller.
[05:55] <DanaG> Though, oddly enough, if I want to read a partitioned SD card in Windows, I have to do exactly what Linux does: disable the MMC controller and use the SDHCI controller.
[07:23] <smerz> lol tehbaut
[07:23] <smerz> excess flooding all night long
[07:23] <smerz> must be some stuipid irc client or bouncer with an insane perform list x)
[07:29] <DanaG> somebody ban it?
[08:04] <coz_> hey guys.. is any progress being made to allow the official nvidia drivers to be installed on  maverick?
[08:22] <DanaG> heh, the one to ask would be nvidia.
[08:28] <Sarvatt> i would have had 256.35 in x-updates 8 hours ago if they bothered to release the x64 version :)
[14:36] <DrHalan> is there no medibuntu support yet?
[15:27] <kkojiband> do you have any idea whether maveric has gcc 4.5 package?
[15:31] <Sensiva> kkojiband you may search packages in here http://packages.ubuntu.com/
[15:35] <kkojiband> i can't see any package to use 'gcc' keyword in maveric distribution, is there some problem?
[16:24] <yofel> !info gcc-4.5 | kkojiband
[16:25] <yofel> 'gcc' is 4.4 though
[16:52] <zniavre> topic
[16:52] <zniavre> ooops sorry
[17:37] <dabossbv> ich bin jetzt erstmal weg
[17:37] <dabossbv> bis später
[17:48] <HTT-Bird> hey: did the libsensors4 version change between lucid and maverick?
[17:48] <sylon> i get the following errors when i tried to boot with my custom compiled kernel: http://pastebin.com/pf3YqTiN
[17:48] <Daekdroom> !info libsensors4
[17:49] <HTT-Bird> thx, didn't see ubottu about here ;P
[17:49] <Daekdroom> HTT-Bird, apparently it got recompiled
[17:49] <Daekdroom> Lucid is using 3.1.2-2
[17:49] <HTT-Bird> kk
[17:49] <HTT-Bird> because I'm having a weird issue where libsensors isn't recognizing a functioning driver
[17:50] <HTT-Bird> (or apparently functioning at least :P)
[17:54] <sylon> can anyone help me? this whole plymouth business looks difficult
[17:59] <marijus> *offtopic* how would i make a script autoexecute on external monitor plug in/out?
[18:00] <Daekdroom> that's not so offtopic
[18:00] <marijus> well... its not related to maverick dev... thats why i thought :)
[18:00] <DanaG> stupid freaking oxford USB-SATA controller.  I leave the thing up running torrents, and some time later, it randomly disconnects from the USB bus.
[18:59] <Vigo> System Testing locked up yesterday, would that data be in /var/logs or is it easier/better to post it with the Bug tool or is it better to post the .log from log viewer?
[19:00] <arand> Use the bug tool, and attach the log as well ;)
[19:00] <Vigo> Thank you.
[19:01] <Vigo> Now I have to install that Bug squisher tool, yipee
[19:02] <arand> Eh, just use ubuntu-bug packagename  ?
[19:03] <arand> Which was the "bug-tool" I was talking about.
[19:04] <Vigo> That is too easy, sorta, I may as well test the report tool while I am at it.
[19:28] <Vigo> okee dokee, reported
[20:26] <coz_> guys I hope with maverick you are going to have the possiblity to install official nvidia drivers.. I know on lucid the drive  _current sucks big time and installing official drivers apparenlty require blacklisting nuveau  or however its spelled
[20:30] <yofel> he's gone...
[20:30] <arand> Hmm, was just about to "wfm" :/
[20:30] <yofel> well, it's wfm too
[20:31] <yofel> and even with nvidia-current you need to blacklist nouveau, it's just that the package does that for you
[20:34] <Daekdroom> wfm?
[20:34] <yofel> works for me
[21:52] <DanaG> hmm, dependencies of unity are screwy.
[21:52] <sylon> maverick has blurry fonts in chromium, is it not using freetype bytecode interpreter?
[21:55] <DanaG1> wow, system just hard-locked when I unplugged and replugged my USB sound card.
[21:55] <DanaG1> Or rather, plugged in and then unplugged.
[21:56] <DanaG1> It was spewing zillions of this line:
[21:56] <DanaG1> ALSA sound/usb/usbaudio.c:357: frame 0 active: -84
[21:57] <DanaG1> ubuntu-netbook-unity-default-settings depends upon ubuntu-netbook-default-settings
[21:57] <DanaG1> ubuntu-netbook-default-settings conflicts with ubuntu-netbook-unity-default-settings
[22:12] <poutine> DanaG1, http:///www.livejournal.com
[23:14] <Ian_corne> whoa weird
[23:14] <Ian_corne> fresh boot
[23:14] <Ian_corne> 700Mb/1gb used
[23:14] <Ian_corne> something is leaking that's run at boot time..


[06:18] <mup> PR snapcraft#1594 opened: code style: remove the extra quotes in the dedent example <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1594>
[06:58] <mup> PR snapcraft#1595 opened: tests: fix the skip of snapd integration tests in armhf <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1595>
[07:07] <mup> PR core#60 closed: Fix handling of secondary addresses <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/core/pull/60>
[07:10] <mup> PR snapcraft#1596 opened: tests: move ruby demo test to snapd integration suite <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1596>
[17:47] <mup> PR snapcraft#1594 closed: code style: remove the extra quotes in the dedent example <Created by elopio> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1594>
[19:52] <ekkis> I'm setting up to publish a snap but need to select a "developer namespace".  can anyone explain to me what this is?
[19:52] <ekkis> I can, apparently, only set it once and I don't want to get it wrong
[19:54] <ekkis> the docs state: "This namespace will represent you as a publisher in the Snap Store and you won’t be able to change it afterwards"
[19:54] <ekkis> represent me? how?
[19:54] <ekkis> I have an account name.  so can I have my account name the same as the namespace?
[20:25] <kyrofa> ekkis, yes
[20:25] <kyrofa> ekkis, your namespace will show up in `snap list` as the publisher of the snap
[20:27] <zyga-solus> ekkis: right
[20:27] <zyga-solus> ekkis: so essentially this is your publisher nickname
[20:27] <zyga-solus> ekkis: if you say "my namespace is ekkis"
[20:27] <ekkis> oh... I see.  it's because my "account" doesn't have an account name, like in most other systems
[20:27] <zyga-solus> ekkis: then if someone "snap install thatfancyapp"
[20:27] <zyga-solus> ekkis: then they will get it from "ekkis"
[20:27] <zyga-solus> ekkis: I agree the word namespace is not clear here
[20:28] <ekkis> so they don't have to run `snap install ekkis/thatfancyapp`?
[20:31] <zyga-solus> ekkis: that's right
[20:31] <zyga-solus> ekkis: users install snaps
[20:31] <zyga-solus> ekkis: snaps have names
[20:31] <zyga-solus> ekkis: and users search by name, not by developer IDs or similar things
[20:31] <ekkis> thanks mate
[20:31] <zyga-solus> my pleasure :)
[20:31] <sergiusens> kyrofa is the time off getting too boring? :-P
[20:31] <ekkis> I'm building my first
[20:32] <kyrofa> sergiusens, haha, no, I just tend to idle here even when I'm not working and noticed a question :)
[20:32] <zyga-solus> nothing like the feeling of building one's first snap :)
[20:33] <ekkis> I can specify the `source` field as a url to a tarball.  can I also point it to a github repo?
[20:33] <zyga-solus> ekkis: snaps give developers the power to publish to users
[20:33] <zyga-solus> ekkis: yes
[20:33] <ekkis> do I use the .git url?
[20:33] <zyga-solus> ekkis: there are lots of possible schemes, sergiusens and kyrofa can tell you all about that
[20:34] <ekkis> for example, for Einsteinium (which I'm trying to package), the Clone or Download button indicates: https://github.com/emc2foundation/einsteinium.git
[20:34] <ekkis> can I use this url?
[20:34] <kyrofa> ekkis, indeed you can
[20:34] <sergiusens> zyga-solus does content interface work with classic snaps?
[20:35] <ekkis> kyrofa++
[20:39] <ekkis> suppose that my project has a bunch of dependencies.  the build doc indicates I should install them using apt-get.  how do I express these in the `parts:` section?
[20:39] <ekkis> I presume these parts are snaps?
[20:39] <ekkis> so I have to find the equivalent snaps? or?
[20:40] <ekkis> which also begs the question, do I have to declare all the building tools?
[20:40] <ekkis> most of the dependencies are developer-level
[20:42] <ekkis> in other words there are dependence packages that don't need to be included in the snap
[20:44] <kyrofa> ekkis, there are three keywords that will be of interest: build-packages, stage-packages, and build-snaps
[20:44] <ekkis> oh... let me read up on those then
[20:44] <kyrofa> build-packages are debs that are installed on the host (builder). Build tools might fit into this section
[20:44] <kyrofa> stage-packages are debs that are fetched from the archive and unpacked into the snap
[20:45] <kyrofa> build-snaps are snaps that are installed on the host (e.g. perhaps your build tools are snapped)
[20:45] <ekkis> it's not part of the `parts` section I see
[20:46] <kyrofa> ekkis, I'm not sure which docs you're reading
[20:46] <kyrofa> Link?
[20:46] <ekkis> I see in the different part of the docs it talks about these 3 keywords
[20:47] <ekkis> so for example, the command `sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils` in the instructions requires I have all those tools for building
[20:47] <ekkis> that means I have to find snaps of them correct?
[20:47] <kyrofa> ekkis, no, those would be build-packages
[20:48] <ekkis> so do I just declare `build-packages: build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils` ?
[20:49] <kyrofa> Something like that. It needs to be a YAML list, but you have the right idea
[20:49] <ekkis> ah.  ok
[20:49] <ekkis> and Snapcraft knows to do an apt-get for each
[20:49] <ekkis> and if snap is running on Fedora it will do a `yum install`? (or whatever it is now)
[20:50] <kyrofa> ekkis, not yet, support for other distros in snapcraft is coming
[20:51] <ekkis> ah, but at least theoreticallly
[20:51] <ekkis> at present I'm only concerned with Ubuntu
[20:51] <ekkis> I used to package stuff in RPM form for Redhat and later Fedora
[20:51] <ekkis> so having a cross-distro packager is great!
[20:55] <kyrofa> ekkis, note that, while Snapcraft currently only runs on Ubuntu, the snaps it produces should run everywhere
[20:58] <ekkis> oh.  anywhere so long as `snap` is available on the platform
[21:01] <kyrofa> ekkis, you got it
[21:01] <kyrofa> ekkis, fedora has snapd, for example
[21:04] <sergiusens> ekkis support for rpm distros is coming through dnf support, you can probably get more detailed information from Son_Goku on that aspect
[21:05]  * Son_Goku waves
[21:06] <sergiusens> kyrofa since you are here, mind quickly glancing at snapcraft#1597 ?
[21:06] <mup> PR snapcraft#1597: pluginhandler: warn about migrated system libraries <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1597>
[21:08] <Son_Goku> ekkis: if you want to build RPM-based snaps, you can do it by hand right now
[21:08] <Son_Goku> though it's a pain to do
[21:08] <Son_Goku> kyrofa and kalikiana have been helping me with getting different aspects of Snapcraft running on Fedora
[21:08] <mup> PR snapcraft#1597 opened: pluginhandler: warn about migrated system libraries <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1597>
[21:14] <ekkis> Son_Goku: I may want to.   I think I only have one part so I could just call it `main`?
[21:27] <ekkis> kyrofa: "A set of Ubuntu packages to be downloaded and unpacked to join the part before it’s built" -- what does "join" mean?
[21:30] <ekkis> guys, I've looked through the docs but it's not at all clear to me where I actually run the commands to build my app
[21:31] <ekkis> I need to run autogen, configure, make and make install
[21:32] <ekkis> oh.... I can use `plugin: autotools`
[21:32] <mup> PR snapcraft#1574 closed: Add Dotnet plugin and a sample snap for integration test <enhancement> <Created by rakeshsinghranchi> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1574>
[21:32] <ekkis> so I just need to figure out how to configure the plugin
[21:43] <zyga-solus> ekkis: part names don't matter
[21:43] <ekkis> ok, cool
[21:43] <zyga-solus> ekkis: snapcraft has nice built in help I think
[21:43] <zyga-solus> including help for particular plugins
[21:44] <ekkis> # snapcraft --help autotools?
[21:44] <sergiusens> snapcraft help autotools
[21:44] <zyga-solus> not quite I think, try snapcraft help and look from there
[21:44] <zyga-solus> I think snapcraft help plugins or something like that talks about it but I don't remember
[21:45] <zyga-solus> thank you sergiusens
[21:46] <ekkis> the help is for commands to snapcraft
[21:47] <ekkis> but I'm looking at the web for help.  the docs are not very clear
[21:49] <sergiusens> ekkis https://docs.snapcraft.io/build-snaps/your-first-snap
[21:50] <ekkis> yes, I'm reading through that doc
[21:51] <sergiusens> my network is wonky, so I cannot verify what I am sending over your way ekkis but this might be useful https://tutorials.ubuntu.com/tutorial/create-your-first-snap
[23:58] <buzz_> Hello
[23:59] <Guest93864> Hello
[23:59] <Guest93864> Anyone hoe
[23:59] <Guest93864> Anyone home


[05:34] <c2tarun> hi
[05:51] <CIA-40> [messages] yurchor * 1219208 * trunk/l10n-kde4/uk/messages/ (12 files in 9 dirs) SVN_SILENT Ukrainian translation update
[08:48] <bambee> hey
[09:04] <CIA-40> [summit] pelcak * 1219212 * trunk/l10n-support/cs/ (61 files in 22 dirs) Update of Summit
[09:09] <CIA-40> [summit] ilic * 1219214 * (44 files in 23 dirs) Summit gather.
[09:29] <bambee> hi, I'm student in computer sciences and I would like get involved in kubuntu development and help you in the process (especially programming)
[09:29] <bambee> what I need to do ?  (sorry my english is not perfect)
[09:30] <bambee> It could be a good experience for a student, imho :)
[09:53] <bambee> no one there ?
[09:54] <tsimpson> bambee: just hang around for a while
[09:55] <tsimpson> bambee: there's some info here too: https://wiki.kubuntu.org/Kubuntu/GettingInvolved
[09:57] <bambee> I already read this page ;)
[10:11] <jussi> bambee: feel free to grab something on this page: https://wiki.kubuntu.org/Kubuntu/Todo
[10:12] <bambee> jussi: ok
[10:13] <jussi> bambee: documentation is a great way to start - its easy to pick up and you learn about things also.
[10:27] <NCommander> Riddell: ping, you about?
[10:35] <NCommander> anyone awake who can answer a Qt packaging question?
[11:03] <Riddell> NCommander: what's up?
[11:03] <Riddell> bambee: you wake up too early for us :)
[11:04] <NCommander> Riddell: what's your feelings w.r.t to changing Qt to build with GCC 4.4? (see https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/705689 for context)
[11:06] <Riddell> NCommander: I've no immediate objection if that fixes it
[11:07] <Riddell> but I guess I'd also want to talk to upstream and try their latest version to see if it's still a problem
[11:22] <NCommander> Riddell: well, considering we're looking at a toolchain regression that is triggered with 4.7.0/4.7.1, I'm doubtful 4.7.2 will fix it except by fluke
[11:23] <NCommander> Riddell: do we have a branch for qt4-x11, or is it just fire and forget? (I'm going to get the necessary signoffs from the toolchain team and would like to upload ASAP once we get those, then get to work towards fixing KDE)
[11:23] <bambee> Riddell: oh sorry I'm in france , I forgot jetlag :)
[11:25] <Riddell> NCommander: ah, blame the tools then :)
[11:25] <Riddell> NCommander: bzr+ssh://bazaar.launchpad.net/~kubuntu-members/qt/ubuntu/
[11:25] <Riddell> bambee: we'd love for you to help of course
[11:25] <bambee> cool :)
[11:25] <Riddell> do you know how to programme Qt, C++, Python?
[11:26] <bambee> yup, I prefer C++ but python is not a problem
[11:27] <NCommander> Riddell: thanks, I 'll upload 0ubuntu9 today if I get the necessary signoffs
[11:30] <bambee> Riddell: don't worry I'm better in programming than in english :P
[11:39] <Riddell> bambee: do you have natty installed?
[11:40] <bambee> not yet, actually I use maverick (with kubuntu-ppa/backports)
[11:41] <Riddell> bambee: does userconfig run?  kcmshell4 userconfig
[11:57] <Riddell> ScottK: kubuntu/daily-live: natty-desktop-powerpc.iso oversized by 2342912 bytes (736346112)  more changes needed
[11:57] <Tm_T> what have changed since alpha2?
[11:58] <Tm_T> hmm, I suppose there's no easy answer, so should dig it up myself or so
[12:01] <Riddell> Tm_T: see natty-changes :)
[12:02] <Tm_T> thanks
[12:09] <bambee> Riddell: yes it does
[12:09] <bambee> on natty it does not ?
[12:10] <Riddell> bambee: no it fails to load the .ui file
[12:12] <Riddell> /usr/share/kde4/apps/userconfig/ui/userproperties-details.ui
[12:14] <CIA-40> [messages] zepires * 1219234 * trunk/l10n-kde4/pt/messages/ (12 files in 9 dirs) Finished HEAD for now
[12:15] <Riddell> CIA-40: huh?
[12:15] <Riddell> why do we care about that
[12:15] <bambee> Riddell: I'll upgrade to natty and test it
[12:27] <debfx> Tm_T: the powerpc kernel images have become larger
[12:43] <debfx> Riddell: I'm applying for kubuntu-dev :)
[12:44] <debfx> Riddell: https://wiki.kubuntu.org/FelixGeyer/KubuntuDevApplication
[12:52] <Riddell> debfx: the black belt of the ninjas!
[12:54] <debfx> :D
[13:04] <shadeslayer> everyone is applying for dev
[13:04] <shadeslayer> maybe i should too
[13:05] <Riddell> the more the merrier (as long as you're know your stuff and can take the grilling)
[13:05] <Tm_T> debfx: interesting, thanks
[13:06] <shadeslayer> yeah
[13:06] <shadeslayer> oh also
[13:06] <shadeslayer> Riddell: what's the new thing that uses authentication in kdm called?
[13:09] <Riddell> shadeslayer: I don't know of any new thing in KDM
[13:09] <shadeslayer> Riddell: the part where you auth kdm to change theme's etc
[13:10] <Riddell> well it's policykit
[13:10] <shadeslayer> ah .. ok
[13:11] <shadeslayer> because the user management KCM does not have it
[13:12] <Riddell> shadeslayer: no it needs to be ported to policykit
[13:12] <Riddell> as does system-config-printer-kde and language-selector
[13:12] <shadeslayer> yeah .... alright ... i might work on it, just after i finish removing some redundant code from rekonq
[13:13] <shadeslayer> it's in kdelibs right?
[13:13] <Riddell> I've never used policykit but I think it involves writing small scripts to do the privilaged changes and calling them from polkit-kde
[13:13] <Riddell> I think the kdelibs API is KAuth
[13:14] <shadeslayer> alright
[13:14] <Riddell> shadeslayer: of course the user management KCM has more immediate issues such as not running at all currently
[13:14] <shadeslayer> err... it doesn't?
[13:14] <shadeslayer> it works for me
[13:14] <Riddell> shadeslayer: on natty?
[13:14] <shadeslayer> erm ... maverick :)
[13:15] <Riddell> there you go :)
[13:15] <shadeslayer> X is all sorts of broken on natty .. so will upgrade when in beta
[13:15] <Riddell> new sip and pyqt causing problems I think
[13:15] <shadeslayer> stupid SIP
[13:16] <shadeslayer> and stupid pyth0rn
[13:16] <Riddell> plan for userconfig should be, fix bugs, port to policykit, get it upstream
[13:16] <Riddell> but that will take someone with some dedication, it hasn't happened yet
[13:16] <shadeslayer> alrighty .... i can have a looksie today :)
[13:16] <shadeslayer> figure out a POA
[13:17] <Riddell> bambee said he would check the ui loading problem (the natty issue) so coordinate with him/her
[13:17] <shadeslayer> #kde-devel? or some sekret channel? :P
[13:17] <Riddell> bambee: you also have message indicator support for kmess?  anything we need to care about or will that just go upstream?
[13:17] <shadeslayer> ah ^^
[13:17] <Riddell> shadeslayer: here, an hour ago
[13:18] <shadeslayer> ok
[13:19] <bambee> Riddell: I prefer a review first and then send it to upstream
[13:21] <Riddell> bambee: if agateau has a moment he's be the best person to review, he's done most of the message indicator work for us
[13:21] <bambee> mhhhh... I don't know... I wrote a patch to integrate support directly in kmess code source... (no plugin manager yet) so probably upstream would be better...
[13:22] <bambee> Riddell: ok :)
[13:30] <bambee> reboot
[13:36] <shadeslayer> hmm
[13:36] <shadeslayer> rebooting : something i haven't done in 2 days
[13:43] <bambee> Riddell: as you said on natty userconfig crashes
[13:43] <bambee> (with a nice backtrace)
[13:46] <Riddell> bambee: yeah :(
[13:46] <Riddell> bambee: since the same code works in maverick I presume it's due to updated sip and pyqt
[13:47] <bambee> probably
[13:47] <Riddell> bambee: so I guess debugging would be to check if any ,ui loads in pyqt now and then start to narrow it down to the part that is a problem with this .ui file
[13:47] <Riddell> assuming that interests you at all
[13:47] <Riddell> bambee: how was upgrading to natty?
[13:50] <bambee> fine except I lost kwin effects :(
[13:50] <bambee> (due to nouveau probably)
[13:51] <bambee> Riddell: I'll try to find a solution for userconfig :)
[14:24] <bambee> Riddell: this is a bug in PyQt4 ui/uiparser.py line 231 =>  bg_i18n is an instance of type QString, so bg_i18n.string is wrong :)
[14:24] <bambee> and apparently it's fixed on upstream in nightly build
[14:25] <bambee> but just for test  replace line 231 by "bg_name = bg_i18n" , and then try kcmshell4 userconfig
[14:25] <bambee> ;)
[14:36] <Riddell> bambee: you tested upstream nightly pyqt?  or you read somewhere the bug is fixed?
[14:38] <Riddell> bambee: 'replace line 231 by "bg_name = bg_i18n"' is that the upstream fix?
[14:39] <bambee> I just read somewhere (on upstream) that a very similar bug was fixed in nightly pyqt
[14:39] <bambee> http://www.riverbankcomputing.co.uk/static/Downloads/PyQt4/ChangeLog-snapshot-4.8.4-278054fd857c
[14:40] <bambee> " is that the upstream fix?" => no it's mine
[14:41] <Riddell> bambee: so we need to track down that 278054fd857c ideally
[14:41] <Riddell> I wonder if pyqt has public git these days
[14:43] <Riddell> http://paste.kde.org/4285/
[14:43] <Riddell> bambee: looks promising ^^
[14:43] <Riddell> yay, fixes it
[14:44] <Riddell> bambee: so we need to add that patch to our python-qt package, do you know how, are you interested in learning how? (else I can just do it)
[14:45] <bambee> yes I'm :)
[14:45] <ari-tczew> Riddell: could you sponsor something for me?
[14:46] <Riddell> ari-tczew: sure
[14:46] <ari-tczew> Riddell: bug 713790
[14:47] <Riddell> bambee: install devscripts, apt-get source python-qt4, put the patch with -p1 level in debian/patches, add to debian/patches/sources, dch -i to add a changelog, debuild -S to build a source package, debdiff <old>.dsc <new>.dsc to make a debdiff to give to someone who can upload (me)
[14:48] <bambee> ok ;)
[14:48] <tazz> Riddell, do you have any small kubuntu sitckers ?
[14:49] <Riddell> ari-tczew: patch on comment #1 is for the wrong package I think
[14:49] <Riddell> tazz: you should have come to FOSDEM, I had some there, all gone now
[14:49] <Riddell> maybe I should get more for conf.kde.in, they're not cheap though
[14:50] <tazz> Riddell, a small problem of funding XD
[14:50] <ari-tczew> Riddell: yea, it's occur often while merging a few packages
[14:50] <tazz> np, Riddell we'll print some in BLR itself.
[14:52] <Riddell> tazz: I don't think I have the design I used but it was the KDE 4.6 wallpaper with kubuntu logo on top and "Friendly Computing" underneith
[14:52] <ari-tczew> Riddell: updated
[14:52] <tazz> Riddell, ok...
[14:53] <Riddell> ari-tczew: since libboost-dev depends on libboost1.42-dev I wonder if we need to keep that change
[14:54] <Riddell> ari-tczew: and since we have kdelibs5-dev >= 4:4.5.2 everywhere that's not vital either
[14:54] <Riddell> ScottK: what's the crack with boost build-depends?
[14:55] <Riddell> ari-tczew: I'd say we can sync this unless ScottK think we really need explicit versioning on boost build-deps
[14:56] <ari-tczew> Riddell: +1 for sync if these changes are deprecated
[14:58] <Riddell> ari-tczew: change the bug into a sync bug and if ScottK doesn't object by tomorrow I'll do it with my archive day
[14:59] <shadeslayer> flipping rekonq won't save LP comments
[14:59] <shadeslayer> sigh
[15:00] <Riddell> shadeslayer: won't save them?  that's worse than normal when it has saved but hasn't done the ajax update thing
[15:00] <ari-tczew> Riddell: done
[15:00] <shadeslayer> ah
[15:00] <Riddell> shadeslayer: it's still losing my login to websites when I log out of KDE
[15:01] <shadeslayer> Riddell: doesn't save them as in ... doesn't show that it has saved them
[15:01] <shadeslayer> i've even disabled all the fooey code that was causing a issue
[15:01] <shadeslayer> err
[15:01] <shadeslayer> Riddell: that might be because of the cache etc ... maybe kde cleans out the cache and thus you can't login ?
[15:04] <Riddell> shadeslayer: my cookie cache?  why would it do that?
[15:05] <Riddell> although .kde/share/apps/kcookiejar/cookies is empty
[15:05] <Riddell> which is weird
[15:05] <Riddell> shadeslayer: I'd say rekonq isn't using kcookiejar properly
[15:06] <Riddell> hmm, better than konqueror which just crashes when loading any web page :(
[15:07] <bambee> Riddell: http://pastebin.com/J3dwS1K1
[15:07] <bambee> :)
[15:09] <Riddell> bambee: lovely, thanks very much
[15:09] <bambee> you're welcome :)
[15:09] <Riddell> I think the only thing I'd change is naming the patch kubuntu_01_...  to make it clear the patch is from us and not from debian (makes merging easier), I can do that easily enough
[15:10] <Riddell> oh also it should close the launchpad bug
[15:10] <bambee> ohhh so I should add "(LP:  #XXXX)" in the changelog...
[15:11] <Riddell> except I don't think there is a bug
[15:11] <Riddell> can't see one on https://bugs.launchpad.net/ubuntu/+source/userconfig
[15:11] <Riddell> so we'll just leave that out
[15:13] <bambee> ok
[15:14] <Riddell> bambee: uploaded!  thanks for helping Kubuntu
[15:16] <bambee> :)
[15:23] <Riddell> bambee: so for coding userconfig can do with more love.  there's also language-selector which needs various things done.  our installer usually needs fixes.  In c++ rbelem is working on file sharing with samba, he might well need some help there
[15:25] <Riddell> and of course we do packaging and bugfixing (kconf upgrade script for the wallpaper change would be good)
[15:25] <Quintasan> \o
[15:28] <Quintasan> It's time to fill out UDS O sponsorship form
[15:28] <Riddell> Quintasan: has it been announced yet?
[15:28] <Riddell> bambee: plus there's the todo list and bug fix list needing done https://wiki.kubuntu.org/Kubuntu/Todo http://goo.gl/yGhJd
[15:28] <bambee> Riddell: what do you mean by language-selector ? I mean language-selector from systemsettings ?
[15:29] <Riddell> bambee: yes, System Settings -> Locale -> Languages -> Install more Languages
[15:29] <bambee> ok
[15:29] <maco> Riddell: where do changes get made to the slideshow in the installer? i spotted a typo when installing my system at work
[15:29] <Riddell> bambee: or just run  kdesudo "qt-language-selector --mode install"
[15:30] <Riddell> maco: ubiquity-slideshow-kubuntu
[15:30] <Riddell> bambee: I think we'd like that changed to a kcontrol module rather than standalone app
[15:30] <Riddell> bambee: it should have feature parity with the gtk frontend
[15:30] <Riddell> bambee: and ideally should be ported to policykit
[15:31] <Riddell> well porting it to policykit might be a requirement for it being a kcontrol module
[15:31] <Quintasan> Riddell: It wasn't but the form is open
[15:32] <Riddell> bambee: or for a project we'd like, implement the sound menu for KDE
[15:32] <Riddell> bambee: so lots to do :)
[15:32] <bambee> indeed :)
[15:32] <Riddell> in return, fame, glory and free trips to Ubuntu Summits!
[15:33] <bambee> w00t :D
[15:34] <Riddell> that kdesudo command reminds me it could do with having its syntax fixed, should be any need for quotes in kdesudo "qt-language-selector --mode install"
[15:43] <Riddell> language-selector should use kpackagekit really rather than its own polictkit stuff
[15:43] <Riddell> doing that would probably get rid of a load of code
[15:46] <debfx> Riddell: you don't need quotes, this works fine: kdesudo -- qt-language-selector --mode install
[15:48] <bambee> mhhh I don't know because language-selector and sound menu in KDE are both very interesting :)
[15:50] <c2tarun> hi
[16:01] <debfx> Riddell: so how does the application process work? we need to set up a meeting?
[16:03] <Quintasan> c2tarun: Hi there
[16:03] <c2tarun> Quintasan: hi :)
[16:05] <c2tarun> Quintasan: I got an error while building a package, it was that build dependencies are missing. There was an application for installing build-depends automatically, can you please tell me that?
[16:05] <Quintasan> c2tarun: sudo apt-get build-dep <name of the package you want build depends of>
[16:06] <c2tarun> Quintasan: do we have to install all the build-deps I mean can't we use pbuilder-dist for this.
[16:07] <maco> Riddell: merge request sent
[16:08] <Quintasan> c2tarun: I don't get what you want to do now
[16:09] <c2tarun> Quintasan: I want to build the package, but I dont want to bloat my system by installing all the build-dep for a application. Can we install all the build-dep in pbuilder-dist env and build application there.
[16:09] <Quintasan> c2tarun: The pbuilder does that automatically
[16:09] <Quintasan> c2tarun: you just add the dependencies to debian/control file
[16:10] <c2tarun> Quintasan: but still the biggest problem is how to copy the folder from my home folder to pbuilder-dist home folder?
[16:10] <debfx> c2tarun: you can build the source package on your system (debuild -S) and then run pbuilder on the resulting .dsc file
[16:11] <c2tarun> debfx: but I am getting error while debuild -S and someone on #ubuntu-motu told me that it was due to missing build-dep
[16:11] <Quintasan> ...
[16:11] <Quintasan> You can ignore it
[16:12] <debfx> some build-deps might be needed when running the clean target (which debuild does by default)
[16:13] <c2tarun> I just installed all the build deps but still getting that error. check this http://paste.ubuntu.com/563925/
[16:14] <c2tarun> any idea about the error ^^
[16:15] <debfx> looks like spyder_2.0.6.orig.tar.gz is not a valid tar.gz file
[16:17] <c2tarun> debfx: hmm..... It was on the website. but on debian site there is a version 2.0.3 do you think that I should pack that one as an upgrade and leave this one?
[16:17] <Quintasan> c2tarun: and that error is certainly not missing build depend but a wrong source file
[16:17] <Quintasan> debfx: if there is a version in Debian then ask the Debian maintainer to update it
[16:18] <Quintasan> debfx: sorry, meant to c2tarun
[16:18] <c2tarun> Quintasan: got it :) can a debian maintainer update in ubuntu archives as well?
[16:18] <Quintasan> c2tarun: unless you are both debian developer and motu or core-dev then no
[16:19] <Quintasan> c2tarun: usually you would ask Debian developer to upgrade the package in Debian and then request a sync in Ubuntu
[16:19] <c2tarun> Quintasan: Can i request the sync, I thought only MOTU's can do that.
[16:19] <Quintasan> You can REQUEST a sync
[16:19] <Quintasan> but only archive admins can do them
[16:20] <c2tarun> Quintasan: request as posting a bug on LP?
[16:20] <Quintasan> yup
[16:20] <c2tarun> Quintasan: god I hate doing this :( when will I be ready for MOTU :((
[16:21] <Quintasan> you need at least two months of fairly constant contributions to get a membership
[16:21] <c2tarun> Quintasan: hmm.... thats cool I thought may be years ;)
[16:22] <Quintasan> c2tarun: I mean Kubuntu Membership
[16:22] <Quintasan> c2tarun: You can apply straight for MOTU
[16:22] <c2tarun> Quintasan: what is the point in applying when they'll reject me STRAIGHT :(
[16:23] <Quintasan> c2tarun: well, you need someone to endore your application
[16:24] <Quintasan> c2tarun: like, you work around here helping us and learn packaging that way, then after sometime, if you think you are ready, you create a MOTU application, attend a meeting on IRC where they ask you questions
[16:24] <c2tarun> Quintasan: there will be an interview session?
[16:25] <Quintasan> c2tarun: there is no special time for that, you just add your application to next DMB agenda and join the irc channel when the meeting stats
[16:25] <c2tarun> Quintasan: question like what?
[16:26] <Quintasan> it will be faster to supply logs than reply
[16:28] <c2tarun> Quintasan: where can i get the logs? can u please tell.
[16:29] <Quintasan> looking for them
[16:29] <c2tarun> Quintasan: thanks me too :)
[16:32] <Quintasan> hmm on 17th December I got accepted
[16:32] <c2tarun> 2009?
[16:33] <c2tarun> Quintasan: ^^
[16:33] <Quintasan> yup
[16:35] <Quintasan> c2tarun: http://irclogs.ubuntu.com/2009/12/11/%23ubuntu-meeting.html
[16:35] <Quintasan> That would be this one
[16:35] <ari-tczew> c2tarun: if you want request a sync from Debian, you can use script "requestsync" from package ubuntu-dev-tools
[16:35] <Riddell> debfx: well kdesudo shouldn't need the -- either, sudo doesn't
[16:35] <Riddell> debfx: yes a meeting of kubuntu-dev, feel free to use doodle.com to set one up
[16:36] <ari-tczew> c2tarun: MOTU can ACK syncs.
[16:36] <Riddell> maco: URL to merge request?
[16:36] <ari-tczew> Quintasan: We have a script syncpackage which developer can use for upload sync directly to archive via dput.
[16:37] <Quintasan> ari-tczew: awesome
[16:38] <Riddell> bambee: I guess agateau isn't around today, best e-mail him the patch to kmess
[16:39] <Quintasan> c2tarun: The meeting looks like this, you sure will want some of us to show up for your meeting so we can support your contributions
[16:39] <Quintasan> man, that sure brings memories :O
[16:39] <agateau> Riddell: I am there :)
[16:40] <agateau> Actually I suggested bambee to submit the patch on LP
[16:40] <Riddell> ah, lovely
[16:40] <agateau> bambee: and subscribe me to the bug
[16:40] <agateau> bambee: or do as Riddell suggested, mail the patch, bug at some point it will need to go in LP
[16:41] <agateau> Riddell: btw, did you get to package this new libindicate-qt?
[16:41] <c2tarun> Quintasan: sure :) thanks as soon as i'll think that I can be a motu i'll request you all.
[16:41] <Riddell> agateau: it's next on my todo list
[16:42] <agateau> Riddell: great
[16:42] <ari-tczew> c2tarun: I encourage you to work on merges and fix some FTBFS with binutils-gold.
[16:42] <c2tarun> ari-tczew: FTBFS?
[16:42] <Quintasan> fails to build from source
[16:43] <c2tarun> for that do I have to make changes in the original source code?
[16:43] <Quintasan> with patches
[16:43] <ari-tczew> it depends
[16:43] <ari-tczew> use command "what-patch" to make sure whether and which patch system package uses
[16:44] <c2tarun> ari-tczew: ok, then
[16:44] <ari-tczew> Quintasan: oh, you were handled by MOTU Council yet, not DMB
[16:44] <Quintasan> the meeting will look most likely the same :P
[16:45] <ari-tczew> Quintasan: but DMB is exapnded than MC
[16:45] <Quintasan> I know
[16:46] <Quintasan> But I do not think they will grill him more than necessary
[16:46]  * Quintasan wonders if Mark ever uses his irc client
[16:47] <ari-tczew> Quintasan: which Mark?
[16:47] <sabdfl> i do
[16:47] <Quintasan> Awesome :)
[16:47] <sabdfl> back to natty, then
[16:47] <sabdfl> :-p
[16:47] <Quintasan> :D
[16:47]  * Quintasan should start working too
[16:48] <Quintasan> shadeslayer: Did I upload your kdegames stuff or not?
[16:48] <ari-tczew> sabdfl: I see you on IRC first time, as well. Nice.
[16:48] <sabdfl> i'm around just about every day
[16:49] <ari-tczew> sabdfl: your nickname is pretty exotic
[16:49] <Quintasan> I think sabdfl get things done instead of talking about them :D
[16:49] <sabdfl> it's more declarative than exotic
[16:49] <sabdfl> gtg, see you later
[16:57] <ulysses> Do we have a time machine? The alpha 2 announcement says the Narwhal will be released in 2010 April:\
[16:57] <Riddell> ulysses: that'll be my fault, please fix
[16:57] <Riddell> (assuming you're looking at the Kubuntu wiki page)
[16:58] <ulysses> Anyway it would be good to have a time machne
[16:58]  * ulysses fixing
[16:58] <Quintasan> Yeah, time machine
[16:58] <Quintasan> like uploading KDE 4.6 as 4.0
[16:59] <Quintasan> and making kde devs go like "WTF? DID WE HIT BALLMER'S PEAK?!"
[17:05] <Riddell> Riddell_: hi
[17:05] <Riddell> jr_: hi
[17:06] <Riddell> agateau: hmm, message indicator doesn't seem to know that quassel or konversation are being run
[17:06] <Quintasan> WAAAAAAH THREE Riddells
[17:06] <Riddell> I get around
[17:07] <Quintasan> Riddell: You sure know how to multi-task
[17:07] <Quintasan> :D
[17:07] <ulysses> Quintasan: it's better than having three apachelogger
[17:07] <Quintasan> Oh god
[17:07] <ulysses> imagine that
[17:07] <Quintasan> I even don't want to imagine this
[17:07] <Quintasan> ulysses++
[17:07] <Quintasan> shadeslayer: ^
[17:08] <Quintasan> yofel: ^^
[17:08] <agateau> Riddell: mmm weird
[17:09] <yofel> Quintasan: as long as they're not around 24/7 it might be tolerable
[17:09] <Quintasan> yofel: at least one of them will be around
[17:09] <yofel> :S
[17:09] <ulysses> and all of them will be drunk 0/24
[17:09] <Quintasan> it's like, MADNESS ROUND TH ECLOCK
[17:09] <Quintasan> CLOCK*
[17:10] <Riddell> Riddell_: ping
[17:10] <Riddell> agateau: ah hah, I need to restart plasma-desktop
[17:10] <agateau> Riddell: ah, could be
[17:26] <maco> Riddell: https://code.launchpad.net/~maco.m/ubiquity-slideshow-ubuntu/kubuntu-fix-714668/+merge/48802
[17:30] <Riddell> I uploaded libindicate-qt with libindicate-qt0 renamed to libindicate-qt1 so transition will be needed, I'll do that once it's through New
[17:30] <Riddell> agateau: I also added a .symbols file so if you break binary compatibility, we'll know about it!
[17:34] <debfx> Riddell: ok, I've set up a doodle poll: http://doodle.com/sbufw9rpaq7vh9i3
[17:36] <Riddell> maco: lovely, merged
[17:36] <maco> Riddell: thanks dear
[17:38] <Riddell> debfx: updated, do post to kubuntu-devel@
[17:40] <bambee> agateau: ok as you said I'll submit the patch on LP:kmess
[17:41] <Riddell> bambee: out of interest why do you use kmess rather than kopete? (or finishing kde-telepathy :)
[17:42] <shadeslayer> Quintasan: lol
[17:42] <shadeslayer> my interwebz was washed out
[17:43] <shadeslayer> bambee: so ... i'd like to work on KAuth from tomorrow .... for User Management
[17:44] <Quintasan> bambee: yeah, Riddell's right, if you can I think guys over at #kde-telepathy could use your help
[17:45] <Riddell> shadeslayer: that probably needs some Policykit scripts to run the privilaged bits, I expect those can be taken from the gnome equivalent, then rewrite the bits of userconfig to use them
[17:45] <Riddell> Quintasan: sssh, he's got enough programming things to do in Kubuntu :)
[17:46] <bambee> because kmess works better than kopete for msn (I've severals problems with kopete, unable to send or download files, unable to see some contacts and so on)
[17:46] <bambee> kmess works just fine
[17:46] <bambee> BUT
[17:46] <bambee> I use kopete for jabber ;)
[17:46] <Quintasan> Riddell: yeah, but if we get rid of kopete then we will have less stuff to work on
[17:46] <shadeslayer> Riddell: oh btw rekonq will probably have a alpha release in till this weekend, before that hopefullt
[17:46] <shadeslayer> *hopefully
[17:46] <bambee> and graphically I prefer kmess too :)
[17:46] <shadeslayer> and lemme test your cookies issue
[17:47] <bambee> however kopete is a very good IM
[17:47] <Riddell> shadeslayer: an alpha release that is certain to have a final release before Kubuntu has a final release?
[17:47] <Quintasan> bambee: well, telepathy is future, if you feel like it then guys at #kde-telepathy are your friends :)
[17:47] <bambee> you're right
[17:48] <Quintasan> bambee: if you ever pop in there just tell em that Riddell or me sent you so you will get cookies ;)
[17:50] <bambee> ;)
[17:52] <bambee> "so ... i'd like to work on KAuth from tomorrow .... for User Management" => I missed something ?
[17:52] <bambee> arrff disconnected :\
[17:53] <bambee> aah reconnected :P
[17:54] <shadeslayer> Riddell: <quote>I think we are delaying it too much, considering the extreme need we have for a long bugfixing period and the necessity to release for the mid of March.<end quote>
[17:54] <shadeslayer> so .. yep :)
[17:54] <shadeslayer> we get 1 month to test out rekonq on our system's as well
[17:54] <shadeslayer> lemme see our release schedule
[17:55] <shadeslayer> oh my
[17:55] <shadeslayer> just in time for user interface freeze
[17:56] <shadeslayer> ( sorry for the pinginng out, the quasselcore has alot of db queries right now )
[18:11] <shadeslayer> Riddell: i dont find anything related to kcookiejar in rekonq @_@
[18:12] <shadeslayer> well ... there's just a small piece of code that clear's cookies based on your settings
[18:12] <shadeslayer> but that's about it
[18:14] <bambee> reboot
[18:25] <maco> anyone who thinks they submitted a sponsor request for UDS-O:   you did it during testing time and so it doesn't count. do-over some time later when it actually opens
[18:27] <shadeslayer> Quintasan: ^^
[18:27] <Quintasan> FFFFFFFFFFFFFFFF
[18:28] <Quintasan> shadeslayer: say that to JonTheEchidna if he gets here
[18:28] <shadeslayer> Quintasan: im leaving in another 30 mins
[18:55] <CIA-40> [messages] asserhal * 1219275 * trunk/l10n-kde4/sv/messages/ (13 files in 10 dirs) SVN_SILENT updated translations
[19:25] <bambee> guys I'm not there tomorrow nor wednesday, however I'm back thursday ;)
[19:26] <bambee> and I'll give some help to shadeslayer for user management and Kauth :)
[19:26] <shadeslayer> :)
[19:26] <shadeslayer> oh and btw : http://wstaw.org/m/2011/02/07/plasma-desktopYD8524.jpg
[19:26] <shadeslayer> :D
[19:26] <shadeslayer> Quintasan: Riddell ^^
[19:27] <shadeslayer> we ripped off Firefox :P
[19:27] <Quintasan> shadeslayer: you mean you ripped off memleaks?
[19:27] <shadeslayer> hah
[19:27] <Quintasan> :P
[19:27] <shadeslayer> Quintasan: rekonq doesn't leak alot of mem tho
[19:28] <shadeslayer> i ran it for 3 days ... and it's still idling at 200 megs
[19:28] <shadeslayer> it started at 180-185
[19:28] <shadeslayer> i agree ... 200 megs looks like alot ... but still
[19:31] <shadeslayer> bambee: https://projects.kde.org/projects/kde/kdebase/kde-workspace/repository/revisions/master/entry/kdm/kcm/kdm-users.cpp#L69
[19:31] <shadeslayer> we will need a dbus entry .. :S
[19:32] <shadeslayer> looks trivial to create one tho ...
[19:32] <shadeslayer> ok time to sleep
[19:33] <shadeslayer> night all
[19:50] <ulysses> Are the desktop effects broken in Natty for anyone?
[19:51] <Riddell> sheytan: how did you rip off firefox?
[19:52] <sheytan> Riddell did you mean shadeslayer? :D
[19:52] <Riddell> ulysses: working better than ever on my laptop, really slow and crap on my netbook, so just the usual lottery, see mgraesslin's blog on planet today
[19:52] <Riddell> sheytan: yes sorry
[19:52] <Riddell> shadeslayer: how did you rip off firefox?
[19:52] <sheytan> no problem
[19:52] <ulysses> I can't resume the desktop effects
[19:52] <ulysses> when it worked, it was good, but now it doesn't work
[20:00] <Riddell> sheytan: I think I should ask the ubuntu-website mailing list if anyone can turn your design into a wiki theme
[20:00] <sheytan> Riddell you know what sucks?
[20:01] <sheytan> That we always need to ask ubuntu ppl to make any step forward
[20:01] <sheytan> same thing with the hosting
[20:01] <sheytan> we need our own stuff
[20:01] <sheytan> own wiki
[20:01] <sheytan> with own information
[20:09] <mgraesslin> ulysses: which graphics card?
[20:09] <ulysses> mgraesslin: Intel GMA4500
[20:10] <mgraesslin> is graphicssystem raster still enabled by default on natty?
[20:14] <fosdemlogger> should be
[20:14] <fosdemlogger> ulysses: echo $QT_GRAPHICSSYSTEM
[20:14] <mgraesslin> still at fosdem?
[20:15] <fosdemlogger> oh
[20:15] <apachelogger> at home for 3 hrs :D
[20:17] <apachelogger> anyone knows where my favorite kpackagekit/apper hacker is?
[20:18] <apachelogger> debfx: did you have beer with Nightrose yet?
[20:30] <Riddell> mgraesslin: qt raster is not longer set with up to date kubuntu-default-settings in natty
[20:31] <mgraesslin> ok
[20:31] <mgraesslin> so that's then not the reason for ulysses problems
[20:31] <Riddell> sheytan: well we could do it, but I have idea about making Moin themes so it seems sensible to find someone who does
[20:31] <Riddell> mgraesslin: unless he has an old version
[20:31] <Riddell> ulysses: got /etc/X11/Xsession.d/80qtgraphicssystem ?
[20:32] <sheytan> Riddell what's Moin?
[20:32] <Riddell> sheytan: the wiki software we use
[20:32] <mgraesslin> it's written in apachelogger's most favorite programming language
[20:32] <apachelogger> french?
[20:33] <apachelogger> oh
[20:33] <apachelogger> pyth0rn
[20:33] <sheytan> Riddell first of all, when we will have info about development tools, and others on the new web page, do we need the wiki ?
[20:33] <apachelogger> mgraesslin: one gets to notice that a lot
[20:34] <apachelogger> sheytan: yes
[20:35] <ulysses> apachelogger: raster
[20:35] <apachelogger> ulysses: you are out of date it seems or you have used the graphicssystem kcm to switch to raster...
[20:35] <ulysses> Riddell: I have
[20:35] <apachelogger> mgraesslin: ^
[20:36] <mgraesslin> ulysses: switch back to native if you want desktop effects
[20:37] <mgraesslin> apachelogger: given our bug reports users who use the 4.6 PPA and have an Intel GPU love your kcm
[20:37] <apachelogger> ^^
[20:37] <ulysses> how?
[20:37] <apachelogger> mgraesslin: sorry :)
[20:37] <mgraesslin> apachelogger: no need - it was useful as it helped to identify the issue
[20:38] <apachelogger> ic
[20:40] <sheytan> apachelogger can't we just put all the stuff into one page?
[20:40] <sheytan> imho wikis suck
[20:40] <apachelogger> IMHO they do not
[20:40] <sheytan> and it's hard to find stuff on them
[20:40] <apachelogger> except for ours
[20:40] <apachelogger> but that is another story
[20:41] <sheytan> apachelogger well, so tell me please what info you can't put into the new kubuntu website which you can on the wiki?
[20:42] <apachelogger> let me throw another question in return... do you want everyone with a launchpad account to be able to edit the kubuntu website?
[20:43] <sheytan> apachelogger edit for what? To add new stuff? Can't we choose like 2-3 person for do that?
[20:43] <sheytan> And even if, we can make just a sepcyfic part of the page editable for them
[20:43] <apachelogger> sheytan: to answer your question then: we cannot put information there that needs or should be editable by everyone
[20:43] <ulysses> apachelogger: how can I switch back?
[20:44] <apachelogger> such as a meeting agenda
[20:44] <apachelogger> ulysses: open the kcm and swich back to native
[20:44] <sheytan> apachelogger as i said, cant we make just a specyfic part of the page editable?
[20:44] <apachelogger> that requires someone doing that
[20:45] <apachelogger> workflows that depend on a small team == ultimate super shit and management nightmare
[20:45] <sheytan> apachelogger you mean to write code for this feature?
[20:45] <apachelogger> sheytan: no, creating new pages as the community requires it
[20:45] <apachelogger> then assigning permissions accordingly
[20:45] <apachelogger> then the community needs to mess with html stuff flip flup
[20:46] <apachelogger> the website and the wiki address different needs
[20:46] <apachelogger> but
[20:46] <ulysses> meh, I can't find
[20:46] <apachelogger> as you were asking in a very specific context anyway
[20:46] <apachelogger> sheytan: the theming should go away
[20:46] <apachelogger> kubuntu wiki should be ubuntu wiki
[20:47] <apachelogger> as we are part of the ubuntu community but form a dedicated team for the kubuntu distribution
[20:47] <sheytan> apachelogger i might agree. Wiki: ubuntu stuff, the new web page: kubuntu stuff
[20:47] <apachelogger> making it appear as if the wiki were made for kubuntu is a wrong thing
[20:47] <apachelogger> as it is confusing
[20:47] <apachelogger> because it is a wiki filled with foobar from all sorts of ubuntu teams
[20:47] <sheytan> wiki: a technical side, for devs and stuff, the page: users related stuff
[20:48] <apachelogger> when do we send users to the wiki now?
[20:48] <apachelogger> AFAIK we do not have user relevant content on the wiki
[20:48] <apachelogger> never had
[20:49] <sheytan> apachelogger: we don't need to. We can put all user related stuff on the page. When there's a meeting or something, we can post a news on the page and link to wiki with the agenda
[20:49]  * apachelogger notes that he does not think meetings should get a news
[20:49] <sheytan> why not?
[20:50] <apachelogger> because those are community meetings and if someone does not feel invovled enough to actually subscribe to the low frequency dev mailing list then I do not care much for their opinion
[20:50] <apachelogger> basically: if things get put into too public places people will show up that have actually no sensible input to give but disrupt discussion
[20:51] <apachelogger> like say we discuss making gstreamer our god, people might show up and flood the meeting with claims how shitty gstreamer is and that actually mplayer should be our god
[20:52] <sheytan> apachelogger well, so there's no need to link users to the wiki
[20:52] <apachelogger> sheytan: isn't that what I said anyway? :P
[20:52] <sheytan> apachelogger yeah, and i do agree with that :D
[20:52]  * apachelogger fails to see the point of the discussion as the wiki has valid use cases and all of them lay outside the scope of the average user and thus the website itself too
[20:56] <Riddell> sheytan: how do you mean info about development tools?
[20:57] <apachelogger> Riddell: I think there was a bit of confusion as to what the wiki is used for
[20:57] <apachelogger> also the new website includes a list and description of dev tools on kubuntu and whatnot
[20:58] <apachelogger> Riddell: have you been hiding on sunday? ^^
[20:59] <sheytan> Riddell we have general info about how to start development for Kubuntu/KDE on the new page
[20:59] <sheytan> Riddell and as we both, me and apachelogger agree, the wiki should be developers related, not users
[20:59] <sheytan> users shouldn't look for information about their OS on the wiki
[21:00] <sheytan> that's what Support page is for
[21:00] <apachelogger> s/developers/community ;)
[21:00] <sheytan> yeah :D
[21:00] <Riddell> apachelogger: on Sunday I was on a train (don't you start, already had hassle from my gf for that!)
[21:00] <apachelogger> uh uh uh
[21:01] <apachelogger> Riddell: I shall hug you twice at UDS then :P
[21:01] <ulysses> apachelogger: I kde-config-qt-graphicssystem, switched to OpenGL, and now after the splash screen nothing happens
[21:01] <apachelogger> :O
[21:01] <ulysses> installed*
[21:01] <apachelogger> yeah
[21:01] <apachelogger> you should not use opengl :P
[21:01] <apachelogger> not on intel anyway
[21:02] <CIA-40> [docmessages] ecuadra * 1219283 * trunk/ (35 files in 18 dirs) SVN_SILENT Spanish translation update by Kira J. Fern?\195?\161ndez & Roc?\195?\173o Gallego CC_MAIL: kirajfdez<EMAIL_ADDRESS>[21:02] <Riddell> sheytan: I'm not sure what change you are proposing
[21:02] <apachelogger> if raster already falls apart there...
[21:04] <sheytan> Riddell first of all, that we should marge the Kubuntu wiki with the Ubuntu one, couse the information are almost the same. Then, we shouldn't add users related info on the wiki. They should go to the new web site.
[21:05] <apachelogger> sheytan: they are *exactly* the same
[21:05] <apachelogger> wiki.kubuntu.org is just wiki.ubuntu.com with a different theme
[21:05] <sheytan> apachelogger and what about a todo lists? They are different :)
[21:05] <apachelogger> and no one is adding user content to the wiki
[21:05] <apachelogger> sheytan: no
[21:05] <apachelogger> they are different pages
[21:06] <sheytan> well, right
[21:06] <sheytan> apachelogger so the Kubuntu wiki should die? :D
[21:06] <apachelogger> woohooo, lover returned with cigs \o/
[21:07] <apachelogger> sheytan: well, if no one cares to keep the theme in line with the website theme it should just use the ubuntu theme
[21:07] <apachelogger> it cannot simply die for consistency reasons and whatnot
[21:07] <apachelogger> also it being there does not particularly cause problems
[21:08] <sheytan> apachelogger But i'm on the way with the theme, the problem is, that the ubuntu team needs to implement it
[21:08] <Riddell> sheytan: anyone can implement it who knows how to make moin themes
[21:08] <sheytan> Riddell do we have anyone in the Kubuntu team
[21:08] <sheytan> ?
[21:08] <Riddell> not that I know of
[21:09] <Riddell> Kubuntu is part of Ubuntu, we should be happy to ask for help from other parts, not be isolated
[21:09] <sheytan> and that's the thing. When i create the theme, it will take ages to implement :)
[21:09] <sheytan> same problem is for ofir, that he has no access to the server, to work on the page
[21:10] <sheytan> did something change in this case?
[21:10] <Riddell> it's unfortunate that it's not easy to make a wiki theme, but that's the fault of the wiki software, not the fault of any part of ubuntu
[21:10] <apachelogger> *nod*
[21:10] <apachelogger> also I would like to remind you that the wiki software is written in pyth0rn ;)
[21:11] <Riddell> it's a pain that we rely on canonical sysadmin to update the website theme but they say they will respond within a day next time we ask them to update it
[21:12] <sheytan> Riddell so i don't understand why ofir needs access to the server to keep the development
[21:12] <sheytan> i'm lost
[21:14] <ryanakca> Aye, they're still running moinmoin 1.6.3, which was severely outdated when I did the current theme. I think the current moinmoin version is 1.9.x
[21:14] <apachelogger> sheytan: well, he does more than just theming :P
[21:15] <apachelogger> themes are considerable easy to deploy (as the security review will be rather quick and stuff)
[21:15] <sheytan> apachelogger sure he does, but as you know, he doesn't have access to the server, so he cannot continue the development which sucks, cause we loose time ;(
[21:16] <apachelogger> yes
[21:16] <apachelogger> though I absolutely understand why he does not get access
[21:17] <sheytan> why
[21:17] <apachelogger> security reasons
[21:17] <Riddell> sheytan: ooh we could always try and convince ryanakca to make us a new wiki theme
[21:17] <apachelogger> also liability
[21:18]  * ryanakca chokes
[21:18] <sheytan> apachelogger well, so tell me please how do we release the new page then?
[21:18] <apachelogger> sheytan: different server or very slowly
[21:19] <sheytan> apachelogger that's the thing. Riddell had to ask KDE to host our page, but i don't know where are we now with it :(
[21:19] <apachelogger> or you convince a sysadmin to fall madly in love with the kubuntu community and help you work on the website in your sparetime and stuff
[21:19] <apachelogger> s/your/his
[21:20] <apachelogger> then when he is at work he is more dedicated to get things moved more quickly and also has more insight in the code already etc. etc.
[21:21] <apachelogger> I call it this the creeping community benefit
[21:21] <ryanakca> apachelogger: regarding a quick security review: our last wiki theme review took three months.
[21:21] <sheytan> apachelogger the code stuff is made by ofir. Anyway, he might don't have freetime when ubuntu guy has. Wouldn't it be way better to have access to it when we need it?
[21:21] <apachelogger> ryanakca: quick WRT time that it actually takes to conduct the review
[21:21] <sheytan> maybe we should like buy  a new server :D
[21:21] <apachelogger> ryanakca: if you take a look at open security bugs I consider 3 months rather fast processing for security team standards ^^
[21:22] <apachelogger> sheytan: sure it would
[21:22] <apachelogger> but it is not possible
[21:22] <apachelogger> for good and sane reasons
[21:22] <sheytan> and they are?
[21:22] <apachelogger> security and liability
[21:22] <apachelogger> anyhow, discussion won't help
[21:23] <apachelogger> they are canonical servers and canonical decides who gets access
[21:23] <sheytan> so in that case, we will never release the new page :)
[21:23] <apachelogger> so other options must be evaluated or deal with the situation or try to get creeping community benefit going
[21:23]  * apachelogger notes that we do way to little with regards to creeping community benefit anyway
[21:24] <apachelogger> Nightrose: you could do a talk on CCB some day ;)
[21:24] <ryanakca> As for me making the new wiki theme, I've had my fill of running after sysadmins, I'll pass for now.
[21:25] <apachelogger> sheytan: the rainbow has many colors... you just have to notice them and enjoy them
[21:25] <apachelogger> wohooo
[21:25] <apachelogger> bf returned with cigarettes \o/
[21:26] <sheytan> apachelogger well, the artwork is almost done, text just needs to be reviewd from some native english dude and  that's it. The technical side is not my thing anyway.
[21:26] <sheytan> But it would suck, that we have everything to make a really great page for everyone, and not have the possibility to publish it
[21:34] <apachelogger> sheytan: you just have to look for other options
[21:35] <apachelogger> or in the worst case scenario hope for quick processing by sysadmins and security team
[21:37] <bambee> see you thursday
[21:37] <bambee> 'night
[22:33] <CIA-40> [messages] alvarenga * 1219291 * (14 files in 9 dirs) [KDE-pt_BR]
[22:34] <Riddell> ?
[22:34] <Riddell> apachelogger, JontheEchidna: who knows about CIA bot and why it's notifying us of translations?
[22:35] <apachelogger> here I was, not reading the notification thinking it was about either things that make me famous or at least make me look like 18 again
[22:35] <apachelogger> yet it was just cia
[22:35] <JontheEchidna> it's announcing muon/libqapt commits. I thought we were filtering out l10n though
[22:35] <apachelogger> Riddell: supposedly the qapt/muon filters are too fuzzy
[22:35] <JontheEchidna> git seems to have broken the qapt/muon filters anyways
[22:36] <apachelogger> so whenver someone touches something like that it matches our bot rules
[22:36] <apachelogger> JontheEchidna: you should be using module stuff sort things
[22:36] <apachelogger> probably requires some playing
[22:36] <apachelogger> also I am drunk
[22:36] <apachelogger> dont listen to me
[22:36] <JontheEchidna> lol
[22:36]  * apachelogger blames it on Riddell
[22:37] <apachelogger> we went home too early on saturday and yesterday I did not get no drink at all
[22:37] <apachelogger> well
[22:37] <apachelogger> except for the 5 beers @fosdem
[22:38] <Riddell> we were up until midnight drinking on saturday!  that's quite late enough for anyone with a conference starting at 9 the next day
[22:38] <apachelogger> shadeslayer: I mentioned that beer deployment was successful?
[22:38] <JontheEchidna> Riddell: I think I've fixed it
[22:38] <Riddell> thanks JontheEchidna
[22:39] <apachelogger> shadeslayer: also jelmer is a very nice guy, you should throw more beer at him at uds-o ;)
[22:39] <apachelogger> Riddell: I was hacking till 4 ;)
[22:39]  * apachelogger made some pretty nice improvements to qt vlc mobile
[22:40] <apachelogger> also the qt mobile ui is getting more defaultism as Qt is becoming available on so many platforms, which means more fame for me :D
[22:40] <apachelogger> Riddell: it actually was working on sunday ;)
[22:41] <apachelogger> kinda broke it doay
[22:42] <apachelogger> also I would like to get hold of dantti
[22:50] <Riddell> apachelogger: something we should consider for future Kubuntu Mobile?
[22:51] <apachelogger> Riddell: possibly
[22:51] <apachelogger> unless I get something mobile going with phonon
[22:52] <apachelogger> I mean, I really really want to make a good looking video player using qgraphisscene, so doing that with a more mobile ui wouldn't be too difficult
[22:52] <apachelogger> but who knows if I ever actually get to do it :)


[00:00] <mnemo> Sarvatt: btw, you should get some sleep..  :)
[00:08] <maxb> Can anyone point me at any documentation which explains how X gets its xkb_layout these days? Since today's hal upload ceasing to deal with keymaps in favour of leaving it to udev-extras, my X no longer picks up the "gb" layout for my system and defaults to "us" instead
[00:10] <Sarvatt> i'd be interested in knowing that too, i have to customize my layout because i use a gateway bios from a clone of this aspire one and i can't just change the acer hal fdi to match Gateway anymore
[00:11] <maxb> Why a Gateway BIOS in an Acer, ooi?
[00:11] <Sarvatt> acer limits the number of backlight brightness levels in their bios
[00:12] <maxb> ah, ues
[00:12] <maxb> *yes
[00:12] <Sarvatt> gateway one is the exact same thing minus that part because they never used the panels with flickering problems at the lowest levels
[00:12] <Sarvatt> i get 30 minutes more battery life with the gateway one :d
[00:12] <maxb> I have a flickery one unfortunately
[00:13] <maxb> Though I'd still like to have the option of the lower brightnesses
[00:13] <Sarvatt> i do too, otherwise I would use the acer bios because it only blacklists the flickery one from the lowest levels
[00:13] <Sarvatt> flickering during hdd access is a small price to pay for 30 minutes more battery life :d
[00:14] <Sarvatt> http://macles.blogspot.com/2009/03/brightness-table.html#comments
[00:30] <Sarvatt> oh good, looks like libdrm is getting updated to 2.4.10 and adding drm_intel_bo_disable_reuse that might fix that swapping/font corruption problem
[01:12] <bryce> mnemo: btw, there's a technique I use in launchpad when asking questions - if the bug is already set to 'Incomplete', I move it to 'New', and then 'Incomplete' after asking my question.  This resets the "without reply" toggle on the bug
[01:12] <bryce> mnemo: it is a hassle, but by doing this it makes it easier to do a search for "Incomplete with response" bugs to see ones that the reporter (or some me-tooer) has answered
[01:13] <bryce> unfortunately launchpad is not smart enough to realize when us triagers comment on an Incomplete bug, it doesn't count as a "response" :-)
[02:31] <Sarvatt> bryce: I build -intel 2.7.1 final release here using your 2.7.0 debian instead of merging debian's like we do on edgers incase you want to copy it to x-updates https://launchpad.net/~sarvatt/+archive/sarvatt-graphics
[02:32] <Sarvatt> so it's got all of the patches except 119_drm_bo_unreference_needs_null.patch which is already in 2.7.1
[03:02] <bryce> Sarvatt: ah, excellent thanks
[03:08] <bryce> probably I should do the merge using the official tarball
[03:14] <Sarvatt> oops, forgot to change the commit id it was based on in the changelog. ah well, wanted to rebuild it against the new 2.4.10 drm anyway
[03:55] <bryce> ok, 2.7.1 packaged and in process of building:  https://edge.launchpad.net/~ubuntu-x-swat/+archive/ppa
[03:55] <bryce> once it's built and a couple people verify it's good to go, I'll move it to x-updates
[09:13] <tjaalton> upgraded to karmic, now reboot..
[09:16] <tjaalton> hmm, wrong layout
[09:25] <Sarvatt> have you guys considered backporting http://cgit.freedesktop.org/mesa/mesa/commit/?h=mesa_7_4_branch&id=63cde0ea0e2bc85005136c353c363777488804d2 to jaunty's mesa?
[09:25] <Sarvatt> re: bug 359392
[09:26] <tjaalton> haven't seen it before, but looks sane
[09:28] <Sarvatt> i was just looking over https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/359392 again and have seen they backported that patch to all the branches
[09:30] <tjaalton> it's just a matter of workflow management
[09:31] <tjaalton> I'd like to put these in a git branch (ubuntu-jaunty for instance) where such fixes can be staged and uploaded to a ppa or -proposed
[13:52] <jpds> Sarvatt: No, this was a hardy -> intrepid -> jaunty upgrade.
[15:38] <apw> bryce, hey ...
[15:38] <apw> it seems that your test version of x does seem to have changed behaviour on mtrr for the better, but it still seems to remove the mtrr ...
[15:39] <apw> 2:2.6.3-0ubuntu9.3~bug314928~2 is installed
[15:40] <apw> by w
[17:43] <bryce> apw, ok, that's good... is there removed mtrr's causing further problems I take it?
[17:44] <apw> it seems to still badly interact with the kernel, as in it still removes the mtrr on exit
[17:44] <apw> i see this both for logout and for guess session exit
[17:45] <apw> it is better in that for a rather more invasive kernel patch which adds and removes the mtrr on vt switch the mtrr does survive with your new xserver.  but the viable patch to add and remove mtrr at load/unload still gets broken by it
[17:47] <bryce> hrm
[17:49] <apw> [  203.861744] Pid: 3553, comm: Xorg Tainted: G        W  2.6.28-13-generic #44~
[17:49] <apw> lp314928apw5
[17:50] <apw> that is the process which is calling the ioctl ...
[17:51] <bryce> what is the "viable patch"?
[17:51] <apw> the clean backport of upstream behavour is to add and remove the mtrr at load/unload time.  the patch matching the further normal semantics is the one i am looking at as viable
[17:52] <bryce> ahh
[17:52] <apw> the other was a bodge i did to see if i could get round things the xserver was doing, doing it at enter/leave vt time.  but that seemed to get hurt by the xserver also fiddling at VT switch time
[17:52] <bryce> ok, so either there is another bit of code removing mtrr's, or the code I if'd still gets called in some circumstances
[17:52] <apw> your change i _think_ has removed the vt switch fiddle, but perhaps not the exit fiddle
[17:53] <apw> yeah something like that
[17:53] <bryce> would it help for me to add some debug comments on each call so you can sort out which is being called?  or have you been able to sort that out via gdb?
[17:53] <apw> i've been tracing it with kernel debug thus far
[17:53] <bryce> (or maybe it'd be obvious if I skim through the code for similar mtrr stuff)
[17:54] <apw> but we can try it pretty easy as it exhibits on guess sessions too, so its not sooo iintrusive to test
[17:55] <hyperair> anyone familiar with the issue of intel's gpu driver leaking memory like a bloody sieve?
[17:56] <apw> which version?  kernel memory?  what workload?  many of us are using intel successfully
[17:56] <bryce> apw: hmm, the driver seems to call i830_fixup_mtrrs in just the one place
[17:56] <bryce> apw: there's mtrr code in the xserver which I wonder about
[17:56] <apw> in the generic part you mean?
[17:57] <bryce> yeah
[17:57] <bryce> I grepped "mtrr" in the xserver core and it spewed a bunch of stuff, but then jbarnes pointed us at this patch so I ignored it.  But now I wonder if it's worth looking at.
[17:58] <jbarnes> bryce: was my patch not sufficient?
[17:58] <jbarnes> I think with libpciaccess the server won't mess with mtrrs anymore
[17:59] <bryce> jbarnes: no apw says he's still getting mtrr's removed, although it's considerably better
[17:59] <jbarnes> hm
[17:59] <bryce> apw: do you get any messages "Removing bad MTRR range" or "Failed to remove bad MTRR range"?
[17:59] <apw> yeah its definatly happening less often.  i beleive it was happening at vt switch into another x-server and is not now
[17:59] <apw> bryce, in Xorg.0.log ?
[18:00] <bryce> yes
[18:00] <apw> nothing about mtrr at all in there
[18:00] <bryce> hmm
[18:00] <bryce> well, from what I understand of the code, if the -intel driver is removing MTRRs it should be printing at least one of  those messages
[18:01] <bryce> so if it's not -intel, and if the xserver isn't messing with mtrrs anymore... could it be something besides X doing it?
[18:03] <jbarnes> I think the mtrr code removes any ranges set by the process when it exits
[18:04] <jbarnes> iirc
[18:04] <bryce> by mtrr_remove_offending() ?
[18:04] <jbarnes> I was thinking the kernel
[18:04] <bryce> ah
[18:06] <jbarnes> yeah, I *think* when the mtrr file gets closed or the process exits its additions will be removed
[18:06] <jbarnes> unless some other process added them too
[18:08] <apw> jbarnes, i am seeing an explicit removals occuring via an ioctl on the mtrr control file, i added a warning to the kernel and it logged the Xorg process as culprit
[18:08] <jbarnes> oh ok
[18:08] <jbarnes> with the intel driver huh?
[18:11] <jbarnes> the only place in the server that should hit that path is xf86MapVidMem, which we don't use anymore afaik
[18:15] <apw> perhaps its time for a version with some explicit debug in that routine to tell us if it is called
[18:15] <apw> just in case somehow my machine is mad and still using it somehow
[18:30] <apw> bryce, so what do you think?  perhaps a bit of debug in userspace might help here?  am able to test here
[18:30] <jbarnes> apw: if you have debug symbols, gdb could help too
[18:30] <jbarnes> set a breakpoint on the setWC callback and backtrace
[18:30] <jbarnes> or in one of the mtrr fns
[18:31] <apw> jbarnes, ok i think bryce did make some dbg ones
[18:31] <bryce> yep, you'll want -dbg's of both -intel and xorg-server
[18:32] <apw> hrm i think i only have the -intel one
[18:32] <bryce> xserver-xorg-core-dbg specifically
[18:50] <mnemo> bryce: -intel only prints those two messages to xorg.log if it tried to delete the mtrr but the operation failed
[18:51] <mnemo> well no sry.. the first one should have been in the xorg.log
[18:51] <mnemo> nevermind
[18:51] <bryce> right
[18:56] <tjaalton> huh, Xorg uses 100% cpu but everything seems to work
[18:57] <mnemo> tjaalton: on what gfx card? and what is it doing if you sample stacks with gdb?
[18:58] <tjaalton> mnemo: intel, karmic
[18:58] <tjaalton> can't use gdb since there's no other machine to ssh from
[18:58] <tjaalton> but I remember hearing something similar recently
[18:59] <mnemo> i've a bunch of -ati bugs for jaunty with constant 50% or 100% cpu (i guess the 50% cpu reports are for dual core users etc)
[19:01] <mikaelhm> mnemo, hi. Remember me:-)
[19:01] <mnemo> mikaelhm: yea, did you find a proper stacktrace yet?
[19:01] <mikaelhm> nop, it just happend again (first time today)
[19:01] <mikaelhm> there is nothing in the log
[19:02] <mikaelhm> but.
[19:02] <mikaelhm> When i look in the dmesg
[19:03] <mikaelhm> I see this http://paste.ubuntu.com/171815/
[19:04] <mikaelhm> and when i booted up I got this apport bug thingy-dingy
[19:05] <mnemo> yea thats like another bug probably
[19:05] <mikaelhm> Sorry the program "firefox" closed unexpe
[19:05] <mikaelhm> it said...
[19:06] <mnemo> mikaelhm: whenever something crashes, just send bug reports using apport.. doesnt matter if its pidgin or firefox or whatever.. they can often be useful for us
[19:06] <mnemo> mikaelhm: also, in some rare cases gfx driver bugs can also show up as application crashes
[19:06] <mikaelhm> should it be a new bug or related? I'm new to bugreporting.
[19:07] <mnemo> when it's a new program, always file a new bug
[19:07] <mikaelhm> oki
[19:07] <mikaelhm> it says, firefox chrashed in SIGSEGV in pthreaths_mutex_lock
[19:08] <mikaelhm> but i'll report it.
[19:08] <mnemo> please do
[19:09] <mikaelhm> Could not upload report data to crash database:
[19:09] <mikaelhm> <urlopen error The read operation timed out>
[19:10] <mnemo> that's because canonical cant run their servers properly :(
[19:10] <mikaelhm> I could only cancel it
[19:10] <mikaelhm> :-(
[19:10] <mnemo> it happens quite often with firefox because the debug dumps are so big that the server times out... i've filed a bug about it to the LP team but they havn't fix it yet
[19:10] <mnemo> this happens only for firefox crashes though
[19:10] <mikaelhm> ok
[19:11] <mnemo> so for those you might want to consider checking the checkbox "reduced report" (and not "complete") because that one works and it still gets us a stacktrace
[19:11] <mikaelhm> but how to report then? just manually,, or? can i get apport again?
[19:11] <mnemo> mikaelhm: if you want to re-submit the firefox that just happened you can look in /var/crash and then double click the .crash file that has firefox in the name (and select "reduce report" this time)
[19:13] <mikaelhm> cannot select reduce report
[19:13] <mnemo> strange.. why not? is that option grayed out?
[19:13] <mikaelhm> there is no option.
[19:14] <mikaelhm> damnit
[19:14] <mikaelhm> about 95% done
[19:15] <mikaelhm> there is only a ratio butten for complete report (106mb recommended) but its grayed out
[19:16] <mnemo> mikaelhm: when you click the .crash file you should see this --> http://temp.minimum.se/apport.png
[19:17] <mnemo> if you cant select "reduced report" then you probably can't report this bug unfortunatly.. :(
[19:20] <mikaelhm> i only see this http://i-dyllen.dk/apport.png
[19:22] <mnemo> ah, strange.. ok so then this bug cannot be submitted
[19:23] <mikaelhm> mnemo, cannot or might not, if i try several times will it work, i dont no the report bug,
[19:24] <mnemo> at least i've never managed to submit one of those, but I didn't try a lot of times..
[19:24] <mnemo> the bug that prevents this bug from being submitted is this bug: https://bugs.launchpad.net/malone/+bug/357907
[19:25] <mikaelhm> I think I managed it.
[19:27] <mikaelhm> no, this time the webpage gave me a timeout error
[19:27] <mikaelhm> https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+filebug/fuAN2CdKMInjhg7HGPiB7uPlNkV?field.title=firefox+crashed+with+SIGSEGV+in+pthread_mutex_lock()
[19:31] <tjaalton> ok, got a backtrace from my hung xserver
[19:31] <tjaalton> well, not hung but cpu-hungry
[19:33] <tjaalton> hmm backtrace wont do, need to use a profiler
[19:35] <mnemo> tjaalton: so what did the backtrace say?
[19:36] <tjaalton> mnemo: nothing of interest, because the server works
[19:36] <tjaalton> something is just eating resources
[19:37] <mnemo> WaitForSomething ?
[19:37] <tjaalton> yes
[19:38] <mnemo> i guess "info threads" also says just one thread?
[19:38] <mnemo> afaik X is always single threaded
[19:42] <tjaalton> sigh, profiling made easy.. not!
[19:42] <mnemo> which one did you use?
[19:42] <tjaalton> trying oprofile
[19:42] <mnemo> i've never tried it myself but I heard they use sysprof in #intel-gfx sometimes
[19:44] <tjaalton> ok, trying it
[19:46] <tjaalton> "in kernel"
[19:46] <tjaalton> right, thanks
[19:46] <tjaalton> not very helpful
[19:46] <mnemo> sysprof can split that up as well I think
[19:46] <mnemo> but then you need kernel debug symbols installed first
[19:47] <tjaalton> sigh^2
[19:48] <tjaalton> don't think they're apt-gettable
[19:51] <tjaalton> ah, found it
[19:53] <mnemo> tjaalton: cool, what package was it?
[19:53] <tjaalton> mnemo: no I mean found the ddebs
[19:55] <mnemo> tjaalton: where did you get them? i'd like to try it as well..
[19:55] <tjaalton> ddebs.ubuntu.com
[19:59] <tjaalton> apt-get doesn't seem to work though
[20:00] <mnemo> tjaalton: was that a replacement kernel with debug info or was it added debug symbols for the existing normal package? (i.e. like how -dbgsym works)
[20:00] <tjaalton> just the symbols
[20:05] <mnemo> they dont even seem to have symbols the stock jaunty kernel in there... i just find 2.6.28-12 in http://ddebs.ubuntu.com/pool/main/l/linux/  but im still on -11 (maybe -12 is in proposed?)
[20:10] <tjaalton> I dont think sysprof is meant for debugging the kernel
[20:10] <tjaalton> it still doesn't split it up
[20:18] <tjaalton> great, opreport doesn't work
[20:19] <tjaalton> needs a rebuild
[20:30] <mnemo> tjaalton: did oprofile give you anything yet?
[20:38] <tjaalton> mnemo: not yet
[20:39] <tjaalton> need to learn how to use it first
[20:42] <tjaalton> bah, opreport doesn't work, and doesn't build
[20:42] <tjaalton> so that's it then
[21:06] <tjaalton> huh, I can't suspend.. grr
[21:13] <Sarvatt> i just started getting this too yesterday tjaalton, are you on karmic too?
[21:13] <tjaalton> Sarvatt: yes
[21:13] <tjaalton> the hotkeys don't work, and the applet only has logout
[21:13] <Sarvatt> systems too darn slow to do anything when it happens, takes about 3 minutes for the VT to come up but I'm on a slow atom cpu :D
[21:21] <Sarvatt> yep no suspend/hibernate on my faster-user-switch applet either, hotkeys are screwy too since the change to udev-extras
[21:21] <Sarvatt> been a rough last few days for karmic
[21:22] <Sarvatt> i get a devicekit battery fully charged notification every time i plug ac in too no matter the charge level
[23:10] <mnemo> bryce: ping?
[23:13] <mnemo> i was going to ask you if you've seen any like this before? --> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/376220
[23:13] <bryce> mm
[23:13] <bryce> looking
[23:13] <mnemo> its my mesa SRU so im a bit paranoid
[23:13] <mnemo> its probably nothing
[23:14] <mnemo> it was copied from proposed to updates today
[23:14] <bryce> guess would be that it's a foss-vs-proprietary issue
[23:14] <mnemo> how so?
[23:14] <bryce> wait, no
[23:14] <mnemo> the log doesnt actually show any error for mesa so I was thinking it might be a bug in apport
[23:15] <mnemo> because those ttf fonts seem to fail
[23:15] <mnemo> and maybe then it gets the package wrong?
[23:15] <bryce> 2009-05-08 11:00:47 ERROR -1: Malformed status line.
[23:16] <bryce> maybe an error in sources.list?
[23:16] <mnemo> i think the malformed status thing could be a bad reply from sourceforge when its wgetting the proprietary fonts
[23:16] <bryce> ok
[23:17] <mnemo> my other theory was that maybe he tried the mesa upgrade from proposed and so thats why he already had it
[23:17] <mnemo> but if apport triggers on that then i guess i should have seen something like it before
[23:17] <mnemo> anyway, its probably nothing
[23:17] <bryce> yeah not sure
[23:18] <mnemo> im going to sleep now so..
[23:18] <mnemo> i hope this doesnt blow up overnight :)
[23:18] <bryce> night mnemo :-)
[23:18] <mnemo> nn bye
[23:45] <bryce> tjaalton: do you know if we need mdetect for anything anymore?  Isn't that no longer needed with dexconf, etc.?
[23:46] <bryce> if not, we can just sync -vmmouse from Debian I think.