[13:03] <excalibr> pong
[20:51] <ejat> pokes ang
[20:51] <ejat> anyone ?
[20:51]  * ejat pang fairuz


[00:39] <pulp> anyone here?
[09:43] <skramer_> Hi. Does anybody know why sometimes when plug-in my USB headset, the normal laptop sound is not muted & no sound comes from USB? Is there any bug in 20.04, Audio device: NVIDIA Corporation Device 10fa (rev a1)...
[10:21] <Mekaneck> skramer_: if you want to know if there'sa bug search launchpad for it :)
[11:19] <skramer_> Mekaneck: That option did not even come to my mind... Thanks for the reminder :)
[12:14] <BluesKaj> Hi folks
[15:39]  * Mekaneck joined the kubuntu side of things
[15:39] <Mekaneck> :D
[18:46] <Omarman> Howdi.. quick question.. When I download something in Firefox, and select the "open containing folder" option... I get sent to a program called Files instead of Dolphin. Is there a way to change that so that I always use Dolphin?
[18:58] <krytarik> Omarman: https://askubuntu.com/questions/84929/how-to-set-up-dolphin-as-default-file-manager/335911#335911 - should be something like this answer.
[19:02] <Omarman> Thank you.. I'll look into it...
[19:42] <Omarman> omar@NUCi5:~$ xdg-mime query default inode/directory
[19:42] <Omarman> org.kde.dolphin.desktop
[19:43] <Omarman> it's already set as dolphin...  but Firefox insists on opening " Files"
[19:45] <Omarman> Oh... I think it's a GTK thing... Firefox is using the GTK default


[17:55] <dax> !kernelcleanup is <reply> For information about removing old kernels to free up space on /boot, see https://help.ubuntu.com/community/RemoveOldKernels
[23:30] <bazhang> CarlFK, teamviewer me!
[23:31] <CarlFK> bazhang: wut?
[23:31] <bazhang> I thought you wanted someone to open a port
[23:32] <CarlFK> it is how I have always done vnc


