=== blueyed_ is now known as blueyed
[03:19] <askvictor> how do I file a bug report for the installation process?
[03:51] <rusivi> Regarding bug 660864 I think it's awesome that a Linux Journal representative feels comfortable enough to appropriately bug Ubuntu via Launchpad and talk about in his article. It is a huge improvement from his complaining about OOo bugs but not bugging them ;) -> http://www.linuxjournal.com/content/sun-now-oracle-virtualbox-observation
[03:51] <ubot2> Launchpad bug 660864 in linux (Ubuntu) "Ubuntu 10.10 Atheros AR9285 Wireless disconnects ( atl1c ) (affects: 5) (heat: 26)" [Undecided,New] https://launchpad.net/bugs/660864
=== Tommekk is now known as tommekk
[10:07] <geekosopher> i can confirm bug 671711 but I think the option 'safe graphics mode' was removed intentionally and so it should be marked as invalid
[10:07] <ubot2> Launchpad bug 671711 in grub2 (Ubuntu) "Boot option "safe graphics mode" not in kubuntu maverick install cd (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/671711
[10:09] <geekosopher> rather it is the wiki page that needs updating i guess
=== yofel_ is now known as yofel
[12:28] <xteejx> bug 671222 - pretty serious at the moment, just so people are made aware
[12:28] <ubot2> Launchpad bug 671222 in update-manager (Ubuntu) (and 3 other projects) "update-manager fails to start (affects: 5) (heat: 28)" [High,Confirmed] https://launchpad.net/bugs/671222
[12:29] <xteejx> no bvious changes in update-manager itself that could have caused it, is likely to be the python version updates
[12:29] <xteejx> or, its because of these updates that les-than-perfect coding got caught?
[14:27] <Amaranth> Please don't mess with the bug status for compiz 0.9 bug reports right now, upstream is currently using our bug tracker as theirs is down. We'll have 0.9 packages soon enough anyway. :)
[14:37] <cjae> logout has been broken in two releases of kubuntu now, I believe with and without prop drivers
[14:37] <cjae> 10.04 and 10.10
[14:44] <yofel> cjae: I'm sorry, but just saying that it's broken doesn't help us in the slightest, and it works just fine here (or are you using GDM?)
[14:45] <yofel> missed him :/
[14:47] <yofel> cjae: I'm sorry, but just saying that it's broken doesn't help us in the slightest, and it works just fine here (or are you using GDM?)
[14:48] <cjae> no kubuntu
[14:48] <cjae> kdm
[14:48] <cjae> think I reported a bug about it too
[14:48] <cjae> maybe two?
[14:49] <cjae> and kdm is freezing here too on kubuntu 10.10 with proprietary ati driver enabled and under a newly created user as well
[14:53] <ScottK> cjae: Did you read the release notes and try the work around given for logout problems with kdm?
[14:53] <cjae> no
[14:54] <cjae> can I just use gdm instead
[14:54] <ScottK> I think so.
[14:54] <cjae> so is the problem with the ati driver or kdm?
[14:55] <ScottK> The logout problem is an X bug that kdm trips, but gdm doens't because they interact with X differently.
[14:58] <ScottK> Bug #651294
[14:58] <ubot2> Launchpad bug 651294 in xorg-server (Ubuntu) (and 1 other project) "X crash on KDM logout (still - yes, really) (affects: 18) (dups: 3) (heat: 178)" [High,Confirmed] https://launchpad.net/bugs/651294
[16:17] <Santman> Hi, i'm trying the first time to install linux (ubuntu 10.10) with my hp notebook nx9005. At the end of the installation, i press the "Restart now" button an while shutdown the cd drive opens end i get the following error message: "[ 3262.542930] end_request: I/O error, dev sr0, sector 529096" (i tried it two times, once with a cd-rw and second try with a cd-r
[16:18] <Santman> A CD is inside the drive while the shutdown process (i tried it with two different cds and a windows installation with the same hardware, was possible)
[16:19] <charlie-tca> That is a reported bug. If you remove the cd, it should simply restart and give the grub menu
[16:19] <charlie-tca> It does not affect the installation
=== emma_ is now known as emma
[16:30] <Santman> charlie-tca: after removing the cd and restart, the system hangs after playing the startsound
[16:30] <charlie-tca> That is a different bug, then
[16:31] <Santman> ok, but what should/can i do now?
[17:00] <charlie-tca> I think asking in #ubuntu would probably get you more responses.
[17:04] <cjae> ScottK: thanks
[17:12] <cjae> ScottK: Edit /etc/kde4/kdm/kdmrc and uncomment the line "#TerminateServer=true" by changing it to "TerminateServer=true" and restart KDM (reboot the system or sudo restart kdm).
[17:13] <cjae> dont see that line
[17:15] <ScottK> cjae: It should be there (pretty far down)
[17:15] <ScottK> If it's missing you can just add it.
[17:16] <cjae> The proposed workaround (or fix) worked for me. Others might like to know, however, that the TerminateServer=true command should be slotted under the category [X-*-Core], as my file did not have the line uncommented or commented in it.
[17:23] <cjae> ScottK: thanks work now :)
[17:24] <ScottK> cjae: Feel free to add that to the bug.
[17:24] <cjae> k
[19:10] <Tommekk> is there an offtopic channel for developers?
[19:55] <jovaro> Is there anyone here that can help me with a possible bug in xserver-xorg-video-openchrome in 10.04? All info is here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/671925
[19:55] <ubot2> Launchpad bug 671925 in xserver-xorg-video-openchrome (Ubuntu) "Xorg freeze, grey screen, no pointer : xserver-xorg-video-openchrome (affects: 1) (heat: 6)" [Undecided,New]
[19:56] <penguin42> jovaro: You could try #ubuntu-x
[19:57] <jovaro> ok thanks!
[19:58] <penguin42> jovaro: The other thing you could try is xorg-edgers - it's a set of bleeding edge X packages; they can make a bigger mess though - so only try if you can fix stuff
[19:59] <jovaro> I tried using a openchrome driver compiled from trunk but that didn't seem to work, so maybe that won't help?
[20:01] <penguin42> yeh I agree
[20:02] <penguin42> #ubuntu-x is worth a go
[20:04] <jovaro> I posted the question there, hopefully someone will pick it up
[20:07] <penguin42> jovaro: Does the main display work OK?
[20:08] <jovaro> I don't have a main display attached to it right now, but it worked fine yesterday when I had
[20:08] <penguin42> jovaro: Do you run with desktop effects or not?
[20:08] <jovaro> not, it is just fluxbox
[20:09] <penguin42> have you got network access to the box?
[20:09] <jovaro> yes
[20:09] <jovaro> the tv works fine in text mode, just not with X
[20:09] <penguin42> jovaro: I wonder about trying some xrandr commands or xlsdisplay to see if the X server is working and if you can get any info from it
[20:09] <jovaro> but I have network access as well
[20:10] <jovaro> ok, what should I do?
[20:11] <jovaro> I added an extra Xorg.0.log to the bug report btw. This one is when I don't use an xorg.conf
[20:12] <jovaro> Then X crashes with a backtrace suggesting something is wrong with the openchrome driver
[20:17] <penguin42> hmm
[20:18] <penguin42> ok, with your xorg.conf in, you could try sshing in to your machine as you, setting your DISPLAY=:0.0 and doing xlsclients and see if it shows anything
[20:19] <jovaro> ok doing that now
[20:21] <jovaro> ok stupid question maybe, how do I set the display?
[20:21] <penguin42> export DISPLAY=:0.0
[20:21] <jovaro> xlsclients doesn't seem to do anything
[20:22] <penguin42> just hangs?
[20:22] <jovaro> returns to prompt immediately
[20:22] <penguin42> with no output?
[20:22] <jovaro> exactly
[20:23] <penguin42> hmm interesting
[20:23] <penguin42> jovaro: OK, try doing  xterm &
[20:23] <jovaro> it says [1] 9566
[20:24] <jovaro> xlsclients now says xterm
[20:24] <penguin42> ok, so the X server is still running - do you see anything on the displaY?
[20:24] <jovaro> no just the grey screen
[20:24] <penguin42> ok, now do xrandr
[20:25] <jovaro> Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768
[20:25] <jovaro> default connected 1024x768+0+0 0mm x 0mm
[20:25] <jovaro>    1024x768       50.0*
[20:25] <jovaro>    800x600        50.0
[20:25] <jovaro>    848x480        50.0
[20:25] <jovaro>    720x480        50.0     60.0
[20:25] <jovaro>    640x480        50.0
[20:25] <penguin42> jovaro: OK, try and use a pastebin rather than just pasting it here - but OK, so that's almost certainly the wrong res for your TV - what xorg.conf are you using?
[20:26] <jovaro> the one that is included in the bug report
[20:26] <jovaro> I got that from running X -configure
[20:27] <jovaro> there are no modelines there though
[20:27] <penguin42> with the TV plugged in or with the main display?
[20:27] <jovaro> the TV
[20:28] <penguin42> what type/standard of TV?
[20:28] <jovaro> PAL
[20:29] <penguin42> jovaro: OK, I think you need an xorg.conf that sets the right mode for the TV - I've never tried doing that myself
[20:30] <penguin42> jovaro: Try : http://wiki.openchrome.org/tikiwiki/tiki-index.php?page=TVOut
[20:30] <penguin42> actually that whole site!
[20:31] <jovaro> I'll go read that
[20:33] <jovaro> According to the site, it should be able to use the resolution 1024x768
[20:34] <penguin42> hmm ok, I'll believe it then - I don't know how openchrome does TV stuff
[20:37] <jovaro> oh hurray, something on the screen!
[20:38] <jovaro> I just pasted the stuff from that website to my xorg.conf and that seems to work
[20:38] <jovaro> I'll try a modeline with some overscanning now
[20:38] <penguin42> jovaro: OK, so if that works for you, please do two things
[20:39] <penguin42> jovaro: 1) Add the working xorg.conf to that bug, and note that the bug relaly is the --configure doesn't work
[20:39] <penguin42> 2) open a new bug with the crash you get from not having an xorg.conf - which should just work
[20:40] <jovaro> ok, I'll try some other modelines first and then I'll do that
[20:40] <jovaro> thank you so much for your help!
[20:49] <penguin42> no problem
[20:54] <bbordwell> Hello, I hate to progress my own bugs, so could someone make sure this bug is reproducible for me? it should only take a few seconds
[20:54] <bbordwell> https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/671948
[20:54] <ubot2> Launchpad bug 671948 in indicator-sound (Ubuntu) "Indicator-sound closes rhytmbox if opened soon after closing (affects: 1) (heat: 6)" [Undecided,New]
[20:55]  * penguin42 hates to think why it takes 5 seconds
[20:56] <penguin42> sorry, I don't use Rhythmbox
[20:56] <bbordwell> penguin42, thats alright thanks for the willingness
[20:58] <bbordwell> penguin42, it takes 10 second before it actually closes on my system
[20:58] <penguin42> weird
[20:58] <bbordwell> penguin42, do you use banshee>
[20:58] <penguin42> bbordwell: I use exaile
[22:54] <Tommekk> hello, i made a mistake and assigned a bug to me. does anybody know how i can change this?
[22:54] <Tommekk> https://bugs.launchpad.net/ubuntu/+source/gbrainy/+bug/671984
[22:54] <ubot2> Launchpad bug 671984 in gbrainy (Ubuntu) "What time is it? (affects: 1) (heat: 6)" [Undecided,New]
[22:58] <Tommekk> found it myself