=== kklimonda_ is now known as Guest17427
=== Guest17427 is now known as kklimonda_`
=== kklimonda_` is now known as kklimonda_
=== kklimonda_ is now known as Guest63630
=== Guest63630 is now known as kklimonda_`
=== kklimonda_` is now known as kklimonda_
=== yofel_ is now known as yofel
[12:13] <xteejx> vish: Here?
[13:00] <shnatsel> Hi everyone! I have a black screen issue with my Radeon 9200, looks very much like the KMS issues that were plaguing Intel GPUs in Lucid and Maverick betas. Intel black screen issues were mentioned in beta release notes; however, the Radeon issues I have now are not mentioned in the current beta release notes. Does it mean that developers are unaware of the problem? Maybe I reported the bug to a wrong place? The LP bug number is https:/
[13:00] <shnatsel> /bugs.launchpad.net/bugs/725580
[13:44] <shnatsel> hmm... maybe I shall ask this in the devel channel instead?
=== nhandler is now known as [N]
=== [N] is now known as PinkUnicorns
=== AndrewMC is now known as SpockVulcan
=== Pici is now known as ZarroBoogs
[16:18] <seb128> om26er, hi
[16:25] <om26er> seb128, Hi! how are you :)
[16:26] <seb128> I'm fine thanks
[16:26] <seb128> how are you?
[16:26] <seb128> great work on triaging unity bugs ;-)
[16:27] <om26er> I am fine, thanks
[16:32] <Abhijit> hi om26er seb128
[16:33] <om26er> Abhijit, hey! long time ;)
[16:33] <Abhijit> yeah! :-)
[16:35] <Abhijit> om26er, hey what r u doin? are you free?
[16:35] <om26er> Abhijit, yeah I could spare a few minutes
[16:35] <Abhijit> om26er, may i pm you?
[16:35] <om26er> sure
[16:36] <Abhijit> om26er, come in pm
[16:38] <om26er> seb128, so I have been away from empathy and other desktop packages, I hope to atleast nail empathy in the weekends ;)
[16:38] <seb128> hey Abhijit
[16:38] <Abhijit> seb128, hows the things going on?
[16:38] <seb128> om26er, oh, right, sorry I got sidetracked, I was pinging about that actually
[16:38] <Abhijit> :-)(
[16:38] <Abhijit> :-)
[16:39] <seb128> some crash bugs got reported against 2.34 and I was wondering if you were going to triage and upstream those
[16:39] <seb128> or if I should ping kenvandine to do it
[16:39] <om26er> seb128, saturday and sunday and empathy is all clear ;)
[16:39] <seb128> if you have some time of it in the w.e great ;-)
[16:39] <seb128> excellent
[16:39] <seb128> thanks!
[16:40] <bcurtiswx> seb128, i plan on tackling empathy bugs this weekend at my LoCo's bug jam
[16:41] <seb128> bcurtiswx, it will be double triaged then ;-)
[16:41] <seb128> if you guys get it cleaned there is also the telepathy-* ;-)
[16:42] <seb128> telepathy-butterfly especially tend to collect bugs, though in most case upstream needs debug log to work on those
[16:42] <bcurtiswx> seb128, maybe even triple triaged.  Then again, I'm the one running the lessons.. so I may not get to a ton of bugs on my own :P
[16:43]  * om26er thinks telepathy-haze needs actualy love from its developers, it so unmaintained
[16:43] <bcurtiswx> om26er, same with tp-idle
[16:44] <om26er> bcurtiswx, I actually was planning to start a discussion about haze on the -desktop list. atleast some not-working-at-all protocols should be hidden
[16:49] <bcurtiswx> om26er, well according to freedesktop the -haze is still in development... but it has been there for_EVER
[16:50] <om26er> less is more, remove tp-haze :p
=== jcastro_ is now known as jcastro
[17:40] <om26er> does anyone have a view about bug 729280
[17:40] <ubot4`> Launchpad bug 729280 in totem (Ubuntu) (and 1 other project) "Totem's default subtitles fonts should be "Ubuntu Bold" (affects: 1) (heat: 170)" [Wishlist,New] https://launchpad.net/bugs/729280
[17:40] <om26er> also current fonts are quite huge
[17:46] <charlie-tca> If totem is full screen, a 12pt subtitle is hard to see, isn't it?
[17:47] <penguin42> I guess that depends on the screen
[17:47] <charlie-tca> At least on my "tiny" 22 inch monitor, they are
[17:49] <penguin42> charlie-tca: I mean that though - subtitles should be some fixed % of the screen height
[17:50] <charlie-tca> I agree with that. Is it possible, though?
[17:50] <charlie-tca> since they are a font, not an image
[17:50] <penguin42> charlie-tca: Well I'm sure it is - but it might mean that you have to calculate the font size rather than hard code it
[17:50] <charlie-tca> I could see wanting them at 12pt on a small screen, but needing them bigger than 20pt on a large screen, too
[17:51] <charlie-tca> Isn't the font size changeable in preferences?
[17:51] <charlie-tca> If it is, then the default no longer matters, and changing size for the sake of one or two who don't want to change it themselves becomes a mute point.
[17:53] <charlie-tca> but I do agree with changing the actual font used. The one there now is not a good/best choice today
[17:53] <penguin42> I could sympathise with the default should be sane
[17:53] <charlie-tca> What's sane for both 7 inch and 22 inch?
[17:54] <penguin42> charlie-tca: you could have an option for it to calculate it
[17:54] <charlie-tca> yes, but that requires a big change in the program itself
[17:54] <penguin42> charlie-tca: you can also specify fonts in pixels which would make sense if you always know it's 1920x1080 for example
[17:54] <charlie-tca> percentages are better, aren't they?
[17:55] <penguin42> yeh but I don't think that exists in the font system
[17:55] <charlie-tca> whether it is small or large screen makes a difference, not the resolution. I have more real estate on the big screen, and sit farther back from it
[17:56] <charlie-tca> a small font on it becomes invisible fast, but a large font on the small screen becomes hard to read too
[17:56] <penguin42> charlie-tca: I was assuming that the field of view of the two screen szies was going to be similar
=== zyga is now known as zyga-brb
=== zyga-brb is now known as zyga
=== zyga is now known as zyga-dinner
=== SpockVulcan is now known as AndrewMC
=== zyga-dinner is now known as zyga
[22:06] <Tetsuo55> i just came out of hibernation, and as usual the videocard driver crashed
[22:06] <Tetsuo55> but unlike before the computer actually booted up now, so some progress has been made
[22:06] <Tetsuo55> however i find myself unable to find the crash log
[22:06] <Tetsuo55> and apport did not start up either
[22:12] <Tetsuo55> what needs to be done to get bug 612816 fixed?
[22:12] <ubot4`> Launchpad bug 612816 in xserver-xorg-video-intel (Ubuntu) "[MASTER] [gm45] GPU lockup 493062ea (EIR: 0x00000010 PGTBL_ER: 0x00000001) (affects: 9) (dups: 5) (heat: 64)" [Medium,Incomplete] https://launchpad.net/bugs/612816
[22:24] <hggdh> Tetsuo55: in /etc/default/apport -- is 'enabled=1'?
[22:25] <Tetsuo55> no its not
[22:26] <Tetsuo55> shouldn't that be the case though by default?
[22:27] <Tetsuo55> how/why is it 0
[22:29] <hggdh> Tetsuo55: it is only enabled by default on development versions
[22:30] <Tetsuo55> ahh ok
[22:30] <Tetsuo55> but apport does report for me when apps crash
[22:31] <Tetsuo55> is that because of a different setting somewhere?
[22:39] <Tetsuo55> ok i get it. at some point an update disabled the apport function when it flagged the os as stable
[22:40] <Tetsuo55> i have re-enabled it now, as a beta tester i should have it running all the time
[22:41] <Tetsuo55> time to report a ton of natty bugs
[22:41] <Tetsuo55> bbl
=== emma is now known as em
[23:26] <Tetsuo55> in a strange twist of fate, todays updates to natty fix all the bugs i had so far :P