[01:45] <mwhudson> um i'm confused
[01:45] <mwhudson> i uploaded golang-1.6_1.6-0ubuntu3_source.changes a while ago but it seems to have disappeared
[01:45] <mwhudson> about 25 mins ago i think
[02:01] <slangasek> mwhudson: I see one in the unapproved queue that arrived 9 minutes after your last comment
[02:01] <mwhudson> slangasek: yes, that's the one that arrived when i just gave up waiting and tried again :/
[02:03] <slangasek> ok
[02:06] <mwhudson> slangasek: should the bot that auto accepts non-seeded uploads still be running?
[02:06] <slangasek> mwhudson: yes, it should
[02:18] <mwhudson> ah there it is
[02:21] <stgraber> golang doesn't get auto-accepted as it's in the supported seed
[02:21] <stgraber> I manually reviewed it
[02:22] <stgraber> slangasek: if you have a minute, can you review that lxc upload?
[02:23] <slangasek> stgraber: yeah... and I guess you just accepted squid3, which is buggy
[02:23] <slangasek> queue needs proper locking. :P
[02:25] <stgraber> there a bunch of things the LP queue implementation needs before locking :)
[02:26] <stgraber> *are
[02:26] <mwhudson> stgraber: oh ok
[02:26] <mwhudson> stgraber: thanks
[02:30] <stgraber> slangasek: I'm taking a look at maas
[02:31] <slangasek> stgraber: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/comments/26
[02:31] <ubot5`> Launchpad bug 1473691 in squid3 (Ubuntu) "[FFe] squid: Update to latest upstream release (3.5)" [Critical,Fix committed]
[02:35] <stgraber> slangasek: shouldn't the new squid package preinst also nuke the old /etc/init.d/squid3 as it does the upstart job?
[02:42] <slangasek> stgraber: yes, it probably should
[02:42] <slangasek> but it doesn't, so that upload is buggy
[02:44] <slangasek> stgraber: alright, this lxc upload doesn't look like something that wants me to do a line-by-line review on it.  Is this bugfix only? what upstream testing has been done?
[02:47] <stgraber> slangasek: bugfix only ran through all of adt upstream as we do for every commit, has been in our ppa (as a git snapshot) for a few days
[02:47] <stgraber> and yeah, those rcs are bugfix only
[02:47] <slangasek> stgraber: ok, approved on the grounds that there are no /obvious/ bugs
[02:48] <stgraber> yeah, that's been the case for the past 13 rcs, hopefully we'll soon be done catching the non-obvious ones :)
[02:51] <stgraber> slangasek: ^ revert of previous upload + added conffile removal for /etc/init.d/squid3
[02:57] <slangasek> stgraber: dpkg-maintscript-helper has bits that are supposed to be called from other scripts besides the preinst; see the postinst and postrm
[02:57] <slangasek> ...which is a lot easier to keep track of if the maintainer were using .maintscript instead of trying to do this by hand
[03:01] <stgraber> wow, wtf, that's not going to be fragile at all
[03:04] <stgraber> grep tells me I've got the same number of those as there was for squid3.conf, that's about as much testing as this got
[03:04] <slangasek> heh
[08:06] <jamespage> hi release team - for some reason I thought I had already raised a FFe for the next Ceph stable release runup for 16.04
[08:06] <jamespage> https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1563714
[08:06] <ubot5`> Launchpad bug 1563714 in ceph (Ubuntu) "[FFe] Ceph Jewel stable release" [Undecided,New]
[08:06] <jamespage> apparently not so here it is....
[12:02] <rtg> infinity, pitti approved the FFE in bug #1558535. Could you also accept linux-snapdragon (and -meta) in the NEW queue ?
[12:02] <ubot5`> bug 1558535 in Ubuntu "FFE: linux-snapdragon" [Undecided,Triaged] https://launchpad.net/bugs/1558535
[12:08] <doko> rtg, done
[12:08] <rtg> doko, thanks
[12:18] <doko> cjwatson, infinity: what can we do about the migration of gcc-5-cross-ports / gcc-defaults-ports. gcc-5-cross-ports isn't mentioned in update_excuses at all
[12:19] <cjwatson> will have to leave that question to somebody else, sorry
[12:59] <stokachu> doko: mind rejecting conjure, i need to update it from the results around the juju discussions
[13:00] <doko> stokachu, done
[13:00] <stokachu> doko: thanks man
[16:33] <infinity> doko: Did you review that new kernel you accepted at all?
[16:57] <doko> infinity, only from a packaging point of view
[16:59] <infinity> doko: A license review tends to be a good thing on BSP kernels like that.
[16:59] <infinity> (it's not all upstream code from Linus's tree)
[16:59]  * infinity grabs it to do a quick once-over.
[17:12] <infinity> rtg: Alright, did a post-accept license review of linux-snapdragon, all looks sane.
[17:38] <teward> infinity: mind if I poke/bother you about nginx for a bit, off-channel in PM, surrounding FinalFreeze?
[17:39] <teward> s/surrounding/regarding/
[18:12] <xnox> i wonder how bad is it that germinate says
[18:12] <xnox> ? Missing source package: golang (for golang-github-gosexy-gettext-dev)
[18:12] <xnox> ? Missing source package: golang (for golang-dbus-dev)
[18:12] <xnox> ? Missing source package: golang (for golang-github-coreos-go-systemd-dev)
[18:12] <xnox> ? Missing source package: golang (for golang-github-pborman-uuid-dev)
[18:12] <xnox> ? Missing source package: golang (for golang-gopkg-tomb.v2-dev)
[18:12] <xnox> ? Missing source package: golang (for golang-github-gorilla-mux-dev)
[18:13] <infinity> xnox: Those should all be rebuilt against golang-1.6
[18:13] <infinity> If we're about to start enforcing Built-Using.
[18:14] <xnox> ah
[18:14] <xnox> so this is legit =)
[18:14] <infinity> Oh.  This is also broken. :(
[18:14]  * xnox is like surely golang is not gone
[18:14] <infinity> mwhudson: I found some lolz.
[18:15] <infinity> (base)adconrad@nosferatu:/var/lib/apt/lists$ grep '^Built-Using: golang ' *Packages | wc -l
[18:15] <infinity> 357
[18:15] <infinity> (base)adconrad@nosferatu:/var/lib/apt/lists$ grep '^Built-Using: golang-1.6 ' *Packages | wc -l
[18:15] <infinity> 0
[18:15] <infinity> (base)adconrad@nosferatu:/var/lib/apt/lists$ grep '^Built-Using: golang-defaults ' *Packages | wc -l
[18:15] <infinity> 12
[18:16] <infinity> mwhudson: Note that last one.  I'm guessing there's something that does a Package->Source resolution for "golang-go" and fills in the wrong bits, when it should actually be hunting down the compiler used (golang-1.6 or gccgo-6)
[18:18] <infinity> xnox: Anyhow, rebuilding all of those would probably turn "golang" into "golang-defaults" which, for the purpose of component-mismatches, will DTRT.  It's less ideal for actually tracking static compiling, though, and should be as above. :P
[18:35] <cjwatson> xnox,infinity: incidentally, per our conversation the other day, I realised that we also need to check for cases where sources in main b-d on virtual packages without a preferred real alternative, since those could end up being resolved differently
[19:55] <doko> does openstack still has a freeze exception?
[19:56] <infinity> yes.
[19:56] <infinity> doko: ^
[19:56] <doko> ta
[19:58] <teward> infinity: any chance you can review nginx (bug #1563393) for a freeze exception?  We're in the home stretch - keeping us as close to what upstream has for 1.10.x is still the goal.  which also reminds me, do you have any issues with me bouncing a couple of questions off you regarding nginx as we approach the final stretches of development?  (I'm keeping an eye on that FinalFreeze date, hence the need for a discussion)
[19:58] <ubot5`> bug 1563393 in nginx (Ubuntu) "[FreezeException Needed] Update nginx to 1.9.13." [Wishlist,New] https://launchpad.net/bugs/1563393
[19:58] <teward> the discussion is more important than ^ that getting a review today, though
[19:59] <infinity> teward: Discuss away.  I'm only doing IRC in small batches while I try to ignore blinky things to get other work done, but I'll get to you.
[19:59] <teward> infinity: OK, the discussion has to occur off-channel, though, mind a PM for that?
[19:59] <teward> given the info being shared
[19:59] <teward> (E:NotForChannel)
[20:05] <mwhudson> infinity: ah haha
[20:05] <mwhudson> infinity: file a bug?
[20:05] <infinity> mwhudson: Is that not what I did, via the IRC interface? :P
[20:05] <teward> heh
[20:06] <slangasek> mwhudson/api/v1/filebug
[20:06] <slangasek> (Internet RESTful Chat)
[20:07] <mwhudson> heh
[20:07] <mwhudson> i wonder what package the bug should be against...
[20:07] <infinity> mwhudson: Guessing dh-golang is where the magic happens.
[20:08] <infinity> mwhudson: And it probably just needs to dereference paths before doing the file->package->source resolution.
[20:08] <infinity> (Assuming it's checking the owner of /usr/bin/go and such)
[20:08] <doko> wondering if mozc should be accepted ... we still have a very old version ...
[20:08] <doko> https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1547816
[20:08] <ubot5`> Launchpad bug 1547816 in mozc (Debian) "Merge mozc (2.17.2116.102+gitfd0f5b34+dfsg-1) from Debian unstable (main)" [Unknown,New]
[21:40] <mwhudson> infinity: got an example of a package that has broken built-using?
[21:41] <mwhudson> uh i guess lxd probably
[21:44] <mwhudson> yeah
[21:48] <rtg> infinity, thanks, re: linux-snapdragon


[04:01] <stgraber> highvoltage: respun Edubuntu, that should give us a working amd64 build this time around. I probably won't be around to watch the build end, but it "should" work. If not, I'll look in the morning.
[08:23] <highvoltage> stgraber: seems like it worked, I'm almost half-way syncing now
[10:44] <highvoltage> hmm, doesn't seem to get to lightdm in virtualbox
[13:51] <stgraber> highvolt1ge: we'll need a FFe to remove the server bits from edubuntu for 13.04
[13:54] <highvoltage> stgraber: we need a FFe to remove features?
[13:54] <stgraber> yes, it's a feature change
[13:54] <highvoltage> ok
[13:56] <highvoltage> stgraber: I'm wondering if we should have a delayed beta release, there's two bugs that I'd rather not want in a beta if there is one (live system doesn't boot if there's a swap partition and default session is '10')
[13:57] <stgraber> and the installer showing stuff that don't work too
[13:58] <highvoltage> indeed, technically a beta shouldn't have that
[13:59] <stgraber> highvoltage: https://bugs.launchpad.net/ubuntu/+source/edubuntu-live/+bug/1154601
[14:00] <stgraber> highvoltage: hmm, and the icon theme is still wrong here...
[14:01] <highvoltage> yep, same. I remember you changing it to choose the right theme so that it has the right fallback set
[14:04] <stgraber> highvoltage: ok, pushing fixed edubuntu-artwork now
[18:26] <stgraber> highvolt1ge: can you make sure we get an updated slideshow by UI freeze (next Thursday)?
[18:38] <highvolt1ge> stgraber: I was just thinking of that today
[18:38] <highvolt1ge> stgraber: I originally pretty much stopped doing anything for this release with all the rolling release stuff happening, but I could have it before thursday, yes. possibly even tomorrow since I pretty much have the whole day for it
[18:50] <highvoltage> stgraber: having fun with the unity ffe? I like the way tumbleweed went ahead and marked it wontfix hehe
[18:51] <stgraber> highvoltage: :)
[18:51] <stgraber> highvoltage: oh, we also need to do something about the wallpaper before UIF
[18:52] <stgraber> highvoltage: so amd64 here boots fine, live ltsp works, installer works, lightdm is fine post-install and LTSP post-install appears to work too
[18:53] <stgraber> now to look at that swap weirdness, see if it fixed itself magically too
[18:55] <highvoltage> stgraber: I'll see what I can do about wallpaper tomorrow too, it's a tough one, I found a few on the wikimedia site a few weeks back but I wasn't sure how well they'd work as wallpapers, will have to check
[18:55] <stgraber> highvoltage: gah, no, that bug is still there, I guess I'll really have to get to the bottom of this then...
[18:59] <highvoltage> a horizontally flipped version of http://commons.wikimedia.org/wiki/File:Fleur_de_givre_L.jpg that's made slightly darker might work
[18:59] <stgraber> highvoltage: that stuff doesn't make sense... it's clearly swap related but it's not the swap script that's hanging...
[19:00] <highvoltage> I tried it before and it was just too bright
[19:00] <highvoltage> stgraber: yeah I also thought it's strange and couldn't think of what could cause it. even weirder that it's edubuntu specific.
[19:03] <stgraber> highvoltage: it's init that's hanging...
[19:04] <stgraber> highvoltage: I just added some debugging to the initramfs and it hangs after "exec run-init /root /sbin/init quiet splash --"
[19:11] <stgraber> highvoltage: and the even weirder thing is that the swap isn't even enabled...
[19:13] <highvoltage> really really weird.
[19:17] <stgraber> highvoltage: ah, ok, I think I understand how that stuff works now. We're probably looking at something blowing up in mountall
[19:20] <stgraber> yeah, definitely mountall being unhappy about something...
[19:38] <stgraber> highvoltage: so the magic conditions are: swap in /etc/fstab + cgroup-lite installed
[20:48] <highvoltage> stgraber: still weird. and interesting :)
[23:38] <stgraber> highvoltage: that one has got to be perfect^ :)


[12:00] <ZenWalker> hi all, ubports is 100% open source?
[13:06] <ThinkT510> the firmware for the devices probably isn't but ubports itself is


[01:40] <callmepk> good morning
[02:04] <duflu> Hi callmepk
[02:05] <callmepk> hi duflu
[05:43] <oSoMoN> good morning desktoppers
[05:55] <duflu> Hi oSoMoN
[05:56] <oSoMoN> hey duflu
[06:30] <seb128> goood morning desktopers
[06:32] <oSoMoN> salut seb128
[06:32] <seb128> oSoMoN, salut! en forme ?
[06:33] <oSoMoN> oui, beaucoup mieux, et toi?
[06:34] <ricotz> hello :) seb128 oSoMoN
[06:34] <oSoMoN> good morning ricotz
[06:34] <seb128> oSoMoN, un peu fatigué, de nouveau une nuit coupée, mais sinon ça va :)
[06:34] <seb128> ricotz, hey, how are you?
[06:35] <ricotz> seb128, a bit tired as well :)
[06:35] <duflu> Hi seb128
[06:35] <seb128> hey duflu! how are you? getting ready for the weekend? ;-)
[06:36] <duflu> seb128, suffering a sinus headache but it's tolerable. I think just feeling better is my first priority.
[06:46] <duflu> Ironically we have a weekend of excellent weather, which is also the cause of my pain
[07:06] <didrocks> good morning
[07:08] <jpnurmi> good morning
[07:09] <duflu> Hi didrocks and jpnurmi
[07:13] <didrocks> hey duflu, jpnurmi
[07:16] <jpnurmi> hey duflu and didrocks
[07:18] <seb128> lut didrocks , en forme ?
[07:18] <seb128> hey jpnurmi, how are you?
[07:18] <didrocks> salut seb128, ça va, et toi ?
[07:19] <seb128> didrocks, un peu fatigué mais ça va sinon :)
[07:24] <jpnurmi> hey seb128, i'm good thanks. as good as it gets in rainy swedish autumn :)
[07:25] <seb128> we have a sunny day here for a change :-)
[11:05] <seb128> jibel, hey, could you check again the utah jobs? the default_de one still fails on what seems ssh connect errors
[17:16] <seb128> https://people.canonical.com/~platform/desktop/versions/snaps.html includes mention for packages that need a rebuild for a CVE fix in a stage package now ;-)
[17:20] <mdeslaur> lol, all of them ;)
[17:20] <mdeslaur> damn security
[17:31] <oSoMoN> nice, well done seb128
[17:32] <seb128> :-)
[18:28] <sarnold> seb128: that's cool!
[21:27] <KGB-2> gnome-chess signed tags 992f4b3 Jeremy Bicha upstream/41.1 * Upstream version 41.1 * https://deb.li/38ZXG
[21:27] <KGB-2> gnome-chess upstream/latest f337567 Michael Catanzaro data/org.gnome.Chess.desktop.in * Fix Exec= line in desktop file * https://deb.li/3SV51
[21:27] <KGB-2> gnome-chess upstream/latest bef396d Dušan Kazik po/sk.po * Update Slovak translation * https://deb.li/Ncbd
[21:28] <KGB-2> gnome-chess upstream/latest 1e5cf80 Michael Catanzaro NEWS data/org.gnome.Chess.appdata.xml.in meson.build * Prepare 41.1 * https://deb.li/igXkV
[21:28] <KGB-2> gnome-chess upstream/latest 8eb52d1 Jeremy Bicha (5 files in 3 dirs) * New upstream version 41.1 * https://deb.li/3hXlz
[21:28] <KGB-2> gnome-chess pristine-tar 481c7d1 Jeremy Bicha gnome-chess_41.1.orig.tar.xz.delta gnome-chess_41.1.orig.tar.xz.id * pristine-tar data for gnome-chess_41.1.orig.tar.xz * https://deb.li/8BgR


[01:06] <VK7HSE> Is anyone having issues getting Karmic Alpha2 to install into VirtualBox? the standard desktop .iso appeared to hang prior to getting to the set up options! now currently attempting with alternate Karmic Alpha2!
[01:08] <VK7HSE> so far so good! 43% installed!
[02:01] <Wicla_> hey. Anyone else had problems with compiz.real? It's currently using 2584MB of swap
[02:02] <Wicla_> or, not only swap but in total it's using that amount of memory.
[02:03] <BUGabundo> Wicla_: mine is not even starting today :(
[02:04] <Wicla_> uhm okey. This is the second time this has happened. Last time was a few days ago
[02:08] <Wicla_> s/Last/First/ to make that sentence correct
[02:31] <ripps> Well, I've finally gotten Karmic installed, I'm trying to restore my sbackup of my /home
[02:36] <BUGabundo> ripps: YAY
[02:36] <BUGabundo> hello DanaG
[02:37] <ripps> BUGabundo: let's just hope everything restores properly. Also, I need to reinstall every package I had before. Hours of downloading packages for me.
[02:37] <BUGabundo> ripps: did you dpkg -l ?
[02:38] <BUGabundo> that would list all installed packages
[02:38] <BUGabundo> so you could just sed it, to generate apt line
[02:38] <ripps> BUGabundo: no, I wanted to have a cleaner system this time, I installed alot a crap I only used once
[02:38] <BUGabundo> I know the feeling
[02:38] <BUGabundo> but some I DO need
[02:46] <virtuald> <:
[02:46] <virtuald> :>
[02:48] <BUGabundo> ^..^
[03:18] <ghindo> Is anybody else having a bunch of packages being held back?
[03:20] <BUGabundo> ghindo: try $ sudo aptitude safe-upgrade
[03:33] <ghindo> Is udev-extras being held back for anybody else?  I haven't been able to update it for at least a week
[04:05] <RAOF> ghindo: That's probably because it'll remove hotkey-setup.  "sudo aptitude full-upgrade" will probably do what you want.
[04:11] <ghindo> RAOF:  Got it, thanks.  I probably should have looked at the changelog/forums
[05:33] <syn-ack> Any particular reason I have symlinks to my kernel in /... was just going thru this build trying to figure out how I can hack the mp3 codecs in it and noticed it
[05:34] <syn-ack> I do have /boot/ on its own ext2 part, btw so I shouldnt have anything in the root
[05:47] <darthanubis> https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose/+bug/347487
[07:05] <DanaG> Is there any easy way to take a non-running karmic 32-bit install and transpose it over to 64-bit?
[07:05] <DanaG> by "transpose", I mean package states, some conf files, and sources.list
[07:24] <virtuald> anyone noticed the horrible io scheduling in 2.6.30?
[07:27] <DanaG> argh!  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/365321
[07:27] <DanaG> ARGH
[07:47] <airstrike> i just wanted to share my opinion that this paper cuts project is simply great!
[08:13] <DanaG> I just figured out why my wifi wouldn't connect..... 2 of 3 wifi antennas were not attached!
[08:33] <ripps> How do I get gpg to use the pinentry method? I just reinstalled Ubuntu to Karmic and I don't know how to get gpg to remember my passpharase. My ppabot requires me to enter it a dozen times for each ppa package it builds w/ it's backports
[08:40] <Hobbsee> DanaG: yeah, that'd do it!
[08:40] <Hobbsee> ripps: install pinenty, relogin to X?
[08:40] <Hobbsee> ripps: actually, gnupg-agent woks quite nicely, too
[08:40] <Hobbsee> iirc
[08:43] <DanaG> But it worked fine in Windows, oddly enough.
[08:44] <DanaG> And it was giving me failed assertions... something about not being 802_1x
[08:44] <DanaG> I guess iwlagn doesn't like diversity.
[08:44] <DanaG> s/like/do/
[08:44] <DanaG> =þ
[09:03] <DanaG> arg, that "ear candy" thing is rather broken.
[09:03] <DanaG> It continuously insists on cranking volume up to 100%.
[09:04] <DanaG> SO IT MAKES EVERYTHING REALLY REALLY LOUD
[09:04] <DanaG> =þ
[09:19] <cwillu> DanaG, I already told you it's by design
[09:20] <DanaG> which is?
[09:20] <cwillu> max volume
[09:20] <DanaG> the REALLY REALLY LOUD?
[09:20] <cwillu> yes
[09:20] <DanaG> I think it's an issue of "earcandy" not dealing well with flat volumes.
[09:20] <DanaG> It cranks the app volume up to 100%.... and thus... affects the device volume, too.
[09:21] <cwillu> shouldn't be affecting the device volume
[09:21] <DanaG> I've honestly found flat volumes too confusing.
[09:21] <DanaG> try earcandy some time.... but have your speakers turned way down, first.
[09:21] <cwillu> you probably don't want to use it anyway, it does really really ugly things with polling
[09:21] <cwillu> DanaG, I sent it a few hundred lines of patches to it, no idea if he ever applied them
[09:21] <DanaG> yeah.  and the "move to new device" moves the thing FROM my BT headset back to onboard.
[09:21] <cwillu> not a huge fan of people who try to run projects out of the comments of a blog post :p
[09:22] <DanaG> I still disagree with flat-volumes... but that's something I can just live with disabling.  Might be nice to add it as a preference reachable by paprefs?
[09:22] <cwillu> earcandy ultimately feels like using a tiling window manager
[09:23] <cwillu> really annoying if you want your windows to stay where you left them
[09:23] <cwillu> and it's buggy too, which doesn't help :p
[09:23] <DanaG> yeah.
[09:23] <DanaG> I wish I could set PA like this:
[09:23] <cwillu> especially when the owner refuses to use such modern project management tools as "email"
[09:23] <DanaG> For App X, prefer sound cards A>B>C.
[09:24] <DanaG> For Y, prefer a different order.  If one is not present, drop back to another.
[09:24] <cwillu> it's got a _little_ bit of that baked in
[09:24] <DanaG> And have it move a stream from B to A when you plug in A.
[09:24] <cwillu> but ya
[09:24] <DanaG> Right now it drops back... but doesn't pop "forward" like win7 does.
[09:25] <cwillu> honestly, I'd be happy with a simple way of alt-mousewheeling on a window to change that window's volume, or to change everything _but_ that window's folume
[09:25] <DanaG> I just don't like how flat-volumes makes the volume slider for an app change the volume slider for the device, and vice versa.
[09:25] <cwillu> s/folume/volume/
[09:25] <DanaG> And moving an app to a different device... makes both the device slider and the app slider jump.
[09:25] <cwillu> which should actually be possible based on how earcandy is resolving pulseaudio clients back to the open applications
[09:27] <DanaG> The way I think of things is: device X is at some percent of its max volume, and app Y is at some portion of whatever the max is, set by X percent.
[09:27] <DanaG> Even if the backend changes the volume slider value to optimize hardware... the frontend should not make things jump around.
[09:29] <DanaG> oh, and then you have my odd USB audio device, that has two Speaker sliders.
[09:30] <DanaG> One has no effect at all when you twiddle it.  The other works fine, but indicates decibel ranges from 0.0dB to 0.0dB.
[09:51] <DanaG> ugh, stock bluetooth-applet is literally useless.
[09:51] <DanaG> You can bond / pair to a device... but then once you've done that, you can't DO anything with the device.
[11:04] <BUGabundo> compiz not starting for me!
[11:04] <BUGabundo> anyone else?
[11:10] <dupondje> BUGabundo: can't test as i'm using nouveau driver that has no 3D :(
[11:18] <BUGabundo> dupondje: yeah
[11:33] <jetienne> !info gcc
[11:35] <dupondje> somebody want to add my ppa ?
[11:35] <dupondje> https://launchpad.net/~dupondje/+archive/ppa
[11:35] <dupondje> need some people to test nautilus patch :D
[12:02] <dupondje> BUGabundo:  ? ;)
[12:02] <BUGabundo> dupondje: no no ! eheh need it working
[12:02] <BUGabundo> LO
[12:02] <BUGabundo> LOL
[12:02] <amortvigil> hi
[12:02] <BUGabundo> hey amortvigil
[12:03] <BUGabundo> eeh using the new webchat from freenode amortvigil?
[12:03] <amortvigil> how is koala doing?
[12:03] <amortvigil> BUGabundo: NOT SURE I USE webchat from the dutch community
[12:03] <BUGabundo> not bad
[12:03] <amortvigil> why?
[12:03] <BUGabundo> a few nagging bugs
[12:04] <amortvigil> ahhh ok
[12:04] <amortvigil> well i hope koala will work for mee 9.04 doesnt work atall :)
[12:05] <BUGabundo> why?
[12:06] <amortvigil> it freezes ramdomly i get atk errors
[12:06] <BUGabundo> and karmic?
[12:07] <amortvigil> not yet tested
[12:07] <amortvigil> afraid of an early alpha
[12:10] <BUGabundo> running a livecd/usb doesn't hurt
[12:56] <frandavid100> do you guys know with what protocols can you do a video call in empathy?
[13:25] <BluesKaj> Howdy
[13:25] <frandavid100> hiya BluesKaj
[13:25] <BluesKaj> hi frandavid100
[13:27] <BluesKaj> what's happening today ?
[14:02] <Tekno_> onks linuxille semmost näppärää powerpoint vieweriä
[14:02] <Tekno_> joka vaan näyttäs ne diat samantien
[14:05] <BluesKaj> !fi | Tekno_
[14:49] <muggi> hi
[14:49] <muggi> anyone followed this for installing grub2: https://wiki.kubuntu.org/Grub2#grub.cfg   ?
[14:49] <muggi> seems like i got stuck at grub 1.96, even though i followed the guide im trying to install grub2 under ubuntu 9.10
[14:50] <muggi> 1. i used to dualboot win xp  and linux mint 7 on my asus eee, i then tried to install .9.10 as the third boot choice, but found out later that grub2 under 9.10 cant dualboot without a fix
[14:50] <muggi>  but 9.10 never installed grub2, but grub-legacy (1.96), and now im tring to install grub2, but cant get it to work
[15:00] <darthanubis> muggi, always read the known issues from the release notes FIRST
[15:02] <muggi> I know now :-)  can see the install can fail, if there is other os's installed
[15:03] <darthanubis> yeah
[15:03] <muggi> at least i got the dualbooting to work
[15:04] <muggi> but its under grub 1.96, seems like i cant install grub2  (all in 9.10)
[15:57] <Machtin> is it usual not to get an answer to a security bug for 4 days?
[15:58] <bazhang> this early in the release cycle? could well be
[15:59] <Machtin> kk
[16:11] <joejc> i got banned from #ubuntu so i decided to never use linux ever again and i want you to ban me from here to so if for some reason i forget how much ubuntu people hate me i still cant come back
[16:13] <dupondje> there was probably a good reason why u got banned ...
[16:14] <joejc> i wanted to know if i could customize the notifications. can you just ban me?
[16:15] <BluesKaj> joejc, ubuntu isn't the only linux OS and if you were banned then you must be a bad bad boy/girl :)
[16:16] <joejc> what wrong with wanting different notifications?
[16:17] <darthanubis> joejc, you got some growing up to do kid.
[16:17] <joejc> just ban me
[16:17] <darthanubis> just leave
[16:17] <darthanubis> ban yourself
[16:18] <joejc> what do i need to do to get banned?
[16:18] <darthanubis> leave and uninstall your IRC client
[16:18] <darthanubis> joejc, your doing just fine, you'll be banned soon enough
[16:18] <joejc> i like irc just not people that ban for no reason so i want to give you a reason
[16:18] <darthanubis> or ignored
[16:18] <darthanubis> I agree there with the abuse of OP power
[16:19] <darthanubis> but you are coming across as a douchbag already
[16:19] <darthanubis> it is no wonder you got banned
[16:19] <darthanubis> ask a question pertinent to the channel, or leave?
[16:19] <BluesKaj> joejc, you din't get banned for no reason...perhaps you became a PITA with your irrelavent questions
[16:19] <darthanubis> do you need help or something?
[16:19] <joejc> if they didnt like what i was doing they could have kicked me and given a reason but they didnt so i want to get banned from every ubuntu related channel
[16:20] <darthanubis> joejc, what re you like 12 or something?
[16:20] <darthanubis> joejc, just go sit in the corner for a while
[16:20] <joejc> 26 just hate OPs who are bitches
[16:21] <BluesKaj> in order not do what hew wants we should just put him on ignore and his dumb questions won't show up in the chat
[16:21] <darthanubis> only type if you have something to add or need specific help. Otherwise, you are just a desperate and sad troll
[16:21] <joejc> figure the op is probably here too
[16:21] <joejc> ban me for being a troll
[16:21] <Hew> BluesKaj, ?
[16:21] <darthanubis> joejc, keep using profanity, that will obviously get you banned, if i could I would right now
[16:21] <BluesKaj> hew=he
[16:21] <tgpraveen> somebody please grant him his wish. he already has used profanity once
[16:21] <Hew> yes :P
[16:22] <joejc> darthanubis, then call the ops and get them to ban me
[16:22] <tgpraveen> call him yourself
[16:22]  * BluesKaj puts joejc on ignore
[16:22] <darthanubis> I don't care about you, or your issue, I can ignore you at my will
[16:22] <joejc> WHO?
[16:22] <darthanubis> Like BluesKaj  just did
[16:23] <lynggaard> I am looking for docs, or tips for doing a triple boot system (windows, ubuntu, opensolaris) having at leats the main part of ubuntu on a SSD, while having /home and /var on a regular disk... any pointers ?
[16:23] <darthanubis> joejc, sooo, troll, what can we do for you besides your sad pleas for attention?
[16:23] <lynggaard> preferably with the solaris readonly parts on the SSD as well
[16:23] <ziroday> lynggaard: well on doing the install you would place those parts where you want, and then describe them in fstab (if not done for you already)
[16:24] <darthanubis> lynggaard, read the release notes and known issues on the main page
[16:24] <joejc> so you arnt going to ban me for asking to be banned and saying bitch?
[16:25] <bazhang> joejc, please stop now
[16:25] <lynggaard> The ubuntu part of having /var and /home elsewhere I am clear on, it is more how to do this best in a triple boot system... should the SSD be the master ? og should the regular HD be the master, but having a /boot partition for linux pointing to the SSD?
[16:25] <joejc> thank you thats all  i needed to prove my point bye
[16:25] <bazhang> ?
[16:26] <ziroday> he has a loose screw, was most odd in #ubuntu
[16:26] <darthanubis> bazhang, he is just a lost kid
[16:26] <bazhang> okay thanks :)
[16:26] <ziroday> darthanubis: I doubt all children have loose screws.
[16:27] <darthanubis> true, I did not mean to insult all kids
[16:27] <lynggaard> darthanubis, the release notes says nothing related to my query
[16:27] <ziroday> lynggaard: mmm it would probably be best to stick /boot on SSD to lose that extra second of boot time.
[16:27] <darthanubis> lynggaard, you don't read well, perhaps?
[16:27]  * BluesKaj is too to waste time with juveys needing attention
[16:27] <BluesKaj> too old
[16:28] <darthanubis> grub2 is going to give you issues with your attempt
[16:28] <darthanubis> BluesKaj, i hear ya
[16:28] <lynggaard> darthanubis, apperently not. Could you be more specific about which paragraph I missed ?
[16:29] <darthanubis> refuse to look it up for you after pointing you in the right direction
[16:30] <darthanubis> in a nutshell, stay away from grub2
[16:31] <lynggaard> darthanubis, http://www.ubuntu.com/testing/karmic/alpha2 says nothing about dual/triple boot (infact the page doesn't even contain the word dual). neither does it say anything about SSD considerations.
[16:32] <ziroday> lynggaard: darthanubis is referring to "Due to the conversion to GRUB2, installation will fail if you try to install Karmic Alpha 2 on a system with other OSes installed. This will be fixed for Alpha 3. As a workaround in the meantime, you can choose to use GRUB1 instead by booting with the option: grub-installer/grub2_instead_of_grub_legacy=false."
[16:32] <ziroday> did any of that get cut off?
[16:32] <darthanubis> ziroday, no, and thank you
[16:32] <dupondje> or use daily cdimage, should work also :)
[16:33] <darthanubis> lynggaard, installation will fail if you try to install Karmic Alpha 2 on a system with other OSes installed.
[16:33] <darthanubis> is it crystal now?
[16:33] <ziroday> dupondje: just about to recommend that :)
[16:34] <lynggaard> ziroday, if that was the information he was trying to convey, it surely covers only a small part. and nothing related to my inquiry of " The ubuntu part of having /var and /home elsewhere I am clear on, it is more how to do this best in a triple boot system... should the SSD be the master ? og should the regular HD be the master, but having a /boot partition for linux pointing to the SSD?"
[16:34] <ziroday> lynggaard: I would recommend the /boot on the SSD as it will improve boot time. Otherwise it doesn't really matter.
[16:35] <dupondje> 14 seconds instead of 16 :p
[16:35] <dupondje> who cares :)
[16:35] <lynggaard> darthanubis, yes crystal clear that you only answered a small item which could be pointed to in the main page, insteda of trying to answer the real question assuming that I had allready read the front page
[16:36] <darthanubis> I threw you a bone is THIS is my thanks, because you can't read coherently? it is not for me or anyone to solve ALL your issues.
[16:36] <lynggaard> ziroday, but doesn't this mean the SSD will have to be master... or can the regular HD be master and have grub(2?) point to a boot on another hd.
[16:37] <dupondje> root & /boot can be on different hdd's ofc
[16:38] <lynggaard> ziroday,so regular HD as master with, Grub1/2, windows, ubuntu /home +/var, and mayby solaris, with SSD as slave having ubuntu / (one partition incl /boot) ?
[16:39] <lynggaard> dupondje, thank you. didn't know that. I was under the assumption the /boot needed to be on the master along with grub :-)
[16:39] <ziroday> lynggaard: sounds like it would work to me
[16:43] <lynggaard> darthanubis, you threw me a bone to a already solved issue, which had very little relevance to my overall query, basically adding nothing much to the information. Next time please assume that people have done their homework.. and you might see that the documentation for doing a setup like mine is not something google/bing is overflowing with
[16:44] <darthanubis> you STILL don't get it?
[16:44] <darthanubis> lynggaard, don't try so hard to piss on help from others
[16:45] <darthanubis> even if you don't like the way in which it is given
[16:45] <darthanubis> you were looking for the word "dual" and if you had READ the page "other OSes" part means what to you?
[16:46] <darthanubis> bing/google would have not helped you, because your search query was NOT found
[16:46] <darthanubis> it required you to do homework you OBVIOUSLY did not do, even with hand holding
[16:46] <darthanubis> we had to read it to you
[16:47] <darthanubis> are you done addressing me now?
[16:47] <darthanubis> because I'm done with you
[16:47] <darthanubis> k?
[16:49] <lynggaard> darthanubis, yes I saw the Other OS'ses part before logging in here, but it does not tell of partition strategies or installation orders (e.g. in dual boot it is normal to start with windows, but what about triple ). It is only a reference to an already solved grup bug. and the workaround was listed directly in the page, so I had allready moved on to other issues.
[16:49]  * darthanubis oh god
[16:50] <darthanubis> where is that moronic kid when you need him
[16:50] <lynggaard> darthanubis, maybe you should work on your support skills? you could improve a bit on your people skills ;-)
[16:50] <darthanubis> he was at least entertaining :/
[16:53] <lynggaard> ziroday, many thaks for the nice and informative replies. Do you by any change have a pointer to the best installation order. I usually only do dual boot, with windows first, and I am not sure when to install opensolaris ? is between windows and ubuntu the best bet?
[16:54] <ziroday> lynggaard: I would probably do Windows, then OpenSolaris finishing off with Ubuntu. You might want to chart out your partitions beforehand with a livecd however.
[16:58] <lynggaard> ziroday, the livecd part that is an excellent suggestion thanx :-) and for confirming then OpenSolaris should go in the middle. I think all I need to figure out now it if/how I can place the solaris "read-only" parts on the SSD as well, but I think that is for another forum
[16:58] <ziroday> lynggaard: good luck
[16:59] <lynggaard> ziroday, thanks, have a nice day
[16:59] <ziroday> lynggaard: you too!
[17:53] <ripps> suspend/resume seems to be broken again in Karmic, it used to suspend, but the display would never resume before intrepid, and now it's doing it again in Karmic
[19:41] <dupondje> pfft, this noise bug is really annoying
[19:41] <dupondje> nobody else has it, that there comes some noise out of the computer
[19:42] <cyphase> i was wondering.. why isn't karmic using firefox 3.5?
[19:42] <dupondje> when I get for example a Pidgin notice, its silent while the notice is shown, and when it dissapears, its starting again :(
[19:42] <dupondje> cyphase: its not default, but u can just install it (firefox-3.5 package)
[19:43] <cyphase> dupondje: yea.. but why?
[19:43] <cyphase> dupondje: 3.5 is going to be default when karmic is released
[19:43] <dupondje> maby
[19:43] <dupondje> no id
[19:43] <cyphase> dupondje: maybe?
[19:43] <DanaG> what noise?
[19:43] <dupondje> cyphase: yes
[19:43] <dupondje> DanaG: dunno where it comes from :s
[19:43] <DanaG> describe it, I mean.
[19:44] <cyphase> dupondje: why maybe? it's going to be out for months by the time karmic is released
[19:44] <dupondje> DanaG: its quite difficult to describe :p
[19:45] <DanaG> high-pitched whining or warbling, or something?
[19:45] <DanaG> Some noises computers can make are due to power regulation.
[19:45] <DanaG> ... for example.
[19:45] <cyphase> it's probably the aliens trying to contact you
[19:45] <dupondje> DanaG: sounds like hdd spinning more
[19:48] <dupondje> DanaG: seems like its the hdd
[19:48] <dupondje> no sound when hdd is accessed
[19:48] <dupondje> and sound while its idle :s
[19:48] <DanaG> Oh yeah, sounds kind of like heads unloading.... when they're over the platters, it makes one sort of noise, and when idle, it has a different (honestly, louder) noise.
[19:49] <dupondje> but didn't notice it before going to karmic :s
[19:49] <dupondje> thats the weird thing
[19:59] <dupondje> argh, becomming crazy of it
[20:19] <dupondje> its not Ubuntu it seems, also in windows
[20:19] <dupondje> but way less in windows (guess why, my hdd is never idle there :P)
[20:21] <Quarth> Hi. anyone can help to trace a problem with X on karmic running on a netbook?
[20:21] <dupondje> tell the problem first :) maby somebody can help then :)
[20:22] <Quarth> Sure :=
[20:23] <Quarth> Sure :=
[20:23] <Quarth> desktop freezes on startup, sometime on the login screen, sometimes few seconds/minutes after.
[20:23] <Quarth> It sounds similar to bug:359392
[20:23] <Quarth> https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/359392
[20:24] <Quarth> But don't have an intel chipset, its an HP2133 all based on VIA chipset. But the same synthoms.
[20:26] <Quarth> Any idea? Or, can anyone guide me on contribute with more info?
[20:26] <Quarth> (Sorry but I've been out of linux for some years)
[20:27] <dupondje> I have no id
[20:28] <Quarth> tx dupondje.
[20:29] <dupondje> maby somebody else has :)
[20:29] <Quarth> Hope so :)
[20:30] <Quarth> Anyway, it run after install. I'm sure it's al update problem.
[20:30] <Quarth> Do you know how to downgrade last updates?
[20:33] <dupondje> I think its possible to downgrade with apt, but don't ask me how :D
[20:34] <Quarth> lol :D I also think so! Let's see if someone kows.
[20:34] <Quarth> ^knows
[20:49] <BUGabundo> boas noites
[20:58] <ripps> Some programs such as banshee and mpd aren't able to recurse the files in symlinked directory that leads to my ntfs external harddrive. Do I have something configured wrong?
[21:19] <FoxBlitzz> Why is GRUB in Karmic so much uglier now?
[21:20] <syn-ack> define uglier...
[21:20] <BUGabundo> FoxBlitzz: 'cause its GRUB2 and it doesn't allow stiles?
[21:23] <FoxBlitzz> Is there a way I can replace it with the older GRUB?
[21:27] <BUGabundo> sure
[21:27] <BUGabundo> install it
[21:28] <DanaG> My gripe with grub2: no savedefault.
[21:28] <FoxBlitzz> Yeah, apparently grub2 isn't installed, so I can't uninstall
[21:28] <DanaG> Just install grub; it "conflicts" on grub-pc.
[21:29] <DanaG> So, it'll remove grub-pc (which is grub2).
[21:29] <FoxBlitzz> Ooh, I see
[21:29] <DanaG> Why don't they combine grub-pc and grub-efi like Fedora does?
[21:29] <DanaG> Sure would make it easier for me to use UEFI.
[21:30] <FoxBlitzz> Gah, I don't have a menu.lst
[21:30] <DanaG> It should create one, I believe.
[21:30] <ripps> Does anybody here know why mpd and banshee won't recognize symlinks to my external harddrive?
[21:30] <FoxBlitzz> It didn't.
[21:31] <FoxBlitzz> And all the GRUB2-looking stuff is still there
[21:31] <FoxBlitzz> In /boot/...
[21:35] <FoxBlitzz> Rrrgh
[21:35] <FoxBlitzz> Now I'm stuck at a freaking GRUB prompt
[21:36] <FoxBlitzz> Great, I should have saved a snapshot of the VM
[21:36] <DanaG> Reinstall grub-pc and it'll use the not-removed grub.cfg.
[21:36] <DanaG> Or boot manually and use os-prober, I think it is.
[21:37] <FoxBlitzz> ...How?
[21:43] <Wicla_> No one else having problems with extremly memory-hungry processes? Firefox is eating 940m, compiz.real 791m, Xorg 535m, pulseaudio 287m, gnome-terminal 216m?
[21:44] <BUGabundo> Wicla_: let me check
[21:44] <BUGabundo> 11882      0      0         82K 872.9M 259.4M     0K     0K   7% firefox-3.6
[21:44] <BUGabundo> 28038    495      0        844K   1.0G 252.5M     0K     0K   6% pidgin
[21:44] <BUGabundo> 17333      0      0       1717K 777.0M 212.5M     0K     0K   5% nautilus
[21:44] <BUGabundo>  8588      0      0       2106K 612.6M 118.3M     0K     0K   3% gwibber
[21:44] <BUGabundo>  4442      0      0       1804K 444.1M 88940K     0K     0K   2% Xorg
[21:44] <BUGabundo> 29852      0      0      18865K 118.8M 70992K     0K     0K   2% chromium-brows
[21:46] <Wicla_> VIRT field in `top' is accurate, right?
[21:47] <BUGabundo> this is from atop, and 'm' option
[21:47] <Wicla_> Either way, procceses eats all memory over time until there is non left and system freezes for a few minutes from time to make memory available. :/
[21:50] <BUGabundo> Wicla_: only if you have a memory leak
[21:50] <Sarvatt> let me guess, intel graphics Wicla_? theres a fix for the memory leak under GL compositing in mesa 7.5
[21:51] <Wicla_> yep. intel graphics here
[21:53] <Wicla_> hm, may I ask how to find it? :)
[21:53] <Sarvatt> it'll be fixed in the not too distant future, fixes just got commited yesterday and will be in the mesa 7.5 release any day now, they're just waiting on some word about packaging gallium from debian to update it on ubuntu
[21:54] <Wicla_> ah ok. I'll wait then. Can survive a extra reboot per day :P
[21:54] <BUGabundo> eehh
[21:54] <Sarvatt> turning off compiz makes it go away for now though :D
[21:55] <Unksi> oh, so thats why the weird freezes that seem to come up from nowhere :p
[21:56] <Wicla_> Sarvatt: do you know if there are any fix for that bug which makes the system unable to turn on screen after it has been blanked (probably with dpms)?
[21:57] <BUGabundo> Sarvatt: question: can you help me get compiz working?
[21:57] <BUGabundo> stop working yesterday or so
[21:58] <ripps> So... nobody has any idea why symlinks in mpd worked yesterday, but not today?
[21:58] <Sarvatt> nope, dont have the problem here but there are *alot* of variables involved that arent accounted for by your description there. do you have a bug report with the logs listed by any chance?
[21:58] <Wicla_> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/383973
[21:59] <BUGabundo> Sarvatt: if you want I'll file one, and upload the trace and .xsessionerrors
[21:59] <Sarvatt> i'd put money on that being a gnome-power-manager problem Wicla :D
[21:59] <Sarvatt> sorry bugabundo, whats wrong?
[21:59] <Unksi> thta bug exists on kubuntu as well
[22:00] <BUGabundo> Sarvatt: compiz won't start
[22:00] <Sarvatt> you disabled metacity compositing in gconf and it still wont?
[22:01] <BUGabundo> Sarvatt: http://paste.ubuntu.com/200312/
[22:01] <BUGabundo> Sarvatt: not sure. I had it disable on the last boot, to test it, but lost gnome-do composite suport
[22:01] <Sarvatt> looks like you have metacity compositing enabled there still
[22:01] <BUGabundo> so I enabled it back, and now I can't start compiz
[22:01] <BUGabundo> it always worked before :(
[22:02] <BUGabundo> Sarvatt: but can't I have compiz AND composite?
[22:02] <BUGabundo> I need it!
[22:02] <Sarvatt> BUGabundo: you can only have one compositing manager at a time, metacity has a problem reliquishing control of compositing to compiz, if you disable metacity compositing compiz has no problems starting fine
[22:02] <BUGabundo> but how can I enable composite IN compiz?
[22:02] <Sarvatt> compiz does the compositing if you use compiz!
[22:02]  * BUGabundo disables composite in metacity yet again
[22:03] <BUGabundo> Sarvatt: err No
[22:03] <BUGabundo> at least not with OSD and gnome-do skins
[22:03] <Sarvatt> you cant disable compositing in compiz man, compiz is a GL compositing window manager
[22:04] <Sarvatt> metacity compositing is xrender based instead of 3d based
[22:04] <BUGabundo> Ok compiz is UP again
[22:04] <BUGabundo> Sarvatt: http://paste.ubuntu.com/200313/
[22:04] <BUGabundo> I'll test on the next reboot
[22:04] <BUGabundo> no idea when that will be
[22:04] <BUGabundo> last time it took me 5 days
[22:05] <Sarvatt> that just means some plugins dont work with your hardware, you can disable them in compiz config setting manager
[22:05] <Sarvatt> dont need to reboot, your gnome-do should be fine now?
[22:05] <BUGabundo> it does
[22:05] <Sarvatt> gnome-do just needs a compositing window manager in general for the transparency, doesnt matter which one you use
[22:06] <BUGabundo> but let me restart DO just to be sure
[22:06] <BUGabundo> seems to be working
[22:06] <BUGabundo> but I had lots of trouble before with this settings
[22:09] <BUGabundo> any way, thanks Sarvatt
[22:09] <BUGabundo> as usual, you are very useful and knowledgeable
[22:09] <BUGabundo> 1st cycle here?
[22:25] <anachronik_> hello
[22:25] <mobnoob> hi
[22:25] <BUGabundo> hey anachronik_ and mobnoob
[22:26] <mobnoob> got a problem after installing grub2 lol
[22:26] <billybigrigger> afternoon all
[22:27] <billybigrigger> BUGabundo::: hola senoir
[22:27] <mobnoob> lo billy
[22:27] <BUGabundo> hey billybigrigger
[22:29] <billybigrigger> whats happenin in the +1 world
[22:29] <mobnoob> n e 1 feel like stepping me through fixing my error 11
[22:29] <hexa--> BUGabundo: nothing fixed so far
[22:30] <BUGabundo> Hi hexa--. please remember me of the prob
[22:30] <billybigrigger> mobnoob:::whats up
[22:30] <hexa--> gtk applications crashing
[22:30] <mobnoob> error 11 on grub2 install
[22:30] <billybigrigger> https://wiki.ubuntu.com/Grub2#Error%2011
[22:31] <billybigrigger> tell me if that helps ya :P i know it doesn't look pretty, its a WIP
[22:31] <mobnoob> im not that good yet
[22:32] <BUGabundo> hexa--: still nothing here
[22:32] <mobnoob> but ill try again brb
[22:32] <BUGabundo> sorry for not being more helpful
[22:32] <hexa--> BUGabundo: we tried debugging nautilus, remember?
[22:32] <mobnoob> np
[22:33] <billybigrigger> mobnoob::: basically change ROOT to UUID
[22:33] <BUGabundo> hexa--: ehe not really, sorry. I've the worse memory you can find :)
[22:33] <hexa--> alright
[22:33] <hexa--> so you told me to keep you posted
[22:34] <hexa--> and if you dont remember it anyway... :P
[22:34] <BUGabundo> billybigrigger: ppl still using /dev/sdXY on root?
[22:34] <BUGabundo> hexa--: ahahh
[22:34] <BUGabundo> np
[22:35] <billybigrigger> BUGabundo::: no, theres a bug in grub when updating from legacy to G2 that it is trying to read for example....root "b850ec51-e1d4-48c3-96d2-a2c6e368d2e1"
[22:35] <billybigrigger> when its try to read UUID, so you need to edit the option and change from ROOT to UUID
[22:35] <billybigrigger> i should read up more on the bug, there might be more to it, but i know it only happens when upgrading from legacy to g@
[22:35] <billybigrigger> s/g@/g2
[22:36] <hexa--> BUGabundo: ehm gtk applications are crashing when they are displaying files, like nautilus in genereal and others when confronted with file opening, saving, etc.
[22:36] <hexa--> then we tried debugging nautilus
[22:36] <Sarvatt> that only happened during a chainload for me, actually updating to grub2 fixed it but when i chainloaded i had to change root to uuid
[22:36] <hexa--> which didnt work
[22:36] <hexa--> now i successfully got a backtrace from transmission: http://paste.ubuntuusers.de/395585/
[22:36] <BUGabundo> ahhh hexa--. yeah I seem to recall that
[22:37] <billybigrigger> Sarvatt::: yeah, it happens before you upgrade-from-grub-legacy right?
[22:37] <hexa--> Sarvatt was involved too :)
[22:38] <hexa--> $ transmission
[22:38] <hexa--> (transmission:12393): Gtk-CRITICAL **: gtk_tree_sortable_set_sort_column_id: assertion `GTK_IS_TREE_SORTABLE (sortable)' failed
[22:38] <hexa--> Segmentation fault
[22:38] <billybigrigger> that looks familiar :P
[22:38] <Sarvatt> you arent the first person i've heard from having problems with gtkfilechooser since the update a few days ago hexa, i didnt see any bugs upstream when i looked yesterday though :(
[22:38] <billybigrigger> i think the same thing happens to me when i try to change where i save my files
[22:39] <billybigrigger> in transmission, and in deluge, and i think my bug is caused from libgtk2.0
[22:39] <hexa--> Sarvatt: well i suppose with my data from transmission i can file one
[22:39] <Sarvatt> there was a change in gtk+ 2.17.2 that let gtk file chooser remember sort column status that might be having problems
[22:40] <hexa--> so which package should i report this bug for?
[22:40] <Sarvatt> lets see if its fixed upstream
[22:40] <hexa--> libgtk+2.0?
[22:40] <hexa--> okay
[22:41] <Sarvatt> gtk+
[22:41] <hexa--> i was searching here https://bugs.launchpad.net/ubuntu/karmic/
[22:41] <hexa--> and didnt find anything
[22:42] <Sarvatt> hmm, do those torrent clients show the size column by default when you open up the save file dialogue?
[22:43] <hexa--> i dont remember that
[22:43] <Sarvatt> http://git.gnome.org/cgit/gtk+/commit/?id=68171b506f1a77b33367f69364d9991a4558a242
[22:43] <Sarvatt> its possible they dont and need to to work with the change
[22:44] <Sarvatt> yeah wow alot of fixes related to the sort column crashing upstream
[22:44] <Sarvatt> http://git.gnome.org/cgit/gtk+/log/
[22:44] <ripps> Okay, I've think I know what's going on, mpd runs as the mpd user, but my external harddrive is mounted as 0700 under my username. Apparently this creates a permission issue so mpd won't parse the files there. I don't know why it creates an issue in Karmic, but not Jaunty, but running mpd under my username fixed the issue.
[22:45] <Sarvatt> is it ntfs ripps?
[22:46] <hexa--> Sarvatt: should i still file the bug?
[22:47] <Sarvatt> ripps: disk mounting is handled via devkit-disks now, it could be mounting with different permissions via that instead of how it was handled via hal in jaunty if it helps looking into the bug further
[22:49] <Sarvatt> hexa--: your call, not trying to imply it wouldnt hurt just that theres some problems with the sort field handling since 2.17.2 that may be known and fixed already when we get the update and there might be bugs on gnomes bugzilla about it already
[22:50] <hexa--> alright
[22:51] <DanaG> Sarvatt: oh hey, is your repo with the radeon KMS supposed to not-work for R600?
[22:52] <DanaG> It gives me "failed to initalize radeon.  Disabling IOCTL"
[22:52] <Sarvatt> yep no support for anything higher than r500
[22:52] <Sarvatt> they're working on it
[22:53] <DanaG> ah.  Might be good to at least have it give a "hey, we don't do R600" message, rather than a simple FAIL. =þ
[22:53] <DanaG> It also doesn't drop back to non-modeset... so xorg loads without any EXA and such.
[22:53] <dupondje> sound is still a hell in Karmic it seems :( Flash + Audacious doesn't work, lowering volume goes weird, ALSA & PulseAudio is not syncronized :(
[22:55] <Sarvatt> i'll put a note on the PPA about it, thought it was common knowledge KMS doesnt work on newer than r500 so it didnt occur to me
[22:58] <hexa--> https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/390035
[22:58] <hexa--> here we got
[23:00] <DanaG> Oddly enough, I HAVE had KMS work on my r600, once.
[23:00] <DanaG> I don't remember when that was, though.
[23:11] <hexa--> lol
[23:11] <hexa--> i'm eager to find replys to my bug report :]
[23:11] <BUGabundo> hexa--: what?
[23:11] <hexa--> because it really bothers me
[23:11] <hexa--> you know, you try to file a bug in firefox
[23:11] <hexa--> and you try to upload a backtrace
[23:11] <Lounge> i wanted to ask about something that should be fixed in the next release: In jaunty, if be chance the USB susbsystem crashes, Jaunty will hand in the middle of shutdown, my guyess is its waiting for modprobe, but modprobe is frozen
[23:12] <Lounge> jaunty will hang*
[23:12] <hexa--> but when you try to upload the file firefox crashes :)
[23:12] <hexa--> this channel is not about jaunty
[23:12] <Lounge> can it be made so that if the usb subsystem crashes ubuntu can still shutdown?
[23:13] <scizzo-> !jaunty | Lounge
[23:13] <BUGabundo> Jun 20 23:13:02 blubug kernel: [22358.088322] ata4: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
[23:13] <Lounge> yes
[23:13] <BUGabundo> what does this mean ^^?
[23:13] <scizzo-> Lounge: this channel is for karmic not for jaunty....
[23:14] <Lounge> sometimes bad usb hardware that's not scripted properlly can crash modprobe/usb subsystem, basically leaving it in limbo
[23:14] <Lounge> problem is if that happens, jaunty will get stuck in the middle of shutting down
[23:14] <hexa--> Lounge: please use the channel for the current release, which would be #ubuntu for english
[23:14] <Lounge> hardy didn't
[23:15] <Lounge> i'm basically asking, can this be fixed in karma?
[23:15] <Lounge> please?
[23:15] <scizzo-> Lounge: I would guess that kind of question is a wishlist item to launchpad
[23:15] <Lounge> kk
[23:15] <hexa--> agreed
[23:16] <hexa--> and it would depend strongly on the informations you can supply
[23:16] <scizzo-> Lounge: asking there will also reach out to more developers then asking in this channel since most developers does not sit on IRC
[23:16] <Lounge> um i have an account but can i be linked to the right area in lunchpad, prretty plz :D
[23:17] <scizzo-> !launchpad
[23:17] <hexa--> !wishlist
[23:17] <scizzo-> https://launchpad.net/ubuntu/karmic
[23:17] <scizzo-> maybe
[23:18] <hexa--> ask a question
[23:18] <hexa--> https://launchpad.net/ubuntu/+addquestion
[23:18] <hexa--> here maybe
[23:18] <hexa--> or you can file a bug for jaunty
[23:18] <Lounge> would it be better to report the bug n jaunty?
[23:19] <hexa--> i dont know exactly
[23:19] <scizzo-> if its a wishlist for jaunty then yes
[23:19] <Lounge> i'm not sure if i can repreduce the bug now that i patched the xpad.c for the xbox 360 controller to prevent the usb subsystem from crashing?
[23:19] <scizzo-> if it is a wishlist for karmic then add it to karmic
[23:20] <Lounge> well maybe i can use the unpatched and compile it to try and reproduce it
[23:21] <mobnoob> ;[
[23:21] <Lounge> basically if modprobe does an "abnormal exit" then that means modprobe is hanging
[23:21] <Lounge> because of a bad scripted driver
[23:22] <Lounge> therefore jaunty wont shutdown
[23:23] <Lounge> hardy was able to shutdown with the this problem
[23:23] <Lounge> not sure about ibex
[23:27] <mobnoob> @billy nice post  but i am not that advanced yet
[23:28] <Lounge> anyhoo i did post the xpad.c
[23:28] <Lounge> http://pastebin.ca/1468025
[23:28] <Lounge> patched
[23:29] <Lounge> but that only for fixing that bad driver
[23:49] <Lounge> ok well i submitted a "question" about Jaunty not shutting down after a USB subsystem crash and hopefully it can get fixed for karma aswell
[23:49] <Lounge> https://answers.launchpad.net/ubuntu/+question/74853
[23:50] <Lounge> shouldn't be that hard to produce a modprobe abnormal exit/usb subsytem crash
[23:50] <Lounge> my guess is it just required a poorly written driver to enable lol
[23:51] <Lounge> yes i would like to see this fix in karmic koala ^^
[23:54] <ctp> hi folks. beeing debian user for 13 years now and using ubuntu for 3 years, would you recommend karmic for daily work?
[23:54] <Lounge> ctp: karmic is still in the development for the time being
[23:55] <Lounge> unless you wanna test it out
[23:55] <Lounge> but the latest stable version is ubuntu 9.04 Jaunty
[23:56] <hexa--> ctp: clearly not.
[23:56] <Lounge> offically speaking of course "Ubuntu 9.04"
[23:56] <mob_> ty all l8r
[23:56] <ctp> Lounge: i know this fact ;-) i don't expect clean-and-no-trouble-ubuntu but where's the most work in karmic now? is the base stable enough to work with?
[23:57] <Lounge> ctp: it should but expect things to get broken after updates
[23:58] <hexa--> ctp: well, for me there are gtk apps crashing if i use file open/save/save as dialogues
[23:58] <hexa--> or nautilus itself
[23:58] <ctp> hexa--: greets to you martin ;-) you know who is speaking? buzzword: 25c3 ;-)
[23:58] <Lounge> yes
[23:58] <hexa--> oh boy
[23:58] <hexa--> indeed
[23:58] <ctp> hexa--: hehe, global village ;-)
[23:58] <BUGabundo> ehe
[23:58] <Lounge> ctp: always report bugs too to help the developers fix and patch things
[23:58] <BUGabundo> ctp: as long as you can produce decent bug reports
[23:59] <hexa--> also ich würde am liebsten downgraden gerade :)
[23:59] <Lounge> i cant lol
[23:59] <Lounge> i try
[23:59] <BUGabundo> and are ready fro breakage, welcome aboard
[23:59] <BUGabundo> in making Ubuntu better for everyone
[23:59] <ctp> Lounge: well, i'm coding myself on the kernel and like bleeding-edge stuff. so if you say me, i can login into my account, every distro is fine ;-)


[09:18] <Nunosav84> Hi, good morning everyone.
[09:18] <Nunosav84> Following up the suggestion given by danilogondolfo yesterday of using netplan-dbus i was able to establish communication successfully. Now, however, i get an error when writing new configuration.
[09:18] <Nunosav84> command: WRITE=$(sudo busctl call io.netplan.Netplan $CONFIG io.netplan.Netplan.Config Set ss \"ethernets.enp2s0={dhcp4: false, addresses: [<IP_ADDRESS>/24], routes: [{to: default, via: <IP_ADDRESS>}], nameservers: {addresses: [<IP_ADDRESS>]}}"}\" \"00-installer-config\" | awk '{print $2}')
[09:18] <Nunosav84> error: Too many parameters for signature.
[09:18] <Nunosav84> the yaml provided is valid and is the structure used in the config files. Any clue why the error?
[09:54] <danilogondolfo> Hi. I'm wondering if it's that " after the nameserver IP
[09:54] <danilogondolfo> the command seems to work fine
[09:58] <Nunosav84> Sorry, that was a leftover from the logs, i failed to remove it. So that's not the cause of the error
[10:00] <Nunosav84> Is it known what could trigger such error message? I searched the github.com/canonical/netplan repo for it but found nothing
[10:02] <danilogondolfo> I think the error message is from dbus itself
[10:04] <danilogondolfo> it's like it's parsing each part of the string as a separate parameter
[10:19] <Nunosav84> any advice on how to proceed?
[10:30] <danilogondolfo> how do you run this command? trying to understand why you need to escape the quotes
[10:33] <Nunosav84> that was a leftover copied from container logs
[10:33] <Nunosav84> {"level":"info","app":"api","time":"2023-03-10T10:32:37Z","caller":"/src/services/settings.go:285","message":"The new config is {dhcp4: false, addresses: [<IP_ADDRESS>/24], routes: [{to: default, via: <IP_ADDRESS>}], nameservers: {addresses: [<IP_ADDRESS>]}}"}
[10:42] <danilogondolfo> ok, but how are you calling this command? From a script? From go code?
[10:43] <danilogondolfo> buctl is not reading the config as a single big string, but as many separated words, thus the "too many parameters" error
[12:56] <Nunosav> Just to let you know, i was successful modifying netplan *.yaml file in GO code and running only netplan-dbus CONFIG() and APPLY() commands
[12:57] <Nunosav> Thanks for your help danilogondolfo, really appreciated <3 (y)
[13:04] <danilogondolfo> you are welcome :)


[12:16] <ajmitch_> Mez: yes?
[12:16] <Mez> ajmitch_, would you be willing to sponsor ifolder into debian once it's finished being packaged (assuming of course that it's of high enough grade packaging quality)
[12:17] <ajmitch_> maybe
[12:17] <ajmitch_> is this an individual packaging effort, separate from the mono packaging team?
[12:17] <Mez> yes
[12:18] <Mez> though - I will of course be poking a lot of the mono team for advice :D
[12:18] <ajmitch_> oh joy
[12:19] <Mez> well, I've had quite a bit of advice off them already on previous attempts
[12:19] <Mez> so it shouldnt be too bad
[01:10] <crimsun> gah, ENOELMO
[01:10] <ajmitch_> crimsun: he's hiding?
[01:10] <ajmitch_> or he's probably stressing over the move to soyuz
[01:10] <ajmitch_> and drinking his troubles away
[01:11] <crimsun> quite reasonable =)
[01:14] <Lathiat> hah
[02:22] <Kyral> Okay...Its a good thing I found Ubuntu before I found SuSE
[02:22] <raphink> Kyral: sssshhh
[02:23] <Kyral> what?
[02:23] <raphink> :s
[02:23] <raphink> nm
[02:23] <Kyral> Its not like I'm up and leaving Ubuntu
[02:23] <raphink> yeah yeah ;)
[02:23] <raphink> of course not :)
[02:23] <Kyral> I'm just saying Yast is NICE ;P
[02:23] <Amaranth> bored2k did
[02:24] <raphink> what did you use before getting to Ubuntu?
[02:24] <Amaranth> suse doesn't have alacarte ;)
[02:24] <Kyral> Ohh...Slack 10, Gentoo
[02:24] <Amaranth> at least i don't think so
[02:24] <Amaranth> but GNOME 2.16 will :D
[02:24] <Kyral> I don't use the Menu Editor much :P
[02:25] <Amaranth> Kyral: it doesn't have easyubuntu either
[02:25] <Kyral> Amaranth: I don't need EasyUbuntu ;P
[02:25] <Amaranth> or all of us on call to fix things :)
[02:25] <Kyral> okay that you have me :p
[02:25] <Kyral> I'm just saying I wanna help the Yast4Debian project now lol
[02:26] <raphink> Kyral: very nice idea :)
[02:27] <raphink> from what I heard about yast, i'd love to see it in Kubuntu :)
[02:27] <raphink> although i've heard it's so complex a program that it's very hard to port
[02:27] <Kyral> SaX wouldn't hurt either
[02:29] <Kyral> It is a NICE GUI to configure X with
[02:31] <zakame> heya MOTUs :)
[02:31] <Kyral> yo zakame
[02:32] <zakame> yo Kyral :)
[02:36] <raphink> hi zakame
[02:37] <zakame> heya raphink master revu-er :)
[02:37] <raphink> lol
[02:37] <zakame> good job on the motu doc move-around :)
[02:37] <raphink> :)
[02:37] <raphink> thanks
[02:37] <raphink> took me about 10h
[02:37] <raphink> so far no one complained
[02:37] <raphink> I take it it was accepted ;)
[02:38] <zakame> actually it was much-needed :)
[02:38] <raphink> I think so too
[02:38] <raphink> otherwise I wouldn't have done it ;)
[02:38] <zakame> hehe
[02:38] <raphink> now we can see much more clearly what needs to be merged, nuked, and so on
[02:39] <raphink> just have to keep the doc tree up-to-date
[02:39] <raphink> :)
[02:39] <raphink> I got back to REVU today though ;)
[02:39] <raphink> I had enough of the wiki ;)
[02:40] <raphink> did you have a look at the tools I developped today zakame ?
[02:40] <raphink> I just posted a message on ubuntu-motu about them half an hour ago
[02:40] <raphink> oh ok :)
[02:40] <zakame> ooh lemme check then :D
[02:40] <raphink> sure
[02:40] <raphink> :)
[02:44] <zakame> wow, REVU-tools are great :D
[02:45] <raphink> glad you like them :)
[02:45] <zakame> (which also reminds me I should ping siretart about making me an account on tiber for remote REVU ;)
[02:45] <raphink> that's the main thing I did today :)
[02:45] <raphink> yes that's very useful
[02:46] <raphink> I'll ping siretart again tomorrow to get sure he checks my changes to the svn and adds the new revu tools to /usr/local/bin so they can be used by all
[02:46] <raphink> so far I call them with ~/revu-report
[02:46] <raphink> which is not useful for other tiber users
[02:46] <raphink> hehe
[02:47] <zakame> hehe, or package it even ;)
[02:47] <raphink> oh sure I'm thinking of it
[02:47] <raphink> but then it has to be made `distributable`
[02:48] <raphink> i.e. REVU-independent
[02:48] <zakame> ooh right
[02:48] <raphink> so far it depends a bit too much on tiber's settings and scripts
[02:48] <raphink> and I think it can be made independent to run on any box
[02:48] <raphink> even be used by DDs for sponsoring imo ;)
[02:48] <zakame> that would be nice indeed
[02:48] <raphink> if some of them accept these tools ;)
[02:48] <zakame> yeah
[02:49] <raphink> so that's work for the days to come :)
[02:49] <zakame> a lot of rocking on for you then :D
[02:50] <raphink> it's not to find work in Ubuntu ;)
[02:51] <zakame> hehe
[02:51] <raphink> $ ~/revu-report pam-abl_0.2.3-0ubuntu1.dsc pam_abl-0.2.3.tar.gz
[02:51] <raphink> hop :)
[02:52] <raphink> I'd really like to be able to get the upstream tarball automatically
[02:52] <raphink> but I think Debian policy should be changed to be able to do that
[02:52] <zakame> yeah, I think it could also work for doing some auto-merging work
[02:52] <raphink> since there would have to be a place in the package where the url of the upstream tarball would be clearly given
[02:53] <Mithrandir> uhm, you do realise you should review all changes in each upstream version?
[02:54] <Mithrandir> anyway, sleep
[02:54] <zakame> Mithrandir: hmm, that too
[03:04] <raphink> yep, sleep
[03:04] <raphink> dist-upgrading my box and I'm off to bed :)
[03:17] <raphink> gn
[03:22] <zakame> bbl
[04:44] <jsgotangco> heya minghua
[04:44] <minghua> hi jsgotangco
[04:45] <jsgotangco> minghua, i got to talk to sabdfl 2 days ago over lunch and we talked about cjk and scim
[04:46] <jsgotangco> minghua, he's in tokyo at the moment i think but he'll be passing over to korea and china so i guess there will be focus on discussions with such support
[04:47] <minghua> jsgotangco: great to hear about it
[04:48] <minghua> jsgotangco: mako talked about CJK support during last CC meeting too
[04:48] <jsgotangco> oh cool
[04:49] <minghua> there sure is interest, we probably need more people though
[04:58] <jsgotangco> yeah
[05:36] <monzie> i want to contribute to Ubuntu
[05:37] <monzie> i have debian packaging experience
[05:38] <hub> monzie: https://wiki.ubuntu.com/MOTU
[05:39] <hub> monzie: that is the starting point
[05:40] <monzie> thanks, hub
[05:49] <monzie> the docs are a bit confusing hub
[05:50] <monzie> where can i get the list of packages to work on or something like that?
[05:53] <StevenK> From the bug list?
[05:53] <StevenK> It's a litle more complicated than working on Debian, you don't just look after a package or two.
[05:54] <monzie> okay
[05:55] <Amaranth> everyone can touch every package, no one owns a package
[05:55] <Amaranth> makes it easier
[05:55] <StevenK> And harder to find someone to blame. ;-P
[05:55] <Amaranth> no, that's still easy
[05:55] <Amaranth> blame who touched it last
[05:55] <hub> StevenK: changelog is your friend
[05:57] <Amaranth> yeah
[05:57] <Amaranth> btw, never touch firefox
[05:57] <Amaranth> people will try to make you the permanent maintainer :P
[05:58] <StevenK> Heh
[05:59] <StevenK> That's what Diziet is for. :-P
[05:59] <jsgotangco> heh
[05:59] <jsgotangco> seamonkey
[05:59] <StevenK> At my place of work we have a 'the person who touched it last gets to look after it' policy.
[06:00] <StevenK> jsgotangco: The other I've heard is 'iceweasel'
[06:03] <jsgotangco> yeah i think that's the future all in one mozilla suite/components
[06:35] <fubarity> Can someone explain how Ubuntu's package versioning nomenclature works? I have browsed everywhere, only to find very little conclusive. And, moreover, why is it that some packages are <package>-(numbers), while some are <package>-(numbers)-(numbers)ubuntu(numbers)?
-(numbers) means that the package has been synced with debian
[06:36] <crimsun> ok, it's pretty straightforward (you can find this info in the Debian New Maintainer's Guide)
[06:36] <crimsun> packages where the versioning is A.B.C are native Debian or Ubuntu packages
[06:36] <crimsun> those where the versioning is A.B.C-X are Debian-maintained
[06:37] <crimsun> those where the versioning is A.B.C-XubuntuY are Ubuntu-modified from their original Debian counterparts
[06:37] <crimsun> so A.B.C-X, lke Gloubiboulga said, are synced straight from Debian
[06:37] <psusi> -ubuntuN is for packages with ubuntu specific changes that replace the previous version from debian, but the next version from debian will be newer than the -ubuntuN
[06:46] <fubarity> Now, suppose that I am going to Debianize (i.e., make a *.deb) a package for Ubuntu for a package for which no actual Debian package exists. Which nomenclature would I use? And what do the X and Y components surrounding XubuntuY mean?
[06:47] <crimsun> if it doesn't exist in Debian yet, then you'd package it as A.B.C-0ubuntu1
[06:47] <crimsun> that way when it enters Debian, Debian's versioning has higher precedence
[06:47] <crimsun> (A.B.C-1)
[06:48] <fubarity> So, what do the 0 and 1 mean? Could these variables have any other values?
[06:48] <crimsun> they signify packaging revisions (as opposed to "upstream" versions)
[06:49] <crimsun> and no, for the case you describe, X must be 0, and Y must be 1
[06:50] <crimsun> generally, however, yes, X and Y are not tightly coupled
[06:51] <zakame> this nomenclature is to avoid possible clashes when someone from Debian decides to make a NEW package (which could either be based on your Ubuntu package, or created from scratch altogether; see njam for an example ;)
[07:01] <fubarity> I appreciate everyone's help here; it means a lot.
[07:01] <zakame> no prob :)
[08:08] <Kyral> Night MOTU
[09:16] <siretart> good morning soyuz lovers!
[09:16] <siretart> :)
[09:16] <siretart> this is what I call quick response: debian #351280
[09:16] <zakame> good morning siretart ! :D
[09:16] <siretart> hi zakame
[09:17] <siretart> zakame: I have a hilight in my backlog, you wanted some sort of 'remote' access to revu?
[09:17] <siretart> huh?
[09:18] <zakame> yeah, but the gist of that is I want to be able to test build of REVU-ed packages, not necessarily shell access
[09:19] <siretart> currently you need shell access to call revu-build
[09:19] <zakame> ah
[09:34] <zakame> heya Hobbsee
[09:34] <Hobbsee> hey zakame :)
[09:38] <zakame> what's up?
[09:39] <Hobbsee> just got home from work, having trouble building asciiquarium
[09:43] <zakame> oooh
[09:43] <zakame> brb, someone needs to call :/ (dialup)
[09:54] <TheMuso> c
[11:28] <siretart> raphink: I updated /srv/revu to rev 120 (currently HEAD)
[11:29] <raphink> siretart: thanks :)
[11:29] <raphink> siretart: did you make the new links in /usr/local/bin too?
[11:31] <siretart> raphink: done
[11:32] <raphink> thanks :)
[11:32] <raphink> much :)
[11:33] <siretart> no problem
[11:34] <raphink> argh I made a mistake in revu-build though
[11:34] <raphink> siretart: I'll correct it, it's just a small mistake, if you can aprove it fast
[11:34] <raphink> siretart: in revu-build, I've put
[11:34] <raphink> PBUILDEROPTS="--buildresult $(pwd) --logfile ${BASENAME}.buildlog --hookdir /srv/revu1/scripts/pbuilder-hooks/"
[11:35] <raphink> it should be
[11:35] <raphink> PBUILDEROPTS="--buildresult $(pwd) --logfile ${BASENAME}.buildlog --hookdir /srv/revu1/pbuilder-hooks/"
[11:35] <raphink> otherwise it won't work
[11:39] <raphink> siretart: updated the svn with this single change, can you commit it?
[11:45] <siretart> raphink: done
[11:45] <raphink> thanks :)
[11:45] <raphink> I think that's all :)
[11:46] <siretart> raphink: could you please install a .forward file on tiber?
[11:46] <raphink> how do you mean siretart ?
[11:46] <siretart> I'd like to add you to the svn postcommit hook, so that you get svn mails as well
[11:46] <raphink> oh ok
[11:46] <raphink> so what do I need to do?
[11:46] <siretart> raphink: do a 'echo raphink@youremail > ~/.forward'
[11:46] <raphink> ok
[11:46] <siretart> you can also configure procmail, if you wish ;)
[11:47] <raphink> done
[11:47] <raphink> I mean the .forward ;)
[11:47] <siretart> ok
[11:48] <raphink> :)
[02:19] <Gloubiboulga> I have 2 packages on REVU advocated once, could someone have a look at them ?
[02:19] <Gloubiboulga> it's http://revu.tauware.de/details.py?upid=1654 and http://revu.tauware.de/details.py?upid=1650
[03:19] <pabs3> anyone seen Mez? if someone does, can you ping him about his debian ifolder ITP?
[03:21] <Tonio_> hi
[03:59] <apachelogger> is it allowed to patch binary format files into a packge (eg pictures)?
[04:01] <\sh> apachelogger: how are you doing this? you can do it via uuencode/uudecode (sharutils)
[04:01] <apachelogger> made a diff ;-)
[04:01] <apachelogger> so how to do it via uuencode?
[04:03] <\sh> apachelogger: since when is diff doing binary diffs? you can't inject binaries into a source tarball..the only way to do this, is to uuencode the picture (e.g. an icon) move it to debian/dir and uudecode it and install it via debian/rules install target
[04:04] <apachelogger> well, the diff worked somehow ... but wasn't very smart ... I'll take a look at uuencode and uudecode, thx :)
[04:05] <jpatrick> apachelogger: you could try .xpm's
[04:06] <apachelogger> hm
[04:06] <apachelogger> I think kblogger 0.4 will just not have a image, the author might have a reason to not include it
[04:25] <Kyral> Morning MOTUish people
[04:25] <apacheLAGger> morning
[04:26] <jpatrick> Kyral: afternoon
[04:28] <apacheLAGger> so there is still a really anoying problem: http://paste.ubuntu-nl.org/7994
[04:30] <apacheLAGger> any ideas?
[04:31] <\sh> yes
[04:31] <\sh> 1. if this lib is not used by anything else, lintian-override it :)
[04:31] <\sh> 2. if this lib is used by anything else then kblogger, write shlibs file
[04:32] <apacheLAGger> just used by kblogger ...  so I shouldn't care about that error?
[04:33] <\sh> apacheLAGger: lintian-override it :)
[04:33] <apacheLAGger> ok, thx :D
[04:33] <\sh> apacheLAGger: you know how to do it?
[04:34] <apacheLAGger> not really .... but learning buy doing and googling ;-)
[04:37] <\sh> apacheLAGger: lynx file:/usr/share/doc/lintian/lintian.html/index.html :)
[04:37] <apacheLAGger> http://lintian.debian.org/manual/ch2.html#s2.4
[05:24] <apacheLAGger> \sh: http://revu.tauware.de/details.py?upid=1656 :)
[05:26] <dholbach> no need to lintian-override - it's a good reminder to not override it and see the message every time (and split it out once it's needed somewhere)
[05:27] <apacheLAGger> dholbach: but why would it be needed?
[05:28] <dholbach> the lintian-override is surely not needed.
[05:28] <dholbach> Or do you mean the library?
[05:28] <\sh> dholbach: it will never be needed
[05:28] <\sh> dholbach: the library
[05:28] <apacheLAGger> that was my point
[05:28] <dholbach> "never"
[05:29] <\sh> dholbach: it's a typical "local lib of kde apps"
[05:29] <dholbach> You often see that libraries which are splitted out of "applications" are used at some stage.
[05:29] <dholbach> Think of beagle.
[05:29] <dholbach> I don't say "split it out now!"
[05:30] <\sh> I wonder what inside this lib anyways...
[05:31] <\sh> lemme have a look
[05:32] <dholbach> Ask fabbione on his take on this.
[05:32] <Simira> hey! I wanna become a MOTU!
[05:33] <\sh> apacheLAGger: it's only the panel applet of kblogger?
[05:33] <Simira> at least as a start to becoming a dev
[05:33] <ogra> Simira, yay
[05:33] <apacheLAGger> \sh: kblogger is the applet
[05:34] <apacheLAGger> http://kde-apps.org/content/show.php?content=29552
[05:34] <apacheLAGger> the whole app is just an applet
[05:34] <\sh> jesus
[05:34] <apacheLAGger> lol
[05:35] <Simira> ogra: hey, wanna help me make a small application? Tollef rather wants to have a bath...
[05:35] <ogra> Simira, hmm, still particulary busy here ....
[05:36] <Simira> ogra: right. I'll have to wait until tomorrow evening then. Are you still working on the rollout?
[05:39] <ogra> i only work on ltsp ... the LP guys do the rollout ...
[05:39] <ogra> #
[05:40] <\sh> ogra: is elmo with the LP guys?
[05:40] <ogra> yup
[05:44] <\sh> going out for a while...laters
[07:34] <apachelogger> raphink: ping
[07:35] <raphink> hi apachelogger
[07:35] <apachelogger> hey ...I'm the kblogger guy... :)
[07:35] <raphink> ok
[07:35] <raphink> :)
[07:35] <apachelogger> raphink: http://revu.tauware.de/details.py?upid=1657 what does the kblogger 0.3 tarball do in the list?
[07:36] <apachelogger> actually the orig.tar.gz should be exactly the 0.4 from kde-apps, cause I repacked it today
[07:36] <raphink> ooops
[07:36] <raphink> right should be 0.4
[07:36] <apachelogger> ;-)
[07:36] <raphink> ok good sorry
[07:36] <apachelogger> no problem
[07:37] <raphink> give me the url of the 0.4 package please
[07:37] <raphink> and I'll run it again
[07:37] <apachelogger> http://whiletaker.homeip.net/~christian/kblogger-0.4.tar.bz2
[07:38] <raphink> thanks
[07:40] <raphink> apachelogger: waita  min ok?
[07:48] <apacheLAGger> raphink: looks better, doesn't it?
[07:48] <raphink> wait a min
[07:49] <apacheLAGger> yup
[07:49] <raphink> I'm doing lots of thigns
[07:49] <raphink> there's still the debuild test I'm not very happy with apachelogger, have a looka t it please
[08:02] <raphink> apachelogger: ok?
[08:02] <apachelogger> raphink: new verison online
[08:02] <raphink> ok
[08:03] <apachelogger> add a unpatch rule
[08:03] <raphink> I'l lhave a look
[08:03] <apachelogger> s/add/added ;-)
[08:04] <raphink> running the test, let's wait till it builds :)
[08:04] <raphink> I'll brb
[08:09] <raphink> looks good now apachelogger, good job... :)
[08:09] <raphink> I'll look at it after my dinner
[08:09] <apachelogger> thx :)
[08:10] <raphink> apachelogger: do you know of the Reviewing guideon the wiki?
[08:10] <apachelogger> nope
[08:10] <raphink> http://wiki.ubuntu.com/MOTU/Packages/Reviewing
[08:10] <raphink> main points to check in a package
[08:11] <raphink> so you can check it yourself :)
[08:11] <apachelogger> ok :)
[09:57] <phanatic> hi people
[11:06] <sebest__> hello, is the login pass on revu the same as launchpad?
[11:09] <minghua> sebest: no
[11:09] <hub> sebest__: no
[11:10] <sebest__> how to get a login?
[11:12] <hub> https://wiki.ubuntu.com/MOTU/Packages/REVU?action=show
[11:14] <sebest__> thanx
[11:45] <LaserJock> hi Hobbsee
[11:45] <Hobbsee> hey LaserJock
[11:46] <LaserJock> how's it going?
[11:48] <Hobbsee> just finished building koffice for Riddell
[11:49] <LaserJock> sweet
[11:51] <Hobbsee> for dapper
[11:53] <raphink> cool :)
[11:55] <Hobbsee> yeah


[07:44] <error404notfound> when I run date, it shows correct date but with CET, I want it to be PKT, how to do that?
[07:44] <error404notfound> oopss, wrong channel
[07:44] <error404notfound> man, I keep confusing ubuntu and ubuntu-classrom
[20:10] <oly562> id like to remove avahi-daemon, but it deps on ubuntu-desktop. of course i know better, but howto remove with apt-get above the normal remove switch so that the desktop doesnt go away... thanks
[20:10] <oly562> ill be here for a bit, let me know your suggestions
[20:10] <oly562> maybe i could just shut the service off in /etc/rcX
[20:11] <oly562> also, how exactly can i do this, im new to ubuntu, not linux
[20:11] <oly562> whats the "ubuntu" way to remove a service from init, and i just read lately about how ubuntu will ditch the init process? something to that effect and move to another way.....
[20:11] <oly562> comments, suggestions, thanks.. bbiam
[20:13] <oly562> ... is now reading man update-rc.d
[20:14] <oly562> this doc update-rc.d is a little outdated... 2005 nov
[20:15] <oly562> anyone know BUM?
[20:15] <oly562> man sysv-rc-conf
[20:15] <oly562> no manual
[20:17] <oly562> should i just chmod 400 /etc/initd.d/avahi-daemon  will this break other things on the ubuntu-desktop? if so,, what?
[20:17] <oly562> bbiab
[20:25] <maxb> oly562: #ubuntu-classroom is used for scheduled classes only. Ad-hoc questions are welcome in #ubuntu
[21:02] <oly562> back
[21:02] <oly562> sorry
[21:02] <oly562> maxb: im banned from #ubuntu. can you have them lift me, its been over 2 months now... sighs
[21:03] <oly562> id glady go there, but ya know... shrugs... i believe it was fennel something like or someone else... let me know if you can help out. i only come on here when i need a little help, and i pretty much talk the same way i did here, YET, they banned me, cheesy....
[21:03] <oly562> howto list the admins of a room in here? i forgot... so i can pm one of them
[21:03] <maxb> fennel is a vegetable. I don't understand what you mean :-)
[21:04] <oly562> lol
[21:04] <oly562> its a nic
[21:04] <oly562> ferral fennel somthing like that, its been 2 months
[21:04] <oly562> i dont remember
[21:04] <oly562> can you ask or tell me how i can pm one of them, i forgot the command to list admin with / switch
[21:04] <oly562> in here
[21:05] <oly562> note, he is in this room as well quite often.. last i remember
[21:05] <oly562> if you can help, that would be great!
[21:07] <oly562> whats the command to list ops? in a room
[21:08] <maxb> oly562: I have asked on #ubuntu, apparently #ubuntu-ops is the place you need to ask
[21:08] <oly562> k
[21:08] <oly562> tanks
[21:42] <tinel> date -u
[22:18] <oly562> how can i send mulitple pm's im's to people on irc?
[22:18] <oly562> or do i have to do that one by one
[23:27] <maxb> (1) This isn't a suitable channel to be asking that. (2) There's no reasonable reason to mass PM people.


[10:09] <seb128> tjaalton, mlankhorst: hey, do you know if there are any know "image corruption issue" with the new intel in saucy? it seems a bit similar to the sna one during raring but easier to trigger
[10:10] <tjaalton> seb128: I haven't noticed anything
[10:11] <tjaalton> what hw, what app?
[10:11] <seb128> i5 (ironlake?), firefox
[10:11] <seb128> quite similar to the one I pinged you about in raring
[10:11] <seb128> when you told me to try without sna (iirc)
[10:11] <seb128> I should perhaps try that again :p
[10:11] <tjaalton> yeah could be the same/worse
[10:12] <seb128> :-(
[10:12] <seb128> do you know if anyone is working on those issues upstream?
[10:12] <tjaalton> but maybe file a new bug against -intel if it's easier to hit
[10:12] <tjaalton> ickle should be
[10:13] <tjaalton> he also monitors the incoming bugs
[10:13] <seb128> bug on launchpad or fdo?
[10:13] <tjaalton> lp is fine
[10:13] <seb128> I've the issue on every second tab opening in firefox
[10:13] <seb128> on the tab summary grid
[10:13] <tjaalton> with a screenshot of the corruption in case it's not the same afterall
[10:13] <seb128> but also in chromium url bars
[10:13] <tjaalton> ah
[10:13] <seb128> and some other places
[10:14] <tjaalton> so it got worse with the -intel update?
[10:14] <mlankhorst> hm I doubt they would have released a new version if they thought it caused a regression, so just check for bugs
[10:14] <mlankhorst> or file one :)
[10:15] <tjaalton> it could be further fallout from copy-on-write support
[10:15] <tjaalton> which happened in 2.21.7
[10:15] <tjaalton> raring has .6
[10:15]  * mlankhorst appears to be hitting some regression with nouveau atm, no fun :/
[10:17] <seb128> tjaalton, yes, I had it once a day in raring, in saucy I can trigger it in 1 min
[10:18] <tjaalton> i have occasional corruption with terminator, but not in other apps
[10:18] <seb128> shrug, got another of those compiz-lock when coming back from guest
[10:18] <tjaalton> yeah still there :/
[10:19] <tjaalton> should be traced
[10:26] <seb128> tjaalton, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1189850 and https://launchpadlibrarian.net/142156716/corruption.png
[10:27] <tjaalton> seb128: thanks
[10:28] <seb128> tjaalton, it doesn't happen with uxa, I added a comment saying that
[10:31] <tjaalton> ok
[12:24] <mlankhorst> finally, isolated those nouveau lockups to a single missing flush :/
[17:11] <tjaalton> hmm, are new driver uploads pushed to both main repo and staging now?
[17:12] <tjaalton> I see the same -intel version on both
[17:13] <tjaalton> guess it's ok, just needs a new bump when copying to the archive
[17:27] <tjaalton> mlankhorst: you didn't remove test/tearing.mp4 from -intel?
[17:31] <tjaalton> heh, ppa didn't have the same version.. of course
[20:28] <bjsnider> tjaalton, is there a way i can test if i'm using sna?
[20:28] <jcristau> grep -i sna /var/log/Xorg.0.log
[20:45] <mlankhorst> tjaalton: build fails if I don't remove it, so I remove it everytime
[20:47] <tjaalton> mlankhorst: so need to remove it from the branch
[20:50] <mlankhorst> is the file from upstream? if so probably harmlless to keep
[20:50] <mlankhorst> we have to do the same for libdrm anyway
[21:06] <tjaalton> still one thing to remember every time
[21:06] <tjaalton> with libdrm it's different
[21:07] <mlankhorst> shrug, we could ask upstream about it ;)
[21:07] <tjaalton> I did
[21:07] <tjaalton> if it'll get on the tarball for the next release then it's not an issue


[06:10] <marinelli> morning everyone
[06:12] <marinelli> there's an annoying bug with jitterentropy-rngd/hirsute -> https://bugs.launchpad.net/ubuntu/+source/jitterentropy-rngd/+bug/1922272
[06:13] <marinelli> I think it would make sense to fix it before releasing hirsute
[06:14] <marinelli> btw, the solution is to update the ubuntu version with the one in debian/testing
[06:15] <marinelli> I experienced the bug on my laptop (running hirsute/hirsute-proposed), and with the patched version jitterentropy-rngd does not show that behaviour
[08:44] <xnox> mwhudson:  well..... if you are up on VPN you can actually fuse mount rsync of the mirror.
[08:44] <xnox> mwhudson:  you can also only have a partial mirror (rsync unsplit mirror on people.canonical.com and then locally) after that only do `apt download` a few bits and pieces.
[08:45] <xnox> mwhudson:  or fix ubuntu-cdimage & debian-cd to use things over the network.
[08:45] <xnox> mwhudson:  btw i edit the mirror script a lot to skip most of the things.
[08:45] <xnox> i ponder if it will not be too hard to change everything to file:/// and then later allow for http://
[09:21] <seb128> mwhudson, hey, did you plan to fix the ubuntu-drivers-common build issue?
[10:04] <mwhudson> seb128: i filed a PR a couple of hours ago
[10:04] <mwhudson> seb128: https://github.com/tseliot/ubuntu-drivers-common/pull/52
[10:04] <seb128> mwhudson, ah, thanks
[10:04] <mwhudson> i suppose i should test build it this time...
[10:20] <mwhudson> yes it builds now
[10:20] <mwhudson> seb128: last time my PR got merged and uploaded pretty quickly, but i guess i can upload my change tomorrow if it doesn't
[10:31] <seb128> mwhudson, let's see if tseliot is around
[11:11] <Laney> seb128: I just noticed the size we're getting for ubuntu isos is the arm64 one, do we need to add the arch in there as a tag maybe?
[12:46] <rbasak> kanashiro_: looks like there are a bunch of other packages that build-depend on docker. Are these also going to FTBFS now due to the change in docker in bundling in the proposed pockets - same as libpod, etc? http://paste.ubuntu.com/p/BPPktym6dR/
[13:18] <cpaelzer__> wgrant: doko: I'm seeing an odd build fail on groovy (for an SRU build). https://launchpadlibrarian.net/532344737/buildlog_ubuntu-groovy-riscv64.nss_2%3A3.55-1ubuntu3.1_BUILDING.txt.gz
[13:18] <rbasak> kanashiro_: could you maybe stick the depending packages into a PPA (both Focal and Groovy I guess) with proposed enabled to check that they still successfully build?
[13:18] <cpaelzer__> wgrant: doko: only riscv64 fails while it worked yesterday just fine
[13:18] <cpaelzer__> good: https://launchpadlibrarian.net/532187116/buildlog_ubuntu-groovy-riscv64.nss_2%3A3.55-1ubuntu3.1_BUILDING.txt.gz bad https://launchpadlibrarian.net/532344737/buildlog_ubuntu-groovy-riscv64.nss_2%3A3.55-1ubuntu3.1_BUILDING.txt.gz
[13:19] <cpaelzer__> one can see that in the good case, the same spot emits a warning "note: variable tracking size limit exceeded with ‘-fvar-tracking-assignments’, retrying without"
[13:19] <cpaelzer__> is that anything known from your riscv64 or toolchain experience?
[13:21] <wgrant> cjwatson: I think this might be the 150 vs 1500 timeout that possibly got reverted?
[13:23] <cjwatson> Hm could be
[13:23] <cjwatson> May have forgotten about that while reflashing, pesky manual steps
[13:31] <seb128> Laney, ups, yes the arch should be a tag, the script does collect it it meant to be used, I've submitted a change for that now
[13:59] <doko> node/npm experts, what's going wrong with https://launchpadlibrarian.net/532496413/buildlog_ubuntu-hirsute-amd64.greenbone-security-assistant_20.8.0-2ubuntu1_BUILDING.txt.gz ?
[14:03] <cjwatson> cpaelzer: I'll fix the timeout, though the reflash process is pretty slow so may take a while
[14:07] <cpaelzer> thank you cjwatson, if you maybe could just restart https://launchpad.net/ubuntu/+source/nss/2:3.55-1ubuntu3.1/+build/21363729 after that is completed that would be great
[14:09] <cjwatson> Sure
[14:18] <cjwatson> cpaelzer: Done (still reflashing, but I gave it an updated builder)
[14:20] <cpaelzer> thanks cjwatson
[14:43] <cjwatson> Reflashing managed to kill one of the VM hosts, sigh
[14:44] <cjwatson> Sorry for the lost build time on 001..030
[14:46] <dbungert> doko: transient network error it looks like to me.  The request looks reasonable otherwise.
[14:48] <doko> dbungert: builds don't have access to the network, so that points to a missing b-d ... but which one?
[14:48] <dbungert> doko: try node-babel-cli please
[14:50] <dbungert> note also that babel tends to bring a lot of friends, so that one missing build-dep might be hiding 10 more
[14:57] <doko> dbungert: how did you see that from the build log?
[14:59] <dbungert> npm ERR! network request to https://registry.npmjs.org/@babel%2fcli failed - the @babel/cli part should be the package name in npm-speak
[16:04] <ginggs> doko: see debian bug #986531 - maybe you don't want to fix greenbone
[16:14] <doko> dbungert: ^^^
[16:15] <dbungert> doko: I think I concur with this analysis.  Even if we wanted to try to fix this, I think that the package has other dependencies that aren't available in ubuntu.
[16:20] <doko> ok, I'll see that I remove these tomorrow
[20:21] <unixbsd> you can find the ubuntuÃ-live memstick for backup of Windows 1, using Ubuntu, the perfect suite for developers like YOU !!! it features partclone: https://openbsdtai123.shell.ircnow.org/ubuntu-live-memstick.html


[00:56] <Ng> has anyone else started seeing weird X crashes and kernel panics in karmic?
[00:57] <Ng> my laptop's done it three times this evening, but not before
[00:59] <Ng> nothing makes it to logs, and even though I get dumped to a console, there's no panic output there
[01:17] <bryce> Ng, nope
[01:17] <bryce> Ng, you could check launchpad
[01:24] <Ng> bryce: I had a quick poke and didn't see anything
[01:25] <bryce> -intel has been super sturdy here
[01:25] <bryce> I've got 3 laptops running it with no problems
[01:26] <Ng> it has been for me too until today. I re-installed with RC and I think I've only rebooted once since then, until I shut the laptop down last night, so some of -updates would only really have started running today, but looking at the logs it's all really boring stuff ;)
[01:27] <Ng> it's weird that I get a console and a wedged kernel (flashing capslock) rather than just a hang in X, and there's no oops text
[01:27] <bryce> did you talk with the kernel guys about it?
[01:28] <Ng> not yet, they're my next stop
[01:28] <Ng> and I'm going to check in with jerone/lool/robbiew tomorrow, all of whom have the same laptop as me
[01:28] <bryce> ok
[01:28] <bryce> out of curiousity, what made you check here first and then kernel?
[01:29] <Ng> I think because it seems like X dies
[01:29] <bryce> (a lot of people do this, but since there's more of them than me I'm wondering how to switch things around)
[01:29] <Ng> heh, this is a fair point :)
[01:30] <bryce> yeah as a general rule if you have a kernel failure, start by solving that.  A kernel fault could easily be the cause of X failing
[01:56] <jg> Ng: or you may have DRAM failures, or the like...
[01:58] <Ng> jg: the thought has crossed my mind, I think I'll leave the thing memtesting while I sleep
[01:58] <jg> Ng: diagnostics are first written to prove hardware works....
[01:58] <jg> (I guess I'm jaded on the topic...)
[01:58] <Ng> hah
[01:59] <jg> but certainly, if it shows problems you have problems.
[02:00] <jg> Ng: I had DRAM problems on a microvax II once upon a time: the problem would only occur if the system was idle.
[02:01] <jg> turns out that the DRAM manufacturer had left a wire off the chip; only if you never referenced the chip would it not get refreshed, and you'd see the failure first thing in the morning when you started to use the machine again.
[02:02] <jg> would run diagnostics forever.  Digital had to hold up shipment of Microvax II's several months while this was figured out.
[02:03] <jg> I happened to be the person who figured out that the systems only failed first thing in the morning after being idle all night....
[09:07] <jcristau> bah no tormod.
[20:30] <tormod> bryce I am getting there: http://git.debian.org/?p=users/tormod-guest/mesa.git;a=summary
[20:31] <bryce> sweet
[20:32] <tormod> some of the commit diffs are ugly because they include the upgrade of the upstream version
[20:32] <tormod> and others are ugly because there is stuff in the package (tarball I guess) which is not in git (WINDOWS/ etc)
[20:33] <tormod> but just to get up to date, maybe it is good enough
[20:46] <bryce> tormod, maybe it needs a script to handle doing it (does debian have something?)
[20:49] <tormod> bryce, I googled quite a bit before I started on it of course. I tried bzr-fast-export/git-fast-import but it failed, I don't know if
[20:49] <tormod> that would handle upstream merges better
[20:52] <tormod> oh I suddenly understood one reason it failed: git tags are more restricted than bzr tags
[20:52] <bryce> oh?
[20:53] <tormod> can not have "~" in a git tag AFAICS
[20:53] <jcristau> tormod: fwiw, if you still want a review/comment on that thing from yesterday, mail works better.
[20:54] <tormod> jcristau, thanks, yes. just mail me your comments if you want
[20:55] <jcristau> no, i mean send me a mail if you want me to look at something :)
[20:56] <tormod> jcristau, I'll do that the next time :)
[21:25] <jbarnes> bryce: ping
[21:25] <jbarnes> bryce: wanted to make sure you picked up http://lists.freedesktop.org/archives/intel-gfx/2009-November/004762.html
[21:26] <jbarnes> along with the other ironlake fixes Zhenyu sent out (http://lists.freedesktop.org/archives/intel-gfx/2009-November/004758.html)
[21:27] <bryce> jbarnes, thanks
[21:27] <bryce> jbarnes, yeah I'm currently distracted from -intel due to -nvidia bugs, but am adding that to my todo list
[21:27] <jbarnes> my ironlake desktop machine is pretty happy with karmic with those bits
[21:27] <jbarnes> bryce: no problem, just wanted to make sure you saw them
[21:27] <bryce> thanks
[21:28] <bryce> yeah it seems (so far) that we've sped up boot speeds to the point that X can start booting before nvidia.ko has finished building.  whoops.
[21:30] <jbarnes> heh
[21:30] <jbarnes> good problem to have
[21:32] <bryce> heh, not if you're active on ubuntuforums apparently
[21:42] <tormod> bryce, is that why fedora is twice as fast as Ubuntu on nvidia according to Phoronix?
[21:44] <bryce> tormod, with that opengl test?  nfi
[21:44] <jbarnes> nv vs nouveau?
[21:44] <bryce> last time I looked into one of the performance regressions they "found" it ended up being just too crackful to get any useful info out.  No one else had the same trouble.
[21:44] <jbarnes> or nv vs nvidia? :)
[21:45] <tormod> they installed nvidia drivers manually on both systems
[21:45] <tormod> wonder what it would look like if they used jockey instead
[21:49] <bryce> wish they published their tests in a way that was more easily reproducible