[00:14] <Palintheus> I'm trying to understand why the stance on this bug is "deal with it" anyone provide some insight? bug 173890
[00:19] <LaserJock> Palintheus: in what way?
[00:19] <Palintheus> "Either way, anyone wanting to use the Ubuntu package is going to have to put up with the periodic breakage. So my point is that they can either wait for the package to go through the update process, or install it themselves."
[00:20] <Palintheus> if someone happens to install flash during one of the times it breaks they could dump ubuntu right there, it seems that the wait or do it yourself attitude shouldn't be the right thing.
[00:20] <LaserJock> Palintheus: that's just one person's opinion though, in that comment
[00:21] <LaserJock> Palintheus: I wouldn't take that as the "stance"
[00:21] <Palintheus> the fact that it's not changed and marked fix released, yet it's currently broken makes me think different
[00:21] <Palintheus> the package was just updated with a new md5sum, not really a fix imho
[00:21] <LaserJock> Palintheus: why would you think that?
[00:22] <Palintheus> because I'm talking to someone right now who is having the issue and is pretty irritated about it after they found that bug
[00:22] <LaserJock> Palintheus: sure, no doubt
[00:22] <LaserJock> it's a very irritating bug
[00:22]  * Hobbsee mutters about propriatory software, and being annoying by default.
[00:22] <Palintheus> Ok.
[00:23] <LaserJock> very irritating to those of use who've had to deal with it
[00:23] <wharp> yes it is, it's a deal-breaker for a new user trying ubuntu
[00:23] <LaserJock> but as far as I know there isn't a really good solution outside of Adobe naming their files differently
[00:23] <LaserJock> which I *think* somebody was talking to them about
[00:24] <Palintheus> or give the user the option to ignore the warning
[00:24] <Palintheus> not as good, but a warning, you could break it do you still want to install
[00:25] <wharp> it's almost a dealbreaker for me and I've used ubuntu for 2+ years
[00:25] <wharp> I just decided to upgrade from hardy to intrepid and now I've got no flash
[00:25] <LaserJock> it's not particularly hard to install
[00:25] <wharp> that's not the point though
[00:26] <wharp> for a new user trying ubuntu the first time it would be
[00:26] <LaserJock> I realize that
[00:26] <LaserJock> but it's not as if you can't get the software period
[00:26] <wharp> right
[00:26] <Palintheus> LaserJock: but then does it get updated with normal updates, and is it easy to switch to the deb?
[00:26] <wharp> but more important than that is getting the issue resolved for other users
[00:26] <LaserJock> heaven forbid you have to go to Adobe to get their software
[00:26] <wharp> not fixing it for myself
[00:26] <maco> Palintheus: no, and yes
[00:26] <maco> in that order
[00:26] <Palintheus> I figured ;)
[00:26] <maco> flash plugins never get auto-updated on $other_os either though
[00:27]  * maco waits for libswfdec to get even more awesomer
[00:27] <Palintheus> ok.
[00:27] <wharp> yeah, I tried using gnash, which just didn't work period
[00:27] <Palintheus> whether or not any other OS works the same way really isn't the issue though.
[00:28] <wharp> right, if Ubuntu wants to be noob-ready, this sort of thing can't happen
[00:28] <LaserJock> it does get a little irritating to get flamed when a service that other OSes don't provide breaks for a bit
[00:28] <LaserJock> we push things through about as quickly as we can
[00:29] <LaserJock> the breakage time sucks, no doubt, and it would be nice to figure out a better way to deal with it
[00:29] <Palintheus> wait what? I never "flamed" because of what another OS does that Ubuntu doesn't
[00:29] <maco> Palintheus: not you, others
[00:30] <LaserJock> yeah
[00:30] <maco> every time this happens
[00:30]  * Hobbsee wondesr why adobe doesn't bother getting their software into the partner repository
[00:30] <LaserJock> I've personally been pretty well jumped, even as I was pushing through an emergency update
[00:30] <LaserJock> Hobbsee: it is
[00:30] <LaserJock> there are two versions of flash in Ubuntu
[00:30] <Hobbsee> oh, is it?
[00:30] <wharp> but, if we want to be better or as good as the rest, jsut because other OSes dont' have it shouldn't be relevant
[00:30] <Palintheus> ok, back to my original question...if it's so irritating why mark the bug fixed, when people see that and they are experiancing the issue I'm sure they get irritated
[00:30] <Hobbsee> oh well, why is it still in multiverse then?
[00:31] <maco> Palintheus: it was fixed last time
[00:31] <Hobbsee> Palintheus: because it's installable again now.
[00:31] <Palintheus> wharp: is it?
[00:31] <LaserJock> Hobbsee: because it was in Multiverse first?
[00:31] <wharp> well how do we go about getting the underlying issue fixed, not just the symptoms
[00:31] <maco> Palintheus: it breaks each time they change it.  so whichever time that bug was filed, the package was updated, and yay it was fixed. and then adobe re-broke it.
[00:31] <Hobbsee> LaserJock: doesn't mean that it needs to stay there, though
[00:32] <LaserJock> wharp: I think by pushing Adobe
[00:32] <Hobbsee> wharp: get people to use the partner repository, and get it from there, where adobe and canonical people can get it uploaded directly.
[00:32] <maco> that whole "convince adobe to change the darned name" idea
[00:32] <LaserJock> Hobbsee: yikes, I don't know that
[00:32] <LaserJock> *about that
[00:32] <maco> LaserJock: why?
[00:32] <LaserJock> so far we've been faster than partner I believe
[00:32] <Hobbsee> LaserJock: well, it depends if partner got added by default, or something.
[00:32] <maco> isnt that why the partner repo exists?
[00:32] <maco> wait, really?
[00:32] <LaserJock> we maintain Flash better than Canonical/Adobe I believe
[00:33] <Hobbsee> well, then poke the partner people.  They've got paid people to maintain it, they should maintain it.
[00:33] <maco> adobe makes their own debs, dont they?
[00:33] <LaserJock> yep
[00:33] <maco> wouldnt it just be a matter of dropping their deb into partner?
[00:33] <LaserJock> yep
[00:33] <LaserJock> we're faster ;-)
[00:33] <Hobbsee> maco: ubuntu doesn't take binaries, afaik.
[00:33] <maco> so people might get it a few days later, but there wouldnt be those few days of breakage in between?
[00:33] <Hobbsee> but it might be a source pulling the binaries, or...
[00:34] <maco> Hobbsee: even for partner? you sure?
[00:34] <LaserJock> it might, I can't remember
[00:34] <LaserJock> look at the .deb size
[00:35] <LaserJock> nah
[00:35] <LaserJock> it's the full thing
[00:35] <LaserJock> not like flashplugin-nonfree
[00:35] <Hobbsee> maco: i would expect so
[00:35] <Hobbsee> maco: id' be surprised if soyuz actually handled binaries uploaded, for anything.
[00:35] <LaserJock> yeah
[00:36] <LaserJock> in any case
[00:36] <LaserJock> it would be useful to find out if talks with Adobe ended up anywhere
[00:36] <maco> Hobbsee: i didnt think the partner repo was done with soyuz. i thought they were just ftp'd up.
[00:36] <LaserJock> it *seemed* to me that they were fairly accomidating, but perhaps that got nixed
[00:36] <maco> LaserJock: they were at least accomodating to have debs now instead of only rpms
[00:37] <Palintheus> OK, then if it's in partner wouldn't it be worth it to delay the package a few days (or is it longer than that) rather than have the breakage?
[00:37] <Hobbsee> maco: new binaries from partner hit the new queue, so i don't think so.
[00:37] <LaserJock> Palintheus: there is *no* breakage if you use partner
[00:37] <LaserJock> Palintheus: in the partner repo the full binary is distributed
[00:38] <LaserJock> it doesn't use the same mechanism that flashplugin-nonfree uses to download from Adobe and install
[00:38] <wharp> but, partner is not how everyone says to install it, and most people dont' have it enabled, or know about it
[00:38] <LaserJock> yep
[00:38] <LaserJock> so I'd start enouraging people to use it, that's what it's there for
[00:38] <Palintheus> ok then if you have partner and multiverse enabled which repo does it pull from/
[00:38] <LaserJock> and eventually we can phase out flashplugin-nonfree
[00:38] <Palintheus> or are they named differently
[00:38] <LaserJock> Palintheus: they have different names
[00:39] <LaserJock> partner is adobe-flashplugin
[00:39] <LaserJock> we *could* drop flashplugin-nonfree altogether and make people use partner
[00:39] <LaserJock> it's kinda "harsh" but would get people moved over
[00:39] <Hobbsee> LaserJock: why harsh?
[00:40] <Hobbsee> LaserJock: although handling upgrades would be a good idea
[00:40] <LaserJock> harsh in the sense that all those people out there reading "install flash by ..."
[00:40] <wharp> LaserJock: yeah, that does sound a bit harsh, but it sounds like the best idea to me
[00:40] <LaserJock> will get dropped
[00:40] <Hobbsee> update the documentation, then
[00:40] <wharp> true, but articles get updated all the time
[00:41] <Hobbsee> replace the package by "warning, this is now somewhere else, you need to use these steps"
[00:41] <wharp> its not jsut documentation, but hundreds of blog posts and articles across the web
[00:41] <Hobbsee> in a gui
[00:41] <LaserJock> seems like last time I talked about this crimsun had a reason not to do it, but I could be remembering wrong
[00:41] <wharp> that's what I was going to suggest Hobbsee but didn't know if that was possible
[00:41] <LaserJock> Hobbsee: hmmm, not sure about that
[00:41] <Hobbsee> wharp: can't see why not, as such.  firefox and such do information bubbles.
[00:42] <LaserJock> I can imagine getting a whole lot of "darn it I installed it and restarte firefox but now flash, WTF?!!"
[00:42] <wharp> should a bug be filed on this?
[00:43] <maco> LaserJock: is it possible to make flashplugin-nonfree a dummy package that enables partner and pulls in adobe-flashplugin?
[00:43] <maco> wharp: ill go post to my blog that adobe-flashplugin is the "right" way
[00:43] <LaserJock> I don't know that you can run apt from a postinst
[00:43] <Palintheus> LaserJock: if there is a way to inform people when installing that the package has moved I don't see it being as big of an issue as that
[00:44] <maco> LaserJock: shall i grab him and make him read my screen to respond? his X is hosed right now.
[00:44] <LaserJock> maco: sure
[00:44] <LaserJock> maco: I just can't remember what he said, but we went rounds about it I remember
[00:44] <wharp> obviously not enough rounds ;)
[00:46] <maco> no, don't do anything with flashplugin-nonfree
[00:46] <maco> asac and I discussed this at uds
[00:47] <maco> there needs to remain an option for people to use 64-bit Flash alphas with nspluginwrapper
[00:48] <maco> canonical can't ship these alphas in partner until the final release
[00:49] <maco> eventually flashplugin-nonfree will be renamed (upon adobe's strong hint) to something along the lines of adobe-flashplugin-wrapped
[00:49] <Palintheus> what are the chances of flashplugin-nonfree going away and moving to adobe-flashplugin?
[00:50] <maco> %50
[00:50] <Palintheus> k
[00:50] <maco> however, there is no guarantee that the native 64-bit version will ship in time for 9.04
[00:51] <Palintheus> so like wharp asked, what is the best way to handle this from a user like us? a bug, just poking randomly?
[00:51] <maco> (that was crimsun...i'm not that in-the-know)
[00:52] <maco> there's no good way
[00:52] <Palintheus> bah.
[00:52] <wharp> well what's the best of the bad ways
[00:53] <maco> update flashplugin-nonfree (via SRU) again
[00:53] <Palintheus> so file a bug when it breaks, and wait
[00:54] <Palintheus> and just deal with the breakage and hope
[00:54] <maco> eventually flashplugin-nonfree will die (there will be a conflicts/replaces in adobe-flashplugin)
[00:55] <Palintheus> ok, so eventually it will move to partner? not following the terminology
[00:56] <maco> no, adobe-flashplugin will remain in partner and eventually offer native 32- and 64-bit plugins
[00:56] <wharp> what's SRU?
[00:56] <maco> it will C/R what was known as flashplugin-nonfree
[00:57] <Palintheus> ok let me rephrase.
[00:57] <Palintheus> eventually there will only be the package in partner?
[00:57] <maco> flashplugin-nonfree's guts may end up as adobe-flashplugin-wrapped
[00:57] <Palintheus> ok
[00:57] <Palintheus> so if that does happen the original issue will still be ther
[00:57] <Palintheus> e
[00:58] <Palintheus> (md5sum breakage)
[00:58] <wharp> no, the adobe-flashplugin does not download from their servers
[00:58] <maco> Palintheus: if and only if there is a package that explicitly depends on nspluginwrapper that also downloads the plugin
[00:58] <Palintheus> no, if -nonfree moves to adobe-flashplugin-wrapped
[00:59] <maco> the intent in the long term is to have adobe-flashplugin Suggest nspluginwrapper
[00:59] <maco> that way there is no more possibility of md5sum breakage
[01:00] <Palintheus> Ok, so eventually the goal is to get away from the current scheme?
[01:00] <Palintheus> i'm really trying to follow this, but it's hard without knowing the normal process of packages, etc
[01:00] <maco> Palintheus: ys
[01:01] <Palintheus> and it's possible, but not likely to be done by 9.04?
[01:01] <maco> ok, here, it's probably clearer like this: for 9.04, still adobe-flashplugin & flashplugin-nonfree. for 9.10, probably only adobe-flashplugin
[01:02] <Palintheus> awesome, thanks so much for explaining maco
[01:02] <maco> (np. it's crimsun)
[01:03] <wharp> a blog post on this and the plan of action might help, if anyone has a chance
[01:03] <Palintheus> ah, well thanks crimsun ;)
[01:03] <LaserJock> sorry, was afk
[01:03] <LaserJock> maco: thanks for getting ahold of crimsun
[01:04] <maco> np, he's hogging my kitchen table trying to configure his keyboard in evdev
[01:04] <LaserJock> wharp: an SRU is a stable release update
[01:04] <LaserJock> wharp: it's the process by which packages end up in -updates
[01:04] <LaserJock> wharp: it normally takes no fewer than 7 days
[01:04] <maco> wharp: well seeing as we dont knwo the actual timeline yet, i'm hesitant to post on my blog all that crimsun said, but i'll go post about using adobe-flashplugin to avoid those md5 headaches
[01:07] <wharp> maco: gotcha, that makes sense
[01:07] <wharp> LaserJock: thanks!
[01:12] <LaserJock> wharp and Palintheus: the reason it can take time to do the update is because we need to test the new flash version
[01:12] <LaserJock> it's not *just* updating the md5sum and pushing it out the door
[01:14] <Palintheus> which is understandable, and that is why I want to get rid of the breakage, not fix it faster
[01:15] <LaserJock> ... if Adobe would just not use the same file name for different versions ...
[01:16] <Palintheus> I realize that.
[01:18] <LaserJock> I wonder how many fresh installs we must have a day
[01:18] <LaserJock> I'm always amazed how many people hit that bug
[01:18] <wharp> well this wasn't even a fresh install, but an upgrade to intrepid from hardy
[01:18] <wharp> and actually I was looking at another flash bug and the resolution was to reinstall
[01:18] <LaserJock> ah, right
[01:21] <maco> LaserJock: lets please just not have that bug crop up within a week of a release! the screams of agony from the installfests would be heard round the world
[01:23] <LaserJock> maco: not a lot we can do about it at this point
[01:24] <Palintheus> how possible is it to source it grabs from adobe until the new release is put through SRU?
[01:24] <Palintheus> *to cache the source
[01:24] <LaserJock> we can't
[01:25] <LaserJock> well, hang on
[01:25] <LaserJock> you mean cache the source on the users machine?
[01:25] <Palintheus> no, grab it from adobe and host it somewhere static that would avoid the md5sum error util it can be updated
[01:25] <LaserJock> well, we can't do that
[01:25] <LaserJock> that's the whole reason we do it the way we do
[01:25]  * Hobbsee notes that would probably violate adobe's licence.
[01:26] <LaserJock> exactly
[01:26] <Palintheus> ah.
[01:26] <LaserJock> hence why we had to get rid of Acrobat Reader as well
[01:26] <maco> i dont understand a desire for adobe acrobat readr
[01:26] <maco> evince loads in about 1/4 the time
[01:27] <maco> and doesnt have a 3 second lag while you wait for it scroll
[01:27] <LaserJock> acroread is still better for me
[01:27] <LaserJock> I use it much of the time over evince
[01:28] <maco> well ive never actually tested acrobat on linux
[01:28] <LaserJock> serious? :-)
[01:28] <maco> i just know it loads in about  the same time as OOo on windows
[01:28] <Hobbsee> sometimes uni students have to use it, with interactive pdfs.
[01:28] <LaserJock> yeah
[01:28] <maco> and OOo isnt exactly filled with helium
[01:28] <LaserJock> I wouldn't be able to use Linux at Uni if it wasn't for acroread
[01:29] <maco> (there, chem joke for ya, LaserJock)
[01:29] <LaserJock> heh
[01:30] <LaserJock> gotta run
[01:30] <LaserJock> it's been fun as always ;-)
[02:41] <Hobbsee> hggdh: guess what
[02:44] <hggdh> Hobbsee, surprise me
[02:44] <hggdh> he is back?
[02:44] <Hobbsee> hggdh: no idea.  but account suspensions relaly work now.
[02:45] <hggdh> COOL
[02:45] <hggdh> finally...
[02:45] <Hobbsee> yup
[02:45] <Hobbsee> or at least, they really work as far as i can tell, i can't seem to break them.
[02:45] <hggdh> heh
[02:46] <hggdh> can we have multiple accounts mapped to the same email?
[02:46] <Hobbsee> no
[02:46] <Hobbsee> iirc
[02:46] <hggdh> good, makes it a bit more time-consuming
[02:46] <Hobbsee> certainly can't have a team using an email attached to anything else in LP
[02:47] <Hobbsee> so i presume it can't for users too
[02:47] <hggdh> I am afraid to try, and find myself locked out
[02:47] <Hobbsee> i created a test account
[02:47] <Hobbsee> wasn't willing to do it on my normal account either
[02:47] <hggdh> yay
[02:48] <hggdh> and I really do not want to go through the hassle of creating Yet Another Email Account
[02:49] <Hobbsee> domain catchalls ftw!
[02:51] <hggdh> I thought of that, but I would have to set up my mail server (and Verizon, my ISP, gets a bit antsy with that)
[02:51] <Hobbsee> gmail handles mail for domains, if you wanted to go that route
[02:51] <hggdh> hum
[02:51] <hggdh> did not know that
[02:51] <hggdh> will look at it
[05:36] <mrooney> anyone know if bug 309574 is in the right package? I would guess that should be flashplugin-nonfree, I have never seen the adobe-flashplugin package
[05:36] <maco> mrooney: adobe-flashplugin is the package adobe makes themselves and puts in the partner repo
[05:36] <maco> it actually includes the binaries
[05:37] <maco> flashplugin-nonfree is in multiverse, i think, and it just downloads adobe's tarball and compiles it
[05:37] <mrooney> oh, interesting, okay
[05:37] <maco> the bug is actually in flash's stuff though, so i think it makes sense to put it in adobe-flashplugin. there's no software actually in flashplugin-nonfree
[05:38] <andersk> Presumably flashplugin-nonfree needs to be upgraded in order to make it download the newer version.
[05:39] <maco> has a newer on been released upstream?
[05:51] <crimsun> flashplugin-nonfree | 10.0.15.3ubuntu1~intrepid1 | intrepid-security/multiverse | source, amd64, i386
[05:51] <crimsun> it has already hit the archives
[05:55] <crimsun> the corresponding fixes for partner are at: http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_10.0.15.3-1gutsy2.dsc http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_10.0.15.3-1hardy2.dsc http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_10.0.15.3-1intrepid2.dsc
[05:56] <crimsun> alexander has a testing version in his ppa for jaunty that pulls from partner instead of downloading from adobe. however, his version does not include the native 64-bit plugin; it's the nspluginwrapper-enabled 32-bit version for both 32- and 64-bit.
[05:56] <crimsun> mrooney: i've triaged that bug
[05:57] <mrooney> crimsun: great, thanks!
[05:57] <kees> crimsun: the jaunty plugin pulls the 64bit plugin
[05:57] <kees> er, jaunty flashplugin-nonfree ...
[05:57] <crimsun> kees: not _his_ version. i know yours does.
[05:58] <kees> okay, right, cool.  I wasn't sure if anyone had noticed my upload yet.  :P
[06:10] <dholbach> good morning
[06:16] <maco> dholbach: hello
[06:17] <dholbach> hi maco
[06:22] <maco> X crashed, and i'm actually running a stable release -_-
[08:31] <BUGabundo_work> gnomefreak: ping
[09:28] <BUGabundo_work> can some one from QA take a look at bug 309483 and help the user collect the extra details he need to file? thanks
[09:37] <BUGabundo_work> Hew: ^^^^^^^^
[09:49] <Hew> BUGabundo_work: Ugh shutdown freezes.. I'm not sure, if the message is relevant then maybe https://wiki.ubuntu.com/DebuggingACPI will help? I think linux is the correct package so hopefully someone more knowledgeable will triage it.
[09:55] <BUGabundo_work> ok
[09:56] <BUGabundo_work> since he mentioned acpi, I filed it against kernel
[09:58] <Hew> yea linux is correct I think, but ACPI problems are usually related to a refusal to boot, from my limited knowledge. I'm not good at triaging linux bugs :P
[10:00] <Hew> BUGabundo_work: I added the DebuggingACPI comment just in case, perhaps acpi=off will fix the shutdown issue, who knows.
[10:04] <BUGabundo_work> yeah
[10:04] <BUGabundo_work> but now the website PT team will also be subscribed to it! nasty LP bug!
[12:46] <xubuntusdi> ciao a tutti
[12:50] <xubuntusdi> anche in thunar non appaiono ho dovuto installare pcmanfm
[13:26] <Hew> !it | xubuntusdi
[13:28] <BUGabundo_work> auau
[13:28] <BUGabundo_work> didn't know we had a multi ling bot!
[13:28] <BUGabundo_work> !pt | me
[13:28] <BUGabundo_work> UIIIIII
[13:28] <BUGabundo_work> PT != BR grrrrrrrrrr
[13:28] <hacktick> hehe
[13:29] <hacktick> !pt_pt | me
[13:29] <BUGabundo_work> will some teach him better!!
[13:30] <hacktick> I think its ok, the brazilian community is way bigger than the portuguese one BUGabundo_work :)
[13:32] <BUGabundo_work> I know
[13:32] <BUGabundo_work> but with don't always get along
[13:32] <BUGabundo_work> at least with should list BOTH channels
[13:44] <hacktick> BUGabundo_work: ubuntu-de is used both by austian and german users
[14:07] <xubuntusdi> sorry I need help I xubuntu 8.10 unfortunately I can not see the disk partitions in Thunar on the desktop or Places able to enter only after you install pcmanfm that? I can to view the partitions ...
[14:14] <hacktick> xubuntusdi: User support is in #ubuntu (or #ubuntu-it)
[14:15] <xubuntusdi> ops sorry
[14:15] <xubuntusdi> :P
[14:15] <xubuntusdi> Helloo
[14:15] <BUGabundo_work> hi
[14:25] <MrKanister> Hi. Can someone set the inportance of bug #304482 to "low" ? Thanks in advance
[14:36] <Hew> MrKanister: Done, thanks for your help :-)
[14:37] <MrKanister> Hew: Thanks for helping me to help ;)
[14:37] <Hew> hehe no worries
[16:09] <fjk> hello
[16:14] <bdmurray> fjk: hi
[16:15] <BUGabundo_work> hi fjk
[16:25] <fjk> i have problem with run my nvidia-settings can i ask for help here ?
[16:26] <pckchem> Sure
[16:26] <pckchem> Although the prefered channel is #ubuntu
[16:26] <fjk> when im trying to run nvidia-settings i recive:
[16:26] <fjk> The error was 'BadLength (poly request too large or internal Xlib length erro'.
[16:26] <fjk>   (Details: serial 141 error_code 16 request_code 128 minor_code 17)
[16:26] <fjk> glxinfo: name of display: :0.0
[16:26] <fjk> Error: couldn't find RGB GLX visual or fbconfig
[16:27] <pckchem> fjk | !paste
[16:27] <pckchem> !paste
[16:27] <fjk> nvidi settings say that is bug
[16:27] <fjk> sry
[16:28] <fjk> http://paste.ubuntu.com/88596/
[16:29] <pckchem> Try this
[16:30] <pckchem> http://paste.ubuntu.com/88598/
[16:30] <pckchem> It's from the forums, I'd have referenced you to the post but they are down and I used a cached version
[16:31] <fjk> but i have glx module in xorg.conf and im think it is loaded
[16:31] <pckchem> hmm.
[16:31] <fjk> my compiz works fine
[16:31] <fjk> but im cannot luchn f.e. counter strike
[16:32] <fjk> im think there is some acceleration when compiz works
[16:32] <fjk> but something mismatch with gdm librares.. ?
[16:32] <pckchem> It's an interesting problem for sure and I'm reading a forum post by someone who has the exact same symptoms and circumstances.
[16:33] <fjk> im trying to install intel linux graphics drivers
[16:33] <fjk> coz im have ubuntu on usb disk and using it in home (nvidia) and in work (intel)
[16:34] <fjk> i think im uninstall almost everything except dmr module
[16:34] <fjk> erlier im trying to lunch opengl on intel graphics card
[16:35] <fjk> and from now i have troubles in home with nvidia-settings
[16:35] <fjk> it is clear ?
[16:35] <fjk> ory for my eng
[16:35] <pckchem> It's fine, actually. I didn't notice.
[16:36] <pckchem> The problem with these USB installations is that often times the specific kernel and settings for ubuntu is set according to the computer you installed it on first.
[16:36] <fjk> wanna some my logs ?
[16:36] <pckchem> So when you try to plug it into something with different hardware, things get a bit troublesome.
[16:36] <fjk> im using this usb system since three months and never have troubles
[16:36] <pckchem> From what it sounds like, installing the intel drivers started this problem, yes?
[16:37] <fjk> im should not try instal this driver
[16:37] <fjk> yes im think that
[16:37] <fjk> yes that im think :)
[16:38] <pckchem> Yes, I'm *thinking* that.
[16:38] <pckchem> Close :)
[16:38] <fjk> i have proper resolution anc color depth....
[16:38] <pckchem> Have you tried reconfiguring the x server?
[16:38] <fjk> yes
[16:38] <fjk> manualy from console and automaticly from recovery kernel
[16:39] <fjk> mybe there is some problem with opengls libraries
[16:39] <pckchem> It could be. Are you using the proprietary NVIDIA drivers?
[16:39] <fjk> yes
[16:40] <fjk> im alredy using its
[16:40] <pckchem> Have you tried reinstalling them?
[16:40] <fjk> tes
[16:40] <fjk> im trying reinstall, and chanding from 177 to 173
[16:40] <fjk> nothing helps
[16:42] <fjk> wanna some logs  ?
[16:42] <pckchem> I can take a look at them, but since I'm not an expert I only tend to get a minimal amount of information out of them.
[16:42] <fjk> :|
[16:42] <fjk> any other suggestions ?
[16:43] <pckchem> I'm combing my resources  right now, give me a minute.
[16:43] <fjk> ok
[16:43] <fjk> mysbe im boot to ubuntu ?
[16:44] <fjk> ok ill be back in few minutes
[16:44] <fjk> im going to boot ubuntu
[16:44] <pckchem> one second
[16:44] <fjk> ok
[16:45] <pckchem> can you pastbin your /var/log/Xorg.0.log file
[16:45] <fjk> ok
[16:45] <fjk> moment
[16:53] <fjk> hi
[16:53] <pckchem> hello again
[16:54] <fjk> http://paste.ubuntu.com/88617/
[16:55] <pckchem> can I also have your xorg.conf?
[16:56] <fjk> yes
[16:56] <fjk> but, now there is no information in conf when im using automaticlu configuration :(
[16:56] <fjk> i have my own config file
[16:57] <pckchem> well post it anyways, that might be the problem.
[16:57] <fjk> http://paste.ubuntu.com/88618/
[16:58] <fjk> and this is my config file which im using when im in home http://paste.ubuntu.com/88619/
[16:58] <fjk> but now my config is overwiritten by configuration from recovery mode
[17:00] <pckchem> can you run glxinfo|grep accel
[17:00] <pckchem> in terminal
[17:02] <pckchem> pastebin what comes out
[17:02] <fjk> but glxinfo giving only :
[17:02] <fjk> Error: couldn't find RGB GLX visual or fbconfig
[17:02] <pckchem> hmm
[17:03] <fjk> illbe back in 2 minutse
[17:03] <fjk> minutes
[17:07] <pckchem> which computer are you on right now? Work or home?
[17:07] <fjk> when im trying install intel driver im install these components: drm, libdrm2.4.1, mesa and xf86 video intel
[17:07] <fjk> home
[17:07] <fjk> nvidia
[17:08] <fjk> mybe i must reinstal my whole desktop ?
[17:09] <fjk> :(
[17:09] <pckchem> dont go that far yet :(
[17:10] <maco> wait um...if you delete xorg.conf, doesnt that force it to re-detect everything so you can redo setup with xfix?
[17:11] <pckchem> Uhh, no more than using the normal reconfigure command, I think. I'm not sure.
[17:12] <fjk> im think this is not problem with xorg.conf and other config files
[17:12] <fjk> xorg.log seems look ok too
[17:12] <fjk> this is problem with som or these intel librairies....
[17:13] <fjk> pckchem, what do u thinking ?
[17:14] <pckchem> I'm out of ideas at this point. My gut instinct is that the problem is due to two sets of graphics drivers conflicting, but I don't know how to prevent it.
[17:15] <fjk> :)
[17:15] <fjk> im dontknown too :)
[17:16] <pckchem> My final idea would be to use synaptics to make sure all NVIDIA drivers are uninstalled. Then install the newest NVIDIA drivers from the NVIDIA website instead of the repos.
[17:17] <fjk> what happend when im completly uninstall  drm compiz gda and all these depending packages ?
[17:17] <fjk> :)
[17:17] <fjk> can i reinstall all these things >? :)
[17:17] <fjk> gdm
[17:18] <fjk> without reinstaling whole sys ?
[17:18] <pckchem> GDM is dependant upon the NVIDIA proprietary drivers?
[17:18] <pckchem> No way.
[17:19] <fjk> when im treing to uninstall libdrm or libmesa  synaptic says tahat must unistall compiz gdla ald milions of libriaries and programs...
[17:19] <fjk> gdm
[17:19] <fjk> sry
[17:20] <pckchem> Don't uninstall libdrm or libmesa. They are probably fine.
[17:21] <pckchem> look for any packages with the nvidia prefix and uninstall those
[17:22] <fjk> ok
[17:22] <fjk> in few minutes
[17:22] <pckchem> system->administration->synaptics package manager
[17:37] <fjk> hi
[17:37] <fjk> im delete all nvidia
[17:37] <fjk> aln some more packages including compiz
[17:37] <fjk> still the same :(
[17:38] <pckchem> If you're uninstalling compiz you did something wrong and removed too many packages.
[17:39] <fjk> forget about compiz
[17:39] <pckchem> Have you tried reinstalling, but with the drivers from the NVIDIA website?
[17:39] <fjk> no
[17:40] <fjk> 177 driver from packages
[17:40] <fjk> this driver work fine eilier
[17:41] <fjk> this is not driver problem... :(
[17:42] <pckchem> No, but it may be a driver configuration problem, which installing using the nvidia configuration utilities might fix. It's the only idea I have at this point. Try asking on the forums if that doesn't help :(
[17:43] <fjk> asking on forums doesn't help :)
[17:43] <fjk> how i can get some more info ? some debug ?
[17:44] <fjk> here im find some post about this http://www.mail-archive.com/dri-devel@lists.sourceforge.net/msg34589.html ...
[17:45] <pckchem> I don't know. http://ubuntuforums.org/forumdisplay.php?f=334  is usually the best resource for these problems. Just be patient.
[17:52] <marmuta> hi, under which source package should I file an xserver crash, xorg or xorg-server?
[17:53] <chrisccoulson> xorg-server
[17:53] <marmuta> great, thanks
[17:53] <chrisccoulson> no problem
[17:53] <chrisccoulson> it doesn't matter really, because the same people will see it, and will reassign it if it's against the wrong package anyway
[17:53] <bdmurray> marmuta: depending on the release of ubuntu using apport to file the bug will gather a lot of information for you
[17:57] <marmuta> thanks, I think I have everything collected. just managed to get a backtrace too.
[17:57] <bdmurray> great!
[18:08] <chimp> I just tried to file a bug report using ubuntu-bug and it sent me to a web page that doesn't exist, a bug in ubuntu-bug?
[18:08] <bdmurray> chimp: did it go to bugs.edge.launchpad.net or bugs.launchpad.net?
[18:08] <chimp> bugs.launchpad.net
[18:09] <chimp> https://bugs.launchpad.net/ubuntu/+source/siggen/+filebug/cG8Rt2S5U62vAM8NxEzb2BaIjOC?
[18:09] <chimp> specifically
[18:09] <bdmurray> stick an edge in there so bugs.edge.launchpad.net ...
[18:10] <chimp> That worked, so that Is a bug then?
[18:10] <bdmurray> chimp: I'm not certain but its on my list of things to look at
[18:11] <chimp> After filing it using ubuntu-bug do I still need to fill in my specific information in further info (version etc.) or has ubuntu-bug already submitted that?
[18:12] <bdmurray> ubuntu-bug has already done that
[18:12] <bdmurray> Thanks for asking!
[18:14] <thekorn> refreshing pages opened by apport or ubuntu-bug after a few seconds also helps
[18:14] <thekorn> hi bdmurray
[18:14] <LaserJock> is pedro around?
[18:16] <bdmurray> LaserJock: he is on Holiday it looks like
[18:16] <LaserJock> heh
[18:16] <LaserJock> doesn't seem to be stopping him from closing bugs ;-)
[18:16] <LaserJock> maybe I'll send him an email then
[18:17] <bdmurray> thekorn: hey there!
[18:24] <fjk> by
[18:24] <fjk> thanks for helping
[19:18] <BUGabundo> ogasawara: ping
[19:34] <ogasawara> BUGabundo: what's up
[19:35] <BUGabundo> hy
[19:35] <BUGabundo> just asking if there is any extra data/tests I can submit
[19:35] <BUGabundo> to bug 308185
[19:35] <ogasawara> BUGabundo: the 2.6.28 kernel is still seeing a lot of churn - so continual testing and updates to the bug will help
[19:36] <BUGabundo> upgrading now to .28.3.3
[19:36] <BUGabundo> there goes my uptime
[19:36] <BUGabundo> lol
[19:36] <BUGabundo> 19:36:29 up 1 day, 19:30,  5 users,  load average: 1.54, 1.53, 1.35
[19:36] <BUGabundo> USER     TTY      FROM              LOGIN@   IDLE   JCPU   PCPU WHAT
[19:36] <BUGabundo> bugabund tty7     :0               Thu00   43:30   2:26   0.04s /bin/bash /usr/
[19:36] <BUGabundo> bugabund pts/0    :0.0             Thu00   37:15m  0.61s  0.61s bash
[19:36] <BUGabundo> bugabund pts/1    :0.0             Thu07   36:52m  0.85s  0.85s bash
[19:36] <BUGabundo> bugabund pts/2    :0.0             11:19    4:30   0.32s  0.32s bash
[19:36] <BUGabundo> bugabund pts/3    :0.0             15:05    2:15   0.25s  0.25s bash
[19:37] <BUGabundo> by the way
[19:37] <BUGabundo> any one here know where I can find devs working on power optimization?
[19:37] <BUGabundo> I have a question about the power needed to keep a laptop on suspend
[19:38]  * BUGabundo is afraid new kernel will stop supporting again suspend and hibernate!
[20:58] <Rocket2DMn> Hey guys, do we support bugs filed in languages other than english?
[21:00] <nhandler> Rocket2DMn: I think they are allowed, but we try and get them translated into English
[21:01] <Rocket2DMn> nhandler, I've seen a few, but I don't think they are well supported
[21:01] <Rocket2DMn> A user asked to translate my bug filing guide into spanish for the LoCos
[21:01] <Rocket2DMn> I was going to include a note about filing in English, unless there was support for other languages that I was unaware of
[21:02] <nhandler> Rocket2DMn: Most of the Developers speak English. As a result, bugs filed in other languages probably will not be fixed as quickly. However, I haven't read anything saying they are not allowed
[21:02] <Rocket2DMn> i've seen a few, but not many
[21:02] <nhandler> I think I've translated the bugs to English using online translators. That way, we at least have a partial translation
[21:03] <Rocket2DMn> I've responded to a few questions and bugs in spanish before
[21:03] <Rocket2DMn> i just havent been able to get a solid answer as to whether we support them
[21:09] <xubuntusdi> hi !!!!
[21:12] <bdmurray> Rocket2DMn: There isn't an official policy regarding non-English bug reports
[21:12] <hggdh> Rocket2DMn, we usually accept them, ask to be translated to English, or they wait for somebody fluent to work on it
[21:12] <Rocket2DMn> thanks bdmurray , i didnt expect there was since i wasnt able to find any documentation about it
[21:13] <Rocket2DMn> i have run across a few bugs/questions in spanish which i have dealt with, i just wanted to see if anybody knew more than i did about the subject
[21:13] <hggdh> bdmurray, we could include a blurb on the standard responses about that
[21:14] <Rocket2DMn> i like that idea
[21:14] <hggdh> something in the line of "the official language is English, please report in English, or please wait for somebody fluent to translate/work on it"
[21:15] <nhandler> hggdh: I'm pretty sure that some wiki page suggests using something like Google Translator to translate them into English
[21:15] <Rocket2DMn> hggdh, do you want to create a separate page about it with the response translated into the primary languages we see?
[21:16] <Rocket2DMn> like on the Bugs/Responses page, have the english response, then a link for triagers to a differnet page where it is translated
[21:16] <LaserJock> it would seem to be a bit odd to have a canned English response tell the reporter to translate into English :-)
[21:17] <hggdh> nhandler, I think so, but auto translators are not as good on generic translation (I have seen some quite horrible ones from French, English, Spanish, and Portuguese to sames
[21:17] <bdmurray> Doesn't that depend on the triager recognizing the foreign language?
[21:17] <Rocket2DMn> bdmurray, yes, but at least its an improvement over ignoring the bug.  i think the majority of langauges are easy to recognize
[21:17] <hggdh> yes, it does. But we could -- with a bit of effort -- have some common languages pre-translated
[21:17] <LaserJock> what if you had a language tag?
[21:18] <LaserJock> and then work with LoCos to have people translating
[21:18] <hggdh> and point on a link if the triager is unable to identify
[21:20] <nhandler> hggdh: I know, but a bad English translation imo is still better than nothing
[21:20] <nhandler> Usually, you can at least partially understand them
[21:22] <YoBoY> hi