[00:11] Some package versions are newer in Precise than Quantal ?! [00:11] that shouldn't be the case I guess ? [00:15] no it shouldn't :\ [00:15] which ones? [00:16] maybe your repo isn't update, dupondje [00:18] https://launchpad.net/ubuntu/+source/bind9 [00:19] info bind [00:19] !info bind [00:19] Package bind does not exist in precise [00:19] !info precise bind9 [00:19] 'bind9' is not a valid distribution: hardy, hardy-backports, hardy-proposed, kubuntu-backports, kubuntu-experimental, kubuntu-updates, lucid, lucid-backports, lucid-proposed, maverick, maverick-backports, maverick-proposed, medibuntu, natty, natty-backports, natty-proposed, oneiric, oneiric-backports, oneiric-proposed, partner, precise, precise-backports, precise-proposed, quantal, quantal-backports, quantal-proposed, stable, testing, unstable [00:19] !info bind9 [00:19] bind9 (source: bind9): Internet Domain Name Server. In component main, is optional. Version 1:9.8.1.dfsg.P1-4 (precise), package size 327 kB, installed size 911 kB [00:20] anyone else getting a "crash" on loading unity [00:20] why are we getting results of precise in this chat room? [00:20] gnomefreak: no more than usual [00:20] FernandoMiguel: please use /msg ubottu [00:21] FernandoMiguel: we havingt added new facts yet give me a moment [00:21] gnomefreak: k [00:21] dupondje: seems to be a security fix [00:21] I assume the quantal will get it soon [00:21] Its uploaded 3 weeks ago ... [00:22] what fix? [00:22] gnomefreak: bind9 [00:22] oh [00:22] newer version in precise then in quantal [00:22] lol [00:23] maybe in proposed or backports maybe why that is [00:23] it is the same version [00:23] It's in updates and security. [00:24] Candidate: 1:9.8.1.dfsg.P1-4 [00:24] There are 2 security patches in precise [00:24] Same version but no fix in quantal. [00:25] The patches were backported from upstream, however. It is possible that quantal gets the newer version at some point. [00:26] Daekdroom: "it is POSSIBLE" :) [00:26] but now its missing a security patch ... [00:26] I know what I said. [00:29] I can't find any bug report on launchpad regarding that. [00:35] that sucked [00:46] anyone else getting a 403 on dpkg update version 1.16.3ubuntu1 [00:48] i cant get past it [00:48] brb smoke [00:52] gnomefreak: I imagine it is related (to avoid temporarily) bug 1015329 [00:52] Launchpad bug 1015329 in dpkg (Ubuntu) "dpkg fails to run after update (error: file triggers record mentions illegal package name `libgtk2.0-0' (for interest in file `/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules'): ambiguous package name 'libgtk2.0-0' with more than one installed instance)" [Critical,Triaged] https://launchpad.net/bugs/1015329 [00:55] Err http://archive.ubuntu.com/ubuntu/ quantal/main dpkg i386 1.16.3ubuntu1 403 Forbidden [IP: 91.189.92.177 80] [00:55] Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/d/dpkg/dpkg_1.16.3ubuntu1_i386.deb 403 Forbidden [IP: 91.189.92.177 80] [00:55] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? [00:55] trism: ^^ i dont think it is the same [00:55] but looking anyway [00:57] i guess i report it [00:58] gnomefreak: not the same, but my guess is they changed permissions so other people won't update to that version until it is fixed (since that is the version with the bug) [00:58] makes sense thanks [00:59] i will hold off filing it until *ubuntu2 [01:15] ok think i caught up on my updates without dpkg update, smoke [01:22] seems cups crashes all over the place [01:25] if you leave evo updates alone and dpkg alone you can update all other packages without much of an issue. the cups crashes do nothing to impeed updates [01:28] impede [01:31] yeah that :) [01:31] thanks === dooglus_ is now known as dooglus [02:43] guys, would compiling a more recent linux kernel like 3.4.3 for ubuntu 12.04 lts break any dependencies that I am unaware of? === nath_will is now known as nathwill === vibhav is now known as Guest81049 === chu_ is now known as chu === yofel_ is now known as yofel === Guest81049 is now known as vibhav [12:19] hiyas all === Jikan is now known as Jikai === Jikai is now known as Jikan === Jikan is now known as Jikai === Jikai is now known as Jikan === LordOfTime is now known as TheLordOfTime === jbicha is now known as Guest6354 === Guest6354 is now known as jbicha_ === andrewaclt is now known as aaustin [19:26] ia32-libs : Depends: ia32-libs-multiarch but it is not installable [19:26] I guess we are having a dependency breakage daily [19:32] I had fun with bug 1015616 today, upgrade with care I guess [19:32] Launchpad bug 1015616 in dpkg (Ubuntu) "dpkg fails with status parsing error after upgrade to dpkg 1.16.3" [Undecided,Confirmed] https://launchpad.net/bugs/1015616 [19:36] yofel: looks like bug 1015567 which I saw a bit earlier [19:36] Launchpad bug 1015567 in dpkg (Ubuntu Quantal) "upgrade failed: mixed non-coinstallable and coinstallable package instances present" [High,Triaged] https://launchpad.net/bugs/1015567 [19:37] yup [19:37] thx [19:40] which I add yesterday [19:41] and fixed today [19:43] Is there a preferred bug number to add to for "mixed non-coinstallable and coinstallable package instances present" ? [19:44] let me check mine [19:45] FernandoMiguel: I think it might be a different bug (although similar looking) from yours yesterday, since this is against 1.16.3ubuntu2 (yours was 1.16.3ubuntu1 unless you added another one later) [19:45] btw, about UEFI we were talking last week. here is a video https://plus.google.com/109386511629819124958/posts/dmVUQwPZSRQ [19:45] trism: AH [19:45] bug 1015329 [19:45] Launchpad bug 1015329 in dpkg (Ubuntu) "dpkg fails to run after update (error: file triggers record mentions illegal package name `libgtk2.0-0' (for interest in file `/usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/immodules'): ambiguous package name 'libgtk2.0-0' with more than one installed instance)" [Critical,Fix released] https://launchpad.net/bugs/1015329 [19:46] I had https://bugs.launchpad.net/bugs/1015329 [19:46] yofel: correcrt [19:46] looked up the changelog [19:47] the coinstallable bug is different. Fun part is that it renders dpkg utterly useless unless you fix the status file [19:48] I had that with cups over a month ago [19:48] trying to fix it, lead me to do a clean install [19:48] ouch [19:51] yofel: I was getting it with libsdl, followed the fix to change Multi-Arch to same. Then it complained about wine1.4 and libsane-common. When apt-get -f install it reverts back to complaining about libsdl-net1.2:i386 again. [19:51] o.O [19:53] bbl , dinner [19:57] Is this a bug which seems to be affecting only 64bit ? [19:58] You're using apt-get right, not aptitude? [20:00] Pici: Me, yes. [20:00] genii-around: okay, just making sure ;) [20:00] !aptitude | for those who don't know [20:00] for those who don't know: aptitude is another terminal-based front-end to APT. You may encounter problems on multiarch installs (11.10 and higher) as aptitude cannot currently handle the same package with different architectures being installed at the same time. See http://pad.lv/831768 for more information. [20:02] Ugh...I can't install lilypond....or gnome for that matter [20:02] I reported a bug for the latter [20:08] genii-around: it would be 64bit only as this is about multiarch [20:12] Do we have bumblebee or something as default now in Quantal ? or [20:17] should i use ubuntu+1 for kde 4.9 betas ? [20:18] yofel: are you there> [20:18] you could use the beta backports too, but +1 works fine except for some dpkg hiccups today [20:19] yofel: i mean the channel [20:19] yofel: you tested 4.9 beta 2 right> [20:19] ah, no, only if you're actually running quantal [20:19] I'm on beta2 yes [20:20] yofel: can you check if microbloging is working for twitter? [20:20] the applet? [20:20] yofel: ya [20:20] sec [20:21] crash [20:22] yofel: right even for me [20:22] Do we have something to support Optimus now in Quantal ? [20:22] yofel: kmix is also malfunctioning, both have the save issue [20:22] kmix works fine, but it had some issues in 4.8 as well that I didn't have [20:23] yofel: " X Error: BadWindow (invalid Window parameter) 3' this is the error message [20:23] yofel: its not with the muti channel audio [20:23] yofel: is that an upstream bug or local one? [20:24] well, it works fine for me. Only crashes I get is kdeµblog and the battery applet config (fixed in master) [20:24] kdeµblog seems like an upstream bug from my crash [20:25] http://paste.kde.org/504812 [20:25] yofel: checking [20:29] yofel: i cant figure out anything can you take a look at my error log? [20:30] sure [20:30] if I add the applet again it doesn't crash - but instead simply doesn't work [20:31] yofel: same here [20:31] yofel: this is a partial log http://paste.kde.org/504824/ [20:31] yofel: what is causing this error "X Error: BadWindow (invalid Window parameter) 3" [20:33] no idea, I don't know how to debug X errors [20:34] yofel: i should tell you i am using nvidia proprietary driver, that is a one good source of bugs [20:35] yofel: so shall i file a bug? [20:35] probably (linus would agree) - but nouveau isn't that much better here [20:35] yofel: true [20:35] feel free to [20:35] yofel: on my way [20:45] Hm. "blah-blah depends dpkg:i386" on a 64bit system [20:51] What is odd... all the 32bit packages it complains about.. if you do for instance apt-cache policy whatever:i386 for those, they have no installation candidates [20:53] yofel: https://bugs.kde.org/show_bug.cgi?id=302267 [20:54] KDE bug 302267 in widget-microblogging "Plasma applet Microblogger doesn't work, crashes the plasma-desktop sometimes" [Normal,Unconfirmed: ] [21:56] OK. So after it hits the libsdl-net1.2 entry in /var/lib/dpkg/status , it doesn't get to read all the entries that come after that, where in this case dpkg is. [22:09] In /var/lib/dpkg/status, I removed the stanzas for: libsdl-net1.2, libsdl-image1.2, xaw3dg, and libsdl-ttf2.0-0. I was able then to complete the apt-get -f install, then a dist-upgrade. After this was able to reinstall them. === chu_ is now known as chu === jbicha_ is now known as jbicha